Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “lifecycle analysis”

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 127 records · Page 7

Towards an A-train Aerosol Assimilation System: Assimilation of MODIS Aerosol Optical Thickness Retrievals into a Global Aerosol Transport and Radiation Model

To understand the role of atmospheric aerosols in Earth's climate system we ideally require a global, three-dimensional, and temporally continuous system of measurements. The view of aerosols provided by a single polar-orbiting satellite instrument (e.g., MODIS), while providing the greatest spatial coverage of any measurement system available, can offer only a single relevant observation per day of a particular location. Furthermore, the quantitative interpretation of those observations is subject to considerable uncertainty because of we do not know the aerosol optical properties or vertical profiles well enough. Ground-based and in situ measurements can provide missing detail about aerosol vertical and optical properties, but lack the spatial (and sometimes temporal) coverage desired. Chemical transport models treating the aerosol lifecycle complement this picture by providing three-dimensional, global, and continuous aerosol fields, but suffer from poor constraints on their initial conditions (e.g., the aerosol source, sink, and transformation mechanisms). Here we present a global, three- dimensional aerosol transport model and assimilation system. The model assimilates the MODIS aerosol optical thickness product to constrain its aerosol distributions and burdens. We provide an analysis of the model aerosol distributions as constrained by ground-based sun photometer measurements and aerosol products from other satellite measurements.

Colarco, P.↗

Advancing the practice of systems engineering at JPL

In FY 2004, JPL launched an initiative to improve the way it practices systems engineering. The Lab's senior management formed the Systems Engineering Advancement (SEA) Project in order to "significantly advance the practice and organizational capabilities of systems engineering at JPL on flight projects and ground support tasks." The scope of the SEA Project includes the systems engineering work performed in all three dimensions of a program, project, or task: 1. the full life-cycle, i.e., concept through end of operations 2. the full depth, i.e., Program, Project, System, Subsystem, Element (SE Levels 1 to 5) 3. the full technical scope, e.g., the flight, ground and launch systems, avionics, power, propulsion, telecommunications, thermal, etc. The initial focus of their efforts defined the following basic systems engineering functions at JPL: systems architecture, requirements management, interface definition, technical resource management, system design and analysis, system verification and validation, risk management, technical peer reviews, design process management and systems engineering task management, They also developed a list of highly valued personal behaviors of systems engineers, and are working to inculcate those behaviors into members of their systems engineering community. The SEA Project is developing products, services, and training to support managers and practitioners throughout the entire system lifecycle. As these are developed, each one needs to be systematically deployed. Hence, the SEA Project developed a deployment process that includes four aspects: infrastructure and operations, communication and outreach, education and training, and consulting support. In addition, the SEA Project has taken a proactive approach to organizational change management and customer relationship management - both concepts and approaches not usually invoked in an engineering environment. This paper'3 describes JPL's approach to advancing the practice of systems engineering at the Lab. It describes the general approach used and how they addressed the three key aspects of change: people, process and technology. It highlights a list of highly valued personal behaviors of systems engineers, discusses the various products, services and training that were developed, describes the deployment approach used, and concludes with several lessons learned.

process improvement↗

Fully Employing Software Inspections Data

Software inspections provide a proven approach to quality assurance for software products of all kinds, including requirements, design, code, test plans, among others. Common to all inspections is the aim of finding and fixing defects as early as possible, and thereby providing cost savings by minimizing the amount of rework necessary later in the lifecycle. Measurement data, such as the number and type of found defects and the effort spent by the inspection team, provide not only direct feedback about the software product to the project team but are also valuable for process improvement activities. In this paper, we discuss NASA's use of software inspections and the rich set of data that has resulted. In particular, we present results from analysis of inspection data that illustrate the benefits of fully utilizing that data for process improvement at several levels. Examining such data across multiple inspections or projects allows team members to monitor and trigger cross project improvements. Such improvements may focus on the software development processes of the whole organization as well as improvements to the applied inspection process itself.

Shull, Forrest↗

Development of Human System Integration at NASA

