Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “lifecycle”

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 397 records · Page 22
All sourcesNASA NTRSDOE OSTI
NASA NTRS2015

The OSIRIS-REx Asteroid Sample Return Mission Operations Design

OSIRIS-REx is an acronym that captures the scientific objectives: Origins, Spectral Interpretation, Resource Identification, and Security-Regolith Explorer. OSIRIS-REx will thoroughly characterize near-Earth asteroid Bennu (Previously known as 1019551999 RQ36). The OSIRIS-REx Asteroid Sample Return Mission delivers its science using five instruments and radio science along with the Touch-And-Go Sample Acquisition Mechanism (TAGSAM). All of the instruments and data analysis techniques have direct heritage from flown planetary missions. The OSIRIS-REx mission employs a methodical, phased approach to ensure success in meeting the mission's science requirements. OSIRIS-REx launches in September 2016, with a backup launch period occurring one year later. Sampling occurs in 2019. The departure burn from Bennu occurs in March 2021. On September 24, 2023, the Sample Return Capsule (SRC) lands at the Utah Test and Training Range (UTTR). Stardust heritage procedures are followed to transport the SRC to Johnson Space Center, where the samples are removed and delivered to the OSIRIS-REx curation facility. After a six-month preliminary examination period the mission will produce a catalog of the returned sample, allowing the worldwide community to request samples for detailed analysis. Traveling and returning a sample from an Asteroid that has not been explored before requires unique operations consideration. The Design Reference Mission (DRM) ties together spacecraft, instrument and operations scenarios. Asteroid Touch and Go (TAG) has various options varying from ground only to fully automated (natural feature tracking). Spacecraft constraints such as thermo and high gain antenna pointing impact the timeline. The mission is sensitive to navigation errors, so a late command update has been implemented. The project implemented lessons learned from other "small body" missions. The key lesson learned was 'expect the unexpected' and implement planning tools early in the lifecycle. This paper summarizes the ground and spacecraft design as presented at OSIRIS-REx Critical Design Review(CDR) held April 2014.

mission operations↗
NASA NTRS2015

Test and Inspection Requirements for Frangible Joints Used in Human-Rated Spacecraft Applications

The purpose of this document is to define a series of test and inspection requirements for a specific type of frangible joint assembly used in human-rated spacecraft applications. It is intended to be an enhancement to the Commercial Crew Program JSC 62809D Human Rated Spacecraft Pyrotechnic Specification and lists very specific tests and inspections with accompanying tables. This document does not eliminate any of the requirements stated in JSC 62809D. Many of the test and inspections in this document are standard operating procedure for pyrotechnics suppliers. This document provides detail on the individual items to avoid ambiguity. In particular, this document details the test and inspection requirements for offset notch style frangible joints with aluminum machined plates. It is expected that a user would tailor the contents of this document for their particular vehicle application and provide a certifying organization with rationale for such tailoring. Tailoring to the requirements of this document requires approval of the certifying organization (e.g. NASA for a NASA human spaceflight program). The FJ must perform in accordance with design specifications after subjection to all environments it would encounter in its lifecycle. This document does not cover all possible environments that may exist in unique applications and a user may determine that additional tests are necessary. The user must develop written inspection and test procedures with detailed acceptance criteria.

Sirri Oguz↗
NASA NTRS2014

Design and Functional Validation of a Mechanism for Dual-Spinning CubeSats

The mission of the Micro-sized Microwave Atmospheric Satellite (MicroMAS) is to collect useful atmospheric images using a miniature passive microwave radiometer payload hosted on a low-cost CubeSat platform. In order to collect this data, the microwave radiometer payload must rotate to scan the ground-track perpendicular to the satellite's direction of travel. A custom motor assembly was developed to facilitate the rotation of the payload while allowing the spacecraft bus to remained fixed in the local-vertical, local-horizontal (LVLH) frame for increased pointing accuracy. This paper describes the mechanism used to enable this dual-spinning operation for CubeSats, and the lessons learned during the design, fabrication, integration, and testing phases of the mechanism's development lifecycle.

