Reuse and Data Module Code Naming Considerations

Mike Olson, Northrop Grumman IT

Ted Briggs, IntergraphIntegrated Shipbuilding Environment (ISE)

ISE-6 Phase 2

Sept. 10, 2008 2

Integrated Shipbuilding Environment (ISE)

• The Integrated Shipbuilding Environment Consortium (ISEC) is led by U.S. shipbuilders along with commercial software vendors, and information technologists

• This team has developed much of the infrastructure and architecture necessary for shipbuilding information interoperability

• NSRP funded program focused on interoperability using international standards – ISO STEP, PLCS, S1000D, W3C

1999

2000

2001

2002

2003

2004

2005

2006

2007

2008

2009

ISE-6ISE-5ISE-4ISE-3ISE-2ISE-1

Ship

Arr

ange

men

ts

Stee

l Pro

cess

ing

Engi

neer

ing

Ana

lysi

sEl

ectr

ical

Elec

trot

echn

ical

Prod

uct

Life

Cyc

le S

uppor

t

Requ

irem

ents HVAC

CPC

Inte

rfac

es

Stru

ctur

esPi

ping

Sept. 10, 2008 3

ISE-6 Project• Two year project, funded by National Shipbuilding Research

Program (NSRP) • Coordinate the use of the PLCS (STEP AP239), S1000D, and

ISE standards to enable these standards to integrate more closely with the shipyard’s product model to enable product life cycle interoperability

• Phase 1 (2007- 2008)– Integrated PLCS with ISE information models– Mapped core Navy ship configuration and logistics data to PLCS– Demonstrated an exchange to reuse configuration and logistics data across

Integrated Data Environments (IDE)

• Phase 2 (2008 – 2009)– Integrate S1000D capabilities with PLCS and STEP information models

– Manage change by linking S1000D modules to design structure – Scope and demonstration details are currently being defined

Sept. 10, 2008 4

ISE-6 Project Scope

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 Technical Publications (S1000D)

ISE-6 Phase 2

International Standard

Standard for Logistics & Life Cycle Support (PLCS)

(STEP AP 239)ISE-6 Phase 1

International ISO Standard

ISE-6 has Prototyped use for Naval Shipbuilding

Sept. 10, 2008 5

Navy PLCS Business Usage

Change Management

Product Structure

Requirements Management

ScheduleActivities

Organizations

Property

Classification

Approvals, Security, Status

Maintenance

Support Tasks

APSI

Support History

Messaging

PLCS

Ship Design

Parts

Manufacturing

Ship Configuration

Logistics Data

Program Data

DocumentsDesign Data

Change Mgmt

Integrated Data Environment (IDE)

Ship Design

Parts

Manufacturing

Ship Configuration

Logistics Data

Program Data

DocumentsDesign Data

Change Mgmt

Integrated Data Environment (IDE)

Regional Maintenance Center

PLCS provides an opportunity to leverage Integrated Data Environments (IDE) developed for each ship program

Legacy Logistics &Support Systems

Sept. 10, 2008 6

ISE-6 Phase 2 Plans

• ISE-6 Team will work with– USSWG and DDG 1000 TDWG to ensure proper definition

and use of S1000D Business Rules

– DDG 1000 Combat Systems ILS Manager and NSWC PHD to demonstrate effective use of PLCS and S1000D for Combat Systems TM, involving both shipyard and ISEA

• ISE-6 Final Demonstration– Simulate a scenario in which Technical Publications and

Training Modules must be modified based on a design change initiated at the Shipbuilder and/or ISEA

– S1000D Data Modules (containing technical data and/or training) will be linked to HM&E and Combat Systems equipment and flagged for modification based on design changes

Sept. 10, 2008 7

Updated Requirements

ISE-6 Phase 2 Demo Scenario

DM 1.1

DM 1.2

DM 1.3

Chillers

Duct 1

Chiller 2

Duct 2

HVAC SysDrawing2

DM 2.3

DM 2.2

HVAC SysIETM 1

HVAC SysIETM 2

ISEA IDE (Radar)

DM 1.1

DM 1.2

Mod 1RadarIETM

Mod 1

