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 109 records · Page 6

Autonomous mission planning and scheduling: Innovative, integrated, responsive

Autonomous mission scheduling, a new concept for NASA ground data systems, is a decentralized and distributed approach to scientific spacecraft planning, scheduling, and command management. Systems and services are provided that enable investigators to operate their own instruments. In autonomous mission scheduling, separate nodes exist for each instrument and one or more operations nodes exist for the spacecraft. Each node is responsible for its own operations which include planning, scheduling, and commanding; and for resolving conflicts with other nodes. One or more database servers accessible to all nodes enable each to share mission and science planning, scheduling, and commanding information. The architecture for autonomous mission scheduling is based upon a realistic mix of state-of-the-art and emerging technology and services, e.g., high performance individual workstations, high speed communications, client-server computing, and relational databases. The concept is particularly suited to the smaller, less complex missions of the future.

Sary, Charisse↗

NASA Taxonomy 2.0 Project Overview

This viewgraph presentation reviews the project to develop a Taxonomy for NASA. The benefits of this project are: Make it easy for various audiences to find relevant information from NASA programs quickly, specifically (1) Provide easy access for NASA Web resources (2) Information integration for unified queries and management reporting ve search results targeted to user interests the ability to move content through the enterprise to where it is needed most (3) Facilitate Records Management and Retention Requirements. In addition the project will assist NASA in complying with E-Government Act of 2002 and prepare NASA to participate in federal projects.

taxonomy↗

Implementing the President's Vision: JPL and NASA's Exploration Systems Mission Directorate

As part of the NASA team the Jet Propulsion Laboratory is involved in the Exploration Systems Mission Directorate (ESMD) work to implement the President's Vision for Space exploration. In this slide presentation the roles that are assigned to the various NASA centers to implement the vision are reviewed. The plan for JPL is to use the Constellation program to advance the combination of science an Constellation program objectives. JPL's current participation is to contribute systems engineering support, Command, Control, Computing and Information (C3I) architecture, Crew Exploration Vehicle, (CEV) Thermal Protection System (TPS) project support/CEV landing assist support, Ground support systems support at JSC and KSC, Exploration Communication and Navigation System (ECANS), Flight prototypes for cabin atmosphere instruments

Industry Day↗

Cloud Computing for Mission Design and Operations

The space mission design and operations community already recognizes the value of cloud computing and virtualization. However, natural and valid concerns, like security, privacy, up-time, and vendor lock-in, have prevented a more widespread and expedited adoption into official workflows. In the interest of alleviating these concerns, we propose a series of guidelines for internally deploying a resource-oriented hub of data and algorithms. These guidelines provide a roadmap for implementing an architecture inspired in the cloud computing model: associative, elastic, semantical, interconnected, and adaptive. The architecture can be summarized as exposing data and algorithms as resource-oriented Web services, coordinated via messaging, and running on virtual machines; it is simple, and based on widely adopted standards, protocols, and tools. The architecture may help reduce common sources of complexity intrinsic to data-driven, collaborative interactions and, most importantly, it may provide the means for teams and agencies to evaluate the cloud computing model in their specific context, with minimal infrastructure changes, and before committing to a specific cloud services provider.

cloud computing↗

The development of the EOS data and information system

The architecture of the Earth Observing System (EOS), a major component of NASA's contribution to the U.S. Global Change Research Program, is described with emphasis on its development strategy. It is noted that the EOS is comprised of a scientific research program, a space measurement system, and an EOS Data and Information System (EOSDIS). Details are presented concerning the EOS program and its candidate instruments. Major components of EOS include Version 0 (V0) built on existing Distributed Active Archive Centers (DAACs), the EOSDIS core system (ECS), DAAC-unique functions, science computing facilities (SCF), and independent verification validation of the ECS. Requirements for EODIS are also reviewed noting that, among other requirements, it must keep up with an orbital average data rate of more than 30 Mbps as well as store, distribute, and manage information about tens of Petabytes of data during and after the 15-year mission.

Taylor, Thomas D.↗

Knowledge-Based System for Flight Information Management

The use of knowledge-based system (KBS) architectures to manage information on the primary flight display (PFD) of commercial aircraft is described. The PFD information management strategy used tailored the information on the PFD to the tasks the pilot performed. The KBS design and implementation of the task-tailored PFD information management application is described. The knowledge acquisition and subsequent system design of a flight-phase-detection KBS is also described. The flight-phase output of this KBS was used as input to the task-tailored PFD information management KBS. The implementation and integration of this KBS with existing aircraft systems and the other KBS is described. The flight tests are examined of both KBS's, collectively called the Task-Tailored Flight Information Manager (TTFIM), which verified their implementation and integration, and validated the software engineering advantages of the KBS approach in an operational environment.

Ricks, Wendell R.↗

Titan Architecture Baseline Options

This slide presentation reviews the mission architecture for the Titan mission. The presentation includes information on mission architecture options, probe delivery options, and Enceladus lighting.

mission architecture↗

The Role of Cis-Lunar Space in Future Global Space Exploration

Cis-lunar space offers affordable near-term opportunities to help pave the way for future global human exploration of deep space, acting as a bridge between present missions and future deep space missions. While missions in cis-lunar space have value unto themselves, they can also play an important role in enabling and reducing risk for future human missions to the Moon, Near-Earth Asteroids (NEAs), Mars, and other deep space destinations. The Cis-Lunar Destination Team of NASA's Human Spaceflight Architecture Team (HAT) has been analyzing cis-lunar destination activities and developing notional missions (or "destination Design Reference Missions" [DRMs]) for cis-lunar locations to inform roadmap and architecture development, transportation and destination elements definition, operations, and strategic knowledge gaps. The cis-lunar domain is defined as that area of deep space under the gravitational influence of the earth-moon system. This includes a set of earth-centered orbital locations in low earth orbit (LEO), geosynchronous earth orbit (GEO), highly elliptical and high earth orbits (HEO), earth-moon libration or "Lagrange" points (E-ML1 through E-ML5, and in particular, E-ML1 and E-ML2), and low lunar orbit (LLO). To help explore this large possibility space, we developed a set of high level cis-lunar mission concepts in the form of a large mission tree, defined primarily by mission duration, pre-deployment, type of mission, and location. The mission tree has provided an overall analytical context and has helped in developing more detailed design reference missions that are then intended to inform capabilities, operations, and architectures. With the mission tree as context, we will describe two destination DRMs to LEO and GEO, based on present human space exploration architectural considerations, as well as our recent work on defining mission activities that could be conducted with an EML1 or EML2 facility, the latter of which will be an emphasis of this paper, motivated in part by recent interest expressed at the Global Exploration Roadmap Stakeholder meeting. This paper will also explore the links between this HAT Cis-Lunar Destination Team analysis and the recently released ISECG Global Exploration Roadmap and other potential international considerations, such as preventing harmful interference to radio astronomy observations in the shielded zone of the moon.

Bobskill, Marianne R.↗

Architectural Design for the Global Legal Information Network

In this report, we provide a summary of our activities regarding the goals, requirements analysis, design, and prototype implementation for the Global Legal Information Network, a joint effort between the Law Library of Congress and NASA.

Kalpakis, Konstantinos↗

Integrated System Health Management: Foundational Concepts, Approach, and Implementation

A sound basis to guide the community in the conception and implementation of ISHM (Integrated System Health Management) capability in operational systems was provided. The concept of "ISHM Model of a System" and a related architecture defined as a unique Data, Information, and Knowledge (DIaK) architecture were described. The ISHM architecture is independent of the typical system architecture, which is based on grouping physical elements that are assembled to make up a subsystem, and subsystems combine to form systems, etc. It was emphasized that ISHM capability needs to be implemented first at a low functional capability level (FCL), or limited ability to detect anomalies, diagnose, determine consequences, etc. As algorithms and tools to augment or improve the FCL are identified, they should be incorporated into the system. This means that the architecture, DIaK management, and software, must be modular and standards-based, in order to enable systematic augmentation of FCL (no ad-hoc modifications). A set of technologies (and tools) needed to implement ISHM were described. One essential tool is a software environment to create the ISHM Model. The software environment encapsulates DIaK, and an infrastructure to focus DIaK on determining health (detect anomalies, determine causes, determine effects, and provide integrated awareness of the system to the operator). The environment includes gateways to communicate in accordance to standards, specially the IEEE 1451.1 Standard for Smart Sensors and Actuators.

Figueroa, Fernando↗

The development of a prototype intelligent user interface subsystem for NASA's scientific database systems

The National Space Science Data Center (NSSDC) has initiated an Intelligent Data Management (IDM) research effort which has as one of its components the development of an Intelligent User Interface (IUI).The intent of the latter is to develop a friendly and intelligent user interface service that is based on expert systems and natural language processing technologies. The purpose is to support the large number of potential scientific and engineering users presently having need of space and land related research and technical data but who have little or no experience in query languages or understanding of the information content or architecture of the databases involved. This technical memorandum presents prototype Intelligent User Interface Subsystem (IUIS) using the Crustal Dynamics Project Database as a test bed for the implementation of the CRUDDES (Crustal Dynamics Expert System). The knowledge base has more than 200 rules and represents a single application view and the architectural view. Operational performance using CRUDDES has allowed nondatabase users to obtain useful information from the database previously accessible only to an expert database user or the database designer.

Campbell, William J.↗

Advanced Information Processing System (AIPS)-based fault tolerant avionics architecture for launch vehicles

