Opportunity

SAM #128PTA27Q0009

USDA RMA Market Research for CDW, HyDRA, and Geospatial Operations Support

Buyer

USDA OCP POD Acquisition Management Branch

Posted

November 17, 2026

Respond By

November 30, 2026

Identifier

128PTA27Q0009

NAICS

541512, 541511, 541519, 541370, 518210

USDA RMA is seeking market information on integrated operations and modernization support for its compliance data, analytics, and geospatial environment. - Government buyer: U.S. Department of Agriculture (USDA), Risk Management Agency (RMA), through the USDA Office of Procurement Operations, Procurement Operations Division. - Scope: Operate, maintain, secure, support, and modernize the Compliance Data Warehouse (CDW), HyDRA analytics portal, and HyDRA Maps geospatial environment within USDA’s Enterprise Data Analytics Platform and Toolset. - Named platforms and services: Tableau, Databricks, FME, ArcGIS Enterprise, and PRISM Weather are identified for integration and support. No prime contractor or awardee is named. - Requested services: Data engineering and warehouse operations; analytics, anomaly detection, machine learning, and responsible AI; geospatial operations and operational-layer products; rules-engine support; platform integration; modernization and migration; monitoring, security, governance, continuity, transition, and user support. - Users and mission: Support RMA, Approved Insurance Providers, Farm Service Agency users, and other authorized stakeholders involved in Federal Crop Insurance Program operations. - Notable requirements: The capability is expected to provide secure, integrated operations across data, analytics, and geospatial functions. Respondents are asked to provide evidence of capabilities and approaches, including staffing, transition, risks, dependencies, restrictions, and rough-order-of-magnitude costs. - Procurement status: This is market research, not a formal solicitation. No quantities or period of performance are specified.

Description

Sources Sought Notice Compliance Data Warehouse (CDW), HyDRA, HyDRA Maps, Analytics, Geospatial Services, and Operational Support

This Sources Sought Notice is issued solely for informational and planning purposes and does not constitute a Solicitation, Request for Proposal (RFP), Invitation for Bid (IFB), or Request for Quotation (RFQ). This notice is issued for market research purposes only pursuant to FAR Part 10. This notice does not obligate the Government to issue a future solicitation, award a contract, reimburse respondents for costs incurred, or otherwise pay for information submitted in response to this notice. Responses will be used to assess market capability and acquisition strategy development. The United States Department of Agriculture (USDA), Risk Management Agency (RMA), is conducting market research to identify commercial, academic, nonprofit, and other qualified organizations capable of providing a fully integrated Compliance Data Warehouse (CDW) capability supporting enterprise data management, analytics, geospatial services, business intelligence, reporting, artificial intelligence, operational-layer development, and modernization activities within the USDA Enterprise Data Analytics Platform and Toolset (EDAPT). The Government seeks information regarding organizations capable of sustaining, operating, securing, modernizing, and enhancing the existing CDW environment while maintaining continuity of operations for RMA, Approved Insurance Providers (AIPs), Farm Service Agency (FSA) users, and other authorized stakeholders.

Respondent Instructions Interested organizations shall submit a written capability response addressing every requirement identified in this notice. Respondents shall complete a requirement-by-requirement compliance matrix and assign one of the following compliance statuses to each requirement: Fully Complies Partially Complies Does Not Comply Requires Future Development For any response identified as other than Fully Complies, respondents shall provide: Description of the limitation. Proposed alternative solution or approach. Required development activities, transition work, or modernization efforts. Government dependencies. Estimated date the capability would become operational. Assessment of potential impacts to: Cost Schedule Performance Security Continuity of operations Technical and programmatic risk These draft requirements are provided solely for market research purposes and may be revised, expanded, reduced, or removed prior to any future solicitation. Respondents shall clearly distinguish between: Existing operational capabilities, Capabilities currently under development, Planned future capabilities, Third-party capabilities, Proposed concepts not yet demonstrated in production.

Purpose The Government seeks to determine the availability of organizations capable of providing a fully integrated solution that: Operates and maintains the Compliance Data Warehouse (CDW). Supports HyDRA and HyDRA Maps. Provides enterprise geospatial operations. Supports Tableau, Databricks, FME, and ArcGIS Enterprise. Maintains operational layers and analytical products. Provides anomaly detection and advanced analytics. Supports machine learning and responsible artificial intelligence. Performs modernization and migration activities. Supports governance, security, continuity, and operational readiness requirements. Delivers nationwide analytical and geospatial products supporting Federal Crop Insurance Program (FCIP) operations.

Mandatory Requirements

