Search NASA⌕ Search

SEARCH · Search NASA

Results for “Systems Engineering and Program Integration”

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,171 records · Page 65

Thermal & Fluids Analysis and the NASA Launch Services Program

This presentation provides the What, Where, Why, and How of the thermal and fluids analysis disciplines within the Launch Services Program (LSP). The LSP manages all commercial launch services to match NASA science mission payloads to the appropriate launch system. The Flight Analysis Division within the LSP provides multi disciplinary analysis support of these flight systems to characterize payload and launch vehicle environments from payload mate to upper stage through on orbit separation. The Thermal Analysis and Fluids Analysis teams are two distinct groups within the Flight Analysis Division of the LSP who cover a wide array of standard and non standard analytical tasks. These teams offer a significant benefit to both the payload design and integration team and the launch vehicle supplier. These benefits, along with the tools and methods are described in this talk to inform engineers and analysts from both sides of the launch system interface how the LSP Thermal and Fluids Analysis teams can benefit the success of their mission.

Fortenberry, Cindy↗

Small Engine Technology (SET). Task 33: Airframe, Integration, and Community Noise Study

Task Order 33 had four primary objectives as follows: (1) Identify and prioritize the airframe noise reduction technologies needed to accomplish the NASA Pillar goals for business and regional aircraft. (2) Develop a model to estimate the effect of jet shear layer refraction and attenuation of internally generated source noise of a turbofan engine on the aircraft system noise. (3) Determine the effect on community noise of source noise changes of a generic turbofan engine operating from sea level to 15,000 feet. (4) Support lateral attenuation experiments conducted by NASA Langley at Wallops Island, VA, by coordinating opportunities for Contractor Aircraft to participate as a noise source during the noise measurements. Noise data and noise prediction tools, including airframe noise codes, from the NASA Advanced Subsonic Technology (AST) program were applied to assess the current status of noise reduction technologies relative to the NASA pillar goals for regional and small business jet aircraft. In addition, the noise prediction tools were applied to evaluate the effectiveness of airframe-related noise reduction concepts developed in the AST program on reducing the aircraft system noise. The AST noise data and acoustic prediction tools used in this study were furnished by NASA.

Lieber, Lys S.↗

IDEAL: A methology for developing information systems

As a result of improved capabilities obtained through current computer technologies, application programs and expert systems, Enterprises are being designed or upgraded to be highly integrated and automated information systems. To design or modify Enterprises, it is necessary to first define what functions are to be performed within the Enterprise, identify which functions are potential candidates for automation, and what automated or expert systems are available, or must be developed, to accomplish the selected function. Second, it is necessary to define and analyze the informational requirements for each function along with the informational relationships among the functions so that a database structure can be established to support the Enterprise. To perform this type of system design, an integrated set of analysis tools is required to support the information analysis process. The IDEAL (Integrated Design and Engineering Analysis Languages) methodology provides this integrated set of tools and is discussed.

Evers, Ken H.↗

Spacecraft contamination programs within the Air Force Systems Command Laboratories

Spacecraft contamination programs exist in five independent AFSC organizations: Geophysics Laboratory (GL), Arnold Engineering and Development Center (AEDC), Rome Air Development Center (RADC/OSCE), Wright Research and Development Center (MLBT), Armament Laboratory (ATL/SAI), and Space Systems Division (SSD/OL-AW). In addition, a sizable program exists at Aerospace Corp. These programs are complementary, each effort addressing a specific area of expertise: GL's effort is aimed at addressing the effects of on-orbit contamination; AEDC's effort is aimed at ground simulation and measurement of optical contamination; RADC's effort addresses the accumulation, measurement, and removal of contamination on large optics; MLBT's effort is aimed at understanding the effect of contamination on materials; ATL's effort is aimed at understanding the effect of plume contamination on systems; SSD's effort is confined to the integration of some contamination experiments sponsored by SSD/CLT; and Aerospace Corp.'s effort is aimed at supporting the needs of the using System Program Offices (SPO) in specific areas, such as contamination during ground handling, ascent phase, laboratory measurements aimed at understanding on-orbit contamination, and mass loss and mass gain in on-orbit operations. These programs are described in some detail, with emphasis on GL's program.

Murad, Edmond↗

Offloading techniques for large deployable space structures

The validation and verification of large deployable space structures are continual challenges which face the integration and test engineer today. Spar Aerospace Limited has worked on various programs in which such structure validation was required and faces similar tasks in the future. This testing is reported and the different offloading and deployment methods which were used, as well as the proposed methods which will be used on future programs, are described. Past programs discussed include the Olympus solar array ambient and thermal vacuum deployments, and the Anik-E array and reflector deployments. The proposed MSAT reflector and boom ambient deployment tests, as well as the proposed RADARSAT Synthetic Aperture Radar (SAR) ambient and thermal vacuum deployment tests will also be presented. A series of tests relating to various component parts of the offloading equipment systems was required. These tests included the characterization and understanding of linear bearings and large (180 in-lbf) constant force spring motors in a thermal vacuum environment, and the results from these tests are presented.

Caravaggio, Levino↗

Feasibility study of an Integrated Program for Aerospace-vehicle Design (IPAD) system. Volume 6: Implementation schedule, development costs, operational costs, benefit assessment, impact on company organization, spin-off assessment, phase 1, tasks 3 to 8

A baseline implementation plan, including alternative implementation approaches for critical software elements and variants to the plan, was developed. The basic philosophy was aimed at: (1) a progressive release of capability for three major computing systems, (2) an end product that was a working tool, (3) giving participation to industry, government agencies, and universities, and (4) emphasizing the development of critical elements of the IPAD framework software. The results of these tasks indicate an IPAD first release capability 45 months after go-ahead, a five year total implementation schedule, and a total developmental cost of 2027 man-months and 1074 computer hours. Several areas of operational cost increases were identified mainly due to the impact of additional equipment needed and additional computer overhead. The benefits of an IPAD system were related mainly to potential savings in engineering man-hours, reduction of design-cycle calendar time, and indirect upgrading of product quality and performance.

Garrocq, C. A.↗

External Tank Program - Legacy of Success

The largest single element of Space Shuttle is the External Tank (ET), which serves as the structural backbone of the vehicle during ascent and provides liquid propellants to the Orbiter s three Main Engines. The ET absorbs most of the seven million pounds of thrust exerted by the Solid Rocket Boosters and Main Engines. The design evolved through several block changes, reducing weight each time. Because the tank flies to orbital velocity with the Space Shuttle Orbiter, minimization of weight is mandatory, to maximize payload performance. The initial configuration, the standard weight tank, weighed 76,000 pounds and was an aluminum 2219 structure. The light weight tank weighed 66,000 pounds and flew 86 missions. The super light weight tank weighed 58,500 pounds and was primarily an aluminum-lithium structure. The final configuration and low weight enabled system level performance sufficient for assembly of the International Space Station in a high inclination orbit, vital for international cooperation. Another significant challenge was the minimization of ice formation on the cryogenic tanks. This was essential due to the system configuration and the choice of ceramic thermal protection system materials on the Orbiter. Ice would have been a major debris hazard. Spray on foam insulation materials served multiple functions including thermal insulation, conditioning of cryogenic propellants, and thermal protection for the tank structure during ascent and entry. The tank is large, and unique manufacturing facilities, tooling, and handling, and transportation operations were developed. Weld processes and tooling evolved with the design as it matured through several block changes. Non Destructive Evaluation methods were used to assure integrity of welds and thermal protection system materials. The aluminum-lithium alloy was used near the end of the program and weld processes and weld repair techniques had to be refined. Development and implementation of friction stir welding was a substantial technology development incorporated during the Program. Automated thermal protection system application processes were developed for the majority of the tank surface. Material obsolescence was an issue throughout the multi-decade program. Process controls were implemented to assure cleanliness in the production environment, to control contaminants, and to preclude corrosion. Each tank was accepted via rigorous inspections, including non-destructive evaluation techniques, proof testing, and all systems testing. In the post STS-107 era, the project focused on ascent debris risk reduction. This was accomplished via stringent process controls, post flight assessment using substantially improved imagery, and selective redesigns. These efforts were supported with a number of test programs to simulate combined environments. The debris risk was reduced by two orders of magnitude. During this time a major natural disaster was overcome when hurricane Katrina damaged the manufacturing facility. Numerous lessons from these efforts, the manufacturing and material processing issues, the key design features, and evolution of the design will be discussed.

