Ship Common Information Model (SCIM) Integrated Logistics Environment Project (ILE) NSRP Information Technologies Panel Narration: We appreciate your interest in this presentation. It will familiarize you with the Ship Common Information Model, or SCIM The Ship Common Information Model is a product of the Navy Product Data Initiative and the Integrated Logistics Environment Project of the National Shipbuilding Research Program. It was developed by members of the Information Technologies Panel of NSRP and is available for implementation by any U.S. Shipyard and the U.S. Navy You will have an opportunity to learn more about NSRP at the end of this presentation; however, if you would like to know about NSRP before you start, select the icon in the lower, right corner of the screen indicated by the pointing hand Learn more about NSRP

Purpose of this presentation: What an IPDE is and why the sharing of data is important An overview of the SCIM and how it can be used within an IPDE The ability of the SCIM to allow the sharing of data between organizations Factors affecting the implementation of the SCIM Narration: The purpose of this presentation is to familiarize you with the following topics: What an IPDE is and why the sharing of data is important within and among organizations An overview of the SCIM and how it makes the sharing of data within an IPDE possible The use of the SCIM to share data across organizations And Factors that affect the implementation of the SCIM

Ship Common Information Model The SCIM is the… Ship Common Information Model …it provides the ability to share data for U.S. Navy ship design, analysis, construction, and post-delivery support Narration: The SCIM is the Ship Common Information Model. It provides the ability to share data for U.S. Navy ship design, analysis, construction, and post-delivery logistics support Let’s see why this ability to share data is important, both within a shipyard and across the industry…

Expansion of CAD/CAE/CAM Systems in U.S. Narration: The proliferation of Computer-aided Design, Engineering and Manufacturing Systems has drastically improved the process of designing and building Ships. But sharing data between these different computer systems is challenging. CAD/CAE/CAM Systems CAD/CAE/CAM Systems

Integrated Product Data Environment (IPDE) Computer-aided Design (CAD) Product Data Management (PDM) Computer-aided Manufacturing (CAM) Enterprise Resource Planning (ERP) Computer-aided Engineering (CAE) Narration: In order to understand why the ability to share data is important, we need to understand what an Integrated Product Data Environment is. An Integrated Product Data Environment, or IPDE, is a collection of business processes and computer systems which house the product model data of the ship. IPDE’s enable people to work in concert towards the business goals of designing, building, operating, and maintaining a ship. When a Shipyard invests in an IPDE to integrate its purchasing, design, planning, and manufacturing systems, it can realize significant efficiencies in the process of designing, building, and maintaining a ship. With this reward come risks that must be addressed, particularly when the data must be maintained for the life of the ship. Let’s take a look at these risks…

Length of time to design and build a ship often exceeds the life span of current computer systems… Concept Preliminary Detail Construction/Test Narration: With the rapid evolution of computer operating systems and software, the length of time it takes to design and build a ship may exceed the life span of the original computer systems and design software chosen for the ship program. This may require that the ship design and construction product model data be moved to a later-generation IPDE during the construction of the follow-hulls in a Class. This may require the ship design and construction product model data to be moved to a later generation IPDE during the construction of the follow hulls in a Class

In-service support vs. life span of computer systems Narration: Beyond its design and construction time, in-service support and future modification of the ship will FAR exceed the life span of the original computer system. Though the current-generation IPDE computer systems may die in a few short years, or at most a decade, much of the design and manufacturing data contained within them must survive long into the future, some for the lifetime of the ship.

Each Shipyard approaches their IPDE differently CAD PDM CAM ERP CAE CAD PDM CAM ERP CAE Narration: Each shipyard approaches their Integrated Product Data Environment differently. The challenges that we have mentioned so far have been challenges between systems within an individual shipyard. The risk and challenge increases when data from these systems must be shared between different shipyards and with the Navy. CAD PDM CAM ERP CAE

