Create Tank, Pump and Valve Symbols in WinCC Graphics Designer

Use the P&ID plan as your symbol specification

Open the equipment register from Lesson 1. The objective is to create symbols that an operator can identify quickly and that an engineer can connect to tags consistently. Build a tank, a transfer pump, an actuated valve and the connecting process line before adding animation.

In WinCC Explorer, open Graphics Designer and create a training picture named U101_Symbols.pdl. Siemens documents the use of the object palette and libraries for process-picture design. Use the library installed with your WinCC release or construct the teaching symbols from basic shapes. See the linked Getting Started guide for the editor workflow.

The drawing below illustrates a consistent visual vocabulary. It is an original teaching reference, not a claim that every WinCC library contains these exact objects.

Construct each symbol in Graphics Designer

1. Tank: create a simple closed outline and an inner rectangle or bar for level. Keep the outline static. Give the dynamic fill area its own object name, such as TK101_LevelFill, and add a separate numeric field with a percent unit.
2. Pump: use a library pump that remains recognizable at your target size, or draw a circle with a directional marker. Add the identifier P-101 and a status label beneath it. Keep the motor state separate from the pipe graphics.
3. Valve: choose a symbol consistent with the approved plant legend. In this teaching sheet the valve is a simplified pair of opposed triangles. Add XV-101 and leave room for OPEN, CLOSED, MOVING and UNKNOWN labels.
4. Pipes: use consistent line width and right-angle routing where practical. Make flow direction explicit. Send the piping behind equipment so it cannot cover an instrument value.
5. Labels: use one font scale for equipment IDs and another for values. Align labels and units rather than resizing each one independently.
6. Object names: choose names that explain the role: P101_Body, P101_StatusText and XV101_StateText. The visible equipment ID and the Graphics Designer object name serve different purposes.

Design appearances before connecting a tag

Colour supports the message; it must not be the only message. A grey pump could otherwise mean stopped, unavailable or disconnected. Give those conditions distinct text or badges. Decide which condition takes priority when several flags are present.

A grouped collection of shapes is not automatically a reusable object with inherited updates. If you use copied groups, document that edits and tag bindings must be checked per copy. If your release and project use library objects or faceplate types, follow their specific reuse workflow and test instance behavior.

Redesign an existing factory symbol deliberately

Suppose an old pump symbol is a large multicolour image with no state text. Keep its equipment identity, but replace decorative detail with a clear body, flow direction, equipment label and status field. Preserve the process relationships before changing appearance.

1. Duplicate the old picture in the training project and record which objects are dynamic.
2. Build the replacement symbol beside the old one, matching its intended state meanings.
3. Record every tag reference, event action and permission used by the old object. Replacing its appearance does not transfer that behavior automatically.
4. Test both symbols against the same training values before removing the old object from the revised picture.
5. Check alignment, click areas and overlapping objects at the target Runtime resolution.

Deliver a reusable symbol sheet

Your task: place two pump instances, one tank, one valve and a pipe legend on U101_Symbols.pdl. Show the second pump as P-102 so you can later detect accidental reuse of P-101 tags.

• All equipment remains identifiable when colour is ignored.
• The tank level graphic does not hide its numeric value.
• The valve has a planned appearance for conflicting feedback.
• Each object has a deliberate name and a documented dynamic property.
• The P-101 and P-102 copies are distinguishable before any tags are connected.

Save the symbol sheet and capture the four state appearances as your project reference. Lesson 3 connects these objects to a small, explicit tag model.