Search NASA⌕ Search

SEARCH · Search NASA

Results for “building systems”

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 55 records · Page 3

NASA's Space Launch System: Momentum Builds Towards First Launch

NASA's Space Launch System (SLS) is gaining momentum programmatically and technically toward the first launch of a new exploration-class heavy lift launch vehicle for international exploration and science initiatives. The SLS comprises an architecture that begins with a vehicle capable of launching 70 metric tons (t) into low Earth orbit. Its first mission will be the launch of the Orion Multi-Purpose Crew Vehicle (MPCV) on its first autonomous flight beyond the Moon and back. SLS will also launch the first Orion crewed flight in 2021. SLS can evolve to a 130-t lift capability and serve as a baseline for numerous robotic and human missions ranging from a Mars sample return to delivering the first astronauts to explore another planet. Managed by NASA's Marshall Space Flight Center, the SLS Program formally transitioned from the formulation phase to implementation with the successful completion of the rigorous Key Decision Point C review in 2014. At KDP-C, the Agency Planning Management Council determines the readiness of a program to go to the next life-cycle phase and makes technical, cost, and schedule commitments to its external stakeholders. As a result, the Agency authorized the Program to move forward to Critical Design Review, scheduled for 2015, and a launch readiness date of November 2018. Every SLS element is currently in testing or test preparations. The Program shipped its first flight hardware in 2014 in preparation for Orion's Exploration Flight Test-1 (EFT-1) launch on a Delta IV Heavy rocket in December, a significant first step toward human journeys into deep space. Accomplishments during 2014 included manufacture of Core Stage test articles and preparations for qualification testing the Solid Rocket Boosters and the RS-25 Core Stage engines. SLS was conceived with the goals of safety, affordability, and sustainability, while also providing unprecedented capability for human exploration and scientific discovery beyond Earth orbit. In an environment of economic challenges, the nationwide SLS team continues to meet ambitious budget and schedule targets through the studied use of hardware, infrastructure, and workforce investments the United States has already made in the last half century, while selectively using new technologies for design, manufacturing, and testing, as well as streamlined management approaches that have increased decision velocity and reduced associated costs. This paper will summarize recent SLS Program technical accomplishments, as well as the challenges and opportunities ahead for the most powerful and capable launch vehicle in history.

May, Todd↗

Building Automation System Replacement and Improvements during Concurrent Integration and Testing for the Spacecraft Systems Development and Integration Facility

The Spacecraft Systems Development and Integration Facility (SSDIF), the premier cleanroom for NASA Goddard Space Flight Center (GSFC), has gone through multiple iterations of changes to its building automation system (BAS). NASA flight projects require more stringent environmental controls for temperature, humidity, air exchange rates, and pressurization. This led to increasingly difficult circumstances with replacing and improving the BAS during Integration and Testing (I&T) operations. The SSDIF was partially transitioned to a new BAS during November and December of 2023. Transition occurred in a live environment, while regular I&T activities resumed for the Roman Space Telescope. This resulted in the development and execution of a comprehensive method of procedure. Strategies such as sequencing equipment transition, and using temporary controls for critical equipment, avoided detriments to cleanroom environment. While the new BAS was being built, data points on the previous system would become obsolete, leading to data gaps and uncertainties. Critical data points were distinguished and trended on the new system, providing key insights on equipment functionality, while the BAS was completed. Control hunting and environmental deviations were persistent cases with the SSDIF. In some instances, proportional-integral-derivative (PID) tuning was implemented on current logic to bring smooth PID loop hunting. In other situations, controls logic was completely altered by changing setpoints or sequences. This provided greater laminar flow, more stable pressurization, and improved temperature and humidity controls. This paper documents the transitionary procedure to a new BAS, the improvements made, and challenges faced when altering a BAS during I&T operations.

Cleanroom↗

Challenges in building intelligent systems for space mission operations

