The documentation chain doesn't hold.
Across oil and gas, petrochemicals, and industrial infrastructure, the record of an asset is held in PDFs, email threads, and handwritten markups. Inspection reports disagree. Deviations agreed at quote stage disappear by delivery. When a dispute reaches counsel, the evidence that should settle it cannot be produced.
The cause is bad information. Documents held in the wrong place, trusted by the wrong people, impossible to verify when the question gets asked.
18%
Average cost overrun on oil and gas megaprojects, with two-thirds running over budget.
EY · Oil & Gas Megaprojects Study
5 to 20%
Industrial project cost lost to rework. Direct rework alone averages around five percent.
Construction Industry Institute
1.5%
Annual revenue lost by process plants to poor asset information management. Every plant, every year.
ARC Advisory Group
Digitise first. Standards follow. Trust is the outcome.
The industry spent two decades waiting for standards to enable digitisation. Helios reverses the sequence. Structure the data you already produce, anchor every event to a verifiable record, and IOGP and EU DPP compliance arrive as a byproduct of the day's work rather than a parallel project.
01 · Digitise first
The evidence already exists.
Quotes, FAT certificates, deviation notes, inspection reports. Helios reads what your teams produce and writes a structured record underneath.
02 · Standards follow
Compliance is a consequence.
Once events are anchored, JIP33 and IOGP S-series alignment, IOGP 797 reporting, CFIHOS handover, and the DPP all fall out of the same record the engine writes daily.
03 · Trust is the outcome
The supply chain reads itself.
Every authorised party verifies any passport without trusting a central administrator. Disputes resolve on evidence rather than counsel.
One engine. Four harnesses.
Helios has one core: a passport schema, the EventChain anchoring layer, and a vertical AI trained on industrial valves. Persona modules layer on top. The Manufacturer module is build-complete; the rest are in build.
Definition
EventChain, in one paragraph
EventChain is the tamper-proof record layer underneath Helios. Each inspection, deviation, certificate, and handover is written as a timestamped entry and cryptographically anchored, so it cannot be altered retroactively. Any authorised party can verify an entry without trusting a central administrator. The protocol is open source: no vendor lock-in, no access fee, no single point of control. Without this layer, a digital passport is a document. With it, the passport is legally defensible.
Manufacturer
From quote to invoice on one verifiable record. Deviations timestamped the moment they are offered. Purchase orders carry an authenticated trail through foundry heat numbers and material certificates. MRB submissions verified on customer receipt, so acceptance cycles shorten because the package is correct the first time.
EPC
Track one RFQ from quote through PO to site acceptance. Supplier emails read themselves into a commitment ledger. Liquidated-damages exposure sits on a dashboard before it becomes a claim. The audit trail sits underneath your existing email flow rather than replacing it.
Operator
Digitise one shutdown's inspection certificates into live passports. IOGP-aligned from day one. Audit-defensible the first time the regulator asks. Where 1.5% of plant revenue bleeds into poor asset information today, this is where it stops.
Inspector
Capture and sign in the field. The certificate the customer receives is the certificate the inspector signed. No retyping, no downstream copies. Mobile capture writes to EventChain; the vertical AI normalises field findings into the operator's required format.
Standards bodies and technology partners
Part Two
How we deploy. What it costs in time. Where we go next.
A companion for customers, prospects, standards-body representatives, and procurement teams.
Sixty days to one verifiable trace.
One senior engineer works alongside your team to take one workflow live on a verifiable record. We pick the workflow that hurts the most. We deliver the first trace in sixty calendar days. Enterprise procurement does not buy software faster than that, and we are honest about it.
01 · Day 1 to 60 · One-time
Deploy
A Helios engineer works with your team for two months. The first two weeks scope the workflow that hurts most: one RFQ package, one shutdown campaign, one quote response. The next six weeks turn it into a live EventChain trace.
02 · Month 2 → · Recurring
Anchor
Every asset the engine touches becomes a passport. Every commitment, deviation, certificate, and handover lands on EventChain. The vertical AI absorbs your formats, BOM conventions, and approval patterns. IOGP and DPP reporting arrive from the same record.
03 · Year 2 → · Intelligence
Scale
The same engine spans maintenance logs, audits, FAT and SAT certificates, dispute resolution, and handovers. Your EPC reads from it. Your manufacturer writes to it. Your inspector signs on it. The passport follows the asset through life.
Four lines on the invoice.
None of the four lines is a seat licence. None is hidden. The invoice fits on one page and procurement can model it in an afternoon. You pay for engineering time once, the software annually, the events you anchor as you anchor them, and the intelligence you choose to consume.
Deploy
One workflow live in sixty days.
One-time · Fixed-scope
The line where engineering time costs you something. Capped at day sixty by contract. After that, our time leaves the invoice.
Module
Annual licence per persona module.
Recurring · Per module
Same engine, different harness. The platform fee. Manufacturer is available now; the others as they ship.
Passport
Per-asset, per-event meter.
Variable · Per event
Each valve gets a passport. Each commitment, certificate, or handover anchored on EventChain is a billable event. You pay for what you track.
Intelligence
Track. Insight. Advisory.
Optional · Value-priced
Track is included. Insight adds AI-driven analysis. Advisory adds prediction and recommendation. You buy the depth you choose.
Three deployment sizes · Scout, Anchor, Enterprise
Tier S · Scout
One workflow. One team.
One module, one site. The workflow you bring on day one. First verifiable trace live in production by day sixty.
Tier M · Anchor
One module. Multiple teams.
One persona module across two to four teams in the same business unit. Module live and metering across the pilot footprint.
Tier L · Enterprise
Multiple modules. Cross-segment.
Two or more persona modules in parallel, with cross-module passport flow. Audit-ready across the segment. Standards alignment continuous.
We publish ranges of effort, not prices; pricing follows the scoping conversation and the workflow you bring. Effort ranges reflect senior engineer-days working hybrid with AI-assist on document ingestion and schema mapping. We commit a maximum of four to six concurrent deployments in 2026; admission is by scoping call.
Where the payback comes from
01 · Operators
Rework averages 12% of project cost.
On a $500M project, that is $60M leaving through the wrong door. Spec deviations caught at quote, not at delivery.
02 · Manufacturers
Cost of quality: 23% of revenue. Target 11%.
Cited on the floor at IVS Bergamo. RFQ weeks become days. MRB-to-invoice cycle shortened by a verifiable trail.
03 · EPCs
98% of megaprojects overrun.
Documentation is a top-three cause. Handover packages assemble from work already done. Rejected paperwork stops triggering site revisits.
04 · Inspectors & TPI
71% of EPC projects fail on quality, budget, or time.
A reinspection visit costs more than the original. FAT, SAT, and hydro pass anchored at the moment of signature.
05 · Oil & gas majors
EU DPP is law. Enforcement 2027.
Compliance reports generate from the same record written daily. DPP readiness comes out of normal operations.
06 · Owners & financiers
Poor data quality costs the industry billions a year.
Insurers and acquirers pay more for a verifiable lifecycle. The passport is the asset's collateral record.
Sources: Construction Industry Institute · McKinsey Capital Projects · IOGP Digital Programme 2026 to 2028 · IVS Bergamo 2026 · European Commission ESPR-2024. IOGP reports 70% of 350 industry leaders surveyed agree the problem is real and a solution exists.
Engaged with
Standards interoperability
Helios is engaging with the IOGP Digital Working Group on industrial passport interoperability and is built to underpin the EU DPP standard as it lands in ESPR. EventChain produces the verifiable trace the standards require. Once events are anchored, CFIHOS, IOGP, and DPP reporting arrive as a byproduct of the day's work.
EventChain is open. Your data stays yours.
Three commitments. Each one closes a failure mode a buyer would otherwise hold against a vendor at this stage.
EventChain open
It will not lock you in.
EventChain will be released as open source, with the protocol white paper published as we approach general availability. Any authorised party can verify any Helios passport without trusting Helios as administrator. The record belongs to the customer.
Security
Your data trains nobody else.
Helios runs in customer-controlled tenants. The base model is trained on industry-wide patterns abstracted from documents; individual customer data is never used to train another customer's model. Anchors are cryptographic hashes, not document contents. The document never leaves your environment.
Capacity
Four to six deployments in 2026.
The constraint is deliberate. Every deployment gets a senior engineer's attention and a clean handover. We grow the bench against confirmed demand, not ahead of it. If you want to be one of those deployments, the conversation needs to start now.
Roadmap · we do not show dates we cannot defend
Done
Foundation
- EventChain infra
- Vertical AI base model
- Manufacturer module build-complete
2026
Manufacturer scale
- More manufacturers onboarded
- EventChain white paper
- Open-source release
2026 to 27
EPC module
- RFQ commitment ledger
- Quote-to-PO traceability
- Email-flow integration
2027
Operator module
- Handover digitisation
- Shutdown inspection capture
- Audit-ready passports
2027 to 28
Inspector module
- Field capture and signing
- Inspector workflow
- Mobile-first
2028 →
Industry scale
- All modules in production
- Cross-module passport flow
- Standards alignment ambient
What CEOs, CTOs, and procurement leads ask us.
Ten questions we hear most often. Each answer is short, specific, and defensible.
Sixty calendar days to the first verifiable trace. Two weeks to scope the workflow that hurts most, six weeks to take it live. Enterprise procurement does not buy software faster, and we are honest about that.