1. 27 Apr ‘06 1 Integrated Shipbuilding Environment (ISE) ISE4 Project Demonstration April 27, 2006

2. 27 Apr ‘06 2 ISE4 Participants

3. 27 Apr ‘06 3 Presentation Agenda Interoperability Demo Scenario Ship Arrangements Exchanges using AP215 and AP216 –Initial Design in TRIBON –Transfer from TRIBON to LEAPS –Modifications in FORAN –Transfer from FORAN to LEAPS (and ISDP) –Transfer from ISDP to Intelliship Electrical Demonstration using AP212 Engineering Analysis Exchanges using AP218 and AP209 Steel Processing Exchanges using AP218

4. 27 Apr ‘06 4 Interoperability Demo Scenario During the demonstrations you are about to witness, we will be exchanging product model data from several disciplines between multiple computer systems The scenarios are not necessarily meant to be realistic, but more to convey the types of exchanges and requirements that can be satisfied by the tools developed in the ISE Project Data to be exchanged will include product model data used for Ship Arrangements, Electrical, Engineering Analysis, and Steel Processing The data will be representative of product models that could be exchanged at any phase of the Life Cycle, from Concept Design through Detail Design through Manufacturing, or continuing through Repair and Overhaul

5. 27 Apr ‘06 5 Description of Exchange Scenarios The models exchanged represent the TWR841 –Torpedo Weapons Retriever ship with data “Approved for Public Release – Distribution Unlimited” –Product Models will capture TWR Compartmentation and details of the TWR Engine Room –These transfers simulate a situation where STEP is in place to enable Shipyards to interoperate smoothly Ship Arrangements exchanges represent –Exchanges to go from Concept Design to Detail Design at two different Shipyards –Models developed will be analyzed by Customer and changes will be suggested –Partnering Shipyards will complete the Design and feed data to other applications for analysis, manufacturing, repair, and lifecycle support Electrical Analysis is done on TWR systems during Preliminary Design New requirements (such as a request from an outside agency, e.g. Homeland Security) can necessitate model transfer to additional software packages for Engineering Analysis Steel Processing scenario shows how design data for a plate can be modified in STEP before being sent to two possible construction yards with different requirements (NGSS and EB)

6. 27 Apr ‘06 6 Lifecycle Phases for Demo Scenario Evolving Ship Design from Concept to Maturity Initial DesignDetail DesignManufacturingLifecycle Support Time

7. 27 Apr ‘06 7 Demo Scenarios for the Four ISE4 Tasks Four Tasks and Demonstrations Initial Design Detail Design Manufacturing Lifecycle Support Engineering FEA Analysis Concept & Preliminary Design Stage Detail Design Stage Steel Processing Electrical Arrangements

8. 27 Apr ‘06 8 Different Representations for Data Part 21 vs. Part 28 –Part 21 is the traditional STEP physical file format –Part 28 is an XML representation of STEP data ARM vs. AIM –ARM (Application Reference Model) objects are in application area terminology e.g. “Ship” or “Plate” –AIM (Application Interpreted Model) objects are in generic terminology e.g. “Product” or “Product Representation” ISE Project is developing mediation tools to enable a sender and receiver to communicate successfully no matter which format they select for their particular data representations –The ensuing Demos will involve the transfer of models using both of these formats

9. 27 Apr ‘06 9 Approach / Background This Approach Employs the NSRP ISE Model for Information Interoperability Translator = Modify Data between CAD System Proprietary Format and STEP Mediator = Change Data Format between various STEP Representations Application A Translator Application B Translator Data ISO STEP Standard Information Model XML Express Part21Part28 Mediator

10. 27 Apr ‘06 10 Systems Involved in the Interoperability Demo Initial DesignDetail DesignManufacturing Lifecycle 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

11. 27 Apr ‘06 11 Integrated Shipbuilding Environment Washington DC April 27, 2006 Arrangements Demonstration

12. 27 Apr ‘06 12 Ship Arrangements Demo Details Initial DesignDetail DesignManufacturing Lifecycle Support TRIBON ISDP LEAPS FORAN Preliminary Arrangement Modify Arrangement Partnership Yard INTELLISHIP Repair Shipyard Suggest Design Changes Submit Design Approval Final Product Model Delivered to Navy B B = Mediators Required Concept & Preliminary Design Detail Design Sener Intergraph Key: Atlantec = Demonstrated= Not Demonstrated Navy Response Center AP215 P21 AP215 P28 AP215 P28 AP215 P21 Submit Design For Approval Arrangements Navy Analysis Programs Engineering Analysis

13. 27 Apr ‘06 13 Overview – Tribon Translator Developed STEP AP215 Translator for Tribon Initial Design Translator Produces file in Part 28 ARM format defined by EB Worked with EB to test File Schema and Mediators Atlantec Enterprise Solutions

