Last modified by Iaroslav Platonov on 2026/06/08 10:08

From version 6.5
edited by Lana
on 2025/12/03 21:54
Change comment: There is no comment for this version
To version 5.4
edited by Lana
on 2025/12/03 21:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -52,426 +52,4 @@
52 52  
53 53  When metrologically significant files change, their checksum changes. Information about checksums is displayed on the "Services" tab of the "System Information" page. Checksums are calculated by **the sed_system** service using the MD5 algorithm. To display up-to-date information about checksums, click the "Update Information" button in the upper-right corner of the System Information page (System - Settings) - see Fig.3.1.
54 54  
55 -[[image:Screenshot 2025-12-03 at 18.47.38.png]]
56 -
57 -Fig. 3.1 – Updating information on checksums of metrologically significant files
58 -
59 -**Data processing services**
60 -
61 -The processing services receive the data coming from the message broker, process it, and write it to the database.
62 -
63 -The data processing services contain a metrologically significant part the binary file "**sed_metrology_YYY.bin**" where YYY is the service identification name. Binary files "**sed_metrology_YYY.bin" **contains information about algorithms and mechanisms for calculating measured values and are used by the processing modules to directly perform their functions.
64 -
65 -The Pre-calculated Parameter Calculation Service (sed_calc_arch service) additionally has a **sed_metrology_formulas.bin** file. The sed_metrology_formulas.bin file contains custom formulas for pre-calculations that have the "metrologically significant" attribute.
66 -
67 -When metrologically significant files or formulas with a metrological significance attribute change, the checksum of the file changes. Information about checksums is displayed on the "Services" tab of the "System Information" page. Checksums are calculated by **the sed_system service **using the MD5 algorithm.
68 -
69 -**Auxiliary Services**
70 -
71 -Auxiliary services are designed to ensure that the main CENTO services perform their functions.
72 -
73 -The list of CENTO services and their brief description is given in Table 1. The composition of CENTO services for a particular system depends on the functions performed and is displayed on the "System Information" tab.
74 -
75 -Table 1 – CENTO software components
76 -
77 -|(% style="text-align:center" %)**№**|(% style="text-align:center; width:214px" %)**Service Name**|(% style="text-align:center; width:676px" %)**Function**|(% style="text-align:center; width:358px" %)**Metrologically significant part**
78 -|(% colspan="4" style="text-align:center" %)**Data collection and transmission services**
79 -|(((
80 -~1.
81 -)))|(% style="width:214px" %)sed_bus_dispatcher|(% style="width:676px" %)Sequential Device Polling Management Service|(% style="width:358px" %)
82 -|(((
83 -2.
84 -)))|(% style="width:214px" %)sed_xml_reader|(% style="width:676px" %)Service for processing received XML files 80020|(% style="width:358px" %)
85 -|(((
86 -3.
87 -)))|(% style="width:214px" %)sed_xml_send|(% style="width:676px" %)XML file transfer Service 80020|(% style="width:358px" %)
88 -|(((
89 -4.
90 -)))|(% style="width:214px" %)sed_archive_webapi|(% style="width:676px" %)Implementation of the web API for transmitting archived data according to the CENTO documentation|(% style="width:358px" %)
91 -|(((
92 -5.
93 -)))|(% style="width:214px" %)sed_s2s_configuration|(% style="width:676px" %)Configuration transmission service between CENTO servers|(% style="width:358px" %)
94 -|(% colspan="4" style="text-align:center" %)**Data collection and transmission services using standard protocols**
95 -|6.|(% style="width:214px" %)sed_modbus_rtd|(% style="width:676px" %)A service for reading real-time data from devices using Modbus protocol (Modbus TCP and Modbus RTU over TCP)|(% style="width:358px" %)sed_metrology_001.bin
96 -|7.|(% style="width:214px" %)sed_modbus_rtd_send|(% style="width:676px" %)A service for sending real-time data to third-party devices using the Modbus TCP protocol|(% style="width:358px" %)
97 -|8.|(% style="width:214px" %)sed_modbus_sync|(% style="width:676px" %)A device time synchronization service using Modbus protocol (Modbus TCP and Modbus RTU over TCP)|(% style="width:358px" %)
98 -|9.|(% style="width:214px" %)sed_snmp_rtd|(% style="width:676px" %)A service for reading real-time data from devices using the SNMP (v1, v2c, v3), ICMP protocols|(% style="width:358px" %)
99 -|10.|(% style="width:214px" %)sed_iec103_waveform|(% style="width:676px" %)A service for reading waveform files from devices using the IEC protocol-60870-5-103|(% style="width:358px" %)sed_metrology_393.bin
100 -|11.|(% style="width:214px" %)sed_iec104_rtd|(% style="width:676px" %)A service for reading real-time data from devices using the IEC 60870-5-104 protocol|(% style="width:358px" %)sed_metrology_011.bin
101 -|12.|(% style="width:214px" %)sed_iec104_rtd_send|(% style="width:676px" %)A service for sending real-time data to third-party devices using the IEC 60870-5-104 protocol|(% style="width:358px" %)sed_metrology_012.bin
102 -|13.|(% style="width:214px" %)sed_opcda_rtd|(% style="width:676px" %)A service for receiving real-time data using the OPC DA protocol|(% style="width:358px" %)
103 -|14.|(% style="width:214px" %)sed_opcua_rtd|(% style="width:676px" %)A service for receiving real-time data using the OPC UA protocol|(% style="width:358px" %)
104 -|15.|(% style="width:214px" %)sed_opcua_arch|(% style="width:676px" %)A service for receiving archived data using the OPC UA protocol|(% style="width:358px" %)sed_metrology_402.bin
105 -|16.|(% style="width:214px" %)sed_opcua_server|(% style="width:676px" %)A service for transmitting data using the OPC UA protocol|(% style="width:358px" %)
106 -|17.|(% style="width:214px" %)sed_dnp3_rtd|(% style="width:676px" %)A service for reading real-time data from devices using the DNP3 protocol|(% style="width:358px" %)
107 -| |(% style="width:214px" %)sed_ftp_waveform|(% style="width:676px" %)A service for receiving waveform files via FTP protocol|(% style="width:358px" %)sed_metrology_380.bin
108 -| |(% style="width:214px" %)sed_iec61107_rtd|(% style="width:676px" %)A service for obtaining real-time data from devices using the IEC 62056-21 protocol|(% style="width:358px" %)sed_metrology_61107.bin
109 -| |(% style="width:214px" %)sed_iec61850_arch|(% style="width:676px" %)A service for receiving archived data from devices using the IEC 61850 protocol|(% style="width:358px" %)
110 -| |(% style="width:214px" %)sed_iec61850_rtd|(% style="width:676px" %)A service for receiving operational data from devices using the IEC 61850 protocol|(% style="width:358px" %)
111 -|(% colspan="4" %)**Proprietary protocol data collection and transmission services**
112 -|(((
113 -1.
114 -)))|(% style="width:214px" %)sed_satec_arch|(% style="width:676px" %)A service for reading archived data (metering and event logs) from SATEC devices|(% style="width:358px" %)sed_metrology_7_8.bin
115 -|(((
116 -1.
117 -)))|(% style="width:214px" %)sed_satec_pq_journal|(% style="width:676px" %)A service for obtaining event logs for monitoring the power quality from Satec devices|(% style="width:358px" %)sed_metrology_106.bin
118 -|(((
119 -1.
120 -)))|(% style="width:214px" %)sed_satec_pq_report|(% style="width:676px" %)A service for receiving reports on the power quality control from Satec devices|(% style="width:358px" %)sed_metrology_106.bin
121 -|(((
122 -1.
123 -)))|(% style="width:214px" %)sed_satec_waveforms|(% style="width:676px" %)A service for proofreading waveforms from SATEC devices using Modbus TCP and RTU over TCP protocols|(% style="width:358px" %)sed_metrology_108_109.bin
124 -|(((
125 -1.
126 -)))|(% style="width:214px" %)sed_iec103_rtd|(% style="width:676px" %)A service for reading real-time data from TOR 200 terminals according to the IEC protocol-60870-5-103|(% style="width:358px" %)sed_metrology_391.bin
127 -|(((
128 -1.
129 -)))|(% style="width:214px" %)sed_sepam_waveform|(% style="width:676px" %)A service for proofreading waveforms and time synchronization using the Modbus RTU over TCP protocol from Sepam devices|(% style="width:358px" %)sed_metrology_298_299.bin
130 -|(((
131 -1.
132 -)))|(% style="width:214px" %)sed_rtu_over_tcp_logikamp_rtd|(% style="width:676px" %)A service for reading real-time data from devices using the LogicaMP RTU over TCP protocol|(% style="width:358px" %)sed_metrology_121.bin
133 -|(((
134 -1.
135 -)))|(% style="width:214px" %)sed_rtu_over_tcp_logikamp_arch|(% style="width:676px" %)A service for reading archived data from devices using the LogicaMP RTU over TCP protocol|(% style="width:358px" %)sed_metrology_122.bin
136 -|(((
137 -1.
138 -)))|(% style="width:214px" %)sed_axis_video_journal|(% style="width:676px" %)An AXIS camera recording service|(% style="width:358px" %)sed_metrology_435.bin
139 -|(((
140 -1.
141 -)))|(% style="width:214px" %)sed_vzlyotmb_arch|(% style="width:676px" %)A service for reading archives and event logs of devices Vzlet TSRV-043, TSRV-027, IVK-TER|(% style="width:358px" %)sed_metrology_25_133.bin
142 -|(((
143 -1.
144 -)))|(% style="width:214px" %)sed_micom_waveforms|(% style="width:676px" %)A service for reading waveform files from Micom devices using Modbus RTU over TCP protocol|(% style="width:358px" %)sed_metrology_370.bin
145 -|(((
146 -1.
147 -)))|(% style="width:214px" %)sed_pulsar_arch|(% style="width:676px" %)A service for reading archives from Pulsar devices using the Modbus protocol|(% style="width:358px" %)sed_metrology_342.bin
148 -|(((
149 -1.
150 -)))|(% style="width:214px" %)sed_rtu_over_tcp_a1800_arch|(% style="width:676px" %)A service for receiving archived data from A1800 meters using the Modbus RTU over TCP protocol|(% style="width:358px" %)sed_metrology_232.bin
151 -|(((
152 -1.
153 -)))|(% style="width:214px" %)sed_rtu_over_tcp_a1800_rtd|(% style="width:676px" %)A service for receiving real-time data from A1800 meters using the Modbus RTU over TCP protocol|(% style="width:358px" %)sed_metrology_231.bin
154 -|(((
155 -1.
156 -)))|(% style="width:214px" %)sed_rtu_over_tcp_acron_arch|(% style="width:676px" %)A service for receiving archived data from Acron meters using the Modbus RTU over TCP protocol|(% style="width:358px" %)sed_metrology_142.bin
157 -|(((
158 -1.
159 -)))|(% style="width:214px" %)sed_rtu_over_tcp_acron_rtd|(% style="width:676px" %)A service for receiving real-time data from Acron meters using the Modbus RTU over TCP protocol|(% style="width:358px" %)sed_metrology_141.bin
160 -|(((
161 -1.
162 -)))|(% style="width:214px" %)sed_rtu_over_tcp_bmrz_waveform|(% style="width:676px" %)A service for reading waveform files from BMRZ terminals using the Modbus RTU over TCP protocol|(% style="width:358px" %)sed_metrology_110.bin
163 -|(((
164 -1.
165 -)))|(% style="width:214px" %)sed_rtu_over_tcp_bzp03_waveform|(% style="width:676px" %)A service for reading waveform files from BZP-03 terminals using Modbus RTU over TCP protocol|(% style="width:358px" %)
166 -|(((
167 -1.
168 -)))|(% style="width:214px" %)sed_rtu_over_tcp_kmp_rtd|(% style="width:676px" %)A service for polling Multitical 601 device using the KMP protocol|(% style="width:358px" %)sed_metrology_191.bin
169 -|(((
170 -1.
171 -)))|(% style="width:214px" %)sed_rtu_over_tcp_majac_arch|(% style="width:676px" %)A service for receiving archived data from devices using the Mayak protocol|(% style="width:358px" %)sed_metrology_152.bin
172 -|(((
173 -1.
174 -)))|(% style="width:214px" %)sed_rtu_over_tcp_mercury200_rtd|(% style="width:676px" %)A service for receiving real-time data from devices using the Mercury 200 protocol|(% style="width:358px" %)sed_metrology_251.bin
175 -|(((
176 -1.
177 -)))|(% style="width:214px" %)sed_rtu_over_tcp_mercury_arch|(% style="width:676px" %)A service for reading archives and event logs from Mercury-230 series devices using the Mercury-230 protocol|(% style="width:358px" %)sed_metrology_202.bin
178 -|(((
179 -1.
180 -)))|(% style="width:214px" %)sed_rtu_over_tcp_mercury_rtd|(% style="width:676px" %)A service for receiving real-time data from devices using the Mercury 230 protocol|(% style="width:358px" %)sed_metrology_201.bin
181 -|(((
182 -1.
183 -)))|(% style="width:214px" %)sed_rtu_over_tcp_photon_rtd|(% style="width:676px" %)A service for receiving real-time data from devices using the photon RTU over TCP protocol|(% style="width:358px" %)sed_metrology_221.bin
184 -|(((
185 -1.
186 -)))|(% style="width:214px" %)sed_rtu_over_tcp_ref542plus_waveform|(% style="width:676px" %)Proofreading of waveforms and time synchronization via Modbus RTU over TCP protocol from ABB REF 542plus devices|(% style="width:358px" %)
187 -|(((
188 -1.
189 -)))|(% style="width:214px" %)sed_rtu_over_tcp_set4tm_arch|(% style="width:676px" %)A service for polling SET-4TM, PSC meters’ archives|(% style="width:358px" %)sed_metrology_112.bin
190 -|(((
191 -1.
192 -)))|(% style="width:214px" %)sed_rtu_over_tcp_set4tm_rtd|(% style="width:676px" %)A service for receiving real-time data from devices using the SET-4TM rtu over tcp protocol|(% style="width:358px" %)sed_metrology_111.bin
193 -|(((
194 -1.
195 -)))|(% style="width:214px" %)sed_rtu_over_tcp_tem104_arch|(% style="width:676px" %)A service for receiving archived data from devices using the TEM104 protocol|(% style="width:358px" %)sed_metrology_162.bin
196 -|(((
197 -1.
198 -)))|(% style="width:214px" %)sed_rtu_over_tcp_tem104_rtd|(% style="width:676px" %)A service for receiving real-tume data from devices using the TEM104 protocol|(% style="width:358px" %)sed_metrology_161.bin
199 -|(((
200 -1.
201 -)))|(% style="width:214px" %)sed_rtu_over_tcp_vist_arch|(% style="width:676px" %)A service for receiving archived data from devices using the VIS.T protocol|(% style="width:358px" %)sed_metrology_172.bin
202 -|(((
203 -1.
204 -)))|(% style="width:214px" %)sed_rtu_over_tcp_vkt5_arch|(% style="width:676px" %)A service for receiving archived data from VKT-5 devices|(% style="width:358px" %)sed_metrology_312.bin
205 -|(((
206 -1.
207 -)))|(% style="width:214px" %)sed_rtu_over_tcp_vkt5_rtd|(% style="width:676px" %)A service for receiving real-time data from VKT-5 devices|(% style="width:358px" %)sed_metrology_311.bin
208 -|(((
209 -1.
210 -)))|(% style="width:214px" %)sed_vkt7_arch|(% style="width:676px" %)A service for receiving archived data from VKT-7 devices|(% style="width:358px" %)
211 -|(((
212 -1.
213 -)))|(% style="width:214px" %)sed_vkt7_rtd|(% style="width:676px" %)A service for receiving real-time data from VKT-7 devices|(% style="width:358px" %)
214 -|(((
215 -1.
216 -)))|(% style="width:214px" %)sed_rtu_over_tcp_vtd_arch|(% style="width:676px" %)A service for receiving archived data of VTD devices|(% style="width:358px" %)sed_metrology_182.bin
217 -|(((
218 -1.
219 -)))|(% style="width:214px" %)sed_rtu_over_tcp_vtd_rtd|(% style="width:676px" %)A service for receiving operational data from VTD devices|(% style="width:358px" %)sed_metrology_181.bin
220 -|(((
221 -1.
222 -)))|(% style="width:214px" %)sed_uvp_arch|(% style="width:676px" %)A service for poling Promavtomatika's archive for devices of the UVP series|(% style="width:358px" %)sed_metrology_352.bin
223 -|(((
224 -1.
225 -)))|(% style="width:214px" %)sed_ce_arch|(% style="width:676px" %)A service for receiving archived data from Energomera devices of the CE series according to the IEC61107 protocol|(% style="width:358px" %)sed_metrology_362.bin
226 -|(((
227 -1.
228 -)))|(% style="width:214px" %)sed_alpha_arch|(% style="width:676px" %)A service for receiving archived data from Alfa-3 devices manufactured by Alfamera|(% style="width:358px" %)sed_metrology_462_472.bin
229 -|(((
230 -1.
231 -)))|(% style="width:214px" %)sed_bug01_rtd|(% style="width:676px" %)A service for receiving archived data of BUG-01 devices|(% style="width:358px" %)sed_metrology_491.bin
232 -|(((
233 -1.
234 -)))|(% style="width:214px" %)sed_dymetic_arch|(% style="width:676px" %)A service for receiving archived data from Dimetik|(% style="width:358px" %)sed_metrology_552.bin
235 -|(((
236 -1.
237 -)))|(% style="width:214px" %)sed_irvis_arch|(% style="width:676px" %)A service for receiving archived data from devices using the Irvis protocol|(% style="width:358px" %)sed_metrology_442.bin
238 -|(((
239 -1.
240 -)))|(% style="width:214px" %)sed_karat_arch|(% style="width:676px" %)A service for receiving archived data from Karat devices|(% style="width:358px" %)sed_metrology_512.bin
241 -|(((
242 -1.
243 -)))|(% style="width:214px" %)sed_lis200_arch|(% style="width:676px" %)A service for receiving archived data from the EK-260 and EK-270 devices manufactured by Elster|(% style="width:358px" %)sed_metrology_452.bin
244 -|(((
245 -1.
246 -)))|(% style="width:214px" %)sed_rtu_over_tcp_sepam_waveform|(% style="width:676px" %)A service for reading waveform files from Sepam devices using Modbus RTU over TCP protocol|(% style="width:358px" %)sed_metrology_298.bin
247 -|(% colspan="4" %)**Data export and import services in SQL databases**
248 -|(((
249 -1.
250 -)))|(% style="width:214px" %)sed_sql_rtd|(% style="width:676px" %)A service for receiving tele-measurement data from MySQL|(% style="width:358px" %)sed_metrology_211.bin
251 -|(((
252 -1.
253 -)))|(% style="width:214px" %)sed_sql_arch|(% style="width:676px" %)A service for archived data retrieval from Microsoft SQL Server|(% style="width:358px" %)
254 -|(((
255 -1.
256 -)))|(% style="width:214px" %)sed_sql_arch_send|(% style="width:676px" %)A service for recording archived data in an external SQL database|(% style="width:358px" %)
257 -|(% colspan="4" %)**Data processing services**
258 -|(((
259 -1.
260 -)))|(% style="width:214px" %)sed_controller|(% style="width:676px" %)A service for telemetry reception and processing (writes to the InfluxDB database)|(% style="width:358px" %)sed_metrology_controller.bin
261 -|(((
262 -1.
263 -)))|(% style="width:214px" %)sed_events_calc|(% style="width:676px" %)A service for generating event based on the conditions specified in the configuration|(% style="width:358px" %)
264 -|(((
265 -1.
266 -)))|(% style="width:214px" %)sed_calc_arch|(% style="width:676px" %)A service for calculating metering channels|(% style="width:358px" %)(((
267 -sed_metrology_calc_arch.bin
268 -
269 -sed_metrology_formulas.bin
270 -)))
271 -|(((
272 -1.
273 -)))|(% style="width:214px" %)sed_calc_rtd|(% style="width:676px" %)A service for calculating pre-calculated tags|(% style="width:358px" %)
274 -|(((
275 -1.
276 -)))|(% style="width:214px" %)sed_round_arch|(% style="width:676px" %)A service for calculating metering channels with rounding|(% style="width:358px" %)sed_metrology_round_arch.bin
277 -|(((
278 -1.
279 -)))|(% style="width:214px" %)sed_energy_calc|(% style="width:676px" %)A service for server-level energy resource calculation|(% style="width:358px" %)sed_metrology_411_421.bin
280 -|(((
281 -1.
282 -)))|(% style="width:214px" %)sed_loadflow_calc|(% style="width:676px" %)A service for calculating modes based on an information model|(% style="width:358px" %)
283 -|(((
284 -1.
285 -)))|(% style="width:214px" %)sed_storage_writer|(% style="width:676px" %)A service for recording archived data (metering and event logs) in a data storage (InfluxDB and MongoDB)|(% style="width:358px" %)
286 -|(% colspan="4" %)**Web Part Services**
287 -|(((
288 -1.
289 -)))|(% style="width:214px" %)php5-cgi|(% style="width:676px" %)A Web Query Service|(% style="width:358px" %)
290 -|(((
291 -1.
292 -)))|(% style="width:214px" %)nginx|(% style="width:676px" %)A Web Server|(% style="width:358px" %)
293 -|(((
294 -1.
295 -)))|(% style="width:214px" %)sed_ui|(% style="width:676px" %)A service for processing requests for web resources (js, css, html files)|(% style="width:358px" %)
296 -|(((
297 -1.
298 -)))|(% style="width:214px" %)sed_rtd_analysis|(% style="width:676px" %)A service for analyzing real-time data|(% style="width:358px" %)
299 -|(((
300 -1.
301 -)))|(% style="width:214px" %)sed_auth|(% style="width:676px" %)A service for authenticating and authorizing users in the system and configuring access rights|(% style="width:358px" %)
302 -|(((
303 -1.
304 -)))|(% style="width:214px" %)sed_auth_privileges|(% style="width:676px" %)A User Privilege Management Service|(% style="width:358px" %)
305 -|(((
306 -1.
307 -)))|(% style="width:214px" %)sed_api_gateway|(% style="width:676px" %)A service for proxying of web requests to other services within the system|(% style="width:358px" %)
308 -|(((
309 -1.
310 -)))|(% style="width:214px" %)sed_dataset_configurator|(% style="width:676px" %)A service for working with datasets|(% style="width:358px" %)
311 -|(((
312 -1.
313 -)))|(% style="width:214px" %)sed_rtd|(% style="width:676px" %)A real-time data subscription service|(% style="width:358px" %)
314 -|(((
315 -1.
316 -)))|(% style="width:214px" %)sed_rtd_archive|(% style="width:676px" %)A service for generating archived data from real-time data|(% style="width:358px" %)
317 -|(((
318 -1.
319 -)))|(% style="width:214px" %)sed_system|(% style="width:676px" %)A service that provides a user interface with information about the system|(% style="width:358px" %)
320 -|(((
321 -1.
322 -)))|(% style="width:214px" %)sed_archive|(% style="width:676px" %)A service that provides user interfaces for analyzing electricity and energy accounting|(% style="width:358px" %)
323 -|(((
324 -1.
325 -)))|(% style="width:214px" %)sed_archive_integrity|(% style="width:676px" %)A service that provides user interfaces for analyzing the completeness of electricity and energy resources data|(% style="width:358px" %)
326 -|(((
327 -1.
328 -)))|(% style="width:214px" %)sed_pq_reports|(% style="width:676px" %)A service for working with power quality reports|(% style="width:358px" %)
329 -|(((
330 -1.
331 -)))|(% style="width:214px" %)sed_pq_journal|(% style="width:676px" %)A service for working with power quality logs|(% style="width:358px" %)
332 -|(((
333 -1.
334 -)))|(% style="width:214px" %)sed_ras_configurator|(% style="width:676px" %)A service for configuring emergency event loggers|(% style="width:358px" %)
335 -|(((
336 -1.
337 -)))|(% style="width:214px" %)sed_reports|(% style="width:676px" %)A service for generating and managing reports, and maintaining user interfaces for reports|(% style="width:358px" %)
338 -|(((
339 -1.
340 -)))|(% style="width:214px" %)sed_widgets|(% style="width:676px" %)A service for the user interfaces of drag'n'drop widgets|(% style="width:358px" %)
341 -|(((
342 -1.
343 -)))|(% style="width:214px" %)sed_menu|(% style="width:676px" %)A service for displaying and configuring CENTO system menu|(% style="width:358px" %)
344 -|(((
345 -1.
346 -)))|(% style="width:214px" %)sed_mnemonic_diagrams|(% style="width:676px" %)A service for the user interfaces of diagrams v2|(% style="width:358px" %)
347 -|(((
348 -1.
349 -)))|(% style="width:214px" %)sed_configuration|(% style="width:676px" %)A service for user interfaces for system configuration (alerts, mail servers, formulas, device trees)|(% style="width:358px" %)
350 -|(((
351 -1.
352 -)))|(% style="width:214px" %)sed_devices_configurator|(% style="width:676px" %)A service for editing device configurations, tags, and channels|(% style="width:358px" %)
353 -|(((
354 -1.
355 -)))|(% style="width:214px" %)sed_common_event_journal|(% style="width:676px" %)A service for user interfaces for generalized configurable event logs|(% style="width:358px" %)
356 -|(((
357 -1.
358 -)))|(% style="width:214px" %)sed_device_event_journal|(% style="width:676px" %)A Device Log Service|(% style="width:358px" %)
359 -|(((
360 -1.
361 -)))|(% style="width:214px" %)sed_operative_journal|(% style="width:676px" %)A service for the user interface of the real-time event log|(% style="width:358px" %)
362 -|(((
363 -1.
364 -)))|(% style="width:214px" %)sed_video_journal|(% style="width:676px" %)A Video Camera Log Service|(% style="width:358px" %)
365 -|(((
366 -1.
367 -)))|(% style="width:214px" %)sed_marking|(% style="width:676px" %)A Dispatch Tag Management Service|(% style="width:358px" %)
368 -|(((
369 -1.
370 -)))|(% style="width:214px" %)sed_sounds|(% style="width:676px" %)A service for the user interface for sound alerts management|(% style="width:358px" %)
371 -|(((
372 -1.
373 -)))|(% style="width:214px" %)sed_video_stream|(% style="width:676px" %)A service for streaming video from cameras registered in the information model|(% style="width:358px" %)
374 -|(% colspan="4" %)**System services**
375 -|(((
376 -1.
377 -)))|(% style="width:214px" %)nats|(% style="width:676px" %)A message broker and a service registry (service registry/service discovery)|(% style="width:358px" %)
378 -|(((
379 -1.
380 -)))|(% style="width:214px" %)influxdb|(% style="width:676px" %)A time series database|(% style="width:358px" %)
381 -|(((
382 -1.
383 -)))|(% style="width:214px" %)mongod|(% style="width:676px" %)A database of configuration and structured data (event logs, requests)|(% style="width:358px" %)
384 -|(((
385 -1.
386 -)))|(% style="width:214px" %)sed_signals|(% style="width:676px" %)A signal reception and transmission service inside the system (remote control, configuration update, manual polling, parameter recalculation)|(% style="width:358px" %)
387 -|(((
388 -1.
389 -)))|(% style="width:214px" %)sed_debug|(% style="width:676px" %)A service for providing access to debugging information of CENTO services|(% style="width:358px" %)
390 -|(((
391 -1.
392 -)))|(% style="width:214px" %)sed_graphql|(% style="width:676px" %)A subscription service for device statuses|(% style="width:358px" %)
393 -|(((
394 -1.
395 -)))|(% style="width:214px" %)sed_energy_calc_configuration|(% style="width:676px" %)A service for creating, changing, and deleting energy resource calculation configurations at the server level|(% style="width:358px" %)
396 -|(((
397 -1.
398 -)))|(% style="width:214px" %)sed_backup|(% style="width:676px" %)A service for backing up data according to the cron rule.|(% style="width:358px" %)
399 -|(((
400 -1.
401 -)))|(% style="width:214px" %)sed_channels|(% style="width:676px" %)A channel subscription service|(% style="width:358px" %)
402 -|(((
403 -1.
404 -)))|(% style="width:214px" %)sed_channels_data|(% style="width:676px" %)A subscription service for protocol statuses and the latest channel data|(% style="width:358px" %)
405 -|(((
406 -1.
407 -)))|(% style="width:214px" %)sed_emission_archive|(% style="width:676px" %)A service for providing emissions metering data|(% style="width:358px" %)
408 -|(((
409 -1.
410 -)))|(% style="width:214px" %)sed_profile_archive|(% style="width:676px" %)A service for providing metering data from InfluxDB via gRPC.|(% style="width:358px" %)
411 -|(((
412 -1.
413 -)))|(% style="width:214px" %)sed_web_storage|(% style="width:676px" %)A service for accessing archived metering data|(% style="width:358px" %)
414 -|(((
415 -1.
416 -)))|(% style="width:214px" %)sed_watchdog|(% style="width:676px" %)A service for managing the launch of CENTO services|(% style="width:358px" %)
417 -|(((
418 -1.
419 -)))|(% style="width:214px" %)sed_scheduler|(% style="width:676px" %)A service for launching scheduled tasks|(% style="width:358px" %)
420 -|(((
421 -1.
422 -)))|(% style="width:214px" %)sed_license|(% style="width:676px" %)A licensing service|(% style="width:358px" %)
423 -|(((
424 -1.
425 -)))|(% style="width:214px" %)sed_monitor|(% style="width:676px" %)A service for monitoring the operation of the system's services and applications|(% style="width:358px" %)
426 -|(((
427 -1.
428 -)))|(% style="width:214px" %)sed_telecontrol|(% style="width:676px" %)A remote control service|(% style="width:358px" %)
429 -|(((
430 -1.
431 -)))|(% style="width:214px" %)sed_notificator|(% style="width:676px" %)A service for notifying users about events by e-mail|(% style="width:358px" %)
432 -|(((
433 -1.
434 -)))|(% style="width:214px" %)sed_waveforms_journal|(% style="width:676px" %)A waveform Log Service|(% style="width:358px" %)
435 -|(((
436 -1.
437 -)))|(% style="width:214px" %)sed_storage_configurator|(% style="width:676px" %)An InfluxDB Database Configuration Service|(% style="width:358px" %)
438 -|(((
439 -1.
440 -)))|(% style="width:214px" %)sed_system_configuration|(% style="width:676px" %)A CENTO System Configuration Editing Service|(% style="width:358px" %)
441 -|(((
442 -1.
443 -)))|(% style="width:214px" %)sed_user_settings|(% style="width:676px" %)A User Settings Configuration Service|(% style="width:358px" %)
444 -|(((
445 -1.
446 -)))|(% style="width:214px" %)sed_system_event_journal|(% style="width:676px" %)A service for registration and provision of system events (business logic and administration)|(% style="width:358px" %)
447 -|(((
448 -1.
449 -)))|(% style="width:214px" %)sed_tech_event_journal|(% style="width:676px" %)A service for processing and managing technological events|(% style="width:358px" %)
450 -|(((
451 -1.
452 -)))|(% style="width:214px" %)sed_information_model|(% style="width:676px" %)A System Information Model Management Service|(% style="width:358px" %)
453 -|(((
454 -1.
455 -)))|(% style="width:214px" %)sed_events_configurator|(% style="width:676px" %)A System Event Configuration Service|(% style="width:358px" %)
456 -|(((
457 -1.
458 -)))|(% style="width:214px" %)sed_information_model_editor|(% style="width:676px" %)A service for editing the information model|(% style="width:358px" %)
459 -|(% colspan="4" %)**Server Backup Services**
460 -|(((
461 -1.
462 -)))|(% style="width:214px" %)sed_coordinator|(% style="width:676px" %)A service for selecting the cluster's host server using the Bully leader election algorithm|(% style="width:358px" %)
463 -|(((
464 -1.
465 -)))|(% style="width:214px" %)sed_reserve|(% style="width:676px" %)A service for displaying a list of backup servers|(% style="width:358px" %)
466 -|(((
467 -1.
468 -)))|(% style="width:214px" %)sed_replicator|(% style="width:676px" %)A log replication service between cluster servers|(% style="width:358px" %)
469 -|(((
470 -1.
471 -)))|(% style="width:214px" %)sed_influx_replicator|(% style="width:676px" %)A data replication service (archives and telemetry) between cluster servers|(% style="width:358px" %)
472 -|(((
473 -1.
474 -)))|(% style="width:214px" %)sed_events_replicator|(% style="width:676px" %)An event replication service between cluster servers|(% style="width:358px" %)
475 -|(((
476 -1.
477 -)))|(% style="width:214px" %)sed_fs_synch|(% style="width:676px" %)A data replication service (gob files, reports, waveforms) between cluster servers|(% style="width:358px" %)
55 +
Screenshot 2025-12-03 at 18.47.38.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Lana
Size
... ... @@ -1,1 +1,0 @@
1 -206.0 KB
Content