Search NASA⌕ Search

SEARCH · Search NASA

Results for “information architectures”

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

Impacts of In-Space Assembly as Applied to Human Exploration Architectures

Human missions to Mars present several major challenges that must be overcome, including delivering multiple large mass and volume elements, keeping the crew safe and productive, meeting cost constraints, and ensuring a sustainable campaign. Traditional methods for executing human Mars missions minimize or eliminate in-space assembly (iSA), which provides a narrow range of options for addressing these challenges and limits the types of missions that can be performed. This paper discusses recent work to evaluate how the inclusion of in-space assembly in space mission architectural concepts could provide novel solutions to address these challenges by increasing operational flexibility, robustness, risk reduction, crew health and safety, and sustainability. Several assembly focus areas identified through previous work were developed and evaluated to identify high-potential iSA applications that can have meaningful impacts on the challenges facing Mars missions. Architecture trade options were developed and assessed through sensitivity analyses, resulting in identification of six iSA-based architecture solutions that could be incorporated into Mars mission architectures with moderate levels of assembly. Assembly agent and infrastructure concepts were also developed that would be necessary to enable or facilitate the iSA operations. Several observations developed through the study are presented to inform future human mission architecture and campaign developments.

Jefferies, Sharon A.↗
NASA NTRS1990

Fast packet switch architectures for broadband integrated services digital networks

Background information on networking and switching is provided, and the various architectures that have been considered for fast packet switches are described. The focus is solely on switches designed to be implemented electronically. A set of definitions and a brief description of the functionality required of fast packet switches are given. Three basic types of packet switches are identified: the shared-memory, shared-medium, and space-division types. Each of these is described, and examples are given.

Tobagi, Fouad A.↗
NASA NTRS2015

Integrated Space Asset Management Database and Modeling

Effective Space Asset Management is one key to addressing the ever-growing issue of space congestion. It is imperative that agencies around the world have access to data regarding the numerous active assets and pieces of space junk currently tracked in orbit around the Earth. At the center of this issues is the effective management of data of many types related to orbiting objects. As the population of tracked objects grows, so too should the data management structure used to catalog technical specifications, orbital information, and metadata related to those populations. Marshall Space Flight Center's Space Asset Management Database (SAM-D) was implemented in order to effectively catalog a broad set of data related to known objects in space by ingesting information from a variety of database and processing that data into useful technical information. Using the universal NORAD number as a unique identifier, the SAM-D processes two-line element data into orbital characteristics and cross-references this technical data with metadata related to functional status, country of ownership, and application category. The SAM-D began as an Excel spreadsheet and was later upgraded to an Access database. While SAM-D performs its task very well, it is limited by its current platform and is not available outside of the local user base. Further, while modeling and simulation can be powerful tools to exploit the information contained in SAM-D, the current system does not allow proper integration options for combining the data with both legacy and new M&S tools. This paper provides a summary of SAM-D development efforts to date and outlines a proposed data management infrastructure that extends SAM-D to support the larger data sets to be generated. A service-oriented architecture model using an information sharing platform named SIMON will allow it to easily expand to incorporate new capabilities, including advanced analytics, M&S tools, fusion techniques and user interface for visualizations. In addition, tight control of information sharing policy will increase confidence in the system, which would encourage industry partners to provide commercial data. Combined with the integration of new and legacy M&S tools, a SIMON-based architecture will provide a robust environment that can be extended and expanded indefinitely.

MacLeod, Todd↗
NASA NTRS1990

Using expert systems to implement a semantic data model of a large mass storage system

The successful development of large volume data storage systems will depend not only on the ability of the designers to store data, but on the ability to manage such data once it is in the system. The hypothesis is that mass storage data management can only be implemented successfully based on highly intelligent meta data management services. There now exists a proposed mass store system standard proposed by the IEEE that addresses many of the issues related to the storage of large volumes of data, however, the model does not consider a major technical issue, namely the high level management of stored data. However, if the model were expanded to include the semantics and pragmatics of the data domain using a Semantic Data Model (SDM) concept, the result would be data that is expressive of the Intelligent Information Fusion (IIF) concept and also organized and classified in context to its use and purpose. The results are presented of a demonstration prototype SDM implemented using the expert system development tool NEXPERT OBJECT. In the prototype, a simple instance of a SDM was created to support a hypothetical application for the Earth Observing System, Data Information System (EOSDIS). The massive amounts of data that EOSDIS will manage requires the definition and design of a powerful information management system in order to support even the most basic needs of the project. The application domain is characterized by a semantic like network that represents the data content and the relationships between the data based on user views and the more generalized domain architectural view of the information world. The data in the domain are represented by objects that define classes, types and instances of the data. In addition, data properties are selectively inherited between parent and daughter relationships in the domain. Based on the SDM a simple information system design is developed from the low level data storage media, through record management and meta data management to the user interface.

