SEARCH · Search NASA

Results for “Rescheduling”

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.

SourceResearch connectionFrom yearThrough year

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

At least 91 records · Page 5

All sources NASA NTRS DOE OSTI

NASA NTRS2012

Role of Computational Fluid Dynamics and Wind Tunnels in Aeronautics R and D

The purpose of this report is to investigate the status and future projections for the question of supplantation of wind tunnels by computation in design and to intuit the potential impact of computation approaches on wind-tunnel utilization all with an eye toward reducing the infrastructure cost at aeronautics R&D centers. Wind tunnels have been closing for myriad reasons, and such closings have reduced infrastructure costs. Further cost reductions are desired, and the work herein attempts to project which wind-tunnel capabilities can be replaced in the future and, if possible, the timing of such. If the possibility exists to project when a facility could be closed, then maintenance and other associated costs could be rescheduled accordingly (i.e., before the fact) to obtain an even greater infrastructure cost reduction.

Malik, Murjeeb R.↗

NASA NTRS2013

Two Mechanisms to Avoid Control Conflicts Resulting from Uncoordinated Intent

This software implements a real-time access control protocol that is intended to make all connected users aware of the presence of other connected users, and which of them is currently in control of the system. Here, "in control" means that a single user is authorized and enabled to issue instructions to the system. The software The software also implements a goal scheduling mechanism that can detect situations where plans for the operation of a target system proposed by different users overlap and interact in conflicting ways. In such situations, the system can either simply report the conflict (rejecting one goal or the entire plan), or reschedule the goals in a way that does not conflict. The access control mechanism (and associated control protocol) is unique. Other access control mechanisms are generally intended to authenticate users, or exclude unauthorized access. This software does neither, and would likely depend on having some other mechanism to support those requirements.

Mishkin, Andrew H.↗

NASA NTRS2015

Real-Time Kennedy Space Center and Cape Canaveral Air Force Station High-Resolution Model Implementation and Verification

NASA's Launch Services Program, Ground Systems Development and Operations, Space Launch System and other programs at Kennedy Space Center (KSC) and Cape Canaveral Air Force Station (CCAFS) use the daily and weekly weather forecasts issued by the 45th Weather Squadron (45 WS) as decision tools for their day-to-day and launch operations on the Eastern Range (ER). Examples include determining if they need to limit activities such as vehicle transport to the launch pad, protect people, structures or exposed launch vehicles given a threat of severe weather, or reschedule other critical operations. The 45 WS uses numerical weather prediction models as a guide for these weather forecasts, particularly the Air Force Weather Agency (AFWA) 1.67 km Weather Research and Forecasting (WRF) model. Considering the 45 WS forecasters' and Launch Weather Officers' (LWO) extensive use of the AFWA model, the 45 WS proposed a task at the September 2013 Applied Meteorology Unit (AMU) Tasking Meeting requesting the AMU verify this model. Due to the lack of archived model data available from AFWA, verification is not yet possible. Instead, the AMU proposed to implement and verify the performance of an ER version of the high-resolution WRF Environmental Modeling System (EMS) model configured by the AMU (Watson 2013) in real time. Implementing a real-time version of the ER WRF-EMS would generate a larger database of model output than in the previous AMU task for determining model performance, and allows the AMU more control over and access to the model output archive. The tasking group agreed to this proposal; therefore the AMU implemented the WRF-EMS model on the second of two NASA AMU modeling clusters. The AMU also calculated verification statistics to determine model performance compared to observational data. Finally, the AMU made the model output available on the AMU Advanced Weather Interactive Processing System II (AWIPS II) servers, which allows the 45 WS and AMU staff to customize the model output display on the AMU and Range Weather Operations (RWO) AWIPS II client computers and conduct real-time subjective analyses.

Meteorology↗

NASA NTRS2013

Surface Hold Advisor Using Critical Sections