14. 27 Apr ‘06 14 Demo Scenario – Tribon Translator Tribon Initial Design Atlantec AP215 Translator Tribon Output Files STEP / XML AP 215 File Mediators STEP AP 215 File FORAN LEAPS Translation Process – High Level

15. 27 Apr ‘06 15 As-Is Process – Tribon Translator Vendor Lock-in  Ship designers and builders stay with one vendor to be able to transfer data between various design and manufacturing software packages System-to-System Bridges  Custom software can be created to link two software packages  These solutions are fragile, as they must be updated with every version change in either software package  Usefulness is limited to the two systems connected Manual Reentry  Ship designers and builders can manually reenter data in a second system  This process is expensive, labor-intensive, and error prone Initial Design Integration Options: Currently Available

16. 27 Apr ‘06 16 ISE Process – Tribon Translator No Vendor Lock-in  Using STEP standards and translators ship designers and shipbuilders can move data between software packages provided by different vendors No System-to-System Links  Using STEP standards and translators there is no need to build system-to- system bridge software.  A translator bridges each software package to the standard  All software systems bridged to the standard are interoperable No Manual Reentry  With automated transfers via the standard, manual reentry can be avoided Initial Design Integration Options: With STEP and ISE Translators

17. 27 Apr ‘06 17 Overview – LEAPS AP215 Translators Project accomplishments: Developed STEP AP215 Import and Export Translators for Navy LEAPS system. PDSC is ISO Editor of STEP AP215. Provided AP215 documents, ARM/AIM EXPRESS schemas, and training/consulting to ISE team. Developed and maintained ISE AP215 Implementation Agreements and Issues Logs for ISE Team. Submitted 20 SEDS (Standard Enhancement and Discrepancy System) to ISO for inclusion in next version of ISO AP215 standard. Product Data Services Corporation (PDSC) for NSWC Carderock Division

18. 27 Apr ‘06 18 Overview – LEAPS AP215 Translators LEAPS – Leading Edge Application for Prototyping Systems Central Navy Repository for Ship design and analysis. Developed and supported by NSWC Carderock Division. Common database for 3D Product Model Data and Analysis results for new Ship Acquisition. Direct translators from ASSET for initial arrangements and to NAVSEA analysis software for performance and vulnerability assessments.

19. 27 Apr ‘06 19 Overview – LEAPS AP215 Translators LEAPS – Leading Edge Application for Prototyping Systems

20. 27 Apr ‘06 20 As-Is Process - LEAPS AP215 Translators LEAPS – Leading Edge Application for Prototyping Systems Existing LEAPS geometry data exchange capability for IGES surfaces developed by NSWC Carderock Division. Previous STEP AP216 (surfaces) import and export translator project completed in 2003-04 by NSWCCD, PDSC, and Atlantec under Navy e-Business Office funding.

21. 27 Apr ‘06 21 ISE Process - LEAPS AP215 Translators ISE4 project added STEP AP215 import and export translators for LEAPS.

22. 27 Apr ‘06 22 Sample Processes-(LEAPS-CBD) GRIDGEN CFX AUTOCAD AutoCAD LEAPS Product Model Generic Class Structure Product Model Schema –NAVSEA Ship Focus Object Model Product Model Data DesignProduct Model IRENE RTS TSSM SMP ASAP/SVM CONTAM EXCEL-COST T T T T T T T T LEAPS/ Editor ASSET SBAAT T T Initialize Federates T Logged Fed’n Data T PRO/E CATIA T STEP/IGES T T T UG T T LEAPS/ Editor STEP/IGES CFX GRIDGEN CONTAM Analysis Developed and implemented by JS CBD FY02 & FY03 Virtual Mockup Presentation Mgr DOORS Initialize Initialize Federates

23. 27 Apr ‘06 23 LEAPS Activity VisMockup IRENE EXCEL TSSM SMP SVM/ASAP EMENG SDWE GENERAL LEAPS Product Model Generic Class Structure Product Model Schema –NAVSEA Ship Focus Object Model Product Model Data T T T T T T T T LEAPS Product Model Presentation Mgr RTS ASSET Surface ASSET Sub HLA Federate(s) T CAD FORAN TRIBON T STEP(214) IGES T T T IntellShip T CFX RTC BAM GMULT/GCPL T MultihullArrange LEAPSEditor In DevelopmentExisting Beta Code Other STEP/IGES T T SHIP AP’s STEP(216) STEP(215) STEP(218) STEP(227) T Capture HLA Sim Data SHIPIR CONTAM FKS DOORS S3D VERES PlannedD SWPE

