01
Hardware-neutral scan ingestion
Drop in E57, RCP/RCS, LAS/LAZ, PTX or drone photogrammetry from any vendor. Automatic registration, georeferencing and noise stripping — no proprietary capture stack required.
E57 · RCP · LAS · PTX · OBJ
Scan-to-twin data layer · GCC oil & gas
Transforming oil & gas with digital twins
DTX turns laser scans into survey-grade 3D models and 2D plans, then keeps them true with live IoT telemetry. One neutral layer that cleanses your reality-capture data and feeds it straight into the platforms your engineers already use.
- ±3 mm
- As-built tolerance on registered scans
- 6 wks → 9 days
- Typical scan-to-model turnaround
- 1.4 M
- Live tags reconciled per facility, daily
Unit 240 · Crude distillationLive sync
Built for national oil companies, terminals and EPC operators
NORTH GULF PETROLEUMAL-RAYYAN LNGKHALEEJ REFINING CO.MARIB OFFSHOREDELTA EPC GROUPSABKHA PETROCHEMHORIZON GAS TERMINALSNORTH GULF PETROLEUMAL-RAYYAN LNGKHALEEJ REFINING CO.MARIB OFFSHOREDELTA EPC GROUPSABKHA PETROCHEMHORIZON GAS TERMINALS
Illustrative operator profiles. Named references are shared under NDA during technical evaluation.
The platform
Everything between the scanner
and a twin you can trust
Six capabilities that turn a folder of raw point clouds into a maintained, tagged, live asset model — without asking your engineers to change the tools they work in.
02
Automated scan-to-3D conversion
Our classifiers fit pipe runs, vessels, structural steel and valves straight from the cloud, producing parametric geometry with diameters, schedules and centrelines instead of dumb meshes.
Parametric · Class-library mapped
03
2D plans & P&ID reconciliation
Generate GA drawings, elevations and isometrics from the same source of truth, then diff them against legacy P&IDs to surface every undocumented field change.
DWG · PDF · ISO sheets
04
Live IoT fusion
Bind pressure, flow, vibration and temperature tags to the geometry they belong to. The twin stops being a snapshot and starts reflecting the plant as it runs right now.
OPC UA · MQTT · PI · Modbus
05
Neutral publishing to your stack
Push the cleansed twin into AVEVA, Hexagon, Bentley, SAP PM or Maximo through maintained connectors. DTX augments the platform you already bought — it never asks you to replace it.
Bi-directional connectors
06
Drift & accuracy assurance
Every re-scan is diffed against the published twin with a signed deviation report, so integrity and turnaround teams know exactly what moved, when, and by how much.
Signed QA reports · Audit trail
How it works
Four stations, one continuous line
From the moment a scanner leaves the plant to the moment your integrity team opens the twin — DTX owns the messy middle.
- 01
Capture
Your surveyors scan with whatever hardware they already own. Upload raw sets over a private link — no vendor conversion step, no re-capture.
Any scanner · Raw upload
- 02
Cleanse
Registration, deduplication, occlusion repair and noise removal run automatically, with a human QA pass on tolerance-critical zones.
Auto register · QA gate
- 03
Twin
Classified geometry, asset tags and 2D deliverables are produced against your class library and equipment register.
3D model · 2D plans
- 04
Sync
The twin is published to your incumbent platform and kept honest by live IoT streams plus scheduled re-scan diffs.
Publish · Live telemetry
Re-scan, don't re-build. Every shutdown or modification is captured, diffed against the published twin and republished — so the model your operators trust on day 900 is as accurate as it was on day one.
Request a drift report sample →Competitive position
We own the data layer, not your platform
Incumbent suites are excellent at authoring and federating engineering data. None of them own the messy step of turning field reality into clean, tagged geometry. That step is the entire product.
Capture — any vendor
- Leica RTC360
- FARO Focus
- Trimble X9
- NavVis VLX
- Drone photogrammetry
DTX scan-to-twin layer
Registration · noise removal · asset classification · tag binding · 2D generation · drift diffing · live telemetry fusion
Open
Formats in, formats out
Neutral
No platform lock-in
Publish — your stack
- AVEVA E3D
- Hexagon SmartPlant
- Bentley iTwin
- SAP PM
- IBM Maximo
AVEVA E3D / PI
Engineering + historian
Hexagon SmartPlant
Engineering
Bentley OpenPlant / iTwin
Federated twin
SAP Plant Maintenance
Maintenance
IBM Maximo
Asset management
Autodesk Navisworks
Review + clash
OSIsoft PI / OPC UA
Telemetry
Esri ArcGIS
Geospatial
Where the incumbents stop, and we start
An honest read of the market. Each of these platforms is strong — and each leaves the same gap open.
AVEVA
Digital Twin / E3DSuperb engineering authoring, but as-built reality capture is a manual, outsourced service line. Scans arrive as unclassified point clouds and modellers rebuild geometry by hand.
DTX closes it
DTX ingests the raw scan, registers it, classifies assets and hands E3D a clean, tagged model — no re-modelling from scratch.
Hexagon
Leica / SmartPlantBest-in-class capture hardware locked to its own registration and viewer stack. Moving cleansed geometry outside the ecosystem usually means lossy exports.
DTX closes it
DTX is hardware-neutral: Leica, FARO, Trimble, NavVis or drone photogrammetry in — open, lossless class-libraries out.
Bentley Systems
OpenPlant / iTwinStrong federated twin infrastructure, but it assumes someone else already produced a trustworthy as-built. Twin drift after each turnaround is the operator's problem.
DTX closes it
DTX re-scans, diffs and republishes on every shutdown, so iTwin always references a twin that still matches the plant.
Social proof
What operators say
Placeholder quotes from illustrative pilot profiles — replaced with named references as evaluations complete.
“We stopped paying three vendors to rebuild the same rack from scratch. DTX handed our engineering team a tagged as-built in nine days, and it landed in E3D without a single manual re-model.”
“The neutral-layer position is what sold our IT committee. Nothing had to be ripped out — DTX simply became the thing that keeps the twin we already owned from going stale.”
“Post-turnaround drift reports used to be a spreadsheet argument. Now every deviation is measured, signed and traceable back to the scan it came from.”
Pricing
Per facility. Not per seat.
Deep integration work priced the way operators budget it — one subscription per live plant or terminal, covering ingestion, conversion, connectors and drift assurance.
Single Facility
One live plant or terminal, fully managed from raw scan to published twin.
$18,000
per facility / month
- Unlimited scan ingestion for one facility
- Automated 3D conversion + 2D deliverables
- Live IoT binding, up to 250k tags
- One incumbent-platform connector
- Quarterly drift & accuracy report
- Named onboarding engineer
Most common
Multi-Site Programme
For NOCs running a portfolio: shared class libraries and one governance model across every site.
Custom
per-facility rate, volume tiered
- Everything in Single Facility
- Portfolio-wide class library governance
- Unlimited connectors + bi-directional sync
- Monthly re-scan diff cadence
- In-region data residency (GCC)
- Dedicated delivery pod & QA lead
EPC Handover
Greenfield and brownfield handover packages for contractors delivering to an operator.
Custom
per project, milestone billed
- Project-duration licence
- As-built vs. design deviation packs
- Client-ready handover data room
- Operator platform hand-off support
- Progress capture at each milestone
- Warranty-period drift monitoring
All plans are invoiced annually in advance and include in-region support during GCC business hours. Indicative pricing — final commercial terms are agreed per facility scope.
FAQ
Questions procurement always asks
If yours is not here, our solutions engineers answer it on the first call — no discovery workshop required.
No — and we would advise against it. DTX is deliberately positioned as the neutral ingestion and cleansing layer that sits underneath the platform you already run. We take raw reality-capture data, turn it into trustworthy tagged geometry, and publish it into your incumbent stack through maintained connectors.
Any output from Leica, FARO, Trimble, NavVis, Matterport or drone photogrammetry rigs. Practically that means E57, RCP/RCS, LAS/LAZ, PTX, PTS and OBJ/glTF meshes. If your survey contractor can export it, we can register and cleanse it.
A typical process unit runs nine to fourteen days from raw scan upload to a published, tagged twin. Full refinery-scale sites are delivered unit by unit so your team sees usable output in the first fortnight rather than at the end of a nine-month programme.
Tags are bound to the geometry they physically belong to, streamed over OPC UA, MQTT or a historian connector such as PI. Scheduled re-scans then diff the physical plant against the published twin, and any deviation beyond tolerance raises a signed drift report.
Multi-site programmes are deployed with in-region GCC data residency, per-facility isolation and role-scoped access. Scan sets, models and telemetry never leave your tenancy boundary, and every export is logged in an immutable audit trail.
Per facility, per month — $18,000 for a single live plant or terminal, with volume-tiered rates once a portfolio comes on. Pricing covers ingestion, conversion, connectors and drift assurance; there is no per-seat licence and no per-scan surcharge.
Join the waitlist
Bring one facility online first.
Tell us about your site and we will come back with a scoped scan-to-twin plan for a single unit — scanner-agnostic, delivered into the platform you already run. Onboarding slots are released facility by facility.
- A scoped pilot proposal within two working days
- Sample deviation report from a comparable unit
- Connector walkthrough for your incumbent platform