Search NASA⌕ Search

SEARCH · Search NASA

Results for “scheduling planning resources model based systems”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

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

At least 37 records · Page 2

Project Management Using Modern Guidance, Navigation and Control Theory

Implementing guidance, navigation, and control (GN&C) theory principles and applying them to the human element of project management and control is not a new concept. As both the literature on the subject and the real-world applications are neither readily available nor comprehensive with regard to how such principles might be applied, this paper has been written to educate the project manager on the "laws of physics" of his or her project (not to teach a GN&C engineer how to become a project manager) and to provide an intuitive, mathematical explanation as to the control and behavior of projects. This paper will also address how the fundamental principles of modern GN&C were applied to the National Aeronautics and Space Administration's (NASA) Constellation Program (CxP) space suit project, ensuring the project was managed within cost, schedule, and budget. A project that is akin to a physical system can be modeled and managed using the same over arching principles of GN&C that would be used if that project were a complex vehicle, a complex system(s), or complex software with time-varying processes (at times nonlinear) containing multiple data inputs of varying accuracy and a range of operating points. The classic GN&C theory approach could thus be applied to small, well-defined projects; yet when working with larger, multiyear projects necessitating multiple organizational structures, numerous external influences, and a multitude of diverse resources, modern GN&C principles are required to model and manage the project. The fundamental principles of a GN&C system incorporate these basic concepts: State, Behavior, Feedback Control, Navigation, Guidance and Planning Logic systems. The State of a system defines the aspects of the system that can change over time; e.g., position, velocity, acceleration, coordinate-based attitude, and temperature, etc. The Behavior of the system focuses more on what changes are possible within the system; this is denoted in the state of the system. The behavior of a system, as captured in the system modeling, when properly done will aid in accurately predicting future system performance. The Feedback Control system understands the state and behavior of the system and uses feedback to adjust control inputs into the system. The feedback, which is the right arm of the Control system, allows change to be affected in the overall system; it therefore is important to not only correctly identify the system feedback inputs, but also the system response to the feedback inputs. The Navigation system takes multiple data inputs and based on a priori knowledge of the inputs, develops a statistically based weighting of the inputs and measurements to determine the system's state. Guidance and Planning Logic of the system, complete with an understanding of where the system is (provided by the Navigation system), will in turn determine where the system needs to be and how to get it there. With any system/project, it is critical that the objective of the system/project be clearly defined -- not only to plan but to measure performance and to aid in guiding the system or the project. The system principles discussed above, which can be and have been applied to the current CxP space suit development project, can also be mapped to real-world constituents, thus allowing project managers to apply systems theories that are well defined in engineering and mathematics to a discipline (i.e., Project Management) that historically has been based in personal experience and intuition. This mapping of GN&C theory to Project Management will, in turn, permit a direct, methodical approach to Project Management, planning and control providing a tool to help predict (and guide) performance and an understanding of the project constraints, how the project can be controlled, and the impacts to external influences and inputs. This approach, to a project manager, flows down to the three bottom-line variables of cost, schedule, and scope ando the needed control of these three variables to successfully perform and complete a project.

Hill, Terry R.↗

A Hybrid Procedural/Deductive Executive for Autonomous Spacecraft

The New Millennium Remote Agent (NMRA) will be the first AI system to control an actual spacecraft. The spacecraft domain places a strong premium on autonomy and requires dynamic recoveries and robust concurrent execution, all in the presence of tight real-time deadlines, changing goals, scarce resource constraints, and a wide variety of possible failures. To achieve this level of execution robustness, we have integrated a procedural executive based on generic procedures with a deductive model-based executive. A procedural executive provides sophisticated control constructs such as loops, parallel activity, locks, and synchronization which are used for robust schedule execution, hierarchical task decomposition, and routine configuration management. A deductive executive provides algorithms for sophisticated state inference and optimal failure recover), planning. The integrated executive enables designers to code knowledge via a combination of procedures and declarative models, yielding a rich modeling capability suitable to the challenges of real spacecraft control. The interface between the two executives ensures both that recovery sequences are smoothly merged into high-level schedule execution and that a high degree of reactivity is retained to effectively handle additional failures during recovery.

Pell, Barney↗

Completable scheduling: An integrated approach to planning and scheduling

