Search NASA⌕ Search

SEARCH · Search NASA

Results for “customization”

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,153 records · Page 64

Operational Parameters, Considerations, and Design Decisions for Resource-Constrained Ion Trap Mass Spectrometers

Mass spectrometers are increasingly finding applications in new and unique areas, often in situations where key operational resources (i.e. power, weight and size) are limited. One such example is the Mars Organic Molecule Analyzer (MOMA). This instrument is a joint venture between NASA and the European Space Agency (ESA) to develop an ion trap mass spectrometer for chemical analysis on Mars. The constraints on such an instrument are significant as are the performance requirements. While the ideal operating parameters for an ion trap are generally well characterized, methods to maintain analytical performance with limited power and system weight need to be investigated and tested. Methods Experiments have been performed on two custom ion trap mass spectrometers developed as prototypes for the MOMA instrument. This hardware consists of quadrupole ion trap electrodes that are 70% the size of common commercial instrumentation. The trapping RF voltage is created with a custom tank circuit that can be tuned over a range of RF frequencies and is driven using laboratory supplies and amplifiers. The entire instrument is controlled with custom Lab VIEW software that allows a high degree of flexibility in the definition of the scan function defining the ion trap experiment. Ions are typically generated via an internal electron ionization source, however, a laser desorption source is also in development for analysis of larger intact molecules. Preliminary Data The main goals in this work have been to reduce the power required to generate the radio frequency trapping field used in an ion trap mass spectrometer. Generally minimizing the power will also reduce the volume and mass of the electronics to support the instrument. In order to achieve optimum performance, commercial instruments typically utilize RF frequencies in the 1 MHz range. Without much concern for power usage, they simply generate the voltage required to access the mass range of interest. In order to reduce the required RF voltage (and power), operation of the ion trap at lower RF frequencies has been investigated. Surprisingly, the performance of the instrument has only been slightly degraded at RF frequencies all the way down to 500 kHz. Mass resolution is relatively stable to this point and depending on the resonant ejection point used, the peak intensity is also quite stable. To date only masses up to m/z 200 have been fully investigated, however, additional studies are planned to verify the performance with higher mass ions. The lower frequency and voltage should reduce the pseudo potential well depth, eventually affecting the trapping efficiency of the instrument -- effect that could manifest itself in significantly limiting the mass range of trapped ions. Other methods to reduce the RF power while maintaining analytical performance are also under investigation. This includes ion ejection at lower q(sub z) values to access a given mass with a lower RF voltage. The loss of mass resolution at lower q(sub eject) points has been measured and current work is underway to leverage scan speed and the use of non-linear resonances in order to counter this trend. The overall trap performance under this range of operating conditions will be presented with a goal of identifying what trade-offs are acceptable.

Danell, Ryan M.↗

Support for User Interfaces for Distributed Systems

An extensible Java(TradeMark) software framework supports the construction and operation of graphical user interfaces (GUIs) for distributed computing systems typified by ground control systems that send commands to, and receive telemetric data from, spacecraft. Heretofore, such GUIs have been custom built for each new system at considerable expense. In contrast, the present framework affords generic capabilities that can be shared by different distributed systems. Dynamic class loading, reflection, and other run-time capabilities of the Java language and JavaBeans component architecture enable the creation of a GUI for each new distributed computing system with a minimum of custom effort. By use of this framework, GUI components in control panels and menus can send commands to a particular distributed system with a minimum of system-specific code. The framework receives, decodes, processes, and displays telemetry data; custom telemetry data handling can be added for a particular system. The framework supports saving and later restoration of users configurations of control panels and telemetry displays with a minimum of effort in writing system-specific code. GUIs constructed within this framework can be deployed in any operating system with a Java run-time environment, without recompilation or code changes.

Eychaner, Glenn↗

MicroShell Minimalist Shell for Xilinx Microprocessors

