ATTACHMENT A - Terms and Conditions- RFP 758 2600000112.pdf

ATTACHMENT A

Commonwealth of Kentucky Request for Proposal (RFP)

For

Large Volume Print Solution Lease

RFP 758 2600000112

Release Date: October 10, 2025 CLOSING DATE AND TIME November 14, 2025 at 3:30pm ET

Issued by

The Finance and Administration Cabinet On Behalf of the Commonwealth Office of Technology (COT)

Commonwealth Buyer:

Melissa Hubbard, KCPM Statewide Procurement Analyst II

COMMONWEALTH OF KENTUCKY

FINANCE AND ADMINISTRATION CABINET

Office of Procurement Services 200 Mero Street, 5th Floor.

Frankfort, KY 40622

(502) 782-5336

Melissa.Hubbard@ky.gov

TABLE OF CONTENTS

Proposal Submission Checklist Section 1 – Summary Section 2 – Introduction Section 3 – Scope of Work Section 4 – Commonwealth Office of Technology Requirements Section 5 – Procurement Requirements and Instructions Section 6 – Proposal Submission Section 7 – Proposal Evaluation Section 8 – Negotiations Section 9 – Contract Requirements Section 10 – Standard Terms and Conditions Section 11 – Attachments mailto:Melissa.Hubbard@ky.gov

PROPOSAL SUBMISSION CHECKLIST

The vendor MUST include the following with the proposal submission.

If the items highlighted below are not submitted with the proposal submission, the Commonwealth MUST deem the proposal non-responsive and SHALL NOT consider for award.

All other items MUST be submitted prior to award.

*PROPOSED TECHNICAL SOLUTION

*PROPOSED COST SOLUTION

TRANSMITTAL LETTER [see Section 6.7(A)]

REVENUE FORM 10A100 KENTUCKY TAX REGISTRATION APPLICATION IF

APPLICABLE (see Section 6.7 (C)], CERTIFICATE OF AUTHORITY- REGISTRATION WITH SECRETARY OF STATE BY

A FOREIGN ENTITY IF APPLICABLE [see Section 6.7 (D)]

REQUIRED ANNUAL AFFIDAVIT AND OTHER AFFIDAVIT(S)

https://finance.ky.gov/office-of-the-secretary/FinanceForms/Annual%20Required%20Affidavit%20for%20Bidders%20Offer ors%20and%20Contractors.pdf

MANDATORY REQUIREMENTS CHECKLIST (SEE ATTACHMENT F)

*Please see Attachment E - The Protection of Personal Information Security and Breach Investigation Procedures and Practice Act (KRS 61.931), et seq.

effective January 1, 2015.

https://finance.ky.gov/office-of-the-secretary/FinanceForms/Annual%20Required%20Affidavit%20for%20Bidders%20Offerors%20and%20Contractors.pdf https://finance.ky.gov/office-of-the-secretary/FinanceForms/Annual%20Required%20Affidavit%20for%20Bidders%20Offerors%20and%20Contractors.pdf https://finance.ky.gov/office-of-the-secretary/FinanceForms/Annual%20Required%20Affidavit%20for%20Bidders%20Offerors%20and%20Contractors.pdf

SECTION 1 - RFP SUMMARY

1.1 Estimated Schedule of RFP Activities

The following table presents the anticipated schedule for major activities associated with the RFP distribution, proposal submission, proposal evaluation process, and contract award. The Commonwealth reserves the right at its sole discretion to change the Schedule of Activities, including the associated dates and times.

Anticipated Schedule of Activities

Release of RFP

October 10, 2025

1st Set Of Vendors’ Written Questions due by 12:00 PM ET

(SUBMIT QUESTIONS ON ATTACHMENT D-VENDORS’ QUESTION

FORM)

October 20, 2025

Commonwealth’s Response to 1st Set of Vendors’ Written Questions October 24, 2025 2nd Set Of Vendors’ Written Questions due by 12:00 PM ET

(SUBMIT QUESTIONS ON ATTACHMENT D-VENDORS’ QUESTION

FORM)

October 28, 2025

Commonwealth’s Response to 2nd Set of Vendors’ Written Questions

October 31, 2025

Proposals due by 3:30 PM ET

November14, 2025

1.2 Issuing Office

The Commonwealth of Kentucky, Finance and Administration Cabinet, Office of Procurement Services, is issuing this RFP on behalf of the Commonwealth Office of Technology (COT). The Finance and Administration Cabinet is the only office authorized to change, modify, amend, alter, or clarify the specifications, terms and conditions of this RFP.

A contract, based on this RFP, may or may not be awarded. Any contract award from this RFP is invalid until properly approved and executed by the Finance and Administration Cabinet.

1.3 Agencies to Be Served

This contract shall be for use by the Commonwealth Office of Technology (COT). No shipments shall be made except upon receipt by vendor of an official delivery order from the using agency.

SECTION 2 - INTRODUCTION

2.1 Purpose

The purpose of this Request for Proposal (RFP) is to solicit proposals for competitive negotiations pursuant to 200 KAR 5:307. The Commonwealth is seeking a vendor to provide two (2) Large Volume Print Solutions, via a lease agreement, for the Commonwealth Office of Technology (COT) Printing Services Branch.

2.2 Background

