FEMA RFI 70FA4026I00000004 Questions and Answers v2.pdf

FEMA RFI# 70FA4026I00000004 Questions and Answers

1. Section 2.2 - Identity Resolution and Matching How does FEMA envision acceptable identity resolution approaches when survivor identifiers are incomplete, inconsistent, or evolving throughout the disaster lifecycle?

FEMA will work collaboratively with the selected vendor or vendors to identify confidence levels. In the case of incomplete, inconsistent, or evolving identity resolutions, FEMA will route those cases for manual review.

2. Section 2.2b - Matching metrics

Does FEMA anticipate establishing minimum confidence thresholds for insurance match results before they can be used in eligibility or duplication-of-benefits determinations?

FEMA collects elements of Sensitive Personally Identifiable Information (SPII) and Personally Identifiable Information (PII) that is expected to support data matching with high confidence. FEMA will work collaboratively with the selected vendor or vendors to determine appropriate confidence thresholds.

3. Section 2.4 and 3.6 - DOB and underinsurance use cases

Which eligibility or duplication-of-benefits determinations does FEMA expect to automate versus retain as caseworker decisions?

This will depend on the information that FEMA receives from the selected vendor or vendors (e.g., covered perils, limits, deductibles, exclusions, etc.) and how that information relates to the assistance type and limits available under FEMA’s program. Broadly, and subject to the results of this RFI, FEMA expects processing will fall into one of three categories:

(1) Completely Automated

(2) Automated with Human-in-the-Loop Review

(3) Manual (where a human reviews the information coming in from the insurance system) As FEMA becomes increasingly comfortable with the information provided by the vendor or vendors, the approach is likely to shift.

4. Section 2.7 and 3.4 - Data freshness and refresh

What latency expectations exist for insurance data refresh relative to IA eligibility timelines?

FEMA looks to insurance coverage that is in force and effect at the time of loss.

In most cases (e.g., home damage) that loss would occur within the incident period. Generally speaking, FEMA would want to validate the presence or absence of insurance at the time of registration as this is one driver of how the agency processes the case. FEMA will be happy to discuss the need for revalidation.

5. Section 4.2 - Integration with IA Processing System

Does FEMA intend Salesforce to act as the system of record for insurance artifacts or as an orchestration layer referencing external systems?

Salesforce is expected to be the System of Record for Individual Assistance.

6. Section 2.5 - Technical interfaces

Should coverage verification occur synchronously during survivor registration, asynchronously afterward, or both?

FEMA’s preference is for verification to occur during survivor registration as

(a) if an error is detected the survivor can be presented an opportunity to cure that error and (b) insurance coverage drives downstream business rules that govern how a case is handled.

7. Section 4.2 and 3.6

Where does FEMA anticipate duplication-of-benefits logic residing - Salesforce flows/rules engines or external services?

Duplication-of-benefits logic is anticipated to rely within Salesforce rules engines, not the external services contemplated under this RFI.

8. Section 10.5 - Alternative architectures

Does FEMA have a preferred architecture between carrier-direct integrations, aggregator-based access, or hybrid approaches?

FEMA is open to exploring both methods. However, in recognition that the insurance landscape changes often and to limit technical debt, FEMA generally prefers aggregator-based access.

9. Section 3.6 - Underinsurance determinations

Will FEMA publish standardized methodologies for calculating underinsurance across policy types?

Please see:

https://www.fema.gov/sites/default/files/documents/fema_insurance_qrg_202410 10.pdf

10. Section 8.3 - Pilot rollout

Does FEMA anticipate piloting with limited carriers, disaster types, or IA categories?

FEMA will determine its approach following review of the submitted responses to this RFI.

11. Section 2 - Acquisition strategy

Does FEMA anticipate a single award or modular procurements for verification vs linking?

FEMA is interested in both capabilities. FEMA will determine its approach following review of the submitted responses to this RFI.

12. RFI Response Submittal Instructions We respectfully request FEMA extend the due date for this RFI response one week to March 11.

The RFI due date has been extended to March 11, 2026 at 3:00pm EST.

13. In your document you refer to Survivors, and Survivor- permissioned. Is this the same as what insurance would refer to as the claimant?

Yes, for the purposes of this RFI.

14. Will you consider granting an extension for RFI deadline?

The RFI due date has been extended to March 11, 2026 at 3:00pm EST.

15. Is this RFI specifically looking for a data as a service provider? Or for both data as a service provider and for data application and integration services?

This RFI is seeking insurance validation and consumer-permissioned data sharing services. We anticipate the selected vendor or vendors will need to work collaboratively with FEMA staff and system integrator vendors to complete the necessary integrations.

https://www.fema.gov/sites/default/files/documents/fema_insurance_qrg_20241010.pdf https://www.fema.gov/sites/default/files/documents/fema_insurance_qrg_20241010.pdf

16. Do you envision a system where FEMA will access insurance data provider APIs to pull information, or will data providers be pushing data to FEMA?

FEMA is eager to learn the industry-recommended approach. However, as the “initiating event” to seek insurance data will be a Survivor registering with FEMA, our initial presumption would be using APIs to pull information. This RFI is designed to obtain information and recommendations about viable approaches, not to set a specific requirement.

17. Are there specific data platforms and/or applications currently in use at FEMA that will need access to the insurance information?

FEMA is in the process of building out a Salesforce platform as the System of Record for Individual Assistance.

18. During a catastrophic event (like a Category 5 hurricane), what is the anticipated intake volume of structured and unstructured data?

The volume of survivor registration is driven by the population affected and in a declared area as opposed to a particular category of storm. The RFI provides historic information on peak transactions.

19. If you have an estimate, approximately how many different data providers will be providing insurance coverage information?

FEMA is using this RFI to understand the market landscape.