Search NASA⌕ Search

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.

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

At least 19 records

Record Management and Design Reuse

Government mandated records management requirements apply to retention and long term archival of a wide variety of records. Part of the attention is on permanent accession and retention by the U.S. National Archives and Records Administration (NARA) but interim requirements for storage by the source agency are included. As government agencies and the Department of Defense move toward implementations, additional goals often include saving design data for reuse. This paper briefly reviews the government records management requirements then investigates candidate meanings of 'reuse' and proposes an enhanced design records retention approach. The recommended strategy that emerges is, for a given program or product family, to invest in rich and readily re-executable preservation of design artifacts for one or two subsequent generations, then downgrade the data in utility through conversions, ultimately reaching the NARA minimum standard for permanent historical-interest archives.

permanent accession↗

NASA Taxonomy 2.0 Project Overview

This viewgraph presentation reviews the project to develop a Taxonomy for NASA. The benefits of this project are: Make it easy for various audiences to find relevant information from NASA programs quickly, specifically (1) Provide easy access for NASA Web resources (2) Information integration for unified queries and management reporting ve search results targeted to user interests the ability to move content through the enterprise to where it is needed most (3) Facilitate Records Management and Retention Requirements. In addition the project will assist NASA in complying with E-Government Act of 2002 and prepare NASA to participate in federal projects.

taxonomy↗

EDOS Evolution to Support NASA Future Earth Sciences Missions

This paper presents a ground system architecture to service future NASA decadal missions and in particular, the high rate science data downlinks, by evolving EDOS current infrastructure and upgrading high rate network lines. The paper will also cover EDOS participation to date in formulation and operations concepts for the respective missions to understand the particular mission needs and derived requirements such as data volumes, downlink rates, data encoding, and data latencies. Future decadal requirements such as onboard data recorder management and file protocols drive the need to emulate these requirements within the ground system. The EDOS open system modular architecture is scalable to accommodate additional missions using the current sites antennas and future sites as well and meet the data security requirements and fulfill mission's objectives

Cordier, Guy R.↗

SSC OCIO, IT SUMMIT 2011

The Stennis Space Center (SSC) Records Retention Facility is a centralized location for all SSC records, Records Management staff, and the SSC History Office. The building is a storm resistant facility and provides a secure environment for records housing. The Records Retention Facility was constructed in accordance with The National Archives and Records Administration (NARA) requirements for records storage, making it the first NARA compliant facility in the agency. Stennis Space Center's Records Retention Facility became operational in May 2010. The SSC Records Retention Facility ensures that the required federal records are preserved, managed and accessible to all interested personnel. The facility provides 20,000 cubic feet of records storage capacity for the purpose of managing the centers consolidated records within a central, protected environment. Records housed in the facility are in the form of paper, optical, film and magnetic media. Located within the SSC Records Retention Facility, the Records Management Office provides comprehensive records management services in the form of: a) Storage and life-cycle management of inactive records of all media types; b) Digitizing/scanning of records and documents; c) Non-textual/digital electronic records media storage, migration and transfer; d) Records Remediation.

Cottrell, Dinna L.↗

Data Integrity Challenges in NASA Giovanni

The Geospatial Interactive Online Visualization ANd aNalysis Infrastructure (Giovanni) is an online tool developed by the NASA Goddard Earth Sciences (GES) Data and Information Services Center (DISC), one of 12 NASA Science Mission Directorate Data Centers (DAACs) to analyze and visualize NASA remote sensing and model data without downloading data and software. As of this writing, over 2000 Earth satellite and model variables are available in Giovanni, including several well-known NASA satellite missions (e.g., TRMM, GPM) and projects (e.g., MERRA-2, GPCP). There are twenty-two plots provided by Giovanni that can be used to analyze, compare, and explore Earth data across disciplines. Results can be shared with colleagues and downloaded for further analysis. Giovanni has helped publish over 3000 referral papers over the years. As open science policies roll in, data integrity has become a major challenge for Giovanni and other tools. For integrity, both data and workflows must be transparent. FAIR-compliant data, including input, intermediate, and result products, as well as their associated statistics, metadata, and information, are needed. The NASA Data Product Development Guide for Data Producers provides a key resource on how to develop FAIR-compliant data products. Data quality information is also needed from data producers and analysis services like Giovanni. The workflow part is quite challenging and requires workflow management improvements, such as recording workflows and making them available to users. In this presentation, we will discuss the data integrity challenges in Giovanni.

