Strategies for system planning: Difference between revisions

From Engineer-it
No edit summary
No edit summary
Tags: Visual edit Mobile edit Mobile web edit
 
(43 intermediate revisions by 2 users not shown)
Line 1: Line 1:
+
[[File:Clydeview.png|center|thumb|850x850px]]
'''An ''Engineer-it'' chapter managed by the Institution of Engineers in Scotland  '''([http://www.engineers.scot/ www.engineers.scot])
'''An ''Engineer-it'' module managed by the Institution of Engineers in Scotland  '''([http://www.engineers.scot/ www.engineers.scot])


{| class="wikitable" style=" margin-right: 20px; background-color:#DEF6FE; paddng-right:15px; width:200px;  vertical-align:top; text-align:left; float:right; margin-left: 10px;"
{| class="wikitable" style=" margin-right: 30px; background-color:#DEF6FE; paddng-left:15px; width:200px;  vertical-align:top; text-align:left; float:left; margin-left: 10px;"
!<big>Links</big>
|-  
|-  
|'''<big>Strategies</big>'''
|'''<big>Strategies</big>'''
Line 10: Line 9:
[[Top-down strategy]]
[[Top-down strategy]]


[[Risk]]  
[[Risk|Risk control]]  


[[Leadership]]
[[Leadership|Collaboratve Leadership]]
 
[[Planning]]


[[Quantify]]
[[Quantify]]


[[Governance]]
Wise [[governance]]


Integrity
[[Integrity|Professional integrity]]
|-
|-
|'''Papers'''
|'''Papers'''


[http://www.iesis.org/toengineer/To-Engineer.pdf To Engineer]
[https://engineers.scot/office/resources/publications/to-engineer.pdf To Engineer]
|-  
|-  
|'''Case Studies'''
|'''Case Studies'''
Line 32: Line 29:
[http://info.iesis.org/papers/Journal+V156_web_secure.pdf The development of an optical scanner] (p22)  How to develop an innovative product
[http://info.iesis.org/papers/Journal+V156_web_secure.pdf The development of an optical scanner] (p22)  How to develop an innovative product
|}
|}
<div style=" margin-right: 20px; background-color:#DEF6FE; border:solid;  width:200px; height:500px; vertical-align:top; text-align:left; float:right; margin-left: 10px;">
'''afdf'''
fdaf


dad
[[File:Engprocess-6.png|alt=|thumb|500x500px|Figure 1 Features of strategies used in system planning ]]
</div>
[[File:Engprocess-6.png|alt=|thumb|500x500px|Figure 1   Features of an 'engineered' process|left]]             
An engineered outcome results from the use of a range of control strategies that are appropriate in situations of complex uncertainty. The strategies used have universal application in complex problem solving. It is not only engineers who use them: Scientists  'engineer' the development of a drug;  professional engineers will engineer the design and development of an aircraft. Businesses are 'engineered' (or 're-engineered'). 


The strategies form the basis of a 'engineered process' that is used to control the risk of unsatisfactory outcomes.
This page provides infomation about strategies that are used in [https://eit.engineers.scot/index.php?title=Main_Page#System_planning system planning] i.e. in the the management of complex uncertainty.      


Figure 1 shows some features of an engineered process.
Figure 1 shows key features of the strategies.  


Key issues are ''competence'', i.e. the skills of those inolved and ''[[governance]]'',  i.e. how responsility, authority and accountabiliy are allocated.
Key issues are ''competence'', i.e. the skills of those inolved and ''[[governance]]'',  i.e. how responsibility, authority and accountabiliy are allocated.


Competence is shown as having two main components:
Competence is shown as having two main components:  


* Disciplinary expertise i.e. the abilities of those involved to carry out specific tasks.  It is common to require expertise from several disciplines
*Disciplinary expertise i.e. the abilities of those involved to carry out specific tasks.  It is common to require expertise from several disciplines
*Ethos - the principles that guide the actions of the participants.
*Ethos - the principles that guide the actions of the participants.


Whereas 'what you know' might be described in term of disciplinary expertise, ethos is 'how you think'.  
Whereas 'what you can do' might be described in term of disciplinary expertise, ethos is 'how you think'.  


[[Critical thinking]] may be the most important feature of an engineered process. Critical thinkers identify and use guiding principles that lead to engineered outcomes.
[[Critical thinking]] may be the most important feature of an engineered process. Critical thinkers identify and use guiding principles that lead to engineered outcomes.
Line 59: Line 49:
Deep collaboration within the project team with unswerving commitment to the project goals are also key features of an engineered process.
Deep collaboration within the project team with unswerving commitment to the project goals are also key features of an engineered process.


Closely related to commitment is the requirment that the process is underpinned by the highest levels of professional integrity.
Closely related to commitment is the requirement that the process is underpinned by the highest levels of professional integrity.
 
All this needs to be inspired by collaborative [[leadership]].
 
===Learning for system planning===
See [https://eit.engineers.scot/index.php?title=Critical_thinking#Learning_for_critical_thinking Learning for critical thinking]

Latest revision as of 23:24, 7 September 2022

Clydeview.png

An Engineer-it module managed by the Institution of Engineers in Scotland (www.engineers.scot)

Strategies

Critical thinking

Top-down strategy

Risk control

Collaboratve Leadership

Quantify

Wise governance

Professional integrity

Papers

To Engineer

Case Studies

The UK Covid-19 Task Force A successful government project

The development of an optical scanner (p22) How to develop an innovative product

Figure 1 Features of strategies used in system planning

This page provides infomation about strategies that are used in system planning i.e. in the the management of complex uncertainty.

Figure 1 shows key features of the strategies.

Key issues are competence, i.e. the skills of those inolved and governance, i.e. how responsibility, authority and accountabiliy are allocated.

Competence is shown as having two main components:

  • Disciplinary expertise i.e. the abilities of those involved to carry out specific tasks. It is common to require expertise from several disciplines
  • Ethos - the principles that guide the actions of the participants.

Whereas 'what you can do' might be described in term of disciplinary expertise, ethos is 'how you think'.

Critical thinking may be the most important feature of an engineered process. Critical thinkers identify and use guiding principles that lead to engineered outcomes.

Deep collaboration within the project team with unswerving commitment to the project goals are also key features of an engineered process.

Closely related to commitment is the requirement that the process is underpinned by the highest levels of professional integrity.

All this needs to be inspired by collaborative leadership.

Learning for system planning

See Learning for critical thinking