The site's notebook — written by everyone, kept for ever.
The most valuable knowledge about a facility lives in people's heads and paper logbooks, and leaves when they do. Vigil keeps it: every event the platform detects and every note a person writes becomes part of one shared memory, attached to the asset it's about.
Many hands write it. Everyone can read it.
The platform writes what it sees; people write what they know. Both land in the same place, so nothing depends on who happened to be on shift.
The platform writes
Excursions from a normal band, slow drifts, broken couplings, site-wide events, forecasts that came true — each one recorded with its evidence.
People write
"Replaced the seal on pump 3." "Valve sticks when it's below freezing." A note or photo from the phone, attached to the asset, in seconds.
Actions write themselves
Every command a node applies, every programme started, every rule changed — recorded with the person or reflex that asked for it.
Memories are periods, not just moments.
A drift lasts days; a repair takes an afternoon; a programme runs for a week. The memory timeline shows each as a span, so you can see what overlapped — and what changed after the fix.
- Who made it — the platform (and which detector) or a person — and when
- The evidence behind it, one click away
- Filter by site, asset, kind, or people only
A memory that works for you.
The point of remembering is using it. Vigil's memory isn't an archive you search once a year — it feeds everything else.
The next shift
Opens the phone and sees what happened overnight and what was done about it, in order of what needs them.
Reports
Each report reads the last one and the memories since, so it says what changed — not just what the numbers are.
Argus
Ask "why does this pump trip in winter?" and Argus reads the notes people left as well as the data.
Forecasts
Data marked bad by a memory stays out of the history the forecasts learn from.
The phone is the field notebook.
What needs you
A ranked feed across every site — swipe to acknowledge or snooze.
Notes & photos
Taken beside the machine, attached to it, read by everyone after you.
Scan a label
Every node carries a QR label — scan it for its history, or to commission it.
Ask in words
"How is the dam tonight?" — a briefing with every fact cited, on the phone.
A site's story, in five answers.
How is it now? What happened? What has Vigil learned? What is watching it? What should happen next? A briefing answers all five from the site's records and its memory — written as you watch, every sentence citing its evidence. It's the handover every manager wishes they had.
Let's make sense of your site.
Tell us about a site — a plant, a dam, a campus, a cold store. We'll show you the platform on demo data like yours and plan a pilot with nodes on your equipment.