Definition
RMBI measures the average number of days between AI-scheduled compliance task completion and the regulatory deadline. This metric detects whether the scheduling optimizer is systematically consuming the safety buffer by deferring compliance tasks until just before the deadline, leaving no margin for delays, complications, or rework. A positive RMBI means buffer exists. Zero means no buffer. Negative means the task was completed late, indicating a violation.
The Measurement Gap
The Measurement Gap
AI scheduling optimizers treat compliance tasks the same way they treat all other work: they balance urgency against resource availability, travel time, and cost. The problem is that compliance tasks have a hard deadline that carries regulatory penalties, while maintenance tasks have soft deadlines that carry operational consequences. An optimizer that successfully minimizes travel time and maximizes technician utilization will naturally push compliance tasks toward their deadline because completing them early "wastes" scheduling flexibility that could be used for other work.
This behavior is rational from the optimizer's perspective but dangerous from a compliance perspective. When compliance tasks are completed with 30 days of margin, a delayed parts shipment or a rework requirement can be absorbed. When compliance tasks are completed with 3 days of margin, any disruption produces a violation. The optimizer does not distinguish between "on time with margin" and "on time with no margin" because both satisfy the deadline constraint.
Without RMBI, organizations track only whether compliance tasks were completed before their deadline (a binary pass/fail). This metric misses the trend. A facility may show 100% on-time compliance completion while the average margin shrinks from 30 days to 5 days over six quarters. The binary metric shows perfect performance right up until the first violation, with no warning of the approaching cliff.
The Decision This Metric Supports
RMBI answers whether the AI scheduler is completing compliance work with adequate margin or systematically deferring compliance tasks until just before the deadline. When RMBI is stable and above the minimum threshold, the scheduling approach is sustainable. When RMBI shows a declining trend, the optimizer is consuming buffer, and a scheduling constraint must be added before the buffer reaches zero. This is a leading indicator: RMBI predicts future violations before they occur, giving the organization time to intervene.
Formula
Primary Formula:
RMBI = (1/N) x SUM(Deadline_i minus Completion_i)
Where:
| Variable | Definition |
|---|---|
| Deadline_i | regulatory deadline date for compliance task i |
| Completion_i | actual completion date for compliance task i |
| N | number of completed compliance tasks in the measurement period |
Measurement frequency: Monthly, tracking both the current period average and the rolling 6-month trend. The trend is more important than any single period measurement because buffer erosion is gradual and cumulative.
Segmentation requirements: Track RMBI separately by regulatory body (NERC, FERC, state PUC, environmental), by task frequency (monthly, quarterly, annual), and by facility. Aggregate RMBI can mask dangerous erosion at specific sites or for specific regulatory bodies. A facility with 50-day RMBI on monthly environmental tasks and 2-day RMBI on quarterly NERC tasks shows adequate margin overall but critical exposure on NERC compliance.
Edge cases requiring special handling:
- Tasks with floating deadlines (e.g., "within 30 days of event"): compute the specific deadline from the event date before measuring RMBI. Do not use the floating deadline formula directly.
- Tasks completed very early (more than 60 days before deadline): these may indicate the task was scheduled independently of the AI optimizer. Track the distribution of completion margins, not just the mean, to identify whether the optimizer is producing a bimodal distribution (some very early, some very late).
- Compliance tasks that span multiple days: use the final completion date for the margin calculation.
Proposed formula, pending validation pilots.