(U) Mercury_RFI_031226_final.pdf

UNCLASSIFIED

(U) REQUEST FOR INFORMATION

(U) PEO Advanced Analytics – Analytic Technology (PAT) – Mercury Requirement

1.0 (U) DESCRIPTION & PURPOSE

1.1 (U) The National Geospatial-Intelligence Agency (NGA) is seeking information on how interested contractors could provide the services described below.

1.2 (U) The purpose of this Request for Information (RFI) is to identify sources that have access to an extensive set of knowledge, skills, experience, and resources to maintain and modernize known systems and the ability to rapidly support unanticipated capabilities. Additionally, NGA would welcome recommendations from industry on acquisition constructs for delivering mission responsive support for unforeseen requirements.

1.3 (U) 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. Furthermore, NGA is not at this time seeking proposals and will not accept unsolicited proposals. Respondents 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.0 (U) BACKGROUND

(U) The mission of NGA is to provide timely, relevant, and accurate Geospatial Intelligence

(GEOINT) to policy makers, the Intelligence Community (IC), Department of War (DoW), and other federal agencies and partners in support of national security. In support of this mission, the

PEOAA – Analytic Technologies (PAT) office develops and maintains a set of mission critical and mission essential software systems, applications, and databases constituting the analytic services for the National System for Geospatial-Intelligence (NSG).

(U) Although future NSG analytic capabilities are extensively planned and prioritized for implementation, past experience and objective risk management forecast that there will be unanticipated changes to mission needs and requirements including adoption of emergent systems and tools. These emergent requirements will require sustainment and modernization efforts to operationalize the system to meet analytic mission needs. Many of these analytic systems do not align specifically to a singular mission in the PAT portfolio and require cross-project support. The ongoing sustainment and modernization of cross-project capabilities throughout the lifecycle of the system would be supported through the Mercury requirements.

(U) The Mercury requirement will be the primary sustainment services provider within PAT, providing services needed for end-to-end operations and lifecycle management of existing and emerging analytic systems that directly or indirectly support the execution of the Analysis mission at NGA, and in support of the Analytic Services Production Environment for the NSG

(ASPEN) major system acquisition. The Mercury requirement is a direct follow-on to the

Chinook contract with similar scope and requirements.

(U) The Mercury scope of work includes the lifecycle support of the Analytic Technology systems and applications identified below, and any additional systems and applications that may be added to the Mercury requirement as they become operational or require terminal support until system disposition. A key to the success of the Mercury requirement will be the ability to rapidly transition current emerging analytic capabilities onto contract and then provide lifecycle services including sustainment and enhancement activities. Mercury supports a rapid response to the current and future cross-project future requirements, critical system transitions, and emerging development efforts essential to empower warfighters and analysts.

(U) The Mercury requirement is designed for a rapidly changing system environment marked by frequent technological advancements, software updates, regulatory shifts, and emerging security threats. Mercury will prioritize interoperability, scalability, and resilience to include the use of

Commercial Off-The-Shelf (COTS) software. These protocols will enable seamless integration of new tools, Artificial Intelligence (AI) enhancements, and evolving data standards, preventing disruptions to operational workflows and guaranteeing sustained performance amid dynamic conditions. In these instances, a nimble and agile contract approach is required to adapt to the changing needs of the agency and the warfighter.

(U) The potential acquisition would provide a range of services covering the full system life-cycle on an as-needed basis. Service needs include:

1. Systems Engineering and Integration: responsible for the complete lifecycle management to ensure the efficient and effective operations of the supported analytic systems.

2. Operations Support: ensure the operation and availability of supported analytic systems.

3. Software Maintenance: perform Corrective, Adaptive, Preventive, and Perfective maintenance of supported analytic systems.

4. Security Engineering: provide cybersecurity engineering and oversight to maintain optimum cyber-operations and compliance with all NGA Assessment and Authorization processes.

5. Technical Support Services: perform cross-functional and enterprise functions that enable the performance of the other service categories to include but not limited to subject matter expertise, configuration management, training, content management, user engagement, and program scheduling.

6. Software Development: services to add new capabilities to existing analytic systems or create new systems with capabilities supporting the analysis mission.

7. Ad-hoc Engineering: provide one or more services above for short-term effort which may be unrelated to specific program or system.

(U) Systems that are expected to transition to a Mercury contract, as of the issuance of this RFI, are outlined in the table below. Additional system needs are anticipated during the Period of

Performance (PoP). These unanticipated needs would be considered in scope and may be added to the potential contract during performance. The resultant activities could require surge capacity. Breadth of expertise, flexibility, and responsiveness is needed to ensure mission continuity and success.

(U) Industry partners should be aware that just as systems may be added to the Mercury area of responsibility, systems may also be deprecated as user requirements evolve and the PEO-AA portfolio strategy matures with more targeted business arrangements intended to provide long-term or revolutionary capability delivery. PEO AA will be conducting additional market research in the coming months around solutioning concepts for key technology areas, such as computer vision, to obtain feedback specifically on these topics of capability portfolio management.

Potential Mercury Supported Systems and Applications

Mercury Systems and Applications

Advanced Analyst Augmentation Analytical Cloud Enablement Systems (4ACES) enables big data analytics to support NGAs ability to make data-driven decisions and automate business processes through algorithms.

Atlas is a cloud-based repository for manually created structured data to support object-based production.

Commercial – Joint Mapping Tool Kit (CJMTK) provides the Mapping, Charting, Geodesy, and Imagery

(MCG&I) functionality for mission applications in the Common Operating Environment (COE).

Computer Vision Data Store (CVDS) is an enterprise repository that stores computer vision detections and labels produced by numerous internal and external models. Detections are made available to consumers via an

OGC compliant interface.

Computer Vision Integration Environment (CVI) is an environment used for evaluating and integrating CV models into CVP.

Computer Vision Processing Environment (CVP) provides services, tools, and models for generating automated observations and detections from imagery sources.

DishTrak provides efficient measurement tools for imagery analysts, trends of dish orientations for intelligence analysts, and alert services based on dish activity.

GEOINT Review of Imagery Products (GRIP) provides the ability to adjudicate GEOINT Maritime Object detection products (TIPs).

Geospatial Observable Web Kit (GOWK) is a web-based application used to design and implement flexible data schemas to capture georeferenced observations.

SOM Companion (SOM-C) is a cloud-based web application designed to provide users the ability to capture and record observations and objects with searchable metadata and add them to the repository of shared GEOINT databases.

SOM Sandbox (SSBX) is a collection of services that enable the storage and transformation of observations and data that is not yet compliant with Atlas vocabulary or the specific mission vocabulary.

Target Coordinate Mensuration Validation (TCMV) is the system used to perform the Independent

Verification and Validation (IV&V) of mensuration tools, methods, and GEOINT sources.

Tearline is a web-based portal providing access to unclassified intelligence reports developed through partnerships with nonprofit organizations and universities

Watchman is an Automated Target Recognition (ATR) reporting application that affords analysts the ability to interact with deep neural networks and benefit from state-of-art artificial intelligence via an intuitive web application.

Watchtower (formerly known as ASPEN SOM CV UI and SOM CNXT) is a web user interface application providing Computer Vision (CV) object detection, object classification, alerting, and imagery prioritization. This includes a user interface with tools and models for generating automated observations and detections from imagery sources, and managing data structures and export capabilities of Atlas.

2.1 (U) Potential Acquisition Approach

(U) The Government is considering flexible contract vehicles that can accommodate changing levels of support and the requisition of specialized expertise to optimize a range of analytic technologies. This may include a single contract or Indefinite Delivery, Indefinite Quantity

(IDIQ) with one or multiple vendors.

2.2 (U) Performance

(U) Estimated Period of Performance (POP): The Government is considering a minimum of five-year period of performance (in annual increments) but may pursue a longer-term contract in order to stabilize support throughout key program lifecycle phases.

(U) Location(s): Government (NGA Washington or NGA St. Louis) and Contractor Facilities

2.3 (U) Security Requirements

(U) The following security requirements are anticipated to apply to this acquisition:

• (U) Classification level for contractor facility may be up to TOP SECRET/Sensitive

Compartmented Information (SCI)

