When a Substitute Is the Wrong Answer: Five Cases Where You

When a Substitute Is the Wrong Answer: Five Cases Where You Should Stop Sourcing and Call the Engineer

A cross-reference request for a discontinued industrial automation part is often an engineering question disguised as a sourcing question. In five recurring situations — safety-rated chains, approval-locked assemblies, undocumented firmware, ownership-of-qualification disputes, and lifecycle-footprint shifts — the responsible answer is to stop the substitution and bring the customer's engineer into the conversation. We document the situation, quote the original part from the independent channel where remaining channel stock is on the shelf, and decline to put our letterhead on a qualification that belongs to the customer.

The cross-reference request looks simple, and that is the trap

A buyer writes: «Нужен аналог [part] — что подходит?» — I need an analog of [part] — what fits? The shape of the question is binary. The shape of the real engineering decision behind it is not. Industrial controls live on firmware revisions, communication protocols, terminal assignments, project documentation, and approval files. Two parts that look identical in a photograph can sit at claim level 0 (documented drop-in) or claim level 1 (visually similar outline) — and the difference between those levels can be a working machine or a stopped line.

We use a 12-axis comparison framework (form and fit, dimensions, terminal and interface assignment, electrical parameters, function and I/O, firmware version, communication protocol, mechanical parameters, environmental class and EMC, ingress and temperature, materials, certifications and lifecycle). For every cross-reference we publish we mark each axis matched, differs, or UNKNOWN — and the rule is that an axis with no documented evidence is written as UNKNOWN, not as a quiet assumption. The same rule applies in reverse: when the answer should be "do not substitute," that answer is itself the responsible answer. Here are the five cases where the answer is to stop.

Case 1 — The part sits on a safety circuit that someone signed for

Functional safety components — safety relays, safety light curtains, emergency-stop devices, dual-channel monitoring — are not interchangeable across brands even when the catalog numbers look adjacent. The substitution is not just about contact arrangement and response time. The safety function is a documented claim: a SIL/PL rating attached to a specific hardware and firmware revision, often paired with a specific wiring diagram and a specific configuration tool. When we receive a request to cross-reference a Pilz or Sick safety relay against a non-OEM equivalent, the responsible answer is that we do not produce a comparison at all. The competence for that decision sits with the customer's safety engineer, with the machinery's CE technical file, and with the notified body if one is involved. Our desk can still help the buyer in other ways — supplying the original part from the franchised or independent channel, or sourcing an unrelated BOM line that does not sit on the safety chain — but the safety line itself is not a candidate for an analog we would publish.

The same applies to the question «какие компоненты нужны для аварийного останова?» — which components for an emergency stop — at the system level. We can quote the parts. We do not certify the safety function. We do not run a repair service, we do not recondition safety devices, and we do not retest them to a different revision. If you need a second source for a safety device, the second source must come from the original manufacturer's own published cross-reference or migration document, with the safety dossier updated to match. Otherwise the assembly is no longer the assembly the original approval covered.

Case 2 — The part carries an approval that is locked to a brand, a file, and a revision

CE / UL / CSA / EAC / TR CU declarations are not generic. A declaration of conformity covers a specific model, a specific revision, and often a specific configuration of accessories. Two sensors from the same series — say a Sick WTB4 and a WTB4 of a different suffix — can share a catalog family but sit on different approval files. The substitution looks cheap on paper. The real cost is the customer discovering, six months after installation, that the technical file does not cover the unit they are running. The customer in Moscow or in Novosibirsk who imports the unit under DDP with our proforma invoice still owns the importer-side declaration of conformity — our role stops at the shipment, and the importer is the party named on the customs file.

This is the case that hurts the slowest. The buyer finds a like-for-like, ships it, installs it, and the line runs. Months later, an audit or an incident draws the technical file, and the substitution is found. At that point, the substitution is no longer a sourcing question — it is a compliance question, and it costs the customer an order of magnitude more to unwind than to do it correctly the first time. For us, the responsible move is to surface the question before the quote goes out: which approval file is this unit covered by, and does the candidate part sit on the same file? If the answer is "we don't have a file" or "the part is from a different family," we put the substitution on hold. We screen end users and end uses, classify before quoting, and decline transactions that cannot be screened, and that classification is where this case is caught before it ships.

Case 3 — The firmware, hardware version, or project file is undocumented