The planning problem has traditionally been treated separately from the scheduling problem. However, as more realistic domains are tackled, it becomes evident that the problem of deciding on an ordered set of tasks to achieve a set of goals cannot be treated independently of the problem of actually allocating resources to the tasks. Doing so would result in losing the robustness and flexibility needed to deal with imperfectly modeled domains. Completable scheduling is an approach which integrates the two problems by allowing an a priori planning module to defer particular planning decisions, and consequently the associated scheduling decisions, until execution time. This allows a completable scheduling system to maximize plan flexibility by allowing runtime information to be taken into consideration when making planning and scheduling decision. Furthermore, through the criteria of achievability placed on deferred decision, a completable scheduling system is able to retain much of the goal-directedness and guarantees of achievement afforded by a priori planning. The completable scheduling approach is further enhanced by the use of contingent explanation-based learning, which enables a completable scheduling system to learn general completable plans from example and improve its performance through experience. Initial experimental results show that completable scheduling outperforms classical scheduling as well as pure reactive scheduling in a simple scheduling domain.

Gervasio, Melinda T.↗

Preliminary Medical Risk Estimates and Clinical Capability Needs for Artemis IV

BACKGROUND Human exploration spaceflight missions to the Moon and Mars present unprecedented challenges for in- mission medical care. Compared with the ISS, the greater distance from Earth will mean increased mission durations, communication delays, limited to no resupply opportunities, and significant limitations on the evacuation of ill or injured crew. Spacecraft mass, volume, and power will be curtailed while higher demands will be placed on the crew’s knowledge, skills, and abilities. In this higher risk environment, it is important to: a) quantitatively estimate human system risk attributable to medical conditions, a process known as Probabilistic Risk Analysis, and b) use these estimates to inform medical system design. IMPACT (Informing Mission Planning via Analysis of Complex Tradespaces) is a PRA and medical trade space analysis tool developed by NASA to advance exploration mission medical system design. IMPACT v1.0 improves upon and will soon replace NASA’s existing tool, the Integrated Medical Model, with: a novel evidence base baselined to exploration environments; an expanded list of 119 medical conditions; a significant increase in the number of medical resources that can be utilized and in the flexibility of their use; and the modelling of time lost performing mission-specific tasks due to medical conditions. METHODOLOGY: This abstract will present IMPACT estimates of medical system risk and clinical capability needs for the Artemis IV mission. Artemis IV is currently scheduled for 2026 and will visit the Gateway space station in lunar orbit prior to the second lunar landing of the Artemis program. The baseline Artemis IV mission that was modeled was 28 days in duration with phases including Orion outbound, 4 days on the Gateway space station in lunar orbit, 2 crew on the surface of the Moon for approximately one week, an additional 5 days on Gateway, and then return to Earth. This baseline was compared to two alternative 34-day design reference missions (DRMs) that shifted the lunar sortie earlier or later in the mission profile. Assumptions included 2 female and 2 male crew and a notional medical system mass of 25 kg. Medical system risk estimates include loss of crew life (LOCL), consideration of medical evacuation (known as return to definitive care – RTDC), and an estimate of crew time lost due to medical conditions (Task Time Lost – TTL). The presentation will also describe the medical conditions that are the greatest drivers of risk as well as the clinical capabilities and resources that have the largest effect on risk. RESULTS: All three DRMs had very low probability of LOCL from medical conditions, primarily due to short duration. RTDC was also similar across the DRMs. In contrast, TTL was higher in the early lunar sortie DRM due to earlier occurrence of EVA-related medical conditions. Taken as a whole, there was no clinically significant difference in medical risk across the three missions. Results for clinical capabilities and an example medical equipment list will be discussed but were similar across DRMs.

D Hilmers↗

Preliminary Medical Risk Estimates and Clinical Capability Needs for Late Artemis Missions

