Evolutionary Acquisition (EA) Spiral Development (SD) Systems Engineering Methodology

1. Evolutionary Acquisition (EA) Spiral Development (SD) Systems Engineering Methodology NDIA SED Conference 20 October 2003 Richard (Dick) Engwall RLEngwall & Associates

2. Industry Recommended DoD IPPD Process IPPD Maturity Model and Self-Assessment Criteria Exit Criteria Entrance Criteria • Generic Technologies Ready • for Integration into New • Production Application • - ATD product isoperationally • suitable for use as fieldable • prototype • - ATD product to be manufactured • with production equipment, tooling • and processes and tested in • real and simulated operational • environments • Product/Process Capabilities • Defined • - Producibility Goals • - Life Cycle Cost • - Reliability & Maintainability • - Supportability • Materials Characterized • Alternative Product/Process • Design Tradeoffs Conducted, • Evaluated and Prioritized • Customer(s) Requirements • - Multi-use • - Dual-use • - Top level • State-of-the-Art Technology • Assessment • - Sub-systems • - Components • - Materials • - Processes • Identify High Risk and/or • Payoff Technologies Needed • Establish Metrics of Success Advanced Development (6.3a/b) Define Gated Process (Methodology) Steps Needs to be Tailored to System Application Based on Business, Induatry, and Technology Risk Scenario • IPPD Management System • IPPD Process Methodology • IPPD Teams • IPPD Tools • Modeling & Simulation • Common Operating Digital Environment t 20Oct03 NDIA SED S3T2 RLEngwall

3. Evolution of MIL STD 499B to ANSI/EIA 632 20Oct03 NDIA SED S3T2 RLEngwall

4. The Systems Engineering Building Block Concept 20Oct03 NDIA SED S3T2 RLEngwall

5. The System Engineering Development Building Block Layers Concept 20Oct03 NDIA SED S3T2 RLEngwall

6. Sample Layered Development System Structure 20Oct03 NDIA SED S3T2 RLEngwall

7. ANSI/EIA-632 Process Requirements for Engineering a System 20Oct03 NDIA SED S3T2 RLEngwall

8. Application Guidelines of ANSI/EIA-632 (What not How Oriented) • Decide Which of the 33 Processes Apply • Decide Which Requirements Apply for the Processes Selected • Establish Appropriate Policies & Procedures • Define Appropriate Tasks for Each of the Selected Requirements 20Oct03 NDIA SED S3T2 RLEngwall

9. Application Guidelines of ANSI/EIA-632 (What not How Oriented) Continued • Establish Methods and Tools to Support Task Implementation • Representative Tasks Along With Their Expected Outcomes Are Provided in Annex C • Appropriate Processes Are Applied Recursively and Iteratively • Many Associate Tasks Are Concurrent And Highly Iterative And Have Interactive Dependencies That Lead To Alteration Of Previously Established Technical Requirements 20Oct03 NDIA SED S3T2 RLEngwall

10. The ‘Newer’ 5000 MODEL User Needs & Technology Opportunities • Process entry at Milestones A, B, or C • Entrance criteria met before entering phase • Evolutionary Acquisition or Single Step to Full Capability (Program A B C FOC IOC Initiation) Concept & Technology Development System Development & Demonstration Production & Deployment Operations & Support Critical Design Review FRP Decision Review Concept Exploration Technology Development LRIP/OT&E Pre-Systems Acquisition Systems Acquisition Sustainment New 20Oct03 NDIA SED S3T2 RLEngwall

11. Interdependency of DoD 5000 and ANSI/EIA 632 Processes 20Oct03 NDIA SED S3T2 RLEngwall

12. Concept & Technology DevelopmentPhase A Technology Development Concept Exploration Concept Exploration Technology Development Enter:Validated & approved ICD • Activity:Paper studies of alternative solutions to the initial concept Exit:MDA selects preferred solution to be pursued Enter:Project leader understands solution as part of the integrated architecture and its DOTMLPF implications. • Activity:Technology development demonstrations Exit: Affordable increment of military-useful capability identified and demonstrated in relevant environment – normally can be developed for production within 5 years 20Oct03 NDIA SED S3T2 RLEngwall

