Run the Demo

The demo includes various screens that allow you to manage batches and monitor the results.

• The Schedule Batches screen allows you to schedule batches.

  • Use the drop-down list at the top to select a schedule CSV file to load. The CSV files are located at "C:\Schedule". Clicking the Load Schedule button loads all of the entries in the selected schedule file into the batch schedule. This demonstrates using the AVEVA Batch Management Stateless API to schedule batches from an external source.

  • You can manipulate scheduled batches using the AVEVA Batch Management GUI control buttons on the right of the list ("Cleanup", "Initialize", and so on).

  • You can change a batch's train using the AVEVA Batch Management GUI controls beneath the list.

  • The current status of the trains is shown at the bottom of the screen. A train's status is calculated by looking at all of its unit statuses; if any are busy, then the train is marked as busy.

• The Current Batches screen shows the status of currently active and scheduled batches.

  • Use the AVEVA Batch Management GUI controls to show the batches and to start them, hold them, and so on.

  • The AVEVA Batch Management SFC control shows the procedure for the selected batch.

• The Process Dashboard screen shows an overview of the process.

  • Units and connection segments change color depending on their status.

  • Click on a unit to see a detailed status for that unit.

  • The Phases buttons go to the Unit Phases screen.

  • The Operate buttons go to the Phase Execution screen.

• The Unit Phases screen shows the status of all the phases for that unit, using the AVEVA Batch Management Object Graphics.

• Use the Phase Execution screen to interact with the phases running on the unit, using the AVEVA Batch Management GUI controls.

• The Recipe Compare screen enables you to compare two different versions of a recipe and see what was changed.

  • Select the Original and Compare To versions of the recipe in the lists and click Compare. The report will be shown below.

  • This screen is an example of how the Stateless API can be used to compare recipe versions.

• The Mixer units contain a phase named GetQAResults. This phase is implemented in Application Server as a scripted phase using the AVEVA Batch Management Phase Object.

  1. When this phase executes, it will go out to the "C:\qa_results" folder and get the associated results file for the unit and return this info using a phase parameter.

  2. The recipe is then written to call this phase and then take one branch or another depending on the result.

  This is just one example showing how the AVEVA Batch Management Phase Object can be used to run scripts that can interface with external systems and/or return data that can influence the execution of the batch.

• The AVEVA Batch Management Unit Objects for the Mixers contain scripts to monitor for Batch Events.

  • Each Mixer Unit Object subscribes to Operation Done events for the "Mix Materials" operation for their respective train.

  • When an event is received indicating that the specified operation is complete, the script schedules a corresponding batch using recipe "CB1000 Hold" to transfer the contents from the Mixer to the Hold Tank and starts the batch.

    This is just one example of how Batch Events can be used to perform custom actions in response to a batch related event.