INSIGHTS • TECHNOLOGY SYSTEM AUDITS
Planning a technology upgrade? Discover how a system audit can identify infrastructure condition, capacity, risks, dependencies and upgrade requirements.
A practical guide to reviewing existing technology systems and infrastructure before planning an upgrade, replacement or wider investment programme.
Fortiva Projects
25 September 2026
9 min read
Introduction
Technology systems rarely remain exactly as they were originally installed.
Over time, equipment is replaced, additional devices are added, networks are expanded and systems are modified to meet changing operational requirements. Documentation may not always be updated, and the people responsible for the original installation may no longer be involved.
When the time comes to upgrade CCTV, access control, network infrastructure, IoT or other building technology, the starting point is therefore not always as clear as it appears.
A technology system audit provides an opportunity to establish what is actually installed, understand its condition and capability, identify infrastructure limitations and determine what can reasonably be retained.
Doing this before developing the replacement solution can reduce assumptions, unexpected additional works and programme risk later in the project.
THE KEY POINT
A successful technology upgrade starts with understanding what you already have, what condition it is in and whether the existing infrastructure can support what comes next.
ARTICLE CONTENTS
In this Guide
01
02
03
Understand What You Already Have
Review the Condition of the Existing Infrastructure
Identify Capacity and Performance Limitations
04
05
Check Cabling, Networks and Connectivity
Review System Configuration and Documentation
06
Identify Dependencies Between Systems
07
Understand the Operational and Business Requirements
08
09
Prioritise Risks, Issues and Recommendations
Turn the Audit into an Upgrade Strategy
01
Understand What You Already Have
The first stage of a technology system audit should establish what is actually installed.
Existing drawings, asset registers and equipment schedules are useful starting points, but they should not automatically be assumed to represent the current installation.
Technology estates evolve. Cameras are replaced, access-controlled doors are added, network switches are changed, cabinets are relocated and additional cabling is installed. Over several years, the physical installation can become significantly different from the original design documentation.
A physical audit provides an opportunity to create an accurate picture of the current estate before decisions are made about its future.
Consider:
Installed equipment and manufacturers
Device models and quantities
Equipment locations
System architecture
Communications cabinets and racks
Servers and recording equipment
Controllers and gateways
Network switches
Copper and fibre infrastructure
Power supplies
Software platforms and versions
Existing drawings and asset registers
Previous modifications and additions
02
Review the Condition of the Existing Infrastructure
Knowing that equipment exists is only part of the picture. Its physical and operational condition should also be understood.
Some infrastructure may be perfectly suitable for continued use, while other components may be approaching end of life or showing signs of deterioration.
Cabling, cabinets, power supplies, connectors and equipment installed in challenging environments can all deteriorate over time.
The audit should distinguish between infrastructure that can reasonably be retained, equipment that requires further investigation and components that should form part of a future replacement programme.
Consider:
Physical condition of equipment
Age of installed technology
Manufacturer support status
Signs of damage or deterioration
Cabinet condition and organisation
Cable condition
Power supplies and battery backup
Environmental conditions
Equipment reliability
Recurring faults
Availability of replacement components
Expected remaining service life
03
Identify Capacity and Performance Limitations
An existing system may be operational without necessarily having sufficient capacity for future requirements.
A network switch may have spare ports but insufficient PoE capacity. A CCTV recorder may function correctly but lack the storage required for higher-resolution cameras. An access-control platform may operate reliably but have limited capacity for additional doors.
Understanding these constraints before developing an upgrade design can prevent existing infrastructure from becoming an unexpected limitation later.
Future requirements should also be considered rather than assessing the system solely against today’s usage.
Consider:
Available system capacity
Network switch capacity
PoE availability and power budget
Recording and storage capacity
Controller capacity
Available cabinet space
Fibre availability
Network bandwidth
Software or licensing limitations
Expansion capability
Current performance issues
Expected future requirements
DON’T ASSUME EXISTING MEANS SUITABLE
Infrastructure may be operating successfully today but still lack the capacity, condition or capability required to support the next generation of technology. Existing equipment should be assessed against the proposed future requirement, not simply whether it currently works.
04
Check Cabling, Networks and Connectivity
The underlying infrastructure can have a significant influence on what can realistically be achieved during a technology upgrade.
Existing copper cabling should be reviewed for type, condition, route and distance. Fibre links should be identified and, where necessary, tested to establish whether they are suitable for continued use.
Network infrastructure should also be considered where IP-connected technology is involved. Available switch ports, PoE capacity, bandwidth, VLANs and connectivity between different areas of the site may all affect the proposed solution.
Understanding this infrastructure early can identify enabling works before they become unexpected additions during installation.
Consider:
Existing copper cabling
Cable category and condition
Cable distances
Existing fibre links
Fibre type and available cores
Fibre condition and testing
Network switches
Available network ports
PoE capacity
Network bandwidth
Existing containment
Cabinet connectivity
Connectivity between buildings or areas
Additional infrastructure requirements
05
Review System Configuration and Documentation
The physical equipment only tells part of the story.
System configuration can be equally important when determining how an existing installation operates and how it might be upgraded.
For CCTV this might include camera configuration, recording settings, retention periods and VMS licensing. For access control it could include access groups, time schedules, door configuration and user databases.
IoT and network-connected systems may involve device configuration, gateways, cloud platforms, software licences and integration settings.
Available documentation should also be reviewed to establish whether it accurately reflects the current installation.
Consider:
System configuration
Software and firmware versions
User and administrator access
Licensing
Device naming conventions
Network configuration
Recording settings
Access groups and permissions
Platform configuration
Existing drawings
Asset registers
Device schedules
Previous commissioning records
Support and maintenance information
06
Identify Dependencies Between Systems
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.
TECHNOLOGY DOESN’T EXIST IN ISOLATION
Changing one system can affect networks, power, cabling and other integrated technologies. Understanding these dependencies before an upgrade begins can prevent changes in one area from creating unexpected problems elsewhere.
07
Understand the Operational and Business Requirements
A technology audit should not focus solely on the equipment.
Understanding why the organisation is considering an upgrade is equally important.
There may be specific operational problems with the existing system, new functionality that is required or changes to the way a building or estate is being used.
Speaking with the people who operate and support the technology can reveal issues that may not be obvious from a physical inspection.
This also helps distinguish between problems that genuinely require equipment replacement and those that could potentially be addressed through configuration, infrastructure improvements or changes to operating processes.
Consider:
Current operational problems
User feedback
Required new functionality
Security requirements
Reporting requirements
Performance expectations
Reliability issues
Changes to building use
Planned expansion
Future technology requirements
Support and maintenance challenges
Budget and programme considerations
Business objectives for the upgrade
START WITH THE REQUIREMENT, NOT THE PRODUCT
An audit should establish what the organisation actually needs before replacement products or solutions are selected. Understanding the operational requirement first makes it easier to determine what should be retained, upgraded or replaced.
08
Prioritise Risks, Issues and Recommendations
An effective audit should do more than produce an inventory of equipment.
The findings should help the client understand which issues require attention, which represent future risks and which improvements could form part of a longer-term programme.
Not every issue will require immediate action. Some may affect operational reliability or security and require early intervention, while others may simply represent opportunities for improvement.
Categorising recommendations can help organisations make informed decisions about budgets, priorities and future investment.
Recommendations might be grouped as:
Immediate operational issues
Critical infrastructure risks
Security concerns
End-of-life equipment
Unsupported software or hardware
Capacity limitations
Reliability concerns
Documentation gaps
Infrastructure improvements
Short-term recommendations
Medium-term improvements
Future upgrade opportunities
Where appropriate, recommendations can also be prioritised by impact, urgency and dependency so that the client has a practical route forward rather than simply a list of observations.
09
Turn the Audit into an Upgrade Strategy
The final objective of the audit should be to provide a reliable foundation for the next stage of the project.
Once the existing estate, infrastructure, operational requirements and risks are understood, the organisation can make better-informed decisions about what needs to happen next.
That may involve replacing an entire system, upgrading selected components, carrying out enabling infrastructure works or developing a phased programme across multiple sites.
Importantly, the audit can also identify equipment and infrastructure that does not need replacing. Retaining suitable existing assets can reduce unnecessary cost and disruption.
The resulting strategy should clearly distinguish between the current position and the recommended future state.
The audit output may include:
Existing system overview
Equipment and asset information
Infrastructure assessment
Condition findings
Capacity limitations
Identified risks
System dependencies
Operational requirements
Recommended remedial works
Upgrade recommendations
Enabling infrastructure requirements
Suggested project priorities
Potential phasing
Further surveys or design work required
Recommended next steps
Key message:
A useful technology audit should not simply describe what is installed — it should help determine what happens next.
TECHNOLOGY SYSTEM AUDITS
Understanding Your Technology Estate Before Planning What Comes Next
A successful technology upgrade starts with reliable information about the systems and infrastructure already in place.
Fortiva Projects provides independent technology system audits covering CCTV, access control, structured cabling, network infrastructure, IoT and associated building technology.
We can review existing equipment, infrastructure, documentation, capacity and operational requirements to identify limitations, risks and opportunities before an upgrade programme is developed.
The result is a clearer understanding of the existing estate and a practical foundation for deciding what should be retained, improved or replaced.
HOW WE CAN HELP