# Business Impact Analysis of AMM Data: A Case Study
## 3 Analysis of AMM Data
### AMM Datasets and Systems Entering the Analysis  
For analysis purposes, it is first necessary to identify the datasets that need to be secured in the AMM measurement. For AMM measurements, security must be devised comprehensively across systems. AMM measurement is used today for so-called Type C measurements. Datasets flow through various systems across the entire structure of the organization; see Figure 1, containing a flow diagram of datasets. For the sake of simplicity, one part has been selected, and that is the path of the data sets from the measurement equipment to the customer. A description of each dataset is given as follows:  
* LP15--This is the so-called \"last profile\", which contains the mean values of the performance in the interval of 15 min. This profile is mainly used to obtain better information about the consumption at the point of consumption for the customer and the trader. This profile can be used as a control element for validation, or it can be used to evaluate the maximum for future microservices and the under-supply for consumption. Thanks to AMM metering, the LP15 profile can be used to calculate consumption more accurately in case of complaints of a defective meter at the point of consumption. * LP60--This is a 60 min profile, which is calculated as the arithmetic mean of the sum of the four LP15 values to obtain a profile at a 60 min interval. Its applicability is mainly in the area of monthly deviation billing to the electricity market operator (EMO) and is also provided as customer information. The calculation of LP60 is always performed as part of the validation in the Reading and Validation System. * BW--This is the billing value data set, which is a copy of the meter registers. For billing purposes for type C metering, using AMM, the value of the Net Energy of Consumption or Production is used. This value always has a time stamp. As part of the reading, the values of all possible variables are always read from the meter, most of which are used for validation and verification purposes. * ODP--This type of dataset is an instruction-type message sent to the meter for remote disconnection due to non-payment. It is not used much in practice at present, but in the future, it should be used in cases where the customer has not paid for the electricity consumed and has an inaccessible tapping point. \begin{table}
\begin{tabular}{c c c} \hline \hline
**OBIS Code** & **Magnificance** & **Description** \\ \hline \hline \multirow{3}{*}{1.0.1.4.0.255} & \multirow{3}{*}{+P} & The mean value of active sampling power per evaluation period (projection of the phasor onto the \(x\)-axis in quadrants I and IV) summed over 3 phases. \\  & & The mean value of the active power of the supply for the evaluation period (projection of the phasor onto the \(x\)-axis in quadrants II and III) in the sum of 3 phases. \\  & & Reactive power phase in Q2. \\  & & Reactive power phase in Q4. \\  & & Reactive power phase in Q1. \\  & & Reactive power phase in Q3. \\ \hline \hline \end{tabular}
\end{table} 
Table 2: OBIS codes profile LP15. * PRIPO--The dataset operates on a similar principle as ODP, except that, in this case, it is a connection of the point of subscription, for example, after payment or overwriting the point of subscription. * TAR--The TAR dataset contains tariff setting information, which will either be a message that sets a fixed switching of blocked appliances within the low and high tariff, or is a direct instruction to switch appliances on or off. The function in the meter replaces the existing bulk remote control system and the meter can also switch more types of appliances than was possible with the old-fashioned AMM metering, thanks to the attached relay box. * BLOCK--The BLOCK dataset indicates the power limiting function. It is mainly used in microdevices where it is necessary to limit power generation in case of a large surplus of power in the network. It is also used if the maximum generation at a customer site is exceeded.