Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Mission”

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 523 records · Page 29

CEO Sites Mission Management System (SMMS)

Late in fiscal year 2011, the Crew Earth Observations (CEO) team was tasked to upgrade its science site database management tool, which at the time was integrated with the Automated Mission Planning System (AMPS) originally developed for Earth Observations mission planning in the 1980s. Although AMPS had been adapted and was reliably used by CEO for International Space Station (ISS) payload operations support, the database structure was dated, and the compiler required for modifications would not be supported in the Windows 7 64-bit operating system scheduled for implementation the following year. The Sites Mission Management System (SMMS) is now the tool used by CEO to manage a heritage Structured Query Language (SQL) database of more than 2,000 records for Earth science sites. SMMS is a carefully designed and crafted in-house software package with complete and detailed help files available for the user and meticulous internal documentation for future modifications. It was delivered in February 2012 for test and evaluation. Following acceptance, it was implemented for CEO mission operations support in April 2012. The database spans the period from the earliest systematic requests for astronaut photography during the shuttle era to current ISS mission support of the CEO science payload. Besides logging basic image information (site names, locations, broad application categories, and mission requests), the upgraded database management tool now tracks dates of creation, modification, and activation; imagery acquired in response to requests; the status and location of ancillary site information; and affiliations with studies, their sponsors, and collaborators. SMMS was designed to facilitate overall mission planning in terms of site selection and activation and provide the necessary site parameters for the Satellite Tool Kit (STK) Integrated Message Production List Editor (SIMPLE), which is used by CEO operations to perform daily ISS mission planning. The CEO team uses the SMMS for three general functions - database queries of content and status, individual site creation and updates, and mission planning. The CEO administrator of the science site database is able to create or modify the content of sites and activate or deactivate them based on the requirements of the sponsors. The administrator supports and implements ISS mission planning by assembling, reporting, and activating mission-specific site selections for management; deactivating sites as requirements are met; and creating new sites, such as International Charter sites for disasters, as circumstances warrant. In addition to the above CEO internal uses, when site planning for a specific ISS mission is complete and approved, the SMMS can produce and export those essential site database elements for the mission into XML format for use by onboard Earth-location systems, such as Worldmap. The design, development, and implementation of the SMMS resulted in a superior database management system for CEO science sites by focusing on the functions and applications of the database alone instead of integrating the database with the multipurpose configuration of the AMPS. Unlike the AMPS, it can function and be modified within the existing Windows 7 environment. The functions and applications of the SMMS were expanded to accommodate more database elements, report products, and a streamlined interface for data entry and review. A particularly elegant enhancement in data entry was the integration of the Google Earth application for the visual display and definition of site coordinates for site areas defined by multiple coordinates. Transfer between the SMMS and Google Earth is accomplished with a Keyhole Markup Language (KML) expression of geographic data (see figures 3 and 4). Site coordinates may be entered into the SMMS panel directly for display in Google Earth, or the coordinates may be defined on the Google Earth display as a mouse-controlled polygonal definition and transferred back into the SMMS as KML input. This significantly reduces the possibility of errors in coordinate entries and provides visualization of the scale of the site being defined. CEO now has a powerful tool for managing and defining sites on the Earth's surface for both targets of astronaut photography or other onboard remote sensing systems. It can also record and track results by sponsor, collaborator, or type of study.

Trenchard, Mike↗

Advances in Astromaterials Curation: Supporting Future Sample Return Missions

NASA's Astromaterials, curated at the Johnson Space Center in Houston, are the most extensive, best-documented, and leastcontaminated extraterrestrial samples that are provided to the worldwide research community. These samples include lunar samples from the Apollo missions, meteorites collected over nearly 40 years of expeditions to Antarctica (providing samples of dozens of asteroid bodies, the Moon, and Mars), Genesis solar wind samples, cosmic dust collected by NASA's high altitude airplanes, Comet Wild 2 and interstellar dust samples from the Stardust mission, and asteroid samples from JAXA's Hayabusa mission. A full account of NASA's curation efforts for these collections is provided by Allen, et al [1]. On average, we annually allocate about 1500 individual samples from NASA's astromaterials collections to hundreds of researchers from around the world, including graduate students and post-doctoral scientists; our allocation rate has roughly doubled over the past 10 years. The curation protocols developed for the lunar samples returned from the Apollo missions remain relevant and are adapted to new and future missions. Several lessons from the Apollo missions, including the need for early involvement of curation scientists in mission planning [1], have been applied to all subsequent sample return campaigns. From the 2013 National Academy of Sciences report [2]: "Curation is the critical interface between sample return missions and laboratory research. Proper curation has maintained the scientific integrity and utility of the Apollo, Antarctic meteorite, and cosmic dust collections for decades. Each of these collections continues to yield important new science. In the past decade, new state-of-the-art curatorial facilities for the Genesis and Stardust missions were key to the scientific breakthroughs provided by these missions." The results speak for themselves: research on NASA's astromaterials result in hundreds of papers annually, yield fundamental discoveries about the evolution of the solar system (e.g. [3] and references contained therein), and serve the global scientific community as ground truth for current and planned missions such as NASA's Dawn mission to Vesta and Ceres, and the future OSIRIS REx mission to asteroid Bennu [1,3]

