IGF::OT::IGF CPC WILL BEGIN CERTIFICATION EFFORTS UNDER PHASE 1 BY CONTRACTING WITH MULTIPLE INDUSTRY PROVIDERS FOR THE PURCHASE OF EARLY LIFECYCLE CERTIFICATION DATA PRODUCTS RELATED TO AN END-TO-END CREW TRANSPORTATION SYSTEM (CTS) FOR AN INTERNATIONAL SPACE STATION (ISS) DESIGN REFERENCE MISSION (DRM). CONTRACT DELIVERABLES INCLUDE ALTERNATE STANDARDS, HAZARD REPORTS, VERIFICATION AND VALIDATION PLAN, AND CERTIFICATION PLAN. PHASE 1 CONTRACT SCOPE WILL INCLUDE TECHNICAL INTERCHANGE BETWEEN NASA AND THE CONTRACTOR ON HOW DELIVERABLES MEET NASA CERTIFICATION REQUIREMENTS. PHASE 2 WILL BUILD ON THE RESULTS OF PHASE 1 AND CONTINUES THE CERTIFICATION ACTIVITY WITH FOCUS ON THE MAJOR CERTIFICATION ACCEPTANCE ACTIVITIES RESULTING IN NASA CERTIFICATION. PHASE 2 WILL ALSO INCLUDE AT LEAST ONE CREWED ISS DEMONSTRATION MISSION AND MAY INCLUDE ADDITIONAL CREWED MISSIONS TO ISS. THE AWARD CRITERIA FOR PHASE 2 WILL INCLUDE DEMONSTRATED COMPLETION OF PREVIOUS SPECIFIED PHASE 1 REQUIREMENTS. THE GOVERNMENT EXPECTS THAT ONLY PHASE 1 CONTRACTORS WILL BE CAPABLE OF SUCCESSFULLY COMPETING FOR PHASE 2. PROPOSALS FOR PHASE 2 WILL BE REQUESTED FROM THESE CONTRACTORS. PHASE 2 WILL BE SOLICITED UNDER A SEPARATE RFP TO BE RELEASED DURING THE PERFORMANCE OF THE AWARDED PHASE 1 CONTRACTS AND WILL BUILD ON THE RESULTS FROM PHASE 1. PHASE 2 WILL BE SYNOPSIZED IN ACCORDANCE WITH FAR 5.201 AND 5.203. THE CONTRACTOR SHALL DELIVER TWO VERSIONS OF EACH CLIN DELIVERABLE: INITIAL AND FINAL. EACH DELIVERABLE SHALL BE CONSISTENT WITH THE DESIGN MATURITY OF THE CONTRACTOR'S CTS AT THE TIME OF DELIVERY AND INCLUDE NOMENCLATURE TO IDENTIFY THE DESIGN MATURITY ASSOCIATED WITH THE CONTENTS IN THE DELIVERABLE. EACH DELIVERABLE SHALL ADDRESS THE RELEVANT REQUIREMENTS IN THE APPLICABLE DOCUMENTS LISTED IN SECTION C.6. EACH DELIVERABLE SHALL IDENTIFY RELEVANT NON-COMPLIANCE WITH CCT-REQ-1130 AND SSP 50808 REQUIREMENTS. FINAL DELIVERABLES MUST ADDRESS CONSISTENCY REQUIREMENTS AS DESCRIBED IN SECTION H, CONSISTENCY OF FINAL DATA DELIVERABLES. WITH THE EXCEPTION OF CLIN 2, HAZARD REPORTS, CONTRACTOR PREFERRED FORMATS AND DOCUMENTATION MAY BE USED TO MEET THE DATA REQUIREMENTS IF TRACEABILITY FROM THE CONTRACTOR DOCUMENT(S) TO THE DELIVERABLE REQUIREMENTS IS PROVIDED. CONTRACTOR PREFERRED CONFIGURATION MANAGEMENT OF DELIVERABLES CAN BE USED AS LONG AS THE DELIVERABLES ARE MARKED WITH THE CONTRACT NUMBER, VERSION, AND CLIN NUMBER. DELIVERABLES SHALL BE READABLE, PRINTABLE, AND DOWNLOADABLE BY NASA UTILIZING PUBLICLY AVAILABLE OFF-THE-SHELF SOFTWARE. | Contract Data Entity | T-Minus Zero
Contract Row Pending Story Join
IGF::OT::IGF CPC WILL BEGIN CERTIFICATION EFFORTS UNDER PHASE 1 BY CONTRACTING WITH MULTIPLE INDUSTRY PROVIDERS FOR THE PURCHASE OF EARLY LIFECYCLE CERTIFICATION DATA PRODUCTS RELATED TO AN END-TO-END CREW TRANSPORTATION SYSTEM (CTS) FOR AN INTERNATIONAL SPACE STATION (ISS) DESIGN REFERENCE MISSION (DRM). CONTRACT DELIVERABLES INCLUDE ALTERNATE STANDARDS, HAZARD REPORTS, VERIFICATION AND VALIDATION PLAN, AND CERTIFICATION PLAN. PHASE 1 CONTRACT SCOPE WILL INCLUDE TECHNICAL INTERCHANGE BETWEEN NASA AND THE CONTRACTOR ON HOW DELIVERABLES MEET NASA CERTIFICATION REQUIREMENTS. PHASE 2 WILL BUILD ON THE RESULTS OF PHASE 1 AND CONTINUES THE CERTIFICATION ACTIVITY WITH FOCUS ON THE MAJOR CERTIFICATION ACCEPTANCE ACTIVITIES RESULTING IN NASA CERTIFICATION. PHASE 2 WILL ALSO INCLUDE AT LEAST ONE CREWED ISS DEMONSTRATION MISSION AND MAY INCLUDE ADDITIONAL CREWED MISSIONS TO ISS. THE AWARD CRITERIA FOR PHASE 2 WILL INCLUDE DEMONSTRATED COMPLETION OF PREVIOUS SPECIFIED PHASE 1 REQUIREMENTS. THE GOVERNMENT EXPECTS THAT ONLY PHASE 1 CONTRACTORS WILL BE CAPABLE OF SUCCESSFULLY COMPETING FOR PHASE 2. PROPOSALS FOR PHASE 2 WILL BE REQUESTED FROM THESE CONTRACTORS. PHASE 2 WILL BE SOLICITED UNDER A SEPARATE RFP TO BE RELEASED DURING THE PERFORMANCE OF THE AWARDED PHASE 1 CONTRACTS AND WILL BUILD ON THE RESULTS FROM PHASE 1. PHASE 2 WILL BE SYNOPSIZED IN ACCORDANCE WITH FAR 5.201 AND 5.203. THE CONTRACTOR SHALL DELIVER TWO VERSIONS OF EACH CLIN DELIVERABLE: INITIAL AND FINAL. EACH DELIVERABLE SHALL BE CONSISTENT WITH THE DESIGN MATURITY OF THE CONTRACTOR'S CTS AT THE TIME OF DELIVERY AND INCLUDE NOMENCLATURE TO IDENTIFY THE DESIGN MATURITY ASSOCIATED WITH THE CONTENTS IN THE DELIVERABLE. EACH DELIVERABLE SHALL ADDRESS THE RELEVANT REQUIREMENTS IN THE APPLICABLE DOCUMENTS LISTED IN SECTION C.6. EACH DELIVERABLE SHALL IDENTIFY RELEVANT NON-COMPLIANCE WITH CCT-REQ-1130 AND SSP 50808 REQUIREMENTS. FINAL DELIVERABLES MUST ADDRESS CONSISTENCY REQUIREMENTS AS DESCRIBED IN SECTION H, CONSISTENCY OF FINAL DATA DELIVERABLES. WITH THE EXCEPTION OF CLIN 2, HAZARD REPORTS, CONTRACTOR PREFERRED FORMATS AND DOCUMENTATION MAY BE USED TO MEET THE DATA REQUIREMENTS IF TRACEABILITY FROM THE CONTRACTOR DOCUMENT(S) TO THE DELIVERABLE REQUIREMENTS IS PROVIDED. CONTRACTOR PREFERRED CONFIGURATION MANAGEMENT OF DELIVERABLES CAN BE USED AS LONG AS THE DELIVERABLES ARE MARKED WITH THE CONTRACT NUMBER, VERSION, AND CLIN NUMBER. DELIVERABLES SHALL BE READABLE, PRINTABLE, AND DOWNLOADABLE BY NASA UTILIZING PUBLICLY AVAILABLE OFF-THE-SHELF SOFTWARE.
IGF::OT::IGF CPC WILL BEGIN CERTIFICATION EFFORTS UNDER PHASE 1 BY CONTRACTING WITH MULTIPLE INDUSTRY PROVIDERS FOR THE PURCHASE OF EARLY LIFECYCLE CERTIFICATION DATA PRODUCTS RELATED TO AN END-TO-END CREW TRANSPORTATION SYSTEM (CTS) FOR AN INTERNATIONAL SPACE STATION (ISS) DESIGN REFERENCE MISSION (DRM). CONTRACT DELIVERABLES INCLUDE ALTERNATE STANDARDS, HAZARD REPORTS, VERIFICATION AND VALIDATION PLAN, AND CERTIFICATION PLAN. PHASE 1 CONTRACT SCOPE WILL INCLUDE TECHNICAL INTERCHANGE BETWEEN NASA AND THE CONTRACTOR ON HOW DELIVERABLES MEET NASA CERTIFICATION REQUIREMENTS. PHASE 2 WILL BUILD ON THE RESULTS OF PHASE 1 AND CONTINUES THE CERTIFICATION ACTIVITY WITH FOCUS ON THE MAJOR CERTIFICATION ACCEPTANCE ACTIVITIES RESULTING IN NASA CERTIFICATION. PHASE 2 WILL ALSO INCLUDE AT LEAST ONE CREWED ISS DEMONSTRATION MISSION AND MAY INCLUDE ADDITIONAL CREWED MISSIONS TO ISS. THE AWARD CRITERIA FOR PHASE 2 WILL INCLUDE DEMONSTRATED COMPLETION OF PREVIOUS SPECIFIED PHASE 1 REQUIREMENTS. THE GOVERNMENT EXPECTS THAT ONLY PHASE 1 CONTRACTORS WILL BE CAPABLE OF SUCCESSFULLY COMPETING FOR PHASE 2. PROPOSALS FOR PHASE 2 WILL BE REQUESTED FROM THESE CONTRACTORS. PHASE 2 WILL BE SOLICITED UNDER A SEPARATE RFP TO BE RELEASED DURING THE PERFORMANCE OF THE AWARDED PHASE 1 CONTRACTS AND WILL BUILD ON THE RESULTS FROM PHASE 1. PHASE 2 WILL BE SYNOPSIZED IN ACCORDANCE WITH FAR 5.201 AND 5.203. THE CONTRACTOR SHALL DELIVER TWO VERSIONS OF EACH CLIN DELIVERABLE: INITIAL AND FINAL. EACH DELIVERABLE SHALL BE CONSISTENT WITH THE DESIGN MATURITY OF THE CONTRACTOR'S CTS AT THE TIME OF DELIVERY AND INCLUDE NOMENCLATURE TO IDENTIFY THE DESIGN MATURITY ASSOCIATED WITH THE CONTENTS IN THE DELIVERABLE. EACH DELIVERABLE SHALL ADDRESS THE RELEVANT REQUIREMENTS IN THE APPLICABLE DOCUMENTS LISTED IN SECTION C.6. EACH DELIVERABLE SHALL IDENTIFY RELEVANT NON-COMPLIANCE WITH CCT-REQ-1130 AND SSP 50808 REQUIREMENTS. FINAL DELIVERABLES MUST ADDRESS CONSISTENCY REQUIREMENTS AS DESCRIBED IN SECTION H, CONSISTENCY OF FINAL DATA DELIVERABLES. WITH THE EXCEPTION OF CLIN 2, HAZARD REPORTS, CONTRACTOR PREFERRED FORMATS AND DOCUMENTATION MAY BE USED TO MEET THE DATA REQUIREMENTS IF TRACEABILITY FROM THE CONTRACTOR DOCUMENT(S) TO THE DELIVERABLE REQUIREMENTS IS PROVIDED. CONTRACTOR PREFERRED CONFIGURATION MANAGEMENT OF DELIVERABLES CAN BE USED AS LONG AS THE DELIVERABLES ARE MARKED WITH THE CONTRACT NUMBER, VERSION, AND CLIN NUMBER. DELIVERABLES SHALL BE READABLE, PRINTABLE, AND DOWNLOADABLE BY NASA UTILIZING PUBLICLY AVAILABLE OFF-THE-SHELF SOFTWARE.
What this contract page answers
This is the canonical contract page for NNK13MA08C. It summarizes the award identity, mission scope, obligated amount, customer, recipient, source evidence, and the exact program page that owns broader context.
Mission
SpaceX Program
Amount
$9,569,525
Recipient
Recipient not published
Story status
Story join pending
Contract evidence mix
Contract pages combine the normalized canonical row with linked actions, notices, spending points, bidder records, and source evidence when those records have been matched.
Actions
1
Notices
0
Spending points
1
Exact source records
0
Source and freshness notes
This page uses T-Minus Zero contract normalization plus linked public-source evidence. Award identifiers, source URLs, agency/customer fields, and amounts are shown only when available in the normalized source data.
Source label
USASpending award record
Freshness
Jul 24, 2026
Data policy
Published source fields only
Contract interpretation
Use this page to identify what the award is, who it is tied to, how much has been obligated, and which evidence rows support the contract story. Program pages own broader mission context and related contract families.
Award date
2013-01-22
Agency/customer
SPACE EXPLORATION TECHNOLOGIES CORP.
Match confidence
Not matched
Contract relationship map
The contract page owns row-level evidence. Program pages own broader mission context, story pages own narrative contract families, and public sources own exact award records.
Use these internal paths to move from this exact contract row into the mission hub, program contract index, source evidence, and broader program pages that own surrounding context.
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: NNK13MA08C | CONT_AWD_NNK13MA08C_8000_-NONE-_-NONE-. Add terms like "USAspending", "SAM.gov", or the awardee name for faster exact matching.
