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 271 records · Page 15
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

Planetary Protection Compliance of NASA Missions Past, Present and Future

NASA monitors its spacecraft from a planetary protection (PP) perspective, to ensure contin-ued compliance with planetary protection requirements. This report to COSPAR on previous, ongoing and future missions will describe the issues and considerations regarding the PP im-plementation and compliance status of each mission, with changes noted as appropriate from previous reports. Missions not described in other presentations will be covered, including (but not limited to): Mars Odyssey, Mars Exploration Rovers, Mars Reconnaissance Orbiter, Escape and Plasma Acceleration and Dynamics Explorers (EscaPADE), Juno, New Horizons, Parker Solar Probe, Artemis I and its secondary payloads, and NASA partnered missions.

James Benardini↗
NASA NTRSDate not supplied

Planetary Protection Compliance Of NASA Missions Past, Present and Future

NASA monitors its spacecraft from a planetary protection (PP) perspective, to ensure continued compliance with planetary protection requirements. This report to COSPAR on previous, ongoing and future missions will describe the issues and considerations regarding the PP implementation and compliance status of each mission, with changes noted as appropriate from previous reports. Missions not described in other presentations will be covered, including (but not limited to): Mars Odyssey, Mars Reconnaissance Orbiter, Escape and Plasma Acceleration and Dynamics Explorers (EscaPADE), Juno, New Horizons, Parker Solar Probe, Dragonfly, Artemis I and its secondary payloads, and NASA partnered missions.

NASA↗
NASA NTRS2008

Best Practices for Researching and Documenting Lessons Learned

Identification, resolution, and avoidance of technical and programmatic issues are important for ensuring safe and successful space missions. Although the importance of applying lessons learned to reduce risk is frequently stressed, there is little material available to help technical and management personnel research and document lessons learned. Collecting, researching, identifying, and documenting lessons learned that will be useful to current and future management and engineering personnel is not always a straightforward task. This white paper presents lessons learned and best practices concerning the research and documentation of technical and organizational lessons learned. It is intended to enable organizations to initiate or improve lessons learned research and documentation efforts. The content of this white paper is based on four technical lessons learned projects conducted by the United Space Alliance (USA) Flight Design and Dynamics Department, in support of the NASA/Johnson Space Center (JSC) Flight Design and Dynamics Division. Each project published a report, titled as follows: (1) GPS Lessons Learned From the ISS, Space Shuttle and X-38; (2) Lessons Learned From Seven Space Shuttle Missions; (3) Space Shuttle Rendezvous and Proximity Operations Experience Report; and (4) Navigation Technical History with Lessons Learned. The four projects were different in availability of subject matter experts and primary source material, subject scope, and the level of effort required to produce the final report. However, generic lessons can be drawn from all of them. The best practices will be discussed by the phases of report research and development: (1) Defining Report Requirements, Project Organization, and Schedule; (2) Collection and Analysis of Source Material; (3) Writing and Integrating the Report; and (4) Review and Revision of the Report.

Goodman, John L.↗
NASA NTRS1975

An early glimpse at long-term subsonic commercial turbofan technology requirements

This paper reports on the exploratory investigation and initial findings of the study of future turbofan concepts to conserve fuel. To date, these studies have indicated a potential reduction in cruise thrust specific fuel consumption in 1990 turbofans of approximately 15% relative to present day new engines through advances in internal aerodynamics, structure-mechanics, and materials. Advanced materials also offer the potential for fuel savings through engine weight reduction. Further studies are required to balance fuel consumption reduction with sound airlines operational economics.

Gray, D. E.↗
NASA NTRS1968

Development requirements for a high-energy hybrid propulsion system Final report

This document presents the development requirements, costs, and schedule for a high-energy upper-stage hybrid propulsion system. High energy is achieved through the use of a lithium fuel formulation (solid) and fluorinated oxidizer (liquid). The propulsion system contains 3 2OO lb of propellant and may be used as a terminal stage for Atlas/Centaur or DSV-3M Delta launch vehicle. A program to develop a fluorinated hybrid propulsion system could be initiated with little risk. An extensive investigation revealed that the technology required to develop most of the components has either been demonstrated or is in progress. Further, it was found that there were no areas of critical technology. The cost to develop a hybrid propulsion system to a status where it could be integrated into a flight-test stage is about $17 million. This cost does not include the development of the stage astrionics. Length of the total development program is 34 months. A total recurring cost of $381 600 was estimated for the first unit (less astrionics and fee). This includes purchased hard\rare, manufacturing, material, assembly, and test costs.

M.B. Adams↗
NASA NTRS2015

Why Don't They Just Give Us Money? Project Cost Estimating and Cost Reporting

Successful projects require an integrated approach to managing cost, schedule, and risk. This is especially true for complex, multi-year projects involving multiple organizations. To explore solutions and leverage valuable lessons learned, NASA's Virtual Project Management Challenge will kick off a three-part series examining some of the challenges faced by project and program managers when it comes to managing these important elements. In this first session of the series, we will look at cost management, with an emphasis on the critical roles of cost estimating and cost reporting. By taking a proactive approach to both of these activities, project managers can better control life cycle costs, maintain stakeholder confidence, and protect other current and future projects in the organization's portfolio. Speakers will be Doug Comstock, Director of NASA's Cost Analysis Division, Kristin Van Wychen, Senior Analyst in the GAO Acquisition and Sourcing Management Team, and Mary Beth Zimmerman, Branch Chief for NASA's Portfolio Analysis Branch, Strategic Investments Division. Moderator Ramien Pierre is from NASA's Academy for Program/Project and Engineering Leadership (APPEL).

