Attachment 4 TOS_DTS_2.0 RFI Consolidated Responses and Review_Finalized.pdf

Date: 10/9/2026

DTS 2.0 RFI: Consolidated Responses for High Frequency Topics

*Please note the survey answers will have more detail in cases where it was deemed necessary or if the question was unique.

Topic High Level - Standardized Response Users and scale For planning purposes, respondents should assume approximately 15,000 to 20,000 active users, approximately 15,000 daily users, approximately 32,000 responder records, and potentially all employees accessing the system during a major activation. Detailed population, transaction, and growth metrics will be refined during requirements development.

Integrations The replacement will need to interface with Government systems to support required functionality at MVP and full deployment. The specific integration inventory, data exchanges, standards, API specifications, volumes, and test access will be refined during requirements definition and solution design.

Data migration The final migration scope, including source systems, data types, volumes, historical periods, attachments, retention, data quality, and extract methods, will be defined during requirements definition and solution design. For planning purposes, respondents should assume more than 10 years of historical DTS data.

Hosting Respondents should assume deployment in a FEMA-provided, Government-owned FedRAMP High cloud environment for the operational solution. Vendor-managed FedRAMP High SaaS offerings may be described but would require FEMA approval.

Security and authorization

The solution must meet applicable FEMA and DHS cybersecurity, privacy, identity and access management, auditing, records-management, accessibility, and supply-chain risk-management requirements. Respondents should identify their current FedRAMP or ATO status and authorization approach.

COTS, custom, or hybrid

FEMA does not have a current preference among COTS, configurable COTS, custom, or hybrid approaches. Respondents should propose the approach that best meets the RFI requirements.

Native capability integration

Respondents should describe how their solution will meet the RFI requirements through native functionality, Government-system integration, or a hybrid approach. The final system boundary will be determined during requirements definition and solution design.

Transition and cutover

Legacy DTS is expected to remain operational during transition to support continuity of operations.

Respondents should describe their proposed phased rollout, data migration, parallel operations, cutover, rollback, and continuity approach.

Acquisition approach

FEMA has not determined the acquisition vehicle, contract type, award structure, or small-business or socioeconomic set-aside. These matters will be addressed through acquisition planning and any future solicitation.

Team arrangements and partial scope

FEMA welcomes market-research responses from providers that address all or part of the DTS 2.0 scope, including teaming arrangements. Respondents should identify roles, capabilities, partners, and material dependencies. For unsupported functional-task rows, select “No Capability Today:

Enhancement needed and possible” and explain in the comments field.

Section 2 estimates

Estimate effort directly tied to each subtask, including design, configuration or customization, and subtask-specific testing. Report shared work, such as platform setup, common integrations, migration, security/ATO, and enterprise testing, once in Section 4 to avoid double counting.

Pricing Provide separate ROM estimates for implementation, licenses or subscriptions, data migration, operations and maintenance, cybersecurity and ATO support, training, surge support, and any cloud-related costs not covered by FEMA. Clearly identify recurring versus non-recurring costs and pricing assumptions.

Testing and documentation

Available interface specifications, representative test data, non-production environments, and other information needed for the selected solution will be provided during requirements definition and implementation, as appropriate. Respondents should identify material assumptions affecting their estimates.

Support model FEMA anticipates internal staff will manage Tier 1 end-user support and help-desk tickets. The contractor should provide escalated Tier 2/3 application, integration, and engineering support, as needed.