Outdoor AGV PtP/PtMP Wireless Comparison: Cisco URWB vs Rajant Kinetic Mesh vs Cambium ePMP vs HPE Aruba Outdoor Mesh

Both URWB and Rajant Kinetic Mesh target the same use cases — high-mobility AGV, rail rolling stock, autonomous haul trucks, mining, ports. The decision driver is documentation depth and management plane. Cisco URWB publishes a sub-millisecond path-reconfiguration figure (per the URWB Fluidity Specs PDF), 99.995 percent availability, less than 10 ms end-to-end latency, and 225 mph speed tolerance — all in primary-source datasheets. Rajant InstaMesh describes “extremely fast decisions” without a millisecond claim. Where a buyer needs sub-ms documentation in a SOW, URWB. Where decentralized, no-controller, peer-mobile mesh is the architectural requirement (military, public safety, ad-hoc deployments), Rajant. See the Cisco URWB Solution Overview.

Cambium ePMP / cnWave / PTP fits when the wireless endpoints are stationary — tower-to-customer, yard-to-building, building-to-tower. PTP 670 / 700 carry 200 mph wind survival and FIPS 140-2 on the 700; ePMP 4500 / 4600 carry 124 mph survival and IP67. There is no make-before-break primitive, no Fluidity equivalent. If the deployment is a fixed mast on a Tehachapi ridgeline feeding a fixed warehouse roof, Cambium is often the more cost-effective and harder-windrating answer than URWB. If the deployment carries an AGV terminal tractor or a rail-wayside node, Cambium is not a fit. See the Cambium PTP 670 datasheet.

Approximately 50 km/h is the practical ceiling for 802.11r FT in production AGV deployments. Below that, 802.11r FT with 802.11k Neighbor Reports + 802.11v BSS Transition Management hints + cached PMK-R1 keys reaches 15-50 ms in production and is fully adequate for warehouse mezzanine voice and mechanic-tablet roaming. Above ~50 km/h, three failure modes stack: OFDM channel coherence drops to ~250 microseconds at 300 km/h, full UNII-band scans run hundreds of ms, and FT 4-message handshake retry pile-ups push exchange time above the 50 ms target. Per IEEE 802.11-2024 (which consolidates 802.11r-2008), 50 ms is a target, not a guarantee.

IW9165D Heavy Duty is the wayside / vehicle / fixed PtP-PtMP / mesh radio with built-in directional antenna, IP67, -50 to +75 °C. IW9165E Rugged is the AGV / vehicle / cabinet form factor (IP30 DIN-rail, -20 to +50 °C) that uniquely operates as WGB / URWB / Wi-Fi AP / URWB+Wi-Fi simultaneously on the same chassis. IW9167E Heavy Duty is the outdoor pole-mount with three 4×4 802.11ax radios, eight N-type connectors, IP67, -50 to +75 °C. IW9167EH-HZ is the HazLoc variant certified for Class I Division 2, ATEX Zone 2/22, IECEx — oilfield, refinery, pipeline meter / compressor / pump station selection. See the IW9167E datasheet.

Cisco Prodigy 2.0 is an MPLS-over-wireless implementation. The current Cisco URWB CLI user manual documents Prodigy 2.0 as “a Multiprotocol Label Switching (MPLS)-based technology used to deliver IP-encapsulated data” with “greatly improved performance compared to Prodigy 1.0” (the two are not compatible). Make-before-break works because the new label-switched path is established before the old one tears down. Rajant InstaMesh runs at Layer 2 with self-routing, no root node, no LAN controller, and no mobility-group construct — “If it works on Ethernet, it works on Kinetic Mesh.” Both deliver fast topology re-routing on moving radios; only Prodigy 2.0 has the published sub-ms figure.

