EV Charge Web Docs | Tridens Technology –

Docs: Chargers

Mon, 01 Jan 0001 00:00:00 +0000

To access this section in EV Charge, from the Menu, select Operations, and click Chargers. A paginated list of all chargers is shown in a tabular format.

To generate the chargers list in a spreadsheet, click CSV. To print, click Print, and to copy, click Copy.

Note:

They are generated, printed, and copied per paginated page.

Information:

You can filter for a charger by name, serial number, model, vendor, operational status, or/and charging status.

To see the list of connectors found in a charger, click Expand.

Both chargers and connectors can be turned on/off. To achieve this, click Request availability change. Turning off a connector will send a request to the charger via OCPP to make that part inoperative.

Turning a charger/connector on/off is the same as making it available or unavailable to end users. Unavailable chargers in the EV Charge - Mobile App cannot be used to start a session.

Change availability is the operation (based on OCPP) which provides an operator to manage the availability of the connected charging device from the Tridens EV Charge’s central system. Operation offers to request the connected charging device to change the availability of the charger or specific connector from Unavailable to Available and vice-versa.

Note:

Please note that this feature can not be used if the charging device is not connected with the central system, as in that case the central system does not have any control over the charging device.

Tip:

Turning a charger/connector on/off can be helpful during maintenance.

Furthermore, a connector can be locked/unlocked by clicking .

Some EV chargers lock the connector to prevent it from being removed during charging for safety purposes. The lock/unlock action manually triggers that process. It is typically used for debugging or resolution if the charger does not release the connector due to a malfunction.

Docs: Charging Session Integration

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

Session Start Timeout
Driver Authorization
Offline Sessions
Meter Values Reporting
Session Event Retry

Session Start Timeout

Please ensure to configure the session start timeout period on charger side. It covers the time available to start the session, since the acceptance of remote start request or driver authorization.

Remote session start and authorization timeout on charger side represents the time since OCPP RemoteStartTransaction/Authorization acceptance, after which session must be started. If this time is breached, the charger should prevent any session start without the next OCPP RemoteStartTransaction or Authorization operation acceptance.

To avoid fraudulent usage, we suggest using preventive measures by configuring the charger’s timeout period in which the session is expected to start. OCPP 1.6 has a ConnectionTimeOut setting, which can be used, as described below.

Charger may also have other settings which are not part of OCPP 1.6 to handle other preventive scenarios - to tackle those, please check the charger’s specific manual or consult with the manufacturer.

OCPP 1.6 requires support for ConnectionTimeOut setting: Interval in seconds from beginning of status: ‘Preparing’ until incipient Transaction is automatically canceled, due to failure of EV driver to (correctly) insert the charging cable connector(s) into the appropriate socket(s). The Charge Point SHALL go back to the original state, probably: ‘Available’.

Session timeout section is related to ready-session-expiration settings of the central system, as it closes inactive sessions based on the expiration settings and idle job configuration. Make sure to use the consistent ready-session-expiration time on the central system, so it works aligned with the charger.

Example:

The EV driver plugs the connector with the vehicle. Then the driver presses the session start request button on the mobile application, and at this point, session is ready. Ready session expiration time of 30 seconds starts ticking. If it reaches 30 seconds and session did not start yet, then the session gets closed on the central system side and is not being tracked anymore.

Note:

If you experience the session without a customer reference, you need to make sure to configure the suitable timeout settings in dependence with ready-session-expiration settings.

Driver Authorization

As the drivers/customers who intend to charge the vehicle may use the payment types of prepaid, postpaid or pay-now, each session charging needs to be first authorized by the Tridens EV Charge’s central system to verify the driver’s fund sufficiency for beginning the charging session. Thus, charger’s local and offline authorizations lists and caches need to be disabled, to propagate all the authorizations to the central system.

Below is the list of OCPP 1.6 and OCPP 2.0.1 standardized authorization settings. Note that the chargers may have their own customized list of configuration settings, out of standardized scope. As a CPO, please review the charger specific implementation for any additional settings that need to be managed.

Configuration Attribute Name	Description	Restriction	OCPP 1.6 Variable Name	OCPP 2.0.1 Variable Name
Authorize Remote Session Requests	Indicates whether remote start requests need to be authorized by the charger before proceeding to charge.	Set to true, to ensure that the session is still authorized to start.	`AuthorizeRemoteTxRequests`	`AuthorizeRemoteStart`
Authorization Cache Enabled	Indicates whether the charger supports the authorization cache for the driver’s identifiers.	Set to false, to prevent using charger’s local authorization caches.	`AuthorizationCacheEnabled`	`AuthCacheEnabled`
Local Offline Authorization	Indicates whether the charger, when offline, will start a transaction for locally authorized identifiers.	Set to false, to prevent using charger’s local authorization caches.	`LocalAuthorizeOffline`	`LocalAuthorizeOffline`
Allow Offline Session of Unknown Driver	Indicates whether the charger allows authorizing any unknown identifiers that cannot be authorized by local authorization list or authorization cache.	Set to false, to prevent any unverified sessions.	`AllowOfflineTxForUnknownId`	`OfflineTxForUnknownIdEnabled`
Central Contract Validation	Indicates whether the Charge Point can provide a contract certificate that it cannot validate to the Central System for validation as part of the authorization. Used in the scope of ISO 15118’s Plug & Charge.	Set to true, so the central system’s verification is used.	`CentralContractValidationAllowed`	`CentralContractValidationAllowed`
Offline Contract Validation	Indicates whether the charge point will try to validate a contract certificate when it is offline (not connected to the central system). Used in the scope of ISO 15118’s Plug & Charge.	Set to false, so the central system’s verification is used.	`ContractValidationOffline`	`ContractValidationOffline`

Table 1: List of authorization settings to manage in OCPP 1.6 and 2.0.1.

Offline Sessions

Disable the charger to start the charging sessions without allowance of the central system, as it would result in non-customer public sessions.

Make sure to disable LocalAuthorizeOffline and AllowOfflineTxForUnknownId settings of OCPP 1.6 on the charger side.

CPO needs to review the charger specific implementation and configuration, as other settings out of standardized scope may apply.

Meter Values Reporting

Configure session meter values report interval on the charger, so the session’s progress will show up. We advise using a 15 seconds interval. You can usually configure this on the charger’s own dashboard, or use EV Charge dashboard, which can do it by OCPP.

To access this section in EV Charge, from the Menu, click Stations. A paginated list of all stations is shown in a tabular format. Click Actions for the specific station. On the station’s page, click Configuration on the top right corner to access Configuration page, then select Meter tab to regulate the sampling interval. Alternatively, the Custom tab can also be used for this.

Figure 1: Example of setting the interval in the Station’s Configuration form on Tridens EV Charge dashboard.

Note:

The settings can be set by the central system to the charger only when charger is connected to the central system and communicating by OCPP protocol.

To show active power measurement in mobile app, CPO needs to configure the charger to send the certain measurements in scope of the charging session (usually at least kW for power and kWh for energy). Once again, this is usually doable by the charger’s dashboard or EV Charge dashboard, where OCPP’s MeterValuesSampledData setting can be used.

To navigate to this area in EV Charge, go to the Menu and select Stations. You’ll see a paginated list of all stations in a tabular format. Click on Actions for the specific station. Once on the station’s page, on the the top right corner access the Configuration page, then select Meter tab to regulate the sampling measurands. Alternatively, the Custom tab at the top right corner can also be used.

Figure 2: Example of setting measurands in the Station’s Configuration form on Tridens EV Charge dashboard.

Note:

The settings can only be configured by the central system to the charger when the charger is connected to the central system and actively communicating via the OCPP protocol.

Important measurands to cope with:

Name	Description	OCPP 1.6 Name	OCPP 2.0.1 Name
Energy Import	Instantaneous imported energy (Wh or kWh) to the vehicle.	`Energy.Active.Import.Interval`	`Energy.Active.Import.Interval`
Power Import	Instantaneous power (W or kW) import to the EV.	`Power.Active.Import`	`Power.Active.Import`
Current Import	Instantaneous current (A) import to the EV.	`Current.Import`	`Current.Import`
Voltage	Instantaneous voltage (V) supply between grid and EV.	`Voltage`	`Voltage`
Battery State of Charge	Percentage representing the vehicle’s battery state of charge.	`SoC`	`SoC`

Table 2: List of measurands settings in OCPP 1.6 and 2.0.1.

Meter values which are related to the specific charging session and representing measurands related to it.

Session Meter Values Interval

Interval in seconds, by which the charger will send the meter value reports to the central system during the charging session. Suggested interval is 10-15 seconds.

Refers to MeterValueSampleInterval of OCPP 1.6 and SampledDataTxUpdatedInterval of OCPP 2.0.1.

Session Meter Values Measurands

Measurands which the charger will send on ‘Session meter values interval’. Suggested: power, energy, state of charge, voltage, current.

Refers to MeterValuesSampledData of OCPP 1.6 and SampledDataTxUpdatedMeasurands of OCPP 2.0.1.

General Meter Values

General meter values are reported independent of the session and may be required in the scenarios of the sessions which are being terminated by the final parking.

General Meter Values Interval

Interval in seconds, by which the charger will send regular meter value reports to the central system during the charging session.

Refers to ClockAlignedDataInterval of OCPP 1.6 and AlignedDataInterval of OCPP 2.0.1.

General Meter Values Measurands

Measurands which the charger will send on ‘General meter values interval’. Suggested: power offered.

Refers to MeterValuesAlignedData of OCPP 1.6 and AlignedDataMeasurands of OCPP 2.0.1.

Energy Reading Type Detection

Absolute: Energy meter reading which is accumulating consumption of all sessions on one connector.

Relative: Energy meter reading starting from 0 for each session.

The central system of Tridens EV Charge is utilizing the following energy consumption detection for a session, as there are different varieties of reporting types by chargers:

Chargers reporting an absolute energy meter values at session start, intermediate, stop. Energy of all the sessions on the charger so far.
Chargers reporting the session relative energy meter values at session start, intermediate, stop. Energy of the specific session.
Chargers reporting an absolute energy meter value at the start and stop of session, but in the intermediate time, they are sending relative session energy reports (zero based).

Energy Report Validation

The central system of Tridens EV Charge utilizes charging session’s energy consumption validation for the persisted charging session, when receiving the reports from the charger. Connector’s power capability is being verified along with the energy meter reading time. This mechanism serves to overcome an issue when the chargers report the deprecated or excessive energy meter consumption.

Validation is made in two steps, where both need to pass:

Timestamp of reported energy meter reading for the persisted session is verified against the persisted session’s latest valid meter reading. It is considered as valid if the energy meter reading’s timestamp is not older than the previous meter reading’s timestamp.
Reported energy (Wh/kWh) is verified against the capability of the connector. It is considered as valid if the energy consumed over time is possible for the connector’s power capacity in the time difference from the previous valid energy meter report timestamp of the persisted session.

Note:

Make sure to properly set the wattage limit on the connector configuration on Stations - Connectors.

If the connector has lower power capability configured, the energy difference reported will be too large for the configured capability and thus energy meter reports are going to be discarded and energy consumption will not be persisted on the Tridens EV Charge’s sessions.

The scenarios below are based on the charging connector which is capable of 30kW energy flow.

Screnario 1

Meter reading scope	Meter reading value	Meter reading time	Notes
Session start	2000 Wh	08:00:00	Absolute meter reading.
Session intermediate	2025 Wh	08:00:30	Absolute meter reading.
Session stop	2050 Wh	08:01:00	Absolute meter reading.

Scenario 2

Meter reading scope	Meter reading value	Meter reading time	Notes
Session start	0 Wh	08:00:00	Session relative meter reading.
Session intermediate	25 Wh	08:00:30	Session relative meter reading.
Session stop	50 Wh	08:01:00	Session relative meter reading.

Scenario 3

Meter reading scope	Meter reading value	Meter reading time	Notes
Session start	2000 Wh	08:00:00	Absolute meter reading.
Session intermediate 1	25 Wh	08:00:30	Session relative meter reading.
Session intermediate 2	50 Wh	08:01:00	Session relative meter reading.
Session stop	2075 Wh	08:01:30	Absolute meter reading.

Scenario 4

Meter reading scope	Meter reading value	Meter reading time	Notes
Session start	2000 Wh	08:00:00	Absolute meter reading.
Session intermediate 1	2025 Wh	08:00:30	Absolute meter reading.
Session intermediate 2	2020 Wh	08:01:00	Absolute meter reading. Valid time, invalid deprecated energy report. Invalid and not impacting the session.
Session stop	2075 Wh	08:01:30	Absolute meter reading.

Scenario 5

Meter reading scope	Meter reading value	Meter reading time	Notes
Session start	2000 Wh	08:00:00	Absolute meter reading.
Session intermediate	2025 Wh	08:00:30	Absolute meter reading.
Session stop	2020 Wh	08:01:00	Absolute meter reading. Valid time, invalid deprecated energy report. Invalid and not impacting the session.

Scenario 6

Meter reading scope	Meter reading value	Meter reading time	Notes
Session start	2000 Wh	08:00:00	Absolute meter reading.
Session intermediate 1	2025 Wh	07:59:59	Absolute meter reading. Invalid deprecated time. Invalid and not impacting the session.
Session intermediate 2	2050 Wh	08:01:00	Absolute meter reading.
Session stop	2075 Wh	08:01:30	Absolute meter reading.

Scenario 7

Meter reading scope	Meter reading value	Meter reading time	Notes
Session start	2000 Wh	08:00:00	Absolute meter reading.
Session intermediate	2025 Wh	08:00:30	Absolute meter reading.
Session stop	2050 Wh	08:00:29	Absolute meter reading. Invalid deprecated time. Invalid and not impacting the session.

Scenario 8

Meter reading scope	Meter reading value	Meter reading time	Notes
Session start	2000 Wh	08:00:00	Absolute meter reading.
Session intermediate	2500 Wh	08:00:30	Absolute meter reading. Valid time. Invalid excessive energy report over connector’s power capacity. Invalid and not impacting the session.
Session stop	2050 Wh	08:01:00	Absolute meter reading.

Scenario 9

Meter reading scope	Meter reading value	Meter reading time	Notes
Session start	2000 Wh	08:00:00	Absolute meter reading.
Session intermediate	2025 Wh	08:00:30	Absolute meter reading.
Session stop	2500 Wh	08:01:00	Absolute meter reading. Valid time. Invalid excessive energy report over connector’s power capacity. Invalid and not impacting the session.

Session Event Retry

Retry to send the event in case of failure. Suggested value is 3.

Refers to TransactionMessageRetryInterval of OCPP 1.6.

Docs: Consumption

Mon, 01 Jan 0001 00:00:00 +0000

To access this section in EV Charge, from the Menu, select Analytics, and click Consumption.

This section is divided into two parts:

The first part shows the total kilowatt-hours (kWh)/total energy consumed by end users for all chargers. The information (total energy consumed for all chargers) is based on the current month, a month ago, six months ago, and a year ago.

Information:
The red or green arrow shows the percentage decrease or increase respectively in total energy consumption at the moment against the same time a month ago, six months ago, and a year ago.
The second part shows a bar chart representing the total energy consumption obtained from all chargers based on an interval (day, week, month, and year) from a specific period. Additionally, the information can be filtered down to an individual charger or a group of chargers.

Information:
The visual representation in the form of a bar chart can be downloaded in various formats. To achieve this, click Chart context menu.

Docs: Consumption

Mon, 01 Jan 0001 00:00:00 +0000

To access this section in EV Charge, from the Menu, select Reports, and click Consumption. A paginated list of the total consumption obtained from each charger from a specific period is shown in a tabular format.

To generate the consumption list in a spreadsheet, click CSV. To print, click Print, and to copy, click Copy.

Note:

They are generated, printed, and copied per paginated page.

Information:

You can filter for the total consumption by date-time, charger/operator or/and a specific operator. Available consumption report types are energy, duration, charge time duration, park time duration and fault time duration.

Table 1: Available report types

Report Type	Description
Energy	Represents energy usage in kWh for the captured sessions, regarding the selected filters.
Duration	Represents the total time spent for the captured charging sessions, regarding the selected filters. Formatted in `HH:MM:SS`.
Charging Duration	Represents the total time spent for charging (energy flow) for the captured charging sessions, regarding the selected filters. Formatted in `HH:MM:SS`.
Parking Duration	Represents the total time spent for parking (energy not flowing) for the captured charging sessions, regarding the selected filters. Formatted in `HH:MM:SS`.
Fault Duration	Represents the total time spent while the charger/connector was faulted in scope of the captured charging sessions, regarding the selected filters. Formatted in `HH:MM:SS`.

In addition, the reporting section enables you to filter for the total consumption obtained from an operator’s charger. Therefore, this will allow you to quickly determine the total consumption obtained from the operator’s charger or group of chargers.

Tip:

In the case of a contract agreement with an operator, knowing the total consumption obtained from their charger or group of chargers can be very helpful.

Docs: Notifications

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

Notifications
Platforms
- Firebase configuration
  - Requirements and process outline
  - Firebase configuration for EV Charge

To access this section in EV Charge, from the Menu, select System configuration, and click Notifications.

Notifications

To access this section, click Notifications. A paginated list of all notifications is shown in a tabular format.

Four actions/subpages can be performed/viewed under this section, namely:

Create notification
Details notification page
Update notification
Delete notification

Create notification

Under notifications, to create a notification, click Create. Provide a name and code.

Note:

The code is a unique identifier of an object. It can be used during integration with the EV Charge API.

Publishers is used to configure what type of notification will be sent: SMS, push notification, URL, Email, and Log. It is also used to configure where the notification will be sent using Receivers.

List of applicable Receiver-value pairs for the publishing type:

Base: Notification targets plain destination contact data, depending on publisher type (email address, phone number or URL).
Customer: Notification targets to the destination of customer’s primary contact info, depending on publisher type (email address, phone number, URL, push notification), if action is related to the specific customer. Additionally, as a value, Customer Type group can be selected, meaning that notification will apply only if the customer belongs to the specific customer group.

To create a publisher, under Publishers, click Add publisher. The action and number of retries specify the type of notification that will be sent and how many times to resend in case of a failure—for instance, sending out an email that will resend three times, suppose it fails.

Information:

The template is configured in EV Charge, under Business configuration Templates. For more information, see Templates.

Note:

The URL action means the notification will be sent as an API request to the URL, while the Log action means the logging service will add a log entry whenever the notification is triggered.

Under each publisher are Receivers. The Receivers refers to where the notification will be sent. It can be a URL or a customer (if it is an email or SMS).

The Scope typifies what will trigger the notification, which can be a change in the charging infrastructure or a change in the charging session.

Once a specific action from the scope occurs, you can add filtering options. To add a filter, under Filters, click Add filter.

Example of a notification

Scope: Charging sessions
Action: Battery percentage
Filter: Battery percentage equals 80% (Reached 80%)

Information:

In this case, a notification will be sent out when the vehicle has reached 80% of charge.

Details notification page

Under notification, to see the full details of a notification, click Details. It contains the following information:

Name
Code
Action
Scope
Publishers
Filters (if any)

Update notification

Under notification, to update a notification, first, click Details; it shows the details of the notification. Then to update, click Update.

Information:

All information filled out under the create notification section can be updated except for the Code.

Delete notification

Under notification, to delete a notification, click Delete.

Notification scopes and actions

Notification scope defines the triggering event scope of EV charging related notifications.

There are currently two scopes of EV charging related notifications:

Charging infrastructure: Notification of charging infrastructure related operations. See Table 1 for applicable actions in the scope.
Charging sessions: Notification of charging session control related operations. See Table 2 for applicable actions in the scope.

Action name	Description
Station connected	Indicates that the charging station has successfully established the connection with the central system of Tridens EV Charge.
Station booted	Indicates that the charging station has reported the boot event. It usually means that the successful boot has happened after the restart, but the boot event can also be triggered on demand.
Station disconnected	Indicates that the charging station has disconnected from the central system of Tridens EV Charge.
Station reset	Indicates that the central system of Tridens EV Charge requested the charging station to reset.
Charger status changed	Indicates that the charger’s status has been modified and reported to the central system of Tridens EV Charge. E.g., status switched to available, unavailable, faulted, etc. Also contains additional reported status info, if provided by the charger manufacturer.
Connector status changed	Indicates that the connector’s status has been modified and reported to the central system of Tridens EV Charge. E.g., status switched to available, preparing, charging, suspended, unavailable, faulted, etc. Also contains additional reported status info, if provided by the charger manufacturer.
Connector unlocking requested	Indicates that the central system of Tridens EV Charge requested the connector to unlock from the mechanical electromagnetic lock.
Connector unlocking result	Indicates the result of connector unlocking (mechanical electromagnetic lock), reported by the charger to the central system of Tridens EV Charge.
Energy meter report	Represents the general energy meter report in kWh reported by the charger to the central system of Tridens EV Charge.
Firmware update requested	Indicates that the central system of Tridens EV Charge requested the firmware upgrade on the charger.
Firmware status	Indicates firmware update status on the charger, as reported by the charger to the central system of Tridens EV Charge. E.g., downloading, downloaded, installing, installed, failed, etc.
Diagnostics requested	Indicates that the central system of Tridens EV Charge requested the charger for diagnostics.
Diagnostic status	Indicates the status of diagnostics reporting by the charger. Reported by the charger to the central system of Tridens EV Charge. E.g., uploading, uploaded, failed, etc.
Display setup requested	Indicates that the Tridens EV Charge central system has requested the station to set up the display message.
Display setup result	Indicates the result to the station display setup request.
Display clear requested	Indicates that the Tridens EV Charge central system has requested the station to clear the display message.
Display clear result	Indicates the result to the station display clearance request.
Display settings reported	Indicates that charging station has reported the display message setup to the central system of Tridens EV Charge.

Table 1. Charging infrastructure actions/events.

