Glossary
The terms, defined once.
The vocabulary of video monitoring differs between markets and between vendors. These are the terms this site uses, what they mean here, and the other names the same thing goes by.
A to Z
Definitions.
Central station
Also: central monitoring station, monitoring centre, CMS
- The staffed facility that receives alarms from many customer sites and acts on them: verifying, dispatching, calling keyholders, logging the outcome. “Central station” is the usual term in North America; “monitoring centre” and “alarm receiving centre” are the usual terms in the UK and Europe. A monitoring centre may be wholesale (serving alarm dealers who own the customer relationship) or direct. Nexus Connect models a monitoring centre as a partner organisation with its client organisations beneath it.
Alarm receiving centre (ARC)
Also: remote video response centre (RVRC), security operations centre (SOC)
- The UK and European term for a central station. An RVRC is an ARC that handles video: operators look at footage, not only signals. A SOC is the enterprise equivalent, run for one organisation rather than for many customers. Nexus Connect treats all three the same way: a partner organisation whose operators work one alarm queue across every client site.
Video alarm verification
Also: video verification, visual verification, verified alarm
- Confirming an alarm with video before anyone is dispatched. Instead of a signal that says only “zone 3 tripped”, the operator receives a clip or snapshot from the camera that saw the event and decides whether it is a person at the fence or a fox. Verified alarms reduce false dispatches and, in many jurisdictions, get a higher police response priority. Nexus Connect delivers every alarm with the clip and a snapshot attached, so verification is the default rather than a second step.
Event-based video monitoring
Also: event-driven monitoring
- Monitoring in which operators see video only when something happens, rather than watching live feeds continuously. Cameras or analytics detect an event, the platform decides whether it counts as an alarm, and the operator receives the clip. It scales to hundreds of sites per operator because attention goes only where there is an event. The alternative, continuous live monitoring, is sometimes called remote guarding or virtual guarding.
Alarm queue
- The single ordered list of open alarms an operator team works from, across every site they are responsible for. In Nexus Connect an operator claims an alarm, opens the clip and live view from the same screen, and resolves or escalates it. Every step is recorded in the audit trail, and last-hour metrics per operator sit beside the queue for the supervisor.
Clip and snapshot
Also: alarm video, pre- and post-alarm clip
- The media attached to an alarm. The snapshot is a single JPEG frame the operator sees immediately; the clip is the short MP4 recording around the event. Nexus Connect attaches both to the alarm itself, so the monitoring platform receives the media rather than a link that could expire or point at a site it cannot reach.
Arming schedule
Also: armed window, schedule-based arming
- The times at which a site’s events should be treated as alarms. A site is armed during its windows, set per day of the week in the site’s own time zone, and disarmed outside them. An event inside a window becomes an alarm and reaches the operator; outside it is recorded and kept but raises nothing. Schedules are the first and cheapest control against false alarms, because most “false” alarms are real events at a time nobody cares about.
Device health
Also: camera health, camera health monitoring
- Whether each camera is reachable, powered and delivering. Nexus Connect tracks connectivity, last-seen time, battery and signal where the camera reports them, and whether its alarms are reaching the monitoring platform, then groups cameras by condition on one page. Offline and low-battery conditions are raised as alarms of their own, once per outage, so a silent camera is a visible problem rather than an absence of events.
Partner organisation and client organisation
Also: multi-tenant
- In Nexus Connect every customer is an organisation. A monitoring centre is a partner organisation, and each of its customers is a client organisation beneath it, with its own sites, people, roles and settings. Partner administrators reach only their own subtree, and a client decides whether the partner may enter its organisation for support. This is what “multi-tenant” means here: many separate organisations in one platform, isolated from each other inside the database, not many tenants in one building.
Site
Also: client site, premises
- One place with cameras: a shop, a yard, a residence, a floor. A site groups its devices, its contacts, its arming schedule and its identifiers at the monitoring platform. Alarms are raised per site, so a client with three locations has three sites under one organisation, each with its own schedule and its own routing.
Outbound-only link
Also: no inbound ports, NAT-friendly
- A connection that the device on site opens towards the cloud, and never the other way round. Nothing on the customer’s network listens for incoming traffic, so no port is forwarded, no firewall rule is changed and no VPN is needed; the link works behind NAT and over LTE. The Nexus NVR connects this way. Remote configuration and video export use an audited tunnel that the appliance itself opens for the job and closes after it.
Store-and-forward
Also: catch-up, outbox
- Keeping events locally while the cloud link is down and delivering them when it returns, in order, so an outage costs a delay rather than a gap in the record. The Nexus NVR queues events in an outbox on the appliance and catches up when its link is back.
Live view on demand
- Opening a camera’s live stream at the moment an operator needs it, from the alarm, rather than streaming everything all the time. For cloud cameras the stream comes from the camera’s service where it provides one; for cameras behind a Nexus NVR the appliance publishes the stream over its outbound link when asked. Nexus Roam does not stream live yet.
Zero-touch enrolment
Also: pending pool, claiming
- Bringing a new device into the platform without configuring it on site. A Nexus NVR or Nexus Roam powers on, dials out, and appears in a pending pool in the cloud; an operator claims it into the right client organisation and site. The installer’s job is power and, for the NVR, a network cable.
Site number and input number
Also: S-number, A-number, alarm number
- The identifiers a monitoring platform uses to route an alarm: a number for the site, and a number for the input (camera or zone) within it. Nexus Connect stores the site’s number on the site and each camera’s input number on its mapping, and can give a site an extra input for device-health events, so alarms and health arrive at the right place with no work at the receiving end.
Audit trail
Also: tamper-evident log, hash chain
- The permanent record of who did what and when: sign-ins, role changes, alarm actions, support entries, configuration changes. In Nexus Connect it is append-only and hash-chained, meaning each entry carries a fingerprint of the one before it, so an altered or deleted entry breaks the chain and shows. The chain can be verified per event from the reports view.
How these fit together for a monitoring centre is on the guide to adding video monitoring.