A PLC, a drive, a remote I/O station, an HMI panel — almost every modern control device carries two layers. The hardware is the visible assembly. The firmware, the engineering-software project, the GSD/GSDML/EDS/ESI files, and the license terms are the invisible assembly. When a buyer writes «нужен аналог модуля ввода-вывода» — I need an analog of the I/O module — they usually mean the hardware. The engineering reality is that the hardware has to host a project file that was built around a specific device description and a specific firmware range.

A cross-reference report that does not address the firmware axis is incomplete. The most common failure mode we see is a buyer installing an analog module, importing the original project, and watching the controller either reject the station or silently downgrade the diagnostic coverage. Both outcomes are worse than the original obsolescence. The responsible response when the firmware axis is UNKNOWN is to refuse to publish a substitute recommendation at all — to tell the customer that the substitution may require a project rebuild, that the rebuild is engineering work their team must lead, and that we can supply the original part as a no-rebuild path while the project is migrated. We do not run that rebuild on the customer's behalf. The rebuild, and the bench-testing that follows it, sits with the customer's engineering team and the integrator they appoint.

This is also where "visually similar outline" gets buyers into trouble. Two ET 200S modules with the same housing can sit on different function states and require different device descriptions. They look identical in the cabinet. They are not identical to the controller.

Case 4 — The customer wants us to validate a substitution their engineer will not sign

Sometimes the request arrives shaped like a sourcing question but is actually a responsibility question. The buyer's engineering team has either declined to sign a substitution, or has not been asked. The buyer then approaches an independent desk looking for a written cross-reference report they can take back into the project meeting. The trap is that a sourcing desk's written report is not an engineering qualification. Our /compare output is a line-by-line comparison on the 12 axes, with UNKNOWN marked UNKNOWN, with a verification clause that says verify against the original manufacturer datasheet and your own qualification process. It is not, and cannot be, the engineering sign-off.

When we detect this shape of request — usually by reading between the lines of the inquiry — we change the response. We will quote the original part from the franchised channel or the independent channel. We will quote a candidate part on the same line. We will produce a written comparison with the 12 axes filled in to the extent our catalog and the manufacturer's published data allow. We will not put our letterhead on a statement that the substitution is fit for purpose. That statement belongs to the customer's engineering function, with the customer's qualification process, and with the customer's signature on the engineering change order. The written report we supply is evidence for that conversation, not a substitute for it.

Case 5 — The substitution would silently change the BOM's lifecycle footprint

The last case is the one most buyers never ask about, and it is the one with the longest tail. A discontinued part is replaced by a current-production part, and the immediate problem is solved. Six years later, when the new part is itself discontinued, the customer is back at the sourcing desk — except this time the original equipment documentation still references the old part number, the spare-parts list still references the old part number, and the maintenance team's training still references the old part number. The substitution that solved today's problem has multiplied tomorrow's.

This is the lifecycle axis at work, and it is the axis most often left blank in a casual cross-reference. The responsible response is to flag the lifecycle footprint of any substitution that crosses a generation boundary — and to ask whether the customer wants the substitution written into their documentation, or whether they want the substitution treated as a one-time bridge that will be replaced again in the next maintenance cycle. We do not make that decision for the customer. We do make sure the question is on the table before the shipment leaves the warehouse.

What we will do instead in these five cases

For each of the five cases above, the answer is not "no" — it is a narrower yes. We will still source the original part from the franchised channel or the independent channel, where remaining channel stock is on the shelf or reachable on a quoted lead time. We will source unrelated BOM lines that do not sit on the disputed chain. We will produce a 12-axis written comparison for the buyer to take into their engineering meeting, with the UNKNOWN axes marked as such. We will quote a candidate part on a separate line so that the buyer can see the price, the lifecycle stage, and the lead time without committing to a substitution. We screen end users and end uses, classify before quoting, and decline transactions that cannot be screened — and that classification is the point at which cases 1, 2, and 3 above are surfaced, not buried. Where the destination is Russia or a CIS country, the quote is issued EXW, DAP, or DDP as the buyer's procurement team specifies, and the commercial invoice, packing list, and proforma invoice travel with the shipment per our standard terms of sale.

If you are looking at a substitution that you suspect falls into one of these five cases, the most efficient first message is a short one: the part number, the application context (one or two sentences), the approval file that covers the assembly if known, and the question you actually need answered. Send it through /inquiry or alongside the BOM line in /procurement. We will tell you on the first reply whether the substitution is in scope for a written cross-reference report, or whether the next step is to bring your engineer into the conversation before we add a line to the quote.

