Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “ARCHITECTURE”

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 1,567 records · Page 87
All sourcesNASA NTRSDOE OSTI
NASA NTRS2007

Boeing Crew Exploration Vehicle Environmental Control and Life Support System Architecture Overview

The Boeing Company under the teaming agreement with the Northrop Grumman Systems Corporation and in compliance with the NASA Phase 1 contract, had the responsibilities for the CEV architecture development of the Environmental control and life support (ECLS) system under the NASA Phase 1 contract. The ECLS system was comprised of the various subsystems which provided for a shirt-sleeve habitable environment for crew to live and work in the crew module of the CEV. This architecture met the NASA requirements to ferry cargo and crew to ISS, and Lunar sortie missions, with extensibility to long duration missions to Moon and MARS. This paper provides a summary overview of the CEV ECLS subsystems which was proposed in compliance with the contract activities.

Saiidi, Mo↗
NASA NTRS2007

Entity-Centric Abstraction and Modeling Framework for Transportation Architectures

A comprehensive framework for representing transpportation architectures is presented. After discussing a series of preceding perspectives and formulations, the intellectual underpinning of the novel framework using an entity-centric abstraction of transportation is described. The entities include endogenous and exogenous factors and functional expressions are offered that relate these and their evolution. The end result is a Transportation Architecture Field which permits analysis of future concepts under the holistic perspective. A simulation model which stems from the framework is presented and exercised producing results which quantify improvements in air transportation due to advanced aircraft technologies. Finally, a modeling hypothesis and its accompanying criteria are proposed to test further use of the framework for evaluating new transportation solutions.

Lewe, Jung-Ho↗
NASA NTRS2006

A Service Oriented Architecture to Enable Sensor Webs

This viewgraph presentation reviews the development of a Service Oriented Architecture to assist in lowering the cost of new Earth Science products. This architecture will enable rapid and cost effective reconfiguration of new sensors.

Sohlberg, Rob↗
NASA NTRS2007

Orion GN and C Overview and Architecture

The Crew Exploration Vehicle, named Orion, is a critical element in the Constellation Program to develop the transportation system needed to send humans back to the moon and then beyond. Lockheed Martin is the prime contractor for the Orion spacecraft, which is managed by the Johnson Space Center. The Orion GN&C sub-system is being jointly developed by NASA and Lockheed Martin through a mode team approach. The GN&C is a critical element of the Orion mission to carry astronauts to low earth orbit to service the International Space Station and then on later flights to transfer and return a crew of four to the moon. The Orion GN&C system must perform monitoring and abort functions during ascent, rendezvous and docking in both low earth and lunar orbits, perform uncrewed lunar loiter operations, perform trans earth injection and atmospheric entry and landing. The Orion also must be integrated with the Ares I Crew Launch Vehicle, the Earth Departure Stage of the Ares V and the Lunar Surface Access Module. This paper provides an overview of the Orion GN&C system. The functional capabilities of the Orion GN&C will be provided in the context of Constellation architecture, the key GN&C requirements will be summarized, the GN&C architecture will be presented, the development schedule and plans will summarized and finally conclusions will be presented.

Hu, Howard↗
NASA NTRS2007

System Engineering Strategy for Distributed Multi-Purpose Simulation Architectures

This paper describes the system engineering approach used to develop distributed multi-purpose simulations. The multi-purpose simulation architecture focuses on user needs, operations, flexibility, cost and maintenance. This approach was used to develop an International Space Station (ISS) simulator, which is called the International Space Station Integrated Simulation (ISIS)1. The ISIS runs unmodified ISS flight software, system models, and the astronaut command and control interface in an open system design that allows for rapid integration of multiple ISS models. The initial intent of ISIS was to provide a distributed system that allows access to ISS flight software and models for the creation, test, and validation of crew and ground controller procedures. This capability reduces the cost and scheduling issues associated with utilizing standalone simulators in fixed locations, and facilitates discovering unknowns and errors earlier in the development lifecycle. Since its inception, the flexible architecture of the ISIS has allowed its purpose to evolve to include ground operator system and display training, flight software modification testing, and as a realistic test bed for Exploration automation technology research and development.

Bhula, Dlilpkumar↗
NASA NTRS2007

Status, Vision, and Challenges of an Intelligent Distributed Engine Control Architecture

A Distributed Engine Control Working Group (DECWG) consisting of the Department of Defense (DoD), the National Aeronautics and Space Administration (NASA) Glenn Research Center (GRC) and industry has been formed to examine the current and future requirements of propulsion engine systems. The scope of this study will include an assessment of the paradigm shift from centralized engine control architecture to an architecture based on distributed control utilizing open system standards. Included will be a description of the work begun in the 1990's, which continues today, followed by the identification of the remaining technical challenges which present barriers to on-engine distributed control.

Behbahani, Alireza↗
NASA NTRS2007

DSN Antenna Array Architectures Based on Future NASA Mission Needs

A flexible method of parametric, full life-cycle cost analysis has been combined with data on NASA's future communication needs to estimate the required number and operational dates of new antennas for the Deep Space Network (DSN). The requirements were derived from a subset of missions in the Integrated Mission Set database of NASA's Space Communications Architecture Working Group. Assuming that no new antennas are 'constructed', the simulation shows that the DSN is unlikely to meet more than 20% of mission requirements by 2030. Minimum full life-cycle costs result when antennas in the diameter range, 18m-34m, are constructed. Architectures using a mixture of antenna diameters produce a slightly lower full life-cycle cost.

array↗
NASA NTRS2004

A Scalable Architecture of a Structured LDPC Decoder

We present a scalable decoding architecture for a certain class of structured LDPC codes. The codes are designed using a small (n,r) protograph that is replicated Z times to produce a decoding graph for a (Z x n, Z x r) code. Using this architecture, we have implemented a decoder for a (4096,2048) LDPC code on a Xilinx Virtex-II 2000 FPGA, and achieved decoding speeds of 31 Mbps with 10 fixed iterations. The implemented message-passing algorithm uses an optimized 3-bit non-uniform quantizer that operates with 0.2dB implementation loss relative to a floating point decoder.

optical communications↗
NASA NTRS2007

Reducing Development and Operations Costs using NASA's "GMSEC" Systems Architecture

This viewgraph presentation reviews the role of Goddard Mission Services Evolution Center (GMSEC) in reducing development and operation costs in handling the massive data from NASA missions. The goals of GMSEC systems architecture development are to (1) Simplify integration and development, (2)Facilitate technology infusion over time, (3) Support evolving operational concepts, and (4) All for mix of heritage, COTS and new components. First 3 missions (i.e., Tropical Rainforest Measuring Mission (TRMM), Small Explorer (SMEX) missions - SWAS, TRACE, SAMPEX, and ST5 3-Satellite Constellation System) each selected a different telemetry and command system. These results show that GMSEC's message-bus component-based framework architecture is well proven and provides significant benefits over traditional flight and ground data system designs. The missions benefit through increased set of product options, enhanced automation, lower cost and new mission-enabling operations concept options .

Smith, Dan↗
NASA NTRS2001

Bit-serial neuroprocessor architecture

A neuroprocessor architecture employs a combination of bit-serial and serial-parallel techniques for implementing the neurons of the neuroprocessor. The neuroprocessor architecture includes a neural module containing a pool of neurons, a global controller, a sigmoid activation ROM look-up-table, a plurality of neuron state registers, and a synaptic weight RAM. The neuroprocessor reduces the number of neurons required to perform the task by time multiplexing groups of neurons from a fixed pool of neurons to achieve the successive hidden layers of a recurrent network topology.

Tawel, Raoul↗
NASA NTRS2006

Simplified Lasercom System Architecture Using a Disturbance-Free Platform

A simplified laser communications (lasercom) system architecture, primarily for a deep-space flight transceivers, can be realized by decoupling the lasercom optical components from the host spacecraft using a disturbance-free platform (DFP) developed by Lockheed Martin Space System Company. Unlike conventional lasercom system architectures where a high bandwidth control loop is used to stabilize the optical line-of-sight in the presence of platform disturbance, the DFP package isolates the optical train from the high frequency platform jitter produced by the host. By preventing the vibration from coupling into the optics train, the need for a high bandwidth beam stabilization control loop (including fast steering mirror, detectors, controls and the associated relay optics) is eliminated with possible mass savings.

deep space↗
NASA NTRS2008

Assessment of Alternative Europa Mission Architectures

The purpose of this study was to assess the science merit, technical risk and qualitative assessment of relative cost of alternative architectural implementations as applied to a first dedicated mission to Europa. The objective was accomplished through an examination of mission concepts resulting from previous and ongoing studies. Key architectural elements that were considered include moon orbiters, flybys (single flybys like New Horizons and multiple flybys similar to the ongoing Jupiter System Observer study), sample return and in situ landers and penetrators.

