Seal vs Siemens Opcenter Execution Pharma

1Opcenter Execution Pharma and Seal, side by side.

Opcenter Execution Pharma and Seal both turn an approved master batch record into guided, signed electronic execution with review by exception. They differ in what the batch record is joined to. Opcenter Execution Pharma integrates natively with the distributed control system beneath it,¹ while In Seal, teams configure lab, manufacturing and quality workflows on one platform around a shared ontology, so the batch, its results and its quality events are records in the same system.

2What Opcenter Execution Pharma is built for.

Opcenter Execution Pharma is built for pharmaceutical manufacturers that want electronic batch records joined closely to their automation layer. It was formerly known as SIMATIC IT eBR, and Siemens Digital Industries Software sells it as part of its Siemens Xcelerator portfolio.¹ Siemens describes a master batch record-driven approach that plans the product definition, resource requirements, process definitions, quality management plans and batch review and release procedures, and says the master batch record incorporates values directly from the automated recipe.²

Siemens lists these functions:³

• Master batch records with graphical workflows, a text editor, pre-built work elements and parameter management.
• Material management from goods receipt, sampling and QC through picking, tracking and goods issue.
• Weighing and dispensing with scale management, 16 predefined weighing methods and potency and density calculations.
• Electronic batch records with electronic instructions, deviation management and release by exception.
• Equipment management for fixed, mobile, single-use and reusable equipment, with an equipment logbook.
• Packaging with line instructions, in-process quality control and reconciliation.
• Automation integration through OPC and OPC UA clients, an MES task list in the HMI and native integration with SIMATIC PCS 7 and SIMATIC Batch, and enterprise integration including Opcenter APS and Opcenter Laboratory.

Version 2511, described by Siemens in December 2025, brought execution of existing operating text in a web browser without redesigning the Process Instructions, and version 2605, in June 2026, extended the web Operator Cockpit and added a web-based weighing application that runs alongside the existing rich-client one for scenarios it does not yet cover.⁴⁵ Version 2605 also added AI: Smart Operation Designer for authoring work instructions, and an AI-based documentation assistant for product knowledge.⁵

3How a process instruction changes.

Both products version the recipe and keep earlier batches tied to what they ran. Opcenter Execution Pharma organises the recipe as Process Instructions built from operating text, sub-processes and scripts; Seal holds the master batch record as structured steps whose changes carry their own reason and verification.

In Opcenter Execution Pharma, Process Instructions can call shared sub-processes and scripts. Since version 2511, an API upgrades the version of each parent Process Instruction automatically when a sub-process or script it calls is updated. Process Instructions move between environments through an import module whose report highlights critical operations, and they can be imported from a different Opcenter version.⁴ Version 2605 lets Process Instructions be imported via API in standardised file formats, and Smart Operation Designer uses AI to extract process information from existing PDF documents into structured electronic work instructions, with a copilot to refine them, templates for standard designs and the option to import a workflow from a BPMN file.⁵

In Seal, the change records why it exists, what it changes and how it was verified. In the example in Seal’s change control blueprint, deviation DEV-018 found a 52-minute post-mix hold on batch B-041 against a 45-minute limit. Changeset CC-019 makes master batch record MBR-014 v05 calculate the elapsed hold from the start and transfer timestamps and route any hold over 45 minutes for assessment. The limit itself does not change, and a missing timestamp reports neither a duration nor a pass.

The verification plan sits on the same changeset: holds of 44 and 45 minutes must stay within the limit, 46 minutes must take the exception route, and a missing start time must leave the record incomplete. A saved plan is not a passed test; the release review asks for the executed checks, the updated configuration specification and the training needs before authorised people approve. Batch B-042 then runs v05. B-041 keeps the version it ran against, and its disposition remains a separate review.

Reuse works through the same definition. Authors reuse approved patterns for dispensing, line clearance, sampling or reconciliation without copying uncontrolled text between records, and the displayed instruction is generated from the structured requirements. When a batch is created, Seal resolves which master version applies for the product, site, market and start date, and records the versions selected.

4How alerts and exceptions are reviewed.

Both products bring abnormal events to a reviewer with signatures. They differ in where the related laboratory and quality records live.

