Security Robot Onboarding: 14 Days to Go-Live

A security robot that is still not running autonomous night shifts after eight weeks of implementation is a failed project. Plant managers who accept this condition burn four-figure opportunity costs every month. They also hand the works council additional arguments against the technology. The following plan describes how security robot onboarding is completed in 14 calendar days, which decisions must be made on Day 0, and how success can be measured.

Security Robot Onboarding: What Gets Decided in 14 Days

The period from Day 0 (contract signature) to Day 14 (first autonomous night shift) is tightly scheduled. Delays originate not from the technology but from unresolved responsibilities inside the plant.

Three decision-makers are named by name on Day 0: the plant manager as the economically responsible party, the security manager for routes and escalation, and the IT lead for network and interfaces. Without these three names in the project plan, onboarding does not start.

Physical delivery occurs 48 hours from site clearance, not from contract signature. Site clearance means: audit completed, charging station mounted, network available. A plant manager who signs on Day 0 and has not ordered a power connection by Day 5 will push the go-live.

The minimum contract term is 24 months. Monthly OpEx sits between €3,200 and €3,800 per unit, depending on model and patrol intensity. Details on the three service tiers are in the three-tier pricing model.

The go-live success criterion is not delivery. It is two consecutive nights of autonomous patrol without human correction. Only then is the robot considered productive.

Site Audit: What Must Be Resolved Before Delivery

The audit takes place between Day 1 and Day 4. It determines whether a QR-1, QR-2, or QR-3 is deployed.

Topography first. Gradients above 15 percent disqualify the QR-1. Plant sites with ramps to loading docks or sloped terrain require the QR-2 for 24/7 outdoor patrol or the heavy QR-3 variant. Model selection follows the site walk, not a satellite map.

Surface conditions are mapped. Gravel areas, grating over cable ducts, rail crossings, and manhole covers with more than 3 cm height offset are marked as no-drive zones. A robot that slides across an icy grating costs more in eight weeks of repair than any Posten.

WLAN coverage at the perimeter is measured, not assumed. A minimum of 25 Mbit/s at every waypoint is mandatory. Where coverage is absent, the system switches to LTE fallback via SIM. Data contract costs run at roughly €35 per month per unit.

The charging station requires a 230 V connection within 30 meters of the return point, weather-protected and with RCD protection. For outdoor installation, plant maintenance should budget approximately €1,800 as a one-time installation cost when no cable run exists.

Lighting conditions determine sensor mode. Below 5 lux, the QR-2 switches automatically to thermal imaging. Plants with dark perimeter sections benefit from this. Investment in lighting is still not eliminated when Werkschutz personnel must assess the zone visually.

Defining Patrol Routes and No-Go Zones

Routes are walked physically with the security manager between Day 5 and Day 8. GPS waypoints are placed every 10 meters. A patrol route of 1.2 kilometers contains roughly 120 waypoints, each individually documented.

No-go zones are marked red in the map layer: industrial rail tracks, fuel stations and hazardous-goods stores, heavy-load zones with forklift traffic, open basins. These zones are blocked in software, not merely flagged as advisory.

Time windows follow shift structure. The day patrol runs at reduced intensity and avoids peak traffic periods. Standard night operation is 22:00 to 06:00. During these hours, plant-site patrol is the primary function of the system.

Trigger points for a full scan are defined with the security manager: gates, fence sections with a historically elevated intrusion rate, loading docks outside operating hours, critical machine rooms. At these points the robot stops and executes a 360-degree scan.

Patrol start points rotate randomly. An insider who knows the fixed 22:00 start at Gate 3 plans around the robot. Rotation eliminates that predictability.

Interfaces: Control Room, Werkschutz, Works Council

Alarm forwarding goes to the existing control room via API or SIA DC-09 protocol. A standalone solution with its own app is excluded because it creates a second user interface for Werkschutz personnel. Operating two parallel systems increases response latency and error rate.

Werkschutz personnel are not replaced. They are freed for escalation and physical intervention. Instead of three Posten on the night shift, two Posten plus the robot operate together. The third person is the saving, not the entire shift staff. The economic effects are compared in the article Wachschutz cost comparison.

The works council is a Day 1 topic, not a Day 12 topic. A data protection impact assessment under Article 35 GDPR is mandatory before commissioning. Reason: systematic video surveillance of the plant site. Plants with KRITIS relevance are additionally subject to the BSI-KritisV and must document their security technology.

Audio recording is deactivated as soon as break areas, smoking zones, or changing rooms fall within the patrol corridor. The loudspeaker function remains active; microphone recording does not. This point determines works council approval more often than any other detail.

Documentation obligation: video data is stored for 72 hours and then automatically deleted. Longer retention is permitted only for documented incidents and must be governed by the works agreement (Betriebsvereinbarung).

Escalation Matrix: Four Levels from Sensor to Patrol Car

Escalation runs through four defined levels. Each level has a trigger, an action, and a responsible party.

Level 1: The robot detects a person outside approved working hours. Action: documentation with timestamp and image, patrol continues. No alarm. This level covers roughly 80 percent of detections, typically own personnel with a legitimate reason.

Level 2: The person approaches a critical zone (gate, fence, transformer station). Action: acoustic address via loudspeaker using a predefined audio track. In 60 to 70 percent of cases the person then withdraws. The recording of the reaction continues.

Level 3: The person remains or continues moving toward the zone. Alarm to the control room with live image. Human verification within 30 seconds. The control-room operator decides, not the robot.

Level 4: The control room dispatches police or an intervention service. The robot never escalates to external parties on its own. This separation is mandatory under liability law and corresponds to the requirements for autonomous mobile service robots under EN ISO 13482.

All four levels are rehearsed in two real exercises with role players before go-live. Exercises take place between Day 11 and Day 13. Going live without rehearsal means experiencing the first false alarm at 03:00 with no coordinated response in place.

Economics: Why Onboarding Speed Is Measured in Hours, Not Weeks

The calculation starts with the reference point. A 24/7 security post costs between €15,000 and €25,000 per month depending on region and qualification level. The basis is the hourly rates under the Manteltarifvertrag and the headcount figures published by the BDSW as sector benchmarks.

The QR-2 does not replace that post. It reduces shift strength by one person per shift: typically the Streife function on the outdoor grounds. With three shifts per day, that equates to a saving of €18,000 to €22,000 per month against full staffing.

At a monthly OpEx of €3,200 to €3,800 per robot, the onboarding investment recovers in the third month of operation. The onboarding investment itself (installation, audit, configuration) is a one-time cost of €4,500 to €8,000.

Every day of delay costs roughly €500 to €800 in opportunity costs, measured against avoided personnel expenditure. Four weeks of delay amounts to €14,000 to €22,400 that the plant manager must explain to the CFO.

For tax purposes, the Robotics-as-a-Service model is fully deductible as OpEx. No CapEx arises, no capitalization, no five-year depreciation schedule. This structure is the decisive budget advantage over a purchase for most plant operations.

Go-Live and the 90-Day Review

The first 14 days after go-live run as shadow operation. The robot patrols; Werkschutz validates every alert. During this phase, false alarms are documented, not forwarded. Typical false-alarm sources: wildlife, plastic sheeting in wind, reflective puddles.

From Day 15, autonomous operation runs with a daily situation report to plant management. The report contains patrol kilometers, detections, escalated incidents, and availability as a percentage. Availability in normal operation is 96 to 98 percent, net of charging times and maintenance windows.

Day 30: First structured route adjustment. Waypoints with high false-alarm rates are relocated, or the sensor configuration in that section is recalibrated. Trigger points are prioritized on the basis of real incident data.

Day 90: Structured review with defined KPIs. Number of incidents by level, false-alarm rate per 100 patrol kilometers, availability, actual costs against plan. The review forms the basis for decisions on additional units, for example for perimeter protection in an industrial park across multiple sites.

Conformity with EN ISO 13482 and the EU Machinery Regulation 2023/1230 is confirmed in writing at go-live. The declaration of conformity is part of the delivery documentation and belongs in the plant manager's file, not the IT folder.

A plant that runs onboarding at the pace described here has a productive security robot on Day 15 and reliable KPI data for the CFO by Day 90. A plant that skips Day 1 with the works council faces a standstill by Day 60. For a site assessment and a binding onboarding plan: request a site audit.