Technology rarely fails on a convenient schedule. A building may have aging controls, cabling, security hardware, or connectivity equipment that still works—yet increasingly limits reliability, visibility, efficiency, or future support. This episode helps owners and facilities leaders make a disciplined decision before an urgent outage forces an expensive one. Alex Morgan speaks with Michael Harrington and James Rogers about how to evaluate technology at the end of its useful life without defaulting to replacement or accepting avoidable risk. They examine three questions: what operational evidence signals that a system is becoming a liability, how to compare retrofit options with full replacement, and how to account for dependencies such as workforce knowledge, documentation, interoperability, maintenance access, and business continuity. The discussion stays vendor-neutral and focuses on decision criteria listeners can use across commercial buildings, campuses, and operational environments. Listeners will leave with a practical way to prioritize refresh decisions based on consequences, not simply age or sales recommendations.

A building is often declared complete when construction is finished, systems are powered on, and punch-list items are shrinking. But operational readiness is a different standard: Can facilities staff respond to an alarm, can security maintain safe access during a connectivity interruption, can tenants understand what changes, and can the right people coordinate when multiple systems behave unexpectedly? Alex Morgan speaks with Michael Harrington and James Rogers about the overlooked gap between technical completion and dependable day-to-day operations. They discuss how to turn commissioning into realistic readiness testing, which cross-functional scenarios reveal hidden dependencies, and how to capture decisions, procedures, and escalation paths without creating an unmanageable paperwork exercise. The conversation stays practical and vendor-neutral, giving owners, facilities leaders, IT teams, and project managers a concise way to judge whether a building is truly ready for occupancy and ongoing service. Listeners will leave with questions to ask before accepting a project and a simple framework for finding operational risk while it is still affordable to fix.

A building system can be installed, monitored, and maintained by several teams—and still belong to no one when a problem occurs. Access systems, building automation, intercoms, environmental sensors, and connectivity services often cross organizational boundaries, creating delays, duplicated effort, and unresolved risk. In this episode, Alex Morgan talks with Michael Harrington and James Rogers about how property and facilities leaders can make technology ownership visible and actionable. The conversation examines the difference between technical ownership, operational responsibility, vendor support, and business accountability; why systems become orphaned after projects, staff changes, or reorganizations; and how unclear escalation paths affect tenants, maintenance teams, and continuity. The guests share practical ways to create an ownership map, define decision rights, identify after-hours responsibilities, and review accountability as systems evolve. Listeners will leave with a straightforward method for asking who monitors each system, who can authorize change, who responds first, and who ensures the system remains fit for purpose.

When a building loses connectivity, power, or access to its central security platform, the most important question is not whether the doors still work—it is whether they behave as the organization intended. In this episode, Alex Morgan speaks with Michael Harrington and James Rogers about the operational decisions behind access-control resilience. They explore how fail-safe and fail-secure choices affect occupants, emergency response, tenant operations, and after-hours maintenance; which dependencies owners should understand before an outage; and how facilities, security, IT, and property teams can agree on responsibilities before an incident occurs. The conversation stays above product and configuration details, focusing instead on decision criteria, recovery priorities, communications, and realistic tabletop scenarios. Listeners will leave with a concise set of questions to use during design reviews, system assessments, and continuity planning—helping them identify whether their building’s access strategy protects people, preserves operations, and remains manageable when normal connectivity disappears.

A building can have excellent equipment and still suffer an avoidable outage when several teams make individually reasonable changes without a shared plan. In this interview, Alex Morgan speaks with Michael Harrington and James Rogers about the overlooked discipline of coordinating maintenance across building automation, HVAC, access systems, networks, power-related equipment, and tenant operations. The conversation examines why maintenance windows are often missed, how dependencies create unexpected consequences, and how property and facilities leaders can establish a practical change calendar without adding unnecessary bureaucracy. Guests will share real-world examples of conflicting schedules, unclear approval paths, and work that seemed routine until it disrupted occupants or critical operations. Listeners will leave with a simple framework for identifying affected stakeholders, defining rollback expectations, communicating downtime, and reviewing outcomes. The episode focuses on decision-making and operational habits rather than product recommendations or technical configuration.