data analysis, visualization↗

CARETS: A prototype regional environmental information system. Volume 3: Toward a national land use information system

It is recommended that a national land use information system be established by an agency of the Federal Government. This recommendation comes at a time of increasing demand for scientific information in support of environmentally relevant land use planning and management at all levels of government. It is also a time when new airborne and spaceborne remote sensors, tested in cooperation with the National Aeronautics and Space Administration (NASA) and the Earth Resources Observation Systems (EROS) Program of the Department of the Interior, make possible the gathering of land use information rapidly and on an unprecedented scale. Furthermore, information handling technology is developing toward a capability to receive, store, and disseminate the huge quantities of data that would be involved. The recommendation for the national land use information system is based upon careful analysis of the results of remote sensing experiments funded by NASA, EROS, and the Geography Program of the Geological Survey, with specific examples drawn from the demonstration project known as the Central Atlantic Regional Ecological Test Site (CARETS). CARETS is cast in the framework of a regional land use information system, channeling the flow bf information generated in response to users' declaration of their needs, through stages dealing with remote sensing data gathering systems, data processing and land mensuration, calibration in-terms of environmental impact, and evaluation with feedback from users. The proposed system would develop and implement a unified approach to the description and interpretation of the changing uses of the nation's land resources, building upon the base of interagency and intergovernmental cooperation already achieved in the experimental work to date. The land use data base that is being derived from high-altitude aerial color infrared photography would be the initial component of the recommended system. High-altitude photographic coverage would immediately be extended to as much of the nation as possible as technological developments and economic considerations permit. The system would later expand to include multiple-sensor, multiple-platform data sources. Six system characteristics are recommended: (1) High capacity storage of data available for quick retrieval, inexpensive processing, and update, (2) provision of accuracy appropriate to the scale of survey or to the level of detail dictated by different types of management and decision requirements; (3) permanent, publicly accessible sensor records for historical interpretation; (4) compatibility of the recording, storage, and retrieval system with all types of inputs, from ground observer to satellite; (5) products of diverse formats and scales, responsive to user feedback; (6) and standardization of formats, scales, and storage inputs to permit nationwide comparability.

Land use mapping↗

Records Management: Preserving the Past to Make the Future

As an intern in the Records Management Office at NASA, I have learned the importance of records management and teamwork. I work in building 60 with Kevin Coleman, the Records and Forms Manager and History Officer, and Deborah Demaline, the senior records specialist. Prior to my internship, I had never paid attention to records and their role in operating a business. However, after my first assignment of identifying files and filling out a C-277 form, I realized the importance of preserving each file. Since NASA is a government agency, keeping our records in a safe and easily accessible area is a major priority. As the records have accumulated over the years, and the destruction of records has been put on hold due to the fairly recent tobacco litigation; the amount of NASA s records has been quickly accumulating. Currently, our records are stored at Plum Brook in Sandusky, Ohio. Recently, rain has leaked through the bunkers and caused damage to some of our records boxes. Plum Brook has been experiencing difficulty in finding the funds to repair the damage. NASA Glenn is reluctant to give Plum Brook more money because the staff at the Sandusky site has not shown us a detailed summary of what they are doing with the funds we give them annually. Even though storing our records at Plum Brook comes with little cost, there are plenty other companies that offer a records storage area and a special software database for easy record retrieval. My assignment is to do a feasibility study on these companies to see how they compare in providing the appropriate criteria for NASA Glenn's needs. Other research I am doing is on which companies will allow us to convert our physical records into an electronic database for quicker retrieval and to eliminate the cost of storing our records in a facility altogether. The two studies have required me to not only work closely with the Records Management Department, but also the Information Technology staff. It has been important for me to thoroughly understand the criteria both departments here at NASA Glenn need in order to make the system effective for the entire organization. The interaction that I am experiencing with different organizations within NASA Glenn and the various companies we are looking at has enhanced my communication skills. Without proficient communication skills, it is difficult to seek how each company meets all of NASA's standards. This includes webx conferences, teleconferences, face-to-face meetings, knowing the appropriate time to ask questions, knowing what those appropriate questions are, and most importantly, being a good listener. During the meetings and conferences I attend, I ensure that I understand where each party is coming from and listen carefully to the points people make. In addition to working with the feasibility study, I will later work on a marketing plan to encourage employees to take care in storing their records and learn the importance of the History Office. Also, the department is trying to develop a special presentation for new employees during their orientation. Assisting Deborah Demaline in taking inventory at Plum Brook is another task that must be done to ensure that the records have been properly placed.