Evans, C. A.↗

Modular Growth NTR Space Transportation System for Future NASA Human Lunar, NEA and Mars Exploration Missions

The nuclear thermal rocket (NTR) is a proven, high thrust propulsion technology that has twice the specific impulse (I(sub sp) approx.900 s) of today's best chemical rockets. During the Rover and NERVA (Nuclear Engine for Rocket Vehicle Applications) programs, twenty rocket reactors were designed, built and ground tested. These tests demonstrated: (1) a wide range of thrust; (2) high temperature carbide-based nuclear fuel; (3) sustained engine operation; (4) accumulated lifetime; and (5) restart capability - everything required for affordable human missions beyond LEO. In NASA's recent Mars Design Reference Architecture (DRA) 5.0 study, the NTR was selected as the preferred propulsion option because of its proven technology, higher performance, lower IMLEO, versatile vehicle design, and growth potential. Furthermore, the NTR requires no large technology scale-ups since the smallest engine tested during the Rover program - the 25 klb(sub f) "Pewee" engine is sufficient for human Mars missions when used in a clustered engine configuration. The "Copernicus" crewed Mars transfer vehicle developed for DRA 5.0 was an expendable design sized for fast-conjunction, long surface stay Mars missions. It therefore has significant propellant capacity allowing a reusable "1-year" round trip human mission to a large, high energy near Earth asteroid (NEA) like Apophis in 2028. Using a "split mission" approach, Copernicus and its two key elements - a common propulsion stage and integrated "saddle truss" and LH2 drop tank assembly - configured as an Earth Return Vehicle / propellant tanker, can also support a short round trip (approx.18 month) / short orbital stay (60 days) Mars reconnaissance mission in the early 2030's before a landing is attempted. The same short stay orbital mission can be performed with an "all-up" vehicle by adding an "in-line" LH2 tank to Copernicus to supply the extra propellant needed for this higher energy, opposition-class mission. To transition to a reusable Mars architecture, Copernicus' saddle truss / drop tank assembly is replaced by an in-line tank and "star truss" assembly with paired modular drop tanks to further increase the vehicle's propellant capacity. Shorter "1-way" transit time fast-conjunction Mars missions are another possibility using this vehicle configuration but, as with reusability, increased launch mass is required. "Scaled down" versions of Copernicus (sized to a SLS lift capability of approx.70 t - 100 t) can be developed initially allowing reusable lunar cargo delivery and crewed landing missions, easy NEA missions (e.g., 2000 SG344 also in 2028) or an expendable mission to Apophis. Mission scenario descriptions, key vehicle features and operational characteristics are provided along with a brief discussion of NASA's current activities and its "pre-decisional" plans for future NTR development.

Borowski, Stanley K.↗

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↗

Managing Flagship Missions to Reduce Cost and Schedule

Flagship missions are highly complex with highly nested systems. This level of complexity poses unique management problems as complexity influences risk which, in turn, affects cost and schedule. Establishing a strong technical and programmatic leadership team is critical to mission success. Developing and using a mission architecture is critical to informing the management organization, product ownership, interface and integration relationships, schedule organization, and integration and test paths. In highly nested systems, the mission phasing can be significantly out of sync with product phasing. Targeted technology development prior to Phase A is critical to reducing risk. Early architecture, concept design, and requirements development is critical to reducing risk. Modular design; pathfinders; parallel manufacturing and integration and test paths; and properly handling institutional requirements across interfaces are all management techniques that can be applied to reduce risk. NASA’s large strategic missions, sometimes referred to as flagship missions, are designed to provide answers to some of the most compelling scientific questions being asked. These types of missions are a series of highly nested subsystems that pose unique management problems when compared to more traditional instrument and spacecraft designs. They typically have an overall architecture that is very complex and nested; they typically require a tremendous amount of technology development; they typically involve many contractors and subcontractors with many associated contracts; and they typically involve staff from all over the world. Successful management of a flagship requires the balance between science requirements, engineering and technology capabilities, and resource constraints. Mismanaging these flagship missions can and will lead to significant cost and schedule growth, both of which are detrimental to NASA’s overall reputation which, in turn, is detrimental to the development of future flagship missions. While many of the same management principles used on smaller instruments and spacecraft are relevant, managing flagship missions requires an evolution of those current best practices to better address the specific needs and additional complexity and vastness of these missions. This paper explores how to leverage lessons learned from previous flagship missions to better manage flagship missions in the future.

