RaaS Contract Clauses: Model Framework for Procurement

RaaS Contract Clauses: Why Standard Contracts Are Insufficient

A Robotics-as-a-Service contract combines four contract types in one document: hardware rental, software licence, telecommunications service, and a surveillance-adjacent service. Treating the contract as a pure rental agreement overlooks three-quarters of the scope of performance.

The standard lease under BGB §535 governs the transfer of use of a physical object. It covers neither ongoing software updates nor the sensor data flows that sit at the centre of every security robot deployment. A Bewachungsvertrag under §34a GewO does not fit either: the robot exercises no sovereign or directly defensive powers. It detects and reports.

When procurement does not explicitly reflect the hybrid character, interpretation gaps arise in the event of a claim. Who is liable for a false alarm that triggers a production stoppage? Who bears the risk when a firmware update disables the patrol route? These questions must be resolved before contract signature, not in dispute proceedings.

Quarero works with modular contract documentation: a framework agreement, a service-level annex, a data processing agreement, and technical annexes containing site plans. Each module is separately negotiable; the overall document remains consistent. Details about the Robotics-as-a-Service model belong in the preamble of the framework agreement, not in a footnote.

Performance Description and Availability SLA

Availability is defined as a percentage per calendar month. QR-2 guarantees 98.5 percent patrol time, excluding scheduled maintenance windows. Source: Quarero Robotics product data sheet QR-2 Maintenance windows must be named explicitly: a maximum of four hours per month, announced 72 hours in advance.

Response times belong in a table, not in running text. Remote diagnosis within 4 hours of a fault report. On-site replacement within DACH within 48 hours. For KRITIS facilities, the on-site deadline shortens to 24 hours, at a surcharge.

The penalty mechanism stays simple: when the SLA threshold is missed, a pro-rated credit against the monthly fee applies, graded by severity. Below 95 percent availability, a credit of 25 percent of the monthly fee applies. Below 90 percent, the credit rises to 50 percent. Penalties are not damages claims; the contract must state this clearly.

Patrol routes and detection zones are attached as a site-plan annex, not described in prose. Each waypoint receives an ID; each camera receives a field-of-view angle in degrees. The separation between detection (robot) and response (PSIM control room or Werkschutz) must be documented in writing. Without it, a liability grey zone arises when escalation is delayed.

Next step: review QR-2 for 24/7 outdoor perimeter as a reference configuration.

Performance Description, Liability, and Insurance in the Security Service Contract

The liability cap per claim should equal at least ten times the annual fee. At an annual fee of €60,000, that produces a liability amount of €600,000 per incident. Cf. market-practice benchmark: Quarero contract framework Lower caps are not viable from the operator's perspective.

Product liability under ProdHaftG remains with the manufacturer, independent of the rental relationship. This separation must appear in the contract so that the operator addresses the correct counterparty in the event of a claim. The RaaS provider's public liability insurance is agreed at a minimum coverage amount of €5 million [market reference value per GDV guidance: https://www.gdv.de], evidenced by a current insurance certificate before contract commencement.

Personal injury caused by autonomous mobility is the most sensitive point. EN ISO 13482 defines safety requirements for personal care robots and serves as the evidentiary standard in personal-injury cases involving autonomous systems. The contract must name the standard explicitly and bind the provider to ongoing conformity. In the event of an accident, a court-appointed expert will assess the case against this standard.

