WinCC Explorer SCADA Manual
WinCC Explorer Runtime Practical Manual

Official Philosophy: Open the software, open the Softwell Notebook, and perform the practical.

20 Complete WinCC Lab Practicals
No-Skipped-Step Workflow
WinCC Explorer Only
Classic SCADA Engineering

Softwell
Digital Practical
Notebook

[check] Prepare -> Configure -> Run -> Test -> Diagnose -> Record

COMPLETE STEPS * WINCC LABS
No-skipped-step edition

How to Use This WinCC Explorer Lab Notebook

Complete the labs in order. Do not advance until Runtime verification passes, faults are corrected and the evidence fields are completed.

1. PrepareConfirm WinCC version, licences, computer name, data source, accounts and safe test scope.
2. ConfigureFollow every editor path, object name, connection, tag, screen, alarm, script and data-setting action.
3. ProveStart Runtime, test normal and failure states, inspect quality/logs and correct every failed check.
4. RecordWrite actual values, filenames, users, diagnostics, recovery times and trainer verification.
Dedicated scope: WinCC Explorer project engineering, PLC/OPC UA tags, graphics, faceplates, alarms, archives, reports, users, Runtime, client-server, redundancy, diagnostics, backup and FAT. Scripting and data-integration training is provided in separate manuals.
P01WinCC Explorer

Softwell Complete WinCC Practical Notebook

Practical 01 - Create and Standardize a WinCC Explorer Project

Objective: Create a controlled WinCC project, configure the target computer and produce a restorable baseline backup.

WinCC ExplorerProject SetupComputer PropertiesBaseline Backup10 Guided Steps
Prerequisite

SIMATIC WinCC Explorer installed and licensed; project type and target computer name confirmed.

Required Setup

Engineering/runtime computer with an approved local project folder and administrator rights where required.

Safety / Data Gate

No plant connection is required. Use a training project and never overwrite an active runtime project.

Completion Rule

All steps checked, Runtime verification passed, faults corrected and evidence recorded.

01
STEP 01 - Record the software baseline

Write the WinCC version/service pack, Windows version, licence status, computer name and student name before creating the project.

02
STEP 02 - Start WinCC Explorer

Open SIMATIC WinCC Explorer. Close any unrelated project and confirm that no production Runtime process is active.

03
STEP 03 - Create the correct project type

Select File > New, choose the trainer-approved Single-User project and continue. Do not select Multi-User/Client unless the architecture requires it.

04
STEP 04 - Name and locate the project

Enter L02_WinCC_StudentName and save it in the approved training folder, not Downloads, Desktop or a temporary path.

05
STEP 05 - Verify project components

Confirm Computer, Tag Management, Graphics Designer, Alarm Logging, Tag Logging, Text Library, User Administrator and Global Script appear in the project tree.

06
STEP 06 - Configure the computer name

Open Computer > Properties and enter/select the actual Windows computer name. Record it exactly, including spelling.

07
STEP 07 - Set graphics/runtime defaults

In Computer properties configure the approved start picture, language, screen resolution and full-screen/window behavior where available.

08
STEP 08 - Set project information

Add customer/training batch, author, description and revision R00 in the available project documentation fields or change record.

09
STEP 09 - Close and reopen the project

Save, close WinCC Explorer and reopen the project from its saved location. Confirm that the computer configuration is retained.

10
STEP 10 - Create baseline backup

Use WinCC Project Duplicator or the approved archive method while Runtime is stopped. Save L02_WinCC_R00 and record the backup path/date.

B. Verification Checklist

C. If the Result Is Wrong

Observed issueCheck / correction
Project will not openCheck WinCC version/project migration and folder permissions.
Computer name mismatchUpdate Computer properties to the actual runtime computer, then reopen.
Backup failsStop Runtime and WinCC processes that lock project files.

D. Student Evidence Record

WinCC version
Project path
Computer name
R00 backup
Student signatureTrainer verificationDate

Expected Result

A named, computer-matched and backed-up WinCC Explorer project is ready for engineering.

P02WinCC Explorer

Softwell Complete WinCC Practical Notebook

Practical 02 - Configure S7 PLC Communication

Objective: Create a Siemens S7 connection, verify PLC addressing and prove live communication before building screens.

S7 Protocol SuiteTCP/IPPLC ConnectionDiagnostics10 Guided Steps
Prerequisite

P01 complete; PLC IP, CPU family, rack/slot and tested PLC tags available.

Required Setup

WinCC computer and S7-1200/S7-1500 PLC on the same approved network or simulator path.

Safety / Data Gate

Use a read-only test tag first. Do not create command tags until communication quality is proven.

Completion Rule

All steps checked, Runtime verification passed, faults corrected and evidence recorded.

01
STEP 01 - Record the network plan

Write the WinCC PC IP, PLC IP, subnet mask, CPU type and communication method. Confirm no duplicate addresses.

02
STEP 02 - Verify basic reachability

Check Ethernet link and use the approved ping/accessible-device method. Resolve subnet, cable or firewall problems before WinCC configuration.

03
STEP 03 - Add the Siemens driver

Under Tag Management add SIMATIC S7 Protocol Suite if it is not already present.

04
STEP 04 - Select the channel unit

Choose the TCP/IP or Industrial Ethernet channel unit supported by the installed WinCC/CPU combination.

05
STEP 05 - Create the PLC connection

Add connection PLC_01. Enter the verified PLC IP and the correct rack/slot or CPU-specific connection parameters.

06
STEP 06 - Create one read test tag

Under PLC_01 create PLC_Heartbeat using the exact PLC address/data type supplied by the PLC project.

07
STEP 07 - Create one safe write test tag

Create SCADA_TestBit mapped to an approved non-safety PLC test bit; keep all real commands excluded.

08
STEP 08 - Configure acquisition

Set a sensible acquisition/update cycle such as 500 ms or 1 s for test tags. Avoid unnecessarily fast cycles.

09
STEP 09 - Start required Runtime components

Enable Tag Management/Graphics Runtime in Computer startup settings, start Runtime and monitor the read value and quality.

10
STEP 10 - Prove read/write and recovery

Change PLC_Heartbeat, verify WinCC updates, write SCADA_TestBit, then interrupt/reconnect communication and record quality recovery.

B. Verification Checklist

C. If the Result Is Wrong

Observed issueCheck / correction
Bad qualityCheck IP, rack/slot, driver/channel unit, firewall and PLC access settings.
Read works but write failsCheck tag write permission, PLC address and CPU protection.
Slow updateCheck tag cycle, network load and PLC/WinCC diagnostics.

D. Student Evidence Record

Connection name
PLC IP/rack/slot
Read quality
Fault/recovery result
Student signatureTrainer verificationDate

Expected Result

WinCC Explorer exchanges verified read/write test data with the intended Siemens PLC.

P03WinCC Explorer

