overview
Aggregated data is data (report data) aggregated by Daily/Monthly/Yearly Report units. Data stores can be either CSV files or databases (ODBC).
If you use a summary action, make sure to configure it so that your data is aggregated.
Also, if you want to import and display data collected in an external system via Historical data server, the Daily/Monthly/Yearly Report data must be collected as a separate file.
The specifications of the aggregation data that can be handled by the energy management function are explained below.
|
How to create a daily report using summary actions is described in "Daily Reports". |
|
How to obtain data using Historical data server is described in "Using Historical data server". |
Daily report data format
Daily report summary data is summary data consisting of one line per hour, and 24 lines per file (24 hours).
When aggregating usage such as electricity or gas, each row must contain the accumulated value in one-hour units (incremental value within one hour). When displaying measured values such as outdoor temperature and outdoor humidity on a graph, the aggregated value in one-hour units must be included in the field. Possible methods for aggregating measured values include maximum value, average value, start value, and final value for one hour. Be sure to perform appropriate aggregation according to the requirements of the monitoring system you are building.
Regarding the first header line, we can support either format with or without a header.
DATETIME |
U01_F01_T000 |
U01_F01_T001 |
... |
2010/4/10 00:00:00 |
23 |
100 |
... |
2010/4/10 00:01:00 |
44 |
120 |
... |
... |
... |
... |
... |
2010/4/10 00:23:00 |
16 |
115 |
... |
File name (example):
DAY_20170117.csv...The file name will end with 8 digits (yyyymmdd) for the date. One file per day, etc.
|
When aggregating measured values such as outdoor temperature and outdoor humidity in the aggregate data, you need to consider what aggregation method you want to use to display the data. Common aggregation methods include maximum, minimum, average, and start value, but you should select the most appropriate aggregation method for the characteristics of the measured values you want to display in the graph (for example, if you want to know the peak current measured value within a period, you should use "maximum"; if you want to record the average temperature, you should use "average"). |
Monthly report data format
Monthly report summary data consists of one line per day, with a maximum of 31 lines per file (for one month).
When aggregating power usage, etc., each row must contain the total value for one day. When displaying measurements such as outdoor temperature and humidity on a graph, the aggregated value for one day must be included in the field.
Regarding the first header line, we can support either format with or without a header.
DATETIME |
U01_F01_T000 |
U01_F01_T001 |
... |
2010/4/1 00:00:00 |
600 |
2400 |
... |
2010/4/2 00:00:00 |
610 |
2410 |
... |
... |
... |
... |
... |
2010/4/30 00:00:00 |
591 |
2394 |
... |
File name (example):
MONTH_201701.csv...The six-digit year and month (yyyymm) is added to the end of the file name. One file per month, etc.
Format of annual report data
The annual report summary data consists of one line per month, and 12 lines per file (for one year).
When aggregating power usage, etc., each row must contain the total value for one month. When displaying measurements such as outdoor temperature and humidity on a graph, the fields must contain the aggregated values for one month.
Regarding the first header line, we can support either format with or without a header.
DATETIME |
U01_F01_T000 |
U01_F01_T001 |
... |
2010/1/1 00:00:00 |
600 |
2400 |
... |
2010/2/1 00:00:00 |
610 |
2410 |
... |
... |
... |
... |
... |
2010/12/1 00:00:00 |
591 |
2394 |
... |
File name (example):
YEAR_2017.csv...The four-digit year (yyyy) is added to the end of the file name. One file per year, etc.
Data conditions for day and night aggregation
On the energy management screen, it is possible to register separate conversion coefficients for the day coefficient and night coefficient, allowing you to tally and convert daytime and nighttime usage amounts separately. However, since the energy management screen itself does not perform daily report tallying, the daytime columns and nighttime columns must be tallied separately at the tallying process stage by the Panel Server function (summary action) that actually performs daily report tallying or an external application.
Example of data format for day and night aggregation (7:00AM to 18:00PM is considered daytime)
Date and time columns |
All Count Columns 1 |
Daytime tally column 1 |
Night tally column 1 |
All Count Columns 2 |
Daytime tally column 2 |
Night tally column 2 |
... |
2017/4/26 00：00：00 |
6 |
0 |
6 |
5 |
0 |
5 |
... |
2017/4/26 01：00：00 |
15 |
0 |
15 |
4 |
0 |
4 |
... |
2017/4/26 02：00：00 |
1 |
0 |
1 |
8 |
0 |
8 |
... |
2017/4/26 03：00：00 |
12 |
0 |
12 |
12 |
0 |
12 |
... |
2017/4/26 04：00：00 |
9 |
0 |
9 |
4 |
0 |
4 |
... |
2017/4/26 05：00：00 |
15 |
0 |
15 |
5 |
0 |
5 |
... |
2017/4/26 06：00：00 |
100 |
0 |
100 |
15 |
0 |
15 |
... |
2017/4/26 07：00：00 |
600 |
600 |
0 |
46 |
46 |
0 |
... |
2017/4/26 08：00：00 |
610 |
610 |
0 |
90 |
90 |
0 |
... |
2017/4/26 09：00：00 |
612 |
612 |
0 |
97 |
97 |
0 |
... |
2017/4/26 10：00：00 |
591 |
591 |
0 |
46 |
46 |
0 |
... |
2017/4/26 11：00：00 |
601 |
601 |
0 |
58 |
58 |
0 |
... |
2017/4/26 12：00：00 |
712 |
712 |
0 |
69 |
69 |
0 |
... |
2017/4/26 13：00：00 |
723 |
723 |
0 |
46 |
46 |
0 |
... |
2017/4/26 14：00：00 |
680 |
680 |
0 |
78 |
78 |
0 |
... |
2017/4/26 15：00：00 |
602 |
602 |
0 |
150 |
150 |
0 |
... |
2017/4/26 16：00：00 |
590 |
590 |
0 |
106 |
106 |
0 |
... |
2017/4/26 17：00：00 |
570 |
570 |
0 |
87 |
87 |
0 |
... |
2017/4/26 18：00：00 |
690 |
690 |
0 |
68 |
68 |
0 |
... |
2017/4/26 19：00：00 |
120 |
0 |
120 |
4 |
0 |
4 |
... |
2017/4/26 20：00：00 |
10 |
0 |
10 |
5 |
0 |
5 |
... |
2017/4/26 21：00：00 |
12 |
0 |
12 |
6 |
0 |
6 |
... |
2017/4/26 22：00：00 |
23 |
0 |
23 |
7 |
0 |
7 |
... |
2010/4/26 23：00：00 |
5 |
0 |
5 |
3 |
0 |
3 |
... |
|
The above table is an example of the format when day and night totals are performed using the summary action. Note that in the above example, a total column for data of all time periods is provided as an "all total column" in addition to the "day total" and "night total", but the "all total column" is not essential as a function of the energy management screen. |
|
If you separate the tally between day and night, you will also need to register point groups separately: a point group for day tally and a point group for night tally. |