ACCESS TO SPACE FOR SMALL SATELLITES IS ENABLED BY THE USE OF EXCESS LAUNCH CAPACITY. AN INTEGRATION PROCESS THAT MINIMIZES RISK TO THE PRIMARY, ALLOWS PARALLEL INTEGRATION AND PREDICTABLE COST/SCHEDULE FOR THE SECONDARY ENABLES USE OF THAT CAPACITY. DESIGN_NET HAS DEVELOPED AND FLOWN A FALCON 1 RIDESHARE ADAPTER (RSA) AND IS DEVELOPING A RSA FOR THE MINOTAUR IV, EELVS AND FALCON 9. AN RSA IS MORE THAN STRUCTURE, IT MUST HAVE ELECTRONICS TO PROVIDE A SINGLE SIMPLE INTERFACE TO THE LAUNCH VEHICLE (CONSTANT FROM MISSION TO MISSION), YET PROVIDE A STANDARD SET OF SERVICES TO PAYLOADS. DNET HAS LEVERAGED WORK ON THE FALCON RSA, WORK ON ADVANCED AFRL PLUG AND PLAY AVIONICS AND COMMERCIAL INVESTMENTS TO DEVELOP A MODULAR SECONDARY PAYLOAD SUPPORT UNIT (SPSU). SPSU PROVIDES DEPLOYMENT, POWER DISTRIBUTION, AND TELEMETRY SERVICES FOR SECONDARIES. WE PROPOSE BUILDING ON THAT WORK BY ADDING VIDEO CAPABILITY TO VERIFY AND EVALUATE PAYLOAD DEPLOYMENT. DURING PHASE 1 WE DEVELOP THE VIDEO TO PDR LEVEL (BEGIN TRL 3; END TRL 4) AND DURING PHASE 2 CARRY DEVELOPMENT OF THAT MODULE COUPLED WITH THE REST OF THE SPSU (CURRENTLY AT TRL 6) TO TRL 8 AND HAVE A SYSTEM READY FOR FLIGHT IN 2012 TIMEFRAME. | Contract Data Entity | T-Minus Zero
Contract Row Pending Story Join
ACCESS TO SPACE FOR SMALL SATELLITES IS ENABLED BY THE USE OF EXCESS LAUNCH CAPACITY. AN INTEGRATION PROCESS THAT MINIMIZES RISK TO THE PRIMARY, ALLOWS PARALLEL INTEGRATION AND PREDICTABLE COST/SCHEDULE FOR THE SECONDARY ENABLES USE OF THAT CAPACITY. DESIGN_NET HAS DEVELOPED AND FLOWN A FALCON 1 RIDESHARE ADAPTER (RSA) AND IS DEVELOPING A RSA FOR THE MINOTAUR IV, EELVS AND FALCON 9. AN RSA IS MORE THAN STRUCTURE, IT MUST HAVE ELECTRONICS TO PROVIDE A SINGLE SIMPLE INTERFACE TO THE LAUNCH VEHICLE (CONSTANT FROM MISSION TO MISSION), YET PROVIDE A STANDARD SET OF SERVICES TO PAYLOADS. DNET HAS LEVERAGED WORK ON THE FALCON RSA, WORK ON ADVANCED AFRL PLUG AND PLAY AVIONICS AND COMMERCIAL INVESTMENTS TO DEVELOP A MODULAR SECONDARY PAYLOAD SUPPORT UNIT (SPSU). SPSU PROVIDES DEPLOYMENT, POWER DISTRIBUTION, AND TELEMETRY SERVICES FOR SECONDARIES. WE PROPOSE BUILDING ON THAT WORK BY ADDING VIDEO CAPABILITY TO VERIFY AND EVALUATE PAYLOAD DEPLOYMENT. DURING PHASE 1 WE DEVELOP THE VIDEO TO PDR LEVEL (BEGIN TRL 3; END TRL 4) AND DURING PHASE 2 CARRY DEVELOPMENT OF THAT MODULE COUPLED WITH THE REST OF THE SPSU (CURRENTLY AT TRL 6) TO TRL 8 AND HAVE A SYSTEM READY FOR FLIGHT IN 2012 TIMEFRAME.
ACCESS TO SPACE FOR SMALL SATELLITES IS ENABLED BY THE USE OF EXCESS LAUNCH CAPACITY. AN INTEGRATION PROCESS THAT MINIMIZES RISK TO THE PRIMARY, ALLOWS PARALLEL INTEGRATION AND PREDICTABLE COST/SCHEDULE FOR THE SECONDARY ENABLES USE OF THAT CAPACITY. DESIGN_NET HAS DEVELOPED AND FLOWN A FALCON 1 RIDESHARE ADAPTER (RSA) AND IS DEVELOPING A RSA FOR THE MINOTAUR IV, EELVS AND FALCON 9. AN RSA IS MORE THAN STRUCTURE, IT MUST HAVE ELECTRONICS TO PROVIDE A SINGLE SIMPLE INTERFACE TO THE LAUNCH VEHICLE (CONSTANT FROM MISSION TO MISSION), YET PROVIDE A STANDARD SET OF SERVICES TO PAYLOADS. DNET HAS LEVERAGED WORK ON THE FALCON RSA, WORK ON ADVANCED AFRL PLUG AND PLAY AVIONICS AND COMMERCIAL INVESTMENTS TO DEVELOP A MODULAR SECONDARY PAYLOAD SUPPORT UNIT (SPSU). SPSU PROVIDES DEPLOYMENT, POWER DISTRIBUTION, AND TELEMETRY SERVICES FOR SECONDARIES. WE PROPOSE BUILDING ON THAT WORK BY ADDING VIDEO CAPABILITY TO VERIFY AND EVALUATE PAYLOAD DEPLOYMENT. DURING PHASE 1 WE DEVELOP THE VIDEO TO PDR LEVEL (BEGIN TRL 3; END TRL 4) AND DURING PHASE 2 CARRY DEVELOPMENT OF THAT MODULE COUPLED WITH THE REST OF THE SPSU (CURRENTLY AT TRL 6) TO TRL 8 AND HAVE A SYSTEM READY FOR FLIGHT IN 2012 TIMEFRAME.
Status: Story pendingScope: spacexContract key: NNX11CG35PAward ID: CONT_AWD_NNX11CG35P_8000_-NONE-_-NONE-
What this contract page answers
This is the canonical contract page for NNX11CG35P. It summarizes the award identity, mission scope, obligated amount, customer, recipient, source evidence, and the exact program page that owns broader context.
Mission
Falcon 9
Amount
$99,956
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
2011-02-18
Agency/customer
DESIGN NET ENGINEERING LLC
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: NNX11CG35P | CONT_AWD_NNX11CG35P_8000_-NONE-_-NONE-. Add terms like "USAspending", "SAM.gov", or the awardee name for faster exact matching.
