UNCLASS_DRAFT_OESET_Data_Platform_Market_Survey.pdf

UNCLASSIFIED

OESET – Data Platform Market Survey

PROCUREMENT OBJECTIVE AND BACKGROUND

(U) Organization and Mission Overview/Background

(U) In 2023, ODNI establishing the Office of Economic Security and Emerging Technologies (OESET) in response to increasing Administration and congressional demand for improved intelligence on the application of disruptive technologies and related global supply chains. Improved IC posture in this area is critical to enabling the whole-of-government response that maintains United States’ economic and technological competitive advantage and ensures U.S. access to good and services central to its national security.

(U) The data platform is a data fusion system designed to serve both National Intelligence Program (NIP)-funded Title 50 Intelligence Community (IC) agencies and select U.S. Government (USG) organizations, including relevant Title 10 and Title 50 elements, whose authorities and missions involve the use of commercial data for economic security, financial intelligence, sanctions, supply chain, foreign investment, and related analytic functions. The data platform’s focus is on landing, ingesting, indexing, fusing, and correlating a variety of commercially available information (CAI) and publicly available information (PAI) along with unclassified datasets. The data platform will effectively enable robust end-to-end data management for financial and economic datasets in a unified back-end platform which will enable a “bring/build your own tool” ecosystem of analytics, visualizations, and user-facing tools to discover, access, consume, and analyze data provided by the platform.

(U) The goal of the data platform is to be the USG’s focal point for managing and serving robust, unified data via rich Application Programming Interfaces (APIs).

The data platform will enable Agencies, Departments, Components, and Offices to address multiple missions around maintaining and extending the economic, technology, and competition advantage in support of the U.S. National Security Strategy (NSS).

(U) The purpose of this Market Survey is to seek input and collect information on available solutions from vendors that could support data platform back-end development. It will gather information on existing commercial capabilities, understand industry experience in the mission space, assess solution maturity, refine technical requirements, and inform future acquisition strategies. The Market Survey is designed to identify not only complete platform offerings, but also component-level tools that could be assembled into a modular solution if OESET determines that a best-of-breed approach is preferable to a single-vendor solution.

(U) Scope of Objectives

(U) Based on the scope of technical requirements, contractors must have documented technical experience in end-to-end data fusion development, to include some or all of the following areas:

• (1) large-scale ingest and fusion of commercial and public data for government or national security missions;

• (2) handling sensitive unclassified government data with role/attribute-based access controls and auditability;

• (3) entity resolution and knowledge graph integration at production scale;

• (4) enable domain-specific analytics through external platform integration;

• (5) API-first data delivery in secure federal cloud environments;

• (6) support for User Interface (UI) query and bulk data download.

(U) Contractors should also note past experience supporting missions related to economic security or financial intelligence.

(U) The goals and objectives of the data platform are as follows:

(U) Goal Number 1 - Data Management and Integration: Ingest data from 5- 10 priority commercial, public, and government economic and financial intelligence data sources into an integrated data platform, supported by a unified backend platform. Specific priority datasets will be determined prior to release of a Statement of Work (SOW).

(U) Goal Number 2 - Automated Entity Resolution: Identifies when companies refer to the same entity, despite spelling inconsistencies, eliminating manual reconciliation that consumes significant analyst time.

(U) Goal Number 3 - Bulk Data Access, APIs, and Services: Allows government end users to interact with the data in the manner best suited for their mission context (API, bulk download, User Interface (UI) query, etc.); configurable for alerts, watch listing, and other data presentations.

(U) Schedule Constraints: OESET is anticipating initial deployment in the 2027 to 2028 timeframe.

(U) OCI

• (U) The Government has not identified any actual or potential OCI concerns at this time; however, respondents are encouraged to identify any actual or potential OCI issues that could arise from their participation in this effort or related activities. The Government may further assess OCI considerations as acquisition planning matures and may request additional disclosures, as appropriate, in any future solicitations.

(U) Rough Order of Magnitude (ROM)

• (U) Please provide a Rough Order Magnitude (ROM) to cover the requirement(s) satisfied by your company’s solution, including the cost structure for the solution (e.g. license fees, cost per seat, etc.).

SATISFYING IDENTIFIED REQUIREMENTS

(U) Instructions: To complete the Requirements Matrix below, mark the appropriate box (either “Prime Solution”, “Planned Solution”, “Partner Solution”, “Former Solution”, or “No Solution”) next to each requirement with an “X”. The Requirements Matrix responses will not count against the 15-page Market Survey page limit.