Softwell Complete WinCC Practical Notebook

Practical 03 - S7-1500 OPC UA with UAExpert and WinCC

Objective: Validate the PLC OPC UA server with UAExpert, configure a secure WinCC client connection and import approved nodes.

OPC UAUAExpertCertificatesWinCC Client10 Guided Steps
Prerequisite

S7-1500 OPC UA server enabled; endpoint, security policy and user credentials supplied; required WinCC OPC option licensed.

Required Setup

PLC, WinCC computer and UAExpert on an approved training network with synchronized date/time.

Safety / Data Gate

Expose/write only designated test variables. Never permit anonymous writes to process commands.

Completion Rule

All steps checked, Runtime verification passed, faults corrected and evidence recorded.

01
STEP 01 - Record endpoint/security

Write the opc.tcp://PLC-IP:port endpoint, security policy, message mode, username method and expected server certificate identity.

02
STEP 02 - Verify with UAExpert first

Add the endpoint in UAExpert, select the planned security/user settings and connect before changing WinCC.

03
STEP 03 - Trust the server certificate

Review the certificate subject, host/IP and validity period; trust only the expected PLC certificate.

04
STEP 04 - Browse approved nodes

Use UAExpert to locate the provided namespace/PLC tags. Record NodeId, data type, value, quality and timestamp for one read tag.

05
STEP 05 - Test the safe node

Write only the designated test node and confirm the PLC receives it. Restore the test value after verification.

06
STEP 06 - Add the WinCC OPC UA channel

In Tag Management add/configure the installed OPC UA client/channel. If unavailable, stop and confirm licensing/options rather than using an unrelated driver.

07
STEP 07 - Create the WinCC connection

Enter the verified endpoint, security policy, certificate and credentials matching the successful UAExpert session.

08
STEP 08 - Exchange client trust

Where required export/trust the WinCC client certificate at the PLC and trust the PLC server certificate on the WinCC computer.

09
STEP 09 - Browse/import selected items

Use the channel's item browser/import function to add only approved OPC UA nodes with meaningful WinCC tag names.

10
STEP 10 - Run and test diagnostics

Start Runtime, confirm value/quality/timestamp, test the safe write and document one certificate or credential failure plus recovery.

B. Verification Checklist

C. If the Result Is Wrong

Observed issueCheck / correction
BadCertificateUntrustedExchange/trust the correct PLC and WinCC certificates.
BadUserAccessDeniedCheck user credentials and node read/write rights.
No OPC UA channelVerify installed WinCC connectivity option and licence.

D. Student Evidence Record

Endpoint
Security policy
Imported NodeId/tag
Failure/recovery
Student signatureTrainer verificationDate

Expected Result

S7-1500 OPC UA data is independently verified and securely available in WinCC Runtime.

P04WinCC Explorer

Softwell Complete WinCC Practical Notebook

Practical 04 - Process/Internal Tags, Groups and Quality

Objective: Create a maintainable tag structure with correct data types, addresses, cycles, limits and communication-quality handling.

Tag ManagementProcess TagsInternal TagsQuality10 Guided Steps
Prerequisite

P02 or P03 communication works; approved PLC/OPC tag list available.

Required Setup

WinCC project with at least one live connection and a tag import worksheet.

Safety / Data Gate

Command tags must be clearly separated from status tags and protected by PLC permissives.

Completion Rule

All steps checked, Runtime verification passed, faults corrected and evidence recorded.

01
STEP 01 - Prepare the tag standard

Define equipment prefix, signal suffix, engineering units, description and group convention before entering tags.

02
STEP 02 - Create connection groups

Under the PLC/OPC connection create groups such as Motor01, Analog, Alarms and Commands.

03
STEP 03 - Create status tags

Add BOOL tags for Ready, Running, Fault and permissives using exact PLC address/OPC item and meaningful comments.

04
STEP 04 - Create command tags

Add Start, Stop/Reset and mode/setpoint tags only from the approved PLC interface DB or test area.

05
STEP 05 - Create analog tags

Use matching INT/REAL types, engineering units, display limits and suitable acquisition cycles.

06
STEP 06 - Create internal tags

Add internal tags for current picture, logged-in user message, report filters and UI-only states; do not give them PLC addresses.

07
STEP 07 - Import in a controlled batch

If importing CSV/tag tables, test a small sample, review address/data type and then import the remaining approved list.

08
STEP 08 - Check duplicates and references

Sort/search for duplicate names, addresses and unused tags; use cross-reference/tag usage where available.

09
STEP 09 - Create a tag test picture

Display value and quality for representative BOOL, analog, command and internal tags.

10
STEP 10 - Run the tag acceptance test

Test normal values, bad communication quality, out-of-range analog data and write permission; sign the tag worksheet.

B. Verification Checklist

C. If the Result Is Wrong

Observed issueCheck / correction
Wrong numeric valueCheck PLC/WinCC data type, byte order and scaling location.
Tag stays staticCheck acquisition cycle, address and PLC value.
Command tag unsafeMove command validation/permissive logic to the PLC interface.

D. Student Evidence Record

Tag standard
Imported count
Quality test
Signed tag worksheet
Student signatureTrainer verificationDate

Expected Result

WinCC tags are structured, typed, traceable and tested for normal and bad-quality states.

P05WinCC Explorer

Softwell Complete WinCC Practical Notebook

Practical 05 - Graphics Designer Screen Standard

Objective: Create a consistent process-screen template with correct dimensions, layers, naming, alignment and reusable visual standards.

Graphics DesignerPDLScreen StandardLayers10 Guided Steps
Prerequisite

P04 tag structure complete; approved resolution, colors and navigation standard available.

Required Setup

WinCC Graphics Designer and a project graphics folder for images/symbols.

Safety / Data Gate

This lab uses display objects only; no live command actions are added.

Completion Rule

All steps checked, Runtime verification passed, faults corrected and evidence recorded.

01
STEP 01 - Create the base picture

Open Graphics Designer, create Overview.pdl and set the approved runtime width/height and background.

02
STEP 02 - Configure grid and layers

Set grid/snap, open layer controls and reserve layers for background, equipment, values, alarms and navigation.

03
STEP 03 - Add header/footer zones

Create fixed areas for plant/title, date/time, logged-in user, communication status and navigation.

04
STEP 04 - Add process layout

Draw a simple tank/pump/valve/conveyor layout using consistent line widths, flow direction and spacing.

05
STEP 05 - Name every important object

Use names such as objMotor01, ioLevelPV and txtCommStatus; do not retain generic Rectangle1 names.

06
STEP 06 - Apply alignment tools

Use align, distribute, size and grouping tools rather than positioning repeated objects by eye.

07
STEP 07 - Add static labels and units

Show equipment tags, signal descriptions and engineering units close to the related value.

08
STEP 08 - Create reusable visual states

