By Topic

NASA Earth Observing System Mission Operations Center development using COTS products

Sign In

Cookies must be enabled to login.After enabling cookies , please use refresh or reload or ctrl+f5 on the browser for the login options.

Formats Non-Member Member
$31 $13
Learn how you can qualify for the best price for this item!
Become an IEEE Member or Subscribe to
IEEE Xplore for exclusive pricing!
close button

puzzle piece

IEEE membership options for an individual and IEEE Xplore subscriptions for an organization offer the most affordable access to essential journal articles, conference papers, standards, eBooks, and eLearning courses.

Learn more about:

IEEE membership

IEEE Xplore subscriptions

1 Author(s)
DiUbaldo, J.A. ; Raytheon Syst. Co., Aurora, CO, USA

The original NASA EOS Terra Spacecraft ground command and control system development started as a custom product but was failing to meet the requirements. Less than six months before launch a replacement system was developed. The new development tested COTS products offering the best potential for a low cost, successful delivery. Some difficulties encountered with using the COTS product were that operations concepts varied considerably from the EOS missions. In this case the EOS Flight Operations Team was well established and had settled on a concept of operations. No single standard exists for space-to-ground communications and the ground interfaces were unique to NASA so new interfaces had to be developed. Another consideration was the mission life cycle of 10-to-12 years COTS (Commercial Off-The-Shelf) product life cycles tend to be much shorter. Our approach involved the operations team and selected COTS products that closely matched the original operations concepts. Requirements were scrubbed to identify those critical to launch and which could be deleted or modified. Multiple builds were made to support mission rehearsal requirements and incorporate critical requirements early to allow the greatest amount of test time. The first build was delivered and installed less than 45 days after the initial contract and the first mission rehearsal was more successful than any previous EOS rehearsal on the original system. A subsequent build 90 days later supported all launch critical requirements and the system was declared launch-ready on time to support the planned launch. COTS products can be used to accelerate development schedules, but tailoring of the product is often unavoidable. If extensive tailoring is required, consideration should be given to a custom development. Upgrades to the COTS products can introduce new problems and must be carefully managed

Published in:

Aerospace Conference Proceedings, 2000 IEEE  (Volume:2 )

Date of Conference: