Table of contents
At a glance
What does SIMATIC BATCH validation involve?
Demonstrate that SIMATIC BATCH is suitable for the intended batch process. Link recipe, formula, batch and process unit, then check controlled interventions and usable records. Define requirements and risks, assess relevant supplier evidence and test any remaining transitions against predetermined results. The scope follows actual use. A successful technical recipe check alone does not establish suitability.
- Supplier release, batch start, and professional assessment serve distinct purposes.
- Formulation parameters and authorized changes are part of the validation basis.
- The occupancy of sections and their actual suitability for intended use must be evaluated separately.
- Interruption, restart, and batch traceability are jointly evaluated.
What SIMATIC BATCH handles and which version is considered
Siemens describes SIMATIC BATCH as batch automation within SIMATIC PCS 7. The V10.0 manual distinguishes between recipe system, batch planning, batch control, and batch data management. This is helpful for clarification: a correctly configured recipe structure does not necessarily indicate that an order has been executed with the correct values and fully documented.
The article is based on the Operating Manual V10.0 issued in May 2024, the BATCH-Readme, and the PCS-7 Configuration Handbook for V10.0 SP1 issued in March 2025. These versions serve as documented reference points and do not constitute statements regarding the most current available release. For your project, the installed state, released combinations, and relevant updates will be cross-checked.
Capture BATCH server and client systems, PCS-7 integration, recipe processing, data retention, and used interfaces. Additional MES functions, laboratory decisions, or maintenance of material master data are included only if they are actually integrated. Your responsibility upon system handover does not end merely because the other system has a different name.
Distinguish the GMP use of the technical batch status.
The examples concern GMP manufacture of human medicinal products. EU GMP Annex 11 addresses computerised systems in this setting. The EudraLex index listed the January 2011 revision when the sources were checked. Check other sectors and regulatory areas separately. For FDA-regulated records, assess Part 11 applicability against the actual use.
A risk may arise, for example, due to incorrect recipe assignment, an unobserved parameter change, or missing context during subsequent batch evaluation. The key initial question therefore becomes: Which incorrect execution or misleading documentation could alter a business decision? This identifies the key focus areas for requirements and assessments.
Software validation is coordinated with equipment qualification and process validation. A batch test can demonstrate that a specification has been transferred; however, the suitability of the actual mixing process has not been established. Functional safety and GMP relevance are distinct considerations. Common technical interdependencies remain part of the evaluation.
Define verifiable requirements for transfer points
Describe first the intended production workflow in production language. Which order requires which recipe? When are the values defined? Under what conditions may the batch commence? What must be visible later for evaluation? A requirement such as "recipe management works" leaves these decisions open.
A more specific statement is required: For order A-204, the approved formula from recipe R-04 must be selected prior to start; the assigned recipe shall remain identifiable in the batch data. Specify which deviation the test operator is intended to induce and at what point the expected behavior should be observable. The terms and status values must align with your installation.
The following work aid links technical requirements with the subject of inspection. It is not a prescribed form. An existing requirements document may already contain the same mapping. Additional tables are only helpful if they facilitate decision-making.
| Transition | Question to check the control | Suitable evidence |
|---|---|---|
| Recipe → Order | Which version and formula apply to this task? | Mapping with a justified expected result |
| Order → batch | Which parameters are active at startup? | Start dates and comparison with target values |
| Batch → Partial unit | Is the selected subunit available and intended? | Equipment availability and suitability criterion |
| Intervention → further execution | Who is authorized to modify which value at what time? | Permitted and rejected intervention |
| Implementation → Documentation | Are changes, quantities, and assignments clear? | Linked records for one batch |
Review recipe structure, formulas, and parameter changes separately
The V10.0 manual describes internal formulas in the master recipe and external formulas assigned to a recipe procedure. Parameters may change during planning and, under certain conditions, execution. Do not assume recipe approval makes every value immutable.
Define for your process which values are freely configurable, limitedly adjustable, or fixed for a specific batch. Assess the permitted pathway and a targeted invalid attempt, including a value with incorrect units or a correctly formatted value outside the professionally defined range. Such requirements must be technically and organizationally implemented in the real system.
The technical validation check described in the handbook for recipe release serves a more specific purpose than GxP validation. It does not automatically confirm the technical suitability of your manufacturing process. Terminology such as "released" should be explicitly referenced in the protocol, specifying which object and which decision is intended.
Distinguishing the occupancy and suitability of the subsystem
Batch control and partial unit occupancy are included within the described BATCH functionality. Whether a technically available partial unit is suitable for the specific approach may require additional information: intended equipment, process boundaries, cleaning requirements, or any other operational prerequisites. The presence of such information in another system does not constitute effective integration.
Therefore, describe the complete pathway for a start condition. Does it originate from an interface, a user confirmation, or a defined procedural process? What occurs when information is missing, outdated, or inconsistent? A manual check is not sufficient solely because automatic coupling is absent; its appropriateness must be justified on the basis of risk.
For a test, a previously occupied subunit and a free, but externally excluded alternative unit are suitable. The previously defined behavior is expected in each case. Any diversion to another unit must not inadvertently alter the technical manufacturing specification.
Example: new formula, occupied partial unit, interrupted addition
The following example was not executed in BATCH. The recipe batch size is 200.0 kg. The previous specification R-03 contains 10% component K; for the new order A-204, recipe R-04 with 12% K is specified. This results in 24.0 kg of K and 176.0 kg of carrier. The approved batch quantity range in the example is 180.0 to 220.0 kg, inclusive of both limits.
Prior to testing, order A-204, auxiliary unit M-1, and recipe R-04 are defined. Unit M-1 is initially occupied by a different batch. Unit M-2 is available but not designated for A-204. The pilot batch may only commence after confirmed availability of M-1. An ongoing, older batch with recipe R-03 remains separate and must not be silently transferred to R-04.
In the event of a disruption, 14.0 kg of K were added. The technical requirement for a permitted continuation is an additional 10.0 kg of K. A further complete addition of 24.0 kg would result in a total of 38.0 kg of K and would be incorrect. However, a safe decision requires a reliable record of the amount already added; simply reading the value displayed after a system restart is insufficient for this purpose.
Each independent variant starts from a documented copy of the initial state. For a continuous interruption scenario, previously recorded events are retained. The table contains target values, not observed test results.
| Variant | Predefined expected result | Consequence to be examined |
|---|---|---|
| 200.0 kg; R-04; M-1 available | 24.0 kg K + 176.0 kg carrier | Correct instruction and process unit |
| 200.0 kg; intended R-03 | 20.0 kg K would be incorrect for A-204. | Detect an invalid assignment |
| M-1 occupied; M-2 available | No start on M-1; no quiet transition to M-2 | Prerequisites effectively implemented |
| 180.0 / 220.0 kg; R-04 | 21.6 + 158.4 / 26.4 + 193.6 kg | Limits including accepted |
| 179.9 / 220.1 kg | Outside the example scope | No routine order release |
| Interruption after 14.0 kg K | Remaining: 10.0 kg; Total K: 24.0 kg | No double dosing |
| The amount already added cannot be established | No decision on residual quantity without checking | Agreed Failure Procedure |
| Batch completed; recipe reference missing | Evidence for A-204 incomplete | No unjustify ed conclusion of release assessment |
Read the batch record together with the operator actions
The batch report serves as a starting point for evaluation, not automatically constituting a complete substantiation of all technical questions. Define which identities, parameters, interventions, time references, and result data are required for the intended assessment. Subsequently, verify that the report and underlying data clearly integrate these information elements.
Chapter 4 of the EU GMP Guideline addresses timely documentation and traceable changes. For the example, original instructions, permitted modifications, and actual execution must remain distinguishable. A subsequently generated report must not erase a prior intervention without proper explanation. The required history shall follow the relevant data and decisions.
Review role-specific responsibilities: Can a user initiate a batch, modify a recipe, or merely view data? What technical changes are authorized for an administrator? A user confirmation is not automatically equivalent to an electronically signed, legally binding signature. Such functions are assessed only with version-compliant documentation and specific configuration details.
Utilize matching supplier documentation and complement with open transfer points
A manufacturer- or integrator's package may contain valuable validation evidence. Assign these to your requirements: Which version, configuration, test environment, and result status are actually in use? A test of the recipe structure may be appropriate, but it may leave open operational preconditions for a partial facility. Conversely, project-specific supplier tests can already cover this handover.
In the system context, suitable FAT documents can be used under justifiable conditions. It is crucial whether installation, transport, integration or configuration changes influence the statement. A repetition of each test is just as untargeted as the flat-rate adoption of a package.
Plan additional checks where transferability is insufficient. Separate required and actual observed performance. When an unexpected sub-unit is selected, document the actual process flow and assess the impact before modifying the configuration and perform a targeted revalidation.
Evaluate recipe modifications and technical updates during operations
Distinguish a new manufacturing instruction, a permission modification, and a technical update. All may have relevant implications, but not the same. A changed formula requires different validation evidence than a new report or a modified integration with PCS 7.
The V10.0 Handbook describes technical status assessments following an update to the system. Therefore, pending tasks and already planned batches must also be evaluated. The technical status determined by such an assessment must align with your professional judgment. The exact responses will be verified based on the actually installed version.
For backup and restoration the associated information counts. A recovered recipe without suitable batch data or an archive without readable context can be useless for the intended purpose. Check a representative recovery case and the subsequent access. Technical redundancy alone does not replace this proof.
Preparation: What Production, Automation, and QA Provide
Before establishing a reliable cost estimate, you require a limited process scope. The number of existing recipes alone provides little insight: reusable workflows, alternative formulas, different route configurations, and poorly traceable transfers have a greater impact on operations. Absence of decisions regarding authorized interventions cannot be compensated by additional test documents.
Production outlines manufacturing specifications and permitted exceptions. Automation or integrator provides details on implementation and equipment integration. IT is responsible for the agreed operational services; QA evaluates GMP-related evidence and outstanding risks. In small teams, roles may overlap, but responsibilities must remain clearly defined.
With this preparation, a realistic testing protocol can be developed and aligned, defining the activities that must be completed prior to usage. A fixed duration or a flat fee is not feasible given the product name.
- List installed BATCH-/PCS-7 systems, components, and interfaces.
- Select a representative order with recipe, formula and sub-assembly.
- Define technically acceptable parameter changes and operational prerequisites.
- provide rolling, testing environment and recoverable output data.
- Make available to view existing supplier/integrator certifications together with deviations.
- Required batch data, report, and retry procedure are defined.
Project experience and collaboration
Identify the recipe version used in the BATCH report
With your team, we trace a recipe version to the executed batch and available event records. This establishes which conclusions a BATCH report supports and where additional data are needed. A single recipe change can provide a manageable starting point. For a new batch process, we first agree the scope, systems involved and test objectives. We link the evidence to the version actually in use.
Frequently asked questions about SIMATIC BATCH
Has SIMATIC BATCH been validated by the manufacturer?
Manufacturer documentation demonstrates a specific product and testing scope. For your intended use, assess alignment with version, recipes, equipment integration, and requirements. Suitable documentation can be adopted. The recipe validation referenced in the product is a technical evaluation; it does not substitute for evidence that your intended batch process, including organizational and interface aspects, is adequately supported.
What role does PCS 7 play in batch validation?
The batch operates within the PCS-7 environment. Therefore, relevant transfers to automation and operation must be defined in the scope of work. It is not necessary to validate every PCS-7 function. However, robust evidence must be provided for the components used and for the system chain upon which the actual batch process actually depends.
Must internal and external formulas be tested equally?
Both must meet their respective technical requirements, but their usage may differ. Specifically review assignment, source of values, and permitted changes. The V10.0 Handbook describes both formula types and subsequent parameter modifications. Therefore, a targeted selection of representative cases is recommended; an identical test list for each formula is not required.
May a parameter change while a batch is in progress?
Only within the designated and approved framework for your process. The V10.0 Handbook outlines technical modifications during execution. Define which changes are permissible, who is authorized to make them, and what evidence of approval remains. Also assess any unauthorized attempt. Technical modifiability alone does not constitute professional authorization.
Does a standalone portion of the facility already demonstrate its GMP suitability?
No. Availability or occupancy first addresses a technical assignment question. Additional operational prerequisites may be required for your process. Verify the actual technical or organizational implementation, including missing or outdated information. The application does not need to manage every prerequisite itself, but the entire intended control must be logically justified and function effectively.
How do we assess a restart without an actual production batch?
Use an appropriate test environment with a defined initial state and realistically represented transfer profiles. In the example provided in this article, predefined quantities, remaining quantities, and allowed continuation are already specified. The limitations of the simulation are documented; physical plant responses may require additional supporting evidence. A successful screen-based example does not automatically validate the complete plant functionality.
Is a BATCH report sufficient as a batch record?
A batch report must include the data and relationships required for your batch evaluation. If relevant parameter changes, events, or recipe references are missing, additional controlled-available records are needed. Therefore, compare the report against a specific batch case and its original data. The PDF format alone does not substantiate completeness or the linkage to the original records.
What documents should be available prior to project initiation?
Useful are system and version overviews, representative recipes with formulas, document attachments, role assignments, and existing tests. Supplement the technical rules for initiation, modification, and suspension. This enables production, automation, and QA to discuss the same cases and specifically define outstanding evidence requirements, rather than first creating a general document set without process context.
What determines effort and duration for a small company?
Key factors include differences between recipe families, the number of critical transfer points, custom programming, and the availability of an appropriate testing environment. Additionally, it is important whether existing documentation is clear and transferable. A smaller facility with individually linked equipment may require more coordination than a larger site with a limited number of standardized processes. A fixed time estimate would be unjustified without this information.
Does every BATCH update require a complete revalidation?
A change is evaluated for its impact. Affected functions, open batches, interfaces, and data usage determine the additional testing requirements. Appropriate, unchanged valid evidence remains applicable. Document the rationale why selected tests are sufficient and identify any limitations. Technical update success alone is not a conclusive determination, nor is a blanket comprehensive retest.
Sources and review date
As of 6 October 2026. Product mechanics is limited to the BATCH Handbook V10.0 (05/2024) and BATCH-/PCS-7 documentation V10.0 SP1 (03/2025). SP1 is not designated as the latest version. Examples and target values are standalone reference aids; no installation or setup has been tested for these.
- Siemens: SIMATIC BATCH V10.0 – Operating Manual
- SIMATIC BATCH Readme V10.0 SP1 (Online)
- SIMATIC PCS 7: PC Configuration V10.0 SP1
- European Commission: EudraLex Volume 4
- EU GMP Annex 11: Computerised Systems
- 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: .
Base the evidence on your actual batch process
We support you in distinguishing recipe, equipment, and data transfers, categorizing existing documentation, and preparing the required assessments.
- 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.

