Siemens

Industry
Online
Support

APPLICATION EXAMPLE

Accessibility of
Services in connected
MTP Units from PCS 7
SIMATIC PCS 7 V9.1 SP2 / PCS 7 Open OS / PCS 7 DBA / MTP Services Accessibility
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 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 under https://www.siemens.com/cert.

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 2

 Table of contents

Table of contents
1. Introduction ...................................................................................................................................6

1.1. Overview ......................................................................................................................................................6

1.2. Supported versions of the MTP Specification ..................................................................................................6
1.3. Components used .........................................................................................................................................7

2. Installation.....................................................................................................................................8

2.1. Prerequisites .................................................................................................................................................8

2.2. Location of the Components .........................................................................................................................8

3. Communication Concept .................................................................................................................9

3.1. Embedding of Open OS into the HMI Engineering Workflow ...........................................................................9

3.2. Additional Components for the Integration of PEA Services ........................................................................... 11

4. MTP Integration Workflow ............................................................................................................13

4.1. The Classic MTP Integration ......................................................................................................................... 13

4.1.1. Preliminary Preparations.............................................................................................................................. 13
4.1.2. Link to the OS Project .................................................................................................................................. 14
4.1.3. Preparation for the Synchronization of the Technological Hierarchy .............................................................. 16
4.1.4. Preparation for the Multiple Integration of an MTP-Module ........................................................................... 18
4.1.5. Integration of an MTP-Unit .......................................................................................................................... 19
4.1.5.1. Preparing the Technological Hierarchy ........................................................................................................ 19
4.1.5.2. Defining a suitable Controller Object ........................................................................................................... 19
4.1.5.3. Updating the Type Set of the Project ........................................................................................................... 22
4.1.5.4. Integrating the AS Objects .......................................................................................................................... 23
4.2. How to link PCS 7 Control to the MTP Services .............................................................................................. 25
4.2.1. Proxy Function Blocks in CFC ....................................................................................................................... 26
4.2.2. The Task of the Open OS Data Marshalling ................................................................................................... 27
4.2.3. Connection Tags in DBA Service Types ......................................................................................................... 27
4.2.4. Addressing of the indirect tags .................................................................................................................... 28
4.2.4.1. Harmonizing Naming Conventions ............................................................................................................. 29
4.2.4.2. Linking PCS 7 Controller Program and PEA Program ..................................................................................... 30
4.3. Finalizing the MTP Integration Workflow ...................................................................................................... 35

5. Block Description..........................................................................................................................37

5.1. Service Block Icons and their Faceplates ....................................................................................................... 37

5.1.1. Service Control Family ................................................................................................................................. 37
5.1.1.1. Block Icon .................................................................................................................................................. 37

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 3

 Table of contents

5.1.1.2. Faceplate................................................................................................................................................... 37
5.1.1.3. Tags of the Type to be transferred by the Open OS Data Marshalling ............................................................ 38
5.1.2. Service Parameter Family ............................................................................................................................ 39
5.1.2.1. Analog Service Parameter ........................................................................................................................... 39
5.1.2.2. Binary Service Parameter ............................................................................................................................ 41
5.1.2.3. Double Integer Service Parameter ............................................................................................................... 42
5.1.2.4. String Service Parameter ............................................................................................................................ 43
5.1.3. ProcessValueIn Family ................................................................................................................................. 45
5.1.3.1. Analog ProcessValueIn ............................................................................................................................... 45
5.1.3.2. Binary ProcessValueIn ................................................................................................................................ 46
5.1.3.3. Double Integer ProcessValueIn ................................................................................................................... 47
5.1.3.4. String ProcessValueIn ................................................................................................................................. 48
5.1.4. ProcessValueOut Family .............................................................................................................................. 48
5.1.4.1. Analog ProcessValueOut ............................................................................................................................ 49
5.1.4.2. Binary ProcessValueOut .............................................................................................................................. 50
5.1.4.3. Double Integer ProcessValueOut ................................................................................................................. 50
5.1.4.4. String ProcessValueOut .............................................................................................................................. 51
5.1.5. ReportValue Family ..................................................................................................................................... 52
5.1.5.1. Analog ReportValue ................................................................................................................................... 52
5.1.5.2. Binary ReportValue..................................................................................................................................... 54
5.1.5.3. Double Integer ReportValue........................................................................................................................ 55
5.1.5.4. String ReportValue ..................................................................................................................................... 56
5.2. Service Block Interfaces ............................................................................................................................... 57
5.2.1. Service Control ........................................................................................................................................... 57
5.2.1.1. Block Interface ........................................................................................................................................... 57
5.2.1.2. Additional Functionality ............................................................................................................................. 58
5.2.2. Procedure Parameter ................................................................................................................................... 60
5.2.2.1. AnaServParam (Analog) ............................................................................................................................. 60
5.2.2.2. DIntServParam (Double Integer) ................................................................................................................. 61
5.2.2.3. BinServParam (Binary) ................................................................................................................................ 61
5.2.2.4. StringServParam (String) ............................................................................................................................ 62
5.2.3. Process Values ............................................................................................................................................ 62
5.2.3.1. Analog Input AnaPVIn ................................................................................................................................ 62
5.2.3.2. Double Integer Input DIntPVIn .................................................................................................................... 62
5.2.3.3. Binary Input BinPVIn ................................................................................................................................... 63
5.2.3.4. String Input StringPV .................................................................................................................................. 63
5.2.3.5. Analog Output AnaPVOut ........................................................................................................................... 63
5.2.3.6. Double Integer Output DIntPVOut ............................................................................................................... 63
5.2.3.7. Binary Output BinPVOut ............................................................................................................................. 64
5.2.3.8. String Output StringPVOut ......................................................................................................................... 64
5.2.4. Report Value ............................................................................................................................................... 64
Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 4
 Table of contents

5.2.4.1. Analog AnaReportValue ............................................................................................................................. 64

5.2.4.2. Double Integer DIntReportValue ................................................................................................................. 64
5.2.4.3. Binary BinReportValue ................................................................................................................................ 65
5.2.4.4. String StringReportVal ................................................................................................................................ 65

6. Appendix .....................................................................................................................................66

6.1. Service and support .................................................................................................................................... 66

6.2. Links and literature ..................................................................................................................................... 67
6.3. Change documentation ............................................................................................................................... 67

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 5

 Introduction

1. Introduction
1.1. Overview
The Module Type Package (MTP) technology according to the VDI/VDE/NAMUR 2658 standard defines interfaces and
modelling rules allowing for convenient package unit integration. In this standard as well as in this application note, the
package units or modules are referred to as Process Equipment Assemblies (PEA). Using the Module Type Packages (MTP)
technology, PEAs can easily be integrated into a Process Orchestration Layer (POL). Both SIMATIC PCS neo and SIMATIC
PCS 7 give you everything on the hand to implement a smart and high-performance POL. Within SIMATIC PCS 7, the
central component for the PEA integration is the OS with the option SIMATIC PCS 7/Open OS.
Since September 2023, the MTP technology is maintained and developed by NAMUR, ZVEI, and PI. New versions of the
MTP Specification will be released with a new document number from NAMUR, ZVEI, and PI. Siemens is actively driving
this standardization. Since the MTP technology is still under development and the MTP Specification might be subject to
changes until the first release from NAMUR, ZVEI, and PI planned in fall 2024, the associated functionalities within
SIMATIC PCS 7/Open OS are sequentially developed. The current version of the product SIMATIC PCS 7/Open OS only
supports functions and features specified in part 1, part 2 and part 3 of the MTP Specification. Access to MTP Services,
their procedures, their parameters, and MTP Process Values as specified in part 4 is not yet available, although SIMATIC
PCS 7/Open OS provides the full basic functionalities for this access.
The aim of this application note and its associated software components is to bridge the time gap until the PCS 7/Open OS
product fully covers the part 4 of the MTP Specification. It does not claim to be a fully certified product but is only an add-
on, delivered “as is”, that has undergone some basic functional tests.
Further, this application note provides objects with a set of faceplates which can operate services and procedures in the
PEA and which form the link between SFCs or SFC Types running in a connected PCS 7 AS. So that at the end of the day,
services and procedures in the PEA can seamlessly be operated from the SFC objects. The SFC objects themselves can
optionally be controlled from SIMATIC BATCH.
Besides the MTP services and procedures, this application note shows how process value interconnections between a PEA
and the PCS 7 AS based on the interfaces specified in the ProcessValueSet of the MTP specification part 4 can be
implemented in PCS 7/Open OS.
This application note describes the steps for installing the associated software components, the underlying
communication concept, the engineering workflow for integrating services and procedures from PEAs into the HMI and
the SFC/CFC, as well as a brief description of the faceplates supplied.

1.2. Supported versions of the MTP

Specification
The VDI/VDE/NAMUR 2658 standard defines several aspect models. The following documents of the standard are
supported in SIMATIC PCS 7in their respective version.

MTP Description Available Releases Supported MTP

Specification
Aspect Models
Part number

1 General concept VDI/VDE/NAMUR 2658-1:2019 Manifest V1.0.0

and interfaces
VDI/VDE/NAMUR 2658-1:2022 and
(draft)
Manifest V1.1.0 1

2 Modeling of VDI/VDE/NAMUR 2658-2:2019 HMI Set V1.0.0

