Why spare parts matter more than people think

This episode makes a simple point that many property teams learn the hard way: a building does not need a massive systems failure to create a serious tenant issue. Sometimes the problem is one small component. In the example that opens the conversation, elevators stall, lights go out on a floor, and a building dashboard shows a network uplink alarm. The root cause turns out to be a single SFP module. The part is inexpensive. The impact is not.

Michael explains that this is where many facilities and building technology teams get stuck. Parts like hot swap power supplies, SFPs, small battery modules, relays, or fuses are relatively cheap on their own, but if there is no compatible spare on site, the system has to wait. There is often no graceful degradation. Operations slow down, tenants notice immediately, and internal teams inherit the pressure.

The main issue is the mismatch between part cost and operational impact. A building can lose hours of productivity because of a component that might have cost very little to stock in advance.

What a practical spares program looks like

A key theme in the episode is restraint. The answer is not to buy everything and fill a room with hardware that will age out before it is needed. Michael calls that out directly as the easy trap. Overstocking ties up capital, increases obsolescence risk, and often leads to another problem: nobody owns the kit, so batteries age, firmware sensitive parts drift, and the inventory becomes unreliable.

Instead, he recommends a tiered approach:

A very small tier one kit for immediate recovery
Vendor and procurement fallbacks for less critical items
Clear ownership so the inventory actually stays usable

The goal is not volume. The goal is faster recovery from the incidents that create the most tenant pain.

The tier one items to prioritize first

Michael focuses on the parts that stop tenant operations and are hard to work around. He breaks the list into practical categories that listeners can act on quickly.

Hot swap power supplies for critical racks and UPS modules
Common SFP modules and at least one compatible spare type
Patch cables in common lengths and types
Door controller relays and small backup power modules for access control systems
Battery modules for emergency lighting and life safety panels
Fuses and surge protectors sized to common panels
Spare PoE injectors or a small edge switch for remote segments
Common sensors or thermostats if the building relies on single sourced devices
Manufacturer specific console cables and adapters
Labeling supplies, a continuity tester, and a small toolkit

His view is straightforward: seven or eight well chosen items can resolve the majority of incidents teams actually face. On paper, that list may look unremarkable. In operations, it can be the difference between a five minute recovery and a two hour outage.

A real example of cost versus impact

One of the strongest examples in the conversation is a campus incident involving a failed SFP during peak hours. Because a compatible spare was already in the cabinet, the team swapped it in within five minutes. Network service came back quickly, elevators returned, and the building avoided a much larger operational disruption.

Michael contrasts that with the alternative. Without the spare, the cost is not just the part and shipping. It is lost tenant hours, escalations, reputational damage, and in some cases tenant credits. That is why he keeps coming back to the same framing: the cost of the kit is often tiny compared with the cost of delay.

How to avoid obsolete or unreliable inventory

A spare parts program only works if the parts are still usable when the incident happens. The episode spends useful time on lifecycle management.

Michael recommends tying spare reviews to manufacturer life cycles and the building's capital plan. He suggests:

Reviewing firmware sensitive parts annually
Rotating or replacing batteries every year
Reviewing mechanical or passive items every 18 to 24 months
Maintaining a short list of preapproved alternates in case an OEM part is discontinued

That approach keeps the program lean while reducing the odds that a team opens the cabinet during an outage and finds a part that is expired, incompatible, or no longer supported.

Governance is what makes the kit work

Michael's final point is one of the most important in the episode: governance is the force multiplier. Even a modest kit fails if nobody owns it.

His recommendations are simple and practical:

Keep spares in one labeled cabinet
Use QR tagged inventory
Assign one owner, such as a facilities lead or tech operations lead
Reconcile inventory quarterly
Require a replenishment request within 48 hours of using a spare
Maintain a simple log of what was used, why it was pulled, and what replaced it

He also advises light routine testing instead of heavy process. Test batteries annually. Where safe, do insertion checks for hot swappable items every six months. Record firmware versions on inventory tags. Keep each cycle under 30 minutes so the process remains sustainable.

How to handle budget objections

For teams that hear, "We can't afford spares," Michael does not dismiss the constraint. He treats it as real, but manageable. His advice is to start small:

