FactoryTalk Batch Software

Shared configuration across redundant batch servers

• Eliminates configuration drift: Engineers no longer need to worry about mismatched recipes, equipment models, phase logic, or security settings between servers. 
• Simplified system management: Changes are made once and automatically available to both servers, reducing engineering effort and maintenance overhead. 
• Lower risk during failover: When the standby server takes over, operators see the exact same system behavior, minimizing surprises or process deviations. 
• Easier validation and compliance: A single configuration baseline supports regulated industries by reducing validation scope and audit complexity.

Faster warm restart and initial hot restart capabilities

• Minimal batch disruption: Batches can resume closer to their point of interruption instead of restarting or requiring manual recovery.
• Lower impact of maintenance activities: Scheduled updates, patches, or reboots take less time and cause shorter production interruptions.
• Improved uptime and throughput: Faster restarts reduce non-productive time, especially on high-volume or continuous batch schedules.
• Less operator confusion: Operators don't need to reconstruct batch state or manually determine what steps were already completed.

Reduced recovery time and lower operator intervention after restarts

• Consistent, repeatable recovery behavior: Automated recovery reduces human error during stressful or time-critical events.
• Reduced training burden: Operators don't need deep knowledge of recovery procedures for complex batch scenarios.
• Improved safety and quality: Less manual intervention means fewer chances to restart batches incorrectly or bypass required steps.
• Faster return to steady-state production: Operators can focus on monitoring rather than troubleshooting.

Event journaling for recipe and parameter changes

• End-to-end traceability:
  • Every modification to recipes or batch parameters is time-stamped, attributed, and preserved.
  • Creates a clear lineage of how each batch was produced, even over time and across revisions.
• Stronger data integrity (ALCOA+):
  • Supports regulatory expectations for Attributable, Legible, Contemporaneous, Original, and Accurate records. 
  • Reduces reliance on manual logs or external tracking systems that are prone to error.
• Faster investigations and root-cause analysis:
  • Engineers and quality teams can quickly identify when a change occurred and its impact on affected batches.
  • Shortens investigations during deviations, non-conformances, or corrective actions (CAPAs).
• Reduced risk of unauthorized changes:
  • Visibility into all changes acts as a deterrent and ensures accountability.
  • Simplifies enforcement of change-management procedures and electronic signatures (where applicable).

Improved audit preparedness for regulated environments

• Always-available audit evidence:
  • Audit data is collected continuously, not assembled retroactively.
  • Reduces the scramble to compile logs, screenshots, and spreadsheets before inspections.
• Shorter, smoother audits:
  • Auditors can readily review who changed a recipe or parameter, what version was used for a given batch, how the system behaved during execution
  • Fewer follow-up questions and less disruption to operations.
• Reduced compliance burden on teams:
  • Quality, IT, and operations spend less time preparing documentation.
  • Frees experts to focus on process improvement rather than administrative overhead.
• Greater confidence during inspections:
  • Consistent, system-generated records demonstrate control and maturity of the batch environment.
  • Helps build trust with auditors and regulators.

New and enhanced read-only API endpoints

• Safe integration with enterprise systems:
  • MES, ERP, LIMS, historians, analytics platforms, and data lakes can consume batch data securely.
  • Eliminates the risk of external applications accidentally changing recipes, parameters, or batch state.
• Faster and simpler integrations:
  • Standardized, documented endpoints reduce custom development and maintenance effort.
  • Integrators can pull the data they need without deep knowledge of internal batch logic.
• Scalable digital transformation:
  • Supports modern use cases such as advanced analytics and AI/ML, digital twins, KPI dashboards and performance monitoring
  • Enables expansion of data consumers without increasing operational risk.
• Clear separation of responsibilities:
  • Batch execution remains controlled and validated.
  • Enterprise and IT teams gain visibility without needing privileged access.

Improved visibility into batches, recipes, and equipment without added risk

• Enterprise-wide operational transparency:
  • Stakeholders can view batch status and progress, recipe versions and usage, equipment utilization and availability
  • Reduces reliance on screenshots, manual reports, or ad-hoc data requests.
• Better decision-making at all levels:
  • Operations managers gain insight into throughput and bottlenecks.
  • Quality teams can correlate outcomes with recipes and execution context.
  • Supply chain and planning teams get accurate production status.
• Zero impact on validated environments:
  • Read-only access avoids re-validation triggers common with writable integrations.
  • Supports regulated industries where system changes must be tightly controlled.
• Reduced operational risk:
  • No additional load on operators.
  • No chance of external systems interfering with live batch execution.

Improved navigation with enumeration sorting

• Faster task completion:
  • Engineers and operators can find the right value more quickly, reducing time spent scrolling or searching.
  • Common tasks like recipe editing, parameter selection, and configuration updates become more efficient.
• Reduced user errors:
  • Logical, predictable ordering lowers the risk of selecting the wrong enumeration-especially in systems with many similar options.
  • Helps prevent subtle configuration mistakes that can lead to batch deviations or rework.
• Lower cognitive load:
  • Users spend less mental effort interpreting lists and more time focusing on process intent.
  • Particularly valuable for infrequent users or operators who rotate across systems.
