Questions and Answers 70FA3021I00000009 FINAL for Posting.xlsx
XLSX spreadsheet 36 KB Posted
- Attached to
- FEMA Crisis Management System - Amend 2 Q&A
- Solicitation number
- 70FA3021I00000009
View the file
Other files
| File | Type | Posted |
|---|---|---|
| A1 RFI FEMA CMS 07-15-2021 - FINAL.pdf | ||
| RFI FEMA CMS 07-15-2021 - FINAL.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Questions & Answers
| 70FA3021I00000009 Questions & Answers | ||||
| Question # | Document | TOR/PWS Section Reference | Question | FEMA Responses |
| 1 | RFI | Section 3 & 4.1 | Question #12 of Section 3 of the RFI asks whether the offeror wishes to provide a market research product demo either virtually or in-person. Later in the RFI, Section 4.1 directs offerors to “Please also provide a demo of your product to accompany your RFI.” |
| The Section 3 question seems to indicate that FEMA intends to schedule a live demo of Offeror’s software at a later date, but Section 4.1 appears to expect a pre-recorded demo be submitted with the RFI response. Are both true? If so, is there a specific format (video file, URL to an online video) FEMA prefers for submission? | Both are true. FEMA intends to schedule live demos of the Offeror's software after reviewing RFI responses. For the pre-recorded demo a URL video link format is preferable. | ||||
| 2 | RFI | Question 3.6.e | Question 3.6.e states, "Please provide detailed examples of functionality in your solution, which mirrors current FEMA WebEOC Capabilities." We will need to have details of all WebEOC Capabilities to provide detailed examples of functionality that mirrors those capabilities. Could you please provide more details on the capabilities of the WEBEOC CMS? | The following critical pieces of existing functionality would need to be replicated in order to ensure a bare minimum operational viability of a new solution. |
1) Ability for the client to easily create customizable fillable forms and displays, which can go from concept to production deployable within minutes. Shifting disaster operations, and leadership data needs, require maximum flexibility in the collection and socialization of information.
2) Ability to design customizable notifications based on user interactions with the system. Due to timeliness of shifting response needs, this would also require rapid build and deployability.
3) Integrations with ArcGIS
4) A publicly available API, to allow partners to request and update data securely from their own solutions. This capability should allow for the quick customization and siloing of different endpoints for the various stakeholder needs.
5) Ability to quickly create and deploy public-facing forms, which feed data into the system, without requiring the individual inputting the data to have an existing account in the system.
6) Ability to quickly aggregate data from various database objects into singular display views
7) Ability to quickly create displayable maps of geo-relevant data from inputs in the system. This can be a part of the solution for the ArcGIS integration, or a separate solution.
8) Ability to quickly delegate partial administrative actions to users in the system.
9) Ability to quickly partition access to various reports, dashboards, and other products in the system, to users based on role assignments
10) Ability to log into the system using a smart card
11) Ability for SSO capabilities
12) Integration of MFA capabilities
| 3 | RFI | Question 3.6 f | Question 3.6 f states, "Please provide detailed examples of functionality in your solution, which is not currently available in FEMA's WebEOC. For us to provide detailed examples of what is in our system that is not in the WEBeoc system we need to know what is currently available in FEMA's WebEOC. Could you please provide more details on all that is currently available in FEMA's WebEOC? | See answer above in Row 4 |
| 4 | RFI | Question 3.6 g | Question 3.6 g. asks for detailed examples of capabilities which would not be immediately comparable to current FEMA WebEOC Functionality. To answer this question accurately we will need to know what is currently available in the current FEMA WebEOC. | See answer above in Row 4 |
| 5 | RFI | Question 3.6 h | Question 3.6 h. Please provide the details of FEMAs WebEOC for us to determine if there are any technological gaps between the current system and ours. | See answer above in Row 4 |
| 6 | RFI | Question 3.6 i | Questions 3.6.i Our company provides quite a long list of services. Are there specific services of interest and/or required? | See answer above in Row 4 for an idea of the basic services we are currently being provided but the intention is to determine what services are available in the market that may be of interest. |
| 7 | RFI | N/A | We would like to request an extension to allow for time to work on the response once we receive the answers to the questions submitted yesterday. Could you please extend the deadline one week? | Regretfully, due to the timeline of the requirement, we are unable to extend the deadline. |
| 8 | RFI | Section 1.2 | In Section I.2, FAR CLAUSES INCORPORATED BY FULL TEXT, FAR 52.219-30 is checked as applicable |
_X__ (24) 52.219-30, Notice of Set-Aside for, or Sole Source Award to, Women-Owned Small Business Concerns Eligible Under the Women-Owned Small Business Program (Dec 2015) (15 U.S.C. 637(m)).
| Is it your intent to put this solicitation out as WOSB set-aside or has a final competition type not been determined? | This RFI is for the purpose of Market Research | ||||
| 9 | RFI | Can the Government confirm if the ten (10) page maximum limit to the RFI response is inclusive of the title and cover letter pages? | Title and cover letter pages are not included in the ten (10) page maximum. | ||
| 10 | RFI | We would like to respectfully request a 7 day extension to the due date of this RFI. We understand that the response has a 10 page maximum, however, the questions are information-dense and will take time to answer fully. We would appreciate any additional time extension that FEMA could provide and believe that it will ultimately allow vendors to deliver more complete information to FEMA for its market research purposes. | Regretfully, due to the timeline of the requirement, we are unable to extend the deadline. | ||
| 11 | RFI | Section 4.1 | Section 4.1 specifies a response deadline of July 25, 2021 (Sunday) while section 4.3 requests a response by July 27 (Tuesday). Please clarify. | Amendment 1 of the RFI clarified the response deadline is July 27, 2021 by 3:00 PM EDT. | |
| 12 | RFI | Please describe the specific issues behind the situation that makes the current WebEOC system obsolete or in need of improvement? | The current WebEOC platform is not obsolete but FEMA is looking to see what other functionality is available in the market that may provide added benefit above and beyond what is currently being offered by the WebEOC platform. | ||
| 13 | RFI | Qustion 11c | Question 11c asks about "lift and shift” services. This term typically refers to migrating a current application (e.g., WebEOC) to a new hosting environment. Is this your intent or do you preferably desire a new, enhanced system? | FEMA is looking at all available options to determine the best possible solution to meet our needs. | |
| 14 | RFI | Does FEMA envision temporarily retaining WebEOC until data migration to a new system is complete? | If FEMA determines it is in it's best interest to transition to a new platform we envision retaining WebEOC for a period of time to complete the transition. | ||
| 15 | RFI | Question 6j | Re question 6j - Are you an authorized WebEOC reseller?: If FEMA opts to issue a solicitation, is it your intent to (a) transfer the operation of the current CMS to a new vendor or (b) procure another, improved, system? | FEMA is looking at all available options to determine the best possible solution to meet our needs. | |
| 16 | RFI | How much time does FEMA envision for the configuration of a new WebEOC? | FEMA is looking for guidance from potential vendors on what they believe is a feasible timeline based on their expertise and experience. | ||
| 17 | RFI | Will FEMA consider making this solicitation a SDVOSB set aside? | This RFI is for the purpose of Market Research. FEMA has reviewing all submission. Small Business | ||
| 18 | RFI | The RFI does not identify the extent to which FEMA CMS and FEMA’s WebEOC are one and the same. Please identify any FEMA CMS functions that are executed principally by third party or DHS software or customized components other than WebEOC. | The FEMA CMS and WebEOC are one and the same, all third party integrations are through the WebEOC platform and not outside of it. | ||
| 19 | RFI | The RFI states: “The FEMA CMS currently supports Response and Recovery disaster-based operations ... for the following: [list of activities]” The RFI contains little to no information as to the role WebEOC plays in supporting the listed activities. Please describe the functions performed by WebEOC for the different listed activities. As an example, what functions does WebEOC perform to support Lifelines (see the RFI bullet situational awareness)? | WebEOC currently performs all CMS functions to support the listed activities. The details of what functions WebEOC performs to support the listed activities are not pertinent to the questions being asked in RFI and therefore the information requested is not applicable to the market research that is being conducted. | ||
| 20 | RFI | Question 6b | In 6b, the RFI states: “Do you have experience and the capability to seamlessly transfer millions of historical digital data records without loss of functionality?” Please identify the one or more repositories of the historical records and describe the requirements for on-going availability of the records. | General responses as to how you have or would faciltate the transfer of data between different systems, suffices. This would include how you would ensure similar or cloned database objects on the destination solution to ingest data from the existing solution without loss of integrity, while simultaneously providing uninterrupted access to the same datasets to allow users to continue inputting and updating those records. Knowledge of current environment isn't necessary as the question is framed more to gauge different options and understanding of the process. But FEMA's CMS is currently housed on environments in AWS East and replicated to AWS West. | |
| 21 | RFI | Please clarify whether all or portions of the submittal in response to the RFI may be marked and treated as “CONFIDENTIAL INFORMATION.” | FEMA requests Contractor to indicate which section of the submittal is "Confidential Information". FEMA will handle the information as "Confidential and Procurement Sensitive". | ||
| 22 | RFI | Question 6e | In 6e, the RFI states: “Please provide detailed examples of functionality in your solution, which mirrors current FEMA WebEOC Capabilities;” and in 6f it states:“Please provide detailed examples on capabilities which would not be immediately comparable to current FEMA WebEOC functionality, and provide examples on how you would overcome that loss of capability.” Please describe the functions that are performed by WebEOC and are either deemed “FEMA WebEOC Capabilities” or “FEMA’s WebEOC functionality” in sufficient detail so that examples can be provided. | The following critical pieces of existing functionality would need to be replicated in order to ensure a bare minimum operational viability of a new solution. |
1) Ability for the client to easily create customizable fillable forms and displays, which can go from concept to production deployable within minutes. Shifting disaster operations, and leadership data needs, require maximum flexibility in the collection and socialization of information.
2) Ability to design customizable notifications based on user interactions with the system. Due to timeliness of shifting response needs, this would also require rapid build and deployability.
3) Integrations with ArcGIS
4) A publicly available API, to allow partners to request and update data securely from their own solutions. This capability should allow for the quick customization and siloing of different endpoints for the various stakeholder needs.
5) Ability to quickly create and deploy public-facing forms, which feed data into the system, without requiring the individual inputting the data to have an existing account in the system.
6) Ability to quickly aggregate data from various database objects into singular display views
7) Ability to quickly create displayable maps of geo-relevant data from inputs in the system. This can be a part of the solution for the ArcGIS integration, or a separate solution.
8) Ability to quickly delegate partial administrative actions to users in the system.
9) Ability to quickly partition access to various reports, dashboards, and other products in the system, to users based on role assignments
10) Ability to log into the system using a smart card
11) Ability for SSO capabilities
12) Integration of MFA capabilities
| 23 | RFI | Question 8 | In 8, the RFI states: “Can this system be scaled for users outside of DHS across any government agency? Please explain how since each agency has its own special requirements regarding IT security.” Please describe how the FEMA CMS or FEMA’s WebEOC is “scaled for users outside of DHS across any government agency” and why another solution would be unable to use the same mechanism to meet this requirement. | Please disregard question 3.8 |
| 24 | RFI | Question 9 | In 9, the RFI states: “Please provide details on how you have, or would, support existing system interconnections.” Please describe the existing “system interconnections.” | Existing system interconnections include the following, and any new solution would have to provide a mechanism to ensure the CMS is able to retrive information from and provide information to these other disparate systems. But a general response as to how your company/solution either currently is facilitating, has facilitated in the past, or would facilitate data exchange with other systems in the future, also suffices as a response to the question. |
1) Interconnection with FEMA's Logistics and Supply Chain Management Systems (LSCMS) to transmit movement and tracking of Resource Requests as they get processed and delivered to their final destination.
2) FEMA CBRNE and Argonne Labs partnership utilization of existing API to retrieve data from the CMS based on partitioned user access rights in the CMS.
3) Same process as in bullet 2, but for HHS and their Palantir devloped and managed solution.
25 RFI Section 4.1 In Section 4.1, the RFI states: “Please also provide a demo of your product to accompany your RFI.” Please confirm or clarify that requirement in light of the statement contained in Section 1 of the RFI as follows: “After reviewing responses to this RFI, FEMA may request respondees to provide a live demonstration of their capabilities and platform at FEMA HQ in Washington, D.C. for the purpose of market research.” Both are true. FEMA intends to schedule live demos of the Offeror's software after reviewing RFI responses. For the pre-recorded demo a URL video link format is preferable.
Interested Parties
| Interested Parties | ||||
| Company | Website | POC | Phone | |
| EDC Consutling | www.edcconsulting.com | Russell E Hall | russ.hall@edcconsulting.com | 301.755.7752 |
| BowHead | www.bowheadsupport.com | Jay Davis | Jay.Davis2@bowheadsupport.com | 850-516-9641 |
| 4cast | 4Cast | Morgan Brooke | Morgan.Brooke@4cast-solutions.com | (206) 550-0523 |
| Dynamis | Carolyn Henandez | chernandez@dynamis.com | 571.438.1270 | |
| Buffalo Computer Graphics (BCG) | www.disasterlan.com | Patrick J. Cerra | rfpteam@bcgeng.com | 716-998-3757 |
| Indiana University | Kyle Stirling | kylestir@indiana.edu | 650.283.5953 | |
| Priority 5 holdings, Inc | Ginny Friedman | ginny@priority5.com | 617.515.1588 |
mailto:russ.hall@edcconsulting.commailto:kylestir@indiana.edumailto:ginny@priority5.comhttps://urldefense.us/v3/__http:/www.edcconsulting.com/__;!!BClRuOV5cvtbuNI!TFMFwP7pXaxOuJmVLm_iXRvrvq5LiqIqHRMOWZsbBA1b0C5ezQ30GtQi868JKgDpQdnJ08qaMIw$https://urldefense.us/v3/__http:/www.bowheadsupport.com__;!!BClRuOV5cvtbuNI!Xh8xirmkXpdIeq8XyOYjxey_5_6gjA-LGRERzUK6mNNsUaprV8t0JXlsi5VvTs90iK0Jrf-Z_tY$mailto:Jay.Davis2@bowheadsupport.comhttps://urldefense.us/v3/__https:/4cast-solutions.com/__;!!BClRuOV5cvtbuNI!XFqbaK8E3bjB0hEMLEk5z83ZCubwb1FkQJwidRavX1Q91895hvIF5Y8o492oUoI45m9z4GCayIY$mailto:Morgan.Brooke@4cast-solutions.commailto:chernandez@dynamis.commailto:rfpteam@bcgeng.comhttps://urldefense.us/v3/__http:/www.disasterlan.com/__;!!BClRuOV5cvtbuNI!WSZEDue35xRUAMa_fw3gXSSQiQVY2ys1EAjKMY5V1NEkWMdzEsyY8CZtb2IWg6fDjQOgmhJtRDo$ Abbreviations Acronyms
| Abbreviations / Acronyms | |
| CLIN | Contract Line Item Number |
| FEMA | Federal Emergency Management Agency |
| FIMA | Federal Insurance & Mitigation Administration |
| FFP | Firm-Fixed-Price |
| LH | Labor-Hour |
| NSP | Not Separately Priced |
| NTE | Not-to-Exceed |
| ODC | Other Direct Cost |
| QTY | Quantity |
| T&M | Time-and-Materials |
| DEL: Deliverable | |
| IAW: In Accordance With | |
| NLT: No Later Than | |
| TOA: Task Order Award | |
| All references to days: Government Workdays | |
| DEFINITION OF TERM: TO will end based on the period of performance (term). See FAR 16.306(d)(2). Level of effort must be defined; see FAR 16.306(d)(4). Majority of FEDSIM TOs will be TERM |
File details come from the government source that posted it. Updated .