Table of contents
At a glance
What does SIMATIC PCS 7 validation involve?
Demonstrate that the installed SIMATIC PCS 7 automation functions suit their intended use. Trace the chain from signal through control logic and operator action to the process record actually used. Define scope from requirements, risks and the real architecture. Supplement relevant supplier and plant evidence where needed. A plausible display, passed function test or safety feature alone does not demonstrate the whole chain.
- The test limit follows the process function including significant dependencies.
- Signal value, signal quality, alarm state, and clearance are distinct test attributes.
- Software validations and physical equipment suitability require appropriate evidence.
- Historized data are evaluated based on their subsequent use.
Assess PCS 7 as a process control system with a specific architecture
SIMATIC PCS 7 is a process control system for the process industry. The Configuration Manual V10.0 SP1 distinguishes between Engineering Station, Operator Station, and other components. The Engineering Station is used for system design and project setup; Operator Stations provide process data for operation and monitoring. In multi-station systems, process values, archives, and alerts are transmitted from the server to the client stations.
This architecture influences the scope of testing. Identify where a function is designed, executed, operated, and recorded. A test conducted on a single workstation may miss a server-side data discrepancy or a difference between delivered project versions. Similarly, dependent time, network, or archive services may be relevant to professional judgment.
The technical reference to this article is the PCS-7 manual "PC Configuration V10.0 SP1" dated March 2025. The current product overview lists V10.0, but not a complete patch level. For your planning, select the documentation for the actual installed stand including service pack and updates. SIMATIC BATCH, PCS neo and Opcenter Pharma are treated as delimited products or components; their functions are not an implied PCS-7 scope.
Define GMP, functional safety, and facility suitability clearly and distinctly
The regulatory example framework is Human Medicinal Product-GMP. Annex 11 addresses computerised systems in this area as a GMP guideline. Its revision dated January 2011 is listed in the current EudraLex directory. Whether additional FDA requirements for electronic records are relevant is determined based on the underlying obligations and actual usage.
A GMP-relevant temperature log and a safety-related shutdown function may pertain to the same equipment area, but address distinct validation questions. A safety case does not substitute for evaluation of the data used in product assessment. Conversely, a CSV review does not establish functional safety. Common signals or interventions must still be clearly understood as dependencies.
The physical measurement setup remains independent. Chapter 3 covers appropriate measurement equipment, calibration, and control. A simulated input can verify software scaling; it does not validate the actual measurement performance of the installed probe. Annex 15 provides the basis for the equipment qualification. The associated documentation should be consistent, without unnecessarily duplicating the same activities.
Select the process function as a continuous test limit
Start with a function whose erroneous behavior could impact manufacturing or its evaluation. For temperature monitoring, relevant factors include sensor location, unit, calibration, alarm condition, user permissions, and data usage. The product name alone is not an adequate boundary. A generic software category neither defines specific failure scenarios nor establishes the necessary evidence of validation.
Describe the professional judgment underlying each piece of information. An active display may be assessed differently from an archived value that is later required to support a critical process step. Shared infrastructure must not be overlooked: incorrect time attribution can adversely affect both assertions.
The following internal support document makes transitions visible. Use existing signal, function, and requirement documentation when these relationships are already clearly documented. For critical systems, Annex 11 requires a current, detailed system description; this does not imply the same level of documentation coverage is necessary for each non-critical auxiliary function.
| Level | Process question | Possible evidence |
|---|---|---|
| Measurement site and entry point | Correct source, unit, and valid status? | Assignment, measurement/simulation test |
| Processing | Appropriate scaling and decision rule? | Independent calculation and edge case analysis |
| Operation | Appropriate advertising and authorized intervention? | Roll and Condition Inspection |
| Notification | When is it activated, quarantined, and terminated? | Separate event sequence |
| Record | What information remains for subsequent evaluation? | Comparison of Planned Series and Stored Data |
| System handover | Is context and quality preserved at the recipient end? | Alignment including error scenario |
Monitor the verified project status up to execution.
Determine the underlying design of the inspection procedure and verify where this design is actually in effect. This includes relevant libraries, customizations, user interfaces, and data configurations. The PCS-7 Handbook describes central and distributed components; this raises the practical question of whether the associated components are consistently provided.
For changes, a brief and specific description of the impact is recommended. "Temperature monitoring updated" is less helpful than specifying which threshold, reset condition, and alert are affected. Additionally, clarify which record and which recipient must also be aware of the change. Otherwise, a modified image caption could conceal an unchanged calculation.
Verify the actually used version after transfer. A documented required version alone is insufficient if the check is performed on a different configuration. The technical method for this reconciliation depends on version and project tools. The article does not claim a specific transaction path nor automatic complete change logging.
Evaluate signal quality, alarms, and operator intervention separately
A numerically plausible value may originate from an incorrect source or be outdated. For critical functions, your checks should therefore also assess the status of the information. Define the expected behavior under invalid signals, connection loss, and reconnection. The required alarm indication, subsequent action, and documentation depend on the intended process.
You should also distinguish between the creation of a report, its clearance, and the end of the triggering condition. A user may acknowledge a report even if the process value remains outside the acceptable range. Whether additional interventions are permissible must be separately defined and evaluated against appropriate roles.
In test planning, a defined role hierarchy provides guidance: the observer monitors the current state, the operator authorizes changes within permitted limits, and the duly authorized responsible party may adjust a limit if necessary. Any unauthorized attempt to modify a parameter must also be included as part of an appropriate test case. These roles serve as a methodological framework, not as a claim of pre-defined PCS-7 authorization profiles.
Example: Temperature value, alert, and recording
The example serves as a reference model for a test environment, not a completed PCS-7 test, and does not represent a specification for actual pharmaceutical temperature control. The input at T-201 provides a linear 4 to 20 mA signal corresponding to 0 to 100 °C. The independently defined conversion formula is T = (I − 4) × 100 / 16. Thus, an input of 12.00 mA corresponds exactly to 50.00 °C.
The example requirement activates a message at 60.00 °C or above. Once activated, it remains active until the temperature reaches 58.00 °C or below. Acknowledging the message leaves the temperature condition unchanged. This project example calls for valid values every five seconds without aggregation. Set these requirements explicitly in the test configuration. They are not stated PCS 7 defaults.
The initial condition at 12:00:00 is valid, with a temperature of 50.00 °C and no active alarm. At 12:00:05, the temperature reads 59.00 °C; at 12:00:10, it is exactly 60.00 °C. At 12:00:15, when the temperature reaches 61.00 °C, the operator acknowledges the condition; the alarm remains active. At 12:00:20, the temperature drops to 58.00 °C. The table below defines the expected behavior and additional independent fault scenarios.
Restore the known starting state for each failure scenario. Record test input, observed display, alarm events and stored time series separately. Set time tolerances before testing based on the architecture. The idealised series does not prescribe a general response time.
| Input / Timestamp | Independently established expected result | Evidence to review |
|---|---|---|
| 12:00:00; 12.00 mA, valid | 50.00 °C; Inactivation notification | Value, unit, time, and quality |
| 12:00:05; 13.44 mA, valid | 59.00 °C; further inactivated | No premature reporting initiation |
| 12:00:10; 13.60 mA, valid | 60.00 °C; Active notification | Limit inclusive of effective value |
| 12:00:15; 13.76 mA; Cancellation | 61.00 °C; terminated, further active | Withdrawal and status separately defined |
| 12:00:20; 13.28 mA, valid | 58.00 °C; active state ends | Reset limit including |
| Incident: Value 50.00, quality invalid | Not to be considered a valid temperature | Invalidity in display and data |
| Incident: Record 12:00:25 is missing | Missing information identifiable | No unmarked replacement with old value |
| Incident: Observer modifies threshold value | Changes not permitted | Validity boundary in effect |
Review stored data based on its intended use
The configuration manual identifies process data, archives, and alerts as components of operator systems. The actual data required, stored, and further utilized remains a project decision. For this example, the stored data series is compared against the independently defined input data series. Additionally, verify units, time reference, and the marking of invalid or missing values.
A compression may be suitable for a specific purpose and may conceal a relevant short deviation for another. The subsequent professional assessment is decisive. A clear trend is no substitute for this decision. Similarly, an export may present a different representation than the original data; the significance must still be preserved.
For relevant changes and operational procedures, the required evidence is defined. An event log, an alarm history, and an audit trail may address different questions. Assess the actual coverage rather than assigning the same significance to each protocol. Whether electronic signatures are required is determined by the process and applicable requirements. The specific execution requires appropriate documentation; a user confirmation alone does not automatically fulfill this obligation.
Integrate FAT, SAT, and software validations appropriately.
Existing equipment and supplier tests may already cover certain requirements. Assign evidence to the following specific statement: A simulation test can verify a computational rule, while the actual signal path must be additionally examined at the installed measurement point. A receipt protocol lacking traceable input and result documentation does not adequately address this question.
In the plant context, Annex 15 describes that appropriate FAT tests do not need to be repeated on site under justified conditions. It is crucial whether transport, installation or integration influence the tested function. This transfer decision is made for the respective proof; it is neither a flat-rate certificate nor a requirement for double testing.
Plan open testing steps jointly with automation, process engineering, and QA. The technical implementation may be correct, while the intended use remains unclear. Conversely, a well-designed process may fail due to a non-representative test setup. Therefore, document the limitations of the environment and remaining validation evidence.
Operation, restoration, and considering changes
For a critical process function, planned updates, disruptions, and access to historical records also apply. Define who evaluates changes and when a technical re-assessment is required. An operating system update may have different implications than a modified functional module or a new archive recipient.
The PCS-7 Operator Manual describes redundancy options for operator systems. However, the presence of a redundant configuration does not prove that the relevant function operates correctly during a switchover or that all required data remains intact. An appropriate test evaluates the agreed-upon impact on operation, processing, and data logging.
A restoration validation record should include the associated system design and usable data. Following a restore, verify not only user login but also a representative function and access to required information. The meaning in the process of incidents should be assessed. A critical event may necessitate further root cause analysis; not every technical observation warrants the same level of investigation.
Which preparation makes the effort manageable
For a small company, start with a defined objective understood by all participants. Select representative critical functions and identify the users. Process engineering defines boundaries, automation explains implementation, IT covers operations and QA assesses the proposed evidence. Clarify external integrators' responsibilities and documentation early.
Qualitative workload drivers include specialized logic, a large number of distinct signal pathways, distributed project statuses, data transfers, and limited testing opportunities. Even a small system can be demanding when critical functions can only be verified during a brief downtime. In contrast, a large, unified installation can provide reusable evidence.
A pre-defined package enables a justified sequence: first, professional guidelines and risks; then, existing evidence; followed by targeted residual checks. The effort aligns with this approach. A general test volume, fixed project duration, or generic GAMP category does not replace the need for clear demarcation.
- Define architecture, installed stations, and effective project configuration.
- Identify critical measurement points and describe their data usage.
- Define professionally relevant signal, unit, alarm, and intervention rules.
- Align suitable simulations, on-site equipment testing, and their limitations.
- Prepare roles and document the initial and reset states.
- Make FAT/SAT records, open deviations, and operating procedures accessible.
Project experience and collaboration
Trace the measurement chain from the input to the record used
With the automation and process teams, we compare the expected scaling of a prepared signal path against the displayed and stored values. Your subject matter experts set the acceptable tolerance. Suitable supplier and qualification evidence can be reused. Different logic or data paths may require additional checks. We help assign the work and link its results so that you can see which parts of the chain are supported and what remains to be demonstrated for the intended use.
Frequently asked questions about SIMATIC PCS 7
When is SIMATIC PCS 7 relevant to our GMP process?
When functions used in manufacturing, process control, or the generation of relevant records are implemented, their specific impact must be evaluated. Consider shared dependencies, such as data transfers or time-based alignments. Not every function automatically warrants the same level of testing. The described framework applies to human medicinal product GMP; other uses are addressed separately.
Are PCS 7 and SIMATIC BATCH subject to the same validation scope?
No. PCS 7 includes the underlying automation and human-machine interface architecture. BATCH complements batch automation with recipes and batch referencing. When co-utilized, the transitions must be documented, without generating duplicate evidence. The focus of this article is on signals, logic, operation, and data, not on complete recipe management.
Does a security certificate demonstrate GMP suitability?
Such evidence may support a specific conclusion within the scope of its evaluation. It does not automatically establish that your GMP-relevant functions and records are appropriate for their intended use. Separate the objectives of the validation and consider shared dependencies. This guide does not include an assessment of functional safety or specific safety certifications.
Can we test with simulated measurement values?
Yes, if the environment is appropriate for the specific testing objective and its limits are documented. The conversion in the example of this article can be independently verified. The actual measurement device, cabling, and physical measurement direction are not fully substantiated thereby. Assign simulation and equipment inspections such that the entire relevant chain is covered.
Why is an alarm clearance not the end of a limit value violation?
Since acknowledgment and process status may represent different interpretations, in the example provided in this article, the alert remains active despite clearance, as long as the predefined reset condition is not met. For your setup, you determine these rules based on technical expertise and verify their implementation. No general PCS-7 default setting or universal alarm threshold is derived.
Sources: [4]
Must all process values be recorded without compression?
The required data volume follows the intended use and risk profile. For some evaluations, consolidated information is sufficient; for others, clear temporal trends or short deviations are necessary. The unaggregated sequence in the example of this article represents a standalone project requirement. Justify, for your function, which documentation enables a competent decision-making process reliably.
Is the integrator's FAT sufficient?
It may cover appropriate requirements. Review the test setup, prerequisites, results, and transferability to the installed system. An algorithm verified during FAT does not necessarily require a full retest upon implementation. However, changes to signal paths, installation, and interfaces may require additional validation evidence. The decision should be based on each individual assertion and its specific conditions.
What must be available prior to the start of PCS-7 validation?
Gather a clear architecture description, the versions actually installed, the relevant process requirements and the available plant records. Identify critical measurement points, roles and intended uses of the data. Confirm that a suitable test environment and the necessary plant access are available. This will help distinguish an outstanding process decision from missing test evidence.
Who must collaborate and what affects the duration?
Process engineering, automation, operations, and IT as well as quality assurance provide disparate information. Integrators support implementation and existing evidence. Time requirements arise particularly from unclear rules, individual logic, numerous handoffs, and limited testing windows. Clear responsibilities and appropriate source data facilitate planning; a fixed duration cannot be reliably derived from the software designation.
Must the entire system be revalidated after each update?
The supplemental validation follows the impact of the change. Assess affected functions, interfaces, data, and operating conditions, as well as the remaining valid records. A technical version update may generate either a limited or an extensive validation requirement. Document the decision and any open limitations; neither an automated complete retest nor unverified carryover is acceptable.
Sources and review date
Date: 6 October 2026. Architectural specifications refer to PCS 7 PC Configuration V10.0 SP1 (03/2025) and the current product overview. SP1 is not claimed to be the latest version. The specific signal, alarm, and storage rules provided in the example are intended use specifications; no installation, facility, or safety function has been verified for these.
- SIMATIC PCS 7 – Distributed Control System
- SIMATIC PCS 7: PC Configuration V10.0 SP1
- European Commission: EudraLex Volume 4
- EU GMP Annex 11: Computerised Systems
- EU-GMP Chapter 3: Facilities and Equipment
- EU GMP Chapter 4: Documentation
- EMA: ICH Q9(R1), Step 5, Corr.2
- FDA: Part 11 — Scope and Application
- EU GMP Annex 15: Qualification and Validation
Sources checked: .
Ensure continuous protection of critical process functions
We support you in consolidating technical requirements, documentation records, and supplementary software evaluations for your PCS-7 environment.
- 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.

