Remote Control Panels Audit DOCU v10 en

Application Example  02/2016
Remote Control of Operator

Panels in the Pharmaceutical
Environment
WinCC Audit (TIA Portal) and WinCC Sm@rtServer (TIA Portal)
https://support.industry.siemens.com/cs/ww/en/view/109482692
Warranty and Liability
Warranty and Liability

Note The Application Examples are not binding and do not claim to be complete
regarding the circuits shown, equipping and any eventuality. The Application
Examples do not represent customer-specific solutions. They are only intended
to provide support for typical applications. You are responsible for ensuring that
the described products are used correctly. These Application Examples do not
relieve you of the responsibility to use safe practices in application, installation,
operation and maintenance. When using these Application Examples, you
recognize that we cannot be made liable for any damage/claims beyond the
liability clause described. We reserve the right to make changes to these
Application Examples at any time without prior notice.
If there are any deviations between the recommendations provided in these
Application Examples and other Siemens publications – e.g. Catalogs – the
contents of the other documents have priority.
We do not accept any liability for the information contained in this document.
Any claims against us – based on whatever legal reason – resulting from the use of
the examples, information, programs, engineering and performance data etc.,
described in this Application Example shall be excluded. Such an exclusion shall
not apply in the case of mandatory liability, e.g. under the German Product Liability
Act (“Produkthaftungsgesetz”), in case of intent, gross negligence, or injury of life,
body or health, guarantee for the quality of a product, fraudulent concealment of a
deficiency or breach of a condition which goes to the root of the contract
 Siemens AG 2016 All rights reserved
(“wesentliche Vertragspflichten”). The damages for a breach of a substantial

contractual obligation are, however, limited to the foreseeable damage, typical for
the type of contract, except in the event of intent or gross negligence or injury to
life, body or health. The above provisions do not imply a change of the burden of
proof to your detriment.
Any form of duplication or distribution of these Application Examples or excerpts
hereof is prohibited without the expressed consent of the Siemens AG.
Security Siemens provides products and solutions with industrial security functions that
informa- support the secure operation of plants, systems, machines and networks.
tion 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 only
form one element of such a concept.
Customer is responsible to prevent unauthorized access to its plants, systems,
machines and networks. Systems, machines and components should only be
connected to the enterprise network or the internet if and to the extent necessary
and with appropriate security measures (e.g. use of firewalls and network
segmentation) in place.
Additionally, Siemens’ guidance on appropriate security measures should be
taken into account. For more information about industrial security, please visit
http://www.siemens.com/industrialsecurity.
Siemens’ products and solutions undergo continuous development to make them
more secure. Siemens strongly recommends to apply product updates as soon
as available and to always use the latest product versions. Use of product
versions that are no longer supported, and failure to apply 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 http://www.siemens.com/industrialsecurity.
Fernsteuerung von Bediengeräten

Entry ID: 109482692, V1.0, 02/2016 2
Table of Contents
Table of Contents
Warranty and Liability ................................................................................................. 2
1 Task ..................................................................................................................... 4
1.1 Overview............................................................................................... 4
1.2 Requirements ....................................................................................... 5
2 Solution............................................................................................................... 6
2.1 Overview............................................................................................... 6
2.2 Description of the core functionality ..................................................... 6
2.2.1 General ................................................................................................. 6
2.2.2 Combination of both options ................................................................ 7
2.3 Hardware and software components ................................................... 8
2.3.1 Validity .................................................................................................. 8
2.3.2 Components used ................................................................................ 8
3 Mode of Operation ............................................................................................. 9
3.1 Connection control ............................................................................... 9
4 Configuration and Settings............................................................................. 11
4.1 Configuring the server operator panel................................................ 11
4.2 Configuring the client.......................................................................... 16
4.3 Configuring another client .................................................................. 17
4.4 Configuring the controller ................................................................... 20
5 Installation and Commissioning .................................................................... 21

5.1 Preparation ......................................................................................... 21
5.2 Commissioning ................................................................................... 21
6 Operating the Application ............................................................................... 22
6.1 Client requests connection and server accepts ................................. 22
6.2 Client requests connection and server declines ................................ 24
7 Related Literature ............................................................................................ 26
8 History............................................................................................................... 26

