1. Integrated Shipbuilding Environment
Enabling Shipbuilding Interoperability ISE-6 Project Exchange of Product Models for Life Cycle Support Demonstration April 2, 2008 Washington, D.C.
2 Apr ‘08

2. Interoperability Problem ISE Architecture and History
Overview
Interoperability Problem
ISE Architecture and History
Product Life Cycle Support (PLCS) Background
Enabling Shipbuilding Interoperability Throughout the Entire Life Cycle (ISE-6)
Demo
2 Apr ‘08

3. 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 problem 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
2 Apr ‘08

4. 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:
STEP (Standard for Exchange of Product Model Data)
XML (Extensible Markup Language)
isetools.org Website
The ISE Projects have helped develop these standards, defined the approach, and implemented a solution to ensure information interoperability
2 Apr ‘08

5. ISE Project Approach Develop and demonstrate tools that are low cost
Can be selectively used by shipyards to support interoperability
Capitalize on XML and related Internet technologies
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
Drive development of shipbuilding product data standards (e.g. STEP, PLIB)
Construct a single Shipbuilding Information Model
Demonstrate and educate U.S. shipbuilding community
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
2 Apr ‘08

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

7. ISE Architecture
ISE architecture represents an innovative, practical solution
to the information interoperability challenge
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
2 Apr ‘08

8. Information Interoperability Roadmap
HVAC
ISO AP 227:2005
Piping
Ship Arrangement
ISO AP 215:2004
Ship Moulded Forms
ISO AP 216:2003
Ship Structures
ISO AP 218:2004
Reference Data
Libraries
ISO 15926
Common Parts
Catalog (CPC)
Electrical
ISO AP 212:2001
Mechanical Systems
Cable Trays
Finite Element
Analysis
ISO AP 209:2001
Product
Config
/ Geometry
ISO AP 203/214:1994
Product Life Cycle
Support
ISO AP 239
Systems Engineering
ISO AP 233
Computational Fluid
Dynamics
ISO AP 237
Logistics / Spares
ISO AP 232:2002
Outfit & Furnishings
NSRP 0428:1992
Manufacturing
ISO
APs
224, 238, 240
Standard
Approved
Information
Model
Prototype
Translators
Testing
Framework
Deployment, integration,
testing
In Work
Ship Product Model Data
Ship Structural
Envelope
Distribution
Systems
Equipment /
Subsystems
Life Cycle
Maintenance
Miscellaneous
HVAC
ISO AP 227:2005
Piping
Ship Arrangement
ISO AP 215:2004
Ship Moulded Forms
ISO AP 216:2003
Ship Structures
ISO AP 218:2004
Reference Data
Libraries
ISO 15926
Common Parts
Catalog (CPC)
Electrical
ISO AP 212:2001
Mechanical Systems
Cable Trays
Finite Element
Analysis
ISO AP 209:2001
Product
Config
/ Geometry
ISO AP 203/214:1994
Product Life Cycle
Support
ISO AP 239
Systems Engineering
ISO AP 233
Computational Fluid
Dynamics
ISO AP 237
Logistics / Spares
ISO AP 232:2002
Outfit & Furnishings
NSRP 0428:1992
Manufacturing
ISO
APs
224, 238, 240
Standard
Approved
Information
Model
Prototype
Translators
Testing
Framework
Deployment, integration,
testing
In Work
Ship Product Model Data
Ship Structural
Envelope
Distribution
Systems
Equipment /
Subsystems
Life Cycle
Maintenance
Miscellaneous
Ship Product Model Data
Ship Product Model Data
Ship Structural
Ship Structural
Distribution
Distribution
Equipment /
Equipment /
Life Cycle
Life Cycle
Miscellaneous
Miscellaneous
Envelope
Envelope
Systems
Systems
Subsystems
Subsystems
Maintenance
Maintenance
Product
Product
Ship Arrangement
Ship Arrangement
Piping
Piping
Common Parts
Common Parts
Systems Engineering
Systems Engineering
Config
Config
/ Geometry
/ Geometry
ISO AP 215:2004
ISO AP 215:2004
ISO AP 227:2005
ISO AP 227:2005
Catalog (CPC)
Catalog (CPC)
ISO AP 233
ISO AP 233
ISO AP 203/214:1994
ISO AP 203/214:1994
Product Life Cycle
Product Life Cycle
Finite Element
Finite Element
Ship Moulded Forms
Ship Moulded Forms
HVAC
HVAC
Reference Data
Reference Data
Support
Support
Analysis
Analysis
ISO AP 216:2003
ISO AP 216:2003
ISO AP 227:2005
ISO AP 227:2005
Libraries
Libraries
ISO AP 209:2001
ISO AP 209:2001
ISO AP 239
ISO AP 239
ISO 15926
ISO 15926
Ship Structures
Ship Structures
Cable Trays
Cable Trays
Outfit & Furnishings
Outfit & Furnishings
ISO AP 218:2004
ISO AP 218:2004
ISO AP 227:2005
ISO AP 227:2005
NSRP 0428:1992
NSRP 0428:1992
Manufacturing
Manufacturing
Mechanical Systems
Mechanical Systems
Support
Support
Logistics / Spares
Logistics / Spares
ISO AP 227:2005
ISO AP 227:2005
ISO AP 232:2002
ISO AP 232:2002
ISO
ISO
APs
APs
224, 238, 240
224, 238, 240
Computational Fluid
Computational Fluid
Electrical
Electrical
Dynamics
Dynamics
ISO AP 212:2001
ISO AP 212:2001
ISO AP 237
ISO AP 237
Information
Model
Prototype
Translators
Standard
Standard
Standard
Standard
Information
Information
Prototype
Prototype
Testing
Testing
Deployment, integration,
Deployment, integration,
In Work
In Work
Approved
Approved
Model
Model
Translators
Translators
Framework
Framework
testing
testing
2 Apr ‘08

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