Action name	Description
Authorization	Indicates that the EV driver has attempted the charging session authorization by identification device (e.g. swiping an RFID) at the charger side and the attempt was forwarded to the central system of Tridens EV Charge. Not to be confused with the rating authorizations.
Authorized	Indicates that the EV driver has successfully authorized for the charging session at the charger side with identification device (e.g. swiping an RFID), by authorization being accepted by the central system of Tridens EV Charge. Not to be confused with the rating authorizations.
Started	Indicates that the charging session has started on the charging infrastructure.
Ended	Indicates that the session has ended and finally terminated. Status goes into ‘closed’. Includes the ending in park-time session termination mode.
Reservation created	Indicates that an instant reservation of the charging infrastructure has been made for the charging session.
Reservation canceled	Indicates that the reservation of the charging infrastructure has been canceled.
Vehicle charged	Indicates that the vehicle has been fully charged. Threshold for the vehicle charged detection is 95%. Conditionally works when the charger reports EV battery’s percentage state-of-charge.
Charging end	Represents the end of the charging in the scope of the session, as the charger reported the charging end event to the central system of Tridens EV Charge. The session may keep going on in the final park time, until the final termination.
Charging end by monetary limit	Indicates that the charging of the session ended, as the central system of Tridens EV Charge detected breaching of the monetary limit, based on the Session Rating Settings.
Charging end by energy limit	Indicates that the charging of the session ended, as the central system of Tridens EV Charge detected breaching of the energy limit, based on the Session Rating Settings.
Charging end by charge time limit	Indicates that the charging of the session ended, as the central system of Tridens EV Charge detected breaching of the charge time limit, based on the Session Rating Settings.
Charging end by payment auth. failure	Indicates that the charging of the session ended, as additional payment authorization on the central system of Tridens EV Charge did not succeed, based on the Session Rating Settings.
Charging end by auth. failure	Indicates that the charging of the session ended, as additional customer resources authorization on the central system of Tridens EV Charge did not succeed, based on the Session Rating Settings.
Battery percentage limit	Indicates that the EV battery’s percentage has breached the defined limit. Can be triggered once per session. Mandatory to provide the ‘State of charge limit’ notification filter, e.g. 80%. Conditionally works when the charger reports EV battery’s percentage state-of-charge.
Energy limit	Indicates that the charging session’s notification energy limit in kWh has been breached. Mandatory to provide the ‘Energy limit’ notification filter, e.g. 60kWh.
Charge time limit	Indicates that the charging session’s notification charge time limit in seconds has been breached. Mandatory to provide the ‘Charge time limit’ notification filter, e.g. 3600 seconds (1 hour).
Park time limit	Indicates that the charging session’s notification park time limit in seconds has been breached. Useful to notify customers that their vehicle is not charging. Mandatory to provide the ‘Park time limit’ notification filter, e.g. 900 seconds (15 minutes).
Park time rating threshold breached	Indicates that the session’s park time duration rating threshold has been breached, based on the Session Rating Settings. Since this point, parking is charged to the driver.
Fault time limit	Indicates that the charging session’s notification fault time limit in seconds has been breached. Mandatory to provide the ‘Fault time limit’ notification filter, e.g. 300 seconds (5 minutes).
Monetary limit	Indicates that the monetary limit (in Site’s default currency) has been breached for the charging session. Can be triggered once per session. Mandatory to provide the ‘Monetary limit’ notification filter, e.g. 40€.
Monetary limit interval	Indicates that the monetary limit interval (in Site environment’s default currency) has been breached for the charging session. Can be triggered once per session. Mandatory to provide the ‘Monetary limit’ notification filter, e.g. 5€. Example for limit of 5 EUR: Notification is triggered when used amount of session breach is made first time over 5 EUR, then 10 EUR, then 15 EUR, …
Meter values reported	Indicates that the charger has reported meter values to the central system of Tridens EV Charge. Usually consists of energy (kWh), power (kW), amperage (A), voltage (V) reports.
Session refused	Indicates that the session has been refused. Customer is known to the central system of Tridens EV Charge, but initial resource authorization did not succeed.

Table 2. Charging session control events/actions.

Platforms

To access this section, click Platforms.

Platforms entail configuring third-party services to enable notifications. It includes Twilio for text messages and Firebase for push notifications.

Note:

You need to set up the services to use it in EV Charge.

To enable Firebase for push notifications in EV Charge, see Firebase Configuration.

Note:

To log and review the occurred events, log notifications feature can be configured by following the instructions of Log Notifications Setup.

Firebase configuration

Requirements and process outline

A Google account is required in order to set up Firebase.
You configure Firebase for EV Charge.
Tridens provides either:
- App - Apple ID
- App - Android Package Name
You configure iOS or Android apps on Firebase.
You provide either:
- GoogleService-Info.plist file (iOS platform)
- google-services.json file (Android platform)

Information:

The packages that Tridens provide (Apple ID & Android Package Name) are typically named based on your brand name.

Firebase configuration for EV Charge

Visit your Firebase portal at https://firebase.google.com/ and click Get started or Go to console.

Figure 1: Firebase portal

Create a new project on Firebase

Create a new project by clicking Create a project.

Figure 2: Create a project

Follow the steps to create a new project.

Figure 3: Create a project - step 1

Figure 4: Create a project - step 2

Figure 5: Create a project - step 3

Configure Firebase credentials in EV Charge

After returning to the Project Dashboard, click Project settings.

Figure 6: Project settings

Go to Service accounts and click Generate new private key.

Figure 7: Generate new private key

After confirming key generation, a JSON file will be downloaded to your computer.

Figure 8: Confirm key generation

The JSON file from the previous step contains your Firebase private key credentials—it can be opened in a text editor.

Figure 9: Private key JSON file contents

Next, visit EV Charge, navigate to System configuration Notifications Platforms. Click Firebase (FCM), then enter the credentials (which are: client ID, client email, project ID, private key ID, and private key) into the form. Finish by clicking Submit.

Note:

The credentials are obtained from the JSON file downloaded previously.

Figure 10: Firebase configuration on EV Charge

You have successfully configured Firebase for EV Charge.

Create a Firebase mobile app configuration - iOS

Go to the Project Dashboard on Firebase and enter the Project settings.

Figure 11: Project settings

Under the General tab, scroll to Your apps and select the iOS platform.

Figure 12: Add iOS app configuration

In the first step, enter the Apple ID (provided by Tridens) and click Register app.

Figure 13: iOS app configuration - Step 1

In the second step, download the GoogleService-Info.plist config file and provide it to Tridens to include it in your app build, then click Next.

Figure 14: iOS app configuration - Step 2

Click Next on steps 3 and 4, then Continue on step 5. This will return you to the Project Settings page, where your iOS app configuration will be visible. You can also re-download the GoogleServiceInfo.plist file here.

Figure 15: iOS app configuration - finished

Create a Firebase mobile app configuration - Android

Go to the Project Dashboard on Firebase and enter the Project settings.

Figure 16: Project settings

Under the General tab, scroll to Your apps and select the Android platform.

Figure 17: Add Android app configuration

In the first step, enter the Android package name (provided by Tridens) and click Register app.

Figure 18: Android app configuration - Step 1

In the second step, download the google-services.json config file and provide it to Tridens to include it in your app build, then click Next.

Figure 19: Android app configuration - Step 2

Click Next on step 3 and Continue on step 4. This will return you to the Project Settings page, where your Android app configuration will be visible. You can also re-download the googleservices.json file here.

Figure 20: Android app configuration - finished

Docs: Roaming Profile

Mon, 01 Jan 0001 00:00:00 +0000

To access this section in EV Charge, from the Menu, click Roaming.

Roaming Profile

Represents roaming node settings of CPO or eMSP, which is primarly using Tridens EV Charge as the central system. Settings are used to represent the CPO or eMSP entity in protocol specific roaming network communication with other third-party roaming platform nodes.
Entity can be related to Operator, otherwise it belongs to a general Site context.

General locational, monetary and informal settings are taken from the Site and Operator context.

Required to configure:

Protocol
Roaming identifier
Platform type

In the scope of Roaming Profile, Roaming Platforms can be configured for the communication and integration with third-party roaming service. See Roaming Platforms.

When desired to expose the charging infrastructure as a charge point operator (CPO) to the third-party providers/services, it is required to populate the charging infrastructure entries, as stated below.

Area: Set area’s roaming id to the unique identifier non-blank value and also populate the phone number of Area or related Operator. Roaming id attribute is required for roaming, but please note that this identifier may not be used in every roaming protocol, due to different protocol rules.

Charger: Set charger’s roaming id to the unique identifier non-blank value and also mark roaming attribute as enabled. Roaming id attribute is required for roaming, but please note that this identifier may not be used in every roaming protocol, due to different protocol rules.

Connector: Set connector’s roaming id to the unique identifier non-blank value. Roaming id attribute is required for roaming, but please note that this identifier may not be used in every roaming protocol, due to different protocol rules.

See Table 1 for the mapping of roaming identifiers in different roaming protocols.

Table 1: Roaming protocol’s attribute mapping from Tridens EV Charge.

Roaming Protocol	Roaming Protocol Attribute	Mapping from Tridens EV Charge	Example
OCPI 2.2.1	location id	Constructed based on Area’s roaming id.	010107
OCPI 2.2.1	evse uid	Constructed based on Connector’s roaming id.	010107
OCPI 2.2.1	evse id	Constructed based on Roaming Profile’s country code, roaming id and Connector’s roaming id.	SI TRI E010107
OCPI 2.2.1	connector id	Constructed based on Connector’s roaming id.	010107
OICP 2.3	evse id	Constructed based on Roaming Profile’s country code, roaming id and Connector’s roaming id.	SI TRI E010107

Docs: Stations

Mon, 01 Jan 0001 00:00:00 +0000

To access this section in EV Charge, from the Menu, select Operations, and click Stations. A paginated list of all charging stations is shown in a tabular format.

To generate the stations’ list in a spreadsheet, click CSV. To print, click Print, and to copy, click Copy.

Note:

They are generated, printed, and copied per paginated page.

Information:

You can filter for a charging station by name, serial number, model, vendor, or/and operational status.

OCPP-related operations on the charging station include the following:

Reboot
Firmware upgrade
Diagnostic logs
Trigger message

Reboot

The charging station in EV Charge is the network component. To send a reboot request to the charging station, click Reboot.

Firmware upgrade

To request a firmware upgrade on the charging station, click Firmware update. Provide a location (in URL form)—typically, this is an FTP location or an HTTP address from where the file can be downloaded.

Information:

The format of the FTP URL is: ftp://user:password@host:port/path where user:password@, :password, or :port can be omitted.

The format of the HTTP address is: http://hostname:port/path where :port can be omitted.

The Retrieve at indicates when the charging station will download the file, and the Install at means when the update (in the form of a file) will be installed on the charging station.

Retries and Retry interval represent how many times and at what interval, respectively, the charging station will re-download the file in case the download fails on the first attempt.

Clicking Request schedules the firmware upgrade on the charging station.

Diagnostic logs

To request diagnostic logs for the charging station, click Diagnostic request. Provide the periods from which to retrieve the diagnostic logs by configuring the start and stop times.

Additionally, provide a URL where the logs will be uploaded because OCPP does not work with direct file transfer. You will need an SFTP/FTP server where the file will be pushed or an HTTP address.

Tip:

Download and install an SFTP/FTP client/software, for example, FileZilla . Run it as a server on your computer, and provide the URL to EV Charge to download the file to the server.

Retries and Retry interval represent how many times and at what intervals the charging station retries to upload the diagnostic logs to the URL if it fails on the first attempt.

By clicking Request, the charging station will collect its internal logs and send them to the link configured in the URL.

Trigger message

Trigger message is used to trigger specific OCPP actions on the charger, mainly for the purpose of debugging or testing. To trigger a message, click Trigger message, and select the type of trigger message, which could be:

Boot notification
Diagnostics status notification
Firmware status notification
Heartbeat
Meter values
Status notification

Docs: Templates

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

Mail templates
SMS templates
Push notification templates

To access this section in EV Charge, from the Menu, select Business configuration, and click Templates.

Mail templates

To access this section, click Mail templates. A paginated list of all mail templates is shown in a tabular format.

A mail template is used to configure the layout and some basic information for an email sent to a receiver.

Information:

The template can include content like images or text.

Four actions/subpages can be performed/viewed under this section, namely:

Create a mail template
Details mail template page
Update mail template
Delete mail template

Create a mail template

Under mail templates, to create a mail template, click Create. Provide a name, code, and description.

Note:

The code is a unique identifier of an object. It can be used during integration with the EV Charge API.

Additional configurable parameters for the mail template include the following:

Subject
From address
To
Cc
Bcc
Reply to

Information:

The from address represents the sender’s address, while the to represents the receiver’s address.

In addition, configure the body for the template.

Note:

EV Charge provides a rich text editor to customize the template body, as shown below. You can also import your template.

Figure 1: Mail template body

Details mail template page

Under mail templates, to see the full details of a mail template, click Details. It contains the following information:

Name
Code
Description
Subject
From address
To
Cc
Bcc
Reply to
Content (if any)

Update mail template

Under mail templates, to update a mail template, first, click Details; it shows the details of the mail template. Then to update, click Update.

Information:

All information filled out under the create a mail template section can be updated except for the Code.

Delete mail template

Under mail templates, to delete a mail template, click Delete.

Note:

Deleting a mail template already used in other parts of EV Charge cannot be done. Every particular reference to the mail template first has to be deleted.

SMS templates

To access this section, click SMS templates. A paginated list of all SMS templates is shown in a tabular format.

An SMS template is used to configure how an SMS will be presented to the receiver.

Four actions/subpages can be performed/viewed under this section, namely:

Create an SMS template
Details SMS template page
Update SMS template
Delete SMS template

Create an SMS template

Under SMS templates, to create an SMS template, click Create. Provide a name, code, description, and content.

Note:

The code is a unique identifier of an object. It can be used during integration with the EV Charge API.

Details SMS template page

Under SMS templates, to see the full details of an SMS template, click Details. It contains the following information:

Name
Code
Description
Content

Update SMS template

Under SMS templates, to update an SMS template, first, click Details; it shows the details of the SMS template. Then to update, click Update.

Information:

All information filled out under the create an SMS template section can be updated except for the Code.

Delete SMS template

Under SMS templates, to delete an SMS template, click Delete.

Note:

Deleting an SMS template already used in other parts of EV Charge cannot be done. Every particular reference to the SMS template first has to be deleted.

Push notification templates

To access this section, click Push notification templates. A paginated list of all push notification templates is shown in a tabular format.

A push notification template is used to configure how a push notification will be presented to the receiver.

Four actions/subpages can be performed/viewed under this section, namely:

Create a push notification template
Details push notification template page
Update push notification template
Delete push notification template

Create a push notification template

Under push notification templates, to create a push notification template, click Create. Provide a name, code, description, and content.

Note:

The code is a unique identifier of an object. It can be used during integration with the EV Charge API.

Details push notification template page

Under push notification templates, to see the full details of a push notification template, click Details. It contains the following information:

Name
Code
Description
Content

Update push notification template

Under push notification templates, to update a push notification template, first, click Details; it shows the details of the push notification template. Then to update, click Update.

Information:

All information filled out under the create a push notification template section can be updated except for the Code.

Delete push notification template

Under push notification templates, to delete a push notification template, click Delete.

Note:

Deleting a push notification template already used in other parts of EV Charge cannot be done. Every particular reference to the push notification template first has to be deleted.

Docs: Users

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

Create a user
Details user page
Update user
Enable/Disable user

To access this section in EV Charge, from the Menu, select User management, and click Users. A paginated list of all users is shown in a tabular format.

Note:

A user with the status of Active means the user is activated. To learn how to enable/disable a user, see Enable/Disable user.

Information:

You can filter for a user by first name, last name, email address, role, or/and status.

To generate the users list in a spreadsheet, click CSV. To print, click Print, and to copy, click Copy.

Note:

They are generated, printed, or copied per paginated page.

Four actions/subpages can be performed/viewed under this section, namely:

Create a user
Details user page
Update user
Enable/Disable user

Create a user

Under Users, to create a user, click Create. Provide a first name, last name, email address, and password.

Under the roles, a user can be a power user or/and an operator. A power user (typically yourself) can access all functionalities on the user interface in EV Charge.

However, if the user role of an operator is selected; in that case, it should be linked to an operator. Consequently, the user will only have access to what is related to the operator’s charging area—for instance, the stations and assets linked to the operator’s charging area.

Information:

To select an operator, start typing the operator name to show the operator.

By default, the user will be activated. However, the Enabled toggle switch allows you to activate or deactivate the user. Once the new user is created, they can log in to EV Charge using their details.

Details user page

Under Users, to see the full details of a user, click Details. It contains the following information:

First name
Last name
Email
Roles (if any)
Sites: This represents the sites the user can access.
Operator (if any)
Status

Update user

Under Users, to update a user, first, click Details; it shows the details of the user. Then to update, click Update.

Note:

All information filled out under the create a user section can be updated except for the Email.

Enable/Disable user

To enable/disable a user, first, click Details; it shows the details of the user. Then, click Update.

Information:

Use the Enabled toggle switch to activate or deactivate the user.

Docs: App Builder

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

Library
Builder interface
Configuration
- Widgets
- Menu

To access this section in EV Charge, from the Menu, select System configuration, and click App builder.

Library

To access this section, click App builder. A list of all created application templates is displayed in a table, showing their Name, Status (e.g., Published or Draft), and creation date.

Figure 1: App Builder template library

You can use the search bar at the top to filter the templates by name. For each template, you can view or modify its specific configuration by clicking the View/Edit icon.

To create a new app template, click + Template. This will open a modal where you must enter the template name. After creating it, you can begin configuring its layout.

Figure 2: Add template modal

Dashboard

After selecting a template via the View/Edit icon, you will enter the builder interface.

The center of the screen features a visual Phone Emulator. This area dynamically represents the application’s user interface, displaying an approximation of how the configured widgets and footers will appear on a mobile device.

The emulator screen is divided into three areas where widgets can be placed:

Top – A supplementary area displayed above the main content, typically used for search bars, filters, or custom HTML banners.
Center – The primary content area. This is the main view users see when they open a screen in the live app (e.g., the station list, map, or account overview). Widgets placed here form the core of the screen’s functionality.
Bottom – A supplementary area below the main content, used for additional controls or custom elements.

Figure 3: Phone emulator interface

Builder interface

The right sidebar contains the primary configuration tools organized into two tabs: Widgets and Menu settings.

Widgets

The Widgets tab allows you to customize the content of individual screens in the app.

Figure 4: Widgets tab configuration

Select screen to build: Use the dropdown menu to choose which specific app screen to configure (e.g., Stations > Map, Stations > List, Account, Sessions).
Drag and drop widgets: Below the screen selection is a library of available widgets for the selected screen. Drag and drop them into the corresponding areas (Top, Center, Bottom) on the Phone Emulator.
- Examples for Stations List include: Search and filter, Station list, Camera button, Custom HTML.
- Examples for Account include: Car list, Card list, Settings, Delete account.

Once a widget is added to the phone emulator, you can configure its placement and behavior by clicking the Settings icon directly on the widget.

Figure 5: Widget settings configuration

The right sidebar will display specific configuration fields for that widget type:

Position: Set relative horizontal and vertical positioning (left, right, top, bottom as percentages).
Padding and Margin: Adjust the inner and outer spacing of the widget in pixels.
Label: For certain widgets, you may adjust the displayed label text.

To delete a widget, click the Delete icon on the widget in the emulator.

The Menu tab is used to configure the app’s bottom navigation footer.

Figure 6: Menu settings tab configuration

Active Menu Tabs: You can reorder and manage the tabs that are currently visible to users in the app’s footer (limited to a maximum of 5 active tabs).
Unused Menu Tabs: Shows available features and screens that are not currently included in the bottom navigation. Drag items here to hide them from the footer.

You can also configure the settings for the structural areas in the emulator. In the emulator, click the Settings icon near the “Top area” or “Bottom area” labels to adjust properties such as making the area “Always visible”.

Figure 7: Menu settings configuration

After making all necessary changes, click the Save button to apply the modifications to the app template.

Figure 8: App builder save configuration

Docs: Authorization

Mon, 01 Jan 0001 00:00:00 +0000

Name	Description
Local offline authorization	Controls whether the charger will authorize the user when they are offline by using the authorization cache and/or local authorization list.
Local pre-authorize	Controls whether the charger will use authorization cache and/or local authorization list to start a session without waiting for an authorization response from the central system. The central system can later deauthorize the user at session event exchange.
Local auth list enabled	Indicates whether the local authorization list is enabled on the charging station.
Set local list max. length	Charging station’s maximum number of identifiers that can be sent in a single request to update the authorization list.
Local auth list	Maximum number of identifiers that can be stored in the local authorization list of the charging station.
Allow offline session of unknown id	Indicates whether the station supports the unknown-offline-authorization feature.
Authorization cache enabled	Indicates whether the authorization cache is enabled on the charging station.
Authorize remote start	Indicates whether additional authorization at remote session start request is enabled on the charger. If enabled, the charger issues authorization when it receives the remote start request from mobile/web.

Docs: Charging Session Malfunctions

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

Introduction
1. Session charging, but energy not progressing on Tridens
2. Session charging, but session shows 0 kW or 0 A on Tridens
3. No customer assigned on session
4. False time tracking
5. Faulted connector
6. Suspended EV/EVSE
7. Rating failed
8. Billing failed
9. Session did not start
10. Obsolete session, charger stops responding
11. Inadequate session

Introduction

This document describes scenarios of frequent EV charging session malfunctions with solution instructions and preventive measures.

1. Session charging, but energy not progressing on Tridens

Session charging at physical charger. Actual energy transferred >0 kWh, but on Tridens EV Charge web/mobile it shows 0 kWh or is stuck at some point above 0 kWh. This is usually the consequence of connector’s power limit being set too low on Tridens EV Charge dashboard, which causes the session energy validation rejections, as described in Energy Report Validation. Alternative issue might be that charging station is not reporting any energy consumption.

Figure 1: Session’s energy consumption not progressing on Tridens dashboard web/mobile.

Table 1: Solution & preventive measures of scenario 1.

