30 April Enabling Shipbuilding Interoperability ISE-6 Project Exchange of Product Models for Life Cycle Support ISE-6 Final Demonstration Overview Presentation Presented on: April 30, 2009 Presented by: Dr. Burton Gischner Electric Boat Corporation Integrated Shipbuilding Environment

30 April Agenda Integrated Shipbuilding Environment (ISE)-6: A National Shipbuilding Research Program (NSRP) Project to Enable Interoperability for Product Life Cycle Support (PLCS) –Overview of NSRP –Interoperability Problem and Solution –ISE Architecture, Information Model Methodology, and Roadmap –Current Focus on Life Cycle Support –Summary

30 April National Shipbuilding Research Program (NSRP) Advanced Shipbuilding Enterprise (ASE) NSRP ASE is a collaboration of 12 major U.S. Shipyards focused on industry-wide implementation of solutions to reduce the cost of building and maintaining U.S. Navy warships The collaboration was created in 1998 by industry in response to the Navy’s request for a cost-effective, cross-program vehicle for rapid and effective implementation of cost-reduction processes and technologies to address common cost drivers The program targets solutions to consensus priority issues that exhibit a compelling business case – solutions that include both leverage of best commercial practices and creation of industry- wide initiatives with aggressive technology transfer to, and buy-in by, multiple U.S. Shipyards

30 April NSRP Major Initiative Areas NSRP is structured into six Major Initiatives that tie the strategic vision to proposed industry research through collaborative R&D and other mechanisms Each Major Initiative constitutes a strategic technology focus area that is managed and budgeted by the NSRP ASE Program The Major Initiatives include: –Shipyard Production Process Technologies –Systems Technology –Business Process Technologies –Facilities, Tooling, and Risk Management –Product Design and Material Technologies –Crosscut Initiatives ISE is a major effort under the Systems Technology initiative

30 April NSRP = Industry-wide Collaboration Effecting Large Scale Change with Industry-wide Solutions Accuracy control – metrology, processes and tools Benefit: Reduces rework labor, materials, cost and cycle time; enables automation Steel Processing – Laser cutting, precision forming, and tab & slot technology Benefit: 30% reduction in steel cutting costs; 8% reduction in steel plate usage in first production use Joint Lean Learning Curve - Accelerate adoption of productivity improvement Benefit: Systematic, repeatable boosts in productivity from shop-level to design, engineering and supply chains eBusiness for Enterprise Integration – across construction, repair, logistics activities and suppliers Benefit: Cuts labor and cycle time of daily processes by 60% Common Parts Catalog – Enterprise standard, shared parts database Benefit: facilitates standardization & IPDE initiatives; fewer parts to procure, inspect, certify, track, warehouse … IT Interoperability – Integrating shipyard IT systems (CAD, CAM, Parts …) across firms & functions Benefit: Reduces costs & acquisition cycle time, improves 1 st time quality, enables outsourcing

30 April Product Data Initiatives Alignment Full Ship Modeling & Simulation LEAPS CPC Navy ERP Navy Initiative NSRP Initiative NPDI MAINTAIN Planning Yard SPARS ISE

30 April NSRP Project – Improved Methods for the Generation of Full-Ship Simulation/Analysis Models 2 NSRP Project – Improved Methods for the Generation of Full-Ship Simulation/Analysis Models 2 The NSRP Modeling and Simulation Workshop The NSRP Modeling and Simulation Project will hold a one day workshop in association with the DoD CREATE Project covering Ship Modeling and Simulation efforts. June 10, 2009

30 April Interoperability Problem Communication between diverse computer systems is a big challenge in today’s environment: –As CAD/CAE/CAM systems have proliferated in the U.S. shipyards, interoperability among these systems has become a major issue –Interoperability is an issue within a shipyard as well as between partnering yards and with the Customer This situation is further aggravated because: –Most recent and future ship design and build contracts involve multiple shipyards –Length of time to design and build a ship often exceeds the life span of current computer systems, driving the need to move existing data to new computer systems –Requirements for life cycle support of the ship will far exceed the life span of current computer systems, again driving the need to move existing data to new computer systems

