I E C 61 68 -3 ® Edition 2.0 201 7-04 I N TE RN ATI ON AL S TAN D ARD N ORM E I N TE RN ATI ON ALE colour i n sid e Ap pl i cati on i n te g rati on at e l ectri c u ti l i ti es – S ys te m i n te rfaces for d i s tri bu ti on m an ag em en t – P art 3: I n te rface for n etwork ope rati on s I n té g rati on d ' appl i cati on s pou r l es servi ces él e ctri q u es – I n te rfaces s ys tèm e pou r l a g es ti on d e l a d i s tri bu ti on – IEC 61 968-3:201 7-04(en-fr) P arti e : I n terface pou r l ' e xpl oi tati on d u rés eau T H I S P U B L I C AT I O N I S C O P YRI G H T P RO T E C T E D C o p yri g h t © I E C , G e n e v a , S wi tz e rl a n d All rights reserved Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either IEC or IEC's member National Committee in the country of the requester If you have any questions about I EC copyright or have an enquiry about obtaining additional rights to this publication, please contact the address below or your local I EC member National Committee for further information Droits de reproduction réservés Sauf indication contraire, aucune partie de cette publication ne peut être reproduite ni utilisée sous quelque forme que ce soit et par aucun procédé, électronique ou mécanique, y compris la photocopie et les microfilms, sans l'accord écrit de l'IEC ou du Comité national de l'IEC du pays du demandeur Si vous avez des questions sur le copyright de l'IEC ou si vous désirez obtenir des droits supplémentaires sur cette publication, utilisez les coordonnées ci-après ou contactez le Comité national de l'IEC de votre pays de résidence IEC Central Office 3, rue de Varembé CH-1 21 Geneva 20 Switzerland Tel.: +41 22 91 02 1 Fax: +41 22 91 03 00 info@iec.ch www.iec.ch Ab ou t th e I E C The I nternational Electrotechnical Commission (I EC) is the leading global organization that prepares and publishes I nternational Standards for all electrical, electronic and related technologies Ab o u t I E C p u b l i ca ti o n s The technical content of IEC publications is kept under constant review by the IEC Please make sure that you have the latest edition, a corrigenda or an amendment might have been published I E C Catal og u e - webstore i ec ch /catal og u e The stand-alone application for consulting the entire bibliographical information on IEC International Standards, Technical Specifications, Technical Reports and other documents Available for PC, Mac OS, Android Tablets and iPad I E C pu bl i cati on s s earch - www i ec ch /search pu b The advanced search enables to find IEC publications by a variety of criteria (reference number, text, technical committee,…) It also gives information on projects, replaced and withdrawn publications E l ectroped i a - www el ectroped i a org The world's leading online dictionary of electronic and electrical terms containing 20 000 terms and definitions in English and French, with equivalent terms in additional languages Also known as the International Electrotechnical Vocabulary (IEV) online I E C G l os sary - s td i ec ch /g l oss ary 65 000 electrotechnical terminology entries in English and French extracted from the Terms and Definitions clause of IEC publications issued since 2002 Some entries have been collected from earlier publications of IEC TC 37, 77, 86 and CISPR I E C J u st Pu bl i s h ed - webstore i ec ch /j u stpu bl i sh ed Stay up to date on all new IEC publications Just Published details all new publications released Available online and also once a month by email I E C C u stom er S ervi ce C en tre - webstore i ec ch /csc If you wish to give us your feedback on this publication or need further assistance, please contact the Customer Service Centre: csc@iec.ch A propos d e l 'I E C La Commission Electrotechnique I nternationale (IEC) est la première organisation mondiale qui élabore et publie des Normes internationales pour tout ce qui a trait l'électricité, l'électronique et aux technologies apparentées A propos d es pu bl i cati on s I E C Le contenu technique des publications IEC est constamment revu Veuillez vous assurer que vous possédez l’édition la plus récente, un corrigendum ou amendement peut avoir été publié Catal og u e I E C - webstore i ec ch /catal og u e Application autonome pour consulter tous les renseignements bibliographiques sur les Normes internationales, Spécifications techniques, Rapports techniques et autres documents de l'IEC Disponible pour PC, Mac OS, tablettes Android et iPad Rech erch e d e pu bl i cati on s I E C - www i ec ch /search pu b La recherche avancée permet de trouver des publications IEC en utilisant différents critères (numéro de référence, texte, comité d’études,…) Elle donne aussi des informations sur les projets et les publications remplacées ou retirées E l ectroped i a - www el ectroped i a org Le premier dictionnaire en ligne de termes électroniques et électriques Il contient 20 000 termes et dộfinitions en anglais et en franỗais, ainsi que les termes équivalents dans langues additionnelles Egalement appelé Vocabulaire Electrotechnique International (IEV) en ligne G l oss re I E C - s td i ec ch /g l ossary 65 000 entrées terminologiques électrotechniques, en anglais et en franỗais, extraites des articles Termes et Dộfinitions des publications IEC parues depuis 2002 Plus certaines entrées antérieures extraites des publications des CE 37, 77, 86 et CISPR de l'IEC I E C J u st Pu bl i s h ed - webstore i ec ch /j u stpu bl i sh ed Restez informé sur les nouvelles publications IEC Just Published détaille les nouvelles publications parues Disponible en ligne et aussi une fois par mois par email S ervi ce Cl i en ts - webstore i ec ch /csc Si vous désirez nous donner des commentaires sur cette publication ou si vous avez des questions contactez-nous: csc@iec.ch I E C 61 68 -3 ® Edition 2.0 201 7-04 I N TE RN ATI ON AL S TAN D ARD N ORM E I N TE RN ATI ON ALE colour i n sid e Ap pl i cati on i n te g rati on at e l ectri c u ti l i ti e s – S ys te m i n te rfaces for d i s tri bu ti on m an ag em en t – P art 3: I n terface for n e twork ope rati on s I n tég rati on d ' appl i cati on s pou r l es servi ce s é l e ctri q u es – I n terfaces s ys tèm e pou r l a g es ti on d e l a d i s tri bu ti on – P arti e : I n terface pou r l ' e xpl oi tati on d u rés eau INTERNATIONAL ELECTROTECHNICAL COMMISSION COMMISSION ELECTROTECHNIQUE INTERNATIONALE ICS 33.200 ISBN 978-2-8322-4084-7 Warn i n g ! M ake su re th at you ob tai n ed th i s pu bl i ca ti on from an au th ori zed d i s tri bu tor Atten ti on ! Veu i l l ez vou s as s u rer q u e vou s avez ob ten u cette p u b l i cati on vi a u n d i s tri bu teu r ag ré é ® Registered trademark of the International Electrotechnical Commission –2– I EC 61 968-3: 201 © I EC 201 CONTENTS FOREWORD I NTRODUCTI ON Scope Norm ative references Terms, definitions and abbreviated term s 1 Terms and definitions 1 Abbreviated terms 1 Reference and I nformation M odels 1 General approach to network operations 1 Reference Model I nterface Reference Model 4 Network operations functions and com ponents Static I nform ation Model 5 General 5 Classes related to network operations 5 Network operations m essage payloads 5 General 5 OperationsConfiguration payload General 2 Message payload MeasurementsAndControls payload General Measurement 3 Control Message payload TemporaryNetworkChanges payload 21 General 21 Message payloads 22 5 SwitchingPlan payload 27 5 General 27 5 Message payload 28 OperationalTags payload 36 General 36 Message payload 37 TroubleTicket payload 38 Incident payload 39 General 39 Message payload 41 Outage payload 42 General 42 Message payload 44 Metering message payloads 45 1 EndDeviceEvent 45 MeterReading 45 I EC 61 968-3: 201 © I EC 201 –3– 1 Work message payloads 46 1 WorkOrder 46 SwitchingOrder 47 General 47 2 Message payload 48 TroubleOrder 49 General 49 Message payload 50 OutageSchedule 51 General 51 Message payload 52 Document Conventions 55 UML diagrams 55 Message payload definitions 55 General 55 2 Mandatory versus Optional 55 Synchronous versus Asynchronous Messages 55 Message exchanges 55 Annex A (informative) U se Cases 56 A General 56 A FLI SR 56 A 2.1 Overview 56 A 2.2 FLI SR for SCADA-detected outage, SCADA switching 56 A 2.3 FLI SR for trouble call and AMI outage, crew switching 58 A Planned outage 62 A 3.1 Planned outage for maintenance – Manual process 62 A 3.2 Planned outage for maintenance – Crew switching 63 Annex B (normative) XM L Schem as for m essage payloads 68 B General 68 B Incidents m essage payload 68 B MeasurementsAndControls message payload 75 B OperationalTags message payload 82 B OperationsConfig m essage payload 85 B OutagesAndFaults message payload 87 B OutageSchedules message payload 96 B SwitchingOrders message payload 1 B SwitchingPlans message payload 23 B TemporaryNetworkChanges m essage payload 40 B 1 TroubleOrders message payload 50 Bibliograph y 60 Figure – I EC 61 968-3 Scope Figure – I EC 61 968-3 Reference Model Figure – OperationsConfiguration m essage payload Figure – MeasurementsAndControls –4– I EC 61 968-3: 201 © I EC 201 Figure – MeasurementsAndControls m essage payload Figure – MeasurementsAndControls message payload, AnalogValue detail 20 Figure – MeasurementsAndControls message payload, Setpoint ( AnalogControl ) detail 21 Figure – Tem porary N etwork Changes 22 Figure – TemporaryNetworkChanges message payload 22 Figure – TemporaryNetworkChanges m essage payload, Clamp detail 23 Figure 1 – TemporaryNetworkChanges m essage payload, Cut detail 24 Figure – TemporaryNetworkChanges m essage payload, EnergySource Details 25 Figure – TemporaryNetworkChanges m essage payload, Ground details 26 Figure – TemporaryNetworkChanges m essage payload, Jumper Details 27 Figure – Switching Plan 28 Figure – SwitchingPlans message payload 29 Figure – SwitchingPlans message payload, SafetyDocument detail 30 Figure – SwitchingPlan message payload, ClearanceAction detail 31 Figure – SwitchingPlan message payload, GenericAction detail 32 Figure 20 – SwitchingPlan message payload, EnergySourceAction detail 32 Figure 21 – SwitchingPlan message payload, CutAction detail 33 Figure 22 – SwitchingPlan message payload, GroundAction detail 34 Figure 23 – SwitchingPlan message payload, JumperAction detail 34 Figure 24 – SwitchingPlan message payload, SwitchingAction detail 35 Figure 25 – SwitchingPlan message payload, TagAction detail 36 Figure Figure Figure Figure 26 27 28 29 – Tags 37 – OperationalTags m essage payload 38 – Trouble Ticket 39 – Incident 40 Figure 30 – Incident m essage payload 41 Figure 31 – Outage 42 Figure Figure Figure Figure Figure Figure Figure Figure Figure Figure 32 33 34 35 36 37 38 39 40 41 – OutagesAndFaults message payload 44 – End Device Event 45 – Meter Reading 46 – Work Order 47 – Switching Order 48 – SwitchingOrder message payload 49 – Trouble Order 50 – TroubleOrder message payload 51 – Outage Schedule 52 – OutageSchedule message payload 53 I EC 61 968-3: 201 © I EC 201 –5– Figure Figure Figure Figure Figure 42 – OutageSchedule message payload, PlannedOutages detail 54 A – FLI SR for SCADA-Detected Outage, SCADA Switching 57 A – FLI SR for trouble call and AM I outage, crew switching 60 A – Planned outage for maintenance – Manual process 63 A – Planned outage for m aintenance, crew switching 65 Table Table Table Table Table Table – Business Functions and Abstract Components – I nterpretation of Network Operations Business Functions – Classes related to network operations A – Message Flow for FLI SR SCADA-Detected Outage, SCADA Switching 58 A – Message flows for FLI SR for trouble call and AM I outage, crew switching 61 A – Message flows for planned outage for maintenance, crew switching 66 –6– I EC 61 968-3: 201 © I EC 201 INTERNATI ONAL ELECTROTECHNI CAL COMMISSI ON AP P L I C AT I O N I N T E G R AT I O N AT E L E C T RI C U T I L I T I E S – S YS T E M I N T E RF AC E S F O R D I S T RI B U T I O N M AN AG E M E N T – P a rt : I n te rfa c e fo r n e tw o rk o p e ti o n s FOREWORD ) The I nternati on al Electrotechni cal Com m ission (I EC) is a worl d wid e organi zation for stan dardization com prisin g all n ation al el ectrotechnical comm ittees (I EC National Comm ittees) The object of I EC is to prom ote internati onal co-operation on all q uestions concerni ng stand ardi zati on in the el ectrical an d electronic fi elds To this en d an d i n additi on to other acti vities, I EC publish es I nternational Stan dards, Techn ical Specificati ons, Technical Reports, Publicl y Avail abl e Specificati ons (PAS) an d Guides (h ereafter referred to as “I EC Publication(s)”) Th ei r preparation is entrusted to tech nical comm ittees; any I EC National Comm ittee interested in th e subj ect dealt with m ay partici pate in this preparatory work I nternational, governm ental an d n on governm ental organ izations liaising with th e I EC also partici pate i n th is preparation I EC collaborates closel y with the I ntern ational Org ani zation for Stand ardi zation (I SO) in accordance with conditions determ ined by agreem ent between th e two organi zati ons 2) The form al decisions or agreem ents of I EC on technical m atters express, as n early as possible, an i nternati onal consensus of opi nion on the rel evant subjects since each technical com m ittee has representati on from all interested I EC N ational Com m ittees 3) I EC Publications have the form of recom m endations for intern ational use an d are accepted by I EC Nati onal Com m ittees in that sense While all reasonable efforts are m ade to ensure that th e tech nical content of I EC Publications is accu rate, I EC cann ot be h eld responsi ble for the way in which th ey are used or for an y m isinterpretation by an y en d u ser 4) I n order to prom ote intern ational u niform ity, I EC National Com m ittees und ertake to apply I EC Publications transparentl y to the m axim u m extent possible i n their national an d regi on al publications Any divergence between an y I EC Pu blication and the correspondi ng national or regi on al publicati on sh all be clearl y in dicated in the latter 5) I EC itself d oes not provi de an y attestation of conform ity I ndepend ent certificati on bodies provide conform ity assessm ent services and, in som e areas, access to I EC m arks of conform ity I EC is not responsi ble for any services carri ed out by ind ependent certification bodi es 6) All users shou ld ensure that th ey h ave the l atest editi on of thi s publicati on 7) No liability shall attach to I EC or its directors, em ployees, servants or ag ents inclu din g in divi du al experts an d m em bers of its technical com m ittees and I EC N ation al Com m ittees for any person al i njury, property d am age or other dam age of any n atu re whatsoever, whether d irect or indirect, or for costs (includ i ng leg al fees) and expenses arisi ng out of the publ ication, use of, or relian ce upon, this I EC Publication or any oth er I EC Publications 8) Attention is drawn to th e N orm ative references cited in this publication Use of the referenced publ ications is indispensable for the correct applicati on of this publication 9) Attention is drawn to the possibility that som e of the elem ents of this I EC Publication m ay be th e subject of patent rig hts I EC shall not be held responsibl e for identifyi ng any or all such patent ri ghts I nternational Standard I EC 61 968-3 has been prepared by I EC technical comm ittee 57: Power system s management and associated inform ation exchange The text of this standard is based on the following documents: FDI S Report on votin g 57/1 81 0/FDI S 57/1 841 /RVD Full information on the voting for the approval of this I nternational Standard can be found in the report on voting indicated in the above table This docum ent has been drafted in accordance with the I SO/I EC Directives, Part This second edition cancels and replaces the first edition published in 2004 I t consti tutes a technical revision I EC 61 968-3: 201 © I EC 201 –7– This edition includes the following significant technical changes with respect to the previous edition: a) b) c) d) e) f) g) h) i) j) k) Replaced M easurem ent list with Measurement and Controls Replaced OperationalRestriction with Tag Replaced OutageRecord with Outage Replaced SafetyDocument with ClearanceDocum ent Replaced SwitchingSchedule with SwitchingOrder Added SwitchingPlan Added Tem porary N etwork Change Added TroubleTicket Added I ncident Added TroubleOrder Added use cases and sequence diagram s I n this standard, the following print types are used: – tokens: in arial black type A list of all parts of the I EC 61 968 series, under the general title: Application integration at electric utilities – System interfaces for distribution management can be found on the I EC website The com mittee has decided that the contents of this document will remain unchanged until the stability date indicated on the I EC website under "http://webstore iec ch" in the data related to the specific document At this date, the document will be • • • • reconfirmed, withdrawn, replaced by a revised edition, or am ended I M P O RT AN T th at it – Th e co n tai n s u n d e rs t a n d i n g c o l o u r p ri n t e r of ' col ou r i n si d e' c o l o u rs i ts wh i ch c o n ten ts logo a re U s e rs on th e co ve r p ag e c o n s i d e re d sh ou ld to t h e re fo re o f th i s be p ri n t p u b l i c ati o n u s e fu l th i s fo r i n d i cates th e d ocu m e n t c o rre c t u si n g a –8– I EC 61 968-3: 201 © I EC 201 INTRODUCTION The purpose of this part of I EC 61 968 is to define a standard for the integration of network operations system s with each other and other systems and business functions within the scope of I EC 61 968 The specific details of comm unication protocols those system s employ are outside the scope of this part of I EC 61 968 I nstead, this part of I EC 61 968 will recognize and m odel the general capabilities that can be potentiall y provided by network operations system s I n this way, this part of I EC 61 968 will not be im pacted by the specification, development and/or deploym ent of next generation network operations system s, either through the use of standards or proprietary means The I EC 61 968 series of standards is intended to facilitate inter-application integration as opposed to intra-application integration I ntra-application integration is aimed at program s in the same application system , usuall y comm unicating with each other using m iddleware that is em bedded in their underlying runtim e environment, and tends to be optim ised for close, real time, synchronous connections and interactive request/repl y or conversation comm unication models Therefore, these inter-application interface standards are relevant to loosely coupled applications with more heterogeneity in languages, operating system s, protocols and management tools This series of standards is intended to support applications that need to exchange data every few seconds, m inutes, or hours rather than waiting for a nightl y batch run This series of standards, which are intended to be implemen ted with m iddleware services that exchange messages am ong applications, will complem ent, not replace utility data warehouses, database gateways, and operational stores As used in I EC 61 968, a distribution management system (DMS) consists of various distributed application com ponents for the utility to m anage electrical distribution networks These capabilities include m onitoring and control of equipm ent for power delivery, managem ent processes to ensure system reliability, voltage m anagem ent, dem and-side management, outage m anagement, work m anagement, autom ated mapping and facilities managem ent Standard interfaces are defined for each class of applications identified in the interface reference model (I RM), which is described in I EC 61 968-1 – 31 – I EC 61 968-3: 201 © I EC 201 Single phase of a multi-phase switch when its attributes might be different per phase. The attribute tells if the switch is considered closed when used as input to topology processing. Phase of this SwitchPhase on the side with terminal sequence number equal Should be a phase contained in that terminal’s phases attribute. Phase of this SwitchPhase on the side with terminal sequence number equal Should be a phase contained in that terminal’s Terminal.phases attribute. Atomic switching step; can be part of a switching step group, or part of a switching plan. Free text description of this activity. Actual date and time of this switching step. Date and time when the crew was given the instruction to execute the action; not applicable if the action is performed by operator remote control. Kind of action on temporary equipment (such as cut, jumper, ground, energy source). Place the jumper (close) or the cut (open). I EC 61 968-3: 201 © I EC 201 – 31 – Remove the jumper (open) or the cut (close). An AC electrical connection point to a piece of conducting equipment Terminals are connected at physical connection points called connectivity nodes. Represents the normal network phasing condition. If the attribute is missing three phases (ABC or ABCN) shall be assumed. Product of RMS value of the voltage and the RMS value of the quadrature component of the current. Electrical voltage, can be both AC and DC. Resistance (real part of impedance). Product of RMS value of the voltage and the RMS value of the in-phase component of the current. Unit of length Never negative. Reactance (imaginary part of impedance), at rated frequency. Phase angle in radians. – 31 – I EC 61 968-3: 201 © I EC 201 B.1 Charge utile de message TroubleOrders Tangible resource of the utility, including power system equipment, various end devices, cabinets, buildings, etc For electrical network equipment, the role of the asset is defined through PowerSystemResource and its subclasses, defined mainly in the Wires model (refer to IEC61 970-301 and model package IEC61 970::Wires) Asset description places emphasis on the physical characteristics of the equipment fulfilling that role. Master resource identifier issued by a model authority The mRID is unique within an exchange context Global uniqueness is easily achieved by using a UUID, as specified in RFC 41 22, for the mRID The use of UUID is strongly recommended. For CIMXML data files in RDF syntax conforming to IEC 61 970-552 Edition , the mRID is mapped to rdf:ID or rdf:about attributes that identify CIM object elements. Coordinate reference system. Master resource identifier issued by a model authority The mRID is unique within an exchange context Global uniqueness is easily achieved by using a UUID, as specified in RFC 41 22, for the mRID The use of UUID is strongly recommended. For CIMXML data files in RDF syntax conforming to IEC 61 970-552 Edition , the mRID is mapped to rdf:ID or rdf:about attributes that identify CIM object elements. A Uniform Resource Name (URN) for the coordinate reference system (crs) used to define 'Location.PositionPoints'. An example would be the European Petroleum Survey Group (EPSG) code for a coordinate reference system, defined in URN under the Open Geospatial Consortium (OGC) namespace as: urn:ogc:def:uom:EPSG::XXXX, where XXXX is an EPSG code (a full list of codes can be found at the EPSG Registry web site http://www.epsg-registry.org/) To define the coordinate system as being WGS84 (latitude, longitude) using an EPSG OGC, this attribute would be urn:ogc:def:uom:EPSG::4236. A profile should limit this code to a set of allowed URNs agreed to by all sending and receiving parties. The name is any free human readable and possibly non unique text naming the object. I EC 61 968-3: 201 © I EC 201 – 31 – Description of a problem in the field that may be reported in a trouble ticket or come from another source It may have to with an outage. Master resource identifier issued by a model authority The mRID is unique within an exchange context Global uniqueness is easily achieved by using a UUID, as specified in RFC 41 22, for the mRID The use of UUID is strongly recommended. For CIMXML data files in RDF syntax conforming to IEC 61 970-552 Edition , the mRID is mapped to rdf:ID or rdf:about attributes that identify CIM object elements. Set of spatial coordinates that determine a point, defined in the coordinate system specified in 'Location.CoordinateSystem' Use a single position point instance to desribe a point-oriented location Use a sequence of position points to describe a line-oriented object (physical location of non-point oriented objects like cables or lines), or area of an object (like a substation or a geographical zone – in this case, have first and last position point with the same values). Zero-relative sequence number of this point within a series of points. X axis position. Y axis position. (if applicable) Z axis position. Current status information relevant to an entity. Date and time for which status 'value' applies. Reason code or explanation for why an object went to the current status 'value'. Pertinent information regarding the current 'value', as free form text. – 31 – I EC 61 968-3: 201 © I EC 201 Status value at 'dateTime'; prior status changes may have been kept in instances of activity records associated with the object to which this status applies. General purpose street and postal address information. Post office box. Postal code for the address. Status of this address. Street detail. Town detail. Street details, in the context of address. First line of a free form address or some additional address information (for example a mail stop). (if applicable) Second line of a free form address. (if applicable) Third line of a free form address. I EC 61 968-3: 201 © I EC 201 – 31 – (if applicable) In certain cases the physical location of the place of interest does not have a direct point of entry from the street, but may be located inside a larger structure such as a building, complex, office block, apartment, etc. (if applicable) Utilities often make use of external reference systems, such as those of the townplanner's department or surveyor general's mapping system, that allocate global reference codes to streets. Name of the street. Designator of the specific location on the street. Prefix to the street name For example: North, South, East, West. Suffix to the street name For example: North, South, East, West. Number of the apartment or suite. Type of street Examples include: street, circle, boulevard, avenue, road, drive, etc. True if this street is within the legal geographical boundaries of the specified town (default). Town details, in the context of address. Town code. Name of the country. – 31 – I EC 61 968-3: 201 © I EC 201 Town name. Town section For example, it is common for there to be 36 sections per township. Name of the state or province. Information about a particular location for various forms of work. The description is a free human readable text describing or naming the object It may be non unique and may not correlate to a naming hierarchy. (if applicable) Direction that allows field crews to quickly find a given asset For a given location, such as a street address, this is the relative direction in which to find the asset For example, a streetlight may be located at the 'NW' (northwest) corner of the customer's site, or a usage point may be located on the second floor of an apartment building. The name is any free human readable and possibly non unique text naming the object. All assets at this location. Coordinate system used to describe position points of this location. Main address of the location. Sequence of position points describing this location, expressed in coordinate system 'Location.CoordinateSystem'. I EC 61 968-3: 201 © I EC 201 – 31 – Secondary address of the location For example, PO Box address may have different ZIP code than that in the 'mainAddress'. Charge utile de message TroubleTickets Organisation receiving services from service supplier. Master resource identifier issued by a model authority The mRID is unique within an exchange context Global uniqueness is easily achieved by using a UUID, as specified in RFC 41 22, for the mRID The use of UUID is strongly recommended. For CIMXML data files in RDF syntax conforming to IEC 61 970-552 Edition , the mRID is mapped to rdf:ID or rdf:about attributes that identify CIM object elements. Conditions for notifying the customer about the changes in the status of their service (e.g., outage restore, estimated restoration time, tariff or service level change, etc.) Type of contact (e.g., phone, email, etc.). Value of contact type (e.g., phone number, email address, etc.). Earliest date time to call the customer. Latest date time to call the customer. – 31 – I EC 61 968-3: 201 © I EC 201 Trigger for this notification. Description of a problem in the field that may be reported in a trouble ticket or come from another source It may have to with an outage. Master resource identifier issued by a model authority The mRID is unique within an exchange context Global uniqueness is easily achieved by using a UUID, as specified in RFC 41 22, for the mRID The use of UUID is strongly recommended. For CIMXML data files in RDF syntax conforming to IEC 61 970-552 Edition , the mRID is mapped to rdf:ID or rdf:about attributes that identify CIM object elements. The description is a free human readable text describing or naming the object It may be non unique and may not correlate to a naming hierarchy. The name is any free human readable and possibly non unique text naming the object. Hazardous situation associated with an incident Examples are line down, gas leak, fire, etc. Master resource identifier issued by a model authority The mRID is unique within an exchange context Global uniqueness is easily achieved by using a UUID, as specified in RFC 41 22, for the mRID The use of UUID is strongly recommended. For CIMXML data files in RDF syntax conforming to IEC 61 970-552 Edition , the mRID is mapped to rdf:ID or rdf:about attributes that identify CIM object elements. The description is a free human readable text describing or naming the object It may be non unique and may not correlate to a naming hierarchy. The name is any free human readable and possibly non unique text naming the object. Status of this hazard. I EC 61 968-3: 201 © I EC 201 – 31 – Kind of trigger to notify customer. Notify customer if estimated restoration time changes. Notify customer that a crew has been dispatched to investigate the problem. Notify customer for the first time that estimated restoration time is available. Notify customer of planned outage. Notify customer when power has been restored. Current status information relevant to an entity. Date and time for which status 'value' applies. Reason code or explanation for why an object went to the current status 'value'. Pertinent information regarding the current 'value', as free form text. Status value at 'dateTime'; prior status changes may have been kept in instances of activity records associated with the object to which this status applies. Kind of trouble reporting. Trouble call received by customer service representative. – 320 – I EC 61 968-3: 201 © I EC 201 Trouble reported by email. Trouble reported through interactive voice response system. Trouble reported by letter. Trouble reported by other means. Master resource identifier issued by a model authority The mRID is unique within an exchange context Global uniqueness is easily achieved by using a UUID, as specified in RFC 41 22, for the mRID The use of UUID is strongly recommended. For CIMXML data files in RDF syntax conforming to IEC 61 970-552 Edition , the mRID is mapped to rdf:ID or rdf:about attributes that identify CIM object elements. Name of the author of this document. Date and time the trouble has been reported. The description is a free human readable text describing or naming the object It may be non unique and may not correlate to a naming hierarchy. A first responder on site such as police, fire department etc. Indicates how the customer reported trouble. Date and time this trouble ticket has been resolved. I EC 61 968-3: 201 © I EC 201 – 321 – Trouble code (e.g., power down, flickering lights, partial power, etc). Customer for whom this trouble ticket is relevant. All hazards reported with this trouble ticket. Notification for this trouble ticket. – 322 – I EC 61 968-3: 201 © I EC 201 Bibliographie I EC 61 968-4, Application integration at electric utilities – System interfaces for distribution management – Part 4: Interfaces for records and asset management (disponible en anglais seulement) I EC 61 968-5, Application integration at electric utilities – System interfaces for distribution management – Part 5: Interfaces for operational planning and optimisation (disponible en anglais seulement) I EC 61 968-6, Application integration at electric utilities – System interfaces for distribution management – Part 6: Interfaces for maintenance and construction (disponible en anglais seulement) I EC 61 968-7, Application integration at electric utilities – System interfaces for distribution management – Part 7: Interfaces for network expansion planning (disponible en anglais seulem ent) I EC 61 968-8, Application integration at electric utilities – System interfaces for distribution management – Part 8: Interfaces for customer support (disponible en anglais seulement) I EC 61 968-9, Intégration d'applications pour les services électriques – Interfaces système pour la gestion de distribution – Partie 9: Interfaces pour le relevé et la commande des compteurs I EC 61 968-1 , Intégration d'applications pour les services électriques – Interfaces système pour la gestion de distribution – Partie 11: Extensions du modèle d'information commun (CIM) pour la distribution I EC 61 968-1 3, Application integration at electric utilities – System interfaces for distribution management – Part 13: CIM RDF Model exchange format for distribution (disponible en anglais seulem ent) I EC 62361 -1 00 , Gestion des systèmes de puissance et échanges d'informations associés – Interopérabilité long terme – Partie 00: Mapping des profils CIM avec le schéma XML _ _ À l'étude INTERNATIONAL ELECTROTECHNICAL COMMISSI ON 3, rue de Varembé PO Box 31 CH-1 21 Geneva 20 Switzerland Tel: + 41 22 91 02 1 Fax: + 41 22 91 03 00 info@iec.ch www.iec.ch