Data Management Study, Volume 5. Appendix H - Contractor Data Package Logistics and Support /LS/ Final Report
Contractor data package for Voyager logistics and support in transportation, communications, supply, and maintenance
SEARCH · Search NASA
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.
Contractor data package for Voyager logistics and support in transportation, communications, supply, and maintenance
A data simulation is presented for instruments and associated control and display functions required to perform controlled active experiments of the atmosphere. A comprehensive user's guide is given for the data requirements and software developed for the following experiments: (1) electromagnetic wave transmission; (2) passive observation of ambient plasmas; (3) ionospheric measurements with a subsatellite; (4) electron accelerator beam measurements; and (5) measurement of acoustic gravity waves in the sodium layer using lasers. A complete description of each experiment is given.
A new method is presented for handling data resulting from Mobile Satellite propagation experiments such as the Pilot Field Experiment (PiFEx) conducted by JPL. This method uses the UNIX operating system and C programming language. The data management system is implemented on a VAX minicomputer. The system automatically divides the large data file housing data from various experiments under a predetermined format into various individual files containing data from each experiment. The system also has a number of programs written in C and FORTRAN languages to allow the researcher to obtain meaningful quantities from the data at hand.
Explore the source record for details and available documents.
Analysis of data flow through the design and manufacturing processes has established specific information management requirements and identified unique problems. The application of data management technology to the engineering/manufacturing environment addresses these problems. An overview of the IPAD prototype data base management system, representing a partial solution to these problems, is presented here.
The use of an engineering data management system to facilitate the extensive stress analyses of the space shuttle orbiter thermal protection system is demonstrated. The methods used to gather, organize, and store the data; to query data interactively; to generate graphic displays of the data; and to access, transform, and prepare the data for input to a stress analysis program are described. Information related to many separate tiles can be accessed individually from the data base which has a natural organization from an engineering viewpoint. The flexible user features of the system facilitate changes in data content and organization which occur during the development and refinement of the tile analysis procedure. Additionally, the query language supports retrieval of data to satisfy a variety of user-specified conditions.
Performance and design criteria for onboard checkout data management system control and display units, and man machine interfaces
Analysis of functional requirements for data management systems used with space shuttle - Vol. 1
An operational and functional description is given of the data management system. Descriptions are included for the test control unit, analog stimulus panel, discrete stimulus panel, and the precision source. The mechanical configuration is defined and illustrated to provide card and component location for modification or repair. The unit level interfaces are mirror images of the DIU interfaces and are described in the Final Technical Report for NASA-MSFC contract NAS8-29155.
The paper outlines the approach used in developing DMS (Data Management Subsystem) alternatives for the LST (Large Space Telescope) and in selecting the concept considered to be the most cost effective means of implementing the LST DMS requirements. Two candidate DMS concepts are discussed: a functionally integrated and a functionally separated one. For the single vehicle LST program, separation of the DMS functions best provides high reliability, operations flexibility, minimal interface complexity, and the least complex software development and verification task. The use of available hardware and NASA standard components is stressed.
This paper demonstrates the use of an engineering data management system to facilitate the extensive stress analyses of the Space Shuttle Orbiter thermal protection system. Descriptions are given of the approach and methods used (1) to gather, organize, and store the data, (2) to query data interactively, (3) to generate graphic displays of the data, and (4) to access, transform, and prepare the data for input to a stress analysis program. The relational information management system was found to be well suited to the tile analysis problem because information related to many separate tiles could be accessed individually from a data base having a natural organization from an engineering viewpoint. The flexible user features of the system facilitated changes in data content and organization which occurred during the development and refinement of the tile analysis procedure. Additionally, the query language supported retrieval of data to satisfy a variety of user-specified conditions.
Performance/design criteria for aid in selecting onboard checkout and data management system computers
Viewgraphs and discussion on data management standards in computer-aided acquisition and logistic support (CALS) are presented. CALS is intended to reduce cost, increase quality, and improve timeliness of weapon system acquisition and support by greatly improving the flow of technical information. The phase 2 standards, industrial environment, are discussed. The information resource dictionary system (IRDS) is described.
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.
Specifications for computer program support system for onboard checkout and data management system
The state of the art of system analysis is reviewed, emphasizing data management. Analytic, hardware, and software techniques are described.
The author has identified the following significant results. An experimental data bank in conjunction with the National Marine Fisheries Service's Fisheries Engineering Laboratory's (FEL) participation in the ERTS-1 program was established. The data management system was demonstrated to be effective in the performance of the NMFS-FEL ERTS-1 experiment involving several input sources and varying user requirements. The system is to be further evaluated under similar conditions during FEL participation in the Skylab and ERTS-B experiments.
The Computer Interface Unit (CIU) and the Data Interface Unit (DIU) of the Data Management System (DMS) were described as to their functional location, purpose and function. This describes the CIU and DIU at the unit level illustrating their interface thru the Data Bus (DBUS) and to other DMS units. All unit level interfaces are defined as to function and characteristics. The controls, indicators, test points and connectors are listed and function, location and application are described for each. The mechanical configuration is defined and illustrated to provide card and component location for modification or repair purposes. Unique disassembly and assembly requirements are outlined where applicable. A unit internal functional block diagram level description is provided.