MicroShell is a lightweight shell environment for engineers and software developers working with embedded microprocessors in Xilinx FPGAs. (MicroShell has also been successfully ported to run on ARM Cortex-M1 microprocessors in Actel ProASIC3 FPGAs, but without project-integration support.) Micro Shell decreases the time spent performing initial tests of field-programmable gate array (FPGA) designs, simplifies running customizable one-time-only experiments, and provides a familiar-feeling command-line interface. The program comes with a collection of useful functions and enables the designer to add an unlimited number of custom commands, which are callable from the command-line. The commands are parameterizable (using the C-based command-line parameter idiom), so the designer can use one function to exercise hardware with different values. Also, since many hardware peripherals instantiated in FPGAs have reasonably simple register-mapped I/O interfaces, the engineer can edit and view hardware parameter settings at any time without stopping the processor. MicroShell comes with a set of support scripts that interface seamlessly with Xilinx's EDK tool. Adding an instance of MicroShell to a project is as simple as marking a check box in a library configuration dialog box and specifying a software project directory. The support scripts then examine the hardware design, build design-specific functions, conditionally include processor-specific functions, and complete the compilation process. For code-size constrained designs, most of the stock functionality can be excluded from the compiled library. When all of the configurable options are removed from the binary, MicroShell has an unoptimized memory footprint of about 4.8 kB and a size-optimized footprint of about 2.3 kB. Since MicroShell allows unfettered access to all processor-accessible memory locations, it is possible to perform live patching on a running system. This can be useful, for instance, if a bug is discovered in a routine but the system cannot be rebooted: Shell allows a skilled operator to directly edit the binary executable in memory. With some forethought, MicroShell code can be located in a different memory location from custom code, permitting the custom functionality to be overwritten at any time without stopping the controlling shell.

Werne, Thomas A.↗

Link Analysis in the Mission Planning Lab

The legacy communications link analysis software currently used at Wallops Flight Facility involves processes that are different for command destruct, radar, and telemetry. There is a clear advantage to developing an easy-to-use tool that combines all the processes in one application. Link Analysis in the Mission Planning Lab (MPL) uses custom software and algorithms integrated with Analytical Graphics Inc. Satellite Toolkit (AGI STK). The MPL link analysis tool uses pre/post-mission data to conduct a dynamic link analysis between ground assets and the launch vehicle. Just as the legacy methods do, the MPL link analysis tool calculates signal strength and signal- to-noise according to the accepted processes for command destruct, radar, and telemetry assets. Graphs and other custom data are generated rapidly in formats for reports and presentations. STK is used for analysis as well as to depict plume angles and antenna gain patterns in 3D. The MPL has developed two interfaces with the STK software (see figure). The first interface is an HTML utility, which was developed in Visual Basic to enhance analysis for plume modeling and to offer a more user friendly, flexible tool. A graphical user interface (GUI) written in MATLAB (see figure upper right-hand corner) is also used to quickly depict link budget information for multiple ground assets. This new method yields a dramatic decrease in the time it takes to provide launch managers with the required link budgets to make critical pre-mission decisions. The software code used for these two custom utilities is a product of NASA's MPL.

McCarthy, Jessica A.↗

NASA's Robotic Lunar Lander Development Project