Peters, Eric↗
NASA NTRS2013

Model-based Systems Engineering: Creation and Implementation of Model Validation Rules for MOS 2.0

Model-based Systems Engineering (MBSE) is an emerging modeling application that is used to enhance the system development process. MBSE allows for the centralization of project and system information that would otherwise be stored in extraneous locations, yielding better communication, expedited document generation and increased knowledge capture. Based on MBSE concepts and the employment of the Systems Modeling Language (SysML), extremely large and complex systems can be modeled from conceptual design through all system lifecycles. The Operations Revitalization Initiative (OpsRev) seeks to leverage MBSE to modernize the aging Advanced Multi-Mission Operations Systems (AMMOS) into the Mission Operations System 2.0 (MOS 2.0). The MOS 2.0 will be delivered in a series of conceptual and design models and documents built using the modeling tool MagicDraw. To ensure model completeness and cohesiveness, it is imperative that the MOS 2.0 models adhere to the specifications, patterns and profiles of the Mission Service Architecture Framework, thus leading to the use of validation rules. This paper outlines the process by which validation rules are identified, designed, implemented and tested. Ultimately, these rules provide the ability to maintain model correctness and synchronization in a simple, quick and effective manner, thus allowing the continuation of project and system progress.

Model-based Systems Engineering (MBSE)↗
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 NTRS2011

Orbit Determination and Navigation Software Testing for the Mars Reconnaissance Orbiter

During the extended science phase of the Mars Reconnaissance Orbiter's lifecycle, the operational duties pertaining to navigation primarily involve orbit determination. The orbit determination process utilizes radiometric tracking data and is used for the prediction and reconstruction of MRO's trajectories. Predictions are done twice per week for ephemeris updates on-board the spacecraft and for planning purposes. Orbit Trim Maneuvers (OTM-s) are also designed using the predicted trajectory. Reconstructions, which incorporate a batch estimator, provide precise information about the spacecraft state to be synchronized with scientific measurements. These tasks were conducted regularly to validate the results obtained by the MRO Navigation Team. Additionally, the team is in the process of converting to newer versions of the navigation software and operating system. The capability to model multiple densities in the Martian atmosphere is also being implemented. However, testing outputs among these different configurations was necessary to ensure compliance to a satisfactory degree.

Deep Space Network↗
NASA NTRS2008

An Improved Wavefront Control Algorithm for Large Space Telescopes

Wavefront sensing and control is required throughout the mission lifecycle of large space telescopes such as James Webb Space Telescope (JWST). When an optic of such a telescope is controlled with both surface-deforming and rigid-body actuators, the sensitivity-matrix obtained from the exit pupil wavefront vector divided by the corresponding actuator command value can sometimes become singular due to difference in actuator types and in actuator command values. In this paper, we propose a simple approach for preventing a sensitivity-matrix from singularity. We also introduce a new "minimum-wavefront and optimal control compensator". It uses an optimal control gain matrix obtained by feeding back the actuator commands along with the measured or estimated wavefront phase information to the estimator, thus eliminating the actuator modes that are not observable in the wavefront sensing process.

adaptive optics↗
NASA NTRS2012

Principles to Products: Toward Realizing MOS 2.0

