APPENDIX A - CAREER COACH REQUIREMENTS FINAL.xlsx
XLSX spreadsheet 33 KB Posted
- Attached to
- 9280-26-R-IFBD-00036
- Solicitation number
- 3160007941
- Issued by
- Greene County, Mississippi
About this file
This is an Appendix A requirements document for a career coaching platform solicitation by the University of Southern Mississippi. The University is seeking a vendor to provide a comprehensive, cloud-based career exploration and job matching system under a three-year contract with a sealed bid deadline of Monday, March 6, 2026, at 2:00 p.m. The requested platform must include an interest-based career exploration tool that guides students through skills inventories and matches them to career pathways and degree programs, local labor market insights linked to academic offerings, and career pages displaying wages, job openings, employment data, and ten-year projections. The solution must feature program-to-career mapping utilizing CIP to O*NET crosswalks, an exportable resume builder aligned with in-demand skills, and integrated widgets for degree program pages. Additionally, the vendor must provide continuous implementation and post-implementation support with remote assistance, documented onboarding plans with timelines, and 24/7/365 technical support for critical incidents with defined escalation procedures.
The system must be a hosted, cloud-based, multi-tenant solution with automatic monthly updates for job postings and quarterly updates for regional labor market information, requiring no manual data refreshes. Security and compliance requirements include LDAP, SAML, Active Directory, or Shibboleth integration; granular role-based access controls; encryption at rest; multi-factor authentication; SSO for admin users; audit trails and logging; and compliance with GDPR and all state and federal privacy laws. The vendor must provide three higher education references, maintain disaster recovery with nightly backups and 24-hour restoration capabilities, support concurrent user scalability without restrictions, and report any data breaches to USM's Technology Security Officer within 72 hours per Mississippi Data Breach Law and GDPR requirements. All data entered into the system remains the sole property of the University, which must not be used or disclosed without written permission, and the vendor must provide a mechanism for returning all data in a non-proprietary format compatible with relational database systems upon contract termination.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| RFP-CAREER COACH SOLUTION FINAL.pdf | ||
| USM BID 26-34 LEGAL AD.pdf |
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
Sheet1
| Identifier | Required/Optional | General Requirements | Yes/No | Details (Explanations/Notes (May also be attached to document. Must reference Requirement ID#) |
| 1 | R | The vendor must provide a 3-year contract | ||
| 2 | R | Must offer interest-based career exploration tool to guide students in interest and skills based inventories and then matches them to potential career pathways and degree programs | ||
| 3 | R | Must provide local labor market insights and link to academic programs at the institution | ||
| 4 | R | Must include career pages displaying local wages, job openings, current employment, and 10-year projections | ||
| 5 | R | Career pages must include required education, in-demand skills, job postings, and live local job data of median salaries | ||
| 6 | R | Must provide program-to-career mapping utilizing the CIP to O*NET crosswalk | ||
| 7 | R | Must provide a resume builder aligned with in-demand skills and produces exportable resume | ||
| 8 | R | Must include widget application to be integrated on degree program pages featuring the program-to-career mapping , based on CIP to SOC crosswalk. | ||
| 9 | R | Widgets and platform must automatically refresh data without manual updates | ||
| 10 | R | Must provide continuous support for the implementation and post-implementation of the product | ||
| 11 | R | Labor-market and skills data must be automatically updated at least monthly (postings) and quarterly (regional LMI) | ||
| 12 | R | Must include documentation on taxonomies, mappings, and any modeling methods | ||
| 13 | R | Must offer the ability for vetted employers to post opportunities to relevant career pages and receive resumes | ||
| Vendor Requirements | ||||
| 14 | R | Vendor must provide 3 higher‑ed references | ||
| 15 | R | The vendor must provide 24x7x365 technical support for critical incidents, with defined escalation procedures. | ||
| 16 | O | The vendor should provide a dedicated technical account manager or customer success manager for the duration of the contract | ||
| Implementation Requirements | ||||
| 17 | R | Must provide remote implementation support | ||
| 18 | R | The vendor must provide a documented implementation and onboarding plan, including estimated timelines and required university resources | ||
| Disaster Recovery Requirements | ||||
| 19 | R | hosted solution must have in place a system recovery plan, including policies around nightly backups and restoration and recovery of data within 24 hours of an outage or request | ||
| Security and Access Control Requirements | ||||
| 20 | R | the solution must allow secure login leveraging LDAP, SAML, Active Directory or Shibboleth security integration and determine level of access via identified fields within LDAP | ||
| 21 | R | the solution must allow for granular Role based control of access to profile data and workflows; including full access, limited access, and view only access; based on user | ||
| 22 | R | the solution must allow the administrator to assign security roles to users | ||
| 23 | R | system must provide logging of user management, administrative activity, and of user activity | ||
| 24 | R | the solution must allow the university admistrator to view user data on system use, (logins, uploads, modifications, etc) | ||
| 25 | R | if the system is doing any authentication, it must not use or provide default credentials | ||
| 26 | R | must be a hosted cloud based solution | ||
| 27 | R | user accounts must be centrally-managed (created, purged, or achieved) as necessary | ||
| 28 | R | must support the current State and Federal privacy laws and general data protection (GDPR) policies | ||
| 29 | R | there must be no restrictions on the number of concurrent users in the system | ||
| 30 | R | must encrypt data at rest | ||
| 31 | R | must provide an audit trail/logs/tracking for any action in the database including real- time notifications | ||
| 32 | R | user permissions and accesses must be role based. Role-based permissions govern each user's rights to add, edit,and view information within the system | ||
| 33 | O | should have attribute based access control available for granting permissions to add, edit,and view information within the system | ||
| 34 | R | admin users must be required to log in through the Single sign-on (SSO) | ||
| 35 | R | must support multi-factor authentication | ||
| 36 | R | must provide a system capability for auditing/auditlogs | ||
| 37 | R | Must be network Redundant, 100% multi-tenant, cloudbased | ||
| 38 | R | Solution must have the ability to track and display the history of information stored in the application. | ||
| 39 | R | any breach of vendor system must be reported to USM's Technology Security Officer in |
accordance with The MS Data Breach Law and the European Union General Data Protection Regulation within 72 hours of having discovered or being made aware of the breach 40 R USM client access must be browser based and should run on the most recent versions.
• Microsoft Edge
• FireFox
• Safari
• Chrome
| 41 | R | Sytem generated data must be read-only and protected from modication by users |
| System Requirements | ||
| 42 | R | the vendor must implement software upgrades and updates to the system with prior notification to the University |
| 43 | R | system must be secure and meet all local, state and federal data security standards |
| 44 | R | documented web services based API for completing custom integration with other applications |
| 45 | R | all configuration changes must be protected across all upgrades |
| 46 | R | Web content must meet ISO/IEC 40500:2012 [Web Content Accessibility Guidelines (WCAG) 2.1 AA] at a minimum. |
| Data Ownership and Management | ||
| 47 | R | All data entered into the solution is the sole possession of the University. Vendor must agree not to use or disclose USM data without USM's written permission, data cannot be stored or processed outside of the united states |
| 48 | R | Vendor must provide a mechanism for returning all data at the end of the contract. The mechanism must provide for automated load into a relational database system & a non-proprietary format |
File details come from the government source that posted it. Updated .