Topic	Description
Connector’s power capacity configuration on Tridens	Adjust the connector’s power (W) capacity on Tridens EV Charge dashboard to reflect an actual power capacity of the connector. Provide the power value in unit of watts (W). This shall adjust the active session’s energy, once the next session meter values are reported. Future sessions shall contain the proper energy consumption. Session Integrations - Energy Report Validation
Enable reporting of energy consumption on station	Enable the reporting of energy (energy active import) on the physical station’s configuration. Adjust physical station’s configuration by using Tridens EV Charge dashboard Station - Actions - Configuration - Meterings. Enable Energy.Active.Import.Register in Measurands. Future sessions shall then contain energy consumption reports.
Enable meter values reporting interval on station	Enable the reporting interval for session-related meter values on the physical charging station. Adjust physical station’s configuration by using Tridens EV Charge dashboard Station - Actions - Configuration - Meterings and adjusting Meter Value Sample Interval. Interval is expected to be between 10-60 seconds. Session Integrations - Meter Values Reporting

2. Session charging, but session shows 0 kW or 0 A on Tridens

EV session charging at physical charger and actual energy is being transferred. Energy is >0 kWh, but power shows 0 kW or current 0 A on Tridens EV Charge web/mobile. This is usually the consequence of insufficient charger configuration in the scope of meter values reporting.

Figure 2: Session’s latest power and amperage missing on Tridens dashboard web/mobile.

Table 2: Solution & preventive measures of scenario 2.

Topic	Description
Enable reporting of energy consumption on station	Enable the reporting of power and current on the physical charging station’s configuration. Adjust physical station’s configuration by using Tridens EV Charge dashboard Station - Actions - Configuration - Meterings. Enable Power.Active.Import and Current.Import in Measurands. Future sessions shall then contain power and current reports, as long as the charger supports reporting these. Session Integrations - Meter Values Reporting
Enable meter values reporting interval on station	Enable the reporting interval for session-related meter values on the physical charging station. Adjust physical station’s configuration by using Tridens EV Charge dashboard Station - Actions - Configuration - Meterings and adjusting Meter Value Sample Interval. Interval is expected to be between 10-60 seconds. Session Integrations - Meter Values Reporting

Topic

Description

Enable reporting of energy consumption on station

Enable the reporting of power and current on the physical charging station’s configuration. Adjust physical station’s configuration by using Tridens EV Charge dashboard Station - Actions - Configuration - Meterings. Enable Power.Active.Import and Current.Import in Measurands. Future sessions shall then contain power and current reports, as long as the charger supports reporting these.

Session Integrations - Meter Values Reporting

Enable meter values reporting interval on station

Enable the reporting interval for session-related meter values on the physical charging station. Adjust physical station’s configuration by using Tridens EV Charge dashboard Station - Actions - Configuration - Meterings and adjusting Meter Value Sample Interval. Interval is expected to be between 10-60 seconds.

Session Integrations - Meter Values Reporting

3. No customer assigned on session

Session has no customer assigned, but charger is not publicly open.

Figure 3: No customer assigned on Tridens session.

Table 3: Solution & preventive measures of scenario 3.

Topic	Description
Session timeout	Such session state can be a consequence of non-proper configuration of connection timeout & session expiration settings. Adjust based on Session Start Timeout and Idle Session Settings. To avoid fraudulent usage, we suggest using preventive measures by configuring the charger’s timeout period in which the session is expected to start. It covers the time available to start the session, since the acceptance of remote start request or driver authorization at the spot. Remote session start and authorization timeout on charger side represents the pending period to start the session upon the acceptance, after which session start confirmation is expected from the charger. If this time is breached, the charger should prevent any session from starting without the next session authorization acceptance, whether by mobile remote request or authorization at the charger. Example: The EV driver plugs the charger’s connector to the vehicle. Then the driver presses the session start request button on the mobile application, and at this point, session is ready. Ready session expiration time of 30 seconds starts ticking. If it reaches 30 seconds and the session has not started yet, then the session gets closed on the central system side and is not being tracked anymore. Charger needs to discard this session as well by using the compatible timeout period, which is advised to be shorter than the one of the central systems due to the time elapsed for the commands exchange. Session timeout section is related to ready-session-expiration settings of the central system, as it closes inactive sessions based on the expiration settings and idle job configuration. Make sure to use the consistent ready-session-expiration time on the central system, so it works aligned with the charger.
Authorization caches	Disable charging station’s local authorization caches. Adjust physical station’s configuration in Stations - Actions - Configuration - Authorization and invalidate/disable authorization caches. Session Integrations - Driver Authorization
Authorization lists	Disable charging station’s local authorization lists. Adjust physical station’s configuration in Stations - Actions - Configuration - Authorization and disable, erase or update authorization lists. Session Integrations - Driver Authorization

4. False time tracking

Session charging most of the time (has high energy consumption), but parking/fault time is tracked instead. This indicates false connector status reporting.

Figure 4: Tridens session has inconsistent times.

Figure 5: Connector has non-proper status on Tridens web dashboard.

Table 4: Solution & preventive measures of scenario 4.

Topic	Description
Investigate OCPP logs	Investigate OCPP communication of the charging station in Tridens EV Charge dashboard under Stations - View Logs - OCPP. Focus on latest reported connector statuses from the charger in StatusNotification. The condition may be a result of false connector status reporting or invalid timestamp included in the report. OCPP communication view: Stations - Logs - Logged OCPP Communication Session duration scopes (reservation, charging, parking, fault): Sessions - Duration Scopes
Use charging station’s latest firmware	Ensure using the charging station manufacturer’s latest stable firmware, which may already provide a correction. Otherwise, please contact the manufacturer about the connector status reporting issue and provide them the OCPP logs excerpt. Tridens EV Charge Operations - Stations - Firmware

Topic

Description

Investigate OCPP logs

Investigate OCPP communication of the charging station in Tridens EV Charge dashboard under Stations - View Logs - OCPP. Focus on latest reported connector statuses from the charger in StatusNotification. The condition may be a result of false connector status reporting or invalid timestamp included in the report.

OCPP communication view:
Stations - Logs - Logged OCPP Communication

Session duration scopes (reservation, charging, parking, fault):
Sessions - Duration Scopes

Use charging station’s latest firmware

Ensure using the charging station manufacturer’s latest stable firmware, which may already provide a correction. Otherwise, please contact the manufacturer about the connector status reporting issue and provide them the OCPP logs excerpt.

Tridens EV Charge Operations - Stations - Firmware

5. Faulted connector

Session starts charging & charges load, then connector switches to faulted (hardware malfunction) and shows OCPP logs for investigation.

Figure 6: Connector has faulted status on Tridens web dashboard.

Figure 7: Tridens session contains fault time.

Table 5: Solution & preventive measures of scenario 5.

Topic	Description
Investigate OCPP logs	Investigate OCPP communication of the charging station in Tridens EV Charge dashboard under Stations - View Logs - OCPP. Focus on the latest StatusNotification reports from the charger and find error logs. Vendor error codes may indicate a specific error that requires a technician’s action. OCPP communication view: Stations - Logs - Logged OCPP Communication Session duration scopes (reservation, charging, parking, fault): Sessions - Duration Scopes
Use charging station’s latest firmware	Ensure using the charging station manufacturer’s latest stable firmware, which may already provide a correction. Otherwise, please contact the manufacturer about the connector status reporting issue and provide them the OCPP logs excerpt. Tridens EV Charge Operations - Stations - Firmware
Notification on faulted connector	Use notifications to notify the charging infrastructure operator about the malfunction. Notification actions of interest: • Faulted connectors • Session with faulted time To configure notifications of different publishing types, follow instructions: System Configuration - Notifications More notification guidelines for operators are defined in: Integrations - Notifications Guidelines

6. Suspended EV/EVSE

Session started charging & charged some load, then connector was switched to suspended EV (charger offering energy, but EV not taking it) or suspended EVSE (charger not offering energy to EV). Please note that suspension may happen temporarily due to energy network load balancing or vehicle’s battery management system, to prevent failures.

Figure 8: Connector has suspended status on Tridens web dashboard.

Figure 9: Tridens session contains parking time, due to suspension.

Table 6: Solution & preventive measures of scenario 6.

Topic	Description
Investigate OCPP logs	Investigate OCPP communication of the charging station in Tridens EV Charge dashboard under Stations - View Logs - OCPP. Focus on the latest StatusNotification reports from the charger. Exact status reason can be found in additional info attributes. Suspended EV means that charger is offering energy, but vehicle is not taking it. Suspended EVSE means that charger is not offering energy. OCPP communication view: Stations - Logs - Logged OCPP Communication Session duration scopes (parking, charging, …): Sessions - Duration Scopes

Topic

Description

Investigate OCPP logs

Investigate OCPP communication of the charging station in Tridens EV Charge dashboard under Stations - View Logs - OCPP. Focus on the latest StatusNotification reports from the charger. Exact status reason can be found in additional info attributes.

Suspended EV means that charger is offering energy, but vehicle is not taking it.

Suspended EVSE means that charger is not offering energy.

OCPP communication view:
Stations - Logs - Logged OCPP Communication

Session duration scopes (parking, charging, …):
Sessions - Duration Scopes

7. Rating failed

Customer’s session was charging successfully, but it ended up in rating-failed status. Failed rating of session can be a consequence of false plan-product catalogue configuration in Tridens Monetization, false customer’s subscription plan configuration in Tridens Monetization or internal error due to maintenance. Rating can be retried manually or by an automated job.

Figure 10: Tridens session with rating-failed status.

Table 7: Solution & preventive measures of scenario 7.

Topic	Description
Manual retry rating	Attempt manual retry rating operation on session by using Tridens EV Charge web dashboard in Sessions - Actions and hit Retry rating. Sessions - Retry Rating
Automated retry rating	Automated retry rating operation is done by automated retry session rating job. Sessions - Retry Rating
Monetization catalogue configuration	Verify whether rate plan configuration is proper in Tridens Monetization.
Customer subscription plan configuration	Verify whether customer’s subscription plan configuration is proper in Tridens Monetization.

8. Billing failed

Customer’s session was charging successfully, but it ended up in billing-failed status. Failed billing of session can be a consequence of false plan-product catalogue configuration in Tridens Monetization, false customer’s subscription plan configuration in Tridens Monetization or internal error due to maintenance. Rating can be retried manually or by an automated job.

Figure 11: Tridens session with billing-failed status.

Table 8: Solution & preventive measures of scenario 8.

Topic	Description
Manual retry billing	Attempt manual retry billing operation on session by using Tridens EV Charge web dashboard in Sessions - Actions and hit Retry billing. Sessions - Retry Billing
Automated retry billing	Automated retry billing operation is done by automated retry session billing job. Sessions - Retry Billing
Monetization catalogue configuration	Verify whether rate plan configuration is proper in Tridens Monetization.
Customer subscription plan configuration	Verify whether customer’s subscription plan configuration is proper in Tridens Monetization.

9. Session did not start

Charging session has been requested to start and was prepared with ready status. Session then never proceeded to start and did not obtain the in-progress status. Eventually, the session becomes closed.

Such session state can be a consequence of non-proper configuration of connection timeout & session expiration settings or missing session event from the charging station.

Figure 12: Prepared session in ready status.

Figure 13: Non-started session has been closed.

Table 9: Solution & preventive measures of scenario 9.

Topic	Description
Ready session expiration on Tridens	Session on the Tridens EV Charge server is considered as idle when not receiving event reports from the charging infrastructure after a certain configured time. Ready session expiration represents allowed inactivity period for a prepared ready charging session. When background job detects a ready session’s inactivity exceeding this time, it finalizes it (rating and closing). Adjust ready session expiration settings on Tridens by following instructions in Tridens EV Charge – Idle Session Settings. Align the expiration period with the Session connection timeout period.
Session connection timeout of station	Ensure to configure the session start connection timeout period on the charging station side. It covers the time available to start the session, since the acceptance of remote session start request or driver authorization. Adjust physical station’s configuration in Stations - Actions - Configuration - Core/General and adjust the Connection timeout, as instructed in Tridens EV Charge – Charging Session Integration – Session Start Timeout Align the timeout with Ready session expiration on Tridens web dashboard.
Station did not report session start event	Verify whether the charging station has reported start session event (OCPP’s StartTransaction or TransactionEventRequest). See OCPP communication logs: Stations - Logs - Logged OCPP Communication If event is missing, ensure using the latest firmware on the charging station, otherwise report an issue to the manufacturer.

10. Obsolete session, charger stops responding

Charging session was charging and progressing, but at some point, the progress was not visible anymore on Tridens web dashboard and mobile application. Eventually, such session was detected as idle and switched from in-progress status to closed. Persisted energy may not reflect the value on the physical charger/vehicle.

Figure 14: Session stopped being tracked and eventually closed.

Table 10: Solution & preventive measures of scenario 10.

Topic	Description
Meter values reporting	Ensure having session meter values reporting enabled. Enable session meter values reporting interval on Stations - Actions - Configuration - Meterings - Interval of 10-60 seconds. Enable session meter values measurands reporting in Stations - Actions - Configuration - Meterings - Measurands. Advised to use Energy.Active.Import.Register, Power.Active.Import and Current.Import. For more guidelines and instructions on configuring the meter values, refer to Tridens EV Charge – Charging Session Integration – Meter Values Reporting.
Ongoing session expiration on Tridens	Session on the Tridens EV Charge server is considered as idle when not receiving event reports from the charging infrastructure after a certain configured time. Ongoing session expiration represents allowed inactivity period for an ongoing in-progress charging session. When background job detects an in-progress session’s inactivity exceeding this time period, it finalizes the session (rating and closing). Adjust ongoing session expiration settings on Tridens by following instructions in Tridens EV Charge – Idle Session Settings.
Charging station’s network issues	Consider that charging station’s web network issues may impact this. In large network inactivity times, session may be detected as idle and closed by ongoing-session-expiration rules on Tridens.
Charging station’s firmware issue	Charging station may stopped operating properly due to firmware issue, full messaging queue, memory overflow or any similar issue. Ensure using the latest stable firmware on the charging station.
Charging station’s hardware issue	Charging station may stopped operating properly due to hardware issue: EV communication error, high temperature, over voltage, power meter failure, reader failure, ground failure or other. Check out OCPP communication logs to find any fault indicators (StatusNotification): Stations - Logs - Logged OCPP Communication

11. Inadequate session

Recognize one of the following:

Sessions shorter than 5 minutes.
Sessions consumed less than 5 kWh of energy.
Non-properly tracked session times: Charging times, parking times, fault times.
No customer assigned on session.
No monetary amount assigned on session.

Table 11: Solution & preventive measures of scenario 11.

Topic	Description
Short session	See Session did not start and Obsolete session, charger stops responding.
Low energy consumption	See Session charging, but energy not progressing on Tridens and Faulted connector.
Session has non-proper times	See False time tracking.
Session has no customer assigned	See No customer assigned on session.
Session has no monetary amount	Verify whether rate plan configuration is proper in Tridens Monetization & whether customer’s subscription plan configuration is proper in Tridens Monetization.

Docs: Revenue

Mon, 01 Jan 0001 00:00:00 +0000

To access this section in EV Charge, from the Menu, select Analytics, and click Revenue.

This section is divided into two parts:

The first part shows the total revenue generated from all chargers. The information is based on the current month, a month ago, six months ago, and a year ago.

Information:
The red or green arrow shows the percentage decrease or increase respectively in total revenue at the moment against the same time a month ago, six months ago, and a year ago.
The second part shows a bar chart representing the revenue generated from all chargers based on an interval (day, week, month, and year) from a specific period. Additionally, the information can be filtered down to an individual charger or a group of chargers.

Information:
The visual representation in the form of a bar chart can be downloaded in various formats. To achieve this, click Chart context menu.

Docs: Revenue

Mon, 01 Jan 0001 00:00:00 +0000

To access this section in EV Charge, from the Menu, select Reports, and click Revenue. A paginated list of the total revenue generated from each charger from a specific period is shown in a tabular format.

To generate the revenue list in a spreadsheet, click CSV. To print, click Print, and to copy, click Copy.

Note:

They are generated, printed, and copied per paginated page.

Information:

You can filter for the total revenue by date-time, charger/operator, or/and a specific operator.

In addition, the reporting section enables you to filter for the total revenue (money) generated from an operator’s charger. Therefore, this will allow you to quickly determine the total revenue generated from the operator’s charger or group of chargers.

Tip:

In the case of a contract agreement with an operator to share a percentage of revenue, knowing the total revenue generated from their charger or group of chargers can be very helpful.

Docs: Roaming Platform

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

Roaming Platform
OCPI Access Configuration
OICP Access Configuration

To access this section in EV Charge, from the Menu, click Roaming.

Roaming Platform

Represents a third-party roaming platform node which is configured to communicate with roaming node configured by roaming profile in Tridens EV Charge central system. Third-party platform node can be a Hub or specific CPO, eMSP, PTP, NAP, NSP or other. Roaming platform is configured in the scope of Roaming Profile, making platform dependent on the profile settings.

Definition of roles for the Platform:

CPO: Charge Point Operator
eMSP: eMobility Service Provider
PTP: Payment Terminals Provider
NAP: National Access Point
NSP: Navigation Service Provider
Hub: Hub connecting CPOs and eMSPs

Required to configure:

Roaming identifier
Platform type (hub, CPO, eMSP, PTP, NAP, NSP, …)
Base API URL of platform
Country

Roaming Access Configuration

In order to enable the communication between the roaming node of Tridens EV Charge and the third-party roaming node, the selected roaming protocol’s specific access configuration is required.

The configuration is separated on two parts, depending on which communication protocol is selected:

OCPI Access Configuration
OICP Access Configuration

OCPI Access Configuration

Applies for protocols: OCPI

Communication between the two OCPI nodes, whether CPO, eMSP, PTP, NAP, NSP, hub or other is initiated by registration and credentials exchange.

As OCPI protocol defines, one of the two integrating nodes provide a registration token to the second node. The second node uses the registration token to initiate the communication between the two nodes, by exchanging and deciding the common protocol version, available operational modules with addresses and to finalize the credentials exchange.

Credentials exchange is done when both nodes determine to each other a new access token and registration token is revoked.

Access Initiation Setup and Guidelines

Step-by-step registration example #1, when roaming node of Tridens EV Charge initiates the registration to the third-party roaming platform node.

Third-party roaming platform generates the registration token.
Registration token is forwarded in a safe way to the roaming client of Tridens EV Charge. How this step is done, depends on the onboarding communication channel between the roaming sides.
Roaming node of Tridens EV Charge uses registration token provided by the third-party roaming platform and assigns it on the roaming platform configuration by using the “Use Registration Token → Assign Registration Token” feature.
Trigger credentials registration by using “Register Credentials” feature.

Step-by-step registration example #2, when third-party roaming platform node initiates the registration to the roaming node of Tridens EV Charge.

Roaming client on Tridens EV Charge provides registration token to the third-party roaming platform by using the feature “Provide Registration Token → Generate and Assign Registration Token”.
Read the generated token for the roaming platform by using the feature “Read Credentials → Read Registration Token”.
Forward the token in a safe way to the third-party roaming platform. How this step is done, depends on the onboarding communication channel between the roaming sides.
Third-party roaming platform initiates the credentials registration.

Operations to manage OCPI credentials on Tridens EV Charge:

Assigning Registration Token
- Provide Registration Token
  - Generate and Assign Registration Token
  - Assign Registration Token
- Use Registration Token
  - Assign Registration Token
Register Credentials
Update Credentials
Invalidate Credentials
Read Credentials

Assigning the Registration Token

Serves for setup of credentials registration for later communication establishment between the Tridens EV Charge and the third-party roaming platform.

To initiate the credentials registration, one of the two integrating OCPI nodes need to provide the registration token to the other node. By the registration token, the other node will initiate the communication and complete the registration process.

There are exclusionary options on how to determine and use the registration token for OCPI nodes registration, as further described in this section. However, token can be provided or used.

Provide Registration Token

A registration token is provided by the Tridens EV Charge OCPI node, so the other OCPI node platform needs to use this registration token to initiate the OCPI credentials registration and connection establishment.

Generate and Assign Registration Token

By this operation, Tridens EV Charge auto-generates a new registration token for a third-party roaming platform. Platform uses the registration token in later steps, to initialize the OCPI credentials registration and connection establishment.

Assign Registration Token

By this operation, a custom registration token for a third-party roaming platform is assigned on the Tridens EV Charge. Platform uses the registration token in later steps, to initialize the OCPI credentials registration and connection establishment.

Use Registration Token

A registration token is provided by the third-party roaming platform node, so the Tridens EV Charge OCPI node platform needs to use this registration token to initiate the OCPI credentials registration and connection establishment.

Assign Registration Token

Assigns the registration token, which is provided by the third-party roaming platform, so it can be used by Tridens EV Charge to initialize the OCPI credentials registration and connection establishment in later steps.

Register Credentials

Serves to trigger credentials exchange based on registration settings and establishes communication between the Tridens EV Charge and the third-party roaming platform.

Executes the credentials registration process with the third-party roaming platform. Operation uses the assigned registration token and invalidates it after, which means that new assigned credentials need to be used in further communication, as of OCPI.

This is an operation which needs to be initiated by the side to whom the registration token is provided.

Update Credentials

Executes the credentials update for the third-party roaming platform. Operation invalidates an existing access token, which means that new assigned credentials need to be used in further communication to Tridens EV Charge, as of OCPI.

Operation notifies other roaming party with new credentials to access Tridens EV Charge.

Invalidate Credentials

Invalidates all roaming platform’s existing access credentials. Includes revocation of access token, remote access token and registration token.

Read Credentials

Serves to read an existing assigned access credentials used in communication between the roaming platforms.

OICP Access Configuration

Applies for protocols: OICP.

Communication between the two OICP nodes, usually CPO/eMSP with the hub requires mutual certificate authentication, also referred to as mTLS. Thus, each of the two roaming nodes must present itself to the other one with a signed certificate, which is trusted and acceptable by the other side. The signed certificate also serves for identification purposes.

