Home

D3.3-Business Services Use Cases and

1. ecce 6 3 16 6 1488 UC Upload Service Content eese ener 6 3 16 7 1247 UC Confirm Service Contract Change cessent 6 3 16 8 1246 UC Create Service Contract Change Request suusss 6 3 17 1 1476 UC View Standard Interface Details sess 6 3 17 2 1475 UC Search and Select Standard Interface sess 6 3 17 3 1487 UC Download Service Specification cesses 6 3 18 1 1257 UC Propose new Standard Interface sss 6 3 18 2 1493 UC Publish Standard Interface ccccccscccccssssccesscceesssccesesseccesssseees 6 3 18 3 1489 UC Upload Service Specification eese 6 3 18 4 1476 UC View Standard Interface Details sess 6 3 18 5 1475 UC Search and Select Standard Interface euessssl 6 3 19 1 1373 UC Search and Select Business Partner esses 6 3 19 2 1374 UC Create Business Partner ACCOUnNt r annnrrnannnvannnnnvranannvrnesvnvrenennr 6 3 20 1 1373 UC Search and Select Business Partner sess 6 3 20 2 1376 UC Change Business Partner Account eese 6 3 20 3 1377 UC View Business Partner Account Details essss 6 3 20 4 1378 UC Change Business Partner Account Details 6 3 21 1 1373 UC Search and Select Business Partner
2. sessi nennen nnne inni nnns sitne en 38 Figure 12 Roaming as defined by Betterplace rrrrnrrnrnrrnnnnrnnnnnvnnnnvrvnnnvnnnnvnnrnnrennr renn nnnnennenrnrresnnrnnsnneneenn 65 Figure 13 Structure of the Roaming Domain sss eee trennt 65 Figure 14 Two Roaming variations esses eene enne sette entente rnnt innen en 66 Figure 15 Roaming Domain Authorization Process sssssssssssssssse eee nennen entren 67 Figure 16 Forward CDR Process floW rrrnannrannnnvnnon venns rrnnnnrnnnenvennr ann nnnnnn vennen nennen nennen tenter sits nnne en 68 Figure 17 Communication process for Roaming by bi lateral agreements ssssssssesss 74 Figure 18 Structure of the Energy Domain ssssssssssssssesseeeeee enne nennen nennen sns nennen 83 Figure 19 Marketplace Buying and Selling ccccccceeeeeeseeceeeeeceeeeeeaeeceeeeesaeeesaaeeseaeeseeeesaeeeteaeneeeees 106 Figure 20 Structure of the Marketplace Domain essere nennen nennen nent 106 Figure 21 Task Cases for Core Marketplace Services sss 107 Figure 22 Hierarchy of Actors in Core Marketplace Services sss 108 Figure 23 Call for Roadside Assistance sssssssssssssssesseseene ener enne 181 Figure 24 Get Current Position sssesssssssssssssesesee nennen enters nn isst nets enne senis stretti 182 Figure 25
3. cccssccccesssccceessccceesseceessseeccessseceessseccesaseccessseceeeaseceesaseeees 123 6 3 8 6 1627 UC Delete Request for a new Service cccccsssscccsssccceessceccessesccesseecsesecceesseceeaesesesseceessseceessaeesees 123 6 3 9 1 1239 UC Search and Select Services isse nidis reet a ntn sata ark s a pata a Ras RARE SA RA ER AR ERE RA ORAE R A RR RAS 124 6 3 9 2 1471 UC View Service Transaction Details esee enne nnne nnne nennen nnns 124 6 3 9 3 1242 UC Search and Select Service Transactions esses eene nnne nnne nnne nnne 125 6 3 10 1 1482 UC View Service Contract Template o cccccssssscscccsssssssscsccesssessssseescessesssasseescesesseuseeseceeesenaees 126 6 3 11 1 1485 UC Create Service COnltract cerit eia a Ene e ERR ea UR d e Enea nina eo enn 127 6 3 11 2 1482 UC View Service Contract Template ccssscccccccssessssscccccsssensssceccessecsssesscecsseensuseeseeesseenaaseesens 127 6 3 11 3 1624 UC Change Service Contract Offering essei seen rnnt nnne nne nnns 127 6 3 11 4 1479 UC View Service Contract Details sees eene nnne nnne nnne nnne nnne s 128 6 3 11 5 1470 UC Create Service Contract Offering eese sees eene nnn nenas ernst nan 129 6 3 11 6 1484 UC View Service Details rie iE dee ra era tb Ro tuba e AXE AE TRE RE pa p ARMED ARR REY o Reagan 129 6 3 12 1 1480 UC Create Service Contract Termination Request rrrrrrrrrrrrrrrrnrrrrrrrrrrrrrr
4. 6 3 15 7 1245 UC Search and Select Service Contracts This Use Case is listed before in this Chapter please refer to paragraph 6 3 5 3 Scope amp Level Core Service Find Service Contracts that satisfy search criteria 6 3 16 940 FTR Version Service Services can be changed by the Service Provider This results in a new Service Version GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 141 of 210 Green N eMotion BG AL 6 3 16 1 1239 UC Search and Select Services This Use Case is listed before in this Chapter please refer to paragraph 6 3 3 1 Scope amp Level Core Service Find Services that satisfy search criteria 6 3 16 2 1486 UC Enable Disable Service permanently This Use Case is listed before in this Chapter please refer to paragraph 6 3 15 5 Scope amp Level Core Service A service may be permanently enabled or disabled 6 3 16 3 1245 UC Search and Select Service Contracts This Use Case is listed before in this Chapter please refer to paragraph 6 3 5 3 Scope amp Level Core Service Find Service Contracts that satisfy search criteria 6 3 16 4 1494 UC Publish Service This Use Case is listed before in this Chapter please refer to paragraph 6 3 14 3 Scope amp Level Core Service A Service is published at the marketplace 6 3 16 5 1489 UC Upload Service Specification This Use Case is listed before in this Chapter please refer to paragraph 6 3 14 4 Scope amp Level Core Service
5. HP B i 5 1 Sufficient 1 Cancel o H H a 1 H 3 H o s Evaluate Options v 771 Identify potential Summarize and Comunicate and Service Providers order potential Register Change Congestion o Mgmt Contracts au i d 2 gt E E amp amp i High Prio od 2 1 en z Low Prio Medium Prio H i i i EU 2 H a a H u H ER Congestion E Pod Mgmt Contracts z H ti i i v H H Pod 5 Lu E C a Process Financial g i H H HH Compensation E i I E i I ii m implement business rules for Calculate and report H Control Vehicle EV charging and V2G flexibility current potential Action 2 Decrease or Increase 2e z 1 Load or Activate V2G v gt i T H Ei 1 a Lj 9 oa c H S S H Decrease or Increase H i Control Charging Point Action Calculate and report current potential EVSE Operator GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 179 of 210 eMotion Green jon a 2 1200 BPD Enhanced charging 9 0O 2 a Driver Request Review Options Cancel il O i 1 gt Vehicle Request ri A H H z i 1 2 SE E H E 1 2 f i f Business Rule ER i OEM Profile i Vehicle Profile H i 8 3 ee ness RUE Register Transaction i Ao EE H 5 i Authorize Request Organize Payment 1 Organize Payment E 1 5 L A o i H
6. Most of these sub processes are covered by the contract management functional component except for the call of services The call of services is based upon the marketplace s functionality of routing the ser vice call of a service requester to the corresponding service provider In addition the marketplace is able to aggregate the results of different service providers Additionally the core marketplace services provide functionality to support the Selling and Buying processes The following figure shows the main functional components of the core marketplace services based upon the business scenarios defined in the Deliverable 3 1 GeM D3 1 BusinessAnalysis V1 4 FINAL WP3 Core Marketplace Services Buying Sellin Standardisa l pean S Service Detail l Contract l Partner and Routin ti f E Records Management iis 5 Management Services Interfaces 8 Figure 20 Structure of the Marketplace Domain GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 106 of 210 Green NS eMotion EE L en E In addition the marketplace offers the ability to record details of the service calls for use in accounting and billing Among the creation of service contracts between business partners the contract management component provides functionality for changing and terminating service contracts A further functional component handles the standardization of interfaces This allows providing similar value added services by diff
7. GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 21 of 210 Green DN eMotion BG AL Marketplace context The before charging services described in this chapter are not exhaustive and number of similar services are expected to be offered in the future by service providers directly or through Marketplaces Currently these services satisfy Business scenarios described in the Charging and OEM domain through the fea tures listed in the table below section 2 3 2 The main use case of this section is 1510Before charging and is complemented by several additional use cases which realize the same features The following table lists the Features that are relevant in the before charging phase ref 2 1 Features Use Cases 917 FTR Basic enhanced charging 1510 UC Before charging 918 FTR Enhanced charging 1527 UC Search for EVSE 1278 FTR Identification of available EVSE 1528 UC Reservation of EVSE 1296 FTR Third party information 1574 Third party information 969 FTR EVSE Charging capabilities 978 FTR Search for charge point or battery switch station 1318 FTR Reservation of Charge Spot Table 2 2 Before Charging Features and their Use Cases Several interactions between these actors as are illustrated in 1200 BPD Enhanced charging please re fer to Appendix B 2 3 2 Before Charging Feature Content 917 FTR Basic enhanced charging Driver can search either by using in vehicle device or mobile phone f
8. esses 6 3 21 2 1480 UC Create Service Contract Termination Request 6 3 21 3 1376 UC Change Business Partner Account rrrrnnnnrrnnnrnnnnnnnnrrrnnsnnnnnnnnnrnr 6 3 21 4 1377 UC View Business Partner Account Details sess 6 3 21 5 1481 UC Confirm Service Contract Termination eese GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 191 of 210 Green NI eMotion BG JL 6 3 21 6 1379 UC Activate Business Partner ACCOUnNt rrrrnnnnnnrrnnrnnnnnnnnnrrnrnnnnnnnnnnerrrnrnnnnnenrrrrnnrnnnnneesrernnrnnnnneeeer 150 6 3 21 7 1380 UC Deactivate Business Partner ACCOUNT sssssseeeccececseeeseececcececnensseeeecesesseusssececessesueneseeeeeees 151 hYqIbIIIB e sanne 153 GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 192 of 210 Green N eMotion LY E Business Scenario s and their Features Ed For the development of Features and Use Cases these Business Scenario s have been elaborated as illustrated in the following table ID Business Scenario Description Satisfied By 1179 BS C1a Charging at home All services basic end user and B2B related charging EV at residential location 557 FTR Reduce load of charging 960 FTR Charging and battery switching status notification 1809 FTR EVSE Service Access 1277 FTR Phone roaming 976 FTR Charging management 563 FTR User identification 953 FTR Human machin
9. Alternatives Related information Access Role Based Authorization required Data Security Data Integrity must be guaranteed Data Confidentiality must be ensured Data Privacy Sensitive Data is only stored when needed and authorized Data Export Policy required Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market 6 3 11 6 1484 UC View Service Details This Use Case is listed before in this Chapter please refer to paragraph 6 3 3 2 Scope amp Level Core Service View the details of a selected Service 6 3 12 931 FTR Change or Terminate Service Contract Any Service Contract can be changed or terminated at any time if both Business Partners Service Pro vider and Service Requester agree This is implemented in a two step asynchronous process e The first Business Partner requests unilateral contract change or termination by the other Business Partner This action is reported to both Business Partners GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 129 of 210 Green N eMotion EE AL V The other Business Partner can then accept or decline at will Note The requesting Business Partner should be able to revoke a request that is still pending 6 3 12 1 1480 UC Create Service Contract Termination Request Goal in context A termination of a bilateral Service Contract is a two step pro
10. Alternatives J 0000000000000 Variations J Related information Access Role Based Authorization required Data Privacy Sensitive Data is only stored when needed and authorized Data Export Policy required Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market 6 3 8 5 1626 UC Change Request for a new Service Scope amp Level Goal in context The Service Requester changes his own Request An existing Request for a new Service is selected Successful out An existing Request for a new Service is changed come Failure outcomes Failure Outcome Condition leading to outcome Request for a new Display of an Not all required attributes of the Re Service is incomplete error message quest for a new Service are filled CC Er m y 138 ACT Service Requester Secondaryactor Main scenario e The Service Requester changes the attributes in a prefilled form with the requirements of his own Request e The changed Request for a new Service is stored Alternatives Variations J Related information Access Role Based Authorization required Data Privacy Sensitive Data is only stored when needed and authorized Data Export Policy required Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability requir
11. Develop and test Service Service Interface H i i i i i i 1 B Call Service i i i i Service Requester GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 162 of 210 Green NyN ES AL eMotion LY 1456 BPD Use of Services GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 163 of 210 Green IN ET p eMotion LY 1431 BPD Contracting Service GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 164 of 210 eMotion Green jon EE 2 1495 BPD Service Detail Records for Accounting and Billing Service Catalog Service Contract GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 165 of 210 Green N eMotion VY 1410 BPD Define and Register Service Contract Offering Service Contract Framework Service Contract Offering GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 E Page 166 of 210 Green IN E 2 eMotion LY 1426 BPD Change or terminate a Service Contract rc GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 167 of 210 Green Ny EE JL eMotion LY 1427 BPD Prolong Service Contract M Service Contract Contract History GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 168 of 210 Green I EE 2 eMotion LY 1428 BPD Enable Disable Service permanently Service Provider O Reject Disabling LLL
12. FTR Authentication of user 1160 BS O1 Enhanced charging 1182 BS R3a Differentiation of customer con tracts SLA check 1794 GRP Identification and Authentication of EV user 1180 BS C1b Semi public charging 1179 BS C1a Charging at home 1181 BS C1c Public charging 1356 BS O4 Basic charging 1161 BS R1 Contractual clearing 917 FTR Basic enhanced charging 1160 BS O1 Enhanced charging 920 FTR Battery life 1162 BS O3 Driver enhanced services 1797 GRP Driving Related Services 956 FTR Battery switching 1356 BS O4 Basic charging 926 FTR Call of Service 1173 BS S1 Marketplace Buying Selling Rout ing 1300 FTR Car information 1798 GRP Cross Domain Services 1368 FTR Change Business Partner Account 1178 BS S6 B2B Partner Management 931 FTR Change or Terminate Service Con 1175 BS S3 B2B Contract Management tract 1357 FTR Charge data collection 1356 BS O4 Basic charging 1299 FTR Charge point management 1795 GRP Services During Charging 950 FTR Charging as guest 1179 BS C1a Charging at home 1309 FTR Charging location mgmt 1543 Run Marketplace 1797 GRP Driving Related Services 976 FTR Charging management 1180 BS C1b Semi public charging 1179 BS C1a Charging at home 1181 BS C1c Public charging GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 200 of 210 Green Dy eMo er BG ID Feature Satisfies 1
13. Green DN eMotion BG Note that for the Cross Domain Features each Feature comprises a number of distinct Use Cases one to many but there are a few fundamental Use Cases such as Access Car Information that support mul tiple Features many to few Feature Use Cases 1300 FTR Car information 1548 UC Access Car Information 1303 FTR Intermodality 1520 UC Users can book pool cars online planning 1525 UC User wants travel and has specific requirements 1548 UC Access Car Information 1301 FTR Fleet management 1522 UC Assign car to scenario 1520 UC Users can book pool cars online 1521 UC Status for cars can be maintained by Fleet Manager 1523 UC Fleet manager tracks pool car 1524 UC Fleet manager monitors energy consumption of pool cars 1320 FTRCO2 intensity 1592 UCCO2 Reporting Table 3 8Cross Domain Services Features and their Use Cases 3 4 1 1300 FTR Car information In order to enable scenarios like intermodal planning and fleet management it is important to have addi tional car information available such as general and detailed information in the categories current status technical performance data usability payload and space and offered equipment infotainment Current status e actual state of charge e remaining range e connection to EVSE and possible options e g pre condition heating or air conditioning possible and offered as additional services e winter summer tires mounted
14. Technical and performance data e range eventually with a minimum average maximum band according to driving and temperature conditions e charging time and capabilities AC 1 2 or 3 phase or DC with power levels battery switching support of ISO15118 with individual contract certificate upload as additional service offered e maximum battery capacity e 2WD or 4AWD e acceleration and top speed e information on range extender yes no Usability e number of seats information on flexibility e g 3rd row can be flatten in trunk e number of doors e volume of trunk e maximum payload GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 56 of 210 Green DN eMotion BG L V e safety systems Isofix system for child s safety seat yes no e possibility of roof box to be mounted yes no and eventually to be order as additional service Equipment Infotainment e Air conditioning electric seat adjustment seat heating etc e navigation system e internet access connectivity e audio system and connections e g USB connection for smart phones This feature also comprises information of a car s charging capabilities in order to locate only compatible EVSE options to the driver 3 4 1 1 1548 UC Access Car Information Scope amp Level Value Added Service Users should get access to car information items Goal in context Users should get access to car information items e g state of charge est range etc Flee
15. 1177 BS S5 Linking of Systems Managing the Marketplace connec 1446 FTR Search and Select Standard Interfaces Standardization of Inter tions with SP backend systems 1459 FTR Aggregate Service Call Results faces Messages 1445 FTR Define new Standard Interface 1617 FTR Marketplace Authentication and Authorization 1469 FTR Suspend Resume Service Contract 1178 BS S6 B2B Partner Manage Service Provider and Requestor Life 1386 FTR Delete Business Partner Account 1366 FTR Create Business Partner Account 1369 FTR Activate Inactivate a Business Partner Account 1368 FTR Change Business Partner Account 1617 FTR Marketplace Authentication and Authorization GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 199 of 210 Green Dy eMotion V F Features Where Used in Business Scenario s ID Feature Satisfies 1369 FTR Activate Deactivate a Business Part 1178 BS S6 B2B Partner Management ner Account 1459 FTR Aggregate Service Call Results 1173 BS S1 Marketplace Buying Selling Rout ing 1177 BS S5 Linking of Systems Standardization of Interfaces Messages 971 FTR Aggregated balancing capacity to 34 BS E2 Virtual Power plant the TSO 1313 FTR Allow interrupting 30 BS E1b Centralized Congestion Mgmt TOU tariff 975 FTR Ancillary services 34 BS E2 Virtual Power plant 981 FTR Authentication 1161 BS R1 Contractual clearing 979
16. 6 3 18 4 1476 UC View Standard Interface Details This Use Case is listed before in this Chapter please refer to paragraph 6 3 14 8 Scope amp Level Core Service View Standard Interfaces details 6 3 18 5 1475 UC Search and Select Standard Interface This Use Case is listed before in this Chapter please refer to paragraph 6 3 14 9 Scope amp Level Core Service Find Standard Interfaces that satisfy search criteria 6 3 19 1366 FTR Create Business Partner Account For a Business Partner that requests access to the GeM Marketplace the following actions have to be approved by the Marketplace Business Manager e Creation of a Business Partner Object in the GeM Marketplace e Provision of an access mechanism to the GeM Marketplace e Partner Contract between the Business Partner and the GeM Marketplace 6 3 19 1 1373 UC Search and Select Business Partner GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 145 0f 210 Green N eMotion EG AL V Business Partners that satisfy search criteria The searching actor is the Marketplace Business Operator Successful out The Marketplace Business Operator receives an ordered list of the Business Part come ners that meet his search criteria and is able to select one or more Business from the list for further activities Search criteria may include e Business Partners that act as Service Providers e Business Partners that act as Service Requester e Active and inactive Business Pa
17. ACT EVSE Electric Vehicle Supply is used to exchange energy between the EV Equipment and the Grid 1406 ACT EVSE Backend Backend administrative systems of the EVSE Operator as opposed to frontend on site sys tems that communicate directly with EV s 132 ACT EVSE Operator in charge of managing the EVSEs 128 ACT EVSP Electric Vehicle Service Pro offers e mobility services to the end customers vider 1407 ACT EVSP Backend Backend administrative systems of the EVSP 1540 ACT HMI Human Machine Interface interface allowing the vehicle user to receive information relative to the charging process and provide input to the charging system 136 ACT Marketplace Operator Operates the platform and communications and manages access to and working of the marketplace 1541 ACT SECC Supply Equipment Communi implements the communication to one or multi cation Controller ple EVCCs 133 ACT Vehicle Driver Human currently driving the Vehicle Table 4 9 Roaming Domain Actors GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 69 of 210 4 3 Features and Use Cases 4 3 1 Overview Green Dy eMotion LY The following table lists the Roaming Features and their Use Cases ID Feature Realized By 985 FTR Roaming in same 1512 UC Start a roaming charging process with Clearinghouse country using Clearing 1502 UC EV Identification Authentication and Authorization House 1518 UC During charging 151
18. Authorization Figure 7 User Identification Scenario s Source ISO 15118 1 GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 29 of 210 Green NN Ka eMotion A ss skyet The following figure illustrates the communication when a visitor in this figure subscriber requests charg ing services from an EVSE operator in the figure Charge Network Operator from the perspective of Bet ter Place EV Driver EVSE EVSE Operator EVSP Tap card Cable connect Figure 8 User Identification as implemented by Betterplace Roaming A visitor taps his RFID card to access charging services from an EVSE The slot opens and he connects the car and the EVSE with a compatible cable A charge request is send to the local EVSE operator ei ther automatically or with certain specified services by the visitor e g priority charge The EVSE opera tor can identify that it is a visitor The EVSE operator asks the EVSP of the visitor in a case of bilateral agreement between the two to authorize the customer and to specify his service level This allows the EVSP to inform his customer about the authorization Based on authorization and service level the EVSE operator creates a charge plan While the plan is send to the EVSP the charge session commences The EVSP can then inform the customer about the charge plan During the charge session when the charging ends the EVSE operator creates a transaction report how much is charged
19. Backend issues EVSP backend EVSE opera tor backend has sent wrong END A h SE 3 Q O 131 ACT EVSE Operator Backend 128 ACT EVSP Backend 136 ACT Marketplace Operator 140 ACT Clearinghouse Main scenario clearing house gets a charge request clearing house checks the available con tracts and clears the request accordingly clearing house notifies the requesting EVSE operator backend Alternatives Charging is started anyway and customer is billed directly at charge point site Authorization is done bilaterally between EVSPs EVSE operators Related informa see Business Process Diagram Contractual Clearing Authorization 1270 tion 4 3 2 2 1502 UC EV Identification Authentication and Authorization This Use Case is listed before in this Chapter please refer to paragraph 2 4 3 1 Scope amp Level Basic end user services This use case covers identification of contract belonging to a user own customer or roamer at a charge spot or battery switch station and his authentication and au thorization to execute the process of charging or battery switching Use case describes the interaction between EV EV driver EVSP EVSE operator and optionally the Clearinghouse when roaming GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 71 of 210 Green N eMotion BG L V 4 3 2 3 1518 UC during charging This Use Case is listed before please refer to paragraph 2 5 3 1 Scope amp Level End user servi
20. Contract is updated within the Clearing House come comes e backend errors Primary actor 128 ACT EVSP Electric Vehicle Service Provider 131 ACT EVSE Electric Vehicle Supply Equipment Secondary ac 140 ACT Clearinghouse tors 136 ACT Marketplace Operator the clearing house clearing house stores the changes have to go full round trip each time Contracts are changed within Marketplace and the Clearing House has access to them tion 4 3 8 2 1512 UC Start a roaming charging process with Clearinghouse This Use Case is listed before in this Chapter please refer to paragraph 4 3 2 1 Scope amp Level Clearing Service Trigger to start a roaming charge after the transaction has been validated by the clearinghouse GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 78 of 210 Green DN eMotion BG L 4 3 8 3 1513 UC Delete EVSP EVSE Contract from Clearing House their mutual relation tracked by the clearing house is informed about the changes Preconditions Contract already exists in the clearing house Marketplace is operational Business Partner is authorized for clearing services and enlisted in the Marketplace come come Contract can Clearing requests are still granted e faulty API call not be deleted e backend errors e connectivity issues ed 128 ACT EVSP Electric Vehicle Service Provider 131 ACT EVSE Electric Vehicle Supply Equipment 140 ACT Clearinghouse EVSP or EVSE operator wants t
21. During the service registration the Service Provider uploads the service specification i e Service Interface e g WSDL and Service Description of the offered Service 6 3 16 6 1488 UC Upload Service Content This Use Case is listed before in this Chapter please refer to paragraph 6 3 14 6 Scope amp Level Core Service During the service registration the Service Provider may upload additional content of the offered Service 6 3 16 7 1247 UC Confirm Service Contract Change This Use Case is listed before in this Chapter please refer to paragraph 6 3 12 5 Scope amp Level Core Service A change of a bilateral Service Contract is a two step process A Business Partner Service Provider or Service Requester accepts or rejects a change request on a Service Contract made by the other Business Partner GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 142 of 210 Green NN eMotion BE AL V 6 3 16 8 1246 UC Create Service Contract Change Request This Use Case is listed before in this Chapter please refer to paragraph 6 3 12 6 Scope amp Level Core Service A change of a bilateral Service Contract is a two step process A Business Partner Service Provider or Service Requester makes a change re quest on a Service Contract 6 3 17 1446 FTR Search and Select Standard Interfaces Service Providers can search and select published Standard Interfaces from the Standard Interface Cata logue Service Prov
22. Electric Vehicle Communication EVCC Controller SLA Service level agreement EVSE Electric vehicle supply equipment SOC State of Charge 96 EVSP Electric vehicle service provider TOU Time of use Grid for vehicle EU research GAV project TSO Transmission System Operator GeM Green eMotion V2G Vehicle to grid HMI Human machine interface V2H Vehicle to home Information Communication ICT Technology VPP Virtual power plant IMS Infrastructure management system WP Work Package GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 8 of 210 Green N eMotion BG Executive summary This deliverable comprises the requirements of e mobility organized through shared information plat form s The Green eMotion Marketplace eco system Partners from relevant e mobility related industries participating in this work package WP3 have defined services which are from their perspective most likely to be used in the demo regions during the first and second release These services were suggested by GeM partners because of their high added value their early market adoption their business oriented perspective as well as the user acceptability The results of the stakeholder analysis and surveys from D3 1 were described as high level business scenarios and were with the use of applied meta model transformed with increasing granularity to features and use cases described in the D3 3 deliverable These requirements will be further detailed by IT developer
23. S S D mmm Te Accept Disabling v v All Contracts terminated v Y D D D D Service Contract Service Contract History Service Catalog Image Catalog Service Catalog Image Catalog i P 1 Service Disabling Request Service Disabling Reply GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 169 of 210 Marketplace Frontend eMotion Green ion El 1387 BPD Service Registration D 0 mi se Standard Contract Acceptance Cancellation Pre Marketplace v Y D Standard Interface H Service Interface Standard Interface Service Contract Service Contract Catalog j and Description Framework Offering a ea eee ere Downloadable Content GA MOVE FP7 265499 Green eiviouon WF 5 DeilveraDie 5 5 Page I U OT Z 1U Green NyN ER TL eMotion LY 1429 BPD Delete Service GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 171 of 210 Green Ny ES AL eMotion V 1271 BPD Propose Standard Interface Business Partner Interface acceptable as Standard Marketplace V D Standard Interface Catalog GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 172 0f 210 Green N 3 2 eMotion A 1363 BPD B2B Partner Management Create Business Partner Account v D Partner Contract GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 173 of 210 Green Ny Ex wa eMot
24. antee this information to be propagated Therefore the EV modifies its charg ing pattern and feeds back power profile to the EVSE that migrates it to the EVSE Operator back end The EVSE Op back end finally aggregates the updated power profiles gath ered from the EVSEs and makes available this update to the DSO as a fulfill ment of its initial request An EVSE could be implemented without the capability to communicate with an EVSE GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 88 of 210 Green DN eMotion Ea N 4 operator backend This would however implicate that it cannot interact with the DSO In this case it would charge regardless of any DSO detections This could be prob lematic when EV penetration into the market becomes higher Variations The DSO may decide not to use the load reduction availability from the EVSEs be cause it is not significant or other reasons Related informa This use case shows the chance of reducing load profile which can be used to sup tion port the DSO in order to operate selectively Instead of stopping the service the EVSE could offer a limited service in order to accomplish the DSO s requirement Issues Regulation and local legislation 5 3 3 973 FTR Reactive power The injection of reactive power coming from a distributed generation unit such as an EVSE into the grid makes it possible to reduce the amount of reactive power on the distribution lines re phasing the mid
25. level product component functionality e Use case describing the interaction of actors towards the system comprehensive elaboration of Features describing goal scope successful outcome possible failures work flow and possible varia tions Rational Requirements Composer Tool The use of the RRC tool helped to increase the Green eMotion Project WP3 team s requirements gather ing efficiency in three distinct ways 1 Eliminate wasteful effort and rework To avoid wasteful efforts and rework the RRC requirements definition helped to avoid the com pounded cost of rework from duplicate efforts and lack of document version control due to documents being passed around the team 2 Respond quickly to dynamic business needs Grouping of documents into defined sets and maintain that relationship over the course of the project enabled the WP3 team to work in secure repositories to collaborate more effectively with stake holders and to customize groups of related requirements artifacts into collections or modules for bet ter quicker organization and retrieval of information 3 Rational Requirement Composer RRC is a IBM Software Product GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 13 of 210 Green I EI 2 eMotion V 3 Deliver high quality products and applications with confidence When documents and spreadsheets are used to define and manage requirements at the beginning of the project teams often lack a me
26. ter 3 read 3 2 and 3 3 1 Please note that chapter 2 has sub chapters than the overview of ser vices is at the beginning of every sub chapter 2 3 1 2 4 1 Select the features service of interest and either continue into the chapter or refer to table of contents to see the page number where the feature description and its use cases start To search for a particular use case you can refer to appendix which lists all use cases in order as they appear in the document The Document is primarily divided to chapters by logical grouping of features services to which the order of Use cases is subordinated Use cases are always described in the chapter where they appear for the first time when the same use case realizes a different feature in a chapter later in the text a reference is made to the first instance The Appendix includes a complete list of 98 use cases organized by the chapters in which they are fully described their first occurrence Each chapter starts with table overview of actors and services fea tures followed by detailed use case descriptions realizing the features There are 75 services structured in 5 chapters as follows Charging services 22 Services Use case tables marked in Red color Driving and Cross 11 Services Domain Services Use Case tables marked in Purple color Roaming services 7 Services Use case tables marked in Green color Energy services 13 Services Use case tables marked in Yellow colo
27. the potential buyer Energy supplier in future also TSO may decide whether or not to use the EVSP provided balancing service The buyer will base his decision on the aggregation of offerings over different load areas under responsibility of dif ferent DSO s Use cases that realize this Feature are also illustrated in Appendix B for more please refer to e 1186 BPD Centralized Congestion Management e 1198 BPD Congestion Management through TOU Tariffs e 1199 BPD Distributed Congestion Management 5 3 6 1 1604 UC Vehicle to grid signal This Use Case is listed before in this Chapter please refer to paragraph 5 3 2 1 Scope amp Level Value added service This use case enables the DSO or other energy stakeholders to distribute the need GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 94 of 210 eMotion Green on E 7 __ for congestion management to multiple service providers through the marketplace 5 3 6 2 1601 UC provide balancing capacity Value added service An EVSP acting as aggregator in the energy market will be able to offer energy from the batteries of the EVs used by its customers that are connected to the re charging infrastructure in a certain timeslot This service may be published from an EVSP on the marketplace and provided to DSO TSO or energy vendors according to the regulatory framework That is In case of balancing services the energy will be bought by the system operator But if the
28. 1520 UC Users can book pool cars online Scope amp Level Value Added Service Goal in context User wants to have a pool car in a specific time frame for a specific trip Preconditions Pool cars available booking homepage is available Fleet Manager is in place Cars communicate at least their Status of charge and the vehicle identification number Successful outcome A sufficiently charged car is available and reserved for the user Failure outcomes Failure Outcome Condition leading to outcome no car available no car is reserved request no car is available which is suffi remains in a queue cient for the request of the user no charge point no car is reserved request the car has to recharge at least available remains in a queue once during the trip and no charge point is available qo Primary actor 133 ACT Vehicle Driver Secondary actors 1594 ACT Fleetmanager propriate car and informs user about reservation Alternatives the fleet manager can try to find an appropriate car manually Variations Related information 3 4 2 2 1525 UC User wants to travel and has specific requirements Scope amp Level Value Added Service of transport He can book his planned travel online Preconditions Marketplace is operational Carpooling is available User has a contract with mobility provider Other means of transportation are available as well as their systems System checks for the best connection considering all mean
29. 265499 Green eMotion WP 3 Deliverable 3 3 Page 205 of 210 Green Dy eMotion V Service Provider from Clearing House ID Use Case Realizes Feature 1500 UC Change EVSP EVSE Contract 1291 FTR CLEARING Managing EVSP data within Clearing House 1626 UC Change Request for a new 1622 FTR Manage Requests for new Services Service 1624 UC Change Service Contract Of 1396 FTR Define and Register Service Contract fering 1529 UC Charging Location mgmt 1309 FTR Charging location mgmt 1592 UC CO2 Reporting 1320 FTR CO2 intensity 1247 UC Confirm Service Contract 940 FTR Version Service Change 931 FTR Change or Terminate Service Contract 1481 UC Confirm Service Contract 1369 FTR Activate Inactivate a Business Partner Ac Termination count 1443 FTR Enable Disable Service 931 FTR Change or Terminate Service Contract 1575 UC Crash Notification 944 FTR Vehicle tracking 1374 UC Create Business Partner Ac 1366 FTR Create Business Partner Account count 1514 UC Create Customer Contract by 982 FTR CLEARING Validation of contract Service Provider in Clearing 983 FTR CLEARING Managing customer data House 1497 UC Create EVSP EVSE Contract 1291 FTR CLEARING Managing EVSP data within Clearing House 982 FTR CLEARING Validation of contract 1625 UC Create Request for a new 1622 FTR Manage Requests for new Services Service 1629 UC Create Response on Re 1622 FTR Manage Reque
30. 29 2 4 3 Identification and authorization Use Case Sj rrrrrannrrnnvrrnnvrnnnvrnenvrnenvnnnnvensnversnversnresnvrssnnsssnrsssnressnen 31 2 5 Services during charging EV connect disconnect cccccescccceessccceessscceessecsessscsesensseceessssessnssseeesssseeeseeaas 33 2 5 1 During Charging Overview rrrrrrrnnnnnnnrrvnrrrnrnnnnnrrvnnssnnnnnnnrrnnsnssnnnnnrsnnssssnnnnnnnsnnesssnnnnnsnnnesssnnsnnasnnnnnnnen 33 2 5 2 During Charging Feature Content ccccccccccccsssssccccceessssssseeesecesseesseeeecessseseseeeeeeseesesaseeeeeeseseseaseeeaes 34 2 5 3 During Charging Use Cassels rociera ei Yen eU eae ea eve a E MERE eve e epe seaeagiceboevsvacesaes 36 2 6 Service performed after charging of EV ccsscccssssccccessssccessssccesseeccesssecceesseccsessseceesssscesesseccessseeeescasseeesasees 38 2 6 1 After Charging OVerVieW ese iie e triti teo teorie be e studeres 38 2 6 2 After Charging Feature COntent cccccccccsssccccsssececssseccessseecesseeecesaeeccesseeecesaeeesessseeeesseeesensecnseeeees 39 2 6 3 After Charging Use Cases siae eoe or HI di ruat cea a Dee a ET c EEG RR AAE 39 3 Driving and cross domain use case model runnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnes 41 3 1 OAA A T E mene 41 3 2 fnnc e a aa Ea aa e eaS EEEa aTa eA EAE aa a Da E EREE 41 3 3 Driving Features and Use Cases seirama iaaea ves THRE
31. 5 By nature this domain is more technical than the other domains This is also the main area of impact for the User Interaction requirements which were catalogued using a special methodology described in Section 1 3 1 2 Methodology Structured Requirements Management In D3 1 the WP3 team developed of a series of high level Business scenarios for EV charging and the related information flow based upon the collected best practices and lesson learned from previous Euro pean projects This collected content was gathered from multiple resources such as other projects deliverables inter views group calls and workshops To use this information for the creation of the marketplace various aspects such as roles rules dependencies and purpose of the scenarios must be clearly defined and well structured For this purpose WP3 has adopted the Structured Requirements Management Method with the use of dedicated tooling the Rational Requirements Composer RRC In D3 3 the WP3 team described the high level Business scenarios divided them into Features and realized these features by comprehensively described Use cases These artifacts and the relations be tween them form the basis of the meta model e Business scenario high level description of a possible business services with the use of the Mar ketplace its actors value drivers costs e Feature textual description of each of the business services of a scenario Features describe high
32. 971 FTR Aggregated balancing capacity esses esee nn nnns nn 93 5 3 7 965 FIR Peak shaving om MV ues cien eoe oret ed erae xen eua eee eaat e didan naaier ENS E een 96 5 3 8 1317 FIR P k shaving On LV erreneren naaa ar aaae ra ee aa aaa Ea EUER RR eee eben ena EE Rn uar pe Uo 98 5 3 9 1313 FTR Allow interrupting siisii ooo irr Ro en ERR Reo ERO isteden SERERE RARE ER Cogo Cre aan ak 98 53 10 961 FIR DSO predefines peaks rte tere E desea demens FERRE SE ERRAT ET ERER EN ERE C EUER Set ERE 99 5 3 11 966 FIR Current EV charg hannes ey BERE ERR EP AERE DPI ERR eR ERE tan EM Eee t oaa d rese Re MARRE 101 5 3 12 1202 FTR V2G energy supply signal cccccsssscccceesssssseeeeccesseeseseeeeeeseseasseeeeeeseeeaseeeeeeesesseeaeeeaaes 103 53 13 560 FTR V2H supply signal 2 rire ote rro Da Ero eov ea a FUn ga eda Pale SR Aa sedrer REESE YS eanet mann 104 5 3 14 967 FIR History of EVSE use rrrrnnnnrrrnnnnrrrronnnrrrnnnnrrrnnnnrrernnnnnnnnsnnnnnnnnnrnsennnnnnsennvensnnnvvenennnnnssenannnnnnen 104 6 Core marketplace services use case MOdel asssnrnnnnnnrnnnnnnnnnnnnnnnnnnnnnnnnunnnennnnnnnnnnnunnnnnennnnnnnnnnnnnnennnnnnnuener 106 6 1 em eda 106 6 2 gno 108 6 3 Features nd Use Ge CP 109 6 3 1 eT teens 109 GA MOVE FP7 265499 Green eMotion WP 3 Delivera
33. Business Partner is terminated come Failure outcomes Failure Outcome Condition leading to outcome Primary actor 1355 ACT Business Partner Secondary actor Main scenario e The Business Partner performs a logout e The session for the Business Partner is terminated Alternatives 2 Variations Related informa tion Issues Availability 24 7 availability required Performance sub second response time for Marketplace Transactions Scalability capable to grow with electro mobility market 6 3 2 2 1618 UC Marketplace Login Core Service Goal in context A Business Partner authenticates himself against the marketplace Business Partner is registered before Successful out The Business Partner has access to the marketplace based on his role come Failure outcomes Failure Outcome Condition leading to outcome Login failed Display of an error Business Partner does not provide message the correct credentials Primary actor 1355 ACT Business Partner Secondary actor Main scenario The Business Partner provides his credentials The marketplace checks the given credentials The role of the Business Partner and his access rights are determined A session for the Business Partner is created Alternatives Related informa tion GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 111 of 210 Green N eMotion BE AL V Access Role Based Authorization required Password Policy required Availability
34. Contract Template 1494 UC Publish Service 1489 UC Upload Service Specification 1470 UC Create Service Contract Offering 1488 UC Upload Service Content 1250 UC Register Service 1476 UC View Standard Interface Details 1475 UC Search and Select Standard Interface 1443 FTR Enable Disable Ser vice 1255 UC Start Stop Service 1480 UC Create Service Contract Termination Request 1687 UC Notify Service Requesters of own Service 1481 UC Confirm Service Contract Termination 1486 UC Enable Disable Service permanently 1479 UC View Service Contract Details 1245 UC Search and Select Service Contracts 940 FTR Version Service 1239 UC Search and Select Services 1486 UC Enable Disable Service permanently 1245 UC Search and Select Service Contracts 1494 UC Publish Service 1489 UC Upload Service Specification 1488 UC Upload Service Content 1247 UC Confirm Service Contract Change 1246 UC Create Service Contract Change Request 1446 FTR Search and Select Standard Interfaces 1476 UC View Standard Interface Details 1475 UC Search and Select Standard Interface 1487 UC Download Service Specification 1445 FTR Define new Standard Interface 1257 UC Propose new Standard Interface 1493 UC Publish Standard Interface 1489 UC Upload Service Specification 1476 UC View Standard Interface Details 1475 UC Search and Select Standard Interface 1366 FTR Create Business Part ner Account 1373 UC Search and Sele
35. Controller EVCCs 137 ACT Service Provider Business Partner that offers and sells EV Ser vices on the marketplace 138 ACT Service Requester Business Partner that consumes EV Services on the Marketplace 1579 ACT Third Party Service Provider An actor which provides access to third party data 133 ACT Vehicle Driver Human currently driving the Vehicle Table 2 1 Charging Domain Actors GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 20 of 210 Green N eMotion Ea L V 2 3 Enduser services before charging 2 3 1 Before Charging Overview Business services described in this chapter support the first part of the charging cycle the time before the driver parks his car and connects the EV to a charging point The area in the red square on a figure below illustrates the part of the cycle timeline where these ser vices occur 2 4 User parks EV near f User connects EVto Userisgoodtogo Charging can may or may not User disconnects EV EV is parked an available charge charge socket EV lights blink due to occur from charge socket disconnected from socket immediate charge user might connect the charge socket cable back right again Parking cycle Charge cycle Parking cycle Connection sequence Charge Dis connection sequence Figure 6 Scope of Before Charging End user perspective Basic end user services in this sub chapter include the possibility to set ch
36. Data Security Data Integrity must be guaranteed Data Confidentiality must be ensured Data Privacy Sensitive Data is only stored when needed and authorized Data Export Policy required Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market 6 3 13 1469 FTR Suspend Resume Service Contract The Service Requester can suspend resume his own Contracts Suspended Service Contracts will not be taken in account during service calls But the Service Contract remains still valid 6 3 13 1 1479 UC View Service Contract Details This Use Case is listed before in this Chapter please refer to paragraph 6 3 11 4 Scope amp Level Core Service View the details of a Service Contract 6 3 13 2 1245 UC Search and Select Service Contracts This Use Case is listed before in this Chapter please refer to paragraph 6 3 5 3 Scope amp Level Core Service Find Service Contracts that satisfy search criteria 6 3 13 3 1490 UC Suspend Resume Service Contract by Service Requester Goal in context A Service Requester suspends or resumes a Service Contract i e the Service Contract itself is not changed or terminated but indicated as not to use during a service call Preconditions A Service Contract between the Service Provider and the Service Requester ex ists and is selected Successful outcome A Service Contract is s
37. Define and Register Service Contract 1443 FTR Enable Disable Service 1469 FTR Suspend Resume Service Contract GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 209 of 210 Green DN eMotion Ea N 4 ID Use Case Realizes Feature 1482 UC View Service Contract Tem 935 FTR Provide Service Contract Framework plate 1315 FTR Register Service 1396 FTR Define and Register Service Contract 1484 UC View Service Details 1396 FTR Define and Register Service Contract 1447 FTR Contracting Service 924 FTR Search and Select Service 1471 UC View Service Transaction 927 FTR Service Transaction overview Details 1476 UC View Standard Interface De 1446 FTR Search and Select Standard Interfaces tails 1315 FTR Register Service 1445 FTR Define new Standard Interface GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 210 of 210
38. EV Identification Authentication and Authorization eese eene nnn 73 4 3 8 2 1518 UC during charging eiiis ssiiisseeee eese eennnnnn nsns Ene eei essa taa anA a sais asas sess saa sos a En AEREA 73 4 3 8 8 1511 UC End a roaming charging process with Clearinghouse eese eene 73 4 3 8 4 1512 UC Start a roaming charging process with Clearinghouse eeessseeeeeeeene eene 73 4 3 4 1 1502 UC EV Identification Authentication and Authorization eese 74 43 42 1518 UC D ring chatgihg ii treten eee ra ee eh eere eee eun a EERE EE EE FH AERE REPRE RAE Ede Eod d 74 4 3 5 1 1518 UC During Chari krisiren ennnen E REALE EAEI EAE IET ao FE HR ERR UR ERRARE EUER d 75 4 3 5 2 1512 UC Start a roaming charging process with Clearinghouse esses eene 75 4 3 6 1 1512 UC Start a roaming charging process with Clearinghouse eeeesseeeeeenen enne 76 4 3 6 2 1497 UC Create EVSP EVSE Contract within Clearing HOUSe cesses 76 4 3 6 5 1514 UC Create Customer Contract by Service Provider in Clearing House eese 77 4 3 71 1511 UC End a roaming charging process with Clearinghouse sess sese 77 4 3 8 1 1500 UC Change EVSP EVSE Contract within Clearing House esee 78 4 3 8 2 1512 UC Start a roaming charging process with Clearinghouse esses ener 78 4 3 8 3 1513 UC Delete EVSP EV
39. EV has an onboard unit that uses an online connection GPRS UMTS to permanently send GPS positions to the Routing Location Service Provider The current position of the EV is stored to a database and ready to read Successful out The current position of the EV is displayed in form of coordinate values or in a come geographical map This information is made available to through the Marketplace Failure outcome Condition leading to outcome No current EV e Display of a warning message The onboard unit of the position The EV is marked as wrongly EV had no network con located at the last known po nection sition The GPS device of the vehicle had no contact to satellites GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 46 of 210 Green Dy eMotion BG V Invalid position Display of a warning message The GPS receiver calcu The EV is located at the last lated an abnormal impos valid position sible new position of the EV No service The current position is stored Temporary loss of mobile available to the onboard unit internal network connection storage and will be sent again The central service is when the connection to the temporary offline central service reestablishes mensen 143 ACT EV Electric Vehicle on board equipment 137 ACT Service Provider Secondary actors 1579 ACT Third Party Service Provider Routing Location Service Provider 128 ACT EVSP Electric Vehicle Se
40. EVSP or municipalities to adapt parking tariffs and to plan the spatial distribution of further parking spaces Failure outcomes Failure Outcome Condition leading to outcome No monitoring No parking space moni Parking Space Monitoring ser toring data will be pro vice of EVSP is not working vided properly rd Primary actor 128 ACT EVSP Electric Vehicle Service Provider requests current usage data 135 ACT Public sector requests aggregated history data 1406 ACT EVSE Operator Backend 131 ACT EVSE Electric Vehicle Supply Equipment e EVSP requests data about current usage of CPs within a selected Charge point EVSE e The Parking Space Monitoring service returns detailed records Alternatives Public sector requests history data about EVSE usage for selected EVSE and time frame The Parking Space Monitoring service returns aggregated records of the se lected time frame Variations Related information Issues 3 3 6 3 1557 UC Parking Space Management Value added service Parking space management An EV driver needs a parking space only Therefore the EV driver shall be able to use a CP as parking lot without charging the EV This use case extends the use case UC Charging Location Management 1529 Preconditions The EVSE Op backend is connected to the market place The EV driver needs to have a roaming contract with a EVSP The EVSE Op needs to have a contract with the EVSP The EVSE Op is able to det
41. Forwarding tion 4 3 3 986 FTR Roaming in different countries using Clearinghouse This feature will allow two different EVSPs which are located in different countries to provide their cus tomers with a roaming opportunity A customer of EVSP A and country X will be allowed to charge on in frastructure of EVSP B in country Y The Clearing House will facilitate the platform for that GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 72 of 210 Green N eMotion En AL V At the moment we see that roaming in different countries is more complex than roaming in the same country because of differences in legal preconditions tax systems and energy market behavior between countries 4 3 3 1 1502 UC EV Identification Authentication and Authorization This Use Case is listed before in this Chapter please refer to paragraph 2 4 3 1 Scope amp Level Basic end user services This use case covers identification of contract belonging to a user own customer or roamer at a charge spot or battery switch station and his authentication and au thorization to execute the process of charging or battery switching Use case describes the interaction between EV EV driver EVSP EVSE operator and optionally the Clearinghouse when roaming 4 3 3 2 1518 UC during charging This Use Case is listed before in this Chapter please refer to paragraph2 5 3 1 Scope amp Level End user services This use case covers the enhanced connect cha
42. How much time etc and a session report why did it end Authorization Depending on the EVSE design many authorization methods are thinkable in the future However all authorization methods could be categorized by means of authorization location and authentication Authorization covers all methods for services rendered to the client It includes the payment for electricity supplied to the vehicle and the authorization to receive a requested value added service Payment for electricity concerns relatively small amounts other services e g car rental may concern larger amounts and may require supplementary security GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 30 of 210 Green eMotion BG With authorization the vehicle user shall be identified in any way to start the charging process Outside the EV i e a phone call or an External Identification Means may be used at the paying unit EVSE for authentication Inside the vehicle a unique authentication code is transmitted between EVCC and SECC to identify the vehicle user With this clustering of the authorization methods they can be classified into four types e authorization with authentication e authorization without authentication e authorization inside the EV e authorization outside the EV These authorization options are an indicator of possible implementations in the field In some cases charging service may be permitted without an authorization pr
43. Provider or the Marketplace Operator fills a form to create a notification to the Service Requester of his own Service The Service Requester of a Service is notified Alternatives Related informa This use case represents a simple notification There will be no information for the tion Service Provider if the Service Requester has received the notification Access Role Based Authorization required Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market 6 3 8 1622 FTR Manage Requests for new Services 137 ACT Service Provider The marketplace provides the capability to create Requests for a new Service A potential Service Requester creates a Request for a new Service which is basically a simple textual description of the service Potential Service Providers can view the Requests and are able to notify the Service Requester if they are willing to fulfill the Request i e to implement the Service and offer it on the marketplace 6 3 8 1 1625 UC Create Request for a new Service Scope amp Level Goal in context If there is no suitable Service the Service Requester is able to create a Request for a new Service Successful out A new Request for a new Service is created come Condition leading to outcome Not all required attributes of the Re quest for a new Service are filled Failure outcome
44. S3 B2B Contract Management 1296 FTR Third party information 1797 GRP Driving Related Services 563 FTR User identification 1180 BS C1b Semi public charging 1181 BS C1c Public charging 1794 GRP Identification and Authentication of EV user 1179 BS C1a Charging at home 1356 BS O4 Basic charging 1160 BS O1 Enhanced charging 1202 FTR V2G energy supply signal 34 BS E2 Virtual Power plant 31 BS E1c Distributed Congestion Mgmt by Ag gregators 1184 BS C4a Charging V2G GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 203 of 210 Green N eMotion EA A ID Feature Satisfies 560 FTR V2H supply signal 31 BS E1c Distributed Congestion Mgmt by Ag gregators 34 BS E2 Virtual Power plant 1185 BS C4b Charging V2H 944 FTR Vehicle tracking 1797 GRP Driving Related Services 1162 BS O3 Driver enhanced services 1159 BS O2c Safety 940 FTR Version Service 1176 BS S4 Service provision ing registration life cycle mgmt GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 204 of 210 Green Dy eMotion V G Use Cases Where Used in Features by Service Provider in Clearing House ID Use Case Realizes Feature 1502 UC EV Identification Authenti 986 FTR Roaming in different countries cation and Authorization 985 FTR Roaming in same country 1812 FTR EVSE Service Monitoring
45. Send Current Position esses esent nennen tentent s nnn en nenas 183 Figure 26 Send Notification M2V ssssssssssssssssesseseeeee eene sn tentent str enne 184 Figure 27 Send Notification V2M sssssssssssssseseseseeeee enne nent enses n nennt innen nnns nnne n nenas 185 Figure 28 Update Charging Details sssssssssesssseseseeenenenneeee nennen nennen enne nnn enne 186 GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 6 of 210 Green N eMotion a 2 List of Tables Table 2 1 Charging Domain Actors sssssssssssseeseeeeen eene nnne nnne nnns nennen nnne EEEE 20 Table 2 2 Before Charging Features and their Use Cases sss 22 Table 2 3 Identification and Authorization Features and their Use Cases sssssesssss 29 Table 2 4 During Charging Features and their Use Cases sessssssseeeeeeeennrennnnns 34 Table 2 5 After Charging Features and their Use Cases sse 39 Table 3 6 Driving and Cross Domain Services ACtOrs mmmmmrsrvrnrrsnnvnrrrrnrvnrrrrnrnrrrrnnvrrrrrnnnnrrrrnnrnrsrrrnnn 42 Table 3 7 Driving services Features and their Use Cases sssssssssseeeeeeeennennnens 42 Table 3 8Cross Domain Services Features and their Use Cases ssssssssseseeenes 56 Table 4 9 Roaming Domain Actors eene enne en nennen nnns nennen sre nnnns 69
46. Specification Sketch Is referenced in the Business scenarios Storyboard mu illustrated by and Use Case specifications Figure 2 Requirements gathering Artifacts and Relations 1 3 Methodology Usability engineering method To speed up validate and enhance the quality of the top down Structured Requirements Management approach the WP3 team selected the Usability Engineering Method This also helped to improve mutual understanding amongst the great variety of Stakeholders coming from very different cultural and indus trial backgrounds Four workshops were conducted following the Usage Centered Design process as developed by Con stantine and Lockwood 1999 To ensure that all implicit and explicit knowledge was available all stake holders took part in these workshops and the knowledge captured in the RRC tool was accessible during the workshops Participation also covered all development roles including domain experts business de velopers requirements engineers software developers architects and usability experts Led by the Usability Engineers the workshops delivered a system model of the future software as well as high level User Interface design sketches These results were integrated into the requirement specifica tion in the RCC tool GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 15 of 210 Green N EI eMotion A WS bur The Usability Engineering Methodology The usability activi
47. Standard Interface Scope amp Level Goal in context A Service Interface is published as Standard Interface at the marketplace The Service Interface is proposed reviewed and accepted as Standard Interface Successful outcome An entry in the Standard Interface Catalogue for the Standard Interface is created and the Business Partners are notified Condition leading to outcome Failure outcome Failure Outcome GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 144 of 210 Green DN eMotion EG AL V 1402 ACT Marketplace Technical Operator Secondary actors S Main scenario e The Marketplace Technical Operator creates an entry in the Standard In terface Catalogue for the Standard Interface Alternatives BE ee C TT Variations e The Business Partners are notified Access Role Based Authorization required Data Security Data Integrity must be guaranteed Data Confidentiality must be ensured Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility 6 3 18 3 1489 UC Upload Service Specification This Use Case is listed before in this Chapter please refer to paragraph 6 3 14 4 Scope amp Level Core Service During the service registration the Service Provider uploads the service specification i e Service Interface e g WSDL and Service Description of the offered Service
48. The Business Partner chooses the details view of a Request of a new Ser vice e The detail view is displayed Alternatives Related informa tion Access Role Based Authorization required Data Privacy Sensitive Data is only stored when needed and authorized Data Export Policy required Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 121 of 210 Green N eMotion EA AL V 6 3 8 3 1629 UC Create Response on Requests for new Services Scope amp Level Goal in context Potential Service Providers are able to create a response to a Request for new Services if they are willing to implement and offer a Service that fulfillsthe request A Request for new Services is selected Successful out A new response to a Request for a new Service is created and the Service Re come quester is notified Failure outcome Failure Outcome Condition leading to outcome EN 9 Primaryactor 137 ACTSewiceProvider Secondary actors 138 ACTServiceRequester Main scenario e The Service Provider fills a form for the response of a Request for a new Service e The new created response on a Request for a new Service is stored e The Service Requester is notified Alternatives Related informa tion Role Based Authorization r
49. There are no service contracts tracts are found sage that meet the search criteria A EE UO ODD AM en UO 1355 ACT Business Partner Secondary actors 1367 ACT Marketplace Business Operator Main scenario e The Business Partner fills the search criteria or load search criteria saved before e The marketplace returns a list of Service Contracts that meet the search criteria e The Business Partner stores optionally the entered search criteria for later use Alternatives HE ERE SCREEN UNDE Variations The Marketplace Business Operator is able to receive a list of all Service Con tracts Relatedinformaion 00 Access Role Based Authorization required Data Privacy Sensitive Data is only stored when needed and authorized Data Export Policy required Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market 6 3 6 1459 FTR Aggregate Service Call Results A Service Requester can have Service Contracts with multiple Service Providers for the same functionality The GeM Marketplace has to enable service calls to all contracted Service Providers and has to aggre gate the results of the different Service Providers As a precondition the Service Requester and all of the Service Providers have to implement an identical Standard Interface 6 3 6 1 1492 UC Aggregate Service Call Results S
50. Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market 6 3 14 8 1476 UC View Standard Interface Details Goal in context View Standard Interfaces details Preconditions e The searching actor is a representative of a Business Partner of the market place or the Marketplace Technical Operator e A Standard Interface is chosen Successful out The Business Partner views the following details of the chosen Standard Interface e Interface specification of Standard Interface e Interface description of the Standard Interface Failure outcome Failure Outcome Condition leading to outcome 1355 ACT Business Partner Secondary actors 1402 ACT Marketplace Technical Operator The Business Partner chooses the details view of a Standard Interface The detail view is displayed Related informa tion d Role Based Authorization required Data Security Data Integrity must be guaranteed Data Confidentiality must be ensured Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 138 of 210 Green N eMotion En AL V 6 3 14 9 1475 UC Search and Select Standard Interface Scope amp Level Goal in context Find Standard Interfaces that satisfy search criteria Precondition
51. Vehicle Service Provider as aggregator 128 ACT EVSP Electric Vehicle Service Provider as contributor 129 ACT DSO Distribution System Operator It is within the DSO responsibility to allow V2G to happen and release a signal to the EVSP by stating that under a specified load area the cars connected to the EVSEs are allowed to feed back into the grid a pre settled amount of energy A contract must be established between EVSP and DSO The EVSP may not act as aggregator but be in contact with it together with other EVSPs In this case the aggregator should fulfill predefined market rules i e penal ties for not allowing EVSPs offer to take place if matched with DSO needs This use case shows the chance of using energy stored in the EVs as a prosumer platform for energy to be eventually fed into the LV grid It is hereby pictured how the information and signaling regarding the V2G supply should be managed Regulation and local legislation 5 3 2 2 1602 UC flexible load for congestion management Value added service Congestion may happen within a load area under critical timeslots and massive EV penetration may jeopardize energy disposal for Energy Vendors generic customers This Use Case enables the use of batteries flexibility for congestion management by DSO This topic is within the duties of the DSO that manages the LV and MV grid The DSO therefore is in charge of avoiding this hazardous condition and eventually reacts whe
52. WP 3 Deliverable 3 3 Page 127 of 210 Green N eMotion En AL V The The chengec Senice Conrac ten ie store Service Contract Offering is stored Alternatives Variations Variations __ _ informa tion Access Role Based Authorization required Data Security Data Integrity must be guaranteed Data Confidentiality must be ensured Data Privacy Sensitive Data is only stored when needed and authorized Data Export Policy required Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market 6 3 11 4 1479 UC View Service Contract Details Scope amp Level Goal in context View the details of a Service Contract Preconditions e The actor is a representative of the Business Partner of the marketplace or the Marketplace Business Operator e One of the Business Partner s own Service Contracts is chosen Successful out The Business Partner views the details and history of one of its own Service Con come tracts e g e Terms and conditions e Pricing Contract period Failure outcome Failue Outcome Condition leading to outcome ENS DE E ACT Business Partner The detail view is disp TG Bl MENE piae The ak ede ikt TT Business Operator is able to view the details of all Service Con tracts Related informa tion Access Role Based Authorization required Data Security D
53. a Charge point EVSE based on personal preferences and current third party information EV driver uses his end user customer application to connect to the city pilot ser vice of his EVSP EV driver will be provided with a list of available Charge points EVSE sorted by his preferences Alternatives ME Related informa tion Issues oT O O GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 28 of 210 Green N eMotion Ea FA VL 2 4 Identification and authorization of EV user 2 4 1 Identification and authorization Overview The following table lists the Features that are relevant in the Identification and authorization of EV user phase ref 2 1 Features Use Cases 563 FTR User identification 1502 UC EV Identification Authentication and Authorization 979 FTR Authentication of user Table 2 3 Identification and Authorization Features and their Use Cases 2 4 2 Identification and authorization Content This feature group comprises the following content 563 FTR User identification Depending on the EVSE infrastructure and the capabilities of the EV the methods of identifying a user differs The figure below classifies possible scenarios data type example 1 ever Contract ID 1 3 E m en EE B e g RFID 1 al econda e g Credit B 1 2 lia Card 1 1 Contract ID 2 e g Power Outlet ID etc 3 e g
54. be acknowledged The driver can only confirm the notification when he stops or interrupts the trip The onboard unit can confirm special types of notification automatically The marketplace acknowledges automatically For more information please refer to Figure 26 Send Notification M2V in the Ap pendix Alternatives Related informa The attention of the driver is never affected The driver must not acknowledge while tion driving For illustration of this use case please refer to Figure 26 Send Notification M2V and Figure 27 Send Notification V2M in Appendix C 3 3 4 6 1576 UC Set Geofence Scope amp Level Basic end user service Set a geofence for a specific EV Goal in context Set the geofence for an EV Preconditions The onboard unit of the EV is connected to a mobile network The limited number of active geofences for an EV has not exceeded The specified EV is always con nected to a mobile network see variations come base of the location service provider EMT 0o c come vehicle unknown Display of a warning The requested vehicle is not messages registered No geofence information is stored Number of Display of a warning The configurable maximum geofences ex message number of geofences is ex ceeded The last geofence is not ceeded stored aS Primary actor 137 ACT Service Provider 1579 ACT Third Party Service Provider Location Service Provider Secondary actors 133 ACT Vehicle Driver 1594 ACT Fleet
55. conditions of the Service Reg istration Contract e The valid Service Registration Contract is stored by the marketplace Alternatives Pee gd Variations Related informa tion Access Role Based Authorization required Data Security Data Integrity must be guaranteed Data Confidentiality must be ensured Data Privacy Sensitive Data is only stored when needed and authorized Data Export Policy required Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market 6 3 14 2 1482 UC View Service Contract Template This Use Case is listed before in this Chapter please refer to paragraph 6 3 10 1 Scope amp Level Core Service The template of the Service Contract Framework is displayed to the Business Partner 6 3 14 3 1494 UC Publish Service Successful out The use case exists in two different contexts come e Publish a new Service e Publish a new version of the Service i e existing Service Contracts have to be changed depending on the contract conditions Failure outcome Failure Condition leading to outcome Unchanged e Notification of the Service Pro Not all Service Contracts Contracts vider are changed as neces exists e Cancellation of the publishing process ee S 137 ACT Service Provider Secondary actors 1402 ACT Marketplace Technical Operator Main scenario e The Service Provider requests th
56. corresponding IT backend of the OEM The Provision of e mobility services is not covered by the role of the ACT OEM in this case the OEM acts in addition as an E Mobility Service Provider 135 ACT Public sector EU commission National govern Public sector needs information about the added value of e mobility to the society ment local government municipali environmental footprint and the need for new infrastructure inputs for planning ties 1541 ACT SECC Supply implements the communication to May be able to interact with secondary actors Equipment Com one or multiple EVSEs munication Con troller 137 ACT Service Pro Business Partner that offers and sells Sells EV Services on the marketplace vider EV Services on the marketplace Are there any criteria of Business Partner to become a Service Provider Who performs an approval of any criteria Child of the Business Partner 138 ACT Service Re Business Partner that consumes EV Uses the Marketplace to buy and re sell EV services to their customers quester Services on the Marketplace Child of the Business Partner GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 156 of 210 Green eMotion V Ed ID Actor Description Full description 1579 ACT Third Party An actor which provides access to The Third Party Service Provider is not connected to the market place directly but Service Provider third party data with one
57. given EV driver Goal in context The charging service of a requested vehicle is reported with a CDR and made available to the EVSP through the Marketplace or transferred directly from the EVSE operator Preconditions The EVSE operator can read the consumption of the EV at a particular EVSE The EVSE operator can communicate energy consumption to the EVSP either di rectly or through a clearinghouse The service consumption of a vehicle for a given period of time is reported to the come EVSP oe sell come The requested e Display of an error message The requested EV ID has vehicle is un e Cancellation of the report not been registered known generation No charging lo e Display of a warning mes The EV has not synchro cation available sage nized any charging data e Limited report generation with a compatible EVSE The location of the EVSE is not registered The vehicle has e Display of an error message The EV has not synchro not transferred e Cancellation of the report nized any battery and any data for the generation charging data for the re requested period quested period of time of time Primary actor Primary actor 132 ACT EVSE Operator Secondary actors 128 ACT EVSP Electric Vehicle Service Provider 1579 ACT Third Party Service Provider 133 ACT Vehicle Driver Main scenario An EVSE operator provides several reports to show the current and past consump tion of charging service of an EV The data that is col
58. identification and authorization use case In some implementations this use case would belong to the Dur ing Charging use case e g Better Place Additional services labeled as driving services include basic end user functionalities such as vehicle tracking use of EV parking spaces without charging monitoring and CC2 analysis In addition extended services such as fleet management and intermodality planning are described in this chapter All these services are described as functional requirements For lack of implementation experience with these services the WP3 team decided to postpone the definition of non functional requirements until the specification phase The connect charge disconnect cycle is illustrated in the following picture Source Better Place 1 2 3 4 5 6 User parks EV near User connects EVto Userisgoodtogo Charging can may or may not User disconnects EV EV is parked an available charge charge socket EV lights blink due to occur from charge socket disconnected from socket immediate charge user might connect the charge socket cable back right again Parking cycle k Charge cycle Parking cycle Connection sequence Charge Dis connection sequence Figure 5 The Connect Charge Disconnect cycle GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 19 of 210 Green Dy eMotion V 2 2 Actors Th
59. metered in the EVSE energy gateway The EVSEs are in communication with an EVSE Op back end that aggre gates data from each EVSEs The EVSP aggregates data from the EVs under its contractual control and is able to perform communication either directly with the DSO or the market place where the dedicated service is running Je AIIthe other preconditions of UC 1601 and 1602 sful out DSO reduces peaks on the MV level by using aggregated V2G on LV substations and rerouting power through uncongested areas 4 outcome Absence of V2G condition in the available contract allow V2G No V2G power There would be no chance to feed EV and EVSE cannot available back energy into the grid Lack of communicate the re communication or lack of compli verse flow of energy ancy to I5015118 where EV EVSE condition communication is available ecc y ac 132 ACT EVSE Operator 129 ACT DSO Distribution System Operator The EVSP is acting as aggregator and delivers energy from the EVs of its cus tomers to the grid as a support for congestion management It is the DSO that decides whether or not to deploy such a congestion management policy after having evaluated the energy availability aggregated per load area from the various EVSPs in order to ensure that switching an amount of cars into V2G can surely trigger peak shaving The EVSE without communication capabilities towards an EVSE Op back end could not interact with the DSO peak predefinitions In th
60. peaks are identified per load area the DSO can update requests for curtailment on the market place setting the constraints for energy provisioning in the load area in which the EVSEs are encom passed It is up to the EVSE Operator to decide whether or not distribute this constraint within all the EVSEs installed in that area or eventually cut off just a few of them A fundamental condition for this feature to take place is that the EVSP states in its contracts with the cus tomers that the average time of recharge is sensitive to the network safety issues peaks management from the DSO and eventually to charging points priority issues coming from the deployment strategy of the EVSE Operator GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 99 of 210 Green NI eMotion BG 5 3 10 1 1597 UC Peak shaving This Use Case i is listed before in this Chapter please refer to paragraph 5 3 7 1 Je amp Value added service If network congestion management and V2G energy supply signal hypothesis are satisfied an advanced solution for dealing with congestion issues would be using the V2G availability published from the EVSPs in order to simultaneously impact positively with a dynamic energy disposal on the grid by sharpening the load peaks in an adaptive way 5 3 10 2 1596 UC Peak load threshold on a substation Value added service Within the MV LV energy distribution management domain the peak energy dis posal per
61. permanently Scope amp Level Goal in context A service may be permanently enabled or disabled GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 140 of 210 Green N eMotion EE AL V Preconditions e A Service is selected e The Service has no active Service Contracts i e all Service Contracts have to be terminated e The Service is stopped The Service is disabled or enabled come BEN Fosse to outcome Active Contracts e Notification of the Service Pro Not all Service Con exists vider tracts are termi e Cancellation of the disabling nated process 795289 3j ER AE Primaryactor p EE E pue jeu e Primary actor 137 ACT Service Provider Secondary actors 1402 ACT Marketplace Technical Operator Main scenario e The Service Provider requests an enabling or disabling of the Service e The Marketplace Technical Operator enables or disables the Service in the Service Catalogue e The Service Provider is notified Alternatives J 0 Variations J Related informa tion Access Role Based Authorization required Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market 6 3 15 6 1479 UC View Service Contract Details This Use Case is listed before in this Chapter please refer to paragraph 6 3 11 4 Scope amp Level Core Service View the details of a Service Contract
62. position of one or multiple cars y O O Related informa tion Issues y y o 3 4 3 5 1524 UC Fleet manager monitors energy consumption of pool cars Scope amp Level Value Added Service Monitoring of energy consumption for single cars or the whole fleet Goal in context Monitoring of energy consumption Preconditions Pool cars available system is available Fleet Manager is in place Cars communi cate at least their Status of charge and the vehicle identification number GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 61 of 210 Green NN eMotion Ea L Successful out Energy consumption can be seen either for single cars or for the fleet as a whole come Fleet Mgr knows where the cars were charged and is able to allocate costs to the respective cost center Failure outcomes Condition leading to out come Energy consump Energy consumption cannot be e Connection issues tion is not avail used for calculations or addi e Backend issues able tional services e Infrastructure is sues e Energy provider is sues POSEN SEE a Se Primary actor 1594 ACT Fleetmanager Secondary actors 132 ACT EVSE Operator 128 ACT EVSP Electric Vehicle Service Provider as Fleet Provider Main scenario fleet manager opens the car information page of the fleet management system fleet manager looks at the history and current consumption of a car Alternatives Car has energy consumption locally available and total calcul
63. re Y 5 D cecccccaccce Reserve Charging i s i Group and report 1 s check availability amp daige point Point amp Generate o Electricity Rate DEE poler options eliminate Conformation ID I duplicates a A i DDD 2 E Schedule Parking Fee Peak Load Iz GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 180 of 210 G eMotion Eg JL V C Use Case Illustrations Assistance Center EV Driver Initiate Roadside Assistance Call Send Notification Receive Notification Store and 3 Send display Acknowledge Assistance Notification Request Receive Acknowledgement Figure 23 Call for Roadside Assistance GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 181 of 210 eMotion Green jon ET 2 Permanently send current requests for location current position notifications of EV N Store to Market database Check if current position of EV is available no yes Show warning Show current message position Figure 24 Get Current Position GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 182 of 210 Green NN ET 2 eMotion FE Evaluate current i position Receive location notification Receive location e Figure 25 Send Current Position GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 183 of 210 eMotion Green jon ET 2 Service Requester Marketplace
64. service to be run in the marketplace Therefore it is the EVSE Operator who acts as Service Provider and takes care of the aggregation and migration of data This service can be requested from other actors in the marketplace for different pur poses i e for statistical analysis on EVs roll out EVSE performance analysis EVSE Operator marketing and certification EVSE History must contain time stamp EVSP ID implicit for single EVSP EVSE s geographical load area energy consumed quality of service i e out of service outage charging status failed authorization attempts V2G historical use GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 105 of 210 eMotion Green on E 2 6 Core marketplace services use case model 6 1 Overview The core marketplace services domain represents the essential services to run the marketplace itself It covers mainly the functionality to offer services by service providers and the use of those services by ser vice requester referring typically to the terms Buying and Selling These terms are processes which can be divided in sub processes as shown in the following figure Selling eroe m Y Y Service Provider iService Contract Offering Service Interface mum Ft xs KES Um i Meere rrr rrr of Accept Offering j i ODs T v Service Requester Service Contract Figure 19 Marketplace Buying and Selling
65. the Service Requester has more than one valid Service Contracts not sus pended with different Service Providers for the same request based on the Service Interface Specification the results will be aggregated Described in UC Aggregate Service Calls c o OMNE tion Access Certificate Mechanism or equivalent is required Data Security Data Integrity must be guaranteed Data Confidentiality must be ensured Data Privacy Sensitive Data is only stored when needed and authorized Data Export Policy required Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market 6 3 5 3 1245 UC Search and Select Service Contracts Scope amp Level Goal in context Find Service Contracts that satisfy search criteria Preconditions The searching actor is a representative of the Business Partner of the market place or the Marketplace Business Operator Successful out The Business Partner receives an ordered list of his own Service that meets his come search criteria and is able to select one or more Service from the list for further activities GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 117 of 210 Green N eMotion En AL V Search criteria may include e Valid and terminated Service Contracts e Active and suspended Service Contracts e Service Contracts for prolongation O eS come pee No Service Con
66. tracking use of EV parking spaces without charging monitoring and CO2 analysis reporting In addition extended services such as fleet management and intermodality planning are described in this chapter Roaming services described in Chapter 4 and led by SAP 7 business services The GeM Marketplace facilitates also information exchange that enables geographic roaming between countries and roaming either between EVSPs and EVSPs or EVSPs and EVSE Ops Roaming is based on contractual clearing services performed by the Clearinghouse which is a third party application ac cessible through the GeM Marketplace Contractual clearing enables intra country and inter county roam ing through the validation of contracts between different EVSE Operators and EVSPs as well as their re spective customers This functionality is of key importance to the Green eMotion project because it en ables charging at different EVSEs with the use of a single contract provided by one EVSP During its first release the Clearinghouse application will only provide roaming and authorization services Future re leases of the Clearinghouse may also provide Financial Clearing which would improve financial and bill ing operations for e mobility Energy services described in Chapter 5 and lead by Enel 13 business services GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 9 of 210 Green N eMotion EG 2 QA WEM The ability to centrally modulate or to
67. using aggregated V2G on LV substations and re routing power through uncongested areas 5 3 7 1 1597 UC Peak shaving NOTE this is a stand alone use case and needs 1601 and 1602 use cases as pre conditions Value added service GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 96 of 210 eMotion Green on ER 7 If network congestion management and V2G energy supply signal hypothesis are satisfied an advanced solution for dealing with congestion issues would be using the V2G availability published from the EVSPs in order to simultaneously impact positively with a dynamic energy disposal on the grid by sharpening the load peaks in an adaptive way This use case enables peak shaving by aggregated EVs V2G deployed for grid congestion management The goal of peak shaving using V2G capability is to guarantee the energy provisioning to all the loads connected to the grid without deploying cut off load management strategies under a congestion situation thus letting the DSO to re route the surplus of power gathered from EVSPs The EVSE Op is connected to the marketplace through its back end The EVSP is connected to the marketplace through its back end The DSO is connected to the marketplace through its front end towards the grid An adequate communication capability should be endorsed in the EV in order to receive modulation orders from the DSO through the EVSE energy gate Way The energy going in the reverse flow has to be
68. 015118 currently under development is compliant with this hypothesis The EVSE Operator is connected to the marketplace through its back end The EVSP is connected to the marketplace through its back end EV manufacturers allow for this information to be delivered to the other stake holders EVSP E pe qmm come HH pf P EV and EVSE can There would be no Lack of communication or lack not communicate chance to deliver such of compliancy to I5015118 the status of re information to the stake where EV EVSE communica GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 102 0f 210 Green Dy eeo BG L Pchage holders CCC tion is available END 128 ACT EVSP Electric Vehicle Service Provider Secondary actors 129 ACT DSO Distribution system operator 132 EVSE Operator 138 ACT Service Requester TSO OEM or Energy Supplier Main scenario The EVs communicate the current EV charge status to the EVSE back end The status of charge is propagated from the EVSE to the EVSE Operator back end EVSP back end system The EVSP collects the current EV charge data from all the connected EVSEs The data are stored in a local DB and after a specific ag gregation procedure they are available to the marketplace through the EVSP front end Alternatives Other actors in the market may act as Service Requestors and access the Current EV charge information made available from a specific EVSP and match this with their ne
69. 1 UC End a roaming charging process with Clearinghouse 986 FTR Roaming in different 1502 UC EV Identification Authentication and Authorization countries using Clearing 1518 UC During charging House 1511 UC End a roaming charging process with Clearinghouse 1512 UC Start a roaming charging process with Clearinghouse 1804 FTR Roaming based on 1502 UC EV Identification Authentication and Authorization bilateral agreements 1518 UC During charging 981 FTR Authentication 1518 UC During charging 1512 UC Start a roaming charging process with Clearinghouse 982 FTR CLEARING Valida 1512 UC Start a roaming charging process tion of contract 1497 UC Create EVSP EVSE Contract within Clearing House 1514 UC Create Customer Contract by Service Provider in Clearing House 984 FTR CLEARING Forward 1511 UC End a roaming charging process with Clearinghouse ing CDR 1291 FTR CLEARING Manag 1500 UC Change EVSP EVSE Contract within Clearing House ing EVSP data 1512 UC Start a roaming charging process with Clearinghouse 1513 UC Delete EVSP EVSE Contract from Clearing House 1497 UC Create EVSP EVSE Contract within Clearing House 983 FTR CLEARING Manag 1512 UC Start a roaming charging process with Clearinghouse ing customer data 1516 UC Delete Customer Contract by Service Provider from Clearing House 1514 UC Create Customer Contract by Service Provider in Clearing House 1515 UC Change Customer Contract by Service Provider in Clearing House 15
70. 10 Green DN eMotion En AL V communication link Preconditions e A service is requested either as a pre setting or a specific request e The service requested can be provided to the user either directly from a service provider or through another service provider on the marketplace can access the user e he user can consume the service through a compatible communication link Successful out The user is enabled to enabled to access and consume consumption monitoring come Services Failure outcomes Failure Condition leading to out come Search failure User is not able to identify a Technical errors requested service Typing errors Connectivity Other Outdated or false The user is offered services Service provider fails to information about based on incorrect or inac update or track real time consumption of curate information information services e User fails at making software updates e Other Seal eG Primary actor 133 ACT Vehicle Driver 1406 ACT EVSE Operator Backend 1407 ACT EVSP backend Secondary actors 140 ACT Clearinghouse 132 ACT EVSE Operator 128 ACT EVSP Electric Vehicle Service Provider User has to keep track of consumption history in alternative ways Variations Related informa In certain cases CDR is sent from EVSE Operator to EVSP via the Clearinghouse tion GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 40 of 210 Green Dy eMotion LY Ed 3 Driving and cr
71. 160 BS O1 Enhanced charging 1795 GRP Services During Charging 1702 FTR Charging monitoring 1795 GRP Services During Charging 1180 BS C1b Semi public charging 1179 BS C1a Charging at home 1181 BS C1c Public charging 951 FTR Charging report 1180 BS C1b Semi public charging 1181 BS C1c Public charging 984 FTRCLEARING Forwarding CDR 1161 BS R1 Contractual clearing 983 FTR CLEARING Managing customer data 1161 BS R1 Contractual clearing 1291 FTR CLEARING Managing EVSP data 1161 BS R1 Contractual clearing 982 FTRCLEARING Validation of contract 1161 BS R1 Contractual clearing 1320 FTR CO2 intensity 1798 GRP Cross Domain Services 1358 FTR Connect Charge Disconnect 1180 BS C1b Semi public charging 1181 BS C1c Public charging 970 FTR Consumption monitoring 1796 GRP Services After Charging 1180 BS C1b Semi public charging 1179 BS C1a Charging at home 1181 BS C1c Public charging 1447 FTR Contracting Service 1173 BS S1 Marketplace Buying Selling Rout ing 1366 FTR Create Business Partner Account 1178 BS S6 B2B Partner Management 1685 FTR Create Notification to Service Re 1173 BS S1 Marketplace Buying Selling Rout quester ing 966 FTR Current EV charge 1356 BS O4 Basic charging 1160 BS O1 Enhanced charging 1396 FTR Define and Register Service Contract 1175 BS S3 B2B Contract Management 1445 FTR Define new Standard Interface 1177 BS S5 Linking of Systems Standardization of Interfaces Messages 14
72. 17 UC Change Customer Contract by Customer himself within Clearing House Table 4 10 Roaming Domain Features and their Use Cases 4 3 2 985 FTR Roaming in same country using Clearing House The feature will allow for roaming between two EVSPs which are located in the same country A customer of EVSP A will be able to charge at an EVSP B s infrastructure The contractual clearing will be done via this feature GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 70 of 210 Green I eMotion BG L At the moment roaming in the same country is be less complex than roaming between different countries since applicable legal preconditions tax systems and energy market behavior will be the same inside a single country 4 3 2 1 1512 UC Start a roaming charging process with Clearinghouse Clearing Service Trigger to start a roaming charge after the transaction has been validated by the clearinghouse Start of a cleared roaming charging process Preconditions Involved EVSPs EVSE operators have valid roaming contracts the Clearing House has access to Driver has valid roaming contract with an EVSP Pending charging request that requires roaming ContractID is part of the charging request of the EVSE operator Successful out Charging Process successfully starts come Failure outcomes Failure 1 Outcome Condition leading to outcome Authorization mes Charging cannot Connectivity issues sages are not sent start
73. 1804 FTR Roaming based on Bi lateral Agreements 1702 FTR Charging monitoring 1809 FTR EVSE Service Access 563 FTR User identification 1704 NFR Tap RFID to access EVSE 979 FTR Authentication of user 1705 NFR Connect EV and EVSE with cable 1548 UC Access Car Information 1303 FTR Intermodality planning 1300 FTR Car information 1379 UC Activate Business Partner 1369 FTR Activate Inactivate a Business Partner Ac Account count 1519 UC After charging 970 FTR Consumption monitoring 1492 UC Aggregate Service Call Re 1459 FTR Aggregate Service Call Results sults 1598 UC Aggregated EV charge over 966 FTR Current EV charge view by the DSO 1522 UC Assign car to scenario 1301 FTR Fleet management 1510 UC Before charging 1812 FTR EVSE Service Monitoring 1318 FTR Reservation of Charge Spot 1561 UC Calculate CO2 Emission 970 FTR Consumption monitoring 1812 FTR EVSE Service Monitoring 1567 UC Call For Roadside Assistance 944 FTR Vehicle tracking 1241 UC Call of Service 926 FTR Call of Service 1376 UC Change Business Partner Ac 1368 FTR Change Business Partner Account count 1369 FTR Activate Inactivate a Business Partner Ac count 1378 UC Change Business Partner Ac 1368 FTR Change Business Partner Account count Details 1517 UC Change Customer Contract 983 FTR CLEARING Managing customer data by Customer himself within Clearing House 1515 UC Change Customer Contract 983 FTR CLEARING Managing customer data GA MOVE FP7
74. 2 CDR forwarding After some entity of the charging chain ends the roaming charging process the EVSE operator backend sends the corresponding CDR to either the EVSP in case of bilateral roaming or to the clearing house in case of centralized agreements In case of the latter the CDR is then validated and forwarded to the EVSP which is responsible for the customer who charged his car V End Charging Process End Charging Process End Charging Process Charge Point B EV Driver A Forward CDR End Charging Process EVSE Operator Backend B Marketplace Validate CDR Store CDR Forward CDR eon a CDR ing Hous Clearii EVSP Backend 4 z Fy T o o m amp Figure 16 Forward CDH Process flow GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 68 of 210 Green Dy eMotion A 4 2 Actors The following table lists the identified Actors in the Roaming domain ID Actor Description 140 ACT Clearinghouse authenticates and processes contractual and financial transactions 129 ACT DSO Distribution system operator Provides the power connection point to the charging spot 143 ACT EV Electric Vehicle Provides access to the vehicle data 1539 ACT EVCC Electric Vehicle Communica embedded system within the vehicle that im tion Controller plements the communication between the vehi cle and the SECC in order to support specific functions 131
75. 24 7 availability required Performance sub second response time for Marketplace Transactions Scalability capable to grow with electro mobility market 6 3 3 924 FTR Search and Select Service Any Business Partner of the GeM Marketplace can search and select services from the Service Cata logue by optional search parameters This Feature is applicable in different contexts Business Scenario s e Service Requester may search services for which they have an active or inactive Service Con tract e Service Requester may search those services which they may contract Service Providers may search all services enabled and disabled services they have offered 6 3 3 1 1239 UC Search and Select Services Scope amp Level Goal in context Find Services that satisfy search criteria Preconditions The searching actor is a representative of the Business Partner of the marketplace or a Marketplace Operator Successful out The Business Partner receives a list of Services that meet his search criteria and is come able to select one or more Services from the list for further activities Search crite ria may include the following e Offered Services by the Business Partner e Available Services for contracting e Contracted Services Failure outcome Condition leading to out come No Service is found Display of an error There are no services that message meet the search criteria 1355 ACT Business Partner Secondary actors 136 ACT Mark
76. 3 4 4 1320 FTR CO2 intensity of AriVing ccc ccccssccesssecceesseeccessseccesseeceessseceessseecesseeecessseeeessseeesesenseeeees 62 4 Roaming functional domain use case model eeeeeeeeeee esee eee ee eene eene n esee eene esee sees esa n nn 65 4 1 OVE 65 4 1 1 Author ZAtiA a dai E 66 4 1 2 CDR Sen rere E 68 4 2 Ln TD E E 69 4 3 Features nd Use CASES D 70 4 3 1 OVErVIEN E aE 70 4 3 2 985 FTR Roaming in same country using Clearing House ccccccccceesessssseeeeeeesssssseeeceesessesaeeeeeeees 70 4 3 3 986 FTR Roaming in different countries using Clearinghouse cccccccssssccessssccessseeccesseeeeessseeeesaees 72 4 3 4 1804 FTR Roaming based on Bilateral Agreements cccccccccceesssssseeceesessssseeeecesessesaseeseeesesssaseeees 73 4 3 5 OSL FIR A uthentiCablOh i ope eter ure terree e ye E Dee e IE E reas ua ere epa coe paese ERR Yea eure en eR Kn 75 4 3 6 982 FTR CLEARING Validation of contract eene eene nennen nennen enne 75 4 3 7 984 FTR CLEARING Forwarding CDR ccsscccccccsssssssceeececsessssseeecceseeseueeeeeeesseeeseeeeceeseesssaeeeseesesen an 77 4 3 8 1291 FTR CLEAR
77. 38 ACT Service Requester Secondaryactor S Main scenario e The Service Requester selects the Service Interface e g WSDL for download e The Service Requester starts the download Variations z Related informa tion Access Role Based Authorization required Data Security Data Integrity must be guaranteed Data Confidentiality must be ensured Data Privacy Sensitive Data is only stored when needed and authorized Data Export Policy required Availability 24 7 availability required Scalability capable to grow with electro mobility market 6 3 4 3 1239 UC Search and Select Services This Use Case is listed before in this Chapter please refer to paragraph 6 3 3 1 Scope amp Level Core Service Find Services that satisfy search criteria 6 3 4 4 1484 UC View Service Details This Use Case is listed before in this Chapter please refer to paragraph 6 3 3 2 Scope amp Level Core Service View the details of a selected Service 6 3 4 5 1478 UC Download Service Content Scope amp Level Goal in context The Service Requester downloads additional content of the offered Service e g manual A Service is selected Successful out The Service Requester downloads additional content of the Service come to outcome 138 ACT Service Requester Secondaryactor 00000 Main scenario e The Service Requester selects additional content of the Service for GA MOVE FP7 265499 Green eMo
78. 4 3 2 1520 UC Users can book pool cars online This Use Case is listed before in this Chapter please refer to paragraph 3 4 2 1 Scope amp Level Value Added Service 3 4 8 3 1521 UC Status for cars can be maintained by Fleet Manager Scope amp Level Value Added Service The fleet manager wants to maintain the status of a car Goal in context Preconditions Successful out come Status for cars can be maintained by Fleet Manager the Fleet Mgr can set status information for each car to track damages failures need for repair maintenance as well as work that has been done so far parts replaced maintenance and service work The System notifies the Fleet Mgr when service works are necessary Pool cars available system is available Fleet Manager is in place Cars communi cate at least their Status of charge and the vehicle identification number The status of a car is changed damage failure need for repair maintenance changes are noted in the system The fleet manager knows exactly in which state the cars are what has been done so far and what needs to be done anytime soon come Secondary actors Main scenario Status cannot No car history creation possible Connectivity issues Cars that are not ready for usage Backend issues are still considered for planning gt service errors 1594 ACT Fleetmanager 128 ACT EVSP Electric Vehicle Service Provider as Fleet Provider 132 ACT EVSE Operator fleet manager en
79. 4 7 availability required Performance sub second response time for Marketplace Transactions Scalability capable to grow with electro mobility market 6 3 4 1447 FTR Contracting Service Contracting a service is performed by the potential Service Requester This includes the following actions Search and select a service from the Service Catalogue View or download Service Interface specification Optionally download additional content Optionally test the service through a trial period Choose options from the Service Contract Offering Accept the Service Contract Offering As a result a valid Service Contract is created by the acceptance of the Service Contract Offering 6 3 4 4 1485 UC Create Service Contract Scope amp Level Goal in context A Service Contract is created by accepting a Service Contract Offering by the GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 113 of 210 Green N eMotion En AL V Service Requester A Service Contract Offering is available for a Service at the marketplace A new Service Contract is created come come Service Contract Display of an error mes Not all required sections from incomplete sage the Service Contract Offering are chosen Service Contract e Display a message Service Requester do not ac Offering rejected e Cancellation of the cept the Service Contract Of process fering eee Primaryactor Lo uua ec Primary actor 138 ACT Service Requester
80. 44 FTR Delete Service 1176 BS S4 Service provision ing registration life cycle mgmt 961 FTR DSO predefines peaks 1160 BS O1 Enhanced charging 30 BS E1b Centralized Congestion Mgmt TOU tariff 1443 FTR Enable Disable Service 1176 BS S4 Service provision ing registration life cycle mgmt 918 FTR Enhanced charging 1160 BS O1 Enhanced charging 969 FTR EVSE Charging capabilities 1356 BS O4 Basic charging 1301 FTR Fleet management 1798 GRP Cross Domain Services 967 FTRHistory of EVSE use 33 BS E1d Monitoring of EVSE 1278 FTR Identification of available EVSE 1356 BS O4 Basic charging 1303 FTR Intermodality planning 1798 GRP Cross Domain Services 1160 BS O1 Enhanced charging GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 201 of 210 Green Dy eMotion V Feature Satisfies 562 FTR Low priority charging 1182 BS R3a Differentiation of customer con tracts SLA check 1795 GRP Services During Charging 1180 BS C1b Semi public charging 1183 BS C3 Mono directional controlled charg ing 1179 BS C1a Charging at home 1181 BS C1c Public charging 1622 FTR Manage Requests for new Services 1173 BS S1 Marketplace Buying Selling Rout ing 1617 FTR Marketplace Authentication and Authorization 1174 BS S2 Service Detail Records for Account ing and Billing 1173 BS S1 Marketplace Buying Selling Rout ing 1177 BS S5 Linking of Systems Standardiz
81. 5 2 3 3 3 1528 UC Reservation Of EVSE idee cies eter ee eda eH ERI DER ERR AL REA E Ee Y o cosshcdandessosehesss 26 2 3 3 4 1574 UC Third party information cccccccscccccessccceesssccsessseceessesccessccessseecseseceecesseceeaasceeessscesesssesseeesssaees 27 2 4 3 1 1502 UC EV Identification Authentication and Authorization eese 31 2 5 3 1 1518 UC During charging eeoa a eaa a E aaa aE raa ABE ERA PARE Y RR EVA VER P SEE aa pip a ana PEERS add 36 2 5 3 2 1502 UC EV Identification Authentication and Authorization esses eene 38 2 6 3 1 1519 UC After charging ice evt eir Rete aee PEE VIE Ev Eee Eye pe WR PER Fe duces FR REE ERE Ye Pa Todas 39 3 Driving and cross domain use case model rnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnes 41 3 3 2 1 1558 UC Update Charging Details ccccccccccccssssssscccccseessssscsccccsseessssassceceesesssasscecceseessaeeseeeeseessaaeusassasees 43 3 3 2 2 1561 UC Calculate COZ Emission oci iint b ERR ER Red edi du Era asiaa ARRA CEA INFERRE skadene 44 3 3 2 3 1562 UC Report Electricity Consumption cscscccccccsssessssscsccesseessssceseccssessssseesceseseessssescesseeeessaaseeessesees 45 3 3 4 1 1564 UC Show Current EV POSION i oit rar ta roe e Ro Fea dba eae EE e ERR FREE aaae doa 46 3 3 4 2 1567 UC Call for Roadside Assistance cccccesccecesssccenssceseessececeseseeessecesesseeceessececaseccesssssce
82. 7 265499 Green eMotion WP 3 Deliverable 3 3 Page 143 of 210 Green N eMotion EG AL V and other Business Partners The proposed Service Interface is uploaded Successful out A new Standard Interface is proposed and reviewed come outcome Rejection of e Notification of the other Busi A Business Partner or Standard ness Partners the Marketplace Tech Interface e Cancellation of acceptance nical Director rejects process the interface Standard e Notification of the other Busi The interface exists Interface ex ness Partners already as Standard ists e Cancellation of acceptance Interface process 1355 ACT Business Partner Secondary actors 1355 ACT Business Partner 1402 ACT Marketplace Technical Operator Main scenario e The Business Partner proposes a Service Interface of a chosen Service as Standard Interface e The Service Interface is reviewed and accepted as Standard Interface by the Marketplace Technical Operator e Optionally the Service Interface is reviewed and accepted as Standard In terface by other Business Partners Notification of all Business Partners Alternatives tion Role Based Authorization required Data Security Data Integrity must be guaranteed Data Confidentiality must be ensured Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market 6 3 18 2 1493 UC Publish
83. 810 FTR EVSE Service Delivery 966 FTR Current EV charge 917 FTR Basic enhanced charging 918 FTR Enhanced charging 561 FTR Priority charging 1317 FTR Peak shaving on LV 979 FTR Authentication of user 965 FTR Peak shaving on MV 961 FTR DSO predefines peaks 1322 FTR Listing of price 1303 FTR Intermodality planning 1701 FTR Open access to EVSE GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 196 of 210 Green eMotion Ea L LY ID Business Scenario Description Satisfied By 953 FTR Human machine interface HMI 976 FTR Charging management 563 FTR User identification 1159 BS O2c Safety Services for safety of EV drivers 945 FTR Notification 944 FTR Vehicle tracking 1162 BS 03 Driver enhanced ser vices Information collected from the car and analyzed for end user e g bat tery history 1321 FTR Eco driving 1808 FTR Find Appropriate Charge Point Battery Station 920 FTR Battery life 945 FTR Notification 944 FTR Vehicle tracking 921 FTR Driving efficiency 1356 BS O4 Basic charging This scenario comprises basic charging services offered through the Marketplace 969 FTR EVSE Charging capabilities 1812 FTR EVSE Service Monitoring 1357 FTR Charge data collection 979 FTR Authentication of user 1701 FTR Open access to EVSE 953 FTR Human machine interface HMI 563 FTR User identification 1278 FTR Identification of available EVSE 956 FTR Battery s
84. CT Marketplace Technical Operator Service Provider ACT Service Requester Figure 22 Hierarchy of Actors in Core Marketplace Services The identified actors and their descriptions are listed in the following table ID Actor Description 1355 ACT Business Partner Abstract actor representing the service provider as well as the service requester 1367 ACT Marketplace Business Operator A special kind of the Marketplace Operator role 136 ACT Marketplace Operator Operates the platform and communications and manages access to and working of the marketplace 1402 ACT Marketplace Technical Operator A special kind of the Marketplace Operator role 137 ACT Service Provider Business Partner that offers and sells EV Services on the marketplace 138 ACT Service Requester Business Partner that consumes EV Services on the Marketplace Table 6 13 Core Marketplace Services Actors The interactions between the Actors in this chapter are for most of the scenarios illustrated in Appendix B for more information please refer to the business process diagrams 1456 BPD Use of Services1431 BPD Contracting Service 1495 BPD Service Detail Records for Accounting and Billing 1410 BPD Define and Register Service Contract Offering 1426 BPD Change or terminate a Service Contract 1427 BPD Prolong Service Contract 1428 BPD Enable Disable Service permanently 1387 BPD Service Registration 1429 BPD
85. Contractual Clearing Authorization 1270 It is important that the data keeps in sync with the binding customer data at the EVSP Therefore the typi cal CRUD creates read update and delete operations will be supported via APIs so that syncing can be triggered from external systems such as EVSP Backends or the marketplace 4 3 9 1 1512 UC Start a roaming charging process with Clearinghouse This Use Case is listed before in this Chapter please refer to paragraph 4 3 2 1 Scope amp Level Clearing Service Trigger to start a roaming charge after the transaction has been validated by the clearinghouse 4 3 9 2 1516 UC Delete Customer Contract by Service Provider from Clearing House Scope amp Level Clearing Service This use case allows the Service provider to delete a customer contract from the Clearing house This is an internal Clearing house characteristics and has no functional effect on the end user Goal in context A Service Provider wants to delete a contract of one of his customers from the Clear ing House Preconditions e Customer contract already exists in the Clearing House e Marketplace is operational e Business Partner is authorized for Clearing Services and enlisted in the Market place Successful out Customer contract is disabled within the Clearing House come Outcome Condition leading to out come Customer con Clearing requests are still granted e faulty API call tract cannot be e backend errors deleted e co
86. Delete Service 1271 BPD Propose Standard Interface 1363 BPD B2B Partner Management Create Business Partner Account 1371 BPD B2B Partner Management Change Business Partner Account 1382 BPD B2B Partner Management Activate Business Partner Account 1403 BPD B2B Partner Management Inactivate Business Partner Account GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 108 of 210 Green Dy eMotion A 6 3 Features and Use Cases 6 3 1 Overview The following table lists the Marketplace Features and their Use Cases ID Feature Realized By 1617 FTR Marketplace Authenti 1619 UC Marketplace Logout cation and Authorization 1618 UC Marketplace Login 924 FTR Search and Select Ser 1239 UC Search and Select Services vice 1484 UC View Service Details 1447 FTR Contracting Service 1485 UC Create Service Contract 1487 UC Download Service Specification 1239 UC Search and Select Services 1484 UC View Service Details 1478 UC Download Service Content 926 FTR Call of Service 1491 UC Create Service Transaction 1241 UC Call of Service 1245 UC Search and Select Service Contracts 1459 FTR Aggregate Service Call 1492 UC Aggregate Service Call Results Results 1685 FTR Create Notification to 1687 UC Notify Service Requesters of own Service Service Requester 1622 FTR Manage Requests for 1625 UC Create Request for a new Service new Services 1623 UC View Details of Requests
87. E PER ERAS REN AE a E FERAS ESSERE Y E AERE a EE Aia 42 3 3 1 Battery life services Feature content rrrnnrrrnsnnrrrnrsnrrrnnnnnrrrrnnvrrnnnnrrrrnnnnnnsnnanrnsnnnnrnsnnnnnnesnsnnnenennnnn 42 3 3 2 Battery life services Use cases cccsccccesssccesssecceessseceeseecesesseccesaeeccessseeeessseccessueccesseeecesssecescesesaeeees 43 3 3 3 Vehicle tracking Feature content cceeccesssececccesssssseeeeecessesssseeeeeesesenssseeeeeeseseessseeeeeeseesaaeeeaaaaeees 46 3 3 4 Vehicle tracking USe aS65 io tie aaee Eea EE RARE SR RAREMENT ATE AERE RF E EEA EA 46 3 3 5 Charging infrastructure management Feature content rrrnrrrrnnnrrrrnnavrrernnnrrrnnnnvnrnnnrnernnnnnnsnnnnnnnn 52 3 3 6 Charging infrastructure management Use cases cccccceesseccessscecesseececeseeceessseecesseeeesesseecessseecensaees 52 3 4 Cross domain Features and Use cases rrerrrnnrrrrennrrnnennrrnnennrnesennreresnrnrsennnneseenresesnnrresennrnesesnrsessenrrenressennseee 55 3 4 1 1300 FIR Car information iuo ecce eei ertet tonio EXE tee RISE N SERE TREES YR a Aaaa eC E NAR Rn FE FR EaR ERa Eaa 56 3 4 2 1303 FTR Intermodality planning cccccccccccccssssscccceesssssceeeeeeesseessseeeecesseseseseeeeceseeeseaseeeeesseeeeseseaes 57 GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 3 of 210 Green N eMotion Ea s V 3 4 3 1301 FTR Feet management ee oer ere ru hae a v dren cocepaessadedevtateceseseuessuense bes 59
88. EV onboard unit Receive notification Send Acknowledgement Receive Acknowledgement Figure 26 Send Notification M2V GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 184 of 210 Green I ET 2 eMotion LY Service Provider Marketplace EV onboard unit Send Acknowledgement Receive Acknowledgement Figure 27 Send Notification V2M GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 185 of 210 eMotion Green on Ea 2 Charging Service Provider Marketplace EU Send Charging Notification Check interrupted transfer of charging details Request for Send Acknowledgement interrupted data Prepare Charging Details Send Charging Details Receive Charging Details Send Acknowledgement Check for more requests e Figure 28 Update Charging Details GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 186 of 210 Green N eMotion Ea AL V D Use Cases in Chapters I3 Cx Innrid 9 MEM epe 11 2 Charging functional domain use case model arannannnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnee 18 23 31 1510 UC Before charging entente etre e Re EH eR cubs Enea e Carla eddik 23 2 3 3 2 1527 UC Search for EVSE iuis diss tex ve Er E ERARHE ERE E o ERE BR o FERRE AAA FERT E TR paa MR dd 2
89. EVSE Mode 1 or 2 charging By default we assume there is only Mode 3 charging The Clearinghouse is involved only in case of roaming Related informa tion GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 37 of 210 Green I Ra eMotion A WS Adur 2 5 3 2 1502 UC EV Identification Authentication and Authorization This Use Case is listed before in this Chapter please refer to paragraph 2 4 3 1 Scope amp Level Basic end user services This use case covers identification of contract belonging to a user own customer or roamer at a charge spot or battery switch station and his authentication and au thorization to execute the process of charging or battery switching Use case describes the interaction between EV EV driver EVSP EVSE operator and optionally the Clearinghouse when roaming 2 6 Service performed after charging of EV 2 6 1 After Charging Overview Business services described in this chapter occur after the EV driver disconnects and physically leaves the parking space In the figure below the blue square area depicts the During Charging services and the black box in cludes all services that may occur after the charging is completed There is expected some overlap with During Charging services which depend on the implementation of the use cases in this chapter r User parks EV near ser connects EVto User is goodtogo Charging can may or may not User disconnects E E
90. EVSE Operator 138 ACT Service Requester 128 ACT EVSP Electric Vehicle Service Provider Main scenario The CO2 index per energy supplier based on the unified CO2 intensity kWh en ergy mix is being calculated for an EV and for a specified period of time GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 44 of 210 Green Dy eMotion BG V Alternatives Ea Variations In some implementations this functionality will be a rather simplified model Betterplace may implement such a simplified model in Denmark calculation CO2 emissions from average share of renewable energy in the grid over a period of time and aver age driver behavior This will not be the accurate CO2 emission of a particular EV driver Related informa Charging data records or at least a subset of these have to be transferred tion through the marketplace to the Charging Service Provider to enable this service It has to be clarified if the benefit for the attendees of the marketplace is bigger than the possible risk of publishing business data All business relevant information has to be made anonymous Only the calculated indexes are exported to an authorized requester 3 3 2 3 1562 UC Report Electricity Consumption Scope amp Level Value added service Show the electricity consumption of a vehicle This use case enables EVSE operator to report an EVSP of current and historical charging service consumed e g electricity consumption by a
91. EVSEs is not implemented in this 5 v Charging Point communicate Scenario but in Etc Distributed 2 t Connection Data 9 Congestion Management EN i 5 z Reschedule Charging Logic equals the logic of Charging tasks within Substation Restrictions g s t i z 2 Change Charging Throughput i i 2 85 Done E 5 V2G Capabilities 21 H v 1 Charging Target amp Status GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 177 0f 210 Green NN EI 2 eMotion FE 1198 BPD Congestion Management through TOU Tariffs Energy Market Market Place EV Operations O Publish new s Q TOU tariffs Validate Start A Done Distributer DSO TSO Energy Supplier D Register for Clearing v D TOU tariffs Identify amp Inform EVSE Partners Identify amp inform relevant Suppliers to EVSE Operators Confirm Parties Involved to Distributor Service Broker Clearing House EVSE Operator GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 178 of 210 eMotion Green on EG A 1199 BPD Distributed Congestion Management Define amp Publish Required Change Select suppliers and request service O e O Congestion Load or Activate V2G Charging Point implement business rules for EV charging and V2G flexibility
92. EVSP is acting as an aggregator will participate in the different energy markets as any generator unit for selling energy and for offering ancillary services There fore the unbundling precondition is true only in the energy market but not in the ancillary services market The customer acceptance is required and V2G availability must be stated in the contract between the EVSP and its customer and there shall also be a B2B The EVSE Op is connected to the marketplace through its back end The EVSP is connected to the marketplace through its back end The DSO is connected to the marketplace through its front end towards the grid The EVSP states in its contracts with the customers that the average time of recharge is sensitive to the network safety issues peaks management from the DSO and eventually to charging points priority issues coming from the deployment strategy of the EVSE Operator A smart recharging infrastructure is needed in order to accomplish peak pre definition demands coming from the DSO to the EVSE Op An adequate communication capability should be endorsed in the EV in order to receive modulation orders from the DSO through the EVSE energy gate way especially for low power and time consuming recharges e g 3 3 kW The EVSEs are in communication with an EVSE Op back end that aggregates data from each EVSEs The EVSEs Operator back end aggregates data from each EVSEs and is able to perform communication with the DSO or the
93. Green N eMotion a AL V Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market 6 3 20 4 1378 UC Change Business Partner Account Details Scope amp Level Core Service Goal in context Detail Data of a Business Partner are changed Business Partner is registered at the marketplace The detail data of a Business Partner are changed in the system at his request come Failure outcomes Condition leading Request not e Display of an error message Request Form is complete e Cancellation of the change re not filled correctly quest lt lt gt S 9Q 1355 ACT Business Partner 1367 ACT Marketplace Business Operator Main scenario e Change Request Form filled and submitted by a representative of the Business Partner e Change of the Business Partner detail data in the system by the Marketplace Business Manager e Notification of the Business Partner Alternatives Related information Access Role Based Authorization required Data Security Data Integrity must be guaranteed Data Confidentiality must be ensured Data Privacy Sensitive Data is only stored when needed and authorized Data Export Policy required Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market 6 3 21 1369 FT
94. Green NN eMotion En AL V Green eMotion Development of a European Framework for Electro mobility Deliverable 3 3 Business Services Use cases and Requirements Helease 1 Prepared by Betterplace BMW Bosch Daimler Endesa EDF Enel RWE SAP Siemens Under the lead of IBM Date April 04 2012 Version v1 5 GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 1 of 210 Green IN eMotion V Document Information Authors Name Company Key author Martin Rapos Paul Frenay IBM Key author Chapter 2 Anders Pold Torben Fog Betterplace Key author Chapter 2 Thomas Gereke Karsten Mirt Siemens schin Robert Jaquet Key author Chapter 2 Holger Braess BMW Key author Chapter 3 Tom Kiemes Bijan Rahnema SAP Key author Chapter 4 Giovanni Coppola Enel Key author Chapter 5 Norbert Reschauer IBM Additional author Brian McBeth Daimler Additional author Thomas Stiffel Bosch Additional author Dominique Bertin EDF Additional author Narcis Vidal Endesa Additional author Luca di Stefano Federico Caleno Enel Additional author Detlef Schumann Ruth Shilling Volker Fricke IBM Additional author Stephan Cater RWE Additional author Felix Ott Joachim Marx SAP Additional author Anke Richter Siemens Distribution PU Public X PP Restricted to other programme participants including the Commission Services RE Restricted to a g
95. Green eMotion WP 3 Deliverable 3 3 Page 33 of 210 Green DN eMotion a 2 listed in the table below The overarching use case of this section is defined as 1502 During Charging and is complemented by several use cases which realize the same features The following table lists the Features that are relevant in the Services during charging phase ref 2 1 Features Use Cases 1358 FTR Connect Charge Disconnect 1518 UC During charging 956 FTR Battery switching 1502 UC EV Identification Authentication and Authoriza 1701 FTR Open access to EVSE tion 564 FTR SLA 561 FTR Priority charging 562 FTR Low priority charging 950 FTR Charging as guest 1702 FTR Charging monitoring 1357 FTR Charge data collection 951 FTR Charging report 976 FTR Charging management 1299 FTR Charge point management Table 2 4 During Charging Features and their Use Cases Several interactions between these actors as are illustrated in 1200 BPD Enhanced charging please re fer to Appendix B 2 5 2 During Charging Feature Content 1358 FTR Connect Charge Disconnect This feature describes the process from a user connects a car to a car is once again disconnected e Auser parks his car by a charge point e The user identifies himself with a compatible ID RFID scan phone call to customer service center etc e The user is authenticated and can connect the car to the charging with a compatible charge cable e A signal beep green l
96. ING Managing EVSP data cccccccccccsssssssecccessssssseeeeeecesssssseeeeeeseeeesaeeeeeeeesessaeeeeeeees 77 4 3 9 983 FTR CLEARING Managing customer data cccccccccccessssssseeeceecesessaueeeeeessesssaseeeeeesseseaseeeeeeeeeees 79 5 Energy functional domain use case MOdel aaannnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnee 83 5 1 o ia 83 5 1 1 End user PePrSPeCtive cceccesssscccccessssneeeeeecesseeseeeeeecesseeeseeeeecessssaseeeeeeesesaseeeeeeseseeesseeeeeeeseeeeeseseeaaes 83 5 1 2 Business to business perspective sisestab iani a EAE A aE E Eas aE aak 84 5 1 3 Mark tplace Context sisenes nao se erac e bon dx naes e a seta eai Eaa Mag FERRE RETE CURA ERR aiea tadak 84 5 2 p 84 5 3 FEOTUNES CNG USEC COSES c 85 5 3 1 NENNE 85 5 3 2 972 FTR Network congestion management ssssssssssseeeee eene enean nennen sse n nnn nasse nnn 85 5 3 3 973 FTR Reactive DOWAR ione shade ceeeeaee exe teo etx tin eR evo eR Te Pe Yd o VERE Vah eaae sa de aea dead Foo EY Hp Na aa 89 5 3 4 974 FTR Phase balancihBsc s ore nere ray eR teens edu estuche nun E psa o eu ER ease 91 5 3 5 975 FTR Ancillary SetrVICeS iiie aereo ruere ERE Eyed seen Fey aa vea tae devo ra dn ku ERE WEE NE RR EN EAR Y NEN ENDS 92 5 3 6
97. MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 125 0f 210 Green N eMotion BE AL V Data Security Data Integrity must be guaranteed Data Confidentiality must be ensured Data Privacy Sensitive Data is only stored when needed and authorized Data Export Policy required Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market 6 3 10 935 FTR Provide Service Contract Framework It is in the intention of the GeM Marketplace to have standardized Service Contracts between the Service Provider and the Service Requester to support easier contract negotiation For that reason the GeM Marketplace has to provide a Service Contract Framework based on modules which the Service Provider has to choose during the service registration process to define its Service Contract Offering The Service Contract Framework itself can be static and provided by a platform independent representa tion e g XML 6 3 10 1 1482 UC View Service Contract Template Goal in context The template of the Service Contract Framework is displayed to the Business Partner Preconditions Contents of the Service Contract Framework are provided to the marketplace by a static platform independent representation e g XML Successful out The Business Partner is be able to view the contents with all available options of come the Service Contrac
98. Main scenario e The Service Requester chooses a Service and reviews the Service Con tract Offering with its options e The Requester chooses all required sections and may choose available optional sections and is able to store his selection e The Service Requester accepts the Service Contract Offering with his se lection on options e The chosen sections configure a new Service Contract between the Service Provider and the Service Requester e The new created Service Contract is stored e The Service Provider will be notified Alternatives Variations Related informa tion Access Role Based Authorization required Data Security Data Integrity must be guaranteed Data Confidentiality must be ensured Data Privacy Sensitive Data is only stored when needed and authorized Data Export Policy required Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market 6 3 4 2 1487 UC Download Service Specification Scope amp Level Goal in context The Service Requester downloads the service specification i e Service Interface e g WSDL of an offered Service at his interest A Service is selected Successful out The Service Requester downloads the Service Interface e g WSDL come Failure outcomes Condition leading to outcome GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 114 of 210 gt 1
99. Management Method on IBM Jazz platform with the use of Rational Re quirements Composer RRC Led by IBM 4 working groups identified features business and core marketplace services and further detailed them through use cases e Interactions from the user perspective were defined using the Usability Engineering Method Led by Siemens a series of workshops resulted in a task case map around the Core services The results of both methodologies were integrated in a final workshop and additional requirements were documented in the RRC tool making it the sole repository of the collected requirements A more detailed description of the two methodologies is presented in the Methodology sections of this chapter To conclude the D3 3 deliverable comprises functional aspects of e mobility under the assumption of the use of shared information platform s the GeM Marketplace eco system Partners from relevant e Hosted environment with access for WP3 Partner Rational Software by IBM was provided to all WP3 Partners as part of the project GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 11 of 210 Green N eMotion BG AL mobility related industries participating in this work package WP3 have defined services which are from their perspective most likely to be used in the demo regions already during the first release These ser vices were suggested because of their high added value and their expected early market adoption and user acc
100. Motion WP 3 Deliverable 3 3 Page 74 of 210 Green eMotion Ea L V UC 1502 but parties may choose to implement UC 1502 within the connect charge disconnect cycle 4 3 5 981 FTR Authentication This feature applies when an EV driver seeks to charge at a public EVSE which might not be operated by the EV Service Provider that this driver has a contract with The Clearinghouse checks whether agreements for that customer or his service provider do exist If so it provides an indication of what services the customer might be is allowed to consume and provides that information to the EVSE which can then e g start the charging process To trigger the feature an EVSE operator has to contact the clearing house 4 3 5 1 1518 UC During charging This Use Case is listed before please refer to paragraph 2 5 3 1 Scope amp Level End user services This use case covers the enhanced connect charge disconnect cycle FTR1358 with additional services Use case describes interaction between EV driver EVSE Backend and optional 3rd parties Energy trader DSO public sector Note that Identification Authentication and Authorization is a separate Use Case UC 1502 but parties may choose to implement UC 1502 within the connect charge disconnect cycle 4 3 5 2 1512 UC Start a roaming charging process with Clearinghouse This Use Case is listed before in this Chapter please refer to paragraph 4 3 2 1 Scope amp Level Clearing Servi
101. O to fulfill the distribution rules established by the regulation framework in which it operates In example frequency and voltage will be adjusted in the local grid by drawing power from the batteries or interrupting load This service will increase the quality of power in the grid and the DSO will reward the EVSP aggregator for provi sion of this service Also reducing the imbalance on phases on the LV substation is another example of use case of an ancillary service Load switching from different phases will provide phase balancing to the grid that will reduce the losses on the dis tribution wires Phase balancing will reduce losses in the distribution grid DSO will reward the EVSP based on the savings it can reach by the reduction of losses The injection of reactive power coming from a distributed generation unit such as an EVSE into the grid makes possible to reduce the amount of reactive power on the transmission lines re phasing the MV grid and this is another example of ancillary service which may be enrolled here All 973 974 and 975 features can be deployed GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 89 of 210 eMotion Green on ER 7 through this single use case Other examples of ancillary services are scheduling and dispatch reactive power and voltage control loss compensation load following system protection energy imbalance An EVSP may offer through a V2G capability to be establishe
102. Privacy Sensitive Data is only stored when needed and authorized Data Export Policy required Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market 6 3 12 6 1246 UC Create Service Contract Change Request Scope amp Level Goal in context A change of a bilateral Service Contract is a two step process A Business Partner Service Provider or Service Requester makes a change request on a Service Contract Preconditions A Service Contract between the Service Provider and the Service Requester ex ists and is selected Successful out A change request on a Service Contract is created and the other Business Partner come is notified Failure outcome Failure Outcome Condition leading to outcome Request Form in Display of an error mes Business partner failed to com complete sage plete the form correctl Primary actor 1355 ACT Business Partner 137 ACT Service Provider or 138 ACT Service Re quester Secondary actors Main scenario e The Business Partner fills a form for the change request on the Service Contract GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 132 of 210 Green N eMotion EA AL V Alternatives Related information Access Role Based Authorization required e Service Contract History Entry is created e The other Business Partner is notified
103. R Activate Inactivate a Business Partner Account A registered Business Partner can request an inactivation of his active account as well as an activation of his inactive account The following actions have to be taken by the Marketplace Business Manager e Check of the Service Contracts of the Business Partner has to be performed e Change of the Business Partner Object in the GeM Marketplace Check of the Partner Contract between the Business Partner and the GeM Marketplace has to be per formed GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 149 of 210 Green DN eMotion En AL V 6 3 21 1 1373 UC Search and Select Business Partner This Use Case is listed before in this Chapter please refer to paragraph 6 3 19 1 Scope amp Level Core Service Find Business Partners that satisfy search criteria 6 3 21 2 1480 UC Create Service Contract Termination Request This Use Case is listed before in this Chapter please refer to paragraph 6 3 12 1 Scope amp Level Core Service A termination of a bilateral Service Contract is a two step process A Business Partner Service Provider or Service Requester makes a termination request on a Service Contract 6 3 21 3 1376 UC Change Business Partner Account This Use Case is listed before in this Chapter please refer to paragraph 6 3 21 3 Scope amp Level Core Service Data of a Business Partner are changed 6 3 21 4 1377 UC View Business Partner Account Details Th
104. R Enable Disable Service The GeM Marketplace must provide the ability to enable and disable a service There are two different scenarios for enabling and disabling e Enable Disable permanently i e the disabling is requested by the Service Provider and all af fected Service Requester have to be notified and they have to agree This results in a termination of their existing Service Contract e Enable Disable temporarily i e starting and stopping the service performed by the Marketplace Technical Operator e g on technical issues 6 3 15 1 1255 UC Start Stop Service Scope amp Level Goal in context A Service can be temporarily disabled Preconditions e A Service is selected e he Service is available and published GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 139 of 210 Green N eMotion EG AL V Successful out The Status of the Service has changed Started or Stopped come Failure outcome Failure Outcome X Condition leading to outcome por Status Error Display of an error message Service is not in status Pub lished StartError Display of an error message Service is not stopped ramanea 000 r splay of an error message Service is notstaded Secondary actors actors e The e ine selesied Samer Technical Operator starts or stops the selected Service The new status of the Service is displayed Alternatives Variations SSCS Related information S Cur
105. SE Contract from Clearing House esses 79 4 3 8 4 1497 UC Create EVSP EVSE Contract within Clearing HOUSe ceesseee eene nnne 79 4 3 9 1 1512 UC Start a roaming charging process with Clearinghouse esses eene 80 4 3 9 2 1516 UC Delete Customer Contract by Service Provider from Clearing House eee 80 4 3 9 3 1514 UC Create Customer Contract by Service Provider in Clearing House sesso 80 4 3 9 4 1515 UC Change Customer Contract by Service Provider in Clearing House eese 81 4 3 9 5 1517 UC Change Customer Contract by Customer himself within Clearing House sees 81 5 Energy functional domain use case model srnannvnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnennnnennnnnnnnenennnnneee 83 5 3 2 1 1604 UC Vehicle to grid sign l tit rtr tr na Re ento re o eH Y e ER FERA REA AREA RR RE EAR XR EAR AR Fed ERA GR 86 5 3 2 2 1602 UC flexible load for congestion management ssccceeesssccessscccessccesessscceesseeccetsesesenseecesssseceetsseees 87 GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 188 of 210 Green N eMotion EG 5 3 3 1 1605 UC Reserve and activate ancillary services cccccccceseesssscccccccssessnsscescesseesssssescesseesnssseascecseseesssssseeeees 89 5 3 3 2 1604 UC Vehicle to grid signal cccesssssscccccsseessnscsccesesesssssessecssessuseescccseeesssessces
106. SE location No charging point available e No communication to charging cannot be point found e inconsistent data scheme P nere 133 ACT Vehicle Driver 131 ACT EVSE Electric Vehicle Supply Equipment 128 ACT EVSP Electric Vehicle Service Provider Main scenario e Entering search criteria for charging points e g address e Show result that mean information about selected charging points Variations The search functionality will vary from service provider to service provider The combination of search functionalities is endless and cannot fully be described Related informa This use case enhances is embedded in the UC 1510 before charging tion e Search of EVSE requires a fast system response response time lt 3 seconds GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 25 of 210 Green N eMotion BG AL 2 3 3 3 1528 UC Reservation of EVSE Scope amp Level Value added service The search function can be supported from different End user Customer applica tions e The result can be shown on a Geo Map e g Google Maps Bing Teleatlas or and in a text table All relevant information e g address plug type etc have to be included To reserve an EVSE the EV driver has to choose a suitable EVSE and then reserve the relevant time frame The reservation function can be with costs from the EVSP EVSE for the EV driver To confirm the reservation of the EVSE the EV driver receives a confirmation message p
107. Service 1447 FTR Contracting Service 1622 FTR Manage Requests for new Services 1685 FTR Create Notification to Service Requester 927 FTR Service Transaction overview 1617 FTR Marketplace Authentication and Authorization 1174 BS S2 Service Detail Records for Accounting and Billing BS S2 Service Detail Records for Accounting and Billing 924 FTR Search and Select Service 927 FTR Service Transaction overview 1617 FTR Marketplace Authentication and Authorization GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 198 of 210 Green eMotion V Ed ment Cycle ID Business Scenario Description Satisfied By 1175 BS S3 B2B Contract Man Create occurance of predefined 1469 FTR Suspend Resume Service Contract agement Service Contract 924 FTR Search and Select Service 1682 FTR Add new Service to existing Service Contract 935 FTR Provide Service Contract Framework 931 FTR Change or Terminate Service Contract 1397 FTR Prolong Service Contract 1396 FTR Define and Register Service Contract 1617 FTR Marketplace Authentication and Authorization 1176 BS S4 Service provision Service Life Cycle Management 924 FTR Search and Select Service ing registration life cycle 1315 FTR Register Service mgmt 1501 FTR Certificate Service 940 FTR Version Service 1444 FTR Delete Service 1617 FTR Marketplace Authentication and Authorization 1443 FTR Enable Disable Service
108. Table 4 10 Roaming Domain Features and their Use Cases sssssssseseeeeennerenens 70 Table 5 11 Energy Domain Actors einn nennen tnnt ddinaa ir danie 84 Table 5 12 Energy Domain Features and their Use Cases sss 85 Table 6 13 Core Marketplace Services Actors ssssssssssssssssssseeee eene nnne nnne nennen 108 Table 6 14 Core Marketplace Services Features and their Use Cases rmmrrnnrrrnrnnnvnrrnsnnrnrrrrnnnvsrrrrnnnne 110 GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 7 of 210 Green DN eMotion BG AL V List of Abbreviations API Application program interface KPI Key Performance Indicator B2B Business to business LV MV Low voltage Medium voltage CA Consortium Agreement MPO Metering Point Operator CDR Charge detail record MSP Measurement Service Provider CH Clearinghouse NOC Network Operations Center Nationale Plattform Elektromobilit t German CP Charge Point NPE initiative Description of Work Annex I of Original Equipment Manufacturer DoW Grant Agreement OEM i e Electric Vehicle manufacturer DSO Distribution system operator PHEV Plug in electric vehicle EOC End of charge RES Renewable energy source ESB Electricity Supply Board RFID Radio frequency identification ETA Estimated time of arrival SDR Service detail record Supply Equipment EV Electric vehicle SECC Communication Controller
109. The collection of charging data is therefore an important information source for current and scheduled energy flow for the energy supplier and the third party ser vice provider This detailed information of the charging process is an extension of the standard Charging Data Records CDR and has to be handled with great accuracy by mak ing it anonymous and encrypted The attendees of the marketplace have to calculate the pros and cons of this ser vice but the potential benefit of detailed reporting data is a major argument For an illustration of this Use case please refer to Figure 28 Update Charging De tails in Appendix C 3 3 2 2 1561 UC Calculate CO2 Emission An EV is registered at the marketplace resp the driver is authenticated Charging data records CDR or battery life data have been synchronized through the mar ketplace before Fall out A calculated list of CO2 indexes of a requested EV for every energy retailer that Fall was involved in charging processes in the specified period of time is generated Failure outcome Condition leading to out come The CO2 index Display of an error mes The requested EV is unknown can t be calcu sage There is no data for the Cancellation of the in given EV and time period dex calculation The specified period of time is invalid FE 137 ACT Service Provider Secondary actors 130 ACT Energy Retailer 143 ACT EV Electric Vehicle 133 ACT Vehicle Driver 132 ACT
110. UC Peak shaving 1313 FTR Allow interrupting 1572 UC Reduce Charge Power by DSO 961 FTR DSO predefines peaks 1597 UC Peak shaving 1596 UC Peak load threshold on a substation 966 FTR Current EV charge 1524 UC Fleet manager monitors energy consumption of pool cars 1598 UC Aggregated EV charge overview by the DSO 1202 FTR V2G energy supply signal 1604 UC Vehicle to grid signal 560 FTR V2H supply signal 1604 UC Vehicle to grid signal FTR Historv of FVSE use 1599 LIG Historv of FVSF use Table 5 12 Energy Domain Features and their Use Cases 5 3 2 972 FTR Network congestion management Congestion may happen within a load area under critical timeslots and massive EV penetration may jeopardize energy disposal for Energy Vendors generic customers It is generally common among several regulatory framework that this topic is within the DSO duties that is the one who manages the LV and MV grid The DSO therefore is in charge of avoiding this hazardous condition and eventually reacts whenever network congestion within a load area is either forecasted or real time detected according to the technology used to monitor the energy distribution grid Once the risk is detected the congestion management process is run according to the DSO needs This requires that both the EVSP and EVSE Op are aware that their performance parameters regarding quality of service towards customers are at lower priority than the network safety and reliability An
111. V is parked an available charge charge socket EV lights blink due to occur from charge socket disconnected from socket immediate charge user might connect the charge socket cable back right again Parking cycle Charge cycle Parking cycle Connection sequence Charge Dis connection sequence Figure 11Scope of After Charging End user perspective Basic end user services that take place after charging include charging history reports billing own EV account status overview statistics of own EV use etc GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 38 of 210 Green NN eMotion En AL V Business to business perspective From the service provider s perspective there are several value added services available to service re questers via a Marketplace These include individual per EV or aggregated reporting on kilometers driven energy consumed CO2 emissions etc Marketplace context In this stage only a few After Charging Services have been identified and described It is expected that more of these will be offered in the future by service providers directly or through Marketplaces Currently these services satisfy Business scenarios from the Charging domains through feature 970 Consumption monitoring The overarching use case of this section is defined as 1502 After charging The following table lists the Features that are relevant in the Services after charging phase ref 2 1 Features Use Ca
112. WP 3 Deliverable 3 3 Page 67 of 210 Green N eMotion a N 4 If the identity is in a black list this would lead to an instant denial of charging If the identity is neither whitelisted nor blacklisted the charge request is forwarded to the EVSE s Operator Backend were the whitelist blacklist concept can be applied again This would most probably occur when the EVSE operator is also an EVSP or has some maintenance or master cards for his infrastructure If the identity is not white or blacklisted at the EVSE Operator Backend either it is unknown to the EVSE Operator This signifies a Roaming scenario In this case the EVSE Operator Backend forwards the charge request either to the EVSP as identified by the ContractID i e bilateral roaming or to a Clearing house i e centralized roaming agreements In case of centralized roaming agreements the Clearinghouse validates the B2B contract between the EVSE operator and the EVSP of the EV Driver identified by the ContractID The Clearinghouse uses the marketplace for this validation the B2B contract details are not available to the Clearinghouse If a valid B2B contract between EVSE Operator and EVSP is in place the EV Drivers right to use this contract remains to be validated For this the Clearinghouse may check its own database or ask the EVSP Now the Clearinghouse may send and a roaming acceptance or rejection back to the EVSE op erator backend where the charging request came from 4 1
113. a mobile phone num ber was transmitted too 3 3 4 3 1568 UC Show EV Position History Scope amp Level Basic end user service Display a history of vehicle positions Goal in context The list of positions of an EV is displayed in a map The EV is registered to the system and has transferred position data before The period of time for the location history is defined A track of vehicle positions in a fitting map is displayed come MN c come unknown EV e Display of a warning The EV s id is not registered message to the central service e No data for the Display of a warning The EV has not sent any lo period of time of message cation information for the re this EV quested period of time n Bin shy actor 137 ACT Service Provider on the Marketplace 1579 ACT Third Party Service Provider Location Service Provider GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 48 of 210 Green Dy eMotion BG V Xe Skin e rel 1594 ACT Fleetmanager 128 ACT EVSP Electric Vehicle Service Provider Main scenario An authorized user of the marketplace is asking for the position of an EV A valid period of time for the position history is defined The request is forwarded to the location service provider that has stored the location history of this vehicle The list of vehicle positions can be displayed in a map Alternatives Related information The service uses data previously stored to the database of the
114. and Select Requests 1622 FTR Manage Requests for new Services for new Services 1245 UC Search and Select Service 1447 FTR Contracting Service Contracts 926 FTR Call of Service 1443 FTR Enable Disable Service 1469 FTR Suspend Resume Service Contract 940 FTR Version Service 931 FTR Change or Terminate Service Contract 1242 UC Search and Select Service 927 FTR Service Transaction overview Transactions 1239 UC Search and Select Services 940 FTR Version Service 1447 FTR Contracting Service 927 FTR Service Transaction overview 924 FTR Search and Select Service 1475 UC Search and Select Standard 1446 FTR Search and Select Standard Interfaces Interface 1445 FTR Define new Standard Interface 1315 FTR Register Service 1527 UC Search for EVSE 978 1278 FTR Identification of available EVSE GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 208 of 210 Green Dy eMo er Ea ID Use Case Realizes Feature 1576 UC Set Geofence 944 FTR Vehicle tracking 1564 UC Show Current EV Position 944 FTR Vehicle tracking 1568 UC Show EV Position History 944 FTR Vehicle tracking 1512 UC Start a roaming charging 986 FTR Roaming in different countries process with Clearinghouse 985 FTR Roaming in same country 983 FTR CLEARING Managing customer data 1291 FTR CLEARING Managing EVSP data 982 FTR CLEARING Validation of contract 981 FTR Authentication 1255 UC Start Stop S
115. arging GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 194 of 210 Green eMotion Ea L LY ID Business Scenario Description Satisfied By 1181 BS C1c Public charging charging at the curbside in public spaces parking lots 1358 FTR Connect Charge Disconnect 1702 FTR Charging monitoring 960 FTR Charging and battery switching status notification 557 FTR Reduce load of charging 1809 FTR EVSE Service Access 1277 FTR Phone roaming 1701 FTR Open access to EVSE 976 FTR Charging management 563 FTR User identification 953 FTR Human machine interface HMI 1811 FTR EVSE Service Control 1318 FTR Reservation of Charge Spot 565 FTR Charge point selection 957 FTR Road side charging 1808 FTR Find Appropriate Charge Point Battery Station 970 FTR Consumption monitoring 951 FTR Charging report 1812 FTR EVSE Service Monitoring 566 FTR Cross sale 558 FTR Increase the load of charging 979 FTR Authentication of user 562 FTR Low priority charging 1183 BS C3 Mono directional con trolled charging Charging can only be reduced or increased by DSO 562 FTR Low priority charging 557 FTR Reduce load of charging 1811 FTR EVSE Service Control 558 FTR Increase the load of charging 1184 BS C4a Charging V2G Electricity from EV battery is fed into the grid 1202 FTR V2G energy supply signal 1810 FTR EVSE Service Delivery 1185 BS C4b Charging V2H Electricity from EV
116. arging preferences renewable energy flexible interruptible or reduced charge if rewarded by lower price charge with commercial of fers nearby charge with free parking search for EV designated parking but no charging etc These preferences would be stored by the EVSP in the driver s user profile and made available to other service providers either directly by the EVSP or through a Marketplace Based on these settings or pre defined preferences the driver is before each trip offered tailored search results with likely preferred charging points This should be communicated through a very simple user interface and is comparable to today s planning of the route through GPS Several constraining characteristics such as the weight and size of the car type of plug type of battery charge AC DC fast normal combination are considered during the optimized search Business to business perspective From the service provider s perspective there are several useful value added services optionally avail able via a Marketplace This may include the current location of the driver to obtain an updated ETA se lected parking lot average amount of energy charged while parking minimum service level granted to particular EV by the EVSP etc Legal constraints may apply in different countries 4 This may lead to a variant of the specific use case Inheriting Artifacts with specific constrains The major case should be interoperable throughout Europe
117. at case the EVSE will not act as a bidirectional energy gateway towards the grid Also the condition of hav ing an EV without ISO 15118 V2G compliant communication leads to the same alternative GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 97 of 210 Green N EI eMotion V The DSO may decide not to use the energy availability published from the EVSP because it is not profitable or other reasons The EVSP can also delete its offer ing This use case shows the chance of using an aggregated high level service e g the amount of EV drivers belonging to an EVSP currently connected and charg ing matched with others location of E V s charging per load area network con gestion management V2G energy supply signal in order to make use of V2G capability as a tool for network congestion management in a proactive way by deploying peak shaving 5 3 8 1317 FTR Peak shaving on LV DSO uses aggregator service to bid peak shaving demand on particular substations through the market place Alternatively DSO can approach the aggregator directly 5 3 8 1 1597 UC Peak shaving ius Use Case i is listed before in this Chapter please refer to paragraph5 3 7 1 Scope amp Leve Value added service If network congestion management and V2G energy supply signal hypothesis are satisfied an advanced solution for dealing with congestion issues would be using the V2G availability published from the EVSPs in ord
118. ata Integrity must be guaranteed Data Confidentiality must be ensured Data Privacy Sensitive Data is only stored when needed and authorized Data Export Policy required Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 128 of 210 Green N eMotion EA AL V Scalability capable to grow with electro mobility market 6 3 11 5 1470 UC Create Service Contract Offering Scope amp Level Goal in context During the service registration a Service Contract Offering is created from the template of the Service Contract Framework by the Service Provider Preconditions Contents of the Service Contract Framework are provided to the marketplace by a static platform independent representation e g XML Successful out A new Service Contract Offering is created come Failure outcomes Failure Outcome X Condition leading to outcome Service Contract Display of an er Not all required sections from the ser Offering incomplete ror message vice contract framework are chosen 137 ACT Service Provider Secondaryactor Main scenario e The Service Provider chooses all of the required sections and additionally optional sections from the Service Contract Framework e The chosen sections configure a new Service Contract Offering e The new created Service Contract Offering is stored
119. ation For the reservation of an EVSE the EV driver has to search for the EVSE This use case enhances is embedded in the UC 1510 before charging e Reservation of EVSE requires a high and fast system performance complex algorithm and response time 3 seconds Issues System performance GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 26 of 210 Green DN eMotion a AL V 2 3 3 4 1574 UC Third party information Scope amp Level Value added service The City pilot service within the EVSP backend uses information from third party providers to adapt the search results regarding to the personal preferences of the EV driver Possible preferences are e g e Points of Interest POI e Favorite chains e Special sales e Special events concert movie Preferences can be combined with options to fine tune the search result Possible options are e g Time of the day Season Traffic news Timetable of public traffic e Weather forecast This use case is linked to the search for CP UC 1527 which is embedded in the before charging use case UC 1510 Goal in context An EV driver wants to search for a Charge point EVSE in order to charge the EV or for short time parking The EV driver uses his end user customer application to connect to the city pilot service of his EVSP This use case enables the search for a Charge point EVSE to combine personal preferences of end user and information from third party providers P
120. ation of Interfaces Messages 1176 BS S4 Service provision ing registration life cycle mgmt 1175 BS S3 B2B Contract Management 1178 BS S6 B2B Partner Management 972 FTR Network congestion management 34 BS E2 Virtual Power plant 945 FTR Notification 1797 GRP Driving Related Services 1162 BS O3 Driver enhanced services 1159 BS O2c Safety 1701 FTR Open access to EVSE 1181 BS C1c Public charging 1356 BS 04 Basic charging 1160 BS O1 Enhanced charging 1180 BS C1b Semi public charging 1297 FTR Parking space management 1797 GRP Driving Related Services 1298 FTR Parking space monitoring 1797 GRP Driving Related Services 1317 FTR Peak shaving on LV 1160 BS O1 Enhanced charging 31 BS E1c Distributed Congestion Mgmt by Ag gregators 965 FTR Peak shaving on MV 31 BS E1c Distributed Congestion Mgmt by Ag gregators 1160 BS O1 Enhanced charging 974 FTR Phase balancing 34 BS E2 Virtual Power plant 561 FTR Priority charging 1160 BS O1 Enhanced charging 1397 FTR Prolong Service Contract 1175 BS S3 B2B Contract Management 935 FTR Provide Service Contract Framework 1175 BS S3 B2B Contract Management 973 FTR Reactive power 34 BS E2 Virtual Power plant 1315 FTR Register Service 1173 BS S1 Marketplace Buying Selling Rout ing 1176 BS S4 Service provision GA MOVE FP7 265499 Green
121. ations are done by hand Variations Related informa tion 3 4 4 1320 FTR CO2 intensity of driving This feature will provide information on CO2 emissions of charging and driving Information as average CO2 level per charge fed into the vehicle will be combined with the mileage driven into an overall CO2 impact of a vehicle absolute value of CO2 emitted g CO2 km In order to support the offer of this service described above it is necessary that the carbon footprint of each charging event which is routed via the market place is captured and documented A service pro vider e g OEM Utility IT Service Provider connected to the market place can perform a carbon inten sity certification for a specific vehicle a whole fleet or specific driver s on request The realization of this feature requires e caption of the carbon intensity of the charged electricity in g CO2 kWh in the CDR e caption of the mileage of the vehicle at charging in the CDR together with the VIN vehicle identifica tion number e Access for the assigned Service Provider to the data CDR that is related to all charging events of the relevant vehicle s or driver s in order to analyze and aggregate the carbon amp vehicle related data to the overall CO2 impact of a vehicle An important issue is an agreement on the methodology of the carbon intensity of the electricity It needs to be agreed if only the power plant emissions are considered e g w
122. batteries is pro vided to the household 560 FTR V2H supply signal GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 195 of 210 Green N users or service requestors B2B eMotion Ea L VL ID Business Scenario Description Satisfied By 30 BS E1b Centralized Conges DSO centrally monitors and con 1313 FTR Allow interrupting tion Mgmt TOU tariff trols all EVSE connected through its 961 FTR DSO predefines peaks substations DSO can disconnect 1316 FTR Emergency DSO interrupts charging or modulate each EVSE to pre vent congestion on MV LV grid 31 BS E1c Distributed Conges Congestion management is per 560 FTR V2H supply signal tion Mgmt by Aggregators formed by EVSPs upon a request 1202 FTR V2G energy supply signal from a DSO through Marketplace 1317 FTR Peak shaving on LV 965 FTR Peak shaving on MV 33 BS E1d Monitoring of EVSE 967 FTR History of EVSE use 34 BS E2 Virtual Power plant Use of the aggregated flexibility of 560 FTR V2H supply signal currently charged EV batteries to 1202 FTR V2G energy supply signal offer regulating power or to trade 975 FTR Ancillary services on intra day markets 972 FTR Network congestion management 971 FTR Aggregated balancing capacity to the TSO 973 FTR Reactive power 974 FTR Phase balancing 1160 BS O1 Enhanced charging Services offered by the EVSP to end 957 FTR Road side charging 1808 FTR Find Appropriate Charge Point Battery Station 1
123. be made from multiple devices e g on board device app internet 1318 FTR Reservation of Charge Spot This feature of reserving a charge spot entails e A user uses the on board device app internet or similar devices to request a reservation of a charge spot through a service provider e The service provider validates the user request through EVSE operator or through clearing house e The service provider confirms or rejects the user request Driver will be able to make a reservation of EVSE e One time e Recurring e When available during a day week year 2 3 3 Before Charging Use Case s The details of this content are described in the following Use Case s 2 3 3 1 1510 UC Before charging Scope amp Level Goal in context Preconditions Basic end user services This use case covers the phase from identifying the need for charged EV batteries through making the charging decision planning the route to the arrival at the se lected or reserved charging location The use case describes interaction between an EV driver and a device that is con nected to a service provider The EVSP might provide its services to the EV driver based on the interaction with other service providers directly or via the Marketplace An EV driver can select a satisfactory EVSE location and find his way to it EV driver may use services such as route planning identification of available EVSE charging location reservation etc and access thes
124. ble 3 3 Page 4 of 210 Green N eMotion EG AL V 6 3 2 1617 FTR Marketplace Authentication and Authorization cesses 111 6 3 3 924 FTR Search and Select Service rrrrrrrrrnrrvnrvnnrernennrrnsennrnnrernrrensennrrssennreesesnrneesnnnresernrnessennressesenn 112 6 3 4 1447 ETR Contracting Service usce aaa potio co soba inca RN ERR ERERR REN Ro CORREA YR an RR NS e RN RR RT ERRRRERSARA 113 6 3 5 926 FTR Calliof Service e MEE 116 6 3 6 1459 FTR Aggregate Service Call Results rrnnrrrnrnonnnnnnrrrrrrnnnnnnnnrvnnnnnnnnnnnrrnnnnsnnnnnnrrnnnssnsnnnnnsnnnssssnen 118 6 3 7 1685 FTR Create Notification to Service Requester rrrrnnnnrnrnnnvvrrnnnnrrnnnnnnrrnnnnrrrnnnnrvennnnnnnnnsnrnennnnn 119 6 3 8 1622 FTR Manage Requests for new SerViCeS ccsccccessssccessseccessseecessseeceessseccesseeceessseeeesaeeeeeaeess 120 6 3 9 927 FTR Service Transaction OVervieW rrrrrrnnnnnnonnnnnrrnnnnnnennnnrrnnnnerrennnnrnnnnnseennnnnrnnenesennnnnrrnnenesenveee 124 6 3 10 935 FTR Provide Service Contract Framework cccccccesssecceesneeecseeecessneeecensueeeceeeeesseaeeeeseneeeeseneeeess 126 6 3 11 1396 FTR Define and Register Service ContraCt srmrnrnnrnrnnnnnnnnnsnrvnnnnnnrnsnnnnvnnnnsnrnnnnnnvvnnennnnnsnsnnvennnnn 127 6 3 12 931 FTR Change or Terminate Service Contract rrrrrnnnnrrrrrrnrnnnnnnrrvnrrnnnnnnnnrnrrrrsrnnannrrnnesssnnnnnnvrnnensnen 129 6 3 13 1469 FTR Suspend Resume Service Contract rrrnnrnrnnrnnn
125. ce Trigger to start a roaming charge after the transaction has been validated by the clearinghouse 4 3 6 982 FTR CLEARING Validation of contract This scenario applies when an EV driver seeks to charge at a public or semi public EVSE which might not be operated by the EV Service Provider that this driver has a contract with The clearing house checks whether existing agreements for that customer or his service provider are in place and provides an indication of what services the customer might be allowed to consume and provides that information to the EVSE which can then e g start the charging process GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 75 of 210 Green N eMotion a A The contractual data or at least a subset can be stored in the clearing house directly If an EVSE operator or EVSP is not willing to store the needed contractual information in the clearing house the CH will send a request directly to them A service to retrieve the information has to be implemented by that partner One argument for the storage of a basic sub set of contractual customer data in the clearing house is per formance The Clearing House can answer the request of the EVSE operator EVSP much faster than it would be if the clearing house has to ask the corresponding EVSP for the required data Based on that faster answer the customer gets the response of the charge point if he is allowed to charge also faster 4 3 6 1 1512 UC Start a roam
126. ces This use case covers the enhanced connect charge disconnect cycle FTR1358 with additional services Use case describes interaction between EV driver EVSE Backend and optional 3rd parties Energy trader DSO public sector Note that Identification Authentication and Authorization is a separate Use Case UC 1502 but parties may choose to implement UC 1502 within the connect charge disconnect cycle 4 3 2 4 1511 UC End a roaming charging process with Clearinghouse Scope amp Level Clearing Service This use case is an internal clearinghouse procedure serving 2 business stakeholders EVSP EVSE operator Goal in context EVSPs receive correct CDRs in order to enable billing reporting and statistics Charging via active Roaming Charging Process Successful out Charging Process successfully ends CDRs are routed correctly come come Failure to send CDR is not received and billing e Connectivity issues CDR cannot be calculated correctly e Backend issues CDR contains Wrong data is transmitted Billing e EVSP backend EVSE sistent data sent wrong data EN J B Primary actor 128 acT EVSP Backend 140 ACT Clearinghouse Main scenario Information about end of charging process is send from EVSE operator backend to clearing house in form of a CDR CDR is evaluated by clearing house and for warded to responsible EVSP backend Alternatives Related informa see Business Process Diagram 1425 Contract Clearing CDR
127. cess A Business Partner Service Provider or Service Requester makes a termination request on a Service Contract Preconditions A Service Contract between the Service Provider and the Service Requester ex ists and is selected Successful out A termination request of a Service Contract is created and the other Business come Partner is notified Failure outcome Failure Outcome Condition leading to outcome Request Form in Display of an error Business Partner filled the form not complete message completely se a D Primary actor 1355 ACT Business Partner 137 ACT Service Provider or 138 ACT Service Re quester Secondary actors Main scenario e The Business Partner fills a form for the termination request on the Service Contract e A Service Contract History Entry is created e The other Business Partner is notified Alternatives tT Variations O Related information TTT Access Role Based Authorization required Data Security Data Integrity must be guaranteed Data Confidentiality must be ensured Data Privacy Sensitive Data is only stored when needed and authorized Data Export Policy required Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market 6 3 12 2 1481 UC Confirm Service Contract Termination Goal in context A termination of a bilateral Service Contract is a two step p
128. cope amp Level Goal in context The Service Requester performs a call of a Standard Interface based Service for which he has more than one Service Contract with different Service Providers It results in service calls on all contracted Services The results of the calls will be aggregated by the marketplace and one response is returned to the Service Re quester GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 118 of 210 Preconditions Successful out come Failure outcome Primary actor Secondary actors Main scenario Alternatives Variations Related informa tion Green IN eMotion V e The Service Requester has more than one valid Service Contracts not suspended with different Service Providers e The service request is based on a Standard Interface The Service Requester receives one single result of a service call that is routed to different Service Providers Condition leading to out come Invalid e Creation of an error re The service request is not Request sponse message compatible with the Service Interface Single e Creation of an information Technical Issues Response message included in the result Error e Aggregation of the remain ing results FEE 138 ACT Service Requester 137 ACT Service Provider e The Service Requester performs a request based upon a Standard Inter face Specification to the marketplace e The marketplace routes the request to every contracted Service Provide
129. ct Business Partner 1374 UC Create Business Partner Account 1368 FTR Change Business Part ner Account 1373 UC Search and Select Business Partner 1376 UC Change Business Partner Account 1377 UC View Business Partner Account Details 1378 UC Change Business Partner Account Details 1369 FTR Activate Inactivate a Business Partner Account 1373 UC Search and Select Business Partner 1480 UC Create Service Contract Termination Request 1376 UC Change Business Partner Account 1377 UC View Business Partner Account Details 1481 UC Confirm Service Contract Termination 1379 UC Activate Business Partner Account 1380 UC Inactivate Business Partner Account Table 6 14 Core Marketplace Services Features and their Use Cases GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 110 of 210 Green N eMotion En AL V 6 3 2 1617 FTR Marketplace Authentication and Authorization The Business Partner has to authenticate against the marketplace After a successful authentication the marketplace determines his role and controls the access to resources pages etc 6 3 2 1 1619 UC Marketplace Logout Scope amp Level Core Service Goal in context A Business Partner ends a valid user session on the marketplace Preconditions Business Partner has a valid user session on the marketplace i e he is logged in Successful out The user session of the
130. ction sequence Charge Dis connection sequence Figure 9 Scope of During Charging End user perspective These basic end user services that take place during charging include the instructions on how to park and connect telematics that navigate how to switch battery trigger priority charge communication with the driver e g sms to a mobile phone when change in charging occurs alerts signals etc but also securing the minimum service level of the end user communication between the EVSP who EV driver has an SLA with and EVSE operator that provides charging services and roaming services It depends on the imple mentation whether the identification is also realized during phase or we consider it already performed by a separate use case in between the before and during charge Business to business perspective From the service providers perspective there are several useful value added services optionally avail able via a Marketplace This may include the change of the speed of charge interrupted charging provi sion of current charge information theft protection etc Marketplace context During charging services described in this chapter are not exhaustive and plentiful of similar services are expected to be offered in the future by service providers directly or through Marketplaces Currently these services satisfy Business scenarios across the Charging OEM and Energy domains through the features GA MOVE FP7 265499
131. ctric vehicles and charging equip ment 135 ACT Public Sector EU commission National government local govern ment municipalities 137 ACT Service Provider Business Partner that offers and sells EV Services on the marketplace 1579 ACT Third Party Service Provider An actor which provides access to third party data 133 ACT Vehicle Driver Human currently driving the Vehicle Table 3 6 Driving and Cross Domain Services Actors Several interactions between these actors as are illustrated in 1200 BPD Enhanced charging please re fer to Appendix B 3 3 Driving Features and Use cases The following table lists the Driving services To improve readability the Driving Features have been grouped into three categories Note that the for the three Driving groups most Use Cases support most Features many to many Group Features Use Cases Battery Life 920 FTR Battery life 1558 UC Update Charging Details Services 1278 FTR EVSE Charging capabilities 1561 UC Calculate CO2 Emission 1562 UC Report Electricity Consumption Vehicle Track 945 FTR Notification 1564 UC Show Current EV Position ing Services 944 FTR Vehicle tracking 1567 UC Call For Roadside Assistance 1568 UC Show EV Position History 1575 UC Crash Notification 1569 UC Transmit Notification 1576 UC Set Geofence Charging In 1309 FTR Charging location Mgmt 1529 UC Charging Location Mgmt frastructure 1298 FTR Parking space monitoring 1563 UC Parking Space Mon
132. cts should always declare performances from a nominal point VIEW out The EVSE achieves a load reduction to satisfy DSO request Condition leading to outcome EV data cannot There would be no chance to deliver Data properties issues jerv retrieved Seen information te fe stakehoiders information to the stakeholders pelsen OEM and EVS OEM and EVSP L 132 ACT EVSE Hl Secc ni lar av 129 ACT DSO Distribution System Operator As soon as the network congestion is detected the DSO front end towards the electricity grid and the energy market that together with the EVSE Op back ends defines the Infrastructure Management System IMS a multi owners layer in the electric mobility framework evaluates aggregated per each EVSE Op back end of interest the requested load profile allowed for EV recharging The DSO therefore forward the power profile request to the EVSE Op back ends that are in charge of distributing the electric mobility load profile over the registered EVSEs according to their own algorithm contractual constraints Once the load reduction is elaborated and distributed in a granular way within all the EVSEs the EVSE Op back end forward the load profile to the EVSEs that are currently in use in the specified load area where the DSO has de tected the network congestion The updated load profile is forwarded to the EV under the assumption that the EV is able to deal with this issue and the communication EV EVSE guar
133. cus on Business Operator Operator role the business of the marketplace The Marketplace Operator is the parent of the Marketplace Business Operator 136 ACT Marketplace Operates the platform and commu Large and Trusted ICT service provider Operator nications and manages access to and working of the marketplace GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 155 of 210 Green N eMotion LY Ed ID Actor Description Full description 1402 ACT Marketplace A special kind of the Marketplace The Marketplace Technical Operator is a Marketplace Operator with the focus on Technical Operator Operator role the technical aspects of the marketplace The Marketplace Operator is the parent of the Marketplace Technical Operator 134 ACT OEM Manufacturers of electric vehicles The ACT OEM subsumes the provision of equipment to the end users whereas and charging equipment equipment is related to an electric vehicle and eventually the charging equip ment EVSE e g for charging at home often called as wallbox Together with the provision of the vehicle sale leasing or other forms of mobility services not related to electric mobility the OEM may offer additional services in the field of naviga tion information and maintenance services This requires a communication to the vehicle depending on the connectivity options of the vehicle refer to FTR 1300 for more details and the existence of a
134. d GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 151 0f 210 Green NS EA 2 eMotion LY Data Security Data Integrity must be guaranteed Data Confidentiality must be ensured Data Privacy Sensitive Data is only stored when needed and authorized Data Export Policy required Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 152 of 210 Green I eMotion EG 2 Appendices GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 153 of 210 Green eMotion LY A Definition of Actors Ed ID Actor Description Full description 1355 ACT Business Part Abstract actor representing the ser Any party that is registered at the marketplace acts as Business Partner They can ner vice provider as well as the service act as Service Provider and or as Service Requester requester The Business Partner is the parent of all Service Providers and Service Requester 140 ACT Clearinghouse authenticates and processes con The Clearing House acts as a roaming enabler tractual and financial transactions It can collect contractual data either from the marketplace where the business partners can store their bilateral contracts or can ask the involved parties by itself Another option is that the clear
135. d ket place in be no plausibility check is made this plausibility check could tween e g prevent the outcome and a household corrected report would be generated instead pee Piman actor 136 ACT Marketplace Operator 128 ACT EVSP Electric Vehicle Service Provider or 137 ACT Service Provider authorized by 133 ACT Vehicle Driver GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 63 of 210 Green N eMotion En AL V Secondary actors 133 ACT Vehicle Driver 134 ACT OEM Main scenario e Select an EV Contract that shall be analyzed for a given period e ACT Driver authorizes EVSP or other Service Provider to perform the report and access the relevant CDRs stored in the EVSP Backend e CO2 and Energy Efficiency Report is generated by including all charging events in this period Alternatives a a Variations Related information Extended Preconditions e All charging events are routed through the market place and the generated CDRs contain the VIN the contract ID the consumed charged energy includ ing the carbon emissions g CO2 kWh and the mileage of the vehicle at the charging event Those are stored centrally in the market place The CDRs are stored in the market place and are accessible for a Service Provider that offers the service of generating a CO2 report for a given EV EV Driver Contract Service provider can request a search to the market place and receives all CDRs that contain the VIN Base
136. d acts as the access layer to charging location management 2 5 3 During Charging Use Case s The details of this content are described in the following Use Case s 2 5 3 1 1518 UC During charging Scope amp Level End user services This use case covers the enhanced connect charge disconnect cycle FTR1358 with additional services Use case describes interaction between EV driver EVSE Backend and optional 3rd parties Energy trader DSO public sector Note that Identification Authentication and Authorization is a separate Use Case UC 1502 but parties may choose to implement UC 1502 between the Before and During charging use cases Goal in context The primary goal of this use case is to acquire a sufficient EV battery state of charge Secondary goals may include use of services related to charging or battery GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 36 of 210 Green DN eMotion a AL V Preconditions EVSE operator can identify a driver and the driver can access the charge point or switch station Interoperability in place hardware as well as communication Charging is controlled by EVSE operator based on a charge profile created by a number of variables standard level agreement with customer grid constraints State of Charge etc Successful out Optional User identified and granted or denied access to Charge Point or bat come tery switch station ref 1502 UC may be implemented within the connec
137. d by a unique VIN vehicle identification number The CDRs are stored in the EVSP backend and are accessible for a Service Provider could be the EVSP as well that offers the service of generating a CO2 report for a given EV EV Driver Contract Service provider can request a search to and receives all CDRs that contain the VIN CO2 intensity is available either provided by the EVSE Operator and captured in the CDR or provided by UC 1561 The EVSP logs mileage data for every charging and stores this information in the EVSP backend e g by writing in the CDR Mileage data needs to be pro vided by the OEM Backend or directly by the EV Successful out A Report is generated that states the carbon footprint and the energy efficiency for come an individual EV for a given period e g one calendar year The carbon footprint is stated in absolute values mass of CO2 emitted within the period and on a spe cific basis CO2 emitted per km driven as well as the specific energy consumption KWh km no CO2 intensity to be discussed Availability of information of of charged en Alternative 1 no CO2 report the CO2 intensity of the ergy available available European countries in the Alternative 2 CO2 intensity of market place as precondi the electricity mix of the rele tion for Alternative 2 vant country is used charging event Too low carbon footprint and No plausibility check in outside the mar specific energy consumption if combination is performe
138. d in the contracts with its partners the possibility of helping the DSO in network safety and quality of service issues by offering a set of ancillary service amongst which phase balancing and reac tive power are the most significant ones Provisioning of ancillary services from an EVSP is guaranteed by the same require ments that have to be fulfilled to satisfy the specific conditions stated for example in Network Congestion Management and V2G capability features i e EVSP back end communicating with DSO front end smart recharge infrastructure proper regulatory framework etc A fundamental prerequisite for this feature to take place is that the regulatory framework allows that distributed generation units connected to the MT do inject power with a significant reactive content In fact nowadays most of regulators forbid injection of power under a Cos Phi of 0 9 which means embedded with an in significant amount of reactive power A communication layer is required to be established on top of the EVSEs between the EVSE Op back end the EVSP back end and the electric mobility marketplace and an direct interaction between the EVSE Op back end and the DSO front end in order to demand the bidirectional flow this feature may be a special condition of V2G capability Other services including phase balancing have similar requirements to the Reactive Power provisioning from an EVSP A communication layer has to be established on top of
139. d on these extended preconditions this use case could also cover a CO2 reporting with more than one contract for one vehicle The CDRs for a specific vehicle need to be accessible see preconditions and variations In addition the CO2 intensity needs to be reported for every charging event by the EVSE and included in the CDR together with the vehicle information VIN consumed energy mileage An important issue is an agreement on the methodology of the carbon intensity of the electricity It needs to be agreed if only the power plant emissions are consid ered e g wind electricity 0 g kWh or if the pre chain such as the hardware pro duction and fuel provision is included as well e g wind electricity 5 10 g CO2 kWh Secondly it needs to be agreed on whether only CO2 emissions are considered or if other emissions contributing to global warming e g methane are considered as well resulting in a CO2 equivalent figure Concerning the provision of the carbon intensity of the electricity provided at the charging point it is recommend that the EVSE operator has to provide this figure and include it in the CDR however the question of certification of this figure by an independent certification body needs to be discussed GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 64 of 210 Green N eMotion E E LY 5 i 4 Roaming functional domain use case model 4 1 Overview Roaming of EV related services occurs
140. e 76 of 210 Green I eMotion BG L V 4 3 6 3 1514 UC Create Customer Contract by Service Provider in Clearing House Scope amp Level Clearing Service This use case triggers the enablement of the roaming agreement with the end user for the Clearing House functionality Goal in context A Service Provider wants to initially create a contract for one of his customers and populate that information to the Clearing House in order to enable faster roaming decisions Preconditions e Marketplace is operational e Business Partner is authorized for Clearing Services and enlisted in the Market place Successful out Customer contract is created within the Clearing House come Customer contract No Contract in the Clearing e inconsistent data scheme moves House all clearing requests e backend errors have to go full round trip EE hm NNNM KE S NN 136 ACT Marketplace Operator house stores that information each time Customer contracts are created within Marketplace and the Clearing House has ac cess to them tion 4 3 7 984 FTR CLEARING Forwarding CDR A Charge Detail Record CDR is generated for each charging event that goes through the clearing house At the end of a charging process the CDR is sent from the EVSE operator backend to the clearing house The clearing house validates the CDR and transmits it to the EVSP that serves the EV driver that is related to the charging event In order to understand the process b
141. e acknowledged automatically The onboard unit of the EV is connected to a mobile network with internet connec tion Successful out The notification is received by the onboard unit of the target vehicle or the market come place and acknowledged if recommended come No response Storage and display The EV is temporarily not from EV of a warning message connected to a network The notification is sent again when an alive signal from the EV is received Missing acknowl Storage and display The driver cannot reply to the edge from EV of a warning message notification due to traffic con when the response ditions or temporary loss of time exceeded network connection Missing acknowl Some specific notifica The service is temporarily edge from Market tion require an ac offline place knowledge In these cases a warning mes sage will be displayed The notification is re peated until the ac knowledge is received 137 ACT Service Provider Marketplace GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 50 of 210 Green Dy eMotion BG V Secondary actors 143 ACT EV Electric Vehicle on board unit 134 ACT OEM on board unit 133 ACT Vehicle Driver 1579 ACT Third Party Service Provider 128 ACT EVSP Electric Vehicle Service Provider Main scenario The message is displayed to the driver of the vehicle if recommended Market to Vehicle Special types of notification have to
142. e following table lists the identified Actors in the Charging domain ID Actor Description 140 ACT Clearinghouse authenticates and processes contractual and financial transactions 129 ACT DSO Distribution system operator Provides the power connection point to the charging spot 143 ACT EV Electric Vehicle Provides access to the vehicle data 131 ACT EVSE Electric Vehicle Supply is used to exchange energy between the EV and Equipment the Grid 1406 ACT EVSE Backend Backend administrative systems of the EVSE Operator as opposed to frontend on site sys tems that communicate directly with EV s 132 ACT EVSE Operator in charge of managing the EVSEs 128 ACT EVSP Electric Vehicle Service Pro offers e mobility services to the end customers vider 1594 ACT Fleet manager Organization that manages a fleet of EV s 1407 ACT EVSP Backend Backend administrative systems of the EVSP 1540 ACT HMI Human Machine Interface interface allowing the vehicle user to receive in formation relative to the charging process and provide input to the charging system 136 ACT Marketplace Operator Operates the platform and communications and manages access to and working of the market place 134 ACT OEM Manufacturers of electric vehicles and charging equipment 135 ACT Public sector EU commission National government local gov ernment municipalities 1541 ACT SECC Supply Equipment Commu implements the communication to one or multiple nication
143. e interface HMI 1811 FTR EVSE Service Control 565 FTR Charge point selection 957 FTR Road side charging 1808 FTR Find Appropriate Charge Point Battery Station 970 FTR Consumption monitoring 1812 FTR EVSE Service Monitoring 566 FTR Cross sale 562 FTR Low priority charging 1702 FTR Charging monitoring 558 FTR Increase the load of charging 950 FTR Charging as guest 979 FTR Authentication of user GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 193 of 210 Green Dy eMotion Ea L LY ID Business Scenario Description Satisfied By 1180 BS C1b Semi public charging charging from a common AC supply and designated parking areas e g shopping centers airports offices 1808 FTR Find Appropriate Charge Point Battery Station 970 FTR Consumption monitoring 951 FTR Charging report 1812 FTR EVSE Service Monitoring 566 FTR Cross sale 562 FTR Low priority charging 558 FTR Increase the load of charging 1358 FTR Connect Charge Disconnect 1702 FTR Charging monitoring 979 FTR Authentication of user 557 FTR Reduce load of charging 960 FTR Charging and battery switching status notification 1809 FTR EVSE Service Access 1277 FTR Phone roaming 1701 FTR Open access to EVSE 976 FTR Charging management 953 FTR Human machine interface HMI 563 FTR User identification 1318 FTR Reservation of Charge Spot 1811 FTR EVSE Service Control 565 FTR Charge point selection 957 FTR Road side ch
144. e marketplace 5 3 6 971 FTR Aggregated balancing capacity GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 93 of 210 Green N eMotion Ea An EVSP acting as aggregator in the energy market will be able to offer energy from the batteries of the EVs used by its customers that are connected to the recharging infrastructure in a certain timeslot Obvi ously the customer acceptance is required and V2G availability must be stated in the contract between the EVSP and its customer and there shall also be a B2B pre agreement between the EVSP and the energy buyers Generally speaking an EVSP while acting as aggregator sees energy vendors as final customers due to the possibility of offering in the energy market a certain amount of energy retrieved from the EVs This activity will be constrained by regulatory framework in each country Where the energy market is run according to an unbundling rule the selling of energy from EVs will be exclusively towards energy vendors Otherwise if the regulatory framework does not foresee constraints for selling and buying energy the EVSP could also offer the energy itself to either the Distribution System Operator DSO or Transmission System Operator TSO as a balancing service for its grid or to Energy Suppliers to manage their Energy Balance The recharging infrastructure is connected to the LV grid and any load variation on the recharging infra structure will impact the LV grid the DSO is r
145. e publishing of the Service e In case of a new version of the Service a change of all Service Contracts has to be performed GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 135 of 210 Green N eMotion E AL V e The Marketplace Technical Operator enables or disables the Service in the Service Catalogue e The Service Provider is notified Alternatives ee ee Variations 0000000000000 Related informa tion Access Role Based Authorization required Data Security Data Integrity must be guaranteed Data Confidentiality must be ensured Data Privacy Sensitive Data is only stored when needed and authorized Data Export Policy required Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market 6 3 14 4 1489 UC Upload Service Specification Goal in context During the service registration the Service Provider uploads the service specifica tion i e Service Interface e g WSDL and Service Description of the offered Service A Service is selected Successful out The Service Interface e g WSDL and the Service is uploaded to the marketplace come Failure outcomes Failure Outcome Condition leading to outcome Validation Error Display of an error The formal validation of the Service esses E failed O 137 ACT Service Provider Secondary actor Main scenario The Se
146. e services through a compatible on board interface telematics mobile app phone call to a customer service center or similar with a service provider An on board interface to a service provider The service provider provides own services or services of other service provid ers via the marketplace or bilateral agreements with these service providers The services are delivered to the EV driver through interaction between EV driver and on board device that is connected to an EVSP This may require the GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 23 of 210 Green N eMotion a AL V EVSP and an EVSE operator or marketplace to interact with each other The provider may provide a service through access to certain information about the driver and the EV e g user ID contract information EVSE and car charging capabilities car position etc This information can be retrieved from various ac tors car driver EVSP and EVSE operator The user is confronted with updated information e g on charge prices or charge spot availabilit Successful out Select between recharging options AC chargers DC chargers or battery switch come station that are compatible and can be filtered by user s current location desti nation and a preferred route Check availability of charge spots prices and optimized suggestions based on user s profile Apply eco routing Arrive at the EVSE location Search failure User is not able to iden Technical err
147. eMotion WP 3 Deliverable 3 3 Page 202 of 210 Green Dy eMotion V Feature Satisfies ing registration life cycle mgmt 1318 FTR Reservation of Charge Spot 1793 GRP Services Before Charging 1180 BS C1b Semi public charging 1181 BS C1c Public charging 1804 FTR Roaming based on Bi lateral Agree ments 1161 BS R1 Contractual clearing 986 FTR Roaming in different countries 1161 BS R1 Contractual clearing 985 FTR Roaming in same country 1161 BS R1 Contractual clearing 924 FTR Search and Select Service 1173 ing 1174 BS S2 Service Detail Records for Account ing and Billing 1176 BS S4 Service provision ing registration life cycle mgmt 1175 BS S3 B2B Contract Management BS S1 Marketplace Buying Selling Rout 1446 FTR Search and Select Standard Inter faces 1177 BS S5 Linking of Systems Standardization of Interfaces Messages 978 FTR Search for charge point or battery switch station 1356 BS O4 Basic charging 927 FTR Service Transaction overview 1174 BS S2 Service Detail Records for Account ing and Billing 1173 BS S1 Marketplace Buying Selling Rout ing 564 FTR SLA 1182 BS R3a Differentiation of customer con tracts SLA check 1469 FTR Suspend Resume Service Contract 1173 BS S1 Marketplace Buying Selling Rout ing 1177 BS S5 Linking of Systems Standardization of Interfaces Messages 1175 BS
148. earch for a trip using several means and combinations of transportation e g EV and train e Fleet management overview and management of EV fleet including analysis and real time moni toring e CO2 intensity reporting of CO2 on aggregated levels 3 2 Actors The following table lists the identified Actors in the Driving and Cross domain Services ID Actor Description 129 ACT DSO Distribution system op Provides the power connection point to the charging erator spot 1595 ACT Emergency Service Center Emergency Service Center 143 ACT EV Electric Vehicle Provides access to the vehicle data 131 ACT EVSE Electric Vehicle Sup is used to exchange energy between the EV and the ply Equipment Grid 1406 ACT EVSE Backend Backend administrative systems of the EVSE Opera tor as opposed to frontend on site systems that com municate directly with EV s 132 ACT EVSE Operator in charge of managing the EVSEs 128 ACT EVSP Electric Vehicle Ser offers e mobility services to the end customers vice Provider GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 41 of 210 Green NS ER 7 eMotion M VL ID Actor Description 1594 ACT Fleet manager Organization that manages a fleet of EV s 136 ACT Marketplace Operator Operates the platform and communications and man ages access to and working of the marketplace 134 ACT OEM Manufacturers of ele
149. easeesessueeeescessseseeesaeesens 172 1363 BPD B2B Partner Management Create Business Partner Account srnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnrnns 173 1371 BPD B2B Partner Management Change Business Partner Account 174 1382 BPD B2B Partner Management Activate Business Partner ACCOUNT rnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnns 175 1403 BPD B2B Partner Management Inactivate Business Partner Account snnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnns 176 1186 BPD Centralized Congestion Manageme nt ccccccccccsssssssscecceessssssseeecccesesesasseesceessessaseeeseeseeseaaeauaeenees 177 1198 BPD Congestion Management through TOU Tariffs cccccccsssccccsssceesseeceessseccessseeeesseeeeessseecessseeeesens 178 1199 BPD Distributed Congestion Management rnnnnrnnnnnnnnnnnnnrvnnnnnnnnnnnrrnnssnnnnnnnnrsnnsnsnennnnnsnnsssnsnnnnnnsnnnnsnnsssnnn 179 1200 BPD Enhanced Charging scscssasssscssasccacssoegdsasscasesadendessawesacsyacatacdsaawanstevecsoasasaseedsddeaseabwuaedaassndacsndsadadenaves eases 180 C Use Case Illustrations ssccccicccsccscssecetscceceescenseccsonstscsseesccescencesssieccsdevecesevexseceisecestesescedscdecesdsausevesenceccssesreses 181 GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 5 of 210 D Use Cases in Chapters icc cccdiccewscesssccteccecceecsicdceseccceesecasdacseccuseadhseciued duueesvevesstwc nscawesestesdGctdcessdecestecsceuss 187 E Business Scenario s and their Feature
150. ect if the CP is blocked by any car The EVSE is equipped with a HMI to allow request of the Parking only mode and to signalize the response e g i GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 54 of 210 Green Dy eMotion BG V The parking lot must be owned by the EVSE Operator Successful out The HMI signalizes that the EV driver is allowed to use the selected CP for Park come ing only by the EVSE backend The EV driver will be billed for parking for the whole parking time independent from aie ang Ve via FOuteome EVSP Failure outcomes Outcome _ Condition leading to outcome O B Parking The mode Parking The CP is proposed for charging NE allowed only for the selected CP only currently is not allowed red light EV driver is not Usage of CP is not al e EV driver is not authorized to allowed to use lowed red light use a CP of this EVSE CP e The CP is reserved for an other EV driver E M SS ACT Vena Primary actor 133 ACT Vehicle Driver 1406 ACT EVSE Operator Backend 128 ACT EVSP Electric Vehicle Service Provider Main scenario e The EV driver authenticates at the EVSE via the HMI of the CP e EV driver selects the Parking only mode e EV driver waits until the HMI signalizes the permission to use the Park only mode for the occupied CP e EV driver stops the parking session by using the HMI of the CP before leaving the CP with the EV EV driver will be billed fo
151. ection to the central rupted database The collected The uploaded data is marked Defective sensor readings data is incon as invalid and will be removed Transmission problems sistent con if requested tains errors No connection e Display of a warning mes The requested EV is not con to vehicle sage nected to an EVSE e Nocharging data will be transferred Secondary actors 128 ACT EVSP Electric Vehicle Service Provider 1579 ACT Third Party Service Provider 143 ACT EV Electric Vehicle 134 ACT OEM Main scenario The data upload is initiated with the beginning of the charging process The charging data SoC state of charge time voltage time V total capacity temperature time optional humidity time optional number of current charging cycle type of charge fast slow charge current time A plus the local timestamp mileage and position is packed and submitted to the marketplace Reports based on this data are provided GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 43 of 210 Green Dy eMotion BG V a For more information please refer to Figure 28 Update Charging Details in the Ap pendix EMEN o MP D hV EVSE has acknowledged the connection of the requested EV Related informa The sensor data of the charging device and the supply equipment will be used for tion reporting purposes and for optimization of charging cycles and electric energy dis tribution
152. ects grid constraints and intervenes in order to ensure supply to pre vent serious overloads or even blackouts only applicable in case of emer gency high priority e Intervention directly DSO sends signal to all affected EVSE Alternatives Intervention indirectly DSO sends signal with location information to all EVSE operators acting in the affected area Variations Related informa tion Issues Costumer s acceptance Contradicting interests between retailers e mobility providers and DSO s 5 3 10 961 FTR DSO predefines peaks Within the MV LV energy distribution domain the peak energy available per load area is one of the de sign parameters for the substations and grid reinforcements maintenance It is within the DSO responsi bility to foresee or evaluate from historical analysis the expected peak energy statistics per hour and day month in order to minimize shortages of energy supplying and fulfilling quality of services rules set by each national authority According to the DSO analysis a threshold is set at every LV location which may have a wide variety of energy loads beneath A smart recharging infrastructure is needed in order to accomplish peak modula tion coming from the DSO because a fast and secure communication layer has to be established between the points of delivery and some sort of EVSE back end which will be communicating either with the mar ketplace or with the DSO front end directly Once the
153. ed Scalability capable to grow with electro mobility market 6 3 8 6 1627 UC Delete Request for a new Service Request for a new Service is selected Request for a new Service is deleted Failure outcomes Failure Outcome GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 123 0f 210 Green I eMotion En AL V gt hw A 138 ACT Service Requester Secondaryactor S O Main scenario e The Service Requester requests the deletion of his own Request e The Request for a new Service is deleted in the system Alternatives Variations EES Related information Access Role Based Authorization required Data Privacy Data Export Policy required Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market 6 3 9 927 FTR Service Transaction overview Any Business Partner can obtain an overview of his own Service Transactions The Business Partner requesting the overview must play an original or delegated role in the transaction buyer seller debtor creditor There may be certain selection criteria e Date range selection e Filters on each of the roles buyer seller debtor creditor e Filters on the magnitude of the Transaction Value may already be part of the Service filters 6 3 9 1 1239 UC Search and Select Services This Use Case is listed before in th
154. ed in the local grid by drawing power from the batteries or interrupting load This service will increase the quality of power in the grid and the DSO will reward the EVSP aggregator for provision of this service Also reducing the imbalance on phases on the LV substation is another example of use case of an ancillary service Load switching from different phases will provide phase balancing to the grid that will reduce the losses on the distribution wires Phase balancing will reduce losses in the distribution grid DSO will reward the EVSP based on the savings it can reach by the reduction of losses The injection of reactive power coming from a distrib uted generation unit such as an EVSE into the grid makes possible to reduce the amount of reactive power on the transmission lines re phasing the MT grid and this is another example of ancillary service which may be enrolled here All 973 974 and 975 features can be deployed through this single use case Other examples of ancillary services are scheduling and dispatch reactive power and voltage control loss compensation load following system protection energy imbalance 5 3 5 2 1604 UC Vehicle to grid signal This Use Case is listed before in this Chapter please refer to paragraph 5 3 2 1 Value added service This use case enables the DSO or other energy stakeholders to distribute the need for congestion management to multiple service providers through th
155. eds Variations The EVSE could eventually decide not to load the current EV charge data is unre liable for a timely recharge The EV could do the same as well Related informa This use case shows the chance of having current EV charge data which can be tion used to supply real time services or to accomplish marketing purposes 5 3 12 1202 FTR V2G energy supply signal An EVSP acting as aggregator in the energy market will be able to offer energy from the batteries of the EVs used by its customers that are connected to the recharging infrastructure in a certain timeslot Obvi ously the customer acceptance is required and a V2G availability must be stated in the contract between the EVSP and its customer and there shall also be a B2B pre agreement between the EVSP and the energy buyers Generally speaking an EVSP while acting as aggregator sees energy vendors as final customers due to the possibility of offering in the energy market a certain amount of energy retrieved from the EVs This activity will be constrained by regulatory framework in each country Where the energy market is run according to an unbundling rule the selling of energy from EVs will be exclusively towards energy vendors Otherwise if the regulatory framework does not foresee constraints for selling and buying energy the EVSP could also offer the energy itself to either the Distribution System Operator DSO or Transmission System Operator TSO as a balancing service f
156. eg ERA Ta pra Sia ESEE a apa b ado 115 6 3 44 1484 UC View Service Details roi eb era thi sp tu RE RAE SERRE ROSE Eo ERE DR AREE P do ERE kao na pagado 115 6 3 4 5 1478 UC Download Service Content ararannnnnnnarnnnnnnrnarnennenenennrnnnenennennnenenvensarensarensanensarensanenrareensavenee 115 6 3 5 1 1491 UC Create Service Transaction iei sinas iere a aho eiae P Re ERR Ree sinirde kaasarin iis ERR FUR drake 116 6 3 5 2 J241 UC Call Of Service kassa GOTT Te 117 6 3 5 3 1245 UC Search and Select Service Contracts sessi einen nnne nnne tnter neret 117 6 3 6 1 1492 UC Aggregate Service Call RESUItS ccssccccccssssssssccccsssessssseesecsseenaseesccsseesssseeesecssesssseeeceeseeseeeeees 118 6 3 7 1 1687 UC Notify Service Requesters of own Service o ccsssccesessscceesscccsessccesessscesssssceesssecesessseceessseessasees 120 GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 189 of 210 Green N eMotion Ea FA V 6 3 8 1 1625 UC Create Request for a new Service ccccssssccesssscccessceceessssccesssecsessecesessecseesaseceessseeesseseessseeeees 120 6 3 8 2 1623 UC View Details of Requests of new Services essent 121 6 3 8 3 1629 UC Create Response on Requests for new Services ssccccessscceessscceesssceeessesccessasccesssscesesssesessaseees 122 6 3 8 4 1620 UC Search and Select Requests for new Services sess eee 122 6 3 8 5 1626 UC Change Request for a new SCLViC
157. enalties may apply for EVSP s which fail to deliver on their peak load commit ments towards the DSO or the balancing responsible party Incentives may be provided on the energy bill for end customers providing poten tial balancing power regardless of it being used I This use case exploits the possibility of using V2G capability in order to aggregate energy and provide balancing to other energy actors e g DSO or TSO Energy Vendor 5 3 7 965 FTR Peak shaving on MV Under the assumption that network congestion management and V2G energy supply signal features hy pothesis are satisfied an advanced solution for dealing with congestion issues would be using the V2G availability published from the EVSPs in order to simultaneously impact positively with a dynamic energy disposal on the grid by sharpening the load peaks in an adaptive way It is the DSO that decides whether or not to deploy such a congestion management policy after having evaluated the energy availability aggregated per load area from the various EVSPs in order to ensure that switching an amount of cars into V2G can surely trigger peak shaving The goal of peak shaving using V2G capability is to guarantee the energy provisioning to all the loads connected to the grid without deploying cut off load management strategies under a congestion situation thus letting the DSO to re route the surplus of power gathered from EVSPs DSO will aim to reduce peaks on the MV level by
158. eptability In the next releases of the Marketplace however it is expected that new services and transactions will emerge and numerous variations of the current D3 3 requirements will occur 1 1 Division of requirements into functional domains One of the main values of Green Emotion is the combination of multiple perspectives on e mobility This involves not only the different regional perspectives within Europe but also the perspectives from differ ent stakeholders as was recognized clearly in deliverable D3 1 The key objective of Work Package 3 and as such this deliverable is to develop and implement a European marketplace that enables clearing houses and service providers to interact and do business and to develop and implement interfaces to support these B2B business relations A European wide market place and clearinghouses do not yet ex ist The purpose of Work Package 3 is both to develop and implement such solutions but also to demon strate regional ongoing and upcoming implementations of marketplaces clearinghouses service provid ers etc Both objectives are equally important This deliverable is reflecting the development implementa tion and demonstration plans at regional as well as European level For release 1 of the Marketplace the WP3 sub teams accommodated this by distinguishing four Func tional Domains for developing the requirements IBM formed four working groups each involving multiple stakeholders but led by a part
159. equired Data Privacy Sensitive Data is only stored when needed and authorized Data Export Policy required Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market 6 3 8 4 1620 UC Search and Select Requests for new Services Scope amp Level Goal in context Find Requests for new Services that satisfy search criteria The searching actor is a representative of the Business Partner of the market place or a Marketplace Operator Successful out The Business Partner receives a list of Requests for new Services that meet his come search criteria and is able to select one or more Requests from the list for further activities Failure outcome Failure Outcome Condition leading to outcome No Requests for new Display of a warning There are no requests that meet Services is found message the search criteria _ ae 1355 ACT Business Partner Secondary actors 136 ACT Marketplace Operator Business or Technical Main scenario e The Business Partner fills the search criteria or load search criteria saved before e The marketplace returns a list of Requests for new Services that meet the search criteria e The Business Partner stores optionally the entered search criteria for later GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 122 of 210 Green NI eMotion BG V Eoo Use ooo
160. er 133 ACT Vehicle Driver Main scenario A crash situation is identified by vehicle sensors A high priority notification is sent to the market place this includes the current position of the vehicle The market place forwards the information this includes a phone number to an emergency service center GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 49 of 210 Green Dy eMotion Ea L V The emergency service center contacts the driver if possible to get more infor mation about the current situation The emergency service center initiates the rescue based on all collected infor mation Alternatives O The driver may activate the crash notification by himself Related informa An emergency service center is contacted automatically They can initiate a call tion back to investigate the emergency situation This critical service is always sup ported by a third party service provider For illustration of this use case please refer to Figure 27 Send Notification V2M and Figure 26 Send Notification M2V in Appendix C 3 3 4 5 1569 UC Transmit Notification Scope amp Level Basic end user service Scenario O2c Send a notification between the marketplace and the EV Goal in context A notification is sent from the marketplace to the onboard unit of the requested EV or the other way round The message is transmitted to the driver of the vehicle if recommended and can be acknowledged Notifications to the market place ar
161. er email sms or similar The reservation function can be supported from different end user customer de vices e Smart Phone e g iPhone Android e Internet Customer Portal e In Car application e g onboard unit Goal in context EV driver is able to reserve a selected EVSE through available interfaces for a desired period of time E g driver wants to reserve a charging point in advance in order to charge the EV This enables extended range journeys with increased con fidence Preconditions EVSE has a communication to a backend system e g Charging Management System or Infrastructure management system IMS EVSE has a unique ID grid ID EVSE master data e g plug type phases address are available EVSE master data entails an option to allow reservation EV driver is supported by an EVSP with an application that entails an option to reserve Successful out Reservation of an EVSE come Failure outcomes Failure Outcome Condition leading to outcome Noreservation of an EVSE The EV driver can t reserve an EVSE gt hm 9 gt AJ 128 ACT EVSP Electric Vehicle Service Provider 131 ACT EVSE Electric Vehicle Supply Equipment Main scenario Entering of search criteria e g address Show result of search criteria that information about selected charging points and availability for reservation Reservation of EVSE optional payment process Confirmation of reservation Related inform
162. er to simultaneously impact positively with a dynamic energy disposal on the grid by sharpening the load peaks in an adaptive way 5 3 9 1313 FTR Allow interrupting DSO and EVSE are in a contractual relationship which allows the DSO to send congestion signals to a particular EVSE operator in order to e interrupt charging e reduce the throughput of the CP 5 3 9 1 1572 UC Reduce Charge Power by DSO S DSO instructs EVSE Operator to reduce the electrical power drawn from the Grid DSO and EVSE are in a contractual relationship which allows the DSO to send congestion signals to a particular EVSE operator in order to interrupt charging reduce the throughput of the CP DSO aware about congestion in particular part of the grid online observation forecast Capability for DSO to communicate send signal to dedicated e g grouped by grid section EVSE or EVSE operators obligation to forward signal to EVSE active in respective grid section GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 98 of 210 Green I eMotion BG AL Successful out e EVSE interrupts charging or reduces charging power reaction of the EV on come EVSE s request e Prevention of congestion blackout come ward signal Communication failure Primary actor 131 ACT EVSE Electric Vehicle Supply Equipment 129 ACT DSO Distribution system operator 132 ACT EVSE Operator Secondary actors 143 ACT EV Electric Vehicle Main scenario e DSO det
163. erent service providers The results of the service calls can be aggregated by the marketplace to return one single result to the service requester The last functional component partner management covers the registration of a business partner as well as changing his data or activating inactivating the business partner As a result of the Usability workshops the methodology of which is described earlier in this deliverable see Introduction the following Task case map was created by the workshop participants This approach is used in the GeM project to validate the requirements features documented in the RCC Tool Manage Manage contract framework account Managing account Placing Publishing Request Viewing details Comparing offers Closing Contract Register Registration on the marketplace Service Requester R e g Salesman ACT 138 Offer service Blackboard for open requests Manage contracts Manage Managing own request contracts Managing Requests Figure 21 Task Cases for Core Marketplace Services GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 107 of 210 Green N Ra 7 eMotion LY 6 2 Actors The actors in the core marketplace services are part of a hierarchy as shown in the following figure ACT Marketplace Operator ACT Business Partner BusinessActor TechnicalActor ACT S ice Pi id ACT Marketplace Business Operator A
164. ervice 1443 FTR Enable Disable Service 1521 UC Status for cars can be main 1301 FTR Fleet management tained by Fleet Manager 1490 UC Suspend Resume Service 1469 FTR Suspend Resume Service Contract Contract by Service Requester 1574 UC Third Party Information 1296 FTR Third party information 1569 UC Transmit Notification 945 FTR Notification 1558 UC Update Charging Details 920 FTR Battery life 1812 FTR EVSE Service Monitoring 1488 UC Upload Service Content 1315 FTR Register Service 940 FTR Version Service 1489 UC Upload Service Specification 1445 FTR Define new Standard Interface 1315 FTR Register Service 940 FTR Version Service 1525 UC User wants travel and has 1303 FTR Intermodality planning specific requirements 1520 UC Users can book pool cars 1301 FTR Fleet management online 1303 FTR Intermodality planning 1604 UC Vehicle to grid signal 1202 FTR V2G energy supply signal 974 FTR Phase balancing 560 FTR V2H supply signal 975 FTR Ancillary services 972 FTR Network congestion management 971 FTR Aggregated balancing capacity 973 FTR Reactive power 1377 UC View Business Partner Ac 1366 FTR Create Business Partner Account count Details 1369 FTR Activate Inactivate a Business Partner Ac count 1368 FTR Change Business Partner Account 1623 UC View Details of Requests of 1622 FTR Manage Requests for new Services new Services 1479 UC View Service Contract Details 931 FTR Change or Terminate Service Contract 1396 FTR
165. es Related information Role Based Authorization required Data Security Data Integrity must be guaranteed Data Confidentiality must be ensured Data Privacy Sensitive Data is only stored when needed and authorized Data Export Policy required Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market 6 3 21 7 1380 UC Deactivate Business Partner Account Scope amp Level Goal in context The account of a Business Partner is inactivated at the marketplace Business Partner is registered and activated at the marketplace come em tame O meom O Co outeome to outcome Request not e Display of an error message Request Form is complete e Cancellation of the change re not filled correctly quest Deactivation not e Notification Business Partner accomplished e Cancellation of the deactivation has active service request contracts at the marketplace FEN Primary actor Primary actor 1355 ACT Business Partner Secondary actor 1367 ACT Marketplace Business Operator Main scenario e Deactivation Request Form filled and submitted by a representative of the Business Partner e Check of his Service Contracts e Deactivation of the Business Partner in the system by the Marketplace Business Manager e Notification of the Business Partner Related informa tion Issues Access Role Based Authorization require
166. es which should support a fleet manager in fulfilling his daily work Basic features can be e managing EVs managing sites and charge points car bookings managing user authorizations charge point reservations billing statistics amp reporting car information vehicle tracking aka car location car maintenance 3 4 3 1 1522 UC Assign car to scenario Scope amp Level Value Added Service Cars can be assigned to various scenarios Goal in context Cars can be assigned to various scenarios which affect availability of the car a scenario can for example be executive use only which restricts booking to execu tives only or maintenance which would indicate that the car is being maintained or in need of maintenance and cannot be booked at all Preconditions Pool cars available system is available Fleet Manager is in place Cars communi cate at least their Status of charge and the vehicle identification number Successful out Availability of the pool car is restricted to certain groups only The Fleet Mgr can come improve availability for certain groups of users by assigning cars to scenarios GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 59 of 210 Car can t be No scenario based car treatments Feature not available assigned to a are possible Backend problems scenario Connection problems ME 1594 ACT Fleetmanager EEE EEE EEE a a Secondary actors Main scenario Related informa tion 3
167. eseesasssecesseseaesseesaassssees 91 5 3 4 1 1605 UC Reserve and activate ancillary services ueessesississeeee seen nnnn nnne nnn hannes nnn 91 5 3 4 2 1604 UC Vehicle to grid signal cccsssssccccccsssessnscsccccssesssseesecsseensseescccsesesssesesceseseeassaececseecaeeeestaaseasees 92 5 3 5 1 1605 UC Reserve and activate ancillary services eessssisesseeese eese nnn nnns nnne nra nnns 93 5 3 5 2 1604 UC Vehicle to grid signal cccesssssccccccsseessnccecccsesesssscesecssecsuseescecssessssssseceseseesssaecesseeseaeeseesaseasees 93 5 3 6 1 1604 UC Vehicle to grid signal cccesssssccccceseessssccescesesesssscesecssesususeescecseseassssscesesessssaecesseeeaeseeetsassesees 94 5 3 6 2 1601 UC provide balancing CAOPACIY cccccceesssscccccesssesssssescccssesuseeescesssecsseeescesesensussescecseeeeasasesssaaeesees 95 5 3 7 1 1597 UC Peak Shaving se eterne re eaae evan s Fe Heu e ye dea Eel eue FER 4 FERT Fuge o EN RENE RR TR ARR EVER ER dd 96 5 3 8 1 1597 UC Peak sh Vihg etre heo ea xe are ve ek ved eene ense o nave el geo cuu Re d Yun ERE AR 98 5 3 9 1 1572 UC Reduce Charge Power by DSO rrrrannnnrrnrnnnnnnnnnnrnnnrrnnnnnnnrnnressnnnnnnnrrnnsnsssnnnnrnnrrssnnnnnnnnrnrerssnnsa adea 98 5 3 10 1 1597 UC UH deiude 100 5 3 10 2 1596 UC Peak load threshold on a substation esses nne 100 5 3 11 1 1524 UC Fleet manager monitors energy c
168. esponsible for the quality and safety of this LV grid and is therefore always involved in any EV related load management including V2G The TSO s responsibility is not affected as long as the V2G load variations stay below a certain threshold Thus V2G can pragmati cally achieve a small scale penetration in the electricity market by offering limited amounts of power to DSO s only To be able to offer V2G balancing capacity to the market Energy Suppliers in future also TSO the fol lowing additional mechanisms must be in place e To manage the LV grid the DSO will retrieve all relevant status and charging information of the re charging infrastructure from the EVSE Operators This includes the infrastructure s generic V2G ca pabilities and the available V2G power for specific time slots vehicle connection windows e When an EVSP wants to provide V2G energy he will offer an amount of kWh based on the status of his connected V2G capable EV s and specify this to the relevant DSO s e The DSO s match the EVSP s kWh offering with the connection data from the EVSE Operator to de termine where and how the EVSP s power offering will enter each DSO s LV Grid e Each DSO considers the relevant part of the offering taking into account Network quality safety and historical load profile analysis The DSO then decides to allow or deny this part of the EVSP s energy offering onto the market e Once the partial offerings are allowed onto the market
169. essful out Customer contract is updated within the Clearing House come Failure outcomes Failure Outcome Condition leading to outcome be changed e backend errors ENS hw AJ O bp B D L Eg 140 ACT Clearinghouse kull ing house stored the changes each time access to them Related informa 4 3 9 5 1517 UC Change Customer Contract by Customer himself within Clearing House Scope amp Level Clearing Service End user is enabled to directly make changes to his roaming agreement or EVSP contract and this will be automatically recorded in the clearing house Goal in context The customer who has already a contract with an EVSP which is stored in the Clearing House wants to change some contract detail which he is allowed to change Preconditions e Customer contract already exists in Clearing House e Marketplace is operational e Business Partner Customer is authorized for Clearing Services and has ac GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 81 of 210 Green DN eMotion BG V cesstothe Marketplace come KNE M EHE MN be changed e backend errors A EE EEE Secondary actors 136 ACT Marketplace Operator asp 128 ACT EVSP Electric Vehicle Service Provider 140 ACT Clearinghouse stores the changes each time Customer contracts are changed within Marketplace and the Clearing House has access to them Related informa t
170. essseeseeesaaees 47 3 3 4 3 1568 UC Show EV Position HIStOLY ccccccccccssessssccscccsssesssssescccsensssasceccecsseesasessecsessssssesceseeesaaeescuaasaasees 48 3 3 4 4 1575 UC Crash Notification cccccccccscccccsssccceesssccsesscscesssesccssseeceessseceessseceesseseesessecseassccsesssceesceessseeesasees 49 3 3 4 5 1569 UC Transmit NOtificAtion cccccccccsssccccesscccsessssccssssecesscecsessecessseceessssceesssccsesasscesseeceseaseasaseestasees 50 3 3 46 1576 UC Set GEOLENCE ix i ose seth odes oves eve ny euer el code heiet ae 51 3 3 6 1 1529 UC Charging Location MANAGCIMENL ssssccccccsseessssscscccsseesssscsscessesssesseeseccseeesssaeseeceseeensasessesensees 52 3 3 6 2 1563 UC Parking Space Monitoring ccccccccccessssscccccsssessacesccessessssssescccssensasseesceseseesssaeseccesensssessasaseeees 53 3 3 6 3 1557 UC Parking Space Management rrnnrannnnrrrnnnnsannnnrrrnsrnsnnnnnrrrnrrrnnrnnnnnrrrrrrrrnannnrrrnrrrsenennnrnnrsssssnan annen 54 3 4 1 1 1548 UC Access Car INfOFMAtiOn cccccccesscccsesscccsesscsecessssccssseceesssecsesseccessesceesssesseesseececssseeeeseeseceesasees 57 3 4 2 1 1520 UC Users can book pool cars online ccsssssscccccssseesssseccccseussssseesccssseesaesesceseseesssessccseeesssaaseessseuees 58 3 4 2 2 1525 UC User wants to travel and has specific requirements sessi eene eerte rnt 58 3 4 2 3 1548 UC Access Car Information ccccccccssccccessccceesssscessssecceseeecessseccesse
171. etplace Operator Business or Technical Main scenario e The Business Partner fills the search criteria or load search criteria saved before e The marketplace returns a list of Services that meet the search criteria e The Business Partner stores optionally the entered search criteria for later use Alternatives Variations Related informa tion Access Role Based Authorization required Availability 24 7 availability required Performance sub second response time for Marketplace Transactions GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 112 of 210 Green I eMotion En AL V Scalability capable to grow with electro mobility market 6 3 3 2 1484 UC View Service Details Scope amp Level Goal in context View the details of a selected Service Preconditions e The actor is a representative of the Business Partner of the marketplace or the Marketplace Operator e A Service is selected Successful out The Business Partner receives a view of the details of the Service come e Service Interface e Service Description e Downloadable Content Manual etc e Service Contract Offering or existing Service Contracts to outcome w 1355 ACT Business Partner Secondary actors 136 ACT Marketplace Operator Business or Technical The Business Partner chooses the details view of a Service The detail view is displayed Related informa tion Role Based Authorization required Availability 2
172. etter have a look at the business process diagram Contractual Clearing CDR Forwarding 1452 4 3 7 1 1511 UC End a roaming charging process with Clearinghouse This Use Case is listed before in this Chapter please refer to paragraph 4 3 2 4 Scope amp Level Clearing Service This use case is an internal clearinghouse procedure serving 2 business stakeholders EVSP EVSE operator It has no functional effect on the end user 4 3 8 1291 FTR CLEARING Managing EVSP data GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 77 of 210 Green DN eMotion BG L V This feature manages the EVSP data That means that EVSP can only register its customers if the EVSP itself is registered as such in the clearing house For the EVSP it is mandatory to state its roaming part ners Also the standard CRUD create read update delete operations have to be in place 4 3 8 1 1500 UC Change EVSP EVSE Contract within Clearing House Scope amp Level Clearing Service This use case is an internal clearinghouse procedure serving 2 business stakeholders EVSP EVSE operator It has no functional effect on the end user Goal in context Change an EVSP EVSE operator contract within the Clearing House in order to keep in sync with contractual changes Preconditions e Contract already exists in Clearing House e Marketplace is operational e Business Partner is authorized for Clearing Services and enlisted in the Market place Successful out
173. f power in the grid and the DSO will reward the EVSP aggre gator for provision of this service Also reducing the imbalance on phases on the LV substation is another example of use case of an ancillary service Load switch ing from different phases will provide phase balancing to the grid that will reduce the losses on the distribution wires Phase balancing will reduce losses in the dis tribution grid DSO will reward the EVSP based on the savings it can reach by the reduction of losses The injection of reactive power coming from a distributed gen eration unit such as an EVSE into the grid makes possible to reduce the amount of reactive power on the transmission lines re phasing the MT grid and this is an other example of ancillary service which may be enrolled here All 973 974 and 975 features can be deployed through this single use case Other examples of ancillary services are scheduling and dispatch reactive power and voltage control loss compensation load following system protection energy imbalance 5 3 4 2 1604 UC Vehicle to grid signal This Use Case is listed before in this Chapter please refer to paragraph 5 3 2 1 Value added service This use case enables the DSO or other energy stakeholders to distribute the need for congestion management to multiple service providers through the marketplace 5 3 5 975 FTR Ancillary services An EVSP offers aggregated flexible load as ancillary service to t
174. file to the EVSE that migrates it to the EVSE Op back end The EVSE Op back end finally aggregates the updated power profiles gathered from the EVSEs and makes available this update to the DSO as a fulfillment of its initial request Use cases that realize this Feature are also illustrated in Appendix B for more please refer to 1186 BPD Centralized Congestion Management and 1198 BPD Congestion Management through TOU Tariffs 5 3 2 1 1604 UC Vehicle to grid signal Scope amp Level Value added service This use case enables the DSO or other energy stakeholders to distribute the need for congestion management to multiple service providers through the marketplace Goal in context An EVSP acting as aggregator in the energy market offers energy to DSO This en ergy is retrieved from the batteries of the EVs that are connected to the recharging infrastructure in a certain timeslot The EVSP could also be not directly acting as ag gregator but in connection with it together with other EVSPs In order to deploy this use case the V2G supply signaling should be accomplished following this use case Preconditions The EVSE Operator is connected to the marketplace through its backend The EVSP is connected to the marketplace through its backend The DSO is connected to the marketplace through its frontend towards the grid The EVSP states in its contracts with the customers that the average time of recharge is sensitive to the network safety is
175. g scenario in the case of Better Place 950 FTR Charging as guest Allow guests to charge their EV at home charger 1702 FTR Charging monitoring This feature comprises the EV drivers ability to monitor different aspects of the charge process while it is connected to an EVSE e g state of charge time left to by fully recharged etc The EV driver can consume the service through various interfaces apps website on board device etc Charging monitoring can be facilitated in various ways One way is through a mobile connection between the EV s on board device and EVSP back end system 1357 FTR Charge data collection e Uploading charge data from EVSE to fulfill the processing OEM EVSP e Type of data harvested ID SLA Car capabilities CO2 951 FTR Charging report The end customer receives charging report through app sms or on board unit after charging informing on latest energy consumption 976 FTR Charging management The feature allows control ofcharging Who is in control of managing the charging depends on the business model In some cases the charging will be controlled by the user in some cases by a service provider and in some cases a combination This feature involves the most basic charging man agement characteristics e Increase load e Decrease load 1299 FTR Charge point management This component is needed as a sub service of charging location management It allows status monitoring and charge point reservation an
176. h the DSO or the marketplace where the dedicated service is running The EVSE is in communication with the DSO either directly if the DSO is the EVSE Operator or indirectly if the EVSE Operator is another actor and therefore the DSO front end is not owned by the same actor of the EVSE Op back end and receives periodic updates on peaks disposal Outcome Condition leading to outcome EVSE cannot The EV will recharge re The EVSE is not endorsed accept prede gardless of the forecasts with communication capabili fined peaks done by the DSO on net ties work safety and quality of The EVSE is installed but service not connected to its back GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 100 of 210 Green s E 2 eMotion V end and through that made available as a manageable point of delivery for the DSO network safety and quality of service issues EVSP provides The EV will recharge re The EVSP is forced to guar anominalser gardless of the forecasts antee recharge time as vice to its cus done by the DSO on net stated in the contract for a tomers work safety and quality of pre settled energy disposal service at the EVSE The EVSP contract does not foresee network safety and EVSE Op priority issues over EVSEs as constraints for service provisioning RENE EEE HERES 132 ACT EVSE Operator 128 ACT EVSP Electric Vehicle Service Provider 129 ACT DSO Distribution system operator According to t
177. hapter 3 describing both geographic roaming between coun tries and roaming between EVSPs Roaming is based upon contractual clearing services performed by a Clearinghouse in this context a third party application accessible through the GeM Marketplace In the first release the Clearinghouse provides roaming authorization services only A future Clearinghouse may also provide Financial Clearing supporting efficient financial and billing operations for EV The Roaming Domain chapter contains separate sections for each of its main Features The Energy Domain is described in Chapter 5 and covers mainly business to business value added ser vices for which the grid operator is the main beneficiary The dominant scenario is centralized congestion GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 12 of 210 Green N eMotion Ea management as performed by Enel in Italy a service that may instantaneously reduce the amount of power that is drawn from the electricity grid to prevent outage Other services in this domain involve using aggregated and controllable EVSE load and V2G to provide ancillary services or regulating power to the TSO The chapter is divided into sections by Features as realized by scenarios no further grouping into sub chapters is applied The Marketplace Domain is described in Chapter 6 This is the only domain defining Core services the technical enablement to the business services described in Chapters 2 3 4 and
178. he DSO analysis a threshold is set at every LV location which may have a wide variety of energy loads beneath Once the peaks are identified per load area the DSO can update requests for curtailment on the marketplace set ting the constraints for energy provisioning in the load area in which the EVSEs are encompassed It is up to the EVSE Operator to decide whether or not to dis tribute this constraint within all the EVSEs installed in that area or eventually cut off just a few of them When the customer approaches the EVSE he is well aware that time of recharge will be due to network safety and EVSE Op priorities over peak disposal within its installed EVSEs in that area The EVSE without communication capabilities towards an EVSE Op back end could not interact with the DSO peak predefinitions In that case the EVSE will continue its dumb charging regardless any forecast historical analysis and haz ards would eventually emerge for higher EV penetration in the market This use case refers to making EVs as a possible tool for managing the LV grid in a safe and reliable way through a communication layer and a smart recharging infrastructure avoiding network reinforcements and eventually leading to sustain ing higher volumes of renewables production towards EU 202020 targets 5 3 11 966 FTR Current EV charge The overview of current EV charge is meaningful information that an EVSP acting as Service Provider in the marketplace can use
179. he DSO in order to help the DSO to fulfill the distribution rules established by the regulation framework in which it operates In example frequency and voltage will be adjusted in the local grid by drawing power from the batteries or increasing or de creasing power load This service will increase the quality of power in the grid and the DSO will reward the EVSP aggregator for provision of this service Other examples of ancillary services are e Scheduling and dispatch e reactive power and voltage control e loss compensation GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 92 of 210 eMotion Green on EG 2 e load following e System protection e energy imbalance Provisioning of ancillary services from an EVSP is guaranteed by the same requirements that have to be fulfilled to satisfy the specific conditions stated for example in Network Congestion Management and V2G capability features i e EVSP back end communicating with DSO front end smart recharge infrastruc ture proper regulatory framework etc 5 3 5 1 1605 UC Reserve and activate ancillary services This Use Case is listed before in this Chapter please refer to paragraph 5 3 3 1 Value Added service Scenario E2 An EVSP offers aggregated flexible load as ancillary service to the DSO in order to help the DSO to fulfill the distribution rules established by the regulation frame work in which it operates In example frequency and voltage will be adjust
180. iders may view or download the Standard Interface specification e g WSDL and the corre sponding documentation for use of the development of their own services 6 3 17 1 1476 UC View Standard Interface Details This Use Case is listed before in this Chapter please refer to paragraph 6 3 14 8 Scope amp Level Core Service View Standard Interfaces details 6 3 17 2 1475 UC Search and Select Standard Interface This Use Case is listed before in this Chapter please refer to paragraph 6 3 14 9 Scope amp Level Core Service Find Standard Interfaces that satisfy search criteria 6 3 17 3 1487 UC Download Service Specification This Use Case is listed before in this Chapter please refer to paragraph 6 3 4 2 Scope amp Level Core Service The Service Requester downloads the service specification 6 3 18 1445 FTR Define new Standard Interface Business Partner may propose a new Standard Interface e The proposed interface has to be reviewed by the GeM Marketplace and optionally by additional Business Partners e After acceptance the new Standard Interface will be published in the Standard Interface Cata logue 6 3 18 1 1257 UC Propose new Standard Interface Core Service Goal in context A Business Partner Service Provider or Service Requester can propose a Service Interface Specification as a Standard Interface The proposed Standard Interface has to be reviewed and accepted by the Marketplace Technical Operator GA MOVE FP
181. ight combination of the two or similar signal from the EVSE indicates that ca ble and car is now connected properly and that charging may occur e User is authorized or not for charging If not the charging is interrupted and the user is notified e The charging will now be executed according to charge plan Effectively this means that charging may or may not continue immediately depending on dictated charge plan e User disconnects car from charge point 956 FTR Battery switching Facility offering customers battery switching services e Acustomer identifies himself with RFID or alternative user identification e The telematics system instructs the user to park the car correctly in the switch station e Upon correctly parking an automated process takes over the car positioning washing and battery switching e The telematics system informs the user when the automated switch process is over and the car can be removed from the switch station GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 34 of 210 Green N eMotion EG AL V 1701 FTR Open access to EVSE This feature comprises the service of an EVSE operator offering EV drivers access to charging services without being a customer of the particular EVSE operator or being supported by a roaming agreement This could be e EV drivers with a contract with an EVSP that does not involve roaming services from the particular EVSE operator or e EV drivers that do not have an EVSP c
182. ilarly to other ancillary services to the DSO The DSO evaluates whether or not such an offer of aggregated power is valuable to increase the quality of service in a specific load area by matching with the capability of bidirectional flow of energy of the EVSEs involved Alternatives The EVSP may not be directly linked to the DSO front end but simply publish its offer ings into a dedicated service on the marketplace that can be eventually accessed from the DSO through its front end after having filtered information according to load area and pricing criteria Related informa This use case shows the chance of using energy stored in the EVs as a prosumer tion platform for energy to be eventually fed into the LV grid It is hereby pictured how an cillary services may be managed by the different actors in the marketplace Issues Regulation 5 3 3 2 1604 UC Vehicle to grid signal This Use Case is listed before in this Chapter please refer to paragraph5 3 2 1 Scope amp Level Value added service This use case enables the DSO or other energy stakeholders to distribute the need for congestion management to multiple service providers through the marketplace 5 3 4 974 FTR Phase balancing EVSP offers aggregated flexible load to the DSO to be used to reduce the imbalance on phases on the LV substation Load switching from different phases will provide phase balancing to the grid that will re duce the losses on the distribution wi
183. in order to deliver benefits to its customers and sell or support services for oth ers business actors in the electric mobility market A requirement for this use case to take place is that there is a specific field which describes the status of charge embedded within the communication data exchanged between EV and EVSE 18015118 currently under development is compliant with this hy pothesis In order to deliver this information from the real time charging process to the marketplace and GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 101 of 210 Green N EG 7 eMotion V make it available for other actors service requestors it is also needed that the status of charge is propa gated from the EVSE to the EVSE Operator back end EVSP back end system Hence it is eventually elaborated i e threshold triggered aggregation of a relevant number of status charge details per area and thus propagated to the marketplace by updating the content of the service placed there Other actors in the market may act as Service Requestors and access the Current EV charge information made available from a specific EVSP and match this with their needs For example this service could be used from a TSO or an Energy Vendor according to the regulatory framework in order to monitor the power eventually available after the network safety and quality preconditioning made by the DSO This service could also be used for marketing purposes by OEMs in order
184. ind electricity 0 g kWh or if the pre chain such as the hardware production and fuel provision is included as well e g wind electricity 5 10 g Requirements are subject to implementation and may vary from the hereby suggested procedure GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 62 of 210 Green Dy eMotion Ea L CO2 kWh Secondly it needs to be agreed if only CO2 emissions are considered or if other emissions contributing to global warming e g methane are considered as well resulting in a CO2 equivalent figure Concerning the provision of the carbon intensity of the electricity provided at the charging point it is rec ommend that the EVSE operator has to provide this figure and include it in the CDR however the ques tion of certification of this figure by an independent certification body needs to be discussed 3 4 4 1 1592 UC CO2 Reporting Scope amp Level Reduction of carbon emission is a major political goal for electric mobility This Use Case will provide information on CO2 emissions of charging and driving in order to allow a monitoring of fleets Information as average CO2 level per charge fed into the vehicle will be combined with the mileage driven into an overall CO2 impact of a vehicle absolute value of CO2 emitted g CO2 km and the en ergy efficiency in kWh km driven Preconditions The EV or the EV Driver needs to have a contract with the EVSP unique con tract ID The EV can be identifie
185. ing charging process with Clearinghouse This Use Case is listed before in this Chapter please refer to paragraph 4 3 2 1 Scope amp Level Clearing Service Trigger to start a roaming charge after the transaction has been validated by the clearinghouse 4 3 6 2 1497 UC Create EVSP EVSE Contract within Clearing House Scope amp Level Clearing Service This use case is an internal clearinghouse procedure serving 2 business stakeholders EVSP EVSE operator It has no functional effect on the end user Non functional improvement is the increased speed of data processing Goal in context Create an EVSP EVSE operator contract within the Clearing House in order to en able faster roaming decisions Marketplace is operational e e Business Partner is authorized for Clearing Services and enlisted in the Market Successful out Contract is created within the Clearing House place come A nu ne come Contract cannot be No Contract in the Clearing e inconsistent data scheme created House all clearing requests e backend errors have to go full round trip Primary actor 131 ACT EVSE Electric Vehicle Supply Equipment 128 ACT EVSP Electric Vehicle Service Provider 140 ACT Clearinghouse clearing house clearing house stores information locally have to go full round trip each time Contracts are created within Marketplace and the Clearing House has access to them tion GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Pag
186. ing house stores a subset of contract information in its own database It forwards the CDR to the corresponding EVSP of a customer who has charged at a foreign location The clearing house does the authentication of charging requests when it is asked by the EVSE operator 129 ACT DSO Distribu Provides the power connection point Is responsible for the voltage stability in the distribution grid MV LV grid tion system opera to the charging spot Is in charge of providing the energy metering to other market actors i e EVSP tor TSO EVSE Op unless there is another actor doing this i e Metering Point Opera tor 1595 ACT Emergency Emergency Service Center Emergency Service Center Service Center 130 ACT Energy retailer Delivers electricity to the charging N A spot 143 ACT EV Electric Provides access to the vehicle data The EV has no direct access to the marketplace only through the systems of an Vehicle EVSP e g OEM 1539 ACT EVCC Electric embedded system within the vehi N A Vehicle Communi cation Controller cle that implements the communi cation between the vehicle and the SECC in order to support specific functions GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 154 of 210 Green eMotion LY Ed ID Actor Description Full description 131 ACT EVSE Electric Is used to exchange energy between Conductors including the phase s neutral and pro
187. ion GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 82 of 210 5 Energy functional domain use case model 5 1 Overview The energy functional domain consists of one main business scenario which is based on the idea of a centralized grid congestion management leveraging the smart metering backbone for conventional energy market and smart recharging infrastructure for brand new electric mobility market as deployed for example by Enel in Italy This scenario is based on the basics of remote grid management with the possibilities to enhance func tionalities through the electric mobility infrastructures and exploit new services and opportunities in the smart grid market of which electric mobility is the very first operative example The scenarios that may be embedded in this functional domain are depicted on the graph below Optional functions of the electric mobility marketplace would include services that operate within this domain pro viding congestion management eventually together with the use of the aggregator role and aggregated energy trading services referred as Virtual Power Plant VPP ENERGY Scenario Centralized VPP energy Aggregator congestion 66 8 trade and grid services management retail services Figure 18 Structure of the Energy Domain 5 1 1 End user perspective From the End user perspective the main Features services that have developed from these scenarios are History of the EVSE u
188. ion VY 1371 BPD B2B Partner Management Change Business Partner Account e Partner Contract and Service Contracts can be changed eiet MIN D Service Contract GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 174 of 210 Green N 3 2 eMotion LY 1382 BPD B2B Partner Management Activate Business Partner Account D Partner Contract GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 175 of 210 Green NI Ea 2 eMotion A 1403 BPD B2B Partner Management Inactivate Business Partner Account O O Rejected Service Contract Inactivation Cancellation Q Notify Business Partner y i 1 H v i inacitvated or fullfilled Partner Object Service Contracts Ener BR 56 05 The Marketplace can trigger an Bi Ss oe an Account Inactivation pi dike upp paler e Inactivation of Service Reject Inactivation Contract requested 3 3 GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 176 of 210 G ig eMotion E ft LY 1186 BPD Centralized Congestion Management o a 3 zz a Define Restriction amp Business Logic is most likely 5 Peer implemented in DMS 2 ec e t v a o 2 e TM Includes status z increase and H decrease E Congestion Warning frise qa A Status Change H 2 JV Select Charging Points Foo Prioritization of Charging Points or FE and EVSP Operators amp
189. ional domains eese eese nnn ntn e nra e anseres na 12 1 2 Methodology Structured Requirements MANAGCMEN ccsseesssccscccseesssssccecccssessaseeescessestuseesccesseensaees 13 1 3 Methodology Usability engineering method sessi seie esee eene ntes nns s es rane nennen 15 1 4 How tore d this document EE 17 2 Charging functional domain use case moOdel aransnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnne 18 2 1 ou T 18 2 2 p n M 20 2 3 End user services before CHALGIING 1cccsseccceessscceesssscesssssecsssccsessescesseeecesssecesssseesessseceesasseceeeesseeeenseseeees 21 2 3 1 Before Charging Overview cccccccssscccessseccessseecessseecessseecessseecesseeeccesseeessasecceasesesesseceessaeeeseeessaeeees 21 2 3 2 Before Charging Feature Content ssiri ect EE e oed ae Fe EV aves GI EH eE aa iasa AEE 22 2 3 3 Before Charging Use Case S ccccssccccssscceessseccessseeeessseccessuececeseeecesseeeesaseecenseeceeaseecessaeeeeceseaeeees 23 2 4 Identification and authorization of EV user eese eene enne rns eats ra seats ra sss aa nsi nas 29 2 4 1 Identification and authorization Overview esssseessseeeeeeee enne nnne nnne nnn enne nn 29 2 4 2 Identification and authorization Content nennen enne nennen inneren nnn
190. is Chapter please refer to paragraph 6 3 3 1 Scope amp Level Core Service Find Services that satisfy search criteria 6 3 9 2 1471 UC View Service Transaction Details Scope amp Level Core Service Goal in context View the details of a Service Transaction Preconditions e The actor is a representative of the Business Partner of the marketplace or the Marketplace Business Operator e A Service that the Business Partner provides or uses is selected Successful out The Business Partner views the details of an own Service come Failure outcome Failure Outcome Condition leading to outcome Primary actor 1355 ACT Business Partner GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 124 of 210 Green N eMotion BG V Secondary actors 1367 ACT Marketplace Business Operator Main scenario e The Business Partner chooses the details view of a Service that it pro vides or uses e The detail view is displayed Alternatives Variations The Marketplace Business Operator is able to view the details of all Service Transactions Related informa tion Issues Access Role Based Authorization required Data Privacy Sensitive Data is only stored when needed and authorized Data Export Policy required Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobilit
191. is Use Case is listed before in this Chapter please refer to paragraph 6 3 21 4 Scope amp Level Core Service View details of a Business Partner 6 3 21 5 1481 UC Confirm Service Contract Termination This Use Case is listed before in this Chapter please refer to 6 3 12 2 Scope amp Level Core Service A termination of a bilateral Service Contract is a two step process A Business Partner Service Provider or Service Requester accepts or rejects a termination request on a Service Contract made by the other Business Partner 6 3 21 6 1379 UC Activate Business Partner Account Scope amp Level Core Service Goal in context The account of a Business Partner is activated Business Partner is registered and inactivated at the marketplace Successful out The Business Partner is activated in the system at his request come ENDE vv moon to outcome eompee c Cacelatomchine rivalen request not ied coneciy complete e Cancellation of the activation request not filled correctly l IET GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 150 of 210 Green N eMotion EA AL V 1355 ACT Business Partner Secondary actor 1367 ACT Marketplace Business Operator Main scenario e Activation Request Form filled and submitted by a representative of the Business Partner e Activation of the Business Partner in the system by the Marketplace Busi ness Manager Notification of the Business Partner Alternativ
192. itoring Management 1297 FTR Parking space management 1574 UC Third Party Information Services 1557 UC Parking Space Management Table 3 7 Driving services Features and their Use Cases 3 3 1 Battery life services Feature content This feature group comprises the following content 920 FTR Battery life This feature comprises use cases related to the reporting on the battery use 1278 FTR EVSE Charging capabilities This feature comprises information of an EVSE s charging capabilities in order to display only compatible EVSE options to the driver GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 42 of 210 Green Dy eMotion BG L V The information should reflect the EVSE s charging capabilities e AC charging e DC charging e Battery swapping Tasks in the feature e Define a format for infrastructure capabilities e Define APIs to retrieve infrastructure capabilities 3 3 2 Battery life services Use cases 3 3 2 1 1558 UC Update Charging Details Value added service Transmission of charging information Goal in context The detailed charging information is transferred to the market place database Preconditions The EV is connected to the supply equipment and ready to transfer the collected data The EVSE is connected to a network and the central marketplace come O 7 nm come The transfer of Cancellation of the data up Network connection problem data is inter load Lost conn
193. lected while charging and at the end of charging and transferred to the EVSP of the EV driver either directly or through a clearinghouse Alternatives IxRMNEC CENE GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 45 of 210 Green N eMotion En AL V Variations Other output formats like Excel or PDF documents should be provided too The consumption of electricity may also be evaluated if the vehicle has been charged at a home EVSE car port Charging services can be bought and sold in a number of variations Reporting consumption in kWh is just one model another could be parking connection time a third could be one fee This completely depends of the business model adopted by business partners Related informa tion Issues Is the usage of a home smart meter provided 3 3 3 Vehicle tracking Feature content This feature group comprises the following content 945 FTR Notification Use cases in this feature will notify through the marketplace in case of one of the following events e Theft Alert Notification e Roadside Assistance 944 FTR Vehicle tracking This feature will comprise information from the vehicle tracking The use cases will utilize the tracking data in following Automatic Crash Notification Manual Crash Notification Vehicle Tracking Geo fencing Speed Alert 3 3 4 Vehicle tracking Use cases 3 3 4 1 1564 UC Show Current EV Position Preconditions The requested
194. ll partners four WP3 working groups were formed each addressing one functional domain Charging Roaming Energy and Marketplace The current deliverable is based upon the same Domain structure The Use Cases are the most comprehensive descriptions of single business sub processes they effec tively specify how a feature will be realized For some groups of Use Cases the coherence and interac tions are illustrated by a Use Case Diagram These diagrams are particularly useful for the system archi GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 14 of 210 eMotion Green on EI 7 tects during the detailed specification phase of the Marketplace Where applicable any Non functional requirements such as security performance and scalability are documented together with the use case Generic Non functional requirements have also been documented separately in the RRC tool The following picture illustrates the requirements gathering and the links between the artifacts of the meta model Business Process Is illustrated by Business Is constrained by i e lossary Te Diagram Scenario Business Rul Glossary Term UU USES Can be referenced NM 7 in every artifact Is satisfidd by satisfies Business Object Feature considers Is realized by Be Non Functional du cm by Requirements Workflow diagram Use Case Diagram i Is linked to Use S d oe Case specifications considers Is illustrated by Use Case Actor
195. load area is one of the fundamental design parameters for the substa tions and grid reinforcements maintenance DSO defines thresholds peaks on each substation It is within the DSO responsi bility to foresee or evaluate from historical analysis the expected peak energy sta tistics per hour and or day month in order to minimize shortages of energy sup plying and fulfilling quality of services rules set by each national regulatory frame work The EVSE Op is connected to the marketplace through its back end The EVSP is connected to the marketplace through its back end The DSO is connected to the marketplace through its front end towards the grid The EVSP states in its contracts with the customers that the average time of recharge is sensitive to the network safety issues peaks management from the DSO and eventually to charging points priority issues coming from the deployment strategy of the EVSE Operator A smart recharging infrastructure is needed in order to accomplish peak pre definition demands coming from the DSO to the EVSE Op An adequate communication capability should be endorsed in the EV in order to receive modulation orders from the DSO through the EVSE energy gate way especially for low power and time consuming recharges e g 3 3 kW The EVSEs are in communication with an EVSE Op back end that aggre gates data from each EVSEs The EVSEs Op back end aggregates data from each EVSEs and is able to perform communication wit
196. location service provider and is not requesting the EV for a current position Issues 11 Privacy of end user data possibly regulated by local legislation 3 3 4 4 1575 UC Crash Notification Scope amp Level Basic end user service Send an automatic crash notification to the marketplace Goal in context Automatic or manual notification of a crash Preconditions The EV can use a mobile connection to the central service The crash incident is identified by the car sensors automatically Successful out The crash notification is sent and acknowledged The information is forwarded to an come emergency service center Failure outcome Condition leading to out come No mobile net e Display of an error message There is temporarily no ac work connection e The notification is stored tive mobile network connec available tion The sending device is dam aged The transmission Display of an error message The mobile network connec of the notification The notification is stored tion is interrupted is interrupted and will be sent again when the connection is reestab lished The request is Display of an error message The central service is tem not acknowl The request is stored and porarily not available edged will be sent again after a de fined period of time Primary actor Secondary actors 137 ACT Service Provider on the marketplace 1595 ACT Emergency Service Center 128 ACT EVSP Electric Vehicle Service Provid
197. m wide balance of the electricity system As part of this task the TSO runs the balancing market In doing so the TSO is an intermediary be tween market parties causing imbalance and parties able to deliver the flexibility to solve this imbalance situation The TSO contacts balancing capacity reserves from producers which are paid for through system services and activates them in real time However the TSO may seek for more cost efficient resources by sending real time price signals to EcoGrid consumers In that case the TSO would be taking the Real time market operator RTMO role and the prices sent to EcoGrid consumers will be based on the need for up or down regulation due to occurring imbalance be tween production and consumption and or restrictions in the transmission system GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 158 of 210 Green Dy eMotion Ea V B Business Process Diagrams e 1270 BPD Contractual Clearing Authorization 1452 BPD Contractual Clearing CDR Forwarding 1441 BPD General Selling Buying Process 1456 BPD Use of Services 1431 BPD Contracting Service 1495 BPD Service Detail Records for Accounting and Billing 1410 BPD Define and Register Service Contract Offering 1426 BPD Change or terminate a Service Contract 1427 BPD Prolong Service Contract 1428 BPD Enable Disable Service permanently 1387 BPD Service Registration 1429 BPD Delete Service 1271 BPD Propose Standa
198. manager 128 EVSP Electric Vehicle Service Provider 1579 ACT Third Party Service Provider Routing Service Provider GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 51 of 210 Green N eMotion BG AL Main scenario e Seta geofence for a specified list of EV e This information is used to initiate automatic geofence notifications by the Lo cation Service Provider o predefined notifications for the driver if the vehicle enters or leaves a specified area o warnings for the EVSP if a vehicle leaves a parking position theft Alternatives ee ee Variations A limited number of geofences could be sent to the vehicle directly to enable local warning messages if the vehicle has no continuous mobile network connection This service could be combined with routing services Related information It is possible to offer this functionality as an additional service to the user of the car The driver may want to be notified if he enters or leaves a user defined area 3 3 5 Charging infrastructure management Feature content This feature group comprises the following content 1309 FTR Charging location management A charging location is a site with charging points usually run by EVSE Operators Every charging location needs a management component that enables site monitoring controlling and communication with the marketplace This component also makes customer authentication requests to the clearinghouse 1298 FTR Parki
199. marketplace where the dedi cated service is running Failure outcomes Condition leading to outcome FEE EVSP cannot use The EV driver does not allow Absence of V2G condi EV for V2G feed energy from his EV to the tion in the contract grid EV data cannot be There would be no chance to Data properties issues retrieved deliver such information to the between OEM and stakeholders EVSP Prii 128 ACT EVSP Electric Vehicle Service Provider y actor 132 ACT EVSE Operator GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 95 of 210 Green N EI eMotion V The EVSP collects and aggregates relevant information regarding the V2G from each connected EVSE Op Also information may be accessed through EVSP that make it available This does not mean that information is published twice but underlines that different actors EVSP and EVSE Op may have the right of delivering it according to the regulatory framework Information about power injection availability over the LV grid is passed from the EVSP to the DSO The DSO matches this data with data from the EVSE operator in order to iden tify where the available power is located in the LV grid The DSO allows or denies the EVSP s energy offering inside its load area The potential buyer Energy supplier in future also TSO can then decide if it wants to use the balancing service from the EVSP This may include aggregat ing the offerings from several DSOs P
200. n nsns nnn nnne na nnns 160 1452 BPD Contractual Clearing CDR Forwarding rrrvrnnonnnnnnrrrvnrrononnnnnrrnnnrnnnnnnnnrrnnnsnnnnnnnnrnnnssnsnnnnnnsnnnrnnnsssnnn 161 1441 BPD General Selling Buying Process sess enne nnne ennnnnnn nnne nn rnnt assises sese r natns nsns 162 1456 BPD USE Of Services eerie teet ise eaaa E ERE MER EET EXE A Ra a eR aia SR FEES ARRAS NEUE ORE ROSE RR RR ERES 163 1431 BPD Contracting Service mumier c tt emu e nx Em po e eaaa Ex eR aU ear sa aa aaa aiSia Eai EFE Pe os euge kunnet 164 1495 BPD Service Detail Records for Accounting and Billing 165 1410 BPD Define and Register Service Contract OffEriNG ccccccsssccccesscccesssescessseeccesseeceesssecesseceessseaeeeens 166 1426 BPD Change or terminate a Service Contract eeessssssssssseeeeeee eene nennen nnns sss r nn rins nnns 167 1427 BPD Prolong Service Contract cccecccsssccccecesessseececeeesessseeeeeeceeessaseeeeeesessessseeeeeeseeeeesaeeseeeseeeeesesesasaeeeens 168 1428 BPD Enable Disable Service permanently cccccscccssecesssecssecessccessecsssecesseesstecsseseseccsseeesesesesensateceanens 169 1387 BPD Service ReglstratlOn i dcn reor ctio eei Ere tao a EA AEAEE bea EEREER ER FEBR EDS BER o RE Roa Fa RE enu 170 1429 BPD Delete Service cos 171 1271 BPD Propose Standard Interface ccccccccssssccssssescessseccessseeecesseeecsseeceessseccessseec
201. never network congestion within a load area is either forecasted or real time de tected according to the technology used to monitor the energy distribution grid EVSEs offer a service to support the DSO which can operate selectively The EVSE Operator is connected to the marketplace through its back end The EVSP is connected to the marketplace through its back end GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 87 of 210 Green Ss E 7 eMotion LY The DSO is connected to the marketplace through its front end towards the grid The EVSP states in its contracts with the customers that the average time of recharge is sensitive to the network safety issues peaks management from the DSO and eventually to charging points priority issues coming from the deployment strategy of the EVSE Operator A smart recharging infrastructure is needed in order to accomplish peak pre definition demands coming from the DSO to the EVSE Operator An adequate communication capability should be endorsed in the EV in order to receive modulation orders from the DSO through the EVSE energy gate way especially for low power and time consuming recharges e g 3 3 kW The EVSEs are in communication with an EVSE Operator Backend that ag gregates data from each EVSE The EVSEs Operator Backend aggregates data from each EVSE and is able to perform communication with the DSO or the marketplace where the dedi cated service is running Service contra
202. ng space monitoring This feature allows the monitoring of parking space usage data for requesting parties like EVSP or public authorities 1297 FTR Parking space management This feature deals with the usage of charging points as parking space only 3 3 6 Charging infrastructure management Use cases 3 3 6 1 1529 UC Charging Location Management Scope amp Level Basic end user service The Management of Charging Infrastructure e g Charge point EVSE Basis for the use case is that the Charging spot master data e g CP ID address technical data are registered within the Charging Location Management The EVSE Op will monitor the charging session with the following functionality e actual status e g free charging maintenance of the EVSE e actual consumption of the EVSE Session e actual status of charging spot environment e g Fl LS switch panel e Alarms from the Charging Spot GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 52 of 210 Green Dy eMotion Ea V The EVSE Op will control the charging spots with the following functionality e Reboot of Charging Spot e Switching e g FI LS e Start End of Charging Session e SW Update per remote connection Configuration management monitoring can be done by a context menu tree map and list The Charging Location Management application need interfaces to the following applications to support the authentication of e vehicle end
203. nnectivity issues ass 128 ACT EVSP Electric Vehicle Service Provider 136 ACT Marketplace Operator Main scenario EVSP sends information about deletion of a customer contract to clearing house clearing house deactivates the customer contract Alternatives pe E a E Ol Variations Related informa tion Customer contracts cannot be deleted completely They only should be deactivated in order to prevent history data loss 4 3 9 3 1514 UC Create Customer Contract by Service Provider in Clearing House This Use Case is listed before in this Chapter please refer to paragraph 4 3 6 3 GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 80 of 210 Green N eMotion BG L V Scope amp Level Clearing Service BS Contractual Clearing This use case triggers the enablement of the roaming agreement with the end user for the Clearing House functionality 4 3 9 8 1515 UC Change Customer Contract by Service Provider in Clearing House Scope amp Level Clearing Service This use case allows the service provider to make changes to the customer contract in the clearing house Use case represents no functional changes to the end user Goal in context Service Provider changes customer contract details which are stored in the Clearing House Preconditions e Customer contract already exists in Clearing House e Marketplace is operational e Business Partner is authorized for Clearing Services and enlisted in the Market place Succ
204. nrnenvnrnnvrrenvrrnnvenenvnrnnverenvnsnnrerenvesnvnsesnrsnnnnsene 133 6 3 17 1315 FIR Register SERVICE os uoi sedere tere e svat evi nena nu eoe eda ci alder eirik gage Ue 134 6 3 15 1443 FTR Enable Disable Service rrnnssvrennrnnvrnnnsvvrnnnnnvrensnnvrnnnsnvvennsnvrenssnsvrnnsssvrnnssnvrenssnnrvessnsve svenn 139 6 3 16 940 FIR Version SEVICE areri sadinar iieiea er yr Re rre RR eee ev bue eR EAA exu e e edes Ri 141 6 3 17 1446 FTR Search and Select Standard Interfaces srrrsnreranvrnnnvensnvnnnvrrrnvrernvrrnsvrssnvensnnnsenversnressnvenen 143 6 3 18 1445 FTR Define new Standard Interface srnranrrnanvrnnnvrnenvrnenvenenvrnsnvensnnnsnnrsssnnssnnrsennsssnsesennnssnvesenn 143 6 3 19 1366 FTR Create Business Partner Account rrrnnnnnnonnnnrrnnnnnnnnnnnnnrnnnnnnnennnnnrnnennsennnnnrrnnnneesnennnrrnnnessee 145 6 3 20 1368 FTR Change Business Partner ACCOUNL ccccccccssssseeccesssssssseeeececeeessaseeeceeseeeasseeeeeeeeessaaeeess 147 6 3 21 1369 FTR Activate Inactivate a Business Partner Account ssrvnnnsnvvnnnnnvrnnnnnvvnnnsrvnnsnnvrenssnsvvessnvrenssne 149 AD PONGICES A een 153 A Definition of Pe to o CERE Rm 154 B Business Process Diagrams isisssseccsecccssscsssscesseccccseadessdassencodenssaeccoscecussersesessencecbesarsesersecnnceassceensssencesss 159 1270 BPD Contractual Clearing Authorization seeeseseeesssseseseeeeee eene eene nn nnnnnn
205. o end their mutual relation the marketplace can send an update to the clearing house clearing house disables the specific contract 1 7 MENNENNNNNNNNNNNRN tion EN prevent history data loss 4 3 8 4 1497 UC Create EVSP EVSE Contract within Clearing House This Use Case is listed before in this Chapter please refer to paragraph 4 3 6 2 Scope amp Level Clearing Service This use case is an internal clearinghouse procedure serving 2 business stakeholders EVSP EVSE operator It has no functional effect on the end user Non functional improvement is the increased speed of data processing 4 3 9 983 FTR CLEARING Managing customer data In order to enable high performance clearing requests a white list concept for customer charging authori zation is introduced within the clearing house Anonymous customer data references can be managed directly within the scope of the clearing house The EVSPs can store such B2C data directly in the clearing house By doing this the clearing house can accept or reject roaming charging requests directly without having to trigger external systems each time This keeps the round trip time as low as possible The load is taken off the EVSP Backend in that case GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 79 of 210 Green DN eMotion BG V and EVSPs can advertise a fast start of roaming charging processes To see the process in detail have a look at the business process diagram
206. o the producer will need to pay for those imbalances 1693 Production BRP It is responsible for keeping the schedule sent to the TSO for all its producer portfo lio and if not it is responsible for paying the resulting imbalances GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 157 of 210 Green N eMotion Ed Actor Description Full description 1690 Retailer The retailer supplies consumers with electricity To that end it buys electricity in the wholesale market and sells it to consumers In addition the retailer on behalf of consumers buys grid access from the DSO and system services from the TSO Any difference between the purchased electricity amount and actual consumption by consumers must be balanced by the TSO so the retailer will need to pay for those imbalances For this model the retailer will also take the BRP role so it will be responsible for keeping the schedule sent to the TSO and for paying the resulting imbalances In addition the retailer will also act as an aggregator of balancing to be provided by EcoGrid consumers since it will be the actor acting as the spokesman of consumers with the TSO If as a consequence of the prices sent in the real time market the retailer is out of balance the TSO must take into account that such imbalance is not a result of a bad behavior but a result of a balancing provision 1694 TSO Maintains the syste
207. ocation mgmt 976 FTR Charging management 981 FTR Authentication 1299 FTR Charge point management 1704 NFR Tap RFID to access EVSE 1705 NFR Connect EV and EVSE with cable 1812 FTR EVSE Service Monitoring 1804 FTR Roaming based on Bi lateral Agreements 1810 FTR EVSE Service Delivery 1811 FTR EVSE Service Control 562 FTR Low priority charging 1809 FTR EVSE Service Access 1702 FTR Charging monitoring 1486 UC Enable Disable Service per 1443 FTR Enable Disable Service manently 940 FTR Version Service 1511 UC End a roaming charging 984 FTR CLEARING Forwarding CDR process with Clearinghouse 986 FTR Roaming in different countries 985 FTR Roaming in same country 1524 UC Fleet manager monitors en 966 FTR Current EV charge ergy consumption of pool cars 1301 FTR Fleet management 970 FTR Consumption monitoring 1523 UC Fleet manager tracks pool 944 FTR Vehicle tracking car 1301 FTR Fleet management 1602 UC flexible load for congestion 972 FTR Network congestion management management 1599 UC History of EVSE use 967 FTR History of EVSE use 1380 UC Inactivate Business Partner 1369 FTR Activate Inactivate a Business Partner Ac Account count 1618 UC Marketplace Login 1617 FTR Marketplace Authentication and Authori zation 1619 UC Marketplace Logout 1617 FTR Marketplace Authentication and Authori zation 1687 UC Notify Service Requesters of 1443 FTR Enable Disable Service own Service 1685 FTR Create Notification to Se
208. ocess EXAMPLE At a car park where parking fees could include the energy consumption of the vehicle or charging at domestic household socket A similar situation is also referred to as Open Access by Better Place 1701 FTR Open access to EVSE 979 FTR Authentication of user This feature allows for an EVSE operator to give a user access to an EVSE from tapping an RFID card or other compatible ID ISO 15118 The feature involves the following e Driver uses a compatible ID to access EVSE e Ifthe EVSE recognizes the driver either as customer or roamer access is given e EVSE starts charging the car e fthe EVSE operator cannot validate the user charging will be interrupted 2 4 3 Identification and authorization Use Case s The details of this content are described in the following Use Case 2 4 3 1 1502 UC EV Identification Authentication and Authorization Scope amp Level Basic end user services This use case covers identification of contract belonging to a user own customer or roamer at a charge spot or battery switch station and his authentication and authorization to execute the process of charging or battery switching Use case describes the interaction between EV EV driver EVSP EVSE operator and optionally the Clearinghouse when roaming Goal in context The goal of this use case is to enable the EVSE operator to authorize the EV driver to use EVSE services charge or replace battery etc and determine the paymen
209. of Charging Point infrastructure e Search and Monitoring of Charging Point infrastructure e Change update adjustment of Charging Point infrastructure Alternatives o Variations J Related informa e Requires a high availability of system e g gt 98 tion e Requiresa high systems performance and fast response time e Requires a secure and stable system environment Issues e 3 3 6 2 1563 UC Parking Space Monitoring Scope amp Level Value added service Parking space monitoring The service requester will be enabled to monitor the GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 53 of 210 Green Dy eMotion BG V e usage of CPs number of CPs connected to any EV e usage of parking spaces CPs physically occupied by vehicles but not charg ing Goal in context A service requester uses the Parking Space Monitoring service to monitor the us age of the parking spaces at charge points EVSEs Preconditions e The EVSE backend is connected to the market place e The EVSE backend provides a Parking Space Monitoring service e The EVSE is equipped with sensors to detect if any car blocks the parking Successful out The real time usage data of the parking spaces within the Charge point come EVSE will be provided to the EVSE operator to support the charging location management The aggregated usage reports can be provided via the market place to demanding parties Analysis of the these reports may help
210. of new Services 1629 UC Create Response on Requests for new Services 1620 UC Search and Select Requests for new Services 1626 UC Change Request for a new Service 1627 UC Delete Request for a new Service 927 FTR Service Transaction 1239 UC Search and Select Services overview 1471 UC View Service Transaction Details 1242 UC Search and Select Service Transactions 935 FTR Provide Service Con 1482 UC View Service Contract Template tract Framework 1396 FTR Define and Register 1485 UC Create Service Contract Service Contract 1482 UC View Service Contract Template 1624 UC Change Service Contract Offering 1479 UC View Service Contract Details 1470 UC Create Service Contract Offering 1484 UC View Service Details 931 FTR Change or Terminate 1480 UC Create Service Contract Termination Request Service Contract 1481 UC Confirm Service Contract Termination 1479 UC View Service Contract Details 1245 UC Search and Select Service Contracts 1247 UC Confirm Service Contract Change 1246 UC Create Service Contract Change Request 1469 FTR Suspend Resume Ser 1479 UC View Service Contract Details vice Contract 1245 UC Search and Select Service Contracts 1490 UC Suspend Resume Service Contract by Service Re quester GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 109 of 210 Green Dy eMotion LY ID Feature Realized By 1315 FTR Register Service 1477 UC Create Service Registration Contract 1482 UC View Service
211. on tract was not ac GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 146 of 210 Green N eMotion EA AL V Primary actor 1355 ACT Business Partner Secondary actor 1367 ACT Marketplace Business Operator Main scenario e Registration Request Form company data and responsible person filled and submitted by a representative of the Business Partner e Acceptance of the Partner Contract by the Business Partner e Creation of a Business Partner in the System by the Marketplace Business Operator e Provision of an access mechanism Access Data Notification to the Business Partner Alternatives Variations Related information Access Role Based Authorization required Data Security Data Integrity must be guaranteed Data Confidentiality must be ensured Data Privacy Sensitive Data is only stored when needed and authorized Data Export Policy required Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market 6 3 20 1368 FTR Change Business Partner Account A registered Business Partner can request a change of his data The following actions have to be taken by the Marketplace Business Manager e Check of the Service Contracts of the Business Partner has to be performed e Change of the Business Partner Object in the GeM Marketplace Check of the Partner Contract between the Business Partner and the GeM Market
212. onsumption of pool cars eeseeeeeeeeee nnne 102 5 3 11 2 1598 UC Aggregated EV charge overview by the DSO snnrnnnnnnnnnnnnrrnnnsnnnnannnrnnrssnnnnnnnrrnnssnnnnnnnnnnnsenn 102 5 3 12 1 1604 UC Vehicle to grid Signal cisissescistitasescencasessasaosnnadncareeesseed ndaseanedcsnddcsnasseaeeheasdadsadeavoes saidsbaatasoanece 103 5 3 13 1 1604 UC Vehicle to grid sighal erspart odes ever irapa e neo Gras or ARE E ER RR EROR e CERES RAV rE akehi pda 104 5 3 14 1 1599 UC History Of EVSE USE aieo retener eaae AE babies 104 6 Core marketplace services use case model eere eene eene eene nnne 106 63 2 1 1619 UC Marketplace LogOUt ie eoi t rte rr reae ue e P Eee AXE coe eme dienes e VIE Fo PCR RR Se RAS SUE e E 111 6 3 2 2 1618 UC Marketplace LOGIN ccscccccccssessssscsscccsscssseseccccssesnsaseescesesensuaeesececseensseseeceeseeauseesseseseeseeeeas 111 6 3 3 1 1239 UC Search and Select Seryices iiis ista aeta a kk a ga CRY RAF RR Led ED bra ATESTE napa kae 112 6 3 3 2 1484 UC View Service Details unna roii hae ir a tein me FERAE ianiai EXRRTR ERE aS ERE aed Ra Ia sea 113 6 3 4 1 1485 UC Create Service Contract easi isset eno si pa prae ERR rruna RAP RE BER FRU SETER RS EAE RYE SERRA Ra aa aas 113 6 3 4 2 1487 UC Download Service Specification eese sessi eene ennt ntn rnnt sentirse ann 114 6 3 4 3 1239 UC Search and Select Services irte ar aea rn dba RD Ca Rua
213. ontract at all In these cases it can be necessary e g due to local regulations to offer the EV driver access to recharging services This is referred to as open access This access can be granted in different ways e g remote access granted by using apps phone call to EVSE operator pre paid cards etc Payment can be settled in various ways depending on the open access solution implemented 564 FTR SLA After a customer is identified at an EVSE the SLA between EVSP and customer dictates e minimum service level e g sufficient charging to drive to the next Charge Point or battery switch sta tion e roaming y n e value added services 561 FTR Priority charging The EV driver can request a priority charge using a compatible communication link to the EVSP mobile app telematics sms etc The EV driver will receive a request confirmation or denial based on EVSE operator approval 562 FTR Low priority charging An EVSE operator is requested by EVSP or clearing house to lower the charging priority of a customer based on a customer s SLA EV Driver EVSE EVSE Operator EVSP Cable connect Roaming denda Roaming Figure 10 Low priority charging as implemented by Betterplace GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 35 of 210 Green eMotion EG The circle on the illustration above shows how the features SLA Priority charge and Low priority are settled between two operators in a roamin
214. or EVSEs based on specified input e g e Current location of driver e Driver s destination e Car and infrastructure capabilities AC charging DC charging battery switching 918 FTR Enhanced charging Driver will be able to e Check availability e Search for the best price e Obtain optimized suggestion based on his profile cost time environment 1278 FTR Identification of available EVSE The driver uses app on board unit or customer service hotline to identify available EVSE when on the road 1296 FTR Third party information This feature comprises the usage of data provided by third party data providers for value added services Services like searching reservation or routing may be enhanced by these data 969 FTR EVSE Charging capabilities GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 22 of 210 Green eMotion BG JL V This feature comprises information of an EVSE s charging capabilities in order to display only compatible EVSE options to the driver The information should reflect the EVSE s charging capabilities e AC charging e DC charging e Battery swapping Tasks in the feature e Define a format for infrastructure capabilities e Define APIs to retrieve infrastructure capabilities 978 FTR Search for charge point or battery switch station This feature allows a driver to make a search of charge spots or battery stations within specified geo graphical area or route A search can
215. or its grid From a gen eral point of view the recharging infrastructure is connected to the LV electricity grid Thus each condi tion that varies the load impacts over the quality and safety of LV grid which is within the responsibility of the DSO As far as the availability of energy that can be retrieved by EVSP customers is below a certain quantity the V2G activity should not reasonably affect the TSO So it is within the DSO duties do release a signal to the EVSP by stating that under a specified load area the cars connected to the EVSEs are allowed to feed back into the grid a pre settled amount of energy This can be accomplished if the DSO smart management layer IMS is somehow connected to the EVSP back end and is able to retrieve and provide information 5 3 12 1 1604 UC Vehicle to grid signal This Use Case is listed before in this Chapter please refer to paragraph 5 3 2 1 Scope amp Level Value added service This use case enables the DSO or other energy stakeholders to distribute the need GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 103 of 210 Green NN eMotion En AL V for congestion management to multiple service providers through the marketplace 5 3 13 560 FTR V2H supply signal The DSO sends a signal to the EV to release energy to the household 5 3 13 1 1604 UC Vehicle to grid signal This Use Case is listed before in this Chapter please refer to paragraph 5 3 2 1 Scope amp Level Val
216. or more Service Providers that do act on the Marketplace Third party Services may include complex interaction with the outside world or may be as simple as supplying specific data such as timetables of public traffic tourist information or weather forecast A Third Party Service Provider has a contract with a Service Provider 133 ACT Vehicle Driver Human currently driving the Vehicle 1689 Consumer Its main goal is to consume electricity and to that end it is willing to pay for it 1695 DSO Maintains the distribution system security 1696 EcoGrid Consumer Being a consumer its goal is to consume electricity Nevertheless it has an addi tional goal which is to alter its power exchange with the electricity network auto matically or by hand in order to 1 consume less and or produce more electricity during high priced periods and 2 consume more and or produce less electricity during low priced periods To that end it receives real time price signals from the TSO or the DSO 1691 Market Operator It manages the wholesale electricity market by receiving purchase offers and sell ing bids from retailers and producers It matches them and calculates the market clearing price 1692 Producer The producers aim is to sell its electricity production and make a profit out of it It is assumed that electricity is sold through the wholesale market Any difference between the sold electricity amount and actual generation must be balanced by the TSO s
217. ore platform services enable the functioning of the Marketplace and facilitate stakeholders to offer and request business services described in Chapters 2 4 The core marketplace services domain describes the essential services to run the marketplace itself It covers mainly the functionality to offer services by service providers and the use of those services by service requesters referring typically to the terms Buying and Selling These terms are processes that can be divided in sub processes described in the core service chapter Marketplace services are crucial to effectively realize the business services with the use of GeM Marketplace This deliverable comprises about one hundred requirements which are considered by major e mobility stakeholders to be of high value and easily adopted by the emerging e mobility market Once they be come tangible through the first release of the Marketplace their potential will be proven by the demo re gions of Green eMotion Variations and enhancements of these requirements will be implemented in the next releases of the Marketplace Note To achieve efficient retrieval of desired content from this comprehensive deliverable please refer to section How to read this document at the end of the Introduction chapter GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 10 of 210 Green N ET 7 eMotion LY 1 Introduction This deliverable provides in form of structured ICT requirements a thor
218. ormance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 116 of 210 Green N eMotion EA AL V 6 3 5 2 1241 UC Call of Service Goal in context The Service Requester performs a call of a contracted Service and receives the result Usually the service call is originated by an end user of the Service Reques ter Preconditions The Service Requester has a valid Service Contract not suspended with the Service Provider Successful out The Service Requester receives the result of a service call from the contracted come Service Provider Failure outcome Failure Outcome Condition leading to outcome Invalid Re Creation of an error response The service request is not compati quest message and a log entry ble with the Service Interface EN D 138 ACT Service Requester Secondary actors 137 ACT Service Provider Main scenario e The Service Requester makes a request based on the Service Interface Specification to the marketplace e The marketplace routes the request to the contracted Service Provider e The Service Provider fulfills the request or displays an error message e A Service Transaction Entry will be created by the marketplace e The response of the Service is routed back to the Service Requester Alternatives Variations If
219. ors tify requested service Typing errors Connectivity Other Outdated or false in The user is offered ser Service provider fails to formation about vices based on outdated track or update real time Charge prices or false information information Charge point User fails at making soft availability ware updates Route information Other Charge sites 2 Set SMa actor 133 ACT Vehicle Driver Ee Vehicle Driver 1406 ACT EVSE Backend 1407 ACT EVSP backend Secondary actors 140 ACT Clearinghouse 128 ACT EVSP Electric Vehicle Service Provider 136 ACT Marketplace Operator 132 ACT EVSE Operator Main scenario e Search for EVSE e Selection of EVSE e Route guidance to EVSE e Arrival at EVSE User plans route and charging unconnected Variations This use case contains a package of basic end user and value added services e g reservation In day to day operation the user may only choose part of the offered services which shall be processed as well Related informa tion Issues Security and privacy GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 24 of 210 Green DN eMotion BG AL 2 3 3 2 1527 UC Search for EVSE Scope amp Level EVSE search includes functions attributes of EVSE such as Geographical information e g actual location of the e car planned location for travel reservation Actual availability status e g free occupied reserved out of order mainte nance AC charger DC charger or ba
220. oss domain use case model 3 1 Overview The use cases in this sub chapter are mostly described by Siemens and realize basic end user services These services relate to the use of the electric vehicle and driving during all three charging cycles as de scribed above The character of these services however is beyond the basic use of EV they include the planning in connection to other means of transport intermodality vehicle tracking parking management without charging battery life information etc Some of these services are overlapping with other domains for example use case ID 1524 describes the monitoring of EVSE by fleet manager and there is a use case in the energy domain ID 1598 which de scribes the monitoring of aggregated EVSE use under a substation Although these use cases are similar in their goal and scope they serve different purposes and have different main actors Driving services satisfy Business scenarios from the Charging and OEM domains mainly through the Fea tures 1298 Parking space management and monitoring 1318 Reservation of charging point 944 Vehicle tracking and FTR 920 Battery life The three Cross domain services stand aside from the usual structure because of their complexity By their scope these features are almost on the level of a scenario there are several variations and multiple actors which act through the use cases These Features are e Intermodality planning considers planning and optimized s
221. other mandatory condi GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 85 of 210 Green N eMotion BG tion is that the recharging infrastructure is able to fulfill fast reliable and secure communication through its back end with the DSO Service contracts should always declare performances from a nominal point view As soon as the network congestion is detected the DSO front end towards the electricity grid and the energy market that to gether with the EVSE Op back ends defines the Infrastructure Management System IMS a multi owners layer in the electric mobility framework evaluates aggregated per each EVSE Op back end of interest the requested load profile allowed for EV recharging The DSO therefore forward the power pro file request to the EVSE Op back ends that are in charge of distributing the electric mobility load profile over the registered EVSEs according to their own algorithm contractual constraints Once the load reduc tion is elaborated and distributed in a granular way within all the EVSEs the EVSE Op back end forward the load profile to the EVSEs that are currently in use in the specified load area where the DSO has de tected the network congestion The updated load profile is forwarded to the EV under the assumption that the EV is able to deal with this issue and the communication EV EVSE guarantee this information to be propagated Therefore the EV modifies its charging pattern and feeds back power pro
222. ough description of the initial yet high value Marketplace services which will be starting point of further evaluation for demonstration in the regions The almost one hundred use cases described in this deliverable shape the first reference archi tecture of the Marketplace and outline the business interactions around it from the Charging Roaming and Energy perspective How was the Marketplace eco system created where do we stand and what are the next steps Prior to the design of the Green eMotion s Marketplace a thorough analysis of previous electric mobility demonstrations and their IT approaches have been performed in task 3 1 Stakeholder ICT Requirements and Business Analysis The first high level requirements were documented as Business scenarios in the deliverable D3 1 and transformed to specialized requirements tool to leverage its reusability and lessons learned In depth survey of the expectations of internal and external stakeholders provided that no basic requirements were omitted This Deliverable is enabling a holistic goal definition of the overall system to be produced In its current form D3 3 represents the first phase of structured description of Marketplace requirements and its IT characteristics will be further detailed in the specification phase The content and interactions of D3 3 features and use cases will be further enhanced in the second phase requirements for the 2 release of the Marketplace multiple variations and al
223. perator EVSP Tap card bk Cable connect It Roaming aaa Roaming Figure 17 Communication process for Roaming by bi lateral agreements Just as when Roaming using a Clearinghouse there will be differences between National and Interna tional Roaming based on local regulations These differences will be covered by the specific agreements and are not specified any further is the current context 4 3 4 1 1502 UC EV Identification Authentication and Authorization This Use Case is listed before in this Chapter please refer to paragraph 2 4 3 1 Scope amp Level Basic end user services This use case covers identification of contract belonging to a user own customer or roamer at a charge spot or battery switch station and his authentication and au thorization to execute the process of charging or battery switching Use case describes the interaction between EV EV driver EVSP EVSE operator and optionally the Clearinghouse when roaming 4 3 4 2 1518 UC During charging This Use Case is listed before in this Chapter please refer to paragraph 2 5 3 1 Scope amp Level End user services This use case covers the enhanced connect charge disconnect cycle FTR1358 with additional services Use case describes interaction between EV driver EVSE Backend and optional 3rd parties Energy trader DSO public sector Note that Identification Authentication and Authorization is a separate Use Case GA MOVE FP7 265499 Green e
224. place has to be per formed 6 3 20 1 1373 UC Search and Select Business Partner This Use Case is listed before in this Chapter please refer to paragraph 6 3 19 1 Scope amp Level Core Service Find Business Partners that satisfy search criteria 6 3 20 2 1376 UC Change Business Partner Account Scope amp Level Core Service Goal in context Data of a Business Partner are changed Business Partner is registered at the marketplace Successful out The Business Partner is changed in the system at his request come El lo outcome FN e Display of an error message Request Form is complete e Cancellation of the change re not filled correctly GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 147 of 210 pO ques Z4 9 J y gt K JJ Secondary actor 1367 ACT Marketplace Business Operator 1355 ACT Business Partner Main scenario This use case act as parent of other use cases for changing partner data e Change Request Form filled and submitted by a representative of the Business Partner e Change of the Business Partner data in the system by the Marketplace Business Manager Notification of the Business Partner Alternatives Related information Access Role Based Authorization required Data Security Data Integrity must be guaranteed Data Confidentiality must be ensured Data Privacy Sensitive Data is only stored when needed and authorized Data Export Polic
225. quip is used to exchange energy between the EV ment and the Grid This can be both slow charg ers fast chargers and battery switch sta tions 132 ACT EVSE Operator in charge of managing the EVSEs 1406 ACT EVSE Operator Backend Is the backend system of the EVSE operator 128 ACT EVSP Electric Vehicle Service Provider offers e mobility services to the end cus tomers 138 ACT Service Requester Business Partner that consumes EV Services on the Marketplace Table 5 11 Energy Domain Actors GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 84 of 210 Green Dy eMotion 5 3 Features and Use Cases 5 3 1 Overview V The following table lists the Energy Features and their Use Cases ID Feature Realized By 972 FTR Network congestion man 1604 UC Vehicle to grid signal agement 1602 UC flexible load for congestion management 973 FTR Reactive power 1605 UC Reserve and activate ancillary services 1604 UC Vehicle to grid signal 974 FTR Phase balancing 1605 UC Reserve and activate ancillary services 1604 UC Vehicle to grid signal 975 FTR Ancillary services 1605 UC Reserve and activate ancillary services 1604 UC Vehicle to grid signal 971 FTR Aggregated balancing capac 1604 UC Vehicle to grid signal ity to the TSO 1601 UC provide balancing capacity 965 FTR Peak shaving on MV 1597 UC Peak shaving 1317 FTR Peak shaving on LV 1597
226. r Core platform marketplace services 22 Services Use case tables marked in Orange color For easy reference to the Business Analysis Deliverable 3 3 the Services are listed in alphabetical order in Appendix F together with the Business Scenario they support GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 17 of 210 G oy eMotion E ft V 2 Charging functional domain use case model 2 1 Overview This chapter is the most complex in both content and structure and includes the highest number of fea tures 28 out of 76 The working group was represented by a variety of industries ranging from automo tive OEM through energy to IT and e mobility services Companies that participated in creating the Charging domain requirements include Better Place BMW Daimler RWE SAP Siemens and IBM The core of this chapter the cycle around connecting charging and disconnecting an electric vehicle was pro vided by Better Place The working group defined basic and value added end user services from the scenarios described in the 3 1 deliverable of GeM There are three main charging scenarios forming this domain It is the basic charging its enhanced func tionalities and the different charge locations which can be at home semi public in offices shopping cen ters or public at curbside This domain covers all kinds of services that give the EV driver access to re charged batteries including slow charging quick charging and bat
227. r e The Service Provider fulfills the request or displays an error message e A Service Transaction Entry will be created for each service call to a Service Provider by the marketplace e The marketplace collects the responses of each single service call and aggregates the results to one service response The response of the Service is routed back to the Service Requester Certificate Mechanism or equivalent is required Data Security Data Integrity must be guaranteed Data Confidentiality must be ensured Data Privacy Sensitive Data is only stored when needed and authorized Data Export Policy required Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market 6 3 7 1685 FTR Create Notification to Service Requester The Service Provider or the Marketplace Operator is able to send notifications to the Service Requester of his own Service GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 119 of 210 Green N eMotion En AL V 6 3 7 1 1687 UC Notify Service Requesters of own Service Scope amp Level Goal in context The Service Provider or the Marketplace Operator sends notifications to the Service Requester of his own Service A Service is selected Successful out The Service Requester of a Service is notified come Secondary actors 136 ACT Marketplace Operator Main scenario e The Service
228. r Parking only by his EVSP Alternatives EV driver forgets to check out at the CP before leaving the CP with the EV In this case the EVSE Operator stops billing when the system detects that the CP is not blocked any longer Gog The EV driver will be billed for parking but only for the time where no charging problems if EV needs only trickle charging d informa This use case refers to CPs where besides charging also a great demand for tion short time parking exists This will happen mainly in central areas In areas where CPs are scarce in relation to the number of EV s only few CPs will be equipped to allow Parking only The allowed parking time should be quite short to prevent longer blocking of the CPs for parking reason It will not be possible to reserve a CP for Parking only The response time to the Park only request should not exceed a few sec onds because it would be unacceptable for the EV driver to wait longer The detection of misuse e acar uses the CP without authentication of the driver at the Charge point EVSE A non electric car uses the CP or shall it be allowed to use the CP with a non electric car by using a much higher parking tariff Currently there exist no legal rules which allow the reservation of a parking space for EV s only 3 4 Cross domain Features and Use cases This group contains the following Features and Use Cases GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 55 of 210
229. rd Interface 1363 BPD B2B Partner Management Create Business Partner Account 1371 BPD B2B Partner Management Change Business Partner Account 1382 BPD B2B Partner Management Activate Business Partner Account 1403 BPD B2B Partner Management Inactivate Business Partner Account 1186 BPD Centralized Congestion Management 1198 BPD Congestion Management through TOU Tariffs 1199 BPD Distributed Congestion Management 1200 BPD Enhanced charging All Business Process Diagrams are created out of the RRC Tool GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 159 of 210 eMotion Green on E AL 1270 BPD Contractual Clearing Authorization it i ij ne w mangoes broene s eoe SD e nett Tha tu sepma on te rd samen m Orom aan a B B nmang stem TA Operator Baer f anger Constans we pork aL x x 29 comtiad mosen hh 829 contract vend E 2 i i GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 160 of 210 Green Ny ES A eMotion V 1452 BPD Contractual Clearing CDR Forwarding O E End Charging Process 0 a End Charging Process i O End Charging Process 0 amp End Charging Process i 3 Store CDR o T i O End GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 161 of 210 Green I EG 2 eMotion V 1441 BPD General Selling Buying Process
230. rd Interface e Optionally providing downloadable content e g service manual portlet used by the Service Re quester s end user portal or an app for a mobile device Creation of a Service Contract Offering based on the Service Contract Framework Providing cloud execution information Acceptance of the Service Registration Contract of the GeM Marketplace Testing of the service by the Marketplace Technical Operator Creation of an entry in the Service Catalogue and optionally an entry in the Image Catalogue Note Any changes on a registered service result in a new service version 6 3 14 1 1477 UC Create Service Registration Contract Goal in context During the service registration the Service Provider has to accept the Service Reg istration Contract of the marketplace The Service Registration Contract is provided by the marketplace Successful out The Service Provider accepts the terms and conditions of the Service Registration come Contract The result is stored by the marketplace Failure outcomes Failure Condition leading to out come Service Registra e Display of an error mes Business Partner has not tion Contract is sage accepted the Service Regis not accepted e Cancellation of the ser tration Contract vice registration re RR 137 ACT Service Provider Secondary actor GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 134 of 210 Main scenario e The Service Provider accepts the terms and
231. reconditions EVSP offers a city pilot service which combines personal preferences and in formation from third party providers The EV driver has a roaming and city pilot service contract with an EVSP The EV driver has configured personalized preferences by using his EVSP ac count The EVSP has a special knowledge base to store the preferences The EVSP has direct contracts with several third party providers e g traffic su pervision shopping malls office of public transportation tourist information Successful out The EV driver will be provided with a list of available Charge points EVSE The come stations will be sorted or highlighted dependent from the accordance with the per sonal preferences Additionally the reasons for recommending selected stations can be returned e g as a link to an event or sales description Failure outcomes Failure Outcome Condition leading to outcome No Charging The EV driver will e No communication to Charge point point is be provided with EVSE available an empty list e Inconsistent data scheme e Nocharging point is available within the search area P dd P 133 ACT Vehicle Driver interacts as described in the main scenario GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 27 of 210 Green N eMotion a AL V Secondary actors 128 ACT EVSP Electric Vehicle Service Provider 1579 ACT Third Party Service Provider Main scenario EV driver requests
232. rent and pending transactions must not be adversely affected Access Role Based Authorization required Data Security Data Integrity must be guaranteed Data Confidentiality must be ensured Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market 6 3 15 2 1480 UC Create Service Contract Termination Request This Use Case is listed before in this Chapter please refer to paragraph 6 3 12 1 Scope amp Level Core Service A termination of a bilateral Service Contract is a two step process A Business Partner Service Provider or Service Requester makes a termination request on a Service Contract 6 3 15 3 1687 UC Notify Service Requesters of own Service This Use Case is listed before in this Chapter please refer to paragraph 6 3 7 1 Scope amp Level Core Service The Service Provider or the Marketplace Operator sends notifica tions to the Service Requester of his own Service 6 3 15 4 1481 UC Confirm Service Contract Termination This Use Case is listed before in this Chapter please refer to paragraph 6 3 12 2 Scope amp Level Core Service A termination of a bilateral Service Contract is a two step process A Business Partner Service Provider or Service Requester accepts or rejects a termination request on a Service Contract made by the other Business Partner 6 3 15 5 1486 UC Enable Disable Service
233. res Phase balancing will reduce losses in the distribution grid DSO will reward the EVSP based on the sav ings it can reach by the reduction of losses This feature has similar requirements to the Reactive Power provisioning from an EVSP The DSO evaluates whether or not such an offer of aggregated power is valuable to increase the quality of service in a specific load area by matching with the capability of bidirectional flow of energy of the EVSEs involved Such a feature obviously requires a communication layer to be established on top of the EVSEs between the EVSE Op back end the EVSP back end and the electric mobility marketplace and an direct interaction between the EVSE Op back end and the DSO front end in order to demand the bidi rectional flow this feature may be a special condition of V2G capability 5 3 4 1 1605 UC Reserve and activate ancillary services This Use Case is listed before in this Chapter please refer to paragraph5 3 3 1 GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 91 of 210 Green Dy eMotion BG AL i Value Added service Scenario E2 An EVSP offers aggregated flexible load as ancillary service to the DSO in order to help the DSO to fulfill the distribution rules established by the regulation framework in which it operates In example frequency and voltage will be adjusted in the local grid by drawing power from the batteries or interrupting load This service will in crease the quality o
234. rge disconnect cycle FTR1358 with additional services Use case describes interaction between EV driver EVSE Backend and optional 3rd parties Energy trader DSO public sector Note that Identification Authentication and Authorization is a separate Use Case UC 1502 but parties may choose to implement UC 1502 within the connect charge disconnect cycle 4 3 8 8 1511 UC End a roaming charging process with Clearinghouse This Use Case is listed before in this Chapter please refer to paragraph 4 3 2 4 Scope amp Level Clearing Service This use case is an internal clearinghouse procedure serving 2 business stakeholders EVSP EVSE operator It has no functional effect on the end user 4 3 3 4 1512 UC Start a roaming charging process with Clearinghouse This Use Case is listed before in this Chapter please refer to paragraph 4 3 2 1 Scope amp Level Clearing Service Trigger to start a roaming charge after the transaction has been validated by the clearinghouse 4 3 4 1804 FTR Roaming based on Bilateral Agreements When Roaming without clearing house to handle contracts and financial clearing the interaction between EV Driver subscriber EVSE charge spot EVSE operator Charge Network Operator and EVSP Electric Car Home Operator will follow a specific procedure as illustrated below GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 73 of 210 Green NN EI 2 eMotion 4 LY EV Driver EVSE EVSE O
235. rketplace for different purposes i e for statisti cal analysis on EVs roll out EVSE performance analysis EVSE Op marketing and certification 5 3 14 1 1599 UC History of EVSE use Scope amp Level Value added service The historical use of EVSEs is useful information that an EVSE Operator acting as Service Provider in the marketplace can use in order to deliver benefits to its cus GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 104 of 210 Green g Ea 7 eMotion LY tomers and sell or support services for others business actors in the electric mobility This use case enables gathering of charging detail by the DSO and making this in formation accessible through the marketplace This requires that the EVSE is able to deal with charging information so the re charging infrastructure is expected to be smart with embedded communication capabilities e Also B2B relationships between EVSP and EVSE Operator must guarantee access to part of the information enrolled above e g the charging status Stakeholders can retrieve EVSE History Information come retrieved to stakeholders tween OEM and EVSP ry acto 32 ACT EVSE Operator ndary actors 128 ACT EVSP Electric Vehicle Service Provider 1406 ACT ECSE Operator Backend The historical use of EVSEs can be aggregated either per EVSE or per geo graphical load area from the EVSE Operator back end This information should be made available as content for a dedicated
236. rocess A Business Partner Service Provider or Service Requester accepts or rejects a termination request on a Service Contract made by the other Business Partner Preconditions e A Service Contract between the Service Provider and the Service Requester exists e The Business Partner has been notified on a termination request on the Service Contract Successful out The termination request on the Service Contract is accepted or rejected The other come Business Partner is notified GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 130 of 210 The Business Partner accepts or rejects the termination request on the Service Contract The Service Contract is terminated A Service Contract History Entry is created The other Business Partner is notified Alternatives Related informa tion Role Based Authorization required Data Security Data Integrity must be guaranteed Data Confidentiality must be ensured Data Privacy Sensitive Data is only stored when needed and authorized Data Export Policy required Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market 6 3 12 3 1479 UC View Service Contract Details This Use Case is listed before in this Chapter please refer to paragraph 6 3 11 4 Scope amp Level Core Service View the details of a Service Contract 6 3 12 4 1245 UC Search and Selec
237. roup specified by the consortium including the Commission Services CO Confidential only for members of the consortium including the Commission Services Revision history Version Date Author Description Draft 0 1 30 6 2011 Andreas Dannhauer Initial version Draft 0 2 0 5 d M Martin Rapos Content and headlines Draft 0 6 13 1 2012 Paul Frenay Populated from RRC Draft 0 7 31 1 2012 Frenay Rapos First complete draft Assembled no layout Draft 0 8 7 2 2012 Frenay Rapos Last Pre release before external review Draft 0 9 10 2 2012 Frenay Rapos Processed WP 3 team feedback Review 1 0 12 2 2012 Detlef Schumann WP3 Lead Review Dave Joynson Alstom External Review es 06 03 2012 a External review implemented V1 3 15 03 2012 Heike Barlag Coordinator review V 1 4 1 5 04 04 2012 Martin Rapos Final comments implemented For Information Draft Version Final Version Internal document Submission for Approval deliverable Final Version deliverable approved on GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 2 of 210 Green N eMotion Ea AL V Table of Contents Executive summary eae paseos een e ena een ann aoo Saa au ERE SERE Oso RES e Fo SUR E SS R RR Pe RNase GENER MNR RE ag Roco SEE aeuo e ar CREE ERR R RR NR aars ESNY 9 MEE ipsi nm 11 1 1 Division of requirements into funct
238. rrnsssrsrsersserssssrsnsssnsrer 130 6 3 12 2 1481 UC Confirm Service Contract Termination eese sees 130 6 3 12 3 1479 UC View Service Contract Details sensere nnne nnne en 131 6 3 12 4 1245 UC Search and Select Service Contracts eese eene 131 6 3 12 5 1247 UC Confirm Service Contract Change eese esee enint ennt atas 131 6 3 12 6 1246 UC Create Service Contract Change Request o ccscsessssscscesssesssseeccessesssuseesecesseetaaseeeseeseetaaaaes 132 6 3 13 1 1479 UC View Service Contract Details eene eene nnne nnne nnne nnn nnne three en 133 6 3 13 2 1245 UC Search and Select Service Contracts essent nne nnne nnne nnne nns 133 6 3 13 3 1490 UC Suspend Resume Service Contract by Service Requester rrrrrnrrnnnrrnnnrennnvrnnvvrnnvrrnsvrennvrernrr 133 6 3 14 1 1477 UC Create Service Registration Contract w rwrrrnnnnnnnnnnnnannnannnnnansnanssnsssnsnsnsssnsnsssnnsnsnsnsnsnsnsnsnnner 134 6 3 14 2 1482 UC View Service Contract Template o ccccccsessscscccsssssssscscecsssecssaeesccssssessseescessseessseseeesesesaaes 135 6 3 14 3 1494 UC P blish Servic m din 135 6 3 14 4 1489 UC Upload Service SPpecifiCQtion ccscccccesscccessssscssssseccessesccssssecseesceceesssceesecesensesceessseeesagaes 136 6 3 14 5 1470 UC Create Service Contract Offering esee esee eene enini nnne tasse rnnt nnan 137 6 3 14 6 1488 UC Upload Service Content wo ccccceeessss
239. rtners Failure outcome Failure Outcome Condition leading to outcome No Business Display of an error There are no business partners that Partners found message meet the search criteria dd 1367 ACT Marketplace Business Operator Secondary actors S Main scenario e The Business Partner fills the search criteria or load search criteria saved before e The marketplace returns a list of Business Partners that meet the search criteria e The Business Partner stores optionally the entered search criteria for later Alternatives Related information Role Based Authorization required Data Security Data Integrity must be guaranteed Data Confidentiality must be ensured Data Privacy Sensitive Data is only stored when needed and authorized Data Export Policy required Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market 6 3 19 2 1374 UC Create Business Partner Account Core Service Goal in context A new Business Partner is registered at the marketplace Business Partner was not registered before The Business Partner is created in the system at his request come to outcome e Display of an error message complete e Cancellation of the registration not filled correctly cepted Partner Contract e Display of an error message The partner con not accepted e Cancellation of the registrati
240. rvice Provider Main scenario The onboard unit of the vehicle permanently calculates the current position The position is sent in configurable intervals to the marketplace and the location service database In case of special events emergency geofence incidents car crash addi tional positions will be sent immediately The history of position data is used for several reports and additional services Related information The interval between position data transmissions is configurable in a central con figuration service of the EVSP The transmission interval is synchronized with the onboard unit configuration The main collector of position data will be a Location Service Provider But the current position will also be available as a basic service of the marketplace to en able further services Please refer to Figure 24 Get Current Position and Figure 25 Send Current Posi tion in the Appendix for more information Issues Privacy 3 3 4 2 1567 UC Call for Roadside Assistance Scope amp Level Basic end user service The driver is actively asking for roadside assistance EVSP directly or through a Marketplace EV is activating the assistance request come tance Service and acknowledged Failure outcome Condition leading to outcome No mobile network Display of an error message There is temporarily connection avail The request is stored and will no active mobile net able be sent when the connection is Work connection es
241. rvice Provider uploads the Service Interface e g WSDL and the Ser vice The marketplace performs a formal validation of the Service Interface The service specification Service Interface and Service Description is stored at the marketplace Alternatives Related informa tion Access Role Based Authorization required Data Security Data Integrity must be guaranteed Data Confidentiality must be ensured Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 136 of 210 Green N eMotion BG L V 6 3 14 5 1470 UC Create Service Contract Offering This Use Case is listed before in this Chapter please refer to paragraph 6 3 11 5 Scope amp Level Core Service During the service registration a Service Contract Offering is created from the template of the Service Contract Framework by the Service Provider 6 3 14 6 1488 UC Upload Service Content Goal in context During the service registration the Service Provider may upload additional content of the offered Service e g manual A Service is selected Successful out Additional content is uploaded to the marketplace come Failure outcomes Failure Outcome Condition leading to outcome gt Ss SE ACT Servo Prove MM ACT Service Provider Secondary actor actor The content is
242. rvice Requester 1557 UC Parking Space Management 1297 FTR Parking space management GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 207 of 210 Green Dy eMo er Ea ID Use Case Realizes Feature 1563 UC Parking Space Monitoring 1298 FTR Parking space monitoring 1596 UC Peak load threshold on a 961 FTR DSO predefines peaks substation 1597 UC Peak shaving 1317 FTR Peak shaving on LV 965 FTR Peak shaving on MV 961 FTR DSO predefines peaks 1257 UC Propose new Standard Inter 1445 FTR Define new Standard Interface face 1601 UC provide balancing capacity 971 FTR Aggregated balancing capacity 1494 UC Publish Service 940 FTR Version Service 1315 FTR Register Service 1493 UC Publish Standard Interface 1445 FTR Define new Standard Interface 1572 UC Reduce Charge Power by 1313 FTR Allow interrupting DSO 1250 UC Register Service 1315 FTR Register Service 1562 UC Report Electricity Consump 970 FTR Consumption monitoring tion 1812 FTR EVSE Service Monitoring 1528 UC Reservation of EVSE 1318 1318 FTR Reservation of Charge Spot 1605 UC Reserve and activate ancil 975 FTR Ancillary services lary services 973 FTR Reactive power 974 FTR Phase balancing 1373 UC Search and Select Business 1369 FTR Activate Inactivate a Business Partner Ac Partner count 1368 FTR Change Business Partner Account 1366 FTR Create Business Partner Account 1620 UC Search
243. s rnannrnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnennnnnnnnnnnnensnnnnnnnnnnnnnnnunnes 193 F Features Where Used in Business Scenario S raannnnsssnnnnnnnnnnnnnnnnnnnnnennnnnnnnnnnnennnnnnnnnnnnennennnnnnnnnnnnennsnnnunnns 200 G Use Cases Where Used in Features errvnnnnvnnvvnnvnnnvnnnvnnnnennnnnnnnnnnnnnnnennnennnennnnennnnnnnennnnnnnnnnnnnnnnnenevenenee 205 List of Figures Figure 1 Structured Requirements Management sssssssssssssesse seen entente nennt 14 Figure 2 Requirements gathering Artifacts and Relations sssssssseeneeennee 15 Figure 3 Usability Engineering Methodology ssssssseseseneneeeee eee 16 Figure 4 Structure of the Charging Domain esses eee enne nennen nnn nnne en 18 Figure 5 The Connect Charge Disconnect cycle ener 19 Figure 6 Scope of Before Charging ssssssssssssssssssess seen enne nnne en nennen nnns intrent 21 Figure 7 User Identification Scenario s Source ISO 15118 1 nmmrsnnvvrrrennvvrrrrnnnrrrrrrnnvrrrrrnnvsrrrrnnrsrrrrnnnnnr 29 Figure 8 User Identification as implemented by Betterplace sssseeeeene 30 Figure 9 Scope of During Charging sssssessssssseees seen nennen nennen nnne nnne nnns intrent 33 Figure 10 Low priority charging as implemented by Betterplace sse 35 Figure 11Scope of After Charging
244. s Failure Outcome Request for a new Display of an er Service is incomplete ror message GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 120 of 210 Green N eMotion BE AL V 138 ACT Service Requester Secondary actor Main scenario e The Service Requester fills a form with the requirements of the Request for a new Service e The newly created Request for a Alternatives Related informa tion Access Role Based Authorization required Data Privacy Sensitive Data is only stored when needed and authorized Data Export Policy required Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market 6 3 8 1623 UC View Details of Requests of new Services Scope amp Level Goal in context View the details of a selected Request of a new Service Preconditions e The actor is a representative of the Business Partner of the marketplace or the Marketplace Operator e A Request of a new Service is selected Successful out The Business Partner receives a view of the details of the Request of a new Ser come vice e g e Requirements e Pre Post conditions Failure outcome Failure Outcome Condition leading to outcome EN O h JJ 9O KE EE EN 1355 ACT Business Partner Secondary actors 136 ACT Marketplace Operator Business or Technical Main scenario e
245. s The searching actor is a representative of a Business Partner of the marketplace or the Marketplace Technical Operator Successful out The Business Partner receives an ordered list of available Standard Interfaces come that meet his search criteria and is able to select a Standard Interface from the list for further activities like view details or download interface specification E g search criteria may include e Proposed and published Standard Interfaces e Standard Interfaces by category Failure outcome Failure Outcome Condition leading to outcome No Standard Inter Display of an error There are no standard interfaces faces are found message that meet the search criteria p e Primary actor 1355 ACT Business Partner 402 ACT Marketplace Technical Operator Main scenario e The Business Partner fills the search criteria or load search criteria saved before e The marketplace returns a list of Standard Interfaces that meet the search criteria e The Business Partner may store the entered search criteria for later use Alternatives J Variations Related information Access Role Based Authorization required Data Security Data Integrity must be guaranteed Data Confidentiality must be ensured Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market 6 3 15 1443 FT
246. s for enabling innovative solutions Tasks are grouped into so called task clusters These clusters are a pre step for the future user interface and they show which tasks functionality are grouped together on one screen mask The relationship be tween the task clusters from the end user point of view is documented in the navigation map The knowledge of the actors and their tasks is the foundation for discussions related to the software re quirements and functional scope This output is used for requirement specification and development planning e g several phases which requirements which features will be realized in which phase which serves as input for architecture and software development References to this section Constantine L and L Lockwood 1999 Software for Use A Practical Guide to the Models and Methods of Usage Centered Design New York ACM Press GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 16 of 210 Green DN eMotion a 2 5 Go M 1 4 How to read this document The WP3 team suggests the following approach to reading this document 1 2 Read the introduction first 2 Select the functional domain of interest a If looking for general impression read each chapter introduction for an overview b If looking for a particular service read the second section of each chapter for overview of ac tors and also the sub section for the list of described services and their use cases e g for chap
247. s in the specification phase leading to the first release of the Marketplace demonstration The Structured Requirements Management Method with the use of the IBM Rational Requirements Com poser RRC was the main methodology used in this deliverable Work package partners identified Fea tures business and core marketplace services to consequently realize them through Use cases with act ing Actors Deliverable D3 3 is a comprehensive export from the RRC tool and its 76 services Features are de scribed by 98 Use cases grouped in 6 chapters Charging services described in Chapter 2 and lead by Betterplace and Siemens include 32 business services divided in sub chapters 6 before charging 2 identification 13 during charging 1 after charging 7 driving 3 cross domain From the end user perspective the timeline of the charging cycle seemed crucial to determine the division of services into those the user will be interested in before connecting its vehicle to a charging point dur ing the charge and afterwards Before charging services such as search and navigation to a suitable EVSE are described Services during and after the charge are expected to include communication with the end user about the status of battery control of charging by third parties monitoring and collection of charge related data Driving Services in chapter 3 describe additional services labeled as driving services include basic end user functionalities as vehicle
248. s of transport System offers the user a multimodal connection using a pool e car to the train station in A taking train to station in B take an e bike to the final destina tion in B Successful outcome User has the ability to alter the system proposal and finally book the travel The system will then reserve e car e bikes seats train and charge the user s credit card Failure outcomes Failure 1 Outcome Condition leading to GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 58 of 210 Green Dy a PEINE BG other mobility sys travel may be not optimal but other mobility system is tem is not avail still a valid travel is calculated not available able END 9 Primary actor 133 ACT Vehicle Driver 137 ACT Service Provider Mobility Provider Secondary actors 1579 ACT Third Party Service Provider Main scenario user enters his request into the system systems searches for possibilities to fulfill the request and informs the user Alternatives Variations pe Related information Luggage may constrain the mode of travel The whole approach is depending on availability of many external systems 3 4 2 3 1548 UC Access Car Information This Use Case is listed before in this Chapter please refer to paragraph3 4 2 3 Scope amp Level Value Added Service Users should get access to car information items 3 4 3 1301 FTR Fleet management The fleet management feature is a superset of different featur
249. sceessecesesseesessaseceesssceeeuesseseessaeees 59 3 4 3 1 1522 UC ASSIGN COLO SCCNQIIO winicsnccesadsncas sinsccsevecscaschecsas ssscdssaeasiaeeenssaseveasssiionndssaeesniovensanadbeasbusaaitassaaads 59 3 4 3 2 1520 UC Users can book pool cars online ssssssscccccsesesssssesccsseesnsuscesecssseesusessceseseeassescecseesessaasseeasesees 60 GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 187 of 210 Green N eMotion Ea V 3 4 3 3 1521 UC Status for cars can be maintained by Fleet MANAGEL ccssscccceesscceeessscsenssccesessscesssssesessaeeees 60 3 4 8 4 1523 UC Fleet manager tracks POOI COM ccccsssccccccseeesssscescccsssesuseescccseeessssssceccessesseeseesesseensaaecessaasees 61 3 4 3 5 1524 UC Fleet manager monitors energy consumption of pool cars assesses eene 61 SAAT 1592 UC COZ Iiolasf om 63 4 Roaming functional domain use case model srrrrrernrennnennvnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnsnnsnnnnsnnennenen 65 4 3 2 1 1512 UC Start a roaming charging process with Clearinghouse eese 71 4 3 2 2 1502 UC EV Identification Authentication and Authorization eese eene 71 4 3 2 3 1518 UC during charging sscccccccsesessssccccessssssasscccsessesssssssesesseesssaeeeesessessaeeeecsessesssaseseceseeuseecesssaaeseeees 72 4 3 2 4 1511 UC End a roaming charging process with Clearinghouse isses esee eene 72 4 3 3 1 1502 UC
250. se which allows EV drivers to control the status of the charge see the loca tions level of service consumed energy etc and congestion management also with V2G perspective related services The former service would be eventually provided by EVSE Operators in the marketplace and EVSP would request it for their customers while the latter services consist in a broad variety of solu tions to make use of the energy stored in the customer s EV in order to sustain grid management or resell energy This service would eventually be published from an EVSP into the marketplace and DSO TSO or Energy Vendor may request it The most advanced congestion management services related to V2G will mean a source of income to the EV owners as the use of their vehicles will be rewarded by service re questors or in case of vehicle to home the EV owners will be able to opt for cheaper electricity contracts for their homes GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 83 of 210 Green Dy eMotion A Ed 5 1 2 Business to business perspective In the energy functional domain the most important benefits of the Marketplace lay in the business to business sphere The one service or benefit with highest value is in allowing the grid operator to realize congestion management by controlling the load of the vehicles This service can be used in case of emergency to prevent black outs brown outs or to help to restart the grid after a black out or
251. ses 970 FTR Consumption monitoring 1519UC After charging Table 2 5 After Charging Features and their Use Cases 2 6 2 After Charging Feature Content This feature comprises the following content 970 FTR Consumption monitoring This feature allows the driver to monitor different aspects of their EV consumption on either on board de vice or through other channels apps internet etc e Energy consumption e Kilometer consumption e Consumption of other services 2 6 3 After Charging Use Case s The details of this content are described in the following Use Case s 2 6 3 1 1519 UC After charging Scope amp Level Basic end user services This use case covers all EVSP or marketplace routed services triggered by the action of unplugging the car from the charging or completing the battery switch Goal in context The primary goal of this use case is that the EVSE Operator documents charg ing data Consequently the EVSE operator distributes relevant information to the EV driver and third parties receive charging report By this use case the user is enabled to use consumption monitoring services or after charging services view bills including kWh km and roaming services con sumed CO2 footprint etc through a compatible interface with a service provider telematics app website email phone call to customer services center or similar GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 39 of 2
252. short term disconnect the EVSE of charged electric vehicles for the purpose of congestion management is of main concern to the WP3 energy partners This scenario con siders the possibility of leveraging the smart metering backbone of the conventional electricity grid or di rectly the smart recharging infrastructure in case of a newly developed e mobility market when embed ded smart metering functionality is deployed These services refer to a nationwide environment and adopt a de localized recharging infrastructure management system or IMS A variation of how these services may run is based on decentralized congestion management as a value added business service not de picted in this document Similarly non binding decentralized approach but from the energy trading and quality perspective the services of synchronized flexible EV load virtual power plant and ancillary ser vices were described All these services could be offered through the Marketplace by aggregators in the long term and by DSOs in the short term and pragmatic scenarios before the aggregation market takes off together with EVSE Ops and based on the local legislation activated bought by DSO TSO or the nearest balance responsible party V2G concept is also described in this deliverable but its full deploy ment is not expected during the first release of the Marketplace Core platform marketplace services described in Chapter 6 and lead by IBM 22 platform services C
253. sscccesesssscescccssesssssceecesseeessseeesceseessssssesceeseeeesseescesseseeeesas 137 6 3 14 7 1250 UC Register SerViCe ceca ae ta pusae esas usse eeu eei ee XA RgS Rege daha area ETATER EEE niaaa 137 6 3 14 8 1476 UC View Standard Interface Details cccccccccesssccsessccceessscceessseccessseccessseceeeseccesssssecetssseessaeees 138 6 3 14 9 1475 UC Search and Select Standard Interface sessi eese eene nnns nns 139 GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 190 of 210 Green N eMotion LY 6 3 15 1 1255 UC Start Stop Service cccccscccessscessscessscesscessseeesssessscensecensssenseeeseees 6 3 15 2 1480 UC Create Service Contract Termination Request 6 3 15 3 1687 UC Notify Service Requesters of own Service sese 6 3 15 4 1481 UC Confirm Service Contract Termination essen 6 3 15 5 1486 UC Enable Disable Service permanently eee 6 3 15 6 1479 UC View Service Contract Details cesse 6 3 15 7 1245 UC Search and Select Service Contracts esses 6 3 16 1 1239 UC Search and Select Services essen 6 3 16 2 1486 UC Enable Disable Service permanently eee 6 3 16 3 1245 UC Search and Select Service Contracts esses 6 3 16 4 1494 UC Publish Service nsnsi renina eiri aiai asoan 6 3 16 5 1489 UC Upload Service Specification
254. stored at the marketplace hematives OOOO SSS Variations Related informa tion Access Role Based Authorization required Data Security Data Integrity must be guaranteed Data Confidentiality must be ensured Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market 6 3 14 7 1250 UC Register Service Scope amp Level Goal in context Preconditions e The Service Interface and the Service Description is uploaded The Service Provider has accepted the Service Registration Contract Successful out The Service is registered come Failure outcome Failure Outcome Condition leading to outcome gt 9 137 ACT Service Provider Secondary actors 1402 ACT Marketplace Technical Operator GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 137 of 210 Green N eMotion BG AL Alternatives EE JE a Main scenario e The Service Provider requests the registration of a Service e The Marketplace Technical Operator registers the Service in the Service Catalogue e The Service is disabled until it is published i e enabled permanently in the context of a registration e The Service Provider is notified Related informa tion Access Role Based Authorization required Data Security Data Integrity must be guaranteed Data Confidentiality must be ensured Performance sub second response for Service
255. sts for new Services quests for new Services 1485 UC Create Service Contract 1396 FTR Define and Register Service Contract 1447 FTR Contracting Service 1246 UC Create Service Contract 940 FTR Version Service Change Request 931 FTR Change or Terminate Service Contract 1470 UC Create Service Contract Of 1315 FTR Register Service fering 1396 FTR Define and Register Service Contract 1480 UC Create Service Contract Ter 1369 FTR Activate Inactivate a Business Partner Ac mination Request count 1443 FTR Enable Disable Service 931 FTR Change or Terminate Service Contract 1477 UC Create Service Registration 1315 FTR Register Service Contract 1491 UC Create Service Transaction 926 FTR Call of Service 1516 UC Delete Customer Contract by 983 FTR CLEARING Managing customer data GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 206 of 210 Green Dy eMo ien Ea ID Use Case Realizes Feature 1513 UC Delete EVSP EVSE Contract 1291 FTR CLEARING Managing EVSP data from Clearing House 1627 UC Delete Request for a new 1622 FTR Manage Requests for new Services Service 1478 UC Download Service Content 1447 FTR Contracting Service 1487 UC Download Service Specifica 1446 FTR Search and Select Standard Interfaces tion 1447 FTR Contracting Service 1518 UC During charging 986 FTR Roaming in different countries 985 FTR Roaming in same country 1309 FTR Charging l
256. sues and eventually to charging points priority issues coming from the deployment strategy of the EVSE Op erator The EV driver own EVs in which are installed batteries coming from manufac turers compliant with V2G capability A smart recharging infrastructure is needed in order to accomplish peak pre definition demands coming from the DSO to the EVSE Operator The EV has adequate communication capability to receive modulation orders from the DSO through the EVSE energy gateway especially for low power and time consuming recharges e g 3 3 kW The EVSEs are in communication with an EVSE Operator Backend that ag GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 86 of 210 Green N Eg 7 eMotion V gregates data from each EVSE The EVSE Operator Backend aggregates data from each EVSE and is able to perform communication with the DSO or the marketplace where the dedicated service is running DSO can make use of V2G capability offered on the market according to its criteria Condition leading to outcome EVSP cannot use EV The EV driver does not allow Absence of V2G condi for V2G feed energy from his EV to the tion in the contract grid EV and EVSE cannot It is not possible to feed energy Lack of communication communicate the re back into the grid or lack of compliancy to verse flow of energy 8015118 where EV condition EVSE communication is available FEE HEGE RERMNEREEMEMMEM O 128 ACT EVSP Electric
257. t This Use Case is listed before in this Chapter please refer to paragraph 6 3 4 1 Scope amp Level Core Service A Service Contract is created by accepting a Service Contract Offer ing by the Service Requester 6 3 11 2 1482 UC View Service Contract Template This Use Case is listed before in this Chapter please refer to paragraph 6 3 10 1 Scope amp Level Core Service The template of the Service Contract Framework is displayed to the Business Partner 6 3 11 3 1624 UC Change Service Contract Offering Goal in context An existing Service Contract Offering can be changed from the template of the pg Service Contract Framework by the Service Provider Existing Service Contracts based on the Service Contract Offering are not affected e Contents of the Service Contract Framework are provided to the market place by a static platform independent representation e g XML e A Service Contract Offering is selected An existing Service Contract Offering is changed come Failure outcomes Failure Outcome ondition leading to outcome Service Contract Display of an er Not all required sections from the ser Offering incomplete ror message vice contract framework are chosen gue 137 ACT Service Provider Secondaryactor Main scenario e The Service Provider changes optional sections from the Service Contract Framework e The chosen sections configure a changed Service Contract Offering GA MOVE FP7 265499 Green eMotion
258. t details Preconditions Communication between SECC and EVCC shall be established successfully The customer can identify himself Online connection between SECC and EVSE operator is required Connection between EVSE operator and EVSP directly or through clearing house GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 31 of 210 Green Dy eMotion EG AL V Authentication and authorization process is successful a session ID is defined and come the required service charging or value added starts Failure outcomes Failure Outcome Condition leading to outcome Authentication The required service User might be informed about the process fails no does not start reason for failure i e contract has authorization given expired contract has been blocked by the secondary stolen car or contract procedure to actor be restarted identification server ME Primary actor 143 ACT EV Electric Vehicle 1539 ACT EVCC Electric Vehicle Communication Controller 131 ACT EVSE Electric Vehicle Supply Equipment 1541 ACT SECC Supply Equipment Communication Controller 1540 ACT HMI Human Machine Interface 133 ACT Vehicle Driver Secondary actors 128 ACT EVSP Electric Vehicle Service Provider 140 ACT Clearinghouse Main scenario User connects the car to the station and activates the service offering the ID This could also be done automatically SECCand EVCCexchange their IDs e g Contract ID Those are forwarded
259. t charge disconnect cycle e g Betterplace EVSE operator manages charging or battery switch successfully according to charge profile User is validated or denied access to further service User is continuously notified in real time about charging status start stop er ror SOC time to finish etc Control of charge reduced interrupted deferred charging based on the in put from the EVSP or third party is performed by the EVSE operator EVSE operator is able to collect transfer and upload charge data user ID con tract details charge profile charge report data etc between EVSE car and other parties EVSPs clearinghouse etc Failure outcomes Failure Outcome Condition leading to outcome Access not No service is provided e Incompatibility in hardware or com granted munication Charging is Service delivery inter e EVSE operator not responding interrupted rupted e DSO EVSE operator or user inter venes e Damaged connection hardware or software re Primary actor 1406 ACT EVSE Backend 1407 ACT EVSP backend 133 ACT Vehicle Driver Secondary actor 129 ACT DSO Distribution system operator 132 ACT EVSE Operator 128 ACT EVSP Electric Vehicle Service Provider 140 ACT Clearinghouse Main scenario EV driver connects EV to EVSE and EVSE operator Charge plan constructed Charging managed according to charge plan EVSE operator monitors and distributes charge data to relevant actors EV driver disconnects EV from
260. t Framework Condition leading to outcome Fats en Hem erre 1355 ACT Business Partner 367 ACT Marketplace Business Operator Main scenario e The Business Partner chooses the details view of the contents with all available options of the Service Contract Framework The detail view is displayed Alternatives Related informa tion Access Role Based Authorization required Data Security Data Integrity must be guaranteed Data Confidentiality must be ensured Data Privacy Sensitive Data is only stored when needed and authorized Data Export Policy required Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 126 of 210 Green I eMotion EG AL LY 6 3 11 1396 FTR Define and Register Service Contract During the service registration process the Service Provider has to establish a Service Contract Offering based on the Service Contract Framework The Service Provider chooses the necessary modules from the Service Contract Framework This may include optional modules that can be chosen by the Service Requester service con tract variations He provides an offering of a set of service contracts e The Service Requester can choose from the set of Service Con tract Offerings and has to accept at least one 6 3 11 1 1485 UC Create Service Contrac
261. t Service Contracts This Use Case is listed before in this Chapter please refer to paragraph 6 3 5 3 Scope amp Level Core Service Find Service Contracts that satisfy search criteria 6 3 12 5 1247 UC Confirm Service Contract Change Goal in context A change of a bilateral Service Contract is a two step process A Business Partner Service Provider or Service Requester accepts or rejects a change request on a Service Contract made by the other Business Partner Preconditions e A Service Contract between the Service Provider and the Service Requester exists e The Business Partner has been notified of a change request on the Service Contract GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 131 of 210 Green N eMotion EN AL V Successful out The change request e g terms amp conditions pricing on a Service Contract is come accepted or rejected by the other Business Partner Failure outcome Failure Outcome Condition leading to outcome 1355 ACT Business Partner 137 ACT Service Provider or 138 ACT Service Re quester The Business Partner accepts or rejects the change request on the Service Contract The Service Contract is changed A Service Contract History Entry is created The other Business Partner is notified Alternatives Related informa tion Access Role Based Authorization required Data Security Data Integrity must be guaranteed Data Confidentiality must be ensured Data
262. t users e g in innovative car on demand pools may have different re quirements regarding space and trunk capacity or range for single trips Hence a vehicle reservation out of such a fleet should allow a search based on these criteria OEMs provide access to car information Successful out User gets car information come Failure outcomes Failure Ge Condition leading to out come No access to No information is shown to the Network issues car information user user can also be a system Backend issues Additional services that rely on Car issues this feature may be affected Infrastructure issues Primary actor 133 ACT Vehicle Driver 137 ACT Service Provider 136 ACT Marketplace Operator 1594 ACT Fleetmanager Secondary actors 134 ACT OEM Main scenario Increase convenience for fleet user Alternatives Direct lookup in the car itself Estimation based on underlying conditions Variations FESTE Related informa tion Issues 3 4 2 1303 FTR Intermodality planning Planning of travels that include different means of transportation e g EV Bus Train Taxi Plane Bike This component should enable to determine the best transportation combinations based on the user s travel request and his preferences GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 57 of 210 eMotion A Green N EI 7 Examples for user preferences e travel duration CO2 emissions travel distance costs comfort 3 4 2 1
263. tablished The sending device is damaged GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 47 of 210 Green N eMotion BG V The request is not Display of an error message The marketplace or acknowledged The request is stored and will the Assistance Ser be sent again after a defined vice is temporarily not period of time available Primary actor 143 ACT EV 133 ACT Vehicle Driver Secondary actors 128 ACT EVSP Electric Vehicle Service Provider 137 ACT Service Provider on the marketplace 1579 ACT Third Party Service Provider Roadside Assistance Service Center The transmission of Display of an error message The mobile network the request is inter The request is stored and will connection is inter rupted be sent again after a defined rupted period of time until it succeeds or a maximum number of re tries is exceeded Main scenario The driver initiates the roadside assistance request The request is received by the marketplace and forwarded to a Roadside As sistance service center The assistance request is acknowledged through the marketplace Please refer to Figure 23 Call for Roadside Assistance in the Appendix for more information Alternatives fT Variations J O Related informa The request and the current position of the vehicle aretransmitted to a Roadside tion Assistance Service Center through the marketplace A voice call can be initiated to ask for the current situation if
264. tective earth conductors the EV Vehicle Supply the EV and the Grid This can be both couplers attached plugs and all other accessories devices power outlets or appa Equipment slow chargers fast chargers and ratuses installed specifically for the purpose of delivering energy from the premises battery switch stations wiring to the EV and allowing communication between them as necessary Relevant Standards ISO 61581 series conductive charging system ISO 15118 series use cases connectivity identification 132 ACT EVSE Operator in charge of managing the EVSEs N A 1406 ACT EVSE Operator Backend administrative systems of N A Backend the EVSE Operator as opposed to frontend on site systems that com municate directly with EV s 128 ACT EVSP Electric offers e mobility services to the end Legal entity that the customer has a contract with for all services related to the EV Vehicle Service customers operation Provider 1407 ACT EVSP Backend Backend administrative systems of N A the EVSP 1594 ACT Fleet manager Organization that manages a fleet of Can be a part of an EVSP an OEM or any other party in the EV market EV s 1540 ACT HMI Human interface allowing the vehicle user to N A Machine Interface receive information relative to the charging process and provide input to the charging system 1367 ACT Marketplace A special kind of the Marketplace The Marketplace Business Operator is a Marketplace Operator with the fo
265. teral agreement between an EVSE operator and an EVSP or with a Clearing House to handle the contractual and or financial clearing between the EVSE operator and the EVSP These two variations are illustrated below EVSE Operator 1 Operation Center Operation Center Communication line Figure 14 Two Roaming variations Note In the 2nd release further use cases and features of roaming will be developed and demonstrated reflecting the experiences with bilateral roaming roaming facilitated by clearing house and open access in release 1 The two main processes in Contractual Clearing are Authorization and CDR forwarding The following paragraphs and process diagrams show the tasks each role has to execute in order to complete the process 4 1 1 Authorization As a first step an EV driver has to identify himself The identification method used e g RFID card is not relevant to the authorization process itself The identity information includes a ContractlD but no details about the contract Once the EV driver is identified the EVSE can apply an internal white or blacklist to perform a pre check for that particular card If the identity is in a white list the charging process can start immediately GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 66 of 210 Green N EA 2 eMotion LY Figure 15 Roaming Domain Authorization Process GA MOVE FP7 265499 Green eMotion
266. ternative services are expected to be documented based on the feedback of the partners and demo regions after their experience with the first release Second phase of the requirements will be similarly as the current phase further detailed by the IT developers during the second specification phase which will lead to a second release of the Marketplace Deliverable D3 3 is based on a tool used within the project Herewith the re use of content for all partners in WP3 is possible The document itself is a comprehensive export document requiring the reader to un derstand its structure to be able to retrieve desired information efficiently Read the table at the beginning of each chapter to search for the service and then refer to the table of contents for its location For de tailed information and for hints on efficient retrieving of content please refer to the section How to read this document at the end of this Introduction chapter To facilitate the requirements gathering process 4 functional domains were derived from the stakeholders WP3 partners expertise areas The structure of this document reflects this classification of requirements A more detailed description of the grouping and hierarchy of the requirements by their context are pre sented in this introductory chapter separately in the section Division into functional domains Two distinct methodologies were used to define these groups of requirements e Structured Requirements
267. ters the edit mode of a car user changes the status of a car i e to in maintenance user saves car data GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 60 of 210 Green N eMotion BG LY Alternatives Deletion of cars from system manual logbook Status is set by the driver in the car directly Related informa tion Issues 3 4 3 4 1523 UC Fleet manager tracks pool car Scope amp Level Value Added Service Tracking of cars Goal in context Tracking of cars the system submits the whereabouts of each car either by GPS GSM or when plugged to EVSE identification through Vehicle Identification Number location through EVSE location The Fleet Mgr is able to track the cars down Pool cars available system is available Fleet Manager is in place Cars communi cate at least their Status of charge and the vehicle identification number Fleet Mgr knows where the cars are located and is able to allocate them efficiently come a tome outcome Tracking not Car location cannot be tracked Ad Backend issues possible ditional Services such as planning Network issues algorithms may be affected Car issues Weather issues Location issues i see a ee FS MESE 1594 ACT Fleetmanager 132 ACT EVSE Operator 128 ACT EVSP Electric Vehicle Service Provider as Fleet Provider Main scenario fleet manager enters the tracking menu of the fleet management system fleet ue manager looks at the current
268. tery switching The following picture illustrates the relations among these three groups of scenarios CHARGING Scenario Basic Functional Charging Charging Enhancement Localization Semi Public Public Figure 4 Structure of the Charging Domain GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 18 of 210 Green N eMotion Ea on 1 BS When considering the end user perspective and the timeline of the charging cycle we have decided to cluster most of the charging features around three main phases of the charging process to obtained three groups sub chapters The First group of features services includes those that the end user is interested in before connecting his vehicle to a charging point services related to a search and navigation to a suit able EVSE The Second group of services includes those that are related to the actual process of a particular charge session from the moment of connecting the vehicle to the charging point until and including its disconnec tion These services include communication with the end user about the status of charge control of charging monitoring and collection of charge related data The Third group of features is formed by the services that summarize charging sessions and includes analytics and reporting about service consumption these are described in an After Charging use case Between the first Before Charging and the second During Charging phases there may be an
269. the EVSEs between the EVSE Op back end the EVSP back end and the electric mobility marketplace and a direct interaction between the EVSE Op back end and the DSO front end in order to demand the bidirectional flow this feature may be a special condition of V2G capabil ity The EVSP succeeds in provisioning ancillary services to the DSO by dealing with its specific network safety and quality of service related needs Condition leading to outcome EV and EVSE cannot commu There would be no Lack of communication nicate the reverse flow of en chance to feed back or lack of compliancy to ergy condition energy into the grid 18015118 where EV EVSE communication is available EVSP cannot use EV for V2G The EV User does not Absence of V2G condi allow to feed energy tion in the contract from his EV to the grid EVSP release V2G without The EVSP force EVs Lack of regulation for V2G safety check to feed energy back into the LV grid ndary ac 132 ACT EVSE Operator 129 ACT DSO Distribution System Operator GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 90 of 210 Green DN eMotion Ea N 4 Main scenario When V2G is allowed and technically supported the EV may act as a prosumer con trolled by EVSPs that use the EVSE energy gateway in order to deliver network safety and quality of service benefits to the DSO An EVSP acting as aggregator offers reactive power from the aggregated flexible load under its control sim
270. thod for assessing the status of the requirement and if it has truly been implemented The RRC enabled WP3 sub teams to gain visibility into project progress and status and was tightly integrated with the quality management process Several examples on how the RRC tool interfaces look like can be found in a figure below Capture connect organize and collaborate sasas cC Document dm ui Sketch Tracing Dashboard Use Case ctoriboard Review amp Approve 4 ILS Ei Y 3 Business Process Screen Flow Guide teams to execution Requirements Plans Tests and Work Items Figure 1 Structured Requirements Management At the beginning of the team work the WP3 team attended three conference calls to get acquainted with the Rational requirements composer RRC the meaning and purpose of the artifacts and the meta model Using a work flow based on the meta model the scenario s from D3 1 were enhanced and broken down into contextual blocks and Features what must a component be capable of Business Objects sources or carriers of information and Business Rules logic constraints on the scenario s were added In many cases Business Process Diagrams were created to document and explain the more com plex scenarios The Features were then allocated to WP3 partners assigned ownership of content to further detail each Feature into one or more Use Cases To ensure involvement of a
271. ties start with analyzing the actors and the tasks they need to perform with the future software as illustrated by the following picture Actors User Roles amp Task Cases Abstract Prototypes amp Visual Prototypes Visual Design Working Prototype mR pa Task Map oe REQUIREMENTS REQUIREMENTS DEFINITION ANALYSIS IMPLEMENTATION TEST Figure 3 Usability Engineering Methodology In this methodology Actors are persons human beings no system actors using the future software such as network operators User roles describe the relationship between the software and the actor for example monitoring energy network The identification of actors and roles allows us to verify that the requirements are complete and enables us to decide on the essentials needed for the future system Task cases are performed by the actor in roles The task case models the what and why of the soft ware use rather than the how Task cases are comparable to essential use cases as they focus on the essentials of the requirements Each task case describes what the user wants to do in order to fulfill the task user intention and what the future software needs to do to support task completion system respon sibility Task cases are abstract simplified and technology free The description allows the project team to focus on the essential user needs resulting from the task The technical feasibility is examined in later step
272. tion WP 3 Deliverable 3 3 Page 115 of 210 Green N eMotion EG AL V download e The Service Requester starts the download Alternatives FEE a EE Related informa tion Access Role Based Authorization required Data Security Data Integrity must be guaranteed Data Confidentiality must be ensured Availability 24 7 availability required Scalability capable to grow with electro mobility market 6 3 5 926 FTR Call of Service The GeM Marketplace enables calls of services that occur when a Service Requester consumes the EV Service based upon the conditions of a Service Contract The GeM Marketplace links the service calls of the requester to the corresponding Service Providers based on existing Service Contracts 6 3 5 1 1491 UC Create Service Transaction Scope amp Level Goal in context During a service call of a Service by the Service Requester a Service Transaction Entry is created A valid call of a Service was performed by a Service Requester come MN 100 outcome dd pp Ere 9 3 gt Err 138 ACT Service Requester SG EEE Secondary actor Main scenario After a valid service call a Service Transaction Entry is created and stored by the marketplace Alternatives Ea Variations J 0000000000000 Related informa Service calls with failures have to be logged separately tion Data Privacy Sensitive Data is only stored when needed and authorized Data Export Policy required Perf
273. to perform active grid management by the DSO who would reward the provider of such availability Obviously this is a condition that triggers several requirements in the whole architecture of EV ecosystem In addition there are multiple ancillary services that can be provided to the DSO by EVSPs in the role of aggregator and in this way locally improve the quality of distributed electricity From the trading perspective there is a similar service however provided to the TSO or to a party responsible for its own energy profile This ser vice is called Aggregated balancing to the TSO 5 1 3 Marketplace context The list of services described in this chapter is not exhaustive Currently these services satisfy Business scenarios across the Energy and Charging domains see appendix E through the features listed in the table below The major use cases that realize the functions described in this chapter and enable the ser vices outlined above are 1601 Provide balancing capacity 1602 Flexible load for congestion manage ment and 1597 Peak shaving 5 2 Actors The following table lists the identified Actors in the Energy domain ID Actor Description 129 ACT DSO Distribution system operator Provides the power connection point to the charging spot 130 ACT Energy retailer Delivers electricity to the charging spot 143 ACT EV Electric Vehicle Provides access to the vehicle data 131 ACT EVSE Electric Vehicle Supply E
274. to retrieve charging behavior of the average customer i e meaningful information could be that most of the people may unplug their vehicle once it reaches 5096 recharge 5 3 11 1 1524 UC Fleet manager monitors energy consumption of pool cars This Use Case is listed before in Chapter 3Driving and cross domain use case model please refer to paragraph 3 4 3 5 Value Added Service Monitoring of energy consumption for single cars or the whole fleet Ps 3 11 2 1999 UC Aggregated EV charge overview by the DSO Value added service The overview of current EV charge is meaningful information that an EVSP acting as Service Provider in the marketplace can use in order to deliver benefits to its customers and sell or support services for others business actors in the electric mobility market This use case creates and distributes through Marketplace the aggregated current charging information of EVs in the area of a DSO The service could be used by a Service Requestor such as the TSO or an Energy Vendor according to the regula tory framework to monitor the power eventually available after the network safety and quality preconditioning made by the DSO This service could also be used for marketing purposes by OEMs in order to influ ence charging behavior of the average customer e g people may unplug their vehicle once it reaches 50 recharge The status of charge is available within the communication data exchanged between EV and EVSE 18
275. to the secondary actor for validation The secondary actor replies with an agreement or non agreement Service starts after successful authorization of the IDs Alternatives ped EVSE Operator and EVCC may exchange information e g Contract ID directly Related informa A user can have multiple contracts tion Issues Security and privacy GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 32 of 210 Green N eMotion Ea FA V 2 5 Services during charging EV connect disconnect 2 5 4 During Charging Overview Business services described in this chapter support the charging cycle between the moment when the driver parks his car and connects to a charging point to the time when he disconnects and physi cally leaves the parking space At the implementation of these services in different demo regions there is expected some overlap between During charging and After charging service described in the next sec tion In the figure below the area in the blue square illustrates the part of the charging cycle timeline during the charging process 1 User parks EV near ser connects EVto User is goodtogo Charging can may or may not User disconnects EV EV is parked an available charge charge socket EV lights blink due to occur from charge socket disconnected from socket immediate charge user might connect the charge socket cable back right again Parking cycle Charge cycle Parking cycle Conne
276. ttery switch station Type of plug e g Type 2 3 household optional mapping with characters from EV Charging power e g 32 ampere optional mapping with characters from EV Phases 1 phased or 3 phases Access EVSP EVSE e g RWE Better Place membership open access Special energy attributes e g green energy nuclear energy Price Per kWh Per hour parking fixed fee etc The search function can be supported from different end user applications o Smart Phone e g iPhone Android o Internet customer portal o In Car application e g onboard unit The result can be shown on a Geo Map e g Google Maps Bing Teleatlas or and in a text table All relevant information e g address charging plug has to be in cluded An EV driver wants to search for an EVSE location in order to increase range of the vehicle The goal of this use case is to enable the EV driver to select from multiple recharging attributes and filter his search by these Preconditions The EVSEs have a communication to a backend system of the EVSE operator e g Charging management system Infrastructure management system IMS The EVSEs have a unique ID grid ID Access to data about the EVSEs e g type of station type of plug charge power exact location prices services energy source EV driver application is integrated Successful out Find a suitable EVSE come Failure outcomes _ Failure Outcome Condition leading to outcome MEN EV
277. ue added service This use case enables the DSO or other energy stakeholders to distribute the need for congestion management to multiple service providers through the marketplace 5 3 14 967 FTR History of EVSE use The historical use of EVSEs is a sensible information that an EVSE Operator acting as Service Provider in the marketplace can use in order to deliver benefits to its customers and sell or support services for others business actors in the electric mobility market EVSE History must contain e time stamp EVSP ID implicit for single EVSP EVSE s geographical load area energy consumed quality of service i e out of service outage charging status failed authorization attempts V2G historical use Such a feature requires that the EVSE is able to deal with charging information so the recharging infra structure is expected to be a smart one with embedded communication capabilities Also B2B relation ships between EVSP and EVSE Op must guarantee access to part of the information enrolled above i e the charging status This information can be aggregated either per EVSE or per geographical load area from the EVSE Op back end and made available as content for a dedicated service to be run in the marketplace Therefore it is the EVSE Op who acts as Service Providers and care about the aggregation and migration of data by updating the content of the service This service can be requested from other actors in the ma
278. user and search reser vation of Charging spots EVSE e EVSE bidirectional e Clearinghouse bidirectional e e Vehicle end user customer portal For the reporting of the Charging Sessions the EVSE operator can analyze the ac tual and historical data within the Charging Location Management application Goal in context A charging location is a site with charging points usually run by EVSE Operators Every charging location needs a management component that enables site monitoring controlling and communication with the marketplace This component also makes customer authentication requests to the clearinghouse The goal of Charging Location Management use case is to control and monitor charge sessions processes as well as to transfer values and status messages from the CP EVSE to third parties e Interface to Charging Spots come ontrolling of Charging spots Failure outcomes Failure Outcome Condition leading to outcome No connection Remote monitoring and con e Damaged hardware to CP trol of CP via Charging Loca e Interrupted connection tion Management application e Incompatible software version not possible ac pem Primaryactor Oooo 2 2 CONI EE ees Primary actor 131 ACT EVSE Electric Vehicle Supply Equipment Secondary actors 128 ACT EVSP Electric Vehicle Service Provider 129 ACT DSO Distribution system operator 133 ACT Vehicle Driver Main scenario e Registration
279. uspended or resumed by the Service Requester Failure outcome Failure Outcome Condition leading to outcome pop eee GE LLL LL LZ I ENS Secondary actors 1 1 1 1 1 1 1 Main scenario e The Service Requester marks the Service Contract as suspended re spectively for use e An Service Contract History Entry is created Alternatives GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 133 of 210 Green I eMotion EA AL V Variations Related information Is the Service Provider able to view the suspended contracts of his own services Access Role Based Authorization required Data Security Data Integrity must be guaranteed Data Confidentiality must be ensured Data Privacy Sensitive Data is only stored when needed and authorized Data Export Policy required Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market 6 3 14 1315 FTR Register Service Any Service Provider can register an EV Service at the Marketplace This can be a completely new ser vice or a new version of an existing service The registration of a service includes the following actions e Providing the Service Interface and a Service Description The Service Interface should be a Standa
280. voltage grid A fundamental prerequisite for this feature to take place is that the regulatory framework al lows that distributed generation units connected to the mid low voltage grid inject power with a signifi cant reactive content In fact nowadays most regulators forbid injection of power under a Cos Phi of 0 9 which means embedded with an insignificant amount of reactive power An EVSP acting as aggregator offers reactive power from the aggregated flexible load under its control similarly to other ancillary services to the DSO The DSO evaluates whether or not such an offer of ag gregated power is valuable to increase the quality of service in a specific load area by matching with the capability of bidirectional flow of energy of the EVSEs involved Such a feature obviously requires a communication layer to be established on top of the EVSEs between the EVSE Op back end the EVSP back end and the electric mobility marketplace and an direct interac tion between the EVSE Op back end and the DSO front end in order to demand the bidirectional flow this feature may be a special condition of V2G capability Provision of reactive power will reduce losses and the DSO will reward the EVSP based on savings it can reach by the reduction of losses 5 3 3 1 1605 UC Reserve and activate ancillary services Scope amp Level Value Added service An EVSP offers aggregated flexible load as ancillary service to the DSO in order to help the DS
281. when a service is contracted between consumer A and provider B but is delivered to consumer A by provider C based on a contract between provider B and provider C The following picture illustrates the Roaming Process EVSE Operator Energy Supplier A Energy Supplier B Nu Operation Center Communication line 9 EYSH s alsa en EVSE Operator Energy line Figure 12 Roaming as defined by Betterplace The Roaming functional domain is divided into two different clearing aspects the Contractual Clearing and the Financial Clearing as well as two different localization approaches the intra country and inter county roaming Roaming Scenario Contractual Financial clearing clearing Roaming between countries Roaming between EVSP s Figure 13 Structure of the Roaming Domain GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 65 of 210 Green NN Ka 7 eMotion LY RTT raamt ibn Contractual Clearing deals with validation of contracts between different EVSE Operators and EVSPs as well as their respective customers This aspect is the most important one for the Green eMotion project in order to be able to charge at different EVSE using one single contract with one EVSP The Financial Clearing which deals with a consolidated rating and billing will be only discussed but most probably not realized From the localization perspective both approaches will be realized Roaming services can be handled in a bila
282. witching 1810 FTR EVSE Service Delivery 1808 FTR Find Appropriate Charge Point Battery Station 966 FTR Current EV charge 978 FTR Search for charge point or battery switch station GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 197 of 210 Green eMotion Ea L VL ID Business Scenario Description Satisfied By 1161 BS R1 Contractual clearing Roaming both between EVSE op 983 FTR CLEARING Managing customer data erators and between coun tries regions concerning contrac tual clearing 979 FTR Authentication of user 1808 FTR Find Appropriate Charge Point Battery Station 1291 FTR CLEARING Managing EVSP data 986 FTR Roaming in different countries 1804 FTR Roaming based on Bi lateral Agreements 985 FTR Roaming in same country 984 FTR CLEARING Forwarding CDR 982 FTR CLEARING Validation of contract 981 FTR Authentication 1182 BS R3a Differentiation of customer contracts SLA check handling of different standard level agreements 564 FTR SLA 1811 FTR EVSE Service Control 562 FTR Low priority charging 558 FTR Increase the load of charging 979 FTR Authentication of user 557 FTR Reduce load of charging 1173 BS S1 Marketplace Buying Selling Routing Value added service are offered bought and paid for 1469 FTR Suspend Resume Service Contract 926 FTR Call of Service 924 FTR Search and Select Service 1459 FTR Aggregate Service Call Results 1315 FTR Register
283. y 6 3 9 3 1242 UC Search and Select Service Transactions Preconditions e The searching actor is a representative of the Business Partner of the marketplace or the Marketplace Business Operator e The Business Partner has a valid or terminated Service Contract belong ing to the Service Successful out The Business Partner receives an ordered list of his own Service that meets his come search criteria and is able to export the list E g search criteria may include e Service Transactions of a given Service i e of a given Service Contract e Service Transactions of services of a given Business Partner e Service Transactions in a given time frame Failure outcome Failue Outcome Condition leading to outcome No Service Transactions Display of an er There are no service transactions are found ror message that meet the search criteria 1355 ACT Business Partner Secondary actors 1367 ACT Marketplace Business Operator Main scenario e The Business Partner fills the search criteria or load search criteria saved before e The marketplace returns a list of Service Transactions that meet the search criteria e The Business Partner stores optionally the entered search criteria for later use e The search result can be exported Alternatives The Marketplace Business Operator is able to receive a list of all Service Transac tions mm Related informa tion Issues 1 Access Role Based Authorization required GA
284. y required Performance sub second response for Service Transactions incl Marketplace Availability 24 7 availability required Scalability capable to grow with electro mobility market 6 3 20 3 1377 UC View Business Partner Account Details Scope amp Level Core Service Goal in context View details of a Business Partner Preconditions e The actor is a representative of a Business Partner of the marketplace or the Marketplace Business Operator e A Business Partner is chosen Successful outcome The Business Partner views the details of a Business Partner or his own details In case of his own data he will view his Partner Contract as well Failure outcome Failure Outcome Condition leading to outcome 1355 ACT Business Partner 1367 ACT Marketplace Business Operator Main scenario e The Business Partner chooses the details view of a Business Partner or his own details e The detail view is displayed Alternatives Br Variations The Marketplace Business Operator is able to view all data of the Business Part ners and their Partner Contracts Related information Access Role Based Authorization required Data Security Data Integrity must be guaranteed Data Confidentiality must be ensured Data Privacy Sensitive Data is only stored when needed and authorized Data Export Policy required GA MOVE FP7 265499 Green eMotion WP 3 Deliverable 3 3 Page 148 of 210
285. y with strong background in the specific domain e Charging Domain working group was led by Betterplace and Siemens Driving Domain was teamwork and derived by the use of a structured approach in RRC Roaming Domain working group was led by SAP Energy Domain working group was led by Enel Marketplace Domain working group was led by IBM Although these domains are inseparable for EV and contain substantial overlap this approach made it possible to create substantial progress in a short time frame The coherence was achieved by joint work ing sessions and by the participation of stakeholders across all working groups This structure is also clearly visible in the design of this document The Charging Domain is described in Chapter 2 This domain contains a large variety of features with a natural grouping based on the phasing of the extended charging process To improve readability Chapter 2 is divided into separate sections for Before Charging requirements search for Charging Point reserve navigate Authorization During Charging requirements monitoring communication with driver control of load After charging analysis The Driving Domain of Chapter 3 describe common features like parking management vehicle track ing and others which include on the end user side intermodality planning extended search beyond e mobility and also on the business to business side fleet management and CO2 reporting The Roaming Domain is elaborated in C

D3.3-Business Services Use Cases and

Contents

Download Pdf Manuals

Related Search

Related Contents