When a Cross-Reference Is the Wrong Answer: Cases Where an I

When a Cross-Reference Is the Wrong Answer: Cases Where an Independent Sourcing Desk Refuses to Substitute

A buyer asks for a cross-reference to a discontinued module. A sourcing desk lines up voltage, current, and terminal layout, ships a part that fits the cabinet, and the line is replaced. Three weeks later, a safety-output I/O error forces a line stop. As an independent industrial automation distributor (Chinese supplier of industrial automation parts, acting as an independent sourcing desk) the desk is paid to find parts, not to certify that any candidate will run a given machine. There are cases where the right answer is to refuse the substitution. Quotation, condition, lead time, and delivery terms are confirmed per line on the quote.

The framing the desk has to apply

The desk operates against the same twelve axes published on /compare: form-fit-outline, electrical ratings, function and I/O mapping, firmware and hardware version, communication protocol, certifications and lifecycle status, materials and environmental class, EMC and immunity, software toolchain, documentation, after-market support, and verification method. A substitution is a working answer only when the candidate scores equal or better on every axis the buyer's machine actually exercises. When two or more axes are unknown for the candidate, the desk does not write a substitute; the desk writes a comparison with the unknown axes named. The buyer, not the desk, owns the engineering call.

The first-pass answer is rarely a substitution. It is usually one of three options: remaining channel stock of the original part (condition disclosed per line on the quote: new surplus, refurbished with bench-test record, or used as-is), a documented last-time-buy through a still-active franchised channel, or a structured redesign using a current successor in the same family. Cross-reference enters only after those three paths are exhausted, and only if the axes check out.

Catalog grounding — the worked-example families

Three families in the catalog anchor the seven refusal cases below. The Omron CP1L series (CP1L-L14DR-A, CP1L-L20DR-A, CP1L-M30DR-A, CP1L-EM40DR-D, CP1L-EM30DR-D, CP1L-EL20DR-D and the CP1E-E10DR-A, CP1E-E14DR-A, CP1E-N40DR-A economy line, all with aiDemandScore in the 60s) is a discontinued compact PLC family with documented program-portability limits. The Omron E3ZM family of photoelectric sensors (E3ZM-T81 2M, E3ZM-T61 2M, E3ZM-D62 2M, E3ZM-T815M, all at aiDemandScore around 89, in the key/premium tier) and the Omron E2E proximity series (E2E-X1R5AH, E2E-X2MY1, E2E-CR8C1, E2EQX10F1 in the 88-89 band) anchor the same-family cases. Part numbers, ratings, and condition are drawn from the catalog; nothing in this article is invented.

Case one: the part is on a safety circuit

Substitution on a safety circuit is the most common place where a cross-reference turns into a liability. A buyer may ask for a cross-reference to an older safety relay or a safety output module that has been discontinued. The desk can line up the part number, the contact arrangement, the terminal layout, and the voltage. None of that addresses the SIL or PL rating the original module carried, the certification scope the buyer filed under, or the documented proof test interval the safety instrumented function is designed against. The desk does not hold the cert, cannot re-issue the cert, and does not see the safety validation file. A cross-reference here is not a substitution; it is a paper artifact that disappears the moment the buyer's safety auditor reads it.

The desk's posture: do not cross-reference safety devices. The buyer must either obtain the original part from remaining channel stock (condition disclosed per line on the quote), return to a current safety-rated part qualified by their own safety process, or escalate to the safety instrumented function owner for a redesign.

Case two: firmware-locked programs that depend on a specific revision

PLC programs are not always portable. A buyer who wants to move a CP1L application to a CP2E successor, or a S7-300 application to a S7-1500, often assumes the program will move. It does not, in general, move without work. Instruction set differences, I/O address mapping, function block libraries, and firmware-version-locked peripherals all enter. The desk can map the I/O, but it cannot see the buyer's program, the project comments, or the version-locked add-on instructions the application depends on. A cross-reference that ignores this turns into a two-week re-write the buyer did not budget.

The desk's posture: the comparison is sent with the firmware and software-toolchain axes marked unknown or differing. The actual porting call belongs to the buyer's controls engineer. The desk can supply both the old and the new unit so the engineering team can test the swap, but it does not promise a working port.

Case three: certified assemblies the buyer cannot re-qualify

A buyer may want a substitute for a module embedded inside a third-party-certified assembly — a panel built and listed by an OEM, a control cabinet built to a regional standard with documented component lists, or a device subject to a notified-body quality system. Substitution here is not a desk-side call. Re-qualification belongs to the OEM or the device maker, not to the buyer's maintenance budget. The desk can supply the part, but the buyer has to walk the change back through the OEM's change-control process. For medical devices specifically — including but not limited to those subject to ISO 13485 quality systems, notified-body review, or any device-side qualification regime — the desk does not hold ISO 13485, does not qualify components for medical-device use, and does not write a substitute for any line intended to be installed inside a medical device. Device-side qualification is the device maker's responsibility, and the change-control process that follows is theirs as well.

The desk's posture: the cross-reference is returned with the certifications-lifecycle axis flagged differing. The desk tells the buyer that the assembly's documentation will need to be re-issued; that is not the desk's scope.

Case four: parts where the axes cannot be verified from published material

Some candidates are unverifiable without physical inspection. An encoder with a custom resolution, a safety controller with a private firmware branch, a legacy HMI with a customer-specific runtime — these all look like normal catalog items on paper. The axes that matter for a working swap are often the ones the manufacturer does not publish for the older revision. The desk cannot guess those. A cross-reference written without those axes is a guess, and a guess installed in a working machine is an avoidable downtime event.

The desk's posture: the comparison is returned with at least two axes marked unknown. The desk tells the buyer what cannot be confirmed from the datasheet and what physical inspection would be required to close the gap.

Case five: when the buyer asks for a one-step swap

The buyer's request for a one-step, no-engineering swap is the desk's red flag. That kind of swap implies that the change requires no engineering review, no firmware update, no re-commissioning. In practice, almost no industrial automation component is a one-step swap across a model revision boundary. Terminal screws move. Status LED positions change. Diagnostic registers shift address. Configuration tool versions matter. The honest answer at this point is to refuse the no-engineering framing and write the comparison with the axes that are likely to differ explicitly named.

The desk's posture: write the comparison, mark any axis the manufacturer does not publish as unknown, and ask the buyer to confirm which axes their machine exercises. The substitution decision is then made by the buyer's engineer, not by the desk.

Case six: when the candidate does not have a documented successor in the same family

A buyer asks for a substitute for a controller whose family has been retired without a successor. The candidate is the next family up — a different CPU, a different backplane, a different programming software. That is a redesign, not a cross-reference. The honest answer is to write the comparison and tell the buyer this is a platform migration. The desk can supply both the old and the new units, and it can help the buyer find an independent controls engineer for the port, but it does not promise a swap.

The desk's posture: the comparison is returned with form-fit-outline, software-toolchain, and function-and-I/O mapping axes flagged as likely differing. The buyer is told this is a redesign, not a substitution.

Case seven: when the only candidate on the open market looks wrong

Sometimes a candidate exists in the open market — a broker list, a liquidation lot, a seller in another region — and the price looks too good. The desk's job is to ask why. Counterfeit industrial automation components enter the supply chain through discounted channels. The desk inspects label etching, batch code formatting, and weight. If the unit fails those checks, the desk does not propose it as a substitute. The desk's candidate list is shorter than the buyer's, on purpose.

The desk's posture: only candidates the desk has either sourced directly from a known channel or inspected physically are proposed as substitutes. The rest are returned to the buyer with a note that the desk did not verify the candidate.

Where the desk does substitute