Pilet, Jeffery C.↗

Validation of Framework Code Approach to a Life Prediction System for Fiber Reinforced Composites

The grant was conducted by the MMC Life Prediction Cooperative, an industry/government collaborative team, Ohio Aerospace Institute (OAI) acted as the prime contractor on behalf of the Cooperative for this grant effort. See Figure I for the organization and responsibilities of team members. The technical effort was conducted during the period August 7, 1995 to June 30, 1996 in cooperation with Erwin Zaretsky, the LERC Program Monitor. Phil Gravett of Pratt & Whitney was the principal technical investigator. Table I documents all meeting-related coordination memos during this period. The effort under this grant was closely coordinated with an existing USAF sponsored program focused on putting into practice a life prediction system for turbine engine components made of metal matrix composites (MMC). The overall architecture of the NMC life prediction system was defined in the USAF sponsored program (prior to this grant). The efforts of this grant were focussed on implementing and tailoring of the life prediction system, the framework code within it and the damage modules within it to meet the specific requirements of the Cooperative. T'he tailoring of the life prediction system provides the basis for pervasive and continued use of this capability by the industry/government cooperative. The outputs of this grant are: 1. Definition of the framework code to analysis modules interfaces, 2. Definition of the interface between the materials database and the finite element model, and 3. Definition of the integration of the framework code into an FEM design tool.

Gravett, Phillip↗

BAE Systems Radiation Hardened SpaceWire ASIC and Roadmap

An Application Specific Integrated Circuit (ASIC) that implements the SpaceWire protocol has been developed in a radiation hardened 0.25 micron CMOS, technology. This effort began in March 2003 as a joint development between the NASA Goddard Space Flight Center (GSFC) and BAE Systems. The BAE Systems SpaceWire ASlC is comprised entirely of reusable core elements, many of which are already flight-proven. It incorporates a 4-port SpaceWire router with two local ports, dual PC1 bus interfaces, a microcontroller, 32KB of internal memory, -and a memory controller for additional external memory use. The SpaceWire ASlC is planned for use on both the Geostationary Operational Environmental Satellites (GOES)-R and the Lunar Reconnaissance Orbiter (LRO). Engineering parts have already been delivered to both programs. This paper discusses the SpaceWire protocol and those elements of it that have been built into the current SpaceWire reusable core. There are features within the core that go beyond the current standard that can be enabled or disabled by the user and these will be described. The adaptation of SpaceWire to BAE Systems' On Chip Bus (OCB) for compatibility with the other reusable cores will be discussed. Optional configurations within user systems will be shown. The physical imp!ementation of the design will be described and test results from the hardware will be discussed. Finally, the BAE Systems roadmap for SpaceWire developments will be discussed, including some products already in design as well as longer term plans.

Berger, Richard↗

National Rocket Propulsion Materials Plan: A NASA, Department of Defense, and Industry Partnership

NASA, Department of Defense, and rocket propulsion industry representatives are working together to create a national rocket propulsion materials development roadmap. This "living document" will facilitate collaboration among the partners, leveraging of resources, and will be a highly effective tool for technology development planning. The structuring of the roadmap, and development plan, which will combine the significant efforts of the Integrated High Payoff Rocket Propulsion Technology (IHPRPT) Program, and NASA's Integrated Space Transportation Plan (ISTP), is being lead by the IHPRPT Materials Working Group (IMWG). The IHPRPT Program is a joint DoD, NASA, and industry effort to dramatically improve the nation's rocket propulsion capabilities. This phased program is structured with increasingly challenging goals focused on performance, reliability, and cost to effectively double rocket propulsion capabilities by 2010. The IHPRPT program is focused on three propulsion application areas: Boost and Orbit Transfer (both liquid rocket engines and solid rocket motors), Tactical, and Spacecraft. Critical to the success of this initiative is the development and application of advanced materials, processes, and manufacturing technologies. NASA's ISTP is a comprehensive strategy focusing on the aggressive safety, reliability, and affordability goals for future space transportation systems established by the agency. Key elements of this plan are the 2 nd and 3 d Generation Reusable Launch Vehicles (RLV). The affordability and safety goals of these generational systems are, respectively, 10X cheaper and 100X safer by 2010, and 100X cheaper and 10,000X safer by 2025. Accomplishment of these goals requires dramatic and sustained breakthroughs, particularly in the development and the application of advanced material systems. The presentation will provide an overview of the IHPRPT materials initiatives, NASA's 2nd and 3 rd Generation RLV propulsion materials projects, and the approach for the development of the national rocket propulsion materials roadmap.

