Difference between revisions of "EPC (Electronic product code)"
From AMTech WikiDocs
Line 1: | Line 1: | ||
Support for EPC decoding at edge level allowing to use epc components for observation enticements leveraging [[Sensor%27s_network#Placeholders_substitution | Placeholders substitution]] | Support for EPC decoding at edge level allowing to use epc components for observation enticements leveraging [[Sensor%27s_network#Placeholders_substitution | Placeholders substitution]] | ||
*Support the following aggregation functions using EPC decoded components | *Support the following aggregation functions using EPC decoded components | ||
− | + | **Count | |
− | + | **Average | |
− | + | **Sum | |
− | + | **Percentage | |
− | + | **Rest | |
*Above functions can be configured with the following criteria | *Above functions can be configured with the following criteria | ||
**percentage changed | **percentage changed | ||
Line 16: | Line 16: | ||
**lost and new | **lost and new | ||
The above configuration can be set at thing instance level for with supported property epcAggregation | The above configuration can be set at thing instance level for with supported property epcAggregation | ||
+ | [[File:EpcAggregation|thumbnail|EPC Aggregation configuration]] |
Revision as of 12:07, 29 August 2017
Support for EPC decoding at edge level allowing to use epc components for observation enticements leveraging Placeholders substitution
- Support the following aggregation functions using EPC decoded components
- Count
- Average
- Sum
- Percentage
- Rest
- Above functions can be configured with the following criteria
- percentage changed
- value changed
- less than"
- greater than
- And the analysis can be triggered by one of the following smoothing criteria
- lost
- new
- lost and new
The above configuration can be set at thing instance level for with supported property epcAggregation