Machine Retrofit With Obsolete Parts: What an Independent So

Machine Retrofit With Obsolete Parts: What an Independent Sourcing Desk Actually Handles

When a panel shop starts a retrofit and the original PLC, drive, or I/O modules are out of production, the question is who locks down what is being replaced, what has to be re-engineered, and what has to be re-qualified. As an independent China-based industrial automation distributor and sourcing desk, we handle the line-by-line parts and the consolidated shipment; we do not write the engineering change order or sign off on functional safety. Below is what an honest retrofit engagement looks like when the original controls are obsolete.

The retrofit that looks easy on paper

A retrofit usually begins with a one-page summary: "replace the controls on machine #17, panel 2012, keep the motors and field wiring, run on PROFINET." The summary never mentions the four things that actually drive the project's cost and timing.

The first is the obsolescence map. A panel built twelve years ago typically mixes three or four hardware generations: a controller that was current in 2012, an I/O system that was already being replaced in 2014, a HMI panel that went end-of-life in 2018, and a few sensor or relay lines that were quietly phased out in the meantime. Each of those four layers has its own last-time-buy window, its own migration path, and its own firmware version matrix. A retrofit cannot be planned as a single parts order; it has to be planned as four parallel obsolescence checks.

The second is the wiring reality. Field wiring was installed against the original I/O layout, terminal numbers, and connector types. Swapping to a different family of I/O does not just mean new modules: it means new terminal assignments, new wiring diagrams, new DIN-rail cuts, and often new cabinet hole patterns. Any quote that comes back without naming which terminals move and which stay put is not a retrofit quote. It is a parts list.

The third is program portability. A controller swap in the same brand typically allows project import with a firmware migration; a cross-brand swap almost never does. Whether the existing logic can be lifted into a different programming environment, or has to be rewritten line by line, is decided by the customer's engineering team, not by the parts supplier.

The fourth is the documentation chain. A retrofit changes the machine's bill of materials, its wiring diagrams, its risk assessment, and, in many jurisdictions, its CE technical file. The parts we ship change the BOM and the wiring list. The risk assessment and the updated technical file are the customer's responsibility, and any desk that claims to "update your CE file" is overstating what a parts supplier can legally do.

What actually breaks when the original controls are obsolete

Three failure modes account for most retrofit overruns.

The first is the silently-upgraded module. A buyer sends a request for "the same module, just newer". The original part number has been replaced by a functionally similar module, but with a different firmware behavior, a different default configuration, or a removed feature. We see this most often with Siemens S7-300 family modules where a 6ES7321-1BL00-... and a 6ES7321-1BH02-... look interchangeable in the catalog but require different programming environments for the same signal. When we flag this on a quote, we do not propose a substitution; we propose a written line-by-line note that the customer takes back to their engineering review. The unknown axis here is the firmware_version axis: the manufacturer does not always publish the firmware behavior for every revision, and we will not infer it from a photo.

The second is the undocumented same-slot claim. Distributors who do not have the original manufacturer's cross-reference document sometimes describe a different-family part as a same-slot replacement on the basis of the photo. For a control panel, the photo is the least useful piece of evidence; wiring terminals, firmware versions, and program portability dominate. We refuse to issue any same-slot or no-rework claim on a retrofit line. If a documented cross-reference from the original manufacturer exists, we quote against it and note its reference number. If it does not, the line is held open until the customer confirms the choice against their own engineering judgment. verify against the original manufacturer datasheet and your own qualification process.

The third is the discount trap. The cheapest line on a retrofit BOM is rarely the cheapest total. A discontinued Siemens module at a low price per unit, with no firmware migration path documented, can cost more than a newer-generation part that is supported, programmable in the same environment, and covered by an existing migration guide. We quote both lines and let the customer choose. We do not write a recommendation that implies an engineering verdict.

A fail-safe case where we do not propose any retrofit line at all: if the original module sat inside a functional-safety circuit (a Cat-3 or Cat-4 stop circuit, a guard interlock, or a safety-rated I/O block on a SIL/PL path), we do not propose a migration path. SIL/PL qualification belongs to the customer's engineering team and their notified body; we only quote the part with the manufacturer-declared safety data sheet attached.

How an independent desk plans a retrofit honestly (the seven things we lock in)

