系統工程管理

1. 系統工程管理

2. Outline • System Definition • What is Systems Engineering? • System Engineering Process

3. System Definition • An integrated set of equipment, computer program, facilities, human and logistical support resources, and procedures which are assembled to accomplish a single purpose or mission. (NSA/CSS) • A system is a construct or collection of different elements that together produce results not obtainable by elements alone. (NASA) • A complete solution to a defined need(s) in its full environment over a prescribed lifetime. (Northrop Grumman) Hardware Software Technical Data Equipment Facilities Personnel

4. Space System Mission Operations Subject Space Mission Concept Space Segment (P/L+S/C) Ground Segment Launch Segment Orbit and Constellation Command Control & Communications Architecture

5. System Definition • What is Systems Engineering? • System Engineering Process

6. What is the Systems Engineering ? (I) The Orchestra Needs a Conductor and ...

7. What is the Systems Engineering ? (II) • Systems engineering is the art and science of developing an operable system capable of meeting requirements within often opposed constraints. • Systems engineering is a holistic, integrative discipline to produce a coherent whole that is not dominated by the perspective off a single discipline.

8. Systems Engineering (Basic Concept) Mission (A Large Problem) SYSTEMS ENGINEERING PROCESS (TO BE DECOMPOSED INTO AN INTEGRATED SET OF SMALL PROBLEMS) #1 #2 #3 #N TO BE SOLVED & EFFECTIVELY MANAGED TO PRODUCE AN OPTIMIZED SOLUTION

9. Relationships between System Engineering and Project Control PROJECT MANAGEMENT • SYSTEMS EMGINEERING • Requirement Definition • Requirement Definition • Technical Solution Definition • Product Realization • Design Realization • Evaluation • Product Transition • Technical Management • Technical Planning • Technical Control • Technical Assessment • Technical Decision Analysis • PROJECT CONTROL • Management Planning • Integrated Assessment • Schedule Management • Cost Management • Resource Management • Acquisition management • Planning • Risk Management • Configuration Management • Data Management • Assessment • Decision Analysis

10. Project Life-Cycle Phases (NASA) Phase Pre-Phase A : Concept Studies Phase A : Concept & Technology Development Phase B : Preliminary Design & Technology Completion Phase C : Final Design & Fabrication Phase E : Operation & Sustainment Phase F : Closeout Phase D : System Assembly Integration & Test Launch Configuration Product Baseline Feasible Concept Top-Level Architecture Functional Baseline As-Deployed Baseline Allocated Baseline Output System Concepts Definition in the form of Simulations, Analysis, Engineering Models, Mockups, Trade Study Definition End Products in the form of Mockups, Trade Study Results, Specifications, Interface Documents, and Prototypes End Products Detailed Designs, End Product, Component Fabrication, And Software Development Feasible System Concepts in the form of Simulations, Analysis, Study Reports, Models, and Mockups Operations- Ready System End Product With Supporting Related Enabling Products Desired System Product Closeout

11. System Definition • What is Systems Engineering? • System Engineering Process

12. Systems Engineering Engine Realized Products to Level Above Requirements Flow Down From Level Above TECHNICAL MANAGEMENT PROCESS PRODUCT REALIZATION PROCESS SYSTEM DESIGN PROCESS Technical Planning Processes 10. Technical Planning • Requirements Definition • Processes • Stakeholder Expectations • Definition • 2. Technical Requirements • Definition Technical Control Processes 11. Requirements Management 12. Interface Management 13. Technical Risk Management 14. Configuration Management 15. Technical Data Management Production Transition Processes 9. Product Transition Evaluation Processes 7. Product Verification 8. Product Validation Technical Solution Definition Processes 3. Logical Decomposition 4. Design Solution Definition Technical Assessment Processes 16. Technical Assessment Design Realization Processes 5. Product Implementation 6. Product Integration Technical Decision Analysis Processes 17. Decision Analysis Requirements Flow Down to Level Below Realized Products From Level Above

13. Interrelationships among the Systems Design Processes Trade Studies and IterativeDesignLoop Stakeholder Expectations High-Level Requirements Mission Objectives & Constraints Mission Authority Start Design and Product Breakdown Structure Functional and Logical Decomposition High-Level Requirements Operational Objectives ConOps Mission Success Criteria Sufficient Depth No Functional & Performance Analysis No Yes Yes Baseline Requirements ? Select Baseline Work ? Safe & Reliable ? Affordable ? Yes No Logical Decomposition Stakeholder Expectation Definition Technical Requirement Definition Design Solution Definition Decision Analysis

