OASIS DEX workshop “Reference data”

3 February 2004 - Oslo

Trine Hansen - DNV

2PLCS Inc. (c) 2002

Criteria for identification of reference data

Criteria for selection of Reference Data:

Can the data be reused? Are the data references for validation and QA activities? Is the intension to extend the data domain, i.e. add new

classes?

3PLCS Inc. (c) 2002

Where is the reference data stored?

FrigatePLCS DB

NDLOISO 15926 RDL

ISO 15926 RDL

External reference data• International standards•Vendor catalogues •Breakdowns for general or domain purposes• Etc.

Internal reference data•Check of legal values from IZAR •Critical items •Repair options dependent on mission •Component information for repair•Component information •Breakdown of ship

ISO 15926 RDL

4PLCS Inc. (c) 2002

NDLO specific reference data

Examples of NDLO specific Reference Data are: Physical things, e.g. diesel engine, pump, mineral oil Functions, e.g. propulsion system, cooling system, compartment, fuel Activities, e.g. maintenance task, navigation task Parts lists Plans Standards Rules and regulations Procedures Common specifications Properties, e.g. weight, length… The specialisation or part of structure of interest The component information publicly available. Component (spare part) information defined according to project needs. Information forms and datasheets including the unique and

unambiguous definition of their content

5PLCS Inc. (c) 2002

Capability Cap_001“Attribute values as reference data”

6PLCS Inc. (c) 2002

Capability Cap_002“Instances as reference data”

7PLCS Inc. (c) 2002

Procedure for registration of reference data

Identify the reference data Reference data is either related to Cap_001 or Cap_002 Proper documentation of each instantiation All reference data systemized into spreadsheets Reference data transferred from spreadheets into ISO 15926

Registered as a “dictionary” outside the existing structure in RDL Linking reference data into the existing structure

Available through internet

8PLCS Inc. (c) 2002

Documentation of instantiated Cap’s

CAP_002: Instances as reference data

Parameter Value

Classification_assignment.role ‘<opt role>’ (a text that uniquely identifies the role of the classification; shall be empty for the time being)

Classification_assignment.items <types of classified instances> (the entity data types of the one or several objects that shall be classified)

Classification_assignment.assigned_class

External_class -- (the External_class that is created as part of this capability)

external_class.id ‘<class id>’ (the unique identifier of the class that represents the attribute value in RDL)

external_class.description ‘<opt class description>’ (description of the external class)

external_class.name ‘<class name>' (name of the external class)

external_class_library.id (use URI) ‘POSC Caesar Reference Data Library’

external_class_library.description ‘The ISO 15926 compliant RDL of POSC Caesar Association’

9PLCS Inc. (c) 2002

Documentation of instantiated Cap’s

CAP_002: Instances as reference data

CAP_002_1 : Overhaul and clean task (COMAN value)'<role>' : (empty)<types of classified instances> : Task'<class id>' : <unique identifier of the class in the RDL>'<opt class description>‘ : Maintenance concept type: overhaul and clean task'<class name>' : <name of the class as in the RDL>

This Capability instance is included on diagram NDLO_P1_11.

10PLCS Inc. (c) 2002

Cap_001 - TUTILOM

Pdb02aec_Marcap

Pdb02aec_Marcah LCN Pdb02aec_Titulom

0 SHIP, GENERAL 0 0A 0A INTEGRATED PLATFORM SYSTEM 0A 1 0A11 HULL, GENERAL 1 11 0A1111 SHELL AND SUPPORTING STRUCTURE 1 12 0A1112 HULL STRUCTURAL BULKHEADS 12 121 0A111211 LONGITUDINAL STRUCTURAL BULKHEADS 12 122 0A111212 TRANSVERSE STRUCTURAL BULKHEADS 122 1221 0A11121211 TRANSVERSE STRUCTURAL BULKHEADS 12 123 0A111213 TRUNKS, TANKS & VOID SPACES 1 13 0A1113 HULL DECKS 1 14 0A1114 HULL PLATFORMS 1 15 0A1115 DECK HOUSE STRUCTURE 1 16 0A1116 SPECIAL STRUCTURES 1 17 0A1117 MAST HOUSE 1 18 0A1118 FOUNDATIONS 18 182 0A111811 PROPULSION PLANT FOUNDATIONS 18 183 0A111812 ELECTRIC PLANT FOUNDATIONS 18 184 0A111813 C4 & SURVEILLANCE FOUNDATIONS 184 1842 0A11181311 NAVIGATION SYSTEM FOUNDATIONS 184 1843 0A11181312 COMMUNICATIONS FOUNDATIONS

184 1846 0A11181313 SURVEILLANCE SYSTEMS(SHIP SENSORS)

FOUNDATIONS 184 1847 0A11181314 COUNTERMEASURES FOUNDATIONS 184 1848 0A11181315 COMBAT MANAGEMENT SYSTEM (CMS) FOUNDATIONS 18 185 0A111814 AUXILIARY SYSTEMS FOUNDATIONS 18 186 0A111815 OUTFIT AND FURNISHING FOUNDATIONS 18 187 0A111816 WEAPONS FOUNDATIONS 1 19 0A1119 MAGAZINES 0A 2 0A12 PROPULSION, GENERAL 0A 3 0A13 ELECTRIC, GENERAL

12PLCS Inc. (c) 2002

DEXLib and / or ISO 15926 RDL

DEX Team 1Identification ofReference Data

DEX Team 2Identification ofReference Data

DEX Team <n>Identification ofReference Data

Registration ofReference Datain spreadsheet

Registration ofReference Datain spreadsheet

Registration ofReference Datain spreadsheet

Validation andharmonisationof Reference Data

PLCS data model

Dexlib Reference Data

Direct use of reference datain ISO 15926 RDL

Use of ISO 15926 reference datathrough dexlib

Spreadsheet

Export

Existing batch loading routines

RDS

ApplicationISO 15926RDL

Application

13PLCS Inc. (c) 2002

Why ISO 15926 RDL?

It’s already there!