AGV RFP red flags: avoiding vendor lock-in

A food and beverage manufacturer in the Midwest ran a successful AGV deployment for 7 years. Fleet performance was solid. At year 7, the vendor discontinued the hardware line. The fleet management software continued to be supported under a legacy agreement, but no new vehicles of the same platform were available — and the FMS was not compatible with any other vendor's vehicles. The manufacturer's choices: pay the vendor's end-of-life premium pricing for the remaining compatible vehicles they could source from secondary markets, or completely re-tender the project (new vehicles, new FMS, new integration) at full project cost.

They re-tendered. The cost to re-tender at year 7 was approximately 85% of the original project cost — a number that would have been significantly lower if the initial RFP had included portability requirements that forced the vendor to design for interoperability.

Lock-in in AGV systems is not incidental. It is a natural consequence of proprietary architectures, and it is frequently engineered — not accidentally — through FMS design, spare-parts agreements, and contract structures that make changing vendors expensive at every stage of the asset lifecycle.

This article covers the 12 most common red flags in AGV vendor proposals and the specific contract provisions and technical requirements that address each one.

Navigation and hardware lock-in

Red flag 1: Proprietary reflector geometry

Laser-guided AGV systems (LGVs) use reflective targets mounted on walls and racking to establish the vehicle's position. Most vendors use standard circular reflectors (typically 100mm or 150mm diameter) from the same 2–3 industrial suppliers. A small number of vendors use proprietary reflector geometries — unique shapes or coded arrays that their vehicles read but competitors' cannot.

If a vendor specifies a proprietary reflector type, your guide infrastructure is tied to that vendor's vehicles. When the vendor's platform is discontinued or you want to expand with a different vendor's units, you replace the entire reflector installation.

What to specify in the RFP: "All laser reflectors must be standard circular retro-reflective targets compatible with at least three independent AGV vendors." Ask the vendor to name the reflector specification (supplier, part number, dimensions). If they cannot, or if the answer is "our proprietary type B reflector," it is a lock-in risk.

Red flag 2: Embedded floor infrastructure tied to the vendor's vehicle

Wire-guided AGV systems are inherently tied to the installation — the wire is in the floor and can be used by any wire-guidance-compatible vehicle. This is actually a portability feature: if you switch wire-guidance AGV vendors, the floor infrastructure is reusable.

The lock-in risk with wire guidance is different: the guide frequency. Different vendors use different electromagnetic frequencies for their wire-guidance systems. If Vendor A uses 10 kHz and Vendor B uses 16 kHz, their vehicles cannot share the same guide wire. Verify at the RFP stage that the guide frequency specified is standard (typically 10 kHz, 20 kHz, or 38 kHz) and shared by at least two major vendors.

For magnetic tape systems, the tape itself is vendor-neutral — any magnetic tape-compatible AGV can follow standard magnetic tape. Verify that the tape specification is standard and not a proprietary encoding.

Red flag 3: No published vehicle communication interface

Modern AGV fleet management depends on communication between the vehicles and the FMS using a standard interface. The emerging standard is VDA 5050 (Vehicle Interface for Automated Guided Vehicles, developed by VDA and VDMA), which defines a JSON-over-MQTT protocol for task assignment, position reporting, and status exchange.

VDA 5050 compliance means a vendor-neutral FMS can manage the vehicle. Without it, the FMS layer is tied to the vehicle vendor.

What to specify in the RFP: "All vehicles must support VDA 5050 v2.0 or later as the primary communication interface. Vendor-proprietary extensions are permitted only as supplementary to the standard interface." Request the VDA 5050 compliance certification or the test results from an independent VDA 5050 interoperability event if available.

VDA 5050 adoption is growing but not universal as of 2025. European automotive and logistics AGV vendors (Jungheinrich, Linde, STILL, Grenzebach) have broad VDA 5050 support. North American vendors vary significantly. Chinese-manufactured AGVs are increasingly VDA 5050 compliant but may have version gaps. Ask specifically for the VDA 5050 version supported and whether the implementation has been tested in a multi-vendor fleet management environment.

