CFIHOS 2.0 Standard
EPC-to-Operations Handover Specification
CFIHOS 2.0 is the international specification for EPC-to-operations data handover at completion of capital projects. Sits on top of ISO 15926. Native support across AVEVA AIM, Hexagon HxGN SDx2, Bentley iTwin, Cognite Data Fusion. Pathnovo emits CFIHOS 2.0 native output across all extraction workflows.
CFIHOS 2.0 Architecture
CFIHOS 2.0 specification has six core components that define what a compliant handover deliverable contains:
CFIHOS Class Library
Extends ISO 15926 Part 4 RDL with capital-facilities-specific classes for EPC-to-operations handover. Includes equipment lifecycle classes (commissioning data, operational readiness data), instrument lifecycle classes (calibration history, SIL verification data), piping handover classes (test pack reference, weld register reference), and document linkage classes (every asset linked to its source documents).
CFIHOS Mandatory Attributes
For each class, CFIHOS specifies which attributes are mandatory at handover, which are optional, and which are recommended. Tightens conformance from ISO 15926 (which is a broad semantic model) to a deliverable specification (which is what an EPC must hand over).
CFIHOS Relationships
Asset-to-asset relationships (e.g. instrument-belongs-to-equipment, equipment-on-line, line-in-piping-system), asset-to-document relationships (e.g. equipment-has-datasheet, equipment-has-mill-cert), and lifecycle relationships (e.g. tag-superseded-by-tag, equipment-replaces-equipment). Foundation for the tag-document register that asset operations actually need.
CFIHOS XML Exchange Schema
Defines how CFIHOS-compliant data is serialised for handover delivery. XML schema with explicit class hierarchy. Compatible with ISO 15926 Part 8 RDF / OWL serialisation as alternative format. Cross-vendor handover deliverables conform to one of these two formats.
CFIHOS Conformance Levels
CFIHOS defines multiple conformance levels (Level 1 through Level 4) reflecting handover scope depth. Level 1 = basic asset register; Level 4 = full lifecycle data handover. Owner-operators specify required conformance level in their CFIHOS handover specification document.
CFIHOS Verification Tools
USPI-published validation tools that check CFIHOS-compliant deliverables for conformance: schema validation, mandatory attribute presence, RDL class resolution, relationship integrity. Deliverables that pass verification are formally CFIHOS 2.0 compliant.
Platforms Supporting CFIHOS 2.0
AVEVA AIM (CFIHOS 2.0 native ingestion; cloud platform within AVEVA Connect)
Hexagon HxGN SDx2 (CFIHOS 2.0 + ISO 15926 native ingestion)
Bentley iTwin (CFIHOS 2.0 native via iTwin Platform Schemas + iTwin Capture Operations)
Cognite Data Fusion (CFIHOS 2.0 ingestion as one of multiple supported handover formats)
Siemens COMOS (CFIHOS 2.0 export from COMOS Walkinside + COMOS Plant Engineering)
SAP Asset Intelligence Network (CFIHOS 2.0 connector for handover into SAP PM downstream)
IBM Maximo (CFIHOS 2.0 adapter via partner ecosystem)
Pathnovo (CFIHOS 2.0 native output across all extraction workflows)
Owner-Operators Specifying CFIHOS
CFIHOS is increasingly contractual on tier-1 owner-operator capex projects. Selected adopters:
Shell (CFIHOS founding member; specifies CFIHOS handover for major capex)
BP (CFIHOS founding member; CFIHOS handover specification on tier-1 projects)
Equinor (CFIHOS founding member; mandatory on Norwegian Continental Shelf projects)
Total (CFIHOS handover specification on tier-1 projects)
Saudi Aramco (CFIHOS-aligned handover specification under SAES + IT-1100 standards)
ADNOC (CFIHOS handover increasingly specified on capex programme)
Petrobras (CFIHOS adoption pilot programmes)
Indian PSU operators (IOCL, BPCL, HPCL: CFIHOS adoption ramping for tier-1 projects)
CFIHOS RDL Examples
CFIHOS RDL (Reference Data Library) sits on top of ISO 15926 Part 4 and defines the class hierarchy, mandatory attributes, and relationship classes for capital facilities handover. Six worked examples below show how typical EPC engineering tags resolve to CFIHOS classes with attribute mapping.
RDL path
physical-object / process-component / equipment / vessel / pressure-vessel
CFIHOS class code
CFIHOS-EQ-PV
Typical tag prefix
V-, D-, T-, C-
Mandatory + optional attributes (example)
Design pressure (kPa), design temperature (°C), corrosion allowance (mm), material specification (ASME SA-516 grade 70), ASME Section VIII Division (1, 2, 3), nominal capacity (m3), insulation type, fire-water protection class
RDL path
physical-object / process-component / equipment / heat-exchanger / shell-and-tube
CFIHOS class code
CFIHOS-EQ-ST
Typical tag prefix
E-
Mandatory + optional attributes (example)
TEMA type (BEM, BEU, AET), heat duty (kW), shell-side fluid, tube-side fluid, design pressure shell (kPa), design pressure tube (kPa), shell material, tube material, surface area (m2), tube count, tube diameter (mm), tube length (mm)
RDL path
physical-object / process-component / equipment / pump / centrifugal-pump
CFIHOS class code
CFIHOS-EQ-CP
Typical tag prefix
P-
Mandatory + optional attributes (example)
Flow rate (m3/h), differential head (m), suction pressure (kPa), discharge pressure (kPa), NPSH required (m), motor power (kW), efficiency (%), shaft seal type, ASME B73.1 or API 610 compliance, material specification
RDL path
physical-object / process-component / instrument / measurement-instrument / transmitter / pressure-transmitter
CFIHOS class code
CFIHOS-IN-PT
Typical tag prefix
PT-
Mandatory + optional attributes (example)
Process service, range minimum (kPa), range maximum (kPa), accuracy (% FS), ISA 5.1 tag, manufacturer, model, signal output type (4-20mA HART, FOUNDATION fieldbus, PROFIBUS PA), hazardous area certification (Ex-d, Ex-ia), SIL certification level
RDL path
physical-object / process-component / instrument / control-valve / globe-control-valve
CFIHOS class code
CFIHOS-IN-CV
Typical tag prefix
FCV-, FV-, PCV-
Mandatory + optional attributes (example)
Process service, flow capacity Cv, fail position (FC, FO, FL), body material, trim material, body class (ANSI 150, 300, 600), end connection, actuator type (pneumatic, electric), positioner type, ISA 5.1 tag, SIS function reference
RDL path
physical-object / process-component / piping / pipe-segment
CFIHOS class code
CFIHOS-PI-LS
Typical tag prefix
Line number per PMS convention
Mandatory + optional attributes (example)
Pipe specification (PMS class), nominal size (DN, NPS), schedule, material grade, insulation type, insulation thickness (mm), tracing type (steam, electrical), test pressure (kPa), service description, P&ID reference, design code (ASME B31.3 Category D, M, Normal, High Pressure)
Class Library Mappings
Pathnovo automates CFIHOS Class Library mapping across the four primary extraction workflows: P&ID tag-to-class resolution, equipment datasheet attribute extraction, P&ID topology to CFIHOS relationship extraction, and mill cert traceability to CFIHOS handover deliverable. Each mapping is validated against CFIHOS 2.0 schema before handover delivery.
EPC engineering tag to CFIHOS Class resolution
Pathnovo extracts ISA 5.1 tag and ASME equipment-numbering convention from P&IDs and resolves each tag to the corresponding CFIHOS RDL class hierarchy. Example: P&ID tag PT-101 (ISA 5.1) → CFIHOS class CFIHOS-IN-PT (pressure transmitter) → ISO 15926 Part 4 class physical-object / process-component / instrument / measurement-instrument / transmitter / pressure-transmitter. Class resolution is automated; manual tag-to-class mapping required only for project-specific extensions outside CFIHOS standard library.
Equipment datasheet attribute extraction to CFIHOS attributes
Pathnovo extracts equipment datasheet content (vendor proposals, IFC datasheets, as-fabricated datasheets) and maps each datasheet line to the corresponding CFIHOS mandatory or optional attribute per class. Example: pump datasheet field 'Flow Rate (m3/h)' → CFIHOS-EQ-CP attribute 'flow-rate-design' with unit 'm3/h'. Missing mandatory attributes flag at handover for engineering review; missing optional attributes flag as warnings. See the datasheet standard reference for the engineering deliverable framework.
P&ID topology to CFIHOS relationship extraction
Pathnovo extracts P&ID line connectivity and resolves to CFIHOS relationships. Example: P&ID line connecting pump P-101 to vessel V-201 → CFIHOS relationship pump-P-101 has-discharge line-LP-102 has-destination vessel-V-201. Asset-to-asset relationships, asset-to-document relationships (equipment-has-datasheet, equipment-has-mill-cert), and lifecycle relationships (equipment-replaces-equipment for brownfield revamps) all extracted and validated against CFIHOS relationship class library.
Mill cert traceability to CFIHOS handover deliverable
Pathnovo's MTR traceability workflow extracts mill certificates and feeds CFIHOS equipment-has-mill-cert relationship into the handover deliverable. Each delivered equipment item carries the heat number, MTR chemistry, MTR mechanicals, EN 10204 certificate type, and PO line reference as CFIHOS-compliant attribute set. Audit-trail traceability from CFIHOS asset register back to source mill certificate maintained throughout handover lifecycle.
Owner-Operator Adoption Notes
Selected owner-operator CFIHOS handover adoption detail across global tier-1 operators (Saudi Aramco, ADNOC, Shell, BP, Equinor) plus Indian PSU operators. Notes cover specification scope, alignment standards, and Pathnovo deployment options for data residency compliance.
Saudi Aramco
Aramco SAES-W series (engineering specifications) and IT-1100 (information technology) standards align with CFIHOS 2.0 for capital project handover. Aramco specifies CFIHOS-compliant handover on major capex programmes (Yanbu refinery expansion, Jazan refinery, NEOM industrial scope). Pathnovo's CFIHOS native output meets Aramco SAES + IT-1100 alignment requirements. AWS Riyadh deployment available for data residency compliance under Saudi NCA.
ADNOC
ADNOC handover specifications increasingly require CFIHOS-compliant data feeds on tier-1 capex projects (Borouge polymer expansion, Ruwais refinery upgrades, Hail and Ghasha offshore development). Pathnovo's CFIHOS 2.0 native output aligns with ADNOC handover specification. Azure UAE North deployment available for data residency compliance under UAE NCA. See the UAE Middle East regional page for the regional engagement model.
Shell
Shell is a CFIHOS founding member and specifies CFIHOS handover on tier-1 capex programmes globally. Shell capital project handover protocol references CFIHOS as the data exchange specification for EPC contractor delivery. Pathnovo's CFIHOS 2.0 native output meets Shell handover specification across global Shell capex.
BP
BP is a CFIHOS founding member and specifies CFIHOS handover on major capex globally. BP capital project handover protocol references CFIHOS for EPC contractor delivery. Pathnovo's CFIHOS 2.0 native output meets BP handover specification across global BP capex.
Equinor
Equinor is a CFIHOS founding member with CFIHOS handover mandatory on Norwegian Continental Shelf projects per Norwegian Petroleum Directorate guidance. Equinor capital project handover protocol references CFIHOS as the formal data exchange specification. Pathnovo's CFIHOS native output meets Equinor handover specification.
Indian PSU operators (IOCL, BPCL, HPCL)
Indian PSU operators are ramping CFIHOS adoption on tier-1 capex projects. CFIHOS-aligned handover specification expected to become standard on major refinery and petrochemical capex within 24-36 months. Pathnovo's CFIHOS 2.0 native output plus Indian regulatory bundle (IBR + OISD 118 + PESO + CCOE) addresses the unified handover requirement for Indian PSU capex. Indian PSU rate-card compatibility available.
Frequently Asked Questions
What is CFIHOS?
CFIHOS = Capital Facilities Information Handover Specification. It is the international specification for EPC-to-operations data handover at the completion of a capital project. Maintained by USPI (Universal Plant Information Initiative), an industry consortium founded by Shell, BP, Equinor, Total, and other tier-1 owner-operators. CFIHOS sits on top of ISO 15926 Part 4 RDL and tightens the specification for the handover-specific scope: which classes, attributes, and relationships an asset register must contain when EPC contractor hands over to owner-operator.
What is CFIHOS 2.0?
CFIHOS 2.0 is the current major version, released by USPI in 2023 with ongoing point releases through 2026. CFIHOS 2.0 expanded the class library, refined mandatory attribute specifications, added new lifecycle relationships (e.g. equipment-replaces-equipment for revamps and brownfield), and improved the XML exchange schema. Backwards-compatible with CFIHOS 1.x for migration; new projects increasingly specify 2.0 directly.
Who manages CFIHOS?
USPI (Universal Plant Information Initiative), an industry consortium hosted in the Netherlands. Founding owner-operator members include Shell, BP, Equinor, Total, ExxonMobil, Chevron. Engineering tool vendors participate as technology members (AVEVA, Hexagon, Bentley, Siemens, SAP, Cognite). USPI maintains the CFIHOS specification through working groups; specification updates are published openly. Pathnovo participates in CFIHOS-aligned data exchange via output format support; broader USPI working-group participation is on the Pathnovo standards-engagement roadmap.
Is CFIHOS mandatory?
Voluntary at the standard level; increasingly mandatory at the project level. Tier-1 owner-operators (Shell, BP, Equinor, Total, Aramco, ADNOC) specify CFIHOS-compliant handover as a contractual requirement on major capex projects. EPC contractors that cannot deliver CFIHOS-compliant data are progressively excluded from tier-1 owner-operator bidding. Indian PSU operators (IOCL, BPCL, HPCL) are ramping CFIHOS adoption on capex programmes; expected to specify CFIHOS-aligned handover on tier-1 projects within the next 24-36 months.
Does AVEVA AIM support CFIHOS?
Yes, native ingestion. AVEVA Connect cloud platform with AIM module ingests CFIHOS 2.0-compliant XML deliverables directly. AVEVA was a founding technology partner in CFIHOS development. For owner-operators on AVEVA AIM, CFIHOS-compliant handover from EPC contractors lands in AIM without manual mapping or remapping.
Does Hexagon HxGN SDx2 support CFIHOS?
Yes. Hexagon HxGN SDx2 supports CFIHOS 2.0 ingestion alongside ISO 15926 Part 4 RDL native and DEXPI XML for P&ID exchange. Hexagon is a CFIHOS technology partner. For SmartPlant Foundation deployments, CFIHOS-compliant handover ingests via SDx2's data take-on schema.
How does CFIHOS support Bentley iTwin?
Bentley iTwin Platform schemas natively support CFIHOS 2.0 mapping. iTwin Capture Operations (Bentley's brownfield digitisation product) ingests CFIHOS-compliant data feeds for asset model population. For EPC contractors using ProjectWise + iTwin during project delivery, CFIHOS-compliant handover lands directly in iTwin without intermediate translation.
How does Pathnovo emit CFIHOS-compliant output?
Pathnovo's extraction output is CFIHOS 2.0 native by default. Extracted tags resolve to CFIHOS class library entries; attributes use CFIHOS-specified property names and units; relationships (equipment-on-line, instrument-belongs-to-equipment, equipment-has-datasheet) use CFIHOS-defined relationship classes. Output serialises as CFIHOS 2.0 XML for handover delivery, or as ISO 15926 Part 8 RDF / OWL for graph-database-backed AIM platforms. Conformance validated automatically against CFIHOS 2.0 schema before delivery; conformance report provided.
Related Pages
Standard
DEXPI
P&ID exchange format. CFIHOS handles the broader handover scope; DEXPI handles P&ID exchange specifically.
Learn more
Standard
ISO 15926
Semantic foundation that CFIHOS sits on top of.
Learn more
Standard
ISA 5.1
Instrumentation tagging conventions used inside CFIHOS instrument classes.
Learn more
Pillar
Engineering Ontologies
Broader pillar covering CFIHOS, ISO 15926, ISA 88, IEC 61346, ISO 14224 standards.
Learn more
Pillar
Asset Information Management
AIM register that ingests CFIHOS 2.0 native output. Foundation of any modern AIM deployment.
Learn more
Pillar
Tag-Document Register
Live with McDermott. CFIHOS-compliant tag-document relationships.
Learn more
Pillar
Engineering Handover Automation
EPC-to-operations handover into SAP PM, Maximo, AVEVA AIM via CFIHOS-compliant data feed.
Learn more
Pillar
Digital Twin Data Integration
Digital twin ingestion via CFIHOS-aligned data feeds.
Learn more
Alternative
AVEVA AIM Alternative
Native CFIHOS 2.0 ingestion. Pathnovo extracts upstream and feeds AVEVA AIM.
Learn more
Alternative
Cognite Data Fusion Alternative
RDF graph backend with CFIHOS 2.0 ingestion. Pathnovo provides EPC-side extraction layer.
Learn more
Alternative
Bentley OpenPlant Alternative
Bentley iTwin native CFIHOS 2.0 mapping for asset model handover.
Learn more
Integration
AVEVA Connect Integration
Pathnovo CFIHOS-compliant output ingests directly into AVEVA Connect / AIM.
Learn more
Integration
Hexagon Partner Integration
Pathnovo CFIHOS-compliant output ingests directly into Hexagon SDx2 / SmartPlant Foundation.
Learn more
Benchmarks
Pathnovo Benchmarks
McDermott live engagement. CFIHOS 2.0 native output validated per delivery.
Learn more
See what your documents actually contain.
Send us 10 documents from your current project. We extract, reconcile, and show you exactly what we find in 48 hours, before any contract.
If the accuracy isn't what we promised, you owe us nothing.