Factory-floor
guidance.
Deliver approved changeover and troubleshooting guidance at the line.
The opportunity
Design for the moment that matters.
What breaks today
Procedure binders and small tablets force workers to look away from the equipment. Expert support is often centralized and arrives only after output has stopped.
The presence pattern
A dedicated Space presents the relevant step, remote engineer or training model at a safe sight line, with simple state controls for the local operator.
Design requirements
Make it useful before making it magical.
- 01
Never obstruct the task
Position the presence and references so workers retain sight lines, movement and access to controls.
- 02
Respect authority
Make clear who can advise, who can approve and which local safety procedures always take precedence.
- 03
Capture operational proof
Measure completion, errors, escalation and repeat visits rather than engagement alone.
Operator runbook
Design the complete service—not only the scene.
- 01
Frame the service
Manufacturing engineering teams should document the intended audience, room, session length, approved content or knowledge, human escalation path and the current baseline for changeover time.
- 02
Invite with clarity
Before the factory-floor guidance experience begins, explain why the presence is there, whether it is live, recorded or AI-assisted, what it can do and how a participant can leave or reach a person.
- 03
Operate the moment
A dedicated Space presents the relevant step, remote engineer or training model at a safe sight line, with simple state controls for the local operator. The operator should be able to observe state, recover the session and protect the physical activity already happening in the room.
- 04
Close the loop
End with a visible next step, capture only consented information and record changeover time, error rate, expert escalations. Review failures and handoffs before repeating or expanding the experience.
Pilot scorecard
Prove a real outcome in the room.
Changeover time
Define the starting event, completion event and current-workflow baseline for changeover time. Count only observable outcomes.
Error rate
Review error rate by audience, session stage and operator. Use the pattern to find where confidence is gained or lost.
Expert escalations
Set a minimum threshold for expert escalations before launch. Name the owner and recovery action when a session misses it.
Decision gates
Know when presence is—and is not—the answer.
Presence must earn the room
If the same factory-floor guidance outcome can be achieved by a well-designed phone, kiosk or conventional video call with equal trust and clarity, use the simpler tool.
The boundary must stay visible
Do not launch factory-floor guidance until participants can identify the role, source, live or synthetic state, information boundary and human fallback without guessing.
The operation must survive novelty
Manufacturing engineering teams should be able to run, pause, recover and measure the experience repeatedly. Do not scale while success depends on a founder or engineer standing beside it.
Evidence status. This page is a product-design field brief, not a claim that Reality Relay has already produced the stated customer outcome. Replace the hypothesis with measured pilot evidence before presenting it as proof.
Build the first pilot
Start narrow enough to learn.
For Factory-floor guidance, begin with one real environment, one defined audience and one repeatable interaction. Establish who operates the experience, what information or tools it can access and exactly when a person must take control.
Reality Relay Platform coordinates content, session state, approved intelligence and operations. Reality Relay Spaces give the experience a calibrated physical endpoint with intentional scale, eye line, sound and grounding. The pilot should earn expansion by improving the scorecard above—not by novelty alone.
- Primary audience
- Manufacturing engineering teams
- Experience family
- Industrial & field operations
- First decision
- Choose the room, baseline and accountable operator
- Expansion rule
- Scale only after the scorecard beats the current workflow