1. March 24, 2009 1 ISE-6 Phase 2 Demo March 24, 2009

2. 2 Introduction Matt Porteus provides a brief introduction to the ISE-6 project and team and introduces Burt Gischner (approx 5 minutes) Burt Gischner provides the ISE-6 Overview Briefing and passes the lead back to Matt Porteus (15 to 20 minutes) Matt Porteus introduces the demo, describes the scenario,

3. March 24, 2009 3 Intro - Demo Scenario The Dual Band Radar (DBR) OEM receives a Government-Industry Data Exchange Program (GIDEP) alert indicating that the sole source vendor has discontinued production of the REX RF oscillator. In response to the DBR REX RF oscillator Diminishing Manufacturing Sources and Material Shortages (DMSMS) issue, the DBR OEM identifies another source for an oscillator that meets the REX functional requirements. However, the oscillator available from the new source is a Double Resonant Optical (DRO) parametric oscillator which dissipates considerably more heat than the original Single Resonant Optical (SRO) parametric oscillator. In addition, the DRO oscillator will require some minor packaging changes in order to satisfy the mechanical interface requirements of its application in the DBR REX. The packaging changes include a different mechanical envelope and different fasteners which employ 3/8“ captive hex head screws vice standard slotted, pan head screws. The alternative to the DRO oscillator is a significant redesign of the DBR REX.

4. March 24, 2009 4 Intro - Demo Scenario The Program Office conducts a trade study to analyze the alternative to the DRO oscillator which again is a significant redesign of the REX. Although the DRO oscillator increases the heat load of the REX, the trade study shows that the alternative of a significant REX redesign represents unacceptable schedule and cost risk to DBR production. The Program Office considers the DRO the best available solution to solving the REX RF oscillator DMSMS problem. As a result of the trade study findings the Program Office initiates a Ship Change Document (SCD). The SCD identifies the proposed DRO change including information regarding the resultant increase in REX heat load. Upon initiation of the SCD the DBR and HM&E ISEAs are notified of the proposed REX RF oscillator change.

5. March 24, 2009 5 OEM ISEA Shipyard / NAVSSES Collaboration Develop ECR Changes Revised Radar Mod 2 Radar Program Office(s) Authorization, Funding NDE-FMP Revised Radar Data Revised HM&E Data Identify Changes Navy Common Source Database (Content@) CDMD-OATDMISLEAPS NAVICP WSF Authorization, Funding Program IDE DB LSAR Update Design and Logistics Update Design and Logistics As-Is Scenario – Point-to-Point Interfaces

6. March 24, 2009 6 OEM ISEA Shipyard / NAVSSES Collaborative Development of SCD Revised Radar Program Office(s) Authorization, Funding Revised Radar Data Revised HM&E Data Update Design and Logistics S1000D Authorization, Funding AP 239 + S1000D AP 239 + S1000D Program IDE LSAR PLCS (with S1000D references) Identify Changes Update Design and Logistics Changes NDE-FMPCDMD-OATDMISLEAPS NAVICP WSF Demo Scenario Navy Common Source Database (Content@)

7. March 24, 2009 7 Linking Design Data to Logistics Data LCB Structure ILS Data & Products Logistics Data Zone/Assembly Structure Design Data & Products Design Data Diagrams/ Drawings Components Catalog Parts 3D Models Compartments TcE LCB Object Supportability RCM Analyses PM/CM Records MIP/MRC CSA SDIF Records Equip. Validation Aids Supply Support Tech Data Manuals/Publications HSC ICN/HSC RIC RMA TMIN Catalog FMECA RMAAA Catalog Number Drawing Number Compartment Number ESWBS PRID Serial Number Vendor Part Number/CAGE … 540 54100 54120 54121 541212 5412121 54121211 … … Grand Block B13 ASSY 2110 ASSY 2120 ASSY 2130 Grand Block B16 ASSY 2140 ASSY 2150 ASSY 2160 … VFI/GFI APL/AEL Test Equipment Tools

8. March 24, 2009 8 Baseline DBR ISEA Shipyard / NAVSSES Revised Radar Data Revised HM&E Data Update Design and Logistics S1000D AP 239 + S1000D AP 239 + S1000D Program IDE LSAR Identify Changes Update Design and Logistics Changes AP 239 + S1000D AP 239 + S1000D NDE-FMP Navy Common Source Database (Content@) CDMD-OATDMISLEAPS NAVICP WSF DDG 1000 IDE has integrated design and logistics data for baseline Common Source Database has S1000D data modules for baseline LEAPS has ship design data for baseline

9. March 24, 2009 9 Baseline DBR ISEA Shipyard / NAVSSES Revised Radar Data Revised HM&E Data Update Design and Logistics S1000D AP 239 + S1000D AP 239 + S1000D Program IDE LSAR Identify Changes Update Design and Logistics Changes AP 239 + S1000D AP 239 + S1000D NDE-FMP Navy Common Source Database (Content@) CDMD-OATDMISLEAPS NAVICP WSF DDG 1000 IDE has integrated design and logistics data for baseline Common Source Database has S1000D data modules for baseline LEAPS has ship design data for baseline

