Noen tanker om ingeniørfaglig systemtenkning

Transcription

1 Noen tanker om ingeniørfaglig systemtenkning Dr. ing. Hans Jørgen Professor II - NTNU Phone: (+47) hjd@gassco.no 1

2 Problemstilling Hva bør være innholdet i et fag som skal ha disse tema som læringsutbytte? Vil de foreslåtte tema lede fram til ønsket måloppnåelse? 2

3 Agenda 1. Kort orientering om Systems Engineering ved NTNU 2. Litt om mfaget og gfagets innhold 3. Noen tanker om hva som kan være pensum Kunnskap om disiplinen Anvendelse av prosessen Modellering et viktig redskap Supplerende disipliner Bedriftsinvolvering 4. Sluttkommentar 3

4 Main purpose of the course Provide to PhD students basic principles, methods and thinking applied in Systems Engineering (SE) Provide to PhD students good examples of SE applications in different fields and technologies Apply SE in own PhD work 4 Course s s ultimate success criteria At the end of the course at least 80% of students shall express an opinion that the SE course significantly can improve the scientific and overall quality of their PhD dissertation

5 Programme fall 2011 Day Date Time Room Topic Issues Tuesday B520 Lecture Part 1-3 Wednesday B520 Lecture Part 4-5 Tuesday B520 Lecture Part 6 Wednesday B520 Lecture Part 7 Guest lecture Modeling Tuesday B520 Lecture Supervision Part 8 Student s thesis Wednesday B520 Supervision Student s thesis Tuesday B520 Supervision Student s thesis Tuesday B520 Supervision Student s thesis TBA Exam Presentations 5 Part 1 Introduction to systems thinking Part 2 Introduction to systems engineering (SE) Part 3 What is a systems engineer? Part 4 Important SE methods and concepts Part 5 Introduction to the systems engineering process Part 6 SE process step by step approach Part 7 Information models (IM) Part 8 SE process and IM a case study

6 Agenda 1. Kort orientering om Systems Engineering ved NTNU 2. Litt om mfaget og gfagets innhold 3. Noen tanker om hva som kan være pensum Kunnskap om disiplinen Anvendelse av prosessen Modellering et viktig redskap Supplerende disipliner Bedriftsinvolvering 4. Sluttkommentar 6

7 System theory (Blanchard) Systems theory is concerned with developing a systematic framework for describing general relationships in the natural and human-made world. The need for a general theory of systems arises of the problem of communication among the various disciplines 7

8 System versus non-system Part of a building system? Are these bricks a system? Part of a defense system? 8

9 Definition according to INCOSE System: An integrated set of elements that accomplish a defined objective. These elements include products (hardware, software, firmware), processes, people, information, techniques, facilities, services, and other support elements. 9

10 Systems engineering neer both a discipline and a process SE is the discipline that deals with the analysis and design, the operation and maintenance of large integrated systems under a total life cycle view. Technology, management, legal aspects, social and environmental issues, finance and corporate strategies are taken care of by a total system integration. SE is the process of acquiring a system for consumer use, or the process of bringing a system into being. That is the process employed in the development of systems from the point when a need is identified through production and / or construction and ultimate deployment of that system for consumer use 10

11 Systems engineering neer both a discipline and a process To viktige forutsetninger i dette faget: 1. Studenten t må ha et problem (som regel en del av forskningsoppgaven) 2. Studenten må ha et faglig ståsted; de må beherske en grunnleggende fagdisiplin som er ståstedet for arbeidet. 11

12 Definitions Systems Engineering: An interdisciplinary approach and means to enable the realization of successful systems. //en.wikipedia.org/wiki/systems_engineeringengineering Systems Engineering Process: A predefined set of activities selectively used to accomplish systems engineering tasks. 12

13 Pareto principle Percenta age Life Cycle Cost Cu umulative 100% Committed Costs 90% 80% 70% 60% 50% 40% 10% 70% 3-6X 85% X 95% X Prod/Test Phase Operations Through Disposal 30% Develop- 100% 20% Design ment Concept Phase 50% Phase 0% 8% 15% 20% Time 13 Full Program Expenditures Defense Systems Management College - 9/1993

14 Systems Engineer Systems Engineer: An engineer trained or experienced in the field of Systems Engineering. and why do we need systems engineers? ece 14

15 This seems to sum up the task of SE 7 DEG-SET A Systems Engineer is needed when the project size does not allow one person s brain-full to run it 15 [From Signs that say what you want them so say Gillian Wearing , Tate Modern Gallery. - UK passer-bys were asked to write a sign. ] UNIVERSITY OF SOUTH AUSTRALIA System Engineering & Evaluation Centre

16 DEG-SET The Knowledge and Experience Tee Diagram Breadth of Depth topics of detail 1. T diagram legend Newly graduated d Detail Engineer 3. Mature University Leader - following optimal 4. Requirement for career path experienced Systems Engineer UNIVERSITY OF SOUTH AUSTRALIA System Engineering & Evaluation Centre

17 Agenda 1. Kort orientering om Systems Engineering ved NTNU 2. Litt om mfaget og gfagets innhold 3. Noen tanker om hva som kan være pensum Kunnskap om disiplinen Anvendelse av prosessen Modellering et viktig redskap Supplerende disipliner Bedriftsinvolvering 4. Sluttkommentar 17

