Jody H. Fluhr August 17, 2010

1. IT Infrastructure: Key to Successful Application of Model-Based Systems Engineering on NASA Programs Jody H. Fluhr August 17, 2010

2. Introduction • Common Principles • Increase Collaboration and Productivity • Improve Integration • Increase effectiveness and efficiency • Constellation Program Systems Engineering • Define and Deploy a Systems Engineering Capability (People, Processes and Tools) for the program • Applicable to Agency’s SE Capability • Innovation in Systems Engineering drives greater innovation in IT Presentation Title —2— March 5, 2010 AGENCY’S INFORMATION TECHNOLOGY AND ENTERPRISE ARCHITECTURE IS KEY TO SUCCESSFUL SYSTEMS ENGINEERING ON NASA PROGRAMS.

3. Constellation Program • Overview • IT-Related Directives • IT Infrastructure Overview • Model-Based Systems Engineering Capability Presentation Title—3—March 5, 2010

4. Constellation Program ISS Initial Capability Moon Lunar Capability Missions Ares I Launch Vehicle Ares V Launch Vehicle Ground Operations Surface Systems Systems Launch Suit EVA Orion Crew Vehicle Mission Operations Altair Lunar Lander Team

5. Constellation Program IT-Related Directives • Directive to use an IT collaborative environment for generating, using and managing information assets • End user has immediate access to all authorized Program/Project data, regardless of their organization (gov’t or contractor) • Consistent Interface to program/project data • Established best practices • Facilitate Traceability/Compliance across systems • Directive to use a single systems engineering database as the authoritative source for: • Technical requirements, verification data • Design Reference Mission data and Operations Concepts data • Operational, functional, and physical architecture data • Functional analysis data • Linkage/Traceability of the above Presentation Title—5—March 5, 2010 Constellation Leadership recognized the importance of IT capabilities and the need for clear policies.

6. Constellation Systems Engineering Capability • System Engineering tools accessible to nation-wide team (via ICE), configured to support the defined systems engineering process • A Model-Based Systems Engineering Process consisting of: • A tool-agnostic process definition that can be implemented in any tool of choice • Work Instruction-level procedures to guide engineers in execution of SE process in program-selected tools • Automated audits/metrics to ensure process compliance and identification of issues • Work Instruction-level procedures to maintain data integrity • Formal Training organized along systems engineering process areas • Approximately 10 training classes available • Over 100 training classes conducted with hundreds of engineers trained

7. Partial List of Constellation Information Assets • Requirements (Architecture/System/Element/Operational) • Operational Concepts • Design Reference Missions • Physical Architecture (Systems, Interfaces) • Verification • Functional/Performance data • Risks • Hazards • Design Compliance • Product Structures • Drawings • Trade Studies • Schedules • Models and Simulations • Documents Presentation Title—7—March 5, 2010

8. Constellation IT Infrastructure - Integrated Collaborative Environment (ICE) Presentation Title—8—March 5, 2010 ICE Portal provides access to applications used to manage information assets.

9. Constellation IT Usage Metrics - Part 1(Tools, Applications, Services and Integrations) High End-User Experience User/Deployment Experience Needed

10. Constellation IT Usage Metrics - Part 2(Tools, Applications, Services and Integrations) High End-User Experience User/Deployment Experience Needed

11. Cradle Systems Engineering Tool Metrics

12. Cradle Systems Engineering Tool Metrics

13. Model-Based Systems Engineering Process & Procedures • Process & Procedures documented and available via Team Wiki • Process involves development in four key areas for each level of the architecture: • Requirements (and Associated Verifications) • Mission Definition • Physical Architecture • Functional Architecture Presentation Title—13—March 5, 2010

14. Constellation SE Process Wiki Presentation Title—14—March 5, 2010

15. Detailed Procedures Available via Wiki Presentation Title—15—March 5, 2010

16. MBSE Example – Integrated Mission Model Existing Products are created by Extracting Reports from SE Tool Models Operational Models as the Authoritative Integrated Source for Operations Information eliminates Product Synch Separate Products Incur Substantial Coordination Costs Published from SE Tool Report Generation OPSCON OPSCON Compiled from Phase Models DRM Model Reports from Simulation Detailed Timeline Simulation Phase Model & Write-ups Summary Timeline Summary Timeline Detailed Timeline Activity Model & Definitions (including attributes like durations, resource usage, etc.) Operational Models in SE Tool Current State Opportunity Desired State

17. Conclusion - Pushing the Envelope • As NASA continues to develop its Systems Engineering capabilities, greater demands will be placed on the IT and the Enterprise Architecture • While benefits have been realized, more needs to be accomplished: • Utilizing tools to develop and manage authoritative information is a big step forward, it’s possible to have program authoritative information locked in “tool silos”. • Tool-to-Tool integrations have been accomplished but has its limits. • Maximizing the value of the authoritative information requires better Data Integration – Timely, customized and accessible. Presentation Title—17—March 5, 2010

18. Backups Presentation Title—18—March 5, 2010

19. Systems Engineering Processes – NASA SE Handbook Figure 2.1-1 The systems engineering engine

20. Model-Based Systems Engineering • An approach to systems engineering where information about the system is: • Contained in an accessible database or repository • Captured in a standardized, methodical manner • Captured in graphical models when appropriate • Related and linked in standardized ways • Capable of being queried and reported • Contrast to “Document-Based” Systems Engineering • Equivalent of data ‘silos’ • Manual correlation of data • What are the benefits? • Improved Traceability of Mission Definition, Requirements, Verification and Architecture • Improved Data Management, Accessibility and Quality • Improved Integration and Insight • Capabilities to query the data, do advanced checks, improve integration • Reduced cost of documentation • Data is captured once in an authoritative data source (repository/database) and is extracted to produce the content of a document • Content integrity between documents and artifacts.

21. Information Integration Needs Data Consumers …… Underlying Architecture IS Services, Link Manager, Security, CDM …. If one end of the data is modified then the end user is notified Data is pulled from authoritative sources Read Only Data Sources (MAS, JSC, ICE, Others) CoFR DB (CxOW) Problems DB (CxPRACA) Risks DB (IRMA) Hazards DB (cxHazard) Schedules DB (Primavera) Others … 21 Additional sources: Cradle, CAIT, Windchill Products Structure, Windchill Documents

22. On Demand CoFR System The CoFR System enables continuous monitoring of flight readiness status for decision makers by dynamically integrating data from engineering databases All CoFR processes pull together diverse information to inform decision making The CoFR System provides interactive overviews of pertinent data and enables drilldown for more detailed analysis Provides a view into the status of tasks and products per each organization that lead up to endorsements for a mission or program event The CoFR System can provide views to meet specific needs of NASA: Programs (Launch Vehicles, elements, etc) Milestones (FRR, DOL Review, etc.) Organizations (MOD, SR&QA, etc.) Roles (Mission Manager, Chief Engineer, Project Managers, etc.)