BACKGROUND Human exploration spaceflight missions to the Moon and Mars present unprecedented challenges for in- mission medical care. Compared with the ISS, the greater distance from Earth will mean increased mission durations, communication delays, limited to no resupply opportunities, and significant limitations on the evacuation of ill or injured crew. Spacecraft mass, volume, and power will be curtailed while higher demands will be placed on the crew’s knowledge, skills, and abilities. In this higher risk environment, it is important to: a) quantitatively estimate human system risk attributable to medical conditions, a process known as Probabilistic Risk Analysis, and b) use these estimates to inform medical system design. IMPACT (Informing Mission Planning via Analysis of Complex Tradespaces) is a PRA and medical trade space analysis tool developed by NASA to advance exploration mission medical system design. IMPACT v1.0 improves upon and will soon replace NASA’s existing tool, the Integrated Medical Model, with: a novel evidence base baselined to exploration environments; an expanded list of 119 medical conditions; a significant increase in the number of medical resources that can be utilized and in the flexibility of their use; and the modelling of time lost performing mission-specific tasks due to medical conditions. METHODOLOGY: This abstract will present IMPACT estimates of medical system risk and clinical capability needs for the Artemis IV mission. Artemis IV is currently scheduled for 2026 and will visit the Gateway space station in lunar orbit prior to the second lunar landing of the Artemis program. The baseline Artemis IV mission that was modeled was 28 days in duration with phases including Orion outbound, 4 days on the Gateway space station in lunar orbit, 2 crew on the surface of the Moon for approximately one week, an additional 5 days on Gateway, and then return to Earth. This baseline was compared to two alternative 34-day design reference missions (DRMs) that shifted the lunar sortie earlier or later in the mission profile. Assumptions included 2 female and 2 male crew and a notional medical system mass of 25 kg. Medical system risk estimates include loss of crew life (LOCL), consideration of medical evacuation (known as return to definitive care – RTDC), and an estimate of crew time lost due to medical conditions (Task Time Lost – TTL). The presentation will also describe the medical conditions that are the greatest drivers of risk as well as the clinical capabilities and resources that have the largest effect on risk. RESULTS: All three DRMs had very low probability of LOCL from medical conditions, primarily due to short duration. RTDC was also similar across the DRMs. In contrast, TTL was higher in the early lunar sortie DRM due to earlier occurrence of EVA-related medical conditions. Taken as a whole, there was no clinically significant difference in medical risk across the three missions. Results for clinical capabilities and an example medical equipment list will be discussed but were similar across DRMs.

D. Hilmers↗

COCPIT: Collaborative Activity Planning Software for Mars Perseverance Rover

Since landing on the Martian surface, the Perseverance rover has relied on a distributed team to generate commands for exploring its new environment each sol(Martian day). The team uses a complex suite of software tools to accomplish this challenging task in time for the next window of opportunity to send commands to the rover. A key piece of this software ecosystem is COCPIT (Component-based Campaign Planning, Implementation, and Tactical). COCPIT is part of the next generation of planning and scheduling software tools developed by NASA's Jet Propulsion Laboratory in partnership with NASA's Ames Research Center. COCPIT is a web-based application that allows users to collaboratively view and update the Perseverance rover's activity plans, continuously verify that the plan satisfies constraints, assign targets for directing scientific instruments, document science intent, and model power and data resources. Mars Surface Operations requires diverse expertise from team members within the Engineering, Science, Robotic, and Instrument Operations groups, distributed across North America and Europe. In order to improve efficiency and reduce risk, all teams are able to review and edit their activities simultaneously and see the effects on the plan in its entirety. As part of the Ground Data System (GDS) tool suite, COCPIT is responsible for the activity plan. It provides specialized views that allow operators to understand where there may be room for additional observations, see whether any planning constraints are being violated, and confirm that energy usage and data generation are within the defined limits. It contains details such as which filters a camera will use for a given observation, what the resolution of the images should be, where to store the data onboard, and how long the observation is expected to take. It predicts when specific data will be downlinked from the rover to a passing orbiter, so that the team knows when to expect that data on Earth for evaluation in future planning. Ultimately the information from the COCPIT plan is translated to sequences that will be bundled and radiated to Perseverance for execution. The COCPIT tool is used throughout all planning phases.

activity planning↗

COCPIT: Collaborative Activity Planning Software for Mars Perseverance Rover

Since landing on the Martian surface, the Perseverance rover has relied on a distributed team to generate commands for exploring its new environment each sol(Martian day). The team uses a complex suite of software tools to accomplish this challenging task in time for the next window of opportunity to send commands to the rover. A key piece of this software ecosystem is COCPIT (Component-based Campaign Planning, Implementation, and Tactical). COCPIT is part of the next generation of planning and scheduling software tools developed by NASA's Jet Propulsion Laboratory in partnership with NASA's Ames Research Center. COCPIT is a web-based application that allows users to collaboratively view and update the Perseverance rover's activity plans, continuously verify that the plan satisfies constraints, assign targets for directing scientific instruments, document science intent, and model power and data resources. Mars Surface Operations requires diverse expertise from team members within the Engineering, Science, Robotic, and Instrument Operations groups, distributed across North America and Europe. In order to improve efficiency and reduce risk, all teams are able to review and edit their activities simultaneously and see the effects on the plan in its entirety. As part of the Ground Data System (GDS) tool suite, COCPIT is responsible for the activity plan. It provides specialized views that allow operators to understand where there may be room for additional observations, see whether any planning constraints are being violated, and confirm that energy usage and data generation are within the defined limits. It contains details such as which filters a camera will use for a given observation, what the resolution of the images should be, where to store the data onboard, and how long the observation is expected to take. It predicts when specific data will be downlinked from the rover to a passing orbiter, so that the team knows when to expect that data on Earth for evaluation in future planning. Ultimately the information from the COCPIT plan is translated to sequences that will be bundled and radiated to Perseverance for execution. The COCPIT tool is used throughout all planning phases.

activity planning↗

COCPIT: Collaborative Activity Planning Software for Mars Perseverance Rover

Since landing on the Martian surface, the Perseverance rover has relied on a distributed team to generate commands for exploring its new environment each sol (Martian day). The team uses a complex suite of software tools to accomplish this challenging task in time for the next window of opportunity to send commands to the rover. A key piece of this software ecosystem is COCPIT (Component-based Campaign Planning, Implementation, and Tactical). COCPIT is part of the next generation of planning and scheduling software tools developed by NASA's Jet Propulsion Laboratory in partnership with NASA's Ames Research Center. COCPIT is a web-based application that allows users to collaboratively view and update the Perseverance rover's activity plans, continuously verify that the plan satisfies constraints, assign targets for directing scientific instruments, document science intent, and model power and data resources. Mars Surface Operations requires diverse expertise from team members within the Engineering, Science, Robotic, and Instrument Operations groups, distributed across North America and Europe. In order to improve efficiency and reduce risk, all teams are able to review and edit their activities simultaneously and see the effects on the plan in its entirety. As part of the Ground Data System (GDS) tool suite, COCPIT is responsible for the activity plan. It provides specialized views that allow operators to understand where there may be room for additional observations, see whether any planning constraints are being violated, and confirm that energy usage and data generation are within the defined limits. It contains details such as which filters a camera will use for a given observation, what the resolution of the images should be, where to store the data onboard, and how long the observation is expected to take. It predicts when specific data will be downlinked from the rover to a passing orbiter, so that the team knows when to expect that data on Earth for evaluation in future planning. Ultimately the information from the COCPIT plan is translated to sequences that will be bundled and radiated to Perseverance for execution. The COCPIT tool is used throughout all planning phases.

Kanefsky, Bob↗

Demonstrations of System-Level Autonomy for Spacecraft

System-level autonomy refers to autonomously meeting the crosscutting needs of a system through awareness and coordinated control spanning the system's breadth of capabilities. In contrast to function-level autonomy, which focuses on capabilities required to achieve a specific function such as surface navigation or image recognition, system-level autonomy addresses the needs to coordinate and manage activities and resources, and estimate the state, across subsystems. This paper describes demonstrations that were conducted on a spacecraft workstation testbed. The autonomy was provided by system-level planning and execution integrated with system-level estimators of orbit knowledge and spacecraft hardware health. These components are embedded in a system-level framework defining how goals are formed and executed, which elements exist, and how control authority is distributed among components. The planning and execution system at the heart of the framework has the capability to schedule, execute and monitor completion of tasks, as well as plan around unexpected events including new science opportunities and anomalies. The planning and scheduling system is the Multi-mission EXECutive (MEXEC), supported by the system-level health state estimator Model-Based Off-Nominal State Identification and Detection (MONSID), and Autonomous Navigation (AutoNav) algorithms, which determine the orbital system state based on optical observation of other targets. These components are applicable to many kinds of missions on different platforms. These demonstrations were elaborations of earlier experiments conducted on the ASTERIA (Arcsecond Space Telescope Enabling Research In Astrophysics) CubeSat, described in a companion submission [1]. The spacecraft’s extended mission served as an in-flight test platform, during which some individual autonomous capabilities were flown successfully. The autonomy experiments described here were performed on the ASTERIA workstation testbed.

Prather, Maurice↗

Impact, a Tool Suite for Crew Health and Performance System Trade Analyses and Decision Support - Status of Development

Mission planners, systems engineers, and clinicians that support crew health and performance face very difficult choices on upcoming exploration missions. Given that there will be a heavily constrained mass and volume allocation for a medical system on these missions, what medical capability should be manifested to minimize both medical risk and mission risk? Given that not all promising research and technology proposals can be funded, how can proposals be prioritized so that those funded research investments produce the maximum benefit in reducing overall medical risk? The Informing Mission Planning via Analysis of Complex Tradespaces (IMPACT) project seeks to answer these kinds of questions and others to support upcoming exploration missions. IMPACT enables risk-informed and evidence-based trade space analysis for future space vehicles, missions, and systems. This presentation will discuss the long-term HRP and ExMC vision for the larger ecosystem of tools, which include an updated medical database (consisting of an Evidence Library for medical conditions and a medical item database (MedID) for medical resources), dynamic Probabilistic Risk Assessment (PRA) capabilities, System Modeling Language (SysML) models, and contextual data visualizations of output data. IMPACT is the result of a multi-center collaborative effort. The trade space analyses performed by IMPACT can directly inform mission, vehicle, and habitat development by quantifying medical risk, given a design reference mission, crew attributes and a set of medical capabilities. This presentation will update the audience on the development status of the tool suite, its constituent parts and the plans for when it will deploy as an operational product, currently scheduled for the end of FY22. Recent development successes on the IMPACT project include the ability to cluster medical resources into medical capabilities and mutually-dependent bundles, the ability to perform trade analyses on different medical sets, different DRMs, and different crew complements, and the ability to specify mission segments as periods of time assigned to one or more members of the crew during which unique mission events occur (e.g., extravehicular activities, surface operations, gravity well adaptations, etc.). IMPACT is gearing up for its verification and validation phase to compile the data package necessary for a successful Transition to Operations (TtO), per the guidance in NPR 8900.1B .

IMPACT↗

Project Management Using Modern Guidance, Navigation and Control Theory

The idea of control theory and its application to project management is not new, however literature on the topic and real-world applications is not as readily available and comprehensive in how all the principals of Guidance, Navigation and Control (GN&C) apply. This paper will address how the fundamental principals of modern GN&C Theory have been applied to NASA's Constellation Space Suit project and the results in the ability to manage the project within cost, schedule and budget. A s with physical systems, projects can be modeled and managed with the same guiding principles of GN&C as if it were a complex vehicle, system or software with time-varying processes, at times non-linear responses, multiple data inputs of varying accuracy and a range of operating points. With such systems the classic approach could be applied to small and well-defined projects; however with larger, multi-year projects involving multiple organizational structures, external influences and a multitude of diverse resources, then modern control theory is required to model and control the project. The fundamental principals of G N&C stated that a system is comprised of these basic core concepts: State, Behavior, Control system, Navigation system, Guidance and Planning Logic, Feedback systems. The state of a system is a definition of the aspects of the dynamics of the system that can change, such as position, velocity, acceleration, coordinate-based attitude, temperature, etc. The behavior of the system is more of what changes are possible rather than what can change, which is captured in the state of the system. The behavior of a system is captured in the system modeling and if properly done, will aid in accurate system performance prediction in the future. The Control system understands the state and behavior of the system and feedback systems to adjust the control inputs into the system. The Navigation system takes the multiple data inputs and based upon a priori knowledge of the input, will develop a statistical-based weighting of the input to determine where the system currently is located. Guidance and Planning logic of the system with the understanding of where it is (provided by the navigation system) will in turn determine where it needs to be and how to get there. Lastly, the system Feedback system is the right arm of the control system to allow it to affect change in the overall system and therefore it is critical to not only correctly identify the system feedback inputs but also the system response to the feedback inputs. And with any systems project it is critical that the objective of the system be clearly defined for not only planning but to be used to measure performance and to aid in the guidance of the system or project.

Hill, Terry↗

IMPACT, a Tool Suite for Crew Health and Performance System Trade Analyses and Decision Support - Status of Development

Mission planners, systems engineers, and clinicians that support crew health and performance face very difficult choices on upcoming exploration missions. Given that there will be a heavily constrained mass and volume allocation for a medical system on these missions, what medical capability should be manifested to minimize both medical risk and mission risk? Given that not all promising research and technology proposals can be funded, how can proposals be prioritized so that those funded research investments produce the maximum benefit in reducing overall medical risk? The Informing Mission Planning via Analysis of Complex Tradespaces (IMPACT) project seeks to answer these kinds of questions and others to support upcoming exploration missions. IMPACT enables risk-informed and evidence-based trade space analysis for future space vehicles, missions, and systems. This presentation will discuss the long-term HRP and ExMC vision for the larger ecosystem of tools, which include an updated medical database, consisting of an Evidence Library for medical conditions and a medical item database (MedID) for medical resources, dynamic Probabilistic Risk Assessment (PRA) capabilities, System Modeling Language (SysML) models, and contextual data visualizations of output data. IMPACT is the result of a multi-center collaborative effort. The trade space analyses performed by IMPACT can directly inform mission, vehicle, and habitat development by quantifying medical risk, given a design reference mission, crew attributes and a set of medical capabilities. This presentation will update the audience on the development status of the tool suite as it nears its System Acceptance Review (SAR). It will review IMPACT’s constituent parts, briefly discuss typical outputs and outline the plans for transitioning to operations, currently scheduled for later in FY23. Recent development successes on the IMPACT project include the integration of the Medical Extensible Dynamic Probabilistic Risk Assessment Tool (MEDPRAT) v2.0 to accommodate segmented missions with multiple carriers and medical systems, full onboarding of the IMPACT Medical Database (IMPACT-MD), clustering medical resources and skills into medical capabilities and mutually-dependent bundles, and the ability to perform trade analyses on different medical sets, different design reference missions (DRM), with different crew complements and extra-vehicular activity (EVA) schedule.

IMPACT↗

Impact, A Tool Suite for Crew Health and Performance System Trade Analyses and Decision to Support - Transition to Operations

Mission planners, systems engineers, and clinicians that support crew health and performance face very difficult choices on upcoming exploration missions. Given that there will be a heavily constrained mass and volume allocation for a medical system on these missions, what medical capability should be manifested to minimize both medical risk and mission risk? Given that not all promising research and technology proposals can be funded, how can proposals be prioritized so that those funded research investments produce the maximum benefit in reducing overall medical risk? The Informing Mission Planning via Analysis of Complex Tradespaces (IMPACT) project seeks to answer these kinds of questions and others to support upcoming exploration missions. IMPACT enables risk-informed and evidence-based trade space analysis for future space vehicles, missions, and systems. This presentation will discuss the long-term HRP and ExMC vision for the larger ecosystem of tools, which include an updated medical database, consisting of an Evidence Library for medical conditions and a medical item database (MedID) for medical resources, dynamic Probabilistic Risk Assessment (PRA) capabilities, System Modeling Language (SysML) models, and contextual data visualizations of output data. IMPACT is the result of a multi-center collaborative effort. The trade space analyses performed by IMPACT can directly inform mission, vehicle, and habitat development by quantifying medical risk, given a design reference mission, crew attributes and a set of medical capabilities. This presentation will update the audience on the development status of the IMPACT tool suite as it comes out of its System Acceptance Review (SAR) and nears Transition to Operations (TTO). It will review IMPACT’s constituent parts, briefly discuss typical outputs, and outline the plans for transitioning to operations, currently scheduled for later in FY24. Recent development successes on the IMPACT project include the integration of the Medical Extensible Dynamic Probabilistic Risk Assessment Tool (MEDPRAT) v2.0 to accommodate segmented missions with multiple carriers and medical systems, full onboarding of the IMPACT Medical Database (IMPACT-MD), clustering medical resources and skills into medical capabilities and mutually-dependent bundles, verification of IMPACT-MD, and the ability to perform trade analyses on different medical sets, different design reference missions (DRM), with different crew complements and extra-vehicular activity (EVA) schedules.

IMPACT↗

IMPACT, A Tool Suite for Crew Health and Performance System Trade Analyses and Decision Support- Transition to Operations

Mission planners, systems engineers, and clinicians that support crew health and performance face very difficult choices on upcoming exploration missions. Given that there will be a heavily constrained mass and volume allocation for a medical system on these missions, what medical capability should be manifested to minimize both medical risk and mission risk? Given that not all promising research and technology proposals can be funded, how can proposals be prioritized so that those funded research investments produce the maximum benefit in reducing overall medical risk? The Informing Mission Planning via Analysis of Complex Tradespaces (IMPACT) project seeks to answer these kinds of questions and others to support upcoming exploration missions. IMPACT enables risk-informed and evidence-based trade space analysis for future space vehicles, missions, and systems. This presentation will discuss the long-term HRP and ExMC vision for the larger ecosystem of tools, which include an updated medical database, consisting of an Evidence Library for medical conditions and a medical item database (MedID) for medical resources, dynamic Probabilistic Risk Assessment (PRA) capabilities, System Modeling Language (SysML) models, and contextual data visualizations of output data. IMPACT is the result of a multi-center collaborative effort. The trade space analyses performed by IMPACT can directly inform mission, vehicle, and habitat development by quantifying medical risk, given a design reference mission, crew attributes and a set of medical capabilities. This presentation will update the audience on the development status of the IMPACT tool suite as it comes out of its System Acceptance Review (SAR) and nears Transition to Operations (TTO). It will review IMPACT’s constituent parts, briefly discuss typical outputs, and outline the plans for transitioning to operations, currently scheduled for later in FY24. Recent development successes on the IMPACT project include the integration of the Medical Extensible Dynamic Probabilistic Risk Assessment Tool (MEDPRAT) v2.0 to accommodate segmented missions with multiple carriers and medical systems, full onboarding of the IMPACT Medical Database (IMPACT-MD), clustering medical resources and skills into medical capabilities and mutually-dependent bundles, verification of IMPACT-MD, and the ability to perform trade analyses on different medical sets, different design reference missions (DRM), with different crew complements and extra-vehicular activity (EVA) schedules.

IMPACT↗

Automated and Adaptive Mission Planning for Orbital Express

The Orbital Express space mission was a Defense Advanced Research Projects Agency (DARPA) lead demonstration of on-orbit satellite servicing scenarios, autonomous rendezvous, fluid transfers of hydrazine propellant, and robotic arm transfers of Orbital Replacement Unit (ORU) components. Boeing's Autonomous Space Transport Robotic Operations (ASTRO) vehicle provided the servicing to the Ball Aerospace's Next Generation Serviceable Satellite (NextSat) client. For communication opportunities, operations used the high-bandwidth ground-based Air Force Satellite Control Network (AFSCN) along with the relatively low-bandwidth GEO-Synchronous space-borne Tracking and Data Relay Satellite System (TDRSS) network. Mission operations were conducted out of the RDT&E Support Complex (RSC) at the Kirtland Air Force Base in New Mexico. All mission objectives were met successfully: The first of several autonomous rendezvous was demonstrated on May 5, 2007; autonomous free-flyer capture was demonstrated on June 22, 2007; the fluid and ORU transfers throughout the mission were successful. Planning operations for the mission were conducted by a team of personnel including Flight Directors, who were responsible for verifying the steps and contacts within the procedures, the Rendezvous Planners who would compute the locations and visibilities of the spacecraft, the Scenario Resource Planners (SRPs), who were concerned with assignment of communications windows, monitoring of resources, and sending commands to the ASTRO spacecraft, and the Mission planners who would interface with the real-time operations environment, process planning products and coordinate activities with the SRP. The SRP position was staffed by JPL personnel who used the Automated Scheduling and Planning ENvironment (ASPEN) to model and enforce mission and satellite constraints. The lifecycle of a plan began three weeks outside its execution on-board. During the planning timeframe, many aspects could change the plan, causing the need for re-planning. These variable factors, ranging from shifting contact times to ground-station closures and required maintenance times, are discussed along with the flexibility of the ASPEN tool to accommodate changes to procedures and the daily or long-range plan, which contributed to the success of the mission. This paper will present an introduction to ASPEN, a more in-depth discussion on its use on the Orbital Express mission, and other relative work. A description of ground operations after the SRP deliveries were made is included, and we briefly discuss lessons learned from the planning perspective and future work.

scheduling↗

Process-Based Cost Estimation for Ramjet/Scramjet Engines

Process-based cost estimation plays a key role in effecting cultural change that integrates distributed science, technology and engineering teams to rapidly create innovative and affordable products. Working together, NASA Glenn Research Center and Boeing Canoga Park have developed a methodology of process-based cost estimation bridging the methodologies of high-level parametric models and detailed bottoms-up estimation. The NASA GRC/Boeing CP process-based cost model provides a probabilistic structure of layered cost drivers. High-level inputs characterize mission requirements, system performance, and relevant economic factors. Design alternatives are extracted from a standard, product-specific work breakdown structure to pre-load lower-level cost driver inputs and generate the cost-risk analysis. As product design progresses and matures the lower level more detailed cost drivers can be re-accessed and the projected variation of input values narrowed, thereby generating a progressively more accurate estimate of cost-risk. Incorporated into the process-based cost model are techniques for decision analysis, specifically, the analytic hierarchy process (AHP) and functional utility analysis. Design alternatives may then be evaluated not just on cost-risk, but also user defined performance and schedule criteria. This implementation of full-trade study support contributes significantly to the realization of the integrated development environment. The process-based cost estimation model generates development and manufacturing cost estimates. The development team plans to expand the manufacturing process base from approximately 80 manufacturing processes to over 250 processes. Operation and support cost modeling is also envisioned. Process-based estimation considers the materials, resources, and processes in establishing cost-risk and rather depending on weight as an input, actually estimates weight along with cost and schedule.

Singh, Brijendra↗

VIPER – Volatiles Investigating Polar Exploration Rover: Mission Overview

VIPER is a low cost, lunar volatiles detection and measurement mission that will be delivered to the lunar south pole by one of NASA’s Commercial Lunar Payload Services partners and will characterize the nature of the volatiles in the area and extrapolate this data to create global lunar water resource maps. It will be the first mining expedition on another world while simultaneously addressing fundamental planetary science questions. Prospecting for lunar water at the poles is the next step in understanding the resource potential and addressing key theories about water emplacement and retention. It now appears that potentially economically significant amounts of water ice exists at the poles of the Moon, however, the distribution of this water is still not understood at a level sufficient to fully evaluate economic models. The water ice (and other potential volatiles), the “ore body”, needs to be understood at the scales of 10s to 100s of meters to evaluate localization, extraction and processing techniques. To accomplish this, VIPER will survey permanently-shadowed regions, semi-permanent shadowed regions, and even semi and full sunlit areas in order to have a comprehensive survey of polar region volatiles, to best inform future mission architectures. In order to characterize the volatiles, a payload suite consisting of a neutron spectrometer, mass spectrometer, near infrared spectrometer and a 1-meter drill will be hosted on the VIPER mobile lunar rover platform. Since VIPER is a relatively low cost, schedule-constrained, risk-tolerant mission, there are architectural limitations that require unique mission planning constraints to enable exploration of the lunar south pole region. These regions offer unique challenges such as uncertain terrain conditions, rock and crater hazards, lunar dust, multipath communications effects, extreme thermal environments and multiple overlapping planning constraints. Mission design/traverse planning, system design capabilities and mission operations are all highly linked through initial development phases. We will describe the current mission overview and the unique approaches taken by the VIPER project based on our programmatic framework and unique mission environment.

VIPER↗

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

The development of the Space Launch System (SLS) launch vehicle requires cross discipline teams with extensive knowledge of launch vehicle subsystems, information theory, and autonomous algorithms dealing with all operations from pre-launch through on orbit operations. The characteristics of these systems must be matched with the autonomous algorithm monitoring and mitigation capabilities for accurate control and response to abnormal conditions throughout all vehicle mission flight phases, including precipitating safing actions and crew aborts. This presents a large complex systems engineering challenge being addressed in part by focusing on the specific subsystems handling of off-nominal mission and fault tolerance. Using traditional model based system and software engineering design principles from the Unified Modeling Language (UML), the Mission and Fault Management (M&FM) algorithms are crafted and vetted in specialized Integrated Development Teams composed of multiple development disciplines. NASA also has formed an M&FM team for addressing fault management early in the development lifecycle. This team has developed a dedicated Vehicle Management End-to-End Testbed (VMET) that integrates specific M&FM algorithms, specialized nominal and off-nominal test cases, and vendor-supplied physics-based launch vehicle subsystem models. The flexibility of VMET enables thorough testing of the M&FM algorithms by providing configurable suites of both nominal and off-nominal test cases to validate the algorithms utilizing actual subsystem models. The intent is to validate the algorithms and substantiate them with performance baselines for each of the vehicle subsystems in an independent platform exterior to flight software test processes. In any software development process there is inherent risk in the interpretation and implementation of concepts into software through requirements and test processes. Risk reduction is addressed by working with other organizations such as S&MA, Structures and Environments, GNC, Orion, the Crew Office, Flight Operations, and Ground Operations by assessing performance of the M&FM algorithms in terms of their ability to reduce Loss of Mission and Loss of Crew probabilities. In addition, through state machine and diagnostic modeling, analysis efforts investigate a broader suite of failure effects and detection and responses that can be tested in VMET and confirm that responses do not create additional risks or cause undesired states through interactive dynamic effects with other algorithms and systems. VMET further contributes to risk reduction by prototyping and exercising the M&FM algorithms early in their implementation and without any inherent hindrances such as meeting FSW processor scheduling constraints due to their target platform - ARINC 653 partitioned OS, resource limitations, and other factors related to integration with other subsystems not directly involved with M&FM. The plan for VMET encompasses testing the original M&FM algorithms coded in the same C++ language and state machine architectural concepts as that used by Flight Software. This enables the development of performance standards and test cases to characterize the M&FM algorithms and sets a benchmark from which to measure the effectiveness of M&FM algorithms performance in the FSW development and test processes. This paper is outlined in a systematic fashion analogous to a lifecycle process flow for engineering development of algorithms into software and testing. Section I describes the NASA SLS M&FM context, presenting the current infrastructure, leading principles, methods, and participants. Section II defines the testing philosophy of the M&FM algorithms as related to VMET followed by section III, which presents the modeling methods of the algorithms to be tested and validated in VMET. Its details are then further presented in section IV followed by Section V presenting integration, test status, and state analysis. Finally, section VI addresses the summary and forward directions followed by the appendices presenting relevant information on terminology and documentation.

Trevino, Luis↗