Export Process Historian Runtime Data for External Use
Process Historian documents a CSV export workflow in its Management Console. Select the time range, destination and tag names, then export runtime data instead of building an integration around undocumented HistorianStorage tables. Although Process Historian runs on SQL Server, the Siemens manual reviewed here does not define its internal schema as a public .NET query interface; confirm direct database access for the installed release before depending on it.
Table of Contents
- Direct database connection
- Export runtime data to CSV
- Procedure
- Verification
- Limitations and Operational Precautions
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
Direct database connection
Process Historian installs a dedicated “Historian” Microsoft SQL Server instance. A .NET program's ability to connect depends on SQL authentication, network configuration and permissions. The Siemens manual reviewed here does not define the internal HistorianStorage schema as a public query interface or specify a direct-query API. Do not build a durable data exchange against undocumented internal tables.
Export runtime data to CSV
The SIMATIC Process Historian System Manual (07/2024) documents a Management Console dashboard named “Export runtime data.” Set the time range, destination folder and language, then select measured-value tags from a flat list/filter or the PCS 7 plant hierarchy. The documented output uses system-generated CSV filenames, one file per tag plus a file for all messages of a data source.
Procedure
- Open the Process Historian Management Console and the Export runtime data dashboard.
- Set the required time range, destination folder and language.
- Add the required tag names using the flat list/filter or plant hierarchy.
- Select required message/alarm data where applicable.
- Export, then inspect file names, timestamp coverage, tag identity and representative values before delivery.
Verification
Check that the exported tags and time interval match the request, verify representative values and timestamp interpretation, and confirm expected message/alarm content. Do not assume an export completed with complete coverage merely because files were created.
Limitations and Operational Precautions
The ticket does not identify the Process Historian or SQL Server version. The 2024 manual verifies CSV export but does not answer whether every internal database table is queryable or establish direct SQL as a public integration interface. Exported runtime data is not encrypted; protect the folder and transfer channel.
Engineer FAQ
Does the manual document a .NET API for HistorianStorage? No. It documents application-level export, not an internal database schema/API.
Can the Management Console export usable CSV data? Yes. The documented workflow exports selected runtime values and messages to CSV; confirm version-specific details.
Technical References
- SIMATIC Process Historian System Manual, 07/2024, A5E53524470-AA, section 3.3, “Exporting runtime data,” pp. 126–127; official PDF opened and read.
- SIMATIC Process Historian System Manual, 10/2022, A5E52028712-AA; opened for release-context cross-check.
Related Articles
Related Tags
Process Historian, CSV export, SQL Server, Information Server