Since early 2005, NASA's Robotic Lunar Lander Development (RLLD) office at NASA MSFC, in partnership with the Applied Physics Laboratory (APL), has developed mission concepts and preformed risk-reduction activities to address planetary science and exploration objectives uniquely met with landed missions. The RLLD team developed several concepts for lunar human-exploration precursor missions to demonstrate precision landing and in-situ resource utilization, a multi-node lunar geophysical network mission, either as a stand-alone mission, or as part of the International Lunar Network (ILN), a Lunar Polar Volatiles Explorer and a Mercury lander mission for the Planetary Science decadal survey, and an asteroid rendezvous and landing mission for the Exploration Precursor Robotics Mission (xPRM) office. The RLLD team has conducted an extensive number of risk-reduction activities in areas common to all lander concepts, including thruster testing, propulsion thermal control demonstration, composite deck design and fabrication, and landing leg stability and vibration. In parallel, the team has developed two robotic lander testbeds providing closed-loop, autonomous hover and descent activities for integration and testing of flight-like components and algorithms. A compressed-air test article had its first flight in September 2009 and completed over 150 successful flights. This small test article (107 kg dry/146 kg wet) uses a central throttleable thruster to offset gravity, plus 3 descent thrusters (~37lbf ea) and 6 attitude-control thrusters (~12lbf ea) to emulate the flight system with pulsed operation over approximately 10s of flight time. The test article uses carbon composite honeycomb decks, custom avionics (COTS components assembled in-house), and custom flight and ground software. A larger (206 kg dry/322 kg wet), hydrogen peroxide-propelled vehicle began flight tests in spring 2011 and fly over 30 successful flights to a maximum altitude of 30m. The monoprop testbed also uses a central gravity-canceling thruster and 3 descent thrusters, but has 12 attitude-control thrusters and a maximum flight time of over a minute. The testbed uses aluminum ortho-grid decks, an LN200-1 IMU, Roke Manor Radar Altimeter, Illunis optical cameras, Novatel Pro-Pak GPS truth data system, Pressure transducers & thermocouples for housekeeping, "In-Control" ground system software, and the core Flight Executive (cFE) modular software environment. The peroxide lander testbed is able to accept other sensors and algorithms for testing, both from within NASA and from other customers. Through these activities, the RLLD team has significantly reduced technical risks for all small and medium class robotic landers for the Moon and other airless planetary bodies.

Cohen, Barbara A.↗

Online Assessment of Satellite-Derived Global Precipitation Products

Precipitation is difficult to measure and predict. Each year droughts and floods cause severe property damages and human casualties around the world. Accurate measurement and forecast are important for mitigation and preparedness efforts. Significant progress has been made over the past decade in satellite precipitation product development. In particular, products' spatial and temporal resolutions as well as timely availability have been improved by blended techniques. Their resulting products are widely used in various research and applications. However biases and uncertainties are common among precipitation products and an obstacle exists in quickly gaining knowledge of product quality, biases and behavior at a local or regional scale, namely user defined areas or points of interest. Current online inter-comparison and validation services have not addressed this issue adequately. To address this issue, we have developed a prototype to inter-compare satellite derived daily products in the TRMM Online Visualization and Analysis System (TOVAS). Despite its limited functionality and datasets, users can use this tool to generate customized plots within the United States for 2005. In addition, users can download customized data for further analysis, e.g. comparing their gauge data. To meet increasing demands, we plan to increase the temporal coverage and expanded the spatial coverage from the United States to the globe. More products have been added as well. In this poster, we present two new tools: Inter-comparison of 3B42RT and 3B42 Inter-comparison of V6 and V7 TRMM L-3 monthly products The future plans include integrating IPWG (International Precipitation Working Group) Validation Algorithms/statistics, allowing users to generate customized plots and data. In addition, we will expand the current daily products to monthly and their climatology products. Whenever the TRMM science team changes their product version number, users would like to know the differences by inter-comparing both versions of TRMM products in their areas of interest. Making this service available to users will help them to better understand associated changes. We plan to implement this inter-comparison in TRMM standard monthly products with the IPWG algorithms. The plans outlined above will complement and accelerate the existing and ongoing validation activities in the community as well as enhance data services for TRMM and the future Global Precipitation Mission (GPM).

Liu, Zhong↗

SpaceCube Mini

