Escalator Maintenance Software for Service Companies

By Sujit Katariya, ElevatorPlus ·

In short: Escalator maintenance software is usually lift software with the word escalator typed into a field. That fails quietly. An escalator has no car, no landing doors and no travelling cable, but it does have steps, combs, handrails, balustrades, a drive chain and a bank of safety switches, and it runs all day. Asset records, checklists, schedules, breakdown routing and spares all need to know which machine they are describing.

Key takeaways

• An escalator is a different asset class, not a lift variant. What fails is steps, comb plates, handrails, balustrade panels, chain tension and safety switches. None of that exists on a lift, so none of it exists on a lift checklist.
• Duty cycle drives the schedule, not the calendar alone. A metro unit and a hotel lobby unit wear at different speeds. Planned maintenance needs to run on dates, on recorded running hours, or on both.
• Running hours are recorded by a person. ElevatorPlus does not read anything from the machine. A technician reads the hour meter on site and enters it. That one number, captured regularly, is what makes usage-based scheduling possible.
• A stopped escalator changes how a building works. People do not queue for the next one, they redistribute, and the site owner feels it at once. Breakdown routing has to reflect that.
• Inspection frequency for escalators varies by jurisdiction, so check your local rule. State and national requirements differ, and a system that hard-codes one interval will be wrong somewhere in your portfolio.
• Spares must be held against the right asset. A step for one unit is not a step for the next. Comb segments, handrail lengths and chain links are model specific, and a store built for lift parts cannot answer the question a technician asks at 8am.

What this guide covers: why escalators end up inside lift software · what actually fails on an escalator · how the maintenance record differs · scheduling on running hours or calendar · breakdown routing when a site cannot wait · spare parts held against the right asset · what to ask before you buy · FAQs.

Why do escalators end up inside lift software at all?

Because the company that services them usually started with lifts.

A service business wins a mall contract with fourteen lifts and nine escalators, and the escalators go into the same system because there is nowhere else to put them. Six months later the schedule fires, a technician opens the job, and the checklist asks about door operator timing on a machine with no doors.

The technician ticks it anyway. Everyone does. That is the moment the record stops being worth anything.

Vertical transportation is two trades wearing one coat. A lift is a car in a shaft, hoisted, guided, doored, counterweighted, still for most of the day. An escalator is a continuous conveyor with people standing on it, running the whole time the building is open, carrying its load through a step chain that never stops flexing.

Same customer. Same technician, often. Completely different machine.

What actually fails on an escalator?

Ask any escalator technician and you get the same short list, in roughly the same order.

Steps and step chain. Steps take the load and the abuse. Risers chip, demarcation lines wear off, cleats get damaged by trolley wheels and grit. Underneath, the step chain stretches over its life, and chain tension tells you how far along that life the unit is. That reading belongs in the record.

Comb plates. The comb at each landing is where feet and steps meet, and it is the most common source of entrapment complaints. Broken teeth are a safety finding, not a tidy-up item. A missing tooth changes the gap, and the gap is the point.

Handrails. Handrail speed should match step speed. When it does not, passengers notice first, usually by being pulled slightly forwards at the top. Handrails also crack, delaminate and get contaminated, and the entry point has its own guard and its own switch.

Balustrades and skirt panels. Skirt deflection, clearance, panel joints, lighting. The skirt gap is a safety dimension and it drifts as panels get knocked.

Safety switches and devices. The bank a lift does not have. Comb impact, skirt obstruction, handrail entry guards, step level and missing step detection, drive chain break detection, reversal protection, emergency stops at both landings. Every one has a test and a result, and a lift checklist has nowhere to put any of it.

Lubrication, drive and brake. Chain lubrication, drive chain tension, the main brake, the auxiliary brake where fitted, and what happens when the unit is asked to stop while loaded.

Notice what is absent. No doors. No car. No landing panel. No travelling cable. No counterweight. Roughly two thirds of a lift checklist is inapplicable, and the parts that matter on an escalator have no home.

How does the maintenance record actually differ?

This is the table worth putting in front of whoever owns the system.

Read down the escalator column. Almost nothing carries over. A system that stores one shape of record and calls the other a subtype loses the right-hand column, and the right-hand column is the job.

