SEARCH · Engineering Papers

Results for “Architecture Identification”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 163 records · Page 9

All sources NASA NTRS DOE OSTI

NASA NTRS2008

Entry, Descent, and Landing Communications for the 2007 Phoenix Mars Lander

This paper addresses NASA's requirement on the 2007 Phoenix Mars Lander to provide spacecraft communications during entry, descent, and landing on Mars to allow the identification of probable root cause should any mission failure occur. The Phoenix mission launched on 4 August 2007 and will land on 25 May 2008 on the northern plains of Mars to conduct a three-month study of the Martian environment. The paper discusses the architectural trades in designing a communications link and surveys the entry, descent, and landing communications approaches taken by previous missions. It then discusses the Phoenix-specific constraints and degrees of freedoms and presents a novel and robust implementation approach to entry, descent, and landing communications. The overall methodology and conclusions described herein can serve as a pathfinder for the entry, descent, and landing communications architecture and implementation of future Mars landed missions.

communications↗

NASA NTRS2000

A Debugger for Computational Grid Applications

The p2d2 project at NAS has built a debugger for applications running on heterogeneous computational grids. It employs a client-server architecture to simplify the implementation. Its user interface has been designed to provide process control and state examination functions on a computation containing a large number of processes. It can find processes participating in distributed computations even when those processes were not created under debugger control. These process identification techniques work both on conventional distributed executions as well as those on a computational grid.

Hood, Robert↗

NASA NTRS2002

Autonomous planning and scheduling on the TechSat 21 mission

The Autonomous Sciencecraft Experiment (ASE) will fly onboard the Air Force TechSat 21 constellation of three spacecraft scheduled for launch in 2006. ASE uses onboard continuous planning, robust task and goal-based execution, model-based mode identification and reconfiguration, and onboard machine learning and pattern recognition to radically increase science return by enabling intelligent downlink selection and autonomous retargeting.

AI architectures applications intelligent agents m↗

NASA NTRSDate not supplied

A Safety-Driven Approach to Exploring and Comparing Air Traffic Management Concepts for Enabling Urban Air Mobility

There is broad recognition that the high tempo and density of Urban Air Mobility (UAM) operations will require identifying new Air Traffic Management (ATM) concepts to safely integrate UAM air traffic into the airspace alongside existing air traffic. However, the simulation models used to compare ATM concepts today are difficult to apply during the early stages of concept development and do not offer enough support in identifying potential new concepts. In addition, they have limited ability to evaluate ATM concepts in terms of safety, security, and other key emergent properties. Instead of using simulation to evaluate ATM concepts, this paper demonstrates how a safety-driven systems engineering approach based on Systems-Theoretic Accident Model and Processes (STAMP) can be used to design properties such as safety into an ATM system from the earliest stages of development. Using a hazard analysis technique called Systems-Theoretic Process Analysis (STPA), system requirements and the desired ATM behavior are derived. As an example, two possible ATM concepts to implement that behavior are compared to identify their safety-related benefits and tradeoffs. This new approach enables (1) systematic exploration of alternative ATM concepts and (2) identification of the safety-related tradeoffs between concepts as early as possible in the development process.

system safety↗

NASA NTRS2012

NASA Integrated Model Centric Architecture (NIMA) Model Use and Re-Use

This whitepaper accepts the goals, needs and objectives of NASA's Integrated Model-centric Architecture (NIMA); adds experience and expertise from the Constellation program as well as NASA's architecture development efforts; and provides suggested concepts, practices and norms that nurture and enable model use and re-use across programs, projects and other complex endeavors. Key components include the ability to effectively move relevant information through a large community, process patterns that support model reuse and the identification of the necessary meta-information (ex. history, credibility, and provenance) to safely use and re-use that information. In order to successfully Use and Re-Use Models and Simulations we must define and meet key organizational and structural needs: 1. We must understand and acknowledge all the roles and players involved from the initial need identification through to the final product, as well as how they change across the lifecycle. 2. We must create the necessary structural elements to store and share NIMA-enabled information throughout the Program or Project lifecycle. 3. We must create the necessary organizational processes to stand up and execute a NIMA-enabled Program or Project throughout its lifecycle. NASA must meet all three of these needs to successfully use and re-use models. The ability to Reuse Models a key component of NIMA and the capabilities inherent in NIMA are key to accomplishing NASA's space exploration goals. 11

Conroy, Mike↗

NASA NTRS2013

