Locating and Integrating Legacy Standard Library Block Icons (Typicals) in PCS 7 V8 and V9

When maintaining or modifying legacy SIMATIC PCS 7 projects built with Standard Library V7.1 using newer engineering software (such as CFC V8.1/V9.0 and WinCC V7.3/V7.4), the required classic block icon template is @PCS7Typicals.pdl (not the APL files @PCS7TypicalsAPLV7.PDL or @PCS7TypicalsAPLV8.PDL). In modern PCS 7 releases, legacy Standard Library typicals are provided via the 'Software update without utilization of new functions' migration package. To integrate them, copy @PCS7Typicals.pdl from the Siemens installation folder or migration media into the OS project's GraCS directory, and execute 'Create/Update Block Icons' in SIMATIC Manager Plant View.

Block Icon Evolution: Standard Library vs Advanced Process Library (APL)

In SIMATIC PCS 7, block icons represent controller function blocks graphically on WinCC process overview screens. The design and structure of block icons underwent a major generational paradigm shift:

Standard Library (Classic, V6.x / V7.x): Utilized classic block icons for technological blocks such as MEAS_MON (FB65), MOTOR (FB66), VALVE (FB73), and CTRL_PID (FB61). All block icon templates were consolidated into a single master template file strictly named @PCS7Typicals.pdl.
Advanced Process Library (APL, V7.1 SP1 onwards): Re-engineered all block icons to follow modern ergonomic standards, creating dedicated template files named @PCS7TypicalsAPLV7.pdl, @PCS7TypicalsAPLV8.pdl, and @PCS7TypicalsAPLV9.pdl.

When engineers open a migrated OS project in WinCC V7.3 or V7.4, the Graphics Designer default library displays only the APL typicals. The classic Standard Library block icons appear missing because their template file must be manually retrieved from the legacy migration repository.

Software Update Without Utilization of New Functions Concept

Siemens defines two distinct migration pathways for aging PCS 7 installations:

Software Update with Utilization of New Functions: Involves a complete block exchange in the AS from Standard Library to APL, redesigning all graphics and faceplates. This is costly and requires an extended plant turnaround.
Software Update WITHOUT Utilization of New Functions: Allows the plant to upgrade PC hardware and engineering software (e.g., migrating to Windows 7 / Windows 10 with PCS 7 V8.2 or V9.0) while leaving the controller logic running legacy Standard Library blocks. To support this mode, Siemens supplies legacy faceplates, scripts, and @PCS7Typicals.pdl files compatible with modern WinCC releases.

Block Icon Typicals File Naming and Version Reference Matrix

The following table identifies template filenames, supported block libraries, and default source locations:

Template File NameTarget Library FamilySupported Block TypesSource Installation Directory@PCS7Typicals.pdlStandard Library V7.1 / V6.xMOTOR, VALVE, MEAS_MON, CTRL_PID<Drive>:\Program Files (x86)\Siemens\WinCC\Options\PDL\StandardLibrary\@PCS7TypicalsAPLV7.pdlAPL V7.1MotL, VlvL, MonAnL, PIDConLDefault WinCC GraCS template folder@PCS7TypicalsAPLV8.pdlAPL V8.0 / V8.1 / V8.2Modernized APL drives and controllersDefault WinCC GraCS template folder@PCS7TypicalsAPLV9.pdlAPL V9.0 / V9.1Current generation APL technological blocksStandard PCS 7 V9.0 installation@Template.pdlProject-Specific CustomCustom engineered icons and symbolsUser created in OS GraCS directory

Step-by-Step Procedure to Integrate Legacy Typicals into Modern WinCC

To restore classic Standard Library block icons into your PCS 7 V8.x or V9.x engineering system:

Locate the Legacy Template File:
- On your PCS 7 installation media (or the installed engineering drive), navigate to the migration folder: <Drive>:\Program Files (x86)\Siemens\WinCC\Options\PDL\StandardLibrary\.
- Locate the file @PCS7Typicals.pdl.
- If unavailable on disk, copy @PCS7Typicals.pdl from an un-migrated V7.1 backup project.
Copy Template to OS Project GraCS:
- In Windows Explorer, browse to your active OS project directory: <Multiproject>\<OS_Station>\wincproj\<OS_Name>\GraCS\.
- Paste @PCS7Typicals.pdl into the GraCS folder.
Ensure Legacy Faceplate Support Files are Present:
- Verify that classic faceplate files (e.g., @PG_VALVE.pdl, @PG_MOTOR.pdl) and C scripts (s7*.fct) are present in the project's GraCS and Library directories.
Execute Block Icon Creation in SIMATIC Manager:
- In SIMATIC Manager Plant View, right-click the target Plant Hierarchy folder or multiproject.
- Select Plant Hierarchy -> Create/Update Block Icons.
- In the wizard, ensure the option @PCS7Typicals.pdl is recognized.
- Execute the generation. The wizard parses @PCS7Typicals.pdl and instantiates the classic block icons in all target process pictures.

Verification

Verify block icon instantiation:
1. In WinCC Graphics Designer, open a process screen containing Standard Library blocks.
2. Confirm that classic block icons (e.g., the classic green/red motor box or valve symbol) are rendered correctly.
3. Open WinCC Runtime.
4. Click a classic block icon to confirm that the legacy Standard Library faceplate opens without script error popups.
5. Verify that live process values, control commands, and alarm states operate as expected.

Limitations and Operational Precautions

Do Not Mix Library Typicals: Do not attempt to merge classic Standard Library block icons into @PCS7TypicalsAPLV8.pdl. Keep classic icons in @PCS7Typicals.pdl to avoid type parsing conflicts.
OS Project Editor Template Protection: If the OS Project Editor is run with 'Update Picture Files' enabled, it will overwrite standard files. Ensure customized typicals are protected.
Long-Term Modernization: Standard Library V7.1 blocks are in product phase-out; plan a full migration to APL during the next major control system upgrade.

Engineer FAQ

Can APL faceplates be opened from classic Standard Library block icons?

No. Classic Standard Library block icons call classic faceplate scripts (s7.fct) and classic PDLs (@PG_.pdl). They cannot interface with APL faceplate OCX controls.

What happens if both @PCS7Typicals.pdl and @PCS7TypicalsAPLV8.pdl exist in GraCS?

The Block Icon Wizard evaluates block types: APL blocks pull icons from @PCS7TypicalsAPLV8.pdl, while classic blocks pull icons from @PCS7Typicals.pdl based on the block type name.

Why did the Create/Update Block Icons wizard fail to create icons for FB73?

Ensure the block in CFC has 'Create block icon' enabled in Object Properties, that the chart folder has Plant Hierarchy assignment, and that @PCS7Typicals.pdl is present in GraCS.

Where can I find the official manual for software updates without new functions?

Consult the Siemens manual 'SIMATIC Process Control System PCS 7 Software Update without Utilization of New Functions' corresponding to your target PCS 7 release.