Network Monitoring for Strata and Apartment Buildings: What It Is and Why It Matters

Most strata and building managers find out something has stopped working the same way — a resident calls to complain. By then, the CCTV camera has been offline for two days, the access panel has been rebooting itself every morning, or half the building's wireless network has been running on a single access point since Tuesday. The problem isn't the technology. It's the lack of visibility.

Network monitoring for apartment buildings and strata complexes changes that dynamic entirely. Rather than waiting for a fault to surface through a frustrated phone call, you know about it before most residents do — often before any resident does. For building managers responsible for multiple properties, that shift from reactive to proactive is one of the most practical operational improvements available.

This guide explains what building network monitoring is, what it covers, how it works in practice, and what to look for when evaluating it for your building or portfolio.

What Is Network Monitoring for a Strata Building?

Building network monitoring means having software and systems that continuously check whether your building's technology infrastructure is online and performing as it should. That infrastructure typically includes WiFi networks, CCTV cameras and recording equipment, access control panels and door hardware, intercom systems, building management systems (BMS), and increasingly, EV charging systems.

The monitoring software checks these systems at regular intervals — every few seconds for critical hardware, every few minutes for less time-sensitive systems — and records the results. When something drops offline, degrades below acceptable performance thresholds, or shows a warning condition (like a storage drive filling up), it generates an alert and routes it to whoever needs to know.

The contrast with the traditional approach is stark.

In a reactive model, your visibility into building systems depends entirely on residents noticing something is wrong and bothering to report it. That introduces delays. A resident who notices the carpark camera is showing a black screen might assume it's a power issue and not say anything for a week. A door panel that's intermittently losing connection might go unreported until it fully fails at 11pm on a Friday. By the time you know there's a problem, the impact has already accumulated — missing footage, security gaps, resident frustration.

In a proactive model, the monitoring system is your first line of information. The alert reaches you at 9am Tuesday rather than through a 2am emergency call on Saturday. You schedule a fix during business hours. The resident never knew there was a risk.

For strata managers who oversee a portfolio of buildings, the difference is even more significant. You cannot physically visit ten or fifteen buildings each day to verify that every system is running. Monitoring gives you that verification automatically, from a single location.

What Gets Monitored in a Modern Strata Building?

The scope of what can be monitored has expanded considerably as building technology has moved onto IP-based networks. Where once CCTV, intercoms, and access control each operated on their own separate systems with no interconnection, modern buildings run most of these systems over the same network infrastructure. That convergence makes centralised monitoring practical.

Here is what a comprehensive building monitoring programme covers.

WiFi and Network Infrastructure

The building's wireless network is usually the most visible system to residents, which means faults generate complaints quickly. But monitoring goes well beyond checking whether the internet is up.

Access point uptime tells you which wireless radios are active across the building. Signal strength data tells you whether coverage in particular zones is adequate or has degraded. Connected device counts let you identify access points that are carrying an unusual load — which might indicate that a neighbouring access point has failed and its clients have migrated. Bandwidth utilisation tells you whether the building is approaching capacity, so infrastructure upgrades can be planned before performance degrades noticeably.

For buildings operating managed WiFi across multiple properties, this data feeds into a single view that makes portfolio-level network management practical. A building with 80 apartments and consistent high utilisation from 6pm to 9pm is telling you something about what the next infrastructure upgrade needs to look like.

CCTV Systems

CCTV monitoring is where the gap between reactive and proactive management has the highest consequences. A camera that's offline is not just inconvenient — it's a security risk and potentially a liability issue, and nobody knows about it until either a resident notices a blank screen or an incident occurs and the footage doesn't exist.

Good monitoring for CCTV systems covers camera uptime (is each individual camera reachable on the network), recording status (is the NVR or DVR actively capturing footage), and storage health. That last one is particularly important. Recording storage fills up silently. When it's full, most systems either stop recording entirely or begin overwriting in a loop that may not be configured correctly. Neither outcome is acceptable if footage is later required for a security investigation or an insurance claim.

A monitoring system that tracks storage utilisation and alerts at, say, 85% capacity turns a crisis into a routine maintenance task.

Access Control Systems

Access control monitoring covers whether door panels and readers are communicating with the central controller, whether credential data is synchronising correctly to panels, and whether there are patterns of failed access attempts that might indicate a hardware fault or a security event.

An access control system that loses network connectivity to a door panel creates an immediate problem. Depending on how the system is configured, it might fail open (the door doesn't lock, which is a security risk) or fail closed (residents can't get in, which generates urgent calls). Neither situation is acceptable, and both are avoidable with monitoring that alerts you the moment a panel loses connectivity rather than after the consequences play out.

Failed access attempt logs are also worth monitoring at a pattern level. A single failed attempt is normal — someone tries their old fob after getting a new one. Fifty failed attempts from the same credential in twenty minutes is worth investigating.

Intercom Systems

Intercom monitoring checks whether individual intercom units are reachable on the network, whether call-handling is working correctly, and whether firmware is current across all devices. Outdated firmware on intercom hardware is a common source of connectivity and audio quality issues that rarely gets caught without active monitoring.

Missed call logs can also reveal patterns — if residents are frequently not getting through to visitors, that's an experience problem that monitoring data can surface systematically rather than through scattered complaints.

Building Management Systems (BMS)

A building management system controls and monitors environmental and mechanical systems — HVAC, lighting, lifts, fire systems, energy metering. Monitoring a BMS from a network perspective means checking whether sensors and control nodes are communicating correctly, whether HVAC and lighting controls are responding to commands, and whether the BMS itself is reachable and operating within expected parameters.

BMS faults often have cascading effects. A temperature sensor that stops reporting correctly can cause an HVAC zone to overheat or overcool. A lighting control node that drops offline can leave a carpark or lobby in the dark. Catching these connectivity issues early means building services are restored before residents experience them.

EV Charging Systems

EV charging is now a standard consideration for new strata developments and a common upgrade request in existing buildings. These systems are network-connected and require monitoring like any other building technology.

Monitoring covers charger connectivity (is each unit reachable and reporting correctly), session data (is charging completing successfully or terminating with errors), and fault codes. An EV charger that's showing a fault code but hasn't generated a resident complaint yet is a service call waiting to happen. Monitoring surfaces it on your terms rather than the resident's.

The Problem With Reactive Fault Management in Strata

The reactive model — where faults are reported by residents and then investigated — is the default for most strata buildings. It's also expensive, risky, and increasingly difficult to justify when the alternative exists.

Here is what reactive fault management actually looks like in practice.

Most strata buildings have no independent visibility into whether their building systems are running. They're dependent on residents noticing, caring enough to report, and knowing who to contact. That's three filters a fault has to pass through before anyone in a position to fix it even knows about it. A fault that passes all three filters might still take days to surface if it happens during a period when the affected system isn't being used.

CCTV storage fills silently. There is no visible symptom until either a resident checks the monitor, an incident occurs and the footage doesn't exist, or someone performs a manual check. In a building where nobody performs regular manual checks — which is most buildings — storage will fill and the system will quietly stop recording. Monitoring catches this automatically.

Access control offline events create immediate security and insurance exposure. If a door is propped open because the access panel has lost connectivity, the building's physical security has a gap. If an incident occurs during that gap, the question of whether the building manager had adequate monitoring and response procedures is a legitimate one for insurers and, potentially, for the owners corporation.

Internet outages in residential buildings don't just inconvenience one resident. In an apartment building where residents work from home, a network fault might generate thirty or forty contacts in the space of an hour. Monitoring lets you get ahead of that — you can send a building-wide notification before the first resident calls, which immediately reduces the volume of contacts and demonstrates that you're already across the issue.

For building managers who look after ten or more properties, there is an additional problem. You cannot tell, at any given moment, whether all your buildings' systems are healthy without either visiting each one or receiving a fault report. Portfolio-level monitoring gives you that visibility continuously. You're not reacting to the loudest complaint; you're managing across the portfolio based on actual system data.

What a Network Monitoring Dashboard Looks Like

The practical output of a network monitoring system is a dashboard — a single screen that shows you the current status of all monitored systems across your building or portfolio. Understanding what that dashboard shows is useful when evaluating what monitoring can and can't do for your operation.

A well-designed monitoring dashboard provides a single-pane-of-glass view, meaning all buildings and all systems appear in one place rather than requiring you to log in to separate tools for WiFi, CCTV, access control, and so on. Each system and device has a status indicator — typically something like online, degraded, or offline — so you can see at a glance what's healthy and what needs attention.

Beyond current status, the dashboard shows historical uptime data. Trend charts let you see whether a system has been stable or whether it has been rebooting repeatedly over the past week. A device that reboots every night at 2am has a problem that a snapshot view won't reveal but a trend view will.

Alert routing is a critical configuration consideration. When a fault is detected, the system needs to notify the right person in the right way. Email works for non-urgent situations where someone will check in the morning. SMS works for time-sensitive issues where a delay of hours matters. The alert routing configuration should reflect the severity of the fault and the roles of the people being notified — a building manager might receive all alerts, while a facilities contractor only receives those relevant to their scope.

Good monitoring platforms also integrate with work order or ticketing systems. When an alert is generated, a ticket can be created automatically and assigned to the relevant contractor. That creates a documented trail from fault detection to resolution, which is useful for OC committee reporting and for insurance purposes.

One distinction that matters particularly in strata: a monitoring platform should make it clear what the building owner is responsible for and what the internet or technology provider is responsible for. If the NBN connection to the building is down, that's the ISP's domain. If the building's internal router has failed, that's the building's infrastructure. Monitoring that can differentiate between these helps building managers have accurate conversations with their providers and avoids situations where everyone points at each other and nothing gets fixed.

To make this concrete — consider this scenario. A CCTV NVR in building B shows storage at 94%. The monitoring system sends an alert to the building manager. The building manager logs a work order for a technician to either expand storage or adjust the retention policy. The technician attends during business hours, the issue is resolved, and recording continues without interruption. No resident ever knew there was a risk. No footage was lost. No emergency callout was required.

That is what proactive monitoring looks like in practice.

Proactive vs Reactive — The Cost Difference

The business case for proactive building network monitoring is straightforward once you look at where reactive fault management actually spends money.

Emergency after-hours callout rates from technology contractors are typically two to three times the standard rate. A fault that's detected at 9am on a Thursday might cost $150 to fix during a scheduled visit. The same fault, discovered at 11pm on a Friday when a resident can't get their access fob to work, might cost $450 in emergency callout fees before the technician even looks at the problem. Across a portfolio of buildings, the difference accumulates quickly.

The insurance dimension is worth taking seriously. CCTV and access control systems are often part of a building's insurance obligations. If a building's CCTV is offline and an incident occurs, the insurer's questions about whether adequate monitoring and maintenance procedures were in place are legitimate. Documented uptime data and fault response records are useful evidence that the building was managed responsibly. Their absence creates exposure.

OC committee liability is a related consideration. When building technology fails and a committee member asks what monitoring was in place and how quickly the fault was detected and responded to, the building manager who can provide a timestamped alert log and a documented response timeline is in a very different position from one who can only say they found out when a resident called.

Resident churn matters in residential buildings where internet connectivity is a significant factor in the tenancy decision. In newer apartment buildings especially, residents have an expectation that internet access will be reliable. A building with a reputation for frequent connectivity issues loses tenants and has difficulty attracting them at comparable rent levels. That's a financial impact that's harder to quantify but very real.

There is also what might be called the 80/20 rule of building network faults. The majority of faults — perhaps 80% — are predictable and catchable before they become outages. Storage drives fill. Firmware goes out of date and hardware begins behaving erratically. Devices reboot at the same time every night because of a configuration issue. These are not random failures; they are patterns that monitoring data surfaces before they become crises. The remaining 20% are genuine unexpected failures, and monitoring reduces their impact by detecting them as quickly as possible rather than when a resident notices.

Monitoring Across a Portfolio of Buildings

For strata managers who look after multiple buildings, the monitoring question is less about a single building and more about how to maintain visibility across an entire portfolio without multiplying your administrative overhead proportionally.

