1. OASIS DEX workshop “Reference data” 3 February 2004 - Oslo Trine Hansen - DNV

2. 2 PLCS 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?

3. 3 PLCS Inc. (c) 2002 Where is the reference data stored? Frigate PLCS DB NDLO ISO 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

4. 4 PLCS 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

5. 5 PLCS Inc. (c) 2002 Capability Cap_001 “Attribute values as reference data”

6. 6 PLCS Inc. (c) 2002 Capability Cap_002 “Instances as reference data”

7. 7 PLCS 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

8. 8 PLCS Inc. (c) 2002 Documentation of instantiated Cap’s CAP_002: Instances as reference data

9. 9 PLCS Inc. (c) 2002 Documentation of instantiated Cap’s CAP_002: Instances as reference data CAP_002_1 : Overhaul and clean task (COMAN value) ' ' : (empty) : Task ' ' : ' ‘ : Maintenance concept type: overhaul and clean task ' ' : This Capability instance is included on diagram NDLO_P1_11.

10. 10 PLCS Inc. (c) 2002 Cap_001 - TUTILOM

11. 11 PLCS Inc. (c) 2002 Pilots – registration of ref.data Registration of Reference Data Registration of Reference Data Registration of Reference Data Validation and harmonisation of Reference Data ISO 15926 RDL Application (PDTF) Existing batch loading routines RDS: application for handeling viewing, upload and export of data to/from ISO 15926 RDL DEX Team 1 Identification of Reference Data DEX Team 2 Identification of Reference Data DEX Team Identification of Reference Data Registration of Reference Data Registration of Reference Data Registration of Reference Data Dexlib / Reference Data Temporary storage No harmonisation routines exists Norwegian pilots PLCS / OASIS RDS

12. 12 PLCS Inc. (c) 2002 DEXLib and / or ISO 15926 RDL DEX Team 1 Identification of Reference Data DEX Team 2 Identification of Reference Data DEX Team Identification of Reference Data Registration of Reference Data in spreadsheet Registration of Reference Data in spreadsheet Registration of Reference Data in spreadsheet Validation and harmonisation of Reference Data PLCS data model Dexlib Reference Data Direct use of reference data in ISO 15926 RDL Use of ISO 15926 reference data through dexlib Spreadsheet Export Existing batch loading routines RDS Application ISO 15926 RDL Application

13. 13 PLCS Inc. (c) 2002 Why ISO 15926 RDL? It’s already there!