Tutorial - Pre-planning a Site
Learn how to use the Pre-Planning tool to plan density and locations of Wildfire Sensors, Mesh Gateways and Border Gateways and to ensure Gateway connectivity .
Last updated
Learn how to use the Pre-Planning tool to plan density and locations of Wildfire Sensors, Mesh Gateways and Border Gateways and to ensure Gateway connectivity .
Last updated
Docs Version
Version 4.2Sales Enquiry
Contact Dryad Sales© 2024, Dryad Networks GmbH, Eisenbahnstr. 37, 16225 Eberswalde, Germany
In this section, we prepare a set of Packets using the Pre-Planning tool. The Site chosen has paths, railways, road and other structures nearby that demonstrate a typical WUI (Wildland Urban Interface). This is an area where wildland (forests and meadows) intersect with urban areas.
The Site also has areas that are typically inaccessible to most people and may require hiking through forests with Silvanet devices and tools to deploy the devices.
If you have already prepared part of your Site Pre-Planning, open the <filename.dryad> Pre-planning fire to continue or to modify the plan.
Find the Site location where you plan on deploying gateways and sensors.
Open the Pre-planning tool
Use the Search field to find the deployment location for the Silvanet Gateways and Sensors.
Save your project.
Paths are typically areas that require a higher density of sensors. Examples of paths in the Pre-Planning tool include hiking paths, lanes and roadways, rail lines, power lines or other linear areas that have a higher level of human activity than a forested area.
The cumulative number of sensors planned for all paths are included in the Sensor count.
Use the Draw Path tool to define the density of sensors along elements of the Site expected to have human use, such as hiking paths, roadways and power lines.
Select the Draw Path tool.
Using the tool, begin the path by selecting a start point, then drag the path along the route and then double-click on the map to end the path. The GPS locations of the sensors in the path are automatically generated and saved.
Enter details in the Path Settings panel:
Name: Enter a descriptive name.
Path type: Select from Hiking Path, Road, Railway, Power Line or Other.
Protection Level: Use the slider to determine sensor density (Low, Mid, High). The distance between sensors affects the amount of sensors deployed. The higher the protection level, the shorter the distance between sensors.
Save your project.
If required, you can add sensors at specific points. Select Manual Planning, then select Add Sensor.
Save your project.
Add or remove sensors You can move, rename or delete a sensor. For details, see Pre-Planning tool.
Switching to Terrain view shows the topology of the path and how it may affect message transmissions to/from the sensors.
Switching to Map view highlights the urban and forested/park areas of the paths.
Areas are large segments of the Site where a lower density of sensors are expected. They are usually areas of low human activity or almost no human activity. This can be areas typically off-limits to human activity, remote areas, or forested areas that may have pathways running through them.
A deployment Site can have multiple areas defined for easier planning.
The cumulative number of sensors planned for all areas are included in the sensor count.
Use the Draw Area tool to define lower sensor density areas of the Site. It also can be used to define inaccessible areas within the define Site geometry.
Select the Draw Area tool.
Using the tool, begin the area by selecting a start point, then drag the path along the boundary of the area and then double-click on the map to complete the area. The GPS locations of the sensors in the area are automatically generated and saved.
Enter details in the Path Settings panel:
Name: Enter a descriptive name.
Surface area: This is automatically generated.
Accessible: Select this option of the area is accessible to humans. If it is inaccessible (such as private property, military area, restricted area) then no sensors can be deployed in the defined area.
Protection Level: Use the slider to determine sensor density (Low, Mid, High). The distance between sensors affects the amount of sensors deployed. The higher the protection level, the shorter the distance between sensors.
Save your project.
Select Draw Area tool and using the same procedure define a second area.
Save your project.
If any areas are not accessible, use the Draw Area tool to define this area. In this case, slide the Accessible selector off. The area then is defined without sensors.
Save your project.
Add or remove sensors You can move, rename or delete a sensor. For details, see Pre-Planning tool.
After planning paths and areas, the sensors need connectivity to one or more Border Gateways.
You 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.
When a Border Gateway or Mesh Gateway is added to the Pre-Planning map, the line-of-sight of the gateway is shown as a blue area. You may notice broken areas in the blue area. This is due to topology that prevents signals from reaching those areas. These areas require Mesh Gateways.
Next, add Mesh Gateways to the Pre-Planning map. They must be added within existing blue areas which allows the Mesh Gateways to connect with existing gateways. Add sufficient Mesh Gateways until you have achieved 90% to 100% coverage of the Site.
Use the Plan Connectivity tool to ensure the sensors have connectivity to the Silvanet Mesh Network and to the Border Gateway.
Select the Plan Connectivity tool.
Use the tool and place a Border Gateway on the map. If no gateways have been added, the initial gateway is defined as a Border Gateway. The GPS location of the Border Gateway is automatically generated and saved.
Save your project.
Use the Plan Connectivity tool to add a Mesh Gateway. Ensure you add it within the blue zone of the Border Gateway. This way the Mesh Gateway has connectivity to the Border Gateway.
Save your project.
Continue added more Mesh Gateways until the Site has sufficient network coverage, as shown in the green bar.
Save your project.
Select 3D View to rotate the site. This reveals areas that may not be covered by sensors or other deployment issues, such as steep hills that may be difficult to traverse.
Comments can be added to the Pre-Planning tool for use during deployment.
When you are satisfied with the deployment plan, you can then generate the Packets for use by the Silvanet Deployment app.
Select Release Deployment Plan.
If the application identifies issues with the planned locations of sensors and gateways (such as sensors not connected to gateways), it prevents the generation of the Packets before the issues are corrected. Go through the list of issues and correct them.
For example, move an unconnected sensor within the blue zone of a Mesh Gateway to resolve one of the issues.
Notice the sensor sitting within an unconnected area. This sensor can be moved a few meters to be within a connected area.
With all issues resolved, the Deployment Plan is ready to be released. Select Release Plan to generate the Packets.
Save your project, then select Quit to close the Pre-Planning tool.
Later if you need to modify the plan, open the project file and make any required changes.
In the latest release of the Pre-Planning tool, we have provided a Export Summary function. For details, see Planning Summary Export in Pre-planning tool.
