Engineering Papers⌕ Search

SEARCH · Engineering Papers

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.

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

At least 1,081 records · Page 60

Structural Acoustic Response of a Shape Memory Alloy Hybrid Composite Panel (Lessons Learned)

This study presents results from an effort to fabricate a shape memory alloy hybrid composite (SMAHC) panel specimen and test the structure for dynamic response and noise transmission characteristics under the action of thermal and random acoustic loads. A method for fabricating a SMAHC laminate with bi-directional SMA reinforcement is described. Glass-epoxy unidirectional prepreg tape and Nitinol ribbon comprise the material system. Thermal activation of the Nitinol actuators was achieved through resistive heating. The experimental hardware required for mechanical support of the panel/actuators and for establishing convenient electrical connectivity to the actuators is presented. Other experimental apparatus necessary for controlling the panel temperature and acquiring structural acoustic data are also described. Deficiency in the thermal control system was discovered in the process of performing the elevated temperature tests. Discussion of the experimental results focuses on determining the causes for the deficiency and establishing means for rectifying the problem.

Turner, Travis L.↗

Perl Tools for Automating Satellite Ground Systems

The freeware scripting language Pert offers many opportunities for automating satellite ground systems for new satellites as well as older, in situ systems. This paper describes a toolkit that has evolved from of the experiences gained by using Pert to automate the ground system for the Compton Gamma Ray Observatory (CGRO) and for automating some of the elements in the Earth Observing System Data and Operations System (EDOS) ground system at Goddard Space Flight Center (GSFC). CGRO is an older ground system that was forced to automate because of fund cuts. Three 8 hour shifts were cut back to one 8 hour shift, 7 days per week. EDOS supports a new mission called Terra, launched December 1999 that requires distribution and tracking of mission-critical reports throughout the world. Both of these ground systems use Pert scripts to process data and display it on the Internet as well as scripts to coordinate many of the other systems that make these ground systems work as a coherent whole. Another task called Automated Multimodal Trend Analysis System (AMTAS) is looking at technology for isolation and recovery of spacecraft problems. This effort has led to prototypes that seek to evaluate various tools and technology that meet at least some of the AMTAS goals. The tools, experiences, and lessons learned by implementing these systems are described here.

McLean, David↗

The Collection, Usage, and Preliminary Examination of the Apollo Sample Suite: Lessons for Artemis

