Consolidated Contract

Indicates whether the IDV record represents a consolidated contract. It is a boolean or coded flag stored at IDV/contractData/consolidatedContract and may appear as a short code such as N rather than a fully descriptive text value.

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__consolidatedContract
Title
Consolidated Contract
FPDS Path
IDV/contractData/consolidatedContract
Description
Indicates whether the IDV record represents a consolidated contract. It is a boolean or coded flag stored at IDV/contractData/consolidatedContract and may appear as a short code such as N rather than a fully descriptive text value.
Business Meaning
This field helps analysts identify contract arrangements that combine requirements into a single vehicle, which can affect competition, scope, award structure, and spend concentration analysis. It is useful for segmentation of IDVs when assessing procurement strategy, compliance patterns, and potential bundling or consolidation effects.
Example Value
N
Observed Non-Null Count
5,329,737

FPDS Compare

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

Use Cases

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

Common Usage

  • Segment IDVs by consolidated versus non-consolidated awards
  • Support bundling, aggregation, or vehicle-structure analysis
  • Filter records for compliance or procurement strategy reviews

Common Mistakes

  • Assuming the field is always a plain boolean instead of a coded flag
  • Using the value without checking the valid code set or source-system conventions

Query Guidance

Use explicit comparisons against the known flag values in WHERE clauses, and standardize the field to a binary indicator if needed for analysis. When joining or grouping, preserve the raw value so coded variants can be audited before aggregation.

SQL Examples

Preview values

SELECT
    content__IDV__contractData__consolidatedContract AS consolidated_contract
FROM fpds.data
WHERE content__IDV__contractData__consolidatedContract IS NOT NULL
LIMIT 25

Flag distribution

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