operator displays

3 Library of data VDI/VDE/NAMUR 2658-3:2020 V1.0.0 2

objects

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 6

 Introduction

4 Modeling of module VDI/VDE/NAMUR 2658-4:2022 ServiceSet V1.0.0

services ProcessValueSet V1.0.0
TextSet V1.0.0

5 Runtime and VDI/VDE/NAMUR 2658-5:2022 General modelling of

Communication (draft) CommunicationSet supported;
proposed profiles are not
supported.

5.1 Runtime and VDI/VDE/NAMUR 2658-5.1:2022 General modelling of

Communication (draft) OPCUAItem supported; proposed
with OPC UA profiles are not supported.

1) The manifest must be modeled either completely based on V1.0.0 or on V1.1.0. It is not acceptable to mix the versions within an MTP.

2) In the released version of VDI/VDE/NAMUR 2658-3, no aspect model is specified. This will only be specified in upcoming versions of the
MTP Specification. To use the monitoring types specified in VDI/VDE/NAMUR 2658-3:2020, e.g. BinMon, AnaMon, the Service Pack 2 of
Open OS V9.1 is required.

Siemens is committed to support official releases of the MTP Specification within the complete MTP portfolio, e.g. within
the Process Function Library, MTP Creator, SIMATIC PCS neo, and SIMATIC PCS 7. These products are tested for
interoperability. Draft versions are only supported selectively and might be discontinued in future product versions. Since
there are no conformance tests specified by NAMUR, ZVEI, and PI yet, we strictly recommend performing interoperability
tests in multi-vendor scenarios.

1.3. Components used

This application example has been created with the following hard- and software components:

Component Article Number

SIMATIC PCS 7 V9.1 SP2 6ES7658-...68-....

SIMATIC PCS 7/Open OS version V9.1 SP1 6EQ2001-…XX68…

Additional software components of the Application Example

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 7

 Installation

2. Installation
2.1. Prerequisites
• Installed PCS 7 version: V9.1 SP2
• Installed PCS 7 / Open OS version: V9.1 SP1

2.2. Location of the Components

Since the software components delivered with this application note are pilot elements, delivered as-is, they do not
provide an installation program. Hence the elements from the different zip files included in the master zip-file “ MTP-
Services-Connectivity-Package.zip “ must be manually unzipped into the respective directories in the Engineering Station
whose name they bear:

C-Program Files (x86)-SIEMENS-DBA-MTP2DBAConverter.zip

→ C:\Program Files (x86)\SIEMENS\DBA\MTP2DBAConverter

C-Program Files (x86)-SIEMENS-WINCC-aplib-OpenOS-MTP.zip

→ C:\Program Files (x86)\SIEMENS\WINCC\aplib\OpenOS\MTP

C-Program Files (x86)-SIEMENS-WINCC-aplib-ScriptLibStd-OpenOS-MTP.zip

→ C:\Program Files (x86)\SIEMENS\WINCC\aplib\ScriptLibStd\OpenOS\MTP

C-Program Files (x86)-SIEMENS-WINCC-Options-PDL-OpenOS-MTP.zip

→ C:\Program Files (x86)\SIEMENS\WINCC\Options\PDL\OpenOS\MTP

Three exceptions exist:

• the content of "GraCS.zip" must be unzipped into the directory GraCS of the OS project being enhanced with the MTP
service functionality.
• the content of "OpenOS_Project.zip" can be unzipped wherever you want, the recommendation would be to put it in
some project related directory next or above the original Open OS project. The XML-file contained in this zip-file brings
all the types required to handle the MTP services and their communication ability to transfer data from the PEA Unit to
a PCS 7 AS and vice-versa. These types must be imported later into the DBA project (cf chapter 4.1.5.3).
• The required PCS 7 Library "MTPService_V1_0.zip", which includes the MTP proxy blocks for the automation system,
can be retrieved as usual with STEP 7 mechanisms. In addition to the blocks, the SCL-Sources are part of the source
section of the library. These can be used to adapt the blocks later if need is.

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 8

 Communication Concept

3. Communication Concept
For a better overview, we start with a short description of the communication concept.

3.1. Embedding of Open OS into the HMI

Engineering Workflow
We begin with the view on the OS in a PCS 7 installation. In a general manner, process data is handled within the OS Data
Manager, which connects through an S7-connection to the PCS 7 controllers in the plant.

The task at hand is to integrate some PEA stations into this OS and to use the embedded services and procedures in these
PEA stations from a SFCs or SFC types in the PCS 7 controller as well as from the operation area of the OS.

The tool for this integration is the PCS 7 option PCS 7/Open OS, which comes with an MTP converter to handle MTP
engineering files describing the content of the PEA stations. It also provides standardized communication channels to the
MTP units through OPC UA.

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 9

 Communication Concept

The converter included in PCS 7/Open OS parses the MTP Engineering file and extracts all relevant data to draw the static
part of the pictures, to create and position the dynamic block icons within the picture, and to create the process data from
the PEA stations in a structured, PCS 7 style way in the Data Manager of the OS.

The creation of the dynamic content is facilitated by the block icon and faceplate library coming by default with Open OS
and the additional service-related block icons and faceplates coming with this application note.

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 10

 Communication Concept

The compilation finalizing this integration process enables the seamless communication between the dynamic objects
i.e., block icons and their associated faceplates, and the control blocks in the PEA station, through the Data Manager and
the OPC UA communication channel.

3.2. Additional Components for the

Integration of PEA Services
All the steps up to here are covered by the current version of the product PCS 7/Open OS. Now follows the description of
the additional enhancements provided by the additional components coming with this application note.

If the PCS 7 controller contains SFCs or SFC types, associated to some Batch process, it could be very interesting to link
these to services and procedures in the PEA stations. As an interface between such SFCs and the PEAs, proxy function
blocks are required within the PCS 7 controller, which can be connected to the different steps and transitions of the SFCs
and interact with the PEA stations through the Data Manager.

These proxy function blocks are provided in a library along with this application note and must be copied into the
respective project. After having them instantiated and connected in due manner, the compilation into the OS creates the
appropriate tags in the Data Manager, which can then be connected as needed to the tags of the PEA, as will be described
later in this document.

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 11

 Communication Concept

Part of the additional components included with this application note is also a set of structure types which can be
imported into the Open OS project. These types have embedded scripting which realizes the Open OS Data Marshalling
shown in the above picture: these scripts copy back and forth the relevant data between the PEA station and the PCS 7
controller. This connection between the different objects in the Data Manager must be defined during the engineering
phase of the Open OS project. It will be explained later in this document.

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 12

 MTP Integration Workflow

4. MTP Integration Workflow

The following description of the integration workflow starts with a general overview of the integration of an MTP Unit
with Open OS. Then the enhancements coming with the additional service-related components will be addressed with
more depth, emphasizing on the additional engineering steps.

4.1. The Classic MTP Integration

Starting point of the MTP integration is an MTP file which describes the content of a PEA Station. Additionally, you’ll need
an OS project as target for the integration. It could be an empty one, but more likely is an existing one, where external
PEA Stations, providing some dedicated services or procedures, should be integrated.

4.1.1. Preliminary Preparations

Start the engineering tool of Open OS, PCS 7 DBA, from the Start button by following Start → Siemens Automation → PCS
7 DBA. Hint: it is good practice to pin it to the task bar for an easier access later.
Create a new project from the menu bar, with File → New Project…

The GUI that opens is divided into 4 panes arranged in 2 levels and 2 sides.
The upper level is the OS level, which handles the desired OS content, the lower level handles the controller level, where
all external controller objects with their included AS Objects are listed.
The left side is always the overview:

• in the OS level it is the technological hierarchy → 1

• in the controller level the list of the connected controllers. → 2

The right side shows the details of a selected object on the left side:

• in the OS level it shows the OS attributes of an object from the technological hierarchy → 3

• in the controller level it shows all the objects coming from the selected controller. → 4

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 13

 MTP Integration Workflow

1 3

2 4

4.1.2. Link to the OS Project

To create the link to the associated OS-Project, open the PC Station View tab…

… and after a right mouse click into the controller overview area (pane 2) …

… add a PC station by clicking on the available context menu item.

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 14

 MTP Integration Workflow

Result:

Enter the computer name of the OS Server and, best practice for a better overview, rename the PC Station node to the
same PC name.

Now, after a right mouse click on the PC station, select "Add Application" from the context menu.

Select the Application Type PCS 7 OS (Server/Single Station)

Use the 3-dots button in the value field of the "Offline MCP File" to navigate to the MCP project file of the related OS
project.

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 15

 MTP Integration Workflow

Make sure that the name of the OS node in the left pane is the same as the MCP filename, otherwise the later plant
hierarchy synchronization won’t work properly.

4.1.3. Preparation for the Synchronization of the

Technological Hierarchy
In case that you want to enhance an existing project, you can import the existing Technological Hierarchy of this project
and new branches or add objects to existing branches. This is done in the project properties, opened via File →
Properties…

… or with a click on the corresponding button.

In the project options window, you can browse the available SIMATIC projects on your engineering station and select the
matching one.

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 16

 MTP Integration Workflow