Table 1: Terminology of access certificates configuration on Roaming Platform

Term	Description
Access Certificate	Access certificate for the third-party roaming platform, by which it gains access to Tridens EV Charge’s roaming protocol specific API. This is a client certificate, which the third-party roaming platform needs to present.
Remote Access Certificate	Access certificate which Tridens EV Charge’s roaming node needs to use when accessing the third-party roaming platform node’s protocol specific API. This is a client certificate, which Tridens EV Charge’s roaming node presents when calling the third-party roaming platform API.
Remote Root Certificate	Public authority certificate of the third-party roaming platform node, so Tridens EV Charge can trust the certificates signed by this authority.

Access Setup and Guidelines

Let’s say a CPO and roaming hub platform wants to integrate with each other by OICP.

To enable a CPO to communicate with the roaming hub in scope of mutual certificate authentication:

CPO manager on Tridens EV Charge generates a private/public key pair and certificate signing request (CSR).
CPO manager handles the public key and CSR to the roaming hub provider manager.
Roaming hub provider manager signs the CSR by roaming hub’s trusted certificate authority, resulting in a signed trusted certificate of CPO.
Roaming hub manager handles the signed trusted certificate to the CPO manager.
Roaming hub trusts and identifies the communication with such signed certificate, as it was signed by its trusted certificate authority.

To enable a roaming hub to communicate with a CPO in scope of mutual certificate authentication:

Roaming hub manager generates a private/public key pair and CSR.
Roaming hub manager handles the public key and CSR to the CPO manager on Tridens EV Charge.
CPO manager signs the CSR by the CPO’s trusted certificate authority, resulting in a signed trusted certificate of a hub.
CPO manager handles the signed trusted certificate to the roaming hub manager.
CPO trusts and identifies the communication with such signed certificate, as it was signed by its trusted certificate authority.

Access Setup Operations

Tridens EV Charge provides operations over the Roaming Platform, to provide management of mutual certificate verification access.

Access Certificate

Operations to manage access certificate for the third-party roaming platform, by which it gains access to Tridens EV Charge’s roaming protocol specific API.

Can be done by either by:

a) Directly assigning the access certificate and its private key to the roaming platform configuration.

b) By preparing and signing the certificate signing request (CSR), where resulting certificate is assigned to the roaming platform configuration.

Available Operations:

Assign Access Certificate
Generate Private Key and Certificate Signing Request (CSR)
Sign CSR and Assign Access Certificate

Assign Access Certificate

Accepts PEM or plain Base64 encoded binary data of certificate with its correlated private key and assigns it to the roaming platform.

Used to verify/identify an access certificate of the third-party roaming node.

Generate Keys and Certificate Signing Request (CSR)

Provides a form to issue a certificate. Form accepts required attributes for the certificate signing and generates a private/public key pair. As a result, Base64 encoded binary data of CSR is returned, along with the Base64 encoded representation of private and public key.

Used to generate a certificate signing request with private/public keys, so the Tridens EV Charge or trusted authority can be requested to sign an access certificate.

Sign CSR and Assign Access Certificate

Accepts PEM or plain Base64 encoded binary data of CSR and a reference to the existing system’s trust root certificate which signs this certificate. Certificate is assigned to the roaming platform. Base64 encoded certificate content is returned back. Used to sign certificate signing request and obtain an access certificate.

Remote Access Certificate

Operations to manage access certificate which Tridens EV Charge’s roaming node needs to use when accessing the third-party roaming platform node’s protocol specific API.

Available Operations:

Generate Keys and Certificate Signing Request (CSR)
Assign Remote Access Certificate
Assign Remote Trusted Root/Intermediate Certificate

Generate Keys and Certificate Signing Request (CSR)

Used to help you generate a certificate signing request with private/public keys, so the third-party roaming platform’s authority can be requested to sign an access certificate.

Assign Remote Access Certificate

Accepts PEM or plain Base64 encoded binary data of certificate with its correlated private key and assigns it to the roaming platform.

Required to use for access to the third-party roaming platform.

Assign Remote Trusted Root/Intermediate Certificate

Accepts PEM or plain Base64 encoded binary data of a trusted public root/intermediate authority certificate of the third-party roaming platform node and assigns it to the roaming platform in Tridens EV Charge, so it can trust the certificates signed by this authority.

Required to trust the communication with the third-party roaming platform.

Invalidate

Invalidates all roaming platform’s existing access credentials. Includes revocation of access certificate, remote access certificate and remote root certificate.

Docs: Web Charging Payment

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

Introduction
Configuring Ad Hoc Web Charging Payment Page

Introduction

The EV Charging Portal allows your users to charge their electric vehicles (EVs) quickly and easily without the need for registration. It provides a straightforward interface that requires minimal input from the users. Users can simply enter their credit card information and start charging immediately.

To access this section in EV Charge, from the Menu, select Business configuration, and click Ad hoc Charging.

Configuring Ad Hoc Web Charging Payment Page

The Web Charging Payment Page can be created via accessing the Ad hoc charging page URL where your users can initiate charging, enter payment information and start charging. A user can also monitor charging on the Charging Status page.

Configure Redirect URL

When using web charging pages, configure redirect URL where users will be redirected upon successful checkout.

Configure Legal Information

Legal Information specifies the Privacy Policy and Terms of Service for the subscription and checkout. Provide URL for this information.

Docs: Areas

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

Charging area explained
Charging area example
Dynamic load balancing
List view
Map view
Charging infrastructure

To access this section in EV Charge, from the Menu, click Areas.

Charging area explained

A charging area is where a charging infrastructure is located; the beginning of the charging infrastructure is the charging area.

A charging area or multiple charging areas can belong to an operator. Also, a charging area can have multiple charging stations.

The primary idea/usefulness of creating a charging area is to group chargers linked to the same power source into one charging area. This is because the charging area’s main functionality is the ability to do dynamic load balancing.

Charging area example

Suppose you have a building with limited power capability and a few charging stations in the basement.

You can create one charging area for those charging stations since they are from the same power source. Then, you provide the maximum capability for the power source, and EV Charge will be able to dynamically allocate the load on the currently active chargers based on the limit on the charging area. This is called dynamic load balancing with the static limit.

Now, suppose residents live in the building who consume out of the power supply.

You can have a smart meter that feeds live data into EV Charge on total building consumption at the moment, which means EV Charge knows how much power is being pulled by the residents and therefore knows how much power it can give to the active chargers. This is called dynamic load balancing with the dynamic limit.

Dynamic load balancing

Dynamic load balancing is about the distribution of energy flow between all the electric vehicles charging on the charging area’s connectors.

Dynamic load balancing is manageable on the area level. It means that we can set different load balancing settings for each area. Areas contain charging stations with chargers and connectors. Tridens EV Charge then dynamically allocates the available energy flow of an area to the active charging sessions on chargers of that area.

Energy supply is dynamically allocated among the active sessions. So if available power supply on that area is 100kW, this power can be distributed among currently active sessions. Redistributions among the sessions happen in time intervals or when new session becomes active, or when the session ends.

Static or dynamic limits can be applied for the area. Static limits are determined by area’s static limit on the Balancing Profile or by area’s Area Limit Period, meanwhile the dynamic limits are defined by the Asset measured reports or by updating Area Limit Periods by energy forecast or demand-supply systems.

Note:

Interoperability

Area’s dynamic load balancing feature utilizes standardized OCPP defined charging profiles, so as long as CPO’s charger supports the OCPP charging profile operations, then interoperability with this feature of Tridens EV Charge is available.

When Ara’s DLB is on, charger is initially instructed to start the session with 0W. This is usually the reason why connector goes to suspended status. Once the charger actually reports that the session is confirmed to start, Tridens EV Charge central system aligns the DLB limit for the session, for example to 22kW.

Load balancing example with the static limit

A charging area has five 50kW chargers and a dedicated power source capable of fully supporting three chargers at maximum power (150kW). Therefore, you set a static limit of 150kW on the charging area because the limit is always known.

Load balancing basic example with the dynamic limit

A charging area has five 50kW chargers and a power source capable of 150kW. Also, there are other consumers in the form of an asset consuming out of the power—for example, an apartment.

Therefore, you cannot set the maximum power limit for the chargers to 150kW because other consumers can pull from the power source. Instead, you install a smart meter that tells EV Charge how much power is drawn from other consumers in real-time—for example, 20kW. Then, EV Charge can dynamically calculate the maximum power threshold for the chargers, which will be 150kW - 20kW = 130kW.

Note:

With dynamic load balancing by the dynamic limit, the power limit for the charging area can be changed in real-time based on inputs from the smart meter.

Load balancing advanced example with the dynamic limit

Area of chargers has the static limit of 60kW total power available. As balancing by asset is enabled, the total power limit of 60kW is overridden by live reports of ‘meter’ type asset, if there is any configured. Let’s say that there are 4 sessions active on the chargers of an area. As meter asset is reporting 40kW available at the moment, 40kW is the total power available for all the charging chargers on area for the sessions. As distribution strategy is set to ‘equal’, 40kW will be distributed equally among the four active sessions, meaning that each session gets 10kW of power supply.

Once meter asset reports 44kW available, each sessions gets 11kW. Lets say that after an hour, there are 10 active sessions on the chargers of area and meter asset reports only 30kW available. If 30kW would be equally distributed, each session would receive 3kW of power supply, but that is below the minimum supply limit configuration, which is 5kW. At that moment, fallout strategy applies, which is set to ‘round allocation’ and it means that the central system of Tridens EV Charge will calculate and instruct the minimum power supply among as many sessions as possible.

For 30kW available, the earlier started six sessions will receive 5kW, meanwhile the latest four sessions will be halted temporarily. At each redistribution interval, the round allocation switches the sessions, so over time, the redistribution is fairly allocated among all the active sessions. If in the meantime one of the sessions is done, the next applicable session obtains the power supply and if new session starts, it is placed to the last position of the round allocation and will start getting power supply in the upcoming redistributions.

Figure 1: Load balancing advanced example with the dynamic limit

Under Areas, there are two sections, namely:

List view
Map view

List view

Under the list view, a paginated list of all charging areas is shown in a tabular format.

To generate the areas list in a spreadsheet, click CSV. To print, click Print, and to copy, click Copy.

Note:

They are generated, printed, and copied per paginated page.

Four actions/subpages can be performed/viewed under this section, namely:

Create area
Details area page
Update area
Delete area

Create area

Under areas, to create an area, click Create new. It has four sections, namely:

Info
Location
Dynamic load balancing
Summary

Info

Under the info section, provide a name and code.

Note:

The code is a unique identifier of an object. It can be used during integration with the EV Charge API.

Additionally, you can provide support contact information for the charging area. It includes a name, phone number, and email address. They are only used for information purposes.

Tip:

The support contact information is used to reach out in case something needs to be checked regarding the charging area. For example, if the charging area is a building, the support contact information can be the owner of the building or the janitor.

The charging area can be assigned to an operator. Then, if the operator logs in to their account, they can see the charging area and all the stations and chargers linked to that area.

Furthermore, any number of custom attributes can be added. They store information in key-value pairs and are intended to store additional information for the charging area.

Location

Under this section, provide a physical address for the charging area. The address is crucial; it is where the chargers linked to the charging area will show up on the map both for you in EV Charge and end users in the EV Charge - Mobile App. Hence, configuring this section matters in presenting the chargers to the end users.

Note:

Configuring the physical address links to Google Maps; therefore, it populates the longitude and latitude once the address is inputted. However, the populated longitude and latitude values can be updated individually.

Roaming

For the area to be applicable and exposed in roaming to the third party providers, populate roaming id attribute as an identifier with unique non-blank value. Please also populate the contact phone number on the Area or on the belonging Operator. Roaming id attribute is required for roaming, but please note that this identifier may not be used in every roaming protocol, due to different protocol rules.

Areas hierarchy

Hierarchy of areas can be used if there is one larger location, e.g., a shopping centre with further sub-locations. Each sub-location is thus more accurately located on the map and may also have a distinct power source, which can be important aspect in the scope of load balancing.

Example of area “Shopping Centre” which has 3 sub areas:

Area “Hall A”

Area “Lake Side”

Area “Amusement Park”

It is up to the operator to decide on how to represent their charging infrastructure location for the best experience and management.

Dynamic load balancing configuration

Under this section, dynamic load balancing can be enabled or disabled.

Note:

Once dynamic load balancing is enabled on the charging area, all the distinct static charging profile settings are unassigned on the charging infrastructure.

Although static charging profile configuration remains, it is not applied to the charging infrastructure. This means enabling dynamic load balancing and assigning charging profiles are mutually exclusive in EV Charge.

Information:

If you are doing dynamic load balancing, create one charging area for one power source.

The following input fields are shown once dynamic load balancing is enabled:

Electric output limit type
Electric output limit
Balancing by asset
Limit periods
Priority levels
Distribution strategy
Fallout strategy
Redistribution interval
Minimum supply
Maximum supply
Custom attributes

Electric output limit type

The electric output limit type can either be power or current. The difference is the unit in which the rate limit amounts are configured for every consumption of electric vehicles in a charging area.

The electric output limit type determines whether load balancing limits are specified for power (wattage) or current (amperage).

Note:

Power (base unit in Watts) represents the rate of energy transfer.

Current (base unit in Amperes) represents the rate of charged particles flow.

Electric output limit

The electric output limit represents the general electric consumption limit for the charging area. If configured, the chargers in the charging area will be limited and will not exceed the configured value for active sessions.

Note:

The electric output limit type determines whether the electric output limit is specified in wattage or amperage.

For example, suppose the electric output limit type is configured as Power, and the value for the electric output limit is 150000W. This means that the value (consumption) for all active charging sessions for that area will not exceed 150kW.

Information:

Since it is recommended that if you are doing dynamic load balancing to create one charging area for one power source, the electric output limit in watts can typify the power source output capability. For more information, see Dynamic load balancing example.

Balancing by asset

Balancing by asset indicates whether measured values of related asset are considered for load balancing on the charging area. Asset’s reported measured value determines the limit of the area for load balancing.

Limit periods

The limit periods represent energy flow rate consumption limits of charging electric vehicles in a one-time/scheduled range for that charging area. Limit periods override the energy flow rate output limit of the charging area’s balancing profile for the specific time range.

Area Limit Periods can be used by the energy forecast or demand-supply management systems, as they can control the measurements and power supply rules which can be then used by Tridens EV Charge to control the dynamic load management.

Priority levels

The priority levels option utilizes the level of the customer’s subscribed plans with the energy flow rate consumption limit in scope of dynamic load balancing.

Distribution strategy

The distribution strategy indicates how electricity consumption is distributed among the charging consumers (active charging sessions).

Configuring the Distribution strategy to Equal means that if load balancing is being done (has to reduce power output on one of the active chargers), it will divide between all active sessions equally.

Alternatively, suppose the Distribution strategy is configured to First in first charged; in that case, it will give maximum power to whoever started charging first and slowly redistribute it when the person finishes charging.

Fallout strategy

The fallout strategy only applies when an Equal distribution strategy is chosen. This is where you define the method when not all active charging sessions can be supplied with the minimum electric output. The rule determines which sessions continue to charge.

Configuring the Fallout strategy to First in means that the electric output is provided on the sessions which started earlier.

Alternatively, configuring the Fallout strategy to Round allocation means that the electric output is fairly allocated over time to all the active sessions (consumers)—using the round-robin algorithm.

Redistribution interval

The redistribution interval in seconds denotes the time range after which the Tridens EV Charge redistributes the charging limits among the active charging sessions of area. Redistribution is automatically handled when the asset limit is updated.

Note:

Minimum redistribution interval is 60 seconds.

Minimum supply

The minimum supply denotes the minimum power/current to provide for the consumer who is charging—it relates to the electric output limit type of the balancing profile.

Note:

The fallout strategy applies if the condition is not fulfilled.

Maximum supply

The maximum supply denotes the maximum power/current to provide for the consumer who is charging—it relates to the electric output limit type of the balancing profile.

For example, if you set the value to 10000 per charger, even if a particular charger has a 50kW capacity, the charging area limit will not let it go above 10kW.

Note:

The limit on the area is effective for ALL active sessions in that area simultaneously.

Custom attributes

Any number of custom attributes can be added. They store information in key-value pairs and are intended to store any additional information.

Summary

This section presents the information filled out in the previous three sections and can be reviewed before the charging area is created.

Information:

Once the charging area is created, it will initially be empty because no chargers or assets have been linked.

Details area page

Under areas, to see the full details of a charging area, click Details. It contains the following:

Name
Code
Location
Geographic coordinate system
Support contact name, phone, and email (if any)
Dynamic load balancing configurations (if enabled)
Any added custom attribute

Update area

Under areas, to update a charging area, first, click Details; it shows the details of the area. Then to update, click Update.

Note:

All information filled out under the create area section can be updated except for the Code.

Warning:

Want to switch Operator of Area? This change may impact the history of charging Sessions and may corrupt data about your charging infrastructure, if exposed in roaming. If you are exposing your charging infrastructure in roaming, we advise you to discard (close) an existing Area structure and open a new one.

Delete area

Under areas, to delete a charging area, click Delete.

Note:

Deleting a charging area already used in other parts of EV Charge cannot be done. Every particular reference to the charging area first has to be deleted.

Map view

Under the map view, all charging areas are shown on a map. By selecting a specific Area on the map, it shows the driving distance away from the charging area. In addition, it shows the name and location of the charging area, including the chargers and assets linked to the charging area.

Information:

If a charging session is in progress, the power the charger’s connector is putting out will be shown.

Charging infrastructure

The charging infrastructure (hierarchy) in EV Charge constitutes the following:

Operator* Area Charging station Charger Connector.

(*) means it is optional.

Docs: Local Authorization Management

Mon, 01 Jan 0001 00:00:00 +0000

Local authorization feature provides that the charger can authorize customers/drivers without using the central system, while being offline.

The central system of Tridens EV Charge instructs the charger about the list of authorization identifiers which can be used locally by the charger to authorize the drivers for charging. Each list has a version for the operational reference. Operation can be used as full override (overrides all identifiers) or differential (add/update the specific identifiers). The system can also request a charger for the version number of the local authorization list. This way an operator/provider can find out which authorization list is currently being set up on the charger.

To manage the charging station’s local authorization list, the following operations are available from the perspective of the central system of Tridens EV Charge:

Send local authorization list (full update).
Send local authorization list (differential - partial update).
Get local authorization list version.
Handling the charging station’s configuration settings for local authorization.

Local authorization and authorization cache are separate features and cache does not impact the local authorization list.

Docs: Payment Terminal Integrations

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

Introduction
Configuration
Charging Session Control

Introduction

This document describes the setup requirements for the payment terminal (POS) integration by OCPI or OICP communication protocols on Tridens EV Charge.

Integration involves Payment Terminal Providers (PTP) communicating with the charging infrastructure of charge point operators (CPO).
In this document, the term payment terminal provider is used as a technical term and is considered a synonym for the less technical term POS provider. The Payment Terminal Provider acts as a gateway to the charging infrastructure via OCPI or OICP protocols for charging session control and related data transfer. OCPI protocol offers official payment terminals support. For OICP, a hybrid concept can be utilized.

Notes:

Payment terminal providers can be added to Tridens EV Charge environment.
Payment terminal provider’s charging sessions are stored in Tridens EV Charge as part of an away charging infrastructure network, without a known customer/driver reference.
When the payment terminal provider charging session is utilized on a related CPO’s charging infrastructure that is part of Tridens EV Charge, such sessions appear as part of the home charging infrastructure network for that CPO.
Sessions are part of reporting in Tridens EV Charge for CPOs.

Figure 1: OCPI communication topology for payment terminal providers.

Configuration

Payment terminal providers can be configured in Tridens EV Charge tenant environments for CPOs. The following instructions focus on the OCPI protocol, as it officially defines payment terminal setup and communication (standardized since OCPI 2.2.1).

Configure Payment Terminal Provider

To configure the environment for a roaming Payment Terminal Provider (PTP):