Hylan, Jason↗

Examining the Trends in Financial Support Given to Science Teams for Data Analysis in Mission Proposals

Introduction: The goal of this summer internship research project was to analyze trends in financial support proposed for the science teams of planetary missions. The analysis focuses on the funding for Co-Investigators (Co-Is) to conduct research and/or data analysis needed to achieve the science objectives of the mission. The operational portion of the missions after launch (i.e., Phase E, including cruise and prime operations at the final destination) were examined since that is when the bulk of research is funded and conducted. The objectives of the project were to determine the average level of support for Co-Investigators, identify variation between mission competitions and over time, and determine the relationship between mission type and the amount of support requested. Methodology: This project was conducted using data from 90 proposals submitted to six mission competitions in the Discovery and New Frontiers programs. The level of support for Co-Is was determined by examining Work Breakdown Structure (WBS) 4 (Science Analysis) for Phase E, which was further subdivided into cruise and prime operations. This data represents a proxy rather than the actual funding Co-Is receive to perform research and data analysis because not every dollar in WBS 4 is spent on this activity. Therefore, the proxy obtained in this research represents an overestimate of the funds allocated to Co-Is for research and data analysis. Findings: Analysis shows that on average a Co-I receives approximately four full years of support spread across the entirety of Phase E for science analysis. The variation among proposed missions is less than expected given the variety of factors that are expected to drive this metric (length of mission, mission type, etc.). Additionally, the level of requested support for Co-Is has been remarkably consistent across every variable considered (by competition, over time, by mission type) over the six competitions and nearly 20 years spanned by this project. This remains true for cruise, primary operations, and all of Phase E. Conclusions: A remarkable amount of science is accomplished by the science teams of planetary missions. However, a surprisingly small amount of funding is requested to support the science analysis driving this productivity, both in terms of absolute magnitude of funding and as a portion of total mission cost. This suggests improvements are needed to refine the estimates of Co-I support and/or that Co-Is rely on other funding sources to conduct their research. Better estimates can be determined by engaging directly with Co-Is and NASA centers to obtain data as well as finding other data sources. Additionally, NASA could consider mandating improved reporting of requested funding levels in mission competitions.

E Murray↗

Quantifying Risk to Improve Medical System Design for Long Duration Artemis Missions: A Demonstration of NASA's IMPACT Tradespace Analysis Tool

BACKGROUND NASA’s human exploration spaceflight missions to the Moon and Mars present unprecedented challenges for in-mission medical care. A greater distance from Earth will mean increased mission durations, communication delays, limited to no resupply opportunities, and constraints on the evacuation of ill or injured crew. Mass, volume, and power will be limited while higher demands will be placed on the crews to manage medical events. NASA’s Moon to Mars exploration strategy outlines increasingly complex Artemis missions both in terms of duration and operations. In these more challenging deep space missions, it is important to quantitatively estimate the human system risk attributable to medical conditions and use these estimates to advance medical system design. METHODS IMPACT (Informing Mission Planning via Analysis of Complex Tradespaces) is a probabilistic risk assessment (PRA) and tradespace analysis tool developed by NASA to advance exploration mission medical system design. IMPACT v1.0 includes a novel evidence library baselined to exploration environments; an expanded list of 119 medical conditions; a large increase in the number of medical resources and the flexibility of their use; and the ability for rapid and iterative analysis. Medical system risk estimates include loss of crew life, consideration of the need for return to definitive care (medical evacuation), and an estimate of crew time affected due to medical conditions. A notional long duration lunar orbit and lunar surface design reference mission (DRM) was chosen with a 4-astronaut crew to mimic a foundational exploration Artemis mission. The DRM profile includes outbound transit on Orion, Gateway space station rendezvous in lunar orbit, 6 months on the Lunar surface with extravehicular activity (EVA), return rendezvous with Gateway, and transit back to Earth. RESULTS/DISCUSSION: Overall, IMPACT successfully quantified medical risk and derived an optimal medical system to support crew on a long duration lunar mission. In this DRM, the calculated loss of crew life from a medical event was 0.008 events per mission, risk of potential need for evacuation was 0.30 events per mission, and cumulative crew time affected by medical conditions was 103 days. The medical conditions that most contributed to medical risk were decompression sickness, trauma, and respiratory failure. The conditions that had the largest effects on crew performance included musculoskeletal injuries and lunar dust exposure. The IMPACT-generated medical system included resources that target the most common and highest risk conditions and performed as expected. This demonstrates the value of the IMPACT tool in medical system design for human exploration spaceflight missions.