13. System Development & DemonstrationPhase B System Integration System Demonstration Critical Design Review System Integration System Demonstration Enter:PM has technical solution but has not integrated subsystems into complete system • Activities:System Integration of demonstrated subsystems and components. Reduction of integration risk. Exit: Demonstration of prototypes in relevant environment Enter:Prototypes demonstrated in intended environment • Activities:Complete development. DT/OT/LFT&E Exit:System demonstration in intended environment using engineering development models; meets validated requirements 20Oct03 NDIA SED S3T2 RLEngwall

14. Production & DeploymentPhase C Full-Rate Production & Deployment LRIP FRP Decision Review LRIP Full-Rate Production & Deployment Enter:System matured for production • Activities:Low-rate initial production. IOT&E, LFT&E of production-representative articles. Establish full manufacturing capability. Exit:System operationally effective, suitable and ready for full rate production Enter:Beyond LRIP (ACAT I) and LFT&E reports (covered systems) submitted to Congress • Activities:Full rate production. Deploy system. Start support. Exit:Full operational capability; deployment compete 20Oct03 NDIA SED S3T2 RLEngwall

15. Operations & SupportPhase Sustainment Disposal Sustainment Disposal Sustainment starts immediately upon fielding or deployment. • Activities: Maintain readiness and operational capability of deployed system(s). Execute operational support plans. Conduct modifications and upgrades to hardware and software. Measure customer confidence. Demilitarization & Disposal • Activities:Demilitarize and dispose of systems IAW legal and regulatory requirements, particularly environmental considerations. Use Defense Reutilization and Marketing Office support, as appropriate. 20Oct03 NDIA SED S3T2 RLEngwall

16. EA/SD System Engineering Impact on Information Systems • Need toCapture System Information Once in Common Interoperable Format • Apply Distributed Tools for Collaborative Assessment & Optimization Including Pervasive Modeling & Simulation Throughout the System Engineering Product Life Cycle • Utilize ANSI/EIA-632 Technical Management and Technical Evaluation Processes Throughout the DoD Acquisition Process • A Broad, Extensible Representation Approach Is Key • Use EIA-927 Common Data Schema For Complex Systems 20Oct03 NDIA SED S3T2 RLEngwall

17. The Complex Systems Tower of Babel A B Concept/Tech. Development C IOC System Development & Demonstration FOC Production & Deployment Requirements Mgmt Operations & Support System Integration Functional Req Elicitation HME / HW / SW and Test Design & Analysis Design and Analysis Tactical and Analysis Decision Training and Support Ops Support System Data Today HME / HW / SW Manufacturing & Development Development Modification Process C and Upgrade B A Maintenance and Logistics Cost / Risk / Schedule Management • Stovepiped Tools With Limited Scope and No Substantial Interoperability • Multiple Independent Files and Databases With Ad Hoc Manual Configuration Management, Traceability, and Consistency Checking across Domains • Most PDM and Enterprise Management Solutions are File Based and Fail to Provide any Useful Integration of the Information Stored in the Files 20Oct03 NDIA SED S3T2 RLEngwall

18. Data Data Top Level Req Conceptual Environment IS Logical MANUFACTURING REQ CONCEPTUAL Logical Implementation Structural / HME 1000 SPEC 100 10 Info Processing Environment Top Level Req Jan Apr Jul Oct Logical Structural / HME Conceptual Manufacturing Syn Env Material Acq Platforms Capabilities Hull Hardware Function Atmospheric Fabrication Sensors Performance Mechanical Software Data Flow Assembly Weapons Dependability Electrical Operators Control Flow Terrestrial Integ / Test Communication Maintainability Hydraulic Documentation Energy Flow Threat Control Environment Handling / Deliv Tactics Constraints Pneumatic Material Flow Allied Factory Floor Robots / Mach Support Sys & Dev Eng Env Management Logistics / Supply Sys Eng Meth & Tools Schedule Operations HW/SW/HF Eng M&T Cost Training HME/Hyd/Pneum M&T Risk Maintenance Power/Propulsion M&T Staffing Repair Programmatics Common Data and Systems Across the Product Lifecycle Oceanographic • A Formal Structure for Representing Spectrum of System Data is needed • A Dynamic Schema Provides Means for Accommodating Emerging Data Representation Needs • A broad, extensible representation approach is key 20Oct03 NDIA SED S3T2 RLEngwall

