• 0
    • ارسال درخواست
    • حذف همه
    • Industrial Standards
    • Defence Standards
  • درباره ما
  • درخواست موردی
  • فهرست استانداردها
    • Industrial Standards
    • Defence Standards
  • راهنما
  • Login
  • لیست خرید شما 0
    • ارسال درخواست
    • حذف همه
View Item 
  •   YSE
  • Defence Standards
  • NASA - National Aeronautics and Space Administration (NASA)
  • View Item
  •   YSE
  • Defence Standards
  • NASA - National Aeronautics and Space Administration (NASA)
  • View Item
  • All Fields
  • Title(or Doc Num)
  • Organization
  • Year
  • Subject
Advanced Search
JavaScript is disabled for your browser. Some features of this site may not work without it.

Archive

NASA-LLIS-0218

Lessons Learned - Mission Control Computer Support System

Organization:
NASA - National Aeronautics and Space Administration (NASA)
Year: 1992

Abstract: Description of Driving Event:
When the mission control center was first activated in the early 1960s, it was considered a technical marvel. However, this original architecture has received only modest upgrades since the Apollo program days. Until recently, it maintained a single mainframe based architecture that displayed data and largely left the job of data analysis and trend determination to the flight controller teams monitoring the consoles. The display technology utilized in this system is monochrome and primarily displays text information. The job of turning data into information, upon which flight decisions could be made is performed by the controllers through interpretation of the incoming numeric data. In cases where it was determined that additional computational support was required, small off-line personal computers were added. The controllers manually copied data from the console display screens and entered it into the small computers to perform off-line analysis.
Although this system is technologically outdated, it contains years of customizing efforts and has served NASA well through space shuttle program missions to date. Several factors are now driving NASA to change the architecture of the mission control center operations. First, the primary reason seems to be to control costs. Second, automation available today can be used to expand the capabilities of controllers by eliminating some of the data reduction tasks they must perform and by increasing the amount of information they can utilize in making decisions. Third, the time required to obtain information for decision-making can be substantially reduced.
URI: https://yse.yabesh.ir/std/handle/yse/131801
Subject: Computers
Collections :
  • NASA - National Aeronautics and Space Administration (NASA)
  • Download PDF : (13.45Kb)
  • Show Full MetaData Hide Full MetaData
  • Statistics

    NASA-LLIS-0218

Show full item record

contributor authorNASA - National Aeronautics and Space Administration (NASA)
date accessioned2017-09-04T17:08:15Z
date available2017-09-04T17:08:15Z
date copyright33925
date issued1992
identifier otherYJZCQCAAAAAAAAAA.pdf
identifier urihttps://yse.yabesh.ir/std/handle/yse/131801
description abstractDescription of Driving Event:
When the mission control center was first activated in the early 1960s, it was considered a technical marvel. However, this original architecture has received only modest upgrades since the Apollo program days. Until recently, it maintained a single mainframe based architecture that displayed data and largely left the job of data analysis and trend determination to the flight controller teams monitoring the consoles. The display technology utilized in this system is monochrome and primarily displays text information. The job of turning data into information, upon which flight decisions could be made is performed by the controllers through interpretation of the incoming numeric data. In cases where it was determined that additional computational support was required, small off-line personal computers were added. The controllers manually copied data from the console display screens and entered it into the small computers to perform off-line analysis.
Although this system is technologically outdated, it contains years of customizing efforts and has served NASA well through space shuttle program missions to date. Several factors are now driving NASA to change the architecture of the mission control center operations. First, the primary reason seems to be to control costs. Second, automation available today can be used to expand the capabilities of controllers by eliminating some of the data reduction tasks they must perform and by increasing the amount of information they can utilize in making decisions. Third, the time required to obtain information for decision-making can be substantially reduced.
languageEnglish
titleNASA-LLIS-0218num
titleLessons Learned - Mission Control Computer Support Systemen
typestandard
page2
statusActive
treeNASA - National Aeronautics and Space Administration (NASA):;1992
contenttypefulltext
subject keywordsComputers
subject keywordsFlight Operations
subject keywordsLaunch Process
subject keywordsRange Operations
DSpace software copyright © 2017-2020  DuraSpace
نرم افزار کتابخانه دیجیتال "دی اسپیس" فارسی شده توسط یابش برای کتابخانه های ایرانی | تماس با یابش
yabeshDSpacePersian
 
DSpace software copyright © 2017-2020  DuraSpace
نرم افزار کتابخانه دیجیتال "دی اسپیس" فارسی شده توسط یابش برای کتابخانه های ایرانی | تماس با یابش
yabeshDSpacePersian