WinCC Explorer SCADA Manual
WinCC Explorer Runtime Practical Manual

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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