SEARCH · Search NASA

Results for “records management 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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 37 records · Page 2

All sources NASA NTRS DOE OSTI

NASA NTRS1991

NASA software documentation standard software engineering program

The NASA Software Documentation Standard (hereinafter referred to as Standard) can be applied to the documentation of all NASA software. This Standard is limited to documentation format and content requirements. It does not mandate specific management, engineering, or assurance standards or techniques. This Standard defines the format and content of documentation for software acquisition, development, and sustaining engineering. Format requirements address where information shall be recorded and content requirements address what information shall be recorded. This Standard provides a framework to allow consistency of documentation across NASA and visibility into the completeness of project documentation. This basic framework consists of four major sections (or volumes). The Management Plan contains all planning and business aspects of a software project, including engineering and assurance planning. The Product Specification contains all technical engineering information, including software requirements and design. The Assurance and Test Procedures contains all technical assurance information, including Test, Quality Assurance (QA), and Verification and Validation (V&V). The Management, Engineering, and Assurance Reports is the library and/or listing of all project reports.

Source record↗

NASA NTRS1976

Health-care district management information system plan: Review of operations analysis activities during calendar year 1975 and plan for continued research and analysis activities

Operations research activities developed to identify the information required to manage both the efficiency and effectiveness of the Veterans Administration (VA) health services as these services relate to individual patient care are reported. The clinical concerns and management functions that determine this information requirement are discussed conceptually. Investigations of existing VA data for useful management information are recorded, and a diagnostic index is provided. The age-specific characteristics of diseases and lengths of stay are explored, and recommendations for future analysis activities are articulated. The effect of the introduction of new technology to health care is also discussed.

Nielson, G. J.↗

NASA NTRS1991

Quality assurance planning for lunar Mars exploration

A review is presented of the tools and techniques required to meet the challenge of total quality in the goal of traveling to Mars and returning to the moon. One program used by NASA to ensure the integrity of baselined requirements documents is configuration management (CM). CM is defined as an integrated management process that documents and identifies the functional and physical characteristics of a facility's systems, structures, computer software, and components. It also ensures that changes to these characteristics are properly assessed, developed, approved, implemented, verified, recorded, and incorporated into the facility's documentation. Three principal areas are discussed that will realize significant efficiencies and enhanced effectiveness, change assessment, change avoidance, and requirements management.

Myers, Kay↗

NASA NTRS1990

GCS programmer's manual

A variety of instructions to be used in the development of implementations of software for the Guidance and Control Software (GCS) project is described. This document fulfills the Radio Technical Commission for Aeronautics RTCA/DO-178A guidelines, 'Software Considerations in Airborne Systems and Equipment Certification' requirements for document No. 4, which specifies the information necessary for understanding and programming the host computer, and document No. 12, which specifies the software design and implementation standards that are applicable to the software development and testing process. Information on the following subjects is contained: activity recording, communication protocol, coding standards, change management, error handling, design standards, problem reporting, module testing logs, documentation formats, accuracy requirements, and programmer responsibilities.

Lowman, Douglas S.↗

NASA NTRS2015

NASA Data Acquisition System Software Development for Rocket Propulsion Test Facilities

Current NASA propulsion test facilities include Stennis Space Center in Mississippi, Marshall Space Flight Center in Alabama, Plum Brook Station in Ohio, and White Sands Test Facility in New Mexico. Within and across these centers, a diverse set of data acquisition systems exist with different hardware and software platforms. The NASA Data Acquisition System (NDAS) is a software suite designed to operate and control many critical aspects of rocket engine testing. The software suite combines real-time data visualization, data recording to a variety formats, short-term and long-term acquisition system calibration capabilities, test stand configuration control, and a variety of data post-processing capabilities. Additionally, data stream conversion functions exist to translate test facility data streams to and from downstream systems, including engine customer systems. The primary design goals for NDAS are flexibility, extensibility, and modularity. Providing a common user interface for a variety of hardware platforms helps drive consistency and error reduction during testing. In addition, with an understanding that test facilities have different requirements and setups, the software is designed to be modular. One engine program may require real-time displays and data recording; others may require more complex data stream conversion, measurement filtering, or test stand configuration management. The NDAS suite allows test facilities to choose which components to use based on their specific needs. The NDAS code is primarily written in LabVIEW, a graphical, data-flow driven language. Although LabVIEW is a general-purpose programming language; large-scale software development in the language is relatively rare compared to more commonly used languages. The NDAS software suite also makes extensive use of a new, advanced development framework called the Actor Framework. The Actor Framework provides a level of code reuse and extensibility that has previously been difficult to achieve using LabVIEW. The