Roelofs, Larry H.↗
NASA NTRS1993

Embedded Data Processor and Portable Computer Technology testbeds

Attention is given to current activities in the Embedded Data Processor and Portable Computer Technology testbed configurations that are part of the Advanced Data Systems Architectures Testbed at the Information Sciences Division at NASA Ames Research Center. The Embedded Data Processor Testbed evaluates advanced microprocessors for potential use in mission and payload applications within the Space Station Freedom Program. The Portable Computer Technology (PCT) Testbed integrates and demonstrates advanced portable computing devices and data system architectures. The PCT Testbed uses both commercial and custom-developed devices to demonstrate the feasibility of functional expansion and networking for portable computers in flight missions.

Alena, Richard↗
NASA NTRS2019

Managing Flagship Missions to Reduce Cost and Schedule

Flagship missions are highly complex with highly nested systems. This level of complexity poses unique management problems as complexity influences risk which, in turn, affects cost and schedule. Establishing a strong technical and programmatic leadership team is critical to mission success. Developing and using a mission architecture is critical to informing the management organization, product ownership, interface and integration relationships, schedule organization, and integration and test paths. In highly nested systems, the mission phasing can be significantly out of sync with product phasing. Targeted technology development prior to Phase A is critical to reducing risk. Early architecture, concept design, and requirements development is critical to reducing risk. Modular design; pathfinders; parallel manufacturing and integration and test paths; and properly handling institutional requirements across interfaces are all management techniques that can be applied to reduce risk. NASA’s large strategic missions, sometimes referred to as flagship missions, are designed to provide answers to some of the most compelling scientific questions being asked. These types of missions are a series of highly nested subsystems that pose unique management problems when compared to more traditional instrument and spacecraft designs. They typically have an overall architecture that is very complex and nested; they typically require a tremendous amount of technology development; they typically involve many contractors and subcontractors with many associated contracts; and they typically involve staff from all over the world. Successful management of a flagship requires the balance between science requirements, engineering and technology capabilities, and resource constraints. Mismanaging these flagship missions can and will lead to significant cost and schedule growth, both of which are detrimental to NASA’s overall reputation which, in turn, is detrimental to the development of future flagship missions. While many of the same management principles used on smaller instruments and spacecraft are relevant, managing flagship missions requires an evolution of those current best practices to better address the specific needs and additional complexity and vastness of these missions. This paper explores how to leverage lessons learned from previous flagship missions to better manage flagship missions in the future.

Hylan, Jason↗
NASA NTRS2005

An Introduction to Message-Bus Architectures for Space Systems

This course presents technical and programmatic information on the development of message-based architectures for space mission ground and flight software systems. Message-based architecture approaches provide many significant advantages over the more traditional socket-based one-of-a-kind integrated system development approaches. The course provides an overview of publish/subscribe concepts, the use of common isolation layer API's, approaches to message standardization, and other technical topics. Several examples of currently operational systems are discussed and possible changes to the system discussed and time for questions and answers will be provided.

Smith, Danford↗
NASA NTRS2005

Introduction to Message-Bus Architectures for Space Systems

This course presents technical and programmatic information on the development of message-based architectures for space mission ground and flight software systems. Message-based architecture approaches provide many significant advantages over the more traditional socket-based one-of-a-kind integrated system development approaches. The course provides an overview of publish/subscribe concepts, the use of common isolation layer API's, approaches to message standardization, and other technical topics. Several examples of currently operational systems are discussed and possible changes to the system development process are presented. Benefits and lessons learned will be discussed and time for questions and answers will be provided.

Smith, Dan↗
NASA NTRS1984

Pilot land data system

During the fall of 1983, the Information Systems Office of NASA's Office of Space Science and Applications assembled a Working Group to develop initial plans for a Pilot Land Data System (PLDS). Workshops coordinated planning and concept development activities between land-related and computer science disciplines, and examined land research requirements, information science technology requirements, PLDS architecture, and methodologies for system evaluation. The PLDS will be a limited-scale distributed information system to explore scientific, technical and management approaches to satisfy land science research needs. PLDS will pave the way for a Land Data System to improve data access, processing, transfer and analysis, fostering an environment in which land science information synthesis can occur on a scale not previously possible owing to limits to data assembly and access and efficiency of processing.