10. History of ISE Projects
The ISEC is led by U.S. shipbuilders along with commercial software vendors, and information technologists
This team has been together for eight years and has developed much of the infrastructure and architecture necessary for shipbuilding information interoperability
Product Life Cycle Support
Ship Arrangements
Steel Processing
Engineering Analysis
Electrical
Electrotechnical
HVAC
CPC Interfaces
Requirements
Structures
Piping
ISE-1
ISE-2
ISE-3
ISE-4
ISE-5
ISE-6
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2 Apr ‘08

11. Interoperability: Current Related Efforts
ISE-6 (Enabling Shipbuilding Interoperability)
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
SCIM (Ship Common Information Model)
SCIM will codify the models developed under the ISE Project under NSRP over the past seven years
It will be a separate document from the IPDE Specification to be produced by the NPDI Project, but it will be referenced by that IPDE Specification
Initial versions of the two documents will be completed in the same timeframe, but updates and subsequent versions can be issued independently
2 Apr ‘08

12. ISE Team Participants
2 Apr ‘08

13. 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.
2 Apr ‘08
2 Apr ‘08 13

14. ISE-2 Demonstration (April 2003)
AP216: Ship Moulded Forms AP218: Ship Structure AP227: Piping
2 Apr ‘08

15. ISE-3 Demonstration (October 2004)
AP227: HVAC
2 Apr ‘08

16. Washington DC • Integrated Shipbuilding Environment HVAC Demonstration •
ISE
2 Apr ‘08

17. ISE-4 Demonstration (April 2006)
Ship Arrangements
Engineering Analysis
Electrical Design
Steel Processing
TWR 3D Product Model Geometry
Engine Room
2 Apr ‘08

18. Systems Involved in the ISE-4 Interoperability Demo
Initial Design
Detail Design
Manufacturing
Lifecycle Support
Concept & Preliminary
Design
Engineering
FEA Analysis
Steel
Processing
Electrical
ADAPT
Feed Mfg
from ISDP
KSS/KM
AP212
P21
AP209
P21
EBC A
AP212
P28
Preliminary
Arrangement
Modify
Arrangement C
Partnership Yard
AP218
P28
GDEB
NGSS
Repair Shipyard
AP218
P28
Atlantec
Sener
Intergraph
TRIBON B
FORAN
ISDP
AP215
P28
INTELLISHIP
AP215
P28 B
Suggest
Design
Changes
Approval
AP215
P21
Submit Design
Final Product Model Delivered
to Navy
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
2 Apr ‘08

19. TWR Compartment Overview
Compartment Name Compt # Volume (m^3)
Air Handling Room Q
Ballast Tank # V
Ballast Tank # V
Ballast Tank # V
Ballast Tank # F
Bosuns Stores A
Bow Thruster Q
Chain Locker Q
CO State Room L
CPO State Room L
Crews Berthing L
Deck Gear A
Electrical Room Q
Engine Room E
Engine Room Exhaust Trunk Q
Engine Room Supply Trunk Q
Forepeak V
Fuel Oil Tank # F
Fuel Oil Tank # F
Fuel Oil Tank # F
Fuel Oil Tank # F
Fuel Oil Tank # F
Galley and Mess Area L
Hold Head L
Hold Passageway L
Lazarette Q
Lazarette Passageway Q
Linen Locker A
Lube Oil Tank F
Main Deck Head L
Main Deck Passageway L
Observers Berthing L
Pilot House C
Pilot House Passageway L
Potable Water Tank # W
Potable Water Tank # W
Provisions Storeroom A
Pump Room Q
Pump Room Passageway Q
Pump Room Supply Trunk Q
Void V
Waste Oil Tank F
2 Apr ‘08

