Skip to main content
GullySystem
Automotive · EV Charging Operator Management Software

One register of sites, pedestals, connectors, sessions and faults.

One record per connector. It holds the charger serial, firmware build, rated kilowatts, tariff in force, session log and repair history, together with the site and pedestal it sits on. The control desk, technicians and accounts read that record, so a driver’s refund request, a landlord’s rent query and a substation meter bill each trace to one bay. Host agreements and fleet cards sit beside it.

  • Site list, connector register and rate cards entered the way your desk quotes them
  • Host agreements and open tickets brought across
  • Settlement rules and fault types changed by GullySystem staff on request

Charge point operators run sites, pedestals, connectors, tariffs and fault tickets in EV Charging Operator Management Software, which GullySystem builds around your network. Each connector keeps its serial, firmware build and repair log. Host agreements produce a monthly settlement. Fleet cards receive a statement per vehicle. Technicians open their own tickets on a phone.

Where it breaks today

What goes wrong before the software.

A faulted connector has no owner

The backend turns a connector red. A driver rings the helpline from a car park. The only technician with a CCS2 cable is two towns away, and nobody knows who was told, whether a residual current device tripped or which van has a contactor.

Sessions and payments are read separately

The backend lists kilowatt-hours by transaction id. The payment provider lists money by card reference, so a refund for a session cut off at 6 kWh means matching two exports by hand. Finance dreads it.

Host settlements differ per site

One landlord takes a share of revenue, another charges fixed rent for the bays, and a mall wants free charging for its staff. Each month the figure is rebuilt from meter readings, a signed schedule and a pile of emails, and the landlord disputes it.

Utility bills do not match sessions

The utility bill covers one site meter while sessions are counted per connector, and idle draw from cooling fans, screens and standby modules never shows in any report. A site that looks profitable on the dashboard loses money once the substation invoice arrives.

Spares are lost between vans

Cables, contactors, holsters and touchscreens travel from the central store to a van and on to a pedestal, so the technician learns at the open cabinet that it sits elsewhere.

Fleet statements are rebuilt each month

A courier company wants sessions per fleet card and cost centre, with depot, vehicle plate and kilowatt-hours on each line. That data exists only after three exports are sorted and merged by hand, so the statement runs late every single month and the customer’s clerk chases it.

How it runs

How the work flows through it, step by step.

Illustration with sample figures. Your screens are built around your own records.
  1. 1

    Site and charger set-up

    A new site goes in. Each charger gets a serial and firmware build. Every connector is given a plug type such as CCS2, CHAdeMO or Type 2, a rated power, a tariff, and the landlord and grid supply it depends on.

  2. 2

    Tariffs applied

    Sessions arrive from the backend with start, stop and kilowatt-hours delivered. Each gets the tariff in force, any idle fee and any free window, a matched payment, and a flag for the desk when a capture fails.

  3. 3

    Fault and ticket

    An alarm or a call raises a ticket. The desk picks the nearest technician. That person sees the fault code, the pedestal and the last repair on a phone before leaving the depot, and the driver is told someone is coming.

  4. 4

    Field visit

    The technician draws spares from the van. The part is repaired or swapped. The firmware build left on the charger is noted, and the ticket closes with parts used, a meter reading and photographs of the opened pedestal.

  5. 5

    Host settlement and energy bill

    At month end the utility bill is loaded per site meter. For every host the share or the fixed rent is calculated from the signed schedule, the metered sessions at that site and the bays kept free for staff. Statements follow.

  6. 6

    Fleet statements and refunds

    Fleet customers get one statement per card. Approved refunds are posted to the session they belong to, so the next statement shows the credit against the right vehicle plate, depot and cost centre line.

Modules

What is inside.

Every module can be switched on, left out or changed to match how your team already works.

Sites and host agreements

Each site is held with its landlord, supply capacity and bays. The agreement sits beside it, with revenue share, fixed rent, minimum payment, free staff bays and the renewal date that the commercial team must watch.

Charger and connector register

