Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Record Management”

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 55 records · Page 3
All sourcesNASA NTRSDOE OSTI
NASA NTRS2019

KSC Integration Office Internship Final Report

This report is a summary of the projects I undertook during this internship period. The objective and scope of each project are be described in detail, and a description of the procedures utilized to work on said projects are provided. The current standing and future work that needs to be done are also discussed for each respective project. Finally, to show the personal growth achieved during this period, a brief overview of other activities undertaken is provided, as well as a summary of important skills gained throughout this internship.

Documentation↗
NASA NTRS1993

A parallel data management system for large-scale NASA datasets

The past decade has experienced a phenomenal growth in the amount of data and resultant information generated by NASA's operations and research projects. A key application is the reprocessing problem which has been identified to require data management capabilities beyond those available today (PRAT93). The Intelligent Information Fusion (IIF) system (ROEL91) is an ongoing NASA project which has similar requirements. Deriving our understanding of NASA's future data management needs based on the above, this paper describes an approach to using parallel computer systems (processor and I/O architectures) to develop an efficient parallel database management system to address the needs. Specifically, we propose to investigate issues in low-level record organizations and management, complex query processing, and query compilation and scheduling.

Srivastava, Jaideep↗
NASA NTRS2002

High-Rate Communications Outage Recorder Operations for Optimal Payload and Science Telemetry Management Onboard the International Space Station

All International Space Station (ISS) Ku-band telemetry transmits through the High-Rate Communications Outage Recorder (HCOR). The HCOR provides the recording and playback capability for all payload, science, and International Partner data streams transmitting through NASA's Ku-band antenna system. The HCOR is a solid-state memory recorder that provides recording capability to record all eight ISS high-rate data during ISS Loss-of-Signal periods. NASA payloads in the Destiny module are prime users of the HCOR; however, NASDA and ESA will also utilize the HCOR for data capture and playback of their high data rate links from the Kibo and Columbus modules. Marshall Space Flight Center's Payload Operations Integration Center manages the HCOR for nominal functions, including system configurations and playback operations. The purpose of this paper is to present the nominal operations plan for the HCOR and the plans for handling contingency operations affecting payload operations. In addition, the paper will address HCOR operation limitations and the expected effects on payload operations. The HCOR is manifested for ISS delivery on flight 9A with the HCOR backup manifested on flight 11A. The HCOR replaces the Medium-Rate Communications Outage Recorder (MCOR), which has supported payloads since flight 5A.1.

Shell, Michael T.↗
NASA NTRS2002

Rapid Spacecraft Development: Results and Lessons Learned

The Rapid Spacecraft Development Office (RSDO) at NASA's Goddard Space Flight Center is responsible for the management and direction of a dynamic and versatile program for the definition, competition, and acquisition of multiple indefinite delivery and indefinite quantity contracts - resulting in a catalog of spacecraft buses. Five spacecraft delivery orders have been placed by the RSDO and one spacecraft has been launched. Numerous concept and design studies have been performed, most with the intent of leading to a future spacecraft acquisition. A collection of results and lessons learned is recorded to highlight management techniques, methods and processes employed in the conduct of spacecraft acquisition. Topics include working relationships under fixed price delivery orders, price and value, risk management, contingency reserves, and information restrictions.

Watson, William A.↗
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 NTRS1986

Verification of post permanently manned configuration Space Station elements

An account is given of the techniques and ground systems designed to fulfill post permanently manned configuration (PMC) Space Station verification tasks. Consideration is given to analysis using computer math models and computer-aided interface verification systems, testing using simulators and interface mixtures, and special inspection. It is noted that an initial Space Station design that accommodates and facilitates verification is crucial to an effective verification program as well as proper instrumentation, built-in test capability, and a precise configuration management, control and record system. It is concluded that post PMC verification should be accounted for both in the initial Space Station design and in the subsequent development of initial assembly flight verification techniques and capabilities.

Scully, E. J.↗
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 NTRS2014

Landsat-8: Science and Product Vision for Terrestrial Global Change Research

Landsat 8, a NASA and USGS collaboration, acquires global moderate-resolution measurements of the Earth's terrestrial and polar regions in the visible, near-infrared, short wave, and thermal infrared. Landsat 8 extends the remarkable 40 year Landsat record and has enhanced capabilities including new spectral bands in the blue and cirrus cloud-detection portion of the spectrum, two thermal bands, improved sensor signal-to-noise performance and associated improvements in radiometric resolution, and an improved duty cycle that allows collection of a significantly greater number of images per day. This paper introduces the current (2012-2017) Landsat Science Team's efforts to establish an initial understanding of Landsat 8 capabilities and the steps ahead in support of priorities identified by the team. Preliminary evaluation of Landsat 8 capabilities and identification of new science and applications opportunities are described with respect to calibration and radiometric characterization; surface reflectance; surface albedo; surface temperature, evapotranspiration and drought; agriculture; land cover, condition, disturbance and change; fresh and coastal water; and snow and ice. Insights into the development of derived 'higher-level' Landsat products are provided in recognition of the growing need for consistently processed, moderate spatial resolution, large area, long-term terrestrial data records for resource management and for climate and global change studies. The paper concludes with future prospects, emphasizing the opportunities for land imaging constellations by combining Landsat data with data collected from other international sensing systems, and consideration of successor Landsat mission requirements.

Landsat↗
NASA NTRSDate not supplied

A User-Focused Renovation of CERES Metadata

Production software and public data products for Clouds and the Earth’s Radiant Energy System (CERES) continue to evolve as the project extends its climate data record. The data management team for CERES is currently undertaking major renovations of both code and data products, the latter of which is, of course, in service of improving user experience. A major mode of CERES’ data product improvement is in renovating products’ metadata. Metadata standards have evolved since CERES began producing its data products in 2000. In its twentieth year, CERES essentially asked the question: how would the project design its data products if it could start all over again? With forthcoming editions, this rebirth will be realized. CERES has redesigned its metadata standards to best position itself for data discoverability. The project has used the latest standards being developed in NASA’s Earth Science Data and Information Systems (ESDIS) Project’s Unified Metadata Model (UMM) documentation; collaborated with the Atmospheric Science Data Center (ASDC) to ensure compliance with Common Metadata Repository compatibility, and continued compliance with Climate and Forecast (CF) Conventions. In doing so, the team created its own, internal document for proper metadata creation and metadata verification software that is deployed prior to all code deliveries. This presentation will discuss this redesign process, as well as needs met and those that are still outstanding in the search for an improved user experience with CERES data products.

Kathleen Dejwakh↗
NASA NTRS2011

Sptrace

