C1219_Gaps_Rev_1

8/8/2019 C1219_Gaps_Rev_1

http://slidepdf.com/reader/full/c1219gapsrev1 1/5

SmartGrid/AEIC AMI Interoperability Standard Guidelinesfor

ANSI C12.19 / IEEE 1377 / MC12.19 End Device Communications and Supporting Enterprise Devices,Networks and Related Accessories

Outstanding Gaps in the C12.19 Guidelines and/or Standard

C12.19 Guidelines Section GAP Assigned toPAP Group

Mitigation

1 6.2.15 Security Service (optional)

Note: ANSI C12.18 as presently written allowssending passwords in clear text on thecommunication path. This is a serious securityissue. Passwords that are operational viaoptical port access using this protocol shouldnot be operational when accessing the EndDevice via a Telephone/MODEM (such as ANSI

C12.21) or over a network (e.g. ANSI C12.22).

Park this note until C12Standards can be appropriatelyamended per Mike Anderson.Dave recommends identifyingthis as a gap in C12.18 &C12.21 and to notify theappropriate ANSI committee

2 §6.2.1.5“Note: ANSI C12.18 as presently written allowssending passwords in clear text on thecommunication path. This is a serious securityissue. Passwords that are operational viaoptical port access using this protocol shouldnot be operational when accessing the EndDevice via a Telephone/MODEM (such as ANSIC12.21) or over a network (e.g. ANSI C12.22)”

Park this note until C12Standards can be appropriatelyamended per Mike Anderson.This as a gap in C12.18 &C12.21; notify the appropriateANSI committee (ANSI C12SC17 WG4)

3 §8.1.2.10: ( Decade 9 Table, Telephone),

ANSI C12.19 / ANSI C12.22Implement an asynchronousmessage generation to a Head-End device on exception.However, except for schedulingelements in Table 94, there areno network message schedulingtables. This needs to becorrected.

DRAFT Page 1 of 5 August 5, 2010

8/8/2019 C1219_Gaps_Rev_1





Mitigation

4 §8.2.1.1: AMI Meters shall be able to:

1. Provide all interval data upon request.

C12.19 does not have network

schedule tables. Theseguidelines propose the use of the Telephone Call ScheduleTables as means to schedule“Network Calls”, where thetelephone #string is replaced bythe ApTitle of the Head-Endsystem.

Note: Tim Morgan would like tobe able to define interval data bychannel using UUDT. Add to gap

document.5 8.2.4 Event/Message Management & History

LogsNot consistent with ANSI C12.19Need to compare terminologyand see whether these arerelated to ANSI C12.19 EventLogs or not. If they are thenthese should be cast in terms of ST76 EVENT_ENTRY_RCD


8/8/2019 C1219_Gaps_Rev_1





Mitigation

6 Decade 9 Telephone Control Tables

Footnote Section:“† Mandatory (M) if ANSI C12.21 / IEEE 1702 /MC1221 communication protocol isimplemented by the end device. Also, ANSIC12.22 / IEEE 1703 / MC12.22 do not provideend device call originating schedule tables.Table 90, 91 and 94 could be used when theend device implements a call originatingcapability using the network. When callscheduling is used from the network then themembersCTRL_BFLD.PRIMARY_PHONE_NUMBER

andCTRL_BFLD.SECONDARY_PHONE_NUMBERshall be ignored (redefined to be ignored); useTable 123, Exception Report ConfigurationTable’s APTITLE_NOTIFY correspondingelement instead. The APTITLE_NOTIFYelement that is associated with scheduled callsshall be any end device access for read eventcode 7”

ANSI C12.19 / ANSI C12.22

Implement an asynchronousmessage generation to a Head-End device on exception.However, except for schedulingelements in Table 94, there areno network message schedulingtables. This needs to becorrected.measure that need to beconsidered.

7 Default Read ScheduleAMI Meters shall be able to:1. Provide all interval data upon

request.

C12.19 does not have networkschedule tables. Theseguidelines propose the use of

the Telephone Call ScheduleTables as means to schedule“Network Calls”, where thetelephone #string is replaced bythe ApTitle of the Head-Endsystem.GAP: Tim Morgan would like tobe able to define interval data bychannel using UUDT.


8/8/2019 C1219_Gaps_Rev_1





Mitigation

8 8.2.4 Event/Message Management & History

Logs

Not consistent with ANSI C12.19

Need to compare terminologyand see whether these arerelated to ANSI C12.19 EventLogs or not. If they are thenthese should be cast in terms of ST76 EVENT_ENTRY_RCD

9 8.2.6 Internal Clock (:Time Keeping”)AMI Meter's clock/time keeper shall be capableof 1. Being validated with an external time

source at least once per day.

2. Automatically synchronizing during the dailytime validation if meter time is greater thansome configurable value out of synch withthe external time source.

ANSI C12.19 does not providemeans to configure this value. Itassumes that this is a pre-defined hard requirement andtherefore it is a property of the

firmware as mandated by localregulators

10 8.2.10 Meter PerformanceAMI Meter shall be able to:2. During a current limiting mode, allow aservice switch reconnect event to occur following a service switch disconnect event onlyafter a configurable amount of time (e.g. at least1 to 2 minutes) has elapsed since the service

switch disconnect event.

ANSI C12.19 provides for Demand Exclusion only. Is thatvalue common to service re-connect? If so it needs to bestated. Otherwise the termconfigurable needs to berevised.

11 8.2.20 Service Switchd. Success = Disconnect success, or Reconnect success

C12.19 fails to identify acommon means for these outcome codes.


8/8/2019 C1219_Gaps_Rev_1





Mitigation

12 8.2.21 Secure Communications

2. Support a lockout for a configurableamount of time after a failed login/accessattempt.

End Devices may support

access lockout, but the amountof time is not configurable byC12.19, C12.18, C12.21 or C12.22 at this time.

13 8.2.23 Service Limiting Many, if not all the servicelimiting “configuration”requirements are notconfigurable using standardtables or procedures.

14 8.4.10 Decade 9 – Telephone Control Tables

90/91

Decade is implemented only when there is atelephone MODEM interfaces in the EndDevice.

This assumes that a device

implements telephone tables ORnetwork tables. What is one todo when the this is not the case,i.e. both are present?

15 8.4.1.3.1 Display List Line items “Kt” & “Kh” are not inthe standard.

16 8.4.1.3.1 Display List The value Ke is not defined inStandards C12.10, then moveto C12.1, C12.19 & C12.20 asneeded. Defined/used differently

by each Utility. This gap needsto be shared with the PAP10group.

17 8.4.1.3.1 Display List Line items with “Integrated”values are not defined withinC12.19 nor its paralleldocuments.:


Documents

C1219_Gaps_Rev_1