Student Minimum Requirements Sample Clauses

Student Minimum Requirements. 1. Vendor must offer an end-to-end workflow to initiate transportation requests (from parent/student, school, or CPS Central Office), evaluate transportation eligibility and viability, route students and/or offer transportation alternatives, and communicate with/enable families to request and receive updates about transportation in real time. All of this functionality does not need to be a part of a single software application, however we do need a solution that streamlines providing transportation for families from request to delivery and incorporates CPS enterprise systems in real time, where necessary. 2. Software must address the need for parents, schools, or CPS staff to understand where each transportation request stands in the workflow, how it will be addressed, and whether outstanding issues are logged and/or holding up delivery of CPS transportation services. 3. Software must be able to read and/or interface directly from CPS’s Student Information Systems (Aspen & SSM) and ServiceNow instance. Software must allow STS to add attributes to students that are taken into consideration when assigning vehicles to routes. These include attributes such as but not limited to lift requirements, air conditioning, bus aides , nurses, harnesses etc. 4. Software must provide a list of new students (via a dashboard, downloadable and editable formats such as but not limited to Google Sheets, a table view via API, or s-ftp CSV) that have entered the District and a list of students who have changed or dropped (fields such as, but not limited to, by date, school, and change type) from the previous day. 5. Software must have the ability to accommodate for CPS-defined demographic fields, both transportation as well as non-transportation related, and be configurable. These include but are not limited to Parent Contact Information, Child home drop off provisions, medical accommodations/needs, other disabilities, lift, harness, A/C, Aide, oxygen, car seat, etc. 6. Software must have the ability to differentiate CPS Schools from Charters and Non-Public Schools (the latter two of which may be partially transported by the District pursuant to Board approved programs) and student types (including but not limited to general education students, preschool students, etc.) as defined by CPS.