CORHQ-25-R-0450 Supplemental QA 121625.xlsx
XLSX spreadsheet 22 KB Posted
- Attached to
- Data Modernization Section Support Federal contract opportunity
- Solicitation number
- 21842
- Issued by
- Federal Deposit Insurance Corporation
About this file
This file is a Supplemental Questions and Answers (Q&A) document for the FDIC Data Modernization Support (DMS) solicitation. The document contains nine key clarifications for potential offerors, addressing technical, procedural, and submission requirements. Significant details include guidance on surge FTE pricing (offerors may create a separate tab in the pricing workbook), confirmation that innovative solutions require both narrative descriptions and Technical Acceptability Matrix submissions, and clarification on document submission requirements such as Letters of Commitment for Key Personnel and background investigation form submission.
The solicitation, issued by the Federal Deposit Insurance Corporation (FDIC), seeks a contractor to provide comprehensive data technology services, including analysis, development, deployment, and operations of emerging data technologies. The proposal due date has been extended multiple times, with the current deadline set for January 2, 2026 at 12:00 PM EST. The scope encompasses full lifecycle support for the CDMA Platform, modernization of the AlphaRex NLP solution, enterprise AI capability operations, and development of new DMS solution initiatives from experimentation through production.
View the file
Other files for this federal contract opportunity
Show all 18
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Questions DMS Support Solicitation Offeror Questions and FDIC Responses
| # | RFP Section | RFP Page # | Question | FDIC Response |
| 1 | Attachment 1 - DMS Support RFP Q and A Answered 111425.xls | In the excel file named "Attachment 1 - DMS Support RFP Q and A Answered 111425", the FDIC's response to question #155 indicates that offerors should provide justification for Surge FTE in the pricing narrative. The amended pricing workbook doesn't provide a way to delineate the Surge FTE line items for the proposal. Can an offeror submit a second pricing workbook that only accounts for the surge FTE pricing, separate the overall contract pricing based on the workstreams and hours in the SOO? That is, one pricing workbook will be the pricing without surge FTEs and the other will be the pricing with just surge FTEs. |
| This will provide the FDIC with clear insights into what surge pricing looks like and a great baseline for price comparison with other offerors. Justification will remain in the pricing narrative as requested. | Offerors may create a separate tab in the provided pricing workbook to delineate the Surge FTE line items. | |||||
| 2 | Technical Acceptability Matrix | TAM Question 1: Secure GenAI with RAG in a Regulated Environment | As this work involves innovative solutions not typically outlined in a PWS/SOW/SOO, can the government confirm that offerors may submit written descriptions demonstrating capabilities and aligning the work under a task or requirements of the original PWS/SOW/SOO as sufficient in meeting the requirement? | Offeror may submit written descriptions demonstrating capabilities, but will also need to submit the proof outline in the Technical Acceptability Matrix to be compliant. You can provide a narrative explaining it was not outlined in a PWS/SOW/SOO. | ||
| 3 | Technical Acceptability Matrix | Production NLP Capabilities and Experience | As this work involves innovative solutions not typically outlined in a PWS/SOW/SOO, can the government confirm that offerors may submit written descriptions demonstrating capabilities and aligning the work under a task or requirements of the original PWS/SOW/SOO as sufficient in meeting the requirement? | Offeror may submit written descriptions demonstrating capabilities, but will also need to submit the proof outline in the Technical Acceptability Matrix to be compliant. You can provide a narrative explaining it was not outlined in a PWS/SOW/SOO. | ||
| 4 | Section L | 43 | Can the FDIC confirm whether Letters of Commitment (LOC) are required for each Key Personnel or only for incumbent hires that will be proposed as Key Personnel? | Letter of Commitment are required for each Key Personnel. | ||
| 5 | Section L | 41 | FDIC question response numbers 51 & 300 stated that form 3700-46 should be included in Volume 5, while response number 28 states to include form 3700-46 in Volume 4, can the FDIC confirm which volume to include to include form 3700-46? | Form 3700-46 should be included in Volume 5. | ||
| 6 | Section L | 46-47 | The FDIC Q&A response is requiring Background Investigation forms to be included in with the proposal; is it acceptable to send the forms in a separate password protected email to the Contracting Officer to protect PII? | The forms may be sent in a separate password protected email. | ||
| 7 | Section 7.3, Paragraph F | 41 | FDIC Q&A #352 states that "Executive, Cover Page and Table of Contents included in page count", whereas the Amendment #1 of the RFP states that "the following will not be included in the page count limitations: cover pages, table of contents, tabs, dividers, glossaries, blank pages and a compliance matrix (if proposed)". Can the FDIC confirm that the cover pages, table of contents, tabs, dividers, glossaries, blank pages and a compliance matrix are not included in the page count? | Cover pages, table of contents, tabs, dividers, glossaries, blank pages and the compliance matrix will not be included in the page count. This was changed from these items being originally included due to concerns from multiple offerors. | ||
| 8 | Attachment 3 - Technical Acceptability Matrix | Can the FDIC confirm whether Column D is referring to the location in the offeror's DMS proposal or in the referenced redacted award document? | It is referencing the location in the offeror's proposal, which can also include the redacted award document. | |||
| 9 | Attachment 3 - Technical Acceptability Matrix | Requirement #1 in Attachment 3 (Technical Acceptability Matrix) specifies that the award date for the referenced contract must be on or after November 14, 2023. If our firm deployed a secure Generative AI solution using RAG or knowledge graphs, grounded in private data, for a federal, state, local government, or HIPAA/PCI-regulated client, under a contract awarded PRIOR TO November 14, 2023, but the relevant work continued beyond that date, would this engagement satisfy the requirement? | No. This would not satisfy the requirement. | |||
| 10 | ||||||
| 11 | ||||||
| 12 | ||||||
| 13 | ||||||
| 14 | ||||||
| 15 | ||||||
| 16 | ||||||
| 17 | ||||||
| 18 | ||||||
| 19 | ||||||
| 20 | ||||||
| 21 | ||||||
| 22 | ||||||
| 23 | ||||||
| 24 | ||||||
| 25 | ||||||
| 26 | ||||||
| 27 | ||||||
| 28 | ||||||
| 29 | ||||||
| 30 | ||||||
| 31 | ||||||
| 32 | ||||||
| 33 | ||||||
| 34 | ||||||
| 35 | ||||||
| 36 | ||||||
| 37 | ||||||
| 38 |
&"Source Sans Pro SemiBold"&12&K000000 NONPUBLIC//FDIC BUSINESS&1#_x000D_
File details come from the government source that posted it. Updated .