Entry ID: 109482692, V1.0, 02/2016 3
1 Task
1.1 Overview
1 Task
1.1 Overview
Introduction
In plants requiring validation, it is important that all operator actions are recorded
and that they can be assigned to the corresponding operators.
In addition, there is the demand for “location-independent access to process data”.
Overview of the automation task

The figure below provides an overview of the automation task:
Figure 1-1
Description of the automation task

A plant is to be operated by means of operator panel A. All relevant operator
actions have to be recorded. In addition, it shall be possible to control the operator
panel remotely from a second different workplace by means of operator panel B.

Entry ID: 109482692, V1.0, 02/2016 4
1 Task
1.2 Requirements
1.2 Requirements
Requirements of the automation task
Table 1-1
Requirement Explanation
Only one user is allowed to operate. It has to be guaranteed that no other
operations can be performed remotely
when the operator panel is operated
directly.
It has to be ensured that no operations are
performed on the device when it is
controlled remotely.
If one operator panel connects with another, To ensure the uniqueness of the audit
the current user has to be logged off recording, only one operator can be logged
automatically. on.
The current user is only logged off
automatically after a re-registration period.
If the remote control is exited, the user has
to be logged off automatically.
The connection has to be disconnected Automatic disconnection is only enabled
automatically in order to avoid a permanent after a longer period with no operation
blocking of an operator panel. taking place.

In an audit trail, login and logoff processes
are to be recorded.

Entry ID: 109482692, V1.0, 02/2016 5
2 Solution
2.1 Overview
2 Solution
2.1 Overview
Schematic layout
The figure below shows a schematic overview of the most important components of the
solution:
Figure 2-1
This solution uses the following options of the TIA Portal:
- WinCC Audit (TIA Portal)

- WinCC Sm@rtServer (TIA Portal)
2.2 Description of the core functionality

2.2.1 General
WinCC Sm@rtServer (TIA Portal)

The “WinCC Sm@rtServer” option enables client/server access from one panel to
another. This is how the devices are “controlled remotely”. The Sm@rtServer
provides its screen content to the Sm@rtClient. The Sm@rtServer can be operated
via the Sm@rtClient.
In addition, the current process values can be accessed plant-wide and their
archiving and analysis can be provided.
Further information on WinCC Sm@rtServer is available here. \5\
WinCC Audit (TIA Portal)

The “WinCC Audit (TIA Portal)” option enables the recording of all relevant
operator actions of an operator panel.
Storing the production data in electronic form offers many advantages compared
with paper documentation, such as the simple recording and archiving of data.
However, at the same time it has to be ensured that the data are unforgeable and
can be read at any time.
Further information on “WinCC Audit (TIA Portal)” is available here. \6\

Entry ID: 109482692, V1.0, 02/2016 6
2 Solution
2.2 Description of the core functionality
2.2.2 Combination of both options
Illegal combination
If both options are combined, the requirements with regard to an application
requiring validation are not fulfilled since there is no interlock for “remote
control/remote service”.
Additional functionality
In addition to the use of both options, server and client are synchronized in this
application via the SIMATIC HMI HTTP protocol.
By means of this additional communication channel, the basic connection and the
interlock for the “remote control” are established.
Advantages of this solution

The solution presented here offers the following advantages:
• Only one client is allowed to operate at a time. Neither a second client nor the
server can “seamlessly” take over the operation.
• If a client connects with the server (to operate), the current user is
automatically logged off beforehand.
• If an (operating) client leaves the remote control screen in which the
Sm@rtClient is displayed, the current user will be logged off automatically.
Moreover, the Sm@rtServer is stopped, so that the client cannot automatically

re-establish the connection and the server is no longer blocked.
• If the connection to the (operating) client is interrupted, the current user is
automatically logged off – even if he previously performed this manually.
Moreover, the Sm@rtServer is stopped, so that the client cannot automatically
re-establish the connection and the server can be operated again.
• The clients separate the connection after a defined period of time, so that a
lock on the server is withdrawn again.
• The Sm@rtServer is only in operation when operated by means of the remote
control. Thus, resources can be saved.
• There is generally no limit for the number of possible connectable clients.
However, only one client can be operated at a time.

Entry ID: 109482692, V1.0, 02/2016 7
2 Solution
2.3 Hardware and software components
2.3 Hardware and software components

2.3.1 Validity
This application is valid for