Development of Hybrid Product Breakdown Structure for NASA Ground Systems

The Product Breakdown Structure is traditionally a method of identification of the products of a project in a tree structure. It is a tool used to assess, plan, document, and display the equipment requirements for a project. It is part of a product based planning technique, and attempts to break down all components of a project in as much detail as possible, so that nothing is overlooked. The PBS for ground systems at the Kennedy Space Center is being developed to encompass the traditional requirements including the alignment of facility, systems, and components to the organizational hierarchy. The Ground Operations Product Breakdown Structure is a hybrid in nature in that some aspects of a work breakdown structure will be incorporated and merged with the Architecture Concept of Operations, Master Subsystem List, customer interface, and assigned management responsibility. The Ground Operations Product Breakdown Structure needs to be able to identify the flexibility of support differing customers (internal and external) usage of ground support equipment within the Kennedy Space Center launch and processing complex. The development of the Product Breakdown Structure is an iterative activity Initially documenting the organization hierarchy structure and relationships. The Product Breakdown Structure identifies the linkage between the customer program requirements, allocation of system resources, development of design goals, and identification logistics products. As the Product Breakdown Structure progresses the incorporation of the results of requirement planning for the customer occurs identifying facility needs and systems. The mature Product Breakdown Structure is baselined with a hierarchical drawing, the Product Breakdown Structure database, and an associated document identifying the verification of the data through the life cycle of the program/product line. This paper will document, demonstrate, and identify key aspects of the life cycle of a Hybrid Product Breakdown Structure. The purpose is to show how a project management and system engineering approach can be utilized for providing flexible customer service in an evolving manned space flight launch processing environment.

Monaghan, Mark W.↗

NASA NTRS2013

Development of Hybrid Product Breakdown Structure for NASA Ground Systems

Monaghan, Mark W.↗

NASA NTRS2016

Rapid Application of Space Effects for the Small Satellites Systems and Services Symposium

NASA Ames Research Center (ARC) has engaged Military Branches, the Department of Defense, and other Government Agencies in successful partnerships to design, develop, deliver and support various space effects capabilities and space vehicles on timeline of need. Contracts with Industry are in place to execute operational and enabler missions using physical and informational infrastructures including Responsive Manufacturing capabilities and Digital Assurance. The intent is to establish a secure, web-enabled "store front" for ordering and delivering any capabilities required as defined by the users and directed by NASA ARC and Partner Organizations. The capabilities are envisioned to cover a broad range and include 6U CubeSats, 50-100 kg Space Vehicles, Modular Space Vehicle architecture variations, as well as rapid payload integration on various Bus options. The paper will discuss the efforts underway to demonstrate autonomous manufacturing of low-volume, high-value assets, to validate the ability of autonomous digital techniques to provide Mission Assurance, and to demonstrate cost savings through the identification, characterization, and utilization of Responsive Space components. The culmination of this effort will be the integration of several 6U satellites and their launch in 2016.

Small Satellite Systems↗

NASA NTRS2007

International Planetary Data Alliance (IPDA) Information Model

This document is the third deliverable of the International Planetary Data Alliance (IPDA) Archive Data Standards Requirements Identification project. The goal of the project is to identify a subset of the standards currently in use by NASAs Planetary Data System (PDS) that are appropriate for internationalization. As shown in the highlighted sections of Figure 1, the focus of this project is the Information Model component of the Data Architecture Standards, namely the object models, a data dictionary, and a set of data formats.

information model↗

NASA NTRS2018

Using the cFS Command and Data Dictionary (CCDD) to Automate Software Development on Habulous

