# Software Integration of Power System Measurement Devices with AI Capabilities
## 3 Proposed Integration Framework  
### Requirements  
The aim of this work is to create a software architecture that can accommodate the measurements of different electrical monitoring devices while making the data available to any artificial intelligence task in real time. Particular attention is given to PMUs, as they exhibit distinctly different behavior compared to the other equipment discussed in the previous section (see Table 2). On the contrary, PQMs and SMs shows some similarities, as both devices collect power and energy data. Usually, PQMs include a wider range of measures, including more detailed power quality data. However, the specific list of measurements may vary based on the manufacturer. They both rely on standard communications protocols on the market. The case of PMUs is different. For them, sample synchronization, efficient storage, and high transmission speed are essential. Since PMUs are capable of sending up to 100 FPS, very high data volumes can be reached in a short period of time. This requires an \begin{table}
\begin{tabular}{c c c c} \hline \hline
**Application** & \(\upmu\)**PMU** & **PQM 1** & **Smart Meter** \\ \hline Monitoring & Yes [14] & Yes: designed for this purpose [4, 13] & Yes [35, 36] \\ \hline Harmonic Analysis & No & Yes [37] & No \\ \hline Event Detection & Yes [38, 39, 40] & Most devices include an event recorder & No \\ \hline Protection and/or Control & Yes: designed for this purpose [41, 42] & Less recommended & No \\ \hline Fault Location & Yes [6, 7, 8] & Yes [4, 5] & Yes [43] \\ \hline Modeling & \
\begin{tabular}{c} State \\ estimation [9, 10, 12] \\ \end{tabular} & Load modeling [2, 44] & Load modeling [45, 46] \\ \hline Topology & Yes [47, 48] & No & No \\ \hline Demand Forecasting &
\begin{tabular}{c} \\ and Management \\ \end{tabular} & Less recommended & Yes [49] & Yes [50, 51, 52] \\ \hline \hline \end{tabular}
\end{table} 
Table 1: Summary of applications for \(\upmu\)PMU, PQM and SM. \begin{table}
\begin{tabular}{c c c c} \hline \hline
**Feature** & \(\upmu\)**PMU** & **PQM** & **Smart Meter** \\ \hline
**Sampling Rate** & 25,600 m/s at 50 Hz & 25,600 m/s at 50 Hz &
\begin{tabular}{c} from 1600 m/s up \\ to 51,200 m/s \\ \end{tabular} \\ \hline
**Transmission Rate** & \begin{tabular}{c} from 10 ms up to \\ 100 ms \\ \end{tabular} & \
\begin{tabular}{c} from 1 s up to \\ 10 min \\ \end{tabular} &
\begin{tabular}{c} from 1 s up to \\ 10 min \\ \end{tabular} \\ \hline
**Transmission Speed** &
\begin{tabular}{c} Crucial. IEEE Std \\ C37.118.2 [53] \\ \end{tabular} & Not crucial & Not crucial \\ \hline
**Measures** & \begin{tabular}{c} Voltage and current \\ phasors. Frequency. \\ ROCOF \\ \end{tabular} & \
\begin{tabular}{c} PQ data. Frequency, \\ Voltage, Current, \\ power, THD, TDD, \\ harmonics, etc. \\ \end{tabular} &
\begin{tabular}{c} Power and energy \\ data. Frequency, \\ voltage, current, etc. \\ \end{tabular} \\ \hline
**Data Volume** & Very high & High & Low \\ \hline
**Synchronism** & \
\begin{tabular}{c} Very important. \\ GPS. \\ \end{tabular} &
\begin{tabular}{c} Less important. \\ NTP (usually) \\ \end{tabular} & Less important \\ \hline
**Most Common** &
\begin{tabular}{c} IEEE Std. C37.118.2. \\ \end{tabular} & Modbus ASCII & Modbus RTU \\ \hline \hline \end{tabular}
\end{table} 
Table 2: \(\upmu\)PMU, PQM, and SM communication capability comparison. infrastructure that can not only store a large volume of data but also access it efficiently. The infrastructure must also be able to respect the original time stamping of the PMU. PMUs generally use the IEEE C37.118.2 standard [53]. Within this standard, the need for a Phasor Data Concentrator (PDC), a software that collects and manages the phasors, is specified. This article proposes a valid framework for PMUs, SMs, and PQMs that collect data based on commercial protocols while incorporating the standards of the IEEE Std. C37.118.2 and the use of a PDC. Firstly, in Section 3.2, a brief sketch of the design is shown.