Spares, Swap Stock and Forward Stock Locations: Field Support's Quiet Engine

Every restore-time SLA is secretly a logistics promise. The engineer's drive is the visible part, but the clock is really decided by a quieter question: where was the replacement part sitting when the device failed? Get that answer right across a national estate and break/fix support becomes routine. Get it wrong and every incident includes a freight subplot.

Swap beats repair, almost always

On-site component repair died for good reasons: it takes longer, fails more often, and turns a store counter into a workbench. Modern field support swaps the failed unit for a known-good one, restores service in minutes, and takes the patient away for triage, repair or warranty recovery offline. The store gets uptime; the economics get sorted elsewhere.

Swap-based support has one dependency, though, and it is absolute: a pool of known-good, correctly imaged, serialised swap stock, positioned where the failures happen.

The geography of a spare part

Central stock is cheap to hold and slow to deploy. One warehouse serving the country means next-day restore at best for metro sites and multi-day for regional ones, with freight risk on top.

Forward stock locations (FSLs) put smaller caches of high-rotation parts near clusters of sites: a shelf in a metro depot, a locker in a regional hub. The cache holds what actually fails, lane printers, terminals, access points, not one of everything. FSL placement is an analytics exercise: twelve months of incident data, mapped against the estate, tells you where the shelves belong.

Boot stock rides with the engineer. For the highest-frequency failures in the densest territories, the fastest warehouse is the van.

A national support model blends all three, and reviews the blend quarterly, because failure patterns move as estates age and refresh.

Serial numbers or chaos

Swap stock only works when every unit is tracked at serial level: what it is, where it sits, what image it carries, whose asset register it belongs to, and where its warranty stands. The failure mode is familiar to anyone who has inherited a support contract: cupboards of unlabelled hardware in unknown states, functionally worthless the moment nobody can say which units are known-good. A spare that might work is not a spare, it is a second incident waiting at the same site.

Our swap pools live in the same integration centres that stage our deployments, which closes a useful loop: units returning from the field are triaged, re-imaged and returned to the pool on the same benches that prepared them originally, and warranty claims are chased while the paperwork trail is fresh.

The question for your provider

Ask one thing of any field support proposal: for our ten most common failures, where does the replacement part physically sit tonight, and how do you know it works? Providers with a real spares strategy answer in postcodes and processes. Providers without one answer in adjectives.

Want restore times measured in hours, not freight days? Speak to an expert.