Don Monell Director, Cx Program Information Systems Office donald.w.monell@nasa.gov

1. Enterprise Architecture – Challenges for CM and DM in the NASA Constellation Program(or “Applying Technology to Constellation’s Configuration and Data Management (CDM) Challenges”) Don Monell Director, CxProgram Information Systems Office donald.w.monell@nasa.gov

2. The Constellation Program is comprised of seven Projects: Constellation’s Projects Orion - Crew Exploration Vehicle Ares - Launch Vehicle Extravehicular Activities Mission Operations Lunar Surface Systems Ground Operations Altair

3. NASA’s Exploration Roadmap(UNDER REVIEW) 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25… Initial Capability Orion (CEV) Lunar Robotic Missions Lunar Outpost Buildup Commercial Crew/Cargo for ISS Space Shuttle Operations SSP Transition Ares I Development Orion Development Ares I-XTest FlightApril 2009 Orion Production and Operation Lunar Lander Development Ares V & Earth Departure Stage Surface Systems Development

4. Constellation Program - What a GREAT Year! Orion Ares GO EVA Flight Test Beyond LEO National Aeronautics and Space Administration

5. Status: Orion Crew ModulePost-landing Orion Recovery Test National Aeronautics and Space Administration

6. Status: Launch Abort SystemTesting the LAS motors National Aeronautics and Space Administration National Aeronautics and Space Administration

7. Status: DM-1 TestSuccessfully Completed September 10 National Aeronautics and Space Administration

8. Status: Ares Mobile Launch PlatformConstruction is under way at KSC National Aeronautics and Space Administration

9. Ares I-X National Aeronautics and Space Administration

10. Ares I-X Launch National Aeronautics and Space Administration

11. Constellation’s Workforce – NASA Glenn Research Center-Lead Service Module and Spacecraft Adapter integration-Flight Test Article “Pathfinder” fabrication-Ares I-X upper stage simulator lead-Ares power thrust vector control and sensors lead-J-2X engine altitude/in-space testing-Systems Engineering and Integration support Langley Research Center-Lead Launch Abort System integration-Lead landing system Advanced Development Program-Ares I-X vehicle integration-Ares aerodynamics lead-System Engineering & Integration support Ames Research Center-Lead thermal protection system development-Aero-Aerothermal database-Ares abort simulators-Software and Guidance, Navigation & Control support Goddard Space Flight Center-Communications support Michoud Assembly Facility-Orion and Ares component mfging-Rocket propulsion testing for Ares Marshall Space Flight Center-Home for Ares Project-Ares I and V development and integration lead-LAS and SM Systems Engineering and Integration support Dryden Flight Research Center-Lead abort test flight integration/operations-Abort test booster procurement-Flight Test Article development/integration Kennedy Space Center-Home for Ground Operations Project-Ground processing-Vehicle integration-Launch operations-Recovery operations Johnson Space Center-Home for Constellation Program-Home for Projects: Orion, Mission Ops, EVA, Altair and Lunar Surface Systems-Lead Crew Module integration-Orion spacecraft integration-GFE projects management-Flight Test Program JPL (Jet Propulsion Laboratory)-Thermal protection system support-Mission Operations support-Test and Verification support Stennis Space Center-Rocket propulsion testing for Ares White Sands Test Facility-Orion Launch Abort System test site 11

12. Constellation’s Workforce – Contractors • Additional Companies with > $10M Contracts: • American Synthetic Rubber Co. (KY) • Ensign Bickford (CT) • Kirkhill-TA Company (CA) • Ladish Company (WI) • Moog, Inc. (NY) • Andrews Space, Inc. (WA) • University Contracts: • Brigham Young University (UT) • University of Illinois (IL) • University of Texas – El Paso (TX) Cytec Engineering Materials Hamilton Sundstrand Air-Lock Inc. David Clark Co. ATK – Thiokol (Ares I First Stage) L3 Communications LOCKHEED-MARTIN (Orion Prime) Aerojet BWX Technologies BOEING (Ares Prime) American Pacific Corp. Orbital Science Corp. PRATT & WHITNEY ROCKETDYNE (J2-X Engine) Honeywell Jacobs Sverdrop Paragon Space Development Votaw Precision Technologies United Space Alliance Harris Corp. Cimmaron Selected Subcontracts < $10M (currently more than 200 across 33 states & Puerto Rico): • Rudell Carbide, Inc. (CA) • Advanced Products Co. (CT) • E.I. Dupont De Nemours & Co. (DE) • Parker Hannifin Corp. (FL) • Productivity APEX (FL) • Global Equipment Co. (GA) • Snap-On Industrial (IL) • Varian Associates Inc. (IL) • Smalley Steel Ring Co. (IL) • The Caldwell Group (IL) • Major Tool & Machine Inc. (IN) • Dynamic Flowform Corp. (MA) • Standex International (MA) • Remmele Engineering, Inc. (MI) • Hitchcock Industries, Inc. (MN) • AV Chem, Inc. (MO) • JPM of Mississippi, Inc. (MS) • Turbocam, Inc. (NH) • Software House International (NJ) • United States Welding Corp. (NV) • UFC Aerospace Corporation (NY) • PCB Piezotronics, Inc. (NY) • Special Metals Corporation (NY) • Metalflex Manufacturing, Inc. (OH) • PCC Structurals, Inc. (OR) • Stein Seal Company (PA) • Electrolizing, Inc. (RI) • Northrop Grumman Systems (AL) • Teledyne-Brown Engineering (AL) • Magellan Aerospace Turbine (AZ) • Curbell Plastics (AZ) • Aero Spring & Manufacturing (AZ) • Pilot Engineering (AZ) • Shultz Steel Company (CA) • Laurel Sheet Metal Prod., Inc. (CA) • Standard Tool & Die Co. (CA) 12

