Exact Contract Story
INTEGRATION AND RE-FLIGHT OF T0247 ORBITAL SYNGAS COMMODITY AUGMENTATION REACTOR(OSCAR) PAYLOAD
INTEGRATION AND RE-FLIGHT OF T0247 ORBITAL SYNGAS COMMODITY AUGMENTATION REACTOR(OSCAR) PAYLOAD
Status: Exact storyScope: blue-originContract key: USASPENDING-80AFRC20F0157Award ID: 80AFRC20F0157
Discovery Data
- Mission
- Blue Origin Program
- Awarded on
- 2020-09-10
- Obligated amount
- $552,707
- Agency
- NASA
- Customer
- BLUE ORIGIN TEXAS, LLC
- Recipient
- BLUE ORIGIN TEXAS, LLC
- Actions
- 1
- Notices
- 0
- Spending points
- 1
- Bidders
- 0
- Exact source records
- 1
Links
Exact Source Evidence
Exact external records already attached to this contract story.
USASpending award
1 linked80AFRC20F0157
Latest Award Actions
Mod 0 • 2020-09-10
Delta: $552,707 • Cumulative: $552,707
Vehicle/Engine Mapping
No vehicle mappings 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: USASPENDING-80AFRC20F0157 | 80AFRC20F0157. Add terms like "USAspending", "SAM.gov", or the awardee name for faster exact matching.