Yes, but with caveats. 6 GHz outdoor Standard Power requires AFC system control under FCC OET Public Notice DA-24-166; outdoor SP APs are capped at 21 dBm EIRP above 30° elevation angle to protect Fixed Satellite Services. The initial 2024-02-23 commercial-approval batch authorized seven AFC system operators (Qualcomm, Federated Wireless, Sony, Comsearch, Wi-Fi Alliance Services, Wireless Broadband Alliance, Broadcom). Subsequent additions through 2025-09 (C3Spectra 2025-07, Axon Networks 2025-09) bring the count to 9 commercially-approved AFC operators as of 2026-04-27. The “13 currently authorized” framing some sources cite mixes the November-2022 conditional-approval pool (13) with current commercial operations (9).

Per 14 CFR § 77.9, the absolute trigger is 200 ft AGL. Below 200 ft, slope-imaginary surfaces still apply: 100:1 within 20,000 ft of a public-use airport runway longer than 3,200 ft; 50:1 within 10,000 ft of a runway 3,200 ft or shorter; 25:1 within 5,000 ft of a heliport. Traverse-way and instrument-approach-area triggers add per-position requirements. FAA Form 7460-1 must be filed at least 45 days before construction start. A 50-ft monopole on a Tehachapi ridgeline below the absolute trigger may still penetrate the slope surface of Mojave Air and Space Port (MHV) or Tehachapi Municipal (TSP); site-specific math is mandatory.

When the wireless equipment installs in an environment where flammable gases, vapors, or liquids are present under abnormal conditions (Class I Div 2) or rare / short-duration (ATEX Zone 2 / 22, IECEx Zone 2 / 22) per NFPA 70 Article 500. Oilfield, refinery, chemical plant, and pipeline meter / compressor / pump stations are textbook Class I Div 2 zones. The IW9167EH-HZ carries Class I Div 2 / ATEX Zone 2/22 / IECEx and imposes a passive-antenna constraint (max inductance 50 microhenries, max capacitance 0.01 microfarads) per the Cisco IW9167EH HazLoc Solution Overview — this eliminates most commodity high-gain Yagis. The base IW9167E and standard Rajant / Cambium / Aruba SKUs do not carry the HazLoc floor.

Yes when the air-link carries technical data classified as defense articles per 22 CFR § 120.54. ITAR scopes the data, not the radio; if a foreign-national mechanic on the hangar floor associates to an outdoor URWB-fed cluster carrying engineering drawings of an F-35 component, the wireless infrastructure is in scope. Practical compliance pattern: WPA3-Enterprise EAP-TLS supplicant authentication terminating against a FIPS 140-2 / 140-3 validated module on the controller side, plus US-citizen-only network policy enforced at the RADIUS layer. WPA3-Enterprise air-link is necessary but not sufficient; cryptographic-module-validation chain per NIST CMVP closes the loop.

Indirectly. NIGC tribal gaming compliance (GLI-11, GLI-26 wireless gaming) scopes the wireless infrastructure adjacent to slot-floor gaming systems — meaning the indoor casino floor wireless. Outdoor AGV / port / mining / pipeline wireless is generally outside the gaming-compliance perimeter. The exception: tribal-owned outdoor distribution centers, hospitality, or industrial facilities operating on tribal land may inherit some compliance scope from the gaming compact. The right-sizing question is whether the outdoor URWB cluster handles any traffic that touches the gaming control plane; if not, the standard outdoor / industrial regulatory frame (FCC 47 CFR Part 15, FAA Part 77, NFPA 70 Article 500) governs.

MSHA-permissible equipment is required underground inby the last open crosscut in coal mines per 30 CFR Part 75. The IW9167EH is NOT MSHA-permissible — it is rated Class I Division 2 (above-ground hazloc), not the MSHA Permissible category required for underground coal. Underground deployments use MSHA-listed mesh radios, leaky feeder, or specialty MF/LF systems. Surface mining per 30 CFR Part 77 is the canonical URWB use case — autonomous haul trucks, AGVs, tele-remote shovels — validated by the Cisco Open-Pit Mining CVD.