The purpose here is to provide a top-level look at the stewardship functions performed in space operations, and to identify the major issues and challenges that must be addressed to build intelligent systems that can realistically support operations functions. The focus is on decision support activities involving monitoring, state assessment, goal generation, plan generation, and plan execution. The bottom line is that problem solving in the space operations domain is a very complex process. A variety of knowledge constructs, representations, and reasoning processes are necessary to support effective human problem solving. Emulating these kinds of capabilities in intelligent systems offers major technical challenges that the artificial intelligence community is only beginning to address.

Hartman, Wayne↗

Building intelligent systems - Artificial intelligence research at NASA Ames Research Center

The basic components that make up the goal of building autonomous intelligent systems are discussed, and ongoing work at the NASA Ames Research Center is described. It is noted that a clear progression of systems can be seen through research settings (both within and external to NASA) to Space Station testbeds to systems which actually fly on the Space Station. The starting point for the discussion is a 'truly' autonomous Space Station intelligent system, responsible for a major portion of Space Station control. Attention is given to research in fiscal 1987, including reasoning under uncertainty, machine learning, causal modeling and simulation, knowledge from design through operations, advanced planning work, validation methodologies, and hierarchical control of and distributed cooperation among multiple knowledge-based systems.

Friedland, Peter↗

Building intelligent systems: Artificial intelligence research at NASA Ames Research Center

The basic components that make up the goal of building autonomous intelligent systems are discussed, and ongoing work at the NASA Ames Research Center is described. It is noted that a clear progression of systems can be seen through research settings (both within and external to NASA) to Space Station testbeds to systems which actually fly on the Space Station. The starting point for the discussion is a truly autonomous Space Station intelligent system, responsible for a major portion of Space Station control. Attention is given to research in fiscal 1987, including reasoning under uncertainty, machine learning, causal modeling and simulation, knowledge from design through operations, advanced planning work, validation methodologies, and hierarchical control of and distributed cooperation among multiple knowledge-based systems.

Friedland, P.↗

Managing computer-controlled operations

A detailed discussion of Launch Processing System Ground Software Production is presented to establish the interrelationships of firing room resource utilization, configuration control, system build operations, and Shuttle data bank management. The production of a test configuration identifier is traced from requirement generation to program development. The challenge of the operational era is to implement fully automated utilities to interface with a resident system build requirements document to eliminate all manual intervention in the system build operations. Automatic update/processing of Shuttle data tapes will enhance operations during multi-flow processing.

Plowden, J. B.↗

Aerospace power systems - A building surge

Dramatic changes in both aircraft and space power systems are being projected. The primary driver is mission cost, although more stringent performance requirements are also being imposed. The order-of-magnitude reductions anticipated in space power, both in cost and specific mass, are partially related to the advent of the Shuttle and the continuing evolution of the STS over the next decade. Automation, microcircuitry, batteries, and structural materials are common aircraft and space technology needs.

Barthelemy, R. R.↗

Software packager user's guide

Software integration is a growing area of concern for many programmers and software managers because the need to build new programs quickly from existing components is greater than ever. This includes building versions of software products for multiple hardware platforms and operating systems, building programs from components written in different languages, and building systems from components that must execute on different machines in a distributed network. The goal of software integration is to make building new programs from existing components more seamless -- programmers should pay minimal attention to the underlying configuration issues involved. Libraries of reusable components and classes are important tools but only partial solutions to software development problems. Even though software components may have compatible interfaces, there may be other reasons, such as differences between execution environments, why they cannot be integrated. Often, components must be adapted or reimplemented to fit into another application because of implementation differences -- they are implemented in different programming languages, dependent on different operating system resources, or must execute on different physical machines. The software packager is a tool that allows programmers to deal with interfaces between software components and ignore complex integration details. The packager takes modular descriptions of the structure of a software system written in the package specification language and produces an integration program in the form of a makefile. If complex integration tools are needed to integrate a set of components, such as remote procedure call stubs, their use is implied by the packager automatically and stub generation tools are invoked in the corresponding makefile. The programmer deals only with the components themselves and not the details of how to build the system on any given platform.

