What happens when the facilities engineer, project manager, or trusted vendor who understands a building’s technology is suddenly unavailable? The risk is not limited to missing passwords or outdated drawings. It can include undocumented sequences of operation, informal workarounds, unclear escalation paths, and maintenance decisions that exist only in someone’s memory. In this interview, Alex Morgan speaks with Michael Harrington and James Rogers about the operational cost of tribal knowledge across building systems. They examine how organizations can identify knowledge concentration, distinguish essential operating knowledge from excessive documentation, and create practical handoff routines without turning every project into a paperwork exercise. The conversation connects BAS, physical security, connectivity, and tenant operations to one central question: can the next qualified person safely operate and support the building? Listeners will leave with a practical way to test knowledge continuity before a departure, service transition, or emergency exposes the gap.

Planned maintenance is supposed to reduce risk, yet a poorly coordinated service window can interrupt access control, affect HVAC sequences, trigger alarms, or leave teams unsure whether a system is truly back online. In this interview, Alex Morgan speaks with Michael Harrington and James Rogers about the operational discipline behind safe maintenance in connected buildings. The conversation examines why routine work becomes risky when system dependencies are undocumented, stakeholders are notified too late, or testing focuses on individual components instead of occupant-facing outcomes. Guests will compare the priorities of property operations and facilities engineering, discuss how to define a maintenance window, and share practical questions teams should ask before, during, and after service activity. Listeners will leave with a lightweight coordination framework for scheduling work, assigning decision owners, validating recovery, and capturing lessons learned—without relying on product recommendations, sensitive site details, or deep configuration guidance.

Building technology often depends on digital accounts created for commissioning, maintenance, remote support, or integration. Years later, those accounts may still exist even though nobody can clearly explain who owns them, what they support, or what happens if they are disabled. In this episode, Alex Morgan speaks with Michael Harrington and James Rogers about the operational side of account ownership in commercial buildings. They explore how unclear responsibility develops across property management, facilities, IT, contractors, and service providers; why teams hesitate to change access that may support critical systems; and how poor records can complicate maintenance, troubleshooting, and business continuity. The conversation stays practical and vendor-neutral, focusing on accountable processes rather than technical configuration. Listeners will leave with a simple way to inventory building-related accounts, assign responsible owners, document business purpose, and review access during staff, vendor, and system changes—without waiting for an outage or security concern to expose the gap.

Modern buildings produce a constant stream of information from automation systems, equipment, access systems, networks, and service platforms. Yet the people responsible for energy, maintenance, security, tenant experience, and business continuity often cannot easily access or interpret the data they need. In this interview, Alex Morgan speaks with Michael Harrington and James Rogers about the data custody gap: who defines ownership, who validates information, who is allowed to use it, and who keeps it useful over time. The discussion moves beyond dashboards and technology features to examine practical operating questions: What data matters during a routine day? What becomes essential during an equipment problem? How should facilities and IT teams coordinate without creating duplicate processes? Guests share examples of how unclear responsibilities, inconsistent naming, and weak handoffs limit decision-making. Listeners will leave with a simple framework for identifying critical building data, assigning accountability, and making sure information survives staff changes, system upgrades, and vendor transitions.

Tenant improvements are often treated as isolated construction projects, but a new wall, relocated room, added equipment, or changed occupancy pattern can affect access control, connectivity, HVAC performance, life-safety coordination, and day-to-day operations. In this interview, Alex Morgan speaks with Michael Harrington and James Rogers about the invisible dependencies that appear when tenant work moves faster than building technology planning. They will examine how property teams discover changes too late, why facilities and technology groups are frequently brought in after decisions are made, and how seemingly minor modifications can create maintenance, security, comfort, or continuity problems. The conversation focuses on practical coordination rather than technical configuration: what questions to ask during scope review, which stakeholders must be involved, how to document impacts, and how to distinguish a manageable change from a future operational liability. Listeners will leave with a repeatable review mindset for tenant projects, capital work, and space changes—without relying on vendor-specific solutions or confidential project details.

