software rcm - data interface

ELECTRIC POWER ENGINEERING 2007 Title of paper:

Software RCM – data interface

Author(s):

Vladimír Král, Stanislav Rusek, Radomír Goňo, Tomáš Raška

SOFTWARE RCM – DATA INTERFACE Ing. Vladimír Král Ø VŠB – TU Ostrava, 17. listopadu 15, 708 33 Ostrava - Poruba, CZ, http://www.vsb.cz Ø tel.: +420 597 324 421, e-mail: [email protected] Prof. Ing. Stanislav Rusek, CSc. Ø VŠB – TU Ostrava, 17. listopadu 15, 708 33 Ostrava - Poruba, CZ, http://www.vsb.cz Ø tel.: +420 597 324 377, e-mail: [email protected] Ing. Radomír Goňo, Ph.D. Ø VŠB – TU Ostrava, 17. listopadu 15, 708 33 Ostrava - Poruba, CZ, http://www.vsb.cz Ø tel.: +420 597 324 554, e-mail: [email protected] Ing. Tomáš Raška, Ph.D. Ø SME, a.s. 28. října 3123/153, 709 02 Ostrava, Moravská Ostrava, CZ, http://www.cez.cz Ø tel.: +420 59 667 3591, e-mail: [email protected]

The paper deals with description of input and output data, which are needed for software RCM. Logic of this software is based on the reliability centred maintenance principles. The inputs are databases of maintenance, outages, equipment condition etc. Because the RCM system utilises many information sources and optimise the maintenance of several thousand components, it was necessary to design a right and transparent data structure of all inputs. Input data for the program are reading from the exports from databases of the real distribution company at present. In the future it is supposed on-line connection to databases on real time information system. The contribution describes in detail only two of these inputs – databases of distribution transformers station MV/LV and circuit breakers 110 kV ELF type, and their corresponding outputs.

Acknowledgement: The research has been supported by the Ministry of Education, Youth and Sports of the Czech Republic - project No: CEZ MSM6198910007.

1. Introduction At the Department of Electrical Power Engineering at VŠB-Technical University of Ostrava we have already been concerned with the development of methodology and software for reliability centred maintenance (RCM) since 2004. Our main objective is development of algorithms and calculation procedures for individual components of the distribution network. The result is either optimization of the maintenance cycle according to the type of equipment, or optimization of the maintenance according to the technical condition and importance. Naturally, the input data needed for the selected component and the acquired results are quite different. Firstly, it was necessary to choose the structure and format of all the input and output data needed for implementation of these algorithms into the RCM software itself. This paper describes the current state of affairs - we have already completed the structures for the following components: distribution transformer substation (DTS), 22 kV overhead line, 110 kV circuit breakers, and 110 kV/ MV transformers. The objective of this paper is not a description of the actual algorithms or the software - this has already been done in [1], [2].

2. Data Interface Requirements The actual design of the data interface structure and format starts from these, sometimes quite antagonistic, requirements. The most important are: - compatibility with different operating systems - expand and availability of tools in which these data can be processed (software) - speed of data access - possibility of export from the existing information systems of distribution companies - off-line interconnection, but also readiness for direct access into the existing information systems The RCM software is developed in Microsoft Visual Basic, therefore other very important criteria is easy manipulation and processing these input and output data in this development system. At the very beginning we rejected export and processing data files due to their bad arrangement in case of more elaborated and complicated structures. Moreover, it would be also unsuitable to use the binary data formats structured with respect to the data itself or the development system. For the reasons stated bellow, we have also abandoned purely database formats. Finally, the optimum way seems to be a combination of the Microsoft Excel and Access tables. Using only Access databases was not possible due to indefiniteness of some input data (the input may be a number, as well as a text). Another reason is that Excel is very wide-spread and part of the basic MS Office software package. Moreover, every user can manage using this program on a lever needed for developing off-line databases and their possible editing.

2.1 General rules, definitions Inputs in Excel format are used in cases where there is further editing possible. Inputs in Access format are used in cases where this sort of access can dramatically accelerate processing the data or where it is advantageous with respect to the calculation algorithm. A typical example is information retrieval, for which in SQL language is used. In some cases there is an option of these two formats, which concerns values of the inputs and the outputs as well.