In addition to this you can also enable the Automatic Synchronization with the SIMATIC Plant View, so that a
synchronization is done with each compilation. However, this is not recommended, as changes in the hierarchy do not
happen that often after the first set up, but the synchronization increases considerably the processing time of each
compilation. A better choice is not to enable this option, but to synchronize the Plant View each time a change in the
branch structure has happened. This can be performed at any time manually after a right mouse click in the upper left
pane (pane 1 earlier) and selecting "Synchronize Plant View" from the context menu.

In our example we do not have a technological hierarchy in our Simatic OS project, hence we just create one from scratch.
Now that the preliminary one-time operations are finalized, we continue with the integration of a first MTP unit.
At this point it is good practice to save the current DBA project under a meaningful name and to update this file regularly.

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 17

 MTP Integration Workflow

4.1.4. Preparation for the Multiple Integration of an

MTP-Module
In a modular plant a common use case could be to integrate the same MTP-Unit type several times. One example could be
a fermenter, of which 5 instances shall be installed in the plant. As it is always the same type of fermenter, it is described
by the same MTP file, which will be integrated 5 times into the project. The challenge of it is that we will have several
times (in our example 5 times) the same instance name in the project and hence the uniqueness of each name is not
given.
This can of course also happen in a non-modular plant, and hence PCS 7 provides the possibility to create the uniqueness
of the names by including the name of different technological levels into the name of the instance. The feature is also
available with DBA.
The selection of the level names to be included is done in the Hierarchy tab of the project options:

Just check the level you want to include into the instance name. It is also possible to select more than one level, in case of
a complex plant.
Important notice: This setting must be the same as in the PCS 7 project into which the MTP units will be integrated!

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 18

 MTP Integration Workflow

4.1.5. Integration of an MTP-Unit

4.1.5.1. Preparing the Technological Hierarchy
In a general manner, the workflow for integrating an MTP Unit is always the same, regardless of whether it contains
services or not.
It starts with creating (or importing as described above) a technological hierarchy. This is done, after a right mouse click
on the root of the hierarchy, by selecting “Add Folder” and renaming this new branch to a meaningful name.

You can add any number of folders at any location by right-clicking on the locations under which the new branches are to
be inserted and "Add Folder". Each folder automatically also contains a picture into which the block icons associated to
this folder will be inserted.
Let’s continue our example with the following structure:

4.1.5.2. Defining a suitable Controller Object

The integration of any kind of 3rd party controller, hence also of an MTP Unit, is started with a right mouse click into the
lower left pane (pane 2) …

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 19

 MTP Integration Workflow

… and then by clicking on the available context menu item.

This opens the selection window for AS Node Types. The note type OPCUAServerMTP is the suitable predefined node type
for MTP units and must be selected.

This opens the window where you insert all the relevant AS Properties of the MTP unit representation in DBA.

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 20

 MTP Integration Workflow

In the "General" tab you define the embedding into the project:

• 1: AS Node Name: Name under which the unit will appear in the Controller list in DBA
• 2: MTP File: can be chosen by clicking on the 3 dots button and navigating to it.
• 3: Plant Hierarchy: hierarchy folder, to which the objects of the MTP unit shall be assigned. A click on the 3 dots
button opens a selection window where the folder can be chosen.

In the tab "Connection" you define the communication settings:

• 4: Connection Name is the name under which the connection will appear in the WinCC Tag Management. The default
entry will automatically take the name entered in the field “AS Node Name” in the tab “General”. But it can be adapted
to your needs.
• 5: Connection Parameter is a string that combines all the entries of the connection parameters of the connection in
the WinCC Tag Management.
Hint: as nobody knows such a string by heart, you can create manually a dummy OPC UA connection in WinCC Tag
Management and then copy the settings from the WinCC string by using the 3 dots button on the right. Only
precondition is to have the WinCC project open offline in the background.
The big advantage to copy these settings is, that you just need to adapt the IP address to the correct one of your MTP
Unit!

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 21

 MTP Integration Workflow

After these entries have been completed, the controller object of the MTP Unit appears in the lower left pane (Pane 2).

4.1.5.3. Updating the Type Set of the Project

Before starting the integration of the AS objects from the MTP Unit, the latest type set of DBA must be installed. The
standard Type Set coming with DBA does not support the service functionality of the MTP Unit, if one exists. The
integration process would hence not identify these service objects.
So, at first this Type Set must be imported from the XML-file coming with the software components delivered with this
application note and having been unzipped in some project related directory next or above the Open OS project. This
procedure is a one-time procedure for the project: after having imported these types they can be used by any additional
controller object defined in this project. Creating a new project would require importing these types in the same way into
the new project.

The import is handled within the Type Editor. It is opened with a right mouse click on the controller object and selecting
“Edit AS Object Types…”.

This opens the Type Editor showing the list of the currently available types of the underlying AS type system, in our case
“OPCUAServerMTP”, which was selected earlier during the definition of the controller object (cf. 4.1.5.2).

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 22

 MTP Integration Workflow

After clicking on the “Tools” button, you can select “Import Type(s)…” from the context menu. This opens a window in
which you can navigate to the above-mentioned XML-file containing the new type set: “All_Types.xml”. The window that

opens shows all available types included in this XML-file. For consistency reasons it is best to select them all with the
button. This moves the type selection to the right pane: these are the types that will be imported. A click on the Start
button triggers this procedure, which is started after you confirmed to “Overwrite All”.
Now you can close the Type Editor with the OK button and can start with the integration of the AS object coming from
the MTP file.

4.1.5.4. Integrating the AS Objects

While the controller object appeared in the pane, the MTP file has been parsed in the background and a list of all included
AS objects has been compiled in the background. These AS Objects can now be brought into the DBA project through the
following update procedure: after a right mouse click on the controller object…

… select "Update Controller Objects" from the context menu.

This brings all the identified AS objects into the DBA project. They are now listed in the detail pane (pane 4) of the
selected controller object.

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 23

 MTP Integration Workflow

They all appear with their name and their type. Instances related to Services in the PEA, e.g. Service Control, Parameter
Elements, Process Value Inputs and Outputs, and Report Values are supplemented with the suffix “_SFC” for a better
distinction.
If you are interested in the detailed tags or attributes of one object, you can inspect it with a right mouse click on the
object and selecting "Inspect Object" from the context menu.

This shows all the tags of the object with their address and their start value, as well as all the attributes with their
parameters.
Now that all the objects are incorporated into the DBA project, they must be assigned to the technological hierarchy. This
can of course be done manually, by dragging and dropping the AS objects into the desired technological hierarchy
folders, but as we already defined the location beforehand, this can be done automatically.
This procedure is started by a right mouse click on the controller object and selecting "Auto-Assign Resource to Plant
View".

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 24

 MTP Integration Workflow

The assignment is visible in the detail pane in the column "Assignment" …

… and all assigned objects can now be found in the technological hierarchy folder:

Up to here, the workflow for monitoring and control from the OS would be completed: the user can monitor analog
measurements and binary signals or operate motors, valves, even services, i.e. all dynamic objects from the OS screen. In
this case a compilation of the DBA project can be started right now
In case that the services inside the MTP unit shall also be operated from an SFC or SFC type in the PCS 7 controller,
perhaps even being under control of a Batch unit, some additional engineering work is required to create the link
between the control in PCS 7 and the service parameters and service controls in the MTP unit.

4.2. How to link PCS 7 Control to the MTP

Services
To be able to route the information back and forth between the PCS 7 controller and the MTP unit, the service types in
DBA already come with some internal connection tags and associated scripting. How these must be connected to the
PCS 7 controller program is described below.

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 25

 MTP Integration Workflow

4.2.1. Proxy Function Blocks in CFC

As explained above, the connection parts on MTP side are the different service types in DBA. They need counterparts on
the PCS 7 controller side to exchange data. These Proxy Function Blocks are provided as a small library which must be
integrated into the Simatic project, and they are the interface between the CFC program and the OS. Each service type in
DBA has a matching function block type on the CFC side and needs to be instantiated when needed. The following list
shows the matching pairs Proxy Function Blocks to DBA Service Types and their interface definition in Namur 2658 Part 4:

Interface Definition Proxy Function Block DBA Service Type Comment

Namur 2658 Part 4
AnaProcessValueIn AnaPVIn MTP_SFC_AnaProcessValueIn

AnaProcessValueOut AnaPVOut MTP_SFC_AnaProcessValueOut AnaView

AnaReportValue AnaReportValue MTP_SFC_AnaReportValue AnaView + MissedValueFlag

AnaServParam AnaServParam MTP_SFC_AnaServParam

BinProcessValueIn BinPVIn MTP_SFC_BinProcessValueIn

BinProcessValueOut BinPVOut MTP_SFC_BinProcessValueOut BinView

BinReportValue BinReportValue MTP_SFC_BinReportValue BinView + MissedValueFlag

BinServParam BinServParam MTP_SFC_BinServParam

DIntProcessValueIn DIntPVIn MTP_SFC_DIntProcessValueIn

DIntProcessValueOut DIntPVOut MTP_SFC_DIntProcessValueOut DIntView

DIntReportValue DIntReportValue MTP_SFC_DIntReportValue DIntView + MissedValueFlag

DIntServParam DIntServParam MTP_SFC_DIntServParam

ServiceControl ServiceControl MTP_SFC_ServiceControl

