Search NASA⌕ Search

SEARCH · Search NASA

Results for “stakeholder training”

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

NY TBO Research: Integrated Demand Management (IDM): IDM Concept, Tools, and Training Package

A series of human-in-the-loop simulation sessions were conducted in the Airspace Operations Laboratory (AOL) to evaluate a new traffic management concept called Integrated Demand Management (IDM). The simulation explored how to address chronic equity, throughput and delay issues associated with New Yorks high-volume airports by operationally integrating three current and NextGen capabilities the Collaborative Trajectory Options Program (CTOP), Time-Based Flow Management (TBFM) and Required Time of Arrival (RTA) in order to better manage traffic demand within the National Air Traffic System. A package of presentation slides was developed to describe the concept, tools, and training materials used in the simulation sessions. The package will be used to outbrief our stakeholders by both presenting orally and disseminating of the materials via email.

trajectory-based operations↗

Testing the Exploration Conops (Excon) Mockup Suit in Lunar Analog Environments in 2022

Understanding how to effectively train for Extravehicular Activities (EVAs) for Artemis missions is critical. Developing high-fidelity simulation environments is important for Artemis mission preparation. Because the actual Lunar exploration environment cannot be fully replicated on Earth, it is paramount to determine where and how to properly train the Artemis team. Tasked by the new Extravehicular Activity and Human Surface Mobility Program(EHP), a team of stakeholders from engineering, flight operations, human health and performance, astromaterials and science, and the crew office worked together to perform EVAs in 3 simulated lunar environments. The overall focus for this test series was developing the capability to perform Artemis simulated EVAs in high-fidelity, full-scale environments. This test series was broken into 3 distinct tests titled after the EHP integrated test team: Joint EVA Test Team (JETT). The test locations are planned to serve as Artemis training sites and were selected because of their relevance to the expected Artemis Lunar terrain. JETT1was conducted near Kilbourne Holeby El Paso, Texas and focused on hardware development and checkout. JETT2 was conducted in the Icelandic Highlands and began the transition towards EVA concept operations(con-ops), risks and technology.JETT3 was conducted near SP Crater by Flagstaff Arizona and focused on simulating the Artemis III mission with a simulated Houston based Flight Control Team (FCT) and a Science Mission Directorate (SMD) science team. All three JETT tests utilized the Excon mockup space suit. The Excon mockup suit is a light-weight, unpressurized Exploration Extravehicular Mobility Unit (xEMU)simulator. While it cannot replicate the feel of working within a pressurized suit, it does introduce similar volume constraints and some of the mobility programing to simulate the user experience in the xEMU. Overall, the JETT testing was able to create a simulated Lunar EVA and have two subjects perform full scale operations in line with Artemis III mission expectations. Future work is planned to continue to improve the simulation quality of Lunar EVA simulations.

spacesuit↗

Promoting Collaborative Open Science through the Stakeholder Engagement Program

Since 2016, the Satellite Needs Working Group (SNWG), an initiative of the U.S. Group on Earth Observations (USGEO), has surveyed federal agencies biennially to identify their satellite Earth observation needs. Coordinating with the agencies, NASA-led assessment teams work to identify solutions for each expressed need. Solutions to a need can involve existing data products or even the formation of new data products and technologies, such as the Harmonized Landsat Sentinel-2 (HLS) product and the Catalog of Archived Sub-Orbital Earth Science Investigations (CASEI). To enhance community engagement with these new data products and technologies, the SNWG Management Office’s Stakeholder Engagement Program (SEP) was established. The SEP within NASA’s Interagency Implementation and Advanced Concepts Team (IMPACT) at Marshall Space Flight Center has three goals: to increase awareness of the SNWG survey and its outcomes, to ensure training coordination and outreach efforts supporting integration and use of SNWG solutions, and to enhance coordination among solution development teams, NASA’s Distributed Active Archive Centers (DAACs), SNWG stakeholders, and end user communities. These goals align with NASA Earth Science Data System’s (ESDS) Open Science initiative by establishing a collaborative community focused on enhancing scientific research at diverse levels of understanding. This presentation will highlight SEP’s facilitation of these open science goals through its support in SNWG’s past and current survey cycles as well as its plans for future involvement.

