SEARCH · Engineering Papers
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.
This demo will rewew the findings of the Shuttle's Debris Transport analysis. The demo focuses on aero analysis of the entlre vehicle in ascent (orbiter, SRB and ET together at low Mach number) for debris transoort and determining maximum allowable debris sizes from various sources. We will present analysis results along with performance data of the simulation runs on Supercomputers such as Columbia.
Launch vehicle payload capacity and the launch environment represent two of the most operationally limiting constraints on space system mass, volume, and configuration. Large-scale space science and power platforms as well as transit vehicles have been proposed that greatly exceed single-launch capabilities. Reconfigurable systems launched as multiple small modular spacecraft with the ability to rendezvous, approach, mate, and conduct coordinated operations have the potential to make these designs feasible. A key characteristic of these proposed systems is their ability to assemble into desired geometric (spatial) configurations. While flexible and sparse formations may be realized by groups of spacecraft flying in close proximity, flyers physically connected by active structural elements could continuously exchange power, fluids, and heat (via fluids). Configurations of small modular spacecraft temporarily linked together could be sustained as long as needed with minimal propellant use and reconfigured as often as needed over extended missions with changing requirements. For example, these vehicles could operate in extremely compact configurations during boost phases of a mission and then redeploy to generate power or communicate while coasting and upon reaching orbit. In 2005, NASA funded Phase 1 of a program called Modular Reconfigurable High-Energy Technology Demonstrator Assembly Testbed (MRHE) to investigate reconfigurable systems of small spacecraft. The MRHE team was led by NASA's Marshall Space Flight Center and included Lockheed Martin's Advanced Technology Center (ATC) in Palo Alto and its subcontractor, ATK. One of the goals of Phase 1 was to develop an MRHE concept demonstration in a relevant 1-g environment to highlight a number of requisite technologies. In Phase 1 of the MRHE program, Lockheed Martin devised and conducted an automated space system assembly demonstration featuring multipurpose free-floating robots representing Spacecraft in the newly built Controls and Automation Laboratory (CAL) at the ATC. The CAL lab features a 12' x 24' granite air-bearing table and an overhead simulated starfield. Among the technologies needed for the concept demo were mating interfaces allowing the spacecraft to dock and deployable structures allowing for adjustable separation between spacecraft after a rigid connection had been established. The decision to use a nonmetallic deployable boom for this purpose was driven by the MRHE concept demo requirements reproduced in Table 1.
Allows demonstration and development of exploration capabilities to help accomplish future missions sooner with less risk to crew and mission Characteristics of ISS as a testbed High fidelity human operations platform in LEO: Continuously operating habitat and active laboratory. High fidelity systems. Astronauts as test subjects. Highly experienced ground operations teams. Offers a controlled test environment.: Consequences to systems performance and decision making not offered in ground analogs International participation. Continuously improving system looking for new technology and ideas to improve operations. Technology Demos & Critical Systems Maturation. Human Health and Performance. Operations Simulations and Techniques. Exploration prep testing on ISS has been ongoing since 2012. Number of tests increasing with each ISS expedition. One Year Crew Expedition starting in Spring 2015. ROSCOSMOS and NASA are partnering on the Participating Crew are Mikhail Kornienko and Scott Kelly Majority of testing is an extension of current Human Biomedical Research investigations Plan for extending & expanding upon current operations techniques and tech demo studies ESA 10 Day Mission in Fall 2015 ESA astronaut focus on testing exploration technologies Many more opportunities throughout the life of ISS! 4/24/2014 david.h.korth@nasa.gov 4 Exploration testing
The main objective of the Holodeck Testbed is to create a cost effective, realistic, and highly immersive environment that can be used to train astronauts, carry out engineering analysis, develop procedures, and support various operations tasks. Currently, the Holodeck testbed allows to step into a simulated ISS (International Space Station) and interact with objects; as well as, perform Extra Vehicular Activities (EVA) on the surface of the Moon or Mars. The Holodeck Testbed is using the products being developed in the Hybrid Reality Lab (HRL). The HRL is combining technologies related to merging physical models with photo-realistic visuals to create a realistic and highly immersive environment. The lab also investigates technologies and concepts that are needed to allow it to be integrated with other testbeds; such as, the gravity offload capability provided by the Active Response Gravity Offload System (ARGOS). My main two duties were to develop and animate models for use in the HRL environments and work on a new way to interface with computers using Brain Computer Interface (BCI) technology. On my first task, I was able to create precise computer virtual tool models (accurate down to the thousandths or hundredths of an inch). To make these tools even more realistic, I produced animations for these tools so they would have the same mechanical features as the tools in real life. The computer models were also used to create 3D printed replicas that will be outfitted with tracking sensors. The sensor will allow the 3D printed models to align precisely with the computer models in the physical world and provide people with haptic/tactile feedback while wearing a VR (Virtual Reality) headset and interacting with the tools. Getting close to the end of my internship the lab bought a professional grade 3D Scanner. With this, I was able to replicate more intricate tools at a much more time-effective rate. The second task was to investigate the use of BCI to control objects inside the hybrid reality ISS environment. This task looked at using an Electroencephalogram (EEG) headset to collect brain state data that could be mapped to commands that a computer could execute. On this Task, I had a setback with the hardware, which stopped working and was returned to the vendor for repair. However, I was still able to collect some data, was able to process it, and started to create correlation algorithms between the electrical patterns in the brain and the commands we wanted the computer to carry out. I also carried out a test to investigate the comfort of the headset if it is worn for a long time. The knowledge gained will benefit me in my future career. I learned how to use various modeling and programming tools that included Blender, Maya, Substance Painter, Artec Studio, Github, and Unreal Engine 4. I learned how to use a professional grade 3D scanner and 3D printer. On the BCI Project I learned about data mining and how to create correlation algorithms. I also supported various demos including a live demo of the hybrid reality lab capabilities at ComicPalooza. This internship has given me a good look into engineering at NASA. I developed a more thorough understanding of engineering and my overall confidence has grown. I have also realized that any problem can be fixed, if you try hard enough, and as an engineer it is your job to not only fix problems but to embrace coming up with solutions to those problems.
In January 2015 the NASA Goddard Space Flight Center (GSFC) released the Core Flight System (cFS) as open source under the NASA Open Source Agreement (NOSA) license. The cFS is based on flight software (FSW) developed for 12 spacecraft spanning nearly two decades of effort and it can provide about a third of the FSW functionality for a low-earth orbiting scientific spacecraft. The cFS is a FSW framework that is portable, configurable, and extendable using a product line deployment model. However, the components are maintained separately so the user must configure, integrate, and deploy them as a cohesive functional system. This can be very challenging especially for organizations such as universities building cubesats that have minimal experience developing FSW. Supporting universities was one of the primary motivators for releasing the cFS under NOSA. This paper describes the OpenSatKit that was developed to address the cFS deployment challenges and to serve as a cFS training platform for new users. It provides a fully functional out-of-the box software system that includes NASA's cFS, Ball Aerospaceâ€"TM"s command and control system COSMOS, and a NASA dynamic simulator called 42. The kit is freely available since all of the components have been released as open source. The kit runs on a Linux platform, includes 8 cFS applications, several kit-specific applications, and built in demos illustrating how to use key application features. It also includes the software necessary to port the cFS to a Raspberry Pi and instructions for configuring COSMOS to communicate with the target. All of the demos and test scripts can be rerun unchanged with the cFS running on the Raspberry Pi. The cFS uses a 3-tiered layered architecture including a platform abstraction layer, a Core Flight Executive (cFE) middle layer, and an application layer. Similar to smart phones, the cFS application layer is the key architectural feature for userâ€"TM"s to extend the FSW functionality to meet their mission-specific requirements. The platform abstraction layer and the cFE layers go a step further than smart phones by providing a platform-agnostic Application Programmer Interface (API) that allows applications to run unchanged on different platforms. OpenSatKit can serve two significant architectural roles that will further help the adoption of the cFS and help create a community of users that can share assets. First, the kit is being enhanced to automate the integration of applications with the goal of creating a virtual cFS 'App Store'. Second, a platform certification test suite can be developed that would allow users to verify the port of the cFS to a new platform. This paper will describe the current state of these efforts and future plans.
In January 2015 the NASA Goddard Space Flight Center (GSFC) released the Core Flight System (cFS) as open source under the NASA Open Source Agreement (NOSA) license. The cFS is based on flight software (FSW) developed for 12 spacecraft spanning nearly two decades of effort and it can provide about a third of the FSW functionality for a low-earth orbiting scientific spacecraft. The cFS is a FSW framework that is portable, configurable, and extendable using a product line deployment model. However, the components are maintained separately so the user must configure, integrate, and deploy them as a cohesive functional system. This can be very challenging especially for organizations such as universities building cubesats that have minimal experience developing FSW. Supporting universities was one of the primary motivators for releasing the cFS under NOSA. This paper describes the OpenSatKit that was developed to address the cFS deployment challenges and to serve as a cFS training platform for new users. It provides a fully functional out-of-the box software system that includes NASA's cFS, Ball Aerospace's command and control system COSMOS, and a NASA dynamic simulator called 42. The kit is freely available since all of the components have been released as open source. The kit runs on a Linux platform, includes 8 cFS applications, several kit-specific applications, and built in demos illustrating how to use key application features. It also includes the software necessary to port the cFS to a Raspberry Pi and instructions for configuring COSMOS to communicate with the target. All of the demos and test scripts can be rerun unchanged with the cFS running on the Raspberry Pi. The cFS uses a 3-tiered layered architecture including a platform abstraction layer, a Core Flight Executive (cFE) middle layer, and an application layer. Similar to smart phones, the cFS application layer is the key architectural feature for users to extend the FSW functionality to meet their mission-specific requirements. The platform abstraction layer and the cFE layers go a step further than smart phones by providing a platform-agnostic Application Programmer Interface (API) that allows applications to run unchanged on different platforms. OpenSatKit can serve two significant architectural roles that will further help the adoption of the cFS and help create a community of users that can share assets. First, the kit is being enhanced to automate the integration of applications with the goal of creating a virtual cFS "App Store".. Second, a platform certification test suite can be developed that would allow users to verify the port of the cFS to a new platform. This paper will describe the current state of these efforts and future plans.
As part of the Appropriations Bill passed by the US Congress in February 2019, NASA was instructed to develop a nuclear thermal propulsion (NTP) flight demonstrator by 2024. [4] In response to this directive, the Advanced Concepts Office (ACO) at Marshall Space Flight Center (MSFC) was tasked with beginning concept studies for the flight demonstration (FD) mission. During the NTP study formulation, two philoso- phies emerged with regards to FD concept design. The first, Flight Demo 1 (FD1), strictly observes the 2024 schedule requirement at the expense of lower engine performance than expected of theoretical NTP engines. The second concept, Flight Demo 2 (FD2), relaxes the schedule requirement to allow for higher engine performance and more traceability to future operational systems. Both the FD1 and FD2 concepts present considerable challenges for subsystem design, specifically in the areas of thermal control, avionics, and power. To guard against undesired graveyard orbits, a requirement to keep the NTP engine and the reaction control system (RCS) separate was put in place. As a result of this requirement, the avionics subsystem must provide separate command and data handling (CDH) and instrumentation for each propulsion system. In-space instrumentation and monitoring of a NTP system has never been done before, necessitating the development of novel strategies and unique hardware. The heating rates produced by the NTP engine are extremely high, leading to difficulties with thermal control. The FD1 concept utilizes high-pressure gaseous hydrogen (GH2), which is largely insensitive to temperature fluctuations. The FD2 concept, however, utilizes cryogenic liquid hydrogen (LH2) which must be kept stable near 20 Kelvin. A high-performance thermal control system (TCS) will be required to ensure all components and subsystems are maintained within their operational temperature ranges. This paper will highlight the thermal, avionics, and power solutions required for the full scope of challenges for a NTP flight demonstrator.
1. Session Proposal o Session Title NASA’s In Space Manufacturing and the On Demand Manufacturing of Electronics o Session Topic Primary -- Space Logistics, Autonomy, and Robotics; Secondary – Transformative Research and Technologies o Session Format: Panel Discussion. o Requested Session Duration: 60 minutes o Short Session Description: The goal of NASA’s On Demand Manufacturing of Electronics project is to develop and demonstrate the feasibility of a low-gravity, on-demand manufacturing system for flexible hybrid electronic devices on the International Space Station. This panel will feature several key collaborators and team members from the commercial sector, academia, and internal to NASA, each of which are contributing an unique and vital role to the design and implementation of this new technology system. o Extended Session Description (Please describe in detail the activity proposed, including how you intend to use the requested session duration. This session description will be provided to the reviewers for consideration and will not be displayed in the online agenda.): The session will be moderated by Curtis Hill, the Project Lead for the On Demand Manufacturing of Electronics (ODME), and he will start by giving a brief introduction to the ODME project which is working to produce a demo system for the manufacturing of electronic devices on the International Space Station. Panelists consisting of collaborators and team members to the ODME project will then give a brief (~5 min) introduction highlighting their contributions to the project, followed by time for Q&A from the audience. The panel will consist of: 1. Kenneth Church, nScrypt. nScrypt is a leader in multi-material printing with a modular system that incorporates a direct write thick film print head, a polymer fused filament fabrication print head, a laser sintering attachment, a drill head attachment for milling, and a pick and place. The system can print a layer and scan for accuracy of prints. The combination of multiple print heads and scanning allows for the on-demand production of intricate electronic components. 2. Andy Kurk, TechShot, Inc. Techshot, Inc. has collaborated extensively with NASA on the in space manufacturing of both printed electronics and fused metal materials. They are currently working to develop and integrate a test system for printed electronics, and a flight demonstration on the International Space Station is anticipated in 2024. 3. Ed Hendricks, NextFlex. NextFlex has the goal of advancing the manufacture of flexible hybrid electronics in the U.S. They are working with ODME on the development of AstroSense, an additively manufactured, wireless, flexible, and wearable health sensor. 4. Dr. Pradeep Lall, Auburn University. Professor Lall is the MacFarlane Endowed Distinguished Professor in the Department of Mechanical Engineering with a Courtesy Joint Appointment in the Department of Electrical and Computer Engineering and a Courtesy Joint Appointment in the Department of Finance. He is collaborating with NASA’s ODME project to develop multilayer printable devices and to develop techniques to test the quality of a printed electronic device. 5. Dr. Wei Gao, California Institute of Technology. Professor Gao is an Assistant Professor of Medical Engineering. His group is developing fully printed, flexible, and wearable biosensors for crew health monitoring in collaboration with NASA’s ODME project. In addition, they are working on using sweat to power biofuel cells for wearable, self-powered electronic devices. 6. Beth Paquette, NASA Goddard. The ODME branch at NASA Goddard is spearheading a sounding rocket flight demo to prove the capability of a printed electronic device with multiple sensors. In addition, they focus on thin film and flexible energy storage evaluations. o Session Goal(s)/Outcome(s): Please list the learning objectives and/or tangible outcomes (technical paper or other publication). The goal of this session is to highlight the internal and collaborative efforts of NASA’s On Demand Manufacturing of Electronics project to develop a system for printing electronics that will be tested on the International Space Station in 2024. In addition, the session with facilitate discussion with the community on the state of the art of printable electronics, current challenges, and new avenues for collaboration.
Successful performance of medical procedures during missions beyond low Earth orbit requires novel solutions to replace real-time support from the ground since the communication delay will be longer as the crew travels farther from Earth. The Autonomous Medical Officer Support software Technology Demonstration project (AMOS Tech Demo) on the International Space Station (ISS) evaluates a novel software tool that shifts the emphasis from preflight training and real-time guidance (current ISS paradigm) to in-flight just-in-time (JIT) instruction (a new paradigm for crew medical autonomy). The AMOS platform introduces a novel, streamlined, skill-management archetype for exploration missions; the current AMOS version features comprehensive training and guidance modules for urinary bladder and kidney ultrasound examinations. The primary goal of the AMOS Tech Demo was to confirm telemedical proof-of-concept through initial use of the platform for autonomous imaging activities in an operational setting. Success metrics encompassed 1) successful software deployment, 2) collection of click tracking data, and 3) recording of ultrasound images. Additional aims included collecting crew feedback on a) AMOS implementation, and b) integrated training and procedure support concepts, as well as c) evaluation of AMOS use in an operational setting.
The FORTRAN subroutine SYMAT and related subroutines are described. In essence SYMAT is an iterative algorithm in which the problem of finding eigenvalues and eigenvectors of a real symmetric matrix is transformed into an equivalent problem of finding eigenvalues and eigenvectors of an infinite sequence of matrices of order two. A DEMO PROGRAM contains a subroutine COVAR which is used to compute the covariance matrix (denoted by A) of a data matrix (denoted by X). Since a covariance matrix is symmetric it can be analyzed by using subroutine SYMAT.
Distributed Earth Model/Orbiter Simulation (DEMOS) is a network based application developed for the UNIX environment that visually monitors or simulates the Earth and any number of orbiting vehicles. Its purpose is to provide Mission Control Center (MCC) flight controllers with a visually accurate three dimensional (3D) model of the Earth, Sun, Moon and orbiters, driven by real time or simulated data. The project incorporates a graphical user interface, 3D modelling employing state-of-the art hardware, and simulation of orbital mechanics in a networked/distributed environment. The user interface is based on the X Window System and the X Ray toolbox. The 3D modelling utilizes the Programmer's Hierarchical Interactive Graphics System (PHIGS) standard and Raster Technologies hardware for rendering/display performance. The simulation of orbiting vehicles uses two methods of vector propagation implemented with standard UNIX/C for portability. Each part is a distinct process that can run on separate nodes of a network, exploiting each node's unique hardware capabilities. The client/server communication architecture of the application can be reused for a variety of distributed applications.
The STX mass storage system design is intended for environments requiring high speed access to large volumes of data (terabyte and greater). Prior to commitment to a product design plan, STX conducted an exhaustive study of the commercially available off-the-shelf hardware and software. STX also conducted research into the area of emerging technologies in networks and storage media so that the design could easily accommodate new interfaces and peripherals as they came on the market. All the selected system elements were brought together in a demo suite sponsored jointly by STX and ALLIANT where the system elements were evaluated based on actual operation using a client-server mirror image configuration. Testing was conducted to assess the various component overheads and results were compared against vendor data claims. The resultant system, while adequate to meet our capacity requirements, fell short of transfer speed expectations. A product team lead by STX was assembled and chartered with solving the bottleneck issues. Optimization efforts yielded a 60 percent improvement in throughput performance. The ALLIANT computer platform provided the I/O flexibility needed to accommodate a multitude of peripheral interfaces including the following: up to twelve 25MB/s VME I/O channels; up to five HiPPI I/O full duplex channels; IPI-s, SCSI, SMD, and RAID disk array support; standard networking software support for TCP/IP, NFS, and FTP; open architecture based on standard RISC processors; and V.4/POSIX-based operating system (Concentrix). All components including the software are modular in design and can be reconfigured as needs and system uses change. Users can begin with a small system and add modules as needed in the field. Most add-ons can be accomplished seamlessly without revision, recompilation or re-linking of software.
Mars Environmental Survey Mission (MESUR) is intended to be a low cost, near term mission to study the chemical composition of Martian surface, structure and circulation of Mars' atmosphere, and the structure and dynamics of Mars' interior. To meet the science objectives of the mission, a network of 16 landers will be placed at various latitudes and longitudes of Mars. The paper identifies various options for powering the landers and lists the attributes of each option. The current strategy is to precede the lander launch and deployment with an engineering demo mission called the Pathfinder which would demonstrate the landing strategy and the engineering subsystems. The paper briefly describes the challenges involved in the power system development for the Pathfinder mission.
The problem domain being addressed by this contractual effort can be summarized by the following list: Automation and Robotics (A&R) technologies appear to be viable alternatives to current, manual operations; Life-cycle cost models are typically judged with suspicion due to implicit assumptions and little associated documentation; and Uncertainty is a reality for increasingly complex problems and few models explicitly account for its affect on the solution space. The objectives for this effort range from the near-term (1-2 years) to far-term (3-5 years). In the near-term, the envisioned capabilities of the modeling tool are annotated. In addition, a framework is defined and developed in the Decision Modelling System (DEMOS) environment. Our approach is summarized as follows: Assess desirable capabilities (structure into near- and far-term); Identify useful existing models/data; Identify parameters for utility analysis; Define tool framework; Encode scenario thread for model validation; and Provide transition path for tool development. This report contains all relevant, technical progress made on this contractual effort.
As part of my assignment connected with the Scientific and Technical Photography & Lab (STPL) at the NASA Langley Research Center I conducted a series of interviews and observed the day to day operations of the STPL with the ultimate objective of becoming exposed first hand to a scientific and technical photo/imaging department for which my school prepares its graduates. I was also asked to share my observations with the staff in order that these comments and observations might assist the STPL to better serve its customers. Meetings with several individuals responsible for various wind tunnels and with a group that provides photo-optical instrumentation services at the Center gave me an overview of the services provided by the Lab and possible areas for development. In summary form these are some of the observations that resulted from the interviews and daily contact with the STPL facility. (1) The STPL is perceived as a valuable and almost indispensable service group within the organization. This comment was invariably made by everyone. Everyone also seemed to support the idea that the STPL continue to provide its current level of service and quality. (2) The STPL generally is not perceived to be a highly technically oriented group but rather as a provider of high quality photographic illustration and documentation services. In spite of the importance and high marks assigned to the STPL there are several observations that merit consideration and evaluation for possible inclusion into the STPL's scope of expertise and future operating practices. (1) While the care and concern for artistic rendition of subjects is seen as laudable and sometimes valuable, the time that this often requires is seen as interfering with keeping the tunnels operating at maximum productivity. Tunnel managers would like to shorten down-time due to photography, have services available during evening hours and on short notice. It may be of interest to the STPL that tunnel managers are incorporating ever greater imaging capabilities in their facilities. To some extent this could mean a reduced demand for traditional photographic services. (2) The photographic archive is seen as a Center resource. Archiving of images, as well as data, is a matter of concern to the investigators. The early holdings of the Photographic Archives are quickly deteriorating. The relative inaccessibility of the material held in the archives is problematic. (3) In certain cases delivery or preparation of digital image files instead of, or along with, hardcopy is already being perceived by the STPL's customers as desirable. The STPL should make this option available, and the fact that it has, or will have this capability widely known. (4) The STPL needs to continue to provide expert advice and technical imaging support in terms of application information to users of traditional photographic and new electronic imaging systems. Cooperative demo projects might be undertaken to maintain or improve the capabilities of the Lab. (5) STPL personnel do not yet have significant electronic imaging or electronic communication skills and improvements in this is an area could potentially have a positive impact on the Center. (6) High speed photographic or imaging services are often mentioned by the STPL as being of primary importance to their mission but the lab supports very few projects calling for high speed imaging services. Much high speed equipment is in poor state of repair. It is interesting to note that when the operation of lasers, digital imaging or quantitative techniques are requested these are directed to another NASA department. Could joint activities be initiated to solve problems? (7). The STPL could acquire more technical assignments if examples of the areas where they posses expertise would be circulated around the center. The fact that the STPL owns high speed video capability could be 'advertised' among its customer base if there truly was an interest in building up a customer base in this area. The STPL could participate in events like TOPS as an exhibitor, as well as a documenter, of the event.
A Global Positioning System (GPS) flight receiver provides a means of precisely determining orbits for satellites in low to moderate altitude orbits. Above 5000 km altitude, however, relatively few GPS satellites are visible. We present a new approach to orbit determination for satellites at higher altitudes. Modification of GPS ground receivers enables a beacon from the orbiter to be tracked simultaneously with GPS data. The orbit accuracy expected from this GPS-like tracking (GLT) technique in principle could be comparable to accuracies of GPS orbits. Present-day GPS orbit quality from a daily semi-automated analysis system at the Jet Propulsion Laboratory is at the 30 - 50 cm level: expected accuracies for orbiters with GLT are calculated to be in the few-meter range for altitudes up to 100000 km. For geosynchronous satellites, however, there are unique challenges due to geometrical limitations and to the lack of strong dynamical signature in tracking data. We examine two approaches for tracking Tracking and Data Relay Satellites (TDRS) geostationary orbiters. One uses GLT with a global network; the other relies on a small `connected element' ground network with a distributed clock for short baseline differential carrier phase (SB Delta Phi). In priciple, both could meet 50-m TDRS operational requirements. However there are practical difficulties with either pure GLT or SB Delta Phi tracking schemes for present-day TDRS satellites. We describe an experiment planned for late 1993 which will combine aspects of both GLT and SB Delta Phi to demonstrate a new approach for tracking TDRS which offers a number of operationally convenient and attractive features. The TDRS demo will in effect ba a proof of concept experiment for both the GLT and SB Delta Phi approaches to tracking spacecraft.
This report provides: (1) a discussion of the origination of decision analysis problems (well-structured problems) from ill-structured problems; (2) a review of the various methodologies and software packages for decision analysis and related problem areas; (3) a discussion of how the characteristics of a decision analysis problem affect the choice of modeling methodologies, thus providing a guide as to when to choose a particular methodology; and (4) examples of applications of decision analysis to particular problems encountered by the IE Group at KSC. With respect to the specific applications at KSC, particular emphasis is placed on the use of the Demos software package (Lumina Decision Systems, 1993).
Better designs are needed for expert systems and other operations automation software, for more reliable, usable and effective human support. A prototype computer-aided Application Reuse Library shows feasibility of supporting concurrent development and improvement of advanced software by users, analysts, software developers, and human-computer interaction experts. Such a library expedites development of quality software, by providing working, documented examples, which support understanding, modification and reuse of requirements as well as code. It explicitly documents and implicitly embodies design guidelines, standards and conventions. The Application Reuse Library provides application modules with Demo-and-Tester elements. Developers and users can evaluate applicability of a library module and test modifications, by running it interactively. Sub-modules provide application code and displays and controls. The library supports software modification and reuse, by providing alternative versions of application and display functionality. Information about human support and display requirements is provided, so that modifications will conform to guidelines. The library supports entry of new application modules from developers throughout an organization. Example library modules include a timer, some buttons and special fonts, and a real-time data interface program. The library prototype is implemented in the object-oriented G2 environment for developing real-time expert systems.