The Future of Gas Stations: Sustain Profitability with EV Charging - EVB

Compare charging architectures by asking which usable connectors remain after a particular component becomes unavailable. Several dispensers connected to one cabinet are not automatically independent chargers. Standalone units can also share a supply, controller or communications service. The number of visible charging bays therefore tells only part of the reliability story.

Start with the service the site needs to retain

Define the minimum useful service during a fault. A car park may need at least one available connector. A depot may need enough charging for a specified set of vehicles before departure. These are different requirements, and neither is captured by counting equipment enclosures.

Keep the statement measurable: which vehicles, how much required energy, by what time, and under which assumed failure? This is a planning scenario, not a prediction of failure frequency.

Avoid beginning with an unsupported claim that split or standalone equipment is inherently more reliable. The comparison needs the proposed design and service arrangements.

Map dependencies before comparing equipment counts

Draw the common components above the dispensers they serve. Include the incoming supply, distribution, conversion equipment, control system and communications path. Show shared services even when they sit outside the charger supplier's scope.

The DC charging product range from EVB separates wall-mounted, floor-mounted and split families. Compare each offered configuration on the same dependency drawing, showing which connectors share conversion equipment, controls or communications.

Request the actual proposed arrangement. A module-based design may have several possible responses to a failed component; do not assume either continued service or complete shutdown.

Build a failure-to-service matrix

Use the following row structure for both offers. Each supplier should identify the affected connectors, remaining capability, required action and supporting document.

· Incoming supply unavailable: which equipment loses its source?

· One conversion module unavailable: what output, if any, remains?

· One dispenser unavailable: can other terminals continue independently?

· Shared controller unavailable: what behaviour is designed and supported?

· Network connection lost: which charging functions remain available?

· Planned maintenance: which equipment must be taken out of service?

Separate “continues at reduced power” from “connector available but unable to start a new session”. Also distinguish existing sessions from new arrivals. A status indicator that stays lit is not evidence that useful charging continues.

Compare equivalent faults and evidence

A fair comparison applies the same operating need to each architecture. Comparing one split cabinet with several standalone chargers can be misleading if the standalone proposal also has a single shared controller or one common supply constraint.

Ask for a drawing, a documented failure response and, where appropriate, a controlled demonstration approved by the supplier. Do not create faults by disconnecting live components. Electrical and service tests belong to authorised people following the applicable procedure.

Record uncertainties explicitly. “Not demonstrated” means the response needs evidence; it is not proof that the design fails. Likewise, a supplier's description of modularity is not a measured uptime record.

Include repair access and restoration

The practical impact of a failure depends on restoration as well as the initial loss of service. Ask who identifies the failed component, who can authorise the work, which replacement parts are stocked and whether servicing one part requires a wider shutdown.

For a hypothetical site with four active connectors, retaining three at reduced output may be more useful than retaining one at full output. For another operating schedule, the opposite could be true. Evaluate the remaining charging service against departure needs rather than enclosure count.

Keep the completed matrix with the procurement decision. It explains why an architecture fits the site's tolerance for interruption and identifies what the service agreement must cover. It does not require an invented reliability percentage or a blanket preference for one hardware layout.