Recruitment and External Applicant Portal Solutions ICE RFI - Final_110926.pdf

RFI #: DHSICE_FY27_RECRUITPORTAL

REQUEST FOR INFORMATION (RFI) / SOURCES SOUGHT

SUBJECT: Recruitment, Applicant Tracking, External Applicant Portal and Position Affordability Solutions

PURPOSE OF REQUEST FOR INFORMATION

THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. THIS IS NOT A SOLICITATION FOR PROPOSALS.

The U.S. Immigration and Customs Enforcement (ICE) Office of Acquisitions (OAQ), Information Technology Division (ITD), is issuing this RFI on behalf of the Office of the Chief Information Officer (OCIO) solely for market research, planning, and information purposes. This RFI is issued solely for market research purposes in accordance with Revolutionary Federal Acquisition Regulation (FAR) Overhaul (RFO) Part 10. This RFI does not constitute a Request for Proposal (RFP), Request for Quotation (RFQ), Invitation for Bid (IFB), or other solicitation. The Government is under no obligation to issue a solicitation, award a contract, or reimburse respondents for any costs incurred. All costs associated with responding to this RFI will be solely at the interested party's expense. Responses will be used to assist the Government in acquisition planning, market research, and requirements development. The information provided in this RFI is subject to change and is not binding to the Government.

Proprietary Information: All submissions become the property of the Government and will not be returned. If submitting proprietary information, clearly mark “PROPRIETARY” on every applicable sheet and segregate such information from other portions of the response (e.g., via attachment). Respondents are responsible for adequately marking proprietary information in their response. All information received in response to this RFI that is marked “Proprietary” will be handled accordingly.

ICE seeks information on commercially available, configurable solutions that provide modern recruitment, applicant tracking, external applicant portal, workforce analytics, and budget-informed position affordability capabilities. ICE is interested in solutions that can support the recruitment and pre-Entry on Duty (EOD) hiring lifecycle while also providing authorized ICE users with integrated visibility into workforce costs, payroll projections, payroll adjustments to budget execution, and the affordability of proposed, modified, and existing positions.

The anticipated solution should complement, and not duplicate or replace, capabilities provided by current and future authoritative ICE and Federal systems, including human capital, payroll, financial management, position management, identity, personnel security, medical, onboarding, training, and enterprise analytics systems. The proposed solution is not intended to serve as the authoritative system of record for ICE financial transactions, payroll disbursements, obligations, expenditures, or budget execution.

The objective is to identify a solution that supports applicable federal hiring requirements and enables ICE to efficiently advertise positions, recruit candidates, manage workflows, and coordinate pre-employment activities. ICE is interested in both solutions that integrate with USA Staffing and USAJOBS and solutions that could perform some of those functions directly.

Respondents should state which model they propose, identify any dependency on USA Staffing, USA Hire, or USAJOBS, and describe how they address ICE-specific needs, including position tracking using ICE position identifiers, applicant visibility into pre-employment phases, workforce-planning, and affordability analysis. For budget-informed position affordability, ICE seeks capabilities that integrate authoritative HR, payroll, financial, workforce, and position-management data to support payroll forecasting, workforce costing, budget-to-actual comparisons, scenario analysis, and affordability assessments. The solution shall enable authorized users to evaluate whether proposed or existing position changes can be supported within available funding, approved budget controls, allotments, and established authorized position count and payroll targets by various types over applicable planning horizons. This RFI is intended to inform acquisition planning only. ICE is not requesting proposals, pricing commitments, or binding technical solutions at this time.

Consistent with Executive Order 14434, Inaugurating the Era of Super Intelligence (91 Fed. Reg.

63129, October 2, 2026), this RFI uses the terms "Super Intelligence" and "SI." For purposes of this RFI, SI means the technologies and systems encompassed by the term "artificial intelligence" as defined in 15 U.S.C. 9401(3), including machine learning, generative and agentic capabilities, chatbots and virtual assistants, automated decision support, and document classification. Respondents may use their own product terminology in their responses.

BACKGROUND, OBJECTIVES, AND SCOPE BOUNDARY

ICE seeks information on modern, user-friendly solutions across three related capability areas:

Talent Acquisition, an External Applicant Portal, and Budget-Informed Position Affordability.

ICE anticipates that a future Core Human Capital Management (HCM) platform may serve as the authoritative enterprise system for applicable human capital data and transactions. Accordingly, this RFI seeks information on complementary recruitment, applicant tracking, workflow, applicant-experience, and pre-Entry on Duty (EOD) capabilities that can operate effectively during any transition period and integrate with applicable current and future enterprise systems.

For purposes of this RFI, the Talent Acquisition and External Applicant Portal lifecycle begins with recruitment planning and vacancy intake and continues through recruitment, applicant processing, selection, pre-employment coordination, final-offer activities, and handoff to onboarding and training processes. Respondents shall identify the proposed solution’s functional boundary and specify whether each major function would serve as: (1) a system of record; (2) a workflow, portal, or user-experience layer; (3) an integration or data-exchange capability; or (4) an out-of-scope function supported by another system.

ICE also seeks information on Budget-Informed Position Affordability solutions that integrate with, but do not replace ICE’s existing financial management tools. These capabilities should support payroll projections, workforce costing, payroll adjustments to budget execution, scenario modeling, and affordability analysis for new, modified, vacant, and existing positions using authoritative financial, payroll, position, and workforce data. For the Budget-Informed Position Affordability capability area, respondents shall identify whether the proposed solution serves as a planning and analytical tool, workflow and approval layer, integration or data-exchange capability, or another complementary function to ICE’s existing financial, payroll, and human capital environment.

The goal is to acquire and implement a system that enables ICE to efficiently advertise, recruit, assess, and track applicants while strictly adhering to federal hiring requirements. Additionally, the solution must feature an external applicant portal that utilizes Human-Centered Design (HCD) to provide candidates with a single, 360-degree view of their hiring process prior to onboarding.

ICE is seeking information on solutions that address one or more of the following capability areas. A respondent may propose a single integrated platform or a combination of products, partner offerings, or services. Respondents should identify which areas their offering covers and, for combined offerings, how the components integrate. Capabilities of interest include::

• Recruitment planning and recruitment campaign management.

• Vacancy, job announcement, and applicant tracking.

• Federal hiring workflow and assessment support.

• Applicant communications, engagement, and self-service.

• Pre-employment clearance (PEC) coordination and approved status visibility, meaning applicant task coordination and display of status received from authoritative ICE or provider systems for screening activities between tentative and final offer (e.g., drug testing, medical, background, fitness). The solution does not perform or adjudicate PECs.

• Secure document collection and management.

• Applicant appointment scheduling.

• Leadership dashboards, analytics, and reporting.

• Integration with Core HCM, identity, clearance, onboarding, training, and other enterprise systems.

• Payroll adjustments to budget execution monitoring, payroll projections, workforce costing, position affordability analysis, and scenario modeling.

In addition to the software capabilities above, respondents should describe associated services, including implementation, data migration and transition, Organizational Change Management (OCM), training, and post-deployment support (see Section 6). Respondents should identify which services are included in the subscription or license and which are separately priced.

Capability Classification Requirement For each capability addressed in this RFI, respondents shall identify whether the capability is:

1. Native and currently available in the proposed platform;

2. Available through standard configuration;

3. Available through a pre-built connector, plug-in, marketplace application, or partner solution;

4. Dependent upon a third-party product or service;

5. Dependent upon custom development;

6. Planned on the vendor’s product roadmap; or

7. Not available.

For any capability that is not native and currently available, respondents shall identify applicable assumptions, dependencies, estimated configuration or development effort, any additional licensing, subscription, or third-party products required, and expected availability date.

ICE Environment (High Level). For planning purposes, respondents should assume the solution would exchange data with the following categories of ICE and Federal systems: financial management and budget (Federal Financial Management System (FFMS), SAP, and OneNumber); payroll and personnel processing (National Finance Center); Federal recruitment (USA Staffing and USAJOBS); a future Federal Core HCM platform; DHS applicant-processing and personnel-security systems (Enterprise Integration Environment (EIE), Information Security Management System (ISMS)); ICE personnel processing system (Electronic System of Personnel (ESP)), enterprise API management (MuleSoft); and enterprise analytics (Databricks). This list is provided for market research only. System-specific technical details will be provided in a later acquisition phase.

HIGH-LEVEL CAPABILITY REQUIREMENTS

Respondents should address the functional areas below that apply to their offering.:

1. Recruitment and Applicant Tracking

