FPDS Query Library
About Us
Contact Us

PIID

A unique procurement identifier assigned to the Other Transaction IDV contract record. It functions as the primary key-like contract reference used to distinguish this agreement from other awards and modifications within FPDS.

Family: Other Transaction IDV
Category: General
Data Type: identifier_or_code
Semantic Type: identifier
Mapping: flattened_fpds_xml_field
AI Confidence: high

Variable Overview

FPDS Query Variable
content__OtherTransactionIDV__OtherTransactionIDVID__OtherTransactionIDVContractID__PIID
Title
PIID
FPDS Path
OtherTransactionIDV/OtherTransactionIDVID/OtherTransactionIDVContractID/PIID
Description
A unique procurement identifier assigned to the Other Transaction IDV contract record. It functions as the primary key-like contract reference used to distinguish this agreement from other awards and modifications within FPDS.
Business Meaning
This field is essential for identifying and tracking a specific Other Transaction IDV across reporting cycles, obligations, and related transactions. Analysts use it to consolidate award activity, link child actions to the parent instrument, and avoid double counting when reviewing portfolio, vendor, or agency performance.
Example Value
W912HZ249C001
Observed Non-Null Count
13,417

FPDS Compare

FPDS Query Variable
content__OtherTransactionIDV__OtherTransactionIDVID__OtherTransactionIDVContractID__PIID
FPDS XML Path
OtherTransactionIDV/OtherTransactionIDVID/OtherTransactionIDVContractID/PIID
Mapping Type
flattened_fpds_xml_field
Comparison Summary
FPDS Query flattens the original nested FPDS XML path 'OtherTransactionIDV/OtherTransactionIDVID/OtherTransactionIDVContractID/PIID' into the SQL-ready variable 'content__OtherTransactionIDV__OtherTransactionIDVID__OtherTransactionIDVContractID__PIID'.

Use Cases

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

Common Usage

  • Joining award-level and modification-level records
  • Deduplicating contract actions within an IDV
  • Filtering or grouping by specific contract vehicle

Common Mistakes

  • Using it as a sortable business metric or descriptive label
  • Trimming or normalizing the value in ways that break joins

Query Guidance

Use exact equality or IN predicates on the full PIID value, and join on the complete identifier when linking FPDS tables or deduplicating records. In SQL, avoid substring logic unless you are deliberately parsing a known agency-specific format; retain the raw stored value for reconciliation.

SQL Examples

Preview values

SELECT
    content__OtherTransactionIDV__OtherTransactionIDVID__OtherTransactionIDVContractID__PIID AS p_i_i_d
FROM fpds.data
WHERE content__OtherTransactionIDV__OtherTransactionIDVID__OtherTransactionIDVContractID__PIID IS NOT NULL
LIMIT 25

Top values

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