Results for “Concept of Operations” — Page 60

NASA NTRS2023

Subsonic Ultra Green Aircraft Research: Phase IV Final Report – Volume I Mach 0.80 Transonic Truss-Braced Wing High-Speed Design Report

This design report summarizes work performed by the Boeing Subsonic Ultra-Green Aircraft Research (SUGAR) team from December 2016 through June 2018. In Phase IV of the SUGAR program, Boeing is working to improve the productivity of a TTBW configuration by updating the Mach 0.745 vehicle concept to operate efficiently at Mach 0.80. Due to the aerodynamic and structural design challenges associated with adapting the design to a higher speed, design tasks have been broken into several subtasks. The information in this report (Volume I) documents the development of a Mach 0.80 vehicle outer mold line, maturation of TTBW structural concepts, and presents a preliminary high-liftsystem assessment. Results from these studies were integrated into an aircraft-level performance code that estimates the benefits of TTBW technology, both on its own and as a part of the SUGAR integrated technology suite. The aerodynamic performance results presented herein detail the high cruise efficiency of the TTBW concept operating at M=0.80. Results from the RANS code OVERFLOW indicate that the TTBW is aerodynamically well suited for operation at the design M=0.80 transonic cruise Mach number. Aircraft-level performance predictions show that the TTBW offers a 7.2% improvement in fuel burn (per seat) for an economic mission of 900nm, and a 9.0% improvement in fuel burn (per seat) for a 3500nm mission with full passenger payload, relative to an aspect ratio 13 conventional tube and wing configuration of equivalent technology. Integration of the TTBW performance benefits into the SUGAR technology suite shows a 55.9% reduction in fuel burn (for the economic mission) relative to the reference (SUGAR Free) aircraft, which is a consistently sized traditional cantilever wing, single-aisle transport typical of the 2008 fleet. This benefit does not include the performance improvement potential of hybrid-electric systems studied in earlier phases of the SUGAR program Structural concept development work completed in Phase IV has identified several strut attachment concepts that are worth additional development activity – an inboard strut attachment swivel joint concept (which enables the strut to carry axial loads while avoiding strut bending induced by wing twist during flight) significantly simplifies the construction of the main strut. An outboard offset strut attachment concept holds significant potential for further reductions in wing-strut interference drag. Based on work performed to date on Phase IV and the previous phases of the SUGAR program, the TTBW concept continues to remain a viable concept for significantly improving the performance of future aircraft. High-fidelity aerodynamic analysis of the Mach 0.80 TTBW aircraft has shown fuel burn improvement that has exceeded initial expectations despite the increase in cruise Mach number. Structural concept maturation has continued to refine the TTBW structure, and has found no obvious ‘show-stoppers’ to date. Therefore, the potential benefit of improved performance through the use of a very high aspect ratio strut-braced wing continues to warrant additional study

SUGAR↗

NASA NTRS2018

Fe(3): An Evaluation Tool for Low-Altitude Air Traffic Operations

The concepts of unmanned aircraft system traffic management (UTM) and urban air mobility (UAM) are introducing high-density operations in low altitude airspace in closer proximity to populated areas than conventional high-altitude air traffic. The Flexible engine for Fast-time Evaluation of Flight Environments (Fe (sup 3)) provides the capability of statistically analyzing the high-density, high-fidelity, and low-altitude traffic system under numerous scenarios, such that stake holders can study impacts of factors in the low-altitude high-density traffic system and define requirements, policies, and protocols needed to support a safe yet efficient traffic system, and even assess operational risks and optimize flight schedules without conducting infeasible and cost-prohibitive flight tests that involve a large volume of aerial vehicles. This work provides an introduction to this simulation tool including its architecture and various models involved. Its performance and sample application in UAM and UTM are also presented.

Collision Avoidance↗

NASA NTRS2018

Fe3: An Evaluation Tool for Low-Altitude Air Traffic Operations

The concepts of unmanned aircraft system traffic management (UTM) and urban air mobility (UAM) are introducing high-density operations in low altitude airspace in closer proximity to populated areas than conventional high-altitude air traffic. The Flexible engine for Fast-time Evaluation of Flight Environments (Fe (sup 3)) provides the capability of statistically analyzing the high-density, high-fidelity, and low-altitude traffic system under numerous scenarios, such that stake holders can study impacts of factors in the low-altitude high-density traffic system and define requirements, policies, and protocols needed to support a safe yet efficient traffic system, and even assess operational risks and optimize flight schedules without conducting infeasible and cost-prohibitive flight tests that involve a large volume of aerial vehicles. This work provides an introduction to this simulation tool including its architecture and various models involved. Its performance and sample application in UAM and UTM are also presented.