Per 33 CFR Part 105, container-terminal facility operators must implement a TWIC Program with PACS records on a separated logical plane and 49 CFR 1520 SSI transit encryption. The wireless design implication is VLAN / VRF separation: the URWB Fluidity cluster carrying RTG crane, AGV terminal tractor, and ASC racking traffic rides one VRF; the TWIC-validated PACS records and access-control telemetry ride a separate VRF terminating against the facility security plane. EVPN-VXLAN tenant-edge isolation per IEC 62443 enforces the boundary. Cisco URWB's named port deployments (Thessaloniki, La Spezia, Malta Freeport, DP World Evyap Körfez) follow this pattern per the URWB Solution Overview.

Yes when deployed per the Cisco Rail CBTC Implementation Guide reference architecture. 49 CFR Part 236 Subpart I mandates uninterrupted controlling-locomotive movement across PTC-railroad property boundaries and AAR S-9210 / S-9215 wireless-interoperability standards underpin the wayside-to-locomotive radio link. URWB's 225 mph speed tolerance and zero handoff time across cluster boundaries align with the FRA's 50 ms wireless handover target and less than 0.1 percent packet loss requirement (Cisco Rail CBTC Design Guide). PTC operational on all 57,536 required freight + passenger route miles as of 2020-12-29 per FRA. URWB is a Cisco-validated PTC architecture component, not the entire PTC stack.

ANSI/RIA R15.08-1-2020 defines safety requirements beyond R15.06 (which assumed stationary robots) and B56.5 (predetermined-guide-path AGVs). R15.08-1 does not specify wireless technology — it specifies safety functional requirements (E-stop reaction time, perception-system performance, mixed-traffic interaction with OSHA 29 CFR 1910.178 forklifts) that the wireless layer must support. URWB's sub-ms path-reconfiguration latency comfortably satisfies the safety-PLC watchdog window where 50 ms 802.11r FT puts the AGV offline 5 percent of the time at sustained 1 Hz roam rate. The wireless layer is necessary-but-not-sufficient; full R15.08-1 compliance is a system-integrator responsibility.

49 CFR Part 674 (FTA State Safety Oversight, replaced 49 CFR Part 659 in 2016, FTA Final Rule formatted 2024-11) requires every State with a rail fixed guideway public transportation system to have an SSO program approved by the Administrator. Wireless CBTC compliance rolls up through the SSOA-approved Public Transportation Agency Safety Plan (PTASP). IEEE 1474.1-2004 is the foundational CBTC functional requirements doc. URWB is a Cisco-validated CBTC architecture for subway / light rail train-to-wayside backhaul, complementing the indoor station Wi-Fi 7 estate that handles passenger-facing services.

From IOS-XE 17.18.1 onward, URWB is supported on Cisco Catalyst 9800 Wireless Controllers and Catalyst Center for provisioning — a beta feature in 17.18.1. The current TAC-recommended IOS-XE for URWB is the 17.18.x train with 17.18.2 specifically called out for the ISSU caveat resolution (the 17.15.1-17.15.4b and 17.18.1 ISSU caveat is resolved in 17.15.4d / 17.18.2). Reference the Cat 9800 17.18.x URWB configuration chapter and the TAC-recommended-builds page for current pinning. New deployments after 17.18 GA should target 17.18.2 minimum.

225 mph / 360 km/h. The figure is published consistently across the legacy FM3200 / FM3500 / FM4200 / FM4500 datasheets and inherited by the current IW9165 / IW9167 platforms after the 2024-07-26 Fluidmesh end-of-sale. Confidence is HIGH: it appears as a verbatim spec on multiple Cisco primary-source datasheets and is reaffirmed in the URWB Solution Overview. The 225 mph figure is the design envelope — meaning deployments engineered against it (notably high-speed rail and autonomous haul truck mining) operate within the window without protocol-level reassociation gaps. Operational practice pins to whichever is lower: 225 mph datasheet spec or the actual operational envelope of the asset (most warehouse AGVs run well under 25 mph).

