Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “flight missions”

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 NTRS2017

Security Vulnerability Profiles of NASA Mission Software: Empirical Analysis of Security Related Bug Reports

NASA develops, runs, and maintains software systems for which security is of vital importance. Therefore, it is becoming an imperative to develop secure systems and extend the current software assurance capabilities to cover information assurance and cybersecurity concerns of NASA missions. The results presented in this report are based on the information provided in the issue tracking systems of one ground mission and one flight mission. The extracted data were used to create three datasets: Ground mission IVV issues, Flight mission IVV issues, and Flight mission Developers issues. In each dataset, we identified the software bugs that are security related and classified them in specific security classes. This information was then used to create the security vulnerability profiles (i.e., to determine how, why, where, and when the security vulnerabilities were introduced) and explore the existence of common trends. The main findings of our work include:- Code related security issues dominated both the Ground and Flight mission IVV security issues, with 95 and 92, respectively. Therefore, enforcing secure coding practices and verification and validation focused on coding errors would be cost effective ways to improve mission's security. (Flight mission Developers issues dataset did not contain data in the Issue Category.)- In both the Ground and Flight mission IVV issues datasets, the majority of security issues (i.e., 91 and 85, respectively) were introduced in the Implementation phase. In most cases, the phase in which the issues were found was the same as the phase in which they were introduced. The most security related issues of the Flight mission Developers issues dataset were found during Code Implementation, Build Integration, and Build Verification; the data on the phase in which these issues were introduced were not available for this dataset.- The location of security related issues, as the location of software issues in general, followed the Pareto principle. Specifically, for all three datasets, from 86 to 88 the security related issues were located in two to four subsystems.- The severity levels of most security issues were moderate, in all three datasets.- Out of 21 primary security classes, five dominated: Exception Management, Memory Access, Other, Risky Values, and Unused Entities. Together, these classes contributed from around 80 to 90 of all security issues in each dataset. This again proves the Pareto principle of uneven distribution of security issues, in this case across CWE classes, and supports the fact that addressing these dominant security classes provides the most cost efficient way to improve missions' security. The findings presented in this report uncovered the security vulnerability profiles and identified the common trends and dominant classes of security issues, which in turn can be used to select the most efficient secure design and coding best practices compiled by the part of the SARP project team associated with the NASA's Johnson Space Center. In addition, these findings provide valuable input to the NASA IVV initiative aimed at identification of the two 25 CWEs of ground and flight missions.

vulnerability↗
NASA NTRS2017

Security Vulnerability Profiles of Mission Critical Software: Empirical Analysis of Security Related Bug Reports

While some prior research work exists on characteristics of software faults (i.e., bugs) and failures, very little work has been published on analysis of software applications vulnerabilities. This paper aims to contribute towards filling that gap by presenting an empirical investigation of application vulnerabilities. The results are based on data extracted from issue tracking systems of two NASA missions. These data were organized in three datasets: Ground mission IVV issues, Flight mission IVV issues, and Flight mission Developers issues. In each dataset, we identified security related software bugs and classified them in specific vulnerability classes. Then, we created the security vulnerability profiles, i.e., determined where and when the security vulnerabilities were introduced and what were the dominating vulnerabilities classes. Our main findings include: (1) In IVV issues datasets the majority of vulnerabilities were code related and were introduced in the Implementation phase. (2) For all datasets, around 90 of the vulnerabilities were located in two to four subsystems. (3) Out of 21 primary classes, five dominated: Exception Management, Memory Access, Other, Risky Values, and Unused Entities. Together, they contributed from 80 to 90 of vulnerabilities in each dataset.

Goseva-Popstojanova, Katerina↗
NASA NTRS2006

Qualification of Technologies and Lessons Learned from Satellite LIDAR and Altimeter Missions

Flight qualified laser transmitters for remote sensing applications from space have progressed significantly over the past decade. More laser-based missions are underway and several are recently launched and on route, under flight build, or being proposed. However, most of the progress made in the solid state laser field has not been solely in the technology front, but more in the design and implementation of existing technologies. Recent events in flight laser performance and delivery have resulted in a more conservative process in the selection of laser-based instruments for space. The result of these efforts will hopefully be an improved rate of success and more flight laser mission awards. An overview of these efforts and some results will be presented as well as current and future work at NASA.

Coyle, Donald B.↗
NASA NTRS1995

