67% of AGV/AMR projects stall in one phase.
Do you know which one?
AGV/AMR Playbook v1.4 — analysis of 87 deployments from 37 manufacturers (2020–2025). What separates projects that close in 245 days from those that slip by half a year? Not the vendor. Not the scale. One phase where 80% of deployment success is decided.
67%
Bottleneck in P2Engineering accounts for 67% of bottlenecks. Together with Procurement (21%) — 88% of projects stall in P2 or P3.
Average deployment time245 days from contract
CUSTOM compliance300–360 days
PILOT4–7 months
Base87 case studies · 37 manufacturers
This summary shows exactly where projects stall and how to detect it in phase 1, before phase 5 collapses.— for the deployment PM who's tired of chaos in spreadsheets.
01 — Process map
8 phases, 245 days, one bottleneck.
Standard deployment of 5–30 robots: 245 days from contract to production start. CUSTOM compliance (pharma/auto/food): 300–360 days. PILOT: 4–7 months.
Phase
Duration
% bottlenecks¹
What happens here
P1 · Site Survey
14 days
5%
Physical audit, WiFi, floor FF/FL
P2 · Engineering
28 days
67%
Layout, simulations, WMS plan, compliance
P3 · Procurement
100–120 days
21%
Order + chip shortage 2026
P4 · Site Prep
21 days
2%
Warehouse, AP WiFi, chargers, HSE
P5 · Installation
28 days
3%
Installation, WMS integration, calibration
P6 · UAT
21 days
1%
Acceptance tests, 25 acceptance points
P7 · Training
21 days
1%
Training, documentation, UDT
P8 · Hypercare
28–90 days
<1%
Start + monitoring + ROI dashboard
¹% case studies (87/87) identifying the main bottleneck here. Engineering 67% + Procurement 21% = 88% of projects stall in P2 or P3.
The rest of P4–P8 is execution according to the P2 plan. If P2 was weak — P5 will exact revenge 5× more expensively.
02 — Critical path
What blocks what — 245-day critical path.
5 tasks block 38 other tasks on the critical path. Every day of delay in the first = one day of delay across the entire project.
DAY 43P3-T1Order
DAY 143P5-T1Installation
DAY 170P5-T3WMS Int.
DAY 191P6-T7Acceptance
DAY 213P8-T1Go-live
01
P3-T1 · Device order
100d lead (STANDARD), 120d (CUSTOM). Every day of delay in P3-T1 = one day of delay for the whole project.
02
P5-T1 · Physical installation
Waits for hardware from P3 and warehouse from P4 (in parallel).
03
P5-T3 · WMS Integration
40h of work + 30d lead. #1 schedule slip risk in the 87 CS database.
04
P6-T7 · Signing acceptance protocol
Without this, the client won't pay the final installment.
05
P8-T1 · Production start
Requires UDT (PL, forklift >1t) and compliance.
Tactical lesson: in the first hour of P3, place the order with the manufacturer. Not the first day, the first hour. 100 days from now is 100 days from now, not 100 days from "when we get around to it".
03 — Top 5 causes of delays
From analysis of 87 deployments — what concretely goes wrong.
Every delay costs 5× more in P5 than in P2. 1h of IT audit in P2 saves 5–10h of emergency work in P5. For enterprise WMS without P2-T13 audit — integration in P5 blows up to 60–80h instead of planned 24h.
01
Underestimated client WMS integration
Mitigated byP2-T13 WMS Audit (8h, CONDITIONAL)
Typical delay4–6 weeks
02
No POC validation before full deployment
Mitigated byPILOT template + decision gate
Typical delay8 wks → 12 mos.
03
Compliance discovery too late (P6 instead of P2)
Mitigated byP2-T18 Compliance Gap Analysis (12h)
Typical delay60+ days
04
Naive lead times in quotes (60d promised, 100d real)
Mitigated byTemplate update from 8 May 2026: 100/120/30
ConsequenceLost credibility
05
No Business Case + KPI Baseline
Mitigated byP3-T0 (8h, mandatory since 8 May 2026)
ConsequenceNo client reference
Shift Left: all 5 causes can be mitigated in P1–P2. Only #4 (lead time) is a contractual decision.
04 — Engineering trap (P2 deep dive)
Why 67% of projects stall in phase 2.
Phase P2 lasts 21–28 days and costs 108h of effective work. Looks cheap. In fact: it decides 80% of project success.
Trap 1
WMS plan written superficially
P2-T5 (WMS integration plan) treated as 16h of documentation. For legacy SAP EWM, Manhattan Active, Oracle WMS Cloud the real effort is 40–80h. Without P2-T13 WMS Audit (8h, CONDITIONAL for WMS=enterprise) risks go undetected until P5.
Trap 2
Compliance discovery deferred to P6
Pharma/automotive/food client signals compliance requirements only during testing. It turns out IATF 16949, GMP or HACCP requires things not accounted for in engineering. Rework P5–P6: 60+ days.
Trap 3
Layout without Operations
P2-T7 design validation with the client skipped. In P5 it turns out the aisle width is 30 cm too narrow for Q4 peak. FlexSim simulation in P2-T2 (24h) reveals these things before hardware is ordered.
Trap 4
Cybersecurity ignored
P2-T22 Vendor Cybersec RFP (SBOM + MFA + patch mgmt) is mandatory for CUSTOM since v1.2. Vendor without SBOM is disqualified in P3 enterprise client RFP. Compliance officer asks in P2, not in P5.
P2 anti-pattern: "we'll start designing, WMS integration we'll add at the end" — guaranteed rework for €50k+.
05 — Procurement reality 2026
100 days, not 60 — and why the client must know this from the start.
Global chip shortage 2024–2026 has changed the AGV/AMR procurement landscape. TechFleet PM template update from 8 May 2026 reflects the new reality. Asian manufacturers (Geek+, Hai Robotics, Quicktron): 60–90d. European premium (KUKA, Jungheinrich, Toyota MH): 100–130d.
Template · STANDARD
100days P3-T1
STANDARD lead time
Typical deployment of 5–30 robots.
Template · CUSTOM
120days P3-T1
CUSTOM lead time
Compliance / heavy_payload / mobile_manipulator.
Template · PILOT
30days P3-T1
PILOT lead time
Rental fleets, concept validation.
3 things that MUST be in P3 (and often aren't)
P3-T0 · 8h · MANDATORY
Business Case + KPI Baseline
Measure UPH/LPH/MTTR BEFORE deployment. Without baseline there's no ROI evidence after a year → CFO won't sign fleet expansion → you lose expansion deal (50% additional revenue per client).
P3-T5 · 24h
FAT + SBOM verification
Factory visit before shipment. Firmware verification, LIDAR calibration, SBOM per NIS2. Skip it? P5 stops for 14–30 days waiting for damaged hardware replacement.
NEW · v1.1
Manufacturer financial due diligence
Check company registry, financial statements. In the last 3 years several significant AGV/AMR vendors went bankrupt or were acquired. 100d advance payment to a failing manufacturer = project cancelled.
Communicate 100–120 days to the client from day one. "Marketing speak" from manufacturers is their problem. Your problem is delivering on the declared timeline.
06 — Compliance Shift Left
ISO 3691-4 + NIS2 + VDA 5050 as Enterprise Filter.
Without these three standards, entry into a modern facility (Pharma, Auto, Enterprise Logistics) is impossible. Compliance discovery must be in P2, not P6.
Safety · CE · mandatory
ISO 3691-4:2023
2023 standard (replaced EN 1525). Defines: safety scanner, speed zones, signaling, escape routes, mixed manual/automated workflows. Without compliance — no production start.
ActionP1-T9 Safety Zones Design (8h, mandatory since 8 May 2026) P5-T6 Safety tests
Cyber · OT · enterprise
NIS2
EU Directive 2022/2555. Requires: VLAN OT segmentation, SBOM (Software Bill of Materials), MFA for vendor access, incident reporting to CERT (24–72h), backup + disaster recovery. Management bears personal liability for lack of controls.
German standard "fleet manager → AMR". Allows mixing AMRs from different manufacturers under one master system. BMW, VW, Mercedes require since 2024.
ActionCheck in P2-T13 whether the manufacturer has VDA 5050-compatible firmware before P3 order.
Industry compliance — which standard when
Industry
Mandatory
Validation phase
Pharma
GMP/GDP, FDA 21 CFR Part 11, IQ/OQ/PQ
P5–P6
Automotive
IATF 16949, ISO/TS 15066, VDA 5050
P2–P6
Food
HACCP, ISO 22000, BRC
P2–P6
ATEX zones
Directive 2014/34/EU
P3–P5
Quality filter: a vendor who doesn't answer questions about SBOM/MFA/patch management is not ready for enterprise clients in 2026+.
07 — UAT it works
25 acceptance points in 6 categories.
P6 lasts 14–30 days. For CUSTOM compliance — 21–30 days with industry-specific tests (P6-T11, 40h). The client will refuse to sign the acceptance protocol without concrete metrics. Each point: criterion + validation method + acceptable deviation + who approves.
Functional
5
Robot executes 100% of picking scenarios with full SKU list
Performance
5
Throughput achieves UPH per contract ±5%
Safety
5
E-Stop response time < 500ms (per ISO 13849)
Integration
4
WMS integration works both ways (50 sample orders)
Documentation
3
As-built CAD delivered before P7-T7
Training
3
Client operators trained with exam
Peak Rehearsal (P6-T15) — critical for retail/e-commerce
For every client with Tag Peak Season enabled — 2× nominal load simulation for 8h. Without this, the first Black Friday reveals a 15–20% UPH drop that could have been detected in UAT for 24h of work.
Anti-pattern: "Battery life ±10%" without conditions
In playbook v1.2.5: criterion must include duty cycle / temperature / load. Otherwise arguments "is 9% acceptance or not" cost weeks in UAT.
Tip: start P6 with a meeting with the client where you go through the list point by point together. 2h investment = save weeks of arguments.
08 — STOP-GATE
8 readiness checklists — one before each phase.
Each phase in the playbook ends with a STOP-GATE — a list of points that must be met before closing the phase. Proceeding with gaps = the most common cause of delays in 87 case studies.
P1 → P2
10 pointsSTOP-GATE Site Survey → Engineering
Warehouse layout in digital form (CAD with dimensions)
WiFi coverage heatmap
Floor FF/FL Class report (brownfield: external surveyor)
Route map + min. 5 collision points
Load specification (cycles, weight, rotation)
Ergonomics report (multi-shift if >1 shift)
Safety zones design signed by EHS (P1-T9, NEW)
Site Survey Report final signed by integrator and client
List of identified risks for P2 with mitigation owner
WMS access account for integrator (key to P2-T13)
P2 → P3
10 points— most criticalSTOP-GATE Engineering → Procurement
Final fleet layout (CAD with robot positions, stations, routes, zones)
FlexSim/AnyLogic simulation report
Complete technical specification
WMS integration plan + assumptions log (P2-T5)
WMS Audit Report (P2-T13 if WMS=medium/enterprise)
Network diagram (WiFi heatmap, VLAN, controller)
Client validation approval (Operations + IT + EHS)
Compliance Gap Report (P2-T18 for pharma/auto/food)
BOM (Bill of Materials) ready to submit in P3-T1
Client decision on budget and payment terms
STOP-GATE pattern in remaining phases
P3 → P4FAT report + hardware physically on site (or confirmed ETA)
P4 → P5Warehouse physically ready + AP WiFi pre-configured
P5 → P6WMS integration end-to-end + safety test report
P7 → P8UDT (PL, forklift >1t) — without this no production start
P8 → closeoutFinal acceptance + MTBF/MTTR dashboard active
Discipline pattern: "Red STOP-GATE > green schedule." Better to be 5 days late closing a phase than enter the next one with gaps and lose weeks on rework.
09 — Toolkit
6 templates to copy.
Ready PM documents based on 87 case studies. Copy into your tool (Excel, Asana, Jira, MS Project). Each template saves 4–8h vs building from scratch.
4.1 · UAT
UAT Acceptance Criteria
25 points × 6 categories. Format: criterion + validation method + acceptable deviation + who approves. Copy into P6 as client acceptance criteria.
4.2 · Gantt
Gantt example (245-day STANDARD)
Visual example for a medium 3PL × 30 AMR deployment. Critical path: P3-T1 → P5-T1 → P5-T3 → P6-T7 → P8-T1. 38 tasks on critical path.
4.3 · Risk
Risk Register
26 typical risks from 87 CS. Format: name, probability (L/M/H), impact (L/M/H), score (1–9), mitigation, owner. Top score 9: WMS underestimated, naive lead times, works council blocks start.
4.4 · SLA
Post-deployment SLA (Hypercare)
4 ticket priorities (P1 critical → P4 low) × response time × restore time × L1/L2/vendor escalation. Copy into client contract for P8 (28d standard, 60–90d retail/peak, 90–120d enterprise).
4.5 · RACI
RACI matrix
17 activities × 8 stakeholders (PM, Senior Eng., Operations, IT, EHS, Procurement, CFO, Legal, HR, Manufacturer, Compliance officer, TechFleet Operations). Living document — review at every phase kick-off.
4.6 · Communication
Communication plan + RAG criteria
Cadence per phase (daily / weekly / bi-weekly / monthly). Explicit health status criteria: green/yellow/red. 1-page weekly status report format. Email > dashboard screenshot — it creates an audit trail.
10 — Insight
A pattern of discipline.
"
Red STOP-GATE > green schedule. Better to be 5 days late closing a phase than enter the next one with gaps and lose weeks on rework.
TechFleet · AGV/AMR Playbook · v1.4 · 9 May 2026
11 — What's next
Join the waitlist for the full playbook.
We're finalizing the full 125-page AGV/AMR Playbook v1.4. Analysis of 87 deployments, 8 STOP-GATE checklists, 6 PM templates, compliance mapping per phase.
Be the first to get it when it's ready.
The playbook covers 8 phases × 4 risks per phase, a glossary of 47+ industry abbreviations, ISO/NIS2/VDA standards mapped per phase, and 87 case studies.
~125 pages · 8 phases × 4 risks per phase
Glossary of 47+ industry abbreviations
ISO / NIS2 / VDA standards mapped per phase
87 case studies with 5 charts
8 conditional tags adapted to industry
This document evolves. v1.4 from 9 May 2026 — next version with every new case study added.