Juptier Icy Moon Orbiter (JIMO)↗
NASA NTRS2008

Space Telecommunications Radio System Software Architecture Concepts and Analysis

The Space Telecommunications Radio System (STRS) project investigated various Software Defined Radio (SDR) architectures for Space. An STRS architecture has been selected that separates the STRS operating environment from its various waveforms and also abstracts any specialized hardware to limit its effect on the operating environment. The design supports software evolution where new functionality is incorporated into the radio. Radio hardware functionality has been moving from hardware based ASICs into firmware and software based processors such as FPGAs, DSPs and General Purpose Processors (GPPs). Use cases capture the requirements of a system by describing how the system should interact with the users or other systems (the actors) to achieve a specific goal. The Unified Modeling Language (UML) is used to illustrate the Use Cases in a variety of ways. The Top Level Use Case diagram shows groupings of the use cases and how the actors are involved. The state diagrams depict the various states that a system or object may be in and the transitions between those states. The sequence diagrams show the main flow of activity as described in the use cases.

Handler, Louis M.↗
NASA NTRS2008

Lunar Communication Terminals for NASA Exploration Missions: Needs, Operations Concepts and Architectures

NASA is conducting architecture studies prior to deploying a series of short- and long-duration human and robotic missions for the exploration of the Moon and Mars under the Vision for Space Exploration Initiative. A key objective of these missions is to establish and expand, through a series of launches, a system of systems approach to exploration capabilities and science return. The systems identified were Crew Exploration Vehicles, crew and cargo launch vehicles, crew EVA suits, crew and cargo landers, habitats, mobility carriers, and small, pressurized rovers. Multiple space communication networks and systems, deployed over time, will support these space exploration systems of systems. Each deployment phase will support interoperability of components and provide 20 years of legacy systems. In this paper, we describe the modular lunar communications terminals needed for the emerging lunar mission operational scenarios. These lunar communication terminals require flexibility for use in stationary, integrated, and mobile environments. They will support links directly to Earth, to lunar relay satellites, to astronauts and to fixed and mobile lunar surface systems. The operating concepts and traffic models are presented for these terminals within variety of lunar scenarios. A preliminary architecture is outlined, providing for suitable long-duration operations in the harsh lunar environment.

Bhasin, Kul B.↗
NASA NTRS2006

Managing the Evolution of an Enterprise Architecture using a MAS-Product-Line Approach

We view an evolutionary system ns being n software product line. The core architecture is the unchanging part of the system, and each version of the system may be viewed as a product from the product line. Each "product" may be described as the core architecture with sonre agent-based additions. The result is a multiagent system software product line. We describe an approach to such n Software Product Line-based approach using the MaCMAS Agent-Oriented nzethoclology. The approach scales to enterprise nrchitectures as a multiagent system is an approprinre means of representing a changing enterprise nrchitectclre nnd the inferaction between components in it.

Pena, Joaquin↗
NASA NTRS2008

Network-Attached Solid-State Recorder Architecture

A document discusses placing memory modules on the high-speed serial interconnect, which is used by a spacecraft s computer elements for inter-processor communications, to allow all multiple computer system architectures to access the spacecraft data storage at the same time. Each memory board is identical electrically and receives its bus ID upon connection to the system. The computer elements are configured in a similar fashion. The architecture allows for multiple memory boards to be accessed simultaneously by different computer elements, and results in a scalable, strong, fault-tolerant system. The IEEE-1393 ring bus can be routed so that multiple card failures can occur and the mass memory storage will still function.

Cox, Brian↗
NASA NTRS2008

Ensemble: an Architecture for Mission-Operations Software

Ensemble is the name of an open architecture for, and a methodology for the development of, spacecraft mission operations software. Ensemble is also potentially applicable to the development of non-spacecraft mission-operations- type software. Ensemble capitalizes on the strengths of the open-source Eclipse software and its architecture to address several issues that have arisen repeatedly in the development of mission-operations software: Heretofore, mission-operations application programs have been developed in disparate programming environments and integrated during the final stages of development of missions. The programs have been poorly integrated, and it has been costly to develop, test, and deploy them. Users of each program have been forced to interact with several different graphical user interfaces (GUIs). Also, the strategy typically used in integrating the programs has yielded serial chains of operational software tools of such a nature that during use of a given tool, it has not been possible to gain access to the capabilities afforded by other tools. In contrast, the Ensemble approach offers a low-risk path towards tighter integration of mission-operations software tools.

Norris, Jeffrey↗