Support automatic ingestion of VOLTTRON data

[timothykang]

End goal:

• OpenEIS VOLTTRON historian agent pushes data to OpenEIS instance as specified in agent's configuration
• All pushed data is in a single OpenEIS dataset (that can grow over time) and available for analysis

One way to achieve this might be to have a special dataset type that provides an endpoint to which external clients (i.e. the historian) can POST timestamp +topic + value.

TBD:

• Will the data set require a sensor map?
  • If so, what if a new sensor is pushed from VOLTTRON?
  • If not, where will sensor metadata (e.g. units) come from?

[fstshrk]

For OpenEIS apps to run, we need to be able to map the sensor data to the
common OpenEIS schema. This can be accomplished via a data map.
Sensor units should come from the metadata associated with the driver on
the VOLTTRON instance. You may want to check out the csv files used to
configure the driver.

On Wed, Apr 22, 2015 at 9:40 AM, timothykang [email protected]
wrote:

End goal:

• OpenEIS VOLTTRON historian agent pushes data to OpenEIS instance as
  specified in agent's configuration
• All pushed data is in a single OpenEIS dataset (that can grow over
  time) and available for analysis

One way to achieve this might be to have a special dataset type that
provides an endpoint to which external clients (i.e. the historian) can
POST timestamp +topic + value.

TBD:

• Will the data set require a sensor map?
  • If so, what if a new sensor is pushed from VOLTTRON?
  • If not, where will sensor metadata (e.g. units) come from?

—
Reply to this email directly or view it on GitHub
#11.