When a major North American midstream operator managing 4,200 kilometres of pipeline infrastructure across three operating regions faced a surge in regulatory scrutiny from PHMSA and API RP 1173 audit requirements in 2023, its existing maintenance and inspection documentation framework could not produce the asset-level integrity records demanded by federal verifiers. The operational performance of the pipeline network was strong — throughput targets were being met — but the documentary infrastructure was fragmented. Inspection logs, corrosion monitoring records, valve maintenance histories, and safety-critical work orders existed in siloed systems across regional subsidiaries, none of which could generate the unified Integrity Management Program documentation required for compliance. Book a demo to see how FleetRabbit structures pipeline integrity and HSE compliance documentation for midstream operators.
Case Study — Midstream / Pipeline Operations
Zero Incidents. Zero Findings. One Platform.
How a North American midstream operator unified pipeline integrity documentation, eliminated HSE audit gaps, and achieved zero recordable incidents across 4,200 km of infrastructure — in under eight weeks.
0
Recordable HSE incidents in 12 months post-deployment
67%
Reduction in unplanned compressor station downtime
8 wks
Full deployment across 38 compressor stations and 4,200 km network
$580K
Annual maintenance cost reduction at 12 months post-deployment
"
Before FleetRabbit, our PHMSA audit preparation required pulling records from three separate regional systems, reformatting them into the IMP documentation structure, and reconciling discrepancies by hand. That process consumed four weeks of compliance team time and still produced records with gaps. After deployment, our verifier pulled everything directly from FleetRabbit exports. The audit closed in five days. We had zero findings for the first time in four audit cycles. That outcome alone justified the entire investment.
Vice President of Integrity & Compliance
North American Midstream Pipeline Operator
The Challenge: When Operational Excellence Outpaces Documentation Infrastructure
Midstream operators face a compliance paradox that becomes acute during regulatory cycle tightening: the pipeline performs. Throughput metrics are healthy, pressure loss is within design parameters, and the maintenance crews are experienced. But when a PHMSA Integrity Management Program audit requests a consolidated, timestamped trail linking every inspection activity to its associated asset record, corrective work order, and sign-off chain — across multiple regional subsidiaries — the operational reality and the documentary reality diverge sharply.
This operator's challenge was not a maintenance culture problem. It was a data architecture problem. Three regional operating companies each maintained asset and inspection records in different systems: a legacy CMMS in the Western region, a proprietary SAP PM configuration in the Central region inherited from an acquisition, and a combination of spreadsheet-based inspection logs and paper forms in the Eastern corridor. None of these systems spoke to each other. None could produce the cross-regional, asset-boundary-aware documentation that PHMSA API RP 1173 now requires.
01
Three Systems, No Unified Audit Trail
Western, Central, and Eastern regions maintained asset and inspection records in incompatible systems. Cross-regional IMP documentation required manual export, reformatting, and reconciliation — consuming 22 analyst-days per audit cycle and still producing record gaps at two compressor stations.
02
HSE Incident Documentation Fragmentation
Safety incident records, near-miss reports, and corrective action work orders existed in separate tools with no linkage to the asset registry. PHMSA verifiers could not trace a corrective action from its triggering inspection event through to closure — a structural gap that generated four open findings in the prior audit cycle.
03
No Real-Time Integrity Risk Visibility
Fleet and operations executives had no consolidated view of in-line inspection results, cathodic protection readings, or valve maintenance status across the 4,200 km network. Monthly integrity summary reports required manual assembly from regional controllers — arriving 12 to 16 days after period-end.
04
Reactive Maintenance Culture at Critical Assets
Planned maintenance ratio across the compressor station portfolio was 54% — meaning nearly half of all maintenance activity was unplanned response. Emergency repair premiums, unscheduled shutdowns, and pipeline pressure interruptions were driving maintenance cost significantly above industry benchmark.
05
EPA Subpart W and GHG Reporting Gaps
Methane emission monitoring records and GHG reporting data were maintained separately from the maintenance management system. Quarterly EPA Subpart W submissions required a dedicated data reconciliation exercise outside the normal maintenance workflow, creating both efficiency loss and a risk of reporting inconsistency.
06
Acquired Assets Not Yet Integrated
Two compressor station clusters acquired in 2022 had not been integrated into the central asset registry. Inspection histories, valve maintenance records, and cathodic protection data for these assets existed only in the prior owner's paper-based system — posing a compliance risk for the next audit cycle.
How FleetRabbit Solves the Midstream Compliance and Maintenance Challenge
FleetRabbit was purpose-built for asset-intensive operations where the maintenance workflow and the compliance documentation requirement must be served by the same system — not reconciled after the fact between separate tools. For midstream operators, this convergence is not a convenience; it is the structural requirement of PHMSA's IMP framework, which demands that asset records, inspection audit trails, and corrective action closure all exist in a connected, verifiable chain.
01
Pipeline Integrity Documentation — Native, Not Configured
FleetRabbit structures inspection records, ILI (In-Line Inspection) findings, cathodic protection readings, and corrective action work orders in the asset-boundary-aware format required by PHMSA API RP 1173. Every inspection activity is timestamped, operator-attributed, and linked to the asset record at the correct pipeline segment or station equipment level. This is not a post-configuration deliverable — it is how FleetRabbit structures data at deployment.
02
HSE Incident-to-Asset Linkage and Corrective Action Closure Tracking
Safety incidents, near-miss events, and regulatory inspection findings are logged directly against the asset record in FleetRabbit, with automatic corrective action work order generation and closure tracking. PHMSA verifiers can trace a pressure anomaly observation from the original inspection finding through to the corrective work order, the technician sign-off, and the return-to-service documentation — in a single system export.
03
Multi-Region Portfolio Dashboard for Fleet Managers and Executives
Operations VPs and fleet managers see a live consolidated view of compressor station availability, PM compliance rates, integrity risk flags, and maintenance cost across all three operating regions — updated in real time from work order and condition data. Monthly KPI assembly is eliminated. Regional anomalies surface immediately rather than appearing in reports two weeks after period-end.
04
Condition-Based Maintenance Scheduling for Compressor and Valve Assets
FleetRabbit's RUL (Remaining Useful Life) engine and condition monitoring integration connect vibration, temperature, and pressure data from existing field instrumentation to the maintenance schedule — automatically elevating inspection frequency for assets approaching threshold conditions. This shifts the maintenance programme from calendar-based to condition-driven, reducing both over-maintenance and failure-driven shutdowns.
05
EPA Subpart W and GHG Reporting Integration
Methane emission monitoring data captured during routine maintenance inspections is structured in FleetRabbit to feed directly into EPA Subpart W reporting — eliminating the separate quarterly data reconciliation exercise. Emission-related maintenance activities are linked to the GHG reporting record automatically, reducing reporting inconsistency risk.
06
Rapid Asset Registry Build for Acquired Infrastructure
FleetRabbit's QR-based mobile scanning enables field operators to register physical assets — pipeline segments, valves, compressor components, and instrumentation — directly from the field, without manual data entry. Acquired assets that have never existed in a digital system can be registered, historically populated from paper records, and brought into the compliance documentation framework within the first two weeks of deployment.
Implementation: Eight Weeks Across Three Regions and 38 Compressor Stations
Deployment followed a phased approach that prioritised compliance documentation capability and HSE audit trail structure in the first four weeks, with condition monitoring integration and predictive maintenance activation in weeks five through eight. All 38 compressor stations were producing PHMSA-compatible inspection and work order records within the first four weeks.
Phase 1 — Weeks 1–2
Asset Registry and Historical Data Migration
6,340
Assets registered across pipeline network and compressor stations via QR field scanning
48 months
Historical inspection and work order data imported from three legacy regional systems
7-level
Asset hierarchy from portfolio to component, mapped to PHMSA IMP segment boundaries
Phase 2 — Weeks 3–4
PHMSA IMP Documentation Structure and HSE Workflow Configuration
63
Inspection templates configured to PHMSA API RP 1173 monitoring plan requirements
218 per site
PM tasks activated per compressor station across shift, weekly, monthly, and annual tiers
3 days per region
Mobile field access and HSE workflow training for all technician and supervisor grades
Phase 3 — Weeks 5–6
Multi-Region Dashboard and Condition Monitoring Integration
Live — Day 36
Portfolio-level dashboard covering all three regions — compressor availability, PM compliance, integrity flags
OPC-UA / SCADA
Existing vibration and pressure monitoring systems connected to FleetRabbit at 31 of 38 stations
Configured
EPA Subpart W emission monitoring data structured for quarterly GHG reporting
Phase 4 — Months 3–5
PHMSA Verification Audit — First Post-Deployment Cycle
5 days
Audit duration vs 22 analyst-days for prior cycle — 4.4x reduction in compliance team time
Zero
Compliance findings — first clean PHMSA audit in four cycles, full IMP conformity confirmed
Full conformity
All inspection trails, corrective action closures, and cathodic protection records accepted without supplementary evidence requests
Results at 12 Months: Safety, Compliance, and Operational Outcomes
Primary Outcome
Zero Recordable HSE Incidents
12 consecutive months post-deployment with zero recordable safety incidents across the 4,200 km pipeline network and 38 compressor stations. The structured HSE corrective action workflow — linking near-miss events directly to asset records and mandatory closure work orders — eliminated the documentation gaps that had previously obscured risk accumulation at two high-consequence pipeline segments.
PHMSA Audit Efficiency
4.4× Faster
Audit preparation reduced from 22 analyst-days to 5 days. Zero findings — first clean audit in four cycles.
Compressor Station Downtime
−67%
Unplanned compressor stops reduced from 5.8 per station per year to 1.9, driven by condition-based PM scheduling.
PM Compliance Rate
91%
Risk-weighted PM compliance across all stations at 12 months, up from 58% at deployment baseline.
Planned Maintenance Ratio
79%
Up from 54% at baseline. Emergency repair premiums and unscheduled shutdown costs reduced materially.
Portfolio Reporting
Live Dashboard
Real-time KPI visibility across all three regions. Monthly report assembly time eliminated — from 14 analyst-days to zero.
Annual Cost Reduction
$580K
Maintenance cost reduction at 12 months, driven by reduced emergency repairs and compressor downtime elimination.
Before and After: Key Performance Metrics
| Metric |
Before FleetRabbit |
After FleetRabbit (12 months) |
| PHMSA IMP audit preparation time |
22 analyst-days — manual export from three regional systems |
5 analyst-days — records available directly from FleetRabbit |
| Recordable HSE incidents (annual) |
3 recordable incidents — corrective action trail incomplete in 2 cases |
Zero recordable incidents — full corrective action closure documented |
| PHMSA audit findings |
4 open findings — incomplete IMP records at 2 compressor stations |
Zero findings — full conformity across all 38 stations |
| Unplanned compressor stops (per station/year) |
5.8 average across portfolio |
1.9 average — 67% reduction |
| PM compliance rate (risk-weighted) |
58% portfolio average |
91% portfolio — safety-critical assets at 96% |
| Planned maintenance ratio |
54% planned across portfolio |
79% planned — emergency repair share materially reduced |
| Monthly portfolio KPI report time |
14 analyst-days, delivered 12–16 days after period-end |
Live dashboard — real-time across all three regions |
| EPA Subpart W reporting preparation |
Separate quarterly data reconciliation exercise — 3 to 4 analyst-days |
Structured from maintenance workflow — no separate exercise required |
What the Operations Leadership Team Said
The prior audit cycle required four weeks of intensive preparation across three regional compliance teams. We submitted documentation packages and still received findings at two stations requiring additional evidence submissions. Post-deployment, our PHMSA verifier accessed everything they needed directly from our FleetRabbit system exports. The audit closed in five days with zero findings. That is the first clean audit we have had since 2019.
VP of Integrity & Compliance
North American Midstream Operator
I had no real-time visibility into what was happening at the compressor stations. Monthly reports arrived two weeks after period-end and by the time I had the data, the situation had already evolved. FleetRabbit's portfolio dashboard changed that entirely. I can see compressor availability, PM compliance, and active work orders across all three regions at any moment. That operational visibility is as valuable as the compliance outcome.
Chief Operations Officer
North American Midstream Operator
The two acquired compressor clusters had never been in a digital system. We had paper inspection logs from the prior owner and nothing else. FleetRabbit's QR scanning process let our field technicians build the full asset registry in eleven days. Those assets are now fully integrated into our IMP documentation structure. From a compliance risk perspective, that was critical — those stations were our biggest audit exposure going into the verification cycle.
Regional Integrity Manager — Eastern Corridor
North American Midstream Operator
Frequently Asked Questions
QHow does FleetRabbit structure maintenance records to satisfy PHMSA IMP verification requirements?
PHMSA API RP 1173 requires that an operator's Integrity Management Program documentation demonstrate a continuous, verifiable chain from the pipeline segment or facility asset record through every inspection activity, anomaly finding, corrective action work order, and return-to-service authorisation. FleetRabbit structures all of these elements natively — the asset hierarchy is mapped to IMP segment boundaries at deployment, every inspection record carries a timestamp and operator attribution, and corrective action work orders are linked directly to the triggering inspection finding with closure tracking. The audit export package is generated directly from FleetRabbit without post-processing.
Book a demo to review the PHMSA documentation output format for your network.
QCan FleetRabbit consolidate records across multiple operating regions with different legacy systems?
Yes. FleetRabbit operates as a single multi-region platform where each operating region's asset registry, work order records, and inspection documentation are maintained independently but accessible on a consolidated portfolio dashboard. Regional compliance reports can be generated per operating area in the format required by the relevant regulatory authority, while the group-level operations dashboard consolidates across all regions in real time. Historical data from legacy CMMS, SAP PM, and spreadsheet-based systems is imported via structured CSV ingestion during deployment weeks one and two.
QHow does FleetRabbit support HSE incident documentation and corrective action closure tracking?
Safety incidents, near-miss observations, and regulatory inspection findings are logged in FleetRabbit directly against the affected asset record. The system automatically generates a corrective action work order linked to the triggering event, assigns it to the responsible technician or work group, and tracks it through to closure — including supervisor sign-off and return-to-service documentation. The complete trace from incident observation to verified corrective action closure is available in a single export, in the format required for PHMSA IMP and OSHA PSM audit submission.
QHow was the eight-week deployment timeline achieved across a geographically dispersed pipeline network?
Asset registry was built using FleetRabbit's QR-based mobile scanning — field operators scanned physical assets at compressor stations and along pipeline infrastructure during weeks one and two, without manual data entry. Historical inspection and work order data was imported via CSV from regional legacy systems in parallel. PHMSA IMP documentation templates were configured in weeks three and four. Condition monitoring connections to existing SCADA and vibration instrumentation were completed in weeks five and six. The portfolio dashboard went live in week six. No enterprise IT integration projects or national subsidiary data migrations were required.
QDoes FleetRabbit support EPA Subpart W methane emission reporting for pipeline operations?
Yes. Methane emission monitoring data captured during routine maintenance inspections — compressor blowdowns, valve fugitive emission checks, and equipment leak detection readings — is structured in FleetRabbit to feed directly into the EPA Subpart W quarterly reporting structure. The emission monitoring record is linked to the associated maintenance work order and asset record, eliminating the separate quarterly data reconciliation exercise that most operators run outside their maintenance management system.
Book a demo to review EPA Subpart W reporting integration for your operations.
Achieve PHMSA Full Conformity Without the Four-Week Audit Preparation Cycle
FleetRabbit structures inspection records, HSE corrective action trails, pipeline integrity documentation, and condition monitoring data in the format required by PHMSA verifiers and EPA auditors — from the same platform your maintenance team uses for daily PM scheduling and work order management across the entire pipeline network.
PHMSA IMP Documentation
HSE Incident-to-Asset Linkage
Multi-Region Portfolio Dashboard
EPA Subpart W Integration
8-Week Deployment
Condition-Based Maintenance
April 14, 2026
By David
All Posts