StringProcessValueIn StringPVIn MTP_SFC_StringProcessValueIn

StringProcessValueOut StringPVOut MTP_SFC_StringProcessValueOut StringView

StringReportValue StringReportValue MTP_SFC_StringReportValue StringView +

MissedValueFlag

StringServParam StringServParam MTP_SFC_StringServParam

The ProcessValueOut and ReportValueOut types do not have a dedicated own interface description in the Namur
standard. They have been explicitly created here because in DBA they are View types with additional scripting for the SFC
interfacing and an additional tag "MissedValue" for the Report types. Hence the need to differentiate them from the
standard View types.

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 26

 MTP Integration Workflow

4.2.2. The Task of the Open OS Data Marshalling

The internal Open OS Data Marshalling is needed because an OS tag can only be connected to one channel. Hence it is
not possible to assign a tag to the Named Connection of the S7-channel and to the OPC UA channel. In addition to this
restriction, the OS runtime scripts of the DBA types cannot access directly to tags of other channels. And the OS runtime
scripting is the solution of choice as the scripts are part of the type and are automatically available when instances of the
type are defined, there is no additional manual scripting required.
The solution now is to bring the required tags from the S7-Channel to the DBA Service Types by using indirect tags in the
type, which point to these S7-Channel tags. So, each DBA Service Type has a set of indirect tags for the tags to be
connected, which move the data from or to the S7-Channel. Internal scripts in the DBA Service Type just copy the data
between these connection tags and the external tags connected through the OPC UA channel to the PEA Unit.
These scripts also consider the direction of the data flow, whether the tag information must be transferred from the PEA
unit to the PCS 7 controller or from the PCS 7 controller to the PEA unit. The scripts moving data from the PEA unit to the
PCS 7 controller are triggered on change of the external tags, which minimizes the scripting load, the scripts moving data
from the PCS 7 controller to the PEA unit run cyclically, as indirect tags cannot be monitored on change.

4.2.3. Connection Tags in DBA Service Types

Service parameter types can have an extensive set of tags. But only a few of them are relevant for the operation from an
SFC or SFC-type, all other tags are mostly needed for OS operation. The proxy function blocks in CFC hence only provide
the small set of SFC relevant tags and map them into the OS to minimize data traffic.
On DBA side, only these required tags of the service types have internal connection tags and suitable scripting. The
scripting here is divided into 2 categories:

• scripts copying values from the PEA to the PCS 7 AS are triggered on change, as this is done by the Open OS Runtime
Framework automatically for the OPC UA Channel,
• scripts copying values from the PCS 7 AS to the PEA are triggered cyclically, because it is not possible for the Open OS
Runtime Framework to monitor the S7-channel on change. In smaller installations, a 1 sec. cycle is conceivable, in
bigger ones 2 seconds should do the job. Anyway, the number of copied tags per instance in this direction is very
small.
This minimizes the scripting load in the OS.
These indirect connection tags within a type have the name of their respective PEA tag, supplemented by "Connect", i.e.,
for instance the PEA tag “VExt” in the type has the associated indirect connection tag “VExtConnect”. The value of these
indirect tags is the tag name of the respective tag in the S7 channel.
Additionally, each type has a tag "Connected" with which each instance can be enabled for data transfer to an SFC in a
PCS 7 controller. Instances that do not connect to an SFC, hence do not have target tag names of the S7 channel, should
be disabled from communicating to the S7 channel by setting this "Connected" tag to "0", its default value, because the
script would regularly generate error messages due to the missing tag names of the S7 channel.

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 27

 MTP Integration Workflow

4.2.4. Addressing of the indirect tags

This chapter shows some tips and tricks to make life easy when engineering the connection between a PEA Unit and an
SFC or SFC type. The basic assumption is that the PCS 7 part of the plant is already existing and is now to be
supplemented by an MTP unit. Proxy Function Blocks have not yet been created in the CFC.
The first step of integrating an MTP unit is to bring it, as described above in chapter 4.1, into the DBA project. This results
in a controller object with an appropriate name.

Good practice is now to add a CFC to the SIMATIC project with the same name as this connection object, in our example
“Clean”, where the associated proxy Function blocks will be collected.

Like this, all relevant connection information is on one page. These Proxy Function Blocks can then be connected to the
appropriate data sources in the controller program.
The question of which proxy function blocks must now be inserted is easy to answer: Each service type from the controller
object in DBA needs a counter part in the CFC. This can easily be determined by sorting the instance list of the controller
object alphabetically by Type name.

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 28

 MTP Integration Workflow

The candidates are the types starting with “MTP_SFC”, resp. the instances ending with “_SFC”. Now you just need to place
one suitable proxy function block per instance on the CFC, following the list in chapter 0.

4.2.4.1. Harmonizing Naming Conventions

The naming of these proxy function blocks now stumbles over the naming conventions of different systems. The names
of the instances from the PEA Unit do not know anything of the naming convention of the OS. As the OS does not accept
blanks in an instance name, the blanks are automatically replaced by $-signs during the import of the MTP Unit. This
changes the name of the instances only slightly, but the length of the name remains unchanged. On the other hand, the
length of the names is limited for CFC blocks to 16 characters. So not always the full name of the instances can be used
for the associated proxy function block. But it should be chosen as close as possible.
As an example, the object name from the PEA unit “Vlv next PEA opened” will be transformed to “Vlv$next$PEA$opened”
when importing it into DBA. The name of the associated proxy function block in the CFC must then be shortened to
“Vlv$next$PEA$ope”, due to the limitation to 16 characters.

After all required blocks have been placed and connected within the PCS 7 program, the project can be compiled and
downloaded. A compilation of the OS will create all the required tags in the Data Manager. By the way, it is not
mandatory that these are assigned to the Technological Hierarchy, the only requirement is that the "OCM possible" check
box ix checked.

In the case of non-assignment to the hierarchy, the tag will appear in the data manager including the connection name…

… while in the case of a hierarchy assignment the name of the connection is not part of the OS tag name.

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 29

 MTP Integration Workflow

4.2.4.2. Linking PCS 7 Controller Program and PEA Program

Indirect tags don’t have numeric values, but they have the OS-internal tag address of their target tag in the S7-channel as
value. With this they handle the numeric value of the S7-channel tag in the background.
One helpful feature of indirect tags for bulk-engineering is, that they are handled in DBA as attributes. These attributes
can be exported into a CSV-formatted file, which can easily be edited with Excel.
The following described workflow to generate these OS-internal tag addresses for the indirect tags assumes that:

• In the PCS 7 AS all the Proxy Function Blocks for one PEA are collected in a CFC-chart with the name of the PEA
Controller Object in DBA (cf. above)

• The block names of the Proxy Function Blocks match the instance name of their corresponding instance in DBA
These 2 prerequisites simplify life considerably, as you can now see.

Attribute Export
DBA offers a variety of selections to export attributes. The best one for our use case is the one starting from the controller
object. Open the context menu with a right mouse click on the object and select “Export Attributes…”

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 30

 MTP Integration Workflow

You’ll be prompted to enter a filename and then the export starts.

Structure of the Exported CSV-File

The exported list contains all the attributes of all the instances of the selected controller object. Arrange the column width
for a better legibility.
The important columns for our work are:

• ASTagName: this is the name of the instance,

• Category: this is the category name of the attribute, in our use case here we will look for the category “Indirect Tags”,
• Name: this is the name of the attribute, i.e. the name of the indirect tag.
• Value: this is the value, where the corresponding S7-tag address must be entered.
Now we use the filter function of Excel to filter on all attributes of the category “Indirect Tags”. This selects only the
“Indirect Tags” attributes. Among the indirect tags whose name ends with “#Indirect” we also have the connection enable
tag “Connected”, whose start value “Connected#Start” is also part of the category “Indirect Tags”.
Usually, the number of attributes is very huge, which might slow down the work pace. Hence it is recommended to save
the filtered selection into an empty CSV-file and continue to work with this file. Be careful to keep the original structure of
the file, especially the header line. With this it is possible to only re-import the resulting file after all tag addresses have
been entered, which shortens the import time considerably.

Calculating the S7-Addresses

In this new, smaller file we have collected 2 types of attributes: the attributes for the S7-tag addresses which we must
enter to create the link between the PEA channel and the PCS 7 AS channel, and the start value of the “Connected” tag,
with which we enable the script calculation on a per instance base to move the data back and forth. We first start with the
indirect tags; hence we filter the file for all attributes containing “#Indirect” in their name. This hides the “Connected” tags
for the moment.
Unfortunately, the Proxy Function Blocks bring a few additional tags with them, which we do not necessarily need.
Additionally, the block name length limitation in CFC does not always allow to find all matches between Proxy Function
Blocks tags and PEA tags. Hence this short description, which shows an easy approach to calculate the S7-Channel
addresses with some easy Excel functions and the attribute names.

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 31

 MTP Integration Workflow

First a look into the OS Data Manager shows the syntax to be created. Here you can also see that the naming
recommendations described in 4.2.4.2 simplify life considerably.

OS-channel name because the

Proxy Function Blocks are not Tag name which is the basis for
assigned to a hierarchy. Is the attribute name.
missing, if assigned.

