This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.
DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.
WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.
CAUTION
indicates that minor personal injury can result if proper precautions are not taken.
NOTICE
indicates that property damage can result if proper precautions are not taken.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will be
used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to property
damage.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions. Qualified
personnel are those who, based on their training and experience, are capable of identifying risks and avoiding
potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:
WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended or
approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be complied with. The information in the relevant documentation must be observed.
Trademarks
All names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this publication
may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software described.
Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in
this publication is reviewed regularly and any necessary corrections are included in subsequent editions.
Siemens AG
Division Process Industries and Drives
Postfach 48 48
90026 NÜRNBERG
GERMANY
10.5.3Releasing a recipe for testing or production.........................................................................582
10.5.4Revoking a release..............................................................................................................583
11BATCH OS controls..................................................................................................................................585
13.4Command line parameters for BatchCC..............................................................................721
14Context help references...........................................................................................................................723
This documentation provides you with a complete overview of the automation of discontinuous
batch processes with SIMATIC BATCH. The documentation supports you in installing and
commissioning the software. The procedures for process cell configuration and the creation
of batch recipes are described.
You will find information about the software components, areas of application, configuration
options, and commissioning of SIMATIC BATCH in the SIMATIC PCS 7 environment.
The following basic questions are answered in this document:
● What is SIMATIC BATCH?
● What are the software components that make up SIMATIC BATCH?
● Which areas of application is SIMATIC BATCH suitable for in the SIMATIC environment?
● How is SIMATIC BATCH planned, configured and operated in the PCS 7 environment?
● How do you migrate your existing BATCH project to a project that uses the new functions
of this version?
Validity of the manual
1
This manual is valid for the SIMATIC BATCH V8.2 software package.
Language support for the SIMATIC BATCH software and the documentation
The following languages are supported:
● Engineering components and documentation: English, German, French, Chinese and
Japanese
● Runtime components: English, German, French, Spanish, Italian, Chinese and Japanese
Readme files
You will find important information regarding installation on the system / product DVD in the
following documents:
● SIMATIC PCS 7:
● SIMATIC BATCH:
–
Readme
–
What's new
During the SIMATIC BATCH installation routine, you are given the opportunity to open the
readme file and read its contents. Following installation, the documents are available in
SIMATIC > Product Notes > Language Selection.
The following table shows the documentation relating to SIMATIC BATCH at a glance. You
can find the documentation in PDF format after installation of SIMATIC BATCH under Start >
SIMATIC > Documentation > Language selection.
Documentation as manualContents
SIMATIC BATCH
manual
SIMATIC BATCH Blocks
Manual
SIMATIC BATCH - Report Views
Programming Manual
SIMATIC BATCH - COM API
Manual
Additional documents and online help files can be found in the installation path of SIMATIC
BATCH:
Basic and reference information that explains the procedures for configuration and rec‐
ipe creation with SIMATIC BATCH.
Reference information that explains the function, layout, integration, and interconnection
of blocks in the CFC or SFC editor.
Explains how you create your own report templates for reading out the SQL database.
Describes all contents and structures of the BATCH data in the SQL database.
Describes the Application Programming Interface (API) for BATCH object and data ac‐
cess. Examples with source code show how the interface is used.
Documentation as
manual/online help
SIMATIC BATCH - PlugIn concept
Manual, Programming Manual available in English only
SIMATIC BATCH - Report Views
online help
SIMATIC BATCH - COM API
online help
SIMATIC BATCH PCC API
Manual
Storage location and content
Path: \\ProgramData\Siemens\Automation\Batch\Example\PlugIn
This description contains instructions that enable you to develop your own plug-in mod‐
ules for SIMATIC BATCH. This involves an external validity check which is used instead
of the SIMATIC BATCH check.
Path on the SIMATIC BATCH server: \\ProgramData\Siemens\Automation\Batch\Ex‐
ample\Views
“As of SIMATIC BATCH V8.2, you obtain the document from technical support”.
The document contains a C-interface specially tailored to the plant configuration of
SIMATIC BATCH.
With this interface, you can write user-specific applications.
Options for accessing the documentation related to SIMATIC BATCH and SIMATIC PCS 7
You can conveniently access all of the documentation for SIMATIC PCS 7 on the PCS 7 web
page www.siemens.com/pcs7-documentation (http://www.automation.siemens.com/mcms/
Additional helpful documents, FAQs, applications, and tools can be found on the Siemens
Industry Online Support page at http://support.automation.siemens.com (http://
support.automation.siemens.com).
My Documentation Manager (http://support.automation.siemens.com/WW/view/en/
38715968) gives you the option of compiling specific documentation contents into your own
manual.
SIMATIC BATCH V8.2
28Operating Manual, 02/2016, A5E35958174-AA
Page 29
Security information
Siemens provides products and solutions with industrial security functions that support the
secure operation of plants, solutions, machines, equipment and/or networks. They are
important components in a holistic industrial security concept. With this in mind, Siemens’
products and solutions undergo continuous development. Siemens recommends strongly that
you regularly check for product updates.
For the secure operation of Siemens products and solutions, it is necessary to take suitable
preventive action (e.g. cell protection concept) and integrate each component into a holistic,
state-of-the-art industrial security concept. Third-party products that may be in use should also
be considered. You can find more information about industrial security under: http://
www.siemens.com/industrialsecurity
To stay informed about product updates as they occur, sign up for a product-specific
newsletter. You can find additional information on this at: http://
support.automation.siemens.com.
SIMATIC BATCH is a SIMATIC PCS 7 program package with which discontinuous processes,
known as batch processes, can be configured, planned, controlled and logged.
Simple batch processes with configurable sequential control systems are automated with the
CFC and SFC tools included in the PCS 7 Engineering System. When you have more complex
requirement of a recipe control strategy, you use SIMATIC BATCH. With SIMATIC BATCH,
recipe structures are designed, modified and started graphically on an operator station or on
a separate PC.
All process and operator data can be collected for a specific batch during batch execution and
can then be processed and printed out in a batch report.
Possible applications of SIMATIC BATCH
SIMATIC BATCH is suitable for batch processes of any complexity. It provides simple support
for batch applications ranging from small to extremely large.
3
The outstanding features of SIMATIC BATCH are as follows:
● Simple, graphic recipe creation
● Control and monitoring of recipe execution with the same graphic representation as used
in recipe creation
● Two modes for working through the recipe logic, PC-based and AS-based
● Control strategy with data from multiple programmable logic controllers
● Integrated permission management with detailed access permissions
● Integrated logging of all events (including manual intervention) for comprehensive
production documentation
● Simple and clear batch planning, when required with interfacing to higher-level PPS systems
SIMATIC BATCH supports you throughout all the stages involved in the automation of batch
processes. The functions provided by SIMATIC BATCH can be divided into four basic areas:
● Recipe system:
Creation and management of any number of master recipes and library operations
● Batch planning:
Planning and replanning of batches and production orders
● Batch control:
Execution, visualization and control of batches released for production and the
corresponding control recipes as well as visualization of the current unit allocation
● Batch data management:
Acquisition, storage and report creation of batch data
3.3Components of SIMATIC BATCH
3.3.1BATCH interface blocks
Introduction
SIMATIC BATCH uses the new functionality of the SFC types in the engineering system to
define operation and phase types. As an alternative, SIMATIC BATCH continues to provide
special interface blocks as the communications interface to the processing programs on the
automation system. These blocks known as BATCH interface blocks ship with SIMATIC
BATCH as a block library.
Additional information: "Setting up the equipment module with interface blocks IEPH and
IEOP (Page 151)"
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.
SIMATIC BATCH V8.2
32Operating Manual, 02/2016, A5E35958174-AA
Page 33
Functions
Product introduction and installation
3.3 Components of SIMATIC BATCH
Using the BATCH interface blocks along with SIMATIC BATCH, makes the following functions
available:
● Controlling the running of the process:
The IEPH/IEOP blocks are used for this purpose. These provide the commands (for
example start or 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.
● Allocating or releasing a unit by a control recipe:
The UNIT_PLC block is used for this purpose.
● You use the TAG_COLL blocks to collect process values to create transition conditions and
for logging measured value sequences in the batch report.
● Transferring setpoints and process values:
The IEPAR blocks are used for this purpose. The batch control writes the recipe parameters
(setpoints) for the processing blocks to these blocks via the IEPH/IEOP blocks. The
processing blocks write the result data (process values) to the IEPAR blocks so that they
can be stored as batch data by the batch control once again using the IEPH/IEOP blocks.
The BATCH configuration dialog is opened in the SIMATIC Manager using the Options >
SIMATIC BATCH menu. As an alternative, you can also open it using the "SIMATIC BATCH"
shortcut menu of any object in the SIMATIC Manager.
Functions in the BATCH configuration dialog
In the BATCH configuration dialog, the following tasks are performed after you have created
the basic automation (SFC / CFC) in the SIMATIC Manager:
● Updating, compiling and downloading the S7 program (objects)
● Updating, compiling and downloading stations (SIMATIC station, for example SIMATIC
S7-400)
– CPU for example 417-4, specifying the memory configuration and assignment for the
recipe logic
– Compiling and downloading the S7 program (charts) The CFC charts of the units
assigned to the S7 program are opened.
– Displaying, updating, compiling and downloading connections
SIMATIC BATCH V8.2
34Operating Manual, 02/2016, A5E35958174-AA
Page 35
● Batch process cell
– Validating the batch process cell
– Transferring messages of the batch process cell to the higher-level PCS 7 OS
– Downloading a batch process cell
● Generating, creating and deleting batch types
● Propagating batch types in a multiproject
● Compiling, creating and deleting batch instances.
● Merging batch instances in a multiproject
Additional information
BATCH engineering (Page 178)
3.3.3BATCH Launch Coordinator
Product introduction and installation
3.3 Components of SIMATIC BATCH
The BATCH Launch Coordinator is responsible for the following:
● Operator control and monitoring of SIMATIC BATCH
● Monitoring the BATCH server applications
The icon of the BATCH Launch Coordinator is displayed within the task bar. If you right-click
the icon, a shortcut menu opens in which commands are available for selection. Additional
information can be found in the first reference below.
Image 3-1BATCH Launch Coordinator shortcut menu
Startup characteristics
The BATCH Launch Coordinator can be started automatically or manually. For automatic start
after computer logon, the Batch process cell must be loaded and WinCC Runtime must be
activated.
If the BATCH Launch Coordinator is not started automatically, start it using the Start > All
Programs > Siemens Automation > SIMATIC > Batch > SIMATIC BATCH Launch
Coordinator command.
Starting the BatchCC
The BATCH Launch Coordinator creates the preconditions for starting BatchCC. BatchCC
cannot be connected to the database of the loaded batch process cell until SIMATIC BATCH
displays the status "running". BatchCC will display a corresponding information dialog on
startup until SIMATIC BATCH is ready.
Information on the BATCH Launch Coordinator (Page 243)
"System characteristics" tab (Page 946)
3.3.4BATCH 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 using the Launch Coordinator on the BATCH server or, in a redundant system, on
both BATCH servers.
BATCH Control Server tasks
The BATCH Control Server (BCS) performs a variety of detailed tasks. The most important
functions are the following:
● Establishing a communication connection to the automation system
● Generating the control recipe
● Downloading the control recipe to the automation system
● Processing the recipe synchronization
● Generating messages on the server status
● Controlling the redundancy mechanisms
● Failure monitoring (watchdog)
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).
Establishing a communication connection to the automation system
The BCS in conjunction with the communication channel (via S7 DOS) ensures the
communication with the process. It monitors the execution of the current batches.
In contrast to the PC-based concept, the AS-based concept has direct process access via the
communication channel.
Transferring step information and control recipe requests
The BCS transfers data to the AS via the S7 DOS communication channel. Commands and
parameters are sent to the automation system. The BCS receives status and process values.
SIMATIC BATCH V8.2
36Operating Manual, 02/2016, A5E35958174-AA
Page 37
Generating the control recipe
Once a batch has been started in the BatchCC or on the PCS 7 OS, the BCS allocates the
unit on the AS, generates the associated control recipe, and sends it to the AS.
Downloading the control recipe to the automation system
The complete control recipe for one unit is loaded in a permanently assigned data block on
the AS using S7 communication.
All of the step and recipe structure data is stored in the data block.
Processing the recipe synchronization
If a synchronization line is reached during execution of a control recipe, the automation system
sends a frame to the BCS. In addition to the batch ID, the frame also contains the
synchronization number that is unique within a recipe.
A signal is sent to the AS when all units involved in synchronization reach the synchronization
line. The batch execution is then resumed simultaneously in all units.
Product introduction and installation
3.3 Components of SIMATIC BATCH
Generating messages on the server status
The BATCH Control Server generates status messages for the BatchCC and the AS link. The
messages are stored along with the corresponding message numbers in PCS 7 Alarm Logging.
Generating the batch report
After a batch is started, the batch data is saved in the online data storage of SIMATIC BATCH.
In order to display and/or print out batch data, a print preview window and the batch report are
available.
Checking state of process cells in the event of a problem in the automation system
In the event of a problem in the AS (AS in STOP), the active automation functions go into error
mode. Depending on the setting under Properties > "AS operating parameters" tab under "SFC
start-up after CPU restart", the SFC / SFC type is automatically reset or retains its state.
Operator intervention is needed in both cases. We would only recommend a restart or
resumption of the function once the state of the process cells has been checked.
3.3.5BATCH CDV
Definition
BATCH CDV (batch data management) is a component of SIMATIC BATCH. It is a server
component responsible for acquisition, storage and reporting of batch data.
BATCH CDV does not have its own user interface. BATCH CDV is controlled as a server
application by the BATCH Launch Coordinator service. The status of the application is
displayed via the "BATCH Status" button in the shortcut menu of the BATCH Launch
Coordinator.
Functions
The “BATCH CDV” server handles the following three tasks:
● Collects and stores WinCC messages.
● Collects and stores WinCC measured values. Only the measured values configured in the
running batches are collected and stored.
● Closing batches. This process is divided into two steps. The transition state "Closing" leads
to the final state "Closed".
Saving measured value and message data
BATCH CDV was enhanced so that the collected measured value and message data can only
be written to the hard disk when sufficient disk space is available.
In addition, a batch can only take the "Closed" status when all batch-specific measured value
data have been collected and written to the hard disk.
Note
Batches can no longer be closed if there is not enough space on the hard disk.
Cause:
A batch can only take the "Closed" status after it has first taken the "Closing" status and all
batch-specific measured value and message data have been collected and written to the hard
disk. If there is not enough hard disk space, the collected measured value and message data
cannot be saved.
Remedy:
As soon as there is enough hard disk space, the pending measured value and message data
is written to the hard disk. If a batch has the "Closing" status at this point in time, it is
automatically closed after the pending measured value and message data has been saved.
3.3.6Batch Control Center (BatchCC)
Definition
The BATCH Control Center (BatchCC) is the central component in SIMATIC BATCH for batch
planning and batch control. The BATCH Control Center manages all the data relevant to
SIMATIC BATCH. This means all BatchCC data can also be displayed in reports.
The Batch Control Center is started on the BATCH servers according to the settings made in
the BATCH Launch Coordinator.
SIMATIC BATCH V8.2
38Operating Manual, 02/2016, A5E35958174-AA
Page 39
Product introduction and installation
3.3 Components of SIMATIC BATCH
Functions
With the BATCH Control Center, you can do the following:
● Read in the process cell data from the basic control
● Specify the user permissions for all functions of BATCH
● Define the names and codes of the materials used
● Manage master recipes and start the BATCH Recipe Editor to configure the recipe structure
● Manage libraries with recipe elements (library operations)
● Edit and manage the formula categories and corresponding formulas
● Plan production orders using master recipes and batches
The BATCH Recipe Editor (RE) 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 (ES) of SIMATIC PCS 7, for example, by ISA-88 type definition of the process cell,
units and equipment modules.
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).
SIMATIC BATCH V8.2
40Operating Manual, 02/2016, A5E35958174-AA
Page 41
● Display the master recipes and library operations in reports.
● Release master recipes and library operations for testing or for production.
● Validate recipes.
When performing these tasks, the familiar functions known from MS Windows programs such
as paste, cut, copy, undo and redo can be used on single or grouped objects.
3.3.8Assembling BATCH data in reports
Reports
Printed reports ensure the documentation of your batch processes. Reports for the following
objects are available with SIMATIC BATCH:
● BATCH process cell
● Libraries
● Master recipes
Product introduction and installation
3.3 Components of SIMATIC BATCH
● Formulas
● Batches
The standard report templates are provided for all types of reports. Report templates are used
for clear and structured visualization of the data. The shortcut menu of a selected object
contains the "Print" and "Print Preview" commands for objects. Commands for navigating,
viewing, printing, and exporting reports are included in a toolbar of the print preview window.
Additional information
Object reports (Page 477)
3.3.9BATCH OS controls
OLE custom controls (OCX) for SIMATIC BATCH
We provide you with SIMATIC BATCH OS controls for operating and monitoring batch
processes on a PCS 7 OS client. In a template screen that is available after installing SIMATIC
BATCH, you will find all the BATCH OS controls for operator control and monitoring of a Batch
process cell.
Graphical user interface on a PCS 7 OS
You can use the BATCH OS controls as a graphical user interface (GUI). They are configured
in the WinCC Graphics Designer for process mode. In process mode (WinCC Runtime), all
the necessary interventions for batch mode can be implemented from a PCS 7 OS using
BATCH OS controls.
3.4.1Introducing the operating modes "AS-based" and "PC-based"
New BATCH block for both operating modes
When you create the master recipes, you can specify whether or not they are processed ASbased or a PC-based for each recipe unit procedure (RUP). This is only possible if the new
block "UNIT_PLC" from supplied block library is configured in the relevant RUP.
What makes the AS-based operating mode possible?
The AS-based mode can only be implemented by using the new unit block "UNIT_PLC". With
the new AS-based mode, you can influence recipes being processed on the AS using the
UNIT_PLC block.
Note
Units with more than one AS
AS-based operation is not possible in units that have more than one AS on which the equipment
phases/operations are configured. In projects with such units, the AS-based operating mode
must be disabled in the BATCH configuration dialog (0% memory allocation).
Which functions are not supported in the AS-based operating mode?
● Flat recipes are not available.
● The "online structure changes (OSC)" from SIMATIC BATCH version 7.1 SP1 with which
structure changes could be made to the recipe logic during the running of a batch is not
possible in AS-based mode.
Memory requirements of the CPU and runtimes in AS-based mode
The following table provides an overview of the amount of CPU memory occupied by SIMATIC
BATCH blocks in the AS-based mode.
Memory allocationsDescriptionMemory required in KB
Static part. Occupied by system.Communication (Event Send)56
Function blocks60
Function calls41
SIMATIC BATCH V8.2
42Operating Manual, 02/2016, A5E35958174-AA
Page 43
Product introduction and installation
3.4 Operating modes in SIMATIC BATCH
Memory allocationsDescriptionMemory required in KB
Dynamic part. Occupied by settings in
the BATCH configuration dialog.
per unit57
per recipe unit procedure (RUP)128
The following table shows the runtimes of the most important recipe structures that result from
the processing of a recipe unit procedure and are required to calculate a cycle time.
Recipe structureAS runtime
Completing recipe phase (average measured value)1.8 ms
Updating setpoint (average measured value)0.07 ms
Processing a transition (average measured value)4 ms
Starting recipe phase (average measured value)1.9 ms
Processing a recipe phase (average measured value)2 ms
You can find an example of how to determine the memory requirements and the runtime in
the section "Measured results for calculating the performance of both operating modes
(Page 71)".
3.4.2Concept expansion
Reason for expansion of the concept
Continuously increasing demands for higher product quality while simultaneously maintaining
full plant capacity have caused a variety of branches in the manufacturing industry to improve
and optimize their batch processes again and again.
For example, the food and beverage industry thus expect deterministic and above all fast step
change times from a batch control system because slow step changes can result in a reduction
in product output.
Requirements for fast batch processes
The determining logic of step changes is a basic requirement for both fast and parallel process
sequences, which need to be synchronized to specific steps. Fast process sequences, for
example, enable configuration of exact deceleration points for dosing, while precise parallel
sequences accelerate the material transfer to synchronization steps.
The following requirements must be met to obtain the needed fast batch processes:
● Clear reduction of the step change times to less than one second
● Clearly defined deterministics for the step change times for batch processing
When compared with previous versions of SIMATIC BATCH, this version allows faster batch
control. The following features characterize SIMATIC BATCH in AS-based mode:
● Shifting of the recipe logic to the automation system (BATCH block UNIT_PLC)
● Reduction of the communication paths and communication traffic
● Shorter reaction times
● SFC time optimization due to event-driven calls
Compatibility with SIMATIC PCS 7 and SIMATIC BATCH
The proven functionalities, such as engineering, convenient recipe management, and operator
control and monitoring of the process, remain available. Added to this are the deterministic
algorithm and the performance at step changes while the runtime system on the AS is activated.
Hierarchical recipes are created in three levels: RUP, ROP, and RPH. These recipes are
executed in the automation system as batches. Either the BATCH Control Center or the
BATCH OS controls are used for operator control and monitoring of recipes.
Online functionalities, such as creating and starting batches, are available not only in BatchCC
but also with the new BATCH OS controls on a PCS 7 OS.
Offline and project functions, such as "Updating process cell", "Permission management",
"Role management", and the creation of materials, formulas, and formula categories continue
to be used exclusively in BatchCC.
Recipes for AS-based operation continue to be created with the Recipe Editor of SIMATIC
BATCH and their use is checked there. For recipes that have parts executed on the AS,
additional constraints were included in the validation. There is a check to determine whether
free memory blocks are available on the AS to execute selected recipe parts during runtime.
Use of existing recipes
With suitable system knowledge, existing hierarchical recipes from previous versions of
SIMATIC BATCH can be reconfigured for AS-based operation.
3.4.3Shifting of the recipe logic to the AS
Acceleration of recipe execution steps
An essential measure for accelerating recipe execution steps is the shifting of the recipe logic
from the BATCH control server to the automation system. It results in substantially faster as
well as deterministic step change times.
In comparison to a server, the automation system operates deterministically because the
individual cycles of organization blocks are controlled in it. On the server, in contrast, the
execution times of the cycles can vary depending on the load of the CPU.
Moving the recipe logic also results in changes to the system architecture. As can be seen in
the figure "Shifting the recipe logic", the BATCH control server is connected to the AS via a
SIMATIC BATCH V8.2
44Operating Manual, 02/2016, A5E35958174-AA
Page 45
Product introduction and installation
3.4 Operating modes in SIMATIC BATCH
separate communication channel (S7DOS). The result is shorter and simplified communication
paths.
Communication path between BATCH control server and automation system
The new concept in AS-based mode uses a direct communication channel for faster and more
stable data exchange between the BATCH control server and the automation system. This
channel is based on S7 DOS and allows the BATCH control server direct access to the process.
The communication channel has the following tasks:
● Downloading blocks with the control recipe for the sequence of a unit
● Sending control commands to the recipe control
● Transferring step data from the automation system to the BATCH control server
● Transferring setpoint values, process values and measured values from the automation
system to the BATCH control server
The communication connections between AS and BCS are created automatically by the
BATCH configuration dialog.
Data communication between the server and automation system
The following figure, "Reducing the communication volume" shows how the individual software
components were changed to reduce the volume of communication.
Impact on the processing time and memory of the AS
The greater the number of currently active unit recipes on the AS, the less memory space or
processing time is available for the remaining automation tasks on the AS.
Image 3-2Shifting the recipe logic
Operator control of the process on a PCS 7 OS using BATCH OS controls
Which recipe phases continue to be processed in the BATCH control server?
46Operating Manual, 02/2016, A5E35958174-AA
To create and operate batches including visualization of the control recipes of currently running
batches, SIMATIC BATCH provides a template screen on a PCS 7 OS with all the necessary
BATCH OS controls.
The following list shows all recipe phases that are still processed in the BATCH control server
in AS-based mode:
● Unit allocation (preferred unit, the longest out of use, operator selection and process
parameters)
● Synchronization lines between two units
SIMATIC BATCH V8.2
Page 47
● Cross-unit transitions and command steps
● Operator instructions
Additional information
Obtaining the memory configuration and setting the allocation (Page 198)
BATCH OS controls (Page 585)
3.4.4Recipe levels and sequence of a recipe
Recipe levels and recipe logic
In AS-based mode, SIMATIC BATCH allows a reduction and a reproducibility of step change
times with the following recipe control runtime functions that have been shifted to the
automation system:
● Unit/RUP level
Product introduction and installation
3.4 Operating modes in SIMATIC BATCH
Recipe execution
● Recipe level 1/ROP level
● Recipe level 2/RPH level
● Logic of the individual control units
Recipe level 2 / RPH level contains the recipe logic and its accelerated execution via the SFC
type or SFC chart.
The logic of the individual control units describes the user configuration on the AS.
The system blocks required for recipe control and the runtime system are grouped together in
the SIMATIC BATCH blocks library.
The mapping of the recipe execution in the AS is made with the following block classes:
1. RUP level -> UNIT_PLC block
2. ROP level -> EOP block (level 1)
3. RPH level -> EPH block (level 2)
Recipes in the automation systems are assigned to the units as control recipes. This property
allows the distribution of a project over several automation systems.
If communication with the SIMATIC BATCH control server is interrupted, the AS continues to
run to the next synchronization line in the recipe or to a reference (transition or command block)
to another unit recipe. Events are temporarily stored on a unit-specific basis until the configured
communication buffers are full.
The volume of data that may be put into interim storage depends on the corresponding volume
of batch communication.
The complete controller information required to execute a batch in the automation system is
called the control recipe. This information is distributed over units and loaded into the
automation system by the BATCH control server. Each unit is assigned one or more data
blocks for storage of unit recipes.
Control recipe request from the AS
A control recipe is requested by the AS. The unit recipe procedure is then generated in the
BATCH control server and loaded into the data block for the UNIT block.
The start of a unit is initiated by:
● The order system (BatchCC) on the BATCH control server
● The SIMATIC BATCH OS controls on the PCS 7 OS
Recipe synchronization
Recipe synchronizations are loaded in the AS with the control recipe. When a recipe
synchronization line is reached during the control of a unit, the the following individual actions
occur:
● The AS sends a frame to the recipe synchronization in the BATCH control server. In addition
to the batch ID, the frame also contains the synchronization number that is unique within
a recipe.
● The BATCH control server determines the participants of the synchronization with the first
frame. The synchronization definition is read for the recipe for this purpose. The definition
includes the recipe unit procedures (RUPs) involved in the synchronization.
● The BATCH control server determines the unit candidates for this batch. The candidate
information includes which unit is selected for this RUP in the current batch.
● If the conditions of a synchronization are met, the BATCH control server will set an
"acknowledgment bit". The acknowledgment bit is set in the AS for each participating unit.
● The execution in all units is then simultaneously resumed in the AS.
3.5Possible configurations
3.5.1System software architecture
System and software architecture.
The following figure shows the hardware components involved in the system (colored gray)
that are interconnected via bus systems (colored brown) Software program packages or parts
of software program packages (colored white) of SIMATIC BATCH are shown for each
SIMATIC BATCH V8.2
48Operating Manual, 02/2016, A5E35958174-AA
Page 49
6,0$7,&%$7&+
GDWDEDVH
6,0$7,&
6
6,0$7,&
6
6,0$7,&%$7&+
$6EDVHGSURFHVVLQJRI
WKHFRQWUROUHFLSH
5HFLSHSKDVHORJLF
6)&W\SHRU,(3+
EORFN
6LJQDOPRGXOH
6,0$7,&
6
3URFHGXUDO
FRQWUROPRGHO
(40ILOH
6,0$7,&%$7&+
FOLHQW
6,0$7,&%$7&+
DGYDQFHGUHSRUW
%$7&+&RQWURO&HQWHU%DWFK&&
5HGXQGDQW6,0$7,&%$7&+VHUYHU
%$7&+
&RQWUROVHUYHU
$6EDVHGPRGH
6,0$7,&%$7&+
&OLHQW
6,0$7,&0DQDJHU
(QJLQHHULQJVWDWLRQ(6
6,0$7,&%$7&+
&RQILJXUDWLRQGLDORJ
6,0$7,&%$7&+
%ORFNV
6,0$7,&%$7&+
&OLHQW
$6FRPPXQLFDWLRQ
5HFLSHFRQYHUWHU
3&EDVHGPRGH
3&626FOLHQW
%$7&+26FRQWUROV2&;
%$7&+UHFLSHHGLWRU5(
9LVXDOL]HEDWFKHV
&UHDWHEDWFKHV
&RQWUROEDWFKHV
6,0$7,&%$7&+
VHUYHU
3&626
VHUYHU
$6FRPP
3ODQWEXV
7HUPLQDOEXV
Product introduction and installation
3.5 Possible configurations
hardware component involved in the process. Blue lines with directional arrows roughly show
the interaction of the components of the software packages.
Installation of the program packages for an ES and the
installation of all other program packages on a sepa‐
rate PC.
Example: OS server, OS client, BATCH server,
BATCH client, RC server, RC client.
All program packages are installed on different PCs
The following program packages can be installed on
different PCs.
Example: Single PC as ES, single PC as BATCH serv‐
er, single PC as OS server, single PC as RC server,
single PC as BATCH client, OS client and RC client,
Process connection to AS from this PC.
Limited performance, engineering and
process mode not separate. For exam‐
ple for small process cells or when work‐
ing with Getting Started.
Process connection to the AS from the
ES and the separate PC. Better per‐
formance. Engineering and process
mode separated. Industrial system.
Process connection to AS from the ES,
from BATCH server and OS server.
Best performance in conjunction with a
fast network. Engineering and process
mode separated. Industrial system.
Data storage systems
SIMATIC BATCH operates with the following three databases:
● Project DB: Storage of user permissions
● Offline DB: Storage of recipes, formulas, materials
● Online DB: Storage of the batches
During installation, the BATCH databases or BATCH shared folder with the databases are
created in the specified location on your hard disk or in a new folder path.
BATCH server
When you install the BATCH server program package on a PC, the following BATCH
applications are installed:
● BATCH control server (BCS)
● Batch data management (CDV)
● SIMATIC BATCH Server (SBS)
● BATCH databases
● BATCH Launch Coordinator
SIMATIC BATCH V8.2
50Operating Manual, 02/2016, A5E35958174-AA
Page 51
BATCH clients
When you install the BATCH client program package on a PC, the following BATCH
applications are installed:
● Batch Control Center (BatchCC / BCC)
● BATCH Recipe Editor (RE)
● BATCH OS controls
● API interface
Additional information
You will find a detailed description of the possible distribution of the SIMATIC BATCH program
packages in the manual
Process Control System PCS 7; PC Configuration and Authorizations
3.5.3Client / server architecture of SIMATIC BATCH
Product introduction and installation
3.5 Possible configurations
Client/server architecture
The SIMATIC BATCH software package is normally installed on more than one PC. PCs are
set up as BATCH clients are always at least one PC as BATCH server. All the BATCH stations
involved work with the same process cell project. The BATCH server provides the services for
the BATCH clients that form the interface to the operator, in other words function as operator
control terminals.
PC-based mode: Interaction with PCS 7 OS server
In process mode (runtime), SIMATIC BATCH is linked to the PCS 7 OS servers.
The communication with the automation system, for example write recipe parameters or read
process values, is via the data manager of the PCS 7 OS server. In other words, a BATCH
server does not need its own interface to the automation system for the PC-based mode.
The "BATCH server" and "OS Server" program packages should, whenever possible, be
installed on separate PCs to improve performance. In the batch process cell configuration, the
PCS 7 OS servers that are relevant for the batches are made known to the BATCH server.
BATCH clients can run on a separate PC as well as together with an OS client on a PC. The
PC configuration of this mode is shown in the following figure.
AS-based mode: Interaction with the automation system
In contrast to the PC-based mode, a BATCH server in the AS-based mode requires a network
connection to both the terminal and plant bus. This ensures direct communication between
the BATCH server and the AS via a separate communication channel. Via this channel, the
control recipes on the automation system are accessed while the runtime system is operating.
To accelerate a step change, for example, switch to next signals are set in the control recipe
and therefore in the automation system.
SIMATIC BATCH V8.2
52Operating Manual, 02/2016, A5E35958174-AA
Page 53
Product introduction and installation
3.5 Possible configurations
multiple station system (distributed system)
SIMATIC BATCH supports the model of multiple station systems or distributed systems. This
means that you can install the software program package relevant to the application on every
PC of a multiple station system. You can, for example, configure your project in such a way
that all stations involved including the AS can be accessed from an engineering station.
Simple multiple station system (distributed system with a PCS 7 OS as BATCH server and OS
server)
The configuration described up to now applies to a multiple station system or distributed
system. For small projects, there may be only one PCS 7 OS. In this case, the BATCH server
and the OS server are installed on this PCS 7 OS. This PC must have the process connection
to the AS. The ES is installed on a separate PC. This provides a network connection to the
terminal and plant bus and therefore to BATCH clients and the AS.
Configuration on an engineering station
BATCH servers, BATCH clients and OS servers and OS clients are configured in the SIMATIC
Manager of the Engineering Station and downloaded from there to the target stations.
Maximum number of BATCH clients
A maximum of 32 BATCH clients can be connected to one BATCH server.
3.5.4Interface to MES/ERP
With the
of SIMATIC BATCH to an OEM system or to any MES/ERP application. The API interface
offers a COM connection (data format XML).
To learn about the possible uses and configuring options, please refer to the associated online
help or manual. You will find the online help named "bfapicm_a.chm" in the following path "..
\SIEMENS\BATCH\Api_Example\BFApi\_doc". Double-click on the file to open the online help.
The manual can be opened as a PDF file under Start > All Programs > Siemens Automation
> SIMATIC > Documentation > English > SIMATIC BATCH - COM API.
SIMATIC BATCH - COM API
interface, you can link the online and offline functions
To increase the availability of the batch control and to allow a software update during operation,
SIMATIC BATCH provides the option of installing a redundant BATCH server. If there is a
failure in the redundant system, there is a standby/master failover between the redundant
BATCH servers.
Redundancy is achieved with redundant BATCH servers each with local data management.
To safeguard data and to allow the batch applications to access the current data, the data is
constantly synchronized between the two local data management systems - a data replication.
This ensures that after the failure of one BATCH Control Server or database server, the
redundant server can continue to work with the same data without the loss of data or gaps in
the documentation.
Configuring and commissioning
Note
Requirements
To establish the software and hardware requirements and when configuring and
commissioning redundant servers in the SIMATIC PCS 7 system, you should always consult
your Siemens representative.
References for redundant PCS 7 OS
An introduction to the general redundancy mechanisms is provided in the function manual
Process Control System PCS 7; Fault-tolerant Process Control Systems
is on the "PCS 7; Electronic Manuals" CD. This is general documentation describing the overall
concept of availability in PCS 7. This also includes, for example, more information on the
redundant PCS 7 OS.
. This documentation
SIMATIC BATCH V8.2
54Operating Manual, 02/2016, A5E35958174-AA
Page 55
3.5.5.2Example configuration - Fault-tolerant Batch Control
6,0$7,&%$7&+
%$7&+6HUYHU
%$7&+&RQWU6HUYHU
'%6HUYHU
6,0$7,&%$7&+
%$7&+6HUYHU
%$7&+&RQWU6HUYHU
'%6HUYHU
%$7&+&OLHQW
3&626
26&OLHQW
%$7&+&OLHQW
7HUPLQDOEXV
3&626
266HUYHU
3&626
266HUYHU
UHGXQGDQW
(QJLQHHULQJ
6WDWLRQ
3URFHVVEXV
6,0$7,&6
6,0$7,&6
The figure below shows an example configuration with a redundant BATCH server and
redundant PCS 7 OS (WinCC):
Product introduction and installation
3.5 Possible configurations
(1) Redundant BATCH server
(2) OS redundancy of the standard PCS 7 operator stations
Redundancy is achieved with two BATCH servers with a standby/master failover. The
redundancy of the BATCH servers ensures the following if a BATCH server fails:
● All BATCH clients (with the BATCH Recipe Editor and BatchCC (batch planning, batch
control)) are immediately operable again following the failover and
● permanent acquisition of the Batch data continues.
The redundancy of the distributed PCS 7 operator stations with an interface to the SIMATIC
S7-400 is achieved by interconnected OS servers with data synchronization and backup of
the archive data. The WinCC archives of the redundant OS servers are synchronized and
contain the same data. The functionality is implemented with the "Redundancy" optional
software of WinCC. For a description of the "Redundancy" optional software, refer to the
manual
The redundancy of the PCS 7 operator stations ensures that the batch processes will continue
uninterrupted even if one of the two OS servers fails. The operator remains informed about
the status of the process cell and can still intervene in the process.
The BATCH Control Server and Batch data management (Batch CDV) are permanently active
on both redundant BATCH servers. From the prospective of the BATCH server, there is no
preferred server; in other words, both BATCH servers access the same OS server when there
are no failures in the system.
If the BATCH server configured as the master fails, there is a failover to the BATCH server
(standby). This then becomes the master.
Possible causes of a failover
● Failure of the BATCH server PC (master), e.g. hardware fault or "blue screen"
● Failure of the network connection of the BATCH server PC. The BATCH server no longer
detects a client or its redundant BATCH server.
● Failure of a BATCH server application, e.g. BATCH Control Server, batch data
management (CDV), SIMATIC BATCH Server (SBS).
Failover of the BATCH clients
If the BATCH server (master) fails, the BATCH clients automatically fail over to the standby
BATCH server.
Startup, hot restart of the BATCH clients
Note
Failover time
Following a failover of the BATCH servers, the BATCH clients can only be operated again after
a certain time has elapsed.
A message window opens informing you that the BATCH server is currently not obtainable.
The message window disappears after a successful failover. This indicates that the server
application is ready for operation again. If the redundant BATCH server is not ready to take
over, the message "BATCH server is in error state (postponed)" is displayed on the PCS 7
OS. When the redundant BATCH server becomes ready to take over, the redundant BATCH
server automatically takes over the server application.
As long as the message window is displayed, the BATCH client cannot be operated. You can,
however, close the client application by clicking the "Quit application" button. On completion
of the failover, the BATCH client can be started again.
Process control messages
In the event of a failover, a process control message is displayed on the message OS.
SIMATIC BATCH V8.2
56Operating Manual, 02/2016, A5E35958174-AA
Page 57
Product introduction and installation
3.5 Possible configurations
3.5.5.4Data replication
Synchronizing databases
Each redundant BATCH server of a server pair (master, standby) has its own local database.
To continually synchronize the two local databases, an independent second network adapter
is used for each of the two server PCs. The following tasks are performed via this connection:
● Lifebeat monitoring of the redundant partners
● Data replication
● Data consistency between the redundant partners
This ensures that both BATCH server always use the same database.
Redundancy switchover, start sequence of the BATCH servers, database synchronization with WinCC
message
● An interruption of the replication connection (extra network adapter in both redundant
SIMATIC BATCH server PCs with network cable) affects the communication between the
AS and the BATCH server. The communication is blocked for approximately 20 s. This
means that the process (batch) continues running but its visualization in the BATCH Control
Center or in the BATCH OS controls is updated after a delay of up to 20 s.
● When starting a redundant BATCH server or during a redundancy switchover, the
databases of the standby server are synchronized with the databases of the master server.
Do not abort the copy procedure needed for this, e.g. by powering down/switching off one
of the BATCH servers. If you do, you will have to reset the BATCH database of the standby
server.
● A "Restart dialog" appears on the previous master once a switchover to a redundant pair
of servers caused by an error has occurred. Please follow the restart request to correctly
restart the PC. All active programs are closed when you acknowledge the restart request.
● If you power down both BATCH servers on a redundant system with a time lag, when
restarting the BATCH server you will have to firstly restart the server you powered down
last. If you don't do this, there is a risk of you losing batch measurements and messages
from the period of the time lag.
● When starting and ending database synchronization between the master and standby
servers, the WinCC messages "Data synchronization started" and "Data synchronization
complete" are produced.
Hardware requirements
● Redundant BATCH servers always require an additional network adapter independent from
the terminal and plant bus. These network adapters can be of the same type.
● The additional network adapters must be installed in your PCs (redundant BATCH server
pair) in free PCI slots.
● Make sure that you read the information in the relevant SIMATIC PCS 7 documents,
especially the document
58Operating Manual, 02/2016, A5E35958174-AA
PCS 7 - PC Configuration and Authorization
.
SIMATIC BATCH V8.2
Page 59
Software requirements
● Installation of SIMATIC PCS 7
● Batch data replication is performed exclusively via an independent, additional network
adapter in both PCs.
● The network adapters are configured within the operating system (IP addresses and subnet
mask).
– Subnet mask: The network adapter for the data replication must not be in the same
– The addresses (IP and subnet mask) of the two PCs must be in the same network,
Configuration
The network configuration of the independent network adapter for a redundant BATCH system
is project-independent. It is performed in the "Simatic Shell" system folder in Windows Explorer.
1. Right-click on the "Simatic Shell" folder and select the shortcut menu command
"Redundancy Settings ...".
Product introduction and installation
3.5 Possible configurations
subnet as the network adapter for the communication with the BATCH clients via the
terminal bus/with the AS via the plant bus.
otherwise no communication is possible between the redundancy partners.
Result
2. In the "Serial Interface" area, select "none, or the following symbol "-------------".
3. In the "Network adapter" area, select the adapter that has been configured and is now
available.
4. Close the dialog with "OK".
5. Open the "Network connections" dialog. Open the "Advanced Settings" dialog with the
menu command Advanced > Advanced Settings. Use the buttons in this dialog to set your
connections in the correct order. First configure the "Terminal bus" and "Plant bus"
connection and then the "Batch replication connection".
Note
Check that a log is not selected in the adapter settings for the plant bus (file and print
sharing).
6. Repeat steps 1-5 for the redundancy partner.
You have now configured the required communication for the redundancy partners and can
no perform database replication for SIMATIC BATCH.
3.5.5.5Configuration of the redundant BATCH server
Configuration of applications on objects
WARNING
Computer names
Configuring applications (WinCC, SIMATIC BATCH, ...) on separate "SIMATIC PC station"
objects and then merging them to create one PC station by assigning the same computer
name to the "SIMATIC PC station" objects is not permitted.
Follow the steps in the SIMATIC Manager outlined below:
1. Select the project in the Component view.
2. Select the menu command Insert > Station > SIMATIC PC Station.
Result: A new SIMATIC PC station is inserted in the current project.
SIMATIC BATCH V8.2
60Operating Manual, 02/2016, A5E35958174-AA
Page 61
Product introduction and installation
3.5 Possible configurations
3. Set the computer name of the PC station.
– To do this, select the SIMATIC PC station.
– Select the menu command Edit > Object properties.
– Enter the computer name in the last field.
4. Configure this SIMATIC PC station in HW Config.
– To do this, select the SIMATIC PC station.
– Select the menu command Edit > Open object.
Result: HW Config opens.
– Insert a batch application from the hardware catalog:
Path in the hardware catalog: Standard > SIMATIC PC-Station > BATCH > BATCH
application (stby).
Select the menu command Station > Save and compile.
The inserted "BATCH application (stby)" object appears in the Component view below the
SIMATIC PC station.
3.5.5.6Information on network connections
Requirements:
The following are requirements for network adapter, serial connection and redundancy
connection:
● A redundant BATCH server must have a second network connection independent of the
terminal bus and plant bus. This is used for BATCH data replication.
● The serial connection (COM interface) may no longer be used in conjunction with SIMATIC
BATCH. It must be removed from "old systems".
● In principle, the redundant connection between both BATCH servers can be produced using
a crossed network cable (cross over cable) or a switch.
3.5.5.7Configuring network connections
Introduction
Network configuration of a redundant batch system is not dependent on the project. There is
therefore no need for configuration of batch redundancy in batch engineering, as was
previously undertaken in the project settings in the BATCH configuration dialog.
Procedure
1. Network configuration for the redundant BATCH server is undertaken via the "Simatic Shell"
folder in Windows Explorer. You will find more information in the online help for SIMATIC
BATCH in the Redundancy > Data replication section.
2. If you are installing BATCH and WinCC servers on a PC, ensure that you use the following
settings in the "Redundancy" WinCC Editor:
– Connection to redundant partner via serial interface: Select "none".
– Connection to redundant partner via network adapter (MAC address): Select the network
adapter you used for data replication and close the dialog using the "OK" button.
SIMATIC BATCH V8.2
62Operating Manual, 02/2016, A5E35958174-AA
Page 63
3.5.5.8Important additional information
Redundant server pair
● In a compact system (WinCC server and batch server on same PCs), the "Start SIMATIC
BATCH automatically after starting WinCC" setting should only be made once the BATCH
process cell (database) has been created. If this is not done, booting the system will be
interrupted with an error under the precondition "Just one server switched on, no client
started, BATCH process cell still not created".
● In a distributed system (WinCC server and batch server on different PCs), the "Start
SIMATIC BATCH automatically after starting WinCC" setting is blocked.
● When starting a redundant BATCH server or during a redundancy switchover, the
databases of the standby server are synchronized with the databases of the master server.
Do not abort the copy procedure needed for this, e.g. by powering down/switching off one
of the BATCH servers. Otherwise, the database of the standby server will have to be reset.
● If a redundancy failover occurs during active client applications, e.g., during actions such
as archiving of batches, reading in of process cell data, starting a print preview or a print,
the current actions may be adversely affected.
Product introduction and installation
3.5 Possible configurations
● A "Restart dialog" appears on the previous master once a switchover to a redundant pair
of servers caused by an error has occurred. Please follow the restart request to correctly
restart the PC. You should first close active programs.
● Both when starting and ending database synchronization between master and standby, the
WinCC messages "Data synchronization started" and "Data synchronization complete" are
produced.
● Batch data management There are no longer any restrictions for the start order of the
BATCH server in a redundant system. The system automatically connects to the valid
project database. You should, however note that following any total system failure in a
distributed system, the servers must be started up in the following order. First start the
WinCC server and wait until its redundant WinCC server is synchronized. Start the BATCH
server only when this completed.
Downloading the BATCH process cell data
When loading the BATCH process cell data from the BATCH configuration dialog, both the
BATCH server (master and standby) and all BATCH clients defined in the project are supplied
with data. However, this data is not valid in the BATCH system immediately after downloading,
but rather not until a defined point in time when this data is applied by the BATCH system.
Data is applied through the following actions:
● The distribution of the components and the BATCH server configuration, e.g. CDV on/off,
are applied during startup of the BATCH server PC (master and standby).
● The BATCH process cell data is applied in the BCC through the active user action "Update
process cell".
In the case of a redundant system, the BATCH process cell data is not automatically
synchronized on the redundant BATCH server when just one BATCH server PC is started up.
This means that when you restart a BATCH server, it is imperative that you also restart its
redundant BATCH server. Inconsistent BATCH process cell data between redundant partners
could lead to the following situations, for example:
● Messages and measured values are recorded on the master (CDV on) but not on its standby
(CDV off).
● Communication between the redundant BATCH servers may be faulty.
● Errors may occur in the recording of messages and measured values by the PCS 7 OS.
● Completely different BATCH process cells may be present on the two BATCH servers
because the databases are not synchronized.
Additional information
BATCH engineering (Page 178)
3.5.5.9Automatic hot restart
What safety strategies are there when using redundancy?
A redundant server pair provides protection for your process against failure. New mechanisms
are available to ensure that there is a failover and hot restart if a problem occurs.
● Prevention on exiting a SIMATIC server application with redundancy
● Automatic hot restart of server applications after problem; cannot be recognized by the user
● Isolation of SIMATIC BATCH server in an error state
● Isolation of the server applications in an error state
● Automatic hot restart of a SIMATIC BATCH server after status check of the partner server
Prevention on exiting a SIMATIC server application
If you want to exit a SIMATIC server application (WinCC server, BATCH server, Route Control
server) for whatever reason, you must make sure that the partner server is fully capable of
taking over. In other words, all the applications running on the server must also run on the
partner server and be ready for operation.
If the result of the application check is negative, a warning dialog is displayed when you exit
a server application informing you that the partner server is not fully capable of taking over
and you will be asked whether you really want a redundancy changeover to the partner server.
If you click "Yes", the server application will be exited even though the partner server is not
ready to take over.
If you click "No", the dialog will be closed without any action being taken.
Automatic hot restart of SIMATIC server application
An automatic hot restart does not require any operator control. The process runs in the
background. The BATCH server applications can be restarted automatically when a problem
occurred. This does not affect redundancy.
SIMATIC BATCH V8.2
64Operating Manual, 02/2016, A5E35958174-AA
Page 65
Product introduction and installation
3.5 Possible configurations
The aim is to keep running in process mode at all times. If a SIMATIC server application
changes to the error state and needs to be exited, make sure that it is restarted automatically.
The following requirements must be met before SIMATIC server applications will restart
automatically:
● Requirements for installation: As of these versions, the restart mechanisms are included
in the software packages to be installed.
– SIMATIC PCS 7 V6.1 SP4 or higher
– SIMATIC BATCH V6.1 SP3 HF18
● Requirements for configuration:
– Automatic hot restart and isolation of the SIMATIC BATCH server are only supported
in a redundant configuration.
– All the mechanisms are available for the following redundant environments: Redundant
WinCC server, redundant BATCH server, redundant Process Historian, redundant
maintenance server and redundant Route Control server.
● Requirements in the operating system and project settings:
– WinCC Autostart must be configured so that the next time the PC is started up, the
corresponding project is opened and activated in the WinCC Explorer. The "AutoStart
configuration" dialog is available from the Start menu with Start > SIMATIC > WinCC >
Autostart.
– In the BATCH Launch Coordinator, one of the two options "Start SIMATIC BATCH
automatically after starting WinCC" or "Start SIMATIC BATCH automatically,
independent of WinCC" must be activated.
– If you also use SIMATIC Route Control, turn on the automatic activation in the shortcut
menu of the Route Control server.
An automatic hot restart following a server application error, can run as follows:
● Initial situation: Server and partner server are ready for operation
● Error on the server
● Partner server becomes master
● The dialog for a restart is ready to start on the server.
● All network connections (terminal bus, plant bus, crossover connection) are terminated.
The network adapters of this terminal bus and crossover connection are disabled. The
server is isolated.
● After a dynamic time dependent on the system, the server automatically acknowledges the
restart request with "OK" and is restarted.
● Once the server returns, the databases of the partner server and server are synchronized.
3.5.5.10Failure behavior of the BATCH server in AS-based mode
Failure of the BATCH server
In AS-based mode, batches are processed in the CPU. If the BATCH server fails, any batches
that have started are processed to the end if the BATCH server does not need to intervene in
the recipe execution, for example for synchronization or due to an operator dialog. Otherwise,
the individual units used in the control recipe continue to the next synchronization line and then
wait for communication with the BATCH server.
The situation still remains that if there is a sudden failure of the SIMATIC BATCH standby PC
(hardware defect, power failure, network connection to the database broken down), the BATCH
server can no longer store the AS frames in the database of the standby PC (redundant storage
for data backup/replication). The timeout time for recognizing the failure is set to 20 seconds
for technical reasons. If more frames are generated in the AS within these 20 seconds than
the internal AS buffer can store, the batches currently running on the AS change to the "Held"
status. This default setting can be changed for specific units in the AS.
Additional information is available in the manual SIMATIC BATCH Blocks V8.0 > Interface
blocks > BATCH interface blocks > UNIT_PLC > Command interface for influencing the entire
unit.
Temporarily storing events in the AS in the buffer memory
If the communication from the AS to the BATCH server breaks down or the server itself fails,
batch processing in the automation system continues until the next synchronization line or to
the end of the batch. This is also the response in a redundant scenario during the failover
phase and in the event of both BATCH servers failing. The corresponding events (the number
depends on the size of the AS memory) are stored temporarily in the AS until they are fetched
by the runtime component of the BATCH server.
When the buffer is full, the AS sends a message to the PCS 7 OS. You can use a parameter
on the UNIT_PLC block to specify whether the control recipe should continue to run or whether
the unit should switch to a previously defined state.
Additional information is available in the manual SIMATIC BATCH blocks V8.0> Interface
blocks > BATCH interface blocks > UNIT_PLC > Settings for communication monitoring and
for the communication buffer.
3.6Configuration limits
3.6.1Definition of configuration limits
Definition
The quantity structure in SIMATIC BATCH describes the quantitative load on the process
control system when executing batch processes. A distinction is made between the quantity
structure for AS-based and PC-based modes.
SIMATIC BATCH V8.2
66Operating Manual, 02/2016, A5E35958174-AA
Page 67
Product introduction and installation
3.6 Configuration limits
Based on the quantity structure, you can calculate the number of BATCH servers and the
number of automation systems for the planned process cell and select suitable dimensions for
them. The load can also be analyzed in advance. This is intended to reduce the automation
costs and to improve the quality, yield, safety, process cell utilization and productivity.
Quantity structure information can, however, only provide a rough guide for planning the
components of a process cell. For example, batches with a short duration (minutes up to a few
hours) with large numbers of setpoints put significantly more load on a SIMATIC BATCH server
(PC-based operation) or an automation system (AS-based operation) than batches with few
setpoints and a duration of several days.
One possible structure of a complex SIMATIC BATCH process cell is shown in the following
figure.
Image 3-3Process cell configuration
Operating batch process cells
The "Process cell configuration" figure shows that three batch process cells can exist
completely independently of each other on one common terminal and plant bus. Normally,
however, one batch process cell is adequate. A distribution over several batch process cells
is necessary only with very complex process engineering plants with an extremely large
quantity structure.
SIMATIC BATCH V8.2
68Operating Manual, 02/2016, A5E35958174-AA
Page 69
Redundant SIMATIC servers increase robustness and protect against failures. For the ASbased mode, a BATCH server pair must always have a network connection to the terminal
and to the plant bus.
The automation system (AS) is connected to the plant bus and communicates with the servers.
You run process control and process operation on clients.
Process cell design
Important characteristic values for the dimensions of your batch process cell are as follows:
● Number of automation systems per batch process cell
● Number of clients per batch process cell
● Number of servers per batch process cell
● Number of batch process cells in a process control system
● Here, you need to take the performance specifications of SIMATIC PCS 7 into account.
3.6.3Basics for calculating the performance of both operating modes
The data shown provides you with guide values that indicate which load states related to typical
data or basic data can be reached in your BATCH process cell both in PC-based and AS-based
mode and how you can select suitable dimensions for your process cell. This allows you to
estimate overload situations in advance and to include these in your planning.
The measured results are shown in the following section "Measured results for calculating the
performance of both modes".
Hardware and software basics
The following hardware and software was used:
● Automation system used CPU 417-4XT05-0AB0
● The PC used for the measurements is equipped with the hardware recommended by
SIMATIC PCS 7
● In PC-based mode, the blocks relevant to SIMATIC BATCH are installed in OB32 (1 second
cycle), recommendation from the section "Introduction" (Page 143)
Number of units50
Number of materials100
Number of qualities per material2
Recipe data
To calculate the performance data, a hierarchical recipe with the following characteristic data
is used.
Configured recipe data in the BATCH Control Center:
Number of RUPs per RP10
Number of ROPs per RUP10
Number of RPHs per ROP15
Number of RPHs in simultaneous branches5
Number of transitions per ROP15
Number of conditions per transition5
Number of header parameters per recipe / formula100 / 10
Number of parameters per RPH15
Number of parameters per control strategy10
Number of active RUPs per RP3
Number of process tags per RUP5
Number of process tags per ROP3
Number of configured electronic signatures (ESIG) in an RP3
Number of of active RPHs within a batch3
Batch data
Number of planned batches100
Number of batches per order100
Number of batches to be created simultaneously100
Number of released batches100
Number of batches to be released simultaneously100
Number of batches running simultaneously100
Number of of active RPHs within a batch3 PC-based
30 AS-based
Number of of active RPHs within a batch process cell30 PC-based
350 AS-based
Number of opened batches (control recipes) on all BATCH clients30
Number of batches to be completed simultaneously50
Number of batches to be archived simultaneously30
Number of batches to be deleted simultaneously30
Number of active BATCH clients (BATCH Control Center)5
SIMATIC BATCH V8.2
70Operating Manual, 02/2016, A5E35958174-AA
Page 71
Product introduction and installation
3.6 Configuration limits
Duration of the RPH10 min
Duration of the transition10 s
Acquisition cycle of the archive tags10 s
Execution of step changesimultaneous
3.6.4Measured results for calculating the performance of both operating modes
The measured values depend on the project, the equipment and load of the PC being used
and can differ from the times shown here. The times were calculated with the hardware
recommended by SIMATIC PCS 7.
Result, measured value (offline)
For the measured times, it is assumed that the step changes execute simultaneously and are
not processed with a time offset. Simultaneous step changes mean maximum load.
Acquired data:
ActionRuntime
Creating a recipe / library< 2 s
Deleting a recipe / library< 4 s
Creating a formula< 2 s
Deleting a formula< 2 s
Creating a material< 2 s
Deleting a material< 2 s
Releasing for testing / production< 90 s
Opening a recipe / library< 4 s
Checking a recipe for validity / releasing< 75 s
Creating an order< 2 s
Creating a batch< 20 s
Release batch< 75 s
Result, measured value (online)
When processing the basic recipe described, a PC equipped with a size of the SIMATIC
BATCH online database has a 30% processor load.
Definition of step change: A step change means that a recipe phase was completed, a transition
run through and the following recipe phase was started. This means that at least 3 recipe
objects are involved in a step change. In practice, however, there are often more than 3 recipe
objects involved, for example in simultaneous branches, alternative branches or when there
is synchronization. As an average value, approximately 5-7 recipe objects are assumed per
step change.
PAUSE command< 2 s
RESUME after PAUSE command< 2 s
Close batch5 to 10 min
Archive batch< 50 s
Change parameter< 3 s
Step change time4 s PC-based
Result of the AS runtimes for AS-based mode
The measured results shown in the following table serve as the basis for the calculations made
below.
Recipe structureAS runtime
Completing recipe phase (average measured value)1.8 ms
Updating setpoint (average measured value)0.07 ms
Processing a transition (average measured value)4 ms
Starting recipe phase (average measured value)1.9 ms
Processing a recipe phase (average measured value)2 ms
< 1 ms AS-based
These measured values result in a step change time of 8.4 ms (1.8 ms + 5 * 0.07 ms + 4 ms
+ 1.9 ms + 5 * 0.07 ms) for a recipe phase with 5 parameters. As a result, with, for example,
100 simultaneously active recipe phases and 32 simultaneous step changes, the recipe
processing time can be calculated as follows:
Recipe processing time = 32 * 8.4 ms + 100 * 2 ms = 469 ms.
This calculation does not, however, apply to parallel branches, alternative branches or when
there is synchronization since more than three recipe objects are then involved in a step
change. 32 simultaneous step changes with such constructs would lead to a loss of
performance.
A reduction in the number of simultaneous step changes increases the number of
simultaneously active recipe phases and vice versa.
To guarantee optimum performance in the automation systems, remember the following:
● The calculated total cycle time (times for communication, firmware, recipe processing and
user program) should always be shorter than the cycle time of the OB in which the
UNIT_PLC and the user blocks are installed.
● Take into account all the CPU requirements relating to the cycle time (you should also refer
to the documentation for the automation system S7-400 CPU Data).
SIMATIC BATCH V8.2
72Operating Manual, 02/2016, A5E35958174-AA
Page 73
Product introduction and installation
3.6 Configuration limits
Distributed over all the automation systems connected to the BCS, the BCS can:
● Have a brief peak load (max. 1 s) of up to 200 simultaneous step changes. In this case, a
maximum of 200 recipe phases that do not execute a step change can also be active. To
ensure that the BCS and AS continue to operate synchronized with each other following
such peak loads, you must ensure a recovery time of that least 60 s.
● Be run in continuous operation with not significantly more than 350 simultaneous, active
recipe phases. In this case, an average of 2 step changes may be active per second.
Result of the determination of memory requirements (data blocks) for AS-based mode
The following table shows the minimum memory requirements (data blocks) of the CPU for
AS-based mode.
Memory allocationsDescriptionMemory requirements in KB
Static part. Occupied by system.Communication (Event Send)56
Function blocks60
Function calls41
Dynamic part. Occupied by settings in
the BATCH configuration dialog.
per unit57
per recipe unit procedure (RUP)128
Based on the recipe data from the section "Basics for calculating the performance of both
modes", the actual memory requirements can be calculated as shown below.
Note
For this performance determination, the units must be configured within one automation
system and the recipe unit procedures must all be active at the same time.
Sample calculation (AS-based mode only)
Memory allocationsDescriptionMemory requirements in KB
Static part. Occupied by system.Communication (Event Send)56
Function blocks60
Function calls41
Dynamic part. Occupied by settings in
the BATCH configuration dialog.
Memory requirementsTotal in KB:2007
10 units570
10 simultaneously running recipe unit
procedures (RUP)
1280
Based on this calculation, it can be seen that the AS requires at least 2007 KB of memory for
the recipe logic. You set the memory required for the recipe logic as a percentage of the entire
work memory in the BATCH configuration dialog for the CPU.
To determine the amount of required memory for a CPU, you need to add the standard BATCH
blocks (SFC type, SFC, IEPH etc.) and the blocks for process control (drivers, actuators,
sensors etc.).
Typical performance data for the two operating modes
The following quantity structure for AS-based mode represents a complex process cell.
Requirement for the AS: A recipe of the size shown below can be downloaded to and processed
for the recipe logic assuming that the AS has a work memory capacity of 30 MB, 60% of which
is being utilized.
Result: The following table specifies from a SIMATIC BATCH perspective how the automation
system can be configured taking into account the conditions listed above.
Automation system (AS)
Setpoints/parameters per RPH
48 setpoints/parameters per recipe phase with a maximum of 5 text
string setpoints/parameters and a maximum of 32 characters per
text string
RPHs per ROP
96 recipe phases and transitions (total quantity) per recipe operation
(ROP)
ROPs per RUP
20 recipe operations (ROPs) per recipe unit procedure (RUP)
RUPs per AS
16 units per AS with 48 setpoints/parameters per recipe phase
(RPH)
BATCH capacity limits Number
Number of batches that can run simultaneously in a batch process cell64
Number of recipe phases (RPH) that can run simultaneously in a batch 150
Number of recipe phases that can run simultaneously in a batch process cell 300
Regardless of the data listed in the table above, in each AS a maximum of 100 recipe objects,
for example recipe operations, recipe phases and transitions, may change their status per
second. In this case, the time taken for recipe processing accounts for approximately 60 to
70% of the maximum automation system cycle load.
We recommend that you do not process more than 300 active recipe phases on a BATCH
server (nor a redundant server).
Note
Number of recipe phases running simultaneously
Depending on the frequency and how often step changes occur, the SIMATIC BATCH server
can process significantly more than 300 active equipment phases/operations.
Report creation and archiving
SIMATIC BATCH can process data (XML archive file) up a maximum of 200 MB in a report.
This applies only when using the XML format with SIMATIC BATCH version V7.0 or earlier.
With SIMATIC BATCH V7.0 SP1 or later, this restriction no longer applies to reports due to
the use of a new XML format.
SIMATIC BATCH V8.2
74Operating Manual, 02/2016, A5E35958174-AA
Page 75
Product introduction and installation
3.7 Security aspects
This quantity of data is made up as follows:
● Size of the batch process cell (PCell)
● Number of recipe phases/recipe operations run through Also include multiple processing
in loops.
● Number of recipe parameters
● Number of trends and the number of measured values per trend. Also take into account
the duration of the recording and cycle time.
The following average data quantities can be used for an estimate:
● approx. 1.1 MB for 100 recipe phases
● approx. 0.5 MB for 100 recipe parameters
● approx. 0.05 MB for 1 trend with 300 measured values
● approx. 0.1 MB for 1 trend with 600 measured values
The situation could be critical with the following recipe constellations:
● Recipe phases run through large numbers of loops.
● Incorrect cycle times are configured for trend archives in WinCC.
The number of measured values is calculated from the duration of the trend divided by the
acquisition cycle time (for example 6000 s runtime for the trend / 10 sec. cycle time = 600
measured values). The number of measured values for trends can be limited to approximately
1000 measured values that are adequate for a good overview. A maximum of 50000 measured
values are possible per trend.
Note
A cycle time of 1 second and 24 hours runtime mean 86400 measured values.
A recipe with 1500 recipe phases would result in an archive data size of approximately 30 MB
for approximately 6 hours runtime.
Exceeding the specified recommendations means that batch reports and possibly also the
archiving of batches are no longer possible.
3.7Security aspects
With the increasing networking of processes in automation, matters concerning all aspects of
IT security are becoming more and more important. Consider all security aspects before
commissioning the hardware and software. You will find information about this with the
following link: www.siemens.com/pcs7-documentation (
SIMATIC PCS 7 makes the following documentation available:
● PCS 7 Compendium Part F - Industrial Security
This document presents the "Defense in Depth" security concept with example
configurations.
● SIMATIC PCS 7 Security Manuals
These documents contain important information on the following topics:
– Security concept
– Virus scanners
Note
Security aspects of SIMATIC BATCH
Shared directories, data, and archives must be continuously protected by suitable security
mechanisms. Note this for the following functions, in particular:
● Archiving batches (Batches > Archiving > Archiving method (Page 745)
) If you are using one of the following methods for archiving, the storage locations of the
archives must be protected:
– "Directory"
– "FTP server"
● Protecting backup files (Backup (Page 1076)/Restore) (Page 1076) and Export/Import
(Page 321)
You must protect these files (.sbx) because SIMATIC BATCH does not provide recognized
protection mechanisms for these files at present. One possibility is to create access
permissions for accessing the directory.
● Printing in process mode in the BatchCC/BATCH recipe editor
To avoid intervention in the operating system, devices/printers such as XPS printers or PDF
printers must not exist or not be selectable in print dialogs. Remove such devices or printers
in the Windows Control Panel.
● Settings for secure process mode
To prevent intervention in the operating system, you need to configure the user rights
accordingly. Remove all rights that are not absolutely necessary for process mode.
We recommend that you do not grant rights for the commands "Back up", "Export" and
"Import" for process mode, as these commands could allow intervention in the operation
system.
The assignment of rights enables you to regulate all access in accordance with your own
wishes and thus guarantee secure process mode.
SIMATIC BATCH system
To increase security, we recommend that you use the "NTLM" mode for communication of the
SIMATIC BATCH system.
SIMATIC BATCH V8.2
76Operating Manual, 02/2016, A5E35958174-AA
Page 77
Product introduction and installation
3.8 Configuring the security settings on the SIMATIC BATCH server
Additional information
● You will find information about the "NTLM" mode in the following section:
Configuring the security settings on the SIMATIC BATCH server (Page 77).
● You will find information on the archiving method "SQL Server" in the sections:
3.8Configuring the security settings on the SIMATIC BATCH server
Security settings
You can increase the security of the communication of the SIMATIC BATCH system.
We recommend that you set the "NTLM" mode.
● For a new installation of version V8.2, the following applies:
On completion of the setup, configure the “NTLM” mode manually on all servers involved.
● The following applies to updates of a version lower then V8.2:
The system is automatically configured in the "Compatible" mode.
To use the increased security, configure the "NTLM" mode manually for all servers involved.
Note
With a redundant server set the same mode on both servers.
Requirements for manual configuration
● In Windows a user account (login) incl. password has been created.
● The user is a member of the SIMATIC BATCH group and a member of the administrators
group..
● The user has the right "Login as service" (1).
● We recommend that you set the runtime of the password so that it never elapses.
● BATCH Runtime and the BATCH project are exited.
Procedure
1. Right-click on the symbol "BATCH Launch Coordinator" in the Windows taskbar.
2. Select the command "Change security settings ...".
3.8 Configuring the security settings on the SIMATIC BATCH server
3. Click on the "Yes" button. in the "User Account Control" dialog box.
4. Select the "NTLM (recommended)" option.
5. Enter the user name in the "Login" input box.
– For the local user
" \User name"
Note
Even if "dots" are shown in the input box for the password, you need to enter a valid
password.
– For the user of a domain
"Domain\User name"
6. Enter the password in the input box.
7. Click on the "OK" button.
8. Select the command BATCH Project > Start"
Result
The SIMATIC BATCH server system uses the NTLM mode.
Note
If the password elapses, the user is disabled or deleted, the SIMATIC BATCH server system
does not operate.
"Compatible" mode
If the "NTLM" mode does not work correctly, change the mode to "Compatible".
In this mode, the SIMATIC BATCH server system operates as in the past.
Additional information
You will find information on security aspects the section Security aspects (Page 75).
(1) You will find information on the right "Login as service" in the documentation of Windows.
SIMATIC BATCH V8.2
78Operating Manual, 02/2016, A5E35958174-AA
Page 79
3.9Installation
3.9.1Delivery type of SIMATIC BATCH
Program packages
SIMATIC BATCH is delivered in different program packages for engineering and process mode
(Runtime). Within the setup of SIMATIC PCS 7, you choose the appropriate programs for
installation depending on the intended use of the PC.
The following program packages are available for SIMATIC BATCH:
Table 3-1BATCH program packages and their components
Product introduction and installation
3.9 Installation
Intended useProgram
package
PC as engineering Station
(ES) with BATCH engineering.
PC as BATCH Single Station
with all available BATCH com‐
ponents for engineering and
runtime (WinCC and BATCH).
PC as classical BATCH Server
with BATCH Runtime
PC as OS Server with WinCC
Runtime, BATCH Faceplates,
and BATCH Communication
Connector
Information server on which
the SIMATIC BATCH reports
are created
-
You install the required SIMATIC BATCH software package on the appropriate PCs depending
on the type of system you have. The accompanying authorizations are required to use the
BATCH software packages. The acquired authorizations are managed with the Automation
License Manager.
The SIMATIC BATCH COM API package is an optional package for SIMATIC BATCH. It
provides you with an interface for accessing SIMATIC BATCH data and initiating actions with
function calls. If authorization is not available, you still have read access to the data. With
authorization, you also have write access to the data.
Additional information
Authorizations (Page 83)
ComponentsAuthorizations
● BATCH Base
● BATCH Client
● Information Server - BATCH
Options
BATCH Single Station User or
BATCH Client and BATCH Recipe
System
Without license
3.9.2SIMATIC BATCH Basic
Authorization characteristics of SIMATIC BATCH Basic
SIMATIC BATCH Basic requires no separate installation. A BATCH client that checks the
authorizations on a BATCH server to distinguish SIMATIC BATCH and SIMATIC BATCH
Basic. The scope of functions for BATCH clients depends on the authorizations transferred to
the BATCH server. BATCH clients are, for example, instances of BatchCC, BATCH OS
controls or API clients.
If a BATCH server contains both the authorization for SIMATIC BATCH and SIMATIC BATCH
Basic, the higher authorization is used with full functionality.
Functional scope of SIMATIC BATCH Basic
The following functions are not available or only available in restricted form in SIMATIC BATCH
Basic:
● The "Libraries" and "Formulas" folders are not displayed in the project tree of BatchCC.
The libraries and formulas can therefore not be used.
If you import a system backup containing libraries or formulas, the two folders and the
objects they contain are shown in BatchCC. In this case, the library or formula can be
released, but not the recipe that uses the library or formula.
● No "Synchronization" tab in the properties dialog for recipe engineering. This means the
connection to MES (MES_Sync_Request) cannot be configured or used.
SIMATIC BATCH V8.2
80Operating Manual, 02/2016, A5E35958174-AA
Page 81
● No "Transfer parameters" tab in the properties dialog for recipe engineering. This means
the connection to SIMATIC Route Control cannot be configured or used.
● No release of recipes that contain command steps or monitoring objects. A list of errors
preventing release is displayed for the plausibility check and and attention is drawn to
insufficient licenses.
● No OSC. This means recipe structures cannot be changed in runtime.
● No electronic signatures (ESIG). This means that electronic signatures cannot be
configured in the recipe engineering or subsequently used in batches.
● The use of the following extended recipe structure elements (extended SFC structures) is
not possible:
– Insertion of library references
– Insertion of command steps
– Insertion of monitoring
Display of the reduced range of functions in the user interfaces
If you authorize SIMATIC BATCH Basic, the functions described above are either not displayed
in the interface menus and dialogs, or they are grayed out. In both cases, the functions are
not available.
Product introduction and installation
3.9 Installation
Handling of structural elements from recipes through restore and import
Recipes that you obtain through import or restore in BatchCC are subjected to a plausibility
check. If these recipes contain elements such as "Monitoring", "Command step" or "Library
reference", the plausibility test will fail because the contained recipe elements are not
authorized. Save these recipes with a new name, remove the objects preventing release, and
release the recipe once again.
3.9.3Requirements for installation
Important information in the readme files
When installing SIMATIC BATCH, the hardware and software requirements for SIMATIC PCS
7 apply. The requirements for the installations are described in the file "PCS 7 readme" and
in the "SIMATIC BATCH readme".
You will find the following information in the file"SIMATIC BATCH Readme" or "sbreadme.mht":
● The hardware requirements for the systems to be installed
● Software requirements for the systems to be installed
Both files can be found on the product DVD and you should read them prior to installation.
They will provide you with important information on installation. You can find the "PCS 7
Readme" in the main directory of the data medium with the name "pcs7-readme.rtf" and the
"SIMATIC BATCH readme" in the subdirectory "..\60_SB__V8.0\SBBASEEU\setup" with the
name "sb-readme.mht". You can display and read both files on the monitor or print them out.
After installing the software packages, the two files are stored in the following path: Start >
SIMATIC > Information > Language selection > PCS 7 - Readme / SIMATIC BATCH readme.
Installation procedure
SIMATIC BATCH contains a setup program that installs the software automatically. Depending
on the operating system configuration, the setup program starts automatically once the DVD
is inserted in the drive. If this does not happen, you can start the setup program manually from
the DVD.
The wizard started with the setup program guides you through the installation procedure step
by step and, after querying the user data and required configuration, starts the actual
installation process.
Access permissions for the operating system set by SIMATIC BATCH
After the installation, SIMATIC BATCH configures the local group "SIMATIC BATCH" in the
Windows user and group management. The members of this group have full access to the
SIMATIC BATCH shared folder "sbdata" . The user who installed SIMATIC BATCH and the
local administrator are entered automatically in this group. Additional members of this group
must be added manually by an administrator.
Additional information
● Make sure that you read the latest information on SIMATIC BATCH in the "sb-readme.mht"
file on the software DVD.
● You fill find detailed information about the installation requirements of the PC stations for
PCS 7 plants in the manual "PCS 7 - PC Configuration and Authorization".
3.9.4Readme file with the latest information
Readme file
Note
Make sure that you read the latest information on SIMATIC BATCH in the SB readme file on
the software DVD.
SIMATIC BATCH V8.2
82Operating Manual, 02/2016, A5E35958174-AA
Page 83
How to open the readme file:
Product introduction and installation
3.9 Installation
● Double-click on the sb
● During the product setup, click the "Readme" button in the right hand pane for the "BATCH
Base ..." component or
● from the Start menu of Windows:
Start > SIMATIC > Information > English > SIMATIC BATCH - Readme
3.9.5Authorizations
General information
To use SIMATIC BATCH software, you require authorizations (licenses, license keys).
Software protected in this way may only be used if the Automation License Manager (ALM)
finds installed authorizations for the relevant installed software package. See the table below
for SIMATIC BATCH client authorizations. In ALM, you can configure which PC in the network
should be searched for licenses. SIMATIC BATCH server authorizations must be located on
the SIMATIC BATCH server concerned, as the employed SIMATIC BATCH software will
search for them there. If the appropriate authorizations are not detected, a dialog regularly
appears informing you of the missing authorizations, which is inconvenient while you are
working.
The authorizations required for SIMATIC BATCH are on the authorization data medium that
ships with the product.
-
readme.mht on the DVD ROM,
To transfer the authorization from the authorization data medium to the hard disk of the PG/
PC, use the "Automation License Manager" program in the Windows start menu under Start
> Programs > Siemens Automation > Automation License Manager.
If you have followed the SIMATIC PCS 7 installation instructions, you will already have
transferred the required authorizations from the authorization data medium to the hard disk of
the PG/PC during the installation of SIMATIC PCS 7. If not, you can subsequently transfer the
required authorizations to the PCs or back to the authorization data medium at any time using
the "Automation License Manager" program.
Transferring authorizations
The number of individual authorizations is recorded by a counter. When transferring a
authorization from the authorization data medium to the hard disk of a PC, the counter on the
data medium is decremented by 1. If the counter (number of authorizations) reads "zero", no
more authorizations are available on the authorization data medium.
You can find detailed information on handling authorizations in the basic help of the SIMATIC
Manager and in the Automation License Manager help.
If you require a larger number of units due the requirements of your project, you will need to
use ALM to transfer a new, extended authorization from the authorization data medium to the
relevant PC. Licenses for units for SIMATIC BATCH are derived from the number of
"UNIT_PLC" unit blocks used.
Maximum distribution of SIMATIC BATCH software for use with all option packages
Depending on the use of a PC, e.g. as a BATCH server (BATCH master server, BATCH
standby server) or BATCH client, different authorizations are required on the relevant PC.
The following authorizations are available for SIMATIC BATCH:
Intended useLicense Key / ProductVersion Note
SIMATIC BATCH serverBATCH ServerV8.2This license is required on a BATCH server PC. In the
case of a redundant configuration, this license is required
on both BATCH server PCs.
If this license is available on a BATCH server, it offers a
connected BATCH client the full range of functions in
BatchCC.
BATCH BasicV8.2This license is required on a BATCH server PC. In the
case of a redundant configuration, this license is required
on both BATCH server PCs.
If this license is available on a BATCH server, it offers a
connected BATCH client a limited range of functions in
BatchCC.
BATCH 1 UnitV8.2This license is required on BATCH server PCs. In the
case of a redundant configuration, this license is required
on both BATCH server PCs. The number 1 indicates the
number of possible, configurable units.
BATCH 10 UnitsV8.2This license is required on BATCH server PCs. In the
case of a redundant configuration, this license is required
on both BATCH server PCs. The number 10 indicates
the number of possible, configurable units.
BATCH 50 UnitsV8.2This license is required on BATCH server PCs. In the
case of a redundant configuration, this license is required
on both BATCH server PCs. The number 50 indicates
the number of possible, configurable units.
BATCH APIV8.2This license is required on BATCH server PCs. In the
case of a redundant configuration, this license is required
on both BATCH server PCs. The license authorizes you
to use the Application Programming Interface.
Upgrade package
BATCH server
BATCH Single Station
System
V8.2Entitles you to install the latest updates of SIMATIC
BATCH on a BATCH server.
V8.2This is a license bundle, containing the following individ‐
ual licenses: BATCH Server.
SIMATIC BATCH V8.2
84Operating Manual, 02/2016, A5E35958174-AA
Page 85
Product introduction and installation
3.9 Installation
Intended useLicense Key / ProductVersion Note
SIMATIC BATCH ClientBATCH ClientV8.2This license is required on each PC on which BatchCC
is to be installed and used, regardless of whether this is
a BATCH server or a BATCH client. Any number of
BatchCC and BATCH OS Control instances can be star‐
ted and operated on this PC.
BATCH Recipe SystemV8.2This license is required on each PC on which recipe en‐
gineering is to be performed, regardless of whether this
is a BATCH server or a BATCH client.
Upgrade package
BATCH Client
BATCH Single Station
User
V8.2Entitles you to install the latest updates of SIMATIC
BATCH on a BATCH client.
V8.2This is a license bundle, containing the following individ‐
ual licenses: BATCH Client and BATCH Recipe Editor.
SB server products: You must have one of the BATCH UNIT authorizations on a SIMATIC
BATCH server. Depending on the number of configured units in your BATCH process cell, it
may be necessary to transfer additional UNIT authorizations. UNITs and authorizations can
be summed or counted here. Example: With a BATCH 10 UNITs and a BATCH 50 UNITs, you
can operate a BATCH process cell with 60 units.
SB client products: The SIMATIC BATCH client authorizations are searched for both locally
on a specified PC and on a PC specified in the network. The method of searching for
authorizations in the network must be configured in the Automation License Manager.
SIMATIC BATCH server authorizations, such as BATCH UNIT authorizations, are searched
for on the SB server. The message about missing authorizations is, however, output on a
SIMATIC BATCH client.
Note
BATCH engineering: The number of units is the sum of the "UNIT_PLC" BATCH interface
blocks. The number of configured and used units is displayed in the log that can be opened
from the BATCH configuration dialog.
Note
Missing authorizations
If neither trial licenses nor BATCH licenses are detected on BATCH PCs, all the actions you
want to perform on BATCH clients are prohibited, except for the operation of batches that are
already active. You can continue to operate, complete, and archive active batches.
Additional information
Display number of units (Page 194)
You can find more information in the following PDF documents:
Automation License Manager - Manual
PCS 7 - PC configuration and authorizations
You start the SIMATIC BATCH installation programs during the SIMATIC PCS 7 system setup.
On-screen prompts guide you step by step through the entire installation. The SIMATIC PCS
7 system setup is started with the normal Windows procedure for installing software.
Note
Make sure that you read the information on installing SIMATIC BATCH in the
The readme file is on the same DVD as SIMATIC BATCH. You will find detailed information
on installing and configuring the PC stations for SIMATIC PCS 7 process cells in the manual
Process Control System PCS 7; PC Configuration and Authorization
Installation options for the software components
The installation program of SIMATIC BATCH guides you through the installation.
Note that with a multiple station system, the installation program must be run on every client/
server PC.
At the start of the installation, the following software components are available for selection:
● BATCH Base (basic software, API; does not need to be selected as it is installed
automatically)
● BATCH Builder (BATCH engineering)
● BATCH Client (Batch Control Center, BATCH Recipe Editor)
● BATCH Fastobjects (for database server)
● BATCH server (BATCH control server, batch data management)
● BATCH WinCC Client Options or BATCH WinCC APL Client Options (block icons and
faceplates in classic or APL design, BATCH OS controls, and BATCH online help)
SB-readme
.
file.
● BATCH WinCC Server Options (block icons and faceplates in classic or APL design)
● BATCH blocks (SIMATIC BATCH blocks)
● Information Server BATCH Options (templates for batch reports on an Information Server)
All components are installed automatically. At the end of the installation, you will be asked for
the path where you want to create the BATCH shared folder (database folder) "sbdata". The
location suggested as standard will vary depending on the operating system. You can also
specify your own folder path. Note that, depending on the operating system, it may be a hidden
folder that you only make visible by changing certain folder options.
You can find the folder path to the BATCH shared folder as follows: Open the "Shares" folder
in Computer Management under System > Shared Folders > Shares. The shared folder name
is "BATCH" and the folder path is also displayed.
SIMATIC BATCH V8.2
86Operating Manual, 02/2016, A5E35958174-AA
Page 87
BATCH BUILDER (BATCH Engineering)
Note
BATCH engineering is only installed if SIMATIC PCS 7 (SIMATIC Manager) has already been
installed on the ES PC. It is possible to install only BATCH engineering on an ES PC without
client or server functionality. This installation is perfectly adequate for configuring batch objects
and their distribution. The BATCH blocks must be installed separately, if required.
BATCH WinCC Client Options or BATCH WinCC APL Client Options
BATCH faceplates and block icons are supplied in two variants:
● In the standard classic "BATCH WinCC Client Options" form
● In the style of the Advanced Process Library "BATCH WinCC APL Client Options"
Note
Installation of Client Options
Product introduction and installation
3.9 Installation
Only one selection is possible during installation.
If one variant is already installed, SIMATIC BATCH setup only offers an update for this variant.
However, you can convert to the other variant at any time after you have uninstalled the
previous variant. Make sure that the same variant of the "BATCH WinCC Options" is installed
and used throughout the entire system (ES, OS server, OS clients).
The following steps are crucial for automatic update to the new picture objects in APL style:
● Installation of the "BATCH WinCC APL Client Options" component
● Plant Hierarchy - Create / update block icons or compile the OS with the "Picture Tree"
option.
Note
Manually update process pictures which do not include automatically created and
interconnected picture objects. Picture objects which you have copied manually from the
"@PCS7Typicals_Batch.pdl" file and pasted into your process pictures are deleted.
A special web plugin is available for both variants of the WinCC Client Options. Depending on
your selection, the corresponding web plugin is installed on a web server using the following
path:
C:\ProgramFiles\Common Files\Siemens\webplugins
The Web Configurator copies the installed web plugin to the following path:
If you select a variant change of the faceplates, the corresponding web plugin is deleted in the
following path.
C:\Program Files\Common Files\Siemens\webplugins
However, the Web Configurator does not delete the corresponding web plugin under C:
\Program Files\SIEMENS\WINCC\Webnavigator\Server\Web\install\custom. Both web
plugins can then be installed on the web client which can result in errors.
There are several options to prevent that an incorrect web plugin in installed on a web client:
● Always install the currently used web plugin on the web client in the end
● Only install the currently used web plugin on new web clients
● Delete the previous web plugin manually in the following path C:\Program Files\SIEMENS
\WINCC\Webnavigator\Server\Web\install\custom
Uninstalling
Note
If you remove SIMATIC BATCH, you must always do this before removing the plant hierarchy
(SIMATIC PH).
Installation in a redundant system
Note
A few particular requirements must be observed in a redundant PCS 7 system. A detailed
description of the installation can be found in section "Redundancy (Page 54)".
SIMATIC BATCH V8.2
88Operating Manual, 02/2016, A5E35958174-AA
Page 89
3.10Plant update
Introduction
The following section describes the basic procedure for a plant update.
Read the information in the "PCS 7 Readme" file before beginning the system update.
A plant update includes:
● Replacement of existing hardware, such as PC, AS memory, network adapters
● If applicable, the installation of new operating systems, such as Windows 7 and Windows
Server 2008 R2 64-bit
● Installation or reinstallation of SIMATIC PCS 7 with SIMATIC BATCH = software update.
For the update, there are two possible options:
– With use of new functions
– Without use of new functions
● Update of PCS 7 project with SIMATIC BATCH = project update
Product introduction and installation
3.10 Plant update
Notes
● It is possible to use a "PC image" for the supported operating systems.
● If you select a 64-bit operating system, you may need to replace existing CP1613 A1 type
communications processors with a new CP1613 A2 for BATCH servers, BATCH clients
and the ES.
● If you use the "AS-based" mode, it may be necessary to expand the memory of your
automation systems.
● Software update during operation (SUIR)
Older versions cannot be upgraded to version SIMATIC BATCH V8.2 during operation.
The software update is once again supported in later versions.
With the redundant SIMATIC BATCH server both servers must be completed using the
SIMATIC BATCH start coordinator before a software update may be started.
Before the servers can be restarted in redundant mode the security settings on both servers
must be set to the same mode (either only “Compatible" or only “NTLM”). If this is not the
case, this can lead to disturbances in operation.
With a software update of the servers the server security setting is initially set to
"Compatible".
With a new installation of servers before starting the server the server security setting
(“Compatible" or “NTLM”) must be made.
The restrictions do not apply to service packs and updates within the version SIMATIC
BATCH V8.2.
For more information about making the security settings data, refer to the section
“Configuring the security settings on the SIMATIC BATCH server (Page 77)“
● As of SIMATIC BATCH V7.0, enumerations are supported for the BOOL data type. If you
use this type, now it will be interpreted as ENUM and no longer as BOOL. This results in a
type change during generation, which means that the plausibility check will mark the release
of such recipe objects as invalid when you update the plant in BatchCC. If you want to use
recipe parameters of the Enumeration data type in master recipes, configure the ENUM
data type instead of BOOL in the PCS 7 engineering.
● If you have configured a redundancy status display of the SIMATIC BATCH server in a
process picture on a WinCC client in a previous version of SIMATIC BATCH, it must be
removed in order to update the system to SIMATIC BATCH V8.2. Instead, use the icons in
the status bar of BatchCC to display and check the status of the BATCH server.
Software update
You can update PCS 7 projects of the following SIMATIC BATCH versions SIMATIC BATCH
V8.2:
● SB AS based
– SB AS based V6.1 (incl. SPs and HFs) (only with Siemens Support)
– SB AS based V7.0 (incl. SPs and HFs)
● SB
– SB V6.0 (up to SP3 and HFs) via SB V6.0 via SB V6.1 SP3
– SB 7.0 (incl. SPs and HFs)
– SB 7.1 (incl. SPs and HFs)
– SB V8.0 (incl. SPs and UPDs)
– SB V8.1 (incl. SPs and UPDs)
Special notes
If the software was updated from one of the following versions to SB V8.0, SB V8.1 or SB V8.2,
the SB data can only be updated using Restore (in the BCC).
● SB V6.0 (up to SP4 including HFs)
● SB V6.1 (incl. SP3 and HFs)
● SB V7.0 (incl. SP1 and HFs)
● SB V7.1 (incl. SP1 and HFs)
● SB V7.1 (incl. SP2 and HFs)
Preparations for a software update
1. Archive closed batches in the BATCH Control Center.
2. Create a backup of your BATCH process cell in the BATCH Control Center.
3. Archive your PCS 7 project in the SIMATIC Manager.
4. If necessary, replace existing hardware, such as PC, AS memory, network adapters.
SIMATIC BATCH V8.2
90Operating Manual, 02/2016, A5E35958174-AA
Page 91
5. Select the recommended Windows operating systems for the PCs of your process cell
configuration (SB servers, SB ).
6. Install the operating system.
You can use images that have already been created.
Software update (standard)
1. Update the software on the engineering station (ES).
2. Update the software on the SB server computer.
3. Update the software on the SB client computer.
4. After a successful update and reboot of the computer, start your SB system.
Note
Since on a single station system, the SB server and the SB clients are installed on one
computer, a software update is only required once.
Product introduction and installation
3.10 Plant update
Software update during operation (SUIR)
To keep the process continuously controllable during a software update, a redundant SB server
is required.
Note the following order during the procedure:
1. Update the software on the engineering station (ES).
2. Update at least one SB client and the SB standby server.
3. Start the updated SB client and the SB standby server after successful updating and
rebooting the computers..
4. Check the status of the SB server.
The SB server data on the standby server are compared completely with the master server
when the standby server reports the status "Listening".
You can check the status of the SIMATIC BATCH server using the symbol of the BATCH
start coordinator or using the shortcut menu command "BATCH status...”.
5. Check the corresponding WinCC status messages in the Alarm Logging "CDV on BATCH
server "server name": CDV is ready for operation".
The message is only displayed when no PH is configured.
The SB standby server is ready to take over when the WinCC status message is displayed.
6. Shut down the SB master server.
This produces a redundancy failover.
The updated SB standby server becomes the SB master server.
7. Update the previous SB master server and all clients that have not yet been updated.
8. After a successful update and reboot of the computers, start the previous SB master server
and the SB clients.
The previous SB master server is now the SB standby server.
9. Check the status of the SB server.
The SB server data on the standby server are compared completely with the master server
when the standby server reports the status "Listening".
You can check the status of the SIMATIC BATCH server using the symbol of the BATCH
start coordinator or using the shortcut menu command "BATCH status...”.
10.Check the corresponding WinCC status message in the Alarm Logging "CDV on BATCH
server "server name": CDV is ready for operation".
The message is only displayed when no PH is configured.
11.The update of the redundant SB system is now complete.
Note
Older versions cannot be upgraded to version SB V8.2 during operation.
Note the paragraph “Software update during operation (SUIR)” in the section”Notes”.
Procedure after a software update
1. Authorize all the PCS 7 software components used on all PCs in the Automation License
Manager.
2. Retrieve your PCS 7 project in the SIMATIC Manager.
3. In HW Config, configure new hardware components, for example, a new communications
processor.
4. Open all the current block libraries and update the blocks used in your PCS 7 project with
the command Options > Charts > Update block types.
5. If you use the "AS-based" mode, the "IUNIT_BLOCK" block from older SIMATIC BATCH
versions must be replaced in all CFC charts by the extended block, "UNIT_PLC". To do
this, drag it directly from the SIMATIC BATCH V8.2 library to the corresponding CFC charts
and interconnect it again if necessary.
6. Update the "UNIT_PLC" block in the CFC editor under Options > Block types... > New
version .... This transfers the block from the chart folder to the block folder, "Offline".
7. Compile and download the CFC charts to the automation system.
8. Compile all PCS 7 operator stations (server, clients). Then, open each individual PCS 7
OS station within your PCS 7 project on the ES and run the OS project editor. When the
WinCC Explorer is closed for each PCS 7 OS, download the current data to the appropriate
destination stations.
SIMATIC BATCH V8.2
92Operating Manual, 02/2016, A5E35958174-AA
Page 93
9. Perform the following configurations in the BATCH configuration dialog:
– If you use the "AS-based" mode, specify the current memory configuration and select
the percent to be allocated to the recipe logic in the AS.
– Generate and propagate batch types
– Compile and merge BATCH instances
– Adapt and update settings, if necessary
– Transfer BATCH messages to the relevant PCS 7 OS
– Download BATCH server. You may be notified about other actions that need to be
performed. Process cell data can only be downloaded to the BATCH server after
performing the remaining actions.
10.Start process mode on all servers (OS, BATCH).
11.Perform a restore on a BATCH client and update the process cell data in BatchCC.
3.11Time-of-day synchronization
Product introduction and installation
3.12 System properties
Time-of-day synchronization of all components involved
PCS 7 time-of-day synchronization must be planned, configured and used with SIMATIC
BATCH.
The time on the AS serves as the basis for the time stamping of recipe element status
transitions. This time must be synchronized with the time of the PCS 7 OS server and the
clients so that entries in the BATCH reports and message list can be put into correct
chronological order.
Additional information
● Set time of day (Page 480)
● Additional information can be found on the Siemens Industry Online Support page by
entering the manual title:
PCS 7 Time Synchronization
3.12System properties
System properties
Note the following system properties for your configuration:
● Batches that use flat recipes cannot be executed in AS-based mode.
● Visualization and operator control of batches with flat recipes is not supported in the BATCH
OS controls.
● The interface blocks from SIMATIC BATCH V4.x contained in your project can continue to
be used in SIMATIC BATCH. A reconfiguration is not possible, however.
● Valid only for recipe unit procedures (RUPs) executed in AS-based mode: Character strings
containing more than 32 characters are truncated. Example: STRING values within
transition conditions. At the start of the batch, a recipe conversion takes place in which
character strings exceeding 32 characters are truncated.
● Number formats: When numbers are entered, displayed, and used further within SIMATIC
BATCH, a comma is converted to a period. This means that a period is used as the decimal
separator. A thousand separator is not used or displayed.
● In batch logs, process values are always output for the configured control strategy in the
master recipe. If there is a control strategy discrepancy between SIMATIC BATCH and the
function or operation type (EPH/EOP), the process values for the parameters are not fully
logged.
Impermissible characters
The following characters are not permitted when assigning names in SIMATIC Manager: " / \
[ ] : | < > + ; , ? " * = . ! @ { } space
The names "EPH", "EOP", "UNIT", and "UNIT_PLC" are key words. Please do not use these
names for name assignment of an SFC type in SIMATIC Manager. In addition, the following
characters are not permitted when assigning names (name of the control strategy): Special
characters except underscore and space
When the name of the control strategy is changed, for example, from "CONTSTRAT1" to
"contstrat1" in the characteristics dialog for SFC types, this change to the control strategy name
is not applied after the generation of the batch types.
The following characters are not permitted when assigning names of WinCC projects: , ; : ! ?
" ' + = / \ @ * % [ ] { } < > space
The following characters are not permitted in AS/OS connection names: : ? " ' \ * % space
The following characters are not permitted when assigning names of hierarchy folders: " ' / \
%
The following characters are not permitted in global declarations (enumerations): space " % .
' \ ? * : @
Note
Also note the extensive information in the online help of PCS 7 OS (WinCC Information
System). Search there for "impermissible characters". We recommend that you never use
special characters when configuring in the SIMATIC Manager. The only exception is the special
character [ _ ] (underscore).
SIMATIC BATCH V8.2
94Operating Manual, 02/2016, A5E35958174-AA
Page 95
3.13Using online help
3.13.1Using help
Introduction
Information on SIMATIC BATCH is described centrally in the SIMATIC BATCH online help.
Contents
For configuration the SIMATIC BATCH online help offers access at any time to the complete
documentation, which consists of the following components:
● Online help
● Release notes with important up-to-date information on SIMATIC BATCH
● SIMATIC BATCH installation instructions
Product introduction and installation
3.13 Using online help
Open SIMATIC BATCH help
● In the BATCH Control Center or in the recipe editor open the SIMATIC BATCH online help
via the "Help Topics" menu item in the "Help" menu. Alternatively you can open the SIMATIC
BATCH online help via the <F1> button.
● If you are using the SIMATIC Manager, open the SIMATIC BATCH online help by selecting
an object in any view and then selecting "SIMATIC BATCH" in the context menu. In the
BATCH configuration dialog "Configure batch process cell..." click on help.
3.13.2Search
Searching in the online help
Introduction
The "Search" tab offers various options for configuring your search for maximum effectiveness.
To search for a complex term, use "*" as a wildcard. The asterisk stands for any character in
any quantity
● Example: Searching for "*alarms" locates all topics containing the following words:
"Alarms," "system alarms" "analog alarms" and "discrete alarms".
Note
In addition to the "*", the search item must contain at least one other non-wildcard character.
If you do not know the exact spelling of a term or you are searching for a series of terms, use
"?" as a wildcard. The question mark stands for any single character at this position.
● Example: Searching for "T?p?" locates all topics containing the following words: "Type",
"Tips", but not "Types".
Full-text search
To perform a full-text search, use quotation marks.
● Example: The "configuring graphic" search string returns all topics containing these words.
Search with Boolean expressions
You can perform a search with a logic operation by linking the search strings with the Boolean
operators AND, OR, NEAR or NOT. Click the arrow next to "Enter search strings".
● Example: The search string "graphic" AND "configuring" returns all topics containing the
word "graphic" and the word "configuring".
● Example: The search string "graphic" OR "configuring" returns all topics containing either
the word "graphic" or the word "configuring," or both.
● Example: The search string "graphic" NOT "function key" returns all topics containing the
word "graphic" but not the term "function key".
● Example: The search string "graphic" NEAR "configuring" returns all topics containing the
word "graphic" and, within the next eight words, the word "configuring," or vice versa.
Note
When a search string contains one of the words AND, OR, NEAR, or NOT, the search item
is interpreted as a Boolean expression. To nest a Boolean expression, use parentheses.
Example: ("Graphic" AND "configuring") OR ("Graphic" NOT "function key").
Search for similar words
To search for words with similar spelling, enable "Search for similar words".
● Example: When "Search for similar words" is enabled, the search string "Mayor" returns all
topics containing the words "Mayer," "Moyer," and "Meyor".
SIMATIC BATCH V8.2
96Operating Manual, 02/2016, A5E35958174-AA
Page 97
Search in titles
To restrict the search for the search string to topic headers, enable "Search in titles only".
Search in search results
To restrict the search to those topics returned by the last search, enable "Search previous
results". This sets a closer range of topics found.
Note
To search across all topics again, disable "Search previous results".
Sorting search results
To sort the topics found in alphabetical order, click "Title" or "Position". The topics are sorted
in alphabetical order according to their title or position. The parent chapter associated with the
topic found is indicated under "Position".
Product introduction and installation
3.13 Using online help
Reusing a search
In order to reuse one of the recent search strings, click the 'Enter search strings" arrow. Select
a search string from the recent list, then click "Show topics".
Note
A search string is added to the recent list only if at least one topic was found containing the
search string.
Highlighting search strings
In the view of a topic found, all instances of the search string are highlighted.
Note
Click the "Options" toolbar button to enable or disable highlighting of search strings.
Search within the topic
To search for terms within a topic, press <Ctrl+F>. You can search for whole words only, define
the search direction, or case-sensitive. When "Whole words only" is disabled, the search string
"Process" returns the term "ProcessValue" also. When "Whole words only" is enabled, only
the word "process" is found.
To access a chapter, click on one of the main topics in the navigation window. The subordinate
topics are shown in the right side of the display window.
SIMATIC BATCH online help toolbar
SymbolBrief descriptionAvailability
Hides the navigation area containing the tabs.
In this case the SIMATIC BATCH online help
requires less space on the screen.
Shows the navigation area containing the
tabs.
Navigates to the recently opened topic. This is not the first topic shown.
The navigation area is shown.
The navigation area is hidden.
Navigates to the next topic in a recent list of
topics.
The topic is not the last in the list of recent
topics.
Note
Icons labels are shown in the operating system language.
Tabs in the navigation area
The SIMATIC BATCH online help in the navigation area has multiple tabs. You access the
online help topics differently in each tab.
TabMeaning
ContentsIn the table of contents you have direct access to every topic of the SIMATIC BATCH
online help.
Index
You can also open the "Index" tab di‐
rectly in SIMATIC BATCH in the
"Help" menu via the "Index" com‐
mand.
Searching
You can also open the "Search" tab
directly in SIMATIC BATCH in the
"Help" menu via the "Search" com‐
mand.
Use keywords to find specific topics in the index. The string entered must match one
of the keywords in the index. A keyword is assigned one or several topics.
To display one of the topics found click on the "Display" button. You can also open a
displayed topic by double-clicking it.
To display the structure of the content of the displayed topic, click the "Contents" tab.
A search item is used to conduct a full-text search for topics. Click on the "Show
topics" button. Topics containing the search item in the header or text are located. To
display one of the topics found click on the "Display" button. You can also open a
displayed topic by double-clicking it.
To display the structure of the content of the displayed topic, click the "Contents" tab.
SIMATIC BATCH V8.2
98Operating Manual, 02/2016, A5E35958174-AA
Page 99
"Contents" tab
Product introduction and installation
3.13 Using online help
Topics are organized into sections and subsections in the table of contents.
The buttons in the "Contents" tab have the following meaning:
SymbolMeaning
Click the icon to display the subsections and topics included in this section.
The topic is displayed unchanged in the topic area.
Click the icon to hide the subsections and topics included in this section.
The topic is displayed unchanged in the topic area.
Click the icon to display the overview for this section.
Double-click the icon to display the overview for this section and, simultaneously, the sub‐
sections and topics included in this section.
Select the "Open all" command in the shortcut menu for this icon to display the overview for
this section and, simultaneously, all subsections and topics of the table of contents.
Navigate to subsections and topics of this section in the overview in the topic area.
Click the icon to display the overview for this section.
Double-click the icon to display the overview for this section and, simultaneously, to hide
the subsections and topics included in this section.
Select the "Close all" command in the shortcut menu for this button to display the overview
for this section and, simultaneously, to hide all subsections and topics of the table of contents.
Navigate to subsections and topics of this section in the overview in the topic area.
This is a "Basics" topic.
This is an "Example" topic.
This is an "Operating instruction" topic.
"Search" tab
The other search options are described in the "Search" section.
Navigation bar in the display window
The SIMATIC BATCH online help has a navigation bar that is located at the top of the display
window. The navigation bar provides links to other topics. The links are organized by link type.
If you move the cursor to a link type, a list of additional links is displayed. Clicking a link brings
you to the required information.
Note
A link type is not available in the navigation bar if no links of that type exist for the displayed
topic.
Link typeMeaning
In the sectionLinks to headers of the displayed topic.
Instructions
Color:
Links to handling instructions.
Subjects that are classified as Operating instruction, whose title bars are shown
in light brown in the display window.
Examples
Color:
Basic principles
Color:
EventsEvents of previously viewed links.
Options > StartThis calls the main help page.
Options > BackNavigates to the recently opened topic.
Options > NextNavigates to the next topic in a recent list of topics.
Options > Glossa‐ryOpens the help glossary.
Navigating with the keyboard
Instead of the mouse, use the keyboard to navigate.
OperationFunction
<Right>Displays in the table of contents the subsections and topics included in
<Left>Hides in the table of contents the subsections and topics included in the
<Up>Moves one row up in the table of contents.
<Down>Moves one row down in the table of contents.
<Page up>Scrolls upwards in the table of contents.
<Page down>Scrolls downwards in the table of contents.
<Enter> or <Input>Open or close the selected chapter
Links to examples.
Subjects that are classified as Example, whose title bars are shown in light green
in the display window.
See also links to background information e.g. definitions, details, GUI.
Subjects that are classified as Basics, whose title bars are shown in light blue in
the display window.
the section.
section.
SIMATIC BATCH V8.2
100Operating Manual, 02/2016, A5E35958174-AA
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.