History stays with the frame
Every leg is keyed on its stamped mechanical serial. Swap a controller and the operational identity rolls over, but wear, intervals and warranty stay with the frame.
Erektor fleet lifecycle
Two consoles. One serial for every leg.
The Erektor Return System runs the recovery line at each of your facilities, on a dedicated server installed with the line, so what the line records stays on site. The Service Console is online, where your company looks after the fleet while it is out on builds. Every leg carries the serial stamped into its frame through both, so its life reads as one history.
One account signs in to both.
Erektor Return SystemOn a server at each facility · when a leg comes home
Frame serial
One account · one serialYour company, facilities and the stamped frame serial
Service ConsoleOnline · while a leg is out on a build
Side by side
Each console covers half of a leg’s life.
A leg spends its working life going out to builds and coming home again. The Return System records what happens when it comes home; the Service Console covers the time it is out. One account signs in to both.
| Compared | Erektor Return System | Service Console |
|---|---|---|
| Where it runs | At each facility, beside the recovery conveyor | In the field and the office, anywhere with a browser |
| Who uses it | Facility operations teams | Your field crews and fleet managers |
| Part of the leg’s life | Coming home: check-in, inspection, cleaning, battery swap, diagnostics, controller check-in, back to the pool | Out on builds: delivery to site, flags raised in the field, replacements dispatched |
| What you do there | Recondition legs and keep the available pool full | Request a replacement, schedule maintenance, read the procedures and the firmware manifest |
| What it records | Check-ins, inspection and diagnostic results, pack swaps, service records | Maintenance flags, emergency replacements and the fleet’s leg registry |
| Where the data lives | On a dedicated server at the facility, installed with the line | Online, in the Erektor leg registry |
| Without the internet | Keeps running; the line never waits on a connection | Needs a connection |
The life of a leg
From stamped frame to retirement, nothing falls between the two.
- Built & commissionedFrame stamped, electronics bound and tested
-
Service Console
- Assigned out
- Delivered to site
- Working builds
- Flagged or replaced
Return SystemRepeats for every build, under the same frame serial- Checked in
- Inspected & serviced
- Pack swapped
- Back to the pool
- RetiredOut of the fleet, with its history intact
What the manufacturer sees
The lifespan of every Erektor asset, in one place.
Every leg is followed by the serial stamped into its frame, on the line and in the field, so decisions about servicing, reconditioning and retiring it rest on its whole working life, not on whichever site saw it last.
Service by use, not the calendar
Intervals accrue in motor-hours against the frame and are flagged at 85%, so maintenance is booked ahead of time, from how hard each leg has actually worked.
Failures traced to the frame
ERS records every inspection and diagnostic failure against the frame serial, and every replacement dispatched from the field is filed under that same serial. A leg that keeps coming back stands out, and quarantining or retiring it rests on evidence.
No leg quietly disappears
Every departure, delivery and return is logged. A leg the fleet has not heard from in 45 days is reported, and a leg that moved between facilities is settled on the books instead of being written off as lost.
Battery packs have their own lives
Packs are swapped on the line and charged off it, and ERS tracks each one on its own, so pack wear never hides inside the leg’s history.
What every leg is running
Controllers re-register at check-in on the line, and every firmware update is recorded in the leg registry, so the fleet’s software state is known rather than assumed.
See your fleet’s record.
Sign in with your Erektor account to see every leg assigned to your facilities, what each one needs next, and every request filed for them.