Clinton, Raymond G., Jr.↗

The X-43A Hyper-X Mach 7 Flight 2 Guidance, Navigation, and Control Overview and Flight Test Results

The objective of the Hyper-X program was to flight demonstrate an airframe-integrated hypersonic vehicle. On March 27, 2004, the Hyper-X program team successfully conducted flight 2 and achieved all of the research objectives. The Hyper-X research vehicle successfully separated from the Hyper-X launch vehicle and achieved the desired engine test conditions before the experiment began. The research vehicle rejected the disturbances caused by the cowl door opening and the fuel turning on and off and maintained the engine test conditions throughout the experiment. After the engine test was complete, the vehicle recovered and descended along a trajectory while performing research maneuvers. The last data acquired showed that the vehicle maintained control to the water. This report will provide an overview of the research vehicle guidance and control systems and the performance of the vehicle during the separation event and engine test. The research maneuvers were performed to collect data for aerodynamics and flight controls research. This report also will provide an overview of the flight controls related research and results.

Bahm, Catherine↗

Human Factors Research for Space Exploration: Measurement, Modeling, and Mitigation

As part of NASA's Human Research Program, the Space Human Factors Engineering Project serves as the bridge between Human Factors research and Human Spaceflight applications. Our goal is to be responsive to the operational community while addressing issues at a sufficient level of abstraction to ensure that our tools and solutions generalize beyond the point design. In this panel, representatives from four of our research domains will discuss the challenges they face in solving current problems while also enabling future capabilities. Historically, engineering-dominated organizations have tended to view good Human Factors (HF) as a desire rather than a requirement in system design and development. Our field has made significant gains in the past decade, however; the Department of Defense, for example, now recognizes Human-System Integration (HSI), of which HF is a component, as an integral part of their divisions hardware acquisition processes. And our own agency was far more accepting of HF/HSI requirements during the most recent vehicle systems definition than in any prior cycle. Nonetheless, HF subject matter experts at NASA often find themselves in catch up mode... coping with legacy systems (hardware and software) and procedures that were designed with little regard for the human element, and too often with an attitude of we can deal with any operator issues during training. Our challenge, then, is to segregate the true knowledge gaps in Space Human Factors from the prior failures to incorporate best (or even good) HF design principles. Further, we strive to extract the overarching core HF issues from the point-design-specific concerns that capture the operators (and managers) attention. Generally, our approach embraces a 3M approach to Human Factors: Measurement, Modeling, and Mitigation. Our first step is to measure human performance, to move from subjective anecdotes to objective, quantified data. Next we model the phenomenon, using appropriate methods in our field, modifying them to suit the unique aspects of the space environment. Finally, we develop technologies, tools, and procedures to mitigate the decrements in human performance and capabilities that occur in space environments. When successful, we decrease risks to crew safety and to mission success. When extremely successful (or lucky), we devise generalizable solutions that advance the state of our practice. Our panel is composed of researchers from diverse domains of our project... from different boxes, if you will, of the Human Factors Analysis and Classification System (HFACS).

Kaiser, Mary K.↗

Developing the Foundations of an Exploration Class Medical System: Bridging the Capability Gap between LEO and Mars

