There’s a meaningful difference between managing EV charging at a single site and managing it across a national fleet operation. The single-site problem is a load management and scheduling challenge — tractable, well understood, and solvable with the right software and electrical design. The multi-site problem adds an entirely different layer: how do you maintain visibility, control, and performance consistency across dozens of sites simultaneously, each with its own grid connection, its own operational schedule, and its own local conditions?
This question moved from theoretical to operational for EVSE through its work with Toll Group’s Project TruckVolt — the deployment of battery electric heavy vehicles and charging infrastructure across 10 distribution centres and customer sites nationally. What Toll required wasn’t a collection of independent charging installations. It was a unified infrastructure that could be monitored, managed, and optimised as a single system, regardless of whether a vehicle was charging in Sydney, Melbourne, or Brisbane.
This article describes what multi-site depot orchestration involves technically, what Toll’s project required in practice, and what organisations planning national fleet electrification need to understand before they start.
Why Multi-Site Management Is a Different Problem
An organisation operating EV charging at a single depot faces a defined set of challenges. Available grid capacity sets a ceiling. The fleet’s departure schedule defines the overnight charging window. Load management software allocates capacity across the charger pool. The variables are known, the system boundary is clear, and the engineering decisions are relatively straightforward.
Extend that to ten sites across five states and the problem changes in character. Each site has its own DNSP, its own connection capacity, its own local electricity tariff structure, and its own operational parameters. Vehicles that operate interstate routes may arrive at sites other than their home depot. The maintenance team responsible for charger uptime is distributed across states. And the organisation’s finance team wants consolidated data on energy costs, charger utilisation, and fleet readiness across the entire network, not ten separate reports.
The software and operational architecture that manages this is what we mean by multi-site orchestration. It’s not one charger management system per site — it’s a platform that treats the national charging network as a single managed asset, with site-level autonomy where necessary and centralised visibility everywhere.
The Technical Architecture of a Multi-Site Charging Network
OCPP as the Foundation
Open Charge Point Protocol (OCPP) is the communication standard that makes multi-vendor, multi-site management possible. OCPP-compliant chargers communicate with a central management system using a standardised protocol, which means the organisation isn’t dependent on a single charger manufacturer’s proprietary software to manage its network.
For Toll’s ten-site deployment, OCPP compliance was non-negotiable. The alternative – managing ten sites through separate vendor platforms – would create exactly the fragmentation that makes national fleet management difficult. OCPP allows a single platform to receive status updates, send charging commands, and collect session data from every charger in the network, regardless of hardware brand.
OCPP 1.6 is the current widely-deployed version in Australia. OCPP 2.0.1 introduces capabilities that are increasingly important for large-scale fleet operations: more granular smart charging controls, improved security through end-to-end encryption, enhanced transaction data, and better support for V2G (vehicle-to-grid) functionality. Specifying OCPP 2.0.1 compliance from the procurement stage is the decision that preserves the most operational flexibility over the life of the infrastructure.
Centralised vs Edge-Based Management
A multi-site charging network needs to handle two types of decisions: those that require real-time local response, and those that benefit from central optimisation.
Real-time local decisions — how to allocate available capacity between the twelve chargers currently drawing load at the Brisbane depot, given the current building demand and this morning’s departure schedule — need to be handled at the site level. Network latency between a site and a central server is too variable to rely on central commands for real-time load management.
Central decisions — how to report energy consumption across all sites, how to identify a charger that’s been reporting faults across multiple sessions, how to push a firmware update to all units across the network — are handled at the platform level.
The architecture that supports both is a combination of edge-based controllers at each site (which handle local load management autonomously using locally cached schedules and priority rules) and a cloud-based central platform (which provides configuration management, reporting, alerting, and cross-site visibility). EVSE’s OCPP-based platform architecture uses exactly this model — each site operates independently for real-time load management but reports back to a central system that gives fleet managers a single view of the network.
Fleet Scheduling Integration
The charging schedule for each depot is driven by the fleet’s operational timetable — which vehicles depart first, which routes have highest energy requirements, which vehicles are reserved for maintenance the following day. For a national fleet operator like Toll, this data lives in a fleet management system.
The charging platform needs to receive this data and translate it into charging priorities. A vehicle departing at 4:00am needs to be fully charged by 3:30am. A vehicle that isn’t leaving until 10:00am can charge later, leaving earlier-departing vehicles first access to the available capacity. The integration between the fleet management system and the charging management platform is what makes this sequencing automated rather than manually managed by depot staff.
At Toll’s scale — 28 battery electric vehicles deployed across 10 sites with plans for expansion — the operational benefit of automated priority scheduling is significant. Without it, a depot manager at each site would need to manually configure charging priorities each evening based on the next day’s run sheet. With it, the system handles the sequencing based on live fleet data, and the depot manager’s role shifts to exception management.
Site-by-Site Variation and Why It Matters
One of the underappreciated challenges of national fleet charging deployment is that no two sites are identical. The infrastructure decisions that are straightforward at a large metropolitan distribution centre become more complex at a regional depot with limited grid capacity, or at a customer site where equipment needs to coexist with the customer’s existing electrical infrastructure.
Grid Connection Variation
Toll’s ten distribution centres span multiple states and multiple DNSPs. Each DNSP has its own connection application process, its own technical requirements, and its own capacity at the relevant network connection points. Some sites had sufficient existing capacity to support the additional charging load with switchboard upgrades only. Others required DNSP augmentation — work on the network side that took months and added to the project cost.
Managing this variation requires a site-by-site grid feasibility assessment as a first step, with the results feeding into the overall project plan. Sites that require DNSP augmentation need to be identified early because their timeline sets the constraint for that portion of the rollout. Toll’s project, supported by ARENA funding and structured around a formal project management framework, built this assessment into the program from the outset.
Electricity Tariff Optimisation Across States
Commercial electricity tariffs vary significantly between states and between network regions within states. Time-of-use tariffs, demand charges, network access fees, and the availability of off-peak periods differ between Ausgrid in NSW, AusNet in Victoria, Energex in Queensland, and the other DNSPs involved in a national rollout.
A fleet operator that manages each site’s charging schedule independently, without reference to the local tariff structure, will pay more than necessary for energy across the network. A platform that incorporates tariff data into the charging schedule — shifting load into the cheapest available windows at each site — generates ongoing savings that compound across the full network over time.
Operational Schedule Differences
A distribution centre handling FMCG freight operates on a different schedule from a customer site handling industrial logistics. Some sites turn vehicles over twice a day; others have consistent overnight dwell times. The charging strategy that works for one doesn’t necessarily work for the other.
The flexibility of an OCPP-based platform is that charging configurations can be set at the site level within the constraints of the central platform. A site with a mid-shift changeover can be configured with different priority rules from a site with overnight-only charging windows, without requiring separate software platforms for each.
Monitoring, Alerting, and Uptime Management at Scale
Fleet readiness — the assurance that every vehicle that needs to depart tomorrow morning will have sufficient charge — is the primary operational output of a well-managed charging network. When it fails, it fails visibly: a vehicle leaves the depot without enough range to complete its route.
For a ten-site national network, achieving fleet readiness consistently requires more than good scheduling software. It requires a monitoring and alerting architecture that identifies problems before they affect fleet readiness, and a maintenance response capability that can resolve issues before the next departure window.
Real-Time Fault Detection
OCPP-compliant chargers report status continuously – active charging, idle, faulted, offline. A central platform that processes these status reports can identify a faulted charger in Brisbane within seconds of the fault occurring, regardless of where the monitoring team is located.
The alert logic needs to be configured thoughtfully. A single charger fault at a depot with twenty chargers and twelve vehicles requiring charge is a minor event — there’s sufficient redundancy to manage around it. The same fault at a depot with eight chargers and eight vehicles requiring full charge overnight is critical. Alert priority needs to reflect the margin between available capacity and required capacity, not just the presence of a fault.
Remote Diagnostics and Over-the-Air Updates
OCPP 2.0.1’s enhanced remote management capabilities allow a significant proportion of charger issues to be diagnosed and resolved without a site visit. Firmware updates can be pushed to all units in the network simultaneously from the central platform. Configuration changes can be applied remotely. Log data from faulted units can be retrieved and analysed without dispatching a technician.
For a national network, the economics of this are substantial. A technician based in Sydney can resolve a configuration issue affecting a Brisbane charger without a flight and a site visit. Even issues that ultimately require on-site attention can be better diagnosed remotely, so the technician who does visit arrives with the right parts and a clear picture of what needs to be done.
What Separates Orchestration from Charger Installation
The distinction that matters for organisations evaluating infrastructure partners is the difference between a company that installs chargers and a company that designs and manages charging infrastructure.
A charger installation is a point-in-time activity. The charger goes in, it works, the installer leaves. What happens over the next five years — firmware updates, tariff changes, fleet expansion, OCPP integration with new fleet management software, responding to charger faults at 2:00am — is a separate question.
Orchestration is an ongoing operational commitment. It requires software infrastructure, monitoring capability, integration expertise, and a service model that spans the life of the network, not just its installation. For Toll’s project, the requirement wasn’t hardware supply — it was a partner capable of managing the full operational lifecycle of a national charging network.
The organisations that will successfully electrify large, complex fleets are the ones that make this distinction at the procurement stage — before selecting an infrastructure partner based primarily on hardware price. The hardware is a commodity. The operational capability to manage it at national scale is not.
Project TruckVolt is the clearest reference case available in Australia for what national fleet electrification infrastructure looks like in practice. The operational challenges it surfaced — site variation, DNSP complexity, tariff optimisation, fleet scheduling integration, uptime management at scale — are the same challenges that any organisation planning a multi-site electric fleet will face. The difference between organisations that manage them successfully and those that don’t is whether they treated the infrastructure as a system from the start, rather than a collection of individual installations.
Frequently Asked Questions
What is multi-site EV depot orchestration?
Multi-site depot orchestration is the unified management of EV charging infrastructure across multiple physical locations as a single network, rather than a series of independent installations. It involves a central software platform that provides visibility, configuration management, reporting, and alerting across all sites, combined with edge-based controllers at each site that handle real-time load management autonomously. The result is a national fleet operator having a single operational view of their entire charging network.
Why is OCPP compliance important for fleet charging infrastructure?
OCPP (Open Charge Point Protocol) allows charger hardware from any compliant manufacturer to be managed through a single central platform. Without it, a multi-site operation is forced to manage each site through the charger manufacturer’s proprietary software, creating fragmented visibility and making cross-site reporting, tariff optimisation, and fleet scheduling integration impossible. OCPP 2.0.1 is the recommended specification for any new fleet installation, providing smart charging controls, enhanced security, and V2G capability.
How does automated fleet scheduling integration work with depot charging?
Fleet management systems contain each vehicle’s departure schedule, route energy requirements, and maintenance status. When this data is integrated with the charging management platform, the system automatically prioritises charging based on departure time and energy need — vehicles leaving first are charged first, and vehicles with higher route energy requirements receive more capacity. This removes the need for depot staff to manually configure charging priorities each evening and reduces the risk of vehicles departing under-charged.
How do electricity tariffs affect multi-site charging costs?
Tariff structures vary significantly between states and network regions. Time-of-use rates, demand charges, and off-peak windows differ between Ausgrid (NSW), AusNet (Victoria), Energex (Queensland) and other DNSPs. A charging platform that incorporates local tariff data and shifts load into the cheapest available windows at each site can generate substantial savings across a national network — savings that compound over time as the fleet scales.
What uptime standards should a fleet-grade charging network meet?
Fleet-critical charging infrastructure should target 97 to 99 percent uptime per charging position, measured monthly. Response time commitments for fault resolution should include acknowledgement within two hours and on-site response within four hours for critical faults. Anything softer than this leaves the fleet operator exposed to operational risk. Real-time fault detection through continuous OCPP status reporting enables faults to be identified within seconds, regardless of where the monitoring team is located.
What is the difference between a charger installer and a charging infrastructure orchestrator?
A charger installer delivers and commissions hardware at a point in time. An orchestrator manages the full operational lifecycle of the charging network — firmware updates, tariff optimisation, fleet scheduling integration, fault monitoring, remote diagnostics, and capacity planning as the fleet grows. For national fleet operators, the orchestration capability is more operationally critical than the hardware itself, and should be the primary criterion when selecting an infrastructure partner.
Tell us about your car and home to see recommendations.
Stocking the best Electric Car products from the World’s leading brands.
All of our EVSE products are compliant with Australian & International standards.
If you find one of our products cheaper with any other Australian retailer, we promise to beat it by 5%. Just make a note of the price and where you have found it, and then give us a call on the following number:
