Exporting PCS 7 Data to Excel: Process Object View and XML Tools

Engineers maintaining Siemens PCS 7 installations routinely need to extract project data — data block structures, function block connections, symbol tables, CFC/SFC topology, and runtime parameter values — for documentation, audit, migration, and engineering change orders. PCS 7 stores this information in a layered set of binary and database files (chiefly *.DBF, *.S7P, *.ZIP archive containers, and auxiliary *.XDB caches) under the project root. While these files are partially encrypted and version-sensitive, Siemens ships several first-party tools that expose the data in human-readable form, and the resulting tables can be pivoted, copied, or scripted into Excel, Access, or any text-aware downstream tool. This reference walks through the supported extraction paths, their limitations, and the engineering judgment required to pick the right one for a given task.

1. PCS 7 Project File Architecture

Before selecting a tool, identify which data category you need. PCS 7 segregates information into multiple storage layers, and each tool exposes a different subset.

2. Prerequisites

1. Installed and licensed PCS 7 Engineering System at the same major version as the project (V8.2 / V9.0 / V9.1 / V10.0). Cross-major access to a project is not supported and will trigger "Version incompatible" errors during compile.
2. Valid license for the Process Object View option (part of the standard PCS 7 ES scope; not separately licensed on V9.0+).
3. Read-only or read/write OS rights to the project directory on the engineering station. The PCS 7 project must be closed in SIMATIC Manager and any background S7-PCT or S7-Graph editors.
4. Microsoft Excel 2010 or later (32-bit recommended) for paste/copy operations; large process object views (>200,000 tags) require Excel 2016+ with the 64-bit build and 8 GB RAM minimum.
5. For XML-based interchange: the XML Transfer Tool add-in, installed via the PCS 7 setup under Options > PCS 7 Tools.

3. Method 1 — Process Object View (POV)

The Process Object View is the most direct path for engineers who need a process-oriented view of the entire automation hierarchy. It consolidates the process tag type, I/O assignment, message configuration, OS picture, and operator faceplate parameters into a single tabular display that can be filtered, sorted, and copied straight to Excel.

3.1 Opening the POV

1. In SIMATIC Manager, select the S7 Program node of the AS station (e.g. AS01 > S7 Program(1)).
2. Right-click and choose Process Object View, or use menu Options > Process Object View.
3. The POV opens in a separate window with the standard columns: Name, Comment, Type, AS, OS, Message, I/O, Block icon, Picture, Operating range, …

3.2 Filtering to a Subset

Use View > Filter to restrict the displayed set, e.g. Type = CTRL_PID to show only PID controllers, or AS = AS02 to limit to a single automation system. Filter expressions can be combined with logical AND/OR using the syntax (Type = MOT_SPEED) AND (OS = OS1).

3.3 Copy to Excel

1. Press Ctrl+A to select all rows (or hold Shift and click column headers for column subsets).
2. Press Ctrl+C. POV places tab-delimited text on the clipboard with column headers in the first row.
3. Open Excel, click cell A1, press Ctrl+V. Use Data > Text to Columns with the Tab delimiter to split fields.
4. Save as .xlsx. For downstream consumption by PIVOT tables or Power BI, use File > Save As > CSV UTF-8.

3.4 What POV Does Not Expose

POV is a high-level view. It does not include:

• Raw symbol table entries (use the Symbol Editor export).
• Compiled instance DB contents (use PLC > Upload to PG, or cross-reference from the S7 program).
• Low-level CFC sheet coordinates or runtime diagnostics.
• Custom user-defined DB structures that are not derived from a process tag type.

For these, fall back to the Symbol Editor, the CFC > Chart > Export functions, or the XML Transfer Tool described in section 4.

4. Method 2 — XML Transfer Tool

The XML Transfer Tool is the only first-party mechanism that produces a vendor-neutral, machine-readable export of the project suitable for interfacing with PAA, COMOS, or SIMIT. It is invoked from the SIMATIC Manager menu and produces a single .xml file plus auxiliary XSD schemas.

4.1 Generating the XML