The EU Machinery Regulation 2023/1230 extends manufacturer obligations to software updates and cybersecurity for autonomous machinery. This produces a dedicated update-obligation clause: safety-relevant patches within 30 days of availability, documented in the maintenance log. [Cf. EU Machinery Regulation 2023/1230, Art. 13: https://eur-lex.europa.eu/eli/reg/2023/1230/oj]

Cyber incidents are governed separately. The reference to NIS-2 obligations for operators belongs in a dedicated annex, not in the general liability section.

Data Sovereignty, GDPR, and Video Data

The data processing agreement under Art. 28 GDPR is non-negotiable. It is attached as a fixed annex, not as an optional document. Signing a RaaS contract without a DPA violates the accountability obligation under Art. 5(2) GDPR.

The storage location of sensor and video data must be stated explicitly: data centres in Germany or Switzerland only. Third-country routing via CDN or backup locations must be excluded. Where US-based sub-processors are involved, even indirectly through cloud providers, a Schrems II conflict arises that must be resolved contractually.

Retention periods for RGB and thermal data: 72 hours as standard. Extended retention only on a documented incident basis, for a maximum of 30 days, followed by automatic deletion with a deletion log. The provider's access rights to telemetry data (battery status, motor temperature, waypoints) must be cleanly separated from personal data. The provider may use telemetry data for product improvement; video data may not be used for this purpose.

Works council involvement under §87 BetrVG must be documented before commissioning. This point is regularly overlooked in standard RaaS texts and causes commissioning delays. Starting without a works agreement risks an interim injunction from the works council. The rented hardware stands idle while the rental fee continues to accrue.

Term, Renewal, and Exit Clause

The minimum term at Quarero is 24 months. Thereafter, quarterly termination applies with three months' notice to the end of a quarter. Shorter minimum terms are available but increase the monthly fee materially.

The right of extraordinary termination applies when the SLA is missed in three consecutive months. This clause is not optional. It is the operator's only lever against sustained underperformance. Penalties alone are insufficient because a persistently underperforming robot fails its security purpose.

The return procedure must be clearly regulated: hardware decommissioning by the provider, physical destruction of data media, destruction certificate issued to the operator. When switching providers, a transition period of 60 days of parallel operation is practical, at a pro-rated fee of 50 percent of the monthly charge.

Automatic renewal for a full 24 months is a standard trap and should be deleted. A renewal of 12 months with three months' notice is acceptable. Anything longer shifts risk unilaterally to the operator.

A clean RaaS exit clause matters more than the lowest entry price. The operator will often pay more for the exit than was saved during onboarding.

Price Adjustment and Indexation

A fixed price for the first 24 months is market standard and should be set out in writing. Thereafter, indexation to the consumer price index of the Federal Statistical Office applies. The calculation formula belongs in the contract, not in a service brochure.

Maximum annual adjustment is capped at 3.5 percent. Without a cap, budget risks arise that cannot be reflected in multi-year planning. Where adjustment exceeds 5 percent, the operator receives a special termination right with 60 days' notice.

Hardware upgrades during the term remain cost-neutral if they are functionally equivalent. When the provider substitutes a model for production reasons, the monthly fee may not increase. Sensor upgrades, such as a change from QR-1 to QR-2 or QR-3, are treated as a change request, not as a new contract. This protects the original term calculation and avoids a renewed minimum-term trap.

Buyers of a three-tier pricing model should also treat tier changes as change requests. A complete TCO comparison against conventional Wachschutz belongs in the decision paper for management.

KRITIS-Specific Additional Clauses in the Security Robot Contract Template

Stricter requirements apply for KRITIS sectors. The subcontractor prohibition without the operator's written consent is non-negotiable. Providers that work with fluid subcontractor networks are unsuitable for KRITIS facilities.

Security vetting of deployed technicians is carried out under §8 SÜG where the facility falls within scope. The provider demonstrates completed vetting before the first on-site deployment, not only on request. The provider's obligation to notify the operator of its own security incidents is 24 hours from the time of knowledge. [Cf. NIS-2 Directive Art. 23: https://eur-lex.europa.eu/eli/dir/2022/2555/oj]

Supply chain security is addressed concretely in the contract: origin of sensors and firmware is documented; no third-country routing of control data. The NIS-2 Directive obliges operators of essential entities to address supply chain security and incident reporting, which must be reflected in RaaS contracts. A clause that passes these obligations to the provider has become standard.

The KritisV defines threshold values and sector classification for critical infrastructures, which shape subcontractor clauses in RaaS contracts. Operators below the thresholds may draft the clauses less strictly. They should still understand the escalation logic in case the facility later grows into scope.

The operator's audit right is exercised once annually on-site, plus on an ad-hoc basis after incidents. Audit costs are borne by the operator, except where deficiencies are identified. This cost allocation is market standard and prevents abusive routine audits. Preparation details are provided in the KRITIS-Dachgesetz checklist 2026.

Negotiation Strategy for Procurement

Comparative offers from at least two RaaS providers should be obtained on an identical performance matrix. Without identical specifications, price comparison is meaningless. One provider calculates on 20 hours of patrol time per day; another calculates on 12. The hourly rate then diverges by 40 percent. Procurement sets the performance matrix; the provider does not.

Calculate TCO over 48 months, not 12. Over 12 months, the acquisition effect distorts the picture in favour of the rental solution. Over 48 months, the true cost structure becomes visible: maintenance, updates, insurance, and exit costs included.

A 90-day pilot phase with a withdrawal right before the minimum term begins is negotiable and reduces risk materially. The provider bears hardware provisioning; the operator pays a reduced pilot fee. Skipping the pilot and moving directly into a 24-month term saves weeks. The risk: misdirected investment in the six-figure range.

Insurance certificates and ISO certifications (ISO 27001, ISO 13482, ISO 9001) are requested in physical form before contract signature, not via email reference. Expired certificates are a warning signal. Legal counsel and the head of security belong at the negotiating table together, not sequentially. Bringing in the lawyer only after the technical review has concluded means reopening material points.

The next concrete step: submit a pilot enquiry for QR-2 and check the clauses described here against the offer. The complete Quarero framework agreement with all annexes is available on request via the Robotics-as-a-Service overview. It serves as a reference for the operator's own negotiating position.