Why Building Networks Are Now Core Real Estate Assets

Most commercial real estate owners can tell you the age of the roof, the condition of the chillers, the status of the elevators, and the finish package in the lobby. But ask who owns the building’s network, where the access control data lives, or whether the Wi-Fi, cameras, lighting controls, thermostats, and elevators are riding on one coordinated system—or seven disconnected ones—and the room gets quiet fast. That silence is expensive. In Episode 42 of the Peak Property Performance® Podcast, we unpacked a simple but often overlooked reality: digital infrastructure is not just a technology line item. It is a building asset. And if you do not understand it, own it, and control it, someone else is making decisions that affect your operating costs, tenant experience, and long-term asset value. You can listen to the full episode here.

Digital Infrastructure Is the Asset Hiding in Plain Sight

Commercial real estate has always been comfortable with physical assets. Owners know how to think about sticks, bricks, glass, facades, signage, landscaping, countertops, amenity spaces, pools, and parking. Those are investments. They are designed, budgeted, maintained, and expected to create value. But when the conversation shifts to data & digital infrastructure, many owners still treat it like a nuisance expense—something they “have to do” because tenants expect connectivity or because a system vendor needs a network connection.

That mindset is the problem. The cables, racks, switches, wireless access points, sensors, cameras, thermostats, lighting controls, access control panels, elevator controls, and building management integrations are not random technology pieces. Together, they form the nervous system of the property. And just like plumbing or electrical, that system should be designed intentionally, documented clearly, and owned by the building—not casually handed over to whoever installed the last piece of hardware.

“Most owners think about buildings as sticks, bricks, glass, and amenities, but digital infrastructure is an asset too.”

Drew made the point in practical terms: if someone is struggling to understand “digital infrastructure,” start with the physical side. Walk into the building’s telecom closet. Look at the racks, cables, blinking lights, and connected devices. Those are tangible. You can point to them. But they are only the visible layer. The real value is what those systems enable: connectivity, automation, operating intelligence, tenant experience, energy optimization, security workflows, and eventually AI-ready decision-making.

This is where the owner/operator perspective matters. You would not let a third party quietly own your electrical risers or dictate how your plumbing infrastructure can be used. Yet owners routinely allow that exact pattern with digital systems because the infrastructure feels less familiar. The reframe is direct: If you don't own your data & digital infrastructure, your vendors do.

The Cost of Not Knowing What You Own

One of the most important examples from the episode came from a recent digital review we did with a building owner. The owner came into the conversation confident. He believed the property had a converged network and strong digital infrastructure. From his perspective, the building was ahead of the curve. That is exactly the kind of situation we like to see—because if an owner truly has a well-designed, owner-controlled network, our job is simple: confirm it, celebrate it, and help them keep building on it.

But when we reviewed the network documentation, the picture changed quickly. What the owner had sent over was not a full converged network map. It was a Wi-Fi network drawing. And in the bottom corner of that drawing was the name of an internet service provider. That detail mattered. We asked the basic ownership question: “Who owns this?” The initial answer was, “We do.” But when the owner pulled up the contract, the truth came out.

The provider had supplied the cable. The building had installed it. The provider owned it. The owner could not touch it, could not fully use it, and did not control it. In effect, the owner had helped install infrastructure inside his own asset that another party controlled for the life of the agreement—or until that provider chose to abandon it.

“They gave us the cable, we installed it, we installed all the sensors, they own it, we can’t touch it, we can’t use it, and it’s theirs for life until they abandon it.”

That is not a small administrative issue. It limits flexibility. It limits future integration. It limits the owner’s ability to connect other systems. It can complicate upgrades, tenant offerings, vendor changes, and even refinancing or sale diligence. The owner thought he had an asset. What he actually had was a dependency.

Once that became clear, we moved to the next questions: Where are the access control systems? Where are the lighting controls? Where do the cameras connect? What about HVAC controls, elevator systems, and other building sensors? The owner had those systems—but did not know where they lived, how they connected, which networks they used, or where the data went. At the end of the conversation, he said it was “brutally painful.” But it was also valuable. He now knew what he did not know, and that gave him the ability to build a strategy.

Stop Building Seven Networks When One Coordinated System Will Do

