Search NASA⌕ Search

SEARCH · Search NASA

Results for “Operational Concepts”

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 1,099 records · Page 61

GN&C Sequencing for Orion Rendezvous, Proximity Operations, and Docking

As part of the Artemis program to return humans to the lunar surface, the National Aeronautics and Space Administration is planning to use the Orion Multi- Purpose Crew Vehicle to transport crew to a small orbital platform called Gate- way in cislunar space. To facilitate this activity, Orion is required to perform Rendezvous, Proximity Operations, and Docking (RPOD) with both the Gate- way and the launch vehicle upper stage. The Orion spacecraft uses sequencing in the form of Phases, Segments, Activities, and Modes (PSAM) to configure Guidance, Navigation, & Control (GN&C) software during each portion of the mission. Significant updates to Orion PSAM definitions are required for RPOD. This paper describes the process of defining these new sequencing elements, implementing them in prototype flight software, and testing them in an integrated simulation environment. First, requirements are specified to determine the nominal and off-nominal sequencing behavior necessary to complete the mission. These requirements also specify which software functions should be fully autonomous and which functions require manual interactions from crew or ground operators. Next, the RPOD concept of operations is defined with detailed events listed in a mission timeline. Third, a state machine diagram is developed to show all PSAM states, including all possible transitions between them. After this, the PSAM states and transitions are entered into a sequencing software emulator and parameter values and modes are defined for GN&C software elements. Finally, the PSAM architecture is tested within an integrated simulation environment by connecting it with prototypes of relevant GN&C flight software elements and with detailed vehicle models. After the sequencing design has been finalized and tested, it is implemented in flight software.

Schulte, Peter Z.↗

Gateway Autonomy for Enabling Deep Space Exploration

The Gateway spacecraft is an important stepping-stone to exploration of the solar system, integrating commercial and international partners into a tightly coupled system, enabling cislunar activities, and implementing key technologies for missions to Mars. Autonomy is a capability area necessary to handle long communication outages where intervention from Earth is impossible, to prepare to operate with long communication delays that will be common in interplanetary travel, and to make spaceflight more affordable and accessible by reducing sustaining operations costs. The Gateway Concept of Operations states that one of Gateway’s goals is to “focus on infrastructure and systems that will allow autonomous operations aboard the Gateway with robotics, automated systems, advanced communications, and distributed computing.” Gateway’s Vehicle Systems Manager (VSM) and associated Autonomous Spacecraft Management Architecture (ASMA) are key products towards delivering autonomous capability. The primary functions of the control architecture are Mission Management and Timeline Execution, Resource Management, Fault Management, and Vehicle Control and Operation (VCO). In each of these areas, there is an initial level of capability to be delivered at launch, with plans to continue development and grow to greater capability. The initial deployment of VSM will focus on maintaining vehicle safety by focusing on full fault management capabilities and deploying only enough resource and timeline planning functionality to support that. The final deployment of VSM will add significant planning and control optimization functionality to support nominal operations for up to 21 days without ground support, even accommodating fault and failure conditions. While the VSM is the vehicle-level representation of autonomous reasoning, distributed automation is essential to provide the right scope and abstraction of information to process. Module and system support of automation and simplicity of interfaces are two important design paradigms that Gateway is focusing on to garner a systems approach to autonomy. Distribution of reasoning can increase complexity, so Gateway is also taking a strict hierarchical approach to information flow and decision making. VSM is not the only capability necessary to achieve an autonomous spacecraft. Robotics support for maintenance of the spacecraft will be essential to provide continued vehicle functionality even when crew is not present. Technical and programmatic challenges exist when implementing autonomous robotics operations. These challenges include sufficient network flexibility to support data transfer to the rest of the vehicle to coordinate module-to-module robotic walk-offs and finding the proper interfaces to allow sufficient dexterity. Communication system upgrades planned for Gateway include Delay Tolerant Networking to best utilize the complex network of relays that will be part of mature cislunar operations. Distributed computing and management will provide failure tolerance, robustness, and growth of capabilities while still allowing significant reuse of heritage software on heritage systems as well as reuse of common applications across a spacecraft to minimize new development, but this requires adherence to key standards and interfaces. The Gateway program has demonstrated significant progress towards these capabilities and has identified challenges other spacecraft developers should be aware of from the start.

Molly Anderson↗

Validation of Fitness for Duty Standards Using Pre- and Post-Flight Capsule Egress and Suited Functional Performance Tasks in Simulated Reduced Gravity

The transition between gravity environments will involve one of the most complex, high-risk phases of exploration missions. The reduced functional capacity caused by physiological deconditioning adaptations in microgravity coupled with the stressors of re-entry into partial gravity environments will increase risks to crew, even with rigorous adherence to inflight countermeasures. Specifically, two high-risk scenarios may be required to be performed soon after gravity transitions: 1) nominal and/or emergency unassisted capsule egress task after return to Earth, and 2) planetary extravehicular activity (EVA) soon after landing on Mars or the Moon. Quantification of crewmember’s functional performance after long-duration spaceflight is necessary to inform concepts of operations for future exploration missions. The overarching aim of this study is to quantify post-landing functional performance with deconditioning after long-duration ISS missions. This study is broken down into two phases. Phase 1 includes a pilot study to assess the overall feasibility and demonstrate the capability to perform mission-like tasks shortly after landing. Phase 2, the Egress Fitness study, which is part of the Complement of Integrated Protocols for Human Exploration Research (CIPHER), uses a task-based approach to characterize functional performance in long-duration ISS crewmembers before flight and shortly after return to Earth. The pilot and full Egress Fitness study includes pre-flight and post-flight testing of simulated emergency egress out of a functional capsule mockup and a Mars gravity EVA simulation at the Active Response Gravity Offload System (ARGOS) facility. The EVA simulation tasks include suit donning, hatch egress, ladder descent, task board cable operations, baggage transfer over sand/rocky regolith, alignment with a rear entry port, and suit egress. The post-flight simulated capsule egress test occurs 1–4 h after landing and the planetary EVA simulation occurs 18–36 h after landing. The full CIPHER Egress Fitness study has additional pre-flight sessions, longer EVA tasks that include traverse and geology sampling, and post-flight sessions on R+1, 4, and 8 to characterize the timeframe of recovery. The Pilot Egress Fitness study has completed baseline and post-flight testing on four crewmembers. All subjects were able to complete the post-flight simulated planetary EVA; three subjects were able to complete the postflight capsule egress simulation. CIPHER study data collection is ongoing. This study will quantify post-landing functional performance in operationally relevant simulations to help inform future planetary concepts of operations shortly after landing.

egress↗

Gateway Autonomy for Enabling Deep Space Exploration

The Gateway spacecraft is an important stepping-stone to exploration of the solar system, integrating commercial and international partners into a tightly coupled system, enabling cislunar activities, and implementing key technologies for missions to Mars. Autonomy is a capability area necessary to handle long communication outages where intervention from Earth is impossible, to prepare to operate with long communication delays that will be common in interplanetary travel, and to make spaceflight more affordable and accessible by reducing sustaining operations costs. The Gateway Concept of Operations states that one of Gateway’s goals is to “focus on infrastructure and systems that will allow autonomous operations aboard the Gateway with robotics, automated systems, advanced communications, and distributed computing.” Gateway’s Vehicle Systems Manager (VSM) and associated Autonomous Spacecraft Management Architecture (ASMA) are key products towards delivering autonomous capability. The primary functions of the control architecture are Mission Management and Timeline Execution, Resource Management, Fault Management, and Vehicle Control and Operation (VCO). In each of these areas, there is an initial level of capability to be delivered at launch, with plans to continue development and grow to greater capability. The initial deployment of VSM will focus on maintaining vehicle safety by focusing on full fault management capabilities and deploying only enough resource and timeline planning functionality to support that. The final deployment of VSM will add significant planning and control optimization functionality to support nominal operations for up to 21 days without ground support, even accommodating fault and failure conditions. While the VSM is the vehicle-level representation of autonomous reasoning, distributed automation is essential to provide the right scope and abstraction of information to process. Module and system support of automation and simplicity of interfaces are two important design paradigms that Gateway is focusing on to garner a systems approach to autonomy. Distribution of reasoning can increase complexity, so Gateway is also taking a strict hierarchical approach to information flow and decision making. VSM is not the only capability necessary to achieve an autonomous spacecraft. Robotics support for maintenance of the spacecraft will be essential to provide continued vehicle functionality even when crew is not present. Technical and programmatic challenges exist when implementing autonomous robotics operations. These challenges include sufficient network flexibility to support data transfer to the rest of the vehicle to coordinate module-to-module robotic walk-offs and finding the proper interfaces to allow sufficient dexterity. Communication system upgrades planned for Gateway include Delay Tolerant Networking to best utilize the complex network of relays that will be part of mature cislunar operations. Distributed computing and management will provide failure tolerance, robustness, and growth of capabilities while still allowing significant reuse of heritage software on heritage systems as well as reuse of common applications across a spacecraft to minimize new development, but this requires adherence to key standards and interfaces. The Gateway program has demonstrated significant progress towards these capabilities and has identified challenges other spacecraft developers should be aware of from the start.

Molly Anderson↗

Gap Analysis of UAS Manuals and Hazards

Emerging aviation includes the use of small Unmanned Aerial Systems (UAS) in novel operations. The manufacture and operation of these small UAS are not as regulated as today’s commercial operation, and their widespread use introduces new risks and hazards to the general public. Today, there are case-by-case approvals for sUAS operations, particularly for emergency response operations in which the potential benefits to use of sUAS is perceived to outweigh potential risks. We analyze operational approvals, procedures, and concepts of operation to identify and categorize the risks and hazards that applicants and approvers are already considering, and also identify barriers and mitigations that the operators have already put in place. This analysis may help lead to routine checklists that standardize safety analysis and lead to more routine operations.

grounded theory↗

Regaining Lost Separation in a Piloted Simulation of Autonomous Aircraft Operations

NASA is currently investigating a new concept of operations for the National Airspace System, designed to improve capacity while maintaining or improving current levels of safety. This concept, known as Distributed Air/Ground Traffic Management (DAG-TM), allows appropriately equipped autonomous aircraft to maneuver freely for flight optimization while resolving conflicts with other traffic and staying out of special use airspace and hazardous weather. While Airborne Separation Assurance System (ASAS) tools would normally allow pilots to resolve conflicts before they become hazardous, evaluation of system performance in sudden, near-term conflicts is needed in order to determine concept feasibility. If an acceptable safety level can be demonstrated in these situations, then operations may be conducted with lower separation minimums. An experiment was conducted in NASA Langley s Air Traffic Operations Lab to address issues associated with resolving near-term conflicts and the potential use of lower separation minimums. Sixteen commercial airline pilots flew a total of 32 traffic scenarios that required them to use prototype ASAS tools to resolve close range pop-up conflicts. Required separation standards were set at either 3 or 5 NM lateral spacing, with 1000 ft vertical separation being used for both cases. Reducing the lateral separation from 5 to 3 NM did not appear to increase operational risk, as indicated by the proximity to the intruder aircraft. Pilots performed better when they followed tactical guidance cues provided by ASAS than when they didn't follow the guidance. As air-air separation concepts are evolved, further studies will consider integration issues between ASAS and existing Airborne Collision Avoidance Systems (ACAS).These types of non-normal events will require the ASAS to provide effective alerts and resolutions prior to the time that an Airborne Collision Avoidance System (ACAS) would give a Resolution Advisory (RA). When an RA is issued, a pilot must take immediate action in order to avoid a potential near miss. The Traffic Alert and Collision Avoidance System (TCAS) II currently functions as an ACAS aboard commercial aircraft. Depending on the own aircraft s altitude, TCAS only issues RA s 15-35 seconds prior to the Closest Point of Approach (CPA). Prior to an RA, DAG-TM pilots operating autonomous aircraft must rely solely on ASAS for resolution guidance. An additional area of DAG-TM concept feasibility relates to a potential reduction in separation standards. Lower separation standards are likely needed in order to improve NAS efficiency and capacity. Current separation minimums are based in large part on the capabilities of older radar systems. Safety assessments are needed to determine the feasibility of reduced separation minimums. They will give strong consideration to surveillance system performance, including accuracy, integrity, and availability. Candidate surveillance systems include Automatic Dependent Surveillance-Broadcast (ADS-B) and multi-lateration systems. Considering studies done for Reduced Vertical Separation Minimums (RVSM) operations, it is likely that flight technical errors will also be considered. In addition to a thorough evaluation of surveillance system performance, a potential decision to lower the separation standards should also take operational considerations into account. An ASAS Safety Assessment study identified improper maneuvering in response to a conflict (due to ambiguous or improper resolution commands or a pilot s failure to comply with the resolution) as a potential safety risk. If near-term conflicts with lower separation minimums were determined to be more challenging for pilots, the severity of these risks could be even greater.

Barhydt, Richard↗

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↗

Transportation-Driven Mars Surface Operations Supporting an Evolvable Mars Campaign

This paper describes the results of a study evaluating options for supporting a series of human missions to a single Mars surface destination. In this scenario the infrastructure emplaced during previous visits to this site is leveraged in following missions. The goal of this single site approach to Mars surface infrastructure is to enable "Steady State" operations by at least 4 crew for up to 500 sols at this site. These characteristics, along with the transportation system used to deliver crew and equipment to and from Mars, are collectively known as the Evolvable Mars Campaign (EMC). Information in this paper is presented in the sequence in which it was accomplished. First, a logical buildup sequence of surface infrastructure was developed to achieve the desired "Steady State" operations on the Mars surface. This was based on a concept of operations that met objectives of the EMC. Second, infrastructure capabilities were identified to carry out this concept of operations. Third, systems (in the form of conceptual elements) were identified to provide these capabilities. This included top-level mass, power and volume estimates for these elements. Fourth, the results were then used in analyses to evaluate three options (18t, 27t, and 40t landed mass) of Mars Lander delivery capability to the surface. Finally, Mars arrival mass estimates were generated based upon the entry, descent, and landing requirements for inclusion in separate assessments of in-space transportation capabilities for the EMC.

Toups, Larry↗

Safely Enabling Low-Altitude UAS Operations: Unmanned Aircraft System Traffic Management

Concept of operations; Roles, responsibilities, implications on who pays; Information architecture paved way for FAA's (Federal Aviation Administration's) RFI (Request for Information); Demonstrated initial feasibility of architecture, application-protocol-interface-based approach, and overall construct; Data exchange and protocols; Demonstration of UTM (Unmanned Aerial Systems Traffic Management) TCL1 (Tuscaloosa, AL Airport Terminal 1) with all 6 test sites; Initial demonstration of UTM TCL2 for BVLOS (Beyond Visual Line-of-Sight) requirements.

Low-altitude UTM↗

Use of a Prototype Airborne Separation Assurance System for Resolving Near-Term Conflicts During Autonomous Aircraft Operations

NASA is currently investigating a new concept of operations for the National Airspace System, designed to improve capacity while maintaining or improving current levels of safety. This concept, known as Distributed Air/Ground Traffic Management (DAGTM), allows appropriately equipped autonomous aircraft to maneuver freely for flight optimization while resolving conflicts with other traffic and staying out of special use airspace and hazardous weather. In order to perform these tasks, pilots use prototype conflict detection, prevention, and resolution tools, collectively known as an Airborne Separation Assurance System (ASAS). While ASAS would normally allow pilots to resolve conflicts before they become hazardous, evaluation of system performance in sudden, near-term conflicts is needed in order to determine concept feasibility. An experiment was conducted in NASA Langley's Air Traffic Operations Lab to evaluate the prototype ASAS for enabling pilots to resolve near-term conflicts and examine possible operational effects associated with the use of lower separation minimums. Sixteen commercial airline pilots flew a total of 32 traffic scenarios that required them to use prototype ASAS tools to resolve close range pop-up conflicts. Required separation standards were set at either 3 or 5 NM lateral spacing, with 1000 ft vertical separation being used for both cases. Reducing the lateral separation from 5 to 3 NM did not appear to increase operational risk, as indicated by the proximity to the intruder aircraft. Pilots performed better when they followed tactical guidance cues provided by ASAS than when they didn't follow the guidance. In an effort to improve compliance rate, ASAS design changes are currently under consideration. Further studies will of evaluate these design changes and consider integration issues between ASAS and existing Airborne Collision Avoidance Systems (ACAS).

Barhydt, Richard↗

An Integrated Energy Systems Prototype Human-System Interface for a Steam Extraction Loop System to Support Joint Electricity-Hydrogen Flexible Operations

Due to increasing economic competition from renewables and combined-cycle natural gas plants, nuclear power plants are looking toward flexible operations to enhance their cost competitiveness. The Integrated Energy Systems project under the Light Water Reactor Sustainability program of the U.S. Department of Energy focuses on joint electricity-hydrogen flexible operations. Joint electricity-hydrogen flexible operations entail the nuclear power plant diverting thermal energy via main steam to a hydrogen production plant located nearby. The steam serves to enhance the efficiency of the hydrogen production. Furthermore, high temperature electrolysis requires a large amount of electricity, which the plant can also provide. The plant provides steam and electricity to the hydrogen plant throughout the day, but during peak demand hours the nuclear power plant returns to solely providing electricity to meet the high demand. Through this flexible concept of operations, the plant can optimize the thermal energy it produces without having to maneuver the power of the plant. This report documents the human factors process to design and develop a prototype human-system interface for the steam extraction loop that serves as the conduit between the nuclear power plant and the adjacent hydrogen plant. The design process followed the human factors guidelines set by NUREG-0711, Human Factors Engineering Program Review Model (O’Hara, Higgins, & Fleger, 2012), and expanded upon by the Guideline for Operational Nuclear Usability and Knowledge Elicitation (GONUKE; Boring, Ulrich, Joe, & Lew, 2015; Boring, Lew, & Ulrich, 2016). The design process entailed operator interviews to determine the concept of operations for the steam extraction loop, a review and adaptation of digital interface design concepts developed by the team in prior projects, an iterative design process, and reviews conducted by both operators and human factors experts. Several versions of the prototype human-system interface were developed. Operators were interviewed to determine what design features they found useful and would like to see in the interface. The design underwent a review by human factors experts against NUREG-0700, Human Interface Design Review Guidelines (U.S. Nuclear Regulatory Commission, 2019), to ensure compliance with the latest human factors standards for digital interfaces in nuclear applications. The design was then prototyped as a functional windows-based application integrated with the Generic Pressurized Water Reactor simulator modified to include the steam extraction loop. The simulation is supported by the Human Systems Simulation Laboratory at Idaho National Laboratory, which supports operator-in-the-loop testing. This is an ongoing project and the next phase of the project entails performing an operator-in-the-loop usability study to evaluate the interface and examine the proposed concept of operations to extraction steam from the nuclear power plant for delivery to the coupled hydrogen production plant.

99 GENERAL AND MISCELLANEOUS↗

Airborne Precision Spacing (APS) Dependent Parallel Arrivals (DPA)

The Airborne Precision Spacing (APS) team at the NASA Langley Research Center (LaRC) has been developing a concept of operations to extend the current APS concept to support dependent approaches to parallel or converging runways along with the required pilot and controller procedures and pilot interfaces. A staggered operations capability for the Airborne Spacing for Terminal Arrival Routes (ASTAR) tool was developed and designated as ASTAR10. ASTAR10 has reached a sufficient level of maturity to be validated and tested through a fast-time simulation. The purpose of the experiment was to identify and resolve any remaining issues in the ASTAR10 algorithm, as well as put the concept of operations through a practical test.

Smith, Colin L.↗

Infrared Communications for Small Spacecraft: From a Wireless Bus to Cluster Concepts

Nanosatellites operating singly or in clusters are anticipated for future space science missions. To implement this new communications paradigm, we are approaching cluster communications by first developing an infrared (IR) intra-craft wireless bus capability, following initially the MIL-STD-1553B protocol. Benefits of an IR wireless bus are low mass, size, power, and cost, simplicity of implementation, ease of use, minimum EMI, and efficient and reliable data transfer. Our goals are to maximize the reliable link margin in order to afford greater flexibility in receiver placement, which will ease technology insertion. We have developed a concept demonstration using a high-speed visible-band silicon PIN photodiode and a high-efficiency visible LED operating at a data rate up to 4 Mb/sec. In designing an internal IR wireless bus, we have characterized various candidate materials, emitters, and geometries, assuming a single reflection. Thus, we have measured the bidirectional reflectance distribution function (BRDF) for five different materials characteristic of typical spacecraft structures, which range from nearly Lambertian to highly specular. We have fit our data to empirical BRDF functions and modeled the detected irradiance anywhere in the plane of incidence for a divergent (LED) emitter. We have also determined the angular limits on the link geometry to remain within the required bit error rate by determining the received signal-to-noise ratio (SNR) for minimum values of irradiance received at the detector.

Webb, Suzanne C.↗

Flight Surgeon Survey Results Review: Long-Duration Artemis Medical System ConOps

Background: The Artemis Mission Functional Medical Concept of Operation (ConOp) is an operational document that describes the functional medical capabilities and concept of operations for early Artemis missions of around 30 days duration. It is currently under revision for longer missions (180+ days), aiming to build a foundational diagnostic and treatment capabilities list considering mission parameters, crew selection and training, and mass/volume constraints. An interview of NASA operational flight surgeons was completed to start the revision of the medical ConOp. Methods: In the survey, 20 experienced NASA flight surgeons responded to 57 standardized questions covering 17 categories, 22 questions of which were covered in this analysis including 4 categories: Cardiovascular, Catastrophic Situations, Pulmonary, and Respiratory/O2 Support. These results were categorized into recommendations and observations. The recommendations were used to objectively quantify the responses to look for consensus, differences and uncertainty among responses. The observations remain important but were not included in this review. Analysis: Regarding questions related to changes in medical conditions treated for long-duration missions, percentage of “No Change” responses varied from 20% to 75%. In the “Change” treatment plan responses, a variety of recommendations were made, which were further made into graphics for better illustration. Additionally, recommendations on capability questions in multiple systems were visualized altogether in one product. Discussion: This work demonstrates the importance of collaboration and thorough analysis amongst experienced NASA flight surgeons for helping establish medical systems and contributing to the likelihood of mission success during Artemis long-duration missions. Through this review, we were able to identify some positive attributes as well as areas for improvement, which will facilitate further discussions.

Andrew Bushong↗

Flight Surgeon Survey Results Review: Long-Duration Artemis Medical System ConOps

The Artemis Mission Functional Medical Concept of Operation (ConOp) is an operational document that describes the functional medical capabilities and concept of operations for early Artemis missions of around 30 days duration. It is currently under revision for longer missions (180+ days), aiming to build a foundational diagnostic and treatment capabilities list considering mission parameters, crew selection and training, and mass/volume constraints. An interview of NASA operational flight surgeons was completed to start the revision of the medical ConOp.

Andrew Bushong↗

Mars Sample Return Using Commercial Capabilities: ERV Trajectory and Capture Requirements

Mars Sample Return was presented as the highest priority planetary science mission of the next decade [1]. Lemke et al. [2] present a Mars Sample Return mission concept in which the sample is returned directly from the surface of Mars to an Earth orbit. The sample is recovered in Earth Orbit instead of being transferred between spacecraft in Mars Orbit. This paper provides the details of this sample recovery in Earth orbit and presents as such a sub-element of the overall Mars sample return concept given in [2]. We start from the assumption that a Mars Ascent Vehicle (MAV), initially landed on Mars using a modified SpaceX Dragon capsule, has successfully delivered the sample, already contained within an Earth Return Vehicle (ERV), to a parking orbit around Mars. From the parking orbit, the ERV imparts sufficient Delta-V to inject itself into an earthbound trajectory and to be captured into an Earth orbit eventually. We take into account launch window and Delta-V considerations as well as the additional constraint of increased safety margins imposed by planetary protection regulations. We focus on how to overcome two distinct challenges of the sample return that are driven by the issues of planetary protection: (1) the design of an ERV trajectory meeting all the requirements including the need to avoid contamination of Earth's atmosphere; (2) the concept of operations for retrieving the Martian samples in Earth orbit in a safe way. We present an approach to retrieve the samples through a rendezvous between the ERV and a second SpaceX Dragon capsule. The ERV executes a trajectory that brings it from low Mars orbit (LMO) to a Moon-trailing Earth orbit at high inclination with respect to the Earth-Moon plane. After a first burn at Trans-Earth Injection (TEI), the trajectory uses a second burn at perigee during an Earth flyby maneuver to capture the ERV in Earth orbit. The ERV then uses a non-propulsive Moon flyby to come to a near-circular Moon-trailing orbit. To perform the Earth Orbit Rendezvous (EOR), a second Dragon capsule is then launched from Earth and a similar lunar flyby is performed to rendezvous with the ERV. The requirements for rendezvous, close proximity operations and capture of the sample canister are described. A concept of operations for sample retrieval is presented along with design specifications of the ERV, the required modifications to the Dragon capsule, as well as the hardware, software, sensors, actuators, and capture mechanisms used. In our concept, a container is mounted to the front hatch of Dragon, capable of accommodating the sample canister and sealing it from the rest of the capsule. The sample canister is captured using a robotic arm with a magnetic grappling mechanism. Dragon then performs a propulsive maneuver to return to Earth for a controlled re-entry while the ERV (sans sample container) is left in the Moon trailing orbit. Contingency cases and related mitigation strategies are also discussed, including the advantages and disadvantages of performing the ERV rendezvous with a crew.

Faber, Nicolas F.↗

Tailoring a ConOps for NASA LSP Integrated Operations

An integral part of the Systems Engineering process is the creation of a Concept of Operations (ConOps) for a given system, with the ConOps initially established early in the system design process and evolved as the system definition and design matures. As Integration Engineers in NASA's Launch Services Program (LSP) at Kennedy Space Center (KSC), our job is to manage the interface requirements for all the robotic space missions that come to our Program for a Launch Service. LSP procures and manages a launch service from one of our many commercial Launch Vehicle Contractors (LVCs) and these commercial companies are then responsible for developing the Interface Control Document (ICD), the verification of the requirements in that document, and all the services pertaining to integrating the spacecraft and launching it into orbit. However, one of the systems engineering tools that have not been employed within LSP to date is a Concept of Operations. The goal of this paper is to research the format and content that goes into these various aerospace industry ConOps and tailor the format and content into template form, so the template may be used as an engineering tool for spacecraft integration with future LSP procured launch services. This tailoring effort was performed as the authors final Masters Project in the Spring of 2016 for the Stevens Institute of Technology and modified for publication with INCOSE (Owens, 2016).

Knowledge↗

Feedback following the Industry Engagement of the NNSA Unique Identifier and Global Monitoring 5 year plan

The National Nuclear Security Administration s project for developing a unique identifier and a concept for a global monitoring system for UF6 cylinders made significant progress on developing functional requirements and a concept of operation for such a system. The multi-laboratory team is working to define the functional requirements for both the unique identifier and the global monitoring system and to develop a preliminary concept of operations to discuss with key industry stakeholders. Team members began meeting with industry representatives in January 2013 to discuss the preliminary concept and solicit feedback and suggestions. The team has met with representatives from United States Enrichment Corporation, Cameco, URENCO, Honeywell/ConverDyn, and others. This paper presents an overview of the preliminary concept of operations and shares the feedback obtained from the industry engagement meetings.

IAEA↗