Many buildings appear resilient until the person who knows the quirks of the BAS, access systems, critical equipment, or vendor relationships is unavailable. This episode introduces the “3 A.M. test”: could the on-call team identify the problem, make a safe first decision, and reach the right support without relying on one individual’s memory? Alex Morgan speaks with Michael Harrington and James Rogers about how knowledge becomes trapped in people, why turnover and after-hours events magnify that risk, and how property, facilities, and IT leaders can improve operational continuity without creating giant manuals no one uses. The discussion covers practical ways to identify key-person dependencies, distinguish essential knowledge from nice-to-have detail, validate escalation paths, and build lightweight habits for sharing lessons after maintenance or incidents. Listeners will leave with a simple framework for making building operations more understandable, transferable, and dependable.

Modern buildings often make decisions through multiple systems at once: access control may indicate who is authorized to enter, building automation may adjust temperature based on schedules, and facilities teams may respond to actual conditions on the floor. The problem is not always a technology failure; it is often a mismatch between the assumptions built into each system. In this interview, Alex Morgan speaks with Michael Harrington and James Rogers about the operational tradeoffs that emerge when comfort, security, energy performance, and tenant needs compete. They will examine common coordination breakdowns, explain who should own cross-system decisions, and share a practical framework for reviewing schedules, exceptions, escalation paths, and manual overrides. Listeners will learn how to identify conflicting rules before they affect occupants, how to make exceptions visible without creating chaos, and how to use routine operational reviews to keep connected building systems aligned with real-world use.

A building can generate thousands of alerts, yet the most important one may be missed because every notification looks urgent. In this interview, Alex Morgan speaks with Michael Harrington and James Rogers about designing an alerting approach that helps facilities, property, and IT teams distinguish immediate threats from maintenance needs and informational events. The conversation examines why alarm fatigue develops, how unclear ownership creates delayed responses, and where automation can improve—or complicate—decision-making. Guests share realistic examples involving building automation, environmental conditions, access events, and equipment performance without relying on vendor-specific tools or sensitive site details. Listeners will learn how to prioritize alerts by consequence, establish practical escalation paths, and use recurring alert reviews to improve operations over time. The episode focuses on a durable principle: an alert is only valuable when the right person can understand it, trust it, and act on it. It gives leaders a concise framework for turning notification volume into operational awareness.

Modern HVAC relies on networks, cloud services, and interdependent systems. In this episode host Alex Morgan talks with Michael Harrington and James Rogers to unpack the operational consequences when HVAC controls lose connectivity — from tenant comfort and IAQ to business continuity and energy waste. We explore root causes (network outages, vendor remote-access dependence, power and controller failures), practical tradeoffs between centralized/cloud-based control and local autonomy, and low-cost resilience tactics that facilities and IT can implement quickly. Michael shares how outages translate into tenant impact and contractual headaches; James describes maintenance-first approaches that reduce downtime and preserve performance. The goal: give owners, facilities teams, and IT leaders a short, actionable roadmap to reduce single points of failure, align vendor responsibilities, and prioritize interventions that protect occupants and revenue without expensive rip-and-replace projects.

Modern elevators are no longer isolated mechanical systems — they are connected, software-driven platforms that touch safety, tenant experience, maintenance, and network risk. In this episode Alex Morgan interviews Michael Harrington and James Rogers about the operational realities and tradeoffs property teams face when elevator controls, remote diagnostics, and predictive maintenance systems join the building network. We unpack common single points of failure, how connectivity changes service and outage impact, what preventive maintenance and change control look like for elevator software, and how to balance vendor remote access with operational ownership. Listeners will get concrete questions to raise during procurements, a short decision framework for when to isolate vs integrate elevator systems, and real-world examples of resilience measures that preserve tenant uptime without compromising safety. Custom CTA: Download the episode's one-page 'Elevator Systems Operational Checklist' from gds-technology.com/bws-elevators to use with your next project or vendor review.