30 April ISE Interoperability Solution The Integrated Shipbuilding Environment Consortium (ISEC) is attacking the interoperability problem on a broad front involving numerous standards, tools, and organizations including: –XML (Extensible Markup Language) –STEP (Standard for Exchange of Product Model Data) –isetools.org Website Demonstrate that improved interoperability will achieve cost reductions in Navy and commercial shipbuilding processes across shipyards and across the design/build/support life cycle Leverage past work by deploying information technology systems that meet the shipbuilder’s interoperability requirements Support other NSRP initiatives for better integration among shipbuilding enterprise functions

30 April ISE Interoperability Solution Drive development of shipbuilding product data standards (e.g. STEP, PLIB) –Construct a single Shipbuilding Information Model –Demonstrate and educate U.S. shipbuilding community Flexibility is critical –Allow shipyards to transform their data to/from common information model –Enable each enterprise to use its own tool set rather than all move to the same tools Develop and demonstrate tools that are low cost –Can be selectively used by shipyards to support interoperability –Capitalize on XML and related Internet technologies

30 April ISE Interoperability Solution The ISE Projects have helped develop standards, defined the approach, and implemented a solution to ensure information interoperability The goal of current and future efforts is to make these techniques and tools available in production to all U.S. shipyards –STEP Shipbuilding Translators –XML Tools –Common Parts Catalog Interfaces

30 April XML + STEP XML = Industry Standard Container for Data STEP = ISO Standard Language for Data Data Company A Standards Virtual Ship part(s) Company B Transactions of Data Packaged in Standards XSLT - map data to another XML schema XML : Accepted format/schema method Web-enabling STEP : Standards for data expression Standards for geometric exchange Data is independent of IT infrastructure, but standards are required to reflect system needs for exchange

30 April ISE Architecture Accessible to large and small shipyards –Only system dependency is Web infrastructure –Utilizes open standards Innovative integration of STEP and XML technologies –Supports sharing of geometry & geometric product models Permissive (mediation) architecture –Lets each enterprise choose its own tool set Amenable with CAD platforms used by U.S. shipbuilders ISE architecture represents an innovative, practical solution to the information interoperability challenge

30 April ISE Tools Tools developed by the ISE Project are made available on the Web at: These include: –Formal information requirements published Ship Piping Ship Structures Ship HVAC CPC Interfaces Electrical –Translator generators for custom representations –XML schema generators ISO ed 2 –Mediators (i.e. between STEP Part 21 and STEP Part 28) –Automated test frameworks for conformance testing

30 April Information Interoperability Roadmap ISO AP 239:2004

30 April ISO STEP NAVSEA Ship Program Standard Approved Standard In Work NSRP ISE Prototype Translators Testing Framework Information Model Phases:Requirements Definition Information Interoperability Specification Production Deployment ISE Information Model Methodology Contractual Specification Deployment, Integration, Testing Technology Business Decisions Standard in Work

30 April ISE Interoperability Focus Areas The Integrated Shipbuilding Environment Consortium (ISEC) is led by U.S. shipbuilders along with commercial software vendors, and information technologists This team has been together for nine years and has developed much of the infrastructure and architecture necessary for shipbuilding information interoperability NSRP funded program focused on interoperability using international standards – ISO STEP, PLCS, S1000D, W3C ISE-6ISE-5 ISE-4 ISE-3ISE-2ISE-1 Ship Arrangements Steel Processing Engineering Analysis Electrical Electrotechnical Product Life Cycle Support Requirements HVAC CPC Interfaces Structures Piping

30 April Interoperability: Current Related Efforts ISE-6(Integrated Shipbuilding Environment) –Deploy information technology systems that meet the shipbuilder’s interoperability requirements in the area of life cycle support and post-delivery operations NPDI(Navy Product Data Initiative) –To specify the requirements for and drive the implementation of product data systems based on an open architecture having suitable functionality and enterprise- wide interoperability to support affordable Navy ship design, construction and service life support –Initial version of the IPDE Specification has been written and delivered to the Navy for review and comment SCIM(Ship Common Information Model) –SCIM will codify the models developed and prototyped by the ISE Project under NSRP over the past nine years –It will be a separate document from the IPDE Specification being produced by the NPDI Project, but it will be referenced by that IPDE Specification –Initial version of the SCIM has not yet been completed Six of fifteen proposed chapters have been developed One of the remaining chapters deals with Product Life Cycle Support and will be based on the results of the ISE-6 Project

30 April ISE Team Participants

