Skip to main content
GullySystem
Automotive · Software for eV charging operators

Chargers, sessions and fault tickets by connector.

Connectors earn only while they work. Software holds each site, charger and connector, records sessions against the tariff, and sends faults to the technician who can fix them. Host agreements and energy bills follow each site, so the monthly settlement for every landlord becomes a report that finance reads instead of a spreadsheet that finance rebuilds.

At a glance

A charging operator runs power stations in other people’s car parks, with a landlord, a grid connection and CCS2 or Type 2 connectors that fail in different ways. Every one needs a record.

Operator software gives each connector its own record, and sessions, faults, meter readings and host payments tie back to it, including the firmware version running on the day. A faulted connector is the easiest place to begin.

How the work runs today

The desk watches for offline, faulted and stuck connectors. A driver rings about a charging cable that will not release, and the agent opens the session, notes the connector and raises a ticket for the stuck latch. Field technicians carry a route of sites, with spare cables, contactors, fuses, RFID readers and screens in the van, each van holding a counted stock. Before leaving a bay, the technician records which part came off, which part went on and which firmware version the charger runs. Whoever returns reads that history first.

Commercial staff keep host agreements: a revenue share with a mall, a fixed rent with a hotel, a free bay arrangement with a fleet depot. Month end brings the energy bill per site, the sessions delivered, the refunds issued and the amounts due to each host under its own share, rent or minimum. Fleet customers ask for a statement per vehicle card.

Where it breaks

What goes wrong for eV charging operators without a proper system.

Faults are known but not owned

A connector shows faulted on the charge point backend, but nobody knows whether a technician has been told or which spare contactor sits in which van. The red icon stays red.

Sessions and payments are read from separate reports

The charge point backend lists kilowatt-hours per session while the payment provider lists money per card, and matching the two to approve one refund takes a spreadsheet. Drivers wait for their refunds.

Landlord payouts are a monthly spreadsheet chore

Every landlord has a different share, rent or minimum, and the payout rests on the site meter reading, the sessions delivered and the tariff in force that month. One wrong cell upsets a host.

Energy bills do not line up with sessions

The utility bill is per site meter while sessions are per connector, so the gap from idle draw, cable losses and cooling fans is never explained. Margins stay a guess.

Fleet statements are rebuilt every month

A delivery company wants sessions per vehicle card and cost centre, and the data exists, but it appears only after an export, a sort and a pivot table. Someone rebuilds it every month.

What the software does

What we would build for eV charging operators.

Named the way your team already talks about the work. We start with whichever part the audit shows is costing you most.

Sites, chargers and connectors

Hold each site with its host, grid supply and bays, each charger with serial number and firmware, each connector with plug type and rated power.

Sessions and tariffs

Record every session with start, stop, energy delivered and the tariff applied, while idle fees, free minutes and peak rates follow the rate card of each site.

Fault tickets and field visits

Raise a ticket from a driver call or a backend alarm, assign the nearest technician, and close it with the part used and firmware left.

Host agreements and settlement

Keep each site agreement with its share, rent or minimum, and work out the amount due to the host from sessions and meter readings.

Fleet accounts and driver cards

Issue RFID cards or app accounts to fleet customers and produce a statement per vehicle and cost centre, with sessions listed by connector.

Spares, energy bills and refunds

Track cables, fuses and screens by van and store, load the utility bill per site meter, and record refunds against the session they came from.

Before you talk to a supplier

A requirements checklist for eV charging operators.

What to cover, which reports to ask for and what to put to every vendor, ready to print or save as a PDF.

Open the checklist
Ready product

A product already built for eV charging operators.

It is adapted to how your business works before it goes live, and anything your trade needs that it lacks is added then.

EV Charging Operator Management Software

Sites, connectors, sessions, tariffs, fault tickets, technician visits, host settlements and fleet statements for operators of public and private EV chargers.

See the product
How it works

How the work runs from Bengaluru for your city.

  1. 1

    The audit, by call

    A screen-share and a look at the sheets, accounting reports and WhatsApp groups your team uses. No travel needed.

  2. 2

    A written proposal

    Scope, what we build first and the cost, agreed in writing before anything starts.

  3. 3

    Build in short rounds

    Working screens shared every few weeks. Your team tests them from your own office.

  4. 4

    Go-live, in person when it helps

    For data migration and training we can come to your city. Travel is agreed in advance.

  5. 5

    Support online

    Fixes, changes and hosting handled remotely by the same team that built it.

Common questions

Questions eV charging operators ask before they call.

Does it talk to our charge point backend?

It can read session and status files or an interface your backend offers, and the feed is agreed once your backend vendor shares its format during implementation.

Can a landlord see their own sessions?

Yes. A host login shows only the sites in that agreement, with sessions, energy delivered, the tariff in force and the settlement statement for the month.

What does it cost?

The quotation depends on how many sites, chargers and connectors you operate, which backend feeds and payment reports are connected, and how many host agreements need settling. You see a sample site on screen first. The quotation then arrives in writing.

Can we take our charger records out later?

Yes. Exports run by site and cover chargers, connectors, sessions and tickets, with the column list and file format agreed and written into the quotation before work begins.

What moves the charging network system quotation?

Choosing sessions and tariffs first, or fault tickets, or host settlement, changes the base most. Add up sites and chargers, then the users. Charger protocols to connect can change the total. A quotation can price sessions and tariffs on their own.

Gathering for the charging network system: what first?

Bring site lists, tariff sheets, fault history and host agreements. Contacts from operations, field service and finance are needed. Samples of tariff sheets help most.

Who owns the charger lists after we stop?

The operator keeps the source code, charger lists, session tariffs and host settlements. Plain-file exports cover charger lists, session tariffs and host settlements. Charger lists support stays in-house.

What happens after I share my requirements?

An engineer reads what you send and replies within one business day. We then look at the software, spreadsheets and WhatsApp groups your business runs on today and write down what works, what slows your team down and what is missing. A demo login, a screen-share or a few screenshots are enough. You get a short written summary ordered by priority, with no obligation to hire us afterwards.

How much will the software cost?

We don’t publish a price, because it depends on what the system has to do. That first review settles the scope, and the cost goes into a written proposal before any work starts.

Category

Part of a wider group.

Talk to us

Tell us how your business runs today.

A few lines on your spreadsheets, software and WhatsApp groups is enough. We reply the same working day.

What happens after you share your requirements

  1. A senior engineer reads your answers. Nobody phones first.
  2. Within one business day you get a written note: what we understood, what we would start with, and the questions we still have.
  3. If it fits, a proposal follows with the order of work, what we need from you and what you receive at each step.
  4. No call is booked and nothing is paid until you have read the note. Your details stay with us.

Start with your requirements

Seven short steps that tell us what you need. A senior engineer reads them before anyone gets in touch.

Share your requirements