NASA/ESA PDE 05 20 Apr 05 MultiView: Common Data Schema for Complex Systems

1. Mr. Jim Colson NASA/ESA PDE 0520 Apr 05MultiView: Common Data Schema for Complex Systems U.S. Army Materiel Command NEED TO BE FASTER, MORE AGILE, LESS BUREAUCRATIC - NEED TO FIGHT THIS EVERYDAY

2. Outline • LOGSA and the GEIA-927 MultiView Standard • MultiView Project Overview • Current Status and Future Plans for MultiView Project

3. Key Players Transfer of Function: DA Mandated. AMC Tasked LOGSA Dec 2004 GEIA-927 (MultiView) Standard Supported by:

4. GEIA-927 (MultiView) Project Overview Data Data Top Level Req Conceptual Environment Top Level Req IS Implementation Manufacturing Conceptual Logical IS Logical Info Processing Structural / HME Structural / HME Environment REQ MANUFACTURING CONCEPTUAL Logical Implementation Structural / HME 1000 SPEC 100 10 Jan Apr Jul Oct Syn Env Control Support Sys & Dev Eng Env Management Environment 4 3 1 2 Develop Common Data Schema Validate in Distributed COTS Testbed • Data Interoperability • Consistency Management • Interaction with Legacy Tools • Integration of Legacy/Emerging Data Sources • Leverage Existing and Emerging Data Standards • Accommodate Tools in Use by Candidate Pilots • Work in the Gaps Where Required Conduct DoD Pilots Manage Transition • Evolve Industry Consortium • Focus on DoD Program Mgr Needs • Implement Testbed Capabilities • Demonstrate Utility (Collect Metrics)

5. Data Source Confusion Operational Need System Data Today System Data in the Future IDE Top-Level Requirements Environment Representations Ops & Support Budget, Schedule, Risk Engineering Development Demonstration Validation Concept Exploration Functional Design HW/SW Design Logistics & Support HW/SW Development • Data Shortfalls, Management Challenges • Stovepiped Tools & Data Stores With Limited Scope and Scalability • Limited Interoperability Among Tools & Data Stores • Error-Prone Traceability & Consistency • Optimized Management Environment • Enables Collaborative, Concurrent Effort Across Distributed Sites • Timely Snapshots of Program Status Across Multiple Information Domains • Complete, Integrated Picture of the Program • Today: Suboptimal, Reactive Program Management Environment • Future: Proactive Management Enabled by Integrated Information

6. Common Systems Information Schema Concept Data Top Level Req Conceptual Environment IS Logical MANUFACTURING REQ CONCEPTUAL Logical Implementation Structural / HME 1000 SPEC 100 10 Jan Apr Jul Oct Control Environment Data Info Processing Environment Top Level Req Logical Structural / HME Conceptual Manufacturing Syn Env Material Acq Platforms Capabilities Hull Hardware Function Atmospheric Fabrication Sensors Performance Mechanical Software Data Flow Oceanographic Assembly Weapons Dependability Electrical Operators Control Flow Terrestrial Integ / Test Communication Maintainability Hydraulic Documentation Energy Flow Threat 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 • Formal Structure for Representing Spectrum of System Data • Dynamic Schema Provides Means for Accommodating Emerging Data Representation Needs • A Broad, Extensible Representation Approach is Key

7. Data InteroperabilityReuse & Management GEIA-927 Schema MV_Element Material_ Document System Event Facility Environment Flow or_component Design Actor Tool Plan Process Objective Function Person Organization Requirement Constraint System HW, SW Design System Requirements Structural System Design Within a Domain, between Tools Systems Engineering

8. Data InteroperabilityReuse & Management GEIA-927 Schema MV_Element Material_ Document System Event Facility Environment Flow or_component Design Actor Tool Plan Process Objective Function Person Organization Requirement Constraint Training Supply Repair System HW, SW Design System Requirements Structural System Design Within a Program, Across Domains Logistics Support Systems Engineering DD(X) Program

9. Data InteroperabilityReuse & Management GEIA-927 Schema MV_Element Material_ Document System Event Facility Environment Flow or_component Design Actor Tool Plan Process Objective Function Concept Development Concept Development Logistics Support Logistics Support Person Organization Requirement Constraint Systems Engineering Within a Service, Across Programs Systems Engineering V-22 JSF USAF

10. Data InteroperabilityReuse & Management GEIA-927 Schema MV_Element Material_ Document System Event Facility Environment Flow or_component Design Actor Tool Plan Process Objective Function Person Organization Requirement Constraint Within DoD, Across Services Virginia Class Submarine V-22 Joint Strike Fighter DD(X) Space Based Radar F/A-18E/F DoD

