Safety Standards¶
Define the safety steps technicians must acknowledge, the repair-request types they can file, and the shutdown reasons they can choose from. All three feed the safety / incident reporting pipeline.
Required role
Mapper or Admin. Supervisor and Viewer have read-only access.
Overview¶
Safety Standards is the umbrella for three closely-related configuration items:
- Safety Procedures — the acknowledgement checklists that gate certain tasks.
- Repair Requests — the dropdown of failure categories technicians pick when filing a repair request.
- Shutdown Reasons — the dropdown of causes technicians pick when reporting a shutdown.
Together they shape how safety and incidents are captured across your plant.
This menu item expands into three sub-menus — one page each.
Submenu¶
- Safety Procedures — acknowledgement-gated procedures attached to tasks.
- Repair Request Types — the failure-category catalogue.
- Shutdown Reasons — the shutdown-cause catalogue.
How the three connect¶
- A Safety Procedure may mention specific failure modes; those failure modes should be reflected in the Repair Request Types catalogue so technicians can file them with the right category.
- Shutdown Reasons split planned / unplanned / force-majeure for OEE attribution; planned maintenance shutdowns can reference the safety procedure that gates them.
- Together they drive the Shutdown Report, Repair Request Report, and any audit packs you generate.
Review cadence¶
These catalogues drift. Review annually (or after any significant incident):
- Any failure type technicians type into the "description" field repeatedly but isn't in the dropdown → promote to a formal category.
- Any safety procedure with tap-through-in-5-seconds acknowledgement patterns → rewrite (steps too vague, or too many).
- Any shutdown reason rarely used → consider merging or deactivating.
Things to watch for¶
These are company-wide
All three catalogues are scoped to the company, not per-user. A change to Safety Procedures affects every task with that procedure attached across the whole tenant.
Co-own with your safety officer
Mapper owns the tool; the safety officer owns the content. Write and review together.
Related topics¶
- Safety Procedures
- Repair Request Types
- Shutdown Reasons
- Repair requests (mobile) — the technician's side.
- Reporting a shutdown (mobile)
- Reports — downstream analytics.
- Mapper handbook