18 1. The concept of integrated systems 2. Systems of system 3. The top-down and bottom-up views of system 4. System boundaries 5. System decomposition 6. Life cycle perspective 7. Interacting systems 8. The systems engineering process 18

19 Integrated systems Environment- Natural Science Hardware - Technology Software - Information Science Bioware / Economics - Personnel - Financial Social Science Science Local 19 Regional Global

20 System of systems Transport Chain Transport network Railway transport Road transport Aviation transport Waterborne transport Transport system Stations Terminals Airports Harbours Trains Heavy duty vehicles Aircrafts HSLC vessels Transport subsystem Rails Roads 20

21 Top-down and bottom-up approaches Generally both top-down and bottom-up approaches are needed and used in SE. The top-down approach is primarily concerned with long-term issues that concern structure and architecture of the overall system. The bottom-up approach is concerned with making parts of the system more efficient and effective so they can be incorporated into the overall system. The top-down approach is required in planning and the system must be viewed as a whole. 21

22 System decomposition and aggregation System boundaries Topdecom -Down mposition Bou undary to env ironment Total system S-0 Interior b oundary Bottom m-up aggrega ation Sub-system S-1 Sub-system S-2 Element Element Element Element E-1.1 E-1.2 E-2.1 E O. A. Asbjornsen: Systems Engineering

23 SE process in the system life cycle 1. PROJECT PLANNING/ DESIGN Formulation of operational needs and requirements Translating requirements into performance measures 2. CONSTRUCTION/ PRODUCTION bringing the system into being Systems Engineering Process Search for solution, analyze and optimize Conceptual functional design of system and elements Detailed design of total system Testing and evaluation 3. OPERATION/ MAINTENANCE/ SUPPORT System operational phase; use, operation, maintenance, support, upgrading SYSTEM RETIREMENT/ SCRAPPING System Life Cycle System depletion phase, depletion, scrapping, demolition

24 Interacting systems The system life cycle of the ship Exhaust treatment Resource extraction Fuel production Fuel combustion Emissions 24

25 Definition of a process (ISO 9000 standard) Process: set of interrelated or interacting activities which transforms inputs to outputs. Note 1: Inputs to a process are generally output of other processes. Note 2: Processes in an organization are generally planned and carried out under controlled conditions to add value. 25

26 The systems engineering process - definitions The SE process is the iterative, but controlled, process in which system performance, functional, operational, economics, and physical needs and requirements are determined, understood and evolved through increasingly detailed levels of system requirement specification and design to an operational system 26 O. A. Asbjornsen: Systems Engineering

27 The systems engineering process, team work It needs a teamwork where the professional skills of the team members covers different disciplines i and are the platform for their participation in the process. It requires of the team members a clear understanding of the needs and requirement of the user of the system. 27

28 Systems engineering process Iterate to find feasible solutions Assess information Establish effectiveness measures Create information models Trade -off Document (requirements) 28

29 Information models based on FFBD Requirement traceability aims to show the break down of requirements from source documents to final allocation of functions to stakeholders and components Architecture aims to show how the physical components are interrelated and the arrangement of elements and subsystems Behavior aims to organize functions into processes and display all interactions, inputs and outputs in the systems and among sub- systems and components 29 Context aims to show how the system interferes with surrounding systems

30 Requirement traceability model conceptual illustration documents System frame documents Statutes, agreements System requirements Regulations System requirements Standards System requirements Agreements incorporates System functions Economic functions are allocated to System functions Organizational functions System functions Hardware functions To be further developed into behavioural model System stakeholders System components To be further developed d into Organizational units System hardware and system software architecture model 30

31 Behavioral model conceptual illustration (old) 1 The system s main process and Sub-process 1 Sub-process 2 Organizational Function 2.1 Sub-process 3 Hardware Function 3.1 Economic Function 1.1 Economic Function 1.2 Organizational Function Organizational Function 2.3 Input or output iterate Hardware Function 3.1 System boundary 31 3 and

32 System architecture model conceptual illustration incorporates System hardware All subsystems Sub-system 1 Sub-system 2 Sub-system 3 Economic systems Hardware systems System s s organization incorporates Sub-sub-system 2.1 Mechanical system 2.1 Sub-sub-system 2.2 Mechanical system 2.2 incorporates Component Component Mechanical part Mechanical part 2.1.2

33 Context model conceptual illustration Neighbor system Neighbor system 1 2 System 3 Neighbor system 33

34 Agenda 1. Kort orientering om Systems Engineering ved NTNU 2. Litt om mfaget og gfagets innhold 3. Noen tanker om hva som kan være pensum Kunnskap om disiplinen Anvendelse av prosessen Modellering et viktig redskap Supplerende disipliner Bedriftsinvolvering 4. Sluttkommentar 34

35 Erfaring fra NTNU: punktene nedenfor er meget relevante for et fag som dette. 1) Tverrfaglighet 2) Helhetlig tenking 3) Modellering 4) Yrkesforberedende 5) Livsløpsforståelse 6) Reelle problemer 7) Presentere komplekse syst. 8) Team-arbeid 35

36 Eksamen ved NTNU Doktorgradsfag 36

37 Noen lenker php/main These are examples of specific US-based top pprograms