Asset Integrity Digital Twin for Saudi Arabia

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 Saudi Arabia.

The asset base this is built for

Saudi Aramco across Abqaiq, Ras Tanura, Shaybah, Khurais, Jazan and Yanbu; SABIC and its Jubail affiliates; Petro Rabigh; Ma'aden minerals and aluminium; SATORP and YASREF joint-venture refineries; and the contractor base serving them out of Dammam and Al Khobar.

The regulatory and code environment

Inspection work is shaped less by a single national code than by Aramco's own engineering standards — SAES engineering standards, SAEP procedures, SAIC inspection checklists and the Aramco approved-vendor regime — layered on top of ASME Section V, VIII and IX, API 510, API 570, API 653 and API 580/581. Personnel are certified to ASNT SNT-TC-1A or ISO 9712, with Aramco-specific approvals and CBT screening often required before mobilisation. The Saudi Standards, Metrology and Quality Organization (SASO) and High Commission for Industrial Security requirements apply alongside.

Why it matters here specifically

The binding constraint for contractors here is not winning work, it is holding vendor approval. A single expired certification or an out-of-calibration instrument found at a pre-mobilisation check costs the mobilisation and damages the approval record. That is an operational systems problem before it is a technical one.

What the twin does

Regional asset detail

Digital twin coverage across Saudi Arabia

Saudi Arabia · Jubail · Yanbu · Dammam · Khobar · Ras Tanura · Abqaiq · Shaybah · Khurais · Jazan · Rabigh · Riyadh

Frequently asked questions

What does an asset integrity digital twin change for operators in Saudi Arabia?

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. The binding constraint for contractors here is not winning work, it is holding vendor approval. A single expired certification or an out-of-calibration instrument found at a pre-mobilisation check costs the mobilisation and damages the approval record. That is an operational systems problem before it is a technical one.

Which codes and regulators does it have to satisfy in Saudi Arabia?

Inspection work is shaped less by a single national code than by Aramco's own engineering standards — SAES engineering standards, SAEP procedures, SAIC inspection checklists and the Aramco approved-vendor regime — layered on top of ASME Section V, VIII and IX, API 510, API 570, API 653 and API 580/581. Personnel are certified to ASNT SNT-TC-1A or ISO 9712, with Aramco-specific approvals and CBT screening often required before mobilisation. The Saudi Standards, Metrology and Quality Organization (SASO) and High Commission for Industrial Security requirements apply alongside. 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 Saudi Arabia.