Cressy, P. J.↗
NASA NTRS2019

Remote ID for Rapid Assessment of Flight and Vehicle Information

The ability to rapidly identify UAS in the field has emerged as a critical need for the integration of small UASs into the national airspace and counter-uas operations. This paper proposes an architecture for rapid retrieval of UAS information leveraging NASA's current Unmanned Aircraft System (UAS) Traffic Management (UTM) system. The proposed architecture utilizes UTM components: FIMS (Flight Information Management System), USS (UAS Service Supplier), and vehicle registration and model database in order to provide assessment of the UAS reported in the field including the ability to distinguish between participating and non- participating UTM actors. Detailed system descriptions are provided and preliminary results from field tests conducted during UTM TCL (Technical Capability Level) 3 are discussed. It is found that 94% of the remote ID look-ups were successful. The average time of a look-up is found to be 1.2 seconds. Failure cases are examined and recommendations on next steps to advance UAS remote identification are provided.

Ishihara, Abraham K.↗
NASA NTRS1992

The Deep Space Network information system in the year 2000

The Deep Space Network (DSN), the largest, most sensitive scientific communications and radio navigation network in the world, is considered. Focus is made on the telemetry processing, monitor and control, and ground data transport architectures of the DSN ground information system envisioned for the year 2000. The telemetry architecture will be unified from the front-end area to the end user. It will provide highly automated monitor and control of the DSN, automated configuration of support activities, and a vastly improved human interface. Automated decision support systems will be in place for DSN resource management, performance analysis, fault diagnosis, and contingency management.

Markley, R. W.↗
NASA NTRS2019

Remote ID for Rapid Assessment of Flight and Vehicle Information

The ability to rapidly identify UAS (Unmanned Aircraft Systems) in the field has emerged as a critical need for the integration of small UASs into the national airspace and counter-UAS operations. This paper proposes an architecture for rapid retrieval of UAS information leveraging NASA's current Unmanned Aircraft System (UAS) Traffic Management (UTM) system. The proposed architecture utilizes UTM components: FIMS (Flight Information Management System), USS (UAS Service Supplier), and vehicle registration and model database in order to provide assessment of the UAS reported in the field including the ability to distinguish between participating and non- participating UTM actors. Detailed system descriptions are provided and preliminary results from field tests conducted during UTM TCL (Technical Capability Level) 3 are discussed. It is found that 94 percent of the remote ID look-ups were successful. The average time of a look-up is found to be 1.2 seconds. Failure cases are examined and recommendations on next steps to advance UAS remote identification are provided.

USS (UAS Service Supplier)↗
NASA NTRS1980

An Engineering Data Management System for Ipad

An overview of the capabilities and software architecture of the IPAD information processor (IPIP) is presented. IPIP is a state-of-the-art data base management system that satisfies engineering requirements not addressed by present day commercial systems. It also significantly advances a number of capabilities that are offered commercially. IPIP capabilities range from support for multiple schemas and data models to support for distributed processing, configuration control, and data inventory management. IPIP exploits semantic commonality in features offered in various forms at different user interfaces in today's commercial systems. An integrated software architecture supports all user interfaces: programming languages, interactive data manipulation, and schema languages. This approach promotes simplicity and compactness in software and permits features to be offered symmetrically across all appropriate user interfaces.

H R Johnson↗
NASA NTRS1993

Parallel Architectures for Planetary Exploration Requirements (PAPER)

The project's main contributions have been in the area of student support. Throughout the project, at least one, in some cases two, undergraduate students have been supported. By working with the project, these students gained valuable knowledge involving the scientific research project, including the not-so-pleasant reporting requirements to the funding agencies. The other important contribution was towards the establishment of a graduate program in computer science at Hampton University. Primarily, the PAPER project has served as the main research basis in seeking funds from other agencies, such as the National Science Foundation, for establishing a research infrastructure in the department. In technical areas, especially in the first phase, we believe the trip to Jet Propulsion Laboratory, and gathering together all the pertinent information involving experimental computer architectures aimed for planetary explorations was very helpful. Indeed, if this effort is to be revived in the future due to congressional funding for planetary explorations, say an unmanned mission to Mars, our interim report will be an important starting point. In other technical areas, our simulator has pinpointed and highlighted several important performance issues related to the design of operating system kernels for MIMD machines. In particular, the critical issue of how the kernel itself will run in parallel on a multiple-processor system has been addressed through the various ready list organization and access policies. In the area of neural computing, our main contribution was an introductory tutorial package to familiarize the researchers at NASA with this new and promising field zone axes (20). Finally, we have introduced the notion of reversibility in programming systems which may find applications in various areas of space research.

