Fix PCS 7 Plant Hierarchy Names Missing Translations Below Level 2

If PCS 7 Plant Hierarchy names at level 3 remain in the source language after text import, make sure the translated texts are imported into the project that contains the OS and then compile that OS. In the reported multiproject, importing translations only into the AS project left OS runtime names untranslated; importing the same translated text into the OS project and compiling resolved the issue. Also check exact source-string matches and hierarchy-name spelling.

Why AS translations may not appear in OS Runtime

SIMATIC Manager text export/import can contain different text types with different OS relevance. Plant hierarchy/OS picture names used by Runtime must be available in the OS project's text resources; translating a related AS project does not necessarily update the separate OS project in a multiproject.

Import the translation into the OS project

Identify the project that contains the WinCC OS and the relevant Plant Hierarchy/OS text resources.
Export the appropriate user texts from the OS project using the installed PCS 7 multilingual-text workflow.
Translate only target-language cells. Preserve every source-language string exactly, including capitalization, spaces and punctuation, because import matching depends on the source text.
Import the translated file back into the OS project—not only the AS project.
Compile the OS using the version-appropriate workflow so the translated names are available in Runtime.
Change the Runtime language and check both the level-2 parent and the level-3 names.

Check duplicate or mismatched source entries

Search the OS project Text Library for the exact original source text (for example, Dryer 1 versus dryer1). Check for duplicate entries with identical source-language text but inconsistent target translations. Do not alter source-language values in an export file to force a match; correct the project's source text only through a deliberate engineering change.

Understand hierarchy display and generated identifiers

The text visible in SIMATIC Manager and a hierarchy path shown in WinCC Text Library can be represented differently. A slash-separated path in the OS text library does not by itself indicate an import failure. PCS 7 hierarchy names may also be transformed when included in plant designations/identifiers during OS compilation; distinguish the display text from the generated identifier and follow the version-specific naming constraints.

Expected result

After the translated texts are imported into the OS project and the OS is compiled, level-2 and level-3 names should display in the selected target language in OS Runtime when corresponding source entries and target translations match.

Verification

Test each configured Runtime language. Check representative hierarchy names at multiple levels and confirm text in the OS project's Text Library matches the exported source string exactly. If a name remains in the source language, inspect the OS project entry and translation pair before editing the AS project.

Limitations and Operational Precautions

The ticket does not identify PCS 7 version/update. The confirmed correction was importing the translations into the OS project and compiling it. Export/import rules and UI paths vary by release; use the installed version's multilingual-text documentation. Avoid editing source names or hierarchy identifiers solely to work around a translation mismatch.

Engineer FAQ

Why did level-2 names translate but level-3 names did not? The source reports the translations had been imported into the AS project but not the OS project; importing into the OS project and compiling fixed all levels.

Must source-language strings remain unchanged during import? Yes. Siemens multilingual-text guidance says the source text must match an existing source-language entry.

Is a slash-separated Text Library entry necessarily wrong? No. It can represent hierarchy context in the OS text resources; check actual translations in the OS project.

Can spelling and case matter? The source reports exact matching matters; compare the exported source text carefully, including spaces and case.

What should be recompiled? The OS project containing the Runtime text resources.

Technical References

Siemens, Configuration of Texts and Languages in SIMATIC PCS 7, Entry ID 56248153, export/import source-text matching and OS relevance: https://support.industry.siemens.com/cs/attachments/56248153/56248153_Multilingual_PCS_7_V100_DOC_V6_0_en.pdf
Siemens, PCS 7 Compendium Part A – Configuration Guidelines V9.0, Plant Hierarchy naming and identifier rules: https://support.industry.siemens.com/cs/attachments/109756485/pcs7_compendium_part_a_en-US_en-US.pdf