Arian Anderson↗

Physical Parameters of Space Mission Asteroid Targets

Ground-based characterization of asteroids that are planned or potential targets of space missions provides important data on their physical parameters and properties. Knowledge of the properties of mission targets is important especially during mission preparation and planning, as it serves to select best or suitable targets for specific purpose of a given mission, to prepare mission plans, to constrain possible mission scenarios, and to design mission experiments. Such characterization efforts may be particularly critical for flyby missions that take only limited data during the high-speed flybys of their target asteroids, but they also provide very crucial data for targets of rendezvous missions. Moreover, long-term observations taken from Earth also allows the modelling of, or constraining, processes acting on the asteroids over extended time scales. Over the past years and decades we have obtained rich data on physical parameters of 82 asteroids that are planned or potential targets of space missions. Our primary observing technique is time-resolved (lightcurve) photometry, but we use also data obtained with other techniques, such as spectroscopy, thermal or radar observations. 15 of the 82 characterized asteroids are planned or possible targets of several space missions that are in flight or preparation, such as ESA’s Hera, RAMSES and PRIAMOS, NASA’s OSIRIS-APEX, JAXA’s Hayabusa2#, DESTINY+ and Next Generation Sample Return (NGSR), the Emirates Mission to Asteroids (EMA), and Karman+’s High Frontier, but we have also characterized 67 asteroids that are potential targets of space missions for their low delta-V’s and were announced as being “of interest to NASA” in the Small-Bodies-Observations- NASA mailing list or listed on the NHATS page of “Accessible NEAs”. The sample of asteroid targets span 3 orders of magnitude in size, with absolute magnitudes H from 12.57 to 26.8, corresponding to diameters from about 10 m to about 10 km. The sample contains a variety of taxonomic types and physically or dynamically interesting objects. Among them, we have identified 5 binary asteroids and 20 tumblers (i.e., asteroids in excited, non-principal axis rotation states). Rotation periods of the characterized asteroids range from 1.45 min to 280 h, reflecting diversity of their properties and formation/evolution paths. We will present an overview of the data set and highlight several representative cases.

Petr Pravec↗

Prioritizing and Managing Technology Needs to Meet River Protection Project Mission Objectives - 16462

Over 56 million gallons of radioactive waste are stored in 177 large underground tanks at the Hanford Site, located in southeastern Washington State. This nuclear waste resulted from plutonium production for the nation's nuclear defense program. The River Protection Project (RPP) mission is to: - Safeguard and safely manage waste stored in the Hanford tanks, - Treat the waste using the Waste Treatment and Immobilization Plant (WTP), - Ensure safe disposition of the waste to protect the Columbia River and the environment. Each aspect of the mission requires some application of technology in order to meet the mission objectives. The RPP Technology Roadmap document presents a comprehensive, integrated assessment of the technology-related advances needed to ensure successful completion of the Hanford tank waste cleanup mission. This paper describes the development of the RPP Technology Roadmap, summarizes its content, describes integration and collaboration with the Department of Energy's national laboratories to support the work identified, and defines how priorities were identified to ensure near-term RPP mission commitments can be accomplished while preserving the longer term technology development elements necessary for mission completion. The Challenge - Managing a wide variety of technology needs that involve multiple organizations, contractors, and national laboratories presents additional challenges when funding constraints are factored in. A process was needed to ensure the technology needs supporting near term mission priorities were appropriately identified, prioritized, and supported through the fiscal year planning process. Additionally, the national laboratory resources necessary to support many of the technologies require coordination to ensure the most appropriate resources are applied at the appropriate level without duplication or contradiction of effort. The Solution - The RPP Technology Roadmap was developed with the primary purposes to: - Identify technology related items needed to support or enhance the River Protection Project (RPP) mission, - Prioritize technology needs to support fiscal year planning processes, - Organize National laboratory support of the RPP mission and communicate needs to the participating contractors. The Technology Roadmap is consistent with Department of Energy (DOE) Hanford mission priorities and is also in alignment with other Hanford Site technical initiatives and policy and planning documents. The Technology Roadmap highlights the current estimated technology needs and identifies where planning shortfalls exist and where national laboratory participation is needed to support mission success. This information assists fiscal year planning and national laboratory contracting processes to ensure that technology needs are supported. In addition to supporting the RPP baseline mission, the Technology Roadmap provides a basis for strategic planning by identifying opportunities to use technology solutions to enhance mission efficiency. This waste management paper describes the innovative and collaborative processes used to develop, validate, and communicate the results so the project owners and the national laboratories can most effectively plan work scope and resources. A discussion of the following processes is included: - Technology needs and task owner identification, - Functional area grouping and area lead identification, - Needs prioritization, - High priority needs ranking (including validation), - Results compilation and planning gap identification, - Results presentation by project and functional area, - National laboratory coordination and collaboration. Application - The process used to develop the RPP technology roadmap is applicable to any site where multiple national laboratories and contractors are involved in identifying and implementing technology based solutions. This process is also applicable to the DOE HQ role to provide prioritization and coordination of the nationwide technology development activities. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