In Opcenter Execution Pharma, operators and reviewers handle alerts, whether deviations or remarks, from the web Operator Cockpit and sign them through signatory paths defined during engineering. Documents attached to a work order as annexes become part of the batch record, and supervisors and reviewers review and sign their conformance; an annex that does not conform can be rejected.⁴ Version 2605 strengthened electronic signature handling for forced values and tolerance deviations.⁵ Genealogy and audit trail tools search forward and backward, and Siemens describes a centralised point of review for alarms, events and reports.⁵²

In Seal, a deviation opened from a step inherits the batch, process version, materials, equipment, values, people and time window, so containment and impact assessment start with a defined population. An in-process result belongs to the batch step it governs, with its sample, method and specification, and the next operation can depend on it. The investigation, the CAPA and any change to the master record stay linked to the deviation, and QA can disposition the batch only when the effective release requirements are resolved.

5Where Opcenter Execution Pharma is the better fit.

Opcenter Execution Pharma is the better fit when your plant runs on Siemens automation and you want the MES and the control layer from one supplier.

• Your production runs on SIMATIC PCS 7 and SIMATIC Batch, and you want native MES integration with the MES task list in the HMI.³
• You want scheduling and laboratory software from the same portfolio, through the integrations with Opcenter APS and Opcenter Laboratory.³
• You have a large library of Process Instructions and want to move operators to web execution without redesigning them.⁴
• Your dispensing needs predefined weighing methods with potency and density calculations, and your packaging lines need in-process quality control and reconciliation in the MES.³
• You want AI to convert existing PDF procedures into electronic work instructions inside your MES engineering tools.⁵

6Where Seal is the better fit.

Seal is the better fit when the batch record should share its records with the laboratory and quality work, and when what you learn should reach the next batch as a tested change.

• Manufacturing execution, laboratory, quality, training and inventory share one platform, so a result, deviation or material lot links to the step it concerns, and an investigation starts from the linked evidence.
• Each improvement becomes a new process version with its specifications, test evidence and approvals. Selected acceptance tests run when a changeset is prepared for review, and earlier runs keep the version they used.
• Neil configures the process from your procedure or master batch record, answers batch questions with sources and prepares changes with their tests. In line with the EU’s draft GMP Annex 22 on AI, Neil is not used in GMP execution. It helps set up configuration, which your team verifies and releases under change control.
• You can start with one process alongside the MES and control systems you already run.

7Running Seal alongside Opcenter Execution Pharma.

Seal has no dedicated Opcenter connector. Where an existing MES stays in place, Seal connects the records a job needs, and each connection’s scope records which system owns them.

Seal’s REST API reads and writes records from another system, and Scripts are versioned Python that can call an external service after an event or on a schedule, edited in a changeset and tested like other Seal records. On the Siemens side, Opcenter Execution Pharma offers interfaces and standard connectors to other business and manufacturing systems, and Process Instructions can be imported via API.³⁵ For process values, Seal’s Siemens S7 and OPC UA pages describe what each of those routes collects and what it does not.

A common arrangement keeps Opcenter Execution Pharma executing batches while Seal runs a laboratory or quality workflow, or while Neil investigates a recurring exception from the records it is given. Start with read access, agree the source of record and treat any write-back as a separate decision. The regulatory guide sets out how to qualify the connection: identifiers, field mappings, missing and duplicate records, and reconciliation against the source.

8Moving from Opcenter Execution Pharma to Seal.

Move one process first, and keep Opcenter Execution Pharma as the record for everything you have not moved.

1. Choose a process whose master record changes often, or whose exceptions keep returning to the same step.
2. Bring the procedure or master batch record, a representative batch and the records it touches. Use sample material, or arrange an NDA before sharing confidential records.
3. Neil proposes the steps, fields, calculations, material and equipment requirements and review gates, and your process experts check the mapping. Once the scope is agreed and the inputs received, Seal prepares the first working configuration and its validation pack within 48 hours.
4. Exercise version resolution for a new order, valid and invalid scans, limits, holds and deviations, signatures and verifier rules, and recovery from an interface failure.
5. Agree which records move and which stay retrievable in Opcenter Execution Pharma, and reconcile representative records before relying on the new workflow.

Production timing then depends on scope, interfaces, migration, operational readiness and your release requirements. The MES blueprint describes how a run, its review and its next version work in Seal.