Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “lifecycle assessment”

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 37 records · Page 2

Cirrus Simulations of CRYSTAL-FACE 23 July 2002 Case

A key objective of the Cirrus Regional Study of Tropical Anvils and Cirrus Layers - Florida Area Cirrus Experiment (CRYSTAL-FACE) is to understand relationships between the properties of tropical convective cloud systems and the properties and lifecycle of the extended cirrus anvils they produce. We report here on a case study of 23 July 2002 where a sequence of convective storms over central Florida produced an extensive anvil outflow. Our approach is to use a suitably-initialized cloud-system simulation with MM5 to define initial conditions and time-dependent forcing for a simulation of anvil evolution using a two-dimensional fine-resolution (100 m) cirrus cloud model that explicitly accounts for details of cirrus microphysical development (bin or spectra model) and fully interactive radiative processes. The cirrus model follows Lin. Meteorological conditions and observations for the 23 July case are described in this volume. The goals of the present study are to evaluate how well we can simulate a cirrus anvil lifecycle, to evaluate the importance of various physical processes that operate within the anvil, and to evaluate the importance of environmental conditions in regulating anvil lifecycle. CRYSTAL-FACE produced a number of excellent case studies of anvil systems that will allow environmental factors, such as static stability or wind shear in the upper troposphere, to be examined. In the present study, we strive to assess the importance of propagating gravity waves, likely produced by the deep convection itself, and radiative processes, to anvil lifecycle and characteristics.

Starr, David↗

Applying Standard Independent Verification and Validation (IVV) Techniques Within an Agile Framework: Is There a Compatibility Issue?

Agile methods have gained wide acceptance over the past several years, to the point that they are now a standard management and execution approach for small-scale software development projects. While conventional Agile methods are not generally applicable to large multi-year and mission-critical systems, Agile hybrids are now being developed (such as SAFe) to exploit the productivity improvements of Agile while retaining the necessary process rigor and coordination needs of these projects. From the perspective of Independent Verification and Validation (IVV), however, the adoption of these hybrid Agile frameworks is becoming somewhat problematic. Hence, we find it prudent to question the compatibility of conventional IVV techniques with (hybrid) Agile practices.This paper documents our investigation of (a) relevant literature, (b) the modification and adoption of Agile frameworks to accommodate the development of large scale, mission critical systems, and (c) the compatibility of standard IVV techniques within hybrid Agile development frameworks. Specific to the latter, we found that the IVV methods employed within a hybrid Agile process can be divided into three groups: (1) early lifecycle IVV techniques that are fully compatible with the hybrid lifecycles, (2) IVV techniques that focus on tracing requirements, test objectives, etc. are somewhat incompatible, but can be tailored with a modest effort, and (3) IVV techniques involving an assessment requiring artifact completeness that are simply not compatible with hybrid Agile processes, e.g., those that assume complete requirement specification early in the development lifecycle.

Agile↗

Scoping, Tailoring, and Abstraction Refinement in Hazard Assessment Processes

Hazard assessment is an engineering activity that produces insight into which states of thing being engineered might be hazardous. In aviation contexts, it is often performed for certification credit at both the aircraft and system levels during the early design phase of the system’s lifecycle. However, novel aircraft paradigms such as urban air mobility (UAM)operations might either violate assumptions on which traditional aviation hazard assessment is based or simply possess attributes that would make other approaches more effective. In this paper, we define the key concepts under pinning hazard assessment and identify the limitations and assumptions inherent in hazard analysis. We analyze popular techniques to show how they embody these key concepts. We identify ways in which hazard assessment may be scoped and tailored to an application. And, using worked examples, we discuss how, where, and why such tailoring might be needed, especially in novel contexts.

aviation safety↗

Scoping, Tailoring, and Abstraction Refinement in the Hazard Assessment Process

