FPDS Query Library
About Us
Contact Us

Referenced IDV Multiple or Single

Boolean or coded flag indicating whether the referenced IDV is a multiple-award or single-award vehicle. In FPDS this field classifies the award structure of the IDV tied to the record; the example value "M" suggests a coded value rather than a plain yes/no indicator.

Family: IDV
Category: Contract Data
Data Type: boolean_or_code_flag
Semantic Type: flag
Mapping: flattened_fpds_xml_field
AI Confidence: high

Variable Overview

FPDS Query Variable
content__IDV__contractData__referencedIDVMultipleOrSingle
Title
Referenced IDV Multiple or Single
FPDS Path
IDV/contractData/referencedIDVMultipleOrSingle
Description
Boolean or coded flag indicating whether the referenced IDV is a multiple-award or single-award vehicle. In FPDS this field classifies the award structure of the IDV tied to the record; the example value "M" suggests a coded value rather than a plain yes/no indicator.
Business Meaning
This field is important for separating contract vehicles by award type, which affects competition analysis, obligation concentration, vendor access, and task/order issuance patterns. Analysts use it to compare multiple-award frameworks against single-award vehicles when assessing market structure, vehicle utilization, and compliance with acquisition strategy.
Example Value
M
Observed Non-Null Count
133,045

FPDS Compare

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

Use Cases

  • Dictionary lookup and field explanation
  • SQL filtering and grouping
  • Analytical reporting and reusable query building

Common Usage

  • Segment IDVs into multiple-award versus single-award populations
  • Filter records for competition or vehicle-structure analysis
  • Join to obligation, vendor, or order data to compare award patterns by vehicle type

Common Mistakes

  • Assuming the field is always a simple true/false boolean
  • Interpreting coded values without confirming the dataset's value map

Query Guidance

Use this field in WHERE clauses to isolate the vehicle structure you need, but first confirm the actual code set in your data source. If a description or lookup field exists, join or decode on the code value and standardize M/S/other variants before aggregating.

SQL Examples

Preview values

SELECT
    content__IDV__contractData__referencedIDVMultipleOrSingle AS referenced_i_d_v_multiple_or_single
FROM fpds.data
WHERE content__IDV__contractData__referencedIDVMultipleOrSingle IS NOT NULL
LIMIT 25

Flag distribution

SELECT
    content__IDV__contractData__referencedIDVMultipleOrSingle AS flag_value,
    count() AS record_count
FROM fpds.data
WHERE content__IDV__contractData__referencedIDVMultipleOrSingle IS NOT NULL
GROUP BY flag_value
ORDER BY record_count DESC

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