Exporting SIMATIC PCS 7 Alarm and Tag Logging Data to Hourly CSV Reports via WinCC IndustrialDataBridge

In SIMATIC PCS 7 (v8.0, v8.1, and v8.2), automated hourly export of historical Tag Logging process values and Alarm Logging event records into comma-separated value (.csv) files is achieved using SIMATIC WinCC IndustrialDataBridge (IDB). IDB acts as an automated middleware bridge connecting the WinCC OLE-DB Provider (data source) to a CSV/Text file destination module (data consumer). Configured via the IDB Configuration Manager with a 3600-second cyclic timer trigger, IDB queries the WinCC SQL archive segments directly without disrupting runtime operations and writes structured time-stamped records into target network directories.

IndustrialDataBridge Architecture in SIMATIC PCS 7

In regulated process industries (pharmaceuticals, water treatment, chemical processing), external enterprise systems, reporting tools, and lab information management systems (LIMS) require periodic raw data extracts from the control system. In SIMATIC PCS 7 standalone OS or distributed OS servers, SIMATIC WinCC IndustrialDataBridge (IDB) provides a standard, parameter-driven software interface:
1. Modular Architecture:
- Data Source: Connects to the plant data repository (WinCC OLE-DB Provider, OPC DA, OPC HDA, OPC UA, or direct relational databases).
- Data Consumer: Delivers data to destination formats (CSV/Text files, Microsoft Excel workbooks, Microsoft SQL Server, Oracle, or OPC destinations).
2. Execution Triggers:
- Triggers can be event-driven (a PLC bit change via OPC) or time-driven (cyclic timer, e.g. every 60 minutes).
3. Non-Intrusive Operation:
- IDB accesses historical archive tables via the certified WinCC OLE-DB interface rather than raw SQL SELECT queries, ensuring that database locks and buffer pools in Microsoft SQL Server are not corrupted or blocked.

Data Source Configuration - WinCC OLE-DB Provider

To extract Tag Logging and Alarm Logging archives:

Prerequisites:
- The WinCC Connectivity Pack (or WinCC Open Development / Connectivity Station) license must be present on the OS station hosting the data.
- The WinCC OLE-DB Provider driver must be registered in Windows.
Source Link Parameterization in IDB:
- Launch IndustrialDataBridge Administration.
- Create a new project (e.g. Hourly_PCS7_Export).
- Define the Data Source:
- Provider: Select WinCC OLE-DB Provider.
- Connection String: Specify the local WinCC runtime database catalog name (or browse to the active project .mcp file).
- Query Type: Select Tag Logging (Historical Process Values) or Alarm Logging (Historical Messages).
- For Tag Logging: Select the target process tags (e.g., TIC_101/PV_Out.Value, FIC_102/PV_Out.Value) and specify the extraction interval (e.g., past 1 hour, cyclic time window).
- For Alarm Logging: Specify filter criteria (e.g., Message Class = Alarm/Warning, state = active or acknowledged).

Data Consumer Configuration - CSV File Generation

Configuring the output file destination in IndustrialDataBridge:

Define Data Consumer:
- Select CSV File / Text File as the Consumer module.
- Target Directory: Enter the local path (e.g. D:\PCS7_Reports\Hourly\) or a mapped network UNC path (\\FileServer\Reports\).
File Naming and Timestamp Formatting:
- Configure dynamic file naming using macros: PCS7_Log_<YYYY><MM><DD>_<hh><mm>.csv.
- Set delimiter to comma (,) or semicolon (;).
- Enable Write Header Row containing Tag Name, Timestamp (UTC or Local), Engineering Unit, and Process Value.
Configure Cyclic Trigger:
- Navigate to the Triggers tab.
- Select Timer Trigger.
- Set cycle time to 3600 seconds (1 hour).
- Link the timer trigger to the configured Source-Consumer link pair.
Service Mode Deployment:
- Deploy IDB as an automatic Windows Service (CCDataBridge.exe) so data extraction operates autonomously without requiring an active Windows user login session.

IndustrialDataBridge Licensing and Operational Constraints

Commercial Accuracy Disclaimer: Software order numbers (MLFBs), package structures, and hardware capacity prerequisites vary across PCS 7 versions and hardware platforms. System integrators must confirm exact software entitlements and licensing requirements against the official Siemens Catalog CA 01 and obtain an authorized Siemens distributor quotation prior to purchasing.

