Same Brand, Same Series, Still Not Interchangeable: Why an A

Same Brand, Same Series, Still Not Interchangeable

A buyer in Saint Petersburg writes: «Купил такой же контактор, того же производителя, той же серии — а он не работает. Что я сделал не так?». The honest answer: same brand and same series is one of the most expensive assumptions in industrial maintenance. The family name groups outline and mounting; the suffix on the part number encodes coil voltage, contact arrangement, output type, firmware generation and certification scope, and that is where the substitution verdict is decided. This article explains why the ABB AF contactor and the Siemens Sirius 3RT families fail same-family substitution, and what an independent China-based industrial automation distributor and sourcing desk actually checks.

What "same series" actually means to a manufacturer

To a manufacturer a "series" is a generation of products built on a common mechanical and electrical platform. The platform covers outline, mounting, the front-connector family, the terminal grid and the engineering software that programs or supervises the device. Within the platform the part number encodes a long list of variables — coil voltage, contact arrangement, terminal type, function block, hardware revision, firmware generation, certification scope and intended market. Reading the family name off the label is the same as reading "Siemens" off the label and assuming any Siemens product will fit. The family name groups; the suffix specifies.

Take the ABB AF contactor family. The family identifier AF116 means "AF series, frame 116". The rest of the part number — 30-11-13 in our example SKU 1SFL427001R1311 AF116-30-11-13, score 83.64 — says coil voltage and contactor construction: 30 stands for 3 main poles with a NO auxiliary mounted on the side; 11 is the auxiliary contact arrangement (1 NO + 1 NC); 13 is the coil code, here 100–250 V AC/DC wide-range. Replace 13 with 14 and the coil becomes 250–500 V AC/DC. The outline is the same, the mounting is the same, the front of the device looks identical, the auxiliary arrangement is identical, and the coil is built for a different supply. Wire that into a 230 V control circuit and the contactor either hums and burns out the coil or sits open and does nothing visible.

The Siemens Sirius 3RT2015 (S00 frame) family does the same thing with its last two digits. Sirius 3RT2015-1AK61, 3RT2015-1BK21, 3RT2015-1BB41 and 3RT2015-1BB42 share the outline, the same mounting footprint on DIN rail, the same front-connector geometry and the same screw-terminal layout. The differences live in coil voltage, in the auxiliary block composition and in the rated power at AC-3. A panel builder who orders one part number and accepts a delivery on a different part number can wire the cabinet and only discover the mismatch at commissioning.

The same mechanism shows up in three other places we see repeatedly on the desk:

Photoelectric sensors in the Omron E3Z family. The E3ZM-T81 2M (score 89.26), the E3ZM-T61 2M (score 89.26), the E3ZM-D62 2M (score 89.10) and the E3Z-LT81 (score 88.78) all live in the same housing. T81 is retro-reflective with PNP output; T61 is retro-reflective with NPN; D62 is diffuse-reflective PNP; LT81 is a laser retro-reflective. Drop the wrong suffix into a machine and the sensor appears to work on the bench and not detect the target in the line.
Siemens S7-300 I/O modules. The 6ES7331-7KF02-0AB0 (score 82.751), the 6ES7322-1BL00-0AA0 (score 82.496) and the 6ES7315-2AH14-0AB0 (score 82.849) are all S7-300 family modules. They share the rail, the backplane and the front connector family; they do not interchange. The CPU runs a different firmware, the analog input resolves a different signal set, the digital output switches a different load class. Same shelf, different device.
Phoenix Contact QUINT power supplies. The QUINT4-PS/3AC/24DC/20 family has variants for 1-phase and 3-phase input, for different output current ratings and for different signal outputs. The mechanic looks the same on the outside; the part number decides whether the supply is right for the cabinet's input.

This is the structural reason "same brand, same series" is not a substitute. The substitution decision is not at the family level — it is at the suffix level, and the suffix is where the manufacturer encodes the variables that determine whether the device works in the application.

Why it keeps happening — and why the catalogue does not help

The natural place to check whether two parts interchange is the manufacturer catalogue. The catalogue will tell you that the family is the same. It will not tell you that the part you have is functionally compatible with the part you need. The catalogue is organised for ordering, not for substitution; it groups products by family because that is how a buyer thinks, and within a family the differences are listed in a way that assumes the reader is choosing a variant, not replacing an existing one. The substitution question is the inverse problem — the reader already has a part and is asking whether another part will do the job of the first.