Herbert, Phillip W., Sr.↗

NASA NTRS1992

Information Management for a Large Multidisciplinary Project

In 1989, NASA's Langley Research Center (LaRC) initiated the High-Speed Airframe Integration Research (HiSAIR) Program to develop and demonstrate an integrated environment for high-speed aircraft design using advanced multidisciplinary analysis and optimization procedures. The major goals of this program were to evolve the interactions among disciplines and promote sharing of information, to provide a timely exchange of information among aeronautical disciplines, and to increase the awareness of the effects each discipline has upon other disciplines. LaRC historically has emphasized the advancement of analysis techniques. HiSAIR was founded to synthesize these advanced methods into a multidisciplinary design process emphasizing information feedback among disciplines and optimization. Crucial to the development of such an environment are the definition of the required data exchanges and the methodology for both recording the information and providing the exchanges in a timely manner. These requirements demand extensive use of data management techniques, graphic visualization, and interactive computing. HiSAIR represents the first attempt at LaRC to promote interdisciplinary information exchange on a large scale using advanced data management methodologies combined with state-of-the-art, scientific visualization techniques on graphics workstations in a distributed computing environment. The subject of this paper is the development of the data management system for HiSAIR.

Kennie H Jones↗

DOE OSTI2022

Corrective Action Unit 98: Frenchman Flat Five-Year Evaluation Nevada National Security Site, Nevada (Revision 1)

The Corrective Action Unit (CAU) 98, Frenchman Flat (FF) Closure Report (CR) (NNSA/NFO, 2016) and its ensuing Records of Technical Change (ROTCs) (compiled in DOE/EMNV, 2019) required the U.S. Department of Energy (DOE), Environmental Management (EM) Nevada Program’s Underground Test Area (UGTA) Activity to collect data for five years to establish triggers for the monitoring network and analyze the monitoring points for viability in long-term monitoring. This document provides the results of the five-year evaluation and presents recommendations for future monitoring of CAU 98.

54 ENVIRONMENTAL SCIENCES↗

NASA NTRS1978

Mobile Phone Terminal

In the photo, an employee of a real estate firm is contacting his office by means of HICOM, an advanced central terminal for mobile telephones. Developed by the Orlando Division of Martin Marietta Aerospace, Orlando, Florida, and manufactured by Harris Corporation's RF Division, Rochester, N.Y., HICOM upgrades service to users, provides better system management to telephone companies, and makes more efficient use of available mobile telephone channels through a computerized central control terminal. The real estate man, for example, was able to dial his office and he could also have direct-dialed a long distance number. Mobile phones in most areas not yet served by HICOM require an operator's assistance for both local and long distance calls. HICOM improves system management by automatically recording information on all calls for accurate billing, running continual performance checks on its own operation, and reporting any malfunctions to a central office.

Source record↗

NASA NTRS2010

NASA Supportability Engineering Implementation Utilizing DoD Practices and Processes

The Ares I design and development program made the determination early in the System Design Review Phase to utilize DoD ILS and LSA approach for supportability engineering as an integral part of the system engineering process. This paper is to provide a review of the overall approach to design Ares-I with an emphasis on a more affordable, supportable, and sustainable launch vehicle. Discussions will include the requirements development, design influence, support concept alternatives, ILS and LSA planning, Logistics support analyses/trades performed, LSA tailoring for NASA Ares Program, support system infrastructure identification, ILS Design Review documentation, Working Group coordination, and overall ILS implementation. At the outset, the Ares I Project initiated the development of the Integrated Logistics Support Plan (ILSP) and a Logistics Support Analysis process to provide a path forward for the management of the Ares-I ILS program and supportability analysis activities. The ILSP provide the initial planning and coordination between the Ares-I Project Elements and Ground Operation Project. The LSA process provided a system engineering approach in the development of the Ares-I supportability requirements; influence the design for supportability and development of alternative support concepts that satisfies the program operability requirements. The LSA planning and analysis results are documented in the Logistics Support Analysis Report. This document was required during the Ares-I System Design Review (SDR) and Preliminary Design Review (PDR) review cycles. To help coordinate the LSA process across the Ares-I project and between programs, the LSA Report is updated and released quarterly. A System Requirement Analysis was performed to determine the supportability requirements and technical performance measurements (TPMs). Two working groups were established to provide support in the management and implement the Ares-I ILS program, the Integrated Logistics Support Working Group (ILSWG) and the Logistics Support Analysis Record Working Group (LSARWG). The Ares I ILSWG is established to assess the requirements and conduct, evaluate analyses and trade studies associated with acquisition logistic and supportability processes and to resolve Ares I integrated logistics and supportability issues. It established a strategic collaborative alliance for coordination of Logistics Support Analysis activates in support of the integrated Ares I vehicle design and development of logistics support infrastructure. A Joint Ares I - Orion LSAR Working Group was established to: 1) Guide the development of Ares-I and Orion LSAR data and serve as a model for future Constellation programs, 2) Develop rules and assumptions that will apply across the Constellation program with regards to the program's LSAR development, and 3) Maintain the Constellation LSAR Style Guide.

