WinCC Tag Selection: Server Prefix and AS-OS Connection Explained

Overview: WinCC Tag Architecture in Step 7 Integrated Projects

When a WinCC project is embedded inside a STEP 7 / TIA Portal project as a WinCC Application (the classic "WinCC Appl." configuration), tag management becomes a hybrid of two worlds: the SIMATIC S7 program domain and the HMI/SCADA domain. Tags are not just local WinCC variables; they are projections of S7 symbols, shared-DB elements, or FB parameters that have been published for operator control and monitoring. The Graphics Designer tag-selection dialog therefore exposes multiple paths to the same underlying process value, and each path carries different consequences for naming, quality propagation, redundancy, and runtime behavior.

The two most common paths the engineer encounters in the tag-selection window are:

1. Project_Name_OS(1)::Tag_Name – a qualified path that includes the server prefix and a redundant-tag index.
2. Tag_Name (or S7_block_folder/DB_Name.Variable) – an unqualified path that addresses the tag directly from the AS-OS connection or STEP 7 symbol server.

Choosing the wrong path on a single I/O field will not stop compilation, but it will surface at runtime as a yellow quality warning on the faceplate, a frozen process value, or a misrouted tag in a redundant WinCC server pair. This reference covers what each prefix means, when each is required, how AS-OS connections are compiled, and how to diagnose and repair mismatched tag references.

Server Prefix Fundamentals: Project_Name_OS(1)::Tag_Name

The string Project_Name_OS(1)::Tag_Name is a fully qualified WinCC reference composed of three logical components:

The server prefix exists because WinCC supports distributed, multi-server, and redundant topologies. A client picture may be served by Server A in plant area 1 and by Server B in plant area 2; the prefix tells the client runtime which server's tag namespace to query. If your project is a single, non-redundant WinCC Application with no remote clients, the prefix is not required for local I/O fields, and omitting it is the cleaner choice.

Tag Selection Paths in the Graphics Designer

When you open the tag-selection dialog from an I/O field, the left-hand tree shows three entries (rectangles 1, 2, and 3 in the legacy dialog):

1. Server prefix entry under "Internal tags" / "Process tags" – prefixed: shows tags as Project_Name_OS(1)::Tag_Name.
2. Server prefix entry – direct selection: shows the same tag tree but allows the engineer to drop the prefix by selecting the leaf node.
3. STEP 7 symbol server / AS-OS connection – unprefixed: shows symbols exactly as exposed by the OS compiler or the STEP 7 symbol server (for example S7 Program / Blocks / DB_Motor / Speed).

The visible string after a drag-and-drop operation depends on the source branch:

• From path (1) or (2): the I/O field will display Project_Name_OS(1)::Tag_Name as its configured output value.
• From path (3): the I/O field will display Tag_Name or the STEP 7-qualified name S7_block_folder/DB_Name.Variable, and the tag is auto-created in WinCC Tag Management if it does not yet exist.

Both paths ultimately reference the same process value at the S7 end. The difference is the resolution path that WinCC Runtime takes when updating the I/O field.

AS-OS Connection: Automatic Compilation vs Manual Creation

The AS-OS connection is the bridge between the S7 program (AS = AutomatisierungsStation / Automation Station) and the WinCC operator station (OS). It is generated by the STEP 7 / TIA Portal "OS compiler" and is exposed in WinCC Explorer under Tag Management > SIMATIC S7 PROTOCOL SUITE > [Connection name].

The recommended path is the automatic OS compiler. The compiler is driven by the STEP 7 symbol table and by attributes stored on shared DBs / FB parameters, so the S7 program remains the single source of truth. If you bypass the compiler and create tags manually, every rename or address change in the S7 program must be replicated manually in WinCC.

Tag Data Types and the WinCC V7.5 Reference

When a tag is created, either automatically by the OS compiler or manually in Tag Management, it must be assigned a data type. The WinCC V7.5 working manual lists the complete set:

The data type is locked when the tag is created by the OS compiler based on the S7 declaration; manually created tags can have any type but must match the byte layout at the PLC end or you will read garbage. Refer to the Siemens Knowledge Base – Tag Types in WinCC V7.5 for the full reference including display format conversion rules.

