ATTACHMENT E - Mandatory Requirements Checklist - RFP 758 2700000012.xlsx
XLSX spreadsheet 12 KB Posted
- Attached to
- HCM ERP System Replacement - Phase 1
- Solicitation number
- RFP 758 2700000012 2
- Issued by
- Kentucky
About this file
This is a Mandatory Requirements Checklist (Attachment E) for RFP 758 2700000012 issued by the Commonwealth of Kentucky for the Human Capital Management Enterprise Resource Planning System Replacement—Phase 1 project. The RFP solicits proposals from a System Service Provider (SSP) partnered with a System Integrator (SI) to implement a Benefits Administration & Billing Software Solution. Proposals are due August 31, 2026, and must be submitted as combined technical and cost proposals in separate files. The mandatory requirements establish that proposals offering only software or only services will be deemed non-responsive, and the SSP-SI partnership structure is mandatory, with each SSP permitted to partner with only one SI and vice versa. The SSP must provide all required software components fully integrated and ensure FedRAMP compliance with hosting services for at least five instances across sandbox, development, preview, production, and training environments.
The checklist establishes that SIs must submit fixed-fee pricing for implementation and deployment services based on the RFP's scoping information, with costs itemized across staffing categories including Leadership and Project Management, Functional/Configuration, Change Management and Training, Technical Team, and Post Go-Live Support. Pricing must be submitted as firm, fixed fees allocated across Kentucky's fiscal years from FY2027 through FY2046, with a blended labor rate accounting for 25% on-site and 75% remote work. The SSP must respond to specific RFP sections using the supplied Attachment F Excel workbook and comply with the Commonwealth Office of Technology's AI Policy (CIO-126), with vendors required to notify the Commonwealth of any known issues or incidents arising from AI use. All awarded vendors must cooperate fully with the Independent Verification and Validation (IV&V) vendor, participate in IV&V meetings and checkpoints, and respond to findings and recommendations within mutually agreed timeframes.
View the file
Other files
Show all 11
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
Mandatory
ATTACHMENT E - MANDATORY REQUIREMENTS CHECKLIST
RFP 758 2700000012
Offeror shall indicate compliance with each mandatory requirement by responding YES. Proposals that do not meet all mandatory requirements shall be deemed non responsive and shall not be considered. Attachment E should be submitted with the Technical Proposal.
| SECTION 3 MANDATORY REQUIREMENTS | YES | NO | |
| 3.1 Proposals that offer only software or only services ill be considered non-responsive and will not be eligible for contract award. | |||
| 3.1 Systems Integrators (SIs) shall not submit proposals independently. | |||
| 3.1 Each SI must partner with an SSP and submit a joint proposal that is owned by the SSP. | |||
| 3.1 An SSP must partner with only one SI. | |||
| 3.1 An SI shall partner with only one SSP. | |||
| 3.1 Each SSP must submit only one proposal. | |||
| 3.1 Each SSP proposal must include all required components identified in Section 3.0 sub sections 3.1.A.1.1 and 3.1.A.1.2. | |||
| 3.1.A.1 Section in its entirety. | |||
| 3.1.A.2 Each component of the proposed software solution must be fully integrated and must be provided by the same SSP. | |||
| 3.1.A.3 Section in its entirety. | |||
| 3.1.A.4 The SSP must ensure FedRAMP requirements are met and provide associated hosting services for at least five (5) instances for the pre-production and production infrastructure to include sandbox, development (may be considered a second sandbox), preview, production and training. | |||
| 3.1.A.5 Section in its entirety. | |||
| 3.1.A.6 Section in its entirety. | |||
| 3.1.A.7 Section in its entirety. | |||
| 3.1.A.8 Section in its entirety. | |||
| 3.1.A.9 Section in its entirety. | |||
| 3.1.A.10 Section in its entirety. | |||
| 3.1.A.11 Section in its entirety. | |||
| 3.1.A.12 Section in its entirety. | |||
| 3.1.A.13 Section in its entirety. | |||
| 3.2.3 The SSP shall respond to RFP Section 3.2.7 in one combined Excel workbook, using the Excel workbook supplied as Attachment F. | |||
| 3.3.1.1 Based on the scoping information provided in this RFP and its attachments, SIs will quote a fixed fee price for implementation and deployment services. | |||
| 3.3.1.2 The Statement of Work between the SI and the Commonwealth will be revised and finalized as part of the final Agreement between the Commonwealth and the SI. | |||
| 3.3.1.3 The SI must include all relevant Business Analytics & Reporting and Mobility, while ensuring security, compliance, and integration to the Commonwealth’s other enterprise systems as designated. | |||
| 3.3.1.4 Section in its entirety. | |||
| 3.3.1.5 The vendor and its subcontractors shall comply with the Commonwealth Office of Technology’s AI Policy - CIO-126, Artificial Intelligence Policy and usage must be approved by COT and the AI committee. (see Section 4.1 and 10.31 of this RFP) | |||
| 3.3.1.5.1 Section in its entirety. | |||
| 3.3.1.5.2 Section in its entirety. | |||
| 3.3.1.5.3 Section in its entirety. | |||
| 3.3.1.5.5 Section in its entirety. | |||
| 3.3.1.5.6 Section in its entirety. | |||
| 3.3.1.5.7 Vendor(s) shall promptly notify the Commonwealth of any known issues, risks, or incidents arising from the use of AI | |||
| 3.3.1.6 The Vendors shall meet with Cabinet personnel, or designated representatives, to resolve technical or contractual problems that may occur during the term of the Agreement. | |||
| 3.4 The awarded vendor(s) shall: | |||
| • | Cooperate fully with the IV&V vendor and provide timely access to project artifacts, environments, documentation, and personnel as reasonably requested | ||
| • | Participate in IV&V led meetings, review and checkpoints | ||
| • | Respond to IV&V findings, recommendations, and risk assessments within mutually agreed timeframes | ||
| • | Support transparency in project status, risks, and issues. |
File details come from the government source that posted it. Updated .