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 343 records · Page 19

Developing NDE Techniques for Large Cryogenic Tanks - Year 2 Report

The Shuttle Program requires very large cryogenic ground storage tanks in which to store liquid oxygen and hydrogen. The existing Launch Complex-39 Pad tanks, which will be passed onto future launch programs, are over 40 years old and have received minimal refurbishment and only external inspections over the years. The majority of the structure is inaccessible without a full system drain of cryogenic liquid and insulation in the annular region. It was previously thought that there was a limit to the number of temperature cycles that the tanks could handle due to possible insulation compaction before undergoing a costly and time consuming complete overhaul; therefore the tanks were not drained and performance issues with these tanks, specifically the Pad B LH2 tank, were accepted. There is a need and an opportunity, as the Shuttle program ends and work to upgrade the launch pad progresses, to develop innovative non-destructive evaluation (NDE) techniques to analyze the current tanks. Techniques are desired that can aid in determining the extent of refurbishment required to keep the tanks in service for another 20+ years. A non-destructive technique would also be a significant aid in acceptance testing of new and refurbished tanks, saving significant time and money, if corrective actions can be taken before cryogen is introduced to the systems. Year one of this project concentrated on analysis of the current tanks located at LC-39 while cryogen was present. Year two of this project concentrated on analysis of detectable thermal variations on the outer surface of the tanks as the cryogen was drained and the inner vessel warmed to ambient conditions. Two techniques have been deployed in the field to monitor the tank. The first consisted of a displacement sensor to monitor for any expansions at the base of the tank during warm-up that could indicate a compaction issue with the insulation. The second technique was continued thermal monitoring of the tank through and after warm up. The indications noted in the thermal images were compared to bore-scope images of the annular region taken once the tank was inert and warmed to ambient conditions. Similar thermal imaging was performed on a smaller tank where an insulation void was induced to compare the effectiveness of thermal imagining on a different tank geometry.

Arens, Ellen↗

Quantifying VOC-Reaction Tracers, Ozone Production, and Continuing Aerosol Production Rates in Urban and Far-Downwind Atmospheres

We have found a surprisingly informative decomposition of the complex question of smoggy ozone production (basically, [HO2] in a more locally determined field of [NO]) in the process of linked investigations of modestly smoggy Eastern North America (by NASA aircraft, July 2004) and rather polluted Flushing, NYC (Queens College, July, 2001). In both rural and very polluted situations, we find that a simple contour graph parameterization of the local principal ozone production rate can be estimated using only the variables [NO] and j(sub rads) [HCHO]: Po(O3) = c (j(sub rads) [HCHO])(sup a) [HCHO](sup b). Here j(sub rads) is the photolysis of HCHO to radicals, presumably capturing many harder-UV photolytic processes and the principle ozone production is that due to HO2; mechanisms suggest that ozone production due to RO2 is closely correlated, often suggesting a limited range of different proportionality factors. The method immediately suggests a local interpretation for concepts of VOC limitation and NOx limitation. We believe that the product j(sub rads) [HCHO] guages the oxidation rate of observed VOC mixtures in a way that also provides [HO2] useful for the principle ozone production rate k [HO2] [NO], and indeed, all ozone chemical production. The success of the method suggests that dominant urban primary-HCHO sources may transition to secondary plume-HCHO sources in a convenient way. Are there other, simple, near-terminal oxidized VOC's which help guage ozone production and aerosol particle formation? Regarding particles, we report on, to the extent NASA Research resources allow, on appealing relationships between far-downwind (Atlantic PBL) HCHO and very fine aerosol (including sulfate. Since j(sub rads) [HCHO] provides a time-scale, we may understand distant-plume particle production in a more quantitative manner. Additionally we report on a statistical search in the nearer field for relationships between glyoxals (important near-terminal aromatic and isoprene reaction products) and aerosol production, looking for VOC's that might be most implicated. All three variables j(sub rads), [HCHO], and [NO] are relatively easily measured in widespread air pollution monitoring networks, and all are deducible form space-borne observations, though estimation of [NO] from [NO2] (the species observable from space) may require care. We report also on airborne and surface observations of HCHO, suggesting that concentrated (urban) and more diffuse (forest) sources may be distinguishable from space. The use of the 3.58 micron microwindow for HCHO remote sensing should allow much sharper resolution of HCHO than the UV. UV sensing requires large and expensive instruments, but even these seem justified since formaldehyde is so informative.

Chatfield, Robert↗

Satellite Power Systems (SPS) concept definition study, exhibit C. Volume 7: System/subsystem requirements data book

