Operating charging infrastructure: organise maintenance, faults and service contracts

A good service contract for charging infrastructure describes who detects a fault, who responds and how operational usability is restored. “Support included” is not enough. Separate regular maintenance, required inspections, ongoing monitoring and actual fault resolution. These services have different aims and may sit with different providers. What matters is that their handovers work in everyday operation.

Define the operational outcome you need

A temporary restriction in a visitor car park may warrant a different assessment from one affecting pool vehicles that must leave in the morning. First describe which vehicles depend on charging and when. The existing guide to charging strategy for businesses helps structure these requirements.

Then agree suitable service hours. An office site with charging during working hours may need a different on-call model from a depot with overnight departures. This does not mean faults never occur outside service hours. You consciously decide which risks internal reserves will absorb and which a service provider should cover.

Define operational priorities for faults: a complete outage of the charging area, failure of a single required connector and an incorrect report are different cases. A single blanket response time usually fails to address their consequences adequately.

Distinguish maintenance, inspection and fault resolution

Maintenance is intended to keep the installation functioning. Inspections assess its safe condition against the applicable requirements. Fault resolution responds to a specific error. A maintenance appointment does not automatically replace a required inspection, and successfully fixing a software error does not demonstrate electrical safety.

In Germany, Section 14 of the Industrial Safety and Health Ordinance (BetrSichV) requires inspections before first use, recurring inspections and inspections after relevant changes or exceptional events under the conditions specified there. Intervals depend on the assessment for the particular work equipment; a blanket “once a year” is not a complete assessment. Results must be recorded. Section 14 of the Industrial Safety and Health Ordinance, as of 24 September 2026.

Ask the responsible specialist contractor for an installation-specific inspection plan, including the associated charging cables. For these cables, the DGUV particularly stresses operating conditions, usage and manufacturers' guidance when setting inspection intervals. DGUV: electromobility FAQ.

Turn the service contract into a service table

Have exclusions presented as clearly as included services. Travel, spare parts, vandalism, mobile connectivity costs or work on the upstream electrical installation may be charged separately. An apparently low base price is hard to compare if the most common causes of faults fall outside the package.

Response time is not restoration time

A promised response within a specified period initially means only that someone is handling the case. Diagnosis, procurement of spare parts and access may still be needed before charging becomes usable again. Ask for separate definitions of intake, a substantive response, an on-site visit and restoration.

Also state when the clock starts and when it may be paused. Does an automated message already count as receipt? What happens if the provider has no access at night? Are weekends included? What obligations must you fulfil for the agreed service to be delivered?

If firm restoration times are not promised, you need a suitable backup supply. Credits can soften the financial impact of a bad month, but they do not get an uncharged vehicle onto its next route. Assess practical protection, rather than only possible contractual penalties.

Define availability from an operational perspective

An online status in the backend does not prove that a vehicle can charge. Cables, authorisation, vehicle communication or an occupied bay may still prevent a session. Define the metric the contract uses: connection to the backend, technical readiness to charge or an actually successful charging session.

A hypothetical calculation: over 720 hours in a month, seven hours of downtime represent roughly one percent. If those hours fall immediately before important departures, the impact can be substantial. High monthly availability can therefore coincide with a poor operational outcome.

Supplement the technical metric with specific consequences: affected vehicles, missed charging targets and necessary backup charging sessions. This supports process improvement. It is not an invitation to attribute every individual fault to a person.

Organise the internal side of fault resolution

Name a responsible person and a deputy. Both should know which faults to report, which bays they may close and when a qualified person is needed. Employees should not open electrical enclosures or carry out improvised repairs.

A useful report includes the charge point reference, time, visible error message, affected vehicles and any known impacts. The existing article “Charging session won't start” is suitable for safe initial observation. Technical interventions remain the responsibility of the designated specialist personnel.

Keep access arrangements, site plans and contacts up to date. A service technician may need a key, vehicle access permission or an escort. For leased sites, define when the landlord or building operator must be involved. Without this preparation, even a good contract is undermined by organisational delays.

Include software maintenance and the end of the provider relationship

Operational planning also includes updates, permissions and data access. Ask how changes are announced, tested and rolled back if problems arise. An update during a tight charging window can have different consequences from the same update at the weekend.

Agree what data you will receive at the end of the contract and how technical access will be transferred. Document configurations, hardware versions and responsible partners. An installation should not become difficult to keep operating simply because only a former contact knows the access details.

Also check the service contract term against hardware support. If spare parts or software maintenance cease, the company needs enough time for a planned adjustment. Request specific contractual statements rather than a general promise of future-proofing.

Run an operational test before final approval

Test a normal alarm, an unavailable contact and a fault requiring an on-site visit as an agreed exercise. Use a controlled process; do not create dangerous conditions. Check that tickets, escalation, access and feedback actually work.

StromNow Fleet describes ongoing operation and support as part of fleet infrastructure. For an enquiry about an operating concept, specify charging times, operational dependencies, existing hardware and internal responsibilities. Then ask for the specific scope of services and verifiable agreements for your site.