FPDS Query Library
About Us
Contact Us

Is Physically Complete

Boolean or coded flag indicating whether the IDV has been physically completed. In NASA-specific FPDS data, 0 represents false and 1 represents true, so the field captures completion status rather than a narrative description.

Family: IDV
Category: NASA Specific Fields
Data Type: boolean_or_code_flag
Semantic Type: flag
Mapping: flattened_fpds_xml_field
AI Confidence: high

Variable Overview

FPDS Query Variable
content__IDV__agencySpecificIDVElements__NASASpecificIDVElements__isPhysicallyComplete
Title
Is Physically Complete
FPDS Path
IDV/agencySpecificIDVElements/NASASpecificIDVElements/isPhysicallyComplete
Description
Boolean or coded flag indicating whether the IDV has been physically completed. In NASA-specific FPDS data, 0 represents false and 1 represents true, so the field captures completion status rather than a narrative description.
Business Meaning
This field helps analysts distinguish active awards from instruments that have reached physical completion, which is important for lifecycle reporting, workload analysis, and compliance checks. It is useful when assessing whether obligations or actions should still be considered current for contract administration, spend tracking, or closeout-related reviews.
Example Value
0
Observed Non-Null Count
57,988

FPDS Compare

FPDS Query Variable
content__IDV__agencySpecificIDVElements__NASASpecificIDVElements__isPhysicallyComplete
FPDS XML Path
IDV/agencySpecificIDVElements/NASASpecificIDVElements/isPhysicallyComplete
Mapping Type
flattened_fpds_xml_field
Comparison Summary
FPDS Query flattens the original nested FPDS XML path 'IDV/agencySpecificIDVElements/NASASpecificIDVElements/isPhysicallyComplete' into the SQL-ready variable 'content__IDV__agencySpecificIDVElements__NASASpecificIDVElements__isPhysicallyComplete'.

Use Cases

  • Dictionary lookup and field explanation
  • SQL filtering and grouping
  • Analytical reporting and reusable query building
  • NASA-specific IDV record interpretation

Common Usage

  • Filter IDVs that are physically complete
  • Segment active versus completed instruments
  • Support closeout and lifecycle analyses

Common Mistakes

  • Assuming 1 means financially complete rather than physically complete
  • Ignoring null, missing, or nonstandard coded values

Query Guidance

Use explicit comparisons against the code values, such as `WHERE content__IDV__agencySpecificIDVElements__NASASpecificIDVElements__isPhysicallyComplete = 1` for completed records or `= 0` for not completed records. When building aggregates, coalesce or separately count nulls so incomplete data is not mistaken for false.

SQL Examples

Preview values

SELECT
    content__IDV__agencySpecificIDVElements__NASASpecificIDVElements__isPhysicallyComplete AS is_physically_complete
FROM fpds.data
WHERE content__IDV__agencySpecificIDVElements__NASASpecificIDVElements__isPhysicallyComplete IS NOT NULL
LIMIT 25

Flag distribution

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