A tender asking for “supply, installation and commissioning of an RFID system at the main gate” will attract bids. It will not attract comparable ones. One bidder quotes a two-antenna lane; another quotes four antennas, an outdoor enclosure and three years of maintenance; a third quotes a different band. The committee then spends weeks normalising offers that were never for the same scope.
An RFID tender specification in India rarely fails because the technology is exotic. It fails because the BOQ is written as a wish rather than a bill of quantities. Whether the requirement goes out as a GeM bid or a departmental tender, the discipline is the same: the document has to describe what is being bought precisely enough that two honest bidders arrive at comparable numbers.
Live RFID-related tenders in India come out steadily from ports, railways, defence establishments, state transport bodies, municipal corporations, universities and libraries, alongside larger reported programmes in tolling and railway safety. Most of these documents are drafted by people who buy RFID once every few years — which is exactly why the same avoidable clauses keep recurring.
This is drafting guidance from a manufacturer’s side of the table, not legal or procurement advice — and for any live procurement, the document on the issuing portal is the only authority on scope, value, earnest money and dates.
Why bids come back incomparable
Scope stated as an outcome, not a bill of quantities. “RFID system for four gates” leaves every quantity to the bidder’s imagination, and the cheapest imagination wins.
A copy-pasted model number. One vendor’s part number either makes the tender effectively single-source, or forces everyone else to file a “deviation” — and deviations cannot be scored against each other.
No measurable acceptance criterion. If the document never defines what “working” means, nothing is enforceable at commissioning.
Split the BOQ properly
There is no single mandated RFID BOQ format, but a workable one gives each head its own quantity, unit and rate columns:
- Tags and consumables — by type and substrate, not “RFID tags — 5,000 nos.”
- Readers — fixed, handheld, desktop or integrated, with port count per unit
- Antennas and RF cable — gain, polarisation, cable type and run length per position
- Infrastructure — poles, gantries, mounts, PoE switches, UPS, enclosures, earthing and surge protection, conduit and civil work
- Software — server and client licences, with integration and API work as a separate line
- Services — site survey, installation, commissioning, training, documentation
- AMC — priced year by year as separate lines, not folded into capital cost
Add a repeat-order rate for consumable tags. A programme can sit stalled for want of an agreed tag replenishment rate long after the hardware itself is working.
Specify performance, not part numbers
A performance line states what is read, in what population, at what speed or distance, and to what success rate. For example: each lane shall read a windshield tag at up to a stated vehicle speed across the full lane width, at a stated success rate over a stated number of passes, without reading the adjacent lane. That is testable; “read range 10 metres” is not, because range depends on tag, substrate, orientation, reader power and the site itself.
The equivalence clause — always cleared by your own legal cell before it goes in — usually runs along these lines: where a make and model is referenced it is indicative only, to establish a performance benchmark; equivalent or superior equipment is acceptable provided the bidder submits a clause-by-clause compliance statement against the parameters at the annexure, supported by the OEM datasheet, with equivalence judged against those parameters and not against the referenced model. It only works if the annexure actually holds parameters. Against a bare model number, “equivalent” means nothing.
The tag lines
An evaluable tag line states the protocol and band (for India, EPC Gen2 / ISO 18000-63 in the 865–867 MHz range), the memory needed, housing material, dimensions, mounting method and — critically — the substrate the tag sits on. A tag on steel behaves nothing like the same tag on a carton. Add read performance on that substrate at a defined reader power, antenna gain and orientation; IP rating and temperature range; survivability (wash cycles, UV, solvents, impact, vibration); encoding and marking; and sample approval before bulk supply. Ask for the datasheet against every line rather than accepting a headline number. Our guide to scoping read range against the real environment covers the physics a spec has to respect.
Reader and antenna lines
Specify port count; band and protocol; RF output power range, configurable within the limit permitted in India; network interfaces (Ethernet, PoE, serial); GPIO count where a barrier or sensor must be driven; whether an SDK is required; enclosure IP rating, temperature range and mounting; and the power source, including whether the position is UPS-backed.
For antennas, state gain, polarisation, beam width and mounting height, and make bidders declare cable type and run length: a long coaxial run can cost several dB that the reader has to make up. Outdoor positions need surge protection and earthing as named lines rather than assumptions. The reader selection guide and gate reader page explain these trade-offs.
Compliance lines, worded without over-claiming
Radiating equipment sits under more than one regime, and they are not interchangeable. A UHF reader or antenna transmits, so equipment type approval for the band it operates in — in India, the domain of the wireless planning wing — is usually the first question. Telecom equipment certification applies to categories of equipment that have actually been notified under that scheme. BIS registration or certification likewise applies where the product category has been notified. Applicability depends on the specific device and on the notifications in force at the time, so verify the current position with the relevant authority rather than with a page like this one.
Draft accordingly: require the approvals applicable to the equipment actually offered, valid as on the bid due date, plus confirmation that the reader operates within the 865–867 MHz range permitted in India. Naming a certificate that does not apply to the device class invites irrelevant paper and can disqualify an otherwise compliant offer. Our BIS and WPC compliance guide explains the distinctions in more detail.
Software, integration and data ownership
The clauses most often missing, and the ones that hurt at renewal:
- Data ownership and exit — data belongs to the buyer, exportable in an open format at any time, with the schema documented.
- API access — documented, with sample code, at no additional charge.
- Named integrations — the actual system and protocol: SIP2 or NCIP for a library system, the specific ERP, HRMS or TOS otherwise, and who provides the endpoint.
- Licence model — perpetual or subscription, per user or per reader, and what happens when AMC lapses.
- Bespoke development — source code or escrow, or the right to engage a third party after AMC.
- Hosting — on-premise or cloud, where data resides, backup and restore, audit logs, role-based access.
Site survey, acceptance testing and AMC
Make the survey contractual: a post-award, pre-despatch survey reporting RF environment, interference, mounting points and power and network availability, approved before material ships. Allow a pre-bid site visit so bidders price reality rather than a floor plan.
Acceptance testing is where the performance lines earn their place: define the test cases, tag population, number of passes, pass criteria and who signs, then tie a payment milestone to it. For AMC, state the warranty period first, then price each year separately with response and resolution times, preventive maintenance visits, spares availability, an uptime commitment and a written definition of downtime.
Worked BOQ shapes
| Application | Separate BOQ heads | Performance line to nail | Common trap |
|---|---|---|---|
| Gate or tolling lane | Reader, antennas, gantry, RF cable, PoE switch, UPS, barrier or camera interface, windshield tags, lane software, civil | Moving tag read at a stated speed across the full lane width, no cross-reads from the next lane | Cross-lane suppression unspecified; barrier interface left “as required” |
| Trackside or rolling stock | On-metal tags rated for the surface and vibration, mounting hardware, fixed and handheld readers, encoding | Retention on steel, plus read at a stated speed and offset | Tag spec with no substrate; no line for encoding or asset-register mapping |
| Armoury or kote | On-metal tags sized to the item, rack or door readers, handheld for verification, tamper interface, issue-return software with roles and audit trail | Complete read of a full rack within a stated time, over stated cycles, with no misses | Free-air read range quoted for dense metal packed in a rack |
| Library | Item tags by media type, staff station, self-issue kiosk, security gate, shelf-audit handheld, LMS integration, tagging labour | Gate detection rate for a stated stack carried through; shelf-audit throughput | LMS and protocol unnamed; tagging labour omitted |
| Port gate | Outdoor-rated readers and antennas, gantry, surge protection and earthing, vehicle or container tags, TOS or weighbridge integration, UPS, redundancy | Read at lane speed across a stated temperature and rainfall envelope, at a stated IP rating | No environmental envelope, no owner named for integration, no redundancy |
The weapon tracking, defence logistics and library automation pages show how these deployments are usually built.
Where Identium fits, stated plainly
We manufacture RFID hardware in New Delhi and supply public sector buyers — Indian Railways and a Government of Tamil Nadu infant-monitoring deployment among them — so read this section as disclosure rather than neutral advice. Identium Tech Solutions is BIS certified, our UHF readers and antennas are WPC-approved for India’s 865–867 MHz band, every unit is tested in-house, and an SDK with source code ships with each reader. We do not hold CE, FCC, RoHS, REACH or ISO 9001 and do not claim them, and we make no claim to be empanelled, rate-contracted or L1 anywhere.
If you are a consultant or technical cell fixing parameters, the proper route to vendor input is the pre-bid queries mechanism, where the answer reaches every bidder. A parameter set that several manufacturers can meet is what produces comparable bids.
General drafting guidance only, not legal or procurement advice. Regulatory applicability depends on the device and on the notifications in force, and must be verified with the relevant authority; any live procurement is governed solely by its own tender document.
Drafting a specification? Talk to us about what a comparable-bid parameter set looks like for your site.