Date: September 21, 2026 What is out there? How long to stand it up? What would it cost?

North Atlantic Industry Classification Code: Classification Code: 541511 - Custom Computer Programming Services

IMPORTANT: ONLY RESPOND DIRECTLY IN THE EXCEL SURVEY PROVIDED

Background and Guidance: Deployment Management Solution Request for Information (RFI)

Purpose: FEMA is conducting market research to identify commercial of the shelf (COTS), configurable commercial of the shelf

(CCOTS), custom, or hybrid solutions capable of replacing the legacy Deployment Tracking System (DTS) and materially improving Federal Emergency Management Agency’s (FEMA) incident workforce management capabilities. The replacement solution should support workforce readiness, personnel availability, qualifications, certifications, training, deployment tracking, incident and event staffing, force package management, equipment assignment, reporting, analytics, secure cloud hosting, and interoperability with existing FEMA and Department of Homeland Security (DHS) systems. FEMA is seeking information on solutions that improve readiness visibility, accelerate staffing, reduce manual work, strengthen data quality, support surge operations, improve reporting and analytics, and reduce long-term sustainment burden.

Desired Future State

FEMA seeks a modern, scalable solution that enables improved management of the incident workforce across the full deployment lifecycle. The desired future state includes:

• Improved visibility into workforce availability, qualifications, skills, training dependencies, and deployment status.

• Faster identification, selection, notification, assignment, deployment, and demobilization of qualified personnel.

• Reduced manual data entry, spreadsheet-based tracking, duplicative workflows, and offline coordination.

• Better integration and interoperability across other critical government systems

• Improved analytics, and reporting to support operational decisions, leadership reporting, and surge planning.

• Scalable support for major disasters, Stafford Act and non-Stafford Act incidents, exercises, and DHS events

• Improved user adoption, workflow continuity, cybersecurity, auditability, and long-term sustainment.

(High-level Overview) What FEMA needs…

1. Personnel Availability and Deployment Tracking

Track availability, deployment status, assignments, mobilization, demobilization, location, and readiness for individuals, teams, task groups, and force packages.

2. Qualification and Certification Management

Manage qualifications, certifications, credentials, skills, expirations, training dependencies, position requirements, and readiness status.

3. Training Management

Support registration, scheduling, transcripts, notifications, training history, learning assignments, and learning management system (LMS) integration.

4. Incident/Event Staffing and Force Package Management

Staff incidents, events, exercises, Stafford Act and non-Stafford Act mission sets, and surge operations based on availability, qualifications, location, readiness, equipment, and mission needs.

5. Equipment Assignment Tracking

Track equipment issuance, return, transfer, condition, accountability, and assignment to personnel, teams, incidents, events, or force packages, either natively or through integration.

6. Reporting, Analytics, and Readiness Metrics

Provide dashboards, automated and ad hoc reporting, visualizations, readiness metrics, staffing, deployment, training, qualification, gap analysis, and surge planning reports.

7. Cloud Architecture, Cybersecurity, and Authority to Operate (ATO) Readiness

Support secure government cloud hosting, FedRAMP/ATO readiness, Zero Trust principles, identity and access management, role-based access, audit logging, encryption, monitoring, continuity, and backup.

8. Integration and Data Interoperability

Exchange data with FEMA/DHS systems, legacy DTS, and relevant personnel, identity, training, qualification, deployment, incident, property, reporting, and enterprise data systems.

9. Legacy DTS Replacement and Transition

Support DTS data migration, workflow and report transition, user adoption, continuity, coexistence, phased rollout, cutover, and decommissioning.

Date: September 21, 2026 What is out there? How long to stand it up? What would it cost?

North Atlantic Industry Classification Code: Classification Code: 541511 - Custom Computer Programming Services

Information Domains… (in the excel file)

Below is a list of information domains that give a high-level overview of the associated sections of the accompanying Excel survey. Respondents should complete the Excel survey provided and address each question in detail. Please refer to the

“Background and Instructions” tab in the workbook for more details on answering each section:

1. Section 1: Solution Profile

a. Company identification and business classification: Company name, address, authorized RFI point of contact, business size, and applicable socioeconomic designations.

b. Solution role, partnerships, and capabilities: Major partners, market position, unique capabilities, and role as primary developer, reseller, integrator, or other solution provider.

2. Section 2: Functional Tasks

a. Workforce readiness and deployment management: Support all aspects of personnel deployment operations, support training, professional development, certifications, equipment assignment, personnel availability, and travel information.

b. Event, incident, and operational data management: Create and manage events and incidents, maintain associated data, and enable standard and ad hoc reporting to support operational awareness and decision-making.

c. System administration, compliance, and user support: Provide secure and accessible system administration capabilities, including user profile and privilege management, interoperability, performance, data management, compliance, and communication/notification functions.

3. Section 3: System Attributes

a. Integration, compatibility, and architecture: Describe how the solution connects with government, cloud-based, and on-premises systems; manages version updates; supports third-party integrations; and aligns with hosting, FedRAMP/ATO, Identity and access management, Zero Trust, security boundary, encryption, logging, monitoring, resilience, continuity, and disaster recovery requirements.

b. Vendor implementation and support capabilities: Explain the vendor’s experience integrating with existing systems, examples of similar integrations, and the structure of post-implementation support, including ongoing maintenance and issue resolution.

c. Scalability, performance, and usability: Address the solution’s ability to handle fluctuating user loads and utilization spikes without performance degradation, as well as the level of training required for users to become proficient in using the system.

d. Customization, feedback, and product improvement: Identify any limitations related to customization and third-party integrations, and describe how user feedback is collected, communicated to the development team, and incorporated into future software updates.

4. Cost, Schedule, Risk

a. Cost model, pricing structure, and cost drivers: Describe software pricing, licensing or subscription approach, per-user costs, scalability impacts, and key cost drivers such as hosting, configuration, customization, migration, migration, migration, integrations, reporting, cybersecurity, training, support, surge usage, and recurring operations and maintenance.

b. Implementation, migration, and lifecycle cost estimates: Provide rough order of magnitude (ROM) labor and non-labor costs for implementation, customization, training, testing, integration, data migration, and sustainment, with costs broken out by Operations & Maintenance, development, subscription, recurring, and non-recurring categories across 1-year, 5-year, and 10-year periods (if possible).

c. Schedule, transition approach, and deployment milestones: Outline pre-implementation activities, integration with government systems, legacy data migration, workflow/report transition, coexistence, phased rollout, cutover, decommissioning, and expected timelines for Minimum Viable Product (MVP) and full deployment, including assumptions, dependencies, government responsibilities, ATO activities, training, change management, and continuity.

d. Implementation risks, constraints, and opportunities: Identify risks and opportunities based on similar implementations, including migration, integrations, ATO, reporting, user adoption, customization, scalability, data quality, workflow change, surge usage, legacy coexistence, and long-term sustainment.

Government Notice

This RFI is issued solely for information and planning purposes. It is not a Request for Proposal, solicitation, or commitment to procure any product or service. The Government will not reimburse respondents for costs associated with preparing or submitting responses. Information received may be used to inform requirements development, acquisition planning, market research, and legacy DTS replacement strategy.