Identify the top five single point items that would stop operations
Fund those through O&M instead of capital where possible
Use vendor agreements, loaners, rapid ship clauses, or distributor consignment for larger or more expensive items

If leadership still pushes back, he suggests documenting one avoided outage and using the logged response time to show the return on investment. In other words, do not argue in theory when a short real world pilot can prove the point faster.

Three next steps to start this week

If you are building a spares program from scratch, Michael closes with three immediate actions:

Identify the top five single point items that would stop operations in your building
Create one labeled cabinet and assign an owner with quarterly reconciliation
Negotiate at least one vendor rapid ship or loaner agreement for items you cannot stock

This episode is a useful reminder that resilience is often built with small operational decisions, not large speeches about strategy. If the right part is on the shelf, clearly labeled, tested, and owned, recovery gets faster. If it is not, even a minor issue can become a tenant facing event.

The episode notes mention Michael's checklist and a GDS spare parts template to help property teams map their top five items and assign ownership.

Right parts, right place: a practical spare parts strategy for building tech

Building technology failures do not always begin with a dramatic event. Sometimes the disruption starts with a tiny missing part.

That is the premise behind this episode of Built, Wired & Secured. The conversation opens with a scene many property teams can picture immediately: a busy weekday morning, stalled elevators, lights out on a floor, and a building dashboard showing a network uplink alarm. After tracing the issue, the team finds the culprit. One small SFP module failed. There is no spare on site. The courier is two hours away, and tenants are already calling.

That story lands because it is ordinary. It is also expensive.

The episode argues that a deliberately small spare parts program can prevent this kind of escalation. Not a warehouse. Not a bloated inventory. Just a disciplined set of parts, ownership rules, and replenishment habits that help facilities and building technology teams restore service fast.

Why small parts create big building problems

Michael makes the core issue clear: many building systems depend on relatively small components that act as single points of failure. Hot swap power supplies, SFPs, battery modules, relays, fuses, surge modules, and other low cost items can halt larger systems when they fail. If there is no spare ready to go, the system waits.

That waiting period matters more than the price tag of the part itself. Tenants do not care that the missing component cost very little. They care that network access is down, access control is impaired, lighting is disrupted, or elevators are unavailable. The help desk gets flooded, escalation chains begin, and the operations team spends the next several hours managing a problem that might have been resolved in minutes.

This is where many ownership groups and facilities teams underestimate risk. They focus on the unit cost of the part and miss the operational cost of not having it nearby.

The goal is not to stock everything

One of the strongest parts of the discussion is the rejection of the obvious but bad answer: buy everything.

Michael describes overstocking as an easy trap. It ties up capital. It increases the chance that hardware becomes obsolete before it is used. It creates clutter. Most importantly, it often leaves teams with a false sense of readiness because nobody is actively governing the inventory. A shelf full of old batteries, incompatible optics, and undocumented parts is not resilience. It is deferred confusion.

His recommendation is a tiered model. Build a very small tier one kit for immediate recovery of the issues most likely to stop tenant operations. For everything else, rely on vendor support, procurement workflows, rapid shipping terms, loaners, or distributor arrangements.

That distinction matters because it turns spare parts planning from a procurement exercise into a risk management exercise. The question stops being, "What could we possibly need?" and becomes, "Which failures create the biggest operational pain, and what is the smallest kit that helps us recover fast?"

What belongs in a tier one kit

The episode gets practical quickly. Michael focuses on the items that are hard to work around and likely to interrupt tenant operations.

His examples include:

Hot swap power supplies for critical racks and UPS modules
Common SFP modules, with at least one compatible spare type on hand
Patch cables in the lengths and media types most often used in the building
Door controller relays and small backup power modules for access control systems
Battery modules for emergency lighting and life safety panels
Fuses and surge protectors sized for common panels
Spare PoE injectors or a small edge switch for remote segments
Common sensors or thermostats when the building depends on single sourced hardware
Manufacturer specific console cables and adapters
Labeling supplies, a continuity tester, and a small toolkit

He notes that seven or eight of these items will solve the majority of incidents he has seen. That is a useful rule of thumb for owners and operators who assume a worthwhile spares program must be complex or expensive. In practice, the highest value kit is often boring. That is exactly why it works.