• WinCC Comfort as of V13 SP1
• WinCC Audit (TIA Portal) as of V13 SP1
2.3.2 Components used
The application has been created with the following components:
Hardware components
Table 2-1
Component Qty Article number Note
TP1200 Comfort 1 6AV2124-0MC01-0AX0 Another Comfort Panel with a
different display size can be
used as well.
TP900 Comfort 1 6AV2124-0JC01-0AX0 Another Comfort Panel with a
different display size can be
used as well.
S7-1516 1 6ES7516-3AN00-0AB0 Alternatively, a different S7
controller can be used as well.
Software components
Table 2-2
Component Qty Article number Note
WinCC Comfort V13 1 6AV2101-0AA03-0AA5
SP1
WinCC Audit for 1 6AV2107-0RP00-0BB0
SIMATIC Panels
WinCC 1 6AV2107-0CP00-0BB0
Sm@rtServer for
SIMATIC panels
Example files and projects

The following list includes all files and projects that are used in this example.
Table 2-3
Component Note
109482692_CODE_v1.zip This zip file contains the STEP 7
project.
109482692_DOKU_v1_d.pdf This document

Entry ID: 109482692, V1.0, 02/2016 8
3 Mode of Operation
3.1 Connection control
3 Mode of Operation
General
In addition to the function of the two options Sm@rtAccess and Audit, the
connection control between server and client is controlled by means of an “HMI
HTTP communication”.
The basic functional mechanisms are explained below.
Overview of the sequence of the connection control

Figure 3-1
Connection
request
no no no
Request is Request Time elapsed
accepted rejected without response
yes yes
no
Upon signaling
of availability
Connection Connection is Connection

disconnected.
is Signaling that it will is
established be available soon. disconnected
no Time for no
Disconnection
by user disconnection
elapsed
yes yes
Connection
is
disconnected

Entry ID: 109482692, V1.0, 02/2016 9
3 Mode of Operation
Sequence of the connection control

Normally, the connection is established automatically via the “Sm@rtViewer Client
Control” (by selecting the screen into which the control is integrated). This
approach is not desired here.
The connection request is made via an additional operating screen. From this
screen, the user can send a connection request to the server.
The “Sm@rtViewer Client” cannot be started directly; an additional connection to
the server is not possible.
Table 3-1
Step Flowchart
Connection request (client  server)
1. The user requests the connection via the button.
2. The button sets the tag for the connection request.
3. The tag for connection request accesses the tags of the server via the HMI
HTTP protocol.
Thus, the connection request is known to the server.
Dialog for connection request (server)
4. A special screen is displayed once the client has set the bit for the connection
request.
5. The Sm@rtServer is started, if the request is accepted.

6. Another bit is set which the client can read via the HMI HTTP protocol.
Connection is established
7. The client detects the set bit for the connection approval via the HMI HTTP
protocol.
8. The Sm@rtViewer client is started and the connection is established.
Disconnecting the connection
9. By changing to another screen or after a lapse of the specified safety time, the
Sm@rtViewer client is exited by changing to another screen.

Entry ID: 109482692, V1.0, 02/2016 10
4 Configuration and Settings
4.1 Configuring the server operator panel

Contents of this chapter
This chapter shows you what configuration steps you have to carry out so that you
can expand your own project or a new project with the described functionalities.
The settings of the server are necessary to use the example project.

Activating the Sm@rtServer
Table 4-1
No. Action
1. In the project tree, navigate to the operator panel you want to use as Sm@rtServer
and open the Runtime settings.
2. Under “Services”, activate the entries “Start Sm@rtServer” and “HTTP Channel
Server”.
Settings of the Sm@rtServer
Table 4-2
No. Action Remark or figure
3. Open the “Control Panel” of your server e. g. when switching on the operator
operator panel, panel.
4. Open the “WinCC Internet Settings”
entry.
5. Go to the “Web Server” tab.

6. Accept the settings as shown in the
screen on the right.
“Tag access” has to be set to

"Read/write”, otherwise no mutual
communication will be possible.
“Start automatically after booting” has to
be enabled.
7. Click on the “User Administration”

button.

Entry ID: 109482692, V1.0, 02/2016 11

8. Create a new user.
For this purpose, click the “New” button.
Assign a user name and password.
Then, click the “Apply” button.
9. Select the newly created user from the

