Session 4. System Engineering Management. Session Speaker : Dr. Govind R. Kadambi. M S Ramaiah School of Advanced Studies 1

Transcription

1 Session 4 System Engineering Management Session Speaker : Dr. Govind R. Kadambi M S Ramaiah School of Advanced Studies 1

2 Session Objectives To learn and understand the tasks involved in system engineering management To learn and understand the various stages of planning and control in project management To understand the risks involved in the different stages of the project To learn the system organization and system engineering standards M S Ramaiah School of Advanced Studies 2

3 Session Topics Managing System Development and Risks Work Breakdown Structure (WBS) System Engineering Management Plan (SEMP) Risk Management Organization of System Engineering M S Ramaiah School of Advanced Studies 3

4 Managing System Development and Risks System engineering is the integral part of the management of the system development project Principal constituents are System Engineering Project Planning and Control Technical guidance being the province of the system engineering Program, financial, contract guidance are the province of the project planning and control Resource allocation and definition of task are necessarily shared functions M S Ramaiah School of Advanced Studies 4

5 System Engineering As a Part of Project Management M S Ramaiah School of Advanced Studies 5

6 Work Breakdown Structure (WBS) WBS is a systematic organization of project tasks Ensures all the essential tasks are defined properly, assigned, scheduled and controlled WBS is also called as project or system breakdown structure Defines all the project tasks to accomplish in hierarchical structure WBS formulation begins in concept definition phase to serve as point of reference for concept trade-off studies Fully articulated to serve as basis for system life cycle M S Ramaiah School of Advanced Studies 6

7 Work Breakdown Structure (WBS) WBS is often a contractual requirement in competitive system developments Typically defines the whole system to be Developed Produced Tested Deployed Supported Hardware Software Services Data Defines a skeleton or framework on which the project is to be implemented M S Ramaiah School of Advanced Studies 7

8 Elements of a Typical WBS Format is generally tailored to the specific project in hand Always follows a hierarchical tree structure designed to ensure a specific place for every significant portion of work under the project With system project at Level 1(or 0) in the hierarchy, the Level 2 categories broken down as System Product System Support System Testing Project Management Systems Engineering M S Ramaiah School of Advanced Studies 8

9 System Product WBS M S Ramaiah School of Advanced Studies 9

10 WBS System Product Total effort required to develop, produce and integrate the system itself together with any auxiliary equipment required for its operation Level 3 entries are seen to be the several subsystem as well as the equipment used by more than one subsystem and other auxiliary required for more than one subsystem Levels 4 and 5 breakdown one of the subsystems into its constituent components, which represent definable products of development engineering and production effort Cost allocation and work packages that define the several steps of component s design, development and test M S Ramaiah School of Advanced Studies 10

11 WBS System Support System support provides equipment, facilities and services necessary for the development and operation of the system product The item can be categorized under six heading Supply support Test equipment Transport and handling Documentation Facilities Personnel and Training Each category applies for both the development process and system operation M S Ramaiah School of Advanced Studies 11

12 WBS System Level Test System testing begins after design of the individual components have been validated via components tests Very significant fraction of the total test effort is allocated to system-level testing, which involves Integration testing, which supports the step-wise integration of components and subsystems to achieve a total system System testing, which provides for overall system tests and the evaluation of test results Acceptance testing, which provides for factory and installation tests of delivered systems Operational testing and evaluation, which tests the effectiveness of the entire system in a realistic operational environment Individual tests performed at each level are prescribed in a series of separate test plans and procedures M S Ramaiah School of Advanced Studies 12

13 WBS Project Management Project management includes all activities associated with Project Planning and Control Management of WBS Costing Scheduling Performance Measurement Project Reviews Reports M S Ramaiah School of Advanced Studies 13

14 WBS System Engineering Activities of the system engineering staff in guiding the engineering of the system through all its conceptual and engineering phases Activities such as Requirement analysis Trade-off studies Test requirement and evaluations System design requirements Configuration management Concurrent Engineering: Integration of specialty engineering into the early phases of the engineering effort is also included M S Ramaiah School of Advanced Studies 14

15 Cost Control and Estimating WBS is the heart of the project cost control and estimating system At the beginning of the project, the target cost is distributed among the identified work packages and is partitioned downward as lower-level packages are defined Project cost control is then exercised by comparing actual reported costs against estimated costs Work packages deviate seriously from initial estimates are identified and focused M S Ramaiah School of Advanced Studies 15