Comstock, Douglas A.↗
NASA NTRS1978

Orbiting Deep Space Relay Station (ODSRS): DSN feasibility study report

Future tracking requirements and advantages over earth based stations justify the design of an orbiting, free flying very long base interferometry system to provide high resolution maps of celestial radio sources. Moderate technology development is required for the following: 30 meter to 60 meter diameter deployable parabolic antennas with less than 2 millimeters surface tolerance; a momentum wheel attitude control system with few arc/second accuracy; solar power design; a hydrogen maser atomic frequency standard; and the cryogenic receivers. The system must meet current Deep Space tracking capabilities as a minimum, and the technology must be compatible with system performance growth in the future. System lifetime must be ten years without major refurbishing.

Thornton, T.↗
NASA NTRS1980

The MOD-OA 200 kilowatt wind turbine generator design and analysis report

The project requirements, approach, system description, design requirements, design, analysis, system tests, installation safety considerations, failure modes and effects analysis, data acquisition, and initial performance for the MOD-OA 200 kw wind turbine generator are discussed. The components, the rotor, driven train, nacelle equipment, yaw drive mechanism and brake, tower, foundation, electrical system, and control systems are presented. The rotor includes the blades, hub and pitch change mechanism. The drive train includes the low speed shaft, speed increaser, high speed shaft, and rotor brake. The electrical system includes the generator, switchgear, transformer, and utility connection. The control systems are the blade pitch, yaw, and generator control, and the safety system. Manual, automatic, and remote control and Dynamic loads and fatigue are analyzed.

Andersen, T. S.↗
NASA NTRS1984

Impact of lunar and planetary missions on the space station: Preliminary STS logistics report

Space station requirements for lunar and planetary missions are discussed. Specific reference is made to projected Ceres and Kopff missions; Titan probes; Saturn and Mercury orbiters; and a Mars sample return mission. Such requirements as base design; station function; program definition; mission scenarios; uncertainties impact; launch manifest and mission schedule; and shuttle loads are considered. It is concluded that: (1) the impact of the planetary missions on the space station is not large when compared to the lunar base; (2) a quarantine module may be desirable for sample returns; (3) the Ceres and Kopff missions require the ability to stack and checkout two-stage OTVs; and (4) two to seven manweeks of on-orbit work are required of the station crew to launch a mission and, with the exception of the quarantine module, dedicated crew will not be required.

Source record↗
NASA NTRS1989

Preliminary design of a lunar construction utility vehicle

Construction of a lunar base, prior to manned occupancy, is one of the most demanding technological challenges facing space system designers today. A flexible lunar construction machine is needed that can be operated remotely and that can perform a variety of construction tasks over a wide range of lunar conditions. A preliminary lunar construction utility vehicle (LCUV) design has been developed as part of a capstone design course at Old Dominion University and is described in this summary report. The design requirements are taken from a 1988 USRA Summer Design Report entitled The Lunar Split Mission: A Robotic Constructed Lunar Base Scenario, and from the proceedings of a workshop hosted by United Technologies Corporation entitled Report of the In Situ Resources Utilization Workshop. The first report describes a bootstrap base concept in which a minimum of essential surface elements are delivered and configured such that minimum EVA is required to bring the initial base on-line. The base is to be built in three phases, the first of which will be unmanned, while the second and third will be manned. The key to these concepts is the development of a semiautonomous, telerobotic lunar construction utility vehicle (LCUV). The tasks required of this robotic vehicle during the phase 1 build-up are as follows: (1) surface element transportation, handling, and assembly; (2) soil excavation and movement for site preparation; (3) radiation protection and materials processing; and (4) repair and maintenance of surface elements. In order to meet the stated requirements, the LCUV must be: (1) transformable to perform a wide variety of tasks; (2) self supporting; (3) designed to allow for telerobotic control as well as autonomous operation; (4) able to transport one fully configured space station common module (SSCM); (5) upgradable to allow for future growth; and (6) easy to maintain.

Bryant, C. A.↗
NASA NTRS1986

Requirements Analysis for Information-Intensive Systems

Report discusses role of requirements analysis in development of information-intensive systems. System examined from variety of human viewpoints during design, development, and implementation. Such examination, called requirements analysis, ensures system simultaneously meets number of distinct but interacting needs. Viewpoints defined and integrated to help attain objectives.

Callender, E. D.↗
NASA NTRS1997

Reuse of a Formal Model for Requirements Validation

This paper reports 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. Two levels of reuse are described here. First, a formally specified generic design model was generated on one project to systematically capture the design commonality in a set of software monitors on board a spacecraft. These monitors periodically check for faults and invoke recovery software when needed. The paper summarizes the use of the design model to validate the software design of the various monitors on that first project. Secondly, the paper describes how the formal design model created for the first project was reused on a second, subsequent project. The model was reused to validate the evolutionary requirements for the second project's software monitors, which were being developed in a series of builds. Some mismatches due to the very different architectures on the two projects suggested changes to make the model more generic. In addition, several advantages to the reuse of the first project's formal model on the second project are reported.

Lutz, Robyn R.↗