SEARCH · Engineering Papers
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.
ADMIS stores and controls data and documents associated with manned space flight effort. System contains all data oriented toward a specific document; it is primary source of reports generated by the system. Each group of records is composed of one document record, one distribution record for each recipient of the document, and one summary record.
The concept of decentralized (remote) neighborhood offices, linked together through a self-sustaining communications network for exchanging voice messages, video images, and digital data was quantitatively evaluated. Hardware and procedures for the integrated multifunctional system were developed. The configuration of the neighborhood office center (NOC) is explained, its production statistics given, and an experiment for NOC network integration via satellite is described. The hardware selected for the integration NOC/management information system is discussed, and the NASA teleconferencing network is evaluated.
The University Program Report provides current information and related statistics for approximately 4300 grants/contracts/cooperative agreements active during the report period. NASA Field centers and certain Headquarters Program Offices provide funds for those R&D activities in universities which contribute to the mission needs of that particular NASA element. This annual report is one means of documenting the NASA-university relationship, frequently denoted, collectively, as NASA's University Program.
The University Program Report provides current information and related statistics for approximately 4200 grants/contracts/cooperative agreements active during the reporting period. NASA Field Centers and certain Headquarters Program Offices provide funds for those research and development activities in universities which contribute to the mission needs of that particular NASA element. This annual report is one means of documenting the NASA-University relationship, frequently denoted, collectively, as NASA's University Program.
The NASA Parts Project Office (NPPO) comprehensive data system to support all NASA Electric, Electronic, and Electromechanical (EEE) parts management and technical data requirements is described. A phase delivery approach is adopted, comprising four principal phases. Phases 1 and 2 support Space Station Freedom (SSF) and use a centralized architecture with all data and processing kept on a mainframe computer. Phases 3 and 4 support all NASA centers and projects and implement a distributed system architecture, in which data and processing are shared among networked database servers. The Phase 1 system, which became operational in February of 1990, implements a core set of functions. Phase 2, scheduled for release in 1991, adds functions to the Phase 1 system. Phase 3, to be prototyped beginning in 1991 and delivered in 1992, introduces a distributed system, separate from the Phase 1 and 2 system, with a refined semantic data model. Phase 4 extends the data model and functionality of the Phase 3 system to provide support for the NASA design community, including integration with Computer Aided Design (CAD) environments. Phase 4 is scheduled for prototyping in 1992 to 93 and delivery in 1994.
The University Program Report, Fiscal Year 1993, provides current information and related statistics for 7682 grants/contracts/cooperative agreements active during the report period. NASA field centers and certain Headquarters program offices provide funds for those R&D activities in universities which contribute to the mission needs of that particular NASA element. This annual report is one means of documenting the NASA-university relationship, frequently denoted, collectively, as NASA's University Program.
The EOSDIS Version 0 system, released in July, 1994, is a working prototype of a distributed data system. One of the purposes of the V0 project is to take several existing data systems and coordinate them into one system while maintaining the independent nature of the original systems. The project is a learning experience and the lessons are being passed on to the architects of the system which will distribute the data received from the planned EOS satellites. In the V0 system, the data resides on heterogeneous systems across the globe but users are presented with a single, integrated interface. This interface allows users to query the participating data centers based on a wide set of criteria. Because this system is a prototype, we used many novel approaches in trying to connect a diverse group of users with the huge amount of available data. Some of these methods worked and others did not. Now that V0 has been released to the public, we can look back at the design and implementation of the system and also consider some possible future directions for the next generation of EOSDIS.
The University Program report, Fiscal Year 1994, provides current information and related statistics for 7841 grants/contracts/cooperative agreements active during the reporting period. NASA field centers and certain Headquarters program offices provide funds for those activities in universities which contribute to the mission needs of that particular NASA element. This annual report is one means of documenting the NASA-university relationship, frequently denoted, collectively, as NASA's University Program.
The University Program Report, Fiscal Year 1995, provides current information and related statistics for grants/contracts/cooperative agreements active during the report period. NASA field centers and certain Headquarters program offices provide funds for those R&D activities in universities which contribute to the mission needs of that particular NASA element. This annual report is one means of documenting the NASA-university relationship, frequently denoted, collectively, as NASA's University Program.
This report summarizes the chronology, results, and lessons learned from the development of the SSFF-MIS. This system has been nearly two years in development and has yielded some valuable insights into specialized MIS development. General: In December of 1994, the Camber Corporation and Science Applications International Corporation (SAIC) were contracted to design, develop, and implement a MIS for Marshall Space Flight Center's Space Station Furnace Facility Project. The system was to be accessible from both EBM-Compatible PC and Macintosh platforms. The system was required to contain data manually entered into the MIS as well as data imported from other MSFC sources. Electronic interfaces were established for each data source and retrieval was to be performed at prescribed time intervals. The SOW requirement that predominantly drove the development software selection was the dual-platform (IBM-PC and Macintosh) requirement. The requirement that the system would be maintained by Government personnel influenced the selection of Commercial Off-the-shelf software because of its inherent stability and readily available documentation and support. Microsoft FoxPro Professional 2.6 for Windows and Macintosh was selected as the development tool. This is a software development tool that has been in use for many years. It is stable and powerful. Microsoft has since released the replacement for this product, Microsoft Visual FoxPro, but at the time of this development, it was only available on the Windows platform. The initial contract included included the requirement for capabilities relating to the Work- and Organizational Breakdown Structures, cost (plan and actuals), workforce (plan and actuals), critical path scheduling, trend analysis, procurements and contracts, interface to manufacturing, Safety and Mission Assurance, risk analysis, and technical performance indicators. It also required full documentation of the system and training of users. During the course of the contract, the requirements for Safety and Mission Assurance interface, risk analysis, and technical performance indicators were deleted. Additional capabilities were added as reflected in the Contract Chronology below. Modification 4 added the requirement for Support Contractor manpower data, the ability to manually input data not imported from non-nal sources, a general 'health' indicator screen, and remote usage. Mod 6 included the ability to change the level of planning of Civil Service Manpower at any time and the ability to manually enter Op Codes in the manufacturing data where such codes were not provided by the EMPACS database. Modification 9 included a number of changes to report contents and formats. Modification 11 required the preparation of a detailed System Design Document.
Thios report summarizes the chronology, results, and lessons learned from the development of the SSFF-MIS. This system has been nearly two years in development and has yielded some valuable insights into specialized MIS development. Attachment A contains additions, corrections, and deletions by the COTR.
Explore the source record for details and available documents.
RISM investigated alternative approaches, technologies, and communication network architectures to facilitate building the Spaceports and Ranges of the future. RISM started by document most existing US ranges and their capabilities. In parallel, RISM obtained inputs from the following: 1) NASA and NASA-contractor engineers and managers, and; 2) Aerospace leaders from Government, Academia, and Industry, participating through the Space Based Range Distributed System Working Group (SBRDSWG), many of whom are also; 3) Members of the Advanced Range Technology Working Group (ARTWG) subgroups, and; 4) Members of the Advanced Spaceport Technology Working Group (ASTWG). These diverse inputs helped to envision advanced technologies for implementing future Ranges and Range systems that builds on today s cabled and wireless legacy infrastructures while seamlessly integrating both today s emerging and tomorrow s building-block communication techniques. The fundamental key is to envision a transition to a Space Based Range Distributed Subsystem. The enabling concept is to identify the specific needs of Range users that can be solved through applying emerging communication tech
The Mars Pathfinder Mission is developing a small, low cost and mass vehicle that demonstrates interplanetary cruise, entry, descent, and upright landing systems for use in future missions.
Recent successes in Integrated Computational Materials Engineering (ICME) have demonstrated the potential in designing fit-for-purpose materials for a given application in a cost and time efficient manner. However, the material design process must contain a level of automation in the material decision process, implementing some optimization algorithms, to truly enable the full benefits of ICME, particularly when considering materials at multiple length/time scales. In this work, we will demonstrate how the GRC ICME schema and Python framework automates a workflow that captures, analyzes, maintains, and disseminates the digital footprint in the context of tailoring resin material at the nanoscale of a woven composite Y-joint at the macroscale for an Aurora D8 double bubble fuselage. This digital footprint incorporates the interaction of both structural digital twins and material twins at various length scales.
Explore the source record for details and available documents.
The Reference Architecture for Space Information Management (RASIM) suggests the separation of the data model from software components to promote the development of flexible information management systems. RASIM allows the data model to evolve independently from the software components and results in a robust implementation that remains viable as the domain changes. However, the development and management of data models within RASIM are difficult and time consuming tasks involving the choice of a notation, the capture of the model, its validation for consistency, and the export of the model for implementation. Current limitations to this approach include the lack of ability to capture comprehensive domain knowledge, the loss of significant modeling information during implementation, the lack of model visualization and documentation capabilities, and exports being limited to one or two schema types. The advent of the Semantic Web and its demand for sophisticated data models has addressed this situation by providing a new level of data model management in the form of ontology tools. In this paper we describe the use of a representative ontology tool to capture and manage a data model for a space information system. The resulting ontology is implementation independent. Novel on-line visualization and documentation capabilities are available automatically, and the ability to export to various schemas can be added through tool plug-ins. In addition, the ingestion of data instances into the ontology allows validation of the ontology and results in a domain knowledge base. Semantic browsers are easily configured for the knowledge base. For example the export of the knowledge base to RDF/XML and RDFS/XML and the use of open source metadata browsers provide ready-made user interfaces that support both text- and facet-based search. This paper will present the Planetary Data System (PDS) data model as a use case and describe the import of the data model into an ontology tool. We will also describe the current effort to provide interoperability with the European Space Agency (ESA)/Planetary Science Archive (PSA) which is critically dependent on a common data model.
In parallel to the evolution of Management Information Systems from simple data files to complex data bases, the stand-alone computer systems have been migrating toward fully integrated systems serving the work force. The next major productivity gain may very well be to make these highly sophisticated working level Data Base Management Systems (DMBS) serve all levels of management with reports of varying levels of detail. Most attempts by the DBMS development organization to provide useful information to management seem to bog down in the quagmire of competing working level requirements. Most large DBMS development organizations possess three to five year backlogs. Perhaps Office Automation is the vehicle that brings to pass the Management Information System that really serves management. A good office automation system manned by a team of facilitators seeking opportunities to serve end-users could go a long way toward defining a DBMS that serves management. This paper will briefly discuss the problems of the DBMS organization, alternative approaches to solving some of the major problems, a debate about problems that may have no solution, and finally how office automation fits into the development of the Manager's Management Information System.