Understand assets, hardware, sites, zones and gateways - OnSight Knowledgebase

Understand assets, hardware, sites, zones and gateways

Back to Onboarding Browse product

Understand the Command digital twin

OnSight Command models the parts of your operation that you want to observe. The relationships between sites, zones, gateways, assets and hardware give the incoming IoT data operational meaning.

Sites and zones

A site represents an operational location, such as a facility, warehouse, production area or customer location.

A zone is a meaningful area within that site. You draw its boundary on the map to define the places where you want Command to understand activity—for example, a storage room, production line, loading area or restricted location.

Gateways

A gateway collects or relays data from hardware into the OnSight platform. Gateways are normally associated with the zone they serve, helping you understand where device coverage and reported activity belong in the digital twin.

Assets

An asset is the real-world thing you want to track or monitor. It can represent equipment, a product, a person, a vehicle, a storage area or another operational entity.

Hardware and sensors

Hardware is the physical IoT device associated with an asset. In most cases, one asset is tracked or monitored by one piece of hardware.

An asset can also have multiple hardware devices when you need to capture a range of sensor information from the same real-world item. For example, one asset may have separate devices or sensor streams for temperature, humidity, battery, location or another operational measurement.

A sensor is the part of the hardware that produces a measurement. Command standardises the incoming sensor data so it can be monitored, alerted on and analysed alongside other data in the system.

How the model works together

  1. Create a site and the zones that describe its operational areas.
  2. Associate gateways with the zones they serve.
  3. Create the assets you want to track or monitor.
  4. Associate the relevant hardware—and, where needed, multiple hardware devices—with each asset.
  5. Use the resulting data in Map, Status, Dashboards, Alerts and Reports.

This model lets Command continuously compare incoming data with the operational context and rules your team has defined.

More in this category

Related guides for this topic.

Need a hand?

Tell us which product you use, what you’re trying to do, and what happened.

Contact support