• (U) Contractors will need access to a SCI Facility (SCIF) with accredited SCI network access at the time of award.

• (U) The contractor may require and is authorized to have access to accountable

COMSEC information and equipment. Access to Communications Security

(COMSEC) information requires a final U.S. Government Personnel clearance at the appropriate level. Access to any COMSEC information requires special briefings at the contractor's facility.

• (U) The Director, NGA has security responsibility for SCI released to the contractor or developed under this requirement.

2.4 (U) Organizational Conflict of Interest

(U) This acquisition is for the development and sustainment of Government developed, contractor developed, Open Source Software (OSS) and Custom Code items. Potential Offerors should identify actual or potential conflicts as early as possible to the Contracting Officer (CO).

In accordance with FAR Part 9.5, please discuss any performance which may lead to an

Organizational Conflict of Interest (OCI) and how the Offeror would mitigate, avoid, or neutralize the conflict.

3.0 (U) Requested Information

(U) Responses may contain UNCLASSIFIED and CLASSIFIED concepts and information, but must be portion marked.

(U) Input on the information contained in the responses may be reviewed by NGA non-

Government consultants / experts who are bound by appropriate non-disclosure agreements.

(U) Responses should focus on those areas where they are able to provide substantive input.

Input is not required for every question.

3.1 (U) Questions for Industry – Acquisition and Contracting

(U) Question 3.1.1: What risks does the Contractor identify in meeting this diverse and challenging set of requirements, and what mitigation strategies would be recommended to the

Government to address these risks effectively? How should the Government consider compartmentalizing the diverse capabilities on separate task orders or contracts such that they receive the right industry expertise, while minimizing GPMO administrative burdens and allowing for easy onboarding/offboarding of capabilities?

(U) Question 3.1.2: What staffing approaches would the Contractor take to address for maintaining workforce flexibility, ensuring appropriate skill coverage, and adapting to a diverse and changing set of requirements?

(U) Question 3.1.3: What mix of contracting elements (e.g., contract types, CLIN/scope bucketing, task order partitions, etc.) would you recommend in order to balance incentivized performance, dynamic capacity management, and efficient contract administration?

(U) Question 3.1.4: What experience has the Contractor had managing a contract with multiple stakeholders, priorities, and changing or unanticipated requirements?

(U) Question 3.1.5: The Government is increasing its acquisition focus on opportunities to accelerate integration of AI and other advanced/commercial technologies to more quickly close capability gaps. What recommendations do you have for inserting scope, business arrangements, or other mechanisms into future contracts that will enable these objectives?

3.2 (U) Questions for Industry – Technical

(U) Question 3.2.1: Describe the Contractor's experience in rapidly transitioning analytic systems during contract performance (i.e., transition-in and transition-out). For each relevant project example, please state the number of systems that were retired/decommissioned and the number of Full-Time Equivalents (FTEs) from the Contractor's team that were involved in the transition effort.

(U) Question 3.2.2: Describe the Contractor's past performance sustaining analytic applications, particularly applications that transitioned from development to sustainment. For any examples provided, please include the application's name and function, the approximate number of active users supported, the size of the Contractor's sustainment team in FTEs, and the key performance metrics the Contractor was responsible for.

(U) Question 3.2.3: What specific approaches would the Contractor recommend for transitioning systems from development to operations, specific to the NGA environment? Describe the recommended methodology for ensuring a smooth transition process, including how to handle documentation, knowledge transfer, and operational readiness.

(U) Question 3.2.4: What are some examples of modern DevSecOps pipelines that you use for

IC Software deployments? How do you see these advancing/evolving in the near future while adhering to strict Security requirements?

(U) Question 3.2.5: With the increase and implementation of AI/ML technical approaches, does the Contractor have recommendations that may benefit the draft PWS? Describe previous experience you have in this effort and how these recommendations were implemented including continuous technology exploration, evaluation, and integration supporting the delivery of state-of-the-art capabilities to mission.

(U) Question 3.2.6: The Government anticipates a substantial increase in the volume of overhead and theater GEOINT collection during the contract's Period of Performance (PoP).