24. 27 Apr ‘06 24 Demo Scenario – FORAN Translator Detail Design in FORAN ISDP used by Partnering Shipyard LEAPS for Customer Review and Approval Preliminary Design done in TRIBON has been transferred to LEAPS for Navy review and suggestions for design changes are forwarded to shipyard using FORAN who will perform Detail Design SENER AP215 Translator STEP AP 215 File

25. 27 Apr ‘06 25 SENER - FORAN FORAN Ship Arrangements Detailed Design Selective STEP Export to LEAPS Spaces Deck zones Zones ( P21 AP215-AIM STEP FILE) Decks and Bulkheads Details List of Ship Spaces Hull Forms FORAN – ISE4 AP215 STEP Translator FORAN – ISE4 Import STEP Translator TRIBON - LEAPS AP215 – SHIP ARRANGEMENTS

26. 27 Apr ‘06 26 Demo Scenario - LEAPS AP215 Import Part21 file from FORAN

27. 27 Apr ‘06 27 Demo Scenario - LEAPS AP215 Import Imported Product Model Data in LEAPS

28. 27 Apr ‘06 28 Overview – Transfer to Life Cycle Support Transfer construction product model to Life Cycle Support for –Engineering support Onboard applications Distance support Maintenance aids Analysis tools –Decision support / simulation –Logistics support Typical deliverables are drawings / documents –Must be re-converted to electronic data –Manual, labor intensive, incomplete process –Integrated Product Model often lost ISE information models designed to interoperate and preserve integrated product model –Supports automated, complete process

29. 27 Apr ‘06 29 As-Is Process – Transfer to Life Cycle Support Life Cycle Support System Integrated Construction Product Model Neutral File Geometry (IGES, STEP, ACIS, DXF) Or Drawings C&A Drawings Equipment Arrangement Drawings Structural Drawings Molded Form Modeler Arrangements Modeler Structural Modeler Equipment Modeler Manual, labor intensive & often incomplete process

30. 27 Apr ‘06 30 ISE Process – Transfer to Life Cycle Support Life Cycle Support System Integrated Construction Product Model AP 216 Molded Form Data AP 215 Arrangements Data AP 218 Structural Data AP 227 Equipment Data Highly automated, integrated, complete process ISE Translators ISE Translators ISE Translators ISE Translators Integrated Life Cycle Product Model

31. 27 Apr ‘06 31 Demo Scenario– Transfer to Life Cycle Support Integrated Construction Product Model AP 216 Molded Form Data AP 218 Structural Data AP 227 Equipment Data ISE Translators ISE Translators ISE Translators ISE Translators Integrated Life Cycle Product Model ISDP: Integrated Ship Design & Production IntelliShip Previous exchange Compartments created using existing molded forms ISE exchanges interoperate & preserve product model AP 215 Arrangements Data

32. 27 Apr ‘06 32 Electrical Demo Details Initial DesignDetail DesignManufacturing Lifecycle Support ISDP Engineering FEA Analysis Preliminary Arrangement Modify Arrangement Repair Shipyard Steel Processing = Mediators Required Concept & Preliminary Design Intergraph Key:= Demonstrated= Not Demonstrated Electrical KSS/KM A AP212 P28 AP212 P21 Detail Design Arrangements

33. 27 Apr ‘06 33 Project Objectives  Exchange and ARCHIVE electrical shipbuilding data using STEP AP212 (developed by the auto industry).  Adopt XML to exchange STEP data.  Lay the groundwork to exchange data between CAD and knowledge-based software systems using STEP.  Leverage existing initiatives in the industry (STEP Part 21, STEP Part 28, STEP AP212, and the Navy XML repository).  Publish project results.

34. 27 Apr ‘06 34 Knowledge Systems Solutions Knowledge management products and expert system software Navy (SPAWAR) C4ISR Ship Shore Installation Design Tool (SSIDT) KSS KnowledgeManager Product to create user-defined knowledge bases Air Force (OC-ALC) SBIR Knowledge-based reverse engineering & automatic creation of 3D CAD models Navy (NAVSEA) SBIR Knowledge-based retention of shipbuilding expertise * ** Transition of NSRP STEP translator technology *

35. 27 Apr ‘06 35 Spiral Development Knowledge-based system  STEP XML AP212 TWR Lighting TWR Power Distribution System Spec Framework Design Single C4ISR Equipment Single C4ISR Circuit Full C4ISR System Generic Objects Design Configurator Integrated Prototype Component Design File Data Import Navy Air Force Commercial STEP – Data – Translator Full Engineering & Design Data Sets

36. 27 Apr ‘06 36 Knowledge Management Demonstration  TWR Power Distribution System  Collect data and information into a knowledge base  Perform calculations and design functions