Every charger is listed by serial, model, firmware build and install date. Plug type and rated power appear against every connector, and the repair history of that single unit sits one click behind.

Sessions and tariffs

Sessions are recorded with start, stop, energy delivered and tariff applied. Rate cards are set per site, with idle fees after a grace period, free windows for staff bays and member prices for subscribers.

Fault tickets

Raise a ticket from a call or alarm. Give it a priority, an owner and a fault type such as earth fault, welded contactor or dead screen. It stays open until a technician closes it with the part used.

Field visits and routes

Plan technician routes across sites. Each visit is pushed to a phone, and arrival time, parts fitted and the firmware build left behind are recorded against the connector.

Spares by van and store

Cables, contactors, fuses, holsters and screens are counted in the central store and in each van. Any part that runs short is flagged before the route begins, long before a technician stands at an open cabinet.

Host settlement

Work out what each landlord is owed from the agreement, the session totals and the meter readings, then send a monthly statement. The landlord can query it line by line.

Fleet accounts and statements

Issue RFID cards or app accounts to fleet customers, set credit terms and print one statement per vehicle plate and cost centre, ready for the customer’s own accounts clerk.

Energy bills and refunds

Load the utility bill per site meter and compare it with kilowatt-hours delivered, so idle draw becomes visible to the commercial team. Refunds carry a reason and a session number.

Maintenance contracts

Keep service contracts for hosted and customer-owned chargers, with visit dates, covered parts and renewal reminders that reach the commercial team before a contract lapses.

Solutions inside

The business modules it is built from.

Each one is also available on its own, or inside a system built for you.

  • Contract Management

    Each landlord agreement is held with its share, rent, minimum and renewal date, and the settlement for that site reads those terms when the month closes.

  • Fixed Asset Register

    Every charger is listed by serial, model and install date, with its connectors and the repair history that belongs to that unit alone.

  • Price Lists and Schemes

    Rate cards per site carry idle fees, free windows and member prices, and each session picks the tariff that was in force at its start.

  • Ticket Management

    A driver call or backend alarm opens a numbered ticket against the connector, with a priority, an owner and a fault type chosen from your own list.

  • Technician Scheduling

    Visits are placed on each technician’s route by site, and the phone shows the charger’s last repair before the van arrives at the pedestal.

  • Stock Tracking and Alerts

    Cables, contactors, fuses and screens are counted in the store and every van, and a short part is flagged before the route starts.

  • Invoice Management

    Landlord statements and fleet invoices are raised from session totals and agreement terms, with local tax settings applied per country and per site.

  • Client Portal

    A fleet customer logs in to read sessions by vehicle card, download statements and see the balance without ringing the accounts team at all.

Services

How we would put it in.

Setup, data migration, integrations and anything built on top.

Who uses it

One system, each person sees their part.

For the control desk

Watch connectors by status. A plug that has sat in fault longer than the limit you chose is highlighted on the board, with the assigned technician named beside it.

For field technicians

Open the day’s route on a phone and read each charger’s last repair. Then record parts used, attach photographs of the cabinet and close the ticket before you leave the bay.

For site and commercial managers

Keep host agreements, tariffs and renewal dates. When a landlord asks about last month’s sessions at one pedestal, the answer is a few taps away and needs no export.

For accounts

Match sessions to payments and load utility bills. Landlord settlements and fleet statements are issued from the same figures, and approved refunds are posted against the sessions they belong to.

For the operations head

Read connector availability, repeat faults by charger model, spares short by van and landlord settlements due, all on one screen that covers every site. The weekly review needs no spreadsheet.

Reports

The numbers the owner asks for.

  • Connectors by status with hours since the last session
  • Fault tickets by model, fault type and technician
  • Sessions, energy delivered and revenue by site
  • Host settlement due, with agreement terms applied
  • Utility bill per site meter against energy delivered
  • Fleet statements by vehicle card and cost centre
  • Spares short by van and store
Good fit