The SFP example says everything

The episode returns more than once to the importance of common optics and other low cost network components. One example from a campus makes the point well. A bad SFP fails during peak hours. Because the building cabinet already holds a compatible spare, the team swaps it in within five minutes. Network service returns, elevators come back, and the incident does not spiral.

Michael frames the economics plainly. The spare may cost a few hundred dollars. The avoided impact can easily reach thousands in lost tenant productivity, not to mention internal disruption and reputational damage.

That is the value of a smart spares strategy. It compresses mean time to repair without requiring major capital outlay.

How to talk about budget without losing the argument

Budget pressure comes up directly in the episode, and the answer is practical rather than rhetorical.

Michael acknowledges that some facilities teams genuinely do not have room for broad spare parts purchases. His advice is to start with the top five single point items that would stop operations and fund those through operating and maintenance budgets instead of waiting for a capital project.

For parts that are bulkier, more expensive, or less likely to fail, he recommends supplementing the kit with external coverage:

Vendor agreements
Loaner arrangements
Rapid ship clauses
Distributor consignment options

If a CFO still refuses, his next move is to prove the point with logged results. Use a minimal kit. Document the next time it prevents a long outage. Show the time saved, the avoided escalation, and any avoided tenant credits. Real operating data wins budget discussions faster than abstract risk language.

That is a useful lesson for commercial real estate leaders. Resilience projects often stall when they are framed as insurance. They move faster when they are framed as measurable operational savings.

Governance is the difference between a spare and a liability

The best line in the episode may be Michael's closing point: governance is the force multiplier.

A modest kit can be effective if someone owns it. A larger kit fails if nobody does.

His governance model is intentionally simple:

Store spares in one labeled cabinet
Use QR tagged inventory for visibility
Assign a single owner, such as a facilities lead or tech operations lead
Reconcile inventory quarterly
Require a replenishment request within 48 hours whenever a spare is used
Keep a simple usage log that records what was pulled, why it was used, and what replaced it

This is not bureaucracy for its own sake. It is how a building avoids the common failure mode of a spare parts cabinet that looks full until the day it matters.

The same logic applies to testing. Michael recommends light, repeatable routines rather than heavy maintenance programs. Test batteries annually. Where safe, do insertion checks on hot swappable items every six months. Record firmware versions on inventory tags. If parts cannot be rotated, mark expiration dates and budget replacements into the annual plan. Keep the work under 30 minutes each cycle.

That last detail is important. A process that takes too long will eventually be skipped.

How this applies to building owners and property operators

For owners and operators, this episode is really about operational resilience. Tenants experience building technology as part of the core product. If access control fails, if network connectivity drops, if elevators go offline because supporting systems are impaired, the building does not feel well run. It feels fragile.

A spare parts strategy is one of the simplest ways to reduce that fragility. It supports faster incident response, lowers disruption, and gives teams a more disciplined way to think about recovery risk across low voltage, power, and connectivity systems.

It also creates a stronger bridge between facilities, property management, and technology operations. Instead of arguing over whose budget owns a part, teams can align around which failures matter most to tenant experience and business continuity.

Three actions to take now

Michael closes with a three step starting point that is hard to improve on:

Identify the top five single point items that would stop operations in your building
Create one labeled cabinet and assign one owner with quarterly reconciliation
Negotiate at least one vendor rapid ship or loaner agreement for items you cannot reasonably stock

That is a manageable starting point for almost any property team. It does not require a massive spend. It requires prioritization, ownership, and follow through.

If there is a broader lesson in this episode, it is that resilience often lives in small decisions. A building may have strong systems, solid vendors, and capable staff, but if the right replacement part is not in the right place when something fails, recovery still slows down. The practical win is not stocking more. It is stocking smarter.

If this topic sounds familiar, that is because it sits right at the intersection of building operations and technology governance. That is where GDS Technology does some of its most useful work: helping clients build environments that are easier to support, faster to restore, and less likely to turn small component failures into tenant facing events.

Listen to the full episode for the full checklist, the real world examples, and the governance guidance that makes a small spares program worth keeping. Then use it to map the top five items your property cannot afford to wait on.

Right Parts, Right Place: Practical Spare-Parts Strategy for Building Tech

Show Notes