SAE J 2836-5-2015 Use Cases for Customer Communication for Plug-in Electric Vehicles RATIONALE.pdf

《SAE J 2836-5-2015 Use Cases for Customer Communication for Plug-in Electric Vehicles RATIONALE.pdf》由会员分享，可在线阅读，更多相关《SAE J 2836-5-2015 Use Cases for Customer Communication for Plug-in Electric Vehicles RATIONALE.pdf（23页珍藏版）》请在麦多课文档分享上搜索。

1、 SURFACE VEHICLE INFORMATION REPORT J2836/5 MAY2015 Issued 2015-05 Use Cases for Customer Communication for Plug-in Electric Vehicles RATIONALE PEV recharging is very much different from refueling a conventional internal combustion engine vehicle where a customer inserts the gas pump nozzle and in s

2、everal minutes the vehicles gasoline tank is full. Standard refueling time for a PEV, especially at 110V and 240V charge levels, is several hours. The customer plugs in the EVSE connector and goes about their business for the next several hours expecting the PEV will be fully charged upon their retu

3、rn. Unfortunately there can be conditions and circumstances that could interrupt or terminate the charging session without the customers knowledge such as a power surge, power outage, circuit failure, EVSE failure, removal of the connector either inadvertently or by another person, circuit power shu

4、t off by the charge host energy management system, etc. The customer will need to know when these situations occur and have the ability to reinitiate charging or to know that the situation cannot be resolved remotely. Customers need an awareness of the charging infrastructure conditions and their ve

5、hicles charging features and capabilities to maximize the utilization of the vehicle for their transportation needs. PEV customers need to be able to remotely access information in the PEV about its charge settings and status, to adjust charging preferences as needed, and to activate the PEV custome

6、r convenience features such as cabin temperature pre-conditioning. TABLE OF CONTENTS 1. SCOPE 2 1.1 Purpose . 2 2. REFERENCES 2 2.1 Applicable Documents 2 2.2 Related Publications . 3 3. DEFINITIONS . 3 4. CUSTOMER INTERFACE ARCHITECTURE . 5 5. USE CASE SUMMARY. 7 5.1 Use Case: U8 Customer Convenien

7、ce Functions . 9 5.2 Use Case: U9: Conflict and Resolution . 21 6. NOTES 23 6.1 Marginal Indicia . 23 _ SAE Technical Standards Board Rules provide that: “This report is published by SAE to advance the state of technical and engineering sciences. The use of this report is entirely voluntary, and its

8、 applicability and suitability for any particular use, including any patent infringement arising therefrom, is the sole responsibility of the user.” SAE reviews each technical report at least every five years at which time it may be revised, reaffirmed, stabilized, or cancelled. SAE invites your wri

9、tten comments and suggestions. Copyright 2015 SAE International All rights reserved. No part of this publication may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permi

10、ssion of SAE. TO PLACE A DOCUMENT ORDER: Tel: 877-606-7323 (inside USA and Canada) Tel: +1 724-776-4970 (outside USA) Fax: 724-776-0790 Email: CustomerServicesae.org SAE WEB ADDRESS: http:/www.sae.org SAE values your input. To provide feedback on this Technical Report, please visit http:/www.sae.org

11、/technical/standards/J2836/5_201505 SAE INTERNATIONAL J2836/5 Issued MAY2015 Page 2 of 23 Figure 1 Customer communications interface architecture . 6 Figure 2 Use case structure and relationships 8 Table 1 Summary of use cases and scenarios 8 Table 2 U8 Scenario A - Customer convenience functions: C

12、ustomer remote start/stop charging 9 Table 3 U8 Scenario B - Customer convenience cabin conditioning . 11 Table 4 U8 Scenario C - Customer convenience: Charge status information . 13 Table 5 U8 Scenario D - Customer convenience: Setting customer preferences . 15 Table 6 U8 Scenario E - Customer conv

13、enience: Public charging - locate and reserve EVSE 16 Table 7 U8 Scenario F - Customer convenience: Public charging - energy usage history . 18 Table 8 U9 Scenario A - Conflict and resolution 21 1. SCOPE This SAE Information Report J2836/5 establishes the use cases for communications between Plug-In

14、 Electric Vehicles (PEV) and their customers. The use case scenarios define the information to be communicated related to customer convenience features for charge on/off control, charge power curtailment, customer preference settings, charging status, EVSE availability/access, and electricity usage.

