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 199 records · Page 11
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

Dione: A Pathfinder Mission for Understanding the Iono-sphere-Thermosphere Responses to Magnetospheric Forcing

Dione is a NASA small satellite prototype for future constellations that in different configurations will provide global and localized measurements of Ionosphere-Thermosphere responses to Magnetospheric energy input in a variety of scales, enabling their better forecast and prediction. This is done with a comprehensive sensor package which includes four instruments: a miniaturized fluxgate magnetometer providing magnetic field measurements with two sensor heads, an ion sensor that measures vector plasma drifts and deduce the in-situ electric fields, an electrostatic analyzer that measures precipitating electrons and up-going secondary electrons, and a neutral mass spectrometer measuring total neutral density and composition. Dione is 3-axis stabilized in a circular low-earth (400-600 km), high-inclination orbit, traversing the auroral precipitation and high latitude currents in every orbit. This paper focuses on the mission-level architecture, but provides contextual information on the science objectives, instruments, and space-craft.

Jaime Esper↗
NASA NTRS2022

Safe Human Expeditions Beyond Low Earth Orbit (LEO)

The NASA Engineering and Safety Center (NESC) conducted an interdisciplinary study and workshop focusing on capabilities needed for crew health and safety on long-duration deep space expeditions in support of the Artemis Program and missions to Mars. The study focused on integration among four disciplines: 1) space weather monitoring and forecasting, 2) shielding technologies, 3) human health research, and 4) human factors engineering tools. An integrated risk assessment was performed to inform characteristics of mission architecture and capabilities needed for safe, long-duration human expeditions beyond low Earth orbit. This report contains the outcome of the NESC assessment.

Low Earth Orbit↗
NASA NTRS2003

Initial SVS Integrated Technology Evaluation Flight Test Requirements and Hardware Architecture

This document presents the flight test requirements for the Initial Synthetic Vision Systems Integrated Technology Evaluation flight Test to be flown aboard NASA Langley's ARIES aircraft and the final hardware architecture implemented to meet these requirements. Part I of this document contains the hardware, software, simulator, and flight operations requirements for this light test as they were defined in August 2002. The contents of this section are the actual requirements document that was signed for this flight test. Part II of this document contains information pertaining to the hardware architecture that was realized to meet these requirements as presented to and approved by a Critical Design Review Panel prior to installation on the B-757 Airborne Research Integrated Experiments Systems (ARIES) airplane. This information includes a description of the equipment, block diagrams of the architecture, layouts of the workstations, and pictures of the actual installations.

Harrison, Stella V.↗
NASA NTRSDate not supplied

Gateway Program Safety and Mission Assurance Integration - the Future of Safe Deep Space Human Exploration

As a foundational element of the National Aeronautics and Space Administration (NASA) Artemis Campaign, the Gateway is an incrementally built cislunar spacecraft that will serve as a platform for deep space human exploration, science, and technology demonstration. The Gateway will be a unifying catalyst for international partners around the world to establish sustained deep space scientific investigations, lunar surface access, and missions to Mars. As human exploration moves farther away from Earth, spacecraft designs must prioritize and optimize mass and volume allocations, while minimizing human and spacecraft risk. To accomplish this objective, the Gateway Program Safety and Mission Assurance functions develop, implement, and ensure compliance with requirements, in concert with the accurate characterization and transparent communication of residual hazard risks, for integrated safety, reliability and maintainability and quality assurance. Safety and Mission Assurance was a key contributor during Gateway program pre-formulation and formulation activities where safety and reliability analysis was embedded in the Gateway Systems Engineering and Integration team. During these early program stages, a preliminary Gateway Integrated Hazard Analysis and Preliminary Gateway Probabilistic Risk Assessment assisted in Gateway architectural and operational definition as part of a risk-informed design process. As the deep space architecture has matured, the integrated Safety and Mission Assurance analyses have matured, new safety review processes have been developed, and requirements have been refined to ensure compliance with integrated safety and mission assurance objectives. The Gateway Program is currently concluding the preliminary design review informed milestone, where the primary objectives included: - Ensured completeness and consistency of the preliminary design, including the meeting of all requirements within appropriate margins and acceptable risk posture. - Identification of any major issues moving forward to the Critical Design phase. At this milestone, Safety and Mission Assurance provided numerous products, including Gateway Top Risks and Risk Mitigation Plans, updated integrated hazard analyses, updated probabilistic risk assessment, Crew Survival Analysis Report, and updated Safety and Mission Assurance Requirements and Plans. These products provide a many-faceted perspective on the inherent risk and available mitigations involved in flying the current proposed vehicle design and anticipated stack configurations. In addition, Safety and Mission Assurance identified top technical, process and workforce concerns to be addressed as the program progresses toward the critical design phase. This paper will detail the evolution of the Gateway Program Safety and Mission Assurance integration functions, provide its current status and lessons learned for future human spaceflight programs. Throughout this paper the key tenets of the Gateway Program Safety and Mission Assurance will be discussed: - Application of a risk-informed approach to identify and mitigate areas of highest risk. - Leverage of valuable processes and lessons learned from earlier spaceflight programs. - Development of Safety and Mission Assurance products to inform design risk trades. - Utilization of common Safety and Mission Assurance practices to identify safety risks for multiple perspectives: top-down, bottom-up, and across lines of integration. - Approval of safety hazards at the appropriate level of authority, keeping most deliberation closest to design expertise and elevating risks of greatest concern for program-level consideration. - Championing of Safety and Mission Assurance processes and forums to foster a pervasive safety culture that is transparent, inclusive, and collaborative between all partners. These tenets have allowed the Gateway Safety and Mission Assurance function to play a key role in optimized vehicle design evolution, and early identification and mitigation of Gateway program and Artemis mission risk.

