Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “integrated planning and scheduling”

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 631 records · Page 35

Improving Efficacy and Safety of Pharmacological Treatment Through Precision Medicine and Pharmacogenomics for Human Deep Space Exploration

INTRODUCTION: Future spaceflight will require increased crew medical autonomy as exploration class missions expanding duration and distance from Earth, especially for Mars missions. As mission duration increases, it will be even more essential to have appropriate amounts of effective medication to ensure the maintenance of crew health and performance. Conversely, mass and volume constraints will become more severe as future spaceflight expands beyond low Earth orbit, where resupply is difficult or becomes impossible. These constraints thus convey an urgency to further tailor medications included in the spacecraft formulary and increased examination of appropriate dosing regimens. BACKGROUND: Precision Health is an exciting area of cutting-edge research and medicine focused on maintaining an individual’s health and performance through in-depth understanding of an individual’s unique factors and molecular profiles. This approach can be adapted to better predict, monitor, and address physiological responses to the spaceflight environment. One example is the field of pharmacogenomics (PGX),the study of how the expressed genome impacts drug responses with the goal of prescribing the right dose of the right drug at the right time. Specifically, PGX testing provides valuable information on an individual’s precise allelic variations to guide physicians in making informed decisions on pharmaceutical choice and dosing to avoid adverse drug events and maximize pharmacological efficacy. The goal of this study was to evaluate which drugs in the current space pharmacy could be evaluated using PGX testing and to understand the potential impact on the health and wellness of the astronaut population. Additionally, we sought to evaluate clinically available FDA-approved PGX testing solutions to better understand its applicability. METHODS: A complete list of drugs onboard the International Space Station (ISS) was analyzed for risk and likelihood of drug failure and PGX actionability. This analysis encompassed both personal astronaut medications, including supplements and over the counter drugs (n=151) and ISS MedKit formulary medications (n=95). Duplicate medications and different formulations were removed, which resulted in 157 total drugs used in the subsequent analysis. A 5x5 risk assessment table was produced by examining the likelihood of drug failure compared to the consequence of drug failure. Likelihood of individual drug failure was defined by whether existing processes are sufficient to prevent adverse events, as ranked from 1 (very low, can easily be prevented) to 5 (very high, cannot be prevented) during a Mars mission. In contrast, the consequence of drug failure was defined by impact to safety, schedule, cost or technical and ranked from 1 (very low) to 5 (very high).A comprehensive assessment of commercially available PGX solutions is currently underway to evaluate specimen requirements, cost/benefit analysis (cost vs. number of alleles assessed), utility of variant analysis, relevance to inflight medication usage, quality of reporting in enabling clinical application, and ease of integration into electronic medical records. RESULTS: Risk assessments(LxC 5x5 table) indicated29medicationswere in the yellow or red zone driven predominantly by drug failure or safety concerns, with the remainder(n=128)of the medications in the green zone where risk is acceptable. We found that current PGX testing results could impact 21% of the total medications in the ISS MedKit and IMAK; of these, 9 medications currently have direct clinically actionable guidance available. Results of the clinical PGX solution evaluations as related to these medications will be presented. CONCLUSION: PGX testing has demonstrated clear benefits in terrestrial medicine and clinical environments for the selection of proper medications, avoiding adverse drug reactions, and maximizing drug efficacy. We propose that similar benefits would be bestowed on the astronaut and commercial spaceflight passenger population by performing preemptive pre-flight PGX testing to reduce risk of mission failure due to ineffective or toxic medications, improve targeting drug efficacy and safety, and further open the door to countermeasure research exploring PGX-related allelic variants. For example, PGX results could allow tailoring of specific medications at optimal doses more precisely to each individual astronaut, particularly in areas of space motion sickness, sleep aids, and analgesics. An additional benefit is that PGX results could provide information for better planning of the components of a space pharmacy for deep space missions to be more cost effective and more efficient in the utilization of limited pharmaceutical resources. Finally, while PGX testing of the astronaut corps is not currently conducted, this approach could provide immediate impact in support of mission success by reducing risks, optimizing astronaut performance, and providing valuable insights into long-term astronaut health. Such advancements in clinical decision making are important next steps in building dynamic individual risk profiles for astronauts, increasing crew autonomy and providing tailored countermeasures

Alice R W Tang↗

An Examination of Selected Datacom Options for the Near-Term Implementation of Trajectory Based Operations

A primary feature of the Next Generation Air Transportation System (NextGen) is trajectory based operations (TBO). Under TBO, aircraft flight plans are known to computer systems on the ground that aid in scheduling and separation. The Future Air Navigation System (FANS) was developed to support TBO, but relatively few aircraft in the US are FANSequipped. Thus, any near-term implementation must provide TBO procedures for non-FANS aircraft. Previous research has explored controller clearances, but any implementation must also provide procedures for aircraft requests. The work presented here aims to surface issues surrounding TBO communication procedures for non-FANS aircraft and for aircraft requesting deviations around weather. Three types of communication were explored: Voice, FANS, and ACARS,(Aircraft Communications Addressing and Reporting System). ACARS and FANS are datacom systems that differ in that FANS allows uplinked flight plans to be loaded into the Flight Management System (FMS), while ACARS delivers flight plans as text that must be entered manually via the Control Display Unit (CDU). Sixteen pilots (eight two-person flight decks) and four controllers participated in 32 20-minute scenarios that required the flight decks to navigate through convective weather as they approached their top of descents (TODs). Findings: The rate of non-conformance was higher than anticipated, with aircraft off path more than 20% of the time. Controllers did not differentiate between the ACARS and FANS datacom, and were mixed in their preference for Voice vs. datacom (ACARS and FANS). Pilots uniformly preferred Voice to datacom, particularly ACARS. Much of their dislike appears to result from the slow response times in the datacom conditions. As a result, participants frequently resorted to voice communication. These results imply that, before implementing TBO in environments where pilots make weather deviation requests, further research is needed to develop communication procedures that integrate voice and datacom.

