Asset Integrity Digital Twin for Oman
Atlantis Digital Twin puts measured inspection data, API 581 risk-based inspection scoring and API 579-1/ASME FFS-1 fitness-for-service on a single live 3D model of the asset, for operators and integrity contractors working in Oman.
The asset base this is built for
Petroleum Development Oman across the interior fields, OQ refineries and petrochemicals at Sohar and Duqm, Vale and Jindal industrial facilities at Sohar port, and the Duqm refinery and drydock complex.
The regulatory and code environment
PDO and OQ contractor approval regimes set the practical bar, applied over ASME and API inspection codes. Oman's Ministry of Labour occupational safety requirements and radiation-source licensing apply, and in-country value (ICV) requirements affect how contractors staff and structure local operations.
Why it matters here specifically
Work is geographically dispersed between the interior fields, Sohar and Duqm, so crew mobilisation cost and scheduling across long distances materially affects contract margin — which makes work-order-level job costing more than an accounting nicety.
What the twin does
- Binds every thickness reading and indication to a CML or TML with persistent identity, so a reading taken years apart is genuinely comparable.
- Assigns damage mechanisms per API RP 571 against actual process service — sulfidation, naphthenic acid corrosion, HTHA per API 941, wet H2S cracking, chloride SCC, CUI, MIC, erosion-corrosion — so inspection targets the mechanism that is credible for that circuit.
- Computes RBI under API 580/581 from measured corrosion rates rather than defaults, which changes which equipment is genuinely flagged.
- Runs API 579 Level 1 and Level 2 assessments — Part 4 general metal loss, Part 5 local metal loss, Part 9 crack-like flaws — against the stored thickness grid, rendering pass/fail zones spatially.
- Retains full provenance on every record: procedure revision, inspector certification state and instrument calibration state at the time of test.
- Integrates with SAP PM, Oracle eAM, IBM Maximo, ServiceNow, AVEVA PI and OSIsoft historians, with documented REST API and full bulk export.
Regional asset detail
- Muscat — Muscat serves as the operational hub for Petroleum Development Oman's extensive onshore oil production network, the OQ (Orpic) Sohar refinery, and LNG trains at Sur that export to global markets. PDO's ongoing digitisation programme and Vision Oman 2040 both emphasise technology adoption in asset management, making digital twin inspection data integration an aligned strategic priority.
- Sohar — Sohar is a Middle East operator centre where digital twin overlay of inspection + RBI + FFS data integrates with Aramco, ADNOC, KOC, KNPC, Bapco, NIOC, QatarEnergy operator stacks. Atlantis NDT Digital Twin platform — affordable, accessible, fully customizable — delivers operator-format dashboards, multi-language inspection workflow visualisation, and audit-ready RBI cycle automation..
- Duqm — Duqm is Oman's flagship Special Economic Zone (SEZAD), built around the greenfield Duqm Refinery operated by OQ8, a joint venture between Oman's OQ and Kuwait Petroleum International designed to process heavy and sour crude blends at 230,000 bpd, alongside the Duqm Port, dry dock, and a planned petrochemical complex. As a newly built refinery and industrial city rising in a previously undeveloped coastal desert location, Duqm's operators face the challenge of establishing digital-first asset integrity programs from first oil rather than retrofitting legacy paper systems, with Oman's Ministry of Energy and Minerals pushing RBI and FFS compliance across new pressure vessel and piping populations.
- Salalah — Salalah in southern Oman combines the Port of Salalah, one of the region's largest transshipment ports, with the Salalah Free Zone's petrochemical and methanol production, anchored by Salalah Methanol Company's world-scale methanol plant supplying regional and export markets. The methanol plant's high-pressure synthesis loops, reformers, and cryogenic-adjacent storage require rigorous API 510/570 mechanical integrity programs, while the port's fuel bunkering and product storage terminals add tank and pipeline inspection scope under Oman's Ministry of Energy and Minerals oversight.
Digital twin coverage across Oman
Muscat · Sohar · Duqm · Salalah
Frequently asked questions
What does an asset integrity digital twin change for operators in Oman?
It moves the integrity case from a spreadsheet snapshot to a live model. Every UT, PAUT, TOFD, RT, MT, PT and ET reading binds to a corrosion monitoring location with a persistent identity, so corrosion rates come from a real time series rather than an assumed default. RBI under API 580/581 then ranks on measured condition, and API 579 fitness-for-service runs against the stored thickness grid. Work is geographically dispersed between the interior fields, Sohar and Duqm, so crew mobilisation cost and scheduling across long distances materially affects contract margin — which makes work-order-level job costing more than an accounting nicety.
Which codes and regulators does it have to satisfy in Oman?
PDO and OQ contractor approval regimes set the practical bar, applied over ASME and API inspection codes. Oman's Ministry of Labour occupational safety requirements and radiation-source licensing apply, and in-country value (ICV) requirements affect how contractors staff and structure local operations. Every record carries provenance — which procedure revision was in force, which inspector performed the work and what their certification state was at that moment, and whether the instrument was in calibration — which is the bundle a regulator, insurer or client audit actually asks for.
Do we need to laser-scan the plant first?
No. Geometry can come from LiDAR or photogrammetry capture, drone survey, or from existing BIM, CAD, isometrics and P&IDs. Many first deployments start from isometrics and add scan-derived geometry later, because reconciling the CML register — not capturing geometry — is the task that actually gates the timeline.
How long until the first unit is live?
Ten to fourteen weeks is typical: two to three weeks of geometry capture or import, three to four weeks reconciling the CML register and importing historical thickness data, two to three weeks assigning damage mechanisms per API RP 571, then RBI and FFS configuration and integrity-team training. Subsequent units are considerably faster once the data model and conventions are set.
Book a technical demo
Thirty minutes walked through your asset classes, your damage mechanisms and your integration stack, co-presented by an ASNT NDT Level III. Affordable, accessible, fully customizable — request a demo and a tailored quote.
Related: asset integrity management software · Atlantis Digital Twin platform · vendor comparison · ROI calculator · inspection management ERP in Oman.