Use Case, Factory Floor Alarm Prioritization and Visibility Across Multiple Machines

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Yes.

In a plastic manufacturing factory (injection molding and blow molding), machine alarms are currently local only. When a fault occurs, the alarm sounds at the machine, but no one outside the immediate area is aware.
and when a production fault happen there's no alarm for that's and can't be figure out until some one can periodically check it locally.

Works must shout or call technicians. Technicians are responsible for multiple machines and have no clear way to prioritize issues. They often respond to the first or loudest request rather than the most critical fault.

This leads to:

• Delayed response to critical failures
• Inefficient use of technician time
• Increased machine downtime
• Lack of visibility for the factory manager

Describe the use case

Today:

1. A machine faults and triggers a local alarm.
2. The operator notices and calls or shouts for help.
3. The technician receives multiple requests from different machines.
4. The technician chooses where to go based on urgency perception, not actual severity.
5. The factory manager is unaware until informed manually.

With Krake:

1. A machine fault triggers a Krake alarm device.
2. The alarm is transmitted via Wi-Fi/MQTT to relevant personnel.
3. The alarm includes severity level (1–5).
4. The technician receives prioritized alerts and selects the highest severity.
5. The technician acknowledges the alarm (e.g., via mute or acknowledgment action).
6. The operator sees a visual/audible indication that help is on the way.
7. The manager has real-time visibility of all active alarms and their severity.
8. Alarm events are logged for later review.

• Factory Manager: Needs real-time overview and historical alarm data.
• Technician: Needs prioritized alerts and ability to acknowledge response.
• Machine Operator: Needs confirmation that the alarm has been received and help is coming.

Value and impact

• Reduced machine downtime through faster and better-prioritized responses
• Improved decision-making for technicians under multiple simultaneous faults
• Reduced stress and noise on the factory floor (no shouting/calling)
• Increased transparency for factory management
• Better post-shift analysis through alarm history and response tracking
• Safer and more organized operation

No files, tests, or implementation entry points are named. Start by reviewing the existing device alarm, Wi-Fi, and MQTT architecture, then clarify the alert, acknowledgment, severity, visibility, and history requirements. Done should include an agreed design and verified behavior for prioritized multi-machine alarms.