Skip to main content
T-Minus ZeroComm Link

Exact Contract Story

KEY OBJECTIVE: THE PRIMARY OBJECTIVE IS TO DEVELOP AND TEST AN EXTERNAL ENVIRONMENT ACCESS PAYLOAD ACCOMMODATION FACILITY. WE PROPOSE TO DEMONSTRATE A VEHICLE ENHANCEMENT AND ONBOARD FACILITY FOR PAYLOAD ACCOMMODATION FOR THE BLUE ORIGIN NEW SHEPPARD REUSABLE SUBORBITAL LAUNCH VEHICLE BY ESTABLISHING AN EXTERNAL ENVIRONMENT ACCESS CAPABILITY. THIS PROPOSAL IS SOLELY FOR INTEGRATION AND FLIGHT TESTING. THE ENHANCEMENT CONSISTS OF THE JANUS INTEGRATION PLATFORM MODIFIED WITH AN AEROGEL COLLECTOR SYSTEM TO BE MOUNTED ON THE UPPER RING OF THE PROPULSION MODULE (PM). TECHNIQUES FOR ACCOMPLISHING THE KEY OBJECTIVE: 1) INTEGRATE AEROGEL COLLECTOR WITH EXISTING JANUS 2.0 INTEGRATION PLATFORM 2) MOUNT OUR PAYLOAD ON THE BLUE ORIGIN NEW SHEPARD VEHICLE TO ALLOW EXTERNAL ENVIRONMENT ACCESS 3) FLY THIS PAYLOAD WITH EXTERNAL ACCESS ON THE TEST FLIGHT. 4) ANALYZE FLIGHT RESULTS AND ASSESS THE EXTERNAL ENVIRONMENT PERCEIVED SIGNIFICANCE: OUR PROPOSED PROJECT IS HIGHLY SIGNIFICANT TO U.S. SPACE EXPLORATION AND UTILIZATION BECAUSE SUCH EXTERNAL ENVIRONMENT ACCESS IS A CRITICAL CAPABILITY THAT MUST BE DEVELOPED IF THESE NEW VEHICLES ARE TO HAVE SUCH A GAME CHANGING IMPACT. CURRENTLY NO EXTERNAL ENVIRONMENT ACCESS CAPABILITY EXISTS ON THE BLUE ORIGIN NEW SHEPPARD VEHICLE SO OUR PROPOSAL EXCEEDS CURRENT STATE OF THE ART. ESTABLISHING SUCH A NOVEL CAPABILITY IS REVOLUTIONARY DISRUPTIVE AND TRANSFORMATIVE. TO DATE RELATIVELY LITTLE IN SITU OBSERVATIONS AND SAMPLING EXIST FOR SUBORBITAL SPACE AT 80-100 KM ALTITUDES DESPITE THIS BEING A CRITICAL REGION WHERE THE ATMOSPHERE (COLLISIONAL) TRANSITIONS TO SPACE (NON-COLLISIONAL). WHAT LITTLE DATA EXISTS WAS DERIVED FROM INFREQUENT AND RELATIVELY EXPENSIVE SOUNDING ROCKETS. ONCE WE ESTABLISH THIS CAPABILITY WE ANTICIPATE A NEW ERA OF DISCOVERY IN THIS REGION WILL PROVIDE UNPRECEDENTED INSIGHT INTO SUBORBITAL SPACE IMPACTING MANY EARTH BASED AND GEOSCIENCE MISSIONS REQUIRING SCIENTIFIC MEASUREMENTS. ADDITIONALLY WE WILL ENABLE MANY MORE INSTRUMENT DEVELOPMENT/TESTING AND TECHNOLOGY DEMONSTRATION PROGRAMS THAT WILL LIKELY MORE RAPIDLY ADVANCE THE STATE OF THE ART FOR INSTRUMENTS ON LARGE SPACE MISSIONS. THIS IS ENABLED BY INSTRUMENT DEVELOPMENT TESTING AND EVALUATIONS AT DRAMATICALLY LOWER COSTS AND MORE RAPID DEVELOPMENT TIMELINES. SUCH A CAPABILITY NOT ONLY ALSO SUPPORTS EARTH BASED MISSIONS BUT ALSO ALL PLANETARY MISSIONS AND COMMERCIAL VENTURES WHERE THIS ENVIRONMENT IS AT LEAST PARTIALLY APPLICABLE. VIRTUALLY ANY MISSION OR COMMERCIAL APPLICATION THAT REQUIRES EXTERNAL ACCESS AT 100 KM ALTITUDES OR BELOW WILL BE ENABLED BY OUR PROPOSED WORK.

