PCS neo

What is PCS neo?

SIMATIC PCS neo is the fully web-based Distributed Control System from Siemens for process automation, combining engineering and operation in a single browser environment built on an object-oriented data model. Siemens introduced the system at Hannover Messe in April 2019 as newly developed system software. PCS neo runs on the same hardware basis as PCS 7, so its controllers and I/O come from the same SIMATIC family. The platform targets chemicals, pharmaceuticals, water, food and energy, and is a clear example of OT convergence in the process industry.

🧠 What makes PCS neo different from a classic DCS?

With a classic DCS, the engineer works on a heavy, locally installed engineering station and the operator uses a separate operator application. PCS neo breaks with that model:

• One workspace - in the PCS neo Workbench, users switch between the engineering view and the monitoring and control view, with all relevant information in one place.
• Object-oriented data model - a plant object such as a pump or control loop holds its logic, displays, alarms and documentation. A change is made once and applied everywhere.
• Browser-based - users work without a local software installation and can collaborate on the same project from several locations at once.
• Roles and sessions - a rights and role model determines who may do what, and a session concept keeps concurrent changes consistent.
• Modular - the system supports Module Type Package (MTP), so process modules from different suppliers can be integrated as ready-made units.

This makes PCS neo a step from closed, workstation-bound control towards a software-defined OT platform with a modern architecture and good scalability.

🔄 What is the difference between PCS neo and PCS 7?

PCS neo is not a direct replacement for PCS 7: Siemens sells both systems side by side and they share the same hardware. The first release built on the hardware and application architecture of PCS 7 V9.0; later versions follow the further development of that shared hardware portfolio.

For existing PCS 7 plants (brownfield), PCS 7 often remains the logical choice; PCS neo is chosen mainly for new builds or as a deliberate migration.

🔧 How is a PCS neo system built?

A PCS neo installation has the same layers as any DCS, complemented by web servers and gateways:

Version 4.0 (November 2022) raised capacity to 64,000 process objects and 56 controllers per system. At the same time Siemens launched the SIMATIC S7-4100: around 30% smaller than the previous model, with up to six PROFINET or PROFIBUS interfaces, up to 50% lower energy consumption, fanless operation between -25 °C and +70 °C, and no backup batteries. The CN 4100 acts as a kind of data switch: plant data is configured once and sent to the controller, the process control system or both, while the third-party network stays separated from the system network. Later versions extended OPC UA support further, so that alarms and events can also be passed to higher-level systems in a structured way. In process plants the Industrial Ethernet network is usually built redundantly to guarantee low latency and continuity.

📈 Which versions of PCS neo exist?

With “SIMATIC PCS neo in the Cloud”, version 7.0 offers a portal in which teams create, engineer and simulate projects without any local installation. The portal has virtual subtenants with their own user management, shared sessions with automatic conflict prevention, and single sign-on to the SIMIT simulation software for virtual commissioning. Equipment Module Classes (EMC) are reusable templates aligned with ISA-88 and ISA-106: engineer once, instantiate many times. Siemens claims 50 to 70% less engineering effort as a result; that is a vendor claim, not an independently measured figure. For alarms, V7.0 introduces a satellite concept that clears related alarms system-wide, and critical operations can be given two-step operation with safety acknowledgement. Certified safety functions go up to SIL 3, so basic process control and the safety instrumented system can be designed in one environment.

🏭 Where is PCS neo used?

PCS neo targets continuous and batch processes where downtime has direct consequences for safety, the environment or production:

• Chemicals - continuous plants, including chemical recycling, battery production and biofuels
• Pharmaceuticals and biotech - batch processes according to ISA-88, validated under GAMP and GMP
• Water - treatment and drinking water production; V7.0 adds telecontrol for widely distributed sites such as pumping stations, comparable to classic telemetry
• Food and energy - utilities and process plants

Integration with higher levels also follows familiar models: ISA-95 for integration with MES and ERP, and Industry 4.0 applications such as digital twins and edge computing via OPC UA or MQTT-based edge platforms. NAMUR Open Architecture can add a second, one-way channel for analytics without touching process control.

🔐 How do you secure a PCS neo environment?

