Creating Custom Block Icons and Configuring Dynamic Typicals in SIMATIC PCS 7 APL

To create a custom block icon in SIMATIC PCS 7 Advanced Process Library (APL), copy an existing block icon from the typicals template @PCS7TypicalsAPLV8.pdl (or create @PCS7CustomTypicals.pdl), assign a unique variant number to the type property (e.g. @MonAnL/10), customize the graphical elements and dynamic properties, and set the block icon variant number in the CFC block's properties. When the OS is compiled with 'Create/Update Block Icons' enabled, the Driver Generator automatically instantiates and interconnects your custom block icon.

Block Icon Architecture in the PCS 7 APL Generation Framework

In SIMATIC PCS 7, the engineering workflow minimizes repetitive graphic design through Automatic Block Icon Generation. Instead of manually drawing graphical representation symbols for hundreds of pumps, valves, and analog transmitters across dozens of WinCC process graphics, the system generates them automatically based on the Plant Hierarchy.

When an engineer checks the option Create block icons in the properties of a process graphic (.pdl) within the Plant Hierarchy and runs an OS Compilation:
1. The OS Compiler queries the CFC charts mapped to that hierarchy folder.
2. It identifies all technological blocks configured with operator control attributes (S7_m_c = 'true').
3. For each block, it fetches a pre-configured template block icon from a dedicated typicals graphic.
4. It places the icon onto the target graphic, assigns the full tag path (e.g. Plant1/Unit02/TIC101), establishes dynamic C-script and direct tag connections, and wires the mouse-click action to open the corresponding faceplate.

The Role of @PCS7TypicalsAPLV8.pdl and @Template_APL.pdl

The PCS 7 OS Graphics Designer utilizes two primary template files:
* @PCS7TypicalsAPLV8.pdl (or @PCS7Typicals.pdl):
The active master template file searched by the OS Compiler during block icon generation. It contains all supported variants of APL block icons (MonAnL, MotL, VlvL, PIDConL, etc.).
* @Template_APL.pdl:
A reference catalog containing uninstantiated building blocks and static graphic components for manual copy/paste operations.
* @PCS7CustomTypicals.pdl (User-Defined Custom Master):
Best-practice engineering dictates creating a separate custom typicals file. Because Siemens software updates and library migrations overwrite @PCS7TypicalsAPLV8.pdl, placing custom icons into @PCS7CustomTypicals.pdl ensures user modifications are permanently preserved across future PCS 7 software upgrades.

Object Properties Governing Block Icon Generation

To participate in automated generation, a block icon in the typicals graphic must be configured with three crucial system properties:
1. type (String):
Specifies the block type and variant number in the exact syntax:
@<BlockType>/<VariantNumber>
For example, @MonAnL/1 is the standard analog monitor icon. A custom variant would be defined as @MonAnL/10 or @MotL/5.
2. servername (String):
Defines the server prefix name; default is PCS7 <BlockType> Control.
3. tag / tagname (String):
Acts as a placeholder variable. During generation, the OS Compiler dynamically replaces this placeholder with the actual hierarchical tag name (e.g. AreaA/Section1/TI_101).
4. StructureType (String):
Specifies the internal WinCC structure tag type corresponding to the APL block (e.g. MonAnL).

Standard vs. Custom Typicals Management Matrix

The following matrix compares methods for maintaining custom block icons in SIMATIC PCS 7:

AspectModifying @PCS7TypicalsAPLV8 directlyCreating @PCS7CustomTypicals.pdlFile LocationWinCC OS Project \GraCS folderWinCC OS Project \GraCS folderUpgrade SafetyHigh Risk (Overwritten during library updates)100% Safe (Preserved across upgrades)Search Order PriorityEvaluated after custom filesEvaluated FIRST by OS CompilerVariant NumberingMust avoid overwriting standard variants (1–6)Can use custom range (e.g. 10–99)Maintenance OverheadHigh (Requires manual backup before updates)Low (Centralized in single custom file)Recommended by Siemens?DiscouragedOfficial Siemens Best Practice

Step-by-Step Procedure to Create and Deploy a Custom Block Icon

Follow this standardized workflow to build and automate a custom block icon:
1. Create the Custom Typicals Graphic:
- In WinCC Explorer, open Graphics Designer.
- Open @PCS7TypicalsAPLV8.pdl.
- Save a copy of the file named @PCS7CustomTypicals.pdl.
- Delete all icons from @PCS7CustomTypicals.pdl except the base icon you wish to modify (e.g. @MonAnL/1).
2. Configure Custom Icon Properties:
- Select the block icon (which is an APL customized object).
- In the Properties palette, expand the System or General property group.
- Change the property type from @MonAnL/1 to @MonAnL/10.
- Modify graphical components: adjust background dimensions, add auxiliary trend buttons, change font colors, or insert company logos.
- Save and close @PCS7CustomTypicals.pdl.
3. Assign the Custom Variant in CFC:
- In SIMATIC Manager, open the CFC chart containing the target technological block (e.g. MonAnL).
- Double-click the block header or right-click and select Object Properties.
- In the Create block icon field, enter 10 (matching the /10 suffix assigned in the type property).
- Click OK.
4. Execute OS Compilation with Block Icon Update:
- In SIMATIC Manager Plant View, right-click the OS project and select Compile.
- In the OS Compile Wizard, ensure the option Create/update block icons is selected.
- Complete the compile process.
5. Inspect the Generated Graphic:
- Open the target process graphic in Graphics Designer: Confirm that your custom variant /10 has been instantiated and wired to the CFC tag.

Verification

Verify custom block icon generation and runtime dynamics:
1. Open the target process graphic in Graphics Designer: Verify that the block icon exhibits the custom geometry, colors, and layout designed in @PCS7CustomTypicals.pdl.
2. Inspect object properties: Verify that property tagname correctly holds the full plant hierarchy path (e.g. Plant1/AreaB/Pump101_Run).
3. Launch WinCC Runtime:
- Confirm the block icon displays live process values, units, and signal statuses.
- Click the block icon: Confirm that the standard APL faceplate opens centered and connected to the target block.
- Simulate an alarm: Verify that the alarm badge and group display on the custom icon illuminate and flash according to APL alarming rules.

Limitations and Operational Precautions

When modifying custom objects, do not delete mandatory internal script connections or standard APL status bit links; altering internal property links can break faceplate navigation or alarm badging.
Variant numbers 1 through 6 are typically reserved by Siemens for standard APL layouts; always use variant numbers 10 and above for custom engineering.
If multiple typicals files define the same variant number, the OS Compiler takes the icon from @PCS7CustomTypicals.pdl, overriding the default system typicals.

Engineer FAQ

Why did the OS Compiler generate the default standard icon instead of my custom icon?

Check the variant number in CFC block properties. If the block property 'Create block icon' is left blank or set to a number not defined in your typicals file, the compiler defaults to variant /1.

Can I create a custom block icon for a non-Siemens third-party block?

Yes, provided the custom block has attribute S7_m_c = 'true' on its parameters and an OS structure tag type exists in WinCC matching the block interface.

Do I need to copy @PCS7CustomTypicals.pdl to OS Clients?

No. Block icons are instantiated into process graphics (.pdl) on the Engineering Station / OS Server. OS Clients simply display the compiled graphics via Server data packages.