URWB delivers make-before-break handoffs with path-reconfiguration latency in the order of one millisecond, and zero handoff time across cluster boundaries — engineered for high-velocity vehicles, AGVs, and rail (up to 225 mph / 360 km/h) where standard 802.11r fast-transition still incurs a reassociation gap. The sub-ms figure comes from the Cisco URWB Fluidity Specifications user manual (PDF) which states “in the order of one millisecond” and “as low as one millisecond” for path reconfiguration. The make-before-break mechanism is documented in the URWB Solution Overview as “99.995 percent availability, less than 10-ms latency, and zero packet loss with seamless handoffs.”

ePMP 4500 / 4500C / 4500L = 124 mph (200 km/h) survival, IP67, -30 to +55 °C per the ePMP 4500 datasheet (verbatim: “The device and its mounting bracket are capable of withstanding wind speeds of up to 200 kph (124 mph)”). PTP 670 = 200 mph (322 km/h) survival, IP66/67, -40 to +60 °C, 100 percent condensing humidity. PTP 700 = 200 mph survival, IP66/67, -40 to +60 °C, FIPS 140-2. PTP 700 is the strongest fixed-link wind-rating and the only Cambium option with FIPS 140-2 certification — relevant for federal / utility deployments on Tehachapi or Mojave ridgelines.

When the AGV / vehicle envelope stays under ~50 km/h sustained AND the handoff failure rate at 50 ms FT is acceptable to the safety case. Hardening 802.11r means: 802.11k Neighbor Reports + 802.11v BSS Transition Management hints + cached PMK-R1 keys + tightly-tuned cell sizing + minimum-rate filtering. For warehouse AGV cells running below 25 mph, that envelope hits 15-50 ms FT and is fully adequate. URWB's sub-ms figure is overkill in that scenario and adds the URWB SKU + IoT Operations Dashboard subscription cost. URWB earns its keep at higher speeds (50+ km/h) or when zero handoff time across cluster boundaries is contractually required (rail PTC, mass transit CBTC). The decision is operational envelope, not technology preference. See IEEE 802.11-2024.

It does not, technically. Indoor Wi-Fi 7 / Wi-Fi 6E and outdoor URWB are two different network underlays. The indoor mechanic tablet, scanner, and voice handset estate associates to standard 802.11 SSIDs terminating against the Catalyst 9800 / Aruba 9240 / Mist Edge controller. The AGV / vehicle / wayside endpoint carries a URWB radio (IW9165D / IW9165E) that joins the URWB Fluidity cluster. The bridge is the IW9165E / IW9167E simultaneous URWB and Wi-Fi AP modes on the same chassis (software-toggleable per radio, no separate firmware, no dual boot) — one outdoor pole-mount AP can serve both an URWB-linked AGV and an 802.11r-roaming mechanic tablet. Cisco IOS-XE 17.18.x on the Cat 9800 is the integration point. See the IW9165 Series datasheet.

Generally no. Sucuri WAF / CDN is a website-layer service that sits in front of the public-facing web application; it has no path through the OT-facing wireless control plane that runs the URWB Fluidity cluster. The exception is the IoT Operations Dashboard Industrial Wireless service tenant if that lives behind a public-facing web edge: in that case, standard WAF rules apply to the management portal, not to the URWB radio control plane. The URWB cluster itself terminates against the FM10000 G2 Gateway and the Cat 9800 / Catalyst Center management plane on private VRF / VLAN underlays per IETF RFC 7348 EVPN-VXLAN. WAF / CDN is the wrong toolbox for outdoor industrial wireless concerns.