13. Current State of Information Systems - “Environment Challenge” • NASA Approach: 10 centers, multiple autonomous levels, separated IT infrastructures, separate tools • “Corporate like” within a single center and/or a directorate at the Centers, particularly the Engineering Directorates • Sharing data across centers, programs and projects, contractors all with different tools requires a new level of collaboration • Corporate Approach: Common IT infrastructure within common firewall • Sharing data easier through common tools/infrastructure • Common Problem (both NASA and Corporate): data sharing across corporate boundaries, e.g., between primes, sub’s and numerous equipment suppliers, is still problematic and must be managed • Constellation Program: Integrating data from 10 “corporate-like” NASA Centers and prime contractors and numerous suppliers DA Operations Review – June 10-11, 2008 Lynn Buquo 13

14. Cx Program CharacteristicsImpacting Configuration and Data Management • Schedule • Multi-decade program • Some systems in operation while other systems are in development • Technical • “Multi-planetary body” infrastructure • Massive amounts of data generated • Massive amount of legacy design data exists (e.g., Ares 1st Stage) • Existing and new applications being used in parallel • Agency enterprise architecture in parallel development • ITAR and SBU data • Organizational • Multiple organizations supporting DDT&E • Separate organization supporting operations • International partnerships being discussed/worked • A PROGRAM spread across 10 NASA centers

15. Additional Cx CDM Challenges • Emphasis on data integration across program came late, after key initial contracts were already in place • Few data stewards actually have requirements to create and manage data as key deliverables • Information Systems policies, con ops, architecture, requirements and standards were defined late in the life cycle • Traditional mind-set of document-centric vs. data-centric • Identification of authoritative data • Development of consistent metadata across program • Security of the data and controlled access to the IT systems

16. Cx Enterprise Architecture • Security Architecture • Authentication • Access Control • Data Security • Network Security Business Architecture • Technology Architecture • Information Framework (high performance and highly scalable) • Data Model Management Service • Workflow and Rules Engine • Metadata Mgt Service • Controlled Vocabulary Service • Search and Query Service • SOAP/REST APIs Software Architecture • Enterprise Architecture Development • Proactively planning horizontal and vertical integration • Applying EA tenets • Utilizing numerous integration technologies as appropriate • Technology Roadmap guiding evolution • Performing trades studies to document develop vs buy decisions (MDM trade status in backup) Data Architecture

17. Cx Information Systems Architecture (CISA) Authoritative Data Consumers External Data Providers ICE Vignette Portal: Centralized Access Cx Data Mashups Other Web Applications CxDL GO MO Federated Connectivity & Interoperability Services D-Aggr API or Web Service Uniform Data Access Information Integration Staging Repository Authoritative Data Sources ICE-NDCCAIT Cobra Cradle Primavera Windchill wInsight (Oracle-Unix) MOD-JSC (?) ISO - JSC IRMA CRpipeline/DM20 Master Link Book IS Portfolio (SQL Server-Windows .NET) MAS-ARC FMEA-CIL GMIP Hazard DB PRACA (MYSQL-Unix) SAvIO-HOSC IBMS CCTR SoR (AllegroGraf-Unix) CxDL-HOSC Websphere iRODS (?) OMS-KSC (?) Hosting for Decision Support Hosting for Operational Support NASA Model Registry Network eAuth NAMS ARC JSC NDC KSC JSC HOSC

