Recurring door fault.

A unit logs repeated door faults — nudging, reopening, or door-time-out events — inside a rolling window without a full stoppage yet. A degradation signal: the door operator is the most common cause of an eventual out-of-service, so it is referred before it strands the car.

01 Detail

Trigger, action plan, and escalation criteria.

optimization_metric vertical_transport low essential tier AI: hybrid

Related metric: vertical_transport_availability
Trigger: count(door_fault, window) >= door_fault_threshold (raises recurring-door-fault degradation)
Value drivers: Avoided truck rolls Operational continuity
Preconditions: Door-fault events are exposed from the controller and counted per unit over a configurable rolling window and count threshold, both server-side attributes confirmed per building.
Human role: Primary — Keedian counts the recurring faults and raises the degradation alarm; the door-operator service is the certified maintenance provider's. Operators confirm the trend and coordinate a planned referral rather than an emergency one.
Action plan: (1) Count door-fault events per unit over the rolling window; raise the alarm when the count crosses the agreed threshold. (2) Refer it to the maintenance provider as a planned door-operator check — a degradation signal, not an emergency — with the fault count and window. (3) Log the referral and keep watching; if the unit stops fully, it escalates to the out-of-service alarm.
Escalation: (1) Door-fault rate accelerating sharply → move the referral forward before the expected stoppage. (2) Faults continue after a provider visit → flag the door operator for a deeper engagement.
Prevention: (1) Set the window and count threshold per building so a normal fault rate is not over-reported. (2) Trend door-fault counts per unit so chronic doors are worked on a planned basis.