The Commonwealth Office of Technology (COT) is an agency embedded within the Finance and Administration Cabinet. COT is responsible for setting Enterprise IT policies and standards, as well as providing Technology services for state agencies. COT’s mission is to support agency partners in the fulfillment of their core mission by providing technology leadership, services, and solutions in a secure, transparent, and fiscally responsible manner.

The COT Printing Services Branch, provides large volume printing services for Executive Cabinet Agencies. The workload is comprised of hard copy reports as well as bulk document postal mailings. COT’s three largest customers are; the Cabinet for Health and Family Services, the Labor and Education Cabinet and the Department of Revenue.

The COT Printing Services Branch provides 24/7 operations, including weekends.

COT produces 5-10 million print images (variable line data print) monthly in both black and white, as well as color format. The workload is approximately 70% black and white and 30% color.

COT currently has three large volume printers in operation to include: two color inkjet-based printers and one toner-based black and white printer. The lease for two high volume printers expires November 30, 2025. This request for proposal is to replace the two printers that come off lease, with two printers capable of black and white print.

SECTION 3 – SCOPE OF WORK

PROPOSALS THAT DO NOT MEET MANDATORY REQUIREMENTS WILL BE

DEEMED NON-RESPONSIVE AND WILL NOT BE CONSIDERED. REFER TO

ATTACHMENT F – MANDATORY REQUIREMENTS CHECKLIST.

Mandatory Requirement means a condition set out in the specifications or statement of work that must be met without exception.”

3.1 Scope of Work/Technical Requirements

A. Vendor shall meet the following minimum Facility Requirements:

1. Printer space dimensions – Size 30’ x 6' x 7’ (W x D x H)

2. Power (dedicated)

a. 60Hz – 120/208 VAC (+6%, -10%) - Typical for 60Hz US, 3-phase wye, with Neutral and Protective Earth, service >63A per Phase

b. 50Hz - 230/400 (+6%, -10%) VAC, 3-phase wye, w/Neutral and Protective Earth – Typical for 50/60 Hz XE installations, service >32A per Phase

3. HVAC controls – altitude (above sea level) – 10,000ft

a. Venting – if required

b. Room Temperature – Minimum (70F) Maximum (80F)

c. Room Humidity - Minimum (35%) Maximum (55%)

4. Floor area capacity weight limits – current printers are 6,769lbs and 2,705lbs. COT will provide additional floor supports if required to accommodate any proposed printers that exceed the current weights.

B. Vendor shall work with COT to install and configure the leased devices’ architecture according to COT Enterprise requirements.

C. Vendor shall deliver a certified letter stating each device is certified to operate within COT’s environment.

D. Print equipment solutions must be available via a lease agreement. The Commonwealth shall not purchase the equipment.

E. Vendor solution shall provide high volume variable line data print.

F. Vendor solution shall be compatible with BARR Enterprise Print Server print management product. Overview Barr Enterprise Print Server G. Vendor solution shall be compliant with IRS Publication 1075 (PUB1075) for sensitive data, federal tax information (FTI) protections.

H. Vendor solution shall be compliant with US Department of Health and Human

Services’ Health Insurance Portability and Accountability Act (HIPPA).

I. Vendor solution shall be compliant with National Institute of Standards and

Technology (NIST) 800-53 framework.

J. Vendor solution shall be capable of printing COT's average monthly volume of

5-10 million print images comprised of variable line data print.

K. Vendor solution shall be capable of at least 135 Pages Per Minute (PPM).

L. Vendor solution shall meet variable specifications: black & white, letter, legal, portrait, landscape, card stock, and labels.

M. Vendor solution shall be capable of connecting back to COT’s network for data communications over secure VPN with protections compliant with PUB1075.

Solution shall have the capability to dial home to the manufacturer for troubleshooting and diagnostics. COT reserves the right to turn vendor connection on or off as needed for PUB1075 compliance.

N. Vendor shall have staffing levels for support staff in place for 24/7/365 print production within a reasonable distance of Frankfort, Kentucky.

O. Vendor shall have replacement parts readily available for printer maintenance.

http://www.barrcentral.com/help/print_channel_beps/Overview_Barr_Enterprise_Print_Server.htm

P. Vendor shall provide Service Level Agreements (SLAs), which shall be negotiated and approved by both parties and shall become part of the awarded contract.

Q. The print solution shall have the ability to produce a report to be used for billing.

This report shall contain the number of images produced by the print file/job. It is imperative that this report is capable of extracting COT internal billing numbers from the file name.

R. Operator training shall be provided for COT Print Operators at no cost to COT.

S. Vendor shall have the capability to use paper (media) produced by multiple media manufacturers that produce media for high volume printers. The print solution shall function while using media from multiple industry standard media producers. Customer shall not be required or limited to one specific brand.

Customer shall have the flexibility to use media from multiple sources.

T. Installation of the leased equipment shall be at the expense of the vendor.

Removal of the leased equipment at the end of the lease shall be at the expense of the vendor and the vendor shall arrange and schedule pickup and removal.

SECTION 4 – COMMONWEALTH OFFICE OF TECHNOLOGY (COT)

REQUIREMENTS

4.1 Commonwealth Information Technology Policies and Standards

A. The vendor and any subcontractors shall be required to adhere to applicable Commonwealth policies and standards.

