THIS STATEMENT OF WORK SPECIFIES THE PROCUREMENT OF CONNECTORS AS REQUIRED FOR NASA ORION CREW SURVIVAL SYSTEMS (OCSS) PROJECT, IN SUPPORT OF THE ORION PROGRAM. | Contract Data Entity | T-Minus Zero
Exact Contract Story
THIS STATEMENT OF WORK SPECIFIES THE PROCUREMENT OF CONNECTORS AS REQUIRED FOR NASA ORION CREW SURVIVAL SYSTEMS (OCSS) PROJECT, IN SUPPORT OF THE ORION PROGRAM.
THIS STATEMENT OF WORK SPECIFIES THE PROCUREMENT OF CONNECTORS AS REQUIRED FOR NASA ORION CREW SURVIVAL SYSTEMS (OCSS) PROJECT, IN SUPPORT OF THE ORION PROGRAM.
Awardee: AIR-LOCK, INCORPORATED • Base award: 2024-04-15
Opportunity Notices
No notices available.
Contract Detail FAQ
Search-first answers for this contract entity and its source identifiers.
What sources feed the contract data on this site?
Contract entities combine USAspending award references with SAM.gov-normalized procurement records (including PIID-linked actions, notices, and spending rows when available).
Why is there a canonical /contracts URL when program pages already exist?
Program pages keep mission context, while /contracts URLs consolidate duplicate contract entities into one indexable canonical URL so search engines attribute ranking signals to a single record.
Which identifiers should I search to find a specific government contract?
Use any of these identifiers: USAspending Award ID, PIID, contract key, solicitation ID, notice ID, recipient/awardee name, or agency/customer name.
How often do contract pages update?
Contract pages revalidate on a 10-minute cadence, while upstream source data refresh timing depends on ingest jobs and source-side publication timing.
What is the difference between SAM.gov and USAspending in these records?
USAspending primarily provides award and obligation visibility, while SAM.gov captures procurement lifecycle context such as solicitation notices and related action thread signals.
Why can the contract amount differ from another source?
Amounts can differ across snapshots because some sources report base award value while others include modification deltas, cumulative obligations, or later adjustments.
Can one contract appear in more than one program section?
Yes. A contract may appear in multiple program contexts; canonical entities are designed to consolidate those overlaps into a single URL for indexing and discovery.
What is a PIID on a contract detail page?
PIID stands for Procurement Instrument Identifier. It is the contracting identifier used to track related awards, actions, and notices across a procurement thread.
Where should I verify the official source record for this contract?
Use the Source record link on the contract detail page. The page also links back to the program-native detail page and, when available, the Artemis story page for thread context.
Why are actions, notices, or spending rows sometimes missing?
Missing rows usually mean no matched records were returned yet for that identifier set in the current source snapshot, not that the contract entity itself is invalid.
What exact terms should I search to verify this specific contract?
Use these identifiers in search: CONT_AWD_80JSC024F0042_8000_80JSC020D0008_8000| | 80JSC024F0042 | CONT_AWD_80JSC024F0042_8000_80JSC020D0008_8000. Add terms like "USAspending", "SAM.gov", or the awardee name for faster exact matching.
