A 4-week read-only shadow pilot on your historian and alarm exports. We agree the KPI model first. If the sealed evidence pack maps $5M+ in addressable operational value, the pilot fee applies — $35K to $75K per process unit, priced by data volume, security requirements, and pilot success criteria. If not, you keep the pack and pay nothing.
A 4-week read-only shadow pilot on historian and alarm exports. We agree the KPI model first. If the sealed evidence pack maps $5M+ in addressable value, the pilot fee applies. If not, you keep the pack and pay nothing.
Performance on the Tennessee Eastman Process public benchmark and the Manca public alarm dataset. Real-plant performance is established during your pilot on your own historian data — that is the point of the pilot.
Not vendor stats. Real questions your engineers ask when the console lights up. Twin-3 was engineered against these four specific conversations. Each one costs measured money. Each one has an audited answer.
Between a vendor guess and a verified answer sits an audited evidence layer.
"Which actuator surprises me this week."
Twin-3 reads the valve, controller, and upstream signature before the loop breaks. The bearing shows up in the physics, not the vendor manual. Physics-led diagnostics, not vendor guesses.
"Loop is cycling. Valve, controller, or upstream — the historian has the answer."
Twin-3 traces the cycle to the tag that started it, in minutes not days. The historian stops being a haystack. Your engineers stop hunting. Your third day of investigation stops costing more than the second.
"The auditor will ask why we missed it. I need evidence, not a screenshot."
Twin-3 returns a SHA-256 sealed evidence pack. Procurement IT runs the hash check in ten seconds. The board sees what was seen, when, and why. The vendor dashboard does not survive a serious review. The sealed pack does.
"70% of our alarms are nuisance. The console stopped being trusted years ago."
Twin-3 ranks alarm floods into a worklist, not noise. Operators see the signal first. The console becomes trusted again. Six years of programs that did not move the numbers compress into one sealed pilot pack that does.
Every Twin-3 finding travels two phases. The Detective searches your historian for the law that broke. The Vault seals what was found so procurement, the regulator, and the board can verify it themselves. The arc reduces the time between alarm and answer.
The detective beam scans your refinery's digital nervous system, ignores the nuisance traffic, and snaps onto the specific bearing, valve, or controller that is about to break the loop. Every step traces back to a physics equation the plant already obeys.
The diagnostic compresses into a sealed evidence pack. A SHA-256 hash crawls across the surface and locks. Timestamps, sensor logs, ISA-18.2 / IEC 62682 alignment checks. Filed to a read-only archive. Audit-ready. Procurement-verified.
Twin-3 does not guess your plant. It reads the laws your plant already obeys, and tells you, with proof, the moment those laws break. Every residual sits inside a conformal coverage bound. Every coverage bound sits inside an audit chain. Every audit chain sits inside a hash you can verify.
No black box. No assumptions you did not approve. The intelligence layer that respects what your engineers already trust.
Engineering direction 11 of 12 fault families today, with IDV3 isolated as a known boundary case. The engineering work continues to push that boundary toward as-close-to-entirely as the physics will allow. The product is benchmarked, sealed, and ready for bounded pilot evaluation. The next benchmark release tightens the boundary further.
Industrial Integrity Metrics, validated on the Tennessee Eastman Process and the Manca public alarm benchmark. Every number you see here lives inside a sealed evidence pack. Procurement IT runs the hash check before the deployment conversation begins.
No. Twin-3 is read-only on historian, alarm, and sensor exports. No DCS access. No SIS access. No control authority. No replacement of certified safety systems.
The deployment surface is your data export, not your control network. No OT asset modification. No DCS install. No control-network access. Your existing IT, security, and procurement workflows still apply — DPIA, vendor onboarding, data-handling review — but the pilot does not touch any safety-rated or control-rated infrastructure.
Three CSV exports: tag list, historian sample, alarm journal. 4-week window. Hosted in your jurisdiction of choice. Deletable on request at any point including after pilot.
No SCADA tunnel, no VPN into your control room, no agent installed on a plant machine. The pilot is procurement-grade because the data surface is procurement-grade — three files, one analysis environment, full chain-of-custody record.
Every artefact in the pack carries a SHA-256 hash and a manifest. Your IT team verifies the chain in 10 seconds with standard tools. No special verifier required.
The pack is designed for procurement IT before it is designed for engineering. Audit trail, timestamp, hash chain, derivation log, ISA-18.2 / IEC 62682 alignment markers, GDPR-compatible. If it fails a review, the deployment never starts — and we want to know.
Those platforms run on your DCS to operate your plant. Twin-3 audits your historian to evidence value-at-risk. Different scope, different deployment, different procurement path.
We do not replace your APM or your historian. We sit beside them and answer one question: where in your existing data is the addressable operational value you have not yet acted on. The output is forensic evidence, not control output.
If the sealed evidence pack does not map at least $5M in operator-agreed addressable value, the pilot fee does not apply. You keep the evidence pack. There are three commercial outcomes, defined before any data is sent:
Above $5M. Pilot fee applies, you keep the sealed evidence pack.
Below $5M, no credible path. You pay nothing and keep the evidence pack.
Below $5M, credible path found. You pay nothing for the first pass. Twin-3 may fund one agreed diagnostic expansion under a written extension. If the second pass still does not clear the value gate, no fee applies and the engagement closes.
We are not guaranteeing realised savings before implementation — realising value depends on your team's maintenance and operations decisions. We are guaranteeing a value-gated pilot: before it starts we agree the KPIs and cost model; Twin-3 then runs read-only and produces sealed evidence against that model. Twin-3 does not ask you to believe a claim — it asks you to test the claim on your own data, under your own KPIs, with a payment gate tied to verified addressable value.
Public-benchmark coverage today: distillation, reactors, heat exchangers, compressors, flow control loops. Equipment beyond the benchmark is scoped explicitly in the pilot — declared coverage, not assumed coverage.
We do not over-promise on equipment families we have not benchmarked. If your unit type sits outside our public-benchmark coverage, the pilot starts with a scoping conversation, and you keep the evidence either way. The current sealed build covers 11 of 12 Tennessee Eastman fault families — IDV3 declared as a known boundary case.
Contract to evidence pack: 4 weeks. Eight hours of your team's time. Week 1 scoping, weeks 2-3 forensic run, week 4 evidence pack delivery and value review.
No multi-month integration project. The deployment is bounded because the data surface is bounded — three CSV files, one analysis environment. If we slip the 4-week window without your prior agreement, the pilot becomes free regardless of evidence.
You. Always. Read-only means we do not retain. The evidence pack is your property under the pilot agreement. We retain only the methodology (the sealed-build release artefacts) and the public-benchmark calibration.
Your operational data is yours. The derived findings are yours. The hash chain proves chain-of-custody. The methodology and benchmark calibration are ours — that is what we license, that is what the fee is for. Nothing about your plant lives in our systems after the pilot closes if you so request.
The standard Twin-3 pilot pack is structured under English law with UK data-protection controls. Operator-local data requirements are handled through a jurisdiction schedule before any export is received.
For UAE operators, a UAE PDPL jurisdiction schedule is drafted to cover cross-border transfer and sharing requirements before any export is received. For Saudi operators, a KSA PDPL schedule is drafted to cover controller obligations and rights. Dispute routes can be set to DIFC or ADGM arbitration where operator procurement requires it. Data residency is operator-selected: UK secure cloud, operator cloud tenant, or local/GCC-hosted environment, defined before data transfer.
Four fields. A defensible range, not a vendor estimate. Every multiplier sourced. Every assumption visible. The calculator below answers "would Twin-3 cross the $5M threshold on our unit?" — auditable in 30 seconds. Forward the URL to your reliability lead; the configuration is preserved.
No pilot fee if we cannot map the value.
Paid only when the evidence clears the gate.
4 weeks of historian data. 8 hours of your time. We deliver a sealed forensic evidence pack mapped against KPIs you already use. The commercial contract follows only once $5M+ in addressable operational value is mapped on your own data. If the evidence does not clear the agreed threshold, you keep the pack and do not pay the pilot fee.
Twin-3 does not stop at "here is the anomaly." Every finding in the closeout pack carries an engineering-backed action and an estimated financial impact under the cost model you agreed before the pilot started. The pack is sealed, the actions are ranked, and the next step is your call.
Unit FC-247 · Alarm Journal · 28-day window. Twin-3 identified a chattering cluster across TI-301 / PIC-204 / LIC-208 generating 73% of console noise during operator shift handovers. Pattern matches priority-inversion signature documented in ISA-18.2 §13. Hash-chain verified. Source rows attached.
Rationalisation of 11 alarm setpoints plus control-loop tuning on PIC-204 and deadband adjustment on TI-301. Estimated implementation effort: 2 engineering days. Estimated time-to-impact: 1 production shift after tuning applied.
$2.3M / year addressable value, derived from: 14,200 alarm events × 4 min loaded operator-handling time × $185/hr loaded labour (your figure), plus avoided event-response cost (your figure). Pre-realisation. Booked only if action is taken.
The decision is yours. Deploy Twin-3 on the pilot unit for measured value capture. Expand to additional units. Request deeper diagnostic work on a specific finding. Integrate evidence into alarm-management or maintenance planning. Or close the engagement with the pack archived. Twin-3 does not assume the next step — the evidence is the basis on which you choose it.
Your next 3 AM shift is quieter. The console no longer screams ninety thousand alarms a month — your operators see the signal first. The cycling loop has a name, the bearing has a forecast, the auditor has a sealed pack. Engineering meetings stop being investigations.
The historian stops being a haystack and becomes an addressable map of operational truth. Every finding traces back to a physics equation your plant already obeys. The board sees the numbers, the regulator sees the evidence, and your engineering team gets the one thing the industry has not given them: time.
Twin-3 ORCA does not optimise your plant for you. It returns to your team the structural clarity they have been working without. The $5M lives in what they can finally see.
Request the Scoping Briefing