1. Core Capability and Operational Baseline 1.1 Complete Integrated Capability The respondent shall provide, operate, maintain, support, secure, and enhance the current operational state and functionality of the Risk Management Agency Compliance Data Warehouse as an integrated data, analytics, reporting, and geospatial capability within the USDA Enterprise Data Analytics Platform and Toolset. The complete capability shall include: HyDRA as RMA's primary System of Analytics portal; HyDRA Maps as the integrated geospatial user experience; Separate RMA, AIP, and FSA portal experiences; Reports; Maps; Analytical tools; Document services; Data products; Interfaces; Integrations; and Associated user workflows.

<p><strong>1.2 Required Operational Availability by March 1, 2027</strong></p>
<p>HyDRA, HyDRA Maps, existing reports, operational layers, mapping workflows, exports, document services, interfaces, and integrated analytical tools shall be fully operational and available to authorized users no later than March 1, 2027.</p>
<p>Replacement functionality shall not satisfy this requirement unless it has successfully completed RMA-approved:</p>
<ul>
  <li>Functional testing</li>
  <li>Security testing</li>
  <li>Accessibility testing</li>
  <li>Performance testing</li>
  <li>Data-reconciliation testing</li>
  <li>Continuity testing</li>
  <li>User acceptance testing</li>
</ul>

<p><strong>1.3 Equivalent or Superior Operational Outcome</strong></p>
<p>The proposed solution shall meet or exceed the Government-defined functional and performance baseline of the current CDW capability.</p>
<p>The solution shall support:</p>
<ul>
  <li>PASS crop insurance data</li>
  <li>FSA data</li>
  <li>Actuarial data</li>
  <li>Weather and hazard data</li>
  <li>Geospatial analytics</li>
  <li>Imagery</li>
  <li>Cadastral information</li>
  <li>Administrative boundaries</li>
  <li>gSSURGO soils data</li>
  <li>Other RMA-approved data sources</li>
</ul>
<p>The environment shall support:</p>
<ul>
  <li>Data engineering</li>
  <li>Geospatial processing</li>
  <li>Statistical analysis</li>
  <li>Machine learning</li>
  <li>Responsible AI</li>
  <li>Business intelligence</li>
  <li>Semantic governance</li>
  <li>APIs</li>
  <li>Dashboards</li>
  <li>Web mapping</li>
  <li>Secure information delivery</li>
</ul>
<p>Unless otherwise approved by RMA, Government information, code, workflows, models, and business rules shall be maintained in Government-approved environments.</p>

2. HyDRA and HyDRA Maps Operations Respondents shall demonstrate their ability to operate, secure, monitor, support, modernize, and enhance both HyDRA and HyDRA Maps. The capability shall include:

<p><strong>2.1 Portal Operations</strong></p>
<p>Support for:</p>
<ul>
  <li>RMA users</li>
  <li>AIP users</li>
  <li>FSA users</li>
</ul>
<p>Including:</p>
<ul>
  <li>Role-based access</li>
  <li>Permissions</li>
  <li>Reports</li>
  <li>Maps</li>
  <li>Documents</li>
  <li>Downloads</li>
  <li>Search capabilities</li>
  <li>Export functions</li>
  <li>Weather information</li>
  <li>Link analysis capabilities</li>
  <li>Mapping tools</li>
  <li>System notices and user support</li>
</ul>

<p><strong>2.2 Geospatial Operations</strong></p>
<p>HyDRA Maps shall provide approved access to:</p>
<ul>
  <li>Operational Layers</li>
  <li>Imagery</li>
  <li>Weather products</li>
  <li>Common Land Units</li>
  <li>Resource Land Units</li>
  <li>Points of Reference</li>
  <li>Production-unit locations</li>
  <li>Administrative boundaries</li>
  <li>Other approved spatial datasets</li>
</ul>
<p>Users shall be able to:</p>
<ul>
  <li>Search locations</li>
  <li>Navigate maps</li>
  <li>Query geographies</li>
  <li>Filter layers</li>
  <li>Export data</li>
  <li>Connect analytical results to mapped features</li>
</ul>

<p><strong>2.3 Operational Layers</strong></p>
<p>Respondents shall support, at a minimum:</p>
<ul>
  <li>Pasture, Rangeland and Forage (PRF)</li>
  <li>AIP Operational Footprints</li>
  <li>Cause of Loss</li>
  <li>Beginning Farmer and Rancher</li>
  <li>Prevented Planting</li>
  <li>Producer Score</li>
  <li>Future RMA-approved operational layers</li>
</ul>

<p><strong>2.4 Data Refresh and Publication</strong></p>
<p>Respondents shall demonstrate ability to:</p>
<ul>
  <li>Refresh operational data monthly</li>
  <li>Publish approved releases</li>
  <li>Preserve historical versions</li>
  <li>Maintain metadata</li>
  <li>Publish source lineage</li>
  <li>Support continuity when upstream sources are delayed</li>