Jenny Wood↗

EVA SPACESUIT INCIDENCE TRACKING

INTRODUCTION: Extravehicular Activity (EVA)suit-related injuries to crew during training and inflight operations are not uncommon. Systematic tracking of these issues has waxed and waned throughout NASA’s history. Given two new EVA suits in development and an increase in EVA training, the need for dutiful recording of this data is critical. The Suited User Incident Tracking System (SUITS) was developed in the last decade to track all suited exposures, recording exposure details and any related issues, pains, or injuries that arise. METHODS: SUITS data collected from 2017 to 2022 was analyzed for issue frequency and severity for each body location and plotted to visualize where issues were occurring. Clustering techniques using a k-modes approach were also applied to the data set to generate profiles of populations that experienced issues in the suit, and populations that did not. RESULTS:A key finding from SUITS is that discomfort and pain observed in the new planetary spacesuits are occurring in new body locations than those experienced in the microgravity space suit (Extravehicular Mobility Unit (EMU)).To date, the lower body and torso regions account for most pain reports in planetary spacesuits whereas most reports in EMU were shoulders and hands. DISCUSSION:SUITS will continue to be used to capture exposures for all suit types. As training suit availability improves and training cadence increases in preparation for planetary missions, it is critical to capture and assess all suit incidences. Further, a Suited Anomaly Assessment Team (SAAT) consisting of a broad range of EVA stakeholders was formed to share and act on SUITS data with the goal of developing robust solutions to issues/injuries as they arise. Understanding the types and locations of injuries that occur during suited operations will help inform future work related to EVA fitness training requirements, suit design, and modeling efforts to avoid injury. LEARNING OBJECTIVES: 1. Systematic tracking of suited exposures and issues is critical for understanding the complex interaction between the human and the EVA spacesuit. 2. As EVA suit issues/injuries arise it is important to share that data with a broad group to ensure robust strategies are developed.

N Newby↗

Citizen Science Data Quality: The GLOBE Program

The Global Learning and Observations to Benefit the Environment (GLOBE) Program is an international program that provides a way for students and the public to contribute Earth system observations. Currently 122 countries, more than 40,000 schools, and 200,000 citizen scientists are participating in GLOBE. Since 1995, participants have contributed 195 million observations. Modes of data collection and data entry have evolved with technology over the lifetime of the program, including the launch of the GLOBE Observer mobile app in 2016 to broaden access and public participation in data collection. GLOBE must meet the data needs of a diverse range of stakeholders, from elementary school classrooms to scientists across the globe, including NASA scientists. Operational quality assurance measures include participant training, adherence to standardized data collection protocols, range and logic checks, and an approval process for photos submitted with an observation. In this presentation, we will discuss the current state of operational data QA/QC, as well as additional QA/QC processes recently explored and future directions.

Amos, Helen↗

Marshall Space Flight Center Propulsion Systems Department (PSD) KM Initiative

NASA Marshall Space Flight Center s Propulsion Systems Department (PSD) is four months into a fifteen month Knowledge Management (KM) initiative to support enhanced engineering decision making and analyses, faster resolution of anomalies (near-term) and effective, efficient knowledge infused engineering processes, reduced knowledge attrition, and reduced anomaly occurrences (long-term). The near-term objective of this initiative is developing a KM Pilot project, within the context of a 3-5 year KM strategy, to introduce and evaluate the use of KM within PSD. An internal NASA/MSFC PSD KM team was established early in project formulation to maintain a practitioner, user-centric focus throughout the conceptual development, planning and deployment of KM technologies and capabilities with in the PSD. The PSD internal team is supported by the University of Alabama's Aging Infrastructure Systems Center Of Excellence (AISCE), Intergraph Corporation, and The Knowledge Institute. The principle product of the initial four month effort has been strategic planning of PSD KM implementation by first determining the "as is" state of KM capabilities and developing, planning and documenting the roadmap to achieve the desired "to be" state. Activities undertaken to support the planning phase have included data gathering; cultural surveys, group work-sessions, interviews, documentation review, and independent research. Assessments and analyses have been performed including industry benchmarking, related local and Agency initiatives, specific tools and techniques used and strategies for leveraging existing resources, people and technology to achieve common KM goals. Key findings captured in the PSD KM Strategic Plan include the system vision, purpose, stakeholders, prioritized strategic objectives mapped to the top ten practitioner needs and analysis of current resource usage. Opportunities identified from research, analyses, cultural/KM surveys and practitioner interviews include: executive and senior management sponsorship, KM awareness, promotion and training, cultural change management, process improvement, leveraging existing resources and new innovative technologies to align with other NASA KM initiatives (convergence: the big picture). To enable results based incremental implementation and future growth of the KM initiative, key performance measures have been identified including stakeholder value, system utility, learning and growth (knowledge capture, sharing, reduced anomaly recurrence), cultural change, process improvement and return-on-investment. The next steps for the initial implementation spiral (focused on SSME Turbomachinery) have been identified, largely based on the organization and compilation of summary level engineering process models, data capture matrices, functional models and conceptual-level systems architecture. Key elements include detailed KM requirements definition, KM technology architecture assessment, evaluation and selection, deployable KM Pilot design, development, implementation and evaluation, and justifying full implementation (estimated Return-on-Investment). Features identified for the notional system architecture include the knowledge presentation layer (and its components), knowledge network layer (and its components), knowledge storage layer (and its components), User Interface and capabilities. This paper provides a snapshot of the progress to date, the near term planning for deploying the KM pilot project and a forward look at results based growth of KM capabilities with-in the MSFC PSD.

Caraccioli, Paul↗

Marshall Space Flight Center Propulsion Systems Department (PSD) Knowledge Management (KM) Initiative

NASA Marshall Space Flight Center's Propulsion Systems Department (PSD) is four months into a fifteen month Knowledge Management (KM) initiative to support enhanced engineering decision making and analyses, faster resolution of anomalies (near-term) and effective, efficient knowledge infused engineering processes, reduced knowledge attrition, and reduced anomaly occurrences (long-term). The near-term objective of this initiative is developing a KM Pilot project, within the context of a 3-5 year KM strategy, to introduce and evaluate the use of KM within PSD. An internal NASA/MSFC PSD KM team was established early in project formulation to maintain a practitioner, user-centric focus throughout the conceptual development, planning and deployment of KM technologies and capabilities within the PSD. The PSD internal team is supported by the University of Alabama's Aging Infrastructure Systems Center of Excellence (AISCE), lntergraph Corporation, and The Knowledge Institute. The principle product of the initial four month effort has been strategic planning of PSD KNI implementation by first determining the "as is" state of KM capabilities and developing, planning and documenting the roadmap to achieve the desired "to be" state. Activities undertaken to suppo~th e planning phase have included data gathering; cultural surveys, group work-sessions, interviews, documentation review, and independent research. Assessments and analyses have beon pedormed including industry benchmarking, related local and Agency initiatives, specific tools and techniques used and strategies for leveraging existing resources, people and technology to achieve common KM goals. Key findings captured in the PSD KM Strategic Plan include the system vision, purpose, stakeholders, prioritized strategic objectives mapped to the top ten practitioner needs and analysis of current resource usage. Opportunities identified from research, analyses, cultural1KM surveys and practitioner interviews include: executive and senior management sponsorship, KM awareness, promotion and training, cultural change management, process improvement, leveraging existing resources and new innovative technologies to align with other NASA KM initiatives (convergence: the big picture). To enable results based incremental implementation and future growth of the KM initiative, key performance measures have been identified including stakeholder value, system utility, learning and growth (knowledge capture, sharing, reduced anomaly recurrence), cultural change, process improvement and return-on-investment. The next steps for the initial implementation spiral (focused on SSME Turbomachinery) have been identified, largely based on the organization and compilation of summary level engineering process models, data capture matrices, functional models and conceptual-level svstems architecture. Key elements include detailed KM requirements definition, KM technology architecture assessment, - evaluation and selection, deployable KM Pilot design, development, implementation and evaluation, and justifying full implementation (estimated Return-on-Investment). Features identified for the notional system architecture include the knowledge presentation layer (and its components), knowledge network layer (and its components), knowledge storage layer (and its components), User Interface and capabilities. This paper provides a snapshot of the progress to date, the near term planning for deploying the KM pilot project and a forward look at results based growth of KM capabilities with-in the MSFC PSD.

Caraccioli, Paul↗

How ExMC Communicates a System Model to Non-Modelers

NASA’s Human Research Program (HRP) Exploration Medical Capability (ExMC) Element adopted Systems Engineering (SE) principles and Model Based Systems Engineering (MBSE) tools to capture the system functions, system architecture, requirements, interfaces, and clinical capabilities for a future exploration medical system. There are many different stakeholders who may use the information in the model: systems engineers, clinicians (physicians, nurses, and pharmacists), scientists, and mission planners. Many of these stakeholders have neither access to MBSE modeling tools nor experience with SE modeling techniques. The challenge faced by ExMC SE team was how to present the content in the model to non-modelers in a way they would understand the content with limited training in MBSE and without using the modeling tool. ExMC SE team created a Hypertext Markup Language (HTML) report that shows key model content and is accessible to anyone with a browser. When creating the HTML report, the ExMC SE received stakeholder feedback on what content they wanted and how to display this content. Incorporating this feedback, the report arranges the content in a way that directs readers through the SE process taken to derive the requirements and helps them to understand the fundamental steps in an SE approach. The report includes links to source information (e.g., NASA documentation that describes levels of care) and other SE products (e.g., Concept of Operations). These links were provided to aid in the understanding of how the team created this content through a methodical SE approach. This presentation outlines the process used to develop the model, the data chosen to share with stakeholders, many of the model elements used in the report, the review process stakeholders followed, the comments received from the stakeholders, and the lessons ExMC learned through producing this HTML report.

J. Cohen↗

Looking to the Future: A Call to Action for Advanced GNC Algorithm Verification and Validation

Future space systems will rely on autonomous Guidance, Navigation, and Control (GNC) functions to efficiently manage safe and precise self-directed operations in uncertain complex environments. Fundamentally, the GNC system plays a key role in mission performance and safety because it computes the ideal trajectory (Guidance), determines the actual trajectory (Navigation), and executes the ideal trajectory (Control) of a vehicle’s position and attitude. Our current GNC systems are highly automated and already have a high degree of complexity. As missions become more ambitious, GNC systems for launch vehicles and space platforms (e.g., spacecraft, probes, and landers) will require higher levels of performance and autonomous operation than previously encountered, for example, this includes GNC for optimizing aerodynamic and/or propulsion performance during planetary entry. This GNC Verification and Validation (V&V) paper highlights concerns with what undoubtedly will be a trend towards increased complexity as fully autonomous GNC systems are developed for future space missions. Clearly, complex GNC systems pose challenges in the prelaunch V&V phase, which is a relatively expensive part of a mission’s life cycle. Essentially the V&V phase is focused on checking that the system effectively meets all the design and operational requirements for the mission. The authors of this paper (i.e., the Inter-Agency Working Group of GNC subject matter experts) focused on this fundamental question over the past few years: Will the GNC engineering community of practice be sufficiently prepared to perform the necessary V&V on evolving GNC architectures that are driven by very demanding requirements for autonomy, resiliency, reconfigurability, adaptability, and mission cost-benefit balance? It is the viewpoint of our Inter-Agency team that the GNC V&V approaches and processes needed to address the next generation of complex GNC systems, which likely will employ various forms of modern GNC technology, are not currently established to the level the community will need in the future. While researchers and practitioners have made some progress in developing new GNC V&V methods for modern GNC systems, a good deal of work remains to be done to codify such methods in a comprehensive and systematic manner. Thus, the Inter-Agency team’s partner organizations [the National Aeronautics and Space Administration (NASA), the European Space Agency (ESA), the National Centre for Space Studies (CNES), the German Aerospace Center (DLR), the French Aerospace Lab (ONERA), and ISAE-SUPAERO] have conducted preliminary investigations into advancing GNC V&V techniques, which resulted in the identification of the need for education, new V&V tools, and benchmark problems for the GNC community. The necessary proactive steps to be taken to meet the challenges and fill the gaps in GNC V&V are summarized in this paper. The first steps include identifying advanced analysis tools, developing a GNC V&V roadmap, and expanding education and training programs for GNC practitioners. This paper is a call to action and proposes a comprehensive set of recommended actions for all our stakeholders: space agencies, researchers, and industry.

