Many buildings list two internet providers on a floor plan — but few can survive a real carrier failure. This episode walks property owners, facilities leaders, and IT teams through practical steps to design, validate, and operate carrier diversity that actually reduces outage risk. Alex Morgan interviews Michael Harrington and James Rogers about common misconceptions (separate ISPs isn't enough), physical-path realities in multi-tenant buildings, testing failover, coordinating carrier maintenance, and the operational tradeoffs between cost, uptime, and manageability. Guests share real-world examples of where redundancy failed and what simple, repeatable practices prevented repeat incidents: mapping physical routes, specifying true diverse meet-me rooms, documenting demarc and handoff responsibilities, scheduling staged failover tests, and building runbooks that include carrier contacts and validation checklists. Listeners will walk away with a short checklist and decision points they can apply on the next procurement, retrofit, or outage drill to make carrier diversity a reliable capability rather than a line item on a bid.

Many building systems—access control, BAS, security cameras, and tenant networks—still ride on aging low‑voltage copper or mixed cabling that wasn’t designed for today’s IP‑first world. This episode walks facilities and IT leaders through a practical, risk‑aware approach to cabling migration that minimizes disruption and preserves operational uptime. Host Alex Morgan interviews Michael Harrington and James Rogers to surface the real causes that keep legacy cabling in place, outline the tradeoffs between full rip‑and‑replace versus staged or hybrid strategies, and explain operational impacts like spares management, testing, and vendor coordination. Listeners get concrete examples from real projects, simple diagnostics to prioritize where to start, and an actionable checklist to plan pilot cutovers. The goal: make migration decisions that reduce long‑term risk without creating short‑term outages or cost shock.

Outages and near‑misses are inevitable in modern buildings, but the difference between a repeating failure and lasting improvement is what happens after the event. In this episode Alex Morgan interviews Michael Harrington and James Rogers about running fast, blameless post‑incident reviews tailored to building technology: what to capture, who to include, and how to convert lessons into capital planning, runbooks, and vendor accountability. We focus on practical steps that fit tight operational schedules: a lightweight agenda, evidence to collect without deep forensics, triage of root causes into operational, technical, and contractual fixes, and simple tracking to ensure action items become reality. Listeners will get a repeatable checklist and real examples of small changes that prevented repeat outages. This episode is for property owners, facilities and IT leaders, and contractors who need a pragmatic, nontechnical process to make buildings more resilient.

When a newly upgraded BAS, security system, or network goes live, the project team celebrates — then operations inherits surprises: missing documentation, unclear ownership, absent spares, and invisible failover steps. In this episode Alex Morgan interviews Michael Harrington and James Rogers to unpack the common failure modes during turnover from project to operations and offer a compact, repeatable handoff playbook. We diagnose the root causes (roles, incentives, and documentation gaps), examine the tradeoffs between speed-to-close and long-term operability, and surface pragmatic practices that reduce outages, speed mean-time-to-repair, and protect tenant continuity. Listeners get concrete examples from commercial property and facilities leaders, an operational checklist you can adapt this week, and guidance for structuring accountability into contracts and capital plans without getting bogged down in procurement or vendor picks.

Modern buildings rely on uninterrupted power for access control, BAS, network gear, and clinical or tenant-critical systems — and increasingly that reliability hinges on battery-backed UPS systems. In this concise interview, host Alex Morgan sits down with Michael Harrington and James Rogers to explain why backup batteries degrade silently, how procurement and maintenance decisions create hidden single points of failure, and what practical, cross-disciplinary processes stop batteries from turning a brief power blip into a multi-hour outage. You’ll hear real-world examples of unexpected failures, tradeoffs between monitoring investments and replacement schedules, and straightforward steps for testing, spares planning, and operational handoffs that facilities and IT can adopt immediately. By the end, listeners will have an actionable checklist to size monitoring, set replacement triggers, and align vendor contracts and internal workflows so backup power actually protects critical services.

Updates and firmware patches for building automation systems (BAS) and operational technology (OT) are necessary but often treated as a nuisance or a nighttime guesswork exercise. In this episode Alex Morgan interviews Michael Harrington and James Rogers about practical, low-friction approaches to patch windows: how to define safe update windows, who owns the checklist, how to stage and validate changes, and when to accept deferred risk. Guests share real-world tradeoffs—why a seemingly simple patch can cascade into tenant-impacting downtime, and how clear change control, short test cycles, and pre-validated rollback plans keep buildings operational. This episode focuses on coordination, not configuration: policies, roles, communication templates, and lightweight verification steps facilities and IT can adopt immediately to reduce operational risk while keeping systems current.

Tenants increasingly bring their own technology — smart sensors, networked AV, PoE devices, EV chargers, and edge compute — and those devices quietly shift responsibility, risk, and cost onto building owners and operators. In this interview, Alex Morgan talks with Michael Harrington and James Rogers about why tenant‑owned tech becomes an operational liability, how it manifests as hidden single points of failure, and practical governance patterns that balance tenant flexibility with building resilience. We cover clear ownership boundaries, lightweight contractual and technical controls (segmentation, power planning, documented spares), and simple verification practices that prevent ad‑hoc tenant installs from turning into recurring outages. The episode focuses on doable steps facilities and property teams can adopt immediately — no vendor deep dives, no legal advice — so owners, facility managers, and IT can keep buildings reliable while accommodating tenant needs.

Smart building sensors and edge devices often feel inexpensive at purchase — but over a building's life they create a steady 'sensor tax' in spares, firmware updates, security patches, interoperability fixes, and unclear ownership. In this 10-minute interview Alex Morgan sits down with Michael Harrington and James Rogers to unpack pragmatic ways to budget for device lifecycles, create firmware and spare-part practices that actually get used, and lock in ownership during project closeout. We'll examine typical root causes (procurement choices, undocumented customizations, missing spare inventories), tradeoffs property teams face (vendor-managed firmware vs. owner control, OEM spares vs. generic parts), and the operational implications for uptime, cybersecurity, and maintenance workload. Michael brings examples of outages caused by missing parts and ownership gaps; James lays out preventive maintenance and inventory routines that scale. Listeners leave with a short checklist, vendor questions for procurement, and concrete steps to operationalize firmware and spare management across facilities and IT.

Buildings are a tangle of interdependent systems, but repairs and recoveries still happen person-to-person. This episode shows how translating tacit operational knowledge into short, testable runbooks and lightweight automation—what we call Maintenance-as-Code—reduces downtime, handoff friction, and vendor confusion. Host Alex Morgan talks with Michael Harrington and James Rogers about why many post‑project handoffs fail, how to scope runbooks so they're actually used, and where automation delivers value without adding brittle complexity. Expect concrete patterns for ownership, simple triggers and acceptance criteria, test cadences that fit busy operations teams, and examples of runbooks that prevented real outages. By the end listeners will know what a one‑page operational play looks like, which checks to automate first, and how to make maintenance artifacts live documents rather than archived PDFs.

When power goes out, the order of who stays on can determine whether a building keeps operating or grinds to a costly stop. In this episode Alex Morgan sits down with Michael Harrington and James Rogers to unpack a repeatable approach for prioritizing critical electrical loads in commercial buildings. We walk through mapping dependencies between life-safety, access control, communications, HVAC, tenant-critical loads and business continuity systems; weigh resilience versus cost and tenant expectations; and create simple, testable rules that stick through staff changes and vendor turnover. Guests share real-world examples from operations and capital planning, plus an easy prioritization checklist listeners can use during design reviews, outages, or budget conversations. By the end, facilities and IT leaders will have clear next steps to reduce single points of failure and make outage decisions that are defensible and operationally executable.