Multi-Site Network Monitoring for Property Portfolios: What to Watch and Who Gets the Call

Once a portfolio passes five or six buildings, the network stops being something you can keep in your head. Each property has its own carrier, its own firewall, its own switches and its own quirks, and the first indication of a failure is usually a phone call from a tenant. Monitoring turns that around. A good monitoring programme tells you a site is down before anyone calls, shows you which of three possible causes is responsible and routes the alert to the person who can act. This guide covers what to measure, how to route alerts and how to bring a newly acquired building under watch.

The metrics that actually matter

Start with availability: is the uplink up, is the firewall responding and are the core switches reachable. Add latency and packet loss on each carrier circuit, since a link that is technically up but dropping five percent of packets feels broken to users. Track device health such as CPU, memory and temperature on core equipment, and power state on battery backup units.

For building systems, watch whether controllers, recorders and access panels are online. A camera system that silently stopped recording last Tuesday is worse than one that shows an alert.

Choosing a platform

Cloud-managed networking from vendors such as Cisco Meraki or Ubiquiti gives central visibility with little infrastructure to run. Larger or mixed estates may add a dedicated monitoring platform that collects data from firewalls, switches, UPS units and building gateways in one view.

Prefer one dashboard for the whole portfolio, organised by building, with a clear status for each site. If staff need five logins to learn whether Building 14 is up, they will not check.

Alert design: fewer, better

Too many alerts and people ignore them; too few and you miss real problems. Define severity levels. A core uplink down is critical and pages the on-call phone. A single access point offline is informational and appears in a daily summary. A battery backup running on batteries is a warning that needs follow-up within the hour.

Add acknowledgement and escalation: if the first person does not respond in ten minutes, the alert goes to the next. Document who is on call each week, including nights and weekends.

Configuration backup and drift detection

Every firewall and switch should have its configuration backed up automatically after each change, with versions stored off the device. When hardware fails, a replacement can be restored in minutes instead of being rebuilt from memory.

Drift detection compares the current configuration with the approved standard and flags differences. It catches the contractor who changed a rule, the technician who left a test port open and the setting that reset after a firmware update.

A circuit and carrier register

Maintain a register with the carrier, circuit ID, bandwidth, demarcation location, account number, support contact and renewal date for every connection. When an outage hits at two in the morning, nobody should be hunting through email for the account number.

The register also supports renewal negotiation. A portfolio with forty circuits and no renewal calendar is likely overpaying on some and out of contract on others.

Onboarding an acquired building

Acquisitions arrive with unknown networks. Use a standard runbook: survey the telecom rooms, document the carrier circuits, record admin credentials, replace default passwords, install a standard firewall or bring the existing one into management, enable monitoring and back up configurations. Complete the process within a defined number of weeks of closing.

Treat the first thirty days after acquisition as a risk period. Prioritise multi-factor authentication for any shared accounts, review vendor remote access and check what building systems are reachable from the internet.

Reporting that owners will read

Monthly reports should show availability by building, incidents and their causes, changes made and upcoming renewals. A single page with a red, amber or green status per site is more useful than twenty pages of graphs.

Include a short list of recommended work, ranked by risk and cost, so owners can approve spending on evidence. Over a year, the same report shows whether the portfolio is improving.

Where this lands by property type

REITs & Asset Managers

REITs and asset managers answer to unit holders, lenders and auditors. Technology risk across the portfolio sits inside that accountability, even when each building is run by someone else. Typical exposure: property managers using different systems with different controls.

Property Management Companies

A management company sells reliability to owners. Its own systems, from the ledger to the after-hours phone line, are the product, and every outage is seen by clients who pay for calm. Typical exposure: head office and site offices on different standards.

Facilities Teams

Facilities teams keep heat, air, water and lifts running. Increasingly those systems are networked, and the team needs IT that understands operational priorities. Typical exposure: mechanical systems on networks the facilities team cannot see.

Services that address this topic

Guidance like this works best inside a coordinated programme, not as a one-off fix. These PropertyIT services cover the topic directly.

Next step: a building technology survey

PropertyIT is a sub-brand of SAZ.ca, led by Ali Sedighi, MBA, combining senior-partner strategy with hands-on IT delivery for property teams. If this article describes a situation in your buildings, book a free 30-minute consultation: call (604) 632-4959 or email info@SAZ.ca. We will give you a plain-language view of your options, and a fixed-price scope if you want one. No lock-in, no pressure and no obligation.