Every stoppage needs
a clear next step.
LYLOX helps your team investigate issues, consult the planned checks and retain context until the technician can take over.
From the alert to the next check.
A stoppage at startup. A recurring alert. An issue that only appears on one job. Context helps you decide where to start.
LYLOX organises the operator's observations and guides checks as new information is added.
- 01Describe what happens and when.
- 02Define the next check.
- 03Prepare the case for whoever takes over.
The press stops when starting the job.
When does the stoppage recur?
Record the exact equipment message and the conditions present when the stoppage occurs.
Finding what the occurrences have in common helps guide the investigation.Issue context
- Issue
- The press stops when starting the job.
- Operator observation
- The stoppage occurs across several jobs.
- Still to check
- Exact equipment message and conditions common to the stoppages.
Cause unconfirmed · Maintenance work not recorded
Illustrative example. Checks are cross-checked against plant procedures.
Prepare for maintenance work with the available context.
Bring equipment documentation and issue history to the person who needs to act. A shared reference for production and maintenance.
- The right equipmentThe machine and assembly the alert refers to.
- The relevant documentationYour plant's manuals and procedures.
- The case statusWhat has been observed and what still needs checking.
Flexographic press
When the technician arrives,
the case already has a history.
Avoid reconstructing the issue from memory. Retain the symptom, observations and open points to continue the investigation with context from the previous shift.
- What was observedWhat happened and under what conditions.
- What was checkedWhat the team checked and with what result.
- What is still pendingOpen questions for the next person responsible.
Stoppage during startup
The stoppage recurs when starting several jobs.
The records reviewed relate to different jobs.
The exact equipment message and the conditions common to the occurrences.
The technician continues from here.
The cause has not yet been confirmed.
Let today's experience help with the next stoppage.
Document the maintenance work and its outcome. The next case can draw on what your team has already observed, checked and resolved.
Equipment history.
Context for the next shift.