Search NASA⌕ Search

SEARCH · Search NASA

Results for “REPORTING REQUIREMENTS”

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.

At least 289 records · Page 16

Ground Systems Development Environment (GSDE) interface requirements and prototyping plan

This report describes the data collection and requirements analysis effort of the Ground System Development Environment (GSDE) Interface Requirements study. It identifies potential problems in the interfaces among applications and processors in the heterogeneous systems that comprises the GSDE. It describes possible strategies for addressing those problems. It also identifies areas for further research and prototyping to demonstrate the capabilities and feasibility of those strategies and defines a plan for building the necessary software prototypes.

Church, Victor E.↗

Microgravity Experiments Safety and Integration Requirements Document Tree

This report is a document tree of the safety and integration documents required to develop a space experiment. Pertinent document information for each of the top level (tier one) safety and integration documents, and their applicable and reference (tier two) documents has been identified. This information includes: document title, revision level, configuration management, electronic availability, listed applicable and reference documents, source for obtaining the document, and document owner. One of the main conclusions of this report is that no single document tree exists for all safety and integration documents, regardless of the Shuttle carrier. This document also identifies the need for a single point of contact for customers wishing to access documents. The data in this report serves as a valuable information source for the NASA Lewis Research Center Project Documentation Center, as well as for all developers of space experiments.

Hogan, Jean M.↗

Reuse of a Formal Model for Requirements Validation

This paper report experience from how a project engaged in the process of requirements analysis for evolutionary builds can reuse the formally specified design model produced for a similar, earlier project in the same domain.

requirements↗

Technology requirements for advanced earth orbital transportation systems. Volume 2: Summary report

The results of efforts to identify the technology requirements for advanced earth orbital transportation systems are reported. Topics discussed include: (1) design and definition of performance potential of vehicle systems, (2) advanced technology assessment, and (3) extended performance. It is concluded that the horizontal take-off concept is the most feasible system considered.

Hepler, A. K.↗

Development of optimized techniques and requirements for computer enhancement of structural weld radiographs. Volume 1: Technical report

A hardware and software specification covering requirements for the computer enhancement of structural weld radiographs was considered. Three scanning systems were used to digitize more than 15 weld radiographs. The performance of these systems was evaluated by determining modulation transfer functions and noise characteristics. Enhancement techniques were developed and applied to the digitized radiographs. The scanning parameters of spot size and spacing and film density were studied to optimize the information content of the digital representation of the image.

Adams, J. R.↗

Roadside tree/pole crash barrier field test

A series of tests was carried out to evaluate the performance of a crash barrier designed to protect the occupants of an automobile from serious injury. The JPL barrier design is a configuration of empty aluminum beverage cans contained in a tear-resistant bag which, in turn, is encased in a collapsible container made of plywood and steel. Tests were conducted with a driven vehicle impacting the barrier. The basic requirements of NCHRP Report 153 were followed except that speeds of 30 mph rather than 60 mph were used. Accelerometer readings on the driver's helmet showed that the driver was never subjected to dangerous decelerations, and never experienced more than temporary discomfort. Also, all of the requirements of the cited report were met. An extrapolation of data indicated that the JPL barrier installed in front of a tree or telephone pole along a roadside would also have met the requirements at a speed of 40 mph.

Wilson, A. H.↗

STARS - Supportability Trend Analysis and Reporting System for the National Space Transportation System

The concept, implementation, and long-range goals of a Supportability Trend Analysis and Reporting System (STARS) for the National Space Transportation System (NSTS) are discussed. The requirement was established as a direct result of the recommendations of the Rogers Commission investigation of the circumstances of the Space Shuttle Challenger accident. STARS outlines the requirements for the supportability-trend data collection, analysis, and reporting requirements that each of the project offices supporting the Space Shuttle are required to provide to the NSTS program office. STARS data give the historic and predictive logistics information necessary for all levels of NSTS management to make safe and cost-effective decisions concerning the smooth flow of Space Shuttle turnaround.

Graham, Leroy J.↗

Supporting Crew Autonomy in Deep Space Exploration: Preliminary Onboard Capability Requirements and Proposed Research Questions. Technical Report of the Autonomous Crew Operations Technical Interchange Meeting