drop-down list and go to the
“Authorizations” tab.
10. Enable the “RTCommunication”
authorization for the user.
11. Confirm the dialog with “OK”.

12. Confirm the dialog for restart of the web
server also with "OK”.
13. Go to the “Remote” tab.
14. Disable the “Start automatically after
booting”
setting.
Note
“Start automatically after booting” has to
be disabled, because the server must
only be started upon connection
request.
15. Click the “Change settings” button.

Entry ID: 109482692, V1.0, 02/2016 12

16. Set the “No local input during client
sessions” option.
“No local input during client sessions”

has to be enabled as otherwise a local
user on the server (without
authorization) can withdraw operation
from a client and is then able to change
values on his own.
These modifications would then be
logged under the user from whom
operation has been withdrawn!
17. Assign a password under “Password 1”
that is not known to the user
and/customer.
18. Go to the “Query” tab.

19. Check whether the “Query console on
incoming connections” option is
disabled.
Note
The “Query settings” are not used, since

this is implemented by the WinCC
project.
The “Query console” deals with

requests for incoming connections. This
means that automatic acceptance of
SmartAccess requests thus can be
enabled.
However, this is not desired in this
application case.
20. Go to the “Administration” tab.
21. Accept the settings as shown in the
screen and confirm the dialog with “OK”.
Confirm the following dialog for the
restart of the remote server with "OK”.
Activate under “Forced Write Access” 

“Password needed”.
Note
The password is not needed in
operation and must not be known to
the user.
“Connection Priority” has to be

set to “Refuse concurrent conn.”.
Access attempts by an unauthorized
client (e. g. via Sm@rtClient.exe) can
thus be prevented during the time when
the Sm@rtServer is active (because it is
currently communicating).

Entry ID: 109482692, V1.0, 02/2016 13
Access to the “Control Panel” of the server operator panel

There must be no access to the Control Panel of the Sm@rtServer operator panel,
because this could change the WinCC Internet Settings and unauthorized people
could gain access to the operator panel.
There are two options:
• assigning a password (Table 4-3)
• setting the waiting time for the boot process to 0 seconds (Table 4-4)
Assigning a password
Table 4-3
1. Start the “Password” dialog in the
“Control Panel” of the server operator
panel.
2. Assign a password.
Note
The user must not know the password.
This password disables the Control

Panel. This means that without this
password you cannot go to the Control
Panel any longer.
3. Close the dialog with “OK”.
Reducing the waiting time for the boot process
Table 4-4
1. Start the “Transfer” dialog in the
“Control Panel” of the server operator
panel.
2. Set the time for delaying the boot
process to “0” seconds.
Note
If the ”OpenControlPanel” system
function is used in the configuration, it
has to be protected in such a way that
only authorized users can access the
Control Panel this way.
Thus, the panel no longer shows the

“Start Center” menu and you can no
longer go to the Control Panel during
ramp-up.
3. Close the dialog with “OK”.

Entry ID: 109482692, V1.0, 02/2016 14
Enabling a regulated project (WinCC Audit (TIA Portal))
Table 4-5
1. Open the Runtime settings of the
operator panel.
2. Select the “GMP” menu.

3. Enable the “Configuration conforms to

GMP” option.
Now the project is expanded by
configuration options to trace operator
actions.

Entry ID: 109482692, V1.0, 02/2016 15
4.2 Configuring the client
4.2 Configuring the client

Connection settings of the client
For the connection control, there is a communication between server and client via
the SIMATIC HMI HTTP protocol.
For this, two connections have to be explicitly created.
Table 4-6
1. In the project tree, open the
“Connections” editor of the operator
panel.
2. Create a new connection and select

“SIMATIC HMI HTTP” as
communication driver.
3. Enter the IP address of the server

operator panel as connection
parameter.
4. Use the data that you have assigned for
your server operator panel as user
name and password.
5. Repeat steps 2 to 4 for the second

connection.

Entry ID: 109482692, V1.0, 02/2016 16
4.3 Configuring another client

Configuration on the client
To add another client by means of the preconfigured project, the following changes
have to be made on the project.
Table 4-7
1. Copy the client operator panel to add
another client.
2. In the tag table (HMI tags >
Remote_Access > Tag table_1), set the
start value of the “Your_Clientnumber”
tag to the value of the client.
If you are to configure e. g. client 3, the
start value of the tag is to be set to
value “3”.
3. Adjust the address of the