Define the approved neutral, running, warning, fault and bad-quality colors without relying only on red/green where accessibility matters.

09
STEP 09 - Save and set start picture

Save Overview.pdl, update Computer Graphics Runtime start picture and verify the correct project path.

10
STEP 10 - Run a visual acceptance check

Start Graphics Runtime and check clipping, overlap, resolution, readability and consistent object naming; record corrections.

B. Verification Checklist

C. If the Result Is Wrong

Observed issueCheck / correction
Picture is croppedMatch picture and runtime resolution/settings.
Objects shift/overlapUse grid, align and group tools; retest at target resolution.
Text unreadableIncrease font/contrast and shorten labels without removing units.

D. Student Evidence Record

Picture filename
Target resolution
Object-name sample
Visual review result
Student signatureTrainer verificationDate

Expected Result

A readable and maintainable WinCC process-screen standard is established.

P06WinCC Explorer

Softwell Complete WinCC Practical Notebook

Practical 06 - Dynamic Objects, I/O Fields and Safe Commands

Objective: Connect process tags to visual properties and build operator commands with validation, confirmation and feedback.

Dynamic DialogI/O FieldButtonsCommand Feedback10 Guided Steps
Prerequisite

P04 tags and P05 Overview picture complete.

Required Setup

Live/simulated PLC tags for motor command, status, fault, analog PV and setpoint.

Safety / Data Gate

Use approved test commands. PLC logic must enforce permissives; screen animation is never a safety function.

Completion Rule

All steps checked, Runtime verification passed, faults corrected and evidence recorded.

01
STEP 01 - Display analog PV

Insert an I/O field, connect Level_PV, set output format/decimals and show engineering units.

02
STEP 02 - Configure setpoint entry

Insert an input field for Level_SP, apply display/input limits and require an authorized user level where supported.

03
STEP 03 - Animate motor state

Connect motor Running/Fault/Ready tags to fill color or symbol state with an explicit bad-quality appearance.

04
STEP 04 - Animate valve position

Use open/closed feedback to show Open, Closed, Moving and Contradictory/Unknown states.

05
STEP 05 - Create start button

Add a button action that writes only the approved PLC command bit/pulse and labels the requested action clearly.

06
STEP 06 - Create stop/reset controls

Use separate Stop and Fault Reset actions. Reset must not issue Start or hide an active process cause.

07
STEP 07 - Add command confirmation

For consequential commands, show a confirmation with equipment name and requested action before writing.

08
STEP 08 - Add feedback indication

Show command accepted, running feedback, rejected/permissive status and fault message instead of changing color immediately on click.

09
STEP 09 - Test normal and rejected commands

In Runtime test start/stop/setpoint, missing permissive, fault and bad communication; record screen and PLC responses.

10
STEP 10 - Review command security

Confirm limits, authorization and PLC validation remain effective after Runtime restart and user logout.

B. Verification Checklist

C. If the Result Is Wrong

Observed issueCheck / correction
Object color never changesCheck tag link, quality and dynamic trigger.
Setpoint accepts unsafe valueAdd UI limits and PLC-side clamping/validation.
Button appears to work but PLC does notCheck write permission, tag address and PLC command interface.

D. Student Evidence Record

PV/setpoint test
Command confirmation
Rejected-command test
Bad-quality display
Student signatureTrainer verificationDate

Expected Result

Process values, animations and operator commands behave safely and transparently in Runtime.

P07WinCC Explorer

Softwell Complete WinCC Practical Notebook

Practical 07 - Navigation, Popups and Reusable Equipment Views

Objective: Build predictable navigation and a reusable equipment popup/faceplate pattern with parameterized tag context.

NavigationPopupFaceplate PatternReusable Graphics10 Guided Steps
Prerequisite

P05-P06 process screen and equipment tags available.

Required Setup

Overview plus placeholder Detail, Alarms and Trends pictures.

Safety / Data Gate

Closing or changing pictures must not clear PLC commands, alarms or safety states.

Completion Rule

All steps checked, Runtime verification passed, faults corrected and evidence recorded.

01
STEP 01 - Create navigation pictures

Create Detail.pdl, Alarms.pdl and Trends.pdl with the same header/footer standard.

02
STEP 02 - Create navigation buttons

Add Overview, Detail, Alarms and Trends buttons using the approved picture-change function/action.

03
STEP 03 - Show current picture state

Use an internal tag/object style so the active destination is clear and a button cannot create duplicate popups.

04
STEP 04 - Create equipment popup

Build MotorPopup.pdl with equipment name, mode, command, feedback, permissive and fault fields.

05
STEP 05 - Define context parameters

Use a documented equipment prefix/structure or picture-tag method to connect the popup to the selected motor instance.

06
STEP 06 - Open popup from equipment

Configure the motor symbol click/action to set the context and open the popup at a controlled position.

07
STEP 07 - Add popup close and focus behavior

Provide a clear close button and verify the popup does not hide critical alarm/navigation areas.

08
STEP 08 - Test two equipment instances

Open the same reusable popup for Motor01 and Motor02 and verify every displayed/command tag changes to the correct context.

09
STEP 09 - Test navigation persistence

Navigate between pictures and confirm current user, alarm status and communication indication remain visible.

10
STEP 10 - Document the template

Record picture names, context convention, object names and required tags for future reuse.

B. Verification Checklist

C. If the Result Is Wrong

Observed issueCheck / correction
Popup shows wrong motorCorrect the context/prefix assignment before opening.
Multiple popups accumulateUse one controlled popup instance or close existing instance.
Navigation button does nothingCheck picture filename and action/event assignment.

D. Student Evidence Record

Picture list
Popup context method
Motor01/Motor02 tests
Navigation test
Student signatureTrainer verificationDate

Expected Result

The project has consistent navigation and a tested reusable equipment-popup pattern.

P08WinCC Explorer

Softwell Complete WinCC Practical Notebook

Practical 08 - Alarm Logging Configuration

Objective: Create structured discrete/analog alarms with classes, priorities, texts, timestamps and acknowledgement behavior.

Alarm LoggingAlarm ClassesPrioritiesMessages10 Guided Steps
Prerequisite

P04 alarm tags and an approved alarm list available.

Required Setup

PLC/simulator can generate warning, trip and analog-limit conditions.

Safety / Data Gate

Do not suppress real faults during tests; use dedicated training alarm bits/values.

Completion Rule

All steps checked, Runtime verification passed, faults corrected and evidence recorded.

01
STEP 01 - Prepare the alarm list

Record alarm number, source tag, trigger condition/bit, class, priority, text, acknowledgement and reset philosophy.

02
STEP 02 - Open Alarm Logging

Start the Alarm Logging editor and review message classes/types available in the installed WinCC version.

03
STEP 03 - Configure classes and colors

Create/verify Warning, Fault and System/Communication classes with approved colors and acknowledgement rules.

