Your people run it. Not ours.
A cell your team cannot operate is a cell you did not buy. We train the technicians who already keep your floor running, and we ship a machine that explains itself to them.
This is the screen your operator stands in front of.
Not a report and not a dashboard — the working screen at the machine. Press the soft keys along the bottom the way you would on the floor. When it stops, follow the fault back to what caused it.
The last four brackets did not go all the way into the fixture. I am picking them up about 2 mm too far forward, so they are going in at an angle.
What I did, step by step — press a stepI gripped the bracket 2.1 mm further forward than I normally do — outside my usual range. The four before this one drifted the same way, each a little further than the last.
Every guide is written for this cell and this part, not a generic manual. Escalation is a named person, not a ticket queue.
Representative screen, shown to illustrate how the cell explains itself. Layout and wording are worked out with each customer's operators and will differ on your floor.
Designed with the people who have to use it at 3am.
We do not design the technician interface in an office and hand it over. We sit with your operators and maintenance techs, watch how the job actually gets done on your floor, and shape the screens around that workflow. The people who will live with this thing every shift are the ones who tell us what it needs to say.
We start by watching
Before a screen is drawn, we learn how your team already diagnoses a stoppage — what they check first, what they trust, and what they ignore.
Their words, not ours
The cell reports faults in the language your floor already uses for the process, not in model telemetry that needs a translator.
The same view we use
No privileged internal tool. If our engineer needs it to resolve an incident, it is on your technician's screen too.
It keeps changing
Operators tell us what is in the way and we move it. The interface a cell ships with is not the interface it runs a year later.
Most automation is sold to a plant manager and abandoned to a maintenance tech.
Robotics programs rarely fail at commissioning, when everyone is watching. They fail four months later, when the one person who understood the cell takes another job and nobody left in the building can say why the arm has started missing.
The specialist trap
If every fault needs a call to the vendor, you have not bought a machine. You have rented a dependency, and it prices itself into every hour the line is down waiting for someone else's calendar.
The instinct already exists
The people who keep your presses and CNCs running have spent careers on symptom, hypothesis, test, cause. That expertise is real and it transfers. What it has never been given is equipment that answers back.
Skills compound
The technicians who learn to run flexible automation now are the ones who will know how to run whatever replaces it. Training is not a line item on the install. It is the part that keeps paying.
What your team learns.
Training is scoped by role. An operator does not need what a maintenance tech needs, and neither should sit through the other's material.
Daily operation
Start, stop, load, and clear the cell. What normal looks like, and when to escalate.
Reading a fault
Work the interface back from the symptom to what the cell was actually doing.
First-line recovery
The failures that come up most, and how to clear them without calling anyone.
Changeover
Move the cell to a known part and confirm it is running right before you walk away.
Safety & lockout
The guarding envelope, the stop behavior, and safe entry for service.
Preventive maintenance
The scheduled work, the wear parts, and what to watch between services.
Training runs alongside the build, not after it.
The fastest way to learn a cell is to watch it being stood up. Your technicians meet the machine during qualification and pilot, while our people are still on the floor with them, so handover is a formality rather than an event.
- 01ScopeWe agree who gets trained and to what level.
- 02Pre-buildCell built and tuned at Relling HQ, not your line.
- 03ConfigureMaterials written against your part and your line.
- 04QualifyYour techs see the cell proven before it ships.
- 05PilotThey run it with us standing behind them.
- 06ProductionThey run it. We are on call, not on site.
- 07FleetYour trained techs bring up the next cell.
The test is whether it runs when we are not there.
Training programs are usually judged by attendance. That measures nothing. The number that matters is how often your floor resolves an incident without picking up the phone.
Covered support, on call
Remote diagnosis and on-call escalation when a cell is down, under the same agreement that covers maintenance and updates.
Fleet visibility
Live health, status, and OEE per cell, so a developing problem is visible before it stops the line.
Failure attribution without ML expertise
Natural-language attribution and a recommended action, so a technician gets a cause rather than a stack trace. In development under Fuselage.
Adjustment without retraining
Correcting drift at runtime in minutes instead of days-long retraining cycles. In development under Fuselage.
Steady-state OEE above 85%, mean time to repair under two hours, and 90% of incidents resolved by your own plant technicians without escalating to us.
These are the targets of the Fuselage program, not a record of shipped deployments. The longer argument sits in the manufacturers brief.
Bring Relling to your shop floor.
We started Relling to help American manufacturers make more of what this country needs. We'll scope projects to your needs and quote you so that your ROI typically closes within 18 months.