• Federal Hiring & Recruitment Workflows: Support comprehensive federal recruitment planning, campaign management, and hiring workflows that align with OPM's Human Capital Business Reference Model (HCBRM). The solution must provide configurable workflows for different hiring pipelines, including both law enforcement and mission-support positions, supporting the end-to-end ICE hiring workflow from Hiring Plan Submission and Job Opportunity Announcement (JOA) publication to the issuance of Tentative Job Offers (TJO) and Final Job Offers (FJO).

• Vacancy & Position Tracking: Track vacancies, announcements, applicants, and selections throughout the hiring lifecycle. The system must track recruitment activity using ICE-specific position identifiers, including Position Descriptions (PDs), job or occupational series, grade, duty location, organization, hiring authority, and announcement number.

• Applicant Assessment & Processing: Support automated applicant assessments, screening, dispositioning, and ongoing applicant communications.

• Access & Auditability: Provide role-based access for HR specialists, recruiters, hiring managers, selecting officials, and other authorized users. The solution must maintain strict auditability of applicant-status changes, workflow activity, communications, and hiring decisions.

• System Integration: The solution is intended to support all ICE recruitment populations, including law enforcement, mission-support, Senior Executive Service (SES), and Office of the Principal Legal Advisor (OPLA) positions. Respondents should describe how the solution supports differing hiring authorities and workflows across these populations.

The solution shall securely exchange data with USAJOBS, the future Core HCM platform, and other Federal systems as needed to meet applicable Federal hiring requirements and to hand off new-hire data. Respondents should also describe how their solution can operate alongside existing recruitment systems during a phased transition.

2. External Applicant Portal & Human-Centered Design (HCD)

• Pipeline Visibility & Status: Provide applicants with a transparent, mobile-ready, and desktop-accessible view of their active applications, current status, required tasks, messages, and relevant points of contact. The hiring process must be presented in clear, plain language across the major phases: Phase 1 (Tentative Selection), Phase 2 (Pre-

Employment Clearances), Phase 3 (Final Selection), and Phase 4 (Onboarding & Training).

• Pre-Employment Requirement Status Visibility: Provide applicants with approved, plain-language visibility into applicable pre-employment requirements and assigned tasks, including, as applicable, drug testing, medical clearance activities, personnel security/background processing milestones, and Physical Fitness Testing (PFT). The solution should support configurable status messages and task instructions while limiting applicant-facing information to the minimum necessary content and avoiding disclosure of sensitive medical, personnel security, investigative, operational, or internal deliberative information.

• Self-Service & Document Upload: Enable applicants to complete assigned tasks, submit forms, and securely upload documents from desktop and mobile devices. The solution must use Optical Character Recognition (OCR) or similar document-validation capabilities. Respondents shall identify supported document types, expected accuracy, required human review, handling of unreadable or incomplete documents, and how the solution identifies potentially missing items or incomplete signatures. The solution should also allow applicants to complete forms online (e.g., OF-306) with data pre-fill where available, apply an electronic signature, and view, download, or print completed forms. Respondents should describe their electronic-signature approach, including any third-party e-signature integration, and how signed forms and audit trails are retained.

• Self-Service Scheduling: Enable self-service scheduling, rescheduling, or cancellation of applicable appointments, such as medical examinations, drug testing, fingerprinting, physical fitness tests, interviews, or other required activities. The solution should support both ICE-managed appointments (e.g., interviews, fitness testing) and appointments performed by external service providers (e.g., medical, drug-testing, and fingerprinting providers), using real-time availability from the relevant calendar or provider system where available. Respondents should describe how appointment availability, confirmations, changes, and completion status are exchanged with third-party provider systems, and how the solution handles providers that do not offer an integration.

• Accessibility & Controls: The applicant portal must fully support Section 508 accessibility standards and maintain appropriate controls over the information displayed to applicants.

3. Super Intelligence (SI) & Omnichannel Communication

• Applicant Support & Omnichannel Messaging: Support automated applicant communications through email, SMS/text messaging, and in-portal notifications. The system must provide applicant FAQs, knowledge-base content, guided self-service, and secure in-portal messaging (or another method for applicants to contact designated ICE HR personnel).

• SI Compliance & Inventory: If the proposed solution includes Super Intelligence (SI), machine learning, generative SI, automated decision support, document classification, predictive analytics, or chatbot capabilities, the SI must align with federal and DHS SI principles (e.g., EO 13960). Respondents shall provide an inventory of each SI-enabled feature and describe its purpose, intended users, inputs, outputs, data handling, human oversight, auditability, monitoring, testing, and ability to be disabled or configured by

