TL;DR: Refinery EHS software lives or dies on scale. A single refinery can carry six figures’ worth of LDAR components, dozens of regulated tanks, multiple stormwater outfalls, and overlapping federal, state, and consent-decree obligations — all inspected by a field crew that doesn’t have time to fight with clunky tools. Here’s what separates software that survives a refinery from software that just demos well.
Table of Contents
- Why Refineries Break Generic EHS Tools
- LDAR Is the Anchor Requirement
- The Rest of the Stack: SPCC, Stormwater, Safety
- Consent Decrees Raise the Bar
- What the Field Crew Actually Needs
- Scaling Across Sites and Business Units
- A Refinery EHS Software Checklist
- FAQ
Plenty of EHS platforms handle a warehouse fine. A distribution center has a few dozen inspection points, one or two permits, and a safety program. Almost anything works.
A refinery is a different animal. Component counts for leak detection alone commonly run into the tens of thousands — often past 100,000 at larger facilities. Layer on tank farms regulated under SPCC, process units under OSHA’s Process Safety Management standard, stormwater outfalls under an industrial permit, and hazardous waste generation, and you get a compliance surface that generic checklist apps were never designed to carry.
The failure mode is predictable. The software chokes on component volume, the field crew reverts to paper and spreadsheets, and the “system of record” quietly becomes three systems and a shared drive.
So the first question when evaluating refinery EHS software isn’t about features. It’s about scale: has this platform actually run a six-figure component inventory in production?
LDAR Is the Anchor Requirement
For most refineries and gas plants, leak detection and repair is the highest-volume compliance obligation on site — and the one where software quality is most visible.
Method 21 monitoring with an OVA or TVA means a technician physically visits each regulated valve, pump, connector, and pressure relief device on a defined frequency, records a reading, and triggers repair workflows when a leak definition is exceeded — thresholds that run as low as 500 ppm for valves under the newer NSPS subparts. Miss a component, blow a monitoring window, or lose a repair record, and you’ve created a findable violation.
That’s a routing and recordkeeping problem as much as an instrumentation problem. LDAR inspection software needs to own the component inventory, build efficient monitoring routes, capture readings in the field, track repair and re-monitor deadlines, and produce the reports an auditor asks for — without a technician ever wondering which valve is which.
Upstream and midstream operations have their own version of this under EPA’s oil and gas air rules: Subpart OOOOa and the newer OOOOb require fugitive emissions surveys at well sites and compressor stations, with OGI camera inspections and documented walking paths. We covered the documentation side in detail in our guide to Subpart OOOOa LDAR compliance and OGI inspections.
The catch is that many vendors treat LDAR as an add-on module. In oil and gas, it’s the center of gravity. Evaluate it first.
The Rest of the Stack: SPCC, Stormwater, Safety
LDAR gets the attention, but refinery enforcement actions come from everywhere:
SPCC. Tank farms put refineries squarely under EPA’s spill prevention rules at 40 CFR Part 112 — routine tank and containment inspections, integrity testing records, and a PE-certified plan reviewed at least every 5 years. Our SPCC inspection software exists because monthly walkarounds across hundreds of oil-containing assets don’t stay organized on paper.
Stormwater. Industrial stormwater permits bring quarterly visual monitoring, benchmark sampling, and annual comprehensive inspections across every outfall. Refineries typically have many, spread across large acreage — exactly the situation where digital stormwater inspections with facility mapping pay off.
Process safety and occupational safety. OSHA’s PSM standard (29 CFR 1910.119) drives mechanical integrity inspections and audit trails, while day-to-day safety inspections generate their own documentation load.
One platform covering all of these beats four point solutions, and not just on price. When the same field app, the same facility map, and the same reporting layer serve every program, cross-training gets easier and nothing falls between systems.
Consent Decrees Raise the Bar
Here’s something specific to this industry: a large share of U.S. refining capacity operates under EPA consent decrees from the refinery enforcement initiative, and those decrees routinely include enhanced LDAR provisions — lower leak definitions, higher monitoring frequencies, tighter repair windows, and third-party audit requirements that go beyond the base regulations.
Software configured only for the regulatory minimums can’t represent those obligations. If your site runs enhanced-LDAR terms, the platform has to support custom leak definitions and monitoring schedules per component class, not just the federal defaults. Ask that question in the demo. The vendors who’ve worked in oil and gas will answer immediately; the generalists will get back to you.
What the Field Crew Actually Needs
Compliance managers pick software, but technicians determine whether it works. A refinery route tech touches hundreds of components a shift. Every extra tap costs minutes at that volume.
The field requirements are blunt:
- A mobile app that works offline. Process units and tank farms kill connectivity. Readings can’t wait for signal.
- Facility mapping with component locations. New techs and contractors find monitoring points without a veteran escort — which matters more every year as experienced staff retire.
- Fast component lookup. Scan or search, see the component’s history, log the reading, move on.
- Automatic deadline tracking. Repair clocks and re-monitor windows managed by the system, not a spreadsheet someone updates on Fridays.
- Photo documentation attached to the asset, so findings carry evidence.
This is the standard we built toward with the EHSTracks oil and gas EHS software — one mobile platform that runs LDAR, SPCC, stormwater, waste, and safety inspections against a single facility map.
Scaling Across Sites and Business Units
Multi-site operators have one more layer to worry about. A platform that works at one refinery still fails the company if every site configures it differently, because corporate can’t roll up compliance status or compare programs.
Look for centralized administration with site-level flexibility: shared checklist templates, one reporting layer across facilities, and permissions that let a regional EHS director see everything while each site manages its own routes. Scalability in oil and gas isn’t a server question — it’s whether the platform stays coherent at site 12.
A Refinery EHS Software Checklist
Bring these to the evaluation:
- Has the platform run a component inventory in the tens of thousands in production? Ask for the reference.
- Does it support custom leak definitions and monitoring frequencies (consent-decree terms), not just federal defaults?
- Can it run Method 21 TVA based workflows that require documented calibrations?
- Does the mobile app work fully offline, with facility maps and component locations?
- Does one platform cover LDAR, SPCC, stormwater, waste, and safety — on the same map and reporting layer?
- Can it produce the specific reports your last audit requested, in minutes?
- Can a new technician or contractor run a route without a site veteran alongside?
Anything scoring poorly on questions 1–3 isn’t refinery software, whatever the brochure says.
FAQ
Are there scalable EHS platforms built for oil and gas operations?
Yes. Purpose-built platforms like EHSTracks handle oil and gas requirements specifically: LDAR component inventories in the tens of thousands, Method 21 and OGI inspection workflows, SPCC tank inspections, and stormwater monitoring — with centralized administration that scales from a single gas plant to multi-site refining operations.
What does refinery EHS software need to include?
At minimum: LDAR component tracking with configurable leak definitions and repair deadlines, SPCC inspection scheduling and records, industrial stormwater inspection workflows, a mobile app with offline capability and facility mapping, and audit-ready reporting across all programs from one system.
How is LDAR software different from general inspection software?
LDAR software manages a regulated component inventory — every valve, pump, and connector with its own monitoring frequency, leak definition, and repair clock. General inspection tools track forms and due dates; they typically can’t represent component-level obligations at refinery volume or produce LDAR-specific regulatory reports.
Can one platform handle both upstream and downstream compliance?
Largely, yes. The programs differ — OOOOa/OOOOb fugitive surveys upstream, Method 21 LDAR and PSM downstream — but the underlying work is the same: scheduled inspections against mapped assets with documented findings. A platform built on that model covers well pads and refineries with configuration, not separate products.
The pattern across every refinery we work with is the same: the compliance obligations aren’t getting smaller, and the workforce carrying them isn’t getting bigger. Software that handles the volume and that the field crew actually likes using is how the math keeps working.
See what EHSTracks looks like on your component inventory. Schedule a demo.