16 Cost Control and Estimating For new components, cost estimates must be developed by adapting the previously experienced cost of items For higher levels departures from one system to the next become too large to reliably use data derived from previous experience without major correction Should not be expected that the lowest indenture level would be uniform throughout the various subsystems and their components M S Ramaiah School of Advanced Studies 16

17 Cost Control and Estimating In general the program including costing is exercised with availability of Detailed specifications Interface definitions Work assignments Contract between the project and the organization Development Engineering Fabrications M S Ramaiah School of Advanced Studies 17

18 Critical Path Method (CPM) CPM is project management tool that traces each major element of the system back through the engineering of its constituent parts Estimations are made out of size and duration of effort required for each step Particular path estimated to require the longest time to complete its constituent steps is called the critical path Difference between this time and times required for other paths is called slack for those paths Resulting critical path network is direct application of the WBS M S Ramaiah School of Advanced Studies 18

19 System Engineering Management Plan (SEMP) SEMP is Specialized documented plan required to control system interfaces Interfacing responsibilities and the authorities within the project must be defined and controlled Primary responsibility of the plan is to guide the engineering effort of the system engineering component of project management Most important function of SEMP is to ensure all of the many active participants (subsystem managers, component design engineers, test engineers, system analysts, specialty engineers and subcontractors) know their responsibilities to one another M S Ramaiah School of Advanced Studies 19

20 SEMP SEMP is exact analogues of the component interface function of system engineering defining the interactions among all parts of the system to fit together and operate smoothly Serves as a reference for the procedures that are followed in carrying out the numerous system engineering tasks Indented to be a living document, starting as an outline and being elaborated/updated as the system development process goes on Formal SEMP also provides a control instrument for comparing the planned with those accomplished M S Ramaiah School of Advanced Studies 20

21 Elements of Typical SEMP SEMP contains detailed statement of how system engineering functions carried in course of system development It consists of three types of activity Development Program Planning and Control System Engineering Process Engineering Specialty Integration M S Ramaiah School of Advanced Studies 21

22 SEMP in Program Management Plan M S Ramaiah School of Advanced Studies 22

23 Development of Program Planning and Control Describes the system engineering tasks that must be implemented in managing the development program including Statements of work Organization Scheduling Technical Performance Measurement Risk Management M S Ramaiah School of Advanced Studies 23

24 System Engineering Process Describes the system engineering process as it applies to the development of the system including Operational requirements Functional analysis System analysis and trade-off strategy System test and evaluation strategy M S Ramaiah School of Advanced Studies 24

25 Engineering Specialty Integration Describes how the areas of specialty engineering are to be integrated into the primary system design and development including Reliability, maintainability and availability (RMA) engineering Producibility engineering Safety engineering Human factors engineering M S Ramaiah School of Advanced Studies 25

26 Risk Management Unpredictable outcomes encountered pose risks of Performance shortfalls Environment susceptibility Unsuitability for production Host of other unacceptable consequences May require a change in course with impacts on program cost and schedule Greatest challenge of system engineering is to steer a course that poses minimum risks while still achieving maximum results Methodology employed to identify and minimize risk in system development is called risk management M S Ramaiah School of Advanced Studies 26

27 Risk Management At the outset, questions should raise like Are the perceived operational requirements realistic? Will they remain valid throughout the new system s operational life? Will the resources required to develop and produce the system be available when needed? Will the advanced technology be necessary to achieve the required operational goal perform as expected? Will the anticipated advances in production automation materialize? Will the development organization be free from work stoppages? Special task of system engineering to be aware of such possibilities and guide to minimize the impact when they occur. M S Ramaiah School of Advanced Studies 27

28 Risk Reduction Through the Systems Life Cycle Reducing program risks is a continual process throughout the life cycle Need analysis phase reduces the risk of embarking on the development of a system that does not address vital operational needs Concept exploration phase reduces the risk of deriving irrelevant or unrealistic system performance requirements System definition phase selects a system concept that utilizes technical approaches that are neither excessively immature nor unaffordable, but rather one that has the best chance of meeting all system goals M S Ramaiah School of Advanced Studies 28