Cezzar, Ruknet↗
NASA NTRSDate not supplied

Integrating Upper Class E Traffic Management (ETM) Operations into the National Airspace System: Use Cases and Research Questions

As new categories of vehicles are introduced in the National Airspace System, so too are novel concepts for a cooperative approach to traffic management environments. One of these new environments, Upper Class E Traffic Management (ETM), is expected to include a variety of high altitude, long endurance vehicles with a range of performance capabilities and mission profiles that operate in cooperative areas above 60,000 feet. In addition to developing the rules, architecture, and systems for operations within the ETM environment itself, it is also important to consider how ETM vehicles will integrate with traditional Air Traffic Management and interact with Air Traffic Control (ATC) as they traverse ATC-controlled airspace and transition in and out of cooperative ETM operating areas. As a first step toward future ETM demonstrations at the National Aeronautics and Space Administration (NASA) Ames Research Center’s Airspace Operations Laboratory, use cases with step-by-step procedures were developed to identify both nominal and off-nominal scenarios in which ETM operations will interact with ATC. As NASA prepares to develop a simulation platform to demonstrate ETM cooperative practices and ETM-ATC interactions, the procedures, ATC roles and responsibilities, data exchange requirements, and research questions that were identified as part of use case development will inform scenario and system architecture design. The upcoming simulation work will include initial prototype ETM-ATC coordination tools to support ATC controllers’ interactions with ETM operations. This paper will briefly discuss NASA’s upcoming ETM development work and then provide background on ETM-ATC interactions, describe each ETM-ATC interaction use case, and discuss open questions on concept, procedures, and assumptions.

ATC↗
NASA NTRSDate not supplied

Integrating Upper Class E Traffic Management (ETM) Operations into the National Airspace System: Use Cases and Research Questions

As new categories of vehicles are introduced in the National Airspace System, so too are novel concepts for a cooperative approach to traffic management environments. One of these new environments, Upper Class E Traffic Management (ETM), is expected to include a variety of high altitude, long endurance vehicles with a range of performance capabilities and mission profiles that operate in cooperative areas above 60,000 feet. In addition to developing the rules, architecture, and systems for operations within the ETM environment itself, it is also important to consider how ETM vehicles will integrate with traditional Air Traffic Management and interact with Air Traffic Control (ATC) as they traverse ATC-controlled airspace and transition in and out of cooperative ETM operating areas. As a first step toward future ETM demonstrations at the National Aeronautics and Space Administration (NASA) Ames Research Center’s Airspace Operations Laboratory, use cases with step-by-step procedures were developed to identify both nominal and off-nominal scenarios in which ETM operations will interact with ATC. As NASA prepares to develop a simulation platform to demonstrate ETM cooperative practices and ETM-ATC interactions, the procedures, ATC roles and responsibilities, data exchange requirements, and research questions that were identified as part of use case development will inform scenario and system architecture design. The upcoming simulation work will include initial prototype ETM-ATC coordination tools to support ATC controllers’ interactions with ETM operations. This paper will briefly discuss NASA’s upcoming ETM development work and then provide background on ETM-ATC interactions, describe each ETM-ATC interaction use case, and discuss open questions on concept, procedures, and assumptions.

ATC↗
NASA NTRSDate not supplied

Desert Research and Technology Studies (D-RATS) 2022 Quicklook Report

