FPDS Query Library
About Us
Contact Us

Ordering Procedure

Boolean or coded flag indicating whether the IDV includes information about the procedure used to place orders under the contract. In FPDS, this is a contract marketing attribute tied to order placement mechanics rather than a narrative description of the acquisition.

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

Variable Overview

FPDS Query Variable
content__IDV__contractMarketingData__orderingProcedure
Title
Ordering Procedure
FPDS Path
IDV/contractMarketingData/orderingProcedure
Description
Boolean or coded flag indicating whether the IDV includes information about the procedure used to place orders under the contract. In FPDS, this is a contract marketing attribute tied to order placement mechanics rather than a narrative description of the acquisition.
Business Meaning
This field helps analysts identify how orders can be issued against an IDV, which affects competition structure, ordering flexibility, and compliance review for task and delivery order acquisitions. It is useful when comparing vehicles, assessing ordering authority, and segmenting contract types by ordering method.
Example Value
Migrated Data Value Unknown
Observed Non-Null Count
454,459

FPDS Compare

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

Use Cases

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

Common Usage

  • Filter IDVs that support a specific ordering approach
  • Segment contract vehicles by ordering mechanism
  • Support compliance and market structure analysis for task and delivery orders

Common Mistakes

  • Interpreting the field as the actual order procedure text rather than an indicator of its presence or type
  • Using migrated or unknown values as evidence that no ordering procedure exists

Query Guidance

Use this field as a boolean/coded filter in WHERE clauses, and join or inspect related description fields when the value is coded, abbreviated, or migrated. For aggregation, group by the normalized flag value rather than raw text, and exclude unknown or migrated records if the analysis requires confirmed ordering procedure data.

SQL Examples

Preview values

SELECT
    content__IDV__contractMarketingData__orderingProcedure AS ordering_procedure
FROM fpds.data
WHERE content__IDV__contractMarketingData__orderingProcedure IS NOT NULL
LIMIT 25

Flag distribution

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