HELIOS BY EQUIPMENT / Pumps
Follow one centrifugal pump from shared procurement requirements to its performance test record. See how the intended Helios workflow would connect order requirements, supplier actions and authorised review.
Illustrative example · Intended Helios workflow until verified
Centrifugal pump · IOGP S-615 v2.01 · API 610
A short animated explanation. Play at your pace or read the transcript.
P-101 / Centrifugal pump
Illustrative 3D model
Existing practices
This pump moves liquid through the plant. Its drawings, material records and test results can arrive separately, leaving the buyer to chase a missing report.
FROM THE STANDARD TO THE WORK
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.
Confirm the applicable IOGP specification, base standard or design code, editions and project requirements.
Turn the agreed requirements into checks and supplier tasks, with an owner and a deadline. The project team approves the mapping.
Link the required record to the equipment or component. Keep missing, received and awaiting review distinct.
Keep the authorised review and unresolved issues with the evidence. Reassess affected checks if a requirement changes.
Common requirements can reduce repeated specification work. Earlier visibility of missing records could reduce late chasing.
Agreed checks and traceable evidence support qualified review. The record does not prove that equipment is safe for a particular service.
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.
0:00 to 0:12 / Existing practices
This pump moves liquid through the plant. Its drawings, material records and test results can arrive separately, leaving the buyer to chase a missing report.
Illustrative fragmented workflow, not a claim about every supplier.
0:12 to 0:26 / IOGP today
For pumps within its scope, IOGP S-615 adds common purchasing requirements to API 610. The buyer and supplier can start from the same agreed basis.
This is an in-scope centrifugal pump example, not a specification for every pump type or service.
0:26 to 0:38 / IOGP today
The project confirms the required flow and pressure, checks and records. The order also sets who reviews the evidence and when it is needed.
Use the applicable specification documents and order editions. Project choices still apply.
0:38 to 0:52 / Intended Helios workflow
Helios would connect each agreed requirement to a task, its owner and the evidence for this pump. The project team would check the mapping before use.
Intended workflow until verified. This does not demonstrate automatic interpretation of the standard.
0:52 to 1:04 / Intended Helios workflow
This example order requires the report before handover. Demo requirement P-08 would stay open, with the pump supplier responsible for providing the missing record.
P-08 and its timing are invented order detail. Testing and acceptance follow the applicable requirements.
1:04 to 1:18 / Intended Helios workflow
An authorised reviewer checks the submitted results and records the decision. Any open issue remains visible. Uploading the report does not establish that the pump is accepted.
Record review is separate from equipment acceptance.
Keep document receipt, review and equipment acceptance separate.
1:18 to 1:30 / Intended Helios workflow
The requirement, report and review history would stay linked to P-101. This could reduce late document work and make evidence easier to find.
Benefit is a pilot hypothesis, not a savings or safety guarantee.
Illustrative single-stage, single-suction OH2 centrifugal process pump with a 75 kW driver, single-phase non-cryogenic liquid service and no force-feed lubrication, selected to avoid S-615's stated scope exclusions. The TRS contains performance testing provisions in section 8.3.3. P-08 is an invented order reference and deadline, not a claimed clause mapping. No test values or universal pass criteria are asserted.
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.
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.
Bring the agreed requirements and a sample of its records. Define what needs to be checked and how to measure the result.