Integration of S7-

1500 Package Units

with SIMATIC
PCS 7/OPEN OS
Siemens
SIMATIC PCS 7 V9.0 Industry
Online
https://support.industry.siemens.com/cs/ww/en/view/49740087 Support
 Legal information

Legal information
Use of application examples
Application examples illustrate the solution of automation tasks through an interaction of several
components in the form of text, graphics and/or software modules. The application examples are
a free service by Siemens AG and/or a subsidiary of Siemens AG ("Siemens"). They are
non-binding and make no claim to completeness or functionality regarding configuration and
equipment. The application examples merely offer help with typical tasks; they do not constitute
customer-specific solutions. You yourself are responsible for the proper and safe operation of the
products in accordance with applicable regulations and must also check the function of the
respective application example and customize it for your system.
Siemens grants you the non-exclusive, non-sublicensable and non-transferable right to have the
application examples used by technically trained personnel. Any change to the application
examples is your responsibility. Sharing the application examples with third parties or copying the
application examples or excerpts thereof is permitted only in combination with your own products.
The application examples are not required to undergo the customary tests and quality inspections
of a chargeable product; they may have functional and performance defects as well as errors. It is
your responsibility to use them in such a manner that any malfunctions that may occur do not
result in property damage or injury to persons.

Disclaimer of liability
Siemens shall not assume any liability, for any legal reason whatsoever, including, without
limitation, liability for the usability, availability, completeness and freedom from defects of the
application examples as well as for related information, configuration and performance data and
any damage caused thereby. This shall not apply in cases of mandatory liability, for example
under the German Product Liability Act, or in cases of intent, gross negligence, or culpable loss of
life, bodily injury or damage to health, non-compliance with a guarantee, fraudulent
non-disclosure of a defect, or culpable breach of material contractual obligations. Claims for
damages arising from a breach of material contractual obligations shall however be limited to the
© Siemens 2014 All rights reserved

foreseeable damage typical of the type of agreement, unless liability arises from intent or gross
negligence or is based on loss of life, bodily injury or damage to health. The foregoing provisions
do not imply any change in the burden of proof to your detriment. You shall indemnify Siemens
against existing or future claims of third parties in this connection except where Siemens is
mandatorily liable.
By using the application examples you acknowledge that Siemens cannot be held liable for any
damage beyond the liability provisions described.

