Cookie preferences
Essential cookies keep this site working. With your permission, we use cookies to recognise you when you return and to remember your activity history. External content such as Google services may also be loaded. You can withdraw your consent at any time.
Project
Electric Vehicle Charging Network Operations Platform
A charging network operations platform that brings the admin panel, the driver app and charger communication together in one hub, is OCPP-compliant and runs EPDK and GİB processes automatically.
Evion EV Charge is an end-to-end platform built to operate electric vehicle charging stations from a single hub. The chargers in the field, the admin panel used by the operations team and the app on drivers' phones all connect to the same central server; charger status, pricing, customer records, payment collection and official notifications are gathered in one place.
The platform consists of three components:
When a charge ends, payment collection, the notification to EPDK (Turkey's Energy Market Regulatory Authority) and the invoice request run on their own; the team does no separate data entry. Thanks to the multi-tenant architecture, a second brand or a completely separate network can be opened on the same installation; partner operators such as shopping malls, hotels or public institutions see their own locations, and the revenue share is written to the record at the start of every charge.
As electric vehicles became widespread, running a charging network stopped being an investment matter and became an operations matter: hundreds of chargers, thousands of drivers, thousands of charges every day, and for every charge a payment collection, an EPDK notification and an invoice.
The request we received came at exactly this point. An operator building a charging network wanted to manage a fleet of chargers from different brands from a single screen, without being bound to the charger manufacturers' own management software; to offer drivers an app under its own brand; and to carry out all of its regulatory obligations — EPDK notifications, GİB (Turkish Revenue Administration) charging unit registration, transfer to accounting — without any human intervention.
We started the project from the realities of the field. Chargers lose their connection, a driver's phone shuts off, a QR code can't be read, a bank verification is left unfinished. We designed the platform around these exceptions: on a charger that loses its connection, an open charge does not stay open indefinitely; it is closed at the last meter value and billed. When a driver's phone is not working, the call center starts a charge on the customer's behalf. The price is frozen at the moment the charge starts; even if the tariff changes later, an ongoing charge is not affected.
The result was a system that works in the field and whose workload does not grow in step with scale: when the number of chargers and customers increases, the work of price definition, registration, payment collection and notification does not increase at the same rate; these tasks are handled centrally and automatically.
Tell us what you need; we'll set out the scope, integrations and roadmap in writing in the first meetings. Built around the way you work, without touching your ERP, accounting or banking systems.
The main screens and their highlights: on every image we magnify the area that matters most. Tap an image for details.
The operations team starts its shift with this screen: all stations on the map, the number of connected and disconnected chargers, the connector occupancy breakdown, the total power being drawn at that moment and the day's revenue are visible at a glance. Chargers that report a fault or send no signal stand out in a separate list; the latest charging activity also streams down the same page.
When a charger is selected on the full-screen map, a side panel opens: connection status, last signal, connectors, meter and current power. From here the team sends commands for restart, unlock, connector disable, diagnostics file, power limit, and reading and writing settings; it follows the charger's response in the communication logs below.
Every charger in the field sits in a single list with its brand, model, current type, power, OCPP version, number of connectors, connection, revenue share and maintenance status. The team imports new chargers in bulk with an Excel template and exports the list; tabs for location, charging card, connector status and EPDK and EŞÜ bulk updates are on the same screen.
This page shows the record of a single charge in full: a summary of duration, energy, amount and current power, session details, and the breakdown of the tariff, promotion and revenue share frozen at the start of the charge. The timeline below lists every step, from scanning the QR code to the invoice request, with its time; the support team also processes refunds and additional charges from here.
The operations team defines tariffs by price per kilowatt-hour, current type, effective date and priority, and makes one of them the default. Promotions apply a percentage discount to all drivers or to selected customer groups. The final price calculator shows the base price, the discount and the final price for the selected station and customer before the tariff changes.
Live counters at the top of the screen summarize EPDK notifications, GİB charging unit records and ERP invoice transfers. Below, each notification's time, station, content, the response returned by the authority and its retry status are visible line by line. At period end, a single check tells whether any unsent or untransferred record remains.
On this screen the operations team defines partner operators (CPOs) such as shopping malls, hotels or public institutions, with their locations, stations and revenue share. A second brand or a separate network on the same installation works as an independent tenant with its own data. The matrix below shows which actions the call center, field team, accounting and partner operator roles can perform.
When the call center finds a driver by phone number or license plate, this screen comes up: wallet balance and transactions, charging cards, vehicles, invoice and payment details, charging history and group memberships. Starting a charge or sending a notification on behalf of a driver whose phone is off also begins from this screen.
The driver signs in to the app with a phone number and a one-time password sent by SMS; there is no need to set a password, and if they wish they can browse the map as a guest. Markers on the map cluster together; DC, AC and free-connector filters bring suitable stations to the front, and the selected station's distance, travel time and price are shown; directions are handed off to the phone's map app.
The station page shows photos, the driver rating, the distance and opening hours; each connector's power, type, price per kilowatt-hour and current status sit on a separate row. The driver plugs in the cable and scans the QR code on the connector with the camera; if the code can't be read, they type in the connector's short code by hand. Once the center has run its checks, charging starts.
While charging, the driver follows battery level, elapsed time, energy delivered, amount and current power live; they receive a notification when the chosen charge level is reached and can stop the charge from the app. The wallet screen brings together the balance, preset top-up amounts, 3D Secure verification with a saved card and all transactions.
The driver reserves a connector for a later time by choosing the date, time and vehicle; if there is no conflict the reservation is created, and a reminder arrives 15 minutes before the start. Upcoming reservations are listed with their status. In settings, charging, reservation, promotion, announcement and additional-charge notifications can be turned on and off individually; theme, language, FAQ and contact are also there.
Instant notifications and alerts, quick actions and live data: users and field teams get their work done from their phones, without waiting.
Any charger that speaks OCPP 1.6 or 2.0.1 can be connected; the only verifiable question at procurement becomes “does the charger support OCPP?”. The network can be renewed in stages.
The tariff, discount and revenue share are written to the record at the moment the charge starts; later changes do not affect an ongoing charge.
On a charger that loses its connection, the charge is closed at the last meter value and billed; an inconsistent meter value is not passed on to the customer as a wrong amount.
Because deducting from the balance does not depend on an external system, it completes under all conditions; the outstanding amount is limited to at most one charge's fee. The card number is not stored on the platform.
Phone, charging card or call center; the same rule, the same record and the same audit trail for all three.
Restart, cable unlock, connector disable, power limit, software update and diagnostics file request; bulk actions at the same location. Site visits are left only for physical problems.
Chargers that report a fault or send no signal are collected in a separate list; the map color changes instantly.
The EPDK notification, the GİB charging unit registration and the invoice request are triggered by the charging event; with a queue, retries and duplicate prevention, no record is left missing at period close.
A shopping mall, hotel, fuel station or public institution is defined as an operator; locations are linked, the revenue share is written to the record at the start of the charge, and periodic settlement is taken from the report.
A new tenant works like an independent installation with its own stations, tariffs and users; no redevelopment is needed for a second brand or a separate network.
Roles are built from individually selected permissions; phone, ID, tax and card fields are shown masked to users without permission.
A connector is reserved for a specific driver for a later time; a reminder 15 minutes before, and automatic release when the time expires.
Announcements, promotions, FAQ and fixed fields go live the moment they are saved; no new version of the app is needed.
Promotions, announcements and notifications through customer groups; corporate discounts are attached to a group without changing the tariff.
Free charges, commands, refunds, wallet corrections and tariff changes are recorded per user; used for disputes and internal control.
Keep scrolling
Move between slides with the arrow keys or by swiping.
How we work
This project was run on the same four principles; yours will be too.
Scope, integrations and roadmap are written down and agreed in the first weeks; no surprises along the way.
ERP, accounting, banking, e-invoicing: whatever you run, we integrate on top of it and your data stays where it is.
Role-based access, two-factor authentication, data-protection compliance and a log of every action are built into the foundation, not bolted on later.
Maintenance, monitoring and new releases come from the team that built the project; someone who knows your system is always a call away.
Evion EV Charge
The home page gives the overall state of the network on a single screen at the start of a shift: which charger is connected, which connector is occupied, how much power is being drawn, which charger is waiting for intervention. The team starts the day knowing its priorities, without waiting for complaints.
The map shows all stations in status colors: available, occupied, faulty and offline. When a marker is selected, the charger's connectors open; an authorized user starts or stops a charge from here. The cards at the top summarize connected chargers, active charges, current power and daily revenue. Chargers report status changes themselves and send a regular connection signal; a charger whose signal drops lands on the attention list automatically.
Fault detection does not depend on customer complaints; a problem charger appears in the list before any complaint arrives, and the map color changes instantly. The shift supervisor starts the day knowing which charger to look at first and plans the site visit early. Statistics and recent transactions refresh themselves at regular intervals; without waiting for a separate report, the team sees the current state of the network on the same screen at any moment.
Live monitoring is the screen for intervening on a single charger without going to the site. The operator sees the charger's connection and connectors, sends the command and confirms the result on the same screen; site visits are left only for physical problems.
Every command given from the panel first goes to the center, which forwards it to the connected charger; the charger's response and the result are recorded. In the side panel, each connector's current power, meter and status are shown separately; from here the operator stops a connector that is charging, starts a charge on an empty connector, and cancels the reservation of a reserved connector. If the charger is not connected, the command options are disabled. The tabs below list recent charges, communication logs and problem chargers.
The team solves the most common problems remotely: it restarts the charger, unlocks the cable lock and disables a faulty connector; on a charger with two connectors, the other connector keeps serving. When the site's electrical infrastructure is under strain, it sets a power limit, and it applies bulk actions to chargers at the same location. For a problem that cannot be solved remotely, the team heads to the site already knowing the nature of the problem; the diagnostics file helps in discussions with the manufacturer's service.
Field inventory brings a charger fleet made up of different brands and protocol versions into a single record structure. Where each charger stands, which OCPP version it speaks, whether it is connected and whether it is under maintenance can all be read from a single list.
The charger record contains brand, model, current type, power, serial number, EPDK numbers, installation number, revenue share, maintenance status, photos and connectors. The location tab holds the address, province, district and the coordinates picked on the map; when a location is linked to a partner operator, all chargers at the address fall within its scope. The connector status tab shows each connector's current status, last meter reading, short code and QR code in a single list.
Choosing a charger does not tie you to the manufacturer's management software; the only verifiable question at procurement is whether the charger supports OCPP 1.6 or 2.0.1. Chargers of different brands and versions appear on the same map, in the same tariff structure and in the same transaction list; the network is renewed in stages. No new charge is opened on a charger put under maintenance, and it cannot be started from the mobile app either; when maintenance ends, the flag is removed.
The transaction record shows line by line how the amount of a charge came about. The support team answers a customer's question about the amount with this breakdown; a refund for a wrongly collected amount and an additional charge for an under-collection are processed from the same page, on the record.
At the moment a charge starts, the tariff, the discount and, if there is one, the partner operator's share are written to that charge's record; even if the tariff changes later, this charge's amount does not change. The amount is found by multiplying the energy between the end and start meter readings by the frozen tariff and subtracting the discount. Session details include the party that started and stopped the charge, the driver identity, reservation, vehicle, invoice recipient, EPDK notification and the status of the invoice request.
The support team does not leave the amount to guesswork: the breakdown shows the tariff, the promotion discount, the operator's share and the amount to be collected separately. For a wrong collection a full or partial refund is made; an amount collected too little is added to the charge as an additional charge; both operations update the wallet, send a notification to the driver and are recorded together with the user who performed them. Each of the two operations requires a separate permission.
The tariff and promotion screen manages pricing across the network from one place. Different prices apply at different locations, corporate discounts are attached to a group without changing the tariff, and every change affects only charges that have just started.
A tariff is the selling price per kilowatt-hour; it carries the applicable current type, effective date, priority order and active status, and is assigned to stations. At a station with no specific tariff assigned, the default tariff applies. A promotion is defined by title, description, image, discount percentage, duration and priority, is applied to all drivers or to selected groups, and a notification goes to the target audience the moment it is published.
In a corporate fleet agreement, drivers are added to a group, the discount is linked to that group and takes effect the same day; when the contract ends, the link is removed and past charges are not affected. Because the price is frozen at the start of the charge, a tariff update or the end of a promotion does not change the amount of ongoing charges. The final price calculator shows in advance the outcome of a planned change for a specific station and customer; the team makes its decision after seeing the result.
The regulatory processes screen makes visible the official correspondence behind every charge. The EPDK notification, the GİB registration and the invoice request run on their own with the charging event; the team only follows the outcome and does no separate data entry.
The platform forwards the start and end of a charge and the energy transferred to EPDK (Turkey's Energy Market Regulatory Authority), and passes connector status changes on to it instantly. When a charge ends, an invoice request is created and goes to the ERP with the charge details, the individual or corporate invoice recipient and the payment method. Every request is written to a queue; a request that cannot be delivered is retried, and a second request for the same charge is blocked. Accounting produces the document; the platform carries the request completely and on time.
For the GİB (Turkish Revenue Administration) charging unit registration, new registration, information update, taxpayer status inquiry, charger transfer and registration closure are carried out from the single-charger screen or from the bulk update screen. Because the EPDK notification and the invoice request are triggered by the charging event, the team does no separate data entry. The time, content and response of every exchange sit on the record screens; the same information can also be reached from the details of the charge record. Period close rests on records, not on estimates.
This screen solves the question, in a multi-party charging network, of who sees what and who does what. Partner operators see their own locations, tenants keep their data separate, and every user's menu is made up of the permissions they hold.
A partner operator is defined with its company name, tax and contact details and its revenue-sharing rate; locations are linked to the operator. The operator's panel users see only the chargers at their own locations; seeing the whole network is a separate permission. A new tenant is opened like an independent copy of the system, with its own stations, tariffs, panel users and settings; an authorized administrator switches tenants from the top bar and sees only the data of the tenant they have switched to.
The revenue share is written to the record at the start of every charge; even if the rate changes later, completed charges are not affected, and the periodic settlement runs from the revenue-sharing report. Roles are not ready-made templates but are built from individually selected permissions: viewing chargers, starting a charge, free charging, refunds, additional charges and bulk official operations are separate permissions. Phone, ID, tax and card fields are shown masked to those without permission to view them; support work can carry on even with the mask.
The customer detail lets the support team answer questions about a driver from a single screen. Balance, card, vehicle, invoice details and charging history sit side by side; personal data is masked according to permission.
The wallet section shows the current balance and any negative balance; below it each entry is listed with its transaction number and amount: charge fee, top-up, refund. Charging cards appear with their status and expiry date, vehicles with the default vehicle indicated; a lost card is canceled from the panel, and the account and balance are not affected. The invoice area shows the invoice type, the last four digits of the saved card and the last bank verification; the card number is not stored on the platform but with the payment provider.
If the driver's phone is off, the signal is weak or the QR code won't scan, the charge can still start: the call center selects the connector on the map, picks the customer's charging card and opens the charge on their behalf; if authorized, it marks the charge as free. Who started it, who stopped it and the free-of-charge flag are written to the audit log. A refund for a wrong collection and an additional charge for an under-collection are processed on the same screen; manual balance correction is done only in exceptional cases, with a separate permission.
The driver signs in to the app without memorizing a password: a phone number and a one-time code are enough. Then, on the map, they find a suitable station with filters, see the distance and price, and hand the directions off to the maps app.
The driver enters the code sent by SMS within the time limit; if the code doesn't arrive, they request it again or change the number. After the first login, registration is completed in three steps: personal details, invoice details and card details; if the steps are left unfinished, the app resumes where it left off. A guest user browses the map and stations without signing in; they are directed to sign in for favorites, charging and profile.
Because no password is stored, there is no password for the driver to forget. Markers that cluster on the map keep crowded areas readable; favorite, DC, AC and free-connector filters leave only the stations that are useful. A driver who taps a marker sees the station's name, distance, travel time and a summary of free connectors; from a search by name they go straight to the station page.
The station page shows the basic information the driver wants before charging: which connector is free, what its power is, what its price is. With a QR code or a short code, the driver starts the charge from the phone without using the charger's own interface.
Tabs on the page separate connectors, station information, driver reviews and photos; the driver adds the station to favorites under a name of their own choosing. The QR code button at the bottom opens the camera; the screen reminds the driver that the vehicle's cable must be plugged in. When the code is scanned, the center checks for a negative balance, an ongoing charge and whether the connector is free, then sends the start command to the charger.
If the checks are not passed, the charge does not start and the driver sees the reason: with a negative balance, they are asked to top up their balance; if they have an ongoing charge, the app takes them to that charge's screen. The short code makes charging possible whenever the QR code can't be read. A charger under maintenance cannot be started from the app. Because the driver does not use the charger's own interface, the experience is the same on chargers of different brands.
The live charging screen shows the values of the charge in progress, and the wallet shows the balance and transactions. The fee is deducted from the balance at the end; because the card comes into play only for topping up and clearing a negative balance, payment collection does not depend on an external system.
The large gauge on the charging screen shows the battery level and the estimated time remaining; below it, charging time, energy delivered, amount and current power update live. The driver chooses for themselves at what charge level they want to be notified. In the wallet, one of the preset amounts or a free amount is chosen, and with a saved or new card the bank's 3D Secure verification is completed in a secure window inside the app; when approval arrives, the balance goes up.
The wallet-first, charge-second model frees payment collection from depending on the card limit, the bank verification and the connection: the charging fee is deducted from the balance at the end and completes under all conditions. If the balance goes negative, no new charge is opened until the negative amount is cleared, so the outstanding amount stays limited to at most one charge's fee. The card number is not stored on the platform; it is kept by the payment provider. A card transaction left unfinished does not affect any ongoing charge.
Reservation lets the driver set a connector aside for a later time; when the time comes, the connector cannot be opened for charging with another identity. Settings leave it to the driver's choice which notifications will arrive, as well as language and theme.
The driver selects a connector, a date, a time and one of the vehicles in their profile; if there is no conflict, the reservation is created as pending, and a reminder notification arrives 15 minutes before the start. At the reserved time, the connector cannot be opened for charging with another identity; for a charge started with a card, the center also checks the reservation belonging to the card. If the charge starts on time, the record is linked to the charging session; if it doesn't, the hold is lifted and the connector becomes free.
Reservation reduces the uncertainty of searching for a free connector on the road; the automatic lifting of an expired hold also keeps a connector from sitting idle. The operator turns the reservation service on or off at the installation level; if it is off, the reservation sections in the app are not shown. In settings, notification types are managed individually, the language is chosen as Turkish or English, the theme as light or dark, and the preference is stored in the account. Closing the account requires double confirmation.
