Show Notes
The outage nobody plans for
The episode opens with a scene that feels painfully real in modern buildings: lunch hour hits, the network drops, point of sale terminals stop working, badge readers fail, and nobody can check visitors in. The carrier says the circuit is good up to the demarcation point. The building team says the handoff still belongs to the carrier. Tenants are calling, operations is under pressure, and the day ends before anyone fully sorts out who owns what.
That is the core problem in this conversation. The issue is not only technical failure. It is ambiguity. When the last meter between carrier service and building infrastructure is unclear, incidents take longer to resolve, responsibility gets blurred, and everyone loses time.
Alex Morgan sits down with Michael Harrington and James Rogers to break down how owners, operators, facilities teams, and IT teams can make that handoff visible, documented, and testable. Their message is simple: clarity at the demark shortens outages.
Why the demark gets messy
Michael lays out the routine failure modes that keep showing up around the handoff point. None of them are exotic. That is what makes them dangerous. They are common, preventable, and easy to ignore until the wrong day.
- Ambiguous ownership creates confusion before troubleshooting even begins.
- Poor labeling on panels, ports, and patch cords slows restoration work.
- Missing spares turn minor issues into extended outages.
- Single points of failure, like one building entry or no alternate power, raise the business risk far beyond the money saved up front.
The discussion makes an important point: good fiber does not help much if nobody can find the right panel, identify the right patch, or confirm who is allowed to touch it. When the first step in a failure is an argument, the outage is already longer than it should be.
Where the ownership line should be drawn
The group spends time on a practical question that comes up in procurement, turnover, and operations: who should own the fiber, the patch panel, and the power feeding the demark?
Michael offers a baseline that is easy to apply. The carrier owns up to a clearly marked demark point, whether that is a splice, handoff box, or patchfield. The building owns everything inside that point. When that physical handoff is defined in writing, accountability gets much cleaner.
James mostly agrees, but adds useful tension. He argues that owners should keep control over a small set of critical local elements, especially the first patch into the building panel and the UPS feeding edge devices. His reasoning is operational: if those pieces stay under owner control, the building team can perform local workarounds during an incident instead of waiting on carrier action.
That exchange is one of the most useful parts of the episode because it avoids a one-size-fits-all answer. The takeaway is not that every building should shift the line in the same direction. The takeaway is that the line must be specific, written down, and backed by shared expectations around spares, power, and access.
What a real acceptance test should include
The episode moves from theory into execution with a clear question: what should a joint acceptance test look like so neither side can later say, "it worked on our end"?
Michael outlines three core steps:
- Run an OTDR trace to establish a measurable baseline for continuity and loss up to the demark.
- Perform an end-to-end functional test, such as a loopback or authenticated ping, from the carrier endpoint to a building endpoint.
- Physically verify labeling and sign the demark diagram.
James adds the operational details that make those tests more useful in the field:
- Require two matching spare patch cords on site.
- Provide a labeled test port at the demark.
- Confirm whether the demark or its feeding equipment is on backed-up power.
- Include a contact and escalation list with names and roles.
- Record pass/fail thresholds, fiber loss values, test times, and technician names.
That last piece matters. A test is not just a checkbox. It is evidence. If the results are recorded clearly, the team has something objective to reference when an incident happens months later.
Two real examples that prove the point
The episode includes two short stories that show how low-effort controls can dramatically cut outage time.
In one campus example, the site had a single fiber entry and had relied on verbal handoffs for years. After a project, the team created a one-page demark diagram, required two labeled spare patch cords, and ran joint OTDR and ping tests. Later, an outside contractor cut the wrong sheath. Because the carrier could prove service up to the splice point and the building team had a spare patch ready, service came back in under an hour. No extended debate. Just a documented fix and an updated record.
In another example from a medical office, badge readers and nurse phones went down. The carrier said the circuit was fine. The building team found that an unlabeled patch had been rolled back during a vendor visit. Because they had a recent joint acceptance form and spares on site, they repatched immediately. Downtime was measured in minutes instead of hours.
Both examples support the same lesson: resilience at the handoff is usually built through documentation, labeling, spares, and testing, not through heroics during the outage.
The checklist listeners can use
For owners, operators, facilities leaders, and IT teams who want something actionable, the episode narrows the work into a short checklist that belongs in contracts, closeout packages, and operations documentation.
- A one-page demark diagram and ownership table
- A physical labeling standard with photos
- Two on-site spare patch cords
- A labeled test port
- Recorded OTDR or trace results and pass/fail functional test results
- A documented contact and escalation list
- Acceptance criteria, including loss thresholds, technician signoff, and power confirmation
- Contract language assigning responsibility for maintaining labeling and spares after turnover
The guests stress that these items should not disappear after project closeout. If labeling, spares, and ownership records are not maintained, the handoff will decay back into ambiguity.
Two actions to take now
The episode closes with two practical actions that almost any building team can start immediately.
- Find or create your building's one-page demark diagram and place it somewhere both facilities and IT can access.
- Schedule a joint acceptance test within 30 days if you have not run one since your last major change.
There is also a strong reminder to ask one business-centered question: what breaks if this goes down? That question helps teams prioritize redundancy where it matters most. Tenants feel outages first. Good design starts by understanding that operational reality.
Why this conversation matters
This episode is really about governance at the physical edge of connectivity. The line between carrier responsibility and building responsibility is easy to overlook until a failure forces everyone to look at it at once. By then, every missing label, undocumented splice, and verbal assumption becomes expensive.
The conversation argues for a different approach: define the handoff early, test it together, keep local spares, make ownership visible, and update the diagram after every change. Do that, and the last meter becomes boring in the best possible way. And in building operations, boring usually means reliable.
Clear handoffs keep building outages from turning into blame games
Modern buildings run on connectivity. That sounds obvious until the network drops in the middle of a workday and everyone learns, very quickly, how many systems depend on that one path staying up. Payments fail. Phones stop working. Badge readers will not authenticate. Front desk operations stall. Tenants start calling. Then comes the part that makes a bad incident worse: nobody agrees where the carrier stops and the building begins.
That is the problem at the center of this episode of Built, Wired & Secured. The conversation focuses on the demarcation point, the handoff between carrier service and building responsibility. It is easy to treat that boundary like a technical detail. In practice, it is an operational control. When the handoff is unclear, downtime stretches out while teams argue over ownership. When it is clear, documented, and tested, service gets restored faster.
The real risk is not just failure. It is ambiguity during failure.
The episode opens with a realistic scenario: a downtown office loses connectivity at lunch. Point of sale terminals fail. Badge readers stop. Nobody can check people in. The carrier says the circuit is good up to the demark. The building team says the demark is still on the carrier. Tenants do not care whose scope it is. They care that the building is not working.
That framing matters because it shifts the conversation away from abstract infrastructure talk and into business impact. This is not just about fiber, splice points, or patch fields. It is about how quickly a building can recover when something goes wrong.
One of the clearest ideas in the episode is that speed alone is not enough. Teams often rush during incidents, but speed without clarity leads to the wrong fix, duplicated effort, or no fix at all. Reliability starts before the outage, in the way the handoff is designed, documented, and maintained.
The failure modes are common and preventable
Michael Harrington outlines the routine failure modes he sees around the demark. They are not exotic engineering problems. They are the kind of operational gaps that quietly sit in the background until a disruption exposes all of them at once.
- Ambiguous ownership. The carrier, building team, and vendors do not agree on who touches what.
- Poor labeling. Panels, ports, and patch cords are unlabeled or mislabeled.
- Missing spares. A simple replacement patch is not available when needed.
- Single points of failure. One building entry, no diversity, or no alternate power creates fragile conditions.
That combination is expensive because it turns small technical faults into long operational events. You can have a perfectly healthy carrier circuit and still lose hours if nobody can identify the correct panel or find a spare cord. In other words, the issue is often not raw infrastructure quality. It is how usable that infrastructure is under pressure.
Where the ownership line should sit
The episode gets especially useful when the conversation turns to ownership. Who should own the fiber? The patch panel? The UPS feeding the demark? There is no value in pretending every property will answer those questions the same way, but there is a strong case for making the answer explicit.
Michael's baseline is simple: the carrier owns up to a clearly marked demark point, whether that is a splice, handoff box, or patchfield. The building owns everything inside that point. That structure makes accountability easier to manage and support obligations easier to enforce.
James Rogers agrees with the principle but pushes on a key operational nuance. Owners need control over a small set of local elements, especially the first patch into the building panel and the UPS feeding edge devices. If those items are locked into carrier control, building teams may lose the ability to make quick local workarounds during an incident.
That tension is productive because it gets to the real objective. The goal is not to hand every responsibility to the carrier or the owner. The goal is to assign responsibility in a way that speeds restoration, reduces confusion, and keeps the boundary easy to understand.
The compromise they describe is strong: define the exact boundary in writing, keep critical local spares and power under owner control, require matching spares and labeled handoff ports from the carrier side, and settle the rest through shared testing.
Testing makes the handoff real
Plenty of teams talk about documentation. Fewer teams make the handoff measurable. This episode is strongest when it moves from theory into acceptance testing.
Michael lays out a practical baseline for a joint acceptance test:
- Run an OTDR trace to establish continuity and loss to the demark.
- Run an end-to-end functional test such as a loopback or authenticated ping between the carrier endpoint and a building endpoint.
- Physically verify labels and sign the demark diagram.
James adds the details that turn a pass/fail event into a usable operational record:
- Two matching spare patch cords should be stored on site.
- A labeled test port should be available at the demark.
- The team should confirm whether the demark and its feeding equipment are on backed-up power.
- Contacts, roles, and escalation paths should be recorded.
- Loss thresholds, technician names, and test times should be documented.
This matters because incidents rarely fail in a perfectly clean way. Shared test evidence gives teams something objective to use when a future outage starts producing conflicting claims.
Why documentation and spares outperform improvisation
The examples in the episode make the business case better than any abstract argument could. In one campus case, a team had lived with verbal handoffs for years. After formalizing the process with a one-page demark diagram, two labeled spare patch cords, and joint OTDR and ping tests, they were ready when an outside contractor cut the wrong sheath. The carrier could prove the trace to their splice point. The building team had a spare patch ready. Service came back in under an hour.
In a medical office example, badge readers and nurse phones went down after an unlabeled patch had been rolled back during a vendor visit. Because the team had a recent joint acceptance form and spares on hand, they repatched immediately and kept downtime to minutes.
These are not stories about massive capital upgrades. They are stories about basic controls. That is the point. The fastest path to better uptime is often not another expensive platform. It is clearer accountability, better turnover discipline, and small operational safeguards that remove guesswork when time matters.
The checklist building teams should carry into procurement and turnover
One of the most practical parts of the episode is the short list listeners can use in contracts, closeout packages, and ongoing operations. The recommended acceptance packet includes:
- A one-page demark diagram and ownership table
- A physical labeling standard with photos
- Recorded OTDR or trace results
- A pass/fail functional test record
- On-site spare patch cords
- A labeled test port
- Documented contacts and 24/7 escalation steps
- Contract language tying all of the above to acceptance and maintenance responsibilities
That last item matters more than it may seem. Labeling standards and spare requirements tend to decay after turnover if they are not tied to responsibility. Without that accountability, the next incident will happen against a stale record set.
What owners and operators should do next
The episode closes with two actions that are easy to start and hard to argue with. First, find or create your building's one-page demark diagram and store it somewhere both facilities and IT can access. Second, schedule a joint acceptance test within 30 days if you have not run one since your last major change.
There is also a more strategic question worth carrying forward: what breaks if this goes down? That is the question that helps owners and operators prioritize redundancy where it matters. Not every system deserves the same investment. But the ones that affect tenant access, payments, phones, and core operations should not depend on fuzzy handoffs and undocumented assumptions.
For commercial real estate teams, this is a useful reminder that infrastructure governance does not stop at installation. The handoff between outside service and inside responsibility is part of the building's operating model. If you define it clearly, test it jointly, and maintain it over time, you reduce downtime and make incident response far cleaner.
If this topic hits close to home, the episode is worth a listen. It turns a commonly overlooked boundary into an actionable operating discipline, and the checklist at the center of the conversation is simple enough to use right away.