Search NASA⌕ Search

SEARCH · Search NASA

Results for “Data 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 217 records · Page 12

Temporal Activation of Extravehicular Activity Science and Operations Data: How Rise2's Enablement of a Novel Data Management Prototype Influenced ISS and Artemis Advancements

SSERVI's RIS4E and Rise2 nodes provided early and repeated opportunities to prototype the organization and visualization of science and field operations data together via temporal vs. type-indexing. This data management approach was first explored in our Apollo in Real Time initiative through its meticulous reconciliation and integration of Apollo 11, 13, and 17 mission data, providing an unparalleled temporal and contextual understanding of these historic missions. The positive results from these prototypes served as pre-cursor examples of what eventually became the Collaborative Operations Data Activation (CODA) application at NASA Johnson Space Center (JSC).

B Feist↗

Advanced data management system architectures testbed

The objective of the Architecture and Tools Testbed is to provide a working, experimental focus to the evolving automation applications for the Space Station Freedom data management system. Emphasis is on defining and refining real-world applications including the following: the validation of user needs; understanding system requirements and capabilities; and extending capabilities. The approach is to provide an open, distributed system of high performance workstations representing both the standard data processors and networks and advanced RISC-based processors and multiprocessor systems. The system provides a base from which to develop and evaluate new performance and risk management concepts and for sharing the results. Participants are given a common view of requirements and capability via: remote login to the testbed; standard, natural user interfaces to simulations and emulations; special attention to user manuals for all software tools; and E-mail communication. The testbed elements which instantiate the approach are briefly described including the workstations, the software simulation and monitoring tools, and performance and fault tolerance experiments.

Grant, Terry↗

Analysis of the Intel 386 and i486 microprocessors for the Space Station Freedom Data Management System

The feasibility is analyzed of upgrading the Intel 386 microprocessor, which has been proposed as the baseline processor for the Space Station Freedom (SSF) Data Management System (DMS), to the more advanced i486 microprocessors. The items compared between the two processors include the instruction set architecture, power consumption, the MIL-STD-883C Class S (Space) qualification schedule, and performance. The advantages of the i486 over the 386 are (1) lower power consumption; and (2) higher floating point performance. The i486 on-chip cache does not have parity check or error detection and correction circuitry. The i486 with on-chip cache disabled, however, has lower integer performance than the 386 without cache, which is the current DMS design choice. Adding cache to the 386/386 DX memory hierachy appears to be the most beneficial change to the current DMS design at this time.

Liu, Yuan-Kwei↗

Analysis of the Intel 386 and i486 microprocessors for the Space Station Freedom Data Management System

The feasibility is analyzed of upgrading the Intel 386 microprocessor, which has been proposed as the baseline processor for the Space Station Freedom (SSF) Data Management System (DMS), to the more advanced i486 microprocessors. The items compared between the two processors include the instruction set architecture, power consumption, the MIL-STD-883C Class S (Space) qualification schedule, and performance. The advantages of the i486 over the 386 are (1) lower power consumption; and (2) higher floating point performance. The i486 on-chip cache does not have parity check or error detection and correction circuitry. The i486 with on-chip cache disabled, however, has lower integer performance than the 386 without cache, which is the current DMS design choice. Adding cache to the 386/387 DX memory hierarchy appears to be the most beneficial change to the current DMS design at this time.

Liu, Yuan-Kwei↗

Data management system performance modeling

This paper discusses analytical techniques that have been used to gain a better understanding of the Space Station Freedom's (SSF's) Data Management System (DMS). The DMS is a complex, distributed, real-time computer system that has been redesigned numerous times. The implications of these redesigns have not been fully analyzed. This paper discusses the advantages and disadvantages for static analytical techniques such as Rate Monotonic Analysis (RMA) and also provides a rationale for dynamic modeling. Factors such as system architecture, processor utilization, bus architecture, queuing, etc. are well suited for analysis with a dynamic model. The significance of performance measures for a real-time system are discussed.

Kiser, Larry M.↗

An operational, multistate, earth observation data management system

The purpose of this paper is to investigate a group of potential users of satellite remotely sensed data - state, local, and regional agencies involved in natural resources management. We assess this group's needs in five states and outline alternative data management systems to serve some of those needs. We conclude that an operational Earth Observation Data Management System (EODMS) will be of most use to these user agencies if it provides a full range of information services - from raw data acquisition to interpretation and dissemination of final information products.

Eastwood, L. F., Jr.↗

Space station data management system assessment methodology

A computer-aided modeling tool and methodology was developed and is currently being used to assess candidate designs for the Space Station Data Management System (DMS). The DMS will be a complex distributed computer system including processors, storage devices, local area networks, and software that will support all processing functions on board the Space Station. The methodology produces assessments of the performance, reliability, cost, and physical attributes of the candidate designs. This paper describes the architecture and design of the modeling tool and presents the modeling methodology.

Jones, W. R.↗

Data Management System (DMS) testbed user's manual development, volumes 1 and 2

A critical review of the network communication services contained in the Tinman User's Manual for Data Management System Test Bed (Tinman DMS User's Manual) is presented. The review is from the perspective of applying modern software engineering principles and using the Ada language effectively to ensure the test bed network communication services provide a robust capability. Overall the material on network communication services reflects a reasonably good grasp of the Ada language. Language features are appropriately used for most services. Design alternatives are offered to provide improved system performance and a basis for better application software development. Section two contains a review and suggests clarifications of the Statement of Policies and Services contained in Appendix B of the Tinman DMS User's Manual. Section three contains a review of the Network Communication Services and section four contains concluding comments.

