Skip to content

Site Management app - Site Management view

Site Management view is where you prepare Site Packets and manage the Site post-deployment.


The Site Management View is the main access point to a Site's details. It provides access to the status of deployed devices. It includes an embedded Map. It also provides access to the Packet Planning page for building and managing Packet sets.

User role

  • Standard
  • Admin

Access to the Site Management View is from the Sites View, from which you select a Site.

Device View

The default view of a Site is now the Device View. It shows at a glance the status of all Active and Inactive deployed devices in a Site.

Site Management View - Device View

Site Management View - Device View

Device Status View

Expanding the device shows the current status of a device. As the devices are autonomously monitored and the device overview provides you with precise troubleshooting guides in case of issues.

Site Management View - Device Status View

Site Management View - Device Status View

Embedded Map and 3D View

The Site Management View has an embedded map that includes all the features of Map View, including 3D View. This allows you to easily navigate around the Site and get an overview of the Site's terrain. Using the Map tools you can expand the Map, toggle on/off the 3D Map View and Fire Risk View, and more.

Site Management View - Embedded Map

Site Management View - Embedded Map

Packet Planning page

The Packet Planning page is used to prepare a Deployment Packet which is a plan for deploying Silvanet devices at defined locations.

For example, for a Site consisting of one Border Gateway, five Mesh Gateways and 400 sensors, a good "rule-of-thumb" is to prepare one Packet for the Mesh and Border Gateways and sixteen Packets for sensors where each Packet includes 25 sensors. If the topology of the site is expected to have significant hills, cliffs or other challenging areas, then prepare Packets with less sensors, but no more than 25.

Gateway Packets

The following shows a Packet for Gateways containing a single Border Gateway and two Mesh Gateways, whose location has been defined and provided with GPS coordinates for deployment.

Border Gateway Packet

Gateway Packet

Sensor Packets

The following shows three sensor Packets of 25 sensors each, with each sensor provided with a GPS deployment location.

Sensor Packets

Sensor Packets

Of course, any number of Packets can be prepared sensor deployments, but we recommend adding no more than 25 sensors per Packet as this allows for a single day's deployment effort.

Consider topology when determining number of sensor per Packet

Typically, a Packet for sensors can have from 15 to 25 sensors, depending on the Site topology. Knowing in advance the Site topology through visiting the site and the density and range of sensors helps you plan for and prepare sensor Packets.