CFC name, identical to the name of the DBA Instance name where the attributes
controller object. This was also the selection belong to (limited to 16 characters due
criteria for the attribute export. Hence these 2 to the block name length).
elements of the address are the same for all
attributes in our CSV-file.

The first 2 elements are constants for all attributes of the list, the latter 2 elements can be picked per attribute of the list.
With this knowledge, it is easy to build the correct address for each attribute.
The correct formula in our case is:
=CONCATENATE("S7-Programm(1)/Clean/";LEFT(A4;16);".";LEFT(D4;FIND("Connect";D4)-1))

constant Instancename, truncated to Tag name without “Connect” and

max. 16 characters appendix.

Result:

And in case of longer tag names, the truncated result:

This was to be achieved:

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 32

 MTP Integration Workflow

Following the preliminary recommendations about naming has simplified this task a lot. Of course, it is also possible not
to follow these naming tips, the work in Excel is then somewhat more extensive, but with Excel everything is possible.
Important at the end of the day is that the addresses and their syntax in the attributes list matches to the target tag
addresses from the S7-channel.
With a simple drag of this formula to all value fields, the correct addresses are calculated.
Now the filter selection can be removed.

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 33

 MTP Integration Workflow

Activating the Scripting for the Instances

To activate the scripting for the instances that connect to the S7-channel you just need to set the attribute
“Connected#Start” of these instances to 1. Depending on the size of the file you can just scroll through it and enter the
value, sort it by name so that all “Connected#Start” attributes are together, or filter for the name “Connected#Start”.
Take care to only enable those instances which have matching counterparts in the S7-channel, i.e. existing tag addresses.

Attribute Import
As mentioned earlier, only the changed attributes can be imported, which reduces the import time considerably in bigger
projects. It is only important that the header line is part of the file and that the separator in the file is the same as in the
exported file.
The import works in the same way as the export earlier: Open the context menu with a right mouse click on the controller
object and select “Import Attributes…”.

Then select the correct CSV-file and start the import.

The result can be checked in the tab "Linked Tags" of the different service instances.

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 34

 MTP Integration Workflow

4.3. Finalizing the MTP Integration

Workflow
When all the steps have been performed, i.e., all objects from the MTP Unit have been created and assigned to the
technological hierarchy, and all required connection information to link PEA and PCS 7 Controller has been entered, then
the DBA project can be brought into the associated OS by compiling it.
The target OS project has been defined in chapter 4.1.2. What is now left is the assignment of the different technologiacal
hierarchy branches to the OS (in our case it is only one, but Open OS can handle more), otherwise the objects in these
branches won’t be compiled.
The settings are opened for each branch of the selected OS area (as defined in the project options) with a right mouse
click on the branch…

… and selecting “Edit Folder Properties…”. The associated OS must be checked in the Folder Properties window.

The compilation can be started when all relevant folders are assigned to an OS. This can be triggered in different ways:

• From the menu bar: Run → Start Compilation

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 35

 MTP Integration Workflow

• From the approriate button in the button bar

• With the F5-key.

Any of these actions opens the Compile Options window, where you can select your needs. The first compilation in a
project is always a full compile (“Entire OS”), all subsequent compilations can be Changes, if the prerequirements are met
(= no changes in the type structures).
“Tags and Messages” should always be checked, “Create/Update Block Icons” can be unchecked if no new instances with
block icon have been added. This shortens compilation time significantly.
“Create Archive Tags” needs only to be checked when there are tags in the types which are archived by default. And only
if new instances with such tags have been added. It does not need to be checked when no archive has been defined.
“Picture Tree” needs only to be checked at the first compilation, later on only if there have been changes in the
Technological Hierarchy.

After the end of the compilation, all tags and structure types can be found in the Tag Management of the OS, all block
icons can be found in their designated pictures where they have been assigned to, and all these pictures can be found in
the picture tree of the OS.

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 36

 Block Description

5. Block Description

5.1. Service Block Icons and their

Faceplates
Among the components delivered with this application note is a set of block icons and faceplates which allow to monitor
and operate the services and parameters in the MTP Unit. These elements are divided into 5 families: Service Control,
Service Parameters, ProcessValueIn, ProcessValueOut, and Report Values.

5.1.1. Service Control Family

This family contains only one object, the Service Control Object, with which a service in the PEA Unit can be monitored
and controlled.

5.1.1.1. Block Icon

1 2 3

The block icon summarizes the current state of the service:

1. Display of the Operation Mode Manual or Automatic
2. Display of the Source Mode Internal or External
3. Display of the current command
4. Display of the current Procedure.

5.1.1.2. Faceplate

1
2
8
3
4
5
6
7

The detailed view of the faceplate shows:

1. Display of the Operation Mode Manual or Automatic, selection possibility via the button

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 37

 Block Description

2. Display of the Source Mode Internal or External, selection possibility via the button

3. Display of the current command, the button opens an additional command window…

… with which the service can be operated.

4. Display of the current active procedure

5. Display of the next selected procedure which will be run with the next start command
6. Selection field for the next procedure. This opens an additional selection window…

… with which the next procedure can be selected. For a better overview, this window is divided into 5 pages
with up to 4 procedure selection buttons on each. Navigation between these pages can be done with the arrow-
buttons or by direct selection via the number button.
The available procedures are represented by a button each. Only buttons for available procedure are shown.

7. Display of the current state of the ReportValueFreeze-Flag

8. Display of the Current State

5.1.1.3. Tags of the Type to be transferred by the Open OS Data

Marshalling
The following tags of the type MTP_SFC_ServiceControl have additional “Connect” tags as described in chapter 4.2.3 and
need input of the target address of the associated tags from the Proxy Function Blocks if a connection to an SFC in a
connected non-modular sub-plant (PCS 7 AS) is required.

Name Direction Datatype

CommandEn POL ← PEA DWORD
CommandExt POL → PEA DWORD
ConfigParam ApplyEn POL ← PEA BOOL
ConfigParam ApplyExt POL → PEA BOOL
ProcedureCur POL ← PEA DWORD
ProcedureExt POL → PEA DWORD
ProcedureReq POL ← PEA DWORD
ProcParam ApplyExt POL → PEA BOOL
ProcParamApplyEn POL ← PEA BOOL
ReportValueFreeze POL → PEA BOOL
SrcExtAct POL ← PEA BOOL
SrcExtOp POL → PEA BOOL
SrcIntAct POL ← PEA BOOL

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 38

 Block Description

SrcIntOp POL → PEA BOOL

StateAutAct POL ← PEA BOOL
StateAutOp POL → PEA BOOL
StateCur POL ← PEA DWORD
StateOffAct POL ← PEA BOOL
StateOffOp POL → PEA BOOL
StateOpAct POL ← PEA BOOL
StateOpOp POL → PEA BOOL
WQC POL ← PEA BYTE

5.1.2. Service Parameter Family

The Service Parameter Family is divided into 4 sub-families, depending on the data type: analog
(MTP_SFC_AnaServParam), binary (MTP_SFC_BinServParam), double integer (MTP_SFC_DIntServParam), and string
(MTP_SFC_StringServParam).

5.1.2.1. Analog Service Parameter

Block Icons
Variant 1 Variant 2

5
1
2

3 4

1. Display of the Feedback Value Variable VFbk

2. Display of the Manual Parameter Value Variable (Prepared SP) VOp
3. Display of the Operation Mode Manual or Automatic
4. Display of the Source Mode Internal or External
5. Display of the current Sync-mode (“!” = Sync active)

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 39

 Block Description

Faceplate

1
8 2
3

5 6

4 7

1. Display of the Operation Mode Manual or Automatic, selection possibility via the button

2. Display of the Source Mode Internal or External, selection possibility via the button

3. Display of the Sync Mode, selection possibility via the button, if not connected to a Proxy Function Block tag.
If connected, it will be driven by a connected SFC.
4. Display of the Manual Parameter Value Variable (Prepared SP) Vop and the Value Unit VUnit. A click in this field
opens an additional command window, through which the value can be entered.
5. Display of the Requested Parameter Value Variable VReq and the Value Unit VUnit
6. Display of the Current Parameter Value Variable VOut and the Value Unit VUnit
7. Display of the Feedback Value Variable VFbk and the Value Unit VUnit
8. Apply Button: triggers the value transfer of the Prepared Setpoint to the PEA

Tags of the Type to be transferred by the Open OS Data Marshalling

The following tags of the type MTP_SFC_AnaServParam have additional “Connect” tags as described in chapter 4.2.3 and
need input of the target address of the associated tags from the Proxy Function Blocks if a connection to an SFC in a
connected non-modular sub-plant (PCS 7 AS) is required.

Name Access Type

ApplyEn POL ← PEA BOOL
ApplyExt POL → PEA BOOL
SrcExtAct POL ← PEA BOOL
SrcIntAct POL ← PEA BOOL
StateAutAct POL ← PEA BOOL
StateOffAct POL ← PEA BOOL
StateOpAct POL ← PEA BOOL
Sync POL → PEA BOOL
VExt POL → PEA REAL
VFbk POL ← PEA REAL
VMax POL ← PEA REAL
VMin POL ← PEA REAL
VOut POL ← PEA REAL
VReq POL ← PEA REAL
VUnit POL ← PEA INT
WQC POL ← PEA BYTE

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 40

 Block Description

5.1.2.2. Binary Service Parameter

Block Icon

