SEARCH · Search NASA
Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.
Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.
Contents: project plan summary; project and mission objectives; related studies and technology support activities; technical summary; management; procurement approach; project definition items and schedule; resources; management review; controlled items; and safety, reliability, and quality assurance.
The nature and use of design languages and associated processors that are used in software development are reviewed with reference to development work on the Galileo spacecraft project, a Jupiter orbiter scheduled for launch in 1984. The major design steps are identified (functional design, architectural design, detailed design, coding, and testing), and the purpose, functions and the range of applications of design languages are examined. Then the general character of any design language is analyzed in terms of syntax and semantics. Finally, the differences and similarities between design languages are illustrated by examining two specific design languages: Software Design and Documentation language and Problem Statement Language/Problem Statement Analyzer.
The objectives are to develop a process for manufacturing superstrate assemblies; demonstrate superstrate technology through fabrication and testing; develop and analyze a preliminary solar array wing design; and fabricate a wing segment based on the wing design. The task description, project flow diagram, and schedule are outlined. The progress to date is presented.
Information is given in viewgraph form on humans in space. Information is given on extravehicular activity/space suit project objectives and program schedule, and space human factors objectives and products.
The prelimary design of the propulsion subsystem for the CRAF and Cassini missions is described. It is noted that the propulsion module subsystem must provide impulse for a number of functions required by these missions. These functions include the acquisition of celestial references and trajectory correction maneuvers. A schedule for the CRAF/Cassini Project is provided.
When applied to a system, the doctrine of successive refinement is a divide-and-conquer strategy. Complex systems are sucessively divided into pieces that are less complex, until they are simple enough to be conquered. This decomposition results in several structures for describing the product system and the producing system. These structures play important roles in systems engineering and project management. Many of the remaining sections in this chapter are devoted to describing some of these key structures. Structures that describe the product system include, but are not limited to, the requirements tree, system architecture and certain symbolic information such as system drawings, schematics, and data bases. The structures that describe the producing system include the project's work breakdown, schedules, cost accounts and organization.
A major objective of the grant was to complete the fabrication, test, and evaluation of the atmosphere structure experiment on the Galileo Probe, and to receive, analyze, and interpret data received from the spacecraft. The grantee was competitively selected to be Principal Investigator of Jupiter's atmosphere structure on the Galileo Probe. His primary motivation was to learn as much as possible about Jupiter's atmosphere by means of a successful atmosphere structure experiment, and to support the needs and schedule of the Galileo Project. After a number of launch delays, the Flight instrument was shipped to Kennedy Space Center 2 years after the start of this collaboration, on April 14, 1989, at which time it was determined from System level tests of the ASI on the Probe that the instrument was in good working order and ready for flight. The spacecraft was launched on October 18, 1989. Data analysis of test and calibration data taken over a period of years of instrument testing was continued in preparation for the encounter. The initial instrument checkout in space was performed on October 26, 1989. The data set received by telemetry was thoroughly analyzed, and a report of the findings was transmitted to the Probe Operations Office on Feb. 28, 1990. Key findings reported were that the accelerometer biases had shifted by less than 1 mg through launch and since calibration at Bell Aerospace in 1983; accelerometer scale factors, evaluated by means of calibration currents, fell on lines of variation with temperature established in laboratory calibrations; pressure sensor offsets, correlated as a function of temperature, fell generally within the limits of several years of ground test data; atmospheric and engineering temperature sensor data were internally consistent within a few tenths of a degree; and the instrument electronics performed all expected functions without any observable fault. Altogether, this checkout was highly encouraging of the prospects of instrument performance, although performed greater than 5 years prior to Jupiter encounter. Capability of decoding the science data from the Experiment Data Record to be provided at encounter was developed and exercised using the tape recording of the first Cruise Checkout data. A team effort was organized to program the selection and combination of data words defining pressure, temperature, acceleration, turbulence, and engineering quantities; to apply decalibration algorithms to convert readings from digital numbers to physical quantities; and to organize the data into a suitable printout. A paper on the Galileo Atmosphere Structure Instrument was written and submitted for publication in a special issue of Space Science Reviews. At the Journal editor's request, the grantee reviewed other Probe instrument papers submitted for this special issue. Calibration data were carefully taken for all experiment sensors and accumulated over a period of 10 years. The data were analyzed, fitted with algorithms, and summarized in a calibration report for use in analyzing and interpreting data returned from Jupiter's atmosphere. The sensors included were the primary science pressure, temperature, and acceleration sensors, and the supporting engineering temperature sensors. This report was distributed to experiment coinvestigators and the Probe Project Office.
The holographic scanning lidar HARLIE made continuous measurements of aerosol and cloud one-micron backscatter and derived the horizontal wind speed and direction at cloud height over the ARM (SGP) site during the water vapor campaign WVIOP, September 17 - October 6, 2000. Whenever possible, these measurements were compared with Loran-C winds as measured by the routine launches of Vaisala radiosonde balloons scheduled by the ARM project. Taken overall, the agreement between these two types of observation is excellent, which could be taken merely as a validation of the relatively new HARLIE technique. However, the detailed comparison for a given sonde launch clearly requires that, out of the HARLIE data which are taken all the time at all altitudes, one must select those segments that match the altitude-time trajectory of the sonde. Moreover, the conical HARLIE scan at a 45 deg. elevation angle covers a wide area that is more representative of the average wind conditions above the site than the isolated track of the sonde's ascent. We suggest that the HARLIE instrument offers a more general and improved representation of the horizontal wind profile whenever there is sufficient backscatter by clouds and aerosols for lidar operation. HARLIE is a rugged and compact lidar that operates from aircraft as well as from the ground and has been used in several meteorological campaigns. As a "direct detection" lidar, HARLIE does not require the complexity of a coherent detection system. The data reduction algorithms facilitate the rapid and accurate determination of wind speed and direction at all altitudes. Wind measurements and HARLIE performance data from WVIOP 2000 and other campaigns will be presented.
Fulfilling the promise of an era of great observatories, NASA now has more than three space-based astronomical telescopes operating in different wavebands. This situation provides astronomers with a unique opportunity to simultaneously observe with multiple observatories. Yet scheduling multiple observatories simultaneously is highly inefficient when compared to single observatory observations. Thus, programs using multiple observatories are limited not due to scientific restrictions, but due to operational inefficiencies. Each year, a number of proposals are accepted by a space-based observatory for conduction of astronomical observations and gathering of science data for the study of galactic events. Since each space-based observatory uses a set of instruments designed to operate in specific energy regions, most such studies are conducted by submitting observation proposals to multiple observatories, with requests to coordinate among themselves. To assure that the proposed observations can be scheduled, each observatory's staff has to check that the observations are valid and meet all the constraints for their own observatory; in addition, they have to verify that the observations satisfy the constraints of the other observatories. Thus, coordinated observations require painstaking manual collaboration among the observatory staff at each observatory. In order to exploit new paradigms for observatory operation, the Goddard Space Flight Center's Advanced Architectures and Automation Branch has developed a prototype tool called the Visual Observation Layout Tool (VOLT). The main objective of VOLT is to provide a visual tool to automate the science planning of coordinated observations for multiple spacecraft, as well as to increase the scheduling probability of observations. However, VOLT is also useful for single observatory planning to optimize observatory control. Three space-based missions are interested in using VOLT (the Hubble Space Telescope, the Chandra X-Ray Observatory, and the Far Ultraviolet Spectroscopic Explorer). The VOLT team members have collaborated with these missions to gather requirements and obtain feedback on their mission planning processes. VOLT has been developed as a cross-platform Java client application for use by scientists and observatory science planning staff to visualize scheduling options and constraints. It also supports a lightweight graphical user interface for remote viewing via a Web front end. Additionally, it uniquely supports the ability to interact with multiple, diverse scheduling packages in order to determine windows of opportunity for observations and visually portray the constraints of each observation request. VOLT enables science data capture scenarios which are currently either impossible, or which require extensive time and manpower to coordinate amongst multiple observatories. it supports early detection of planning conflicts by generating coordinated solutions based on observatory schedulability and constraints. The project development approach has included frequent prototype demonstrations to our interested missions to obtain feedback after each release of the software. We will present an overview of our lessons learned in infusing the VOLT tool into the operations of the missions we have collaborated with and a brief demonstration of the software.
The Swift Observatory will be launched in early 2004 to examine the dynamic process of gamma ray burst (GRB) events. The multi-wavelength Observatory will study the GRB afterglow characteristics, which will help to answer fundamental questions about both the structure and the evolution of the universe. The Swift Observatory Contamination Control Program has been developed to aid in ensuring the success of the on-orbit performance of two of the primary instruments: the Ultraviolet and Optical Telescope (UVOT) and the X-Ray Telescope (XRT). During the design phase of the Observatory, the contamination control program evolved and trade studies were performed to assess the risk of contaminating the sensitive UVOT and XRT optics during both pre-launch testing and on-orbit operations, within the constraints of the overall program cost and schedule.
The Swift Observatory will be launched in early 2004 to examine the dynamic process of gamma ray burst (GRB) events. The multi-wavelength Observatory will study the GRB afterglow characteristics, which will help to answer fundamental questions about both the structure and the evolution of the universe. The Swift Observatory Contamination Control Program has been developed to aid in ensuring the success of the on-orbit performance of two of the primary instruments: the Ultraviolet and Optical Telescope (UVOT) and the X-Ray Telescope (XRT). During the design phase of the Observatory, the contamination control program evolved and trade studies were performed to assess the risk of contaminating the sensitive UVOT and XRT optics during both pre-launch testing and on-orbit operations, within the constraints of the overall program cost and schedule.
Visible Infrared Imager Radiometer Suite (VIIRS) instrument on-board the National Polar-orbiting Operational Environmental Satellite System (NPOESS) Preparatory Project (NPP) satellite is scheduled for launch in October, 2011. It is to provide satellite measured radiance/reflectance data for both weather and climate applications. Along with radiometric calibration, geometric characterization and calibration of Sensor Data Records (SDRs) are crucial to the VIIRS Environmental Data Record (EDR) algorithms and products which are used in numerical weather prediction (NWP). The instrument geometric performance includes: 1) sensor (detector) spatial response, parameterized by the dynamic field of view (DFOV) in the scan direction and instantaneous FOV (IFOV) in the track direction, modulation transfer function (MTF) for the 17 moderate resolution bands (M-bands), and horizontal spatial resolution (HSR) for the five imagery bands (I-bands); 2) matrices of band-to-band co-registration (BBR) from the corresponding detectors in all band pairs; and 3) pointing knowledge and stability characteristics that includes scan plane tilt, scan rate and scan start position variations, and thermally induced variations in pointing with respect to orbital position. They have been calibrated and characterized through ground testing under ambient and thermal vacuum conditions, numerical modeling and analysis. This paper summarizes the results, which are in general compliance with specifications, along with anomaly investigations, and describes paths forward for characterizing on-orbit BBR and spatial response, and for improving instrument on-orbit performance in pointing and geolocation.
Disciplined approach to Fault Management (FM) has not always been emphasized by projects, contributing to major schedule and cost overruns. Progress is being made on a number of fronts outside of Handbook effort: (1) Processes, Practices and Tools being developed at some Centers and Institutions (2) Management recognition . Constellation FM roles, Discovery/New Frontiers mission reviews (3) Potential Technology solutions . New approaches could avoid many current pitfalls (3a) New FM architectures, including model ]based approach integrated with NASA fs MBSE efforts (3b) NASA fs Office of the Chief Technologist: FM identified in seven of NASA fs 14 Space Technology Roadmaps . opportunity to coalesce and establish thrust area to progressively develop new FM techniques FM Handbook will help ensure that future missions do not encounter same FM ]related problems as previous missions Version 1 of the FM Handbook is a good start.
The NPOESS Preparatory Project (NPP) mission is scheduled to launch in the fall of 2011. Although several teams from the government and the instrument contractor will be assessing and characterizing the performance of the Advanced Technology Microwave Sounder (ATMS) and the Cross-track Infrared Sounder (CrIS) sounding suite, the NASA NPP Science Team will be paying particular attention to the aspects of these sensors that affect their utility for atmospheric and climate research. In this talk we discuss relevant aspects of ATMS and our post launch analysis approach.
This paper describes operations and procedures envisioned for NASA s Air Traffic Management (ATM) Technology Demonstration #1 (ATD-1). The ATD-1 Concept of Operations (ConOps) demonstration will integrate three NASA technologies to achieve high throughput, fuel-efficient arrival operations into busy terminal airspace. They are Traffic Management Advisor with Terminal Metering (TMA-TM) for precise time-based schedules to the runway and points within the terminal area, Controller-Managed Spacing (CMS) decision support tools for terminal controllers to better manage aircraft delay using speed control, and Flight deck Interval Management (FIM) avionics and flight crew procedures to conduct airborne spacing operations. The ATD-1 concept provides de-conflicted and efficient operations of multiple arrival streams of aircraft, passing through multiple merge points, from top-of-descent (TOD) to touchdown. It also enables aircraft to conduct Optimized Profile Descents (OPDs) from en route altitude to the runway, using primarily speed control to maintain separation and schedule. The ATD-1 project is currently addressing the challenges of integrating the three technologies, and implantation into an operational environment. Goals of the ATD-1 demonstration include increasing the throughput of high-density airports, reducing controller workload, increasing efficiency of arrival operations and the frequency of trajectory-based operations, and promoting aircraft ADS-B equipage.
This document is an update to the operations and procedures envisioned for NASA s Air Traffic Management (ATM) Technology Demonstration #1 (ATD-1). The ATD-1 Concept of Operations (ConOps) integrates three NASA technologies to achieve high throughput, fuel-efficient arrival operations into busy terminal airspace. They are Traffic Management Advisor with Terminal Metering (TMA-TM) for precise time-based schedules to the runway and points within the terminal area, Controller-Managed Spacing (CMS) decision support tools for terminal controllers to better manage aircraft delay using speed control, and Flight deck Interval Management (FIM) avionics and flight crew procedures to conduct airborne spacing operations. The ATD-1 concept provides de-conflicted and efficient operations of multiple arrival streams of aircraft, passing through multiple merge points, from top-of-descent (TOD) to the Final Approach Fix. These arrival streams are Optimized Profile Descents (OPDs) from en route altitude to the runway, using primarily speed control to maintain separation and schedule. The ATD-1 project is currently addressing the challenges of integrating the three technologies, and their implantation into an operational environment. The ATD-1 goals include increasing the throughput of high-density airports, reducing controller workload, increasing efficiency of arrival operations and the frequency of trajectory-based operations, and promoting aircraft ADS-B equipage.
The Software Developer's Assistant (SDA) helps software teams more efficiently and accurately conduct or execute software processes associated with NASA mission-critical software. SDA is a process enactment platform that guides software teams through project-specific standards, processes, and procedures. Software projects are decomposed into all of their required process steps or tasks, and each task is assigned to project personnel. SDA orchestrates the performance of work required to complete all process tasks in the correct sequence. The software then notifies team members when they may begin work on their assigned tasks and provides the tools, instructions, reference materials, and supportive artifacts that allow users to compliantly perform the work. A combination of technology components captures and enacts any software process use to support the software lifecycle. It creates an adaptive workflow environment that can be modified as needed. SDA achieves software process automation through a Business Process Management (BPM) approach to managing the software lifecycle for mission-critical projects. It contains five main parts: TieFlow (workflow engine), Business Rules (rules to alter process flow), Common Repository (storage for project artifacts, versions, history, schedules, etc.), SOA (interface to allow internal, GFE, or COTS tools integration), and the Web Portal Interface (collaborative web environment
The purpose of the Sentiment of Search Study for NASA Johnson Space Center (JSC) is to gain insight into the intranet search environment. With an initial usability survey, the authors were able to determine a usability score based on the Systems Usability Scale (SUS). Created in 1986, the freely available, well cited, SUS is commonly used to determine user perceptions of a system (in this case the intranet search environment). As with any improvement initiative, one must first examine and document the current reality of the situation. In this scenario, a method was needed to determine the usability of a search interface in addition to the user's perception on how well the search system was providing results. The use of the SUS provided a mechanism to quickly ascertain information in both areas, by adding one additional open-ended question at the end. The first ten questions allowed us to examine the usability of the system, while the last questions informed us on how the users rated the performance of the search results. The final analysis provides us with a better understanding of the current situation and areas to focus on for improvement. The power of search applications to enhance knowledge transfer is indisputable. The performance impact for any user unable to find needed information undermines project lifecycle, resource and scheduling requirements. Ever-increasing complexity of content and the user interface make usability considerations for the intranet, especially for search, a necessity instead of a 'nice-to-have'. Despite these arguments, intranet usability is largely disregarded due to lack of attention beyond the functionality of the infrastructure (White, 2013). The data collected from users of the JSC search system revealed their overall sentiment by means of the widely-known System Usability Scale. Results of the scores suggest 75%, +/-0.04, of the population rank the search system below average. In terms of a grading scaled, this equated to D or lower. It is obvious JSC users are not satisfied with the current situation, however they are eager to provide information and assistance in improving the search system. A majority of the respondents provided feedback on the issues most troubling them. This information will be used to enrich the next phase, root cause analysis and solution creation.