Quality Code Diagnostics: Why the I/O Field Shows a Yellow Triangle

The yellow warning indicator on a WinCC I/O field is the runtime's way of telling the engineer that the tag's OPC quality code is not 0xC0 (Good). The most common codes observed in single-server AS-OS configurations are:

When two I/O fields are configured on the same picture — one with IntegracjaWinCC_OS(1)::Tag_Name and one with Tag_Name — and only the prefixed one shows the yellow warning, the most common cause is that the prefix is being resolved against a server context that does not own the tag. In a single-server project that has no clients, the server context of the prefix resolves to a server that is not the one running the picture, so the tag is reported as not found. The unprefixed form resolves against the local server's AS-OS connection and returns the live value.

Troubleshooting Matrix: Mismatched Tag References

Multi-Server and Redundant Topologies

The prefix _OS(1) is essential when the architecture includes redundant servers or a client/server split:

• Redundant pair: _OS(1) addresses the master, _OS(2) addresses the standby. WinCC Runtime automatically fails over to the standby if the master becomes unavailable.
• Client with multiple servers: A client picture that needs to display a value from Server A's tag namespace uses ServerA_OS(1)::Tag_Name; a value from Server B's namespace uses ServerB_OS(1)::Tag_Name. Both prefixes may appear in the same picture.
• Single-server, no client: The prefix is unnecessary. All I/O fields can reference tags directly. This is the simplest configuration and the one that most often produces the "prefixed tag does not work" symptom described in the original issue.

If you find yourself adding a prefix in a single-server project, ask whether the project will ever be expanded to a client/server topology. If yes, accept the extra discipline of always using the prefix. If no, drop the prefix to keep tag references portable and easy to read.

STEP 7 Symbol Server vs AS-OS Connection

Two mechanisms can populate the WinCC tag namespace from STEP 7:

The OS Compiler is the recommended mechanism for production. The STEP 7 symbol server is convenient during early commissioning but creates tags that are not linked to the S7 program's published attributes, so renaming or re-typing a symbol can silently break WinCC references.

Limits, Alarms, and Range Configuration (WinCC Unified)

For engineers transitioning to WinCC Unified in TIA Portal V20, tag limits are configured in the Inspector window under Properties > Properties > Range. The limits are evaluated by the HMI Runtime to drive color changes, alarm generation, and value substitution. Refer to the Siemens TIA Portal V20 documentation – Defining limits for a tag (WinCC Unified) for the exact workflow. The limits are stored as properties on the tag, not as separate entries in the tag database, so they are exported automatically with the tag when the project is migrated.

Verification Checklist After a Tag Selection Change

1. Open the affected picture in Graphics Designer, double-click the I/O field, and confirm the output value string. It should be either the unprefixed tag name or the explicitly intended Server_OS(n)::Tag_Name — never both.
2. Activate WinCC Runtime and observe the I/O field. A correct reference updates within the configured acquisition cycle and shows no quality-code indicator.
3. Open WinCC Explorer > Tools > Status of Connections and confirm the AS-OS connection reports Connected with the correct rack/slot of the S7 CPU.
4. In Tag Management, right-click the tag and select Find in Process Screen to verify every picture that references it. Replace any inconsistent references.
5. If the project is a WinCC Application inside TIA Portal, run Compile > Software (rebuild) to regenerate the OS data.
6. Check the WinCC Alarm Logging and Tag Logging runtime windows for any tags reported with quality code 0x00 (Bad – configuration error).

Best Practices

• Let the OS compiler create your tags. Avoid manual tag creation against STEP 7 symbols except for genuinely ad hoc engineering values.
• Decide your prefix policy once per project: either always prefixed (for distributed architectures) or always unprefixed (for single-server architectures). Mixing both within one picture is a frequent source of yellow warnings.
• Use the drag-and-drop action from the tag tree to minimize typing errors. Drag-and-drop binds the exact tag selected, so the resulting reference matches the path you intended.
• Document the prefix policy in the project's functional specification so that every future modification follows the same convention.
• When commissioning, use the "Status of Connections" view in WinCC Explorer as your primary diagnostic tool before opening any faceplate.