Navigate to Roaming:
- Go to the Roaming section on the left-side menu of the Tridens EV Charge dashboard.
- Roaming Profile in this case represents environment as the operator of the charging infrastructure (chargers) in the roaming network.
- Roaming Platform here represents the third-party payment terminal provider.
- Submit configuration.
Create Roaming Profile (CPO):
- On the Roaming Profiles tab, create a new profile or use an existing one.
- Name & Code: Assign a name and code to identify the roaming profile.
- Type: Select CPO (charge point operator).
- Protocol: Select OCPI.
- Roaming ID: Three-uppercase-letter identifier that will represent CPO in roaming.
- Submit configuration.
Create Roaming Platform (PTP):
- Create a new Roaming Platform:
- Name & Code: Assign values to identify the platform.
- Type: Select Payment Terminal Provider (PTP).
- URL: Enter the payment terminal provider’s back-office server URL (e.g., https://your-pos-provider.com/api/ocpi).
- Country: Select the origin country of the payment terminal provider.
- Connection Initiation: Select which side will initiate the OCPI connection using the registration token.
- Credentials Exchange (Token):
  - If PTP provides the token: Select “I will use token provided by my roaming partner” and enter the token in the field.
  - If CPO provides the token: Select “I will provide token to my roaming partner” and click Generate. Share the generated token and your connection URL with the payment terminal provider.
Registration:
- Communication must be initiated via registration.
- Register credentials
  - If you used the partner’s token, click “Register credentials” on the selected Roaming Platform.
  - If you provided the token, the payment terminal provider must initiate the registration.
- Update Credentials: Use “Update credentials” to renegotiate credentials if needed.
- Invalidate Credentials: Use “Invalidate credentials” to stop communication/integration.

Figure 2: OCPI communication sequence.

Charging Infrastructure Setup

Once the CPO and PTP are communicating, the payment terminal provider can fetch the CPO’s charging infrastructure (Locations, EVSEs, Connectors). The CPO must populate specific roaming attributes to expose the infrastructure:

Area: Populate the roaming id with a unique identifier and the phone number.
Charger: Populate the roaming id with a unique identifier and mark the roaming attribute as enabled.
Connector: Populate the roaming id with a unique identifier.

Locations and charging infrastructure are reported to the payment terminal provider (push mode) and can also be fetched (pull mode).

Roaming Tariffs

As the charge point operator, you might want to assign roaming tariffs to represent prices for sessions initiated by payment terminal providers (PTP). Set up the Roaming Tariff for ad-hoc payments with the desired prices for energy and time, including taxes. Tariff also contains the max. amount for payment authorization of the charging session.

Important Notes:

Roaming tariffs calculate the expenses the payment terminal provider must pay to the charge point operator.
These prices are not necessarily what the end customer (EV driver) pays.

Configuration Guidelines:

Create Roaming Tariff:
- Navigate to Roaming -> Roaming Tariffs.
- Add a new tariff with a Name and Code.
- Set Status to Active and define the validity time range.
- Submit to create the tariff definition.
Add Tariff Details:
- Inside the tariff, add Tariff Details.
- Recurrency: Select One-time or Daily recurring.
- Priority: Higher priority details override lower ones if time frames overlap.
- Time Frame: Determine the inclusive start date-time and exclusive stop date-time. Select on which days the Tariff Detail applies.
- Pricing: Set the price and VAT percentage for rating metrics (energy, charge time, park time, flat, reservation time, etc.). Empty fields are treated as zero.
- Submit the configuration.
Assign Tariff to Roaming Platform (PTP):
- Navigate back to Roaming -> Roaming Platforms.
- Edit the specific Roaming Platform for the payment terminal provider configured earlier.
- In the setup wizard (usually Step 1), assign the Roaming Tariff.
- Submit the configuration.
Assign Tariff to Charging Infrastructure:
- Navigate to any charging infrastructure level having the Session Settings (also referred to as Session Rating Profile), which is assigned to the charging infrastructure on different levels.
- Assign the Roaming Tariff for the desired scope level:
  - Site
  - Operator
  - Charger
- Submit the configuration.

Once configured, new charging sessions related to this payment terminal provider will have costs calculated based on these settings. Tariffs are reported to the payment terminal provider (push mode) and can also be fetched (pull mode).

Charging Session Control

Operations by which the payment terminal provider can request the charge point operator of Tridens EV Charge to manage the charging session:

Remote session start
Remote session stop

Resulting and intermediate charging session actions are forwarded back to the payment terminal provider by API:

Session start
Session update
Session end
Charging infrastructure status changes
Final consumption report

Session progress is reported to the payment terminal provider (push mode) and can also be fetched (pull mode).

Docs: Roaming Tariffs

Mon, 01 Jan 0001 00:00:00 +0000

General information about tariffs in EV charging roaming:

Roaming tariffs are owned and defined by the charging infrastructure operators (CPO).
Roaming tariffs define charging expenses for the usage of the charging infrsatructure (energy, duration, parking, reservation, flat fee).
CPO in roaming does not know the end customer (EV driver), as the customer is the subject of mobility service provider (MSP). Thus, Monetization is not utilized to charge these kinds of end customers.
CPO side calculates the expenses for each session and provides charge detail record (CDR) to the mobility service provider (MSP).
Mobility service providers (MSP) who have the end customers/drivers base, cannot change the CPO’s roaming tariffs. CPO provides the tariffs as informative and as the base for the charge details record breakdown.
Tariffs are matched by validity (date and time). Recurrency modes are available in daily, weekly, one-time.
Roaming tariffs apply for a charging infrastructure where they are being used (referenced).
Roaming tariff applies for the third-party end customers for a roaming platform where the reference is assigned.
Third-party roaming providers can use push and pull models to obtain tariffs. When roaming tariff is being managed, integrated roaming third-party platforms are also being notified about the updates.
While home network roaming sessions are handled on Tridens EV Charge, expenses are calculated based on valid tariffs. Handling mid-session and at session completion.

Topics in this document:

Define Roaming Tariffs
Assign Roaming Tariffs to Charging Infrastructure
Assign Roaming Tariffs to Roaming Platform

To access this section in EV Charge, from the Menu, click Roaming and then Roaming Tariff.

Roaming Tariff

Roaming tariff defines the pricing that applies for charging infrastructure�s roaming usage and contains tariff details which define prices for metric types (energy, charge time, park time, reservation, flat), recurrency policy and constraints.

To add or manage Roaming Tariffs, navigate to EV Charge and while in the Menu, click Roaming and select the Roaming Tariffs tab. By using the button to add the tariff, wizard form shows up.

Assign name, alphanumeric code, status and validity restrictions for the whole Roaming Tariff structure.

Add roaming tariff details with the date-time recurrence policy and assign the desired monetary prices for metric types of energy, charging time, parking time, reservation time, reservation flat or just a flat fee. Monetary prices are determined without VAT, meanwhile VAT needs to be entered in a separate field. Unpopulated value means 0 (zero) expense for such metric type.

Roaming Tariff:

Defines validity restrictions for the whole tariff.
Validity frames should not overlap.
Provides transitions among the tariffs. E.g., one tariff stops on 2025-01-01 at 02:59:59 and the next one starts at 2025-01-01 03:00:00. Tariff element’s start/stop date and time attributes are optional. If no date-time restrictions are set, elements last indefinitely.
Accumulates the tariff details.

Roaming Tariff Detail:

Defines the schedules (recurring, one-time) and the cost at the moment when the schedule applies.
Defines prices and VAT for kWh energy, reservation time, charging time, parking time, flat fee and flat reservation fee.
Empty price means zero cost for the schedule.

Figure 1: Roaming Tariff Detail Configuration

Troubleshoot:

Tariffs not exposed in roaming integration or sessions have no monetary impact?

Please ensure the following is well set:

Roaming tariff is assigned on a proper context level: Charger/Operator/Site.
Roaming tariff is assigned on an integrated Roaming Platform.

Assign Roaming Tariff to Charging Infrastructure

Once Roaming Tariffs are configured, assign them on the charging infrastructure context, so the tariffs will apply in calculating the roaming expenses on the belonging chargers.

Tariffs can be set on Session settings of Site/Operator/Charger, where the lowest assigned level applies. The lowest level is Charger, so if Roaming Tariff is specified there, it overrides any tariff configurations on higher levels of Operator and Site.

To assign Roaming Tariff to the charging context, navigate to Site, Operator or Charger view and enter the wizard form. While managing the Session settings, there is a Roaming Tariffs selection where the desired tariffs can be picked to apply for the belonging charging sessions.

Assigning Roaming Tariffs to Roaming Platform

Once Roaming Tariffs are configured, assign them on the Roaming Platform context, so the tariffs will apply in calculating the roaming expenses for the events related to such roaming integration.

To assign Roaming Tariff to Roaming Platform, navigate to EV Charge and while in the Menu, click Roaming and select the Roaming Profiles tab. Select the desired Roaming Profile to see the Roaming Platforms. Select the platform and hit the Update button, so the wizard shows up. In the first step of wizard, find the Roaming Tariffs selection and pick the tariffs that are meant to apply for the sessions related to the specific roaming platform integration.

Docs: Assets

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

Assets overview
Assets explained
Assets example
List view
Map view

To access this section in EV Charge, from the Menu, click Assets.

Assets overview

Assets relate directly to dynamic load balancing. Each charging area, next to its chargers, can also have assets.

Note:

Charging areas would work even if no assets are linked to the area. However, assets are helpful when dealing with solar panels or smart meters.

An asset can be a consumer or producer of power. It can also be a smart meter delivering data into EV Charge for truly dynamic load balancing to be achieved instead of static dynamic load balancing.

Assets explained

Under assets, additional consumers or producers of energy can be added to a charging area—this is useful if you want to keep track of them.

For instance, a consumer of energy can be an apartment, while a producer of energy can be a solar panel.

Suppose you have a smart meter capable of sending data on the energy production from the solar panel; in that case, it can be added under assets as a smart meter and, therefore, can see how much power it produces.

Assets example

A producer can be a solar panel installed outside or on a hotel’s roof—here, the hotel represents a charging area. Then, if you tell EV Charge how much power that solar panel produces at a specific time, similar to a smart meter, EV Charge can consider that when it comes to dynamic load balancing.

Therefore, EV Charge knows how much power the solar panel produces. Suppose it also knows how much the hotel consumes through a smart meter. Then, EV Charge can perform dynamic load balancing in the charging area.

You can also have a battery; then, through the API, you can tell EV Charge when the battery is turned on. This battery will become an active producer, and EV Charge can pull out its power.

A consumer will be something else that you have plugged into the same network that is consuming power, and you can tell EV Charge precisely how much it consumes.

Under Assets, there are two sections, namely:

List view
Map view

List view

Under the list view, a paginated list of all assets is shown in a tabular format.

To generate the assets list in a spreadsheet, click CSV. To print, click Print, and to copy, click Copy.

Note:

They are generated, printed, and copied per paginated page.

Four actions/subpages can be performed/viewed under this section, namely:

Create asset
Details asset page
Update asset
Delete asset

Create asset

Under assets, to create an asset, click Create new. Provide a name, code, and description.

Note:

The code is a unique identifier of an object. It can be used during integration with the EV Charge API.

Choose the type of asset, whether a smart meter, a producer, a consumer, or any other kind.

Additionally, choose the type of supplied electric current of the asset, whether DC, AC single phase, or AC three phase. It represents the asset’s electricity flow setup.

Selecting a particular area denotes the charging area the asset belongs to. The list gets filtered as you type when searching for a charging area.

Note:

Once the charging area is selected, the asset becomes part of the area and can then be shown on the map based on the location of the charging area.

The power factor represents the relationship between current and voltage; the value has to be between 0 - 1, while 1 is the default.

The custom attribute is a key-value pair representing any additional information that can be stored for the asset.

Details asset page

Under assets, to see the full details of an asset, click Details. It contains the following:

Name
Code
Description
Type
Electric current type
Electric voltage type
Power factor
Any added custom attribute*

Update asset

Under assets, to update an asset, first, click Details; it shows the details of the asset. Then to update, click Update.

Note:

All information filled out under the create asset section can be updated except for the Code and Area.

Delete asset

Under assets, to delete an asset, click Delete.

Map view

Under the map view, all assets are shown on a map. The location of the asset is based on the charging area’s location. By selecting a specific Asset on the map, it shows the driving distance away from the asset. In addition, it shows the name, location, and type of the asset, including the power the asset is generating or consuming.

Docs: Authorization Cache

Mon, 01 Jan 0001 00:00:00 +0000

Operators/providers may utilize the charger’s ability for the authorization cache. Authorization cache autonomously maintains a record of previously presented identifiers (RFID, NFC, certificate, …) that have been successfully authorized by the central system of Tridens EV Charge. This charger’s feature is controllable from the Tridens central system side by using the configuration keys, as described in Stations - Live Configuration Parameters.

This feature needs to be used carefully and might only be proper in the following cases:

For the businesses, where the charging service is available only for post-paid customers, as sessions regulated by the local authorization cache are not authorizing any customer/driver resources, to verify whether customer has enough funds.
Charging station is located in area with non-stable network connection.

Authorization cache impacts:

Cache entries may contain expiry dates, which are considered at validation.
If authorization happens and an invalid identifier is present in the cache while the charger is online, the charger uses the central system to authorize.
Authorization cache has no impact on the local authorization list! These two features are separated and local authorization lists are fully controllable from the central system. Also, identifiers from local authorization list should not be added to the authorization cache. If both are used, the local authorization list has priority over the authorization cache for the same identifiers.

Local authorization and authorization cache are separate features and cache does not impact the local authorization list.

Docs: Charging Identification Device Setup

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

Device Type Setup
Device Setup
Assign Device to the Customer
Resign Customer’s Device

These are instructions to set up charging identification devices, e.g., RFID, NFC or certificate and assign them to the customers (drivers).

When the driver presents an identification device to the charger, for example by an RFID swipe, the charger requests the central system to identify and verify whether the driver is eligible to start the charging session.

Consists of multiple steps:

Device Type Setup
Device Setup
Assign Device to the Customer
Resign Customer’s Device

Device Type Setup

Set up the device types, which are intended to be supported. E.g., RFID, NFC, VIN, MAC.

Set up the device type first. To access this section in Monetization, from the Menu, click Devices. Open Device Type section tab on top. Use the green Create new button on the top right corner, so the creation form shows up.

Determine device type name as you desire and assign the code by one of the predefined code tags, which depend on the identification technology to be used, e.g., “RFID”. See the table of predefined device type code tags. You may also use the description box, to append additional helpful information and submit the creation form.

Code Tag	Description
RFID	Radio-frequency identification. Represents a badge or card of the driver.
NFC	Near field communication. Represents mobile or badge device of the driver.
VIN	Vehicle identification number. Represents a vehicle.
MAC	Media access control address, as unique device identifier in the network. May represents a vehicle or other device
ISO15118	Plug & charge of ISO 15118 for vehicle/driver identification. Represents a charging service contract of the vehicle and driver.
…	You can define your custom type as well.

Table 1: Device type’s predefined code tags, representing an identification technology.

Device Setup

Set up an instance of device. On the left side navigation, open the Devices section. Move the the Device section tab on top. Use the green Create new button on the top right corner, so the creation form shows up.

Assign name and code, as best suits you, select the belonging device type, for example an RFID.

Populate the Identifier field by the unique identification value, which is transferred from the charger to the central system, to be verified later when for example swiping an RFID. Submit the form.

Assign Device to the Customer

Once an identification device instance is set up, it is ready to be assigned to an existing customer (driver) with subscription plan.

To access this section in Monetization, from the Menu, click Customers and find the customer for which you would like to assign a device. Open up the customer details by Info button on the right side, under actions column. Then move to the Subscriptions section and expand the subscription which is desired to have an identification device assigned.

Move down to the Services section and find the one which is named CHARGING_SERVICE (also QUANTITY_CHARGING_SERVICE or similar - depends on the catalogue configuration) entry and hit Edit action. Edit the service’s Device column and search for the previously set up identification device, assign it and hit Submit action to update the service.

Figure 1: Find a customer

Figure 2: Expand customer’s subscription and find the suitable service

Figure 3: Assign device to service

Once identification device is assigned to the customer, swiping it (e.g., an RFID card) on the charger will result in charger requesting the central system to verify the device. This is called authorization, by which central system identifies the customer driver and verifies her/his monetary eligibility to start charging.

Once authorization is accepted, the charger is expected to allow the charging process to start.

Note:

Make sure that the customer to which an identification device is assigned has a valid subscription plan with a service, so the customer can be verified if eligible to charge.

If customer is pay-now, make sure credit card is assigned as well.

One device can be assigned to one customer at a time.

Resign Customer’s Device

When there is intention to remove an identification device from the customer, it can be done by navigating to the customer’s details view, as stated in section Assign Device to the Customer. Edit an existing service on hitting the cross button on the device, which is desired to be removed. Hit Submit action to update the service.

Figure 4: Resign customer’s service

Docs: Terminals

Mon, 01 Jan 0001 00:00:00 +0000

A Terminal represents a physical unit (for example, a payment terminal) that can be assigned to the charging infrastructure.

In the context of Tridens EV Charge, terminals enable seamless interaction between the charging environment and payment systems, ensuring secure transactions and operational efficiency.

Topics in this document:

Terminals
Payment Terminals Integration
View Terminals
Assign Terminal to Charging Infrastructure
Unassign Terminal from Charging Infrastructure

Terminals

A Terminal consists of the following attributes:

Identification (id, code): Unique identifiers used to distinguish the terminal.
Naming (name, description): Human-readable name and additional descriptive information.
Type (payment): Defines the terminal type, such as a payment terminal.
Address (address, city, zip, state, country): Specifies the official physical location of the terminal.
Geolocation (latitude, longitude): Indicates the terminal’s exact geographical coordinates.
Roaming (platform, roaming id, roaming reference): Indicates whether the terminal belongs to a third-party roaming platform (Payment Terminal Provider — PTP) and provides its roaming identification details.
Operator: Optional site operator associated with the terminal. When present, the terminal configuration applies to the operator context; otherwise, it applies to the general site environment.

Payment Terminals Integration

Terminals can be stored through roaming integrations with Payment Terminal Providers (PTPs), where the integrating party is the Charge Point Operator (CPO) managing the charging infrastructure in Tridens EV Charge.

To set up the roaming integration, see Roaming - Roaming Platforms.

Tridens EV Charge automatically persists payment terminals received from an integrated PTP roaming platform either:

on pull demand, or
through automatic push updates.

Once integrated, the charge point operator can assign payment terminals to Areas or Connectors, ensuring accurate terminal association within the charging network.

View Terminals

Operators can view all integrated terminals through a filterable table view, allowing quick access to terminal details and management actions.

Assign Terminal to Charging Infrastructure

A charging infrastructure operator can connect a terminal by assigning it to a specific Area or Connector.
When roaming integration with Payment Terminal Provider is active, the assigned terminal will reflect as assigned on the charging infrastructure in roaming to ensure data consistency across platforms.

Unassign Terminal from the Charging Infrastructure

A charging infrastructure operator can disconnect a terminal by unassigning it from an Area or Connector.
When roaming integration with Payment Terminal Provider is enabled, such Terminal will reflect as unassigned from the charging infrastructure in roaming to ensure data consistency across platforms.

Docs: FTP Server Setup

Mon, 01 Jan 0001 00:00:00 +0000

Download and install an SFTP/FTP software, for example, FileZilla . Run it as a server on your platform/computer, and provide the URL to EV Charge dialog to request the charger to use the FTP to upload/download files.

Here is the step-by-step tutorial for the FileZilla software.

1. Download the FileZilla

Download the FileZilla server installer uitable for your MacOS/Windows/Linux platform from FileZilla - The free FTP solution.

2. FileZilla Setup

a. Run the installer.

b. Check the licence agreement.

c. Among the components, select at least Server and Administration Interface.

Figure 1: Administration Interface

d. Choose the installation directory. Default value can be used.

e. Choose how FileZilla’s server is started. Manually (advised for usage on demand) or automatically at system start.

f. Assign adminstration interface’s listenting communication port. Default value can be used.

g. Protect your administration interface with the password and choose how administration interface is initiated (manually advised).

3. FTP setup

a. Once you open up the FileZilla Server, you can connect into it by using administration interface. Use host (localhost or 127.0.0.1), port (as configured in FileZilla setup step) and password (as configured in FileZilla setup step)

b. Assign a directory on your platform’s file system which will be shared. Use an existing directory or create a new directory on your desired path, e.g., C:\shared-directory.

c. FTP Users Setup

i. Open up the FileZilla configuration of user rights management (navigate by Server -> Configure -> Rights Management -> Users).

Figure 2: Users setup

ii. Hit Add User and perform the following:

Assign the user’s name (e.g., ‘mikejones’).

Figure 3: Assigning the user’s name

Determine the password if selecting Require the password to log in.

Figure 4: Password Login

Add a mount point. Assign the native path C:\shared-directory, meanwhile virtual path represents what FTP users can see.

Figure 5: Mount point settings

Assign access rights on the right side, whether users are allowed to read or read/write.

d. FTP Port Setup

To set up the FTP port, follow the steps below:

i. Open up the network configuration wizard (navigate by Server → Network Configuration Wizard).

Figure 6: Network Configuration Wizard

ii. Assign the port range, e.g. 30050-30055.

iii. Assign public IP address or hostname. This is the address by which your FTP will be accessed. Assing your device’s public IP by which your device will be accessible. Alternativelly you can use the domain, if available.

iv. Make sure your platform’s firewall has inbound/outbound TCP ports open for the communication on 30050-30055.

Figure 7: Ports and Protocols

The contents of configured directory C:\shared-directory are now accessble to the FTP user, which can connect to FTP server by using the platform/computer’s IP, for example ftp://miikejones:testpassword@192.168.5.1:30050.

Docs: Stations

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

Charging station overview
- Charging Infrastructure Status
List view
Map view
Connectivity Configuration
Charger’s session settings
Boot Configuration
Live Configuration Parameters
- Authorization
View Logs
- Logged Notifications
- Logged OCPP Communication
Local Authorization Management
Authorization Cache To access this section in EV Charge, from the Menu, click Stations.

Charging station overview

Under Stations, three major components can be created and managed:

Charging station
Charger
Connector

The charging station represents the networking component that can be connected to EV Charge, while the charger represents the hardware component of the charging infrastructure.

Charging Infrastructure Status

Charging station has a status that represents the operational availability of its charging components (chargers and connectors). This is displayed based on the reports from the charging infrastructure.

The broad operational statuses are as follows:

Operational Status	Description
Operative	Charging component is operating.
Inoperative	Charging component not operating.
Closed	Charging component has been discarded and is not in use anymore.

They can be further specified based on the individual state of each charging infrastructure component.

Here’s a detailed overview of each specific status:

Status	Description
Available	Indicates that the charging infrastructure is available to a new driver. Operative.
Preparing / Occupied	Indicates that charging infrastructure is no longer available for a new driver, but there is no ongoing session (yet). Occurs when user inserts the cable or vehicle occupies the parking spot. Operative.
Charging	Indicates that EV is being charged by the charging device. Operative.
Suspended EVSE	Indicates that EV is connected to the charger, but the charger is not offering energy to the EV. Reason could be load balancing restriction, local power supply constraints, or other limits. Operative.
Suspended EV	Indicates that EV is connected to the charger and the charger is offering energy, but EV is not taking any energy. Operative.
Finishing	Indicates that the charging session has stopped at the charging infrastructure, but infrastructure is not yet available for a new user. It can mean that cable has not yet been removed or the vehicle is still occupying the parking spot. Operative.
Reserved	Indicates that charging infrastructure is reserved. Operative.
Unavailable	Indicates that charging infrastructure is not available for use by drivers. Inoperative.
Faulted	Indicates that charging infrastructure is not working/set-up properly. Inoperative.
Closed	Indicates that charging infrastructure is not in use any more. Closed.

Figure 1: Charging infrastructure’s statuses

Under Stations, there are two sections, namely:

List view
Map view

List view

Under the list view, a paginated list of all charging stations is shown in a tabular format.

To generate the stations’ list in a spreadsheet, click CSV. To print, click Print, and to copy, click Copy.

Note:

They are generated, printed, and copied per paginated page.

Information:

You can filter for a charging station by name, model, vendor, area, operator, or/and operational status.

Six actions/subpages can be performed/viewed under this section, namely:

Create station
Details station page
- Websocket URL link example
- Connecting to EV Charge
Disconnecting from EV Charge
Configuration
Update station
Delete station

Note:

To create a charger for the charging infrastructure in EV Charge, you must create a new charging station or add it to an existing one.

Create station

Under stations, to create a station, click Create. Provide a name and code for the charging station.

You can choose whether the charging station should be visible/invisible in the EV Charge - Mobile App. To achieve this, use the Visible toggle switch to enable/disable. This is handy if there is a testing station you do not want end users to see in the EV Charge - Mobile App.

As stated, invisible stations are hidden from the map, but exceptions can be made for the drivers which are station area operator’s private group members. See more.

The Boot configuration indicates whether Tridens EV Charge central system needs to execute a basic configuration for the charging station when it boots and connects to Tridens EV Charge central system. It covers charger/connector status synchronization, time synchronization and resets the charging profiles for energy rate limits, if necessary. Use the Boot configuration’s toggle switches to enable/disable each available setting. See Station Boot Configuration.

The Physical address represents the MAC address of your charging station. In EV Charge, it is for information purposes; however, it can be helpful for inventory management.

The connectivity section specifies the protocol and the rules for the communication between the charging station and the central system. Communication protocol, Connection policy and Connection identifier are the rules which need to be set according to the connectivity configuration guidelines. See Connectivity Configuration.

In addition, assign the charging station to a charging area. This will determine the position of the charger(s) on the map both for you in EV Charge and end users in the EV Charge - Mobile App.

By clicking Save, EV Charge will create a template of the charging station (which represents your charging station).

Note:

The charging station will be inoperative because your station has not been connected to EV Charge. To learn how to connect your station to EV Charge and make it operative, see Details station page.

Details station page

Under stations, to see the full details of a charging station, click Details. It contains the following:

Area
Serial number
Model
Vendor
Firmware version
Modem iccid
Modem IMSI
WebSocket

Note:

Initially, once a charging station template is created in EV Charge, the information listed above will be empty except for the area and WebSocket. This is because the charging station is yet to be connected to EV Charge’s central system. Once connected, it reports the values.

The connection links are provided automatically by EV Charge. The WebSocket URL links connect your charging station to EV Charge. It contains a unique identifier assigned by EV Charge for your charging station.

Information:

There is a secure version of the WebSocket URL link and a less secure version. The less secure (regular) version can be used for testing purposes.

Note:

Using the WebSocket URL link is how your physical charger connects to EV Charge.

Connecting to EV Charge

To connect your charging station to the central system of Tridens EV Charge, see Connectivity Configuration.

After a successful connection, the information from the handshake request will be populated in EV Charge. It can include the following:

Serial number
Model
Vendor
Firmware version

The charging station then becomes connected/operative in EV Charge.

Disconnecting from EV Charge

Under details station page, to disconnect the charging station from EV Charge, click Disconnect.

Configuration

Under details station page, specific live configuration parameters/variables with their values can be read from your charging stations. To achieve this, first, click Configuration. Then, on each configuration, click Read from station. In addition, you can change and push back the specific live configuration values.

Note:

The live configuration values can only be read if your station has been connected to EV Charge. To connect your charging station to EV Charge, see Connecting to EV Charge.

Information:

To understand what each live configuration variable typifies, see Live configuration parameters.

Update station

Under stations, to update a charging station, first, click Details; it shows the details of the charging station. Then to update, click Update.

Note:

All information filled out under the create station section can be updated except for the Code.

Warning:

Want to switch Area of the Charging Station? This change may impact the history of charging Sessions and may corrupt data about your charging infrastructure, if exposed in roaming. If you are exposing your charging infrastructure in roaming, we advise you to discard (close) the Charging Station structure and open a new one.

Delete station

Under stations, to delete a charging station, click Delete.

Charger

The charging station created in EV Charge represents the networking component. Once the charging station is created, a representation of your physical charger and connector can be created. To create a charger in EV Charge, see create charger.

Information:

By OCPP terminology, you have a charging station representing the highest hardware level. The charging station can be described as a networking component connecting and communicating with EV Charge. The charger/charging unit, which belongs to the charging station, represents the physical charger with multiple or one connector/sockets/plugs.

Note:

With OCPP 1.6, a charging station can have only one charger. It is like a charger with the networking component built into it directly.

However, with OCPP 2.0, multiple chargers can be created and controlled with the same networking component (one charging station).

Create charger

Under details station page, to create a new charger, click Create New Charger.

Note:

The charger will only be shown in the EV Charge - Mobile App if the charging station is configured to be visible. For more information, see Create station.

Provide a name and code for the charger. The charger’s name will be visible to end users in the EV Charge - Mobile App. The code is automatically populated; however, it can be modified as long as it is unique for each charger.

The charger’s code is vital in EV Charge. Through the code, you can generate a QR code for the charger. Therefore, end users can start a charging session in the EV Charge - Mobile App using the QR code. For more information, see Scanning a QR code.

Tip:

To create a QR code for a charger, go to an online QR code generator, change the input to text, and input/paste the code of the charger.

For instance, if the charger’s code is B1C1, to generate a QR code for the charger, input the text B1C1 to the QR code generator.

Once the QR code is generated for the charger, it can be printed and pasted on your physical charger for end users to scan to start a charging session.

Note:

The approach of end-users starting a charging session through a QR code is the optimum approach in EV Charge because it emphasizes that customers are actually at the charging station location.

For a charger with two or more connectors that can be used simultaneously, when generating a QR code, the connector code must be included in the charger’s code as part of the text that gets converted to a QR code.

Tip:

To create a QR code for a charger with two or more connectors that can be used simultaneously, go to an online QR code generator, change the input to text, and input the code of the charger. Then, add a semicolon (;) and continue with the connector code.

For example, the charger code B1C1 and the connector code 22_kW will be inputted in the online QR code generator as follows: B1C1;22_kW. The same can be done for the second connector.

Therefore, this creates two QR codes, one for the first connector and the other for the second.

Note: This procedure is only for chargers with two or more connectors that can be used simultaneously.

The Physical address represents the MAC address of the charger.

Reservable indicates whether the charger allows reservations. For more information, see Reservations. Use the Reservable toggle switch to enable/disable.

Roaming indicates whether the charger is available for roaming. For more information, see Roaming. Use the Roaming toggle switch to enable/disable. For the charger to be applicable and exposed in roaming to third party providers, populate roaming id attribute as an identifier with unique non-blank value. Roaming id attribute is required for roaming, but please note that this identifier may not be used in every roaming protocol, due to different protocol rules.

The Electric current type represents the charger’s electricity flow setup.

The Charging profile limits the charger’s power output based on a fixed schedule. For instance, the charger outputs a maximum of 20kW of power at night. While at day, the output is lowered to 10kW of power. For more information, see Charging Profiles.

Note:

Adding a charging profile to a charger and enabling dynamic load balancing on the charging area are mutually exclusive in EV Charge.

The Custom field is a key-value pair, enabling you to include additional information for the charger.

Note:

Whenever a charging session occurs on a charger, the key-value pair included in the custom field will be transmitted to Monetization as part of the session.

The Custom field can also be used to categorize and parameterize your charging infrastructure.

For instance, suppose the key-value pair for a location category:

Key	Value
location_category	city
location_category	highway
location_category	suburb

By assigning these parameters to the charger as custom fields, in Monetization, when defining the prices that end users would pay, the parameters can be used to affect the price. For example, chargers in the city can be more expensive than those in the suburb.

Information:

Multiple connectors can be added to a charger in EV Charge. To achieve this, see Create connector.

Create connector

Under create charger, to create a connector, click Create New. Provide a name and code.

Tip:

Give the connector a name that will be useful to end users; the connector name is visible to the customer in the EV Charge - Mobile App.

The connector types are standardized types that let your end users know in the EV Charge - Mobile App whether or not the connector is compatible with their vehicle.

For the connector to be applicable and exposed in roaming to third party providers, populate roaming id attribute as an identifier with unique non-blank value. Roaming id attribute is required for roaming, but please note that this identifier may not be used in every roaming protocol, due to different protocol rules.

The most commons connector/socket types to be used are:

CCS 1: Known as Combined Charging System 1 (CCS) Combo 1, CCS1.
CCS 2: Known as Combined Charging System 2 (CCS) Combo 2, CCS2.
Type 1: Known as Type 1, SAE J1772, J plug, IEC 62196 Type 1.
Type 2: Known as Type 2, Mennekes, IEC 62196 Type 2.
Type 3: Known as Type 3, Scame, IEC 62196 Type 3.
ChaoJI: Known as ChaoJI.
GB/T: Known as Guobiao GB/T 20234.2.
CHAdeMO: Known as G105, JARI G105-1993, CHAdeMO.

Wattage limit: Connector’s maximum electric power limit (Watts). Amperage limit: Connector’s maximum electric current limit (Amperes). Voltage limit: Connector’s maximum electric voltage limit (Volts).

The Wattage, Amperage and Voltage limits depict the connector’s maximum capability. Limits are reflected on:

Utilized when Tridens EV Charge is performing the dynamic load balancing on Area for power/current supply distribution among the connectors, which are charging the vehicles.
Limit values also serve for user experience in mobile application (filtering connectors by power), and when exposing charging infrastructure on the roaming network.
Limit values are exposed as connector’s capability in roaming protocols, like OCPI and OICP.

In addition, end users in the EV Charge - Mobile App can filter for a connector based on the minimum power a connector can supply. The filtering option is based on the wattage limit configured for the connector.

The Power factor represents the relationship between current and voltage and must be between 0 and 1.

A connector can have a Custom field, which can be used for parametrization and categorization. For example, if you have a charger with two connectors, with one charging faster. The price for the connector with a faster charge rate can be higher.

By clicking Save, the charger is added at the bottom of the details station page. Also, the charger will be visible in the map view in EV Charge. Furthermore, the charger and the connector(s) will also be visible to end users in the EV Charge - Mobile App.

Update charger

Under details station page, to update a charger, click Update.

Note:

All information filled out under the create charger section can be updated except for the Code.

Delete charger

Under details station page, to delete a charger, click Delete.

Map view

Under the map view, all chargers are shown on a map based on the charging area’s location. By selecting a specific Charger on the map, it shows the distance away from the charger. Also, it shows the charger’s name, location, and charging status. In addition, the charger’s connector(s) are shown, including their status.

Connectivity Configuration

The connectivity section of the charging station specifies the protocol and the rules for the communication between the charging station and the central system. Communication protocol, Connection policy and Connection identifier are the rules which need to be set properly.

As station is the side which initiates the connection to the Tridens EV Charge’s central system, Tridens EV Charge’s dashboard shows up the allocated connection URL based on the assigned connection settings. Connection configuration guidelines are described in the subtitles.

Charging device needs to be configured with the central system’s allocated URL. How this is done differs among different charging device implementations, as they may provide web interface, mobile device interface or configuration on screen.

Figure 2: Tridens EV Charge central system’s allocated connection settings for the charging station

Communication Protocol

The Communication protocol, which can be OCPP 1.6 or 2.0.1 specifies the protocol your charging station uses to communicate.

Figure 3: Communication protocol selection for the charging station on the Tridens EV Charge’s central system dashboard

Connection Identifier

Unique Connection identifier needs to be assigned for the charging station on Tridens EV Charge, so the device can be identified when communicating with the central system.

Figure 4: Connection identifier of the the charging station, as assigned on the Tridens EV Charge’s central system

Connection Policy

Connection policies as security profiles for the selected communication protocol between the charging device and the Tridens EV Charge’s central system.

Connection policy options:

WSS: WebSocket encrypted communication.
WSS with Authentication: WebSocket encrypted communication which requires authentication credentials, by which the charger is verified for the access rights.
Disabled: Connection and communication not allowed.

Figure 5: Connection policy selection for the charging station on Tridens EV Charge dashboard

Connection Example

Given the WebSocket URL link:

wss://app.tridenstechnology.com/ev-charge/gw-comm/your-charging-company/station-01

Breaking down the link:

wss # Communication protocol.

app.tridenstechnology.com # Tridens server address.

/ev-charge/gw-comm/your-charging-company # Allocated service path.

station-01 # The unique identifier of your charging station.

The WebSocket URL link (wss://app.tridenstechnology.com/ev-charge/gw-comm/your-charging-company/station-01) should be configured into your charging station. Then, your station will send a handshake request to EV Charge to establish a connection; it follows this order:

Your station introduces itself as station-01 through the handshake request.
EV Charge checks if the unique identifier (station-01) is a valid identifier of a charging station in its system.
A successful connection is made if it is a valid identifier.

Tip:

Establishing a connection with EV Charge can differ from one charging station to another because different manufacturers may have different interfaces. However, the logic behind it is technically the same.

Additional notes about WSS charger connection with Tridens’ central system. There are multiple ways to use WSS:

WSS without authentication.
WSS with basic authentication, accepting username/pass combination.
WSS with basic authentication, accepting token.

Troubleshooting when unable to establish the connection with the central system:

Ensure that the charger is configured to automatically reconnect to the central system, if for any reason disconnection occurs.
Charger’s on-site configuration, if settings are reset for any reason.
Charger’s network stability.

Charger’s session settings

See Session Rating Settings.

Boot Configuration

Configuration of actions which are performed once the charging station connects to the Tridens EV Charge’s central system. Boot configuration settings are used to synchronize the charger with the central system, once the connection is established. Whether these settings need to be enabled or disabled, depends on the charger implementation. Some chargers automatically send these messages, once they connect to the central system, the others don’t do that and for the latter we advise enabling the triggering at boot.

The following are the boot configuration settings:

Trigger boot notification: Trigger station to send the boot notification after the connection establishment. It synchronizes the charging device’s information on Tridens EV Charge central system, by triggering the charging device to report the boot notification. Information include data of serial number, vendor, model, firmware version, modem ICCID, modem IMSI.
Trigger status notification: Trigger station to send charger/connector status reports, so system obtains the latest status values after the connection establishment. It synchronizes the status of charger and connectors by triggering the charging device to report the latest statuses.
Trigger heartbeat: Trigger heartbeat for station’s clock sync after the connection establishment with the central system. It synchronizes the charger’s clock to the clock of the Tridens EV Charge’s central system, after the connection establishment between the charging device and the central system.
Clear charging profiles: Clears any previously set charging profiles with limits on the station. Any configured profiles will apply after. Wattage/amperage limits on the charging device can be set by using the charging profiles configuration. See Charging Profiles Configuration.

Figure 6: Charging station’s boot configuration on Tridens EV Charge dashboard

Live Configuration Parameters

Live configuration parameters/variables for OCPP can be read from the charge point or set to the charge point without any database persistence.

Supported standardized variables constitute the following:

General variables
Transactional variables
Metering variables

General variables

Name	Description
Connector phase rotation	Connector’s phase rotation in respect to the connector’s electrical meter.
Heartbeat interval	Seconds inactivity interval (no exchanged messages) after which charge point sends heartbeat to central system.
Reset retries	Number of times to retry unsuccessful charge point reset.
Web socket ping interval	Client-side ping interval. When 0, it is disabled.

Transactional/session variables

Name	Description
Transaction message attempts	Number of retries the charge point submits transactional message after failed submit.
Transaction event interval	Seconds wait time before resubmitting a transactional message.
Stop tx on ev side disconnect	If true, the charge point stops the transaction if cable unplugged from EV.
Stop tx on invalid id	If true, charge point will stop an ongoing transaction when it receives a non-accepted authorization status.
Ev connection timeout	Seconds interval for which transaction waits in preparing state for a plug-in, before going back to available.
Allow Offline Tx For Unknown Id	Indicates whether offline cache authorizations are supported prior session start (e.g., an RFID), when the charger is not connected to the central system (by OCPP).

Metering variables

Name	Description
Aligned data interval	Seconds clock aligned interval for measuring, starting at 00:00:00. Measures are accumulated per period. 0 disables it.
Aligned data measurands	Clock-aligned measurands to be included in meterings regarding Aligned data interval.
Sampled data interval	Seconds interval for sampling meter data. 0 disables it.
Sampled data measurands	Sampled measurands to be included in meterings regarding Sampled data interval.
Aligned data measurands at transaction end	Measurands to be included in transaction end event for every Aligned data interval of transaction.
Sampled data measurands at transaction end	Sampled measurands to be included in transaction/session end event.

Authorization

Name	Description
Local offline authorization	Controls whether the charger will authorize the user when they are offline by using the authorization cache and/or local authorization list.
Local pre-authorize	Controls whether the charger will use authorization cache and/or local authorization list to start a session without waiting for an authorization response from the central system. The central system can later deauthorize the user at session event exchange.
Local auth list enabled	Indicates whether the local authorization list is enabled on the charging station.
Set local list max. length	Charging station’s maximum number of identifiers that can be sent in a single request to update the authorization list.
Local auth list	Maximum number of identifiers that can be stored in the local authorization list of the charging station.
Allow offline session of unknown id	Indicates whether the station supports the unknown-offline-authorization feature.
Authorization cache enabled	Indicates whether the authorization cache is enabled on the charging station.
Authorize remote start	Indicates whether additional authorization at remote session start request is enabled on the charger. If enabled, the charger issues authorization when it receives the remote start request from mobile/web.

Plug & Charge

Name	Description
Plug & charge enabled	Indicates whether the charger supports ISO 15118 Plug&Charge feature.
Central contract validation	Indicates whether the charger can provide a Plug&Charge contract certificate that it cannot validate to the central system for validation as part of the authorization.
Offline contract validation	Indicates whether the charger will try to validate a contract certificate when it is offline and not connected to the central system (by OCPP).

View Logs

Logs can be a helpful tool for the charging infrastructure operators to better understand the events over the charging infrastructure and communication between the charging station and the central system. Operators usually utilize them at onboard testing and for troubleshooting.

To view the logs, navigate to the stations view, find and open the charging station of interest and hit the button View Logs on the top right. Logging review tool shows up and users can choose between the two options to read logs by selecting the tab on the top of the tool.

The first option are the logged notifications and the second are the OCPP logs covering the communication between the charging station and the central system of Tridens EV Charge. Logs are filterable by the time range and can be exported by CSV or Print options which appear on the bottom of the tool.

Figure 7: Charging station view and the navigation to view the logged notifications.

Logged Notifications

Notification logs are present based on the system configuration for Notifications and Log Notifications Setup.
Use Events tab to view.
Logs will appear after the configuration is established, meaning that past events are not logged.

Figure 8: Logged notifications of the charging station.

Logged OCPP Communication

Logs of Open Charge Point Protocol (OCPP) communication exchanged between the central system of Tridens EV Charge and the charging station.
Use OCPP tab to view.

Figure 9: OCPP communication logs of the charging station.

Local Authorization Management

Local authorization feature provides that the charger can authorize customers/drivers without using the central system, while being offline.

To manage the charging station’s local authorization list, the following operations are available from the perspective of the central system of Tridens EV Charge:

Send local authorization list (full update).
Send local authorization list (differential - partial update).
Get local authorization list version.
Handling the charging station’s configuration settings for local authorization.

Local authorization and authorization cache are separate features and cache does not impact the local authorization list.

Authorization Cache

This feature needs to be used carefully and might only be proper in the following cases:

For the businesses, where the charging service is available only for post-paid customers, as sessions regulated by the local authorization cache are not authorizing any customer/driver resources, to verify whether customer has enough funds.
Charging station is located in area with non-stable network connection.

Authorization cache impacts:

Cache entries may contain expiry dates, which are considered at validation.
If authorization happens and an invalid identifier is present in the cache while the charger is online, the charger uses the central system to authorize.
Authorization cache has no impact on the local authorization list! These two features are separated and local authorization lists are fully controllable from the central system. Also, identifiers from local authorization list should not be added to the authorization cache. If both are used, the local authorization list has priority over the authorization cache for the same identifiers.

Local authorization and authorization cache are separate features and cache does not impact the local authorization list.

Docs: Charging Profiles

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

Charging profile explained
Create a charging profile
Details charging profile page
Update charging profile
Delete charging profile

To access this section in EV Charge, from the Menu, click Charging profiles. A paginated list of all charging profiles is shown in a tabular format.

To generate the charging profiles list in a spreadsheet, click CSV. To print, click Print, and to copy, click Copy.

Note:

They are generated, printed, and copied per paginated page.

Charging profile explained

Configuring a charging profile is optional among the components in setting up a charging infrastructure in EV Charge.

A charging profile is commonly used with private chargers at home, where you want to give specific limitations to the power output based on a scheduled period. For instance, at night, the charger outputs a maximum of 20kW of power; at day, it is lowered to 10kW of power.

Note:

A scheduled limit created in a charging profile is not considered as dynamic load balancing. This is because a single charger will be limited to a specific maximum power output based on the fixed schedule, and the power output only acts by the schedule.

Enabling dynamic load balancing in EV Charge can only be achieved from the charging area. For more information, see Areas.

When dynamic load balancing is enabled, smart charging profiles are not applied.

Interoperability

Charging profiles feature utilizes standardized OCPP defined charging profiles, so as long as CPO’s charger supports the OCPP charging profile operations, then interoperability with this feature of Tridens EV Charge is available.

Four actions/subpages can be performed/viewed under this section, namely:

Create a charging profile
Details charging profile page
Update charging profile
Delete charging profile

Create a charging profile

Under charging profiles, to create a charging profile, click Create new. Provide a name and code.

Note:

The code is a unique identifier of an object. It can be used during integration with the EV Charge API.

The Stack level represents a priority; therefore, the charger will use the charging profile with the highest priority number if multiple charging profiles are configured on the charger.

Note:

A higher number indicates a higher priority.

Select the Type, which could be one-time or recurring. If recurring is selected, the schedule restarts periodically after the first schedule period ends. Also, choose between a daily or weekly recurrence for the recurring type.

Purpose indicates the context of the limit, whether it is charger total limit or default limit for the charging sessions.

a. Charger total limit represents maximum power/current available on the whole Charger. Never applies for the Connector.

b. Session default limit represents default power/current limit for each session on Charger/Connector. This limit can be overridden by the session specific limit.

Energy limit only applies when Session default limit is selected. The limit represent max. energy amount (kWh) to be consumed by the EV for a session in case when the charging profile is explicitly selected/assigned for the session. When the limit is achieved on session, the session is requested to stop and the termination phase applies. Empty value represents no limit.

The Duration indicates the length of time for the charging profile after the schedule is kick-started. It could be in minutes or hours. It is applicable only for the recurring type.

Configuring the validity period denotes when the charging profile will be active (in force). The Schedule start marks when the configured schedule periods should begin to apply on the charger.

The Unit represents the unit of measurement that will be applied under the Schedule periods limit.

The Scheduling periods represent turning points, where milestones can be created on how to limit the power output. It is based on the amount of time configured for the Duration.

For instance, by setting the Duration to last for 24 hours, the following milestones can be created:

Start point = 0, Unit = Hours, and Limit = 5000 Watts(W).
Start point = 6, Unit = Hours, and Limit = 10000 Watts(W).
Start point = 18, Unit = Hours, and Limit = 5000 Watts(W).

Explanation: The first milestone means that at 0 hours (which represents midnight), the power output is limited to 5000W. The second milestone means that at 6 hours (which is 6 AM), the power output is limited to 10000W. Finally, the third milestone implies that at 18 hours (6 PM), the power output is limited to 5000W.

Information:

The charging profile in EV Charge aligns with the Open Charge Point Protocol (OCPP) documentation regarding configurability.

Once the charging profile is created, it can be assigned to a charger. If the charger accepts the charging profile, it will become operative based on the Schedule start configuration.

However, if a charger rejects a smart charging profile, it could be that it is not a supported operation or a malfunction in its software.

Details charging profile page

Under charging profiles, to see the full details of a charging profile, click Details. It contains the following:

Name
Code
Type
Unit
Recurrency
Stack level
Scheduling start
Validity
Duration

Below the above information are all the scheduled periods, which include the start point, unit, and limit.

Update charging profile

Under charging profiles, to update a charging profile, first, click Details; it shows the details of the charging profile. Then to update, click Update.

Note:

All information filled out under the create a charging profile section can be updated except for the Code.

Delete charging profile

Under charging Profiles, to delete a charging profile, click Delete.

Note:

Deleting a charging profile already used in other parts of EV Charge cannot be done. Every particular reference to the charging profile first has to be deleted.

Docs: Log Notifications Setup

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

Configuration
- Basic Example
- Advanced Example
Reading the Logs

Tridens EV Charge platform can be utilized to log and review the occurred events by the charging infrastructure or those related to the charging sessions control. Feature is called log notifications and is based on the instructions of System Configuration - Notifications, where logging notifications configuration can be made by the Log publishers.

Configuration

Operators can configure to be notified on the wide range of events, related to the charging infrastructure availability and charging session control.

A few events to consider enabling for log notifications, so the operators can track the charging infrastructure’s behavior:

Station connected
Station disconnected
Connector status changed
Reservation created
Reservation canceled
Session started
Session refused
Session’s charging ended
Session ended
Session’s state-of-charge (EV battery) limit breached
Session’s charge time limit breached
Session’s park time limit breached
Session’s fault time limit breached

For the complete list of actions in different scopes, see Notifications.

Basic Example

Basic example is represented in Figure 1 about adding a new logging notification configuration for the event when the charging station successfully connects to the central system of Tridens EV Charge. Log publisher is used with the default template format, as template attribute remained unselected.

Figure 1: Log notification configuration for charging station’s connection establishment with the central system.

Advanced Example

Advanced example is represented by Figures 2 and 3, where Figure 2 shows the logging notification configuration for the event when monetary limit of 50€ has been breached for the customer’s charging session. Filter Monetary limit is mandatory for the event and is set to 50€ threshold in this case. Instead of a default logging notification template, the custom configured notification template named as ‘Monetary Limit Breach 50€’ can be used. Figure 2 shows such notification template configuration on the different section of the UI.

Figure 2: Log notification configuration for the charging session’s monetary limit breach of 50€.

Figure 3: Notification template configuration for monetary limit breach of 50€ for the charging session.

Reading the Logs

Navigate to Stations and select the specific station for which you would like to review its logs and click under Actions to view station details. On the top right icons on the specific station’s page, click View logs icon (Figure 4).

Figure 4: Navigating to view the charging station’s notification logs.

The paginated logs view shows up, as in Figure 5. Time filters can be used to restrict the results range. Use Preferences to manage pagination and appearance.

Figure 5: Filtering the logs.

Docs: Notifications Guidelines

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

Notifications Setup Guidelines in General
Notifying EV Drivers
Notifying the Operators

Notifications Setup Guidelines in General

Charging providers usually want to enable the notifying features, so they can inform the EV drivers about the status of their charging session or to inform themselves about the status of the charging infrastructure.

This section can serve as a guide on the options which can be utilized for the notifying. Base general steps for configuring the notifications can be found in Notifications section.

See the following references to find notifications setup technologies:

Notifying EV Drivers

EV drivers (also end users, end customers), usually want to be notified about the status of the charging sessions. Setup of these kind of notifications differs based on the session handling configuration, as described in Sessions - Session Rating Settings. Full list of available notification actions is described in Notifications Scopes and Actions.

The most used actions for notifying the EV drivers during the session by using the push notifications or SMS for mobile devices are the following:

Charging end - Indicating that session’s charging has ended, but parking fees may apply after. You can notify the driver that the charging process is done and prompt them to remove the vehicle.
Battery percentage limit - Indicating that certain amount of battery percentage (configurable) has been breached for the session, if reported by the charger. E.g., EV battery achieved 85%.
Energy limit - Indicating that certain amount of energy in kWh (configurable) has been spent for the session so far. E.g., EV session’s energy consumption achieved 40 kWh.
Charge time limit - Indicating that certain time for charging (configurable) has been spent for the session so far. E.g., EV session charging duration achieved 30 minutes.
Park time limit - Indicating that the certain parking time (configurable) has been spent for the session so far. E.g., EV session in parking mode duration achieved 15 minutes. Prompt driver to remove the vehicle and release the spot.
Park time threshold breach - Indicating that the parking time spent for the session has achieved the configured rating threshold of the EV charging session. From this point, parking time fees may apply. Based on configuration of Sessions - Session Rating Settings.
Monetary limit - Indicating that certain amount of money (configurable) has been spent for the session so far. E.g., EV session charging cost achieved 25€.

For the cases of notifying EV drivers by an email, the following actions may be useful:

Session end - Indicating that the charging session has ended and summary can be published.
Session refused - Indicating that the charging session didn’t succeed, as initial authorization of customer’s resources didn’t succeed.

Notifications are headed to the session’s driver/customer, when an action is related to the specific customer and notification rule’s receiver of type ‘Customer’ is selected. See Fig. 1 below. Applies for the session related actions, as these are customer related. Customer’s primary contact info is used for it, so push notification reference, email or phone number for SMS is taken from there.

See Notifications - Create Notification Rule section.

Fig. 1: Example of notification rule configuration headed to the customer when the EV charging session ends.

Content formatting definition example:

Charging session ${object.contents.session.id?c!'/'} ended.
Consumed ${object.contents.session.totalEnergy?c!'/'}kWh for the cost of ${object.contents.session.usedAmount?c!'/'}€.

Results in:

Charging session 9718 ended. Consumed 29.33kWh for the cost of 8.28€.

Notifying the Operators

Operators may be interested in being notified when significant changes appear on the charging infrastructure. Informing can be done by an email, SMS, logging or API call. Full list of available notification actions is described in Notifications Scopes and Actions.

Actions which can be especially helpful to operators:

Station connected - Indicating that the charging station has established a connection with the central system of Tridens EV Charge. If re-connections are happening, the station may need an urgent review.
Station disconnected - Indicating that the charging station has been disconnected from the central system of Tridens EV Charge. May need an urgent review, as connected station is necessary for availability of operations.
Station booted - Indicating that charging station has sent the boot notification. If the boot was not intentionally triggered, it may need a review.
Status changed - Indicating that the charger’s or connector’s status has changed. Advised to use notification for the transition to the ‘faulted’ status, as it usually needs to be troubleshooted.
Fault time limit - Indicating that certain fault time (configurable) has been spent for the charging session so far. E.g., EV session in fault mode duration breached 5 mintues. Needs operator’s review.

Operator related notifications are usually headed to the specific address (i.e. email), hence notification rule’s receiver of type ‘Base’ is usually selected with the contact populated. See Fig. 2 below.

Alternativelly, email sender (from) can be determined on email template as well.

See Notifications - Create Notification Rule section.

Fig. 2: Example of notification rule configuration headed to the specific operator’s email address when the charging station device disconnects from the central system and the occasion needs to be reviewed.

Content formatting definition example:

Charging station ${object.contents.charging_station.name!'/'} has disconnected from the central system. Id:${object.contents.charging_station.id?c!'/'} Code:${object.contents.charging_station.code!'/'} Address: ${object.contents.charging_station.address!'/'} ZIP: ${object.contents.charging_station.zip!'/'} City: ${object.contents.charging_station.city!'/'} Country: ${object.contents.charging_station.country!'/'} Latitude: ${object.contents.charging_station.latitude?c!'/'} Longitude: ${object.contents.charging_station.longitude?c!'/'}

Results in:

Charging station Tridens Building has disconnected from the central system. Id:5274 Code:f1db01db-3f7c-4804-9d9a-e54cb1037040 Address: Titova 2a ZIP: 2000 City: Maribor Country: SI Latitude: 46.56007700000001 Longitude: 15.6510651.

Docs: Sessions

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

Sessions Overview
Session Status
Session Actions on the Dashboard
Idle Session Control
Session Rating Settings
Requesting the Session to Start
Duration Scopes
Requesting the Session to Stop
Payment Authorization Policy
Authorization Mode
Termination Strategy
Session Retry Rating
Session Retry Billing
Idle Session Settings
Session Reactivation
View Logs
Limitations

Sessions Overview

To access this section in EV Charge, from the Menu, click Sessions. A paginated list of all sessions from a specific period is shown in a tabular format.

To produce charging sessions, please refer to Charging Sessions Integration, to find the guidelines.

To generate the sessions list in a spreadsheet, click CSV. To print, click Print, and to copy, click Copy.

Note:

They are generated, printed, and copied per paginated page.

Information:

You can filter for a session by date-time, customer ID, or/and status.

The session list will be empty if no active charging session has been made on the charging network.

Note:

A charging session is started by end users in the EV Charge - Mobile App. For more information, see Starting a charging session.

For all charging sessions, it shows:

the charger and connector used to charge the vehicle
the date-time the session started and ended
session duration scopes (charge time, park time)
the customer ID
the total energy (kWh) consumption from the session
the monetary amount

An ongoing session (a session in progress) will be shown with a Status flag as In progress. Also, the consumption and amount of the active session will be updated in EV Charge as any live update occurs.

Information:

You can forcefully stop an ongoing session under Actions.

Note:

Clicking the customer ID on a session will take you to Monetization, where the customer information resides.

Session Status

Represents the latest status of the session.

Session status	Description
Ready	Session was requested to start by the driver. Central system is waiting for the charger to start the charging process.
Refused	Session refused to start. Reason could be insufficient driver’s resources, configuration issue or other failure.
Reserved	Session is reserved for the driver. Only the driver which reserved the charger can proceed to charging until reservation expires. Reserved session can transition to an actual charging or expires and closes otherwise.
In progress	Session is charging.
Limit reached	Indicates that session has reached one of the configured limits: - Monetary limit - Energy limit - Charge time limit - Not able to authorize additional driver’s resources
Closing	Session is in the closing process. Triggered when force session stop is triggered by the Tridens EV Charge.
Closed	Final stage when session is completed and driver’s resources are spent. Final stage of session depends on the session settings configuration, whether it ends by the charging end or by parking end. See “Session settings”.
Rating failed	Indicates that session is over regarding the session settings, but the driver was not monetarily rated. Retry operation can be used on domand or by an automated job execution.
Billing failed	Indicates that session is over regarding the session settings, but the pay-now driver was not billed. Retry operation can be used either on demand or by an automated job execution.

Session Actions on the Dashboard

Session action	Description
Force close	While session is ready/in-progress, system operator may demand to forcefully close the session by using the EV Charge dashboard, by clicking the close button on the right side. This operation requests the session to stop on the charging infrastructure, but if the infrastructure is not responding for any reason, session is forcefully closed. Driver is rated, session closes. See more details of this status in Requesting the Session to Stop.
Retry rating	While session is in rating failed status, retry rating button is available for use. When triggered, session rating is retried. See more details of this status and possible actions in Retry Session Rating.
Retry billing	While session is in billing failed status, retry billing button is available for use. When triggered, session billing is retried. See more details of this status in Session Retry Billing.

Session action

Description

Force close

While session is ready/in-progress, system operator may demand to forcefully close the session by using the EV Charge dashboard, by clicking the close button on the right side.

This operation requests the session to stop on the charging infrastructure, but if the infrastructure is not responding for any reason, session is forcefully closed.

Driver is rated, session closes. See more details of this status in Requesting the Session to Stop.

Retry rating

While session is in rating failed status, retry rating button is available for use.

When triggered, session rating is retried. See more details of this status and possible actions in Retry Session Rating.

Retry billing

While session is in billing failed status, retry billing button is available for use.

When triggered, session billing is retried. See more details of this status in Session Retry Billing.

Idle Session Control

The pre-configured recurring background job checks for idle ready/ongoing sessions and also closes any expired reservations. The session is idle, regarding the Site/Operator settings. See Idle Session Settings.

Session Rating Settings

These are settings which apply for the rating of session, considering different metric types.

Rating settings are determined on the following levels:

Site (lowest priority)
Operator
Charger (highest priority)

Settings are overridable, meaning the settings of the highest priority level are used.

Below are the rating settings available:

Table 1: Description of session rating settings.

Setting name	Unit/value	Description
Energy step	kWh	Energy step for rating authorization control (kWh).
Charge time step	seconds	Charge time step for rating authorization control (seconds).
Park time step	seconds	Park time step for rating authorization control (seconds).
Park time threshold	seconds	Defines seconds threshold, as point in park time duration at which parking becomes ratable. Difference between the total park time and threshold (park_time minus park_time_threshold) is ratable quantity. Rating authorizations start executing once threshold breaches.
Reservation	true / false	Indicating whether the charging reservations are being authorized by rating.
Termination	Applicable values of: - Session end - Park time end	Indicating which action stops the charging session on the server side. See termination strategy for further explanations.
Monetary limit	Site currency	Max. monetary amount allowed for a session. Empty value represents no limit. When the central system of Tridens EV Charge detects that the charging session’s used monetary amount is above the configured `Monetary limit` value for the charging session, it requests the charger to stop that charging session. In order for a session to actually end as closed and rated on the central system, charger needs to report the final stop event or if session is detected as idle. Final used amount is persisted on the session based on the charger’s reports, as it needs to track the actual consumption reported.
Energy limit	kWh	Max. energy amount to be consumed for a session. Empty value represents no limit. When the central system of Tridens EV Charge detects that charger’s reported energy is above the configured `Energy limit` value for the charging session, it requests the charger to stop that charging session. In order for a session to actually end as closed and rated on the central system, charger needs to report the final stop event or if session is detected as idle. Energy (kWh) is persisted on the session based on the charger’s reports, so if the energy limit is set 50 kWh and the charger reports 57 kWh, the system is going to use 57 kWh, as it needs to track the actual consumption reported.
Charge time limit	seconds	Max. duration allowed for a session to charge. Empty value represents no limit. When the central system of Tridens EV Charge detects that the charging session’s elapsed charge time is above the configured `Charge time limit` value for the charging session, it requests the charger to stop that charging session. In order for a session to actually end as closed and rated on the central system, charger needs to report the final stop event or if session is detected as idle. Final charge time is persisted on the session based on the charger’s reports, as it needs to track the actual consumption reported.
Payment auth. policy	Applicable values: - None - Initial auth only - Auth control	Payment authorization policy which applies for pay-now customers and defines how charging session is controlled by payment provider’s authorizations. See payment authorization policy for further explanations.
Payment auth. amount	Site currency	Amount used for session’s payment authorizations. See payment authorization policy for further explanations.
Charge time price	Site currency	Price per hour of charging time. Used in scope of simple pricing.
Park time price	Site currency	Price per hour of parking time. Used in scope of simple pricing.
Energy consumed price	Site currency	Price per kWh of energy consumed. Used in scope of simple pricing.
Home roaming energy price	Site currency	Home roaming energy price (per kWh). Applies for monetary amount calculation, if session is in roaming on CPO of Tridens EV Charge, but customer/driver is of third-party roaming eMSP.
Home roaming charge time price	Site currency	Home roaming charge time price (per hour). Applies for monetary amount calculation, if session is in roaming on CPO of Tridens EV Charge, but customer/driver is of third-party roaming eMSP.
Home roaming park time price	Site currency	Home roaming park time price (per hour). Applies for monetary amount calculation, if session is in roaming on CPO of Tridens EV Charge, but customer/driver is of third-party roaming eMSP.
Home roaming reservation time price	Site currency	Home roaming reservation time price (per hour). Applies for monetary amount calculation, if session is in roaming on CPO of Tridens EV Charge, but customer/driver is of third-party roaming eMSP.
Home roaming reservation fixed price	Site currency	Home roaming fixed reservation price (flat fee). Applies for monetary amount calculation, if session is in roaming on CPO of Tridens EV Charge, but customer/driver is of third-party roaming eMSP.
Start Restriction - Connector Occupied	True / False	Indicates whether the connector/socket is required to be occupied (EV connected) for the charging session start request to proceed.
Reactivation grace period	Seconds	Grace period allowed for session reactivation after closure. Empty or 0 value indicates no limit.

Requesting the Session to Start

Sessions can be initiated in the following ways:

Driver as mobile user requests to start the charging session on the selected connector. The central system verifies that customer for the sufficient monetary resources and in case of success, it forwards the request to the charging infrastructure and requests it to start the charging process, upon which the charging session is expected to start.
Driver swipes an RFID device, uses NFC, Plug & Charge or any other way to initiate the session authorization at the charger side. Charger uses the identification means and asks the central system to verify the customer, whether he/she has sufficient monetary resources to charge and in case of acceptance, the charging is expected to start.
Driver starts charging immediately on the charging station, without prior authorization. In this case, the session customer is not known and not charged.

When customer is detected, but is not successfully authorized for the charging session, the session is persisted as rejected. Otherwise no session is persisted.

Duration Scopes

While the charging session is in progress, the applicable charger’s connector status impacts how the session is being tracked by the Tridens EV Charge central system and thus how it appears to the drivers on mobile application.

Session duration is being separated into scopes of charge time, park time, reservation time and fault time. See table below to see which status applies for the specific duration scope.

Table 2: Duration scopes and applicable Connector statuses.

Duration Scope	Applicable Connector Statuses
Charge time	Charging
Park time	Preparing, Occupied, Suspended EV, Suspended EVSE, Finishing, Available.
Fault time	Faulted, Unavailable
Reservation time	Reserved

Requesting the Session to Stop

While session is ready/in-progress, system operator may demand to forcefully close the session using the Tridens EV Charge dashboard, by clicking the close button on the right side. This operation requests the charging session to stop on the charging infrastructure, but if the infrastructure is not responding for any reason, session is forcefully closed.

Driver is rated, and the session closes.

The table below shows how session stop requesting may reflect on the charging infrastructure.

Table 3: Charging infrastructure reflecting the session stop command.

Stop Response Type	Description
Accepted	Charging infrastructure accepted the stop request. It is expected that it will send the session stop event.
Rejected	Session is not being closed on the charging infrastructure.

Force session close covers the following issues:

Remote stop request is accepted by the charge point, but no stop event confirmation comes from the charging infrastructure.
Remote stop requests are always rejected by the charging infrastructure.
Charging infrastructure is not responding due to lost connection to the central system, lost track of the session.

Payment Authorization Policy

Payment authorization policy applies for customers of pay-now type and defines how charging session is controlled by payment authorizations. The setting is used along with the payment authorization amount.

The following settings apply:

None: Charging session is not controlled by payment authorizations.
Initial authorization only: Charging session initialization depends on the success of the initial payment authorization.
Authorization control: Charging session progress depends on the continuous payment (re)authorizations.

Example with Initial authorization only policy:

When environment is configured for Initial authorization only for payment auth. amount of $10, it means the system will check for $10 on the payment card (authorize/lock the amount) at the beginning of the session, and if this operation is successful, then it will allow the user to charge as much as they like. At the end, the system will collect/capture the original authorized amount of $10, and if the total session price exceeds it, it will try to take the remaining funds as a direct card charge. This also comes with a risk of the user lacking the remainder of the funds and being unable to pay.

Our recommendation would be to raise the initial authorization amount to a value that will cover most of the sessions (like an average session price) in a single payment transaction. You may want to use the Authorization control policy instead. This policy will perform another authorization when the first one is fully consumed, ensuring that the user always has enough funds on the card to continue the session or stop it if no more funds are available.

Example with Authorization control policy:

Once Authorization control is configured for payment auth. amount of $5, the system will try to authorize $5 every time the previously authorized $5 is consumed. Then at the end of the session it will collect (capture) all of the authorizations. This way we are ensuring the user always has enough money on the card to continue the session. If we receive a negative response from the payment provider for authorization, then our system will stop the session and collect the amount the customer has authorized up to that point.

If the charging session would progress to the cost of $22.88, then the session would result in 5 x $5 authorizations, where 4 of them would be fully captured, and one would only capture for $2.88. This would also mean 5 payment gateway transactions, which is why we recommend raising the authorization amount in order to lower the number of necessary transactions, impacting the cost.

Authorization Mode

Authorization mode indicates whether a charging session is linked to a Monetization customer, a payment intent, a roaming provider, or is open/public.

Table 4: Authorization modes of session.

#	Mode	Features
1	Monetization Customer	- The session is tied to a known customer in the Monetization system. - Charges are applied directly to that customer’s account.
2	Payment Transaction	- The session is linked to a payment intent, not a customer. - The customer is unknown to Monetization. - Authorization and payment capture are handled by the payment provider. - Useful for guest users or single-use charging. - Session payment authorization settings are part of this mode with the final monetary capture.
3	Roaming Customer	- Session initiated by a third-party EMSP (e-Mobility Service Provider). - The charger is part of Tridens EV Charge (CPO), but the customer belongs to the third party EMSP. - The customer is not directly known to Tridens but is authenticated via roaming.
4	Public Free	- Session was not initiated by Tridens EV Charge. - Indicates the charger is allowing free/public access without known customer or payment.

Note:

This may allow unauthorized use. Ensure this mode is explicitly intended.

Note: Use configuration rules and charger settings to control and restrict authorization modes as required by your business or compliance policies.

Termination Strategy

Once the stop session event comes from the charger, it depends on the Tridens EV Charge’s configuration of session termination strategy (see Session Rating Settings) how the event impacts the session.

If desired, the session can be completed at that point, or alternatively the session can continue to be tracked for the idle/park time, until the connector remains connected to the vehicle.

Park time end detection may be different based on the charger implementation by the manufacturer, as different actions may indicate when the charging session is over, as it can be by unplugging the connector, or until leaving the parking spot completely. So this can be configurable on the charger side.

Table 5: Session termination strategy.

Strategy name	Description
Charging end	At the session stop event from the charger, the central system stops tracking the session and applies the final session fees for the driver. Session gets closed.
Parking end	At session stop event from the charger, the central system keeps tracking the session in park time, until connector is released. At the time of connector’s final release, the central system stops tracking the session and applies the final session fees for the driver. Session gets closed.

Session Retry Rating

Session in rating-failed status indicates that the charging session is over, but the driver was not monetarily rated. Thus, retry rating operation can be used to charge the driver/customer of the charging session. The driver’s payment type, billing and payment may also apply afterwards.

Session’s rating-failed status may arise for the following reasons:

Invalid Monetization rating configuration, which causes that session can not be rated for the customer. This could be a configuration issue of rate plans, products, rating metrics or customer’s subscription-plan setup.
System maintenance work.

Session retry rating can be used in different modes to determine rating session identifier, used for Monetization charge event rating when session is in rating-failed status.

See the table below.

Table 6: Rating identifier modes of session retry rating.

Rating Identifier Mode	Description
Use existing	Existing session rating identifier is being used for Monetization rating. Default option.
Use existing, otherwise generate new	Existing session rating identifier is being used for Monetization rating. If rating fails, new rating identifier is auto-generated by the system and rating automatically retries.
Assign new	New explicit session rating identifier is assigned in the request and used for Monetization rating.
Generate new	New rating identifier is auto-generated by the system and used for Monetization rating.

Notes:

Session’s retry rating is handled by the pre-configured automated execution job in 30 minutes interval, otherwise it can be triggered for the specific session on demand.

Session Retry Billing

Session in billing-failed status indicates that the session is over regarding the session settings, but the pay-now driver/customer was not billed. Thus, retry billing operation can be used to retry billing and payment of a driver for the charging session.

Session’s billing-failed status may arise for the following reasons:

Invalid Monetization rating and billing configuration, which causes that session can not be rated for the customer. This could be a configuration issue of rate plans, products, rating metrics, customer’s subscription-plan or billing profile setup.
System maintenance work.

Notes:

Session’s retry billing is handled by the pre-configured automated execution job in 30 minutes interval, otherwise it can be triggered for the specific session on demand.

Idle Session Settings

Session on the central system is considered as idle when not receiving event reports from the charging infrastructure after a certain configured time of Site or Operator. Operator’s settings have higher priority, if set.

When session is detected as idle, the central system closes/completes it, which means that such session is not being tracked anymore.

Table 7: Idle session expiration settings.

Setting name	Description
Ready session expiration	Allowed inactivity in seconds for a ready charging session. When background job detects a ready session’s inactivity exceeding this time, it finalizes it (rating and closing). Setting impacts user’s experience. When user requests to start the new session by mobile application, the app uses this time for the countdown time display in which session is expected to transition into an active status.
Ongoing session expiration	Allowed inactivity in seconds for an ongoing, in-progress charging session. When background job detects an in-progress session’s inactivity exceeding this time, it finalizes the session (rating and closing).
Session closed verification time	Amount of seconds since the session stop request, after which session is verified to be closed. Used in scope of force stopping and idle sessions stopping. Limitation: This settings only applies for the Site currently.

Table: Session expiration settings

Pre-configured idle sessions job operation is responsible for detecting idle sessions based on expiration settings of Site and Operator.

Job’s execution interval determines how often the central system checks for the idle sessions.

Notes:

Consider setting the ready-session-expiration time setting of site/operator to the proper amount, regarding your chargers. For some AC chargers, time to start charging may be 5 seconds, meanwhile for DC it can take up to 20-40 seconds. Please consider it and adjust ready-session-expiration in your settings of the site/operator.

Consider these effects in scope of ready-session-expiration:

Session requested to start by mobile application (operated by central system), charger is not responding with acceptance. Session will be closed after ready-session-expiration time.
Session requested to start by mobile application (operated by central system), charger accepting the request. Central system is waiting for the session’s start event. If not started, session will be closed after ready-session-expiration time.
Session requested to start by mobile application (operated by central system), charger responds with rejection, session is closed immediately.
Session requested to start by mobile application (operated by central system), charger accepting the request. Central system is waiting for the session’s start event. Charger responds with a start event before the ready-session-expiration time and session proceeds for charging.

Consider these effects in scope of ongoing-session-expiration:

Session is in progress and charging. Charger stops sending the session update reports and once inactivity time breaches ongoing-session-expiration time setting, session is detected as idle by the central system. System thus requests the charger to stop the session and closes/completes it, which means not tracking it anymore.

Session Reactivation

When the charger sends the charging session event (start/update) with an authorization token (id tag) to the Tridens EV Charge central system, and the system does not find any prepared session (status: READY) or active session for that authorization token on that specific charger, the following process takes place:

The Tridens EV Charge system checks whether a completed session (status: e.g., CLOSED) exists with the same authorization token-type combination and assigned customer.
If such a completed session is found within the configured grace time, it is reactivated.
Authorization of customer resources is made based on the Session Rating Settings.

Note:

Default grace time period for session reactivation is 900 seconds from the session’s creation. Default can be overridden by a value defined in Session Rating Settings.
Once session is reactivated, its status changes to IN_PROGRESS.
If reactivation fails due to unsuccessful resource authorization, the session is requested for termination.
If existing session is found, it gets reactivated only if stop session events haven’t yet arrived from the charger for such session. If stop events have already arrived, reactivation won’t happen.

View Logs

Logs of Open Charge Point Protocol (OCPP) communication exchanged between the central system of Tridens EV Charge and the charging station for the time of the specific charging session. Operators usually utilize them at onboard testing and for troubleshooting.

To view session’s OCPP logs, navigate to the sessions view, find the session of interest, move to the Actions column and hit the View Logs button. See Figure 1. Logs are filterable by the time range and can be exported by CSV or Print options which appear on the bottom of the tool. See Figure 2.

Figure 1: Sessions view and the navigation to view OCPP communication logs.

Figure 2: OCPP communication logs of the session.

Limitations

Session initiation limitations:

a) If requesting to start the session on connector A with customer A, session is prepared and charger is requested to start charging. If customer A tries to start the another session on connector A or any other connector, the request is rejected, as this customer already has an active session. There is a limitation of one active session per customer.

b) If requesting to start the session on connector A with customer A, session is prepared and charger is requested to start charging. If customer B tries to start the session on connector A, the request is rejected, as connector already has another active session assigned.