Sptrace is a general-purpose space utilization tracing system that is conceptually similar to the commercial Purify product used to detect leaks and other memory usage errors. It is designed to monitor space utilization in any sort of heap, i.e., a region of data storage on some device (nominally memory; possibly shared and possibly persistent) with a flat address space. This software can trace usage of shared and/or non-volatile storage in addition to private RAM (random access memory). Sptrace is implemented as a set of C function calls that are invoked from within the software that is being examined. The function calls fall into two broad classes: (1) functions that are embedded within the heap management software [e.g., JPL's SDR (Simple Data Recorder) and PSM (Personal Space Management) systems] to enable heap usage analysis by populating a virtual time-sequenced log of usage activity, and (2) reporting functions that are embedded within the application program whose behavior is suspect. For ease of use, these functions may be wrapped privately inside public functions offered by the heap management software. Sptrace can be used for VxWorks or RTEMS realtime systems as easily as for Linux or OS/X systems.

Burleigh, Scott C.↗
NASA NTRS2008

Guidance and Control Software Project Data - Volume 4: Configuration Management and Quality Assurance Documents

The Guidance and Control Software (GCS) project was the last in a series of software reliability studies conducted at Langley Research Center between 1977 and 1994. The technical results of the GCS project were recorded after the experiment was completed. Some of the support documentation produced as part of the experiment, however, is serving an unexpected role far beyond its original project context. Some of the software used as part of the GCS project was developed to conform to the RTCA/DO-178B software standard, "Software Considerations in Airborne Systems and Equipment Certification," used in the civil aviation industry. That standard requires extensive documentation throughout the software development life cycle, including plans, software requirements, design and source code, verification cases and results, and configuration management and quality control data. The project documentation that includes this information is open for public scrutiny without the legal or safety implications associated with comparable data from an avionics manufacturer. This public availability has afforded an opportunity to use the GCS project documents for DO-178B training. This report provides a brief overview of the GCS project, describes the 4-volume set of documents and the role they are playing in training, and includes configuration management and quality assurance documents from the GCS project. Volume 4 contains six appendices: A. Software Accomplishment Summary for the Guidance and Control Software Project; B. Software Configuration Index for the Guidance and Control Software Project; C. Configuration Management Records for the Guidance and Control Software Project; D. Software Quality Assurance Records for the Guidance and Control Software Project; E. Problem Report for the Pluto Implementation of the Guidance and Control Software Project; and F. Support Documentation Change Reports for the Guidance and Control Software Project.

Hayhurst, Kelly J.↗
NASA NTRS2000

Operational Methodology for the International Space Station (ISS) High Rate Communications Outage Recorder (HCOR)

The HCOR will be used onboard the ISS to record digital data during Ku-band Loss of Signal (LOS) periods. This recorded data will be played back to the ground during Ku-band Acquisition of Signal (AOS) periods. The Data Management (DM) Team at the Payload Operations and Integration Center is the primary operator of this complex recorder. The record and playback capabilities - along with the memory management functions - are presented in this paper. To illustrate how the DM Team plans to manage the record, playback and memory management tasks of operating the HCOR, an operational scenario for a ninety-minute orbit is presented.

Mixson, C. David↗
NASA NTRS1972

Report of the Tape Recorder Action Plan Committee, 21 March 1972

A NASA/AF Tape Recorder Action Plan Committee was formed in January 1972 to investigate tape recorder problems and to recommend an action plan to NASA management. The committee collected data on tape recorder failure history, pinpointed problem areas, discussed needed technical and management changes, and proposed an action plan for the recommended approaches.

Source record↗
NASA NTRS1974

Space shuttle configuration accounting functional design specification

An analysis is presented of the requirements for an on-line automated system which must be capable of tracking the status of requirements and engineering changes and of providing accurate and timely records. The functional design specification provides the definition, description, and character length of the required data elements and the interrelationship of data elements to adequately track, display, and report the status of active configuration changes. As changes to the space shuttle program levels II and III configuration are proposed, evaluated, and dispositioned, it is the function of the configuration management office to maintain records regarding changes to the baseline and to track and report the status of those changes. The configuration accounting system will consist of a combination of computers, computer terminals, software, and procedures, all of which are designed to store, retrieve, display, and process information required to track proposed and proved engineering changes to maintain baseline documentation of the space shuttle program levels II and III.

Source record↗
NASA NTRS2004

Space Communications Emulation Facility

Establishing space communication between ground facilities and other satellites is a painstaking task that requires many precise calculations dealing with relay time, atmospheric conditions, and satellite positions, to name a few. The Space Communications Emulation Facility (SCEF) team here at NASA is developing a facility that will approximately emulate the conditions in space that impact space communication. The emulation facility is comprised of a 32 node distributed cluster of computers; each node representing a satellite or ground station. The objective of the satellites is to observe the topography of the Earth (water, vegetation, land, and ice) and relay this information back to the ground stations. Software originally designed by the University of Kansas, labeled the Emulation Manager, controls the interaction of the satellites and ground stations, as well as handling the recording of data. The Emulation Manager is installed on a Linux Operating System, employing both Java and C++ programming codes. The emulation scenarios are written in extensible Markup Language, XML. XML documents are designed to store, carry, and exchange data. With XML documents data can be exchanged between incompatible systems, which makes it ideal for this project because Linux, MAC and Windows Operating Systems are all used. Unfortunately, XML documents cannot display data like HTML documents. Therefore, the SCEF team uses XML Schema Definition (XSD) or just schema to describe the structure of an XML document. Schemas are very important because they have the capability to validate the correctness of data, define restrictions on data, define data formats, and convert data between different data types, among other things. At this time, in order for the Emulation Manager to open and run an XML emulation scenario file, the user must first establish a link between the schema file and the directory under which the XML scenario files are saved. This procedure takes place on the command line on the Linux Operating System. Once this link has been established the Emulation manager validates all the XML files in that directory against the schema file, before the actual scenario is run. Using some very sophisticated commercial software called the Satellite Tool Kit (STK) installed on the Linux box, the Emulation Manager is able to display the data and graphics generated by the execution of a XML emulation scenario file. The Emulation Manager software is written in JAVA programming code. Since the SCEF project is in the developmental stage, the source code for this type of software is being modified to better fit the requirements of the SCEF project. Some parameters for the emulation are hard coded, set at fixed values. Members of the SCEF team are altering the code to allow the user to choose the values of these hard coded parameters by inserting a toolbar onto the preexisting GUI.

Hill, Chante A.↗
NASA NTRS1981

LANDSAT-D data format control book. Volume 6, appendix K: Unprocessed multispectral scanner high density tape (HDT-RM/HDT-GM)

Unprocessed MSS data which is recorded on HDT-RM (a 28 track, high density tape) and on HDT-GM (a 14 track, nonbias recorded, high density tape) are inputs for the LANDSAT 4 data management system. All MSS data initially recorded on HDT-GM are copied to HDT-RM prior to processing. This specification establishes the requirements for the format of the LANDSAT D HDT-RM/HDT-GM.

Andersen, K. E.↗
NASA NTRS1987

NASA Uniform Files Index

This handbook is a guide for the use of all personnel engaged in handling NASA files. It is issued in accordance with the regulations of the National Archives and Records Administration, in the Code of Federal Regulations Title 36, Part 1224, Files Management; and the Federal Information Resources Management Regulation, Subpart 201-45.108, Files Management. It is intended to provide a standardized classification and filing scheme to achieve maximum uniformity and ease in maintaining and using agency records. It is a framework for consistent organization of information in an arrangement that will be useful to current and future researchers. The NASA Uniform Files Index coding structure is composed of the subject classification table used for NASA management directives and the subject groups in the NASA scientific and technical information system. It is designed to correlate files throughout NASA and it is anticipated that it may be useful with automated filing systems. It is expected that in the conversion of current files to this arrangement it will be necessary to add tertiary subjects and make further subdivisions under the existing categories. Established primary and secondary subject categories may not be changed arbitrarily. Proposals for additional subject categories of NASA-wide applicability, and suggestions for improvement in this handbook, should be addressed to the Records Program Manager at the pertinent installation who will forward it to the NASA Records Management Office, Code NTR, for approval. This handbook is issued in loose-leaf form and will be revised by page changes.

Source record↗