Appendix F Requirements UPDATE.xlsx
XLSX spreadsheet 56 KB Posted
- Attached to
- Course Sharing System RFP
- Solicitation number
- 2024-RFP-002
- 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. SBCTC is seeking to implement a robust course sharing solution to enhance educational access and equity across the state's community and technical colleges. The solution must integrate with SBCTC's existing PeopleSoft 9.x installation, support multi-institutional setup, adhere to FERPA and accreditation regulations, and provide comprehensive reporting and management capabilities. Key requirements include fee structure configuration, data synchronization, program-specific calendars, and role-based access control. The solution must also meet accessibility standards and provide multi-level technical support.
The RFP outlines the evaluation criteria, which includes experience and qualifications, general system requirements, data and reporting capabilities, accessibility, and cybersecurity protocols. Bidders must provide a comprehensive proposal addressing these areas. Pricing is worth 10 points out of the total 100-point evaluation. The RFP does not specify any set-asides or incumbent information, but it does indicate that the solution must integrate with SBCTC's existing PeopleSoft and HighPoint Campus Experience systems.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Preproposal Teleconference information.docx | DOCX document | |
| QA Course Sharing RFP Vol 1.doc | DOC document | |
| Course Sharing SBCTC 2024-RFP-002.doc | DOC document | |
| APPENDIX B Contract.doc | DOC document | |
| Appendix F Requirements Course Sharing.xlsx | XLSX spreadsheet | |
| QA Course Sharing RFP Vol 2.doc | DOC 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 | Experience and Qualifications | |||
| Level | Requirement | Code | Comment | |
| 5.1.1 | MS | Provide a brief overview of your firm’s history of providing applications and services to support your higher education clients. Please also indicate the number of higher education clients you currently serve. If any current or former clients are comparable in size to SBCTC, please let us know. | ||
| 5.1.2 | MS | Describe your organization’s outstanding qualifications that indicate you will successfully deliver and support the required application and associated services and support. |
| 5.2 | Solution & General System Requirements | |||
| Level | Requirement | Code | Comment | |
| Proposal must contain a comprehensive description including the following elements | ||||
| 5.2.1 | MS | Integrate with existing PeopleSoft 9.x installation (30+ institutions in a single instance, pillars: CS, HCM, FCM, using Okta SAML authentication) | ||
| 5.2.2 | MS | Product integration compatible with class setup of multiple enrollment and teaching sections of the same course | ||
| 5.2.3 | MS | Product integration compatible with multi-institutional setup in PeopleSoft; including but not limited to, students PS records to remain with home instituion, fluid class search and enrollment, and begining and end of term processes | ||
| 5.2.4 | MS | Faculty Workload is calculated accurately for both enrolling and teaching institutions. | ||
| 5.2.5 | DS | Fee Structure Configuration: The system allows adminstrators to set up and modify different fee categories based on various parameters. | ||
| 5.2.6 | DS | Allowing institutions to automatically apply terms, conditions, and financial obligations agreed upon, streamlining the invoicing process for affiliated students. | ||
| 5.2.7 | MS | Data Synchronization: Implement technology to enable timely updates between home college and enrollment systems and teaching college database | ||
| 5.2.8 | MS | Vendor product allows for an increasing number of colleges, from several up to 30+, to take part in sharing courses, with no effect on non-shared courses. | ||
| 5.2.9 | MS | Adherence to FERPA, state and regional accreditation regulations concerning student enrollments and reporting. | ||
| 5.2.10 | DS | Support multiple educational programs, with different sets of courses and participating colleges. | ||
| 5.2.11 | DS | Program-specific calendars, to help consolidate different start and end dates between multiple colleges | ||
| 5.2.12 | MS | Combined sections close when total enrollments reach capacity. Manually override enrollment limits. Support Campus Solutions waitlists. | ||
| 5.2.13 | MS | Product is compatible with PeopleSoft Campus Solutions course and class coding, so that shared section details may be viewed in PeopleSoft. | ||
| 5.3 | Data, Search, and Reporting Requirements | |||
| Level | Requirement | Code | Comment | |
| Proposal must contain a comprehensive description including the following elements | ||||
| 5.3.1 | MS | Centralized Dashboard: Reporting and management of shared courses and programs across colleges | ||
| 5.3.2 | DS | Billing System: Administrators can generate reports on billing activities, payment collected, oustanding balances. | ||
| 5.3.3 | DS | Generate Reports to help colleges analyze trends and make data-driven decisions regarding course offering. | ||
| 5.3.4 | M | Search: The system should allow college admins (deans, program schedulers) to search for courses using various means, such as by course name, keywords, course codes, department, or instructors' name | ||
| 5.4 | Role Based Access and Functionality Requirements | |||
| Level | Requirement | Code | Comment | |
| Proposal must contain a comprehensive description including the following elements | ||||
| 5.4.1 | MS | Role and Permission Management: Ability to set up applications roles and permissions for specific user groups (Program Coordinators, Deans, Class schedulers) | ||
| 5.5 | Accessibility Requirements | |||
| Level | Requirement | Code | Comment | |
| Proposal must contain a comprehensive description including the following elements | ||||
| 5.5.1 | MS | Must provide a current and completed VPAT (Voluntary Product Accessibility Template) for your product to demonstrate compliance with 2.1 AA WCAG (Web Content Accessibility Guidelines) standards. Version 2.4 and no more than 12 months old, ideally. | ||
| 5.5.2 | DS | Does your organization have an individual or team focused on Accessibility conformance and usability of your product? Are they involved in the product development process and product lifecycle? | ||
| 5.5.3 | DS | If you have one, please provide a product roadmap with a timeline for accessibility improvements or fixes to known issues. | ||
| 5.5.4 | DS | Please describe the method you provide customers with for documenting/ticketing accessibility issues. | ||
| 5.5.5 | MS | Is the product compatible 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.5.6 | MS | Responsive Web UI: Management portal should perform well on various screen sizes, allowing schedule coordinators to use desktop, tablet, or smartphone browsers. | ||
| 5.5.7 | MS | Do you test on mobile devices: iOS and iPad/VoiceOver and Android/Talkback | ||
| 5.6 | Help Desk & Technician Support Requirements | |||
| Level | Requirement | Code | Comment | |
| Proposal must contain a comprehensive description including the following elements | ||||
| 5.6.1 | MS | Level 1 (Basic) Support: Vendor should specify the hours dedicated to level 1 support, ideally including a 24/7 availability framework to ensure customer issues are addressed | ||
| 5.6.2 | MS | Level 2 (Intermediate) Support: Vendor should indicate how person hours are allocated for level 2 support and whether these hours cover both standard business hours and extended availability, as well as response time commitments for high-priority issues | ||
| 5.6.3 | MS | Level 3 (Expert Support): Vendor should outline the hours allocated for level 3 support, including availability for urgent escalation and the process for accessing expert resources quickly. | ||
| 5.6.4 | MS | Reporting & Metrics: Vendor should include details how support hours are tracked, reported, and evaluated for performance improvement, as well as how metrics will be shared with clients. | ||
| 5.6.5 | MS | Vendor should outline training programs that ensure support staff are well versed in the latest technologies and customer service practices, enabling high quality support at all levels | ||
| 5.6.6 | MS | Product integration compatible with SBCTC support model for troubleshooting and testing across multiple environments during multiple phases of testing | ||
| 5.6.7 | MS | Vendor provides and maintains product design and integration documentation, general configuration guides, and training guides and provided error reports | ||
| 5.6.7 | MS | Vendor partners with SBCTC to provide long term support and troubleshooting assistance | ||
| 5.6.9 | MS | Vendor requires SBCTC to test vendor's product enhancements prior to production release to ensure changes are compatible withsystem |
| 5.7 | Integrations and Cybersecurity Requirements | |||
| Level | Requirement | Code | Comment | |
| Proposal must contain a comprehensive description including the following elements | ||||
| 5.7.1 | MS | Provide a detailed explanation of your proposed implementation process and bidirectional integration capabilities, with a focus on data mapping and transformation, API integration, error handling and logging, scalability and performance, and testing and quality assurance. | ||
| 5.7.2 | MS | Outline your cybersecurity protocols, covering data protection measures, compliance certifications, encryption standards, audit and monitoring capabilities, incident response and breach notification procedures, and adherence to industry regulations. | ||
| 5.7.3 | MS | Describe data lifecycle management, including backup frequency and retention, and how long course and enrollment info is persisted. | ||
| 5.7.4 | MS | Vendor maintains product integration compatibility with PeopleSoft Images Updates (PUMS) and PeopleTools upgrades | ||
| 5.7.5 | MS | Product integration is compatible with HighPoint Campus Experience integration without requiring a customization from HighPoint | ||
| 5.7.6 | MS | Vendor maintains product integration compatibility with HighPoint Campus Experience upgrades | ||
| 5.7.7 | MS | Transactional data follows SBCTC environment architecture URLs (i.e. testing in a lower environment doesn't impact production) |
Points Summary
| List of all requirement areas | Points | |
| 5.1 | Experience and Qualifications | 5 |
| 5.2 | Solution & General System Requirements | 20 |
| 5.3 | Data, Search, and Reporting Requirements | 20 |
| 5.4 | Role Based Access and Functionality Requirements | 5 |
| 5.5 | Accessibility | 10 |
| 5.6 | Help Desk & Technician Support Requirements | 10 |
| 5.7 | Integrations & Cyber Security Requirements | 20 |
| 6.5 | Price | 10 |
| Total | 100 |
File details come from the government source that posted it. Updated .