B. The Commonwealth posts changes to COT Standards and Policies on its Commonwealth Office of Technology - Home - Commonwealth Office of Technology (Kentucky) website. Vendors and subcontractors shall ensure their solution(s) shall work in concert with all posted changes. Vendors or subcontractors that cannot comply with changes must, within thirty (30) days of the posted change, request written relief with the justification for such relief.

The Commonwealth may: 1) deny the request, 2) approve an exception to the policy/standard, or 3) consider scope changes to the contract to accommodate required changes. Vendors or subcontractors that do not provide the response within the thirty (30) day period shall be required to comply within ninety (90) days of the change.

4.2 Compliance with Kentucky Information Technology Standards (KITS)

A. The Kentucky Information Technology Standards (KITS) reflect a set of principles for information, technology, applications, and organization. These standards provide guidelines, policies, directional statements and sets of standards for information technology. It defines, for the Commonwealth, functional and information needs so that technology choices can be made based on business objectives and service delivery. The vendor shall stay https://technology.ky.gov/Pages/index.aspx https://technology.ky.gov/Pages/index.aspx knowledgeable and shall provide a solution that works in concert with these standards for all related work resulting from this RFP.

https://technology.ky.gov/about-the-agency/Pages/kits.aspx

B. The vendor and any subcontractors may be required to submit a technology roadmap for any offered solution. Additional roadmaps will be submitted upon request of the Commonwealth. If required, the roadmap shall include, but is not limited to, planned, scheduled and projected product lifecycle dates and historical release/patch or maintenance dates for the technology. In addition, any guidance on projected release/revision/patch/maintenance schedules would be preferred.

4.3 Compliance with Industry Accepted Reporting Standards Based on Trust Service Principles and Criteria The vendor must employ comprehensive risk and threat management controls based on defined industry standards for service organizations such as ISO AICPA TSP section 100, Trust Services Principles and Criteria. The vendor must annually assert compliance and engage a third-party certification registrar to examine such assertions and controls to provide a Report, such as ISO 9000, ISO 14001, AT101 SOC 2 type 2, on Controls at a Service Organization Relevant to Security, Availability, Processing Integrity, Confidentiality, and Privacy, which contains an opinion on whether the operating controls effectively support the assertions. All such reports, including publicly available reports (i.e. AT 101 SOC

3) shall be made available to the Commonwealth for review.

4.4 System Vulnerability and Security Assessments

The Commonwealth reserves the right to conduct, in collaboration with the vendor, non-invasive vulnerability and security assessments of the software and infrastructure used to provide services prior to implementation and periodically thereafter. Upon completion of these assessments, the Commonwealth will communicate any findings to the vendor for action. Any cost relating to the alleviation of the findings will be the responsibility of the vendor. Mitigations will be subject to re-evaluation after completion. In cases where direct mitigation cannot be achieved, the vendor shall communicate this and work closely with the Commonwealth to identify acceptable compensating controls that will reduce risk to an acceptable and agreed upon level. An accredited third-party source may be selected by the vendor to address findings, provided they will acknowledge all cost and provide valid documentation of mitigation strategies in an agreed upon timeframe.

4.5 Privacy Assessments

The Commonwealth reserves the right to conduct privacy assessments of the collection, use, maintenance and sharing of Commonwealth data by any vendor services, software, and infrastructure used to provide services prior to implementation and periodically thereafter. Upon completion of this assessment, the Commonwealth will communicate any findings to the vendor for action. Any cost relating to the alleviation of the findings will be the responsibility of the https://technology.ky.gov/about-the-agency/Pages/kits.aspx vendor. Mitigations will be subject to re-evaluation after completion. In cases where direct mitigation cannot be achieved, the vendor shall communicate this and work closely with the Commonwealth to identify acceptable compensating controls or privacy practices that will reduce risk to an acceptable and agreed upon level. An accredited third-party source may be selected by the vendor to address findings, provided they will acknowledge all cost and provide valid documentation of mitigation strategies in an agreed upon timeframe.

4.6 Privacy, Confidentiality and Ownership of Information

The Commonwealth is the designated owner of all Commonwealth data and shall approve all access to that data. The vendor shall not have ownership of Commonwealth data at any time. The vendor shall not profit from or share Commonwealth data. The vendor shall be in compliance with privacy policies established by governmental agencies or by state or federal law. Privacy notice statements may be developed and amended from time to time by the Commonwealth and will be appropriately displayed on the Commonwealth portal (Ky.gov). The vendor should provide sufficient security to protect the Commonwealth and COT data in network transit, storage, and cache. All Commonwealth data, including backups and archives, must be maintained at all times within the contiguous United States. All Commonwealth data, classified as sensitive or higher, as defined in Enterprise Standards, must be encrypted in-transit from vendor’s network and at rest while stored on vendor’s laptops or other portable media devices.

4.7 License Agreements

Any proposed software agreements, i.e. license agreement, subscription agreement, end-user license agreement, etc. shall include the following language, or similar, and must be submitted to the Commonwealth Office of Technology (COT) for review and approval prior to the award of the contract:

“All terms in this agreement/EULA shall be read as applicable only to the extent permitted by Kentucky law and no term in violation of the Kentucky law, inclusive of Kentucky Procurement Law, shall be given effect.”

Any third-party software licenses and cloud resources necessary for the proposed solution may be procured via the Commonwealth’s existing contracts.

4.8 Software Version Requirements