29 Program Risk and Effort Throughput Program risk of a hypothetical system decreases as the development progresses through the phases of the life cycle Descending curve conveys the fact that as the development progresses, uncertainties constitute risks of unforeseen adverse events are systematically eliminated or reduced by analysis, experiment, test or change in course. M S Ramaiah School of Advanced Studies 29

30 Program Risk and Effort Throughput Variant of the curve is referred to as the risk mitigation waterfall Ascending effort curve represents the stepwise increases in the costs of succeeding phase of the system development, showing the progression of activity from conceptual to engineering to integration and evaluation M S Ramaiah School of Advanced Studies 30

31 Key Principles As the development progresses, the investment in program effort typically rises steeply To maintain program support, the risk of failure must be correspondingly reduced so as to maintain the financial risk at reasonable levels Initial stages in the program produce major reductions in risk, when the basic decisions are made regarding the system requirements and the system concept Demonstrates the importance of investing adequate effort in the formative phases Two phases that typically produce the greatest risk reduction are concept exploration and advanced development M S Ramaiah School of Advanced Studies 31

32 Key Principles Concept exploration provides a solid conceptual basis for the system approach and architecture. Advanced development matures new advanced technologies to ensure their meeting performance goals By the time the development is complete and the system is ready for production and distribution the residual level of risk must be extremely low if the system is to be successful M S Ramaiah School of Advanced Studies 32

33 Example of Risk Mitigation Waterfall Chart M S Ramaiah School of Advanced Studies 33

34 Component of Risk Management Risk management is formally recognized as systems engineering standards Each program is expected to prepare a risk management plan DoD expects risk management for a major system have its own Organization Staffing Database Reporting Independent review Extend to all phase of program development Production Operation Support M S Ramaiah School of Advanced Studies 34

35 Risk Assessment General process of risk assessment is inherent in all decisions involving prospective uncertainty Used to eliminate alternative concepts that are overly dependent Immature technologies Unproven technical approaches Other ambitious advances that do not appear to be warranted by their projected benefits Useful approach to identify and characterize the proposed design features that represent a sufficient development risk Significant program impact to warrant analysis and if necessary development and test M S Ramaiah School of Advanced Studies 35

36 Risk Assessment Identifies the weakest and most uncertain features of the design Focuses attention on means for eliminating the possibility features which has complications and require design changes during the subsequent phases of development Take action to reduce their potential danger to the program to an acceptable level Two important risk components are Risk likelihood Risk impact or Risk criticality M S Ramaiah School of Advanced Studies 36

37 Risk Likelihood Risk Likelihood High Medium Low Design Status Significant extension from past designs Multiple new and untried component Complex components and / or interfaces Marginal analytical tools and data Moderate extension from past designs Components complex but not highly stressed Analytical tools available Application of qualified components Components of medium complexity Mature technologies and tools M S Ramaiah School of Advanced Studies 37

38 Risk Criticality Criticality System Impact Program Impact High Medium Low Major degradation in performance (50-90%) Serious safety problem Significant degradation in performance (10-50%) Short losses of operability Costly operational support Minor degradation in performance (<10%) Occasional brief delays Increased maintenance Major increase in cost and/or schedule (30-70%) Production cutbacks Significant increase in cost and/or schedule (10-30%) Intense reviews, oversight Production delays Minor increase in cost and/or schedule (<10%) Vigorous reviews, oversight M S Ramaiah School of Advanced Studies 38

39 Role of System Engineering Risk assessment is clearly the responsibility of system engineering Judgments that are involved require a breadth of knowledge of system characteristics For constituent technologies beyond that possessed by design specialists, judgments of risk criticality are at system and program level Process of risk assessment helps system engineer to identify the system failures that need to be most thoroughly understood and raised to a level of design maturity suitable for full-scale engineering M S Ramaiah School of Advanced Studies 39

40 Risk Mitigation Common method of dealing with the identified programs are Intensified technical and management reviews of the engineering process Special oversight of designated component engineering Special analysis and testing of critical design items Rapid prototyping and test feedback Consideration of relieving critical design requirements Initiation of fallback parallel developments M S Ramaiah School of Advanced Studies 40