(abstract) MEASURE-Jupiter: Low Cost Missions to Explore Jupiter in the Post-Galileo Era

MEASURE-Jupiter is a new mission concept for the exploration of giant planets, with initial application to Jupiter. By flying sets of lightweight spacecraft with highly focused measurement objectives, it is designed to break the apparent impass in giant planet exploration beyond Cassini. The MEASURE-Jupiter concept is characterized by: 1) intensive exploration of a giant planet system, 2) multiple small missions flown in focused waves using spacecraft costing $100M to $200M, and 3) mission sets launched every 2 to 3 years. Why Jupiter? Jupiter is the most complex planetary system in the Solar System with many scientifically intriguing bodies and phenomena to explore. The Galileo mission will scratch the surface of the exploration of Jupiter, posing many questions for the MEASURE-Jupiter missions to address. Jupiter is also the easiest planet in the Outer Solar System to reach, making possible flight times of 2 years and total mission durations of 3 years or less. Concept design studies have uncovered a number of scientifically rewarding, simple, low-cost mission options. These options have the additional attraction of being able to launch on 2-year trajectories to Jupiter with low-cost Delta II expendable launch vehicles. A partial list of mission concepts studied to date include: Io Very Close Flyby, Jupiter Close Polar Pass, Mini-Orbiters, and Galilean Satellite Penetrators. Key to the realization of the MEASURE-Jupiter missions is the judicious use of the new low power consuming advanced technology and applicable systems from the Pluto Fast Flyby mission spacecraft design. Foremost of the new technologies planned for inclusion are the elements of hybrid solar array/battery power systems which make it possible to perform the identified missions without the need for Radioactive Thermoelectric Generators (RTGs). This relieves the mission design of the attendant programmatic complexities, cost, and constraints attendant with the use of RTGs.

MEASURE-Jupiter Jupiter Pluto Fast Flyby low cost ↗

Preparing for Human Missions to Mars: The role of ISS and Artemis as Analogs for Research and Technology Testing

The hazards of spaceflight to the human system are present in in varying degrees on different spaceflight platforms: altered gravity, isolation and confinement, distance from Earth, radiation, and hostile closed environments. A strategic view of the fidelity of hazards experienced on different platforms can shape the testing plans for human research and technology demonstration related to crew health and performance. Working across the international partnership, the International Space Station (ISS) is planning periods of modified operations to improve the fidelity of Mars simulations. To understand transit durations as an independent variable, a series of 1-year, 6-month and 30-45 day missions are being planned on ISS. Standard measurements across ISS missions of different durations, lunar missions and ground analogs offers the opportunity to distinguish different hazards and their effects in the context of the relevance to future mission concepts. The ISS partnership is planning for additional test cases that are aligned with Mars mission plans. (1) Evaluating crew performance capabilities when transitioning to gravity after long durations in microgravity representative of a Mars transit. (2) Simulating crew medical care under Mars-like autonomous operations. (3) Identification and testing of operations under communications delay and autonomy expected for Mars missions and the linked effects on behavioral health and performance of the crew. Artemis missions serve as a valuable analogs for Mars surface operations, with partial gravity and deep space radiation hazards, but with crewmembers that are probably more physically capable than their counterparts would be after a Mars transit. Getting unobtrusive data from early Artemis missions, and knowledge gained from operational experience as Artemis operations develop can improve engineering design, medical requirements and countermeasures, and ultimately ensure mission success on Mars. Linking Mars architectures with the plans and capabilities for ISS and Artemis allows us to plan to most operationally relevant tests of crew health and performance on current spaceflight missions to inform planning for future missions to Mars. By using human spaceflight platforms as well as ground simulation in an integrated way, the international community can improve exploration readiness, develop countermeasures and reduce risks of future human space missions.