Callahan, John R.↗

An Autonomous Vault-Building Robot System for Creating Spanning Structures

Research in autonomous robots for construction has largely focused on ground-based robots whose reach constrains the size of what they can build, or on climbing or aerial robots that build solid or unroofed structures. Autonomous construction of larger, multistory buildings, or bridges spanning unsupported distances, would require robots that build sturdy structures supporting their own weight. In this paper, we present VaultBot, a system of autonomous robots that build a load-bearing spanning vault using identical modular blocks. The custom blocks employ mechanical and other features to facilitate robotic manipulation and locomotion, and can be removed from and replaced in an assembled structure as a way of repairing damage. We characterize the system's performance and failure modes, and demonstrate reliable autonomous assembly for a structure composed of 46 blocks. Blocks can be made collapsible and deployable as a way of reducing mass and volume that must be transported to a construction site. Such a system could be used to help enable construction of protective shelters in challenging environments, such as disaster relief scenarios, arctic settings, or extraterrestrial habitats.

Nathan Melenbrink↗

Inductive knowledge acquisition experience with commercial tools for space shuttle main engine testing

Since 1984, an effort has been underway at Rocketdyne, manufacturer of the Space Shuttle Main Engine (SSME), to automate much of the analysis procedure conducted after engine test firings. Previously published articles at national and international conferences have contained the context of and justification for this effort. Here, progress is reported in building the full system, including the extensions of integrating large databases with the system, known as Scotty. Inductive knowledge acquisition has proven itself to be a key factor in the success of Scotty. The combination of a powerful inductive expert system building tool (ExTran), a relational data base management system (Reliance), and software engineering principles and Computer-Assisted Software Engineering (CASE) tools makes for a practical, useful and state-of-the-art application of an expert system.

Modesitt, Kenneth L.↗

ART/Ada design project, phase 1

An Ada-Based Expert System Building Tool Design Research Project was conducted. The goal was to investigate various issues in the context of the design of an Ada-based expert system building tool. An attempt was made to achieve a comprehensive understanding of the potential for embedding expert systems in Ada systems for eventual application in future projects. The current status of the project is described by introducing an operational prototype, ART/Ada. How the project was conducted is explained. The performance of the prototype is analyzed and compared with other related works. Future research directions are suggested.

Source record↗

Expert system terms and building tools

The characteristics of an Expert System Building Tool (ESBT) capable of inference and hypothetical reasoning are discussed. The inference capabilities of ESBTs allow such functions as classification, design-synthesis, forecasting, decision-aiding, scheduling and planning, real-time monitoring, situation assessment, the discovery of novel relations, and debugging. ESBTs are noted to have made possible order-of-magnitude improvements in expert system construction. Higher-end ESBTs are moving from LISP machines to less expensive workstations, and lower-end ones are appearing on PCs.

Gevarter, William B.↗

Low cost miniature data collection platform

The development of the RF elements of a telecommunications package involved detailed study and analysis of concepts and techniques followed by laboratory testing and evaluation of designs. The design goals for a complete telecommunications package excluding antenna were a total weight of 300 grams, in a total volume of 400 cu cm with a capability of unattended operation for a period of six months. Of utmost importance is extremely low cost when produced in lots of 10,000. Early in the program it became apparent that a single Miniature Data Collection Platform would not satisfy all users. A single high efficiency system would not satisfy a user who had available a large battery capacity but required a low cost system. Conversely, the low cost system would not satisfy the end user who had a very limited battery capacity. A system design to satisfy these varied requirements was implemented by designing several versions of the system building blocks and then constructing three systems from these building blocks.

Source record↗

The Transportable Applications Environment - An interactive design-to-production development system

An account is given of the design philosophy and architecture of the Transportable Applications Environment (TAE), an executive program binding a system of applications programs into a single, easily operable whole. TAE simplifies the job of a system developer by furnishing a stable framework for system-building; it also integrates system activities, and cooperates with the host operating system in order to perform such functions as task-scheduling and I/O. The initial TAE human/computer interface supported command and menu interfaces, data displays, parameter-prompting, error-reporting, and online help. Recent extensions support graphics workstations with a window-based, modeless user interface.

