Keedian operations · Standard procedure

Generator fuel low.

Usable fuel has been drawn down so the standby generator's run-time falls under the building's required autonomy — the generator leg of the ride-through is short even if the UPS bridge is intact. Read-only: Keedian surfaces the run-time shortfall and refers refuelling to the customer and the electrical / power vendor.

01 Detail

Trigger, action plan, and escalation criteria.

optimization_metric continuity high managed tier AI: hybrid

Related metric: backup_autonomy
Trigger: usable_fuel_runtime_hours < required_runtime_hours
Value drivers: Operational continuity
Preconditions: The generator's required run-time (autonomy) and fuel policy agreed per set; the fuel-level signal mapped and verified; the consumption rate at load recorded so run-time is computed, not assumed.
Human role: AI tracks usable fuel against the required run-time and routes the refuelling referral; operators confirm the fuel signal is current, notify the customer, and coordinate refuelling.
Action plan: (1) Confirm the fuel reading is current and correctly mapped before treating the shortfall as real; a stuck or mis-scaled tank sensor manufactures a false low-fuel alarm. (2) Convert the usable fuel to run-time at the present consumption rate and compare against the set's required autonomy, not a bare tank percentage. (3) Refuelling is the customer's / vendor's — Keedian surfaces the run-time shortfall and the volume needed and refers it; the generator is not commanded. (4) Where several sets trend down together, present the pattern as a fuel-management item rather than a string of single referrals.
Escalation: (1) Fuel run-time below the required autonomy while the primary source is stressed or an outage is forecast → direct customer + vendor alert before the set is called on. (2) A low-fuel run-time on a set covering a load the customer has flagged as material → out-of-cycle notification. (3) Tanks recurringly drawn down and slow to refill across several buildings → carry into the MBR as a fuel-management program candidate.
Prevention: (1) Agree the fuel policy and the required run-time per set at onboarding as the reference the fuel level is reported against. (2) Verify the fuel-level signal maps and scales correctly so the run-time estimate reflects the tank, not a default. (3) Trend fuel level against consumption at load so a slow draw-down is visible and refuelling is scheduled before the run-time is short.