trajectory based operations↗

Forecasting Solar Photovoltaic Power Production: A Comprehensive Review and Innovative Data-Driven Modeling Framework

The intermittent and stochastic nature of Renewable Energy Sources (RESs) necessitates accurate power production prediction for effective scheduling and grid management. This paper presents a comprehensive review conducted with reference to a pioneering, comprehensive, and data-driven framework proposed for solar Photovoltaic (PV) power generation prediction. The systematic and integrating framework comprises three main phases carried out by seven main comprehensive modules for addressing numerous practical difficulties of the prediction task: phase I handles the aspects related to data acquisition (module 1) and manipulation (module 2) in preparation for the development of the prediction scheme; phase II tackles the aspects associated with the development of the prediction model (module 3) and the assessment of its accuracy (module 4), including the quantification of the uncertainty (module 5); and phase III evolves towards enhancing the prediction accuracy by incorporating aspects of context change detection (module 6) and incremental learning when new data become available (module 7). This framework adeptly addresses all facets of solar PV power production prediction, bridging existing gaps and offering a comprehensive solution to inherent challenges. By seamlessly integrating these elements, our approach stands as a robust and versatile tool for enhancing the precision of solar PV power prediction in real-world applications.

14 SOLAR ENERGY↗

Multistage robust optimization for the day-ahead scheduling of hybrid thermal-hydro-wind-solar systems

The integration of large-scale uncertain and uncontrollable wind and solar power generation has brought new challenges to the operations of modern power systems. In a power system with abundant water resources, hydroelectric generation with high operational flexibility is a powerful tool to promote a higher penetration of wind and solar power generation. In this paper, we study the day-ahead scheduling of a thermal-hydro-wind-solar power system. The uncertainties of renewable energy generation, including uncertain natural water inflow and wind/solar power output, are taken into consideration. We explore how the operational flexibility of hydroelectric generation and the coordination of thermal-hydro power can be utilized to hedge against uncertain wind/solar power under a multistage robust optimization (MRO) framework. To address the computational issue, mixed decision rules are employed to reformulate the original MRO model with a multi-level structure into a bi-level one. Column-and-constraint generation (C &CG) algorithm is extended into the MRO case to solve the bi-level model. The proposed optimization approach is tested in three real-world cases. Furthermore, the computational results demonstrate the capability of hydroelectric generation to promote the accommodation of uncertain wind and solar power.

29 ENERGY PLANNING, POLICY, AND ECONOMY↗

Assessment of Crew Time for Maintenance and Repair Activities for Lunar Surface Missions

NASA is currently evaluating different methods to predict how much time crewmembers will spend conducting repair and maintenance activities on future space missions. As mission scope and spacecraft architectures change, understanding how crew repair and maintenance timelines are impacted by mission operations and technology changes is vital for future mission planning. Past work has been done using historical International Space Station (ISS) data to accurately predict crew habitation and operation timelines, resulting in the development of NASA’s Exploration Crew Time Model (ECTM). However, understanding crew maintenance and repair requirements has posed a unique challenge due to the complexity of available datasets, the probabilistic nature of sub-system failures, and the impacts of reliability growth on failure rates. This paper presents a methodology to collect and condition empirical repair and maintenance time data from available datasets, to extrapolate from that data to estimate projected maintenance and repair times for a lunar Surface Habitat (SH), and to assess how uncertainty in repair time could impact utilization time on the lunar surface. NASA ISS maintenance and crew time data are logged into two central databases: the Maintenance Data Collection (MDC) and the Operations Planning Timeline Integration System (OPTimIS). Separately, each of these two datasets capture only portions of the complete set of data required to generate an accurate assessment of crew time spent on maintenance activities at a sub-system level. To create a more useful crew time estimate for maintenance timelines, the authors developed a methodology to capture relevant data from each set and combine and utilize that data by linking crew time requirements to specific components. The authors compare the failure logs in the MDC to crew activity logs pulled from OPTimIS and then process the data to estimate required repair time for each failure and repair event. The entire maintenance activity dataset is then categorized based on the class of failed component to ensure a significant sample size for each class and accurate crew time estimates for any components lacking relevant data. This resultant component repair time data can be used in the future to generate Mean Time to Repair (MTTR) estimates and confidence intervals for each class of component based on a probabilistic distribution of documented maintenance events. These improved MTTR values can then be applied to candidate element sub-system architectures, along with component Mean Time Between Failure (MTBF) data to generate distributions for potential required system crew repair time estimates for a given mission. The authors applied these modeling methods to a case study of a crewed mission to the planned SH and produced expected corrective maintenance crew time distributions. The results produced an expected corrective maintenance crew time at over 24 hours per mission, and a maintenance crew time distribution that reflects the importance of planning for sufficient maintenance requirements each mission. Repair time distributions can then be used to develop more accurate crew schedules and to assess potential available utilization time.

Crew Time↗

Assessment of Crew Time for Maintenance and Repairs Activities for Lunar Surface Missions

