The path to every hydrant stays clear — and someone always knows when it is not.
A camera watches each fire hydrant through a virtual line. Anything left on that line raises an alert to the area in-charge, then escalates level by level — up to WhatsApp — until it is cleared, with a record of every obstruction and how long it stayed.
Pallets and bins drift into hydrant paths; the next safety walk is next week.
“A virtual line around each hydrant on the existing cameras; anything left on it alerts the area in-charge and escalates to WhatsApp until cleared.”
Drawn, not promised: the top row is a blocked hydrant found on the next safety round. The bottom row is the same trolley crossing a virtual line, the area in-charge alerted at once, and the time to clear on record.
Hover or tap a stage to see what is captured there.
Not a standalone tool — a product on the MOS platform, sharing one login, one set of people and roles, and one database with every other module. The lit layers are the ones this product uses; the signal path shows how data moves through them.
The honest map, drawn as one thread. Filled nodes are in the product today; outlined nodes are other MOS modules on the same platform; dotted nodes are roadmap and never represented as available until built. Hover a node.
Each card ends with the thing itself as it appears in MOS — not a description of it.
Step through it or let it play. Each step: who does it, on what, what is captured, and the check that guards it.
A virtual line is drawn around each hydrant on its camera view.
Anything left on the line beyond the set time is detected; a person walking past is not.
The area in-charge gets the picture at once.
If not acknowledged, it escalates level by level, up to WhatsApp.
The obstruction is cleared; the time to clear is recorded.
Zone-wise reports: events, time to clear, repeat spots.
| Your ERP / Tally typically gives | Fire Safety adds |
|---|---|
| A safety walk once a week | Every hydrant watched all the time |
| A blocked path found during the fire | An alert within seconds, with the picture |
| A verbal reminder | Escalation up to WhatsApp until cleared |
| No record | Every obstruction with time to clear |
Existing IP cameras that see the hydrant and its path
A GPU machine on the plant network — shared with Gangway & PPE Watch
WhatsApp for the final level
MOS Edge in the plant
What it connects to, where it runs and what it gives you — the short version your IT and your plant head both want.
Virtual lines, obstruction detection, escalation to WhatsApp, time to clear, zone reports.
Gangway & PPE Watch on the same cameras and GPU.
Camera coverage of each hydrant is confirmed at site.
Fire-panel integration — not represented as available.
Capabilities depend on the plant's process and what is connected at site. Nothing on this page is represented as available until it is built and running.
The first alert, with the snapshot
Open obstructions and escalations
Zones that keep blocking hydrants
A record of every obstruction
A view from a camera the plant already has, or a new one.
A GPU machine on the plant network.
The people for each level, and WhatsApp numbers.
A virtual line around each hydrant on its camera.
Who is told first, next and last, and after how long.
Reports by zone and time to clear.
No. Only something left on the line for longer than the set time raises an alert.
Yes, where the camera sees the hydrant and its path.
People in vehicle zones and missing PPE — flagged as it happens.
See the module →Every machine, live — and the real reason it stopped.
See the module →Every unit scanned at every station. Nothing skips a stage.
See the module →Tell us about your plant and what you want to see. We visit, connect one machine or station, and you watch your own data in MOS before anything is quoted.