Regional Charging Infrastructure for Plug-In Electric Vehicles: A Case Study of Massachusetts

Eric Wood, Joshua Eichman, Sesha Raghavan, Marc Melaina, Clement Rames

Research output: NRELTechnical Report

Abstract

Given the complex issues associated with plug-in electric vehicle (PEV) charging and options in deploying charging infrastructure, there is interest in exploring scenarios of future charging infrastructure deployment to provide insight and guidance to national and regional stakeholders. The complexity and cost of PEV charging infrastructure pose challenges to decision makers, including individuals, communities, and companies considering infrastructure installations. The value of PEVs to consumers and fleet operators can be increased with well-planned and cost-effective deployment of charging infrastructure. This will increase the number of miles driven electrically and accelerate PEV market penetration, increasing the shared value of charging networks to an expanding consumer base. Given these complexities and challenges, the objective of the present study is to provide additional insight into the role of charging infrastructure in accelerating PEV market growth. To that end, existing studies on PEV infrastructure are summarized in a literature review. Next, an analysis of current markets is conducted with a focus on correlations between PEV adoption and public charging availability. A forward-looking case study is then conducted focused on supporting 300,000 PEVs by 2025 in Massachusetts. The report concludes with a discussion of potential methodology for estimating economic impacts of PEV infrastructure growth.
Original languageAmerican English
Number of pages40
DOIs
StatePublished - 2017

NREL Publication Number

  • NREL/TP-5400-67436

Keywords

  • charging infrastructure
  • EVI-Pro
  • Massachusetts
  • plug-in electric vehicle

Fingerprint

Dive into the research topics of 'Regional Charging Infrastructure for Plug-In Electric Vehicles: A Case Study of Massachusetts'. Together they form a unique fingerprint.

Cite this