Extended Power Quality Data Interchange Formats
GLOBAL STANDARDExtended Power Quality Data Interchange FormatsPage 1 of 116GSTQ002Rev. 0107/03/2016Extended Power Quality Data Interchange FormatsThis global standard define the formats to exchange PQ measurements and eventsbetween PQI and PQMS, mainly based on extension to international standard formats(particurarly PQDIF according to IEEE 1159.3) or on the adoption of a REST server.Countries’ I&N – NT/RCPElaborated byVerified byApproved byArgentina--Marcelo DenicolaBrasil--Chile--Colombia-Raul ErnestoMoreno ZeaIberiaSee Global I&N – NT Iberia – Solution Development CenterItalyStefano RivaStefano RivaLilia ConsiglioPeru--Roberto LeonidasSanchez VargasRomania--Marius MihaiDomnicuElaborated byVerified byApproved byGlobal I&N – NT/RCPChristian NoceChristian NoceGiorgio Di LemboGlobal I&N – NT Iberia –Solution DevelopmentCenterJose MariaRomero GordonJose MariaRomero GordonMaria AveryFernandezVictor ManuelGalvao MacedoCostHans ChristianRother SalazarCesar AugustoRincon AlvarezThis document is intellectual property of Enel Spa; reproduction or distribution of its contents in any way or by any meanswhatsoever is subject to the prior approval of the above mentioned company which will safeguard its rights underunthe civil andpenal codes.It is for internal Use. Each Country can provide a translation in local language but the official reference document is thisth GS Englishversion.RevisionData0107.03.2016List of modificationsApproved first version
GLOBAL STANDARDExtended Power Quality Data Interchange FormatsPage 2 of 116GSTQ002Rev. 0107/03/2016Index1ACRONYMS . 52NORMATIVE REFERENCES AND BIBLIOGRAPHY . 62.1For all countries . 62.2For EU countries . 62.3For Italy . 63REPLACED STANDARDS . 74APPLICATION FIELDS . 85EXTENDED PQDIF REQUIREMENTS . 95.1Main considerations . 95.2No GPS synchronization . 95.3Memory full . 105.4Voltage anomaly . 105.5Logical channels for PQ events . 105.6Data about PQ parameters . 115.7Logical channels for system events . 115.8Data about system events . 125.9Voltage dip monitoring according to Italian Regulation . 126REST SERVER REQUIREMENTS.136.1URLs . 136.2Variables encoding . 146.3 config upload json . 146.4 output simple. 156.5 input file list . 156.6 output file list . 15
GLOBAL STANDARDExtended Power Quality Data Interchange FormatsPage 3 of 116GSTQ002Rev. 0107/03/20166.7 input files download . 156.8 input file delete. 166.9 input data periodic . 166.10 output data periodic jsontput data periodic json . 176.11 output data periodic csv . 176.12 input data events . 176.13 output data events . 186.14 input data waveformput data waveform . 196.15 output data waveform json . 196.16 output data waveform csv . 206.17 output data zipcomtrade . 206.18 input data delete . 207MISCELLANEOUS.227.1Amendement . 228ANNEXES .238.1Annex A: “data source definition record” examples for PQ events .238.2Annex B: “observation record” examples . 568.3Annex C: “data source definition record” examples for system events .578.4Annex D: List of variables . 58TablesTable 1 – Rest Server Urls Functionalities . 13Table 2 – Rest Server Config Upload Json . 14Table 3 – Rest Server Output Simple . 15Table 4 – Rest Server Input File List . 15Table 5 – Rest Server Output File List . 15
GLOBAL STANDARDExtended Power Quality Data Interchange FormatsPage 4 of 116GSTQ002Rev. 0107/03/2016Table 6 – Rest Server Input Files Download . 16. 16Table 7 – Rest Server Input Files Delete. Input Files DeleteTable 8 – Rest Server Input Data Periodic . 16Table 9 – Rest Server Input Data Periodic Json . 17Table 10 – Rest Server Output Data Periodic Csv . 17Table 11 – Rest Server Input Data Events . 18Table 12 – Rest Server Output Data Events1 . 18Table 13 – Rest Server Output Data Events2 . 19Table 14 – Rest Server Input Data Waveform . 19Table 15 – Rest Server Output Data Waveform Json . 19Table 16 – Rest Server Output Data Waveform Csv . 20Table 17 – Rest Server Input Data Delete . 20Table 18 – List Of Variables . 58
GLOBAL STANDARDExtended Power Quality Data Interchange Formats1ACRONYMS PQPower Quality PQIPower Quality Instrument according to IEC 62586-1 M3GModem GSM – GPRS – UMTS (2G 3G) RTURemote Terminal Unit GPSGlobal Positioning System GPSRGPS Receiver Time Syncro Receiver PQMSPower Quality Management System DNP3Distributed Network Protocol RESTRepresentational State Transfer COMTRADECommon format for Transient Data Exchange for power systems DNSDomain Name System DHCPDynamic Host Configuration Protocol DHCPv6Dynamic Host Configuration Protocol (IPv6) JSONJavaScript Object Notation CSVComma-separatedseparated values TCPTransmission Control Protocol HTTPHypertext Transfer Protocol HTTPSHypertext Transfer Protocol SecurePage 5 of 116GSTQ002Rev. 0107/03/2016
GLOBAL STANDARDExtended Power Quality Data Interchange Formats2Page 6 of 116GSTQ002Rev. 0107/03/2016NORMATIVE REFERENCESRENCES AND BIBLIOGRAPHYBIBLIOGRAAll the references are intended in the last revision or amendement.2.1For all countriesIEC 61000-4-30Electromagnetic compatibility (EMC) – Part 4-30:30: Testing and measurement techniques – Powerquality measurement methods.IEEE 1159.3IEEE Recommended Practice for the Transfer of Power Quality Data.DataIEEE C37.111IEEE Standard Common Format for Transient Data Exchange (COMTRADE) for Power SystemsISO 8601:2004Data elements and interchange formats – Information interchange – Representation of dates andtimesECMA-404(October 2013)RFC 4180(October 2005)The JSON Data Interchange FormatCommon Format and MIME Type for Comma-SeparatedComma Separated Values (CSV) FilesRFC 791Internet Protocol, Version 4 (IPv4)RFC 2460Internet Protocol, Version 6 (IPv6)Appnote,1APPNOTE.TXZIP File Format Specification, PKWARE Inc., September 2012NMEA 0183National Marine Electronics Association electrical signal requirements, data transmissionprotocol and time, and specific sentence formatsforma for a 4800-baudbaud serial data busISO/IEC 7810Identification cards - Physical characteristicsGSTQ003Power Quality Management SystemGSTQ001Power Quality InstrumentIEC 60870-5-104Telecontrol equipment and systems - Part 5-104: Transmission protocols - Network access forIEC 60870-55-101 using standard transport profilesIEC 62749Assessment of power quality - Characteristics of electricity supplied by public networks2.2For EU countriesEN 501602.3Voltage characteristics of electricity supplied by public distribution systems.systemsFor ItalyRSE 12004159[1]ARG/elt 198/11Specifiche tecnico-funzionalitecnico funzionali delle apparecchiature di monitoraggio della qualità della tensioneper le reti MT.R. Chiumeo, M. de Nigris, L. Garbero, C. Gandolfi, L. Tenti, E. Carpaneto, “Implementation of aNew Method for an Improved Voltage Dips Evaluation by the Italian Power Quality MonitoringSystem in Presence of VT Saturation Effects”, International Conference on Renewable Energiesand Power Quality (ICREPQ’10), Granada (Spain), 23rdd to 25th March, 2010.Testo integrato della qualità dei servizi di distribuzione e misura dell’energia elettrica per ilperiodo di regolazione 2012-20152012
GLOBAL STANDARDExtended Power Quality Data Interchange Formats3Page 7 of 116GSTQ002Rev. 0107/03/2016REPLACED chiatura di monitoraggio della qualita’ della tensione delle reti elettriche MT
GLOBAL STANDARDExtended Power Quality Data Interchange Formats4Page 8 of 116GSTQ002Rev. 0107/03/2016APPLICATION FIELDSThe PQ monitoring architecture can be made by central system and distributed instruments.The PQI (according to GSTQ001) will be installed in the MV or LV distribution grid in order to meausureall the relevant PQ parameters. The relevant PQ parameters are defined in IEC 61000-4-30,61000IEC 62749and EN 50160.The installation will be a substation or another indoor premise in a country where one or more utilitiesare under Enel control.The PQMS is the Power Quality Management System (according to GSTQ003),GSTQ003 including dataacquisition from PQI.The PQI must include RTU functionalities in order to allow data exchange (according to this GS) with thePQMS.
GLOBAL STANDARDExtended Power Quality Data Interchange Formats5Page 9 of 116GSTQ002Rev. 0107/03/2016EXTENDED PQDIF REQUIREMENTSPQI and PQMS must exchange the data about the relevant PQ parameters fully compliant with PQDIF(according to IEEE 1159.3),, additional requests are present in this chapter.5.1Main considerationsIn the PQDIF, the ID QT MAGDURTIME is used for the managementgement of PQ events, by a starttimestamp,tamp, a duration and a characteristics value (the minimum in the case of dips/interruptions, themaximum in case of swells, etc .);.) ID QT MAGDURTIME is defined by the tag tagQuantityTypeIDtagQuantiinthe "data source definition record”record for each input channel.So, tagQuantityTypeID ID QT MAGDURTIME has three data series (see also par.5.5):par.a. Timestamp;b. Event duration;c. Characteristics value.In order to identify the PQ parameter (dips, interruption, swell,, flicker, thd, etc.),etc.) the tagDisturbanceCategoryID is used in the ''observation records".In the following the term "Voltage Li" (i 1, .,. 4) identify the voltage measured by the i-th channel, whichcorresponds to the i-thth phase-to-neutralphasevoltage in the case of 4-wirewire connection, or to the phase-tophasephase voltage in the case of 3-wire3connection.In the implementation of the PQDIF for eventeven management two approach are allowed:d. Too hold a definition of channels independent for the two types of connection (4 wires phase-tophaseneutral or 3 wires phase-to-phase);phasee. Too use a single definition of channels (corresponding to the type of wiring actually in use).In both cases the specification of the phase must be properly appropriate: this in view of the fact thatvoltage events are, however, recognized only for the type of wiring in use.Although not strictly related to the measurement of the PQ parametrs,, the system events, related to thediagnosis of abnormal conditions of the equipment, contribute to the correct interpretation of themeasurements made by the device.Following crucial events must be approached as follow:followf. NO GPS SYNCHRONIZATION;SYNCHRONIZATIOg. MEMORY FULL;h. VOLTAGE ANOMALY.5.2No GPS synchronizationdue to a recognition of a no synchronized time base (typically on start beforebefengaging the GPS orabsence/interruptioninterruption connection to GPSR) the PIMS must record an event of "time basebof sync",identifying the instant of start and the duration of this condition.conditionIf the condition of no synchronization continues for a long time (for example, for a permanent failure ofthe GPS receiver), in order to signal this condition, (power quality events can take placeplin suchcondition), the analyzer records the event of "NO GPS SYNCHRONIZATION" at the permanence in thiscondition for 4 hours, and, it reiterated this periodic registration until the restoration of the synchronism ofthe time base. This avoids recognizerecognize the event of "no synchronism" at the end of the abnormal condition(in the case of permanent fault to the GPS receiver could during for days), and then invalidate theelaborations on the origin of voltage dips already carried out. The organization of informationin"NO GPSSYNCHRONIZATION” in the format IEEE 1159.3 "PQDIF" uses the standard type of greatnessID QT MAGDURTIME, defined in the definition tag tagQuantityTypeID in the relative channel in the"data source definition record". At this type of channelchannel ("System Event") are associated three series,which respectively specify the instant of occurrence (time stamp), the event duration and the amplitude
GLOBAL STANDARDExtended Power Quality Data Interchange FormatsPage 10 of 116GSTQ002Rev. 0107/03/2016(not significant and conventionally equal to 1 (one)). The series of data associated with the events in'"observation records" specify the nature of the event through the tag tagDisturbanceCategoryID, but thestandard does not provide a value applicable to this type of event, so is necessary create onespecifically (ID TIME NO SYNC).5.3Memory fullThis event occurs when the internal data storage occupation overcome the 80% of filling, identifying theinstant of happening. The organization of information " MEMORY FULL” in the format IEEE 1159.3"PQDIF" uses the standard type of greatness ID QT MAGDURTIME, defineddefinin the definition tagtagQuantityTypeID in the relative channel in the "data source definition record". At this type of channel("System Event") are associated three series, which respectively specify the instant of occurrence (timestamp), the event durationration and the amplitude (not significant and conventionally equal to 2 (two)). Theseries of data associated with the events in '"observation records" specify the nature of the eventthrough the tag tagDisturbanceCategoryID, but the standard does not provideprovide a value applicable to thistype of event, so is necessary create one specifically (ID MEMORY FULL).5.4Voltage anomalyThis event is due the persistence (at least 6 hours) of the voltage measurement in the range 10% Vnfor one or two channels of the PQI and the voltage measuring over the range 30% Vn for theremaining channels (two or one, respectively). Identifying the instant of start and the duration of thiscondition. After the first recording (after 6 hours of the occurrence of the fault condition),condition the event isrepeated at most once a day, for the duration of the fault condition. Note that the absence of voltage onall channels of the apparatus is not considered an anomaly voltage channels. Furthermore, themanagement of this event is significant only if the device is configured for three-phasethreemeasures, whilenot provided for single-phasephase measures. The organization of information "VOLTAGE ANOMALY” in theformat IEEE 1159.3 "PQDIF" uses the standard type of greatness ID QT MAGDURTIME, defined in thethdefinition tag tagQuantityTypeID in the relative channel in the "data source definition record". At this typeof channel ("System Event") are associated three series, which respectively specify the instant ofoccurrence (time stamp), the event duration andand the amplitude (not significant and conventionally equalto 3 (three)). The series of data associated with the events in '"observation records" specify the nature ofthe event through the tag tagDisturbanceCategoryID, but the standard does not provide a valueapplicable to this type of event, so is necessary create one specifically (ID VOLTAGE ANOMALY).5.5Logical channels for PQ eventsThe following input channels are mapped in the “data source definition record”:record”a.b.c.d.e.f.g.Voltage events: up to 4 channels (L1, L2, L3, L4) for events of dips,s, interruptions,interruption swells etc.;Frequency events:: 1 channel for under/overunder/frequency events;Imbalance events: 1 channel for over-imbalanceoverevents;Flicker events: 3 channels (L1, L2,L2 L3) per over-Plt/ Pst events;Voltage THD events: 3 channels (L1,(L2, L3) for over-Thd events;Current events: 3 channelshannels (L1, L2, L3) for overcurrent events;Events of digital inputs: 12 channels (one for each digital input) for event of input variation.variationThe following tags are defineded for the channels:h.i.j.k.tagChannelName that is a character string;tagPhaseID;tagQuantityTypeID ID QT MAGDURTIME;ID QT MAGDURTIMEtagQuantityMeasuredID.Three data series (tagValueTypeID) are available for each channel:l. ID SERIES VALUE TYPE TIME: timestamp event;eventm. ID SERIES VALUE TYPE VAL: characteristics value;n. ID SERIES VALUE TYPE DURATION: event duration.
GLOBAL STANDARDExtended Power Quality Data Interchange FormatsPage 11 of 116GSTQ002Rev. 0107/03/2016With reference to tagPhaseID:o. for the voltage events on L1, L2 and L3, tagPhaseID ID PHASE AN/BN/CN in the case of 4-wire4configuration, and/or tagPhaseID ID PHASE AB/CB/CA in thehe case of 3-wire3configuration;p. for the voltage events on L4, tagPhaseID IID PHASE RES;q. for channels of frequency and imbalance events takes the values ID PHASE NONEr. for channels of L1-L2-L3L3 current events takes the values of ID PHASE AN/BN/CNID PHASE AN/BN/CNs. for channels of digital inputs events takes values ID PHASE GENERAL 1, ,ID PHASE GENERAL 12With reference to tagQuantityMeasuredID:tagQuantityMeasuredIDt.for channels of events voltage, frequency, imbalance, Voltage THD events takes the value ofID QM VOLTAGEu. forr the channels of the current events takes the value of ID QM CURRENTv. for channels of digital events takes the value of ID QM STATUSPar. 8.1 shows an example of “data source definition record” mapping with the definition of channels forevent management.5.6Data about PQ parametersPower quality events are stored in “observation record” as instances of the channels previously defined.The tag tagDisturbanceCategoryID is used to qualify the nature of the event in the type of channel:a.b.c.d.e.f.g.h.i.j.k.l.m.n.o.ID DISTURB 1159 SHORTDUR INSTANT SAG: voltage dips 500msID DISTURB 1159 SHORTDUR MOMENT SAG: voltage dips 500ms and 3secID DISTURB 1159 SHORTDUR TEMP SAG: voltage dips 3sec3sec and 60se 60secID DISTURB 1159 LONGDUR SAG: voltage dips 60secID DISTURB 1159 SHORTDUR MOMENT INTERRUPT: interruption 3 secID DISTURB 1159 SHORTDUR TEMP INTERRUPT: interruption 3 sec and 60 secID DISTURB 1159 LONGDUR INTERRUPT: interruption 60 secID DISTURB 1159 SHORTDUR INSTANT SWELL: voltage swell 500 msID DISTURB 1159 SHORTDUR MOMENT SWELL: voltage swell 500 and 3 secID DISTURB 1159 SHORTDUR TEMP SWELL: voltage swell 3 sec and 60 secID DISTURB 1159 LONGDUR SWELL: voltage swell 60 secID DISTURB 1159 SHORTDUR:DISTURB 1159 SHORTDUR: rapid voltage changesID DISTURB 1159 POWERFREQVARIATION: overover and under-frequencyfrequency eventsID DISTURB 1159 IMBALANCE: events of over-imbalanceoverID DISTURB 1159 VOLTAGEFLUCTUATION: events of over-flickeroverPltThe following categories off disturbance are defined (not present in the IEEE 1159.3 standard):p. ID INRUSH CURRENT (in-rush(icurrent events): static const GUID ID INRUSH CURRENT {0xdec995f, 0x2f83, 0x4302, { 0xbc, 0x62, 0x29,0x67, 0x4c, 0x53, 0xb, 0x87 } };q. ID LOW TO HIGHGH INPUT (digital( gital input events from logic state off to on):on static const GUIDID LOW TO HIGH INPUT { 0x1cfe23bd, 0xac40, 0x416b, { 0x84, 0xc9,0x11, 0x64, 0x36, 0x8f,0xdc, 0x0b } };r. ID HIGH TO LOW INPUT (digital(digital input events from logic state on to off):off static const GUIDID HIGH TO LOW INPUT { 0x89f6b3cf, 0xe2f5, 0x4ac9, { 0xa2, 0x42,0xaf, 0xe5, 0x53, 0x5f,0xba, 0x4e } };Par. 8.2 shows an example of recorded event as an instance of a series of type ID QT MAGDURTIME.5.7Logical channels for system eventsIs defined the following logical channel "System Event" in the “data source definition record” for themanagement of system events, with the following tags:a. tagChannelName: CHAR1: "System Event"
GLOBAL STANDARDExtended Power Quality Data Interchange FormatsPage 12 of 116GSTQ002Rev. 0107/03/2016b. tagPhaseID: ID PHASE NONEc. tagQuantityTypeID: ID QT MAGDURTIMEd. tagQuantityMeasuredID: ID QM STATUSTo each channel is associated threethree series with the following typologies (tagValueTypeID):e. ID SERIES VALUE TYPE TIME: event timestampf. ID SERIES VALUE TYPE VAL: conventionally set equal to 1 for "NO GPS SYNCHRONIZATION",2 for event "MEMORY FULL", 3 for event "VOLTAGE ANOMALY"g. ID SERIES VALUE TYPE DURATION:VALUE TYPE DURATION: event duration (seconds).5.8Data about system eventsThe system events are stored in the “observation record” as instances of the the channel previouslydefined. The tag tagDisturbanceCategoryID is used to qualify within the type of the channel concernedthe nature of the event, by the following category of event that has been defined specifically, as notpresent in the standard IEEE 1159.3:a. ID TIME NO SYNC (nono GPS synchronization):synchronization static const GUID ID TIME NO SYNC {0x59402026, 0x7a96, 0x44d3, {0xb1, 0x99, 0x66, 0x9b, 0x51, 0xa5, 0xd0, 0xf4} };b. ID MEMORY FULL (memoryemory full): static const GUID ID MEMORY FULL {0x08a90717, 0x6263,0x4119, {0xae, 0xb6, 0x1e, 0x60, 0x2d, 0x17, 0xc8, 0x13} };c. ID VOLTAGE ANOMALY (voltage(vanomaly): static const GUID ID VOLTAGE ANOMALY {0x79678710, 0x b45
Data elements and interchange formats times ECMA-404 (October 2013) The JSON Data Interchange Format RFC 4180 (October 2005) Common Format and MIME Type for Comma RFC 791 Internet Protocol, Version 4 (IPv4) RFC 2460 Internet Protocol, Version 6 (IPv6) Appnote,1 APPNOTE.TX ZIP File Format Specification, PKWARE Inc., September 2012 NMEA 0183
2 15 ' 1 2 15 ' 2 15 ' notes: mainline 1 typ. lighting limits interchange 215' lighting limits interchange lighting limits interchange lighting limits interchange lighting limits interchange 3. 2. 1. interchange lighting limits n.t.s. reports indicates. of what that the lighting justification the mainline will be illuminated regardless
2. Diamond interchange: Diamond interchange is a popular form of four-leg interchange found in the urban locations where major and minor roads crosses. The important feature of this interchange is that it can be designed even if the major road is relatively narrow. A typical layout of diamond interchange is shown in figure. Diamond interchange 3.
diverse computer systems has exacerbated the data interchange problems. To date, most of the attempts to minimize the interchange problem revolve around the establishment of standard formats. Individual disciplines and projects have solved their data interchange problems by defining formats specialized to the applications.
Extended Power Quality Data Interchange Formats Extended Power Quality Data Interchange Formats This global standard define the between PQI and PQMS, mainly based on extension to
Technical changes from the OMF Interchange Specification Version 2.0 are marked with change bars. For More Information This section tells where you can get more information about OMF Interchange and OMF software. There is a form at the end of this document that describes how you can register as an OMF Interchange Sponsor, Partner, or Champion.
6.2 writing the extended essay 7. formal presentation of the extended essay 7.1 the length of the extended essay 7.2 title 7.3 abstract 7.4 contents page 7.5 illustrations 7.6 bibliography 8. how the extended essay is assessed? 9. extended essay assessment criteria checklist 10. extended essay tutees and supervisors
A Data types library describing the types for data elements; A Messages library describing each interchange format as a hierarchy of data blocks. The three libraries persist the current data interchange format modeled with the help of the meta-model. This corresponds to the data structure representation creational pattern [Spinellis, 2000].
CORE SKILLS FOR PSYCHOTHERAPY. by Ian Rory Owen. 1. It is easy to define what therapy is not. It is not lecturing, nor moralizing, patronizing nor befriending. It is not the use of counselling skills by non-mental health professionals in interviewing or management. Some clinical psychologists describe their work as making "clinical psychology interventions", rather than counselling or .