Deploying IndustrialDataBridge requires verifying software entitlements in Automation License Manager (ALM):
- WinCC IndustrialDataBridge License: Licensed based on the number of active tags/variables transferred (e.g., packages of 100, 500, 1000, 10000 tags; e.g. MLFB 6AV6371-1DX07-4AX0 or release-specific equivalent).
- WinCC Connectivity Pack License: Mandatory on the OS station when querying historical Tag Logging or Alarm Logging via the WinCC OLE-DB Provider (e.g. MLFB 6AV6371-1DH07-4AX0).
- Runtime licenses must be installed on the local PC executing the IDB software service.

IndustrialDataBridge vs Alternative PCS 7 Data Export Methods Table

The following table compares IDB against other common reporting and data extraction solutions:

Solution ArchitectureLicensing RequirementsSetup ComplexityReal-Time Impact on OSSupported Export FormatsWinCC IndustrialDataBridge (IDB)IDB Tag License + Connectivity PackLow (Configured via graphical UI, zero coding)Minimal (Read-only via optimized OLE-DB)CSV, TXT, Excel, SQL Server, Oracle, OPCCustom VBScript / C-Script in WinCCStandard WinCC RTHigh (Manual ADODB connection scripts)Medium to High (Risk of thread stalls if queries block)CSV, TXT, ExcelSIMATIC Process Historian & Information Server (PH/IS)PH RT PO + IS Server / Client LicensesMedium (Enterprise reporting suite)Zero (Queries offloaded to dedicated historian server)Automated PDF, Excel, Word, Web DashboardsDirect Microsoft SQL Query (Raw SQL)Not supported by SiemensHighSevere (Can corrupt transaction logs, invalidate warranty)Any SQL-compatible format

Verification

To confirm that IDB is successfully exporting hourly CSV files:
1. In IndustrialDataBridge Administration, click Test Connection for both the WinCC OLE-DB Source and the CSV Consumer. Verify both return successful handshakes.
2. Manually trigger a test execution using the Run Once button.
3. Open Windows Explorer at D:\PCS7_Reports\Hourly\ and confirm that a new .csv file was generated with the correct timestamped name.
4. Open the CSV file in a text editor or Excel:
- Check that the header row is formatted correctly.
- Verify that process timestamps, tag names, and analog values match the historical values shown on the WinCC Trend Control for that hour.
5. Leave the system running and check back after 3 hours to confirm that 3 distinct hourly CSV files were created automatically.

Limitations and Operational Precautions

When using IndustrialDataBridge in SIMATIC PCS 7:
1. Never Perform Direct SQL Writes into WinCC: IDB should only read from WinCC OLE-DB. Writing external data into WinCC internal tables can corrupt the Alarm Logging and Tag Logging database schemas.
2. Network Share Buffering: If the target CSV destination is a remote corporate file share, ensure network interruptions do not cause IDB service hangs. Configure local temporary directory caching where supported.
3. Query Time Span Limits: Ensure the time span of each query matches the trigger cycle (e.g. past 60 minutes for a 60-minute trigger). Querying oversized time windows (e.g. 30 days) every hour will overload the SQL Server CPU and disk I/O.

Engineer FAQ

Can IndustrialDataBridge export both alarms and tag trends into the same CSV file?

No. Alarms (discrete events with text strings and acknowledgment states) and Tag Logging (analog time-series values) possess different database schemas. They must be configured as two separate IDB links generating separate CSV files.

Does IndustrialDataBridge require WinCC to be in runtime to export data?

Yes. The WinCC OLE-DB Provider queries the SQL Server database instances attached by the active WinCC runtime project. If WinCC Runtime is stopped, historical segments are detached and unavailable.

How does IDB handle daylight saving time changes?

Because WinCC stores all historical timestamps in UTC, configuring IDB to output UTC ensures continuous chronological logs without duplicate or omitted hours during DST transitions.

Can IDB run on a remote office PC rather than the PCS 7 OS station?

Yes, via the WinCC Connectivity Station package. IDB can reside on a remote workstation accessing the WinCC OS Server over the plant terminal bus via authenticated OLE-DB network calls.