Omron vs Siemens PLC: total cost over five years — myth vs reality

The most expensive mistake in PLC procurement is not the hardware sticker — it’s the ripple cost of a constraint you didn’t model. A plant engineer who picks a Siemens S7‑1200 for a 16‑axis packaging machine because “it’s the brand we always use” will discover that the real constraint is not scan speed but motion‑axis scalability and software‑project debt. Over five years, the total cost difference between an Omron NX1P2 and a Siemens S7‑1200 can exceed 40 % of the initial purchase – and the direction flips depending on whether you hit the constraint wall in year two or year four. This is the myth‑vs‑reality map for that decision.

1. The myth: “any micro PLC handles motion if the cycle is fast”

Reality: motion‑axis count is the hard constraint, and it propagates into hardware cost, software effort, and spare‑part inventory.

The Omron NX1P2‑9024DT has integrated EtherCAT motion for up to 8 axes (4 PTP axes standard, 16 nodes) with a primary task cycle as low as 2 ms. The Siemens S7‑1200 (CPU 1214C) offers integrated motion via PTO – typically 2 to 4 pulse‑train outputs – and does not support a dedicated motion bus like PROFIdrive over PROFINET without an additional technology module. The mechanism is simple: EtherCAT uses a distributed‑clock mechanism that synchronises multiple axes deterministically at the µs level, whereas PTO is a digital‑pulse train that cannot coordinate more than two or three axes without external stepper controllers and separate wiring. When you need six servo axes on a pick‑and‑place cell, the S7‑1200 forces you to buy an additional motion controller (e.g., S7‑1500 or SIMOTION) or add a third‑party CANopen module — both add ≳€1 200 in hardware plus engineering time to integrate two programming environments (TIA Portal plus the motion vendor’s tool). The NX1P2 handles the same six axes from one Sysmac Studio project.

Worked consequence: A machine builder who assumed “fast scan time is enough” (the S7‑1200 bit instruction time is ~85 ns — faster than the NX1P2’s ~4 ms cycle) will discover that cycle speed does not help when the constraint is axis synchronisation. The S7‑1200’s 85‑ns bit speed is irrelevant because the application is waiting for pulse trains, not solving logic. The real cost: one extra controller (€1 200), one extra enclosure (≈€300), plus 40 h of integration engineering (≈€4 000 at €100/h), totalling about €5 500 over five years. The Omron path adds zero incremental hardware.

When it flips: If your application uses ≤2 axes (e.g., a conveyor with one motor and a divert gate), the S7‑1200’s PTO is simpler and the TIA Portal ecosystem, with its vast library of function blocks, can reduce programming time. In that case, the myth is actually true — but only below the axis threshold.

2. The myth: “100 KB of work memory is plenty for a micro PLC”

Reality: program memory is a soft constraint that becomes hard when you add HMI recipes, OPC UA, or data logging — and upgrading mid‑life is 3× the cost.

The S7‑1200 CPU 1214C has 100 KB integrated work memory (code + data). The Omron NX1P2‑9024DT has 1.5 MB program memory + 2 MB variable memory + 32 kB retentive, and it includes a built‑in OPC UA server. The mechanism: 100 KB may hold a moderate logic program (~2 000 instruction blocks in ST or ladder), but once you add an HMI recipe database (e.g., 60 recipes × 200 bytes each = 12 KB), a data‑logging buffer (assume 50 KB), and OPC UA address space (another 20 KB), the headroom shrinks to near zero. The NX1P2’s 3.5 MB total gives a >20× buffer. When the S7‑1200 runs out of memory, the only option is to buy the next family up (S7‑1500, starting ~€800) or add an external memory card and restructure the application — both cost >€1 000 in hardware and re‑engineering. The NX1P2’s OPC UA server is already resident; adding it to a S7‑1200 requires a CP 1542‑1 (≈€600) plus configuration effort.

Worked consequence: A facility that planned to connect 20 machines to a MES via OPC UA will face a €600‑per‑PLC add‑on for the Siemens PLC path (≈€12 000 for 20 units) versus zero for the Omron path. Over five years, that alone is a €12 000 difference in a 20‑machine line. The “100 KB is enough” myth holds only if you never add OPC UA, never store recipes locally, and never log data — a rare scenario in 2026 production.

When it flips: For a simple standalone machine with no HMI, no data logging, and no remote access, the S7‑1200’s 100 KB may last the full five years. But as soon as a customer asks for “a quick OPC UA interface,” you hit the constraint.