Hazard assessment is an engineering activity that produces insight into which states of thing being engineered might be hazardous. In aviation contexts, it is often performed for certification credit at both the aircraft and system levels during the early design phase of the system’s lifecycle. However, novel aircraft paradigms such as urban air mobility (UAM) operations might either violate assumptions on which traditional aviation hazard assessment is based or simply possess attributes that would make other approaches more effective. In this paper, we define the key concepts underpinning hazard assessment and identify the limitations and assumptions inherent in hazard analysis. We analyze popular techniques to show how they embody these key concepts. We identify ways in which hazard assessment may be scoped and tailored to an application. And, using worked examples, we discuss how, where, and why such tailoring might be needed, especially in novel contexts.

Aviation Safety↗

Practical Application of PRA as an Integrated Design Tool for Space Systems

This paper presents the application of the first comprehensive Probabilistic Risk Assessment (PRA) during the design phase of a joint NASA/NOAA weather satellite program, Geostationary Operational Environmental Satellite Series R (GOES-R). GOES-R is the next generation weather satellite primarily to help understand the weather and help save human lives. PRA has been used at NASA for Human Space Flight for many years. PRA was initially adopted and implemented in the operational phase of manned space flight programs and more recently for the next generation human space systems. Since its first use at NASA, PRA has become recognized throughout the Agency as a method of assessing complex mission risks as part of an overall approach to assuring safety and mission success throughout project lifecycles. PRA is now included as a requirement during the design phase of both NASA next generation manned space vehicles as well as for high priority robotic missions. The influence of PRA on GOES-R design and operation concepts are discussed in detail. The GOES-R PRA is unique at NASA for its early implementation. It also represents a pioneering effort to integrate risks from both Spacecraft (SC) and Ground Segment (GS) to fully assess the probability of achieving mission objectives. PRA analysts were actively involved in system engineering and design engineering to ensure that a comprehensive set of technical risks were correctly identified and properly understood from a design and operations perspective. The analysis included an assessment of SC hardware and software, SC fault management system, GS hardware and software, common cause failures, human error, natural hazards, solar weather and infrastructure (such as network and telecommunications failures, fire). PRA findings directly resulted in design changes to reduce SC risk from micro-meteoroids. PRA results also led to design changes in several SC subsystems, e.g. propulsion, guidance, navigation and control (GNC), communications, mechanisms, and command and data handling (C&DH). The fault tree approach assisted in the development of the fault management system design. Human error analysis, which examined human response to failure, indicated areas where automation could reduce the overall probability of gaps in operation by half. In addition, the PRA brought to light many potential root causes of system disruptions, including earthquakes, inclement weather, solar storms, blackouts and other extreme conditions not considered in the typical reliability and availability analyses. Ultimately the PRA served to identify potential failures that, when mitigated, resulted in a more robust design, as well as to influence the program's concept of operations. The early and active integration of PRA with system and design engineering provided a well-managed approach for risk assessment that increased reliability and availability, optimized lifecyc1e costs, and unified the SC and GS developments.

Kalia, Prince↗

Software Requirements Analysis as Fault Predictor

Waiting until the integration and system test phase to discover errors leads to more costly rework than resolving those same errors earlier in the lifecycle. Costs increase even more significantly once a software system has become operational. WE can assess the quality of system requirements, but do little to correlate this information either to system assurance activities or long-term reliability projections - both of which remain unclear and anecdotal. Extending earlier work on requirements accomplished by the ARM tool, measuring requirements quality information against code complexity and test data for the same system may be used to predict specific software modules containing high impact or deeply embedded faults now escaping in operational systems. Such knowledge would lead to more effective and efficient test programs. It may enable insight into whether a program should be maintained or started over.

Wallace, Dolores↗

TMIS-design knowledge capture

The Boeing Advanced Technology Center is conducting research towards the goal of building a corporate memory facility that will provide techniques for capturing and using decision history and rationale throughout the lifecycle of a major NASA program. Currently, much of the information regarding decision alternatives and trade-offs made in the course of a major program development effort is not represented or retained in a way that permits computer-based reasoning over the lifecycle of the program. The loss of this information results in problems in tracing design alternatives to requirements, in assessing the impact of change in requirements, and in configuration management. To address these problems, we are studying the problem of building an intelligent active corporate memory facility which would provide for the capture of the requirements and standards of a program, analyze the design alternatives and trade-offs made over the program's lifetime, and examine relationships between requirements and design trade-offs.

Boose, John H.↗