37. 27 Apr ‘06 37 Component Design Framework Knowledge Based System Component Part Catalog Object Classes STEP.stp Files AP Schemas AP Schemas CAD Systems Mediators Design Configurator AP Schemas AP Schemas AP Schemas Design File Component Structure CDFComponent Structure Multiple AP’s & Schemas Auto-configured Objects Structured Design File KB CAD (future) CAD KB (future)

38. 27 Apr ‘06 38 Electrotechnical Results  Developed Component Design Framework for data translation and archival using STEP AP212.  Knowledge Management(knowledge & rules)  Engineering Data(results)  Created reusable STEP toolsets (mediator stylesheets) for DoN repository.  Tested AP212 with diverse electrotechnical test cases.  Demonstrated the joint use of STEP and XML with new programming resources.

39. 27 Apr ‘06 39 Electrotechnical Future –Continued joint service implementation and benefit. –ISE4 follow-on project Facilitates detailed engineering along with early conceptual electrical engineering. Integrates knowledge management with 2D and 3D CAD via STEP formatted files. –Automatically generate knowledge bases from existing CAD data elements.

40. 27 Apr ‘06 40 Engineering Analysis Demo Details Detailed Design Stage NGSS, Intergraph EBC Electrical Concept & Preliminary Design Engineering FEA Analysis XSLTs NGSS, Intergraph EBC ADAPT AP218 P28 AP209 P21 ISDP Steel Processing Initial DesignDetail DesignManufacturing Lifecycle Support Detail Design Arrangements

41. 27 Apr ‘06 41 Engineering Analysis Project Final Demonstration April 27, 2006 Washington, DC ISE-4 L = Left Screen

42. 27 Apr ‘06 42 Engineering Analysis Project Final Demonstration April 27, 2006 Washington, DC ISE-4 R= Right Screen Note: This was a simultaneous 2-screen demo; L = Left screen, R = Right screen.

43. 27 Apr ‘06 43 Participating Organizations: General Dynamics / Electric Boat – Task Lead Northrop Grumman Ship Systems Intergraph Corporation Engineering Analysis Task L

44. 27 Apr ‘06 44 Individual Participants: Burt Gischner Ron Wood Steve Gordon Denny Moore Ted Briggs Art Hundiak Tom Rando Heidi Preston Steve Skrabacz Engineering Analysis Task R

45. 27 Apr ‘06 45 Engineering Analysis Task Focus and Outline: Multiple ISO STEP Application Protocols (APs) –Primarily AP218 and AP209 Different file exchange formats –Traditional STEP Express and XML forms Leverage existing CAE software Demonstrations: Demo 1 - Accommodating different formats –Both Part21 (Express) and Part28 Ed. 2 (XML) –Using mediation (XSLT transformation) Demo 2 - Using parametric geometry –AP218 ‘Implicit’ and ‘Explicit’ Geometry –Creating explicit from implicit L

46. 27 Apr ‘06 46 Engineering Analysis Task Goals Task Goals and Objectives: Extend interoperability capabilities by employing both the newer shipbuilding APs and the other existing ISO STEP 10303 standards. Build on work accomplished under previous ISE projects and related efforts. Illustrate flexible use of both STEP Express and XML formats for exchange and mediation. Demonstrate TWR structural model exchange from AP218 to AP209 for use with various engineering finite element analysis software packages Leverage these methodologies for both future Product Lifecycle Management (PLM) and Long Term Data Retention (LTDR) efforts. L

47. 27 Apr ‘06 47 Interoperability Extend ISO 10303 Interoperability R

48. 27 Apr ‘06 48 The utility of the ISO STEP 10303-209 (AP209) for supporting interoperability and collaborative design (combining design geometry with detailed finite element analysis) has already been demonstrated in other venues (e.g. PDES). All of that collaboration has been based upon exchange of traditional STEP files encoded in Express (Part21). In this ISE-4 task we demonstrate extensions to that approach by integrating with STEP application protocols for ship structure (primarily AP218), and by employing more flexible collaboration and exchange scenarios using XML (Part28) encoded files. Engineering Analysis Approach PDES, Inc. R R

49. 27 Apr ‘06 49 Data ISO STEP Standard Information Model Express Part21Part28 The STEP Standards can be delivered (“wrapped”) in multiple forms, yet contain exactly the same data! ISO STEP 10303 Information Model = Core Content ISE Paradigm R

50. 27 Apr ‘06 50 XML Mediation Addresses CAx Interoperability among the Ship APs and with other Existing ISO STEP APs Ship CAD Tools STP (Express) Files XML Files XSLT Interoperability CAE Analysis Tools Engineering Analysis Approach / Progress CAx = CAD / CAE / CAM CAD  CAE CAD  CAM L

