Refinery Jamnagar

Reliance Jamnagar is, by every measure, the largest single-location refining complex in the world. The DTA (Domestic Tariff Area) refinery runs ~668,000 bpd of mostly heavy-sour crude. The adjacent SEZ (Special Economic Zone) refinery runs another ~704,000 bpd, primarily for export. Together they exceed 1.36 million bpd of installed capacity — more than the largest US refinery (ExxonMobil Baytown) by a factor of 2.4×. Add the adjacent Nayara Energy Vadinar refinery (~400,000 bpd, previously Essar Oil) and the Gulf of Kutch coastline holds nearly 1.8 million bpd of refining within a single industrial cluster. Inspection labour, turnaround scope, CUI exposure, and HTHA risk all scale with this footprint.

Jamnagar runs one of the broadest damage-mechanism profiles in global refining, driven by deep conversion of heavy sour crudes:

Inspection capture at Jamnagar scale — tens of thousands of CMLs across the DTA and SEZ — demands an offline-capable mobile capture workflow. Atlantis runs on iPad and rugged Android tablets, captures UT thickness, PAUT B/C-scans, MT/PT indications, and visual surveys with GPS+photo tagging, and syncs to the asset record automatically when the device is back on Wi-Fi. Reliance’s in-house inspection team plus the contractor pool (TCR Engineering, Bureau Veritas, Lloyd’s, SGS, IRClass, IRISNDT) all use the same capture pattern, with role-based permissions ensuring contractor data is reviewed by Reliance integrity engineers before being committed to the corporate record.

The Atlantis API 579 FFS engine handles Level 1, Level 2, and Level 3 assessments natively. For a complex with 60,000+ CMLs and tens of thousands of weld map entries, the FFS workflow at scale matters: bulk FFS screening can identify the top 1–2% of components requiring detailed Level 2 or Level 3 assessment, which is then routed to the integrity engineering team or to an external engineering firm (E2G, Becht, Wood, KBC). The Atlantis API 581 RBI engine recalculates risk scores whenever process severity tags from the AVEVA PI historian change — a crude swap, a unit re-blend, or an operating pressure trim can re-rank the inspection schedule within hours.

Jamnagar turnaround scope decisions move tens to hundreds of millions of dollars. The Atlantis turnaround scoping module ranks every overdue CML, every elevated RBI risk component, every FFS ‘requires further evaluation,’ and every weld pending re-inspection into a defensible scope list. OISD-129 (pressure vessel inspection) and OISD-130 (piping inspection) audit packs generate directly from the twin in <30 seconds, ready for PNGRB inspector review.

For a full Jamnagar SEZ + DTA deployment (or an equivalent-scale refinery cluster like SABIC’s Saudi network or Sinopec’s Maoming/Zhenhai), Atlantis Digital Twin enterprise tier (affordable, accessible, fully customizable SaaS — quote on request) typically pays back through:

Net: $8M–$25M/yr in measurable value at refinery scale, comfortably justifying a multi-year platform investment.

First process unit live in 10–14 weeks (typically a hydroprocessing unit or the coker complex). Subsequent units 4–6 weeks each. A full DTA + SEZ deployment realistically lands in 18–24 months from kickoff to last-unit-live, with continuous expansion into adjacent assets (PX, polypropylene, lube base oil) thereafter. Coexistence with the existing SAP PM + AVEVA PI + Bentley AssetWise stack is the norm, not the exception.

What this page covers

  • Why Jamnagar is a different scale of digital twin opportunity
  • The Jamnagar damage-mechanism stack
  • Workflow walkthrough for Jamnagar scale
  • ROI math for a Jamnagar-scale deployment
  • Implementation path
  • Inspection capture at 60,000–180,000 CML scale
  • FFS and RBI at Jamnagar scale
  • Turnaround scope and OISD compliance

Key points covered

  • Reliance Jamnagar — the world’s largest single-location refinery complex at ~1.36 million bpd (DTA + SEZ combined), plus the adjacent Nayara Energy Vadinar at ~400,000 bpd
  • Deep-conversion: FCC, hydrocracker, coker, RDS/VRDS, alkylation, paraxylene/PX, propylene, polypropylene, lube base oil, petcoke. Among the highest Nelson Complexity Indices in the world.
  • Sour service (high-sulfur Middle-East crudes), naphthenic acid corrosion, HTHA on hydroprocessing, MEROX corrosion, coker drum fatigue, Gulf of Kutch CUI from monsoon humidity
  • API 510, 570, 653, 579, 581 mirrored in Reliance internal standards + PNGRB (Petroleum and Natural Gas Regulatory Board) requirements + OISD-129/130 inspection codes
  • 60,000–180,000 CMLs site-wide; one of the largest fixed-equipment integrity programs in the world
  • $8M–$25M/yr at full-site scale — driven by turnaround scope optimisation, FFS-backed life extension, and integrated CUI program
  • Reliance runs a deeply customised mix of SAP PM, AVEVA PI, in-house RBI tooling, and Bentley AssetWise components. Atlantis is built to coexist with this stack: SAP PM integration via standard BAPIs, AVEVA PI via OPC-UA or PI Web API, AssetWise via REST. The Atlantis advantage is not replacement; it is the daily inspector and integrity-engineer workflow that the corporate stack does not deliver natively. CML capture, weld map maintenance, FFS calculations, 3D twin visualisation, and ASNT-compliant report templates plug into the existing landscape rather than displacing it.
  • How does the Indian regulatory regime affect digital twin requirements?

Frequently Asked Questions

What makes Jamnagar uniquely well-suited to a digital twin programme?

Three factors. First, scale — Reliance Jamnagar is the world’s largest single-location refinery complex (~1.36 million bpd across the DTA and SEZ refineries combined), which means inspection labour cost, turnaround scope decisions, and unplanned downtime risk all multiply against numbers that make even single-digit-percent improvements very large. Second, complexity — the Jamnagar Nelson Complexity Index is among the highest in the world, with deep-conversion hydroprocessing, coking, FCC, paraxylene, polypropylene, and lube base oil integrated into one site. The damage mechanism stack is correspondingly broad. Third, integrated culture — Reliance runs one of the most mature in-house integrity engineering teams in global refining, with an Operating Management System (OMS) that demands defensible, auditable inspection evidence at every level. Atlantis Digital Twin is built for exactly this profile.

Which Jamnagar units would be the highest-leverage starting point?

Two candidate units stand out. The hydroprocessing complex (RDS / VRDS / DHDT) is HTHA-prone, sour-service, and high-pressure — the canonical Atlantis sweet spot, with API 941 Nelson Curve screening, API 571 damage-mechanism templates, and the FFS/RBI engine all directly applicable. The coker complex (delayed cokers feeding petcoke production) is fatigue-driven with shell cracking, drum bulging, and quench-cycle thermal fatigue that maps cleanly to API 579 Part 14 fatigue assessment. Either makes a strong first-unit-live target. Reliance typically deploys integrity tooling unit-by-unit rather than big-bang, which fits the Atlantis implementation cadence (10–14 weeks first unit, 4–6 weeks subsequent).

How does Atlantis fit with Reliance’s existing in-house tools?

Reliance runs a deeply customised mix of SAP PM, AVEVA PI, in-house RBI tooling, and Bentley AssetWise components. Atlantis is built to coexist with this stack: SAP PM integration via standard BAPIs, AVEVA PI via OPC-UA or PI Web API, AssetWise via REST. The Atlantis advantage is not replacement; it is the daily inspector and integrity-engineer workflow that the corporate stack does not deliver natively. CML capture, weld map maintenance, FFS calculations, 3D twin visualisation, and ASNT-compliant report templates plug into the existing landscape rather than displacing it.

How does the Indian regulatory regime affect digital twin requirements?

PNGRB (Petroleum and Natural Gas Regulatory Board) sets the upstream and midstream regulatory baseline. OISD (Oil Industry Safety Directorate) standards — particularly OISD-129 (inspection of pressure vessels) and OISD-130 (inspection of piping) — set the inspection cadence and methodology requirements for Indian refineries. The Atlantis audit-pack module generates OISD-compliant evidence bundles directly from the digital twin data repository. For internationally-traded products (jet fuel, gasoline, diesel exports), the API/ASME inspection regime applies in parallel; Atlantis handles both code regimes in the same twin.

What about monsoon-driven CUI in the Gulf of Kutch climate?

Jamnagar sits on the Gulf of Kutch in Gujarat — high-humidity, salt-laden coastal climate with a sharp monsoon-driven wet season from June through September. CUI rates on insulated piping and vessels exposed to this environment run noticeably higher than inland Indian refineries (Bhatinda, Panipat, Mathura). Atlantis ships API 583 CUI risk overlays directly on the 3D twin, with monsoon-aware re-inspection scheduling that frontloads CUI surveys before the wet season starts. Reliance’s in-house CUI programme has matured to the point where systematic digital-twin-backed CUI tracking is the natural next step.

Related: Atlantis NDT ERP · Digital Twin platform · NDT inspection software · NDT reporting software · ASNT Level III consulting · NDT training. Book a free consultation.