1

ILE Project

Integrated Logistics EnvironmentKickoff Meeting

Task 2 Task 2 Completion of the Ship Common Completion of the Ship Common

Information ModelInformation Model

Presented by: Presented by:

Dr. Burton GischnerDr. Burton Gischner

2

Objective

Completion of the Ship Common Information Model (SCIM Development)– The Ship Common Information Model (SCIM)

was defined as requiring fifteen chapters to specify the requirements for exchange of product model data among shipyards and the Navy. The development of eight of these chapters has been funded through NSRP under the Navy Product Data Initiative (NPDI).

– This effort will complete the SCIM and thereby will facilitate the data exchanges to be developed within the Integrated Logistics Environment

3

Ship Common Information Model (SCIM)

BackgroundBackground– Models developed under the Integrated Shipbuilding Models developed under the Integrated Shipbuilding

Environment (ISE) Project under NSRP over the past ten Environment (ISE) Project under NSRP over the past ten yearsyears

Association with IPDE Specification to be produced Association with IPDE Specification to be produced under NPDIunder NPDI– Will be a separate documentWill be a separate document– Will be referenced by IPDE SpecificationWill be referenced by IPDE Specification– All common terms in the two documents will share one All common terms in the two documents will share one

definitiondefinition» Definitions will be detailed in the SCIMDefinitions will be detailed in the SCIM

– Versions of the two documents will be completed and issued Versions of the two documents will be completed and issued independentlyindependently

– SCIM will be placed on Web and made available as Open SCIM will be placed on Web and made available as Open SourceSource

4

IPDE Product Model Data Must Transition

Throughout the Life CycleConcept Detail Construction/

TestIn Service Support Decomm.

Milestone Reviews/Decision Points

SC

IM

ToExternal Systems/

IPDEs

Preliminary

IPDE/PDMs maintained byMaintenance ContractorIPDE/PDM maintained by Design Agent/Builder

Archive

• During design and construction phases a set of PDM and applications tools capture and maintain product model data in native format

• However at any time during those phases, product model data may need to be transferred to external systems or archived

• These transfers should comply with the Ship Common Information Model (SCIM)

5

Integrated Shipbuilding Environment (ISE)

Shipbuilding information requirements are a Shipbuilding information requirements are a prerequisite both for IPDE implementation and for prerequisite both for IPDE implementation and for interoperabilityinteroperability

Over the past ten years ISE has formulated the US Over the past ten years ISE has formulated the US Navy shipbuilding requirements:Navy shipbuilding requirements:– Identifying from the comprehensive ISO standards, those Identifying from the comprehensive ISO standards, those

requirements that apply to US Navy shipbuildingrequirements that apply to US Navy shipbuilding– Formulating the technical approaches for implementation Formulating the technical approaches for implementation

including:including:» Simplification of information modelsSimplification of information models» Definition of an implementation-independent means of specifying Definition of an implementation-independent means of specifying

information requirementsinformation requirements» Establishment of a means for validationEstablishment of a means for validation

6

concept

designfabricate

assembletest

support

deliver

What is STEP?

...an international standard (ISO 10303) for exchanging data between different systems (CAD, CAM, CAE and PDM)

...a computer interpretable definition of the physical and functional characteristics of a product throughout its life cycle

SCIM is based on STEP (ISO 10303)Standard for the Exchange of

Product Model Data

7

Relationship of ISO Standards to SCIM Models

ISOApplication Protocol

Attributes________________________________________________________________

.

.

.

200

Vendor AISO/STEP Compliant

Translator

Attributes________________________________________________________

.

.

.

75

Shipyard

Attributes____________________________________________________________________

50

NEWNEWNEW

ISOApplication Protocol

Attributes________________________________________________________________

.

.

.

200

Vendor AISO/STEP Compliant

Translator

Attributes________________________________________________________

.

.

.

75

• Attributes and Properties in SCIM Models will be a Subset of the Attributes and Properties in the Associated STEP Standard

• They will be the Subset Required for US Shipbuilding Product Model Exchanges

8

What remains to be done…

The IPDE information requirements assembled The IPDE information requirements assembled by ISE have been published in a formal, XML-by ISE have been published in a formal, XML-based notationbased notation

Remaining work: package the ISE work in a Remaining work: package the ISE work in a manner that is:manner that is:– Fully documented and user-friendlyFully documented and user-friendly– Usable by shipyard personnel, including non-IT Usable by shipyard personnel, including non-IT

specialistsspecialists– Capable of validationCapable of validation– Suitable for contractual specificationSuitable for contractual specification– Of practical use for agreements between Of practical use for agreements between

shipbuilder and CAD/system vendorsshipbuilder and CAD/system vendors

9

The SCIM provides an information model that defines the minimum entities and attributes that must be transferred for applications supported by the IPDE

Ship Common Information Model

(SCIM)

10

SCIM - Overview Ship Common Information Model (SCIM)Ship Common Information Model (SCIM) Data DictionaryData Dictionary

– Neutral product data model (Neutral product data model (vocabulary)vocabulary) supporting all supporting all phases of shipbuilding lifecyclephases of shipbuilding lifecycle

– STEP-basedSTEP-based» STEP Application Protocols (APs) identify domain-specific contentSTEP Application Protocols (APs) identify domain-specific content

Content Description for Data ExchangeContent Description for Data Exchange– Implementers choose the portion of the schema that will be Implementers choose the portion of the schema that will be

supportedsupported– Incorporates results from past ISE programsIncorporates results from past ISE programs