Helen Vaccaro↗
NASA NTRS2000

BOREAS TE-23 Canopy Architecture and Spectral Data from Hemispherical Photographs

The Boreal Ecosystem-Atmospheric Study (BOREAS) TE-23 (Terrestrial Ecology) team collected hemispherical photographs in support of its efforts to characterize and interpret information on estimates of canopy architecture and radiative transfer properties for most BOREAS study sites. Various Old Aspen (OA), Old Black Spruce (OBS), Old Jack Pine (OJP), Young Jack Pine (YJP), and Young Aspen (YA) sites in the boreal forest were measured from May to August 1994. The hemispherical photographs were used to derive values of leaf area index (LAI), leaf angle, gap fraction, and clumping index. This documentation describes these derived values. The derived data are stored in tabular ASCII files. The hemispherical photographs are stored in the original set of 42 CD-ROMs that were supplied by TE-23. The data files are available on a CD-ROM (see document number 20010000884), or from the Oak Ridge National Laboratory (ORNL) Distributed Active Archive Center (DAAC).

Rich, Paul M.↗
NASA NTRS2023

X-57 Cockpit Interface Control Document (ICD-CEPT-006)

The Cockpit Interface Control Document defines the hardware interfaces between the X-57 cockpit and subsystems. It provides locational and operational information in support of ground and flight operations with details on controls and displays that include Modes of Operation, Start-Up and Shut- Down Sequence diagrams and captures the current state of the MOD II Avionics Power Architecture. There is also preliminary information of the MOD III and MOD IV configurations. Microsoft PowerPoint was chosen for the document as early development required frequent meetings with multiple customers including aircraft operators (pilots), ground operations, support contractors and power, instrumentation, and human systems integration engineers and PowerPoint enabled presentations that could be quickly modified based on customer and developer interaction. One of the driving requirements for the cockpit design was to keep the left side panel as close the stock Tecnam panel as possible to reduce the failure risk of flight critical indicators. The original annunciator panel in the left side panel was modified to alert the pilot to failures in critical X-57 subsystems and an operator audio alert capability was added for these subsystems. Power-Up switches for the aircraft low voltage 13.8 VDC systems are located at the bottom of the left side panel and center panel, the same location as the stock Tecnam 13.8 VDC switches. The switches for energizing the high voltage system were located in the overhead panel to reduce the risk of inadvertently energizing the high voltage system during the low voltage power-up sequence. The Cruise Motor ARM switches were also located in the overhead panel and correspond to the same location as the stock Tecnam ignition switches. The stock Tecnam throttle levers and prop pitch levers were retained for the X-57. The throttle levers were renamed torque levers since they controlled the commanded torque to the cruise motors. The prop pitch levers provide a commanded RPM signal to an electronic prop pitch controller. X-57 specific displays, located in the right-side panel, are driven by dedicated sensors that monitor right and left side cruise motor RPM, right and left high voltage “Traction Bus” A and B (voltage, current and power) and the Avionics Bus DC converters (A and B) voltage and current. An X-57 Multi-Function Display (MFD) located in the center panel displays CAN Bus parameters. CAN Bus architecture is not certified for flight so these displays could not be used for safety critical information but were designed to be used for test point information only.

Laura Kushner↗
NASA NTRS2004

