FPDS Query Library
About Us
Contact Us

Vendor Alternate Site Code

Alternate site code that identifies a specific vendor location recorded for the IDV vendor profile. It is an identifier/code value rather than a descriptive name, and it may represent an internal or standardized location key used to distinguish one vendor site from another.

Family: IDV
Category: Vendor Site Details
Data Type: identifier_or_code
Semantic Type: identifier
Mapping: flattened_fpds_xml_field
AI Confidence: high

Variable Overview

FPDS Query Variable
content__IDV__vendor__vendorSiteDetails__vendorAlternateSiteCode
Title
Vendor Alternate Site Code
FPDS Path
IDV/vendor/vendorSiteDetails/vendorAlternateSiteCode
Description
Alternate site code that identifies a specific vendor location recorded for the IDV vendor profile. It is an identifier/code value rather than a descriptive name, and it may represent an internal or standardized location key used to distinguish one vendor site from another.
Business Meaning
This field helps analysts distinguish awards tied to different vendor locations, which is important when assessing geographic concentration, site-level performance, or matching vendor records across FPDS and external reference data. It can also support analyses of routing, administration, and vendor footprint when the same vendor has multiple operating sites.
Example Value
532010423
Observed Non-Null Count
3,706,482

FPDS Compare

FPDS Query Variable
content__IDV__vendor__vendorSiteDetails__vendorAlternateSiteCode
FPDS XML Path
IDV/vendor/vendorSiteDetails/vendorAlternateSiteCode
Mapping Type
flattened_fpds_xml_field
Comparison Summary
FPDS Query flattens the original nested FPDS XML path 'IDV/vendor/vendorSiteDetails/vendorAlternateSiteCode' into the SQL-ready variable 'content__IDV__vendor__vendorSiteDetails__vendorAlternateSiteCode'.

Use Cases

  • Dictionary lookup and field explanation
  • SQL filtering and grouping
  • Analytical reporting and reusable query building
  • Contractor profiling and competitor analysis

Common Usage

  • Grouping obligations by vendor site
  • Linking FPDS records to vendor master or location reference tables
  • Filtering awards associated with a specific alternate site

Common Mistakes

  • Interpreting the code as a ZIP code or street address
  • Using it as a standalone geography field without a lookup table

Query Guidance

Use equality filters or joins against reference tables when the code is known. In SQL, treat it as an exact-match string field, preserve leading zeros if present, and pair it with vendor name or site-description fields when validating distinct locations.

SQL Examples

Preview values

SELECT
    content__IDV__vendor__vendorSiteDetails__vendorAlternateSiteCode AS vendor_alternate_site_code
FROM fpds.data
WHERE content__IDV__vendor__vendorSiteDetails__vendorAlternateSiteCode IS NOT NULL
LIMIT 25

Top values

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