1 / 102

Integrated Shipbuilding Environment (ISE) ISE4 Project Demonstration

Integrated Shipbuilding Environment (ISE) ISE4 Project Demonstration. April 27, 2006. ISE4 Participants. Presentation Agenda. Interoperability Demo Scenario Ship Arrangements Exchanges using AP215 and AP216 Initial Design in TRIBON Transfer from TRIBON to LEAPS Modifications in FORAN

rian
Télécharger la présentation

Integrated Shipbuilding Environment (ISE) ISE4 Project Demonstration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Integrated Shipbuilding Environment (ISE)ISE4 ProjectDemonstration April 27, 2006

  2. ISE4 Participants

  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. 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. 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. Lifecycle Phases for Demo Scenario Initial Design Detail Design Manufacturing Lifecycle Support Evolving Ship Design from Concept to Maturity Time

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

  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. Approach / Background Express XML Application A Application B ISO STEP Standard Information Model Translator Translator Data Part21 Part28 Mediator 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

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

  11. Integrated Shipbuilding Environment Arrangements Demonstration Washington DC • April 27, 2006

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

  13. Overview – Tribon Translator Atlantec Enterprise Solutions • 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

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

  15. As-Is Process – Tribon Translator Initial Design Integration Options: Currently Available • 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

  16. ISE Process – Tribon Translator Initial Design Integration Options: With STEP and ISE Translators • 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

  17. Overview – LEAPS AP215 Translators Product Data Services Corporation (PDSC) for NSWC Carderock Division • 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.

  18. Overview – LEAPS AP215 Translators LEAPS – LeadingEdgeApplicationforPrototypingSystems • 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. Overview – LEAPS AP215 Translators LEAPS – LeadingEdgeApplicationforPrototypingSystems

  20. As-Is Process - LEAPS AP215 Translators LEAPS – LeadingEdgeApplicationforPrototypingSystems • 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. ISE Process - LEAPS AP215 Translators • ISE4 project added STEP AP215 import and export translators • for LEAPS.

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

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

  24. Demo Scenario – FORANTranslator 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 Detail Design in FORAN SENER AP215 Translator STEP AP 215 File LEAPS for Customer Review and Approval ISDP used by Partnering Shipyard

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

  26. Demo Scenario - LEAPS AP215 Import • Part21 file from FORAN

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

  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. As-Is Process –Transfer to Life Cycle Support Neutral File Geometry (IGES, STEP, ACIS, DXF) Or Drawings Molded Form Modeler C&A Drawings Arrangements Modeler Structural Drawings Structural Modeler Equipment Arrangement Drawings Equipment Modeler Manual, labor intensive & often incomplete process Life Cycle Support System Integrated Construction Product Model

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

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

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

  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. 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. Spiral Development Knowledge-based system  STEP XML AP212 Design Configurator Single C4ISR Equipment Generic Objects Single C4ISR Circuit Framework Design Full Engineering & Design Data Sets Navy Air Force Integrated Prototype Commercial System Spec Full C4ISR System TWR Lighting TWR Power Distribution Component Design File Data Import STEP – Data – Translator

  36. Knowledge Management Demonstration • TWR Power Distribution System • Collect data and information into a knowledge base • Perform calculations and design functions

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

  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. 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. Engineering Analysis Demo Details Initial Design Detail Design Manufacturing Lifecycle Support Concept & Preliminary Design Engineering FEA Analysis Steel Processing Electrical ADAPT EBC EBC AP209 P21 XSLTs AP218 P28 ISDP NGSS, Intergraph NGSS, Intergraph Arrangements Detailed Design Stage Detail Design

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

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

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

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

  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. 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. Interoperability Extend ISO 10303 Interoperability R

  48. R PDES, Inc. Engineering Analysis Approach • 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. R

  49. Express <XML> ISO STEP Standard Information Model Data Part21 Part28 ISE Paradigm ISO STEP 10303 Information Model = Core Content The STEP Standards can be delivered (“wrapped”) in multiple forms, yet contain exactly the same data! R

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

More Related