(U) Requirements (U)Prime Solution

(U)Partner Solution

(U)No Solution

(U) Core Minimum Requirements

1. The system shall support scalable ingestion and processing of structured and unstructured data from diverse economic security and financial intelligence sources (e.g., files, streams, and API responses in JSON, XML, YAML, delimited, or flat formats). In doing so, it shall host and execute ETL workflows to extract, validate, clean, and transform ingested data; capture and preserve timestamps and geographic coordinates; manage data changes and versioning; and load results into intermediate storage with appropriate metadata in accordance with IC policies.

2. (U) The system shall provide a unified transformation layer that joins, filters, and enriches data using both SQL style and code-based transformations, while mapping vendor inputs to IC standard ontologies and storing processing metrics (file size, record counts, field population stats, geographic coverage, runtime, errors, and nonconforming records).

3. (U) The system shall provide a cloud based, multimodal data platform that combines a raw data lake, relational databases for structured data, and graph-based databases to store raw, temporary, ETL, and final data in addition to data catalog content, metrics, usage, access, and security logs, while maintaining automated backups.

4. (U) The system shall integrate sensitive, unclassified USG data into the data catalog with policy-compliant access and dissemination controls aligned to user role and mission.

5. (U) The system shall enforce role-based access for different mission users, licensing/seat usage controls, governance features (owners/stewards, quality indicators, lineage, and provenance), and automatic purging of vendor data on subscription expiration.

