📝 Work Safety
The core KPI "Occupational Safety" in ValueStreamer helps you systematically record safety-related incidents such as accidents and near misses. The integrated safety cross provides a quick visual assessment and makes it easier to derive actions directly from the KPI view.
⚠️ Note: The Occupational Safety function will undergo functional and visual updates in the coming months. Please check the release notes regularly to stay up to date.
🔍 Contents
-
Why this topic matters
-
Prerequisites
-
Step-by-step: Using the Occupational Safety KPI
1️⃣ Understanding the detail view
2️⃣ Entering KPI values
3️⃣ Reporting a deviation
4️⃣ Defining non-working days -
Tips & Best Practices
-
FAQ
📌 Why This Topic Matters
The Occupational Safety KPI provides transparency on safety-related incidents and helps teams identify risks early and implement preventive measures.
ℹ️ Note: This KPI is predefined in the system, available in multiple languages, and can be used in all safety-relevant teams.
✅ Prerequisites
-
🔐 Permission: Team membership in the respective team to record values
-
📘 Knowledge of internal company safety processes
🛠️ Step-by-Step: Using the Occupational Safety KPI
1️⃣ Understanding the Detail View
In the detail view, you’ll find:
-
📅 Month navigator
-
🔲 Safety cross (current month)
-
🧮 Counter “Accident-free since (days)”
Color logic of the safety cross:
Color | Meaning |
---|---|
🟥 Red | Accident reported |
🟨 Yellow | Near miss |
🟩 Green | Accident-free |
⬜ Gray | Non-working day |
📸 Screenshot: Safety cross
2️⃣ Entering KPI Values
-
Click on the desired date in the safety cross.
-
Select the status:
-
🟩 Green = Accident-free
-
🟨 Yellow = Near miss (reason required)
-
🟥 Red = Accident (reason required)
-
⬜ Gray = Non-working day
-
ℹ️ Note: Yellow and red statuses cannot be saved without a reason.
-
Save the entry.
📸 Screenshot: Input form with reason field activated
3️⃣ Reporting a Deviation
-
After entering a reason, the “Deviation” button appears.
-
Click it – the reason will automatically be used as the deviation title.
-
Confirm creation.
✨ Tip: Use this feature before the shop floor meeting for quick incident documentation.
4️⃣ Defining Non-Working Days
-
Open the KPI editor in system administration.
-
In the Occupational Safety tab, define which weekdays are non-working by default (e.g., Saturday, Sunday).
ℹ️ Note: Changes only apply to future calendar days.
✨ Tips & Best Practices
-
Use the KPI as an early indicator for necessary safety measures.
-
⚠️ Ensure all incidents are recorded promptly and completely.
-
💡 Link the KPI to the PDCA cycle to systematically eliminate safety issues.
❓ FAQ
Can I enter past accidents retroactively?
→ Yes, any calendar day in the safety cross can be edited retrospectively.
What happens if I don’t provide a reason?
→ Yellow or red statuses cannot be saved without a reason.
Who can change non-working days?
→ Only system administrators with access to the KPI editor.