Sub Meter Protocol Road Map

Transcription

BEFORE THE PUBLIC UTILITIES COMMISSION OF THE
STATE OF CALIFORNIA
Order Instituting Rulemaking on the
Commission’s Own Motion to Consider
Alternative-fueled Vehicle Tariffs, Infrastructure
and Policies to Support California’s Greenhouse
Gas Emissions Reduction Goals.
Rulemaking 09-08-009
(Filed August 20, 2009)
SUBMETERING PROTOCOL ROADMAP REPORT
JANET S. COMBS
ANDREA L. TOZER
Attorneys for
SOUTHERN CALIFORNIA EDISON COMPANY
2244 Walnut Grove Avenue
Post Office Box 800
Rosemead, California 91770
Telephone:
(626) 302-6713
Facsimile:
(626) 302-6693
E-mail: [email protected]
Dated: January 3, 2012
BEFORE THE PUBLIC UTILITIES COMMISSION OF THE
STATE OF CALIFORNIA
Order Instituting Rulemaking on the
Commission’s Own Motion to Consider
Alternative-fueled Vehicle Tariffs, Infrastructure
and Policies to Support California’s Greenhouse
Gas Emissions Reduction Goals.
Rulemaking 09-08-009
(Filed August 20, 2009)
Pursuant to Decision 11-07-029 Phase 2 Decision Establishing Policies to Overcome
Barriers to Electric Vehicle Deployment and Complying with Public Utilities Code Section
740.2, issued July 25, 2011 (Decision),1 Southern California Edison Company (U 338-E)
submits, on behalf of itself, Pacific Gas and Electric Company (U 39-M), and San Diego Gas &
Electric Company (U 902-M) (the Utilities), this Submetering Protocol Roadmap Report
(Roadmap Report), attached hereto as Attachment A.
As directed by the Decision, the Utilities formed a working group and collaborated with
stakeholders to develop a submeter protocol. The Utilities prepared this Roadmap Report with
input from third party participants on key technical issues; however, it has not been reviewed or
subject to comment by third parties and reflects primarily the assessment of the Utilities unless
otherwise noted. Therefore, the Utilities recommend that the Roadmap Report be subject to
review and comment by third parties as part of the collaborative process and anticipate that the
1
The Utilities requested an extension of time to file this Roadmap Report until December 31, 2011, which was
granted by the letter from Executive Director Paul Clanon, dated October 12, 2011. Because December 31,
2011, falls on a Saturday and the following Monday is a holiday, the Utilities submit this compliance filing on
January 3, 2012, in accordance with Rule 1.15 of the California Public Utilities Commission Rules of Practice
and Procedure.
-1-
Roadmap for development of a submeter protocol will evolve as the market for plug-in electric
vehicles develops and the Utilities receive additional information from stakeholders.
Respectfully submitted,
JANET S. COMBS
ANDREA L. TOZER
/s/ Andrea L. Tozer
By: Andrea L. Tozer
Attorneys for
SOUTHERN CALIFORNIA EDISON COMPANY
2244 Walnut Grove Avenue
Post Office Box 800
Rosemead, California 91770
Telephone:
(626) 302-6713
Facsimile:
(626) 302-6693
E-mail:[email protected]
January 3, 2012
-2-
ATTACHMENT A
Submetering Protocol Roadmap Report
As Directed by Alternative-Fueled Vehicle Proceeding R.09-08-009,
Decision 11-07-029 Ordering Investor-Owned Utilities To Develop Protocols
Supporting The Use Of Customer-Owned Submeters For Use In Billing EV Load
Pacific Gas and Electric Company
Southern California Edison Company
San Diego Gas & Electric Company
January 3, 2012
ACaliforniaInvestorOwnedUtilitiesjointinitiative.
Contents
1. ExecutiveSummary.................................................................................................................5
2. IntroductiontoRoadmapReport............................................................................................10
2.1
RoadmapReportStructure..........................................................................................10
2.2
ProjectObjectives&Background................................................................................11
2.2.1 AFVOIRRequirements.....................................................................................11
2.2.2 RoadmapReportDevelopmentMethodology.................................................12
2.2.3 Participants........................................................................................................13
3. POLICYANDIMPLEMENTATIONDEPENDENCIES....................................................................14
3.1.1 OpenIssuesforRoadmap.................................................................................14
3.1.2 ConsumerProtectionQuestions.......................................................................14
3.1.3 GuidingPrinciplesforResolvingDependenciesRelatingtoEVSubmetering
ProtocolDevelopment.................................................................................................15
4. USECASEEVALUATION..........................................................................................................16
4.1
Background..................................................................................................................16
4.1.1 PurposeandApplicationofUseCases..............................................................16
4.1.2 UseCaseDevelopmentProcess........................................................................16
4.1.3 UseCaseApplicationtoSubmeteringProtocolRoadmap................................17
4.1.4 Overviewoffundamentalusecasestobeaddressed......................................18
January3,2012
Page2
4.2
UseCaseEvaluation.....................................................................................................19
4.2.1 Summary...........................................................................................................19
4.2.2 Detailedevaluationofindividualusecases......................................................20
UseCase0:BaselineParallelMetering............................................................22
UseCase1:ResidentialUseCase(Basic).........................................................25
UseCase2:ResidentialUseCase(MultipleEVs).............................................28
UseCase3:SmallMultiDwellingUnit(MDU)UseCase..................................31
UseCase4:LargeMultipleMeter/CommercialUseCase..............................34
UseCase5:No3rdPartyInvolvement(FieldAreaNetwork)...........................37
UseCase6:ResidentialUseCase(Basic)w/EVSP...........................................40
UseCase7:ResidentialUseCase(MultipleEVs)w/EVSP...............................43
UseCase8:SmallMultiDwellingUnit(MDU)UseCasew/EVSP...................46
UseCase9:LargeMDUUseCase(Garage)w/EVSP.......................................49
UseCase10:StandardMobileSubmeterUseCase.........................................52
UseCase11:InParallelUseCase(FSub+MSub)............................................55
UseCase12:InSeriesUseCasew/oCrossTalk(FSub+MSub)......................59
UseCase13:InSeriesUseCasew/CrossTalk(FSub+MSub)........................62
UseCase14:InSeriesUseCase(2MSubs)......................................................65
UseCase15:AdvancedMeteringInfrastructure(AMI)UseCase...................68
UseCase16:DirectOpenEVUseCase.............................................................71
UseCase17:NetEnergyMetering(NEM)BasicCase......................................73
5. SUBMETERINGIMPLEMENTATIONISSUESANDREQUIREMENTS...........................................76
5.1
SubmeteringImplementationIssuesandRequirements............................................76
5.1.1 Introduction.......................................................................................................76
5.1.2 Guideline1:Useofsubmetersinvariouslocations..........................................77
5.1.3 Guideline2:Technicalperformancerequirementsforsubmeters..................77
January3,2012
Page3
5.1.4 CommunicationRequirements.........................................................................80
5.1.5 Billing&RegulatoryAnalysis.............................................................................82
StandardUtilityServiceScenario.....................................................................85
5.1.6 AnalysisofOtherImpactsonSubmetering,SubtractiveBilling,andIOUBilling
Systems........................................................................................................................86
6. SUBMETERINGROADMAP.....................................................................................................87
6.1
MultiStageRoadmapOverview..................................................................................87
6.1.1 DetailedRoadmapforPhase1–Define/Plan(Complete)................................87
6.1.2 DetailedRoadmapforPhase2–Design/DevelopCalifornia
SubmeteringProtocol..................................................................................................87
6.1.3 DetailedRoadmapforPhase3–BuildInterimCaliforniaSolution..................88
6.1.4 DetailedRoadmapforPhase4–BuildScalableLongTermSolution...............88
6.1.5 DetailedRoadmapforPhase5–BuildSmartGridSolution.............................89
7. APPENDICES...........................................................................................................................91
A.
MatrixofDetailedRequirements...............................................................................91
B.
Glossary......................................................................................................................106
January3,2012
Page4
1. ExecutiveSummary 1
ProjectBackground
TheCaliforniaPublicUtilitiesCommission(CPUC)hasdirectedtheCaliforniaInvestorOwned
Utilities(IOUs),wherepossible,toconsultwithappropriatestakeholdersofthePublicElectric
VehiclesCollaborativeandnationalstandardsbodiestodevelopaSubmeteringProtocolfor
electricvehicles.ThesestakeholdersincluderepresentativesofthePluginElectricVehicle
industry,consumergroups,andothersaswellastheEnergyDivisionoftheCPUC.TheIOUs
considerthisRoadmapReportasnapshotofapointintimeinthecollaborative,withissuesand
solutionsexpectedtoevolveasgreaterclarityintocustomerneeds,3rdpartyproductsand
services,submeteringtechnologyandcosts,andregulationareachieved.
ProjectMethodology
ToestablishthepathtoidentifyingtheissuesandsolutionsthatwillleadtotheSubmetering
Protocol,fourworkingteamswereformedcomprisedofmorethan100peoplefromtheutilities,
StateofCalifornia,and3rdpartyorganizationstoaddressthe7areasspecifiedbytheCPUCinits
Phase2DecisionondevelopingaSubmeteringProtocol.Theseteamswere:
1. UseCaseIdentification.
2. BillingandRegulatory.
3. MeterRequirements,Compliance,andStandards.
4. CommunicationandSecurity.
SubmeteringUseCases
Usecasesarethefirststepinthedevelopmentofbusinessandfunctionalrequirements.Basedon
acollaborativeeffortinvolvingutilityandotherstakeholders,atotalof17fundamentalusecases
wereidentified.The17fundamentalusecasesdefinedtodatewillbeusedtodeveloptariffand
technicalrequirementsbasedonourcurrentcollectiveunderstandingofpotentialsubmetering
impact,feasibilityandcosteffectiveness.Itisanticipatedthatadditionalusecasesmaybe
identifiedastheworkinggroupcontinuestodeveloptheSubmeteringProtocol.
Foreachusecase,adiagramwasproduceddepictingeachscenarioandtheassociationbetween
3rdpartiessuchasdatamanagementagentsandutilitysystems.Inaddition,theIOUsperformeda
highlevelimplementationanalysislistingallperceivedadvantagesanddisadvantages.
1
Section source: Primarily PG&E, SCE, SDG&E, based on working group team meetings, individual
telephone and email communication among utilities and third parties, and inter-utility communication.
January3,2012
Page5
SubmeteringBillingandRegulatoryRequirements
TheBillingandRegulatoryteamassessedthepotentialimpactusecasesmayhaveoncurrenttariffs
todeterminetheneedforpotentialfuturetariffrefinementanddevelopment.Presenttariffsfor
DirectAccess(DA)servedasausefulbase,becausethroughDA,theCommissionhaspreviously
decidedmattersofunbundlingofutilityservices,andrequirementsforthirdpartiestobecomean
integratedcomponentoftheutilitybillingsystem.TheRoadmapReportidentifiesthebillingand
regulatorydependenciesandissuestobeaddressed.Forexample,akeyinitialconclusionisthat,as
isthecasewithDA,splitloadsshouldnotbeallowed.
SubmeteringTechnicalRequirements
TheTechnicalRequirementsTeamidentifiedthetechnicalrequirementsandstandardstoestablish
EVsubmetering.Theteam,asisthecasewiththeBillingandRegulatoryTeam,usedtheDirect
AccessMeteringandDataStandards(DASMMD)asastartingpoint,andidentifiedhowthese
standards,whichweredevelopedfollowingaverydetailedprocessunderCommissiondirection,
couldbeappliedtosubmetering.
Tofutureproofsubmeterdesigns,theTechnicalRequirementsteamconcludedthatfunctionality
shouldincludebidirectionalcapabilitiesenablingvehicletogridfunctionality;demandresponse
capabilitiesenablingloadcontrol;NEMcapabilitiesenablingthecombinedmeasurementofself
generationandbatterychargingandremotefirmwareandconfigurationupdatecapabilities.
SubmeteringCommunications,Security,andStandardsRequirements
TheCommunicationsteambegantoidentifytherequirementsandstandardsnecessarytoestablish
dataexchangebetween3rdpartydevicesandtheutility.Amongthevarioustopicsaddressedbythe
communicationsteamaremethodsofsecuringandprotectingEVcustomerdata.Theteam
concludedthatdevelopingcommunicationfunctionalityfortheSubmeteringProtocolintheshort
termisbestservedbyleveragingexistingstandardsincludingNAESBESPI,OpenSGOpenADEand
OAuthaswellasbenchmarkingfunctionalityandsecurityapproachesusedinotherindustriessuchas
HealthCare(HIPAA)andCreditCards(PCI).Movingforwardintothemidandlongtermthe
availabilityoffuturestandardssuchasSmartEnergy2.0willgiveindustryanopportunitytoadopt
moreadvancedusedcases.
SubmeteringProtocolPolicyandImplementationStrategies
TheroadmapfurtherdefinesdependenciesandsomeguidingprinciplesidentifiedbythethreeIOUs
toincorporateintothedevelopmentoftheSubmeteringProtocol:
x TheSubmeteringprotocolwillfocusonmatterswithinCPUC’spolicyandregulatoryjurisdiction
becausetheCPUCmustenforcetheprotocolandresolvedisputesamongutilities,EVSPsand
customers.
January3,2012
Page6
- Forexample,theprotocolwillneedtofocusonhowsubmetersmaybeusedinlieuofIOU
separatemetersforIOUbillingpurposesinaccordancewithsimilarstandardsandprotocols
usedforcustomerownedseparatemetersunderDAprogram.
- TheprotocolwillnotaddressEVSPthirdpartybusinessissues,suchasthetermsand
conditionsofathirdparty’ssaleofelectricityforuseasEVfuelbecausetheCPUC(initsPhase
1decision)determineditwillnotregulatethetermsandconditionsofthirdpartyfuelsales.
x TheprotocolwilladdresstherightsandobligationsofIOUs,customersandthirdpartiesastothe
useofsubmetersbycustomersandIOUsforIOUbillingpurposes.
x TheprotocolwillbedocumentedinCPUCapprovedtariffsandassociatedtechnicaldocuments.
x TheIOUshaveanobligationtoaccuratelybilltheircustomers;consequently,theIOUswill
continuetoseparatelymetertheirseparatecustomers.
x ForcustomerownedsubmetersusedbyIOUsforbilling,meterreadingand/ormeter
maintenancemaybeofferedbytheIOUorbyqualifiedthirdpartiesconsistentwithDAmodel.
x BillingdisputeswillcontinuetoberesolvedbytheCPUCthesameasbillingdisputesgenerally.
x IOUcostsassociatedwiththeuseofsubmeteringorparallelmeteringforIOUbillingpurposes
willbesubjecttoreviewandcostrecoveryapprovalbytheCPUC,thesameasotherutilitycosts
ofservice.
SubmeteringRoadmap
TheRoadmaptimelineillustratedonthenextpagedepictsalongterm,multiphaseviewof
SubmeteringProtocolplanning,development,andimplementation.
x Phase1representsthedefinitionofaCaliforniaSubmeteringProtocolroadmapthathasbeen
developedbytheprojectworkinggroupsanddetailedinthisreportdocument.
x Phase2consistsoftheactivitiesrequiredtodevelopaCaliforniaSubmeteringProtocol.
x Phase3consistsofimplementingaSubmeteringProtocolsolutionmakingcustomerand3rd
partyownedsubmeteringavailabletocustomersinCaliforniaforbillingpurposes.Duringthis
stageutilitieswillbeabletoexecutemanual,smallscalesubtractivebillingofEVchargingloads.
x Phase4againenablescustomerand3rdpartyownedsubmetering;howeverinthisphase
nationalstandardsarecompleteandimplemented,andutilitieswillbeabletoexecute
automated,fullscalesubtractivebillingofEVchargingloads.
x Phase5representslongtermsolutionsincluding—butnotlimitedto—thedeploymentofSmart
Gridfieldareanetworkscapableofcommunicatingwithcustomerdevices.
January3,2012
Page7
January3,2012
• Completeandsubmitthe
SubmeteringRoadmapReport
- Responsibleorganizationsand
individualsforeach
- Keytasksoractivitiesand
timingforeach
• Developcertificationprocessfor3rd
partydevices,systems,processes
• Enable3wayhandshakeamongthe
utility,customer,and3rd partymeter
serviceprovider
• Pursuedevelopmentofnational
standardsforsubmetersand
subtractivebilling
• Implementasolution build,test,and
refinethenecessaryprocesses,
systems,andsysteminterfaces
- Implementationstrategyandplan,
schedule,tasks,anddeliverables
- Architecturaldesignforendto
endsystems(includingbackoffice • Developandcarryoutcustomer
integration)
informationcampaign
- Technical,security,privacy
requirements,specs,and
standardsalignedwithnational
standards
- Businessrequirementsandspecs
forutilities,customersand3rd
partymeterserviceproviders
- Marketplaceunderstanding
• Develop a CaliforniaSubmetering
Protocol
• Fullutilitycostrecoveryinplacefor
upgradestoIT/billingsystemsand
relatedcosts
• Utilitiesexecutemanual,smallscale
subtractivebilling ofEVchargingloads
• Submeter dataforIOUsubtractive
billing tobeprovided according to
protocol(includessubmeterID,
premiseID,anddate/timestamped
intervalusage)
• SubmetersforIOUsubtractivebilling
areownedbycustomersor3rd parties
• Nationalstandardsare
implemented
• Upgradeutilitysystemstohandle
automated,fullscalesubtractive
billing
relatedcosts
• Utilitiesexecuteautomated,full
scalesubtractivebilling
• SubmeterdataforIOUsubtractive
billing tobeprovidedaccordingto
protocol
• Submetersforsubtractivebilling are
ownedbycustomersor3rd parties
• NationalStandardsareinplace
• Assessthemarketvalueofinterutility
communicationstoaddressvehicle
"roaming"
• LeverageinvestmentsinSmartGrid
Technologiesbyusinganadvancedfield
areanetworktocollectcustomersubmeter
data
• Verifythatmobilesubmetersaredeployed
consistentwithalltechnicalandbilling
requirements
• NEMmetershavetheabilitytoreport
disaggregateddata(loadandgeneration)
• NationalStandardsareinplace(PowerLine
Communications)forassociatingmobile
submeterselectricallytomastermeters
• UtilitiesdeploySmartGridfieldarea
networkscapableofcommunicatingwith
customerdevices
• DivisionofMeasurementStandardshas
developedandimplementedproceduresfor
certifyingmobilemeters.
• Mobilemetersmeettechnicalperformance
andcertificationrequirementsaremarket
available.
NEXTGENERATION
TECHNOLOGYISAVAILABLE
LongTermImplementation
Phase5
BuildSmartGridSolution
DESCRIPTION
- ListofIssuesand/or
RequirementsandPreliminary
Recommendations
- Goals,objectives,scope,
guidelines
• Define aCaliforniaSubmetering
ProtocolRoadmap
• IOUcustomerscaninstallasubmeter,eitherownedbythecustomer
ora3rd party,andreceiveusagedatafromthose(nonutility)sources
forenergymonitoring
• IOUcustomerscanaddaparallelmeterservicepanelforadedicated
utilityownedandreadparallelmeter forEVchargingandbilling
• IOUcustomerscancontinuetousetheutility’ssinglewholehouse
meter,whichincludesEVchargingandbilling
• IOUcustomersmayhavethechoiceofresidentialandseveralEV
rates
MidTermImplementation
Phase4
BuildScalable
Solution
CUSTOMEROR3RD PARTYOWNEDSUBMETERINGIS
AVAILABLETOCUSTOMERSFORBILLING PURPOSES
ShortTermImplementation
CurrentPlanningandDevelopmentofSubmeteringProtocol
AVAILABLETOCUSTOMERSFORNONBILLING PURPOSES
Phase3
BuildInterimSolution
Phase2
Design/Develop
Phase1
Define/Plan
ACTIVITIES
Page8
Conclusions
Basedonthefourmonthsofcomprehensiveanalysisoftheissuesrelatedtosubmetering,the
IOUsreachedthefollowingconclusions:
x SubmeteringfornonbillingpurposescanbedonetodayunderCPUCapprovedtariffsand
doesnotinvolveutilitiesorrequirenewprotocols.
x EVpenetrationhasbeenlimitedtodateandhasnotjustifiedthecostofautomatingIOU
subtractivebillingtosupportrevenuegradesubmeteringofEVloads.
x Itiscriticaltobetterunderstandwhatourcustomerswantwithrespecttosubmeteringand
othersolutionstoEVmetering,andstepstoachievethisunderstandinghavebeenbuiltinto
theroadmap.
x Theemergingsubmeteringmarketisexpectedtogrowslowlyuntiltechnologicaladvances
providecustomerswithlowcost,innovativesolutions.
x Implementingsubmeteringisdependentonanddrivenby,ataminimum,theresolutionofthe
following7issuesidentifiedbytheCPUC:
x
-
Feasibleuseofsubmetersinvariouslocations.
-
Technicalperformancerequirementsforsubmeters.
-
Minimumcommunicationfunctionalityandstandardstobemet.
-
SecurityandprivacyofEVuserdatacollectedbyutilitiesandthirdpartyentities.
-
Methodologyforsettlingbillingdisputesandotherissuesamongutilities,3rdparties,and
customers.
-
Compliancewithnationalstandardsformeasurementandcommunicationfunctions.
-
Rulesforincorporatingsubtractivebillingintosubmeteringtariffs.
Inadditiontotheabove7issuesidentifiedbytheCPUC,theIOUsbelievethereareadditional
financialandmarketissuestobeconsidered,includingrecoveryofthecostsofupgrading
utilityadvancedmeteringinfrastructure(AMI)andbillingsystems.
x Therefore,submeteringshouldbeimplementedthroughaphasedapproachdescribedinthe
roadmap,basedoncustomerdemandforsubmetering,market/technologyrealitiesandcost
ofimplementationofvarioussubmeteringsolutionscomparedtootheralternatives,suchas
parallelmeteringandnonrevenuegradesubmetering.
x Basedonthisphasedapproach,theIOUsdonotanticipatedevelopingandimplementing
potentiallycostlyITbackofficesystemsolutionsuntiltheEVmarketsdevelopsufficiently.
x Whiletheteamsattemptedtoaddressalltheissuesidentified,inthecomingmonths,further
workwillberequiredastheroadmapreportcannotfullyresolvealltheseissuesatthistime.
January3,2012
Page9
2. IntroductiontoRoadmapReport
2.1 RoadmapReportStructure
ThisroadmapreportistheresultofaprocesswheretheIOUscollaboratedwith3rdparty
stakeholders.However,thisroadmapreporthasbeenpreparedsolelybytheIOUsasacompliance
filingpursuanttothePhase2Decision.TheIOUsconsideritasnapshotofapointintime,with
understanding,issues,andsolutionsexpectedtoevolveasgreaterclarityintocustomerneeds,3rd
partyproductsandservices,submeteringtechnologyandcosts,andregulationisachieved.
Primarycontributorstoeachsectionareidentifiedthroughoutthereport.
Thefollowingcontentisprovided:
x IntroductiontoRoadmapReport:Projectobjectivesandbackground,andAlternativeFueled
VehiclesOrderInstitutingRulemaking(AFVOIR)requirements.
x RoadmapDependenciesEvaluation(IOUDeveloped):IOUassessmentofandconclusions
regardingunresolvedtechnical,financialandregulatoryissuesthatneedtoberesolvedby
furtheractionbytheCaliforniaPublicUtilitiesCommission(CPUC)priortofurther
developmentoftheSubmeteringProtocol,includingissuesrelatingtoCPUCpoliciesand
authorityoversubmeteringrequirements,thirdpartymeteringserviceproviders,subtractive
billingdisputes,andrelatedmatters;and—basedontheseunresolvedissues—keyprinciples
recommendedforguidingtheresolutionoftheseissuesforfurtherdevelopmentand
implementationofEVsubmetering.
x UseCaseEvaluation(IOUDeveloped):IOUdescriptionsofusecasepurpose,development,
andevaluationcriteriaanddetailedtechnicalassessmentsof17usecases.
x SubmeteringImplementationIssuesandRequirements(DevelopedbyIOUsand3rdParties):
Descriptionsofsubmeteringtechnicalrequirements;communicationfunctionality,standards,
andsecurity;andbillingandregulatoryrequirementsandprotocols.
x RoadmapforDevelopmentofSubmeteringProtocol(IOUDeveloped):Descriptionsof
feasiblemultistagesubmeteringdevelopmentandimplementationpathsbasedoncurrent
understandingoftechnicalfeasibility,regulatoryandfinancialissues.
x Appendices:DetailedSubmeteringRequirementsMatrices;andGlossaryofAbbreviations.
January3,2012
Page10
2.2 ProjectObjectives&Background
2.2.1 AFVOIRRequirements2
2011AFVOIRPhase2Decision
ThePhase2DecisionincludedthefollowingkeydirectivesondevelopmentofSubmetering
Protocols:
x
“TheutilitiesmustcooperatewithstakeholderstoformaworkinggrouptodevelopanElectric
VehiclesubmeterprotocolthatcouldbeadoptedbytheCPUC.
- UtilitiesshouldprovidemultipleEVmeteringoptions,includingsinglewholehouse,
separateparallel,andsubmeteringatvariouslocations,and
- EVsubmetersandEVchargingserviceequipmentshouldbetreatedconsistentwiththe
treatmentofanyotherequipmentlocatedonthecustomersideofthemeter.”
x Theutilitiesaretoincludeintheworkinggroup,ataminimum,CommissionStaff,California
DepartmentofFoodandAgriculture,automakers,andelectricvehicleserviceproviders.
x Thefiledprotocolmustachieve,ataminimum,thefollowing:
- Supporttheuseofsubmeterslocatedinelectricvehicleserviceequipmentoronavehicle,
includingmobiledetachablemeters.
- Determinethetechnicalperformancerequirementsforanysubmeters.
- Identifytheminimumcommunicationfunctionalityandstandards.
- Describehowsubmeterdatamanagementwillsupportandprotectthesecurityand
privacyofElectricVehicleuserdatacollectedbyutilitiesandthirdpartyentities.
- Provideamethodologyforsettlingdisputes.
- Identifyandadheretoallexistingandapplicablenationalstandardsformeasurementand
communicationfunctions.
- Developrulesforincorporatingsubtractivebillingintosubmeteringtariffs.
2
Section source: California Public Utilities Commission
January3,2012
Page11
OnJuly28,2011,theAssignedCommissioner’sScopingMemoRuling–Phase3clarifiedthetiming
ofPhase2Decisiondeliverables.ThesedateswereconfirmedinaletterfromCPUCExecutive
DirectorPaulClanondatedOctober12,2011:
x HoldpublicworkshopbyOctober31,2011andfileareport15dayslater.
x SubmitroadmapreportbyDecember31,2011.
x FileaTier2adviceletterbyJuly31,2012supportingtheimplementationofsubmeter
protocol.
x SubmittariffsheetstoestablishrulesforuseofcustomersubmetersbySeptember1,2012.
2.2.2 RoadmapReportDevelopmentMethodology3
TheIOUs:
x KeptinplacethejointIOUprojectcoordinationteamestablishedinSeptember2011to
respondtotheSubmeteringProtocolorderintheCPUC’sPhase2Decision.
x ConductedaNovember14RoadmapReportWebExkickoffmeetingtowhichtheentire
AlternativeFueledVehicleOrderInstitutingRulemaking(AFVOIR)ServiceListandOctober
27,2011SubmeteringProtocolWorkshopattendeeswereinvited.
x Formedusecase,technicalrequirements,billing&regulatory,andcommunicationsteams
comprisedofmorethan20partiesrepresentingutility,StateofCalifornia,and3rdparty
organizationstoaddressthe7areasspecifiedbytheCPUCinitsPhase2Decisionon
developingaSubmeteringProtocol.
x Analyzedthefeasibilityofvarioususecasesidentified.
x Facilitated5weeksofteammeetingsspanningover30hoursofformaldiscussion,alongwith
numerousemailexchangesandindividualtelephoneconversations,toreviewsubmetering
requirementsandopenissueswithintheframeworkofthe7guidelinesspecifiedbytheCPUC.
x Providedweeklystatusreportstoallworkinggroupmembers.
x
CompletedinternalIOUreviewsandmeetingstoassesssubmeteringjurisdictionaland
consumerprotectionissuesanddevelopkeyprinciplestoguidethedevelopmentofa
SubmeteringProtocol.
3
Section source: PG&E, SCE, SDG&E
January3,2012
Page12
x ConductedanallhandsRoadmapReportDevelopmentTeamMeetingonDecember16to
presentdraftRoadmapissuesandimplementationrecommendationsandreceive3rdparty
comments.
x RespondedtoaNovember29,2011CPUCDataRequestforinformationonhowutilityAMIs
couldbeleveragedforsubmeteringdatacommunicationwiththeirindividualsubmittalson
December20,2011.
x Drafted,reviewed,andcompletedthisSubmeteringProtocolRoadmapReportandsubmitted
ittoCPUConJanuary3,2012.
2.2.3 Participants
InvitationstoparticipateinthecollaborativeweresenttoallmembersoftheAFVOIRServiceList.
ParticipantsintheteammeetingsandWebExconferencecallsincludedrepresentativesofthe
followingorganizations:
x
AeroVironment
x
DigiInternational
x
AlamedaCountyDept.of
Agriculture/Weights&Measures
x
ECOtalityNA
x
EVConnect
x
ArgonneNationalLaboratory
x
FordMotorCompany
x
BetterPlace
x
GeneralElectric
x
CaliforniaPublicUtilitiesCommissionEnergy
Division
x
Itron
x
x
PacificGasandElectricCompany
CaliforniaDepartmentofFoodand
AgricultureDivisionofMeasurement
Standards
x
PlugSmart
x
SanDiegoGas&Electric
x
SouthernCaliforniaEdison
x
SustainableUnlimitedMobilityGroup,
ProjectGreenOnRamp
x
CommunityRenewableSolutions,onbehalf
oftheGreenPowerInstituteandCommunity
EnvironmentalCouncil
x
Coulomb
x
Tendril,Inc.
x
DeloitteConsulting
ThinkSmartGrid
x
x
DivisionofRatepayerAdvocates
January3,2012
Page13
3. POLICYANDIMPLEMENTATIONDEPENDENCIES 4
3.1.1 OpenIssuesforRoadmap
x ThereareuncertaintiessurroundingthedevelopmentofthirdpartyEVchargingmarketsand
associatedwillingnessofEVcustomersorEVSPstopayforcostsofsubmeteringforsubtractive
billing.Developmentofcosteffectivenessandmarketassessmentsareneededtojustify
automatedIOUthirdpartysubtractivebillingprocesses,whicharenecessaryfirststepsinthe
evaluationofSubmeteringProtocols.
- Mitigationstrategy:furtherassessmentofsubmeteringforsubtractivebillingfeasibilityand
costeffectivenesscomparedtoalternativessuchasseparatemetering,andphased
implementationwithmanualprocessesandnonrevenuegradesubmeteringfornonbilling
purposesinneartermuntilandunlessthirdpartyandcustomersupported,revenuegrade
subtractivebillingisfeasibleandcosteffectiveinlongerterm.
x CommunicationsinterfaceandnationalstandardsincludingHANimplementationnotreadyyet.
- Mitigationstrategy:CoordinatewithandcompleteHANimplementationandopenSEP2.0
nationalstandardspriortoEVSubmeteringProtocol.
x EnforcementofSubmeteringProtocolincludingconsumerprotectionsandbillingdispute
resolutionuncertainunderPhase2decision(CPUCvs.Dept.Food&Agriculture).
- Mitigationstrategy:theCPUCneedstoclarifythePhase2decisionandestablishits
enforcementauthorityfortheSubmeteringProtocol,includingstandardsandbillingregulation,
meterinspectionandmaintenanceandresolvingconsumercomplaintsanddisputes.
3.1.2 ConsumerProtectionQuestions
x WhatistheCPUC’sjurisdictionoverSubmeteringProtocolandsubtractivebilling?
- Phase2ordersdevelopmentandadoptionofSubmeteringProtocolbyIOUs,butdoesnot
assertjurisdictiontoenforceitagainstthirdpartiesortoadjudicatebillingdisputesamong
utilities,thirdpartiesandcustomers.
- Phase2decisiondeferstoDept.Food&Agtoregulateandcertifymeteraccuracy.
x BecausethedecisionisunclearastotheCPUC’sjurisdiction,theCPUCshouldclarifyitsPhase2
decisiontoprovideforenforcementauthoritypriortomovingforwardwithfurtherSubmetering
Protocoldevelopment.
4
Section source: PG&E, SCE, SDG&E
January3,2012
Page14
3.1.3 GuidingPrinciplesforResolvingDependenciesRelatingtoEV
SubmeteringProtocolDevelopment
x SubmeteringprotocolwillfocusonmatterswithinCPUCjurisdictionbecausetheCPUCmust
enforcetheprotocolandresolvedisputesamongutilities,EVSPsandcustomers.
- Forexample,theprotocolwillfocusonhowsubmetersmaybeusedinlieuofIOUseparate
metersforIOUbillingpurposesinaccordancewithsimilarstandardsandprotocolsusedfor
customerownedseparatemetersundertheDirectAccess(DA)program.
- TheprotocolwillnotaddressEVSPthirdpartybusinessissues,suchasthetermsandconditions
ofathirdparty’ssaleofelectricityforuseasEVfuelbecausetheCPUC(initsPhase1decision)
determineditwillnotregulatethetermsandconditionsofthirdpartyfuelsales.
x TheprotocolwilladdresstherightsandobligationsofIOUs,customersandthirdpartiesastothe
useofsubmetersbycustomersandIOUsforIOUbillingpurposes.
x TheprotocolwillbedocumentedinCPUCapprovedtariffs,associatedtechnicaldocuments,and
costrecoverydecisions.
x TheIOUshaveanobligationtoaccuratelybilltheircustomers;consequently,theIOUswillcontinue
toseparatelymetertheirseparatecustomers.
x ForcustomerownedsubmetersusedbyIOUsforbilling,meterreadingand/ormetermaintenance
maybeofferedbytheIOUorbyqualifiedthirdpartiesconsistentwithDAmodel.
x BillingdisputeswillcontinuetoberesolvedbytheCPUCthesameasbillingdisputesgenerally.
x IOUcostsassociatedwiththeuseofsubmeteringorparallelmeteringforIOUbillingpurposeswill
besubjecttoreviewandcostrecoveryapprovalbytheCPUC,thesameasotherutilitycostsof
service.
January3,2012
Page15
4. USECASEEVALUATION 5
4.1 Background
4.1.1 PurposeandApplicationofUseCases
AUseCaseisastructuredscenariodevelopedfordiscussionpurposestoaidintheselectionand
planningofcomplextechnicalprojects.UseCasesenabletheevaluationofhowvarioussolutionsare
likelytoaffectcustomers,systems,andprojectstakeholders.Asaconsequence,UseCaseshelpproject
decisionmakersdeterminewhichapproachesarenotfeasibleandwhich,amongapproachesthatare
feasible,havethegreatestlikelihoodofsuccessforallstakeholders.UseCasesaregenerallyoneofthe
firststepsindevelopingbusinessandfunctionalrequirementsforcomplexprojects.
ObjectivityiskeytotheeffectivedevelopmentandreviewofUseCases.Thepreliminarydevelopment
oftheUseCasesinthisroadmapdoesnotmeananyoftheUseCasesarecurrentlyfeasible,cost
effective,desirable,orpreferredbycustomersorstakeholders.Thesoleassessmentincludedinthese
UseCasestodateisanassessmentoftechnologyfeasibilitywithoutregardtocosteffectiveness,
marketconditions,orcustomerdemand.ThelistingoftheUseCasesdoesnotindicateaconsensusor
preferenceamongtheIOUsorotherstakeholdersatthisstageofSubmeteringProtocoldevelopment.
4.1.2 UseCaseDevelopmentProcess
TheIOUsinitiallycreatedalistofUseCasesrepresentingseveralapplicationsofsubmetering.For
completeness,thelistwaspresentedto3rdPartiesandtheCPUC;thereupon,moreUseCaseswere
added.Thecollectiveeffort,throughdiscussionsamongtheseparticipants,helpeddefineandclarify
theidentifiedsetofUseCases.Eachusecaseassumesoriginalvehicle,chargingequipment,submeter
owner,andcustomeratoriginallocation.UseCasevariationsinvolvingresaleormovementof
equipmentand/orcustomersaddcomplexitytheIOUsarenotpreparedtoaddressatthistime.
AdditionalvariationsoftheseUseCasescouldalsopotentiallybedevelopedforfixed,mobile,single,
andmultiplesubmeterscenarios,basedonfurther3rdPartyrecommendations.
5
Section source: Primarily PG&E, SCE, SDG&E, based on working group team meetings, individual telephone
and email communication among utilities and third parties, and inter-utility communication.
January3,2012
Page16
4.1.3 UseCaseApplicationtoSubmeteringProtocolRoadmap
TheUseCaseswerethenevaluatedbytheIOUsusingasetofcriteriatodetermineaspectsofthe
actualimplementationthatcouldaidinthedevelopmentoftheroadmap.However,manyofthe
responsestotheevaluationcriteria,whichinturnaffecttheimplementation,provedtobedifficultto
defineandultimatelybecamesubjective.Becausesubmeteringisstillbeingconceptualized,therearea
numberofassumptionsthatweremadethatareeithercurrentlyuncertainorhavenotbeenfinalized,
oneexamplebeingtheOpenEVstandard.Becausemost,ifnotall,oftheevaluationcriteriatosome
extentdependonthesedetails,itwasdifficulttoclearlyrespondtoeachevaluationcriteria.
January3,2012
Page17
4.1.4 Overviewoffundamentalusecasestobeaddressed
USECASENUMBER*
andNAME
DESCRIPTION
0:Baseline:ParallelMetering
PremisesusageandEVusagearemeteredseparatelyusingtwoMaster
Meters.Subtractivebillingisnotrequired.
1:Residential(Basic)
A3rdPartysendsfixedsubmeterdatatotheutility,whothencalculated
Premisesusagethroughsubtractivebilling.PremisesisbilledbothEVand
premisesusage.
2:Residential(MultipleEVs)
VariantofUseCase1,withtheexceptionthattherearemultiplefixed
submetersononepremises.
3:SmallMultiDwellingUnit(MDU)
VariantofUseCase1,withtheexceptionthattherearemultipleMaster
Metersononepremises.
4:LargeMultipleMeter/CommercialUse
submetersononepremisesandmultiple3rdPartiessendingdatatotheutility.
5:No3rdPartyInvolvement
Theutilitycollectsfixedsubmeterdatathroughautilityspecifiedsolutionsuch
asaFieldAreaNetworkandcalculatesPremisesusagethroughsubtractive
billing.
6:Residential(Basic)w/EVSP
A3rdPartysendsfixedsubmeterdatatotheutility,whothencalculated
Premisesusagethroughsubtractivebilling.Premisesisbilledpremisesusage,
and3rdpartyisbilledEVusage.
7:Residential(MultipleEVs)w/EVSP
submetersononepremises.
8:SmallMultiDwellingUnit(MDU)w/EVSP
VariantofUseCase6,withtheexceptionthattherearemultipleMaster
Metersononepremises.
9:LargeMDU(Garage)w/EVSP
submetersononepremisesandmultiple3rdPartiessendingdatatotheutility.
10:Standard(MSub)
A3rdPartysendsmobilesubmeterdatatotheutility,whothencalculated
Premisesusagethroughsubtractivebilling.PremisesisbilledbothEVand
premisesusage.
11:InParallel(FSub+MSub)
CombinationofUseCase1andUseCase10,wheresubmetersareinparallel.
12:InSeriesw/oCrossTalk(FSub+MSub)
CombinationofUseCase1andUseCase10,wheresubmetersareinseries.
Mobilesubmetercommunicatescorrectly.
13:InSeriesw/CrossTalk(FSub+MSub)
CombinationofUseCase1andUseCase10,wheresubmetersareinseries.
Mobilesubmetercommunicatesincorrectly.
14:InSeries(2MSubs)
Twomobilesubmetersareinseries.Mobilesubmeterscommunicate
incorrectly.
15:AMI
VariantofUseCase5,withtheexceptionthatthesolutionistheutility's
existingAMINetwork.
16:DirectOpenEV
VariantofUseCase1,withtheexceptionthatthecustomersendsfixed
submeterdatatotheutility.
17:NetEnergyMetering
SubmeteringisusedonapremisesconfiguredforNetEnergyMetering
*PleasenotethatUseCasenumberinghaschangedsincetheOctober27,2011CPUCworkshop.
January3,2012
Page18
4.2 UseCaseEvaluation
4.2.1 Summary
TheUseCasepreliminaryanalysisperformedbytheIOUshasidentifiedwhichusecasescanbe
implementedintheshort,mid,andlongterm,andwhichcannotbeimplemented.TheIOUs
recognizetherearetechnologicaldevelopments,CPUCdirectionandfundingapprovals,andmarket
factorsthatwillaffectthetimeperiodsdescribedbelow:
Period/Use
Cases*
ShortTerm
MidTerm
LongTerm
Timing
Rationale
13yearsfromtheCPUC’sapproval
oftheSubmeteringProtocol.
Assumesatthispointintimethat
usecaseimplementationmay
requireonlymoderateinvestment
andlimited3rdpartyintegration.
24yearsfromapprovalofthe
SubmeteringProtocolandapproval
offundingforbackofficesystem
upgrades.
UseCasesimplementedinthemid
termarethoserequiringinvestment
oftimeandfundinginOpenEV
and/orAMI.
Beyondmidterm.
UseCasestobeimplementedinthe
longtermarebasedonnext
generationtechnologysuchas
mobilemetersandsmartgridfield
areanetworks.
* Actualshort,medium,andlongtermtimingcoulddifferamongutilities,basedondifferentsystems,technology,andsmartgridrolloutplans.
Short Term
LongTerm
MidTerm
1
15
5
Residential(Basic)
AdvancedMeteringInfrastructure
No3rdPartyInvolvement
2
16
10
Residential(MultipleEVs)
DirectOpenEV
Standard(MSub)
3
11
SmallMultiDwellingUnit(MDU)
InParallel(FSub+MSub)
4
12
LargeMultipleMeter/Commercial
InSeriesw/oCrossTalk(FSub+MSub)
17
Net Energy Metering
Not
Feasible
January3,2012
6
Residential(Basic)
w/EVSP
8
SmallMultiDwelling
Unit(MDU)w/EVSP
13
InSeriesw/CrossTalk
(FSub+MSub)
7
Residential(Multiple
EVs)w/EVSP
9
LargeMDU(Garage)
w/EVSP
14
InSeries(2MSubs)
Page19
4.2.2 Detailedevaluationofindividualusecases
Eachusecaseevaluationconsistsoffoursections:
x Description.
x Diagram.
x EvaluationCriteria(detaileddefinitionsbelow).
x KeyConclusions.
ThecriteriausedfortheimplementationanalysisofeachUseCaseareasfollows:
x TechnologicalCharacteristics
- Describesthetechnicalcharacteristicsofthedevicesneededtorealizeaparticular
scenario.Thesedevicescouldincludethemastermeter,submeter,premisesidentifier,
communicationnetworkand/oranyotherhardwareneededtoachievedesired
functionality.
x TechnicalAvailability
- Describestheavailabilityofhardwaresupportingusecasefunctionalityinthecurrent
marketenvironment.Thesecriteriaidentifydevicesthatarecurrentlynotavailableand
thosedevicesthatcanbeleveragedtoday.
x UtilityIntegration
- Summarizesananalysisoftherelativeeaseorcomplexitybywhichsubmeteringdevices
and/orhardwarecouldbeintegratedwithcurrentandplannedutilitysystemsforthe
purposeofbillingsubmeteredEVcharging.
x NationalStandards
- Identifiestheavailabilityand/orlackofnationalstandardsnecessarytoachieveusecase
functionality.
x Billing&Regulatory
- Identifiesthepossiblepositiveornegativeimpactseachusecasecanhaveonutility
billingsystemsand/orregulatorypolicy.
January3,2012
Page20
x UtilityCostofIntegration
- Evaluatesthevariousscenariosfromtheperspectiveoftheutilities’costtoimplement
theproposedusecase.
x CustomerExperience(Tobedeveloped.)
- Describesthepossibleexperiencescustomersmayencounterwhenapplyingaparticular
usecase.
- Aspartofprotocoldevelopment,theIOU’swillseekfurtherinputfrom3rdpartiesand
customersforeachusecase.
x CustomerCostFactors(Tobedeveloped.)
- Describesthepossiblecostimpactsonacustomerwhenapplyingaparticularusecase.
- Aspartofprotocoldevelopment,theIOU’swillseekfurtherinputfrom3rdpartiesand
customersforeachusecase.
January3,2012
Page21
UseCase0:BaselineParallelMetering6
ParallelmeteringispresentedhereasthefirstUseCasebecauseitisavailablecurrentlyand
becauseitprovidesabasisforcomparisonwiththeUseCasesdevelopedintheworkinggroups.
Description
x
ParallelsubmeteringconsistsoftwoMasterMetersonasinglePremises.
x
CustomerofRecordis:
- ThePremisesOwner(forPremisesUsage).
- EitherthePremisesOwnerora3rdParty(forEVUsage).
x
Submeterreadingservicesareperformedbya3rdPartyortheutility,whichreadstheFSuband
transfersusagedatatoitsDataManagementSystem(DMA).
x
PremisesUsageandEVUsagearemeasuredseparately.Subtractivebillingdoesnotoccur.
Diagrams
6
Copyright©2011SouthernCaliforniaEdison,PacificGasandElectricCompany,SanDiegoGas&ElectricCompany.
AllRightsReserved
January3,2012
Page22
UseCase0:BaselineParallelMeteringImplementationAnalysis
CRITERIA
Technological
Characteristics
TechnicalAvailability
DESCRIPTION
x MasterMetersareutilityownedfixeddevicesthatmeasureusageindependentlyanduse
theutilityAMINetwork.
x TheCustomerofRecordforeachMasterMeterisbilleditsrespectiveusage.
x Parallelmeteringusesexistingutilitynetworkinfrastructure.
x Parallelmeteringisavailabletoday.
x Nonrevenuegradesubmetersareavailabletoday.
x Parallelmeteringusesexistingutilitynetworkinfrastructure.
UtilityIntegration
x Nonationalstandardsarerequiredtoperformseparatebilling.
NationalStandards
x Usesexistingbillingprocessesandregulation.
Billing&Regulatory
x None.
UtilityCostofIntegration
x Tobedeveloped.
CustomerCost
x Tobedeveloped.
CustomerExperience
January3,2012
Page23
UseCase0:BaselineParallelMeteringKeyConclusions
Thisusecaseisalreadyavailablebecauseparallelmeteringiscurrentlyoffered.ThisUseCase
servesasabaselineforcomparisontoallsubmeteringscenarios.
January3,2012
Page24
UseCase1:ResidentialUseCase(Basic)7
Description
x
Thisusecaseconsistsofonesubmeter(FSub)ononePremises.
x
ThePremisesOwneristheCustomerofRecord.
x
Submeterreadingservicesareperformedbya3rdPartyorutility,whichreadstheFSubandtransfers
usagedatafromitsDataManagementSystem(DMA)totheUtility.
Diagram
7
Copyright © 2011 Southern California Edison, Pacific Gas and Electric Company, San Diego Gas & Electric
Company. All Rights Reserved
January3,2012
Page25
UseCase1:ResidentialUseCase(Basic)ImplementationAnalysis
CRITERIA
PERCEIVEDADVANTAGE
PERCEIVEDDISADVANTAGE
x Submetersarefixeddevicesandcan
provideaccurateelectricalassociation.
x Addedflexibility:Platformand
configuration.(I.e.canbeinmany
shapesandsizesaslongasitonly
measurestheEVload.
x Embeddedsubmetersposepotentiallycomplex
calibration,verification,securityprocedures.
x Standardutilitymetersandboxescan
beused.
x SomeEVSPhaveincludedembedded
submetersintheirbasicEVSEdesigns.
x Addedinfrastructure(meterbox)maybe
neededtoinstallasocketbasedmeter.
x NotallEVSEsincludeembeddedsubmeters.
calibration,verification,andsecurityprocedures.
UtilityIntegration
x “StagingServers”impacttheleastback
officesystems.
x Doesnotrequiretheutilitytoestablish
connectionswithpotentiallythousands
of3rdpartyowneddevices.
x Submeterdataisassociatedtoonlyone
mastermeter.
x NotallEVSPshavea“cloudservice”networkfor
communicationswithutilities.
x Althoughnotasextensiveasothersolutions,this
usecasestillimpactsutilityenterprisesystems.
(Effectsarestillunknown.).
NationalStandards
x NAESBESPIstandardratifiedonOctober x AnEVprofile(i.e.“OpenEV”)fortheESPI
2011iscurrentlyavailableforuse.
standardstillneedstobedeveloped.
Technological
Characteristics
x Dependenceontimingandaccuracyof3rdparty
supplieddata.
Billing&Regulatory
x Willrequiremanualcalculationand/or
adjustmenttoautomatedIOUbillingprocess.
x Utilityupgradecostsforimplementing
x Utilitiesareexpectedtoseekadditionalfunding
thisusecasemaybelowerthanthecost
forimplementationofa3rdPartyinterface
ofupgradingtheAMIsystem.
(costsarecurrentlyunknown).
x Fixedsubmeterestablishespersistent
associationbetweenpremisesandEV
comparedtomobilesubmetering.
CustomerCost
x Tobedeveloped.
x Tobedeveloped.
CustomerExperience
x Tobedeveloped.
x Tobedeveloped.
January3,2012
Page26
UseCase1:ResidentialUseCase(Basic)KeyConclusions
TheassessmentofthisUseCasehasledtheIOUstocategorizethisusecaseastechnically
implementableintheshortterm,because:
x ThenewlyratifiedNAESBESPIstandardallowsutilitiestoestablishUtility3rdPartydata
exchangeusingastandardizedmethod.
x Autilitystagingserverallowsutilitiestobypasscomplexbackofficesystemsinordertooffera
shorttermmanualsubmeteringprocess.
x Upgradingtoprovideautilityowned3rdpartystagingservermaybelesscostlythanupgrading
AMIbackofficesystems.
x Thisusecaseallowsutilitiesaphasedscalablesolution,withtheabilitytotransitionto
automatedbackofficesystemprocessingwhen(andif)itbecomesavailable.
x Thisusecasecouldalsotransitiontousecase#16(“DirectOpenEV”)andallowdirect
consumerutilitycommunications.
x Thecosteffectivenessandtimingfortechnicalimplementationarestillindeterminate,
comparedtoseparatemeteringandothernonsubtractivebillingoptions.
January3,2012
Page27
UseCase2:ResidentialUseCase(MultipleEVs)8
Description
x
ThisusecaseconsistsofmultipleFSubsononePremises.
x
x Submeterreadingservicesareperformedbya3rdPartyorutility,whichreadseachFSubandtransfers
usagedatafromitsDMAtotheUtility.
Diagram
8
Company. All Rights Reserved.
January3,2012
Page28
UseCase2:ResidentialUseCase(MultipleEVs)ImplementationAnalysis
CRITERIA
Technological
Characteristics
UtilityIntegration
NationalStandards
PERCEIVEDADVANTAGE
measurestheEVload.
beused.
officesystems.
mastermeter.
usecasestillaffectsutilityenterprisesystems.
x Multiplesubmetersaddalayerofcomplexity;
newprocessesmustbeestablishedtoidentify
eachsubmeter.
x Utilitieswillrequiremeterdatatablesforeach
submeter(notaggregateload).
supplieddata.
Billing&Regulatory
x Multipledatafeedsfrommultiplesubmeters
createorderofmagnitudeincreaseindata
processingandbillcalculationfunctions.
x Increasedsubmetersatapremiseswillincrease
processingtimeandburdenonsystems.
CustomerCost
x Tobedeveloped.
x Tobedeveloped.
CustomerExperience
x Tobedeveloped.
x Tobedeveloped.
January3,2012
Page29
UseCase2:ResidentialUseCase(MultipleEVs)KeyConclusions
TheassessmentofthisUseCasehasledtheIOUstocategorizethisusecaseasimplementablein
theshortterm,because:
x Upgradingtoprovideautilityowned3rdpartystagingservermaybelesscostlythan
upgradingAMIbackofficesystems.
January3,2012
Page30
UseCase3:SmallMultiDwellingUnit(MDU)UseCase9
Description
x
ThisusecaseconsistsofmultipleMasterMeters(MM)ononePremises.
x
x
Submeterreadingservicesareperformedbya3rdPartyorutility,whichreadseachFSubandtransfers
usagedatafromitsDMAtotheUtility.
Diagram
9
January3,2012
Page31
UseCase3:SmallMultiDwellingUnit(MDU)UseCaseImplementationAnalysis
CRITERIA
PERCEIVEDADVANTAGE
Technological
Characteristics
configuration.(I.e.canbeinmanyshapes
andsizesaslongasitonlymeasuresthe
EVload.)
x Standardutilitymetersandboxescanbe
used.
TechnicalAvailability x SomeEVSPhaveincludedembedded
x Addedinfrastructure(meterbox)maybeneededto
installasocketbasedmeter.
officesystems.
x Multiplesubmetersaddalayerofcomplexity;new
processesmustbeestablishedtoidentifyeach
submeter.
x Addedcomplexityinhavingtoassociatemultiple
submeterstomultiplemastermeters
x NAESBESPIstandardratifiedonOctober
x AnEVprofile(i.e.“OpenEV”)fortheESPIstandard
stillneedstobedeveloped.
supplieddata.
x Willrequiremanualcalculationand/oradjustment
toautomatedIOUbillingprocess.
x Criticaldependenceonassociatingthecorrect
submetertothecorrectmastermeteronmulti
meterpremises.
createsorderofmagnitudeincreaseindata
x Utilitiesareexpectedtoseekadditionalfundingfor
implementationofa3rdPartyinterface(costsare
currentlyunknown).
processingtimeandburdenonbackofficesystems.
x Associatingmultiplesubmeterstomultiplemaster
meterswillincreaseprocessingtimeandburdenon
backofficesystems.
UtilityIntegration
NationalStandards
Billing&Regulatory
UtilityCostof
Integration
x Tobedeveloped.
x Tobedeveloped.
CustomerExperience x Tobedeveloped.
x Tobedeveloped.
CustomerCost
January3,2012
Page32
UseCase3:SmallMultiDwellingUnit(MDU)UseCaseKeyConclusions
x Thecosteffectivenessandtimingfortechnicalimplementationofthisusecase,comparedto
separatemeteringandothernonsubtractivebillingoptions,isstilltobedetermined.
January3,2012
Page33
UseCase4:LargeMultipleMeter/CommercialUseCase10
Description
x
x
x
Submeterreadingservicesareperformedbyoneofmany3rdPartiesorutility,whichreadeachFSub
andtransfersusagedatafromtheirDMAtotheUtility.
x No3rdPartyFuelSupplier(BundledServiceCustomer).
Diagram
10
January3,2012
Page34
UseCase4:LargeMultipleMeter/CommercialUseCaseImplementationAnalysis
CRITERIA
Technological
Characteristics
UtilityIntegration
NationalStandards
PERCEIVEDADVANTAGE
configuration.(i.e.canbeinmany
measurestheEVload.
beused.
officesystems.
mastermeter.
(Effectsarestillunknown.).,
eachsubmeter.
x Dependenceontimingandaccuracyofmultiple
3rdpartydatamanagementagentsforutilityto
beabletobillsinglepremise.
Billing&Regulatory
meterpremises.
CustomerCost
x Tobedeveloped.
x Tobedeveloped.
CustomerExperience
x Tobedeveloped.
x Tobedeveloped.
January3,2012
Page35
UseCase4:LargeMultipleMeter/CommercialUseCaseKeyConclusions
January3,2012
Page36
UseCase5:No3rdPartyInvolvement(FieldAreaNetwork)11
Description
x
ThisusecaseconsistsofoneFSubononePremises.
x
x
Submeterreadingservicesarenotperformedbya3rdParty.Instead,theUtilityreadstheFSubusinga
utilitydefinedsolution.
Diagram
11
January3,2012
Page37
UseCase5:No3rdPartyInvolvementImplementationAnalysis
CRITERIA
PERCEIVEDADVANTAGE
x Submetersarefixeddevicesandcanprovide
accurateelectricalassociation.
Technological
Characteristics
configuration.(i.e.canbeinmanyshapes
andsizesaslongasitonlymeasurestheEV
load.
used.
UtilityIntegration
NationalStandards
Billing&Regulatory
UtilityCostof
Integration
CustomerCost
calibrationandverificationprocedure.
x Submetermanufacturermustadopttechnology
tobecompatiblewithutilitysolution;limits
submeterusetoasingleutilityserviceterritory.
calibration,verification,andsecurity
procedures.
x Mayrequire3rdPartytomanufacturehardware
x Doesnotrequiretheuseofanadditional
specifictoeachutility.
stagingserver.
x Requirestheutilitytoestablishconnectionswith
potentiallythousandsof3rdpartyowned
mastermeter.
devices.
x Potentiallycouldleverageasmartgridutility
x Addedinfrastructureisrequiredtosupport
fieldareanetwork.
utilitysolution,assumingAMIisnotused.
x Nonerequired.
x Requires3rdPartytomanufacturehardware
accordingtonationalstandardsfollowedbythe
utility,whichmaybeuniquetoeachutility.
x WillrequireIOUtooperatesubmeterdata
x UtilityasDMAremovesdependenceon3rd
retrievalsystem/network,andassumeprimary
partytosupplysubmeterdata.
responsibilityfordataintegrity,storage,
security,anddistributionto3rdparties.
x Utilitycostsforimplementingthisusecase
areunknownasautilitysolutionhasnot
forimplementationofa3rdpartyinterface
beendefined.
x Utilitywoulddevelopinfrastructureforutility
solution,addingconsiderablecost.
x Tobedeveloped.
x Tobedeveloped.
CustomerExperience x Tobedeveloped.
x Tobedeveloped.
January3,2012
Page38
UseCase5:No3rdPartyInvolvementKeyConclusions
thelongterm,because:
x Thisusecaserequiresthedevelopmentofautilityowned(IndependentfromtheAMIsystem)
fieldareanetwork.
x Thisnetworkisunlikelyuntillongtermsmartgridsystemsareimplemented.
x Technicalspecificationsofafieldareanetworkareunknown.
January3,2012
Page39
UseCase6:ResidentialUseCase(Basic)w/EVSP12
Description
x
ThisusecaseconsistsofoneFSubononePremises.
x
TheEVSP,a3rdPartyfuelsupplier,isaCustomerofRecordandthedomesticcustomerisaseparate
CustomerofRecord.
x
Submeterreadingservicesmaybeperformedbya3rdPartyorUtility,whichreadstheFSuband
transfersusagedatafromitsDMAtotheUtility.
Diagram
12
January3,2012
Page40
UseCase6:ResidentialUseCase(Basic)w/EVSPImplementationAnalysis
CRITERIA
Technological
Characteristics
UtilityIntegration
NationalStandards
Billing&Regulatory
CustomerCost
CustomerExperience
PERCEIVEDADVANTAGE
measurestheEVload.
beused.
procedures.
officesystems.
mastermeter.
x NAESBESPIstandardratifiedon
October2011iscurrentlyavailablefor
use.
procedures.
x Althoughnotasextensiveasothersolutions,
thisusecasestillimpactsutilityenterprise
systems.(Effectsarestillunknown.).
x AnEVprofile(i.e.“OpenEV”)fortheESPI
thisusecasemaybelowerthanthe
costofupgradingtheAMIsystem.
x Tobedeveloped.
supplieddata.
x Tobedeveloped.
x Tobedeveloped.
x Tobedeveloped.
January3,2012
Page41
UseCase6:ResidentialUseCase(Basic)w/EVSPKeyConclusions
TheassessmentofthisUseCasehasledtheIOUstocategorizethisusecaseasnotimplementable:
x BecausetheIOUshaveanobligationtoaccuratelybilltheircustomers,theIOUswillcontinue
comparedtothecurrentcapabilityoftheIOUs’AMI,separatemetering,andothernon
subtractivebillingoptions.
January3,2012
Page42
UseCase7:ResidentialUseCase(MultipleEVs)w/EVSP13
Description
x
x
TheEVSP,a3rdPartyfuelsupplier,isaCustomerofRecordandthedomesticcustomerisaseparate
CustomerofRecord.
x Submeterreadingservicesmaybeperformedbya3rdPartyorUtility,whichreadstheFSuband
Diagram
13
January3,2012
Page43
UseCase7:ResidentialUseCase(MultipleEVs)w/EVSPImplementationAnalysis
CRITERIA
Technological
Characteristics
PERCEIVEDADVANTAGE
measurestheEVload.
beused.
x Tobedeveloped.
x Tobedeveloped.
x Addedinfrastructure(meterbox)maybeneeded
toinstallasocketbasedmeter.
x “StagingServers”impacttheleastback x NotallEVSPshavea“cloudservice”networkfor
officesystems.
x Doesnotrequiretheutilitytoestablish x Althoughnotasextensiveasothersolutions,this
UtilityIntegration
x Submeterdataisassociatedtoonlyone x Multiplesubmetersaddalayerofcomplexity;
mastermeter.
eachsubmeter.
NationalStandards
use.
supplieddata.
Billing&Regulatory
forimplementationofa3rdPartyinterface(costs
arecurrentlyunknown).
x
Tobedeveloped.
x
Tobedeveloped.
CustomerCost
CustomerExperience
January3,2012
Page44
UseCase7:ResidentialUseCase(MultipleEVs)w/EVSPKeyConclusions
January3,2012
Page45
UseCase8:SmallMultiDwellingUnit(MDU)UseCasew/EVSP14
Description
x
ThisusecaseconsistsofmultipleMasterMeters(MM)ononePremises
x
TheEVSP,a3rdPartyfuelsupplier,isaseparateCustomerofRecord.
x Submeterreadingservicesmaybeperformedbya3rdPartyorutility,whichreadseachFSuband
Diagram
14
January3,2012
Page46
UseCase8:SmallMultiDwellingUnit(MDU)UseCasew/EVSPImplementationAnalysis
CRITERIA
Technological
Characteristics
PERCEIVEDADVANTAGE
measurestheEVload.
beused.
officesystems.
UtilityIntegration
NationalStandards
use.
Billing&Regulatory
procedures.
eachsubmeter.
x Addedcomplexityinhavingtoassociate
multiplesubmeterstomultiplemastermeters.
supplieddata.
meterpremises
createorderofmagnitudeincreaseindata
processingtimeandburdenonbackoffice
systems.
x Associatingmultiplesubmeterstomultiple
mastermeterswillincreaseprocessingtimeand
burdenonbackofficesystems.
January3,2012
Page47
CRITERIA
PERCEIVEDADVANTAGE
x Tobedeveloped.
x Tobedeveloped.
x Tobedeveloped.
x Tobedeveloped.
CustomerCost
CustomerExperience
UseCase8:SmallMultiDwellingUnit(MDU)UseCasew/EVSPKeyConclusions
January3,2012
Page48
UseCase9:LargeMDUUseCase(Garage)w/EVSP15
Description
x
x
TheEVSP,a3rdPartyfuelsupplier,isaseparateCustomerofRecord.
x
Oneofmany3rdPartiesperformssubmeterreadingservices,i.e.,readstheFSubandtransfersusage
datafromitsDMAtotheUtility.
Diagram
15
January3,2012
Page49
UseCase9:LargeMDUUseCase(Garage)w/EVSPImplementationAnalysis
CRITERIA
Technological
Characteristics
Technical
Availability
UtilityIntegration
National
PERCEIVEDADVANTAGE
andsizesaslongasitonlymeasurestheEV
load.
used.
officesystems.
connectionswithpotentiallythousandsof
3rdpartyowneddevices.
mastermeter.
x Addedinfrastructure(meterbox)maybeneededto
installasocketbasedmeter.
x Althoughnotasextensiveasothersolutions,thisuse
casestillimpactsutilityenterprisesystems.(Effects
arestillunknown.).
x Multiplesubmetersaddalayerofcomplexity;new
processesmustbeestablishedtoidentifyeach
submeter.
x AnEVprofile(i.e.“OpenEV”)fortheESPIstandardstill
needstobedeveloped.
Standards
x Tobedeveloped.
x Dependenceontimingandaccuracyofmultiple3rd
partydatamanagementagentsforutilitytobeableto
billsinglepremise.
x Willrequiremanualcalculationand/oradjustmentto
automatedIOUbillingprocess.
submetertothecorrectmastermeteronmultimeter
premises.
x Multipledatafeedsfrommultiplesubmeterscreates
orderofmagnitudeincreaseindataprocessingandbill
calculationfunctions.
currentlyunknown).
x Tobedeveloped.
x Tobedeveloped.
x Tobedeveloped.
Billing&
Regulatory
UtilityCostof
x Utilityupgradecostsforimplementingthis
usecasemaybelowerthanthecostof
upgradingtheAMIsystem.
Integration
CustomerCost
Customer
Experience
January3,2012
Page50
UseCase9:LargeMDUUseCase(Garage)w/EVSPKeyConclusions
January3,2012
Page51
UseCase10:StandardMobileSubmeterUseCase16
Description
x
x
x Submeterreadingservicesareperformedbya3rdPartyorutility,whichreadstheFSubandtransfers
x MobileSubmeter(MSubB1)isassociatedwithPremises1Accountandisproperlyattachedtothefixed
premiseidentificationdevice.Noothersubmetersarepresent.
AdditionalAssumptions
x
Alldataanddocumentsreceivedfromthethirdpartymustbeaccurate,whichwouldrequiresignificant
securitytesting(includingnegativetesting)toensuretheintegrityofthedatareceivedfromthese
mobilesubmeters.
x Premisesidentifiermustbecapableofverifyingcorrectelectricalconnectivityandsensingwhether
vehicleischargingatdesignatedlocation.
Diagram
16
January3,2012
Page52
UseCase10:StandardMobileSubmeterUseCaseImplementationAnalysis
CRITERIA
Technological
Characteristics
PERCEIVEDADVANTAGE
andsizesaslongasitonlymeasuresthe
EVload.
x Itisconceivablethattheremaybeinthe
neartermamobilemeterstandardand
automakerswouldbeabletoplacesuch
asubmeterinacaraslongasitmeets
protocolrequirements.
used.
x EVSPshavedevelopedsubmetersin
cordsets.
x Requiresundeterminedcommunicationbetween
submeterandPremisesIdentifier.
x Submeterisassociatedtomultiplemastermeters,
creatingcomplexityinregistrationandassociation.
x Currentlythereisnomethodforassociatingamobile
submetertoamastermeter.
x Currentlythereisnosystemavailableforinterutility
dataexchangefora“roaming”scenario.
x PremisesIdentifierandcommunicationwithithasnot
beendefinedyet.
x PossibleinfrastructuremustbebuilttoinstallPremises
Identifier.
x NotallEVsandcordsetsincludesubmeters.
x Leveragingmobilesubmetersforthepurposeofroaming
(interutilitychargingandbillreconciliation)willcontinue
tobeunavailableuntila3rdpartydevelopsaubiquitous
clearinghouseforchargingdataaggregation.
x Duetodifferentadditionsandexemptionsofassociations
betweensubmeterandmastermeter,thisusecase
heavilyimpactsutilityenterprisesystems.(Effectsare
stillunknown.).
x Mobilesubmetersaredifficulttoelectricallyassociate
withamastermeter.
x Submeterdatamaybeassociatedtomanymaster
meters,althoughcustomersmaynotnecessarilycharge
atallofthem.
x AnEVprofile(i.e.“OpenEV”)fortheESPIstandardstill
needstobedeveloped.
x Mobilesubmetersmayrequireadifferentsetof
standardsduetoruggedenvironment.
x PremisesIdentifiermayrequiredevelopmentofa
nationalstandard.
Technical
Availability
Utility
officesystems.
Integration
National
Standards
x Itisconceivablethattheremaybea
mobilemeterstandardinthenearterm.
x SAEiscurrentlyworkingonthetesting
andevaluationofPLCtechnologyfor
electricalassociation.
x Noneidentified
Billing&
Regulatory
January3,2012
x Dependenceontimingandaccuracyof3rdpartysupplied
data.
x IfEVchargesatmultiplepremisesduringsinglebilling
period,createsorderofmagnitudeincreaseindata
x Mobilesubmeterchargingindifferentmunicipality
jurisdictionscreatesUtilityUsertaxandFranchisetax
allocationissues.
x MobilesubmeterchargingindifferentIOUservice
territoriescreatesbillallocationandtaxallocationissues.
Page53
CRITERIA
PERCEIVEDADVANTAGE
UtilityCostof
x Utilitycostsforimplementinghardware
forthisusecaseareexpectedtobelower
thanusingtheAMIsystem.
x Tobedeveloped.
currentlyunknown).
x Duetoheavilyaffectedutilityenterprisesystems,
costsareassumedtobeveryhigh(Effectsarestill
unknown.).
x Tobedeveloped.
x Tobedeveloped.
x Tobedeveloped.
Integration
CustomerCost
CustomerExperience
UseCase10:StandardMobileSubmeterUseCaseKeyConclusions
x Itisconceivablethattheremaybeamobilemeterstandardintheneartermandautomakers
maybeabletoplacesuchamobilesubmeterinacaraslongasitmeetsprotocol
requirements.
x Inadditiontomeetingtechnicalperformancerequirements,mobilesubmeterswouldneedto
developamethodforassociatingtomastermeters.
x Untilperformanceandassociationissuesareresolved,utilitiesfindthatmobilesubmeteringis
nottechnicallyfeasible.
x Leveragingmobilesubmetersforthepurposeofroaming(interutilitychargingandbill
reconciliation)isnotfeasibleuntilaubiquitousclearinghouseforrevenuegradebillingdata
aggregationisdevelopedandavailableandotherissuesresolved.
comparedtothecurrentcapabilityoftheIOUs’AMI,separatemeteringandothernon
January3,2012
Page54
UseCase11:InParallelUseCase(FSub+MSub)17
Description
x
Thisusecaseconsistsofonemobilesubmeter(MSub)andonefixedsubmeterononePremises.
x
x
Submeterreadingservicesareperformedbya3rdPartyorutility,whichreadstheFSubandtransfers
x
Mobilesubmeter(MSubB1)isassociatedwithPremises1Account.FSubA1ispresent.Mobile
submeter(MSubB1)isproperlyattachedtothefixedpremiseidentificationdevice.Bothsubmeters
provideinformationtotheutility.
x
mobilesubmeters.
x Premisesidentifierwouldhavetobecapableofverifyingcorrectelectricalconnectivityandsensing
whethervehicleischargingatdesignatedlocation.
Diagram
17
January3,2012
Page55
UseCase11:InParallelUseCase(FSub+MSub)ImplementationAnalysis
CRITERIA
PERCEIVEDADVANTAGE
Technological
measurestheEVload.
Characteristics
UtilityIntegration
NationalStandards
x Requiresundeterminedcommunication
betweensubmeterandPremisesIdentifier.
x Submeterisassociatedtomultiplemaster
meters,creatingcomplexityinregistrationand
association.
x Currentlythereisnomethodforassociatinga
mobilesubmetertoamastermeter.
x Currentlythereisnosystemavailableforinter
utilitydataexchangefora“roaming”scenario.
x PremisesIdentifierandcommunicationwithit
beused.
hasnotbeendefinedyet.
x Possibleinfrastructuremustbebuilttoinstall
cordsets.
PremisesIdentifier.
x NotallEVsandcordsetsincludesubmeters
x Leveragingmobilesubmetersforthepurposeof
roaming(interutilitychargingandbill
reconciliation)willcontinuetobeunavailable
untila3rdpartydevelopsaubiquitous
officesystems.
x Duetodifferentadditionsandexemptionsof
associationsbetweensubmeterandmaster
meter,thisusecaseheavilyimpactsutility
enterprisesystems.(Effectsarestillunknown.)
x Mobilesubmetersaredifficulttoelectrically
associatewithamastermeter.
x Submeterdatamaybeassociatedtomany
mastermeters,andmaynotnecessarilycharge
atallofthem.
x PremisesIdentifiermayrequiredevelopmentof
anationalstandard.
January3,2012
Page56
CRITERIA
PERCEIVEDADVANTAGE
x Noneidentified.
x Tobedeveloped.
supplieddata.
x Multipledatafeedsfrommultiplesubmeters/DMAs
createsorderofmagnitudeincreaseindataprocessing
andbillcalculationfunctions.
x IfMobileEVsubmeterchargesatmultiplepremises
duringsinglebillingperiod,createsorderofmagnitude
increaseindataprocessingandbillcalculation
functions.
allocationissue.
territoriescreatesbillallocationandtaxallocation
issues.
currentlyunknown).
x Duetoheavilyimpactedutilityenterprisesystems,costs
areassumedtobeveryhigh(Effectsarestillunknown.).
x Tobedeveloped.
x Tobedeveloped.
x Tobedeveloped.
Billing&Regulatory
UtilityCostof
Integration
x Utilitycostsforimplementing
hardwareforthisusecaseare
expectedtobelowerthanusingthe
AMIsystem.
CustomerCost
CustomerExperience
January3,2012
Page57
UseCase11:InParallelUseCase(FSub+MSub)KeyConclusions
x Itisconceivablethatinneartermtheremaybeamobilemeterstandardandautomakersmay
beabletoplacesubmetersinthecaraslongastheymeetprotocolrequirements.
x Inadditiontomeetingtechnicalperformancerequirements,amethodwouldneedTobe
developed.forassociatingmobilesubmeterstomastermeters.
January3,2012
Page58
UseCase12:InSeriesUseCasew/oCrossTalk(FSub+MSub)18
Description
x
x
x
Mobilesubmeter(MSubB1)isnotassociatedwithPremises1Account.FSubA1ispresent.MSubB1
chargesatFSubA1insteadofchargingatitsdesignatedlocation.CrossTalkNotPresent.
x
securitytesting(includingnegativetesting)tobeperformedtoensuretheintegrityofthedatareceived
fromthesemobilesubmeters.
x Premisesidentifiermusteithercapablebeverifyingcorrectelectricalconnectivityandsensingwhether
vehicleischargingatdesignatedlocationorduetoattenuationneverreceivesthesignalfrommobile
submeter.
Diagram
Note:Communicationsbetweenthemobilesubmeterandfixedsubmeterisoutofscopeofthisdocument.
18
January3,2012
Page59
UseCase12:InSeriesUseCasew/oCrossTalk(FSub+MSub)ImplementationAnalysis
CRITERIA
Technological
Characteristics
PERCEIVEDADVANTAGE
measurestheEVload.
x Itisconceivablethattheremaybe
intheneartermamobilemeter
standardandautomakerswouldbe
abletoplacesuchasubmeterina
caraslongasitmeetsprotocol
requirements.
x Standardutilitymetersandboxes
canbeused.
cordsets.
x Embeddedsubmetersposepotentiallycomplexcalibration,
verification,andsecurityprocedures.
x Requiresundeterminedcommunicationbetweensubmeterand
PremisesIdentifier.
x Submeterisassociatedtomultiplemastermeters,creatingcomplexity
inregistrationandassociation.
x Currentlythereisnomethodforassociatingamobilesubmetertoa
mastermeter.
x Currentlythereisnosystemavailableforinterutilitydataexchange
fora“roaming”scenario.
Technical
Availability
UtilityIntegration
x “StagingServers”impacttheleast
backofficesystems.
x Doesnotrequiretheutilityto
establishconnectionswith
potentiallythousandsof3rdparty
owneddevices.
October2011iscurrentlyavailable
foruse.
mobilemeterstandardinthenear
NationalStandards
term.
x SAEiscurrentlyworkingonthe
testingandevaluationofPLC
technologyforelectricalassociation.
x Assumingfixedsubmeteris
accuratelyassociatedwithpremises,
utilityisagnostictomobile
submeterandwillaccuratelycharge
premises1customerforEVservice.
However,utilitywillhaveno
capabilitytodistinguishbetween
Billing&Regulatory
customerofrecordEVandany
otherEVthatchargesatpremises,
andwillassumeallEVchargingis
responsiblyofcustomerofrecord.
January3,2012
x PremisesIdentifierandcommunicationwithithasnotbeendefined
yet.
x PossibleinfrastructuremustbebuilttoinstallPremisesIdentifier.
x Leveragingmobilesubmetersforthepurposeofroaming(interutility
chargingandbillreconciliation)willcontinuetobeunavailableuntila
3rdpartydevelopsaubiquitousclearinghouseforchargingdata
aggregation.
x Embeddedsubmetersposepotentiallycomplexcalibration,
verification,andsecurityprocedures.
x NotallEVSPshavea“cloudservice”networkforcommunicationswith
utilities.
x Duetodifferentadditionsandexemptionsofassociationsbetween
submeterandmastermeter,thisusecaseheavilyimpactsutility
x Mobilesubmetersaredifficulttoelectricallyassociatewithamaster
meter.
x Submeterdatamaybeassociatedtomanymastermeters,andmay
notnecessarilychargeatallofthem.
x AnEVprofile(i.e.“OpenEV”)fortheESPIstandardstillneedstobe
developed.
x Mobilesubmetersmayrequireadifferentsetofstandardsdueto
ruggedenvironment.
x PremisesIdentifiermayrequiredevelopmentofanationalstandard.
x Dependenceontimingandaccuracyof3rdpartysupplieddata.
x Willrequiremanualcalculationand/oradjustmenttoautomatedIOU
billingprocess.
x IfMobileEVsubmeterchargesatmultiplepremisesduringsingle
billingperiod,createsorderofmagnitudeincreaseindataprocessing
andbillcalculationfunctions.
x Mobilesubmeterchargingindifferentmunicipalityjurisdictions
createsUtilityUsertaxandFranchisetaxallocationissues.
x MobilesubmeterchargingindifferentIOUserviceterritoriescreates
billallocationandtaxallocationissues.
x 3rdPartieswouldneedtoensurethatthereisnocrosstalkand
duplicationofdataforthesamechargingeventduetosubmeter
redundancy.
Page60
CRITERIA
PERCEIVEDADVANTAGE
UtilityCostof
x Utilitycostsforimplementinghardware
forthisusecaseareexpectedtobe
lowerthanusingtheAMIsystem.
x Tobedeveloped.
currentlyunknown).
x Duetoheavilyimpactedutilityenterprisesystems,
costsareassumedtobeveryhigh.(Effectsarestill
unknown.)
x Tobedeveloped.
x Tobedeveloped.
x Tobedeveloped.
Integration
CustomerCost
CustomerExperience
UseCase12:InSeriesUseCasew/oCrossTalk(FSub+MSub)KeyConclusions
x Itisconceivablethattheremaybeamobilemeterstandardintheneartermandautomakers
maybeabletoplaceinthecaraslongasitmeetsprotocolrequirements.
x Inadditiontomeetingtechnicalperformancerequirements,mobilesubmeterswouldneedto
developamethodforassociatingtomastermeters.
x 3rdPartieswouldhavetoensurethatcrosstalkisnotpresentandthereisnoduplicationof
dataforthesamechargingeventduetoredundancyinsubmeters.
January3,2012
Page61
UseCase13:InSeriesUseCasew/CrossTalk(FSub+MSub)19
Description
x
x
x Mobilesubmeter(MSubB1)isassociatedwithPremises1Account.FSubA1ispresent.MSubB1isnot
properlyattachedtothefixedpremiseidentificationdeviceatFSubA1creatingaduplicativescenario.
CrossTalkpresent.
x
mobilesubmeters.
x Premisesidentifierisnotcapableofverifyingcorrectelectricalconnectivityandsensingwhether
Diagram
19
January3,2012
Page62
UseCase13:InSeriesUseCasew/CrossTalk(FSub+MSub)ImplementationAnalysis
CRITERIA
PERCEIVED ADVANTAGE
Technological
measurestheEVload.
Characteristics
UtilityIntegration
NationalStandards
association.
cordsets.
hasnotbeendefinedyet.
PremisesIdentifier.
unlessa3rdpartydevelopsaubiquitous
officesystems.
atallofthem.
mobilemeterstandardinthenearterm
anationalstandard.
January3,2012
Page63
CRITERIA
PERCEIVEDADVANTAGE
x Noneidentified.
x Tobedeveloped.
data.
x Wouldrequiremanualcalculationand/oradjustmentto
x Withoutcapabilitytoreceivemobilesubmeterpremises
verification,Utilitywillreceiveduplicateusageforsame
chargingevent(fromfixedandmobilemeter),andmay
billbothusagevaluesinerror.
x IfMobileEVsubmeterchargesatmultiplepremisesduring
singlebillingperiod,createsorderofmagnitudeincrease
indataprocessingandbillcalculationfunctions.
allocationissues.
currentlyunknown).
areassumedtobeveryhigh(Effectsarestillunknown.)
x TheUtilitydoesnothavetheabilitytodetermineiftwo
metersareinseries.
x Tobedeveloped.
x Tobedeveloped.
x Tobedeveloped.
Billing&Regulatory
UtilityCostof
AMIsystem.
Integration
CustomerCost
Customer
Experience
UseCase13:InSeriesUseCasew/CrossTalk(FSub+MSub)KeyConclusions
TheassessmentofthisUseCasehasledtheIOUstocategorizethisusecaseasnotimplementable,
because:
x Utilitiesdonothaveamethodofknowingwhethertwosubmetersareinseries.
x Twosubmetersinseriesrecordingdataforthesamechargingeventcouldleadtoerroneous
billingdata,andthereforenationalstandardsandprocesseswouldneedTobedeveloped.by
bothutilitiesand3rdpartiestoavoidduplicatedataforthesamechargingevent.
x Utilitieswouldneedtodevelopprocessestoavoidduplicatedataforthesamechargingevent.
January3,2012
Page64
UseCase14:InSeriesUseCase(2MSubs)20
Description
x
Thisusecaseconsistsoftwomobilesubmeters(MSub)ononePremises.
x
x Separatemobilesubmetersbothinthevehicleandcordsetsendtheutilitytwoenergyconsumption
datatablesforthesametransaction/charging.
x
securitytesting(includingnegativetesting)tobeperformedtoensuretheintegrityofthedatareceived
fromthesemobilesubmeters.
x Premisesidentifierisnotcapableofverifyingcorrectelectricalconnectivityandsensingwhether
Diagram
20
January3,2012
Page65
UseCase14:InSeriesUseCase(2MSubs)ImplementationAnalysis
CRITERIA
PERCEIVEDADVANTAGE
Technological
measurestheEVload.
Characteristics
UtilityIntegration
NationalStandards
association.
cordsets.
hasnotbeendefinedyet
PremisesIdentifier.
untila3rdpartydevelopsaubiquitous
officesystems.
atallofthem.
x TheUtilitydoesnothavetheabilityto
determineiftwometersareinseries.
anationalstandard.
January3,2012
Page66
CRITERIA
PERCEIVEDADVANTAGE
x Noneidentified.
x Tobedeveloped.
data.
x Wouldrequiremanualcalculationand/oradjustmentto
x IfEVchargesatmultiplepremisesduringsinglebilling
period,createsorderofmagnitudeincreaseindata
allocationissues.
x Twometersinseriesreportingdatapertainingtothesame
chargingeventcouldleadtoerroneousbilling.
currentlyunknown).
areassumedtobeveryhigh.(Effectsarestillunknown.)
x Tobedeveloped.
x Tobedeveloped.
x Tobedeveloped.
Billing&
Regulatory
UtilityCostof
Integration
AMIsystem.
CustomerCost
Customer
Experience
UseCase14:InSeriesUseCase(2MSubs)KeyConclusions
TheassessmentofthisUseCasehasledtheIOUstocategorizethisusecaseasnotimplementable,
because:
x Utilitiesdonothaveamethodofknowingwhethertwomobilesubmetersareinseries.
x Twosubmetersinseriesrecordingdataforthesamechargingeventcouldleadtoerroneous
billingdata,andthereforenationalstandardsandprocesseswouldneedTobedeveloped.by
bothutilitiesand3rdpartiestoavoidduplicatedataforthesamechargingevent.
x Utilitieswouldneedtodevelopprocessestoavoidduplicatedataforthesamechargingevent.
January3,2012
Page67
UseCase15:AdvancedMeteringInfrastructure(AMI)UseCase21
Description
x
x
x CustomerownedsubmetercommunicatessubmeterdatatotheutilityviatheHANandthroughthe
AMIsystem.
Diagram
Electricity
UsageData
Billing
MasterMeterRead
Submeter Usage
PremisesUsage
Premises1
MM1
UtilitySystems
PU1
Staging
Server
Back
Office
FSubA1
AMI
21
January3,2012
Page68
UseCase15:AdvancedMeteringInfrastructure(AMI)UseCaseImplementationAnalysis
CRITERIA
PERCEIVEDADVANTAGE
measurestheEVload.
x AMImetershavetheabilityto
communicatewithHANdevices.
x AMImetershavetheabilitytostoreand
transmitdataforbackofficeprocessing.
x 3rdPartysubmetersmaysignificantlyimpactthe
mastermeter’smemoryallocation.
x Quantityofsubmetersatapremiseswillbe
limitedtothemaximumsupportedbythe
masterAMImeter.
x 3rdPartysubmetersmaysignificantlyimpactthe
mastermeter’sbandwidthbetweenthe
premisesandthebackoffice.
x 3rdpartydeviceswouldberequiredto
communicateviaZigbeeWirelessusingthe
SEP2.0messagingprotocol.
x AMIarecurrentlybeingdeployedand
areexpectedtobeavailablestatewide
byendof2012.
x SEP2.0enabledsubmetersarenonexistent
today.
x Submeterswouldleveragetheexisting
AMIlinktobackofficesystems.
x Submeterswouldleveragethesoonto
beestablishedHomeAreaNetwork.
x Significantlyimpactsutilitybackofficesystems,
includingthemetereddatamanagement
systems,datawarehouseandthecustomer
servicesystem.
x Doesnotallowforshorttermmanualsolution.
x Wouldrequirethedevelopmentofnewback
officeprocesses.
x Utilitiesarecurrentlysupportingthe
developmentofSEP2.0for
communications.
x NISTisexpectedtosupporttheuseof
SEP2.0forsmartgridHAN
communications.
x TheSAEsupportstheuseofSEP2.0for
communicatingEVmessagestothegrid
andhavedevelopedJ2847/1toaddress
itsimplementation.
x SEP2.0iscurrentlyunderdevelopmentandisnot
expecteduntilQ42012attheearliest.
x Furthermore,itistheIOU’sunderstandthat
automakershavenotfullyendorsedtheuseof
SEP2.0forutilitycommunications.
x Mayrequirethepotentiallytimeconsuming
developmentofCDFADMSand/orCounty
WeightsandMeasuresprocessestocalibrate
andverifymeteraccuracy.
x Noneidentified.
x Thisusecaseisexpectedtorequiresignificant
upfrontcostsasitdoesnotallowforaninterim
manualsolution.
CustomerCost
x Tobedeveloped.
x Tobedeveloped.
CustomerExperience
x Tobedeveloped.
x Tobedeveloped.
Technological
Characteristics
UtilityIntegration
NationalStandards
Billing&Regulatory
January3,2012
Page69
UseCase15:AdvancedMeteringInfrastructure(AMI)UseCaseKeyConclusions
TheassessmentofthisUseCasehasledtheIOUstocategorizethisusecaseasimplementable
onlyinthemidtermorlongterm,because:
x AMImetersarestillbeingdeployedandadequatetimeisnecessarytodeploymastermeter
backofficesystems.
x Backofficesystemsnecessarytosupportsubmeteringarenotcurrentlyplannedorfunded.
x SEP2.0isstillunderdevelopment.
x
Thesebackofficeupgradesareprimarilyonetimefixedcoststoupgradethesystem,butover
timetherewillbemaintenancecosts,aswellasnewmeters,standards,andcommunication
technologiesrequiringadditionalinvestment.
January3,2012
Page70
UseCase16:DirectOpenEVUseCase22
Description
x
x
x CustomerownedsubmetercommunicatessubmeterdatatotheutilityviaadirectOpenEVconnection.
x SimilartoAMIusecase,exceptthatitleveragesthestagingserverratherthanthebackoffice.
Diagram
Electricity
UsageData
Billing
MasterMeterRead
Submeter Usage
PremisesUsage
Premises1
UtilitySystems
PU1
OpenEV
MM1
Staging
Server
Back
Office
FSubA1
AMI
22
January3,2012
Page71
UseCase16:DirectOpenEVUseCaseImplementationAnalysis
CRITERIA
PERCEIVEDADVANTAGE
x Doesnotarequirea3rdpartycloud
service,butinsteadleveragesthe
customer’sInternetconnection.
x 3rdpartiesneedtodevelopOpenEVcompatible
submeters.
x DependentoncustomerInternet(whichcanbe
slow,out,orintermittent)fordata
communication.
x Noneidentified.
x SubmetersconformingtoOpenEVstandardare
notcurrentlyavailable.
UtilityIntegration
x Allowsfortheuseofastagingserver
withmanualbackofficeprocessing
x Scalabletoautomatedsystem.
x Investmentrequiredinstagingserverandinterim
manualprocesses.
NationalStandards
use.
standardwouldneedtobedeveloped.
x Communicationbetweencustomerand
utilitystagingserverisdirect,thereby
reducinghandoffsandinterimdata
storageneeds.
x PossibleInternetconnectionfailurescouldlead
customerstobechargedsolelyontheirdomestic
rate.
x Mayrequirethepotentiallytimeconsuming
developmentofCDFADMSand/orCounty
WeightsandMeasuresprocessestocalibrateand
verifymeteraccuracy.
(Effectsarestillunknown.)
CustomerCost
x Tobedeveloped.
x Tobedeveloped.
CustomerExperience
x Tobedeveloped.
x Tobedeveloped.
Technological
Characteristics
Billing&Regulatory
KeyConclusions
onlyinthemidtermorlongterm,because:
x Thisusecasewillleveragetheutilityinterfacestagingserverandthecustomer’sexisting
Internetconnection.
x Initiallythebackofficeprocesswillbemanualbuthastheabilitytobescalableandautomated
subjecttotheavailabilityoffuturefunding.
x NAESBESPIenabledproductsareyettobedeveloped.
January3,2012
Page72
UseCase17:NetEnergyMetering(NEM)BasicCase23
Description
x
x
x Customershaveinstalleddistributedgenerationequipmentandcurrentlyhaveanet(bidirectional)
meter.
Diagram
Electricity
UsageData
Billing
MasterMeterRead
Submeter Usage
PremisesUsage
Premises1
UtilitySystems
PU1
FSubA
DMA
NetMM1
OpenEV
Staging
Server
Back
Office
FSubA1
AMI
23
January3,2012
Page73
UseCase17:NetEnergyMetering(NEM)ImplementationAnalysis
CRITERIA
PERCEIVEDADVANTAGE
x
Thisusecasesupportsadvanced
applicationsofrenewableenergy.
x
Netmetersdonothavetheabilityto
disaggregategenerationandload.
x
NEMmetersareusedtoday.
x
Netmeterswiththerequireddisaggregation
functionalityarenotcurrentlyavailable.
x
Thisusecasecouldpotentiallyreduce
systemimpactofvehiclecharging
becauseNEMcustomerswouldbe
generatingtheirownpower,soNEM
couldreducecustomeruseofelectric
powerdeliveredfromtheutility.
x
Utilitysystemsarenotequippedtocalculate
billsinNEMsituationsinwhichcustomer
generationexceedscustomerconsumption
fromthegrid.
Thecapabilitytocorrectlynetout
consumptionandgenerationforbilling
purposeshasnotyetbeendeveloped.
Toensurethatalldifferentusagesarebilled
atthecorrectrate,acustomergeneration
submeterwouldberequired.
Meterdatamanagement,customer
information,andcustomerservicesystems
wouldalsoneedtobeupdatedtoestablish
customertomultimeterrelationships.
Thegenerationsubmeterwouldneedto
followthesamesetofstandardsastheEV
submeter.
NEMaddssignificantcomplexitytothe
billingprocessaswellastechnicalandtariff
issuestoberesolved.
Commercialratesarefurthercomplicated
becauseofdemandchargescurrently
applied.
Increasedpotentialforbillingdisputes.
Technological
Characteristics
UtilityIntegration
x
x
x
x
Noneidentified.
x
PotentialEVchargingloadsconsume
x
significantamountsofgeneratedpower
withinthecustomer’spremises,helping
reducetheneedforutilitybillingcredits x
fornetgenerationonanannualbasis.
NationalStandards
Billing&Regulatory
x
x
.
January3,2012
Page74
CRITERIA
PERCEIVEDADVANTAGE
x
UtilitiesarealreadyprocessingNEM
credits,sothisisfunctionalitythatdoes
nothavetobebuilt.
x
UtilityCostof
Integration
x
Existingutilitybillingsystemsarenot
equippedtocalculatebillswiththe
combinationofNEMandsubtractive
billingfortheEVsubmeter,insituations
wherethecustomer’sgenerationexceeds
totalpremisesusage,orexceedstotalEV
usageatthesubmeter.
Wouldrequireadditionalsubmetering
hardwareinordertodobilling
calculations.
Tobedeveloped.
x
Tobedeveloped.
x
x
Tobedeveloped.
x Tobedeveloped.
CustomerCost
CustomerExperience
UseCase17:NetEnergyMetering(NEM)KeyConclusions
onlyinthemidtolongterm,because:
x
Thecapabilitytocorrectlynetoutconsumptionandgenerationforbillingpurposeshasnotyet
beendeveloped.
x ItisunclearhowutilitieswouldprovideEVchargingbillingwhenpremisesnetloadsare0or
negative(generationexceedsconsumption).
January3,2012
Page75
5. SUBMETERINGIMPLEMENTATIONISSUESAND
REQUIREMENTS 24
5.1 SubmeteringImplementationIssuesandRequirements
5.1.1 Introduction
TherequirementsdevelopedbytheworkinggroupsaddresstheguidelinesspecifiedintheCPUC’s
Phase2decision:
1. Useofsubmetersinvariouslocations.
2. Technicalperformancerequirementsforsubmeters.
3. Minimumcommunicationfunctionalityandstandards.
4. SupportandprotectionofthesecurityandprivacyofEVuserdatacollectedbyutilitiesand
thirdpartyentities.
5. Methodologyforsettlingdisputes.
6. Compliancewithnationalstandardsformeasurementandcommunicationfunctions.
7. Rulesforincorporatingsubtractivebillingintosubmeteringtariffs.
Theserequirementsweredevelopedduringprojectworkinggroupmeetingsconductedbetween
SeptemberandDecember2011.Duetothenumberandcomplexityofissuesreviewedduringthis
period,thesubmeteringimplementationrequirementsdevelopedthusfarremainatafairlyhigh
levelandwillbesubjecttofurthercollaborationandinputfromallstakeholders.Thatsaid,the
requirementspresentedinthisdocumentdodescribethescopeofissuesanddependenciesthat
mustbeaddressedandresolvedbyutilities,theCPUC,theCDFADMS,and,toalesserextent,third
partiesinordertoimplementsubmetering.Furtherassessmentsanddetailedrequirementswillbe
developedasworkinggroupscontinuetoaddressSubmeteringProtocoldevelopmentplanningin
2012.
24
Section source: Primarily PG&E, SCE, SDG&E, based on working group team meetings, individual
telephone and email communication among utilities and third parties, and inter-utility communication.
January3,2012
Page76
ͷǤͳǤʹ Guideline1:
PleaseseeUseCaseSection4inthisRoadmapReport.
ͷǤͳǤ͵ Guideline2:
Inits5weeklymeetingsandindiscussionsanddraftdevelopmentinbetween,theSubmetering
ProtocolTechnicalRequirementsAnalysisteamreviewedsubmeteringtechnicaldesign,testing,
certification,audit,installation,maintenance,worker,andsafetyissues,arrivingatthefollowing
decisionsandconclusions.
x Definingsubmetertechnicalperformanceandfunctionaldesignrequirementsandstandards
requiresthefollowingactivities:
- IOUsdefineinfunctionaldesignrequirementsdocumentationtheconfiguration,usage,
andbillingparametersnecessarytosupportsubmeteringandsubtractivebilling,including:
à Formatofusageinformation.
à Percenterrortolerance.
à Submeter/utilitymetertimeanddatesynchronizationmethods.
à Localmeterreadingrequirementsandapprovalofmeterlocation.
à Meterdataestimationrequirements.
- CDFA/DMSassumesresponsibilityforadoptingspecificationsandestablishing
requirements,withtechnicalsupportfromIOUsandMSPs.
- MSPsassumeresponsibilityforimplementationoftechnicalrequirements,compliance,and
standards.
x Establishingrequirementsforsubmeterreliabilityrequiresthefollowingactivities:
- CDFA/DMSandCCWMcollaboratewithsubmetermanufacturerson:
à Developingareliabilitystatementandparametersspecifyingrequirementsfor
submeteraccuracythroughoutitsexpectedlife.
- CDFA/DMSandCCWMalso:
à Investigatetheappropriatelengthoftimeformeterrecertification,ifnecessary.
à BuildreliabilityrequirementsintoCDFA/DMStesting,certification,andauditing
policiesandprocedures.
January3,2012
Page77
x Establishingrequirementstoaddresspotentialsafetyrisksforcustomers,workers,and
equipmentrequiresthefollowingactivities:
- MSPsmapexistingstandardstothetypeofdevicebasedonelectricalandconnection
parameters.
- CDFA/DMSestablishesequipmentsafetyrequirements.
- Buildingcodedepartmentsestablishinstallationsafetyrequirements.
x Establishingprocessestocertifyandauditsubmetersandrelatedsubmeteringequipmentand
sitesrequiresthefollowingactivities:
- CDFA/DMSdevelopscertificationandauditprocessesandpolicies,including:
à Sampling.
à Testing.
à Recertification.
à Howsubmetermanufacturerscanselfcertifythesubmeter.
à Howaccuracyauditscanoccurwithsubmetersembeddedinotherequipment.
à HowEVSE,cordset,andautomakersubmetermanufacturerssubmit:
·
Newmetertypesforinitialcertification.
·
NewproductsassoldtoCountyWeightsandMeasures.
·
Operatingsubmetersforrecertification,ifnecessary.
- IOUsprovidefunctionaldesignrequirementsdocumentation.
- IOUsandMSPsprovidetechnicalsupport.
x Establishingrequirementsforsubmeterinstallation,maintenance,andtestingofsubmeters
andrelatedequipmentcompatiblewithutilitymeterusagedatarequiresthefollowing
activities:
- IOUsprovidedirectionintheformoftariffedrulestoMSPsonkeyrequirementsandhowto
workeffectivelywithutilities,includingrequirementsfor:
à Deenergizingcircuitsduringsubmeterinstallation.
à Associatingeachsubmeterwithaparticularpremisesmeter/accountandnetwork
(registration)infixedandmobilemeterscenarios.
à Establishingcommunicationbetweensubmeterandpremisesmeter.
January3,2012
Page78
- MSPsassumeresponsibilityforimplementingsubmeterandrelatedequipmentinstallation,
maintenance,andtestingrequirements,including:
à Obtainingdataforverificationpurposes.
à Recognizingwhenameterisoutoftolerance.
à Fixing/updatingsubmetersoftware,firmware,andhardware.
à Handlingreconfigurationsbasedonchangesinutilityratesandprograms.
à Testingandverifyingsubmetertestingequipment.
x Establishingrequirementsforthecertificationofsubmeterworkersandprovidersrequiresthe
followingactivities:
- IOUsproviderecommendationsforworkerrequirements.
- DMSdevelopsguidelines.
- MSPsdevelopandimplementworkertraining,certification,andauditingprocessesand
content.
ConclusionsofSubmeteringTechnicalRequirementsAnalysisTeam
TheSubmeteringProtocolTechnicalRequirementsAnalysisteamarrivedatthefollowing
conclusionswithrespecttocompletingtheaforementionedactivities:
x SignificantcollaborationwillcontinuetoberequiredbetweentheIOUs,submeter
manufacturers,automakers,andCaliforniainspectionandcertificationauthoritiesthroughout
theSubmeteringProtocoldevelopmentprocess,with:
- IOUsprovidingtechnicalrequirements,guidelines,recommendations,andsupportto
MSPs,CDFA/DMS,andCCWMoffices.
- CDFA/DMSandCCWMofficesdevelopingequipmentaccuracy,reliability,installation,
testingequipment,worker,andsafetyrequirementsbasedonbothIOUandMSPinput.
- MSPsengineeringfunctionalityandbuildingequipmentmeetingtherequirementsof
CDFA/DMSandCCWMandfactoringintherecommendationsoftheIOUs.
January3,2012
Page79
x Tofutureproofsubmeterdesigns,functionalityshouldinclude:
- Bidirectionalcapabilitiesenablingvehicletogridfunctionality.
- Demandresponsecapabilitiesenablingloadcontrol.
- NEMcapabilitiesenablingthecombinedmeasurementofselfgenerationandbattery
charging.
- Remotefirmwareandconfigurationupdatecapabilities.
x CDFA/DMSandCCWMhavenotinthepastworkedwithtimeofusesubmeters,submeters
embeddedinotherequipment,orsubmetersrelyingonremotecommunication.
- Establishingtherequiredcertification,testing,auditing,andrecertificationrequirements,
processes,andpoliciescouldtakeaconsiderableamountoftime.
5.1.4 CommunicationRequirements
CommunicationFunctionality,Standards,Securityteamreviewedandevaluatedissues
concerning:
x Guideline3:Minimumcommunicationfunctionalityandstandards.
x Guideline4:SupportandprotectionofthesecurityandprivacyofEVuserdatacollectedby
utilitiesandthirdpartyentities.
x Guideline6:Compliancewithnationalstandardsformeasurementandcommunication
functions.
KeyFindings
x EstablishinganinterfacebetweenMSPsandutilitiestoshare3rdpartysubmeteringdatafor
billingpurposesrequiresthefollowingactivities:
- DraftanEVProfilewithintheCommunicationsteamandprovideittoOpenSGOpenADE
forevaluation.
January3,2012
Page80
- Developa3waysubmeteringagreementfor3rdpartysubmeteringdocumentedinutility
tariffs.
à Theactualthreewayagreementismostlikelytobeexecutedviaawebportaland
storedelectronicallywiththeDataCustodian(DataCustodianneedstobe
determined).
- IdentifyrequirementsforrevisionstoESPI(e.g.,advancedusecases).
- FacilitatetheimplementationofanESPIsubmeteringprofileonutilityandMSPsystems.
- Ensurecommunicationtesting,certification,interoperability,andsecurity.
à Scopeofteamhandlingtesting,certification,andsecurity/privacyisyettobe
determined.
x MakingthebestuseofIOU,MSP,andotherstakeholdertimeandeffortrequiresparticipation
inUCAIugandOpenSGOpenADEcommitteesandactivitiestoaddress:
- ESPIconformancecertificationandinteroperability.
- Interoperabilitytesting.
- Testplansandrequirements.
x
Identifyhowcommunicationrequirementsrelatedtoprivacyandsecurity—contractual
agreements,privacyandsecurity,certification,etc.—aredefined,implemented,andenforced,
including:
Whoownsthe“globaleffort”ofensuringdatasecurity.
Whatlevelshouldbeattained(e.g.,HIPAA,PCIcreditcardscouldbeusedasbenchmarks).
Responsibilityandwherethisworkshouldbecompleted.
Whetherexistingstandardsavailableorinplacearesufficient.
Other(Liability,connectiontoongoingCPUCwork,scope,etc.).
x
Othernecessarysubmeteringprofilework(requirementsidentification,revisions,etc.),
includingtheidentificationofusecasespotentiallyinvolvingstandardizedcommunicationsfor
submeters.
January3,2012
Page81
ConclusionsofSubmeteringCommunicationsAnalysisTeam
TheSubmeteringProtocolCommunicationsRequirementsAnalysisteamarrivedatthefollowing
conclusionswithrespecttocompletingtheaforementionedactivities:
x DevelopingcommunicationfunctionalityfortheSubmeteringProtocolisbestservedby
leveragingexistingstandardsandstandardsdevelopmentorganizations,including:
- NAESBESPI.
- OpenSGOpenADE.
- OAuth.
- Benchmarking.
5.1.5 Billing&RegulatoryAnalysis
BillingandRegulatoryAnalysisteamreviewedissuesrelatingto:
x Guideline5:Methodologyforsettlingdisputes.
x Guideline7:Rulesforincorporatingsubtractivebillingintosubmeteringtariffs.
KeyFindings
x Amendingtariffsordevelopingnewruleswillrequirethefollowingactivities:
- Identifypotentiallynecessarytariffprovisions–e.g.,registration,enrollment,billing
arrangements,fees,disputeresolution,technicalperformance,eligibility,etc.
- Modifytariffs(rateschedulesandrules)orcreateanewtariff(anewrulewithreferenceto
atechnicalprotocol,orothersolution)asnecessarytoalignwithapprovedProtocol.
- Developanynecessarynewtechnicalprotocoldocumentsandformsviaworkingprocess.
- Fileformalapplicationsand/orTier2AdviceLetter(s)withtheCPUCtoformallyapprove
tariffedprotocol(s)andtofullyrecoverfixedandvariablecostsofsubmeteringfor
subtractivebilling,includinganyAMIandbillingsystemupgradecosts.
January3,2012
Page82
x Anticipatingandaverting–totheextentpossible–challengescausedbythecomplexityof
customerMSPutilityrelationshipsrequiresthefollowingactivities:
- Definerolesandresponsibilities,rightsandobligations,andperformanceexpectations.
- Identify,describe,anddevelopmitigationstepsforanticipateddisputes.
- Identifyanddescribeincrementalinfrastructureneededtoaddressdisputes.
- Reviewadequacyofexistingrulesandfilenewrulesasnecessary.
submeteringdatacollectionandsubtractivebillingforDirectAccess(DA)andCommunity
ChoiceAggregation(CCA)customersrequiresthefollowingactivities:
- IdentifyrightsandobligationsinthecontextofDAandCCA.
- ExpanddisputeresolutionapproachesandstepsifnecessarytoaddressDAandCCA
customers.
combiningsubmeteringandNEMservicesrequiresdetermining:
- ThetechnicalandregulatoryfeasibilityofcombiningNEMandsubmeteringservices.
- MeasurementneededtointegrateNEMandEVSubmetering.
- Tariffrequirementsresultingfromintegration.
- Technologycapabilitiesneededtoprocessintegratedbilling.
- ExpanddisputeresolutionapproachesandstepstoaddressNEMcustomers.
x EstablishingrequirementsforcertificationofDataManagementAgentsprovidingdatafor
billingpurposesrequiresthefollowingcollaboration:
- IOUsproviderecommendationsbasedonDirectAccessexperience.
- MSPscomplywithCPUCapprovedrequirementsandimplementpoliciesandprocedures.
January3,2012
Page83
Determininghowtorecoupincrementalutilitycostsassociatedwithsubmeteringinvolvesthe
followingactivities:
- Identifyincrementalmetering,billing,customerservice,andinformationsystemcosts
associatedwithsubmetering.
- IdentifycapitalandO&Minvestmentsassociatedwithnewrequirements,anddetermine
whethersubmeteringrelatedcostsare:
à IncrementaloralreadyaccountedforintheGRC.
à OverlappingwithcostsincludedinMSPbusinessmodels.
SubmeteringImpactonIOUBillingSystems
InadditiontoparticipatingintheweeklyBillingandRegulatoryteammeetings,IOU
representativesinvestigatedtheimpactonbackofficeutilitybillingsystemsofusingsubmetersto
trackandcommunicateEVchargingloadinstandard,demandresponse,andnetenergyutility
servicescenarios.Anew,requiredsubmeteringbillingprocess—asdepictedintherighthand
columnbelow—changeshowtheutilitymanagescustomerpowerusage,andsubmetering
customerratesandcharges,allbillingprocesseswouldinturnaffectallexistingrates.
January3,2012
Page84
StandardUtilityServiceScenario
ExistingBillingProcessesand
SystemSteps
BillingProcessesandSystemStepswith
theAdditionof3rdPartySubmeters
SupplyingUsageData
1. Createcustomerofrecord
1. Createnewcustomersofrecordforsubmeters
2. Associatemetertothecustomer
2. Associatesubmeterswithmastermeterstoallow
subtractivebilling
3. Assignrateclasstocustomer’susage
4. Assignothercustomerchargestothecustomer’s 3. Assignrateclasstosubmeters
bill
4. Receiveandprocess3rdpartydata
5. Calculatebillchargesforspecificperiodandrate 5. Performanalysisbyintervalofusageon
version
submetersandassociatedmastermeter,notify
3rdpartyDMAofanydataanomalies/omissions
6. Printandsendbillandpopulateusageandbilling
infotowebportalforcustomeraccess
6. Reprocesscorrecteddatasubmittedby3rdparty
DMA,ifany
7. Createnewbillwithoverallusageandsubmeter
usage
8. Assigncoststoonlyresidualmastermeterusage
(MMminusSubM)
9. Assigncoststosubmeters
10. Assignothercustomerchargestosubmeterbills
andmastermeterbills
11. Printandsendbillandpopulateusageandbilling
infotowebportalforcustomeraccess
WhileautomatedmassbillingsystemsandprocessesaredevelopedbyPG&E,SCE,andSDG&E
temporarysolutionswillberequiredtoproducesubtractivebillingfromsubmetergenerateddata.
Itisexpected,then,thatduringthisperiod—potentiallyseveralyears—subtractivebillingwillneed
tobehandledviaa“specialty"billingsystemwithmorelaborandathighercostthanthe
automatedmassbillingsystemTobedeveloped.Thisshorttermsolutionimpliestheneedfor
multipletransitionalstages:thefirstfromcurrentsystemsandprocessestotheinterimmanual
solution,andthenfromtheinterimsolutiontotheautomatedmassmarketsystem.
AndwhiletheIOUs’currentsystemsareautomatedandintegratedtohandletraditionalbilling
requirements,theuseoftheAMInetworktocollectsubmeterdataforsubtractivebillingwould
requirefurthersoftwareupdatesandintegrationtoautomatebackofficebillingforsubmeter
data.
January3,2012
Page85
5.1.6 AnalysisofOtherImpactsonSubmetering,SubtractiveBilling,and
IOUBillingSystems
Thefourworkinggroupsidentifiedotherkeyquestionsmeritingadditionalconsideration.The
utilitiesunderstandthesequestionstonotbeinscopeatthistimebutwewillkeepthemunder
considerationastheprotocolisdevelopedandaddressthemasdirectedbytheCommission:
1. HowwillDemandResponseprogramsbeaffectedbysubmeteringforsubtractivebilling?
2. HowwillNetEnergyMeteringprogramsbeaffectedbysubmeteringforsubtractivebilling?
3. HowwillQuickChargingstationsbeaffectedbysubmeteringforsubtractivebilling?
4. HowwillMobileHomeParkbillingbeaffectedbysubmeteringsubmetersforsubtractive
billing?
5. Whatimpactsonthegridmaybecausedbymovingawayfromparallelmeterstosubmeters
forsubtractivebilling?
6. ShouldtheSubmeteringProtocolincludefunctionalityenablingvehicletogridcapability?
January3,2012
Page86
6. SUBMETERINGROADMAP 25
6.1 MultiStageRoadmapOverview
TheRoadmaptimelinethatfollowsillustratesalongterm,multiphaseviewofSubmetering
Protocolplanning,development,andimplementation,providedthatkeycosteffectiveness,
marketdevelopment,andcustomerpreferenceissuesareresolved.Keyelementsaredescribedin
sections6.1.1–6.1.5below.
6.1.1 DetailedRoadmapforPhase1–Define/Plan(Complete)
ThisinitialplanningphaserepresentsthecreationofaCaliforniaSubmeteringProtocolroadmap,
whichhasbeendevelopedbytheprojectworkinggroupsanddetailedinthisreportdocument.
ReasonsfortheinitialfocusontheCaliforniamarketincludeIOUoperationandCPUCjurisdiction
inCaliforniaandthetimerequiredtoestablishnationallyacceptedstandards.Protocol
developmentworkisplannedtofacilitatenationalacceptance.Duringthisphase,customerand
3rdpartyownedsubmeteringisavailabletocustomersfornonbillingpurposes.
6.1.2 DetailedRoadmapforPhase2–Design/DevelopCalifornia
SubmeteringProtocol
Phase2consistsoftheactivitiesrequiredtodevelopaCaliforniaSubmeteringProtocol.Asin
Phase1,customerand3rdpartyownedsubmeteringisavailabletocustomersfornonbilling
purposes.KeyPhase2activitiesinclude:
x Completinganassessmentofcustomerneeds,technologicalandregulatorydevelopments,
and3rdpartyproduct,service,andmarketplans:
- Inordertofocusenergiesandleverageresourcesappropriatelytheprojectteamhas
determinedthatitmustmaintainanuptodateunderstandingofthemarketplaceasit
continuestoevolve.
25
Section source: PG&E, SCE, and SDG&E
January3,2012
Page87
x Foreachusecaseapplicableinthephase:
- Developingbusinessrequirementsandspecificationsforutilities,customersand3rdparty
MSPs.
- Developingtechnical,security,privacyrequirements,specifications,andstandardsaligned
withnationalstandards.
- Developingarchitecturaldesignforendtoendsystems(includingbackofficeintegration).
- Developingimplementationstrategyandplan,schedule,tasks,anddeliverables.
6.1.3 DetailedRoadmapforPhase3–BuildInterimCaliforniaSolution
Phase3consistsofimplementingaSubmeteringProtocolsolutionmakingcustomerand3rdparty
ownedsubmeteringavailabletocustomersinCaliforniaforbillingpurposes.Inthisphaseutilities
willbeabletoexecutemanual,smallscalesubtractivebillingofEVchargingloads.KeyPhase3
activitiesinclude:
x Building,testing,andrefiningthenecessaryprocesses,systems,andsysteminterfaces.
x Pursuingdevelopmentofnationalstandardsforsubmetersandsubtractivebilling.
x Establishingtariffsgoverningutility,customer,and3rdpartymeterserviceproviders.
x Developingcertificationprocessfor3rdpartydevices,systems,processes.
x Developingandcarryingoutcustomerinformationcampaigns.
6.1.4 DetailedRoadmapforPhase4–BuildScalableLongTermSolution
Phase4continuestoenablecustomerand3rdpartyownedsubmetering;howeverinthisphase
nationalstandardsarecompleteandimplemented,andutilitieswillbeabletoexecuteautomated,
fullscalesubtractivebillingofEVchargingloads.KeyPhase4activitiesinclude:
x Upgradingutilitysystemstohandleautomated,fullscalesubtractivebilling.
January3,2012
Page88
6.1.5 DetailedRoadmapforPhase5–BuildSmartGridSolution
Phase5representslongtermsolutionsincluding:
x
UtilitiesdeploySmartGridfieldareanetworkscapableofcommunicatingwithcustomer
devices.
x
NationalStandardsareinplaceenablingtheuseofPowerLineCommunicationsfor
associatingmobilesubmeterstomastermeters.
x
NEMmetershavetheabilitytoreportdisaggregateddata(loadandgeneration).
KeyPhase5activitiesincludeutilities:
x
Verifyingthatmobilesubmetersaredeployedconsistentwithalltechnicalandbilling
requirements.
x
LeveraginginvestmentsinSmartGridTechnologiesbyusinganadvancedfieldareanetworkto
collectcustomersubmeterdata.
x
Assessingthemarketvalueofinterutilitycommunicationstoaddressvehicle"roaming".
January3,2012
Page89
January3,2012
• Completeandsubmitthe
SubmeteringRoadmapReport
- Responsibleorganizationsand
individualsforeach
- Keytasksoractivitiesand
timingforeach
• Developcertificationprocessfor3rd
partydevices,systems,processes
• Enable3wayhandshakeamongthe
utility,customer,and3rd partymeter
serviceprovider
• Pursuedevelopmentofnational
standardsforsubmetersand
subtractivebilling
• Implementasolution build,test,and
refinethenecessaryprocesses,
systems,andsysteminterfaces
- Implementationstrategyandplan,
schedule,tasks,anddeliverables
- Architecturaldesignforendto
endsystems(includingbackoffice • Developandcarryoutcustomer
integration)
informationcampaign
- Technical,security,privacy
requirements,specs,and
standardsalignedwithnational
standards
- Businessrequirementsandspecs
forutilities,customersand3rd
partymeterserviceproviders
- Marketplaceunderstanding
• Develop a CaliforniaSubmetering
Protocol
relatedcosts
• Utilitiesexecutemanual,smallscale
subtractivebilling ofEVchargingloads
• Submeter dataforIOUsubtractive
billing tobeprovided according to
protocol(includessubmeterID,
premiseID,anddate/timestamped
intervalusage)
• SubmetersforIOUsubtractivebilling
areownedbycustomersor3rd parties
• Nationalstandardsare
implemented
• Upgradeutilitysystemstohandle
automated,fullscalesubtractive
billing
relatedcosts
• Utilitiesexecuteautomated,full
scalesubtractivebilling
• SubmeterdataforIOUsubtractive
billing tobeprovidedaccordingto
protocol
• Submetersforsubtractivebilling are
ownedbycustomersor3rd parties
• NationalStandardsareinplace
• Assessthemarketvalueofinterutility
communicationstoaddressvehicle
"roaming"
• LeverageinvestmentsinSmartGrid
Technologiesbyusinganadvancedfield
areanetworktocollectcustomersubmeter
data
• Verifythatmobilesubmetersaredeployed
consistentwithalltechnicalandbilling
requirements
• NEMmetershavetheabilitytoreport
disaggregateddata(loadandgeneration)
• NationalStandardsareinplace(PowerLine
Communications)forassociatingmobile
submeterselectricallytomastermeters
• UtilitiesdeploySmartGridfieldarea
networkscapableofcommunicatingwith
customerdevices
• DivisionofMeasurementStandardshas
developedandimplementedproceduresfor
certifyingmobilemeters.
• Mobilemetersmeettechnicalperformance
andcertificationrequirementsaremarket
available.
NEXTGENERATION
TECHNOLOGYISAVAILABLE
LongTermImplementation
DESCRIPTION
- ListofIssuesand/or
RequirementsandPreliminary
Recommendations
- Goals,objectives,scope,
guidelines
• Define aCaliforniaSubmetering
ProtocolRoadmap
• IOUcustomerscaninstallasubmeter,eitherownedbythecustomer
ora3rd party,andreceiveusagedatafromthose(nonutility)sources
forenergymonitoring
• IOUcustomerscanaddaparallelmeterservicepanelforadedicated
utilityownedandreadparallelmeter forEVchargingandbilling
• IOUcustomerscancontinuetousetheutility’ssinglewholehouse
meter,whichincludesEVchargingandbilling
• IOUcustomersmayhavethechoiceofresidentialandseveralEV
rates
MidTermImplementation
AVAILABLETOCUSTOMERSFORBILLING PURPOSES
AVAILABLETOCUSTOMERSFORNONBILLING PURPOSES
ShortTermImplementation
Phase5
BuildSmartGridSolution
CurrentPlanningandDevelopmentofSubmeteringProtocol
Phase4
BuildScalable
Solution
Phase3
BuildInterimSolution
Phase2
Design/Develop
Phase1
Define/Plan
ACTIVITIES
Page90
An analysis of the use
cases must be
performed
Short-term decisions
may impact long-term
approaches, costs,
timing, etc.
x
x
x
x
x
x
x
x
x
x
x
x
Identify which use cases are short term and
which are long term
Use Direct Access as a starting point /
reference point
Assess current capabilities of utility & 3rd Party
systems
Assess current status of technical gaps to
determine timing (Comms)
Clarify regulatory jurisdictions as they may
impact cost & technical feasibility (Billing &
Reg)
Section source: Submetering protocol working groups
January3,2012
26
x
x
x
x
x
x
x
x
Where does the power come from?
Can submeters be an in-line solution,
complementary to customers with existing
EVSE equipment?
Consideration of parallel metering
Inter-utility issue with mobile submetering
Is there a use case with no 3rd Party
involvement (possibly near-term solution)?
EVSP role needs clarification (whether
reselling electricity or just seeking to bill
separately)
Possibility of customer’s EVSE acting as
DMA?
Determine extent of submeter measurements,
whether they are impacted down to the EV
driver
Address net metering use case(s)
Address mobile submetering
Address community choice aggregators (CCAs)
use case(s)
Address use of utility AMI
x
DISCUSSION
x
x
x
x
x
x
x
x
x
Determine aspects of each use case, namely
technological, legal and regulatory, cost (to
consumers, customers, utilities, and 3rd
parties), actor capabilities, national and/or
collaborative requirements, & timing
With challenges, attempt to identify solutions
and/or timing of solutions
Determine timing and cost of each use case
(feasibility)
Place use cases into buckets corresponding to
the 4 phases of the roadmap
Find discrepancies between short- and longterm decisions; go through each aspect of the
use cases, which are identified in use case
analysis
Distinguish residential vs. commercial
Distinguish Single Family Home vs. MDU
Identify “who uses” and “who pays”
Identify any missing use cases / applications
KEY TASKS OR ACTIVITIES
USE CASES
PRELIMINARY RECOMMENDATIONS
All use cases must be
identified
ISSUES and/or
REQUIREMENTS
x
A. MatrixofDetailedRequirements26
7. APPENDICES
x
x
x
x
x
x
Use Cases Team
Use Cases Team
Billing & Reg Team
Comms Team
Use Cases Team
RESPONSIBLE
ORGANIZATIONS
x
x
x
x
TIMING
Estimate
…
x …
x
To be done before
Protocol Report is
completed (7/31/12)
x
Estimate
…
x …
Factors
…
x …
x
Page91
COSTS
Factors
x …
x …
Occurs in conjunction Factors
with identification of
x …
use cases
x …
Likely to be used as
input for roadmap
Estimate
(due end of year)
x …
x …
Must be addressed
before end of year
2
x
1
x
x
x
x
Adopt appropriate rules, procedures, prerequisites,
and fees to mitigate conditions likely to generate
disputes
Leverage DA dispute rules as a starting point
Put rules and protocols in place to assure
appropriate customer service contact for customers
and utilities, such as availability during CA business
hours
Establishment of the Customer / 3rd Party MSPs /
Utility relationship introduces complexity to utility
billing and service delivery, and this more complex
relationship has higher potential for disputes
x
x
x
Assess existing rates and rules to determine which
areas will require new language or modifications
Identify and to detail relationships with 3rd Party
MSP’s
Leverage Direct Access rules (where / if
applicable). What was put in place for Direct
Access that would need to be done for AFV submetering in some form
Amend tariffs or develop new rule(s)
x
x
ISSUES
and/or REQUIREMENTS
January3,2012
x
x
x
x
x
Utilities and customers will need ability to contact
third party MSPs in the event of billing issues or
other disputes
Some 3rd party MSP’s may have a business model
that in the long run will have customers dealing
directly with them in disputes
Submetering and other PEV services may
introduce billing relationships beyond CPUC and
Utility jurisdiction Spell out what each party will
have to do and when
x
x
Define the nature of the relationship between IOUs, x
Customers and 3rd parties, including:
- Roles and responsibilities of each party
- Performance expectations of all participants
x -Rights and obligations of each party
x Identify and detail expected dispute types
x
x Identify methods for settling identified dispute types
x Identify and detail incremental infrastructure needed
to address these disputes
Review adequacy of existing rules and file new rules
as necessary with commission
x
x
x
x
Identify regulatory requirements of Protocol. What
tariff provisions are needed such as registration,
enrollment, billing arrangements, fees, dispute
resolution, technical performance, eligibility, etc.
Identify required changes implied by Protocol.
Modify tariffs (rate schedules and rules) or create a
new tariff (a new rule with reference to a technical
protocol, or other solution) to align with approved
Protocol
Develop any new technical protocol documents via
working process as well as new forms to file with
Commission
Make advice filling (Tier 2)
Factors
P to September 2012
filing, will need a vetting x …
step to ensure all parties x …
at least have reviewed
proposals and
Estimate
supporting arguments.
x …
Review process
x …
Iterative process aligned Factors
with Protocol
x …
development schedule
Make compliance filing x …
by due date and decision Estimate
(September 3rd, 2012)
x …
x …
TIMING
BILLING AND REGULATORY REQUIREMENTS
What was exactly done in Direct Access, what can x
be done, will we be addressing the same questions
here?
DA rules, start with IOUs to look over and
x
comment on
Discussion Points
COST
x
x
x
x
x
x
x
x
x
x
x
x
x
Page92
Utility and 3rd Party MSP
Regulatory Policy
Legal Team
IOU revenue services org
Customer service org
IOU Customer relations
dept.
Regulatory policy and
affairs
Rate design groups
Law
Customer service
organizations ( Revenue
Services, Meter Services
and Customer
Communication Services)
Information technology
Communication and
training
Other stakeholders
(parties to the proceeding)
RESPONSIBLE
ORGANIZATIONS
4
3
x
x
x
x
x
x
x
x
Current DA rules were not designed to address
sub-metering; DA meters measure the entire
load., DA rules and protocols may require
significant restructuring to properly facilitate submetering
Maintain existing rules that load cannot be split (you
can have only one generation supplier)
Providing sub-metered services with Direct Access
(DA) or Community Choice Aggregation (CCA)
customers expected to add complexity to the
overall utility / customer relationship, and billing
systems and processes
Identify costs and recommend method of recovery
from fees, rates, or other means.
If appropriate, leverage current DA or CCA service
fee structure, and/or assess allocation of costs to
rates
Utilities will need to recoup incremental costs
associated with sub-metering including data
collection, assembly, and QC services provided to
3rd Party MSP’s
ISSUES
and/or REQUIREMENTS
January3,2012
Determine method for the utilities to request
recovery through application to recover costs
Cost allocation – what and how are costs built in to
EV rates?
Each utility may take a different approach to the
cost allocation and recovery
At what point would this need to be submitted to
recover costs through an application? Early
decision point?
There are some use cases not covered under the
regulatory directive, would need to consider
leaving the doors open to allow for use cases at a
later date
Where DA is considered in this context, CCA
should also be considered
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Identify rights and obligations of DA customers,
CCA customers, and 3rd Party MSP’s
Review and expand the results of Item #2 (Dispute
Resolution) to address DA and CCA customers
Identify incremental metering, billing, and customer
service processes, O&M and Capital costs
associated with providing submetering services to
DA and CCA customers for inclusion in #3 above
Determine impact of each requirement on existing
utility processes and systems for each use case
Identify O&M and Capital costs associated with
each of the requirements
Review existing / forecast PEV-related O&M and
capital expenditures in GRC to determine which
costs are incremental to existing / forecast costs
Review costs to determine any overlap with costs
included in 3rd party MSPs business models
Determine cost allocation within the utilities
x
x
x
x
Ready by time report is
due.
COST
Estimate
x …
x …
Factors
Could be costs
x …
x
Make a submittal
Factors
according to the decision
x …
Then make a
recommendation for filing x …
an application on how to Estimate
recoup costs (in advance
x …
of implementation)
x …
TIMING
x
Discussion Points
x
x
x
x
x
x
x
x
Page93
IOU Regulatory / Law
IOU ESP and CCA
Services
CCAs, ESPs, and other
DA market participants as
appropriate
MSP Law
Energy Division
IOU Law, Regulatory,
and finance
DRA
Parties to the proceeding
RESPONSIBLE
ORGANIZATIONS
7
6
5
x
x
x
x
x
x
x
x
x
There should be interval usage measurement
The submeter should have some capacity for
demand response direct load control
How we extend demand response controls to
submeters
Develop integration solutions applicable on a broad
basis (manual and automated)
IOUs anticipate the need for subtractive billing as
the method to process the submeter output into the
utility billing stream and bill the premise and PEV
loads separately
Establish common interface protocol to receive data
from the 3rd parties to the utility
Associate all submeters to one common master
meter
Complexity and additional cost of multiple 3rd Party
MSP’s providing metering services at the master
meter and multiple submeters
ISSUES
and/or REQUIREMENTS
January3,2012
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x Early resolution is
Determine whether addressing this issue is in scope required
Identify what we mean by “in scope.” (can again be
multiple stages of development), and what are the
priorities.
Assess the technical feasibility of load control for a
light-duty electric vehicle submeter.
Determine the necessary steps to implement DR
load controls from the technical (standards /
communications) and regulatory perspectives
(Suggest removing because of number and current
status of DR programs.)
May be worthwhile to look into how this would work
Don’t want to preclude any future requirements
x
x
when addressing submetering
Specify in the protocols what would be enabled or
excluded to meet these needs
Do we need Cal ISO involvement? (Can’t answer x
right now. Could be beyond what we’re trying to
x
enable with submeters.)
Where are quick charging technologies today with
respect to DR? (Appears to be out of scope for
x
developing a submetering protocol.)
x
x
x
x
COST
Estimate
x …
…
Factors
x …
x …
IT development will be
Factors
addressed with the
x Understand the costs of
Communications team
various categories of
Rules for receiving 3rd
subtractive billing
party data will be guided
x Identify differences
by existing DA rules
between 3 IOUs
(pertaining to unbundling
of the metering services) x …
SM Technical
Estimate
Requirements to
x …
address…
x …
Estimate
x …
x …
Early inventory of what is Factors
in scope for this protocol x …
x …
Understand methodology for subtractive billing
Determine the roles and responsibilities of each
party
Review existing IT systems to determine the cost to
implement subtractive billing through the
development of new or enhancement of existing IT
systems
Determine the cost to develop an interface to
receive the 3rd party data
Develop the rules to receive 3rd party data
Understand (ref. metering team) what is
technologically feasible
Define where is it that we’re actually trying to go.
What will it look like when we’re done? (In
stages…toward the “lofty goal.”)
x
x
x
TIMING
There is a whole tariff aspect to this and would
x
want to look at usage patterns and implications for x
rate design and cost recovery
IT to understand who development for EV
x
subtractive billing may be include future products
Understand variable and fixed components of each
product
When does the data need to move from Party A to x
Party B
Identify boundaries to define what is included
x
Dependent on which use cases will be in play for
this protocol
Determine if this issue is already resolved through
the use cases
May not be a requirement for this protocol
x
Is this applicable for CCAs?
This may not be an issue. Already resolved within x
the DA context
Potential for apartment complex where tenants can
select different 3rd party MSPs
Discussion Points
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
Page94
Regulatory Policy
Legal Team
IOU IT
IOU Demand Response
CAISO
Regulatory Policy
Legal Team
IOU IT
IOU Regulatory
IOU and 3rd Party MSP
Law
RESPONSIBLE
ORGANIZATIONS
8
x
x
x
x
x
x
x
x
x
x
x
x
x
NEM integration with Submetering protocol should
be separate, focused effort after Dec 2011 roadmap x
filing, but acknowledged in the roadmap report.
CPUC: Main point of roadmap report: define the
problem and potential ways to solve it.
x
SUM: Submetering could allow NEM customers to
participate in market signal programs.
x
The possible combination of NEM and submetered
services may add further complexity to the overall
utility / customer relationship, and billing systems
and processes
ISSUES
and/or REQUIREMENTS
January3,2012
Determine the technical and regulatory feasibility of
combining NEM and submetering services.
Review and expand the results of Item #2 (Dispute
Resolution) to address NEM customers
Identify incremental metering, billing, and customer
service processes, O&M and Capital costs
associated with providing submetering services to
NEM customers for inclusion in #3 above
Determine measurement needed to integrate NEM
and PEV Submetering
Determine tariff requirements resulting from
integration
Determine technology capabilities needed to
process integrated billing
x
TIMING
At least half of customers will have EV and Solar x
NEMMT (multiple technologies) can be expanded
to include EVf
x
Need to determine what can be done (talk to Meter
x
group about this)
Subtractive billing capabilities may not be the
solution in this instance, will need to look at other
solutions
Current net metering process and technology is
x
not sufficient to provide direct PV to PEV
x
measurement
Separate rates for master meter and sub meter
x
add more complexity to measurement
If customer chooses to have master meter and sub
meter on same rate, this could reduce the
complexity from a price per kwh standpoint
Need to consider projected volume of customers
that would fall in this scenario
Not noted in protocol guideline. Need to determine
if this is in or out of the OIR decision.
This is going to come up a lot, and will do
ourselves a disservice if we delay…need to
address metering of NEM and PEV via or with PEV
submeters. Need to identify possible variations of
how PEV charging and NEM systems are metered,
data communicated, and billing handled.
Definitely need to note in the roadmap
Use case team is adding a NEM use case
Discussion Points
Estimate
x …
x …
Factors
x …
x …
COST
x
x
x
x
x
x
x
Page95
IOU Regulatory / Law
IOU ESP and CCA
Services
PV suppliers
IOU Metering Standards
IOU Generation
Interconnection
IOU RP&A
IOU DR and EE
Programs
RESPONSIBLE
ORGANIZATIONS
DISCUSSION
x
and clocks in meters.
ECOtality: I agree we should reduce the number of synchronizations required,
PRELIMINARY
and that clock standards need to be established
RECOMMENDATIONS x CSMD: I don’t believe that’s happened yet.
(10.27.2011)
x The immediate task at hand is to determine kWh usage formats and to determine
how calendar and clock requirements are handled. Agree with UTC approach.
EV participants jointly
x SUM: Be careful about federal requirements and time changes
develop these, using
DASMMD (Direct Access x DMS: If time becomes a function of billing, then we would have some involvement
Standards for Metering and Local Meter Reading, Usage Estimation
Meter Data) as baseline x Is there a requirement about local meter reading that can be specified for MSPs?
x We don’t want data estimation to be the default solution when data isn’t available.
This is especially important for DR programs.
x If tariffs change—e.g., DR—that can drive a change for the submeter
Error Tolerance Levels
x GE: There is a possibility that DMS will have to retool their requirements and
testing. Current accuracy requirement is 1%, while meter capability is .01%.
x There appear to be two requirements for DMS: Initial certification at 1%, recertification at 2%.
x Requirements are at a system level.
Accuracy Standards
x Utilities are driven by ANSI standards for testing while the state sets the tolerance
levels
x Regulations have not kept up with advancements in meter technology
x DMS hasn’t determined how to re-certify meters every 10 years
x Utilities do annual sample testing among different meter types and will check
when there are billing complaints (SCE and SDG&E do similar testing). Once
installed the bulk of the testing is in the field, both for general accuracy and billing
complaints. (PG&E to provide more information.) DASMMD standards are
followed.
x Wouldn’t the utility still have the authority to set the standards for what would be
used for billing?
x We would accept what CDFA DMS specifies for accuracy. It’s the same
requirement imposed on the utilities. It should be the same level, or on par, with
existing meter accuracy standards.
x SDG&E: That’s very important; SM accuracy has to be the same as other meters.
Other
x Utilities may have different parameters. Won’t necessarily be one set of
requirements; need to maintain flexibility.
January3,2012
ISSUES and/or
REQUIREMENTS
-
-
-
-
-
-
-
-
VEE (data Validation, Estimation, and Editing) Rules for situations in which
data doesn’t exist and estimations are required
Recommend meter data estimation requirements when it is not available locally
either
If we can’t get the data remotely, how do we get it locally? We need to
determine that this is a requirement.
Recommend local meter reading requirements
Defining data storage requirements:
à Data quantity
à Duration of storage
à Duration of intervals
Recommend how to synchronize submeter time clocks with utility meters on the
premises, including:
Should be on par with a utility meter (or better), if it’s used for customer billing
purposes
Confirm utility accuracy requirements
Confirm that CDFA DMS creates the standards for billing accuracy
Confirm CDFA DMS processes for testing embedded meters and meters with
TOU/synchronization clocks that can communicate wirelessly
Establish percent error tolerance
IOUs responsible for
identifying for DMS how the
submeters should be
configured to support
submetering & subtractive
Confirm format of usage information, especially for time of use and associated
billing;
clocks and synchronization, including impacts of federal requirements and time
x IOUs provide functional
change impacts
design requirements
documentation and technical
Address V2G power flow scenarios in requirements in order to future-proof the
support
technology
x CDFA/DMS responsible for
Verify that types of technical requirements, compliance, and standards identified
adopting specifications and
are complete
establishing requirements
Identify source documents offering requirements that can either be used as is, as x MSPs responsible for
models, or for ideas
implementation
Review DASMMD standards for appropriateness, make comments on what’s
appropriate and what isn’t (e.g., multiple users of same meter during the day)
Check F&A DMS documents (Reference Manual) posted on web (need to
assure accuracy, avert tampering)
Gary Fox has documents and can share them
x
RESPONSIBLE
ORGANIZATIONS /
INDIVIDUALS
x
x
x
x
x
TIMING
UTILITY
COSTS
Page96
Dependent on tariff
Factors
requirements.
x Labor only
Need language on meter clock x Communication
and calendar.
Approximately 1-3 months
Estimate
(just tech functional design)
x No incremental cost
Need to integrate discussions
w/ MSPs and DMS
But if requirements cause a
change in standards that will
extend the time frames.
METERING TECHNICAL REQUIREMENTS, COMPLIANCE, STANDARDS REQUIREMENTS
x IOUs define billing and usage parameters (load, time, etc.)
Technical performance and TOU, Timing, Synchronization
x TOU measurement is 60 min. for residential and 15 min. for commercial.
functional design
- Define interval data needs, or if we need interval data at all.
x SCE keeps meters on standard time and do seasonal adjustments in the back
requirements and
- Define configuration needs
office
systems,
not
at
the
meter.
There
has
been
too
much
trouble
with
calendars
standards
January3,2012
DISCUSSION
RESPONSIBLE
ORGANIZATIONS /
INDIVIDUALS
Determine how data communication technology, standards, security will affect the
metering hardware
x
Inform Comms Team
The task at hand is to determine the jurisdiction of the submeter, and that will drive the x Refer to B&R Team
accuracy requirements. In California we've heard over time that DMS has the
jurisdiction over submetering in California in a billing application. If there's a final
transaction going on CDFA DMS drives the accuracy requirements.
If tariffs change—e.g., DR—that can drive a change for the submeter. Tariffs can drive
the need for much more complex submeters.
Is there a requirement about local meter reading that can be specified for MSPs?
We don't want data estimation to be the default solution when data isn't available. This
is especially important for DR programs
.
Narrow the use case scenarios (meters don’t care who’s plugging in, but there are
x Refer to Use Case Team
requirements on the billing side, which is complicated)
Can we have a one size fits all use case scenario? This becomes very complicated and
time-consuming.
Accuracy Standards (continued)
x
x SUM: In speaking with consumers, they’re also looking for similar levels of
x
accuracy in NEM situations.
x CCWM: I don’t believe any of our systems have a clock in them. This hasn’t been
relevant to the mobile home parks, so industry hasn’t developed this equipment.
x TOU, IDR, interval data needs will drive requirements into submeter
x
manufacturing.
x Other
PRELIMINARY
RECOMMENDATIONS x ANL: It would be nice to have a table of submeter vendors.
x ANL: Shouldn’t we be defining what we want in the future, rather than looking at x
(10.27.2011)
what EVSE manufacturers are doing today?
x
x ANL: Computational power demands will increase significantly.
x
DASMMD (Direct Access x The ideal way to do this project would be: Use Case Team Æ Billing &
Regulatory Æ Tech & Comms Requirements
Standards for Metering and
x ANL: Point of contact question. Who is a good point of contact to give DOE the
Meter Data) as baseline
official line on what’s happening with CPUC? DOE is currently getting different x
(continued)
information from different sources. (A little bit of misinformation goes a long way.)
x DOE should be referencing the October 27 Workshop Report and December 31
Roadmap Report as the proper source.
x Will refer DOE to Adam Langton at CPUC.
ISSUES and/or
REQUIREMENTS
Technical performance
and functional design
requirements and
standards
(continued)
TIMING
Page97
COSTS
DISCUSSION
certification process
(reference: DASMMD)
DMS: Yes.
-
DMS: We have to compare the metering and readout to double-check them
We need to define and standardize what needs to be read out on the meter (cum.
Hours, hours by time period, etc.)
-
Coulomb: Is it reasonable to have a display that is a separate device than the meter
displaying the energy usage on the outside?
DMS: Our preference would be that the meter be exposed so a cabinet doesn’t
have to be opened up.
-
x
Coulomb: Would we have to certify state by state then?
IOU: Probably.
x GE: Only California has existing language on submeters
x IOU: But if you go by what CA has there’s a chance the other states would accept it.
Other
x IOUs may have input on certification and audit requirements and processes, but
basically this is a CDFA/DMS activity.
x
We don’t think there is one.
But in the DASMMD there is language about using a nationally recognized
testing lab (NRTL). There are independent testing labs out there marketing their
services to whoever needs a product tested. They would test according to the
standards applying to those devices.
-
DMS not experienced with TOU, embedded meters, or wireless communication of
metering data
MSP Certification Requirements
x Coulomb: Is there a federal certification body for multi-state certifications?
x
x
x
-
- Determine how testing and certification occur with meters built into EVSE
PRELIMINARY
(cordset and charger) and automotive equipment
RECOMMENDATIONS
x Current reference manual covers traditional utility socket meter, and not a submeter
(10.27.2011)
connected to something else.
Dept. of Food &
x ECOtality: We currently have a meter that is internal to our equipment which you can
see from the outside. That meter could be certified. The meter is being used by some
Agriculture Division of
Measurement Standards utilities and incorporated it into our level 2 EVSE. Would we need to expose this
meter to the outside? If the EVSE is certified, would this meter need to be physically
(CDFA/DMS) oversees
mounted on the outside?
January3,2012
ISSUES and/or
REQUIREMENTS
x
Understand current CDFA/DMS/CCWM processes, and confirm that they are the
drivers of this process.
-
Determine how submeter accuracy auditing can occur with meters built into EVSE
(cordset and charger) and automotive equipment
-
Determine how EVSE, cordset, and automaker submeter manufacturers
Submit new meter types for initial certification
Submit products as sold to County Weights and Measures
Submit products decennially for re-certification
Understand how submeter manufacturers can prove accuracy prior to (or instead of)
testing and certification
-
-
Clarify circumstances requiring 100% vs. a sampling of meters for certification
Clarify whether CDFA/DMS and/or CCWM can adjust their current processes and
requirements
-
SCE would accept that process as established by CDFA DMS
SDG&E: Uncertain as to accuracy requirements of CDFA as compared to
existing accuracy levels; so there could be an issue if there is a mismatch
CPUC: I have the same question; I thought utilities set their own standards for
utility meters
How meter certification is documented
Roles and responsibilities
-
Re-certification requirements and timing
How the meters are to be tested
-
-
Testing and auditing approaches
100% vs. sampling
-
CDFA/DMS establishes process to certify and audit technical requirements (as defined
above)
IOUs responsible for
x
identifying for DMS how the x
submeters should be
configured to support
submetering & subtractive
x
billing;
x IOUs provide functional
design requirements
documentation and
technical support
x
RESPONSIBLE
ORGANIZATIONS /
INDIVIDUALS
Certification and Audit of Current CDFA/DMS Procedures, Guidelines, Tools
x Current understanding is that meter approval is in multiple stages: (1) Basic meter
submeters and
type/technology certification; (2) Then individual meters are certified at County
submetering
Weights and Measures Departments (CCWM); (3) Every 10 years meters are reequipment/sites
certified
DMS’ timeline
6-12 months max, certainly
< 1 year (including county
weights and measures)
NOTE: DMS activity is on
the critical path of utilities
developing a submetering
protocol. If DMS has to
start from scratch it could
take a long while.
TIMING
Page98
Estimate
x No incremental cost
Factors
x Labor only
x Communication
COSTS
DISCUSSION
Lazier to join us on these calls.
Dept. of Food &
Agriculture Division of
Measurement Standards
(CDFA/DMS) oversees
certification process
(reference: DASMMD)
(continued)
x
Customer complaints usually start at the county level; disputes then move to the
submeter manufacturer and then to the utility. There are implications for the auditing
process depending on who owns the billing dispute process.
- Ron described meter from England with comparable accuracy
PRELIMINARY
RECOMMENDATIONS
(10.27.2011)
Dispute Resolution
January3,2012
ISSUES and/or
REQUIREMENTS
x
RESPONSIBLE
ORGANIZATIONS /
INDIVIDUALS
DMS has not verified its role in sub-metering; responsibility may be delegated to
county weights and measures. There appears to be flexibility in existing standards.
Verify in field reference manual.
-
IOUs determine impact of dispute resolution processes on the auditing process
x
Refer to Billing &
Regulatory Team
CPUC/CDFA/DMS clarify the jurisdiction of the submeter in California, and identify guiding x Refer to Billing &
documents (F&A DMS, regulation, legislation).
Regulatory Team
- Check with legal
x IOUS determine whether certification requirements come from submeter manufacturers,
utilities, and/or CPUC. (Certification requirements should come from the CDFA DMS with
input from the utilities or CPUC.)
x
Certification and Audit of CDFA/DMS Authority
x CCWM: Until CPUC decides that submeters are subject to DMS regulation, I’ll have
submeters and
nothing to do with it…
submetering
equipment/sites
- Adam to forward decision. We may need new standards and processes.
(continued)
- Adam to get a call together with DMS to discuss these issues, and to get David
TIMING
Page99
COSTS
interval data (e.g. 15
minute interval data
configuration)
January3,2012
DISCUSSION
x
Utilities develop:
x
RESPONSIBLE
ORGANIZATIONS /
INDIVIDUALS
TIMING
x
How to know when a meter is out of tolerance
Generally, at a high level, when we retrieve data you stop getting it. Or, the data
looks way out of whack; the numbers don’t compare with the premises meter;
it’s grossly wrong.
Requirement for shut-down/de-energizing circuits during installation of submeters,
particularly at commercial sites.
Determine how to correct and/or replace submeters discovered to be out of tolerance
Determine how to handle reconfigurations based on utility rates and programs
For example, shifting from 60 min. intervals to 15 min. intervals
Determine how to fix/update software and firmware issues
-
Benchmark EVSE, cordset, automaker, utility processes for data verification
-
- Validation should be provided by meter reader (MDMA)
MSPs:
-
-
MSPs responsible for
x 1 – 2 months
requirements definition and
implementation, with
specifics spelled out in the
- What it takes to associate the meter with a particular premises meter/account and
tariffs
network (registration) in fixed and mobile meter scenarios
x Utilities provide direction on
Establishing communication between submeter and premises meter
key requirements and how
submetering? Will we need a whole new protocol for this?
à There are multiple ways to get the data back to the cloud
to work effectively with the
utilities
IOUs: We’ll need a bi-directional meter. That would be driven the rates and tariffs. If that
à There are multiple types of submeters to be profiled as well (Comms team
PRELIMINARY
comes into play,
addressing)
RECOMMENDATIONS IOUs: Good point. We might need to include that in technical design that submeters
x MSPs identify source documents offering installation, maintenance, and testing
(10.27.2011)
need to be bidirectional. (to future-proof them)
requirements either usable as is, as models, or for ideas
IOUs: There have been discussions about this concept. It’s not that big of a deal with
- Review DASMMD contents; determine what’s appropriate and what isn’t
solid state electronics today.
- Identify EVSE, cordset, and auto manufacturer materials; determine what’s
appropriate (as is, as a model, or to generate ideas) and what isn’t
DASMMD (Direct Access IOUs: If scope of decision is charging only, generation would not be included in the
protocol, but we need to be mindful of it. (Get Billing & Regulatory opinion on this.)
x MSPs determine how to verify the quality of submeter data
Standards for Metering
ECOtality: This would fall into the category of net metering. Submetering should
and Meter Data) as
- How to obtain data for verification purposes
probably follow that approach/work.
baseline submeter is
Locally and remotely
CPUC: Something to address, don’t want to preclude it with what we’re doing now.
capable of providing
Relates to VEE rules for verifying quality of data once retrieved into MDMS
ISSUES and/or
REQUIREMENTS
Roles and Responsibilities
Requirements for
installation, maintenance, x EVSE, cordset, and auto manufacturers have to figure out how to maintain this
device with respect to testing and accuracy
and testing of submeter
x Utilities need to support the registration of these SMs when installed
and related equipment
compatible with the utility Other
ECOtality: What impact will vehicle-to-grid (V2G) power flow have an impact on
meter usage data
Estimate
x …
x …
Page100
Factors
x Labor time adapting current
electrician and other
training, web info
COSTS
Certification of Data
Management Agents
January3,2012
ISSUES and/or
REQUIREMENTS
DASMMD (Direct Access
Standards for Metering
and Meter Data) as
baseline
PRELIMINARY
RECOMMENDATIONS
(10.27.2011)
ISSUES and/or
REQUIREMENTS
DISCUSSION
-
RESPONSIBLE
ORGANIZATIONS /
INDIVIDUALS
DISCUSSION
CPUC and DMS don’t have authority in this area.
TIMING
How training, certification, and auditing results are documented
Responses for out of conformance results
-
How certification occurs
How certification results are documented
Responses for out of conformance results
Determine roles and responsibilities
-
- Determine roles and responsibilities
x DMS develops a submeter testing equipment certification process
How training, certification, and auditing occur
-
x
MSP certifies
RESPONSIBLE
ORGANIZATIONS /
INDIVIDUALS
TIMING
MSPs identify source documents offering testing equipment manufacturer, data
x MSP certifies
x 4 – 6 months
processing, and worker certification methods that can either be used as is, as models, x DMS to provide guidelines
or for ideas
for worker requirements
- Review DASMMD contents; determine what’s appropriate and what isn’t
x IOUs to provide
recommendations
- Identify EVSE, cordset, and auto manufacturer materials; determine what’s
appropriate (as is, as a model, or to generate ideas) and what isn’t
x MSPs develop a worker training, certification, and auditing process
x
equipment.
Installers need to meet certain qualifications/state requirements
What are we talking about?
We’re talking about certifying the DMAs providing data for billing purposes.
x 3rd party DMAs have to be certified to OpenEV interface standards. Who has
responsibility for this? Today in the DA world MDMAs are certified by utilities (forced on
utilities because no one else could do it). This role is undesirable for cost and other
reasons.
x We’d have to meet with MDMAs to check on how well they were meeting data
requirements (time, quality)
x DMS certifies data, shouldn’t they certify the DMA as well, the provider of the data?
x
x
Certification of submeter Roles and Responsibilities
x In DA the IOUs certified employees and their training, because they’re touching utility
workers/providers
Estimate
…
x …
x
Factors
x …
x …
Page101
COSTS
COSTS
January3,2012
x
x
x
x
x
x
x
DISCUSSION
Many EV drivers might be interested in 110 volt charging on a submetering basis.
x
8 hours of home and workplace charging can be handled with 110 v.
In the future, if we can handle L2 240v like a dryer circuit, EVSE equipment could just become
plug-in equipment if homes come with 240v and rated amperage. Would that fulfill technical
requirements?
This is valid. I submitted to use case team the idea of a dumb EVSE.
There are already manufacturers with plug in 50 amp equipment. Tesla has 70 amp and 90 amp
on the way.
There’s a case for a smart submeter standalone unit or in line. The service providers could
cover a lot of those cases.
RESPONSIBLE
ORGANIZATIONS /
INDIVIDUALS
- This should be a fairly routine process for manufacturers
Part of certification process by DMS (UL or ANSI certified equipment meets
DMS requirements. Installation should be referred to building code agencies.)
MSPs identify applicable standards (on manufacturing side) and develop
requirements
x
Refer to Use Case Team
The task here is for MSPs to map the standards to the type of device based on x MSPs (e.g., EVSE
its electrical parameters and how it makes a connection. Hard-wired vs. plug in manufacturers) and DMS
device have different requirements.
certification and audit
processes
- Look at issues by location of meter.
Definition and Background
x
Mitigating potential damage to life and property
x Meters are embedded in equipment.
x This refers to building equipment to various standards applying to electrical devices installed in
PRELIMINARY
x
residential, commercial, industrial premises.
RECOMMENDATIONS
x Safety requirements are driven by local jurisdictions (electrical inspectors and guiding
(10.27.2011)
documents can differ depending on location and resource availability)
x
Use applicable and
x First you have to make the device and have it comply with applicable standards, and then
existing national and state there’s an installation process that has to comply with local safety standards.
standards & requirements Existing Safety Standards
x UL is standard agreed with. Main standard. It is required. It’s about the safety of the overall
(e.g. UL, NEC, FCC,
equipment as a device by itself.
ANSI, DASMMD)
x UL 2594 is the standard used by most EVSE manufacturers for L1 and L2 charging stations.
Defining and Implementing Safety Standards
x Product use needs to be listed. This is already part of the NEC Section 90.7, calls for a testing
laboratory. Makes it possible for AHJs to complete assessments without inspections of internal
components.
x There is the local AHJ, which will vary across the state and country. It’s a local thing, so you
have to comply with local jurisdiction requirements driven by NEC and various other local codes.
(Installation side). There will be installation instructions from the manufacturer, and the AHJ will
check for compliance.
Other
x These different metering scenarios and charging levels feed into the use case work. But the
safety—and certification—needs are related to the type of device.
x SCE is doing testing and evaluation of a smart receptacle (110v). Also working with DOE US
Drive on a standalone submeter that could be inserted in a circuit for a non-smart EVSE. The
Roadmap should include continued investigation.
ISSUES and/or
REQUIREMENTS
Safety risk (equipment,
workers, customers)
TIMING
Page102
COSTS
Reliable submeter
January3,2012
x
x
RESPONSIBLE
ORGANIZATIONS /
INDIVIDUALS
DISCUSSION
RESPONSIBLE
ORGANIZATIONS /
INDIVIDUALS
Contents moved to first issue on developing technical requirements.
DISCUSSION
Consumer Elements
x We need to establish a reliability statement and parameters such that the
x CDFA DMS, CCWM and
meter maintains its accuracy over its expected life. At a high level the submeter EVSE manufacturers
People have to know that once you get to certain point in time it’s time to replace the device.
has
to
perform
its
function
reliably
and
accurately
over
its
expected
life.
Utilities give premises meter requirements to manufacturers. Originally called out in ANSI. Life
PRELIMINARY
expectancy of solid state equipment has dropped from electro-mechanical days.
x Investigate whether meter recertification should be more often than 10 years
RECOMMENDATIONSx Consumers will use a device as long as they can (beyond designed life and accuracy levels). x This all has to be spelled out in the initial certification process, which describes
CSMD needs to revisit the recertification/accuracy verification interval.
initial evaluation and ongoing testing
(10.27.2011)
Utility Preferences
Use applicable and
existing national and state x Utilities want the meter device to have a safe and accurate life time of 20 years (SCE-specific)
standards & requirements allowing for temperature, humidity, vibration, voltage variation
(e.g. ANSI, DASMMD)
x Mainly up to the device manufacturers to determine the expected life of their equipment.
Changing State Recertification Requirements
x CSMD: Given this issue, should recertification be more often than 10 years?
x Let’s defer this to CSMD and the manufacturers
ISSUES and/or
REQUIREMENTS
Use applicable and
existing national and state
standards & requirements
(e.g. ANSI, DASMMD)
PRELIMINARY
RECOMMENDATIONS
(10.27.2011)
ISSUES and/or
REQUIREMENTS
Accurate billing
TIMING
TIMING
Page103
COSTS
COSTS
January3,2012
ESPI conformance
certification and
interoperability
Implement ESPI on end
device (sub-meter) to
interface with service
provider directly (for submetering only purposes)
x
x
Establish an interface
between 3rd parties and
utilities to share 3rd party
sub-metering data for billing
purposes
ISSUES
and/or
REQUIREMENTS
x
x
x
x
x
x
x
x
x
x
x
Participate in UCAIug and OpenSG OpenADE committees
Interoperability testing
EV profile will be drafted within Submetering
Communications, Std & Sec. team and shared with
OpenADE for verification.
o Need to choose data types to determine if revisions
need to made (e.g., Usage Data, PQ data)
o Possible sub-team work
Develop 3 way sub-metering contract for 3rd party submetering
Implement ESPI sub-metering profile on utility and EVSP
systems
Identify requirements for revisions to ESPI (e.g., advanced
use cases)?
Testing, Certification, Interoperability, Security
Determine priority compared to other use cases
Determine OAuth and ESPI implications
Next Steps?
Utilize existing utility systems to implement interface
standard
Utilize the NAESB Energy Services Provider Interface
(ESPI) standard
Leverage the OpenSG OpenADE working group to create
an ESPI profile or necessary document modifications to
align with proposed sub-metering phased approach
x
PRELIMINARY RECOMMENDATIONS &
DISCUSSION
Could be implemented w/ current technology as alternative
to Use Case 1&2
x Could add a 3rd party in at a later date
x Similar to VOIP. Certified device list able to call home (?)
when plugged in to the internet
x Security? 3rd party management- certificate?
o Benefit: Direct communication b/t sub-meter and utility
x VPN through homeowners internet connection
x Servicing? Access?
x EVSP Networks in use for value Added Services?
o Synchronization problems
x EVSE Wi-Fi possibility
x Other comms connections for upgrades, etc.
x Sub-meter identified as conformant
x Use the certification authority and processes in
development by UCAIug and OpenSG OpenADE
x
x
x
x
x
x
x
x
x
Integration
COST
(Utility)
By middle of next year
Estimate
x …
x …
Factors
…
x …
x
Estimate
x …
x …
Depends on priority compared Factors
to existing use cases (Use
x
Case team?)
x …
Depends on many systemFactors
wide factors (development,
x
testing and certification,
x …
implementation…)
Updates provided to ESPI in Estimate
2012 (if necessary for fixed
x …
sub-metering or advanced use x …
cases)
Ability to certify by middle of
next year
TIMING
COMMUNICATION FUNCTIONALITY, STANDARDS, AND SECURITY REQUIREMENTS
x
x
x
x
x
Page104
Test plan development,
Testing and Certification
w/in OpenSG OpenADE
OpenSG OpenADE
(participation encouraged)
and iinterop committee
Use case (and
RegulatoryTeam?) to look at
Work will be conducted within
CPUC Submetering Comms,
Std & Comm team. OpenSG
OpenADE working group.
Expected participants include
California IOUs, Interested
EVSPs, and other interested
parties.
Determine next steps for
advanced use cases (e.g.,
Use Cases 4 & 5)
RESPONSIBLE
ORGANIZATIONS/ CROSS
CUTTING ISSUES
January3,2012
3rd party communication complies with defined
requirements identified in contractual relationship
between customers, 3rd parties, and utilities
x
Communication
standards for submeters
x
Common security and privacy requirements for
customer and energy information (at rest and in
transit). E.g., ESPI security requirements on utility side
Included as part of the contractual relationship
between customers, 3rd parties, and utilities (Terms
and Conditions)
x
Privacy and Security of
the customer and energy
consumption data
x
x
x
x
x
x
x
x
x
Define which use cases could involve standardized
comms
Review ESPI security requirements
Determine who owns the “global effort” of ensuring
data security.
Determine what level should be attained (HIPAA,
PCI, credit cards?)
Determine responsibility and where this work should
be completed
Determine if existing standards available or in place
are sufficient
x
x
TIMING
Factors
x …
Estimate
x …
Factors
x Dependent on level of
cert.
x …
Estimate
x …
x …
Integration
COST
(Utility)
COMMUNICATION FUNCTIONALITY, STANDARDS, AND SECURITY REQUIREMENTS
PRELIMINARY RECOMMENDATIONS &
DISCUSSION
ISSUES
and/or
REQUIREMENTS
Page105
DOE Report
(http://energy.gov/gc/downloads/departmentenergy-data-access-and-privacy-issues-relatedsmart-grid-technologies)
QUESTIONS FOR CPUC, REGULATORY
TEAM, OTHERS:
x Is there coordination or discussions in the
CPUC DECISION ADOPTING RULES TO
PROTECT THE PRIVACY AND SECURITY OF
THE ELECTRICITY USAGE DATA OF THE
CUSTOMERS workshops relating to the use of
ESPI for sub-metering?
x What is the scope and outcomes of that rule and
workshops (e.g., 3rd parties requirements?
utility regulations? data being communicated?
Access to data? Contracts? Certification? Data
storage? Enforcement/liability? Others?) that
can or must be applied to the sub-metering
effort?
x What is the scope of the (1) CPUC (2) IOUs (3)
Communications team to define security and
privacy for sub-metering beyond the ESPI
interface (e.g., on the sub-meter, between the
sub-meter and 3rd parties, etc.)?
x For 3rd party collection, communication, and
storage?
x Related to existing IOU rules and practices?
x Certification? Liability? Contracts (Terms and
Conditions)? Enforcement? Etc.
x Use Case group should look at where/if submeter communication is in scope (e.g.,
standardization)
x
RESPONSIBLE ORGANIZATIONS/ CROSS
CUTTING ISSUES
ALJ
ANL
ANSI
CCA
CDFA/DMS
CPUC
CCWM
DA
DASMMD
DMA
DOE
DR
ESPI
EVSE
EVSP
FCC
GE
HIPAA
MDMA
MDMS
January3,2012
AHJ
B. Glossary
MeterDataManagementSystem
MeterDataManagementAgent
HealthInsurancePortabilityandAccountabilityAct(healthcareprivacyandsecuritystandards)
GeneralElectric
U.S.FederalCommunicationsCommission
ElectricVehicleServiceProvider
ElectricVehicleSupplyEquipment
EnergyServicesProviderInterfacestandard
DemandResponse
U.S.DepartmentofEnergy
DataManagementAgent
DirectAccessStandardsforMeteringandMeterData
DirectAccess
CaliforniaCountyWeightsandMeasures(offices)
CaliforniaPublicUtilitiesCommission
CaliforniaDepartmentofFoodandAgricultureDivisionofMeasurementStandards
CommunityChoiceAggregator
AmericanNationalStandardsInstitute
ArgonneNationalLabs
AdministrativeLawJob
AuthorityHavingJurisdiction
Page106
MSP
NEC
NEM
OAuth
OpenADE
OpenSG
PCI
PG&E
PLC
PQData
SCE
SDG&E
SM
SUM
TOU
UCAIug
UL
V2G
VEE
VPN
January3,2012
MDU
VirtualPrivateNetwork
Page107
Validation,Estimation,andEditing(ofdataestimatesusedinbillingwhenactualdataarenotavailable)
VehicletoGrid(powerflow)
UnderwritersLaboratories
UtilityCommunicationsArchitectureInternationalUsersGroup(notforprofitcorporationconsistingof
utilityuserandsuppliercompaniesthatisdedicatedtopromotingtheintegrationandinteroperabilityof
electric/gas/waterutilitysystemsthroughtheuseofinternationalstandardsbasedtechnology)
TimeofUse
TheSUMGroupSecuritySolutionsCompany
Submeter
SanDiegoGasandElectric
SouthernCaliforniaEdison
PowerQualityData
PowerLineCommunications
PacificGasandElectric
PaymentCardIndustry(dataprivacyandsecuritystandards)
OpenSmartGrid(forumforthedevelopmentofrequirementsforSmartGridsystems)
OpenAutomaticDataExchange(specificationsforgrantinga3rdpartyaccesstocustomerelectricitydata
heldbyutilities)
OpenAuthorization(datasecurityprotocolenablinguserstogrant3rdpartyaccesstowebresources
withoutsharingpasswords)
NetEnergyMetering
NationalElectricCode
MeterServicesProvider
MultiDwellingUnit

Sub Meter Protocol Road Map

Transcription

Similar documents

PureNet™ Asset Management

covers layout.indd - The Edison Foundation

GA Power Utility Easement Pebblebrook HS

Avisena - Sevocity

Revenue Systems Brochure

4929 139,000

Metered Bill - Truckee Meadows Water Authority

Mobile: a cashless wallet

ED Sheet - Zotec Partners