Three things happen when a buyer accepts "same brand, same series" on trust. First, the part is mechanically interchangeable with the original, which is why the substitution feels safe — it fits, it clicks, the wiring reaches. Second, the part is electrically and functionally different from the original in at least one axis, and that axis is not visible without reading the suffix. Third, the buyer only learns about the axis that mattered at the moment the machine needs to perform the function the missing axis was carrying — usually commissioning, usually with the panel builder's clock running. By then the cabinet is wired, the cable schedule is fixed, and the discovery turns into rework rather than a corrected order.

The substitution check that catches these is the twelve-axis check that we publish in the cross-reference work for the desk. The relevant axes here are terminal and interface assignment (the wiring grid and the front connector), electrical parameters (coil voltage, contact rating, output type), function and I/O specification (the actual job the device does), firmware and hardware version (which can move the engineering software to a different project file), communication protocol (the bus and the role the device plays on the bus), environmental class and EMC, ingress protection and certification and lifecycle status. For a contactor the electrical axis carries the failure; for an I/O module the firmware axis carries it; for a photoelectric sensor the function and I/O axis carries it. In every case the family name matches and the part number does not.

Where the assumption goes wrong, by axis

We treat each axis as a question, and we treat the answer as matched, differs or unknown rather than yes and no. The differ verdict is where a same-brand same-series substitution fails. The four axes where it fails most often:

Coil voltage and supply range. The most common cause of "I installed the same contactor and it does not work". Wide-range coils (100–250 V AC/DC) look like they could substitute for 230 V coils, and they can — but a 24 V DC coil ordered by mistake into a 230 V cabinet will not pull in, and a 230 V coil ordered by mistake into a 24 V cabinet will draw enough current to destroy the coil in seconds. The label is the same family; the suffix changes.

Contact arrangement and auxiliary block. A 3-pole contactor with 1 NO + 1 NC auxiliaries and a 3-pole contactor with 2 NO + 2 NC auxiliaries share the same family and the same outline. The auxiliary terminals on the front are not interchangeable, and a PLC expecting one auxiliary contact will report a different machine state if it sees the other. The substitution looks correct until the first interlock fails.

Output type and signal logic. Photoelectric sensors in the same housing with different output configurations — NPN versus PNP, normally open versus normally closed, dark-on versus light-on — are the canonical example. The sensor installs, the indicator LED lights, and the PLC input never sees a transition because the electrical event the sensor is signalling does not match the electrical event the input is listening for. The family name matches; the function does not.

Firmware and hardware version. PLC and HMI modules are where this bites hardest. A CPU module from the same family with a different firmware generation expects a different engineering project, communicates on the bus with a slightly different protocol state, and reports a different module identifier to the controller. Two modules from the same shelf can look interchangeable on the parts list and refuse to substitute on the network.

The substitution ladder that this ladder of failures implies starts at the bottom: same series is a visual similarity, not a compatibility claim. The compatibility claim has to be built axis by axis, with each axis checked against the datasheet and against the project record, and with the axes that cannot be checked marked unknown. The verification clause that belongs at the end of any comparison is therefore the one we use in every cross-reference on the desk: verify against the original manufacturer datasheet and your own qualification process.

What an independent desk does that a franchised channel does not

A franchised channel is structured around the catalogue and the family — it answers the question "what do you want to order", not the question "what will substitute for what you have". The independent desk is structured the other way: the question is always "you have X, you need Y, will X interchange with Y, and if not, what will". The desk's daily work is to read the suffix, read the firmware state, read the terminal layout and then put a verdict on the table with the unverified axes named.

Three things this desk does that the family-level answer does not:

Reads the suffix. Every part on a BOM is matched on the part number including the suffix, the dash number and the firmware revision, not on the family. Where the buyer has only the family, the desk asks for the marking on the device and reads the label back rather than guessing from a family description.
Reports axis by axis. The cross-reference is a comparison with twelve axes, each with matched, differs or unknown. The unknown is reported, not skipped; the differ is reported, not glossed over; the matched is reported, not implied. A comparison that ends with "compatible" without the axis list is not a comparison the desk will sign.
Carries the lines separately. The desk will not merge two part numbers into one line on a quote just because they share a family. Each line carries its own MPN, its own condition (new, new surplus, refurbished or used), its own MOQ, its own price and its own lead time, with the substitution verdict on a separate sheet. That way the buyer can drop or defer one line without breaking the others.

For buyers in Moscow, the Russian regions and the CIS the second point matters more than it does elsewhere, because the after-sales path for a wrong substitution runs through the buyer's own engineering team rather than through a local authorised partner. The cross-reference report travels with the goods and is what the buyer's team uses to decide whether to install. We screen end users and end uses, classify before quoting, and decline transactions that cannot be screened.

When "same brand, same series" is genuinely enough

There are cases where the suffix carries no functional difference for the application and the substitution is safe. Three are worth naming because they are the legitimate exceptions:

Identical marking, different packaging. A buyer may receive the same MPN in two different pack sizes or with two different accessory bundles. The device is the same; the box is different. Reading the label resolves this without a twelve-axis check.
Identical suffix, different date code or hardware revision. The suffix encodes the functional specification; the date code encodes the production batch. A hardware revision letter that does not appear on the suffix is a manufacturing state, not a functional change, and within the same firmware generation it does not change the function.
A substitution the manufacturer documents in a migration guide or PCN. A small number of substitutions are documented by the manufacturer itself, with the axis check written into the migration document. The axis check still runs, but the outcome is that every axis matches because the manufacturer has done the work. These are rare.

The fourth case — where the substitution looks same-family and is in fact a redesign — is one the desk will not call a substitution. A redesign is a redesign, and the verification work that goes with it belongs to the buyer's engineering process. Telling the two apart is part of the desk's job.

Where the desk declines the substitution

The desk is an independent distributor and sourcing desk, not a certification body and not a substitute for the buyer's engineering process. Three classes of substitution are declined even where the suffix appears to match:

Where the part sits inside a cabinet covered by a third-party listing (UL, CSA, CE as a listed assembly). The listing covers the part numbers written on the file; substituting a different MPN, even from the same family, voids the listing and reopens the conformity file. The buyer who needs that listing intact sources the exact part or treats the change as a redesign.
Where the machine's own documentation pins the design to a specific MPN. Spare-parts lists that name a specific part are part of the machine's permanent record. The substitution that diverges from that record is a redesign, and the documentation update is the buyer's, not ours.
Where the substitution cannot be verified on the axes the application depends on. If the firmware generation cannot be confirmed from the marking, if the coil code is ambiguous, or if the manufacturer does not publish a figure the application needs, the comparison ends with one or more unknown axes and the desk reports that rather than signing off. The decision then belongs to the buyer's qualification process.

The substitutions we do not decline are the ones where the axis check passes, the documentation is available, the buyer's engineering team accepts the verdict and the resulting line can be carried with a stated condition (new, new surplus, refurbished or used) and a stated MOQ per line.

A practical discipline for the buyer's side

A buyer who treats the family name as the spec ends up with one of two outcomes: a rejected order that arrives on the wrong coil voltage, or a panel that does not commission. A buyer who treats the suffix as the spec still has to do the work of reading the suffix and matching it to the project record, but the failure mode is "I noticed the suffix was wrong before I ordered" rather than "I noticed at commissioning". The substitution decision gets pushed upstream, where it is cheap, rather than downstream, where it is expensive.

The practical discipline, in order of how cheap it is to apply:

Capture the MPN including the suffix, the hardware revision and the firmware generation for every line on the BOM before the part goes obsolete. The marking on the device is the source of truth; the project file is a copy. Take a photograph at the moment of panel build.
When sending the BOM for sourcing, send the marking text alongside the part number. The desk reads both and flags mismatches at quote stage rather than at delivery stage.
For a line that has been superseded, ask the desk to write the comparison as a cross-reference report and to name the axes that could not be verified rather than asking for a single yes-or-no answer.
Treat the cross-reference report as input to your own qualification process. The desk verifies what the datasheet says; it does not verify whether the project still works on the substitute. The verification work is yours and stays yours.

This is the discipline that closes the gap between the family name on the catalogue and the suffix on the device. The desk does its part by reading the suffix and reporting axis by axis; the buyer's team does its part by treating the report as the start of the qualification, not the end.

Where the desk stops

The desk is an independent distributor and sourcing desk, not an authorised partner, not a certification body and not a substitute for the buyer's engineering process. The cross-reference report we issue compares what the manufacturer publishes; it does not certify that a substitute will run your program, that it will hold in your environment or that it will satisfy a conformity file. That determination is the buyer's, with the buyer's quality system and the buyer's engineering team. The desk also does not repair, does not retest as a service to a manufacturer and does not issue conformity certificates such as EAC or TR CU. The desks's role is to find the part, state its condition, consolidate it with the rest of the order and ship it with the documentation that the source can actually provide. Where the part cannot be found, the standing-request path is the route to keep the line open until stock appears.

The takeaway

Same brand and same series are the family name on the label. The part number, including every suffix, dash number and firmware revision, is the specification. If you can read the marking off the device before the order goes out, you can avoid the substitution you will only discover at commissioning. If you cannot, the cross-reference report we publish is the document that turns "same brand, same series" from an assumption into a comparison. Send the marking, send the project context, and the answer is line by line rather than family by family.

For an order, send us your BOM through the procurement desk. For a cross-reference report on a single line, request a quote with the marking on the device and the line you need it to replace, and the desk will return a twelve-axis table with the unverified axes named. The substitution verdict belongs to your engineering team; the sourcing belongs to us.\n\n-- By aoctrl sourcing desk, September 2026

FAQ

What does "same brand, same series" actually mean on a label?

It means the part belongs to a manufacturer's product generation — the family identifier groups outline, mounting and the front-connector geometry. The suffix that follows the family identifier encodes coil voltage, contact arrangement, output type, hardware revision, firmware generation and certification scope. The family is the platform; the suffix is the specification. Two parts with the same family name and different suffixes can share an outline and disagree on every functional axis.

Why does an ABB AF contactor with the same outline refuse to work?

Because the suffix encodes coil voltage and contact arrangement. The ABB AF116-30-11-13 has coil code 13, a 100–250 V AC/DC wide-range coil. Replace 13 with 14 and the coil becomes 250–500 V AC/DC; replace 11 with another auxiliary code and the auxiliary terminals change. The contactor fits, the wiring reaches, and the coil either hums and burns out on a 230 V cabinet wired for 24 V DC or refuses to pull in on the wrong supply. Reading the suffix off the device label before ordering prevents this.

How does the Siemens Sirius 3RT2015 family differ within the same series?

The Sirius 3RT2015 family covers the S00 frame with shared outline, mounting and front-connector geometry. Within the family the last two digits of the part number encode coil voltage, contact arrangement and rated power at AC-3. Two Sirius 3RT2015 part numbers can be visually indistinguishable on the panel and disagree on coil voltage or auxiliary block composition. The substitution check is at the suffix level, not the family level.

Why is same-family not a substitute on photoelectric sensors like the Omron E3Z?

Because the E3ZM-T81 2M is retro-reflective with PNP output, the E3ZM-T61 2M is retro-reflective with NPN, the E3ZM-D62 2M is diffuse-reflective PNP and the E3Z-LT81 is laser retro-reflective. They share the housing and the mounting. They do not share the sensing mode, the output logic or the target behaviour. The substitution check is on sensing mode and output type, not on housing.

What is the most expensive same-family mistake in industrial maintenance?

Coil voltage on a contactor or a relay is the most common, because the device looks correct on the shelf and the wiring schedule matches, and the failure mode is either silent (the contactor does not pull in) or destructive (the coil burns out within seconds). Output type on a sensor is a close second, because the failure is also silent and is only discovered when the line misses the function the sensor was supposed to signal. Both are caught by reading the suffix off the device label before the order goes out, not by reading the family name off the catalogue.

How does a cross-reference report treat the unknown axes?

A cross-reference report lists the comparison axes one by one — twelve in the desk's standard framework — and assigns each axis a verdict of matched, differs or unknown. The unknown verdict is reported, not skipped; it is named with the reason it could not be verified, such as the manufacturer does not publish the figure for the second-source part or the firmware generation cannot be confirmed from the marking alone. The buyer uses the report to decide whether the unknown axes are tolerable in the application or whether the substitution has to be reworked.

What does the desk not certify about a same-family substitution?

The desk does not certify that the substitute will run the buyer's control program, that it will hold in the buyer's environment, or that it carries a manufacturer-issued warranty. The cross-reference report is a comparison of what the manufacturer publishes. The qualification decision — whether the substitute actually fits the application — sits with the buyer's engineering process. We screen end users and end uses, classify before quoting, and decline transactions that cannot be screened.

Data Notes

Catalog references in this article are drawn from the aoctrl.com CMS records for the ABB AF116-30-11-13 (1SFL427001R1311, score 83.64), Omron E3ZM-T81 2M (89.26), E3ZM-T61 2M (89.26), E3ZM-D62 2M (89.10), E3Z-LT81 (88.78), Siemens 6ES7315-2AH14-0AB0 (82.849), 6ES7331-7KF02-0AB0 (82.751) and 6ES7322-1BL00-0AA0 (82.496), and Phoenix Contact QUINT4-PS/3AC/24DC/20. Series and part-number conventions are quoted from publicly available manufacturer datasheets; verification against the original manufacturer datasheet and the buyer's own qualification process remains the buyer's responsibility.
This article is informational. aoctrl.com is an independent distributor and sourcing desk, not an authorised distributor, certification body or conformity assessor. We do not hold EAC, TR CU, ISO 13485, UL, CE, ATEX or any equivalent certification for the goods we supply, and we do not certify that a substitute is compatible with a specific application.
Independent distributor notice: every cross-reference issued by the desk is a comparison of manufacturer-published specifications with the unverified axes named. The decision to substitute rests with the buyer's engineering process.
Data through: September 2026.
Byline: aoctrl sourcing desk.