ICE.

• SI Limitations & Guardrails: SI-enabled capabilities shall not independently make, or materially determine without meaningful human review, an applicant's eligibility, qualification, selection, suitability, personnel-security status, medical status, drug-testing status, physical-fitness status, or other determination affecting an individual's rights, opportunities, or safety. Proposed SI capabilities must support applicable federal and DHS requirements in effect during performance, including requirements related to privacy, security, transparency, human oversight, testing, monitoring, and records management.

4. Leadership Reporting & Business Intelligence (BI)

• Advanced Analytics & Reporting: The solution must provide robust Business Intelligence (BI) and reporting capabilities, including interactive dashboards, configurable visualizations, scheduled reporting, data exports, and role-based access to analytics.

Respondents shall describe available capabilities utilizing tools comparable to commonly used BI platforms (e.g., Databricks, Power BI, Tableau), enabling leadership to rapidly process data, conduct trend analysis, and perform drill-down and filtering functions.

Additionally, because ICE is standardizing on Databricks as its enterprise analytics and data lake platform, the proposed solution must support seamless data pipelines, delta sharing, or automated data extraction (e.g., scheduled batch feeds, Change Data Capture [CDC], or direct connectors) to continuously replicate raw and processed recruitment, clearance, and workforce data into ICE's Databricks environment for agency-wide reporting.

• Forecasting & Predictive Analytics Guardrails: If the solution includes forecasting or predictive analytics, respondents shall describe the intended use case, data inputs, analytical method at an appropriate level, user controls, limitations, validation approach, and human-review process. Any predictive capability must not be used to make or materially influence individual applicant determinations without separate ICE authorization and applicable governance.

• Executive Dashboards: Natively generate real-time pipeline analytics for various mission areas and law enforcement officers, including tracking metrics such as Temporary Job Offers (TJOs) issued, Pre-Employment Clearance pipeline statuses (passed, pending, failed), Final Job Offer (FJO) issuance, and Entry on Duty (EOD) / Federal Law Enforcement Training Center (FLETC) scheduling statuses.

5. Integrations, Architecture & Security

• HCM & Legacy Plugins: Describe the solution’s integration architecture, including support for application programming interfaces (APIs) such as internal DHS systems (e.g.

Enterprise Integration Environment (EIE), Information Security Management System (ISMS)), event-based integrations, webhooks, secure file transfer, batch interfaces, identity federation, data transformation, interface monitoring, error handling, retry processing, and reconciliation. Because ICE is implementing MuleSoft as its enterprise API management and integration gateway, the proposed solution must provide modern, standards-based Representational State Transfer (REST)/JavaScript Object Notation (JSON)APIs (documented via OpenAPI/Swagger specifications) and webhooks capable of direct ingestion, governance, and orchestration through MuleSoft. Respondents shall identify available integration capabilities with major enterprise HCM platforms (such as Oracle, Workday, etc.), USA Staffing or similar federal recruitment systems, identity and access-management services, external clearance, scheduling, onboarding, and training systems, and ICE enterprise systems, as applicable. ICE will provide controlled system-specific technical interface information, as appropriate, in a future acquisition phase. For each proposed integration, respondents shall identify the data objects exchanged, direction and frequency of exchange, integration method, system-of-record assumptions, security and authentication approach, error-handling process, and whether the capability is native, configurable, third-party dependent, custom, or on the roadmap.

• DHS Security Compliance: The proposed solution must be capable of supporting applicable ICE and DHS security, privacy, accessibility, records-management, and interconnection requirements. Respondents shall identify the solution’s current FedRAMP authorization status, authorizing body, impact level, authorization boundary, and the specific product or service offering covered by that authorization. Respondents shall also describe their ability to support ICE and DHS security authorization activities, continuous monitoring, Interconnection Security Agreements (ISAs), encryption in transit and at rest, role-based access controls, audit logging, privileged-access controls, incident response, business continuity, disaster recovery, data retention, legal hold, data export, data deletion, and privacy compliance support. Respondents shall identify hosting locations, data residency, subcontractor and support-access locations, and any non-U.S. data processing or support arrangements.

