Contract Bundling

Indicates whether the IDV is a bundled requirement, meaning multiple requirements or products/services were combined into one procurement action. The field appears to be a coded flag rather than a free-text description, so observed values should be interpreted using the valid code set and any paired description fields if present.

Family: IDV
Category: Product Or Service Information
Data Type: boolean_or_code_flag
Semantic Type: flag
Mapping: flattened_fpds_xml_field
AI Confidence: high

Variable Overview

FPDS Query Variable
content__IDV__productOrServiceInformation__contractBundling
Title
Contract Bundling
FPDS Path
IDV/productOrServiceInformation/contractBundling
Description
Indicates whether the IDV is a bundled requirement, meaning multiple requirements or products/services were combined into one procurement action. The field appears to be a coded flag rather than a free-text description, so observed values should be interpreted using the valid code set and any paired description fields if present.
Business Meaning
Bundling can affect competition, small business participation, and acquisition strategy, so this field is important for compliance review and market structure analysis. Analysts use it to identify acquisitions that may consolidate demand and to study the impact of bundling on award outcomes and vendor concentration.
Example Value
D
Observed Non-Null Count
4,411,263

FPDS Compare

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

Use Cases

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

Common Usage

  • Filter IDVs that are marked as bundled
  • Measure bundling frequency by agency, PSC, or NAICS
  • Support small business and competition compliance analysis

Common Mistakes

  • Assuming any non-null value means true without checking the code meaning
  • Comparing the field as a numeric or free-text value instead of a coded flag

Query Guidance

Use explicit code-based predicates, for example `WHERE contractBundling = 'D'` only if the FPDS code set confirms that 'D' represents bundled; otherwise join to the reference description or normalize the code values first. If the dataset includes multiple representations of the same concept, standardize them in a CASE expression before aggregating.

SQL Examples

Preview values

SELECT
    content__IDV__productOrServiceInformation__contractBundling AS contract_bundling
FROM fpds.data
WHERE content__IDV__productOrServiceInformation__contractBundling IS NOT NULL
LIMIT 25

Flag distribution

SELECT
    content__IDV__productOrServiceInformation__contractBundling AS flag_value,
    count() AS record_count
FROM fpds.data
WHERE content__IDV__productOrServiceInformation__contractBundling 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.