Fleet management software lock-in

Red flag 4: FMS not exportable or replaceable without vendor consent

The fleet management software is the highest-value component of the AGV system and the component most vulnerable to lock-in. The FMS holds:

• The route and zone configuration
• The traffic management rules and intersection logic
• The WMS/WCS integration logic
• The historical performance data and KPI logs
• The vehicle calibration parameters

If all of this data is stored in a proprietary database with no export capability, and if the FMS is licensed on a per-instance basis that makes it non-transferable to a neutral platform, the operator cannot switch FMS vendors without losing years of configuration and performance history.

What to require in the RFP:

• Route and zone configuration must be exportable in an open format (XML, JSON, or VDA 5050 topology format)
• All historical task and performance data must be exportable in CSV or JSON at any time, without vendor assistance
• Software license must be site-perpetual — tied to the facility, not to a vendor account
• Source code escrow for critical FMS components, accessible in the event of vendor insolvency

Red flag 5: Annual SaaS licensing with no off-ramp

Cloud-hosted fleet management platforms (increasingly common from newer vendors and AMR-first vendors entering the AGV market) often use annual SaaS licensing structures. SaaS licensing is not inherently problematic, but these provisions are:

• No perpetual license option: if the vendor ceases to offer the product, your FMS ceases to function. This is existential for a fleet running production logistics.
• Data portability not guaranteed: some SaaS agreements specify that the vendor retains data ownership during the licensing period, limiting what you can export without the vendor's cooperation.
• Price escalation provisions: SaaS contracts with annual price escalation clauses tied to "market rates" or CPI + X% give the vendor pricing leverage after the fleet is live and switching is expensive.

What to require: A software escrow agreement that gives you access to the FMS software and configuration data if the vendor ceases to support the product. A data portability clause that allows full export at any time. A fixed or CPI-capped escalation on annual software fees.

Red flag 6: Traffic management rules not documented in a portable format

The traffic management configuration — how intersections are arbitrated, which routes have priority, what happens when two vehicles compete for the same zone — is intellectual work that accumulates over months of tuning. If it exists only as vendor-internal configuration in the FMS, you lose it if you change vendors.

Require that all traffic management rules be documented in a human-readable format (not just a database export) and included in the project deliverables. This documentation should be detailed enough that a new vendor's integration team could recreate the logic in a different FMS.

Spare parts and maintenance lock-in

Red flag 7: Sole-source spare parts clauses

Some AGV contracts include explicit provisions requiring the operator to purchase spare parts exclusively from the vendor for the life of the vehicle. These clauses are typically buried in the maintenance agreement or the warranty terms, not in the main commercial contract.

Sole-source spare parts are a reliable path to elevated cost in years 3–10: the vendor knows you cannot source the part elsewhere and prices accordingly.

What to require: The right to source standard components (motors, drive units, batteries, sensor heads, wheels) from third-party suppliers or directly from the component manufacturers after the warranty period. The warranty should cover defects in the vendor's assembly and integration work, not restrict your procurement options for commodity components.

What to check specifically: Ask the vendor to specify the make and model of the drive motors, the LiDAR sensor, and the battery management system used in the vehicle. If all three are proprietary components with no OEM listed, the spare parts chain is entirely vendor-controlled. If all three are third-party components (Beckhoff, SICK, Hokuyo, CATL, etc.) with available OEM part numbers, spare parts can be sourced competitively after the warranty period.

Red flag 8: On-site maintenance required to be performed by vendor personnel

Some contracts specify that any maintenance beyond Level 1 (cleaning, visual inspection) must be performed by vendor-certified technicians — and that the only certified technicians are vendor employees or approved vendor partners. This creates a permanent labor dependency.

What to require: A training program that qualifies your own maintenance staff to perform all maintenance procedures up to Level 3 (component replacement, sensor calibration, software parameter changes) within 12 months of system commissioning. Certification should transfer to your staff, not be held by the vendor.