18. CxP Configuration Data Management • Significant progress made in CDM over the last year: • Guiding documentation (e.g., plans, policies & guidelines, and requirements) near completion • Developing a program wide CSA/ERS capability (covered in following slides) • Leading, with ICE and Cx IS EA, development of a product structure plan and capability (covered in following slides) • Developing a records management approach that is a paradigm shift for NASA (briefly covered in following slides) • Playing a key role in understanding and “locking down” the program PDR dataset • Realizing improvements in the CR process management and execution across the program

19. Cx Configuration Status Accounting (CSA): Ongoing Changes to Baseline CR SPEC to Rev C BOARD Third CR CR SPEC to Rev B CR SPEC to Rev A CR SRD to Rev A CR SRD to Rev B Second CR CD & DIRECTIVE ACTIONs to PROJECT(s) First CR CD & DIRECTIVE ACTIONS to PROJECT(s) CD & DIRECTIVE ACTIONs to PROJECT(s) BOARD BOARD • Over time, keeping track of the versions and keeping them in sync is more difficult. • Program must be able to see current baseline all the time, not just at major reviews • By integrating tools used by program/project and available to elements, Cx CSA provides the visibility real time • What is being designed to is the right specification • Built to the right CAD drawing • Delivering the right version of the part and finally • Flying the correct integrated configuration TIME

20. CSA Data Combined with Managed Technical Data • CISA allows traditional CSA to be merged with other data managed by the program to provide users a complete historical picture at any step in the product’s lifecycle

21. Cx Engineering Release System • Established an automated release process utilizing the capabilities inherent within our product data management tool • Associative release information with the product data – one common system for ease of visibility and traceability • Flexible workflows allowing for greater use among distributed groups in adherence with standards High-level process flow for ERS

22. Product Breakdown Structure - Vision Why a Space Program needs an Integrated PBS Provides the Program the ability to organize and trace product information (e.g. data, documents) throughout its life cycle (e.g. design, manufacturing, verification and validation, assembly/integration, launch, operations). The PBS is an integrated hardware Parts and software Components list with all related data associated to it. Operations Single source to begin to locate all part information Today’s SSP MER process Understanding process of obtaining data harder than actually learning functionality of systems operation. Current ISS/SSP programs if something goes wrong – can usually get crew or equipment back to Earth for further research repair; this is not the case for other missions Future Programs will strive to maximize automated data access while curtailing the number of human resources deployed to support operations. Some data structure MUST be defined for the future programs being considered by the agency; the structure can be product-, mission-, architecture-, or TBD-based 12 February 2010

23. Building the Integrated PBS PBS Support for Cx PDR The PBS is populated with data over time based on the phase of a Program. 12 February 2010

24. Product Associations to External Data PBS and CAD model data is associated to many other authoritative data items. • Identifying Associations • Design Data • Analysis, Requirements, Risk, Manufacturing, Verifications, Variance, Test, and Operation Data • Managing Associations • Release and CM processeswill provide management ofassociations • Associating Products to otherData 12 February 2010

25. CxP Records Management Approach • Due to possible acceleration of CxP Closeout, ISO CDM is drafting a Records Closeout Plan • Requirements that are applicable to closeout will be identified in the RM Closeout Plan • In cases where authoritative data is not yet fully mature, alternative methods for storing records must be established • Records Management Approach • Vetted understanding of RM Requirements for CxP • NARA RM requirements • CxP Records Management Requirements

26. CxP Records Closeout Plan Approach • Key Components of CxP Records Closeout Plan • Identifying Authoritative data that will become records • To include authoritative data and the systems in which it resides • Area of focus includes Contractor Authoritative Data to be worked with the Contracts Office • Collecting identified records • Goal is to perform this task in a manner that leverages off the work that has been done in automating and moving toward a data centric methodology • Will allow for better access to data and improve ability to re-instantiate any record or grouping of records for a future use • Storing the identified records (while preserving ability to access records) • Contracting organization to work contractor data delivery • Information Systems team to provide a system to catalog, search and retrieve records

27. Areas of Focus for CM/DM Community • Early support to defining enterprise architectures • Configuration and data management processes that adapt to emerging technology capabilities • Model-based project management and systems engineering • Application-independent data descriptions / models • Evolving support across the whole lifecycle of a program

28. Concluding Remarks • Constellation’s success is highly-dependent upon the CM and DM community’s support and proactive involvement • CDM has key roles in developing the Cx Information Systems Architecture • Data is “KING”…for many years in CxP • Records Management involves more than just “locking down the data” • The Constellation Program has significant, and sometimes unique, challenges to consider when applying CM and DM