Who this is built for.

  • Public charging networks that run chargers in car parks and on highways, with a control desk taking driver calls around the clock
  • Mall, hotel and workplace hosts
  • Fleet depot operators with buses and vans plugged in overnight, where each vehicle plate needs its own line on a monthly statement
  • Charge point installers that keep maintenance contracts for customers
  • Residential community managers who bill residents for bay charging
Honest answer

When it is not the right choice.

  • A host with one or two chargers can simply read the backend.
  • Makers of chargers and power modules will find EV Charger Manufacturer Management Software closer, and vehicle sellers will find EV Dealer Management Software.
Made to fit

Adapted to your business before it goes live.

You are not handed a login and left to it. The product is set up around your records, your people and the tools you already use.

Sites, models and connector types

Rated powers, charger models, plug types and the site list are entered first, in the order of the register your desk keeps now. Staff recognise it on day one.

Tariffs and settlement rules

Rate cards, idle fees and the share or rent for each landlord follow your signed schedules, while currency and tax differ by country and are set per site. Nothing is assumed.

Fault types and priorities

The fault list, ticket priorities and the response targets you promise landlords are entered exactly as your desk uses them today. Changes later are made by GullySystem staff on request.

Backend feed

Sessions and status alarms arrive through the file or interface that your charge point backend offers, and the format is reviewed with its vendor. The OCPP transaction id is used to match each payment to its session.

Records migrated

Your site list, charger serials, open tickets and landlord agreements arrive from the working spreadsheets before the first live session. No site starts from a blank screen.

Hosted by GullySystem

The control desk, the field technicians and the accounts team open one shared record for each connector, held on servers that GullySystem looks after. Backups run nightly.

Works alongside

  • Charge point backend feed
  • Payment gateway
  • Email
  • SMS
  • WhatsApp
  • Accounting export
Common questions

Questions owners ask before a demo.

Does it replace our charge point backend?

No. The backend still talks to the chargers. This system holds the business side, meaning sites, tickets, landlord settlements, fleet statements and spares, and it reads the backend rather than replacing it.

How do sessions get in?

Through a file or interface your backend provides. We read its format with your vendor during implementation, then test with a week of sample sessions before any live data moves across.

Can a fault ticket start from an alarm?

Yes, where the feed carries alarms. A connector that stays faulted past your set limit opens a ticket and tells the desk which technician is nearest.

Can hosts see their own site?

Yes. A landlord login shows only the sites in that agreement, with sessions, energy delivered and the settlement statement for each month, so fewer calls reach your commercial staff.

How are refunds for cut-off sessions handled?

The desk records a reason and an amount. A manager approves it. The refund is saved against that session number, and it shows on the next fleet or driver statement as a credit line.

Can one technician cover many sites?

Yes. Sites belong to a route. A technician’s day lists the visits in order, and each visit shows the spares that charger model has needed before, drawn from earlier tickets on the same model.

Do you support different currencies and taxes?

Currency and tax are held per country and per site. Your accountant goes through each country’s rules with us during configuration, and the agreed setting is stored against the site.

What does it cost?

Site count, connector count and the backend feeds to read decide the quotation. Rules for host settlement, fleet statements and migrated records are each priced as parts. A demo on a sample network comes first, and a written quotation follows.

Can the data leave if we change systems?

Yes. History is exported by site, covering chargers, sessions, tickets and settlements. The columns and the file names are agreed with you and written into the quotation, so the export matches what your finance team expects.

How long before the control desk works faults in it?

Sites, the charger register, sessions with tariffs and fault tickets go in first. Field visits, spares, host settlement and fleet statements follow. The proposal shows dates for each stage.

What must the operator have ready first?

Bring the site list with host agreements, the charger and connector register, tariff sheets, recent fault logs and a sample utility bill. Arrange access to the backend feed. A control desk lead, a field lead and an accounts person should be named.

Wondering what it would cost? Share your requirements and an engineer will come back with a scope.

Industries

Built for.

The trades this product is set up for. Pick yours to see how the work runs there.

Related

Related products.

Your requirements

See EV Charging Operator Management Software set up around your records.

Tell us how you run things today. An engineer reads it and writes back with what fits as it is, what would need changing, and what we would start with.

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