14. Purpose of Stakeholder Expectations Definition Process • The main purpose is to identify who the stakeholders are and how they intend to use the product. • The early task is to understand the objectives of the mission. Mission Authority Mission Objectives Operational Objectives Success Criteria Design Drivers Operation Driver • Integration and test • Transportation • Science data distribution • …... • Agency strategic plans • Announcements of opportunity • Road maps • Science • Technology demonstration • Technology development • Programmatic • Operation duration • Environment • …. • What measurements ? • How well ?

15. Stakeholder Expectations Definition Process Establish List ofStakeholders Validated Stakeholder Expectations Elicit Stakeholders Expectations Initial Customer Expectations Establish Operations Concept and Support Strategies Concept of Operations Other Stakeholder Expectations Define Stakeholder Expectations in Acceptable Statements Analyze Expectation Statements For Measures of Effectiveness Enabling Product Support Strategies Validate That Defined Expectation Statements Reflect Bidirectional Traceability Obtain Stakeholder Commitments to the Validated Set of Expectations Customer Flowdown Requirements Measure of Effectiveness Baseline Stakeholder Expectations

16. Operation Architecture

17. Technical Requirements Definition Process Analyze Scope of Problem Validated Technical Requirements Baselined Stakeholder Expectations Define Functional and Behavioral Expectation in Technical Terms Define Design and Product Constraints Define Performance Requirements for Each Defined Functional and Behavior Expectation Measures of Performance Baselined Concept Of Operations Define Technical Requirements in Acceptable “Shall” Statements Baselined Enabling Supports Strategies Technical Performance Measures Validate Technical Requirements Define Measure of Performance for Each Measure of Effectiveness Measures of Effectiveness Define Technical Performance Measures Establish Technical Requirements Baseline

18. Characteristics of Requirements Technical Requirements – Allocation Hierarchically to PBS Functional Requirements Performance Requirements Interface Requirements Operational Requirements – Drive functional Requirements Mission Timeline Sequence Mission Configurations Common and Telemetry Strategy Reliability Requirements – Project Standards – Levied Across Systems Mission Timeline Sequence Mission Configurations Common and Telemetry Strategy Safety Requirements – Project Standards – Levied Across Systems Toxic Substances Pressurized Vessels Radio Frequency Energy Specialty Requirements – Project Standards – Drive Product Design Producibility Maintainability Asset Protection

19. Flowdown Requirements Mission Objectives Mission Requirements NEEDS • Cost • Schedule • Constraints System Functional Requirements Assumption Environmental and other Design Requirements SYSTEM System Performance Requirements SUBSYSTEM Subsystem A Subsystem B Subsystem C Subsystem D … Allocated Requirements Derived Requirements Allocated Requirements Allocated Requirements

20. Logical Decomposition Process Define One or More Logical Decomposition models Validated Technical Requirements Baselined Technical Requirements Allocate Technical Requirements to Logical Decomposition Models to Form A Set of Derived Technical Requirements Logical Decomposition models Resolve Derived Technical Requirements Conflicts Measures of Performance Validate the Resulting Set of Derived Technical Requirements Logical Decomposition Wok Products Establish the Derived Technical Requirements Baseline

21. Product Breakdown Structure Spacecraft System System Subsystem Structure and Mechanism Attitude Determination & Control Command & Data Handling Telemetry Tracking & Comm. Thermal Control Reaction Control Energy Power Component • Gyros • Star Tracker • Momentum • Wheels • Magnetic • Torquers • Control • Electronics • Thruster • Tanks • Valves • Antennas • Receivers • Multiplexers • GPS Receiver • TWTAs • On Board • Computer • Solid State • Recorder • Remote I/O • Units • Radiator • Heat Pipe • Heater • MLI (multi-layer insulator) • Solar Arrays • Battery • Regulator • Power Control • Structure • Element • Deploy • Mechanism • Solar Panel Traveling-wave tube

22. Functional Breakdown Block Diagram

23. N2 Chart M, SS M M, E, SS M, E, SS M, E, SS A B C D E F G M : Mechanical E : Electrical SS : Supplied Services : Interface

24. Design Solution Definition Process System Specified Requirements Define Alternative Design Solution Analyze Each Alternative Design Solution Baselined Logical Decomposition models End Product- Specified Requirements Establish Operations Concept and Support Strategies Subsystem Specification Select Best Design Solution Alternative Baselined Derived Technical Requirements General Full Design Description of the Selected Solution Enabling Products Requirements Baseline Design Solution Specified Requirements and Design Description Yes Enabling Product Exist Need lower Level Product? No Product Verification and Validation Plan No Yes Initiate Development of Enabling Products Initiate Development of Next lower level Products

