Coverage estimation
Use the Planning tool to quickly generate a rapid and precise coverage estimation of a Site.
Last updated
Was this helpful?
Use the Planning tool to quickly generate a rapid and precise coverage estimation of a Site.
Last updated
Was this helpful?
The Planning tool provides a set of tools for rapidly estimating the number of Wildfire Sensors and Silvanet Gateways needed to provide fire-detection coverage for a Site.
For a given deployment area, you use the Planning tool to first create areas of high and low density of Silvanet Wildfire Sensors.
High density areas are called Paths which are areas of high human use such as hiking paths or valuable assets such as power lines.
For more information, see Sensor density guidelines.
After planning the areas of Sensor density, the Sensors need to be connected to the Silvanet Mesh Network. Connectivity begins by placing a Border Gateway at the appropriate location on the map. Afterwards, place Mesh Gateways throughout the Sensor deployment areas.
For more information, see Border Gateway guidelines and Mesh Gateway guidelines.
When completed, the result is an estimation of the number of Wildfire Sensors, Border Gateways and Mesh Gateways.
You then export a summary of the coverage estimate, then send a resulting set of Packages to the Deployment app.
Save your work regularly
While working on the Planning project, save your progress regularly to a local drive on your computer or to a network drive. If you quit or refresh the page, your progress will not be saved.
From the Site Dashboard select Planning from the Ellipsis dropdown menu to open the Planning tool.
Planning tool file
A Planning tool file is saved as <Descriptive Name - Site #.dryad>, where<Site #> is the Site Id which is shown in the breadcrumb of the Site Management app. You can use a more descriptive file name but it must use the .dryad extension.
The main menu provides access to saving and opening planning projects.
Open: Access saved Planning work on a local or network drive.
Save: Save and store your progress locally.
Export to CSV: Export device coordinates to a CSV file.
Help: Links to an the Planning tool tutorial.
Quit: Closes the Planning tool.
Save your work
Any work is lost if you do not save your work before closing.
The Toolbar provides access to the tools for estimating coverage requirements.
Select: Use to select paths, areas or Gateways on the map.
Draw path: Use the Path tool to define high-density deployment areas such as hiking paths, rail lines, power lines.
Draw area: Use the Area tool to define lower density deployment areas such as forested areas.
Plan connectivity: Use the Connectivity tool to define the number and placement of Border Gateways and Mesh Gateways to build up a successful Mesh Network in the Site.
Comments: Use the Comment tool to add relevant comments to the plan.
You can view the Site in Terrain view, Map view, 3D view and Fire risk view.
Terrain view shows the topology of the path and how it may affect message transmissions to/from the sensors. Select the Terrain icon at the lower-left edge of the map.
Selecting the Fire Risk icon displays an overlay that indicates areas of high to low risk of fires.
Select the 3D View icon to show a 3D map of the Site. It shows areas that may cause connectivity issues such as hills and valleys. It also may show areas that are challenging for deployments such as steep hills that may be difficult to traverse.
The Planning tool allows for externally prepared Reference files to be imported as a starting point.
You can import KML, KMZ and Shapefiles as a geographical reference.
Shapefiles must be uploaded as a .zip file bundle containing all required components (.shp, .shx, .dbf, etc.).
Open the Planning tool.
Select + next to Reference field label.
From a local or remote folder, import a prepared reference file. It can be a .kmz, .kml, or Shapefile.
The Planning tool imports the paths, areas and pins from the reference file.
Make the required modifications, such as paths, area and connectivity zones.
Save the Planning tool file.
Paths are typically areas that require a higher density of sensors. For example, this can include hiking paths, lanes and roadways, rail lines, power lines or other linear areas that have a high level of human activity.
Start path: Start creating a new path by selecting a location on the map where you want the path to start.
End path: End the path by double-clicking on the map where you want the path to end.
Add settings: See Path settings below for details.
Save the project.
Remember to save the project frequently.
The Path settings are accessed by selecting a path.
Name: Give the path a descriptive name.
Path type: Choose a path presets which influence the placement and amount of sensors on the path:
Hiking path
Road
Railway
Power line
Path length: Length of path in Imperial or Metric, depending on app settings. See User preferences.
Protection Level: Set based on the path type. It can be adjusted. Low level of protection is 100m between each sensor. High level is 20m between each sensor.
Distance between sensors: Distance set by Prediction Level slider. A precise value can be entered here, as required.
Amount of sensors: Set by Prediction Level slider based on the length of the path and density. A precise number of sensors can be entered, as required.
Any path can be modified after it has been added and saved to the project file. Two types of dots are used that follow the route of the path:
White dots: Key points in the path that alter segments of the path. They can be deleted to straighten a path in that segment.
Yellow dots: Mid-points between white dots. Selecting a yellow dot converts them into white dots which adds other mid-point yellow dots.
Select a path from the list of paths to open the Edit Path panel, then select the Pencil icon.
Change basic settings, as required:
Name: Update the path name.
Path type: Choose from Hiking Path, Road, Railway, Power LIne.
Protection level: Modify the Protection level using the slider or manually change the distance between Wildfire Sensors and amount of Sensors.
Make path changes, as required
Change the route of the path: Drag a white dot to move a section of a path.
Add an angle: Select a yellow dot and drag it to a new location to add an angle to the path.
Remove a path dot: Remove a path dot by selecting a white dot and press Delete or Backspace.
Delete a path: When a path is active, select the Trash icon to delete a path.
Select any location on the map to deselect the path.
Save the project.
Areas are large segments of the Site where a lower density of Wildfire Sensors are expected. They are usually areas of low (or lower) human activity or even no human activity. For example, they can be areas off-limits to human activity, remote areas or forested areas that may have pathways running through them. They
Start area: Start creating a new area by clicking on the map where you want the area to start and continue drawing the outline of the area.
End area: End the area by double-clicking on the map where you want the area to end.
Add settings: See Area settings below.
Save the project.
Select an area to access the Area Settings panel.
Name: Give the area a descriptive name.
Surface covered: Automatically generated.
Accessible: The slider defines the area as accessible or inaccessible. Making the area inaccessible prevents any sensors or gateways placed in this area. For example, it can be used to indicate areas which are physically or legally not accessible for your deployment.
Protection Level: Default settings is Mid level (200 m between sensors). Use the slider to adjust sensor density. Low density is 500 m between each sensor, while high density is 100 m between each sensor.
Distance between sensors: Setting is based on the Protection Level slider. It can be set manually.
After making an area, you can alter the dimensions of the area through the use of the perimeter dots. Two types of dots make up the perimeter:
White dots: Key points in the perimeter that can be moved to change the dimensions of the area. They can be deleted to reduce the area dimension.
Yellow dots: Mid-points between white dots. Selecting a yellow dot converts them into white dots which adds other mid-point yellow dots.
Expanding the Area moves the sensors as well. It may also add sensors to accommodate the increased size of the area. Ensure the sensors are placed correctly (not over structures, in open spaces, etc.).
Select an area from the list of defined areas to open the Edit Area panel, then select the Pencil icon.
Change basic settings, as required:
Name: Update the area name.
Change the accessible type: When selected, it removes all Sensor icons as no Sensors can be deployed in the area.
Change protection level: Modify the Protection level using the slider or manually change the distance between Wildfire Sensors and amount of Sensors.
Make area changes, as required:
Change a perimeter: Select a a white dot, then drag it to add an angle to the perimeter. New midpoints are also created.
Delete an angle in the perimeter: Select a white dot, then press Delete or Backspace to remove the angle.
Delete a dot: Select a dot, then press Delete or Backspace to remove the dot.
Delete an area: Select the Trash icon to delete a area.
Click anywhere on the map to deselect the area.
Save the project.
Use the Plan Connectivity tool to add Border Gateways and Mesh Gateways to the Site. When adding a Gateway, the Planning tool creates a connectivity zone identified by an irregular blue pattern on the map. This zone shows the range of the Gateway based on several factors including:
Site topology
Expected range of the gateway
Installation height
Areas outside the blue zone do not have direct Line of Sight to the Gateway.
First add a Border Gateway to ensure connectivity to the Internet. Find a location that is at the edge of a forest and, ideally, has access to a mains power supply. Then you add the Mesh Gateways to build up a Silvanet Mesh Network.
Place your first gateway by clicking on the map at the desired location. If you already know where your Border Gateway should be placed, start by placing your first gateway at this location.
Ensure at least one Border Gateway per mesh network. If you create a site with several Border gateways, account for them manually.
Select Connectivity Mesh, then select Add Gateways. A Gateway icon appears on the map.
Place Gateway on the Map where you plan on locating it (based on requirements).
In the Edit Gateway form, set properties:
Name: Identify the Gateway with a name.
Gateway Type: Options include Border Gateway, Mesh Gateway. Choose Border Gateway
Installation Height: Options include 3m Standard, 5m Pole, 10m Tower
Network: Options include Unknown/TBD, Cellular, Satellite
Power Type: Options include Unknown/TBD, Solar, POE
Location: Latitude and Longitude is set automatically based on where the Gateway was placed on the map.
Save the project.
Extend Mesh Network coverage by placing Mesh Gateways within the blue zone (connectivity zone) of an existing Gateway.
Select Connectivity Mesh, then select Add Gateways. A Gateway icon appears on the map.
Place Gateway on the Map where you plan on locating it (based on requirements).
In the Edit Gateway form, set properties:
Name: Identify the Gateway with a name.
Gateway Type: Options include Border Gateway, Mesh Gateway. Choose Mesh Gateway
Installation Height: Options include 3m Standard, 5m Pole, 10m Tower
Location: Latitude and Longitude is set automatically based on where the Gateway was placed on the map.
Add additional Mesh Gateways as required.
Save the project.
To build a resilient mesh network, we advise that each gateway should be in line of sight with at least 2 other gateways, when possible.
After placing the Border and Mesh Gateways on the map, the Planning tool estimates the network coverage. When reaches a high enough coverage percentage, it is indicated by a Sufficient Coverage message.
Connectivity threshold - 95%
When connectivity reaches 95%, this is considered a threshold for acceptable coverage in a Site.
After a path or area has been drawn, a sensor may have been placed in a location free of trees or perhaps in a location where a sensor cannot be deployed, such as on a building.
Wildfire Sensors can be added to areas or paths.
Any customization of an area or path overwrites the default placement of sensors.
Select an Area or a Path.
From the Edit Path panel, select the Manually Planning tab.
Select Add Sensor.
Drag the Sensor to the required location, then click to place the Sensor icon.
A red icon indicates the sensor is outside the zone of the selected path or area.
Save the project.
The name and location of a Sensor can be changed.
In an area or path, select a Wildfire Sensor.
In the Edit Sensor dialog, enter a descriptive name in the Name field.
Save the project.
In an area or path, select a Wildfire Sensor.
Using the mouse, move a Sensor to update the latitude and longitude settings of the sensor. This may be required if a Sensor is placed outside a Connectivity zone.
Save the project.
In an area or path, select a Wildfire Sensor.
In the Edit Sensor dialog, select Delete Sensor. This cannot be undone.
Save the project.
The Comments tool allows users to include additional information about the deployment or any other relevant topic. They can be added anywhere on the map.
Add comment: Select Comment and then click anywhere on the map to add a comment. Remember to save the project.
Deleted comment: Select a comment icon. Erase the text in the Comment field to delete the comment item, then save the project.
The Device Counter keeps track in real time of all Border Gateways, Mesh Gateways and Sensors placed on the Site.
Once you have created all the paths and areas you wish to protect and have placed gateways to ensure sufficient mesh network coverage, the estimated number of Gateways and Wildfire Sensors are shown.
Estimation uses
This estimation can be used for quoting purposes. However, the Export Summary feature includes a detailed list of devices and their deployment locations.
After planning the coverage, you are ready for deployment:
Export Summary document: Export your plan which appears as a set of devices with their planned deployment locations.
Release Deployment Plan When finished, release the deployment plan. Any issues that need to be resolved before release are identified. After resolving these issues, the plan becomes available in the Deployment app.
After completing the Site plan, you can export a Planning Summary document as either a .docx file or a CSV file.
Selecting Site overview document (.docx) generates an editable .docx file that includes an overview of site planning, details of the connectivity network and a comprehensive view of each planned packet. It also provides an estimate of the deployment time.
After selecting Confirm, the Planning tool builds the .docx and/or CSV file and generates a .zip file that can be saved on a local or remote drive.
Dryad recommends opening the .docx file in Word, OpenOffice or GoogleDocs and exporting it as a PDF file.
Releasing the Deployment Plan exports the coverage estimate to the Silvanet Cloud which loads it into the Deployment app as well as the Device overview section of the Sites view.
However, before it can be released, the Planning tool analyzes the plan and ensures the plan does not have any connectivity issues. If any issues are detected, they need to be resolved before continuing.
For example, a Sensor may have been located outside a connectivity zone, which means it is not connected to the Mesh Network. Move the Sensor within a connectivity zone.
Warning icon
A warning icon is displayed next to the Package containing the issue.
After resolving the issues, the Deployment Plan is ready to be released.
After releasing the Deployment Plan, the Packages appear in the Deployment app.
Try the Planning tool tutorial to practice what you have learned in this section.
See also
To try out the Planning tool, see Planning tool tutorial.
