Introducing Aizon Execute 4.0: Connecting the Batch Record
Aizon Execute 4.0 is a major release that extends the Intelligent Batch Record beyond the boundaries of a single record. Equipment status now updates from execution. Recurring records are created on a defined schedule rather than by hand. Data moves between process orders without transcription. And events in Execute can trigger action in Aizon Unify — with traceability at every step.
What's New in Execute 4.0
Five capabilities in this release close the gaps between the batch record and everything around it: the equipment on the floor, the records that come before and after, and the analytics layer above.
1. Equipment Status Management
Until now, the equipment used at each step lived inside the batch record and nowhere else. Execute 4.0 lets you model your facility on the ISA-95 physical hierarchy — site, area, process cell, unit, equipment — and define the statuses your SOPs already use, such as clean, in use, or under calibration. Master recipes declare which asset type a phase requires, and execution updates that asset's status automatically. Equipment usage history becomes traceable in the batch record itself.
2. Schedule-Based Creation
Some batch records are predictable — a room cleaned every Monday, a fixed monthly quality run — and each one still had to be created by hand. A schedule defined once on a general recipe now generates process orders for every approved master recipe it contains, as Planned or released and Ready to start. Operators find them waiting at their station, attributed to the system in the audit trail. Manufacturing orders continue to originate as they always have: manual creation or your ERP integration.
3. Attributes and Results
Finding one critical value — a final pH, a step yield — meant working down through the execution record to get to it. Master recipes now distinguish Attributes, the critical outcomes of a step, from Arguments, the settings that go into it. Attributes defined in the recipe are captured during execution and surfaced as Results on the process order, so reviewers see the values that matter without granular log analysis.
4. Cross-Process Data Linking
Long processes are often split across several process orders running over weeks, where the output of one step is an input to the next. That value was read off one record and typed into another. Links configured at the general recipe level now map a Result on one process order to an Argument on another. Values populate automatically, stay pending until the source Result exists, and a correction made upstream propagates downstream. Manual transcription between records disappears, and so does the error it introduces.
5. Event and Actions Sync
Getting Execute data into Aizon Unify meant pulling on a timer. Execute now emits an event when a milestone occurs — a process order finishes, a master recipe reaches review. Unify subscribes to the events it cares about, applies its own conditions, and runs an action: a custom function, a notification, or a call back into the Execute API for fuller context. One configuration emails the compliance team the moment a recipe is ready for review. Integration follows the work instead of the clock.
Learn More
Execute 4.0 also carries a wide set of usability refinements, performance improvements, and fixes across the platform, and existing customers can find the full detail in the 4.0 release notes and the upcoming-features training module.
Book a demo with our team to learn more.