NASA is currently evaluating different methods to predict how much time crewmembers will spend conducting repair and maintenance activities on future space missions. As mission scope and spacecraft architectures change, it will be necessary to understand how crew repair and maintenance timelines are impacted by mission operations and technology changes. Past work has been done using historical ISS data to accurately predict crew habitation and operation timelines, resulting in the development of NASA’s Exploration Crew Time Model (ECTM). However, understanding crew maintenance and repair requirements has posed a unique challenge due to the complexity of available datasets, the probabilistic nature of sub-system failures, and the impacts of reliability growth on failure rates. This paper presents a methodology to collect and condition empirical repair and maintenance time data from available data sets, to extrapolate from that data to estimate projected maintenance and repair times for a lunar Surface Habitat, and to assess how uncertainty in repair time could impact utilization time on the lunar surface. NASA International Space Station (ISS) maintenance and crew time data are logged into two central databases, the Maintenance Data Collection (MDC) and the Operations Planning Timeline Integration System (OPTimIS) respectively. Separately, each of these two datasets capture only portions of the complete set of data required to generate an accurate assessment of crew time spent on maintenance activities at a sub-system level. MDC provides a detailed catalog of failure events and an overview of the failure’s required maintenance and OPTimIS provides a description of crew activities and crew time durations dedicated to maintenance. To create a more useful crew time estimate for maintenance timelines, the authors developed a methodology to capture relevant data from each set and combine and utilize that data by linking crew time requirements to specific components. The authors compare the failure logs in the MDC to crew activity logs pulled from OPTimIS and then process the data to estimate required repair times for each failure event. Data is also classified by the outcome of each repair event, whether the failed component was replaced or whether it was repaired in place. The entire maintenance activity dataset is then categorized based on the class of failed component to allow for a statistically significant sample size for each class and to provide accurate crew time estimates for any components lacking relevant data. This resultant component repair time data can be used in the future to generate Mean Time To Repair (MTTR) estimates and confidence intervals for each class of component based on a probabilistic distribution of documented maintenance events. These improved MTTR values can then be applied to candidate element sub-system architectures, along with component Mean Time Between Failure (MTBF) data to generate distributions for potential required system crew repair time estimates for a given mission. Repair time distributions can then be used to develop more accurate crew schedules and to assess potential available utilization time.

Crew Time↗

NASA's Exploration and In-Space Services (NExIS) Division OSAM-1 Propellant Transfer Subsystem Progress 2020

National Aeronautics and Space Administration (NASA)’s Exploration and In-Space Services (NExIS) Division of Goddard Space Flight Center has been developing technology for the On-orbit Servicing, Assembly and Manufacturing Mission 1 (OSAM-1) to robotically refuel heritage and new satellites on-orbit. OSAM-1, formerly known as Restore-L, successfully passed an important NASA milestone called Key Decision Point-C (KDP-C), receiving agency-level approval for its implementation. The decision point also establishes the mission’s official schedule and budget. The OSAM-1 spacecraft, Servicing Payload and the Space Infrastructure Dexterous Robot (SPIDER) payload will refuel a satellite in space, assemble a communications antenna and manufacture a beam. By demonstrating these capabilities, the mission is advancing never-before tested technologies for use in future missions (by NASA and other government organizations and private industry). The mission is funded by the Technology Demonstration Missions program within NASA’s Space Technology Mission Directorate. This paper covers a review of servicing extensibility and critical technologies that are being developed within NExIS with a focus on the fluid transfer refueling technology within the framework of the Propellant Transfer Subsystem (PTS). An overview of the planned initial technology demonstration servicing mission via the OSAM-1 Space Vehicle is provided as an extension of the technology development progress reported in 20181, and 20192. The general objectives, challenges, and key technologies are presented as an introduction to the context of the OSAM-1 mission, and a precursor to the OSAM-1 PTS specific development status. Development and progress of the Hose Management Assembly (HMA) and Propellant Transfer Assembly (PTA) are discussed. HMA risk reduction test results including those of thermal vacuum testing are presented. Important analytical results are discussed and progress of drawings and procedures developed for the fabrication and testing phase are shown. A summary of the PTS overall verification status and design activities prepared for the critical design peer review are presented. Procurement progress is shown with status on long, medium, and short term efforts to acquire the hardware required to support the mission objectives. Technology development, challenges, and testing status are discussed with particular regard to the OSAM-1 specific key assemblies including the PTA and HMA along with the overall integrated flight mockup of the spacecraft to client fluid transfer testing conducted in the servicing testbeds. The paper concludes with key milestones leading to the goal of on-orbit refueling to be demonstrated in 2024. The overall mission Launch Readiness Date (LRD) has been realigned to accommodate budget profiles and incorporation of additional on-orbit assembly and manufacturing demonstration efforts.

Propellant transfer, satellite servicing↗

SXI prototype mirror mount

The purpose of this contract was to provide optomechanical engineering and fabrication support to the Solar X-ray Imager (SXI) program in the areas of mirror, optical bench and camera assemblies of the telescope. The Center for Applied Optics (CAO) worked closely with the Optics and S&E technical staff of MSFC to develop and investigate the most viable and economical options for the design and fabrication of a number of parts for the various telescope assemblies. All the tasks under this delivery order have been successfully completed within budget and schedule. A number of development hardware parts have been designed and fabricated jointly by MSFC and UAH for the engineering model of SXI. The major parts include a nickel electroformed mirror and a mirror mount, plating and coating of the ceramic spacers, and gold plating of the contact rings and fingers for the camera assembly. An aluminum model of the high accuracy sun sensor (HASS) was also designed and fabricated. A number of fiber optic tapers for the camera assembly were also coated with indium tin oxide and phosphor for testing and evaluation by MSFC. A large number of the SXI optical bench parts were also redesigned and simplified for a prototype telescope. These parts include the forward and rear support flanges, front aperture plate, the graphite epoxy optical bench and a test fixture for the prototype telescope. More than fifty (50) drawings were generated for various components of the prototype telescope. Some of these parts were subsequently fabricated at UAH machine shop or at MSFC or by the outside contractors. UAH also provide technical support to MSFC staff for a number of preliminary and critical design reviews. These design reviews included PDR and CDR for the mirror assembly by United Technologies Optical Systems (UTOS), and the program quarterly reviews, and SXI PDR and CDR. UAH staff also regularly attended the monthly status reviews, and made a significant number of suggestions to improve the design, assembly and alignment of the telescope. Finally, a high level assembly and alignment plan for the entire telescope was prepared by UAH. This plan addresses the sequence of assembly, the required assembly and alignment tolerances, and the methods to verify the alignment at each step during the assembly process. This assembly and alignment plan will be used to assemble and integrate the engineering model (EM) of the telescope. Later on, based on this plan more detailed assembly and alignment procedures will be developed for the lower-level assemblies of SXI.

