Keba KeContact Series - Page 74

Load management program
74 / 156
Automatically accepts token?
Decides whether a Charging Token is generated by plugging in an Elec-
tric Vehicle into a Socket with enabled Authorization.
Automatic acceptance dura-
tion:
Default value for the number of days until expiration of a Charging Token
that will be automatically created.
Default expiry period:
Default value for the number of days a Charging Token will be considered
accepted if no expiration date is delivered to the Charge Point when au-
thenticating the Charging Token.
May change imported
white lists?
Indicates whether it is possible to edit imported white lists.
(*) This options are only active if “Authorization enabled?” = “Yes”.
Buttons
Save:
Press the [Save] button to save the configuration data.
- Pressing the "Save" button affects all tabs of the screen.
-Generate Charging Tokens, Acceptance Duration and Automatically
accepts token are only relevant for Charge Points that authorizes using
PEV-ID.
Additional information:
The KeContact M10 provides functions to ensure that only drivers entitled to use the charge point may
charge their electric vehicles. The following mechanisms are supported:
 RFID: The user may swipe a RFID contained in the white list of the KeContact M10. If the KeContact
M10 is connected to an optional central administration system using its OCPP system management in-
terface, the KeContact M10 will inquire the white list of the central system if the RFID is not contained in
the white list of the KeContact M10.
 EVCCID (PEV-ID): The KeContact M10 supports ISO/IEC 15118 Plug&Charge using a vehicle ID (PEV-
ID or in newer versions of the ISO/IEC 15118 standard EVCCID). During setup of an ISO/IEC 15118
charging session, the KeContact M10 compares the vehicle ID passed by the electric vehicle with its in-
ternal white list. As with RFIDs, the KeContact M10 can also inquire the white list of a central manage-
ment system if the vehicle ID is not contained in the internal white list of the KeContact M10.
 GUI: The KeContact M10 provides a GUI screen allowing a system administrator to approve an electric
vehicle for charging. For example, this can be used if the driver has forgotten her or his RFID.
 Central System: A central system may approve an ongoing charging session that could not be author-
ized locally using the OCPP system management interface. For example, this can be used from a call
centre.
The charging tokens (RFID or vehicle ID) that can be used to authorize a charging session are maintained
in a white list stored at the KeContact M10. A white list entry may be entered at the GUI of the KeContact
M10, imported from a file that is uploaded from the Web GUI or at the OCPP system management interface
of the KeContact M10. In addition, it is possible to "teach" vehicle IDs to a KeContact M10.
It is possible to switch off authorization for a charge point or an individual Wallbox.