Configuring Custom Picture Naming and Automated Block Icon Placement in PCS 7 Models

In SIMATIC PCS 7, when replicating technological Models containing process tags and WinCC pictures from the Master Data Library using the Import/Export Assistant (IEA), replica pictures default to taking the model's picture name with an appended numerical index in brackets (e.g., 'ModelPicture(1).pdl'). To assign custom, meaningful picture names (such as matching P&ID equipment tags) during model import, engineers must configure the Plant Hierarchy settings to 'Derive picture name from the hierarchy folder' so that each replica automatically adopts its target unit folder name upon creation. Furthermore, block icons configured inside the library model picture automatically bind their tag connections to the replica's specific CFC chart tags during the standard OS compilation process.

Concept of Models and Replicas in SIMATIC PCS 7

In large-scale process automation, engineering efficiency relies on standardized technological templates. While Process Tag Types (PTT) standardize individual control loops (e.g., a single motor or analog transmitter), Models in SIMATIC PCS 7 expand this modularity to entire technological units (e.g., a standardized dosing tank comprising valves, pumps, level transmitters, interlocks, and an associated WinCC process graphic).

A Model is created inside the Master Data Library (MDL) within a dedicated Plant Hierarchy folder. When an engineer defines the folder as a Model:
1. All CFC charts inside the folder become template charts.
2. An embedded WinCC picture (.pdl) serves as the standardized graphic display.
3. The Import/Export Assistant (IEA) generates an Import/Export File (an IEA .csv or .txt file) detailing parameter variations, I/O addresses, and text strings for each planned plant instance (Replica).

Mechanism of Automated Picture Naming During Model Replication

When the IEA replicates a model across multiple hierarchy folders, it instantiates the CFC charts and copies the embedded process picture.

By default, the IEA names replicated pictures by taking the source model's filename and appending a sequential integer in parentheses:
$$\text{Source: } Tank_Template.pdl \rightarrow \text{Replicas: } Tank_Template(1).pdl,\; Tank_Template(2).pdl$$

This default behavior is undesirable in production plants because plant operations require pictures named after specific P&ID designations (such as TK_101_Acid.pdl or TK_102_Caustic.pdl).

Because the IEA table interface does not provide a direct column for manual picture renaming during batch import, the name must be controlled through the Plant Hierarchy Picture Derivation Architecture.

Configuring Hierarchy-Derived Picture Naming

To ensure that every replicated model picture adopts the exact P&ID name of its target unit without manual renaming:

Step 1: Configure Plant Hierarchy Naming Settings

In SIMATIC Manager, select the Multiproject or target AS project.
Select menu Options > Plant Hierarchy > Settings....
In the Plant Hierarchy Settings dialog:
- Locate the section OS Picture Name.
- Select the option: Derive picture name from the hierarchy folder (or check Hierarchy folder name determines picture name).
- Ensure the hierarchy level defining the unit matches your P&ID structure.
Click OK to apply the configuration across the project.

Step 2: Structure the IEA Import File with Meaningful Folder Names

Open the IEA import file in Microsoft Excel or a text editor.
In the column specifying the target Plant Hierarchy path (Hierarchy Path or Folder Name), enter the exact P&ID identifier for each replica (e.g., Plant1/AreaA/TK101_Dosing).
Execute the IEA model import via Options > Process Tags > Import....
During import, the system creates the hierarchy folder TK101_Dosing and instantiates the replica picture. Because hierarchy derivation is active, the picture is automatically created as:
$$\text{Picture Name: } TK101_Dosing.pdl$$

Automated Block Icon Placement and Binding in Model Pictures

A major advantage of using Models is pre-arranging graphical block icons in the template picture so that replica pictures do not require manual graphic drawing.

Configuration Workflow:

In the Master Data Library model folder, open the template picture in WinCC Graphics Designer.
Draw the static plant equipment (e.g., tank outlines, piping).
Place the block icons for the model's template CFC blocks (e.g., copy @MotL/1 and @VlvL/1 from @PCS7Typicals_APL.pdl).
Position the icons exactly where they belong relative to the equipment drawing.
In the block icon object properties, set the property tagname to the relative block name inside the model (e.g., Valve1 or Motor1).
When the IEA replicates the model into the target project, the layout geometry is preserved.
During the next OS Compile with Create/update block icons enabled, the compiler recognizes the pre-existing block icons in the replica picture and updates their tag bindings to the full hierarchical tag paths (e.g., Plant1/AreaA/TK101_Dosing/Valve1) without displacing their physical screen coordinates.

PCS 7 Model Replication Parameter Matrix

The following matrix outlines configuration parameters governing model replication and picture generation:

Engineering ParameterConfiguration LocationSetting OptionOperational ResultOS Picture Name RulePlant Hierarchy SettingsDerive from hierarchy folderPicture automatically named after the P&ID unit folderIEA Hierarchy PathIEA Import File (*.csv)Full technological pathDefines destination folder and derived picture nameBlock Icon GeometryModel Template .pdlFixed X/Y pixel coordinatesReplicas inherit identical spatial layout across all unitsOS Compile Block IconsOS Compilation WizardCreate/update block iconsBinds pre-placed icons to replica tags without repositioningPicture Hierarchy TreePlant Hierarchy ViewAssigned picture objectPicture automatically inserted into WinCC Picture Tree Navigator

Verification

To confirm that model pictures are properly named and block icons are functional:
1. Execute the IEA model import for multiple instances.
2. In SIMATIC Manager Plant View, expand the created folders: Verify that each folder contains a picture named identically to the folder (e.g., TK101.pdl, TK102.pdl).
3. Run an OS Compile with 'Changes only'.
4. Open TK101.pdl in Graphics Designer: Verify that block icons exist in their intended graphical positions.
5. Inspect the Object Properties of a block icon: Verify that tagname contains the complete hierarchical path Plant1/AreaA/TK101/Valve1.
6. Launch WinCC Runtime: Verify that clicking the block icon opens the correct faceplate controlling the specific instance.

Limitations and Operational Precautions

Observe the following engineering constraints when utilizing Models:
- Character Restrictions in Picture Names: Picture names derived from hierarchy folders must not contain special characters forbidden by Windows or WinCC (forward slash, backslash, colon, asterisk, question mark, quotation marks, angle brackets, pipe, or spaces). Use underscores (_) or hyphens (-).
- Control Module Types (CMT) Superseding PTT: In PCS 7 V8.1, V8.2, and V9.0, Siemens introduced Control Module Types (CMT) and Equipment Modules (EM), which offer superior flexibility over classic Process Tag Types and Models. For new greenfield projects, evaluate CMT technology.
- Model Synchronization: Unlike CMTs, modifying a Model in the Master Data Library does not automatically synchronize existing replicas; updates must be managed through re-exporting and re-importing IEA files.

Engineer FAQ

Why did my replica pictures end up named 'Picture(1).pdl' instead of the tank name?

This happens when 'Derive picture name from the hierarchy folder' is disabled in Plant Hierarchy Settings. Without this setting, the Import/Export Assistant generates sequential numbers appended to the library template name.

Will running 'Create/update block icons' rearrange the icons I positioned in the model picture?

No. The OS Compiler detects that the block icons already exist in the picture and updates their tag connections in place, preserving your manual placement.

Can I replicate models across different multiprojects?

Yes. You can export the Master Data Library model and IEA configuration files to archive format and import them into any PCS 7 multiproject sharing identical library versions.