A. Student ridership software must provide the SDOC with real-time data from student ridership. The software should provide parents notification when their student enters and exits the bus. B. Compliance with Family Education rights and Privacy Act (FERPA) and other privacy standards to protect student and employee information. C. Role-based access control to limit visibility of data to authorized personnel only. D. Student ridership software should have the ability to track students effectively combine two or multiple runs by utilizing one tablet. E. Student ridership software must seamlessly transfer students riding alternate buses, ensuring administration and parents have the ability to track student location when transported by a different bus or route. F. Allows multiple users to view the information produced by the system. The student ridership/ GPS system must integrate with the SDOC already established routing and student information software. • Data pulled from Bus Planner or other routing software. • Data pulled from FOCUS student school information. G. End users will need Key Performance Indicator (KPI) data for district reports to reflect the following, but not limited to: • Time and Attendance data. • Real time student boarded and un-boarded the bus. • Location of scan (Plotted scans on maps). • GPS routing history. • On-time arrivals. • Pre and Post trip inspection data. • Scanning ridership percentages. • Reunification status. • All other data request by the district pertaining service rendered. H. Software and system overall should be able to create reports through a dashboard or menu within the dashboard. I. These reports must have the capability to print.