Does the asset record itself need to change?

Yes, and it is the least glamorous fix with the biggest effect.

An escalator needs its own fields. Rise and inclination, because those decide the number of steps and the access arrangements. Step width, because it decides which step you order. Balustrade type. Indoor or outdoor, because a unit at a metro entrance lives a harder life than one inside a conditioned mall.

It needs its own hierarchy too. A mall is not a flat list of nine machines. It is levels, wings, entrances and pairs, and a record that cannot express "east wing, level one to level two, down unit" produces work orders nobody can find on site.

It also needs the customer's own name for the machine. Site staff say "the one by the food court", and if the record cannot hold that, every breakdown call starts with guesswork.

That is the work asset management has to do before anything else is worth switching on. Get the asset wrong and every checklist, schedule, job and part hangs off a wrong record.

How should planned maintenance be scheduled for a machine that never stops?

Calendar scheduling is the default everywhere, and for lifts it is mostly defensible. For escalators it is blunt.

Two units of the same model, same age, same contract. One is in a metro station running sixteen hours a day with dense standing loads. The other is in a hotel lobby running eight hours a day, lightly used. On a calendar schedule they get the same visits in the same months. One is over-serviced and the other is quietly accumulating chain stretch nobody is measuring.

The fix is not exotic. Record running hours.

Escalators carry an hour meter. A technician reads it and the number goes into the asset record on every visit. That is the whole mechanism. There is no gateway and no automatic feed, and nothing in ElevatorPlus reads anything from the machine on its own. A person reads it and a person enters it. What the system does with it is hold the history, show the accumulation rate, and fire a schedule on hours as well as dates, whichever comes first.

Set up planned maintenance reminders so that both triggers exist, then let the schedule tell you which unit is due rather than assuming the calendar knows.

Why does a breakdown on an escalator need different routing?

Because the site owner's tolerance is different, and it is different for a reason.

When a lift in a bank of four goes out of service, the building copes. The remaining lifts absorb the load, and unless it is the only lift in the building the situation is inconvenient rather than urgent.

When an escalator stops it becomes a staircase, and the way people move through that floor changes at once. In a mall the units are placed where the owner wants footfall to go, so a stopped unit reroutes shoppers away from the shops that paid for that position.

In a metro station it changes crowd flow at the moment crowd flow matters most. In an airport it pushes passengers into corridors that were not sized for them. In a hotel it is simply visible to every guest.

None of that shows up as a downtime figure on a report. It shows up as a phone call from a site manager who is not interested in your SLA clock.

So breakdown handling has to know the asset type and the site type before it sets priority. A call on a paired unit is not a call on the only unit serving a level. And the technician sent needs to have worked on that machine, because escalator faults are frequently safety-switch faults, and finding which switch tripped is not a task you improvise.

Good breakdown management records the fault at device level, not as free text. Comb impact device on the upper landing, tripped, cause found, action taken. Do that for a year and you have a repeat-fault picture per unit that narrative notes will never give you.

👉 Can your system tell an escalator from a lift before the technician arrives?

See how asset records separate the two →

What goes wrong with escalator spare parts?

Almost everything, if the store was built for lifts.

Escalator parts are model specific in a way that catches people out. A step is not a generic step. Width, cleat pattern, colour, demarcation and mounting all vary by manufacturer and by generation. Comb segments are the same story. Handrails are cut to a length that belongs to one rise and one profile.

So the useful question is never "do we have steps in stock". It is "do we have steps for that unit". If inventory is organised by generic part name rather than against the asset it fits, nobody can answer that from a desk.

Two habits fix most of it. Hold the parts list against the asset, so the unit's record carries what fits it. And capture the part reference the first time a technician orders it, so the second order takes minutes instead of a site visit. A bill of materials held per unit is worth building even if it takes a season to populate, because escalator part failures repeat.

Every escalator contractor knows the alternative. A comb tooth is broken, the unit is barriered off, the site manager calls daily, and weeks go on identifying a part somebody already ordered for the same machine two years ago.

What should an operator ask before buying anything?