1. In SIMATIC Manager, select the project root or a specific S7 Program.
2. Choose Options > XML Transfer Tool > Export.
3. Select the scope: Complete project, Selected S7 program, or Selected chart.
4. Choose the target schema version (default = current PCS 7 major; older schemas available for backward compatibility with COMOS 10.x).
5. Click Export; the file PCS7_Export_<ProjectName>_<Timestamp>.xml is written to the configured directory.

4.2 XML Structure

The exported document follows a fixed hierarchy:

<PCS7_Project version="9.0" generated="2024-...">
  <Plant>
    <Unit> id="U01" name="Reactor Feed">
      <ProcessTagType name="CTRL_PID"> ... </ProcessTagType>
    </Unit>
  </Plant>
  <AS id="AS01">
    <CFC name="Reactor_Temp.sfc">
      <Block instance="PID_001" type="CTRL_PID">
        <Input name="SP" connection="TAG_TEMP_SP"/>
        <Parameter name="GAIN" value="1.20"/>
      </Block>
    </CFC>
  </AS>
</PCS7_Project>

4.3 What the XML Contains and Omits

4.4 Post-Processing the XML in Excel

1. Open Excel 2016+, choose Data > Get Data > From File > From XML.
2. Select the exported .xml file; the Power Query navigator lists the root tables.
3. Click Transform Data; expand nested <Parameter> and <Input> nodes to rows.
4. Use Close & Load to land the data in a worksheet, then build pivot tables on block counts, parameter distribution, or unused tags.

For very large projects (5,000+ CFCs), use the Power Query XML.Tables M-function in a custom query to stream only the nodes you need instead of loading the full document into memory.

5. Method 3 — Direct Symbol and DB Export from SIMATIC Manager

When the symbol table or specific data block layout is required, the SIMATIC Manager itself provides export functions that bypass the higher-level tools.

5.1 Exporting the Symbol Table

1. Open the Symbol Editor from the S7 program.
2. Select all symbols (Ctrl+A) or filter to the desired address range.
3. Choose Symbol Table > Export and pick a .SDF, .CSV, or .AWL destination.
4. Import the resulting CSV into Excel using Data > From Text/CSV with comma as the delimiter.

5.2 Exporting Data Block Structures

1. Open the target DB in the LAD/FBD/STL editor.
2. Choose File > Generate Source to produce an STL source file (DB1.AWL) that contains the full declaration section.
3. The STRUCT and END_STRUCT blocks can be parsed with a small script (e.g. PowerShell) to a CSV of Name, Type, Offset, Comment.

5.3 Uploading Live Instance DBs

For runtime values, the procedure is different and operates over MPI/PROFINET to the AS:

1. Establish an online connection: PLC > Connect to Target System.
2. Choose PLC > Upload Station to PG to read the entire AS image including instance DBs.
3. Open the uploaded DB; right-click > Monitor/Modify to view live values. Snapshot to CSV via Table > Copy.

6. Method 4 — Programmatic Access via COM and DLL

Siemens exposes the SIMATIC Manager's project tree as a COM automation model. This is the path to scripted, repeatable extraction without manual clicks.

6.1 The SIMATIC Automation Model

The type library S7WEBSVC.DLL and the older STEP7.DLL expose the SIMATIC.Project hierarchy. From PowerShell or any COM-capable language:

$project = New-Object -ComObject "S7Proj.S7Project"
$project.Open("C:\PCS7_Projects\Plant01\Plant01.S7P")
$stations = $project.Stations
foreach ($s in $stations) {
    $programs = $s.S7Programs
    foreach ($p in $programs) {
        Write-Output ("{0}\{1}" -f $s.Name, $p.Name)
    }
}
$project.Close()

6.2 Using the XML Transfer Tool from the Command Line

The XML Transfer Tool can also be called headlessly:

"C:\Program Files\Siemens\Automation\PCS7\XML_Tool\xml_transfer.exe" ^
  /export ^
  /project "C:\PCS7_Projects\Plant01\Plant01.S7P" ^
  /scope complete ^
  /out "D:\Export\Plant01.xml" ^
  /schema V9.0