1. Display of the Current Parameter Value Variable VOut

Faceplate

1
7 2
3

6
5
4

1. Display of the Operation Mode Manual or Automatic, selection possibility via the button

2. Display of the Source Mode Internal or External, selection possibility via the button

3. Display of the Sync Mode, selection possibility via the button, if not connected to a Proxy Function Block tag.
If connected, it will be driven by a connected SFC.

4. Display of the Manual Parameter Value Variable (Prepared SP) VOp. Selection possibility via the button if in
Manual Mode
5. Display of the Current Parameter Value Variable VOut
6. Display of the Requested Parameter Value Variable VReq
7. Apply Button: triggers the value transfer of the Prepared Setpoint to the PEA

Tags of the Type to be transferred by the Open OS Data Marshalling

The following tags of the type MTP_SFC_BinServParam have additional “Connect” tags as described in chapter 4.2.3 and
need input of the target address of the associated tags from the Proxy Function Blocks if a connection to an SFC in a
connected non-modular sub-plant (PCS 7 AS) is required.

Name Access Type

ApplyEn POL ← PEA BOOL
ApplyExt POL → PEA BOOL
SrcExtAct POL ← PEA BOOL

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 41

 Block Description

SrcIntAct POL ← PEA BOOL

StateAutAct POL ← PEA BOOL
StateOffAct POL ← PEA BOOL
StateOpAct POL ← PEA BOOL
Sync POL → PEA BOOL
VExt POL → PEA BOOL
VFbk POL ← PEA BOOL
VOut POL ← PEA BOOL
VReq POL ← PEA BOOL
WQC POL ← PEA BYTE

5.1.2.3. Double Integer Service Parameter

Block Icons
Variant 1 Variant 2

5
1

3 4

1. Display of the Feedback Value Variable VFbk

2. Display of the Manual Parameter Value Variable (Prepared SP) VOp
3. Display of the Operation Mode Manual or Automatic
4. Display of the Source Mode Internal or External
5. Display of the current Sync-mode (“!” = Sync active)

Faceplate

1
8 2
3

5 6

4 7

1. Display of the Operation Mode Manual or Automatic, selection possibility via the button

2. Display of the Source Mode Internal or External, selection possibility via the button

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 42

 Block Description

3. Display of the Sync Mode, selection possibility via the button, if not connected to a Proxy Function Block tag.
If connected, it will be driven by a connected SFC.
4. Display of the Manual Parameter Value Variable (Prepared SP) Vop and the Value Unit VUnit. A click in this field
opens an additional command window, through which the value can be entered.
5. Display of the Requested Parameter Value Variable VReq and the Value Unit VUnit
6. Display of the Current Parameter Value Variable VOut and the Value Unit VUnit
7. Display of the Feedback Value Variable VFbk and the Value Unit VUnit
8. Apply Button: triggers the value transfer of the Prepared Setpoint to the PEA

Tags of the Type to be transferred by the Open OS Data Marshalling

The following tags of the type MTP_SFC_DIntServParam have additional “Connect” tags as described in chapter 4.2.3 and
need input of the target address of the associated tags from the Proxy Function Blocks if a connection to an SFC in a
connected non-modular sub-plant (PCS 7 AS) is required.

Name Access Type

ApplyEn POL ← PEA BOOL
ApplyExt POL → PEA BOOL
SrcExtAct POL ← PEA BOOL
SrcIntAct POL ← PEA BOOL
StateAutAct POL ← PEA BOOL
StateOffAct POL ← PEA BOOL
StateOpAct POL ← PEA BOOL
Sync POL → PEA BOOL
VExt POL → PEA DINT
VFbk POL ← PEA DINT
VMax POL ← PEA DINT
VMin POL ← PEA DINT
VOut POL ← PEA DINT
VReq POL ← PEA DINT
VUnit POL ← PEA INT
WQC POL ← PEA BYTE

5.1.2.4. String Service Parameter

Block Icons

1
2

1. Display of the Feedback Value Variable VFbk

2. Display of the Manual Parameter Value Variable (Prepared SP) VOp

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 43

 Block Description

Faceplate

1
8 2
3

7
6
5
4

1. Display of the Operation Mode Manual or Automatic, selection possibility via the button

2. Display of the Source Mode Internal or External, selection possibility via the button

3. Display of the Sync Mode, selection possibility via the button, if not connected to a Proxy Function Block tag.
If connected, it will be driven by a connected SFC.
4. Display of the Manual Parameter Value Variable (Prepared SP) VOp. A click in this field opens an additional
command window, through which the value can be entered.
5. Display of the Feedback Value Variable VFbk
6. Display of the Current Parameter Value Variable VOut
7. Display of the Requested Parameter Value Variable VReq
8. Apply Button: triggers the value transfer of the Prepared Setpoint to the PEA

Tags of the Type to be transferred by the Open OS Data Marshalling

The following tags of the type MTP_SFC_StringServParam have additional “Connect” tags as described in chapter 4.2.3
and need input of the target address of the associated tags from the Proxy Function Blocks if a connection to an SFC in a
connected non-modular sub-plant (PCS 7 AS) is required.

Name Access Type

ApplyEn POL ← PEA BOOL
ApplyExt POL → PEA BOOL
SrcExtAct POL ← PEA BOOL
SrcIntAct POL ← PEA BOOL
StateAutAct POL ← PEA BOOL
StateOffAct POL ← PEA BOOL
StateOpAct POL ← PEA BOOL
Sync POL → PEA BOOL
VExt POL → PEA STRING
VFbk POL ← PEA STRING
VOut POL ← PEA STRING
VReq POL ← PEA STRING
WQC POL ← PEA BYTE

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 44

 Block Description

5.1.3. ProcessValueIn Family

The ProcessValueIn family is divided into 4 sub-families, depending on the data type: analog
(MTP_SFC_AnaProcessValueIn), binary (MTP_SFC_BinProcessValueIn), double integer (MTP_SFC_DIntProcessValueIn), and
string (MTP_SFC_StringProcessValueIn).

5.1.3.1. Analog ProcessValueIn

Block Icon

1 2

1. Display of the Current Value V

2. Display of the Value Unit VUnit

Faceplate

2
3
4

1. Display of the Current Value V and the Value Unit VUnit. The value cannot be operated from the faceplate, it is
only driven by a connected SFC.
2. Display of the Current Unit UnitCur
3. Display of the Current Scale Maximum SclMaxCur.
4. Display of the Configuration Input for the Scale Maximum SclMaxExt
5. Display of the Configuration Input for the Scale Minimum SclMinExt
6. Display of the Current Scale Minimum SclMinCur
7. Apply Button: triggers the value transfer of the Configuration Inputs to the PEA. It is only shown if the ApplyEn
bit of the respective process value in the PEA is true.

Tags of the Type to be transferred by the Open OS Data Marshalling

The following tags of the type MTP_SFC_AnaProcessValueIn have additional “Connect” tags as described in chapter 4.2.3
and need input of the target address of the associated tags from the Proxy Function Blocks if a connection to an SFC in a
connected non-modular sub-plant (PCS 7 AS) is required.

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 45

 Block Description

Name Access Type

UnitCur POL ← PEA INT
V POL → PEA REAL
WQC POL ← PEA BYTE

5.1.3.2. Binary ProcessValueIn

Block Icon

1. Display of the Current Value V

Faceplate

1. Display of the Current Value V as string (VState0/VState1 from the PEA). The value cannot be operated from the
faceplate, it is only driven by a connected SFC.
2. Display of the Current Value V as binary value

Tags of the Type to be transferred by the Open OS Data Marshalling

The following tags of the type MTP_SFC_BinProcessValueIn have additional “Connect” tags as described in chapter 4.2.3
and need input of the target address of the associated tags from the Proxy Function Blocks if a connection to an SFC in a
connected non-modular sub-plant (PCS 7 AS) is required.

Name Access Type

V POL → PEA BOOL
WQC POL ← PEA BYTE

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 46

 Block Description

5.1.3.3. Double Integer ProcessValueIn

Block Icon

1 2

1. Display of the Current Value V

2. Display of the Value Unit VUnit

Faceplate

2
3
4

1. Display of the Current Value V and the Value Unit VUnit. The value cannot be operated from the faceplate, it is
only driven by a connected SFC.
2. Display of the Current Unit UnitCur
3. Display of the Current Scale Maximum SclMaxCur.
4. Display of the Configuration Input for the Scale Maximum SclMaxExt
5. Display of the Configuration Input for the Scale Minimum SclMinExt
6. Display of the Current Scale Minimum SclMinCur
7. Apply Button: triggers the value transfer of the Configuration Inputs to the PEA. It is only shown if the ApplyEn
bit of the respective process value in the PEA is true.

Tags of the Type to be transferred by the Open OS Data Marshalling

The following tags of the type MTP_SFC_DIntProcessValueIn have additional “Connect” tags as described in chapter 4.2.3
and need input of the target address of the associated tags from the Proxy Function Blocks if a connection to an SFC in a
connected non-modular sub-plant (PCS 7 AS) is required.

Name Access Type

UnitCur POL ← PEA INT
V POL → PEA DINT
WQC POL ← PEA BYTE

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 47

 Block Description

5.1.3.4. String ProcessValueIn

Block Icon