In the following chapters we have described in detail structure of the input values, their format (data type), and possible description. We used expressions in accordance with the Visual Basic language to identify every data type, see Tab. 2.1. Tab. 2.1 the list of data types Identification integer long single double Boolean string string (X) variant date

Data type integer integer (double accuracy) decimal number decimal number (double accuracy) logical value string of variable length string of firm length general (number and string) date in international format (d.m.y.)

Number of bytes 2 4 4 8 1 10+length of the string length of string (X) 16 / 22+ length of string 8

The number of bytes is given in Tab. 2.1 only because the length of the given data type in Visual Basic may be different from another programming language. The length has no influence on further processing of these values itself. Differentiation of the input and output values is relevant to Tab. 2.2. In some cases a value may have a meaning of both, the input and the output. Tab. 2.2 Identification of the input and output values Input value Output value (outcome)

In Out

3. DTS DTS are the case of the first approach to calculation – optimisation of the maintenance cycle. The characteristic feature of the input database is a great number (thousands) of individual components. Accuracy of the input database design essentially influences the speed of further processing. The values for the calculation are downloaded from several independent tables. Parameters of individual DTS are read up from the table, where the number of lines is equal to the number of evaluated DTS. Every DTS contains data that are given in Tab. 3.1. If one or more parameters are missing, the given DTS is not included in the calculation. This table may be in Excel and Access format for both - downloading the input values and saving the result of the calculation. Nevertheless, the original table is always in Excel, as the export in the relevant format from information systems directly into Access is not possible. A table in Access is also used for calculations of 22 kV lines and 110 kV / MV transformers. The output values that can be inserted only manually are in green colour. These can correct values calculated by a given algorithm on the practice basis. The final result – the maintenance schedule for every single DTS – is in blue. All the other tables are in Excel. The data types in these tables reflective the internal variables in the software itself. Excel does not distinguish individual types and all the numerical data are internally stored as a decimal number with double accuracy – identification double.

Tab. 3.1 DTS Inputs/Outputs Name

Description

Data type

CIS_DTS S

Number DTS Nominal load Residential sector (homes) Commercial sector (businesses) Number of wholesale consumers

long long

Input / Output In In

long

In

long

In

long

In

MOO MOP VO

PRODUKT UTVAR KREDIT

Kiosk / not a kiosk type Description

Calculated group to which it belongs Corrected group to SKUPINAM which it belongs Date of the last MINULA_UDRZBA maintenance Maintenance DATLSI_UDRZBA schedule DALSI_UDRZBA_M Corrected schedule SKUPINA

string (50)

Allowed Values

kiosk DTS 22/0,4 kV / tower DTS 22/0,4 kV

In

string (50) long

In Out

long

Out

long

Out

date

In

date

Out

date

Out

Tab. 3.2 Parameters of the DTS Name

Description

Data type

kMOO kMOP kVO n k kp pskupin hmez2 hmez3

Residential sector (homes) Commercial sector (businesses) Wholesale consumers factor DTS– not a kiosk DTS - kiosk Importance factor of load Number of DTS groups for division Upper limit for group 2 Upper limit for group 3

long long long long long long long long long

The number of hmez parameters in Tab. 3.2 is variable and depends on the number of groups for DTS division.

Tab. 3.3 Inputs from the technical and financial information system Name nQ kQ uN025 No Ppor TPpor Tu ERR Sodb Lu P SO Cmoo Cmop Cvo Vmoo Vmop Vvo V1 V2 V3 Np1 Nup1 Kned

Description Demand factor of maintenance of distribution transformer stations – not of kiosk type Demand factor of maintenance of distribution transformer stations – of kiosk type Costs of maintenance of quarter of equipment per year (CZK) Total costs of repair per year (CZK) Number of failures Total time of failures per year (h) Time of scheduled outage (h) Number of outages at not obeying the standards per year Penalty considered per one consumer (CZK) Maintenance rate (1/year) Average output of one distribution transformer station (MW) Period under consideration (year) Price of undelivered energy for residential sector (homes) Price of undelivered energy for commercial sector (businesses) Price of undelivered energy for wholesale consumers Relationship between the costs of undelivered energy by consumer type - for residential sector - homes Relationship between the costs of undelivered energy by consumer type - for commercial sector - businesses Relationship between the costs of undelivered energy by consumer type - for wholesale consumers Relationship between the costs of outage by particular groups – group 1 Relationship between the costs of outage by particular groups – group 2. Relationship between the costs of outage by particular groups – group 3. Fixed costs due to unscheduled outage Fixed costs due o maintenance shutdown Multiple of undelivered energy during unplanned unavailability time