“Connection_rejected” tag of your client.
Note
If you are to configure e. g. “Client
three”, the address is to be set to
“Client3_rejected”.

Entry ID: 109482692, V1.0, 02/2016 17
Configuration on the server

To add another client at the server, the following changes have to be made on the
project.
Table 4-8
No. Action
1. Create the “Clientx_rejected” tag under “TagsClient_SyncClients”.
Example: “Client3_rejected”
2. In the “Ask_for_Connection” script, add a new “Case” for the new client and adjust
the client number. The new “Case” always has to correspond to the client number.
3. In the “Clients_call” script, add a new “Case” for the new client and adjust the client
number. The new “Case” always has to correspond to the client number.

Entry ID: 109482692, V1.0, 02/2016 18
No. Action
4. In the “Clients_rejected” script, add a new “Case” for the new client and adjust the
tag (as explained in step 1).
The values from the script do not have to be adjusted.
The new “Case” always has to correspond to the client number.
5. In the “SmartClient_Test” script, add a new “Case” for the new client and adjust the
client number. The new “Case” always has to correspond to the client number.

Entry ID: 109482692, V1.0, 02/2016 19
4.4 Configuring the controller
4.4 Configuring the controller
Note The configurations of the operator panels access flag words and the clock
memory of the controller.
The flag words MW140 and MW142 are used. Observe these flag words, if you
integrate the example into an existing controller project.
Configuring the use of the clock memory

Check whether the clock memories are enabled correspondingly in the hardware
configuration of the controller used.
Table 4-9
1. Open the Device configuration of the
controller.
2. Open the Properties and go to the menu

“General > System and clock memory”.
3. Enable the use of clock memories.
4. Adjust the address of the clock memory

byte, if necessary.

Entry ID: 109482692, V1.0, 02/2016 20
5 Installation and Commissioning
5.1 Preparation
5 Installation and Commissioning

5.1 Preparation
General
Make sure that a controller and the two panels are located in an Industrial Ethernet
network and connected to the power supply.
Unzip the example project and open the project with the TIA Portal.
5.2 Commissioning
Adjusting the IP addresses to the operator panels
Table 5-1
No. Action
1. In the Control Panel of the two panels, change the IP addresses according to the specifications
of your network.
2. Assign an individual password in the safety settings of the Sm@rtServer.
Loading the server operator panel

Table 5-2
No. Action
1. Select the server operator panel.
2. Load the project into the operator panel as described in the manual.
WinCC V13 SP1 Manual > Visualize processes > Compiling and loading
Loading the client operator panel

Table 5-3
No. Action
1. Adjust the IP address of the server panel in the connection settings for the http connections.
Use the user name and password that you have assigned for the server operator panel.
2. Assign the IP address of the server panel in the General settings of the Sm@rtClient display.
3. Select the client operator panel.
4. Load the project into the operator panel as described in the manual.
WinCC V13 SP1 Manual > Visualize processes > Compiling and loading

Entry ID: 109482692, V1.0, 02/2016 21
6 Operating the Application
6.1 Client requests connection and server accepts

Table 6-1
No. Server Client
1.
Go to the “Application” screen.

2.
Enter the password you have assigned for

establishing a connection to the server.
To make an entry, you have to be logged on
as administrator:
(User: admin, password: 100)
Click the “Operation request” button.
3.
In the dialog opening now, you can decide how

to proceed.
Click the “Request” button and thus send a
request to the server.

Entry ID: 109482692, V1.0, 02/2016 22
No. Server Client

4.
A client request appears.

In the menu opening now, you can see which
client it is and how much time remains until the
automatic acceptance. You can accept this
request or decline it, and a reply will be sent
automatically to the client.
Click the “Accept” button.
5.
A connection has been established.

On the server, you can see the running To execute actions requiring validation, you
connection on the left top edge of the screen. have to authorize yourself as
"serviceengineer” with the password
It is displayed which client is connected
“serviceengineer”.
and how long it takes until
automatic logoff. The time until automatic logoff is displayed as
well.

Entry ID: 109482692, V1.0, 02/2016 23
6.2 Client requests connection and server declines

Table 6-2
No. Server Client
1.

