A practical review of lifecycle scope, installed-base evidence, critical-spares planning and the engineering work required before migration to S7-1200 G2.
Effective milestone stated for 1 November 2026
The first-generation S7-1200 phase-out is an installed-base planning event. It should trigger a controlled review of exact article numbers, recoverability and operational exposure—not an assumption that every S7-1200 item has become unavailable or that an S7-1200 G2 device is a direct field replacement.
For maintenance and procurement teams, the immediate question is not simply “Which new PLC replaces this one?” The stronger question is: “Can this machine still be restored safely and predictably, and what evidence supports the chosen spare or migration route?”
What the lifecycle change means
Siemens published an advance notice for the first-generation SIMATIC S7-1200 portfolio and identified 1 November 2026 as the phase-out milestone. Siemens also positions S7-1200 G2 as the successor direction for new development and migration planning.
A portfolio announcement does not establish the commercial status of one installed CPU, signal module, communication module or accessory. Availability, delivery conditions and the applicable product documents must still be checked against the complete Siemens article number and regional product record. The installed hardware version, firmware, expansion arrangement and approved software environment remain part of the technical identity.
Scope boundary: “First generation” is important. Do not convert a family-level notice into the claim that every S7-1200 product is already obsolete, unavailable or approved for substitution.
Build an installed-base register before buying
A useful register connects procurement data to the actual control function. A photograph of the CPU label is valuable, but it does not describe the complete assembly or prove that a replacement can be commissioned.
- Complete CPU article number and label photograph
- Hardware version and firmware
- Signal boards, signal modules and communication modules
- Installed position, panel space and power arrangement
- Machine function and consequence of controller failure
- I/O count, signal types and special functions
- PROFINET device names, IP settings and connected equipment
- HMI, drives, remote I/O and third-party communications
- Approved TIA Portal project and software version
- Licences, libraries and configuration files
- Known-good archive and restoration instructions
- Last verified backup date and responsible owner
Set spare priorities by operational risk
Buying the same quantity for every installed device rarely produces an efficient service-stock plan. Rank each item using evidence from the plant, then document why it is—or is not—held as a spare.
Failure consequence.
Identify the production, quality or restart impact if the component fails.
Recovery exposure.
Compare the acceptable recovery time with realistic sourcing, configuration and commissioning time.
Installed population.
Count identical article numbers and determine whether one controlled spare can cover several machines.
Recoverability.
Confirm that the project, tools, licences, firmware records and competent personnel required for restoration are available.
Procurement boundary: a physically matching unit is not yet an accepted spare. The condition, complete article number, supply scope and available technical evidence must be confirmed in writing.
Migration is an engineering project, not a part-number swap
Siemens states that S7-1200 G2 is not hardware-compatible with the previous S7-1200 family. The official migration guideline therefore treats the change as a hardware-and-software review rather than a like-for-like exchange.
The guideline calls for hardware-availability checks, verification of direct equivalents, review of external devices and a complete backup of the existing project. It also describes Migration Checker, the Migration Tool and manual migration paths. The current guideline states that S7-1200 G2 hardware and TIA Portal V20 or later are required to begin migration; the applicable software requirement should still be checked against the current document revision and selected hardware.
- Map every CPU, module and accessory to the proposed architecture.
- Review panel space, connectors, power, I/O and network interfaces.
- Check HMI, drives, remote devices and communication partners.
- Run the applicable migration checks on a controlled project copy.
- Compile the migrated project and review ignored or unsupported objects.
- Define I/O, interlock, alarm, communication and sequence tests.
- Record backups, versions, changes and acceptance evidence.
- Keep a rollback plan until commissioning is formally accepted.
Choose between service stock and migration
The decision should reflect remaining machine life, failure consequence and the quality of the recovery path—not only the price of one component.
- The exact configuration is documented and recoverable.
- Critical spare quantities can be justified by risk.
- The remaining machine life supports controlled service stock.
- A tested restoration process and competent resources exist.
- Critical devices have uncertain availability or poor recovery evidence.
- The approved project can no longer be restored reliably.
- I/O, networking, performance or security requirements have changed.
- A planned shutdown allows conversion, testing and acceptance.
Prepare a reviewable spare-parts enquiry
Send one complete requirement rather than several partial messages. Leave unknown values blank until they are verified from the installed equipment or approved records. A practical enquiry should contain:
Technical identityArticle Number · Hardware Version · Firmware · Installed Expansion · Project Version
Supply requirementQuantity · Preferred Condition · Destination · Required-on-Site Date
Request written confirmation of the offered article number, condition, included items, available label photographs, dispatch basis and documentation scope. Do not treat a family name, photograph or verbal description as acceptance evidence.
Explore our Siemens SIMATIC S7 catalogue or view the broader Siemens product range. Listed products should be checked against the complete installed article number and are not presented as automatic S7-1200 replacements.
Questions maintenance and procurement teams should resolve
Does phase-out mean every first-generation item is unavailable now?
No. Check the current Siemens product record and the written supplier offer for each complete article number.
Can an S7-1200 G2 CPU be treated as a direct replacement?
No automatic assumption should be made. Siemens states that the new generation is not hardware-compatible with the previous S7-1200 family.
What should be protected first?
Preserve the approved project, software versions, firmware records, network settings, licences and a documented restoration procedure before the installed knowledge is lost.
What makes a spare genuinely usable?
The exact hardware must be supported by the correct project, tools, accessories, engineering knowledge and a defined test process. Stock without recoverability evidence may not reduce downtime risk.
Official Siemens manuals
- Siemens — S7-1200 Programmable Controller System Manual
Official Siemens system manual for the first-generation S7-1200 platform. - Siemens — S7-1200 G2 Programmable Logic Controller System Manual
Official Siemens system manual for S7-1200 G2; it does not by itself approve a direct replacement for an installed first-generation configuration.
Use the manual edition applicable to the installed hardware and verify the complete article number before purchase or migration approval.