Human Systems Integration seeks to design systems around the capabilities and limitations of the humans which use and interact with the system, ensuring greater efficiency of use, reduced error rates, and less rework in the design, manufacturing and operational deployment of hardware and software. One of the primary goals of HSI is to get the human factors practitioner involved early in the design process. In doing so, the aim is to reduce future budget costs and resources in redesign and training. By the preliminary design phase of a project nearly 80% of the total cost of the project is locked in. Potential design changes recommended by evaluations past this point will have little effect due to lack of funding or a huge cost in terms of resources to make changes. Three key concepts define an effective HSI program. First, systems are comprised of hardware, software, and the human, all of which operate within an environment. Too often, engineers and developers fail to consider the human capacity or requirements as part of the system. This leads to poor task allocation within the system. To promote ideal task allocation, it is critical that the human element be considered early in system development. Poor design, or designs that do not adequately consider the human component, could negatively affect physical or mental performance, as well as, social behavior. Second, successful HSI depends upon integration and collaboration of all the domains that represent acquisition efforts. Too often, these domains exist as independent disciplines due to the location of expertise within the service structure. Proper implementation of HSI through participation would help to integrate these domains and disciplines to leverage and apply their interdependencies to attain an optimal design. Via this process domain interests can be integrated to perform effective HSI through trade-offs and collaboration. This provides a common basis upon which to make knowledgeable decisions. Finally, HSI must be considered early in the requirements development phase of system design and acquisition. This will provide the best opportunity to maximize return on investment (ROI) and system performance. HSI requirements must be developed in conjunction with capability ]based requirements generation through functional. HSI requirements will drive HSI metrics and embed HSI issues within the system design. After a system is designed, implementation of HSI oversights can be very expensive. An HSI program should be included as an integral part of a total system approach to vehicle and habitat development. This would include, but not limited to, workstation design, D&C development, volumetric analysis, training, operations, and human -robotic interaction. HSI is a necessary process for Human Space Flight programs to meet the Agency Human ]System standards and thus mitigate human risks to acceptable levels. NASA has been involved in HSI planning, procedures development, process, and implementation for many years, and has been building several internal and publicly accessible products to facilitate HSI fs inclusion in the NASA Systems Engineering Lifecycle. Some of these products include: NASA STD 3001 Volumes 1 and 2, Human Integration Design Handbook, NASA HSI Implementation Plan, NASA HSI Implementation Plan Templates, NASA HSI Implementation Handbook, and a 2 ]hour short course on HSI delivered as part of the NASA Space and Life Sciences Directorate Academy. These products have been created leveraging industry best practices and lessons learned from other Federal Government agencies.

Whitmore, Mihriban↗

Comm for Small Sats: The Lunar Atmosphere and Dust Environment Explorer (LADEE) Communications Subsystem

September 6, 2013 through April 21, 2014 marked the mission lifecycle of the highly successful LADEE (Lunar Atmosphere and Dust Environment Explorer) mission that orbited the moon to gather detailed information about the thin lunar atmosphere. This paper will address the development, risks, and lessons learned regarding the specification, selection, and deployment of LADEE's unique Radio Frequency based communications subsystem and supporting tools. This includes the Electronic Ground Support Equipment (EGSE), test regimes, and RF dynamic link analysis environment developed to meet mission requirements for small, flexible, low cost, high performance, fast turnaround, and reusable spacecraft communication capabilities with easy and reliable application to future similar low cost small satellite missions over widely varying needs for communications and communications system complexity. LADEE communication subsystem key components, architecture, and mission performance will be reviewed toward applicability for future mission planning, design, and utilization.

transponder↗

Autonomous In-space Construction, Maintenance, and Reconfiguration Using Programmable Meta-Material

