For elevator manufacturers
Ship a connected lift
with your name on it.
Elevator IoT for OEMs, engineered to your controller and branded as your product. White-label hardware and firmware, an elevator dashboard your dealers work from, and the billing layer behind a monitoring contract. You get a connected product line. RnD Square does the engineering.
Where manufacturers are being squeezed
The product is fine.
The data story is missing.
Regional and mid-size elevator manufacturers build good lifts. What they are losing on is the layer the large players wrapped around theirs a decade ago. Four places it shows up on the invoice.
The tender asks whether the lift is connected
Specification documents from developers, facility managers, and government buyers increasingly assume remote monitoring. If the answer is no, the conversation moves to price, and price is a fight you win by giving something away.
The competitor brochure has a dashboard in it
The multinationals ship connected lifts as standard and use the data story to defend premium pricing. A regional OEM with better engineering and no telemetry looks older than it is.
Your dealers cannot see their own installed base
The people selling and servicing your product in the field have no visibility of the units they are responsible for. Every status question becomes a phone call to your office, and every service failure lands on your brand.
The relationship ends at handover
A lift sells once and is serviced for twenty five years by somebody else. Without a connected product there is no mechanism for the manufacturer to hold a recurring commercial position in that period.
What gets engineered
Six blocks between your controller
and a shippable product.
Standing up an internal IoT team means hiring hardware engineers, firmware developers, cloud architects, and deployment specialists, then waiting. This is the same scope, delivered as an engagement, with your product at the end of it.
Documented at signal level
Board and firmware to your panel
Dashboard, portal, and enclosure
The customer sees your product
Controller signal mapping
Your controller documented at signal level: pin configuration, protocol format, fault register structure, electrical characteristics, and behaviour across the revisions you have shipped. Every design decision starts from this map.
Interface hardware
A board designed to sit inside your panel and read your controller. Engineered for the electrical interference, vibration, temperature, and space constraints of the environments your lifts actually go into.
Controller-specific firmware
Firmware that translates your controller output into structured elevator data: floor position, direction, door state and timing, motor current, trip counts, and fault codes decoded into plain language.
Edge buffering and connectivity
Local buffering for the basements and lift shafts where connectivity drops, then encrypted transport with device authentication over cellular or Ethernet as the site allows.
OTA update architecture
A firmware delivery path to the whole installed base, with staged rollout, targeting, and rollback. New controller variants and fixes reach the field without truck rolls.
Branded dashboard and dealer portal
Your brand on the elevator dashboard, your dealer hierarchy in the permission model, your territory rules in the data visibility. The customer sees your product end to end.
Send us your controller specification. We will tell you exactly what data can be read from it and what the interface would look like.
Book a controller assessment →The commercial case
A lift sells once.
Monitoring bills monthly.
The reason the large manufacturers pushed connectivity into standard specification is that it changes the shape of the revenue. A connected installed base gives the OEM a commercial position for the whole life of the unit instead of a single sale and a warranty obligation.
Monitoring attached at the point of sale
A connected lift supports a monitoring or extended service plan sold with the unit or attached at handover. The contract, the billing, and the renewal live in the same system as the telemetry, so the subscription is administered where the evidence of value already sits.
A reason to stay in the service conversation
When the manufacturer holds elevator health data across the installed base, the annual service discussion with the building owner has something behind it. Fault trends, uptime, and component wear are arguments a spreadsheet cannot make.
Warranty exposure you can actually see
Fault patterns across a production batch surface early rather than as a wave of claims. Component behaviour in the field becomes engineering feedback into the next revision of your product.
Channel performance you can measure
Response times, fault resolution, and service delivery per dealer become visible. Territory decisions, dealer support, and channel investment stop being based on who complains loudest.
Why RnD Square
Your extended
R&D team.
Off-the-shelf products ship one fixed design and expect your controller to be normal. RnD Square starts from your controller, your brand, your channel, and your commercial model, and builds to that. You keep the customer relationship and the brand. We build the product behind it.
- A connected product line under your own brand
- Interface hardware built for your panel environment
- Firmware that decodes your controller into plain data
- A dealer portal scoped to your channel and territories
- Over the air updates across the installed base
- A monitoring contract with billing built in
Hardware and firmware in house
The board and the firmware are designed by the same team that builds the platform. When a controller does something unexpected, there is no vendor boundary to argue across.
The whole stack, not the sensor
Telemetry alone does not make a product. Operations, dealer management, CRM, ERP, and accounting are part of the same build, so the monitoring contract has somewhere to be sold, tracked, and billed.
Staged, not big bang
Most OEM engagements start with one controller family and a pilot batch, prove the data, then extend across variants and markets. Each stage is designed so the next one does not require a rebuild.
FAQ
What manufacturers ask first.
Related
Go deeper on the build.
Your controller. Your brand.
Our engineering.
Tell us the controller families you ship, the size of your installed base, and the markets your dealers cover. We will come back with a technical assessment and a staged build plan.