FPDS Query Library
About Us
Contact Us

Inherently Governmental Function

Boolean or coded flag indicating whether the IDV includes inherently governmental functions. It identifies records where the acquisition touches work that, by law or policy, must remain under government control or direction. The example value "CT" suggests the field may store coded values rather than a simple true/false, so the observed code set should be verified in the data.

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

Variable Overview

FPDS Query Variable
content__IDV__contractData__inherentlyGovernmentalFunction
Title
Inherently Governmental Function
FPDS Path
IDV/contractData/inherentlyGovernmentalFunction
Description
Boolean or coded flag indicating whether the IDV includes inherently governmental functions. It identifies records where the acquisition touches work that, by law or policy, must remain under government control or direction. The example value "CT" suggests the field may store coded values rather than a simple true/false, so the observed code set should be verified in the data.
Business Meaning
This field supports oversight of contracts and IDVs that raise sourcing, compliance, and risk concerns because inherently governmental work is restricted from contractor performance. Analysts use it to segment awards for policy review, identify potential acquisition control issues, and monitor portfolios involving sensitive functions.
Example Value
CT
Observed Non-Null Count
1,312,171

FPDS Compare

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

Use Cases

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

Common Usage

  • Filter IDVs that involve inherently governmental functions
  • Support compliance and policy review analyses
  • Segment awards for risk or oversight reporting

Common Mistakes

  • Assuming every non-null value means a simple true value
  • Using the field as a proxy for contract sensitivity or dollar value

Query Guidance

When querying, first confirm the valid code-to-meaning mapping from the FPDS extract or associated description field. In SQL, filter on the confirmed affirmative code(s) rather than on string presence alone, and use DISTINCT or CASE logic to inspect observed values before building reporting logic.

SQL Examples

Preview values

SELECT
    content__IDV__contractData__inherentlyGovernmentalFunction AS inherently_governmental_function
FROM fpds.data
WHERE content__IDV__contractData__inherentlyGovernmentalFunction IS NOT NULL
LIMIT 25

Flag distribution

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