Apollo Sample Collection and Usage: From 1969 to 1972 there were six Apollo missions to the surface of the Moon during which the astronauts collected 382 kg of rock and regolith (~2200 samples). The samples collected fall into these general categories: rocks (~66% by mass), rake samples (~4%), bulk regolith (~24%), and specialty regolith (deep drill cores, drive tubes, sealed bulk regolith) samples (~6%). In each category there are a variety of different subtypes available for study, e.g., among the bulk regolith samples there are also skim, trench, and (partially) shaded regolith samples each sampling unique types or depths of regolith. This variety of subsamples has enabled a multitude of different studies over the past 55 years (>3400 individual requests). We are still averaging ~50 unique requests and have allocated >500 individual Apollo samples annually for the past 10 years (2020 excepted). Looking at the 4,675 non-ANGSA (Apollo Next Generation Sample Analysis) samples allocated over the past 10 years, the proportions of allocated samples do not precisely align with the abundance (by mass) of those samples withing the collection: Rock (69.4 %); Rake (10.8 %); Bulk Regolith (15.5 %); Drive Tube (3.3 %); Core/Specialty (1.0 %). Apollo Preliminary Examination (PE): The PE process differs significantly for the various sample types enumerated above; we focus on regolith and rock samples here. During the Apollo mission era, the PE process evolved over the course of the missions; below is what was done for the Apollo 17 mission. For regolith samples, the PE process was: (1) documented bags containing regolith are opened, photographed, and described; (2) large rocks are removed and treated separately; (3) 25% to 33% of the bulk soil is scooped out, weighed, and stored in reserve; (4) the remaining sample is sieved to produce the size fractions <1, 1- 2, 2-4, and 4-10 mm, all of which are weighed. For rock samples, the process is: (1) removing rocks from the container(s) it came back from the Moon in; (2) rematching any materials that spalled off the rock to their original location; (3) numbering, weighing, and basic photographic documentation; (4) dusting with a gentle N2 gas jet; (5) Orthogonal photography; (6) detailed description of the textures and features of the rock; (7) rock modelling and measurement; (8) stereophotography; (9) determination of the orientation of the rock on the lunar surface. Drive tubes and deep drill cores were not characterized during PE beyond an initial weight and a sketch of the interior tube materials derived from 2D medical X-ray images. Catalogs: The ongoing utility of the Apollo samples is enabled by the robust cataloguing process for the samples [3-5], which allows the scientific community to accurately request samples uniquely suited to their proposed studies. A common misconception, however, is the amount of detail that goes into the initial catalog (e.g., [6]) for a collection from the preliminary examination (PE) period, versus what goes into the catalogs that come later in the life cycle of the samples from that mission (e.g., [7]). The only required data for a PE catalog is a weight, a basic photograph, and a description of the nature of the sample. Artemis PE: Over the past few years, the ongoing ANGSA project studied previously unopened Apollo 17 double drive tube samples 73001/2 [1], and a PE of the drive tubes was done. The PE took the existing core dissection process (developed during PE of Apollo cores in the 1970s, 1980s), and modernized it [7]. The main lesson from the ANGSA PE relative to future missions was that the physical work done during PE of lunar samples has not changed much over the past 5 decades. The use of “modern” technology during PE (e.g., XCT; multispectral analyses) resulted in an enhanced initial understanding of the 73001 and 73002 drive tubes, but greatly increased the time required. The lessons learned from recent astromaterial PEs (e.g., ANGSA and OREx) are important to consider when planning for Artemis, but the unique nature of the Artemis Campaign means many lessons learned from these mission will not be applicable. Given the time constraints (6 months) and likely number of samples that will be returned by Artemis (>200), the Artemis PE catalog will necessarily look much more like [4] than [6].

J Gross↗

User observations on information sharing (corporate knowledge and lessons learned)

The sharing of 'corporate knowledge' and lessons learned in the NASA aerospace community has been identified by Johnson Space Center survey participants as a desirable tool. The concept of the program is based on creating a user friendly information system that will allow engineers, scientists, and managers at all working levels to share their information and experiences with other users irrespective of location or organization. The survey addresses potential end uses for such a system and offers some guidance on the development of subsequent processes to ensure the integrity of the information shared. This system concept will promote sharing of information between NASA centers, between NASA and its contractors, between NASA and other government agencies, and perhaps between NASA and institutions of higher learning.

Montague, Ronald A.↗

A Glimpse from the Inside of a Space Suit: What Is It Really Like to Train for an EVA?

The beauty of the view from the office of a spacewalking astronaut gives the impression of simplicity, but few beyond the astronauts, and those who train them, know what it really takes to get there. Extravehicular Activity (EVA) training is an intense process that utilizes NASA's Neutral Buoyancy Laboratory (NBL) to develop a very specific skill set needed to safely construct and maintain the orbiting International Space Station. To qualify for flight assignments, astronauts must demonstrate the ability to work safely and efficiently in the physically demanding environment of the spacesuit, possess an acute ability to resolve unforeseen problems, and implement proper tool protocols to ensure no tools will be lost in space. Through the insights and the lessons learned by actual EVA astronauts and EVA instructors, this paper twill take you on a journey through an astronaut's earliest experiences working in the spacesuit. termed the Extravehicular Mobility Unit (EMU), in the underwater training environment of the NBL. This work details an actual Suit Qualification NBL training event, outlines the numerous challenges the astronauts face throughout their initial training, and the various ways they adapt their own abilities to overcome them. The goal of this paper is to give everyone a small glimpse into what it is really like to work in a spacesuit.

Gast, Matthew A.↗

Experiences in Applying Earth Observing Satellite Technology in SERVIR Regions with an Emphasis on Disasters: Successes, Lessons and Paths Forward

Earth observing satellites offer a unique perspective of our environment from the vantage point of space. Repeated measurements of the Earths subsystems such as the biosphere, atmosphere, lithosphere, hydrosphere, and of humans interactions with their environments, allow for a better understanding of Earth system processes, and they can provide input for decision making in areas of environmental management and disaster risk reduction. SERVIR is a joint initiative of the US National Aeronautics and Space Administration (NASA) and the US Agency for International Development (USAID) that began in 2005 and has been active in applying Earth observations for sustainable development in many regions around the world, recently the Lower Mekong and West Africa regions. This talk will highlight some successes achieved and lessons learned through SERVIR in Central America, Eastern Southern Africa, and the Hindu Kush-Himalaya region, focusing on disasters. We will also present opportunities for enhanced decision making with Earth observations and geospatial technologies in the Lower Mekong region.

SERVIR↗

Evolution of the JPSS Ground Project Calibration and Validation System

The Joint Polar Satellite System (JPSS) is the National Oceanic and Atmospheric Administrations (NOAA) next-generation operational Earth observation Program that acquires and distributes global environmental data from multiple polar-orbiting satellites. The JPSS Program plays a critical role to NOAAs mission to understand and predict changes in weather, climate, oceans, coasts, and space environments, which supports the Nation’s economy and protection of lives and property. The National Aerospace and Atmospheric Administration (NASA) is acquiring and implementing the JPSS, comprised of flight and ground systems on behalf of NOAA. The JPSS satellites are planned to fly in the afternoon orbit and will provide operational continuity of satellite-based observations and products for NOAA Polar-orbiting Operational Environmental Satellites (POES) and the Suomi National Polar-orbiting Partnership (SNPP) satellite. To support the JPSS Calibration and Validation (CalVal) node Government Resource for Algorithm Verification, Independent Test, and Evaluation (GRAVITE) services facilitate: Algorithm Integration and Checkout, Algorithm and Product Operational Tuning, Instrument Calibration, Product Validation, Algorithm Investigation, and Data Quality Support and Monitoring. GRAVITE is a mature, deployed system that currently supports the SNPP Mission and has been in operations since SNPP launch. This paper discusses the major re-architecture for Block 2.0 that incorporates SNPP lessons learned, architecture of the system, and demonstrates how GRAVITE has evolved as a system with increased performance. It is now a robust, stable, reliable, maintainable, scalable, and secure system that supports development, test, and production strings, replaces proprietary and custom software, uses open source software, and is compliant with NASA and NOAA standards.

Data Processing↗

Canonsburg, Pennsylvania, UMTRCA Title I Disposal Site 35 Years Postclosure (1985-2020) - 20288

The DOE Office of Legacy Management (LM) Canonsburg, Pennsylvania, Disposal Site is a former uranium ore-processing site located in the borough of Canonsburg and an important part of US history. For 46 years (1911-1957), the site processed ore, for vanadium, radium and then uranium. Soils and groundwater beneath the site were contaminated by the milling operations. The 15-hectare (37-acre) site is owned by the US government and managed by LM, which serves as the federal land manager and steward of cultural, historical, and natural resources at Cold War legacy sites that have been successfully cleaned up to remedial standards. In 1978 Congress directed DOE to remediate 22 inactive uranium-ore processing sites under the Uranium Mill Tailings Radiation Control Act (UMTRCA), in accordance with standards promulgated by the US Environmental Protection Agency in Title 40 CFR Part 192 (40 (CFR 192). Subpart B of 40 CFR 192 regulates the cleanup of contaminated groundwater at the processing sites. The radioactive materials were encapsulated in US Nuclear Regulatory Commission (NRC)-approved disposal cells, and the NRC general license for UMTRCA Title I sites is established in 10 CFR 40.27. Canonsburg was the first site to be remediated under UMTRCA. From 1983 to 1985, the Canonsburg site underwent cleanup under this US law that provides for the safe and environmentally sound disposal, long-term stabilization, and control of uranium mill tailings in a manner that minimizes or eliminates radiation health hazards to the public. The site is unique in that it is one of only two UMTRCA Title I sites in the eastern half of the United States, the other site being the Burrell, Pennsylvania, Title I Disposal Site, a vicinity property to the Canonsburg site. It has been 35 years since the disposal cell at the Canonsburg site was completed. This paper discusses the many efforts that have been taken to maintain the site and presents some of the lessons learned concerning the long-term care of the site. The discussion includes but is not limited to the following: (1) Preserving site history so the community can better appreciate and understand the site. (2) Community outreach efforts, and the importance of maintaining transparency of environmental monitoring results with the community. (3) Pursuing reuse opportunities that offer the potential for improving the community. (4) Remaining engaged with the local community. (5) Remaining proactive in the long-term care of the site. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

MDP: Reliable File Transfer for Space Missions

This paper presents work being done at NASA/GSFC (Goddard Space Flight Center) by the Operating Missions as Nodes on the Internet (OMNI) project to demonstrate the application of the Multicast Dissemination Protocol (MDP) to space missions to reliably transfer files. This work builds on previous work by the OMNI project to apply Internet communication technologies to space communication. The goal of this effort is to provide an inexpensive, reliable, standard, and interoperable mechanism for transferring files in the space communication environment. Limited bandwidth, noise, delay, intermittent connectivity, link asymmetry, and one-way links are all possible issues for space missions. Although these are link-layer issues, they can have a profound effect on the performance of transport and application level protocols. MDP, a UDP (User Datagram Protocol)-based reliable file transfer protocol, was designed for multicast environments which have to address these same issues, and it has done so successfully. Developed by the Naval Research Lab in the mid 1990s, MDP is now in daily use by both the US Post Office and the DoD (Department of Defense). This paper describes the use of MDP to provide automated end-to-end data flow for space missions. It examines the results of a parametric study of MDP in a simulated space link environment and discusses the results in terms of their implications for space missions. Lessons learned are addressed, which suggest minor enhancements to the MDP user interface to add specific features for space mission requirements, such as dynamic control of data rate, and a checkpoint/resume capability. These are features that are provided for in the protocol, but are not implemented in the sample MDP application that was provided. A brief look is also taken at the status of standardization. A version of MDP known as NORM (Nack Oriented Reliable Multicast) is in the process of becoming an IETF (Internet Engineering Task Force) standard.

Rash, James↗

MDP: Reliable File Transfer for Space Missions

This paper presents work being done at NASA/GSFC by the Operating Missions as Nodes on the Internet (OMNI) project to demonstrate the application of the Multicast Dissemination Protocol (MDP) to space missions to reliably transfer files. This work builds on previous work by the OMNI project to apply Internet communication technologies to space communication. The goal of this effort is to provide an inexpensive, reliable, standard, and interoperable mechanism for transferring files in the space communication environment. Limited bandwidth, noise, delay, intermittent connectivity, link asymmetry, and one-way links are all possible issues for space missions. Although these are link-layer issues, they can have a profound effect on the performance of transport and application level protocols. MDP, a UDP-based reliable file transfer protocol, was designed for multicast environments which have to address these same issues, and it has done so successfully. Developed by the Naval Research Lab in the mid 1990's, MDP is now in daily use by both the US Post Office and the DoD. This paper describes the use of MDP to provide automated end-to-end data flow for space missions. It examines the results of a parametric study of MDP in a simulated space link environment and discusses the results in terms of their implications for space missions. Lessons learned are addressed, which suggest minor enhancements to the MDP user interface to add specific features for space mission requirements, such as dynamic control of data rate, and a checkpoint/resume capability. These are features that are provided for in the protocol, but are not implemented in the sample MDP application that was provided. A brief look is also taken at the status of standardization. A version of MDP known as NORM (Neck Oriented Reliable Multicast) is in the process of becoming an IETF standard.

Rash, James↗

Overview of NASA's Thermal Control Technology Development Project

NASA?s Constellation Program included the Orion, Altair, and Lunar Surface Systems project offices. The first two elements, Orion and Altair, were planned to be manned space vehicles while the third element was much broader and included several sub-elements including Rovers and a Lunar Habitat. The planned missions involving these systems and vehicles included several risks and design challenges. Due to the unique thermal operating environment, many of these risks and challenges were associated with the vehicles? thermal control system. NASA?s Exploration Technology Development Program (ETDP) consisted of several technology development projects. The project chartered with mitigating the aforementioned thermal risks and design challenges was the Thermal Control System Development for Exploration Project. These risks and design challenges were being addressed through a rigorous technology development process that was planned to culminate with an integrated thermal control system test. Although these Constellation elements have been cancelled or significantly changed, the thermal technology development process is being continued within a new program entitled Enabling Technology Development and Demonstration (ETDD). The current paper summarizes the development efforts being performed by the technology development project. The development efforts involve heat acquisition and heat rejection hardware including radiators, heat exchangers, and evaporators. The project has also been developing advanced phase change material heat sinks and performing a material compatibility assessment for a promising thermal control system working fluid. The to-date progress and lessons-learned from these development efforts will be discussed throughout the paper.

Stephan, Ryan A.↗

The NASA Continuous Risk Management Process

As an intern this summer in the GRC Risk Management Office, I have become familiar with the NASA Continuous Risk Management Process. In this process, risk is considered in terms of the probability that an undesired event will occur and the impact of the event, should it occur (ref., NASA-NPG: 7120.5). Risk management belongs in every part of every project and should be ongoing from start to finish. Another key point is that a risk is not a problem until it has happened. With that in mind, there is a six step cycle for continuous risk management that prevents risks from becoming problems. The steps are: identify, analyze, plan, track, control, and communicate & document. Incorporated in the first step are several methods to identify risks such as brainstorming and using lessons learned. Once a risk is identified, a risk statement is made on a risk information sheet consisting of a single condition and one or more consequences. There can also be a context section where the risk is explained in more detail. Additionally there are three main goals of analyzing a risk, which are evaluate, classify, and prioritize. Here is where a value is given to the attributes of a risk &e., probability, impact, and timeframe) based on a multi-level classification system (e.g., low, medium, high). It is important to keep in mind that the definitions of these levels are probably different for each project. Furthermore the risks can be combined into groups. Then, the risks are prioritized to see what risk is necessary to mitigate first. After the risks are analyzed, a plan is made to mitigate as many risks as feasible. Each risk should be assigned to someone in the project with knowledge in the area of the risk. Then the possible approaches to choose from are: research, accept, watch, or mitigate. Next, all risks, mitigated or not, are tracked either individually or in groups. As the plan is executed, risks are re-evaluated, and the attribute values are adjusted as necessary. Metrics are established and monitored as tools for risk tracking. Also a trigger or threshold should be set on the metric data that indicates when an action is needed. Results of this tracking are usually evaluated and reported in a relevant format at weekly or monthly meetings. Choosing controls is the subsequent step, which involves the effects of the tracking. The three basic controls are: close, continue tracking, and re- plan. Finally communicate & document is the last step, but occurs throughout the process. It is vital that main risks, plans, changes, and progress are known by everyone in the project. A good way to keep everyone updated and inform other projects of common issues is by thoroughly documenting project risks. NASA sees value in risk management and believes that projects have greater probability or success by using the NASA Continuous Risk Management Process.

Pokorny, Frank M.↗

Let’s get our hands dirty: a comprehensive evaluation of DAQDB, key-value store for petascale hot storage

Data acquisition systems are a key component for successful data taking in any experiment. The DAQ is a complex distributed computing system and coordinates all operations, from the data selection stage of interesting events to storage elements. For the High Luminosity upgrade of the Large Hadron Collider, the experiments at CERN need to meet challenging requirements to record data with a much higher occupancy in the detectors. The DAQ system will receive and deliver data with a significantly increased trigger rate, one million events per second, and capacity, terabytes of data per second. An effective way to meet these requirements is to decouple real-time data acquisition from event selection. Data fragments can be temporarily stored in a large distributed key-value store. Fragments belonging to the same event can be then queried on demand, by the data selection processes. Implementing such a model relies on a proper combination of emerging technologies, such as persistent memory, NVMe SSDs, scalable networking, and data structures, as well as high performance, scalable software. In this paper, we present DAQDB (Data Acquisition Database) — an open source implementation of this design that was presented earlier, with an extensive evaluation of this approach, from the single node to the distributed performance. Furthermore, we complement our study with a description of the challenges faced and the lessons learned while integrating DAQDB with the existing software framework of the ATLAS experiment.

Abed Abud, Adam↗

The Oak Ridge Refrigerant Management Program

