Static Meters presentation on meters ppt

Static Meters presentation on meters ppt

1. Static Energy Meter Features, Testing & Failure analysis as per IS 15959 (Part 1): 2011

2. IS 13779: 1999 - ac Static Watthour Meters, Class 1and 2 - Specification IS 14697: 1999 - ac Static Transformer Operated Watthour & Var -hour Meters, Class 0.2 S, 0.5 S & 1.0 S . Specification IS 15884: 2010 - Alternating Current D irect C onnected S tatic P repayment M eters for Active Energy (Class 1 and 2) - Specification IS 15959 (Part 1): 2011 - Data Exchange for Electricity meter reading, tariff & Load control - Companion Specification (Static Energy Meter)

3. Meter Categories S. No Server Category Description 1 A Energy Accounting & Audit Metering 2 B Boundary / Bank / Ring / ABT Metering 3 C1 HT (PT / CT) Operated & LT (CT Operated) Consumer meters 4 C2 3 Phase 4 Wire Whole current meters 5 C3 Single Phase Whole Current Meters Cat A Meter - Consider as subset of cat C Meter.

4. Connectivity Scheme B/w Meter/Server & Client

5. Physical Requirements P1 - Electrical Port (RS232 / RS485) - used for remote access P2 - Optical Port complying hardware specification as per IS / IEC 62056 - 21 - for local access Both P1 & P2 shall support: 3 layer connection Oriented COSEM / HDLC Profile (Default Baud rate of 9600) 4 Byte & 1 byte addressing Cat C3 - at least one communication port (i.e. P2) All Other Categories meters - Minimum two communication port (P1 & P2)

6. Client – Server model and communication Protocols

7. Association Properties S. No Feature Public Client (PC) Meter Reader (MR) Utility Settings (US) 1 SAP address (Client, Server) (16, 1) (32, 1) (48,1) 2 Application context - Basic security Long Names (LN) with out ciphering LN with out ciphering LN with out ciphering 3 Application context - Basic security Not Applicable LN - Ciphered LN - Ciphered 4 Sign on authentication mechanism Lowest Level Low Level High Level 5 Services required Get Get, Get with block transfer, Selective access & Set Get, Set, Action, Get with block transfer, Set with block transfer & Selective access In MR - Set services is applicable for RS485 meters (RS 485 Device address)

8. Mandatory Objects Logical Device Name: Maximum length of 16 Characters (first 3 letter – Manufacturer's 3 letter code) Manufacturer's 3 letter code – administrated by the FLAG Association, In co- operation with the DLMS / UA Current Association (0.0.40.0.e.255) All association (PC, MR & US) shall contain following in addition to mandatory objects: Meter’s real time clock Meter Serial Number

9. Required Input Details for Smart Meter Testing Meter under test should be tested for configured metering mode submitted by the customer Conformance Test Information (CTI) Functional Test Information (FTI) Tamper logic conditions with neat circuit diagram Communication cables (Optical & Electrical)

10. Conformance to DLMS / COSEM (IEC 62056) “The primary purpose of conformance testing is to increase the probability that different implementations are able to interwork .” The main characteristics of the DLMS/COSEM I t covers COSEM interface object model and the DLMS/COSEM application layer, including the security suites (Right now security suite 0). T esting can be performed using either the 3-layer, CO, HDLC based profile or using the TCP/IP based profile. If 3-layer , CO, HDLC based profile is used with direct HDLC connection - HDLC data link layer is also tested CTT automatically generates the Test Result necessary for the Certification

11. Conformance to DLMS / COSEM (IEC 62056) Conformance test information (CTI ): Information provided by the supplier / implementer of an IUT stating the capabilities and options that have been implemented and additional information necessary to executable test cases. C onformance testing : “IUT is a conforming to the relevant specification(s) implementation” P rotocol conformance test report (PCTR ): G iving the details of the testing carried out for a particular protocol, including the identification of the abstract test cases

12. Protocol conformance test report (PCTR): Identification (Manufacturer name, Flag id, Type & S. No) Communication profile :HDLC Application context names :LONG_NAMES Security mechanisms: : NO_SECURITY,LOW_LEVEL_SECURITY ACSE and xDLMS features: :GET,SELECTIVE_ACCESS, SERVICE_SPECIFIC_BLOCK_TRANSFER Security features: :Not Collected Logical device(s) found: SAP = 1 is “XXXXXXXXXXXXXXXXXXXXXXXXXXXX" COSEM classes tested :1,3,4,7(1),8,15,17,20,22,23(1) COSEM classes found but not tested:(none) Type Total Skipped Inapplicable Inconclusive Passed Failed HDLC 36 3 33 APPL 47 13 34 COSEM 422 2 32 388 SYMSEC All (No association with a ciphered context supporting the required services)

13. SNRM / UA Object list download Association Properties Security (Lowest, Low level & High level) ToU Settings Billing period & counter General Purpose parameters (Name plate & programmable parameters) Instantaneous parameters & profile Block load profile parameters Billing profile parameters Daily load profile parameters Event condition (Voltage, Current, Other, Control , Non rollover, Power, Transaction) Selective access by range & entry Simultaneous Operation Test Cases

14. Test Cases SNRM / UA: SNRM - Set Normal Response Mode; UA - Unnumbered acknowledgement Information Size: D efault value of the Maximum information field length parameter is 128 . The maximum value of the information field length is 2030 bytes Window Size: The default value of the Window size is 1 . The maximum value is 7 . Object list down load : Both One & Four byte addressing (PC, MR & US) Verifying the OBIS codes for parameters & profiles. Some Failure Case: Some of the OBIS codes for parameters are missing & no proper access rights for the parameter.

15. Test Cases Association Properties: PC, MR & US To check the conformance services Sign on mechanism Verifying mandatory objects Some Failure Case / Deviating stand.: Conformance services are not as per stand. Simultaneous Properties : (PC, MR & US) Meter not required to allow more than one association to be open at any one time. If P1 & P2 accessed simultaneously, P2 shall have high priority (after sending DM message to HOST). Some Failure Case / Deviating stand.: Higher priority given to P1

16. Test Cases Security: Sign on authentication for PC, MR & US Security setup – IC 64 (0.0.43.0.e.255) Lowest Level Security: PC Open access without any authentication at sign on Low Level Security: MR Write access through US Modify - Positive test case - Negative test case - Restore High Level Security: US Write access through US Modify - Positive test case - Negative test case - Restore

17. Test Cases Security: Sign on authentication for PC, MR & US Security setup – IC 64 (0.0.43.0.e.255) Lowest Level Security: PC Open access without any authentication at sign on Low Level Security: MR Write access through US Modify - Positive test case - Negative test case - Restore High Level Security: US Write access through US Modify - Positive test case - Negative test case - Restore

18. Instantaneous Parameters Instantaneous Parameters: Each Parameter is a separate entity OBIS code for each parameter is identified as per DLMS / COSEM protocol Snap Shot of Instantaneous Parameters: 1.0.94.91.0.255 Read attribute 2 of each object Scaler Profile: 1.0.94.91.3.255 Capturing Scaler unit Profile having only one entry Not required to update periodically Power & Energy values verified at UPF, 0.5 lag & 0.8 lead

19. Instantaneous Parameters Some failure cases observed during testing: Signed Reactive Power (+ Lag; - Lead) Apparent Power, kVA Three Phase Power factor, PF Cumulative Billing / Tamper / programming count Maximum demand, kW & kVA Billing date (default - first day of the month & time shall be 00:00 h) Wrong scalar unit kVAH 2 = kWh 2 + kVARh 2 for Lag & UPF condition kVAH 2 = kWh 2 for Lead condition

20. Block Load Profile Parameters Block Load Profile Parameters: IC 7 (1.0.99.1.0.255) Capture period set through 1.0.0.8.4.255 Capture time 15 mins (22 days) / 30 mins (45 days) - Some utilities - 5 mins For Cat B Meters - capture time 15 mins (by default) Storage time can be varies - No. of Parameters Scaler Profile: 1.0.94.91.4.255 Capturing Scaler unit Profile having only one entry Not required to update periodically

21. Block Load Profile Parameters Zero Padding: Full day defined as 24 h (from midnight 00 h to next mid night 00 h) Power down for full day - No need to record or store the block load profile If small duration meter is power up (boot up and record the power up event) - it should store & return the block load profile for the full day Some failure cases observed during testing : Wrong scalar unit Energy updating with wrong value

22. Daily Load Profile Parameters Daily Load Profile Parameters: IC 7 (1.0.99.2.0.255) Data capture as a profile at end of 24 h Parameters logged at midnight 00 h Capture period set through 1.0.0.8.5.255 Storage time same as Block load. Storage time for Cat B – 22 days Scaler Profile: 1.0.94.91.5.255 Capturing Scaler unit Profile having only one entry Not required to update periodically

23. Daily Load Profile Parameters Some failure cases observed during testing : Wrong scalar unit Values logged at other than midnight (00 h) / first power up condition Profile entries will be erased after PCP Energy updating with wrong value / No updating

24. Billing Profile Parameters Billing Profile Parameters: IC 7 (1.0.98.1.0.255) Cash box to utilities Billing action controlled by billing dates Data stored up to (6 +1) / (12+1) billing cycles Capture period set to zero Scaler Profile: 1.0.94.91.6.255 Capturing Scaler unit Profile having only one entry Not required to update periodically

25. Billing Profile Parameters Some failure cases observed during testing: Wrong scalar unit Billing power ON duration in minutes Energies are updated in wrong time zone Capturing MD, kW or MD, kVA (After DIP) Energy will be updated in only one time zone (after activation new activity calendar) System power factor for billing period

26. Selective access by range & by entry Selective Access: As per Clause 11 of IS 15959 (Part 1): 2011 By Range: Block Load profile parameters Daily load profile parameters By Entry: Billing profile parameters Events (Voltage, Current, Power, Transaction, Other, & Control) Some failure cases observed during testing : Only one entry will be available

27. ToU Settings Activity calendar for Time zones: IC 20 (0.0.13.0.0.255) Time switches for tariffs based on a season, week, & day profile (tree) & schedules (at least one season, one week & one day profile - Present) Activity calendar shall be updated by writing to the passive calendar Causing all changes (Calendar) to be come effective simultaneously Script identifiers: 1 to 16 - Tariff rate registers 17 to 32 - Maximum demand registers Transaction Event: Activity Calendar: 155 (Immediate has to occur after write action)

28. ToU Settings Some failure cases observed during testing : Increment in programming counter Transaction event Tree structure not followed Mismatch in day profile / weak profile / season profile No calendar format (Date & Time) - DDMMYYYY; HH:MM If multiple seasons are present (No proper format followed in side meter) Bill is not generated after activation of ToU settings (for Cat C3 Meters) Clear format should be followed with out any mismatch in profiles in side the meter & same thing should reflect in FTI file

29. Billing Period Counter Billing Period Counter: (0.0.0.1.0.255) Cumulative value since installation DLMS data type unsigned 32 bit Some failure cases observed during testing : No increment in billing period counter after bill generation Wrong data type

30. Billing Period Billing Period: (0.0.0.1.1.255) Cumulative value since installation DLMS data type unsigned 8 bit Maximum billing period will be 6+1 or 12+1 Some failure cases observed during testing : No increment in billing period after bill generation Wrong data type

31. Name Plate Details Name Plate Details: IC 7 (0.0.94.91.10.255) Observations noticed during testing: Meter serial number Meter year of manufacture Internal CT / PT ratio Meter type & Category FW version number All the above parameters are not matching with FTI provided to CPRI / Meter Physical Name plate / In side meter

32. Programmable parameters Programmable parameters Real time clock, date & time - 151 Demand Integration Period (DIP) – 152 (NA for Cat B meters) Profile Capture Period (PCP) - 153 Single action schedule for billing dates - 154 Activity calendar for time zones etc. - 155 RS485 device address – 156 (applicable for meter with RS485 ports) Programming of any parameter - Increment in cumulative programming counter Some failure cases observed during testing: Increment in cumulative programming counter

33. Programmable parameters Real time clock, date & time: (0.0.1.0.0.255; IC 8) - Event Id: 151 RTC time format HH:MM:SS (by default) Programmed: Forward; Reverse; & Restore Some failure cases / deviation observed during testing: Increment in cumulative programming counter Allow only in forward direction Allow only in particular block period Allowed only in time format

34. Programmable parameters Demand Integration Period (DIP): (1.0.0.8.0.255; IC 1) - Event Id: 152 Not applicable for Cat B meters Unit is in ‘second’ Programmed: 3600/1800/900 Default; Modified; & Restore Some failure cases / deviation observed during testing: Unit is not in ‘second’ No cumulative programming counter increment Values are not capture with new period in Billing profile & Instantaneous profile & parameters

35. Programmable parameters Profile Capture Period (PCP): (1.0.0.8.4.255; IC 1) - Event Id: 153 Related with block load profile Unit is in ‘second’ Programmed: 3600/1800/900 (Some utilities asking 300) Default; Modified; & Restore Some failure cases / deviation observed during testing: Unit is not in ‘second’ No cumulative programming counter increment Data will be cleared & stamping with new capture period Both 15 mins & 30 mins data are available

36. Programmable parameters Single action schedule for billing dates: (0.0.15.0.0.255; IC 22) - Event Id: 154 To generate bill by schedule Some failure cases / deviation observed during testing : No cumulative programming counter increment Some meters with even month / odd month billing (Clearly mention in FTI) Meters with only one bill will be generated in a day Meter support billing dates from 1 to 28 Billing date (default - first day of the month & time shall be 00:00 h )

37. Event conditions, profile & parameters Event conditions, profile & parameters: For Three Phase: Voltage related - 1 to 12 (NA for Single Phase meter) Missing Potential, Low voltage, High voltage & Voltage unbalance Current Related - 51 to 68 CT Open, CT reverse, CT Bypass, Over current & Current unbalance Power Failure - 101 & 102 (Meter Power off & on condition) Transaction Events - 151 to 156 RTC, DIP, PCP & Single action schedule for billing dates, Activity calendar for Time zones etc.

38. Event conditions, profile & parameters Other related – 201 to 206 Influence of magnet, Neutral disturbance & Low power factor Non roll over - 251 Meter cover open For Single Phase Meters: Voltage related - Not applicable Current related - Earth loading (69 & 70) Power , Transaction related & Non roll over - Same as Three Phase Other related: Influence of magnet, Neutral disturbance & Single wire operation (207 & 208)

39. Event conditions, profile & parameters Some failure cases / deviation observed during testing : Increment in cumulative tamper count Capture parameters No proper tamper condition provided in FTI file Wrong event stamping time for tamper (Mostly in non rollover)

40. For utilities Samples: Supported events are not uniform for all manufactures Event conditions are not uniform in FTI provided for testing Profile parameters are not uniform in load survey parameters No clarity in Energy updating: kVAH 2 = kWh 2 + kVARh 2 for Lag & UPF condition kVAH 2 = kWh 2 for Lead condition

41. References IS 15959 (Part 1): 2011 IS 15959 (Part 2): 2016 IS 15959 (Part 3): 2017 IS 16444 (Part 1): 2015 IS 16444 (Part 2): 2017 DLMS Colour books (White, Yellow, Blue & Green)

42. Any Queries? Thank you..)