Drew used a simple analogy in the episode: we do not install multiple plumbing systems for every vendor that needs water. We do not build separate electrical infrastructure for every device that needs power. Yet in buildings, we regularly see separate networks for Wi-Fi, cameras, access control, HVAC, lighting, elevators, tenant amenities, parking systems, and more. Each one may have made sense in isolation. Over time, the result becomes operational clutter.

That clutter has real costs. Separate networks mean duplicate hardware, duplicate cabling, duplicate service contracts, duplicate maintenance processes, and duplicate points of failure. They also mean fragmented data. Your access control system knows when people enter. Your HVAC system knows when spaces are conditioned. Your lighting system knows when areas are occupied. Your cameras know movement patterns. But if those systems are isolated, the building cannot learn from itself.

This is why the PPP 5C™ framework matters. Owners need to Clarify what they have, Connect the right systems, Collect the right data, Coordinate operations across the asset, and Control the infrastructure and information that create value. You do not jump straight to automation or AI because a vendor has a new dashboard. You start by understanding the foundation.

• Clarify: What networks, devices, systems, contracts, and data sources exist today?
• Connect: Which systems should share infrastructure instead of operating in silos?
• Collect: What data is being generated, and where does it live?
• Coordinate: How can systems work together to reduce cost and improve experience?
• Control: Who owns the infrastructure, access rights, documentation, and data?

The owner in our example discovered that even though one network had effectively been given away, the situation was not hopeless. There were still other systems in the building. There were still opportunities to map the environment, understand contractual constraints, consolidate where possible, and make better decisions going forward. That is the practical point: this does not have to be fixed overnight. But it does need to be made visible.

For existing assets, that starts with a digital infrastructure review. For acquisitions, it means adding digital due diligence to the process—not as an afterthought, but alongside roofs, mechanicals, leases, environmental reports, and title. For developments, it means designing the digital infrastructure from the beginning so the building owner retains the value instead of unintentionally giving it away one vendor agreement at a time.

Start by Finding Out What You Actually Own

One of the most useful moments in the episode came from a real conversation we had with an owner who believed they had a converged network. On paper, that sounded right. In practice, the building had one network they could not touch because a provider had installed it, owned it, controlled it, and tied key systems to it. The owner could see the equipment. They could benefit from parts of it. But they did not own it, and they did not have the freedom to use it as the foundation for the rest of the building.

That is the uncomfortable part of this conversation. You may be able to point to the cable, the rack, the access point, or the sensor, but that does not mean you control the system. In this case, we started asking basic operational questions: Where are your access controls? Where are your lighting controls? Where do the cameras connect? What network are the thermostats using? Where is the data stored? Who has administrative access? The owner’s answer, after working through the list, was honest: “I just don’t know where they are and how they connect.”

“This was brutally painful. I’m sorry I wasted your time.”

Bill’s response was the right operator response: you did not waste our time. This is the work. The first step is not to make anyone feel foolish. The first step is to Clarify. That is why the PPP 5C™ framework starts there. Clarify what exists, who owns it, what it costs, what it touches, and what rights you have. Only then can you Connect, Collect, Coordinate, and Control in a way that protects the asset.

The encouraging part is that the situation was not hopeless. Even if one network had effectively been given away, the owner could still build a strategy around everything else. They could map the systems they did own, identify the systems they did not, decide whether to leave the provider-owned network alone for now, and create a long-term plan to regain control. That is a much better position than ignoring the problem until a renewal, capital project, tenant demand, or system failure forces an expensive decision.

Stop Treating Networks Like One-Off Vendor Decisions

Drew used a simple analogy in the episode: a teenager with a loud truck. At 16, the rumble feels like the point. But once that same driver has to pay for tires, brakes, fuel, and repairs, the driving changes. The system becomes real when the cost becomes personal. Buildings work the same way. A vendor-funded cable plant can feel like a win during development because it removes a line item from the budget. But if that decision creates duplicate networks, limits future integrations, or locks the owner out of useful data, the building pays for it for years.

This is where owners need to slow down and look at the whole system. When someone badges into the lobby, what actually happens? Which panel reads the credential? Which network carries the signal? Where is the controller? Is it connected to the same infrastructure as cameras, elevators, visitor management, lighting, and tenant connectivity—or is it sitting on Network A while the cameras are on Network 7 and the thermostats are on something else entirely? Redundancy can be valuable when it is designed for resilience. It is wasteful when it is accidental.

“Redundancies are only there if you designed them specifically to be in there. Sometimes they’re good. Oftentimes they’re not.”

We see this constantly in operating buildings. Owners are paying for multiple internet circuits, multiple service contracts, multiple boxes, multiple hubs, multiple repeaters, and multiple vendor-managed systems that could have been coordinated through a single building-owned digital backbone. One multifamily property we discussed avoided roughly $150,000 in unnecessary hubs and repeaters because the building already had infrastructure that could support the smart thermostats and door locks. Instead of interrupting hundreds of residents to install extra hardware, the team validated the devices in the lab and connected them through the existing system.

That is not theory. That is practical operating leverage. It reduces capital waste, lowers operating complexity, minimizes tenant disruption, and gives the owner a cleaner path for future systems. This is also why we compare data & digital infrastructure to a fifth utility. If you need to add a sink, you tie back to the main plumbing system. If you need more power, you tie back to the electrical distribution. You do not install a totally separate utility system every time a new device shows up. Your digital systems should be treated with the same discipline.

Make Digital Due Diligence Part of the Owner’s Playbook

One of the biggest reasons buildings end up with fragmented infrastructure is simple: nobody owned the design. Architects design the physical building. Engineers make sure it stands, drains, cools, heats, and complies. Contractors build what is in the drawings. But data & digital infrastructure often shows up late, sometimes 90 days before opening, when the property team realizes they need access control, cameras, Wi-Fi, elevator phones, emergency phones, lighting controls, thermostats, parking systems, EV charging, and tenant connectivity. By then, everyone is reacting.

That late-stage scramble creates expensive buildings. Systems get bolted on instead of designed in. Vendors bring their own networks because no one gave them a shared infrastructure to use. Data lands in separate portals. The property manager inherits complexity. Then, if the building is sold, the buyer usually completes physical due diligence but rarely performs a true digital infrastructure review. They inspect the roof, structure, parking deck, mechanical systems, and plumbing, but they do not inspect the asset that increasingly controls operations, tenant experience, risk, and intelligence.

That needs to change. If you are acquiring a property, make digital review part of due diligence before you close. Map the networks. Identify provider-owned infrastructure. Review contracts and administrative control. Confirm what systems are connected, where the data goes, and whether you can access it. Look for duplicated circuits, unnecessary monthly charges, unsupported hardware, unmanaged closets, and vendor lock-in. If remediation is needed, price it into the transaction instead of discovering it after close and absorbing the pain in your operating budget.

If you are developing, architect the digital layer from the beginning. Decide where closets go, how pathways are sized, what systems will share infrastructure, what standards vendors must follow, and what the owner will control. If you are operating an existing asset, start with a PPP 5C™ review: Clarify what is there, Connect the right systems, Collect usable data, Coordinate vendor activity, and Control the infrastructure as an owner-held asset. For a deeper dive into the operating philosophy behind this, we talk about it in the Peak Property Performance® book and regularly unpack real-world examples on the Peak Property Performance® Podcast.

The larger point is this: AI, automation, energy optimization, predictive maintenance, and better tenant experience all depend on a foundation. You cannot build intelligence on infrastructure you do not control. Vendor-specific AI tools may be useful inside individual platforms, but the real operating advantage comes when owners can see across systems—access, occupancy, energy, parking, lighting, connectivity, security, and service workflows—and make better decisions from their own data.

So the takeaway is direct. Walk your building. Open the closets. Ask who owns the network. Ask where the data lives. Ask what systems are duplicated. Ask which vendors have administrative access. Ask whether you can replace a system without losing the infrastructure beneath it. And ask these questions before a capital project, refinancing, acquisition, disposition, or tenant demand forces your hand.

If you don’t own your data & digital infrastructure, your vendors do. The good news is that control can be rebuilt. It starts with visibility, then strategy, then disciplined execution. Treat the digital layer like the building asset it is, and it will support lower costs, better operations, stronger tenant experience, and long-term Peak Property Performance®.

About OpticWise: OpticWise provides owner-controlled data & digital infrastructure for commercial real estate — from PPP Audits to portfolio-wide intelligence. See how we operate or read customer outcomes.