Outdoor URWB / Rajant / Cambium / Aruba 387 deployments touch four service lines: enterprise wireless engineering (the indoor / outdoor handoff design and dual-mode IW9165E/9167E provisioning), warehouse network design (AGV / AMR fleet design for distribution centers and 3PL operations), aerospace and industrial Wi-Fi (hangar / MRO / flight-line / outdoor industrial), and independent validation testing (post-cutover acceptance against the URWB cluster's published spec). Engagement model is fixed-fee SOW; first call scopes the operating envelope (speed, environment, regulatory floor), the wireless platform shortlist, and the closeout deliverable map. Send floor plans and a brief operating-envelope description to /contact-us/.

Because it is the buying-decision answer, not a vendor knock. Cambium ePMP / cnWave / PTP and HPE Aruba AP-387 / AP-518 are fixed-link / fixed-mesh / outdoor-coverage products. Cambium PTP 670 is in many ways a stronger fixed-link than URWB on a static yard-to-building mast (200 mph wind survival, FIPS 140-2 on the 700, channel widths down to 5 MHz for spectrum efficiency). Cambium and Aruba simply do not publish a make-before-break / sub-ms / cluster-boundary-zero-handoff primitive comparable to Cisco URWB Prodigy 2.0 or Rajant InstaMesh peer-mobile mesh. Listing them on a comparison page that includes URWB and Rajant is valid only when the use case is fixed PtP / outdoor mesh / outdoor coverage. For high-mobility AGV, the shortlist is two vendors: Cisco URWB or Rajant Kinetic Mesh.

Per the Cisco URWB Former Fluidmesh Family End-of-Sale Bulletin, FM1000 Gateway, FM3200 Base, FM3500 Endo, FM4200 Mobi/Fiber, FM4500 Mobi/Fiber, and FM4800 reached last-day-to-order on 2024-07-26 with 3-year tech support thereafter. Replacement path: IW9165D + IW9167E + FM10000 Gen 2. Migration is firmware-train aware: Prodigy 1.0 (legacy Fluidmesh) and Prodigy 2.0 are not compatible. The cluster transitions are coordinated swaps — new IW9165 / IW9167 radios paired with FM10000 G2, then legacy Fluidmesh decommission. FM Racer (legacy Fluidmesh management) end-of-life'd 2024-08-30; the new management plane is Cisco IoT Operations Dashboard Industrial Wireless.

The Catalyst 9800 URWB integration is a feature of IOS-XE 17.18.1 as a beta feature, with TAC-recommended pinning at 17.18.2 minimum due to the 17.15.1-17.15.4b and 17.18.1 ISSU caveat (resolved in 17.15.4d / 17.18.2). The integration brings URWB Mobility / PtP / PtMP provisioning under the Cat 9800 controller that already manages the indoor Wi-Fi 7 / Wi-Fi 6E AP estate. Software train pinning per the Cat 9800 17.18.x URWB configuration chapter. New deployments should target 17.18.2 minimum; pre-17.18 deployments use the standalone URWB management path.

URWB total cost is driven by three line items: the radio SKU (IW9165D / IW9165E / IW9167E / IW9167EH-HZ), the FM10000 G2 Gateway aggregating the cluster (1+1 ATX redundant 300 W PSUs, up to 10 Gbps aggregate), and the IoT Operations Dashboard Industrial Wireless subscription (Essentials or Advantage tier, per-radio). Cambium PTP / ePMP / cnWave is mostly hardware cost — the radios and the dish; no per-radio cloud subscription on the standard PTP product. Rajant is hardware + InstaMesh license; no controller dependency reduces ongoing cost vs URWB. WiFi Hotshots quotes fixed-fee SOW with hardware, licensing, deployment labor, validation testing, and closeout deliverables priced in — not hourly T&M. Send AP / radio counts, site count, regulatory scope, and operational envelope to /contact-us/ for a comparable scoped quote.

Post-cutover acceptance maps eight specific deliverables to the URWB cluster's published spec: AGV speed-tolerance verification at the 225 mph datasheet figure (or the operational envelope, whichever is lower); handoff path-reconfiguration latency in the order of one millisecond per the Cisco URWB Fluidity Specs PDF; end-to-end latency under 10 ms; availability up to 99.995 percent; IEEE 802.3bt Type 4 outdoor PoE delivery under loaded draw; IW9167EH wind-survival and temperature-range envelope verification; NEC Class I Div 2 / ATEX Zone 2/22 hazloc passive-antenna inductance / capacitance limits validation; and Catalyst 9800 IOS-XE 17.18.x URWB integration acceptance. Deliverable is a vendor-neutral acceptance report mapping every pass / fail to the relevant primary spec — not a screenshot of the IoT Operations Dashboard's self-reported telemetry. See the independent validation testing service line.