The short version.

• India's oil-and-gas safety rules run through four separate bodies, not one: OISD (Oil Industry Safety Directorate, a Ministry of Petroleum & Natural Gas technical directorate set up in 1986, with 121 published standards/recommended practices) writes most of the domestic playbook; PESO (Petroleum and Explosives Safety Organisation) is the actual statutory licensing authority under the Petroleum Act 1934/Petroleum Rules 2002, and has adopted roughly a dozen OISD standards into binding rule; PNGRB regulates downstream pipelines and transport economics; and BIS works to harmonise Indian standards with international ones. Only offshore installations give OISD its own direct statutory authority, under the 2008 Offshore Safety Rules.
• American Petroleum Institute (API) standards — the same API RP 583 this blog has already cited for corrosion-under-insulation risk — already sit alongside OISD's in practice, not in competition with it: Indian PSU engineering documents routinely specify API design codes (API 650 for tanks, API 510/570 for pressure equipment) layered under OISD siting rules and PESO licensing, with the more stringent requirement governing where they differ. Per API's own 2025 international usage report, India has formally referenced 90 API standards in its technical regulations — the 4th-highest count of any country, behind Indonesia, Canada and Brazil.
• What's actually new: in April 2024, API signed a memorandum of understanding with FIPI (Federation of Indian Petroleum Industry, the ~95-member apex body for India's hydrocarbon sector) aimed at, among other things, "facilitating the adoption and implementation of API standards within India's energy industry." A follow-up FIPI meeting with API and IOCL reportedly saw API express interest in opening an India office to liaise more closely with BIS, PESO and OISD, using FIPI as the connecting body. API separately signed comparable MOUs with OISD and (per one government document) has an older MOU with PNGRB reported to be under renewal.
• Read the sourcing carefully, though: this looks like an API-initiated outreach programme, with FIPI, OISD and PNGRB each as separate MOU partners and liaison points — not a FIPI-originated lobbying campaign or a formal regulatory submission demanding greater recognition of API standards in Indian law. No standalone FIPI position paper, PNGRB filing, or ministry consultation response making that specific ask was found for this piece.
• India's layered-but-fragmented model isn't unusual internationally. Saudi Aramco's own mandatory internal codes (SAES) are themselves built by referencing API, ASME and ASTM standards directly; the EU's Pressure Equipment Directive maintains its own binding law while deliberately cross-referencing ISO standards aligned to API's (ISO 23251 to API 521, ISO 28300 to API 2000). What's distinctive about India isn't running a domestic-code-plus-API model — it's splitting that domestic side across four separate bodies with only partial statutory linkage between them.

Four bodies, and only some of what they publish is actually law

The Oil Industry Safety Directorate (OISD) is the body most people mean when they say "India's oil-safety standards." It's a technical directorate under the Ministry of Petroleum & Natural Gas, established in 1986 — commonly linked to the broader wave of Indian industrial-safety reform that followed the 1984 Bhopal disaster, rather than one specific oil-sector accident. It reports to the Safety Council, the Ministry's apex safety body chaired by the MoPNG Secretary, and has published 121 technical standards and recommended practices covering everything from tank-farm layout to pipeline integrity. But OISD publishing a standard doesn't automatically make following it a legal requirement. Its statutory authority is narrower and more specific than its reputation suggests: OISD is the direct, named "competent authority" only for offshore installations, under the Petroleum & Natural Gas (Safety in Offshore Operations) Rules, 2008, with real consent and audit powers there. Onshore, OISD's standards become mandatory only where a separate body, PESO (Petroleum and Explosives Safety Organisation), formally adopts them into the rules it actually administers under the Petroleum Act 1934 and Petroleum Rules 2002 — roughly a dozen OISD standards have been incorporated that way. Outside those two routes, most OISD RPs function as authoritative best-practice guidance that public-sector oil companies treat as effectively mandatory internally, without a direct statutory compulsion behind every one of them.

Two more bodies complete the picture, doing genuinely different jobs rather than overlapping with OISD directly. PNGRB (Petroleum and Natural Gas Regulatory Board), created by its own 2006 Act, regulates the downstream economics and access rules for pipelines, city gas distribution and marketing infrastructure — a licensing and tariff function, not a process-safety design-code function. BIS (Bureau of Indian Standards), the national standards body, plays a harmonisation role by its own description: working "in collaboration with BIS, OISD & other apex bodies" to align Indian standards with international ones, rather than acting as the primary safety regulator for the sector. The result is a genuinely fragmented statutory map: no single Indian body has the combined authority OISD is often assumed to have, and how a given piece of equipment actually gets regulated depends on which of these four bodies' rules happen to reach it.

OISD's 1986 founding, its Safety Council reporting line, its 121 published standards, and its 2008-Offshore-Rules statutory status are corroborated across Wikipedia's OISD article, the Ministry of Petroleum & Natural Gas's own OISD page, and industry technical-compliance coverage (ifluids.com), which also states roughly a dozen OISD standards have been formally adopted into PESO's rules and made mandatory. PESO's role as the actual statutory licensing authority under the Petroleum Act 1934/Petroleum Rules 2002 is from PESO's own site and Wikipedia's PESO article. PNGRB's 2006 Act and downstream-regulation scope, and BIS's harmonisation role (quoting PESO's own description of working with BIS and OISD), are from Wikipedia's PNGRB article and PESO's own objective page respectively. This piece was researched via web search rather than direct page fetches of oisd.gov.in, peso.gov.in or pngrb.gov.in, which this session's network could not reach directly; the statutory framework above is corroborated across multiple independent secondary sources rather than read from each body's own primary rule text.

Where API standards already sit inside that structure

American Petroleum Institute standards aren't a rival track competing with OISD's for the same ground; in practice, Indian public-sector refiners and EPC contractors already layer the two together on the same project. This blog has already covered one concrete example from that overlap: API RP 583's carbon-steel corrosion-under-insulation temperature bands, cited alongside NACE SP0198, sit behind a paywalled $170 standard from the American Petroleum Institute — not an OISD-published, freely available Indian document, even though the risk it addresses (CUI on Indian refinery and FSRU/FPSO piping) is squarely inside OISD's own domain. Engineering-procurement documentation for Indian PSU tank-farm projects illustrates the same layering directly: one technical account of a typical scope combines API 650 tank design, ASME B31.3 piping (via India's own Indian Boiler Regulations framework), OISD-118's inter-tank distance rules under the Petroleum Rules 2002, and CCOE licence paperwork, all on one project — with the rule that, wherever OISD/statutory and API requirements differ, the more stringent one governs. API itself tracks how far this layering has already gone: its own 2025 International Usage Report states that India has formally referenced 90 API standards in its technical regulations, the fourth-highest count of any country in the report, behind Indonesia (149), Canada (106) and Brazil (99).

The API RP 583/NACE SP0198 paywalled-standard detail is drawn directly from this blog's own prior verified reporting on corrosion under insulation. The API-650/ASME-B31.3/OISD-118/CCOE layered-compliance description for Indian PSU tank projects, and the "more stringent requirement governs" convention, are from ifluids.com's technical-compliance coverage of OISD/API overlap. The 90-referenced-standards figure and India's 4th-place global ranking (behind Indonesia, Canada, Brazil) are from API's own 2025 International Usage Report, reached via search-result summary and corroborating trade coverage (Inspectioneering); this session's network could not fetch api.org or inspectioneering.com directly, so the exact figures rest on search-engine-visible text rather than a primary PDF read in full.

What's actually new: API signing up FIPI, OISD and PNGRB as partners

FIPI (Federation of Indian Petroleum Industry) is a real, substantial body: an apex industry society representing roughly 95 members across India's hydrocarbon sector, including the major public-sector oil companies, that interfaces with government and regulators on sector policy. In April 2024, API announced a strategic memorandum of understanding with FIPI, described in API's own materials as aimed at "sharing knowledge, collaborating on key events and driving innovation" — with facilitating "the adoption and implementation of API standards within India's energy industry" named as one specific goal. A follow-up meeting, recorded on FIPI's own event pages, brought API together with FIPI and Indian Oil Corporation, where API reportedly expressed interest in continuing the MOU and in establishing an office in India specifically to liaise more closely with standard-setting bodies — BIS, PESO and OISD by name — with FIPI's help. This wasn't API's only such move: separate reporting indicates API also signed its own MOU directly with OISD, and a government document on green-hydrogen standards notes an older API-PNGRB MOU (modelled, per that same document, on an existing PNGRB-ASME arrangement) reported to be under renewal.

What this adds up to, read carefully, is an API-initiated outreach programme running through three separate Indian counterparts — FIPI, OISD, PNGRB — each with its own MOU, rather than a single coordinated push originating from the Indian side. That distinction matters for how this development should be read. Nothing found for this piece shows FIPI itself authoring a position paper, filing a PNGRB submission, or responding to a ministry consultation specifically arguing that API standards deserve greater formal recognition inside India's regulatory framework; what's actually documented is FIPI functioning as a convening and liaison partner for an initiative API brought to the table. Whether that liaison role eventually produces a genuine change in how much statutory weight API standards carry in India — versus OISD's own standards, or BIS's harmonisation work — is not something any source found for this piece has resolved yet; the MOUs are real and dated, their downstream regulatory effect is not yet visible in any notification or rule change this piece could locate.

FIPI's ~95-member scope and its role as an apex hydrocarbon-industry society are from FIPI's own site and its 2023-24 Annual Report. The April 2024 API-FIPI MOU and its "facilitating the adoption and implementation of API standards" language are from API's own blog post on the partnership and corroborating trade coverage (World Oil); this session's network could not fetch api.org or worldoil.com directly, so this rests on search-engine-visible text. The follow-up API-FIPI-IOCL meeting, and API's reported interest in an India office liaising with BIS/PESO/OISD via FIPI, are from FIPI's own event pages, also not directly fetchable in this session, so that specific account rests on a search snippet rather than the full page text and should be treated as directionally reliable rather than word-for-word verified. The separate API-OISD MOU and the older, reportedly-under-renewal API/PNGRB-ASME arrangement are from a government document on green hydrogen standards and approval systems (2024), also reached via search snippet. This piece searched specifically for a standalone FIPI position paper, regulatory submission, or consultation response advocating greater API-standard recognition and found none; that absence is reported as this piece's own research finding, not proof no such document exists anywhere in FIPI's fuller record.

India's model isn't unusual; what's unusual is the fragmentation

A domestic safety-code system that coexists with heavy use of API's privately-published standards is not a distinctly Indian arrangement. Saudi Arabia's Aramco runs its own mandatory internal code set, the Saudi Aramco Engineering Standards (SAES), but those standards are themselves built by referencing API, ASME and ASTM directly as their baseline — a domestic-overlay-on-API model, not a fully separate national standard developed from scratch. The European Union runs a genuinely different structure — its own binding law, the Pressure Equipment Directive, with harmonised EN standards carrying legal force — but even there, deliberate cross-referencing to API-aligned international standards exists: ISO 23251 (pressure-relief system sizing) is aligned with API 521, and ISO 28300 (venting of atmospheric/low-pressure storage tanks) is aligned with API 2000, reflecting decades of standards convergence pressure from multinational operators active in both markets. The UK's Health and Safety Executive takes yet another approach, regulating offshore and pipeline safety through its own goal-based statutory instruments that don't name API by reference at all, even though API and ISO standards are the practical tools most operators use to demonstrate compliance with those goals.

Set against that comparison, what actually distinguishes India isn't the coexistence of a domestic code and heavy API usage — that's the norm, not the exception. It's the fragmentation of the domestic side across four bodies (OISD, PESO, PNGRB, BIS) with only partial statutory linkage between them, rather than one body (like Aramco, or the EU's single directive) holding both the technical-standard-writing role and the enforcement authority together. API's MOU programme with FIPI, OISD and PNGRB separately is, in that light, arguably a response to exactly that fragmentation: rather than one Indian counterpart to negotiate standards recognition with, API has had to open parallel relationships with three.

Saudi Aramco's SAES structure and its direct referencing of API/ASME/ASTM standards, the EU Pressure Equipment Directive's binding-law status and its ISO-23251/API-521 and ISO-28300/API-2000 alignment, and the UK HSE's goal-based (rather than standard-by-reference) regulatory approach are drawn from search-result summaries of each jurisdiction's regulatory structure and API's own usage-report commentary on international referencing; this piece did not read the EU directive's or Aramco's own primary documents directly, so these should be read as a reasonably reliable comparative sketch rather than an exhaustively verified regulatory analysis of each jurisdiction.

What doesn't follow from any of this

None of the above should be read as India's safety-regulation structure being either broken or a settled, working system that needs no scrutiny — the evidence found here supports neither a crisis narrative nor a clean-bill-of-health one. The API-FIPI, API-OISD and API-PNGRB MOUs are real, dated, and worth watching, but nothing found for this piece shows them having produced a concrete regulatory change yet; readers should treat "API standards achieving greater coverage in India" as a stated aspiration in an early-stage partnership, not an accomplished fact. Nor should FIPI's role as a convening partner in that partnership be read as FIPI actively campaigning for reduced OISD authority or a wholesale shift toward American standards — the sourcing available doesn't support that framing, and this piece deliberately doesn't make it. The international comparisons in Section 4 are illustrative sketches of how other jurisdictions structure the same domestic-code-versus-international-standard question, not a ranking of which system is safer or more efficient; that would require compliance-outcome data (incident rates, audit findings) this piece did not attempt to gather. Finally, the 90-referenced-API-standards figure describes formal regulatory references, not how consistently those references are actually enforced or audited in practice — a distinct question this piece's sourcing doesn't answer.

Sources and caveats