Appearance
Trigger All Checks
When a machine stops and there is time to spare, an operator can make all of its checks due immediately rather than waiting for each one's schedule to come round. A planned changeover, an unplanned stop, a quiet end of shift — any window where the line is not running is a chance to get ahead on autonomous maintenance.
This is extra work, not a replacement for the schedule. Completing a check early does not cancel or move its next scheduled occurrence.
Who Can Do This
Any mobile user who can complete checks, including kiosk operators. The person standing at the stopped machine is usually the one who knows there is a window.
Trigger The Checks
- Open the Continual mobile app and select the correct factory.
- Open the
Checkstab, then select the line or group and the asset. - Tap the
⋯button besideStart these checks. - Choose
Trigger all checks. - Confirm the count when prompted — the app tells you how many checks it is about to make due.
- Work through them using the normal check flow.
The option appears whether or not anything is currently due, because an empty due list is exactly when you are most likely to want it.
What Gets Triggered
Every active check on the asset, with two exceptions:
- Checks that are already due are left exactly as they are. You complete those as normal and they count towards compliance in the usual way. This is also why tapping twice is harmless — nothing is duplicated.
- Checks that do not apply to the format the line is running are left out, and the app tells you how many. They could not be completed anyway.
Checks assigned to a different function are still triggered. Queuing work is not the same as doing it, so a trigger raises work for whoever is qualified to complete it.
How Triggered Checks Behave
- They become due immediately and can be completed straight away.
- They are never marked missed. Work nobody was obliged to do cannot count against you.
- Each one stays available until that check's own next scheduled occurrence comes round, at which point the triggered one expires and the scheduled one takes over. Complete the scheduled occurrence instead — that is the one that counts towards compliance.
- Manually triggered checks and on-format-change checks have no next scheduled time, so they stay available until completed or skipped.
- No
Checks Duenotification is sent to the line or factory. The person who triggered them is already there.
How Triggered Checks Are Reported
Results are real observations of the machine, so they are treated as such:
| Counted | Not counted |
|---|---|
| Pass rate | Completion rate |
| Actions raised from failures | Timeliness |
Operations → Checks → Activity | "Checks scheduled" totals |
In other words, anything a triggered check finds is recorded and acted on exactly as a scheduled check's finding would be — but doing extra work never inflates the numbers that measure whether the schedule was followed.
Triggered occurrences are labelled Ad-hoc in the portal's check activity, and the expanded row names the person who triggered them.
Common Problems
The Option Is Missing
- Confirm that you selected the correct factory, line or group, and asset.
- Confirm that the asset has at least one active check.
- Pull to refresh, and check your connection.
Fewer Checks Became Due Than Expected
Some were already due, or some do not apply to the format the line is currently running. The confirmation and the follow-up message both report the numbers.
A Check Expired While I Was Working Through The List
Its scheduled occurrence came round in the meantime. Reload the list and complete the scheduled one instead — nothing is lost, and that occurrence counts towards compliance where the triggered one would not have.
Expected Result
An operator with a downtime window can bring a machine's whole check list forward, complete what they have time for, and have the findings recorded and acted on — without the schedule being disturbed or the compliance figures being distorted in either direction.