Symbols relationship class of relationship class of class of relationship Name RDS Identifier/URI Relationships Classes Name Level 2/Class of class Level.

Slides:



Advertisements
Similar presentations
SDMX in the Vietnam Ministry of Planning and Investment - A Data Model to Manage Metadata and Data ETV2 Component 5 – Facilitating better decision-making.
Advertisements

Radiopharmaceutical Production
Composition CMSC 202. Code Reuse Effective software development relies on reusing existing code. Code reuse must be more than just copying code and changing.
Machine Independent Assembler Features
United Nations Statistics Division Principles and concepts of classifications.
DDR Modelling Patterns
T h e U n i v e r s i t y o f B r i t i s h C o l u m b i a Bi-Level Image Compression EECE 545: Data Compression by Dave Tompkins.
TC3 Meeting in Montreal (Montreal/Secretariat)6 page 1 of 10 Structure and purpose of IEC ISO - IEC Specifications for Document Management.
Object-Oriented PHP (1)
The Hierarchical Scan Description Language (HSDL) was developed by to complement BSDL.
Data Quality Class 3. Goals Dimensions of Data Quality Enterprise Reference Data Data Parsing.
QMS Documentation Click the mouse to advance slides and animations in this slide show…
Prepared by Long Island Quality Associates, Inc. ISO 9001:2000 Documentation Requirements Based on ISO/TC 176/SC 2 March 2001.
C++ fundamentals.
ASPEC Internal Auditor Training Version
11 Data Interface Standard for Accounting Software Project Progress Report China National Audit Office June, 2015.
1 SPL Technology Presentation The Technology of Structured Product Labeling Presented by Robert H. Wallace 06 June 2004.
Object Oriented Software Development
Module 3: Table Selection
DATA MODELLING TOOLS FOR ORGANISING DATABASES. For a database to be organised and logical, it must be well-designed and set out. In such cases, the databases.
Project “European CDDA and INSPIRE”: scope, transformation workflow and mapping rules INSPIRE Conference 2014 Workshop: Implementing Existing European.
DDR Modelling Patterns Bit data, Casing/Liner/Tubing, and Cement.
Writing Classes (Chapter 4)
OBJECT ORIENTED PROGRAMMING CONCEPTS ISC 560. Object-oriented Concepts  Objects – things names with nouns  Classes – classifications (groups) of similar.
By: Md Rezaul Huda Reza 5Ps for SE Process Project Product People Problem.
DICOM Audit Messages. Functional Structure Three components: –Event Description (DICOM) –Audit Policy (Local) –Message Definition (DICOM) Real World Event.
Database Design Sections 6 & 7 Second Normal Form (2NF), Unique Identifiers (UID), Third Normal Form (3NF), Arcs, Hierarchies and Recursive relationships.
Templates. The Problem Supplier X A range on the data sheet.
SDMX Standards Relationships to ISO/IEC 11179/CMR Arofan Gregory Chris Nelson Joint UNECE/Eurostat/OECD workshop on statistical metadata (METIS): Geneva.
Abstract Syntax Notation ASN.1 Week-5 Ref: “SNMP…” by Stallings (Appendix B)
GlencoIS – Interoperability through Reference Data ISO15926 Reference Data Some Template Ref Data Issues (Relevant to coordinating JORD take-up) PCA /
Adobe Dreamweaver CS3 Revealed CHAPTER SIX: MANAGING A WEB SERVER AND FILES.
RELATORS, ROLES AND DATA… … similarities and differences.
DDR Drilling and Well model Status – core group meeting.
ITEC 3220A Using and Designing Database Systems Instructor: Prof Z. Yang Course Website: 3220a.htm
Chapter 6 Introduction to Defining Classes. Objectives: Design and implement a simple class from user requirements. Organize a program in terms of a view.
C. Huc/CNES, D. Boucon/CNES-SILOGIC Producer-Archive Interface Specification.
Domain Classes – Part 1.  Analyze Requirements as per Use Case Model  Domain Model (Conceptual Class Diagram)  Interaction (Sequence) Diagrams  System.
Winter 2011SEG Chapter 11 Chapter 1 (Part 1) Review from previous courses Subject 1: The Software Development Process.
Domain Model A representation of real-world conceptual classes in a problem domain. The core of object-oriented analysis They are NOT software objects.
WG3 Presentation to TC184/SC 4 Closing Plenary Baltimore, USA 23 Oct 2015 WG3 Oil, Gas, Process and Power Paul van Exel, Convener Nils Sandsmark, Deputy.
Synchronise work on DEXs and reference data between PLCS pilots and OASIS/PLCS Workshop #3 10 – 11 November 2004.
Microsoft Office 2013 Try It! Chapter 4 Storing Data in Access.
Subscribers – DatA Extensions
Pål Rylandsholm 16 June 2009 DRAFT DDR Phase 2 Status EPIM RUF meeting June 16th 2009.
Data Modeling and Entity-Relationship Model I
GDSN Mandatory Attributes -- Simplified 3 December 2008.
Combined Metamodel for UCM Contributed by Anthony B. Coates, Londata 17 February, 2008.
DOMAIN CLASSES – PART 1 BTS430 Systems Analysis and Design using UML.
Elements Of Modeling. 1.Data Modeling  Data modeling answers a set of specific questions that are relevant to any data processing application. e.g. ◦
Chapter 5: Structural Modeling
OGP Seabed Survey Data Model (SSDM)
Graphical Data Engineering
DDR Modelling Patterns
DDR Modelling Patterns
Data Dictionaries ER Diagram.
Building Configurable Forms
SYS466 Domain Classes – Part 1.
Development of a specification
Daily Drilling Report Phase 2
ITEC 3220A Using and Designing Database Systems
Machine Independent Assembler Features
EPIM RUF meeting June 16th 2009
Symbols Classes Relationships Name
Metadata Updates (for S / 4
Machine Independent Assembler Features
Radiopharmaceutical Production
Domain Model: Visualizing Concepts
August 2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Still More LB156 Comment Resolutions Date.
August 2019 Project: IEEE P Working Group for Wireless Personal Area Networks (WPANs) Submission Title: Still More LB156 Comment Resolutions Date.
Presentation transcript:

Symbols relationship class of relationship class of class of relationship Name RDS Identifier/URI Relationships Classes Name Level 2/Class of class Level 1/Class of individual COICOI COIPO Entity type (when relevant) Level 0/Individual COIPO Entity type (when relevant) # Name Exist in RDL Name To be added to RDL Name To be deleted from RDL Name To be modified COICOI Entity type (when relevant) COICOI Entity type (when relevant) COICOI Entity type (when relevant) Template Signature Instance CLASS IN FOCUS COIPO Object in focus

6 “Sectional drawing”, Generic STRING IN ROLE 2 id COI COCOI id OR/CORWS ES OR/CORWS This involves establishing a relationship from the ‘class in focus’ to a string that is said to be an identifier of a class of “documents” that contains a sectional drawing for members of the class. It is not known to us what the document structure used by the actual company is, and there is no structure that is “standard” across companies. In addition, the string we have been presented may just be a “local” name used in the sending application. Hence we are in this context not in the position to make any further statements regarding the string. This should therefore only be modelled for particular organisations, and not be part of a standard RDL. The only correct approach is therefore to reference a document identification code. This construct does not include any “context” data; e.g. classification of the string or the class of relationship to record who made the statement. (If the sending application has additional information we may state it, but using a different template signature). ELECTRICAL PRESSURE TRANSMITTER COIPO ARTEFACT CLASS IN FOCUS ABCDEFGHI DOCUMENT IDENTIFICATION CODE ARTEFACT IN FOCUS. DOCUMENT IDENTIFIER CODE STRING IN FOCUS. DOCUMENT ABCDEFGHI COIO It is not known to us what the document structure used by the actual company is, and there is no structure that is “standard” across companies. This should therefore only be modelled for particular organisations. The only correct approach is therefore to reference a document number HOLD ? 1 2 SECTIONAL DRAWING IDENTIFIER CODE STRING CLASS SECTIONAL DRAWING REFERENCE (RDS ) CORWS IDENTIFIER REFERENCE (RDS ) CORWS NOTE The modelling of the product classes, document classes etc. is out of scope for this template signature. It can be added as an extension without violating the present modelling, which is a “shortcut” for the relevant part of the full model, and still valid when the additional data is added.

id Datum Reference I COI COCOI id OR/CORWS ES OR/CORWS DRILL BIT 13 3/4 NPS AI DRILL BIT THE ACTUAL DRILL BIT NOW ABCDEFGHI NNNNNN IDENTIFICATION CODE ARTEFACT IN FOCUS. IDENTIFIER STRING IN FOCUS. KELLY #NNNNNNN NOW AI 1 2 (DRILL BIT?) DATUM IDENTIFIER REFERENCE (RDSXXXXXX) CORWS KELLY COIPO KELLY BUSHING IDENTIFIER STRING CLASS STRING IN ROLE 2 RF LENGTH TRUE VERTICAL DEPTH TO MEASURING POINT RELATIVE RKB (RDS ) 455 m IP P TRUE VERTICAL DEPTH RELATIVE TO RKB TEMPLATE SIGNATURE Role 1: THE ACTUAL “WELL OBJECT” NOW Role 2: STRING IN ROLE 2 Role 3: TRUE VERTICAL DEPTH TO MEASURING POINT RELATIVE Role 4: 455 Role 5: METRE 3 Possessor Property IDENTIFIER REFERENCE (RDS ) CORWS “WELL OBJECT” DATUM IDENTIFIER REFERENCE (RDSXXXXXX) id TRUE VERTICAL DEPTH RELATIVE TO RKB (RDS ) “WELL OBJECT” 4 5 COIPO COFO SPD COIP ISO INDIRECT PROPERTY ISO IDENTIFICATION ISO PROPERTY QUANTIFICATION ++++ * * RKB? KELLY = KELLY BUSHING? KELLY DRIVE ROTARY TABLE DDR DATUM CLASS

“OBJECT IN FOCUS” 10 Mapping of “text attributes” IP-Class 1 9 RDS RDS RDS RDS RDS RDS ATEX group ATEX category Temperature class Gas-group Explosion protection COCOId IEC INGRESS PROTECTION CODE ASSIGNMENT CLASS 7 8 This approach is used for all cases where “validation tables” (EqHub terminology) or “standard options” are involved. NB! “Text” attribute is mapped to a specialisation relationship represented COIPO pattern COId 3 IP66 APPARATUS IEC ES IP66 2 ES 2 IP66 ES 2 5 IEC INGRESS PROTECTION CODE STRING CLASS RF COCOInd 6 IEC INGRESS PROTECTED APPARATUS CLASS IP6X PPARATUS IEC IPX6 APPARATUS IEC ARTEFACT INGRESS PROTECTED APPARATUS

File for use when mapping IP-class Code used in external applications PCA RDL class name PCA RDL class identifier PCA RDL class description (not necessarily the definition) The RDS# that is presented to EqHub (according to agreement with SHAREcat) is the RDS# for the class IEC INGRESS PROTECTION CODE STRING CLASS that holds the codes used in external applications. For a particular instance the RDS# for the appropriate member of the class IEC INGRESS PROTECTED APPARATUS CLASS is used in a transfer file

Mapping of Drill bit “Size (in)” Size (in) 1 RDS RDS RDS RDS RDSxxxxxxx xxxxx COCOId DRILL BIT CODE ASSIGNMENT CLASS represented COIPO pattern COId 3 DRILL BIT 13 3/4 NPS 13 3/4 NPS ES 2 DRILL BIT CODE STRING CLASS RF COCOInd DRILL BIT CLASS DRILL BIT THE ACTUAL DRILL BIT NOW ARTEFACT COIPO THE ACTUAL DRILLING ACTIVITY THE ACTUAL DRILLED SECTION DRILL BIT SIZE TEMPLATE SIGNATURE Role 1: THE ACTUAL DRILL BIT NOW Role 2: THE RDS# FOR THE CLASS IDENTIFIED BY THE APPROPRIATE MEMBER OF “DRILL BIT CODE STRING CLASS” Role 3: THE APPROPRIATE STRING THAT IS A MEMBER OF “DRILL BIT CODE STRING CLASS” THE PREVIOUS DRILLING ACTIVITY THE ACTUAL CASING STRING SECTION THE ACTUAL CEMENTED SECTION THE ACTUAL CEMENTING JOB

Mapping of Drill bit “Size (in)” Code used in external applications PCA RDL class name PCA RDL class identifier PCA RDL class description (not necessarily the definition) DEFINE SIMILAR TABLE FOR DRILL BIT SIZES

“Make”, Generic STRING IN ROLE 2 #nnnnnnn id COMPANY COI COMPANY NAME IDENTIFICATION COCOI id OR/CORWS ES PO MANUFACTURING COMPANY NAME REFERENCE (RDS ) OR/CORWS Only indicative. Need further modelling to arrive at a proposed structure Default from the signature/template. HOLD. In the context of this template signature we have assumed that this is not known. IDENTIFIER REFERENCE (RDS ) COMPANY NAME AI DRILL BIT THE ACTUAL DRILL BIT NOW NOTE The modelling of the manufacturing activities, products, company etc. is out of scope for this template signature, but could be added without violating the present modelling, which is a “shortcut” for the full modelling. COMPANY REGISTERED NAME IDENTIFICATION DRILL BIT 13 3/4 NPS ACME INC SUPERDUPER DRILL BIT 13 3/4 NPS id OR

id Size Reference ES OR/CORWS DRILL BIT 13 3/4 NPS AI DRILL BIT THE ACTUAL DRILL BIT NOW 1 2 DRILL BIT CODE ASSIGNMENT CLASS (RDSXXXXXX) CORWS DRILL BIT IDENTIFIER STRING CLASS RF LENGTH TRUE VERTICAL DEPTH RELATIVE TO RKB (RDS ) 455 m IP P TRUE VERTICAL DEPTH RELATIVE TO RKB TEMPLATE SIGNATURE Role 1: THE ACTUAL DRILL BIT NOW Role 2: STRING IN ROLE 2 Role 3: TRUE VERTICAL DEPTH RELATIVE TO RKB Role 4: 455 Role 5: METRE 3 Possessor Property IDENTIFIER REFERENCE (RDS ) CORWS “WELL OBJECT” DATUM IDENTIFIER REFERENCE (RDSXXXXXX) id TRUE VERTICAL DEPTH (RDS ) “WELL OBJECT” 4 5 COIPO COFO SPD COIP ISO INDIRECT PROPERTY ISO IDENTIFICATION ISO PROPERTY QUANTIFICATION ++++ RDSxxxxxxx represented pattern COId 13 3/4 NPS