Smith, David A.↗

NASA NTRS2010

Database for Safety-Oriented Tracking of Chemicals

SafetyChem is a computer program that maintains a relational database for tracking chemicals and associated hazards at Johnson Space Center (JSC) by use of a Web-based graphical user interface. The SafetyChem database is accessible to authorized users via a JSC intranet. All new chemicals pass through a safety office, where information on hazards, required personal protective equipment (PPE), fire-protection warnings, and target organ effects (TOEs) is extracted from material safety data sheets (MSDSs) and recorded in the database. The database facilitates real-time management of inventory with attention to such issues as stability, shelf life, reduction of waste through transfer of unused chemicals to laboratories that need them, quantification of chemical wastes, and identification of chemicals for which disposal is required. Upon searching the database for a chemical, the user receives information on physical properties of the chemical, hazard warnings, required PPE, a link to the MSDS, and references to the applicable International Standards Organization (ISO) 9000 standard work instructions and the applicable job hazard analysis. Also, to reduce the labor hours needed to comply with reporting requirements of the Occupational Safety and Health Administration, the data can be directly exported into the JSC hazardous- materials database.

Stump, Jacob↗

DOE OSTI2026

Compliance of NNSS Activities with P322-4 Issues Management and NNSSWAC Requirements

The Institutional Quality and Performance Assurance Division's Quality Support Services Group conducted a surveillance of the compliance of Waste Management Program activities to Issues Management/Corrective Action requirements communicated in P322-4 and the Nevada National Security Site Waste Acceptance criteria (NNSSWAC). All corrective actions reviewed and records examined were found to be compliant with appropriate and relevant procedures. There were no Findings or Opportunities for Improvement noted.

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

NASA NTRS1997

Data management at Biosphere 2 center

Throughout the history of Biosphere 2, the collecting and recording of biological data has been sporadic. Currently no active effort to administer and record regular biological surveys is being made. Also, there is no central location, such as an on-site data library, where all records from various studies have been archived. As a research institute, good, complete data records are at the core of all Biosphere 2's scientific endeavors. It is therefore imperative that an effective data management system be implemented within the management and research departments as soon as possible. Establishing this system would require three general phases: (1) Design/implement a new archiving/management program (including storage, cataloging and retrieval systems); (2) Organize and input baseline and intermediate data from existing archives; and (3) Maintain records by inputting new data.

McCreary, Leone F.↗

DOE OSTI2026

Frontier Job-Centric Telemetry Dataset

Comprehensive analysis of high-performance computing (HPC) systems requires linking workload execution to system behavior. This kind of analysis is vital for diagnosing performance issues, managing capacity, detecting anomalous workloads, and understanding how applications interact with system hardware. This job-centric telemetry dataset unifies scheduler job records with node-level measurements, enabling direct association between workloads and their corresponding power, thermal, and performance characteristics. It contains sanitized, scheduler related metadata for 152,400 individual jobs that ran on the Frontier supercomputer and ended on selected days throughout 2024 and 2025, a subpopulation of ~6.8% of the total number of allocated jobs with non-zero run time on the system over that same period. Each is linked with files that contain telemetry time series records of the power utilization and temperature behavior of its allocated nodes and their processors during the run time of the job. Where available, a portion of the job files also contain network performance time series. Jobs are sampled from select days that reflect normal levels of user activity and possess job size distributions with large numbers of leadership class jobs (>20% of Frontier nodes). Jobs in this dataset attempt to best represent successful user workflows.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