This is a report on the Operations Revitalization Initiative, part of the ongoing NASA-funded Advanced Multi-Mission Operations Systems (AMMOS) program. We are implementing products that significantly improve efficiency and effectiveness of Mission Operations Systems (MOS) for deep-space missions. We take a multi-mission approach, in keeping with our organization's charter to "provide multi-mission tools and services that enable mission customers to operate at a lower total cost to NASA." Focusing first on architectural fundamentals of the MOS, we review the effort's progress. In particular, we note the use of stakeholder interactions and consideration of past lessons learned to motivate a set of Principles that guide the evolution of the AMMOS. Thus guided, we have created essential patterns and connections (detailed in companion papers) that are explicitly modeled and support elaboration at multiple levels of detail (system, sub-system, element...) throughout a MOS. This architecture is realized in design and implementation products that provide lifecycle support to a Mission at the system and subsystem level. The products include adaptable multi-mission engineering documentation that describes essentials such as operational concepts and scenarios, requirements, interfaces and agreements, information models, and mission operations processes. Because we have adopted a model-based system engineering method, these documents and their contents are meaningfully related to one another and to the system model. This means they are both more rigorous and reusable (from mission to mission) than standard system engineering products. The use of models also enables detailed, early (e.g., formulation phase) insight into the impact of changes (e.g., to interfaces or to software) that is rigorous and complete, allowing better decisions on cost or technical trades. Finally, our work provides clear and rigorous specification of operations needs to software developers, further enabling significant gains in productivity.

AMMOS↗
NASA NTRS2010

Identification and Classification of Common Risks in Space Science Missions

Due to the highly constrained schedules and budgets that NASA missions must contend with, the identification and management of cost, schedule and risks in the earliest stages of the lifecycle is critical. At the Jet Propulsion Laboratory (JPL) it is the concurrent engineering teams that first address these items in a systematic manner. Foremost of these concurrent engineering teams is Team X. Started in 1995, Team X has carried out over 1000 studies, dramatically reducing the time and cost involved, and has been the model for other concurrent engineering teams both within NASA and throughout the larger aerospace community. The ability to do integrated risk identification and assessment was first introduced into Team X in 2001. Since that time the mission risks identified in each study have been kept in a database. In this paper we will describe how the Team X risk process is evolving highlighting the strengths and weaknesses of the different approaches. The paper will especially focus on the identification and classification of common risks that have arisen during Team X studies of space based science missions.

Risk Identification↗
NASA NTRS2008

Automated and Adaptive Mission Planning for Orbital Express

The Orbital Express space mission was a Defense Advanced Research Projects Agency (DARPA) lead demonstration of on-orbit satellite servicing scenarios, autonomous rendezvous, fluid transfers of hydrazine propellant, and robotic arm transfers of Orbital Replacement Unit (ORU) components. Boeing's Autonomous Space Transport Robotic Operations (ASTRO) vehicle provided the servicing to the Ball Aerospace's Next Generation Serviceable Satellite (NextSat) client. For communication opportunities, operations used the high-bandwidth ground-based Air Force Satellite Control Network (AFSCN) along with the relatively low-bandwidth GEO-Synchronous space-borne Tracking and Data Relay Satellite System (TDRSS) network. Mission operations were conducted out of the RDT&E Support Complex (RSC) at the Kirtland Air Force Base in New Mexico. All mission objectives were met successfully: The first of several autonomous rendezvous was demonstrated on May 5, 2007; autonomous free-flyer capture was demonstrated on June 22, 2007; the fluid and ORU transfers throughout the mission were successful. Planning operations for the mission were conducted by a team of personnel including Flight Directors, who were responsible for verifying the steps and contacts within the procedures, the Rendezvous Planners who would compute the locations and visibilities of the spacecraft, the Scenario Resource Planners (SRPs), who were concerned with assignment of communications windows, monitoring of resources, and sending commands to the ASTRO spacecraft, and the Mission planners who would interface with the real-time operations environment, process planning products and coordinate activities with the SRP. The SRP position was staffed by JPL personnel who used the Automated Scheduling and Planning ENvironment (ASPEN) to model and enforce mission and satellite constraints. The lifecycle of a plan began three weeks outside its execution on-board. During the planning timeframe, many aspects could change the plan, causing the need for re-planning. These variable factors, ranging from shifting contact times to ground-station closures and required maintenance times, are discussed along with the flexibility of the ASPEN tool to accommodate changes to procedures and the daily or long-range plan, which contributed to the success of the mission. This paper will present an introduction to ASPEN, a more in-depth discussion on its use on the Orbital Express mission, and other relative work. A description of ground operations after the SRP deliveries were made is included, and we briefly discuss lessons learned from the planning perspective and future work.

