FPDS Query Library
About Us
Contact Us

Fed Biz Opps

Boolean or coded flag indicating whether the IDV record was posted in Federal Business Opportunities (FedBizOpps). In FPDS, this is a condition indicator stored at IDV/competition/fedBizOpps, and the observed value may appear as an abbreviated code such as "X" rather than a plain-language yes/no.

Family: IDV
Category: Competition
Data Type: boolean_or_code_flag
Semantic Type: flag
Mapping: flattened_fpds_xml_field
AI Confidence: high

Variable Overview

FPDS Query Variable
content__IDV__competition__fedBizOpps
Title
Fed Biz Opps
FPDS Path
IDV/competition/fedBizOpps
Description
Boolean or coded flag indicating whether the IDV record was posted in Federal Business Opportunities (FedBizOpps). In FPDS, this is a condition indicator stored at IDV/competition/fedBizOpps, and the observed value may appear as an abbreviated code such as "X" rather than a plain-language yes/no.
Business Meaning
This field helps analysts identify which pre-award opportunities were publicly posted in the legacy FedBizOpps system, supporting transparency, competition, and process compliance analysis. It is useful for segmenting obligations and awards by posting channel, especially when studying public notice practices or comparing competition patterns across acquisition methods.
Example Value
X
Observed Non-Null Count
5,644,298

FPDS Compare

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

Use Cases

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

Common Usage

  • Filter IDVs that were posted through FedBizOpps
  • Compare competition patterns for posted versus non-posted actions
  • Support compliance or transparency review of solicitation posting practices

Common Mistakes

  • Assuming the field is always a simple boolean instead of a coded flag
  • Treating null, blank, and non-"X" values as equivalent without validating the source code set

Query Guidance

Use this field as a filter on the specific coded value present in your extract, commonly `= 'X'` for posted records. In SQL, confirm whether the source stores yes/no as `X`, `Y/N`, or another code, and use `IS NOT NULL` only if you intend to capture any populated indicator rather than the affirmative condition specifically.

SQL Examples

Preview values

SELECT
    content__IDV__competition__fedBizOpps AS fed_biz_opps
FROM fpds.data
WHERE content__IDV__competition__fedBizOpps IS NOT NULL
LIMIT 25

Flag distribution

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