Safety¶
The Safety application is where your teams report safety incidents (accidents and near misses) and safety inspection findings, and follow each one until it is closed. Open it from the application launcher: Manufacturing → Safety.
The page has two tabs, Incident and Inspection. Both work the same way: a summary table at the top, a button to write a new entry, and — for users allowed to see logs — a list of every entry, where you can update one.
The summary table¶
Each tab opens on a table that counts the entries of the last 6 months, one row per period.
Incident tab
| Column group | Columns |
|---|---|
| Severity | High, Medium, Low, Near miss — how many incidents of each severity |
| Status | Reported (all incidents), Closed, Open, and % of closures (closed ÷ reported) |
| Accident | Accident without loss, Accident with loss |
Inspection tab
| Column group | Columns |
|---|---|
| Severity | High, Medium, Low — how many findings of each severity |
| Status | Findings (all findings), Open, Closed, and % of compliance (closed ÷ findings) |
An entry you have just written appears in the table straight away.
Filters¶
Click Filters to change what the table counts, then Apply:
| Filter | What it does |
|---|---|
| Time period | One row per Day, Week, Month (the default) or Quarter |
| Locations | Count only the entries of the locations you pick. Leave it empty for all locations |
| Inspection type | (Inspection tab only) Process related or maintenance related findings |
The number on the Filters button shows how many filters are in use.
Week labels
In the Week view, each week is labelled by a date at its start.
Writing an incident¶
Click Write incident and fill in:
| Field | Notes |
|---|---|
| Accident, Accident with loss, Closed | Tick the ones that apply |
| Incident description | Required; up to 300 characters |
| Location | Required — where it happened. Locations are set up under Settings → Derived & Data Units → Manufacturing → Locations |
| Date | Required; today by default. A future date cannot be picked |
| Time | Optional. Left empty, the incident is recorded at the start of that day |
| Employee ID | Required; up to 25 characters |
| Severity | High (default), Medium, Low or Near miss |
| Corrective action | Required; up to 300 characters |
Click Create.
Writing an inspection log¶
Click Write inspection log and fill in:
| Field | Notes |
|---|---|
| Inspector ID | Required; up to 25 characters |
| Location | Required |
| Inspection date | Required; today by default |
| Follow-up date | Optional |
| Findings | Required; up to 300 characters |
| Severity | High (default), Medium or Low |
| Inspection type | Process related finding (default) or maintenance related finding |
| Status | Open (default) or Closed |
| Actions required | Required; up to 300 characters |
Click Create.
Checking and updating the logs¶
Users with the logs access right see a Check logs button on each tab. It opens every entry of a date range:
- Incidents: pick a start and end date and time (the last 30 days up to 3 days ahead by default) and click Fetch.
- Inspections: pick a from and to date (same default) and click Fetch. The range is on the inspection date.
The table lists each entry with its details and who logged it. To update one, open the ⋮ menu on its row and choose Edit. Once an entry is written, only its outcome can change:
| Tab | What you can change |
|---|---|
| Incident | Accident with loss, Closed, Corrective action |
| Inspection | Status, Actions required |
The description, location, date, severity and the other details stay as they were written. If one of them is wrong, write a new entry.
Closing the loop
The % of closures and % of compliance columns only rise when entries are marked Closed. Make it a habit to update an incident or inspection from Check logs once its corrective action is done.