Elevator and Escalator Energy Monitoring

Elevators and escalators are the equipment every building has and almost nobody monitors. They run on a contract with an OEM service provider, their energy consumption is buried in the general-power meter, and their maintenance is scheduled on a calendar rather than on evidence. In a high-rise office tower, vertical transportation can account for a surprisingly visible share of the electricity bill — in the range of 5–10% of a building’s total use, concentrated in the demand peaks that drive your demand charge. What makes them worth instrumenting is that their energy behavior is tightly coupled to their mechanical health: a car that runs more trips than its traffic justifies, a drive that returns less regeneration than its design allows, and a door that cycles far more often than the OEM’s maintenance interval assumes are all the same signal read three different ways.

How Vertical Transportation Actually Uses Energy

A counterweighted elevator is a two-way machine: it consumes energy lifting a loaded car, and it returns energy to the supply when the counterweight overbalances the car and pulls it down — or when the loaded car drives the counterweight up. Older non-regenerative drives burned that energy off as heat in resistors. Modern variable-voltage, variable-frequency (VVVF) drives with regenerative capability feed it back to the building grid, and the physics of that recovery is what makes the monitoring interesting.

The energy profile is dominated by four factors:

• Trip count and traffic pattern. Each full-height run is roughly 0.5–1.5 kWh depending on car load, speed, and building height; a busy lobby-to-upper-floor pattern is the expensive one.
• Counterweight balance. The standard 45–50% balance means a lightly loaded car consumes far less than a full one — but only if the drive is doing its part of the work. A drive running without regeneration converts every downhill run into waste heat.
• Standby and ancillary loads. When idle, the car still draws power for the controller, the cabin lighting, the ventilation fan, and the door operator. A car “parked” for the night can still be drawing a kilowatt-class trickle that runs 24/7.
• Escalator no-load running. An escalator with no passenger detection runs its motors at full speed from opening to closing, every day, moving nobody.

Regenerative Recovery: Measuring What the Drive Returns

Regenerative drives are the headline efficiency feature of modern elevators, and they genuinely deliver: a high-rise elevator with a well-balanced car and heavy traffic can recover 20–30% of its energy consumption during a busy day — meaning it effectively runs at that fraction of what a resistor-based drive would consume. But regeneration is not automatic; it requires a working regenerative unit, correct counterweight balance, and a drive that actually sends recovered power back instead of dumping it. Two elevators of identical model on the same building can differ by more than 10 percentage points in recovery depending on setup and control tuning.

Monitoring makes recovery visible: a sub-meter on the elevator feeder with per-direction energy tracking, or — better — a direct read of the drive’s regenerative energy register over its serial interface, shows the building team whether the regeneration promised at commissioning is actually happening. When a drive’s recovered-energy figure drops month over month, the cause is usually mechanical drag (bad guide shoes, brake drag, rope friction) — which is exactly the fault the maintenance contract is supposed to catch, now caught by data instead of by a scheduled inspection.

Standby Management and Idle Detection

The largest single monitoring-driven saving in vertical transportation is usually standby discipline. A car left with lights and fan running all night, or an escalator run at full speed with no traffic, is pure waste that no traffic pattern justifies. The monitoring stack delivers three related capabilities:

• Idle detection from the controller. Modern controllers report the time since the last call; a car idle more than, say, 90 seconds can drop into standby mode that dims the lights and shuts the ventilation fan, saving on the order of 0.5–1 kW per car per idle hour.
• Escalator passenger detection. Presence sensors (infrared, pressure, or camera-based counting) allow escalators to run slow or stop between passengers, recovering a large share of their always-on consumption. A busy shopping-center escalator runs far more hours than it carries passengers; the ratio is typically worse than 1:3.
• Schedule-based hunting. Banks of cars can be put to sleep at night and brought up by a time schedule or a pre-call — a standard feature that is only effective if the platform tracks whether the cars are actually sleeping and actually waking.

A Worked Example: The 12-Car Office Tower

A 30-story office tower with a bank of twelve elevators and four escalators in its atrium was monitored for a quarter. The baseline showed the group consuming about 480,000 kWh per year, or roughly 7% of the building’s total. The monitoring data produced three findings:

1. Regeneration shortfall. The three cars serving the lower floors recovered only 8% of their consumption while the upper-floor cars recovered 24%. A drive inspection found the low-rise cars’ regenerative units were disabled during a firmware update two years earlier; re-enabling them cut that bank’s consumption by about 14%.
2. Night standby. Between 11 p.m. and 6 a.m., the bank drew 9 kW total — mostly standby loads. Reconfiguring the group controller to park cars with lights and fans off, and to sleep the atrium escalators after closing, saved roughly 68,000 kWh a year.
3. Door-cycle evidence. The door-operator logs showed the lobby doors cycling 40% more than the OEM’s service-interval assumption. The maintenance contract was renegotiated to condition-based intervals, catching a failing door motor at 9,000 cycles instead of at the 12,000-cycle scheduled visit.

Combined, the three findings cut the group’s consumption by about 22%, and the regeneration and standby changes required no hardware beyond the monitoring and a control reconfiguration.

Maintenance Scheduling From Evidence

The maintenance payoff is the one that usually justifies the project even when the energy numbers are marginal. Elevator service is expensive, emergency call-outs are disruptive, and both are driven by components whose wear is measurable:

• Door operator cycles. The highest-wear subsystem in most installations; cycle counts predict belt, motor, and roller failure far better than calendar days.
• Motor current and torque. A current trace that climbs steadily on identical runs indicates mechanical drag building up long before a noise complaint.
• Vibration on the car and drive. Acceleration-axis sensors on the car floor detect guide-rail wear, rope issues, and alignment drift; the trend precedes the roughness passengers complain about.
• Ride-quality events. Data on jerk and leveling errors correlates with passenger experience scores and predicts which cars will get the next complaint call.

With these signals, the building can move from a fixed OEM calendar — which over-serves some cars and under-serves the ones that actually fail — to a condition-based plan that swaps the failing component before it takes a car out of service during the morning peak.

The Data Sources and Integration Approach

Vertical-transportation monitoring is a pragmatic integration exercise because the controller already measures most of what you need:

• Elevator controller serial interfaces (most modern groups expose the drive’s trip, energy, fault, and state registers) are the primary source.
• Sub-meters on the feeder provide the ground-truth AC-side consumption and catch loads the controller does not report.
• Standalone sensors — door contact, vibration, passenger-count — fill the gaps for older installations that predate rich controller telemetry.
• BAS integration gives the group controller the schedules and standby commands, while the monitoring platform records whether those commands took effect.

The platform’s job is to normalize all of these into one record per car and escalator, so “energy used, trips made, regeneration returned, doors cycled, faults logged” is answerable per unit, per day, with the trend visible.

The Bottom Line

Vertical transportation repays monitoring out of proportion to its share of the bill, because the same data that saves energy also catches maintenance problems early and gives the building leverage over its service contract. Regeneration recovery, standby discipline, and condition-based maintenance are three mechanisms, all driven by the same small set of sensors, and all measurable with a per-unit, per-month accounting that makes the saving defensible. Integrar IoT’s platform reads elevator and escalator controller data alongside feeder sub-meters, tracks regeneration and cycle counts against baselines, and feeds the condition-based maintenance and energy reports from the same data source.