International Space Station↗

In-Depth Modeling and Simulation Analysis of Artemis Missions Using the Impact Probabilistic Risk Assessment Tool

BACKGROUND The Artemis campaign is a Moon exploration program with a series of six planned missions, five of which will be crewed. These five crewed missions will contain a single mission segment (space flight), or multiple mission segments involving space flight (Orion), lunar landing (LTV) and/or space habitat (Gateway). Each crewed segment faces the risk of unique medical conditions, necessitating medical sets/kits tailored to those specificities. To support and enable a data-driven and evidence-based decision-making process through out a mission’s life cycle, a software tool called IMPACT was developed. Using probabilistic risk assessment (PRA) methodologies, IMPACT (Informing Mission Planning via Analysis of Complex Tradespaces) is a novel tool built for analyzing the possibility of encountering complex medical risks during space flight, and for identifying the medical resources and capabilities needed to treat those potential at-risk medical conditions. IMPACT achieves this by performing hundreds of thousands of Monte Carlo simulations of missions to build aggregate pictures of medical risk. During an extended simulation modeling phase, IMPACT generated analytical results for medical risks, and the medical resources and capabilities to address those risks, for every segment of every crewed Artemis mission. This presentation will highlight the reliability, consistency and validity of IMPACT’s computational modeling techniques and will showcase the library of analytical outcomes generated for the Artemis missions. OVERVIEW During the early stages of IMPACT’s design, architecture and technical requirements collection, “scenarios” (use cases) - achievement goals required for acceptance testing, were identified by stakeholders. IMPACT successfully completed the scenario testing requirements and undertook an extensive operational run phase utilizing a wide range of input combinations with a goal of delivering a cohesive, trustworthy, reliable, vast, and diverse body of evidence. The intent of these modeling runs was to validate consistency in output, ensure solidity of executable operations and to streamline processes by identifying areas requiring efficiency improvements. Using the many missions of Artemis, IMPACT ran variations of operational runs to assess the output for acceptable, as well as unusual characteristics. This rigorous long-term “shakedown” analysis was implemented to help build a collective body of evidence to aid in securing a high level of confidence, reliability, and validity in the output, whether from the applicational components of IMPACT, or the entirety of the operational process. ANTICIPATED ANALYSIS AND CONCLUSION This presentation will discuss the various categories of input criteria; the comparisons in the application of these input criteria to various Artemis missions; the preparation and collection of the body of evidence, and reliability of the computational modeling techniques. This paper serves as an initial analytical overview of IMPACT’s probabilistic risk assessment (PRA) medical risk outputs covering Artemis missions and is not intended to be deemed the official medical response for the Artemis campaign.

Crew Composition↗

Empire. a study of early manned interplanetary missions final report, may 26 - nov. 25, 1962

