Mining
The classification question, the site split and the energy programme.
Configurations
One catalogue, six operating environments — what actually changes
Every buyer draws from the same catalogue. What separates a mining specification from a hotel specification is the order the questions are asked in — and in four of the six environments below, one constraint overrides that order entirely.
An operations manager and a procurement officer can look at the same catalogue and reach different specifications without either of them being wrong. The difference is not the hardware. It is the order the questions get asked in: a mining site settles whether any part of the operation is classified before it looks at anything else, and a hotel settles what the device looks like in a lobby before it looks at ingress protection. This note sets out that ranking for six operating environments, and names the one constraint that overrides it in each.
What this note does not do
This note explains how the decision is made. It does not quote a specification for a particular site, a quantity or a coverage result, 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
- Find the environment that matches the operation, not the industry label the buyer works under.
- Read the constraint column first. Where it applies, it removes builds before the ranking gets a chance to matter.
- Send the operating environment and the destination country together — the ranking is only meaningful against both.
What changes is the ranking, not the catalogue
This catalogue records the same identifiers for every buyer. Nothing about a portable changes because it is being bought for a hotel rather than a mine. What changes is which recording in that catalogue is the deciding one — the same two-build decision that is a detail on one site is the whole specification on another.
| Environment | Ranked first | The constraint that overrides it |
|---|---|---|
| Oil and gas | Hazardous-area listed portables as the default handset rather than as an exception, and listed energy items ordered against that build. | Permit-to-work rules and hazardous-area approvals are site-specific. The listed variant a site accepts is decided by that site, not by the supplier. |
| Mining | Non-display portables where the operator wears gloves, and higher-capacity energy items as standard rather than as an upgrade. | Where the operation is classified, the listed-variant requirement overrides every other selection preference. |
| Security and guarding | Simple portables that need minimal operator training, and one battery format across the fleet. | Some sites require encryption or recording beyond the standard build. Confirm it before ordering rather than after. |
| Logistics and ports | Vehicle mobiles for yard and terminal equipment, portables with one charging discipline per shift, and coverage extension for steel-heavy areas. | Terminal access rules may restrict which bands are permitted on site, independently of what your own licence covers. |
| Hospitality and events | Slim portables where the device is seen by guests, and a channel plan that temporary staff can learn within a shift. | Event venues often operate on temporary spectrum permissions rather than on the operator's own authorisation. |
| Public safety and government | The family the programme standard requires, and a documentation pack prepared for tender submission. | Programme specifications and type-approval requirements are set by the awarding authority. This site asserts compliance with no specific tender. |
In four of the six, one constraint decides more than the ranking does
An admission constraint is not a preference you can trade against
Where a site is classified, or an awarding authority has fixed a standard, or a terminal restricts a band, that constraint sits outside the transaction. It is not a feature to be weighed against cost or delivery; it removes options before the weighing starts. And in each of those cases the party who decides is not the supplier.
Confirm the constraint with the party that owns it before the ordering code is fixed, not after the quotation is issued.No client names are published here
These are configuration logics, not delivered projects. Naming a client would require their permission and a verifiable delivery record, and neither is published on this site. Ask for references directly, and expect them to be checked — a reference that cannot survive being checked is worth less than no reference at all.
Not covered here
- A specification for your site. The ranking narrows the questions; the answers are site-specific.
- Quantity, headcount ratios or a spare percentage for any environment.
- Coverage across a yard, a pit, a tunnel or a building. Each is a survey question rather than a catalogue one.
- A certification number, a type-approval reference or a permit condition.
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.
- Which of the six environments the operation most resembles, and where it differs from that pattern.
- Whether any part of the site is classified, and under which zone.
- Who owns the frequency authorisation on your side, and whether it is already held.
- Whether equipment is audited per unit by the client, which changes what has to be recorded.
Questions this note answers
Both, and the stricter one wins where they conflict. A guarding contract at a classified plant takes the classification constraint and the guarding logic together — the constraint decides what may be supplied, and the guarding logic decides how it is configured.
Only through a constraint, never through preference. Preference picks between builds that are all admissible; a constraint removes builds outright. Ask which of the two is doing the work before narrowing anything.
Because the configuration logic still holds — a programme fixes its standard before it chooses a supplier, and knowing that changes the order enquiries are handled in. What this site does not do is claim compliance with any particular programme or authority.
No. The environment sets the order the questions are asked in; the answers come from your site, your regulator and your forwarder. A specification produced from the environment alone is a template, not a specification.
Where to go from here
Logistics and ports
Fleet sizing from the working pattern, and how a channel plan is built.
Hospitality and events
Why a guest-facing build is ranked differently from an industrial one.
Security and guarding
Turnover, one battery format and the encryption question.
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 markets worldwide, 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.