Volume 7 of the Satellite Power Systems (SPS) Concept Definition Study final report summarizes the basic requirements used as a guide to systems analysis and is a basis for the selection of candidate SPS point design(s). Initially, these collected data reflected the level of definition resulting from the evaluation of a broad spectrum of SPS concepts. As the various concepts matured these requirements were updated to reflect the requirements identified for the projected satellite system/subsystem point design(s). The identified subsystem/systems requirements are defined, and where appropriate, recommendations for alternate approaches which may represent improved design features are presented. A more detailed discussion of the selected point design(s) will be found in Volume 2 of this report.

Hanley, G. M.↗

Requirements for Large Eddy Simulation Computations of Variable-Speed Power Turbine Flows

Variable-speed power turbines (VSPTs) operate at low Reynolds numbers and with a wide range of incidence angles. Transition, separation, and the relevant physics leading to them are important to VSPT flow. Higher fidelity tools such as large eddy simulation (LES) may be needed to resolve the flow features necessary for accurate predictive capability and design of such turbines. A survey conducted for this report explores the requirements for such computations. The survey is limited to the simulation of two-dimensional flow cases and endwalls are not included. It suggests that a grid resolution necessary for this type of simulation to accurately represent the physics may be of the order of Delta(x)+=45, Delta(x)+ =2 and Delta(z)+=17. Various subgrid-scale (SGS) models have been used and except for the Smagorinsky model, all seem to perform well and in some instances the simulations worked well without SGS modeling. A method of specifying the inlet conditions such as synthetic eddy modeling (SEM) is necessary to correctly represent the inlet conditions.

Grid↗

Spaceborne computer executive routine functional design specification. Volume 2: Computer executive design for space station/base

The computer executive functional system design concepts derived from study of the Space Station/Base are presented. Information Management System hardware configuration as directly influencing the executive design is reviewed. The hardware configuration and generic executive design requirements are considered in detail in a previous report (System Configuration and Executive Requirements Specifications for Reusable Shuttle and Space Station/Base, 9/25/70). This report defines basic system primitives and delineates processes and process control. Supervisor states are considered for describing basic multiprogramming and multiprocessing systems. A high-level computer executive including control of scheduling, allocation of resources, system interactions, and real-time supervisory functions is defined. The description is oriented to provide a baseline for a functional simulation of the computer executive system.

Kennedy, J. R.↗

Data Requirement (DR) MA-03: Payload missions integration

Project management and payload integration requirements definition activities are reported. Mission peculiar equipment; systems integration; ground operations analysis and requirement definition; safety and quality assurance; and support systems development are examined for payloads planned for the following missions: EOM-1; SL-2; Sl-3 Astro-1; MSL-2; EASE/ACCESS; MPESS; and the middeck ADSF flight.

Source record↗

Modelling and Laboratory Testing of Particle Resuspension and Transport for the Assessment of Terrestrial-Borne Biological Contamination of the Samples on the Mars 2020 Mission

The Mars 2020 mission will land a rover on the surface of Mars that will acquire, encapsulate, and cache scientifically selected samples of martian material for possible return to Earth by a future mission. The samples will be individually encapsulated and sealed in sample tubes. Each sample, and therefore each sample tube, must be kept clean of viable organisms with a terrestrial origin, which may adhere to the rover on their own and/or on other non-biological particles. Therefore, contrary to previous missions to the Red Planet, Mars 2020 is subject to new and more stringent biological, organic and inorganic contamination requirements. This paper reports on the analyses and testing performed to assess the various vectors that can lead to the terrestrial-borne contamination of the samples, focusing on those that are predicted to be the larger contributors. Specifically, the contamination of the sample tubes is expected to be very small prior to the commencement of the mission’s science phase since these tubes are protected by so-called Fluid Mechanical Particle Barriers. Once on the surface of Mars however the sample tubes will be removed from their FMPBs and be subject to contamination from the rover. Of specific interest is the vector by which winds dislodge some particles from the surface of the rover and transport them to the surrounding soil. Naturally, such assessments require multi-disciplinary analyses involving at minimum the physics of particle adhesion and resuspension from surfaces, fluid mechanics and aerosols. Here we provide an overview of these models. We also report on particle resuspension experiments we have performed at the Jet Propulsion Laboratory to both guide and validate the aforementioned physics models.

Steltzner, Adam↗

Requirements, Verification, and Compliance (RVC) Database Tool