• Supply Chain Risk Management: Respondents shall describe their Cyber-Supply Chain Risk Management (C-SCRM) practices, including third-party dependency governance, subcontractor oversight, vulnerability monitoring, vulnerability disclosure, remediation practices, software-integrity controls, and customer notification processes. Respondents shall state whether they can provide a current Software Bill of Materials (SBOM) for the proposed platform in a machine-readable industry-standard format. The response should identify SBOM coverage, update frequency, treatment of third-party components, and the process for notifying ICE of significant vulnerabilities affecting the proposed solution.

6. Organizational Change Management (OCM)

• Implementation, Discovery, and Transition: The vendor shall provide a phased implementation and transition approach appropriate for a high-volume federal hiring environment. The approach should address discovery, requirements validation, solution configuration, integration development, testing, data conversion, migration or preservation of active hiring actions, pilot deployment, phased rollout, training, applicant support, and post-deployment optimization. Respondents shall describe their approach to active hiring actions, including the migration or preservation of applicant profiles, uploaded documents, workflow status, task completion status, appointments, communications, audit history, and reporting data. Respondents shall identify data-quality dependencies, validation and reconciliation methods, rollback procedures, and any need for legacy-system read-only access. Respondents should describe how the proposed solution scales to support variable and surge hiring volumes, and identify the largest hiring volumes (e.g., applications received and candidates in active processing) it has supported for a Federal or comparable customer.

• Usability & Adoption: The approach must incorporate Human-Centered Design (HCD) and active usability testing with external applicants and internal ICE users, including HR specialists, recruiters, hiring managers, selecting officials, and administrators.

Respondents should describe proposed testing methods, accessibility testing, participant recruitment approach, usability measures, defect and enhancement prioritization, testing artifacts, and remediation process. Respondents shall describe how they measure adoption, task-completion rates, applicant satisfaction, internal-user satisfaction, training effectiveness, data quality, and continuous user feedback.

• Training & Deployment Support: The vendor must employ strategic communication and training methods to ensure solutions are readily adopted. This includes training HR personnel, recruiters, hiring managers, and administrators, as well as creating comprehensive user guides, job aids, knowledge articles, and in-application guidance.

• Post-Deployment & Applicant Support: Respondents shall describe their approach to supporting both applicants and ICE users (including HR specialists, recruiters, hiring managers, selecting officials, and administrators) during transition and after deployment. This should include help desk tiers and hours of support, escalation, knowledge articles, and continuous improvement. Respondents should also describe how they would handle hiring actions and applicants in process at cutover, such as migration, completion in the legacy system, parallel operation, or a hybrid, and how applicants would be informed and supported.

• Data Portability and Exit Planning: Respondents shall describe how ICE can export or transition structured data, documents, communications, audit logs, workflow history, reporting data, and configuration information in usable formats upon contract transition or completion. Respondents shall identify transition-assistance services, secure data return or deletion processes, and any proprietary data formats or constraints.

7. Budget-Informed Position Affordability and Workforce Cost Modeling

• Integrated Position Affordability & Planning: The solution shall provide a centralized, secure decision-support capability to evaluate the affordability of proposed, modified, vacant, and existing positions. The solution must complement, and not replace, ICE's authoritative financial management system, payroll system, or position-management systems of record. Authoritative budget controls, annual allotments, and payroll actuals will be ingested from budget, financial and payroll systems to establish planning thresholds. Affordability calculations and scenario outputs are planning and decision-support tools; they shall not independently obligate, deobligate, or certify funds, establish positions, or approve personnel actions.

• Volume Hiring and Position Costing Calculations: The solution must calculate the estimated full cost of positions and evaluate whether proposed staffing actions are affordable within established financial targets. The system should enable program offices and leadership to model specific hiring requests such as adding a cohort of positions

(e.g., 20 new hires) and calculate the time-phased financial impact. Costing must account for full personnel cost drivers, including series, grade, step, career-ladder progression, within-grade increases (WGIs), locality pay, benefits, historical overtime trends, awards, and planned onboard/EOD dates. The solution should also evaluate actions such as delaying vacancy fills, restructuring positions, and converting contract support to federal staffing.

• Scenario & What-If Modeling: The solution should allow authorized users to create, evaluate, save, and compare multiple hiring scenarios without altering approved baseline plans or financial records. Users should be able to evaluate:

o Changes to target hire dates, phased onboarding schedules, or vacancy lapse rates;

o Alternative grade, step, full-time equivalent (FTE), duty location, and organizational allocations;

