FPDS Query Library
About Us
Contact Us

Department Id

Code that identifies the department associated with the contracting office for this IDV record. It is an internal FPDS organizational identifier, not a descriptive agency 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__contractingOfficeAgencyID__departmentID
Title
Department Id
FPDS Path
IDV/purchaserInformation/contractingOfficeAgencyID/departmentID
Description
Code that identifies the department associated with the contracting office for this IDV record. It is an internal FPDS organizational identifier, not a descriptive agency name.
Business Meaning
This field helps analysts group obligations and award activity by department-level buyer organization, supporting spending rollups, organizational comparisons, and oversight of procurement activity across federal departments.
Example Value
4700
Observed Non-Null Count
5,856,017

FPDS Compare

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

Use Cases

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

Common Usage

  • department-level spend aggregation
  • agency or bureau attribution
  • filtering awards by buying organization

Common Mistakes

  • using the code as if it were the department name
  • joining on this field without confirming the correct reference table or code format

Query Guidance

Use this field for grouping, filtering, or joining to an organizational lookup table. In SQL, compare it as a string unless the source explicitly documents it as numeric, and include the paired agency/office fields when validating organizational hierarchy.

SQL Examples

Preview values

SELECT
    content__IDV__purchaserInformation__contractingOfficeAgencyID__departmentID AS department_id
FROM fpds.data
WHERE content__IDV__purchaserInformation__contractingOfficeAgencyID__departmentID IS NOT NULL
LIMIT 25

Top values

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