Regulatory Activity Scheduling Segregation Index (RASSI)

GMI-OG-003Oil and GasPilot-Ready

Definition

The Regulatory Activity Scheduling Segregation Index (RASSI) measures whether regulatory work is being completed on time at the same rate as the work population as a whole.

Plain language.

The Measurement Gap

Trevor is the maintenance superintendent on a manned production platform in the Gulf of Mexico. The operator brought in an AI maintenance scheduler 18 months ago: it ranks work orders by production impact, crew availability, weather windows, and parts logistics, and produces a weekly schedule that the planners modify before release. Production uptime is up 2.1 percentage points year-over-year. Mechanical availability is at 96.8%, the best the platform has seen in a decade. On-time work order completion, measured platform-wide, is at 91%. Every dashboard metric Trevor reports to onshore management is green.

The BSEE inspector arrives in November. The pre-inspection records review reveals that six SCSSV (subsurface safety valve) function tests are 30+ days past their regulatory cycle. Two SSV (surface safety valve) tests are over 60 days late. The platform's emergency shutdown function test for one of the wells has been pushed three times. The Notice of Incidence cites a pattern of regulatory work falling behind production-supporting work. Trevor pulls the work order history. The overdue regulatory items were rescheduled by the AI optimizer six times each: every time, in favor of a higher-ranked production-impact item. The optimizer never violated its objective function. It optimized exactly what it was told to optimize.

This is not a story about a sloppy scheduler. The 91% overall OTR shows that the AI is completing work on time. The 96.8% mechanical availability shows that the platform is performing. What no metric on Trevor's dashboard captured was the systematic deprioritization of the regulatory subset within that on-time pool. The on-time completion of production-supporting jobs ran at 95%. The on-time completion of regulatory jobs ran at 72%. The aggregate metric averaged them into a healthy-looking number.

Legacy maintenance metrics cannot see this by design. Mechanical availability counts uptime on producing equipment: regulatory work that does not directly take a unit offline does not move the metric. Wrench time measures crew productivity once assigned to a job: it has nothing to say about which jobs got assigned. Overall on-time completion (OTR_overall) is the most relevant legacy metric and is the one that misled Trevor: by aggregating all work, it hides the regulatory subset entirely. A facility can run 91% OTR_overall with 100% OTR on production work and 50% OTR on regulatory work, and the aggregate looks fine. Even targeted metrics like BSEE/PHMSA-specific completion rates often live in the compliance group's separate tracker, not in the AI optimizer's input data, so the optimizer never sees them as a constraint.

This is the structural failure mode of AI scheduling against a single objective function. The optimizer follows the gradient. The gradient says production uptime. Regulatory work has a deadline but rarely an immediate production impact, so it slides: quietly, repeatedly, every cycle, in small increments that none of the legacy dashboards register until the Notice of Incidence lands.

The measurement gap is precise. The aggregate on-time completion metric averages over a subset that has a different decision profile than the work as a whole, and the averaging hides the segregation. The question RASSI proposes to answer is the one Trevor could not ask in May: is the AI scheduler deprioritizing BSEE, PHMSA, EPA, or OSHA work relative to everything else?

Formula

The Regulatory Activity Scheduling Segregation Index (RASSI) measures whether regulatory work is being completed on time at the same rate as the work population as a whole.

Plain language. Take all the work orders that were due in your measurement period. Compute the percentage that were completed on time, that is OTR_overall, the metric most operations already track. Now take the subset of those work orders that are regulatory (work that satisfies a BSEE, PHMSA, EPA, OSHA, or other regulatory requirement) and compute the same on-time rate. That is OTR_regulatory. RASSI is the ratio of the two. If the AI scheduler is treating regulatory work the same as everything else, RASSI will be near 1.0. If regulatory work is sliding while production-supporting work is not, RASSI will be below 1.0, and the size of the gap tells you how much segregation is happening.

Notation:

RASSI = OTR_regulatory รท OTR_overall

Where:

  • OTR_regulatory = the on-time completion rate for the regulatory subset of work orders in the measurement period (percentage)
  • OTR_overall = the on-time completion rate for all work orders in the measurement period (percentage)
  • The "regulatory" subset is defined by the CMMS regulatory classification tag, which must be applied consistently to qualify work as BSEE-, PHMSA-, EPA-, or OSHA-driven

A regulatory work order is one whose deadline is set by a regulatory requirement and whose late completion creates compliance exposure. Examples: SCSSV/SSV function tests on BSEE-permitted wells; PHMSA-required pipeline integrity assessments; EPA Method 21 LDAR (Leak Detection and Repair) monitoring; OSHA-required pressure vessel inspections under PSM. The classification tag must distinguish these from "good engineering practice" work that is not directly mandated.

Edge cases. Inconsistent regulatory tagging makes the metric meaningless. If half the BSEE-driven work orders are not flagged "regulatory" in the CMMS, RASSI will be wrong in either direction depending on which way the unflagged items completed. The first investment for any facility considering this metric is auditing the regulatory tag for completeness. Some facilities I have seen carry the tag on the work plan template but not on the issued work order; some carry it as a free-text "regulatory" note that nobody filters on. Get the tag structured and consistent before you compute the ratio.

Deadline rigidity varies. A BSEE function test has a hard deadline tied to a specific cycle count or calendar date: late is late. An LDAR survey has a deadline that is structured against the calendar but with some flexibility in when within the period the work occurs. A PHMSA reassessment interval is hard with a long horizon. The metric should segment by deadline rigidity, a 0.78 RASSI driven by LDAR slippage is operationally different from a 0.78 RASSI driven by SCSSV slippage, even though they read the same on the dashboard.

Low overall OTR makes the ratio less meaningful. If OTR_overall is 50% (the facility is missing half its deadlines across the board) RASSI loses its diagnostic value. The question is no longer "is regulatory being segregated" but "is the entire scheduling process broken." The metric is most useful when OTR_overall is high enough that the regulatory subset's underperformance is a signal, not noise.

Sign convention: higher is better. RASSI = 1.0 means regulatory work completes on time at exactly the same rate as everything else. RASSI > 1.0 (regulatory better than overall) is unusual and typically indicates either a backlog being cleared or aggressive prioritization of the regulatory subset by compliance pressure. RASSI < 1.0 is the failure mode the metric exists to surface.

Proposed formula, pending validation pilots.

At a Glance

Category
Regulatory Compliance & Workforce Qualification
← Regulated Work Certification Verification Rate (RWCVR)Downhole Sensor Reliability Index (DSRI) →

Assess Your Organization

The AI-GPS Assessment evaluates your AI governance maturity and recommends KPIs like this one for your implementation roadmap.

Take the Free AI-GPS Assessment