3. The myth: “TIA Portal is the industry standard — it saves cost in the long run”

Reality: TIA Portal’s licensing model creates a recurring cost that is often invisible at purchase, while Sysmac Studio is a single‑project environment with no runtime fees.

TIA Portal Basic (for S7‑1200) is included with the hardware, but any advanced features — OPC UA, web server, motion technology objects, or step‑7‑professional blocks — require licensed add‑ons (e.g., TIA Portal STEP 7 Professional V19, ~€1 200 per seat). Maintenance renewals are typically 15 % of licence cost per year. Sysmac Studio is a single‑environment tool that covers all Omron NX‑series controllers, including motion, safety, OPC UA, and vision, with no per‑feature licences. The mechanism is a licensing “cost‑constraint” that propagates: every time an engineer needs a function beyond Basic, a purchase order is triggered. Over five years, a three‑engineer team using TIA Portal Professional will spend about €3 600 on initial licences plus €2 700 in maintenance (15 % × 3 seats × 5 years) = €6 300. The same team using Sysmac Studio spends €1 850 per seat once (no maintenance) = €5 550, a saving of about 12 %.

Worked consequence: For a small integrator with two engineers, the difference is roughly €2 100 over five years — not enormous, but enough to tip the decision when combined with the motion and memory advantages. The myth that “TIA is cheaper because it’s standard” ignores the fact that “standard” often means “pay more for every feature.”

When it flips: If your facility is exclusively Siemens and you already own TIA Portal licences (i.e., the licence cost is sunk), the incremental cost for one more S7‑1200 project is near zero. In that case, the myth holds.

4. The myth: “spare‑part cost is negligible in the total”

Reality: the constraint of a single‑vendor ecosystem forces higher spare‑part inventory and shorter obsolescence cycles; the alternative is a more modular, standards‑based architecture.

The Omron NX1P2 uses the NX‑I/O series (up to 8 units), which share the same bus coupler and form factor across the entire NX line. The Siemens S7‑1200 uses signal modules (SM) and signal boards (SB) that are specific to the 1200 family; if you later migrate to an S7‑1500, these modules are physically incompatible. The mechanism is platform‑lock: a spare‑parts inventory for a Siemens‑only line must stock SM1231, SM1232, SB1221, etc., while an Omron line stocks NX‑ID, NX‑OD, and NX‑AD modules that also fit the NX102 and NX701 controllers. Over five years, a 20‑machine line might need 5 spare I/O modules. The NX modules are ≈€30–€60 each, while Siemens SM modules are ≈€50–€90 each. The difference is small per module, but the real cost is the risk of a discontinued form factor: Siemens has changed the S7‑1200 form factor once (from G1 to G2), which makes G1 spares harder to source. Omron’s NX platform has been stable since 2015 and is backward‑compatible.

Worked consequence: A 5‑year inventory of 5 spare I/O modules + 1 spare CPU for a 20‑machine Siemens line costs about €1 800; for an Omron line it costs about €1 100, a €700 saving. Not massive, but part of the constraint chain.

When it flips: If you have an existing Siemens‑only maintenance team and a stocked spare‑parts crib, the incremental cost of adding one more S7‑1200 is near zero. The myth is true only for brownfield Siemens sites.

🔍 Non‑obvious insight: the real constraint is not the PLC — it’s the ecosystem inertia

The myth‑vs‑reality analysis shows that the S7‑1200’s apparent “low cost” (€300–€400 CPU) vanishes when you propagate the constraints of motion, memory, and licensing. But the non‑obvious takeaway is that the Omron NX1P2’s strongest advantage — the unified software and EtherCAT motion — becomes a liability if your maintenance team is Siemens‑trained and you cannot afford retraining. The failure mode is a team that buys Omron for cost reasons but neglects to budget 80 h of training (≈€8 000) for two technicians. In that scenario, the total cost flips and the Siemens path becomes cheaper. The decision must be made not on hardware cost alone, but on the entire propagation chain: hardware → software → motion → spare parts → human capital.

⚠️ When the myth becomes real (the failure mode)

Consider a plant with five existing Siemens‑based lines, a maintenance crew fluent in TIA Portal, and a store of S7‑1200 spare modules. Adding a sixth identical line with an Omron NX1P2 would force a second software ecosystem, a different spare‑parts pool, and training costs that exceed the per‑machine savings. In that case, the “Siemens is cheaper” myth is actually true for that specific brownfield. The constraint propagation analysis must include the installed base.