o Attrition and backfill assumptions by program or mission area; and o The financial impact of revised funding ceilings or budget constraints.

The solution must compare scenario results against baseline funding, clearly identifying variances and quantifying the net affordability impact.

• Financial & Workforce Data Ingestion: The solution shall securely ingest necessary baseline data from authoritative ICE systems, including position attributes, historical payroll expenditures, current-year budget ceilings/allotments, and attrition trends.

Responses shall describe supported integration methods (including APIs, batch/file interfaces, and scheduled loads) and compatibility with enterprise integration platforms (such as MuleSoft) and enterprise data lakes (such as Databricks).

• Calculation Transparency & Model Explainability: The solution shall provide transparent, reproducible calculation formulas so that program offices and finance stakeholders can review the underlying assumptions, cost drivers, effective dates, and logic supporting an affordability determination.

• Configurable Affordability Rules & Approvals: Authorized users should be able to configure affordability thresholds, business rules, and approval criteria without custom software development. The solution shall support configurable workflows and alerts when a proposed hiring plan or scenario breaches approved funding limits or creates projected out-year deficits.

• Dashboards & Stakeholder Reporting: The solution shall provide intuitive dashboards and reports for program managers, HR, and finance leaders displaying aggregate and position-level affordability status, projected payroll trajectories against budget targets, and scenario comparison summaries, with export capabilities to Excel, CSV, and PDF.

• Security, Privacy, and Access Controls: The solution shall support granular role-based access control (RBAC) to ensure program offices only view and model positions within their organizational purview, while safeguarding sensitive compensation and workforce data in compliance with DHS security and privacy requirements.

SUBMISSION INSTRUCTIONS

Sources capable of satisfying one or more of the capability areas described above are invited to submit information describing their ability to meet the requirements. Respondents may propose a single solution or a combination of products and services and should identify which areas their response covers.

RFI/Sources Sought Responses shall be provided by November 23, 2026, at 9:30 AM Eastern Time (ET).

• Responses shall be submitted in Microsoft Word or PDF in size 12 Times New Roman/Arial font with single spacing and 1” margins.

• Please limit RFI submission responses to 21 pages (including cover page and excluding the two pages of administrative information). Questions and requests for additional information must be sent to DHS/ICE via e-mail to: ITD Contracting Officer, at itd-sd-procurements-10@ice.dhs.gov, by November 13, 2026, at 9:00 AM ET. Phone calls and verbal questions will NOT be accepted or responded to.

• Questions shall NOT contain proprietary or classified information. The Government does not guarantee that questions will be answered or can say questions received after the due date deadline will be answered.

• ICE reserves the right to review late RFI submissions but makes no guarantee to the order of, or possibility for, this review.

• All company proprietary information, performance capabilities and/or future modifications must be clearly identified and marked so segregation of proprietary information is required.

Interested parties are requested to respond to this RFI with the following two attachments:

1-Administrative Information Table (2-page limit) 2-Responses to Questions (21-page limit)

QUESTIONS FOR VENDORS

1. Please provide an itemized list of products (modules, etc.) available within your catalog that offer end-to-end recruitment lifecycle management and external applicant portal capabilities. Please note if the products are Section 508 compliant and FedRAMP authorized.

2. Describe your solution's capability to manage federal hiring requirements (e.g., OPM's HCBRM) and track vacancies using federal position IDs, PDs, and job series.

3. How does your solution utilize Human-Centered Design (HCD) to ensure a seamless, mobile-ready experience for external applicants navigating complex, multi-phase law enforcement hiring processes?

4. If your solution employs Super Intelligence (SI) or chatbots for applicant FAQs and support, how do you ensure the SI model is transparent, accurate, secure, and compliant with federal SI mandates (e.g., EO 13960)?

5. Describe your system's Business Intelligence (BI) and analytics capabilities. Can your solution natively generate pipeline dashboards tracking Tentative Job Offers, specific Pre- Employment Clearance statuses (e.g., Drug, Medical, Background, Fitness), Final Job Offers, and Entry on Duty metrics? Describe how your solution can feed or integrate with an external enterprise analytics and data lake platform, specifically Databricks, to support ICE-wide cross-functional reporting.

6. Describe your platform's ability to facilitate self-service scheduling and omnichannel communication (SMS, email, in-portal messaging) for applicants. Does it support mobile document uploads utilizing OCR capabilities?