Before we issue any quotation, we ask the customer or the engineering contact to confirm seven points in writing — by email, by marked-up drawing, or by signed proforma reference. We do not need all seven at the same time; we need them in the order they constrain the quote.

The exact machine identifier and the original equipment or installation line. Manufacturer, model, year, serial number, and the panel drawing revision. Without these, the discontinued line is unrecognizable to us.
The original MPN list, per row, including any "-0AB0" or function-state suffixes. Two parts that look identical in a photo can be a different revision.
The intended replacement family, if any. If the customer already has a target controller and I/O family in mind, we match against that. If not, we quote the original part and flag whether the franchised channel still has it, where the channel is dry, and what the documented migration path points to.
The wiring and cabinet boundary. Whether the new modules have to fit the same DIN-rail cut, the same terminal layout, and the same connector family, or whether the cabinet will be reworked. A no-rework line has to be qualified by the customer's engineering sign-off before we write the order.
The programming environment. Whether the existing program will be lifted into the same engineering software or rewritten. We do not lift programs; the customer's engineering team or a third-party integrator does that work.
The certification boundary. Whether the machine keeps its existing CE file, or whether the retrofit triggers a new risk assessment, a new technical file, or a functional-safety re-evaluation. We do not sign off on functional safety; we only confirm what each line we ship is and what the manufacturer declares it to be.
The shipping terms for the whole consolidated consignment. For Russia and the CIS, this is where EXW, DAP, and DDP come in, and the term written on the quotation is the term we use. Delivery is arranged under the term written on the quote; we do not write fixed lead times anywhere.

We screen end users and end uses, classify before quoting, and decline transactions that cannot be screened.

What we will not do on a retrofit

Three things sit outside what an independent parts desk can do, and naming them is part of how the engagement works.

First, we do not sign off on functional safety. A safety relay, an e-stop circuit, or a guard interlock is a system-level decision that depends on the customer's risk assessment, their category, and their application. We can quote the part, including its manufacturer-declared safety data sheet and SIL or PL rating where the manufacturer publishes one. We do not issue a SIL or PL verdict on a system that we did not design.

Second, we do not migrate programs. If the new controller requires a firmware upgrade, a different programming environment, or a different function-block library, the migration is done by the customer's engineering team or by a third-party system integrator. We do not run the migration, we do not host the engineering software, and we do not take responsibility for a program that we did not write.

Third, we do not take responsibility for a machine's compliance file. The CE technical file, the EAC declaration where Russian customs requires it for the final machine, the GOST-R registration, and the local industrial safety registration are the importer's and the machine builder's responsibilities. We can describe what the manufacturer publishes about each line; we cannot certify the machine.

The catalog side: where Phoenix Contact sits in our retrofit kit

Phoenix Contact shows up in our retrofit quotes most often in three roles: as a power-supply replacement for the original 24 VDC line, as an I/O block where the cabinet footprint has to change, and as a connection and terminal-block layer where field wiring has to be re-terminated without re-running the cable.

Phoenix Contact's QUINT and TRIO lines are the most common 24 VDC power supply replacements we see. They are widely available, the migration path is documented by Phoenix Contact themselves, and the dimensions and terminal layout are stable across generations. When the original panel used a different manufacturer's supply, we typically quote the Phoenix Contact equivalent alongside the original-spec line and let the customer decide which one fits their cabinet. We do not present the Phoenix Contact line as a like-for-like replacement; we present it as a separate line that the customer's engineering team chooses against the original datasheet. Mounting style, terminal layout, output current, and ambient temperature rating must each be verified against the original datasheet before the line is written.

For I/O, the Axioline F and Axioline E lines are the fieldbus-connected blocks we see most often on PROFINET and EtherNet/IP retrofits. They are a different family that the customer has chosen as the migration path. When we quote these lines, we quote against the customer's stated target family, and we do not propose a no-rework wording. The firmware_version and communication_protocol axes are typically the unknown axes on this kind of swap; we mark them as not directly verified unless the customer's datasheet comparison is on file.

For terminal blocks and marshalling, Phoenix Contact's CLIPLINE complete range is one of the denser kits we see in Chinese surplus and broker channels. This is the layer where the engineering team most often asks us to source from a known brand to keep the wiring diagrams readable to the downstream maintenance crew. We honor that, with the same caveat: each line is quoted per row against the customer's marked-up drawing.