04
STEP 04 - Create a discrete warning

Add a message for a training warning bit, set number, text, class, priority and trigger.

05
STEP 05 - Create a trip alarm

Add motor overload/no-feedback alarm using the PLC-provided alarm bit and equipment-specific message text.

06
STEP 06 - Create analog limit alarms

Use approved high/low alarm bits from the PLC or supported analog monitoring; retain PLC delay/hysteresis philosophy.

07
STEP 07 - Add message values/text

Include equipment tag, process value/batch/operator fields only where correctly configured and meaningful.

08
STEP 08 - Configure acknowledgement

Set single/group acknowledgement as approved; acknowledgement must not reset the PLC fault cause.

09
STEP 09 - Save/activate components

Save Alarm Logging configuration and confirm Alarm Logging Runtime is included in Computer startup.

10
STEP 10 - Generate each alarm

Start Runtime, trigger warning/trip/high/low in order and record appear time, class, priority, state change and disappear behavior.

B. Verification Checklist

C. If the Result Is Wrong

Observed issueCheck / correction
Alarm does not appearCheck trigger tag/bit, Alarm Logging Runtime and message activation.
Wrong alarm textCorrect message number/source mapping and text fields.
Alarm disappears unexpectedlyReview latching/reset philosophy in PLC and alarm configuration.

D. Student Evidence Record

Alarm list filename
Message numbers tested
Timestamp result
Class/priority result
Student signatureTrainer verificationDate

Expected Result

WinCC alarm messages are consistently configured and proven against the approved alarm list.

P09WinCC Explorer

Softwell Complete WinCC Practical Notebook

Practical 09 - Alarm Control, Acknowledgement and Audit Test

Objective: Build an operator alarm page and prove filtering, acknowledgement, user authorization and audit evidence.

Alarm ControlAcknowledgeFiltersAudit10 Guided Steps
Prerequisite

P08 alarm messages tested; users/authorization can be added temporarily or completed in P11.

Required Setup

Alarms.pdl and multiple training alarm conditions.

Safety / Data Gate

Only acknowledge training alarms. Process reset remains a separate PLC command.

Completion Rule

All steps checked, Runtime verification passed, faults corrected and evidence recorded.

01
STEP 01 - Insert the alarm control

Open Alarms.pdl and insert the WinCC Alarm Control/message window supported by the installed version.

02
STEP 02 - Select displayed columns

Show time, number, class, priority, state, text, value and user/acknowledgement fields where available.

03
STEP 03 - Configure message views

Provide current, short-term/archive or incoming/outgoing/acknowledged views according to the project standard.

04
STEP 04 - Add filters

Create filters by class, priority and equipment/text so operators can isolate relevant alarms without hiding critical totals.

05
STEP 05 - Add acknowledge controls

Provide single and approved group acknowledgement buttons; protect group acknowledgement with authorization.

06
STEP 06 - Add summary indicators

Display unacknowledged warning/trip counts in the common header and make them navigate to Alarms.pdl.

07
STEP 07 - Configure audit message/action

Record acknowledgement user/time and, where required, create an audit/system message for operator actions.

08
STEP 08 - Test the full lifecycle

Trigger one warning and one trip, acknowledge one while active, clear causes, then perform approved PLC reset separately.

09
STEP 09 - Test authorization

Log in as unauthorized and authorized users; verify who can acknowledge/group acknowledge and that denied action is visible.

10
STEP 10 - Review history

Open the archive/history view and verify incoming, acknowledgement and outgoing events with correct user and timestamps.

B. Verification Checklist

C. If the Result Is Wrong

Observed issueCheck / correction
Acknowledge button disabledCheck message state, control selection and user rights.
User not recordedCheck User Administrator/audit configuration and Runtime login.
Filter hides critical alarmProvide clear filter reset and persistent total indicators.

D. Student Evidence Record

Alarm page screenshot/reference
Authorized/denied test
Audit user/time
Archive lifecycle
Student signatureTrainer verificationDate

Expected Result

Operators can view, filter and acknowledge alarms with traceable authorization and history.

P10WinCC Explorer

Softwell Complete WinCC Practical Notebook

Practical 10 - Tag Logging, Trends and Report Designer

Objective: Archive process values, display reliable trends and produce a simple time-filtered WinCC report.

Tag LoggingTrendsArchivesReport Designer10 Guided Steps
Prerequisite

P04 analog/status tags and P05 screen standard complete.

Required Setup

Stable changing test values and enough Runtime time to create archive samples.

Safety / Data Gate

Choose archive cycles based on process/report need; very fast logging can overload storage.

Completion Rule

All steps checked, Runtime verification passed, faults corrected and evidence recorded.

01
STEP 01 - Plan archive tags/cycles

List tag, engineering unit, normal rate, change behavior, retention and report requirement.

02
STEP 02 - Create process-value archive

Open Tag Logging, create ProcessArchive and select cyclic or event/change-controlled acquisition.

03
STEP 03 - Add archive tags

Add Level_PV, Speed_PV and one status/value tag with justified acquisition/archive cycles.

04
STEP 04 - Configure storage/retention

Set segment/time/size and retention options supported by the installed version; record the expected disk requirement.

05
STEP 05 - Enable Tag Logging Runtime

Add Tag Logging Runtime to Computer startup and activate Runtime long enough to collect changing values.

06
STEP 06 - Create Trends picture

Insert WinCC Online Trend Control on Trends.pdl and add pens for the archived tags with readable colors/units/scales.

07
STEP 07 - Configure time navigation

Enable current/historical view, time range, zoom, cursor/value and legend controls.

08
STEP 08 - Verify archived data

Change test values, stop/start Runtime if approved and confirm historical samples, timestamps and gaps are correctly displayed.

09
STEP 09 - Create a simple report layout

Open Report Designer, create/select a layout that includes project title, time range and selected archived values/table.

10
STEP 10 - Generate and reconcile report

Run/print-preview the report for a known period and compare reported values/timestamps with Trend Control and source tags.

B. Verification Checklist

C. If the Result Is Wrong

Observed issueCheck / correction
No archive samplesCheck Tag Logging Runtime, tag assignment and archive cycle.
Trend is flat/wrong scaleCheck source value, pen tag and axis scaling.
Report emptyCheck selected archive/time range and Runtime data availability.

D. Student Evidence Record

Archive/cycle table
Trend test range
Retention setting
Report filename/result
Student signatureTrainer verificationDate

Expected Result

WinCC archives, trends and a basic report provide consistent historical process information.

P11WinCC Explorer

Softwell Complete WinCC Practical Notebook

Practical 11 - User Administrator and Runtime Security

Objective: Create role-based users and prove that commands, setpoints, acknowledgement and engineering exit follow authorization rules.

User AdministratorRolesAuthorizationLogin10 Guided Steps
Prerequisite

P06 commands and P09 alarm controls available.