Data type double double long long double double double integer integer double double integer double double double integer integer integer long long long integer integer integer

Tab. 3.4 Outcomes of the DTS summary, all of them are the Out type Name

Description

Data type

kDTS nDTS DTSO ODB MOO MOP VO kDTS1 nDTS1 kDTS2 nDTS2 kDTS3 nDTS3

Number of all individual DTS – kiosk type Number of all individual DTS – not kiosk type Number of DTS with no consumers Total of all consumers from their own DTS Number of all MOO consumers Number of all MOP consumers Number of all VO consumers Number of DTS in group 1.- kiosk type Number of DTS in group 1. – not a kiosk type Number of DTS in group 2. – kiosk type Number of DTS in group 2. – not a kiosk type Number of DTS in group 3. – kiosk type Number of DTS in group 3. – not a kiosk type

long long long long long long long long long long long long long

Again, the number of kDTS and nDTS parameters is dependant on the number of groups for division of DTS. This whole table may be used as an input one for the actual calculation – in such a case the original Tab. 3.1. needs not to be at disposal. Consequently, all the output data are in Tab. 3.5., i.e. the results of optimal maintenance in individual DTS groups. Tab. 3.5 Results of the optimal maintenance of DTS for individual groups, and all of them are Out type Name Group Rate Interval Costs

Description Number of group Optimum maintenance rate Maintenance cycle Costs

Data type integer single single single

4. SF6 Circuit breakers, type ELF This component is an example of the second calculation approach – condition and importance based maintenance. Both possible formats of the input tables are used here for a benefit – 4 are in Excel, 5 in Access. Detailed and total results are stored in Excel, however in Access only totals are stored. There are input data on the technical condition in Tab. 4.1. The first three identification data are the same in tables for technical diagnostics and importance; the other seven data are only in this one.

Tab. 4.1 Technical condition input data Name Name of the distributing substation Outlet Type Extinction medium Year of putting into service Year of manufacture Serial number of the circuit breaker Kind of the drive Type of the drive Year of the drive manufacture Date of the last action Date of the last overhaul of contacts Number of close/open (CO) cycles after the overhaul of contacts Date of the last overhaul of drive Number of CO after the overhaul of drive Number of engine hours after overhauling (Mh) Date of technical condition evaluation Weather conditions (%) Number of CO Number of drive engine hours (Mh) Tightness of extinguishing chamber (%) Condition of metal parts (corrosion, coating) (%) Earth wire condition (protection against dangerous contact with nonlive parts) (%) Condition of insulators (%)

Data type Allowed values string string ELF SF2-1, string ELF 145pc1z, ELF 123 string SF6 long long string string air string long date date double variant variant variant date double 0 ÷ 100 double double double 0 ÷ 100 double 0 ÷ 100 double

0 ÷ 100

double

0 ÷ 100

Tab. 4.2 Technical diagnostics input data name Name of distributing substation Outlet Type Voltage drop on the main contacts(mV) Switching-in time (ms) Releasing time (ms) Asynchrony at switching-in (ms) Asynchrony at releasing (ms) Composition SF6 (%) Dew point SF6 (°C) – circuit breaker without filter Dew point SF6 (°C) – circuit breaker with filter Decomposition products SO2 (ppm) - circuit breaker without filter Decomposition products SO2 (ppm) - circuit breaker with filter

Data type Allowed values string string ELF SF2-1, string ELF 145pc1z, ELF 123 variant variant variant variant variant variant variant variant variant variant

Tab. 4.3 Importance input data Data type Allowed values string string ELF SF2-1, string ELF 145pc1z, ELF 123 transformer, variant line, KSP, SP variant radial, parallel variant yes, no variant 1, 2, 3 variant