Final paper is attached. The NASA developed Core Flight System (cFS) is a reusable software architecture that has been used on multiple spaceflight missions. By using this framework, missions are able to reuse code from other missions, as well as leverage deployment onto similar computer architectures (i.e. not "reinvent the wheel" on each new mission). The success in the cFS concept can be seen in the large number of projects using cFS at FSW-2018. The Habulous project is an Earth-based testbed, used for hardware and software that may one day be used on a future space habitat unit, with many participating groups from various NASA centers and aerospace organizations around the country. The distributed nature of the various teams mean that defining (and following) an interface definition is critical on the project. Additionally, since various groups use various types of computer hardware (32/64-bit, big/little endian, Linux/VxWorks/Windows) many additional complications exist in interfacing all the various components into a final integrated system. cFS is used on the majority the flight software (FSW) in running in Habulous. But some subsystems have elected to not use cFS, and use a software bridge (called SBN_lib) to interact with the other cFS nodes in Habulous. In order to most efficiently develop the FSW, a central database is used to define and store each message sent by cFS. A Command and Data Dictionary (CDD) is something nearly universal on spacecraft, but as a team we worked to develop the CDD before the SW development was complete, and not treat it like "as built" documentation. To manage the CDD, the cFS Command and Data Dictionary (CCDD) tool was chosen (available from NASA as open source software). The CCDD tool has successfully been used to automate/autocode a large amount of software used on Habulous, as we are hoping to use it to define even more items in the future (time-triggered Ethernet (TTE) network maps, CPU scheduling). Additionally, Habulous has been exploring the use of cFS on wildly heterogeneous CPUs, and how to coordinate all those various machines using/extending the software bus â€“ network (SBN) application in cFS, as well as TTE to coordinate message passing between various synchronized machines. The major topics to be covered in the presentation are: (1) Updating to the CCSDS_v2 extended headers (and using CPU# as subsystem ID). (2) Managing all the message identification numbers for each cFS message sent/received on any of the various CPUs. (3) Using the CCDD information to automatically generate the C-header files that define the structure for all software bus (SB) commands/telemetry messages. (4) Using the CCDD to automatically generate XML Telemetry and Command Exchange (XTCE) files, which streams display production/integration/testing in a web based display architecture (5) Extending/customizing SBN to pass messages among computers on multiple networks. (6) Using "Protobetter" inside SBN to manage different endian-ness/architectures. (7) Using SBN_lib to allow non-cFS node to communicate with cFS nodes. (8) Developing TTE network and schedule tables for all the various CPUs to use.

Hirsh, Robert L.↗

NASA NTRSDate not supplied

Entry, Descent, and Landing Analysis for the OSIRIS-REx Sample Return Capsule

The Origins, Spectral Interpretation, Resource Identification, and Security – Regolith Explorer (OSIRIS-REx) sample return capsule (SRC) returned to Earth on September 24, 2023, safely landing in the Utah Test and Training Range (UTTR). To ensure a safe and successful landing, a pair of high-fidelity EDL simulations, based on the Program to Optimize Simulated Trajectories (POST) architecture, were used to regularly assess the latest orbit determination (OD) solution from the navigation team, making predictions on Entry, Descent, and Landing (EDL) performance and SRC landing location. The results from these analyses fed into the decision processes for the final trajectory correction maneuvers (TCM’s) and SRC release. The models and methods of analysis will be discussed and a comparison of the final pre-entry landing prediction against the observed landing location will be presented along with an assessment of the best estimates of day-of-entry environmental conditions.

Scott R Francis↗

NASA NTRS2002

A provisional regulatory gene network for specification of endomesoderm in the sea urchin embryo

We present the current form of a provisional DNA sequence-based regulatory gene network that explains in outline how endomesodermal specification in the sea urchin embryo is controlled. The model of the network is in a continuous process of revision and growth as new genes are added and new experimental results become available; see http://www.its.caltech.edu/~mirsky/endomeso.htm (End-mes Gene Network Update) for the latest version. The network contains over 40 genes at present, many newly uncovered in the course of this work, and most encoding DNA-binding transcriptional regulatory factors. The architecture of the network was approached initially by construction of a logic model that integrated the extensive experimental evidence now available on endomesoderm specification. The internal linkages between genes in the network have been determined functionally, by measurement of the effects of regulatory perturbations on the expression of all relevant genes in the network. Five kinds of perturbation have been applied: (1) use of morpholino antisense oligonucleotides targeted to many of the key regulatory genes in the network; (2) transformation of other regulatory factors into dominant repressors by construction of Engrailed repressor domain fusions; (3) ectopic expression of given regulatory factors, from genetic expression constructs and from injected mRNAs; (4) blockade of the beta-catenin/Tcf pathway by introduction of mRNA encoding the intracellular domain of cadherin; and (5) blockade of the Notch signaling pathway by introduction of mRNA encoding the extracellular domain of the Notch receptor. The network model predicts the cis-regulatory inputs that link each gene into the network. Therefore, its architecture is testable by cis-regulatory analysis. Strongylocentrotus purpuratus and Lytechinus variegatus genomic BAC recombinants that include a large number of the genes in the network have been sequenced and annotated. Tests of the cis-regulatory predictions of the model are greatly facilitated by interspecific computational sequence comparison, which affords a rapid identification of likely cis-regulatory elements in advance of experimental analysis. The network specifies genomically encoded regulatory processes between early cleavage and gastrula stages. These control the specification of the micromere lineage and of the initial veg(2) endomesodermal domain; the blastula-stage separation of the central veg(2) mesodermal domain (i.e., the secondary mesenchyme progenitor field) from the peripheral veg(2) endodermal domain; the stabilization of specification state within these domains; and activation of some downstream differentiation genes. Each of the temporal-spatial phases of specification is represented in a subelement of the network model, that treats regulatory events within the relevant embryonic nuclei at particular stages. (c) 2002 Elsevier Science (USA).

Non-NASA Center↗

NASA NTRS2011

Putting the Power of Configuration in the Hands of the Users

Goal was to reduce the overall cost of human space flight while maintaining the most demanding standards for safety and mission success. In support of this goal, a project team was chartered to replace 18 legacy Space Shuttle nonconformance processes and systems with one fully integrated system Problem Reporting and Corrective Action (PRACA) processes provide a closed-loop system for the identification, disposition, resolution, closure, and reporting of all Space Shuttle hardware/software problems PRACA processes are integrated throughout the Space Shuttle organizational processes and are critical to assuring a safe and successful program Primary Project Objectives Develop a fully integrated system that provides an automated workflow with electronic signatures Support multiple NASA programs and contracts with a single "system" architecture Define standard processes, implement best practices, and minimize process variations

Al-Shihabi, Mary-Jo↗

NASA NTRS1987

Fault-tolerant computer architecture based on INMOS transputer processor

Redundant processing was used for several years in mission flight systems. In these systems, more than one processor performs the same task at the same time but only one processor is actually in real use. A fault-tolerance computer architecture based on the features provided by INMOS Transputers is presented. The Transputer architecture provides several communication links that allow data and command communication with other Transputers without the use of a bus. Additionally the Transputer allows the use of parallel processing to increase the system speed considerably. The processor architecture consists of three processors working in parallel keeping all the processors at the same operational level but only one processor is in real control of the process. The design allows each Transputer to perform a test to the other two Transputers and report the operating condition of the neighboring processors. A graphic display was developed to facilitate the identification of any problem by the user.

Ortiz, Jorge L.↗

NASA NTRS1990

Neural networks for function approximation in nonlinear control

Two neural network architectures are compared with a classical spline interpolation technique for the approximation of functions useful in a nonlinear control system. A standard back-propagation feedforward neural network and a cerebellar model articulation controller (CMAC) neural network are presented, and their results are compared with a B-spline interpolation procedure that is updated using recursive least-squares parameter identification. Each method is able to accurately represent a one-dimensional test function. Tradeoffs between size requirements, speed of operation, and speed of learning indicate that neural networks may be practical for identification and adaptation in a nonlinear control environment.

Linse, Dennis J.↗

NASA NTRS2005

Line of Sight Stabilization of James Webb Space Telescope

The James Webb Space Telescope (JWST) builds upon the successful flight experience of the Chandra Xray Telescope by incorporating an additional LOS pointing servo to meet the more stringent pointing requirements. The LOS pointing servo, referred to in JWST as the Fine Guidance Control System (FGCS), will utilize a Fine Guidance Sensor (FGS) as the sensor, and a Fine Steering Mirror (FSM) as the actuator. The FSM is a part of the Optical Telescope Element (OTE) and is in the optical path between the tertiary mirror and the instrument focal plane, while the FGS is part of the Integrated Science Instrument Module (ISIM). The basic Chandra spacecraft bus attitude control and determination architecture, utilizing gyros, star trackers/aspect camera, and reaction wheels, is retained for JWST. This system has achieved pointing stability of better than 0.5 arcseconds. To reach the JWST requirements of milli-arcsecond pointing stability with this ACS hardware, the local FGCS loop is added to the optical path. The FGCS bandwidth is about 2.0 Hz and will therefore attenuate much of the spacecraft ACS induced low frequency jitter. In order to attenuate the higher frequency (greatet than 2.0 Hz) disturbances associated with reaction wheel static and dynamic imbalances, as well as bearing run-out, JWST will employ a two-stage passive vibration isolation system consisting of (1) 7.0 Hz reaction wheel isolators between each reaction wheel and the spacecraft bus, and (2) a 1.0 Hz tower isolator between the spacecraft bus and the Optical Telescope Element (OTE). In order to sense and measure the LOS, the FGS behaves much like an autonomous star tracker that has a very small field of view and uses the optics of the telescope. It performs the functions of acquisition, identification and tracking of stars in its 2.5 x 2.5 arcminute field of view (FOV), and provides the centroid and magnitude of the selected star for use in LOS control. However, since only a single star is being tracked at any time within the FGS FOV there is only tip and tilt information; rotation about the FGS LOS will not be sensed. The FGCS uses the FSM to move the guide star within the FGS FOV and place the centroid of the guide star at any desired position within the FGS focal plane. Using this architecture allows the FGCS to correct the low frequency LOS jitter that is induced by the spacecraft ACS in pitch and yaw, and achieve the milli-arcsecond pointing stability required by JWST. The less stringent ISIM FOV roll performance will be provided solely by the ACS, using the spacecraft gyros and star trackers. Since the FSM is in the optical path, the pointing stabilrty of a science object in any of the instruments will be similar to that of the guide star LOS.

Meza, Luis↗

NASA NTRS1984

AIPS technology survey report

The results of a technology survey conducted for the NASA/JSC by the CSDL during Phase 1 of the NASA Advanced Information Processing System (AIPS) program at the CSDL are discussed. The purpose of the survey was to ensure that all technology relevant to the configuration, design, development, verification, implementation, and validation of an advanced information processing system, whether existing or under development and soon to be available, would be duly considered in the development of the AIPS. The emphasis in the survey was on technology items which were clearly relevant to the AIPS. Requirements were developed which guided the planning of contacts with the outside sources to be surveyed, and established practical limits on the scope and content of the Technology Survey. Subjects surveyed included architecture, software, hardware, methods for evaluation of reliability and performance, and methods for the verification of the AIPS design and the validation of the AIPS implementation. Survey requirements and survey results in each of these areas are presented, including analyses of the potential effects on the AIPS development process of using or not using the surveyed technology items. Another output of the survey was the identification of technology areas of particular relevance to the AIPS and for which further development, in some cases by the CSDL and in some cases by the NASA, would be fruitful. Appendices are provided in which are presented: (1) reports of some of the actual survey interactions with industrial and other outside information sources; (2) the literature list from the comprehensive literature survey which was conducted; (3) reduced-scale images of an excerpt ('Technology Survey' viewgraphs) from the set of viewgraphs used at the 14 April 1983 Preliminary Requirements Review by the CSDL for the NASA; and (4) reduced-scale images of the set of viewgraphs used in the AIPS Technology Survey Review presentation to the NASA monitors by the CSDL at the NASA Langley Research Center on 28 Sep. 1983.

Ogletree, Glenn↗

NASA NTRSDate not supplied

Surface Transportation of the Common Habitat from Lander to Habitation Zone

The Common Habitat Architecture is a feasibility study surrounding the use of an SLS core stage liquid oxygen tank as the pressure vessel for a long-duration habitat intended for use in multiple gravity environments. The Common Habitat is used within this study as the primary habitation element in both Moon and Mars surface base camps. The Common Habitat Architecture offloads the Common Habitat from its lander and transports it to a Habitation Zone instead of leaving the habitat integrated with the lander. In this study, the Landing Zone is assumed to be approximately 3.5 kilometers from the Habitation Zone. Given the physical size and estimated 90-ton mass of the Common Habitat, a four-week trade study encompassing Moon and Mars lander identification, offloading, surface transport, and emplacement was conducted in February 2021 to assess whether there are any credible options for landing the Common Habitat on the Moon or Mars and deliver it to its intended point of use. Constrained to use only public data, the study applied subject matter expert opinion to each component of the study. The surface transportation component of the trade study assumes the habitat has been successfully offloaded from its lander and is at a point of handover to the surface transportation system. It is assumed that there are no crew present, and all human operations are performed remotely by Mission Control personnel. Three core cargo handling elements from prior NASA studies were used as the basis from which to derive surface transportation options – the Chariot, the All-Terrain Hex-Limbed Extra-Terrestrial Explorer, and the Lightweight Surface Manipulator System. Variations and hybrid combinations of these elements were used to develop transportation options for the Moon and Mars, given different habitat masses. Ultimately, several potentially feasible solutions were identified, and a solution was recommended that is common to both the Moon and Mars, with the potential to use a dissimilar system as a backup during lunar Common Habitat delivery. Next steps for sizing and additional development and analysis of the recommended surface transportation system are included as forward work.

Surface Mobility↗