A Simple Model of Global Aerosol Indirect Effects

Most estimates of the global mean indirect effect of anthropogenic aerosol on the Earth's energy balance are from simulations by global models of the aerosol lifecycle coupled with global models of clouds and the hydrologic cycle. Extremely simple models have been developed for integrated assessment models, but lack the flexibility to distinguish between primary and secondary sources of aerosol. Here a simple but more physically based model expresses the aerosol indirect effect (AIE) using analytic representations of cloud and aerosol distributions and processes. Although the simple model is able to produce estimates of AIEs that are comparable to those from some global aerosol models using the same global mean aerosol properties, the estimates by the simple model are sensitive to preindustrial cloud condensation nuclei concentration, preindustrial accumulation mode radius, width of the accumulation mode, size of primary particles, cloud thickness, primary and secondary anthropogenic emissions, the fraction of the secondary anthropogenic emissions that accumulates on the coarse mode, the fraction of the secondary mass that forms new particles, and the sensitivity of liquid water path to droplet number concentration. Estimates of present-day AIEs as low as 5 W/sq m and as high as 0.3 W/sq m are obtained for plausible sets of parameter values. Estimates are surprisingly linear in emissions. The estimates depend on parameter values in ways that are consistent with results from detailed global aerosol-climate simulation models, which adds to understanding of the dependence on AIE uncertainty on uncertainty in parameter values.

Clouds↗

End-User Assessment of the NASA SPoRT Lightning AI Product

The NASA Short-term Prediction Research and Transition (SPoRT) Center has begun to develop products to address operational challenges and enhance safety during the lifecycle of lightning activity, and conduct evaluations in concentrated R2O/O2R efforts. The product evaluated for this study is Lightning Artificial Intelligence (A.I.), which predicts the probability of lightning out to 15 minutes in advance and spatially maps it using filled color contours. Lightning A.I. uses reflectivity, differential reflectivity, and correlation coefficient data from a subset of radars within the NEXRAD network to generate lightning probabilities at approximately 2 km resolution. The domains, spanning 145 x 145 km are centered over NASA-affiliated centers across the CONUS and use radar data which are closest in proximity. Lightning A.I. was developed with intended use by emergency managers at NASA centers. However, National Weather Service (NWS) offices are also often tasked with monitoring and forecasting the threat for lightning within their County Warning Areas for various impact-based decision support services. These forecasts are typically provided for aviation operations and large-scale, outdoor events, which may have varying safety requirements for decision-making based on lightning proximity and recency. The NASA SPoRT center conducted an assessment of the operational uses of Lightning A.I by various collaborative NWS Offices from late July into early September. This assessment included feedback from participants on both the product itself as well as its accessibility within the new, interactive NASA SPoRT Lightning Viewer. This presentation will include background information about Lightning A.I. and highlight results from this assessment. The feedback from the assessment will be used to inform research on any necessary modifications to this and future lightning products to assist end users.

Kelley Murphy↗

Improving Spacecraft Design and Operability for Europa Clipper through High-Fidelity, Mission-Level Modeling and Simulation

NASA’s planned Europa Clipper mission seeks to assess the habitability of Jupiter’s moon Europa, which exhibits strong evidence of an ocean of liquid water underneath its icy crust. The sheer number of unique instruments, all of which require quiescent environments in order to operate, compounded with Jupiter’s distance from the Sun and Earth, make this planned mission challenging and resource-constrained. High fidelity, mission-level simulations that model the spacecraft, ground, and environment from launch to end-of-mission with a given trajectory and mission plan have been employed early in the project lifecycle to better understand the interactions between various components of the mission and how design changes impact the entire system. These simulations have already resulted in tangible benefits to the project by providing vital input to key spacecraft trades, assessing impacts to operability, and quantifying how well the scientific objectives of the mission can be achieved. Improvements to simulation performance and to the process by which information defining the system is gathered and built into models used by simulations have the potential to further expand the scope of their use on Europa Clipper and future missions.

Lawler, C.R.↗

A Vehicle Management End-to-End Testing and Analysis Platform for Validation of Mission and Fault Management Algorithms to Reduce Risk for NASAs Space Launch System