Commercial and contractual red flags

Red flag 9: SLA that references "best efforts" or "commercially reasonable"

Service level agreements that commit to "best efforts" or "commercially reasonable response" have no contractual bite. They cannot be measured and cannot trigger remedy provisions.

What to require: Time-based SLAs with specific numbers and specific remedies:

• Remote support response: ≤ 30 minutes acknowledgment for Class A faults
• Remote resolution: ≤ 2 hours for software-resolvable Class A faults
• On-site response: ≤ [X] hours (based on actual geography of nearest service center)
• Penalty: credit against annual maintenance fee for SLA misses, at a rate that creates real incentive

Ask for the nearest field service location by city, not by region. An SLA that says "same-region response" could mean the technician is 4 hours away.

Red flag 10: Contract includes first right of refusal on expansion

Some AGV vendor agreements include a clause giving the vendor right of first refusal to supply any additional AGVs purchased for the same facility. This clause sounds benign but eliminates competitive pressure on fleet expansion. If you want to add 5 units to a 10-unit fleet and the original vendor knows you cannot go to market without their consent, they can price accordingly.

What to require: Remove any right of first refusal clause entirely. All expansion purchases are separately tendered. The incumbent vendor may bid.

Red flag 11: Non-standard data ownership provisions

Increasingly, AGV vendors claim ownership of operational performance data generated by their vehicles — cycle time records, route telemetry, maintenance events. This data is valuable for the vendor (for product development, fleet benchmarking, and upselling analytics tools) and for you (for operational optimization and vendor accountability).

What to require: "All operational data generated by vehicles and systems operating at Buyer's facility is the exclusive property of Buyer. Vendor may use aggregate, anonymized data for product development purposes with Buyer's consent, subject to a data processing addendum."

Red flag 12: Software update rights not addressed

Firmware and software updates for AGV systems are not optional — they fix safety issues, address sensor drift, and maintain FMS compatibility. But software updates also introduce risk: a firmware change that improves performance in one environment may introduce bugs in another.

Contracts that don't address update rights leave you in an ambiguous position: you may be required to accept updates to maintain warranty coverage, or you may be unable to update without triggering expensive re-validation (in regulated industries).

What to require:

• All software updates must be documented with a change log before deployment
• Operator retains the right to delay non-security updates for up to 90 days
• Rollback procedure for every update must be documented and tested
• In GMP-regulated environments: updates must be provided with sufficient documentation for re-validation under the operator's change control procedure

The VDA 5050 litmus test

If you take only one technical requirement from this list: require VDA 5050 v2.0 compliance.

VDA 5050 compliance is not just a technical specification — it is a signal about the vendor's posture toward interoperability. A vendor that has invested in VDA 5050 certification is building for a world where their vehicles must compete on price and performance without relying on proprietary lock-in. A vendor that deflects on VDA 5050 — "we have our own more advanced interface," "VDA 5050 doesn't cover all our capabilities," "we'll add VDA 5050 support in a future version" — is making a commercial choice to defend their FMS monopoly.

This doesn't make them a bad vendor. It makes them a vendor whose vehicles will be harder to integrate into a multi-vendor fleet, harder to manage under a neutral FMS, and more expensive to move away from if the relationship deteriorates. Price that risk accordingly.

The RFP structure that protects you

Close your RFP with a portability requirements section that addresses each of these twelve risk categories. Structured as explicit requirements — "the vendor must..." or "the proposal must include..." — rather than preferences. Score proposals on their compliance with portability requirements, not just on price and feature set.

A vendor who scores well on portability may not be the cheapest option in year one. They will almost certainly be the less expensive option in year seven.

The goal is not to eliminate vendor relationships — it is to maintain competitive leverage throughout the asset lifecycle. Proprietary lock-in transfers that leverage entirely to the vendor. Well-structured RFP requirements keep it with you.