AEP's gridSMART sm Project Greg Steinmetz AEP gridSMART sm 11/12/2009 AEP's gridSMART Project - Implementation of CIM within Metering/AMI South Bend pilot

AEP's gridSMARTsm Project

Greg Steinmetz

AEP gridSMARTsm

11/12/2009

AEP's gridSMART Project - Implementation of CIM within Metering/AMI South Bend pilot


2

Presentation Contents• What is AEP’s gridSMARTsm Initiative?

• What is gridSMARTsm South Bend Pilot?

• How is AEP implementing CIM within the South Bend Pilot?

• How can you prepare yourself and your companies?


3

What is AEP’s gridSMARTsm Initiative?

• A multi-year initiative that includes a suite of customer programs and advanced technology initiatives that will transport us into a new era of energy delivery and customer service.

• gridSMARTsm components, include:– Customer programs: Energy efficiency and conservation opportunities and options. – Distribution grid management and advanced metering: New technologies that

improve service reliability by quickly identifying and possibly reconfiguring the distribution circuit to minimize the impacts of certain service interruptions; advanced data and communications systems that provide customers and AEP with real-time use and pricing information to facilitate usage decisions that immediately impact the monthly electric bill; and installation of new technologies that will allow AEP's facilities to accommodate customers' new technologies.

– Distributed resources: Energy storing and energy producing devices located throughout the distribution system that respond quickly to local needs and conditions for greater service reliability.

– Internal efficiencies: AEP demonstrates its commitment to gridSMART by implementing numerous efficiency improvements within its own operations - from lighting efficiencies in office buildings to variable-speed motors in power plants.


4

What is gridSMARTsm South Bend Pilot?

• AMI metering (10,000 Smart Meters)• Automatic meter reading• Prepaid metering• Remote connect and disconnect

• Distribution grid management (via AMI communications)

• Enable customer conservation• Web Portal• Distribution Load Control• Time of use rates• HAN devices


5

IEC 61968: Interface Reference Model Framework Used - Identifying Message Types

(NE)Network

ExtensionPlanning

(CS)CustomerSupport

(MR)Meter

Reading &Control

(AM) Records &

AssetManagement

(MC)Maintenance

& Construction

InterfaceStandard: Part 4





(ACT)CustomerAccount

Management

(FIN)Financial

(PRM)Premises

(HR)Human

Resources

(EMS)Energy

Management & Energy Trading

(RET)Retail


(SC)Supply

Chain and Logistics

(NO)Network

Operation


(OP)OperationalPlanning &

Optimization








Electric Distribution NetworkPlanning, Constructing,

Maintaining, and Operating

Generation and Transmission Management, Enterprise Resource Planning, Supply Chain, and

General Corporate Services

Business Functions External To Distribution

Management

Distribution ManagementBusiness Functions


6

IEC 61968 Part 9 - Reference Architecture


7

AEP South Bend Pilot Architecture


8

Meter Status• WSDL Location:

http://xxxx/gridSmartAdaptation-war/MeterStatusWService?wsdl

• Description– The purpose of this service is to provide a "ping" capability, allowing back-office

applications to contact a device in the field and confirm if it is energized. The operation is asynchronous in nature, in that back-office applications must "provision" a job(s) in the AMI system(s) to perform the meter status operation. When the AMI system(s) complete processing the request, a call back service in the back-office application (called a "deliver" message) will return the results.

– This message supports requesting Meter Status operations for multiple devices. For the Indiana Pilot, the <MeterGroups> element will not be supported.

– The Response type for this service contains a standardized Acknowledgement message. Embedded in the acknowledgement is a ContextID field, which represents an AMI head-end system agnostic identifier for the requested operation, along with a timestamp marking when the operation was started. If the operation was targeted as multiple devices, a collection of <Result> elements is also returned, indicating the success/failure to submit jobs to the AMI system for each unique device identifier (mRID).


9

AEP South Bend Pilot Integration Model

Persistence Components

Datastore

MRID[i] to AUID[i]

AUID[i] to MRID[i]

CanonicalProvisioning

Service

CanonicalDeliverService

AMI AdapterProvisioning

Service

AMI AdapterDeliverService

AEP +CIM

Types

AEP +CIM

Types

AEP + CIMProvision XML

AEP + CIMDeliver XML

VendorProvision XML

Vendor Deliver XML

AEPBack-officeApplications

Context ID XAck

Context ID XAUID AEP[i]

AMISystem

MRID[i]

AUID AEP[i]To MRID[i] Mapping

MRID[i]

Context ID Legend

