NASA Satellite Boosts Space Network
By Elena Malykhina
InformationWeek
The Tracking and Data Relay Satellite, or TDRS-K, blasted off Jan. 30 aboard a United Launch Alliance Atlas V rocket from Cape Canaveral, Fla. The satellite is one piece in a broader plan to modernize the Space Network, which is a geosynchronous relay system that performs tracking and data transfer for NASA missions.
The Space Network's ground terminals date to the 1980s, and its communications protocols are becoming obsolete. Under a project called Space Network Ground Segment Sustainment (SNGSS), NASA is creating a more scalable ground terminal architecture.
TDRS-K is the eleventh satellite in NASA's TDRS program. The satellites provide tracking services and data streaming between Earth-orbiting missions, including the International Space Station, Hubble Telescope and climate research spacecraft, and the ground stations.
[ Gun control critics and supporters may overlook the importance of IT in Obama's executive order. See Federal Gun Control Requires IT Overhaul. ]
TDRS-K, which will be renamed TDRS-11 when it reaches orbit at 22,300 miles, features redesigned telecom payload electronics and a high-performance solar panel to provide more power to the spacecraft.
Building high-speed communications in space is a big focus for NASA. In September 2011, it began working on a laser-based optical communications system to reduce the time it takes to transmit multimedia from space. And last October, NASA and the European Space Agency operated a small robot in Germany from the International Space Station, using a networking protocol designed for deep space communications.
TDRS-K will be put through a three-month test before it goes into service. The satellite is designed to operate for 15 years. NASA also revealed plans for two subsequent satellites: TDRS-L will launch in 2014, to be followed by TDRS-M. NASA's goal is to always have one TDRS in orbit as a spare, according to an agency spokesman.
Federal agencies must eliminate 800 data centers over the next five years. Find how they plan to do it in the new all-digital issue of InformationWeek Government. Download it now (registration required).
Offensive cybersecurity is a tempting prospect. It's also way too early to go there. Here's what to do instead. Also in the new, all-digital Nuclear Option issue of InformationWeek: Military agencies worldwide are figuring out the tactics and capabilities that will be critical in any future cyber war. (Free registration required.)
 |
To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy. |
Subscribe to RSSInformationWeek Reports
Cloud Implementer's Checklist
Once your agency has completed the business case for a private cloud, how do you actually move ahead with your data center transformation? Our report provides a practical set of steps to get you there, including a "to do" list that will be helpful to anyone on your IT team who's involved in the project. By the time you're done, your data center should be home to a more flexible, on-demand IT services.
Cloud Compliance in Government
Compute clouds created for government data centers must adhere to a range of specifications designed to support data and system security, privacy, and governance. FISMA, HIPAA, SOX, and SAS 70 are just some of the requirements that have to be taken into account as federal IT pros deploy a shared-services cloud model. In this report, we identify the key specs that need to be factored into any federal cloud architecture.
Government Cloud Platform Strategy
This report analyzes the key IT infrastructure considerations that must be taken into account for implementing cloud services in federal data centers: software/hardware environment, multi-tenancy, security, virtualization, and management tools. We also explain the key important role that APIs play in supporting hybrid scenarios that tap into public cloud services.
The Business Case for Government Clouds
This report assesses usage scenarios, barriers, and other variables that factor into the decision of whether and how to implement cloud computing in federal environments.