Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Missions”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

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

At least 1,081 records · Page 60
All sourcesNASA NTRSDOE OSTI
NASA NTRS2014

An Analysis of Green Propulsion Applied to NASA Missions

The advantages of green propulsion for five mission classes are examined, including a Low Earth Orbit (LEO) mission (GPM), a Geosynchronous Earth Orbit (GEO) mission (SDO), a High Earth Orbit (HEO) mission (MMS), a lunar mission (LRO), and a planetary mission (MAVEN). The propellant mass benefits are considered for all five missions, as well as the effects on the tanks, propellant loading, thruster throughput, thermal considerations, and range requirements for both the AF-M315E and LMP-103S propellants.

Pocket Propulsion↗
NASA NTRS2012

NASA's Solar Dynamics Observatory (SDO): A Systems Approach to a Complex Mission

The Solar Dynamics Observatory (SDO) includes three advanced instruments, massive science data volume, stringent science data completeness requirements, and a custom ground station to meet mission demands. The strict instrument science requirements imposed a number of challenging drivers on the overall mission system design, leading the SDO team to adopt an integrated systems engineering presence across all aspects of the mission to ensure that mission science requirements would be met. Key strategies were devised to address these system level drivers and mitigate identified threats to mission success. The global systems engineering team approach ensured that key drivers and risk areas were rigorously addressed through all phases of the mission, leading to the successful SDO launch and on-orbit operation. Since launch, SDO's on-orbit performance has met all mission science requirements and enabled groundbreaking science observations, expanding our understanding of the Sun and its dynamic processes.

systems engineering↗
NASA NTRS2014

RS-34 Phoenix In-Space Propulsion System Applied to Active Debris Removal Mission

In-space propulsion is a high percentage of the cost when considering Active Debris Removal mission. For this reason it is desired to research if existing designs with slight modification would meet mission requirements to aid in reducing cost of the overall mission. Such a system capable of rendezvous, close proximity operations, and de-orbit of Envisat class resident space objects has been identified in the existing RS-34 Phoenix. RS-34 propulsion system is a remaining asset from the de-commissioned United States Air Force Peacekeeper program; specifically the pressure-fed storable bi-propellant Stage IV Post Boost Propulsion System. The National Aeronautics and Space Administration (NASA) Marshall Space Flight Center (MSFC) gained experience with the RS-34 propulsion system on the successful Ares I-X flight test program flown in the Ares I-X Roll control system (RoCS). The heritage hardware proved extremely robust and reliable and sparked interest for further utilization on other potential in-space applications. Subsequently, MSFC has obtained permission from the USAF to obtain all the remaining RS-34 stages for re-use opportunities. The MSFC Advanced Concepts Office (ACO) was commissioned to lead a study for evaluation of the Rocketdyne produced RS-34 propulsion system as it applies to an active debris removal design reference mission for resident space object targets including Envisat. Originally designed, the RS-34 Phoenix provided in-space six-degrees-of freedom operational maneuvering to deploy payloads at multiple orbital locations. The RS-34 Concept Study lead by sought to further understand application for a similar orbital debris design reference mission to provide propulsive capability for rendezvous, close proximity operations to support the capture phase of the mission, and deorbit of single or multiple large class resident space objects. Multiple configurations varying the degree of modification were identified to trade for dry mass optimization and propellant load. The results of the RS-34 Phoenix Concept Study show that the system is technically sufficient to successfully support all of the missions to rendezvous, capture, and de-orbit targets including Envisat and Hubble Space Telescope. The results and benefits of the RS-34 Orbital Debris Application Concept Study are presented in this paper.

Esther, Elizabeth A.↗
NASA NTRS2014

Virtualization - A Key Cost Saver in NASA Multi-Mission Ground System Architecture

With science team budgets being slashed, and a lack of adequate facilities for science payload teams to operate their instruments, there is a strong need for innovative new ground systems that are able to provide necessary levels of capability processing power, system availability and redundancy while maintaining a small footprint in terms of physical space, power utilization and cooling.The ground system architecture being presented is based off of heritage from several other projects currently in development or operations at Goddard, but was designed and built specifically to meet the needs of the Science and Planetary Operations Control Center (SPOCC) as a low-cost payload command, control, planning and analysis operations center. However, this SPOCC architecture was designed to be generic enough to be re-used partially or in whole by other labs and missions (since its inception that has already happened in several cases!)The SPOCC architecture leverages a highly available VMware-based virtualization cluster with shared SAS Direct-Attached Storage (DAS) to provide an extremely high-performing, low-power-utilization and small-footprint compute environment that provides Virtual Machine resources shared among the various tenant missions in the SPOCC. The storage is also expandable, allowing future missions to chain up to 7 additional 2U chassis of storage at an extremely competitive cost if they require additional archive or virtual machine storage space.The software architecture provides a fully-redundant GMSEC-based message bus architecture based on the ActiveMQ middleware to track all health and safety status within the SPOCC ground system. All virtual machines utilize the GMSEC system agents to report system host health over the GMSEC bus, and spacecraft payload health is monitored using the Hammers Integrated Test and Operations System (ITOS) Galaxy Telemetry and Command (TC) system, which performs near-real-time limit checking and data processing on the downlinked data stream and injects messages into the GMSEC bus that are monitored to automatically page the on-call operator or Systems Administrator (SA) when an off-nominal condition is detected. This architecture, like the LTSP thin clients, are shared across all tenant missions.Other required IT security controls are implemented at the ground system level, including physical access controls, logical system-level authentication authorization management, auditing and reporting, network management and a NIST 800-53 FISMA-Moderate IT Security plan Risk Assessment Contingency Plan, helping multiple missions share the cost of compliance with agency-mandated directives.The SPOCC architecture provides science payload control centers and backup mission operations centers with a cost-effective, standardized approach to virtualizing and monitoring resources that were traditionally multiple racks full of physical machines. The increased agility in deploying new virtual systems and thin client workstations can provide significant savings in personnel costs for maintaining the ground system. The cost savings in procurement, power, rack footprint and cooling as well as the shared multi-mission design greatly reduces upfront cost for missions moving into the facility. Overall, the authors hope that this architecture will become a model for how future NASA operations centers are constructed!

Ground System Architecture↗
NASA NTRS2013

The Single Habitat Module Concept for Exploration - Mission Planning and Mass Estimates

The Single Habitat Module (SHM) concept approach to the infrastructure and conduct of exploration missions combines many new promising technologies with a central concept of mission architectures that use a single habitat module for all phases of an exploration mission. Integrating mission elements near Earth and fully fueling them prior to departure of the vicinity of Earth provides the capability of using the single habitat both in transit to/from an exploration destination and while exploring the destination. The concept employs the capability to return the habitat and interplanetary propulsion system to Earth vicinity so that those elements can be reused on subsequent exploration missions. This paper provides an overview of the SHM concept and the advantages it provides. The paper also provides a summary of calculations of the mass of the Habitat Propulsion System (HPS) needed to get the habitat from low-Mars orbit (LMO) to the surface and back to LMO, and an overview of trajectory and mission mass assessments related to use of a high specific impulse space-based propulsion system. Those calculations led to the conclusion that the SHM concept results in low total mass required and streamlines mission operations to explore Mars (or other exploration destinations).

Chambliss, Joe↗
NASA NTRS2014

Asteroid Redirect Mission Concept: A Bold Approach for Utilizing Space Resources

