Elevator Monitoring
Every elevator, live, and one lift, in three clicks.
Live status across every site and every city, uptime and health scores per unit, and a drill path that takes you from a portfolio number to the exact lift causing it without opening another system.
The problem
Most elevator reporting is a monthly count of things that already went wrong.
Ask a service director how the elevators are doing right now and the honest answer is usually a pause, then a call to two branch managers. The data exists, but it is spread across a ticket list, a maintenance spreadsheet, and whatever the technicians happen to have reported. It arrives as a report at month end, which is roughly four weeks after it could have been useful.
The consequence is a business run on lagging indicators. A city where fault rates doubled is discovered at the quarterly review. A client on the edge of leaving is identified after the notice arrives. A unit that has been down for three days looks the same on the sheet as one running perfectly, because nothing was watching either of them.
What the dashboard reads
Real controller signal. Not a status someone typed in.
The interface hardware sits in the lift panel and reads the controller directly. The firmware decodes what it says. Everything on the dashboard traces back to a signal from the machine rather than a field someone updated on Friday.
Position and direction
Which floor, moving up, moving down or idle, straight from the controller.
Door state and timing
Open, closed, obstructed, and how long the cycle is taking against the unit baseline.
Decoded faults
Controller fault codes translated into plain language with the time they fired.
Motor current and load
Draw against the normal envelope for that unit, which is where binding shows up early.
Trips and call registrations
How hard the unit is actually working, which drives usage-based servicing.
Connectivity
Online, offline or buffering, so a silent unit is never mistaken for a healthy one.
Sample shape only. The site carrying the most open faults surfaces at a glance.
Drill-down
Five levels. One continuous view.
Every number on a higher level is clickable down to the records underneath it. When the elevator uptime figure moves, the path to the units responsible is a few clicks rather than a data request to someone else.
- All elevators: units running, down, and at SLA risk right now
- Region and city: health and fault density by geography
- Client and contract: portfolio health per account
- Site and building: every unit side by side
- Unit: live state, decoded faults, and full history
All elevators
The whole installed base in one number set: units running, units down, units under maintenance, open critical alerts and contracts at SLA risk right now.
Region and city
Health by geography, with unit counts, fault density and technician coverage. The city that is quietly getting worse becomes visible before it becomes a complaint.
Client and contract
Portfolio health per account. Useful before a renewal conversation, and useful when a client claims their lifts are always broken and you need the actual figure.
Site and building
Every unit in the building with live status side by side. Where a building has six lifts and two are carrying the traffic, the pattern shows.
Unit
Live floor position, direction, door state, current draw, recent decoded faults, open tickets, maintenance schedule and full service history on one screen.
Tell us how many elevators you run and your site structure. We will show you what the dashboard looks like shaped around it.
Book a Session →Uptime and health scores
A number that says which lift to worry about.
Uptime alone hides the interesting cases. A unit at ninety-nine percent that has thrown the same door fault every day for a fortnight is a failure waiting for a weekend. A health score exists to surface exactly that.
The inputs and their weighting are set with your engineers during the build. If your team considers current-draw drift the earliest reliable warning, it weighs more. The score has to match the judgement of the people acting on it or it gets ignored.
Fault frequency and severity over the period
Door cycle timing drift against the unit baseline
Motor current trend across comparable loads
Recorded downtime and time to restore
Open tickets, overdue maintenance and unresolved blockers
Age, usage intensity and time since last major intervention
A sample elevator dashboard. Targets and results are built to your contracts.
Alerting
An alert channel people still read after six months.
Monitoring systems fail for one reason more than any other: they alert too much, people stop looking, and the one alert that mattered scrolls past. The rules below are designed to prevent that, and every one of them is set to your policy.
Severity, defined by you
An entrapment and a display fault do not share a path. Severity tiers, and the response each one demands, come from your escalation policy rather than a vendor default.
Routing by responsibility
Alerts go to the technician covering that district, the supervisor for that contract, and the account owner where the client needs telling. Out of hours, the path changes.
Grouping over repetition
A unit throwing the same fault eleven times in an hour produces one grouped alert with a count, not eleven notifications that teach people to ignore the channel.
Acknowledgement and escalation
An unacknowledged critical alert escalates on a timer. Every acknowledgement is recorded, so the question of whether anyone was told has an answer.
Critical alerts do more than notify. They open a ticket with the decoded fault attached and start the SLA clock at the moment the controller faulted. See the elevator ticketing system for what happens next.
FAQ
Common questions
From live controller signal: fault frequency and severity, door cycle timing against the unit baseline, motor current trend, downtime in the period, and how many open issues the unit carries. The weighting is agreed with you during the build so the score reflects what your engineers consider serious rather than a generic formula.
Related
Connected modules.
Know the state of your elevators before the phone rings.
Tell us your controller types, your cities and your contract structure. We will come back with what the dashboard reads and how quickly it can be live.