FPDS Query Library
About Us
Contact Us

Extent Competed

Human-readable extent-of-competition value recorded for an Other Transaction Award contract detail. It indicates how the requirement was competed or whether it was effectively noncompetitive, as captured in the FPDS record.

Family: Other Transaction Award
Category: Competition
Data Type: string
Semantic Type: attribute
Mapping: flattened_fpds_xml_field
AI Confidence: high

Variable Overview

FPDS Query Variable
content__OtherTransactionAward__contractDetail__competition__extentCompeted
Title
Extent Competed
FPDS Path
OtherTransactionAward/contractDetail/competition/extentCompeted
Description
Human-readable extent-of-competition value recorded for an Other Transaction Award contract detail. It indicates how the requirement was competed or whether it was effectively noncompetitive, as captured in the FPDS record.
Business Meaning
This field supports competition analysis by showing the competition treatment reported for an award, which is important for assessing acquisition strategy, source selection patterns, and potential noncompetitive use. It helps analysts distinguish competed awards from limited- or noncompetitive actions when reviewing award portfolios.
Example Value
H
Observed Non-Null Count
38,894

FPDS Compare

FPDS Query Variable
content__OtherTransactionAward__contractDetail__competition__extentCompeted
FPDS XML Path
OtherTransactionAward/contractDetail/competition/extentCompeted
Mapping Type
flattened_fpds_xml_field
Comparison Summary
FPDS Query flattens the original nested FPDS XML path 'OtherTransactionAward/contractDetail/competition/extentCompeted' into the SQL-ready variable 'content__OtherTransactionAward__contractDetail__competition__extentCompeted'.

Use Cases

  • Dictionary lookup and field explanation
  • SQL filtering and grouping
  • Analytical reporting and reusable query building
  • Competition and sole-source analysis

Common Usage

  • Classifying awards by competition status
  • Identifying noncompetitive or limited-competition transactions
  • Segmenting award volumes and obligations by competition category

Common Mistakes

  • Assuming the value is a full narrative explanation rather than a coded label
  • Aggregating without first normalizing codes and descriptions

Query Guidance

Use this field in GROUP BY, DISTINCT, or CASE logic to bucket competition categories after normalizing code values and descriptions. In SQL, compare against the actual stored string values observed in the data rather than assuming the example value represents the full code set.

SQL Examples

Preview values

SELECT
    content__OtherTransactionAward__contractDetail__competition__extentCompeted AS extent_competed
FROM fpds.data
WHERE content__OtherTransactionAward__contractDetail__competition__extentCompeted IS NOT NULL
LIMIT 25

Top values

SELECT
    content__OtherTransactionAward__contractDetail__competition__extentCompeted AS value,
    count() AS record_count
FROM fpds.data
WHERE content__OtherTransactionAward__contractDetail__competition__extentCompeted IS NOT NULL
GROUP BY value
ORDER BY record_count DESC
LIMIT 25

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