30 April ISE Test Ship – TWR841 This ship is used to locate and retrieve torpedoes and missile drones. It has a maximum payload capacity of 42 long tons which includes the deck cargo plus full liquids, full complement, and normal stores. This ship was selected because it is in-service, has a complete set of drawings available for distribution, and is: Approved for Public Release: Distribution Unlimited.

30 April ISE-2 Demonstration (April 2003) AP216: Ship Moulded Forms AP218: Ship Structure AP227: Piping

30 April ISE-3 Demonstration (October 2004) AP227: HVAC

30 April Washington DC Integrated Shipbuilding Environment HVAC Demonstration

30 April ISE-4 Demonstration (April 2006) TWR 3D Product Model Geometry Engine Room ISE-4: Ship Arrangements Engineering Analysis Electrical Design Steel Processing

30 April Systems Involved in the ISE-4 Interoperability Demo Initial DesignDetail DesignManufacturingLifecycle Support TRIBON ISDP LEAPS Engineering FEA Analysis FORAN Preliminary Arrangement Feed Mfg from ISDP Modify Arrangement Partnership Yard INTELLISHIP Repair Shipyard Suggest Design Changes Submit Design Approval Final Product Model Delivered to Navy GDEBNGSS Steel Processing Navy Analysis Programs Engineering Analysis B B C = Mediators Required Concept & Preliminary Design Detail Design Sener Intergraph EBC ADAPT Key: Atlantec = Demonstrated= Not Demonstrated Electrical KSS/KM Navy Response Center AP215 P21 AP215 P28 AP215 P28 AP218 P28 AP218 P28 AP209 P21 AP215 P21 A AP212 P28 AP212 P21 Submit Design For Approval Arrangements

30 April Compartment NameCompt #Volume (m^3) Air Handling Room1-8-3-Q Ballast Tank # V Ballast Tank # V Ballast Tank # V Ballast Tank # F Bosuns Stores2-2-0-A Bow Thruster2-5-0-Q Chain Locker2-2-0-Q CO State Room1-5-2-L CPO State Room1-5-1-L Crews Berthing2-6-0-L Deck Gear A Electrical Room1-7-1-Q Engine Room E Engine Room Exhaust Trunk Q Engine Room Supply Trunk Q Forepeak2-0-0-V Fuel Oil Tank # F Fuel Oil Tank # F Fuel Oil Tank # F Fuel Oil Tank # F Fuel Oil Tank # F Galley and Mess Area1-9-0-L Hold Head L Hold Passageway2-8-0-L Lazarette Q Lazarette Passageway Q Linen Locker2-9-1-A Lube Oil Tank F Main Deck Head1-7-2-L Main Deck Passageway1-7-0-L Observers Berthing L Pilot House C Pilot House Passageway1-9-1-L Potable Water Tank # W Potable Water Tank # W Provisions Storeroom A Pump Room Q Pump Room Passageway Q Pump Room Supply Trunk Q Void2-2-0-V Waste Oil Tank F TWR Compartment Overview

30 April ISE-5 Demonstration (February 2007) DXF or IGES (2D CAD) DXF or IGES (2D CAD) AP227 (3D Cableways) Design Agent 1 Design Agent 3 Design Agent 2 AP214 (3D CAD) AP212 (ET Data) AP212 (ET Data) XML SVG Electrotechnical Data and Document Interoperability Concept & Preliminary Design Production Design Refit & Upgrade Design

30 April ISE Interoperability Progression Interoperability solutions must apply to the entire life cycle Initial efforts focused on Design issues –Transfer between multiple Design Agents –Exchange between Design and Construction Agents –Transfer of Product Models from Design Agent to Customer Later stages focused on Manufacturing –ISE efforts addressed unique Manufacturing issues involved in transfer of Models for Steel Processing, HVAC, and Piping Focus has now shifted to Life Cycle processes (such as Maintenance and Repair) –Involves different issues and requires different information

30 April Issues Arising for Data Transfers Throughout Life Cycle The information exchanged to support Maintenance and Repair is different from Design and Construction –As-built conditions of the ship needed –Changes made during ship’s service must be reflected in the product model –Updates to Catalogs for replacement parts must be available Ships have long life span (up to 50 years) –Ship will likely outlive CAD systems used during Design –Even computer hardware and storage media will not survive for life of ship Change management is a major cost driver throughout the life of the ship and should be addressed by any interoperability solution

30 April Majority of the total cost of ownership of a Navy ship accrues after the ship has been delivered Life cycle support; repair, maintenance and overhaul; ships’ operations; testing and training are all information intensive processes The Navy has steadily moved toward more modern systems and technologies to cope with the burgeoning information needs, but technology has evolved faster than the deployed solutions Issues Arising for Data Transfers Throughout Life Cycle

30 April STEP for Archiving and Sustainability of Data Long Term Retention of Product Model Data is a Problem –Shipbuilding Products in general have life spans that far exceed the span of the CAD, CAE, or PDM systems that create the Product Models –Accurate Product Model Data is needed throughout the Life Cycle of the Product for Repairs, Overhauls, In-Service Modifications, etc. –Data must be retained for the life of the product which can be up to 50 years –On the other hand, the life of a CAD, CAE, or PDM system used to design the product is often less than 10 years How will you read your product model data in 5 years? 10? 15?

30 April Data Archiving: STEP Standard Formats Preserve Data for Future Use Regardless of changes to Hardware, OS or CAD System STEP is a Potential Solution Years Convert X to STEP Convert A to STEP Convert B to STEP Convert C to STEP System X System A System B System C System N Convert to long- time archiving format (STEP) once Years Convert X to A Convert A to B Convert B to C Convert C to N System X System A System B System C System N Preserving data for future use without standardsrequires you to convert all your data each time you modify Hardware, OS or CAD system

30 April ISE-6 Project Two year project, funded by National Shipbuilding Research Program (NSRP) Coordinate the use of the PLCS (STEP AP239), S1000D, and ISE standards to enable these standards to integrate more closely with the shipyard’s product model to enable product life cycle interoperability Phase 1 - April 2007 through March 2008 –Integrated PLCS with ISE information models –Mapped core Navy ship configuration and logistics data to PLCS –Demonstrated an exchange to reuse configuration and logistics data across Integrated Data Environments (IDE) Phase 2 - April 2008 through June 2009 –Integrate S1000D capabilities with PLCS and ISE information models –Manage change by linking S1000D modules to design structure –Final Demonstration on April 30, 2009

30 April ISE-6 Phase 1: Functional Scenario 34 Design (3D CAD Data) Shipyard A IDE (Design & Logistics) Shipyard B IDE (Design, Logistics, & CAD ) Navy IDE (Design & Analysis) Navy Depot (Design, Logistics, Support) Data Prep & QA (Design, Logistics, & CAD)

30 April AIM/SIR LPD 17 IPDE Software Teamcenter DDG 1000 IDE Software episTree Knowledge Management Software LEAPS Navy Design & Analysis Repository CATIA (V4 AEC) ShipConstructor 2006 ShipConstructor 2008 AP 227 AP 239 AP 214 Design Navy IDE Shipyard A-IDE Shipyard B-IDE 3D Design Design & Logistics AP 214 AP 239 Design & Logistics, including 3D Design AP 239 AP239/PLCS (ISE-6) Phase 1 Scenario Demo: April 2, 2008 in Washington, DC

30 April Standards for Life Cycle Support Standards for Design, Engineering, Production (STEP AP 212, 215, 216, 218, 227ed2 ) (ISE information models) International ISO Standards Focus of ISE Projects since 1999 Standard for Technical Publications (S1000D) ISE-6 Phase 2 International Standard Driven by Aerospace, Defense Emerging DoD IETM Standard Standard for Logistics & Life Cycle Support (PLCS) (STEP AP 239) ISE-6 Phase 1 International ISO Standard Driven by Aerospace and Defense ISE-6 has Prototyped Use for Shipbuilding Use of these standards is the focus of today’s demonstration

30 April ISE-6 Phase 2 Phase 2 of the ISE-6 Project runs from April 2008 through June 2009 S1000D is an international specification for the procurement and production of technical publications –It is an SGML/XML standard for preparing, managing, and using equipment maintenance and operations information The Navy has been working toward a new-generation of interactive technical manuals for deployment on-board ship –There has been pressure to move to the topic- based approach embodied in the S1000D standard but, to date, this migration has been only partially accomplished This phase of ISE-6 has developed use cases for shipboard interactive technical documents that take advantage of the new capabilities of the S1000D standard

30 April S1000D Use Cases #Use Case Title 24.Develop S1000D Technical Publications and Training Modules 25.Distribute S1000D Technical Publications and Training Modules 26.Manage Changes to Technical Publications and Training Modules Although one can go to many different levels of detail, and can easily divide these Use Cases into several discrete operations, it was felt that these three Use Cases provide a consistent and discrete level of consideration for the ISE-6 efforts. These Use Cases will be the basis of the context schemas and exchanges to be developed during Phase 2 of the ISE-6 Project. The ISE-6 Use Cases focus on the usage and aggregation of data modules. The data module content is assumed to be authored correctly for the purposes intended and is not addressed by the Use Cases. While the S1000D Standard has been adopted for technical documentation, including technical manuals, the training community has adopted an analogous standard for e-learning, the Sharable Content Object Reference Model (SCORM). Both standards are modular, allowing the reuse of content. An S1000D Data Module (DM) packages content within an XML file. A SCORM Sharable Content Object (SCO) packages learning content. SCORM is a reference model used to aggregate and sequence SCOs, but does not address how learning content is arranged within an SCO.

30 April S1000D Use Cases Mapped to IDEF0 Models Use Cases for Development of Technical Data IDEF0 Diagram - Develop S1000DTechnical Publications and Training Modules All S1000D Use Cases can be mapped to Activity Models in IDEF0

30 April Product Life Cycle Support (PLCS) 40 Project to Develop AP239 as an ISO Standard for PLCS Copyright Eurostep Group AB

30 April The Key Business Problem Copyright Eurostep Group AB Feedback Copyright Eurostep Group AB

30 April Business Drivers Reduced Cost of Ownership Users of products are seeking improved availability, reliability, maintainability, and lower cost of ownership Exploit Investment in Product Data Users of information systems want more open platforms to reduce IT costs and ensure longevity in use of information Digital Product Data has become a valuable business asset For shipyards, the investment in Product Data has not yet been leveraged for life cycle support Copyright Eurostep Group AB

30 April ISO Product Life Cycle Support (PLCS) Change Management Product Structure Requirements Management Schedule Activities Organizations Property Classification Approvals, Security, Status Maintenance Support Tasks APSI Support History Messaging PLCS PLCS provides an integrated data model with a scope that is a holistic view encompassing the entire product life cycle ISE-6 Lifecycle community needs to access information defined during acquisition ● Acquisition community can also benefit from the use of PLCS to exchange integrated design and logistics information

30 April Copyright Eurostep Group AB Typical complex systems environment – point to point integration

30 April Product Life Cycle Support (PLCS) 45 Copyright Eurostep Group AB

30 April PLCS Vision 10/20/ 2008Intergraph Proprietary and Confidential Ship Acquisition Programs Ship Life Cycle Support Design Data Ship Design Parts Manufacturing Ship Configuration Logistics Data Program Data Documents Change Mgmt Ship Program A Integrated Data Environment (IDE) Ship Design Parts Manufacturing Ship Configuration Logistics Data Program Data DocumentsDesign Data Change Mgmt Ship Program B Integrated Data Environment (IDE) Shipyard Legacy Logistics & Support Systems Navy Legacy Logistics & Support Systems Regional Maintenance Centers Change Management Product Structure Requirements Management ScheduleActivities Organizations Property Classification Approvals, Security, Status Maintenance Support Tasks APSI Support History Messaging PLCS Marine Corps Legacy Logistics & Support Systems NATO Legacy Logistics & Support Systems

30 April Updated Requirements ISE-6 Phase 2 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

30 April Current Process for Updating Technical Data Radar Navy Legacy Systems Navy Tech Manuals & Deliverables Embedded Tech Data Training Radar Tech Data Radar System is designed and produced Contractor and Navy agree on LRU breakdown Logistics Organization builds Tech Manual ­ Primary inputs are Drawings and Parts List ­ Maintenance Engineering defines maintenance data and procedures Documents delivered to Navy Navy Logistics Organization ­ Builds Navy Tech Manual ­ Generates data for other Navy Logistics systems from documents Goal is to Control Costs through Integration and Automation