</ul>

<p><strong>2.5 Platform Integrations</strong></p>
<p>Support and maintenance of integrations with:</p>
<ul>
  <li>CDW</li>
  <li>Databricks</li>
  <li>Tableau</li>
  <li>ArcGIS Enterprise</li>
  <li>FME</li>
  <li>PRISM Weather</li>
  <li>Identity Management Services</li>
  <li>APIs</li>
  <li>Government-approved systems</li>
</ul>

<p><strong>2.6 Monitoring and Reporting</strong></p>
<p>Capabilities shall include:</p>
<ul>
  <li>Availability monitoring</li>
  <li>Security monitoring</li>
  <li>Performance monitoring</li>
  <li>Capacity management</li>
  <li>Incident response</li>
  <li>Escalation procedures</li>
  <li>Root-cause analysis</li>
  <li>Monthly service reporting</li>
</ul>

3. Accountability, Readiness, Transition, and Security Respondents shall address their ability to meet the following requirements:

<p><strong>3.1 No Additional Government Workload</strong></p>
<p>The proposed approach shall not require RMA to assume additional operational responsibilities beyond those expressly defined in any future solicitation.</p>

<p><strong>3.2 Single Point of Accountability</strong></p>
<p>The respondent shall remain responsible for all subcontractors, cloud services, software providers, and third-party components.</p>

<p><strong>3.3 Operational Readiness</strong></p>
<p>Respondents shall identify which capabilities are currently operational and which require additional development.</p>

<p><strong>3.4 Transition and Continuity</strong></p>
<p>Respondents shall describe their approach to:</p>
<ul>
  <li>Transition planning</li>
  <li>Historical access preservation</li>
  <li>Portal continuity</li>
  <li>User support continuity</li>
  <li>Operational risk mitigation</li>
</ul>

<p><strong>3.5 Operations and Security</strong></p>
<p>Respondents shall demonstrate their ability to operate, secure, and support the current CDW environment, including ingestion and management of:</p>
<ul>
  <li>RMA PASS Data</li>
  <li>FSA Data</li>
  <li>Actuarial Systems</li>
  <li>PRISM Weather Data</li>
  <li>Satellite and Aerial Imagery</li>
  <li>Cadastral Data</li>
  <li>Administrative Boundary Data</li>
  <li>Soil Data</li>
</ul>
<p>Respondents shall further demonstrate scalable data pipelines supporting:</p>
<ul>
  <li>Effective-dated products</li>
  <li>Metadata management</li>
  <li>Semantic definitions</li>
  <li>Business definitions</li>
  <li>Lineage tracking</li>
  <li>Data reconciliation</li>
  <li>Quality controls</li>
  <li>Retention and archival</li>
  <li>Exception processing</li>
</ul>

4. Modernization, Analytics, and Rules Engine Respondents shall demonstrate capabilities supporting: Descriptive analytics Diagnostic analytics Predictive analytics Spatial analytics Machine learning Responsible AI Geospatial analytics Model governance Validation and monitoring 4.1 Pasture, Rangeland, and Forage Rules Engine Respondents shall demonstrate capability to: Complete development Validate results Deploy and operate Maintain and enhance the existing RMA Rules Engine supporting the Pasture, Rangeland, and Forage program. The rules engine shall convert approved policy and business requirements into transparent and auditable machine-executable rules.

5. Governance and Integrated Platform Support Respondents shall demonstrate experience supporting and integrating: Tableau Databricks FME ArcGIS Enterprise The response shall address: Governance Change control Release management Security Collaboration User support Knowledge transfer Lifecycle management

6. ArcGIS Enterprise Operations and Migration Respondents shall demonstrate experience with: ArcGIS Enterprise application-layer operations ArcGIS Enterprise 11.5 support ArcGIS Enterprise 12.x migration planning Geospatial governance Dependency management Migration rehearsals Production cutover planning Rollback procedures Stabilization activities Lifecycle support The Government is particularly interested in organizations with demonstrated experience migrating mission-critical ArcGIS Enterprise environments while maintaining continuity of operations.

7. Anomaly Analytics Deliverables Respondents shall demonstrate capability to produce RMA anomaly analytics products including: 7.1 Anomalous Producer List Capability to identify anomalous producers using the criteria described in this notice, including: High-loss producers High-yield loss producers Only-loss situations New producers with anomalous losses Repeat loss behavior Production-shifting indicators Producer scoring methodologies Linked-entity analysis Neighborhood analysis Cause-of-loss analysis 7.2 Anomalous Crop Insurance Agent and Loss Adjuster Listings Capability to identify: Anomalous crop insurance agents Added-land database anomalies Coverage-break anomalies New-business anomalies Just-cover producers Disproportionate losses Repeated excessive losses Larger policy loss anomalies Anomalous loss-adjuster behavior