This paper describes the development, design, and implementation of the Requirements, Verification, and Compliance (RVC) database used on the International Space Welding Experiment (ISWE) project managed at Marshall Space Flight Center. The RVC is a systems engineer's tool for automating and managing the following information: requirements; requirements traceability; verification requirements; verification planning; verification success criteria; and compliance status. This information normally contained within documents (e.g. specifications, plans) is contained in an electronic database that allows the project team members to access, query, and status the requirements, verification, and compliance information from their individual desktop computers. Using commercial-off-the-shelf (COTS) database software that contains networking capabilities, the RVC was developed not only with cost savings in mind but primarily for the purpose of providing a more efficient and effective automated method of maintaining and distributing the systems engineering information. In addition, the RVC approach provides the systems engineer the capability to develop and tailor various reports containing the requirements, verification, and compliance information that meets the needs of the project team members. The automated approach of the RVC for capturing and distributing the information improves the productivity of the systems engineer by allowing that person to concentrate more on the job of developing good requirements and verification programs and not on the effort of being a "document developer".

Rainwater, Neil E., II↗

Apollo experience report guidance and control systems

The Apollo guidance and control systems for both the command module and the lunar module are described in a summary report. General functional requirements are discussed, and general functional descriptions of the various subsystems and their interfaces are provided. The differences between the original in-flight maintenance concept and the final lunar-orbital-rendezvous concept are discussed, and the background in philosophy, the system development, and the reasons for the change in concept are chronologically presented. Block diagrams showing the command module guidance and control system under each concept are included. Significant conclusions and recommendations contained in more detailed reports on specific areas of the guidance and control systems are included.

Wilson, R. E., Jr.↗

A hybrid finite element-boundary integral for the analysis of cavity-backed antennas of arbitrary shape

This is the final report on this project which was concerned with the analysis of cavity-backed antennas and more specifically spiral antennas. The project was a continuation of a previous analysis, which employed rectangular brick elements, and was, thus, restricted to planar rectangular patch antennas. A total of five reports were submitted under this project and we expect that at least four journal papers will result from the research described in these reports. The abstracts of the four previous reports are included. The first of the reports (028918-1-T) is over 75 pages and describes the general formulation using tetrahedral elements and the computer program. Report 028918-2-T was written after the completion of the computer program and reviews the capability of the analysis and associated software for planar circular rectangular patches and for a rectangular planar spiral. Measurements were also done at the University of Michigan and at Mission Research Corp. for the purpose of validating the software. We are pleased to acknowledge a partial support from Mission Research Corp. in carrying out the work described in this report. The third report (028918-3-T) describes the formulation and partial validation (using 2D data) for patch antennas on a circular platform. The 3D validation and development of the formulation for patch antennas on circular platforms is still in progress. The fourth report (028918-4-T) is basically an invited journal paper which will appear in the 'J. Electromagnetic Waves and Applications' in early 1994. It describes the application of the finite element method in electromagnetics and is primarily based on our work here at U-M. This final report describes the culmination of our efforts in characterizing complex cavity-backed antennas on planar platforms. The report describes for the first time the analysis of non-planar spirals and non-rectangular slot antennas as well as traditional planar patch antennas. The comparisons between measurements and calculations are truly impressive. Another unique aspect of this work is the incorporation of the FFT as part of the BiCG solver by overlaying a structured triangular mesh over the unstructured mesh. The implementation of this BiCG-FFT solution algorithm is important in minimizing the CPU and storage requirements. This final report will be submitted for publication in a refereed journal.

Gong, Jian↗

Countermeasure Evaluation and Validation Project (CEVP) Database Requirement Documentation

The initial focus of the project by the JSC laboratories will be to develop, test and implement a standardized complement of integrated physiological test (Integrated Testing Regimen, ITR) that will examine both system and intersystem function, and will be used to validate and certify candidate countermeasures. The ITR will consist of medical requirements (MRs) and non-MR core ITR tests, and countermeasure-specific testing. Non-MR and countermeasure-specific test data will be archived in a database specific to the CEVP. Development of a CEVP Database will be critical to documenting the progress of candidate countermeasures. The goal of this work is a fully functional software system that will integrate computer-based data collection and storage with secure, efficient, and practical distribution of that data over the Internet. This system will provide the foundation of a new level of interagency and international cooperation for scientific experimentation and research, providing intramural, international, and extramural collaboration through management and distribution of the CEVP data. The research performed this summer includes the first phase of the project. The first phase of the project is a requirements analysis. This analysis will identify the expected behavior of the system under normal conditions and abnormal conditions; that could affect the system's ability to produce this behavior; and the internal features in the system needed to reduce the risk of unexpected or unwanted behaviors. The second phase of this project have also performed in this summer. The second phase of project is the design of data entry screen and data retrieval screen for a working model of the Ground Data Database. The final report provided the requirements for the CEVP system in a variety of ways, so that both the development team and JSC technical management have a thorough understanding of how the system is expected to behave.

