Open AMI Network

1
Open AMI Network

• 10/22/08

2
Standards Overview
AMI-SEC
Utility Systems
Data Collection Systems
Meter-Specific Networks
MDM System
Wide Area Networks
HAN
Network Operations 61968-3
OMS 61968-3
MDM Or MDUS 61968-9
Data Collection 61968-9
Planning Scheduling 61968-5
GIS 61968-4
Open HAN 1.0
Control Configuration 61968-9
MDM 61968-9
AMI Network ???
WMS 61968-6
Load Mgmt. 61968-9
Load Control 61968-9
MDUS 61968-9
Meter Data Comm. C12.19 C12.22
Meter Maintenance 61968-9
CIS 61968-8
AMI-SEC
3
Consumers Energys Service Territory

• 1.8 Million Electric Meters
• 1.6 Million Gas Meters
• 1 Million gas meters in non Consumers Energys
  service territory

4
AMI Observations

• Differences between systems
• Proprietary Communication Technology
• System logging and auditing
• Device registration device dependant
• Collector
• Meter
• Substation metering
• Other (smart grid devices, etc)
• Network management interfaces
• Outage reporting
• Troubleshooting
• Monitoring performance
• System configuration and upgrades

5
AMI Observations (Cont.)

• AMI communication vendors are not interoperable
  for maintenance and management
• Meter
• Collector/Access Point/Mesh Gate/Take out
  point/Cell Relay/Tower Gateway Base Station/ Base
  Station
• HAN ESP interface managed and implemented
  different between vendors

6
AMI-Network TF Proposal

• Define the devices and well defined points of
  interoperability within the AMI network for
  maintenance
• Define the benefits of interoperability between
  AMI network maintenance components to utilities
• Sharing backhauls
• Gas AMR meters
• Water AMR meters
• Hybrid AMI systems
• Point to Point and mesh and PLC

7
Proposed TF Scope

• Evaluate existing Maintenance Use Cases
• Define New Maintenance Use Cases
• Define System Functional Requirements for AMI
  meters to the AMI head end for maintenance/lifecyc
  le purposes
• Identify areas within an AMI network that are
  viable for maintenance interoperability
• Scope is outside of OpenHAN and the
  Zigbee/Homeplug efforts
• Input from the Group???

8
Evaluate Existing Use Cases

• SCE use cases
• S1 AMI system recovers after power outage,
  communications or equipment failure
• U1 Utility installs, provisions and configures
  AMI system
• U2 Utility manages end-to-end life-cycle of the
  meter system
• U3 Utility upgrades AMI system to address future
  requirements
• Other Utility use cases
• AMI Vendor use cases

9
Define New Use Cases

• Focus on maintenance life cycle related
  activities for the meter thru the head end system
• Avoid HAN use cases with the exception of the AMI
  Communication interface with the ESP
• IP/3rd party gateways

10
Functional Requirements

• Create a SRS (system requirements specification)
  similar to OpenHANs efforts
• Derive requirements from the use case review
• Focus on the AMI head end to the meter from a
  network maintenance perspective
• Input from the group???

11
Schedule

• Meet via teleconference every 3 weeks
• Meet at every UCA face to face meeting

Questions/Comments?
Next Steps?