Specifications include, but are not limited to: 4.2 Hardware A. Local controller and connections installed in a weatherproof container. B. Have the ability for Automated Load Management, in case of additional charging infrastructure implementations. C. Connection to on-site charging stations via ethernet interface (physical cable). D. Connection between the local controller and the backend should be connected by local internet or cellular. 4.3 Platform Compatibility A. Different bus types & OEMs (Original Equipment Manufacturer) (e.g., 35’, 40’, 60’ low floor, etc.). B. Accommodate/operate across different bus and charger types. C. Different battery capacities, and types. D. Different charging rates. E. Compatible with (OCPP) latest version (1.6 or greater). F. Must be compatible with customer-owned equipment and vehicles to allow for proper charge management of electric buses by means of multiple charging cabinets and dispenser type – both inverted overhead pantographs and plug-in dispensers. G. Capable of adapting to changes in charging, and communication standards between buses and chargers (any common practices surrounding communication and firmware). H. Commission the CMS with compatibility with all applicable charging equipment (power cabinets, pantographs, stand-alone units, etc.) with all bus manufacturer types. 4.3.1 Integration A. Integration with other transit operation systems: B. Bus telematics, specifically ChargePoint (also known as ViriCiti) C. Scheduling software (desired but not required) D. CAD/AVL software (desired but not required) E. Be responsive to changing route assignments (desired but not required)