FPDS Query Library
About Us
Contact Us

Contracting Officer Code

A NASA-specific identifier that stores the contracting officer code associated with an IDV record. It is a coded value used to identify the official responsible for the instrument rather than a narrative description.

Family: IDV
Category: NASA Specific Fields
Data Type: identifier_or_code
Semantic Type: identifier
Mapping: flattened_fpds_xml_field
AI Confidence: high

Variable Overview

FPDS Query Variable
content__IDV__agencySpecificIDVElements__NASASpecificIDVElements__contractingOfficerCode
Title
Contracting Officer Code
FPDS Path
IDV/agencySpecificIDVElements/NASASpecificIDVElements/contractingOfficerCode
Description
A NASA-specific identifier that stores the contracting officer code associated with an IDV record. It is a coded value used to identify the official responsible for the instrument rather than a narrative description.
Business Meaning
This field helps analysts attribute IDVs to the responsible contracting officer for workload, accountability, and internal NASA management reporting. It is useful for reviewing award activity by officer, office, or organization and for tracing administrative ownership of a vehicle.
Example Value
jKA
Observed Non-Null Count
57,747

FPDS Compare

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

Use Cases

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

Common Usage

  • Linking IDVs to a contracting officer roster or internal personnel file
  • Grouping awards by officer for workload or portfolio analysis
  • Filtering NASA records for administrative review or oversight

Common Mistakes

  • Assuming the code is a universal federal identifier instead of a NASA-specific code
  • Using the value as a person name without a lookup to the corresponding description or reference table

Query Guidance

Use exact equality or IN filters for the code, and join to a NASA lookup table if you need the officer name or role. If codes are inconsistently formatted, normalize trimming and case first, and do not aggregate this field as a numeric measure.

SQL Examples

Preview values

SELECT
    content__IDV__agencySpecificIDVElements__NASASpecificIDVElements__contractingOfficerCode AS contracting_officer_code
FROM fpds.data
WHERE content__IDV__agencySpecificIDVElements__NASASpecificIDVElements__contractingOfficerCode IS NOT NULL
LIMIT 25

Top values

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