DM 1.3Mod 2

DM 2.1

Mod 2RadarIETM

DM 2.2

Chiller 1

HVAC Sys

HVAC Ducts

HVAC SysDrawing1

Shipyard Design & IDE

Sept. 10, 2008 8

Reuse & DMC Naming Considerations

• ISE is working with DDG 1000 TDWG to help define Data Module Code (DMC) naming standard– Initial proposed standard focused exclusively on DDG 1000

• Goal is to recommend naming standard that can also be applied to other Navy programs– Need to reuse TM/DM from other programs– Need to reuse TM/DM from vendors– Need to ensure DDG 1000 TM/DM can be used on other

programs

• The danger is content cannot be effectively reused if DMC naming conventions are not properly defined– Once TMs are built, it is too late to easily change the DMC– Window of opportunity to define this properly is now

Sept. 10, 2008 9

Approach

Define use cases for data module usage

Define framework to discuss reuse and naming standards

Develop set of use cases for data module reuse

Analyze the current DMC naming recommendation against the use cases and determine gaps.

Propose approach to DMC naming standard

• Recommend DMC naming standard to satisfy as many use cases as possible

• Document use cases that are not satisfied (or only partially satisfied) and present to DDG 1000 TDWG and USSSWG for their consideration

Sept. 10, 2008 10

Data Module Use Cases

• Define DMC structure

• Create specific data module for a defined DMC structure

• Search for a specific data module, or set of data modules, in a CSDB– Update technical documentation – find specific data module

– Reuse existing data module – find an data module with required content

• Given a data module, search for set of related data modules:– Find where it is used within a specific technical document

– Find where it is used across multiple technical documents and/or training modules

– Find related data modules

• Identify data modules affected by a design change

Sept. 10, 2008 11

DMC Naming Standard

• Ideally DMC would uniquely identify DM which have same logistics requirements, e.g. maintenance procedures

• Two limitations– Unique DMC cannot be generated from existing identifiers

• Existing identifiers do not uniquely identify logistics requirements.

– DMC will be not be named consistently across all domains

• Too many different business rules / naming domains

Sept. 10, 2008 12

Using Existing Identifiers for DMC

Ideal

Too general

Too specific

Equip HSC

Equip HSC OEM Part

NumberOEM Part Number

Too general - Same DMC identifies items with different logistics requirementsProhibits reuse

Too specific - Different DMC identifies items with same logistics requirementsLimited reuse

Sys HSCSys HSC

UICUIC

RIC / APLRIC / APLLCNLCN

NSN / NIINNSN / NIINICNICN

Sept. 10, 2008 13

Business Rules / Naming Domains

DOD

Navy

DDG 1000

CVN 21

Virginia Army

AF

MoD

NATO

Part 1

OEM

Part 2

Program Program

ProgramProgram

Sept. 10, 2008 14

S1000D Reuse & Data Modules

• S1000D Data Module is the minimal unit of reuse– Data modules cannot include other data modules

• Only Publication Module includes data modules

– All data content has a unique DMC

• Need to be manageable size/scope for data module– Other programs manage at level of maintenance procedure,

not individual steps

• Choice of data module granularity limits what can be shared– If data modules implement maintenance procedures, then

cautions and warnings cannot effectively be shared• Not very effective to use PM to reference cautions and warnings

Sept. 10, 2008 15

Alternatives for Reuse & Data Modules

• Data module references allow data content to be used for different DMC

• IWS6 Common Schema (NSP)– Allows data modules to be referenced within a data module

– Can embed references within content• Can effectively share content, including warning and cautions

• S1000D Learning Modules– SCO data includes embedded references

• DMC reference

• Xpath – composed of URL, DMC, id (tag)

Sept. 10, 2008 16

Data Module Reuse Scenarios

• Same equipment can be used multiple times within the same system as well as in different systems

• Sub components can be used multiple times within a piece of equipment as well as in different pieces of equipment

• Same systems can be deployed on multiple ships and ship classes

• Same systems can be used across services or NATO.

• Equipment data module (DM) can be supplied by vendor, contractor, or government

• Equipment can be tracked by vendor part number, RIC, HSC

