Systems Engineering Management

1. Systems EngineeringManagement MSE607B Chapter 2, Part I The System Engineering Process

2. Learning Objectives • Identify the applications for systems engineering • Overview of the systems engineering process • Introduce the basic activities of the process • Evaluating systems in terms of their effectiveness • Material provided is a necessary prerequisite to the information presented later

3. Systems Applications • Associated with the purpose the system needs to fulfill • Often thought of as primarily at the design stage • Engineers can apply the Systems Engineering process to each phase of the life cycle • Often progresses concurrently

4. Symptoms of Poor Systems Engineering • Behind schedule • Over budget • Confusion over requirements and mission • Not achieving technical requirements • Frayed nerves

5. Pragmatic Principles • Know the problem, the customer, and the consumer • Use effectiveness criteria • Establish and manage requirements • Identify and assess alternatives • Verify and validate requirements and solution performance • Maintain integrity • Use articulated and documented process • Manage against a plan

6. Systems Engineering Benefits • Internal Benefits • Defined Process and Shared Roadmap of ‘Where we are and Where we are going’ • Realistic Project Schedules/Budgets • Higher Quality and less none-value-added rework • Shorter Time to Market • Re-use of ‘Brand Assets’ • External Benefits • Customer Satisfaction • Quality • Sales / Revenue / Market Share

7. Systems Engineering Philosophy • Focus on identifying requirements • Not technology driven • Includes: • System analysis • Decision making

8. The System Engineering Process in the Life Cycle

9. Definition of the Problem • Identification of a “want” or “desire” • Based on a real (or perceived) deficiency • Complete description of the problem • Qualitative • Quantitative • Enough detail to justify progress to next step • Nature and magnitude of the problem? • Associated risks if problem not addressed

10. System Feasibility Analysis • Identify functions the system must perform • May be various different functions • At this early stage major decisions are made relative to design approach • Important to address all possibilities • Identify possible design approaches • Evaluate the most likely candidates • Performance • Effectiveness • Logistics • Recommend a preferred approach

11. System Operational Requirements • The consumer needs relative to utilization and mission accomplishment • Operational distribution or deployment • Mission profile or scenario • Performance and related parameters • Utilization requirements • Effectiveness requirements • Operational life cycle (horizon) • Environment

12. Maintenance and Support Concept • Must be considered early • Level of maintenance • Repair policies • Organizational responsibilities • Maintenance support elements • Effectiveness requirements • Environment • Basis for establishing supportability in system design • Basis for detailed maintenance plan

13. Identification/Prioritization of Technical Performance Measures (TPMs) • Review in terms of relative degrees of importance • Criticality of accomplishing the desired mission(s) • Priorities in design when trade-offs are necessary • Express objectives in quantitative terms • “measurable” goals • Must reflect customer’s/consumer’s requirements

14. Functional Analysis • Specify the “What” not the “How” • What needs to be accomplished • Baseline for many activities conducted subsequently • Specific action to achieve a given objective • What system must perform • Maintenance action to restore system into use • Breakdown from system level to subsystem

15. Functional Approach • Ensures the following: • All facets of system design and development, production, operation, support, and retirement are covered • All system elements recognized and defined • Means provided for relating system packaging concepts and support requirements • Established proper activity sequence and design relationships

16. Requirements Allocation • Defines specific input design criteria for the overall system: • Various subsystems • Lower-level components • Top-down system level analysis • “Design to” requirements • Must support the specified system requirements

17. System Synthesis, Analysis, and Design Optimization • Combining and structuring of components • Represent a feasible system configuration • Synthesis is design • Initially to develop preliminary concepts to establish basic relationships among system components • Later to further define the “HOWS” in response to “WHAT” requirements • Leads to definition of possible design approaches

18. 10 System Synthesis Steps • Definition of analysis goals • Selection and weighing of evaluation parameters • Identification of data needs • Identification of evaluation techniques • Selection and/or development of a model • Generation of data and model application • Evaluation of design alternatives • Accomplishment of a sensitivity analysis • Identification of risk and uncertainty • Recommendation of preferred approach

19. Design Integration • Commence during early conceptual design stages • Extend through system life cycle • Design team formed when requirements established • Specialists added as development progresses • Role during latter phases in form of • Evaluation/validation • Design changes

20. Stages Of System Evaluation During The Life Cycle

21. System Test and Evaluation (Validation) • Verify compliance to Technical Performance Measures (TPM) • Acquire a high degree of confidence as early in the life cycle as possible • Involve a physical replica of the system • Laboratory and field testing • Simulation, CAD, CAM • Various stages of system evaluation during the life cycle

22. Sample Test Program • Environmental Qualification • Reliability qualification • Maintainability demonstration • Support equipment compatibility • Technical data verification • Personnel test and evaluation • Software compatibility

23. Production and/or Construction • Construction • One of a kind system (shuttle, satellite) • Production • Multiple quantities

24. System Operational Use and Life-cycle Support • Sustaining maintenance and support • Incorporating new technologies and modifications for improvement • Assessment to ensure system performs as desired • Data collection, analysis and feedback into the design process

25. System Retirement and Material Disposal • Phase out of inventory • Replace obsolete components • Incorporate new technologies • Effect of disposal on environment • Design for disposability/environment

26. Questions? Comments?