Deployment Checklist
A successful IoT deployment requires careful planning. This checklist covers every phase.
Key Metrics
6 Phases
Complete Process
4-8 weeks
Timeline
$5-50
per Sensor/mo
90%+
On-Time
Why This Matters
Deployments Fail in the First 100 Meters
Most IoT projects do not fail because of the technology. They fail because of scope creep, network assumptions, and unclear ownership - problems that surface in the first weeks and compound for months. A phased rollout is the single most reliable protection: it limits the blast radius of any mistake, produces a demonstrable win early, and forces decisions to be made in order rather than all at once.
The checklist on this page organizes a deployment into six phases, from business case through scale-out. The structure reflects the way successful enterprise programs actually run: define the value, prove it on a pilot, then expand with the same discipline that made the pilot work.
Timelines below assume a single-site pilot. Multi-site portfolios add integration and rollout-management effort but follow the same sequence.
Phases
The Six-Phase Rollout
Confirm the business problem, the metric that defines success, and the systems already in place. No sensor is purchased before this is written down.
A small, instrumented zone - typically 10-30 sensors - proves data quality and value. Success criteria are defined before the POC starts.
A meaningful area (one floor, one building) runs the full stack: sensors, network, platform, alerts, and dashboards used by real operators.
Segmentation, certificates, and monitoring are applied for scale. The pilot network is treated as the production standard.
IoT data is joined with the BMS, metering, and analytics platforms. Alerts route to the right team with the right context.
Rollout to remaining sites, with documentation, training, and a savings-verification cadence that keeps the program funded.
Deep Dive
Phase by Phase: What Must Be True Before You Move On
Each phase has a small set of exit criteria. If a criterion is not met, the rollout should stop there rather than carry risk forward. These are the gate checks that experienced programs enforce.
| Phase | Exit Criteria | Typical Duration |
|---|---|---|
| Discovery | Signed-off business case with named sponsor and success metric | 1-2 weeks |
| Proof of Concept | Data quality confirmed; value hypothesis validated or rejected with evidence | 1-2 weeks |
| Pilot | Operators using dashboards daily; alerts triaged to the correct owner | 2-4 weeks |
| Network Hardening | Segmentation active, certificates issued, credentials removed | 1 week |
| Integration | IoT and BMS data reconcile; alert routing verified end to end | 1-2 weeks |
| Scale & Sustain | Rollout runbook documented; savings verified monthly for one quarter | Ongoing |
Deep Dive
Budgeting and Cost Models
IoT cost is best understood in three layers: hardware, connectivity, and platform. Hardware is a one-time capital cost; connectivity and platform are recurring. The dominant hidden cost in most budgets is not any single layer but the integration engineering required to make the data usable.
Recurring cost is usually quoted per sensor per month and varies with connectivity choice. Wi-Fi sensors ride on existing infrastructure but compete for bandwidth; LoRaWAN and cellular sensors bring their own spectrum but add gateway or SIM cost. Battery-powered devices add a battery-replacement schedule that becomes a real operating cost at portfolio scale.
Cost Drivers
What Drives the Budget
$25-150 per unit depending on type and enclosure
$50-300 per gateway plus $2-10 per sensor/month
$3-40 per sensor/month by feature tier
$40-120 per point for wireless; more for hardwired
Often 20-35% of total, the most underestimated line
Battery, firmware, and calibration ~5-10% of first-year cost annually
Best Practices
Pitfalls That Derail Rollouts
Network Assumptions
Never assume Wi-Fi coverage where the sensor will sit. Do a site survey and verify RSSI at each planned location before committing to wireless sensors.
Unclear Ownership
Name a single accountable owner per phase. "Everyone is responsible" is the most reliable predictor of a stalled deployment.
Skipping the POC
Going straight from proposal to full build guarantees that errors discovered at 30 sensors get repeated at 300.
No Data-Quality Gate
If the platform accepts bad data silently, every downstream alert and report inherits the corruption. Gate data quality at ingestion.
Integration Underestimation
Connecting the platform to the BMS, metering, and ticketing systems usually takes longer than the sensors themselves.
Unfunded Sustainability
Programs that fund deployment but not operations lose their savings within a year. Budget for the sustaining phase.
Final Pre-Launch Checklist
- Success metric is numeric, owned, and tied to a budget line
- Every sensor location verified for connectivity and mounting before installation day
- Alert ownership matrix published and acknowledged by each receiving team
- Rollback plan defined for every automated control change
Plan a Phased IoT Rollout
Get help structuring your deployment into phases with clear gates and defensible budgets.
Get Started