Mcbride, John G.↗

Space Station Freedom data management system growth and evolution report

The Information Sciences Division at the NASA Ames Research Center has completed a 6-month study of portions of the Space Station Freedom Data Management System (DMS). This study looked at the present capabilities and future growth potential of the DMS, and the results are documented in this report. Issues have been raised that were discussed with the appropriate Johnson Space Center (JSC) management and Work Package-2 contractor organizations. Areas requiring additional study have been identified and suggestions for long-term upgrades have been proposed. This activity has allowed the Ames personnel to develop a rapport with the JSC civil service and contractor teams that does permit an independent check and balance technique for the DMS.

Bartlett, R.↗

Program on Earth Observation Data Management Systems (EODMS), appendixes

The needs of state, regional, and local agencies involved in natural resources management in Illinois, Iowa, Minnesota, Missouri, and Wisconsin are investigated to determine the design of satellite remotely sensed derivable information products. It is concluded that an operational Earth Observation Data Management System (EODMS) will be most beneficial if it provides a full range of services - from raw data acquisition to interpretation and dissemination of final information products. Included is a cost and performance analysis of alternative processing centers, and an assessment of the impacts of policy, regulation, and government structure on implementing large scale use of remote sensing technology in this community of users.

Eastwood, L. F., Jr.↗

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

Data management in NOAA

NOAA has 11 terabytes of digital data stored on 240,000 computer tapes. There are an additional 100 terabytes (TB) of geostationary satellite data stored in digital form on specially configured SONY U-Matic video tapes at the University of Wisconsin. There are over 90,000,000 non-digital form records in manuscript, film, printed, and chart form which are not easily accessible. The three NOAA Data Centers service 6,000 requests per year and publish 5,000 bulletins which are distributed to 40,000 subscribers. Seventeen CD-ROM's have been produced. Thirty thousand computer tapes containing polar satellite data are being copied to 12 inch WORM optical disks for research applications. The present annual data accumulation rate of 10 TB will grow to 30 TB in 1994 and to 100 TB by the year 2000. The present storage and distribution technologies with their attendant support systems will be overwhelmed by these increases if not improved. Increased user sophistication coupled with more precise measurement technologies will demand better quality control mechanisms, especially for those data maintained in an indefinite archive. There is optimism that the future will offer improved media technologies to accommodate the volumes of data. With the advanced technologies, storage and performance monitoring tools will be pivotal to the successful long-term management of data and information.

Callicott, William M.↗

ALSEP data management.

Nine million measurements a day are transmitted from each functional ALSEP on the moon and continuously collected on earth for use in long-term scientific analysis. Periodically, this massive flow of intricate data is examined on a real-time basis to evaluate ALSEP performance and to study the need for new commands to any of the ALSEP systems. A worldwide complex of facilities and personnel has the challenging task of efficient and timely data processing and dissemination. This paper describes facility characteristics and support activities and details certain constraints imposed on ALSEP hardware design by data handling requirements. The highlights of the first two years of lunar data management are reviewed.

Murtaugh, C. R.↗

Modeling the data management system of Space Station Freedom with DEPEND

Some of the features and capabilities of the DEPEND simulation-based modeling tool are described. A study of a 1553B local bus subsystem of the Space Station Freedom Data Management System (SSF DMS) is used to illustrate some types of system behavior that can be important to reliability and performance evaluations of this type of spacecraft. A DEPEND model of the subsystem is used to illustrate how these types of system behavior can be modeled, and shows what kinds of engineering and design questions can be answered through the use of these modeling techniques. DEPEND's process-based simulation environment is shown to provide a flexible method for modeling complex interactions between hardware and software elements of a fault-tolerant computing system.

Olson, Daniel P.↗

An overview of the Hubble Space Telescope command and data management system

The Hubble Space Telescope (HST) will be an orbiting observatory which will extend the capability of large earth-based observatories to view the universe by approximately 350 times in volume and approximately seven times in distance. The HST program, which includes the Orbiting Observatory, the Space Telescope Science Institute, and the Space Telescope Operations Control Center, is supported by the Space Shuttle, the Tracking and Data Relay Satellite System, and the NASA Communications Network. This paper describes the Command and Data Management System for the HST spacecraft, including flexibility, operation modes, and end-to-end data flow paths used to meet stringent synchronization and data quality requirements. The results of system tests indicate that the use of concatenated coding techiques consisting of both block and convolutional codes as a protection against random and burst errors has been successful. Diagrams of the HST data system are included.

Clubb, Jerry↗

Data Management System

CENTRA 2000 Inc., a wholly owned subsidiary of Auto-trol technology, obtained permission to use software originally developed at Johnson Space Center for the Space Shuttle and early Space Station projects. To support their enormous information-handling needs, a product data management, electronic document management and work-flow system was designed. Initially, just 33 database tables comprised the original software, which was later expanded to about 100 tables. This system, now called CENTRA 2000, is designed for quick implementation and supports the engineering process from preliminary design through release-to-production. CENTRA 2000 can also handle audit histories and provides a means to ensure new information is distributed. The product has 30 production sites worldwide.

Source record↗