The typical situation for a portfolio manager running fifteen or more buildings looks like this. Each building has its technology installed by different contractors. Some buildings have vendor-specific dashboards that require separate logins. Others have no monitoring at all. Getting a picture of whether everything across the portfolio is healthy requires either visiting each site, calling each contractor, or waiting for a fault to surface. None of those is scalable.

Centralised portfolio monitoring replaces that situation with a single dashboard that aggregates status across all buildings. Each building appears as a column or section. Each system type — WiFi, CCTV, access control, intercom, BMS, EV charging — appears as a row. Status is updated continuously. A fault in any building at any system level is visible from the same view. You don't need to log in to fifteen different tools or wait for fifteen different contractors to report in.

SLA visibility is a specific benefit for buildings where technology providers are contracted to maintain particular uptime levels. If a provider is committed to 99.5% uptime on the building's WiFi network, the monitoring data either demonstrates that commitment is being met or provides documented evidence that it isn't. That data is useful in contract conversations and in situations where remedies or credits are being discussed.

Alert escalation should be structured deliberately. Not every fault warrants the same response. A single access point going offline in a building with twelve access points is low severity — coverage is degraded but most residents won't notice. A CCTV NVR going offline is high severity — recording has stopped. An access control panel losing connectivity is critical — there may be an immediate security impact. The monitoring system should route alerts to different people at different severity levels, so that every minor event doesn't page the senior building manager at 11pm.

A practical escalation structure might look like this.

Monthly uptime reports are a deliverable that differentiates a proactive building manager in OC committee conversations. A report showing 99.7% uptime across all monitored systems over the past month, with a log of any faults detected and their resolution times, is a professional artefact that demonstrates competent management. Most buildings don't have it. The ones that do have it tend to have fewer escalating disputes about technology performance.

What to Look for When Evaluating Network Monitoring for Your Building

If you're assessing network monitoring options for a building or portfolio, here are the practical considerations worth working through.

Agentless vs agent-based monitoring. Agent-based monitoring requires software installed on each monitored device. That can be practical in a corporate IT environment but becomes complicated in a multi-tenant building where you have a mix of device types from different vendors, not all of which accept third-party agents. Agentless monitoring — which works by querying devices remotely using protocols like SNMP, ICMP ping, and vendor APIs — is generally easier to deploy in building environments. Look for a solution that doesn't require hands-on configuration of each monitored device.

Protocol coverage. SNMP (Simple Network Management Protocol) is the standard protocol for monitoring network hardware — routers, switches, access points. Ping-based monitoring confirms whether a device is reachable. API-based monitoring is used for systems that expose their own data interfaces, such as modern CCTV platforms and EV charging management systems. What matters is not which protocols a solution supports in theory but whether it covers the specific systems in your building. Ask for a list of what the monitoring platform can actually monitor, not what protocols it supports in general.

Alert fatigue. A monitoring system that generates 40 alerts a day — many of them for minor or transient conditions — is worse than no monitoring at all. When everything is marked urgent, nothing is. Look for threshold-based alerting (alert when storage exceeds 85%, not when it changes at all) and trend-based alerting (alert when a device has rebooted more than three times in 24 hours, not when a single reboot occurs). The goal is to receive actionable alerts, not a continuous stream of noise.

Integration with building management platforms. If your organisation uses a property management platform, a work order system, or a facilities management tool, check whether the monitoring solution can integrate with it. Automatic ticket creation when a fault is detected, and automatic ticket closure when a fault resolves, reduces the administrative burden significantly and creates a clean audit trail.

Who manages the monitoring. There are three models: in-house IT team, managed service provider, and the technology or telecoms provider who installed and maintains the infrastructure. For most strata buildings, the third model is most practical. The provider who installed the WiFi network, for example, is already responsible for its performance, already has access to the management interfaces, and already has the context to know what a normal versus abnormal reading looks like. Having a managed service provider or technology partner own the monitoring is often more efficient than building internal capability.