scheduling↗
NASA NTRS2009

Probabilistic Risk Assessment for Decision Making During Spacecraft Operations

Decisions made during the operational phase of a space mission often have significant and immediate consequences. Without the explicit consideration of the risks involved and their representation in a solid model, it is very likely that these risks are not considered systematically in trade studies. Wrong decisions during the operational phase of a space mission can lead to immediate system failure whereas correct decisions can help recover the system even from faulty conditions. A problem of special interest is the determination of the system fault protection strategies upon the occurrence of faults within the system. Decisions regarding the fault protection strategy also heavily rely on a correct understanding of the state of the system and an integrated risk model that represents the various possible scenarios and their respective likelihoods. Probabilistic Risk Assessment (PRA) modeling is applicable to the full lifecycle of a space mission project, from concept development to preliminary design, detailed design, development and operations. The benefits and utilities of the model, however, depend on the phase of the mission for which it is used. This is because of the difference in the key strategic decisions that support each mission phase. The focus of this paper is on describing the particular methods used for PRA modeling during the operational phase of a spacecraft by gleaning insight from recently conducted case studies on two operational Mars orbiters. During operations, the key decisions relate to the commands sent to the spacecraft for any kind of diagnostics, anomaly resolution, trajectory changes, or planning. Often, faults and failures occur in the parts of the spacecraft but are contained or mitigated before they can cause serious damage. The failure behavior of the system during operations provides valuable data for updating and adjusting the related PRA models that are built primarily based on historical failure data. The PRA models, in turn, provide insight into the effect of various faults or failures on the risk and failure drivers of the system and the likelihood of possible end case scenarios, thereby facilitating the decision making process during operations. This paper describes the process of adjusting PRA models based on observed spacecraft data, on one hand, and utilizing the models for insight into the future system behavior on the other hand. While PRA models are typically used as a decision aid during the design phase of a space mission, we advocate adjusting them based on the observed behavior of the spacecraft and utilizing them for decision support during the operations phase.

dynamic fault trees↗
NASA NTRS2015

Play Nice Across Time Space

Lecture is an overview of Simulation technologies, methods and practices, as applied to current and past NASA programs. Focus is on sharing experience and the overall benefits to programs and projects of having appropriate simulation and analysis capabilities available at the correct point in a system lifecycle.

system engineering↗
NASA NTRS2015

Model-Based Systems Engineering in Concurrent Engineering Centers

Concurrent Engineering Centers (CECs) are specialized facilities with a goal of generating and maturing engineering designs by enabling rapid design iterations. This is accomplished by co-locating a team of experts (either physically or virtually) in a room with a focused design goal and a limited timeline of a week or less. The systems engineer uses a model of the system to capture the relevant interfaces and manage the overall architecture. A single model that integrates other design information and modeling allows the entire team to visualize the concurrent activity and identify conflicts more efficiently, potentially resulting in a systems model that will continue to be used throughout the project lifecycle. Performing systems engineering using such a system model is the definition of model-based systems engineering (MBSE); therefore, CECs evolving their approach to incorporate advances in MBSE are more successful in reducing time and cost needed to meet study goals. This paper surveys space mission CECs that are in the middle of this evolution, and the authors share their experiences in order to promote discussion within the community.

systems engineering↗
NASA NTRS2015

[Fall 2015 Abstract by Stephanie Scharf]

