ࡱ> gifyG Pbjbjَ D!]n n n D < | hn /J"QJ ]Jhhhhhhh$ik@hQn eJI|/JeJeJ@hQ = QQQeJ :n h eJhQnQIVd n h j D`u73 ANgNISOHEP - COMPUTERIZED MAINTENANCE MANAGEMENT SYSTEM FOR CROATIAN NATIONAL ELECTRICITY (HEP) Zdravko HEBEL Mirta BARANOVI Slaven ZAKO`EK Keywords: Computerized Maintenance Management System Maintenance Rules Maintenance Planning - Technical Database - Active Database ABSTRACT: The foundation of the system lies in a technical database containing all the data relevant for the maintenance processes. ISOHEP helps the users to plan maintenance activities, to store and analyze the information about maintenance process. The outage management subsystem enables the minimization of the number and duration of outages. Embedded active mailing subsystem helps the users to be informed about all the relevant events in the power system.  INTRODUCTION ISOHEP is an information system for technical maintenance (1), developed for Croatian National Electricity (HEP) and implemented in the Control and Transmission Department. Within the Control and Transmission Department, the equipment maintenance is organized in four transmission areas (PrP), which are: PrP Opatija, PrP Osijek, PrP Split, and PrP Zagreb. Every PrP deals with the maintenance of its own equipment, and the only interfering points are the places where high-voltage lines cross the border between two areas. In such a case, every PrP is responsible for its own part of the common high-voltage line maintenance, but a coordination of the maintenance activities becomes necessary. Within each PrP, there are different groups specialized for maintenance of specific device types, like: high-voltage equipment within the transformer stations, high-voltage lines: overhead lines and cables, protection relays, metering equipment, telecommunication network equipment, telecontrol system equipment. The maintenance of some device types, like voltage transformers, is performed by different groups. In that case, a coordination of activities among different groups is very important. In the described real-world environment, ISOHEP is helping to achieve the principal maintenance goals: availability and reliability of the power system, cost-effective maintenance, systematic maintenance planning, minimizing the need for outages. ISOHEP is planned as a system that will cover three levels of the information pyramid in maintenance domain: operational level, operational planning level and strategic planning level.  Figure 1 Three Information Levels of ISOHEP In Figure 1, the information pyramid is presented together with respective activities on each level. On each higher level, a summary of data from lower levels is present. While progressing to upper levels of the information pyramid, the amount of data is diminished, but the quality is improved due to increased sophistication in the data processing. ISOHEP BASIC STRUCTURE  The basic structure of ISOHEP is presented in Figure 2. The foundation of the system lies in a technical database containing the data relevant for the devices, transformer stations, high-voltage lines and the other subjects to the maintenance processes. The maintenance technology is described by the maintenance rules. The system helps the users to plan and trace maintenance activities, to store and analyze the information about failures and repairs, to issue work orders and to store and analyze all the information about work results. A very important part of the ISOHEP is the outage management subsystem, which enables the minimization of the number and duration of outages. In addition, the active alerting and message management subsystem informs the users properly and timely about all the relevant events and states in the power system. TECHNICAL DATABASE The technical database contains data about devices, where any equipment prone to maintenance is regarded as a device. Every device is described by all the data relevant to its maintenance processes. The data are divided into several classes, as presented in Figure 3.  The basic data are common for all the device types and are independent of the particular device type. Examples for such data are: the device producers, the year of production, a factory catalog number and so on. Depending on the device type, there are several data classes to be recorded. Therefore, a compound device, like the power transformer, is described by data classes that span across ten screens, while some elementary device can be described by only a few fields within one screen. For every device, depending on its class, there are some data about the function that it performs within the power system. The placement of a device, its maintenance, failures, repairs and comments are being recorded throughout the device history, what makes possible a comprehensive analysis of the functioning and the status of the device. MAINTENANCE PLANNING Two fundamental types of maintenance activities have been implemented in ISOHEP. The distinction was made according to the source of stimulus for maintenance: Periodical maintenance is performed after predefined intervals of time. It is the preventive periodical maintenance, defined by the maintenance rules. Event or status driven maintenance is triggered by an event or by a predefined device status. It encompasses: preventive status-indicated maintenance. For example, a prescribed number of accomplished device operations since its last maintenance triggers a maintenance activity. corrective maintenance and urgent interventions are triggered by a failure report Periodical maintenance rules For every device type, a set of periodical maintenance rules is defined (2). These rules are user definable within the ISOHEP. In general, a rule can be defined by the description of an activity and its period. However, the same activity can be applied with different periodicity, depending on some characteristics, location, or functions of the device. For that reason, to each activity more than one pair of conditions and respective periods can be attached. More formally, maintenance rules can be described as follows. Let nt be the number of different device types. Every device that belongs to the type i, i ( [1, nt] is described by mi different attributes, Ai, 1, , Ai, mi , defined over their respective domains Vi, 1, , Vi, mi. For each device type, a set of nwi periodical maintenance activities is defined: wi, j , where, i =1,..,nt , j=1,,nwi Every activity, wi, j, is described as follows: wi, j = (di, j, si, j, gi, j ) ; i = 1,.., nt; j = 1,.., nwi where di, j denotes the activity description, si, j indicates an outage requirement, and gi, j denotes a specialized group that performs the maintenance activity. For every activity, different conditions and periods can be defined. Let nci, j be the number of different conditions for the activity wi, j . The condition, ci, j, k, (k = 1, ..nci, j , where nci, j ( 1) is defined as follows: ci, j, k = (f i, j, k, p i, j, k), k = 1, ..nci, j where f i, j, k is a formula that has to be satisfied by the device i to trigger the application of the activity wi, j with period p i, j, k. Formula f i, j, k , (i = 1,.., nt; j = 1,.., nwi ; k = 1, ..nci ) can either be: a tautology (T); in that case activity wi, j is performed on every device that belongs to the type i or defined as follows: Let Ai, m RelOp c and c RelOp Ai, m be formulae, where RelOp is a comparison operator from the set {(, (, (, (, (, ( }, and let c be a constant from Vi,m ; m([1, mi] If G and H are formulae, then G(H, G(H, ( G and (H also are formulae Nothing else is formula In the case where the number of conditions defined for a particular activity is greater then 1, those conditions have to be mutually excluded, what is defined by the following expressions: Let Di be the set of devices of type i, (i=1, nt) and let the sets Di, j, k, and Di, j, p be the subsets of Di , such that contain devices satisfying conditions f i, j, k and fi, j, p, respectively: Di, j, k = { d (d ( Di ( f i, j, k (d)}, j = 1,.., nwi, k ( (1, nci, j ) Di, j, p = { d (d ( Di ( f i, j, k (d)}, j = 1,.., nwi, p ( (1, nci, j ) Accordingly, they have to satisfy also the following condition: Di,j,k ( Di, j, p ( (, (k, k ( (1, nci, j ), (p, p ( (1, nci, j ), k ( p In other words, a certain activity on a device can have only a single maintenance period. Periodical maintenance planning Basic information to calculate the periodical maintenance plan for a device is the date of the last performed maintenance activity, (or the date of commissioning, for devices that have not been maintained yet) and the respective maintenance period. According to that information, the due date of the next maintenance activity is computed. The planner within a specialized group has to fix a planned date for the maintenance activity, according to the outage plan, to the other group plans and in coordination with other participants in the maintenance process. The maintenance plan consists of a large number of records (one record per device and activity). ISOHEP helps the user to retrieve the plan according to various criteria. In addition, it is very important to inform the user about the time discrepancy between the data, and the activity urgency level. Different urgency levels are presented in different colors on the screen. The activity urgency level is determined by its computed due date and TODAY. The observable discrepancy OD is defined for an activity with period T, expressed by the number of days, as follows: OD = min (T/2, 365) For an activity with the computed due date DC and the period T, the urgency levels are defined as follows: activity is late if : DC < TODAY activity is very late if : DC + OD < TODAY activity is urgent if DC + T ( TODAY Late, very late and urgent activities are presented in red, reverse red and blinking reverse red fields in the screen. The user can also retrieve activities according to different urgency levels. Status-indicated maintenance planning Status-indicated maintenance activities are triggered by some event or by a change in the device status. A trigger action can stem from the telecontrol system when the number of operations, requiring certain maintenance activities, was exceeded. Such an activity is included into the plan with its due date of maintenance set to TODAY. In addition, the system automatically sends an alert to the user responsible for planning of this type of activities within his/her specialized group. This person has to schedule the activity, according to the other elements of the plan in his/her own group and to the plans of other groups. Another possibility to trigger a certain activity arises from results of periodical inspections. After the inspection process, the findings are recorded, the status of the device is determined and a status-dependent activity is scheduled: as urgent, to be performed within a specified period of time, to be performed together with the next periodical maintenance activities. When the need for an urgent intervention is detected, the system generates an alert to the user responsible for the required activity and he/she will issue a work order and all the accompanying documentation. In the other two cases, the required activity is introduced into the plan to meet the specified due date. Planning of repairs When a failure occurs, a procedure analog to the state-triggered maintenance is performed. The trigger for an activity is a failure report. It can be obtained from the telecontrol system, or it can be manually introduced into the ISOHEP at the moment of the failure reporting. WORK ORDERS ISOHEP enables issuing of work orders and all the accompanying documents (check-lists, permissions, outage notification) needed for the maintenance. A work order can contain the activities for maintenance, installation and replacement of devices. A work order is issued for activities within: one location, e.g. transformer station, - activities can be performed on different positions, only one position within the same location - usually in the case when an outage is required, a high voltage line or parallel high voltage lines, a part of a high voltage line(s). After the work has been done, the results are recorded. For all the periodical maintenance activities that have been accomplished, new due dates are computed according to their periods. Those activities that have not been accomplished, are postponed to wait for a future work order. The repairs, which have not been committed, have also to wait for a future work order. The work report contains information about workers, their engagement, the vehicles used and distances traveled. The issued spare parts are recorded within the material management system. ISOHEP records only the respective document identifier, what enables a connection during the cost analysis. OUTAGE PLANNING During the maintenance of high voltage devices, it is necessary to switch off the appropriate part of the electric power system. The maintenance process has to be so organized, that the number and the duration of outages be as small as possible. Special care is paid to the outage planning and to the management of demands for outages. Outage demands management is performed in the following way: Specialized groups are posting the outage demands. The Control department unites the demands and forwards them to the dispatcher. In accordance to the dispatcher's reply, a member of the Control department will approve or reject an outage demand. At any time, every user can observe all the active outage demands and approvals. Whenever a date is to be entered, a calendar appears where the days bearing outage demands and approvals for a location or a position are highlighted. A planner in another department can review all the necessary information and he/she can try to schedule the activities of his/her department right for the same time. EMBEDDED MAILING SYSTEM A system has been developed to inform the users about some important event or status. It has been predefined: types of events or states, message text, users or user groups to be notified. Within ISOHEP, the triggers have been defined for each specified event or status. They initiate the sending of messages to the predefined users or user groups. Mailing groups are defined to be informed about specific events and/or states. Each user can subscribe to one or more mailing groups or message types. Some typical examples for the automatically generated messages form ISOHEP are: an employee from the Control department receives a notification about a new outage demand, the employee who sent the outage demand receives an information about approval/rejection, the planner, who is in charge for the circuit braker maintenance, receives the message that the number of operations of this device since its last maintenance has exceeded the prescribed value and a maintenance activity is required The ISOHEP mailing system supports also the communication among the users. Receipt of each message is signaled by a visual and audio notification. The users connected to Internet/Intranet can receive their ISOHEP mail via their standard mailer. CONCLUSION ISOHEP is a computerized system to help the maintenance personnel. At any time, every user can achieve all the necessary information to make the decisions regarding maintenance. All the recorded information can optionally be printed in the form of documents. The system has been implemented in the open environment, on the SCO UNIX platform supported with the relational database management system INFORMIX. The first version was installed in 1993. The ISOHEP users (about 200 of them, nowadays) have passed a basic education. They can be acquainted to new functions via the news system, integrated into ISOHEP. A parallel training system is also available where the users can try the system functions without fear of data damage. Currently, ISOHEP covers the operational domain and the operational planning domain. Within the Transmission areas, separate ISOHEP systems exist which are interconnected by the National Electricity Computer Network (HEPAK). Recently implemented infrastructure allows the system integration into a distributed database. The hierarchically superior node will contain common operational data, common catalogues and the data required for coordinated operational planning. Currently, a part of the decision support system, (Data Warehouse, Data Marts) is also under development.  BIBLIOGRAPHY: 1. Z. Hebel, M. Baranovi, A. Maruai, S. Zakoaek, V. Kalafati, E. Mileusni : Informacijski sustav odr~avanja opreme u Hrvatskoj elektroprivredi, Croatian Committee of International Conference on Large High Voltage Electric Systems - CIGR , Primoaten, May 14-18, 1995 2. Pravilnik o odr~avanju elektroenergetskih objekata prijenosne mre~e, HEP, Zagreb, 1991 Prof. dr. sc. Zdravko Hebel University of Zagreb, Faculty of Electrical Engineering and Computing Unska 3, 10000 Zagreb, Croatia Phone: +385 1 6129 980, Fax: +385 1 6129 890, e-mail: zdravko.hebel@fer.hr Doc. dr. sc. Mirta Baranovi University of Zagreb, Faculty of Electrical Engineering and Computing Unska 3, 10000 Zagreb, Croatia Phone: +385 1 6129 916, Fax: +385 1 6129 915, e-mail: mirta.baranovic@fer.hr Mr. sc. Slaven Zakoek University of Zagreb, Faculty of Electrical Engineering and Computing Unska 3, 10000 Zagreb, Croatia Phone: +385 1 6129 879, Fax: +385 1 6129 915, e-mail: slaven.zakosek@fer.hr Operational planning Strategic planning Operational data maintenance rules, personnel, maintenance strategy maintenance schedule, coordination among the groups recording of data about the devices and their maintenance, retrieving of all the data relevant for the maintenance Comments Data about repairs Data about failures Preventive maintenance data Device function dependent data Device type dependent data Device loaction data Basic data OUTAGE PLAN MAINTENANCE PLAN E-MAIL  EMBED CorelDRAW.Graphic.6   EMBED CorelDRAW.Graphic.6   EMBED Excel.Sheet.8  FAILURE REPORT Operational data Operational planning PrP ZG WORK ORDER MAINTENANCE RULES TECHNICAL BASE Operational data Operational planning PrP OS Common operational data & operational planning Data Warehouse -Data Marts Operational data Operational planning PrP OP Operational data Operational planning PrP ST ISOHEP Figure 3 Data Classes for Description of Devices DOCUMENTATION Figure 2 ISOHEP Basic Structure (WXdl5WKL#$&'().0BCD\`fk 239RTX]adhko~H*mH  5H*mH  jmH 5hmH nH  hmH nH  jUmH  jUmH6mH  56mH mH 5mH  5CJmH J*$$l4  #$$$ $$ P r$ P & F$ hP & Fr$ hP$ P P$ P$*  Q > Z { WYZû~xuroI k         BC  ?  S  f      67BC            +  Q > Z { WY & F8 h8 & F8 h8 & F h PYZ[\]^_`ab     Z[\]^_`ab      ?@tzwtq    UV, ?@t5L<=[!"RS4ľ~{xuroliLM}~DbcI  I"   D" !   K!   (5L<=[!"RS & F"8 h8 & F!~  ! ' . 2 9 E G K U \ ! ! !!!!8!;!T!U!Y!!!!!!!!!!!""""""""" jhmH  j>hmH  jhmH  j=hmH hmH  OJQJmH  jmH mH H*mH 5mH N45 M -!!!!R"""n#o#7$$$$%X%Y%% & F h & F  h & F8 h8$45 M -!!!!R"""n#o#7$$$$%X%Y%%%((5)6)B*Y*Z***+8+9++¿~vnkhz{$  $   $ YZq}~5   5FGh01   M       r Rjk$"""" ","-"A"B"E"I"J"N"O"P"R"r"s"w"x"{"|"""t#v###########$$ $'$9$@$G$H$J$K$M$N$O$P$R$T$[$l$n$o$s$t$y${$$$$$$$$ jhmH  jhmH  H*hmH  jhmH  jhmH  jhmH  5H*mH 5mH  jmH H*mH mH  5hmH  jhmH  j*@mH  @H*mH @mH @mH  5@mH  jmH  j"hmH  jhmH  j=hmH  jmH 5mH H*mH mH  jhmH  H*hmH hmH  jhmH >%%((5)6)B*Y*Z***+8+9++#,,,.///0000 & F  h & F$*$8 h08*$ 0++0+1++,#,/0Q1e1{2;;EEEEHHHHI6J^J`JJKKLLLLLLLLLLLMMM9M:MnMoMMM꾲CJmHB*CJOJQJhmH nH 5B*CJOJQJhmH nH 5B*CJOJQJhmH nH B*OJQJhmH nH 5B*CJOJQJhmH nH 5mH @CJmH  @CJmH 5mH  jUmH mH  hmH nH  j@mH @mH /+#,,,.///0000Q1e1{222333 4j44444656_7o7p788829õ}zwtlifc`Z `   FG    n         5  h   s dop   !0Q1e1{222333 4j44444656_7o7p788829999; & F8 h8 & F*$ 029999;;; <'<5<Z<[<<<===?>>??x@@@6AAAaCbCEEEEEEEEE¿}zwtqnkheb:    F    *+P  ^   y   hi  -  %;;; <'<5<Z<[<<<===?>>??x@@@6AAAaCbCEE & F h & F8 h8EEEEEEEEEEEEEEEEEEHHHHHHHHIIIrEEEEEEEEEEEHHHHHHHHIII`JbJJ(KfKLLL^L}LLLLLLLLMM9M:MnMoMMMMMMMMMMMNN N N N N NN"N#N$N%N&N'NCNDNENFNGNHNINJNjNkNNNNNNNNNN WI`JbJJ(KfKLLL^L}LLLLLLLLMM9M:MnMoMMMMMM$rMMMMMMMMMNN N N N N NN"N#N$N%N&N'NBNCNDNENFNGNHNINJNjNkNNNNNNNNNNNNNNNNNNNNNNNNNOOOOOO/O0O1O2O jUjg 9 UV jUj[m 9 UVj n 9 UV jU5OJQJmH5CJOJQJmH5CJOJQJmHCJmHmH5CJOJQJmHCMMMMMMNN N N N N NN"N#N$N%N&N'NCNDNENFNGNHNINJNjNkNkNNNNNNNNNNNNNNNNNNNOO3O4OCODOVOkOrOsO~ONNNNNNNNNNOO3O4OCODOVOkOrOsO~OOOOOOOOOOPPPPPP0PEPLPMP_PtP{P|P}P~PPPPPPPPPPP 72O4OCODOkOqOrOsO~OOOOOOOOOOPPPPEPKPLPMPtPzP{P|P~PPPPPPPPPPPPPPmH 5CJOJQJmH5mH5OJQJmHmH5CJOJQJmHCJ mH5CJOJQJmH5CJOJQJmH5CJOJQJmH+~OOOOOOOOOOPPPPPP0PEPLPMP_PtP{P|P}P~PPPPP$PPPPPPPr$. A!"n# $%. A!"n#$%1 0. A!"n#$%0o#U1 0. A!"n#$%0o#U`!zu}y~Xz "`xWIOTAޛQHhƃF=x@Or"Qщ \AzLTbLYfiB󺪫z^! >%%h4ҾTT)9K/I]LzDWW퉤Ɉu];1.>CźW!,KLNWI&ڔAd Jm8`]ym%*3ܠDZưmRlrxs wޤg|)v;`#nIJ9ܤhSlr4g {!u~a| ',9?=,GsmRIg <lr4gD!F\ՔbVNj7ۡorKSuf w#)m`!-'w4䖑>)xteĆ:ꠀTAj5$!QA,Х:DBh"U (bAHr}x5kXJNrΟ}m"Sw:|_*zO;ME߽wooQ<|O-[0dnl)9ZoobELddXL1R"pA#[%]Hai;u@^2( N;Q}1Tz1 z`.62f?e&m% k;SL2 &jG$U%ig]dvMkw=MMSh$kI$IdI]J,:D:Piå.Gk:VZkTiNf:EDߖgu<Εx'tE..].uuDjk~(5tTӏn \RFI)= %߫!GzռZAԪPKHަMVmyWz]sk[ͥ\=QUiAzUGeVL*r jgd%,R=,ydT;k'ܥ_gW>,٭{ BYK_٧_7Ue9F*U=.srʜr^o:N.QTAR:S@Y(! *@Ed2TP ['5km:Y# օh1 AQ뮏Pzo oC` 6X[}Ԗ6K6B_F+6ikKW-0U_鐦q6fl`{ط2ȀV*X X X`3ll~ vN>]|/`| YװY!^bMX#/8GYc!Zp5>S48C]~ ΆhbB4! 7j|Z_B4;=q޸L\_7W顫R6=Moegb1 uMCDAE@Q jB nT*P*Yn C9( e42 8bWKw}8S)GXYYX~Vp+awQO*IQTo3DU7PT|_K'OWCV- :i).[L-ґt:u;6Gg34mNeL:2цxvP*;*68:=`Ci/^F!VG!! " jCMlա*TtЁVA(u!>ܭ.nd@nk0MdpV NӎO`}'t}žζ[:٧vH{Xmvnk5[%ryŖKX^E 6Olyf3& mYJX_)nIRH!KKwK{m%uۭ.:Yd'.-.15~SxxcpOrQ·pf/d .v@&l:? \DIJT5NV ȀRalMQ1dv;a=3AG(cp^w 뛇uuz=^jq?5Gm[?)H SԮ$u,méH'bmԢ@MoK͢I=I',~Y%m >$#iaۥ%}2ʲß$^_$y Nï҆ocF^ኴlm˾igU۳ڳڳ:=p/ܯُ-?NNVTٿx+۝Y=3{,g8T-:u>s~"<32<*:0 U& 3Plyj<HG% Qwѕ%R7YF֠PѤ4jꙉfD!w'RAx Aa(_pB1(r9C $<84w甁SsNOT.7ESh|T4WP|V jCbPX*EYch,_ R *A6 R  / ΣxG=_]X ȧtx\`&̀! s`*L0g`<[t.uY5::BMNhm^M M h;-qК4CBP´ZD <@JOsKp%IHy2<]9<+PըT#`j`I(V5 d էI iҔ.@^tyEk$u!4ӤN.:IITIc%YG`!Cu7eqT@B/Ld}%MdڛĞ(sk,]{)Z 2V`5> z}m.%1s,V1 >DkV\?ʍ\7Mn*7Un4}o*ԯ2,Js&z>O|J9Χn>iO|3̧b> O|-f˧V>O| '6ɧJ>IO|J䓡; My|Ƨ->Q)ON|Z$dAce4'9: >IɁO|ӽ'yO=}_KjOҞ=1{Jdi^On=ziT4>%ΈdJ=)z:D)Г=Ox}$Ao\z /Gp_^5u޵5u۵>C:zZ:zZ:zZp'܍_%e`! hXj hxQ @ }/w#  Az&`L@i=h%() Prӽg^; @tycK4 4,rj2ᅯ7H4e[$NAh4M1|fXΦaC_ߙ+z,^7}d"Ebzb{PLǼa Iẗ[(ubt:C>÷z/=#W>IE٫Vu"u\>7[DdN 0  # A2E hXj!D`! hXj hxQ @ }/w#  Az&`L@i=h%() Prӽg^; @tycK4 4,rj2ᅯ7H4e[$NAh4M1|fXΦaC_ߙ+z,^7}d"Ebzb{PLǼa Iẗ[(ubt:C>÷z/=#W>IE٫Vu"u\>7[Dd gh0  # A2Y'w4䖑>5 `!-'w4䖑>)xteĆ:ꠀTAj5$!QA,Х:DBh"U (bAHr}x5kXJNrΟ}m"Sw:|_*zO;ME߽wooQ<|O-[0dnl)9ZoobELddXL1R"pA#[%]Hai;u@^2( N;Q}1Tz1 z`.62f?e&m% k;SL2 &jG$U%ig]dvMkw=MMSh$kI$IdI]J,:D:Piå.Gk:VZkTiNf:EDߖgu<Εx'tE..].uuDjk~(5tTӏn \RFI)= %߫!GzռZAԪPKHަMVmyWz]sk[ͥ\=QUiAzUGeVL*r jgd%,R=,ydT;k'ܥ_gW>,٭{ BYK_٧_7Ue9F*U=.srʜr^o:N.QTAR:S@Y(! *@Ed2TP ['5km:Y# օh1 AQ뮏Pzo oC` 6X[}Ԗ6K6B_F+6ikKW-0U_鐦q6fl`{ط2ȀV*X X X`3ll~ vN>]|/`| YװY!^bMX#/8GYc!Zp5>S48C]~ ΆhbB4! 7j|Z_B4;=q޸L\_7W顫R6=Moegb1 uMCDAE@Q jB nT*P*Yn C9( e42 8bWKw}8S)GXYYX~Vp+awQO*IQTo3DU7PT|_K'OWCV- :i).[L-ґt:u;6Gg34mNeL:2цxvP*;*68:=`Ci/^F!VG!! " jCMlա*TtЁVA(u!>ܭ.nd@nk0MdpV NӎO`}'t}žζ[:٧vH{Xmvnk5[%ryŖKX^E 6Olyf3& mYJX_)nIRH!KKwK{m%uۭ.:Yd'.-.15~SxxcpOrQ·pf/d .v@&l:? \DIJT5NV ȀRalMQ1dv;a=3AG(cp^w 뛇uuz=^jq?5Gm[?)H SԮ$u,méH'bmԢ@MoK͢I=I',~Y%m >$#iaۥ%}2ʲß$^_$y Nï҆ocF^ኴlm˾igU۳ڳڳ:=p/ܯُ-?NNVTٿx+۝Y=3{,g8T-:u>s~"<32<*:0 U& 3Plyj<HG% Qwѕ%R7YF֠PѤ4jꙉfD!w'RAx Aa(_pB1(r9C $<84w甁SsNOT.7ESh|T4WP|V jCbPX*EYch,_ R *A6 R  / ΣxG=_]X ȧtx\`&̀! s`*L0g`<[t.uY5::BMNhm^M M h;-qК4CBP´ZD <@JOsKp%IHy2<]9<+PըT#`j`I(V5 d էI iҔ.@^tyEk$u!4ӤN.:IITIc%YG`!Cu7eqT@B/Ld}%MdڛĞ(sk,]{)Z 2V`5> z}m.%1s,V1 >DkV\?ʍ\7Mn*7Un4}o*ԯ2,Js&z>O|J9Χn>iO|3̧b> O|-f˧V>O| '6ɧJ>IO|J䓡; My|Ƨ->Q)ON|Z$dAce4'9: >IɁO|  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]_`abcdehwlmnopqrstuvx{|}~Root Entry  @  FL3j B Data C Dc=) TB  C D^ WordDocument)3F ` H< # ObjectPool     13 _9571159161ד1Ole ObjInfoCorelDRAk  !"#$&w *L4\ǷE FMicrosoft Excel ChartBiff8RIFFCDR6vrsnXccmmHPPHj4Cn-[`d;= K7 ŏy333333LISTINFOIKEYICMTLISTdoc mcfgD " *4 @ @? 8c|2LISTXfnttfont#@ AvantGarde Bk BTfont @CommonBulletsLIST<filtfill[fill$,3d@<fillXpC@<2ddfillhdL@<?W2f2fdfill$dUf@<LISTotltoutl\dd@<outl3dd@<outlU??f@<LISTL stltLISTfstylstydZX$4s@DHX\[Default GraphicLIST6stylstyd)' $XLdt| 'c9 V? c5  ncd .0H`x p`Q A@B@B@B' -aaJ@@@!aaJ@@@3,3Default Paragraph TextLISTstylstyd$4 `1@P J@;0,33!Bullet1LISTstylstyd$4 `2@P J@;0,33!Bullet2LISTstylstyd$4 `3@P$$J@;0,33!Bullet3LISTstylstyd$4 `4@P J@;0pC3!Special Bullet1LISTstylstyd$4 `5@P J@;0dL36Special Bullet2LISTstylstyd$4 `6@P J@;0dUU?Special Bullet3LISThstylstyd\Z$D?`<@DZc9 V? c5  ncd@B@B@B' -aaJ@@@3,3Default Artistic TextLISTpageflgsLISTgobjLIST^layrflgsLISTFlgobloda99 (49hddGridLIST`layrflgs LISTHlgobloda;; (4;hddGuidesLIST`layrflgsLISTHlgobloda<< (4<&dDesktopLIST`layrflgsLISTHlgobloda<< (4<dLayer 1LISTpageflgsLISTvgobjLISTPlayrflgsLIST8lgobloda,, ,hddLISTPlayrflgs LIST8lgobloda,, ,hddLISTPlayrflgsLIST8lgobloda,, ,&dLISTblayrflgsLIST8lgobloda,, ,dLIST obj spndflgs usdnLISTlgoblodajj,@DHLfjd.Hv * *33v Ѧv7 Ѧ7 Ѧv7 Q' X Xc Qc Q' X j Xj X X #S #SK XK X X1` !1` ! X X1` DDDH DDDH DDDH DDDH DDDH DDDH ܾ,3LIST\trfltrfdPPPcG?:?PACDRExtents_957115739 x1`1Ole ObjInfo CorelDRA zCDRExtents_957114310 FA1` 1Ole RIFFCDR6vrsnXccmmHPPHj4Cn-[`d;= K7 ŏy333333LISTINFOIKEYICMTLIST<doc mcfgD " *4 @ @? 8c|2LISTXfnttfont#@ AvantGarde Bk BTfont @CommonBulletsLISThfiltfill[fill$@<fill$,3d@<fillXpC@<2ddfillhdL@<?W2f2fdfill$dUf@<LISTotltoutl\dd@<outl3dd@<outlU??f@<LISTL stltLISTfstylstydZX$4s@DHX\[Default GraphicLIST6stylstyd)' $XLdt| 'c9 V? c5  ncd .0H`x p`Q A@B@B@B' -aaJ@@@!aaJ@@@3,3Default Paragraph TextLISTstylstyd$4 `1@P J@;0,33!Bullet1LISTstylstyd$4 `2@P J@;0,33!Bullet2LISTstylstyd$4 `3@P$$J@;0,33!Bullet3LISTstylstyd$4 `4@P J@;0pC3!Special Bullet1LISTstylstyd$4 `5@P J@;0dL36Special Bullet2LISTstylstyd$4 `6@P J@;0dUU?Special Bullet3LISThstylstyd\Z$D?`<@DZc9 V? c5  ncd@B@B@B' -aaJ@@@3,3Default Artistic TextLISTpageflgsLISTgobjLIST^layrflgsLISTFlgobloda99 (49hddGridLIST`layrflgs LISTHlgobloda;; (4;hddGuidesLIST`layrflgsLISTHlgobloda<< (4<&dDesktopLIST`layrflgsLISTHlgobloda<< (4<dLayer 1LISThpageflgsLISTPgobjLISTPlayrflgsLIST8lgobloda,, ,hddLISTPlayrflgs LIST8lgobloda,, ,hddLISTPlayrflgsLIST8lgobloda,, ,&dLIST<layrflgsLIST8lgobloda,, ,dLISTobj spndflgs usdnLISTlgoblodaDD,@DHL@Dd.?bO:NIǷbh.N*HbeǷh.NENNNNENyN4\N4\yyNaXe Y` aXy's^4\m$X|y'LtLtL` R8_\&UJ&؟f[u)ii`+u(d%saU!7`2 F& o''5U'kgwgڐZg& f6eUetK8K8(a\N OG_7\RDROuROT VPM7ZLjTpLtLtVV\LW\ X)Y3Z>ZZMEB VTP^T:ӷSCOUQ\VjXvHZRV/![ Z ZZ#Z$dzeupkfaQY\2SMJJJMSwYc`Zeh Nu Bd`6$`&d`#`` k agc_f]P<&SB"Е   BVVH~LrLrH~H~ DDDH DDDH DDDH DDDH DDDH DDDHDDDDDTDD DDDHLIST\trfltrfdPPPc>??CompObjbObjInfo WorkbookSummaryInformation( Excel.Sheet.89qOh+'08@Xp Mirta BaranovicMirta BaranovicMicrosoft Excel@O՜.+,D՜.+,H PXl t|  ABa=f=hx> 8X1#Arial1#Arial1#Arial1#Arial1#Arial1#Arial1#Arial1#Arial"Kn"\ #,##0;\-"Kn"\ #,##0#"Kn"\ #,##0;[Red]\-"Kn"\ #,##0$"Kn"\ #,##0.00;\-"Kn"\ #,##0.00)$"Kn"\ #,##0.00;[Red]\-"Kn"\ #,##0.00>*9_-"Kn"\ * #,##0_-;\-"Kn"\ * #,##0_-;_-"Kn"\ * "-"_-;_-@_-,)'_-* #,##0_-;\-* #,##0_-;_-* "-"_-;_-@_-F,A_-"Kn"\ * #,##0.00_-;\-"Kn"\ * #,##0.00_-;_-"Kn"\ * "-"??_-;_-@_-4+/_-* #,##0.00_-;\-* #,##0.00_-;_-* "-"??_-;_-@_-                + ) , *   Chart1Sheet1#Sheet2 Sheet3bZ 3  @@  ]br0b0BBIr0bbM MMS0bt00MMM^n00b 00Ԣ0bbb0bbtb0bp4bPercent0]y bΝ0db0ZT0_T0=l0Pe0P0P`?b 0`-6b4b=NJT0e0YT0L0b@Db|0Tb~0BT0dbxbbu0(1T0bbbb|0bbbb04bb 0  A"??3`  `  3d23 M NM4 3QQ ; QQ3_ O    MM<4E4 3QQ ; QQ3_ O   MM<4E4D$% M 3O&Q4$% M 3O&Q4FA3O3 b+MZ! M!  43*#M! M! M! M  43 #M! M43" :dd444ee@@@"@@ @@@e>   A  dMbP?_*+%"0??4U T0bb b b Ľ@ @@@@@@"@"@@"@"@$@@$@&@@@@ @@"@@@@@  @"@   @ @   @@ <""""""***(  p  6NMM?<]`$  AMHP LaserJet III@g ,,@MSUDOHP LaserJet IIId " d,,??3`  `  PH 0(  3d23 M NM4 3QQ ; QQ3_ O    MM<4E4 3QQ ; QQ3_ O   MM<4E4D$% M 3O&Q4$% M 3O&Q4FA3O3 b+MZ! M!  43*#M! M! M! M  43 #M! M43" :dd444eee >@    A  dMbP?_*+%"??U>@  A  dMbP?_*+%"??U>@ DocumentSummaryInformation81TablelSummaryInformation(DocumentSummaryInformation8  FER Zagreb1  Sheet1Sheet2Sheet3Chart1  WorksheetsCharts 6> _PID_GUIDAN{9BF67021-EF56-11D1-91D7-00805FE4896A}Oh+'0x  ӽ'yO=}_KjOҞ=1{Jdi^On=ziT4>%ΈdJ=)z:D)Г=Ox}$Ao\z /Gp_^5u޵5u۵>C:zZ:zZ:zZp'܍_%eeDd 0  # A2zu}y~Xz`!zu}y~Xz "`xWIOTAޛQHhƃF=x@Or"Qщ \AzLTbLYfiB󺪫z^! >%%h4ҾTT)9K/I]LzDWW퉤Ɉu];1.>CźW!,KLNWI&ڔAd Jm8`]ym%*3ܠDZưmRlrxs wޤg|)v;`#nIJ9ܤhSlr4g {!u~a| ',9?=,GsmRIg <lr4gD!F\ՔbVNj7ۡorKSuf w#)m ( 4 @ LX`hp1ssMirta Baranovicirt Dot2.dotanoMirta Baranovic2rtMicrosoft Word 8.0@F#@@t"@t" 8՜.+,D՜.+,4 hp   FER ZagrebxwE  1 Title 6> _PID_GUIDAN{968C115A-876A-11D1-91D7-00805FE4896A}  FMicrosoft Word Document MSWordDocWord.Document.89q [(@(NormalCJmH L@L Heading 1$ & FQ<@&5KHP@P Heading 2'$ & FQ<@& >5<< Heading 3$ & F<@&HH Heading 4$ & F<@& 5OJQJ<< Heading 5 & F<@&CJ@@ Heading 6 & F<@&6CJDD Heading 7 & F<@& CJOJQJHH Heading 8 & F<@&6CJOJQJJ J Heading 9 & F<@&56CJOJQJ<A@<Default Paragraph Font8Y8 Document Map-D OJQJ(U@( Hyperlink>*B*8V@8FollowedHyperlink>*B* +=q%')+?ACEZ\^{} -Ok{9U H   G  a cdfhiS+=q%')+?ACEZ\^{} -Ok{9U #      !"#$%&'()*+,-. 0B2BH  < o"$++M2OP5>ABDLPY%0;EIMkN~OPP689;=?CFHIKMNQRZ4+29ENP7:<@EGJO (*-JLOfh#:::hMWo2$zu}y~Xz2$*s.Uw/q?2$'w4䖑>5_2$Ǟɩwui_t2$ hXj!2$ z,A `www@R<V@ ;(   @ - VTB  C Dc=)cTB  C D3)3F ` 04`H< #     0e0e    Bp CDEF  1 8c8c     ?1  d0u0@Ty2 NP'p<'pA)BCD|E||p   @`0:`H<;    `  1?P:<?     0e0e    B CDEF f3 1 8c8c     ?1  d0u0@Ty2 NP'p<'pA)BCD|E||  @`ph79?   ` 1?87Cx9C     0e0e    BCDEF  1 8c8c     ?1  d0u0@Ty2 NP'p<'pA)BCD|E||@ @`479    `  1?@487H `  C c, f  S H- f   S  +w X@ m & #-4 UT vB C --*T/T u C -*8 0 ` .P6 g# m' 0T d # (d.P03" (T f # )f03P6 )BR l   (m *BR m   (m *HR p # )}M,m-HR rB # )M,m-N s 3  /m0N" t 3  /m0 `  &(4 j# m & -4T a # #a &(p, #T h # *h @/(4 * ` &p#4 k# m& #-4T c # 'c&p#p, 'T i # +i@/p#4 +* @ |,*0< Z  3  @- I2 p`  p" #  |,9$o2N    p! N   @ P" T  #  P" Z  3  @-I2 Z  3  Q@- I2 `  p# #  1309N    ! N    P" N   `" T  # @pp# p`  p" #   3x9N    p! N   @ P" T  #  P" `  p# #  139N    ! N     P"  N    `"  T  # @pp#  `  p# #   03'8N     !  N     P"  N   `" T  # @pp# Z  3 - :*0< ->@ "`'0< TZ  m&   "m&:NB  3 Ǡ).dNB  3  8/NB  3 /1eNB  3 ⭍A r  B.f,k,kXX? #: .H  # -jNB  3 K2  <,vd @ uz ,xB  0&v2 @M &F`  ` # m :   3 r%f,k,kXX?0<P ` %   `f,k,kXX?0<P  `42   P@ 42   @ Hb  # =zjl   c $$ ))?    $NR   3 |R b l   c $" ))?*  "Z   S  A !? H   #  Z  S A  ? Z  S A ? Fl  c $  f Z  `'   m&T  #  `'  TB  C D@`'@TB  C D"@" TB  C D!@! TB  C D %@ % TB  C D@&@@& TB  C D$@$ TB  C D @  TB  C D`'TB  C D``'`TB  C D`'TB  C D`'Z -$   -$'4  W H   # = W 4 ! =  W 4 "  ]!W H # # ]!!W 4 $ !}"W 4 % }" #W H & #  ##W 4 ' W  H ( # W = 4 ) = W 4 *  W ]! 4 + ]!W ! 4 , !W }" H - # }"W # 4 .  #W # 4 /  w H 0 #  = w H 1 # = w 4 2  ]!w H 3 # ]! !w 4 4 ! }"w H 5 # }" #w 4 6  # #w 4 7 w  H 8 # w =  4 9 = w  4 :  w ]! 4 ; ]!w ! 4 < !w }" 4 = }"w # 4 >  #w # H ? #   4 @  = 4 A =  4 B   ]! H C # ]! ! 4 D ! }" 4 E }" # H F #  # # T G # G-$ H H # #-$W 4 I #W -$ H J # # -$w H K # #w -$ H L # # -$ H M # W 4 N W  H O #  w 4 P w  H Q #   Z S 3 /S:`'0< /H c $ ?W  @HV[& tTK!t .$tU+t _Hlt422581340BHCH-1A"B-B.B1B4BQBBBBBBBBBBBBCCCCCCCCCCCCCDDDDDDDD E E>E@EEEEEEEEEFF:FE@EEEEEEEEEFF:F#ya  WaXN/eȗLM7eȗL*Pĕ{RjXNCmȗLvp gsB@*hhCJOJQJo(hhCJOJQJo(hhCJOJQJo(hhCJOJQJo(hho(- hhOJQJo(hhB*OJQJo(P.Y..>...?....  .....  .....  ...... `....... 00........ hhOJQJo(hhCJOJQJo(hhCJOJQJo(hhCJOJQJo(hhCJOJQJo(hhCJOJQJo(hhB*OJQJo( hhOJQJo(hhB*OJQJo(hhCJOJQJo(hhCJOJQJo(hhB*OJQJo(hhCJOJQJo(hhCJOJQJo(hhCJOJQJo(hhCJOJQJo(hhCJOJQJo(hhCJOJQJo(hho(.hho(-hhCJOJQJo(hhCJOJQJo(hhCJOJQJo(hho(-hhCJOJQJo( hhOJQJo(hhCJOJQJo($>#ya,Bq77*gs7/eht vy/73eQ364NRhrXnnHKP`4S  Wa{Rj7Q"CmOM7e5MB6FgP._~!K_E E,;71vpxx6*Pe/"`Mtr @CJOJQJo(F$@3B3BX3B3BL@ABCH @FHJ@GTimes New Roman5Symbol3& Arial5& Tahoma;WingdingsEMonotype Sorts"1h}&&}&&U&f 8x!0dwE4C:\Program Files\Microsoft Office\Templates\Dot2.dot1Mirta BaranovicMirta BaranovicCompObj%j