The timing of the underlying event is not clearly specified in the provided information, but on June 20, 2026, Germany’s TÜV Rheinland released Version 2.1 of its IEC 61511-1:2026 functional safety implementation guide. The update is drawing attention across petroleum, chemicals, and other high-risk sectors because it explicitly adds a verification expectation for SIL2 safety instrumented systems using domestically produced PLCs as logic controllers, with immediate relevance for both new bidding activity and retrofit work.

What the updated guide explicitly requires

According to the provided summary, TÜV Rheinland’s IEC 61511-1:2026 Functional Safety Implementation Guide V2.1, issued on June 20, 2026, states for the first time that where a domestically produced PLC is used as the logic controller in a SIL2 safety instrumented system for high-risk industries such as oil and chemicals, its Modbus TCP and PROFINET communication protocol stack must undergo independent third-party black-box penetration testing and fault-injection verification.

The same summary states that the testing output must include a report compliant with ISO/IEC 17025. It also states that this requirement takes effect immediately for new project tenders and for modifications to existing systems.

Where the impact is likely to appear first

Bid preparation and owner-side procurement review

From an industry perspective, project owners and procurement teams may be affected first because the requirement is described as immediately applicable to new tenders. In practice, that makes technical documentation, supplier qualification review, and tender compliance checks the most likely points of immediate attention.

System integrators and retrofit execution

System integrators and engineering teams involved in existing system upgrades may also face direct implications. Observably, the inclusion of retrofits means communication protocol stack verification may become a practical checkpoint in project scope definition, testing preparation, and delivery documentation.

PLC suppliers and supporting test service providers

Manufacturers supplying domestically produced PLCs for SIL2 SIS use, along with third-party testing organizations, are likely to see the change most directly in verification workflows. What deserves closer attention is not only the test activity itself, but also the availability, completeness, and acceptance of ISO/IEC 17025-aligned reports within project timelines.

What companies should watch now

Check whether current projects fall into the immediate scope

Companies should first distinguish between pipeline tenders, ongoing bidding, and retrofit projects already in planning, because the provided information says the requirement applies immediately to both new projects and existing system modifications.

Review protocol stack evidence, not only controller selection

Analysis shows the key issue is not simply whether a PLC is domestic, but whether the Modbus TCP or PROFINET stack in a SIL2 SIS application has the required independent verification and supporting report. That shifts attention toward test evidence attached to the communication layer.

Prepare document paths and supplier communication early

For procurement, engineering, and compliance teams, an immediate practical concern is whether suppliers can provide third-party black-box penetration testing records, fault-injection verification results, and ISO/IEC 17025-compliant reporting in a form acceptable for bid review or project delivery.

Separate policy wording from implementation detail

What deserves closer attention is the difference between the stated requirement and its project-level interpretation. The provided information confirms the requirement itself, but companies may still need to keep tracking how it is cited, requested, or checked in tender documents, retrofit specifications, and acceptance processes.

Why this reads as more than a one-off wording change

Analysis shows this update is better understood as a concrete compliance signal rather than a routine editorial adjustment. The reason is that it links a specific technical object—the Modbus TCP/PROFINET communication protocol stack—to specific verification methods and a specific reporting expectation, while also stating immediate applicability.

At the same time, it would be premature to treat the development as a fully settled market outcome based only on the provided information. It is more appropriate to understand this as a rule-level signal with direct operational consequences, while continuing to observe how consistently it is reflected in actual bidding, retrofit implementation, and documentation review.

How the industry may best interpret this update

On balance, this development points to a more explicit compliance threshold for SIL2 SIS projects in high-risk industries where domestically produced PLCs are used as logic controllers. The immediate significance lies less in broad market conclusions and more in project execution, supplier qualification, and evidence readiness.

It is more appropriate to understand this as a near-term operational change with longer-term signaling value. The short-term issue is whether required testing and reporting can be produced in time for tenders and retrofits; the longer-term issue is whether similar expectations become embedded more broadly in safety-related procurement and engineering review.

Basis of this article and what still needs verification

This article is generated solely from the user-provided news title, the note that the event timing is not clearly specified, and the provided event summary. For this type of industry update, relevant source categories would typically include official notices, company announcements, industry association releases, authoritative media reporting, and documents issued by standards-related organizations.

No specific official source link was provided in the input, so the exact original publication path still requires ongoing verification. Areas that remain worth monitoring include any subsequent official wording, how the requirement is referenced in tender and retrofit documents, and whether further clarification appears around testing and reporting expectations.