A Software Architecture for Semiautonomous Robot Control

A software architecture has been developed to increase the safety and effectiveness with which tasks are performed by robots that are capable of functioning autonomously but sometimes are operated under control by humans. The control system of such a robot designed according to a prior software architecture has no way of taking account of how the environment has changed or what parts of a task were performed during an interval of control by a human, so that errors can occur (and, hence, safety and effectiveness jeopardized) when the human relinquishes control. The present architecture incorporates the control, task-planning, and sensor-based-monitoring features of typical prior autonomous-robot software architectures, plus features for updating information on the environment and planning of tasks during control by a human operator in order to enable the robot to track the actions taken by the operator and to be ready to resume autonomous operation with minimal error. The present architecture also provides a user interface that presents, to the operator, a variety of information on the internal state of the robot and the status of the task.

Kortenkamp, David↗
NASA NTRS2015

Connecting Requirements to Architecture and Analysis via Model-Based Systems Engineering

In traditional systems engineering practice, architecture, concept development, and requirements development are related but still separate activities. Concepts for operation, key technical approaches, and related proofs of concept are developed. These inform the formulation of an architecture at multiple levels, starting with the overall system composition and functionality and progressing into more detail. As this formulation is done, a parallel activity develops a set of English statements that constrain solutions. These requirements are often called "shall statements" since they are formulated to use "shall." The separation of requirements from design is exacerbated by well-meaning tools like the Dynamic Object-Oriented Requirements System (DOORS) that remained separated from engineering design tools. With the Europa Clipper project, efforts are being taken to change the requirements development approach from a separate activity to one intimately embedded in formulation effort. This paper presents a modeling approach and related tooling to generate English requirement statements from constraints embedded in architecture definition.

Cole, Bjorn F.↗
NASA NTRS1990

Diverter Decision Aiding for In-Flight Diversions

It was determined that artificial intelligence technology can provide pilots with the help they need in making the complex decisions concerning en route changes in a flight plan. A diverter system should have the capability to take all of the available information and produce a recommendation to the pilot. Phase three illustrated that using Joshua to develop rules for an expert system and a Statice database provided additional flexibility by permitting the development of dynamic weighting of diversion relevant parameters. This increases the fidelity of the AI functions cited as useful in aiding the pilot to perform situational assessment, navigation rerouting, flight planning/replanning, and maneuver execution. Additionally, a prototype pilot-vehicle interface (PVI) was designed providing for the integration of both text and graphical based information. Advanced technologies were applied to PVI design, resulting in a hierarchical menu based architecture to increase the efficiency of information transfer while reducing expected workload. Additional efficiency was gained by integrating spatial and text displays into an integrated user interface.

Rudolph, Frederick M.↗
NASA NTRS1993

NELS 2.0 - A general system for enterprise wide information management

NELS, the NASA Electronic Library System, is an information management tool for creating distributed repositories of documents, drawings, and code for use and reuse by the aerospace community. The NELS retrieval engine can load metadata and source files of full text objects, perform natural language queries to retrieve ranked objects, and create links to connect user interfaces. For flexibility, the NELS architecture has layered interfaces between the application program and the stored library information. The session manager provides the interface functions for development of NELS applications. The data manager is an interface between session manager and the structured data system. The center of the structured data system is the Wide Area Information Server. This system architecture provides access to information across heterogeneous platforms in a distributed environment. There are presently three user interfaces that connect to the NELS engine; an X-Windows interface, and ASCII interface and the Spatial Data Management System. This paper describes the design and operation of NELS as an information management tool and repository.

Smith, Stephanie L.↗
NASA NTRS1991

FIDEX: An expert system for satellite diagnostics

A Fault Isolation and Diagnostic Expert system (FIDEX) was developed for communication satellite diagnostics. It was designed specifically for the 30/20 GHz satellite transponder. The expert system was designed with a generic structure and features that make it applicable to other types of space systems. FIDEX is a frame based system that enjoys many of the inherent frame base features, such as hierarchy that describes the transponder's components, with other hierarchies that provide structural and fault information about the transponder. This architecture provides a flexible diagnostic structure and enhances maintenance of the system. FIDEX also includes an inexact reasoning technique and a primitive learning ability. Inexact reasoning was an important feature for this system due to the sparse number of sensors available to provide information on the transponder's performance. FIDEX can determine the most likely faulted component under the constraint of limited information. FIDEX learns about the most likely faults in the transponder by keeping a record of past established faults. FIDEX also has the ability to detect anomalies in the sensors that provide information on the transponders performance.