Required Setup

Training user names/password policy and approved role matrix.

Safety / Data Gate

Never publish real credentials in screenshots or student records; use training accounts only.

Completion Rule

All steps checked, Runtime verification passed, faults corrected and evidence recorded.

01
STEP 01 - Create the role matrix

List Viewer, Operator, Supervisor and Engineer tasks: view, command, setpoint, acknowledge, report and exit Runtime.

02
STEP 02 - Open User Administrator

Create groups/authorizations supported by the WinCC version and name them according to the matrix.

03
STEP 03 - Create training users

Add one user per role with temporary training passwords; apply password/expiry settings where available.

04
STEP 04 - Assign authorizations

Grant only the minimum required rights and verify no user inherits engineering/exit rights unintentionally.

05
STEP 05 - Protect command objects

Assign authorization to Start/Reset/setpoint/acknowledge and critical navigation or maintenance controls.

06
STEP 06 - Create login/logout controls

Add login, logout and current-user display to the common header; define behavior after timeout/logout.

07
STEP 07 - Protect Runtime exit

Require Engineer/Supervisor authorization or approved key sequence so an operator cannot close Runtime accidentally.

08
STEP 08 - Test every role

For each user test allowed and denied actions and record actual behavior, not only configured settings.

09
STEP 09 - Test logout/session change

Verify protected controls are unavailable after logout and rights change correctly when another user logs in.

10
STEP 10 - Document securely

Record the role matrix and test result without storing passwords; create a controlled backup after approval.

B. Verification Checklist

C. If the Result Is Wrong

Observed issueCheck / correction
Unauthorized user can commandCheck object authorization and inherited group rights.
Authorized user deniedConfirm login, assigned group and exact authorization ID.
User remains activeConfigure/test logout and inactivity policy.

D. Student Evidence Record

Role matrix
Four-user test
Logout test
Protected exit test
Student signatureTrainer verificationDate

Expected Result

WinCC Runtime enforces tested role-based access without exposing credentials.

P12WinCC Explorer

Softwell Complete WinCC Practical Notebook

Practical 12 - Runtime Startup, Communication Faults and Recovery

Objective: Configure required Runtime components, prove clean startup/shutdown and test visible recovery from PLC/OPC communication loss.

Runtime StartupDiagnosticsBad QualityRecovery10 Guided Steps
Prerequisite

P01-P11 project components configured and backed up.

Required Setup

WinCC Runtime with live/simulated connection and permission to perform a controlled interruption.

Safety / Data Gate

Do not disconnect a production network. Perform fault tests only on the isolated training setup.

Completion Rule

All steps checked, Runtime verification passed, faults corrected and evidence recorded.

01
STEP 01 - Review startup components

Open Computer properties and list Graphics, Tag Management, Alarm Logging, Tag Logging, Global Script and other required Runtime components.

02
STEP 02 - Set start picture/language

Confirm Overview.pdl, runtime language, screen behavior and any autostart settings.

03
STEP 03 - Configure communication indication

Create a visible CommHealthy/quality indicator and a system alarm/banner for loss of the primary connection.

04
STEP 04 - Save and close editors

Save Graphics/Alarm/Tag Logging/Global Script editors before starting Runtime to avoid configuration locks.

05
STEP 05 - Start Runtime cleanly

Activate Runtime and record startup time, first picture, user state, tag quality, alarms and archive activity.

06
STEP 06 - Test normal navigation/function

Open every picture and verify commands, alarms, trends and users before introducing a fault.

07
STEP 07 - Introduce controlled connection loss

Disconnect the training link or stop the simulated data source; note the time and observe tag quality, banner and system alarm.

08
STEP 08 - Verify safe screen behavior

Confirm values do not appear falsely valid, commands are inhibited as designed and last values/bad quality are distinguishable.

09
STEP 09 - Restore and measure recovery

Reconnect the source, record recovery time and confirm tags, alarms, trends and scripts recover without duplicate/unintended commands.

10
STEP 10 - Stop Runtime and inspect diagnostics

Use the approved stop method, review WinCC logs/diagnostics for errors and document corrective actions.

B. Verification Checklist

C. If the Result Is Wrong

Observed issueCheck / correction
Runtime component missingAdd it in Computer startup and restart Runtime.
Bad quality not visibleConfigure quality-driven animation/system message.
Recovery requires restartCheck channel diagnostics, script errors and connection settings.

D. Student Evidence Record

Startup component list
Startup time
Fault indication
Recovery time/log result
Student signatureTrainer verificationDate

Expected Result

WinCC Runtime starts predictably and handles communication loss with visible, safe recovery.

P13WinCC Explorer

Softwell Complete WinCC Practical Notebook

Practical 13 - Report Designer Layouts and Print Jobs

Objective: Create a controlled WinCC report layout, configure a print job and verify time-filtered alarm/archive output.

Report DesignerPrint JobAlarm ReportArchive Data10 Guided Steps
Prerequisite

Alarm and Tag Logging archives from P08-P10 contain known test data.

Required Setup

WinCC Report Designer, target printer or PDF device and an approved report template standard.

Safety / Data Gate

Use training archives and a test printer/PDF output; avoid unattended repeated print jobs.

Completion Rule

All steps checked, Runtime verification passed, faults corrected and evidence recorded.

01
STEP 01 - Define the report requirement

Record report title, data source, time range, columns, grouping, page size, output destination and operator trigger.

02
STEP 02 - Open Report Designer

In WinCC Explorer open Report Designer and create a new page layout from the approved blank/template layout.

03
STEP 03 - Configure page properties

Set paper size, orientation, margins, header/footer and page numbering before adding data objects.

04
STEP 04 - Add identification fields

Insert project/plant title, report name, generation time, computer/user and selected filter/time-range fields where supported.

05
STEP 05 - Add alarm or archive table

Insert the suitable report object/control and select the approved alarm archive or process-value archive.

06
STEP 06 - Choose columns and order

Show meaningful timestamp, tag/message, value, unit, state/class and user fields; remove internal columns operators do not need.

07
STEP 07 - Configure print job

Create a print job with the layout, output device, start/end criteria and manual/approved scheduled trigger.

08
STEP 08 - Preview with known data

Use print preview for a period containing known alarm/archive records and verify page breaks, columns and chronological order.

09
STEP 09 - Run the print/PDF test

Generate one report and compare at least three rows with Alarm/Trend views and source timestamps.

10
STEP 10 - Record and secure settings

Save the layout/job, record output filename/device and confirm no rapid cyclic print trigger remains enabled.

B. Verification Checklist

C. If the Result Is Wrong

Observed issueCheck / correction
Report is emptyCheck archive selection, Runtime data and filter/time range.
Columns are clippedAdjust orientation, width, font and page margins.
Repeated reports printDisable unintended cyclic/event trigger and review print job settings.

D. Student Evidence Record

