In be.ENERGISED and also in the articles in the Support Center, certain terms are often used that are not necessarily self-explanatory and known to everyone. In the following glossary, you will find a definition for these terms.
Term | Definition |
mandant (no longer in use) | "mandant" refers to you as a customer and user of be.ENERGISED. The new term for this is "client". |
instance | Denotes your customer access to be.ENERGISED. Ex: "Log in to your instance (also customer instance)." |
subscription |
A "subscription" is your authorization to use be.ENERGISED. There are different subscription models, which differ in price and in terms of the functions that can be used. Examples of different subscriptions are: "Monitoring" subscription, "Essentials" subscription, "Business" subscription, etc. More details here. |
client |
"client" means you as a customer and user of be.ENERGISED. |
COMMUNITY |
COMMUNITY is a free software feature that you can activate for your charging stations in the backend of be.ENERGISED. You simply define the desired tariff at which third-party customers can charge at your charging station. has·to·be takes care of the marketing via the COMMUNITY network. |
operator |
"operator" also refers to a company within your company structure. You will find the term "operator" in the price configurations in the tariff management. |
invoice run |
The invoice run is another name for the automated invoicing function. |
OCPP |
OCPP is a unified communication protocol that enables communication between charging stations and a central management system. |
energy & output |
Energy is calculated in kWh. Output is calculated in kW. |
Connector or charging point |
These are all terms that denote the charging point of a charging station. |
entity |
"Entity" refers to an entity in your corporate structure. A parent entity is a company in your corporate structure that has other companies (entities) under it. Conversely, a subordinate entity is one that is subordinate to another entity. |
backend |
"backend" refers to the be.ENERGISED software. In general, "backend" is a term that covers data processing and data storage in the background of software, apps or websites. |
tag ID |
The tag ID is an identification number for an identification medium (RFID card). The tag ID of the identification medium must be entered as a HEX code, since the OCPP specification requires this. |
(charging) station interface |
When you connect locally to your charging station, you can access the charging station interface, which allows you to make various settings on your charging station. |
authorization/ authorization amount |
At the beginning of a charging process via the Direct Payment Page, an amount up to 100.00 EUR (or an equivalent in another currency) is authorized (reserved, not debited!). This is also called authorization amount. |
OCPP broker |
A so-called broker is a "connection bundler". It bundles charging station data (which communicate with the broker via the OCPP protocol) and passes the relevant data to the be.ENERGISED backend. As the direct connection via websocket is technically limited, we need the broker, as the connection via it is almost unlimited. Compared to the old direct connection, we have the advantage of the broker that the data is more scalable, and we therefore have better performance. |
credit note run |
The "credit note run" refers to the creation and sending of credit memos via the be.ENERGISED COMMUNITY or within your corporate structure via the "CPO crediting process" function. |
blocking fee |
The blocking fee is a fee that charging station operators charge when e-cars stand too long at a charging station, thus blocking it for others. In most cases, this fee is due after a certain period of time, which is determined by the charging station operator. |
Version: 2023-02-21 07:58:10 UTC