Web Service

Asynchronous Messaging

Native Connections / JDBC

AUID AEP[i]


10

AEP South Bend Pilot Integration ModelMeter Status (Provision)

<soapenv:Envelope xmlns:soapenv=“..." xmlns:met= "http://metering.si.buslogic.gridsmartadaptation.aep.com" xmlns:v1= "http://iec61968/part9/XSD/MeterStatusRequest/v1"> <soapenv:Header/> <soapenv:Body> <met:provisionMeterStatus> <met:ProvisionMeterStatusRequest QOS="" correlator="" definitive="true" onBehalfOf="userx" origin="MACSS" sequence="1" version="1"> <MeterStatusRequest> <v1:MeterAssets> <v1:MeterAsset> <v1:mRID>123456789</v1:mRID> </v1:MeterAsset> </v1:MeterAssets> </MeterStatusRequest> </met:ProvisionMeterStatusRequest> </met:provisionMeterStatus> </soapenv:Body></soapenv:Envelope>


11

AEP South Bend Pilot Integration Model Mapping AEP AUID’s to AMI MRID’s (Provision)

<soapenv:Envelope xmlns:soapenv=“…” xmlns:urn="urn:com:[confidential]"> <soapenv:Header/> <soapenv:Body> <urn:ListNetworkDevices> <urn:SerialNumber>123456789</urn:SerialNumber> </urn:ListNetworkDevices> </soapenv:Body></soapenv:Envelope>--------------------------------<soapenv:Envelope xmlns:soapenv=“..." xmlns:xsd=“..." xmlns:xsi=“..."> <soapenv:Body> <ListNetworkDevicesResponse xmlns=“[confidential]"> <Device> ... <UtilDeviceID>SSN0000344</UtilDeviceID> <UtilDeviceState> <Name>UTL_DEVICE_STATE_ACTIVE</Name> <LocalizedValue>Active</LocalizedValue> </UtilDeviceState> ... <Name>123456789</Name> <NicSerialNumber>123456789</NicSerialNumber> <MacID>00:13:50:ff:fe:00:fe:b3</MacID> <IPAddress>fdbc:cec5:e8fe:32:213:50ff:fe00:feb3</IPAddress> ... </Device> </ListNetworkDevicesResponse> </soapenv:Body></soapenv:Envelope>


12

AEP South Bend Pilot Integration Model Invoking AMI Vendor Meter Status Service (Provision)

<soapenv:Envelope xmlns:soapenv=“..." xmlns:urn=“[CONFIDENTIAL]"> <soapenv:Header/> <soapenv:Body> <urn:AddPingJob AutoActivate="false"> <urn:JobInfo> <urn:Name>Meter Status Request</urn:Name> </urn:JobInfo> <urn:PingJob IsBackboneJob="false"> <urn:NetworkLevelPing PacketSize="1"> <urn:DeviceMacID>00:13:50:ff:fe:00:82:46</urn:DeviceMacID> <urn:NumberPings>2</urn:NumberPings> </urn:NetworkLevelPing> <urn:NumberRetries>3</urn:NumberRetries> <urn:Priority> <urn:Name>JOB_PRIORITY_NORMAL</urn:Name> </urn:Priority> </urn:PingJob> <urn:Schedule> <urn:Immediate/> </urn:Schedule> </urn:AddPingJob> </soapenv:Body></soapenv:Envelope>------------------<soapenv:Envelope xmlns:soapenv=“...“ xmlns:xsd=“..." xmlns:xsi=“..."> <soapenv:Body> <JobIDResponse xmlns=“[CONFIDENTIAL]"> <JobID>13219</JobID> </JobIDResponse> </soapenv:Body></soapenv:Envelope>


13

AEP South Bend Pilot Integration ModelDeliver Meter Status Acknowledgement (Provision)

<S:Envelope xmlns:S=“..."> <S:Body> <ns3:provisionMeterStatusResponse xmlns:ns4= "http://metering.si.gridsmartadaptation.aep.com" xmlns:ns3= "http://metering.si.buslogic.gridsmartadaptation.aep.com" xmlns:ns2= "http://iec61968/part9/XSD/MeterStatusRequest/v1"> <ns4:ProvisionMeterStatusResp version="1" sequence="1" origin="MACSS" onBehalfOf="userx" definitive="true" correlator="" QOS=""> <Acknowledgement> <ContextID>422830c7-4e33-4a81-b8de-3232420f1e8f</ContextID> <CreationTime>2008-09-09T03:14:02.206-04:00</CreationTime> <Results> <Result Reason="" Outcome="SUCCESS" mRIDType="METERASSET" mRID=“123456789"/> </Results> </Acknowledgement> </ns4:ProvisionMeterStatusResp> </ns3:provisionMeterStatusResponse> </S:Body></S:Envelope>


