Public Sector and Municipalities
A radio specification has to describe an outcome, not a shopping list. The clauses that decide whether the delivered system works are the coverage acceptance criterion, the party responsible for licensing, programming as a deliverable, and service terms with response times.
A radio tender that lists model numbers and quantities will receive quotations for model numbers and quantities. The delivered result is a stack of radios, and everything that turns radios into a working system — coverage, licensing, programming, training, service — is out of scope because nobody put it in.
The specification is the only place these can be secured.
Before writing anything technical, establish and record:
This is the analysis a bidder cannot do for you, and its absence is the root of most of what follows.
Scope and purpose. What the system is for and which sites it serves.
Coverage requirement. Areas by name, with the acceptance criterion. Treated below because it decides everything.
Technology. Analogue, DMR, DMR Tier III, TETRA or PoC — stated with a reason, and consistently. A specification that asks for TETRA features at a DMR price will receive offers that satisfy neither.
Device requirements by class and quantity, written as properties rather than brands.
Infrastructure — repeaters, antennas, feeders, power, backup, linking between sites.
Software — dispatch, recording, device management, position reporting, with licences and their duration.
Licensing — who applies, who pays, by when.
Programming — the channel plan as a deliverable.
Training — audiences, duration, materials.
Documentation — as-built drawings, coverage report, codeplug files, manuals.
Warranty and service — response times, spares, repair route.
Acceptance testing — how the system is proved before payment.
Properties, with numbers and standards:
Each line should be there because the operation needs it. Copied specifications contain requirements nobody can justify, and those either exclude good offers or get waived, which undermines the rest.
This is the clause that determines whether the tender was worth writing.
> The Contractor shall provide portable-to-repeater coverage in all areas listed in Annex A. Coverage shall be verified by measurement at not fewer than five points per area at 1.5 m above floor level, with received signal level not less than −100 dBm and voice quality not less than DAQ 3.4. At least 95 percent of measured points shall pass. Testing shall be witnessed by the Employer and the results submitted as a coverage report forming part of the acceptance documentation.
Every element closes a specific dispute: which areas, what threshold, how measured, how many points, what passing means, and what is handed over. Add the conditions under which testing occurs — a warehouse tested empty is not the warehouse — and name the areas exhaustively, including basements, lift cars, stairwells and plant rooms.
Without this clause, "the coverage is inadequate" and "the coverage meets the specification" are both unfalsifiable, and the argument is settled by whoever has more stamina.
Say who applies for the frequency assignment, who pays the fees, and by when. Licensing in Türkiye is a per-organisation, per-site process through the BTK, and coordination is frequently the longest item in the schedule.
Specifications that omit it produce a familiar outcome: equipment delivered, installed, and unable to transmit lawfully, with both parties having assumed the other was handling it.
Programming is not a formality; it is where the system either matches how people work or does not.
Require: a channel plan document agreed before delivery, programming of all devices including spares, the master codeplug handed over in editable form, and one free reprogramming round after a settling-in period. Reasoning in how to build a channel plan.
Training should name its audiences — users, supervisors, the control room — with duration, and require written materials that stay on site: a channel list, a quick reference, an emergency procedure. Training delivered as a talk on handover day has evaporated by the time the first new starter arrives.
State: warranty duration for devices, batteries and infrastructure separately, because they differ. Response time for a fault, distinguishing infrastructure from handsets. Whether spare devices are held on site and how many. The repair route and expected turnaround. Availability of parts for a stated number of years.
For hazardous-area equipment, add that repairs must preserve the certification — an ATEX radio repaired outside an authorised process is no longer certified.
Lowest price is defensible only when compliance is defined tightly enough that a system which will not work cannot be compliant.
That means coverage, service response, programming, training and licensing are mandatory requirements, not scored extras. Offers either satisfy them or are non-compliant. Price then competes between offers that would each actually deliver a working system, which is what the process was supposed to achieve.
Where scoring is used, weight service capability and coverage methodology, and require a named local service capability with parts — because a two-week repair turnaround is a cost that never appears in the bid price.
A specification that answers all nine takes longer to write and removes the failure mode that costs the entire budget a second time.
Public procurement rules generally require technical criteria rather than brand names, with equivalence permitted. That is workable: write the properties that matter — band, channel spacing, IP and drop rating, battery capacity in mAh and hours at a stated duty cycle, encryption type — and any compliant product can be offered against them.
The coverage acceptance criterion. Everything else can be inspected on delivery; coverage cannot be argued about afterwards unless the contract said what would be measured, where, how and what counts as passing. Its absence is why so many delivered systems are described as working by the supplier and not working by the user.
Whoever the contract names — and it must name someone. Licensing takes real time and is often the critical path. Specifications that leave it unstated produce a delivered system that legally cannot transmit, with each party reasonably believing it was the other's job.
Lowest compliant price only works if compliance is defined tightly enough that a non-working system cannot be compliant. In practice that means coverage, service response, programming and training are all mandatory requirements rather than scored extras, so price competes between offers that would each actually work.
The Hytera product range, TechnoRF engineering, installation, maintenance, technical service and business continuity planning — brought together into a system designed for how your operation actually works.
We deliver not only what you need, but more than you expect .