Petro, Kathryn↗

Research Opportunities in Nutrition and Metabolism in Space

The objectives of the Life Sciences Research Office (LSRO) study on nutrient requirements for meeting metabolic needs in manned space flights are as follows: review extant knowledge on the subject; identify significant gaps in knowledge; formulate suggestions for possible research; and produce a documented report of the foregoing items that can be used for program planning. In accordance with NASA's request for this study, the report focuses on issues of nutrition and metabolism that relate primarily to the contemplated United States Space Station, secondarily to the Shuttle Program as an orbital test bed for operational studies, and incidentally to scenarios for future long-term space flights. Members of the LSRO ad hoc Working Group on Nutrition and Metabolism were provided with pertinent articles and summaries on the subject. At the meeting of the Working Group, presentations were made by NASA Headquarters program staff on past experiences relative to space-flight nutrition and metabolism, as well as scenarios for future flights. The discussions of the ad hoc Working Group focused on the following: (1) metabolic needs related to work and exercise; (2) nutrients required to meet such needs; (3) food types, management, and records; and (4) nutritional amelioration or prevention of space-related physiological and behavioral changes.

Altman, Philip L.↗

NASA Software Documentation Standard

The NASA Software Documentation Standard (hereinafter referred to as "Standard") is designed to support the documentation of all software developed for NASA; its goal is to provide a framework and model for recording the essential information needed throughout the development life cycle and maintenance of a software system. The NASA Software Documentation Standard can be applied to the documentation of all NASA software. The 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. The 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↗

Automation of Hubble Space Telescope Mission Operations

On June 13, 2011, after more than 21 years, 115 thousand orbits, and nearly 1 million exposures taken, the operation of the Hubble Space Telescope successfully transitioned from 24x7x365 staffing to 815 staffing. This required the automation of routine mission operations including telemetry and forward link acquisition, data dumping and solid-state recorder management, stored command loading, and health and safety monitoring of both the observatory and the HST Ground System. These changes were driven by budget reductions, and required ground system and onboard spacecraft enhancements across the entire operations spectrum, from planning and scheduling systems to payload flight software. Changes in personnel and staffing were required in order to adapt to the new roles and responsibilities required in the new automated operations era. This paper will provide a high level overview of the obstacles to automating nominal HST mission operations, both technical and cultural, and how those obstacles were overcome.

Burley, Richard↗

The Challenges of Releasing Human Data for Analysis

The NASA Johnson Space Center s (NASA JSC) Committee for the Protection of Human Subjects (CPHS) recently approved the formation of two human data repositories: the Lifetime Surveillance of Astronaut Health Repository (LSAH-R) for clinical data and the Life Sciences Data Archive Repository (LSDA-R) for research data. The establishment of these repositories forms the foundation for the release of data and information beyond the scope for which the data was originally collected. The release of clinical and research data and information is primarily managed by two NASA groups: the Evidence Base Working Group (EBWG), consisting of members of both repositories, and the LSAH Policy Board. The goal of unifying these repositories and their processes is to provide a mutually supportive approach to handling medical and research data, to enhance the use of medical and research data to reduce risk, and to promote the understanding of space physiology, countermeasures and other mitigation strategies. Over the past year, both repositories have received over 100 data and information requests from a wide variety of requesters. The disposition of these requests has highlighted the challenges faced when attempting to make data collected on a unique set of subjects available beyond the original intent for which the data were collected. As the EBWG works through each request, many considerations must be factored into account when deciding what data can be shared and how - from the Privacy Act of 1974 and the Health Insurance Portability and Accountability Act (HIPAA), to NASA s Health Information Management System (10HIMS) and Human Experimental and Research Data Records (10HERD) access requirements. Additional considerations include the presence of the data in the repositories and vetting requesters for legitimacy of their use of the data. Additionally, fair access must be ensured for intramural, as well as extramural investigators. All of this must be considered in the formulation of the charters, policies and workflows for the human data repositories at NASA.

