Seal vs Emerson DeltaV MES (Syncade)

1DeltaV MES and Seal, side by side.

DeltaV MES and Seal both guide operators through an approved recipe, keep a signed electronic batch record and send exceptions to review before release. They differ in where the batch record is anchored. DeltaV MES sits on Emerson’s DeltaV Automation Platform beside the DeltaV control system and gathers data from ERP, LIMS, CAPA and maintenance systems into one batch record.¹² In Seal, teams configure lab, manufacturing and quality workflows on one platform around a shared ontology, so an exception, its investigation and the change that follows are records in the same system.

2What DeltaV MES is built for.

DeltaV MES is built for life sciences manufacturers, with native integration to Emerson’s DeltaV control system and interfaces to other control systems.² Emerson Electric Co. sold it as Syncade, and calls DeltaV MES “the newest evolution of the Syncade MES”.³ In March 2024 Emerson extended its DeltaV brand, long used for its distributed control and safety systems, into the DeltaV Automation Platform, adding SCADA, MES and operations management software, all supported through its Guardian digital customer experience.⁴ Earlier material, such as the Message Broker data sheet, still carries the Syncade MES name.⁵

Emerson sells DeltaV MES as part of a life sciences software suite with these solutions:¹

• Electronic Batch Record, which integrates natively with the DeltaV DCS or communicates with other DCS, PLC and SCADA systems, and keeps recipes in a library of class- and instance-based objects consistent with ISA-88 and ISA-95.²
• Quality Review Manager, for identifying, reviewing and resolving process exceptions while the batch runs.⁶
• Material Management, Equipment Management with an electronic equipment logbook, and Information Integration with ERP, LIMS and CMMS.¹⁷
• Workflow Management, cloud software for recipe authoring, execution and data capture, introduced in April 2024 for early-stage life sciences companies with limited IT infrastructure.³
• Digital Batch Record, a paper-on-glass entry point with recipe import, version control and approvals. Its Recipe Importer, launched in January 2026, converts paper batch records written into a Microsoft Word template into digital recipes, which developers review and test in a built-in simulator before production.⁸⁹

DeltaV MES runs both the legacy WF and the newer WFX workflow engines in one instance, so existing recipes can be modernised gradually.¹ For technology transfer, Emerson describes creating a general recipe and risk profile in DeltaV Process and Knowledge Management (PKM) and sending the recipe information to DeltaV MES or the DeltaV DCS through its Tech Transfer Hub.¹⁰ From version 7, DeltaV MES is licensed by subscription; perpetual licences remain usable, but new features come only on subscription.¹¹

3How a recipe changes, before and during a batch.

Both products control the master recipe and allow authorised departures during a batch. They differ in how a departure is modelled and how a lasting change reaches later batches.

In DeltaV MES, recipe authors annotate changes and link documents that explain them, such as URS, design specifications, use cases and validation reports, and the electronic batch record includes archiving, approval signatures and change control. During a batch, users with the right permissions can make in-process changes: modify parameters in real time, adjust navigation, insert new requirements or instructions and require specific signing authority. With permission, they can override forced sequencing, re-execute a step and link further orders, such as equipment set-up or cleaning, to the record.²

In Seal, each abnormal path is part of the configured process: correction, variance, alarm, intervention, deviation, rework, repeat, abort and not-applicable work each have their own permissions, rationale, evidence and approval rules, and the planned path stays visible. Authorised rework creates additional executable work without altering the original course. If an urgent change must apply to live work, authorised users define the transition point and approve the additional instructions, and both the original and the changed course remain on the record.

A change meant for future batches is a new version of the master record. When a batch is created, Seal resolves which version applies for the product, site, market and start date and records it, so a later change does not rewrite work in progress. The new version carries its requirements, specifications and acceptance tests; selected tests run when the changeset is prepared for review, and publication requires current passing results.

4How an exception reaches review.

Both products start review while the batch is still running. DeltaV MES gathers each exception’s context and takes it through configured resolution stages; Seal opens the exception from the step it concerns and keeps the investigation and any resulting change on the same platform.