Layout filename
Print job name
Compared records
PDF/print result
Student signatureTrainer verificationDate

Expected Result

WinCC Report Designer produces a readable and reconciled archive report through a controlled print job.

P14WinCC Explorer

Softwell Complete WinCC Practical Notebook

Practical 14 - Text Library and Runtime Language Switching

Objective: Centralize operator text, configure two Runtime languages and prove complete switching without missing translations.

Text LibraryLanguagesRuntime SwitchLocalization10 Guided Steps
Prerequisite

P05-P09 pictures and alarm texts available; primary/secondary languages approved.

Required Setup

WinCC Text Library and a training translation worksheet.

Safety / Data Gate

Translations must preserve equipment identity, units and safety meaning; unclear text must not be deployed.

Completion Rule

All steps checked, Runtime verification passed, faults corrected and evidence recorded.

01
STEP 01 - Select project languages

Record primary and secondary Runtime languages, locale/date/decimal expectations and translator/reviewer.

02
STEP 02 - Open Text Library

Enable/add the approved languages and inspect existing text IDs and translations.

03
STEP 03 - Create shared operator texts

Add text IDs for Start, Stop, Reset, Auto, Manual, Running, Fault, communication status and navigation.

04
STEP 04 - Replace duplicate static text

Link repeated screen labels/buttons to Text Library entries instead of separate hard-coded translations.

05
STEP 05 - Translate alarm/operator text

Enter approved translations for alarm classes/messages and important operator prompts without changing tag/equipment codes.

06
STEP 06 - Check units and numeric locale

Keep engineering units technically correct and verify decimal/date/time formats for each language.

07
STEP 07 - Add language controls

Provide authorized language-selection buttons/menu and a clear current-language indication.

08
STEP 08 - Switch in Runtime

Start Runtime and switch languages on Overview, Detail, Alarms, Trends and Report pages.

09
STEP 09 - Find missing/truncated text

Check blanks, fallback language, clipped buttons, long alarm messages and special characters; correct every issue.

10
STEP 10 - Export/review translations

Export or document the Text Library, obtain review approval and create a project backup revision.

B. Verification Checklist

C. If the Result Is Wrong

Observed issueCheck / correction
Text does not changeLink object text to the correct Text Library ID/language.
Special characters failUse supported fonts/encoding and verify locale.
Button text clipsResize/reflow the object for the longest approved translation.

D. Student Evidence Record

Languages configured
Text Library export
Five-picture test
Translation approval
Student signatureTrainer verificationDate

Expected Result

The WinCC project switches between approved languages with complete, reviewed operator text.

P15WinCC Explorer

Softwell Complete WinCC Practical Notebook

Practical 15 - Reusable Symbols, Faceplates and Graphic Library

Objective: Create a reusable equipment graphic with a documented tag interface and prove two independent instances.

Graphic LibraryFaceplate PatternReusable ObjectsTag Interface10 Guided Steps
Prerequisite

P05-P07 screen standard, dynamics and popup context proven.

Required Setup

Two motor/valve equipment tag structures with identical member patterns.

Safety / Data Gate

Reusable graphics must not hide missing feedback, bad quality or authorization requirements.

Completion Rule

All steps checked, Runtime verification passed, faults corrected and evidence recorded.

01
STEP 01 - Define the visual interface

List required equipment tags: command, running, ready, fault, mode, permissive, feedback and description.

02
STEP 02 - Create the master symbol

Build a motor/valve group with approved neutral/running/warning/fault/bad-quality states and consistent object names.

03
STEP 03 - Create status dynamics

Connect colors/visibility/text to interface tags using Direct Connection/Dynamic Dialog instead of copied absolute tags where possible.

04
STEP 04 - Create the detail view

Add popup/faceplate objects for command, mode, feedback, permissives, first fault and authorized reset.

05
STEP 05 - Parameterize the context

Use the supported structure/prefix/picture-tag method and document exactly how an instance receives its equipment context.

06
STEP 06 - Save to the project library

Store the approved symbol/popup in the project/library with version, description and required interface list.

07
STEP 07 - Instantiate Motor01

Insert the symbol, assign Motor01 context and test every status and authorized command.

08
STEP 08 - Instantiate Motor02

Insert a second instance with Motor02 context and verify no object retains Motor01 absolute tags.

09
STEP 09 - Test fault and bad quality

Create fault and communication-loss states for each instance; confirm unmistakable, independent indication.

10
STEP 10 - Release the library object

Record version/change note, lock/archive the approved master and document the reuse procedure.

B. Verification Checklist

C. If the Result Is Wrong

Observed issueCheck / correction
Both instances show same dataCorrect context/prefix parameters and absolute links.
Copied object loses dynamicsPackage/save the complete grouped/library object.
Command bypasses rightsApply authorization and PLC-side validation to every instance.

D. Student Evidence Record

Library object/version
Interface list
Motor01 test
Motor02/fault test
Student signatureTrainer verificationDate

Expected Result

A versioned WinCC graphic/faceplate pattern is reusable across equipment without tag mixing.

P16WinCC Explorer

Softwell Complete WinCC Practical Notebook

Practical 16 - Multi-User Engineering and Client-Server Runtime

Objective: Create a controlled WinCC multi-user/client-server architecture and prove project distribution and client Runtime access.

Multi-User ProjectServerClientProject Distribution10 Guided Steps
Prerequisite

Required WinCC Server/Client licences and two approved training computers/VMs available.

Required Setup

Server and client with fixed names/IPs, synchronized time and approved Windows/network accounts.

Safety / Data Gate

Do not convert or distribute a production project; use an isolated training copy and approved shares/firewall rules.

Completion Rule

All steps checked, Runtime verification passed, faults corrected and evidence recorded.

01
STEP 01 - Draw the architecture

Record server/client names, IPs, project paths, licences, Windows users, data sources and expected Runtime roles.

02
STEP 02 - Verify network/time

Test name resolution, connectivity, firewall/ports and time synchronization before project configuration.

03
STEP 03 - Create/open multi-user copy

Use the approved WinCC project type/conversion on a backup copy and assign the server computer.

04
STEP 04 - Configure server startup

Set server project components, start picture, archives and Runtime services required by clients.

05
STEP 05 - Create client computer

Add/configure the WinCC client computer and its Runtime graphics, language, startup and server-project reference.

06
STEP 06 - Configure package/distribution

Generate/distribute the server package or project data using the method supported by the installed WinCC version.

07
STEP 07 - Open/start client Runtime

On the client load the distributed package/project and start Runtime without using local conflicting project data.

08
STEP 08 - Test shared data/functions

Verify tags, alarms, archives, users and navigation on server and client with matching timestamps.

09
STEP 09 - Test client interruption

Disconnect one client, confirm server Runtime continues, restore connection and measure client recovery.

10
STEP 10 - Document deployment