Samir Bennani↗

From NASA's EOS to ESO: Advancing Applications of the Future Atmosphere Observing (AOS) Mission

The NASA Earth System Observatory (ESO) Atmosphere Observing System (AOS) is being designed to explore the fundamental questions of how interconnections between aerosols, clouds and precipitation impact our weather and climate, addressing real-world challenges to benefit society. A fundamental component of the AOS mission is ensuring that applications for economic and societal benefit are considered to the greatest extent possible in mission design. As a result, the AOS Applications Impact Team (AIT) was formed to address this objective. The overarching goal of the AIT is to help improve capacity for transitioning science to applications to make it possible to more quickly and effectively inform decisions that will directly benefit society. We seek to maximize AOS benefit to impact decisions through early engagement in the mission development phase in order to prepare stakeholders to apply observations as soon as AOS mission data become available. A critical component of preparing future users of AOS mission data is building on the successes of applications of NASA’s existing Earth Observing System (EOS), A-Train, and sub-orbital campaigns with the goal of advancing current mission applications activities and preparing for innovative AOS mission observations. NASA’s GPM mission forms a framework to enhance AOS precipitation applications while AOS health and air quality applications benefit from the heritage of CALIPSO and MODIS. Additionally, AOS will likely benefit from current and future missions such as TROPICS, MAIA, TEMPO, and PACE which launch before AOS. Additionally, current sub-orbital field campaigns, such as NASA IMPACTS and ACTIVATE, provide rich data sources to highlight future AOS capabilities. Engaging with existing missions and sub-orbital field campaigns helps to identify and understand data needs, gaps, and opportunities for current and future stakeholders, determine what data products are of highest value and use, and connect stakeholders with current mission data that can serve as AOS proxy data, among others. In this presentation, we provide an overview of AOS AIT activities, initiatives, and the AOS Applications Seminar Series to highlight how existing EOS, A-Train, and sub-orbital missions can play a critical role in advancing AOS applications prior to launch.

Emily B. Berndt↗

NASA’s Global Precipitation Measurement Mission: Leveraging Stakeholder Engagement & Applications Activities to Inform Decision-making

The application of satellite precipitation estimates from NASA’s Global Precipitation Measurement (GPM) Mission for decision-making has been a focus for the mission since launch. As a result, GPM data have enabled a range of applications that address societal needs, including water resource management, crop forecasting, ecological monitoring, disaster response, public health, aviation, weather forecasting, and climate modeling, among others. GPM applications activities have continued to focus on user engagement through in person trainings and interviews, workshops, webinars, and educational outreach activities. The goals of these efforts are to synthesize community data needs in order to effectively support and enable decision-making across agencies, academia and the global community. While these efforts have helped the GPM mission establish a large stakeholder community that encompasses federal and state partners, academic institutions, nd private and nonprofit companies, there remains difficulties associated with accessing, processing, and applying the data to support or enable applications. In this article, we present GPM applications strategies and approaches used to enhance the applications value of GPM data, and most importantly, demonstrate how these efforts have and can inform different decision-making contexts. This work also provides a discussion on key lessons learned from the user community and how this information can be utilized to help better support and shape applications approaches for future NASA Earth Science missions.

Satellite precipitation↗

Intelligent Response and Interaction System (IRIS) - FY21 Closeout Report

In the second year, the IRIS team developed the components necessary for successful offline deployment of the IRIS services. This includes custom automated speech recognition training on NASA audio data, and in-house development and integration of online and offline conversational services. Lastly, the team worked on integrating the IRIS technology with stakeholders and projects that have a strong need for voice interaction.

Aly Shehata↗

Suited User Incident Tracking System

The Suited User Incident Tracking System (SUITS) tracks all suited exposures during terrestrial analog simulations and trainings with the objective of recording any related issues, pains, or discomforts that arise from the exposure. This information is vital for informing where, how, and why issues are occurring during suited extravehicular activity (EVA) training and operations. The outputs of SUITS will be the foundation for the newly formed Suited Anomaly Assessment Team (SAAT) which consists of a broad range of EVA stakeholders including suit engineers, biomechanists, ergonomists, flight surgeons, athletic trainers, and physiologists. This team has been formed to provide robust, wholistic solutions to suit anomalies and issues identified by SUITS. SUITS data collected from September 2017 to June 2022 was analyzed for issue frequency and severity for each body location and plotted to visualize where issues were occurring. Clustering techniques using a k-modes approach were also applied to the data set to generate profiles of populations that experienced issues in the suit and populations that did not. A key finding identified by the SUITs analysis was that suited issues translate from predominantly upper body areas in microgravity space suits and associated analog simulations to lower body areas in planetary space suits and analog simulations. In addition, specific injury frequency and severity metrics were identified that will help drive requirements for commercially provided space suits. The SAAT will continue to meet on a biannual basis to identify trends in issues and injuries from the SUITS database to evaluate and develop solution strategies where needed for the purposes of suit design, EVA operations optimization, injury characterization and mitigation, and personalized improvements for human-suit interactions.

K. Dolick↗

Presenting Model-Based Systems Engineering Information to Non-Modelers

NASA’s Human Research Program’s (HRP) Exploration Medical Capability (ExMC) Element adopted Systems Engineering (SE) principles and Model Based Systems Engineering (MBSE) tools to capture the system functions, system architecture, requirements, interfaces, and clinical capabilities for a future exploration medical system. There are many different stakeholders who may use the information in the model: systems engineers, clinicians (physicians, nurses, and pharmacists), scientists, and program managers. Many of these individuals do not have access to MBSE modeling tools or have never used these tools. Many of these individuals (clinicians, scientists, even program managers) may have no experience with SE in general let alone interpreting a systems model. The challenge faced by ExMC was how to present the content in the model to non-modelers in a way they could understand with limited to no training in MBSE or the Systems Modeling Language (SysML) without using the modeling tool. Therefore, from the model, ExMC created an HTML report that is accessible to anyone with a browser. When creating the HTML report, the ExMC SE team talked to stakeholders and received their feedback on what content they wanted and how to display this content. Factoring in feedback, the report arranges the content in a way that not only directs readers through the SE process taken to derive the requirements, but also helps them to understand the fundamental steps in an SE approach. The report includes links to source information (i.e., NASA documentation that describes levels of care) and other SE deliverables (e.g., Concept of Operations). These links were provided to aid in the understanding of how the team created this content through a methodical SE approach. This paper outlines the process used to develop the model, the data chosen to share with stakeholders, many of the model elements used in the report, the review process stakeholders followed, the comments received from the stakeholders, and the lessons ExMC learned through producing this HTML report.1Trade names and trademarks are used in this report for identification only. Their usage does not constitute an official endorsement, either expressed or implied, by the National Aeronautics and Space Administration.

Jeffrey R. Cohen↗

Presenting Model-Based Systems Engineering Information to Non-Modelers

NASA’s Human Research Program’s (HRP) Exploration Medical Capability (ExMC) Element adopted Systems Engineering (SE) principles and Model Based Systems Engineering (MBSE) tools to capture the system functions, system architecture, requirements, interfaces, and clinical capabilities for a future exploration medical system. There are many different stakeholders who may use the information in the model: systems engineers, clinicians (physicians, nurses, and pharmacists), scientists, and program managers. Many of these individuals do not have access to MBSE modeling tools or have never used these tools. Many of these individuals (clinicians, scientists, even program managers) may have no experience with SE in general let alone interpreting a systems model. The challenge faced by ExMC was how to present the content in the model to non-modelers in a way they could understand with limited to no training in MBSE or the Systems Modeling Language (SysML) without using the modeling tool. Therefore, from the model, ExMC created an HTML report that is accessible to anyone with a browser. When creating the HTML report, the ExMC SE team talked to stakeholders and received their feedback on what content they wanted and how to display this content. Factoring in feedback, the report arranges the content in a way that not only directs readers through the SE process taken to derive the requirements, but also helps them to understand the fundamental steps in an SE approach. The report includes links to source information (i.e., NASA documentation that describes levels of care) and other SE deliverables (e.g., Concept of Operations). These links were provided to aid in the understanding of how the team created this content through methodical SE approach. This paper outlines the process used to develop the model, the data chosen to share with stakeholders, many of the model elements used in the report, the review process stakeholders followed, the comments received from the stakeholders, and the lessons ExMC learned through producing this HTML report.

Jeffrey R. Cohen↗

Presenting Model-Based Systems Engineering Information to Non-Modelers

NASA’s Human Research Program’s (HRP) Exploration Medical Capability (ExMC) Element adopted Systems Engineering (SE) principles and Model Based Systems Engineering (MBSE) tools to capture the system functions, system architecture, requirements, interfaces, and clinical capabilities for a future exploration medical system. There are many different stakeholders who may use the information in the model: systems engineers, requirement engineers, clinicians (doctors, nurses, and pharmacists), scientists, and program managers. Many of these individuals do not have access to MBSE modeling toolsor have never used these tools. Many of these individuals (clinicians, scientists, even program managers)may have no experience with SE in general let alone interpreting a systems model. The challenge faced by ExMC was how to present the content in the model to non-modelers in a way they could understand with limited to no training in MBSE or the Systems Modeling Language (SysML) without using the modeling tool. Therefore, from the model, ExMC created an HTML report that is accessible to anyone with a browser. When creating the HTML report, the ExMC SE team talked to stakeholders and received their feedback on what content they wanted and how to display this content. Factoring in feedback, the report arranges the content in a way that not only directs readers through the SE process taken to derive the requirements, but also helps them to understand the fundamental steps in an SE approach. The report includes links to source information (i.e., NASA documentation that describes levels of care) and other SE deliverables (e.g., Concept of Operations). These links were provided to aid in the understanding of how the team created this content through a methodical SE approach. This paper outlines the process used to develop the model, the data chosen to share with stakeholders, many of the model elements used in the report, the review process stakeholders followed, the comments received from the stakeholders, and the lessons ExMC learned through producing this HTML report.

Jeff Cohen↗

Crew Performance Support System to Aid in Anomaly Resolution: Concept of Operations

