IoT implementation and maintenance considerations

This section highlights tasks that may be considered when implementing an IoT solution and ensuring successful integration and communication with existing infrastructure and systems.

Where an IoT solution is required to integrate or communicate with existing connectivity infrastructure and other systems, particularly when implementing a new connectivity technology, it is essential to consider interoperability, that is, how the elements (hardware, software, connectivity infrastructure, data formats, storage) of both the IoT solution and existing systems can be made to work together.

To accomplish this, developers collaborate to agree standards for hardware communication protocols, data formats, and so on, to enable different systems to communicate and exchange data. Various stakeholders work together to agree these open standards including governments, industry and technology groups, and international standards organisations.

Depending upon the size and level of integration of a new IoT solution, it may be beneficial to undertake an assessment of existing systems and infrastructure. The aim of this assessment is to ensure existing systems and networks are compatible with the new solution and demonstrate that performance requirements can be met (or exceeded), for example, increased network load or improved performance to support a real-time application.

The list below outlines some key factors to consider when launching a new IoT solution.

1. Existing infrastructure readiness

Can the existing network support the additional traffic load generated by the proposed new IoT solution(s)?

Considerations:

• assess current network traffic
• obtain data on traffic load, server requirements etc. for proposed new IoT solution(s)
• what additional comms infrastructure (for example, wired/wireless network, comms rooms/cabinets, power) is required

2. IoT solution integration with existing systems

Considerations:

• how will the IoT system communicate with existing systems (for example, APIs and middleware)?
• can this be implemented seamlessly (without downtime to existing solutions or network)?
• are any upgrades to existing system required?

3. IoT solution is a non-trivial implementation and impacts/integrates with existing systems

In this instance, a suitable test process is good practice. It may include:

• a test plan with required scenarios, tools, and criteria to evaluate success
• a rollback plan
• post implementation evaluation

As with any IT deployment it is best practice to define and use an asset management approach for your IoT solution, setting out how all devices will be managed and maintained, including deployment and commissioning, configuration, software updates, and disabling/decommissioning.

For large and complex IoT solutions organisations should consider a central IoT management platform (also known as connected devices platforms) to manage the estate. A range of platforms are available from suppliers, so consideration should be given to compatibility with your device providers software and scalability of solution and capabilities.

Some key factors to consider for effective IoT device management are:

Security

It is important to ensure that appropriate security is in place, both for the whole IT solution and individual devices, to protect sensitive data, maintain privacy, and prevent unauthorised access and malicious attacks on your network via the IoT device. 

See the section on network security considerations for more detail.

Device monitoring

A central platform would typically be used to monitor a large number of IoT devices. The platform also collects utilisation and diagnostic data from the IoT devices to support fault finding and resolution and to enable the IT support team to improve the efficiency of the solution.

Decommissioning

It is important to plan for decommissioning, both for the whole IoT solution or only dedicated components. If applicable, the device should be deregistered from the management platform.

Security certificates should be revoked, and other confidential or sensitive data should be deleted securely. The National Cyber Security Centre (NCSC) provides some guidance on decommissioning and disposing of network devices and the secure sanitisation of storage media.

Power consumption

Most IoT devices are small and include hardware that does not require high power usage. For some solutions, the IoT devices do not need to be constantly ‘awake’ so can be put into sleep mode to reduce energy consumption.

Use of a large number of devices will increase overall energy consumption. IoT devices generate large amounts of data that needs to be transmitted, processed, and stored, leading to increased demands on your network and supporting infrastructure (for example, servers and network hardware) leading to higher electricity usage.

Battery powered devices

IoT devices require power to operate and send data.  While some IoT sensors are passive and can draw power from the devices in which they are embedded, many will require a battery.

When using battery powered IoT devices you should consider:

• are the batteries single use or rechargeable?
  • for single use battery replacement will need to be planned to minimise disruption and downtime
  • for rechargeable batteries it is important to know how often and how many times they can be charged and discharged
• if buying and fitting batteries separately from the IoT device, make sure to choose the battery with the optimum cell voltage for the IoT device
• using standby mode (power down) when the IoT device is not in use to maximise battery life

Safely dispose of IoT device batteries at the end of use. You can find further guidance here:

• Consumer products: recycling batteries and electrical waste (GOV.UK)

• Are you disposing of waste batteries correctly? Here’s what you need to know (The Compliance People)

• Safe Lithium Ion Battery Disposal in the UK (Recover Recycling Ltd)