Name Name of the DTS Outlet Type Location of the circuit breaker Type of the line Possibility of back-up Importance of consumption Energy transmitted per year (MWh) The type Variant has been used in majority in these three tables. Tab. 4.4 Criteria weights for assessing technical condition Name Weather conditions Extinction medium Age of the circuit breaker Number of CO after the last overhaul or repair of contacts Tightness of extinguishing chamber Kind of the drive Number of engine hours from the last overhaul or repair of contacts Tightness of the pressure system of the drive Evaluation of diagnostic tests Condition of metal parts (corrosion, coating) Condition of earth-wire Condition of insulators Time from the last common maintenance

Data type double double double double double double double double double double double double double

Tab. 4.5 Evaluation spans Name (wanted parameter) Extinction medium Extinction medium Age of the circuit breaker Number of engine hours from the last overhaul or repair of contacts Kind of the drive Kind of the drive Kind of the drive Limit for number of CO Number of engine hours from the last overhaul or

Allowed values (wanted value)

Return value

SF6 oil limit (year)

long long long

limit (CO)

long

spring-loaded pneumatic air 5000 2000

long long long long long

repair of contacts Tightness of the pressure system of the drive Time from the last common maintenance

(Mh.year-1) year

long long

Tab. 4.6 Evaluation of importance Name ( wanted parameter) Location of the circuit breaker Location of the circuit breaker Location of the circuit breaker Location of the circuit breaker Type of the line Type of the line Type of the line Possibility of back-up Possibility of back-up Importance of consumption Importance of consumption Importance of consumption Energy transmitted in a year [MWh] Energy transmitted in a year [MWh] Energy transmitted in a year [MWh]

Allowed values (wanted value) transformer line KSP SP radial parallel other yes no 1 2 3 400000 other

Return value long long long long long long long long long long long long long long long

Foregoing tables 4.5 (Evaluation spans) and 4.6 (Evaluation of importance) and the following tab. 4.7 (Limits of technical diagnostics) are in Access format, they have been used to retrieval of values of three types of these circuit breakers. Identification of the type serves as an index of the given table. Tab. 4.7 Limits of technical diagnostics Name

Description

Data type

UbytekU ZapCas VypCas NesPriZap NesPriVyp SlozSF6 RosBodBezF RosBodSF RozProBezF

Voltage drop on the main contacts (mV) Switching-in time (ms) Releasing time (ms) Asynchrony at switching-in (ms) Asynchrony at releasing (ms) Composition of SF6 (%) Dew point SF6 (°C) – circuit breaker without filter Dew point SF6 (°C) – circuit breaker with filter Decomposition products SO2 (ppm) - circuit breaker without filter Decomposition products SO2 (ppm) - circuit breaker with filter

long long long long long long long long long

RozProSF

In tab. 4.8 the total outcomes are in Access.

long

Tab. 4.8 Total outcomes of SF6 circuit breakers Name ROZVODNA VYVOD TYP VYR_CISLO TECH_STAV DULEZITOST DIAGNOSTIKA PRIORITA PORADI

Description Name of the substation Outlet Type Manufacture number Outcomes of the technical condition Importance of the circuit breaker Final evaluation of the diagnostics Priority Optimal order of the maintenance

Data type string (20) string (20) string (20) string (20) long long long long long

5. Conclusion We have described here all the data inputs/outputs for the DTS and HV circuit breakers of the ELF type. In practice it will be necessary to ensure interconnection of these off-line databases with real information systems of distribution companies. The optimum solution seems to be development of a support system completing the above tables with values from these information systems so that the software itself can work with all the databases off-line seems. Another possibility is direct on-line connection on the information system. However, the disadvantage of such a solution is detailed knowledge of this system and mainly its data structures.

Acknowledgment The research has been supported by the Ministry of Education, Youth and Sports of the Czech Republic - project No: CEZ MSM6198910007.

Literature: [1] [2]

Skog J.: Maintenance Task Interval Determination. Maintenance and Test Engineering Co. USA, 1999. Rusek, S., Král, V., Goňo, R., Raška, T.: Software RCM – an Optimization Tool for the Maintenance of Electric Power Network Devices. In 6th International Scientific Conference Electric Power Engineering 2005, Kouty nad Desnou, Ostrava:VŠB - TU Ostrava, 2005, 10 p., ISBN 80-248-0842-0.