This version of the SpaceCube will be a full-fledged, onboard space processing system capable of 2500+ MIPS, and featuring a number of plug-andplay gigabit and standard interfaces, all in a condensed 3x3x3 form factor [less than 10 watts and less than 3 lb (approximately equal to 1.4 kg)]. The main processing engine is the Xilinx SIRF radiation- hardened-by-design Virtex-5 FX-130T field-programmable gate array (FPGA). Even as the SpaceCube 2.0 version (currently under test) is being targeted as the platform of choice for a number of the upcoming Earth Science Decadal Survey missions, GSFC has been contacted by customers who wish to see a system that incorporates key features of the version 2.0 architecture in an even smaller form factor. In order to fulfill that need, the SpaceCube Mini is being designed, and will be a very compact and low-power system. A similar flight system with this combination of small size, low power, low cost, adaptability, and extremely high processing power does not otherwise exist, and the SpaceCube Mini will be of tremendous benefit to GSFC and its partners. The SpaceCube Mini will utilize space-grade components. The primary processing engine of the Mini is the Xilinx Virtex-5 SIRF FX-130T radiation-hardened-by-design FPGA for critical flight applications in high-radiation environments. The Mini can also be equipped with a commercial Xilinx Virtex-5 FPGA with integrated PowerPCs for a low-cost, high-power computing platform for use in the relatively radiation- benign LEOs (low-Earth orbits). In either case, this version of the Space-Cube will weigh less than 3 pounds (.1.4 kg), conform to the CubeSat form-factor (10x10x10 cm), and will be low power (less than 10 watts for typical applications). The SpaceCube Mini will have a radiation-hardened Aeroflex FPGA for configuring and scrubbing the Xilinx FPGA by utilizing the onboard FLASH memory to store the configuration files. The FLASH memory will also be used for storing algorithm and application code for the PowerPCs and the Xilinx FPGA. In addition, it will feature highspeed DDR SDRAM (double data rate synchronous dynamic random-access memory) to store the instructions and data of active applications. This version will also feature SATA-II and Gigabit Ethernet interfaces. Furthermore, there will also be general-purpose, multi-gigabit interfaces. In addition, the system will have dozens of transceivers that can support LVDS (low-voltage differential signaling), RS-422, or SpaceWire. The SpaceCube Mini includes an I/O card that can be customized to meet the needs of each mission. This version of the SpaceCube will be designed so that multiple Minis can be networked together using SpaceWire, Ethernet, or even a custom protocol. Scalability can be provided by networking multiple SpaceCube Minis together. Rigid-Flex technology is being targeted for the construction of the SpaceCube Mini, which will make the extremely compact and low-weight design feasible. The SpaceCube Mini is designed to fit in the compact CubeSat form factor, thus allowing deployment in a new class of missions that the previous SpaceCube versions were not suited for. At the time of this reporting, engineering units should be available in the summer 2012.

Michael Lin↗

Communicating the Threat of a Tropical Cyclone to the Eastern Range

The 45th Weather Squadron (45 WS) has developed a tool to help visualize the Wind Speed Probability product from the National Hurricane Center (NHC) and to help communicate that information to space launch customers and decision makers at the 45th Space Wing (45 SW) and Kennedy Space Center (KSC) located in east central Florida. This paper reviews previous work and presents the new visualization tool, including initial feedback as well as the pros and cons. The NHC began issuing their Wind Speed Probability product for tropical cyclones publicly in 2006. The 45 WS uses this product to provide a threat assessment to 45 SW and KSC leadership for risk evaluations with an approaching tropical cyclone. Although the wind speed probabilities convey the uncertainty of a tropical cyclone well, communicating this information to customers is a challenge. The 45 WS continually strives to provide the wind speed probability information to customers in a context which clearly communicates the threat of a tropical cyclone. First, an intern from the Florida Institute of Technology (FIT) Atmospheric Sciences department, sponsored by Scitor Corporation, independently evaluated the NHC wind speed probability product. This work was later extended into a M.S. thesis at FIT, partially funded by Scitor Corporation and KSC. A second thesis at FIT further extended the evaluation partially funded by KSC. Using this analysis, the 45 WS categorized the probabilities into five probability interpretation categories: Very Low, Low, Moderate, High, and Very High. These probability interpretation categories convert the forecast probability and forecast interval into easily understood categories that are consistent across all ranges of probabilities and forecast intervals. As a follow-on project, KSC funded a summer intern to evaluate the human factors of the probability interpretation categories, which ultimately refined some of the thresholds. The 45 WS created a visualization tool to express the timing and risk for multiple locations in a single graphic. Preliminary results on an on-going project by FIT will be included in this paper. This project is developing a new method of assigning the probability interpretation categories and updating the evaluation of the performance of the NHC wind speed probability analysis.

Winters, Katherine A.↗

