HEALTH & WELFARE: $5.55 per hour, up to 40 hours per week, or $222.00 per week or $962.00 per month HEALTH & WELFARE EO 13706: $5.09 per hour, up to 40 hours per week, or $203.60 per week, or $882.27 per month* *This rate is to be used only when compensating employees for performance on an SCA- covered contract also covered by EO 13706, Establishing Paid Sick Leave for Federal Contractors. A contractor may not receive credit toward its SCA obligations for any paid sick leave provided pursuant to EO 13706. | VACATION: 2 weeks paid vacation after 1 year of service with a contractor or successor, 3 weeks after 8 years, and 4 weeks after 15 years. Length of service includes the whole span of continuous service with the present contractor or successor, wherever employed, and with the predecessor contractors in the performance of similar work at the same Federal facility. (See 29 CFR 4.173) | HOLIDAYS: A minimum of eleven paid holidays per year: New Year's Day, Martin Luther King Jr.'s Birthday, Washington's Birthday, Memorial Day, Juneteenth National Independence Day, Independence Day, Labor Day, Columbus Day, Veterans' Day, Thanksgiving Day, and Christmas Day. (A contractor may substitute for any of the named holidays another day off with pay in accordance with a plan communicated to the employees involved.) (See 29 CFR 4.174) THE OCCUPATIONS WHICH HAVE NUMBERED FOOTNOTES IN PARENTHESES RECEIVE THE FOLLOWING: 1) COMPUTER EMPLOYEES: This wage determination does not apply to any individual employed in a bona fide executive, administrative, or professional capacity, as defined in 29 C.F.R. Part 541. (See 41 C.F.R. 6701(3)). Because most Computer Systems Analysts and Computer Programmers who are paid at least $27.63 per hour (or at least $684 per week if paid on a salary or fee basis) likely qualify as exempt computer professionals under 29 U.S.C. 213(a)(1) and 29 U.S.C. 213(a)(17), this wage determination may not include wage rates for all occupations within those job families. In such instances, a conformance will be necessary if there are nonexempt employees in these job families working on the contract. Job titles vary widely and change quickly in the computer industry, and are not determinative of whether an employee is an exempt computer professional. To be exempt, computer employees who satisfy the compensation requirements must also have a primary duty that consists of: (1) The application of systems analysis techniques and procedures, including consulting with users, to determine hardware, software or system functional specifications; (2) The design, development, documentation, analysis, creation, testing or modification of computer systems or programs, including prototypes, based on and related to user or system design specifications; (3) The design, documentation, testing, creation or modification of computer programs related to machine operating systems; or (4) A combination of the aforementioned duties, the performance of which requires the same level of skills. (29 C.F.R. 541.400). Any computer employee who meets the applicable compensation requirements and the above duties test qualifies as an exempt computer professional under both section 13(a)(1) and section 13(a)(17) of the Fair Labor Standards Act. (Field Assistance Bulletin No. 2006-3 (Dec. 14, 2006)). Accordingly, this wage determination will not apply to any exempt computer employee regardless of which of these two exemptions is utilized. 2) AIR TRAFFIC CONTROLLERS AND WEATHER OBSERVERS - NIGHT PAY & SUNDAY PAY: If you work at night as part of a regular tour of duty, you will earn a night differential and receive an additional 10% of basic pay for any hours worked between 6pm and 6am. If you are a full-time employed (40 hours a week) and Sunday is part of your regularly scheduled workweek, you are paid at your rate of basic pay plus a Sunday premium of 25% of your basic rate for each hour of Sunday work which is not overtime (i.e. occasional work on Sunday outside the normal tour of duty is considered overtime work). ** HAZARDOUS PAY DIFFERENTIAL ** An 8 percent differential is applicable to employees employed in a position that represents a high degree of hazard when working with or in close proximity to ordnance, explosives, and incendiary materials. This includes work such as screening, blending, dying, mixing, and pressing of sensitive ordnance, explosives, and pyrotechnic compositions such as lead azide, black powder and photoflash powder. All dry-house activities involving propellants or explosives. Demilitarization, modification, renovation, demolition, and maintenance operations on sensitive ordnance, explosives and incendiary materials. All operations involving re-grading and cleaning of artillery ranges. A 4 percent differential is applicable to employees employed in a position that represents a low degree of hazard when working with, or in close proximity to ordnance, (or employees possibly adjacent to) explosives and incendiary materials which involves potential injury such as laceration of hands, face, or arms of the employee engaged in the operation, irritation of the skin, minor burns and the like; minimal damage to immediate or adjacent work area or equipment being used. All operations involving, unloading, storage, and hauling of ordnance, explosive, and incendiary ordnance material other than small arms ammunition. These differentials are only applicable to work that has been specifically designated by the agency for ordnance, explosives, and incendiary material differential pay. ** UNIFORM ALLOWANCE ** If employees are required to wear uniforms in the performance of this contract (either by the terms of the Government contract, by the employer, by the state or local law, etc.), the cost of furnishing such uniforms and maintaining (by laundering or dry cleaning) such uniforms is an expense that may not be borne by an employee where such cost reduces the hourly rate below that required by the wage determination. The Department of Labor will accept payment in accordance with the following standards as compliance: The contractor or subcontractor is required to furnish all employees with an adequate number of uniforms without cost or to reimburse employees for the actual cost of the uniforms. In addition, where uniform cleaning and maintenance is made the responsibility of the employee, all contractors and subcontractors subject to this wage determination shall (in the absence of a bona fide collective bargaining agreement providing for a different amount, or the furnishing of contrary affirmative proof as to the actual cost), reimburse all employees for such cleaning and maintenance at a rate of $3.35 per week (or $.67 cents per day). However, in those instances where the uniforms furnished are made of """"wash and wear"""" materials, may be routinely washed and dried with other personal garments, and do not require any special treatment such as dry cleaning, daily washing, or commercial laundering in order to meet the cleanliness or appearance standards set by the terms of the Government contract, by the contractor, by law, or by the nature of the work, there is no requirement that employees be reimbursed for uniform maintenance costs. ** SERVICE CONTRACT ACT DIRECTORY OF OCCUPATIONS ** The duties of employees under job titles listed are those described in the """"Service Contract Act Directory of Occupations"""", Fifth Edition (Revision 1), dated September 2015, unless otherwise indicated. ** REQUEST FOR AUTHORIZATION OF ADDITIONAL CLASSIFICATION AND WAGE RATE, Standard Form 1444 (SF-1444) ** Conformance Process: The contracting officer shall require that any class of service employee which is not listed herein and which is to be employed under the contract (i.e., the work to be performed is not performed by any classification listed in the wage determination), be classified by the contractor so as to provide a reasonable relationship (i.e., appropriate level of skill comparison) between such unlisted classifications and the classifications listed in the wage determination (See 29 CFR 4.6(b)(2)(i)). Such conforming procedures shall be initiated by the contractor prior to the performance of contract work by such unlisted class(es) of employees (See 29 CFR 4.6(b)(2)(ii)). The Wage and Hour Division shall make a final determination of conformed classification, wage rate, and/or fringe benefits which shall be paid to all employees performing in the classification from the first day of work on which contract work is performed by them in the classification. Failure to pay such unlisted employees the compensation agreed upon by the interested parties and/or fully determined by the Wage and Hour Division retroactive to the date such class of employees commenced contract work shall be a violation of the Act and this contract. (See 29 CFR 4.6(b)(2)(v)). When multiple wage determinations are included in a contract, a separate SF-1444 should be prepared for each wage determination to which a class(es) is to be conformed. The process for preparing a conformance request is as follows: 1) When preparing the bid, the contractor identifies the need for a conformed occupation(s) and computes a proposed rate(s). 2) After contract award, the contractor prepares a written report listing in order the proposed classification title(s), a Federal grade equivalency (FGE) for each proposed classification(s), job description(s), and rationale for proposed wage rate(s), including information regarding the agreement or disagreement of the authorized representative of the employees involved, or where there is no authorized representative, the employees themselves. This report should be submitted to the contracting officer no later than 30 days after such unlisted class(es) of employees performs any contract work. 3) The contracting officer reviews the proposed action and promptly submits a report of the action, together with the agency's recommendations and pertinent information including the position of the contractor and the employees, to the U.S. Department of Labor, Wage and Hour Division, for review (See 29 CFR 4.6(b)(2)(ii)). 4) Within 30 days of receipt, the Wage and Hour Division approves, modifies, or disapproves the action via transmittal to the agency contracting officer, or notifies the contracting officer that additional time will be required to process the request. 5) The contracting officer transmits the Wage and Hour Division's decision to the contractor. 6) Each affected employee shall be furnished by the contractor with a written copy of such determination or it shall be posted as a part of the wage determination (See 29 CFR 4.6(b)(2)(iii)). Information required by the Regulations must be submitted on SF-1444 or bond paper. When preparing a conformance request, the """"Service Contract Act Directory of Occupations"""" should be used to compare job definitions to ensure that duties requested are not performed by a classification already listed in the wage determination. Remember, it is not the job title, but the required tasks that determine whether a class is included in an established wage determination. Conformances may not be used to artificially split, combine, or subdivide classifications listed in the wage determination (See 29 CFR 4.152(c)(1)).
FMLA Case Management System - UPDATED
Federal opportunity from Central Procurement Office • Tennessee Department of General Services. Place of performance: TN.
- Source
- Open on official portal →
- Solicitation
- tn_cpo__RFI 31903-00005
- Performance
- TN
- Response
- No due date posted
Point of Contact
Agency & Office
Applicable wage determinations
Best public WD match for the notice location and scope.
View more WD detail3 more WD matches and 359 more rate previews.↓
Description
1 STATE OF TENNESSEE DEPARTMENT OF HUMAN RESOURCES REQUEST FOR INFORMATION FOR FMLA CASE MANAGEMENT SYSTEM RFI # 31903-00005 APRIL 1, 2026 1. STATEMENT OF PURPOSE: The State of Tennessee, DEPARTMENT OF HUMAN RESOURCES issues this Request for Information (“RFI”) for the purpose of identifying qualified vendors capable of delivering a comprehensive, secure, and scalable technology solution to support the administration and management of Family and Medical Leave Act (FMLA) processes. The State seeks a modern platform that streamlines case management, automates eligibility determinations and workflows, ensures compliance with federal and state regulations, and enhances reporting and analytics capabilities. The solution must integrate seamlessly with existing enterprise resource planning (ERP), payroll, and HR systems while maintaining the highest standards for data security, privacy, and accessibility. Through this RFI, the State aims to evaluate available technologies and approaches that will improve operational efficiency, reduce administrative burden, and provide a consistent, transparent, and user-friendly experience for employees, managers, and HR professionals. We appreciate your input and participation in this process. 2. BACKGROUND: The State of Tennessee currently administers Family and Medical Leave Act (FMLA) processes through a combination of manual activities. Existing system limitations in reporting, automation, and integration with HR and payroll systems require manual workarounds and reduce overall operational efficiency. Additionally, the lack of a centralized platform to manage multiple leave types and related documentation creates challenges in maintaining case records. The State is seeking to better understand available solutions that can modernize FMLA administration, improve data accuracy and transparency, and support a more efficient and compliant process. 3. PROPOSED SOLUTIONS: DOHR is requested to review cloud-based software applications available to meet the needs addressed in the List of Business needs (Table 3.1) below. 2 Table 3.1 List of business needs Requirement # REQUIREMENT DESCRIPTION REQUIRED?* ("N" indicates Not Required) Abstract : The State is seeking information from qualified vendors on a technology solution to support the administration and management of Family and Medical Leave Act (FMLA) processes. The proposed solution should streamline case management, ensure regulatory compliance, enhance reporting capabilities, and integrate with existing HR and payroll systems. AUDIT & SECURITY 1 Security that meets all the requirements listed at the following location: https://www.tn.gov/finance/strategic-technology-solutions/strategic- technology-solutions/sts-security-policies.html. 2 Backup and recovery of the system that adheres to State regulations. 3 Audit trail, for changes in the system, including timestamp and user associated with the change. 4 Online tool designed to view audit trails. 5 History tables that maintain change information related to grant activity. 6 Date and time synchronization, which supports multiple time zones. 7 Confidential data encrypted at rest and in transit, using the current version of Federal Information Process Standard (“FIPS”) 140-3 or higher, specifically designed to safeguard PII, PHI, CMS, SSA, HIPAA and other confidential Federal and State data. 8 The Vendor shall maintain a current SOC 2 Type II report, issued by an independent AICPA-accredited auditing firm, covering the Security Trust Services Criteria at a minimum. The report must be dated within the most recent 12 months and applicable to all systems and environments supporting the proposed FMLA platform. The Vendor shall provide a copy of the report under NDA upon request and maintain SOC 2 Type II certification throughout the term of any resulting contract. 9 Ensures that all State data, including production, backup, and disaster recovery environments, is stored, processed, and maintained exclusively within the continental United States. 10 The solution shall comply with the Americans with Disabilities Act (ADA) and conform to Web Content Accessibility Guidelines (WCAG) 2.1 Level AA standards, ensuring accessibility for individuals with disabilities across all user-facing components. 11 Ability to manage access to screens and tables, data elements, functions, electronic documents, or case type. 12 The solution shall enforce a minimum password length of eight (8) characters for standard user accounts and fifteen (15) characters for service accounts, system administrator accounts, and system/application accounts. Service, system administrator, and system/application account passwords may be configured as non-expiring where justified and approved. 13 Provide a minimum of fourteen (14) days’ notice prior to expiration of password. 14 Provide the ability of security role to manage external user accounts ( i.e., log out users, reset passwords, disable log-on). 15 Provides the ability support Single Sign-On (SSO) for secure internal user authentication. 16 Supports Multi-Factor Authentication (MFA) for all user access, including configurable authentication methods and enforcement based on role, 3 risk, or access level. 17 Records unsuccessful logon attempts and allows for automatic lockout of accounts upon five (5) consecutive invalid login attempts. 18 Automatically deactivate user account upon System Administrator defined time of inactivity (days/weeks). 19 Provide ability to restrict access by IP address. 20 Ability to generate security reports reflecting authorized use, security breaches or attempts. 21 Ability to segment user access/roles by section. 22 Adherence to all legal and regulatory standards as needed by State of TN. 23 The vendor shall disclose whether the proposed solution includes any artificial intelligence (AI) or machine learning (ML) capabilities. If AI/ML functionality is included, the vendor shall provide a brief description of all features and their intended use. 24 The solution must ensure that all data used, generated, processed, or stored by AI components—including training data, prompts, metadata, model outputs, logs, and intermediate datasets—is stored exclusively within the United States. No AI-related data may be transmitted to, processed in, or stored in locations outside the United States at any time. 25 Any AI or ML components shall not train on, store, or share state-owned data with external systems, services, or models. The vendor shall describe all data flows and any third-party systems involved. 26 Any AI functionality of the system shall be fully or partially disabled if desired. The vendor shall describe the methods available for disabling AI and any impacts on system functionality. 27 The vendor shall identify whether the AI components used within the solution are proprietary, closed-source, open-source, or supplied by third-party providers. The vendor shall provide details regarding ownership, licensing, and dependencies. COMPATIBILITY 28 The solution must support all major modern web browsers running current stable versions (e.g., Microsoft Edge, Google Chrome, Mozilla Firefox). Compatibility must extend to browsers and environments that incorporate AI-assisted features or agents (e.g., ChatGPT-integrated browsers, Microsoft Edge with Copilot, Perplexity Comet, and similar tools). 29 The system should support cross-platform compatibility, ensuring equivalent functionality and user experience on desktop, mobile, and web environments. 30 Provide configurable and extensible tools to customize leave types, roles, fields, forms/templates, notifications, and workflows, including granular role-based access and page/data-level configuration. 31 System should have the ability to integrate State branding to all pages. 32 Provides integration with Microsoft Office applications, supporting 'cut and paste' functionality between Office application and system applications/modules. 33 The solution shall provide full compatibility with Adobe Acrobat, including support for Adobe Forms, electronic document signing workflows, and extraction of structured data from PDF files. INTERFRACES 34 Ability to interface (both incoming and outgoing data) with the State's 4 ERP system. 35 Ability to interface with external systems that provide the ability to validate or auto-populate information (electronic signature, email, etc.). 36 Ability to create custom data feeds using API. 37 Ability to provide real time notifications via O365 tools or options for Email and SMS notifications for high level actions/status changes. 38 The vendor must provide a detailed Data Dictionary for the data repository and a current Entity Relationship Diagram (ERD) 39 The system must include database connection capabilities for data extraction and transfer. At a minimum, the system must support connections to the database platforms of Oracle Database, Microsoft SQL Server, and Cloud-based databases hosted on AWS and Google Cloud 40 The solution should include built-in data connection capabilities (such as CData Connect AI or Windsor.ai) that enable seamless integration with AI analysis tools (such as Claude Cowork). These connections should support the ability to generate insights including reports, dashboards, graphs, predictions, and trend analyses. DASHBOARDS & REPORTING 41 Ability for users within a specific group to view a shared dashboard, including case status (upcoming due dates, overdue status, # cases open, etc.). 42 Dashboards and reports shall be available based on employee's assigned cases. 43 Dashboards and reports shall be available for leave hours used on a global basis and filterable down to specific case. 44 Dashboards and reporting shall be available detailing an anticipated return date for each case. 45 Dashboards and reporting shall be available for cases nearing the end of entitlement. 46 Dashboard and reporting shall be available for outstanding FMLA actions, deadlines, and escalations. 47 System should have the ability to audit logs of actions taken by users on a case level. 48 Ability to view cases on a system level and filter by defined variables (Agency, department, etc.). 49 Native low-code/no-code reporting with the ability to identify specific fields and filters. 50 Allow users to customize dashboards by selecting specific criteria ( e.g., cases by region, agency, leave type, coordinator or status, filter by open/close). 51 Ability to provide predictive analytics to use historical data to predict outcomes or identify patterns. 52 Allow display of KPIs such as average compliance rate, case closure rates, workload distribution, etc. 53 Include predictive search or keyword-based search capabilities by coordinator name, employee name, date range, leave type, and other parameters. 54 Ability to retrieve and view all historical cases linked to a person/ coordinator, including previous FMLA cases, eligibility and qualifications. 55 Ability to generate reports for public record requests based on various parameters (leave type, paid time off, etc.). 56 Ability to report leave types and quantities entered to ERP timesheets for employees and by requests. 5 57 Alert coordinator and/or interested parties in which employee exceeds certified FMLA frequency/duration; recertification required. 58 System shall be able to indicate when an employee has timesheet exceptions in ERP system. N 59 System should log actions by logged in user. DOCUMENT SOLUTIONS 60 Ability to store documents by case (including emails, images, etc.). 61 Ability to retain and destroy documents per records disposition authorization. 62 Ability to upload documents of multiple file types. 63 Ability to view and edit documents within the platform. 64 System must have a centralized repository for all case-related documents, with the ability to attach and update files. 65 System must support mass import of legacy data and documents with automated mapping of existing fields to system fields for consistency. 66 System should give the option to redact sensitive information before sharing files. 67 Ability to version control for FMLA request documents by maintaining a record of past requests and tracking actions taken on the case. 68 Ability to view historical cases based on employee. 69 Ability to create employee or user checklists to ensure compliance with FMLA requirements. N 70 Ability to create custom document templates by leave type. 71 Notification templates must be editable by Human Resources or other authorized personnel. 72 Ability to create common reusable forms that detail determinations and include specific information for the case. 73 Ability to bulk download and upload case files. CALENDAR SYNCING 74 Ability to sync calendars to Outlook/Teams within the platform. 75 Ability to track deadlines and send relevant notifications during workflow intervals. 76 System should send reminders for key deadlines to a defined mailing list at set intervals. WORKFLOW 77 System must be configured to follow and comply with all FMLA requirements. 78 System must support multiple FMLA request channels (employee self-service, HR initiation, manager initiation). 79 System should have the ability to create case requests to specific FMLA type or allow for a general request with comments and the FMLA type will be determined during FMLA workflow. 80 System should allow for alternative email for communications regarding the case request. 81 System must automatically trigger the FMLA eligibility review workflow upon request submission. 82 Workflow must validate employee eligibility data pulled from the ERP (tenure, hours worked, job status). 83 System should determine leave type based on details of request and applicability of state policy and FMLA requirements. 84 System should allow for audit of logic for case determinations. 85 System should allow for administrative intervention if case eligibility warrants a change of status. 6 86 System must support auto
Pricing and bid posture
Contractor-side estimate from visible notice metadata, NAICS/PSC, contract type, schedule hints, and BidPulsar workpaper assumptions. Not an IGCE, incumbent price, award value, or government budget.
This advisory bid range is visible page text for contractors and search engines: it summarizes the modeled floor, target, and premium bid posture for this solicitation.
Market snapshot
Baseline awarded-market signal across all contracting (sample of 400 recent awards; refreshed periodically).
Files
Files size/type shown when available.
BidPulsar Analysis
A practical, capture-style breakdown of fit, requirements, risks, and next steps.
Central Procurement Office issued solicitation FMLA Case Management System. 1 STATE OF TENNESSEE DEPARTMENT OF HUMAN RESOURCES REQUEST FOR INFORMATION FOR FMLA CASE MANAGEMENT SYSTEM RFI # 31903-00005 APRIL 1, 2026 1. STATEMENT OF PURPOSE: The State of Tennessee, DEPARTMENT OF HUMAN RESOURCES issues this Request for Information (“RFI”) for the purpose of identifying qualified vendors capable of delivering a comprehensive, secure, and scalable technology solution to support the administration and management of Family and Medical Leave Act (FMLA) processes.
1 STATE OF TENNESSEE DEPARTMENT OF HUMAN RESOURCES REQUEST FOR INFORMATION FOR FMLA CASE MANAGEMENT SYSTEM RFI # 31903-00005 APRIL 1, 2026 1. STATEMENT OF PURPOSE: The State of Tennessee, DEPARTMENT OF HUMAN RESOURCES issues this Request for Information (“RFI”) for the purpose of identifying qualified vendors capable of delivering a comprehensive, secure, and scalable technology solution to support the administration and management of Family and Medical Leave Act (FMLA) processes. The State seeks a modern platform that streamlines case management, automates eligibility determinations and workflows, ensures compliance with federal and state regulations, and enhances reporting and analytics capabilities. The solution must integrate seamlessly with existing enterprise resource planning (ERP), payroll, and HR systems while maintaining the highest standards for data security, privacy, and ac…
- Solicitation contractors with direct experience delivering comparable work for public buyers.
- FMLA Case Management System
- Review 1 linked source document.
- The State seeks a modern platform that streamlines case management, automates eligibility determinations and workflows, ensures compliance with federal and state regulations, and enhances reporting and analytics capabilities.
- The solution must integrate seamlessly with existing enterprise resource planning (ERP), payroll, and HR systems while maintaining the highest standards for data security, privacy, and ac...
- Download and review all official solicitation documents and addenda.
- Confirm submission format, due date, and delivery method with the buyer portal or notice.
- Prepare pricing, scope response, and required forms/certifications.
More BidPulsar strategy notesCompliance, pricing, teaming, risks, questions, and coverage notes
- Validate insurance, licensing, and any site-access requirements in the official documents.
- Price to the actual scope and staffing assumptions in the official documents.
- Watch for multi-site, overtime, after-hours, mobilization, or equipment cost drivers.
- Confirm whether the buyer expects all-inclusive pricing, line items, or optional services.
- Use subs or teaming partners if specialized staffing, equipment, or local coverage is required.
- Align subcontract scopes to compliance-sensitive work and document responsibilities clearly.
- Do not assume unstated requirements, contract duration, or evaluation factors.
- Are there mandatory site visits, staffing minimums, or licensing requirements?
- What exact documents and forms must be submitted at bid time?
- Are there incumbent, transition, or performance-reporting requirements not obvious from the summary?
Some notices publish limited source detail. Confirm these points before final bid/no-bid decisions.
- Exact due time is not confirmed in the current record.
- Set-aside status is not confirmed.
- Contracting office/contact is not clearly identified.
Service match
Optional support routes matched to this notice after the core solicitation details.
Other matched support routes↓
Related hubs & trends
Navigate the lattice: hubs for browsing, trends for pricing signals.