All commercially supported and Commonwealth approved software components such as Operating system (OS), Database software, Application software, Web Server software, Middle Tier software, and other ancillary software must be kept current. In the event that a patch interferes with the solution, the vendor must present a plan for compliance to the Commonwealth outlining the constraints and an appropriate plan of action to bring the solution in to compliance to allow this patch to be applied in the shortest timeframe possible, not to exceed three (3) months, unless otherwise negotiated with the Commonwealth.

4.9 No Surreptitious Code Warranty

The vendor represents and warrants that no copy of licensed software provided to the Commonwealth contains or will contain any Self-Help Code or any Unauthorized Code as defined below. This warranty is referred to in this contract as the "No Surreptitious Code Warranty”.

As used in this contract, "Self-Help Code" means any back door, time bomb, drop-dead device, or other software routine designed to disable a computer program automatically with the passage of time or under the positive control of a person other than the licensee of the software. Self-Help Code does not include Software routines in a computer program, if any, designed to permit an owner of the computer program (or other person acting by authority of the owner) to obtain access to a licensee's computer system(s) (e.g. remote access) for purposes of maintenance or technical support.

As used in this contract, "Unauthorized Code" means any malware designed to permit unauthorized access to disable, erase, or otherwise harm software, equipment, or data; or to perform any other such actions. The term Unauthorized Code does not include Self-Help Code.

In addition, vendor will use up-to-date commercial virus detection software to detect and remove any viruses from any software prior to delivering it to the Commonwealth.

The vendor shall defend the Commonwealth against any claim and indemnify the Commonwealth against any loss or expense arising out of any breach of the No Surreptitious Code Warranty.

4.10 Project Governance

Vendor shall work with the agency and appropriate COT offices, when needed, in the cases of data governance, security aspects, hosting, integration, etc., provided that such work does not expand the scope of the services as described in this RFP absent a corresponding change order agreed to by the parties reflecting such expansion.

4.11 Application and Service Requirements

Current Enterprise Applications and Services

1. COT provides a number of Enterprise Shared Services to State agencies.

Vendor shall use published IT Applications and Services provided on KITS for: Enterprise Service Bus, Enterprise Content Management, Data Warehousing, Data Analytics and Reporting, Business Intelligence, Web Services, GIS, unless explicitly approved by COT.

2. Vendor provided dedicated application components (i.e., Application Servers, Databases, etc.) shall comply with KITS or if the technology is not included in KITS, the technology must be accepted by the Commonwealth for inclusion in KITS or granted a written exception to KITS according to COT Information Technology Standards Policy currently

CIO-051.

3. Vendor applications must describe in detail all available features and functionality accessible via APIs.

4. All business applications must support the ability to use modern authentication for authentication and authorization. Modern authentication technologies would include SAML 2.0, WSFED, OAuth, or OpenID Connect.

4.12 Applicable Security Control Framework Compliance

The vendor must have an awareness and understanding of the NIST Special Publication 800-53 Security Control Framework and employ safeguards that meet or exceed the moderate level controls as defined within the standard. The vendor must provide sufficient safeguards to provide reasonable protections around the Commonwealth’s data to ensure that the confidentiality, integrity, and availability is maintained at an appropriate level. These include but are not limited to:

• Access Control The vendor must employ policy and process that provide for stringent control to limit physical and logical access to systems that house Commonwealth data, on a need to know basis, provide clear separation of duties, and adheres to least privilege principles.

• Awareness and Training The vendor must provide the appropriate role specific training for staff to ensure that there is awareness and understanding of roles and responsibilities as they relate to the protections around the Commonwealth’s data.

• Audit and Accountability There must be sufficient auditing capability to ensure that actions are tracked and there is individual accountability for all actions taken by vendor staff.

• Configuration Management The vendor must work within established baselines that provide minimal functionality needed to ensure service delivery without exposing unnecessary risk. The vendor must also employ structured change control processes that provide a level of coordination with the client agreed upon in a Service Level Agreement (SLA).

• Contingency Planning The vendor must employ contingent planning policy and procedures that ensure service delivery based on agreed SLA levels while maintaining all Commonwealth data within the continental Unites States.

• Identification and Authorization The vendor must employ appropriate identity and access management policies and procedures to ensure that access is appropriately authorized and managed at a level to ensure that access is provisioned and de-provisioned in a timely and efficient manner.

• Incident Response The vendor must employ policy and procedures to ensure that an appropriate response to all identified security incidents are addressed in a timely manner and are reported to the appropriate parties in an agreed upon SLA timeframe.

The vendor must also ensure that all staff are sufficient trained to ensure that they can identify situations that are classified as security incidents.

• Maintenance The vendor must employ policy and procedures that ensure that all maintenance activities are conducted only by authorized maintenance staff leveraging only authorized maintenance tools.

• Media Protection The vendor must employ policy and procedure to ensure that sufficient protections exist to protect Commonwealth data on all storage media throughout the media lifecycle and maintain documentation from media creation through destruction.

• Physical and Environmental Controls The vendor must employ physical and environmental policies and procedures that ensure that the service and delivery infrastructure are located in a physically secure and environmentally protected environment to ensure the confidentiality, integrity, and availability of Commonwealth data.

• Personnel Security The vendor must employ policies and procedures to ensure that all staff that have access to systems that house, transmit, or process Commonwealth data have been appropriately vetted and have been through a background check at the time of hire and periodically thereafter.