NASA's overarching mission is to drive advances in science, technology, aeronautics, and space exploration to enhance knowledge, education, innovation, economic vitality, and Earth stewardship. Its Artemis Program encompasses the next steps in human space exploration, critical elements of which include the Orion vehicle and Gateway outpost in lunar orbit. Artemis is the first "exploration class" space travel system with the stated mission to establish sustainable exploration of the lunar surface and serve as a bridge to future human exploration of Mars. Success requires understanding both the commonalities and the differences between our experience to date, predominantly in Low-Earth-Orbit, and the challenges expected in long-duration exploration missions. In addition, these missions will incur significant constraints on both vehicle and human systems. To that end, NASA Exploration Medical Capability (ExMC) element clinicians, engineers, and scientists are developing the "foundation" for a fully vehicle-integrated exploration-class medical system using model-based systems engineering to trace and leverage clinical and engineering content to expand and refine the fidelity and confidence in the medical system itself.

MEDICAL SYSTEMS↗

Solar Dynamics Observatory Guidance, Navigation, and Control System Overview

The Solar Dynamics Observatory (SDO) was designed and built at the Goddard Space Flight Center, launched from Cape Canaveral on February 11, 2010, and reached its final geosynchronous science orbit on March 16, 2010. The purpose of SDO is to observe the Sun and continuously relay data to a dedicated ground station. SDO remains Sun-pointing throughout most of its mission for the instruments to take measurements of the Sun. The SDO attitude control system (ACS) is a single-fault tolerant design. Its fully redundant attitude sensor complement includes sixteen coarse Sun sensors (CSSs), a digital Sun sensor (DSS), three two-axis inertial reference units (IRUs), and two star trackers (STs). The ACS also makes use of the four guide telescopes included as a part of one of the science instruments. Attitude actuation is performed using four reaction wheels assemblies (RWAs) and eight thrusters, with a single main engine used to provide velocity-change thrust for orbit raising. The attitude control software has five nominal control modes, three wheel-based modes and two thruster-based modes. A wheel-based Safehold running in the attitude control electronics box improves the robustness of the system as a whole. All six modes are designed on the same basic proportional-integral-derivative attitude error structure, with more robust modes setting their integral gains to zero. This paper details the final overall design of the SDO guidance, navigation, and control (GN&C) system and how it was used in practice during SDO launch, commissioning, and nominal operations. This overview will include the ACS control modes, attitude determination and sensor calibration, the high gain antenna (HGA) calibration, and jitter mitigation operation. The Solar Dynamics Observatory mission is part of the NASA Living With a Star program, which seeks to understand the changing Sun and its effects on the Solar System, life, and society. To this end, the SDO spacecraft carries three Sun-observing instruments: Helioseismic and Magnetic Imager (HMI), led by Stanford University; Atmospheric Imaging Assembly (AIA), led by Lockheed Martin Space and Astrophysics Laboratory; and Extreme Ultraviolet Variability Experiment (EVE), led by the University of Colorado. The basic mission is to observe the Sun for a very high percentage of the 5-year mission (10-year goal) with long stretches of uninterrupted observations and with constant, high-data-rate transmission to a dedicated ground station to be located in White Sands, New Mexico. These goals guided the design of the spacecraft bus that will carry and service the three-instrument payload. Overarching design goals for the bus are geosynchronous orbit, near-constant Sun observations with the ability to fly through eclipses, and constant HGA contact with the dedicated ground station. A three-axis stabilized ACS is needed both to point at the Sun accurately and to keep the roll about the Sun vector correctly positioned with respect to the solar north pole. This roll control is especially important for the magnetic field imaging of HM I. The mission requirements have several general impacts on the ACS design. Both the AIA and HMI instruments are very sensitive to the blurring caused by jitter. Each has an image stabilization system (ISS) with some ability to filter out high frequency motion, but below the bandwidth of the ISS the control system must compensate for disturbances within the ACS bandwidth or avoid exciting jitter at higher frequencies. Within the ACS bandwidth, the control requirement imposed by AIA is to place the center of the solar disk no more than 2 arc sec, 3 , from a body-defined target based on one of the GTs that accompany the instrument. This body-defined target, called the science reference boresight (SRB), was determined from the postlaunch orientation of the GTs by averaging the bounding telescope boresights for pitch to get a pitch SRB coordinate, and by averaging the bounding boresights for yaw toet the yaw SRB coordinate. The location of this SRB in the 0.5-deg field-of-view for each GT then becomes the central target for each telescope; one GT is selected for use as the ACS controlling guide telescope (CGT) at any given time. Fine Sun-pointing is effected based on this SRB for all three instruments when the Sun is within the linear range of the CGT. In addition to limiting jitter, HMI science requires averaging several observations, making the instrument sensitive to low frequency motion that induces differential motion between each observation. This requires the spacecraft attitude to be stable about the roll axis to approximately 10 arcsec over a ten-minute period. Instrument calibrations require that the spacecraft point the SRB up to 2.5 degrees in pitch and yaw away from the center of the Sun, placing the Sun outside the field-of-view of the guide telescopes. In such instances, when the GTs cannot provide the definitive target for the ACS, on-board attitude determination combined with ephemeris prediction of the Sun direction must provide the definitive target. EVE is capable of observing the Sun with less dependence on attitude control. However, the ground data processing needs for calibrations result in the most strict attitude knowledge requirements for the mission: [35,70,70] arcsec, 3 , of knowledge with respect to the center of the solar disk. In addition to driving the ACS sensor selection, the knowledge requirements, which have their effect primarily during Inertial mode calibrations, drive the accuracy requirements for the solar ephemeris. The need to achieve and maintain geosynchronous orbit (GEO) drove the need for high-efficiency propulsive systems and appropriate attitude control. The main engine provided high specific impulse for the maneuvers to attain GEO, while the smaller ACS thrusters managed the disturbance torques of the larger engine and provided the capability for much smaller adjustment burns on orbit. SDO s large solar profile means that solar radiation pressure is a large torque disturbance, and the momentum buildup from this disturbance and the GEO altitude drives the ACS to use thrusters to manage vehicle momentum. The demanding data capture budget for the mission, however, requires SDO to avoid frequent thruster maneuvers, while concerns about on-orbit jitter restrict the maximum desired wheel speeds desired from the RWAs. The plan for on-orbit wheel speed and momentum management will be discussed as well as what is now being done in operation after the jitter environment was characterized. The SDO ACS hardware complement is single-fault tolerant. Two main processors carry virtually identical copies of the command and data handling and ACS software, and two identical attitude control electronics (ACE) boxes carry Coldfire processors with contingency ACS software and other hardware interface cards; the ACE structure allows reaction wheels to be commanded by the Sun-pointing Safehold independent of the Mil Std 1553 data bus. The sixteen Adcole CSSs are grouped into primary and backup sets of eight sensors, each set providing the ability to calculate a sun vector. Each set of eight eyes provides full 4 -steradian coverage. The Adcole DSS comprises an optics head and a separate electronics box providing a 1553 data interface. The electronics box is mounted inside the Faraday cage created by the spacecraft bus module. The DSS head with its 32- deg square FOV is mounted on the instrument module with its boresight along the spacecraft X axis, nearly aligned with the Sun during observations. Adcole has designed the DSS calibration parameters so that the accuracy is 0.24 arcminutes within 10 deg of the boresight, and diminishes to 3 arcminutes as the Sun moves towards the edges of its FOV . This DSS calibration scheme provides higher accuracy attitude determination over the range of the instrument calibration maneuvers.