• More consistent experience across the system:
  • A cleaner, more predictable Ul improves confidence and usability for both new and experienced users.

Faster troubleshooting using formulation duplication

• Rapid root-cause analysis:
  • Engineers can isolate and test changes by working from a known, validated baseline.
  • Makes it easier to identify which parameter or step is driving an issue.
• Reduced risk to production:
  • Original formulations remain untouched, protecting validated and approved recipes.
  • Troubleshooting can occur without jeopardizing live or released configurations.
• Shorter downtime and quicker resolution:
  • Faster experimentation means issues are resolved sooner, minimizing production delays.
  • Supports parallel problem-solving without waiting on full change-control cycles.
• More efficient continuous improvement:
  • Teams can easily explore optimizations or process improvements before formally promoting changes.
  • Encourages best practices without increasing administrative burden.

• Integration with OPC UA data servers via FactoryTalk Linx OPC UA Connector for seamless data integration and improved operational efficiency
• Browing data server paths now includes FactoryTalk Linx OPC UA Connector

• Script the import of complete or partial Area Model XML (AXML) files into an Equipment Model configuration (CFG) file
• Import via Command-line or scripts
• Develop using your preferred tools and seamlessly integrate those area models within FactoryTalk® Batch

• Script the import of recipes to automate the import process, improve workflows and reduce manual efforts
• Simplifies importing and exporting files from different systems, allowing more design modularity
• Supported through the Batch XML format only

• Updated archive database schema, resulting in performance to speed up transactions, queries, and reports
• Introduces a new database migration utility, making it seamless to transition older databases to the new database schema for FactoryTalk Batch version 15 and later

• Add batches to the batch list without specifying all parameters
• Introduces three new API endpoints
• Allows for ongoing support of streamlined batch management, improved integration capabilities, and repeatable and modular design

Enhanced Batch Journals

• New batch journal file format makes parsing and sharing data easier.
• Allows the addition of new data fields without breaking parsing tools and third-party applications.

UTC time stamps

• Improves integration & correlation of data across data sources, by adding UTC time stamps into the new EVTJ journal format.
• UTC time stamp from the EVTJ journals is used in the FactoryTalk Batch History Database so that they do no must be calculated, thus improving the accuracy and consistency UTC time stamps in the database.

Deferred Material Parameters

• Reduce the number of recipes with material-based recipe and batch creation workflow improvements. Support for deferring material parameters, lots, and labels. Revamped batch creation workflows to support additional material-based workflows.

Enhance support for scripting in manual instructions

• Improved support for custom scripting in eProcedure® Manual Instructions. Build custom scripts to accept barcode inputs and interact with objects in the instruction file.

Expanded Runtime Area Model Updates

• Support for additional runtime area model edits and increased system limits combine to make your system more flexible while at the simultaneously improving the system uptime.
• Delete and remove elements from an area model at runtime.

Phase/Sequence Program Selection

• Enabled flexible modular factory design.
• Promote reuse of controller code
• Improve integration of OEM skids into a system

Improved Phase synchronization

• Added support for the new Phase program name property
• Fewer issues when synchronizing phases between FactoryTalk Batch and Logix Designer application project files.
• Support for additional synchronization workflows

Increased Tag Count

• Improve support for large complex systems and OEMs by increasing the overall limit on the number of tags that can be included in an Area Model.

Increased Memory Limits (LBA)

• Support larger and more complex systems by taking advantage of the 4.0GB of memory available to 32-bit processes on 64-bit operating systems.
• Improve system stability and uptime, with new guardrails that help prevent users from performing actions that will cause the server to run out of memory.

• eProcedure subscribes to Area Model data from the Batch Server allowing it to support runtime area models updates without restarting the eProcedure server.

• eProcedure® server will start even if there are missing or malformed instruction files, while still helping prevent execution of batches that have missing instruction files.

• New runtime area model edits make your system more flexible while at the simultaneously improving the system uptime.

Recipe formulations

• Use recipe formulations to reduce the complexity of recipe management and provide greater flexibility in product variations.
• Easily adjust for seasonal, environmental, or other discrepancies.

FactoryTalk® Linx adoption

• Take advantage of the improved connectivity and stability of FactoryTalk Linx Enterprise for communication with PhaseManager™ and SequenceManager™.

Modern intuitive interface

• FactoryTalk® Batch View™ provides a modern and intuitive portal into a comprehensive batching solution for effective operations.
• The product leverages its own web server using HTML5 technology to provide fundamental connectivity into a FactoryTalk Batch Server
• Zero install simplifies device administration on the client

FactoryTalk® View SE integration

• User credentials are automatically inherited from FactoryTalk® View SE Client, reducing the amount of scripting required for integrated security.
• When the runtime language in the FactoryTalk View SE client is changed, the FactoryTalk Batch View HMI Controls automatically update as well.

• FactoryTalk Batch v14.0 is the first release to include the new Enterprise Integration API. This API is built on top of the BatchView™ web server and provides a modern API that allows the web-based enterprise system to easily integrate with FactoryTalk Batch