Shin, Sung Y.↗

Partitioning in Avionics Architectures: Requirements, Mechanisms, and Assurance

Automated aircraft control has traditionally been divided into distinct "functions" that are implemented separately (e.g., autopilot, autothrottle, flight management); each function has its own fault-tolerant computer system, and dependencies among different functions are generally limited to the exchange of sensor and control data. A by-product of this "federated" architecture is that faults are strongly contained within the computer system of the function where they occur and cannot readily propagate to affect the operation of other functions. More modern avionics architectures contemplate supporting multiple functions on a single, shared, fault-tolerant computer system where natural fault containment boundaries are less sharply defined. Partitioning uses appropriate hardware and software mechanisms to restore strong fault containment to such integrated architectures. This report examines the requirements for partitioning, mechanisms for their realization, and issues in providing assurance for partitioning. Because partitioning shares some concerns with computer security, security models are reviewed and compared with the concerns of partitioning.

Rushby, John↗

Cassini Orbit Determination Operations Through The Final Titan Flybys and The Mission Grand Finale (February 2016 - September 2017)

This paper reports on the orbit determination performance for the final 1.5 years of the Cassini Solstice mission, including the mission’s Grand Finale. During this period, Cassini encountered its final eleven targeted flybys of Titan (T116-T126) and executed its last 62 orbits of Saturn. In these final months, the spacecraft’s inclination was gradually raised from near equatorial to near 63 degrees, critical inclination, to prevent the line of apsides from rotating out of Titan’s orbital plane. Critical inclination enables continued Titan flybys, the last of which places Cassini on an impact trajectory with Saturn, thereby satisfying planetary protection requirements. In this reporting period, the orbit period moved from 16 days to nearly 32 and, for the final 6 months, it was brought down to less than 7 days. By design, the spacecraft entered the Saturn atmosphere on its final orbit and vaporized on September 15, 2017. We also report on the particular challenges associated with a stellar occultation, a flyby of Saturn’s rocks, and the last revolutions of the mission’s Grand Finale.

Criddle, Kevin↗

S&MA Internship to Support Orion and the European Service Module

