## 4 Automated Process for Calculating the Technical Conditions of Devices in an HV Switching Bay
### Data Model for Calculating the Technical Conditions of Devices in an HV SB  
The data model connects all IS databases that are populated during maintenance processes. Each database represents a specific entity. The entities in Figure 4 calculate the technical conditions based on the previously presented criteria. The entities are described according to their usage for the criteria's evaluation. All mentioned criteria utilize the following entities: the evaluation criterion, the asset criterion, and the technical state. The evaluation criterion stores information about the criteria used to calculate the technical state. The asset criterion contains the weight of a specific criterion used for a particular asset. The technical state stores the calculated value of the technical state of an asset using all its asset criteria. Criteria \(CR_{-1}\), \(CR_{1}\), \(CR_{2}\), and \(CR_{3}\) utilize the Asset and Deficiency entities. The Asset is the central entity of the data model, and it collects various data regarding assets, such as their description, type, production year, manufacturer, voltage level, location, etc. The Deficiency refers to a maintenance task for condition assessment defined in IBM Maximo IS. The set of values for the deficiency or internal defect (problem), cause, and resolution is predefined, and it has a finite number of unique values. Criterion \(C_{-2}\), which is used exclusively for ITs, utilizes the entity Measurements. This entity provides data on the diagnostic measurements of the transformer oil properties in measuring transformers and the electrical measurements of the insulating system properties of ITs. Criterion \(C_{4}\) uses the entity Weather to link events with weather conditions, indicating the weather during unplanned events. As described previously, the other entity used is Asset. Criterion \(C_{5}\) uses only the entity Asset for all devices. Criterion \(C_{6}\) for CBs uses the entity Event, which records information about unplanned events in the power grid, and Event statistics, which connect events with the affected assets. The consequence of an event stores the potential failure modes of a device affected by the event that are relevant to the technical state. Another entity used is the Codebook, which links codes with the corresponding codebooks. It contains unique identifiers for the types of codebooks and their entries, allowing access to data on the actual values of the codes. The final entity used is Asset. Criterion \(C_{7}\), for CBs, uses the entity Work Order, which contains data about work orders intended for equipment inspections and deficiency remediation. It has two primary keys to connect with entities. The Work Order for the Task on an asset connects the affected assets with the work order and the tasks that can be implemented on the assets within this workforce. The next entity is the Inspection task, which contains data about tasks that must be performed during an inspection without disconnecting the HV SB. Weather links provide information about the weather conditions during unplanned events. The following entity is Task for Deficiency Correction, which contains data about the tasks performed when remediating deficiencies. The last entity used is Event and its related entities, as described previously. Criterion \(C_{8}\) uses the entity Work Order for Tasks on assets, as described previously. Criterion \(C_{7}\) for Ds and \(C_{9}\) for CBs use the entity Asset's service, a logbook of services performed on an asset. When a service is completed on equipment, the Asset receives a responsiveness rating, indicating its condition. The other entity is the Service Department, which contains data about companies that perform services on specific assets and the previously described Asset. The quality analysis of the input data was implemented, but a detailed explanation is beyond the scope of this study. A quality analysis was implemented of the input data. The limitation of the data model is the data collection period for devices older than 20 years.