Appearance
Actions
Actions are trackable work items that capture problems found on the production floor. They link a failure back to the check that found it, record the root cause, and close the loop once the issue is fixed and verified.
How Actions Are Created
Automatic Actions
When a check result fails, the system automatically raises an action:
- A failing CIL check creates a defect action.
- A failing Centreline check where the value is outside the target range creates a deviation action.
Only one active automatic action exists per check at a time. If a check keeps failing, the existing action accumulates the failure count rather than creating duplicates.
Auto-close for deviations: A deviation action closes automatically when the next result for that check passes. This reflects the nature of centreline deviations — often transient and self-correcting.
Manual resolution for defects: A CIL defect action requires explicit resolution by a Manager or Admin, followed by verification that the fix held.
Manual Actions
Managers and Admins can raise actions manually — for example, to capture an observation that did not come from a failing check, or to record a corrective task that needs tracking.
- In the portal, go to
Operations->Actions. - Click
Create action. - Select the factory, Line or Group, and machine.
- Enter a title and optional description.
Managers, Admins, and Owners can also create manual actions from the Actions tab in the mobile app.
Action Lifecycle
Actions move through three statuses:
| Status | Meaning |
|---|---|
| Open | The problem exists and has not been addressed. |
| Pending verification | A resolution has been submitted; awaiting confirmation that it held. |
| Closed | The action is fully resolved and verified. |
Resolving An Action
When you have addressed the root cause:
- Open the action (portal or mobile).
- Select
Resolve. - Choose a root cause category:
- Equipment fault: A machine or tool was at fault.
- Consumable material: A raw material or consumable caused the issue.
- Operator error: Incorrect technique or procedure.
- Process issue: The process itself was out of spec or undefined.
- Other: Anything that does not fit the above.
- Add a resolution note describing what was done.
- Submit.
The action moves to Pending verification. It closes automatically when a subsequent check result for that check passes, confirming the fix held.
Viewing Actions
In The Portal
Go to Operations -> Actions to see all actions across your factories. Filter by:
- Factory, line, or machine
- Status (open, pending verification, closed)
- Category (defect or deviation)
- Date range
Click an action to see its full history, including every state change and who made it.
In The Mobile App
The Actions tab in the mobile app shows open and pending actions for your selected factory. Tap an action to view details or submit a resolution.
Actions In Insights
The Analytics -> Insights -> Actions tab gives a cross-category view of every action (defects, deviations, and manual), including:
- Count of actions created per period, by category
- Median time to resolution (MTTR), by category
- Top affected machines
- Root cause breakdown
The Defects and Deviations tabs give the same kind of breakdown scoped to just that category — Defects additionally shows a resolution-time distribution (how long defects take to close, bucketed).
See Insights for details.
Who Can Do What
| Action | Operator | Manager | Admin | Owner |
|---|---|---|---|---|
| View actions | ✓ | ✓ | ✓ | ✓ |
| Create manual action | ✗ | ✓ | ✓ | ✓ |
| Resolve an action | ✗ | ✓ | ✓ | ✓ |
Auto-close is system behaviour, not a user permission: a deviation action closes automatically when the next result for its check passes, regardless of who submitted it.