Engineering Roadmap and Technical Manual Hierarchy for SIMATIC PCS 7 Project Creation

Creating and programming an industrial automation project in SIMATIC PCS 7 requires a disciplined, top-down engineering methodology distinct from standard PLC programming. Rather than writing standalone ladder logic, PCS 7 engineering centers on the Plant Hierarchy (PH), Continuous Function Charts (CFC), Sequential Function Charts (SFC), and the Advanced Process Library (APL). Engineers should follow the official Siemens documentation hierarchy: begin with 'PCS 7 First Steps' and 'Getting Started Part 1 & 2' for foundational workflows, use 'PCS 7 Compendium Part A - Configuration Guidelines' as the master engineering specification, and consult the 'APL Function Manual' and 'PCS 7 OS Engineering' manuals for detailed control logic and WinCC HMI configuration.

DCS Paradigm vs Traditional PLC Programming

Engineers transitioning from standard programmable logic controllers (PLCs like S7-300 or S7-1500 programmed in STEP 7 or TIA Portal) to SIMATIC PCS 7 frequently struggle because PCS 7 is a Distributed Control System (DCS).

In a traditional PLC environment, the engineer manually assigns memory words, writes ladder logic routines, manually creates DB tags, and independently designs WinCC HMI screens by manually linking tags to screen objects.

In SIMATIC PCS 7, the engineering paradigm is unified and object-oriented:
- Centralized Multiproject: A single Multiproject structure hosts the Automation Stations (AS S7-400), Operator Stations (OS WinCC Servers/Clients), Engineering Stations (ES), and communication networks (Plant Bus and Terminal Bus).
- Plant Hierarchy (PH): The physical plant is structured into technological levels (Plant, Area, Unit, Equipment Module). The Plant Hierarchy automatically dictates AS chart organization, OS picture navigation hierarchies, and tag naming conventions.
- Continuous Function Chart (CFC): Control logic is assembled graphically by placing pre-tested, standardized function blocks from the Advanced Process Library (APL) and interconnecting them with signal lines.
- Automated OS Compilation: When an engineer places a block (e.g., MotL or PIDConL) in CFC, compiling the OS automatically generates the WinCC tag structures, alarm logging entries, archive variables, and block icons in process graphics.

The Official Siemens Technical Manual Hierarchy

Siemens provides thousands of pages of technical documentation for PCS 7. To navigate this literature effectively, engineers should follow the structured reading hierarchy:

flowchart TD
    A["1. Foundational Entry: PCS 7 First Steps & Getting Started Part 1 & 2"] --> B["2. Master Engineering Guide: PCS 7 Compendium Part A - Configuration Guidelines"]
    B --> C["3. Automation Control: PCS 7 CFC / SFC / APL Function Manual"]
    B --> D["4. Visualization: PCS 7 OS Process Control System & WinCC Information System"]
    B --> E["5. Hardware & Comm: S7-400H Fault-Tolerant Systems & PROFINET / PROFIBUS Manuals"]
    C --> F["6. Advanced Execution: Compendium Part B / C / D (Process Safety, Industrial Security)"]
    D --> F

1. The Core 5 Must-Read Documents

PCS 7 First Steps: Practical introductory guide walking through the creation of a basic project, configuring an AS, and compiling an OS.
PCS 7 Getting Started - Part 1 & Part 2: Hands-on tutorial guiding the configuration of a sample water treatment plant using the Advanced Process Library (APL).
PCS 7 Compendium Part A - Configuration Guidelines: The authoritative engineering handbook. Specifies rules for project structure, Plant Hierarchy depth, memory allocation, execution cycle times, and network layout.
PCS 7 Advanced Process Library (APL) Function Manual: Comprehensive encyclopedia of all standard control blocks (PIDConL, MotL, VlvL, MonAnL), documenting all inputs, outputs, operating modes, and feature bits.
PCS 7 Operator Station (OS) Engineering Manual: Master reference for configuring WinCC OS servers, multi-clients, picture trees, alarm logging, and trend curves.

Step-by-Step Project Creation Workflow

Creating a production-ready PCS 7 project follows a strict six-phase engineering lifecycle:

Phase 1: Multiproject Setup and Master Data Library

Launch SIMATIC Manager and select File > 'New Project' Wizard.
Create a Multiproject containing an AS Station (e.g., AS 410-5H or CPU 416-3), an OS Station (WinCC Server/Client), and a Master Data Library (MDL).
Clean out unused blocks and import the latest Advanced Process Library (APL) blocks into the Master Data Library. All project AS stations will derive their blocks exclusively from this central library.

Phase 2: Hardware Configuration (HW Config)

Open HW Config for the AS station.
Configure the rack, power supply, CPU, Industrial Ethernet CP (or onboard PROFINET interfaces), and fieldbus masters.
Add distributed I/O stations (ET 200M, ET 200SP HA) on PROFIBUS DP or PROFINET IO.
Assign symbolic names to all physical I/O channels in the symbol table.

