Reporting a Dual-Connector Charger with One Output Unavailable

Report a partially working charger at output level as well as cabinet level. If one output cannot serve a vehicle while another still works, “charger online” hides a service loss and “charger offline” hides remaining service. Drivers and maintenance staff need a more precise description.
First establish what the equipment can do simultaneously. Two physical connectors do not necessarily represent two independent charging ports. The status record and its denominator must follow the actual service arrangement, not just the number of cables on the cabinet.
Define the equipment hierarchy
Keep identifiers for the site, cabinet, charging port and physical connector where the equipment distinguishes them. Map those identifiers to the labels a driver and service engineer can see.
A port serves a vehicle; a connector is the physical interface. Some arrangements provide alternative connectors for one service, while others support more than one vehicle at once. Confirm the installed configuration before choosing a reporting model.
EVB’s direct-current (DC) charging category lists wall-mounted, floor-mounted and split families, including two-gun configurations. That public variety is a reason to define the hierarchy for the actual equipment. It does not establish simultaneous service capacity from a product-family name alone.
Separate communications from serviceability
“Online” can describe communication with a management platform. It does not establish that every output can start and sustain a session. An output fault can remain while the cabinet continues sending data.
Also distinguish a working output that is occupied from an output that cannot charge. The first may be serviceable but unavailable to a new arrival. The second is an equipment or service restriction that needs its own reason and duration.
Agree the states the operator will use and how they map to the platform’s actual records. Preserve unknown status when data is missing; an absent message should not silently become either a confirmed fault or confirmed availability.
Use a denominator that answers the stated question
Consider an illustrative cabinet verified to support two vehicles simultaneously. During a one-hour period, one output is serviceable throughout and the other is out of service throughout. The cabinet communicates for the whole hour.
Its communications record could show 100% online time. Its serviceable output-time record would show one of two output-hours, or 50%, under the stated definition. Neither number should be presented as the other.
That simple example is not a measured EVB reliability result or a regulatory uptime calculation. Real reports must define operating hours, planned exclusions, occupied states, missing data and any other conditions consistently. Keeping the definitions visible prevents a percentage from concealing its denominator.
Tell the driver which service remains
Publish the affected output and connector type where the information channel supports that detail. A driver whose vehicle needs the failed connector may have no usable service even though the cabinet still serves other vehicles.
If a channel accepts only one cabinet-level state, agree how the operator will describe partial service without overstating availability. Keep the limitation in the internal record and in any appropriate driver notice.
Record when the public status was changed and later checked. A repair ticket marked open does not prove that the driver-facing app has been updated, and a completed ticket does not prove the output is ready until the required return-to-service check is recorded.
Give maintenance the output history
For each incident, keep the first confirmed affected time, output identifier, symptom, cabinet communication state and evidence. Add any effect on the remaining output, such as an agreed power restriction. Separate observed events from estimates of when the fault began.
After repair, retain the component or configuration change, test result and return-to-service time. If evidence supports only a narrower restored function, describe that limit instead of closing the record as fully normal.
This layered reporting lets the operator answer three different questions accurately: can the cabinet communicate, which vehicles can currently be served, and which part needs attention? Those answers are more useful than forcing every partial fault into a single online-or-offline label.