Dryad Silvanet Documentation
Get StartedExplore SilvanetPlan a SiteDeploy SilvanetFAQ
  • Dryad Silvanet Documentation
  • Tutorials
    • Get started tutorial (Gen 2)
    • Get started tutorial (Gen 3)
    • Planning tool tutorial
  • Silvanet Suite
    • Explore Silvanet
    • Silvanet Suite (Gen 2)
      • Silvanet Wildfire Sensor (Gen 2)
      • Silvanet Mesh Gateway (Gen 2)
      • Silvanet Border Gateway (Gen 2)
    • Silvanet Suite (Gen 3)
      • Silvanet Wildfire Sensor (Gen 3)
      • Silvanet Mesh Gateway (Gen 3)
      • Silvanet Border Gateway (Gen 3)
    • Silvanet Cloud Platform
    • Silvanet Mesh Network
    • Site Management App
      • User access
      • Dashboard
      • Sites view
      • Site details
        • Device overview
        • Wildfire Sensor data
        • Device info tabs
      • Map view
      • Alert center
      • User Management view
      • User preferences
    • Deployment App
    • Fire detection
  • Site Planning
    • Plan Sites
    • Planning guidelines
      • Deployments stages
      • Scout deployment locations
      • Gateway ratios
      • Gateway ranges
      • Sensor ratios
      • Sensor range
      • Sensor density
    • Coverage planning
      • Planning tool
      • Import KML, KMZ and Shapefiles
      • High density paths
      • Low density areas
      • Connectivity zones
      • Add or move Sensors
      • Export plan
    • Packet editor
  • Silvanet Deployment
    • Deploy Silvanet
    • Deployment guidelines
      • Deployment preparation
      • Border Gateway guidelines
      • Border Gateway scenarios
      • Mesh Gateway guidelines
      • Wildfire Sensor guidelines
    • Deploy Border Gateways (Gen 2/3)
      • Register Border Gateway
      • Mount Border Gateway (Gen 2)
      • Mount Border Gateway (Gen 3)
      • Border Gateway Connectivity Test
    • Deploy Mesh Gateways (Gen 2/3)
      • Register Mesh Gateway
      • Mount Mesh Gateway (Gen 2)
      • Mount Mesh Gateway (Gen 3)
      • Mesh Gateway Connectivity Test
    • Deploy Wildfire Sensors
      • Register Wildfire Sensors
      • Mount Wildfire Sensors
      • Sensor Calibration
      • Sensor normalization
    • Relocate a Silvanet Sensor or Gateway
  • Silvanet API
    • Silvanet API - MQTT Sensor Data Integration
    • Silvanet API - Webhook Integration
  • Silvanet Test Fires
    • Overview
    • Test fire preparation
    • Run test fires
    • Modify fire setups
  • Resources
    • Contact Technical Support
    • Release Notes
    • FAQs
      • General Questions
      • Border Gateway FAQs
      • Mesh Gateway FAQs
      • Wildfire Sensor FAQs
      • Site Management FAQs
      • User Management FAQs
    • Glossary of Terms
    • Status icons
    • Device troubleshooting
    • Firmware updates (FUOTA)
    • Declaration of Conformity (EU)
  • Chandler Burning Index (CBI)
Powered by GitBook

Docs Version

  • Version 4.6.4

Sales Enquiry

  • Contact Dryad Sales

Dryad

  • Dryad.net

© 2025, Dryad Networks GmbH, Eisenbahnstr. 37, 16225 Eberswalde, Germany

On this page
  • Completed plan
  • Device counter
  • Completed coverage estimate
  • Export summary
  • Release deployment plan

Was this helpful?

Export as PDF
  1. Site Planning
  2. Coverage planning

Export plan

After building the deployment plan, export it as a document and release it to the Deployment app.

PreviousAdd or move SensorsNextPacket editor

Last updated 2 months ago

Was this helpful?

Completed plan

When completed, the result is an estimation of the number of Wildfire Sensors, Border Gateways and Mesh Gateways.

Device counter

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

Completed coverage estimate

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.

Export summary

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.

Release deployment plan

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.

This estimation can be used for quoting purposes. However, the feature includes a detailed list of devices and their deployment locations.

Releasing the Deployment Plan exports the coverage estimate to the Silvanet Cloud which loads it into the Deployment app as well as the section of the Sites view.

After releasing the Deployment Plan, the Packages appear in the .

Device overview
Deployment app
Add comment to plan
Export summary document
Issues detected
No issues found
Export Summary