• System and Communications Protections The vendor must employ physical and logical protection that protect system communications and communication media from unauthorized access and to ensure adequate physical protections from damage.

4.13 IRS Publication 1075 -Exhibit 7 Safeguarding Contract Language Publication 1075 (Rev. 11-2021) (irs.gov)

I. PERFORMANCE

In performance of this contract, the Contractor agrees to comply with and assume responsibility for compliance by officers or employees with the following requirements:

(1) All work will be performed under the supervision of the contractor.

(2) The contractor and contractor’s officers or employees to be authorized access to FTI must meet background check requirements defined in IRS Publication 1075. The contractor will maintain a list of officers or employees authorized access to FTI. Such list will be provided to the agency and, upon request, to the

IRS.

https://www.irs.gov/pub/irs-pdf/p1075.pdf

(3) FTI in hardcopy or electronic format shall be used only for the purpose of carrying out the provisions of this contract. FTI in any format shall be treated as confidential and shall not be divulged or made known in any manner to any person except as may be necessary in the performance of this contract.

Inspection or disclosure of FTI to anyone other than the contractor or the contractor’s officers or employees authorized is prohibited.

(4) FTI will be accounted for upon receipt and properly stored before, during, and after processing. In addition, any related output and products require the same level of protection as required for the source material.

(5) The contractor will certify that FTI processed during the performance of this contract will be completely purged from all physical and electronic data storage with no output to be retained by the contractor at the time the work is completed.

If immediate purging of physical and electronic data storage is not possible, the contractor will certify that any FTI in physical or electronic storage will remain safeguarded to prevent unauthorized disclosures.

(6) Any spoilage or any intermediate hard copy printout that may result during the processing of FTI will be given to the agency. When this is not possible, the contractor will be responsible for the destruction of the spoilage or any intermediate hard copy printouts and will provide the agency with a statement containing the date of destruction, description of material destroyed, and the destruction method.

(7) All computer systems receiving, processing, storing, or transmitting FTI must meet the requirements in IRS Publication 1075. To meet functional and assurance requirements, the security features of the environment must provide for the managerial, operational, and technical controls. All security features must be available and activated to protect against unauthorized use of and access to

FTI.

(8) No work involving FTI furnished under this contract will be subcontracted without the prior written approval of the IRS.

(9) Contractor will ensure that the terms of FTI safeguards described herein are included, without modification, in any approved subcontract for work involving

FTI.

(10) To the extent the terms, provisions, duties, requirements, and obligations of this contract apply to performing services with FTI, the contractor shall assume toward the subcontractor all obligations, duties and responsibilities that the agency under this contract assumes toward the contractor, and the subcontractor shall assume toward the contractor all the same obligations, duties and responsibilities which the contractor assumes toward the agency under this contract.

(11) In addition to the subcontractor’s obligations and duties under an approved subcontract, the terms and conditions of this contract apply to the subcontractor, and the subcontractor is bound and obligated to the contractor hereunder by the same terms and conditions by which the contractor is bound and obligated to the agency under this contract.

(12) For purposes of this contract, the term “contractor” includes any officer or employee of the contractor with access to or who uses FTI, and the term “subcontractor” includes any officer or employee of the subcontractor with access to or who uses FTI.

(13) The agency will have the right to void the contract if the contractor fails to meet the terms of FTI safeguards described herein.

II. CRIMINAL/CIVIL SANCTIONS

(1) Each officer or employee of a contractor to whom FTI is or may be disclosed shall be notified in writing that FTI disclosed to such officer or employee can be used only for a purpose and to the extent authorized herein, and that further disclosure of any FTI for a purpose not authorized herein constitutes a felony punishable upon conviction by a fine of as much as $5,000 or imprisonment for as long as 5 years, or both, together with the costs of prosecution.

(2) Each officer or employee of a contractor to whom FTI is or may be accessible shall be notified in writing that FTI accessible to such officer or employee may be accessed only for a purpose and to the extent authorized herein, and that access/inspection of FTI without an official need-to-know for a purpose not authorized herein constitutes a criminal misdemeanor punishable upon conviction by a fine of as much as $1,000 or imprisonment for as long as 1 year, or both, together with the costs of prosecution.

(3) Each officer or employee of a contractor to whom FTI is or may be disclosed shall be notified in writing that any such unauthorized access, inspection or disclosure of FTI may also result in an award of civil damages against the officer or employee in an amount equal to the sum of the greater of $1,000 for each unauthorized access, inspection, or disclosure, or the sum of actual damages sustained as a result of such unauthorized access, inspection, or disclosure, plus in the case of a willful unauthorized access, inspection, or disclosure or an unauthorized access/inspection or disclosure which is the result of gross negligence, punitive damages, plus the cost of the action. These penalties are prescribed by IRC sections 7213, 7213A and 7431 and set forth at 26 CFR 301.6103(n)-1.

(3) Additionally, it is incumbent upon the contractor to inform its officers and employees of the penalties for improper disclosure imposed by the Privacy Act of 1974, 5 U.S.C. 552a. Specifically, 5 U.S.C. 552a(i)(1), which is made applicable to contractors by 5 U.S.C. 552a(m)(1), provides that any officer or employee of a contractor, who by virtue of his/her employment or official position, has possession of or access to agency records which contain individually identifiable information, the disclosure of which is prohibited by the Privacy Act or regulations established thereunder, and who knowing that disclosure of the specific material is so prohibited, willfully discloses the material in any manner to any person or agency not entitled to receive it, shall be guilty of a misdemeanor and fined not more than $5,000.

