WinCC SCADA · Lab Manual

WinCC SCADA User Administration and Security: Authorisation Levels, Audit Trail and PLC Release Lab Manual (V8.1)

SCADA security is only as strong as the PLC behind it. This lab manual secures a WinCC Explorer V8.1 station through all six stages – a maintenance key switch, a PLC release in ladder and SCL, User Administrator groups and levels, object authorisation, automatic logout and an operator-input audit trail – and tests each user live.

2,500+ engineers trained 4.9/5 Google rating 21+ years, Chinchwad, Pune Next batch: contact for dates
Quick answer

Create groups and users in the WinCC User Administrator with the authorisation levels each role needs and an automatic logout, set the Authorization property on every operable object, enable operator input messages for an audit trail, and let the PLC (ladder or SCL) release critical functions only when the authorised WinCC request and a physical key switch agree.

  • Authorise objects, not people: groups carry the levels.
  • Audit every value change and command.
  • The PLC enforces critical rights – request AND key.

The WinCC User Administrator

The User Administrator holds groups, users and numbered authorisation levels. Objects in Graphics Designer reference a level; a user can operate the object only if their group has it. Automatic logout, password rules and, with SIMATIC Logon, central Windows accounts complete the picture.

Lab Flow: From Key Switch to a Secured WinCC Station

Every lesson in the Softwell PLC lab manual series follows the same six stages and the same address rule, so the code you write here plugs straight into the HMI lessons.

Lab manual flow: field input to tested HMI screenSix stages: field device and PLC tag, input mapping to DB_IO, PLC logic, HMI tags, graphics linking, and perform and test.1Field + tags%I9.6 S70key switch2Input mappingFC_InputMapping→ DB_IO3LogicMaint releaseLAD + SCL4WinCC tagsDB_Access_*request, enable5Graphicslevels, auditUser Administrator6Perform + testSimulatoreach roleAddress rule for every lesson: %I only in FC_InputMapping, %Q only in FC_OutputMapping, symbolic DB members everywhere else – including the HMI.
Figure 1 – Six-stage lab flow for this lesson.

Stage 1Field Wiring and PLC Tag

PLC tagAddressTypeDevice / comment
S70_KeyMaint%I9.6BoolMaintenance key switch, 1 = MAINT

Stage 2Input Mapping into DB_IO

// FC_InputMapping
"DB_IO".S70_KeyMaint     := "S70_KeyMaint";

Stage 3PLC Logic in Ladder and SCL

Maintenance release: WinCC authorisation AND key switchLadder diagram: Network 1 — Maintenance mode only with SCADA request (authorised button) AND physical key; Network 2 — Request expires after 10 min (TON) or when the key is turned backNetwork 1 — Maintenance mode only with SCADA request (authorised button) AND physical keyS70_KeyMaint"DB_IO"Maint_Req"DB_Access" (from WinCC)Any_Fault"DB_Alarm"Maint_Enable"DB_Access"Network 2 — Request expires after 10 min (TON) or when the key is turned backT_ReqAlive.Q"T_ReqAlive" TON 10 minMaint_Req_Timeout"DB_Access" → resets Maint_Req
Figure 2 – Maintenance release in ladder: WinCC request AND key AND no fault.

The same logic in SCL – use whichever your plant standard prefers; both write the same DB members that WinCC reads:

