Upload
kory-hamilton
View
213
Download
1
Tags:
Embed Size (px)
Citation preview
Smart Grid Research ConsortiumNovember 9, 2010
DM Goals/ObjectivesUser adoption & consumer engagementProve consumer behavioral changeProve consumer acceptance of utility controlReduce overall consumptionReduce consumer costCurtail peaks & determine shared value of
created energy reserves with LCRA
DM StrategyResearched DM solutions via RFI processInitiate two DM pilots in 2010:
Consert Inc. & LCRA (12 months)Incenergy, LLC (6 months)Parallel test of 5 GE AMI meters
Continued market research
Consert & LCRA Pilot250 service locations
Approx. 240 residential, 10 small commercial12 month pilotProviding thermostat, water heater LCD, pool
pump LCDMember & utility control via web portalsAMI meters – GE 2S240 volt I-210+c (gateway
under glass)Verizon Cellular backhaul from meter to server5 min data intervals provided to consumer
Member Portal
Utility Portal
Incenergy Pilot25 residential
service locations6 month pilotProviding
thermostat, portal, & phone app
Member control, no utility control in pilot
Participant Recruitment
Response Rates = Consert = ~15%Incenergy = <5%
Consert Target = 2,000NEM
users + 600 on single feeder
Incenergy Target =
265 NEM users
Sample Criteria:•# in household•% of time at home•High-speed internet•Pool pumps•Electric heat & cooling•Size of home•Homeowner
Email containing
link to online
consent form and survey
DM Pilot OperationsInstallation & Scheduling
Consert: Bluebonnet installs meters CapGemini schedules & installs HAN
Email & text reminders sent to participantsIncenergy:
No meter install Incenergy/DSI schedules & installs HAN
Monitoring and ControllingLCRA-triggered events (4CP, MCPE, EEA, LCRA
load)Bluebonnet-triggered events
Communications & MarketingTexas Coop Power Articles
Showcase 2 member experiences for 12 month period
Host member orientation meetings prior to installations
Web portal/NEMConduct surveys & focus groups
Future StrategyCommercialize DM in 2012
Available to interested membersCost/incentives TBD
Select AMI vendor in 2011, begin deployment in 2012