Phase 3: Plant Hierarchy Definition

Open the Plant View in SIMATIC Manager.
Define the technological hierarchy levels (e.g., Level 1 = Site, Level 2 = Unit, Level 3 = Equipment).
Assign picture objects (.pdl) to the appropriate hierarchy folders to establish the WinCC picture navigation tree.

Phase 4: Control Logic Implementation in CFC and SFC

Insert CFC charts into the Equipment Module folders.
Place APL channel driver blocks (Pcs7AnIn, Pcs7DiIn) and control blocks (MotL, VlvL, PIDConL).
Interconnect block parameters and assign physical I/O symbols to channel drivers.
For batch or sequence operations, create SFC charts or SFC Types to govern phase execution.
Execute Options > Optimize Run Sequence in CFC.

Phase 5: Automation Station Compilation and Driver Generation

In SIMATIC Manager, select the Charts folder and click Compile Charts as Program.
Select Generate Module Drivers. The system automatically creates diagnostic and channel driver blocks (MOD_..., CH_...) linking physical I/O modules to process blocks.
Download the compiled program to the S7-400 CPU or S7-PLCSIM.

Phase 6: OS Compilation and Graphic Deployment

Right-click the OS project in SIMATIC Manager and select Compile.
Enable Create/update block icons. The OS compiler imports all tags, alarms, and instantiates block icons into process pictures.
Open WinCC Graphics Designer to arrange block icons and draw static plant equipment.

Core Architectural Concept Matrix

The following matrix contrasts traditional PLC engineering with SIMATIC PCS 7 DCS standards:

Engineering DimensionTraditional PLC (STEP 7 / TIA)SIMATIC PCS 7 DCS ArchitectureLogic ConstructionLadder Logic (LAD), Statement List (STL), SCLGraphical Continuous Function Charts (CFC)I/O ProcessingDirect addressing (IW, QW) or manually mapped DBsAutomated Module Drivers (Pcs7AnIn, Generate Module Drivers)Library StandardizationCustom user blocks or fragmented librariesStandardized Advanced Process Library (APL)HMI Tag GenerationManual tag export/import or tag browser linkingFully automated OS Compilation with structural tag generationAlarm ManagementManual alarm bit mapping in HMI alarm tablesSystem-integrated ALARM_8P with automated timestampingSequential ControlCustom integer state machines or S7-GraphStandardized Sequential Function Charts (SFC / SFC Types)DiagnosticsCustom diagnostic code written by engineerAutomated system diagnostics (hardware, module, channel levels)

Verification

To verify that a new PCS 7 project is configured in accordance with Siemens DCS standards:
1. Open the Plant View in SIMATIC Manager. Ensure all CFC and SFC charts reside strictly within Plant Hierarchy folders rather than in the root S7 Program.
2. In the Blocks folder of the AS, verify that driver blocks with the @ prefix (@MOD_...) exist, confirming that Generate Module Drivers executed successfully.
3. Run an OS Compile with 'Changes only'. Verify that the compile log reports zero errors.
4. Open the OS project in WinCC Explorer. Verify that the Tag Management directory contains structured tags organized under the S7 Named Connection.
5. Launch WinCC Runtime. Verify that the Picture Tree Navigator displays the Plant Hierarchy buttons and clicking a button opens the correct process picture with operational block icons.

Limitations and Operational Precautions

Observe the following structural rules when designing PCS 7 projects:
- Never Program Directly in OBs: In PCS 7, engineers never write code directly inside Organization Blocks (OB1, OB35). The CFC editor automatically manages OB insertion and task run sequences. Manual block calls in OBs will be deleted or cause compiler collisions.
- Maintain Master Data Library Integrity: Never import blocks from standard libraries directly into individual AS stations. Always place blocks into the Master Data Library and distribute them to AS stations to prevent library version drift.
- Do Not Exceed Plant Hierarchy Limits: While PCS 7 supports up to 8 hierarchy levels, Siemens Compendium Part A strongly recommends restricting the hierarchy to 3 or 4 levels to maintain optimal OS compile performance and legible tag names.

Engineer FAQ

Where can I download the official Siemens PCS 7 manuals and updates?

All official manuals, updates, and application examples are published on the Siemens Industry Online Support (SIOS) portal (support.industry.siemens.com). Siemens maintains a dedicated 'PCS 7 Overview' page aggregating all lifecycle documents.

What is the difference between PCS 7 Compendium Part A and Part B?

Compendium Part A focuses on standard project configuration guidelines, system architecture, and performance rules. Compendium Part B focuses on Process Safety (Safety Integrated, F-Systems, and safety matrices). Compendium Part C covers technical functions and Compendium Part D covers industrial security.

Can I create a PCS 7 project without using the New Multiproject Wizard?

Yes, you can create a blank Multiproject manually via 'File > New' and add AS and OS stations individually. However, using the Wizard is recommended for beginners because it automatically establishes the Master Data Library and cross-project connections.