» Schema development/enhancementsSchema development/enhancements» Data mediationData mediation» Implementer agreementsImplementer agreements» Usage scenariosUsage scenarios

11

SCIM Content

Ship Structures APsLifecycle Engineering APs

DistributionSystems APs

Equipment APs

Misc APs

• Current STEP APs support broad application

• Content primarily normative• Dated modeling language

• SCIM identifies relevant product model entities, within existing APs, specific to shipbuilding

• Adds informative material to serve as a usage guide

• Uses industry-standard modeling language (UML) for describing schema

SCIM

• For each entity, SCIM will provide:• Entity Name• Definition• Intent• Motivation• Structure

• Information Requirements• Properties• Implementation Consequences• XML

12

Relevant Definitions to Describe the SCIM

DData Modelata Model is an abstract model that describes how data is is an abstract model that describes how data is represented and usedrepresented and used

SchemaSchema is defined as a is defined as a data modeldata model that represents the that represents the relationships of a set of concepts within a domain relationships of a set of concepts within a domain – XML Schema is a way to define the structure, content and, to XML Schema is a way to define the structure, content and, to

some extent, the semantics of XML documents some extent, the semantics of XML documents Data File FormatData File Format is a particular way to encode information is a particular way to encode information

for storage in a computer filefor storage in a computer file

SCIM provides a Data Model and associated Schema

STEP Part 28 or other XML are possible Data File Formats that can be used to transfer the SCIM Data Models

SCIM provides a Data Model and associated Schema

STEP Part 28 or other XML are possible Data File Formats that can be used to transfer the SCIM Data Models

13

Entity name

Property name: datatypeProperty name: xs:datatype [Primary Key]<<stereotype>>Property name:datatype = value

Entity name

Relationship

Cardinality

CardinalityAssociation End name

Association End name

SCIM Diagrams are in the Universal

Modeling Language (UML) Key

Entity is referenced on another page

Entity: An entity is a modeling construct that is a representation of some item of interest in the real world.

Property: A property is a particular aspect of an entity, which represents values, constraints, behavior, etc.

Constraint: A constraint is a particular kind of property that specifies a restriction on other properties of an entity, or the entity taken as a whole, or on relationships.

Relationship: An association between two constructs in a model. A relationship may be implied or explicitly Identified.

Association: The semantic relationship between two or more classifiers that involves the connections among their instances.

Cardinality: The specification of the number of instances of one construct that can be associated with one Instance of a related construct.

Stereotype: An extension of the vocabulary of the UML, which allows you to create new kinds of building blocks that are derived from existing ones. Eg. “Implied”, “default”, “fixed”, “required’, “etc”.

14

SCIM Front Matter for Each Discipline

OverviewOverview Data Definitions of TermsData Definitions of Terms Usage Guides and Implementation AgreementsUsage Guides and Implementation Agreements

15

SCIM Content for each Entity

Entity NameEntity Name DefinitionDefinition IntentIntent MotivationMotivation StructureStructure Information RequirementsInformation Requirements PropertiesProperties Implementation ConsequencesImplementation Consequences XMLXML

16

Application Areas in the SCIM

SCIM Chapters CompletedSCIM Chapters Completed PDM and Change Management FundamentalsPDM and Change Management Fundamentals Structural Moulded FormsStructural Moulded Forms Ship ArrangementsShip Arrangements Structural Detailed DesignStructural Detailed Design Piping Functional DesignPiping Functional Design Piping Physical DesignPiping Physical Design Common Parts: ProcurementCommon Parts: Procurement Product Life Cycle SupportProduct Life Cycle Support

SCIM Chapters RequiredSCIM Chapters Required HVAC Functional DesignHVAC Functional Design HVAC Physical DesignHVAC Physical Design Electrotechnical Functional DesignElectrotechnical Functional Design Electrotechnical Physical DesignElectrotechnical Physical Design Engineering AnalysisEngineering Analysis Pipe Stress AnalysisPipe Stress Analysis Structural CAMStructural CAM

To be Developed under Task 2

To be Validated under Task 1

17

Task 2 Deliverables and Milestones

MonthMonth DeliverableDeliverable

1414 Complete SCIM Chapters for HVAC Complete SCIM Chapters for HVAC Functional & Physical DesignFunctional & Physical Design

1717 Complete SCIM Chapters for Electrotechnical Complete SCIM Chapters for Electrotechnical Functional & Physical DesignFunctional & Physical Design

2020 Complete SCIM Chapters for Pipe Stress & Complete SCIM Chapters for Pipe Stress & Engineering AnalysisEngineering Analysis

2323 Complete SCIM Chapter for Structural CAM Complete SCIM Chapter for Structural CAM (Lofting & Nesting)(Lofting & Nesting)

2424 Final ReportFinal Report

18

Synergy Between Tasks 1 & 2 of the ILE Project

Task 1 (SCIM Evaluation) will demonstrate the Task 1 (SCIM Evaluation) will demonstrate the capabilities of the SCIM as a means for supporting capabilities of the SCIM as a means for supporting the next generation IPDEthe next generation IPDE

Task 2 (SCIM Development) proposes to complete Task 2 (SCIM Development) proposes to complete the last seven chapters of the SCIMthe last seven chapters of the SCIM

In addition, the SCIM will modified and updated to In addition, the SCIM will modified and updated to incorporate lessons learned during Task 1incorporate lessons learned during Task 1– The already completed chapters will be updated as The already completed chapters will be updated as

requiredrequired– The style of the new chapters generated will be modified The style of the new chapters generated will be modified

to incorporate the above lessons learnedto incorporate the above lessons learned