(4) Granting a contractor access to FTI must be preceded by certifying that each officer or employee understands the agency’s security policy and procedures for safeguarding FTI. A contractor and each officer or employee must maintain their authorization to access FTI through annual recertification of their understanding of the agency’s security policy and procedures for safeguarding FTI. The initial certification and recertifications must be documented and placed in the agency's files for review. As part of the certification and at least annually afterwards, a contractor and each officer or employee must be advised of the provisions of IRC sections 7213, 7213A, and 7431 (see Exhibit 4, Sanctions for Unauthorized Disclosure, and Exhibit 5, Civil Damages for Unauthorized Disclosure). The training on the agency’s security policy and procedures provided before the initial certification and annually thereafter must also cover the incident response policy and procedure for reporting unauthorized disclosures and data breaches. (See Section 10) For the initial certification and the annual recertifications, the contractor and each officer or employee must sign, either with ink or electronic signature, a confidentiality statement certifying their understanding of the security requirements.

III. INSPECTION

The IRS and the Agency, with 24 hour notice, shall have the right to send its inspectors into the offices and plants of the contractor to inspect facilities and operations performing any work with FTI under this contract for compliance with requirements defined in IRS Publication 1075. The IRS’ right of inspection shall include the use of manual and/or automated scanning tools to perform compliance and vulnerability assessments of information technology (IT) assets that access, store, process or transmit FTI. Based on the inspection, corrective actions may be required in cases where the contractor is found to be noncompliant with FTI safeguard requirements.

SECTION 5 – PROCUREMENT REQUIREMENTS AND INSTRUCTIONS

5.1 Procurement Requirements

Procurement requirements are listed under “Procurement Laws, Preference, Regulations and Policies” and “Response to Solicitation” located on the eProcurement Web page at https://finance.ky.gov/eProcurement/Pages/procurement-laws-regulations-and-policies.aspx and https://finance.ky.gov/eProcurement/Pages/doing-business-with-the-commonwealth.aspx respectively. The vendor must comply with all applicable statutes, regulations and policies related to this procurement.

5.2 Access to Solicitation, RFP, and Addenda

The Commonwealth wants each prospective vendor to have full and complete information on which to base a proposal response. Only information presented or referred to in this RFP and any additional written information that is supplied by the Commonwealth Buyer shall be used by vendors in preparing the response.

The solicitation, addenda, and attachments shall be posted to the Kentucky Vendor Self Service link at https://vss.ky.gov

It is not necessary to register to access the solicitation. Unregistered vendors can access solicitations by clicking on public access.

In the event of any conflict or variation between the solicitation or modification as issued by the Commonwealth and the vendor’s response, the version as issued shall prevail.

5.3 RFP Terminology

For the purpose of this RFP, the following terms may be used interchangeably:

o Proposer, Offeror, Contractor, Provider, or Vendor o Commonwealth Buyer, Buyer, Purchaser, or Contract Officer o RFP, Solicitation, or Procurement o Bid, Proposal, or Offer o Commonwealth of Kentucky, Commonwealth, or State, Agency, Commonwealth Office of Technology (COT) o Fiscal Year will be defined as the Commonwealth fiscal year: July 1 through

June 30 o Biennium will be defined as the Commonwealth biennium: July 1 of each even numbered year through June 30 of the next even numbered year o Requirements that include the words “Shall”, “Will”, “Must” indicate a mandatory requirement o Mandatory Requirement means a condition set out in the specifications or statement of work that must be met without exception.”

5.4 Restrictions on Communications

The Commonwealth Buyer named on the Cover Sheet of this RFP shall be the sole point of contact throughout the procurement process. All communications, https://finance.ky.gov/eProcurement/Pages/procurement-laws-regulations-and-policies.aspx https://finance.ky.gov/eProcurement/Pages/procurement-laws-regulations-and-policies.aspx https://finance.ky.gov/eProcurement/Pages/doing-business-with-the-commonwealth.aspx https://finance.ky.gov/eProcurement/Pages/doing-business-with-the-commonwealth.aspx https://vss.ky.gov/ oral and written (regular, express, or electronic mail,), concerning this procurement shall be addressed to the Buyer.

For violation of this provision, the Commonwealth shall reserve the right to disqualify the vendors’ proposal response.

5.5 Confidentiality of Contract Terms

The contractor and the Commonwealth agree that all information communicated between them before the effective date of the contract shall be received in strict confidence and shall not be necessarily disclosed by the receiving party, its agents, or employees without prior written consent of the other party. Such material will be kept confidential subject to Commonwealth and Federal public information disclosure laws.

Upon signing of the contract by all parties, terms of the contract become available to the public, pursuant to the provisions of the Kentucky Revised Statutes.

The contractor shall have an appropriate agreement with its subcontractors extending these confidentiality requirements to all subcontractors’ employees.

5.6 Written Questions Regarding this RFP

Vendors are encouraged to submit written questions pursuant to Section 1.1 of this RFP. Written questions shall be submitted to the Commonwealth Buyer via email at Melissa.Hubbard@ky.gov. Vendors should submit questions on Attachment D Vendors Question Form. No questions shall be accepted after the date(s) listed in Section 1.1 unless the question(s) is considered material to the procurement. The Commonwealth shall respond to salient questions in writing by issuing an addendum to the solicitation. The addendum shall be posted to the Kentucky Vendor Self Service site.

