How to Resolve Missing OS Tags for Specific Plant Hierarchy Areas After Project Merging in PCS 7

When merging an S7-400 station from one multi-project into another in PCS 7, missing OS tags in specific Plant Hierarchy folders (such as Coal Mill area tags failing while Kiln area tags succeed) typically result from unassigned or broken OS Assignments in the Plant Hierarchy, missing 'PH Assignment' links in Component View, or block interface discrepancies generating 'does not match the number of operable IOs' compiler errors. To resolve this, verify that the hierarchy folder's OS Assignment points to the active WinCC OS, update block types from the Master Data Library across all merged charts, and perform a full OS compilation with memory reset.

Mechanisms of OS Tag Generation and the Plant Hierarchy (PH)

In SIMATIC PCS 7, the Plant Hierarchy (PH) structures the automation plant into logical units (e.g., Plant > Unit > Function). The Engineering System utilizes this hierarchy to automate AS-OS engineering:
* When an OS compilation is executed, the compiler traverses the Plant Hierarchy.
* It identifies all CFC charts residing in hierarchy folders that possess an active OS Assignment.
* It parses every block in those charts that has the attribute S7_m_c := 'true' (Operator Control and Monitoring).
* It creates corresponding WinCC structure tags, raw archive variables, and alarm definitions within the target OS server database.
* If a hierarchy branch lacks an OS Assignment or points to an orphaned OS object, the compiler completely skips that entire process section without generating an error.

Root Causes of Missing OS Tags Following Project Merges

When an engineer merges an S7-400 program (such as importing a CEMAT or standard AS program from Multi-Project A into Multi-Project B):
1. Orphaned OS Assignment in Plant View: The merged hierarchy folder often still retains a pointer to the original OS Server object from Project A. Because that specific OS object does not exist in Project B, the compiler skips the folder during compilation.
2. Missing PH Assignment in Component View: In Component View, select the Charts folder. If individual charts were copied manually between folders, their internal PH Assignment attribute may be disconnected, leaving them detached from the plant tree.
3. Network Connection (NetPro) Mismatch: If the S7 Named Connection between the merged AS and the new OS is named differently or was not compiled in NetPro, the compiler cannot establish communication channels for those specific charts.

Resolving 'Does Not Match the Number of Operable IOs' Compiler Errors

A critical symptom frequently accompanying tag loss in merged projects is the compiler warning:
Error when compiling OS: Block ... does not match the number of operable IOs.

The Cause: The merged charts contain block instances compiled from an older or modified version of a function block (e.g., a custom CEMAT group block C_DRV_1D). However, the Master Data Library (MDL) or block folder contains a newer block type with added or removed S7_m_c attributes.
The Result: The OS compiler encounters a mismatch between the instance data block structure stored in the AS program and the block type template. To protect database integrity, the compiler aborts tag generation for that entire chart!
The Fix: The block types across the merged charts must be updated from the Master Data Library using Options > Charts > Update Block Types... prior to OS compilation.

Step-by-Step Procedure to Reconcile Hierarchy and Regenerate Tags

Follow this procedure to recover tag generation across all plant hierarchy folders:

Verify Plant Hierarchy OS Assignment:
* Open SIMATIC Manager in Plant View.
* Right-click the problematic root folder (e.g., Coal Mill) and select Properties.
* Open the Plant Hierarchy tab.
* Under OS Assignment, ensure the dropdown points to your active WinCC OS project (e.g., OS(1)). Check the box: Pass on assignment to lower-level objects.
* Click OK.
Verify Component View PH Linkage:
* Switch to Component View.
* Open the target S7 Program and select the Charts folder.
* Review the Plant Hierarchy Assignment column for every chart: verify that none show blank or unassigned paths.
Reconcile Master Data Library:
* In SIMATIC Manager, open the Master Data Library.
* Select Options > Charts > Update Block Types....
* Select all AS programs and confirm the update.
Compile AS Charts:
* Open any CFC chart and execute Chart > Compile > Entire Program.
Execute OS Compilation with Memory Reset:
* In Component View, right-click the OS Server object and select Compile.
* Select Entire OS with With memory reset (to purge orphaned tag handles).
* Verify that the compilation log reports that all tags across the newly assigned hierarchy are generated successfully.

Comparison of OS Tag Compilation Scope and Settings

The table below outlines OS compilation scope options and their impact on tag generation.

Compilation ScopeProcessing SpeedScope of Tags ProcessedClears Orphaned Tags?Recommended UsageChanges OnlyFast (1-2 minutes)Only charts modified since last compileNoRoutine online commissioning editsEntire OSModerateAll charts with valid OS AssignmentNoAdding major hardware or new AS stationsEntire OS (With Memory Reset)Slower (Full rebuild)All charts; completely rebuilds tag tablesYesProject merges, library upgrades, missing tags

Verification

To confirm that all missing OS tags have been generated:
1. Open WinCC Explorer on the target OS project and launch Tag Management.
2. Browse SIMATIC S7 PROTOCOL SUITE > Named Connections > [Connection_Name].
3. Locate the folder corresponding to the merged hierarchy path (e.g., Coal Mill).
4. Confirm that all motor, valve, and transmitter structure tags appear in the list with valid data types.
5. In Graphics Designer, open the process mimic display: verify that dynamic wizards and tag selectors can browse and connect to the newly created tags.

Limitations and Operational Precautions

Compiling the OS with 'With memory reset' clears runtime archive associations temporarily until runtime is restarted; perform full compilations during scheduled engineering intervals.
Never merge projects without verifying that block type numbers (FB/FC numbers) in the merged program do not collide with existing blocks in the destination multi-project.
Ensure NetPro connections are compiled and downloaded to the AS controller before compiling the OS; missing NetPro links will cause the OS compiler to generate communications errors.
When using industry libraries like CEMAT, ensure that the CEMAT system parameters and message number ranges are aligned across all merged stations.

Engineer FAQ

Why did one hierarchy folder compile tags while another folder in the same PLC failed?

OS compilation evaluates OS Assignment on a folder-by-folder basis in Plant View. If the Kiln folder had an active OS Assignment but the Coal Mill folder was unassigned or assigned to a defunct OS name from the source project, the compiler skipped the Coal Mill area completely.

What does 'does not match the number of operable IOs' mean?

It indicates that the instance DB in CFC has a different number of parameters tagged with S7_m_c := 'true' than the FB template in the block folder. Updating block types across all charts resolves this conflict.

Can I compile the OS without assigning charts to the Plant Hierarchy?

In standard PCS 7, no. The OS compiler requires the Plant Hierarchy to generate the structure prefix and picture tree navigation. Charts not assigned to the Plant Hierarchy cannot be automatically compiled into WinCC.