Productization
← Back to SOPs catalog
Keedian operations · Standard procedure

Generator not in AUTO.

A standby set is found in MANUAL or OFF — it will not start on a utility failure regardless of its mechanical condition. The classic silent fault left after service. Read-only: Keedian surfaces the mode and refers the return to AUTO to the customer / electrical / power vendor; the set is not commanded.

01 Detail

Trigger, action plan, and escalation criteria.

optimization_metric continuity urgent essential tier AI: hybrid
Related metric
generator_start_readiness
Trigger
generator_control_mode != AUTO
Value drivers
Operational continuity
Preconditions
The generator control-mode signal (AUTO / MANUAL / OFF) mapped over Modbus from the controller (DeepSea / ComAp / Woodward) or via dry contacts and verified per set; which sets cover critical load recorded.
Human role
AI detects the control-mode state, attributes it to the specific set, and routes the referral immediately; operators confirm the mode is real, notify the customer, and coordinate the return to AUTO.
Action plan
(1) Confirm the mode reading is current and correctly mapped before alerting — a stale or mis-mapped mode point manufactures a false not-in-AUTO alarm — but treat a confirmed MANUAL / OFF as the highest-yield readiness catch, surfaced immediately. (2) Attribute it to the specific set and, where known, whether it was left in MANUAL after a service visit (the common cause). (3) A set not in AUTO will not start when called — notify the customer for a return to AUTO, and the electrical / power vendor if the mode traces to a fault; Keedian does not command the set. (4) Distinguish an authorized MANUAL for scoped service in progress from a set left in MANUAL after a completed visit so an active service window is not alarmed as an exposure.
Escalation
(1) A critical-load set in MANUAL / OFF → direct customer + vendor alert; the set will not start on a primary-source failure. (2) A set left in MANUAL after a service visit closed → escalate the service-handoff gap so it is returned to AUTO out of cycle. (3) Sets recurringly found in MANUAL after service across the fleet → carry into the MBR as a service-handoff discipline gap for the vendor.
Prevention
(1) Verify the control-mode signal maps correctly per set before arming so a mode-mapping fault is not read as MANUAL. (2) Record which sets cover critical load so a not-in-AUTO on a critical set is surfaced first. (3) Keep a per-set log of not-in-AUTO events so a recurring post-service MANUAL pattern surfaces the handoff gap for the vendor.