The utilization of natural resources from asteroids is an idea that is older than the Space Age. The technologies are now available to transform this endeavour from an idea into reality. The Asteroid Redirect Mission (ARM) is a mission concept which includes the goal of robotically returning a small Near-Earth Asteroid (NEA) or a multi-ton boulder from a large NEA to cislunar space in the mid 2020's using an advanced Solar Electric Propulsion (SEP) vehicle and currently available technologies. The paradigm shift enabled by the ARM concept would allow in-situ resource utilization (ISRU) to be used at the human mission departure location (i.e., cislunar space) versus exclusively at the deep-space mission destination. This approach drastically reduces the barriers associated with utilizing ISRU for human deep-space missions. The successful testing of ISRU techniques and associated equipment could enable large-scale commercial ISRU operations to become a reality and enable a future space-based economy utilizing processed asteroidal materials. This paper provides an overview of the ARM concept and discusses the mission objectives, key technologies, and capabilities associated with the mission, as well as how the ARM and associated operations would benefit humanity's quest for the exploration and settlement of space.

Mazanek, Daniel D.↗
NASA NTRS2011

The Ganymede Interior Structure, and Magnetosphere Observer (GISMO) Mission Concept

The NASA Planetary Science Summer School (PSSS) at JPL offers graduate students and young professionals a unique opportunity to learn about the mission design process. Program participants select and design a mission based on a recent NASA Science Mission Directorate Announcement of Opportunity (AO). Starting with the AO, in this case the 2009 New Frontiers AO, participants generate a set of science goals and develop a early mission concept to accomplish those goals within the constraints provided. As part of the 2010 NASA PSSS, the Ganymede Interior, Surface, and Magnetosphere Observer (GISMO) team developed a preliminary satellite design for a science mission to Jupiter's moon Ganymede. The science goals for this design focused on studying the icy moon's magnetosphere, internal structure, surface composition, geological processes, and atmosphere. By the completion of the summer school an instrument payload was selected and the necessary mission requirements were developed to deliver a spacecraft to Ganymede that would accomplish the defined science goals. This poster will discuss those science goals, the proposed spacecraft and the proposed mission design of this New Frontiers class Ganymede observer.

radar sounder↗
NASA NTRS2013

Human and Robotic Space Mission Use Cases for High-Performance Spaceflight Computing

Spaceflight computing is a key resource in NASA space missions and a core determining factor of spacecraft capability, with ripple effects throughout the spacecraft, end-to-end system, and mission. Onboard computing can be aptly viewed as a "technology multiplier" in that advances provide direct dramatic improvements in flight functions and capabilities across the NASA mission classes, and enable new flight capabilities and mission scenarios, increasing science and exploration return. Space-qualified computing technology, however, has not advanced significantly in well over ten years and the current state of the practice fails to meet the near- to mid-term needs of NASA missions. Recognizing this gap, the NASA Game Changing Development Program (GCDP), under the auspices of the NASA Space Technology Mission Directorate, commissioned a study on space-based computing needs, looking out 15-20 years. The study resulted in a recommendation to pursue high-performance spaceflight computing (HPSC) for next-generation missions, and a decision to partner with the Air Force Research Lab (AFRL) in this development.

use cases↗
NASA NTRS2012

Nano-Satellite Secondary Spacecraft on Deep Space Missions

NanoSat technology has opened Earth orbit to extremely low-cost science missions through a common interface that provides greater launch accessibility. They have also been used on interplanetary missions, but these missions have used one-off components and architectures so that the return on investment has been limited. A natural question is the role that CubeSat-derived NanoSats could play to increase the science return of deep space missions. We do not consider single instrument nano-satellites as likely to complete entire Discovery-class missions alone,but believe that nano-satellites could augment larger missions to significantly increase science return. The key advantages offered by these mini-spacecrafts over previous planetary probes is the common availability of advanced subsystems that open the door to a large variety of science experiments, including new guidance, navigation and control capabilities. In this paper, multiple NanoSat science applications are investigated, primarily for high risk/high return science areas. We also address the significant challenges and questions that remain as obstacles to the use of nano-satellites in deep space missions. Finally, we provide some thoughts on a development roadmap toward interplanetary usage of NanoSpacecraft.

Klesh, Andrew T.↗
NASA NTRS2010

MOS 2.0: The Next Generation in Mission Operations Systems

A Mission Operations System (MOS) or Ground System constitutes that portion of an overall space mission Enterprise that resides here on Earth. Over the past two decades, technological innovations in computing and software technologies have allowed an MOS to support ever more complex missions while consuming a decreasing fraction of Project development budgets. Despite (or perhaps, because of) such successes, it is routine to hear concerns about the cost of MOS development. At the same time, demand continues for Ground Systems which will plan more spacecraft activities with fewer commanding errors, provide scientists and engineers with more autonomous functionality, process and manage larger and more complex data more quickly, all while requiring fewer people to develop, deploy, operate and maintain them. One successful approach to such concerns over this period is a multimission approach, based on the reuse of portions (most often software) developed and used in previous missions. The Advanced Multi-Mission Operations System (AMMOS), developed for deep-space science missions, is one successful example of such an approach. Like many computing-intensive systems, it has grown up in a near-organic fashion from a relatively simple set of tools into a complexly interrelated set of capabilities. Such systems, like a city lacking any concept of urban planning, can and will grow in ways that are neither efficient nor particularly easy to sustain. To meet the growing demands and unyielding constraints placed on ground systems, a new approach is necessary. Under the aegis of a multi-year effort to revitalize the AMMOS's multimission operations capabilities, we are utilizing modern practices in systems architecting and model-based engineering to create the next step in Ground Systems: MOS 2.0. In this paper we outline our work (ongoing and planned) to architect and design a multimission MOS 2.0, describe our goals and measureable objectives, and discuss some of the benefits that this top-down, architectural approach holds for creating a more flexible and capable MOS for Missions while holding the line on cost.

ground systems↗
NASA NTRS2016

Proving Ground Potential Mission and Flight Test Objectives and Near Term Architectures

NASA is developing a Pioneering Space Strategy to expand human and robotic presence further into the solar system, not just to explore and visit, but to stay. NASA's strategy is designed to meet technical and non-technical challenges, leverage current and near-term activities, and lead to a future where humans can work, learn, operate, and thrive safely in space for an extended, and eventually indefinite, period of time. An important aspect of this strategy is the implementation of proving ground activities needed to ensure confidence in both Mars systems and deep space operations prior to embarking on the journey to the Mars. As part of the proving ground development, NASA is assessing potential mission concepts that could validate the required capabilities needed to expand human presence into the solar system. The first step identified in the proving ground is to establish human presence in the cis-lunar vicinity to enable development and testing of systems and operations required to land humans on Mars and to reach other deep space destinations. These capabilities may also be leveraged to support potential commercial and international objectives for Lunar Surface missions. This paper will discuss a series of potential proving ground mission and flight test objectives that support NASA's journey to Mars and can be leveraged for commercial and international goals. The paper will discuss how early missions will begin to satisfy these objectives, including extensibility and applicability to Mars. The initial capability provided by the launch vehicle will be described as well as planned upgrades required to support longer and more complex missions. Potential architectures and mission concepts will be examined as options to satisfy proving ground objectives. In addition, these architectures will be assessed on commercial and international participation opportunities and on how well they develop capabilities and operations applicable to Mars vicinity missions.

Smith, R. Marshall↗
NASA NTRS2008

Orbit Control Operations for the Cassini-Huygens Mission

The Cassini-Huygens spacecraft was launched in 1997 as an international and collaborative mission to study Saturn and its many moons. After a seven-year cruise, Cassini began orbiting Saturn for a four- year tour. This tour consists of 157 planned maneuvers, and their back-up locations, designed to target 52 encounters, mostly of Saturn's largest moon Titan. One of the mission's first activities was to release the Huygens probe to Titan in December 2004. Currently in its last year of the prime mission, Cassini-Huygens continues to obtain valuable data on Saturn, Titan, and Saturn's other satellites. Return of this information is in large part due to a healthy spacecraft and successful navigation. A two-year extended mission, beginning July 2008, will offer the opportunity to continue science activities. With a demanding navigation schedule that compares with the prime tour, the Cassini Navigation team relies on operations procedures developed during the prime mission to carry-out the extended mission objectives. Current processes for orbit control operations evolved from the primary navigational requirement of staying close to predetermined targeting conditions according to Cassini science sequence planning. The reference trajectory is comprised of flyby conditions to be accomplished at minimal propellant cost. Control of the planned reference trajectory orbit, and any trajectory updates, is achieved with the execution of Orbit Trim Maneuvers (OTMs). The procedures for designing, processing, and analyzing OTMs during Cassini operations is presented. First, a brief overview of the Cassini-Huygens Mission is given, followed by a general description of navigation. Orbit control and maneuver execution methods are defined, along with an outline of the orbit control staffing and operations philosophy. Finally, an example schedule of orbit control operations is shown.

navigation↗
NASA NTRS2015

Crew Transportation System Design Reference Missions

Contains summaries of potential design reference mission goals for systems to transport humans to andfrom low Earth orbit (LEO) for the Commercial Crew Program. The purpose of this document is to describe Design Reference Missions (DRMs) representative of the end-to-end Crew Transportation System (CTS) framework envisioned to successfully execute commercial crew transportation to orbital destinations. The initial CTS architecture will likely be optimized to support NASA crew and NASA-sponsored crew rotation missions to the ISS, but consideration may be given in this design phase to allow for modifications in order to accomplish other commercial missions in the future. With the exception of NASA’s mission to the ISS, the remaining commercial DRMs are notional. Any decision to design or scar the CTS for these additional non-NASA missions is completely up to the Commercial Provider. As NASA’s mission needs evolve over time, this document will be periodically updated to reflect those needs.

potential design reference↗
NASA NTRS2015

Big Software for SmallSats: Adapting CFS to CubeSat Missions

Expanding capabilities and mission objectives for SmallSats and CubeSats is driving the need for reliable, reusable, and robust flight software. While missions are becoming more complicated and the scientific goals more ambitious, the level of acceptable risk has decreased. Design challenges are further compounded by budget and schedule constraints that have not kept pace. NASA's Core Flight Software System (cFS) is an open source solution which enables teams to build flagship satellite level flight software within a CubeSat schedule and budget. NASA originally developed cFS to reduce mission and schedule risk for flagship satellite missions by increasing code reuse and reliability. The Lunar Reconnaissance Orbiter, which launched in 2009, was the first of a growing list of Class B rated missions to use cFS. Large parts of cFS are now open source, which has spurred adoption outside of NASA. This paper reports on the experiences of two teams using cFS for current CubeSat missions. The performance overheads of cFS are quantified, and the reusability of code between missions is discussed. The analysis shows that cFS is well suited to use on CubeSats and demonstrates the portability and modularity of cFS code.

Open Source↗
NASA NTRS2016

Post-Flight Back Pain Following International Space Station Missions: Evaluation of Spaceflight Risk Factors

INTRODUCTION Back pain during spaceflight has often been attributed to the lengthening of the spinal column due to the absence of gravity during both short and long-duration missions. Upon landing and re-adaptation to gravity, the spinal column reverts back to its original length thereby causing some individuals to experience pain and muscular spasms, while others experience no ill effects. With International Space Station (ISS) missions, cases of back pain and injury are more common post-flight, but little is known about the potential risk factors. Thus, the purpose of this project was to perform an initial evaluation of reported post-flight back pain and injury cases to relevant spaceflight risk factors in United States astronauts that have completed an ISS mission. METHODS All US astronauts who completed an ISS mission between Expeditions (EXP) 1 and 41 (2000-2015) were included in this evaluation. Forty-five astronauts (36 males and 9 females) completed 50 ISS missions during the study time period, as 5 astronauts completed 2 ISS missions. Researchers queried medical records of the 45 astronauts for occurrences of back pain and injury. A case was defined as any reported event of back pain or injury to the cervical, thoracic, lumbar, sacral, or coccyx spine regions. Data sources for the cases included the Flight Medicine Clinic's electronic medical record; Astronaut Strength, Conditioning and Rehabilitation electronic documentation; the Private Medical Conference tool; and the Space Medicine Operations Team records. Post-flight cases were classified as an early case if reported within 45 days of landing (R + 45) or a late case if reported from R + 46 to R + 365 days after landing (R + 1y). Risk factors in the astronaut population for back pain include age, sex, prior military service, and prior history of back pain. Additionally, spaceflight specific risk factors such as type of landing vehicle and onboard exercise countermeasures were included to evaluate their contribution to post-flight cases. Prior history of back pain included back pain recorded in the medical record within 3 years prior to launch. Landing vehicle was included in the model to discern if more astronauts experienced back pain or injury following a Shuttle or Soyuz landing. Onboard exercise countermeasures were noted for those astronauts who had a mission following 2009 deployment of the Advanced Resistive Exercise Device (aRED) (EXP 19 to 41). T-test and chi-squared tests were performed to evaluate the association between each individual risk factor and post-flight case. Logistic regression was used to evaluate the combined contribution of all the risk factors on post-flight cases. Separate models were calculated for cases reported by R + 45 and R + 1y. RESULTS During the study time period, there were 13 post-flight cases reported by R + 45 and an additional 5 reported by R + 1y. Most of these cases have been reported since EXP 19 with 10 cases by R + 45 and 4 by R + 1y. Individual risk factors of age, sex, landing vehicle, and prior military service were not significantly associated with post-flight cases identified at R + 45 or R + 1y (p greater than 0.05). Having back pain or injury within 3 years prior to launch significantly increased the likelihood of becoming a case by R + 1y (p = 0.041), but not at R+45 (p=0.204). Additionally, astronauts who experienced onboard exercise countermeasures that included aRED had a significantly increased risk of becoming a case at R + 45 (p = 0.024) and R + 1y (p=0.003). Multiple logistic regression evaluating all the risk factors for cases identified no significant risk factors at either the R + 45 or R + 1y time period (p greater than 0.05). Overall model fit was poor for both the R + 45 (R(exp 2) = 0.132) and R + 1y (R(exp 2) = 0.186) cases showing that there are risk factors not represented in our model. CONCLUSIONS Regardless of cause, post-flight cases are reported more often since aRED was deployed in 2009. This may reflect improved documentation or unidentified risk factors. No spaceflight risk factor explains the data fully. Post-flight cases are probably due to multi-faceted factors that are not easily elucidated in the medical data.

Laughlin, M. S.↗
NASA NTRS2014

The Cassini Solstice Mission: Streamlining Operations by Sequencing with PIEs

The Cassini Solstice Mission (CSM) is the second extended mission phase of the highly successful Cassini/Huygens mission to Saturn. Conducted at a much-reduced funding level, operations for the CSM have been streamlined and simplified significantly. Integration of the science timeline, which involves allocating observation time in a balanced manner to each of the five different science disciplines (with representatives from the twelve different science instruments), has long been a labor-intensive endeavor. Lessons learned from the prime mission (2004-2008) and first extended mission (Equinox mission, 2008-2010) were utilized to design a new process involving PIEs (Pre-Integrated Events) to ensure the highest priority observations for each discipline could be accomplished despite reduced work force and overall simplification of processes. Discipline-level PIE lists were managed by the Science Planning team and graphically mapped to aid timeline deconfliction meetings prior to assigning discrete segments of time to the various disciplines. Periapse segments are generally discipline-focused, with the exception of a handful of PIEs. In addition to all PIEs being documented in a spreadsheet, allocated out-of-discipline PIEs were entered into the Cassini Information Management System (CIMS) well in advance of timeline integration. The disciplines were then free to work the rest of the timeline internally, without the need for frequent interaction, debate, and negotiation with representatives from other disciplines. As a result, the number of integration meetings has been cut back extensively, freeing up workforce. The sequence implementation process was streamlined as well, combining two previous processes (and teams) into one. The new Sequence Implementation Process (SIP) schedules 22 weeks to build each 10-week-long sequence, and only 3 sequence processes overlap. This differs significantly from prime mission during which 5-week-long sequences were built in 24 weeks, with 6 overlapping processes.