The engineering development of the National Aeronautics and Space Administration's (NASA) new Space Launch System (SLS) requires cross discipline teams with extensive knowledge of launch vehicle subsystems, information theory, and autonomous algorithms dealing with all operations from pre-launch through on orbit operations. The nominal and off-nominal characteristics of SLS's elements and subsystems must be understood and matched with the autonomous algorithm monitoring and mitigation capabilities for accurate control and response to abnormal conditions throughout all vehicle mission flight phases, including precipitating safing actions and crew aborts. This presents a large and complex systems engineering challenge, which is being addressed in part by focusing on the specific subsystems involved in the handling of off-nominal mission and fault tolerance with response management. Using traditional model-based system and software engineering design principles from the Unified Modeling Language (UML) and Systems Modeling Language (SysML), the Mission and Fault Management (M&FM) algorithms for the vehicle are crafted and vetted in Integrated Development Teams (IDTs) composed of multiple development disciplines such as Systems Engineering (SE), Flight Software (FSW), Safety and Mission Assurance (S&MA) and the major subsystems and vehicle elements such as Main Propulsion Systems (MPS), boosters, avionics, Guidance, Navigation, and Control (GNC), Thrust Vector Control (TVC), and liquid engines. These model-based algorithms and their development lifecycle from inception through FSW certification are an important focus of SLS's development effort to further ensure reliable detection and response to off-nominal vehicle states during all phases of vehicle operation from pre-launch through end of flight. To test and validate these M&FM algorithms a dedicated test-bed was developed for full Vehicle Management End-to-End Testing (VMET). For addressing fault management (FM) early in the development lifecycle for the SLS program, NASA formed the M&FM team as part of the Integrated Systems Health Management and Automation Branch under the Spacecraft Vehicle Systems Department at the Marshall Space Flight Center (MSFC). To support the development of the FM algorithms, the VMET developed by the M&FM team provides the ability to integrate the algorithms, perform test cases, and integrate vendor-supplied physics-based launch vehicle (LV) subsystem models. Additionally, the team has developed processes for implementing and validating the M&FM algorithms for concept validation and risk reduction. The flexibility of the VMET capabilities enables thorough testing of the M&FM algorithms by providing configurable suites of both nominal and off-nominal test cases to validate the developed algorithms utilizing actual subsystem models such as MPS, GNC, and others. One of the principal functions of VMET is to validate the M&FM algorithms and substantiate them with performance baselines for each of the target vehicle subsystems in an independent platform exterior to the flight software test and validation processes. In any software development process there is inherent risk in the interpretation and implementation of concepts from requirements and test cases into flight software compounded with potential human errors throughout the development and regression testing lifecycle. Risk reduction is addressed by the M&FM group but in particular by the Analysis Team working with other organizations such as S&MA, Structures and Environments, GNC, Orion, Crew Office, Flight Operations, and Ground Operations by assessing performance of the M&FM algorithms in terms of their ability to reduce Loss of Mission (LOM) and Loss of Crew (LOC) probabilities. In addition, through state machine and diagnostic modeling, analysis efforts investigate a broader suite of failure effects and associated detection and responses to be tested in VMET to ensure reliable failure detection, and confirm responses do not create additional risks or cause undesired states through interactive dynamic effects with other algorithms and systems. VMET further contributes to risk reduction by prototyping and exercising the M&FM algorithms early in their implementation and without any inherent hindrances such as meeting FSW processor scheduling constraints due to their target platform - the ARINC 6535-partitioned Operating System, resource limitations, and other factors related to integration with other subsystems not directly involved with M&FM such as telemetry packing and processing. The baseline plan for use of VMET encompasses testing the original M&FM algorithms coded in the same C++ language and state machine architectural concepts as that used by FSW. This enables the development of performance standards and test cases to characterize the M&FM algorithms and sets a benchmark from which to measure their effectiveness and performance in the exterior FSW development and test processes. This paper is outlined in a systematic fashion analogous to a lifecycle process flow for engineering development of algorithms into software and testing. Section I describes the NASA SLS M&FM context, presenting the current infrastructure, leading principles, methods, and participants. Section II defines the testing philosophy of the M&FM algorithms as related to VMET followed by section III, which presents the modeling methods of the algorithms to be tested and validated in VMET. Its details are then further presented in section IV followed by Section V presenting integration, test status, and state analysis. Finally, section VI addresses the summary and forward directions followed by the appendices presenting relevant information on terminology and documentation.

Trevino, Luis↗

A Vehicle Management End-to-End Testing and Analysis Platform for Validation of Mission and Fault Management Algorithms to Reduce Risk for NASA's Space Launch System

The engineering development of the new Space Launch System (SLS) launch vehicle requires cross discipline teams with extensive knowledge of launch vehicle subsystems, information theory, and autonomous algorithms dealing with all operations from pre-launch through on orbit operations. The characteristics of these spacecraft systems must be matched with the autonomous algorithm monitoring and mitigation capabilities for accurate control and response to abnormal conditions throughout all vehicle mission flight phases, including precipitating safing actions and crew aborts. This presents a large and complex system engineering challenge, which is being addressed in part by focusing on the specific subsystems involved in the handling of off-nominal mission and fault tolerance with response management. Using traditional model based system and software engineering design principles from the Unified Modeling Language (UML) and Systems Modeling Language (SysML), the Mission and Fault Management (M&FM) algorithms for the vehicle are crafted and vetted in specialized Integrated Development Teams (IDTs) composed of multiple development disciplines such as Systems Engineering (SE), Flight Software (FSW), Safety and Mission Assurance (S&MA) and the major subsystems and vehicle elements such as Main Propulsion Systems (MPS), boosters, avionics, Guidance, Navigation, and Control (GNC), Thrust Vector Control (TVC), and liquid engines. These model based algorithms and their development lifecycle from inception through Flight Software certification are an important focus of this development effort to further insure reliable detection and response to off-nominal vehicle states during all phases of vehicle operation from pre-launch through end of flight. NASA formed a dedicated M&FM team for addressing fault management early in the development lifecycle for the SLS initiative. As part of the development of the M&FM capabilities, this team has developed a dedicated testbed that integrates specific M&FM algorithms, specialized nominal and off-nominal test cases, and vendor-supplied physics-based launch vehicle subsystem models. Additionally, the team has developed processes for implementing and validating these algorithms for concept validation and risk reduction for the SLS program. The flexibility of the Vehicle Management End-to-end Testbed (VMET) enables thorough testing of the M&FM algorithms by providing configurable suites of both nominal and off-nominal test cases to validate the developed algorithms utilizing actual subsystem models such as MPS. The intent of VMET is to validate the M&FM algorithms and substantiate them with performance baselines for each of the target vehicle subsystems in an independent platform exterior to the flight software development infrastructure and its related testing entities. In any software development process there is inherent risk in the interpretation and implementation of concepts into software through requirements and test cases into flight software compounded with potential human errors throughout the development lifecycle. Risk reduction is addressed by the M&FM analysis group working with other organizations such as S&MA, Structures and Environments, GNC, Orion, the Crew Office, Flight Operations, and Ground Operations by assessing performance of the M&FM algorithms in terms of their ability to reduce Loss of Mission and Loss of Crew probabilities. In addition, through state machine and diagnostic modeling, analysis efforts investigate a broader suite of failure effects and associated detection and responses that can be tested in VMET to ensure that failures can be detected, and confirm that responses do not create additional risks or cause undesired states through interactive dynamic effects with other algorithms and systems. VMET further contributes to risk reduction by prototyping and exercising the M&FM algorithms early in their implementation and without any inherent hindrances such as meeting FSW processor scheduling constraints due to their target platform - ARINC 653 partitioned OS, resource limitations, and other factors related to integration with other subsystems not directly involved with M&FM such as telemetry packing and processing. The baseline plan for use of VMET encompasses testing the original M&FM algorithms coded in the same C++ language and state machine architectural concepts as that used by Flight Software. This enables the development of performance standards and test cases to characterize the M&FM algorithms and sets a benchmark from which to measure the effectiveness of M&FM algorithms performance in the FSW development and test processes.

Trevino, Luis↗

