9-MPS Technology Standards - September 2024.docx

DOCX document 29 KB Posted

Attached to
RFB 5827 - Busing Services for Field Trips State and local contract opportunity
Solicitation number
RFB 5827 - Busing Services for Field Trips
Issued by
Milwaukee County, Mattoon Village, Wisconsin

About this file

The document is a Technology Standards file for Milwaukee Public Schools (MPS), outlining comprehensive technology requirements for potential vendors seeking to provide software and technology solutions. The standards specify technical preferences and mandatory requirements for SaaS applications, with a strong emphasis on browser-based solutions compatible with Chromebooks and supporting scalable infrastructure. The district anticipates supporting up to 10,000 staff accounts, 68,500 student accounts, 18,000 staff devices, and 170,000 student devices, with a robust network infrastructure featuring 20 Gbps symmetrical data center connectivity and Wi-Fi 6 standard access points.

The technology standards mandate specific technical integrations, including Clever for student application rostering and single sign-on, OAuth 2.0 authentication, and compatibility with Windows 11 and ChromeOS devices. Vendors must provide detailed technical specifications, including required URLs and ports, support web service exchange standards like SFTP and XML, and demonstrate compatibility with Microsoft ADFS or Google SSO authentication protocols. The document explicitly prohibits applications requiring Adobe Flash, Internet Explorer, Microsoft Silverlight, or Windows 10, signaling a forward-looking technological approach that prioritizes modern, cloud-based, and easily integrated solutions.

View the file

Other files for this state and local contract opportunity

Other files attached to RFB 5827 - Busing Services for Field Trips, newest first.
File Type Posted
11-Alternative Placement Site List FY25.pdf PDF
16-B 5827 Appendix C.2.doc DOC document
5-CCS - SCHEDULE H1-B 10.12.20.pdf PDF
15-Scope of Services - RFB 5827.docx DOCX document
20-B 5827 Appendix C.4.doc DOC document
8-CCS Directive SE Assignments.pdf PDF
10-CCS - requirements Overview.pdf PDF
13-Attachment A - Bus Specifications and Operating Procedures.docx DOCX document
21-Addendum 1.docx DOCX document
4-CCS - Appendix A.pdf PDF
6-RFB Notices, Terms, and Conditions.docx DOCX document
17-B 5827 Appendix C.3.doc DOC document
1-CCS - Appendix B.pdf PDF
12-Milwaukee Board of School Directors Busing Contract.docx DOCX document
14-CCS Requirements with Sliding Scale.docx DOCX document
18-B 5827 Appendix C.1.doc DOC document
19-B 5827 Appendix C.5 - SPECIAL OLYMPICS.doc DOC document
2-CCS - SCHEDULE H1-A.pdf PDF
3-CCS - Schedule H1-C.pdf PDF
7-Respondent Authorization Form.docx DOCX document
Show all 20

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Milwaukee Public Schools Technology Standards Updated September 2024 The purpose of the Technology Standards is to inform prospective Vendors of the District’s technical standards and capabilities. The Technology Standards are not meant to be a deterrent to prospective Vendor solutions, however, integration with existing systems is key to a successful implementation. Deviation from these standards must be approved by the Department of Technology. Solutions that most closely align with these standards will receive preferential scoring when procured as part of an RFI or RFP.

Software / Architecture SaaS (Software as a Service) delivered applications are required unless otherwise requested. MPS will not support any solution that requires on premises hardware for core application functionality.

· Browser-based applications are strongly preferred. The primary device used in schools for all students and some staff is a Chromebook.

· For proposed solutions requiring application installation on Windows workstations, the Vendor must be willing to work with MPS staff to develop a software delivery and update process through the district’s software library (currently Microsoft SCCM).

· For on-premises deployed software, the proposed solution must show evidence of regular software vulnerability patching and application development.

Rostering/Single Sign-On For student applications, the proposed solution must have an existing Clever integration, or be willing to develop a Clever integration, for automated rostering and single sign-on.

· More information is available at https://www.clever.com/partners

· Respondent must provide a copy of their Clever Certification letter, if applicable.

· Our district uses many products that offer single sign-on via the Clever Portal and applications are preferred to be integrated with Instant Login via the OAuth 2.0 standard. More information is available at https://dev.clever.com/v2.1/docs/identity-api

Performance Standards The proposed solution must be designed and/or scalable to support the following estimated maximum quantities of user accounts and devices (actual subscription quantities may vary):

· Staff Accounts: 10,000

· Student Accounts: 68,500

· Staff Devices: 18,000

· Student Devices: 170,000 Internet and Bandwidth The district supports a robust state-of-the-art network infrastructure at all schools and support sites. Deployed access points in each classroom support the latest Wi-Fi 6 standard. The district has a 20 Gbps symmetrical uplink/downlink per data center (40 Gbps total combined capacity).

The district network is protected by a next generation firewall and many applications require “allowlisting” for district devices to access outside resources. Respondent must provide a list of all URL or ports required to access their proposed solution.

Data Exchange Standards When required, the proposed solution must have efficient data exchange capabilities that can be automated to handle large volumes of data manipulation (e.g., student data). The Vendor must be able to demonstrate how data exchange in and out will be performed. This is especially important for SaaS solutions. Web Services solutions supported include:

Web Services

· SQL Server Integration Services (SSIS)

· Extensible Markup Language (XML) Transport Services

· Secure File Transfer Protocol (SFTP)

· Secure Copy (SCP)

· Secure Shell (SSH) Authentication Standards The proposed solution must use one of the following application authentication standards:

· Microsoft’s ADFS integration (ADFS 5.0)

· Google SSO solution (Oauth 2.0 or SAML) MPS prefers ADFS or Google SSO solution over AD/LDAP integration.

User Device Standards Note: The primary device for a student is a Chromebook. Applications intended for student use must be fully compatible on a Chromebook with the minimum specifications below.

Staff devices will meet the following minimum specifications:

· Windows 11 (64 bit)

· 8 GB RAM

· Intel 2nd Gen i3

· 128 GB hard drive space

· Google Chrome Browser

· Screen resolution 1024 X 768 or higher Student devices will meet the following minimum specifications:

· ChromeOS

· 4 GB RAM

· Intel Celeron

· 32 GB hard drive space Note: MPS will not support applications that require Adobe Flash, Internet Explorer, or Microsoft Silverlight, as end-of-life dates for these applications have been announced by the manufacturer(s). MPS will not adopt applications that solely run on Windows 10 OS or earlier. Windows 10 End of Life has been announced by Microsoft as October 14, 2025.

File details come from the government source that posted it. Updated .