Durkin, John↗
NASA NTRS2007

System for Secure Integration of Aviation Data

The Aviation Data Integration System (ADIS) of Ames Research Center has been established to promote analysis of aviation data by airlines and other interested users for purposes of enhancing the quality (especially safety) of flight operations. The ADIS is a system of computer hardware and software for collecting, integrating, and disseminating aviation data pertaining to flights and specified flight events that involve one or more airline(s). The ADIS is secure in the sense that care is taken to ensure the integrity of sources of collected data and to verify the authorizations of requesters to receive data. Most importantly, the ADIS removes a disincentive to collection and exchange of useful data by providing for automatic removal of information that could be used to identify specific flights and crewmembers. Such information, denoted sensitive information, includes flight data (here signifying data collected by sensors aboard an aircraft during flight), weather data for a specified route on a specified date, date and time, and any other information traceable to a specific flight. The removal of information that could be used to perform such tracing is called "deidentification." Airlines are often reluctant to keep flight data in identifiable form because of concerns about loss of anonymity. Hence, one of the things needed to promote retention and analysis of aviation data is an automated means of de-identification of archived flight data to enable integration of flight data with non-flight aviation data while preserving anonymity. Preferably, such an automated means would enable end users of the data to continue to use pre-existing data-analysis software to identify anomalies in flight data without identifying a specific anomalous flight. It would then also be possible to perform statistical analyses of integrated data. These needs are satisfied by the ADIS, which enables an end user to request aviation data associated with de-identified flight data. The ADIS includes client software integrated with other software running on flight-operations quality-assurance (FOQA) computers for purposes of analyzing data to study specified types of events or exceedences (departures of flight parameters from normal ranges). In addition to ADIS client software, ADIS includes server hardware and software that provide services to the ADIS clients via the Internet (see figure). The ADIS server receives and integrates flight and non-flight data pertaining to flights from multiple sources. The server accepts data updates from authorized sources only and responds to requests from authorized users only. In order to satisfy security requirements established by the airlines, (1) an ADIS client must not be accessible from the Internet by an unauthorized user and (2) non-flight data as airport terminal information system (ATIS) and weather data must be displayed without any identifying flight information. ADIS hardware and software architecture as well as encryption and data display scheme are designed to meet these requirements. When a user requests one or more selected aviation data characteristics associated with an event (e.g., a collision, near miss, equipment malfunction, or exceedence), the ADIS client augments the request with date and time information from encrypted files and submits the augmented request to the server. Once the user s authorization has been verified, the server returns the requested information in de-identified form.

Kulkarni, Deepak↗
NASA NTRS1991

Recommendations for an Executive Information System (EIS) for the NASA Accounting and Financial Information System (NAFIS)

The objectives were to: (1) survey state-of-the-art computing architectures, tools, and technologies for implementing an Executive Information System (EIS); (2) review MSFC capabilities and efforts in developing an EIS for Shuttle Projects Office and the Payloads Project Office; (3) review management reporting requirements for the NASA Accounting and Financial Information System (NAFIS) Project in the areas of cost, schedule, and technical performance, and insure that the EIS fully supports these requirements; and (4) develop and implement a pilot concept for a NAFIS EIS. A summary of the findings of this work is presented.

Goss, Ernest Preston↗
NASA NTRS2018

How Public Private Partnerships Enable NASA Future Space Communication Needs