Other information
Siemens reserves the right to make changes to the application examples at any time without
notice. In case of discrepancies between the suggestions in the application examples and other
Siemens publications such as catalogs, the content of the other documentation shall have
precedence.
The Siemens terms of use (https://support.industry.siemens.com) shall also apply.

Security information
Siemens provides products and solutions with Industrial Security functions that support the secure
operation of plants, systems, machines and networks.
In order to protect plants, systems, machines and networks against cyber threats, it is necessary
to implement – and continuously maintain – a holistic, state-of-the-art industrial security concept.
Siemens’ products and solutions constitute one element of such a concept.
Customers are responsible for preventing unauthorized access to their plants, systems, machines
and networks. Such systems, machines and components should only be connected to an
enterprise network or the Internet if and to the extent such a connection is necessary and only
when appropriate security measures (e.g. firewalls and/or network segmentation) are in place.
For additional information on industrial security measures that may be implemented, please visit
https://www.siemens.com/industrialsecurity.
Siemens’ products and solutions undergo continuous development to make them more secure.
Siemens strongly recommends that product updates are applied as soon as they are available
and that the latest product versions are used. Use of product versions that are no longer
supported, and failure to apply the latest updates may increase customer’s exposure to cyber
threats.
To stay informed about product updates, subscribe to the Siemens Industrial Security RSS Feed
at: https://www.siemens.com/industrialsecurity.

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 2
 Table of contents

Table of contents
Legal information ......................................................................................................... 2
1 Task ..................................................................................................................... 4
2 Solution............................................................................................................... 5
2.1 Overview............................................................................................... 5
2.2 Description of the core functionality ..................................................... 6
3 Basic principles ................................................................................................. 7
3.1 Configuration guidelines ....................................................................... 7
3.2 Editors ................................................................................................ 10
3.2.1 PCS 7 DBA AS Node Type Wizard .................................................... 10
3.2.2 PCS 7 DBA ......................................................................................... 11
3.2.3 PCS 7 DBA Type Editor ..................................................................... 11
4 Configuring an S7-1500 package unit ........................................................... 13
4.1 Acquiring data .................................................................................... 14
4.2 Generating OS block icons and faceplates ........................................ 16
4.3 Generating the AS node with the AS Node Type Wizard .................. 18
4.3.1 General tab ......................................................................................... 18
4.3.2 Instance Source tab ........................................................................... 19
4.3.3 "Connection" tab ................................................................................. 20
4.3.4 Addressing tab ................................................................................... 23
© Siemens AG 2014 All rights reserved

Special features when addressing an S7-1500 PU ........................... 24

Structured program design in the S7-1500 PU .................................. 27
Unstructured program design in the S7-1500 PU .............................. 31
4.4 Creating the AS node ......................................................................... 33
4.5 Generating AS object types ............................................................... 34
4.5.1 Creating a new type ........................................................................... 37
4.5.2 Including default types........................................................................ 37
4.5.3 Creating tags ...................................................................................... 39
4.5.4 Configuring alarms ............................................................................. 42
4.5.5 Attributes ............................................................................................ 46
4.6 Creating ASO instances ..................................................................... 47
5 Configuring the PC station with the DBA...................................................... 50
5.1 Adding a PC Station ........................................................................... 50
5.2 Creating a plant hierarchy .................................................................. 52
5.2.1 Setting project properties ................................................................... 52
5.2.2 Synchronizing the plant hierarchy ...................................................... 54
5.2.3 Extending the plant hierarchy ............................................................. 54
5.2.4 Assigning hierarchy folders to an OS ................................................. 55
5.2.5 Assigning AS object instances ........................................................... 56
5.2.6 Editing the properties of the objects ................................................... 57
5.2.7 Compile OS ........................................................................................ 57
5.3 PCS 7 operator station ....................................................................... 59
6 Appendix A ....................................................................................................... 61
6.1 Skript „CalcS71500Addr“.................................................................... 61
6.2 Skript „CalcS71500ASOAddr“ ............................................................ 62
7 Appendix B ....................................................................................................... 63
7.1 Service and support ........................................................................... 63
7.2 Industry Mall ....................................................................................... 64
7.3 Literature ............................................................................................ 64
7.4 History ................................................................................................ 64

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 3
 1 Task

1 Task
Introduction
System landscapes that have grown over time often consist of heterogeneous
automation technologies. With the introduction of the TIA portal, there exists the
requirement that new Package Units containing S7-1500 CPUs can also be
operated and monitored using a PCS 7 operator system.
SIMATIC PCS 7/OPEN OS is a PCS 7 option with which controllers that does not
belong to the range of SIMATIC PCS 7 system components can be integrated
into the PCS 7 process control system.
PCS 7/OPEN OS V9.0 enables the data exchange between the PCS 7 operator
station and various automation systems via the existing WinCC channels or via
the OPC channel. For third-party systems that can only be integrated via the OPC
channel, only the appropriate OPC server for the particular controller type is
necessary. PCS 7/OPEN OS supports the data exchange with the controllers via
Classic OPC DA, Classic OPC A&E and OPC UA DA.
The core of PCS 7/OPEN OS is based on the database automation software (DBA)
familiar from other OS options. This software is mainly composed of the following
components:
• SIMATIC PCS 7 OS engineering and runtime software
• PCS 7/OPEN OS DBA data base automation software
• PCS 7/OPEN OS runtime software option
© Siemens AG 2014 All rights reserved

The supplied base functionality of PCS 7/OPEN OS allows configuration engineers

to effectively integrate the S7-1500 controllers into the process control using the
PCS 7 operator system. This gives operators the option of operating and
monitoring the entire system from a single operator station, even if it contains
package units with S7-1500 controllers.

Overview of the automation task

An S7-1500 package unit is to be operated and monitored using the SIMATIC PCS
7 operator station. The integration of the system into the PCS 7 landscape will take
place using SIMATIC PCS 7/OPEN OS via S7-1500 OMS+ Channel.

Figure 1–1
PCS 7 Operator Station S7- 1500 Package Unit

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 4
 2 Solution

2 Solution
Using the PCS 7 SIMATIC PCS 7/OPEN OS option, this application example will
show you how you can effectively integrate S7-1500 controllers that do not belong
to the PCS 7 range into the PCS 7 system landscape.

2.1 Overview
The example contained in this document shows you how to integrate an S7-1500
package unit into an existing PCS 7 landscape. The S7-1500 controller is
integrated with the aid of the SIMATIC S7-1200 or S7-1500 channel of the PCS 7
operator station.

Figure 2–1
PCS 7 ES, PCS 7 OS
PCS 7/OPEN OS Client
Engineering

PCS 7 OS PCS 7/OPEN OS

Server Server
© Siemens AG 2014 All rights reserved

S7- 1500 Package Unit

Industrial Ethernet

PCS 7 AS

ET 200M
PROFIBUS

Advantages
The solution presented in this document offers you the following advantages:
• Complete integration of controllers that do not conform to PCS 7 into the
PCS 7 operator system
• Step by step instruction for configuration with PCS 7/OPEN OS
• Shared alarm and tag logging management of PCS 7 and third-party systems
on one operator system

Required knowledge
The following basic knowledge is required:
• Systems configuration with PCS 7 AS engineering
• Generation of a visualization with PCS 7 OS engineering

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 5
 2 Solution

2.2 Description of the core functionality

A core component for the PCS 7/OPEN OS engineering is the
PCS 7/OPEN OS DBA database automation software.
The DBA generates OS data such as:
• Plant hierarchy
• Tags and archive tags
• Connections
• Alarms and messages

The DBA can use the channels available in the PCS 7 OS to connect the systems
that are not PCS 7-conform. For example, drivers are integrated in WinCC for the
following third-party systems:
• SIMATIC S7-1200, S7-1500
• SIMATIC 505
• Allen Bradley
• Mitsubishi
• …

Third-party systems for which no special connections exist can use the OPC or
© Siemens AG 2014 All rights reserved

Modbus TCP open standards.

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 6
 3 Basic principles

3 Basic principles
3.1 Configuration guidelines
You will find here an overview of the steps necessary for integrating a third-party
system into the PCS 7 operator station using PCS 7/OPEN OS.

Table 3–1
No. Description
1. Collecting data

Before you start configuring, you will need the following information in order to
operate and monitor the package unit:
• Access type (S7 connection, OPC DA, OPC A&E, ...)
• Network addresses (OPC server, automation systems)
• Syntax of tag addresses
• Tags, interfaces, alarms
• Project file path of the target operator system
Plant hierarchy
2. Generating OS block icons and faceplates
© Siemens AG 2014 All rights reserved

Using the available knowledge of the structure of the objects (type of objects and
related tags) in the AS, you can generate the block icons and faceplates.
In conformance with PCS 7, the icons are stored in a Typicals file and the
individual views of the faceplates are generated.
Further information on the generation of icons and faceplates can be found in
the "SIMATIC PCS 7 Process Control System APL Style Guide" configuration
instructions in the following article:
https://support.industry.siemens.com/cs/ww/en/view/65601446

Note
It is imperative that this work be completed before the initial compilation of the
plant hierarchy.
3. Generating the AS node type

You will generate the AS node type using the AS Node Type Wizard. The Wizard
already contains information about the channel used and the corresponding
connections as well as the syntax of the tag addresses.
4. Creating the AS node

In the AS View of the DBA, you will generate an instance of the previously
generated AS node type. Depending on the setting, you may still be able to
adjust the connection parameters and assign an instance name in this view.
5. Generating AS object types

The AS objects (ASO) represent the objects present in the automation system,
e.g. motors, valves, closed-loop controllers, analog and digital values, and are
connected to the AS node type.
The ASO types can contain tag addresses, the tag format, tag attributes, and tag
alarms and messages.

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 7
 3 Basic principles

No. Description
6. Creating ASO instances

Create the ASO instances. These instances are always assigned to an AS node.
7. Creating a PC station

In the PC Station View of the DBA, you can define the OS project to which the
data will be compiled. Here, you will set the project path of the target system and
also specify a data log if one exists.
8. Specifying the plant hierarchy

An existing plant hierarchy can be read out from the SIMATIC project and
synchronized with the DBA project. In the Plant View of the DBA, you can then
create additional hierarchy folders and subsequently synchronize them with the
SIMATIC project again.
9. Assigning ASO instances to the plant hierarchy

Drag the ASO instances on to the corresponding hierarchy folder in the plant
view to establish the relationship of the AS objects to the operator system.
Depending on the mode of configuration, you may still be able to assign or adjust
tag addresses and attributes.
10. Compiling the DBA project
© Siemens AG 2014 All rights reserved

This process roughly corresponds to that of the OS compilation from the

SIMATIC Manager. Here, the necessary connections, tags, messages and icons
are created in the OS project.
11. Loading the OS and starting the runtime

If all sequences have been executed properly, the OS project can be loaded and
the OS runtime can be started.

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 8
 3 Basic principles

The following flow diagram shows the procedure for configuring third-party systems
using SIMATIC PCS 7/OPEN OS in abbreviated form.

Figure 3–1
© Siemens AG 2014 All rights reserved

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 9
 3 Basic principles

3.2 Editors
PCS 7/OPEN OS includes the following editors, which are briefly described below:
• PCS 7 DBA AS Node Type Wizard
• PCS 7 DBA
• PCS 7 DBA Type Editor

3.2.1 PCS 7 DBA AS Node Type Wizard

You will generate the AS node types using the AS Node Type Wizard.
Here, the following information will be stored:
• AS name
• Typical display
• Instance source (DBA or XML)
• Connection parameters
• Address syntax

You can start the AS Node Type Wizard at "Start > Siemens Automation > AS
Node Wizard".
You will find detailed information in the "PCS 7 Open OS Engineering Workflow
© Siemens AG 2014 All rights reserved

Guide" manual. The manuals are copied to your system during the OPEN OS
installation.

Figure 3–2

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 10
 3 Basic principles

3.2.2 PCS 7 DBA

The DBA Editor is the heart of PCS 7/OPEN OS. This is where you configure the
AS structures and connect them to the PCS 7 operator system. Here, you must
carry out the following tasks:
• Create the AS node and AS object instances (ASO's)
• Generate the plant hierarchy and assign ASO instances
• Compile the DBA project
You can start the DBA at "Start > Siemens Automation > PCS 7 DBA".
You will find detailed information in the "PCS 7 Open OS DBA" manual.
The manuals are copied to your system during the OPEN OS installation.
Figure 3–3
© Siemens AG 2014 All rights reserved

3.2.3 PCS 7 DBA Type Editor

Using the DBA Type Editor, you can generate the AS objects, which map the
structure of the blocks in the third-party system. They contain:
• Tags, possibly with addresses
• Enumerations
• Alarms and messages
• Attributes
• Runtime scripts

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 11
 3 Basic principles

You can start the Editor via the shortcut menu of an AS node in the DBA by
selecting the "Edit AS Object Types..." item.
You will find detailed information in the "PCS 7 Open OS DBA Type Editor"
manual. The manuals are copied to your system during the OPEN OS installation.

Figure 3–4
© Siemens AG 2014 All rights reserved

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 12
 4 Configuring an S7-1500 package unit

4 Configuring an S7-1500 package unit

The following chapters describe how to integrate an S7-1500 PU into PCS 7 using
OPEN OS. The SIMATIC project used in the example is provided solely for
purposes of demonstration. However, the basic procedure for real package units
with S7-1500 controllers is largely identical.

Figure 4–1
© Siemens AG 2014 All rights reserved

In order to purge a pipe system, a tank is filled with water and the water is then fed
into the pipe system. A maximum level and a minimum level of the tank can be
predetermined for the purging sequence.
The sequence places the valves and motors in automatic mode and controls them
until the purging process is complete. The actuators are then switched into manual
mode again.

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 13
 4 Configuring an S7-1500 package unit

4.1 Acquiring data

This example project contains the following components, which are relevant for
operation and monitoring at the OS:

Table 4–1
Type Name AS address Description
Motor MOT1 DB100, DBB0 Pump drive for filling the tank
Valve VAL1 DB100, DBB12 Tank intake valve
Analog P1001 DB101, DBB40 Tank intake pressure transducer
Analog F1001 DB101, DBB80 Tank intake flow sensor
Motor MOT2 DB100, DBB2 Pump drive for emptying the tank
Valve VAL2 DB100, DBB14 Tank drain valve
Analog P2001 DB101, DBB120 Tank drain pressure transducer
Analog F2001 DB101, DBB160 Tank drain flow sensor
Analog L1001 DB101, DBB0 Tank level
Sequenc SFC1 DB400, DBB0 Sequence for purging the pipelines
e
© Siemens AG 2014 All rights reserved

The object types motor, valve and analog value are always based on the same
function block. This makes it possible to derive a structure from the instance DB of
a block.

Motor block
The following motor block variables are required for configuring the OS:

Table 4–2
Tag Type DB Offset Type Description
MAN_ON BOOL 0.0 IN Start motor manually
MAN_OFF BOOL 0.1 IN Stop motor manually
AUTO_ON BOOL 0.2 IN Start motor in automatic mode
MAN BOOL 0.3 IN Manual mode
AUTO BOOL 0.4 IN Automatic mode
FB BOOL 0.5 IN Motor feedback signal
RESET BOOL 0.6 IN Reset of a feedback error
QSTART BOOL 0.7 OUT Signal for starting the motor
QAUTO BOOL 1.0 OUT Automatic mode active
QMAN BOOL 1.1 OUT Manual mode active
QMOTRUN BOOL 1.2 OUT Motor running
QOPCOND BOOL 1.3 OUT Operating condition
QERR BOOL 1.4 OUT Motor feedback error
The time limit for the block to report a feedback error is permanently set to 5
seconds.

Valve block
The following valve block variables are required for configuring the OS:

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 14
 4 Configuring an S7-1500 package unit

Table 4–3
Tag Type DB Type Description
Offset
MAN_OPEN BOOL 0.0 IN Open valve manually
MAN_CLOSE BOOL 0.1 IN Close valve manually
AUTO_OPEN BOOL 0.2 IN Open valve in automatic mode
MAN BOOL 0.3 IN Manual mode
AUTO BOOL 0.4 IN Automatic mode
FB_OPEN BOOL 0.5 IN Open valve feedback signal
FB_CLOSE BOOL 0.6 IN Close valve feedback signal
RESET BOOL 0.7 IN Reset of a feedback error
QOPEN BOOL 1.0 OUT Signal for opening the valve
QAUTO BOOL 1.1 OUT Automatic mode active
QMAN BOOL 1.2 OUT Manual mode active
QVALOPEN BOOL 1.3 OUT Valve open
QOPCOND BOOL 1.4 OUT Operating condition
QERR BOOL 1.5 OUT Valve feedback error
The time limit for the block to report a feedback error is permanently set to
5 seconds.
© Siemens AG 2014 All rights reserved

Analog value monitoring

The following analog block variables are required for configuring the OS:

Table 4–4
Tag Type DB Type Description
Offset
VALUE REAL 0.0 IN Process value
AL REAL 4.0 IN Lower alarm limit
WL REAL 8.0 IN Lower warning limit
WH REAL 12.0 IN Upper warning limit
AH REAL 16.0 IN Upper alarm limit
OUT_AL BOOL 20.0 OUT Lower alarm limit reached
OUT_WL BOOL 20.1 OUT Lower warning limit reached
OUT_WH BOOL 20.2 OUT Upper warning limit reached
OUT_AH BOOL 20.3 OUT Upper alarm limit reached
MLH REAL 22.0 IN Maximum value
MLL REAL 26.0 IN Minimum value
UNIT STRING [8] 30.0 IN Process value unit

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 15
 4 Configuring an S7-1500 package unit

Block sequence
The following block sequence variables are required for configuring the OS:

Table 4–5
Tag Type DB Type Description
address
START BOOL 0.0 IN The sequence is started.
STOP BOOL 0.1 IN The sequence is stopped.
CYCLE BOOL 0.3 IN The sequence runs in a continuous loop

4.2 Generating OS block icons and faceplates

You can generate OS block icons and faceplates with the aid of the WinCC
Graphics Designer. The process conforms to the PCS 7 standard. For this reason,
the topic is not discussed in greater detail in this documentation. Detailed
information on the generation of user-defined icons and faceplates can be found
in the "SIMATIC Process Control System PCS 7 APL Style Guide" manual in the
following article:
https://support.industry.siemens.com/cs/ww/en/view/65601446
© Siemens AG 2014 All rights reserved

Use the collected data to generate the block icons and faceplates. Taking into
consideration the naming conventions for Typicals pictures, use a meaningful
name for the icon picture, e.g. "@S71500_Typicals.pdl".

Note When creating the block icons, please bear in mind the correct labeling for the
object name. E.g., for the "S7MEAS" block, the object name for the associated
block icon is "S7MEAS/1".

In the present example, these are the blocks for:

• Motor
• Valve
• Analog value
• SFC (no faceplates)

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 16
 4 Configuring an S7-1500 package unit

Figure 4–2

One faceplate set each was created for the motor, valve and analog value icons.
The block icon for the sequence does not have a faceplate.

Figure 4–3
© Siemens AG 2014 All rights reserved

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 17
 4 Configuring an S7-1500 package unit

4.3 Generating the AS node with the AS Node Type Wizard

The AS node type is generated with the aid of the PCS 7 DBA AS Node Type
Wizard. You can find the editor in the Start menu at: "Start > Siemens Automation
> AS Node Wizard".
The AS node type is not part of a specific DBA project and is therefore stored in
the installation directory of OPEN OS. You can use all the created AS node types
in each of your DBA projects. The following sections explain how to create an AS
node type.

4.3.1 General tab

In the "General" tab, you assign the name of the AS node type and define the
name of the typical picture from which the OS block icons are copied during
compilation.
1. Enter the name for the AS node type.
2. Enter the name of the WinCC screen that contains the generated picture
symbols.

Figure 4–4
© Siemens AG 2014 All rights reserved

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 18
 4 Configuring an S7-1500 package unit

4.3.2 Instance Source tab

This document only describes the DBA Integrated Instances option.

1. Select the DBA Integrated Instances option.

Figure 4–5
© Siemens AG 2014 All rights reserved

You can find a description of the use of XML instances in the following article:
"How do you create an XML input file for automatic creation of instances in DBA?"
(Entry ID: 78032500).

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 19
 4 Configuring an S7-1500 package unit

4.3.3 "Connection" tab

Because the S7-1500 is a SIMATIC product, using the compatible SIMATIC S7-
1200 or S7-1500 channel is a logical choice.
1. Select the Other Channel option.
2. Enter the channel and the channel unit that are used.
3. Enter a permanent connection name or use the following possible tags:
– %SystemName%: The name of the AS node type is used (General tab).
– %ASName%: The name of the AS node is used that is entered in the DBA.
4. Enter the connection string used by WinCC as the initial parameter.

Figure 4–6
© Siemens AG 2014 All rights reserved

The text in the "Channel" and "Channel Unit" fields must be identical to the
corresponding WinCC channel. You can find the necessary inputs in the WinCC
Tag Management. Follow the steps below:
5. Open an existing or new OS project.
6. Open the WinCC Tag Management.
7. Click on "Tag management" with the right hand mouse button and add the new
"SIMATIC S7-1200, S7-1500 Channel" driver.

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 20
 4 Configuring an S7-1500 package unit

Figure 4–7

The "initial parameter" corresponds to the string that WinCC creates for
a connection. If you do not know the exact string syntax, you can read the
parameter out of WinCC. Proceed as follows:
8. Open an existing or new OS project.
9. Open the WinCC Tag Management.
10. In the desired channel unit, temporarily create a new connection with the
desired connection parameters (it can be deleted later).

Note Since the existing access points might be used by other channels, it is advisable
to create a new access point for the TCP/IP protocol for the S7-1500 channel in
the SIMATIC NET "Communications settings" editor.
© Siemens AG 2014 All rights reserved

11. Select the created access point in the "New Connection" window.

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 21
 4 Configuring an S7-1500 package unit

Figure 4–8
© Siemens AG 2014 All rights reserved

12. Use the option button next to the text field for the initial parameter to start the
WinCC Connection String Inspector. It is vital that the WinCC project with the
corresponding connections is open. Otherwise, no connections will be
displayed.

Figure 4–9

13. In the event that multiple connections are available, select the appropriate
connection and click OK in the dialog window to confirm the selection.
14. Do not delete the temporary connection yet. You will need it again at a later
point to determine the address syntax.

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 22
 4 Configuring an S7-1500 package unit

4.3.4 Addressing tab

In the Addressing tab, you can specify the structure of the AS and variable
addressing that will be used when the project is compiled at a later point.
The address structure depends on the communications driver that is set.
Here, the DBA offers the option of assigning parameters for all conceivable
constellations. These range from a structured approach and the free assignment
of addresses for all tags, to the use of scripts that can calculate the addresses
individually.

The following tags are available for the assignment of ASO address parameters:
• %ASName% – name of the AS type
• %ASOName% – name of the AS instance
• %Instance% – assigned during instantiation
• %Attribute:Name% – value of the specified attribute
• %UID% – unique identifier generated by the DBA

The following tags are available for the assignment of variable address parameters:
• %ASName% – name of the AS type
• %ASOName% – name of the AS instance
© Siemens AG 2014 All rights reserved

• %Instance% – assigned during instantiation

• %Tagname% – name of the tags for which the address is calculated
• %Address% – value of the address field of the tags
• %Field#TagAddress% – value of the extended attribute. Input during
parameter assignment
• %Attribute:Name% – value of the extended attribute with the name "Name"
• %UID% – unique identifier generated by the DBA
• %OPCDataType% - OPC data type number for the tag type
• %UANamespace% - OPC UA adress namen space
• %UAType% - OPC UA identifier type
• %UAValue% - OPC UA identifier

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 23
 4 Configuring an S7-1500 package unit

Special features when addressing an S7-1500 PU

Access by the PCS 7 OS to S7-1500 DBs basically only functions if the "Optimized
block access" attribute is deactivated in the TIA project (Figure 4–10). Otherwise it
is not possible to recognize which data are in which area of the corresponding DB.

Figure 4–10
© Siemens AG 2014 All rights reserved

Note also that when an S7-1500 CPU is used, the tag addresses in WinCC and in
the SQL database are different. DBA must create the addresses as they appear in
the SQL database.
Proceed as follows to read the correct address from the SQL database:
1. Create a temporary connection in the WinCC tag manager or use the
temporary connection from chapter "4.3.3 "Connection" tab".
2. Create a new structure with at least one element.
3. Generate an instance of the structure and select the temporary connection.

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 24
 4 Configuring an S7-1500 package unit

4. In the "Address" field you can see the syntax of the tag connection in WinCC
(Figure 4–11).

Figure 4–11

5. Open the "Microsoft SQL Server Management Studio".

© Siemens AG 2014 All rights reserved

6. In your corresponding WinCC project, click on "Select Top 1000 Rows" in the
context menu for the "dbo.MCPTCONNECTION" table.
You can read the "CONNECTIONID" for the S7-1500 connection from the
results table (Figure 4–12).

Figure 4–12

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 25
 4 Configuring an S7-1500 package unit

7. Select the command "Select Top 1000 Rows" from the context menu for the
"dbo.MCPTVARIABLEDESC" table.
At the end of the "SELECT TOP 1000" script, insert the following syntax
with the CONNECTIONID just determined in Step 6 (in our example: 14),
(Figure 4–13): where CONNECTIONID like ‘14‘
8. When the "Execute" button is clicked, the entries in the results table will be
filtered according to the CONNECTIONID and you will be able to see the
address of the S7-1500 structure in the "ADDRESSPARAMETER" column
(Figure 4–13):
0001:CL:%DBxxx.%Dxxx

Note You will need this addressing syntax for any unstructured program design in the
S7-1500 PU (see further on in this chapter).
For the structured program design in the S7-1500 PU in this example we will use
a script to calculate the correct tag addresses.

Figure 4–13
© Siemens AG 2014 All rights reserved

CAUTION The PCS 7 OS project can be damaged

Only use the SQL database and filtering options to check the tag addresses.
Do not make any changes to the database and use only reading operations.

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 26
 4 Configuring an S7-1500 package unit

Structured program design in the S7-1500 PU

In this example, the S7-1500 program of the PU is designed in a structured
manner. There exist structure objects from which instances which interact with the
field have been created. These structure objects are defined as data types (UDT)
(Figure 4–14), which communicate with the PCS 7 OS by means of data blocks.
These data blocks reproduce the structure of the data types and the addresses
of the tags can be precisely calculated from the offset of the structure address
(Figure 4–15).

Figure 4–14
© Siemens AG 2014 All rights reserved

Figure 4–15

In this case, based on the structure of the object, the offset in the DB and the
various data types of the tags, the addresses of the individual tags can be
automatically calculated using scripts.
Then only the DB number and the offset of the structure within the DB are entered
for the definition of instances (Figure 4–16).

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 27
 4 Configuring an S7-1500 package unit

Figure 4–16

The scripts for calculating the tag addresses must be contained in the AS node
types in DBA. They are only run for the definition of the ASO instance or during an
updating run of the AS objects, and do not appear in the OS runtime.

Note Scripts in this context are a later topic. They will not be dealt with here, rather
only their effects will be considered.

1. Enter the following syntax in the AS object instance address text field:
%@@CalcS71500ASOAddr(„%Instance%“)@@%
© Siemens AG 2014 All rights reserved

2. Enter the following syntax in the tag address text field:

%@@CalcS71500Addr(oTag,“%Instance%“,“%Address%“)@@%

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 28
 4 Configuring an S7-1500 package unit

Figure 4–17
© Siemens AG 2014 All rights reserved

Here, the labels "CalcS71500ASOAddr" and "CalcS71500Addr" are the names

of the two scripts which calculate exactly the addresses of the tags.
These scripts can be found in Chapter "6 A". Copy these into the corresponding
script file for your AS node type. The scripts can be inserted at the end of the script
file, in the "USER DEFINED FUNCTIONS" area.
The script file can be found in the following directory:
"C:\Program Files (x86)\SIEMENS\DBA\<Name of AS node type>\<Name of
AS node type>Scripts.txt"
In our example:
„C:\Program Files (x86)\SIEMENS\DBA\S71500\S71500Scripts.txt“

Without going into the details of these scripts, it is possible to see the result in the
WinCC tag manager after successful configuration (Figure 4–18). It can be seen
that, based on the DB offset value of 0 entered during the instance definition
(Figure 4–16), the byte offset for each tag has been calculated and entered as
an address.

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 29
 4 Configuring an S7-1500 package unit

Figure 4–18

Note Note that the addresses in WinCC and in the SQL database are different.
With the aid of the scripts, DBA creates the addresses just as they appear in the
SQL database (e.g., "0001:CL:%DB101.%DD16"). They are then automatically
displayed correctly in WinCC (e.g., "DB101,DD16").
In cases where the address syntax in your SQL database differs from our
example, you must adapt the scripts at the appropriate points ("sAddr" tag).
© Siemens AG 2014 All rights reserved

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 30
 4 Configuring an S7-1500 package unit

Unstructured program design in the S7-1500 PU

If the S7-1500 program to be integrated has been created in an unstructured
manner and no rules for addressing can be derived, you can set the parameters
for the addresses of all the tags when an instance is being created.
1. Enter the following syntax in the AS object instance address text field
(Figure 4–19):
0001:CL:%Instance%

Note With this setting, the address must be entered as follows when creating an
AS object in DBA at a later time (Chapter "4.6 Creating ASO instances"):
%DBxxx.%Dxxx.
© Siemens AG 2014 All rights reserved

2. Enter the following syntax in the tag address text field (Figure 4–19):
0001:CL:%DBNum#TagAddress%.%DBOffset#TagAddress%

Note With this setting, a new "Address" tab with the columns TagName, DBNum and
DBOffset is available when you assign the ASO instance parameters at a later
time. Here, you can individually assign the address parameters for each tag

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 31
 4 Configuring an S7-1500 package unit

Figure 4–19
© Siemens AG 2014 All rights reserved

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 32
 4 Configuring an S7-1500 package unit

4.4 Creating the AS node

All the created AS node types are stored in the OPEN OS system folder.
From these AS node types, you can now create instances in DBA that map the
controllers of the third-party system.
Once you have generated the AS node type, you can then create the AS node in
the DBA.

1. Open a new or existing project in DBA.

2. In the "AS View" tab of the component view, add a new AS node.
Select the "Add AS Source Node..." command in the shortcut menu.
3. Select the AS node type that was generated.

Figure 4‑20
© Siemens AG 2014 All rights reserved

4. Assign a name for the station.

5. Depending on the setting that was chosen during the generation of the AS
node type, you may still be able to adjust the connection name and the
addressing.

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 33
 4 Configuring an S7-1500 package unit

Figure 4–21
© Siemens AG 2014 All rights reserved

The new AS node has now been crated in the DBA AS View.

4.5 Generating AS object types

The AS object types in the DBA map the function blocks from the AS. An ASO type
can be instantiated in the DBA as often as needed. Changes made to a type effect
all instances of the type. The following steps use a block for an analog value
measuring point to demonstrate how to generate this type. These tasks should
then be carried out for all required blocks.
The data established in the chapter "4.1 Acquiring data" are the basis for
generating the ASO types.
An ASO type can contain the following objects:
• Tags (type and address)
• Messages (message text, triggering event, accompanying values)
• Enumerations
• Attributes
• Runtime scripts
Start the DBA Type Editor by selecting the "Edit AS Object Types..." command
from the AS node shortcut menu.

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 34
 4 Configuring an S7-1500 package unit

Figure 4–22

Note The AS object parameters are assigned for an AS node but are project specific.
If you wish to reuse the objects in another DBA project, which uses the same AS
node type, you can use the Export/Import function for ASO types.
© Siemens AG 2014 All rights reserved

Some attributes and tags in DBA must be added to the AS objects so that the third-
party system objects behave like PCS 7 objects at a later stage. For this, the
following types have already been created by default in DBA:
• AlarmGroupDisplaySupport
• CommonMembers
• SymbolAndFaceplateExtendedAttributes

These types introduce tags or attributes which are required for managing alarms
or for managing block icons or faceplates. They can be included in any type that
these functionalities are intended to work with.

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 35
 4 Configuring an S7-1500 package unit

Figure 4–23

The following sections contain more detailed descriptions of the "Variables,

Messages, Attributes, Includes, Docs and OS Runtime" tabs. In the "Docs" tab you
can link descriptions to your types in HTML format, and in the "OS runtime" tab you
can add scripts for the OS runtime. You can find more detailed information about
this topic in the "PCS 7 Open OS DBA Type Editor" manual.
© Siemens AG 2014 All rights reserved

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 36
 4 Configuring an S7-1500 package unit

4.5.1 Creating a new type

To create a new type in the DBA Type Editor, click the "Add New Type" button.
The dialog window that is then displayed prompts you to enter the following data:
• AS Type Name – Choose a name that creates a relation to the object in
the AS.
• HMI Type Name – Choose the same name that you assigned for the HMI
symbol. It is recommended additionally to work in a reference to the name of
the third-party system.

Figure 4–24
© Siemens AG 2014 All rights reserved

4.5.2 Including default types

With type inclusion, it is possible to add variables and attributes to the new types
to achieve specific functionalities.
The following types are included by default:
• CommonMembers
• SymbolAndFaceplateExtendedAttributes

All available types are displayed in the left-hand window. The right-hand window
contains the types that are already included. If the block also features an alarm
function, include the "AlarmGroupDisplaySupport" type.
1. Select the "AlarmGroupDisplaySupport" type in the left-hand window.
2. Include the type by clicking the button (right arrow).

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 37
 4 Configuring an S7-1500 package unit

Figure 4–25

The new type is now equipped with the basic functionality for PCS 7 blocks.
You can remove the functionality of the included types by clicking the "Left arrow"
button.
© Siemens AG 2014 All rights reserved

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 38
 4 Configuring an S7-1500 package unit

4.5.3 Creating tags

The tags form the interface between the OS and the automation system.
You can configure the tags in the "Tags" tab in the DBA Type Editor.

Figure 4-26
© Siemens AG 2014 All rights reserved

To add new tags, click the "Add" button. An additional dialog window is opened.
In the "General" tab, you can enter the following data:
• Name of the tag
• Data type
• WinCC type (default is structure tag)
• Source (external, internal, indirect)
• Address
• Runtime options
• Inclusion rules

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 39
 4 Configuring an S7-1500 package unit

Use the data type as illustrated in Table 4–6 in the "Address Syntax" column below:
Table 4–6
WinCC data type Address Syntax AS Data Type
Binary D Bit
Unsigned 8-bit DBB Byte
Signed 8-bit DBB Byte
Unsigned 16-bit DBW Word
Signed 16-bit DBW Word
Unsigned 32-bit DD Double word
Signed 32-bit DD Double word
Float 32-bit DD Double word
Float 64-bit DD Double word
Text 8-bit DBB Byte
Text 16-bit DBW Word

The entry in the "Address" field (Figure 4–27) is used in the script referred to in
Chapter "4.3.4 Addressing tab" to calculate the tag addresses automatically.
In the "Advanced" tab, you can configure additional settings for the tag:
• Upper and lower limit
© Siemens AG 2014 All rights reserved

• Start value
• Auxiliary tags (description, unit, ...)
• Archiving

The “DBA Edit” option allows you to customize the specified start values at
instantiation of the type.

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 40
 4 Configuring an S7-1500 package unit

Figure 4–27
© Siemens AG 2014 All rights reserved

Click the "OK" button to close the dialog window and create the type tag.

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 41
 4 Configuring an S7-1500 package unit

4.5.4 Configuring alarms

In the "Messages" tab, you can configure the process messages of the AS block.
The messages can be triggered by different tags or by means of an OPC A&E
server. You can configure the following parameters:
• Alarm name
• Message text
• Message class
• Priority
• Trigger tag
• Associated message values

Figure 4–28
© Siemens AG 2014 All rights reserved

Click "Add" to configure new messages of the ASO type. A dialog with the following
tabs will open:
• General
• Tags
• Process Vars
• Free Vars

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 42
 4 Configuring an S7-1500 package unit

General tab
Assign the following parameters in the "General" tab:
• Name
• Display name
• Message class
• Priority
• Message text

Figure 4–29
© Siemens AG 2014 All rights reserved

Associated message values are integrated using the control commands known
from PCS 7. For example, associated value 2 of the floating-point number type:
@2%3.2f@.
The associated values must be declared in the "Process Vars" tab.

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 43
 4 Configuring an S7-1500 package unit

Tags tab
In the "Tags" tab, the triggering tags for the message in WinCC and the initiating
trigger in the AS are configured.

Figure 4–30
© Siemens AG 2014 All rights reserved

Here you can configure the trigger and optional acknowledge in the controller for
the OS – if the connected third-party system supports this. The message behavior
then corresponds to that of the PCS 7 blocks. Messages are shown in the alarm
group display and in the message line, and the "Loop in Alarm" function can be
used.
With button "fx" any desired terms can be build. Basing of variables and limit
values these terms calculate and – if necessary - activate the trigger of a message.

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 44
 4 Configuring an S7-1500 package unit

Process Variables tab

In this tab, you can configure the tags that you wish to use as associated values in
your message texts. The system provides 10 fields.
You may select any of the tags you created when generating the type.

Figure 4–31
© Siemens AG 2014 All rights reserved

Free Variables tab

In the "Free Tags" tab, you can parametrize constantly recurring text blocks, for
example. You can find further information in the WinCC Alarm Logging description.

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 45
 4 Configuring an S7-1500 package unit

4.5.5 Attributes

The attributes determine the behavior of a tag, a message or the instance of

a type. Most attributes are automatically created during the generation of tags
and messages or copied during the inclusion of other types. It is not necessary
to make changes to these attributes. By default, attributes generated by the
system are not displayed. You can display these attributes by activating the
"Show All Attributes" selection box.

You will find detailed information about the attributes in the "PCS 7 Open OS DBA
Type Editor" manual under chapter 6.5 "Working with the Attribute Editor".

Figure 4–32
© Siemens AG 2014 All rights reserved

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 46
 4 Configuring an S7-1500 package unit

4.6 Creating ASO instances

The ASO types created in the last chapter emulate the structures (UDTs) of
the S7-1500. Using the ASO types, instances will now be generated that emulate
the instances in the data blocks of the AS.
As established in the chapter "4.1 Acquiring data", two motors, two valves,
five analog value measuring points and one sequence (SFC) are used for our
example PU. You can generate these instances by following the steps below:

Open the AS node shortcut menu and select the "Create New AS Object..."
command.

Figure 4–33
© Siemens AG 2014 All rights reserved

Enter the following data in the "Single Instance Editor" dialog window:
• Name of the instance (choose a name that you can associate with the
AS program)
• ASO type
• AS address

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 47
 4 Configuring an S7-1500 package unit

Note The "Address" text box is only available if you defined it when generating the AS
type. In our case, the address string was as follows:

With %Instance%, we specified that the input was to occur in the "Address" field.
By entering the DB number and the DB offset, the correct address can then be
put together.
e.g.: DB100,DBB0 (WinCC) → 0001:CL:%DB100.%DBB0 (SQL database)

The addresses of the individual tags are calculated from the following address
string:

As above, each individual tag address is calculated from the DB number,

the DB offset and additionally the address that was entered in the ASO type
(Figure 4–27).
In the event that you have an unstructured S7-1500 program, take note of
the corresponding paragraph in Chapter "4.3.4 Addressing tab".
© Siemens AG 2014 All rights reserved

Carry out these steps for all required objects.

Figure 4–34

Whenever changes are made to the settings of the AS node, to the related types or
to the created instances, the text "(changed)" is added to the AS node as a note.

Note With the "DBA Object Inspector", you can read out information about which data
was created on the OS. For example, you can already verify whether the
structure of the address syntax is correct.
The command to open the "DBA Object Inspector" can be found in the shortcut
menu of an AS node or an ASO instance.

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 48
 4 Configuring an S7-1500 package unit

By calling the "Update Controller Objects" function from the AS node shortcut
menu, you can update all instances of the AS object.

Figure 4–35

The configuration of the AS part for the S7-1500 package unit is now complete.
© Siemens AG 2014 All rights reserved

The next steps can be found in the chapter "5 Configuring the PC station with the
DBA".

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 49
 5 Configuring the PC station with the DBA

5 Configuring the PC station with the DBA

The PC station in the DBA Editor serves as an interface to the operator system on
which the third-party system is operated and monitored.
To create a PC station in the DBA, you first need a PCS 7 project complete with an
operator station (OS) and a plant hierarchy. This can be a finished project that is
to be expanded to include the functionality of the package unit, or you can create
a new project.

5.1 Adding a PC Station

To create a new PC station in the DBA, follow the steps below:

1. Switch to the "PC Station View" tab.

2. Select the "Add PC Station" command in the DBA project shortcut menu.

Figure 5–1
© Siemens AG 2014 All rights reserved

3. Assign the name of your ES to the PC station.

4. Also add the name of the ES (target OS) at the "Computer Name" line in the
"Value" column.

Figure 5–2

5. Select "Add Application" from the context menu of the PC station. A dialog
window will then open.
6. Select the appropriate project type and click OK in the dialog window to
confirm your selection. Name the application using the name of the
corresponding OS project in the SIMATIC Manager.

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 50
 5 Configuring the PC station with the DBA

Figure 5–3

7. You can link the DBA project to the PCS 7 OS project by entering the path for
the OS project at the "Offline MCP File" line in the "Value" column.
8. By clicking the "..." button you can navigate to the OS project with the aid of
a file selection dialog window and then insert the path string.

Figure 5–4
© Siemens AG 2014 All rights reserved

9. Update the project data in the DBA by selecting the "Refresh OS Cache"
function in the shortcut menu. This function opens the PCS 7 OS project, reads
the alarm classes, alarm types and tag logging archive information, and saves
all of this information in the DBA project.

Figure 5–5

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 51
 5 Configuring the PC station with the DBA

10. Select a Tag Logging archive if one is present.

Figure 5–6

5.2 Creating a plant hierarchy

In the DBA, you can use the plant hierarchy to define the picture hierarchy as it
appears on the OS. It is possible to use and extend an existing hierarchy from
a PCS 7 project or to generate a new hierarchy.
You will find detailed information in the PCS 7 Open OS DBA user manual.
In this example, an existing PH will be extended.
© Siemens AG 2014 All rights reserved

5.2.1 Setting project properties

1. Click the "Change Project Properties" button.

Figure 5–7

2. In the "General" tab, you can define the project and the project path with which
you intend to synchronize the PH. With the "Automatic Synchronize with
Simatic Plant View" option, you can trigger an automatic synchronization
with each compiling operation.

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 52
 5 Configuring the PC station with the DBA

Figure 5–8

3. In the "Hierarchy" tab, you can configure the PH settings. Here, you must
choose the same settings as the ones in the PCS 7 project.

Figure 5–9
© Siemens AG 2014 All rights reserved

4. Click the "OK" button to confirm the settings.

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 53
 5 Configuring the PC station with the DBA

5.2.2 Synchronizing the plant hierarchy

Select the "Synchronize Plant View" command in the DBA project shortcut menu.

Figure 5–10

In this case, the PH is read from the PCS 7 project and created in the DBA, since
© Siemens AG 2014 All rights reserved

no hierarchy was present.

Figure 5–11

5.2.3 Extending the plant hierarchy

You will now extend the loaded hierarchy to include the hierarchy of the third-party
system. By selecting the "Add Folder" command in the shortcut menu, you can
create additional hierarchy folders. Every new folder is automatically assigned an
OS picture with the same name as the folder.
Add additional hierarchy folders according to your plant structure.

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 54
 5 Configuring the PC station with the DBA

Figure 5–12

If you have not enabled automatic synchronizing, you should synchronize the PH
with the OS project again after expanding it in the DBA.

Note PH synchronization can only be used to add folders. If you wish to remove
existing folders, you must delete them in the SIMATIC project and in the DBA.
© Siemens AG 2014 All rights reserved

5.2.4 Assigning hierarchy folders to an OS

If multiple OS projects have been created, it is possible to select a specific OS for

each hierarchy folder. Lower-level hierarchy folders inherit the setting of higher-
level folders.
To assign a hierarchy folder to an OS project, select the "Edit Folder Properties..."
command in the shortcut menu of the relevant folder. In the dialog window that
then opens, you can select an OS project for the chosen PH folder and its
subfolder.

Figure 5–13

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 55
 5 Configuring the PC station with the DBA

5.2.5 Assigning AS object instances

There are various ways to assign the process objects of the automation system to
the PH. The simplest version is to drag-and-drop the objects from the AS View to
the corresponding hierarchy folder.

Figure 5–14
© Siemens AG 2014 All rights reserved

Changes to the plant hierarchy are indicated in the Plant View by a green
background. This means that the OS project still needs to be compiled at a later
point in time.

Figure 5–15

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 56
 5 Configuring the PC station with the DBA

5.2.6 Editing the properties of the objects

After assigning the AS objects to the PH, you can still make changes to a few OS-
relevant settings. For example, a different symbol version can be selected, or
the alarm class can be changed for messages. If, as mentioned in the chapter
"4.3.4 Addressing tab", the addressing parameters of the process variables were
assigned individually, an additional tab labeled "Addresses" will still be present.
In this tab, it is then possible to set the AS address individually for each variable
(Figure 5–16).

Figure 5–16
© Siemens AG 2014 All rights reserved

5.2.7 Compile OS

With the Compile OS function, all objects configured in the DBA (tags, symbols,
messages) are created in the OS project. Click the button with the triangle pointing
to the right:

Figure 5–17

In the dialog window that then opens, you can still configure the usual SIMATIC
Manager settings for an entire compilation or the compilation of changes.

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 57
 5 Configuring the PC station with the DBA

Figure 5–18

You can track the progress of the OS compilation in another dialog window. If the
compiling process cannot be executed without errors, you can display the log by
activating the "Show Details" option.

Figure 5–19
© Siemens AG 2014 All rights reserved

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 58
 5 Configuring the PC station with the DBA

5.3 PCS 7 operator station

When you now open the OS project on the Engineering Station, all connections,
tags, messages, process pictures and block icons should be created.

Figure 5–20
© Siemens AG 2014 All rights reserved

5. With the Graphics Designer, open the process pictures that were created using
the DBA. The block icons for the AS objects will have been inserted next to
one another.
6. Draw the process picture according to your requirements and move the block
icons into the desired position.

Figure 5–21

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 59
 5 Configuring the PC station with the DBA

7. In the SIMATIC Manager, execute the "Load OS" function and start the runtime
at the OS server.

Figure 5–22
© Siemens AG 2014 All rights reserved

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 60
 6 Appendix A

6 Appendix A
6.1 Skript „CalcS71500Addr“
Function CalcS71500Addr(ByVal oTag, ByVal sInstAddr, ByVal sTagAddr) 'V2.0
Dim sInstAddrTokens, sTagAddrTokens, sTag, sType, sTagAddrOffsetPart
Dim sDBNum, nDBStartOffset, fDBOffset, sQualifier, nNumDecPlaces
Dim sAddr

sTag = GetAttr(oTag,"Na","")
sType = GetAttr(oTag,"Ty","")

sInstAddrTokens = SPlit(sInstAddr, ",")

sTagAddrTokens = SPlit(sTagAddr, ",")

sDBNum = sInstAddrTokens(0)
nDBStartOffset = CLng(sInstAddrTokens(1))
sTagAddrOffsetPart = SPlit(sTagAddrTokens(0),".")

fDBOffset = CDbl(sTagAddrOffsetPart(0))

If UBound(sTagAddrTokens) > 0 Then

© Siemens AG 2014 All rights reserved

sQualifier = sTagAddrTokens(1)
If Len(sQualifier) = 0 Then
sQualifier = VarTypeToS7Type(sType)
End If
Else
sQualifier = VarTypeToS7Type(sType)
End If

If UBound(sTagAddrTokens) > 1 Then

nNumDecPlaces = sTagAddrTokens(2)
If Len(nNumDecPlaces) = 0 Then
nNumDecPlaces = 0
End If
ElseIf sType = "BIT" Then
nNumDecPlaces = 1
Else
nNumDecPlaces = 0
End If

sAddr = "0001:CL:%DB"
sAddr = sAddr & sDBNum
sAddr = sAddr & ".%" & sQualifier
sAddr = sAddr & FormatNumber(nDBStartOffset + fDBOffset,0, , ,False)

If nNumDecPlaces > 0 Then

sAddr = sAddr & "." & sTagAddrOffsetPart(1)
End If
CalcS71500Addr = sAddr
End Function

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 61
 6 Appendix A

6.2 Skript „CalcS71500ASOAddr“

Function CalcS71500ASOAddr(ByVal sInstAddr)
Dim sInstAddrToken, sAddr

sInstAddrToken = SPlit(sInstAddr, ",")

'Trace "InstanceAddr[0] : " & sInstAddrToken(0) & " InstanceAddr[1] : "

& sInstAddrToken(1)

sAddr = "0001:CL:%DB"
sAddr = sAddr & sInstAddrToken(0)
sAddr = sAddr & ".%DBB"
sAddr = sAddr & sInstAddrToken(1)

CalcS71500ASOAddr = sAddr
End Function
© Siemens AG 2014 All rights reserved

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 62
 7 Appendix B

7 Appendix B
7.1 Service and support
Industry Online Support
Do you have any questions or need assistance?
Siemens Industry Online Support offers round the clock access to our entire
service and support know-how and portfolio.
The Industry Online Support is the central address for information about our
products, solutions and services.
Product information, manuals, downloads, FAQs, application examples and videos
– all information is accessible with just a few mouse clicks:
support.industry.siemens.com

Technical Support
The Technical Support of Siemens Industry provides you fast and competent
support regarding all technical queries with numerous tailor-made offers
– ranging from basic support to individual support contracts.
Please send queries to Technical Support via Web form:
support.industry.siemens.com/cs/my/src
© Siemens AG 2014 All rights reserved

SITRAIN – Digital Industry Academy

We support you with our globally available training courses for industry with
practical experience, innovative learning methods and a concept that’s tailored to
the customer’s specific needs.
For more information on our offered trainings and courses, as well as their
locations and dates, refer to our web page:
siemens.com/sitrain

Service offer
Our range of services includes the following:
• Plant data services
• Spare parts services
• Repair services
• On-site and maintenance services
• Retrofitting and modernization services
• Service programs and contracts
You can find detailed information on our range of services in the service catalog
web page:
support.industry.siemens.com/cs/sc

Industry Online Support app

You will receive optimum support wherever you are with the "Siemens Industry
Online Support" app. The app is available for iOS and Android:
support.industry.siemens.com/cs/ww/en/sc/2067

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 63
 7 Appendix B

7.2 Industry Mall

The Siemens Industry Mall is the platform on which the entire siemens Industry
product portfolio is accessible. From the selection of products to the order and the
delivery tracking, the Industry Mall enables the complete purchasing processing –
directly and independently of time and location:
mall.industry.siemens.com

7.3 Literature

Table 7–1
Subject area Title
© Siemens AG 2014 All rights reserved

\1\ Siemens Industry https://support.industry.siemens.com

Online Support
\2\ Article download https://support.industry.siemens.com/cs/ww/en/view/49740087
page
\3\ SIMATIC PCS 7 in https://support.industry.siemens.com/cs/ww/en/view/63481413
Industry Online
Support
\4\ Product information https://support.industry.siemens.com/cs/ww/en/view/109750265
PCS 7/OPEN OS
\5\ Doenload https://support.industry.siemens.com/cs/ww/en/view/109781622
PCS 7/OPEN OS
V9.0 Update 1
\6\ SIMATIC PCS 7 https://support.industry.siemens.com/cs/ww/en/view/65601446
APL Style guide

7.4 History

Table 7–2
Version Date Change
V1.0 09/2014 First edition
V1.1 07/2018 Correction in script "CalcS71500Addr"
V1.2 06/2021 Update to PCS 7/OPEN OS V9.0 and further correction in
Script "CalcS71500Addr"
V1.3 09/2021 Fixing an error in chapter 6

Integration of S7-15000 PU with OPEN OS

Entry-ID: 49740087, V1.3, 09/2021 64