8. Operational Layers and Geospatial Data Products Respondents shall demonstrate their ability to develop, maintain, publish, and support: PRF Operational Layer AIP Operational Footprints Cause of Loss Layer Beginning Farmer and Rancher Layer Prevented Planting Layer Producer Score Layer Capabilities shall include: Effective dating Metadata management Historical reproducibility Location resolution Confidence scoring Geospatial quality assurance Publication controls Auditability Security

9. Nationwide Analysis and Mapping Deliverables Respondents shall demonstrate capability to produce nationwide analytical and geospatial products. Specifically, respondents shall describe their ability to generate: Nationwide crop analysis Organic versus conventional production comparisons County-level and state-level ratio calculations Historical analyses Statistical validation Nationwide thematic map products using the methodology and criteria described in this notice.

10. Staffing Requirements Respondents shall describe personnel qualifications and availability for the following labor categories:

<p><strong>10.1 Project Manager</strong></p>
<p>Responsible for:</p>
<ul>
  <li>Project planning</li>
  <li>Resource coordination</li>
  <li>Schedule management</li>
  <li>Risk management</li>
  <li>Stakeholder communications</li>
  <li>Delivery oversight</li>
</ul>

<p><strong>10.2 Project Director</strong></p>
<p>Responsible for:</p>
<ul>
  <li>Contract oversight</li>
  <li>Organizational management</li>
  <li>Staff supervision</li>
  <li>Quality assurance</li>
  <li>Communications</li>
  <li>Meeting coordination</li>
  <li>Deliverable management</li>
  <li>Documentation oversight</li>
</ul>

<p><strong>10.3 Data Scientists</strong></p>
<p>PhD-qualified personnel experienced in:</p>
<ul>
  <li>Statistical modeling</li>
  <li>Machine learning</li>
  <li>Predictive analytics</li>
  <li>Experimental design</li>
  <li>Data interpretation</li>
  <li>Applied research</li>
</ul>

<p><strong>10.4 Senior Geospatial SME</strong></p>
<p>Personnel with demonstrated experience in:</p>
<ul>
  <li>Enterprise geospatial operations</li>
  <li>ArcGIS technologies</li>
  <li>Spatial analytics</li>
  <li>Geospatial data engineering</li>
  <li>Operational-layer development</li>
  <li>Geospatial governance</li>
</ul>

<p><strong>10.5 Broader SME Resources</strong></p>
<p>Personnel experienced in:</p>
<ul>
  <li>Federal Crop Insurance Program operations</li>
  <li>RMA business processes</li>
  <li>FSA systems and operations</li>
  <li>Agricultural production systems</li>
  <li>Program integrity</li>
  <li>Investigative analytics</li>
  <li>Data engineering</li>
  <li>Geospatial analytics</li>
  <li>Tableau</li>
  <li>Databricks</li>
  <li>FME</li>
  <li>ArcGIS</li>
</ul>

Mandatory Evidence and Compliance Response Respondents shall provide a complete compliance matrix covering every requirement element contained in this notice. For each requirement, respondents shall provide: Compliance status Objective evidence Current operational status Technical approach Data restrictions Software restrictions Government dependencies Transition requirements Staffing commitments Assumptions Rough-order-of-magnitude cost information Proposed alternative language (if any) The Government is particularly interested in identifying organizations capable of providing a fully integrated, operationally mature solution that minimizes transition risk, preserves continuity of operations, supports modernization objectives, and maintains the current mission capabilities of the RMA Compliance Data Warehouse environment.

Requested Response Information Interested organizations should provide: Organization name and contact information. Business size and socioeconomic status. Relevant contract vehicles. Description of corporate capabilities. Description of directly relevant projects performed within the last five years. Compliance matrix addressing all requirements. Estimated transition approach and timeline. Identification of key risks, assumptions, and dependencies. Information regarding any proprietary, licensing, hosting, or data restrictions.

Response Format The Government requests responses not to exceed 20 MB.

Disclaimer Participation in this Sources Sought Notice is voluntary. The Government will not reimburse respondents for any costs associated with preparing or submitting a response. Information received may be used in developing acquisition strategies, determining the availability of qualified sources, evaluating small business participation opportunities, and refining requirements for any future procurement. Responses will not be returned. The Government reserves the right to use any non-proprietary information submitted in response to this notice.

View original listing