This report summarizes the investigations and results of the EMPIRE Study Program undertaken by Aeronutronic Division of Ford Motor Company for the Future Projects Office, Marshall Space Flight Center, under Contract NAS8-5025. The dual planet flyby missions of the Crocco and Symmetric trajectory classes are discussed. The Crocco mission with an August 1971 launch window requires an interplanetary injection velocity increment of i0.i km/sec, has a return velocity of 13.5 km/sec, and takes approximately 400 days. The Symmetric mission with a July 1970 launch window has an injection velocity increment of 5.3 km/sec, a return velocity of 15.8 km/sec, and takes approximately 630 days. Additional results of the trajectory studies and abort trajectories are reported. The guidance and navigation subsystem, midcourse corrections, and planetary approach corrections are discussed. A detailed analysis of the reentry phase of EMPIRE includes consideration of an Apollo-type, a Drag Brake, and a lifting-type reentry vehicle to return the six-man crew at mission completion or in an aborted condition. The High L/D reentry vehicle is used in the missions considered. The various technological areas required for design criteria are developed and several spacecraft designs are considered. The all chemical propulsion Crocco system is discarded due to weight, complexity, and cost. The nuclear injected Crocco is treated in a similar manner. The lower energy injection for the Symmetric Mission leads to the feasibility of a nuclear injected vehicle with an Earth orbit weight of about 180,000 kilograms (400,000 pounds) before interplanetary transit. In addition, two chemical symmetric vehicles are treated. Conservative radiation exposures are derived, for the 630 day mission, of less than 200 REM and a polyethelene radiation shelter is designed. Scientific aspects of the missions are discussed. Mission Success Probabilities are presented for the various missions considered and for Saturn C-5, Nova, and Super-Nova Earth launch vehicles in light of possible development. The need for acceleration of nuclear rocket engine developments and auxiliary power developments is indicated. Definition of a larger nuclear engine of the order of 200,000 pounds thrust and about 800 seconds burning time or 50,000 pound thrust and 3600 seconds burning time is indicated for the Symmetric Mission in 1970 (energy requirements are higher in 1972 and for later launch due to the less favorable position of Mars)_ Immediate development of this advanced nuclear propulsion capability is recommended. A Development Plan and Funding Schedule is given for the 1970 launch window pinpointing the critical development areas and indicating a total program cost of $12.6 billion independent of other programmed R&D costs. In conclusion, technological feasibility for an early manned dual planet Mars-Venus flyby is believed to be demonstrated in this study. Several areas of accelerated development and experimental confirmation of theory are pinpointed. The necessary funding and development of Nova or orbital operations capability with Saturn C-5's is required. The 1970 launch window appears to offer the least expensive Symmetric Mission for several years into the 1980's.

F. P. Dixon↗

Missions to comets - The perspective in 1980

The design and performance characteristics of deep space missions to study comets are discussed. Following a brief review of the scientific objectives of cometary missions and the problems posed by cometary orbits and the cometary environment to designers of space missions, consideration is given to the spacecraft and planned trajectories of cometary missions either planned or under consideration at one time. The missions include the Gioto mission, a Halley fly-through to be launched by ESA which developed out of the defunct NASA/ESA Halley/Tempel 2 rendezvous mission; the Japanese Planet A and Soviet/French flyby missions to Halley; and the Halley Intercept Mission, studied by NASA but not approved. It is pointed out that although much new information will be obtained from the Halley flyby missions, the second generation of cometary missions will undoubtedly require a rendezvous mission such as the one NASA is still studying.

Wilkening, L. L.↗

Galileo mission planning for Low Gain Antenna based operations

The Galileo mission operations concept is undergoing substantial redesign, necessitated by the deployment failure of the High Gain Antenna, while the spacecraft is on its way to Jupiter. The new design applies state-of-the-art technology and processes to increase the telemetry rate available through the Low Gain Antenna and to increase the information density of the telemetry. This paper describes the mission planning process being developed as part of this redesign. Principal topics include a brief description of the new mission concept and anticipated science return (these have been covered more extensively in earlier papers), identification of key drivers on the mission planning process, a description of the process and its implementation schedule, a discussion of the application of automated mission planning tool to the process, and a status report on mission planning work to date. Galileo enhancements include extensive reprogramming of on-board computers and substantial hard ware and software upgrades for the Deep Space Network (DSN). The principal mode of operation will be onboard recording of science data followed by extended playback periods. A variety of techniques will be used to compress and edit the data both before recording and during playback. A highly-compressed real-time science data stream will also be important. The telemetry rate will be increased using advanced coding techniques and advanced receivers. Galileo mission planning for orbital operations now involves partitioning of several scarce resources. Particularly difficult are division of the telemetry among the many users (eleven instruments, radio science, engineering monitoring, and navigation) and allocation of space on the tape recorder at each of the ten satellite encounters. The planning process is complicated by uncertainty in forecast performance of the DSN modifications and the non-deterministic nature of the new data compression schemes. Key mission planning steps include quantifying resource or capabilities to be allocated, prioritizing science observations and estimating resource needs for each, working inter-and intra-orbit trades of these resources among the Project elements, and planning real-time science activity. The first major mission planning activity, a high level, orbit-by-orbit allocation of resources among science objectives, has already been completed; and results are illustrated in the paper. To make efficient use of limited resources, Galileo mission planning will rely on automated mission planning tools capable of dealing with interactions among time-varying downlink capability, real-time science and engineering data transmission, and playback of recorded data. A new generic mission planning tool is being adapted for this purpose.

Gershman, R.↗

Mission operations management