The NASA Space Communications and Navigation (SCaN) Program is responsible for providing communication and navigation services to scientific and human space exploration missions. SCaN's current Space Network provides radio frequency (RF) relay services to near Earth space missions via Tracking and Data Relay Satellites (TDRS). SCaN plans to offer a new generation of relay services beginning in 2025, including the addition of optical communications capabilities and enhanced RF capabilities. The primary drivers behind the development of these next generation relay network services are to enhance communication and navigation services with significantly reduced development and operational costs. Several approaches being considered for implementation of these services are through government owned capabilities, through commercial service providers, or a combination of the two. One approach receiving a great deal of attention is the use of Public-Private Partnerships (PPP) to develop and provide capabilities or services. Utilizing Public-Private Partnerships allows NASA and commercial entities to share the investment, standards, and risks of developing and testing new or enhanced capabilities which can benefit both NASA and the commercial space communication industry. The capabilities developed under the PPP can then be used to support the growth of the commercial satellite communications industry while simultaneously being introduced into NASA operations to provide service to future NASA missions as part of the NASA Next Generation Architecture. Partnerships formed for this purpose can also serve as the basis for further NASA acquisition activities where government and industry can continue to share the cost, risk, and benefits of space communications capability development and operations. This objective is consistent with the 2010 National Space Policy stated principles: "The United States is committed to encouraging and facilitating the growth of a U.S. commercial space sector that supports U.S. needs, is globally competitive, and advances U.S. leadership in the generation of new markets and innovation-driven entrepreneurship." [1]NASA has conducted several internal studies as well as externally funded studies with industry to define the next generation space communication architecture. NASA has approached the commercial industry through a Request for Information (RFI) to define further the next generation architecture and has conducted numerous internal and external studies. The results are promising and are shaping the approach to utilize Public Private Partnership to achieve NASA's objectives while reducing costs. The commercial satellite industry has begun to deploy high performance, high throughput global satellite constellations which have the potential to provide communication services to NASA Missions. Commercial satellite manufacturers have advanced their processes to rapidly design, build, and deliver, reliable communication satellites using minimum government oversight. In this paper, we will 1) describe the NASA Next Generation Architecture, Concept of Operations (ConOps), and salient characteristics; 2) Discuss the rational of Public-Private Partnerships to achieve NASA’s next generation communication architecture; and 3) Summarize the preliminary analysis performed to date and describe the path forward.

Stegeman, James↗
NASA NTRS2017

Updated Mars Mission Architectures Featuring Nuclear Thermal Propulsion

Nuclear thermal propulsion (NTP) can potentially enable routine human exploration of Mars and the solar system. By using nuclear fission instead of a chemical combustion process, and using hydrogen as the propellant, NTP systems promise rocket efficiencies roughly twice that of the best chemical rocket engines currently available. The most recent major Mars architecture study featuring NTP was the Design Reference Architecture 5.0 (DRA 5.0), performed in 2009. Currently, the predominant transportation options being considered are solar electric propulsion (SEP) and chemical propulsion; however, given NTP's capabilities, an updated architectural analysis is needed. This paper provides a top-level overview of several different architectures featuring updated NTP performance data. New architectures presented include a proposed update to the DRA 5.0 as well as an investigation of architectures based on the current Evolvable Mars Campaign, which is the focus of NASA's current analyses for the Journey to Mars. Architectures investigated leverage the latest information relating to NTP performance and design considerations and address new support elements not available at the time of DRA 5.0, most notably the Orion crew module and the Space Launch System (SLS). The paper provides a top level quantitative comparison of key performance metrics as well as a qualitative discussion of improvements and key challenges still to be addressed. Preliminary results indicate that the updated NTP architectures can significantly reduce the campaign mass and subsequently the costs for assembly and number of launches.

Rodriguez, Mitchell A.↗
NASA NTRSDate not supplied

Open Data Integration (ODIN): A Concurrent, Distributed Message-Based Architecture and Framework for Disaster Response

The Runtime for Airspace Concept Evaluation (RACE) is an open-source software architecture and framework to build configurable, highly concurrent and distributed message-based systems that offer scalable, low-latency performance on commodity hardware. RACE was used in commercial aviation applications to rapidly build systems that span several machines (including synchronized displays), interface existing hardware simulators and other live data feeds, and incorporate sophisticated visualization components such as NASA WorldWind. These RACE applications validated elements of the FAA’s System Wide Information Management (SWIM) Program, handling up to 1000 messages/sec from diverse sources (SFDPS, TFM-DATA, TAIS, ASDE-X, ITWS and local ADS) for 4,500 simultaneous flights tracked in the next-generation air transportation system’s digital backbone. We have since generalized RACE to support Open Data Integration (ODIN) applications outside aviation. Systems built with RACE/ODIN can be deployed in the field, on commodity hardware, and operate with limited or intermittent connectivity to the outside world. Our primary use case is a web-server with local/persistent data storage that runs within and only serves the stakeholder network (e.g. an incident command post). We are tailoring the RACE/ODIN system to support wildland fire management for the upcoming NASA Wildland Fire Safety Demonstration Series. RACE-ODIN is under consideration for application in the Scalable Traffic Management for Emergency Response Operations project, or STEReO, which aims to create a system that can be deployed during emergencies, to coordinate multiple elements of disaster response. Such data sources predominantly come from existing services on the internet (e.g. weather and satellite data, imported from so called "edge servers") but can also include dynamic (real-time) data from computer simulations and within the stakeholder network (such as aircraft and personnel tracking information). We will present the architecture and ODIN system demonstration incorporating local data from instrumented power-line towers, interpolated weather data and geospatial data from space-based platforms.

Joseph C Coughlan↗