Solution design

The radio is a decision, not a default.

Most connectivity projects pick the radio the first vendor sold them. The right one follows from five questions a buyer can answer without us: where the asset is, whether it moves, how often it must speak, what powers it, and who should own the network.

The five questions
  1. 01 Where is the asset?
  2. 02 Does it move?
  3. 03 How often must it speak?
  4. 04 What powers it?
  5. 05 Who should own the network?
Answer them; the table does the rest.
The short version · the table below is the whole decision
02 · Does it move? yes CellularLTE · LTE-M no coverage Satellitethrough a bridge no 01 · Is there a wire where it is? yes Wired fieldbusModbus · BACnet · OPC UA no 04 · Battery powered? no Wi-FiHTTP or MQTT devices yes 05 · Your own land or site? yes LoRaWAN, privateyour gateways, no fee no 05 · NB-IoT coverage there? yes NB-IoTdeep indoors · battery no LoRaWAN, publican operator’s network · a fee
The decision tableLast column: what HOLOIN reads today, from holoin.ai’s live facts

How to read it.

Go across the five numbered columns with your asset in mind. A vehicle that leaves the site needs cellular. A sensor on a battery that reports twice an hour from your own land wants private LoRaWAN. A meter or controller already on a wire needs no radio at all — it needs a line that reads and never writes. Mixing is normal: a farm is LoRaWAN for probes and valves, cellular for the pickup, wire for the pump house.

Radio01 · Reach02 · Moves with the asset03 · How often · data per message04 · Power05 · Who owns the networkRunning costHOLOIN reads it today
Cellular
LTE · LTE-M
anywhere with coverageyeslarge · live positionsmains or vehiclethe carriera SIM per deviceyes · trackers through the bundled server
NB-IoT
cellular, low power
anywhere with coverage, deeper indoorspoorlysmall · infrequentbattery, yearsthe carriera SIM per device, cheaper plansyes · LwM2M through the bundled server
LoRaWAN
private
your site, kilometres per gatewaywithin the sitesmall · infrequentbattery, yearsyougateways once; no per-device feeyes · the bundled network server
LoRaWAN
public
where a public network existswithin its coveragesmall · infrequentbattery, yearsthe operatora fee per deviceyes · the operator forwards uplinks to an HTTP source (ChirpStack format, or a generic source with a field map)
Wired fieldbus
Modbus TCP · BACnet/IP · OPC UA · SNMP
inside the building or plantnocontinuousmainsyounone beyond the wiringyes · through the Field Agent, read-only
Wi-Fiinside a buildingwithin the sitelargemainsyounonethrough HTTP or MQTT devices
Satelliteanywhereyessmall · costlyvehicle or solarthe operatorhigh per messagethrough an HTTP or MQTT bridge; not a native source
Worked examplesSix operations, six fits

60 trucks on regional routes

Cellular trackers (one make or several) through the bundled server; a fuel sensor on the CAN bus where the tracker reads it.

Moving assets; positions every few seconds; vehicle power.

A 200-hectare farm, 24 zones

Private LoRaWAN: soil probes, valves and a weather station on one or two gateways; a flow meter on Modbus at the pump house.

Battery sensors, your own land, no per-device fee; the pump house is wired already.

A 12-floor office with a BMS

The Field Agent on the BACnet segment, reading the BMS’s own points, trend logs and schedules; LoRaWAN CO₂ sensors in rooms the BMS doesn’t see.

The building is wired; the gaps are battery sensors.

40 telecom sites, two hours apart

The generator controller and the rectifier over Modbus through a Field Agent at the site, uplinked by cellular; a fuel sensor on the tank.

Wired on site, nothing but cellular off site.

A 5 MW solar plant

SunSpec over Modbus TCP from the inverters and the meter through a Field Agent; the weather station the same way.

Everything is on the plant’s wire; read-only by design.

A depot with 30 chargers

The chargers’ own OCPP connection to HOLOIN; the site meter on Modbus.

OCPP is the charger’s radio; the meter is on the switchboard.

The device, once the radio is chosenRendered from holoin.ai’s facts · verified items only

Devices we have proved, by name.

HOLOIN’s hardware catalogue lists the device models an acceptance run has proved, each with its verification level; a model not on the list can still be read — it is a catalogue entry away. The list below is holoin.ai’s, read live from its facts, so this page never claims a device the product hasn’t shown.

Cellular trackers

A device model is listed here once an acceptance run has proved it.

LoRaWAN sensors and actuators

  • Decentlab DL-SHT35 air temperature and humidity sensor · verified (simulated)

Wired fieldbus (Modbus · BACnet · OPC UA · SNMP)

  • Invertek Optidrive E3 variable speed drive · verified (simulated)

OCPP charge points

A device model is listed here once an acceptance run has proved it.

● verified on hardware · ○ verified (simulated) · the pill text comes from site-facts.json, never typed here
Three questions we’ll ask youIn the session
  1. 01Which assets leave the site, and how often must they be heard?
  2. 02What already has a wire, and who owns it — IT, OT, or a vendor?
  3. 03Who should own the network in five years: you, a carrier, or an operator?

Next

Bring your sites. We’ll fill in the table together.

An assessment walks your assets through the five questions and ends with a radio, a device list and an order of work — yours to take anywhere. The first session is free.