CFIHOS Data Model

C-DM-001 version 1.5.1

CFIHOS 1.5.1 © 2023 by IOGP is licensed under Attribution 4.0 International. To view a copy of this license, visit http://creativecommons.org/licenses/by/4.0/
 Notes
This page provides some explanation of how to read the data model. The tool used to generate the drawings is ER Studios and so
some of the conventions are driven by that tool. As a result this page does not try to provide a comprehensive legend but highlights
key points the user should be aware of.

Indicates a subtype. A subtype is a sub-grouping of the entities in an entity type that is meaningful to the organization and
that shares common attributes or relationships distinct from other subgroups. Subtypes inherit all supertype attributes.
The parent entity is indicated via the arrow. By convention subtypes do not have a relationship verb.
The significance of dashed vs solid relationship lines is due to the notation selected in ER Studios. For optional
vs relationships, IE (Crows Feet ) uses dashed relationship lines, whereas the Martin notation uses solid lines for all
relationships.
Starting point : the tag
Plant breakdown structure : the relationships view
Plant breakdown structure :
the definitions view
Plant breakdown structure : the attributes view
Other tag inbound relationships view
Other tag inbound definitions view
Other tag inbound attributes view
The tag attributes view
Tag and its relationship to tag class
Tag to equipment : the relationships view
Tag to equipment : the definitions view
Tag to equipment : the attributes view
Equipment attributes view
Checkpoint 1 : Summary after review of the first third of the data model
As was
Checkpoint 1 : Summary after review of the first third of the data model
As is

Solid line for identifying relationships, dashed line for non identifying ones
Classes : the relationships view
Classes: the definitions view
Classes: the attributes view
Properties: the conceptual view on relationships
Properties: the logical view on relationships
Properties : the definitions view
Properties : the attributes view
Property
use : the
attributes
view
Process activity and stream, their class and their properties: the relationships view
Process
activity
and
stream,
their class
and their
properties:
the
definitions
view
Process
activity
and stream,
their class
and
their
properties:
the
attributes
view
Cases : the
relationships
view
Cases : the
definitions
view
Cases : the attributes view
Properties, classes and units of measure : the relationships view
Properties, classes and units of measure : the definitions view
Properties, classes and units of measure : the attributes view
Properties, tags, equipment and units of measure : the relationships view
Properties, classes and units of measure : the definitions view
Properties, classes and units of measure : the attributes view
Checkpoint 2 : Summary after review of the second third of the data model
As was
Checkpoint 2 : Summary after review of the second third of the data model
As is

Solid line for identifying relationships, dashed line for non identifying ones
Disciplines and document types : the relationships view
Disciplines
and
document
types : the
definitions
view
Disciplines
and
document
types :
the
attributes
view
Discipline document type : zoom on the attributes
Document master : the relationships view
Document master : the definitions view
Document master : the attributes view
Document revision : the relationships view
Document revision : the simplified relationships view
Document
revision :
the
definitions
view
Document
revision :
the
attributes
view
Document revision : zoom on the attributes
Checkpoint 3 : Summary after review of the third third of the data model
As was
Checkpoint 3 : Summary after review of the third third of the data model
As is

Solid line for identifying relationships, dashed line for non identifying ones
JIP33:
the relationships view – what JIP33 would add vs what is already present in CFIHOS data model
How to link tag or equipment classes to source standards : the relationships view
How to link tag or equipment classes to source standards : the definitions view
How to link tag or equipment classes to source standards : the attributes view
Source standard document and data requirements : the relationships view
Source standard document and data requirements : the relationships view
Source standard document and data requirements : the definitions view
Source standard document and data requirements : the definitions view
Source standard document and data requirements : the attributes view
Source standard document and data requirements : the attributes view
From the source standard document and data requirements to the purchase order - the
relationships view (1/4)
From the source standard document and data requirements to the purchase order - the
relationships view (2/4)
From the source standard document and data requirements to the purchase order - the
relationships view (3/4)
Purchase order VDDRs: the relationships view – the case of the tag
Purchase order VDDRs: the relationships view – the case of the model
From the source standard document and data requirements to the purchase order - the
relationships view (4/4)
From the
source
standard
document
and data
requirements
to the
purchase
order - the
relationships
view (4/4) –
including
views
Purchase order VDDRs: the relationships view
Purchase
order
VDDRs:
the
definitions
view
Purchase
order
VDDRs:
the
attributes
view
Checkpoint 4 : Summary of the vendor document and data requirements

Solid line for identifying relationships, dashed line for non identifying ones
Overview of the whole model
Overview of tag or equipment class relationships
Overview of CFIHOS alternate code mapping capabilities
Overview of pick lists
The relationship between the logical model and the CSV files :
1) tag and equipment class
The relationship between the logical model and the CSV files :
2) tag and equipment class property
The relationship between the logical model and the CSV files :
3) Property, pick list and unit of measure
The relationship between the logical model and the CSV files :
4) Discipline and document type