Signals takes in the signals an operation produces, works out what they mean together, weighs that against the operator's rules, and acts with the permission the operator gives it.
Structured data such as schedules, transactions and work orders arrives with its meaning attached. Sensors and cameras need more work to read, and each reading carries a confidence, not a certainty. Outside data such as weather and event calendars comes in the same way.
A single signal is rarely the answer. A warm reading on a refrigerator at 2pm while it is being loaded is normal; the same reading at 11pm with the door open and nobody there is not. Signals holds the readings together and asks what the combination means.
Signals is configured to how the operation runs: its thresholds, its chain of command, its definition of a busy day. It says what is happening, what it is costing, and what to do next.
A recommendation goes to the person you named. Where you set a standing rule, Signals acts on it within the limits you gave it. Every action path has a manual override, and every outcome is recorded so the next call is better.
As much as possible, Signals runs on what you have. Where something needs adding, it is scoped with you first.
Processing runs in the cloud, on site, or split between them. The shape is chosen per deployment by cost, latency, connectivity and regulation, and hardware is added only where that shape calls for it.
Privacy is a setting the operator controls, decided with you and written into the deployment.
Counts and events, not people. No video is stored and no identity is tracked by default.
Available where the operator wants them and regulations allow. The operator collects consent and sets the scope, agreed in writing.
Yours to access and export, on your retention schedule. We do not train on it by default. What improves across deployments is the pipeline and the playbook, not another customer's records.
Signals proposes and a person you named approves, unless you set a standing rule. Each action is logged with who or what approved it.
SOC 2 Type I begins when an engagement requires it, followed by Type II over the standard observation window.
We complete your questionnaire, and HECVAT for higher education, during procurement.
Ask us directly.