20. ISE-5 Demonstration (February 2007)
DXF or IGES
(2D CAD)
DXF or IGES
(2D CAD)
AP214
(3D CAD)
AP227
(3D Cableways)
2 Apr ‘08

21. ISE Interoperability Solutions
Interoperability solutions must apply to the entire life cycle
Initial efforts focused on Design issues
Focus has been on:
Transfer between multiple Design agents
Exchange between Design and Construction agents
Transfer of Product Models from Design agent to Customer
Attention later focused on Manufacturing
Recent ISE efforts have discussed 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
2 Apr ‘08

22. Issues Arising for 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
2 Apr ‘08

23. Standards for Life Cycle
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 Logistics & Life Cycle Support (PLCS)
(STEP AP 239)
ISE-6 Phase 1
International ISO Standard
Driven by Aerospace and Defense
ISE-6 is Prototyping Use for
Shipbuilding
Standard for Technical Publications
(S1000D)
ISE-6 Phase 2
International Standard
Driven by Aerospace, Defense
Emerging DoD IETM Standard
2 Apr ‘08

24. Product Life Cycle Support (PLCS)
Project to Develop AP239 as an ISO Standard for PLCS
2 Apr ‘08
Copyright Eurostep Group AB

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

26. Extended Enterprise enabled by Internet technology
Product Life Cycle Support (PLCS)
Extended Enterprise enabled by Internet technology
Internet-based architecture and federated data models make possible implementations involving thousands of users across many sites
Extended Enterprise of
OEM’s, Customer, Partners
and Suppliers
Capture product info for support use
Develop the support solution
PLCS
Domain
Maintain product
Provide feedback
Suppliers
Tier 2
Product Lifecycle Management (PLM)
Tier 1 Suppliers
Enterprise Integration
through dedicated networks
Extended Enterprise Integration
Customers
Partners
Domain specific
information systems
(e.g. CAD, MRPII, Planning)
Enterprise
Dept
Concept
Assessment
Demonstration
Manufacture
In-Service
Disposal
Product Life Cycle
2 Apr ‘08
2 Apr ‘08
Copyright Eurostep Group AB 26

27. Product Life Cycle Support (PLCS)
ISE
2 Apr ‘08
Copyright Eurostep Group AB

28. The Key Business Problem
Product
In Focus
Feedback
2 Apr ‘08
Copyright Eurostep Group AB
Copyright Eurostep Group AB

29. ISE 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
2 Apr ‘08
Copyright Eurostep Group AB

30. Typically complex systems environment – point to point integration
2 Apr ‘08
Copyright Eurostep Group AB

31. Product Life Cycle Support (PLCS)
2 Apr ‘08
Copyright Eurostep Group AB

32. Enabling Shipbuilding Interoperability (ISE-6)
Motivation
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
2 Apr ‘08

33. ISE-6 Project Participants
Electric Boat
Northrop Grumman Shipbuilding
Atlantec-es
Industrial Planning Technology
Intergraph
Knowledge Systems Solutions
NSWC-CD
Northrop Grumman Information Technology
Product Data Services Corporation
ShipConstructor Software USA
2 Apr ‘08

34. Navy Participation in ISE-6
The ISE-6 Team is anxious to have Navy participation and review of its efforts
NSWC-CD (Naval Surface Warfare Center – Carderock Division) is a Team Member
Personnel from PEO-IWS (Program Executive Office – Integrated Warfare System) and NSWC - PHD (Naval Surface Warfare Center - Port Hueneme Division) attended the ISE-6 Meeting in Virginia Beach, VA in January 2008
Reviewed ISE-6 Use Cases and Scenarios
Participated in developing plans for this ISE-6 Demo
Project results will be presented at conferences with strong Navy and shipyard participation
e.g. ShipTech, SPS, NSRP Panels, etc.
2 Apr ‘08

35. Navy Logistics Data Requirements Configuration Changes &
SCLSIS data is core of Navy configuration and maintenance
RADCOM
Configuration Changes &
Work Candidates (WCs)
Sailor
RADMB
OMMS NG
R-SUPPLY
3-M
History DB
3MC
Maintenance
Data
Configuration
Data
Maint
Team
NAVICP
RMAISDB
CDMD OA
SCLSIS
Navy Supply Chain
NEMAIS
RMC
ISEA
ISEA
Shipyard
2 Apr ‘08