Creep-Fatigue Interaction Testing

Fatigue fives in metals are nominally time independent below 0.5 T(sub Melt). At higher temperatures, fatigue lives are altered due to time-dependent, thermally activated creep. Conversely, creep rates are altered by super. imposed fatigue loading. Creep and fatigue generally interact synergistically to reduce material lifetime. Their interaction, therefore, is of importance to structural durability of high-temperature structures such as nuclear reactors, reusable rocket engines, gas turbine engines, terrestrial steam turbines, pressure vessel and piping components, casting dies, molds for plastics, and pollution control devices. Safety and lifecycle costs force designers to quantify these interactions. Analytical and experimental approaches to creep-fatigue began in the era following World War II. In this article experimental and life prediction approaches are reviewed for assessing creep-fatigue interactions of metallic materials. Mechanistic models are also discussed briefly.

Halford, Gary R.↗

Using Facility Condition Assessments to Identify Actions Related to Infrastructure

To support cost effective, quality research it is essential that laboratory and testing facilities are maintained in a continuous and reliable state of availability at all times. NASA Langley Research Center (LaRC) and its maintenance contractor, Jacobs Technology, Inc. Research Operations, Maintenance, and Engineering (ROME) group, are in the process of implementing a combined Facility Condition Assessment (FCA) and Reliability Centered Maintenance (RCM) program to improve asset management and overall reliability of testing equipment in facilities such as wind tunnels. Specific areas are being identified for improvement, the deferred maintenance cost is being estimated, and priority is being assigned against facilities where conditions have been allowed to deteriorate. This assessment serves to assist in determining where to commit available funds on the Center. RCM methodologies are being reviewed and enhanced to assure that appropriate preventive, predictive, and facilities/equipment acceptance techniques are incorporated to prolong lifecycle availability and assure reliability at minimum cost. The results from the program have been favorable, better enabling LaRC to manage assets prudently.

Rubert, Kennedy F.↗

Ensuring Success of Adaptive Control Research Through Project Lifecycle Risk Mitigation

Lessons Learne: 1. Design-out unnecessary risk to prevent excessive mitigation management during flight. 2. Consider iterative checkouts to confirm or improve human factor characteristics. 3. Consider the total flight test profile to uncover unanticipated human-algorithm interactions. 4. Consider test card cadence as a metric to assess test readiness. 5. Full-scale flight test is critical to development, maturation, and acceptance of adaptive control laws for operational use.

Pavlock, Kate M.↗

End-user Assessment of the NASA SPoRT GLM Stoplight Product

National Weather Service (NWS) offices monitor and forecast the threat for lightning within their County Warning Areas for various impact-based decision support services (IDSS). These forecasts are provided routinely for aviation operations, but irregularly for large-scale, outdoor events, which typically have varying safety requirements with regards to lightning. Lightning monitoring and forecasting can require synthesizing a plethora of data, so products that make this process more efficient and effective are sought by the operational community. The NASA Short-term Prediction Research and Transition (SPoRT) Center has begun to develop several products to address these operational challenges during the lifecycle of lightning activity, and conduct evaluations in concentrated (Research-to-Operations/Operations-to-Research) efforts. The product evaluated for this study is the Geostationary Lightning Mapper (GLM) Stoplight product, which addresses lightning safety specifically with regards to lightning recency and cessation. The GLM Stoplight product displays the spatial extent of lightning and uses color-coded pixels to show the recency of lightning in 10-minute increments. This presentation highlights results from an assessment of the GLM Stoplight product by select NWS offices, as well as emergency managers, that took place over a 5-week period from May 1st to June 2nd. Feedback was collected on the GLM Stoplight product and on a new and interactive lightning viewer, which allowed participants to tailor visualization of the product based on their location and desired application. Results will help NASA SPoRT gain a better understanding of how forecasters and emergency managers use lightning data for safety applications. In addition, the assessment will inform research on any necessary modifications to this and future lightning products to assist end users.

Kelley Murphy↗

SCRL-Model for Human Space Flight Operations Enterprise Supply Chain

This paper will present a Supply Chain Readiness Level (SCRL) model that can be used to evaluate and configure adaptable and sustainable program and mission supply chains at an enterprise level. It will also show that using SCRL in conjunction with Technology Readiness Levels (TRLs), Manufacturing Readiness Levels (MRLs) and National Aeronautics Space Administrations (NASA s) Project Lifecycle Process will provide a more complete means of developing and evaluating a robust sustainable supply chain that encompasses the entire product, system and mission lifecycle. In addition, it will be shown that by implementing the SCRL model, NASA can additionally define supplier requirements to enable effective supply chain management (SCM). Developing and evaluating overall supply chain readiness for any product, system and mission lifecycle is critical for mission success. Readiness levels are presently being used to evaluate the maturity of technology and manufacturing capability during development and deployment phases of products and systems. For example, TRLs are used to support the assessment of the maturity of a particular technology and compare maturity of different types of technologies. MRLs are designed to assess the maturity and risk of a given technology from a manufacturing perspective. In addition, when these measurement systems are used collectively they can offer a more comprehensive view of the maturity of the system. While some aspects of the supply chain and supply chain planning are considered in these familiar metric systems, certain characteristics of an effective supply chain, when evaluated in more detail, will provide an improved insight into the readiness and risk throughout the supply chain. Therefore, a system that concentrates particularly on supply chain attributes is required to better assess enterprise supply chain readiness.

Tucker, Brian↗

Space Launch System Accelerated Booster Development Cycle

With the retirement of the Space Shuttle, NASA is seeking to reinvigorate the national space program and recapture the public s interest in human space exploration by developing missions to the Moon, near-earth asteroids, Lagrange points, Mars, and beyond. The would-be successor to the Space Shuttle, NASA s Constellation Program, planned to take humans back to the Moon by 2020, but due to budgetary constraints was cancelled in 2010 in search of a more "affordable, sustainable, and realistic" concept2. Following a number of studies, the much anticipated Space Launch System (SLS) was unveiled in September of 2011. The SLS core architecture consists of a cryogenic first stage with five Space Shuttle Main Engines (SSMEs), and a cryogenic second stage using a new J-2X engine3. The baseline configuration employs two 5-segment solid rocket boosters to achieve a 70 metric ton payload capability, but a new, more capable booster system will be required to attain the goal of 130 metric tons to orbit. To this end, NASA s Marshall Space Flight Center recently released a NASA Research Announcement (NRA) entitled "Space Launch System (SLS) Advanced Booster Engineering Demonstration and/or Risk Reduction." The increased emphasis on affordability is evident in the language used in the NRA, which is focused on risk reduction "leading to an affordable Advanced Booster that meets the evolved capabilities of SLS" and "enabling competition" to "enhance SLS affordability. The purpose of the work presented in this paper is to perform an independent assessment of the elements that make up an affordable and realistic path forward for the SLS booster system, utilizing advanced design methods and technology evaluation techniques. The goal is to identify elements that will enable a more sustainable development program by exploring the trade space of heavy lift booster systems and focusing on affordability, operability, and reliability at the system and subsystem levels5. For this study, affordability is defined as lifecycle cost, which includes design, development, test, and engineering (DDT&E), production and operational costs (P&O). For this study, the system objectives include reducing DDT&E schedule by a factor of three, showing 99.9% reliability, flying up to four times per year, serving both crew and cargo missions, and evolving to a lift capability of 130 metric tons.3 After identifying gaps in the current system s capabilities, this study seeks to identify non-traditional and innovative technologies and processes that may improve performance in these areas and assess their impacts on booster system development. The DDT&E phase may be improved by incorporating incremental development testing and integrated demonstrations to mitigate risk. To further reduce DDT&E, this study will also consider how aspects of the booster system may have commonality with other users, such as the Department of Defense, commercial applications, or international partners; by sharing some of the risk and investment, the overall development cost may be reduced. Consideration is not limited to solid and liquid rocket boosters. A set of functional performance characteristics, such as engine thrust, specific impulse (Isp), mixture ratio, and throttle range are identified and their impacts on the system are evaluated. This study also identifies how such characteristics affect overall life cycle cost, including DDT&E and fixed and variable P&O.

Arockiam, Nicole↗