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.

Many building outages are the result of hidden, cross-system dependencies: a failed UPS that takes down access control, BAS sequences tied to a cloud service, or tenant-critical systems that share a common breaker. In this interview, host Alex Morgan speaks with Michael Harrington and James Rogers about building and using simple dependency maps to expose those domino relationships, prioritize mitigations, and make resilience decisions that align with operations and capital planning. We cover how to start a map with a single floor or critical tenant, choose the right level of detail, assign ownership, and turn the map into tests and maintenance tasks. Listeners will hear concise, real examples of dependencies that surprised property teams, practical rules for scoring critical paths, and a lightweight template you can adopt this week. By the end, you’ll have a clear framework to reduce blindspots, improve cross-trade coordination, and focus investments where they prevent the biggest outages.

Many buildings rely on a mix of automatic failover, manual procedures, and ad-hoc workarounds—but those choices are rarely tested together. In this episode Alex Morgan sits down with Michael Harrington and James Rogers to unpack realistic failover design for modern commercial buildings. We examine common causes of cascade failures across power, networks, BAS, and access control; weigh tradeoffs between automatic vs. manual failover, single points of failure, and the operational costs of redundancy; and hear concrete, non-technical examples of what worked (and what didn’t) when teams were pressed to keep tenants and systems running. Listeners will get practical rules of thumb for deciding where to automate, when to accept manual procedures, how to codify roles and escalation paths, and how to validate assumptions without expensive simulation. The episode closes with a concise checklist facilities and IT leaders can use to evaluate their current failover posture and prioritize fixes.

Most building teams plan for maintenance but rarely rehearse cross‑trade outages. In this episode Alex Morgan interviews Michael Harrington and James Rogers about running compact tabletop exercises tailored to building technology: networks, BAS, power, access control, and vendor dependencies. We frame a simple 60‑ to 90‑minute drill that reveals ownership gaps, single points of failure, communication breakdowns, and unrealistic vendor SLAs. Michael shares how drills change capital planning and tenant messaging; James explains realistic failure scenarios for HVAC and BAS that expose hidden assumptions. The conversation focuses on causes, tradeoffs, and practical steps: designing scenarios, selecting participants, documenting decisions, and turning findings into low‑cost mitigations and SLOs. Listeners will come away with a lightweight playbook to run their first drill this quarter, the top failure modes to prioritize, and how to convert exercise outcomes into durable operational changes.

Most building outages don’t start in the cloud — they start where fiber, copper, and power meet: the cable plant. In this 10‑minute interview Alex Morgan talks with Michael Harrington and James Rogers to map the common single‑point failures hiding in risers, closets, demarc rooms, and patching practices. We explain how procurement shortcuts, inconsistent labeling, contractor handoffs, and cramped closets turn a single cable or uncooled IDF into a building‑wide outage. Listeners will get a prioritized, realistic checklist for a 15‑minute on‑site audit, tradeoffs to weigh when funding redundancy, and governance steps to assign ownership between property, IT, and carriers. The episode ends with concrete examples from Michael and James’ operational experience and three immediate actions teams can take to reduce outage risk this month. CTA: grab the two‑page Cable Plant Audit checklist from GDS Technology to run your first assessment.

The Handover Playbook examines why most building technology projects falter after ribbon-cutting: information gets lost, ownership is unclear, and systems degrade because nobody knows how they were configured or who maintains them. In this interview Alex Morgan talks with Michael Harrington and James Rogers about practical closeout deliverables that facilities and IT teams will actually use—concise runbooks, verified spares lists, accessible network and power maps, and tenant handoff checklists. We explore the causes (project timelines, vendor assumptions, and handoff friction), the tradeoffs between thorough documentation and operational burden, and the long-term implications for maintenance, uptime, and capital planning. Listeners will hear real-world examples from commercial property and facilities leaders about handoffs that worked and ones that didn't, plus actionable steps for turning project closeouts into sustainable operations. This episode gives owners and operators a realistic playbook to reduce surprises, preserve institutional knowledge, and keep building systems reliable after vendors leave the site.

