Specifications include, but are not limited to: STATEMENT OF WORK 1. Student Information Systems The application(s) will dictate the future infrastructure design that will allow users to quickly and efficiently access the information they need, whenever they need it, wherever it resides, and in the format they require. The Student Information System with the enrolling of students begins the flow of almost all follow-on data. The counting of students determines the allocation of all resources. The Student Information System should be a system that allows the schools the autonomy to setup their student management functions independent of other schools because of the different tracks of attendance, scheduling, grade reporting, etc. It should also be compliant for data to flow across multiple platforms. With each school managing its own computing requirements and priorities, we are seeking a Student Information System solution that will be Microsoft based at the school building. While the system must provide schools with the independent ability to enter and manage their data, all student data must be maintained within a central Microsoft based DBMS accessible from any district location. Collectively, the design of the Student Information System solution must: 1) Provide a system of data sharing of student information 2) Provide removal of redundant data entry on student transfer and re-entry 3) Allow Timetable Building for scheduling of student courses 4) Allow for curriculum monitoring 5) Ensure that students are enrolled in only one school at a time 6) Enable monitoring of student registrations and withdrawals 7) Automatically pass data from sending to receiving schools when students transfer locations 8) Enable the retrieval of individual student data from any District location 9) Provide capability for educational accountability and assessment data to be tracked 10) Provide for accurate collection of student and family demographic data, including foreign students. 11) Respond in real-time to requests for student information relating to attendance, discipline action, student progress, etc. 12) Easily produce student transcripts, grade information, class rank, college entry, scholarship and graduation reports 13) Enable the processing of student report cards 14) Will decrease the turn-around time for manual document preparation, handling, inputting, maintaining, and using student data The Student Information System will also serve as a data hub for the sharing of data with a number of satellite management systems, including but not limited to the current software systems listed in the CURRENT STUDENT INFORMATION SYSTEM ENVIRONMENT chart section. Satellite system interfaces not supplied with the Student Information System will be developed by the respective software vendors or by NPS technology professionals. These technical professionals must be able to select from and input to the Student Information System DBMS via in-house developed scripts and query language commands. 2. Required Functionality The selected Student Information System must contain the following components: 1) Web based 2) Student Registration and Enrollment 3) Online Registration 4) Scheduling 5) Attendance 6) Grade & Multi-Level Reporting (Low Income, Low Performance, etc.) 7) Teacher grade book 8) Finance / Human Resource data integration and reporting 9) Transportation data integration and reporting 10) Free & Reduced Lunch Reporting 11) Content Management 12) Disciplinary Action Reporting 13) Special Education IEP Tracking, Case Management and Medicaid Reinbursement 14) Health Records 15) Parent Web Portal 16) Student Web Portal 17) Emergency Contact Information 18) Supplemental and demographic student data 19) Customization 20) Query Capabilities including Drill-Down 21) Data Import/Export capabilities 22) Data dictionary 23) Security 24) Student Records/Transcripts 25) Student Profiles 26) Compliant with Federal and Virginia State reporting requirements Additionally, the Student Information System Solution will serve as a critical part of a NPS data-driven decision process. Therefore, identify the system architecture and scalability. Also describe the applications database structure and how it can interface with other applications including IEP system, ERP applications, data warehouse applications, etc. Also, identify if the application is government compliant as well as its compliance with the standards: SIF, ODBC, SQL, RDBMS, etc. Provide examples of K12 School Districts that have integrated your application into their enterprise. 3. Scope of Vendor Responsibilities Contractor must provide, or identify: a. Proposed Software Configuration Required Software b. Maintenance and/or Upgrade costs for the Required Software c. Conversion Methodology and Effort d. Implementation Methodology and Effort e. Documentation f. Comprehensive Training Program g. Any additional required integration services h. Provide a detailed written recommended hardware configuration to support the proposed software solution. i. The District requires, and the Contractor will, conduct weekly status meetings to discuss project status, deliverables, milestones, problem resolution, potential obstacles, conducting project status presentations as requested, attend Board meetings as requested, and resolve any other critical issues relating to this project.
