A conveyor stops on Monday morning after its variable-speed drive fails. The original model is discontinued. Maintenance finds a used unit online, the manufacturer offers a repair route, and an integrator recommends a current drive. Procurement now has three prices, but it does not yet have three comparable recovery plans. One quote may be for an untested box, one may require the failed unit to leave site for a week, and one may hide engineering, software and commissioning work behind the word replacement.
Treat stock, repair and migration as different routes to a safe restart. Compare the elapsed time, evidence, engineering work and failure exposure of each route against one exact Requirement. The lowest unit price is not the cheapest recovery if it misses the restart window or cannot pass the site's acceptance test. The fastest shipment is not the fastest restart if the unit does not match the installed hardware, firmware, communications or application.
Write the recovery clock before the purchase order
Start with two times, not one. The first is the latest safe restart time for the affected process. The second is the point at which a temporary recovery becomes unacceptable because it leaves the plant exposed to another failure. A stock unit may be the right bridge for a 48-hour restart and the wrong long-term plan for a line expected to run for another decade. A migration may be the right long-term plan and still be useless for this week's stoppage.
Record what the stopped equipment affects: the whole line, one redundant train, a quality check, a safety function or a convenience feature. Add the production window, access window, engineering availability and latest decision time. Do not convert lost-output estimates into confirmed financial loss unless the plant owner has supplied and approved those figures. The immediate purpose is to make the deadline and consequence visible to every bidder.
Freeze the installed baseline
The failed component is more than the family name on its front. Capture the complete manufacturer part or order number, series and hardware revision, rated voltage and power, firmware where it can be read, fitted options, connectors, network interface, mounting dimensions and surrounding equipment. Retain clear nameplate and connector photographs. Record the machine, panel position and function, plus the failure symptom and any diagnostic code.
Preserve the application evidence before removing or shipping the unit. That may include an authorised backup, parameter export, program version, network settings, licence position and wiring drawings. Do not assume those files exist or are current. State what has been recovered, when, by whom and from which device. If the unit cannot be powered safely, mark the missing data instead of guessing from a similar machine.
Check the manufacturer's current lifecycle record for the exact part. Rockwell Automation, for example, distinguishes Active, Active Mature, End of Life and Discontinued. Its own definitions say that a discontinued product is no longer sold, manufactured or procured, while repair or exchange may still be available. ABB uses Active, Classic, Limited and Obsolete for low-voltage drives and says the available services depend on the phase. Those labels are useful evidence, but they do not prove that a particular unit is in stock, repairable or suitable for the machine.
Route one: buy stock as a bridge
Stock is attractive when an exact compatible unit can arrive inside the recovery window. Ask the seller for the literal part number, series or revision, serial number, condition basis, photographs of the offered unit, test method and date, warranty, return terms, dispatch location and collection cut-off. Separate present physical stock from a product page, broker search result or supplier database entry.
Define compatibility before ordering. A matching family or base number may still leave differences in firmware, option cards, communications, safety features, input voltage or mechanical fit. The site's authorised engineer should decide what may vary and what must match. The acceptance plan should cover receipt inspection, configuration restore, installation checks, controlled start-up and the operating test needed for that application.
A bridge also needs an exit. Record whether the installed stock unit will remain, become the spare after repair, or be replaced during a planned migration. Without that decision, an emergency purchase can become an undocumented permanent design change.
Route two: repair or exchange the failed unit
Repair preserves the installed model and may reduce conversion work, but the quote must describe more than a bench fee. Confirm that the exact catalog number is accepted, whether the route is repair-and-return or exchange, the diagnostic stage, parts availability, expected turnaround, freight legs, warranty, test standard, treatment of configuration data and the point at which the provider can declare the unit beyond repair.
Rockwell's current industrial repair page describes repair and exchange services, including firmware and security updates where applicable. That is evidence that such service routes exist; it is not a promise that every discontinued unit can be repaired inside a particular plant's deadline. Ask for an item-specific confirmation and keep the failed unit's symptoms and service history with the request. If an exchange unit is offered, apply the same identity and compatibility checks as purchased stock.
Do not lose the only recoverable configuration by sending the unit before the backup question is settled. Also check whether opening, prior third-party work, contamination or physical damage changes the repair route or warranty. A repair that returns after the required restart is a resilience action, not the immediate recovery route. It can still become the future spare.
Route three: migrate to a current platform
Migration changes the system rather than replacing one box. Ask for the proposed target, replacement basis and full engineering boundary: panel and wiring changes, interfaces, software conversion, licences, safety review, cyber and network work, documentation, training, spares, commissioning, acceptance and rollback. A manufacturer's suggested replacement is a starting point for engineering, not proof of drop-in compatibility.
Siemens describes its automation migration service as five stages: initial analysis, concept development, engineering, implementation and commissioning. Its examples include hardware and HMI changes, application conversion and complete system modernisation. That scope explains why a migration quote cannot be compared with a stock-unit price alone. It also shows what a credible migration plan should make visible before the plant commits to a shutdown window.
Migration becomes more attractive when support has narrowed, compatible stock is uncertain, repeat failures are plausible, skills or software are disappearing, or several linked components are nearing the same lifecycle boundary. Those are decision inputs, not automatic triggers. The plant still needs a safe design, an approved change process and a tested cutover plan.
Compare the routes on one recovery sheet
- Elapsed time to accepted restart: availability check, approval, dispatch, transport, site access, installation, configuration, commissioning and acceptance.
- Technical fit: exact identity, allowed differences, application compatibility, software and licence needs, and the engineer who can approve the fit.
- Evidence quality: offered-unit photographs, test results, repair confirmation, engineering scope, exclusions and validity date.
- Failure exposure: chance that the unit is wrong, the repair is declined, the migration overruns or the same unsupported component fails elsewhere.
- Reversibility: return rights, retained failed unit, backups, rollback plan and ability to restore the previous operating state.
- Second-failure position: spare coverage, remaining repair route, support horizon, documentation and owner for the longer-term action.
- Comparable cost boundary: goods, freight, diagnostics, engineering, licences, installation, commissioning and any planned follow-on work, kept separate from unapproved production-loss estimates.
Illustrative worked example: a failed conveyor drive
This example is synthetic. A 7.5 kW conveyor drive fails at a packaging plant. The line can run a reduced schedule for 72 hours using another route, after which orders begin to miss their dispatch windows. Maintenance has the full drive identity, nameplate photographs, wiring drawing, parameter backup from six months earlier and a fault history. The installed drive is discontinued. No safety function is hosted in the drive, but the site's engineer must still approve the replacement and start-up test.
A specialist offers a matching series unit for next-day delivery, subject to photograph and serial confirmation. It is described as tested, but the test report and return terms have not arrived. The manufacturer confirms that the failed unit can enter diagnosis, with an illustrative five-working-day turnaround only after receipt; repairability is not yet confirmed. An integrator proposes a current drive, but needs a site survey, a revised panel drawing, parameter conversion and a planned commissioning shift. The three headline prices do not describe the same scope or restart date.
The plant runs two authorised tracks. It asks the stock supplier for the exact evidence and terms needed to approve the bridge inside the 72-hour window. It also books diagnosis of the failed unit so a successful repair can become the spare. The migration proposal moves into a planned-change review rather than the emergency purchase. If the offered stock fails the identity, condition or return gate, the operator knows before payment that the immediate route has failed and can reassess the production plan. The example does not assume that any route succeeds.
Failure modes that turn urgency into delay
- Comparing unit prices: the stock, repair and migration quotes exclude different work and reach different finish lines.
- Calling a replacement drop-in: the target part is treated as equivalent before firmware, options, communications, dimensions, software and application behavior are checked.
- Buying a listing: a web page or database result is accepted as proof of physical, dispatchable stock.
- Shipping the failed unit too early: the only current parameters or program leave site before an authorised backup is secured.
- Treating diagnosis as repair: acceptance into a repair process is reported as a confirmed return date or successful outcome.
- Skipping the site acceptance test: delivery is counted as recovery even though configuration, controlled start-up and process checks remain.
- Letting the bridge disappear into the asset base: the temporary unit remains installed without an updated record, spare plan or migration decision.
- Authorising beyond the Requirement: a request for evidence becomes permission to purchase, ship, repair or change the machine without the required owner approval.
The 15-minute move
Open one recovery sheet for the failed part. Add the exact identity, photographs, machine function, latest safe restart time, available backup and named engineering approver. Create three rows: stock, repair and migration. For each row, write the next fact that would make it usable or rule it out. That may be a serial photograph, an item-specific repair confirmation or a defined migration survey. Send those evidence requests before asking anyone to compare prices.
If you have one exact failed or obsolete part, bring the identity, available evidence, site location and recovery deadline to Find what you need. Middleman can prepare the private Requirement and qualified route questions without implying that stock, repair capacity or a successful outcome already exists.