120 likes | 267 Views
OASIS DEX workshop “Reference data” 3 February 2004 - Oslo Trine Hansen - DNV. 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?
E N D
OASIS DEX workshop “Reference data” 3 February 2004 - Oslo Trine Hansen - DNV
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? PLCS Inc. (c) 2002
FrigatePLCS DB NDLOISO 15926 RDL ISO 15926 RDL Where is the reference data stored? ISO 15926 RDL • 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 • External reference data • International standards • Vendor catalogues • Breakdowns for general or domain purposes • Etc. 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 PLCS Inc. (c) 2002
Capability Cap_001“Attribute values as reference data” PLCS Inc. (c) 2002
Capability Cap_002“Instances as reference data” 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 PLCS Inc. (c) 2002
Documentation of instantiated Cap’s • CAP_002: Instances as reference data PLCS 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. PLCS Inc. (c) 2002
Cap_001 - TUTILOM PLCS Inc. (c) 2002
Application Application ISO 15926RDL PLCS data model Dexlib Reference Data DEXLib and / or ISO 15926 RDL Registration of Reference Data in spreadsheet Registration of Reference Data in spreadsheet Registration of Reference Data in spreadsheet Validation andharmonisationof Reference Data Direct use of reference datain ISO 15926 RDL Existing batch loading routines RDS Export DEX Team 1Identification of Reference Data Spreadsheet DEX Team 2Identification of Reference Data Use of ISO 15926 reference datathrough dexlib DEX Team <n>Identification of Reference Data PLCS Inc. (c) 2002
Why ISO 15926 RDL? • It’s already there! PLCS Inc. (c) 2002