ONVIF Security Robots: Control Room Without Special Cases

Anyone running a control room with Genetec, Milestone or Bosch has no appetite for a second operator window. An autonomous patrol robot has to plug into the same VMS surface as a fixed camera. That is exactly what ONVIF exists for. The article below sets out what the standard delivers, where it ends and how quickly a QR-2 or QR-3 goes into production.

ONVIF Security Robots: Why the Standard Decides the Integration

ONVIF has been the open language between camera, VMS and control room since 2008. [Citation required: insert external link to ONVIF founding history] More than 30,000 device profiles are certified today. [Citation required: insert external link to ONVIF product database] Anyone ignoring this standard is building isolated solutions.

A security robot without ONVIF conformance forces two consequences in the control room. First: a parallel operator interface alongside the VMS. Second: double shifts for the operator, because alarms from two systems have to be acknowledged. Both increase response time. On top of that comes training overhead with every staff change.

The Quarero robots QR-1, QR-2 and QR-3 implement ONVIF Profile S, T and M at every sensor layer. QR-1 covers the indoor area, QR-2 the outdoor perimeter with thermal sensor, QR-3 KRITIS facilities with LiDAR. The result: the robot appears in the VMS as a moving camera with telemetry overlay. GPS position, battery level and patrol status sit as metadata on the same stream.

Integration time drops from a typical six weeks (as required by proprietary robotics stacks) to 48 hours. One engineer day plus acceptance test, no more.

Next step: technical details on the QR-2 outdoor robot with thermal sensor.

Profiles S, T and M: What the Standard Actually Delivers

The three profiles together cover everything a control room needs from a mobile sensor.

Profile S governs live streaming via RTSP, PTZ commands and the audio backchannel. An operator activates the robot like a PTZ dome, pans the camera and addresses people directly. No special interface, no extra headset.

Profile T extends with H.265 codec, motion alarming and bidirectional metadata. Bandwidth costs drop by roughly 40 percent against H.264. [Citation required: insert external link to ONVIF or codec benchmark] Motion alarms are published directly from the robot as event topics, the VMS subscribes to them.

Profile M covers analytics metadata, including object classification and geo-coordinates. This is where the robotics specifics become visible. QR-2 sends thermal detections as Profile M events with GPS position, confidence value and classifier label (person, vehicle, animal). QR-3 additionally delivers LiDAR-based drone detections as structured metadata, including flight altitude and vector.

The control room prioritises these alarms by the same rules that apply to fixed cameras. A person in a restricted area at 02:14 generates an identical pop-up in the VMS, regardless of whether the detection came from a mast camera or a QR-3.

Details on LiDAR sensing: QR-3 for KRITIS with LiDAR and drone detection.

Compatible VMS and PSIM Platforms in the DACH Market

The four leading VMS platforms in the DACH region integrate Quarero robots without adaptation.

Genetec Security Center accepts the robot as an ONVIF camera profile device. Add, enter IP address, credentials, done. The stream appears in the Monitoring Desktop, events run into the standard Action Manager.

Milestone XProtect detects the robot as a hardware device with dynamic geo-position. The XProtect Smart Map displays the robot as a moving icon, a click leads directly to the live stream. Available from XProtect Corporate 2022 R2.

Bosch BVMS from version 11.0 and Axxon Next from 4.6 use Profile T events for rule chains. A drone detection from the QR-3 there automatically triggers a predefined sequence: switch to operator desk 2, alarm to duty supervisor, activate recording.

For PSIM systems such as Advancis WinGuard, the robot runs as a georeferenced sensor layer. WinGuard visualises the patrol route on the site map and correlates robot events with access control and fire alarm systems.

Important: no proprietary middleware is required. No licence fees for additional connectors. The ONVIF driver is included in every standard VMS licence listed.

Event Architecture: From Sensor to Control Room Action

The chain from detection to operator action runs in four defined steps.

1. Detection on the robot generates an ONVIF event with topic (example: tns1:RuleEngine/CellMotionDetector/Motion), timestamp, geo-coordinates and payload (classifier, confidence, bounding box).
2. The event triggers a predefined workflow rule in the VMS. This includes a pop-up on the operator monitor, automatic activation of the live stream, activation of the audio address and a parallel SMS to the duty manager.
3. The operator acknowledges in the same mask used for fixed cameras. Double training is unnecessary.
4. The audit trail is kept in the VMS: who acknowledged which alarm when, which action followed, when the incident was closed.

This audit trail meets the logging obligations under BSI Grundschutz module OPS.1.1.5 (logging). For KRITIS facilities, the chain additionally fulfils the reporting obligations under the KRITIS Umbrella Act draft (KRITIS-Dachgesetz), which defines logging and reporting obligations for operators of critical facilities. Which facilities fall under it is governed by the KritisV.

