Application Example HMI Wincc Unified
Application Example HMI Wincc Unified
Industry
Online
Support
APPLICATION EXAMPLE
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.
Table of contents
1. Introduction ...................................................................................................................................5
4. Configuration notes......................................................................................................................64
5. Appendix .....................................................................................................................................73
1. Introduction
1.1. Overview
Systems and machines are becoming more and more complex and, therefore, the demands on the system operators are
increasing. For this reason, designing an intuitive and graphically appealing user interface as a link between human and
machine is becoming increasingly more important.
The HMI Template Suite offers you templates and ideas to make the configuration of your operator panel clear and
modern.
Figure 1-1
Layout and design are designed for smooth operation, transparency, and scalability. In this way, you can simplify the
operation of your machine and reduce operator errors.
NOTE You can find additional information on the operator philosophy in the free HMI Design Masterclass:
https://new.siemens.com/global/en/products/automation/simatic-hmi/design-masterclass.html
1 2
The navigation can be likened to the Table of Contents in a Word document in which a main heading contains sub-
chapters.
Here, the "Tile" named "Tile 1.1" is analogous to the first "navigation level" which pulls up the associated plant screen.
The "Tile" named "Tile 2.1" is analogous to the second "navigation level" which pulls up its own associated plant screen.
The following graphic is provided to illustrate the principle of operation.
Figure 1-3
Tile navigation
Navigation layer 1
Tile
1.1
Tile
1.2
Navigation layer 2
Tile
2.1
Tile
2.2
Tile
1.3
Tile
1.4
A detailed description of how to configure a "tile navigation" can be found in Section 2.2.2.
SIMATIC HMI MTP700 Unified 1 6AV2128-3GB06-0AX0 Alternativ können Sie Bediengeräte in der
Comfort Größe von 7 bis 22 Zoll einsetzen.
You can purchase these components from the Siemens Industry Mall.
Documentation 91174767_HMITemplateSuiteUnified_V4.2_DOC_de.pdf
3. In the console tree of the "Computer Management" window, double-click the local "Siemens TIA Openness" user group
under "Groups".
Figure 2-4
4. Check whether the user under which you've logged in to the engineering PC is a member of the "Siemens TIA
Openness" user group. If it is not a member, add the user to the group.
Figure 2-5
2.1.3. Installation
1. Download the file "SIMATIC HMI Template Suite Wizard V3.0.0 Setup.zip" from this application example and unzip it.
2. Start the installation by double clicking the file "SIMATIC HMI Template Suite Wizard V3.0.0 Setup.exe".
Figure 2-6
2. Select the navigation type. You have two types to choose from:
a. Sidebar navigation (navigation elements arranged to the side).
b. Tile navigation.
Figure 2-9
a b
3. Select your TIA Portal project or create a new TIA Portal project:
- In the next step, choose whether you want to modify an existing TIA project (1) or create a new project.
To modify an existing project, the project must already be open.
If you create a new project, you must also specify the "Project name" and "Location".
- Click "Next" button (2).
Figure 2-12
4. Various functions now run automatically in the background, such as establishing a connection to the TIA Portal
project, etc.
Figure 2-13
Figure 2-14
Error message
If the "Openness access" message (see Figure 2-14) is not confirmed in time, the following message appears. In this case,
click "Quit".
The Wizard is canceled. Start the Wizard a second time.
Figure 2-15
7. In the last step, all chosen settings are displayed again in summary.
Click "Finish" (1) to complete the Wizard and apply the changes to your project.
Figure 2-18
3. Select your TIA Portal project or create a new TIA Portal project:
- Choose whether you want to modify an existing TIA project (1) or create a new project.
To extend an existing project, the project must already be open.
If you create a new project, you must also specify the "Project name" and "Location".
- Click the "Next" button (2).
Figure 2-21
4. Various functions now run automatically in the background, such as establishing a connection to the TIA Portal
project, etc. This can cause a brief waiting time and is necessary for transmitting the screen navigation that will be
programmed below.
Figure 2-22
The properties of the project are displayed as read-only. Click "Next" to go to the screen selection screen.
Error message
Frei verwendbar
If the "Openness access" message (see Figure 2-23) is not confirmed in time, the following message appears. In this case,
click "Quit".
The Wizard is canceled. Start the Wizard a second time.
Figure 2-24
Figure 2-25
3 1
4
1 2
3
Before starting to create the individual navigation levels and their page calls with the "tiles", you
NOTE
should create an overview of the plant structure and its naming conventions. This will help you keep
track of the configuration steps below.
Unit100 Screen 1
Unit200 Screen 2
Unit300
navigation level 1
Unit310
navigation level 2
Unit320 Screen 1
Unit321 Screen 2
Unit322 Screen 3
Unit311 Screen 1
Unit312 Screen 2
Assign tiles
5. In the generated HMI project, the tiles are used to access the assigned HMI Template Suite screens.
Zoom out of the view using the drop-down menu (1) for a more manageable view.
Figure 2-27
9. The properties of the tile (2) appear under the selected tile (1). You can change various settings here. Some of the
settings are described in greater detail below.
(3) You can give the tile a background color. This lets you color-code plant areas, for example.
(4) Give the tile a unique name under the "Name" section. The name will be used for the screen navigation. Do not
change it later on. If your project is in multiple languages, try to use English names for the "Name" property where
possible.
(5) Here you can select a graphic from a preset list and have it displayed on the foreground of the tile.
(6) Give the tile a name with the "Text" section, for example the name of the screen that this tile will pull up. This
text appears at the bottom edge of the tile and serves as a tooltip about the function of the tile, for example to change
to the screen indicated. This text can be changed later on in the generated HMI project.
Figure 2-30
2
3
Optional: Assign a tile an image from the HMI Template Suite collection
Select a tile. In this example: the tile "Unit100" (1). Click the "library" icon (2) in the header. A window will open where
you can select images from the HMI Template Suite library (3). Select an image from the library collection (4) and
confirm the selection with "Ok" (5).
Figure 2-32
11. Repeat these steps if you wish to assign other tiles images from the library collection.
The Figure below shows two levels that were added (1) and (2).
The view corresponds to the plant structure created earlier (see Figure 2-26).
Figure 2-34
1
2
Before making any changes, make a backup copy of the current configuration.
CAUTION
By renaming the screens manually, there is a possibility that the "link" of the automatically generated
screens will be lost if the renaming is done incorrectly.
1. In the project tree, open the screen "Screens > 01_ScreenLayout > 01_ScreenLayout".
2. The names of the navigation levels are stored under "Properties > Events". Now modify these manually.
Figure 2-37
2 1
Navigation within the "Tile navigation" is done with the "navigation elements" in the title bar. The "sub-navigation" is
hidden for this (it can also be shown if needed).
Figure 2-41
The Figure below shows a screen from the HMI Template Suite with the "sub-navigation" visible.
Figure 2-42
Configuration
1. Modify/check "01_ScreenLayout" screen.
a. Open the screen "01_ScreenLayout"
("Project tree > Screens > 01-Screenlayout").
3. In all screens where the "sub-navigation" needs to be hidden, you must put the following script under the screen
properties ("Properties > Events > Loaded"):
{HMIRuntime.UI.SysFct.SetPropertyValue("../swSubNavigation", "Visible", 0)
The "0" means that the sub-navigation will be hidden. If the sub-navigation needs to remain visible, change the "0" to
"1".
Figure 2-43
Move the various HMI objects into you operator panel using the drag-and-drop feature.
When dragging an operator panel into your project, make sure that you also include the faceplates
NOTE
(see also Section 3.1.1).
Use the preconfigured operator panels that are stored in the library under the different resolutions in the folder "00 –
Device".
Figure 2-44
The operator panels are located in the library within the subfolders "00 – Device". They are stored
NOTE
according to resolution.
You can create your visualization on this basis and enhance it using the other objects (i.e., pop-up
screens) from the library.
The preconfigured pop-up screens are screens that are used as pop-ups in WinCC Unified via a screen
NOTE
window.
The HMI screens are stored in the subfolder "02 - Screens" in the respective resolution.
NOTE
Figure 2-46
You can find the navigation and operator panels in the "04 – Grouped objects" subfolder.
NOTE
Figure 2-47
Figure 2-48
NOTE Ensure that the components of the automation system you are using are VoT-capable. You can find
help in the compatibility tool.
You can find the tool via https://www.siemens.com/compatool.
To stay within the VoT limits, do not configure more than 10 screens. The folder "00 - Info: Use up to
NOTE
ten screens for your VoT application!" does not contain any screens and is for information purposes
only.
• An accent color
• A complementary color
• Various graded gray tones for navigation
• Light gray for the application area (MainWindow) and for operating the system
• Another shade of gray for regular text
The accent color is used to highlight objects such as the title bar or active buttons and tabs.
The gray tones are used to separate the navigation bars and the status bar from the content of the main screen.
The Main Window background is lighter. The main content stands out due to its placement in the center of the Operator
Panel and the high-contrast differentiation from the other objects at the edge of the screen.
Figure 2-49
For visualization, the following main colors are used for the HMI objects.
Table 2-1
Color RGB color code Function
0,161,209 Accent color blue ("selective" color)
For example, if a button is active
38,39,41 Anthracite
Main Navigation (background)
255,255,255 White
Status bar (background), content board (background)
SubNavigation (background)
222,56,88 Alarm
133,147,153 Gray
Value descriptions for ContentBoards
If the contents of the Title bar (1) and Status bar (2) remain the same throughout the project, a screen
NOTE
window can also be used for both areas.
Figure 2-50
1
2
6 3 5
The contents displayed in the screen window are configured in the folder "Screens".
In the "01_ScreenLayout" screen, the following elements are located next to the screen windows:
NOTE
• "btnHideMainNavigation":
Closes the MainNavigation if it is open and is clicked outside the MainNavigation.
• "RecBackground":
Semi-transparent rectangle that blocks the entire screen except the image that is called as a pop-
up.
Screen window
1 1
The first navigation level (MainNavigation) is implemented via a screen window "swMainNavigation" in the
"01_ScreenLayout" screen on the right side. The "03_MainNavigation" screen is displayed in the screen window.
The main navigation can be displayed via the hamburger ( ) menu in the Title bar.
If you want to show or hide levels of navigation and highlight the selected navigation point, please
NOTE
refer to Section 2.5.2.
In the main navigation, you can switch between the configured application and the global message page. In "Settings",
you can, for example, change the display language or the brightness of the operator panel.
Configuration
The first menu level is already included in the preconfigured operator panel.
Figure 2-52
You can switch between the individual HMI screens of a plant module using the navigation bar (see Section 4.2).
Configuration
The second navigation level is configured via the "swSubNavigation" screen window in the "01_ScreenLayout" screen. You
can configure page calls and adjust the text in the corresponding screen, "04_SubNavigation".
Figure 2-54
Figure 2-55
Figure 2-56
Configuration
The third navigation level is also implemented as the "swThirdNavigation" screen window in the "01_ScreenLayout"
screen. You can configure the page calls and add button text for the third-level navigation bar in the corresponding
screen, "05_ThirdNavigation". If you want to use the icon variant, you must configure the associated
"05_ThirdNavigation_Icons" screen and select it in the screen window under the "Screen" property.
Figure 2-57
Figure 2-58
Configuration:
A "Tab" view is already stored in the "Mixed Examples" folder in the library.
The contents of the tabs are each implemented in a separate screen. The different tabs allow you to set the respective
screen in the screen window via a "click" event.
Figure 2-59
Figure 2-60
To ensure that the scripts are executed correctly, the screen objects within the navigation must be
NOTE
numbered sequentially. The name before the number (e.g., "btnSubNav") can be freely defined, but
must remain the same for all elements.
e.g., "btnSubNav1", "btnSubNav2", "btnSubNav3", etc.
"HideMainNavigation" function
This script function hides the first navigation level "MainNavigation".
"HideSubNavigation" function
This script function hides the second navigation level "SubNavigation".
"HideThirdNavigation" function
This script function hides the third navigation level "ThirdNavigation".
NOTE The main navigation screen objects are named "txtMainNav.." by default. If you change the name of
the screen objects within the MainNavigation, you must adapt it in the script function as well.
NOTE The screen objects in the navigation are named "btnThirdNav..", "gfxThirdNavActive.." and
"gfxThirdNavNotActive.." by default. If you change the name of the screen objects within
ThirdNavigation_Icons, you must adapt it in the script function as well.
"ShowMainNavigation" function
The script function displays the first navigation level "MainNavigation".
If the second-level or third navigation level is displayed again after a screen change, the screen object
NOTE
specified with the "ButtonNumber" parameter is set to active.
Clicking the text of the "Title bar" will take you to the overview screen.
NOTE
The color of the left icon visualizes the current operating state of the system.
The color white is used for the "Status bar". This makes it stand out from the upper "Title bar" and the lower main window.
CurrentMachineState = 1
Figure 2-64
CurrentMachineState = 2-3
Figure 2-65
CurrentMachineState = 4
Figure 2-67
2.6.4. MainWindow
The screen edges of the operator panel are used for navigation or to display global functions. The control area of the plant
or the main window is located in the middle of the operator panel.
Figure 2-68
This is the area where the operator’s main attention is focused. For this reason, configure the visualization of the machine
in the main area of the operator panel. This central area takes up about 70% of the display area. The background color is
light gray. The contents of the main display can consist of additional tabs or controls for navigation within the screen.
Appearance
The uniform design of the buttons is ensured by the use of an operating concept. The following Table lists the objects in
your interface and what they mean.
Table 2-5
Object name Appearance Use/place of use
"Button" Standard button, for normal operating action e.g., executing a
function or opening a pop-up screen
"Cancel_Abort_ Close" Button to cancel actions or close pop-up screens.
→ no effect on the machine
"Delete" Button that triggers a delete action.
→ critical actions
"Execute_Action" Button for actions that have an effect on the machine, such as
executing script functions or setting machine parameters.
"StatusBar" Button for opening the pop-up screens of the Status bar, e.g.,
logon dialog or Recipe view.
To configure buttons without a color gradient, text fields were used in the "HMI Template Suite_V17
NOTE
(Unified)".
With WinCC Unified, the event "Click left mouse button" can also be used to execute "Events" on a "text
box". This is done using both mouse and touch operation.
Size
Present the text in such a way that the operators can recognize them quickly and reliably.
The font size used depends on the distance between the operator and the configured operator panel.
Font
"Siemens Sans" was used as the default font for all text and process values.
Appearance of texts
Table 2-6
2.6.7. Rectangles
Rectangle styles are defined with the main colors (Colors, see Section 2.4).
The rectangles are defined without a border so that they fit with the intended flat design.
Table 2-8
3. Library elements
This section explains the additionally available screens and screen objects and their intended use.
If you drag a device available in the global library into your project, all faceplates linked to the device
NOTE
are automatically created in the project library. You can find the faceplates you have created under
"Project library" > "Types".
Additional steps are not required.
NOTE If you drag a faceplate available in the global library directly into the project library or into the screen
where it is needed, the faceplate is automatically added to the project library.
Figure 3-2
Below you will find an overview of the faceplates in the HMI Template Suite.
"Progress Indicator"
The "progress indicator" can be used to visualize the progress of a process. Each point indicates a process step (see
Figure 3-3). As soon as the step has been completed, it is displayed in blue with a white checkmark. There are templates
with 3, 4, and 5 steps.
Figure 3-3
At the interface, you can select an INT tag for each step (2 = step completed, 1 = step active, 0 = step still pending).
Table 3-1
Interface Function
"Step1" Connect one HMI tag for each step.
"Step2" Depending on the value of the tag, the display changes as follows:
"Step3"
HMI tag = "0"
…
HMI tag = "1"
"Value Stepper"
The "Value Stepper" is an element with two buttons used to increase or decrease a value. The current value is displayed
between the two steppers.
Figure 3-4
The library contains different "Value Stepper" templates for REAL and INT variable values.
One tag for the incrementation (delta) and another for the process value must be connected to the control panel
interface.
Table 3-2
Interface Function
"Value" Connect to an HMI tag (Int/LReal).
If you click the "-" button, the tag value is reduced by the delta value.
If you click the "+" button, the tag value is increased by the delta value.
"Delta" Connect to an HMI tag (Int/LReal).
The "Value" tag is incremented or decremented by this value.
The following "value steppers" can be found in the HMI Template Suite.
Table 3-3
Faceplate name Appearance Benefits
"ValueStepperInt" Horizontal "value stepper" with rounded square buttons for
switching between the values for the process values and delta
values as INT tags with the output as an INT value
"ValueStepperInt_Vertical" Vertical "value stepper" with square buttons for switching between
the values for the process values and delta values as REAL tags with
output as INT values
"PieChart"
The "PieChart" is used to display KPI values. You can connect up to 5 parameters as INT tags to the interface and display
them in the diagram.
Figure 3-5
Table 3-4
Faceplate name Appearance Benefits
"BasicControlModulPopUp_Layer1" Faceplates for displaying a process variable on an
alternative gauge control
3.1.2. ContentBoard
The "ContentBoard" is a purely visual tool for grouping and structuring HMI elements on a screen.
The "ContentBoard" consists of a white rectangle. This rectangle is placed behind the HMI objects to represent a functional
context.
Configuration
Insert a new screen into your image and assign the color white to the rectangle.
Figure 3-6
You can use horizontal and vertical lines within the content board as additional structuring features.
NOTE
Figure 3-7
Figure 3-8
The screens serve as a template for your visualization. You still have to connect the objects properly so
NOTE
that the objects can display process values.
3.2.1. Dashboards
With a Dashboard, you can display the most important information and analyses such as the "efficiency" or "produced
quantity" of the machine. Furthermore, the most important HMI Screens are linked to it.
The Dashboard, therefore, displays the most important information about a machine and links to other HMI screens at a
glance.
In the library, different versions are preconfigured for different application scenarios. From the multitude of display
formats, you can always put together new Dashboards individually adapted to your machine. In addition to the two
variants shown, further variants are available in the library.
Figure 3-9
Figure 3-10
3.2.3. Wizard
Use
Use a "Wizard" to guide the operator through some steps in a predefined order.
The Wizard should always appear on the entire screen.
This allows the operator to concentrate fully on the current step. Only apply the new settings to the configuration once
the operator has completed all steps.
Versions with 3 to 5 steps are available in the Wizard.
Figure 3-11
3.2.4. Notifications
Use
Notifications are displayed at the bottom of the screen. If you are in second navigation level, the message overlays the
navigation elements (see Figure 3-12). If you do not use the second navigation level, the notification also appears along
the bottom of the screen.
Figure 3-12
4. Configuration notes
Requirements
Before you start configuring your HMI operator panel, you must prepare a complete design concept with concrete
visualization ideas.
If you need more information and tips on creating a design concept, take a look at the free "HMI
NOTE
Design Masterclass".
The "HMI Design Masterclass" gives you an introduction to the topic of HMI design in 7 x 10 min video
units.
Link to the Masterclass: https://new.siemens.com/global/en/products/automation/simatic-hmi/design-
masterclass.html
Figure 4-1
Figure 4-2
Frei verwendbar
8. Once you have selected the appropriate object, move the object to the project tree using the drag-and-drop feature. In
this case, the fully configured "MTP1200" is added to the project tree using "Add new device".
NOTE The operator panels are sorted by resolution in the "00 – Device" folder. All elements (navigation bars,
example screens, etc.) of the library are already included in these operator panels.
Figure 4-4
9. In the next step, copy the faceplate from the library into your project (see Section 3.1.1).
10. The operator panel is now fully configured. You can test it immediately with the runtime simulation or load it into a
real operator panel. For this, adjust the IP address to match your configuration.
Frei verwendbar
• German (Germany)
• English (United States)
For the project texts to be displayed correctly, the previously mentioned languages must be activated. Check the language
settings in your project.
4. Enter the name of the screen to be displayed in the center screen window.
5. Change the input mode for the screen window path to "String".
6. Enter the path "../swContent" in the field "Screen window path".
Figure 4-9
Runtime screen
NOTE
The button for accessing the currently active screen is always displayed in the accent color.
Highlighting the active screen is done using the script function "HighlightButton" in the Global Module
"Navigation".
By setting the "WindowFlags" property to zero, you hide all faceplate properties (frame, moveable,
NOTE
etc.).
Block background
To focus on the content of the screen (opened as a pop-up), the background is displayed as locked. For this purpose, a
semi-transparent rectangle has been configured in the "01_Screenlayout" screen in level 6. The rectangle is turned visible
when the screen is displayed.
Figure 4-11
On the left you can see 2 modules. The button allows you to then jump from the Dashboard to the Module
Overview.
Figure 4-13
5. Appendix
5.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.
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
V4.1 06/2023 Accessibility and procedure of the WinCC Unified V18 Wizards
V4.2 09/2024 Added "Unified Basic Panels" and adaptation to V18 Upd3