PLCS and S1000D Technical Issues

2

ISE 6 Phase 2 Technical Issues

• S1000D PLCS DEX– Need to exchange S1000D data modules and relationships to

product model– Listed under Business DEX section of plcs-resources

• But non content defined

• Linkage between product data and data modules– If design change occurs, need to identify the data modules (TM

and training) affected so they can be reviewed and updated.

3Updated

Requirements

Technical Issue – Linkage

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.2Mod 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

4

Linkage• If design change occurs, need to identify the data modules (TM and

training) affected so they can be reviewed and updated.– 1. Create Ship Alt

• Identify affected support systems• Identify affected components

– 2. List DM related to affected components– Need mechanism to link a DM to equipment.

• Can’t always rely on DMC to provide linkage– Data modules may have been authored by vendor or other program– May utilize different business rules (applied at time of creation, not use)

• Must be relationship – – DMC is generated based on business rules in effect at the time DM was

created– Example – pump TM generated for carrier, reused on DDG

– Assume dual use DM used to manage training and tech pubs

5

EuroSTEP Approach

6

Linkage• Equipment level TM

– PM linked to piece of equipment– TDMIS would related PMC to APL

• System level TM– PM linked to system– Individual DM linked to equipment/components within system

• DM where used– Need to derive inverse relationship from PM– LSAR – already maintains relationships

7

Questions / Issues• Linkage for DMC, PMC to product structure

– DDG 1000 linker must identify linkage

• GIA 0007