Specifications include, but are not limited to: A high-level outline of the expected system solution: SOFTWARE Primary Functions (Required) Student Information System • Attendance • Discipline • Document Management • Faculty & Staff Management • Fees & Billing • Standards Based Report Cards • Teacher Grade Book • Transcripts • Parent Portal • Registration – including On-line option • Scheduling • Testing, Assessment, & Reporting • Individualized Educational Plan (IEP documentation) Online enrollment • Programs & Services • Ability to identify specific student groups; IEP, ESOL, Homeless, Gifted through an alert system • Data uploads (custom) • Data importing & exporting • All State of Missouri Mandated Core Data Reporting • College Career Readiness Data Tracking • Interface capabilities to be set up for specific vendors, i.e., Panorama, Renaissance, Savvas, Rethink, others to be determined • Medical Module • Street Block/Boundary File • Train Environment – duplication of live environment student application file • Login Options > Staff > Parent > Student Desired Capabilities • School Lunch System- Vendor integrated system or ability to integrate with current district system. • Student/Parent Messaging System Auto Dial system with SMS availability - Vendor integrated system or ability to integrate with School Messenger. • Transportation- Vendor integrated system or ability to integrate with Versatrans. • Ability to use system to accommodate our magnet and choice lottery system. • Ability to impersonate employees for troubleshooting purposes. • Ability to generate Photo rosters and IDs. • Link street/boundary file to on-line registration providing parents school assignment information. • Online registration notification – alerts Pupil Accounting Office directly when an online registration occurs. Pupil Accounting reviews/approves and forwards to the appropriate site. • Have the ability to “lock” previous school year. Data would remain the same for that particular year and would not change if data is changing the following year. For example, if the address changes next year, the change would only be reflected in the current year; address would not change in prior year’s file set. • Place a “tag” on every transaction indicating who’s responsible. • Scheduling – includes 4-year plan. • Validation file (pending file) – requires approval from Pupil Accounting prior to being applied to the student database.