As missions progress into deep space, communication delays and disruptions will disenable the crew’s reliance on Earth experts. There are also limitations in the amount of data that can be downlinked to the ground. It is prudent to assume that critical, complex vehicle or habitat sub-systems will malfunction at a time when a lunar or Mars’ crew cannot rely on the Earth-Support team to detect, diagnose and resolve the problem and it is impractical to expect a small crew to step-in with the same level of expertise as 50+ authorities. The crew will need novel processes and advanced technological support to independently identify and resolve safety- and time-critical anomalies. That a self-reliant crew is unable to respond appropriately to time-critical anomalies is a significant risk to crew safety and mission success. This risk is driven by several factors; novel and unanticipated anomalies would not have been trained pre-flight, the crew could forget their pre-flight training or spaceflight stressors could impair the crew’s problem-solving ability. At last year’s IWS, Beard reported that a single spaceflight stressor (elevated CO2) could undermine the crew’s ability to independently respond to emergencies. Concept of Operations (ConOps) provide a common view of future system functions to all stakeholders. For the current project, a ConOps was developed that describes the operational processes, practices and capabilities needed by a crew of astronauts on deep space missions to autonomously respond to anticipated and unanticipated anomalies. It is crucial to recognize that, as of August 2018 existing technologies are unable to effectively support crew anomaly response to unanticipated events. “Intelligent technology” has not reached a maturity level that permits generalizing a solution to novel situations. For example, to train intelligent technology requires volumes of data that do not exist. The complexities involved in a manned mission to Mars cannot be compared to sending rovers to Mars using scripted software. This ConOps proposes a Crew Performance Support System (CPSS) that will push NASA and its industry partners toward what will be required for a safe and successful manned mission to Mars. Anomaly resolution during a deep space mission will take place within a dynamic, or changing, context. The figure to the left shows five broad contextual variables: the organizational culture, mission context, system characteristics, team characteristics and individual characteristics. The yellow arrow indicates that spaceflight and task-related stressors can affect system, team and individual crewmember characteristics and therefore anomaly response potential. The figure depicts a protective umbrella of Human-System Integration (HSI) principles that should be instituted during CPSS development including a balanced workload, shared situation awareness and building an appropriate level of trust in the automation. The figure also depicts two interrelated and cooperative components, an HSI Data System and other Enabling Capabilities will be required to support crew anomaly response and Earth-Support situation awareness. As we journey from ISS to Gateway to Mars, multiple, simultaneous and integrated research and development efforts (i.e., support systems co-evolution) must be implemented to meet the problem-solving challenges a self-reliant crew will face on a Mars’ mission. The crossovers between the capabilities are just as important as the discrete capabilities themselves. As the capabilities mature, the lines between the support subdomains will blur and an integrated system will emerge. The ConOps summarizes current knowledge about how highly trained people solve anomalies in safety- and time-critical situations, describes a group of capabilities that could help to reduce the extant risk and documents requirements levied on additional systems that provides critical inputs to the CPSS. Scenarios are used to promote a shared understanding of processes, practices and technological goals needed for safe and productive manned missions beyond LEO.

HSIA risk↗

SERVIR: Leveraging the Expertise of a Space Agency and a Development Agency to Increase Impact of Earth Observation in the Developing World

SERVIR is a joint initiative of the National Aeronautics and Space Administration (NASA) and the U.S. Agency for International Development (USAID), in collaboration with leading technical organizations around the world-- called SERVIR hubs--that serve and empower developing countries to use satellite data addressing critical challenges in food security and agriculture; water and water-related disasters; land cover, land use and ecosystems; and weather and climate. Over the past fourteen years, the program has worked with stakeholders in 50 countries across the world, partnered with 390 institutions, and generated and shared over 70 products from 27 satellites and sensors. In that process, around 7,400 specialists have been trained in the application of Earth observation data and technology. In its lifetime, SERVIR has been agile and innovative in shifting from what was essentially an incubator for testing and deploying Earth observation science and technology to making co-development the hallmark of its work, exemplified by both South-South and North-South scientific collaborations. SERVIR’s approach has embodied the concept that to solve really big problems, big, creative solutions are needed. SERVIR represents the world working together to address environmental challenges using spaced-based and geospatial technologies. Aligning with the very meaning of SERVIR, i.e. “to serve,” the program continues to be demand-driven in developing and deploying services (versus one-off products) which address development challenges using geospatial tools and Earth observation science. In 2016, as part of SERVIR’s evolution, USAID and NASA released the ‘SERVIR Service Planning Toolkit,’ a guidance document which provides a framework for how geospatial services can be used to tackle development challenges in a sustained manner. Since then, the Service Planning Toolkit’s systematic approach has begun to catch on in other Earth observation efforts. To improve access and use, SERVIR launched a Service Catalogue in February 2019, a searchable collection of demand-driven geospatial services that use Earth observations to support decision making. SERVIR implementing hub partners –include SERVIR-West Africa at the Agrometeorology, Hydrology and Meteorology (AGRHYMET) Regional Center, in Niamey, Niger; SERVIR-Eastern & Southern Africa at the Regional Centre for Mapping of Resources for Development in Nairobi, Kenya; SERVIR-Hindu Kush Himalaya at the International Centre for Integrated Mountain Development in Kathmandu, Nepal; SERVIR-Mekong at the Asian Disaster Preparedness Center in Bangkok, Thailand; and SERVIR’ -Amazonia, at the International Center for Tropical Agriculture (CIAT) in Cali, Colombia.

Searby, Nancy D.↗