Property managers across the United States wrestle with an expensive problem that rarely earns attention outside the industry. Many buildings burn through energy simply because their critical systems operate in isolation. Heating can surge while windows are left open. Cooling can compete with heat in neighboring zones. Cameras can capture hours of video that no one checks until after something goes wrong. The U.S. Department of Energy notes that commercial and residential buildings account for nearly 40% of America’s energy use, and a meaningful share of that total comes from operational inefficiency rather than unavoidable demand.
The issue becomes clearer when you step into the day-to-day reality of building operations. A typical property team may manage several separate platforms at once: HVAC controls from one provider, access systems from another, utility meters that still require manual work, and service-request tools that do not communicate with anything else. When a tenant reports a heating issue in the middle of the night, staff often have to jump between logins, scan disconnected dashboards, and sometimes travel to the site just to identify the cause. Many multifamily properties still depend on infrastructure installed 15 to 20 years ago, from an era when a “connected” building might have meant a basic programmable thermostat in a lobby.
That fragmentation also limits what leaders can learn from their portfolio. Questions that should be routine, such as which properties consume the most energy or how quickly repairs are completed, can turn into multi-day spreadsheet exercises. The operational picture stays blurred, not because the information does not exist, but because it is scattered across systems that were never designed to work together.
Turning a Mess Into One Operational View
Ashok Kumar Kalyanam encountered this kind of environment while leading a technology modernization effort for a residential portfolio spread across multiple locations. Each building had its own configuration, shaped by past vendors and incremental upgrades. Energy meters captured data locally but could not share it beyond the site. Maintenance history lived in email threads or paper logs. Even basic reporting demanded time-consuming manual compilation because there was no unified source of truth.
“We had operational silos everywhere,” Kalyanam recalls. “A maintenance issue in one building wouldn’t show up in portfolio analytics. Compliance audits required manual data gathering across properties. Real-time visibility simply didn’t exist.” The assignment was not just to introduce new tools, but to create a structure that could collect information from both aging equipment and newer sensors, centralize it, and present it in a way that operations teams could actually use.
He built a hybrid architecture anchored in AWS cloud infrastructure, forming a centralized repository where disparate building data could land and be organized. Building management systems, sub-metering, access controls, and edge devices fed into this hub so that the portfolio could be seen as a single operational environment rather than a collection of isolated sites. He also implemented OKTA for identity management, allowing property managers and maintenance teams to access the right data without weakening security controls.
The real challenge was never the shopping list of technologies. The difficulty was interoperability, especially across legacy systems. Older building equipment often speaks in protocols that modern applications do not recognize, and some devices were installed long before APIs were a standard expectation. To bridge that gap, edge computing devices were deployed to translate legacy data streams into formats that cloud systems could process. Data pipelines were designed for continuous updates rather than periodic uploads, giving teams near real-time insight across more than 1,000 residential units, including occupancy levels, energy draw, equipment condition, and open work orders.
Measurable Gains, and a Model That Scales
Once the systems could finally “see” each other, the operational impact became measurable in daily work. Administrative burden fell by about a quarter because staff no longer had to repeat tasks across multiple disconnected tools. Maintenance teams reduced average response time by 30%, helped by the ability to review equipment performance before leaving the office. Instead of arriving on site to diagnose an issue from scratch, crews could show up prepared with clearer insight and the right parts, which cut down unnecessary trips and accelerated repairs.
Energy performance improved as well. With consumption patterns visible at a meaningful level, waste became easier to spot and correct, and energy costs dropped by roughly 20%. Across the portfolio, that translated into more than $400,000 in annual utility savings. The improved performance also qualified the properties for $3.1 million in States Real-Time Energy Management incentive credits tied to sustained energy optimization.
Kalyanam also focused on ensuring that progress would not fade once the initial rollout ended. He introduced formal change request procedures so that ad hoc tweaks would not destabilize the platform over time. Managed service protocols supported continuous monitoring, and the work order system began generating tickets automatically when sensors detected performance outside normal ranges. For property managers, the difference was practical and immediate: a single view of portfolio status replaced the constant switching between tabs, tools, and passwords. “When we started, gathering data for a regulatory audit meant weeks of spreadsheet work,” Kalyanam notes. “Now it’s a button click.”
In an industry where many smart-building initiatives stall after installing sensors or isolated software, this approach held because integration stayed at the center of the design. The smart building market continues to expand, and Markets and Markets projects it will reach $328 billion globally by 2029, yet many projects fail to deliver meaningful improvement because they never solve the core problem of systems working separately. Kalyanam’s hybrid model was built to scale from the start, which helped it avoid becoming a one-off success confined to a pilot location. The organization preserved the architecture as a reference framework for future properties, making expansion less about reinvention and more about connection.
That scalability matters as pressure rises around energy efficiency and carbon reporting. Building performance standards tighten at the city level, investors demand ESG documentation, and tenants expect reliability and predictable costs. Buildings that cannot demonstrate strong operational control risk losing value. With commercial and residential buildings producing about 35% of U.S. carbon emissions, according to the Environmental Protection Agency, modernization cannot rely on tearing out everything and starting from scratch. This work showed a different path: a way to respect existing infrastructure while adding the connectivity and intelligence that modern operations require, one integration at a time.