6. (U) The system shall expose all transformed and stored data via user interface (UI), bulk data download, and API using industry standard interfaces (JSON/XML over REST, gRPC, and efficient binary formats, allowing end users to export data in configurable formats (CSV, JSON, XML, PNG, JPEG, etc.).

7. (U) The system shall support integrated, web-based documentation and management of data holdings metadata, sample records, vendor information, data delivery schedules, data quality reports and metrics, and live technical information about system health, status, and performance.

8. (U) The system shall provide ensemble entity resolution using exact, fuzzy/string, semantic/vector, and graph-structure matching techniques.

9. (U) The system shall host, manage, and execute automated data protection and quality control workflows (masking/unmasking, redaction, anonymization, age off, broken record detection, and U.S. Person handling per EO 12333), retaining audit trails that satisfy IC directives (ICD 203/206, ICPM 50401, etc.).

10. (U) The system shall enforce industry standard identification and access management (IAM) using Login.gov, CAC/PKI, and IC PKI authentication together with Attribute Based and Role Based access controls.

(U) Desired Requirements

11. (U) The system shall have the ability to expand or reduce data storage while maintaining a granular pay for use fee structure.

12. (U) The system shall capture real time, immutable logs for every API call, data workflow, transformation, and enrichment to maintain end to end data lineage and continuously monitor policy compliance.

13. (U) The system shall provide a unified knowledge graph that integrates economic and financial data at scale by linking (not merging) source records into entities and relationships.

14. (U) The system shall provide an integrated data catalog that tags every dataset with full metadata, offering keyword and category search/filtering.

15. (U) The system shall provide integrated capability for indexing, multi-mode searching (e.g. simple, term/keyboard, Boolean, and compound including foreign language search), and filtering on any user-defined fields.

(U) Future Requirements

16. (U) The system shall support the ability to export unclassified data to higher classification systems via approved cross-domain solutions, with full auditing and rollback capability.

17. (U) The system shall provide secure, non-public integration API that allows approved developers to build, deploy, and integrate custom applications, analytics views, AI/LLM, and other “addon’’ components.

18. (U) The system shall provide public integration API to enable compatible, external economic commercial tools to connect to the data platform.

MARKET SURVEY QUESTIONS

1. (U) Is your company’s solution intended to satisfy all requirements (full data platform solution) or a subset of requirements (component in a broader modular solution)?

2. (U) Does your company have an existing solution through an OTA or commercially available solution that meets all requirements or a subset of the market survey requirements?

3. (U) Please describe your approach to ingesting and integrating data from multiple economic security and financial intelligence sources. What methods do you use to capture timestamps, geographic coordinates, and manage data versioning?

4. (U) Please describe your approach to providing access to a data fusion platform and/or disseminating data to mission users across USG organizations.

5. (U) Please describe your pricing model for data storage. Is there an existing ability to expand or reduce storage as needed?

6. (U) Please describe how your solution handles sensitive, unclassified U.S. government data, including policy-compliant access and dissemination controls.

7. (U) Please explain the mechanisms your company offers to manage data holdings and records, quality, performance, and other metadata.

8. (U) Please explain what applicable security and compliance mechanisms your company offers in the context of the data platform’s mission requirements.

9. (U) Are there any other requirements that you envision the data platform needing that are not explicitly defined here?

10. (U) What experience, technical capability, integration maturity, security posture, or delivery attributes should the Government consider in distinguishing among vendors for this type of effort?

11. (U) What specific KPIs or performance metrics would industry recommend for assessing successful implementation and operation of the data platform?

12. (U) What is your FedRAMP status, and can you provide the scope and evidence (e.g., marketplace listing or authorization details)?

13. (U) Please provide any additional comments concerning the feasibility of any aspects of this requirement, including labor and facility qualifications, OCI, contract type and schedule. Please note that the Government welcomes such comments; any response to this question, on its own, will not disqualify any firm from receipt of the RFP.

14. (U) Would your firm like to receive a copy of the RFP?

15. (U) Does your company anticipate a Prime or Subcontractor role for this acquisition?

Please note that every firm that requests a copy of the RFP will receive one, regardless of their role.

16. (U) References (Responses should not exceed one half page in length) Respondents are requested to provide references for efforts of similar scope, complexity, and relevance to the notional data platform requirement. References should demonstrate experience relevant to data platform requirements. For each reference, please provide:

a. Customer/organization name

b. Contract number

c. Period of performance

d. Brief description of the effort and its relevance to the data platform

e. Dollar value, if available

f. Government or customer point of contact

g. Contracting Officer (CO), Contracting Officer’s Representative (COR), or equivalent, if available

SUBMISSION INSTRUCTIONS

1. All responses to this Market Survey are due no later than 5:00 p.m., Eastern Time, on 16 November 2026. This timeline provides 3 weeks to submit responses to the market survey.

2. Responses should be no more than 15-pages (inclusive of all substantive content) and should use a minimum of 12-point font, single line spacing and 1-inch margins on 8.5 by 11-inch paper.

3. Responses to this Market Survey must include the organization(s), technical and administrative points of contact - including names, addresses, phone and fax numbers, and email addresses of all co-authors.

4. All submissions must be electronically submitted to whomever the cognizant CO will be with a PDF document.

5. When submitting a response, please use the subject “OESET Data Platform Market Survey [-Organization Name]”.

6. Any responses submitted through different channels or to a different email address will not be considered.

7. Organizations under a common banner are encouraged to limit to a single response.

8. Classified responses are not required or expected. If a respondent would like to include classified information, please submit an unclassified response as requested with a classified addendum. Contact the above mailbox for classified submission approval and instructions prior to any such submissions. Please indicate the classification level desired. Any classified materials not specifically approved by ODNI prior to submission will not be considered. Classified addendums are subject to the same submission deadline but are further limited to 5-pages in length, 12-point font and single line spacing. Any classified pages submitted will be deducted from the 15-page limit of the overall response.

9. Inquiries to this Market Survey must be submitted to Elias V. (elias.voces@odni.gov) and Raymond B. (raymond.v.banks@odni.gov). Do not send questions with proprietary content. No telephone inquiries will be accepted.

DISCLAIMERS AND IMPORTANT NOTES

This announcement contains all information required to submit a response. No additional forms, kits, or other materials are needed. This is a Market Survey issued solely for information and planning purposes and does not constitute a formal solicitation.

Submission of a response is strictly voluntary and is not required to propose on subsequent ODNI solicitation. No solicitation exists; therefore, do not request a copy of the solicitation.

It is the responsibility of any potential offers/bidders to monitor this site for release of any solicitation or synopsis. ODNI will acknowledge receipt of all submissions but is under no obligation to provide feedback to respondents with respect to any information submitted under this Market Survey.

In accordance with FAR 15.201(e), responses to this notice are not offers and cannot be accepted by the Government to form a binding contract. Respondents are solely responsible for all expenses associated with responding to this Market Survey. ODNI will NOT provide reimbursement for costs incurred in responding to this Market Survey or participating in any subsequent workshop.

It is the respondent's responsibility to ensure that the submitted material has been approved for public release by the information owner. To the maximum extent possible, please submit non-proprietary information. If proprietary information is submitted, it must be appropriately and specifically marked. It is the submitter’s responsibility to clearly define to the Government what is considered proprietary data. Any proprietary data should be clearly labeled as “Proprietary”. The ODNI will not publicly disclose proprietary information obtained as a result of the Market Survey. To the full extent that it is protected pursuant to the Freedom of Information Act and other laws and regulations, information properly identified by the respondent as “Proprietary” will be appropriately controlled.

Submissions may be reviewed by Government personnel and support contractors bound by appropriate non-disclosure agreements. Responses to this Market Survey will not be returned. Intellectual or other privileged or proprietary information contained in responses to this Market Survey will not be distributed outside ODNI or United States Government employees from other Government agencies who are working with ODNI on this Market Survey.

Contracting Office Address:

Office of the Director of National Intelligence Office of Economic Security and Emerging Technologies Washington, District of Columbia 20511 United States

Preaward Survey of Prospective Contractor Accounting System Checklist

MARK “X” IN THE APPROPRIATE COLUMN (Provided explanations for boxes marked “No” or “N/A” in continuation pages.) YES NO N/A

1. IS THE ACCOUNTING SYSTEM IN ACCORDANCE WITH

GENERALLY ACCEPTED ACCOUNTING PRINCIPLES?

2. ACCOUNTING SYSTEM PROVIDES FOR:

a. Proper segregation of direct costs from indirect costs.

b. Identification and accumulation of direct costs by contract.

c. A logical and consistent method for the allocation of indirect costs to intermediate and final cost objectives (A contract is a final cost objective.)

d. Accumulation of costs under a general ledger control.

e. A timekeeping system that identifies employees’ labor by intermediate or final cost objectives.

f. A labor distribution system that charges direct and indirect labor to the appropriate cost objective.

g. Interim (at least monthly) determination of cost charged to a contract through routine posting of books of account.

h. Exclusion from costs charged to government contracts of amounts, which are not allowable in terms of FAR 31, Contract Cost Principles and Procedures, or other contract provisions.

i. Identification of costs by contract line item and by units (as if each unit or line item was a separate contract) if required by the proposed contract.

j. Segregation of preproduction costs from production costs.

3. ACCOUNTING SYSTEMS PROVIDES FINANCIAL

INFORMATION:

a. Required by contract clauses concerning limitation of costs (FAR 52.232-20 and 21) or limitation on payments (FAR 52.216-16).

b. Required to support requests for progress payments.

4. IS THE ACCOUNTING SYSTEM DESIGNED, AND ARE THE

RECORDS MAINTAINED IN SUCH A MANNER THAT ADEQUATE,

RELIABLE DATA ARE DEVELOPED FOR USE IN PRICING

FOLLOW-ON ACQUISITIONS?

5. IS THE ACCOUNTING SYSTEM CURRENTLY IN FULL

OPERATION?

(If not, describe which portions are (1) in operation, (2) set up, but not yet in operation, (3) anticipated, or (4) nonexistent.)

Signature:

Printed Name:

Title:

Date:

PROPERTY MANAGEMENT SYSTEM SURVEY

INSTRUCTIONS: In accordance with FAR 52.245-1, Contractors shall have a system to manage Government property in its possession. Complete the pre-award survey regarding your

Property Management System. If a section or part of section does not apply to your operation, please mark N/A and provide explanation in comments section.

A. Property Management Yes No N/A

Does your company have a system to manage government property? (COTS Software, Homegrown Software, Excel)

Does your company have written property management plans and procedures?

Have your property management procedures been previously reviewed by this or another Government Agency?

4 Do you maintain supporting documentation (Invoice/PO/Receiving) for all Government Property?

5 Are items properly received and inspected against your purchase order and shipping documents?

6 Are property asset tags attached to all GFP/CAP upon receipt?

7 Do your records include all FAR data elements? (Acquisition Cost & Date Received/Placed in Service)

8 Are physical inventories performed cyclically or as required?

9 Do you have Sub-Contractors with Government Property?

10 Are the Government Property Contract Clause Requirements flowed down to the sub-contractors?

11 Do you conduct property reviews on your sub-contractors?

12 Do you have a process for reporting Loss, Damage, Destroy, Theft of Government Property?

13 Do you maintain records for material (consumables) not currently issued for consumption?

14 Does your property system capture location of assets?

15 Do you have a process for tracking movement?

16 Is preventative maintenance/calibration accomplished as required?

17 Do you have a process to identify and report excess, residual assets throughout the contract?

Comments:

Contractor's Certification: If awarded a contract having Government property, I am willing to work with the Government Property Administrator to ensure my company’s Property Management System and practices meet all FAR and contract requirements.

Print Name: _______________________________________

Signature: _________________________________________ Date: _______________

Contractor Name:

Address:

Contractor Property Representative Name:

Phone No.:

Unclassified Fax No:

Classified Fax No:

E-mail Address (secure preferred):

OESET – Data Platform Market Survey