Navigating the Giants of Energy: A Detailed Look at the Top Oil and Gas Companies
Oil and gas is not one industry. It is a handful of vertically integrated majors, a bigger layer of national oil companies (NOCs), and a long tail of independents and service firms. If you are an engineer, maintenance lead, or procurement person, that structure is not a business-school diagram. It decides which standards your equipment has to meet, who signs off on your budget, and which supply chains you can actually reach when a critical component fails at three in the morning.
Know how these outfits are built, how they run differently, and what that means at the field level. That is practical, not corporate trivia.
Why Organisational Structure Matters to the Field Engineer
A centrifugal pump trips on a platform run by a major integrated operator. The shift engineer works inside a technical authority framework that can stretch across continents. Approved vendor lists, minimum equipment standards, and safety integrity level (SIL) targets are not set on the platform. They come down from corporate engineering standards the major has built over decades. Those standards usually reference — and sometimes go beyond — baseline industry codes such as API 610 (centrifugal pumps for petroleum, petrochemical, and natural gas industries) and API 670 (machinery protection systems).
Now put an engineer at a smaller independent or a NOC. They may have much more room to specify equipment. They also carry more responsibility to get that specification right without a corporate backstop. One setup is not automatically safer. Each has its own risk profile, and maintenance and procurement teams have to manage it deliberately.
Categories of Major Operators and Their Engineering Implications
Integrated Majors
Integrated majors operate across exploration, production, refining, and retail. They keep large internal technical authorities. Their engineering standards are usually proprietary documents layered on top of international codes. Process safety management in these companies commonly lines up with IEC 61511 (functional safety of safety instrumented systems for the process industry sector), and SIL verification workflows are often audited at corporate level, not left to individual asset teams.
For procurement, that means:
- Approved vendor lists are tightly controlled and slow to change.
- Deviations from standard specifications require formal engineering concessions.
- Long-lead items are usually identified through a structured criticality ranking process.
The engineering rigour is real. So is the bureaucratic friction. A maintenance lead waiting on a concession approval for a non-standard seal arrangement on a gas compressor needs to see the delay as part of the system, not a malfunction.
National Oil Companies
NOCs operate the majority of the world's proved reserves. Their engineering cultures vary widely. Some have internal technical capabilities that rival the majors. Others lean hard on international service companies for engineering authority. For a field engineer, the critical question is where technical decisions actually sit: inside the NOC's own engineering function, or delegated to an EPC contractor or operator partner.
Process hazard analysis (PHA) practices vary too. Some NOCs mandate IEC 61511-aligned SIL assessments on all new safety instrumented functions. Others use less structured hazard review methods. If you move to a NOC-operated project from a major-operated background, verify the applicable safety case framework early. Assumptions from your last posting can leave gaps.
Independents and E&P Companies
Independents usually run leaner engineering teams and shorter decision cycles. Equipment specs may be more flexible, but under-specification is a real risk. An independent in deepwater may buy subsea control systems, flexible risers, and wellhead equipment against operator-developed specs that have had limited peer review.
For procurement at independents, the practical discipline is simple: make sure minimum baseline standards — API 610, API 617 (axial and centrifugal compressors and expander-compressors), API 6D (pipeline and piping valves), and the relevant IEC functional safety standards — are written into purchase orders, not assumed.
Operational and Technical Comparison Across Company Types
The table below compares key operational characteristics relevant to engineering and procurement decisions. No numerical performance figures are included because the variation across assets and geographies makes any single figure misleading.
| Characteristic | Integrated Major | NOC | Independent |
|---|---|---|---|
| Internal technical authority | Strong, multi-tier | Variable — asset-dependent | Limited; often project-specific |
| Approved vendor list rigidity | High | Moderate to high | Low to moderate |
| SIL/functional safety framework | Typically IEC 61511-aligned |
Variable | Variable |
| Equipment specification baseline | Proprietary + API/IEC | API/IEC with local additions | API/IEC, sometimes informal |
| Procurement lead-time management | Structured, criticality-ranked | Variable | Often reactive |
| Maintenance strategy formality | RCM/RBI programmes common | Variable | Often corrective-dominant |
Functional Safety Across Company Types
No matter the company type, any safety instrumented function protecting a hydrocarbon process has to be designed, verified, and maintained against a coherent functional safety lifecycle. IEC 61511 defines that lifecycle — hazard and risk assessment, SIL determination, SIS design, installation, commissioning, and ongoing proof testing.
The gap engineers hit most often is not in design. It is in proof testing. A safety instrumented system that was correctly specified and installed will still degrade in its ability to perform its protective function if proof tests are not done at the required interval and to the required coverage. ISA-TR84.00.02 gives technical guidance on SIL verification methods, including fault tree analysis and simplified equations. It is useful for maintenance engineers who need to understand why a particular proof-test procedure was written the way it was.
For maintenance leads at any company type, the discipline is the same: keep test records that show the as-found and as-left condition of every safety instrumented function, and escalate any as-found failure to the asset's safety case holder.
Illustrative Scenario: Procurement Decision on a Gas Lift Compressor Package
This scenario is illustrative and does not represent a specific project or incident.
An independent operator developing a shallow-water gas lift project needs to procure a reciprocating compressor package. The operator's engineering team is small, and the project schedule is tight. The procurement lead gets a bid from a vendor offering a package built to the vendor's own standard rather than API 618 (reciprocating compressors for petroleum, chemical, and gas industry services).
The risk is not that the vendor's standard is necessarily inferior. It may not be. The risk is that the operator has no independent way to verify adequacy without the API baseline as a reference. When the package arrives on site and the maintenance team needs to establish a lube oil analysis programme, set vibration alarm philosophy, or plan a valve inspection interval, they are working without the structured guidance an API 618-compliant package would carry.
The right procurement call is to require API 618 compliance as a minimum, with any deviations formally documented and reviewed by the operator's technical authority — even if that authority is a contracted specialist rather than an internal engineer.
Practical Checklist: Engaging with a Major Operator or NOC as a Supplier or Contractor
Use this checklist when entering a new operating company relationship:
- [ ] Identify the technical authority structure: who holds engineering approval authority for equipment specifications and deviations?
- [ ] Obtain and review the operator's approved vendor list before preparing any equipment proposal.
- [ ] Confirm which functional safety standard governs the project —
IEC 61511, a proprietary equivalent, or a national standard — and ensure your SIL documentation matches that framework. - [ ] Identify all long-lead critical equipment early and confirm whether the operator's criticality ranking process has been applied.
- [ ] Verify that all rotating equipment specifications explicitly reference the applicable API standard (
API 610,API 617,API 618as appropriate) and that any deviations are formally concession-approved. - [ ] Confirm the proof-test philosophy for all safety instrumented functions and ensure maintenance procedures are written to achieve the required diagnostic coverage.
- [ ] For any work involving opening, depressurising, or inspecting hydrocarbon-containing equipment: confirm that the isolation philosophy, depressurisation procedure, zero-energy verification, lockout/tagout (LOTO) protocol, hazardous-area classification controls, gas detection requirements, and safe vent routing are all documented and approved before work begins.
- [ ] Establish the change management process — understand what triggers a management of change (MOC) review and who approves it.
Conclusion
The structure of the oil and gas industry — majors, NOCs, and independents — is not background noise for engineers and procurement teams. It directly determines the technical framework within which equipment is specified, safety cases are built, and maintenance is executed. Working across company types without adjusting your assumptions is a practical risk.
The immediate next steps for any engineer or procurement lead moving into a new operating company environment are: map the technical authority structure, confirm the applicable standards baseline, and verify that the functional safety lifecycle documentation is current and auditable. Those three actions will surface the gaps that matter before they become incidents or cost overruns.