c) If customer A and customer B both want to start the session on connector A at the same time, the request that came in first will be proceed (access lock), meanwhile the other request will be rejected.

Docs: Push Notifications Setup

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

Push Notifications Provider Configuration
Notification Template
Notification Rules Configuration

Set up push notifications for Tridens EV Charge using a third-party solution. Once configuration is established and the configured notification action happens, push notification is expected on the targeting driver/customer device.

Push Notifications Provider Configuration

First of all, configuring the push notifications provider is required. Currently, Firebase is available. See System Configuration - Firebase Configuration.

Notification Template

In the next step, we need to determine the push notification template(s). To achieve this, go to Business Configuration → Templates → Push Notification Templates. There you can manage the message templates. Name the template, assign code as alphanumeric identifier, apply description if necessary and most importantly, enter the formatted content.

See Business Configuration - Templates - Push Notification Templates for more details.

Notification Rules Configuration

Then proceed to the notification rules configuration. Go to System Configuration → Notifications → Notifications and edit your existing configurations. In the Publishers section, add and select new Push action. No need to specify any specific ‘Receivers’, as such notifications are headed to the action’s belonging customer device directly. See Fig. 1 below.

Figure 1: Notification rule configuration with push publisher.

Docs: Reservations

Mon, 01 Jan 0001 00:00:00 +0000