Redefining the approach and philosophy that operations management uses to define, develop, and implement space missions will be a central element in achieving high efficiency mission operations for the future. The goal of a cost effective space operations program cannot be realized if the attitudes and methodologies we currently employ to plan, develop, and manage space missions do not change. A management philosophy that is in synch with the environment in terms of budget, technology, and science objectives must be developed. Changing our basic perception of mission operations will require a shift in the way we view the mission. This requires a transition from current practices of viewing the mission as a unique end product, to a 'mission development concept' built on the visualization of the end-to-end mission. To achieve this change we must define realistic mission success criteria and develop pragmatic approaches to achieve our goals. Custom mission development for all but the largest and most unique programs is not practical in the current budget environment, and we simply do not have the resources to implement all of our planned science programs. We need to shift our management focus to allow us the opportunity make use of methodologies and approaches which are based on common building blocks that can be utilized in the space, ground, and mission unique segments of all missions.

Rocco, David A.↗

Integrated Network Architecture for NASA's Orion Missions

NASA is planning a series of short and long duration human and robotic missions to explore the Moon and then Mars. The series of missions will begin with a new crew exploration vehicle (called Orion) that will initially provide crew exchange and cargo supply support to the International Space Station (ISS) and then become a human conveyance for travel to the Moon. The Orion vehicle will be mounted atop the Ares I launch vehicle for a series of pre-launch tests and then launched and inserted into low Earth orbit (LEO) for crew exchange missions to the ISS. The Orion and Ares I comprise the initial vehicles in the Constellation system of systems that later includes Ares V, Earth departure stage, lunar lander, and other lunar surface systems for the lunar exploration missions. These key systems will enable the lunar surface exploration missions to be initiated in 2018. The complexity of the Constellation system of systems and missions will require a communication and navigation infrastructure to provide low and high rate forward and return communication services, tracking services, and ground network services. The infrastructure must provide robust, reliable, safe, sustainable, and autonomous operations at minimum cost while maximizing the exploration capabilities and science return. The infrastructure will be based on a network of networks architecture that will integrate NASA legacy communication, modified elements, and navigation systems. New networks will be added to extend communication, navigation, and timing services for the Moon missions. Internet protocol (IP) and network management systems within the networks will enable interoperability throughout the Constellation system of systems. An integrated network architecture has developed based on the emerging Constellation requirements for Orion missions. The architecture, as presented in this paper, addresses the early Orion missions to the ISS with communication, navigation, and network services over five phases of a mission: pre-launch, launch from T0 to T+6.5 min, launch from T+6.5 min to 12 min, in LEO for rendezvous and docking with ISS, and return to Earth. The network of networks that supports the mission during each of these phases and the concepts of operations during those phases are developed as a high level operational concepts graphic called OV-1, an architecture diagram type described in the Department of Defense Architecture Framework (DoDAF). Additional operational views on organizational relationships (OV-4), operational activities (OV-5), and operational node connectivity (OV-2) are also discussed. The system interfaces view (SV-1) that provides the communication and navigation services to Orion is also included and described. The challenges of architecting integrated network architecture for the NASA Orion missions are highlighted.

Bhasin, Kul B.↗

Mission Reliability Estimation for Repairable Robot Teams

A mission reliability estimation method has been designed to translate mission requirements into choices of robot modules in order to configure a multi-robot team to have high reliability at minimal cost. In order to build cost-effective robot teams for long-term missions, one must be able to compare alternative design paradigms in a principled way by comparing the reliability of different robot models and robot team configurations. Core modules have been created including: a probabilistic module with reliability-cost characteristics, a method for combining the characteristics of multiple modules to determine an overall reliability-cost characteristic, and a method for the generation of legitimate module combinations based on mission specifications and the selection of the best of the resulting combinations from a cost-reliability standpoint. The developed methodology can be used to predict the probability of a mission being completed, given information about the components used to build the robots, as well as information about the mission tasks. In the research for this innovation, sample robot missions were examined and compared to the performance of robot teams with different numbers of robots and different numbers of spare components. Data that a mission designer would need was factored in, such as whether it would be better to have a spare robot versus an equivalent number of spare parts, or if mission cost can be reduced while maintaining reliability using spares. This analytical model was applied to an example robot mission, examining the cost-reliability tradeoffs among different team configurations. Particularly scrutinized were teams using either redundancy (spare robots) or repairability (spare components). Using conservative estimates of the cost-reliability relationship, results show that it is possible to significantly reduce the cost of a robotic mission by using cheaper, lower-reliability components and providing spares. This suggests that the current design paradigm of building a minimal number of highly robust robots may not be the best way to design robots for extended missions.

Trebi-Ollennu, Ashitey↗