Search NASA⌕ Search

SEARCH · Search NASA

Results for “heritage”

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 127 records · Page 7
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

Heritage to Flight; The Test Program that Brought an Inflation System Back to Life for the Low Earth Orbit Flight Test of an Inflatable Decelerator (LOFTID)

Following the success of the Inflatable Reentry Vehicle Experiment-3 (IRVE-3) project, the Terrestrial Hypersonic Inflatable Aerodynamic Decelerator (HIAD) Orbital Reentry (THOR) project was stood up with a “built to print” Inflation System utilizing the IRVE-3 flight spares. When THOR was canceled, this Inflation System had already been tested and assembled, ready for use. Thus, when the Low Earth Orbit Flight Test of an Inflatable Decelerator (LOFTID) was spun up, the THOR system seemed like a good candidate to salvage flight ready hardware. There were, however, some key differences in the IRVE/THOR system and the LOFTID one. LOFTID’s HIAD was two times the size of IRVE for starters and would require much higher flows to accommodate inflating such an article within a specific timeframe. With new requirements and a tight schedule, the LOFTID Inflation team set to work to verify flight readiness under LOFTID conditions and eliminate the need to requalify new hardware. LOFTID, utilizing an Inflation System built primarily hardware from IRVE-3 spares, successfully flew in November of 2022. This paper will outline the mission differences, the test campaign used to prepare LOFTID’s Inflation System for flight, and some lessons learned in repurposing older hardware.

Inflation System↗
NASA NTRSDate not supplied

Heritage to Flight: The Test Program that Brought an Inflation System Back to Life for LOFTID

Following the success of the Inflatable Reentry Vehicle Experiment-3 (IRVE-3) project, the Terrestrial Hypersonic Inflatable Aerodynamic Decelerator (HIAD) Orbital Reentry (THOR) project was stood up with a “built to print” Inflation System utilizing the IRVE-3 flight spares. When THOR was canceled, this Inflation System had already been tested and assembled, ready for use. Thus, when the Low Earth Orbit Flight Test of an Inflatable Decelerator (LOFTID) was spun up, the THOR system seemed like a good candidate to salvage flight ready hardware. There were, however, some key differences in the IRVE/THOR system and the LOFTID one. LOFTID’s HIAD was two times the size of IRVE for starters and would require much higher flows to accommodate inflating such an article within a specific timeframe. With new requirements and a tight schedule, the LOFTID Inflation team set to work to verify flight readiness under LOFTID conditions and eliminate the need to requalify new hardware. LOFTID, utilizing an Inflation System built primarily hardware from IRVE-3 spares, successfully flew in November of 2022. This paper will outline the mission differences, the test campaign used to prepare LOFTID’s Inflation System for flight, and some lessons learned in repurposing older hardware.

Inflation System↗
NASA NTRSDate not supplied

Heritage to Flight: The Test Program that Brought an Inflation System Back to Life for LOFTID

Following the success of the Inflatable Reentry Vehicle Experiment-3 (IRVE-3) project, the Terrestrial Hypersonic Inflatable Aerodynamic Decelerator (HIAD) Orbital Reentry (THOR) project was stood up with a “built to print” Inflation System utilizing the IRVE-3 flight spares. When THOR was canceled, this Inflation System had already been tested and assembled, ready for use. Thus, when the Low Earth Orbit Flight Test of an Inflatable Decelerator (LOFTID) was spun up, the THOR system seemed like a good candidate to salvage flight ready hardware. There were, however, some key differences in the IRVE/THOR system and the LOFTID one. LOFTID’s HIAD was two times the size of IRVE for starters and would require much higher flows to accommodate inflating such an article within a specific timeframe. With new requirements and a tight schedule, the LOFTID Inflation team set to work to verify flight readiness under LOFTID conditions and eliminate the need to requalify new hardware. LOFTID, utilizing an Inflation System built primarily hardware from IRVE-3 spares, successfully flew in November of 2022. This paper will outline the mission differences, the test campaign used to prepare LOFTID’s Inflation System for flight, and some lessons learned in repurposing older hardware.

Inflation System↗
NASA NTRSDate not supplied

A Heritage BioSensor for Lunar Biology Experiments

Introduction: Automated biological experiments on small spacecraft missions have gained prominence over the past decade due to their simplicity, accessibility, and small mass, volume, and power needs. Most recently, the BioSensor microfluidic CubeSat payload aboard BioSentinel used an automated microfluidic cell culture system to study the effects of environmental stressors like deep space radiation and microgravity on yeast growth and metabolism. BioSentinel’s successor, the Lunar Explorer Instrument for space biology Applications (LEIA), will study the effects of lunar gravity and radiation using an improved version of the BioSensor microfluidic platform. The BioSensor payload has great adaptability to host a diverse range of biological experiments with single- and multi-celled organisms in both crewed and uncrewed missions, making it a compelling candidate for future space biology studies in a lunar surface environment. BioSensor Instrumentation on BioSentinel: The first spaceflight mission with the BioSensor, BioSentinel’s biology experiments occurred at three locations -- deep space, ISS and ground. The payload contained 18 microfluidic cards, each featuring 16 growth wells (a total of 288 growth wells). Each well was loaded before launch with desiccated yeast. In space, liquid culture medium (nutrients) was automatically introduced to batches of wells at a time to initiate a series of biology experiments. Temperature was maintained by thin film heaters on both sides of each card. Each well was equipped with three LEDs emitting at 570 nm, 630 nm, and 850 nm, paired with photodetectors to measure cell concentration and the alamarBlue (metabolic indicator dye) color transition from blue to pink. Phenotypic parameters like cell viability, metabolic rate, and generation time can be derived from these measurements. The sequence and timing of fluid fills, optical measurements, and thermal control were stored onboard, but could be updated asynchronously via ground communication. LEIA: LEIA is slated for launch no earlier than 2026 on a CLPS lander. BioSentinel’s BioSensor has been modified for use in LEIA. These improvements include: (a) storage for multiple culture medium types, (b) additional LED color (465 nm) for a new biological assay for antioxidant (carotenoid) production, (c) housing modifications for later biology load before launch, (d) improved isolation between electronic and fluidic components, and (e) improved humidity control for prolonged organism viability in case of post-load launch delay. Future Prospects: The consistent and successful demonstration of complex fluidics platforms alongside reliable instrument operations in a space environment is poised to create strong momentum for BioSensor-based biological experiment payloads. Planned future developments with the BioSensor include extending compatibility to a broader range of organisms and assays. Preliminary work has already demonstrated successful growth of Arabidopsis seedlings in fluidic cards. With a few modifications to the optical assembly, the setup could easily measure photosynthetic traits in plants and cyanobacteria. The addition of fluorescence measurements and generation of novel luminescent assays will elevate BioSensor’s functionality further. Beyond the BioSensor’s potential uses on free-flyer missions, ISS and Gateway, and CLPS landers, deploying the BioSensor to the lunar surface or in an artificial habitat on crewed missions could enable pioneering research on both how life responds to lunar conditions and future bioproduction capabilities making the BioSensor an indispensable tool for future space biology research.

Chinmayee Govinda Raj↗
NASA NTRS2026

Surprisingly Enriched CO and CH4 in Halley-type Comet 13P/Olbers: Clues to Its Interstellar Heritage

The native ice composition of Halley-type Comet 13P/Olbers (hereafter 13P) was measured post-perihelion, on UT 2024 August 16 using iSHELL, the 1–5 μm cross-dispersed, high-resolution facility spectrograph at the NASA InfraRed Telescope Facility. At that time, the heliocentric distance (Rh) of 13P was 1.37 au and the geocentric distance (Δ) was 1.99 au. Using a slit that delivered spectral resolving power RP λ/Δλ 4.5 × 104, two instrument settings targeted rovibrational emissions of seven parent molecules released into the coma through sublimation of ices in the nucleus. These settings provided broad and contiguous or nearly contiguous spectral coverage, one simultaneously measuring H2O, CO, and OCS, and the other simultaneously measuring CH4, C2H6, CH3OH, and H2CO. Meaningful abundances were obtained for all seven species. Our study revealed substantial enrichments of CO and CH4, the two most volatile species systematically targeted at IR wavelengths in comets. Relative to their respective mean abundance ratios among measured comets from the Oort cloud reservoir, CO in 13P was enriched by a factor of about six and CH4 was enriched by a factor of about three. Together with near-average abundances measured for CH3OH and C2H6, this suggests large endowments of CO and CH4 on interstellar grains, yet it could indicate inhibited surface chemistry on the pre-cometary grains subsequently contained in the nucleus or 13P. Assuming that this represents the primordial composition of 13P, it could reflect very low temperatures in its natal environment (∼10 K or lower).

Michael A Disanti↗
NASA NTRS2009

Design Evolution and Verification of the A-3 Chemical Steam Generator

Following is an overview of the Chemical Steam Generator system selected to provide vacuum conditions for a new altitude test facility, the A-3 Test Stand at Stennis Space Center (SSC) in Bay St. Louis, MS. A-3 will serve as NASA s primary facility for altitude testing of the J-2X rocket engine, to be used as the primary propulsion device for the upper stages of the Ares launch vehicles. The Chemical Steam Generators (CSGs) will produce vacuum conditions in the test cell through the production and subsequent supersonic ejection of steam into a diffuser downstream of the J-2X engine nozzle exit. The Chemical Steam Generators chosen have a rich heritage of operation at rocket engine altitude test facilities since the days of the Apollo program and are still in use at NASA White Sands Test Facility (WSTF) in New Mexico. The generators at WSTF have been modified to a degree, but are still very close to the heritage design. The intent for the A-3 implementation is to maintain this heritage design as much as possible, making minimal updates only where necessary to substitute for obsolete parts and to increase reliability. Reliability improvements are especially desired because the proposed system will require 27 generators, which is nine times the largest system installed in the 1960s. Improvements were suggested by the original design firm, Reaction Motors, by NASA SSC and NASA WSTF engineers, and by the A-3 test stand design contractor, Jacobs Technology, Inc. (JTI). This paper describes the range of improvements made to the design to date, starting with the heritage generator and the minor modifications made over time at WSTF, to the modernized configuration which will be used at A-3. The paper will discuss NASA s investment in modifications to SSC s E-2 test facility fire a full-scale Chemical Steam Generator in advance of the larger steam system installation at A-3. Risk mitigation testing will be performed in early 2009 at this test facility to verify that the CSGs operate as expected. The generator which will undergo this testing is of the most recent A-3 configuration, and will be instrumented far in excess of what is normally required for operation. The extra data will allow for easier troubleshooting and more complete knowledge of expected generator performance. In addition, the early testing will give SSC personnel experience in operating the CSG systems, which will expedite the process of installation and activation at A-3. Each Chemical Steam Generator is supported by a complement of valves, instruments, and flow control devices, with the entire assembly called a "module." The generators will be installed in groups of three, historically called "units". A module is so called because of its modular ability to be replaced or serviced without disturbing the other two modules installed on the same unit. A module is pictured in Figure 1, shown with its generator secured by white bands in its shipping (vs. installed) configuration. The heritage system at WSTF is composed of a single unit (three generator modules), pictured in Figure 2 as it was installed in 1965. In contrast, A-3 will have nine units operating in parallel to achieve vacuum conditions appropriate for testing the J-2X engine. Each of the combustors operates in two modes and achieves the so-called "full-steam" mode after all three of its stages ignite. Ignition of the first stage is achieved by exciting a spark plug; the second stage and main stage are lit by the flame front of the previous stage. The main stage burns approximately 97% of the total propellant flow and uses the heat energy to vaporize water into superheated steam. While the main stage remains unlit, the combustor is in so-called "idle" mode. In the WSTF system, this idle mode is not optimized for water usage, and does not need to be, as the water is pumped from a large reservoir. The water supply at A-3 will be contained in tanks with finite volume, so water optimization is preferred for the modnized configuration. Multiple solutions for this issue have been proposed, with the leading concept being a change to the operational definition of "idle mode," with the generator running in a lower heat flux condition.

Kirchner, Casey K.↗
NASA NTRS2013

The HERschel Inventory of the Agents of Galaxy Evolution in the Magellanic Clouds, a HERschel Open Time Key Program

We present an overview or the HERschel Inventory of The Agents of Galaxy Evolution (HERITAGE) in the Magellanic Clouds project, which is a Herschel Space Observatory open time key program. We mapped the Large Magellanic Cloud (LMC) and Small Magellanic Cloud (SMC) at 100, 160, 250, 350, and 500 micron with the Spectral and Photometric Imaging Receiver (SPIRE) and Photodetector Array Camera and Spectrometer (PACS) instruments on board Herschel using the SPIRE/PACS parallel mode. The overriding science goal of HERITAGE is to study the life cycle of matter as traced by dust in the LMC and SMC. The far-infrared and submillimeter emission is an effective tracer of the interstellar medium (ISM) dust, the most deeply embedded young stellar objects (YSOs), and the dust ejected by the most massive stars. We describe in detail the data processing, particularly for the PACS data, which required some custom steps because of the large angular extent of a single observational unit and overall the large amount of data to be processed as an ensemble. We report total global fluxes for LMC and SMC and demonstrate their agreement with measurements by prior missions. The HERITAGE maps of the LMC and SMC are dominated by the ISM dust emission and bear most resemblance to the tracers of ISM gas rather than the stellar content of the galaxies. We describe the point source extraction processing and the critetia used to establish a catalog for each waveband for the HERITAGE program. The 250 micron band is the most sensitive and the source catalogs for this band have approx. 25,000 objects for the LMC and approx. 5500 objects for the SMC. These data enable studies of ISM dust properties, submillimeter excess dust emission, dust-to-gas ratio, Class 0 YSO candidates, dusty massive evolved stars, supemova remnants (including SN1987A), H II regions, and dust evolution in the LMC and SMC. All images and catalogs are delivered to the Herschel Science Center as part of the conummity support aspects of the project. These HERITAGE images and catalogs provide an excellent basis for future research and follow up with other facilities.

AGENTS↗
NASA NTRS2017

Development of the European Service Module Propulsion Subsystem for the Multi-Purpose Crew Vehicle

Hardware Heritage Schedule limitations and budget constraints drove the need for extensive use of heritage hardware designs. In some cases (OMS and TVC) flight hardware reuse (from Shuttle) was required,and will be delta-qualified for use on Orion Primary sources of heritage: ATV Shuttle Orion CM PSS Ariane 5 EPS Targeted Development Testing Component development testing was performed to address the highest risk areas of heritage design compliance with Orion requirements Assembly level development testing was performed to understand complex assemblies and component interactions Heritage Direct re-use of assets from Shuttle Orbiters, all assets have varying flight history. Orion Use Used by Orion to gimbal the main engine during major translational maneuvers Development Testing Random vibration on controller box (lead to card retention design mod) Design Changes (only as required) Circuit board retention in controller box (single instance from Shuttle flight history) New, longer harnesses Basic Specs(8) fixed position engines Thrust: 105 lbf Nozzle area ratio: 164:1 Orion Use Nominally used for separation maneuvers and mid-course correction maneuvers In contingency scenario (failed main engine), used for major translational maneuvers Drives the need for long continuous duration firing Drives the need for off-pulsing (to steer) Control authority requires 50 duty cycle Development Testing Random Vibration (added vibration isolation bracket) Hot fire, duty cycle (changed MR)

pressure fed↗
NASA NTRS2022

Flight Software Dictionary Development for the Mars2020 Rover

The Mars2020 project, developed and operated by the Jet Propulsion Laboratory (JPL), successfully landed the Perseverance rover and its flying companion Ingenuity on the surface of Mars on February 18th 2021. Perseverance combines heritage and cutting-edge flight software and hardware to accomplish crucial mission requirements related to Martian surface sampling. The design, development, and operation of NASA’s large strategic science missions require the ability to communicate spacecraft capabilities to hundreds of engineers across multiple disciplines. The interaction between flight and ground software development, Verification and Validation (V&V), Assembly, Test, and Launch Operations (ATLO), and management each demand quick understanding of unique slices of information for each discipline. This information includes the current capabilities of the flight system as well as future capabilities and their status as they are developed and tested. Despite the fundamental and critical nature of this information, the flight software dictionaries used to track it are a stumbling block for many projects. These dictionaries provide the cornerstone for the interpretation of data sent from the spacecraft, allowing for quick comprehension by engineers on the ground. During both spacecraft development and operations, flight software dictionary management includes significant challenges due to the large number of interfacing systems and the subtle yet distinct needs of each.The engineering of flight software dictionaries for Mars2020 had numerous challenges, most-notably: parallel dictionary development to support simultaneous separate flight software build campaigns for each mission phase (cruise and surface), managing requests for operations-enabling information without perturbing the heritage interface with the rover, and the introduction of new tools by the dictionary stakeholders that forced the dictionary team to innovate and redesign the heritage tool chain. These challenges generated guiding principles for the dictionary development effort: emphasize coding best practices and unit testing in the dictionary code development tool chain, use institutionally provided COTS (commercial-off-the-shelf) tools whenever possible, and maintain the heritage flight-ground interface all while advancing operations-enabling information via a loosely coupled interface.Throughout development and operations, the Mars2020 dictionary toolchain included IBM DOORS Next Generation, GitHub, Microsoft Excel, Docker, Jenkins, and a significant custom-built Python codebase. Significant interfaces included JPL’s command and control software, heritage flight software team tools and processes, and the many cloud-based ground tools developed for the mission.This paper will discuss the requirements for the Mars2020 dictionary development, the development team’s response to those requirements, lessons learned throughout the process, steps taken towards automated deliveries and continuous integration of stakeholder inputs, potential toolchain improvements for Mars2020, and key takeaways that could be applied to future missions.

Pyrzak, Guy↗
NASA NTRS2013

Flight Hardware Packaging Design for Stringent EMC Radiated Emission Requirements

This packaging design approach can help heritage hardware meet a flight project's stringent EMC radiated emissions requirement. The approach requires only minor modifications to a hardware's chassis and mainly concentrates on its connector interfaces. The solution is to raise the surface area where the connector is mounted by a few millimeters using a pedestal, and then wrapping with conductive tape from the cable backshell down to the surface-mounted connector. This design approach has been applied to JPL flight project subsystems. The EMC radiated emissions requirements for flight projects can vary from benign to mission critical. If the project's EMC requirements are stringent, the best approach to meet EMC requirements would be to design an EMC control program for the project early on and implement EMC design techniques starting with the circuit board layout. This is the ideal scenario for hardware that is built from scratch. Implementation of EMC radiated emissions mitigation techniques can mature as the design progresses, with minimal impact to the design cycle. The real challenge exists for hardware that is planned to be flown following a built-to-print approach, in which heritage hardware from a past project with a different set of requirements is expected to perform satisfactorily for a new project. With acceptance of heritage, the design would already be established (circuit board layout and components have already been pre-determined), and hence any radiated emissions mitigation techniques would only be applicable at the packaging level. The key is to take a heritage design with its known radiated emissions spectrum and repackage, or modify its chassis design so that it would have a better chance of meeting the new project s radiated emissions requirements.

Lortz, Charlene L.↗
NASA NTRSDate not supplied

Gimbal Bearing Friction in the SLS Core Stage Thrust Vector Control System

The Space Launch System (SLS) Core Stage Thrust Vector Control (TVC) system is comprised of eight mechanical feedback Shuttle heritage Type III TVC actuators that vector the four Shuttle heritage RS-25 engines about a Shuttle heritage gimbal block/bearing. The MSFC Controls community has long regarded gimbal friction to be a negligible effect on the overall control of gimbaled RS-25 engines. This is corroborated by Space Shuttle test and flight data that does not appear to show degraded effects, nor limit cycling at the end of the shuttle flight. For this reason, friction was not expected to be a driving factor of performance and control of the reused RS-25 engines aboard the SLS. However, after test data showed a large shift in frequency behavior and a highly damped step-response in the time series, there was further investigation into what could have caused this behavior. Heritage friction models used in previous gimbal and ball bearings were evaluated such as Coulomb, Dahl and LuGre, but the single degree of freedom friction models alone were not enough to explain the behavior and shifts seen in the test data. This paper presents the additional findings and modeling efforts regarding friction on the RS-25 engines. Using the Two Actuator Operational Simulation (TAOS), the difference from modeling separate friction degrees of freedom to coupled degrees of freedom was investigated to deduce the effects of one axis’s movement on the other. Next, due to the vibration environment, a modified LuGre model has been proposed that adds an additional term to decrease the friction coefficient at low engine velocity amplitudes. Lastly, the addition of the stiffness in each half of the gimbal bearing has increased modeling fidelity by also adding the effect on the gimbal bearing bending in compliance to both the friction torque on the surface of the gimbal bearing and the actuator force that is forcing the engine in a specified direction. Through these effects, the time and frequency domain behavior seen in test can be characterized accurately.

Friction↗
NASA NTRSDate not supplied

Gimbal Bearing Friction in the SLS Core Stage Thrust Vector Control System

The Space Launch System (SLS) Core Stage Thrust Vector Control (TVC) system is comprised of eight mechanical feedback Shuttle heritage Type III TVC actuators that vector the four Shuttle heritage RS-25 engines about a Shuttle heritage gimbal block/bearing. The MSFC Controls community has long regarded gimbal friction to be a negligible effect on the overall control of gimbaled RS-25 engines. This is corroborated by Space Shuttle test and flight data that does not appear to show degraded effects, nor limit cycling at the end of the shuttle flight. For this reason, friction was not expected to be a driving factor of performance and control of the reused RS-25 engines aboard the SLS. However, after test data showed a large shift in frequency behavior and a highly damped step-response in the time series, there was further investigation into what could have caused this behavior. Heritage friction models used in previous gimbal and ball bearings were evaluated such as Coulomb, Dahl and LuGre, but the single degree of freedom friction models alone were not enough to explain the behavior and shifts seen in the test data. This paper presents the additional findings and modeling efforts regarding friction on the RS-25 engines. Using the Two Actuator Operational Simulation (TAOS), the difference from modeling separate friction degrees of freedom to coupled degrees of freedom was investigated to deduce the effects of one axis’s movement on the other. Next, due to the vibration environment, a modified LuGre model has been proposed that adds an additional term to decrease the friction coefficient at low engine velocity amplitudes. Lastly, the addition of the stiffness in each half of the gimbal bearing has increased modeling fidelity by also adding the effect on the gimbal bearing bending in compliance to both the friction torque on the surface of the gimbal bearing and the actuator force that is forcing the engine in a specified direction. Through these effects, the time and frequency domain behavior seen in test can be characterized accurately.

Friction↗
NASA NTRSDate not supplied

Space ROS TOFU: Flying Space ROS with Containerized Hybrid Trust

Space ROS is a distribution of Robot Operating System 2 (ROS2) targeting the specific requirements of flight software and spaceborne robotics while maintaining the flexibility that has made ROS indispensible for robotics research and industrial system integration. With Space ROS, a project can leverage the existing ROS2 ecosystem to reduce redundant development while tackling increasingly complex demands for on-device intelligence; however, there is no substitute for flight heritage to combat the risk-aversion common to spaceflight projects, and Space ROS has yet to fly. To break the collective-action standoff and gain valuable flight experience, the Distributed Spacecraft Autonomy (DSA) team at NASA Ames Research Center developed Opportunistic Software Experiments for Spacecraft Autonomy Testbeds (OSE-SAT) architecture, utilizing containerization to execute lower-trust software under traditionally verified heritage flight software for demonstration on-orbit. OSE-SAT leverages a hybrid-trust model where flexible, complex components like Space ROS can run without risk to the host spacecraft while providing validated feedback to a highly scrutinized, trusted core. We leverage this testbed to demonstrate Space ROS in flight, building heritage, and experience for projects with "Trust On First Use" (TOFU) requirements for flight heritage. We present a Space ROS component for OSE-SAT, lessons learned integrating Space ROS into a flight software stack, and the results of the first known use of Space ROS in orbit.

small satellites↗
NASA NTRS1990

Systems engineering and integration: Cost estimation and benefits analysis

Space Transportation Avionics hardware and software cost has traditionally been estimated in Phase A and B using cost techniques which predict cost as a function of various cost predictive variables such as weight, lines of code, functions to be performed, quantities of test hardware, quantities of flight hardware, design and development heritage, complexity, etc. The output of such analyses has been life cycle costs, economic benefits and related data. The major objectives of Cost Estimation and Benefits analysis are twofold: (1) to play a role in the evaluation of potential new space transportation avionics technologies, and (2) to benefit from emerging technological innovations. Both aspects of cost estimation and technology are discussed here. The role of cost analysis in the evaluation of potential technologies should be one of offering additional quantitative and qualitative information to aid decision-making. The cost analyses process needs to be fully integrated into the design process in such a way that cost trades, optimizations and sensitivities are understood. Current hardware cost models tend to primarily use weights, functional specifications, quantities, design heritage and complexity as metrics to predict cost. Software models mostly use functionality, volume of code, heritage and complexity as cost descriptive variables. Basic research needs to be initiated to develop metrics more responsive to the trades which are required for future launch vehicle avionics systems. These would include cost estimating capabilities that are sensitive to technological innovations such as improved materials and fabrication processes, computer aided design and manufacturing, self checkout and many others. In addition to basic cost estimating improvements, the process must be sensitive to the fact that no cost estimate can be quoted without also quoting a confidence associated with the estimate. In order to achieve this, better cost risk evaluation techniques are needed as well as improved usage of risk data by decision-makers. More and better ways to display and communicate cost and cost risk to management are required.

Dean, ED↗