Buying a Radio System From a China-Based Supplier: What Remote Support Can and Cannot Do
A supplier abroad can design the system, programme the radios and join your commissioning call. It cannot walk your site, pull cable or sign your acceptance sheet. Projects go wrong when that line is discovered after the order rather than written into it. Here is the split, and the wording that makes it stick.
| Specification | Who does it.. | How it is.. |
|---|---|---|
| Task | Who does it | How it is evidenced |
| Requirement analysis and quantity planning | Supplier, remotely | Written configuration proposal with the reasoning per quantity |
| System architecture | Supplier, remotely | Connection diagram showing what talks to what, optional items marked |
| BOM and quotation | Supplier | Itemised lines with model, quantity, configuration and terms |
| Programming and pre-configuration | Supplier, before dispatch | Codeplug loaded to your plan; scope stated in the order |
| Export documents and shipping | Supplier | Commercial invoice, HS code, DDP or DAP terms as agreed |
| RF survey and coverage measurement | Customer locally | Test plan agreed in advance; results recorded per location |
| Physical installation and cabling | Customer locally | Installer sign-off; supplier supports remotely |
| Final acceptance and coverage sign-off | Customer locally | Acceptance record per the agreed criteria |
| Frequency licence | Customer locally | Assignment held by the operator, not the supplier |
Remote Support
The value a supplier abroad can add is concentrated in the part that travels well over a network: configuration. Selecting models against a site description, working out quantities, drawing the architecture, building an itemised BOM, programming talk groups and emergency behaviour, and then sitting on a call while your technician powers the system up - all of that is location-independent. What does not travel is physical presence. Nobody can measure a building they are not in, and a design that has not been measured is an assumption. Suppliers who blur this line are not necessarily dishonest; they are answering the question they were asked, which is usually 'can you supply the system', not 'who signs for coverage'. The buyer's protection is to ask the second question explicitly and put the answer in the order.
Scope Boundary
Make the split contractual rather than conversational. Three sentences do most of the work: the supplier is responsible for design, equipment, programming to the supplied frequency plan and remote support during commissioning; the customer is responsible for the on-site survey, installation, the frequency licence and acceptance; coverage is confirmed by measurement on site against criteria agreed before installation. Add what happens if a location fails - who re-tests, in what timeframe, and what the supplier's obligation is (design review, reprogramming, additional hardware at agreed terms) rather than a vague commitment to 'support'. Then ask for the deliverables in a form you can keep: the BOM as a spreadsheet, the codeplug file, the architecture drawing, and the programming notes. A project you can hand to a different technician next year is the real return on buying carefully.
Data Source: Scope boundary as published on /systems and /about: remote planning, supply, programming and support; local survey, installation, licensing and acceptance. No supplier performance claims are made.
Fleet Pricing & Lead Time
Send your model list and quantities — pricing, stock and DAP/DDP terms within one working day.