Australian data residency. For buildings with access control or security systems, the monitoring data contains information that may be sensitive — access logs, footage metadata, security event records. Where that data is stored matters. Check whether the monitoring platform stores data in Australian data centres. If a provider is vague about where data is processed and stored, that should prompt further questions. This consideration aligns with the broader topic of network segmentation and data isolation in multi-dwelling environments.

How Pickle Approaches Network Monitoring

Pickle provides managed network infrastructure for strata buildings, apartment complexes, and commercial properties across Australia. As part of its managed service model, Pickle monitors the network infrastructure it is responsible for — WiFi access points, network switches, routers, and related equipment — and alerts building managers proactively when issues are detected. That means building managers receive fault notifications before residents do, and remediation can be scheduled on their terms rather than in response to a complaint.

For buildings that want visibility across all technology systems — not just the network infrastructure Pickle manages, but also CCTV, access control, intercoms, BMS, and EV charging — Pickle can work with building managers and committees to assess what monitoring capability is feasible, what systems can be brought into a centralised view, and what a practical management approach looks like for that specific building or portfolio.

The goal is straightforward: building managers should know the status of their building's technology before residents do. Monitoring is how that becomes possible.

To discuss monitoring for your building or portfolio, call Pickle on 1300 688 588 or email [email protected].

Frequently Asked Questions

Q: Does every strata building need a dedicated network monitoring system?

A: Not necessarily dedicated, but every building benefits from some level of monitoring. The practical question is what your current visibility is. If you're entirely dependent on resident complaints to know when something has failed, the cost of gaps in visibility — missed CCTV footage, access control outages, internet faults — typically exceeds the cost of monitoring. Smaller buildings with simpler technology may be well-served by monitoring included as part of a managed network service rather than a standalone monitoring platform. Larger buildings and portfolios generally warrant a more comprehensive approach.

Q: What is the difference between monitoring the building network and monitoring the internet connection?

A: The internet connection is the link between your building and the outside world — typically the NBN connection or a dedicated business fibre service. The building network is everything on the inside — the routers, switches, access points, and all the devices connected to them. Monitoring can cover both, but they're distinct. An internet outage is the ISP's responsibility to resolve. An internal network fault is the building's. A good monitoring platform distinguishes between the two, which helps building managers have clear conversations with providers rather than getting caught in situations where everyone points at someone else's infrastructure.

Q: How does network monitoring help with CCTV footage gaps?

A: The most common cause of footage gaps isn't camera failure — it's storage filling up. Most CCTV recording equipment records continuously, and when storage reaches capacity, recording either stops or begins overwriting older footage in a way that may not preserve what you need. Monitoring tracks storage utilisation continuously and alerts when it approaches a threshold, so a scheduled maintenance task (expanding storage or adjusting retention settings) can prevent the gap from occurring. Monitoring also tracks camera uptime, so a camera that loses network connectivity is detected immediately rather than days later when the footage is needed.

Q: Who is responsible for building network monitoring — the strata manager, the building owner, or the technology provider?

A: In practice, responsibility is usually shared. The technology provider — whether a managed network provider, a CCTV installer, or a building systems integrator — is typically responsible for monitoring the systems they installed and maintain. The building manager is responsible for ensuring that monitoring arrangements are in place across all systems and that the results feed into appropriate response procedures. The building owner or owners corporation sets the overall expectation and funds the infrastructure. Where monitoring falls through the gaps is usually at the boundary between providers — when one contractor assumes another is monitoring something, and neither is. Strata managers are best placed to close those gaps by ensuring monitoring coverage is explicitly addressed in each technology service agreement.

Q: Can network monitoring data be used as evidence in OC committee disputes?

A: Yes, and it often is. Timestamped uptime logs, alert records, and fault resolution timelines are documented evidence of how a building's technology was managed and how quickly faults were detected and responded to. In disputes about whether a system was adequately maintained, whether a fault was reported promptly, or whether a service level commitment was met, that data is relevant and credible. The absence of monitoring data isn't neutral — it can suggest that adequate oversight was not in place. For building managers who want to be able to demonstrate professional management standards, maintaining documented monitoring records is a meaningful protection.