An avionics architecture for the advanced launch system (ALS) that uses validated hardware and software building blocks developed under the advanced information processing system program is presented. The AIPS for ALS architecture defined is preliminary, and reliability requirements can be met by the AIPS hardware and software building blocks that are built using the state-of-the-art technology available in the 1992-93 time frame. The level of detail in the architecture definition reflects the level of detail available in the ALS requirements. As the avionics requirements are refined, the architecture can also be refined and defined in greater detail with the help of analysis and simulation tools. A useful methodology is demonstrated for investigating the impact of the avionics suite to the recurring cost of the ALS. It is shown that allowing the vehicle to launch with selected detected failures can potentially reduce the recurring launch costs. A comparative analysis shows that validated fault-tolerant avionics built out of Class B parts can result in lower life-cycle-cost in comparison to simplex avionics built out of Class S parts or other redundant architectures.

Lala, Jaynarayan H.↗

Project Integration Architecture: Application Architecture

The Project Integration Architecture (PIA) implements a flexible, object-oriented, wrapping architecture which encapsulates all of the information associated with engineering applications. The architecture allows the progress of a project to be tracked and documented in its entirety. Additionally, by bringing all of the information sources and sinks of a project into a single architectural space, the ability to transport information between those applications is enabled.

Jones, William Henry↗

Project Integration Architecture: Architectural Overview

The Project Integration Architecture (PIA) implements a flexible, object-oriented, wrapping architecture which encapsulates all of the information associated with engineering applications. The architecture allows the progress of a project to be tracked and documented in its entirety. By being a single, self-revealing architecture, the ability to develop single tools, for example a single graphical user interface, to span all applications is enabled. Additionally, by bringing all of the information sources and sinks of a project into a single architectural space, the ability to transport information between those applications becomes possible, Object-encapsulation further allows information to become in a sense self-aware, knowing things such as its own dimensionality and providing functionality appropriate to its kind.

Jones, William Henry↗

Government Information Locator Service (GILS). Draft report to the Information Infrastructure Task Force

This is a draft report on the Government Information Locator Service (GILS) to the National Information Infrastructure (NII) task force. GILS is designed to take advantage of internetworking technology known as client-server architecture which allows information to be distributed among multiple independent information servers. Two appendices are provided -- (1) A glossary of related terminology and (2) extracts from a draft GILS profile for the use of the American National Standard Information Retrieval Application Service Definition and Protocol Specification for Library Applications.

Source record↗

Information data systems for a global change technology initiative architecture trade study

The Global Change Technology Initiative (GCTI) was established to develop technology which will enable use of satellite systems of Earth observations on a global scale, enable use of the observations to predictively model Earth's changes, and provide scientists, government, business, and industry with quick access to the resulting information. At LaRC, a GCTI Architecture Trade Study was undertaken to develop and evaluate the architectural implications to meet the requirements of the global change studies and the eventual implementation of a global change system. The output of the trade study are recommended technologies for the GCTI. That portion of the study concerned with the information data system is documented. The information data system for an earth global change modeling system can be very extensive and beyond affordability in terms of today's costs. Therefore, an incremental approach to gaining a system is most likely. An options approach to levels of capability versus needed technologies was developed. The primary drivers of the requirements for the information data system evaluation were the needed science products, the science measurements, the spacecraft orbits, the instruments configurations, and the spacecraft configurations and their attendant architectures. The science products requirements were not studied here; however, some consideration of the product needs were included in the evaluation results. The information data system technology items were identified from the viewpoint of the desirable overall information system characteristics.

Murray, Nicholas D.↗

ATAM - Automated Trade Assessment Modeling

Automated Trade Assessment Modeling program, ATAM, one of software tools designed to assess candidate architectures for data-management system of Space Station. Designed to discriminate among candidates having equally acceptable performance and reliability characteristics. Utilizes data base, defined by user, containing information on candidate architecture. Assesses such trade factors of system as weight, power consumption, and life-cycle cost. Produces detailed parameter assessments as well as single figure of merit for candidate architecture. Written in Microsoft FORTRAN.

Vallone, Antonio↗

Communications System Architecture Development for Air Traffic Management and Aviation Weather Information Dissemination

This document is the NASA AATT Task Order 24 Final Report. NASA Research Task Order 24 calls for the development of eleven distinct task reports. Each task was a necessary exercise in the development of comprehensive communications systems architecture (CSA) for air traffic management and aviation weather information dissemination for 2015, the definition of the interim architecture for 2007, and the transition plan to achieve the desired End State. The eleven tasks are summarized along with the associated Task Order reference. The output of each task was an individual task report. The task reports that make up the main body of this document include Task 5, Task 6, Task 7, Task 8, Task 10, and Task 11. The other tasks provide the supporting detail used in the development of the architecture. These reports are included in the appendices. The detailed user needs, functional communications requirements and engineering requirements associated with Tasks 1, 2, and 3 have been put into a relational database and are provided electronically.

Gallagher, Seana↗