This report summarizes the Desert Research and Technology Studies (D-RATS) 2022 analog tests. BACKGROUND - Artemis Challenges – NASA’s concept of operations (ConOps) for the Artemis mission architecture brings new challenges for human exploration of the lunar surface, including: (1) Low-angle, natural lighting at lunar poles; and (2) Exploration sites that challenge communication with Earth. - International Partner Involvement – NASA is working with the Japan Aerospace Exploration Agency (JAXA) to scope mission & functional requirements for an Artemis Pressurized Rover (PR), which JAXA may provide. - Charter – HQ Exploration Systems Development Mission Directorate (ESDMD) Moon to Mars Architecture Development Office (M2MADO) Strategy and Architectures (SA) chartered the Human-in-the-Loop (HITL) test team to investigate Artemis architectural questions related to pressurized rover ConOps. - Rationale – to inform the NASA/JAXA pressurized rover study-agreement. PLAN - Objectives – Analog tests conducted in October 2022 by the D-RATS team addressed three high-level objectives: 1. Investigate pressurized rover (PR) ConOps and capabilities for Artemis exploration 2. Integrate with JAXA engineers & astronauts and incorporate JAXA PR design elements into testing. 3. Re-establish analog field-testing skills & capabilities with rovers to investigate Artemis architecture ConOps. - Secondary Objectives – Work with other groups to leverage D-RATS field test for additional objectives. 4. Work with the Public Affairs Office (PAO) to perform D-RATS public outreach activities. 5. Coordinate with the Human Physiology Performance Protection & Operations (H-3PO) team to facilitate in-field evaluation of human health and performance (HHP) objectives. 6. Share D-RATS field-site and assets with Lunar LTE Studies (Lunar LiTES) team, to aid their study of the use of 4G/LTE communication protocols and devices for astronauts and robotic nodes on the lunar surface. - Team – Fully integrated test team comprised of members from 5 NASA centers, JAXA, and the United States Geological Survey (USGS) - Location – Black Point Lava Flow, ~40 miles north of Flagstaff, AZ HIGH-LEVEL OBJECTIVES ACCOMPLISHED - Investigated Pressurized Rover ConOps & Capabilities for Artemis Exploration (Objective 1) - Completed testing with 4 crew pairs, each spending 3 days and 2 nights in the rover conducting Artemis PR dayin-the-life activities (2 JAXA astronauts, 2 JAXA engineers, 1 NASA astronaut, 3 NASA engineers). - Collected detailed objective & subjective data supporting 10 strategic questions related to Artemis PR operations. - Field geologists present in field observed rover operations & EVAs. - Science team in Houston MCC communicated directly with crew. - Demonstrated crew-led and MCC-led PR teleoperation use cases during EVAs. - Integrated with JAXA Engineers & Astronauts and Incorporated JAXA PR Design Elements into Testing (Objective 2) - NASA & JAXA engineers, flight controllers, scientists, roboticists, and astronauts directly participated in and/or observed testing both in field and in MCC-Houston. - Incorporated JAXA PR design elements into both integrated and standalone testing at JSC and in the field. - Re-established Analog Field-Testing Skills & Capabilities with Rovers to Investigate Artemis Architecture ConOps (Objective 3) - Multiple teams successfully worked to establish and manage field-test base camp, monitor and maintain the rover, and plan and execute 2 weeks of consecutive field-testing with little to no breaks between crews. TEST OUTCOMES - Results will inform Artemis architecture ConOps & capabilities related to pressurized rover operations (see sections 2 for more details) - Summary and team detailed reports will be posted on the D-RATS 2022 wiki

Analog↗
NASA NTRS2004

Architecture and Functionality of the Advanced Life Support On-Line Project Information System (OPIS)

An ongoing effort is underway at NASA Amcs Research Center (ARC) tu develop an On-line Project Information System (OPIS) for the Advanced Life Support (ALS) Program. The objective of this three-year project is to develop, test, revise and deploy OPIS to enhance the quality of decision-making metrics and attainment of Program goals through improved knowledge sharing. OPIS will centrally locate detailed project information solicited from investigators on an annual basis and make it readily accessible by the ALS Community via a web-accessible interface. The data will be stored in an object-oriented relational database (created in MySQL(Trademark) located on a secure server at NASA ARC. OPE will simultaneously serve several functions, including being an R&TD status information hub that can potentially serve as the primary annual reporting mechanism. Using OPIS, ALS managers and element leads will be able to carry out informed research and technology development investment decisions, and allow analysts to perform accurate systems evaluations. Additionally, the range and specificity of information solicited will serve to educate technology developers of programmatic needs. OPIS will collect comprehensive information from all ALS projects as well as highly detailed information specific to technology development in each ALS area (Waste, Water, Air, Biomass, Food, Thermal, and Control). Because the scope of needed information can vary dramatically between areas, element-specific technology information is being compiled with the aid of multiple specialized working groups. This paper presents the current development status in terms of the architecture and functionality of OPIS. Possible implementation approaches for OPIS are also discussed.

Hogan, John A.↗