When Shared Infrastructure Becomes a Building-Wide Risk

A commercial building can appear to have reliable power, connectivity, security, and building systems—until one pathway failure takes them all down at once. In this episode of Built, Wired & Secured, Alex Morgan speaks with Michael Harrington and James Rogers about the hidden dependencies that turn shared infrastructure into a single point of failure.

Modern buildings are designed for efficiency. Power, data, security, and other systems may share risers, conduits, vaults, panels, or utility pathways. That approach can save space and money, but it also creates risk. When a shared path is damaged, flooded, disconnected, or compromised during construction, multiple critical systems can fail simultaneously.

Why Shared Pathways Create Hidden Risk

The episode opens with a familiar but disruptive scenario: a building suddenly loses its lights, elevators, card readers, Wi-Fi, and HVAC. The cause may be a single cut fiber line or a failed utility feed. The problem is not necessarily that every system was poorly designed. The problem is that several systems depended on the same physical route.

James explains that these dependencies often become visible only after something goes wrong. A contractor may damage a conduit during a renovation, or a water leak may affect an electrical panel that also powers security equipment. Once the failure occurs, building operators discover how much infrastructure was shared.

Start by Mapping Critical Dependencies

Michael recommends beginning with a physical walkthrough involving facilities and IT teams. The goal is to trace where power enters the building, where data enters, where security panels are located, and how those systems connect. A simple diagram can reveal whether multiple services use the same conduit, riser, underground vault, or electrical panel.

Trace the primary power and data entry points.
Document the locations of security panels and critical network equipment.
Identify conduits, risers, vaults, and panels shared by multiple systems.
Record which systems depend on each pathway.
Compare the drawings with what is physically installed.

One example discussed in the episode involved plans that showed separate feeds for a data center and security system. In reality, both routes passed through the same underground vault. When a water main break flooded the vault, the electrical feed and fiber backbone failed together. A generator activated, but it did not restore the network or security systems because those systems depended on the damaged pathway.

Redundancy Only Works When It Is Independent

Redundancy is valuable, but only when the backup is genuinely separate and maintained. A second feed or backup connection does not provide meaningful resilience if it travels through the same conduit, vault, panel, or excavation zone as the primary system.

The guests also emphasize that redundancy on paper is not enough. One building had two utility feeds, but one had been disconnected during a renovation without anyone noticing. A backup connection can also fail to help if it shares the same fiber cut as the primary connection. Regular testing and documentation are essential.

The practical question is not simply whether a building has redundancy. It is whether the backup has a different physical path, a separate source, and an operating process that confirms it will work when needed.

Balance Resilience Against Cost

Additional conduits, feeds, equipment, and maintenance all carry costs. The right level of redundancy depends on the building's risk tolerance and the consequences of downtime. A hospital or data center may justify extensive separation because the cost of an outage is exceptionally high. A typical office building may need a more targeted approach.

Rather than attempting to rewire an entire building, the episode recommends starting with the most consequential weaknesses. That could mean adding a secondary path for security, confirming that a generator covers the panels that matter, or creating a monthly testing routine. Preventive maintenance is often more practical and less expensive than emergency recovery.

Coordinate Every Trade

Shared infrastructure is especially vulnerable during renovations and maintenance work. Electrical contractors, low-voltage contractors, IT providers, and other trades may all need access to the same riser or pathway. Without clear coordination, cables can be crowded into one conduit, existing systems can be damaged, or a future contractor may discover that no usable path remains for fiber.

Property managers and owners need to establish accountability for the shared infrastructure. Contractors should understand which pathways are critical, what they are permitted to modify, and how completed work will be documented. Someone must oversee the handoffs so the building does not end up with systems that no one fully owns.

A Practical Monday Morning Checklist

The episode closes with a straightforward first step for building owners and operators: walk the building. Visit the electrical room, data closet, and security panel. Ask where power and data enter the building. Ask what would stop working if a specific conduit, panel, vault, or feed failed.

Walk the physical infrastructure instead of relying only on drawings.
Verify how backup systems are actually connected.
Ask, “What breaks if this goes down?”
Review upcoming work with every affected trade.
Test critical backups on a defined schedule.
Update documentation when systems are added or modified.

The central message is simple: map dependencies, identify shared pathways, verify redundancy, and coordinate work before a failure exposes the risk. The best day in building operations is the day nobody notices the infrastructure—because it continues working as intended.

The Single Point of Failure You Never Planned For

Commercial buildings depend on a network of physical pathways that most occupants never see. Power enters through utility feeds. Data travels through fiber and copper pathways. Security systems connect through panels and low-voltage cabling. Building operations depend on electrical rooms, data closets, risers, conduits, and underground vaults.

These systems are often designed for efficiency. Several services may share the same riser, conduit, vault, or electrical panel. That can reduce construction cost and preserve valuable space. It can also create a single point of failure that affects the entire building.

In the latest episode of Built, Wired & Secured, Alex Morgan, Michael Harrington, and James Rogers examine how shared infrastructure can turn one physical incident into a building-wide outage. Their discussion offers a practical way for owners, property managers, facilities teams, and IT leaders to identify risk before it becomes an operational crisis.

