Signed Date

The date the Other Transaction IDV was signed, stored as a timestamp-like string in the contract's relevant dates section. It represents the execution date of the instrument, not necessarily the award announcement or obligation date.

Family: Other Transaction IDV
Category: Dates
Data Type: string
Semantic Type: attribute
Mapping: flattened_fpds_xml_field
AI Confidence: high

Variable Overview

FPDS Query Variable
content__OtherTransactionIDV__contractDetail__relevantContractDates__signedDate
Title
Signed Date
FPDS Path
OtherTransactionIDV/contractDetail/relevantContractDates/signedDate
Description
The date the Other Transaction IDV was signed, stored as a timestamp-like string in the contract's relevant dates section. It represents the execution date of the instrument, not necessarily the award announcement or obligation date.
Business Meaning
This field establishes when the IDV became effective for procurement analysis, enabling timeline reconstruction, period-based reporting, and comparison against related award, action, or obligation dates. Analysts use it to measure award timing, align agreements to fiscal periods, and identify patterns in OT use over time.
Example Value
2018-08-24 00:00:00
Observed Non-Null Count
13,417

FPDS Compare

FPDS Query Variable
content__OtherTransactionIDV__contractDetail__relevantContractDates__signedDate
FPDS XML Path
OtherTransactionIDV/contractDetail/relevantContractDates/signedDate
Mapping Type
flattened_fpds_xml_field
Comparison Summary
FPDS Query flattens the original nested FPDS XML path 'OtherTransactionIDV/contractDetail/relevantContractDates/signedDate' into the SQL-ready variable 'content__OtherTransactionIDV__contractDetail__relevantContractDates__signedDate'.

Use Cases

  • Dictionary lookup and field explanation
  • SQL filtering and grouping
  • Analytical reporting and reusable query building
  • Timeline, cohort, and period analysis

Common Usage

  • Assigning OT IDVs to fiscal periods
  • Measuring time from solicitation or proposal to signed instrument
  • Grouping awards by signature month or quarter

Common Mistakes

  • Using it as the obligation date
  • Comparing raw strings without date conversion or time-zone handling

Query Guidance

Cast or parse the field to a DATE or TIMESTAMP before filtering, sorting, or aggregating. Use it in WHERE clauses for date ranges and in GROUP BY expressions for monthly or quarterly trend analysis.

SQL Examples

Preview values

SELECT
    content__OtherTransactionIDV__contractDetail__relevantContractDates__signedDate AS signed_date
FROM fpds.data
WHERE content__OtherTransactionIDV__contractDetail__relevantContractDates__signedDate IS NOT NULL
LIMIT 25

Top values

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