Connections to 3rd Party Data Sources

Connections to 3^rd Party Data Sources 

In addition to dataPARC’s native historian and internal database sources, connections can be made to a wide array of 3^rd party data sources so that all integrate seamlessly into PARCview displays, reports, calculations, etc.

Summary of available connections:

Connecting dataPARC to any combination of these sources can bring their data together in PARCview for visualization (trend, graphic, pareto, centerline, etc.). Additionally, tags from all sources can contribute to automated calculations and reports. Data from these sources are not duplicated in the dataPARC historian, thus reducing their disk space and hardware requirements.

OPCDA, HDA

OPC Server data sources utilizing the OPCDA or OPCHDA protocol can be configured as dataPARC data sources.

Use Cases

This connection type is best for data sources that include an OPC Server, but do not have a specific source type pre-configured in dataPARC. Each data request by a dataPARC collector app will trigger an OPC call to the source to fetch data. Aggregates can be calculated within dataPARC or read from the historian.

Common Historian ProgID List:

DeltaV Continuous Historian       DeltaV.OPCHDAsvr

ABB 800XA                                     ABB.RtdbOpcHdaServer

Rockwell FactoryTalk                   OSI.HDA.1

Canary                                             CanaryLabs.OPCHDAServer

GE iFix Proficy                                Proficy.Historian.HDA

MOPS                                              MOPS.MOPSOPCHDAHIST.1

Yokogawa Exaquantum               Yokogawa.ExaopcHDA_PIAEEXQ.1

Aveva PI

dataPARC reads data directly from the PI historian utilizing the PI API or SDK.

Use Cases

Facilities with established PI historians can benefit from adding dataPARC for visualization, calculations, reporting, alarms and more.

Aveva PI AF

PARCview reads asset data directly from the PI historian if clients also have the PI AF SDK installed, OR utilizes a Remote UA server if the dataPARC server has the PI AF SDK installed (clients are routed through the server). Exposes asset element and template hierarchy and allows selecting entire tag templates for visualization. Event frames are not exposed via this connection.

Use Cases

Facilities with established PI historians with Asset Framework can connect dataPARC using the PI AF SDK. This allows access to the Asset Framework and can also improve long-term data query performance.

Rockwell FactoryTalk

The Rockwell FactoryTalk historian is based on the Aveva PI historian, so all connection options/settings are similar.

Use Cases

Facilities with Rockwell FactoryTalk historians can benefit from adding dataPARC for visualization, calculations, reporting, alarms and more.

Aspentech IP.21

dataPARC reads data directly from the IP.21 historian utilizing the Process Explorer API for data reads and the IPSQL ODBC connection type for reading the tag list.

Use Cases

Facilities with established IP.21 historians can benefit from adding dataPARC for visualization, calculations, reporting, alarms and more.

SQL

dataPARC reads data from an SQL database using standard SQL calls.

Use Cases

Facilities with pre-existing and/or custom data histories in SQL databases can add these as a dataPARC source for full functionality in visualization, calculations, reporting, alarms and more.

Common Queries

Tag Scripts

Tag List – Returns list of tags used by the template

Tag Info. – Returns tag information

Limit – Returns tag limits

Read Data Scripts

Current – Returns current value

Data – Returns raw data for specified time period

Data Prior – Returns value just prior to start time for use as start bound point

Data After – Returns value just after end time for use as end bound point

Projection – Returns projected (future) data

Data Plot – Returns plot-reduced data set for trends

Data Aggregate – Returns aggregated data

Data Providers

**Note: dataPARC’s SQL dataseries does not support EntityClient Provider (System.Data.EntityClient) or .NET Framework Data Provider for SQL Server Compact 4.0 (System.Data.SqlServerCe).

PHD

dataPARC reads data directly from the PHD historian utilizing the Com, ComRemote, NetRemote, NetApi200 or NetApi150 connection type.

Use Cases

Facilities with established PHD historians can benefit from adding dataPARC for visualization, calculations, reporting, alarms and more. Aggregates can be calculated within dataPARC or read from historian.

Proficy

PARCview reads data directly from the Proficy historian if clients also have the Proficy client installed, otherwise they are routed through the dataPARC server using the HDA remoting source. Can use API to read from legacy Historian (v5 and v6) or SDK for newer versions of Proficy Historian.

Use Cases

Facilities with established Proficy historians can benefit from adding dataPARC for visualization, calculations, reporting, alarms and more. Aggregates can be calculated within dataPARC or read from the historian.

Aveva Historian (previously WonderWare)

Aveva Historian (WonderWare) data can be read by a special setup of the dataPARC SQL source type.

Use Cases

Facilities with established Aveva historians (WonderWare) can benefit from adding dataPARC for visualization, calculations, reporting, alarms and more.

SAP (custom configuration)

Business and/or accounting data can be read from SAP, typically via SQL queries. Requires some customization for each application.

Use Cases

SAP systems can provide material inventory or usage, cost, production or other data to dataPARC to enable inclusion in visualization, reporting, etc. alongside process and lab data.

Excel

dataPARC reads timeseries data stored in an MS Excel spreadsheet. Data is read on an ad-hoc basis, updating only when the tag’s dataPARC display is initially loaded or modified.

Use Cases

Facilities with archived historical data, Lab or other manual-entry data stored in Excel spreadsheets can connect to these spreadsheets via the Tag Browser. This method is not intended for large quantities of data or long histories due to Excel file size and load speed limitations.