NASA NTRS2002

Software Assists in Extensive Environmental Auditing

The Base Enivronmental Management System (BEMS) is a Web-based application program for managing and tracking audits by the Environmental Office of Stennis Space Center in conformity with standard 14001 of the International Organization for Standardization (ISO 14001). (This standard specifies requirements for an environmental-management system.) BEMS saves time by partly automating what were previously manual processes for creating audit checklists; recording and tracking audit results; issuing, tracking, and implementing corrective-action requests (CARs); tracking continuous improvements (CIs); and tracking audit results and statistics. BEMS consists on an administration module and an auditor module. As its name suggests, the administration module is used to administer the audit. It helps administrators to edit the list of audit questions; edit the list of audit locations; assign manditory questions to locations; track, approve, and edit CARs; and edit completed audits. The auditor module is used by auditors to perform audits and record audit results: It helps the auditors to create audit checklists, complete audits, view completed audits, create CARs, record and acknowledge CIs, and generate reports from audit results.

Callac, Christopher↗

NASA NTRS2002

Software Assists in Extensive Environmental Auditing

The Base Environmental Management System (BEMS) is a Web-based application program for managing and tracking audits by the Environmental Office of Stennis Space Center in conformity with standard 14001 of the International Organization for Standardization (ISO 14001). (This standard specifies requirements for an environmental-management system.) BEMS saves time by partly automating what were previously manual processes for creating audit checklists; recording and tracking audit results; issuing, tracking, and implementing corrective-action requests (CARs); tracking continuous improvements (CIs); and tracking audit results and statistics. BEMS consists of an administration module and an auditor module. As its name suggests, the administration module is used to administer the audit. It helps administrators to edit the list of audit questions; edit the list of audit locations; assign mandatory questions to locations; track, approve, and edit CARs; and edit completed audits. The auditor module is used by auditors to perform audits and record audit results: it helps the auditors to create audit checklists, complete audits, view completed audits, create CARs, record and acknowledge CIs, and generate reports from audit results.

Callac, Christopher↗

NASA NTRS2003

Software Assists in Extensive Environmental Auditing

Callac, Christopher↗

DOE OSTI2022

Nevada National Security Site Radiological Control Manual

Please have this STIP assigned, documented, and recorded in OSTI as Report Number DOE/NV/03624--0257 Revision 1 and Author as Radiological Control Managers' Council. This manual contains the radiological control requirements to be used for all radiological activities conducted by programs under the purview of the U.S. Department of Energy (DOE), National Nuclear Security Administration Nevada Field Office (NNSA/NFO). (Activities conducted under the purview of the U.S. Department of Energy, Office of Environmental Management Nevada[(EM Nevada] may require additional approval authorities as described in the EM Nevada Prime Contractor’s implementation plan.) Compliance with these requirements will ensure compliance with Title 10 Code of Federal Regulations (CFR) Part 835, “Occupational Radiation Protection.” This manual represents policies, guidelines, and best practices for implementing the DOE/NV/03624--0082, “Nevada National Security Site Radiation Protection Program,” (NNSS RPP) according to the requirements of 10 CFR 835.

61 RADIATION PROTECTION AND DOSIMETRY↗

DOE OSTI2025

A U.S. Scientific Community Vision for Sustained Earth Observations of Greenhouse Gases to Support Local to Global Action

Managing carbon stocks in the land, ocean, and atmosphere under changing climate requires a globally‐integrated view of carbon cycle processes at local and regional scales. The growing Earth Observation (EO) record is the backbone of this multi‐scale system, providing local information with discrete coverage from surface measurements and regional information at global scale from satellites. Carbon flux information, anchored by inverse estimates from spaceborne Greenhouse Gas (GHG) concentrations, provides an important top‐down view of carbon emissions and sinks, but currently lacks global continuity at assessment and management scales (<100 km). Partial‐column data can help separate signals in the boundary layer from the overlying atmosphere, providing an opportunity to enhance surface sensitivity and bring flux resolution down from that of column‐integrated data (100–500 km). Based on a workshop held in September 2024, the carbon cycle community envisions a carbon observation system leveraging GHG partial columns in the lower and upper troposphere to weave together information across scales from surface and satellite EO data, and integration of top‐down/bottom‐up analyses to link process understanding to global assessment.

Parazoo, Nicholas C. [California Institute of Tech↗