Creating and Assigning Custom APL Block Icon Variants in SIMATIC PCS 7

In SIMATIC PCS 7, creating and assigning custom APL block icon variants for technological objects (such as motors, valves, or analog indicators) requires defining unique icon variants within project typical files and linking them via the CFC block instance properties. In the template file (@PCS7Typicals_Project.pdl), the Customized Object property 'type' is formatted as @/ (for example, @MotL/2 or @MotL/custom1). In Continuous Function Chart (CFC), the engineer specifies this variant number in the block properties under 'Create block icon'. When the OS compilation wizard 'Create/Update Block Icons' is executed, WinCC scans the CFC chart, locates the matching variant in the typical template, instantiates the graphic, and automatically maps the instance tag prefix.

APL Block Icon Variant Architecture in SIMATIC PCS 7

The SIMATIC PCS 7 Advanced Process Library (APL) provides multiple visual representations (variants) for standard technological blocks. For instance, the standard motor block MotL includes variants such as @MotL/1 (standard horizontal orientation with status symbols), @MotL/2 (vertical orientation), @MotL/3 (compact square icon for dense mimic displays), and @MotL/4 (high-performance HMI style).

Each variant is implemented as a WinCC Customized Object (Anwenderobjekt) residing within a typical picture file. The core mechanism linking a controller block in CFC to a specific graphic representation is the Type String defined on the Customized Object: @<BlockType>/<VariantNumber>.

When an engineer designs a plant schematic in Graphics Designer, they do not manually copy and interconnect individual block icons. Instead, they assign a variant index to the block instance in CFC, assign the process picture to the Plant Hierarchy folder, and allow the Create/Update Block Icons wizard to generate and position the icons deterministically.

Template Configuration: System Typicals vs. Project Typicals

To ensure that customized block icons survive software updates and migrations, engineers must adhere to Siemens template hierarchy rules:

System Typicals (@PCS7TypicalsAPLV8.pdl / @PCS7TypicalsAPLV9.pdl): These files are installed and managed by Siemens. During PCS 7 updates, OS Project Editor executions, or service pack installations, these files are silently overwritten. Custom modifications made directly inside system typicals will be lost.
Project Typicals (@PCS7Typicals_Project.pdl or @PCS7Typicals<Name>.pdl): WinCC searches all files in the OS project's GraCS directory whose names begin with @PCS7Typicals. If a block type variant exists in both a project typical file and a system typical file, the wizard prioritizes the project-specific file, allowing engineers to override standard Siemens graphics safely.
Customized Object Interface Consistency: When altering shape dimensions, colors, or fonts, the internal attribute connections (type, tag, servername, TagLowLimit, TagHighLimit) must remain intact to allow the OS wizard to inject instance tag paths.

Block Icon Type Definition and Property Mapping Matrix

The following table details the property requirements and CFC linkages across standard and custom APL icon variants:

Configuration ParameterLocationFormatting SyntaxOperational FunctionCustomized Object TypeGraphics Designer Properties@<BlockType>/<Variant> (e.g., @MotL/5)Identifies block type and variant numberCFC Block Icon PropertyCFC Block Properties (General)Numeric index (e.g., 5) or textInstructs the wizard which variant to deployTag Connection PropertyCustomized Object tagDot prefix (e.g., .)Completed with <Chart>/<Block> at compileServername PropertyCustomized Object GeneralPCS7 <BlockType> ControlBinds the icon to the APL faceplate engineStatus Double-WordsCustomized Object Links.Status1, .Status2, .Status3Drives dynamic status colors and state flagsTemplate File PrecedenceOS GraCS Directory@PCS7Typicals_Project.pdlOverrides standard system typical templates

Step-by-Step Procedure to Create and Assign Custom Icon Variants

To create a custom block icon variant and assign it to a CFC instance:

Create the Project Typical File:
- In WinCC Explorer on the Engineering Station, open Graphics Designer.
- Open @PCS7TypicalsAPLV8.pdl (or V9) from the project GraCS folder.
- Select File -> Save As, and save the file as @PCS7Typicals_Project.pdl.
Create and Customize the New Icon Variant:
- Inside @PCS7Typicals_Project.pdl, locate the standard motor icon @MotL/1.
- Copy and paste the object to create a duplicate within the same picture.
- Right-click the duplicate object and select Configuration Dialog.
- Change the property type from @MotL/1 to @MotL/5 (or another unused variant number).
- If modifying graphics, right-click the object and select Customized Object -> Edit.
- Adjust rectangle sizes, fonts, or add static text indicators, then select all objects and choose Customized Object -> Finish Editing.
- Save and close @PCS7Typicals_Project.pdl.
Assign the Variant Number in CFC:
- In SIMATIC Manager, open the CFC chart containing the motor block instance (MotL).
- Double-click the MotL block header to open Block Properties.
- Ensure the checkbox Create block icon is checked.
- In the text box adjacent to the checkbox, enter the variant index: 5.
- Click OK to close block properties.
Generate Block Icons in WinCC:
- Ensure the CFC chart is placed inside a Plant Hierarchy folder assigned to a WinCC process graphic.
- In SIMATIC Manager, select the plant hierarchy folder, then select Options -> Plant Hierarchy -> Create/Update Block Icons.
- In the generation dialog, select your target OS and click OK.
- Open the destination process graphic in Graphics Designer; confirm that the custom @MotL/5 icon is inserted with all tags connected.

Verification

Verify custom block icon functionality:
1. Open the process picture in Graphics Designer; select the generated block icon and verify that property tag is populated with the full instance tag path (e.g., Plant/Area/Line1_MotL).
2. Launch WinCC Runtime; verify that the custom icon displays active motor running states (green), stopped states (grey), and alarm frames.
3. Click the block icon in Runtime; confirm that the standard @PG_MotL.pdl faceplate opens cleanly.
4. Run a test OS Compile; confirm that compilation completes without block icon warnings and that custom graphics are preserved.

Limitations and Operational Precautions

Never Overwrite Standard System Typicals: Do not modify @PCS7TypicalsAPLV8.pdl directly. All custom variants must reside in @PCS7Typicals_*.pdl.
Variant Number Collision: Ensure the variant number (e.g., /5) does not collide with existing Siemens variants (/1 through /4) to prevent unpredictable wizard instantiation.
Customized Object Integrity: Do not dissolve (ungroup) customized objects on process graphics, as ungrouping destroys the internal tag-binding interface and faceplate scripts.

Engineer FAQ

How does PCS 7 know which block icon variant to place on a picture?

The wizard matches the numeric index entered in the CFC block properties under 'Create block icon' with the suffix of the 'type' property (@/) in the typicals file.

Can I use alphanumeric variant names instead of numbers?

Yes. You can configure '@MotL/Small' in the typical file and enter 'Small' in the CFC block icon field.

Why did my custom block icon disappear after OS Compile?

If 'Create/Update Block Icons' was re-run without saving the icon in an '@PCS7Typicals_*.pdl' file, the wizard replaced the icon with a clean template from the system file.