10
SCE PEV Demand Response Pilot
SCE PEV Demand Response
Pilot
Background
1
SCE’s strategic plan includes industry support for developing
interoperable field technologies and ensuring their integration
with utility back-office systems
1. Open Standards (Since 2007) - Enabling Smart Energy Profile 1.X and 2.0
- SEP2.0 Harmonization with SAE & IEC
- Leading the development of Electric Service Provided Interface (ESPI)
and Automated Demand Response (OpenADR) standards
2. Equipment Lab Testing (Since 2009) - Evaluate market available smart charging products
- Work with industry partners to develop interoperable products
- Verify that smart charging devices are compatible with back-office
systems
3. Pilots (2012-2014) - Evaluate smart charging products in “real world” conditions
- Use results to structure future PEV specific programs
- End to End Integration Testing (System and Field)
PEV/Grid Communications
2
2. Direct (Residential)
• AMI, Internet, Zigbee, Wi-Fi
• Program Enrollment for residential
customers
• SEP 1.X and SEP 2.0 function sets
• DRLC, Pricing and TOU programs,
Metering, Response, Charge
Reservation
SCE
Field Devices
3rd
Parties
(C&I, Aggregators)
Indirect/Aggregated
Direct
B2B
1. Business to Business (B2B)
• Internet (HTTPS)
• 3rd Party Programs
• OpenADR 2.0, ESPI
• DRLC, Pricing and TOU Programs,
Sub-metering
3. 3rd Party Communications
• Translation between
OpenADR/ESPI and local
communications
• Workplace Charging
• DR, Pricing and TOU programs,
sub-metering
SCE PEV Communications Architecture
3
3rd Party Cloud
Public
Residential Home Area Network
SEP 2.0 Network(Wi-Fi)
SEP 2.0 Network(ZIP)
SEP 1.X Network
Gateway/Router
ZIP EVSE
Wi-Fi EVSE
1.X EVSE
SCE Back Office (ATO Labs) Fleet (C&I)
Internet
SEP 2.0
SEP 1.X
Sub-meter (3rd Party)
Aggregator
?
EMS
SEP 1.1
SEP 1.1
?
SEP 1.1 ?
?
SEP 1.1
SEP 2.0 Web Server ALCS
NMS
OpenADR 2.0 DRAS
ESPI Web Server
OpenADR 2.0
OpenADR 2.0
ESPI MDMA
4 Domains:
• SCE Back Office
• Residential HAN with
multiple topologies
• Fleet (C&I)- Includes
SCE workplace
charging
• Public (TBD)
Direct Communications
4
SCE
Field Devices
3rd
Parties
(C&I, Aggregators)
Indirect/Aggregated
Direct
B2B
SEP1.x ESI
SEP1,x
Network
Gateway/
Router
SEP2.0
Network (Wi-Fi)
SEP2.0
Network (ZIP)
SEP2.0 Cloud Server
Internet
Wi-Fi EVSE
(SEP 2.0)
ZIP EVSE
(SEP 2.0)
Zigbee 1.1
EVSE
SEP 2.0
Meter
(ZIP)
SEP 2.0
Meter
(Wi-Fi)
Communications tested:
• AMI to Zigbee SEP 1.X EVSE
• AMI to Zigbee/Wi-Fi Bridge to Zigbee IP/
Wi-Fi EVSE
• Internet to Gateway to Zigbee IP
• Internet directly to Wi-Fi EVSE
Functions Tested:
• Demand Response Load Control
• Pricing and TOU programs
• Metering
• Response
• Messaging
• Charge Reservation
Various HAN Topologies
Direct Communications- Considerations
5
AMI to Zigbee EVSE
• EVSE must be Zigbee
SEP 1.1 enabled
• Utilize existing AMI
communications
• Provides ‘real time’
consumption
information to HAN
Gateway
• Translates SEP 1.x to
2.0 for energy
consumption info to
Wi-Fi devices
• Bridges Wi-Fi to ZIP
• Could include routing
functions
SEP 2.0 Cloud Server to ZIP or Wi-Fi EVSE
• Direct communications
to Wi-Fi devices possible
• Cloud server would be utility ESI
• DR, pricing, etc. (energy info from SEP 1.x)
Potentially: Test communication directly to PEVs via PLC
Potentially: Test SEP2.0 metering using the internet
Business to Business Communications
6
SCE
Field Devices
3rd
Parties
(C&I, Aggregators)
Indirect/Aggregated
Direct
B2B
ESPI Web Server OpenADR 2.0 DRAS
EVSE
Internet
PLC
?
3rd Party Aggregator/ EMS
Internet
3rd Party
??
Communications tested:
• ESPI over the internet
• OpenADR 2.0 over the internet
Functions Tested:
• Demand Response Load Control
• Pricing and TOU programs
• Metering
B2B Communications- Considerations
7
ESPI interface with 3rd Party
• ESPI sub-metering server must interface with Billing systems for automation (TBD)
• OAuth necessary for 3rd
party/customer authentication and authorization
• Certification
• Communication of data from sub-meter to 3rd party systems and translation to ESPI
OpenADR interface with 3rd Party
• OpenADR 2.0 under
development
• Technical details for OpenADR EV communications will need to be aligned with current/ future SCE OpenADR plans (to device?)
Potentially: Testing of OpenADR 2.0 communications to include both EV
aggregators (including telematics providers) C&I customers
Potentially: Testing of OpenADR 2.0 to SEP Gateway for Workplace Charging
Timeline
8
