Multi Year Contract

Boolean or coded indicator showing whether the IDV is structured as a multi-year contract. In FPDS, the value N means the record is not a multi-year contract; other observed values should be treated according to the source code set.

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__multiYearContract
Title
Multi Year Contract
FPDS Path
IDV/contractData/multiYearContract
Description
Boolean or coded indicator showing whether the IDV is structured as a multi-year contract. In FPDS, the value N means the record is not a multi-year contract; other observed values should be treated according to the source code set.
Business Meaning
This field helps analysts identify obligations and award structures that span multiple fiscal years, which can affect budgeting, funding availability, competition analysis, and contract strategy reviews. It is useful for separating long-term commitments from standard single-year awards when assessing acquisition patterns or compliance with multi-year contracting rules.
Example Value
N
Observed Non-Null Count
4,355,975

FPDS Compare

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

Use Cases

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

Common Usage

  • Filter IDVs that are multi-year contracts
  • Segment obligations by contract structure for trend analysis
  • Review awards for compliance or strategy analysis involving multi-year contracting

Common Mistakes

  • Using it as a proxy for contract period length or performance duration
  • Assuming missing or non-N values always mean true without checking the source code set

Query Guidance

In SQL, filter explicitly on the coded value rather than on a textual interpretation, for example WHERE multiYearContract = 'Y' or WHERE multiYearContract <> 'N' only if the code set is verified. If the field is nullable or inconsistently populated, combine the flag check with data-quality handling such as COALESCE and validate against companion descriptive fields or reference data.

SQL Examples

Preview values

SELECT
    content__IDV__contractData__multiYearContract AS multi_year_contract
FROM fpds.data
WHERE content__IDV__contractData__multiYearContract IS NOT NULL
LIMIT 25

Flag distribution

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