EDU02-635610.pdf
PDF 475 KB Posted
- Attached to
- Student Portal RFQ
- Solicitation number
- BD-27-1036-EDU02-EDU02-134845
- Issued by
- Massachusetts
About this file
This Request for Quotation (RFQ) is issued by the Commonwealth of Massachusetts Executive Office of Education (EOE) on behalf of the Department of Higher Education (DHE) in coordination with the Department of Elementary and Secondary Education (DESE). The procurement seeks a qualified vendor to design, develop, implement, and support a new Student Portal that will serve as a secure, student-centered digital platform for the Commonwealth's Direct Admissions initiative. The Student Portal will enable eligible Massachusetts students to review admissions offers from participating institutions of higher education and confirm their intent to enroll through a "Claim My Spot" workflow. The minimum viable product (MVP) is targeted for pilot launch in June 2027 with a limited number of institutions and school districts. Bidders must be vendors on the statewide software contract RFR ITS81, Category 3, User Centered Design and Development. Written questions are due November 4 at 1:00 PM EST, with responses posted by November 9. Proposals are due November 13 at 1:00 PM EST. Selected bidder(s) will be notified of presentation requirements by November 20, with presentations estimated for December. Final bidder selection and negotiation are expected to occur in January.
The Commonwealth has established a not-to-exceed budget of $650,000 for the MVP scope on a fixed-price basis with payment tied to agreed delivery milestones. Bidders must propose a fixed price not exceeding this amount and complete Attachment F Cost Workbook as part of their response. The solution must be deployed and hosted within the Commonwealth's AWS infrastructure, developed using Infrastructure as Code (Terraform preferred), and maintain all source code and development assets in EOE's GitHub repository. The engagement requires expertise in product design, user experience, solution architecture, application development, systems and data integration, security, accessibility, quality assurance, and knowledge transfer. Bidders must demonstrate at least five years of experience designing and implementing custom enterprise digital solutions, with successful completion of at least three comparable implementations including at least one in AWS or comparable cloud environment, and experience with AI-assisted software development practices. The Commonwealth retains full intellectual property rights and ownership of the resulting solution, and all personnel must sign the Intellectual Property and Work Effort Agreement prior to rendering services.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Attachment C Vendor Digital Accessibility Requirements.docx | DOCX document | |
| Attachment B SOW Firm Fixed Price FFP Template.docx | DOCX document | |
| Attachment D CORI Check Requirements.docx | DOCX document | |
| Attachment E Commonwealth AI Policy.docx | DOCX document | |
| Attachment F - Cost Workbook.xlsx | XLSX spreadsheet |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
i
Commonwealth of Massachusetts Executive Office of Education
Commonwealth of Massachusetts Executive Office of Education (“EOE”)
Request for Quotation RFQ REF #EDU02-635610
COMMBUYS Bid: ####
For Department of Higher Education (“DHE”) Student Portal
THIS RFQ AND ALL RESPONSES HERETO INCLUDING THE WINNING BID SHALL
BECOME PUBLIC RECORD, AND CAN BE OBTAINED BY REQUEST FROM THIS
WEBSITE: https://www.mass.gov/topics/executive-office-of-education-public-records-requests
ANY PORTIONS OF A RESPONSE THAT ARE LABELED AS CONFIDENTIAL WILL
STILL BE CONSIDERED PUBLIC RECORD.
I. GENERAL PROCUREMENT INFORMATION
A. Department Information
Purchasing Agency: Executive Office of Education Address: 135 Santilli Highway, Everett MA Procurement Contact: EOEFISCAL@MASS.GOV RFQ Number and Title: EOE RFQ XXXXXX
This Request for Quotes (“RFQ”) does not commit the Commonwealth of Massachusetts (“Commonwealth”) or the Executive Office of Education (the “Agency”) to approve a statement of work, pay any costs incurred in the preparation of a Bidder’s response to this RFQ or to procure or contract for products or services. The Agency reserves the right to accept or reject any and all proposals received as a result of this RFQ and to contract for some, all or none of the products and services as a result of this RFQ. The Agency further reserves the right to negotiate with any or all qualified Bidders and to cancel in part or in its entirety this RFQ if it is in the best interest of the Agency or the Commonwealth to do so.
The Agency reserves the right to amend this RFQ at any time prior to the date the responses are due. Any such amendment will be posted to the Commonwealth’s procurement website, COMMBUYS (www.commbuys.com). Bidders are advised to check this site regularly, as this will be the sole method used for notification of changes.
B. Attachments o Attachment A – High-Level MVP Functional Capabilities o Attachment B – Template Statement of Work o Attachment C – Vendor Digital Accessibility Requirements o Attachment D – CORI Requirements o Attachment E – Commonwealth AI Policy o Attachment F – Cost Workbook
C. Eligible Bidders
This RFQ is restricted to vendors on the following statewide software contracts: RFR ITS81, Category 3, User Centered Design and Development.
Interested Bidders must submit their proposals through the Commonwealth’s online procurement system, COMMBUYS Bidders may contact the COMMBUYS Help Desk at commbuys@state.ma.us or call during normal business hours (8AM – 5PM, Monday – Friday) at 1-888-627-8283 or 617-720-3197 for technical assistance.
Responses must be received no later than the response due date/bid opening date and time indicated in the Event Calendar or they will not be evaluated.
D. Event Calendar All times in this RFQ are in prevailing Eastern Time.
Procurement Step Due Date Time RFQ Posted Monday Oct 26 Bidder Questions Due Wednesday
November 4 1pm EST
Commonwealth Responses posted to COMMBUYS (estimated date)
Monday November 9
RFQ Response Due Friday November
1pm EST
Selected Bidder(s) Notified of Presentation (estimated date)
Friday November
Bidder Presentations (estimated date) December Final Bidder Selection and Negotiation January
EST- Eastern Standard Time
E. Agencies
The Massachusetts Executive Office of Education (“EOE”) works with the Department of Early Education and Care (“EEC”), Children’s Trust (“CT”), the Department of Elementary and Secondary Education (“DESE”) and the Department of Higher Education (“DHE”) to connect programs and policies across the public education system.
EOE Information Technology (“EOE IT”) is responsible for the provisioning and managing of information technology systems, applications and services for DHE, DESE and EEC. In this document, “EOE” collectively refers to both EOE and EOE IT.
DHE (or “Department”) is responsible for coordinating and supporting the Commonwealth’s public higher education system, including its public universities, state universities and community colleges. DHE develops and implements policies and programs that promote access, affordability, student success and educational opportunity for Massachusetts residents.
EOE is posting this RFQ on behalf of DHE in coordination with DESE. EOE may purchase similar services for other EOE agencies under the terms of this RFQ. Any EOE agency may purchase similar services under the terms of this RFQ provided EOE has given it express written permission to do so.
II. DESCRIPTION AND PURPOSE OF PROCUREMENT
A. Background
EOE and DHE, in coordination with DESE, seek to procure services to design, develop, implement and support a new, secure, student-centered web portal that will serve as the primary digital entry point for students engaging with DHE, with an initial focus on those participating in the Commonwealth’s Direct Admissions initiative whereby students are “pre-admitted” to participating colleges and universities based on data in the possession of Commonwealth, such as their high school grade point average and other details, without filling in any application.
The Student Portal will provide eligible Massachusetts students with a streamlined and transparent experience for reviewing admissions opportunities from participating institutions of higher education and confirming their intent to enroll. By consolidating admissions offers into a single, secure platform, the Commonwealth aims to reduce barriers to college enrollment, simplify the admissions process and encourage greater participation in Massachusetts higher education.
The initial engagement will focus on delivering a Minimum Viable Product (“MVP”) targeted for a pilot launch with a limited number of institutions and school districts in June 2027. The MVP will support the Direct Admissions student experience, enabling eligible students to securely access and review their admissions opportunities, understand applicable tuition, fee and financial aid or affordability information, and indicate their intent to enroll through a “Claim My Spot” process. The MVP will also support the administrative and institutional data exchange capabilities needed to operate and oversee the program and support the exchange of enrollment information with participating schools, districts, agencies, and institutions.
The Commonwealth expects the Student Portal to evolve into a modular platform supporting additional student-facing services and workflows over time. Future capabilities may include expanded institutional integrations, financial aid and affordability tools, transcript and document management, credit transfer functionality, personalized college planning resources and other constituent services. The solution should therefore establish a maintainable and extensible foundation that can evolve as programs, policies, student needs and Commonwealth technology capabilities change.
B. Project Goals and Objectives
The purpose of this procurement is to establish an intuitive, secure, accessible and maintainable Student Portal to support the Direct Admissions experience for students, DHE and DESE, and participating schools, districts, agencies, and institutions.
The Commonwealth’s primary goals are to:
1. Simplify Student Experience: Provide students with a centralized, accessible and mobile-responsive experience through which they can securely access, understand and act upon their Direct Admissions opportunities.
2. Support Effective Direct Admissions Operations: Enable DHE to securely manage admissions information, enrollment-intent transactions, institutional data exchange, administrative functions, reporting and program oversight.
3. Establish a Scalable Student Services Platform: Create a modular and extensible foundation capable of supporting additional student-facing services following initial application and continuing throughout a student’s post-secondary education journey with reusable and configurable capabilities.
4. Promote Long-Term Commonwealth Maintainability: Minimize unnecessary custom code and proprietary dependencies so the solution can be operated, maintained and enhanced by EOE and other qualified implementation partners.
5. Accelerate Delivery Through an Iterative Approach: Use an iterative delivery approach, including AI-Driven Development Life Cycle (“AI-DLC"), to support efficient delivery while maintaining appropriate human oversight, governance, security and quality controls.
C. Description of Solution & Services
EOE and DHE, in coordination with DESE, seek a qualified vendor to serve as a collaborative product, technology and implementation partner for the Student Portal.
The selected Bidder will work with EOE, DHE, DESE, participating schools, districts, agencies, and institutions, and other stakeholders as appropriate to develop and refine requirements, design the student experience and technical solution, implement the MVP, and establish an extensible foundation for future Student Portal capabilities.
The engagement is expected to require expertise in product and service design, user experience, solution architecture, application configuration and development, systems and data integration, security and privacy, accessibility, quality assurance, deployment and knowledge transfer.
The Commonwealth has identified the required business outcomes and capabilities described in this RFQ but expects the selected Bidder to bring relevant experience, recommendations and best practices regarding how those outcomes can best be achieved.
III. STUDENT PORTAL REQUIREMENTS
A. Functionality and Business Requirements
The Student Portal MVP implementation will focus on supporting the Direct Admissions student experience and the administrative capabilities necessary for DHE, in coordination with DESE, to operate and oversee the program. The capabilities below represent the Commonwealth’s current requirements for the MVP implementation. Requirements and business rules will continue to be refined throughout the engagement as policy decisions are made and the solution is developed.
Attachment A, High-Level MVP Functional Capabilities, provides additional detail regarding the functional capabilities currently identified for the MVP and should be read together with the requirements in this section.
AI-DLC practices should be used to document and refine requirements during working sessions and rapidly produce working code for stakeholder review and validation.
The Student Portal MVP includes three primary areas of functionality: the student experience, the capabilities DHE needs to operate and oversee the portal, and data exchange with participating schools, districts, agencies, and institutions. The student portal must provide an accessible and mobile-responsive student experience. The student experience must comply with the requirements of Attachment C, Accessibility Obligations of Bidders.
The content, navigation and functionality of the Student Portal should adapt appropriately for use across mobile phones, tablets and desktop devices.
B. High Level Direct Admissions Flow (MVP)
The following diagram provides context for how the Student Portal is expected to support the Direct Admissions process. Activities occurring outside the Student Portal are included to show how information reaches and leaves the solution and do not expand the scope of the
MVP.
C. The Student Experience
1. Student Authentication and Access
Students will access the Student Portal through the Commonwealth’s MyMassGov constituent/customer identity and access management platform for people accessing Commonwealth digital services.
The solution must securely authenticate students and associate the authenticated user with the appropriate student record so that students can access admissions information specific to them.
Student Profiles Student information used in the Direct Admissions Process
Institution Eligibility Requirements
Direct Admissions eligibility requirements from participating institutions
DHE Matching Process
DHE matches student profiles to institutional eligibility requirements and produces the admissions offer file
Student Authentication
Student logs into the Student Portal using MyMassGov
Student Dashboard Student views available opportunities
Claim My Spot Student indicates their intent to enroll and intent recorded
Enrollment Intent Data Exchange
Student enrollment intent is securely transmitted to participating institutions
Foundation for the Future The solution is built to be ready to support additional services, communication channels and languages that may be added in the future
UPSTREAM INPUTS & PROCESS
STUDENT PORTAL
Admissions Offer File Processing
DHE uploads the admissions offer file for processing
DHE Operations
Student Experience
Institutional Data Exchange
DIRECT ADMISSIONS HIGH LEVEL MVP FLOW
https://www.mass.gov/orgs/mymassgov
2. Student Dashboard and Admissions Opportunities
Upon successful authentication, students must be able to view the Direct Admissions opportunities associated with their student record.
The student experience must clearly present relevant information about available opportunities, including:
• participating institutions from which the student has received a Direct Admissions offer
• Institution-specific admissions and enrollment decision-making information
• applicable tuition, fee, financial aid or affordability information
• actions available to the student for each opportunity, such as “Claim My Spot,” where applicable
Where applicable, the portal should distinguish between Direct Admissions offers and other opportunities that may require additional student action.
The Student Portal will present admissions and financial aid information provided by DHE, in coordination with DESE, and participating institutions, as applicable. The Student Portal will not independently determine admissions or financial aid eligibility as part of the initial implementation.
3. Enrollment Intent – “Claim My Spot”
Students must be able to indicate their intent to enroll at a participating institution through a “Claim My Spot” workflow.
The workflow must support confirmation or collection of the information necessary to process the student’s selection, including, as applicable:
• student contact information
• selected institution
• intended major or program
• intended enrollment / start term
• housing interest
• required acknowledgments or attestations
• student consent for DHE to transmit applicable information to the selected institution
Students must be able to review and, where permitted, update information associated with their record. Student-editable fields and fields that must remain read-only will be defined during requirements refinement based on the source and use of the information.
The Student Portal should allow students to review their selections and information before submitting their intent to enroll.
Following submission, the student must receive confirmation that their intent to enroll has been recorded and information regarding appropriate next steps.
The student must also receive a confirmation email with their selection and next steps.
Students must be able to view the history and status of their “Claim My Spot” transactions within the Student Portal. The Student Portal must record the date and time of each submission and maintain an appropriate audit trail of the transaction.
4. Student Guidance and Continuity
The Student Portal must preserve a student’s progress and saved selections across sessions so that the student can return and continue where they left off.
The Student Portal should provide clear help, explanatory content and guidance for common questions or situations.
D. DHE Operations
1. Admissions Data Management
The Student Portal must support the secure receipt and processing of admissions information provided by DHE through an admissions offer file.
The solution must support subsequent admissions offer file uploads by DHE, to update admissions information and ensure that students are presented with the most current successfully processed information.
Authorized DHE users must be able to:
• upload or otherwise provide admissions data for processing
• validate required information and identify duplicate or inconsistent records
• identify records that fail validation or cannot be processed
• view processing status and results
• review file upload and processing history, including error information
• manage processing errors and reprocess failed or corrected records as appropriate
Successfully processed admissions information must be available to the appropriate authenticated student through the Student Portal.
2. Administrative Capabilities
Authorized DHE users must have administrative capabilities necessary to operate and oversee the Student Portal and Direct Admissions process.
DHE users will be authenticated to access the backend of the portal via MyMassGov’s business tenant.
These capabilities must include, as appropriate:
• searching for and retrieving relevant student or transaction information
• viewing student enrollment-intent activity and transaction status
• managing operational issues, errors or exceptions
• initiating or reprocessing appropriate data and transaction activities
• accessing reporting and other operational information
• viewing appropriate audit information
Administrative access must be restricted to authorized users based on their roles and responsibilities.
3. Reporting and Analytics
The solution must provide reporting capabilities necessary for DHE to monitor and manage the Direct Admissions program and Student Portal operations.
The solution should provide standard reports for commonly used information, including:
• student participation and portal activity
• Direct Admissions offers
• enrollment-intent activity
• Direct Admissions activity by participating institution
• admissions data processing status
• errors and exceptions
Authorized DHE users should also be able to explore and report on available data without requiring technical development, including the ability to search, filter and query data and save commonly used views or reports for future use.
Users should be able to export report results in commonly used formats for additional analysis, as appropriate.
The reporting capabilities identified above represent the minimum requirements for the MVP. Detailed report definitions, fields and additional reporting needs will be refined with DHE during implementation.
E. Institutional Data Exchange
• The Student Portal must support the secure transmission of student enrollment-intent information to participating institutions.
• The system shall transmit enrollment intent confirmations to participating institutions using Commonwealth-approved methods. The solution should favor standardized data formats, interfaces and integration patterns that minimize institution-specific development and ongoing support, while providing flexibility to support secure APIs, CRM integration, secure file exchange or other approved methods where needed. The approach should accommodate future institutional integrations without significant redevelopment.
• The approach should support current institutional needs while allowing institutional integrations to evolve over time.
• DHE must be able to identify enrollment confirmations that fail to transmit and support appropriate reprocessing.
• The MVP should support limited access for authorized users from participating institutions to information relevant to their institution. Specific institutional roles, permissions and workflows will be defined during requirements refinement.
F. Future Student Portal Capabilities
The MVP implementation will focus on Direct Admissions. The Commonwealth expects the Student Portal to evolve over time to support additional student-facing services and workflows.
Potential future capabilities identified by DHE include:
• multilingual student experiences with initial priority languages including English, Spanish, Brazilian Portuguese, Haitian Creole and Chinese
• expanded institutional integrations
• financial aid and affordability tools
• transcript and document management
• credit transfer functionality
• personalized college planning resources
• other student-facing higher education services
• expanded student communication and notification channels
These future capabilities are provided for context and are not part of the initial implementation unless specifically identified as such.
IV. TECHNICAL AND SOLUTION REQUIREMENTS
The Commonwealth requires a modern, secure, accessible, scalable and maintainable solution that supports the MVP business capabilities and requirements identified in this RFQ while establishing a flexible foundation for future Student Portal capabilities.
EOE will provide technical and architectural oversight throughout the engagement. The selected Bidder will be expected to collaborate with EOE, DHE and other stakeholders to refine the solution architecture and ensure alignment with applicable Commonwealth enterprise standards and approved technology patterns. The selected Bidder will maintain current code in an EOE GitHub repository throughout the project and log their work in EOE’s Jira instance. If Bidders’ proprietary design and development approach prevents code or other development assets from being maintained in EOE’s GitHub repository, the Bidder must explain this in its proposal, including any limitations, dependencies, or conflicts for EOE and its express goal of owning all project deliverables.
A. Commonwealth Hosting and Enterprise Environment
The solution must align with EOE’s approved technology environment and should leverage existing EOE enterprise services, development frameworks, tooling and CI/CD capabilities where appropriate. Specifically, the Student Portal must:
• Be deployed and hosted within the Commonwealth’s AWS infrastructure.
• Be developed and maintained using Infrastructure as Code (IaC). Preference is given to Terraform, an infrastructure-as-code tool, as it aligns with the current EOE ecosystem.
• The solution must be designed to remain available during normal operating conditions and to continue operating or recover within an acceptable period following a component or infrastructure failure. Bidders must describe a proposed approach to high availability, resiliency and recovery and identify any assumptions or limitations.
• Operate in EOE’s development, testing, staging, and production environments.
• Include deployment automation and repeatable release processes where appropriate.
• Support infrastructure monitoring and operational alerting.
• Use cost effective, low maintenance infrastructure services such as containerization, serverless compute and database services.
The selected Bidder will work with EOE to define and implement the application and infrastructure architecture necessary to support the Student Portal.
B. Solution Architecture, Ownership and Maintainability
The solution must be modular, extensible and designed for long-term Commonwealth use and management. The solution must:
• Employ a modern, modular, service-oriented architecture that supports future enhancement and expansion.
• Support phased implementation of functionality through the MVP, and future releases.
• Align with EOE preferred technologies where appropriate such as Typescript/Node, React or Angular framework, REST APIs, etc.
• Provide data access using an Object Relational Mapping layer to reduce vendor lock-in storage (e.g., Sequelize or Prisma) or similar mapping layer if not using relational storage.
• Leverage cost effective solutions such as serverless technology and open-source offerings.
• Be designed to support future integrations with additional Commonwealth systems and external partners.
• Include documented application, data, integration, and infrastructure architecture.
• Allow authorized users to configure appropriate content, such as instructional and informational text and headings, without requiring code changes.
• Be browser-based and must not require users to install proprietary client software or browser plug-ins.
• Follow the Commonwealth’s Massachusetts Design System.
https://www.mass.gov/massachusetts-design-system
The Commonwealth will retain full intellectual property rights, ownership, and control of the Student Portal and its data. The vendor must provide full access to source code, configurations, data models, integration specifications, documentation and deployment materials needed to operate and enhance the solution.
Bidders should identify all third-party products, services or licenses and any dependencies or restrictions, including lifecycle costs prior to introducing them into the solution.
https://www.mass.gov/massachusetts-design-system
C. Integration and Interoperability
The solution must support secure and maintainable integration with Commonwealth systems, participating institutions and other approved external systems.
Initial integration requirements include:
• MyMassGov’s personal and business tenants for student authentication and DHE adjudication
• receipt and processing of admissions information
• transmission of student enrollment-intent information to participating institutions
MyMassGov is an established Commonwealth identity and access management service with defined integration standards and implementation guidance. Applicable MyMassGov technical documentation and integration support will be made available to the selected Bidder.
The solution should use standards-based integration approaches and favor standardized data formats, interfaces and integration patterns where practical.
The solution should support future integration with communication services for email, SMS and other potential notification channels. Future communication services should be able to provide delivery status and related information back to the Student Portal.
The integration architecture should support future integrations without any material redesign of the Student Portal.
D. AI-Driven Development Lifecycle
The selected Bidder will be expected to use an AI-DLC approach in delivering the Student Portal.
AI-enabled techniques may be used throughout requirements, design, development, testing and documentation where appropriate.
The AI-DLC approach should support rapid refinement of requirements and development of working software while maintaining traceability between requirements, implementation and testing throughout delivery.
The selected Bidder remains accountable for the quality, security, accessibility, maintainability and correctness of the work.
Any use of AI must include human review and approval, traceability, security controls and quality assurance.
Use of AI tools and services must comply with applicable Commonwealth security, privacy and data protection requirements. Use of AI tools and services must also comply with the Commonwealth’s Enterprise Use and Development of Generative AI Intelligence Policy:
https://www.mass.gov/doc/enterprise-use-and-development-of-generative-artificial-intelligence-policy-0/download
E. Security, Privacy and Data Protection
The Student Portal will process sensitive student and admissions information. Sensitive information may include student/personally identifying and contact information, education and admissions information, admissions opportunities, enrollment-intent information, financial aid or affordability information and other information necessary to support the Direct Admissions process. At a minimum, the solution must comply with all applicable state and federal information security, privacy, identity, records-management and data-protection requirements, for example but not limited to Massachusetts laws such as M.G.L. c. 93H, M.G.L. c. 66A, M.G.L. c. 93I, and the Federal Family Educational Rights and Privacy Act.
The solution and services provided under this engagement must also comply with the Commonwealth’s Enterprise Information Security Policies and Standards:
https://www.mass.gov/handbook/enterprise-information-security-policies
Security and privacy must be considered throughout solution design, development, testing, deployment and operation. The solution will protect against common web application vulnerabilities, including those identified in the OWASP Top Ten, as updated throughout the project term. The solution will support secure administrative access and generate security and audit logs sufficient for monitoring and incident investigation. The selected Bidder will support security testing, vulnerability scanning, and penetration testing prior to production deployment.
Bidders should explicitly state assumptions and requirements regarding open ports for integration in their proposals.
The solution must encrypt data in transit using TLS 1.2 or higher, with TLS 1.3 supported and preferred where technically feasible and encrypt data at rest using AES-256 or an equivalent NIST-approved cryptographic algorithm. The solution must also provide authentication and authorization, role-based access, logging and auditability, secure session management and automatic session timeout, and maintain authentication and authorization audit logs, secure integrations and protection of sensitive information. The Commonwealth's integration architecture is based on a Zero Trust security model. All API communications shall be authenticated using JSON Web Tokens (JWTs) or an equivalent standards-based token mechanism approved by the Commonwealth. Authentication and authorization shall be enforced for every API request, with no implicit trust based on network location or system identity.
The solution must support secure management of application secrets, credentials, and encryption keys.
APIs must be designed following the principle of least privilege, with each endpoint exposing only the functionality and data required to support its intended business purpose.
https://www.mass.gov/doc/enterprise-use-and-development-of-generative-artificial-intelligence-policy-0/download https://www.mass.gov/doc/enterprise-use-and-development-of-generative-artificial-intelligence-policy-0/download https://www.mass.gov/handbook/enterprise-information-security-policies
Endpoints shall be scoped to minimize the attack surface and reduce the potential impact of a compromised credential or service.
To protect against denial-of-service (DoS) and other abusive traffic patterns, APIs must support configurable rate limiting, request throttling, and other appropriate traffic management controls. The solution should provide mechanisms to detect, limit, and log excessive or anomalous API requests while maintaining availability for legitimate users.
APIs must be implemented in accordance with industry best practices, including the principles of Zero Trust Architecture as described in NIST SP 800-207, and shall employ secure authentication, authorization, and traffic management controls to protect the confidentiality, integrity, and availability of Commonwealth data and services.
The selected Bidder will be expected to collaborate with EOE on applicable security architecture reviews, testing and production-readiness requirements.
F. Accessibility and User Experience
The selected Bidder must work with EOE to ensure the Student Portal complies with the Commonwealth’s Enterprise Information Technology Accessibility Policy:
https://www.mass.gov/policy-advisory/enterprise-information-technology-accessibility-policy. Applicable accessibility testing and remediation requirements will be incorporated into any resulting contract in accordance with Attachment C, Accessibility Obligations for Bidders.
Accessibility must be incorporated throughout design, development, testing and ongoing enhancement. The Bidder must provide a solution that meets all applicable Commonwealth WCAG accessibility requirements, and bear all costs associated with remediating any accessibility deficiencies necessary to achieve or maintain compliance.
The Student Portal must support an accessible and inclusive experience across commonly supported devices and browsers. The solution should account for students with differing accessibility needs, language needs, levels of digital literacy and technology access.
G. Performance, Scalability and Operational Support
The solution must be designed to eventually support statewide use and periods of high concurrent student activity, including the potential for a significant portion of the Massachusetts high school graduating class (~80,000 students annually) to access the Student Portal within a short window. The architecture must be capable of scaling to meet increased demand without substantial redesign.
The architecture should support monitoring, logging, troubleshooting, performance management and operational visibility as Student Portal adoption and functionality expand.
The solution should minimize ongoing operational complexity and total cost of ownership.
https://www.mass.gov/policy-advisory/enterprise-information-technology-accessibility-policy https://www.mass.gov/policy-advisory/enterprise-information-technology-accessibility-policy
V. SERVICES SCOPE OF WORK
The selected Bidder will provide the services needed to refine, design, build, test, deploy and transition the Student Portal.
A. Delivery Approach
The Commonwealth expects an iterative, Agile delivery approach using AI-DLC practices.
Discovery, design, development, integration, testing and stakeholder feedback may occur concurrently. Stakeholder feedback should be incorporated throughout delivery through regular review and demonstration of working functionality, allowing requirements and the solution to be refined as the engagement progresses.
The business capabilities identified in this RFQ define the scope of the MVP. Detailed requirements, business rules, workflows and user interactions necessary to implement those capabilities will continue to be refined throughout delivery and are expected to be included within the fixed price.
B. Areas of Work
The areas of work below describe the services expected from the selected Bidder. They are not intended to prescribe sequential project phases and may occur concurrently and iteratively throughout the engagement.
1. Discovery and Requirements Refinement The selected Bidder will lead and facilitate requirements discovery and refinement with DHE, DESE, EOE and other stakeholders as appropriate throughout delivery. Activities are expected to include:
• developing and refining detailed business and functional requirements based upon the business capabilities and requirements identified in this RFQ
• refining student journeys and administrative workflows
• identifying and validating data and integration requirements
• identifying assumptions, dependencies, constraints and risks
• supporting ongoing prioritization of functionality based on business needs and the target implementation timeline
2. Product and User Experience Design The selected Bidder will design and refine the student and administrative experiences throughout delivery. Activities are expected to include:
• user research and stakeholder engagement
• student journey and workflow design
• prototyping and usability testing
• content design
• accessible and mobile-responsive design
• incorporating user and stakeholder feedback as functionality is developed
3. Solution Design and Implementation The selected Bidder will design, configure, develop and implement the Student Portal in accordance with the requirements of this RFQ and EOE’s approved technology environment.
Activities are expected to include:
• solution and application architecture
• configuration and development of student-facing functionality
• configuration and development of administrative functionality
• implementation of reporting and analytics capabilities
• use of reusable components and Commonwealth enterprise services where appropriate
• maintenance of source code and other applicable code assets in EOE-provided GitHub repositories
• documenting all infrastructure dependencies and hosting requirements.
• Other technical documentation necessary to support the solution
Solution design and implementation will occur iteratively as requirements and capabilities are refined.
4. Data and Integration The selected Bidder will design and implement the data processing and integration capabilities required for the Student Portal. Activities are expected to include:
• integration with MyMassGov
• integration with participating institutions for enrollment-intent data exchange
• receipt, validation and processing of admissions information
• management and reprocessing of data errors
• transmission of enrollment confirmations to participating institutions
• monitoring and handling of data exchange errors
• implementation of standardized data formats, interfaces and integration patterns where practical to minimize institution-specific development
5. Quality Assurance and Production Readiness
Quality assurance will occur throughout delivery. The selected Bidder will be responsible for testing and validating the solution as functionality is developed. Testing is expected to address:
• functional requirements
• data processing and integrations
• accessibility
• security
• performance
• support for user acceptance
The selected Bidder will work with DHE and EOE to address material issues and complete applicable Commonwealth reviews necessary for production deployment. Detailed testing procedures and acceptance criteria will be developed and agreed upon with DHE and EOE during the engagement.
6. Deployment, Knowledge Transfer and Transition
The selected Bidder will support deployment and transition of the Student Portal to Commonwealth operations. Activities are expected to include:
• production deployment and stabilization
• production readiness and transition planning
• documentation necessary to operate, support, maintain and enhance the solution
• appropriate user and operational documentation for DHE, participating institutions and students
• training and knowledge transfer to designated Commonwealth personnel
• transition of the solution to Commonwealth operations
Knowledge transfer should occur throughout the engagement rather than solely at the end of implementation.
C. Key Outcomes and Deliverables
At the conclusion of the engagement, the Commonwealth expects to have:
Deliverable Outcome Production-ready Student Portal A production-ready Student Portal that supports the
Direct Admissions business and functional requirements described in this RFQ and is deployed within the Commonwealth's AWS environment.
Commonwealth-Owned Solution The source code, configurations, data models, integration components, deployment artifacts and other solution materials necessary for the Commonwealth to own, operate and enhance the Student Portal.
Operational Documentation and Knowledge Transfer
Documentation and knowledge transfer sufficient for EOE to operate, support, maintain and enhance the solution without reliance on the original implementation vendor.
Future-State Roadmap A recommended roadmap for the continued evolution of the Student Portal beyond the MVP
D. High-Level Timeline, Budget, and Implementation Expectations
DHE and EOE are targeting June 2027 for implementation of the Student Portal MVP release.
The Commonwealth intends to procure the Student Portal MVP on a fixed-price basis with payment tied to agreed delivery milestones.
The Commonwealth has established a not-to-exceed budget of $650,000 for the MVP scope described in this RFQ. Bidders must propose a fixed price that does not exceed this amount.
The Commonwealth expects the work to be delivered iteratively. Requirements and solution design may be refined throughout the engagement within the business capabilities and scope described in this RFQ. Refinement of requirements within those capabilities is expected as part of the engagement and is included in the fixed price. This includes defining and refining business rules, workflows, user interactions, data fields and how the required functionality is presented to users. Changes that materially expand the business capabilities or technical scope described in this RFQ may be considered a change in scope.
E. Staffing Changes
EOE expects that the winning Bidder will manage their staffing resources and will ensure the availability of all proposed resources for the duration of the project. Any replacement resources are subject to EOE approval of the candidate’s resume and private interview, if requested. The skills of the replacement individual for any staff member who is removed from or leaves the project for any reason must match or exceed the replaced staff member in terms of skill level and experience. EOE reserves the right to address individual staff performance with the Vendor’s Project Manager or the Vendor’s executive team should the need arise during the project.
Any Vendor initiated staff replacement, or a replacement for cause, must be assigned to overlap at least two weeks with the staff member being replaced, or acceptable alternate, to provide for a smooth, effective transition/transfer. The Bidder must provide EOE with a transition plan which ensures that replacement staff receive orientation and the knowledge transfer required for their role. In the context of time and materials services, the vendor shall not invoice EOE for replacement staff for their first eighty (80) hours.
VI. BIDDER QUALIFICATIONS
The Commonwealth seeks an implementation partner with demonstrated experience delivering secure, accessible and maintainable digital solutions of comparable scale and complexity.
A. Mandatory Minimum Bidder Qualifications
• At least five years of experience designing, developing and implementing custom enterprise digital solutions.
• Successful completion of at least three comparable custom implementations involving public-facing portals, transactional applications or similar enterprise digital services, including at least one implementation in AWS or a comparable enterprise cloud environment.
• Experience using AI-assisted software development practices in enterprise application delivery.
B. Preferred Bidder Qualifications
• Experience delivering student-facing digital services or applications.
• Experience delivering custom software solutions for government, education or other public-sector organizations
VII. BIDDER RESPONSES AND EVALUATION
All bids submitted in response to this RFQ must be valid for a minimum of ninety (90) calendar days. The Bidder must provide the following as part of its response:
A. Cover Letter Bidders must submit a Cover Letter (1 page) in which the Bidder (a) expressly states that they agree to all the terms, conditions, and requirements of this RFQ, (b) certifies that it has, or can have, the qualified resources to meet the timelines stated herein; and (c) that the Commonwealth retains full ownership and control over the solution and its data. Note that
Bidders that take exception to the Commonwealth Terms and Conditions, ITS81, or the terms of this RFQ, and Bidders that propose to renegotiate such terms, may be disqualified.
Furthermore, all bidder exceptions and assumptions MUST be identified in an attachment to the cover letter, under the heading, “Exceptions and Assumptions”. Any exceptions and assumptions that are not expressly identified in this format shall be considered void and not a part of any resulting agreement.
B. Business Response
1. Solution and Delivery Approach – 6-page limit
The Bidder must describe their understanding of the Student Portal objectives and their proposed solution and delivery approach. The response must address the following:
• Describe their proposed solution and technical approach, including how it will align with the Commonwealth’s AWS environment.
• Explain where they propose to use configuration, low-code/no-code capabilities, reusable components and custom development.
• Describe how they will address data and institutional integrations.
• Describe how they will address data security (especially in the context of student data), privacy and accessibility.
• Explain how they will apply the required AI-DLC approach and iterative delivery throughout the engagement, including how they will develop and refine detailed requirements from the business capabilities identified in this RFQ and carry those requirements through design, development, testing and stakeholder validation.
• Provide examples of AI-DLC artifacts they have produced or used on prior engagements and describe how those artifacts supported delivery.
• Identify the AI-DLC tools they use, whether those tools are commercially available, open source or proprietary to the Bidder, whether they will be available to EOE during and after the engagement and any dependencies those tools may create for EOE’s ongoing maintenance of the solution.
• Describe their proposed stakeholder engagement approach, including how and when DHE, DESE, EOE, participating schools, districts, agencies, and institutions and other stakeholders will be engaged to review working functionality and provide feedback throughout delivery.
• Identify recommendations or alternative approaches that could improve outcomes, reduce cost or complexity, accelerate delivery or improve long-term maintainability.
2. High Level Solution Architecture – 2-page limit
The Bidder must provide a high-level architecture diagram and brief supporting narrative for the proposed Student Portal solution.
The Bidder must:
• Identify the major components of the proposed solution and the technologies or platforms they expect to use.
• Show the major integrations and data flows, including MyMassGov and institutional data exchange.
• Describe their proposed CI/CD approach and identify any related requirements or dependencies.
• Identify where existing Commonwealth services or reusable components are expected to be used.
• Identify any third-party products, services or licenses included in the proposed solution.
3. Implementation Approach and Timeline — 3-Page Limit
The Bidder must provide a high-level implementation approach and timeline for delivering the initial Student Portal release by June 2027.
The Bidder must:
• Identify the major milestones and anticipated timing.
• Describe how functionality will be delivered incrementally throughout the engagement.
• Identify key assumptions, dependencies and risks that could materially affect the proposed timeline or fixed price.
• Identify the involvement or decisions needed from DHE, DESE, EOE and participating schools, districts, agencies, and institutions.
• Identify any areas that could put the June 2027 target at risk.
• Describe the proposed delivery and payment milestones associated with the fixed-price implementation, with milestones tied to meaningful delivery outcomes where practical
• Describe any offered warranties, over and above the required warranties in ITS81, that may add value to your proposal.
4. Proposed Team — 3-Page Limit*
The Bidder must identify the key personnel proposed for the engagement and describe their roles and relevant experience.
The Bidder must:
• Identify each key team member and their proposed role.
• Describe each key team member’s responsibilities on the engagement.
• Summarize the experience each key team member brings that is relevant to the Student Portal.
• Describe the proposed team’s experience working together on comparable engagements, including experience using the proposed delivery approach.
• Identify any subcontractors and the work they are expected to perform.
• Describe how the proposed team will be staffed to support the engagement through the June 2027 implementation.
• Any Offshore Resources must be expressly identified with their specific city/country location
*Note: Resumes for key personnel should be provided separately and will not count toward the page limit
5. Relevant Experience — 4-Page Limit
The Bidder must provide up to three examples of comparable implementations that demonstrate their ability to successfully deliver work of similar scale and complexity.
For each example, the Bidder must:
• Identify the client and briefly describe the project.
• Describe the solution delivered and the Bidder’s role.
• Identify the implementation timeframe.
• Describe any significant challenges encountered and how they were addressed.
• Describe the results achieved.
• Indicate whether the project was completed within the planned schedule and budget and explain any material variance.
• Identify the key personnel who worked on the implementation, their roles and whether they are proposed for the Student Portal engagement.
• Provide full client reference contact information.
C. Bidder Presentation and Discussion
The Commonwealth may invite Bidders to participate in a presentation and discussion of their proposal as part of the evaluation process. The presentation should focus on demonstrating the Bidder’s relevant experience, proposed approach and ability to successfully deliver the Student Portal rather than repeating the written proposal. Bidders may be asked to:
• demonstrate a comparable student-facing or transactional solution previously delivered by the Bidder, including relevant administrative capabilities;
• demonstrate or walk through their AI-DLC approach, including the tools used, examples of artifacts produced and how requirements are translated into working code for stakeholder review;
• demonstrate how their approach supports configuration, maintainability and Commonwealth ownership of the resulting solution, including how common business or program changes could be accommodated over time;
• identify which members of the proposed team participated in the demonstrated implementation and their roles;
• discuss the proposed Student Portal solution and high-level architecture;
• discuss the implementation approach, timeline and delivery milestones, including how the Bidder will meet the June 2027 target and manage key risks and dependencies;
• respond to questions from the Commonwealth.
Key personnel proposed for the engagement should be available to participate. Bidders must use appropriately synthetic or sanitized data for demonstrations.
D. Cost Response
The Bidder must provide a fixed price for the MVP that does not exceed the Commonwealth’s $650,000 budget.
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .