FDM_RFIv2.docx

DOCX document 62 KB Posted

Attached to
RFI: Foundation Dissemination Modernization (FDM)
Solicitation number
RFI-OCSA-FY24-FDM
Issued by

About this file

This document is a Request for Information (RFI) issued by the National Geospatial-Intelligence Agency (NGA) seeking information from interested contractors on improving and modernizing NGA's current Foundation GEOINT systems and services. The RFI covers data ingest and management, condition and cataloging, disclosure and release, dissemination services, and user interface requirements. NGA is interested in information on contractor incentives, approaches to demonstrating work completion, leveraging existing microservices, systems integration, and adapting to changing data types, volumes, and delivery methods. The period of performance is one 12-month base year with four 12-month option years, with an anticipated contract award date no later than FY25Q3. Responses are limited to 10 pages in a Microsoft Word format and are due by the date posted on SAM.gov. The RFI is for information and planning purposes only and does not constitute a formal solicitation.

View the file

Other files

File Type Posted
FDM_Draft_PWSv2.docx DOCX document

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

UNCLASSIFIED

REQUEST FOR INFORMATION (RFI)

Foundation Dissemination Modernization (FDM)

1. Purpose & description

1.1. The purpose of this Request for Information (RFI) is to determine those who can satisfy the requirements for a potential RFP. This is an update to the 2022 RFI for Source Content Dissemination Services (SCDS).

1.2. The National Geospatial-Intelligence Agency (NGA) is seeking information on how an interested contractor would improve/modernize NGA’s current Foundation GEOINT systems and services providing data ingest and management, condition and catalog, disclosure and release, dissemination, and user interface (reference Section 4 in PWS).

1.2.1. Conduct modernization, patching, adaptive/corrective maintenance, maintain STIGS, conduct tech refreshes and patches.

1.2.2. Expand functionality of the system to potentially include replacing and realigning workflows for optimization and automation of large bulk orders of Foundation content. May also require expansion of functionality to ingest, condition and provide for discoverability and dissemination for NGA product lines.

1.2.3. Provide Operations and Maintenance (O&M) support to the system and network that has the ability to ingest Foundation GEOINT products and data, tag metadata, catalog, and disseminate those products.

1.3. THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. This RFI is issued solely for information and planning purposes – it does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. This RFI does not commit the Government to contract for any supply or service whatsoever. Further, NGA is not at this time seeking proposals and will not accept unsolicited proposals. Responders are advised that the U.S. Government will not pay for any information or administrative costs incurred in response to this RFI. All costs associated with responding to this RFI will be solely at the interested party’s expense. Not responding to this RFI does not preclude participation in any future RFP, if any is issued.

2. Soliciting feedback

2.1. What incentives or motivating factors would encourage an interested contractor to identify/incorporate efficiencies when modernizing current systems, services, and processes supporting dissemination of FG?

2.2. With SCDS being mostly back-end services, how would an interested Contractor demonstrate completed work to the Government? And how often?

2.3. NGA has some SCDS microservices in NGA’s operational environment.

2.3.1. How would an interested Contractor take advantage of existing code? Would you use it as a reference, reuse/repurpose it, or develop something new?

2.4. How would an interested Contractor approach the integration of systems with different tech stacks and mission sets into a unified architecture? (Front end, Back end, Databases, Application layers, etc.)

2.5. How would an interested Contractor follow, or modify, the use of SAFe Agile methodology when modernizing IT systems at NGA?

Data Ingest and Management: (reference PWS section 4.1)

2.6. How would an interested Contractor adapt to new product types that are produced over time?

2.7. How would an interested Contractor adapt to new data formats that may emerge over time (Ex. NITF, JSON, STAC, COG, etc…)?

2.8. How would an interested Contractor adapt to increasing data volumes and velocity?

2.9. What would an interested Contractor propose (cloud, on-prem, or hybrid) as the most cost-effective option for each of the following functions, and what would be the general design? 1) Large scale Source FG file transfers, and 2) Tile Generation for FG products.

Condition & Catalog: (reference PWS section 4.2)

2.10. How would an interested Contractor position products/content as potential raw data sources for future Dissemination capabilities?

Disclosure & Release: (reference PWS section 4.3)

2.11. How would an interested Contractor ensure that content/data is never over-shared with unauthorized persons or Non-Person Entities (NPE), and yet provide content/data search capabilities?

Dissemination Services: (reference PWS section 4.4)

2.12. How would an interested Contractor fully or partially automate existing or new dissemination related processes?

2.13. How would an interested Contractor sync content across external nodes?

2.14. How would an interested Contractor adapt to and take advantage of increasing “over the wire/electronic” digital delivery of content from vendors?

2.15. How would an interested Contractor improve the data Extract Transform Load (ETL) process for digital delivery (Ex. from electronic hard media to complete digital delivery)?

2.16. What design elements would an interested Contractor recommend to provide Open GEOspatial Consortium (OGC) Compliant Services for Source FG content?

2.17. How would an interested Contractor improve rapid and relevant discovery of new data for the user and/or client applications?

2.18. How would an interested Contractor increase product/data utility, reuse, and Return On Investment (ROI) for the agency and end-users alike?

User Interface: (reference PWS section 4.5)

2.19. How would an interested Contractor improve User Experience (UX) of Degraded, Denied, Intermittent and Limited (DDIL) environment users?

2.20. How would an interested Contractor improve the accessibility and User Experience (UX) of user's interactions with NGA "Dissemination" services?

2.21. What would an interested Contractor propose as the best solution for collecting Business Analytics / Business Intelligence on products/data (content ingest and dissemination)?

3. Planned Acquisition:

3.1. The period of performance for this requirement is one (1) 12-month base year and four (4) twelve-month option years. The anticipated contract award date is NLT FY25Q3.

4. Performance and locations:

4.1. The primary place of performance will be the contractor facility, preferably within close proximity to NGA Washington (National Capital Region) or NGA St Louis (St Louis, MO). The specific location will be agreed upon at contract award.

5. Constraints and Limitations:

5.1. The Contractor shall ensure Contractor personnel performing information assurance (IA) functions possess and maintain appropriate certifications. Personnel performing IA functions shall achieve and maintain the relevant IA training certifications as specified by the current versions of DoD 8570.01-M and NGA Instruction 8010.2 which includes reference to NGA Instruction 8010.

5.2. Security certification and accreditation expertise shall include, but is not limited to: DCID 6/3, Intelligence Community Directive ICD 503, FISMA, and Xacta.

6. Requirements:

6.1. Responses must only contain UNCLASSIFIED information and be marked “UNCLASSIFIED” on all pages in both the header and footer. No classified information may be included in your response.

6.2. Neither proprietary or classified concepts, nor classified information shall be included in the submittal. Input on the information contained in the responses may be solicited and reviewed by NGA non-Government consultants or experts who are bound by appropriate non-disclosure agreements.

7. Administrative:

7.1. Information to include the following as a minimum: Name, mailing address, phone number, company website, e-mail of designated point(s) of contact, and GSA Schedule (if applicable).

8. Past Performance:

8.1. COMMERCIAL: Provide relevant details, if any, on the responder providing the same or similar services offered or made to the general public or to non-governmental entities for purposes other than governmental purposes in the last three (3) years. Relevant details should include, but not be limited to, information regarding the contract value, period of performance, responder performing as a prime or subcontractor, customary practices (warranty, financing, discounts, contract types, etc.) under which the sales of the service(s) are made, security details, the customary practices regarding customizing, modifying, or tailoring of a service(s) to meet customer needs and associated costs, the kinds of factors that are used to evaluate performance; the kinds of performance incentives used; the kinds of performance assessment methods commonly used; the common qualifications of the people performing the services; and requirements of law and/or regulations unique to these service(s), that can demonstrate the responder’s abilities and capacity to meet NGA’s potential requirements.

8.2. GOVERNMENT: Provide relevant details, if any, on the responder providing the same or similar services offered or made to Government agencies, other than NGA, in the last three (3) years. Relevant details should include, but not be limited to contract value, period of performance, contract number, agency, responder performing as a prime or subcontractor, type of pricing and/or cost, security details, the kinds of factors used to evaluate performance; the kinds of performance incentives; the kinds of performance assessment methods; the qualifications of the people performing the services; and any unique terms and conditions, that can demonstrate the responder’s abilities and capacity to meet NGA’s potential requirements.

8.3. NGA: Provide relevant details, if any, on the responder providing the same or similar services offered or made to NGA in the last three (3) years. Relevant details should include, but not be limited to contract value, period of performance, contract number, program name, responder performing as a prime or subcontractor, type of pricing and/or cost, security details, the kinds of factors used to evaluate performance; the kinds of performance incentives; the kinds of performance assessment methods; the qualifications of the people performing the services; and any unique terms and conditions, that can demonstrate the responder’s abilities and capacity to meet NGA’s potential requirements.

9. Recommendations:

9.1. The responder is invited to provide information and recommendations for fashioning this proposed acquisition. Recommendation areas may include the type of contract, anticipated contract terms & conditions, incentives, variations in delivery schedule, price and/or cost proposal support, data requirements, contract pricing, and any other areas that the responder believes is relevant for the Government to achieve its stated objectives. The responder may opine regarding what portion of the work could be set-aside for small businesses if all the required work cannot be provided by a small business. Details to support any recommendations for partial small business set-asides should be included.

10. Follow on Discussions Clause:

10.1. The Government representatives may or may not choose to meet with interested vendors whom responded to the RFI. Such meetings and discussions would only be intended to get further clarification of potential capability, especially any development and certification risks.

11. Questions:

11.1. Questions and the whitepaper regarding this RFI should be submitted in writing by e-mail to Victoria.K.Le@nga.mil

12. Responses:

12.1. Interested parties are directed to respond to this RFI with a white paper.

12.2. White paper shall be in Microsoft Word for Office or compatible format and shall not exceed 10 pages. A page is defined as each face of an 8½” x 11” sheet with information contained within a one-inch margin on all sides. Font type shall be Times New Roman 12 point.

12.3. Interested parties are encouraged to utilize the Comment Matrix format in their white paper when providing comments, questions, and/or suggestions to the draft SOW.

12.4. Responses containing the white paper are due no later than the date and time referenced on SAM.gov. Responses shall be limited to and submitted via e-mail only as a message attachment to the Government Point of Contacts provided with the message subject line “FDM RFI Response – Contractor Name”.

12.5. Proprietary information, if any, should be minimized and MUST BE CLEARLY MARKED. To aid the Government, please segregate proprietary information. Please be advised that all submissions become Government property and will not be returned.

13. Summary:

13.1. This RFI is intended to update Industry and for the Government to identify sources that can provide the needed services to fulfill the Government’s requirements. The information provided in this RFI is subject to change and is not binding to the Government. The Government has not made a commitment to procure any of the RFI requirements discussed, and release of this RFI should not be construed as such a commitment or as authorization to incur cost for which reimbursement would be required or sought. All submissions become Government property and will not be returned.

14. PWS Comment Matrix for FDM:

COMMENT #
PWS PAGE #
PWS SECTION
COMMENT/QUESTION/SUGGESTION

File details come from the government source that posted it. Updated .