51. 27 Apr ‘06 51 Interoperability Backdrop Ship CAD Tools CAE Tools STP AP218AP209 XML R

52. 27 Apr ‘06 52 EA Demo 1 Roadmap Ship CAD Tools CAE Tools AP218 STP AP209 XML Shipyard CAD DS / CATIA Sener / FORAN Intergraph / ISDP Aveva / TRIBON Intergraph / IntelliShip Atlantec Step Tools AP218 ARM P28 AP218 AIM P21 AP209 AIM P21 EB / COMMANDS FESOL AP209 Existing CAE Structural Analysis MSC / PATRAN EB / ADAPT AP203 ? R

53. 27 Apr ‘06 53 Ship CAD Tools CAE Tools AP218 STP AP209 AIM P21 XML Mediation Tools AP218 AIM P28 AP209 AIM P28 AP209 ARM P28 XSLT P21-P28 XSLT NSRP Tools & Infrastructure Shipyard CAD DS / CATIA Sener / FORAN Intergraph / ISDP Aveva / TRIBON Intergraph / IntelliShip EB / COMMANDS FESOL AP209 Existing CAE Structural Analysis Atlantec Step Tools AP218 ARM P28 AP218 AIM P21 MSC / PATRAN EB / ADAPT AP203 EA Demo 1 Roadmap R

54. 27 Apr ‘06 54 Actual EA Demo 1 Flow DS / CATIA Ship CAD Tools Sener / FORAN Aveva / TRIBON MSC / PATRAN CAE Tools EB / COMMANDS FESOL AP209 STI AP218 ARM P28 AP218 AIM P21 Atlantec AP218 AP209 AIM P21 STP AP209 AP218 AIM P28 AP209 AIM P28 AP209 ARM P28 XSLT P21-P28 XSLT XML Mediation Intergraph / IntelliShip EB / ADAPT AP203 Intergraph / ISDP L

55. 27 Apr ‘06 55 XML STP NSRP ISE Demo GUI Mediator GUI R

56. 27 Apr ‘06 56 Multiple APs Different ISO STEP Application Protocols have differing file content. –AP218 (Ship Structures) vs. AP209 (Composite and Metallic Structural Design & Analysis). Several ship CAD vendors have selected XML (Part28) format for data exchange. Other CAx (CAD and CAE) vendors employ existing (older) ISO STEP exchange files in Express (Part21) format. AP203 (IS, 1994) has had more than a decade of usage. Along with AP214, they are the most commonly used APs. They are pervasively used for CAD geometry exchange in various industries today. How can that work? L

57. 27 Apr ‘06 57 AP218: Ship Structures L

58. 27 Apr ‘06 58 Configuration Control, Approvals Part, product definitions Finite element analysis model, controls, and results Configuration Control, Approvals Part, product definitions Finite element analysis model, controls, and results Analysis Discipline Product Definitions Finite Element Analysis –Model (Nodes, Elements, Properties,...) –Controls (Loads, Boundary Constraints,...) –Results (Displacements, Stresses,...) Analysis Report Analysis Discipline Product Definitions Finite Element Analysis –Model (Nodes, Elements, Properties,...) –Controls (Loads, Boundary Constraints,...) –Results (Displacements, Stresses,...) Analysis Report Design Discipline Product Definition Shape Representations Assemblies Design Discipline Product Definition Shape Representations Assemblies Information Shared Between Analysis & Design 3D Shape Representations Composite Constituents Material Specifications & Properties Part Definitions Information Shared Between Analysis & Design 3D Shape Representations Composite Constituents Material Specifications & Properties Part Definitions Composite Constituents Ply Boundaries, Surfaces Laminate Stacking Tables Reinforcement Orientation Composite Constituents Ply Boundaries, Surfaces Laminate Stacking Tables Reinforcement Orientation Material Specifications & Properties Composites Homogeneous (metallics) Material Specifications & Properties Composites Homogeneous (metallics) 3D Shape Representation AP202/203 Commonality Plus Composite Specific 3D Shapes –Advanced B-Representation –Faceted B-Representation –Manifold Surfaces With Topology –Wireframe & Surface without Topology –Wireframe Geometry with Topology –Composite Constituent Shape Representation 3D Shape Representation AP202/203 Commonality Plus Composite Specific 3D Shapes –Advanced B-Representation –Faceted B-Representation –Manifold Surfaces With Topology –Wireframe & Surface without Topology –Wireframe Geometry with Topology –Composite Constituent Shape Representation AP209: Composite & Metallic Structural Analysis & Related Design R

59. 27 Apr ‘06 59 ISO STEP 10303-218 (AP218) Ship Structures PDM Geometric Shape Representations Structural Parts and Features CAD Configuration Management, Class Approval General Characteristics, Hull Cross Section, Weight Description Production Design & Engineering Data Wireframe, Non_Manifold Surfaces, Brep Solids ISO STEP 10303-218 (AP218) “Explicit” Geometry“Implicit” Geometry (Parametric Geometry) L

