Elevator Analytics Software
The numbers that run the business, in one place.
AMC billing, revenue, contract margin, SLA compliance and elevator health, reconciled from the same records operations already work in. No rebuilding the month in a spreadsheet after it has ended.
The problem
When accounts sit in one system and operations in another, month end is an archaeology project.
The work happened in the field. The record of it is in job cards, emails and a ticket list. The invoice is built somewhere else entirely, by someone piecing it together. By the time the numbers agree, they describe a month that is already over, and nobody can say with confidence which contracts made money.
What it reports on
Four views of the same operational truth.
Billing, margin, compliance and elevator health are computed from the same underlying records rather than four separate extracts that disagree with each other in a meeting.
AMC billing software
AMC and contract billing
Billable, raised, due and overdue positions per contract
Recurring AMC schedules generated from contract terms
Chargeable work from approved proposals and completed job cards
Parts and labour priced against your own rate cards
Credit notes, adjustments and disputes tracked against the original line
Contract margin
Revenue and profitability
Revenue by contract, site, city and service line
Cost to serve from technician hours, travel, parts and callout frequency
Margin per contract, so loss-making accounts stop hiding in the average
Modernization and repair revenue separated from recurring AMC income
Renewal exposure by value, ahead of the contract date rather than after it
Elevator SLA reporting
SLA compliance
Response and resolution performance per contract tier
Breach count, near-miss count and the units driving both
Timestamped evidence behind every figure, pulled from ticket history
Client-ready export formats built to your report templates
Penalty exposure calculated against contract terms rather than estimated
Elevator performance
Elevator health KPIs
Uptime and downtime by unit, site, city and client
Fault trends over time, grouped by category and controller family
Mean time to respond and mean time to restore
Maintenance completion rates against contracted schedules
Technician utilisation, first-time fix rate and repeat visit rate
Sample shape only. Revenue and cost to serve sit against each contract so margin is visible.
Send us the report you rebuild by hand every month. We will show you what it looks like generated.
Book a Session →Why RnD Square
A report is only as honest as the data feeding it.
An uptime figure calculated from statuses typed in by a supervisor is an opinion with a decimal point. RnD Square builds the interface hardware and the controller firmware, so downtime, fault counts and usage come off the machine. When a client challenges a number, the trail goes back to a controller event with a timestamp.
The same applies on the commercial side. Because dispatch, parts, proposals and billing all live in one built-to-spec suite, cost to serve is captured while the work happens rather than estimated afterwards. That is what makes contract margin a number you can act on at renewal.
Report formats, KPI definitions and billing rules are specification items. If your business measures first-time fix differently from the industry default, the system measures it your way. See the elevator management software suite for how the modules underneath connect, and the accounting module for the finance layer.
A sample figure. Real compliance is computed from your timestamped ticket history.
FAQ
Common questions
Yes. Every figure can be sliced by contract, site, building, city, region or service line. Client-facing reports and internal management reports are separate formats built to your templates, because what you show a customer and what you show the board are rarely the same view.
Related
Connected modules.
Stop rebuilding the month in a spreadsheet.
Tell us how your contracts are billed and what your management pack looks like today. We will come back with a scope for the reporting layer.