41 Organization of Systems Engineering Virtually all system engineering projects are managed by a single industrial company Organizational structure of the prime contractor is usually some form of a matrix organization Most of the engineering staff are organized in discipline-or technology oriented groups in a matrix organization Major projects are managed by project management teams reporting to a vice president for project management or equivalent Technical staff assigned to individual projects as required, but employees retain affiliation with their engineering groups M S Ramaiah School of Advanced Studies 41

42 System Analysis Staff Any system engineering organization is highly competent and experienced analytical staff Staff need not be single entity nor does it need to be organizationally co-located with the project staff itself Must be part of the system engineering organization during conceptual and early engineering phases of the project Must have deep understanding of the system environment, with respect to both its operational and physical characteristics Able to model system environment by mathematical or computer models to provide basis for analyzing the effectiveness of system models M S Ramaiah School of Advanced Studies 42

43 System Analysis Staff In concept exploration phase, the system analysis staff is the source of much of the quantitative data involved in defining the system performance required to meet its operational requirements In concept definition phase, the analysis staff is responsible for constructing the system simulations used in the trade-off studies and the selection of the best system concept System analysis staff must be skilled in mathematical modeling, software design and other specialized techniques M S Ramaiah School of Advanced Studies 43

44 System Design Team Leadership and coordination in any large program requires one or more teams of key individuals working closely together System Engineer Team Leader Lead Engineers for major subsystems Software Systems Engineering Support Engineering (Logistics) Test Engineering User Representatives Specialty and Concurrent Engineering Members (as appropriate) M S Ramaiah School of Advanced Studies 44

45 System Engineering Capability Maturity Assessment Similar approach to software capability assessment methodology System Engineering by Electronics Industries Association (EIA) issued as an interim standard EIA/IS 731 in 1999 Merged prior efforts by INCOSE with other model developed by the system engineering community M S Ramaiah School of Advanced Studies 45

46 Capability Maturity Model Integration (CMMI) CMMI is a standard bridging software and system engineering Objective is to replace both CMM and EIA 731 with unified methodology It consists of two model representations CMM EIA 731 Both the models have common and individual representations M S Ramaiah School of Advanced Studies 46

47 CMMI Process Areas The 24 CMMI Pas can be grouped under four categories as listed Process Management Category Organization process focus Organizational process definition Organizational training Organizational process performance Organizational innovation and deployment Engineering Category Requirements management Requirements development Technical solution M S Ramaiah School of Advanced Studies 47

48 CMMI Process Areas Provide integration Verification Validation Project Management Category Project planning Project monitoring and control Supplier agreement management Integrated project management Risk management Quantitative Project management Support Category Configuration management Process & product quality assurance Measurement and analysis Decision analysis and resolution Causal analysis and resolution M S Ramaiah School of Advanced Studies 48

49 System Engineering Standards System Engineering became widely recognized as an essential field of concentration Efforts to define its governing principles and practices In 1990s DoD adopted industrial professional organizations EIA Interim Standard EIA/IS 632 patterned after DoD 499B Recently the Interim Standard was revised and official standard EIA 632 departs significantly from its predecessors M S Ramaiah School of Advanced Studies 49

50 ISO/IEC International Organization for Standardization (ISO) and International Electrotechnical Commission (IEC) developed new system engineering standard ISO/IEC Standard defines the system broadly than its predecessors Major emphasis on the enterprise view of the system Expected that ISO/IEC will used as a common definition of system engineering methodology M S Ramaiah School of Advanced Studies 50

51 Session Summary System Engineering is a part of project management Provides technical guidelines to system integration and technical coordination Contributes to resource allocation, task definition and customer interaction WBS is hierarchical task organization which subdivides total effort into successively smaller work elements WBS provides basis for scheduling, costing and monitoring Critical path method (CPM) is based on WBS CPM creates a network of sequential activities and identifies path that take the longest to complete M S Ramaiah School of Advanced Studies 51

52 Session Summary System Engineering Management Plan (SEMP) is the plan implementation of all system engineering tasks SEMP defines roles and responsibilities of all participants Risk management is major challenge to system engineering Reducing program risk is a continual process throughout the life cycle Risk must reduce as program investment rises Large program requires formal system design teams CMMI extends methodology, applies for software and system engineering, adopted by government and defense programs ISO/IEC emphasizes broad enterprise view of system M S Ramaiah School of Advanced Studies 52