How It Works

To dynamically create asset properties and link them to external data, you'll need to go through a couple of steps.

In your site folder (ie. /opt/web/sites/default on Linux servers), create a writable folder called 'dynamiccontent'.

Make sure you have setup the data sources you want to read information from (if you are going to bind these properties to external data).

You'll need to know the data source name and address format before-hand.

Next, create a JSON file describing the properties you want to create on your assets.

For example…

{
   "style": "property", 
   "type": "measurement", 
   "default": "0|PSI|0|100", 
   "name": "Pressure - Air PSI", 
   "attachto": 171, 
   "livebind": "DEEP>Objects/Air Pressure Sensor/Pressure - Air PSI",
   "histbind": "DEEP>Air_Pressure_Sensor_Pressure_Air_PSI"
}

Above is an example of the file generated by a modelling system. It's converting metric variables to imperial ones.

Describes the type of dynamic content. At the present time, 'property' is the only supported option.

The type of property to be created. measurement, status, enum and text are the most common types.

The default value to write. This is in the same format that the properties are exported in - for example for a measurement, the format is <value>|<min>|<max>|<units>|<precision>.

The name of the property

The ID of the ARDI asset to attach this property to.

The live data address for this item, in the format [sourcename]>[address].

In the example above, DEEP uses OPC-UA - this is the full OPC-UA address of the data point.

The historical address for this item, in the format [sourcename]>[address].

In the example above, DEEP uses Prometheus. This is the full Prometheus point-name for the data point.