Fitts, Mary↗

NASA's EOSDIS, Trust and Certification

NASA's Earth Observing System Data and Information System (EOSDIS) has been in operation since August 1994, managing most of NASA's Earth science data from satellites, airborne sensors, filed campaigns and other activities. Having been designated by the Federal Government as a project responsible for production, archiving and distribution of these data through its Distributed Active Archive Centers (DAACs), the Earth Science Data and Information System Project (ESDIS) is responsible for EOSDIS, and is legally bound by the Office of Management and Budgets circular A-130, the Federal Records Act. It must follow the regulations of the National Institute of Standards and Technologies (NIST) and National Archive and Records Administration (NARA). It must also follow the NASA Procedural Requirement 7120.5 (NASA Space Flight Program and Project Management). All these ensure that the data centers managed by ESDIS are trustworthy from the point of view of efficient and effective operations as well as preservation of valuable data from NASA's missions. Additional factors contributing to this trust are an extensive set of internal and external reviews throughout the history of EOSDIS starting in the early 1990s. Many of these reviews have involved external groups of scientific and technological experts. Also, independent annual surveys of user satisfaction that measure and publish the American Customer Satisfaction Index (ACSI), where EOSDIS has scored consistently high marks since 2004, provide an additional measure of trustworthiness. In addition, through an effort initiated in 2012 at the request of NASA HQ, the ESDIS Project and 10 of 12 DAACs have been certified by the International Council for Science (ICSU) World Data System (WDS) and are members of the ICSUWDS. This presentation addresses questions such as pros and cons of the certification process, key outcomes and next steps regarding certification. Recently, the ICSUWDS and Data Seal of Approval (DSA) organizations merged their Core Trustworthy Data Repositories Requirements and require that members be recertified every three years. Given the rigor with which NASA manages the ESDIS Project and the DAACs, the recertification through WDSDSA, while involving some additional work, is a relatively simple process.

Certification↗

A data management system for weight control and design-to-cost

The definition of the mass properties data of aircraft changed on a daily basis as do design details of the aircraft. This dynamic nature of the definition has generally encouraged those responsible for the data to update the data on a weekly or monthly basis. The by-product of these infrequent updates was the requirement of manual records to maintain daily activity. The development of WAVES changed the approach to management of mass properties data. WAVES has given the ability to update the data on a daily basis thereby eliminating the need for manual records. WAVES has demonstrated that a software product can support a data management system for engineering data.

Bryant, J. C.↗

Spaceflight Ground Support Equipment Reliability & System Safety Data

Presented were Reliability Analysis, consisting primarily of Failure Modes and Effects Analysis (FMEA), and System Safety Analysis, consisting of Preliminary Hazards Analysis (PHA), performed to ensure that the CoNNeCT (Communications, Navigation, and Networking re- Configurable Testbed) Flight System was safely and reliably operated during its Assembly, Integration and Test (AI&T) phase. A tailored approach to the NASA Ground Support Equipment (GSE) standard, NASA-STD-5005C, involving the application of the appropriate Requirements, S&MA discipline expertise, and a Configuration Management system (to retain a record of the analysis and documentation) were presented. Presented were System Block Diagrams of selected GSE and the corresponding FMEA, as well as the PHAs. Also discussed are the specific examples of the FMEAs and PHAs being used during the AI&T phase to drive modifications to the GSE (via "redlining" of test procedures, and the placement of warning stickers to protect the flight hardware) before being interfaced to the Flight System. These modifications were necessary because failure modes and hazards were identified during the analysis that had not been properly mitigated. Strict Configuration Management was applied to changes (whether due to upgrades or expired calibrations) in the GSE by revisiting the FMEAs and PHAs to reflect the latest System Block Diagrams and Bill Of Material. The CoNNeCT flight system has been successfully assembled, integrated, tested, and shipped to the launch site without incident. This demonstrates that the steps taken to safeguard the flight system when it was interfaced to the various GSE were successful.

Fernandez, Rene↗

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↗

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.↗

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 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.↗