The same honesty applies to the rest of our catalog: Siemens, Omron, Schneider, Mitsubishi, Inovance, WAGO, Weidmüller, Yaskawa, Delta, and others. We do not pick the brand for the customer. We pick the lines the customer has already chosen, or we quote the original line and flag the choices.

The RFQ side: how to send a retrofit BOM so we can quote line by line

A retrofit BOM is not the same as a maintenance BOM. Three points save days of back-and-forth.

Send the original drawing revision number, not just the panel name. A 2012 panel can have had three drawing revisions; the part numbers in revision B are not the same as in revision C.

Mark which lines are "exact match required" and which are "engineering-approved alternative". For the exact-match lines we quote only what the customer marks; for the alternative lines we offer the alternative and quote against the customer's engineering sign-off.

Send the target country and the Incoterm preference, even if you only have a rough idea. Russia, the CIS, and the EU all have different customs and shipping patterns; we quote against the term that the customer writes on the inquiry.

For a 20-line retrofit BOM we typically return a quote inside two business days. For a 100-line BOM we ask for five business days. We do not write a fixed lead time on the quote; lead time is something we confirm per line on the order acknowledgment, and the customer confirms against their own downtime plan.

The takeaway

A retrofit is a parts-and-engineering project, not a parts-only project. As an independent China-based industrial automation distributor and sourcing desk, we handle the parts side: the line-by-line match against the original MPN, the alternative-family lines that the customer has already chosen, the consolidated shipment under the term the customer has written on the inquiry, and the per-line condition (new surplus, refurbished, or used) on the order. The engineering-side re-design, the programming-side migration, and the compliance-side sign-off are the customer's, and we name that on every retrofit quote we issue.

If you have a retrofit in front of you, send the panel drawing revision, the original MPN list with suffixes, the target family if you have one, and the Incoterm. We will quote per line, confirm per line, and consolidate per the term on the quote.

Data Notes

By the aoctrl sourcing desk. Data through September 2026.
Phoenix Contact QUINT and TRIO 24 VDC power supply lines, Axioline F and Axioline E I/O blocks, and CLIPLINE complete terminal blocks are real product lines in the Phoenix Contact catalog. The references are descriptive of manufacturer-published positions, not compatibility verdicts.
Siemens S7-300 family module numbers (6ES7321-1BL00-..., 6ES7321-1BH02-...) are real Siemens catalog numbers, used as an example of which parts did not necessarily behave the same across revisions.
The seven lock-in points, the four respondents, and the three failure modes are descriptive of the engagement on the desk and are not a formal standard.

FAQ

What does an independent distributor actually do on a retrofit?

We source the parts per line, quote per line with the manufacturer part number, the condition (new surplus, refurbished, or used), and the term written on the quotation (EXW, DAP, or DDP). We do not write the engineering change order, the new wiring diagram, or the risk assessment.

Who does the program migration when the controller is obsolete?

The customer's engineering team or a third-party system integrator. We ship parts. The program migration is done outside our scope.

How long does a retrofit quote take to come back?

For a 20-line retrofit BOM, two business days is a typical turnaround; for a 100-line BOM we ask for five. Lead time on the parts themselves is confirmed per line on the order acknowledgment, not on the quote.

Can you sign off on functional safety for the new e-stop circuit?

No. Functional safety (SIL or PL) is a system-level decision based on the customer's risk assessment. We can quote the part and the manufacturer-declared safety data; we do not sign off on the system.

What condition do obsolete parts typically come in?

Per line on the quote. New surplus, refurbished (with a recorded bench test), or used (as removed, no test declaration). We do not mix the three conditions in a single line.

Do you take a partial retrofit BOM and add lines later?

Yes. We quote the lines you send first and add the lines you send later as a separate proforma. We do not enforce a minimum order quantity per line on a retrofit BOM.

What shipping terms are available for a retrofit consignment to Russia and the CIS?

EXW, DAP, or DDP, as written on the quotation. Delivery to Russia is arranged under the term the quotation states. We screen end users and end uses, classify before quoting, and decline transactions that cannot be screened.