Record versions, names, distribution steps, licences, backup and client recovery result.

B. Verification Checklist

C. If the Result Is Wrong

Observed issueCheck / correction
Client cannot find serverCheck DNS/name, firewall, package and WinCC services.
Project version mismatchAlign WinCC version/update and redistribute package.
Different timestampsFix time synchronization/time zone before acceptance.

D. Student Evidence Record

Architecture diagram
Server/client names
Shared-data test
Client recovery
Student signatureTrainer verificationDate

Expected Result

The WinCC server/client training architecture operates with documented distribution and recovery.

P17WinCC Explorer

Softwell Complete WinCC Practical Notebook

Practical 17 - WinCC Redundancy and Time Synchronization

Objective: Configure and test a licensed redundant server pair with synchronized time, archive alignment and controlled failover.

RedundancyServer PairFailoverTime Sync10 Guided Steps
Prerequisite

P16 client-server test complete; WinCC Redundancy licences and two server nodes available.

Required Setup

Primary/standby training servers plus client, fixed names/IPs and an approved time source.

Safety / Data Gate

Perform only on an isolated training system; failover tests can interrupt data and commands if architecture is wrong.

Completion Rule

All steps checked, Runtime verification passed, faults corrected and evidence recorded.

01
STEP 01 - Approve redundancy design

Record primary/standby names, IPs, network paths, redundancy channel, archive scope and client preference.

02
STEP 02 - Synchronize servers

Configure/verify Windows and WinCC time synchronization; record offset before redundancy testing.

03
STEP 03 - Prepare matching projects

Ensure both servers use the same approved WinCC version, project revision, computer settings and required licences.

04
STEP 04 - Configure redundancy pair

Open Redundancy configuration and enter the partner server/connection/settings required by the installed version.

05
STEP 05 - Configure archives/messages

Select the supported archive/message synchronization behavior and confirm sufficient storage on both nodes.

06
STEP 06 - Start primary and standby

Start both Runtimes, observe redundancy status/system messages and confirm the active server.

07
STEP 07 - Connect the client

Verify the client uses the active server and receives current tags, alarms and archived values.

08
STEP 08 - Force approved failover

Stop/disconnect the active training server, record client interruption, new active server and system messages.

09
STEP 09 - Restore and synchronize

Restart the failed server, observe resynchronization and verify alarms/archive records across the outage period.

10
STEP 10 - Complete the failover matrix

Repeat for partner/network interruption as approved and document recovery time, data gaps and limitations.

B. Verification Checklist

C. If the Result Is Wrong

Observed issueCheck / correction
Partner not detectedCheck names, redundancy network, services, firewall and project match.
Archive gaps remainReview synchronization settings/storage/time sync.
Client stays on failed serverCheck redundant server assignment/package and client diagnostics.

D. Student Evidence Record

Pair configuration
Time offset
Failover time
Archive reconciliation
Student signatureTrainer verificationDate

Expected Result

A licensed WinCC redundant pair fails over and resynchronizes within documented acceptance limits.

P18WinCC Explorer

Softwell Complete WinCC Practical Notebook

Practical 18 - System Diagnostics, Performance and Archive Maintenance

Objective: Measure Runtime health, diagnose bottlenecks and establish archive/storage maintenance without hiding faults.

DiagnosticsPerformanceSystem MessagesArchive Maintenance10 Guided Steps
Prerequisite

P01-P17 project running with representative tags, alarms, trends and clients where available.

Required Setup

WinCC diagnostics/log viewers, Windows performance tools and approved archive-maintenance plan.

Safety / Data Gate

Do not delete active archives/logs. Work on a backup or use approved retention/maintenance functions.

Completion Rule

All steps checked, Runtime verification passed, faults corrected and evidence recorded.

01
STEP 01 - Define the baseline

Record computer resources, tag count/cycles, picture count, archive cycles, script count, clients and expected Runtime response.

02
STEP 02 - Review WinCC diagnostics

Open system/diagnostic messages and relevant log files; classify communication, archive, graphics and licensing errors.

03
STEP 03 - Measure startup/navigation

Record Runtime startup, picture-change and popup response times under normal load.

04
STEP 04 - Inspect tag/acquisition load

Find unnecessarily fast cycles, duplicate tags and bad-quality sources; correct only with documented engineering approval.

05
STEP 05 - Inspect graphics load

Identify oversized images, excessive dynamics, hidden active objects and controls that slow picture opening.

06
STEP 06 - Inspect alarm/archive load

Review message storms, archive rates, retention, segment sizes and free disk space.

07
STEP 07 - Review computer resources

Record CPU, memory, disk activity/free space and network utilization during normal and stressed tests.

08
STEP 08 - Apply one controlled optimization

Change one justified setting, repeat the same measurement and document before/after result.

09
STEP 09 - Test archive maintenance

Use approved backup/export/segment/retention procedure on training data; confirm Runtime and historical access remain valid.

10
STEP 10 - Create the health checklist

Document thresholds, daily/weekly checks, log locations, backup frequency and escalation actions.

B. Verification Checklist

C. If the Result Is Wrong

Observed issueCheck / correction
Runtime CPU highInspect cycles, scripts, dynamics, trends and alarm storm.
Disk fillsCorrect archive rates/retention and implement monitored maintenance.
Picture slowOptimize images/dynamics and verify data-source latency.

D. Student Evidence Record

Baseline metrics
Diagnostic findings
Before/after optimization
Maintenance checklist
Student signatureTrainer verificationDate

Expected Result

WinCC Runtime performance and archive health are measured, improved and governed by a maintenance checklist.

P19WinCC Explorer

Softwell Complete WinCC Practical Notebook

Practical 19 - Project Backup, Migration and Restore Test

Objective: Create a verified WinCC backup, perform controlled migration on a copy and prove restore/startup on the target environment.

Project DuplicatorBackupMigrationRestore10 Guided Steps
Prerequisite

P18 health review complete; source/target WinCC versions and licences recorded.

Required Setup

Source master, separate backup/restore folders and approved test computer/VM when available.

Safety / Data Gate

Stop Runtime and protect the only working copy; never test migration directly on the production master.

Completion Rule

All steps checked, Runtime verification passed, faults corrected and evidence recorded.

01
STEP 01 - Record source baseline

Write project revision, WinCC/Windows versions, computer name, licences, drivers/options, SQL/archive paths and checksums where used.

02
STEP 02 - Close Runtime/editors

Stop Runtime normally and close Graphics, Alarm, Tag Logging and other editors so files/databases are not locked.

03
STEP 03 - Create WinCC backup

Use Project Duplicator/approved backup method and store a dated read-only master outside the live project folder.

04
STEP 04 - Verify backup contents

Check project files, pictures, scripts, text library, reports, archives/config files and external dependencies.

05
STEP 05 - Restore to a test path

Restore/duplicate the backup to a different approved folder and keep the original untouched.