// FC_AccessControl – SCL equivalent
"DB_Access".Maint_Enable := "DB_IO".S70_KeyMaint AND "DB_Access".Maint_Req AND NOT "DB_Alarm".Any_Fault;
"T_ReqAlive"(IN := "DB_Access".Maint_Req, PT := T#10M);          // request expires after 10 min
IF "T_ReqAlive".Q OR NOT "DB_IO".S70_KeyMaint THEN
    "DB_Access".Maint_Req := FALSE;                     // never rely on WinCC alone
END_IF;
// The PLC enforces the right; WinCC only asks for it.
"DB_Manual".Jog_Allowed := "DB_Access".Maint_Enable;

Stage 4Link PLC Tags to WinCC

In Tag Management add the SIMATIC S7-1200, S7-1500 Channel, create a connection with the CPU IP address, then use AS Symbols to load the PLC symbols and drag the DB members you need into a tag group. The DB members must have Accessible from HMI ticked in TIA Portal. Names and menus can differ slightly between WinCC versions.

WinCC tagData typeConnection / addressUsed by
DB_Access_Maint_ReqBinarysymbolicButton with level 1001 Maintenance
DB_Access_Maint_EnableBinarysymbolicMaintenance panel visibility

Stage 5User Administrator, Object Authorisation and Audit

GroupAuthorisation levelsAuto logout
OperatorsValue input, process controlling, change screen, acknowledge alarms10 min
MaintenanceOperators + 1001 Maintenance (custom level)5 min
AdministratorsAll, including user administration5 min
#ObjectPropertiesTag / event
①Login / Logout buttonsLogin dialog via a short C or VB action, or the configured hotkey–
②Command buttons and I/O fieldsMiscellaneous → Authorization; Operator-Input Message enabledProcess tags
③Button Request maintenanceAuthorization 1001 MaintenanceDB_Access_Maint_Req
④Maintenance groupDisplay dynamic on Maint_EnableDB_Access_Maint_Enable
⑤AlarmControl (operator messages)Filter on operator input messages for the audit viewAlarm Logging

The panel version with backup is in HMI user administration and backup.

Stage 6Perform and Test: Login, Authorisation Levels and Audit Trail

Log in as different users and see which objects their authorisation levels unlock. Request maintenance with and without the key switch, wait for the automatic logout, and read the operator-input audit trail. Passwords are for this simulation only.

oper / 1111 · maint / 2222 · admin / 3333
Key switch and PLC
WinCC Runtime · Line screen
Line.pdl ·
Operator input messages (audit trail)

Troubleshooting

SymptomLikely causeFirst check
Everyone can operate a buttonNo Authorization on the objectObject properties
Maintenance enabled without keyRelease only in WinCCPLC rung must include the key
No record of a changeOperator input message not enabledObject property
User stays logged inNo automatic logoutUser Administrator settings

Hands-On Lab: Secure a WinCC Station and Prove the Audit Trail

Hands-on
Before you start
  • TIA Portal and WinCC Explorer V8.1
  • Estimated time: 75 minutes
1

Wire and declare the key switch

Declare S70_KeyMaint.

Key switch declared.
2

Map into DB_IO

Copy the key switch in FC_InputMapping.

DB_IO.S70_KeyMaint follows the key.
3

Write the release in ladder and SCL

Maint_Enable from key, WinCC request and no fault; request timeout.

Ladder and SCL release behave identically.
4

Load the tags into WinCC

Load DB_Access members.

Tags appear in WinCC.
5

Configure User Administrator and objects

Groups, users, levels, auto logout; Authorization on objects; operator input messages; login/logout buttons.

Each object requires its level; changes are logged.
6

Test every role

Log in as each user, request maintenance with and without the key, check the audit trail and the auto logout.

Each role sees exactly its rights; maintenance needs request and key.
Checkpoint—how to know you did it right

Each role can do exactly what its levels allow, every change is recorded, and maintenance mode is impossible without the physical key.

Frequently asked questions

What are authorisation levels in the WinCC User Administrator?

Numbered rights such as user administration, value input, process controlling or acknowledging alarms. Groups get a set of levels, users belong to groups, and each screen object references the level it needs.

How do I protect a button or an I/O field?

Set its Authorization property to the required level. Without that level the object cannot be operated; add an Operator-Control Enable dynamic if it should also look disabled.

How do I get an audit trail of operator actions?

Enable operator input messages on the objects that change values or send commands, so Alarm Logging records who changed what and when, and archive those messages.

What is SIMATIC Logon?

An option that uses Windows or domain users for WinCC log-in, giving central password rules, account lock-out and an audit of log-ins across stations.

Why combine a WinCC right with a key switch in the PLC?

A password can be shared and WinCC is not the only client of the PLC. The PLC enforces maintenance mode only when the authorised request and the physical key agree.

Should the PLC logic be ladder or SCL?

The release is a three-contact rung, ideal for ladder; the request timeout is equally short in SCL. Both are shown.

Reviewed by Bhawesh Kumar SinghIndustrial Automation Trainer and Industry 4.0 Consultant · Softwell Automation · 21+ years industry experience

Get the full syllabus + free demo class

Share your details—a Softwell training advisor will contact you with batch dates, fees and hardware-practice options.

No spam. Used only to share course details for this enquiry.

Learn with practical industrial examples

Join live online, Pune classroom or corporate in-plant automation training.

Request Course Details
Verified learning pathway

Discuss WinCC SCADA User Administration

Explore practical curriculum, software, hardware and batch options for this technology.

Content reviewed: 16 October 2026

Siemens PLC & TIA Portal Learning Path

Continue with the related Siemens PLC tutorials in this practical learning series.

  1. SCL vs Ladder Logic
  2. Upload PLC Program
  3. TIA Selection Tool
  4. Analog Input Scaling
  5. PLC Counters
  6. PLC Timers
  7. Addressing & Data Types
  8. Hardware & PLC Tags
  9. OB, FB, FC & DB
☎ Call WhatsApp ✉ Email Enquire Now