5.7 Vendor Response and Proprietary Information

The RFP specifies the format, required information, and general content of proposals submitted in response to the RFP. The Finance and Administration Cabinet will not disclose any portions of the proposals prior to Contract Award to anyone outside the Finance and Administration Cabinet, representatives of the agency for whose benefit the contract is proposed, representatives of the Federal Government, if required, and the members of the evaluation committees. After a contract is awarded in whole or in part, the Commonwealth shall have the right to duplicate, use, or disclose all proposal data submitted by vendors in response to this RFP as a matter of public record.

Although the Commonwealth recognizes the vendor's possible interest in preserving selected data which may be part of a proposal, the Commonwealth must treat such information as provided by the Kentucky Open Records Act, KRS

61.870 et sequitur.

Informational areas which normally might be considered proprietary shall be limited to individual personnel data, customer references, selected financial data, formulae, and financial audits which, if disclosed, would permit an unfair advantage to competitors. If a proposal contains information in these areas that a vendor declares proprietary in nature and not available for public disclosure, the vendor should declare in the Transmittal Letter [see Section 6.7 (A)] the inclusion of proprietary information and shall noticeably label as proprietary each file containing such information. Proprietary information shall be submitted separately and identified as “Proprietary Data”. Proposals containing information declared by the vendor to be proprietary, either in whole or in part, outside the areas listed above may be deemed non-responsive to the RFP and may be rejected.

5.8 Notification of Award of Contract

The procurement process will provide for the evaluation of proposals and selection of the successful proposal in accordance with State law and regulations. KRS Chapter 45A of the Kentucky Model Procurement Code provides the regulatory framework for the procurement of services by State agencies.

All applicable statutes, regulations, policies and requirements shall become a part of an award as well as the Information Technology requirements.

For additional award information, vendors may email the Commonwealth Buyer.

5.9 Protest

Pursuant to KRS 45A.285, the Secretary of the Finance and Administration Cabinet, or his designee, shall have authority to determine protests and other controversies of actual or prospective offerors in connection with the solicitations or selection for award of a contract.

Any actual or prospective offeror or contractor, who is aggrieved in connection with solicitation or selection for award of a contract, may a file protest with the Secretary of the Finance and Administration Cabinet. A protest or notice of other controversy must be filed promptly and in any event within two (2) calendar weeks after such aggrieved person knows or should have known of the facts giving rise thereto. All protests or notices of other controversies must be in writing and shall be addressed and mailed to:

Holly M. Johnson, Secretary

COMMONWEALTH OF KENTUCKY

FINANCE AND ADMINISTRATION CABINET

200 MERO STREET, 5TH FLOOR

FRANKFORT, KY 40622

The Secretary of Finance and Administration Cabinet shall promptly issue a decision in writing. A copy of that decision shall be mailed or otherwise furnished to the aggrieved party and shall state the reasons for the action taken.

The decision by the Secretary of the Finance and Administration Cabinet shall be final and conclusive.

5.10 Vendor Notification – Ineligible for Award

The Commonwealth will not consider or evaluate any proposal submitted by a vendor when the vendor, the vendor’s employees or agents, had any involvement, contribution or participation in the development, preparation or review of this RFP prior to its issuance. The vendors proposal will be deemed ineligible for award.

5.11 Past Vendor Performance

Past vendor performance may be considered in the award of this Contract.

Vendors with a record of poor performance in the last twelve (12) months may be found non-responsible and ineligible for award.

SECTION 6 – PROPOSAL SUBMISSION

6.1 Disposition of Proposals

All proposals become the property of the Commonwealth of Kentucky. The successful proposal shall be incorporated into the resulting contract by reference.

Disposal of unsuccessful proposals shall be at the discretion of the Commonwealth Buyer.

6.2 Rules for Withdrawal of Proposals

Prior to the date specified for receipt of offers, a submitted proposal may be withdrawn by electronic or written notice by submitting a signed written request for its withdrawal to the Commonwealth Buyer.

6.3 Commonwealth’s Right to Use Proposal Ideas

The Commonwealth of Kentucky shall have the right to use all system ideas, or adaptations of those ideas, contained in any proposals received in response to the RFP. Selection or rejection of the proposal will not affect this right.

6.4 Submission of RFP Response

Each qualified offeror shall submit only one (1) proposal. Alternate proposals shall not be allowed. Failure to submit as specified shall result in a non-responsive proposal.

Acknowledgment of Addenda It is the vendor's responsibility to check the web site for any modifications to this solicitation.

Failure to specifically acknowledge addenda with submission will not excuse the vendor from adhering to all changes to the requirements of the solicitation set forth therein nor provide justification for any pricing changes.

6.5 Electronic Proposal Submission

Proposals shall be received by electronic submission in the eProcurement system.

An electronic proposal shall be authorized by the proper agent of the firm by the act of submitting it electronically through the eProcurement system.

Proposal information MUST be completed online. Response must contain all required information for the Solicitation. All bidders MUST be registered in the Commonwealth eProcurement System via the Vendor Self Service System at https://vss.ky.gov