14

AEP South Bend Pilot Integration ModelAMI System Delivers Provisioning Acknowledgement (Delivery)

<?xml version="1.0" encoding="UTF-8"?> <PingResults RowCount="1" SearchKey="ADV-7952" xmlns=“[CONFIDENTIAL]"> <DevicePing DeviceMacID="00:13:50:ff:fe:00:82:46" DeviceName=“123456789" GatewayName="EV0000362" GatewaySerialNumber="SSN0000362" JobCreator="jimgreene" JobExecutionTime="2008-09-09T03:22:52.541-04:00" JobID="13219" JobName="Meter Status Request" LocLatitude="39.86547" LocLongitude="-82.87527" PacketSize="0"> <ExecutionStatus> <Name>JOB_EXEC_STATUS_COMPLETE</Name> <LocalizedValue>Completed</LocalizedValue> </ExecutionStatus> <Ping GatewayTimestamp="2008-09-09T03:22:53.000-04:00" PacketLost="false" PingSequenceNumber="0" RoundtripMS="2622"> ... </Ping> </DevicePing> </PingResults>


15

AEP South Bend Pilot Integration ModelMessage to Back-office via Callback Service (Delivery)

<soapenv:Envelope xmlns:soapenv=“..." xmlns:si="http://si.endpoints.gridsmart.aep.com" xmlns:v1="http://iec61968/part9/XSD/MeterStatus/v1"> <soapenv:Header/> <soapenv:Body> <si:deliverMeterStatus> <si:DeliverMeterStatusRequest QOS="" correlator="" definitive="true" onBehalfOf=“userid" origin=“MACSS" sequence="1" version="1"> <DeliverAcknowledgement> <ContextID>422830c7-4e33-4a81-b8de-3232420f1e8f</ContextID> <CreationTime>2008-08-04T04:00:00-04:00</CreationTime> <Results> <Result mRID="123456789" mRIDType="METERASSET" Outcome="SUCCESS" Reason=""/> </Results> </DeliverAcknowledgement> <MeterStatusResult> <v1:MeterAssets> <v1:MeterAsset> <v1:mRID>123456789</v1:mRID> <v1:status>ENERGIZED</v1:status> <v1:statusDateTime> 2008-08-01T04:00:00.000-04:00 </v1:statusDateTime> <v1:statusRemarks/> <v1:statusReason/> </v1:MeterAsset> </v1:MeterAssets> </MeterStatusResult> </si:DeliverMeterStatusRequest> </si:deliverMeterStatus> </soapenv:Body></soapenv:Envelope>


16

AEP Future Integration Model

Persistence Components

Datastore

MRID[i] to AUID[i]

AUID[i] to MRID[i]

CanonicalProvisioning

Service

AEP + CIMProvision XML

AEPBack-officeApplications

Context ID XAck

Context ID XAUID AEP[i]

AMISystem

A

MRID[i]


MRID[i]

Context ID Legend

Web Service

Asynchronous Messaging

Native Connections / JDBC

AEP +CIM

Types

AEP +CIM

Types

CanonicalDeliverService

AEP + CIMDeliver XML

AUID AEP[i]

AMISystem

B

MRID[i]



Service

Vendor AProvision XML


Vendor ADeliver XML


Service

Vendor BProvision XML


Vendor BDeliver XML


17

• Educate yourself– EPRI Resources– Grid Interop 2007 -

http://www.gridwiseac.org/historical/gridinterop2007/forum_papers.aspx

• Join the UCA - http://www.ucaiug.org/default.aspx– Join the CIM UG - http://cimug.ucaiug.mobi/default.aspx– Read IEC 61968 – It will be available

• Purchase a Tool that you can actually look at the CIM – PowerPoint's don’t tell the entire story

• Figure out how you change your organization to be a Semantics friendly, model driven integration, standards involved Utility.

• Get Buy in from the Right Levels – you will need to be an Educator/Advocate of Utilizing CIM in your company

How do you to prepare yourself and your companies?

http://cimug.ucaiug.mobi/default.aspx

http://cimug.ucaiug.mobi/default.aspx


18

Questions?

Documents

AEP's gridSMART sm Project Greg Steinmetz AEP gridSMART sm 11/12/2009 AEP's gridSMART Project - Implementation of CIM within Metering/AMI South Bend pilot