Siemens developed PCS neo in line with the requirements of IEC 62443 and the Defense in Depth principle. Even so, the web architecture makes the system an IT-like target for Ransomware, credential misuse and lateral movement. User management runs through the User Management Component (UMC), which can connect to Active Directory.

That this platform has vulnerabilities too became clear in September 2023: CVE-2023-38558 (Siemens advisory SSA-646240) in the Administration Console of V4.0 and V4.0 Update 1 exposed Windows administrator credentials to a locally authenticated attacker (CVSS 5.5) and was fixed with Security Patch 01. Later advisories covered UMC, where for some older versions Siemens recommends an upgrade or mitigating measures rather than a patch.

Design the zones according to the Zones and Conduits Model and the Purdue Model, with an IDMZ between OT and office IT, and apply Zero Trust principles where possible.

🧪 How do you approach a PCS neo project in practice?

A typical project for a new chemical plant in the Netherlands:

1. Define the architecture - decide on zones, redundancy and server placement, possibly with virtualisation on configurations released by Siemens, and check hypervisor security.
2. Standardise - fix libraries and Equipment Module Classes before engineering starts.
3. Integrate modules - have skid suppliers deliver an MTP; for S7-1500 modules, TIA Portal exports that configuration.
4. Test - simulate the control system and carry out a FAT and SAT, including failover tests of redundant controllers.
5. Operate - secure lifecycle management of Windows Server, browsers, certificates and firmware.

If the plant falls under the Dutch Cybersecurity Act (Cyberbeveiligingswet, in force since 15 August 2026, the Dutch implementation of NIS2), risk management, patching and incident reporting must be demonstrably in place. For the Dutch water boards, CERT-WM is the point of contact for incidents. Siemens itself, as a manufacturer, falls under the Cyber Resilience Act, with a reporting obligation for actively exploited vulnerabilities from 11 September 2026; for you as an end user that means more and faster ProductCERT advisories to process. Standards such as NIST SP 800-82 and ISO 27001 help structure operations.

❓ Frequently asked questions

Is PCS neo the successor to PCS 7?

PCS neo is not a direct successor to PCS 7: Siemens sells both systems side by side on the same hardware basis. PCS neo is the new, web-based line, while PCS 7 remains supported for existing plants. Moving across is a migration project, not a simple update.

Does PCS neo still need a local engineering station?

PCS neo works through the browser, so engineers and operators do not need to install local engineering software. The servers do run on Windows Server in the OT network. In recent versions, engineering and simulation can also take place in a Siemens cloud portal, which V7.0 expanded into SIMATIC PCS neo in the Cloud.

Which controllers does PCS neo use?

PCS neo uses the SIMATIC S7-410 and the S7-4100, which appeared in 2022 initially exclusively for PCS neo. Process modules with an S7-1500 are integrated via Module Type Package. Field devices are connected through ET 200 I/O over PROFINET or PROFIBUS.

Does PCS neo support Module Type Package?

PCS neo has supported Module Type Package since its launch in 2019, and from version 4.0 it supports all parts of the MTP standard that NAMUR and ZVEI had released at that time. This lets skids and process modules from different suppliers be added to the DCS without custom work. For newer MTP versions, always check the Siemens release list for your PCS neo version.

Is PCS neo secure given its web technology?

PCS neo was developed in line with IEC 62443 and Defense in Depth, but web technology enlarges the attack surface compared with a closed DCS. Vulnerabilities such as CVE-2023-38558 show that patching, network segmentation and strict user management remain necessary. A PCS neo network should therefore never be connected directly to the internet.

Can PCS neo also run safety functions?

Since version 6.0, PCS neo supports the safety lifecycle in line with IEC 61508 and IEC 61511, with certified safety functions up to SIL 3. Basic process control and safety instrumentation can thus be designed in one engineering environment. Functional separation between the two remains a design requirement.

📌 In summary

PCS neo is Siemens’ fully web-based DCS, combining engineering and operation in one object-oriented browser environment on the same hardware as PCS 7. With MTP, OPC UA, the S7-4100 and cloud engineering it fits modern, modular process plants well, but its IT-like architecture demands strict segmentation, patching and user management in line with IEC 62443.