Zynetic
Talk to salesRequest a demo

Command Palette

Search for a command to run...

CPMS module · Maintenance

Faults become tickets. Automatically.

Reactive, automatic, planned and customer-raised. Every path a fault can take becomes a ticket the console can prove was fixed.

Four journeysSLA and TAT trackedPlaybooks that self-heal

Four journeys

Every path a fault can take, handled.

One work queue, four ways onto it, and the same SLAs whichever door a problem came through.

Reactive maintenance.
A live fault becomes a ticket with history, priority and an assignee, before anyone calls to complain.
Auto-recovery.
Known faults trigger playbooks first: reset, verify, log. Many chargers heal without a human being paged.
Periodic maintenance.
PM schedules on a calendar with task templates. Visits happen before failures do, not after.
Customer support.
A raised complaint becomes a tracked ticket on the same queue. Same SLAs, same evidence, same proof of fix.

The back-office console

One console for support and network operations.

The systems underneath the four journeys, shared by your support desk and your network team.

Fault catalog.
Mechanical, thermal and electrical errors, each mapped to a playbook, or flagged unmapped so it gets one.
Work queue, kanban.
Tickets by status and priority, Low to Critical. Assign, reprioritise, cancel, all logged.
SLA and TAT.
Due dates that mean something. Waive or extend with a reason, and the clock is part of the record.
Parts inventory.
Stock levels, adjustments and consumption. Tickets pull the parts they used, so counts stay true.
Playbooks, versioned.
Steps, exceptions and a function library. Test-run a new version before it touches a live charger.
PM calendar.
Month and week views, the next 30 days at a glance, task templates. Pause or end a schedule any time.

The fault catalog

Every error has a name, and most have a playbook.

Mechanical, thermal and electrical faults live in one catalog, each mapped to the playbook that clears it.

  • Errors classified mechanical, thermal or electrical
  • Each code mapped to a recovery playbook, or flagged unmapped until it gets one
  • The same fault twice becomes a pattern, not a surprise
  • New codes from any charger vendor join the catalog, not a spreadsheet
Zynetic Maintenance fault catalog showing classified charger errors mapped to recovery playbooks.

The work queue

One work queue for every ticket.

Tickets move Open to In progress to Awaiting parts with priority and SLA on every card, and every intervention on the record.

  • Priorities from Low to Critical, sortable and filterable
  • SLA and TAT clocks on every ticket. You see them before they breach
  • Waive, extend, reassign or reprioritise, with who and why logged
  • Reactive, auto-recovery, PM and support tickets on the same board
Zynetic Maintenance work queue showing tickets by status with priority and SLA.

PM schedules

Visits happen before failures do.

Preventive maintenance runs on a calendar: month and week views, task templates, and the next 30 days at a glance.

  • Month and week calendars with every planned visit
  • Task templates so a quarterly DC inspection means the same thing every time
  • Upcoming-30-days list for planning crews and parts
  • Pause or end a schedule any time, with the history kept
Zynetic Maintenance PM schedules showing planned visits on a calendar and the upcoming list.

Parts and playbooks

Spare parts counted right. Repair steps tested first.

Tickets consume parts so inventory stays honest, and playbooks are versioned, test-run and only then trusted with live chargers.

  • Stock levels and adjustments, every change with a reason
  • Tickets pull the parts they used. Counts stay true without an audit
  • Playbooks with steps, exceptions and a shared function library
  • You test-run new versions against a charger before they go live
Zynetic Maintenance parts inventory and playbooks with stock levels and versioned repair steps.

The named jobs

Know about problems before your customers do.

They just stop coming. Six named jobs watch your infrastructure around the clock and decide what is worth waking someone for.

Watchtower
Probes chargers that have gone quiet, before a customer finds them dead.
Knightwatch
Tells operations the moment a site or charge point drops off.
Session Monitor
Catches runaway and unpaid sessions while they are still small.
Overstay Monitor
Clears or charges for connectors held after the charge ends.
Charger Error Monitor
Grades faults by severity and acts on the serious ones.
Flap Tracker
Keeps the connection history that proves a network problem.

Ninety-one seconds, no engineer, no lost weekend. The jobs live on the OCPP layer

The platform

Explore the other modules.

The CPMS.
The console the whole business runs on.
Explore
Native Android and iOS app.
Your customers charge under your brand.
Explore
Host Portal.
Site owners see their numbers and set their price.
Explore
Fleet Portal.
Fleets run wallets, RFID caps and reports.
Explore
Operations App.
The engineer app for the Maintenance module.
Explore
OCPP.
How your chargers connect to the CPMS.
Explore
OCPI roaming.
Your chargers on partner apps.
Explore
Integrations.
Hardware, payments and your systems.
Explore

Questions

Frequently asked questions.

Usually past twenty charge points, or the first time a fault is discovered by a customer rather than by you. Below that, the CPMS status view and the named-job alerts are generally enough.

Next step

Tell us your worst repeat fault.

We will show you how the error repository, playbook and spares flow would have handled it.

  • Demo on your data, not ours
  • Honest answers, including when it is no
  • We reply within one business day

We reply within one business day · Singapore · Dubai · Abu Dhabi