System shall be capable of providing options/features but is not limited to: ● a school bus routing application (with the ability to interact with multiple instances simultaneously–current school year, summer, and subsequent school year); ● dispatch module (current status of routes at seven different depot locations; bus substitutions; school and community communications); ● Field trip module (workflow process for approvals, ability to invoice, track payment, etc.) ● bus mounted tablet solution (capable of providing bus operator with real-time left/right directions, ability to send/receive messaging from dispatch, student tracking capability and tracking hours for bus operators/bus attendants); ● employee work monitoring function (route data, payroll/timekeeping with the ability to interface with current district operating systems such as Synergy and Oracle-based Lawson (HRIS)/HCM for payroll); ● Extracting and creating reports and archival data; ● Interaction with current Samsara GPS systems for parent application and student monitoring features; and ● components that MCPS may not have yet identified. The replacement system shall include support for the following areas: ● Single Sign-On ● System requirements ● Functional requirements ● Student data - Identified route number in synergy from assigned bus routes ● Stops (students who receive transportation services and special education transportation services) ● Schools (allows different programs at schools, different bell schedules, etc.) ● Schedules (dynamic scheduling to enable routes to have different trips each day).
