Industrial Site Before and After Robotics: A Case Study on Shift Gaps and Incident Load

The case study presented here follows the logic of Chapter 19.1 of KRITIS: Die verborgene Macht Europas by Dr. Raphael Nagel and Marcus Köhnlein. It compares a mid-sized European industrial estate in two distinct operating states. The first state relies exclusively on human patrols, fixed cameras and a conventional control room. The second state integrates mobile security robotics operated by Quarero Robotics under a Robot-as-a-Service model. The comparison is not intended as a marketing exercise but as a structural observation of how shift gaps, documentation quality and incident load shift when a site moves from static coverage toward a resilience architecture. Figures are kept within the plausible range of typical DACH operating conditions and reflect the order of magnitude that operators of KRITIS-adjacent industrial sites regularly report when they begin to measure their own performance rather than rely on assumed availability.

The Site Before Integration: A Familiar European Pattern

The site under review is a logistics and light-manufacturing estate of roughly 140,000 square metres, with three production halls, an outdoor storage yard, two gate areas and approximately 2,300 metres of perimeter fence. It operates on a standard three-shift rhythm and is classified as a relevant supplier to two KRITIS operators in the energy and food sectors. Security was provided by a contracted guard service with two officers per shift, supported by 48 fixed cameras and a local control room staffed during weekdays.

On paper the arrangement looked complete. In practice, the operational reality matched a pattern that European security managers will recognise. Each scheduled patrol took between 55 and 70 minutes. Between two consecutive patrols of the same sector, a gap of up to 90 minutes was structurally unavoidable. During breaks, shift handovers and weather-related slowdowns, the effective gap widened further. Fixed cameras covered fixed angles, which meant that roughly 18 percent of the outdoor area was not continuously observable, particularly along the rear fence line and between container rows.

Documentation relied on handwritten tour books and radio logs. Incidents were described in short free-text entries, often written after the end of the shift. Escalation to the control room followed voice communication, and from there to the client and, where relevant, to public authorities. In the twelve months preceding the review, the site recorded 214 security-relevant events, from trespassing and vehicle intrusion to minor vandalism and two confirmed theft attempts on copper cabling.

Shift Gaps, Ambiguous Records and Slow Escalation

An internal analysis commissioned by the operator produced three findings that are consistent with the structural observations in Chapter 19 of the source book. First, patrol density was uneven. Sectors close to the main gate received on average 11 patrol passes per 24 hours, while the rear yard and the technical compound received between 4 and 6 passes. This imbalance was not the result of negligence but of the arithmetic of two officers covering a large area on foot or by vehicle.

Second, documentation was ambiguous. Of the 214 recorded events, 63 could not be fully reconstructed afterwards because timestamps, locations or photographic evidence were missing or inconsistent. For a site that supplies KRITIS operators, this gap is more than an administrative inconvenience. It weakens the evidentiary chain that insurers, auditors and, in the case of cascading incidents, public authorities expect.

Third, escalation latency was longer than the control room assumed. The median time between the first physical indication of an incident and a verified alert reaching the client duty officer was 17 minutes. In roughly one out of five cases, latency exceeded 30 minutes. Under normal conditions this is manageable. Under the stress conditions described in the 72-hour scenarios of the source book, such latency would translate directly into loss of situational control.

The Integration: Mobile Robotics as a Layer, Not a Replacement

Quarero Robotics was engaged to design and operate a mobile robotic layer on top of the existing security architecture. The explicit scope was additive. Human officers were not replaced. Fixed cameras remained in place. The objective was to close the structural gaps identified in the review, specifically patrol density in low-frequency sectors, completeness of documentation and detection latency at the perimeter.

Four autonomous patrol units were deployed under a Robot-as-a-Service contract. Two units operated on the outdoor perimeter route, one unit inside the storage yard and one unit as a dynamic reserve assigned by the control room. The robots were integrated with the existing video management system, the access control platform and the client control room through a standard interface maintained by Quarero Robotics. Data protection officers and the works council were involved from the design phase, in line with the approach described in Chapter 14 of the source book, and detection zones as well as recording logic were documented before the first operational shift.

The integration phase lasted eleven weeks, including site mapping, route validation, integration testing with the control room and a four-week shadow-operation period during which robotic patrols ran in parallel with the established human routine without formal reliance on their output.

Measured Effects After Twelve Months of Operation

After twelve months of regular operation, the same internal team repeated the analysis using the metrics framework outlined in Chapter 16 of the source book. Patrol density in the previously under-covered sectors increased from 4 to 6 passes per 24 hours to a consistent band of 22 to 28 passes, without additional human personnel. Coverage of the outdoor area rose from 82 percent to approximately 97 percent of observable surface, measured against the site map used by the operator.

Detection latency improved substantially. The median time between a physical indication at the perimeter and a verified alert in the client control room fell from 17 minutes to 3 minutes and 40 seconds. The share of cases exceeding 30 minutes of latency dropped from around 20 percent to below 2 percent. Documentation completeness, measured as the proportion of recorded events with consistent timestamp, geolocation and image or video evidence, rose from 71 percent to 98 percent.

The incident load itself also shifted. Total recorded events increased slightly in the first three months, which the operator attributes to improved detection rather than a change in the threat environment. Over the full year, confirmed intrusion attempts at the perimeter declined by 41 percent, and attempted copper theft fell to zero. Insurance negotiations for the following period were conducted on the basis of the new evidence quality, which the broker treated as a material factor.

What the Case Study Does and Does Not Prove

The case study does not demonstrate that robotics alone creates resilience. It demonstrates that a combination of trained officers, fixed sensors and mobile robotics, coordinated through a single operational picture, closes gaps that were previously structural. The robots did not replace judgement. They removed the arithmetic problem of too few people covering too much space for too many hours, which is the core limitation identified in Chapter 10 of the source book.

The case also illustrates the governance value of a Robot-as-a-Service model. The operator did not acquire a fleet of machines with uncertain lifecycle cost. It contracted an availability-based service with defined response times, software update cycles and documented data handling. This converts a capital decision into an operational one and aligns with the due diligence expectations that flow from the NIS2 transposition and the KRITIS umbrella legislation discussed in Chapter 4.

Finally, the case study confirms the central thesis of the source book at the level of a single site. Stability is an architectural property. It emerges when technology, organisation and responsibility are combined deliberately. Quarero Robotics contributed the mobile layer, but the measurable improvement belongs to the operator who decided to measure, to document and to integrate.

The value of a before-and-after case study lies less in its headline figures than in the questions it makes answerable. A European industrial estate that could not previously state with confidence how many patrol passes its rear perimeter received per day, or how long it took for a perimeter event to reach a verified alert, can now state both, and can defend its answer with documented evidence. That is the operational meaning of resilience in the sense used throughout the source book by Dr. Raphael Nagel and Marcus Köhnlein. For operators preparing for the regulatory trajectory of NIS2, the KRITIS umbrella framework and the expectations of insurers and clients, the relevant question is no longer whether mobile robotics can contribute to a security architecture. It is whether the existing architecture is measured closely enough to notice the difference when it does. Quarero Robotics designs, deploys and operates the mobile layer on the assumption that its contribution should be visible in the numbers, in the evidence trails and in the behaviour of the control room under pressure. A site that cannot see the difference has not yet finished the work of measuring itself, and a site that can see the difference has already moved from static coverage toward the resilience architecture that European critical environments will increasingly require.