11. Life Cycle System Management GEIA-927 Schema MV_Element Material_ Document System Event Facility Environment Flow or_component Design Actor Tool Plan Process Objective Function Person Organization Requirement Constraint COTS Server Viewer Agents Queries Administration Schema Editing Manufacturing Operations, Logistics & Training Program Mgmt. Concept Development System HW, SW Design System Requirements Test & Eval Structural System Design • Establish Traceability • Determine impact of changes across domains • Perform complex analysis on integrated information • Configuration Manage Data • Baseline across all information domains • Manage multiple options & tradeoffs • Be alerted when data of interest changes or schedule periodic analysis of data • Graphically View or Edit Any Information • Common interface to all information • Aids verifying data completeness

12. What Has Been Done? Common Data Schema Development • Standards Based • ISO 18876 (IIDEAS) Basis for Data Modeling Methodology • ISO 15926-2 (EPISTLE Core Model(ECM)) Initial Integration • Current State of Data Schema • Detailed Integration Procedure Defined • Standards Integrated (ongoing) • ISO 10303 STEP (Standard for the Exchange of Product Model Data) • PAS 20542 – Systems Engineering • DoD Corporate Logistics Data Model • AP212 – Electrotechnical Design and Installation • AP239 – Requirements, Effectivity, Documentation, Class, State, Activity (Systems Engineering) • Data Concepts Mapped to Model • Usage and Tailoring Guides Developed

13. Implementation Initiatives Post-Fielding Support Analysis SPAR (Simulation) Excel GEIA 927 Schema Data Comms Controller Data Mapping & Translation Database Interface Mechanisms ODBC Native Oracle JDBC XML Future FED LOG CCSS CMIS Engineering Concept PHASE Demonstration / Production & Upgrade IETM Manufacturing Exploration & Validation Deployment and Future & Development Definition Replace nt LIF CDDB MGMT FVPDS SBSX 1000 100 10 ATAV MEARS Jan Apr Jul Oct WLMP OSMIS WOLF PADDS LIDB SB AMDF FVPDS 700 - 20 Web PFSA JED CBS X CATS MICS ATIRS RIDB SDS AMCOS ReqVal Modified COTS MultiView-specific Key Legacy COTS • Initial Schema Implementation on Abrams • Schema Training and some Utilization on Navy DD(X) Program. • Interest From V-22 and Other Programs. • LOGSA Acquisition Logistics Tools Schema Implementation.

14. LOGSA Acquisition Logistics Tools Technology Development System Development & Demonstration Production & Deployment Operations & Support Concept Refinement A B C Logistics System Development Ensure Supportability Considerations Evaluate Post Production Support ILS Planning/ Analyzing Alternatives Metrics Tracking – Recap • Integrated Logistics Support (ILS) And Supportability Planning Documents Generation • Rule Based Expert System • Current Policy Compliant • Web Based • Standard Logistics Formats • Interface with LMP • Satisfies LSAR And LMI Requirements • Assists In Technical Manual Development • Level Of Repair Analysis • Force Structure Evaluation • Sparing/Stockage Optimization • Repair Versus Discard • Provides Weapon System View • Supports Fleet Management • Metric Tracking • Weapon system Assessment • Performance Data • Life Cycle Cost Model • Trade Off/ Comparative Analyses • Warranty Analysis • Reliability Growth Analysis • Risk Analysis

15. What is Next ? Common Data Schema Development • Next Integration Steps • Further Integration of AP233 (Systems Engineering) • Further Integration of AP239 (Product Life Cycle Support) • Evaluate EIA-836 (CM) for Integration • Future Plans • Identify Industry “Voids” in Data Interchange Standards such as LMI/LSA Data. • Integration of Acquisition Logistics Data Elements • Simplify Schema (Remove Little Used Areas to Reduce Complexity) • Development of Domain-Specific Views • Facilitate Standard Review by Industry Experts • Incorporate Comments & Revisions • Restructure Standard to Accommodate Views • Send for Ballot in Late 2005

16. Moving Forward • Upcoming Meetings/Workshops • GEIA G33 (SE) & G47 (CDM) 2005 Quarterly Meetings: • April 12-14 Phoenix, AZ • June 20-23 Baltimore, MD • Sept 19-23 Atlanta, GA (Annual Conference) • LOGSA/SOLE/ASAALT Hosted ILS Conference and Workshops • May 3-5 Huntsville, AL (Enabling Life Cycle Logistics) • Government & Industry Working Group • Cross Service Representation (Army, Navy, AF, DLA) • Multiple Industry Representatives • Promotion of Standard at All Levels of Government & Industry.