The Surface Hold Advisor Using Critical Sections is a system and method for providing hold advisories to surface controllers to prevent gridlock and resolve crossing and merging conflicts among vehicles traversing a vertex-edge graph representing a surface traffic network on an airport surface. The Advisor performs pair-wise comparisons of current position and projected path of each vehicle with other surface vehicles to detect conflicts, determine critical sections, and provide hold advisories to traffic controllers recommending vehicles stop at entry points to protected zones around identified critical sections. A critical section defines a segment of the vertex-edge graph where vehicles are in crossing or merging or opposite direction gridlock contention. The Advisor detects critical sections without reference to scheduled, projected or required times along assigned vehicle paths, and generates hold advisories to prevent conflicts without requiring network path direction-of-movement rules and without requiring rerouting, rescheduling or other network optimization solutions.

Law, Caleb Hoi Kei↗

NASA NTRS2015

Software Testbed for Developing and Evaluating Integrated Autonomous Subsystems

To implement fault tolerant autonomy in future space systems, it will be necessary to integrate planning, adaptive control, and state estimation subsystems. However, integrating these subsystems is difficult, time-consuming, and error-prone. This paper describes Intelliface/ADAPT, a software testbed that helps researchers develop and test alternative strategies for integrating planning, execution, and diagnosis subsystems more quickly and easily. The testbed's architecture, graphical data displays, and implementations of the integrated subsystems support easy plug and play of alternate components to support research and development in fault-tolerant control of autonomous vehicles and operations support systems. Intelliface/ADAPT controls NASA's Advanced Diagnostics and Prognostics Testbed (ADAPT), which comprises batteries, electrical loads (fans, pumps, and lights), relays, circuit breakers, invertors, and sensors. During plan execution, an experimentor can inject faults into the ADAPT testbed by tripping circuit breakers, changing fan speed settings, and closing valves to restrict fluid flow. The diagnostic subsystem, based on NASA's Hybrid Diagnosis Engine (HyDE), detects and isolates these faults to determine the new state of the plant, ADAPT. Intelliface/ADAPT then updates its model of the ADAPT system's resources and determines whether the current plan can be executed using the reduced resources. If not, the planning subsystem generates a new plan that reschedules tasks, reconfigures ADAPT, and reassigns the use of ADAPT resources as needed to work around the fault. The resource model, planning domain model, and planning goals are expressed using NASA's Action Notation Modeling Language (ANML). Parts of the ANML model are generated automatically, and other parts are constructed by hand using the Planning Model Integrated Development Environment, a visual Eclipse-based IDE that accelerates ANML model development. Because native ANML planners are currently under development and not yet sufficiently capable, the ANML model is translated into the New Domain Definition Language (NDDL) and sent to NASA's EUROPA planning system for plan generation. The adaptive controller executes the new plan, using augmented, hierarchical finite state machines to select and sequence actions based on the state of the ADAPT system. Real-time sensor data, commands, and plans are displayed in information-dense arrays of timelines and graphs that zoom and scroll in unison. A dynamic schematic display uses color to show the real-time fault state and utilization of the system components and resources. An execution manager coordinates the activities of the other subsystems. The subsystems are integrated using the Internet Communications Engine (ICE). an object-oriented toolkit for building distributed applications.

Testbed↗

NASA NTRS2015

Real-Time Kennedy Space Center and Cape Canaveral Air Force Station High-Resolution Model Implementation and Verification

Customer: NASA's Launch Services Program (LSP), Ground Systems Development and Operations (GSDO), and Space Launch System (SLS) programs. NASA's LSP, GSDO, SLS and other programs at Kennedy Space Center (KSC) and Cape Canaveral Air Force Station (CCAFS) use the daily and weekly weather forecasts issued by the 45th Weather Squadron (45 WS) as decision tools for their day-to-day and launch operations on the Eastern Range (ER). For example, to determine if they need to limit activities such as vehicle transport to the launch pad, protect people, structures or exposed launch vehicles given a threat of severe weather, or reschedule other critical operations. The 45 WS uses numerical weather prediction models as a guide for these weather forecasts, particularly the Air Force Weather Agency (AFWA) 1.67 kilometer Weather Research and Forecasting (WRF) model. Considering the 45 WS forecasters' and Launch Weather Officers' (LWO) extensive use of the AFWA model, the 45 WS proposed a task at the September 2013 Applied Meteorology Unit (AMU) Tasking Meeting requesting the AMU verify this model. Due to the lack of archived model data available from AFWA, verification is not yet possible. Instead, the AMU proposed to implement and verify the performance of an ER version of the AMU high-resolution WRF Environmental Modeling System (EMS) model (Watson 2013) in real-time. The tasking group agreed to this proposal; therefore the AMU implemented the WRF-EMS model on the second of two NASA AMU modeling clusters. The model was set up with a triple-nested grid configuration over KSC/CCAFS based on previous AMU work (Watson 2013). The outer domain (D01) has 12-kilometer grid spacing, the middle domain (D02) has 4-kilometer grid spacing, and the inner domain (D03) has 1.33-kilometer grid spacing. The model runs a 12-hour forecast every hour, D01 and D02 domain outputs are available once an hour and D03 is every 15 minutes during the forecast period. The AMU assessed the WRF-EMS 1.33-kilometer domain model performance for the 2014 warm season (May-September). Verification statistics were computed using the Model Evaluation Tools, which compared the model forecasts to observations. The mean error values were close to 0 and the root mean square error values were less than 1.8 for mean sea-level pressure (millibars), temperature (degrees Kelvin), dewpoint temperature (degrees Kelvin), and wind speed (per millisecond), all very small differences between the forecast and observations considering the normal magnitudes of the parameters. The precipitation forecast verification results showed consistent under-forecasting of the precipitation object size. This could be an artifact of calculating the statistics for each hour rather than for the entire 12-hour period. The AMU will continue to generate verification statistics for the 1.33-kilometer WRF-EMS domain as data become available in future cool and warm seasons. More data will produce more robust statistics and reveal a more accurate assessment of model performance. Once the formal task was complete, the AMU conducted additional work to better understand the wind direction results. The results were stratified diurnally and by wind speed to determine what effects the stratifications would have on the model wind direction verification statistics. The results are summarized in the addendum at the end of this report. In addition to verifying the model's performance, the AMU also made the output available in the Advanced Weather Interactive Processing System II (AWIPS II). This allows the 45 WS and AMU staff to customize the model output display on the AMU and Range Weather Operations AWIPS II client computers and conduct real-time subjective analyses. In the future, the AMU will implement an updated version of the WRF-EMS model that incorporates local data assimilation. This model will also run in real-time and be made available in AWIPS II.

Numerical Weather Prediction↗

NASA NTRS2017

Increasing Crew Autonomy for Long Duration Exploration Missions: Self-Scheduling

Over the last three years, we have been investigating the operational concept of crew self-scheduling as a method of increasing crew autonomy for future exploration missions. Through Playbook, a planning and scheduling software tool, we have incrementally increased the ability for Earth analog mission crews to modify their schedules. Playbook allows the crew to add new activities from scratch, add new activities or groups of activities through a Task List, and reschedule or reassign flexible activities. The crew is also able to identify if plan modifications create violations, i.e., plan constraints not being met. This paper summarizes our observations with qualitative evidence from four NASA Extreme Environment Mission Operations (NEEMO) analog missions that supported self-scheduling as a feasible operational concept.

crew autonomy↗

NASA NTRS2016

In the Hot Seat: STS-115 Lightning Strike Stand Down Debate - NASA Case Study

There is no way the PIC's could have seen any current' was the gist of Mike Griffin's assessment. Griffin was the NASA Administrator at the time. The buck stopped at his desk. Holding a napkin out to Pat Lampton, Griffin showed Lampton the calculations he'd made over dinner that predicted that the Pyrotechnic Initiator Controllers (PIC's) at the base of the Space Shuttle Solid Rocket Boosters (SRBs) were fine. A lightning strike the day before, the worst ever experienced with a Space Shuttle on the launch pad, caused a halt to the launch count down as technicians, engineers, and managers scrambled identify any damage to the launch system. SRB technicians and engineers assessed the data against their Lightning Strike Re-Test Requirements, determining that all but one of the requirements could be checked if they resumed the countdown. For the one remaining requirement, testing the integrity of the PIC's would require 96 hours to set up, test, and reassemble. The engineers were convinced that there was no way to do calculations to show the PIC's were okay. The only option was to stand down. It was SRB Deputy Project Manager (PM) Pat Lampton's responsibility to decide what the SRB project position needed to be to certify that their hardware was safe to fly. He had to communicate that decision to the Mission Management Team (MMT) as a Go or No Go position to resume the count down. If the answer was Go they could still meet a delayed, but acceptable launch schedule. If the answer was No Go, rescheduling the launch would be a grueling shuffling of hardware, personnel, and mission timelines to accommodate Russian missions to the Space Station, supplies for the launch, and personnel manning launch operations. On top of that, Hurricane Ernesto was spinning off the coast of Florida, threatening the need for the Shuttle to roll back to the hangar if they waited too long.

Kummer, Lizette↗

NASA NTRS2017

Close Range Photogrammetry in Space - Measuring the On-Orbit Clearance between Hardware on the International Space Station

When photogrammetrists read an article entitled "Photogrammetry in Space" they immediately think of terrestrial mapping using satellite imagery. However in the last 19 years the roll of close range photogrammetry in support of the manned space flight program has grown exponentially. Management and engineers have repeatedly entrusted the safety of the vehicles and their crews to the results of photogrammetric analysis. In February 2010, the Node 3 module was attached to the port side Common Berthing Mechanism (CBM) of the International Space Station (ISS). Since this was not the location at which the module was originally designed to be located on the ISS, coolant lines containing liquid ammonia, were installed externally from the US Lab to Node 3 during a spacewalk. During mission preparation I had developed a plan and a set of procedures to have the astronauts acquire stereo imagery of these coolant lines at the conclusion of the spacewalk to enable us to map their as-installed location relative to the rest of the space station. Unfortunately, the actual installation of the coolant lines took longer than expected and in an effort to wrap up the spacewalk on time, the mission director made a real-time call to drop the photography. My efforts to reschedule the photography on a later spacewalk never materialized, so rather than having an as-installed model for the location of coolant lines, the master ISS CAD database continued to display an as-designed model of the coolant lines. Fast forward to the summer of 2015, the ISS program planned to berth a Japanese cargo module to the nadir Common Berthing Mechanism (CBM), immediately adjacent to the Node 3 module. A CAD based clearance analysis revealed a negative four inch clearance between the ammonia lines and a thruster nozzle on the port side of the cargo vehicle. Recognizing that the model of the ammonia line used in the clearance analysis was "as-designed" rather than "as-installed", I was asked to determine the real clearance between the ammonia lines and expected position of the thruster bell using existing on-orbit imagery. Imagery of the area of interest, taken several years earlier from the Space Shuttle during a fly-around of the ISS, was found and used to set a stereo pair. Space Vision System Targets and Handrail bolts measured in the ISS analytical coordinate system (ISSACS) prior to launch, were used to obtain an absolute orientation so all photogrammetric measurement's would be in the ISSACS coordinate system. Coordinates for the design location of the edges of the thruster bell, when the cargo vehicle was fully berthed to the ISS, were displayed in 3-D relative to the as-installed ammonia lines. This immediately revealed a positive clearance, which was later quantified to be a minimum of 10" +/0.5". The analysis was completed over a single weekend by a single analyst. Using updated imagery, acquired from the station's robotic arm, a complete as-installed model of the coolant lines was generated from stereo photography and replaced the design model in the master ISS CAD database.

Liddle, Donn↗

NASA NTRS2017

Increasing Crew Autonomy for Long Duration Exploration Missions: Self-Scheduling

planning and scheduling↗

NASA NTRS2017

Integrated Demand Management: Minimizing Unanticipated Excessive Departure Delay while Ensuring Fairness from a Traffic Management Initiative

This paper introduces NASA's Integrated Demand Management (IDM) concept and presents the results from an early proof-of-concept evaluation and an exploratory experiment. An initial development of the concept was focused on integrating two systems - i.e. the FAA's newly deployed Traffic Flow Management System (TFMS) tool called the Collaborative Trajectory Options Program (CTOP) and the Time-Based Flow Management (TBFM) system with Extended Metering (XM) capabilities to manage projected heavy traffic demand into a capacity-constrained airport. A human-in-the-loop (HITL) simulation experiment was conducted to demonstrate the feasibility of the initial development of the concept by adapting it to an arrival traffic problem at Newark Liberty International Airport (EWR) during clear weather conditions. In this study, the CTOP was utilized to strategically plan the arrival traffic demand by controlling take-off times of both short- and long-haul flights (long-hauls specify aircraft outside TBFM regions and short-hauls specify aircraft within TBFM regions) in a way that results in equitable delays among the groups. Such strategic planning allows less airborne delay to occur within TBFM by feeding manageable long-haul traffic demand while reserving sufficient slots in the overhead streams for the short-haul departures. The manageable traffic demand indicates the TBFM scheduler assigns no more airborne delay than its assigned airspace is capable of absorbing. TBFM then uses its time-based metering capabilities to deliver the desirable throughput by tactically rescheduling the TBFM entered long-haul flights and short-haul departures. Additional research was also performed to explore use of Required Time of Arrival (RTA) capabilities as a potential control mechanism for the airborne flights to improve arrival traffic delivery accuracy of scheduled long-haul traffic demand. The study results show that both short- and long-haul flights received similar ground delays. In addition, there was a noticeable reduction in the total amount of excessive unanticipated last-minute ground delays, i.e. delays that are frequently imposed on the short-haul flight in current day operations due to saturation in the overhead stream, commonly referred to as 'double penalty'. Furthermore, the concept achieved the target throughput while minimizing the expected cost associated with overall delays in arrival traffic. Assessment of the RTA capabilities showed that there was indeed improvement of the scheduled entry times into TBFM regions by using RTA capabilities. However, with respect to reduction in delays incurred within TBFM, there was no observable benefit of improving the precision of long-haul flights entry times.

Collaborative Trajectory Options Program (CTOP)↗

NASA NTRS2018

Increasing Human Spaceflight Capabilities: Demonstration of Crew Autonomy Through Self-Scheduling Onboard International Space Station

For the first time in a spaceflight operational environment, our team enabled an ISS (International Space Station) crewmember to plan, reschedule, and execute their activities in real-time while abiding by flight and scheduling constraints. The Crew Autonomous Scheduling Test (CAST) investigated the novel concept of operations: allowing crew to manage their own timeline.

crew autonomy↗

NASA NTRSDate not supplied

Crew Scheduling Performance

As NASA considers long-duration exploration missions (LDEMs), it is envisioned that crew will behave more autonomously as compared to low-Earth orbit missions. The necessary shift of Ops Planners’ complete management of scheduling and planning to provide flexibility for crew to manage their own schedule in real-time requires significant research and investigation in evaluation of concepts of operations, of software tools to support tasks, and of crew performance to complete scheduling tasks. Our research objective is to characterize the human performance envelope for the task of planning and scheduling (crew self-scheduling), develop countermeasures to mitigate adverse performance effects due to plan complexity, and inform performance standards and guidelines based on research results. In our efforts to understand and characterize scheduling performance of crew members, we have conducted subject matter expert interviews to obtain feedback on scheduling plan complexity drivers and plan goodness. Following the pilot study conducted last year, we designed a study and have begun remote human subject testing to evaluate non-expert human performance, workload, and situational awareness for the task of planning and scheduling. This study investigates the effects of the number and type of constraints on human performance, and the differences in scheduling metrics between scheduling and rescheduling tasks. Subject testing is currently in progress, and we aim to collect data from approximately thirty subjects. We will summarize the methods used and impacts of the number and type of scheduling constraints. We will also present lessons learned as well as relevant results of the study.

crew scheduling↗

NASA NTRS2020

Dynamic Scheduling: Target of Opportunity Observations of Gravitational Wave Events

The simultaneous detection of electromagnetic and gravitational waves from the coalescence of two neutron stars (GW170817 and GRB170817A) has ushered in a new era of ‘multimessenger’ astronomy, with electromagnetic detections spanning from gamma to radio. This great opportunity for new scientific investigations raises the issue of how the available multimessenger tools can best be integrated to constitute a powerful method to study the transient Universe in particular. To facilitate the classification of possible optical counterparts to gravitational wave events, it is important to optimize the scheduling of observations and the filtering of transients, both key elements of the follow-up process. In this work, we describe the existing workflow whereby telescope networks such as GRANDMA and GROWTH are currently scheduled; we then present modifications we have developed for the scheduling process specifically, so as to face the relevant challenges that have appeared during the latest observing run of Advanced LIGO and Advanced Virgo. We address issues with scheduling more than one epoch for multiple fields within a skymap, especially for large and disjointed localizations. This is done in two ways: by optimizing the maximum number of fields that can be scheduled and by splitting up the lobes within the skymap by right ascension to be scheduled individually. In addition, we implement the ability to take previously observed fields into consideration when rescheduling. We show the improvements that these modifications produce in making the search for optical counterparts more efficient, and we point to areas needing further improvement.

Gravitational waves↗

NASA NTRSDate not supplied

Risk-Reduction Autonomy Implementation to Enable NASA Artemis Missions

To achieve NASA’s Artemis program mission objectives a high level of autonomy and ubiquitous autonomy throughout the systems that are being developed will be necessary. The autonomous systems of Artemis will require a distributed autonomy capability, with autonomous systems organized functionally in a hierarchical architecture, where systems at higher levels of the hierarchy have authority over systems at lower levels. The challenge of developing autonomy technologies and concepts of operations for Artemis has been undertaken by the NASA Gateway Working Group. This group has developed requirements, architectures, concepts of operations, and interface control documents, in the context of a hierarchical distributed architecture that includes the following: a Vehicle System Manager (VSM) that autonomously manages the entire Gateway; Module System Managers (MSMs) that autonomously manage each module; and System Managers (SMs) that autonomously manage systems within a module(i.e. ECLSS).A substantially high level of autonomy needs to be achieved by each element of the hierarchy (VSM, MSM, SM)to meet requirements for uncrewed operations; this includes conditions that will have minimal and/or delayed ground intervention (i.e. requirements for sustainability for months of operation without crew or ground support). To advance an implementation of this autonomy design (Gateway Autonomy Design –GAD), a collaboration was established between the Autonomous Systems Laboratory (ASL) at NASA Stennis Space Center and Lockheed Martin. The objectives of this partnership were the following: (1)to implement autonomy at the VSM, MSM, and SM levels;(2) to implement communications among a VSM, 2 MSMs, ORION (a visiting vehicle somewhat equivalent to a module) and 1 SM (a power system), and (3) test autonomous operations with representative use cases. A SM backed by a high-fidelity simulation was created to facilitate demonstrations of use cases that originated in a system of a module. Communication between the VSM and MSMs was implemented according to Concepts of Operations and Interface Control Documents (ICDs). Demonstrations were conducted to address nominal and off-nominal operations and multi-module interactions with VSM. Additionally, user interfaces were created to provide awareness about ongoing processes and results while enhancing the demonstration. Demonstrations included the following use cases: (1)Orion as visiting vehicle registers with VSM;(2) VSM reschedules a module’s timelines when another module’s MSM task fails; and (3) a module’s Power System Manager (PSM) standalone demonstration that included component failure diagnostics, tracing component failure to effected components, which in turn, reports failure information up to the VSM for acknowledgement and display. This paper will describe the detailed technology and autonomous systems developed, and the integrated multi-module demonstrations conducted. Also, challenges that must be met to fully implement the GAD defined by Gateway will be addressed.

Autonomous Systems↗

NASA NTRSDate not supplied

Risk-Reduction Autonomy Implementation to Enable NASA Artemis Missions

To achieve NASA’s Artemis program mission objectives a high level of autonomy that is ubiquitous throughout the systems that are being developed will be necessary. The autonomous systems of Artemis will require a distributed autonomy capability, with autonomous systems organized functionally in a hierarchical architecture, where systems at higher levels of the hierarchy have authority over systems at lower levels. The challenge of developing autonomy technologies and Concepts of Operations (ConOps) for Artemis has been undertaken by the NASA Gateway Working Group. This group has developed requirements, architectures, ConOps, and interface control documents (ICDs), in the context of a hierarchical distributed architecture that includes the following: a Vehicle System Manager (VSM) that autonomously manages the entire Gateway; Module System Managers (MSMs) that autonomously manage each module; and System Managers (SMs) that autonomously manage systems within a module (i.e. ECLSS). A substantially high level of autonomy needs to be achieved by each element of the hierarchy (VSM, MSM, SM) to meet requirements for uncrewed operations; this includes conditions that will have minimal and/or delayed ground intervention (i.e. requirements for sustainability for months of operation without crew or ground support). To advance an implementation of this autonomy design (Gateway Autonomy Design – GAD), a collaboration was established between the Autonomous Systems Laboratory (ASL) at NASA Stennis Space Center and Lockheed Martin. The objectives of this partnership were the following: (1) to implement autonomy at the VSM, MSM, and SM levels; (2) to implement communications among a VSM, 2 MSMs, ORION (a visiting vehicle somewhat equivalent to a module) and 1 SM (a power system), and (3) test autonomous operations with representative use cases. A SM backed by a high-fidelity simulation was created to facilitate demonstrations of use cases that originated in a system of a module. Communication between the VSM and MSMs was implemented according to Concepts of Operations and Interface Control Documents (ICDs). Demonstrations were conducted to address nominal and off-nominal operations and multi-module interactions with the VSM. Additionally, user interfaces were created to provide awareness about ongoing processes and results while enhancing the demonstration. Demonstrations included the following use cases: (1) Orion as visiting vehicle registers with VSM; (2) VSM reschedules a module’s timelines when another module’s MSM task fails; and (3) a module’s Power System Manager (PSM) demonstration that included component failure diagnostics, tracing component failure to effected components, which in turn, reports failure information up to the VSM for acknowledgement and display. This paper will describe the detailed technology and autonomous systems developed, and the integrated multi-module demonstrations conducted. Also, challenges that must be met to fully implement the GAD defined by Gateway will be addressed.

Fernando Figueroa↗

NASA NTRSDate not supplied

APRES Prototype Mission Planner System Demonstration

Activity Planning with Resources for the Exploration of Space (APRES) is a mixed-initiative mission planning system for ground operations. APRES has been designed to support multi-spacecraft missions. The APRES Interface is browser-based and includes a plan editor, a timeline plan display, a temporal constraint editor, display of the state and numeric chronicles, and a violation resolution manager. Automation support is supplied by the APRES Service, which includes components that provide the following capabilities:(1) plan simulation, which determines the state and numeric chronicles (values of the model variables over time) and determines when "processes" are triggered and terminated based on world states in the execution trace, (2) violation detection of constraints and flight rules encoded in the domain model, and of the temporal constraints created by the user, (3) violation resolution suggestions as to how to fix the plan's violations via rescheduling. The user controls when and how to utilize the automation support. Demo video included with paper, runtime 8:54 in color with sound.

John L. Bresina↗

NASA NTRSDate not supplied

Analyzing Launch Operations using the Spaceport Throughput Analysis Resource (STAR)

NASA’s Kennedy Space Center (KSC) and Cape CanaveralSpace Force Station (CCSFS) are the world’s preeminent multi-user spaceport, providing facilities and launch capabilities to the agency, NASA’s commercial partners, and other government agencies. KSC works to ensure an environment in which NASA’s programs and other users can safely and effectively carry out their operations. Approximately 100 launches are expected to take place in 2024. KSC needs to meet the needs of customers who request launches based on their own schedules, but who may not be aware of KSC-wide resource limitations and external constraints on launch operations. KSC-wide resources include telecommunications, range tracking, commodities such as Helium and Nitrogen, and special equipment needed to support launches. External constraints include seasonal launch operations. Since space vehicles are complex and launch operations are uncertain, unexpected events can also cause delays in operations. The Spaceport Throughput AnalysisResource (STAR) assesses whether a specific set of pro-posed launches and associated activities can be performed given the resources KSC currently has available, and external constraints imposed on KSC operations. STAR integrates short-horizon scheduling and simulation of launches using a monte-carlo approach driven by configurable probabilities of different classes of event outcomes, including de-lays and worst-case use of resources. The resulting analyses inform stakeholders of key constraints preventing customers from being able to perform their missions as desired, and give insight into how to improve spaceport throughput. The rest of the paper is organized as follows. In 2 we de-scribe the problem STAR is intended to solve. In Section3 we formally describe the scheduling problem ingredients. In Section 4 we describe how manifests are simulated. InSection 5 we describe the constraints problem that is solved when rescheduling. In Section 6 we describe what information is recorded during manifest simulation in order to evaluate delays. In Section 7 we describe the specific problem solved for KSC. In Section 8 we describe the challenges of knowledge engineering for STAR.

Planning Scheduling Analysis↗