2.
Enter the password you have assigned for

establishing a connection to the server.
To make an entry, you have to be logged on as
administrator:
(User: admin, password: 100)
Click the “Operation request” button.
3.
In the dialog opening now, you can decide how

to proceed.
Click the “Request” button and thus send a
request to the server.

Entry ID: 109482692, V1.0, 02/2016 24
No. Server Client

4.
A client request appears.

In the menu opening now, you can see which
client it is and how much time remains until the
automatic acceptance. You can accept this
request or decline it, and a reply will be sent
automatically to the client.
Click the “Reject” button.
5. A connection has not been established.

A connection has not been established.

A message for the operator is displayed
indicating the reason.

Entry ID: 109482692, V1.0, 02/2016 25
7 Related Literature
7 Related Literature
Table 7-1
Topic
\1\ Siemens Industry Online Support
https://support.industry.siemens.com
\2\ Download page of the entry
https://support.industry.siemens.com/cs/ww/en/view/109482692
\3\ Machine-oriented operator control and monitoring in the Online Support

https://support.industry.siemens.com/cs/ww/de/view/93905586
\4\ SIMATIC HMI operator panels
www.siemens.de/hmi-panels
\5\ WinCC Sm@rtServer
http://www.industry.siemens.com/topics/global/de/tia-portal/hmi-sw-tia-portal/wincc-
tia-portal-optionen/simatic-wincc-smartserver/Seiten/Default.aspx
\6\ WinCC Audit (TIA Portal)
http://www.industry.siemens.com/topics/global/de/tia-portal/hmi-sw-tia-portal/wincc-
tia-portal-optionen/simatic-wincc-audit/Seiten/Default.aspx
8 History
Table 8-1
Version Date Modification
V1.0 02/2016 First version

Entry ID: 109482692, V1.0, 02/2016 26

Remote Control Panels Audit DOCU v10 en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Remote Control Panels Audit DOCU v10 en

Uploaded by

Copyright:

Available Formats

Application Example  02/2016

Remote Control of Operator

Warranty and Liability

(“wesentliche Vertragspflichten”). The damages for a breach of a substantial

Fernsteuerung von Bediengeräten

5 Installation and Commissioning .................................................................... 21

Fernsteuerung von Bediengeräten

Overview of the automation task

Description of the automation task

Fernsteuerung von Bediengeräten

blocking of an operator panel. taking place.

Fernsteuerung von Bediengeräten

This solution uses the following options of the TIA Portal:

- WinCC Audit (TIA Portal)

2.2 Description of the core functionality

WinCC Sm@rtServer (TIA Portal)

WinCC Audit (TIA Portal)

Fernsteuerung von Bediengeräten

2.2.2 Combination of both options

Advantages of this solution

Moreover, the Sm@rtServer is stopped, so that the client cannot automatically

Fernsteuerung von Bediengeräten

2.3 Hardware and software components

This application is valid for

2.3.2 Components used

The application has been created with the following components:

Example files and projects

Fernsteuerung von Bediengeräten

Overview of the sequence of the connection control

accepted rejected without response

Connection Connection is Connection

Fernsteuerung von Bediengeräten

Sequence of the connection control

5. The Sm@rtServer is started, if the request is accepted.

Fernsteuerung von Bediengeräten

4 Configuration and Settings

4.1 Configuring the server operator panel

Settings of the Sm@rtServer

5. Go to the “Web Server” tab.

“Tag access” has to be set to

7. Click on the “User Administration”

Fernsteuerung von Bediengeräten

No. Action Remark or figure

9. Select the newly created user from the

11. Confirm the dialog with “OK”.

15. Click the “Change settings” button.

Fernsteuerung von Bediengeräten

No. Action Remark or figure

“No local input during client sessions”

18. Go to the “Query” tab.

The “Query settings” are not used, since

The “Query console” deals with

Activate under “Forced Write Access” 

“Connection Priority” has to be

Fernsteuerung von Bediengeräten

Access to the “Control Panel” of the server operator panel

This password disables the Control

Reducing the waiting time for the boot process

Thus, the panel no longer shows the

Fernsteuerung von Bediengeräten

Enabling a regulated project (WinCC Audit (TIA Portal))

2. Select the “GMP” menu.

3. Enable the “Configuration conforms to