The takeaway

A substitution is the right answer when the 12 axes can be checked, the firmware and approval files align, and the customer owns the qualification decision. A substitution is the wrong answer when any of those five cases above is in play. The shortest path through either scenario is the same first message: the part number, the context, the approval scope, and the question. From there, the answer is either a written comparison or a referral to your engineering function — and either answer saves the line, the file, and the budget.

FAQ

What does it mean when a substitution is written as "requires verification against the original manufacturer datasheet"?

It means the cross-reference report has checked what could be checked against published manufacturer data, but the engineering qualification — the work of confirming the substitute behaves correctly in your specific machine, project file, and approval scope — has not been done by us. That work belongs to your engineering function, because it depends on your project file, your wiring, and your safety dossier. The report is evidence for your qualification conversation, not a replacement for it.

Can you cross-reference a safety relay, light curtain, or emergency-stop device against a different brand?

We do not produce that comparison. A safety function is a documented claim attached to a specific hardware and firmware revision, a specific wiring diagram, and a specific configuration tool. Any second source has to come from the original manufacturer's own published cross-reference or migration document, with the safety dossier updated to match. If you need a second source, send us the manufacturer part number and the safety dossier reference, and we will tell you what the OEM's own migration path looks like.

How do you handle a cross-reference where the firmware version or the engineering-software project file is unknown?

We mark the firmware axis and the project-file axis as UNKNOWN, and we surface that UNKNOWN on the first reply rather than in a footnote. The substitution may still be possible — many projects are rebuilt rather than migrated — but the rebuild is engineering work, and we name it as such before we add the line to the quote. We can quote the original part as a no-rebuild path while the project is being migrated, and we can quote the candidate part as a separate line so the price and lead time are visible without committing to the substitution.

What if my engineering team has already declined to sign off on a substitution?

Send us the part number, the reason for the decline (one sentence is enough), and the original part you would accept as the no-substitution path. We will quote the original part, quote the candidate part as an alternative line, and produce a written comparison on the 12 axes if you want it for the project meeting. The written comparison is evidence for the meeting, not a substitute for the engineering sign-off. The sign-off belongs to your team.

Do you ever quote a candidate part that your own report says should not be substituted?

Yes, on a separate line, with the comparison report attached. The quote lists the candidate's price, lifecycle stage, and lead time so the buyer has full visibility. The substitution decision stays with the buyer's engineering function. This is the honest answer — it gives the buyer the data without putting our letterhead on a qualification we did not perform.

What if the substitution would change the long-term lifecycle footprint of the assembly?

We flag the lifecycle axis in the comparison report and ask whether the substitution should be written into the equipment documentation or treated as a one-time bridge. The buyer decides. We do not write the substitution into the documentation on the customer's behalf, and we do not pretend that a one-time bridge is a permanent fix. Either way, the lifecycle tail is on the table before the shipment leaves our warehouse.

How do I phrase a cross-reference request so it does not waste a round trip?

Send the part number, the application context in one or two sentences, the approval file or CE technical file that covers the assembly if known, and the question you actually need answered. Send it through /inquiry or alongside the BOM line in /procurement. The shorter the first message, the faster the first reply — and the faster we can tell you whether the substitution is in scope for a written report or whether the next step is to bring your engineer into the conversation before we add a line to the quote.

Data Notes

By aoctrl sourcing desk. Last updated September 2026. Catalog grounding: Sick ZL2-P2428 photoelectric sensor family (aiDemandScore 80, premium-candidate tier) and Sick WTB4 referenced as the recurring case-2 example. Schneider XU series photoelectric sensors referenced for cross-brand application context. Cross-reference framework: 12-axis comparison with claim ladder levels 0–4, UNKNOWN-by-default for firmware_version and certifications_lifecycle axes. Screening statement included verbatim per aoctrl compliance policy. Service boundary explicit: independent distributor, not an authorized distributor; not a notified body; not a safety-qualified certifier; we do not run a repair service. Pre-dispatch inspection and bench-testing of refurbished items is part of our standard quality flow; this article does not change that. Real anchors: /compare, /procurement, /quality, /inquiry, /about, /shipping-returns, /terms-of-sale.