10. March 24, 2009 10 Baseline: LEAPS ISEA Shipyard / NAVSSES Revised Radar Data Revised HM&E Data Update Design and Logistics S1000D AP 239 + S1000D AP 239 + S1000D Program IDE LSAR Identify Changes Update Design and Logistics Changes AP 239 + S1000D AP 239 + S1000D NDE-FMP Navy Common Source Database (Content@) CDMD-OATDMIS LEAPS NAVICP WSF 3D graphical context for Radar and HVAC Systems Data import (PLCS XML), potential relationship between design and logistics data How the data is used by the Navy in Life Cycle maintenance

11. March 24, 2009 11 Baseline: IDE ISEA Shipyard / NAVSSES Revised Radar Data Revised HM&E Data Update Design and Logistics S1000D AP 239 + S1000D AP 239 + S1000D Program IDE LSAR Identify Changes Update Design and Logistics Changes AP 239 + S1000D AP 239 + S1000D NDE-FMP Navy Common Source Database (Content@) CDMD-OATDMISLEAPS NAVICP WSF This is the DDG1000 IDE implemented on Teamcenter Data import from OEM/ISEA and Shipyard (PLCS XML) Logistics Configuration Baseline and associated design and logistics data Link between equipment configuration and S1000D data modules Link from Program IDE to Content@

12. March 24, 2009 12 Updated Requirements Data Scenario DM 1.1 DM 1.2 DM 1.3 Chillers Duct 1 Chiller 2 Duct 2 HVAC Sys Drawing2 DM 2.3 DM 2.2 HVAC Sys TM 1 HVAC Sys TM 2 ISEA IDE (Radar) DM 1.1 DM 1.2 Mod 1 Radar TM Mod 1 DM 1.3 Mod 2 DM 2.1 Mod 2 Radar TM DM 2.2 Chiller 1 HVAC Sys HVAC Ducts HVAC Sys Drawing1 Shipyard Design & IDE

13. March 24, 2009 13 DBR Update: ISEA ISEA Shipyard / NAVSSES Revised Radar Data Revised HM&E Data Update Design and Logistics S1000D AP 239 + S1000D AP 239 + S1000D Program IDE LSAR Identify Changes Update Design and Logistics Changes AP 239 + S1000D AP 239 + S1000D NDE-FMP Navy Common Source Database (Content@) CDMD-OATDMISLEAPS NAVICP WSF Evaluate SCD design changes Contract OEM for updated design and data modules Review updated data modules Update Navy system data Export to IDE

14. March 24, 2009 14 DBR Update: IDE Update ISEA Shipyard / NAVSSES Revised Radar Data Revised HM&E Data Update Design and Logistics S1000D AP 239 + S1000D AP 239 + S1000D Program IDE LSAR Identify Changes Update Design and Logistics Changes AP 239 + S1000D AP 239 + S1000D NDE-FMP Navy Common Source Database (Content@) CDMD-OATDMISLEAPS NAVICP WSF Import updated DBR data LCB data updated

15. March 24, 2009 15 DBR Update: HVAC design impact ISEA Shipyard / NAVSSES Revised Radar Data Revised HM&E Data Update Design and Logistics S1000D AP 239 + S1000D AP 239 + S1000D Program IDE LSAR Identify Changes Update Design and Logistics Changes AP 239 + S1000D AP 239 + S1000D NDE-FMP Navy Common Source Database (Content@) CDMD-OATDMISLEAPS NAVICP WSF The HM&E ISEA evaluates the SCD and notes the increased heat load that would result from the DRO. AC Unit design changed to account for additional cooling requirements - higher cooling capacity compressor HVAC system modified Updated equipment information imported into Program IDE from Shipyard using PLCS XML

16. March 24, 2009 16 DBR Update: HVAC Logistics Impact ISEA Shipyard / NAVSSES Revised Radar Data Revised HM&E Data Update Design and Logistics S1000D AP 239 + S1000D AP 239 + S1000D Program IDE LSAR Identify Changes Update Design and Logistics Changes AP 239 + S1000D AP 239 + S1000D NDE-FMP Navy Common Source Database (Content@) CDMD-OATDMISLEAPS NAVICP WSF Need to identify which S1000D data modules must be updated Candidate S1000D data modules requiring change are identified Query IDE based on HSC for changed equipment in PLCS Candidate S1000D data modules are reviewed and updated in Navy CSDB