Trajectory Modeling↗

NASA NTRS2008

Integrated Network Architecture for NASA's Orion Missions

NASA is planning a series of short and long duration human and robotic missions to explore the Moon and then Mars. The series of missions will begin with a new crew exploration vehicle (called Orion) that will initially provide crew exchange and cargo supply support to the International Space Station (ISS) and then become a human conveyance for travel to the Moon. The Orion vehicle will be mounted atop the Ares I launch vehicle for a series of pre-launch tests and then launched and inserted into low Earth orbit (LEO) for crew exchange missions to the ISS. The Orion and Ares I comprise the initial vehicles in the Constellation system of systems that later includes Ares V, Earth departure stage, lunar lander, and other lunar surface systems for the lunar exploration missions. These key systems will enable the lunar surface exploration missions to be initiated in 2018. The complexity of the Constellation system of systems and missions will require a communication and navigation infrastructure to provide low and high rate forward and return communication services, tracking services, and ground network services. The infrastructure must provide robust, reliable, safe, sustainable, and autonomous operations at minimum cost while maximizing the exploration capabilities and science return. The infrastructure will be based on a network of networks architecture that will integrate NASA legacy communication, modified elements, and navigation systems. New networks will be added to extend communication, navigation, and timing services for the Moon missions. Internet protocol (IP) and network management systems within the networks will enable interoperability throughout the Constellation system of systems. An integrated network architecture has developed based on the emerging Constellation requirements for Orion missions. The architecture, as presented in this paper, addresses the early Orion missions to the ISS with communication, navigation, and network services over five phases of a mission: pre-launch, launch from T0 to T+6.5 min, launch from T+6.5 min to 12 min, in LEO for rendezvous and docking with ISS, and return to Earth. The network of networks that supports the mission during each of these phases and the concepts of operations during those phases are developed as a high level operational concepts graphic called OV-1, an architecture diagram type described in the Department of Defense Architecture Framework (DoDAF). Additional operational views on organizational relationships (OV-4), operational activities (OV-5), and operational node connectivity (OV-2) are also discussed. The system interfaces view (SV-1) that provides the communication and navigation services to Orion is also included and described. The challenges of architecting integrated network architecture for the NASA Orion missions are highlighted.

Bhasin, Kul B.↗

NASA NTRS1990

Guidance concepts for time-based flight operations

Airport congestion and the associated delays are severe in today's airspace system and are expected to increase. NASA and the FAA is investigating various methods of alleviating this problem through new technology and operational procedures. One concept for improving airspace productivity is time-based control of aircraft. Research to date has focused primarily on the development of time-based flight management systems and Air Traffic Control operational procedures. Flight operations may, however, require special onboard guidance in order to satisfy the Air Traffic Control imposed time constraints. The results are presented of a simulation study aimed at evaluating several time-based guidance concepts in terms of tracking performance, pilot workload, and subjective preference. The guidance concepts tested varied in complexity from simple digital time-error feedback to an advanced time-referenced-energy guidance scheme.

Vicroy, Dan D.↗

NASA NTRS2018

Air Traffic Management Technology Demostration-1 (ATD-1) Avionics Phase 2 Flight Test and Results

NASA’s first Air Traffic Management Technology Demonstration (ATD-1) subproject successfully completed 19 days of flight test validation in January and February 2017 of an Interval Management (IM) avionics prototype and the procedures used to conduct IM arrival and approach operations. IM is one of the three elements integrated into NASA’s ATD-1 concept of operations with the subproject goal of improving aircraft efficiency and airport throughput during high-density arrival operations. The ATD-1 concept of operations combines advanced arrival scheduling, controller decision support tools, and interval management (IM) avionics to enable merging of multiple, time-based, efficient arrival streams. IM contributes to the operation by calculating speeds that enable an aircraft to precisely achieve a specific time or distance behind another aircraft. When precise spacing intervals can be calculated, achieved, and then maintained during high-density operations, aircraft efficiency should be improved by enabling the aircraft to remain closer to the optimum descent trajectory instead of using vectors and step-down altitudes, and airport throughput should be maintained or improved by each aircraft arriving at the runway threshold closer to the assigned spacing interval. This avionics development and flight test was conducted under a NASA contract by Boeing Research and Technology, with Boeing Commercial Aircraft, Honeywell, United Airlines, and Jeppesen as sub-contractors. The Honeywell built IM avionics were the first ever prototype built based on NASA requirements as well as developing and non-flight tested international IM standards, integrated into two test aircraft, and then flown in real-world conditions at the Grant County International Airport (KMWH). The IM prototype flown in the flight test used data from the Ownship and the assigned lead, or Target, aircraft to calculate the airspeed necessary for the Ownship to achieve the desired spacing. The flight test demonstrated that the IM avionics prototype generally met the IM requirement for spacing accuracy. However, the control laws implemented require further development to reduce the high IM speed command rate and the number of speed reversals observed during the test. Pilots assessed the IM procedure as acceptable, and issues requiring further attention were identified. In summary, the IM avionics prototype showed significant promise in contributing to the goals of improving aircraft efficiency and airport throughput. The flight test results also provided important data to the FAA and the working group developing the follow-on version of the international IM standards.

