FPDS Query Library
About Us
Contact Us

IDV Number of Offers Received

Stores the reported number of offers received for the IDV solicitation. Although the field is typed as a string, it represents a count-like value and may include coded or exceptional entries such as 999 rather than a simple numeric count.

Family: IDV
Category: Competition
Data Type: string
Semantic Type: attribute
Mapping: flattened_fpds_xml_field
AI Confidence: high

Variable Overview

FPDS Query Variable
content__IDV__competition__idvNumberOfOffersReceived
Title
IDV Number of Offers Received
FPDS Path
IDV/competition/idvNumberOfOffersReceived
Description
Stores the reported number of offers received for the IDV solicitation. Although the field is typed as a string, it represents a count-like value and may include coded or exceptional entries such as 999 rather than a simple numeric count.
Business Meaning
This field helps analysts assess competition at the IDV level by indicating how many offers were received when the solicitation was competed. It is useful for comparing sourcing intensity, identifying potentially limited competition, and evaluating whether award outcomes align with the level of market response.
Example Value
999
Observed Non-Null Count
62,142

FPDS Compare

FPDS Query Variable
content__IDV__competition__idvNumberOfOffersReceived
FPDS XML Path
IDV/competition/idvNumberOfOffersReceived
Mapping Type
flattened_fpds_xml_field
Comparison Summary
FPDS Query flattens the original nested FPDS XML path 'IDV/competition/idvNumberOfOffersReceived' into the SQL-ready variable 'content__IDV__competition__idvNumberOfOffersReceived'.

Use Cases

  • Dictionary lookup and field explanation
  • SQL filtering and grouping
  • Analytical reporting and reusable query building
  • Competition and sole-source analysis

Common Usage

  • Measure the volume of responses to an IDV solicitation
  • Compare competition levels across agencies, products, or periods
  • Flag records with unusually low or coded offer counts

Common Mistakes

  • Casting every value directly to numeric without checking for codes like 999
  • Using this field alone to infer competitive status without validating related competition fields

Query Guidance

Use as a text field first, then normalize to numeric only after identifying special codes and nonnumeric values. In SQL, filter or case-map known placeholder values before aggregation, and combine with competition indicators to avoid misclassification.

SQL Examples

Preview values

SELECT
    content__IDV__competition__idvNumberOfOffersReceived AS i_d_v_number_of_offers_received
FROM fpds.data
WHERE content__IDV__competition__idvNumberOfOffersReceived IS NOT NULL
LIMIT 25

Top values

SELECT
    content__IDV__competition__idvNumberOfOffersReceived AS value,
    count() AS record_count
FROM fpds.data
WHERE content__IDV__competition__idvNumberOfOffersReceived IS NOT NULL
GROUP BY value
ORDER BY record_count DESC
LIMIT 25

Each dictionary item includes SQL-ready examples generated alongside the variable metadata, allowing immediate use in FPDS Query for filtering, aggregation, and analysis.