We Don’t Have Spare Parts When Critical Systems Fail: Building a Spares Inventory Strategy for Production IT

A $9 network module failed and took a plant down for a week. Not because the part was hard to find or expensive to replace. Because by the time they identified the problem, ordered the replacement, had it shipped, and got someone on-site to install and configure it, seven days had passed.

Seven days at hundreds of thousands of dollars per day in lost production. All for a $9 part.

This scenario plays out in manufacturing plants more often than you’d think. When critical IT infrastructure fails on the plant floor, the cost of downtime usually dwarfs the cost of the failed component. Yet many manufacturers don’t stock spare parts for their production IT systems. This isn’t a reflection of poor planning; it’s usually because nobody has clearly defined what spares are needed or who’s responsible for maintaining them.

Manufacturing IT disaster recovery isn’t just about backups and recovery procedures. It’s also about having the right parts ready when hardware fails.

Why Production IT Spares Are Different

Most manufacturers have good spare strategies for their production equipment. They know which mechanical parts are likely to fail. They stock critical components. They have relationships with vendors for fast shipping of specialized parts.

But production IT equipment often falls into a gap:

• It’s not treated like production equipment. The IT department might manage it, and IT typically doesn’t stock hardware spares; they just order replacements as needed. This works fine for office equipment,t where someone can wait a day or two for a new laptop. It doesn’t work for a switch that connects PLCs to your SCADA system.
• It’s not treated like mechanical equipment. Your maintenance team knows every bearing, seal, and motor on the line. But they often don’t know what network switch is in which cabinet, what firmware version it’s running, or where to get a replacement.
• The failure patterns are different. Mechanical parts often have predictable wear patterns. IT equipment can fail suddenly with no warning. A switch that worked perfectly yesterday can be completely dead today.
• The vendor landscape is different. Your production equipment might come from vendors you’ve worked with for decades who understand your urgency. Your IT equipment might come from distributors who treat your emergency like a routine order.

The Real Cost of Not Having Spares

When critical production IT fails, and you don’t have spares, here’s what actually happens:

Day 1: Diagnosis and Ordering

The problem occurs during production. Your team troubleshoots to identify the failed component. By the time they’ve confirmed the diagnosis and placed the order, it’s late afternoon. The part will ship tomorrow.

Production impact: Full day of downtime, possibly more if this happened overnight or on a weekend.

Day 2: Shipping

The part is in transit. Nothing you can do but wait.

Production impact: Another full day down.

Day 3: Installation and Configuration

The part arrives. But it needs to be configured. Maybe it needs to be loaded with the right firmware version. Maybe it needs to have specific settings applied. If it’s a PLC module or HMI component, it might need to be programmed.

If documentation is good and staff are available, this might take a few hours. If documentation is outdated or the person who knows the system is on vacation, it could take another day.

Production impact: Partial to full day, depending on complexity.

Total cost: Three days of downtime for a component that costs less than an hour of production.

What Belongs in a Spares Kit

Not every component needs to be stocked. The goal is to have spares for items that are:

• Critical to production
• Likely to fail
• Fast to replace when you have the spare on hand
• Slow to obtain if you don’t

Here’s what should typically be in a production IT spares kit:

Network Infrastructure

• Switches: At a minimum, spare switches that match your critical production network switches. These should be pre-configured with the same firmware version and basic settings.
• Cables: A selection of common Ethernet cables in various lengths. Cables fail more often than people think, especially on the plant floor.
• Power supplies: For switches and other equipment that use external power supplies, having spares prevents a $20 power supply failure from causing days of downtime.
• SFP modules and fiber cables: If you use fiber optic connections (common for longer runs on plant floors), spare SFPs and cables should be on hand.

HMI and Control System Components

• HMI computers or displays: Depending on your setup, either complete spare HMI computers or at least spare displays and input devices.
• PLC modules: The specific modules depend on your PLC platform, but commonly:
  – Communication modules (Ethernet, serial, etc.)
  – I/O modules that are heavily used
  – Power supply modules
  – CPU modules (for critical systems)
• Industrial PCs: If you use industrial computers for data collection, edge computing, or other plant floor applications, spare appropriate to your critical systems.

Wireless Infrastructure

• Access points: Spare wireless access points if your plant uses wireless for production systems.
• Antennas and mounting hardware: These can be damaged and aren’t always available quickly.

Server and Storage Components

• Hard drives or SSDs: If you have local servers supporting production, spare drives appropriate to your RAID configuration.
• Power supplies: Server power supplies fail regularly and can take down production systems.
• RAM: Memory failures happen, and the specific type might not be readily available.

The Firmware and Configuration Challenge

Here’s where the pares strategy gets complicated: having the physical hardware isn’t enough. The spare needs to be at the right firmware version and have the right configuration.

Firmware Version Management

When you buy a network switch today, it comes with the current firmware. But your production network might be running on firmware from two years ago because:

