FPDS Query Library
About Us
Contact Us

Performance Based Service Contract

Boolean or coded indicator showing whether the IDV is classified as a performance-based service contract. In FPDS, this field records the presence of that condition rather than a narrative description of the contract.

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__performanceBasedServiceContract
Title
Performance Based Service Contract
FPDS Path
IDV/contractData/performanceBasedServiceContract
Description
Boolean or coded indicator showing whether the IDV is classified as a performance-based service contract. In FPDS, this field records the presence of that condition rather than a narrative description of the contract.
Business Meaning
This field supports analysis of service acquisition practices, compliance with performance-based contracting policy, and segmentation of award portfolios by contract management approach. It is useful for identifying how often agencies use performance-based structures and for comparing obligations, vendors, or categories where outcomes-based requirements are expected.
Example Value
X
Observed Non-Null Count
5,859,746

FPDS Compare

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

Use Cases

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

Common Usage

  • Filter IDVs that are performance-based service contracts
  • Calculate the share of service awards marked performance-based by agency or fiscal year
  • Compare obligations and award counts across performance-based versus non-performance-based contracts

Common Mistakes

  • Assuming a blank or null value always means 'No'
  • Treating the flag as a full description of contract performance requirements

Query Guidance

In SQL, test for the populated code rather than the literal wording, for example `WHERE performanceBasedServiceContract = 'X'` or equivalent logic based on the extract. When building metrics, explicitly handle nulls separately from affirmative values so missing data is not counted as a negative response.

SQL Examples

Preview values

SELECT
    content__IDV__contractData__performanceBasedServiceContract AS performance_based_service_contract
FROM fpds.data
WHERE content__IDV__contractData__performanceBasedServiceContract IS NOT NULL
LIMIT 25

Flag distribution

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