Quality Review Manager raises exceptions automatically from DeltaV MES workflows when it detects an issue with a critical process parameter, when a non-standard activity such as a forced step occurs, or when a comment is added to a work instruction, and recipes do not need to change to support these exception types. It can also register DeltaV alarms that match configured criteria, and monitor OPC tags through an Event Monitor plug-in. Each exception type can gather data automatically to give the exception its context, and has a severity and resolution stages that must be completed in sequence, each requiring an electronic signature. When all workflows are complete and all exceptions closed, it gathers the review signatures and closes the order. It can be extended to third-party systems that generate exceptions.⁶ For order manufacturing review, Emerson has integrated Informetric’s InfoBatch reporting.²

In Seal, the example in the MES blueprint is batch B-041, whose step 07 hold ran 52 minutes against its 45-minute limit. Deviation DEV-018 is linked to that step and carries the original timestamps and the applicable requirement into review; the authorised reviewer assesses the departure, records the disposition and retains the evidence. The investigator can follow DEV-018 to the batch, its start and transfer timestamps and the version of master batch record MBR-014 used. When the corrective action changes how the hold is controlled, it becomes changeset CC-019, verified before release and linked back to DEV-018, as the change control blueprint shows. Closing the deviation does not release B-041; disposition stays a separate decision.

5Where DeltaV MES is the better fit.

DeltaV MES is the better fit when your plant runs on DeltaV and you want MES, control and support from Emerson.

• Your process control runs on the DeltaV DCS, and you want the electronic batch record to integrate natively with it and orchestrate MES and DCS activity together.²
• You want exceptions raised directly from DeltaV alarms and events into a structured review.⁶
• You manage many products from ISA-88 class-based recipe libraries.²
• You develop processes in DeltaV PKM and want recipe information sent from there to the MES or the control system.¹⁰
• You already run Syncade and want to modernise recipes gradually on the same system.¹
• You need a paper-on-glass start, or cloud recipe software for early-stage work, from the same supplier.⁸³

6Where Seal is the better fit.

Seal is the better fit when an exception should lead to a verified change to the process, with the laboratory and quality evidence on the same records.

• Manufacturing execution, laboratory, quality, training and inventory share one platform, so a result, deviation or material lot links to the step it concerns.
• A corrective action can be released as a new version of the process, carrying its specifications, test evidence and approval, and measured on the batches that follow.
• Neil configures the process from your procedure or master batch record, compares runs 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 control system and MES you already run.

7Running Seal alongside DeltaV MES.

Seal reads process values from DeltaV, and its API can connect records held in DeltaV MES. Each connection is scoped before it goes live: what Seal may read, whether anything is written back and which system stays the source of record.

Seal’s DeltaV connection captures the current value or a completed period of history for a subscribed DeltaV parameter as a reference in Seal, through an IT-approved DeltaV Edge REST API gateway with a dedicated read-only profile. Alarms, events and batch records are not included, and the connection does not change setpoints, acknowledge alarms or operate equipment. Seal’s guide to DeltaV batch record integration works through reconciling DeltaV phase events with historian evidence.

For records held in DeltaV MES, Seal’s REST API and Scripts can make the connection. On Emerson’s side, the Message Broker exchanges XML transactions between the MES and other systems, with configurable retries and reprocessing of failed transactions.⁵ Start with read access, and treat write-back as a separate decision with its own controls.

8Moving from DeltaV MES to Seal.

Move one process first. DeltaV MES and the DeltaV DCS stay in place for everything else.

1. Choose a process whose exceptions keep recurring or whose recipe changes often, such as a clinical or recently transferred product.
2. Bring the procedure or master batch record, a representative batch with its exceptions and the records they touch. 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. Connect the DeltaV parameters the review needs, read-only, and confirm the gateway, parameter paths and capture windows with your automation team.
5. Exercise limits, holds, deviations, rework, signatures and interface failure before release, and agree which records move and which stay retrievable in DeltaV MES.

Production timing then depends on scope, interfaces, migration, operational readiness and your release requirements. Process control stays with the DCS: Seal’s connection reads values and does not operate equipment.