What is your proposed approach for managing new data types (e.g., multi-spectral imagery or synthetic aperture radar), emerging data sources (e.g., commercial satellites or unmanned systems), and evolving workflows (e.g., automated processing or AI-driven analytics)? Please include details on data ingestion, scalability, interoperability, security, and adaptation strategies to ensure efficient processing and analysis

(U) Question 3.2.7: Describe Contractor's experience in metrics collection. For each example, please state what specific metrics have provided the most value to the program.

(U) Question 3.2.8: Describe your experiences with rapidly supporting unanticipated yet critical emerging mission requirements while balancing the delivery of planned mission requirements in the Program Increment (PI)?

3.3 (U) Administrative

(U) Responses should include the following:

3.3.1 (U) Name, mailing address, overnight delivery address (if different from mailing address), phone number, fax number, company website, and e-mail of designated point(s) of contact.

3.3.2 (U) Business Type.

(U) Based upon North American Industry Classification System (NAICS) code 541511 –

Custom Computer Programming Services applicable to this acquisition, the respondent is to provide answers to the following questions:

Table is UNCLASSIFIED

To be considered for a Small Business set-aside, at least 50 % of the cost of contract performance incurred for personnel shall be expended for employees of the respondent. (FAR 52.219-14, Limitation of Subcontracting)

RESPONSE

Are you a Small Business? (FAR 19.102), If so, which type: ☐ YES ☐ NO

Small Disadvantaged business concern? (FAR 19.304) ☐ YES ☐ NO

Service Disabled small business? (FAR 19.14) ☐ YES ☐ NO

8(a) Small Disadvantaged participant? (FAR 19.8) ☐ YES ☐ NO

HUBZone small business? (FAR 19.13) ☐ YES ☐ NO

Woman-Owned Small Business? (FAR 19.15) ☐ YES ☐ NO

Involved in a mentor and/or protégé program? (DFARS 219.71) ☐ YES ☐ NO

Table is UNCLASSIFIED

3.3.3 (U) Recommendation for alternative NAICS Code? Provide rationale for any NAICS

Code applicable to the planned acquisition other than the NAICS code identified above.

3.3.4 (U) Unique Entity ID: _________________

3.3.5 (U) Commercial and Government Entity (CAGE) Code:

3.3.6 (U) Defense facility security clearance? What type? What level?

http://www.census.gov/cgi-bin/sssd/naics/naicsrch?chart=2012 http://www.naics.com/naicsfiles/Size_Standards_Table2013.pdf http://www.acquisition.gov/far/current/html/Subpart%2019_1.html http://www.acquisition.gov/far/current/html/Subpart%2019_3.html http://www.acquisition.gov/far/current/html/Subpart%2019_14.html#wp1093836 http://www.acquisition.gov/far/current/html/Subpart%2019_8.html#wp1092796 http://www.acquisition.gov/far/current/html/Subpart%2019_13.html#wp1094801 http://www.acquisition.gov/far/current/html/Subpart%2019_15.html#wp1094868 http://www.acq.osd.mil/dpap/dars/dfars/html/current/219_71.htm

3.3.7 (U) Accounting system, if applicable? Date of last audit? Audit performed by?

Determined adequate/inadequate?

3.3.8 (U) Purchasing system? Date determined adequate or inadequate?

3.3.9 (U) Timekeeping system? Date of last audit? Who performed? Determined adequate/inadequate?

3.3.10 (U) Do you hold a GSA Federal Supply Schedule (FSS) contract applicable to the NAICS code (s) identified above? If yes, provide contract number(s).

3.3.11 (U) Are you registered in SAM?

3.3.12 (U) Are you interested in: Prime contract? Teaming to include Joint Venture?

Subcontractor opportunities?

3.3.13 (U) Include additional details that are not already requested based on the constraints of the information request.

3.4 (U) Experience

3.4.1 (U) Commercial.

(U) Provide relevant details on the respondent 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 to NGA’s proposed acquisition should include, but not be limited to, information regarding the contract value, size and length of the effort, respondent 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 respondent’s abilities and capacity to meet NGA’s objectives.

3.4.2 (U) Government.

(U) Provide relevant details on the respondent providing the same or similar services offered or made to Government agencies other than NGA in the last three (3) years. Relevant details to