For many years, chlorofluorocarbons (CFC's) have been used by the Department of Energy's (DOE) Oak Ridge Y-12 Plant in air conditioning and process refrigeration systems. However, Title 6 of the Clean Air Act Amendments (CAAA) and Executive Order 12843 (Procurement Requirements and Policies for Federal Agencies for Ozone Depleting Substances) signed by President Clinton require, as policy, that all federal agencies maximize their use of safe, alternate refrigerants and minimize, where economically practical, the use of Class 1 refrigerants. Unfortunately, many government facilities and industrial plants have no plan or strategy in place to make this changeover, even though their air conditioning and process refrigeration equipment may not be sustainable after CFC production ends December 31, 1995. The Y-12 Plant in Oak Ridge, Tennessee, has taken an aggressive approach to complying with the CAAA and is working with private industry and other government agencies to solve tough manufacturing and application problems associated with CFC and hydrochlorofluorocarbon (HCFC) alternatives. Y-12 was the first DOE Defense Program (DP) facility to develop a long-range Stratospheric Ozone Protection Plan for refrigerant management for compliance with the CAAA. It was also the first DOE DP facility to complete detailed engineering studies on retrofitting and replacing all air conditioning and process refrigeration equipment to enable operation with alternate refrigerants. The management plan and engineering studies are models for use by other government agencies, manufacturing plants, and private industry. This presentation identifies some of the hidden pitfalls to be encountered in the accelerated phaseout schedule of CFC's and explains how to overcome and prevent these problems. In addition, it outlines the general issues that must be considered when addressing the phase-out of ozone depleting substances and gives some 'lessons learned' by Y-12 from its Refrigerant Management Program. Discussion topics include requirements for developing a refrigerant management plan and establishing priorities for cost-effective compliance with the CAAA, as well as ways in which employees can be empowered to develop a comprehensive refrigerant management plan. The result of this employee empowerment was a cooperative labor-management effort that is beneficial for Y-12, DOE, and the environment.

Kevil, Thomas H.↗

Workshop on Discovery Lessons-Learned

As part of the Discovery Program's continuous improvement effort, a Discovery Program Lessons-Learned workshop was designed to review how well the Discovery Program is moving toward its goal of providing low-cost research opportunities to the planetary science community while ensuring continued U.S. leadership in solar system exploration. The principal focus of the workshop was on the recently completed Announcement of Opportunity (AO) cycle, but the program direction and program management were also open to comment. The objective of the workshop was to identify both the strengths and weaknesses of the process up to this point, with the goal of improving the process for the next AO cycle. The process for initializing the workshop was to solicit comments from the communities involved in the program and to use the feedback as the basis for establishing the workshop agenda. The following four sessions were developed after reviewing and synthesizing both the formal feedback received and informal feedback obtained during discussions with various participants: (1) Science and Return on Investment; (2) Technology vs. Risk; Mission Success and Other Factors; (3) Cost; and (4) AO.AO Process Changes and Program Management.

Saunders, M.↗

Reducing NPR 7120.5D to Practice: Transitioning from Design Reviews to the SIR Hardware Review

The Gravity Recovery And Interior Laboratory (GRAIL) mission was the first Jet Propulsion Laboratory (JPL) project initiated under NASA's revised rules for space flight project management, NPR 7120.5D, "NASA Space Flight Program and Project Management Requirements." NASA selected GRAIL through a competitive Announcement of Opportunity process and funded its Phase B Preliminary Design effort. The team's first major milestone was a JPL institutional milestone, the Project Mission System Review (PMSR), which proved an excellent tune-up for the end-of-Phase-B NASA life-cycle review, the Preliminary Design Review (PDR). Building on JPL experience on the Prometheus and Juno projects, the team successfully organized for and conducted these reviews on an aggressive schedule. For the Project Critical Design Review (CDR), lessons learned from the PDR and updated Standing Review Board (SRB) practices from the Agency were factored into the review preparation effort. Additionally, the review was held at the Principal Investigator's institution, the Massachusetts Institute of Technology, rather than at the project management center (JPL), which necessitated additional cross-country coordination steps. The PMSR, PDR, and CDR were design reviews and largely paper-oriented. For the System Integration Review (SIR), the project needed to transition to a hardware review and deal with paper in a very different manner. While many of the practices employed for the design reviews were modified and retained (e.g., review preparation team, gate products management, pre-reviews, SRB coordination), the review agenda, presentation style, and slide templates were significantly changed. A key success factor concerned the handling of project open paper, which was succinctly and effectively communicated to the SRB in presentations.This paper provides a brief overview of the GRAIL mission and its project management challenges, provides a detailed description of project SIR preparation and execution activities, including positive and negative lessons learned and identifies recommendations for future NASA (and non- NASA) project teams.

NPR 7120.5D↗

Sleuthing the MSL EDL Performance from an X Band Carrier Perspective

During the Entry, Descent, and Landing (EDL) of NASA's Mars Science Laboratory (MSL), or Curiosity, rover to Gale Crater on Mars on August 6, 2012 UTC, the rover transmitted an X-band signal composed of carrier and tone frequencies and a UHF signal modulated with an 8kbps data stream. During EDL, the spacecraft's orientation is determined by its guidance and mechanical subsystems to ensure that the vehicle land safely at its destination. Although orientation to maximize telecom performance is not possible, antennas are especially designed and mounted to provide the best possible line of sight to Earth and to the Mars orbiters supporting MSL's landing. The tones and data transmitted over these links are selected carefully to reflect the most essential parameters of the vehicle's state and the performance of the EDL subsystems for post-EDL reconstruction should no further data transmission from the vehicle be possible. This paper addresses the configuration of the X band receive system used at NASA / JPL's Deep Space Network (DSN) to capture the signal spectrum of MSL's X band carrier and tone signal, examines the MSL vehicle state information obtained from the X band carrier signal only and contrasts the Doppler-derived information against the post-EDL known vehicle state. The paper begins with a description of the MSL EDL sequence of events and discusses the impact of the EDL maneuvers such as guided entry, parachute deploy, and powered descent on the frequency observables expected at the DSN. The range of Doppler dynamics possible is derived from extensive 6 Degrees-Of-Freedom (6 DOF) vehicle state calculations performed by MSL's EDL simulation team. The configuration of the DSN's receive system, using the Radio Science Receivers (RSR) to perform open-loop recording for both for nominal and off-nominal EDL scenarios, is detailed. Expected signal carrier power-to-noise levels during EDL are shown and their impact on signal detection is considered. Particular attention is given to the selection of the appropriate RSR processing bandwidths and to its configuration for real-time signal detection. The X-band carrier frequency obtained through post-processing of the open-loop recorded spectrum is given. Detection of spacecraft status and completion of key vehicle events through their Doppler signature is discussed and illustrated. This Doppler-derived information is compared against the very accurate vehicle data obtained post-EDL via MSL's UHF radio subsystem. The paper concludes with a discussion on the advantages and disadvantages of transmitting the X-band carrier and tone signal in the general context of EDL communications and lessons learned for future missions with EDL sequences are given

Mars Science Laboratory (MSL)↗

Design Limit Loads and Verification Approach for the TESS Observatory

The Transiting Exoplanet Survey Satellite (TESS) is a NASA Explorer mission. The TESS Observatory is scheduled to launch on Falcon 9 in April 2018. This presentation covers the process used to define and update design limit loads for the observatory, instrument, and components throughout the life of the program. The limit loads that drove the need for a SoftRide isolation system are highlighted. The testing performed to qualify the observatory for launch loads at the instrument and observatory level is also detailed. In addition, exchanges with the launch vehicle provider in terms of loads predictions and hardware for test are discussed along with the associated issues encountered and lessons learned. The loads development and verification success on TESS was a team effort. Orbital ATK is the spacecraft provider, NASA GSFC provides project management and technical oversight, the instrument is managed by MIT Kavli Institute and the instrument cameras are built and tested by MIT Lincoln Laboratory. Since the instrument was designed in parallel with the spacecraft, the instrument design limit loads were developed in partnership with NASA and the instrument team. The three teams collaborated on a regular basis starting in the early design phase and continuing through observatory level testing.

Limit Loads↗