Six, all answerable in a demo. Can the system hold an escalator as its own asset type with its own fields? Can it carry a checklist listing combs, handrails, skirt clearance and the safety device bank? Can planned maintenance fire on recorded running hours as well as dates? Can a breakdown be routed by asset type and site type? Can a spare part be held against a specific unit? And can the record be produced for a site owner without anyone assembling it by hand the night before?

If the answer to any of those is "put it in the notes field", you have your answer. Notes are where records go to be forgotten.

One more that people forget. Can the technician finish it on a phone at the lower landing, with the unit isolated and no signal? Inspection management that works on paper and then needs re-entering in an office produces a record that will be late, thin and eventually invented.

Frequently asked questions

1. Is escalator maintenance software different from elevator maintenance software?

It should be. One system can and should hold both, but the asset record, the checklist and the schedule logic all have to differ. Software that only models a lift forces escalator work into fields never designed for it.

2. How often should an escalator be inspected?

Statutory inspection frequency for escalators varies by jurisdiction, so check your local rule. It is often set by a different regulation from the one covering lifts, and it can differ between states within one country. Contractual planned maintenance frequency is a separate matter, agreed with the customer and driven by duty cycle.

3. Can maintenance be scheduled on escalator running hours?

Yes, provided the hours are recorded. A technician reads the hour meter on site and enters the reading. The system stores the history and can trigger planned maintenance on accumulated hours, on the calendar date, or on whichever comes first. Nothing is read from the machine automatically.

4. What is on an escalator maintenance checklist that is not on a lift checklist?

Step condition and step chain tension, comb plate teeth and alignment, handrail speed and condition, handrail entry guards, balustrade and skirt clearance, drive chain tension and lubrication, and the escalator safety device bank including comb impact, skirt obstruction, missing step and reversal protection.

5. Why does a stopped escalator matter more to a mall than a stopped lift?

Because it changes how people move through the building. Escalators are positioned to direct footfall, and when one stops that flow goes somewhere else. Tenants notice and the site manager calls. The disruption is qualitative rather than a number on a report, which is why it does not show up in downtime statistics.

6. How should escalator spare parts be organised?

Against the asset, not against a generic catalogue name. Steps, comb segments, handrails and chain components are specific to the model and often to the generation. Holding a parts list per unit turns a three-week identification exercise into a same-day order.

7. Do escalators and moving walkways need separate handling?

They are close relatives and the same logic applies. A moving walkway has pallets rather than steps and runs level or on a shallow incline, but the comb, handrail, chain and safety device structure is the same family. Both belong in an asset type that is not "lift".

8. Can one system run lifts and escalators for the same customer?

Yes, and it should. A mall contract covers both and the site manager wants one contact. What matters is that inside the system the two asset types keep their own records, checklists and schedules rather than being flattened into one.

📲 Join our WhatsApp channel for compliance tips, updates: ElevatorPlus - Business Automation Tool

Escalators are the part of a portfolio that gets managed by memory. Technicians know which unit eats steps, which chain needs watching, which comb has been replaced twice. That knowledge is real, undocumented, and it leaves with whoever leaves.

Software does not make anyone better at escalator work. It stops the knowledge being personal. A checklist that asks the right questions produces a record of the right answers. A schedule that knows the duty cycle sends people to the unit that needs them. A parts list held per asset turns an argument into a lookup.

The test is simple. Open your system and look at how an escalator is stored. If it is a lift record with the word escalator in a text field, that half of your portfolio is being run on goodwill.

Which works until the day it does not, and on an escalator that day tends to be a day when the machine is full of people.

👉 See how one record handles lifts and escalators without pretending they are the same machine. Book a demo →

Related reading

• Asset management built for lifts, escalators and moving walkways
• Planned maintenance and AMC reminders that fire on the right trigger
• Breakdown management for portfolios where downtime is visible
• Inspection management your technicians can complete on site
• Inventory and spare parts held against the asset they fit

About the author. Sujit Katariya ElevatorPlus, the Elevator Business Operating System used by 200+ elevator companies across 20+ countries.

Book a Demo with ElevatorPlus

👉 Follow ElevatorPlus on,
Instagram LinkedIn Facebook YouTube Qoura Substack Twitter