WONDERMAR II Workshop Information Exchange in Ship Design Thomas Koch Atlantec-es Andreas Weidig Aker Ostsee
Overview Information Exchange vs. Integration The Role of Standardisation Process Issues Business Cases: Collaboration (Scenario 1) Design to Production (Scenario 3) Wondermar Workshop Lisbon October 2, 2003 2
Information Exchange vs. Integration Exchange provides a fixed scope of data with known content structure is asynchronous, i.e. it can happen at any time requires a request/response/acknowledge interaction does not include information flow management by default Information Flow Management access control history and journaling meta data pertaining to the unit of data exchange Wondermar Workshop Lisbon October 2, 2003 3
Integration data references beyond individual exchange boundaries versioning and configuration option 1: tight integration through single branding accomplishes advanced levels of integration restricts capabilities and existence to the selected software product regularly prohibits an dynamic project team configuration and access option 2: integration through higher level interaction accomplishes similar levels of integration requires a reasonable level of accessibility in participating systems allows and supports independence of partners provides secured local environments supports all aspects of security Wondermar Workshop Lisbon October 2, 2003 4
The Role of Standardisation Standardisation means a contract between parties It s not a technology, nor a product you can buy What is needed for Exchange/Integration? application data content general principles: naming, structure Are ISO 10.303, ISO 13.584,... useful? the value is in the application data models the issue is the brokering too much energy has been wasted in low-level agreements Wondermar Workshop Lisbon October 2, 2003 5
Process Issues enabling data exchange is only solving part of the problem it's the process that needs to be supported unmanaged exchange of data leads to confusion technology is not solving it all a mechanism for coordination is needed the coordinating mechanism would greatly benefit from process monitoring which event has happened when? did a task complete successfully? Wondermar Workshop Lisbon October 2, 2003 6
Process Coordination requirements: history and journaling state recording implementation decisions: centralized vs. distributed heavy-weight vs. light-weight strict rules vs. exception tolerance Wondermar Workshop Lisbon October 2, 2003 7
Business Case: Collaboration situation before: Pipe Design and Production at different sites of a merged shipyard group Different CAD and CAM tools in use Different Part Catalogues in use problem statement: enable collaboration between different tools and locations requirements: data retrieval and creation at each connected tool information flow monitoring Wondermar Workshop Lisbon October 2, 2003 8
From design to production? Virtual Reality CAD Reality Assembly Hall Wondermar Workshop Lisbon October 2, 2003 9
Business Case: Design to Production Replacement of an older version of a nesting application new and enhanced software functionality switch of operating system platform, obsoleting earlier custom link tools Problem statement: migrate existing set of tools to a new configuration while improving overall functionality and performance Requirements: data retrieval and creation at each connected tool exploit the potential of a new, wider scoped set of information information flow monitoring Wondermar Workshop Lisbon October 2, 2003 10
Design & Production Information Flow PPS-System (Projector) Mat Form Lists NAPA Autocad Topgallant Nesting Tribon Drafting, Hull, Nesting (PL+PR+PAN), WOP Pipe, Component, Equipment PDI DXF Drawings Part lists AutoNest ALMA Roni RAMP PRE/PRB Profile bending PLI/ATX/GEN Welding robot Drawings/Lists/Production/NC-Files/Production Control Wondermar Workshop Lisbon October 2, 2003 11
CAD-CAM CAM Connector Architecture original situation CAD CAD System 1 inhouse developed link integrated (same vendor) CAM CAD System 1 IGES CAD CAD System 12 missing link CAD CAD System 13 manual input XLS inhouse developed link proprietary format DXF CAM CAD System 13 CAM CAD System 12 Wondermar Workshop Lisbon October 2, 2003 12
CAD-CAM CAM Connector Architecture after introducing the connector architecture solution CAD System 1 A D P T A D P T Nesting CAD System 2 A D P T Connector Architecture A D P T Welding CAD System 3 A D P T A D P T CAM System X Wondermar Workshop Lisbon October 2, 2003 13
An application: automatic nesting solution AMTW (Wismar shipyard) Topgallant AutoNest AWW (Warnemünde shipyard) Topgallant AutoNest Tribon Hull Alma act/cut Adapter Adapter Topgallant Information Server Topgallant Information Server Adapter Adapter Tribon Hull Alma act/cut Wondermar Workshop Lisbon October 2, 2003 14
Automatic Nesting Process Controler Wondermar Workshop Lisbon October 2, 2003 15
Use best of class tools Need of data exchange Why do we need to use a set of tools? Leveraging CAD System functions Customisation to yard demands Flexibility of data input Enable not only design view to data Send data other special applications Engineering calculation Production process planning and simulation Minimise investment and maintenance cost Local partner Flexible and quick response Wondermar Workshop Lisbon October 2, 2003 16
Manufacturing Simulation Concept Projektor em Plant Tasks Schedule Facilities Duration Database Aker Warnow Werft Aker MTW Build Strategy Dimensions Weight Boundary Conditions Simulation results Modules Wondermar Workshop Lisbon October 2, 2003 17
Summary & Statements 1. Data exchange is not enough, integration across system boundaries is a must. 2. Support of non-centralized, distributed process execution is necessary. 3. Standardization is misunderstood as a magic solution. It is an agreement, which needs to be implemented. Wondermar Workshop Lisbon October 2, 2003 18