15、 Also addresses customer information resulting from conflicts to customer charging preferences. This document only provides the use cases that define the communications requirements to enable customers to interact with the PEV and to optimize their experience with driving a Plug-In Electric Vehicle.

16、 Specifications such as protocols and physical transfer methods for communicating information are not within the scope of this document. 1.1 Purpose The purpose of SAE J2836/5 is provide a Technical Information Report documenting the use cases and requirements to support the development of SAE Recom

17、mended Practice J2847/5, Customer Communication for Plug-in Vehicles. 2. REFERENCES 2.1 Applicable Documents The following publications form a part of this specification to the extent specified herein. Unless otherwise indicated, the latest issue of SAE publications shall apply. 2.1.1 SAE Publicatio

18、ns Available from SAE International, 400 Commonwealth Drive, Warrendale, PA 15096-0001, Tel: 877-606-7323 (inside USA and Canada) or +1 724-776-4970 (outside USA), www.sae.org. J1715TM Hybrid Electric Vehicle (HEV) and depicts the relationship of the U8 and U9 use cases within the structure. SAE INT

19、ERNATIONAL J2836/5 Issued MAY2015 Page 8 of 23 U1 U2 U3 U5S1 S2 S3S1: Cordset EVSE (120V AC to vehicle)S2: Premise EVSE (240V AC to vehicle)S3: Premise EVSE w/Charger(DC to vehicle)Utility Programs (Awareness, Specific Enrollment)Binding/Rebinding(Startup, VIN Authentication,Basic Charging per enrol

20、led program, Shutdown) (How)(Why)(What)PR1:ChargeV2G, V2H, V2L, V2VPR3:DiagnosticsPR4:VM SpecificDetailed Use Case SummaryU1: TOUU2: Direct Load/Price ControlU3: RTP (Active Management)U4: Critical Peak PricingU5: Optimized ChargingCustomer selects one or moreEGeneral Registration/Enrollment StepsIn

21、itial Setup for PHEV-Utility Communication and for each EVSE within the public charge site provide the brand name, type (SAE, Chademo, etc.), configuration (AC Level 1/2, DC Level 1/2, power rating, number couplers, etc.), operational status, and availability. EVSE Network Providers have a schedulin

22、g/reservation processing capability for specific EVSEs within designated public charge site. EVSE Network Providers, OEM telematics providers, or other have APPs developed to integrate public charge site location information with GPS Navigation systems for customer trip planning services. 7. Post Co

23、nditions Customer successfully acquires real time information about public charge site location and logistics; and is able to acquire scheduled EVSE slot reservations. Failure Conditions: There is a site host conflict or PEV processor fault. Internet Communications failure. Table 7 - U8 Scenario F -

24、 Customer convenience: Public charging - energy usage history NO. Type Description 1. Use Case Title Customer Convenience: Public Charging Energy Usage History 2. Use Case Element/Scenario ID U8 Scenario F 3. Objectives Customers will have ability to inquire and access information about energy usage

25、 history for PEV charging. 4. Description Customers want access to information about energy usage history relative to their PEV charging behavior. There are several scenarios in this regard: Customers will want energy usage history for PEV charging at their residence. Customers want ability to know

26、PEV charging portion of total residence energy usage. Customers will want information separated between residence energy usage and non-residence energy usage history. Customers will want aggregated PEV energy usage history to ascertain PEV efficiency based on energy usage versus electric miles trave

27、led. SAE INTERNATIONAL J2836/5 Issued MAY2015 Page 19 of 23 NO. Type Description Information on energy usage history and related price/cost may require the accumulation of data from alternative sources which may create complexity to the ability to provide the information scenarios specified above. T

28、here are three main actors that are sources for the elements of information required the PEV, Utility, and the EVSE Network Provider. Primary Actors: Customer, PEV, Utility, Secondary Actors: OEM Telematics Server, EVSE Network Provider Scenario/Conditions: The following are the conditions and scena

29、rios for providing energy usage history to the customer: Customers will want energy usage history for PEV charging at their residence. Information format is total residential energy usage and identification of portion or quantity of residential energy usage for PEV charging. Information can be reque

30、sted by year, month, week, day or periods of same, inception to date or by charge session. o Utility provides the residential energy usage information. May also provide PEV charging energy usage history based on the presumption the specific residence employs separate metering of PEV charging. Utilit