A scientific assessment of a new technology orbital telescope

As part of a program designed to test the Alpha chemical laser weapons system in space, the Ballistic Missile Defense Organization (BMDO) developed components of an agile, lightweight, 4-meter telescope, equipped with an advanced active-optics system. BMDO had proposed to make space available in the telescope's focal plane for instrumentation optimized for scientific applications in astrophysics and planetary astronomy for a potential flight mission. Such a flight mission could be undertaken if new or additional sponsorship can be found. Despite this uncertainty, BMDO requested assistance in defining the instrumentation and other design aspects necessary to enhance the scientific value of a pointing and tracking mission. In response to this request, the Space Studies Board established the Task Group on BMDO New Technology Orbital Observatory (TGBNTOO) and charged it to: (1) provide instrumentation, data management, and science-operations advice to BMDO to optimize the scientific value of a 4-meter mission; and (2) support a space studies board assessment of the relative scientific merit of the program. This report deals with the first of these tasks, assisting the Advanced Technology Demonstrator's (ATD's) program scientific potential. Given the potential scientific aspects of the 4-meter telescope, this project is referred to as the New Technology Orbital Telescope (NTOT), or as the ATD/NTOT, to emphasize its dual-use character. The task group's basic conclusion is that the ATD/NTOT mission does have the potential for contributing in a major way to astronomical goals.

Source record↗
NASA NTRS1996

Flight Dynamics Mission Support and Quality Assurance Process

This paper summarizes the method of the Computer Sciences Corporation Flight Dynamics Operation (FDO) quality assurance approach to support the National Aeronautics and Space Administration Goddard Space Flight Center Flight Dynamics Support Branch. Historically, a strong need has existed for developing systematic quality assurance using methods that account for the unique nature and environment of satellite Flight Dynamics mission support. Over the past few years FDO has developed and implemented proactive quality assurance processes applied to each of the six phases of the Flight Dynamics mission support life cycle: systems and operations concept, system requirements and specifications, software development support, operations planing and training, launch support, and on-orbit mission operations. Rather than performing quality assurance as a final step after work is completed, quality assurance has been built in as work progresses in the form of process assurance. Process assurance activities occur throughout the Flight Dynamics mission support life cycle. The FDO Product Assurance Office developed process checklists for prephase process reviews, mission team orientations, in-progress reviews, and end-of-phase audits. This paper will outline the evolving history of FDO quality assurance approaches, discuss the tailoring of Computer Science Corporations's process assurance cycle procedures, describe some of the quality assurance approaches that have been or are being developed, and present some of the successful results.

Oh, InHwan↗
NASA NTRS2013

Conceptual Design of a Hypervelocity Asteroid Intercept Vehicle (HAIV) Flight Validation Mission

In this paper we present a detailed overview of the MDL study results and subsequent advances in the design of GNC algorithms for accurate terminal guidance during hypervelocity NEO intercept. The MDL study produced a conceptual con guration of the two-body HAIV and its subsystems; a mission scenario and trajectory design for a notional flight validation mission to a selected candidate target NEO; GNC results regarding the ability of the HAIV to reliably intercept small (50 m) NEOs at hypervelocity (typically greater than 10 km/s); candidate launch vehicle selection; a notional operations concept and cost estimate for the flight validation mission; and a list of topics to address during the remainder of our NIAC Phase II study.

Barbee, Brent W.↗
NASA NTRS2012

Landsat Data Continuity Mission (LDCM) Flight Dynamics System (FDS)

The Landsat Data Continuity Mission (LDCM) will be launched in January 2013 to continue the legacy of Landsat land imagery collection that has been on-going for the past 40 years. While the overall mission and science goals are designed to produce the SAME data over the years, the ground systems designed to support the mission objectives have evolved immensely. The LDCM Flight Dynamics System (FDS) currently being tested and deployed for operations is highly automated and well integrated with the other ground system elements. The FDS encompasses the full suite of flight dynamics functional areas, including orbit and attitude determination and prediction, orbit and attitude maneuver planning and execution, and planning product generation. The integration of the orbit, attitude, maneuver, and products functions allows a very smooth flow for daily operations support with minimal input needed from the operator. The system also provides a valuable real-time component that monitors the on-board orbit and attitude during every ground contact and will autonomously alert the Flight Operations Team (FOT) personnel when any violations are found. This paper provides an overview of the LDCM Flight Dynamics System and a detailed description of how it is used to support space operations. For the first time on a Goddard Space Flight Center (GSFC)-managed mission, the ground attitude and orbits systems are fully integrated into a cohesive package. The executive engine of the FDS permits three levels of automation: low, medium, and high. The high-level, which will be the standard mode for LDCM, represents nearly lights-out operations. The paper provides an in-depth look at these processes within the FDS in support of LDCM in all mission phases.

Good, Susan M.↗
NASA NTRS1993

Mission Operations and Command Assurance: Flight Operations Quality Improvements

Flight mission operations systems place human operators in demanding, high risk environments. The objective of Mission Operations and Command Assurance (MO&CA) is to help improve the operational reliability of flight projects by reducing error -- Pareto Analysis shows that the human is the largest error category. MO&CA is a system level task reporting to project flight management and JPL Systems Assurance Division. MO&CA provides direct transfer of knowledge, continuous process improvement, and communication facilitation.

mission↗
NASA NTRS2018

Preparing to Assure Mission Success

Space flight missions are inherently risky. The mission operations assurance discipline grew out of strategies to control error and evolved into what today is an independent technical authority dedicated to achieving mission success. After the Mars Climate Orbiter loss, NASA made a set of recommendations for missions. Two of those recommendations led to the creation of today’s Mission Operations Assurance Manager role: (1) require an independent Mission Assurance representative during the operational phase of every flight project, and (2) require all flight projects to report and track post-launch anomalies. Since then, the MOAM role has been continually refined by lessons learned from its practice on more than 20 concurrent missions. The MOAM role requires significant operations experience as well as an additional set of skills. In the interests of developing a cadre of potential MOAMs, the MOAM training program was developed. It is a 14-unit set of presentations/discussions covering the 11 categories of MOAM tasks. It is offered to new MOAMs and interested systems engineers with an eye to preparing both types of personnel for present and future assignments, as well as building relationships among personnel of different organizations. MOAM training sessions include presentations on the various tools and processes employed by MOAMs, interspersed with mindset lessons illustrated via “war story” discussions of previous missions.

Bryant, Larry↗
NASA NTRS2012

JPL Innovation Foundry

Space science missions are increasingly challenged today: in ambition, by increasingly sophisticated hypotheses tested; in development, by the increasing complexity of advanced technologies; in budgeting, by the decline of flagship-class mission opportunities; in management, by expectations for breakthrough science despite a risk-averse programmatic climate; and in planning, by increasing competition for scarce resources. How are the space-science missions of tomorrow being formulated? The paper describes the JPL Innovation Foundry, created in 2011, to respond to this evolving context. The Foundry integrates methods, tools, and experts that span the mission concept lifecycle. Grounded in JPL's heritage of missions, flight instruments, mission proposals, and concept innovation, the Foundry seeks to provide continuity of support and cost-effective, on-call access to the right domain experts at the right time, as science definition teams and Principal Investigators mature mission ideas from "cocktail napkin" to PDR. The Foundry blends JPL capabilities in proposal development and concurrent engineering, including Team X, with new approaches for open-ended concept exploration in earlier, cost-constrained phases, and with ongoing research and technology projects. It applies complexity and cost models, projectformulation lessons learned, and strategy analyses appropriate to each level of concept maturity. The Foundry is organizationally integrated with JPL formulation program offices; staffed by JPL's line organizations for engineering, science, and costing; and overseen by senior Laboratory leaders to assure experienced coordination and review. Incubation of each concept is tailored depending on its maturity and proposal history, and its highest leverage modeling and analysis needs.

mission development↗
NASA NTRS2014

Implementation Options for the PROPEL Electrodynamic Tether Demonstration Mission

The PROPEL flight mission concept will demonstrate the safe use of an electrodynamic tether for generating thrust. PROPEL is being designed to be a versatile electrodynamic-tether system for multiple end users and to be flexible with respect to platform. As such, several implementation options are being explored, including a comprehensive mission design for PROPEL with a mission duration of six months; a space demonstration mission concept design with configuration of a pair of tethered satellites, one of which is the Japanese H-II Transfer Vehicle; and an ESPA-based system. We report here on these possible implementation options for PROPEL. electrodynamic tether; PROPEL demonstration mission; propellantless propulsion

Bilen, Sven G.↗
NASA NTRS2020

Blackbird: Object-Oriented Planning, Simulation, and Sequencing Framework Used by Multiple Missions

Every JPL flight mission relies on activity planningand sequence generation software to perform operations. Mostsuch tools in use at JPL and elsewhere use attribute-basedschemas or domain-specific languages (DSLs) to defineactivities. This reliance poses user training, softwaremaintenance, performance, and other challenges. To solve thisproblem for future missions, a new software called Blackbirdwas developed which allows engineers to specify behavior instandard Java. The new code base has over an order ofmagnitude fewer lines of code than other JPL planningsoftware, since no DSL or schema interpreter is needed. Theuse of Java for defining activities also allows mission adaptersto debug their code in an integrated development environment,seamlessly call external libraries, and set up truly multimissionmodels. These efficiency gains have significantlyreduced the amount of development effort required to supportthe software. This paper discusses Blackbird’s design,principles, and use cases.

Rothstein-Dowden, Ansel↗
NASA NTRS2020

Blackbird: Object-Oriented Planning, Simulation, and Sequencing Framework Used by Multiple Missions

Every JPL flight mission relies on activity planning and sequence generation software to perform operations. Most such tools in use at JPL and elsewhere use attribute-based schemas or domain-specific languages (DSLs) to define activities. This reliance poses user training, software maintenance, performance, and other challenges. To solve this problem for future missions, a new software called Blackbird was developed which allows engineers to specify behavior in standard Java. The new code base has over an order of magnitude fewer lines of code than other JPL planning software, since no DSL or schema interpreter is needed. The use of Java for defining activities also allows mission adapters to debug their code in an integrated development environment, seamlessly call external libraries, and set up truly multimission models. These efficiency gains have significantly reduced the amount of development effort required to support the software. This paper discusses Blackbird’s design, principles, and use cases.

Lawler, Christopher↗
NASA NTRS2013

Conceptual Design of a Flight Validation Mission for a Hypervelocity Asteroid Intercept Vehicle

Near-Earth Objects (NEOs) are asteroids and comets whose orbits approach or cross Earth s orbit. NEOs have collided with our planet in the past, sometimes to devastating effect, and continue to do so today. Collisions with NEOs large enough to do significant damage to the ground are fortunately infrequent, but such events can occur at any time and we therefore need to develop and validate the techniques and technologies necessary to prevent the Earth impact of an incoming NEO. In this paper we provide background on the hazard posed to Earth by NEOs and present the results of a recent study performed by the NASA/Goddard Space Flight Center s Mission Design Lab (MDL) in collaboration with Iowa State University s Asteroid Deflection Research Center (ADRC) to design a flight validation mission for a Hypervelocity Asteroid Intercept Vehicle (HAIV) as part of a Phase 2 NASA Innovative Advanced Concepts (NIAC) research project. The HAIV is a two-body vehicle consisting of a leading kinetic impactor and trailing follower carrying a Nuclear Explosive Device (NED) payload. The HAIV detonates the NED inside the crater in the NEO s surface created by the lead kinetic impactor portion of the vehicle, effecting a powerful subsurface detonation to disrupt the NEO. For the flight validation mission, only a simple mass proxy for the NED is carried in the HAIV. Ongoing and future research topics are discussed following the presentation of the detailed flight validation mission design results produced in the MDL.

Barbee, Brent W.↗
NASA NTRS2000

Shuttle Radar Topography Mission (SRTM) Flight System Design and Operations Overview

This paper provides an overview of the Shuttle Radar Topography Mission (SRTM), with emphasis on flight system implementation and mission operations from systems engineering perspective. Successfully flown in February, 2000, the SRTM's primary payload consists of several subsystems to form the first spaceborne dual-frequency (C-band and X-band) fixed baseline interferometric synthetic aperture radar (InSAR) system, with the mission objective to acquire data sets over 80% of Earth's landmass for height reconstruction. The paper provides system architecture, unique design features, engineering budgets, design verification, in-flight checkout and data acquisition of the SRTM payload, in particular for the C-band system. Mission operation and post-mission data processing activities are also presented. The complexity of the SRTM as a system, the ambitious mission objective, the demanding requirements and the high interdependency between multi-disciplined subsystems posed many challenges. The engineering experience and the insight thus gained have important implications for future spaceborne interferometric SAR mission design and implementation.

Shen, Yuhsyen↗