1. Display of the Current Value V

Faceplate

1. Display of the Current Value V as binary value.

No operation is possible. Only the string value originating from an SFC in a connected PCS 7 Controller is
displayed and routed through to the PEA.

Tags of the Type to be transferred by the Open OS Data Marshalling

The following tags of the type MTP_SFC_StringProcessValueIn have additional “Connect” tags as described in chapter 4.2.3
and need input of the target address of the associated tags from the Proxy Function Blocks if a connection to an SFC in a
connected non-modular sub-plant (PCS 7 AS) is required.

Name Access Type

V POL → PEA STRING
WQC POL ← PEA BYTE

5.1.4. ProcessValueOut Family

The ProcessValueOut family is divided into 4 sub-families, depending on the data type: analog
(MTP_SFC_AnaProcessValueOut), binary (MTP_SFC_BinProcessValueOut), double integer
(MTP_SFC_DIntProcessValueOut), and string (MTP_SFC_StringProcessValueOut).
The ProcessValueOut types are essentially similar to the corresponding Basic View types, except that they have been
enhanced with some scripting to pass data back and forth between a connected PCS 7 Controller and the PEA.

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 48

 Block Description

5.1.4.1. Analog ProcessValueOut

Block Icon

Variant 1 Variant 2

3
3
2 2

1
1. Display of the Current Value V
2. Display of the Value Unit VUnit
3. Display of the Worst Quality Code Variable WQC

Faceplate

2
1
3

1. Display of the Current Value V and the Value Unit VUnit from the PEA, without any operation option.
2. Display of the Value Scale High Limit VSclMax
3. Display of the Value Scale Low Limit VSclMin.

Tags of the Type to be transferred by the Open OS Data Marshalling

The following tags of the type MTP_SFC_AnaProcessValueOut have additional “Connect” tags as described in chapter 4.2.3
and need input of the target address of the associated tags from the Proxy Function Blocks if a connection to an SFC in a
connected non-modular sub-plant (PCS 7 AS) is required.

Name Access Type

V POL ← PEA REAL
VUnit POL ← PEA INT
WQC POL ← PEA BYTE

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 49

 Block Description

5.1.4.2. Binary ProcessValueOut

Block Icon
Variant 1 Variant 2

1
1 1

1. Display of the Current Value V

2. Display of the Worst Quality Code Variable WQC

Faceplate

1. Display of the Current Value V from the PEA as string (VState0/VState1 from the PEA).
2. Display of the Worst Quality Code Variable WQC

Tags of the Type to be transferred by the Open OS Data Marshalling

The following tags of the type MTP_SFC_BinProcessValueOut have additional “Connect” tags as described in chapter 4.2.3
and need input of the target address of the associated tags from the Proxy Function Blocks if a connection to an SFC in a
connected non-modular sub-plant (PCS 7 AS) is required.

Name Access Type

V POL ← PEA BOOL
WQC POL ← PEA BYTE

5.1.4.3. Double Integer ProcessValueOut

Block Icon
Variant 1 Variant 2

3 3

2 2

1
1. Display of the Current Value V
2. Display of the Value Unit VUnit
3. Display of the Worst Quality Code Variable WQC

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 50

 Block Description

Faceplate

2
1
3

1. Display of the Current Value V and the Value Unit VUnit from the PEA, without any operation option.
2. Display of the Value Scale High Limit VSclMax
3. Display of the Value Scale Low Limit VSclMin.

Tags of the Type to be transferred by the Open OS Data Marshalling

The following tags of the type MTP_SFC_DIntProcessValueOut have additional “Connect” tags as described in chapter
4.2.3 and need input of the target address of the associated tags from the Proxy Function Blocks if a connection to an SFC
in a connected non-modular sub-plant (PCS 7 AS) is required.

Name Access Type

V POL ← PEA DINT
VUnit POL ← PEA INT
WQC POL ← PEA BYTE

5.1.4.4. String ProcessValueOut

Block Icon

1. Display of the Current Value Text

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 51

 Block Description

Faceplate

1. Display of the Current Value Text from the PEA

Tags of the Type to be transferred by the Open OS Data Marshalling

The following tags of the type MTP_SFC_StringProcessValueOut have additional “Connect” tags as described in chapter
4.2.3 and need input of the target address of the associated tags from the Proxy Function Blocks if a connection to an SFC
in a connected non-modular sub-plant (PCS 7 AS) is required.

Name Access Type

Text POL ← PEA STRING
WQC POL ← PEA BYTE

5.1.5. ReportValue Family

The ReportValue family is divided into 4 sub-families, depending on the data type: analog (MTP_SFC_AnaReportValue),
binary (MTP_SFC_BinReportValue), double integer (MTP_SFC_DIntReportValue), and string (MTP_SFC_StringReportValue).
The ReportValue types are essentially similar to the corresponding Basic View types, except that they have been enhanced
with some scripting to pass data back and forth between a connected PCS 7 Controller and the PEA, and they have been
supplemented with a MissedValue flag.

5.1.5.1. Analog ReportValue

Block Icon
Variant 1 Variant 2

3 3

2 2

1
1. Display of the Current Value V
2. Display of the Value Unit VUnit
3. Display of the Worst Quality Code Variable WQC

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 52

 Block Description

Faceplate

2
1
3

1. Display of the Current Value V and the Value Unit VUnit from the PEA, without any operation option.
2. Display of the Value Scale High Limit VSclMax
3. Display of the Value Scale Low Limit VSclMin.
4. Display of the MissedValue flag

Tags of the Type to be transferred by the Open OS Data Marshalling

The following tags of the type MTP_SFC_AnaReportValue have additional “Connect” tags as described in chapter 4.2.3 and
need input of the target address of the associated tags from the Proxy Function Blocks if a connection to an SFC in a
connected non-modular sub-plant (PCS 7 AS) is required.

Name Access Type

V POL ← PEA REAL
VUnit POL ← PEA INT
WQC POL ← PEA BYTE

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 53

 Block Description

5.1.5.2. Binary ReportValue

Block Icon
Variant 1 Variant 2

2
1 2 1

1. Display of the Current Value V

2. Display of the Worst Quality Code Variable WQC

Faceplate

1. Display of the Current Value V from the PEA as string (VState0/VState1 from the PEA, if available).
2. Display of the MissedValue flag
3. Display of the Worst Quality Code Variable WQC

Tags of the Type to be transferred by the Open OS Data Marshalling

The following tags of the type MTP_SFC_BinReportValue have additional “Connect” tags as described in chapter 4.2.3 and
need input of the target address of the associated tags from the Proxy Function Blocks if a connection to an SFC in a
connected non-modular sub-plant (PCS 7 AS) is required.

Name Access Type

V POL ← PEA BOOL
WQC POL ← PEA BYTE

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 54

 Block Description

5.1.5.3. Double Integer ReportValue

Block Icon
Variant 1 Variant 2

3 3

2 2

1
1. Display of the Current Value V
2. Display of the Value Unit VUnit
3. Display of the Worst Quality Code Variable WQC

Faceplate

2
1
3

1. Display of the Current Value V and the Value Unit VUnit from the PEA, without any operation option.
2. Display of the Value Scale High Limit VSclMax
3. Display of the Value Scale Low Limit VSclMin
4. Display of the MissedValue flag

Tags of the Type to be transferred by the Open OS Data Marshalling

The following tags of the type MTP_SFC_DIntRepoprtValue have additional “Connect” tags as described in chapter 4.2.3
and need input of the target address of the associated tags from the Proxy Function Blocks if a connection to an SFC in a
connected non-modular sub-plant (PCS 7 AS) is required.

Name Access Type

V POL ← PEA DINT
VUnit POL ← PEA INT
WQC POL ← PEA BYTE

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 55

 Block Description

5.1.5.4. String ReportValue

Block Icon

1. Display of the Current Value Text

Faceplate

1. Display of the Current Value Text from the PEA

2. Display of the MissedValue flag

Tags of the Type to be transferred by the Open OS Data Marshalling

The following tags of the type MTP_SFC_StringReportValue have additional “Connect” tags as described in chapter 4.2.3
and need input of the target address of the associated tags from the Proxy Function Blocks if a connection to an SFC in a
connected non-modular sub-plant (PCS 7 AS) is required.

Name Access Type

Text POL ← PEA STRING
WQC POL ← PEA BYTE

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 56

 Block Description

5.2. Service Block Interfaces

As mentioned in chapter 4.2, the Proxy Function blocks are the link between the PCS 7 controller and the MTP Unit via the
OS scripting. The blocks are installed on PCS 7 Engineering station as an additional library. Additionally, the SCL-Sources
are included for further adaptation.
This chapter describes the block interfaces and their functionality.

5.2.1. Service Control

The Service Control block is the link to the Service block of the MTP Unit. In addition to the standardized MTP interface,
some further inputs and outputs are available to improve the usability and to realize a connection to an SFC-Type.

5.2.1.1. Block Interface

Name Type Name Type

