Smart Elevator Operations Suite
Run every elevator from one screen.
Elevator management software built to your specification. Live lift data, fault detection, ticketing, maintenance, dispatch, proposals and accounts in one suite, so the whole team works from a single source of truth instead of four tools and three people's memory.
Where the day goes wrong
Most elevator companies did not choose their software. It accumulated.
A monitoring tool here. A maintenance spreadsheet there. Quotes in email, complaints on the phone, accounts in a system nobody reconciles until month end. Every handoff between those tools is a place where something falls through. Here is what that looks like in practice.
The fault nobody saw
A lift throws an intermittent door fault on Tuesday. The controller logs it. Nobody reads the controller. On Friday the door strands a passenger and the callout costs a technician, a night rate, and a hard conversation with the building manager.
The ticket that went cold
A complaint arrives on WhatsApp. Someone screenshots it into a group. Someone else says they will handle it. The SLA clock has been running for six hours before anyone opens a record, and there is nothing timestamped to prove otherwise.
The AMC visit that lapsed
Service intervals live in a spreadsheet one person maintains. That person goes on leave. Two contracts miss a quarterly visit. The customer finds out before you do.
The invoice that never went out
Work is done, parts are consumed, the job card is on paper in a van. Accounts reconcile at month end from memory and email. Revenue leaks quietly between the tools, and nobody can say which contracts are actually profitable.
The difference
Built to your spec, down to the invoice.
Elevator software vendors sell a fixed product and ask you to reshape your business around it. Your contract tiers become their tiers. Your approval chain becomes their three-step approval. Your billing rules go into a spreadsheet because the product cannot express them.
RnD Square works the other way. We document how your business runs, write it up as a specification, and engineer the suite against it. That includes the layers most elevator platforms skip: the ERP that moves parts, the accounting that bills the AMC, and the custom workflows that make your operation different from the company down the road.
The hardware and firmware come from the same team, so the data underneath is real controller signal rather than numbers a technician typed in three days later.
The software layer
Seven modules. One record per lift.
Each module is a page in its own right, and each one reads and writes the same asset, contract and customer records. A fault becomes a ticket, the ticket becomes a visit, the visit becomes a service record, and the service record becomes a line on the invoice.
Live controller event on a unit
Raised with the fault data attached
Technician dispatched to site
Spare consumed and logged
Billable line on the contract
Bring us your current process, spreadsheets and all. We will show you what the suite would look like built around it.
Book a Working Session →The business layer
The part other elevator platforms leave to you.
Operations software that stops at the job card leaves the hard half of the business in spreadsheets. Parts do not order themselves, AMCs do not bill themselves, and renewals do not chase themselves. These modules sit on the same records as the service layer.
Anything the list does not cover
If your operation has a workflow nothing off the shelf models, that is a build item rather than a dead end. See custom elevator workflows for how bespoke processes get engineered into the suite.
How it gets built
Specification first. Then code.
We map how you work today
Controller types, site structure, contract tiers, approval chains, billing rules, and the spreadsheets and WhatsApp groups that hold the gaps together. The output is a written specification you sign off before anything is built.
We build the data layer first
Interface hardware and controller firmware come from the same team, so the suite reads real signal from your lifts. Every downstream module works from that data rather than manual entry.
We deliver the module that hurts most
Usually ticketing and maintenance. It goes live with your data, your states, your SLA definitions, and your team using it in production before the next module starts.
We extend into the business layer
CRM, ERP, accounting and account management are added against the same records, so a job card, a part, an invoice and a renewal all reference one truth.
We keep engineering it
New controller types, new workflows, new reports and new integrations are handled as extensions by the team that built the system. You are not filing feature requests into a product backlog you cannot see.
Who runs on this
Fifty lifts or five thousand.
The suite is scoped per engagement, so a regional AMC provider and a multi-city OEM get different builds from the same engineering team and the same underlying platform.
Elevator OEMs
Ship a connected product line and run the service business behind it on one system.
AMC and service companies
Contract-driven operations with SLA exposure, recurring billing and technician utilisation to defend.
Modernization integrators
Mixed-brand, mixed-vintage portfolios where the controller landscape is never uniform.
Distributors and dealers
Multiple principals, multiple territories, and one view of installed base and renewals.
FAQ
Questions buyers ask first
No. Most engagements start with the module that hurts most, usually ticketing and maintenance, then consolidate the rest over time. There is no big-bang cutover. Existing tools stay in place until the replacement is proven in production with your own data.
Connected operations
One operations center, every system talking to it.
The modules share one data layer, so a fault becomes a ticket, a ticket becomes a job, a job becomes a billable line, and every one of them stays tied to the same lift. Nothing is re-entered by hand between systems.
Operations
Related
Where to go next.
Your workflows. Your suite.
Tell us how your operation runs and which part of it is costing you the most right now. We will come back with a scope, a sequence and a timeline.