Allow 24 – 48 hours to complete Vendor Registration. Vendors must be logged in to their Vendor Self Service (VSS) account in order to submit a response. Registrations completed the day of bid closing must be completed by the Vendor in the VSS portal. The Customer Resource Center is not able to complete registrations and activate accounts on the same day. Closing dates will not be extended for Vendors not registered by the date/time of the bid closing.

Vendor Self Service Registration Guides are provided at https://vss.ky.gov

All bidders are cautioned to begin their electronic submission in sufficient time to complete before the closing date and time. Delays due to technical difficulties or document upload impediments shall not be justification for acceptance of a late bid or proposal. Vendor attention to this advisory is encouraged. If you need assistance, please contact the Customer Resource Center (CRC) by email at Finance.CRCGroup@ky.gov or phone 502-564-9641 or toll-free 877-973-HELP (4357).

Proposals shall be submitted in three (3) parts: The Technical Proposal, the Cost Proposal, and Proprietary Information. Each part should consist of one document attachment. Do not submit multiple document attachments as Technical, Cost or Proprietary. All files shall be labeled accordingly. Attachments may not exceed

65,000 KB.

Proposals submitted online must be in an “Accepted” status and shall be assigned a date and time stamp from the eProcurement system at the time of final acceptance and formal submission by the vendor. The system will not allow submission of an online proposal after the published date and time for closing.

A proposal may be modified or withdrawn by electronic or written notice ONLY if received prior to the bid closing date and time. An electronic offer may be modified https://vss.ky.gov/ https://vss.ky.gov/ mailto:Finance.CRCGroup@ky.gov by applying the appropriate electronic signature and following the procedure in the state’s eProcurement system.

6.6 Format of Response

A. . Proposals shall be submitted in three (3) parts: the Technical Proposal, the Cost Proposal, and Proprietary Information. Each part should consist of one document. Do not submit multiple documents as Technical, Cost or Proprietary.

a. The Technical Proposal should be submitted on one (1) document marked Technical (in Microsoft Word, Microsoft Excel or PDF format ONLY). Do not include embedded documents, hyperlinks or hyperlinks to videos. The document should be named in the following manner: Technical – Name of offeror RFP number

b. The Cost Proposal should be submitted on one (1) document marked Cost (in Microsoft Word, Microsoft Excel or PDF format ONLY). Do not include embedded documents, hyperlinks or hyperlinks to videos. The document should be named in the following manner: Cost – Name of offeror RFP number

c. Any Proprietary Information shall be submitted on one (1) document marked Proprietary (in Microsoft Word, Microsoft Excel or PDF format ONLY). Do not include embedded documents, hyperlinks or hyperlinks to videos. The document should be named in the following manner: Proprietary – Name of offeror RFP number

Pricing shall only be provided in the Cost Proposal. DO NOT SUBMIT

ANY PRICING INFORMATION IN THE TECHNICAL PROPOSAL.

All submitted Technical and Cost Proposals shall remain valid for a minimum of six (6) months after the proposal due date.

6.7 Technical Proposal Content

A. Transmittal Letter

The transmittal letter should be on the vendor’s letterhead and signed by an agent authorized to bind the vendor. The transmittal letter should include the following:

i. A statement that deviations are included, if applicable. Proposed deviations must be outlined in the transmittal letter. Any deviation from the provisions of the solicitation must be specifically identified by the vendor in its proposal, which if successful, shall become part of the contract. Such deviations shall not be in conflict with the basic nature of this solicitation. The Commonwealth reserves the right to reject any and/or all deviations in whole or in part.

ii. A statement that, if awarded a contract as a result of this solicitation, the vendor shall comply in full with all requirements of the Kentucky Civil Rights Act, and shall submit all data required by KRS 45.560 to 45.640;

iii. A statement pursuant to KRS 11A.040 that the vendor has not knowingly violated any provisions of the Executive Branch Code of Ethics;

iv. A statement of that the vendor is in compliance with Prohibitions of Certain Conflicts of Interest;

v. A statement of certification in accordance with Federal Acquisition Regulation 52.209-5, Certification Regarding Debarment, Suspension, and Proposed Debarment that to the best of its knowledge and belief, the vendor and/or its principals is (are) not presently debarred, suspended, proposed for debarment, or declared ineligible for the award of contracts by any State or Federal agency.

vi. The name, address, telephone number, and email address of the contact person for this RFP. The address shall be one in which the major overnight delivery services will deliver.

vii. The name, address, telephone number, and email address of the contact person to serve as a point of contact for day-to-day operations.

viii. Subcontractor information to include name of company, address, telephone number and contact name, if applicable.

ix. Federal Tax ID

x. A statement that the vendor agrees to comply with items included in the Mandatory Checklist, if applicable.

B. Disclosure of Violation of Statutes Pursuant to KRS 45A.485, contractors are required to reveal final determinations of violation of certain statutes incurred within the last five (5) years and be in continuous compliance with those statutes during the contract. Where applicable, the vendor is required to complete and submit Report of Prior Violations of Tax and Employment Laws.

C. Kentucky Tax Registration Application

Revenue Form 10A100, Kentucky Tax Registration Application effective July 2008, is a form to be completed by any person or entity wishing to contract with the Commonwealth to provide goods or services subject to sales and use tax pursuant to KRS 139.200.

https://revenue.ky.gov/Forms/10A100(P)(4-25)_FINAL_locked%20Fill-in.pdf…