A building can generate alarms for temperature, access, equipment, power, and connectivity, yet still lose valuable time because no one owns the response. In this interview, Alex Morgan speaks with Michael Harrington and James Rogers about the operational gap between detecting a condition and taking useful action. They explore how property teams and facilities leaders can distinguish urgent alarms from informational noise, assign responsibility across vendors and internal teams, and create escalation paths that work after hours. The conversation also examines the tradeoff between centralized monitoring and local expertise, why recurring alarms are often normalized, and how unclear handoffs affect tenant operations, equipment reliability, and business continuity. Guests will share practical examples without naming products, properties, or incidents. Listeners will leave with a simple framework for reviewing alarm ownership, response expectations, and follow-through before a routine notification becomes an operational disruption.

A utility interruption can turn a routine building dependency into a safety, security, and business continuity challenge. In this interview, Alex Morgan speaks with Michael Harrington and James Rogers about what actually happens between the moment normal power disappears and the moment operations stabilize. They will examine how power loss affects access control, elevators, HVAC, building automation, communications, tenant operations, and the teams responsible for responding. The conversation focuses on practical resilience questions: Which systems must remain available, which can pause, how should facilities and property teams coordinate, and where do backup systems create false confidence? Guests will share operational examples without identifying sites or vendors, emphasizing decision-making rather than equipment specifications. Listeners will leave with a simple way to map the first fifteen minutes of an outage, identify handoff gaps, and test whether their continuity plan reflects how the building really operates.

Building technology projects often reach turnover with every component installed, yet the first real problem reveals missing integrations, unclear responsibilities, or operating procedures nobody tested. In this interview, Alex Morgan speaks with Michael Harrington and James Rogers about what “ready” should mean before a new or renovated building technology environment is accepted. They distinguish installation from operational readiness, examine how to test dependencies across connectivity, access, life-safety-adjacent workflows, building automation, and maintenance processes, and discuss the tradeoffs between a fast handover and credible evidence that systems will perform. The conversation focuses on practical questions owners and facilities leaders can ask without requiring deep configuration expertise: What scenario was tested? Who observed it? What happens when a dependency is unavailable? Who accepts the remaining risk? Listeners will leave with a lightweight readiness framework for commissioning conversations, project closeout, and future capital planning—helping prevent “complete” systems from becoming operational surprises.

Modern buildings depend on automation for comfort, access, alarms, energy performance, and everyday operating decisions. But when a building automation system, supervisory interface, or connected service becomes unavailable, the real test is not whether a backup exists—it is whether people can use it under pressure. In this interview, Alex Morgan speaks with James Rogers and Michael Harrington about the human override test: how facilities teams and property leaders evaluate manual controls, decision authority, staff readiness, and operating procedures before an automation disruption occurs. The conversation explores why manual modes are often overlooked, how unclear ownership creates hesitation, and how to distinguish a workable fallback from a risky workaround. Listeners will learn practical questions to ask during design reviews, commissioning, maintenance planning, and operational exercises without getting buried in configuration details. The episode reframes resilience as a combination of technology, process, and human usability.

A modern building may label access control, HVAC, connectivity, life-safety support systems, tenant services, and building automation as “critical.” But when resources, backup capacity, maintenance time, or recovery attention are limited, treating every system equally creates confusion and weakens resilience. In this interview, Alex Morgan speaks with Michael Harrington and James Rogers about how to distinguish technical importance from operational consequence. They explore how a failed system affects occupants, tenants, facilities staff, security operations, and business continuity; why system rankings often differ between property management, IT, and engineering; and how to create a practical priority map without relying on vendor claims or complicated scoring models. Listeners will learn how to ask better planning questions, identify competing priorities, and turn vague criticality labels into shared decisions that guide maintenance, redundancy, staffing, and recovery planning.