Issues to be solved
The requirements of this scenario are:
-
Two basic parameters that are collected periodically from each device:
-
energy consumption
-
power consumption
-
-
It is neccessary to incorporate the "point of meassure" concept. This represents the physical location where meassures are taken. In this situation, the device meter can be changed (due to a maintenance issue or other) but the new measures need to be associated to the same measurement point.
Addressing implementation
The design using the OpenGate platform is showed in the next figure:
In this case it will be implemented using:
-
Two datastreams of information
-
electricity.consumption
-
electricity.power
-
-
The device will be associated to the smart meter using as device identifier the unique number of the meter
-
The feed resource is used to:
-
To identify the "point of measure"
-
To group around it the measures of each datastream but taken from different devices as a same collection of datapoints
-
To group all the datastreams of the different sensor types
-
-
The measure-device association can be traced because for the collection of datapoints of a same datastream
Steps for build
Previously it is recommended to take a look of the section getting started
Step 1: Provision Device into the platform
You can use for example next identifier:
my_meter_1
|
There is not necessary to provision the feed. |
Step 2: Data Collection from device
The device must use South API to inject meassures into the platform attending to the already defined datastream templates for electricity AMR datamodel
Step 3: Data Query to the platform
The backoffice application must use North API to retrieve meassures stored into the platform using device identifier and feed identifier (point of meassure) as part of the filter