HELIOS BY EQUIPMENT / Pressure vessels

    Trace the vessel’s record back to the work.

    Follow one unfired, welded pressure vessel from agreed procurement requirements to an inspection record for one weld. The intended Helios workflow would keep the requirement, evidence and review decision connected.

    Illustrative example · Intended Helios workflow until verified

    Unfired pressure vessel · IOGP S-619 v2.01 · Specified design code
    A short animated explanation. Play at your pace or read the transcript.

    V-101 / Unfired pressure vessel

    Illustrative 3D model

    1. Requirement
    2. Task
    3. Evidence
    4. Review

    Existing practices

    One vessel. Many fabrication records.

    This vessel contains fluid under pressure. Material certificates and weld inspection records may come from different teams. A missing report can slow the final review.

    1. 01Vessel V-101
    2. 02Fabricator
    3. 03Inspection records

     

    00:00 / 01:30

    FROM THE STANDARD TO THE WORK

    What “built into the workflow” means.

    IOGP provides a shared procurement basis today. Helios would carry the requirements agreed for this order into the work, keeping each check connected to its source.

    1. 01

      Agree the source

      Confirm the applicable IOGP specification, base standard or design code, editions and project requirements.

    2. 02

      Plan the work

      Turn the agreed requirements into checks and supplier tasks, with an owner and a deadline. The project team approves the mapping.

    3. 03

      Connect the evidence

      Link the required record to the equipment or component. Keep missing, received and awaiting review distinct.

    4. 04

      Record the decision

      Keep the authorised review and unresolved issues with the evidence. Reassess affected checks if a requirement changes.

    Where the benefit comes from.

    Cost

    Common requirements can reduce repeated specification work. Earlier visibility of missing records could reduce late chasing.

    Safety decisions

    Agreed checks and traceable evidence support qualified review. The record does not prove that equipment is safe for a particular service.

    Efficiency

    Owners and deadlines make the next action clear. Building the record during manufacture could reduce work left at handover.

    Measure the result on one order: document-chasing hours, time to find the correct record, and unresolved review issues. No Helios savings are asserted here.

    Read the exact film transcript · 1:30

    0:00 to 0:12 / Existing practices

    One vessel. Many fabrication records.

    This vessel contains fluid under pressure. Material certificates and weld inspection records may come from different teams. A missing report can slow the final review.

    • Vessel V-101
    • Fabricator
    • Inspection records

    Illustrative fragmented workflow. Existing fabrication and inspection controls remain essential.

    0:12 to 0:26 / IOGP today

    IOGP provides common procurement requirements.

    IOGP S-619 covers unfired, fusion-welded pressure vessels within its scope. It works alongside the specified design code and the project's requirements.

    • Specified design code
    • IOGP S-619
    • Project requirements

    The code and applicable editions are selected for the order. S-619 does not replace the design code.

    0:26 to 0:38 / IOGP today

    Agree the checks for this vessel.

    The order identifies the required fabrication checks, inspections and records. The team agrees what must be reviewed, by whom, and at which stage of the work.

    • Fabrication requirements
    • Inspection plan
    • Required records

    Inspection extent and methods depend on the applicable requirements, material, service and design code.

    0:38 to 0:52 / Intended Helios workflow

    Connect the requirement to the relevant weld.

    Helios would turn the agreed requirements into tasks and link the evidence to this vessel or its components. Each task would retain its source and responsible owner.

    • Source requirement
    • Weld W-17
    • Task and evidence

    Intended workflow until verified. The project team would confirm the requirement mapping.

    0:52 to 1:04 / Intended Helios workflow

    One weld examination report is missing.

    This example order requires the report for weld W-17 before handover. Demo requirement V-12 would show the gap and ask the fabricator for the record.

    • Demo V-12
    • Owner: fabricator
    • W-17 report missing

    Identifiers, report and deadline are illustrative order detail, not an IOGP clause or universal inspection requirement.

    1:04 to 1:18 / Intended Helios workflow

    A qualified reviewer makes the decision.

    The reviewer checks the correct weld and applicable requirements, then records the decision and unresolved issues. Receipt alone does not approve the vessel.

    • Received
    • Correct weld and requirements
    • Review decision

    Record review is separate from equipment acceptance.

    Record review is separate from equipment acceptance and required inspection responsibilities.

    1:18 to 1:30 / Intended Helios workflow

    Keep the evidence with the vessel.

    V-101 would stay connected to its records and review history. Earlier visibility could reduce late chasing and help the next team find the evidence.

    • V-101
    • Source records
    • Review history

    Measure the benefit in a pilot. No claim of automatic certification or guaranteed safety.

    Scope and source specifications

    Illustrative unfired, fusion-welded carbon-steel process vessel, designed to the code specified by the purchaser and within S-619's stated material, pressure, temperature and thickness boundary conditions. TRS section 8 addresses non-destructive examination. V-12, weld W-17 and its particular report/deadline are illustrative order details. The script does not claim universal 100% examination, a specific technique or universal acceptance limits.

    IOGP is the International Association of Oil & Gas Producers. Its JIP33 programme develops common purchasing specifications. Technical requirements, project choices, quality requirements and required information work with the purchase order. The responsible team determines applicability, inspection responsibilities and acceptance.

    These references do not establish a live integration, complete standards coverage, IOGP certification or endorsement of Helios. Illustrations represent the equipment category and are not manufacturing drawings.

    What needs to be verified in a pilot

    Compare the intended checklist with the approved order and inspection plan. Test a missing record, an incorrect equipment or component reference and a revised requirement. Confirm that unresolved holds remain visible and that receipt cannot substitute for review.

    Check that every decision leads back to the correct source and revision. Validate access permissions and agreed handover fields. CFIHOS information mapping and use of the IOGP Material Digital Passport framework require separate verification.

    The pilot would need to verify who attested each record and whether it changed. A traceable record does not establish that its underlying statement is true. Read about EventChain.

    Review one equipment order with us.

    Bring the agreed requirements and a sample of its records. Define what needs to be checked and how to measure the result.