Morgenstern, Wendy M.↗

Development of an Information Fusion System for Engine Diagnostics and Health Management

Aircraft gas-turbine engine data are available from a variety of sources including on-board sensor measurements, maintenance histories, and component models. An ultimate goal of Propulsion Health Management (PHM) is to maximize the amount of meaningful information that can be extracted from disparate data sources to obtain comprehensive diagnostic and prognostic knowledge regarding the health of the engine. Data Fusion is the integration of data or information from multiple sources, to achieve improved accuracy and more specific inferences than can be obtained from the use of a single sensor alone. The basic tenet underlying the data/information fusion concept is to leverage all available information to enhance diagnostic visibility, increase diagnostic reliability and reduce the number of diagnostic false alarms. This paper describes a basic PHM Data Fusion architecture being developed in alignment with the NASA C17 Propulsion Health Management (PHM) Flight Test program. The challenge of how to maximize the meaningful information extracted from disparate data sources to obtain enhanced diagnostic and prognostic information regarding the health and condition of the engine is the primary goal of this endeavor. To address this challenge, NASA Glenn Research Center (GRC), NASA Dryden Flight Research Center (DFRC) and Pratt & Whitney (P&W) have formed a team with several small innovative technology companies to plan and conduct a research project in the area of data fusion as applied to PHM. Methodologies being developed and evaluated have been drawn from a wide range of areas including artificial intelligence, pattern recognition, statistical estimation, and fuzzy logic. This paper will provide a broad overview of this work, discuss some of the methodologies employed and give some illustrative examples.