Communication delays are a critical challenge posed by long duration deep space exploration. Space missions historically have relied on an ever-present Mission Control Center (MCC) to direct operations in near real-time. As unanticipated anomalies that defeat fault detection and resolution systems do arise, the lack of real-time communication will significantly weaken what the MCC support represents: a reliable safety net for the flight crew through its deep and diverse areas of expertise and investigative resources. As a consequence, future space vehicles and habitats need to be equipped with capabilities to support the flight crew to operate with little or no ground support. Considerations must be given to vehicle and mission designs that will fortify the traditionally ground-centered safety net and forge new support systems, when communication delays exist. In August 2018, NASA’s Human Research Program, through its Human Factors and Behavioral Performance Element, convened a Technical Interchange Meeting (TIM) on Autonomous Crew Operations at NASA Ames Research Center. The goal of the meeting was to gather input from NASA centers, industry, academia, and branches of the Department of Defense (DoD) to address how intelligent technologies can be applied to augment onboard capabilities to support crew anomaly response. The TIM featured 24 presentations by 29 speakers and hosted a total of 59 attendees, including 43 from 5 NASA centers (Ames, Johnson, Langley, Marshall, and Jet Propulsion Lab) and 4 from the DoD (3 from Army Research Lab and 1 from Naval Postgraduate School), with remaining attendees from academia (e.g., UC Davis, CMU) and industry (e.g., IBM, Siemens). Discussions were centered around three themes: standards and guidelines, lessons learned in analog environments, and technologies. To help provide a framework for discussion, a concept matrix describing anomaly response processes was created prior to the TIM (Figure 1, page 6). The matrix captures the steps involved (monitoring and detection, diagnosis, solution development and evaluation, solution implementation and verification, resolution documentation) as well as the resources and capabilities required to support these steps (data, knowledge, analysis, synthesis, resource management). A wallpaper size printout of the matrix was utilized at the TIM to solicit attendee inputs along the three themes; the activity garnered 108 submissions of ideas. Overall, what emerged from TIM discussions was a picture of mismatch between crew anomaly response needs and support that can be provided by existing intelligent technologies. The needs are broad, spanning multiple steps and processes/resources, with many of which lacking support from existing technologies, such as knowledge management throughout the steps of problem solving (especially in resolution documentation) and manpower management. The solutions provided by existing intelligent technologies are specific to the steps/processes that they are designed to support and constrained to solving only problems similar to those that have occurred before. What is lacking from technologies is typically made up by humans, specifically their complex critical thinking, creative problem solving, and domain expertise. In the end, the TIM highlighted the pressing need to support responses to onboard anomalies during autonomous crew operations, particularly those that have eluded the system tests, inspection, and other assurance processes. Such anomalies can potentially threaten crew and vehicle safety, as well as significantly impact overall operations with additional workload. These fairly rare events are difficult to anticipate and prepare for, given the state-of-the-art in intelligent technologies. This is true even for anomalies that stem from “unknown knowns”—cases in which there is sufficient external information to characterize the problem but the overall pattern fails to be recognized by the problem solver, or in which the internal knowledge needed to solve a problem is held tacitly and potentially accessible by the problem solver but not articulated. It follows that the ability to tackle anomalies lies not only with the availability of relevant information and knowledge but also their accessibility in times of need. To that end, we propose research questions along the following three broad themes: • How intelligent technologies can help make relevant knowledge and information available? • How intelligent technologies can help make relevant knowledge and information accessible? • How intelligent technologies can help support the crew operating as a team in anomaly response processes?

autonomous crew operations↗

Expert system verification and validation study. Phase 2: Requirements identification. Delivery 1: Updated survey report

The purpose is to report the state-of-the-practice in Verification and Validation (V and V) of Expert Systems (ESs) on current NASA and Industry applications. This is the first task of a series which has the ultimate purpose of ensuring that adequate ES V and V tools and techniques are available for Space Station Knowledge Based Systems development. The strategy for determining the state-of-the-practice is to check how well each of the known ES V and V issues are being addressed and to what extent they have impacted the development of Expert Systems.

Source record↗

PACE Technical Report Series, Volume 6: Data Product Requirements and Error Budgets Consensus Document

