FPDS Query Library
About Us
Contact Us

Fee Paid for Use of Service

Numeric amount showing the fee paid for use of the service under the award's contract marketing data. It represents the recorded payment amount associated with service usage, and in FPDS it is stored as an attribute value rather than a text description.

Family: Award
Category: Contract Marketing
Data Type: numeric
Semantic Type: attribute
Mapping: flattened_fpds_xml_field
AI Confidence: high

Variable Overview

FPDS Query Variable
content__award__contractMarketingData__feePaidForUseOfService
Title
Fee Paid for Use of Service
FPDS Path
award/contractMarketingData/feePaidForUseOfService
Description
Numeric amount showing the fee paid for use of the service under the award's contract marketing data. It represents the recorded payment amount associated with service usage, and in FPDS it is stored as an attribute value rather than a text description.
Business Meaning
This field helps analysts identify and compare service-use fees embedded in contract marketing records, which can affect total contract cost, pricing structure, and vendor compensation analysis. It is useful when reviewing fee-based service arrangements, monitoring unusual charges, or segmenting awards with payment terms tied to service usage.
Example Value
0
Observed Non-Null Count
111,508,691

FPDS Compare

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

Use Cases

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

Common Usage

  • Filter awards with nonzero service-use fees
  • Summarize fee amounts by agency, vendor, or award type
  • Flag records where service-use fees appear in pricing analysis

Common Mistakes

  • Assuming 0 always means no fee was charged
  • Using the field without checking related contract marketing attributes

Query Guidance

Use numeric comparisons and aggregation functions such as SUM, AVG, and CASE WHEN feePaidForUseOfService > 0. When joining or grouping, keep the field at the award-level grain and avoid treating it as a coded text field; if your dataset stores nulls and zeros differently, test both in filters.

SQL Examples

Preview values

SELECT
    content__award__contractMarketingData__feePaidForUseOfService AS fee_paid_for_use_of_service
FROM fpds.data
WHERE content__award__contractMarketingData__feePaidForUseOfService IS NOT NULL
LIMIT 25

Aggregate total

SELECT
    sum(content__award__contractMarketingData__feePaidForUseOfService) AS total_value
FROM fpds.data
WHERE content__award__contractMarketingData__feePaidForUseOfService IS NOT NULL

Distribution overview

SELECT
    min(content__award__contractMarketingData__feePaidForUseOfService) AS min_value,
    avg(content__award__contractMarketingData__feePaidForUseOfService) AS avg_value,
    max(content__award__contractMarketingData__feePaidForUseOfService) AS max_value,
    count() AS record_count
FROM fpds.data
WHERE content__award__contractMarketingData__feePaidForUseOfService IS NOT NULL

Each dictionary item includes SQL-ready examples generated alongside the variable metadata, allowing immediate use in FPDS Query for filtering, aggregation, and analysis.