RFI_Cost_Recovery_for_11_18.pdf
PDF 242 KB Posted
- Attached to
- Cost Recovery Services
- Solicitation number
- RFI 40100-51762
- Issued by
- Davidson County, Tennessee
About this file
This Request for Information (RFI) is issued by the Tennessee Department of Transportation to assess vendor capability to meet state security requirements for a future solicitation involving Cost Recovery Services. The State seeks a vendor to manage cost recovery for damages to public highway property and incident response/cleanup on Tennessee's highway system, including interstate and state highways. Responses to the RFI are a prerequisite for participation in any future solicitations related to this project. The RFI written questions and comments deadline is December 8, 2026, with the state's response to written questions due December 11, 2026, and the RFI response deadline set for December 18, 2026. All responses must include a signed written confirmation from legal counsel, the Chief Executive Officer, or an authorized designee confirming the respondent's ability or inability to comply with the requirements outlined in Attachment A. Responses to this RFI do not create any contract rights, and the state will not pay for costs associated with responding.
The RFI does not establish pricing terms, set-asides, or contract award amounts, as it is an information-gathering instrument. Respondents must address mandatory information technology security requirements, including ensuring all state data is housed in the continental United States with access limited to US-based resources only, encryption compliance with FIPS 140-2 or 140-3 standards, and annual NIST audits assessing compliance with NIST Special Publication 800-53 security controls. Additional requirements include annual penetration testing and vulnerability assessments, maintenance of business continuity and disaster recovery capabilities with a Recovery Time Objective of one hour and Recovery Point Objective of twenty-four hours, Payment Card Industry Data Security Standard certification, Comptroller of the Treasury audit compliance, Personally Identifiable Information protection per the Gramm-Leach-Bliley Act, and compliance with the State of Tennessee's Enterprise Artificial Intelligence Policy prohibiting use of state data through unapproved AI tools and platforms.
View the file
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
STATE OF TENNESSEE
TENNESSEE DEPARTMENT OF TRANSPORTATION
REQUEST FOR INFORMATION
FOR
COST RECOVERY SERVICES
RFI # 40100-51762
November 18, 2026
1. STATEMENT OF PURPOSE:
The State of Tennessee, Department of Transportation issues this Request for Information (“RFI”) for the purpose of assessing the ability of Respondents to meet the State security requirements of a future solicitation for Cost Recovery Services. We appreciate your input and participation in this process.
2. BACKGROUND:
The Department of Transportation is seeking a vendor to manage cost recovery for damages to public highway property and incident response/cleanup on Tennessee's highways, including interstate highways and other state highways (the "State Highway System"), as applicable.
TDOT issues this RFI to gather information from potential vendors to understand the Respondent’s ability or describing Respondent’s inability to comply with the requirements set forth in Attachment A.
3. COMMUNICATIONS:
3.1. Please submit your response to this RFI to:
Camryn Cholewinski, Procurement and Contracts Division Tennessee Department of Transportation Tennessee Tower, 11th floor 312 Rosa L Parks Ave, Nashville, TN 37243 TDOT.RFP@tn.gov
3.2. Please feel free to contact the Tennessee Department of Transportation with any questions regarding this RFI. The main point of contact will be:
mailto:TDOT.RFP@tn.gov
Camryn Cholewinski, Procurement and Contracts Division Tennessee Department of Transportation Tennessee Tower, 11th floor 312 Rosa L Parks Ave, Nashville, TN 37243 TDOT.RFP@tn.gov
3.3. Please reference RFI # 40100-51762 with all communications to this RFI.
4. RFI SCHEDULE OF EVENTS:
EVENT
TIME
(Central Time Zone)
DATE
(all dates are State business days)
1. RFI Issued 11/18/2026
2.
RFI Written Questions and Comments Deadline
12/8/2026
3.
RFI State Response to Written Questions and Comments Deadline
12/11/2026
4. RFI Response Deadline 12/18/2026
5. GENERAL INFORMATION:
5.1. Responding to this RFI is a prerequisite for responding to any future solicitations related to this project. Responses to this RFI will not create any contract rights and responses to this RFI will become property of the State.
5.1.1 All Respondents will be required to provide a signed written response from their legal counsel, or Chief Executive Officer or their authorized designee legally empowered to bind the respondent to the provisions of the solicitation and resulting contract (if awarded), either confirming Respondent’s ability or describing Respondent’s inability to comply with the requirements set forth in Attachment A.
5.2. The information gathered during this RFI is part of an ongoing procurement. In order to prevent an unfair advantage among potential respondents, the RFI responses will not be available until after the completion of evaluation of any responses, proposals, or bids resulting from a Request for Qualifications, Request for Proposals, Invitation to Bid or other procurement method. In the event that the state chooses not to go further in the procurement process and responses are never evaluated, the responses to the procurement including the responses to the RFI, will be considered confidential by the State.
5.3. The State will not pay for any costs associated with responding to this RFI.
mailto:TDOT.RFP@tn.gov
6. INFORMATIONAL FORMS:
The State is requesting the following information from all interested parties. Attachment A are being provided as information only for the Respondent to provide an informed response. Please fill out the following forms:
RFI #40100-51762
TECHNICAL INFORMATIONAL FORM
1. RESPONDENT LEGAL ENTITY NAME:
2. RESPONDENT CONTACT PERSON:
Name, Title:
Address:
Phone Number:
Email:
3. Provide a signed written response from either the legal counsel, Chief Executive Officer, or their authorized designee legally empowered to bind the respondent to the provisions of the solicitation and resulting contract (if awarded), either confirming the Respondent’s ability or describing the Respondent’s inability to comply with the requirements outlined in Attachment A.
4. If Contactor cannot meet the following requirement specified in Attachment A, “The Contractor shall ensure that all State Data is housed in the continental United States, inclusive of backup data. All State data must remain in the United States, regardless of whether the data is processed, stored, in-transit, or at rest. Access to State data shall be limited to US-based (onshore) resources only,” provide the name of the host country(ies) where any data may be processed or stored, in-transit, or at rest.
Attachment A
Notable Terms and Conditions Requirements:
(This Attachment does not represent all State of Tennessee contractual Terms and Conditions, but reflects those the State requires acknowledgement of the Respondent’s ability, or inability, to comply with to determine inclusion in a future procurement for the services referenced in this
RFI).
D.#. Information Technology Security Requirements (State Data, Audit, and Other Requirements).
a. “State Data” is any and all data that can be accessed, processed, generated, including derivative works, stored, or hosted by the Contractor in performance of this Contract.” The Contractor shall protect State Data as follows:
(1) The Contractor shall ensure that all State Data is housed in the continental United States, inclusive of backup data. All State Data must remain in the United States, regardless of whether the data is processed, stored, in-transit, or at rest. Access to State Data shall be limited to US-based (onshore) resources only.
All system and application administration must be performed in the continental United States.
Configuration or development of software and code is permitted outside of the United States.
However, software applications designed, developed, manufactured, or supplied by persons owned or controlled by, or subject to the jurisdiction or direction of, a foreign adversary, which the U.S. Secretary of Commerce acting pursuant to 15 C.F.R. § 7 has defined to include the People’s Republic of China, among others are prohibited. Any testing of code outside of the United States must use fake data. A copy of production data may not be transmitted or used outside the United States.
(2) The Contractor shall encrypt State Data at rest and in transit using the current version of Federal Information Processing Standard (“FIPS”) 140-2 or 140-3 (or current applicable version) validated encryption technologies. The State shall control all access to encryption keys. The Contractor shall provide installation and maintenance support at no cost to the State.
(3) The Contractor shall maintain, obtain, or undergo the following third-party information security audit(s) for both the Contractor and the Contractor’s processing environment containing State Data. The Contractor shall ensure that each assessment remains current and valid throughout the term of the Contract.
i. NIST Audit - The Contractor and Contractor’s processing environment containing State Data shall undergo an annual independent audit assessing compliance with the privacy and security controls established in the National Institute of Standards and Technology (NIST) Special Publication 800-53. The audit shall be conducted by a qualified independent assessor, which may include a reputable CPA firm, cybersecurity firm, or other organization with demonstrated expertise in assessing NIST control compliance. The audit must evaluate compliance with the security controls defined in the NIST Special Publication 800- 53B moderate-impact security control baseline or a higher-impact baseline.
(4) Upon request by the State or the Comptroller of the Treasury, and within thirty (30) days of completion or receipt of any audit required under Contract Section D.#,a.(3) the Contractor shall provide the State or the Comptroller of the Treasury with the following documentation and deliverables. The Contractor shall ensure that all documentation remains current, complete, and accurate throughout the term of the Contract.
i. NIST Audit
1) The audit report in its entirety;
2) A corrective action plan describing each identified deficiency, planned remediation steps, and anticipated completion dates.
Upon request by the State or the Comptroller of the Treasury, the Contractor shall also provide current Subcontractor certifications, reports, and related deliverables pertaining to services provided under this Contract within thirty (30) days. If any certification, authorization, examination, or assessment required under this Contract for any Subcontractor supporting this
Contract lapses, expires, is suspended, or is revoked, the Contractor shall notify the State in writing within five (5) business days of learning of the status change and provide: (i) the effective date and reason; (ii) the services and State Data affected; and (iii) the Contractor’s corrective action plan and interim risk mitigations.
No additional funding shall be allocated for these examinations as they are included in the Maximum Liability of this Contract.
(5) The Contractor must annually perform Penetration Tests and Vulnerability Assessments against its Processing Environment per the NIST 800-115 definition. “Processing Environment” shall mean the combination of software and hardware on which the Application runs. “Application” shall mean the computer code that supports and accomplishes the State’s requirements as set forth in this Contract. “Penetration Tests” shall be in the form of attacks on the Contractor’s computer system, with the purpose of discovering security weaknesses which have the potential to gain access to the Processing Environment’s features and data.
The “Vulnerability Assessment” shall be designed and executed to define, identify, and classify the security holes (vulnerabilities) in the Processing Environment. The Contractor shall allow the State, at its option, to perform Penetration Tests and Vulnerability Assessments on the Processing Environment. The Contractor shall provide a letter of attestation on its processing environment that penetration tests and vulnerability assessments has been performed on an annual basis and taken corrective action to evaluate and address any findings.
In the event of an unauthorized disclosure or unauthorized access to State Data, the State Strategic Technology Solutions (STS) Security Incident Response Team (SIRT) must be notified and engaged by calling the State Customer Care Center (CCC) at 615-741-1001. Any such event must be reported by the Contractor within twenty-four (24) hours after the unauthorized disclosure has come to the attention of the Contractor.
(6) If a breach has been confirmed a fully un-modified third-party forensics report must be supplied to the State and through the STS SIRT. This report must include indicators of compromise (IOCs) as well as plan of actions for remediation and restoration. Contractor shall take all necessary measures to halt any further Unauthorized Disclosures.
(7) Upon State request, the Contractor shall provide a copy of all State Data it holds. The Contractor shall provide such data on media and in a format determined by the State
(8) Upon termination of this Contract and in consultation with the State, the Contractor shall destroy, and ensure all subcontractors shall destroy, all State Data it holds (including any copies such as backups) in accordance with the current version of National Institute of Standards and Technology (“NIST”) Special Publication 800-88. The Contractor shall provide a written confirmation of destruction to the State within ten (10) business days after destruction.
(9) The Contractor shall be certified to host Payment Card Industry (PCI) data in accordance with the current version of PCI DSS (Data Security Standard) maintained by the PCI Security Standards Council.
b. Minimum Requirements
(1) The Contractor shall implement and maintain privacy and security controls that follow the guidelines set forth in NIST 800-53, “Security and Privacy Controls for Federal Information Systems and Organizations,” as amended from time to time. The Contractor shall meet annually, or as otherwise agreed, with the State to review the implementation of this Section. Upon request from the State or the Comptroller of the Treasury, the Contractor must provide the State or the Comptroller of the Treasury with a System Security Plan that describes how the Contractor implemented privacy and security controls within NIST 800-53.
(2) The Contractor agrees to maintain the Application so that it will run on a current, manufacturer-supported Operating System. “Operating System” shall mean the software that supports a computer's basic functions, such as scheduling tasks, executing applications, and controlling peripherals.
(3) If the Application requires middleware or database software, Contractor shall maintain middleware and database software versions that are always fully compatible with current versions of the Operating System and Application to ensure that security vulnerabilities are not introduced.
(4) In the event of drive/media failure, if the drive/media is replaced, it remains with the State and it is the State’s responsibility to destroy the drive/media, or the Contractor shall provide written confirmation of the sanitization/destruction of data according to NIST 800-88.
c. Business Continuity Requirements.
The Contractor shall maintain sets of documents, instructions, and procedures that enable the Contractor to respond to accidents, disasters, emergencies, or threats without any stoppage or hindrance to key operations (“Business Continuity Requirements”). Business Continuity Requirements shall include:
(1) Disaster Recovery Capabilities
Disaster Recovery Capabilities refer to the actions the Contractor takes to meet the Recovery Point Objective (RPO) and Recovery Time Objective (RTO) defined below. Disaster Recovery Capabilities shall comply with NIST SP 800-53 Rev. 5, Contingency Planning (CP) controls, (moderate baseline controls) including CP-1 through CP-10, as applicable, and shall ensure continuity of operations for critical systems and services.
i. Recovery Point Objective (RPO)
The RPO is defined as the maximum targeted period in which data might be lost from an IT service due to a major incident: TWENTY-FOUR (24) HOURS
ii. Recovery Time Objective (RTO)
The RTO is defined as the targeted duration of time and service level within which a business process must be restored after a disruption in order to avoid unacceptable consequences: ONE (1) HOUR
Commented [LS1]: Per FA template instructions, this belongs here.
(2) Disaster Recovery Plan
The Contractor and Subcontractor(s) shall maintain a documented Disaster Recovery Plan aligned with NIST SP 800-53 CP controls (e.g., CP-2: Contingency Plan, CP-4: Contingency Plan Testing, CP-6: Alternate Storage Site). The plan shall include, at minimum:
i. Identification and prioritization of critical systems, applications, and dependencies
ii. Backup and restoration procedures
iii. Roles, responsibilities, and communication protocols
iv. Periodic review and maintenance procedures
The Contractor shall provide a summary of the Disaster Recovery Plan to the State upon request.
(3) Disaster Recovery Testing
The Contractor and Subcontractor(s) shall perform at least one Disaster Recovery Test every 365 days. A Disaster Recovery Test shall verify the effectiveness of restoration procedures executed after a critical IT failure or disruption. Success shall be def ined as demonstrating the ability to meet the State’s RPO and RTO objectives.
(4) Reporting
The Contractor shall provide written confirmation to the State after each Disaster Recovery Test, verifying that the Contractor’s Disaster Recovery Capabilities meet the RPO and RTO requirements.
d. Comptroller Audit Requirements.
Upon reasonable notice and at any reasonable time, the Contractor agrees to allow the Comptroller of the Treasury, or the Comptroller’s duly appointed representatives, to perform information technology control audits of the Contractor’s information technology hosting and processing environment used by the Contractor to provide services under this Contract. The audit may evaluate whether the Contractor has implemented appropriate privacy and security controls consistent with NIST Special Publication 800-53, including controls generally classified as general controls and application controls. The audit may also assess whether those controls are designed and operating effectively and whether the Contractor is complying with applicable policies, laws, and regulations.
For purposes of this section:
General Controls are policies, procedures, and technical mechanisms that support the overall operation and integrity of information systems and applications, including areas such as access security, change management, system development, backup and recovery, and system maintenance.
Application Controls are the automated or manual controls built into specific applications to ensure the completeness, accuracy, authorization, and validity of data and transactions processed by those applications.
The audit may include, but is not limited to:
1) Review and evaluation of independent assurance deliverables required under Contract Section
D.a.(4). to determine whether the Contractor’s or Subcontractor’s control environment and related safeguards are designed and operating effectively;
2) Review of documentation describing the Contractor’s information technology control environment, policies, and procedures;
3) Interviews with technical and management personnel responsible for implementing, monitoring, and maintaining information technology controls;
4) Inspection of technical, administrative, or physical controls implemented to protect State Data and support service delivery under this Contract;
5) Review of relevant transaction logs, audit trails, vulnerability scans, or other supporting evidence necessary to verify compliance with applicable control requirements; and
6) Performance of other audit procedures deemed necessary by the Comptroller of the Treasury to verify compliance with applicable federal or state laws, regulations, or policies, or to assess the adequacy and effectiveness of the Contractor’s control environment.
The Contractor shall ensure that its Subcontractors cooperate and provide reasonable access to information or personnel necessary for the audit to the extent such information pertains to the services provided under this Contract.
The Contractor must have a process for correcting control deficiencies that were identified in the Comptroller of the Treasury’s information technology audit. For any audit issues identified, the Contractor shall submit a corrective action plan to the Comptroller of the Treasury which addresses the actions taken, or to be taken, and the anticipated completion date in response to each of the audit issues and related recommendations of the Comptroller of the Treasury. The corrective action plan shall be provided to the Comptroller of the Treasury upon request from the Comptroller of the Treasury and within 30 days from the issuance of the audit report or communication of the audit issues and recommendations. Upon request from the Comptroller of the Treasury, the Contractor shall provide documentation and evidence that the audit issues were corrected.
Each party shall bear its own expenses incurred while conducting the information technology controls audit.
E. SPECIAL TERMS AND CONDITIONS
E.#. Personally Identifiable Information. While performing its obligations under this Contract, Contractor may have access to Personally Identifiable Information held by the State (“PII”). For the purposes of this Contract, “PII” includes “Nonpublic Personal Information” as that term is defined in Title V of the Gramm-Leach-Bliley Act of 1999 or any successor federal statute, and the rules and regulations thereunder, all as may be amended or supplemented from time to time (“GLBA”) and personally identifiable information and other data protected under any other applicable laws, rule or regulation of any jurisdiction relating to disclosure or use of personal information (“Privacy Laws”). Contractor agrees it shall not do or omit to do anything which would cause the State to be in breach of any Privacy Laws. Contractor shall, and shall cause its employees, agents and representatives to: (i) keep PII confidential and may use and disclose PII only as necessary to carry out those specific aspects of the purpose for which the PII was disclosed to Contractor and in accordance with this Contract, GLBA and Privacy Laws; and (ii) implement and maintain appropriate technical and organizational measures regarding information security to: (A) ensure the security and confidentiality of PII; (B) protect against any threats or hazards to the security or integrity of PII;
and (C) prevent unauthorized access to or use of PII. Contractor shall immediately notify State: (1) of any disclosure or use of any PII by Contractor or any of its employees, agents and representatives in breach of this Contract; and (2) of any disclosure of any PII to Contractor or its employees, agents and representatives where the purpose of such disclosure is not known to Contractor or its employees, agents and representatives. The State reserves the right to review Contractor's policies and procedures used to maintain the security and confidentiality of PII and Contractor shall, and cause its employees, agents and representatives to, comply with all reasonable requests or directions from the State to enable the State to verify or ensure that Contractor is in full compliance with its obligations under this Contract in relation to PII. Upon termination or expiration of the Contract or at the State’s direction at any time in its sole discretion, whichever is earlier, Contractor shall immediately return to the State any and all PII which it has received under this Contract and shall destroy all records of such PII.
Commented [CC2]: There was no separation here just different letter so I added this. I’m not sure it is correct but
I looked at the other RFI’s.
Commented [LS3R2]: Section E is “Special” Terms and
Conditions while Section D is “Mandatory” Terms and
Conditions
I am not sure if these sections are part of the challenges of our IT procurements so will let @Kenny weigh in on their inclusion in the RFI and how it needs to be laid out. Since they ultimately will end up different # on the final FA, I would leave it as a # sign on this document.
Commented [KW4R2]: OK to leave in here
The Contractor shall report to the State any instances of unauthorized access to or potential disclosure of PII in the custody or control of Contractor (“Unauthorized Disclosure”) that come to the Contractor’s attention. Any such report shall be made by the Contractor within twenty-four (24) hours after the Unauthorized Disclosure has come to the attention of the Contractor. Contractor shall take all necessary measures to halt any further Unauthorized Disclosures. The Contractor, at the sole discretion of the State, shall provide no cost credit monitoring services for individuals whose PII was affected by the Unauthorized Disclosure. The Contractor shall bear the cost of notification to all individuals affected by the Unauthorized Disclosure, including individual letters and public notice. The remedies set forth in this Section are not exclusive and are in addition to any claims or remedies available to this State under this Contract or otherwise available at law.
The obligations set forth in this Section shall survive the termination of this Contract.
E.#. Artificial Intelligence (AI) Use and Compliance Requirements. The Contractor agrees that any product, service, or solution incorporating Artificial Intelligence (AI), including Generative AI (GenAI), procured under this Agreement shall comply fully with the State of Tennessee’s Enterprise Artificial Intelligence Policy (Policy 200-POL-007), available at:
https://www.tn.gov/content/dam/tn/finance/artificial-intelligence/Enterprise_Artificial_Intelligence_Policy.pdf
The Contractor further agrees to the following:
a. Data Privacy and Security
Contractor shall not use, access, store, transmit, or process any State Data—including but not limited to confidential, privileged, personally identifiable information (PII), protected health information (PHI), Payment Card Industry (PCI) data, criminal justice information (CJIS), federal tax information (FTI), Centers for Medicare & Medicaid Services (CMS) data, Social Security Administration (SSA) data, Family Education Rights & Privacy Act (FERPA) data, or internal communications—through any AI tools or platforms unless:
(1) The AI tool is explicitly approved in writing by the State.
(2) The tool is operated within a secure State-controlled or approved environment.
b. Prohibition on Model Training
Contractor shall not use State Data to train, fine-tune, or otherwise improve AI models, unless expressly authorized in writing by the State and in accordance with Policy No. 200-
OL-007.
c. Transparency and Accountability
Contractor shall clearly disclose when AI tools are used in providing services or generating content on behalf of the State. Contractor is responsible or the accuracy, reliability, and appropriateness of all AI-generated outputs.
d. Use of Approved Tools Only
Only State-approved AI platforms, systems, or services may be used in the performance of this contract. Use of public, consumer, or non-State-managed AI platforms (e.g., ChatGPT, Google Gemini, etc.) with State Data is strictly prohibited unless authorized in writing.
e. Ongoing Compliance and Risk Mitigation https://www.tn.gov/content/dam/tn/finance/artificial-intelligence/Enterprise_Artificial_Intelligence_Policy.pdf https://www.tn.gov/content/dam/tn/finance/artificial-intelligence/Enterprise_Artificial_Intelligence_Policy.pdf
Contractor shall ensure continued compliance with evolving State and federal regulations related to AI. The State reserves the right to audit or review AI usage under this Contract at any time.
f. Indemnification
Contractor shall further indemnify and hold harmless the State in accordance with the Hold Harmless section of this Agreement for any unauthorized disclosure, misuse, or compromise of State Data resulting from AI-related processing that violates this Contract or State policy.
File details come from the government source that posted it. Updated .