Virginia Class & Ohio Replacement Class Submarines Most recent and future U.S. Navy ship design and build contracts involve multiple shipyards Virginia Class & Ohio Replacement Class Submarines Bath DDG51 Flight II & DDG1000 Ford Class Carrier Newport News Narration: These risks and challenges are relevant in that most recent and future U.S. Navy ship design and construction contracts have involved collaboration among multiple shipyards The latest carrier design is partnered between Newport News Shipbuilding and Electric Boat Ingalls and Bath are working on the DDG1000 and the DDG51 Flight 2 Restart Electric Boat & Newport News Shipbuilding have been partnering on the Virginia Class and the Ohio-Class replacement Submarines This means that each Integrated Product Data Environment needs to communicate from the earliest stages of design, throughout the life of the ship. Ingalls Electric Boat

Interoperability U.S. NAVY IPDE IPDE IPDE Narration: The ability to “work in concert” is called “interoperability” Interoperability can be challenging within the systems and organizations of each individual shipyard As already mentioned, the challenge increases when there is a need to communicate between these systems and those at partnering shipyards and the Navy IPDE

Collaboration is a trend that will continue U.S. NAVY “One Shipyard” Narration: Collaboration among multiple shipyards is prevalent today and this trend is going to continue In these cases, interoperability is critical to the success of these collaborations The Navy views interoperability as enabling multiple yards to be seen as “One Shipyard” We will now look at the standards that allow data exchange between different computer systems and software…

A Standard is required for this exchange of product data So, why not use the STEP ISO Standard directly ? ISO 10303 is the international standard Informally known as “STEP ”: (STandard for The Exchange of Product Model Data) Narration: ISO 10303 is an international ISO standard for the exchange of product design, manufacturing, and through life support information It is informally known as "STEP", which stands for "Standard for the Exchange of Product model data” STEP’s objective is to provide a mechanism that is capable of describing product data throughout the life cycle of a product, independent of any particular computer system So, why don’t we use the STEP ISO Standard directly instead of using the SCIM, the Ship Common Information Model?

The STEP Series of ISO Standards support many industries The STEP series of ISO Standards were developed by and support many industries in addition to shipbuilding, such as aerospace, automotive, and process plant design and construction Translators must be developed using these standards so that data can be exchanged These translators for data exchange have not been developed for all of these industries…particularly for the shipbuilding industry… Aerospace Automotive Shipbuilding Plant Design

The STEP Standards require Translators Shipyard A The STEP Standards require Translators to share the data between different systems and between shipyards Developing the translators requires specialized knowledge and special software tool kits, making them expensive to implement Shipyard B Shipyard C Require Special TOOL KITS Are EXPENSIVE

Here are your STEP-Translators The limited market of Shipbuilding has not encouraged commercial CAD vendors to develop ship-specific translators Here are your STEP-Translators What about us? Aerospace While many current CAD systems have STEP geometry translators that can be used by any industry, the limited market of shipbuilding and repair has discouraged the commercial Cad vendors from developing the ship-specific translators that our industry needs. Let’s see how the SCIM makes it possible for the shipyards and the Navy to solve our data-sharing challenges … Automotive Shipbuilding Plant Design

The SCIM provides a blueprint for shipyard IT personnel to develop translators Narration: The Ship Common Information Model, or SCIM, serves as a blueprint for Shipyard IT personnel to develop the needed translators Shipyard IT Personnel

SCIM is Structured to use existing Commercial STEP Geometry Translators Shipyard IT Personnel CAD Vendors SCIM XML Version Narration: The SCIM is structured to use the STEP geometry translators from the CAD vendors together with shipyard-developed XML translators This allows the geometry of the CAD Vendor software to be related to the non-graphical shipbuilding information from CAD, CAM, PDM, ERP, and Logistics systems. Commercial STEP Geometry Translators Shipyard-developed Translators

The SCIM satisfies the STEP Requirements The SCIM is based on shipbuilding portions of the Step Standards The SCIM defines the requirements and XML data model for Ship data exchange This XML Data defines the minimum set of entities & attributes that must be available for applications supported by an IPDE… …and for sharing with business partners and the Navy Narration: The SCIM is based on the Shipbuilding portions of the STEP Standards The SCIM defines the data exchange requirements and the XML data model to enable interoperability among shipyard and Navy systems This XML data model defines the minimum set of entities and attributes that must be available for applications supported by an IPDE… …and for sharing with business partners and the Navy.