This makes the export a scheduled task: the resulting XML is dropped to a network share, and a Power BI gateway refreshes dashboards each morning.

6.3 COM Method Caveats

• The COM model is 32-bit only on most PCS 7 versions; PowerShell must be launched as %SystemRoot%\SysWOW64\WindowsPowerShell\v1.0\powershell.exe on a 64-bit OS.
• Calling the COM model on a project open in SIMATIC Manager can return read-only handles. Close the project first.
• Third-party vendors (Innovex, M&M Software, COPA-DATA) wrap the same COM model behind higher-level Python or C# libraries, which is the practical path for non-Siemens integrations.

7. Cross-Reference: Exporting to Excel from Non-Siemens Tools

The same "copy a structured view into Excel" pattern is the de-facto standard for engineering documentation across all major DCS platforms. For comparison, Microsoft Project exposes its schedule through File > Save As > Workbook or by using the Export to Excel add-in documented at the Microsoft Project export support page. The technique is identical: structured source → tabular clipboard → spreadsheet → pivot/chart. Adopting this pattern in PCS 7 with POV or XML Transfer Tool yields the same downstream benefits: PIVOT tables, XLOOKUP merges against the I&E database, and version-controlled CSV diffs in Git.

8. Method Comparison

9. Engineering Workflow: Typical Audit

The following 8-step workflow produces a signed, traceable project-data audit suitable for a regulatory submission (e.g. 21 CFR Part 11 / EU GMP Annex 11).

1. Verify the project checksum with the PCS 7 project integrity tool (Project > Check Project Consistency).
2. Close the project in SIMATIC Manager.
3. Run the XML Transfer Tool headlessly to D:\Audit\XML\<Project>_<Timestamp>.xml.
4. Run the Symbol Editor export to D:\Audit\CSV\<Project>_symbols_<Timestamp>.csv.
5. Generate STL sources for all global DBs into D:\Audit\AWL\.
6. Power-Query the XML into Excel workbook D:\Audit\<Project>_audit_<Timestamp>.xlsx.
7. Generate a SHA-256 hash of each export and write it to a manifest CSV.
8. Archive the directory with the manifest hash in the document management system.

10. Troubleshooting Matrix

11. Version-Specific Notes

• PCS 7 V8.2: Last release to support the legacy SIMATIC Manager exclusively; XML schema is V8.2 with limited parameter coverage.
• PCS 7 V9.0: Introduced multi-user engineering in the SIMATIC Manager; XML Transfer Tool gains /scope:program for incremental exports. The PCS 7 Compendium Part A — Configuration Guidelines (V9.0) documents the Process Object View workflow in the chapter Managing process tag types with the process object view.
• PCS 7 V9.1: XML schema v9.1 adds native PROFIsafe parameter export.
• PCS 7 V10.0: Process Object View supports column-level export to .xlsx directly (right-click > Export > Excel Open XML); XML Transfer Tool CLI gains a /filter argument for unit scoping.

12. Security and Compliance Considerations

Project data files often contain passwords, IP addresses, and process-critical setpoints. Treat every export as controlled documentation:

• Store exports only on access-controlled shares; never email as attachments.
• Apply a project-specific watermark or hash (SHA-256) at export time to detect tampering.
• Redact user IDs and passwords from XML output before third-party distribution; the XML Transfer Tool has a /redact-pwd flag from V9.1 onward.
• Log every export event (user, timestamp, file, hash) in the audit trail per 21 CFR Part 11 §11.10(e).

13. References to Official Documentation

For schema details, error code tables, and upgrade procedures, consult the following official Siemens manuals, all available on the Siemens Industry Online Support (SIOS) portal:

• PCS 7 Compendium Part A — Configuration Guidelines (edition for the deployed V9.x or V10.0), chapter Managing process tag types with the process object view.
• PCS 7 Engineering System (function manual), chapter The process object view.
• PCS 7 XML Transfer Tool (release notes and schema XSDs).
• SIMATIC S7-300/400 Automation System — Programming with STEP 7, for the COM automation model and the Symbol Editor.

FAQ