NASA ARC's Coded Structures Laboratory (CSL) is developing autonomous construction, maintenance, and reconfiguration technologies to meet long-duration and deep space infrastructure needs, in accordance with long-term NASA goals of "in-space reliance" and "mass-less exploration." We seek to achieve these capabilities by utilizing a "programmable meta-material" approach that integrates emerging advances in materials (mechanical meta-materials), manufacturing (cooperative mobile robotics), and autonomy (multi-agent planning algorithms). Through the ARMADAS project, we have shown assembly of high-performance engineered cellular materials using multiple cooperating mobile robotic assemblers. In this paper, we describe how such a programmable meta-material architecture may shift the paradigm of how we design, build, manufacture, and operate future space infrastructure and assets. The core of a programmable meta-material architecture consists of 3 main technology sub-areas: the structure, the assembly agents, and the assembly algorithms. We co-design these systems to ensure an adaptable system that can create and reconfigure structures from a base set of building block components. From this core technology, we can branch out and expand the capability of the system through additional secondary component types and robotic agents to perform activities such as inspections, maintenance, repair, payload installation, or perform power and communications interconnect. As these technologies mature, future designers will be able to utilize the system to rapidly integrate and operate assets in space or on planetary surfaces from a set of well-tested part library, or create their own modules to integrate into the system. A core trait to the development of this system is the automation approach. Because of the modular and functional discrete (pixel-like) nature of the structural system, a diverse set of powerful algorithms for analysis, planning, and simulation can be adapted and leveraged to optimize construction, maintenance, and dynamic reorganization (as hardware with programmable form and function). With an ability to free the design space from launch vehicle constraints and fundamentally shift how a mission is designed and conducted, we discuss the influence of a programmable meta-material architecture on mission design, build, and operations. For the "design phase", we discuss project lifecycle effects, costs, time, and performance. For the "build phase", we discuss reusability, ISRU, manufacturing, material logistics, and scalability. And for "operations", we discuss autonomy, maintenance and upgrades, reliability, and reconfiguration. Autonomy and modularity are the primary enabling traits of this system. Engineering systems that utilize a modular and reconfiguration building block approach such as digital communication and computation systems, currently lead all other areas of technology in size and complexity scalability. NASA is extending the benefits and flexibility of digital systems to hardware systems, to optimize materials lifecycle management and expand our space exploration mission capabilities.

in space assembly↗

Human Factors in the Design of the Crew Exploration Vehicle (CEV)

NASA s Space Exploration vision for humans to venture to the moon and beyond provides interesting human factors opportunities and challenges. The Human Engineering group at NASA has been involved in the initial phases of development of the Crew Exploration Vehicle (CEV), Orion. Getting involved at the ground level, Human Factors engineers are beginning to influence design; this involvement is expected to continue throughout the development lifecycle. The information presented here describes what has been done to date, what is currently going on, and what is expected in the future. During Phase 1, prior to the contract award to Lockheed Martin, the Human Engineering group was involved in generating requirements, conducting preliminary task analyses based on interviews with subject matter experts in all vehicle systems areas, and developing preliminary concepts of operations based on the task analysis results. In addition, some early evaluations to look at CEV net habitable volume were also conducted. The program is currently in Phase 2, which is broken down into design cycles, including System Readiness Review, Preliminary Design Review, and Critical Design Review. Currently, there are ongoing Human Engineering Technical Interchange Meetings being held with both NASA and Lockheed Martin in order to establish processes, desired products, and schedules. Multiple design trades and quick-look evaluations (e.g. display device layout and external window size) are also in progress. Future Human Engineering activities include requirement verification assessments and crew/stakeholder evaluations of increasing fidelity. During actual flights of the CEV, the Human Engineering group is expected to be involved in in-situ testing and lessons learned reporting, in order to benefit human space flight beyond the initial CEV program.

Whitmore, Mihriban↗

Androgynous Fasteners for Robotic Structural Assembly

We describe the design and analysis of an androgynous fastener for autonomous robotic assembly of high performance structures. The design of these fasteners aims to prioritize ease of assembly through simple actuation with large driver positioning tolerance requirements, while producing a reversible mechanical connection with high strength and stiffness per mass. This can be applied to high strength to weight ratio structural systems, such as discrete building block based systems that offer reconfigurability, scalability, and system lifecycle efficiency. Such periodic structures are suitable for navigation and manipulation by relatively small mobile robots. The integration of fasteners, which are lightweight and can be robotically installed, into a high performance robotically managed structural system is of interest to reduce launch energy requirements, enable higher mission adaptivity, and decrease system life-cycle costs.

Formoso, Olivia↗

Reliability-Aware Requirements Development for Autonomy Software

Autonomy is the ability of a system to make decisions and take actions in the presence of uncertainty. Validating autonomy, therefore, is a matter of validating that the system makes intelligent decisions even when there might be discrepancies between the observed and the expected state of the world as well as when the possible outcome of each of the possible courses of action is uncertain. During the requirements engineering phase, the functions, including those that are required to be autonomous and their expected behavior are specified. However, in the case of autonomous software system, it is challenging to specify all possible scenarios that the software may encounter. Additionally, since autonomous behaviors cannot always be fully predetermined, it is difficult to reason about their completeness and correctness. While these challenges are also faced with non-autonomous system, they are more prevalent for autonomous system due to their complexity and emergent behavior. Our efforts have been three-fold. On one hand, we have developed a goal-based method for requirements decomposition. We have embedded this approach into a higher-level systems engineering framework and then developed methods for decision and reliability analysis within this framework. And finally, we use simulation analysis to validate the more theoretical methods and provide a feedback mechanism. The decision analysis approach (DA) helps in identifying and mitigating the run-time risks, by bringing to the forefront the uncertainties, decisions, interactions, and other factors that may cause autonomous software to make erroneous decisions. The DA framework is used to quantify, for each decision that the software can make, failure risk due to uncertainties. The information about the key decisions and circumstances that can cause autonomous system to make incorrect decisions are used to generate test scenarios to be run in a simulator to ensure that the system can handle error-prone circumstances. The results or outcomes from decisions, based on the simulated scenarios, can then be leveraged to further gain insight of the assured system. We combine a goal-based approach with simulation analysis to facilitate requirements development for autonomous systems and further provide a method for run-time systems level reliability considerations during the autonomous software development process. The DA and the reliability analysis methods provide a formalism for the consideration of uncertainty in the run time decision-making process for autonomous software. This formalism considers the uncertainty involved in the outcome of different courses of action, in terms of performance and cost, as well as a method to consider the system level reliability implications. System level reliability considerations for autonomous software decision making contribute to the satisfaction of the system level goals over the lifecycle of a given mission. We demonstrate our approach using a hypothetical rover path planning example. The requirements for our rover simulator are based on existing literature about Mars rovers and lessons learned from real world observations at JPL. The specifics of the autonomy design for the Mars rovers, that have not been previously cleared for external release, are not used for our demonstrations.

Lindvall, Mikael↗

Integrated Concurrent Engineering Teams for Increased Efficiency in Flight Projects

A highly integrated Concurrent Engineering Team (CET) within a flight project evolves in its function and has the potential to provide many benefits through the project lifecycle. The benefits include superior systems-oriented design products, as well as overall improved project efficiency and higher-performing interpersonal relationships within the project. If physically integrated, this can manifest as a Concurrent Engineering Center (CEC) centrally located within a project’s physical office space. Here we discuss the process to establish and maintain a tightly integrated engineering and design team for providing highly streamlined service to the project, including a cost/benefits analysis discussion.

Flight Project↗

Integrated Concurrent Engineering Teams for Increased Efficiency in Flight Projects

A highly integrated Concurrent Engineering Team (CET) within a flight project evolves in its function and has the potential to provide many benefits through the project lifecycle. The benefits include superior systems-oriented design products, as well as overall improved project efficiency and higher-performing interpersonal relationships within the project. If physically integrated, this can manifest as a Concurrent Engineering Center (CEC) centrally located within a project’s physical office space. Here we discuss the process to establish and maintain a tightly integrated engineering and design team for providing highly streamlined service to the project, including a cost/benefits analysis discussion.

Flight Project↗

The Convective Nature of the Tropical Cyclone Lifecycle via GLM and GPM Observations

This study examines the convective nature of the tropical cyclone (TC) lifecycle from tropical storm through extratropical transition. We analyze lightning observations collected from the Geostationary Lightning Mapper (GLM) on the GOES-16 satellite in combination with coincident passive microwave and Ku-band radar observations collected from Global Precipitation Measurement (GPM) mission satellites. A unique aspect of this study, which spans the Atlantic basin hurricane seasons 2018-2020, is that it provides the first known total lightning observations in TCs throughout their extratropical (ET) transition. Analysis of Tropical Storm (TS), Category 1-2 hurricanes (CAT12), Category 3-5 hurricanes (CAT35), and ET time periods, which are grouped by storm-motion and shear-relative characteristics, show that lightning maxima generally occur regimes of down-motion (up-shear), consistent (inconsistent) with previous studies. Further analysis also breaks down time periods by geographic location (e.g., land, coast, ocean) and shear strength; shifting lightning patterns are observed with increasing shear. The lightning maxima are also generally collocated with minima in 37-GHz brightness temperature observations, which is indicative of precipitation-sized ice. DPR Ku-band reflectivity profiles from the GPM Precipitation Feature (PF) database exhibit distinct differences in depth and intensity for electrically active PFs vs those that are not. On average, PFs defined by a rain rate threshold are larger for hurricane strength ITPs (CAT12, CAT35) as compared to either TS or ET ITPs. This indicates that during the hurricane strength ITPs, PFs may be capturing the entire, symmetric rain shield.

hurricane↗

Dust Spectroscopy and the Nature of Grains

Ground-based, air-borne and space-based, infrared spectra of a wide variety of objects have revealed prominent absorption and emission features due to large molecules and small dust grains. Analysis of this data reveals a highly diverse interstellar and circumstellar grain inventory, including both amorphous materials and highly crystalline compounds (silicates and carbon). This diversity points towards a wide range of physical and chemical birthsites as well as a complex processing of these grains in the interstellar medium. In this talk, I will review the dust inventory contrasting and comparing both the interstellar and circumstellar reservoirs. The focus will be on the processes that play a role in the lifecycle of dust in the interstellar medium.

Tielens, A. G. G. M.↗

Reducing V&V Cost of Flight Critical Systems: Myth or Reality?

This paper presents an overview of NASA research program on the V&V of flight critical systems. Five years ago, NASA started an effort to reduce the cost and possibly increase the effectiveness of V&V for flight critical systems. It is the right time to take a look back and realize what progress has been made. This paper describes our overall approach and the tools introduced to address different phases of the software lifecycle. For example, we have improved testing by developing a statistical learning approach tor defining test cases. The tool automatically identifies possible unsafe conditions by analyzing outliers in output data; using an iterative learning process, it can then generate more test cases that represent potentially unsafe regions of operation. At the code level, we have developed and made available as open source a static analyzer for C and C++ programs called IKOS. We have shown that IKOS is very precise in the analysis of embedded C programs (very few false positives) and a bit less for regular C and C++ code. At the design level, in collaboration with our NRA partners, we have developed a suite of analysis tools for Simulink models. The analysis is done in a compositional framework for scalability.

Brat, Guillaume P.↗

Formalizing and Analyzing Requirements with FRET

Formal verification and simulation are powerful tools to validate requirements against complex systems. Requirements are developed in early stages of the software lifecycle and are typically written in ambiguous natural language. There is a gap between such requirements and formal notations that can be used by verification tools, and lack of support for proper association of requirements with software artifacts for verification. We propose to write requirements in an intuitive, structured natural language with formal semantics, and to support formalization and model/code verification as a smooth, well-integrated process. To this end, we have developed an end-to-end, open source requirements analysis framework that checks Simulink models against requirements written structured natural language.

Mavridou, Anastasia↗

Capturing, Analyzing, Maintaining, and Disseminating Shape Memory Material Data Between Information Management Systems

With an increased demand on reducing the time, cost, and effort to develop new materials, Integrated Computational Materials Engineering (ICME) has received widespread attention in various engineering disciplines as a catalyst for significantly reducing experimental testing during the material design process. An ICME approach to design can enable ‘fit-for-purpose’ materials to be realized in engineering applications by incorporating well-understood process-property-performance relationships between the various length and time scales in a material’s structure, enabling material optimization. However, such an approach requires validated multiscale models at the various length scales for a material, which in turn requires a large amount of data, a robust means of storing the data, and the ability to link data to developed material models. The NASA Vision 2040 [1] has identified nine key elements to enabling ICME approaches in system level design, with one being “Data, Information, and Visualization”, thus outlining the importance of a robust information management system for ICME. As the relationship between microstructure, properties, and material performance become better understood and incorporated into multiscale models that can be leveraged in application design, the emergence of new materials with application-driven properties can be realized. One such new material class that has seen growing attention are shape memory materials (SMM), in which a material can transition between a deformed and undeformed state via a reversible phase transformation when subject to a thermal, mechanical, or magnetic load [2]. SMMs have been used widely in aerospace and biomedical industries, including applications such as actuators, low-shock mechanisms, medical staples, braces, and stents [3, 4]. These materials exhibit unique behavior due to their ability to transition between phases, and thus the mechanisms that enable this transition must be captured in a data information management system and incorporated into SMM material models. At NASA Glenn Research Center, the Shape Memory Materials Database (SMMD) Tool has been developed to capture the necessary information that governs SMM material behavior and provide users the ability to select and visualize various SMMs for a specific application [5]. The database contains point-wise data for published SMM materials, along with the pedigree metadata for traceability necessary for a robust information management system. The database is also capable of storing in-house test data performed at NASA GRC by interacting with the developed Shape Memory Alloy (SMA) Analytics tool to extract the necessary point-wise values and populate the database. Although the SMMD Tool offers its users a single, authoritative source for SMM material data that is critical for model development and material design, the full material pedigree of the in-house test data for SMMs is not currently captured and is out of the scope for the SMMD tool. In this work, the schema for capturing SMM test data within the larger NASA GRC ICME Schema [6, 7, 8, 9] will be developed and implemented for thermomechanical tests conducted at NASA GRC. The developed schema will not only store the relevant data needed for the SMMD tool, but also the material pedigree (i.e., production of the bulk material, bulk material analysis, sample cut-out diagrams, sample fabrication procedure, etc.), test pedigree (i.e., test equipment used, measurement systems used, raw test data), and analysis pedigree (i.e., how the data in the SMMD tool is calculated). Furthermore, a Python-based framework will be developed to seamlessly interact between the SMA Analytics and SMMD tools, which will write the full dataset and associated metadata to the GRC Information Management System before passing the required point-wise data to the SMMD tool. Data informatics is a key element of the NASA Vision 2040, which requires not only that data is stored and maintained throughout the material lifecycle, but that the data is also accessible and reusable such that material development efforts can be minimized. Therefore, for an ICME design approach to be realized, a centralized information management system that drives the ICME process must be able to communicate with other databases. The work that will be presented in this presentation will therefore not only demonstrate the ability of NASA GRC’s information management system to capture SMM data, but also its ability to interact with pre-existing tools specialized for such materials.

Data management↗

Towards a systems approach to risk considerations for concurrent design

This paper describes the new process used by the Project Design Center at NASA's Jet Propulsion Laboratory for the identification, assessment and communication of risk elements throughout the lifecycle of a mission design. This process includes a software tool, 'RAP' that collects and communicates risk information between the various designers and a 'risk expert' who mediates this process. The establishment of this process is an attempt towards the systematic consideration of risk in the design decision making process. Using this process, we are able to better keep track of the risks associated with the design decisions. Furthermore, it helps us develop better risk profiles for the studies under consideration. We aim to refine and expand the current process to enable more thorough risk analysis capabilities in the future.

concurrent design↗

Multi-Mission Power Analysis Tool (MMPAT) Version 3

The Multi-Mission Power Analysis Tool (MMPAT) simulates a spacecraft power subsystem including the power source (solar array and/or radioisotope thermoelectric generator), bus-voltage control, secondary battery (lithium-ion or nickel-hydrogen), thermostatic heaters, and power-consuming equipment. It handles multiple mission types including heliocentric orbiters, planetary orbiters, and surface operations. Being parametrically driven along with its user-programmable features can reduce or even eliminate any need for software modifications when configuring it for a particular spacecraft. It provides multiple levels of fidelity, thereby fulfilling the vast majority of a project s power simulation needs throughout the lifecycle. It can operate in a stand-alone mode with a graphical user interface, in batch mode, or as a library linked with other tools. This software can simulate all major aspects of a spacecraft power subsystem. It is parametrically driven to reduce or eliminate the need for a programmer. Added flexibility is provided through user-designed state models and table-driven parameters. MMPAT is designed to be used by a variety of users, such as power subsystem engineers for sizing power subsystem components; mission planners for adjusting mission scenarios using power profiles generated by the model; system engineers for performing system- level trade studies using the results of the model during the early design phases of a spacecraft; and operations personnel for high-fidelity modeling of the essential power aspect of the planning picture.

Wood, Eric G.↗