25. System Level Trades and Baseline GROUND PAYLOAD ORBIT TT&C Low Inclination Mission VIS + NIR TDRS Existing X X IR Sensor Sun-Synch Receiving Station SAR h=564 km h=891 km New NCU HSI i=97.650 i=98.990 Upgrade RGS COM ARCH LAUNCHER S/C STABILIZ. Imaging Data MISSION OPS Athena II X X X-Band X S-Band X Three- axis Muti-Mission Operations Taurus-XL TT&C Spin(or Dual Spin) Single Mission Operations Rocket X-Band S-Band Gravity Gradient Athena I Science Data S-Band X-Band :Baseline : Alternatives

26. Requirements Verification Matrix

27. Product Realization Design Realization Evaluation Processes Product Transition Process • Delivery to Next Higher Level in PBS • Delivery to Operational System • Assembly • Functional • Evaluation • Functional • Environmental • Operational • Testing in • Integration & • Test Environment • Operational • Testing in • Mission • Environment • Acquire • Make/Code • Reuse

28. Product Implementation Process Required Raw Materials Prepare to Conduct Implementation Desired End Product If Implementation by Reuse : Participate in Acquiring the Reuse End Product If Implementation by Making : Evaluate Readiness Of Product Implementation Enabling Products If Implementation by Buying : Participate in Purchase of Specified end Product End Product Design Specifications Subsystem Specification Configuration Documentation Make the Specified End Product Product Implementation Work Products Prepare Appropriate Product Support Documentation Enabling Product Prepare Appropriate Product Support Documentation Capture Product Implementation Work Products

29. Product Integration Process Prepare to Conduct Product integration Lower Level Products to be Integrated Desired Product Obtain Lower Level Products for Assembly and Integration End Product Design Specifications Confirm That Received Products Have Been Validated Product Documents and Manuals Prepare the Integration Environment for Assembly and Integration Configuration Documentation Assemble and Integrate the Received Products into the Desired End Products Product Integration Work Products Prepare Appropriate Product Support Documentation Enabling Product Prepare Appropriate Product Support Documentation Capture Product Integration Work Products

30. Spacecraft Configuration Propulsion Module SSR Fixed panel Solar Array Connector TRSPs IPUs GPS Rcvrs BASS & radiator GPS antenna (x2) MTQs (x3) Rwheels (x4) DRU Solar Side Ombilical IF W/ launcher Battery MAGs (x2) S-Band antenna (x2) Thermal Doubler OBMU TMI Wall

31. Product Verification Process Prepare to Conduct Product Verification Verified End Product End Product To Be Verified Perform the Product Verification Specified Requirements Baseline Product Verification Results Analyze the Outcomes of the product Verification Product Verification Report Product Verification Plan Prepare a Product Verification Report Product Verification Work Products Enabling Product Prepare Appropriate Product Support Documentation Capture Work Products from Products Verification

32. Requirement Allocation, Integration, and Verification Process Mission/System Requirements Test System Verification System Segment Requirements Test System Segments Test Subsystems Subsystem Requirements Unit Requirements Test Units Allocation Integration Design and Build Units

33. Types of Verification • Analysis • The use of mathematical modeling and analytical techniques to predict the suitability of a design. • Demonstration • Showing that the use of an product achieves the individual specified requirement. • Inspection • The visual examination of a realized end product. • Test • The use of an end product to obtain detailed data needed to verify performance, or provide sufficient information to verify performance through further analysis.

34. Products Forms of Verification • Simulated (algorithmic models, virtual reality simulator). • Mockup (plywood, brass board, breadboard) • Concept description (paper report); • Prototype (product with partial functionality); • Engineering unit (fully functional but may not be same form/fit); • Design verification test units (form, fit, and function is the same, but they may not have flight parts); • Qualification units (identical to flight units but may be subjected to extreme environments) • Flight units (end product that is flown, including proto-flight units).

35. Environmental Tests

36. Product Validation Process Prepare to Conduct Product Validation Validated End Product End Product To Be Validated Perform the Product Validation Stakeholder Expectation Baseline Product Validation Results Analyze the Outcomes of the product Validation Product Validation Report Product Validation Plan Prepare a Product Validation Report Product Validation Work Products Enabling Product Prepare Appropriate Product Support Documentation Capture Work Products from Products Validation

37. Product Transition Process Prepare to Conduct Product Transition Delivered End Product with Applicable documentation End Product To Be Transitioned Evaluate the End Product, Personnel, and Enabling Product Readiness for Product Transition Product Transition Work Products Prepare the End Product for Transition Documentation To Accompany The Delivered End Product Transition the End Product to be the Customer with Required Documentation Based on the Type of Transition Required Realized Enabling Products Enabling Product Prepare Sites, as Required, where the End Product Will Be Stored, Assembled, Integrated, Installed, Used, and/or Maintained Capture Product Implementation Work Products

38. Thanks for your Attention…