As a University Space Research Association (USRA) intern for NASA Johnson Space Center (JSC) during the summer 2016 work term, I worked on three main projects for the Space Exploration Division (NC) of the Safety and Mission Assurance (S&MA) Directorate. I worked on all three projects concurrently. One of the projects involved facilitating the status and closure of technical actions that were created during European Service Module (ESM) safety reviews by the MPCV Safety & Engineering Review Panel (MSERP). The two main duties included accurately collecting and summarizing qualitative data, and communicating that information to the European Space Agency (ESA) and Airbus (ESA's prime contractor) in a clear, succinct and precise manner. This project also required that I create a report on the challenges and opportunities of international S&MA. With its heavy emphasis on soft skills, this project taught me how to communicate better, by showing me how to present and share information in an easy-to-read and understandable format, and by showing me how to cooperate with and culturally respect international partners on a technical project. The second project involved working with the Orion Thermal Protection System (TPS) Process Failure Modes and Effects Analysis (PFMEA) Working Group to create the first full version of the Orion TPS PFMEA. The Orion TPS PFMEA Working Group met twice a week to analyze the Avcoat block installation process for failure modes, the failure modes effects, and how such failure modes could be controlled. I was in charge of implementing changes that were discussed in meeting, but were not implemented real time. Another major task included creating a significant portion of the content alongside another team member outside the two weekly meetings. This project caused me to become knowledgeable about TPS, heatshields, space-rated manufacturing, and non-destructive evaluation (NDE). The project also helped me to become better at working with a small team and helped improved my technical communication skills. My main duty for the third project was creating a Safety Verification Tracking Log (SVTL) for the Orbital Maneuvering System Engine (OMS-E), and contacting subject matter experts to close Hazard Report (HR) control verifications. This project also required me to support other OMS-E safety process tasks, like monitoring OMS-E vibration testing for Quality Assurance (QA) purposes. This project helped me become even more proficient in Excel. Throughout the project, I gained knowledge about the OMS-E system and improved my understanding of pressure systems and propellant systems. In terms of education goals, this work term has affirmed my desire to take a few more space-related courses, like orbital mechanics, so that I can have a better understanding of human spaceflight and the industry surrounding it. However, the work term did not persuade me to pursue a master's degree. In terms of career goals, this work term has helped me clarify the direction I would like to head in the future. The perspective of three summer terms working for NASA in S&MA has allowed me to observe that most S&MA employees joined S&MA after working in other NASA directorates, such as Engineering or Flight Operations. It is my belief that it would be advantageous for both NASA and I for me to broaden my knowledge base and technical skill set by completing hands-on technical work on human spaceflight projects, and for me to integrate my safety experience directly into technical work in other directorates. The other significant advantage to this proposed situation is that if I were to eventually return to S&MA, I would be returning with a substantial set of hands-on technical experience and knowledge, which would be a significant resource for S&MA tasks and projects.

Hutcheson, Connor↗

Automated Medical Inventory System (AMIS) TechPort Entry

The current medical inventory paradigm on the International Space Station (ISS) requires crew to report use of medications and supplies to be manually decremented by ground teams. This method is not only tedious and time consuming for both the crew and ground teams but also results in inaccuracies in location and availability of medical supplies over time. Fortunately, the ISS is frequently resupplied by cargo launches and crew expeditions, and an accurate inventory count is less critical. However, for exploration missions, resupply will be greatly limited or unavailable entirely, and increasing communication latency will impair crew-ground communications. On longer missions, with large medical systems and time constrained crew, NASA needs a method of accurately managing medical inventory without reliance on ground teams and with as little crew time and effort as possible. The Exploration Medical Integrated Product Team (XMIPT) project called Medical Exploration Development and Implementation Scoping (MEDIScope) prepared a concept of operations and preliminary requirements for an Automated Medical Inventory System (AMIS) and completed a market survey and trade study of potential inventory management technologies in partnership with the market research firm, yet2. The products from the MEDIScope effort, including the market survey results, preliminary functional requirements and a concept of operations, have been handed off to a development team at Glenn Research Center (GRC) and ZIN Technologies for technology maturation. In the development phase, the AMIS team will finalize system requirements, down select technologies, integrate with a future exploration Crew Health and Performance Integrated Data Architecture, and conduct design reviews. The project will culminate in an ISS technical flight demonstration in FY27.

MEDIScope↗

Architecture and Information Requirements to Assess and Predict Flight Safety Risks During Highly Autonomous Urban Flight Operations

As aviation adopts new and increasingly complex operational paradigms, vehicle types, and technologies to broaden airspace capability and efficiency, maintaining a safe system will require recognition and timely mitigation of new safety issues as they emerge and before significant consequences occur. A shift toward a more predictive risk mitigation capability becomes critical to meet this challenge. In-time safety assurance comprises monitoring, assessment, and mitigation functions that proactively reduce risk in complex operational environments where the interplay of hazards may not be known (and therefore not accounted for) during design. These functions can also help to understand and predict emergent effects caused by the increased use of automation or autonomous functions that may exhibit unexpected non-deterministic behaviors. The envisioned monitoring and assessment functions can look for precursors, anomalies, and trends (PATs) by applying model-based and data-driven methods. Outputs would then drive downstream mitigation(s) if needed to reduce risk. These mitigations may be accomplished using traditional design revision processes or via operational (and sometimes automated) mechanisms. The latter refers to the ‘in-time’ aspect of the system concept. This report comprises architecture and information requirements and considerations toward enabling such a capability within the domain of low altitude highly autonomous urban flight operations. This domain may span, for example, public-use surveillance missions flown by small unmanned aircraft (e.g., infrastructure inspection, facility management, emergency response, law enforcement, and/or security) to transportation missions flown by larger aircraft that may carry passengers or deliver products. Caveat: Any stated requirements in this report should be considered initial requirements that are intended to drive research and development (R&D). These initial requirements are likely to evolve based on R&D findings, refinement of operational concepts, industry advances, and new industry or regulatory policies or standards related to safety assurance.

Young, Steven↗

Technology requirements for advanced earth orbital transportation systems. Volume 3: Summary report - dual mode propulsion

The impact of dual-mode propulsion on cost-effective technology requirements for advanced earth-orbital transportation systems is considered. Additional objectives were to determine the advantages of the best dual mode concept relative to the LO2/LH2 concept of the basic study. Normal technology requirements applicable to horizontal take-off and landing single-stage-to-orbit systems utilizing dual mode rocket propulsion were projected to the 1985 time period. These technology projections were then incorporated in a vehicle parametric design analysis for two different operational concepts of a dual mode propulsion system. The resultant performance, weights and costs of each concept were compared. The selected propulsion concept was evaluated to confirm the parametric trending/scaling of weights and to optimize the configuration.

Hepler, A. K.↗