Table of contents
At a glance
What should WinCC validation demonstrate?
Validate the specific WinCC application, controllers, communications, runtime, options and records for intended GMP use. Demonstrate that the correct recipe takes effect, operator actions remain traceable, and process data and alarms support the intended decisions. Test communication failure, unauthorised changes and restoration. A product name, audit licence or plausible trend does not demonstrate this.
- Classical WinCC V8.1, WinCC Professional, and WinCC Unified must be treated separately.
- Recipe specification, transferred value, and actually effective control value are different points of validation evidence.
- Process value archive, alarm log, and audit trail address different questions.
- Archiving procedures, runtime configuration, and option settings determine the specifically testable scope.
1. First determine the WinCC product family and the current system status
The focus is on classical SIMATIC WinCC V8.1. A specific vendor version, Update 6 with identifier K8.1.0.6, is documented by a Readme file dated February 2026. Additionally, the Audit Handbook from September 2024 and the System Handbook "Working with WinCC" from June 2025 are referenced. These documents cover different components of the system; they do not constitute a claim that the latest available patch is installed on the current installation.
WinCC Professional in TIA Portal and WinCC Unified are separate product lines. Therefore, features, clients, and options cannot be transferred solely due to the shared name. The TIA V20 documentation explicitly distinguishes these products from WinCC V7.x/V8.x and includes specific installation limitations. Existing V7 installations require a documented version and migration scope.
Keep track of engineering and runtime, server, clients, operating system, database, drivers, controls and options. The V8.1 order overview distinguishes between RT and RC as well as archive scope and additional options. Use this overview for orientation; the actual acquired and installed scope proves your own documents. Also a single missing option can change the intended test path.
2. Describe the process linkage of the SCADA application
WinCC visualizes and processes projected process information. Its GMP significance arises from whether operations, setpoints, or records influence manufacturing and quality assessment. A simple overview is to be evaluated differently from an operation that alters critical parameters, or an archive whose history supports a batch release decision.
The scope of consideration is the manufacture of human medicinal products under EU GMP. Annex 11 addresses computerised systems in this context on a risk-based approach; Chapter 4 distinguishes between controlled instructions and execution records. An audit function neither validates official software licensing nor confirms the suitability of any customer's system.
Describe the system boundary from the sensor or data generation level through control and communication to display, archiving, and subsequent evaluation. Identify key data sources: where does the recipe status reside, where does process logic execute, and which records are critical for which purpose? Clearly define the boundaries with respect to MES, SIMATIC BATCH, or a higher-level historian.
3. Assign data pathways and evidence types separately
A plausible screen value initially reflects a displayed state. This does not automatically imply that the same value was correctly received by the control system, archived at the intended cycle interval, or later uniquely assignable to a batch. The following dedicated work matrix ensures that validation evidence is not inadvertently reused for multiple distinct assertions.
Capture for each row the specific component and the responsible party. Add interfaces that lie outside of WinCC. This enables, for example, visibility into whether the recipe management system is leading or merely receiving a dataset from a higher-level system.
| Area | Example statement | Targeted evidence |
|---|---|---|
| Engineering | The project includes the assessed parameter status | Project identity, change, and transferred runtime status |
| User archives/recipient data | R2 belongs to product P and the next batch. | Dataset identity, intended use, and regulated transfer |
| Control and Connectivity | The confirmed target value is actually effective. | Readback value and expected behavior, including in case of transfer error |
| Tag Logging | The relevant history is fit for decision-making. | Time-based, unit, capture, archiving, and data quality |
| Alarm Logging | The limit event, acknowledgement and return to normal remain distinguishable | Configured alert states and reaction workflow |
| WinCC/Audit | Relevant change can be traced. | Activated components, event scope and readable context |
| Security and Long-Term Usage | Earlier batch data remain retrievable | Appropriate data sets, segments, and restore proof |
4. Review and verify formulation changes and transfer into control
The WinCC manual describes user archives as data structures through which, among other things, formulation and production parameters can be exchanged with the automation system. Data structure and communication are to be configured. This does not result in an automatic GMP release or guaranteed batch correct transfer in any project.
Therefore, define a specific transition: a professionally approved dataset is selected for a specific facility and batch, transferred, and deemed effective. Verify incomplete transfers, incorrect units, inappropriate product assignment, and repeated triggering. The type of lock or feedback mechanism used depends on your project design and control logic.
When a change occurs between two batches, it must be clearly evident which version was actually in effect. A new recipe version must not retrospectively alter the meaning of a previous version. Additionally, specify how a deliberate and authorized change during an ongoing batch shall be handled and documented. A blanket prohibition against any online modification is equally unhelpful as unlimited modification capability.
5. Evaluate process value archives based on their respective procedures
Data capture, archiving, and screen refresh are separate cycles in the WinCC handbook. Therefore, the refresh rate of the process display alone is insufficient for a reliable verification. Identify the measurement variable, unit, data type, time source, archiving procedure, and relevant quality information. Verify the actual stored data volume.
The handbook also describes condensation methods such as the Swinging-Door algorithm, where not every value is stored. Therefore, a simple target number of measurement points is only suitable for a specifically defined cyclic procedure. Define the expected capability of the archive: for example, the ability to detect a relevant deviation from established limits or to provide a traceable process segment trend.
For Audit-GMP tags, the cumulative update 6 Readme document, in the section on Audit Update 3, specifies a concrete limit: when data acquisition cycles are below one second, values may be lost. This applies specifically to the audit data collection described therein. It does not represent a general performance ceiling for all WinCC process value archives, nor does it constitute evidence that a one-second cycle is sufficient for every application.
6. Alarm state, acknowledgment, and response separation
A clearance addresses a different question than the return of the process to the intended operating range. For relevant alarms, define what the event signifies, who is responsible for recognizing it, the expected response, and how the conclusion of the event is detected. The evidence should also demonstrate that a clearance does not render an ongoing deviation invisible.
The WinCC alarm system documentation describes configurable alarm classes, alarm types, and quittance behaviors. Therefore, verify the actually selected configuration against the intended client systems. A professionally relevant alarm must reach the correct operator interface with clear and understandable information. A communication issue may require a different response than a genuine process boundary violation.
For the test protocol, input event, time, visible state, receipt and subsequent findings are helpful separate fields. Complete the failure of an operating station and the regulated change to the replacement workstation. The professional evaluation of possible batch effects depends on the specific event, its data and its own quality system.
7. Test actual event rights and audit scope
WinCC/Audit differentiates between components for configuration changes, user archives, operator actions, GMP tags, and signature events. These are selectively enabled. Therefore, an existing license does not necessarily mean that all relevant changes to your project are being captured. First, define which actions should be traceable.
For example, assess a legitimate recipe change, a rejected change request, an administrative configuration modification, and an action triggered by a project-specific script. Compare the triggered event with the stored context. Also evaluate the failure and re-attempt of data capture, to the extent that these pathways are relevant to your system boundary.
The Audit Handbook describes electronic signatures as configuration-dependent functions and distinguishes between immediate and subsequent confirmations. Determine when the relevant action is permitted and the significance of a confirmation. A standard login, an alarm acknowledgment, and a quality-related approval are not inherently equivalent decisions. The intended use determines the required evaluation.
8. Worked example of a recipe change and twelve missing archive points
No equipment was operated during the following setpoint verification. This example does not describe a fault in Siemens WinCC and is not a completed product test. A system processes Batch A using Recipe R1 with a setpoint of 60.0 °C. Recipe R2 with a setpoint of 65.0 °C is exclusively intended for the next batch, Batch B. These temperatures are example parameters and do not represent pharmaceutical acceptance criteria.
An additional archive test is defined for exactly one temperature channel: a stored value is recorded every second, with no dead zone, compression, or aggregation. The time window extends from 10:00:00 to 10:10:00, inclusive of both endpoints. The selected test configuration must actually meet these requirements.
- Determine the missing time period based on the timestamps, not merely comparing a total count.
- Investigate whether the disruption affects only the documentation or also the operation and process control.
- Do not display missing values as measured by a drawn connecting line.
- Only after evaluation of the findings regarding the intended further use and required actions is a decision made.
| Test step | Starting state and intervention | Expected demonstration and decision |
|---|---|---|
| Start Batch A | R1 selected; control confirmed at 60.0 °C | Batch reference A/R1, transferred and effective target value agree. |
| Prepare R2 | R2 at 65.0 °C is provided for B | A remains at R1; simple preparation does not alter the ongoing dosage. |
| Unauthorized intervention | User without change authorization attempts to modify R2 | Changes are prevented according to role requirements; the original dataset remains intact. |
| Errors during transfer | For B, R2 is requested, the re-read value remains 60.0 °C | No false success notification; B initiates its setpoint regulation only after clear acceptance of takeover. |
| Create archive gap | No stored value for twelve scheduled time points | 589 instead of 601 values; identify missing time points, separately investigate event and process impact. |
| Acknowledge alarm | Temperature remains outside the projected limit. | Termination evident, ongoing condition still clearly understood; reaction documented. |
| Start Batch B | Correction applied; R2 and 65.0 °C confirmed | B/R2 is recorded; A/R1 remains historically traceable. |
9. Operation, restoration, and SME involvement preparation
Plan the collaboration between production, automation, IT, and QA based on specific decisions. Production defines critical requirements and response protocols; automation outlines control logic and data flow; IT manages infrastructure and security. Competence requirements and necessary assessments are defined within the respective quality management system. Manufacturers and integrators provide the relevant technical documentation and project information.
The effort increases with more complex scripts, numerous controls, diverse client pathways, ambiguous recipe responsibilities, and legacy data inventories. A complete, representative data flow provides more meaningful insights for planning than a generic count of screen views. Test performance under a representative load; documented system peak values do not guarantee suitability for your specific combination of hardware and implementation.
The safeguarding must actually include the required inventories. The Audit Handbook highlights that a manual backup only captures the active segment and considers prior segments through the configured automated backup process. Data migrations also differ by data type. Therefore, historical readability, project status, runtime, and restart capability must be incorporated into change planning. Redundancy alone does not substitute for this evidence.
10. Checklist for specific WinCC validation evidence
This standalone assistance tool is designed to focus the audit plan on critical data pathways. Link each point to a requirement, a responsible party, and a verifiable outcome. An unexplained deviation cannot be resolved merely by a generally plausible visualization.
- Product family, version, updates, RT/RC and used options clearly documented.
- Control, communication, servers, and all relevant operator interfaces defined and bounded.
- Lead recipe definition, selection, acceptance, and batch assignment defined.
- Roles for recipe modification, operation, configuration and administration practically tested.
- Data capture, archiving, and display procedures including units and time references.
- Alarm state, clearance, response, and return to normal state distinguished.
- Relevant audit events reviewed based on triggered actions.
- Communication errors, incorrect feedback, and targeted repetition explicitly addressed.
- Required archive and audit segments, as well as project status reports, considered in backup and recovery safeguards.
- Changes, historical data, and required re-evaluations during operation are governed.
Project experience and collaboration
Compare the recipe, the value read back and the batch record
For a planned recipe transfer, we agree independent setpoints with your automation and operations teams. In a suitable test environment, we trace the values actually received and the batch to which they are assigned. Manufacturer and equipment records can help define the test scope. Custom scripts or interfaces need additional cases. We introduce a controlled interruption to assess the restart and the resulting record. With QA, we match the results to the requirements and check whether the evidence supports the apparent trend.
Frequently asked questions about Siemens WinCC
Does this guideline also apply to WinCC Unified?
The specific manufacturer's mechanics refer to classic WinCC V8.1. Unified and WinCC Professional in TIA Portal have separate product and runtime limitations. Fundamental validation questions can be helpful, but options, data retention, and user interfaces must be mapped according to the relevant documentation. Do not assume audit or archiving functions solely due to shared naming.
Is WinCC V8.1 with Audit automatically compliant with GMP?
An audit option supports certain evidences but does not confirm the suitability of your entire application. Key factors include the intended process, design, activated components, data pathways, and operation. Assess whether the required context is actually captured based on specific changes. Additionally, relevant process data and further controls may be necessary outside of the audit trail.
Is displaying the correct recipe on screen sufficient?
In addition, the transition to control for the process relevant to your procedure must be demonstrated. Compare selected data sets, transmitted parameters, and the actually effective state including batch reference. Also assess any unsuccessful or partial transmission. The method of feedback used must be defined on a project basis; a visible recipe label alone does not constitute proof of correct execution.
Must every recipe change be blocked while a batch is in progress?
This cannot be specified generally. First, describe the specific process changes allowed and their implications. For authorized changes, regulated authorizations, appropriate controls, and clear evidence of the actually used version must be established. If a change is intended only between batches, the exact boundary must be effectively verified. The original batch statement must remain traceable and understandable.
How can a gap in the process value archive be demonstrated?
Compare the stored inventory with the expected recording for the selected procedure. For defined cyclic storage, use timestamps and target count. For event-triggered or compressed logging, employ alternative criteria tailored to the procedure. Additionally, clarify whether data quality, connection status, or filtering affects the display. A visually closed trend line does not prove a continuous sequence of measurement values.
Does the one-second limit apply to all WinCC archives?
No. The specific note in the Update-6 Readme regarding GMP tag audit logging warns of potential value loss in shorter cycles. Process parameter logging, tag logging, and image updates should be evaluated separately. Select and verify the temporal resolution as specified in the process requirements; the manufacturer's guidance provides a specific limit, not a universal recommendation.
Has a cleared alarm already been resolved?
Clearance alone does not indicate whether the root cause has been eliminated or whether the required response has been completed. Evaluate the designed alerting behavior and distinguish professionally relevant conditions. When a boundary violation persists, the team must be able to assess its significance. The assessment of potential batch impact is based on the event and available data, not solely on the clearance status.
Does every operational procedure require an electronic signature?
The need is determined by action, significance, and regulatory scope. It does not follow that a general obligation to sign off on every keystroke is required. Where an electronic signature is specified, the timestamp, authorization, and linkage to the relevant action must be valid. Therefore, the configuration options described in the Audit Manual must be assessed against the organization's own process; login alone does not constitute the required authorization.
Is a current backup sufficient for older batch records?
Verify which inventories are included in this backup. For WinCC/Audit, the handbook describes a segmented backup logic featuring an active segment and previously automatically backed-up segments. Therefore, a single current backup operation does not inherently guarantee the completeness of historical data. Demonstrate, based on a required older record, that data, context, and appropriate read access remain jointly available.
What documentation should a small and medium-sized enterprise collect prior to the project?
Useful are project and option status reports, control overview, data flow, recipe responsibility assignments, roles, archiving configuration, alarm response procedures, as well as backup and change documentation. Select a representative batch production flow. Based on this, it can be determined which evidence is already sufficient and where issues of transfer, failure, or historical readability remain unresolved. Only from this emerges a reliable plan for testing and internal involvement.
Sources and review date
Sources checked on 6 October 2026. The technical scope is classic SIMATIC WinCC V8.1, documented Update 6 K8.1.0.6 and manual editions 09/2024, 02/2025 and 06/2025. Professional and Unified are distinct products. We selected the expected outcomes for these examples without testing a particular licence, configuration or runtime. The regulatory scope is the described use in human medicinal product GMP.
- Siemens: SIMATIC WinCC V8.1 Order Data
- Siemens: Update 6 (K8.1.0.6) for WinCC V8.1
- Siemens: WinCC V8.1 General Information and Installation
- Siemens: WinCC/Audit
- Siemens: WinCC Working with WinCC
- Siemens: TIA Portal V20, parallel installation
- European Commission: EudraLex Volume 4
- European Commission: EU GMP Annex 11 – Computerised Systems
- European Commission: EU GMP Chapter 4 – Documentation
Sources checked: .
Clarify WinCC data pathways and verification evidence
We support you in defining the specific SCADA application and in clearly integrating recipe, archive, and operational records.
- Computer system validation →
Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

