Guide
Adding video monitoring to a central station.
Most monitoring centres already receive video from a few professional systems. The demand now is for everything else: the consumer cameras, cloud doorbells and small recorders that clients already own and expect to be watched. This is how that is done without a different app per brand.
The problem
Every brand is its own island.
Three things make consumer and prosumer cameras hard to monitor professionally, and none of them is the camera.
Motion is not an alarm
A camera that reports every motion produces a flood. Without a schedule and event typing, the operator is looking at deliveries and cats.
No path to the platform
Consumer cameras notify a phone app. They do not know what a central station is, let alone how to reach its monitoring platform with a clip attached.
No way to see health
A flat battery or a lost connection shows up as silence. The client discovers the camera was dead when something happens.
The method
Six steps, in the order they matter.
- 01
Decide what an alarm is
Give every site an arming schedule in its own time zone. Inside the armed window an event is an alarm; outside it is recorded and kept. This alone removes most of what operators call false alarms, because most are real events at a time nobody cares about.
- 02
Deliver in the platform’s own format
Alarms should arrive in the platform your operators already use, typed (person, vehicle, intrusion, tamper, offline), with the snapshot and clip attached rather than linked. Nexus Connect delivers into SureView Immix this way today; support for further platforms is planned.
- 03
Bring the cameras the client already owns
Connect cloud cameras through their own accounts with the client’s credentials, professional cloud services through their interfaces, and local-network cameras through a Nexus NVR that connects outbound only. Nothing is installed on the client network and no port is opened.
- 04
Map, then test
Give the site its number and each camera its input number at the platform, and press “Test alarm”. It arrives on the right input, labelled as a test, before the first real event.
- 05
Give people the right reach
Create each client as its own organisation under yours. Your operators work one queue across all of them; your administrators reach only your subtree; each client decides whether you may enter its organisation for support. Two-factor is mandatory for anyone who can change things.
- 06
Watch the cameras, not just the events
Route offline and low-battery events to a health input on the platform and put the camera-health page on a screen. A silent camera becomes a ticket, not a surprise.
Then
What to measure.
Alarms per site per day
The overview shows alarm volume over the last hour to the last month, per organisation and per site. A site that spikes needs its schedule or its cameras looked at.
Operator load
Last-hour metrics per operator sit beside the alarm queue: claimed, resolved, escalated. Enough to staff a shift on.
Delivery
Every alarm delivery is recorded, and cameras whose alarms are not getting through are listed on the camera-health page. Delivery is a number, not an assumption.
Questions
What central stations ask first.
Do we need new hardware or a new platform?
No. Alarms are delivered into the monitoring platform you already run, and cameras are connected through their own accounts. A Nexus NVR is used only at sites whose cameras must stay on the local network.
How do consumer cameras reach us?
Through the camera’s own cloud service, connected with the client’s credentials. The platform reads the events and media from that service and delivers a typed alarm with the clip attached to your input. The client’s phone app keeps working as before.
What about false alarms?
Three controls: the arming schedule (nothing outside the window reaches an operator), event typing (person and vehicle arrive as distinct alarm types, so you can prioritise), and the clip attached to every alarm, so the operator verifies in one look.
Can operators see live video?
Yes, from the alarm, in the Nexus Connect dashboard, for cloud cameras whose service provides a stream and for cameras behind a Nexus NVR. Nexus Roam delivers events, snapshots and clips but does not stream live yet.
How is a client kept separate from another client?
Each client is its own organisation with its own people, sites and settings. Isolation is enforced inside the database, not only in the application, and a 152-case isolation test runs on every change.
What does it cost to start?
There is no public price list. Tell us how many sites and cameras and we will quote; a walkthrough on a test organisation comes first.
Terms used here are defined in the glossary; the delivery mechanics are on the how it connects page.
Now in early access.
We are onboarding a limited number of monitoring providers, integrators and multi-site operators ahead of general release. Join the waitlist, or sign in if you are already enrolled.