Analog Exercise Hardware to Implement a High Intensity Exercise Program During Bed Rest

Background: In order to evaluate novel countermeasure protocols in a space flight analog prior to validation on the International Space Station (ISS), NASA's Human Research Program (HRP) is sponsoring a multi-investigator bedrest campaign that utilizes a combination of commercial and custom-made exercise training hardware to conduct daily resistive and aerobic exercise protocols. This paper will describe these pieces of hardware and how they are used to support current bedrest studies at NASA's Flight Analog Research Unit in Galveston, TX. Discussion: To implement candidate exercise countermeasure studies during extended bed rest studies the following analog hardware are being utilized: Stand alone Zero-Gravity Locomotion Simulator (sZLS) -- a custom built device by NASA, the sZLS allows bedrest subjects to remain supine as they run on a vertically-oriented treadmill (0-15 miles/hour). The treadmill includes a pneumatic subject loading device to provide variable body loading (0-100%) and a harness to keep the subject in contact with the motorized treadmill to provide a ground reaction force at their feet that is quantified by a Kistler Force Plate. Supine Cycle Ergometer -- a commercially available supine cycle ergometer (Lode, Groningen, Netherlands) is used for all cycle ergometer sessions. The ergometer has adjustable shoulder supports and handgrips to help stabilize the subject during exercise. Horizontal Squat Device (HSD) -- a custom built device by Quantum Fitness Corp (Stafford, TX), the HSD allows for squat exercises to be performed while lying in a supine position. The HSD can provide 0 to 600 pounds of force in selectable 5 lb increments, and allows hip translation in both the vertical and horizontal planes. Prone Leg Curl -- a commercially available prone leg curl machine (Cybex International Inc., Medway, MA) is used to complete leg curl exercises. Horizontal Leg Press -- a commercially available horizontal leg press (Quantum Fitness Corporation) is used for leg press and heel raise exercises. Minor modifications were made to the device including adding 200 lbs to the weight stack, raising the frame by 12 inches, making the footplate adjustable, and providing removable handles. Conclusion: A combination of novel and commercial exercise hardware are used to mimic the exercise hardware capabilities aboard the ISS, allowing scientific investigation of new countermeasure protocols in a space flight analog prior to flight validation

Loerch, Linda↗

Space Transportation System Availability Requirement and Its Influencing Attributes Relationships

It is important that engineering and management accept the need for an availability requirement that is derived with its influencing attributes. It is the intent of this paper to provide the visibility of relationships of these major attribute drivers (variables) to each other and the resultant system inherent availability. Also important to provide bounds of the variables providing engineering the insight required to control the system's engineering solution, e.g., these influencing attributes become design requirements also. These variables will drive the need to provide integration of similar discipline functions or technology selection to allow control of the total parts count. The relationship of selecting a reliability requirement will place a constraint on parts count to achieve a given availability requirement or if allowed to increase the parts count will drive the system reliability requirement higher. They also provide the understanding for the relationship of mean repair time (or mean down time) to maintainability, e.g., accessibility for repair, and both the mean time between failure, e.g., reliability of hardware and availability. The concerns and importance of achieving a strong availability requirement is driven by the need for affordability, the choice of using the two launch solution for the single space application, or the need to control the spare parts count needed to support the long stay in either orbit or on the surface of the moon. Understanding the requirements before starting the architectural design concept will avoid considerable time and money required to iterate the design to meet the redesign and assessment process required to achieve the results required of the customer's space transportation system. In fact the impact to the schedule to being able to deliver the system that meets the customer's needs, goals, and objectives may cause the customer to compromise his desired operational goal and objectives resulting in considerable increased life cycle cost of the fielded space transportation system.

Rhodes, Russell E.↗

Space Transportation System Availability Requirements and Its Influencing Attributes Relationships

