2 Product introduction and installation
2.4 Components of SIMATIC BATCH
2.4.1 Components of SIMATIC BATCH
SIMATIC BATCH consists of the following components:
• BATCH Start Coordinator
• Batch Control Center (BatchCC)
• BATCH Recipe Editor
• BATCH Report
• BATCH Control Server
• Batch CDV
• BATCH interface blocks
2.4.2 BATCH Start Coordinator
Introduction
The BATCH Start Coordinator is responsible for the following:
• Communication to the OS
• Data storage for SIMATIC BATCH
• Monitoring of the SIMATIC BATCH data storage
• Controlling, monitoring, starting and stopping the SIMATIC BATCH server applications
Startup
The BATCH Start Coordinator starts automatically at logon on the computer on which the BATCH server is installed. It is displayed as an icon in the task bar (lower right) and is in the "READY" status.
The Batch Control Server and the Batch data management, SIMATIC BATCH CDV, are automatically started in addition to the BATCH Start Coordinator. These two server applications are also displayed as icons in the task bar. The Batch Control Server and the Batch data management are then in the "READY" status.
If the BATCH Start Coordinator are not started automatically with the two server
SIMATIC BATCH
A5E00495287-01 2-5
Shortcut menu of the BATCH Start Coordinator
The BATCH Start Coordinator, which is shown as an icon in the task bar, offers the following settings and functions. When you right-click on the BATCH Start
Coordinator icon in the task bar, its shortcut menu is displayed. You can set the startup characteristics under "Settings". Select on of the three options:
• SIMATIC BATCH starts automatically after WinCC starts:
• SIMATIC BATCH starts automatically regardless of WinCC
• SIMATIC BATCH is started manually
The preferred setting is the start option "Start Simatic BATCH automatically after starting WinCC". This means that the BATCH Start Coordinator is automatically started as soon as you start your WinCC project in process mode (activate runtime).
You can also configure the startup characteristics of the Start Coordinator in the
"Configure batch process cell" dialog of the SIMATIC Manager. These settings there only go into effect when the Start Coordinator is not active in the task bar at the time the changes are made.
The "Start" function is displayed under "Startup/shutdown". Click "Start" to set the BATCH Start Coordinator from the "READY" status to "RUNNING" status. The Start Coordinator then starts the two other BATCH applications. You can only work and communication with the SIMATIC BATCH editors (BCC and BRE) when all BATCH applications are in the "RUNNING" status, indicated by a green triangle in the icons of the applications in the task bar.
Note:
If the server applications do not start, indicated by a red triangle, generate, compile and download the Batch data again. Check the configuration of the PC station (computer name, IP address, etc.).
Additional information
• BATCH Control Server
• BATCH CDV
• Starting the BATCH server
2.4.3 Batch Control Center (BatchCC)
Definition
The Batch Control Center (BatchCC) is the central component in SIMATIC BATCH for batch planning and batch control. BatchCC manages all the data relevant to SIMATIC BATCH. This means that all Batch data is logged in BatchCC.
The Batch Control Center is started on the runtime computers according to the settings made in the Batch Launch Coordinator.
Functions
With the Batch Control Center (BatchCC), you can:
SIMATIC BATCH
A5E00495287-01 2-7
• Plan production orders using master recipes and batches
• Start and control batch executions
• Monitor and troubleshoot batch executions
• Log recipes and Batch data
2.4.4 BATCH Recipe Editor
Definition
The BATCH Recipe Editor is part of SIMATIC BATCH and provides you with a graphical user interface for creating and modifying master recipes and library operations. Recipe creation is based on the BATCH objects from the batch process cell configuration in the engineering system of SIMATIC PCS 7, for example, units and equipment phases.
Functions
With the BATCH Recipe Editor, you can do the following:
• Create new master recipes and library operations.
• Modify existing master recipes and library operations (structural or parameter modifications).
• Log the master recipes and library operations.
• Release master recipes and library operations for testing or for production.
• Validate recipes.
When working in the editor, the familiar functions known from MS Windows programs such as paste, cut, copy, undo and redo can be used on single or grouped objects.
SIMATIC BATCH
A5E00495287-01 2-9
2.4.5 BATCH Report
Definition
BATCH Report allows documentation of recipes and Batch data in the form of logs.
• The "off-the-shelf" recipe report contains all the data required for production.
This includes the recipe header data, the input material and output material list and the procedural rules.
• The batch report contains all the information required for the reproducibility of the batch process, quality assurance and the fulfillment of legal requirements.
These include the identification data, control recipe data, effective production data, chronological sequence of the steps, error and disturbance messages as well as operator intervention.
BATCH Report is fully integrated in the user interface of BatchCC. The recipe reports and batch reports are created in BatchCC and can be displayed and printed out in BatchCC at any time.
To be able to view recipe reports and batch reports on other computers, for example, at a later time, the Viewer of BATCH Report is available as a separate setup.
Functions
Within an open report (recipe or batch report) you can browse through the individual elements using a hierarchical table of contents:
• Recipe/batch
• Recipe unit procedure
• Recipe operation
• Recipe phase
• Transition
2.4.6 BATCH Control Server
Definition
The BATCH Control server is a component of SIMATIC BATCH. The BATCH Control server handles communication with the process and controls and monitors execution of the current batches.
The BATCH Control Server does not have its own user interface. The BATCH Control Server is started on the runtime computer (redundancy).
Functions
Once a batch has been released and started, the BATCH Control server takes over monitoring of its execution. The batch data (online data) of SIMATIC BATCH are stored temporarily in the online data management of SIMATIC BATCH.
To acquire Batch data (messages), there is a connection to the message server and to the process data acquisition of the PCS 7 OS (WinCC).
SIMATIC BATCH
A5E00495287-01 2-11
2.4.7 Batch CDV
Definition
BATCH CDV is a component of SIMATIC BATCH. It is a server component responsible for acquisition, storage and logging of Batch data.
BATCH CDV does not have its own user interface. It is displayed as an icon in the Windows task bar. The status of the application is displayed with an information button in the shortcut menu. The Batch CDV is started on the runtime computer (redundancy) according to the settings made in the Batch Launch Coordinator.
Functions
The Batch CDV server performs the following three tasks:
1. Collects and stores WinCC messages.
2. Collects and stores WinCC measured values. Only the measured values configured in the running batches are collected and stored.
3. Closing batches. This process is divided into two steps. The transition state
"Closing" leads to the final state "Closed".
2.4.8 BATCH interface blocks
Introduction
SIMATIC BATCH as of V6.0 can use the new functionality of the SFC types in the engineering system to define operation and phase types. As an alternative, SIMATIC BATCH as of V6.0 continues to provide special interface blocks as the communications interface to the processing programs on the programmable controller. These so-called BATCH interface blocks are supplied as a block library with SIMATIC BATCH (see also section "Using BATCH interface blocks").
Definition
The BATCH interface blocks form the communications interface between SIMATIC BATCH and the processing programs of the process cell control system in the automation system. The BATCH interface blocks are implemented as CFC blocks and are inserted in the CFC charts according to their function and stored in the corresponding hierarchy folders in the plant view in the SIMATIC Manager.
Functions
Using the BATCH interface blocks along with SIMATIC BATCH, makes the following functions available:
• Controlling the procedure:
The IEPH/IEOP blocks are used for this purpose. These provide the
commands (for example start or put on hold) of the recipe control steps from the batch control to the processing blocks (for example,. SFC_CTL or user blocks). The processing blocks report their current statuses back to the batch control.
• Assigning and releasing a unit via a running control recipe:
The IUNIT_BLOCK blocks are used for this purpose.
• Summing up actual values for the creation of transition conditions and for logging measured values in the batch log:
The TAG_COLL blocks are used for this purpose.
• Transferring setpoint and actual values:
The IEPAR blocks are used for this purpose. The batch control writes the recipe parameters (setpoints) for the processing blocks into these blocks via the IEPH/IEOP blocks. The processing blocks write the result data (actual values) into the IEPAR blocks so that they can be stored as Batch data by the batch control once again using the IEPH/IEOP blocks.
SIMATIC BATCH
A5E00495287-01 2-13