Industrial App Store

The Industrial App Store from Intelligent Plant is built on an architecture that enables cloud-based applications and services to interact with on-site Process Data Historians and Alarm & Event Logs. Use the Industrial App Store Connector to introduce plant data to your flows.

This connector is available in the following products and regions:

Industrial App Store Power Automate connector

Intelligent Plant developed the Industrial App Store which enables interaction with all the different historian data through a unified API. At the start of May 2020 Intelligent Plant released an official, Microsoft certified Industrial App Store connector for Power Automate. No more hefty SQL queries or Excel document interrogations with no easy real-time update option or complicated architecture solutions, simply install Industrial App Store connect and out of the box you will be able to connect to Aspentech IP.21, OSIsoft PI, Honeywell Dynamo, OPC DA & HDA, Siemens and many more. This allows our customers to bring data from various sources into Microsoft Automate flows to deliver insights that weren’t possible before. Real-time updates prompt money-saving decisions by engineers that also increase plant safety and efficiency. More information can be found here.

Prerequisites

• Register with the Industrial App store simply by logging in using your Linked In, Google or Microsoft account. Microsoft Entra ID sync is also supported which will enable you to log in using your work credentials.
• Demo data sources are there for you to play around with but if you want to connect to your historian data simply install App Store Connect, connect to your data using one out of the box data source driver and you're ready to go!

How to get credentials

Simply log in using your Linked In, Google or Microsoft account. Microsoft Entra ID sync is also supported which will enable you to log in using your work credentials.

Getting started with your connector

Simply add Industrial App Store as an action in your flow, specify one of the queries, enter parameters e.g. Tagname, start, end times and thats it! An example of data retrieval:

1. Start Power Automate
   Navigate to Microsoft Power Autoamte. Log in if required.
2. Create new Flow
   Hit :heavy_plus_sign: Create on the left hand side menu and choose an Instant Flow or a Scheduled Flow and confirm your selection.

3. Sign in
   Sign in using your credentials.

NOTE: you'll only need to do this once per flow. The same connection credentials can be re-used in other flows

4. Fill in parameters
   Fill in the required parameters with the following values:

The historical data returned to Power Automate describes the instrument values using the JSON file format. An example data set is shown below:

{
    "Edge Historian (LDT-INTELPLANT)": {
        "TIC001-HI": {
            "TagName": "TIC001-HI",
            "DisplayType": "TrailingEdge",
            "Values": [
                {
                    "IsNumeric": true,
                    "TagName": "TIC001-HI",
                    "UtcSampleTime": "2020-09-08T04:20:40Z",
                    "NumericValue": 13.89999,
                    "TextValue": "13.89999",
                    "Status": "Good",
                    "Unit": "degC",
                    "Notes": null,
                    "Error": null,
                    "HasError": false
                },
                {
                    "IsNumeric": true,
                    "TagName": "TIC001-HI",
                    "UtcSampleTime": "2020-09-09T04:20:40Z",
                    "NumericValue": 13.89999,
                    "TextValue": "13.89999",
                    "Status": "Good",
                    "Unit": "degC",
                    "Notes": null,
                    "Error": null,
                    "HasError": false
                },
				// -- remaining values removed for brevity --
            ]
        }
    }
}

The data is indexed by data source name (Edge Historian (LDT-INTELPLANT)) and then tag name (TIC001-HI). The entry for each tag contains the following fields:

• TagName - the display name of the tag.
• DisplayType - provides a hint describing how lines between individual values should be drawn when visualizing the data on a chart.
• Values - a list of tag values.

Each entry in the Values collection describes a single value for the tag at a specific point in time. Although there are several fields defined on each value, the fields that we are most interested in are:

• UtcSampleTime - the UTC timestamp for the sample, specified in ISO 8601 format.
• NumericValue - the numerical value recorded by the instrument.
• Status - the quality status associated with the value (Good, Bad, or Uncertain). The status will generally be Good unless the physical instrument has been diagnosed with a fault.
• Unit - the unit of measure for the value.

And that's it, you have historical data for futher processing. From here you can issue notifications, compile rpeorts, kick off procedures, etc.

Known issues and limitations

We are working on better schema definition so the returned data set is easier to navigate.

Common errors and remedies

Make sure you are authorised to access the data source. Either contact the person who configured your App Store Connect or Intelligent Plant ([email protected]).

FAQ

Please refer to this article which dives into more detail of the whole set up. Do not hesitate to contact Intelligent Plant for more information or if you have any questions at [email protected]

Throttling Limits

Actions

Get Data Sources

Get Tags

Read Aggregated Values

Read Plot Values

Read Raw Values

Read Snapshot Value

Definitions

HistoricalDataQueryResponsev2