60. 27 Apr ‘06 60 PDM Product Data Management PDM Info AP209 = CAD + CCS + CAE + FEM + FEA + PDM ISO STEP 10303-209 (AP209) One can use STEP APs with any one or more of these pieces. AP209 CAD Nominal CAD Geometry CAE Idealized CAE “Simulation-Specific” Geometry FEA Finite Element Analysis FEA Controls & Results FEM Finite Element Model(s) FEM CCS Composite Constituent Shape(s) CCS R

61. 27 Apr ‘06 61 AP218: Ship Structures Structural System Tank Structure L

62. 27 Apr ‘06 62 ISO STEP 10303-209 (AP209) R

63. 27 Apr ‘06 63 This NSRP ISE-4 Task Demo PDM First Step is to Create a Starting AP209 File with Explicit Geometric Shape Representations CAD Configuration Management, Class Approval Multiple STEP Application Protocols, Different Formats: XML (P28), Express (P21) AP218 P28 ARM PDM CAD AP209 P21 AIM XSLTs L

64. 27 Apr ‘06 64 PDM CAD PDM CAE FEM FEA AP209 The Next Demo Step is to Illustrate Analysis of the Exchanged Ship Structure Automated Creation of Idealized (Analysis) Geometry Construct the Finite Element Model(s) Solve, Display, and Interpret Analysis Results All These can be Merged into a Single “Growing” AP209 File or Repository for LTDR and PLM This NSRP ISE-4 Task Demo R

65. 27 Apr ‘06 65 Demos Employ TWR 3D Product Model Geometry Engine Room Engineering Analysis Task Demos EA Demo 1 L

66. 27 Apr ‘06 66 TWR Engine Room Looking Aft with Bulkhead at FR 16 Removed TWR Engine Room L

67. 27 Apr ‘06 67 Engines are Supported on Outboard and Inboard Girders TWR Engine Room Twin Caterpillar Diesel Propulsion Engines Fuel Oil Tank Top R

68. 27 Apr ‘06 68 Selected TWR Engine Room Solid Model Geometry with Port Caterpillar Engine Partial Design Change - Additional Brackets Inserted at FR 17 & FR 19 TWR Engine Room L

69. 27 Apr ‘06 69 Selected TWR Engine Room Solid Model Geometry with Port Caterpillar Engine TWR Engine Room R

70. 27 Apr ‘06 70 Port-Side Outboard Girder - Solid Model Geometry for Analysis TWR Engine Room Fuel Oil Tank & Engine Support Structure Shown in Intergraph’s ISDP Software Demo Geometry in ISDP L

71. 27 Apr ‘06 71 Demo 1 Engineering Analysis Task Demonstrations: Demo 1 - Accommodating different formats – Both Part21 (Express) and Part28 Ed. 2 (XML) – Using mediation (XSLT transformation) Demo 2 - Using parametric geometry – AP218 ‘Implicit’ and ‘Explicit’ Geometry – Creating explicit from implicit L

72. 27 Apr ‘06 72 Demo 1 Engineering Analysis Task Demonstrations: Demo 1 - Accommodating different formats – Both Part21 (Express) and Part28 Ed. 2 (XML) – Using mediation (XSLT transformation) Demo 2 - Using parametric geometry – AP218 ‘Implicit’ and ‘Explicit’ Geometry – Creating explicit from implicit R

73. 27 Apr ‘06 73 Port-Side Outboard Girder - Solid Model Geometry Outboard Girder – Mid-Surface Shell Geometry for Analysis Demo Geometry Nominal (CAD) and Idealized (Analysis) Geometry in EB’s ADAPT code L

74. 27 Apr ‘06 74 Outboard Girder – Shell Finite Element Analysis Model 6 “G” Simulated Shock Loads Applied in Vertical and Athwartship Directions Shock Stress FE Analysis Model L

75. 27 Apr ‘06 75 Analysis 2 Outboard Girder – With Intermediate Brackets at Frames 17, 18, and 19 Analysis 1 Outboard Girder – With Single Intermediate Bracket at Frame 18 For the Simulated Athwartship Shock Loading, Adding the Additional Brackets Results in an Eight-Fold Reduction in Von Mises Stress Level Shock Stress FE Analysis Result L

76. 27 Apr ‘06 76 Demo 2 Engineering Analysis Task Demonstrations: Demo 1 - Accommodating different formats – Both Part21 (Express) and Part28 Ed. 2 (XML) – Using mediation (XSLT transformation) Demo 2 - Using parametric geometry – AP218 ‘Implicit’ and ‘Explicit’ Geometry – Creating explicit from implicit R

