FPDS Query Library
About Us
Contact Us

Contracting Office Id

Code identifying the contracting office associated with the IDV record. It is an internal FPDS reference used to designate the office responsible for the instrument rather than a free-text office name.

Family: IDV
Category: Purchaser Information
Data Type: identifier_or_code
Semantic Type: identifier
Mapping: flattened_fpds_xml_field
AI Confidence: high

Variable Overview

FPDS Query Variable
content__IDV__purchaserInformation__contractingOfficeID
Title
Contracting Office Id
FPDS Path
IDV/purchaserInformation/contractingOfficeID
Description
Code identifying the contracting office associated with the IDV record. It is an internal FPDS reference used to designate the office responsible for the instrument rather than a free-text office name.
Business Meaning
This field lets analysts attribute IDVs to the contracting office that executed or manages the award, which is essential for workload, spend, and portfolio analysis by office. It also supports rollups, trend comparisons, and identification of concentration across agencies or organizational units.
Example Value
HDEC01
Observed Non-Null Count
4,511,476

FPDS Compare

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

Use Cases

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

Common Usage

  • grouping IDVs by contracting office
  • filtering awards for a specific office code
  • joining to office reference or organizational lookup tables

Common Mistakes

  • assuming the code is a human-readable office name
  • using the field without accounting for code changes or missing reference mappings

Query Guidance

Use equality filters or GROUP BY on this field when analyzing office-level activity, and join to a lookup table if you need readable office names. In SQL, normalize case and handle blanks/nulls explicitly, since coded identifiers may appear inconsistently across feeds.

SQL Examples

Preview values

SELECT
    content__IDV__purchaserInformation__contractingOfficeID AS contracting_office_id
FROM fpds.data
WHERE content__IDV__purchaserInformation__contractingOfficeID IS NOT NULL
LIMIT 25

Top values

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