Metal or liquids
Confirm tag construction, spacing and placement on RF-challenging products or assets.
Prove the read before committing
RFID site surveys, read-range testing and proof-of-concept trials
Reduce deployment risk by testing representative tags, products, movements and integration rules before final hardware and installation are specified.
UK-wide integrationRepresentative trialsHardware + middlewareMeasured acceptance
Quick answer
What is an RFID site survey?
An RFID site survey assesses the items, tag options, physical read zone, movement, radio environment and system interfaces for a proposed application. It is followed by controlled read tests or a pilot with representative items. The objective is to produce evidence for tag choice, antenna position, reader settings, event logic and measurable acceptance criteria before full deployment.
Technical content reviewed
Application overview
Replace assumptions with test evidence
Published read ranges are measured under particular conditions and cannot predict every factory, warehouse or product. Metal, liquids, packaging density, item orientation, cable loss, nearby tags and traffic flow can all change the result.
Oxford Traceability uses a staged discovery and trial process. The output is not simply a signal-strength reading: it is a practical design for the intended business event, including what should count as success, how exceptions are handled and what data must reach the customer system.
System scope
What an RFID survey and pilot can cover
- Process and movement mapping
- Representative tag and attachment trials
- Fixed, handheld and antenna read testing
- Portal, conveyor and workstation zone assessment
- Cross-read, missed-read and exception analysis
- Pilot acceptance criteria and rollout recommendations
Typical outcomes
When a survey is especially valuable
Dense populations
Test cases, totes, racks or pallets where tags can shield one another or change orientation.
Adjacent read zones
Measure cross-reads and define containment for neighbouring doors, conveyors or workstations.
System integration
Prove that reader observations become the correct PLC, WMS, ERP or MES transaction.
Decision guide
A practical RFID project pathway
Use this as a starting point. Final selection should be based on representative items, movement and the required business event.
| Stage | Main question | Typical evidence | Decision |
|---|---|---|---|
| Discovery | What business event must be captured? | Process map, items, volumes, constraints and target systems | Define scope and success criteria |
| Bench testing | Which tag and reader approach is viable? | Read results across representative items and orientations | Shortlist tags, antennas and reader type |
| On-site survey | How will the real environment affect the zone? | Mounting positions, RF risks, traffic, network and controls | Produce the installation concept |
| Pilot | Does the end-to-end workflow meet acceptance criteria? | Measured reads, exceptions, user feedback and system events | Approve, refine or stop before rollout |
| Rollout | How should the proven design scale? | Standard configuration, commissioning checks and support plan | Deploy repeatably across further points or sites |
Application engineering
Define success before testing begins
Oxford Traceability specifies the physical read and the resulting data flow as one working system.
01
Representative samples
The trial set should include normal variation in product, fill, packaging, tag position, orientation and movement.
02
Acceptance criteria
Agree required reads, prohibited cross-reads, response time, exception handling and data output before judging the pilot.
03
Repeatability
Testing should cover repeated passes and realistic traffic rather than relying on one successful demonstration read.
Frequently asked
RFID site survey questions
For an answer based on your items and process, speak directly with Oxford Traceability.
Ask an RFID specialistDo all RFID projects need a site survey?+
Simple handheld applications may only need representative tag trials. Automatic portals, tunnels, production stations and environments containing metal or liquids normally benefit from an on-site assessment.
What samples should we provide?+
Provide the actual items, packaging and tag positions where possible, including different sizes, fill levels, materials and orientations that occur in normal operation.
Can a survey confirm a guaranteed read range?+
It can establish a tested operating window for the agreed item and conditions. RFID performance changes with tags, materials, orientation and environment, so acceptance criteria should describe the complete application rather than one distance figure.
Can you test integration as part of a pilot?+
Yes. A useful pilot can pass validated events to a test database, API, PLC, WMS, ERP or MES endpoint so the physical read and business transaction are proven together.
What happens after the pilot?+
The results are used to finalise hardware, mounting, reader settings, filtering, interface requirements, commissioning tests and a controlled rollout plan.
Oxford Traceability
Turn your RFID requirement into a testable system.
Measure RFID success per movement, not per antenna read
An RFID reader may observe one stationary tag many times. That can produce a large read count without proving that every intended movement was captured. Before a pilot starts, define the unit of success: for example, one tagged tote crossing a nominated doorway in a specified direction and creating one accepted transaction.
Keep an independent record of the trial movements and compare it with the resulting business events. Include a tote that pauses in the zone, reverses direction or remains nearby while another item passes where those conditions are credible. The test should reveal missed movements, duplicate transactions and reads from items that were never meant to cross the boundary. Signal strength alone cannot settle those questions.
Report the number of movement opportunities and the exceptions, with the tested product, tag placement and route identified. This gives a more useful rollout decision than a total of successful antenna responses. It also separates a physical read problem from an event-filtering problem. Send the actual movement workflow and explain which transaction the receiving system must create when requesting an RFID site survey.
Can a high RFID read count conceal missed movements?
Yes. Repeated observations of the same tag can inflate raw reads without showing that every intended crossing produced the correct event.
What should an RFID portal pilot count?
Count independently known movement opportunities and reconcile them with accepted events, duplicates, misses and unintended cross-reads.
Convert reader observations into business events Plan an RFID portal read zone