Labor Exchange Case Management Software

2026-11-03

STATEMENT OF PURPOSE : The State of Tennessee , Department of Labor and Workforce Development issues this Request for Information (“ RFI ”) for the purpose of Labor Exchange Case Management System . We appreciate your input and participation in this process . TECHNICAL INFORMATIONAL FORM 1 . RESPONDENT LEGAL ENTITY NAME : 2 . RESPONDENT CONTACT PERSON : Name , Title : Address : Phone Number : Email : 3 . BRIEF DESCRIPTION OF EXPERIENCE PROVIDING SIMILAR SCOPE OF SERVICES / PRODUCTS 4 . Indicate whether solution is Commercial Off The Shelf ( COTS ), COTS + custom services , or custom - built . If COTS , describe upgrade policy and frequency and whether tenant - level customizations will be retained through upgrades . 5 . Describe how you keep the System technology current ( e . g ., scheduled upgrades , modular architecture , use of modern frameworks , Continuous Integration / Continuous Delivery ( CI / CD ) practices . 6 . How frequently are major and minor releases deployed ? How do you handle deprecated features ? 7 . Explain options for backward compatibility and how customizations are preserved across upgrades . 8 . Provide a high - level roadmap ( next 12 – 24 months ) and examples of recent major enhancements 9 . Provide a detailed description of your change control / change management process , covering : Types of changes ( minor bug fix , configuration change , major enhancement , emergency patch ), approval workflows , and estimated lead times for each type ; How changes are regression tested ( unit , integration , User Acceptance Testing ( UAT ) and who performs UAT with the State ; Versioning , release notes , rollback plans , and communication procedures ; How State - requested changes are estimated , prioritized , and scheduled ( including change request forms , governance , and cost estimation practices ); Any chargeable vs non - chargeable change types ( e . g ., security patching vs new feature dev ). 10 . If AI is utilized , explain the AI governance and ethics methodology and model development , bias mitigation , explainability tools , and State override abilities . 11 . Describe APIs , authentication , webhooks , SFTP / SOAP , and example integrations with UI , TCAT , ETPL , and apprenticeship systems . 12 . The Contractor shall describe to the State the data migration methodology , validation , tools , and data mapping . 13 . The Contractor shall provide the State with a description of PII / SSN and other sensitive data are protected , and how the System supports auditability for federal / state audits . 14 . Provide examples timelines from initial build to implementation of functional software of similarly complex software of similar nature to the system requirements in this RFI .

Tennessee

2026-05-15