Connect Factory Symbols to Tags in WinCC Explorer SCADA

Separate equipment identity, tag names and addresses

P-101 is the drawing identifier. U101_P101_RunFb is a proposed WinCC tag name. The PLC connection and address are a third, separate item. Keeping these concepts distinct prevents a drawing label from being mistaken for a usable communication address.

Start with internal tags in a training project so you can exercise the graphics without writing to plant equipment. In WinCC Tag Management, internal tags support local values; process tags belong to an appropriate communication connection. The WinCC V8.0 manual describes these separately in its Working with Tags chapter.

The following names and ranges are original exercise choices. They are not a PLC download file or a universal naming standard.

Prepare the tag sheet before editing properties

The training helper U101_DataValid is not automatic WinCC communication-quality detection. In a connected application, define how channel status and tag quality produce the corresponding display behavior. Test that path separately.

Add columns for source, actual WinCC data type, units, scaling owner, read/write direction and test result. For process tags, confirm the type and address against the PLC interface; do not simply reuse the exercise ranges as instrument calibration.

Connect values and symbol properties

1. Create the training tags. Use the relevant binary or floating-point type in your version of Tag Management. Organize the names so all Unit 101 points are easy to find.
2. Connect the numeric fields. In Graphics Designer, bind the level and flow output values to their corresponding PV tags. Set the intended decimal display and show the unit in a separate label.
3. Connect level fill. Set the graphic or bar range to the same engineering range used by the displayed value. Test zero, midpoint and full scale before styling it.
4. Connect discrete appearance. Use a supported tag connection or Dynamic Dialog for the relevant property. Siemens documents these methods for dynamic properties. Choose a simple method for a single condition; do not add scripts merely to change one colour.
5. Provide a state result. For combined states, define a documented evaluation in the PLC or a reviewed display expression. Keep a table of the result values and appearances so the logic can be checked independently.
6. Check updates. Select an update cycle appropriate to the process and test it in Runtime. A tag can be correct while the picture updates too slowly to be useful.

Make ambiguous states visible

Use this display priority for the pump exercise: invalid data → UNKNOWN; valid data with fault → FAULT; otherwise running feedback → RUNNING; otherwise → STOPPED. This is an exercise display rule, not motor protection logic.

Keep operator commands separate from feedback. A future start button would write a defined request; running colour must still depend on actual feedback. This lesson is indication-only. Command arbitration, permissives and protection remain in the designed control system.

Test one point at a time

Your task: use temporary, clearly labelled training inputs or a simulator to change the internal tags. Keep those controls on a separate test picture. Do not use production command tags for this exercise.

• Set level to 0, 50 and 100 and verify both number and fill.
• Change only flow and verify the level display does not change.
• Set RunFb = 1 and Fault = 1; verify FAULT takes priority.
• Try all four valve feedback combinations.
• Set DataValid = 0; verify values/states are visibly marked invalid.
• Inspect P-102 and confirm it does not silently reuse P-101 bindings.

Record the value, expected appearance and actual result for each test. The completed sheet becomes the basis for the whole-screen checks in Lesson 4.