• System, equipment, and equipment sub-components can be revised independently

Sept. 10, 2008 17

DMC Strategy• Don’t expect that a DM will be named consistently across all

domains– DM will be named within a context when created– Can’t rely on DMC alone to identify content

• DM usage changes over time and cannot be predicted, it is separate from the identity of a DM

• Use metadata for searching, especially reuse• Pick best DMC naming strategy

– Do not use identifiers that are too general– Utilize lessons learned from other programs

• Maximize potential for reuse across domains– Adopt a general strategy that everyone can understand– Use generally used identifiers to maximize reuse– Find identifiers used most commonly across databases / systems– Identify consistent numbering system across domains that id common

information

Sept. 10, 2008 18

ISE-6 Recommendations (In-Progress)

• Model Id– Need to consider how to decompose structure into distinct

products

– If can be used elsewhere - use unique Model Id • Gun, radar, radio, water filtration

– If unique to the ship class – use Ship Model Id• DDG 1000, LCS, Virginia

Sept. 10, 2008 19

ISE-6 Recommendations (In-Progress)

• SNS– Do not use identifiers that are too general or too specific

– Alternatives• Use maintained SNS in chapter 8 as-is

– Useful at high level, need to fill gaps

• Use ICN from Preventive & Corrective Maintenance Database– ICN identifies the unique maintenance procedure

• Use HSC– Very little reuse, does not translate between ship classes.

• Use LCN– In ship acquisition world, this is often the HSC

Sept. 10, 2008 20

ISE-6 Recommendations (In-Progress)

• Metadata– Need to define required metadata

– Candidates• ESWBS / HSC / Functional Description

• Nomenclature

• OEM Part number

• RIC / APL

• NSN

– Need to define mapping from S1000D metadata to identifiers

• ConOps– Define data module usage rules

Backup Slides

Sept. 10, 2008 22

System Level Reuse

• Same equipment used within the same system on the same ship

• Same equipment used in different systems on same ship

• Same equipment within the same system on different ship classes

• Same equipment used in different systems on different ships

Sept. 10, 2008 23

Equipment Reuse Scenarios

• Vendor supplies DM, uses their naming convention

• Same subcomponent in same part– Same switch used multiple times in an amplifier

• Same subcomponent in different parts with same RIC– Same switch used in two different amplifiers

• Same subcomponent used in different parts with different functional use – Same switch used in electrical equipment and in a pump, which is hydro

equipment

Sept. 10, 2008 24

ISO STEP

NAVSEA

Ship Program

Standard Approved

Standard In Work

NSRP ISE Prototype Translators

Testing Framework

Information Model

Phases: RequirementsDefinition

Information Interoperability Specification

ProductionDeployment

ISE Information Model Methodology

ContractualSpecification

Deployment,Integration,

Testing

Technolo

gyB

usiness Decisions

Standardin Work

Sept. 10, 2008 25

Information Interoperability Roadmap

HVACISO AP 227:2005

PipingISO AP 227:2005

Ship ArrangementISO AP 215:2004

Ship Moulded FormsISO AP 216:2003

Ship StructuresISO AP 218:2004

Reference Data LibrariesISO 15926

Common Parts Catalog (CPC)

ElectricalISO AP 212:2001

Mechanical SystemsISO AP 227:2005

Cable TraysISO AP 227:2005

Finite Element Analysis

ISO AP 209:2001

Product Config / Geometry

ISO AP 203/214:1994

Product Life Cycle SupportISO AP 239

Systems EngineeringISO AP 233

Computational Fluid DynamicsISO AP 237

Logistics / SparesISO AP 232:2002

Outfit & FurnishingsNSRP 0428:1992

Manufacturing Support

ISO APs 224, 238, 240

Standard Approved

Information Model

Prototype Translators

Testing Framework

Deployment, integration,testing

Standard In Work

Ship Product Model Data

Ship StructuralEnvelope

DistributionSystems

Equipment /Subsystems

Life CycleMaintenance

Miscellaneous

HVACISO AP 227:2005

PipingISO AP 227:2005

Ship ArrangementISO AP 215:2004

Ship Moulded FormsISO AP 216:2003

