Water Plant Alarm Flood Triage
Self-hostTerminalTurn a burst of alarms into a briefing with likely causes, urgency and separate chattering signals.
by admin · listed 7 days ago
⚡ What System1 does here
About
An operator-support example for organizing a water plant's alarm flood before an agent reads it. In one prepared scenario, an intake power dip trips pumps and triggers downstream alarms while an unrelated chlorine-gas alarm also arrives. Jev classifies each alarm's possible role in the event and scores its urgency independently. Python applies explicit briefing rules: priority-1 alarms stay in the immediate-action section, repeated alarms are identified by counts, and other entries are ordered by urgency. A suspected downstream effect can therefore remain prominent when it is urgent. Stage: two prepared scenarios with author-supplied labels, not evidence of a live deployment. The README reports classification mistakes and urgent items occasionally falling just below the example score cutoff. The output changes what an agent reads first; it does not acknowledge, silence or modify the plant's alarm system. Run locally with Python and your own TypeSafe API key; model usage may cost extra. This listing was checked against the README and implementation, not independently run. Sources: https://github.com/smslavin/jev-industrial-samples/tree/main/04-alarm-triage https://github.com/smslavin/jev-industrial-samples/blob/main/04-alarm-triage/triage.py