SEARCH · Search NASA

Results for “lessons learned process”

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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 127 records · Page 7

All sources NASA NTRS DOE OSTI

NASA NTRS2012

Model Based Systems Engineering on the Europa Mission Concept Study

At the start of 2011, the proposed Jupiter Europa Orbiter (JEO) mission was staffing up in expectation of becoming an official project later in the year for a launch in 2020. A unique aspect of the pre-project work was a strong emphasis and investment on the foundations of Model-Based Systems Engineering (MBSE). As so often happens in this business, plans changed: NASA's budget and science priorities were released and together fundamentally changed the course of JEO. As a result, it returned to being a study task whose objective is to propose more affordable ways to accomplish the science. As part of this transition, the question arose as to whether it could continue to afford the investment in MBSE. In short, the MBSE infusion has survived and is providing clear value to the study effort. By leveraging the existing infrastructure and a modest additional investment, striking advances in the capture and analysis of designs using MBSE were achieved. In the process, the need to remain relevant in the new environment has brought about a wave of innovation and progress. The effort has reaffirmed the importance of architecting. It has successfully harnessed the synergistic relationship of architecting to system modeling. We have found that MBSE can provide greater agility than traditional methods. We have also found that a diverse 'ecosystem' of modeling tools and languages (SysML, Mathematica, even Excel) is not only viable, but an important enabler of agility and adaptability. This paper will describe the successful application of MBSE in the dynamic environment of early mission formulation, the significant results produced and lessons learned in the process.

Bayer, Todd J.↗

NASA NTRS2011

Gain Scheduling for the Orion Launch Abort Vehicle Controller

One of NASAs challenges for the Orion vehicle is the control system design for the Launch Abort Vehicle (LAV), which is required to abort safely at any time during the atmospheric ascent portion of ight. The focus of this paper is the gain design and scheduling process for a controller that covers the wide range of vehicle configurations and flight conditions experienced during the full envelope of potential abort trajectories from the pad to exo-atmospheric flight. Several factors are taken into account in the automation process for tuning the gains including the abort effectors, the environmental changes and the autopilot modes. Gain scheduling is accomplished using a linear quadratic regulator (LQR) approach for the decoupled, simplified linear model throughout the operational envelope in time, altitude and Mach number. The derived gains are then implemented into the full linear model for controller requirement validation. Finally, the gains are tested and evaluated in a non-linear simulation using the vehicles ight software to ensure performance requirements are met. An overview of the LAV controller design and a description of the linear plant models are presented. Examples of the most significant challenges with the automation of the gain tuning process are then discussed. In conclusion, the paper will consider the lessons learned through out the process, especially in regards to automation, and examine the usefulness of the gain scheduling tool and process developed as applicable to non-Orion vehicles.

McNamara, Sara J.↗

NASA NTRS2013

Moving Technologies from the Test Tube to Commercial Products

Successful technologies include objects, processes, and procedures that share a common theme; they are being used to generate new products that create economic growth. The foundation is the invention, but the invention is a small part of the overall effort. The pathway to success is understanding the competition, proper planning, record keeping, integrating a supply chain, understanding actual costs, intellectual property (IP), benchmarking, and timing. Additionally, there are obstacles that include financing, what to make, buy, and sell, and the division of labor i.e. recognizing who is best at what task. Over the past two decades, NASA Langley Research Center (LaRC) has developed several commercially available technologies. The approach to commercialization of three of these inventions; Langley Research Center-Soluble Imide (LaRC-SI, Imitec Inc.), the Thin Layer Unimorph Driver (THUNDER, FACE International), and the Macrofiber Composite (MFC, Smart Material Corp.) will be described, as well as some of the lessons learned from the process. What makes these three inventions interesting is that one was created in the laboratory; another was built using the previous invention as part of its process, and the last one was created by packaging commercial-off-the-shelf (COTS) materials thereby creating a new component.

Bryant, Robert G.↗

DOE OSTI2026

MINERvA s Open Data Product: A First for Neutrino Data Preservation

Access to information on neutrino nucleus interactions is critical to the success of all neutrino oscillation experiments. MINERvA's rich dataset covers a range of energies and nuclei unique amongst experiments, and as such is critical to the community in building the important shared knowledge needed to unravel the mysteries of the neutrino. In particular, its dataset provides the greatest statistical coverage in in the range of neutrino energies pertinent for DUNE until DUNE's near detector begins operation. Historically, such significant datasets in neutrino physics have been preserved primarily through their published results. While meaningful and useful, this limits the ability to explore the data to its fullest extent as new perspectives continue to form. MINERvA has undertaken a major effort to break this trend and preserve its data in a format to be as analyzable as possible from outside the collaboration. This has culminated in the officially-released MINERvA Open Data Product for the community to take advantage of and utilize. Maintaining direct access to the dataset in an analyzable form will allow new insights to continue to be extracted indefinitely. This talk will cover the contents of this product, the information included (and excluded), the tools provided to utilize the product effectively, the support MINERvA intends to provide in its use, and some lessons learned through the process.

Last, David [Rochester U.] (ORCID:0000000245147183↗

NASA NTRS1972

Formulation of an effective safety design review for the Skylab Program.

The Skylab Program is presenting a unique set of requirements by extending the capabilities of both men and equipment to withstand extended periods of time in space. The progression of space programs which preceded Skylab have provided a set of building blocks of knowledge and experience coupled with an extensive ground test program which makes it possible to plan its flight program without earlier, unmanned test flights. This approach, however, makes it mandatory that to the maximum extent possible, we factor into the design review process all the 'lessons learned' which are applicable. It is this conscious review of the Skylab design, based on checklists prepared from design criteria, gleaned from a variety of sources and experiences, which is the subject of this paper. A brief description of the Skylab Program, its objectives, and the missions planned for it are presented briefly to better understand the degree of extrapolation of hardware development from previous programs.

Cohen, H.↗

NASA NTRS1988

Post-Challenger evaluation of space shuttle risk assessment and management

As the shock of the Space Shuttle Challenger accident began to subside, NASA initiated a wide range of actions designed to ensure greater safety in various aspects of the Shuttle system and an improved focus on safety throughout the National Space Transportation System (NSTS) Program. Certain specific features of the NASA safety process are examined: the Critical Items List (CIL) and the NASA review of the Shuttle primary and backup units whose failure might result in the loss of life, the Shuttle vehicle, or the mission; the failure modes and effects analyses (FMEA); and the hazard analysis and their review. The conception of modern risk management, including the essential element of objective risk assessment is described and it is contrasted with NASA's safety process in general terms. The discussion, findings, and recommendations regarding particular aspects of the NASA STS safety assurance process are reported. The 11 subsections each deal with a different aspect of the process. The main lessons learned by SCRHAAC in the course of the audit are summarized.

Source record↗

NASA NTRS1989

The Real Time Interactive Display Environment (RTIDE), a display building tool developed by Space Shuttle flight controllers

NASA's Mission Control Center, located at Johnson Space Center, is incrementally moving from a centralized architecture to a distributed architecture. Starting with STS-29, some host-driven console screens will be replaced with graphics terminals driven by workstations. These workstations will be supplied realtime data first by the Real Time Data System (RTDS), a system developed inhouse, and then months later (in parallel with RTDS) by interim and subsequently operational versions of the Mission Control Center Upgrade (MCCU) software package. The Real Time Interactive Display Environment (RTIDE) was built by Space Shuttle flight controllers to support the rapid development of multiple new displays to support Shuttle flights. RTIDE is a display building tool that allows non-programmers to define object-oriented, event-driven, mouseable displays. Particular emphasis was placed on upward compatibility between RTIDE versions, ability to acquire data from different data sources, realtime performance, ability to modularly upgrade RTIDE, machine portability, and a clean, powerful user interface. The operational and organizational factors that drove RTIDE to its present form, the actual design itself, simulation and flight performance, and lessons learned in the process are discussed.

Kalvelage, Thomas A.↗

NASA NTRS1995

High-Temperature Optical Window Design

A high-temperature optical window is essential to the optical diagnostics of high-temperature combustion rigs. Laser Doppler velocimetry, schlieren photography, light sheet visualization, and laser-induced fluorescence spectroscopy are a few of the tests that require optically clear access to the combustor flow stream. A design was developed for a high-temperature window that could withstand the severe environment of the NASA Lewis 3200 F Lean Premixed Prevaporized (LPP) Flame Tube Test Rig. The development of this design was both time consuming and costly. This report documents the design process and the lessons learned, in an effort to reduce the cost of developing future designs for high-temperature optical windows.

Roeloffs, Norman↗

NASA NTRS2001

Lessons from Adaptive Level One Accelerator (ALOA) System Implementation

The Adaptive Level One Accelerator (ALOA) system was developed as part of the Earth Science Data and Information System (ESDIS) project. The reconfigurable computing technologies were investigated for Level 1 satellite telemetry data processing to achieve computing acceleration and cost reduction for the next-generation Level 1 data processing systems. The MODIS instrument calibration algorithm was implemented using reconfigurable a computer. The system development process and the lessons learned throughout the design cycle are summarized in this paper.

Patel, Umesh D.↗

NASA NTRS2002

Secure Remote Access Issues in a Control Center Environment

The ISS finally reached an operational state and exists for local and remote users. Onboard payload systems are managed by the Huntsville Operations Support Center (HOSC). Users access HOSC systems by internet protocols in support of daily operations, preflight simulation, and test. In support of this diverse user community, a modem security architecture has been implemented. The architecture has evolved over time from an isolated but open system to a system which supports local and remote access to the ISS over broad geographic regions. This has been accomplished through the use of an evolved security strategy, PKI, and custom design. Through this paper, descriptions of the migration process and the lessons learned are presented. This will include product decision criteria, rationale, and the use of commodity products in the end architecture. This paper will also stress the need for interoperability of various products and the effects of seemingly insignificant details.

Pitts, Lee↗

NASA NTRS2002

Secure Payload Access to the International Space Station

Pitts, R. Lee↗

NASA NTRS2004

Identifying, Assessing, and Mitigating Risk of Single-Point Inspections on the Space Shuttle Reusable Solid Rocket Motor

In the production of each Space Shuttle Reusable Solid Rocket Motor (RSRM), over 100,000 inspections are performed. ATK Thiokol Inc. reviewed these inspections to ensure a robust inspection system is maintained. The principal effort within this endeavor was the systematic identification and evaluation of inspections considered to be single-point. Single-point inspections are those accomplished on components, materials, and tooling by only one person, involving no other check. The purpose was to more accurately characterize risk and ultimately address and/or mitigate risk associated with single-point inspections. After the initial review of all inspections and identification/assessment of single-point inspections, review teams applied risk prioritization methodology similar to that used in a Process Failure Modes Effects Analysis to derive a Risk Prioritization Number for each single-point inspection. After the prioritization of risk, all single-point inspection points determined to have significant risk were provided either with risk-mitigating actions or rationale for acceptance. This effort gave confidence to the RSRM program that the correct inspections are being accomplished, that there is appropriate justification for those that remain as single-point inspections, and that risk mitigation was applied to further reduce risk of higher risk single-point inspections. This paper examines the process, results, and lessons learned in identifying, assessing, and mitigating risk associated with single-point inspections accomplished in the production of the Space Shuttle RSRM.

Greenhalgh, Phillip O.↗

NASA NTRS2005

Toward a Benchmark for Multi-Threaded Testing Tools

Looking for intermittent bugs is a problem that has been getting prominence in testing. Multi-threaded code is becoming very common, mostly on the server side. As there is no silver bullet solution, research focuses on a variety of partial solutions. We outline a road map for combining the research on the different disciplines of testing multi-threaded programs and on evaluating its quality. The project goals are to create a benchmark that can be used to evaluate different solutions, to create a framework with open API's that enables combining techniques in the multithreading domain, and to create a focus for the research in this area around which a community of people who try to solve similar problems with different techniques, could congregate. The benchmark, apart from containing programs with documented bugs, includes other artifacts, such as traces, that are used for evaluating some of the technologies. We have started creating such a bench mrk and detail the lesson learned in the process. The framework will enable technology developers, for example, race detectors, to concentrate on their components and use other ready made components, (e.g., instrumentor) to create a testing solution.

Eytani, Yaniv↗

NASA NTRS2007

Integration and Testing Challenges of Small, Multiple Satellite Missions: Experiences From The Space Technology 5 Project

This brief presentation describes the mechanical and electrical integration activities and environmental testing challenges of the Space Technology 5 (ST5) Project. Lessons learned during this process are highlighted, including performing mechanical activities serially to gain efficiency through repetition and performing electrical activities based on the level of subsystem expertise available.

Sauerwein, Timothy A.↗

NASA NTRS2011

Space Shuttle Day-of-Launch Trajectory Design Operations

A top priority of any launch vehicle is to insert as much mass into the desired orbit as possible. This requirement must be traded against vehicle capability in terms of dynamic control, thermal constraints, and structural margins. The vehicle is certified to specific structural limits which will yield certain performance characteristics of mass to orbit. Some limits cannot be certified generically and must be checked with each mission design. The most sensitive limits require an assessment on the day-of-launch. To further minimize vehicle loads while maximizing vehicle performance, a day-of-launch trajectory can be designed. This design is optimized according to that day s wind and atmospheric conditions, which increase the probability of launch. The day-of-launch trajectory design and verification process is critical to the vehicle s safety. The Day-Of-Launch I-Load Update (DOLILU) is the process by which the National Aeronautics and Space Administration's (NASA) Space Shuttle Program tailors the vehicle steering commands to fit that day s environmental conditions and then rigorously verifies the integrated vehicle trajectory s loads, controls, and performance. This process has been successfully used for almost twenty years and shares many of the same elements with other launch vehicles that execute a day-of-launch trajectory design or day-of-launch trajectory verification. Weather balloon data is gathered at the launch site and transmitted to the Johnson Space Center s Mission Control. The vehicle s first stage trajectory is then adjusted to the measured wind and atmosphere data. The resultant trajectory must satisfy loads and controls constraints. Additionally, these assessments statistically protect for non-observed dispersions. One such dispersion is the change in the wind from the last measured balloon to launch time. This process is started in the hours before launch and is repeated several times as the launch count proceeds. Should the trajectory design not meet all constraint criteria, Shuttle would be No-Go for launch. This Shuttle methodology is very similar to other unmanned launch vehicles. By extension, this method would likely be employed for any future NASA launch vehicle. This paper will review the Shuttle s day-of-launch trajectory optimization and verification operations as an example of a more generic application of day-of-launch design and validation. With Shuttle s retirement, it is fitting to document the current state of this critical process and capture lessons learned to benefit current and future launch vehicle endeavors.

Harrington, Brian E.↗

NASA NTRS2011

Ares I-X Range Safety Simulation Verification and Analysis Independent Validation and Verification

NASA s Ares I-X vehicle launched on a suborbital test flight from the Eastern Range in Florida on October 28, 2009. To obtain approval for launch, a range safety final flight data package was generated to meet the data requirements defined in the Air Force Space Command Manual 91-710 Volume 2. The delivery included products such as a nominal trajectory, trajectory envelopes, stage disposal data and footprints, and a malfunction turn analysis. The Air Force s 45th Space Wing uses these products to ensure public and launch area safety. Due to the criticality of these data, an independent validation and verification effort was undertaken to ensure data quality and adherence to requirements. As a result, the product package was delivered with the confidence that independent organizations using separate simulation software generated data to meet the range requirements and yielded consistent results. This document captures Ares I-X final flight data package verification and validation analysis, including the methodology used to validate and verify simulation inputs, execution, and results and presents lessons learned during the process

Merry, Carl M.↗

NASA NTRS2012

Early Formulation Model-centric Engineering on Nasa's Europa Mission Concept Study

By leveraging the existing Model-Based Systems Engineering (MBSE) infrastructure at JPL and adding a modest investment, the Europa Mission Concept Study made striking advances in mission concept capture and analysis. This effort has reaffirmed the importance of architecting and successfully harnessed the synergistic relationship of system modeling to mission architecting. It clearly demonstrated that MBSE can provide greater agility than traditional systems engineering methods. This paper will describe the successful application of MBSE in the dynamic environment of early mission formulation, the significant results produced and lessons learned in the process.

science mission afforability↗

NASA NTRS2016

MOPITT Mechanisms 16 Years In-Orbit Operation on TERRA

The 16th anniversary of the launch of NASA's Terra Spacecraft was marked on December 18, 2015, with the Measurements of Pollution in the Troposphere (MOPITT) instrument being a successful contributor to the NASA EOS flagship. MOPITT has been enabled by a large suite of mechanisms, allowing the instrument to perform long-duration monitoring of atmospheric carbon monoxide, providing global measurements of this important greenhouse gas for 16 years. Mechanisms have been successfully employed for scanning, cooling of detectors, and to optically modulate the gas path length within the instrument by means of pressure and gas cell length variation. The instrument utilizes these devices to perform correlation spectroscopy, enabling measurements with vertical resolution from the nadir view, and has thereby furthered understanding of source and global transport effects of carbon monoxide. Given the design requirement for a 5.25-year lifetime, the stability and performance of the majority of mechanisms have far surpassed design goals. With 16 continuously operating mechanisms in service on MOPITT, including 12 rotating mechanisms and 4 with linear drive elements, the instrument was an ambitious undertaking. The long life requirements combined with demands for cleanliness and optical stability made for difficult design choices including that of the selection of new lubrication processes. Observations and lessons learned with regards to many aspects of the mechanisms and associated monitoring devices are discussed here. Mechanism behaviors are described, including anomalies, long-term drive current/power, fill pressure, vibration and cold-tip temperature trends. The effectiveness of particular lubrication formulations and the screening method implemented is discussed in relation to continuous rotating mechanisms and stepper motors, which have exceeded 15 billon rotations and 2.5 billion steps respectively. Aspects of gas cell hermeticity, optical cleanliness, heater problems and SEU effects on accelerometers are also discussed.

Gibson, Andrew S.↗