Mission architecture
Explore the source record for details and available documents.
mission architecture project life cycle system eng↗
SEARCH · Search NASA
Results for “mission architecture project life cycle system engineer”
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.
Developing Systems Engineering Skills Through NASA Summer Intern Project
During the Formulation phases of the NASA Project Life Cycle, communication systems engineers are responsible for designing space communication links and analyzing their performance to ensure that the proposed communication architecture is capable of satisfying high-level mission requirements. Senior engineers with extensive experience in communications systems perform these activities. However, the increasing complexity of space systems coupled with the current shortage of communications systems engineers has led to an urgent need for expedited training of new systems engineers. A pilot program, in which college-bound high school and undergraduate students studying various engineering disciplines are immersed in NASA s systems engineering practices, was conceived out of this need. This rapid summerlong training approach is feasible because of the availability of advanced software and technology tools and the students inherent ability to operate such tools. During this pilot internship program, a team of college-level and recently-hired engineers configured and utilized various software applications in the design and analysis of communication links for a plausible lunar sortie mission. The approach taken was to first design the direct-to-Earth communication links for the lunar mission elements, then to design the links between lunar surface and lunar orbital elements. Based on the data obtained from these software applications, an integrated communication system design was realized and the students gained valuable systems engineering knowledge. This paper describes this approach to rapidly training college-bound high school and undergraduate engineering students from various disciplines in NASA s systems engineering practices and tools. A summary of the potential use of NASA s emerging systems engineering internship program in broader applications is also described.
Bhasin, Kul↗
Building Operations Efficiencies into NASA's Ares I Crew Launch Vehicle Design
The U.S. Vision for Space Exploration guides the National Aeronautics and Space Administration's (NASA's) challenging missions that expand humanity's boundaries and open new routes to the space frontier. With the Agency's commitment to complete the International Space Station (ISS) and to retire the venerable Space Shuttle by 2010, the NASA Administrator commissioned the Exploration Systems Architecture Study (ESAS) in 2005 to analyze options for safe, simple, cost-efficient launch solutions that could deliver human-rated space transportation capabilities in a timely manner within fixed budget guidelines. The Exploration Launch Projects (ELP) Office, chartered by the Constellation Program in October 2005, has been conducting systems engineering studies and business planning to successively refine the design configurations and better align vehicle concepts with customer and stakeholder requirements, such as significantly reduced life-cycle costs. As the Agency begins the process of replacing the Shuttle with a new generation of spacecraft destined for missions beyond low-Earth orbit to the Moon and Mars, NASA is designing the follow-on crew and cargo launch systems for maximum operational efficiencies. To sustain the long-term exploration of space, it is imperative to reduce the $4 billion NASA typically spends on space transportation each year. This paper gives toplevel information about how the follow-on Ares I Crew Launch Vehicle (CLV) is being designed for improved safety and reliability, coupled with reduced operations costs. These methods include carefully developing operational requirements; conducting operability design and analysis; using the latest information technology tools to design and simulate the vehicle; and developing a learning culture across the workforce to ensure a smooth transition between Space Shuttle operations and Ares vehicle development.
Dumbacher, Daniel L.↗
Building Operations Efficiencies into NASA's Ares I Crew Launch Vehicle Design
The U.S. Vision for Space Exploration guides the National Aeronautics and Space Administration s (NASA's) challenging missions that expand humanity s boundaries and open new routes to the space frontier. With the Agency's commitment to complete the International Space Station (ISS) and to retire the venerable Space Shuttle by 2010, the NASA Administrator commissioned the Exploration Systems Architecture Study (ESAS) in mid 2005 to analyze options for safe, simple, cost-efficient launch solutions that could deliver human-rated space transportation capabilities in a timely manner within fixed budget guidelines. The Exploration Launch Projects Office, chartered in October 2005, has been conducting systems engineering studies and business planning over the past few months to successively refine the design configurations and better align vehicle concepts with customer and stakeholder requirements, such as significantly reduced life-cycle costs. As the Agency begins the process of replacing the Shuttle with a new generation of spacecraft destined for missions beyond low-Earth orbit to the Moon and Mars, NASA is designing the follow-on crew and cargo launch systems for maximum operational efficiencies. To sustain the long-term exploration of space, it is imperative to reduce the $4.5 billion NASA typically spends on space transportation each year. This paper gives top-level information about how the follow-on Ares I Crew Launch Vehicle (CLV) is being designed for improved safety and reliability, coupled with reduced operations costs.
Dumbacher, Daniel↗
Life Support Goals Including High Closure and Low Mass Should Be Reconsidered Using Systems Analysis
Recycling space life support systems have been built and tested since the 1960s and have operated on the International Space Station (ISS) since the mid 2000s. The development of space life support has been guided by a general consensus focused on two important related goals, increasing system closure and reducing launch mass. High closure is achieved by recycling crew waste products such as carbon dioxide and condensed humidity. Recycling directly reduces the mass of oxygen and water for the crew that must be launched from Earth. The launch mass of life support can be further reduced by developing recycling systems with lower hardware mass and reduced power. The life support consensus has also favored using biological systems. The goal of increasing closure using biological systems suggests that food should be grown in space and that biological processors be used for air, water, and waste recycling. The goal of reducing launch mass led to use of Equivalent System Mass (ESM) in life support advocacy and technology selection. The recent consensus assumes that the recycling systems architecture developed in the 1960s and implemented on ISS will be used on all future long missions. NASA and other project organizations use the standard systems engineering process to guide hardware development. The systems process was used to develop ISS life support, but it has been less emphasized in planning future systems for the moon and Mars. Since such missions are far in the future, there has been less immediate need for systems engineering analysis to consider trade-offs, reliability, and Life Cycle Cost (LCC). Preliminary systems analysis suggests that the life support consensus concepts should be revised to reflect systems engineering requirements.
systems analysis↗
Low Impact Docking System (LIDS)
Since 1996, NASA has been developing a docking system that will simplify operations and reduce risks associated with mating spacecraft. This effort has focused on developing and testing an original, reconfigurable, active, closed-loop, force-feedback controlled docking system using modern technologies. The primary objective of this effort has been to design a docking interface that is tunable to the unique performance requirements for all types of mating operations (i.e. docking and berthing, autonomous and piloted rendezvous, and in-space assembly of vehicles, modules and structures). The docking system must also support the transfer of crew, cargo, power, fluid, and data. As a result of the past 10 years of docking system advancement, the Low Impact Docking System or LIDS was developed. The current LIDS design incorporates the lessons learned and development experiences from both previous and existing docking systems. LIDS feasibility was established through multiple iterations of prototype hardware development and testing. Benefits of LIDS include safe, low impact mating operations, more effective and flexible mission implementation with an anytime/anywhere mating capability, system level redundancy, and a more affordable and sustainable mission architecture with reduced mission and life cycle costs. In 1996 the LIDS project, then known as the Advanced Docking Berthing System (ADBS) project, launched a four year developmental period. At the end of the four years, the team had built a prototype of the soft-capture hardware and verified the control system that will be used to control the soft-capture system. In 2001, the LIDS team was tasked to work with the X- 38 Crew Return Vehicle (CRV) project and build its first Engineering Development Unit (EDU).
LaBauve, Tobie E.↗
NASA's Space Launch System: Momentum Builds Toward First Launch
NASA's Space Launch System (SLS) is gaining momentum toward the first launch of a new exploration-class heavy lift launch vehicle for international exploration and science initiatives. The SLS comprises an architecture that begins with a vehicle capable of launching 70 metric tons (t) into low Earth orbit. It will launch the Orion Multi-Purpose Crew Vehicle (MPCV) on its first autonomous flight beyond the Moon and back in December 2017. Its first crewed flight follows in 2021. SLS can evolve to a130-t lift capability and serve as a baseline for numerous robotic and human missions ranging from a Mars sample return to delivering the first astronauts to explore another planet. The SLS Program formally transitioned from the formulation phase to implementation with the successful completion of the rigorous Key Decision Point C review in 2014. As a result, the Agency authorized the Program to move forward to Critical Design Review, scheduled for 2015. In the NASA project life cycle process, SLS has completed 50 percent of its major milestones toward first flight. Every SLS element manufactured development hardware for testing over the past year. Accomplishments during 2013/2014 included manufacture of core stage test articles, preparations for qualification testing the solid rocket boosters and the RS-25 main engines, and shipment of the first flight hardware in preparation for the Exploration Flight Test-1 (EFT-1) in 2014. SLS was conceived with the goals of safety, affordability, and sustainability, while also providing unprecedented capability for human exploration and scientific discovery beyond Earth orbit. In an environment of economic challenges, the SLS team continues to meet ambitious budget and schedule targets through the studied use of hardware, infrastructure, and workforce investments the United States made in the last half century, while selectively using new technologies for design, manufacturing, and testing, as well as streamlined management approaches that have increased decision velocity and reduced associated costs. This paper will summarize recent SLS Program accomplishments, as well as the challenges and opportunities ahead for the most powerful and capable launch vehicle in history.
May, Todd A.↗
Life Cycle Systems Engineering Approach to NASA's 2nd Generation Reusable Launch Vehicle
The overall goal of the 2nd Generation RLV Program is to substantially reduce technical and business risks associated with developing a new class of reusable launch vehicles. NASA's specific goals are to improve the safety of a 2nd- generation system by 2 orders of magnitude - equivalent to a crew risk of 1 -in- 10,000 missions - and decrease the cost tenfold, to approximately $1,000 per pound of payload launched. Architecture definition is being conducted in parallel with the maturating of key technologies specifically identified to improve safety and reliability, while reducing operational costs. An architecture broadly includes an Earth-to-orbit reusable launch vehicle, on-orbit transfer vehicles and upper stages, mission planning, ground and flight operations, and support infrastructure, both on the ground and in orbit. The systems engineering approach ensures that the technologies developed - such as lightweight structures, long-life rocket engines, reliable crew escape, and robust thermal protection systems - will synergistically integrate into the optimum vehicle. Given a candidate architecture that possesses credible physical processes and realistic technology assumptions, the next set of analyses address the system's functionality across the spread of operational scenarios characterized by the design reference missions. The safety/reliability and cost/economics associated with operating the system will also be modeled and analyzed to answer the questions "How safe is it?" and "How much will it cost to acquire and operate?" The systems engineering review process factors in comprehensive budget estimates, detailed project schedules, and business and performance plans, against the goals of safety, reliability, and cost, in addition to overall technical feasibility. This approach forms the basis for investment decisions in the 2nd Generation RLV Program's risk-reduction activities. Through this process, NASA will continually refine its specialized needs and identify where Defense and commercial requirements overlap those of civil missions.
Thomas, Dale↗
Method for Tracking and Communicating Aggregate Risk Through the Use of Model-Based Systems Engineering (MBSE) Tools
Large, complex projects can identify a significant number and variety of risks, throughout the project life cycle. These risks are analyzed, mitigated, closed or accepted as independent uncertainties. Once closed or accepted, it is easy for projects to lose awareness of their impact. In reality, each of these risks contributes some amount to the overall risk posture of the project. The ability to track and effectively communicate this aggregate risk has represented a challenge to project management. There have been previous attempts to create a schema to communicate the aggregate effect of risks, without notable success. Most of these attempts have centered on some additive metric derived from the scoring of likelihood and consequence values. This, in and of itself, is a logical approach, but all too often the scores were then aggregated to a level where all context was lost. One weakness has been a lack of attempt to create linkages or logical groups of the risks upon which useful aggregation could then occur. The overall move to model-based (systems) engineering (MBSE) has opened up a vast frontier of opportunities to better integrate all project data. MBSE provides an underlying layer that links data items to each other. Objectives link to requirements, which then link to functions, functions to physical architecture items, and so on, as far down as projects want to model. While it started with a focus on modeling requirements based on things like use cases, efforts are now underway to integrate safety and mission assurance (S&MA) information and analyses, such as risks. This effort, called Model Based Mission Assurance (MBMA), is yielding models that are more useful and are a more accurate representations of the systems. MBSE models, with this ability to link related items, provide a new means of tracking and communicating aggregate risks. In the proposed method, risks are added into the models as distinct items, having attributes that communicate a scoring derived from the likelihood and consequence values as charted on the standard NASA 5x5 risk matrix. Like earlier efforts, each box in the 5x5 has an associated scoring, which may include both a current score and potential post-mitigation/control score. The risk items are then linked to elements of the model, such as system objectives/goals, requirements, functions, or physical architecture items, with "Risk to" relationships. These risks will then be communicated by use of reports generated from the model, detailing all risks and/or hazards linked to model elements. These reports can include aggregate impacts, including a current scoring and potential future state scoring based on the planned mitigations and/or controls. These reports will show all risks, open, accepted, and closed, linked to project objectives or requirements. When run as part of an upcoming risk acceptance discussion, these reports will serve to remind the team of all previous risks that relate to the effected portion of the system. When included as part of periodic program or project reviews, risk reviews, and safety reviews, this method can improve the overall understanding of the system's true risk posture. This proposed method takes full advantage of the advances that modern modeling techniques provide, with a minimal investment of additional time. Utilizing the model environment also enables a near constant access to current state of aggregate risks.
model based mission assurance↗
Demonstrating the Performance Benefits of the Strutjet RBCC for Space Launch Architectures
The Rocket Based Combined Cycle (RBCC) engine synergistically combines the best elements of airbreathing and rocket propulsion to benefit a wide range of future reusable launch vehicles. Aerojet's Strutjet RBCC offers high I(sub sp) during mid-phase acceleration, and high thrust for boost and final ascent phases. The result is a relatively low gross weight vehicle with lower thrust requirements than comparable all-rocket solutions. Relative to combination propulsion systems, the integrated propulsive elements of the Strutjet reduce engine weight and complexity. In the recent NASA Highly Reusable Space Transportation (HRST) study, vehicles with RBCC-class engines were projected to have lower per flight operations costs than comparable rockets. The more benign operating environment of the RBCC engine primary rockets (2000 psi chamber pressure, lower internal temperatures, gas generator cycle) lead to longer service life, fewer maintenance actions, and increased reliability. Operations costs are typically the most significant contributor to life cycle costs. RBCC-powered vehicles lend themselves naturally to horizontal takeoff, which typically requires less thrust for a given gross vehicle weight when compared to an all-rocket-powered vehicle. The lower thrust requirements reduce engine size and/or quantity, reducing the n of ground personnel and facilities required to maintain the vehicle. The reduced sensitivity to mass fraction also allows the vehicle to be designed with higher margins for improved life and reliability. Because of its multi-mode ascent operation and ability to perform long cruise segments, the strutjet RBCC offers RLV designers a chance to create vehicles with an unprecedented level of mission flexibility. Features such as supersonic cruise, flyback, off-set launch, self-ferry, horizontal takeoff and landing, multi-base operation, and flexible aborts open up a broad range of potential revenue producing missions. The Strutjet can lead to low-cost vehicle designs in traditional areas such as LEO cargo delivery and ISS resupply, and also lead to economically attractive vehicles for small payload missions difficult to achieve with all-rocket solutions. The performance capability of the Strutjet RBCC has been demonstrated in all operating mod underfunding from NASA MSFC and Aerojet as a result of over 1000testsand over 13 years of continuous development-a significant resource investment in the Strutjet engine design.
Johnson, D.↗
Collaborative Systems Engineering in the Ascent Abort-2 Crew Module/Separation Ring Project
Generally speaking, systems engineering (SE) tool-sets face a dilemma balancing power and accessibility. High-powered SE tools (MagicDraw, Cradle, Core, etc.) tend to be specialized and are available only to highly trained Systems Engineers, and/or through the use of a 'back room' developer team making the output products available to the broader team. On the other hand, highly accessible tools (MS Word, Excel, etc.) do not have the power to implement SE in a rigorous manner. NASA has to test all aspects of the new human-rated Orion Multi-Purpose Crew Vehicle spacecraft prior to its first crewed mission. The test program includes uncrewed launch abort flight tests to demonstrate the capability to save the crew in the event that a launch failure occurs. Orion's second abort flight test will be a low-altitude flight test known as "Ascent Abort 2 (AA-2)." This test is currently scheduled to be carried out at Cape Canaveral Air Force Station's Space Launch Complex 46 (SLC-46) in Florida in 2019. NASA's in-house AA-2 Crew Module and Separation Ring (CSR) Team is producing the crew module and separation ring. Operating jointly as both an Advanced Exploration Systems (AES) Project and an Orion Project, the CSR project charter includes development of innovative, streamlined and generally more efficient practices for creation of flight hardware and software. One result of this tasking has been development of a collaborative and data-centric systems engineering environment within the team's shared web environment (Microsoft SharePoint). Through the use of built-in, 'out of the box capabilities' present in MS SharePoint, the CSR Systems Engineering team has created (with some limited developer support) a data-centric architecture for the project's SE implementation, including functional and interface analysis, requirements development and management, risk management, verification planning and management, test results, and end item management. Data elements are linked between data structures so as to define and control relationships between item types, link requirements to parents and children, and link tests to the requirements that they verify. The overall project team integration is increased by also linking SE content to project management content over the project life cycle, including team communication, action items, configuration management, decisional and meeting materials, and life cycle reviews. This presentation will provide an overview of the collaborative SE environment, showing how it provides the power for a number of SE tasks while still providing the accessibility and transparency to allow the full project team to collaborate and succeed. Given the project phase, we'll be able to present a nearly full lifecycle discussion, from concept through verification and approaching delivery.
Systems Engineering environments↗
NASA's Space Launch System: Moving Toward the Launch Pad
The National Aeronautics and Space Administration's (NASA's) Space Launch System (SLS) Program, managed at the Marshall Space Flight Center, is making progress toward delivering a new capability for human space flight and scientific missions beyond Earth orbit. Developed with the goals of safety, affordability, and sustainability in mind, the SLS rocket will launch the Orion Multi-Purpose Crew Vehicle (MPCV), equipment, supplies, and major science missions for exploration and discovery. Supporting Orion's first autonomous flight to lunar orbit and back in 2017 and its first crewed flight in 2021, the SLS will evolve into the most powerful launch vehicle ever flown, via an upgrade approach that will provide building blocks for future space exploration and development. NASA is working to develop this new capability in an austere economic climate, a fact which has inspired the SLS team to find innovative solutions to the challenges of designing, developing, fielding, and operating the largest rocket in history. This paper will summarize the planned capabilities of the vehicle, the progress the SLS program has made in the 2 years since the Agency formally announced its architecture in September 2011, and the path the program is following to reach the launch pad in 2017 and then to evolve the 70 metric ton (t) initial lift capability to 130-t lift capability. The paper will explain how, to meet the challenge of a flat funding curve, an architecture was chosen which combines the use and enhancement of legacy systems and technology with strategic new development projects that will evolve the capabilities of the launch vehicle. This approach reduces the time and cost of delivering the initial 70 t Block 1 vehicle, and reduces the number of parallel development investments required to deliver the evolved version of the vehicle. The paper will outline the milestones the program has already reached, from developmental milestones such as the manufacture of the first flight hardware and the record-breaking testing of the J-2X engine, to life-cycle milestones such as the vehicle's Preliminary Design Review. The paper will also discuss the remaining challenges in both delivering the 70 t vehicle and in evolving its capabilities to the 130 t vehicle, and how the program plans to accomplish these goals. As this paper will explain, SLS is making measurable progress toward becoming a global infrastructure asset for robotic and human scouts of all nations by harnessing business and technological innovations to deliver sustainable solutions for space exploration
Creech, Stephen D.↗
Integration of In-Situ Resource Utilization Into Lunar/Mars Exploration Through Field Analogs
The NASA project to develop In-Situ Resource Utilization (ISRU) technologies, in partnership with commercial and international collaborators, has achieved full system demonstrations of oxygen production using native regolith simulants. These demonstrations included robotic extraction of material from the terrain, sealed encapsulation of material in a pressurized reactor; chemical extraction of oxygen from the material in the form of water, and the electrolysis of water into oxygen and hydrogen for storage and reuse. These successes have provided growing confidence in the prospects of ISRU oxygen production as a credible source for critical mission consumables in preparation for and during crewed missions to the moon and other destinations. Other ISRU processes, especially relevant to early lunar exploration scenarios, have also been shown to be practical, including the extraction of subsurface volatiles, especially water, and the thermal processing of surface materials for civil engineering uses and for thermal energy storage. This paper describes these recent achievements and current NASA ISRU development and demonstration activity. The ability to extract and process resources at the site of exploration into useful products such as propellants, life support and power system consumables; and radiation and rocket exhaust plume debris shielding, known as In-Situ Resource Utilization or ISRU, has the potential to significantly reduce the launch mass, risk, and cost of robotic and human exploration of space. The incorporation of ISRU into missions can also significantly influence technology selection and system development in other areas such as power, life support, and propulsion. For example. the ability to extract or produce large amounts of oxygen and/or water in-situ could minimize the need to completely close life support air and water processing system cycles, change thermal and radiation protection of habitats, and influence propellant selection for ascent vehicles and surface propulsive hoppers. While concepts and even laboratory work on evaluating and developing ISRU techniques such as oxygen extraction from lunar regolith have been going on since before the Apollo 11 Moon landing, no ISRU system has ever flown in space, and only recently have ISRU technologies been developed at a scale and at a system level that is relevant to actual robotic and human mission applications. Because ISRU hardware and systems have never been demonstrated or utilized before on robotic or human missions, architecture and mission planners and surface system hardware developers are hesitant to rely on ISRU products and services that are critical to mission and system implementation success. To build confidence in ISRU systems for future missions and assess how ISRU systems can best influence and integrate with other surface system elements, NASA, with international partners, are performing analog field tests to understand how to take advantage of ISRU capabilities and benefits with the minimum of risk associated with introducing this game-changing approach to exploration. This paper will describe and review the results of four analog field tests (Moses Lake in 6/08, Mauna Kea in 11/08. Flagstaff in 9/09; and Mauna Kea in 1/10) that have begun the process of integrating ISRU into robotic and human exploration systems and missions, and propose future ISRU-related analog field test activities that can be performed in collaboration with international space agencies.
Sanders, Gerald B.↗