KEY OBJECTIVE: THE PRIMARY OBJECTIVE IS TO DEVELOP AND TEST AN EXTERNAL ENVIRONMENT ACCESS PAYLOAD ACCOMMODATION FACILITY. WE PROPOSE TO DEMONSTRATE A VEHICLE ENHANCEMENT AND ONBOARD FACILITY FOR PAYLOAD ACCOMMODATION FOR THE BLUE ORIGIN NEW SHEPPARD REUSABLE SUBORBITAL LAUNCH VEHICLE BY ESTABLISHING AN EXTERNAL ENVIRONMENT ACCESS CAPABILITY. THIS PROPOSAL IS SOLELY FOR INTEGRATION AND FLIGHT TESTING. THE ENHANCEMENT CONSISTS OF THE JANUS INTEGRATION PLATFORM MODIFIED WITH AN AEROGEL COLLECTOR SYSTEM TO BE MOUNTED ON THE UPPER RING OF THE PROPULSION MODULE (PM). TECHNIQUES FOR ACCOMPLISHING THE KEY OBJECTIVE: 1) INTEGRATE AEROGEL COLLECTOR WITH EXISTING JANUS 2.0 INTEGRATION PLATFORM 2) MOUNT OUR PAYLOAD ON THE BLUE ORIGIN NEW SHEPARD VEHICLE TO ALLOW EXTERNAL ENVIRONMENT ACCESS 3) FLY THIS PAYLOAD WITH EXTERNAL ACCESS ON THE TEST FLIGHT. 4) ANALYZE FLIGHT RESULTS AND ASSESS THE EXTERNAL ENVIRONMENT PERCEIVED SIGNIFICANCE: OUR PROPOSED PROJECT IS HIGHLY SIGNIFICANT TO U.S. SPACE EXPLORATION AND UTILIZATION BECAUSE SUCH EXTERNAL ENVIRONMENT ACCESS IS A CRITICAL CAPABILITY THAT MUST BE DEVELOPED IF THESE NEW VEHICLES ARE TO HAVE SUCH A GAME CHANGING IMPACT. CURRENTLY NO EXTERNAL ENVIRONMENT ACCESS CAPABILITY EXISTS ON THE BLUE ORIGIN NEW SHEPPARD VEHICLE SO OUR PROPOSAL EXCEEDS CURRENT STATE OF THE ART. ESTABLISHING SUCH A NOVEL CAPABILITY IS REVOLUTIONARY DISRUPTIVE AND TRANSFORMATIVE. TO DATE RELATIVELY LITTLE IN SITU OBSERVATIONS AND SAMPLING EXIST FOR SUBORBITAL SPACE AT 80-100 KM ALTITUDES DESPITE THIS BEING A CRITICAL REGION WHERE THE ATMOSPHERE (COLLISIONAL) TRANSITIONS TO SPACE (NON-COLLISIONAL). WHAT LITTLE DATA EXISTS WAS DERIVED FROM INFREQUENT AND RELATIVELY EXPENSIVE SOUNDING ROCKETS. ONCE WE ESTABLISH THIS CAPABILITY WE ANTICIPATE A NEW ERA OF DISCOVERY IN THIS REGION WILL PROVIDE UNPRECEDENTED INSIGHT INTO SUBORBITAL SPACE IMPACTING MANY EARTH BASED AND GEOSCIENCE MISSIONS REQUIRING SCIENTIFIC MEASUREMENTS. ADDITIONALLY WE WILL ENABLE MANY MORE INSTRUMENT DEVELOPMENT/TESTING AND TECHNOLOGY DEMONSTRATION PROGRAMS THAT WILL LIKELY MORE RAPIDLY ADVANCE THE STATE OF THE ART FOR INSTRUMENTS ON LARGE SPACE MISSIONS. THIS IS ENABLED BY INSTRUMENT DEVELOPMENT TESTING AND EVALUATIONS AT DRAMATICALLY LOWER COSTS AND MORE RAPID DEVELOPMENT TIMELINES. SUCH A CAPABILITY NOT ONLY ALSO SUPPORTS EARTH BASED MISSIONS BUT ALSO ALL PLANETARY MISSIONS AND COMMERCIAL VENTURES WHERE THIS ENVIRONMENT IS AT LEAST PARTIALLY APPLICABLE. VIRTUALLY ANY MISSION OR COMMERCIAL APPLICATION THAT REQUIRES EXTERNAL ACCESS AT 100 KM ALTITUDES OR BELOW WILL BE ENABLED BY OUR PROPOSED WORK.

Status: Exact storyScope: blue-originContract key: USASPENDING-80NSSC18K0268Award ID: 80NSSC18K0268

Discovery Data

Mission
Blue Origin Program
Awarded on
2017-12-14
Obligated amount
$235,484
Agency
NASA
Customer
THE JOHNS HOPKINS UNIVERSITY
Recipient
THE JOHNS HOPKINS UNIVERSITY
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 linked

Latest Award Actions

  • Mod 02017-12-14

    Delta: $235,484 • Cumulative: $235,484

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-80NSSC18K0268 | 80NSSC18K0268. Add terms like "USAspending", "SAM.gov", or the awardee name for faster exact matching.