Specifications include, but are not limited to: A. Required 1. Provide user interface accessible by every teacher in an LEA that: a. Shows which programs, websites, extensions, and add-ons have been vetted by the LEA; b. Allows for a tag feature or equivalent in which an LEA can indicate information such as student data security or purpose of a program; and c. Allows for requests for additional software program to be vetted by the LEA. 2. Provide analytics for device and application usage of teachers and students: a. At least on an LEA level; and b. Share aggregate usage LEA data to USBE on a quarterly basis. 3. Maintain a user-friendly interface for both users and local administrators. 4. Provide training and continued support to LEAs using product. B. Optional 1. Drill down to the student level and provide teacher reports. 2. Collect student data on digital programs to determine Tier II and Tier III interventions and display teacher reports. 3. Contain an Application Programming Interface (API) that allows the education technology management system to interface with LEA’s existing Learning Management Systems (LMS) USBE will: 1. Provide a list of all LEAs and population sizes at the beginning of each school year. 2. Disseminate quarterly reimbursement based on Offeror’s quarterly project invoice (only for services and work that has been completed in the quarter).
