Skip to Content

Changes for page 6. Flexible Reports Guide

Last modified by Iaroslav Platonov on 2026/06/08 15:20
From version 4.3
edited by Lana
on 2025/12/10 22:44
Change comment: There is no comment for this version
To version 9.1
edited by Lana
on 2025/12/10 22:50
Change comment: Uploaded new attachment "Screenshot 2025-12-10 at 19.50.54.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -92,9 +92,9 @@
92 92  * rr_imp - readings of R+
93 93  * rr_exp - readings of R-
94 94  
95 - The specified channels can be renamed to their decryptions in the config.toml configuration file of the sed_channels service.
95 +The specified channels can be renamed to their decryptions in the config.toml configuration file of the sed_channels service.
96 96  
97 -When referring to **energy** measurements instead of **electrical**, the channels are encoded with numbers. For example, it would be recorded as **en-dev-30-15-3m**, which represents 3-minute data for channel with id = 15 in the device with id = 30.
97 +When referring to **energy** measurements instead of **electrical**, the channels are encoded with numbers. For example, it would be recorded as **en-dev-30-15-3m**, which represents 3-minute data for the channel with id = 15 in the device with id = 30.
98 98  
99 99  Possible interval options include: **1m** for minute data, **3m** for 3-minute data, **15m** for 15-minute data, **20m** for 20-minute data, **30m** for 30-minute data, **1h** for hourly data, **1d** for daily data, **1m** for monthly data, as well as other intervals that the device may return.
100 100  
... ... @@ -104,10 +104,85 @@
104 104  
105 105  The data request form for flexible period reports is similar to reports for a day, month, or year. However, in the date block at the beginning of the query, instead of a specific date (**y-m-d**), the start and end of the report period are used as **#begin-#end**. For example, the query **#begin-#end:h10-m00:el-dev-30-ea_imp-3m:sum** means that the total active energy value (reception) is requested for the user-defined period from 10:00 a.m. at the beginning of the period (**#begin**) to 10:00 a.m. at the end of the period (**#end**) from a device with ID 30.
106 106  
107 -Queries for flexible reports for a period can be generated indicating only the beginning of the period (**#begin**) or only the end (**#end**). In this case, CENTO will fill the cell with the value only for the specified time, ignoring the formula at the end of the query (if there is one).
107 +Queries for flexible reports for a period can be generated, indicating only the beginning of the period (**#begin**) or only the end (**#end**). In this case, CENTO will fill the cell with the value only for the specified time, ignoring the formula at the end of the query (if there is one).
108 108  
109 109  Flexible period reports also allow time offsets in queries, but **only by day**. For example, **#end+2d** or **#begin-1d**.
110 110  
111 -The formulas described above can be replaced with formulas with **#date**. Using formulas with **#date** to expand the query toolkit. The comparison of queries is performed in Table 2.3. Additional queries are described in lines 13 - 16 in the specified table
111 +The formulas described above can be replaced with formulas with **#date**. Using formulas with **#date** to expand the query toolkit. The comparison of queries is performed in Table 2.3. Additional queries are described in lines 13 - 16 in the specified table.
112 112  
113 -
113 +Table 2.3. Comparative table of y-m-d and #date formulas
114 +
115 +|**№**|(% style="width:161px" %)**Format with y-m-d**|(% style="width:134px" %)**Format with #date**|(% style="width:198px" %)**Description**|(% style="width:106px" %)**Type of report in which the formula is applied**
116 +|1|(% style="width:161px" %)y-m-d3:*:el-dev-201-ea_imp-30m:sum|(% style="width:134px" %)#date-d3:d:dev-201-ea_imp:sum|(% style="width:198px" %)Sum of all half-hours on the 3rd day of the month|(% style="width:106px" %)monthly, daily
117 +|2|(% style="width:161px" %)y-m-d1:h00-m30:el-dev-201-ea_imp-30m:sum|(% style="width:134px" %)#date-d1-h00-m30:*:dev-201-ea_imp|(% style="width:198px" %)Value of the half-hour is 00-30 on the first day|(% style="width:106px" %)monthly, daily
118 +|3|(% style="width:161px" %)y-m-d+1:h00-m30:el-dev-201-ea_imp-30m|(% style="width:134px" %)#date+1-h00-m30:*:dev-201-ea_imp|(% style="width:198px" %)Value of the half-hour is 00-30 of the day following the selected one|(% style="width:106px" %)daytime
119 +|4|(% style="width:161px" %)y-m-d+10:h00-m30:el-bg-42-30m|(% style="width:134px" %)#date+10-h00-m30:*:bg-42|(% style="width:198px" %)Value of the half-hour is 00-30 per day +10; checking the operation of the electro-billing group|(% style="width:106px" %)daytime
120 +|5|(% style="width:161px" %)y-m-d-1:h00-m30:el-dev-201-ea_imp-30m|(% style="width:134px" %)#date-1-h00-m30:*:dev-201-ea_imp|(% style="width:198px" %)Value of the 00-30 half-hour per day is -1|(% style="width:106px" %)daytime
121 +|6|(% style="width:161px" %)y-m-d1-1:h01-m00:el-dev-201-ea_imp-30m|(% style="width:134px" %)#date-d1-1-h01-m00:*:dev-201-ea_imp|(% style="width:198px" %)Value of the 01-00 half-hour for the last day of the previous month|(% style="width:106px" %)monthly, daily
122 +|7|(% style="width:161px" %)y-m-d1-2:h00-m30:el-dev-201-ea_imp-30m|(% style="width:134px" %)#date-d1-2-h00-m30:*:dev-201-ea_imp|(% style="width:198px" %)Value of the half-hour is 00-30 for the penultimate day of the previous month|(% style="width:106px" %)monthly, daily
123 +|8|(% style="width:161px" %)y-m-d:*:el-dev-201-ea_imp-30m:sum|(% style="width:134px" %)#date:d:dev-201-ea_imp:sum|(% style="width:198px" %)Sum of all half-hours for the selected day|(% style="width:106px" %)daytime
124 +|9|(% style="width:161px" %)y-m:*:el-dev-201-ea_imp-30m:sum|(% style="width:134px" %)#date:m:dev-201-ea_imp:sum|(% style="width:198px" %)Sum of all half-hours for the selected month|(% style="width:106px" %)annual, monthly, daily
125 +|10|(% style="width:161px" %)y:*:el-dev-201-ea_imp-30m:max|(% style="width:134px" %)#date:y:dev-201-ea_imp:max|(% style="width:198px" %)The maximum half-hour for a selected year|(% style="width:106px" %)annual, monthly, daily
126 +|11|(% style="width:161px" %)y-m-1m:*:el-dev-201-ea_imp-30m:min|(% style="width:134px" %)#date-1m:m:dev-201-ea_imp:min|(% style="width:198px" %)Minimum half-hour for the previous month|(% style="width:106px" %)annual, monthly
127 +|12|(% style="width:161px" %)y-m1:*:en-dev-220-1021-1h:mean|(% style="width:134px" %)#date-m2:m:ch-1021-1h:mean|(% style="width:198px" %)Output the average of all hours from channel 1021 at device 220 for February of the year selected by the user|(% style="width:106px" %)annual, monthly, daily
128 +| |(% style="width:161px" %) |(% style="width:134px" %)**New functions available only with #date**|(% style="width:198px" %) |(% style="width:106px" %)
129 +|13|(% style="width:161px" %) |(% style="width:134px" %)#date-h08-#date-h17:*:dev-201-ea_imp:sum|(% style="width:198px" %)Sum of energy as of the report date from 8 a.m. to 5 p.m.|(% style="width:106px" %)daytime
130 +|14|(% style="width:161px" %) |(% style="width:134px" %)#date+1-h08-#date+1-h17:*:dev-201-ea_imp:sum|(% style="width:198px" %)Sum of energy for the day following the reporting day from 8 a.m. to 5 p.m.|(% style="width:106px" %)daytime
131 +|15|(% style="width:161px" %) |(% style="width:134px" %)#date-d1-h08-#date+1-h17:*:dev-201-ea_imp:sum|(% style="width:198px" %)Sum of energy from the first day of the month at 8 a.m. to the day following the reporting day at 5 p.m.|(% style="width:106px" %)daytime
132 +|16|(% style="width:161px" %) |(% style="width:134px" %)#date-d1-1-h08-#date+1-h17:*:dev-201-ea_imp:sum|(% style="width:198px" %)Sum of energy from the last day of the previous month, 8 a. m. to the day following the reporting one, up to 5 p.m.|(% style="width:106px" %)daytime
133 +
134 +== 2.4. Query examples ==
135 +
136 +**y2019-m-d:h10:el-dev-30-ea_imp-3m:sum-k0.001**
137 +
138 +The is data for 2019, the month and day values from the date associated with the report, the time from 10:00 a.m. to 11:00 a.m., data from the electricity table (el) for three minutes (3m), data on the device with id = 30, for the ea_imp channel, apply the sum aggregating function with the coefficient 0.001 (result is in megawatts).
139 +
140 +**y-m1:*:en-dev-220-1021-1d:sum**
141 +
142 +The data is for the 1st month of the year from the date associated with the report. The data is taken from the energy resources table for daily records for device 220 and channel 1021. The day is skipped here, so there will be a selection based on the range of all days from the 1st to the 2nd month. If, for example, the year is 2019, then the range is: from 2019-01-01 to 2019-02-01 excluding the 1st day of the 2nd month.
143 +
144 +**y-m+1-d1:h00-m00:el-dev-1202-ra_imp-30m**
145 +
146 +The data is for 00:00 on the 1st of the month following the date associated with the report. This request outputs electricity readings for a device with id = 1202. You can also write **m+2**, **m+3, y+5**, etc.
147 +
148 +**y-m-d1-1:h10-m00:el-dev-1202-ra_imp-30m**
149 +
150 +The data is for10:00 a.m. on the last day of the previous month of the device with Id 1202, the ra_imp channel from the database of 30 minutes.
151 +
152 +**#begin-#end:h00-m00:el-dev-46-ea_imp-3m:sum**
153 +
154 +The data is for the period from 00:00 of the date **#begin **to 00:00 of the date **#end**. The data is downloaded using the active received energy from the device with ID 46. The value is given as the sum of the three-minute values of the specified interval.
155 +
156 +**#begin:h06-m30:el-dev-58-ea_exp-30m**
157 +
158 +The data of the half-hour starting at 6:30 a.m., the date indicated at the beginning of the requested period. The data is on the output of active energy from a device with ID 58.
159 +
160 +**#end+2d:h02-m00:el-bg-22-30m**
161 +
162 +The data of the half-hour starting at 2:00 a.m., the date running 2 days after the end of the period requested by the user. The data is requested for the billing group with ID 22 according to the readings of the received active energy.
163 +
164 +== 2.5. Output of information on devices to the report. Device codes and tags. ==
165 +
166 +The request **#dev.201.IP** displays the IP address of the device with id = 201201 from the configuration in the report. Instead of the device ID, the device code can be specified.
167 +
168 +**#dev.201.Name** displays the device name with id = 201201 from the configuration in the report. Instead of the device ID, the device code can be specified.
169 +
170 +**#dev.201.VendorNumber** displays the serial number of the device with id = 201 from the configuration in the report. Instead of the device ID, the device code can be specified.
171 +
172 +The serial number of the device can also be taken from the tag if the device can output its number according to any protocol. For example, the SATEC device can be queried via Modbus, and the serial number can be retrieved from the **ti11001** tag. To display this tag in the report, write the formula **y-m-d:*:ti11001 **where **ti11001** can be replaced with the tag code. In the same way, add any tags from the configuration to flexible reports.
173 +
174 +In query formulas, device IDs can be replaced with device codes. Unlike the id, the code can contain Latin letters, which allows it to encode a lot of useful information. For example, the code P22S1Y8 may mean that the device collects data on PS22 in the first bus section in cell 8. To write the code in the request, add the channel to it, for example, Energy A+, which is encrypted as **ea_imp** by default.
175 +
176 +Thus, the formula **y-m-d1:*:el-dev-201-ea_imp-30m:sum** can be replaced by the formula **y-m-d1:*:E123457ea_imp:sum**. A similar logic applies to all the formulas described above.
177 +
178 += 3. MANAGING REPORT TEMPLATES =
179 +
180 +Flexible reports are managed in the Flexible Reports window accessible using the **Reports menu: Reports -> Flexible Reports**.
181 +
182 +A template generated in accordance with the query language specified in Section 1 is uploaded to the Flexible Reports page (see Figure 3.1) by clicking the (Create Template) button [[image:Screenshot 2025-12-10 at 19.48.07.png||height="27" width="29"]] in the upper-right corner of the template list.
183 +
184 +[[image:Screenshot 2025-12-10 at 19.48.44.png]]
185 +
186 +Figure 3.1 – Flexible Report Template Management window
187 +
188 +After clicking the button [[image:Screenshot 2025-12-10 at 19.48.07.png||height="27" width="29"]] (see Figure 3.1), a download dialog box will open. Enter the template name, type, object, and category in this dialog box. Then, select the template file (Excel file), configure auto generation if needed, select a network resource and/or email address for saving automatically generated reports (see Figure 3.2), and click the button [[image:Screenshot 2025-12-10 at 19.49.45.png||height="23" width="46"]] to complete.
Screenshot 2025-12-10 at 19.48.07.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +2.5 KB
Content
Screenshot 2025-12-10 at 19.48.44.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +128.9 KB
Content
Screenshot 2025-12-10 at 19.49.45.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +2.8 KB
Content
Screenshot 2025-12-10 at 19.50.16.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +69.1 KB
Content
Screenshot 2025-12-10 at 19.50.54.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Lana
Size
... ... @@ -1,0 +1,1 @@
1 +1.6 KB
Content