Is Your Manufacturing Site Ready for a Private Network Survey? A Complete Domain-by-Domain Readiness Guide
A 20-question, six-domain diagnostic — physical environment, power and backhaul, OT integration, spectrum and compliance, and survey logistics — surfaces the gaps that turn a routine RF survey into a wasted site visit or a mid-deployment respecification
Commissioning an RF survey before a manufacturing site is genuinely ready is one of the more expensive sequencing mistakes in private network deployment — not because the survey itself is flawed, but because the gaps it uncovers on-site (missing site drawings, unassessed power availability, undefined OT segmentation, unengaged ATEX classification) are exactly the gaps that should have been resolved before the survey team was ever booked. TeckNexus has launched a Private Network Site Survey Readiness Checklist for manufacturing, a 20-question diagnostic across six domains that generates a manufacturing-specific checklist, required documents list, and field validation sequence before a formal survey is commissioned.
Site profile: AGV handover and ATEX classification set the technical baseline
The checklist opens with six context questions establishing site type — factory floor, warehouse and distribution centre, mixed production and warehouse, multi-building campus, or outdoor yard — deployment stage, and in-scope use cases, before asking two questions specific to manufacturing risk. Whether AGVs, AMRs or collaborative robots are live today on Wi-Fi, planned within twelve months, or still under evaluation matters because AGV and cobot connectivity requires seamless handover across the full vehicle route — widely regarded as the most demanding RF design requirement in manufacturing environments, and one that has to be confirmed before survey design, not discovered during it.
The second manufacturing-specific question addresses ATEX/IECEx classified zones, hazardous process areas, or washdown environments. This matters because Ex-rated radio equipment is a genuinely different product category from standard industrial radios, not a variant with a higher rating. Sites with hazardous areas that haven’t been formally classified are flagged as a direct blocker: ATEX zone maps must be produced before radio equipment can even be specified, making zone classification a pre-survey requirement rather than a parallel workstream.
Domain A — Physical environment: where coverage failures actually originate
The physical environment domain treats construction materials, ceiling heights, dynamic obstructions and environmental conditions as the primary input to RF design — gaps here are what lead to coverage failures discovered only after deployment, when they’re far more expensive to fix. Accurate site maps or CAD drawings, validated against field reality, are required for RF propagation modelling; surveys that proceed on manual field measurement alone carry materially higher design risk than those with validated drawings in hand.
RF propagation environment is scored on a spectrum from open — minimal obstructions, standard ceiling height, good line-of-sight — through mixed, dense industrial (significant metal machinery, high racking, reinforced concrete), to extreme environments with Faraday-like enclosed production cells. Dynamic obstructions add a layer static surveys routinely underestimate: moving forklifts, AGVs and trucks create different coverage variability than large moving machinery like cranes, robotic arms or overhead gantries — and sites with both are flagged as needing the most conservative design margin. Known interference sources — dense existing Wi-Fi, variable-frequency drives, welders, induction heating, TETRA systems, adjacent radar — round out the domain, with “unknown, not yet assessed” treated as its own answer requiring resolution before design.
Domain B — Power and backhaul: the most common deployment blocker
Power and backhaul availability at each planned radio location is identified as one of the most common deployment blockers in manufacturing specifically. Mains power within 5 metres of all planned locations sits at one end; multiple locations with no nearby power source at the other — and the gap between them determines whether additional civil work is required, which directly affects both timeline and cost. Backhaul follows the same logic: fibre or Ethernet within 20 metres of every planned location is the target state, but in dense factory environments, running new cable is often the longest-lead civil works item on the entire programme. Sites with significant backhaul gaps may need wireless backhaul designed in from the outset rather than treated as a fallback. Existing infrastructure that can be reused or integrated — Wi-Fi access points, fibre backbone, TETRA systems, DAS — is captured separately, since integration strategy changes materially depending on what’s already in place versus what’s being built from scratch.
Domain C — OT systems and devices: the most consistent source of project delay
OT integration is named directly as the most consistent source of manufacturing private network project delays. Confirming which systems need to connect — SCADA/DCS and historians, PLCs and field devices running PROFINET, EtherNet/IP or Modbus, MES/ERP integration, video management systems, or safety instrumented systems — determines whether the design needs OT network segmentation, protocol bridging, or specialist integration work, and that determination has to happen before survey rather than during it.
Device count and inventory status matter independently of OT system type: a documented inventory of device types, quantities and locations changes the design conversation entirely compared to an estimated count with no formal inventory, regardless of whether that count is under 100 or over 2,000 devices. And performance requirements — latency, throughput, availability, handover — need to be defined for the most demanding use case specifically, because AGV handover, machine vision and safety-critical applications each carry distinct performance requirements that must be defined before RF design begins, not negotiated once a vendor is already on-site.
Domain D — Spectrum and compliance: what shapes vendor selection before vendors are engaged
Spectrum status ranges from already-secured licensed spectrum with band and geography confirmed, through CBRS with SAS registration not yet initiated, to spectrum options not yet evaluated at all — and this status directly determines which radio technology can realistically be deployed on the intended timeline. Compliance and security standards — IEC 62443, ISO 27001, NIS2, GDPR for video and personnel data, sector-specific regulation for defence supply chain, automotive or aerospace work — are treated as determining security architecture requirements before vendor engagement, not as a checklist to work through after a vendor has already been selected.
Domain E — Survey logistics and stakeholder approvals: what actually wastes a site visit
The final domain addresses what causes most wasted survey visits in practice: site access not arranged, safety inductions not completed, or internal stakeholder approvals not yet secured. These are logistics failures rather than technical gaps, but the checklist treats them with equal weight, because a technically well-prepared site still produces a wasted visit if the survey team can’t actually get access to the areas requiring coverage on the day they arrive.
From readiness diagnosis to field-ready checklist
The output translates all five domains into what a deployment partner actually needs before mobilising: a manufacturing-specific site survey checklist, a required documents list, and a field validation sequence — sequenced so that AGV handover requirements, ATEX classification, OT segmentation and stakeholder access are resolved before the RF survey team is commissioned, rather than surfacing as blockers once they’re already on-site.
Manufacturing engineering, OT/IT teams and facilities leads planning a private network deployment can take the free, vendor-neutral readiness checklist directly and receive a complete readiness report across all six domains.
Related Tool: AI Use Case Prioritiser (Manufacturing)
Once site readiness is confirmed, prioritise which manufacturing AI use cases — AGV coordination, machine vision, predictive maintenance — to deploy first based on operational impact and feasibility.