Source record↗

Using an Automated Air Traffic Simulation Capability for a Parametric Study in Traffic Flow Management

Flight delays occur when demand for capacity-constrained airspace or airports exceeds predicted capacity. Demand for capacity-constrained airspace or airports can be controlled by a series of Traffic Management Initiatives (TMIs), which use departure and airborne delays, as well as pre-departure and airborne reroutes, to manage access to the constrained resources. Two systems exist in current and planned future operations to address imbalances between demand and capacity. The Collaborative Trajectory Options Program (CTOP) reduces demand to constrained resources by assigning strategic departure delay and pre-departure reroutes. Reroutes are selected from Trajectory Options Sets (TOSs) submitted by airlines. As flights approach the constrained resource, the Time-Based Flow Management System (TBFM) is used to assign tactical delay to satisfy constraints. This paper describes experiments performed to study the impact of varying levels of airline participation in CTOP via submission of TOSs on ground delay and flight time, and the impact of departure uncertainty on TBFM delays. Results suggest that as CTOP participation increases, average ground delays decrease for all airlines, but to the greatest extent for airlines participating in CTOP. A threshold in CTOP participation, which varies with the constraint capacity, is identified beyond which there is relatively little further reduction in average ground delays. Similarly, given the likely level of CTOP participation, the capacity reduction for which CTOP would be an appropriate TMI is also identified. Results also suggest that high average departure errors and high variability in departure error can make the prioritization of TBFM internal departures in TBFM metering and scheduling infeasible. Departure errors at current levels are, however, acceptable.

integrated demand management↗

High Altitude Long Endurance Remotely Operated Aircraft - National Airspace System Integration - Simulation IPT: Detailed Airspace Operations Simulation Plan. Version 1.0

The primary goal of Access 5 is to allow safe, reliable and routine operations of High Altitude-Long Endurance Remotely Operated Aircraft (HALE ROAs) within the National Airspace System (NAS). Step 1 of Access 5 addresses the policies, procedures, technologies and implementation issues of introducing such operations into the NAS above pressure altitude 40,000 ft (Flight Level 400 or FL400). Routine HALE ROA activity within the NAS represents a potentially significant change to the tasks and concerns of NAS users, service providers and other stakeholders. Due to the complexity of the NAS, and the importance of maintaining current high levels of safety in the NAS, any significant changes must be thoroughly evaluated prior to implementation. The Access 5 community has been tasked with performing this detailed evaluation of routine HALE-ROA activities in the NAS, and providing to key NAS stakeholders a set of recommended policies and procedures to achieve this goal. Extensive simulation, in concert with a directed flight demonstration program are intended to provide the required supporting evidence that these recommendations are based on sound methods and offer a clear roadmap to achieving safe, reliable and routine HALE ROA operations in the NAS. Through coordination with NAS service providers and policy makers, and with significant input from HALE-ROA manufacturers, operators and pilots, this document presents the detailed simulation plan for Step 1 of Access 5. A brief background of the Access 5 project will be presented with focus on Steps 1 and 2, concerning HALE-ROA operations above FL400 and FL180 respectively. An overview of project management structure follows with particular emphasis on the role of the Simulation IPT and its relationships to other project entities. This discussion will include a description of work packages assigned to the Simulation IPT, and present the specific goals to be achieved for each simulation work package, along with the associated deliverables necessary to achieve these goals and the needs of other Access 5 IPTs. The simulation environment chosen for this task is then outlined. This section includes a description of the system architecture, a list of the necessary assumptions made by the Simulation IPT, and the roles, responsibilities and interactions of simulation participants. The method of simulation conduct is presented in the next section with particular emphasis on scenario development and applicability to evaluation of Step 1 HALE-ROA operations. Following, data collection and analysis methods are discussed for air traffic specialists and air vehicle control station operators. Lastly, a schedule of Step 1 simulation activities is presented for reference.

Source record↗

2020 Exascale Computing Project Annual Meeting (Executive Summary Report)

The Exascale Computing Project (ECP) delivers specific applications, software products, and outcomes on DOE computing facilities. Integration across these elements for specific hardware technologies for exascale system instantiations is fundamental to ECP success. The outcome of the ECP is the delivery of a capable exascale computing ecosystem to provide breakthrough solutions addressing our most critical challenges in scientific discovery, energy assurance, economic competitiveness, and national security. This outcome is not a matter of ensuring more powerful computing systems. The ECP is designed to create more valuable and rapid insights from a wide variety of applications (“capable”), which requires a much higher level of inherent efficacy in all methods, software tools, and ECP-enabled computing technologies to be acquired by DOE laboratories (“ecosystem”). The ECP annual meeting provides a unique opportunity for the core technical expertise in the United States focused on achieving this next plateau of computational science and computing performance to engage in direct discussions on project execution. Face-to-face gatherings in technical communities like this are common and needed for the exchange of scientific ideas and technical performance. The ECP annual meeting stands apart from other technical conferences and meetings in the computing community as it is uniquely and solely focused on the execution of the ECP and the integration of technical activities leading to the creation of the exascale computing ecosystem for the future. The direct interaction of key critical technical staff, who are leaders in their respective fields, and the resulting give-and-take between software, applications, and hardware and the technical co-design therein, is unique and essential to the effective execution of the ECP. The first annual meeting was held in Knoxville, Tennessee, January 31 – February 2, 2017 and brought together, for the first time, a diverse collection of researchers from 16 DOE national laboratories as well as university computer and computational science researchers to discuss shared problems and joint solutions for the development of a capable exascale computing ecosystem. These interactions resulted in focused technical plans and an energized community centered on advances for ECP. The second annual meeting was held in Knoxville, Tennessee, February 5–9, 2018. It included 643 individual thought leaders and performers in application development, software research and deployment, and hardware research and integrators, all of whom are part of the multifaceted, billion dollar HPC community. This meeting provided a platform to discuss and disseminate numerous examples where researchers with common goals and synergistic solutions came together for the first time to deliver tangible results. Additionally, at the 2018 meeting, ECP researchers had the opportunity to digest all US HPC vendor R&D product roadmaps pointing to exascale – not only to learn how their research can play a role, but, more importantly, to influence those roadmaps to ensure successful delivery on DOE applications that will contribute to (if not solve) problems of national interest in national security, science, energy, and health, as well as growing security threats. The third annual meeting was held in Houston, Texas, January 14–17, 2019. With a 19% increase in the number of registrations (768 people), and the change in location, the third annual meeting was considered the most impactful of the three at the time. The new website provided a better platform for the dissemination of the content, the new venue as a meeting hotel instead of a conference center facilitated interactions and discussions after event hours, and the addition of an award-winning mobile event conference app (Whova) transformed dramatically the attendee experience at the event. This fourth annual meeting was held in Houston, Texas, February 3-7, 2020. This meeting had an increase in the number of attendees for a total of 824 people registered (782 attendees) and included numerous enhancements based on feedback and lessons learned from previous meetings, some of which are listed here: Improved quality of the sessions, their material and the whole program.; Had more industry participation and addition of external collaborators from overseas.; Published the full agenda earlier to better accommodate attendance and travel plans based on schedule.; Centralized all sessions in one venue.; Provided additional hotels and room blocks for the attendees.; Improved communication with the audience (links, material, directions, notifications, etc.) to go paperless.; Enhanced side meeting scheduling, management and user experience.; Made available additional space and tables for impromptu meetings and side discussions.; Improved IT and A/V solutions for speakers. In addition, our final survey captured the following points as opportunities for improvement in future meetings: consider a different meeting location that is more pedestrian friendly, reduce talks during working meals to allow more collaboration and informal time, adapt the agenda to acknowledge attendees from different timezones, consider recording some of the tutorials and/or sessions to share broadly with the HPC community, have a larger poster room, provide additional power strips, and improve the WiFi.

97 MATHEMATICS AND COMPUTING↗

Using an Automated Air Traffic Simulation Capability for a Parametric Study in Traffic Flow Management

Flight delays occur when demand for capacity-constrained airspace or airports exceeds predicted capacity. Demand for capacity-constrained airspace or airports can be controlled by a series of Traffic Management Initiatives (TMIs), which use departure and airborne delays, as well as pre-departure and airborne reroutes, to manage access to the constrained resources. Two systems exist in current and planned future operations to address imbalances between demand and capacity. The Collaborative Trajectory Options Program (CTOP) reduces demand to constrained resources by assigning strategic departure delay and pre-departure reroutes. Reroutes are selected from Trajectory Options Sets (TOSs) submitted by airlines. As flights approach the constrained resource, the Time-Based Flow Management System (TBFM) is used to assign tactical delay to satisfy constraints. This paper describes experiments performed to study the impact of varying levels of airline participation in CTOP via submission of TOSs on ground delay and flight time, and the impact of departure uncertainty on TBFM delays. Results suggest that as CTOP participation increases, average ground delays decrease for all airlines, but to the greatest extent for airlines participating in CTOP. A threshold in CTOP participation, which varies with the constraint capacity, is identified beyond which there is relatively little further reduction in average ground delays. Similarly, given the likely level of CTOP participation, the capacity reduction for which CTOP would be an appropriate TMI is also identified. Results also suggest that high average departure errors and high variability in departure error can make the prioritization of TBFM internal departures in TBFM metering and scheduling infeasible. Departure errors at current levels are, however, acceptable.

CTOP↗

The New Millenium Program: Serving Earth and Space Sciences

NASA has exciting plans for space science and Earth observations during the next decade. A broad range of advanced spacecraft and measurement technologies will be needed to support these plans within the existing budget and schedule constraints. Many of these technology needs are common to both NASA's Office of Earth Science (OES) and Office of Space Sciences (OSS). Even though some breakthrough technologies have been identified to address these needs, project managers have traditionally been reluctant to incorporate them into flight programs because their inherent development risk. To accelerate the infusion of new technologies into its OES and OSS missions, NASA established the New Millennium Program (NMP). This program analyzes the capability needs of these enterprises, identifies candidate technologies to address these needs, incorporates advanced technology suites into validation flights, validates them in the relevant space environment, and then proactively infuses the validated technologies into future missions to enhance their capabilities while reducing their life cycle cost. The NMP employs a cross-enterprise Science Working Group, the NASA Enterprise science and technology roadmaps to define the capabilities needed by future Earth and Space science missions. Additional input from the science community is gathered through open workshops and peer-reviewed NASA Research Announcement (NRAs) for advanced measurement concepts. Technology development inputs from the technology organizations within NASA, other government agencies, federally funded research and development centers (FFRDC's), U.S. industry, and academia are sought to identify breakthrough technologies that might address these needs. This approach significantly extends NASA's technology infrastructure. To complement other flight test programs that develop or validate of individual components, the NMP places its highest priority on system-level validations of technology suites in the relevant space environment. This approach is not needed for all technologies, but it is usually essential to validate advanced system architectures or new measurement concepts. The NMP has recently revised its processes for defining candidate validation flights, and selecting technologies for these flights. The NMP now employs integrated project formulation teams, 'Which include scientists, technologists, and mission planners, to incorporate technology suites into candidate validation flights. These teams develop competing concepts, which can be rigorously evaluated prior to selection for flight. The technology providers for each concept are selected through an open, competitive, process during the project formulation phase. If their concept is selected for flight, they are incorporated into the Project Implementation Team, which develops, integrates, tests, launches, and operates the technology validation flight. Throughout the project implementation phase, the Implementation Team will document and disseminate their validation results to facilitate the infusion of their validated technologies into future OSS and OES science missions. The NMP has successfully launched its first two Deep Space flights for the OSS, and is currently implementing its first two Earth Orbiting flights for the OES. The next OSS and OES flights are currently being defined. Even though these flights are focused on specific Space Science and Earth Science themes, they are designed to validate a range of technologies that could benefit both enterprises, including advanced propulsion, communications, autonomous operations and navigation, multifunctional structures, microelectronics, and advanced instruments. Specific examples of these technologies will be provided in our presentation. The processes developed by the NMP also provide benefits across the Space and Earth Science enterprises. In particular, the extensive, nation-wide technology infrastructure developed by the NMP enhances the access to breakthrough technologies for both enterprises.

Li, Fuk K.↗

Evolving Design Criteria for Very Large Aperture Space Based Telescopes and Their Influence on the Need for Integrated Tools in the Optimization Process

NASA's Advanced Mirror Technology Development (AMTD) program has been developing the means to design and build the future generations of space based telescopes. With the nearing completion of the James Webb Space Telescope (JWST), the astrophysics community is already starting to define the requirements for follow-on observatories. The restrictions of available launch vehicles and the possibilities of planned future vehicles have fueled the competition between monolithic primaries (with better optical quality) and segmented primaries (with larger apertures, but with diffraction, costs and figure control issues). Regardless of the current shroud sizes and lift capacities, these competing architectures share the need for rapid design tools. As part of the AMTD program a number of tools have been developed and tested to speed up the design process. Starting with the Arnold Mirror Modeler (which creates Finite Element Models (FEM) for structural analysis) and now also feeds these models into thermal stability analyses. They share common file formats and interchangeable results. During the development of the program, numerous trade studies were created for 4-meter and 8-meter monolithic primaries, complete with support systems. Evaluation of these results has led to a better understanding of how the specification drives the results. This paper will show some of the early trade studies for typical specification requirements such as lowest mirror bending frequency and suspension system lowest frequency. The results use representative allowable stress values for each mirror substrate material and construction method and generic material properties. These studies lead to some interesting relationships between feasible designs and the realities of actually trying to build these mirrors. Much of the traditional specifications were developed for much smaller systems, where the mass and volume of the primary where a small portion of the overall satellite. JWST shows us that as the aperture grows, the primary takes up the majority of the mass and volume and the established rules need to be adjusted. For example, a small change in lowest frequency requirement can change the cost by millions of dollars. The paper uses numerous trade studies created during the software development phase of the Arnold Mirror Modeler to illustrate the influences of system specifications on the design space. The future telescopes will require better performance, stability and documented feasibility to meet the hurdles of today's budget and schedules realities. AMTD is developing the tools, but the basic system planning mentality also has to adopt to the requirements of these very large and complex physical structures.

Arnold, William R., Sr.↗

Evaluating Liftoff Debris for NASA’s Space Launch System (SLS) Prior to the Artemis I Launch

The SLS Artemis I launch vehicle is the first of several planned Artemis launch vehicles, with a number of design differences from earlier NASA missions that incur liftoff debris risk to the mission. As a test vehicle, the Artemis I hardware also endured environments and tests not planned for future missions, which led to several additional factors contributing to an evolving liftoff debris risk to the SLS vehicle. This paper will summarize these risk factors and address the processes used to evaluate and communicate the risks to support a successful Artemis I launch. It will discuss how the evolving risks that were quantified and evaluated by a Cross-Program team of debris Subject Matter Experts to mitigate liftoff debris hazards and communicate updated risk to the SLS vehicle. This process was performed through the inaugural use of an SLS debris day-of-launch (DOL) standard operating procedure that will be used for subsequent Artemis missions. This paper addresses the risk of liftoff debris, debris released by the vehicle or from the launch pad during liftoff through vehicle tower clear. Expected liftoff debris is well understood from previous NASA programs’ experience and from tests of materials, processes and functions that are known to release liftoff debris. These expected sources were assessed and cleared well ahead of launch day. However, given the ever-changing schedules and environments, processes were in place to evaluate any additional potential liftoff debris risks identified during launch countdown. Although many of the Artemis vehicle hardware components are similar to those on the NASA Shuttle Program, there are important differences in the architecture of the Artemis I vehicle which require new assessments of liftoff debris risk for the Artemis missions. The more favorable Artemis crew module location and surfaces are far less vulnerable to debris impacts; however, the longer vehicle can result in higher liftoff debris impact energies to those components on the aft end of the vehicle. Additionally, the positional change of the RS-25 liquid engines to nearer the Booster nozzle exit plane along with the change in Booster throat plug design is a disadvantage to the overall liftoff debris risk which resulted in additional test and analysis efforts for evaluating the integrated vehicle debris risk. In spite of the comprehensive tests and analyses of Artemis I expected liftoff debris, a number of additional tests/processes were completed prior to the Artemis I mission that were required to support a complete understanding of a new launch vehicle, but increased the risk of releasing liftoff debris. The hardware endured several additional cryogenic loading cycles, including the Green Run tests at Stennis Space Center, Wet Dress Rehearsals at Kennedy Space Center, and multiple launch attempts. Each of these cycles induced stresses in the thermal protection system (TPS) materials, increasing the risk of damage to and release of the TPS. Additionally, induced and weather environmental factors that could increase the likelihood of debris release were significant. Vibrations and stresses in the TPS were induced by a required roll-back to the Vehicle Assembly Building before Hurricane Ian to protect the vehicle from damage by high winds. Wind damage and potential internal stresses to several outer mold line materials on the integrated SLS vehicle and mobile launcher were caused by weathering Hurricane Nicole at Pad 39B the week before launch. A thorough imagery scan of the vehicle was performed after each event and the damage observed was repaired, removed, or assessed and the risk to the mission evaluated. Mitigation of debris risk can occur by tests and analyses to show debris impacted components as damage tolerant, by new/improved processes for prevention of debris availability, or redesign. Risk mitigation processes for Artemis I-specific liftoff debris events and the development and use of the SLS debris day of launch (DOL) procedures that will be used for subsequent Artemis missions will be described.

Space Launch System↗

Evaluating Liftoff Debris for NASA’s Space Launch System (SLS) Prior to the Artemis I Launch

The SLS Artemis I launch vehicle is the first of several planned Artemis launch vehicles, with a number of design differences from earlier NASA missions that incur liftoff debris risk to the mission. As a test vehicle, the Artemis I hardware also endured environments and tests not planned for future missions, which led to several additional factors contributing to an evolving liftoff debris risk to the SLS vehicle. This paper will summarize these risk factors and address the processes used to evaluate and communicate the risks to support a successful Artemis I launch. It will discuss how the evolving risks that were quantified and evaluated by a Cross-Program team of debris Subject Matter Experts to mitigate liftoff debris hazards and communicate updated risk to the SLS vehicle. This process was performed through the inaugural use of an SLS debris day-of-launch (DOL) standard operating procedure that will be used for subsequent Artemis missions. This paper addresses the risk of liftoff debris, debris released by the vehicle or from the launch pad during liftoff through vehicle tower clear. Expected liftoff debris is well understood from previous NASA programs’ experience and from tests of materials, processes and functions that are known to release liftoff debris. These expected sources were assessed and cleared well ahead of launch day. However, given the ever-changing schedules and environments, processes were in place to evaluate any additional potential liftoff debris risks identified during launch countdown. Although many of the Artemis vehicle hardware components are similar to those on the NASA Shuttle Program, there are important differences in the architecture of the Artemis I vehicle which require new assessments of liftoff debris risk for the Artemis missions. The more favorable Artemis crew module location and surfaces are far less vulnerable to debris impacts; however, the longer vehicle can result in higher liftoff debris impact energies to those components on the aft end of the vehicle. Additionally, the positional change of the RS-25 liquid engines to nearer the Booster nozzle exit plane along with the change in Booster throat plug design is a disadvantage to the overall liftoff debris risk which resulted in additional test and analysis efforts for evaluating the integrated vehicle debris risk. In spite of the comprehensive tests and analyses of Artemis I expected liftoff debris, a number of additional tests/processes were completed prior to the Artemis I mission that were required to support a complete understanding of a new launch vehicle, but increased the risk of releasing liftoff debris. The hardware endured several additional cryogenic loading cycles, including the Green Run tests at Stennis Space Center, Wet Dress Rehearsals at Kennedy Space Center, and multiple launch attempts. Each of these cycles induced stresses in the thermal protection system (TPS) materials, increasing the risk of damage to and release of the TPS. Additionally, induced and weather environmental factors that could increase the likelihood of debris release were significant. Vibrations and stresses in the TPS were induced by a required roll-back to the Vehicle Assembly Building before Hurricane Ian to protect the vehicle from damage by high winds. Wind damage and potential internal stresses to several outer mold line materials on the integrated SLS vehicle and mobile launcher were caused by weathering Hurricane Nicole at Pad 39B the week before launch. A thorough imagery scan of the vehicle was performed after each event and the damage observed was repaired, removed, or assessed and the risk to the mission evaluated. Mitigation of debris risk can occur by tests and analyses to show debris impacted components as damage tolerant, by new/improved processes for prevention of debris availability, or redesign. Risk mitigation processes for Artemis I-specific liftoff debris events and the development and use of the SLS debris day of launch (DOL) procedures that will be used for subsequent Artemis missions will be described.

Space Launch System↗

SOAREX-8 Suborbital Experiments 2015 - A New Paradigm for Small Spacecraft Communication

In 2015 NASA plans to launch a payload to 280 Km altitude on a sounding rocket from the Wallops Flight Facility. This payload will contain several novel technologies that work together to demonstrate methodologies for space sample return missions and for nanosatellite communications in general. The payload will deploy and test an Exo-Brake, which slows the payload aerodynamically, providing eventual de-orbit and recovery of future ISS samples through a Small Payload Quick Return project. In addition, this flight addresses future Mars mission entry technology, space-to-space communications using the Iridium Short Messaging Service (SMS), GPS tracking, and wireless sensors using the ZigBee protocol. SOAREX-8 is being assembled and tested at Ames Research Center (ARC) and the NASA Engineering and Safety Center (NESC) is funding sensor and communications work. Open source Arduino technology and software are used for system control. The ZigBee modules used are XBee units that connect analog sensors for temperature, air pressure and acceleration measurement wirelessly to the payload telemetry system. Our team is developing methods for power distribution and module mounting, along with software for sensor integration, data assembly and downlink. We have demonstrated relaying telemetry to the ground using the Iridium satellite constellation on a previous flight, but the upcoming flight will be the first time we integrate useful flight test data from a ZigBee wireless sensor network. Wireless sensor data will measure the aerodynamic efficacy of the Exo-Brake permitting further on orbit flight tests of improved designs. The Exo-Brake is 5 sq m in area and will be stored in a container and deployed during ascent once the payload is jettisoned from the launch vehicle. We intend to further refine the hardware and continue testing on balloon launches, future sounding rocket flights and on nanosatellite missions. The use of standards-based and open source hardware/software has allowed for this project to be completed with a very modest budget and a challenging schedule. There is a wealth of hardware and software available for both the Arduino platform and the XBee, all low-cost or open-source. Along with the Exo-Brake hardware and deployment discussion, this paper will describe in detail the system architecture emphasizing the successful use of open source hardware and software to minimize effort and cost. Testing procedures, radio frequency interference (RFI) mitigation, success criteria and expected results will also be discussed. The use of Iridium short messaging capability for space-to-space links, standards-based wireless sensor networks, and other innovative communications technology are also presented.

aerobrake↗

Development and Demonstration of a Fuel-Efficient, Class 8 Tractor & Trailer Engine System (SuperTruck II)

Navistar presents the SuperTruck II (ST II) Final Report to the Unites States Department of Energy (US DOE), which covers the five Budget Periods (BPs) from 10-1-2016 through 6-30-2022. For ST II, Navistar built on the achievements of the SuperTruck I (ST I) Program as a catalyst to continue critical research, design and development, testing, and operations to reach the ambitious goals of the ST II project. This approach allowed Navistar to continue contributing to the essential needs of our nation for safe, efficient, and cost-effective delivery of goods and services, as we reduced negative environmental effects and improved operational productivity. This document contains information specified in DOE F 4600.2, Final Scientific/Technical Report DOE F 241.3, B. SCIENTIFIC/TECHNICAL REPORTS, explaining how we met and exceeded program requirements. Throughout this Final Report, Navistar extracted information from documents prepared during the project that represent our management, design and development, building, and testing efforts to meet and exceed SuperTruck II project goals. Navistar followed Plan requirements to achieve / exceed Project Objectives: a) >100% improvement in vehicle freight efficiency (FE) (on ton-MPG basis) relative to 2009 baseline with stretch goal of 140% improvement [actual: 170%); b) >55% engine brake thermal efficiency (BTE) demonstrated in operational engine at a 65-mph cruise point on a dynamometer – ≥31% increase from 2009 baseline [actual: 55.20% of combined BTE) ; and c) development and implementation of commercially cost effective technologies (in terms of a simple payback). Technology selection / development path focused on developing technologies applicable for production within 3-year approach, while ensuring technology readiness and cost of ownership for end users. The Program was organized into five budget periods: Requirements / Technology Assessment and Initial Hardware Testing; Technology Development and Concept Readiness Demonstration; Technology Finalization and Validation Tractor / Trailer Fabrication, Integration and Commissioning Demonstration; and Fuel Economy (FE) and Brake Thermal Efficiency (BTE) and Program Completion. Leadership was provided by DOE, with tasks performed by laboratories (Argonne National Laboratory, Lawrence Livermore National Laboratory); partners at Bosch, TPI, Dana, and J.B. Hunt; , and support from University of Michigan and Clemson University. Navistar lead this team with Principal Investigator / Contracting Officer; Project Manager (PM); Vehicle, Engine, and Aftertreatment Engineers; Finance Manager, Technical Program Leads, and Legal/IP; and other key personnel. Work also included personnel in risk management; funding / budget / finance. Work involved analysis, development, testing, and down selection of individual/system engine, aftertreatment, and vehicle technologies, with integration of selected technologies into a prototype vehicle for demonstration of fuel-efficiency gain. Work also included component/integrated system level development of truck and trailer aerodynamics, base engine efficiency, advanced aftertreatment, combustion efficiency, waste heat recovery, hybrid powertrain, reduced rolling resistance, weight reduction, idle reduction, and driver feedback. As ST II progressed, Navistar performed computer-based modeling / simulations of technologies focused on the primary operational areas: Engine, Aftertreatment, and Vehicle. During the ST II Program, the COVID Virus outbreak unexpectedly challenged by the effects of, which affected staffing, scheduling, design, supplies, availability of materials, production procedures, and testing. The DOE responded by extending the program by three quarters to ensure that project tasks were completed for this vital project. Focus continued on analyzing, developing, testing, and down selecting individual-/system-level engine and vehicle technologies for integration of the final selected technologies into a prototype vehicle that would demonstrate fuel-efficiency gains made possible through these technologies. This included component/integrated system-level development of truck and trailer aerodynamics, base engine efficiency, advanced aftertreatment, combustion efficiency, waste heat recovery, solar power, distributed and intelligent vehicle power, hybrid powertrain, reduced rolling resistance, weight reduction, idle reduction, and driver feedback. Throughout the program, function, reliability, and performance at all levels were ensured through testing. Proof of this approach was demonstrated in multiple, on-road demonstrations: Scenario A (Flatland) Fuel Economy, Scenario B (Hilly) Fuel Economy, and City Cycle Tests. Other benefits derived from ST II included new/improved products, publications, patents, and next-step capabilities related to electric/hydrogen vehicles and autonomous driving.

Zukouski, Russ↗