Monitoring is where it starts, not where it stops.
Sentinel is a managed platform, not a dashboard you have to run. It watches the site, then runs the work that follows: assets, tickets, technician workload, preventive schedules and controlled change. Delta provisions the hardware, secures the connection, operates the cloud and watches the fleet.
- DELIVERY
- Managed, end to end
- EDGE
- Offline-first
- TENANCY
- Multi-tenant, SSO
- DETECTORS
- 35
- OPEN APIS
- 110+
- TIMEZONE
- Africa/Johannesburg
Capability register
13 SUBSYSTEMS / ALL SHIPPED| SUBSYSTEM | WHAT IT DOES | STATE |
|---|---|---|
| Live SCADA | Every node polled continuously, whether that is a generator, a water meter, a cold-room probe, a PLC or a network link. Values, units and freshness are shown together. | |
| Offline-first edge | Local buffering with sequencing and persist-acknowledgements. Load-sharing logic keeps running through an outage and replays every reading in order on recovery. | |
| Alarm engine | Roughly 35 always-on detectors with escalation paths. Each alarm carries what it means, what it does not mean, the measurement behind it, and the action to take. | |
| Supervisory control | Rule-based automation on alarm, status and schedule triggers. Guarded commands, role-based control, human approval gates, every action in the audit log. | |
| Zero-touch provisioning | A gateway goes from blank to online in minutes. Secure automatic enrolment, staged over-the-air updates, one-click rollback. | |
| Protocol layer | One normalised ingest pipeline, vendor-agnostic, with auto-discovery of telemetry variables. Sub-devices create themselves as they appear on the bus. | |
| Dashboards & reports | Drag-and-drop dashboards, branded PDF and Excel reports on a schedule, notifications that reach people rather than an inbox nobody reads. | |
| Asset register | Every device, its site, its parent, its service history and its documents in one register. Telemetry and paperwork sit on the same record, so an asset's condition and its history are never two systems apart. | |
| Tickets & workload | An alarm raises a ticket, a ticket is assigned to a technician with a due date, and the workload view shows who is loaded and what is overdue. Field techs close jobs from the mobile app, offline if the site has no signal. | |
| Preventive maintenance | Schedules run on runtime hours, calendar dates or measured condition, not on someone remembering. Drift in vibration, temperature or load raises the job before the failure, which is the whole point. | |
| Change control | Configuration, setpoints, firmware and rules move through a request, an approval and a staged rollout, with rollback. Nothing changes on a live site without a name against it. | |
| Evidence & compliance | Alarm to work order to signed dossier, one chain of custody. Compliance packs come out of the same data the operators watch, so the report matches the site. | |
| Multi-tenancy | Per-tenant branding, role-based access scoped per site, single sign-on, and a documented open API for whatever you already run. |
The gateway is the site's source of truth.
The cloud is where you look at the data. The edge is where the data is decided. When power or connectivity drops, the gateway keeps polling, keeps enforcing rules, and replays the gap in order once the link returns, so the record has no holes to explain later.
Devices polled on the bus; variables discovered automatically.
Rules and detectors run locally, with or without a network.
Guarded commands fire; humans are paged only when it matters.
Buffered readings replay in order into the audit and report trail.
See Sentinel against your own site's assets.
Bring an asset list and a recent bill. We will show what would be instrumented, what would be automated first, and what the reporting would look like.