19. CG47 CG47 DDG51 DDG51 DD963 DD963 PLAT SIG/ KINE SENS 4 2 SENS 3 C SENS 2 SENS 1 COMMS DATA FUSION MNS SYSTEM CONCEPTS ORD System Info Repository System Info Repository REQ SPEC Logical Structural / HME CONCEPTUAL REQ SPEC Logical Structural / HME CONCEPTUAL System Info Repository REQ SPEC Logical Structural / HME CONCEPTUAL Concept Engineering PHASE Demonstration / Production & Upgrade Exploration & Manufacturing Validation Deployment and Definition & Development Replace nt MGMT 1000 100 10 Jan Apr Jul Oct Conceptual Development SBA Concept Functional Design Top Level System Requirements Physical & Info System (HW/SW) Design Distributed Sim Framework ADVANCED SENSORS AND WEAPONS Dist Info Repository ADVANCED PLATFORMS ADVANCED COMBAT SYSTEMS Cost, Schedule & Program Mgmt DRIVERS Operations, Logistics & Training Eng Development & Manufacturing Test & Eval Capture System Information Once in Common Interoperable Format and Apply Distributed Tools for Collaborative Assessment and Optimization

20. JSF Product Development Information Model (top-level) LM Aero provided Product Information Model (DPD) (Variants = layered instance values) • Coherency & completeness cross-checks • Solid lines = primary • Dashed lines = secondary Logicalarchitecture (from SE/IPT designers) • System/ subsystem topology • Functional allocation • Technologies • Interfaces Functional allocationtrade studies Government provided context information • Air vehicle performance • Mission system capabilities • Autonomic logistics • Signatures • Reliability Operational Context (scenarios, etc.) Blue systems (Requirements are recorded in appropriate information domain) Interactions (from Kr/gov’t analysts) Performance (from IPT analysts,with gov’t review) Threat systems • Lethality/ effectiveness • Survivability Natural environment Personnel rqmts Support infrastructure Civil/militaryinfrastructure Maintainability • Assemblies & components • Software • Spatial & electrical relationships • Connections • Part records Physicalarchitecture (from IPT designers) Transportation capabilities Mobility • Specialized views: • OML, Cost, BOM, mass properties, etc. Manufacturingprocess Manufacturing/supplier capabilities DISTRIBUTION STATEMENT A: Approved for Public Release; Distribution is Unlimited.

21. FCS ACE Enables SMART Cost-Performance Trades Requirements Definition Prototyping Detailed Design Manufacturing & Production ProgramManagement Developmental &Operational T&E Training Life Cycle Sustainment Field FCS-Equipped Units of Action With Threshold Objective Force Capability by the End of the Decade. 20Oct03 NDIA SED S3T2 RLEngwall

22. Color Key • Govt • Industry • Shared • Example (i.e. Data) • Interface FCS ACE Diagram 20Oct03 NDIA SED S3T2 RLEngwall

23. Questions? Contact Dick Engwall: President RLEngwall & Associates 560 Choptank Cove Court Annapolis, Maryland 410 571-8623 rlengwall@aol.com Member NDIA SED, NDIA SED Producibility, M&S, EA/SD, & Supportability Committees; GEIA SS&TC, IT&IC, & EIA-927; AFEI; AIA SMC(exofficio); SME; IIE; WFS; IMTI; LAI 20Oct03 NDIA SED S3T2 RLEngwall