Specifications include, but are not limited to: Basic System Requirements o The system should have a hardware/software solution installed on-site to manage the charging operations locally. This allows the system to function autonomously even if the internet connection falters or fails. The system should always ensure a reliable charging operation. o Dynamically schedule charging across vehicles and chargers to (#1) reduce overall power demand, and (#2) ensure charge completion for all vehicles by a set pullout time for each vehicle based on actual plug-in time. o Reduce utility costs: by limiting total demand across all chargers to a specified limit by the time of day, but with logic to override demand limits if buses will not be fully charged by a specific time of day, as well as using schedule management to minimize time-of-use rates (kWh costs) o In case of a system failure, the solution should be able to provide a predefined maximum output value (fallback value) to the charging stations. o The system should be compatible with vehicles from different manufacturers. (BYD, Gillig, New Flyer, etc., and different chargers and manufacturers). o The systems should be compatible with manufacturers' charging stations using non-OCPP-compliant methods (such as the BYD chargers) and with OCPP-compliant charging systems such as the Induct-Ev Chargers and IndyGo’s future BEB fleet. Integration of various AC/DC charging systems should be possible under the following basic conditions. • Comparable with IndyGo’s BYD AC chargers or through electronic control module such as gateway system. • The charging stations have a local Ethernet interface/port. • The charging stations can communicate with a backend using OCPP 1.6 or higher. (is preferred for future applications) o The systems should have a dynamic interface with third-party systems as a bus depot management system for bidirectional data transfer (departure times, energy requirements, malfunctions, etc....).