To access this section in EV Charge, from the Menu, click Reservations. A paginated list of all reservations from a specific period is shown in a tabular format.

To generate the reservations list in a spreadsheet, click CSV. To print, click Print, and to copy, click Copy.

Note:

They are generated, printed, and copied per paginated page.

Information:

You can filter for reservations by date-time, customer ID, service, or/and status.

Typically, a charger usually has a single connector. Therefore, reserving a connector also means the charger is automatically reserved. However, some chargers can have multiple connectors.

If a charger has multiple connectors that cannot be used simultaneously, the entire charger will be reserved if a customer reserves a connector from the charger.

In contrast, if a charger has multiple connectors that can be used simultaneously, then if a customer reserves a connector from the charger, the entire charger will not be reserved because a different connector can be reserved and used by another customer.

A connector reserved by a customer in the EV Charge - Mobile App will lock the connector for a short period. This implies that other users will not be able to use the connector; it is shown as a reserved/unavailable connector for the rest of your users.

Information:

To reserve a connector in the EV Charge - Mobile App, see Reserving a connector.

The primary purpose of a customer reserving a connector is to ensure that even though the customer is not present currently at the charging station location, the connector can remain vacant for some time as they travel to the charging station.

Information:

You can stop an active reservation under Actions.

Note:

Clicking the customer ID on a reservation will take you to Monetization, where the customer information resides.