This Fall I worked on two different projects that culminated into a redesign of the spacesuit LLB (long life battery). I also did some work on the PLSS (personal life support system) battery with EC. My first project was redlining the work instruction for completing DPAs (destructive physical analysis) on battery cells in the Branch. The purpose of this document is to create a standard process and ensure that the data is collected in the same way, no matter who carries out the analysis. I observed three DPAs, conducted one with help, and conducted two on my own, all while taking notes on the procedure. These notes were used to write the final work instruction, which will become the Branch standard. My second project continued the work of the Summer co-op before me. I tested aluminum heat sinks for their ability to provide good thermal conduction and structural support during a thermal runaway event. The heat sinks had been designed by the previous Summer co-op, but there was not much time for testing before he left. We thus ran tests with a heater on the bottom of a trigger cell to try to drive thermal runaway and ensure that it will not propagate to adjacent cells. We also ran heat-to-vent tests in an oven to see if the assembly provided structural support and prevented sidewall rupture during thermal runaway. These tests were carried out at ESTA (Energy Systems Test Area) and are providing very promising results, indicating that safe, high performing (>180 Wh/kg) designs are possible. My main project was a redesign of the LLB (Lightweight Lithium Battery). Another summer intern had done some testing and concluded that there was no simple fix to mitigate thermal runaway propagation hazards in the existing design. The only option was a clean sheet redesign of the battery. I was given a volume and ideal energy density, and the rest of the design was up to me. First, I created new heat sink banks in CREO, using the information gathered in the metal heat sink tests from the summer intern. After this, I made capture plates to hold the cells in place, and I worked on nickel bussings for the electrical connections between the cells. Finally, I designed the test box enclosure that included sections for flame arresting materials. The battery brick design, which is the heart of the battery, promises to become the first for a manned spacecraft application to achieve > 180 Wh/kg. My work in redlining the DPA work instructions will also be used in selecting the cells for the battery. We had a few options for cells that would provide the necessary power output and needed to make a choice. We repeatedly charged and discharged cells for around a month until they went through 100 lifecycles. The plan was to compare the DPA results on fresh and cycled cells from each manufacturer to see if cycling introduces any differences. After the complete LLB design was approved, the parts were ordered and testing should begin the first week of December. Cutting open a cell for DPA After photo from oven heat-to-vent test

Scharf, Stephanie↗
NASA NTRS2015

Generalized Nanosatellite Avionics Testbed Lab

The Generalized Nanosatellite Avionics Testbed (G-NAT) lab at NASA Ames Research Center provides a flexible, easily accessible platform for developing hardware and software for advanced small spacecraft. A collaboration between the Mission Design Division and the Intelligent Systems Division, the objective of the lab is to provide testing data and general test protocols for advanced sensors, actuators, and processors for CubeSat-class spacecraft. By developing test schemes for advanced components outside of the standard mission lifecycle, the lab is able to help reduce the risk carried by advanced nanosatellite or CubeSat missions. Such missions are often allocated very little time for testing, and too often the test facilities must be custom-built for the needs of the mission at hand. The G-NAT lab helps to eliminate these problems by providing an existing suite of testbeds that combines easily accessible, commercial-offthe- shelf (COTS) processors with a collection of existing sensors and actuators.

Testing data and general test protocols↗
NASA NTRS2015

Assuring NASA's Safety and Mission Critical Software

What is IV&V? Independent Verification and Validation (IV&V) is an objective examination of safety and mission critical software processes and products. Independence: 3 Key parameters: Technical Independence; Managerial Independence; Financial Independence. NASA IV&V perspectives: Will the system's software: Do what it is supposed to do?; Not do what it is not supposed to do?; Respond as expected under adverse conditions?. Systems Engineering: Determines if the right system has been built and that it has been built correctly. IV&V Technical Approaches: Aligned with IEEE 1012; Captured in a Catalog of Methods; Spans the full project lifecycle. IV&V Assurance Strategy: The IV&V Project's strategy for providing mission assurance; Assurance Strategy is driven by the specific needs of an individual project; Implemented via an Assurance Design; Communicated via Assurance Statements.

Validation↗
NASA NTRS2015

[Redesign of the Spacesuit Long Life Battery and the Personal Life Support System Battery]

