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
  • Pilot deployments
  • Live deployments

Was this helpful?

Export as PDF
  1. Site Planning
  2. Planning guidelines

Deployments stages

Validate the scalability of the Silvanet System using a Pilot deployment followed by a full-scale Live deployment.

PreviousPlanning guidelinesNextScout deployment locations

Last updated 4 months ago

Was this helpful?

Deploying a Silvanet Network in a forest is typically a two-stage process:

  • Pilot (2 - 4 months): Small-scale deployment of up to 400 sensors that demonstrates Silvanet's scalability and Mesh Network to detect controlled test fires.

  • Live (10-15 years): Large-scale deployment of the required Wildfire Sensors and Mesh/Border Gateways across a targeted forest area (the Site).

Pilot deployments

A Pilot deployment validates Silvanet System's core functionality and scalability. This type of deployment typically monitors an area of about 400 to 500 hectares (approximately 1000 acres to 1250 acres).

This deployment typically has a duration of approximately 2-4 months.

Use the to determine the required number of Wildfire Sensors, Border Gateways and Mesh Gateways.

  • 400 Wildfire Sensors Garden wire can be used to temporarily mount the Wildfire Sensors to trees. Sensor spacing should be from 80m to 100m.

  • Four to eight Mesh Gateways For an area of 400 to 500 hectares, deploy at least four up to eight Mesh Gateways, depending on the terrain and RF signal propagation conditions (line-of-sight).

  • Topology and forest density determines number of Mesh Gateways Hilly areas need more Mesh Gateways. Less dense and relatively level forest floors need less Mesh Gateways where 4 should be sufficient.

  • One Border Gateway Only one Border Gateway is typically needed. Additional Border Gateways can be added for redundancy.

Typical deployment schedule

To deploy 400 sensors and Gateways, a team of 2 people can deploy 20 to 50 devices a day.

However, this depends entirely on the difficulty of the terrain and state of the forest floor. In general, deployment is achieved quicker when more teams are available to deploy the devices.

Live deployments

A Live deployment can use the results of a Pilot deployment (but not necessarily) to determine the number of sensors and gateways needed to effectively cover the entire Site.

This has a deployment duration of 10-15 years.

  • Site dimensions The size of the Site in hectares determines the number and type of Silvanet devices to effectively cover the Site area.

  • Topology and forest density determines number of Mesh Gateways Mesh Gateways require line-of-sight between other Mesh Gateways. Hills, ravines and other aspects of the topology may interfere with line-of-sight. Mounting Mesh Gateways higher than the recommended 3 meters or even mounting them on a hill may increase line-of-sight.

  • Effect of interactions on sensor calibrations Emissions from vehicles on lanes and roadways may interfere with Wildfire Sensor calibrations. Similarly, human interactions with the devices can be reduced by placing them away from roadways and hiking trails.

  • Device ratios Use the follow (maximum) device ratios:

    • Ratio of Wildfire Sensors to Mesh Gateways is 100 to 1.

    • Ratio of Mesh Gateways to Border Gateways is 20 to 1.

  • Wildfire Sensor density Distances between Wildfire Sensors is based on human activity and the Wildlife Urban Interface:

    • For areas of high human activity, distances between Wildfire Sensors should be no further than 100 meters between devices.

    • For areas of low human activity, distances between Wildfire Sensors can be increased to 400 meters to 500 meters between devices.

  • Prepare installation plans Consider how the deployment teams must traverse the forest so they can efficiently use the time. With such a large deployment area, several teams of two workers may be required to deploy all the sensors. Ensure you prepare one site Packet per team, considering how the team must navigate through the forest.

Use the to determine the required number of Wildfire Sensors, Border Gateways and Mesh Gateways. Use treenails to permanently attach the sensors to trees.

Planning Tool
Planning Tool
Pilot deployment