Baxley, Brian T.↗

NASA NTRS2017

Orbit Determination Strategy and Simulation Performance for OSIRIS-REx Proximity Operations

The Origins Spectral Interpretation Resource Identification Security Regolith Explorer (OSIRISREx)is a NASA New Frontiers mission to the near-earth asteroid Bennu that will rendez vousin 2018, create a comprehensive and detailed set of observations over several years, collect a regolith sample, and return the sample to Earth in 2023. The Orbit Determination (OD) team isa sub-section of the Flight Dynamics System responsible for generating precise reconstructions and predictions of the spacecraft trajectory. The OD team processes radiometric data, LIDAR, as well as center-finding and landmark-based Optical Navigation images throughout the proximity operations phase to estimate and predict the spacecraft location within several meters. Stringent knowledge requirements stress the OD teams concept of operations and procedures to produce verified and consistent high quality solutions for observation planning, maneuver planning, and onboard sequencing. This paper will provide insight into the OD concept of operations and summarize the OD performance expected during the approach and early proximity operation phases,based on our pre-encounter knowledge of Bennu. Strategies and methods used to compare and evaluate predicted and reconstructed solutions are detailed. The use of high fidelity operational tests during early 2017 will stress the teams concept of operations and ability to produce precise OD solutions with minimal turn-around delay.

Leonard, Jason M.↗

NASA NTRS2013

SARDA: An Integrated Concept for Airport Surface Operations Management

The Spot and Runway Departure Advisor (SARDA) is an integrated decision support tool for airlines and air traffic control tower enabling surface collaborative decision making (CDM) and departure metering in order to enhance efficiency of surface operations at congested airports. The presentation describes the concept and architecture of the SARDA as a CDM tool, and the results from a human-in-the-loop simulation of the tool conducted in 2012 at the FutureFlight Central, the tower simulation facility. Also, presented is the current activities and future plan for SARDA development. The presentation was given at the meeting with the FAA senior advisor of the Surface Operations Office.

surface collaborative decision making↗

NASA NTRS1989

Space station operations management

Space Station Freedom operations management concepts must be responsive to the unique challenges presented by the permanently manned international laboratory. Space Station Freedom will be assembled over a three year period where the operational environment will change as significant capability plateaus are reached. First Element Launch, Man-Tended Capability, and Permanent Manned Capability, represent milestones in operational capability that is increasing toward mature operations capability. Operations management concepts are being developed to accomodate the varying operational capabilities during assembly, as well as the mature operational environment. This paper describes operations management concepts designed to accomodate the uniqueness of Space Station Freedoom, utilizing tools and processes that seek to control operations costs.

Cannon, Kathleen V.↗

NASA NTRS2012

A Systems Approach to Developing an Affordable Space Ground Transportation Architecture using a Commonality Approach

This paper presents a structured approach for achieving a compatible Ground System (GS) and Flight System (FS) architecture that is affordable, productive and sustainable. This paper is an extension of the paper titled "Approach to an Affordable and Productive Space Transportation System" by McCleskey et al. This paper integrates systems engineering concepts and operationally efficient propulsion system concepts into a structured framework for achieving GS and FS compatibility in the mid-term and long-term time frames. It also presents a functional and quantitative relationship for assessing system compatibility called the Architecture Complexity Index (ACI). This paper: (1) focuses on systems engineering fundamentals as it applies to improving GS and FS compatibility; (2) establishes mid-term and long-term spaceport goals; (3) presents an overview of transitioning a spaceport to an airport model; (4) establishes a framework for defining a ground system architecture; (5) presents the ACI concept; (6) demonstrates the approach by presenting a comparison of different GS architectures; and (7) presents a discussion on the benefits of using this approach with a focus on commonality.

Garcia, Jerry L.↗

NASA NTRS2020

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.↗

NASA NTRSDate not supplied

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↗

NASA NTRSDate not supplied

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↗

NASA NTRSDate not supplied

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↗

NASA NTRSDate not supplied

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↗

NASA NTRS2002

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↗

NASA NTRSDate not supplied

Risk-Reduction Autonomy Implementation to Enable NASA Artemis Missions

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

Autonomous Systems↗

NASA NTRS2015

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↗