77. 27 Apr ‘06 77 AP218 Implicit Geometry Various parts and features have parametric definitions in AP218 implicit geometry. T Bar Cross Section Drain Hole Cutout Bulbflat Cross Section Outward Round Corner Cutout L

78. 27 Apr ‘06 78 EA Demo 2 uses ESTEP AP218 Test Case 2 (based on TWR Frame 12) from the ISE-2 project as input. A prototype demonstrator code creates the explicit geometry, visualizes both, allows parametric change, an exports a STEP file. EA Demo 2 L

79. 27 Apr ‘06 79 Ship CAD Tools CAE Tools AP218 STP AP2XX AP203 AIM P21 DS / CATIA Sener / FORAN EB / COMMANDS FESOL AP209 Existing CAE Structural Analysis Step Tools AP218 AIM P21 MSC / PATRAN EB / ADAPT AP203 EA Demo 2 Roadmap STEP P21 Reader 3D Viewer Math Lib ‘OneStop’ AIM 218 Valid. Manifold Solid Generator ARM Lister Prototype Demonstrator AP218 Implicit to Explicit Geometry & Visualizer Implicit & Explicit Geometry Explicit Geometry Modular Java software Multiple project funding & support (EB, CNST, ISE) Implicit Geometry Explicit Geometry L

80. 27 Apr ‘06 80 EA Demo 2 Part Selector and Parameter Change Implicit (Parametric) Geometry Created Explicit Geometry L

81. 27 Apr ‘06 81 Demo 2 Engineering Analysis Task Demonstrations: Demo 1 - Accommodating different formats – Both Part21 (Express) and Part28 Ed. 2 (XML) – Using mediation (XSLT transformation) Demo 2 - Using parametric geometry – AP218 ‘Implicit’ and ‘Explicit’ Geometry – Creating explicit from implicit L

82. 27 Apr ‘06 82 60 Degree Bevel Outward Round Corner Circular Cutout Round Corner Rectangular Cutout Inward Round Corner Examples of AP218 Parametric Features EA Demo 2 – Implemented Features L

83. 27 Apr ‘06 83 AP218 Implicit Geometry Explicit Geometry AP203 1. Implicit  Explicit 2. Solid Import 3. Solid (TET) Meshing EA Demo 2A FEMAP Example L

84. 27 Apr ‘06 84 It is an innovative integration of STEP and XML technologies –Supports sharing of geometry & geometric product models It employs a permissive (mediation) architecture –Lets each enterprise choose its own tool set It is accessible to both large and small shipyards –The only system dependency is Web infrastructure –Utilizes open standards It can be incorporated into CAD platforms used by U.S. shipbuilders and into software from other collaborating vendors These demos show that the ISE approach and architecture do represent an innovative, practical solution to the information interoperability challenge. ISE Approach L

85. 27 Apr ‘06 85 Steel Processing Demo Details Initial DesignDetail DesignManufacturing Lifecycle Support ISDP Engineering FEA Analysis Preliminary Arrangement Feed Mfg from ISDP Modify Arrangement Partnership Yard Repair Shipyard GDEBNGSS Steel Processing = Mediators Required Concept & Preliminary Design Detail Design Intergraph Key:= Demonstrated= Not Demonstrated Electrical AP218 P28 Arrangements

86. 27 Apr ‘06 86 Agenda - Steel Processing Objectives/Proposed scope Manufacturing Rules Description/ Applicability Demonstration Scenario Benefits

87. 27 Apr ‘06 87 Objectives/Scope General Objectives (from NSRP SIP) –Decouple CAM from CAD –Enable efficient partnering among yards Project Scope –Create a framework for defining manufacturing rules/processes –Develop a Yard-Neutral Mfg Model (STEP AP218) Suitable for work package definition Make recommended enhancements to specification as required –Apply manufacturing rules to generate a manufacturing product model that respects the requirements of a given yard

88. 27 Apr ‘06 88 Usage Scenario Shipyard A Shop B STEP 218 Shipyard B Shop A STEP 218 CAD (Detailed Design) Steel Processor (Lofting/ Mfg Engineering) Steel Processor (Lofting/ Mfg Engineering) Mfg Rules

89. 27 Apr ‘06 89 Mfg Product Model Shell Plate Design CAD Develop Flat Plate Specialized Macro Add Excess Stock for Rolling Manufacturing Rule Adjust Size for Weld Shrinkage Manufacturing Rule Yard Processes and Assembly Plan Add Edge Prep & Punch-marking Source Process ManufacturingDesign