17. March 24, 2009 17 Summary Enables Virtual Navy Enterprise Automated identification of change impacts –Reduce costs to evaluate changes –Support cost benefit analysis, design trade studies, etc. –Impact of design or logistics changes Exchange of integrated design and logistics product data –Between Design and Logistics –Between ISEA, NAVSEA 05, Shipyards, and OEMs –Throughout full life cycle (currently only in acquisition) Standardized data exchange formats –Neutral format IDE data –Improved quality and reduced cost through standardized schema and automated validation/exchange –Enable data reuse

18. March 24, 2009 18 Backup

19. March 24, 2009 19 Demo Script Baseline System Delivered to the Navy –Pete Lazo describes the scenario data for the baseline system using LEAPS (10 minutes) 3D graphical context for Radar and HVAC Systems Data import (PLCS XML), relationship between design and logistics data How the data is used by the Navy in Life Cycle maintenance –Mike Olson describes the baseline system using Teamcenter Enterprise (10 minutes) Data import from OEM/ISEA and Shipyard (PLCS XML) Logistics Configuration Baseline and associated design and logistics data Link between equipment configuration and S1000D data modules Link from Program IDE to Content@

20. March 24, 2009 20 Demo Script Ship Change Document (SCD) initiated to update REX RF Oscillator –Ted Briggs describes the design change to the REX RF Oscillator and its affect on logistics data (15 minutes) Show changes to equipment configuration data and S1000D data modules –Discuss adding Navy specific information to OEM data (such as compartment numbers, APLs or HSCs) –Show data and linkage to data modules Review updated baseline (using IETPS Viewer) from OEM (PLCS XML file including links to S1000D data modules) Discuss load of S1000D data modules into Navy CSDB Data export to Program IDE using PLCS XML

21. March 24, 2009 21 Demo Script Ship Change Document (SCD) initiated to update REX RF Oscillator (cont’d) –Mike Olson describes the affect of the REX RF Oscillator change on the HM&E HVAC equipment and logistics data using Teamcenter and Content@ (25 minutes) Import DBR PLCS file and show changes to LCB.(TBD) Discuss impact of radar changes on AC system AC Unit design change to account for additional cooling requirements - higher cooling capacity compressor Updated equipment information imported into Program IDE from Shipyard using PLCS XML Candidate S1000D data modules requiring change are identified (list) –Query IDE based on HSC for changed equipment in PLCS Candidate S1000D data modules are reviewed and updated in Navy CSDB –Create work package in Content@ Discuss using PLCS file to transfer modified system configuration to LEAPS

22. March 24, 2009 22 Demo Script Matt Porteus provides a brief summary, emphasizing the potential importance of this type of exchange to automate and improve identification and management of changes in the Navy enterprise. (approx 5 minutes)

23. March 24, 2009 23 Presentation Template Role in Scenario Name and short description of system being used to demonstrate activities Description of activities being demonstrated Description of activity inputs and outputs (data, formats, and sender/receiver)

24. March 24, 2009 24 Demo Scenario - Radar The DBR ISEA evaluates the SCD and notes that tech manual changes would result from replacing the SRO oscillator with the DRO oscillator. However, the DBR ISEA also notes that the SCD does not specify the exact data modules impacted in the DBR tech manual. Realizing that there is a DBR tech manual change under development as a result of a previous SCD, the DBR ISEA sees an immediate need to quickly understand the exact impact of the DRO oscillator SCD to the DBR tech manual. The DBR ISEA sees an opportunity to combine the tech manual changes resulting from the DRO SCD with the change under development. Using the IDE, the DBR ISEA runs a query of the DBR tech manual against the REX RF oscillator Hierarchical Structure Code (HSC). The query returns the list of DBR tech manual S1000D data modules related to the REX RF oscillator. The list is compared to the changes under development to determine the impact. The S1000D data modules affected by the REX RF oscillator change are updated by the OEM to reflect the change and submitted to the ISEA for review and approval. The approved S1000D data modules are loaded to the Navy Common Source Database (CSDB) and the revised technical manual is published for distribution.

25. March 24, 2009 25 Demo Scenario – HM&E The HM&E ISEA evaluates the SCD and notes the increased heat load that would result from the DRO. Using the IDE, the HM&E ISEA runs a query of cooling equipment using the space number in which the REX is housed. The query returns the list of cooling equipment for the space in which the REX is housed. The cooling equipment is evaluated for the impact of the change and it is determined that a compressor with higher cooling capacity is required. The AC Unit is redesigned to include a higher capacity compressor. Based on the new design, the technical manuals need to be updated. Using the IDE, the HM&E ISEA runs a query of the AC Unit tech manuals against the compressor Hierarchical Structure Code (HSC). The query returns the list of AC Unit tech manual S1000D data modules related to the compressor. The Navy Common Source Database (CSDB), where the data modules are maintained, is queried using the list of S1000D data modules related to the compressor. The data modules are evaluated by the technical writer and the appropriate data modules are updated to reflect the change. The new technical manual is published for distribution.