SBIR Topic N Ocean Data Telemetry MicroSat Link ODTML SERB.1 Ocean Data Telemetry MicroSat Link ODTML – Concept OBJECTIVES: –Develop next-generation communications relay microsatellite network system architecture –Design, build one ODTML payload to demonstrate technology and ConOps DESCRIPTION –Capabilities: -Global access -Higher bandwidth than Service Argos -> 50,000 bits per buoy per day -< 0.1 joule per bit transmitted -Position determination of ocean monitoring platforms (OMPs) -Two-way delay-tolerant messaging (sensor-to-sensor, sensor-to-user) –Elements of ODTML network system: -Microsatellites ("routers in the sky") -OMPs (e.g., Free-floating buoys) -Ground stations -The internet (communication conduit between the users and OMPs) –Compatible with existing Service ARGOS

SBIR Topic N Ocean Data Telemetry MicroSat Link ODTML SERB.2 Ocean Data Telemetry MicroSat Link ODTML – Justification MILITARY RELEVANCE –Need cost-effective, near real-time, higher-bandwidth, integrated, global communications relay system -Outdated communications relay system for ocean-monitoring platforms (Service ARGOS) -National Defense Authorization Act (P.L ) Directs SECNAV To Fund/Establish Partnerships for New Facilities In Ocean Research and Sciences –ODTML will enhance the U.S. Navy's ocean-monitoring capabilities -Network of communications relays, enabling users to interrogate and task ocean-monitoring platforms -Faster response time to a detected event –DoD Applications: -Anti-submarine warfare -Surveillance, battlefield awareness -Environmental monitoring NEED FOR SPACEFLIGHT –Ocean-wide, sustained “24/7” coverage requires space-borne platforms –Airborne platforms (e.g., P-3) operationally not viable -Cannot provide ocean-wide network -Cannot meet 24/7 availability in the long run (resources limited) COMPARISON TO ALTERNATIVES –Higher bandwidth/efficiency, more capabilities than Service Argos, GOES –Commercial “store-n-forward” satellites (HealthSat-2/UOSAT-12, and WavSat: no DoD application, no position determination) –2-way LEO satellites (ORBCOMM, Iridium – Freq. and EIRP Requirements Not Compatible With Power-Constrained Buoys

SBIR Topic N Ocean Data Telemetry MicroSat Link ODTML SERB.3 Ocean Data Telemetry MicroSat Link ODTML – Detailed Overview FLIGHT DATA –Piggyback experiment to a free-flyer km, circular orbit -98   10  inclination –One flight required –Min. 12-month duration (gathering of seasonal oceanic data) –0.2 m 3, 50 kg max, 50 W STATUS –Concept design review PRIORITY –N/A RQUESTED STP SERVICES –As “piggyback” experiment: -Launch services -Spacecraft/experiment integration EXPERIMENT FUNDING –To-date: $100k concept study –$750k being requested for design, development, and build of one “tabletop” demonstration unit –* Estimated $1.5M needed for one flight unit FY03FY04FY05FY06FY07 SBIR Phase I & II $100k Funded $400k Pending $350k Pending SBIR Phase III $300k (*est.) $800k (*est.) $400k (*est.)

SBIR Topic N Ocean Data Telemetry MicroSat Link ODTML SERB.4 Ocean Data Telemetry MicroSat Link ODTML – Summary of Data Application Navy’s Naval Research Laboratory can use the data from this experiment to develop a 3- or 4-satellite ocean data telemetry communications relay system, which will provide global coverage for the Navy’s autonomous ocean- monitoring platforms (e.g., buoys). ODTML system will allow the Navy to acquire better tactical information on the oceanic environment where operations will take place – this will ensure increased operational effectiveness and success. It will also extend the Navy’s surveillance and remote-sensing capabilities. It may also serve as a backup UHF communications system to other DoD ComSat. The data analysis will be complete 18 months after the experiment is launched. Applicable category of this research: Advanced Technology Demonstration A Possible Concept of Operations

SBIR Topic N Ocean Data Telemetry MicroSat Link ODTML SERB.5 Ocean Data Telemetry MicroSat Link ODTML – Flight Mode Suitability ODTML demonstration model –Can be launched as a free flyer or as piggyback payload (preferred) to a LEO satellite No need for flight hardware retrieval Flight Mode% Experiment Objectives Satisfied Shuttle25% (short duration) Shuttle Deployable50% (design costs, complexity) Shuttle Deployable with Propulsion50% (design costs, complexity) International Space Station75% (limited fly-over coverage) “Piggyback” Free-flyer on ELV100% Dedicated Free-flyer on ELV100%