30 April Logistics - LRU Breakdown Navy Logistics -LRU Breakdown CDMD-OA PMS / MRC Contractor / OEM Vendor Tech Man Training Drawings Specs Docs Diagrams Navy System Design -System def -Functional Prop -Connectivity System Analysis Requirements Detailed Design (3D CAD) -Packaging MRP/ERP -Parts -Purchasing PDM -Documents  Drawings -Product Structure  Parts List Manufacturing Tools Design & Production Technical Data Maintenance Engineering - Maintenance Data & Procedures - Tech Man - Training - R & M - Navy Tech Man - Navy Training Current Contractor Delivery Process

30 April Sequential Logistics data is manually generated from design / production data Document-based deliverables –Documents are expensive to generate Progress is hard to track Content cannot be validated automatically Same technical data is formatted several times –Navy needs data and documents Technical data must be extracted from documents Changes must be reverse engineered from documents Current Delivery Process Problems

30 April To-be Delivery Process & Vision Integrated Environment for Technical Data –Shared collaborative environment between Navy and Contractor Involves Contractor’s Logistics Organization Does not affect Design and Production –Incremental Data Definition Data is defined once, used many times Data initially generated by contractor –Automate data capture from design / production Data enhanced / augmented by Navy Logistics Data extracted to –Build Tech Manual –Populate CDMD-OA –Generate PMS / MRC Changes can be tracked jointly Can automatically validate data population at any stage

30 April To-be Delivery Process & Vision Logistics Navy Logistics CDMD-OA PMS / MRC Contractor / OEM VendorNavy System Design -System def -Functional Prop -Connectivity System Analysis Requirements Detailed Design (3D CAD) -Packaging MRP/ERP -Parts -Purchasing PDM -Documents  Drawings -Product Structure  Parts List Manufacturing Tools Design & Production Technical Data Integrated Environment - LRU breakdown Maintenance Engineering - Tech Man - Training - R & M - Maintenance Data & Procedures - Navy Data - Navy Tech Man - Navy Training - Technical Data

30 April To-be Process & Vision: Updates Logistics Navy Logistics Contractor / OEM VendorNavy System Design -System def -Functional Prop -Connectivity System Analysis Requirements Detailed Design (3D CAD) -Packaging MRP/ERP -Parts -Purchasing PDM -Documents  Drawings -Product Structure  Parts List Manufacturing Tools Design & Production Technical Data Integrated Environment - LRU breakdown Maintenance Engineering - Tech Man - Training - R & M - Maintenance Data & Procedures - Navy Data - Navy Tech Man - Navy Training - Technical Data Changes CDMD-OA PMS / MRC Changes

30 April Technical Data –Functional properties –Physical properties –Parts list –Diagrams / Drawings –Tech Manual –Training Material –R&M –Input for Navy logistics systems –Maintenance data –Maintenance procedures –Troubleshooting procedures Configuration –Variants / models / revisions –Baseline configuration –Hull applicability by serial numbers –Packing / kitting / shipping Contractual –Documentation delivery –CDRL –Correspondence Potential Scope of Environment

30 April Win - Win Benefits both Contractor AND Navy –Avoids unnecessary document costs –No new data requirements –Automate data capture from design / production –Faster and cheaper logistics product development Define once, use many times Changes propagated automatically –Higher quality logistics products Automated validation Reduce number of review cycles –Reduce risk Better completion tracking Can gather completion / progress metrics –Ability to integrate with Navy Logistics Systems –Manage multiple versions / variants Contractor –Reduce cost of logistics deliverables –Increase money available for Engineering –Reduce cost of updates in life cycle Navy –Lower cost for logistics deliverables –Lower cost to process deliverables –Much lower cost for updates in life cycle

30 April PLCS/S1000D is the right choice for the U.S. Navy and Shipbuilding Industry PLCS (ISO ) and S1000D Standards have been used successfully by: –Norwegian Frigate Program –Air Force Joint Strike Fighter (JSF) –Army TACOM ISE-6 Project is prototyping these tools and standards for current Navy systems The right solution for today’s IPDE environments in the Navy and the Shipyards

30 April Summary Computer system interoperability in U.S. shipyards is a major issue facing shipbuilders and the Navy Enabling interoperability throughout the ship’s life cycle is a major challenge in achieving the goals of NSRP –ISE Project is addressing these goals by developing and prototyping the tools necessary to enable interoperability ISE-6 tasks support the development of future integrated technical data scenarios