• You can’t easily take the network down to upgrade
• The current firmware version has been proven stable
• Other systems have dependencies on specific versions

If you pull your spare switch off the shelf and try to install it with new firmware, you might have compatibility issues. So your spares strategy needs to include firmware management:

• Document current versions. Maintain a list of what firmware/software versions are running on your production equipment.
• Maintain older versions. Download and archive firmware versions you’re actually using, not just the latest versions.
• Pre-configure spares. When possible, configure spare equipment with the correct firmware before you need it.

Configuration Management

A switch isn’t just plug-and-play on a production network. It likely has:

• VLAN configurations
• Port settings
• Security settings
• Management IP addresses
• Other specific configurations

Having detailed documentation of these configurations is critical. Even better is having pre-configured spares or configuration files that can be loaded quickly.

Where Spares Should Be Located

Having spares is only useful if you can access them when needed. Consider:

• On-site storage: For equipment that’s needed immediately during emergencies, on-site storage is essential. This should be in a controlled environment (not on the hot plant floor) but readily accessible.
• Regional spares: If you have multiple facilities, you might maintain a regional spares inventory that can be shipped overnight between locations.
• Vendor arrangements: For less critical items or very expensive components, you might arrange with vendors for emergency access to their inventory or expedited shipping.

The Lifecycle Challenge

Spares create a lifecycle challenge: the spare sitting on your shelf is aging without being used. Eventually, it might be as old as the equipment it’s meant to replace.

• Rotation strategy: Periodically rotate spares into service during planned maintenance and replace them with fresh spares. This ensures your spares are functional and relatively current.
• Technology refresh: When you upgrade production systems, update your spares inventory to match. Don’t leave spares for equipment you’ve replaced.
• Testing schedule: Periodically test critical spares to verify they’re functional. A spare that doesn’t work when you need it is worse than no spare at all.

Who Owns the Spares Strategy?

The biggest challenge with production IT spares is often organizational: who’s responsible?

• IT might say: “We don’t stock hardware. We order what we need when we need it.”
• Maintenance might say: “We handle mechanical spares, not computer equipment.”
• Operations might say: “We just need it to work. We don’t care who stocks the spares.”

Someone needs to own this. In an ideal scenario:

• IT and maintenance collaborate. IT provides the technical knowledge of what spares are needed and how to configure them. Maintenance handles physical inventory management, storage, and tracking.
• Operations provides the budget. The cost of spares should come from the production budget, not the IT budget, because these are production assets that prevent downtime.
• A single person is accountable. One person should be responsible for maintaining the spares inventory, ensuring it’s current, and coordinating restocking.

The Business Case for Spares

If you’re trying to justify the cost of a spares inventory, the math is straightforward:

• Calculate downtime cost: What does an hour of production downtime cost? Include lost production, labor, potential spoilage, and downstream impacts.
• Estimate failure frequency: How often do critical components fail? Look at historical data if you have it, or use conservative estimates.
• Calculate spare cost versus downtime cost: If a spare switch costs $2,000 and prevents even one day of downtime, what’s the ROI?

For most manufacturers, a basic spares kit costing $10,000-25,000 pays for itself with a single prevented incident.

A Practical Implementation Plan

If you don’t currently have a spares strategy for production IT, here’s how to build one:

Phase 1: Identify Critical Systems

Map your production IT infrastructure and identify what’s truly critical. What single failure would stop production or create safety issues?

Phase 2: Assess Current State

What spares do you already have? What’s missing? What condition are existing spares in?

Phase 3: Prioritize Acquisitions

You probably can’t buy everything at once. Prioritize based on:

• Likelihood of failure
• Cost of downtime
• Lead time to obtain if not in stock
• Cost of the spare

Phase 4: Document Everything

Create detailed documentation:

• What spares do you have
• Where they’re located
• What firmware/software versions should they use
• How to configure and install them
• Who to contact if you need help

Phase 5: Establish Processes

Define:

• Who maintains the inventory
• How spares are tracked and rotated
• When and how they’re tested
• How they’re replenished after use

Moving Forward

Manufacturing IT disaster recovery is about more than backups and redundancy. It’s about having the physical components needed to recover quickly when hardware fails.

The cost of a comprehensive spares inventory is usually less than a single day of production downtime. Yet many manufacturers don’t have this basic protection in place because they don’t understand the value, but because nobody has taken ownership of creating and maintaining it.

If you’re responsible for production uptime, take a hard look at your spares situation. Do you have the critical components needed to recover quickly from common failures? Are they properly configured and ready to deploy? Does your team know where they are and how to use them? These are exactly the gaps that a dedicated manufacturing IT services partner can help you identify, document, and resolve before a failure forces the conversation.

The time to answer these questions isn’t at 2 AM when production is down, and you’re waiting for overnight shipping. It’s now, when you can build a thoughtful spares strategy that protects your production capability.

That $9 part shouldn’t cost you a week of production. With proper planning, it doesn’t have to.