Vandermey, Nancy↗
NASA NTRS2012

Printable Spacecraft: Flexible Electronic Platforms for NASA Missions

Atmospheric confetti. Inchworm crawlers. Blankets of ground penetrating radar. These are some of the unique mission concepts which could be enabled by a printable spacecraft. Printed electronics technology offers enormous potential to transform the way NASA builds spacecraft. A printed spacecraft's low mass, volume and cost offer dramatic potential impacts to many missions. Network missions could increase from a few discrete measurements to tens of thousands of platforms improving areal density and system reliability. Printed platforms could be added to any prime mission as a low-cost, minimum resource secondary payload to augment the science return. For a small fraction of the mass and cost of a traditional lander, a Europa flagship mission might carry experimental printed surface platforms. An Enceladus Explorer could carry feather-light printed platforms to release into volcanic plumes to measure composition and impact energies. The ability to print circuits directly onto a variety of surfaces, opens the possibility of multi-functional structures and membranes such as "smart" solar sails and balloons. The inherent flexibility of a printed platform allows for in-situ re-configurability for aerodynamic control or mobility. Engineering telemetry of wheel/soil interactions are possible with a conformal printed sensor tape fit around a rover wheel. Environmental time history within a sample return canister could be recorded with a printed sensor array that fits flush to the interior of the canister. Phase One of the NIAC task entitled "Printable Spacecraft" investigated the viability of printed electronics technologies for creating multi-functional spacecraft platforms. Mission concepts and architectures that could be enhanced or enabled with this technology were explored. This final report captures the results and conclusions of the Phase One study. First, the report presents the approach taken in conducting the study and a mapping of results against the proposed Phase One objectives. Then an overview of the general field of printed electronics is provided, including manufacturing approaches, commercial drivers, and the current state of integrated systems. The bulk of the report contains the results and findings of Phase One organized into four sections: a survey of components required for a printable spacecraft, technology roadmaps considerations, science mission and engineering applications, and potential risks and challenges of the technology.

Spacecraft↗
NASA NTRS2016

Implementing Effective Mission Systems Engineering Practices During Early Project Formulation Phases

Developing and implementing a plan for a NASA space mission can be a complicated process. The needs, goals, and objectives of any proposed mission or technology must be assessed early in the Project Life Cycle. The key to successful development of a space mission or flight project is the inclusion of systems engineering in early project formulation, namely during Pre-phase A, Phase A, and Phase B of the NASA Project Life Cycle. When a space mission or new technology is in pre-development, or "pre-Formulation", feasibility must be determined based on cost, schedule, and risk. Inclusion of system engineering during project formulation is key because in addition to assessing feasibility, design concepts are developed and alternatives to design concepts are evaluated. Lack of systems engineering involvement early in the project formulation can result in increased risks later in the implementation and operations phases of the project. One proven method for effective systems engineering practice during the pre-Formulation Phase is the use of a mission conceptual design or technology development laboratory, such as the Mission Design Lab (MDL) at NASA's Goddard Space Flight Center (GSFC). This paper will review the engineering process practiced routinely in the MDL for successful mission or project development during the pre-Formulation Phase.

Processes↗