The Product Model Data needs to be captured throughout the Life Cycle Milestone Reviews Concept Preliminary Detail Construction/Test In Service Support Decommission S C I M Narration: The Product Data needs to be captured as it transitions throughout the Life Cycle of the ship. The Product Data is spread across many computer systems and specialized software packages The SCIM, the Ship Common Information Model, facilitates the sharing of this Product Data between the pieces of an IPDE and with external systems such as collaborating shipyards and the Navy. It can also be used as a method for long term archiving of the ship design product data that may need to be retrieved at any point in the future. Archive External Systems Collaborating Shipyards And the Navy

No need to rely exclusively on CAD Vendors for all Data Translator Support XML is standard method for accessing non-graphical data SCIM Documented in XML Narration: XML has become the standard method for accessing non-graphical data in software systems. Documenting the SCIM in XML, using shipbuilding terminology, allows shipyard IT personnel to develop the IPDE data translators in-house, with or without support from their CAD vendors. This allows for development of IPDE Data Translators In-House Shipyard IT Personnel

The SCIM specification is… Of practical use for agreements between shipbuilder and CAD System vendors Usable by shipyard personnel, including non-IT specialists Capable of validation Narration: The Ship Common Information Model (SCIM) specification is… Fully documented and user-friendly Usable by shipyard personnel, including non-IT specialists Capable of validation Suitable for contractual specification And is of practical use for agreements between the shipbuilder and their CAD System vendors Suitable for contractual specification Fully documented and user-friendly

The SCIM Chapters support each shipbuilding functional area Product Data Management Piping Physical Design Piping Functional Design Ship Molded Form Heating, Ventilation, and AC Design Ship Arrangements Electrical Design and Installation Ship Structures Narration: The SCIM is organized as a series of Chapters that support each shipbuilding functional area. The shipbuilding functional areas supported by the SCIM chapters are: Product Data Management - Ship Moulded Forms - Ship Arrangement - Ship Structures - Common Parts Procurement - Piping Physical Design - Piping Functional Design - Heating, Ventilation, and Air-Conditioning Design - Electrical Design and Installation - Engineering Analysis and - Product Life Cycle Support Engineering Analysis Common Parts: Procurement Product Life Cycle Support

SCIM Chapters: Shipbuilding Functional Areas: Each SCIM Chapter supports one of these functional areas Each of these SCIM Chapters has a corresponding XML Schema Narration: These are the shipbuilding functional areas just displayed As mentioned, each SCIM Chapter supports one of these functional areas In addition, each of these SCIM Chapters, has a corresponding XML Schema

Importance of the Ship Common Information Model Allows shipyards to move data between different pieces of their Integrated Product Data Environments (IPDE) Allows shipyards to exchange data with each other and the Navy Necessary due to the Navy’s practice of requiring multiple-shipyard design and build contracts, and… … because of the short lifespan of computer systems and software compared to the life of a ship Narration: Hopefully, by now, you see the importance of the Ship Common Information Model It allows shipyards to move data between the different pieces of their Integrated Product Data Environments. It allows shipyards to exchange data with each other and with the Navy. This is necessary due to the Navy’s practice of requiring multiple-shipyard design and build contracts, and… …because of the short lifespan of computer systems and software compared to the life of a ship. To conclude, let’s go over the advantages to implementing the SCIM at your shipyard…

Advantages to implementing SCIM at YOUR Shipyard Uses inexpensive or free XML tools rather than expensive STEP EXPRESS language toolkits Uses existing XML application programming interfaces to shipyard PDM and CAD tools Minimal introductory training needed for shipyard IT personnel to quickly implement XML-based translators Narration: It uses inexpensive or free XML tools rather than expensive STEP EXPRESS language toolkits; It uses existing XML application programming interfaces to shipyard PDM and CAD tools; Minimal introductory training is needed for shipyard IT personnel to quickly implement XML-based translators.

For more information… Please contact the Information Technologies Panel Chairman through the NSRP Website at http://www.nsrp.org Or… …Your Organization’s Information Technologies Panel members Narration: You can obtain more information about the Ship Common Information Model by contacting the NSRP Information Technologies Panel Chair at the email address provided on the NSRP Website