7. Describe your platform's architectural approach to integrations (e.g., pre-built connectors, APIs, event-based integrations). Specifically, describe how you support integrations with major Core HCM systems (e.g., Oracle, Workday), USA Staffing, DHS internal systems (e.g., EIE, ISMS), and external clearance providers. Describe your platform's capability to publish OpenAPI-compliant endpoints, manage event webhooks, and integrate with enterprise API gateways, specifically MuleSoft, for centralized interface governance and lifecycle management.

8. Describe your solution's overarching security and compliance posture. Please detail your current FedRAMP authorization status, Section 508 conformance, identity-management capabilities, and ability to support DHS-specific requirements (e.g., ISAs). Please specifically address role-based access, encryption, and data segregation for sensitive payroll, compensation, medical, and personnel data.

9. Explain your Cyber-Supply Chain Risk Management (C-SCRM) practices. Do you provide a Software Bill of Materials (SBOM), and how do you handle third-party dependencies and vulnerability management?

10. What is your approach to Implementation and Organizational Change Management (OCM) when transitioning a federal agency from legacy systems to your proposed solution? Specifically describe your approach to discovery, usability testing, migrating active hiring actions, training varied user groups, and post-deployment continuous improvement.

11. Have you ever implemented a similar Recruitment and Applicant Portal solution for a federal law enforcement agency? If yes, please explain your approach, scale, and implementation process.

12. Identify the products, modules, and services in your catalog that support payroll adjustments to budget execution monitoring, payroll projection, workforce costing, scenario modeling, and position affordability analysis. Identify whether each capability is available out of the box, configurable, requires customization, or is not currently supported.

13. Describe how your solution integrates with the ICE systems identified in the ICE Environment paragraph, including the financial management and budget systems, payroll and position data sources, and Core HCM. For each, describe supported integration methods, data formats, refresh frequencies, error handling, and reconciliation. Identify any pre-built connectors, and state whether each integration is native, configurable, third-party dependent, or custom.

14. Describe how your solution supports full-year and multi-year payroll projections, including actual payroll expenditures, current-pay-period costs, overtime, awards, lump-sum payments, benefits, hiring, attrition, career ladder progression, within-grade increases, and other configurable cost assumptions.

15. Describe how your solution calculates and evaluates position affordability. Include the ability to assess new, modified, vacant, and existing positions against available funding, approved budget controls, allotments, and financial targets.

16. Describe your scenario-modeling capabilities. Can users model and compare the financial impact of changes to hiring dates, vacancy duration, grade, step, FTE, locality, organization, funding source, overtime, awards, benefits, or hiring and attrition assumptions?

17. Explain how your solution supports configurable assumptions, mapping tables, business rules, and exception handling. Specifically address object-code, task-code, program-code, funding-code, and transaction-type mappings; exclusions; program-specific adjustments; and one-time manual overrides.

18. Describe your data-quality, reconciliation, and exception-management capabilities. How does the solution identify missing, invalid, duplicate, late, or inconsistent source data?

How are exceptions assigned, tracked, resolved, and retained for audit purposes?

19. Describe the standard reports, dashboards, and analytical views available for budget execution, payroll forecasting, workforce costing, and position affordability. Address payroll and position actuals versus budget, forecast versus control, position affordability status, variance analysis, and drill-down capabilities.

20. Describe your solution's workflow, approval, notification, and audit-trail capabilities for affordability determinations, scenario approvals, assumption changes, manual adjustments, and budget-control exceptions.

21. Describe comparable implementations for federal agencies or other large organizations involving payroll adjustments to budget execution, payroll projection, workforce costing, or position affordability. Include your approach to model baseline validation, parallel testing against existing reports, scale, and measurable outcomes.

22. Rough Order of Magnitude (ROM) Estimate:

Provide a non-binding, preliminary Rough Order of Magnitude (ROM) estimate for your proposed solution. Please provide estimated costs for a base requirement and up to four optional capability areas or phases, as applicable. At a high level, distinguish one-time implementation costs from recurring annual costs and identify the major cost categories, such as software or subscription fees, implementation and integration services, data migration, cloud or hosting services, training, operations and maintenance, and any significant third-party products or services. Please identify the primary assumptions, anticipated period of performance, major cost drivers, and any material dependencies or exclusions underlying the estimate. Cost ranges are acceptable. This information is requested solely for market research and acquisition planning and is not binding, a formal solicitation, or an evaluation factor for a competitive award.