Inputs Outputs
CommandExt DWORD WQC BYTE
ProcedureExt DWORD StateCur DWORD
StateOffOp BOOL CommandEn DWORD
StateOpOp BOOL ProcedureCur DWORD
StateAutOp BOOL ProcedureReq DWORD
SrcIntOp BOOL StateOpAct BOOL
SrcExtOp BOOL StateAutAct BOOL
ProcParamApplyExt BOOL StateOffAct BOOL
ProcParamApplyOp BOOL SrcIntAct BOOL
ConfigParamApplyExt BOOL SrcExtAct BOOL
ReportValueFreeze BOOL ProcParamApplyEn BOOL
Reset BOOL ConfigParamApplyEn BOOL
Start BOOL ConfigParamApplyInt BOOL
Stop BOOL Stopped BOOL
Hold BOOL Starting BOOL
Unhold BOOL Idle BOOL
Pause BOOL Paused BOOL
Resume BOOL Execute BOOL
Abort BOOL Stopping BOOL
Restart BOOL Aborting BOOL
Complete BOOL Aborted BOOL
SFC_Ctrl_On BOOL Holding BOOL
SFC_State DWORD Held BOOL
Unholding BOOL
Pausing BOOL
Resuming BOOL
Resetting BOOL
Completing BOOL
Completed BOOL

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 57

 Block Description

ResetEnabled BOOL
StartEnabled BOOL
StopEnabled BOOL
HoldEnabled BOOL
UnholdEnabled BOOL
PauseEnabled BOOL
ResumeEnabled BOOL
AbortEnabled BOOL
RestartEnabled BOOL
CompleteEnabled BOOL
ReadyToCtrl BOOL

5.2.1.2. Additional Functionality

StateCur:
The output StateCur represents the current state of the service control in DWORD data format. For an optimized overview,
each state is also routed to a single Boolean output:

StateCur Output = True

16#4 Stopped
16#8 Starting
16#10 Idle
16#20 Paused
16#40 Execute
16#80 Stopping
16#100 Aborting
16#200 Aborted
16#400 Holding
16#800 Held
16#1000 Unholding
16#2000 Pausing
16#4000 Resuming
16#8000 Resetting
16#10000 Completing
16#20000 Completed

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 58

 Block Description

CommandExt:
The output CommandExt represents the executable external commands of the service control in DWORD data format. For
an optimized overview, each command is also routed to a single Boolean output:

CommandExt Output = True

16#2 Reset
16#4 Start
16#8 Stop
16#10 Hold
16#20 Unhold
16#40 Pause
16#80 Resume
16#100 Abort
16#200 Restart
16#400 Complete

CommandEn:
The output CommandEn represents the enabled commands of the service control in data format DWORD. For an
optimized overview, each enabled command is also routed to a single Boolean output:

CommandEn Output = True

16#2 ResetEnabled
16#4 StartEnabled
16#8 StopEnabled
16#10 HoldEnabled
16#20 UnholdEnabled
16#40 PauseEnabled
16#80 ResumeEnabled
16#100 AbortEnabled
16#200 RestartEnabled
16#400 CompleteEnabled

ReadyToCrtl:
The output ReadyToCrtl is true when the service is in operating mode automatic as well as in source mode external.
ReadyToCrtl = StateAutAct AND SrcExtAct

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 59

 Block Description

SFC-Type Control:
The input SFC_Ctrl_On activates the SFC-Type control option. In that case, the external commands will be set by the
connected SFC-Type via the input SFC_State. Simultaneous commands via the block interface inputs are disabled.
The following command matrix will be activated:

Rules Result
SFC-Type Interconnection Service control Service control
(SFC_State) logic (StateCur) (ComandExt)
Idle AND Not Idle Reset
Run - - Start
Stopped - - Stop
Held OR Error - - Hold
Resuming AND Held Unhold
Resuming AND Paused Resume
Aborted - - Abort
Completed - - Complete

Please note:
Further information about the SFC_STATE of the SFC-Type can be found in the manual “SIMATIC Process Control System
PCS 7 SFC for SIMATIC S7 (V9.0 SP7).

Please note:
The rules for the CommandExt are a possibility for a simple connection between an SFC Type and the service control. If
other rules are required, the source can be adapted.

5.2.2. Procedure Parameter

The procedure parameter blocks are the link to the procedure parameter of the MTP Unit.

5.2.2.1. AnaServParam (Analog)

Name Type Name Type

Inputs Outputs
ApplyExt BOOL WQC BYTE
Sync BOOL ApplyEn BOOL
VExt REAL StateOpAct BOOL
StateAutAct BOOL
StateOffAct BOOL
SrcIntAct BOOL
SrcExtAct BOOL
VReq REAL
VOut REAL
VFbk REAL
VUnit INT
VMin REAL
VMax REAL

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 60

 Block Description

5.2.2.2. DIntServParam (Double Integer)

Name Type Name Type

Inputs Outputs
ApplyExt BOOL WQC BYTE
Sync BOOL ApplyEn BOOL
VExt DINT StateOpAct BOOL
StateAutAct BOOL
StateOffAct BOOL
SrcIntAct BOOL
SrcExtAct BOOL
VReq DINT
VOut DINT
VFbk DINT
VUnit INT
VMin DINT
VMax DINT

5.2.2.3. BinServParam (Binary)

Name Type Name Type

Inputs Outputs
ApplyExt BOOL WQC BYTE
Sync BOOL ApplyEn BOOL
VExt BOOL StateOpAct BOOL
StateAutAct BOOL
StateOffAct BOOL
SrcIntAct BOOL
SrcExtAct BOOL
VReq BOOL
VOut BOOL
VFbk BOOL

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 61

 Block Description

5.2.2.4. StringServParam (String)

Name Type Name Type

Inputs Outputs
ApplyExt BOOL WQC BYTE
Sync BOOL ApplyEn BOOL
VExt STRING StateOpAct BOOL
StateAutAct BOOL
StateOffAct BOOL
SrcIntAct BOOL
SrcExtAct BOOL
VReq STRING
VOut STRING
VFbk STRING

5.2.3. Process Values

The process value input and output blocks are the link to the process values of the MTP Unit.

5.2.3.1. Analog Input AnaPVIn

Name Type Name Type

Inputs Outputs
VQC BYTE WQC BYTE
V REAL UnitCur INT
UnitExt INT ApplyEn BOOL
Apply BOOL

5.2.3.2. Double Integer Input DIntPVIn

Name Type Name Type

Inputs Outputs
VQC BYTE WQC BYTE
V DINT UnitCur INT
UnitExt INT ApplyEn BOOL
Apply BOOL

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 62

 Block Description

5.2.3.3. Binary Input BinPVIn

Name Type Name Type

Inputs Outputs
VQC BYTE WQC BYTE
V BOOL

5.2.3.4. String Input StringPV

Name Type Name Type

Inputs Outputs
VQC BYTE WQC BYTE
V STRING

5.2.3.5. Analog Output AnaPVOut

Name Type Name Type

Inputs Outputs
WQC BYTE
V REAL
VUnit INT

5.2.3.6. Double Integer Output DIntPVOut

Name Type Name Type

Inputs Outputs
WQC BYTE
V DINT
VUnit BYTE

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 63

 Block Description

5.2.3.7. Binary Output BinPVOut

Name Type Name Type

Inputs Outputs
WQC BYTE
V BOOL

5.2.3.8. String Output StringPVOut

Name Type Name Type

Inputs Outputs
WQC BYTE
Text STRING

5.2.4. Report Value

The Report value blocks are the link to the Report values of the MTP Unit.

5.2.4.1. Analog AnaReportValue

Name Type Name Type

Inputs Outputs
WQC BYTE
V REAL
VUnit INT
MissedValue BOOL

5.2.4.2. Double Integer DIntReportValue

Name Type Name Type

Inputs Outputs
WQC BYTE
V DINT
VUnit INT
MissedValue BOOL

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 64

 Block Description

5.2.4.3. Binary BinReportValue

Name Type Name Type

Inputs Outputs
WQC BYTE
V BOOL
MissedValue BOOL

5.2.4.4. String StringReportVal

Name Type Name Type

Inputs Outputs
WQC BYTE
Text STRING
MissedValue BOOL

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 65

 Appendix

6. Appendix
6.1. Service and support
SiePortal
The integrated platform for product selection, purchasing and support - and connection of Industry Mall and Online
support. The SiePortal home page replaces the previous home pages of the Industry Mall and the Online Support Portal
(SIOS) and combines them.

• Products & Services

In Products & Services, you can find all our offerings as previously available in Mall Catalog.
• Support
In Support, you can find all information helpful for resolving technical issues with our products.
• mySieportal
mySiePortal collects all your personal data and processes, from your account to current orders, service requests and
more. You can only see the full range of functions here after you have logged in.
You can access SiePortal via this address: sieportal.siemens.com

Industry Online Support

Industry Online Support is the previous address for information on our products, solutions and services.
Product information, manuals, downloads, FAQs and application examples - all information is available 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

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

Industry Online Support app

You will receive optimum support wherever you are with the "Industry Online Support" app. The app is available for iOS
and Android:

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 66

 Appendix

6.2. Links and literature

Nr. Thema

\1\ Siemens Industry Online Support

https://support.industry.siemens.com

\2\ Link to this entry page of this application example

https://support.industry.siemens.com/cs/ww/en/view/109955053

\3\

Table 6-1

6.3. Change documentation

Version Date Modification

V1.0 03/2024 First version

Table 6-2

Entry ID: 109955053 | V1.0 | 03/2024 © Siemens 2024 | 67