Ship StructuresISO AP 218:2004

Reference Data LibrariesISO 15926

Common Parts Catalog (CPC)

ElectricalISO AP 212:2001

Mechanical SystemsISO AP 227:2005

Cable TraysISO AP 227:2005

Finite Element Analysis

ISO AP 209:2001

Product Config / Geometry

ISO AP 203/214:1994

Product Life Cycle SupportISO AP 239

Systems EngineeringISO AP 233

Computational Fluid DynamicsISO AP 237

Logistics / SparesISO AP 232:2002

Outfit & FurnishingsNSRP 0428:1992

Manufacturing Support

ISO APs 224, 238, 240

Standard Approved

Information Model

Prototype Translators

Testing Framework

Deployment, integration,testing

Standard In Work

Ship Product Model Data

Ship StructuralEnvelope

DistributionSystems

Equipment /Subsystems

Life CycleMaintenance

Miscellaneous

HVACISO AP 227:2005

PipingISO AP 227:2005

Ship ArrangementISO AP 215:2004

Ship Moulded FormsISO AP 216:2003

Ship StructuresISO AP 218:2004

Reference Data LibrariesISO 15926

Common Parts Catalog (CPC)

ElectricalISO AP 212:2001

Mechanical SystemsISO AP 227:2005

Cable TraysISO AP 227:2005

Finite Element Analysis

ISO AP 209:2001

Product Config / Geometry

ISO AP 203/214:1994

Product Life Cycle SupportISO AP 239

Systems EngineeringISO AP 233

Computational Fluid DynamicsISO AP 237

Logistics / SparesISO AP 232:2002

Outfit & FurnishingsNSRP 0428:1992

Manufacturing Support

ISO APs 224, 238, 240

Standard Approved

Information Model

Prototype Translators

Testing Framework

Deployment, integration,testing

Standard In Work

Ship Product Model Data

Ship StructuralEnvelope

DistributionSystems

Equipment /Subsystems

Life CycleMaintenance

Miscellaneous

HVACISO AP 227:2005

PipingISO AP 227:2005

Ship ArrangementISO AP 215:2004

Ship Moulded FormsISO AP 216:2003

Ship StructuresISO AP 218:2004

Reference Data LibrariesISO 15926

Common Parts Catalog (CPC)

ElectricalISO AP 212:2001

Mechanical SystemsISO AP 227:2005

Cable TraysISO AP 227:2005

Finite Element Analysis

ISO AP 209:2001

Product Config / Geometry

ISO AP 203/214:1994

Product Life Cycle SupportISO AP 239

Systems EngineeringISO AP 233

Computational Fluid DynamicsISO AP 237

Logistics / SparesISO AP 232:2002

Outfit & FurnishingsNSRP 0428:1992

Manufacturing Support

ISO APs 224, 238, 240

Standard Approved

Information Model

Prototype Translators

Information Model

Prototype Translators

Testing Framework

Deployment, integration,testing

Standard In Work

Ship Product Model Data

Ship StructuralEnvelope

DistributionSystems

Equipment /Subsystems

Life CycleMaintenance

Miscellaneous

Sept. 10, 2008 26

ISO 10303-239Product Life Cycle Support (PLCS)

Change Management

Product Structure

Requirements Management

ScheduleActivities

Organizations

Property

Classification

Approvals, Security, Status

Maintenance

Support Tasks

APSI

Support History

Messaging

PLCS

• PLCS provides an integrated data model with a scope that is a holistic view encompassing the entire product life cycle

ISE-6

• Lifecycle community needs to access information defined during acquisition

● Acquisition community can also benefit from the use of PLCS to exchange integrated design and logistics information

Sept. 10, 2008 27

ISE-6 PLCS Approach

Change Management

Product Structure

Requirements Management

ScheduleActivities

Organizations

Property

Classification

Approvals, Security, Status

Maintenance

Support Tasks

APSI

Support History

Messaging

PLCS

ISE-6 Schema

Navy LogisticsData Requirements

STEP Shipbuilding APsDesign and Manufacturing

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 maintains linkage to

design data

ISE Information ModelsLink back to Design Data