One Physical Failure Can Affect Multiple Systems

Imagine a normal Tuesday morning. Tenants arrive, elevators are operating, Wi-Fi is available, access control is working, and the HVAC system is running. Then a single fiber line is cut or a utility feed fails. Suddenly, the building loses more than one service. Connectivity disappears. Card readers stop responding. Monitoring systems go offline. Building personnel may lose visibility into what is happening.

This kind of event is possible because multiple systems can depend on the same physical route. A conduit may carry cabling for several services. An underground vault may contain supposedly separate feeds. A single electrical panel may power both a core building function and the security equipment needed to monitor it.

The individual systems may each be reliable. The vulnerability is in the dependency between them.

The Drawings May Not Match Reality

One of the most important points from the episode is that documentation cannot be treated as the final authority. As-built drawings may show separate feeds or pathways, but the physical installation may have changed over time. Renovations, tenant improvements, repairs, and undocumented modifications can create dependencies that do not appear on current plans.

Michael describes a project in which the plans showed separate feeds for the data center and security system. The routes actually passed through the same underground vault. When a water main broke and the vault filled, both the electrical feed and fiber backbone were affected.

The building's generator started, but that did not solve the problem. It powered emergency lights and the elevator, while the network and security systems remained down because their shared path had been damaged. The lesson is clear: documentation is useful, but verification is essential.

Redundancy Must Be Physically Independent

Many buildings have a backup connection, a second utility feed, or a generator. Those resources can be valuable, but the existence of a backup does not automatically mean the building is resilient.

A backup connection that travels through the same trench as the primary connection can be lost in the same excavation accident. Two feeds that enter through the same vault can be affected by the same flood. A generator that does not serve the relevant electrical panel will not keep security or network equipment online during an outage.

True redundancy requires meaningful separation. The backup should be evaluated by asking several questions:

Does it use a different physical pathway?
Does it connect to a separate source or panel?
Can one incident affect both the primary and backup?
Is the backup tested regularly?
Does the documentation reflect the current installation?

James makes another important point: a backup that is never tested may be worse than no backup at all because it creates confidence without proving capability. Redundancy is only real when the organization knows what it covers and has verified that it works.

Risk Tolerance Should Drive Investment

Complete physical separation for every system can be expensive. Additional conduits, feeds, pathways, equipment, and maintenance all require investment. The right decision depends on what an outage would mean for the building and its occupants.

A hospital or data center may need extensive redundancy because the consequences of downtime are severe. A typical office building may choose a targeted approach. That does not mean accepting unnecessary risk. It means prioritizing the dependencies that would cause the greatest operational impact.

Owners do not necessarily need to rewire an entire building. A more practical first step may be adding a secondary path for security, confirming generator coverage, testing backup systems monthly, or improving documentation before the next renovation. These measures can reduce risk without requiring a massive capital project.

Coordination Between Trades Is a Resilience Issue

Shared infrastructure is particularly vulnerable when several contractors work in the same building. Electrical contractors, low-voltage contractors, and IT providers may all need space in the same riser. If their work is not coordinated, pathways can become overcrowded, existing cabling can be damaged, and future systems may have no usable route.

One example discussed in the episode involved a contractor cutting a shared fiber line during parking lot repairs. The line served the whole block, and the building lost internet connectivity for nearly a day. The building had a backup connection, but it traveled through the same cut, so it provided no protection. With connectivity down, tenants could not work normally, security systems went offline, and the management office had to handle the resulting disruption.

Coordination should begin before work starts. Contractors need to understand which pathways are critical and which systems depend on them. Owners and property managers should assign accountability for protecting shared infrastructure and documenting changes. A project is not complete simply because the new equipment works. It is complete when the work has not compromised the systems already in place.

Walk the Building and Ask the Right Question

The most practical advice from the episode is also the easiest to act on: walk the building. Visit the electrical room, data closet, and security panel. Ask facilities and IT teams where power and data enter the building. Trace the cables and inspect the pathways. Compare what is physically installed with what the drawings claim.

Then ask one question repeatedly: “What breaks if this goes down?”

The answer helps reveal the real business impact of an infrastructure failure. A single conduit may affect access control, network connectivity, and monitoring. A single panel may affect both electrical service and security. A single vault may connect systems that appear independent on paper.

Once those dependencies are known, the building team can prioritize improvements. Some risks may require a separate pathway. Others may be addressed through testing, labeling, contractor coordination, or updated documentation.

Build Resilience Before the Outage

Shared infrastructure is not automatically a design mistake. It is often a practical response to space, cost, and construction constraints. The risk comes from treating shared pathways as invisible or assuming that a backup is independent without verifying it.

Resilient operations begin with visibility. Map the dependencies, identify the shared pathways, test the backups, and make sure every trade understands what it is working around. These steps help building owners move from reactive repairs to deliberate risk management.

For a deeper conversation about infrastructure dependencies, redundancy, and practical building resilience, listen to this episode of Built, Wired & Secured. The best time to discover a single point of failure is before it fails.

The Single Point of Failure You Never Planned For: When Shared Infrastructure Becomes a Building-...

Show Notes