Perkins, Dorothy C.↗

Automated Predictive Diagnosis (APD): A 3-tiered shell for building expert systems for automated predictions and decision making

The APD software features include: On-line help, Three level architecture, (Logic environments, Setup/Application environment, Data environment), Explanation capability, and File handling. The kinds of experimentation and record keeping that leads to effective expert systems is facilitated by: (1) a library of inferencing modules (in the logic environment); (2) an explanation capability which reveals logic strategies to users; (3) automated file naming conventions; (4) an information retrieval system; and (5) on-line help. These aid with effective use of knowledge, debugging and experimentation. Since the APD software anticipates the logical rules becoming complicated, it is embedded in a production system language (CLIPS) to insure the full power of the production system paradigm of CLIPS and availability of the procedural language C. The development is discussed of the APD software and three example applications: toy, experimental, and operational prototype for submarine maintenance predictions.

Steib, Michael↗

CLIPS/Ada: An Ada-based tool for building expert systems

Clips/Ada is a production system language and a development environment. It is functionally equivalent to the CLIPS tool. CLIPS/Ada was developed in order to provide a means of incorporating expert system technology into projects where the use of the Ada language had been mandated. A secondary purpose was to glean information about the Ada language and its compilers. Specifically, whether or not the language and compilers were mature enough to support AI applications. The CLIPS/Ada tool is coded entirely in Ada and is designed to be used by Ada systems that require expert reasoning.

White, W. A.↗

NGST/XRCF Design and Build Wavescope System Pallet

Based on the successful Wavescope demonstration at MSFC at the end of March, the decision was made by the optical testing team to purchase an upgraded Wavescope from AOA. The MSFC version would include: a higher resolution camera (1000 x 1000 pixels); a higher density lenslet array (150 x 150); updated software; and longer cables (to accommodate the remote operation of the Wavescope optical head which was resident in the Beam Guide Tube). The AOA proposal for the new instrument was received in mid-April, and delivered to MSFC in mid-July. A considerable amount of effort was expended to provide the infrastructure needed for Wavescope operation, and to incorporate it into the overall test system. This was provided by the Wavescope System Pallet (WSP) built by UAH. The WSP is illustrated. Several instruments are incorporated on this pallet. These include the: Wavescope optical head; a PDI wavefront sensor; a point spread function sensor; a Leica light-based distance measuring sensor. In addition there is a single mode fiber point source (fed from a separate source pallet) which serves both as a reference for the Wavescope and as a source point for the test mirror. There is a dual function lens which both collimates the beam from the test image point, and images the test mirror onto the lenslet array. There is a high quality Collimator which can provide a flat input wavefront directly into the Wavescope. There are also various aids such as an alignment laser, an alignment telescope, alignment sticks and apertures. The WSP was delivered to MSFC on 7/28/99. An picture shows the WSP installed in the Guide Tube at the X-Ray Calibration Facility (XRCF).

Geary, Joe↗

Design for Verification: Using Design Patterns to Build Reliable Systems

Components so far have been mainly used in commercial software development to reduce time to market. While some effort has been spent on formal aspects of components, most of this was done in the context of programming language or operating system framework integration. As a consequence, increased reliability of composed systems is mainly regarded as a side effect of a more rigid testing of pre-fabricated components. In contrast to this, Design for Verification (D4V) puts the focus on component specific property guarantees, which are used to design systems with high reliability requirements. D4V components are domain specific design pattern instances with well-defined property guarantees and usage rules, which are suitable for automatic verification. The guaranteed properties are explicitly used to select components according to key system requirements. The D4V hypothesis is that the same general architecture and design principles leading to good modularity, extensibility and complexity/functionality ratio can be adapted to overcome some of the limitations of conventional reliability assurance measures, such as too large a state space or too many execution paths.

Mehlitz, Peter C.↗