Exact Contract Story
AGGIESAT: AUTONOMOUS RENDEZVOUS&DOCKING TECHNOLOGY DEMONSTRATOR CURRENT AUTONOMOUS RENDEZVOUS AND DOCKING (AR&D) CAPABILITY IN LOW EARTH ORBIT (LEO) IS CONSTRAINED BY SENSOR AND EFFECTOR MASS, POWER, AND ACCURACY LIMITS. TO THIS END, NASA JOHNSON SPACE CENTER HAS DEVELOPED A GPS RECEIVER, CALLED DRAGON (DUAL RF ASTRODYNAMIC GPS ORBITAL NAVIGATOR), SPECIFICALLY TO ADDRESS THE SENSOR CONSTRAINTS. THE PROPOSED INNOVATION INCLUDES CREATING A SMALL, LOW-COST, AND VERSATILE TECHNOLOGY DEMONSTRATOR TO VALIDATE AND INCREASE THE TECHNOLOGY READINESS LEVEL OF DRAGON AND OTHER STATE-OF-THE-ART MINIATURIZED SENSORS AND EFFECTORS IN AN ON-ORBIT AR&D OPERATIONAL SCENARIO. FOR PHASE 1, A DEMONSTRATION PLATFORM WILL BE DEVELOPED THAT UTILIZES TWO PICOSATELLITES IN LEO, AND RELATIVE GPS AS THE PRIMARY SENSOR. THESE SATELLITES WILL BE LAUNCHED AS A SINGLE UNIT FROM THE SSPL (SPACE SHUTTLE PAYLOAD LAUNCHER) ON STS 127, THEN SEPARATE AND TRANSMIT DRAGON GPS DATA. THE PICOSATELLITE TECHNOLOGY DEMONSTRATOR WILL BE AT A TRL OF 7 AT THE END OF PHASE 1. FOR PHASE 2, THE DEMONSTRATION PLATFORM WILL BE FURTHER DEVELOPED TO FURTHER VALIDATE DRAGON, AND VALIDATE IMU SENSORS, A 1ST GENERATION REACTION CONTROL SYSTEM, A 1ST GENERATION GUIDANCE NAVIGATION AND CONTROL SYSTEM, COMMUNICATION LINKS, AND AN UNDOCKING MECHANISM.
AGGIESAT: AUTONOMOUS RENDEZVOUS&DOCKING TECHNOLOGY DEMONSTRATOR CURRENT AUTONOMOUS RENDEZVOUS AND DOCKING (AR&D) CAPABILITY IN LOW EARTH ORBIT (LEO) IS CONSTRAINED BY SENSOR AND EFFECTOR MASS, POWER, AND ACCURACY LIMITS. TO THIS END, NASA JOHNSON SPACE CENTER HAS DEVELOPED A GPS RECEIVER, CALLED DRAGON (DUAL RF ASTRODYNAMIC GPS ORBITAL NAVIGATOR), SPECIFICALLY TO ADDRESS THE SENSOR CONSTRAINTS. THE PROPOSED INNOVATION INCLUDES CREATING A SMALL, LOW-COST, AND VERSATILE TECHNOLOGY DEMONSTRATOR TO VALIDATE AND INCREASE THE TECHNOLOGY READINESS LEVEL OF DRAGON AND OTHER STATE-OF-THE-ART MINIATURIZED SENSORS AND EFFECTORS IN AN ON-ORBIT AR&D OPERATIONAL SCENARIO. FOR PHASE 1, A DEMONSTRATION PLATFORM WILL BE DEVELOPED THAT UTILIZES TWO PICOSATELLITES IN LEO, AND RELATIVE GPS AS THE PRIMARY SENSOR. THESE SATELLITES WILL BE LAUNCHED AS A SINGLE UNIT FROM THE SSPL (SPACE SHUTTLE PAYLOAD LAUNCHER) ON STS 127, THEN SEPARATE AND TRANSMIT DRAGON GPS DATA. THE PICOSATELLITE TECHNOLOGY DEMONSTRATOR WILL BE AT A TRL OF 7 AT THE END OF PHASE 1. FOR PHASE 2, THE DEMONSTRATION PLATFORM WILL BE FURTHER DEVELOPED TO FURTHER VALIDATE DRAGON, AND VALIDATE IMU SENSORS, A 1ST GENERATION REACTION CONTROL SYSTEM, A 1ST GENERATION GUIDANCE NAVIGATION AND CONTROL SYSTEM, COMMUNICATION LINKS, AND AN UNDOCKING MECHANISM.
Discovery Data
- Mission
- Dragon
- Awarded on
- 2009-01-22
- Obligated amount
- $99,998
- Agency
- U.S. Government
- Customer
- U.S. Government
- Recipient
- PHYSICS, MATERIALS, AND APPLIED MATHEMATICS RESEARCH L.L.C.
- 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 linkedNNX09CF69P
Latest Award Actions
Mod 0 • 2009-01-22
Delta: $99,998 • Cumulative: $99,998
Spending Timeline
FY 2009 M01
Obligations: $99,998 • Outlays: N/A
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-NNX09CF69P | NNX09CF69P. Add terms like "USAspending", "SAM.gov", or the awardee name for faster exact matching.