90. 27 Apr ‘06 90 Rules Application Data Creation –Creation of manufacturing data based on the input data and rules –Examples Feature definition (edge preps, added/removed mat’l) Annotation creation and positioning Process definition Data extractions for post-processing applications (reports, mfg aids, nesting) Data Verification –Check the data for conformance to a set of yard-specific processes, geometry correctness (e.g., closed parts), consistency, and produce-ability –Examples Data integrity (content, structure, associations) Geometry correctness Structural part relationships Correlation of processes applied to structural data

91. 27 Apr ‘06 91 Demonstration Example Deck Plates Bulkhead

92. 27 Apr ‘06 92 Yard-Specific Annotation Ex. Thickness Throw Indicator (Northrop Grumman Ship Systems) Thickness Throw Indicator (General Dynamics Electric Boat) Stiffener Marking Line

93. 27 Apr ‘06 93 Demonstration Scenario Northrop Grumman Avondale Shop B STEP 218 General Dynamics Electric Boat Shop A Launch Demo STEP 218 1 2 ISDP Steel Processor 1 Apply manufacturing rules for NG Avondale 2 Apply manufacturing rules for GD Electric Boat STEP 218 Mfg Rules STEP 218 Mfg Rules

94. 27 Apr ‘06 94 Benefits of Approach - Steel Processing Explicit definition and application of rules to structural data –Maintained separate from design/lofting systems –Streamline manufacturing product model creation and verification Evolution of ship structural standards –Use STEP specifications as the native import/export format and as a framework for the internal structure

95. 27 Apr ‘06 95 Recap of the 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 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 Navy Analysis Programs Engineering Analysis

96. 27 Apr ‘06 96 Availability of ISE Project Results ISE Project has: –Developed Information Models based on STEP –Created Mediator Tools –Verified that the above meet requirements of U.S. shipyards and work with currently available CAD tools –Published Implementors Agreements to enable others to use these tools effectively –Registered ISE Schemas with the DONXML Repository –Identified proposed changes/corrections to ISO STEP Standards –Created a Website to contain the relevant software tools, schemas, etc. as provided by the ISE Project www.isetools.org –JEN-X Mediator from EXPRESS to XML will be publicly available on Sourceforge and PDES, Inc. Websites

97. 27 Apr ‘06 97 Goal: Implement in Production The ISE Project has developed tools and demonstrated interoperability between shipyards in the areas of: –Structure –Piping –HVAC –Common Parts Catalog Interfaces –Ship Arrangements –Electrical –Engineering Analysis –Steel Processing The goal of current and future efforts is to make these techniques and tools available in production and to all U.S. shipyards –STEP Shipbuilding Translators –XML Tools –Common Parts Catalog Interfaces A Website has been established to contain the relevant software tools, schemas, etc. as provided by the ISE Project –www.isetools.org ISE2 ISE3 ISE4

98. 27 Apr ‘06 98 Continuing Efforts An ISE4 Follow-On Project was awarded for 2006: –Electrical: Finish task including addition of 3D information –Program Management: Continue support and involvement of ISO and DONXML activities An ISE Systems Technology Panel Project was awarded for 2006: –Steel Processing: Continue efforts with emphasis on STEP-NC Future Projects: Complete the Information Interoperability Roadmap –Goal is to turn all boxes “Blue” –ISE Project is providing tools to turn boxes from “Red” to “Yellow” and then to “Green” –Customer must invoke Requirements on Contracts in order to get these tools Implemented in Production

99. 27 Apr ‘06 99 Information Interoperability Roadmap Note: Circled boxes have been addressed under the ISE Project

100. 27 Apr ‘06 100 Conclusions These testing, modeling, and simulation efforts are part of an attempt to develop a suite of product model data exchange tools that will enable U.S. shipyards to become more productive These efforts revolve around implementation of the ISO 10303 STEP Shipbuilding standards and XML technology The APs that enable these exchanges have completed their development and approval as International Standards The primary focus has shifted to testing and validating their implementations ISE Tools Enable Interoperability between Shipyards and Reduce the Life Cycle Cost of Ships

101. 27 Apr ‘06 101 Two major challenges lie ahead of us: –Commercialization of this technology –Continuing to prototype standards based data exchange in other application areas In order to increase the availability and lower the price of production ready tools: –The ship owner / operator needs to insist that data be delivered in a system neutral format –The shipbuilder needs to insist that STEP functionality be an integral part of computer software products The next challenge is to move this technology into the mainstream and insure that the technology is mature enough to transition into commercial CAD, CAE, CAM, and PDM products Challenges

102. 27 Apr ‘06 102 Summary Enabling interoperability is a major challenge in achieving the goals of NSRP Achieving these goals will have a major impact on reducing the cost of ships The ISE Project is attacking these problems in many different disciplines and environments Although ISE has been very successful, much work remains to achieve our goals