Mobility Infrastructure · Depot and Workplace Charging
Business charging works when vehicle duty, dwell time, site capacity, user policy and service ownership are designed as one operating system—not when chargers are selected first.
For: Fleet, facilities, energy, parking, finance, procurement, IT and sustainability teams defining a business, depot, workplace, tenant or visitor charging service.
Key decisions on this page
Define the service before the hardware
State who needs energy, when vehicles must depart, how charging is prioritized and what constitutes a failed service.
Model demand with operating data
Use route, dwell, parking and adoption scenarios; nameplate charger power alone does not determine the infrastructure need.
Contract for operation and exit
Specify reliability, diagnostics, maintenance, data rights, cybersecurity, network portability and the responsibilities that survive handover.
Quick answer: what a business is actually procuring
A business is procuring a charging service supported by vehicles, parking, electrical distribution, chargers, communications, software and operating processes. The same charger can be suitable at one site and unworkable at another because the vehicle schedule, grid connection, parking turnover, accessibility, support model or tariff is different.
The Depot and Workplace Charging hub sets the cluster boundary. This guide owns the service and operating model: why charging is being provided, who uses it, how demand is controlled, who is accountable, and what evidence should be required before a contract is approved.
Choose the use case and decision stage
| Use case | Primary outcome | Evidence needed before equipment selection | Operating issue to resolve |
|---|---|---|---|
| Fleet or depot | Vehicles ready for routes, shifts or service calls | Vehicle list, route energy, return and departure windows, reserve policy, seasonal and duty variability | Priority, missed-departure response, redundancy and overnight supervision |
| Employee workplace | Convenient charging during working hours | Employee demand survey, parking occupancy, commute pattern, home-charging access and adoption scenarios | Eligibility, sharing, pricing, idle behavior, accessibility and fairness |
| Customer or visitor | Amenity, paid service or destination charging | Expected dwell, customer profile, utilization scenario, parking rules and payment need | Access, payment, support, wayfinding and charging-space turnover |
| Tenant or shared campus | Allocate a limited resource across organizations | Lease boundaries, user groups, meter and billing options, growth plan and landlord approvals | Cost allocation, credentials, data ownership and responsibility for faults |
| Mixed site | Serve fleets, staff and visitors with one site architecture | Separate demand profiles, service priorities, spaces and billing or allocation rules | Prevent one group from consuming capacity needed by another |
A procurement-heavy call to action is premature when the organization has not yet decided which of these services it is offering. At the awareness stage, define the service. At the evaluation stage, establish demand and site readiness. At procurement, translate those decisions into measurable requirements, acceptance tests and support obligations.
Build a charging-demand model
For controlled fleets, start with energy required between charging opportunities rather than annual mileage alone. For each vehicle or duty group, record distance, energy consumption under realistic conditions, arrival time, departure time, minimum departure state of charge, charger acceptance limit and operational reserve. Use route and telematics data where available, but keep unusual duty days and seasonal effects visible.
For employees, tenants or visitors, the problem is probabilistic. Not every parked electric vehicle needs a full charge every day. Survey likely users, observe parking duration, estimate adoption and model several participation cases. A port-sharing policy or reservation system can reduce the number of dedicated spaces, but it adds user behavior and administrative work that should be included in the operating model.
| Input | Useful measure | Common mistake |
|---|---|---|
| Vehicle energy need | kWh required before the next controlled charging opportunity | Using battery capacity as if every vehicle arrives empty |
| Dwell window | Arrival, departure and usable charging hours | Assuming the full parking period is available despite loading, cleaning or shift handover |
| Vehicle acceptance | Maximum and expected AC or DC power accepted by each vehicle | Sizing every charger to its nameplate maximum without checking vehicle limits |
| Concurrency | Number of vehicles likely to need energy at the same time | Adding charger ratings without managed charging or realistic schedules |
| Reserve and disruption | Energy or spare capacity held for late returns, route changes and charger faults | Optimizing the normal day with no contingency |
| Growth | Vehicle and user scenarios by stage | Installing only for day-one demand or oversizing an unsupported forecast |
Design the operating model
The operating model determines whether charging is a fleet asset, employee benefit, parking service, customer amenity or revenue activity. It should identify the service owner, site owner, charger operator, network provider, maintenance contractor, utility interface, user-support route and the person authorized to change pricing, access or load-management settings.
- Access: fleet-only, employee, tenant, visitor, customer, public or mixed; include exceptions and temporary access.
- Authentication: vehicle identifier, RFID, app, payment card, Plug & Charge, reservation or no authentication; define an offline fallback.
- Pricing and allocation: free, reimbursed, internal cost center, per-kWh, time, session or parking basis, subject to current local rules.
- Parking and turnover: dedicated spaces, shared spaces, queue, reservation, idle policy, towing authority and accessible-space treatment.
- Support: who answers a failed-session report, what information is collected, who can reset equipment and when a technician is dispatched.
- Change control: who approves firmware, tariff, access, connector, network, cybersecurity or load-management changes.
Treat the site as an integrated load
Charging must be assessed with the building or depot load, not in isolation. The National Laboratory of the Rockies describes site-integrated charging as a holistic problem involving building loads, charging demand and smart-charge management. Managed charging can reduce peak demand or defer some upgrades, but it cannot create energy that is not available before a critical departure.
The EV Charging Site Readiness guide owns the detailed electrical, utility, civil, accessibility, communications and permitting evidence. At business-case stage, the key question is whether the site has a credible path to deliver the required energy within operating windows under both normal and disrupted conditions.
Specify reliability as a service outcome
An equipment-uptime percentage can hide failed starts, payment problems, unavailable spaces, damaged cables or sessions that end prematurely. The Joint Office and ChargeX Consortium promote customer-focused measures such as charge-start success, charge-start time, session success and station-visit success. A private fleet may use different service levels from a public network, but the principle is the same: measure whether the user or vehicle received the required service.
| Measure | What it reveals | Contract or operating evidence |
|---|---|---|
| Ready-to-charge availability | Whether an assigned port is physically and digitally available when needed | Port status, blocked-space checks, cable condition and communication state |
| Charge-start success | Whether a valid attempt begins power delivery | Attempt and start timestamps, authorization failures and reason codes |
| Departure-energy success | Whether the vehicle reaches the required energy by departure | Required kWh or state of charge, actual delivery and exception reason |
| Fault-resolution time | How quickly a fault is diagnosed and restored | Alert time, triage, responsible party, remote action, dispatch and repair completion |
| Data completeness | Whether sessions, errors, energy and status records are usable | Export, reconciliation, missing-record rate and retained diagnostics |
| Service continuity | What remains available during cloud, network or vendor interruption | Offline rules, local control, credential fallback, backup and recovery test |
Minimum required error codes proposed by the ChargeX Consortium are intended to make diagnostics more consistent across the ecosystem. The contract should still define which party receives each alert, what data it can access, and how root causes are assigned across the vehicle, charger, network, payment and site systems.
Plan accessibility and user experience from the layout stage
Accessible charging is not achieved by labeling one conventional space after construction. The U.S. Access Board notes that existing accessibility requirements can apply to routes, spaces, operable parts and user interfaces, and its technical assistance highlights cable reach, clear floor space, access-aisle alignment, vehicle inlet location, payment and customer support. Applicable legal duties vary, so the project needs jurisdiction-specific review rather than a generic “ADA-ready” product claim.
Workplace policies also affect accessibility and usability. Instructions should be understandable, help should be reachable without relying on one app, and moving or sharing vehicles should not create a barrier for users who cannot easily handle a heavy cable or relocate a vehicle during the day.
Control software, data and cybersecurity dependencies
Networked charging can support access, pricing, load management, diagnostics and reporting, but it also creates dependencies on communications, cloud services, credentials and software updates. The Joint Office identifies charging stations as both grid-connected energy assets and transportation infrastructure. Define network segmentation, identity, remote access, logging, update responsibility, vulnerability handling, backups, incident response and the boundary between site IT and the charging provider.
Open protocols can improve portability, but a protocol claim is not a complete exit plan. Require a tested export of session, energy, user, tariff, fault and configuration data; document charger-to-network compatibility; preserve administrator credentials; and state what happens if the network provider or hardware vendor stops supporting the service. The Technology Procurement Process provides the wider contracting and acceptance sequence.
Compare ownership and service models
| Model | Potential advantage | Material dependency to test |
|---|---|---|
| Site-owned hardware and software contract | Direct asset and configuration control | Internal capability, warranty coordination, network portability and maintenance procurement |
| Third-party-owned or hosted | Lower initial responsibility for equipment and operations | Contract term, minimum payment, pricing control, site access, data rights and removal obligations |
| Lease or charging-as-a-service | Spreads cost and may bundle maintenance or upgrades | Escalation, usage assumptions, service exclusions, residual value and termination cost |
| Utility-supported make-ready or program | May reduce connection or infrastructure burden | Eligibility, timing, ownership boundary, tariff, control rights and program durability |
| Mixed model | Can allocate specialist duties to different parties | Interface risk, fragmented accountability and incompatible service levels |
Build the business case with scenarios
Use a base, growth and disruption case. Include vehicle and charger utilization, electricity tariff, demand exposure, network and payment fees, internal labor, parking administration, maintenance, replacements, utility work, downtime and exit. Count avoided fuel or operating cost only when vehicle duty and current prices support it. The Green Technology Business Case guide explains how to make assumptions and decision gates visible.
Procurement and acceptance checklist
A proposal should fail or remain conditional where the evidence below is missing.
- Approved service purpose, users, vehicle or parking demand and growth scenarios.
- Site-readiness evidence, utility pathway and stated electrical capacity assumptions.
- Per-port and aggregate power behavior, including shared power and managed-charging fallback.
- Accessible layout and interface review appropriate to the site and jurisdiction.
- Clear ownership of hardware, software, data, credentials, maintenance, support and cybersecurity.
- Reliability definitions, diagnostic data, response times, repair expectations and departure-energy tests.
- Comparable capital and operating cost boundary, exclusions, escalation and change-control rates.
- Commissioning with representative vehicles, simultaneous demand, network interruption and failed-session scenarios.
- Data export, network transition and end-of-contract or end-of-life plan.
Risks and limitations
A business can install technically compliant chargers and still create an unreliable service through weak demand assumptions, inaccessible layout, insufficient utility capacity, opaque network dependencies or unclear support responsibility. Conversely, a low-utilization first stage may be appropriate where enabling works and a controlled expansion plan reduce long-term disruption.
This guide does not determine electrical safety, accessibility compliance, utility capacity, tax treatment, incentive eligibility or financial return for a specific project. Vehicle specifications, tariffs, local codes, connector support and service terms must be verified at the decision date.
Continue from service definition to a deliverable project
The next page depends on whether the main uncertainty is site feasibility, cost or charging-power selection.
Test the site
Verify electrical, utility, civil, accessibility, communications and operating readiness.
Normalize project cost
Compare equipment, enabling works, software, operation, growth and exit on one boundary.
Choose the power mix
Compare Level 2, DC fast and mixed architectures against energy need and dwell.
For structured evaluation, use the Technology Evaluation Scorecard and record commercial differences in the Universal Vendor Comparison Worksheet.
Sources and evidence
Primary and authoritative references used for this page are listed below. Recheck current versions, local codes, tariffs and program terms before a live project decision.
- Procurement and Installation for Electric Vehicle Charging Infrastructure — U.S. Department of Energy Alternative Fuels Data Center
- Workplace Charging for Electric Vehicles — U.S. Department of Energy Alternative Fuels Data Center
- Operation and Maintenance for Electric Vehicle Charging Infrastructure — U.S. Department of Energy Alternative Fuels Data Center
- Site-Integrated Electric Vehicle Charging — National Laboratory of the Rockies
- Electric Vehicle Charging User Experience and Reliability — Joint Office of Energy and Transportation
- Electric Vehicle Charging Data and Communications Protocol Interoperability — Joint Office of Energy and Transportation
- Cybersecurity for Electric Vehicle Charging Infrastructure — Joint Office of Energy and Transportation
- Design Recommendations for Accessible Electric Vehicle Charging Stations — U.S. Access Board
- Customer-Focused Key Performance Indicators for Electric Vehicle Charging — ChargeX Consortium / Idaho National Laboratory
- Recommendations for Minimum Required Error Codes for Electric Vehicle Charging Infrastructure — ChargeX Consortium / Idaho National Laboratory
- Project Control authority: approved page map, complete page criteria and page-rules addendum — Future Green Technology
Reviewed and updated 29 June 2026. Recheck when connector standards, accessibility guidance, utility programs, tariffs, charging reliability methods or cybersecurity guidance materially change. Organizational author: Future Green Technology, published by Zenith Star Media.