NGA’s proposed acquisition should include, but not be limited to contract value, information regarding the contract number, agency, respondent performing as a prime or subcontractor, size and length of the effort, 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 respondent’s abilities and capacity to meet NGA’s objectives.

3.4.3 (U) NGA.

(U) Provide relevant details on the respondent providing the same or similar services offered or made to NGA in the last three (3) years. Relevant details to NGA’s proposed acquisition should include, but not be limited to contract value, information regarding the contract number, program name, size and length of the effort, respondent 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 respondent’s abilities and capacity to meet NGA’s objectives.

3.5 (U) Capabilities

(U) Respondents shall identify and describe specific capabilities to meet the proposed acquisition set forth in section 2 of this RFI.

3.5.1 (U) Requirement capabilities that the respondent currently possesses. Responses should include the relevant information regarding specific skills, experience, and security clearances that its employees, by labor category, currently possess in performing these services, and any needed hardware or software.

3.5.2 (U) Extent to which the respondent has the ability to meet the proposed acquisition.

3.5.3 (U) Notional schedule and type of plan for transition and performance periods based on previous or similar work efforts.

3.5.4 (U) Security capabilities and plans that demonstrate the ability to meet NGA’s security requirements beginning at contract award and throughout the POP.

3.5.5 (U) Extent to which the respondent is aware of any potential OCI issues in accordance with FAR Part 9.5 or any non-mitigatable OCI related issues to current development work at

NGA.

3.6 (U) Recommendations

(U) The respondent is invited to provide any other information and recommendations for fashioning this proposed acquisition. Recommendation areas may include the anticipated contract terms & conditions, incentives, variations in delivery schedule, data requirements, contract pricing, and any other areas that the respondent believes is relevant for the Government to achieve its stated objectives. The respondent may suggest 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.

4.0 (U) Responses

(U) Interested parties are directed to respond to this RFI with a white paper. The white paper shall be submitted in Microsoft Word for Office (or compatible) format and shall not exceed 15 pages. A page is defined as one side of an 8½” x 11” sheet with content contained within one-inch margins on all sides. Font shall be 12-point Times New Roman.

(U) RFI response email subject line format:

Request for Information (RFI): MERCURY_CompanyName_YYYYMMDD.

(U) RFI response file name format:

RFI_MERCURY_CompanyName_YYYYMMDD

(U) Responses containing the white paper are due no later than 12:00 PM ET on 2 April 2026.

(U) Responses shall be submitted to:

UNCLASSIFIED: jokera.s.mcneil@nga.mil phong.v.chau@nga.mil mailto:jokera.s.mcneil@nga.mil mailto:phong.v.chau@nga.mil

CLASSIFIED: jokera.s.mcneil@coe.ic.gov phong.v.chau@coe.ic.gov

(U) 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.

5.0 (U) MEETINGS AND DISCUSSIONS

(U) The Government representatives may or may not choose to meet with potential RFI service providers. Such meetings and discussions would only be intended to get further clarification of potential capability, especially any development and certification risks.

6.0 (U) QUESTIONS

(U) Questions and comments regarding this RFI shall be submitted to:

UNCLASSIFIED: jokera.s.mcneil@nga.mil phong.v.chau@nga.mil

CLASSIFIED: jokera.s.mcneil@coe.ic.gov phong.v.chau@coe.ic.gov

(U) Questions and comments are due no later than 12:00 PM ET on 19 March 2026. Early submission of comments/questions is encouraged. The Government reserves the right to not respond to any question/comment.

7.0 (U) SUMMARY

(U) This RFI is only intended for the Government to identify sources that can provide the needed services to fulfill the Government’s objectives. 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.

mailto:jokera.s.mcneil@coe.ic.gov%20 mailto:jokera.s.mcneil@nga.mil mailto:phong.v.chau@nga.mil mailto:jokera.s.mcneil@coe.ic.gov%20

PERFORMANCE WORK STATEMENT (PWS)

COMMENT MATRIX FOR MERCURY

REQUEST FOR INFORMATION

COMMENT

PWS

PAGE #

PWS

SECTION

COMMENT/QUESTION/SUGGESTION