Logistics and ports configuration
The full configuration logic for yards, terminals and fleet operations.
Logistics and ports
How many radios does a logistics fleet need, and how do you plan the channels?
Fleet size is not headcount. It follows from concurrent positions, shift overlap and charging — and the channel plan follows from who has to reach whom, not from the size of the yard.
The configuration reference for this environment is specific about where the difficulty sits: coverage spans large yards with steel structures, and handovers happen between shifts rather than between people. Both facts push against the intuitive approach of ordering one radio per employee.
What this note does not do
This note explains how the decision is made. It does not quote a quantity, a coverage result or a channel count for a named facility, because the site does not hold one it can evidence. Anything shown as unconfirmed on the catalogue pages is unconfirmed here too.
Confirm the position with your regulator, your site authority or your freight forwarder before you commit to an order.How to use this note
- Count concurrent positions, not headcount — that gives the working baseline.
- Build the channel plan as access groups, then read the recorded capacities against it.
- Send the position list and the shift pattern.
Sizing the fleet from positions, not people
| Input | Why it changes the number | How to state it |
|---|---|---|
| Concurrent positions | The real demand is how many people are working and reachable at the same moment, not how many are employed. | Count positions on your busiest shift. |
| Shift overlap | At handover two shifts are on the radio at once. That peak, not the average, sizes the fleet. | State the overlap period and how many positions it contains. |
| Charging arrangement | Radios charging cannot be carried. If charging is centralised, charging time is out of service time. | State where charging happens and whether it can be done during a shift. |
| Breakage and loss rate | A yard is a handling environment. A fleet sized exactly to the peak has no headroom. | State whether the figure you need is an operating fleet or a delivered quantity. |
| Vehicles versus people | A vehicle mobile is fitted, not carried, so a vehicle is not a person for sizing purposes. | Split the list into fixed positions and roaming positions. |
| Contractors and visitors | Temporary users are a channel-plan question more often than a hardware question. | State whether contractors need to be reachable on the same system. |
Building the channel plan
The plan is built from who must reach whom, then split so that unrelated traffic does not occupy the same channel. It is not built from the size of the yard. This ordering matters, because a plan built from geography produces channels nobody can use.
- List the access groups: yard operations, gatehouse, drivers, maintenance, supervision, emergency.
- Decide which of those must talk to each other directly, and merge the ones that always do.
- Give emergency and control their own channel and make sure it cannot be occupied by routine traffic.
- Add the plan to the enquiry. Programming is a separate line item and is done per fleet.
What capacity this catalogue records
Capacities recorded here are between five and several thousand, and the differences follow the family rather than the price band. Very large recorded figures are system capacities, not conventional channel counts, and are recorded as such on the identifier pages.
| Recorded channel capacity | Identifiers |
|---|---|
| 1000 | 25 |
| 3000 | 16 |
| 16 | 12 |
| 64 | 12 |
| 512 | 9 |
| 32 | 8 |
| 1000 (standard); 3000 (Enhancement Level 2) | 7 |
| 255 | 7 |
| TETRA network group/folder management (not a conventional channel count) | 7 |
| 870 | 6 |
| 99 | 6 |
| 1200 | 5 |
| 1250 | 5 |
| 512 (standard); 1000 (extended) | 5 |
| 1000 (standard); 3000 (extended) | 4 |
| 128 | 4 |
| 512 (standard); 1000 (Enhancement Level 1) | 4 |
| Fixed channel count not stated in the supplied configuration data | 4 |
| 160 | 3 |
| 96 (standard); 1200 (Enhanced Zone Bank) | 3 |
| MPT system capacity (not a fixed conventional channel count) | 3 |
| TMO 2048 talkgroups; DMO 1024 talkgroups | 3 |
| 16 (DM1400) /160 (DM1600, firmware-dependent) | 2 |
| 16 (GP340Ex) / 255 (GP380Ex) | 2 |
| 256 | 2 |
| Official documentation does not confirm a fixed value | 2 |
| 10 | 1 |
| 100 | 1 |
| 16 (conventional channels; exact capacity depends on the system configuration) | 1 |
| 5 | 1 |
| 6 | 1 |
| 8 | 1 |
| 96 | 1 |
| Source not confirmed — request verification | 1 |
| System-dependent (Motorola official specification: system-dependent) | 1 |
Terminal access rules are a separate constraint
Terminal and port authorities may restrict which bands are permitted on site, and that restriction is independent of what your own licence covers. Confirm it before specifying a band rather than after the order is placed.
Steel and coverage
Large yards with steel structures and stacked containers are the case where handheld-to-handheld reach is least predictable, and where the coverage answer is least likely to be a handset answer. The configuration reference lists coverage extension for steel-heavy areas as part of the standard logic. Whether it is needed on your site is a survey finding.
Not covered here
- A quantity for a named facility, or a spare percentage to apply.
- Coverage across a specific yard, with its particular steel and container density.
- Any statement that a particular band is permitted at a particular terminal.
What to put in the first message
Every one of these removes a round trip. The enquiry page composes a brief containing them; you send it from your own mail or messaging app.
- Destination country — this decides the approved variant and the marking.
- The frequency range you are licensed to use, in MHz.
- Quantity per site, and whether spares are included in that number.
- Operating environment, if it is classified (hazardous area, mine, tunnel).
- Whether the units must arrive programmed, and if so the channel plan.
- Positions per shift, and the peak count during the handover overlap.
- Roaming positions versus fixed positions such as gatehouses.
- Where radios will be charged, and whether charging happens within the shift.
- The access groups you need, and who must reach whom.
- Whether terminal access rules restrict the band you may bring on site.
Questions this note answers
It usually overshoots. The demand is concurrent reachable positions, so the peak overlap shift is the figure to work from, plus whatever headroom your loss and breakage rate justifies.
By test, not by yard size. Steel density and container stacking change the answer far more than the measured area does. Treat it as a survey item and leave room for it in the budget rather than assuming it away.
Usually, as extra users on the existing plan rather than extra channels. Whether they need to be on your system at all is a commercial and security decision before it is a technical one.
Not automatically. If the requirement is voice within access groups, analog may serve. The point at which digital earns its place is when individual calling, text or location is actually needed — see the analog or digital note.
Where to go from here
Vehicles and mobiles
In-vehicle units for fixed positions in the fleet, with recorded parameters.
Battery Finder
Look up recorded energy items by model, or run the reverse lookup by part number.
Buyer notes are written from the catalogue and the published reference pages. They carry no parameter the site cannot evidence, and an unconfirmed value stays unconfirmed here too. BaltiGo is a trading and distribution company supplying Motorola two-way radio hardware into Saudi Arabia and the wider GCC, and does not claim to be a Motorola authorised dealer or official distributor.
Enquiry
Send the configuration, not just the model name
Band, destination and quantity decide whether a quotation is usable in one round or three. Compose the brief and it carries all three.