Substitution is the right answer when the candidate scores equal or better on every axis the buyer's machine actually exercises, when the unknown axes can be closed by physical inspection or by a bench test, and when the candidate's certifications cover the buyer's region of use. A modern photoelectric sensor swapping to a current-generation sensor in the same family, a current-production power supply with the same input and output envelope, a current PLC in the same family with documented backward compatibility — these are candidates that pass. The desk returns the comparison with the axes that match called out, the axes that differ called out, and the axes the desk could not verify named.

The desk will not write a one-step, no-engineering claim on a working machine. The desk will write "candidate with verified equal axes, buyer to confirm fit in their machine before commissioning."

What the desk does not do

The desk does not certify that any candidate substitute meets an SIL or PL target. Functional-safety qualification belongs to the buyer's safety process. The desk does not certify that any candidate substitute is suitable for a medical device. Device-side qualification belongs to the device maker's quality system; the desk does not hold ISO 13485. The desk does not provide repairs. The desk finds parts; it does not rebuild them. The desk does not issue EAC or TR CU documentation; those belong to the importer of record. The desk does not make compliance calls on behalf of the buyer.

The standard form a refusal takes

When the desk declines to write a substitute, the line item in the quote is returned with three pieces of information: why the desk will not write a substitute, which axes could not be verified, and what the buyer's next step should be. The next step is usually one of: contact the OEM, walk the change through the buyer's quality system, return to remaining channel stock of the original part (condition per line on the quote), or escalate to a redesign with a controls engineer in the buyer's team.

A worked example from the desk's queue

A buyer asked the desk for a cross-reference to a discontinued Omron CP1L PLC. The desk pulled the CP1L specification, mapped the I/O count, the program capacity, and the option board slots. The candidate identified was the Omron CP2E, the same vendor's current replacement in the CP family. The desk wrote the comparison with the I/O mapping, option board slot, and instruction-set axes called out as differing. The firmware-version axis and the program-portability axis were marked unknown because the desk did not see the buyer's program. The desk told the buyer: this is a same-family platform migration, the swap is doable but it requires a port, and the desk can supply both units so the buyer's engineer can do the port. The desk did not write a one-step claim. The buyer was told to bring their engineer into the loop before commissioning.

What the buyer should send in the first message

When the desk is asked for a substitute that the desk suspects it should not propose, the buyer's first message is the fastest way to clarify. Send the original part number, the manufacturer, the machine and year if known, the application (general control, safety, motion, weighing, dosing), and the candidate the buyer has already considered if any. Photos of the label and the surrounding wiring help when the part is older and the catalog cross-reference is ambiguous. A single photo of the marking can save a round of email.

The next step on the buyer's side is to send the request to /inquiry with the original part number, the application, and a photo of the marking. The desk returns the comparison, names the axes that cannot be verified from the datasheet, and either supplies the original part from remaining channel stock or declines the substitution with the reason named.

What the desk writes back

The desk writes back one of three answers. First, the desk confirms it can supply the original part from remaining channel stock and confirms condition line by line on the quote. Second, the desk identifies a candidate in the same family, writes the axis-by-axis comparison, and tells the buyer which axes their engineer has to verify. Third, the desk returns the line without a substitute and explains why — usually because the line is on a safety circuit, on a certified assembly, or because the axes that matter cannot be verified from published material.

The third answer is the answer most buyers do not expect from a sourcing desk. It is also the answer that protects the buyer's machine. The desk's first loyalty is to the buyer's commissioning day, not to a substitute sale.

What this means for the buyer's engineering team

The buyer's engineering team owns the substitution call. The desk's job is to surface the comparison honestly, name the axes that cannot be verified, and refuse to over-claim. When the desk refuses a substitution, the buyer should treat the refusal as a flag, not as a sales tactic. The flag usually points at one of: a safety circuit, a certified assembly, an unverifiable firmware path, a documented platform migration, or a candidate that the desk cannot verify.

The desk is paid to find parts. The desk is also paid, by implication, to refuse the parts it should not propose. That is the standard an independent sourcing desk has to hold if it is going to be useful on commissioning day.

