Elevator Fault

What you can build

• Turn an entrapment call into a dispatch

  A call from a car phone arrives in Amazon Connect. The operator matches the number to the car, checks the controller's state over BACnet/IP, and proposes a priority ServiceNow incident for the contractor plus a Teams notice to building staff.

  With Amazon Connect, BACnet / IP, ServiceNow, Microsoft Teams

• Read the fault before anyone calls

  A Modbus gateway on a machine-room controller reports a door fault and out-of-service state. The operator proposes a Jira Service Management request for the contractor and a Slack notice naming the car and the nearest working one.

  With Modbus TCP, Jira Service Management, Slack

• Log the cars that keep faulting

  The same car goes out of service week after week. The operator proposes a recurrence note on the open ticket, with each fault and call listed, so the contractor's next visit starts with the pattern.

  With Modbus TCP, ServiceNow

Requirements

• A source of elevator state: a manufacturer monitoring API, or a BACnet/IP or Modbus TCP gateway on each controller with its point or register map
• An Amazon Connect or Twilio connector on the numbers your elevator car phones dial, with permission to read contact or call records
• A ServiceNow or Jira Service Management connector with a queue or table for elevator service tickets
• A Microsoft Teams, Slack, or Twilio connector for tenant and building-staff notices

Authentication

Reads controller and call data through the credentials your gateway, contact-center, and manufacturer connectors hold, and files tickets and notices through your work-management and messaging connectors; it holds none of its own.

Limits

• It reads what the controller or manufacturer exposes. Cars with no monitoring interface are seen only through car-phone calls.
• It never resets a fault, returns a car to service, or interrupts a call. Your answering service or monitoring centre handles the entrapment call itself.
• Manufacturer APIs differ in what they publish and to whom; some require a service contract with the manufacturer.
• A call from a car phone is treated as an entrapment until a person says otherwise. Test calls raise proposals too.

Questions and answers

What does a person approve?

The service ticket, its priority, and each notice. The proposal shows the car, the fault or the call that triggered it, the controller state at the time, and the ticket and notice text. You approve, edit, or dismiss each one separately.

What record is left?

A receipt per proposal: the fault codes and call records cited, the ticket id in ServiceNow or Jira Service Management, the notices sent and to whom, who approved them, and the all-clear when the car returned to service.

Does it talk to the person in the car?

No. The car phone rings your answering service or monitoring centre as it does today. The operator only reads that a call happened and when, and proposes the dispatch and notices around it. It never resets a controller or moves a car.