36. Requirements Management Approvals, Security, Status
Navy Business Usage
PLCS provides an opportunity
to leverage Integrated Data
Environments (IDE) developed
for each ship program.
Ship Design
Parts
Manufacturing
Ship Configuration
Logistics Data
Program Data
Documents
Design Data
Change Mgmt
Integrated Data
Environment (IDE)
Ship Design
Parts
Manufacturing
Ship Configuration
Logistics Data
Program Data
Documents
Design Data
Change Mgmt
Integrated Data
Environment (IDE)
Change Management
Product Structure
Requirements Management
Schedule
Activities
Organizations
Property
Classification
Approvals, Security, Status
Maintenance
Support Tasks
APSI
Support History
Messaging
PLCS
Legacy Logistics &
Support Systems
Regional
Maintenance
Center
2 Apr ‘08

37. Requirements Management Approvals, Security, Status
ISE-6 PLCS Approach
STEP Shipbuilding APs
Design and Manufacturing
ISE Information
Models
Molded Forms
Link design and
Logistics data
Mechanical Systems
Ship Structure
Arrangements
Navy Logistics
Data Requirements
Distributive Systems
Change Management
Product Structure
Requirements Management
Schedule
Activities
Organizations
Property
Classification
Approvals, Security, Status
Maintenance
Support Tasks
APSI
Support History
Messaging
PLCS
ISE-6
Drawings
Equipment
Navy Logistics
Data Requirements
(SCLSIS)
Design Data
Captured by Shipbuilding APs
Focus of previous ISE projects
Logistics Data
Now captured by PLCS (AP 239)
Focus of ISE-6
Capture Navy requirements
Normally developed independently from design data
ISE-6 schema maintain linkage to design data
2 Apr ‘08

38. Shipbuilding Use Cases Mapped to AP239
Standard Work Processes in PLCS (AP239) have been mapped to Shipbuilding Specific Use Cases
All Shipbuilding Use Cases can be represented by DEXs in PLCS
Life Cycle Support Business Process for Ship Acquisition
Application Activity Model (AAM) Diagram from AP239
2 Apr ‘08

39. Business Usage Scenarios
This technology is applicable to a wide-range to scenarios
Reuse within Navy
Life cycle support
Modernization & repair
Co-design
Co-production
PLCS enables exchange of consistent design and logistics data
Typically design and logistics data separately
Logistics data often exchanged piece-meal
Integrated exchange of design and logistics data supports
Distance Support
Regional Waterfront Integration
‘One Shipyard’ concept
Efficient logistics product development
Lifecycle Maintenance
Operations
2 Apr ‘08

40. Example of an ILS Data Collection
*FOT – Fuel Oil Transfer
Link Key
Ship Info Book
Ship
TMINS number
FOT* System
System Diagram
Drawing #, rev
TMINS number
Or ESWBS
Tech Manual
FOT SubSystem
3D Drawing
Drawing #, rev
FOT SubSystem
VFI Photo
Catalog part number
VFI Product Sheet
Catalog part number
Pump
VFI Quote
Catalog part number
Today’s Demonstration:
Exchange Components of Fuel Oil Transfer System
Equipment design and logistics data
Related logistics documents
AP 214 File
Catalog part number
Logistics Reports
RIC
2 Apr ‘08

41. PLCS Exchange: Functional Scenario
Design
(3D CAD Data)
Navy IDE
(Design & Analysis)
Data Prep & QA
(Design, Logistics, & CAD)
Shipyard B IDE
(Design, Logistics, & CAD)
Shipyard A IDE
(Design & Logistics)
Navy Depot
(Design, Logistics, Support)
2 Apr ‘08

42. AP239/PLCS (ISE-6) Demo Scenario
Design
Navy IDE
ShipConstructor
LEAPS
Navy Design & Analysis
Repository
2008
AP 227
CATIA
ShipConstructor
AP 227
(V4 AEC)
2006
AP 214
AP 239
3D Design
Design & Logistics
episTree
Knowledge Management
Software
Shipyard A -
IDE
AP 239
Shipyard B -
IDE
AP 239
Design & Logistics
AP 214
AIM/SIR
LPD 17 IPDE Software
Design & Logistics,
Teamcenter
including 3D Design
DDG 1000 IDE Software
2 Apr ‘08

43. ISE-6 Phase 2
Phase 2 of the ISE-6 Project will run from April 2008 through March 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
The next phase of ISE-6 will develop use cases for shipboard interactive technical documents that take advantage of the new capabilities of the S1000D standard
2 Apr ‘08

44. 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
Automated test frameworks for conformance testing
2 Apr ‘08

45. Summary
In order to increase the availability and lower the price of production ready computer systems:
The ship owner / operator needs to insist that data be delivered in a system neutral format
The shipbuilder needs to insist that robust STEP functionality be an integral part of computer software products
The next challenge is to move this demonstrated technology into the mainstream and insure that the technology is mature enough to transition into commercial CAD, CAE, CAM, and PDM products
Enabling interoperability throughout the ship’s life cycle is a major challenge in achieving the goals of NSRP
2 Apr ‘08