Appendix F Requirements.xlsx
XLSX spreadsheet 70 KB Posted
- Attached to
- Student Success Software Solution RFP
- Solicitation number
- 2024-RFP-001
- Issued by
- Adams County, Asotin County, Benton County, Chelan County, Clallam County, Clark County, Columbia County, Cowlitz County, Douglas County, Ferry County, Franklin County, Garfield County, Grant County, Grays Harbor County, Island County, Jefferson County, King County, Kitsap County, Kittitas County, Klickitat County, Lewis County, Lincoln County, Mason County, Okanogan County, Pacific County, Pend Oreille County, Pierce County, San Juan County, Skagit County, Skamania County, Snohomish County, Spokane County, Stevens County, Thurston County, Wahkiakum County, Walla Walla County, Whatcom County, Whitman County, Yakima County, Asotin City, Clarkston City, Clarkston Heights-Vineland CDP, West Clarkston-Highland CDP, Benton City, Chelan City, Chelan Falls CDP, Clallam Bay CDP, Lewisville CDP, Rock Island City, Pacific Beach CDP, Whidbey Island Station CDP, Mercer Island City, Pacific City, Bainbridge Island City, Kingston CDP, Kitsap Lake CDP, Kittitas City, Klickitat CDP, Okanogan City, Anderson Island CDP, Fort Lewis CDP, Fox Island CDP, Herron Island CDP, Ketron Island CDP, North Fort Lewis CDP, Raft Island CDP, Stevenson City, Hat Island CDP, Lake Stevens City, Snohomish City, Spokane City, Spokane Valley City, Puget Island CDP, Garfield Town, Yakima City, Washington
About this file
This document is a Request for Proposal (RFP) issued by the State Board for Community and Technical Colleges (SBCTC) in Washington state, seeking a student success software solution to enhance and support academic progress, planning, and achievement. The solution should provide insights into disaggregated student performance, engagement, and behavior, allowing for interventions and support. The RFP covers detailed functional and technical requirements across areas such as student goal planning and progress, communication, case management, accessibility and equity, data and analytics, technology integration, and client support. The RFP is open to all 34 community and technical colleges within the SBCTC system, with an anticipated contract term of multiple years.
The RFP outlines specific pricing requirements, including the need for the vendor to provide detailed cost information for the proposed solution. Additionally, the RFP emphasizes the importance of accessibility and equity, requiring the vendor to demonstrate compliance with industry standards and provide examples of how the solution supports equitable practices for diverse student populations.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| APPENDIX B Contract.doc | DOC document | |
| Preproposal Teleconference information.docx | DOCX document | |
| QA Student Success RFP Vol 1.doc | DOC document | |
| SBCTC 2024-RFP-001 Student Success.doc | DOC document | |
| SBCTC 2024-RFP-001 UPDATE.doc | DOC document | |
| Sole_Source_Notification_20250280.pdf | ||
| Accessibility Rubric.docx | DOCX document |
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
Bidder Instructions
| Response Instructions to Scored Requirements | ||
| This section of the RFP contains requirements for the solution desired by SBCTC. In responding to the requirements located in the spreadsheet tabs labeled, the following codes must be used, where applicable. | ||
| Please use the appropriate response code listed below in the "Code" column for each of the requirements. | ||
| Bidder must not alter, modify, insert or delete any part of the spreadsheets other than providing Bidder's response as per the instructions detailed below. Failure to comply may result in disqualification of the proposal. | ||
| Response to Requirement | Code | Definition and Criteria |
| Yes | Y | Functional capability exists (out-of-the-box). Requirement is installed and operational at other sites and can be demonstrated to SBCTC. |
| Configuration | C | Requirement will be met through changes to the existing solution using built-in tools to perform the specific function. |
Note: In the Comments column next to this response, indicate estimated level of complexity (Simple, Medium or Complex) Modification M Requirement will be met through changes to the source code which would require analysis and re-application during updates, upgrades, or when applying software patches.
Note: In the Comments column next to this response, indicate estimated level of complexity (Simple, Medium or Complex) Supplied by 3rd Party (Embedded) 3E Requirement is met or provided by third-party software package. License fees for this software are included in this proposal. Capability is fully embedded in and does not require maintenance of the integration with the core package. Functionality to meet this requirement is installed and operational at other sites and can be demonstrated to the organization.
Note: In the Comments column, indicate the name of the proposed third-party software package.
Supplied by Third Party (Non-Embedded) 3 Requirement is met or provided by third-party software package. License fees for this software are included in this proposal. Capability is “bolt-on” and will require maintenance of the integration with the core package as well as future updates, upgrades, or software patches to the 3rd party component. Functionality to meet this requirement is installed and operational at other sites and can be demonstrated to the organization.
Note: In the Comments column, indicate the name of the proposed third-party software package.
Future F Requirement will be met by the solution that is currently under development, in Beta test, or not yet released.
Note: In the Comments column next to this response, indicate the date when requirement will be available for implementation.
| No | N | Requirement will not be provided. |
| Note: | ||
| 1. An omitted response will be assumed to be the same as a response code of “N”. | ||
| 2. Any deviation from the response codes will be re-coded at the discretion of SBCTC. |
&14ERP Functional Requirements - Student Version &D
&9CONFIDENTIAL - For SBCTC Use Only &9Appendix A5 - Functional Requirements Student__Page &P of &N &9&A
Score Sheet
| Functional Requirements | ||||
| 5.1 | Student Goal Planning & Progress | |||
| Level | Requirement | Code | Comment | |
| 5.1.1 | Degree & Certificate Planning - Describe your proposed solution's ability to do the following: | |||
| 5.1.1.1 | MS | Describe the integration of your solution with the ctcLink Academic Advising Reports (AARs) and class schedules. | ||
| 5.1.1.2 | MS | Describe how your solution will allow for planning from Basic Education for Adults (BEDA) to graduation, including both credential and non-credential students. | ||
| 5.1.1.3 | MS | Describe how you account for multiple measures placement data in your solution. | ||
| 5.1.1.4 | MS | Describe how your solution includes or takes into account transfer credits | ||
| 5.1.1.5 | MS | Describe how your solution works with students who don’t have an Academic Advising Report (AAR), such as those in Basic Education for Adults (BEDA) or job skills upgrade programs. | ||
| 5.1.1.6 | MS | Show how your solution enables students to view their plan autonomously. | ||
| 5.1.1.7 | M | Describe how your solution allows students to view and save "what if" plans for alternate programs of study | ||
| 5.1.1.8 | MS | Describe how your solution allows students to save mulitple plans simultaneously. | ||
| 5.1.1.9 | MS | Describe how your tool supports service requests, such as formal program changes, and the level of customization available. | ||
| 5.1.1.10 | MS | Describe how your solution must allow faculty and staff to view student plans. | ||
| 5.1.2 | Degree & Certificate Audit: Describe your proposed solution's ability to do the following: | |||
| 5.1.2.1 | MS | Solution must allow students to view their degree or certificate audit independently. | ||
| 5.1.2.2 | MS | Solution must allow faculty and staff to view degree and certificate audits. | ||
| 5.1.3 | Career & Transfer Planning: Describe your proposed solution's ability to do the following: | |||
| 5.1.3.1 | DS | Solution must provide reminders to students when it is time to apply for transfer. | ||
| 5.1.3.2 | DS | Solution must inform students about their career options based on their program of study | ||
| 5.1.3.3 | DS | Solution must inform students about their transfer options based on their program of study | ||
| 5.1.4 | Support for Student Engagement & Connection to Campus Resources: Describe your proposed solution's ability to do the following: | |||
| 5.1.4.1 | MS | Describe how solution connects students to their assigned advisors and faculty. | ||
| 5.1.4.2 | MS | Describe how your solution allows staff to refer students to other resources. | ||
| 5.1.4.3 | M | Solution must remind students about important dates. | ||
| 5.1.4.4 | MS | Solution must allow teams of staff to be assigned to a student. | ||
| 5.1.4.5 | M | Describe self-service functionalities that empower students to autonomously mange appropriate aspects of the educational journey. | ||
| 5.1.4.6 | MS | Describe your solution's ability to notify students of warnings like Satisfactory Academic Progress (SAP) or other funding impacts based on course choices. | ||
| 5.1.5 | Reporting & Intervention: Describe your solution's ability to do the following: | |||
| 5.1.5.1 | MS | Solution must inform students and relevant staff if students are “off track” with their plan. | ||
| 5.1.5.2 | DS | Describe your solution's ability to manage manual overrides, such as prerequisite requirements, including how these are documented and tracked. | ||
| 5.1.5.3 | DS | Describe your solution's ability to allow the college to review student plans to inform the development of next year’s annual class schedule. | ||
| 5.1.5.4 | DS | Describe how your solution tracks which students are in specific meta-majors, especially within Direct Transfer Agreements (DTAs). | ||
| 5.1.6 | Automated Student Registration into ctcLink: Describe your proposed solution's ability to do the following: | |||
| 5.1.6.1 | DS | Describe how your solution enables students to register for courses directly from their degree or certificate plan. | ||
| 5.1.6.2 | DS | Describe how your solution allows students to register for courses for multiple terms simultaneously. | ||
| 5.2 | Communication | |||
| Code | Requirement | Code | Comment | |
| Proposal must contain a comprehensive description including the following elements | ||||
| 5.2.1 | Automated & Schedulable Communications | |||
| 5.2.1.1 | MS | Describe your process for creating automated and scheduled communications. (include details on creating individual ad hoc communications) | ||
| 5.2.1.2 | MS | Describe the solution's ability to customize the content, timing, and triggers for automated communications. | ||
| 5.2.1.3 | MS | Explain how to set up communication triggers based on student activity. | ||
| 5.2.2 | Campaigns & Selective Group Communications | |||
| 5.2.2.1 | MS | Describe your solution's ability to identify specific populations/cohorts of students for communication campaigns (e.g., using service indicators, student coding, programs/majors, demographic information, etc.). | ||
| 5.2.2.2 | MS | Describe your solution's ability to assign campaigns to specific employees and teams of employees. | ||
| 5.2.2.3 | MS | Describe how your solution ensures that features are in place to securely handle student data and deliver communications in accordance with privacy standards. | ||
| 5.2.2.4 | MS | Describe the solution's capability to track the success of campaigns. | ||
| 5.2.3 | MS | Differentiated User Level Access - Describe how your solution provides different levels of access to different employee classifications (e.g advisors, faculty, financial aid staff, disability services staff, etc.) | ||
| 5.2.4 | Communication Modalities & Preferences: Describe your proposed solution's abilities in the following areas: | |||
| 5.2.4.1 | MS | Describe how your solution allows students to select their preferred method of communication. (please clarify if this forces the college to only use the preferred method of communication) | ||
| 5.2.4.2 | MS | Please specify if your solution's texting platform/functionality is build into your tool or dependent upon a third party. Please provide details of how this is set up, explaining security and if any additional costs are included. All related costs must be stated and any direct to college costs must be included in your price proposal and student costs must be identified in this section as well. | ||
| 5.2.4.3 | MS | Describe how your solution supports two-way communication, allowing students to respond and engage in back-and-forth interactions with employeeds via the platform. | ||
| 5.2.5 | 4 | |||
| 5.2.5.1 | MS | Describe any differences between information available on the desktop version of your solution and the mobile version. | ||
| 5.2.5.2 | MS | Describe any limitations on the mobile version of your solution for students. Please identify any costs to students for using the mobile version of the solution (if any). | ||
| 5.2.5.3 | MS | Describe any limitations on the mobile version of your solution for employees. | ||
| 5.2.5.4 | MS | Please specify if the mobile version of the solution is an app, web-based, or other (e.g., both). | ||
| 5.2.5.5 | MS | Describe your solution's ability to push notifications to mobile devices (e.g., alerts, new note/communication, appointment reminder, etc.) | ||
| 5.3 | Case Management Tool | |||
| Code | Requirement | Code | Comment | |
| Proposal must contain a comprehensive description including the following elements | ||||
| 5.3.1 | Advising Notes: Describe your proposed solution's ability to do the following: | |||
| 5.3.1.1 | MS | Please specify how long records are maintained for students and staff. Provide details about data retention policies as opposed to advising. Provide details about record visibility and retention, including any related costs (related costs must be stated in your pricing proposal). | ||
| 5.3.1.2 | MS | Describe how advising notes are collected, stored, retained, and protected. | ||
| 5.3.1.3 | MS | Explain whether or not note templates are available for quick note-taking. | ||
| 5.3.1.4 | MS | Describe your solution's ability to allow colleges to create their own note templates, if available. | ||
| 5.3.1.5 | MS | Describe the student's ability to see the notes about their experiences, including notes taken by advisors during advising sessions. | ||
| 5.3.1.6 | MS | Describe in detail how to assign visibility of notes in the employee interface. | ||
| 5.3.2 | Student Data Access: | |||
| 5.3.2.1 | MS | Describe how your proposed solution provides different levels of access to different employee classifications (e.g. advisors, faculty, financial aid staff, disability services staff, etc.) | ||
| 5.3.2.2 | MS | Describe your access control model around a student's record | ||
| 5.3.2.3 | MS | Describe your solution's ability to assign caseloads to employees and teams of employees, including how caseloads are viewed and managed. | ||
| 5.3.2.4 | MS | Describe how data for students dually enrolled at more than one campus is pushed to the correct location, including how notes, flags, and enrollments will occur without data conflicts or the need for manual overrides. | ||
| 5.3.2.5 | MS | Identify any anticipated impact to dually enrolled students, given a rolling implementation process where campuses will adopt the platform at different times. | ||
| 5.3.3 | Scheduling | |||
| 5.3.3.1 | MS | Describe how your solution manages scheduling appointments from the student interface. | ||
| 5.3.3.2 | MS | Describe how your solution manages scheduling appointments from the employee interface. | ||
| 5.3.3.3 | MS | Explain how your solution manages scheduling drop-in appointments. | ||
| 5.3.3.4 | MS | Describe your solution's ability to schedule group advising sessions. | ||
| 5.3.3.5 | MS | Describe how your solution allows students to see past and future appointment dates. | ||
| 5.3.3.6 | MS | Describe how your technology integrates with other platforms for calendaring and scheduling. | ||
| 5.3.4 | Dashboards | |||
| 5.3.4.1 | MS | Describe your solution's capacity to customize dashboards from a college’s perspective. | ||
| 5.3.4.2 | MS | Describe your solution's capacity to customize dashboards from the student perspective. | ||
| 5.3.4.3 | MS | Provide a list of the specific information available on the student dashboard. | ||
| 5.3.4.4 | MS | Provide a list of the specific information available on the employee dashboard. | ||
| 5.3.4.5 | M | Provide a description of any information available on the desktop dashboard that isn’t on the mobile site. | ||
| 5.3.4.6 | M | Describe your solution's ability to allow employees to easily see what the student sees on the student’s dashboards and replicate the student view. | ||
| 5.3.5 | Caseload Management | |||
| 5.3.5.1 | MS | Describe how preferred names, pronouns, and legal names are stored and tracked. | ||
| 5.3.5.2 | DS | Explain your solution's ability to help balance advisors’ workload. | ||
| 5.3.5.3 | MS | Describe how your solution allows advisors to create action plans and manage timelines for students. | ||
| 5.3.5.4 | MS | Describe how your solution enables filtering, categorizing, and prioritizing students based on specific criteria (e.g., risk level, program). | ||
| 5.3.5.5 | MS | Describe the process of assigning employees (including faculty, staff, care teams, etc.) to students. | ||
| 5.3.5.6 | MS | Describe your solution's process to batch assign, batch re-assign, and batch un-assign students to advisors, including one-at-a-time assignments. | ||
| 5.3.5.7 | MS | Describe your solution's ability to enable automatic assignment of groups of students from ctcLink. If it requires additional effort and cost, please explain and include those costs in the pricing proposal. | ||
| 5.3.5.8 | MS | Describe how records are maintained for accounts that are no longer active, including pricing implications. | ||
| 5.3.6 | Early Alert | |||
| 5.3.6.1 | MS | Provide an overview of how your solution supports early alert for students and advisors. | ||
| 5.3.6.2 | MS | Explain how communication between employees and students is facilitated once an alert has been triggered. | ||
| 5.3.6.3 | MS | Describe your solution's ability to customize and automate early alert notifications | ||
| 5.4 | Accessbility & Equity | |||
| Code | Requirement | Code | Comment | |
| Proposal must contain a comprehensive description including the following elements | ||||
| 5.4.1 | Information and Documentation | |||
| 5.4.1.1 | M | Please provide any publicly available statement you have regarding accessibility | ||
| 5.4.1.2 | MS | Provide the accessibility compliance documentation identified in RFP Section 4.11 | ||
| 5.4.1.3 | DS | Provide testimonials containing concrete examples of how the tools has been used to support equity or equitable practices. Include evidence of how the tools has supported first generation college students, specifically. | ||
| 5.4.2 | Accessbility Conformance | |||
| 5.4.2.1 | MS | Describe how the solution includes accessibility in the design of included products. | ||
| 5.4.2.2 | MS | Describe how the solution complies with industry standards based on the documentation provided | ||
| 5.4.2.3 | MS | Describe how your solution integrates accessibility testing into the product management process, including any manual and/or automated testing | ||
| 5.4.2.4 | MS | Describe your solution's compatibility with commonly used assistive technology products (e.g., JAWS, NVDA, VoiceOver, ZoomText, Dragon Naturally Speaking). Describe the process you use to evaluate such compatibility, including any manual testing that is done with assistive technology devices. | ||
| 5.4.2.5 | MS | Please describe the method you provide customers with for documenting/ticketing accessibility issues. | ||
| 5.4.3 | Alternatives and Accomodations | |||
| 5.4.3.1 | M | Provide guidance or suggestions for alternatives or workarounds to address known accessibility gaps. | ||
| 5.4.3.2 | M | Share any documented roadmap for accessibility improvements and enhancements (i.e., how you will address existing accessibility gaps). | ||
| 5.4.4 | Compliance with WCAG 2.1AA standards: Please describe how your proposed solution performs the following: | |||
| 5.4.4.1 | MS | Ensure all menus, links, buttons, and other controls can be operated by keyboard, making them accessible to users who are unable to use a mouse. | ||
| 5.4.4.2 | MS | Use well-defined keyboard visual focus on all pages. | ||
| 5.4.4.3 | MS | Allow text to be resized up to 200% without losing clarity or impeding navigation. | ||
| 5.4.4.4 | MS | Use sufficient color contrast. | ||
| 5.4.4.5 | MS | Properly label all form fields. | ||
| 5.4.4.6 | MS | Make pop-ups such as menus, dialogs, and tooltips accessible. | ||
| 5.4.4.7 | MS | Include mechanisms for adjusting time limits on pages for users who need more time. | ||
| 5.4.5 | Equity | |||
| 5.4.5.1 | M | Describe how your tool supports multiple languages. | ||
| 5.4.5.2 | M | Highlight your company’s commitment to social and racial equity in product design and development. Provide any relevant artifacts. | ||
| 5.4.5.3 | MS | Specify the available fields and display options for names and pronouns. | ||
| 5.4.5.4 | M | Please provide your company's publicly available diversity/equity statement. Provide the statement as an artifact. | ||
| 5.4.5.5 | MS | Describe how the product supports receiving, retaining, changing (particularly by students), reporting, and managing access to student demographic and identity information (e.g., race, ethnicity, gender, sexual orientation, SES, etc.). | ||
| 5.4.5.6 | MS | Describe any limitations in how demographics and identities are incorporated (e.g., general demographics rather than specific such as “Asian,” inability for a student to change identity within the system, missing demographic fields, etc.). | ||
| 5.5 | Data & Analytics | |||
| Code | Requirement | Code | Comment | |
| Proposal must contain a comprehensive description including the following elements | ||||
| 5.5.1 | MS | Data Synchronization: Describe how, and how often, the data within the solution will synchronize with ctcLink. Include details on data storage and security protocols. | ||
| 5.5.2 | MS | User Security Roles: Describe how the solution defines user security roles and allows colleges to assign those roles. | ||
| 5.5.3 | M | System-Generated Alerts: Describe how users can create parameters/markers for solution-generated alerts and how the solution delivers those alerts. | ||
| 5.5.4 | DS | Predictive Models: Describe how the solution develops predictive models and their typical use cases. Include how these will be made transparent to the colleges and the extent to which they are customizable. | ||
| 5.5.5 | MS | Reporting: Describe the types of built-in reports that come with the solution and the ability to create ad hoc reports. | ||
| 5.5.6 | MS | Event Tracking: Describe the solution's capacity to track attendance at live events, such as class or event attendance or appointments. | ||
| 5.5.7 | M | Artificial Intelligence: Describe where the solution uses AI. | ||
| 5.6 | Technology Integration | |||
| Code | Requirement | Code | Comment | |
| Proposal must contain a comprehensive description including the following elements | ||||
| 5.6.1 | Data Synchronization | |||
| 5.6.1.1 | MS | Describe how your proposed solution ensures real-time or near real-time data synchronization between PeopleSoft and the vendor’s system. | ||
| 5.6.1.2 | MS | Describe your solution's ability to support both push (PeopleSoft to vendor) and pull (vendor to PeopleSoft) data operations. Explain the differences between push and pull operations. Describe how synchronization between instances is managed and the flexibility in synchronization. Specify the frequency of synchronization and the capacity to address real-time synchronization in addition to scheduled synchronization (e.g., twice a day). | ||
| 5.6.2 | Data Mapping & Transformation | |||
| 5.6.2.1 | MS | Describe your solution's ability to map PeopleSoft data fields to the corresponding fields in your proposed solution. | ||
| 5.6.2.2 | MS | Describe how your proposed solution will implement data transformation rules to ensure compatibility between different data formats and structures. | ||
| 5.6.3 | API Integration | |||
| 5.6.3.1 | M | Describe your solution's ability to use PeopleSoft Integration Broker for handling web services (SOAP/REST APIs). | ||
| 5.6.3.2 | MS | Descrive how your solution supports standard APIs for integration. | ||
| 5.6.3.3 | MS | Describe your solution's ability to provide secure API endpoints with proper authentication and authorization mechanisms. | ||
| 5.6.4 | Error Handling & Logging | |||
| 5.6.4.1 | MS | Describe how your proposed solution implements comprehensive error handling mechanisms to capture and report integration errors. | ||
| 5.6.4.2 | MS | Describe your solution's ability to provide detailed logging of integration transactions for auditing and troubleshooting purposes. | ||
| 5.6.5 | Security & Compliance | |||
| 5.6.5.1 | MS | Provide documentation of your solution's compliance and your organization's certifications in: ISO/IEC 27001 Certification, SOC 2 Type II Certification, PCI-DSS Compliance, GDPR Compliance, Other relevant certificatoins (e.g. HIPPA, FERPA, GLBA) | ||
| 5.6.5.2 | MS | Describe how your proposed solution ensures data encryption during transmission (SSL/TLS). | ||
| 5.6.5.3 | MS | Describe your solution's implementation of role-based access control to ensure only authorized users can access or modify data. | ||
| 5.6.5.4 | MS | Describe your organization's and the proposed solution's security practices in the areas of: Principle of Least Privilege Implementation, Third-Party Security Management, Configuration Management Process, and Regular Security Audits. | ||
| 5.6.5.5 | M | Audit & Monitoring: Describe how your organization and the proposed solution address: Continuous Monitoring , Right to Conduct Surprise Audits, Audit Report Availability. | ||
| 5.6.5.6 | MS | Describe your solution's Confidential Information Protection Measures and Data Privacy Compliance (e.g. CCPA, GDPR) | ||
| 5.6.5.7 | MS | Describe your proposed solution's Incident Response, Incident Reporting, and Breach Notification Processes | ||
| 5.6.5.8 | M | Describe the level of Cyber Liability Insurance Coverage and Errors and Omissions Insurance Coverage your Organization carries or will carry for the implementation of your proposed solution. | ||
| 5.6.6 | Batch Processing | |||
| 5.6.6.1 | MS | Describe how your proposed solution supports batch processing of data for scenarios where real-time integration is not feasible. | ||
| 5.6.6.2 | MS | Describe how your solution will enable scheduling and monitoring of batch jobs. | ||
| 5.6.7 | Data Validation | |||
| 5.6.7.1 | MS | Describe your proposed solution's ability to implement validation rules to ensure data integrity and consistency before transmission. | ||
| 5.6.7.2 | MS | Describe your solution's ability to handle rejections for invalid data entries. | ||
| 5.6.8 | User Interface (UI) | |||
| 5.6.8.1 | MS | Describe your solution's administrative UI for configuring and monitoring integration settings. | ||
| 5.6.8.2 | MS | Describe your solution's included dashboards and reports for real-time status updates and performance metrics. | ||
| 5.6.9 | Scalability & Performance | |||
| 5.6.9.1 | MS | Describe your solution's ability to handle large volumes of data and high transaction rates. Include examples of how the solution has functioned during high volume episodes, such as registration periods. | ||
| 5.6.9.2 | MS | Describe how your solution will optimize performance to ensure minimal impact on PeopleSoft performance. | ||
| 5.6.10 | Testing & Quality Assurance | |||
| 5.6.10.1 | MS | Describe your proposed process for comprehensive testing (unit, integration, and end-to-end testing). | ||
| 5.6.10.2 | MS | Describe your solution's available sandbox environments for testing and validation before production deployment. | ||
| 5.6.11 | Support & Maintenance | |||
| 5.6.11.1 | MS | Describe your organization's ongoing support for integration issues and enhancements. | ||
| 5.6.11.2 | MS | Describe how your organization plans to regularly update and patch the solution to address security vulnerabilities and improve functionality. | ||
| 5.7 | Client Support | |||
| Code | Requirement | Code | Comment | |
| Proposal must contain a comprehensive description including the following elements | ||||
| 5.7.1 | MS | Implementation Support: Describe how your organization will ensure accurate implementation with thorough User Acceptance Testing (UAT) at the college level and obtain sign-off for accuracy, particularly during the first two years of implementation. Include proactive strategies that will be used for supporting colleges that onboard beyond the initial two-year window. | ||
| 5.7.2 | MS | Project Management: Describe your organization’s plan to utilize a robust project management methodology to facilitate implementation, regular system updates, and effective onboarding training. Demonstrate experience with managing implementation at or beyond the scale of 34 colleges, including lessons learned and recommended approaches for effective change management. | ||
| 5.7.3 | Training Support | |||
| 5.7.3.1 | MS | Describe your built-in end user training in plain language, catering to various user groups with different digital literacy skills. Describe your process for collaborating with college site leads to ensure effective and accessible training materials and delivery. | ||
| 5.7.3.2 | MS | Describe how you offer training materials in multiple formats (e.g., text, video, and other formats) with Closed Captioning, ensuring usability by all colleges. | ||
| 5.7.4 | MS | Customer Service Support: Describe how you maintain a responsive service desk for addressing functional issues through service tickets and your average time to resolution.. Describe how your solution enables institutions to see tickets that have been submitted. Describe how your solution provides administrator access to admin systems at various levels and explain how this is managed. | ||
| 5.7.5 | MS | Ongoing Technical Support: Describe how you provide continuous support for both students and staff. Clarify who has access to information in the system and how different levels of access are established. Describe how your proposed solution allows system administrators to view the system through the lens of the user to diagnose and resolve issues (impersonating other users). Explain the protocol for staff access, specifically. | ||
| 5.7.6 | MS | Ease of Navigation: Describe usability or ease of navigation for all users, including examples of where improvements have been implemented to streamline navigation. Describe your system improvement timeline and process, including any protocols for community informed product changes. |
Points Summary
| List of all requirement areas | Points | |
| 5.1 | Student Goal Planning & Progress | 130 |
| 5.2 | Communication | 120 |
| 5.3 | Case Management Tool | 135 |
| 5.4 | Accessibility & Equity | 130 |
| 5.5 | Data & Analytics | 110 |
| 5.6 | Technology Integration | 115 |
| 5.7 | Client Support | 120 |
| 6.5 | Price | 140 |
| Total | 1000 |
File details come from the government source that posted it. Updated .