This fall I was working on two different projects that culminated into a redesign of the spacesuit LLB (long life battery). I also did some work on the PLSS (personal life support system) battery with EC. My first project was redlining the work instruction for completing DPAs (destructive physical analysis) on battery cells in the department. The purpose of this document is to create a standard process and ensure that the data in the same way no matter who carries out the analysis. I observed three DPAs, conducted one with help, and conducted two on my own all while taking notes on the procedure. These notes were used to write the final work instruction that will become is the department standard. My second project continued the work of the summer co-op before me. I was testing aluminum heat sinks for their ability to provide good thermal conduction and structural support during a thermal runaway event. The heat sinks were designed by the summer intern but there was not much time for testing before he left. We ran tests with a heater on the bottom of a trigger cell to try to drive thermal runaway and ensure that it will not propagate to adjacent cells. We also ran heat-to-vent tests in an oven to see if the assembly provided structural support and prevented sidewall rupture during thermal runaway. These tests were carried out at ESTA (energy systems test area) and are providing very promising results that safe, high performing (greater than 180 Wh/kg) designs are possible. My main project was a redesign of the LLB battery. Another summer intern did some testing and concluded that there was no simple fix to mitigate thermal runaway propagation hazards in the current design. The only option was a clean sheet redesign of the battery. I was given a volume and ideal energy density and the rest of the design was up to me. First, I created new heat sink banks in Creo using the information gathered in the metal heat sink tests from the summer intern. After this, I made capture plates to hold the cells in place and I worked on nickel bussings for the electrical connections between the cells. Finally, I designed the test box enclosure that included sections for flame arresting materials. The battery brick design, which is the heart of the battery, promises to become the first for a manned spacecraft application to achieve greater than 180 Wh/kg. My work in redlining the DPA work instructions will also be used in selecting the cells for the battery. We had a few options of cells that would provide the necessary power output and needed to make a choice. We repeatedly charged and discharged cells for around a month until they went through 100 lifecycles. The plan is to compare the DPA results on fresh and cycled cells from each manufacturer to see if cycling introduces any differences. After the complete LLB design was approved, the parts were ordered and testing should begin the first week of December. Some of my side projects included working on the CAD data for the PLSS with EC and attending the NASA Aerospace Battery Workshop in Huntsville. I was also a member of the Tours and Lectures Committee for the USRA and Pathways interns. I coordinated Apollo Evening and was on the committee for touring KSC and seeing an Atlas 5 launch. I really enjoyed my time at JSC and I would like to continue working for NASA or another aerospace company in the future. I have worked other internships prior to this, but I think the heavy research and development focus is the best fit for me. I originally thought I would need to go to grad school to work in an environment like this, but I now see it is possible with a bachelor’s degree and hard work. I would like to go into the workforce and maybe continue my education with night classes.

Scharf, Stephanie↗
NASA NTRS2014

Sensitivity of Cirrus Properties to Ice Nuclei Abundance

The relative importance of heterogeneous and homogeneous ice nucleation for cirrus formation remains an active area of debate in the cloud physics community. From a theoretical perspective, a number of modeling studies have investigated the sensitivity of ice number concentration to the nucleation mechanism and the abundance of ice nuclei. However, these studies typically only addressed ice concentration immediately after ice nucleation. Recent modeling work has shown that the high ice concentrations produced by homogeneous freezing may not persist very long, which is consistent with the low frequency of occurrence of high ice concentrations indicated by cirrus measurements. Here, I use idealized simulations to investigate the impact of ice nucleation mechanism and ice nuclei abundance on the full lifecycle of cirrus clouds. The primary modeling framework used includes different modes of ice nucleation, deposition growth/sublimation, aggregation, sedimentation, and radiation. A limited number of cloud-resolving simulations that treat radiation/dynamics interactions will also been presented. I will show that for typical synoptic situations with mesoscale waves present, the time-averaged cirrus ice crystal size distributions and bulk cloud properties are less sensitive to ice nucleation processes than might be expected from the earlier simple ice nucleation calculations. I will evaluate the magnitude of the ice nuclei impact on cirrus for a range of temperatures and mesoscale wave specifications, and I will discuss the implications for cirrus aerosol indirect effects in general.

Nuclei↗