It is important that engineering and management accept the need for an availability requirement that is derived with its influencing attributes. It is the intent of this paper to provide the visibility of relationships of these major attribute drivers (variables) to each other and the resultant system inherent availability. Also important to provide bounds of the variables providing engineering the insight required to control the system's engineering solution, e.g., these influencing attributes become design requirements also. These variables will drive the need to provide integration of similar discipline functions or technology selection to allow control of the total parts count. The relationship of selecting a reliability requirement will place a constraint on parts count to achieve a given availability requirement or if allowed to increase the parts count will drive the system reliability requirement higher. They also provide the understanding for the relationship of mean repair time (or mean down time) to maintainability, e.g., accessibility for repair, and both the mean time between failure, e.g., reliability of hardware and availability. The concerns and importance of achieving a strong availability requirement is driven by the need for affordability, the choice of using the two launch solution for the single space application, or the need to control the spare parts count needed to support the long stay in either orbit or on the surface of the moon. Understanding the requirements before starting the architectural design concept will avoid considerable time and money required to iterate the design to meet the redesign and assessment process required to achieve the results required of the customer's space transportation system. In fact the impact to the schedule to being able to deliver the system that meets the customer's needs, goals, and objectives may cause the customer to compromise his desired operational goal and objectives resulting in considerable increased life cycle cost of the fielded space transportation system.

Rhodes, Russell E.↗

ISS Live!

International Space Station Live! (ISSLive!) is a Web application that uses a proprietary commercial technology called Lightstreamer to push data across the Internet using the standard http port (port 80). ISSLive! uses the push technology to display real-time telemetry and mission timeline data from the space station in any common Web browser or Internet- enabled mobile device. ISSLive! is designed to fill a unique niche in the education and outreach areas by providing access to real-time space station data without a physical presence in the mission control center. The technology conforms to Internet standards, supports the throughput needed for real-time space station data, and is flexible enough to work on a large number of Internet-enabled devices. ISSLive! consists of two custom components: (1) a series of data adapters that resides server-side in the mission control center at Johnson Space Center, and (2) a set of public html that renders the data pushed from the data adapters. A third component, the Lightstreamer server, is commercially available from a third party and acts as an intermediary between custom components (1) and (2). Lightstreamer also provides proprietary software libraries that are required to use the custom components. At the time of this reporting, this is the first usage of Web-based, push streaming technology in the aerospace industry.

Price, Jennifer↗

Simscape Modeling Verification in the Simulink Development Environment

The purpose of the Simulation Product Group of the Control and Data Systems division of the NASA Engineering branch at Kennedy Space Center is to provide a realtime model and simulation of the Ground Subsystems participating in vehicle launching activities. The simulation software is part of the Spaceport Command and Control System (SCCS) and is designed to support integrated launch operation software verification, and console operator training. Using Mathworks Simulink tools, modeling engineers currently build models from the custom-built blocks to accurately represent ground hardware. This is time consuming and costly due to required rigorous testing and peer reviews to be conducted for each custom-built block. Using Mathworks Simscape tools, modeling time can be reduced since there would be no custom-code developed. After careful research, the group came to the conclusion it is feasible to use Simscape's blocks in MatLab's Simulink. My project this fall was to verify the accuracy of the Crew Access Arm model developed using Simscape tools running in the Simulink development environment.

SIMSCAPE↗

An Evaluation of the Additional Acoustic Power Needed to Overcome the Effects of a Test-Article's Absorption during Reverberant Chamber Acoustic Testing of Spaceflight Hardware

The exposure of a customers aerospace test-article to a simulated acoustic launch environment is typically performed in a reverberant acoustic test chamber. The acoustic pre-test runs that will ensure that the sound pressure levels of this environment can indeed be met by a test facility are normally performed without a test-article dynamic simulator of representative acoustic absorption and size. If an acoustic test facilitys available acoustic power capability becomes maximized with the test-article installed during the actual test then the customers environment requirement may become compromised. In order to understand the risk of not achieving the customers in-tolerance spectrum requirement with the test-article installed, an acoustic power margin evaluation as a function of frequency may be performed by the test facility. The method for this evaluation of acoustic power will be discussed in this paper. This method was recently applied at the NASA Glenn Research Center Plum Brook Stations Reverberant Acoustic Test Facility for the SpaceX Falcon 9 Payload Fairing acoustic test program.

acoustic↗

An Evaluation of the Additional Acoustic Power Needed to Overcome the Effects of a Test-Article's Absorption During Reverberant Chamber Acoustic Testing of Spaceflight Hardware

The exposure of a customer's aerospace test-article to a simulated acoustic launch environment is typically performed in a reverberant acoustic test chamber. The acoustic pre-test runs that will ensure that the sound pressure levels of this environment can indeed be met by a test facility are normally performed without a test-article dynamic simulator of representative acoustic absorption and size. If an acoustic test facility's available acoustic power capability becomes maximized with the test-article installed during the actual test then the customer's environment requirement may become compromised. In order to understand the risk of not achieving the customer's in-tolerance spectrum requirement with the test-article installed, an acoustic power margin evaluation as a function of frequency may be performed by the test facility. The method for this evaluation of acoustic power will be discussed in this paper. This method was recently applied at the NASA Glenn Research Center Plum Brook Station's Reverberant Acoustic Test Facility for the SpaceX Falcon 9 Payload Fairing acoustic test program.

absorption↗

Hierarchthis: An Interactive Interface for Identifying Mission-Relevant Components of the Advanced Multi-Mission Operations System

Even though NASA's space missions are many and varied, there are some tasks that are common to all of them. For example, all spacecraft need to communicate with other entities, and all spacecraft need to know where they are. These tasks use tools and services that can be inherited and reused between missions, reducing systems engineering effort and therefore reducing cost.The Advanced Multi-Mission Operations System, or AMMOS, is a collection of multimission tools and services, whose development and maintenance are funded by NASA. I created HierarchThis, a plugin designed to provide an interactive interface to help customers identify mission-relevant tools and services. HierarchThis automatically creates diagrams of the AMMOS database, and then allows users to show/hide specific details through a graphical interface. Once customers identify tools and services they want for a specific mission, HierarchThis can automatically generate a contract between the Multimission Ground Systems and Services Office, which manages AMMOS, and the customer. The document contains the selected AMMOS components, along with their capabilities and satisfied requirements. HierarchThis reduces the time needed for the process from service selections to having a mission-specific contract from the order of days to the order of minutes.

Advanced Multi-Mission Operations System (AMMOS)↗

A Discussion of the Software Quality Assurance Role

The basic idea underlying this paper is that the conventional understanding of the role of a Software Quality Assurance (SQA) engineer is unduly limited. This is because few have asked who the customers of a SQA engineer are. Once you do this, you can better define what tasks a SQA engineer should perform, as well as identify the knowledge and skills that such a person should have. The consequence of doing this is that a SQA engineer can provide greater value to his or her customers. It is the position of this paper that a SQA engineer providing significant value to his or her customers must not only assume the role of an auditor, but also that of a software and systems engineer. This is because software engineers and their managers particularly value contributions that directly impact products and their development. These ideas are summarized as lessons learned, based on my experience at Jet Propulsion Laboratory (JPL).

experience↗

Service Quality Assessment for NASA's Deep Space Network: No Longer a Luxury

When NASA's Deep Space Network (DSN) was established almost a half century ago, the concept of computer-based service delivery was impractical or infeasible due to the state of information technology As a result, the interface the DSN exposes to its customers tends to be equipment-centric, lacking a clear demarcation between the DSN and the mission operation systems (MOS) of its customers. As the number of customers has continued to increase, the need to improve efficiency and minimize costs has grown. This growth has been the impetus for a DSN transformation from an equipment-forrent provider to a provider of standard services. Service orientation naturally leads to requirements for service management, including proactive measurement of service quality and service levels as well as the efficiency of internal processes and the performance of service provisioning systems. DSN System Engineering has surveyed industry offerings to determine if commercial successes in decision support and Business Intelligence (BI) solutions can be applied to the DSN. A pilot project was initiated, and subsequently executed to determine the feasibility of repurposing a commercial Business Intelligence platform for engineering analysis in conjunction with the platform's intended business reporting and analysis functions.

Operations Efficiency↗