The buyer's next step is to send us your bom, the machine reference, and the application note, or to request a quote through /inquiry with the original part number and a photo of the marking. Contact our sourcing desk for any line where the desk's written refusal below would otherwise leave the buyer without a documented next move.

Data notes (editor's provenance)

Catalog grounding as of september 2026, drawn from the published catalog on aoctrl.com for Omron CP1L, CP1E, CP2E, E3ZM, and E2E families. Part numbers, ratings, and aiDemandScore bands reflect the published catalog at the time of writing.
Methodology paragraphs reference the twelve-axis cross-reference framework that the desk applies on every line, and which is published in summary on /compare. The desk does not publish axis-level data on every line; the framework is the policy, not the per-line output.
Worked CP1L to CP2E example is a methodology example; specific part numbers on the CP2E side reflect catalog entries available as of the dateline above. The desk did not disclose a customer, a project, or a part serial number.
No external sources are cited in the body. The desk's first-party catalog, internal methodology, and published service pages are the source. Any secondary statistic is omitted rather than mis-cited.

Disclaimer

This article is methodology, not engineering advice, not certification, and not a quotation. The desk is not a notified body, a functional-safety certifier, a medical-device quality-system registrar, or an EAC/TR CU issuing party. Substitutions are returned line by line, with condition disclosed per line on the quote, and verified against the original manufacturer datasheet and the buyer's own qualification process. The desk does not warrant fitness for any particular machine or installation. As an independent distributor (not an authorized distributor for any listed brand), the desk supplies surplus, refurbished, and used parts per line on the quote and does not represent any manufacturer.

We screen end users and end uses, classify before quoting, and decline transactions that cannot be screened. Where delivery is arranged to buyers in Russia or the CIS, it is arranged under the Incoterms stated on the quote (DAP or DDP where the quotation states it); the desk does not write destination promises, fixed transit times, or compliance interpretations on behalf of the buyer.

FAQ

What does a no-engineering swap usually mean when applied to industrial automation parts?

In practice, almost nothing. Same-family units share voltage, current, and terminal layout but usually differ in firmware revision, status-LED position, diagnostic-register address, or supported configuration-software version. Verify against the original manufacturer datasheet and your own qualification process before treating any candidate as a one-step, no-engineering change.

Is it ever acceptable to cross-reference a safety relay or safety output module?

No. Safety devices carry SIL or PL ratings with a specific certification scope and proof-test interval the buyer's safety process is filed against. A cross-reference does not transfer the certification. The buyer's safety instrumented function owner has to re-qualify or return to a current safety-rated part qualified by their own process.

Can a CP1L program move to a CP2E without rewriting?

In most cases, no. Instruction set, I/O address mapping, function block libraries, and firmware-version-locked peripherals differ between the two. The desk can supply both units so the buyer's engineer can do the port, but the port itself is an engineering project, not a cross-reference.

What information should a buyer include in the first message when asking for a substitute?

Send the original part number, the manufacturer, the machine and year if known, the application (general control, safety, motion, weighing, dosing), and the candidate already considered if any. Photos of the label and surrounding wiring help when the part is older or the catalog cross-reference is ambiguous.

Why would a sourcing desk return a line without a substitute?

Usually because the line is on a safety circuit, sits inside a certified assembly, depends on a firmware-locked program, or because the candidate's verifiable axes are too few to write a comparison the desk will stand behind. The desk is paid to find parts; it is also paid, by implication, to refuse the parts it should not propose.

Does an independent desk certify that a candidate will run a specific machine?

No. The desk lines up the comparison and names the axes that cannot be verified from published material. The buyer, or the buyer's controls engineer, owns the qualification call. A sourcing desk is not a certification body.

How does a desk decide which axes to flag as unknown?

The axes the desk cannot verify from the manufacturer datasheet or from physical inspection are flagged unknown. Typical unknowns include firmware-version compatibility with the buyer's program, the certifications lifecycle status for the buyer's region, and EMC immunity under the buyer's actual installation conditions. The unknown axes are named in the comparison so the buyer's engineer can close them.