HELIOS BY EQUIPMENT / Compressors

    One compressor package. One connected record.

    Follow one air compressor package from agreed requirements to a missing test report and an authorised review. IOGP provides the shared procurement basis. Helios would connect that basis to the work and its evidence.

    Illustrative example · Intended Helios workflow until verified

    Centrifugal air compressor · IOGP S-612 v2.01 · API 672
    A short animated explanation. Play at your pace or read the transcript.

    AC-101 / Centrifugal air compressor

    Illustrative 3D model

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

    Existing practices

    One package. Records from several teams.

    This compressor supplies compressed air. Its drawings and test records can arrive separately. A missing report can leave reviewers chasing evidence as delivery approaches.

    1. 01Air compressor AC-101
    2. 02Package supplier
    3. 03Test 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 package. Records from several teams.

    This compressor supplies compressed air. Its drawings and test records can arrive separately. A missing report can leave reviewers chasing evidence as delivery approaches.

    • Air compressor AC-101
    • Package supplier
    • Test records

    Illustrative fragmented workflow. Existing teams may already have effective controls.

    0:12 to 0:26 / IOGP today

    IOGP provides a common starting point.

    IOGP S-612 adds common purchasing requirements to API 672 for this type of air compressor package. Shared requirements can reduce repeated specification work.

    • API 672
    • IOGP S-612
    • Project requirements

    Scoped to packaged, integrally geared centrifugal air compressors. Use the editions agreed in the order.

    0:26 to 0:38 / IOGP today

    Agree this package's checks and records.

    The buyer and supplier confirm the order requirements, inspection plan and required records. Project choices and approved changes stay part of that agreed basis.

    • Technical requirements
    • Inspection plan
    • Records and deadlines

    The applicable specification family and purchase order work together.

    0:38 to 0:52 / Intended Helios workflow

    Turn requirements into work people can follow.

    Helios would turn the agreed requirements into tasks, with an owner and a due date. Each task would retain its source and link to this package.

    • Source requirement
    • Task and owner
    • Evidence for AC-101

    Intended workflow until verified. The project team would approve the mapping before use.

    0:52 to 1:04 / Intended Helios workflow

    The mechanical test report is missing.

    In this example order, requirement C-04 asks for the report before handover. The package supplier sees the gap and provides the missing record.

    • Demo C-04
    • Owner: package supplier
    • Status: missing

    C-04 and its deadline are illustrative order detail, not an IOGP clause or universal requirement.

    1:04 to 1:18 / Intended Helios workflow

    Received. Now check it.

    An authorised reviewer checks the report against the applicable requirements. The decision and any open issues stay with it. Receipt does not approve the compressor.

    • Received
    • Awaiting review
    • Decision recorded

    Record review is separate from equipment acceptance.

    A reviewed report may still contain unresolved issues. Equipment acceptance is separate.

    1:18 to 1:30 / Intended Helios workflow

    Keep the evidence connected to the package.

    The next authorised team could follow the package record. Earlier visibility could reduce late chasing and make review evidence easier to find.

    • AC-101
    • Source and review history
    • Authorised handover

    Measure the benefit in a pilot. Records support decisions; engineering and acceptance remain with responsible people.

    Scope and source specifications

    Packaged, integrally geared centrifugal air compressor to API 672, within the applicable S-612 scope. S-612 must not be relabelled API 617 or generalized to all gas compressors.

    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.