Next step: review NIS-2 obligations for operators in detail.

Network, Cybersecurity and NIS-2 Conformance

A robot on the network is an OT asset. It has to meet the same requirements as any PLC or camera.

ONVIF communication at Quarero runs over TLS 1.3 with certificate-based authentication. Plaintext streams are disabled in the factory configuration. Anyone wanting Profile S without encryption has to enable it explicitly, which we do not recommend for KRITIS customers.

Quarero robots support IEEE 802.1X for port authentication in the OT network. This allows the robot to be authenticated via RADIUS against Active Directory. An open switch port as an entry vector is eliminated. Segmentation via VLAN cleanly separates robot telemetry from the office network. Recommendation: dedicated VLAN for robotics, separate one for VMS, with a firewall rule containing an explicit ONVIF whitelist between them.

The NIS-2 Directive requires an initial report of security incidents within 24 hours (Art. 23(4)(a) NIS-2 Directive). Both (asset inventory and incident reporting) can be derived from the VMS, provided the robot is managed there as a regular device. That is precisely the advantage of the ONVIF architecture over proprietary stacks.

Penetration tests according to BSI specifications are part of onboarding for every RaaS contract. We deliver the report in a form that a NIS-2 auditor will accept.

Cost: ONVIF Robots in the TCO Comparison

The cost calculation is plain. A human 24/7 guard post costs €15,000 to €25,000 per month gross in the DACH region [BDSW industry data]. This covers shift factor 4.2, social charges, collective agreement supplements and holiday cover.

A QR-2 as an ONVIF sensor in the control room costs €3,500 per month under the RaaS model. Included: hardware, maintenance, software updates, cyber patches, insurance and replacement device in case of failure.

No additional investment in connectors, because the ONVIF standard is already included in the VMS licence. Integration effort comes to a maximum of two person-days per site, calculated with an experienced VMS administrator.

Minimum contract term: 24 months. Quarterly notice thereafter. No vendor lock-in beyond the standard. Follow-up devices from other manufacturers can also be integrated if ONVIF-conformant.

Detailed comparison: Guard service cost comparison and the Robotics-as-a-Service model.

Integration Roadmap in Five Steps

The order is fixed, the duration depends on the existing VMS.

Step 1: Inventory. Which VMS version is running, which ONVIF profiles are licensed, which switch will carry the future robot VLAN. Duration: half a day remote.

Step 2: Define network segment. Set VLAN ID, enable firewall rules (ports 80, 443, 554, 3702 for WS-Discovery, plus event ports). Configure 802.1X profile in RADIUS. Duration: one day.

Step 3: Add robot to VMS. Open device wizard, enter IP, credentials, select profile. Test stream and events. Done in around 20 minutes on Genetec and Milestone.

Step 4: Define workflow rules. Which event triggers which action, which escalation chain applies for drone alarms, who is notified when. Coordination with control room manager and duty supervisor. Duration: half a day.

Step 5: Acceptance test. Simulated incidents (person in restricted area, drone approach, fire hotspot), stopwatch from detection to acknowledgement. Handover to regular operation. Duration: one day.

Total duration from contract signature: 48 hours with prepared infrastructure, up to five working days with complex network topology.

Practical example with a hybrid setup: Hybrid TCO at an industrial park.

Limits of the Standard and Quarero's Proprietary Extensions

ONVIF is a camera language. Anyone applying the standard to robotics hits clear limits.

ONVIF does not cover charging station management and no route planning. A robot has to know when it goes to the docking station, which route it takes and how it avoids obstacles. The Quarero API via REST and MQTT exists for that, separate from the ONVIF stack.

Complex multi-robot coordination runs over a separate orchestration layer. If two QR-2s and one QR-3 patrol the same area, logic decides which robot drives to which alarm. ONVIF cannot do that, the Quarero Fleet Manager can.

Drone defence sequences require proprietary command chains beyond Profile T. LiDAR tracking, classification, escalation to authorities: this runs over dedicated APIs, because the standard defines no topics here.

Data export for forensic evaluation additionally follows BSI specifications for evidence preservation (hash values, timestamp signature, complete chain of custody). The ONVIF recording service is not sufficient here.

Safety requirements for the platform itself are governed by EN ISO 13482 for personal care and service robots, applicable to autonomous patrol platforms.

Important: standard and extension are cleanly separated. Anyone wanting to use only the ONVIF layer can do so. Anyone using the full Quarero API retains the VMS integration in parallel. The ONVIF layer remains verifiable in any conformance test.

---

Anyone wanting to check whether their own VMS will accept a QR-2 or QR-3 in 48 hours should start with an inventory. We send an engineer to your control room for two days, document the connection and deliver the test report. Request a pilot for your site.