Docs: Configuration Templates

Mon, 01 Jan 0001 00:00:00 +0000

Overview

Configuration Template defines the set of configuration variables applied to the charging station once it establishes the connection with Tridens EV Charge.

The Configuration Template consists of the following attributes:

Identification (Id, Code): Identification values that uniquely represent the configuration template.
Naming (Name, Description): Descriptive details providing the template name and additional information.
Validity & priority (Valid from, Valid to, Priority): Time range during which the template is considered active. All overlapping templates are applied, but those with a higher priority value are applied first.
Communication protocol: Protocol of communication between the charging station and Tridens EV Charge. When populated, the configuration template applies only to stations that use the specified protocol.
Settings: List of configuration settings applied to the physical charging station once it establishes the connection with Tridens server. If charger/connector relations are specified within settings, such settings will have a charger/connector-based limitation.
Set Configuration Batch Size: Distributes settings into batches of given size, while settings are being instructed to the physical station.
Operator: Optional site operator for which the configuration template applies. When an operator is defined, the template applies within that limited operator’s context. Otherwise, it applies to the general site environment context.

Configuration Setup

Create, View, Update, Delete

Under the Configuration Template section, the following management possibilities are available:

New Configuration Template can be created by pressing Create new button and providing the settings, as defined in overview.
View existing Configuration Templates by using a filterable table view. Apply search criteria if necessary.
Detailed view of existing Configuration Template can be accesed from the table view and pressing Details.
Existing Configuration Template can be modified by pressing Update on the detailed view.
Existing Configuration Template can be deleted by pressing Delete on the detailed view.

Assigning to Charging Infrastructure

Charging infrastructure operator can assign the Configuration Template to the infrastructure by linking the template to specific Areas or Stations.

Unassign from Charging Infrastructure

Charging infrastructure operator can unassign the Configuration Template from the charging infrastructure when the template is no longer needed.

Operation

Once a charging station establishes connection with Tridens EV Charge, the system checks for configured templates on that specific Station or its parent Area. Tridens EV Charge system then automatically applies all valid template settings in batches of the defined size.

If multiple templates exist, they are ordered by priority.

When changes are made to templates, or when templates are assigned/unassigned, the physical charging station’s configuration is updated the next time it reconnects with Tridens EV Charge system.

Docs: SMS Notifications Setup

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

SMS Provider Configuration
SMS Template
Notification Rules Configuration

Set up SMS notifications for the actions on Tridens EV Charge. Once configuration is established and the configured notification action happens, SMS notification is expected on the targeting receiver.

SMS Provider Configuration

First of all, configuring the SMS notifications provider is required. Currently, Twilio provider is available.

Once you register on Twilio, you can manage your provider configuration in Tridens EV Charge’s dashboard by navigating to System Configuration → Platforms and select Twilio.

Once the form shows up, insert the phone number (E.164 format), client id and client secret, which was provided to you by Twilio following the registration.

SMS Template

In the next step, we need to determine the SMS template(s). To achieve this, go to Business Configuration → Templates → SMS Templates.

There you can manage the message templates. Name the template, assign code as alphanumeric identifier and apply description, if helpful. Then define the dynamically formattable content, which represents an actual content of the SMS notification message.

See Business Configuration - Templates - SMS Templates for more details.

Figure 1: SMS template creation

Notification Rules Configuration

In the Receivers sub-section of a Publisher, add the necessary receivers, as desired:

Base: Enter the specific phone number to which the SMS notification should be sent for the action.
Customer: SMS notification targets to the destination of customer’s primary contact info phone number, if action is related to the specific customer. Applies for the session related actions, as these are related to the customer. Additionally, as a value, Customer Type group can be selected, meaning that SMS notification will apply only if the customer belongs to the specific customer group.

Figure 2: Notification rule configuration with the SMS publisher

Docs: Email Notifications Setup

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

Email Server (SMTP) Configuration
Email Template
Notification Rules Configuration

Set up email notifications for the actions on Tridens EV Charge. Once configuration is established and the configured notification action happens, email notification is expected on the targeting receiver.

Email Server (SMTP) Configuration

First step to enable email notifications is to equip yourself with an email server, usually by utilizing the email server hosting provider.

Once Simple Mail Transfer Protocol (SMTP) email server is established, enter the SMTP settings into environment of Tridens EV Charge - these settings are manageable in the Site settings section. At the point when SMTP host server is configured on environment with username, password, host and port, proceed to configuring the notification template.

Email Template

In the next step, we need to determine the email template(s). To achieve this, go to Business Configuration → Templates → Email Templates.

There you can manage the message templates. Name the template, assign code as alphanumeric identifier and apply description, if helpful. Determine the subject which will appear on the emails. From, to, carbon-copy, blind-carbon-copy and reply-to are optional - note that from (source) can be auto-assigned based on your email server and to (destination) also gets populated by the notification rule’s receivers, as defined in System Configuration - Notifications.

The most important part comes at the bottom, where dynamically formattable content can be defined by using the content builder.

See Business Configuration - Templates - Email Templates for more details.

Figure 1: Email template creation.

Notification Rules Configuration

In the Receivers sub-section of a Publisher, add the necessary receivers, as desired:

Base: Enter the specific email address to which the notification should be sent.
Customer: Notification targets to the destination of customer’s primary contact info email, if action is related to the specific customer. Applies for the session related actions, as these are related to the customer. Additionally, as a value, Customer Type group can be selected, meaning that notification will apply only if the customer belongs to the specific customer group.

Figure 2: Notification rule configuration with the email publisher.

Docs: Operators

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

Operator explained
Create an operator
Details operator page
Update operator
Delete operator
Operator with Members in Private Network
Operator Commission Report Setup

To access this section in EV Charge, from the Menu, click Operators. A paginated list of all operators is shown in a tabular format.

Operator explained

Creating an operator in EV Charge is optional. However, it comes in handy if you have a revenue share agreement with the operator or something related.

Information:

The reporting section in EV Charge enables you to filter for the total consumption obtained from an operator’s charger and the total revenue (money) generated from an operator’s charger. For more information, see Reports.

An operator is intended to represent a company, like a hotel, a restaurant, etc., where they have chargers. Typically, they are the owner of the chargers; however, you are the manager of those chargers.

You can create entities for the operators and link them to user accounts for them to receive login details to EV Charge. However, they will only be able to view the sections that pertain to them—for example, the stations they own. In addition, they can see their chargers’ session history.

Note:

An operator can be linked to multiple charging areas; for example, if you work with a restaurant, all restaurant chains will be managed by the same operator because they are the same business entity.

However, it can also be a one-to-one relationship: one operator to one charging area.

Four actions/subpages can be performed/viewed under this section, namely:

Create an operator
Details operator page
Update operator
Delete operator

Create an operator

Under operators, to create an operator, click Create new. It has three sections, namely:

Operator
Environment setup
Summary

Operator

Under this section, provide a name and code.

Note:

The code is a unique identifier of an object. It can be used during integration with the EV Charge API.

Additionally, provide the operator’s details. The details are only used for information purposes and can be used to reach out to the operator.

The operator’s details consist of the following:

Organization Name
Address
Phone number
Country
State
City
Zip code

Environment setup

The Timezone is configured to give the operator a standard timezone regardless of which part of the world they are connecting. Therefore, if an operator logs in to EV Charge, all the date-time on the interface will follow the timezone assigned in this section.

Session Rating Settings

Session Rating Settings provides settings about the charging behavior, usage patterns, and performance metrics associated with the charging sessions.

Idle Session Settings

Idle Session Settings are allowed session’s inactivity time after which the session is stopped being tracked.

Summary

This section shows the information inputted in the previous two sections: it can be reviewed before creating the operator.

Once the operator is created, it can be assigned to a charging area.

Note:

An operator does not automatically receive login details to EV Charge. They receive login details when you purposely create a user for the operator. For more information, see Users.

Details operator page

Under operators, to see the full details of an operator, click Details. It contains the following information:

Name
Code
Status
Organization
Country
State
City
Zip
Address
Phone
Timezone
Energy step delta
Security key
Monetary session limit

Update operator

Under operators, to update an operator, first, click Details; it shows the details of the operator. Then to update, click Update.

Note:

All information filled out under the create an operator section can be updated except for the Code.

Delete operator

Under operators, to delete an operator, click Delete.

Note:

Deleting an operator already used in other parts of EV Charge cannot be done. Every particular reference to the operator first has to be deleted.

Operator with Members in Private Network

Charging station’s visibility can be managed by toggling its visibility attribute.

When station is marked as visible, it will be generally visible on the map to all the drivers/customers. Otherwise, when marked as invisible, it will be hidden from the map, except for drivers which are station operator’s private group members.

When station is assigned to the operator, operator has control to grant/revoke drivers an access to its generally invisible stations.

Requirements to achieve this:

Create an Operator.
Area has Operator assigned.

To manage members, navigate to the top right corner on the operator’s view page and selecting “Add/remove members” button.

Figure 1: Create Operator with Private Network.

Once the form shows up, operator can see and manage the active customers of his private charging network (group).

Figure 2: Manage customers of Operator’s private network.

Operator can search for the existing customers and grant them access to his private network (Figure 3), or alternatively revoke an access (Figure 4).

Figure 3: Operator can search for the customers he would like to grant access to his network.

Figure 4: Operator can revoke customer’s access to his private network.

Operator Commission Report Setup

Under Operators, to set up operators’ commissions, click Details, then Update and proceed to the second step on Environment Setup and click Share/reimbursement settings.

Once the fields show up, fill the prices and the percentage revenue share.

Figure 5: Share / Reimbursement settings.

Docs: Site

Mon, 01 Jan 0001 00:00:00 +0000

Topics in this document:

Site Settings
Session Rating Settings
Idle Session Settings

To access this section in EV Charge, from the Menu, click Settings.

Site Settings

Represents the Tridens EV Charge environment’s general settings of location, contact, language, currency, time zone, organization, logo, SMTP, session expiration and session rating.

Under Settings there is Session settings where site session configurations can be set up.

Figure 1: Site Settings

Figure 2: Site Session Settings

Session Rating Settings

Session Rating Settings provides settings about the charging behavior, usage patterns, and performance metrics associated with the charging sessions.

Idle Session Settings

Idle Session Settings are allowed session’s inactivity time after which the session is stopped being tracked.

EV Charge Web Docs | Tridens Technology –

Docs: Chargers

Note:

Information:

Note:

Tip:

Docs: Charging Session Integration

Session Start Timeout

Example:

Note:

Driver Authorization

Offline Sessions

Meter Values Reporting

Note:

Note:

Session Related Meter Values

Session Meter Values Interval

Session Meter Values Measurands

General Meter Values

General Meter Values Interval

General Meter Values Measurands

Energy Reading Type Detection

Energy Report Validation

Note:

Session Event Retry

Docs: Consumption

Information:

Information:

Docs: Consumption

Note:

Information:

Tip:

Docs: Notifications

Notifications

Create notification

Note:

Information:

Note:

Example of a notification

Information:

Details notification page

Update notification

Information:

Delete notification

Notification scopes and actions

Platforms

Note:

Note:

Firebase configuration

Requirements and process outline

Information:

Firebase configuration for EV Charge

Create a new project on Firebase

Configure Firebase credentials in EV Charge

Note:

Create a Firebase mobile app configuration - iOS

Create a Firebase mobile app configuration - Android

Docs: Roaming Profile

Roaming Profile

Docs: Stations

Note:

Information:

Reboot

Firmware upgrade

Information:

Diagnostic logs

Tip:

Trigger message

Docs: Templates

Mail templates

Information:

Create a mail template

Note:

Information:

Note:

Details mail template page

Update mail template

Information:

Delete mail template

Note: