Decision Tree for Industry domain data model adoption

Business tenant has the option to not adopt industry standards, however, may use this decision tree as reference)

PROJECT INPUT

Project Requirement Business Process Data Type

Start
Is the data type
Is the project’s project requirements, business
Is the project 1 No
2 process and data type matches considerably No
3 a master/
No
requirement to reference data?
with below table?
serve information to
Open Subsurface
Data Universe (Note: please refer to appendix for more comprehensive and clearer list)
Upstream data Is the data a
(OSDU) Data • Tags and Equipment
Platform? (snippets from full list in • Capital Facility Data Yes normalized 4
appendix) : Entities transaction data? No
• Additives • Master Document
• Applications Register
• Areas
Yes • Contracts/ Agreements
• Entitlement
Data Type

• Production
• Rate Schedule
Yes

upstream exploration and designing, operating,

production maintaining or
decommissioning
plant facilities
Business
Process

DATA MODEL Yes Yes

STANDARD TO USE

OSDU PPDM CFIHOS IDM Customized

Internal
Decision Tree for Industry domain data model adoption
Example 1: Project that captures PI information with performance reading of upstream equipment
PROJECT INPUT
Project Requirement Business Process Data Type
(Capture PI information with (upstream) (Equipment and Readings)
performance reading)

Start
Is the data type
Is the project’s project requirements, business
Is the project 1 No
2 process and data type matches considerably No
3 a master/
reference data? No
requirement to with below table?
serve information to Project
Open Subsurface requirement
not related to (Note: please refer to appendix for more comprehensive and clearer list)
Data Universe
OSDU
Upstream data Is the data a
(OSDU) Data • Tags and Equipment
Platform? (snippets from full list in • Capital Facility Data
Yes normalized 4
appendix) : Entities transaction data? No
• Additives • Master Document
• Applications Register
• Areas
Yes • Contracts/ Agreements
• Entitlement
Data Type

• Production
• Rate Schedule
Yes

upstream exploration and designing, operating,

production maintaining or
decommissioning
plant facilities
Business
Process

DATA MODEL Yes [YES] Project Yes

STANDARD TO USE requirement, data type
is heavily biased towards
OSDU PPDM equipment and CFIHOS IDM Customized
Internal
operation of facilities
Decision Tree for Industry domain data model adoption
Example 2: Project that captures asset expenditure data for upstream business
PROJECT INPUT
Project Requirement Business Process Data Type
(Capture asset expenditure for (upstream) (asset, work order, notification, cost center, GL posting)
maintenance)

Start
Is the data type
Is the project’s project requirements, business
Is the project 1 No
2 process and data type matches considerably No
3 a master/ No
requirement to reference data?
with below table?
serve information to [NO] Project
[NO} The project
Open Subsurface requirement
requirement &
Data Universe not related to (Note: please refer to appendix for more comprehensive and clearer
datalist)
type do not Yes
OSDU Upstream data Is the data a
(OSDU) Data • Tags and Equipment overlap greatly
Platform? (snippets from full list in • Capital Facility Data
with PPDM or normalized 4
appendix) : Entities CHIFOS data transaction data? No
• Additives • Master Document type & business
• Applications Register process area
• Areas
Yes • Contracts/ Agreements
• Entitlement
Data Type

• Production
• Rate Schedule
Yes

upstream exploration and designing, operating,

production maintaining or [YES] Many of the data
decommissioning type and heavy
plant facilities requirement on
Business
Process

financial reporting are

DATA MODEL Yes available in IDM
Yes
STANDARD TO USE

OSDU PPDM CFIHOS IDM Customized

Internal
 APPENDIX

Internal
Appendix: Decision Tree for Industry domain data model adoption
PPDM
Legend: Anchor Tables

Data Model Data Domain/ Business Data Type Business Requirement/ Process
PPDM 53 subject area, grouped as below: manage upstream exploration and production data

Internal
Appendix: Decision Tree for Industry domain data model adoption
CFIHOS
Legend: Anchor Tables

Data Model Data Domain/ Business Data Type Business Requirement/ Process
CHIFOS Tags and Equipment designing, operating, maintaining or decommissioning
Capital Facility Data Entities, e.g: industrial facilities
• Geographical Surface (Site and Area);
• Function (Plant - Process Unit - Tag);
• Plant Breakdown Structure:
• Commissioning Unit - Commissioning System – Tag;
• Maintenance Unit - Maintenance System - Tag and Equipment;
• Construction Assembly - Tag;
• Process Unit - Equipment;
• Tag Physical Connection;
• Corrosion (Corrosion Loop Type – Corrosion Loop);
• Master Data (Company, Purchase Order, Property, and Property Pick List);
Facility related Master Document Register
Example of documents:
• Project Plans and Procedures;
• Engineering deliverables, including those supplied by
Supplier/Manufacturers;
• Engineering documents;
• Engineering drawings;
• Procurement related documents;
• Construction related documents;
• Commissioning related documents;
• QA and QC related documents;
• Any other documents required by Principal.

Internal
Appendix: Decision Tree for Industry domain data model adoption
OSDU
Legend: Anchor Tables

Data Model Data Domain/ Business Data Type Business Requirement/ Process
OSDU Subsurface data and wells application integration between our domain applications
and the OSDU Data Platform.

Internal
Appendix: Decision Tree for Industry domain data model adoption
IDM
Legend: Anchor Tables

Data Model Data Domain/ Business Data Type Business Requirement

/ Process
IDM others

Internal

Note: If IDM is identified as the Data Model standard to be used, IDM would be enhanced if the data domain/ business data type are not available