31、y will also provide the related cost of energy usage for the residence and for PEV charging separately under this presumption. o Alternatively if the residence does not separately meter energy usage for PEV charging then the information will need to be provided from the PEV which has the embedded co

32、mputer processing to measure and record energy consumption for PEV charging. Combining information from the PEV with the Utility residential energy consumption information will require the engagement of the OEM telematics server. The OEM telematics server will have to extrapolate the residential ene

33、rgy usage and cost data from the utility (Green Button or other utility protocol) requiring an interface between the OEM telematics server and the utility Green Button application server. Customer permissions will be required. OEM telematics server processes the combined information and provides to

34、the customer via website and/or smart phone APP. o Note that there may be variances in the accuracy of the kWh measurement data between the utility and the PEV but not a significant cost variance. o The EVSE Network Provider will typically not be tracking residential energy consumption for PEV charg

35、ing unless the residential charging by the specific customer is included in a subscription payment model which means the EVSE Network Provider is acting as the Energy Services Provider to the customer for PEV charging under a resale contract. o Further development of the EVSE Embedded Submetering pr

36、otocol will allow the EVSE Network Provider to become a secondary actor for providing the residential information. Under the CPUC Ruling EVSE Network Providers with EVSE Embedded Submeters will be responsible to provide the PEV charging submeter data to the utilities for billing purposes. SAE INTERN

37、ATIONAL J2836/5 Issued MAY2015 Page 20 of 23 NO. Type Description Customers request energy usage information segregated between residential and non-residential sources. Information can be requested by year, month, week, day or periods of same or inception to date o PEV is the primary source for this

38、 information. PEVs track and records charging locations based on GPS coordinates and can distinguish between home charging and away from home (public/workplace) charging. o Costs associated with this energy usage information from the PEV will be complex to determine due to the variability in pricing

39、 methods for non-residential charging. o OEM telematics providers have the capability to retrieve and report this information via a website and/or smart phone APP. o By virtue of applying the National Counsel of Weights and Measures HB 130 and HB 44 requirements for commercial EVSE - the EVSE Networ

40、k Provider may be a primary actor in providing energy usage information for non-residential PEV charging. Requires that all EVSE be submetered and provide pricing information to the customer. Based on customer account tracking the EVSE Network Provider can provide to the customer the energy consumpt

41、ion and cost data for non-residential PEV charging. This data combined with the data available for residential energy consumption from the PEV and utility could suffice to provide the customer with all related cost data. Customers will want aggregated PEV energy usage history to ascertain PEV effici

42、ency based on energy usage versus electric miles traveled. Information may be requested by inception to date, monthly, weekly, daily, or by trip. o This energy usage information is more relative to the energy used by the vehicle during driving modes versus energy usage history based on charging. o I

43、ndication is the related electric miles traveled related to the requested criteria will also be provided. o PEV is the primary source for both energy usage and miles traveled. OEM telematics providers can retrieve and report the information to the customer via website and/or smart phone APP. 5. Prer

44、equisite OEM Telematics Providers, Utilities, and EVSE Network Providers have in place the required telemetry, interfaces, and data collection/reporting protocols to acquire and consolidate customer requested energy usage history. 6. Requirements An established interface architecture utilizing stand

45、ard protocols between the OEM Telematics Providers, the utilities, and the EVSE Network Providers to process and share specific customer energy usage data predicated on compliance with regulatory, cyber security and privacy criteria. Legal and formal Customer permissions are needed to acquire, share

46、, and report energy usage data 7. Post Conditions Customer successfully acquires energy usage history data according to requested data parameters. SAE INTERNATIONAL J2836/5 Issued MAY2015 Page 21 of 23 NO. Type Description Failure Conditions: Security or privacy violations/issues, problem with data

47、reliability systems failure 5.2 Use Case: U9: Conflict and Resolution This use case addresses conflicts between customer preferences and other controlling sources for load management and Demand Response programs administered by utilities, facility EMSs, and aggregation services providers. This use c

48、ase also includes scenarios for identifying customer information requirements and responses to alerts for scheduled DR events and other load management programs Table 8 - U9 Scenario A - Conflict and resolution NO. Type Description 1. Use Case Title Conflict and Resolution 2. Use Case Element/Scenar

49、io ID U9 Scenario A 3. Objectives Customer preferences for charging may conflict with premise or facility Energy Management System load control parameters. Resolutions are determined either manually (business model or pricing options) or based on prescribed automated prioritization with notification 4. Description Customer or