INSIGHTS • IoT • PROJECT DELIVERY
Planning an IoT Deployment: What Should You Consider Before Installation Starts?
A practical guide to the connectivity, infrastructure, data and project considerations that should be addressed before an IoT deployment begins.
Fortiva Projects
21 September 2026
9 min read
Introduction
An IoT deployment can appear relatively straightforward: install the devices, connect them to a network and begin collecting data.
In practice, successfully deploying connected technology across a building or estate involves much more than the devices themselves.
Connectivity, power, network infrastructure, device locations, data platforms, integrations and ongoing support all need to work together. A device that performs perfectly during a trial may behave very differently when hundreds of units are deployed across multiple operational sites.
The physical environment can also have a significant impact. Building construction, network coverage, mounting locations, access restrictions and existing infrastructure can all influence how the solution needs to be designed and delivered.
Understanding these requirements before installation begins can significantly reduce connectivity problems, additional works and deployment delays later in the project.
THE KEY POINT
A successful IoT deployment starts with understanding the operational requirement and the environment in which the technology needs to work — not simply selecting the devices.
ARTICLE CONTENTS
In this Guide
01
02
03
Define What the IoT Solution Needs to Achieve
Understand the Site and Existing Infrastructure
Choose the Right Connectivity
04
05
Consider Power and Device Locations
Plan the Network and Data Architecture
06
Understand the Platform and Integrations
07
Plan Installation and Deployment at Scale
08
09
Agree Testing and Data Validation Requirements
Documentation, Support and Handover
01
Define What the IoT Solution Needs to Achieve
Before selecting devices or designing the deployment, establish exactly what the technology is expected to achieve.
IoT projects should ideally begin with the operational requirement rather than the technology itself.
The objective may be to understand visitor numbers, monitor occupancy, measure environmental conditions, track assets, monitor equipment or provide information that supports wider building operations.
The required outcome will influence the type of device, frequency of data collection, connectivity method and platform requirements.
It is also important to establish how the data will actually be used. Collecting large quantities of information provides little value if the organisation does not have a clear way of interpreting or acting upon it.
Consider:
Business and operational objectives
Information or measurements required
Required level of accuracy
Frequency of data collection
Real-time or historical reporting requirements
Alerts and exception reporting
Users and stakeholders requiring access
Reporting and dashboard requirements
Integration with existing systems
Future expansion requirements
How the data will support operational decisions
02
Understand the Site and Existing Infrastructure
A physical survey should be completed before the final deployment design is agreed.
IoT devices can be affected by building construction, available power, network coverage, mounting positions and the environment in which they are installed.
A solution that performs successfully in one location may require a different approach elsewhere, particularly across multi-site estates where building layouts and infrastructure can vary considerably.
Existing network and communications infrastructure should also be reviewed. Ethernet connectivity, Wi-Fi coverage, cellular signal and existing IoT gateways may all influence the most appropriate deployment strategy.
Consider:
Building layout and construction
Proposed device locations
Existing network infrastructure
Wi-Fi availability and coverage
Ethernet connectivity
Cellular signal strength
Existing gateways or IoT infrastructure
Available power
Mounting surfaces and locations
Ceiling and service-area access
Environmental conditions
Access restrictions
Existing drawings and documentation
03
Choose the Right Connectivity
Connectivity is one of the most important decisions in an IoT deployment.
Different technologies provide different combinations of bandwidth, range, power consumption and infrastructure requirements. The correct approach depends on the devices being deployed, the amount of data being transmitted and the physical environment.
Some devices may use the existing Ethernet or Wi-Fi network, while others may use cellular connectivity or low-power wireless technologies such as LoRaWAN.
Connectivity should therefore be designed around the application rather than assuming that one technology will be suitable across every location.
Consider:
Ethernet
Wi-Fi
4G or 5G cellular connectivity
LoRaWAN
Bluetooth or other short-range technologies
Required transmission distance
Bandwidth requirements
Frequency of data transmission
Building construction and signal penetration
Network availability
Coverage surveys
Gateway requirements
Resilience and loss of connectivity
CONNECTIVITY CAN MAKE OR BREAK THE DEPLOYMENT
An IoT device is only useful if it can reliably communicate with the wider platform. Connectivity should be tested in the actual deployment environment rather than assuming that Wi-Fi, cellular or other wireless coverage will be available where it is needed.
04
Consider Power and Device Locations
Device location can have a significant impact on both performance and installation complexity.
Sensors need to be positioned where they can accurately collect the required information while remaining accessible for installation and future maintenance.
People-counting sensors, for example, may require specific mounting heights and positions, while environmental sensors may need to avoid areas affected by direct sunlight, ventilation systems or other local conditions.
Power requirements should also be considered early. Depending on the technology, devices may use PoE, local mains supplies or batteries.
Consider:
Optimum device position
Mounting height
Required field or area of measurement
PoE availability
Local mains power
Battery-powered devices
Expected battery life
Access for battery replacement
Cable routes
Mounting surfaces
Environmental conditions
Tampering or accidental damage
Future maintenance access
05
Plan the Network and Data Architecture
Where IoT devices use the client’s network infrastructure, IT involvement should begin early.
IP addressing, VLANs, firewall rules, internet access, cybersecurity policies and cloud connectivity may all need to be agreed before devices can communicate with their platform.
For larger deployments, the volume and frequency of data should also be understood. Hundreds or thousands of connected devices can introduce requirements that may not be apparent during a small proof-of-concept installation.
The project should clearly establish how data moves from the device through the network to the platform where it is processed and presented.
Consider:
IP addressing
DHCP or static addressing
VLAN requirements
Firewall rules
Internet connectivity
Cloud platform access
Bandwidth requirements
Gateway architecture
Cybersecurity requirements
Device authentication
Data encryption
Client IT approval
Network monitoring and support
06
Understand the Platform and Integrations
Replacing an existing CCTV system on a live site requires more than an installation programme. The transition from the old system to the new one needs to be planned so that security coverage and site operations are maintained throughout the project.
A phased approach is often appropriate, particularly on larger estates. Cameras, network infrastructure and recording equipment can be migrated in controlled stages rather than attempting to replace the entire system at once.
The sequence should consider which cameras are operationally critical, when existing equipment can be removed, when new equipment becomes available to operators and how any temporary loss of coverage will be managed.
Installation windows also need to reflect the environment. In retail, commercial and other operational sites, access restrictions, trading hours, permits, control-room coordination and out-of-hours working can all influence the programme.
THE DEVICE IS ONLY PART OF THE SOLUTION
The real value of an IoT deployment usually comes from the information produced by the devices. Platform configuration, reporting, integrations and data accessibility should therefore be considered alongside the physical installation.
07
Plan Installation and Deployment at Scale
A successful proof of concept does not automatically guarantee a successful estate-wide deployment.
Installing a handful of devices in a controlled environment is very different from coordinating hundreds of devices across multiple operational locations.
For larger programmes, installation standards and repeatable processes become increasingly important. Device naming, configuration, mounting, commissioning and documentation should be consistent regardless of which engineer or installation team completes the work.
Site access, inductions, permits, delivery logistics and coordination with local teams should also form part of the deployment programme.
Consider:
Pilot or proof-of-concept phase
Deployment programme
Site prioritisation
Standard installation methodology
Device pre-configuration
Device naming conventions
Asset tracking
Installation teams
Site access and inductions
Equipment logistics
Local stakeholder communication
Installation reporting
Progress tracking
Exceptions and failed installations
A PILOT IS NOT THE SAME AS A ROLLOUT
A solution that works successfully on one site still needs a repeatable deployment process before it can be scaled across an estate. Installation standards, logistics, configuration, testing and reporting become increasingly important as device numbers and site quantities grow.
08
Agree Testing and Data Validation Requirements
Testing should establish more than whether the device is simply online.
The project should confirm that each device is communicating reliably and producing the expected information.
Where the technology measures people, occupancy, environmental conditions or other real-world activity, data accuracy may also need to be validated against an agreed reference.
Acceptance criteria should therefore be defined before deployment begins so that installers, technology providers and clients have a common understanding of what constitutes a successfully commissioned device.
Testing should consider:
Device connectivity
Device health
Correct configuration
Device identification
Data transmission
Platform visibility
Data accuracy
Reporting
Alerts and notifications
Integration functionality
Connectivity resilience
Offline behaviour
Firmware versions
Failed-device replacement
Client acceptance
Define what a successfully commissioned IoT device looks like before the rollout begins.
09
Documentation, Support and Handover
A large IoT deployment can quickly become difficult to support if accurate information about the installed devices is not maintained.
The client should be able to identify where each device is installed, how it connects, how it is configured and which platform account or location it belongs to.
Support arrangements should also be clear. Responsibilities for network connectivity, device hardware, platform software and physical maintenance may sit with different organisations.
These responsibilities should be established before the project is closed.
The final handover should typically include:
Device and asset register
Site and device locations
Device serial numbers
Network and connectivity information
Gateway information
Configuration records
Platform configuration
User and administrator information
Testing and validation results
As-installed drawings where applicable
Warranty information
Support and escalation arrangements
Battery replacement requirements where applicable
Outstanding defects and actions
Formal client acceptance and sign-off
IOT PROJECT DELIVERY
Managing an IoT Deployment
A successful IoT deployment involves much more than installing connected devices. Connectivity, infrastructure, device locations, platforms, data and operational requirements all need to work together.
For larger or multi-site programmes, the deployment process itself becomes equally important. Consistent installation standards, configuration, logistics, testing and reporting are essential when technology is being rolled out across multiple locations.
Fortiva Projects provides IoT project management and deployment support, helping clients coordinate projects from initial surveys and pilot deployments through rollout, testing, data validation and final handover.
HOW WE CAN HELP