This chapter summarizes ocean color science data product requirements for the Plankton, Aerosol, Cloud,ocean Ecosystem (PACE) mission's Ocean Color Instrument (OCI) and observatory. NASA HQ delivered Level-1 science data product requirements to the PACE Project, which encompass data products to be produced and their associated uncertainties. These products and uncertainties ultimately determine the spectral nature of OCI and the performance requirements assigned to OCI and the observatory. This chapter ultimately serves to provide context for the remainder of this volume, which describes tools developed that allocate these uncertainties into their components, including allowable OCI systematic and random uncertainties, observatory geo location uncertainties, and geophysical model uncertainties.

Cetinic, Ivona↗

Development of Mirror Segments for the Constellation-X Observatory

As NASA's next major X-ray observatory, Constellation-X will have a photon collection area of 30,000 sq cm at 1 keV, which, after folding other instrumental responses, translates into an effective area of 15,000 sq cm. The observatory consists of four identical satellites each of which carries a spectroscopic X-ray telescope mirror assembly (SXT) that is 1.6 m in diameter and has a focal length of 10 m and a collection area of 7,500 sq cm at 1 keV and an angular resolution of 15 sec. HPD (half-power diameter) at the system level. Each mirror assembly consists of a large number of mirror segments precisely assembled together. Our development of the mirror segments is divided into two steps. The first one is to develop the basic approach and fabricate segments within the constraints of existing infrastructure to meet the angular resolution requirement, but not mirror segment size requirement. We have all but successfully completed this part of the development. We are now on the verge of going into the second step, that is to fabricate mirror segments of larger sizes to reduce the number of segments that have to be aligned and integrated. In this paper, we report on the requirements and the development status of the mirror segments. These assembly and other requirements of the SXT are reported elsewhere.

Zhang, W.↗

Guidance and control requirements for high-speed Rollout and Turnoff (ROTO)

This report defines the initial requirements for designing a research high-speed rollout and turnoff (ROTO) guidance and control system applicable to transport class aircraft whose purpose is to reduce the average runway occupancy time (ROT) for aircraft operations. The requirements will be used to develop a ROTO system for both automatic and manual piloted operation under normal and reduced visibility conditions. Requirements were determined for nose wheel/rudder steering, braking/reverse thrust, and the navigation system with the aid of a non-real time, three degree-of-freedom MD-11 simulation program incorporating airframe and gear dynamics. The requirements were developed for speeds up to 70 knots using 30 ft exit geometries under dry and wet surface conditions. The requirements were generated under the assumptions that the aircraft landing system meets the current Category III touchdown dispersion requirements and that aircraft interarrival spacing is 2 nautical miles. This effort determined that auto-asymmetric braking is needed to assist steering for aft center-of-gravity aircraft. This report shows various time-history plots of the aircraft performance for the ROTO operation. This effort also investigated the state-of-the-art in the measurement of the runway coefficient of friction for various runway conditions.

Goldthorpe, Steve H.↗

Thermal power systems small power systems application project: Siting issues for solar thermal power plants with small community applications

The siting issues associated with small, dispersed solar thermal power plants for utility/small community applications of less than 10 MWe are reported. Some specific requirements are refered to the first engineering experiment for the Small Power Systems Applications (SPSA) Project. The background for the subsequent issue discussions is provided. The SPSA Project and the requirements for the first engineering experiment are described, and the objectives and scope for the report as a whole. A overview of solar thermal technologies and some technology options are discussed.

Holbeck, H. J.↗

EG&G Florida, Inc., KSC base operations contractor Launch Readiness Assessment System

A computerized Launch Readiness Assessment System (LRAS) which compares 'current status' of readiness against the 'required status' of readiness for the Space Shuttle. The five subsystems of the LRAS are examined in detail. The LRAS Plan specifies the overall system requirements, procedures, and reports. The LRAS Manager drives the operation of the LRAS system. The Responding Units (RU) maintain support plans and procedures which specify the detail requirements for each mission or milestone. The Master Data Tables contain the milestone, responsible RU relationships, and requirements assessment categories. The LRAS Status System serves as the launch readiness assessment reporting system. The relationships between these subsystems are displayed in diagrams.

Geaslen, W. D.↗