Volponi, Allan J.↗

A Demonstration Advanced Avionics System for general aviation

A program initiated within NASA has emphasized the use of a data bus, microprocessors, electronic displays and data entry devices for general aviation. A Demonstration Advanced Avionics System (DAAS) capable of evaluating critical and promising elements of an integrating system that will perform the functions of (1) automated guidance and navigation; (2) flight planning; (3) weight and balance performance computations; (4) monitoring and warning; and (5) storage of normal and emergency check lists and operational limitations is described. Consideration is given to two major parts of the DAAS instrument panel: the integrated data control center and an electronic horizontal situation indicator, and to the system architecture. The system is to be installed in the Ames Research Center's Cessna 402B in the latter part of 1980; engineering flight testing will begin in the first part of 1981.

Denery, D. G.↗

STS-114: Discovery Post MMT Press Conference

Bruce Buckingham of NASA Public Affairs hosted this press conference. Wayne Hill, Space Shuttle Deputy Program Manager; John Muratore, Shuttle Systems and Integration Manager; Mike Wetmore, Director for Shuttle Processing were present. Wayne started with a video from Shuttle Logistics Depot showing details of a point sensor box commonly named the black box. Work with the trouble shooting continues on a day to day basis, no definite launching date is set. John reports that they are in a mission support mode all over the country until the sensor problem is solved. Mike reports his team will complete scrub and securing tasks through the next day, restore the facility to its normal mode, and will start to a four day process of getting back to launch once trouble shooting is completed. Tanking test, thermal environment, problem identification, engine cut-off sensor problems, sensors, risk, design reviews, test and analysis, correlation of the problem with Columbia, are some of the topics covered with the News media.

Source record↗

The scheme machine: A case study in progress in design derivation at system levels

The Scheme Machine is one of several design projects of the Digital Design Derivation group at Indiana University. It differs from the other projects in its focus on issues of system design and its connection to surrounding research in programming language semantics, compiler construction, and programming methodology underway at Indiana and elsewhere. The genesis of the project dates to the early 1980's, when digital design derivation research branched from the surrounding research effort in programming languages. Both branches have continued to develop in parallel, with this particular project serving as a bridge. However, by 1990 there remained little real interaction between the branches and recently we have undertaken to reintegrate them. On the software side, researchers have refined a mathematically rigorous (but not mechanized) treatment starting with the fully abstract semantic definition of Scheme and resulting in an efficient implementation consisting of a compiler and virtual machine model, the latter typically realized with a general purpose microprocessor. The derivation includes a number of sophisticated factorizations and representations and is also deep example of the underlying engineering methodology. The hardware research has created a mechanized algebra supporting the tedious and massive transformations often seen at lower levels of design. This work has progressed to the point that large scale devices, such as processors, can be derived from first-order finite state machine specifications. This is roughly where the language oriented research stops; thus, together, the two efforts establish a thread from the highest levels of abstract specification to detailed digital implementation. The Scheme Machine project challenges hardware derivation research in several ways, although the individual components of the system are of a similar scale to those we have worked with before. The machine has a custom dual-ported memory to support garbage collection. It consists of four tightly coupled processes--processor, collector, allocator, memory--with a very non-trivial synchronization relationship. Finally, there are deep issues of representation for the run-time objects of a symbolic processing language. The research centers on verification through integrated formal reasoning systems, but is also involved with modeling and prototyping environments. Since the derivation algebra is basd on an executable modeling language, there is opportunity to incorporate design animation in the design process. We are looking for ways to move smoothly and incrementally from executable specifications into hardware realization. For example, we can run the garbage collector specification, a Scheme program, directly against the physical memory prototype, and similarly, the instruction processor model against the heap implementation.

Johnson, Steven D.↗