Actions
Route: Admin → OEE → Actions (/admin/oee/actions)
An action is one standard corrective response to a downtime event — "Replaced belt", "Called maintenance", "Cleared jam". This screen is the flat master list; Action Trees arranges those actions into the hierarchy an operator navigates. It is the exact counterpart of Reasons and its reason trees.
Permission
perm:oee-config:write, the same permission as every other screen under Admin → OEE. OpSee has no admin bypass — without it the route renders Access Denied and the API refuses every create, edit and delete.
Managing the list
The grid has two columns, Name and Status, plus row controls. Search filters by name; Show inactive actions brings deactivated entries back into view. Both are mirrored into the URL, so a filtered view can be bookmarked.
Creating and editing
Click Add action. The dialog asks for exactly two things:
| Field | Required | Notes |
|---|---|---|
| Action name | Yes | The text operators will see, e.g. "Replaced belt" |
| Active | — | On by default |
Keep names specific enough to be useful in analysis, and general enough to be reused across incidents and equipment. The same action can appear in several places in one action tree and in several trees.
Deactivate, delete, activate
An active row offers Edit, Deactivate and Delete; an inactive row offers Edit and Activate.
| Control | What happens |
|---|---|
| Deactivate | The action stops being offered for new tree nodes but stays linked to existing action trees and downtime records. The list switches Show inactive actions on so you can still see the row you just deactivated. |
| Delete | Permanent, and cannot be undone |
| Activate | Puts a deactivated action back in circulation |
Prefer Deactivate for anything that has ever been used — deleting removes an entry that historical downtime records refer to.
Working with action trees
The two screens are used in sequence:
- Here — create the actions themselves.
- Action Trees — arrange them into a hierarchy. A tree node cannot be created without picking an action, so this list has to exist first.
- Admin → Equipment → OEE — bind the tree to equipment so operators see an Actions tab when they justify a stop.
Related
- Action Trees — the hierarchy built from these actions
- Reasons — the same idea for downtime causes
- Downtime Screen — where operators record actions