Specifications include, but are not limited to: Application should only utilize native browser-based technologies such as HTML and HTML5. No application utilizing third-party plugins will be considered (Examples of plugins include, but not limited to, Flash, Java, Silverlight, etc.) No local caching server or software required or recommended. The vendor’s application should scale as needed to support client demand. Will support any modern OS, defined as the current publicly available version minus three versions. The most common Operating Systems used by KCS are: MacOS, ChromeOS, and Windows. As system updates become available, vendor to give KCS adequate notice of any foreseeable disruptions due to updates. **Vendor is to also list any and/or all required plugins for full product functionality. Will support current browser versions, defined as the current publicly available version minus three versions, for the following web browsers: Google Chrome, Safari, Microsoft Edge, Mobile Safari, Mobile Chrome. As browser updates become available, vendor to give KCS adequate notice of any foreseeable disruptions due to updates. System must have user authentication using SAML, preferably Microsoft 365 SAML. Data exchange from our SIS to vendor should be automated. Vendor will be responsible for processing any differencing (changes, updates) to vendor data based on the automated exchange. KCS options for data exchange include Classlink OneRoster (preferred) or secure exchange of .csv files directly with vendor via SFTP transfer. KCS will not use Clever for data exchange. Vendor must be in full compliance with FERPA, COPPA, and all applicable federal/state laws pertaining to student data privacy and governance.