06
STEP 06 - Handle computer-name change

Use the supported duplicate/rename/computer configuration procedure and record changes for the target computer.

07
STEP 07 - Perform version migration on copy

Open/convert only the restored copy in the target WinCC version and save the migration log.

08
STEP 08 - Resolve dependencies/licences

Install/verify required drivers, options, fonts, ActiveX controls and licences before Runtime.

09
STEP 09 - Run restore acceptance

Open every editor, start Runtime, test tags, alarms, trends, users, reports and diagnostics.

10
STEP 10 - Finalize rollback/handover

Document restore result, known migration changes and the exact rollback archive/path.

B. Verification Checklist

C. If the Result Is Wrong

Observed issueCheck / correction
Project files lockedStop Runtime/services/editors and repeat approved backup.
ActiveX/driver missingInstall matching approved component and retest.
Computer mismatchUse Project Duplicator/computer settings; do not rename files manually.

D. Student Evidence Record

Source baseline
Backup path/date
Migration log
Restore acceptance
Student signatureTrainer verificationDate

Expected Result

The WinCC project can be backed up, migrated on a copy and restored with a documented rollback path.

P20WinCC Explorer

Softwell Complete WinCC Practical Notebook

Practical 20 - Final WinCC Explorer Project and FAT

Objective: Integrate the complete WinCC Explorer scope into a tested, documented and restorable SCADA project.

Final ProjectFATRuntimeHandover12 Guided Steps
Prerequisite

P01-P19 records and trainer-approved process/acceptance specification available.

Required Setup

WinCC Runtime, PLC/OPC source, archive data and optional client/server/redundancy training environment.

Safety / Data Gate

Use a written FAT plan; real commands require PLC permissives and trainer/plant authorization.

Completion Rule

All steps checked, Runtime verification passed, faults corrected and evidence recorded.

01
STEP 01 - Freeze the specification

Approve connection/tag list, pictures, alarms, archives, users, languages, reports, architecture and FAT criteria.

02
STEP 02 - Create final revision

Restore/duplicate the approved baseline as Final_WinCC_R00 and update computer/project change history.

03
STEP 03 - Verify connections/tags

Test S7/OPC UA read/write samples, quality, cycles, data types and command separation.

04
STEP 04 - Complete graphics/navigation

Apply screen/faceplate standards, commands, feedback, bad quality, popups and both configured languages.

05
STEP 05 - Complete alarms/archives/reports

Verify alarm lifecycle/audit, trends, retention and Report Designer output against known source data.

06
STEP 06 - Complete users/architecture

Run the authorization matrix and, where included, client-server/redundancy tests.

07
STEP 07 - Configure Runtime startup

Set start picture/components and perform a clean cold start with no engineering editors open.

08
STEP 08 - Execute normal FAT

Test navigation, commands, setpoints, alarms, trends, users, reports and expected operating workflow.

09
STEP 09 - Execute fault FAT

Test PLC/OPC loss, bad quality, archive/disk warning, unauthorized action, client/server loss and recovery as applicable.

10
STEP 10 - Review diagnostics/performance

Confirm accepted startup/picture response, no unexplained errors and adequate disk/resources.

11
STEP 11 - Remove test conditions

Clear training commands, temporary accounts, filters and bypasses; repeat safe startup.

12
STEP 12 - Back up and hand over

Create final backup, prove restore/open, export documentation and obtain FAT/trainer sign-off.

B. Verification Checklist

C. If the Result Is Wrong

Observed issueCheck / correction
FAT result cannot repeatRestore signed revision and use recorded test inputs/versions.
Hidden bad qualityReview every connection/tag quality and screen fallback.
Backup fails on targetCheck version, computer name, licences and dependencies.

D. Student Evidence Record

Final project/backup
Normal FAT
Fault FAT
Restore/sign-off
Student signatureTrainer verificationDate

Expected Result

A pure WinCC Explorer project is engineered, fault-tested, backed up and ready for supervised handover.

Frequently Asked Questions

Which WinCC version and Windows environment should I use?

Use the approved SIMATIC WinCC Classic release with its supported Windows, SQL, communication channel and license combination. Record the installed build before engineering.

Is WinCC Explorer the same as WinCC Unified?

No. WinCC Explorer refers to the classic SIMATIC WinCC architecture. WinCC Unified uses a different runtime and JavaScript-based scripting model, so procedures are not interchangeable.

How should alarms, trends and archives be verified?

Generate a controlled source value or event, confirm timestamp and quality, verify display and acknowledgement behavior, then prove the archive can be queried after runtime restart.

What must be included in a WinCC recovery test?

Retain the project backup, license and version record, communication settings, archives policy and a documented restore test in an isolated environment.

Before You Start: Prerequisites, Tested Version, Safety and Evidence

This manual is a practical training workbook, not a substitute for the installed product manual or the site's approved engineering procedure. Record the exact software, firmware, license and hardware before following a step because menus and supported functions can vary by release.

Tested-version planning scope: Confirm SIMATIC WinCC V7.5 where supported, approved Windows and SQL components, communication channel and runtime license. Enter the exact lab-tested software, firmware and hardware in the record below before course delivery; never assume cross-version compatibility.

Environment record

Software build, firmware, device catalog, driver, communication interface and license status.

Safe lab boundary

Use an isolated training system. Follow electrical, mechanical, process and cybersecurity controls before energizing or downloading.

Evidence pack

Keep the source project, parameter/code export, screenshot/trend, fault test, correction and final pass result.

Technical review

Last reviewed by Softwell Automation Technical Training Team on 17 July 2026.

FieldLearner recordVerification
Software / firmware________________Matches the training device and official compatibility information
Project / backup________________Saved before and after the practical
Pass evidence________________Runtime value, trend, alarm, diagnostic or report attached
Fault tested________________Symptom, cause, check and corrective action documented

Practice, Viva and Extension Challenge

Practice

Change one approved input or parameter, predict the result, execute the test and explain any difference.

Viva

Explain the data flow, safety boundary, first diagnostic check and recovery method without opening the answer.

Extension challenge

Add one useful function while preserving the original pass criteria, alarm behavior and rollback path.

Graded mini-project

Combine at least three practicals, submit a versioned project and evidence pack, and demonstrate repeatable recovery.

SIMATIC WinCC Explorer four-stage practical lab, runtime verification, diagnosis and backup workflow
Instructional workflow diagram: complete configuration, measurable verification, controlled diagnosis and recovery evidence in sequence.
Siemens Industry Online Support — official documentation

Content status: Substantively reviewed and expanded 17 July 2026. Verify release-specific details against the linked official documentation.

Verified learning pathway

Practise This Manual with Guidance

Use the manual with trainer-led practicals, software exercises and troubleshooting support.

Content reviewed: 17 July 2026

☎ Call WhatsApp ✉ Email Enquire Now