{"title":"Default, Deployed, and Deferred: The Operational Cost of Out‑of‑the‑Box Building Tech","one_liner":"How accepting vendor defaults for BAS, networks, and security creates quiet operational debt — and a practical playbook owners and facilities teams can use to fix it before it becomes an outage.","description":"Many building teams accept out-of-the-box settings on networks, building automation, security, and power because systems 'work' at install — and the defaults stay hidden until they cause alerts, energy waste, tenant friction, or outages. In this interview, Alex Morgan talks with Michael Harrington and James Rogers to unpack why defaults persist, who shoulders the risk, and how owners can convert defaults into intentional, documented baselines. The conversation surfaces root causes (installation timelines, unclear handoffs, and resource constraints), tradeoffs between speed and maintainability, and practical mitigations: commissioning checkpoints, minimal secure baselines, spares and firmware tracking, and lightweight post‑install audits. Listeners get concrete examples from property and facilities perspectives plus a prioritized 30‑day checklist to start reducing operational debt without disrupting tenants or projects.","why_now":"Defaults and handoff gaps are perennial in building projects; avoiding them is a persistent operational challenge rather than a time‑bound trend, so practical controls and governance remain valuable at any time.","target_audience":"Property owners, facilities leaders, IT and OT professionals, engineers, contractors, and commercial real estate operators who need practical steps to reduce operational risk and improve handoffs between vendors and building teams.","episode_type":"interview","estimated_runtime_s":600,"outline":["00:00-00:45 — Cold open / hook: A concise real-world anecdote where an out-of-box setting turned into a costly tenant complaint and system outage — frame the decision point listeners face.","00:45-02:00 — Context: Why defaults exist across BAS, networks, security, and power — installation pressures, vendor incentives, and common handoff failures explained for non‑specialists.","02:00-03:30 — Segment 1 — Causes: Michael and James describe typical project moments that lock in defaults (fast turnovers, incomplete commissioning, missing documentation) and who usually assumes ownership.","03:30-05:30 — Segment 2 — Tradeoffs and implications: Discuss the operational, security, energy, and tenant-experience tradeoffs of leaving defaults in place versus the cost of changing them.","05:30-07:30 — Segment 3 — Practical mitigations: Concrete patterns — baseline configuration checklists, commissioning gates, minimal telemetry, firmware/spare tracking, and low‑friction change control steps facilities can adopt.","07:30-08:45 — Expert examples: Michael and James share short, anonymized case studies where small configuration changes prevented outages or reduced costs, plus common pitfalls to avoid.","08:45-09:30 — Key takeaways: A concise, prioritized 30‑day plan and the top three configuration checks every building team should run this quarter.","09:30-10:00 — CTA and outro: Custom CTA — invite listeners to download a one‑page 'Default Baseline Checklist' from GDS Technology, share examples on social, and submit topics for future episodes; wrap up.","tags":["configurations","operational-debt","building-automation","facilities-management","risk-management"],"duplication_check":{"nearest_match_title":"Change Orders, Changed Networks: Managing OT/IT Change Control in Modern Buildings","similarity_score":0.48,"decision":"distinct"},"risks":["Discussion stays abstract without actionable next steps that listeners can apply immediately.","Guests may avoid discussing specific vendor behaviors, limiting practical examples.","Episode could exceed runtime trying to cover causes, tradeoffs, and examples within 10 minutes."],"mitigations":["Include a clear 30‑day prioritized checklist in the episode and reference it in the CTA so listeners have concrete actions.","Ask guests for anonymized, process-focused examples rather than vendor or product names to keep the conversation practical and on‑brand.","Use tight host moderation with timed segments and two micro‑prompts per guest to keep answers concise and ensure the episode stays within the 600‑second limit."]}

Renovations, pop-up tenants, construction sites, and special events all rely on temporary technology services: temporary power, rented network equipment, interim access control, and provisional BAS connections. Left unmanaged, those short-term fixtures become long-term operational debt that increases outage risk, complicates maintenance, and weakens security. In this episode Alex Morgan interviews Michael Harrington and James Rogers to unpack common failure modes, real-world examples, and pragmatic choices teams can make in the first 48 hours of a temporary deployment. We focus on ownership boundaries, minimal documentation, safe decommissioning, and low-friction checks that reduce downstream costs. Listeners will come away with a concise decision framework for approving temporary services, a short checklist to hand contractors, and guidance on when a temporary solution should be hardened or retired. This is practical, project-level advice for property owners, facilities leads, IT, and contractors who want to avoid surprise outages and unnecessary capital spend.

Many buildings assume electronic access control stays available — until it doesn't. This episode digs into how physical access systems behave when power, network, or backend services fail, and what facility and security leaders can do to keep people safe and operations moving. Host Alex Morgan interviews Michael Harrington and James Rogers to diagnose common failure modes (battery exhaustion, offline credential caches, carrier outages, human workarounds), walk through design tradeoffs between resilience and security (mechanical overrides, local caching, portable credentials), and highlight operational practices that reduce risk (routine tests, cross-team playbooks, and spare inventory). Listeners will get concrete decision criteria for choosing backup methods, short scripts for tabletop exercises, and a maintenance checklist to avoid the most frequent surprises. The episode prioritizes practical steps owners and operators can implement quickly to balance safety, access, and cybersecurity without major capital projects.

Buildings succeed or fail on small things: a replacement controller, a discontinued sensor, or a firmware image you can’t find. In this episode Alex Morgan interviews Michael Harrington and James Rogers about how end‑of‑life parts, firmware drift, and fragile spare inventories silently create outage risk and technical debt. We ground the conversation in real operational examples, then walk through pragmatic policies — spares strategy, firmware custody, lifecycle mapping, and procurement signals that matter to facility and IT owners. Listeners will get an actionable, prioritized set of steps to reduce surprise outages, protect tenant operations, and make maintenance budgets go further. This episode is practical, non‑technical, and designed so property owners, facilities leaders, and IT teams can start a 90‑day review that pays off immediately.