Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “mobile resources”

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 73 records · Page 4

A New Architecture for Visualization: Open Mission Control Technologies

Open Mission Control Technologies (MCT) is a new architecture for visualisation of mission data. Driven by requirements for new mission capabilities, including distributed mission operations, access to data anywhere, customization by users, synthesis of multiple data sources, and flexibility for multi-mission adaptation, Open MCT provides users with an integrated customizable environment. Developed at NASAs Ames Research Center (ARC), in collaboration with NASAs Advanced Multimission Operations System (AMMOS) and NASAs Jet Propulsion Laboratory (JPL), Open MCT is getting its first mission use on the Jason 3 Mission, and is also available in the testbed for the Mars 2020 Rover and for development use for NASAs Resource Prospector Lunar Rover. The open source nature of the project provides for use outside of space missions, including open source contributions from a community of users. The defining features of Open MCT for mission users are data integration, end user composition and multiple views. Data integration provides access to mission data across domains in one place, making data such as activities, timelines, telemetry, imagery, event timers and procedures available in one place, without application switching. End user composition provides users with layouts, which act as a canvas to assemble visualisations. Multiple views provide the capability to view the same data in different ways, with live switching of data views in place. Open MCT is browser based, and works on the desktop as well as tablets and phones, providing access to data anywhere. An early use case for mobile data access took place on the Resource Prospector (RP) Mission Distributed Operations Test, in which rover engineers in the field were able to view telemetry on their phones. We envision this capability providing decision support to on console operators from off duty personnel. The plug-in architecture also allows for adaptation for different mission capabilities. Different data types and capabilities may be added or removed using plugins. An API provides a means to write new capabilities and to create data adaptors. Data plugins exist for mission data sources for NASA missions. Adaptors have been written by international and commercial users. Open MCT is open source. Open source enables collaborative development across organizations and also makes the product available outside of the space community, providing a potential source of usage and ideas to drive product design and development. The combination of open source with an Apache 2 license, and distribution on GitHub, has enabled an active community of users and contributors. The spectrum of users for Open MCT is, to our knowledge, unprecedented for mission software. In addition to our NASA users, we have, through open source, had users and inquires on projects ranging from Internet of Things, to radio hobbyists, to farming projects. We have an active community of contributors, enabling a flow of ideas inside and outside of the space community.

Trimble, Jay↗

iPhone in NASA Ground Operations

A comprehensive review of the literature and historical background of NASA established a need for an easy-to-implement technological improvement to displaying procedures which is cost effective and risk reducing. Previous unsuccessful attempts have led this team to explore the practicality of using a mobile handheld device. The major products, inputs, resources, constraints, planning and effort required for consideration of this type of solution were outlined. After analyzing the physical, environmental, life-cycle, functional, and socio-technical requirements, a Functional Analysis was performed to describe the top-level, second-level, and third-level functions of the system requirements. In addition, the risk/value proposition of conversion to a new technology was considered and gave a blueprint for transitioning along with the tasks necessary to implement the device into the Vehicle Assembly Building's (VAB) current infrastructure. A Work Breakdown Structure (WBS) described the elemental work items of the implementation. Once the viability of this system was confirmed, a device was selected through use of technical design comparison methods including the Pugh Matrix and House of Quality. Comparison and evaluation of the Apple iPhone, Motorola Q, Blackberry, PC Notebook, and PDA revealed that the iPhone is the most suitable device for this task. This paper outlines the device design/ architecture, as well as some of the required infrastructure.

Benedict, Ashley↗

MERRA Analytic Services: Meeting the Big Data Challenges of Climate Science Through Cloud-enabled Climate Analytics-as-a-service

Climate science is a Big Data domain that is experiencing unprecedented growth. In our efforts to address the Big Data challenges of climate science, we are moving toward a notion of Climate Analytics-as-a-Service (CAaaS). We focus on analytics, because it is the knowledge gained from our interactions with Big Data that ultimately produce societal benefits. We focus on CAaaS because we believe it provides a useful way of thinking about the problem: a specialization of the concept of business process-as-a-service, which is an evolving extension of IaaS, PaaS, and SaaS enabled by Cloud Computing. Within this framework, Cloud Computing plays an important role; however, we it see it as only one element in a constellation of capabilities that are essential to delivering climate analytics as a service. These elements are essential because in the aggregate they lead to generativity, a capacity for self-assembly that we feel is the key to solving many of the Big Data challenges in this domain. MERRA Analytic Services (MERRAAS) is an example of cloud-enabled CAaaS built on this principle. MERRAAS enables MapReduce analytics over NASAs Modern-Era Retrospective Analysis for Research and Applications (MERRA) data collection. The MERRA reanalysis integrates observational data with numerical models to produce a global temporally and spatially consistent synthesis of 26 key climate variables. It represents a type of data product that is of growing importance to scientists doing climate change research and a wide range of decision support applications. MERRAAS brings together the following generative elements in a full, end-to-end demonstration of CAaaS capabilities: (1) high-performance, data proximal analytics, (2) scalable data management, (3) software appliance virtualization, (4) adaptive analytics, and (5) a domain-harmonized API. The effectiveness of MERRAAS has been demonstrated in several applications. In our experience, Cloud Computing lowers the barriers and risk to organizational change, fosters innovation and experimentation, facilitates technology transfer, and provides the agility required to meet our customers' increasing and changing needs. Cloud Computing is providing a new tier in the data services stack that helps connect earthbound, enterprise-level data and computational resources to new customers and new mobility-driven applications and modes of work. For climate science, Cloud Computing's capacity to engage communities in the construction of new capabilies is perhaps the most important link between Cloud Computing and Big Data.

Data Analytics↗

High Resolution Nature Runs and the Big Data Challenge

NASA's Global Modeling and Assimilation Office at Goddard Space Flight Center is undertaking a series of very computationally intensive Nature Runs and a downscaled reanalysis. The nature runs use the GEOS-5 as an Atmospheric General Circulation Model (AGCM) while the reanalysis uses the GEOS-5 in Data Assimilation mode. This paper will present computational challenges from three runs, two of which are AGCM and one is downscaled reanalysis using the full DAS. The nature runs will be completed at two surface grid resolutions, 7 and 3 kilometers and 72 vertical levels. The 7 km run spanned 2 years (2005-2006) and produced 4 PB of data while the 3 km run will span one year and generate 4 BP of data. The downscaled reanalysis (MERRA-II Modern-Era Reanalysis for Research and Applications) will cover 15 years and generate 1 PB of data. Our efforts to address the big data challenges of climate science, we are moving toward a notion of Climate Analytics-as-a-Service (CAaaS), a specialization of the concept of business process-as-a-service that is an evolving extension of IaaS, PaaS, and SaaS enabled by cloud computing. In this presentation, we will describe two projects that demonstrate this shift. MERRA Analytic Services (MERRA/AS) is an example of cloud-enabled CAaaS. MERRA/AS enables MapReduce analytics over MERRA reanalysis data collection by bringing together the high-performance computing, scalable data management, and a domain-specific climate data services API. NASA's High-Performance Science Cloud (HPSC) is an example of the type of compute-storage fabric required to support CAaaS. The HPSC comprises a high speed Infinib and network, high performance file systems and object storage, and a virtual system environments specific for data intensive, science applications. These technologies are providing a new tier in the data and analytic services stack that helps connect earthbound, enterprise-level data and computational resources to new customers and new mobility-driven applications and modes of work. In our experience, CAaaS lowers the barriers and risk to organizational change, fosters innovation and experimentation, and provides the agility required to meet our customers' increasing and changing needs

big data analysis↗

The Flexible Lunar Architecture for Exploration (FLARE): Designed for the Artemis-3 Moon 2024 Mission and Beyond

The Flexible Lunar Architecture for Exploration (FLARE) is a concept to deliver four crew to the lunar surface for 7 to 14 days and then return them safely to Earth by 2024. This meets NASA’s internal 2024 lunar landing deadline directed by President Trump (Trump, 2017) and the “5-year” goal set forth by Vice President Pence (Pence, 2019). FLARE is an alternative to NASA’s Human Landing System reference architecture from the Design Analysis Cycle (DAC) #2 (NASA, 2019b). The minimum FLARE concept uses one Space Launch System launch, one Orion, one European Service Module (ESM), and one human lander to deliver four crew to the Moon for a minimum surface duration of 7 days and return them to Earth. FLARE adds a new capability, called the SpaceTug, based upon the mature and successful United Launch Alliance “Common” Centaur Upper Stage vehicle, with modifications. In FLARE, the SpaceTug provides propulsion needed to return the Orion+ESM from the Moon to Earth. The SpaceTug also provides propulsion to deliver the human lander Descent Element (DE) and Ascent Element (AE) separately to lunar orbit. The Orion+ESM then completes a rendezvous with the mated DE+AE in lunar orbit. FLARE also offers optional phases to the Moon 2024 mission. The SpaceTug can also deliver components of the planned Gateway - including the Power and Propulsion Element and the Habitation and Logistics Outpost - to lunar orbit; however, the planned FLARE destination is a Low Lunar Frozen Polar Orbit unlike the NASA DAC2 plan for a Near Rectilinear Halo Orbit. FLARE also provides an option to deliver precursor equipment - including a habitation module, crew mobility devices and an In-Situ Resource Utilization demonstration - to the lunar surface for enhanced crew exploration and science with the extended 14-day surface mission.

Commercial Launch Vehicles (CLV)↗

A Flexible Lunar Architecture for Exploration (FLARE) Supporting NASA’s Artemis Program

The Flexible Lunar Architecture for Exploration (FLARE) is a concept to deliver four crew to the lunar surface for a minimum of seven days and then return them safely to Earth. FLARE can be implemented whenever the component vehicles are operational. FLARE was developed as an alternative to NASA’s Human Landing System (HLS) reference architecture from the Design Analysis Cycle (DAC) #2 created in 2019. The DAC2 guidelines required utilization of the Gateway vehicle in a Near- Rectilinear Halo Orbit (NRHO). Instead, FLARE chooses a Low Lunar Frozen Polar Orbit (LLFPO) for lunar rendezvous of components, and an optional Gateway vehicle. The LLFPO provides a stable orbit that overflies the south pole every 2 h, ensuring easy access to the lunar surface for surface aborts with a much lower propellant requirement than NRHO. The minimum FLARE concept uses one Space Launch System (SLS) launch, one Orion, one European Service Module (ESM), and one human lander (launched on commercial vehicle(s)). FLARE adds the SpaceTug, based upon the mature and successful ULA “Common” Centaur Upper Stage vehicle, with modifications to create an Earth-Moon transfer vehicle. In the FLARE baseline mission, the SpaceTug provides propulsion needed to return the Orion + ESM from LLFPO to Earth. The SpaceTug also provides propulsion to deliver the separate human lander components – the Descent Element (DE) and the Ascent Element (AE) - from Low Earth Orbit (LEO) to LLFPO. The SLS Block 1 then launches the Orion + ESM and completes a rendezvous with the mated DE + AE components in LLFPO. FLARE offers optional phases beyond the baseline mission. The SpaceTug can deliver components of the planned Gateway, including the Power and Propulsion Element (PPE) and the Habitable and Logistics Outpost (HALO), to LLFPO. FLARE provides an option to deliver precursor equipment to the lunar surface to enhance and extend the human mission. With these components, including an inflatable habitation module and airlock, individual crew mobility vehicle(s), an In-Situ Resource Utilization (ISRU) demonstration, and science and technology experiments, the crew can explore and conduct science on the lunar surface for up to 14 days.

Moon 2024↗

Surface Systems and Interface Standardization

Space exploration on planetary surfaces will require the use of various surface systems which will likely need to interface with one another. These systems must communicate and share data, as well as distribute power and transfer fluids for sustainable surface operations. Such systems can range from landers, surface habitats, mobility systems, cargo, and In-Situ Resource Utilizations (ISRUs). Previous and current programs have developed space interoperability standards that help aid in reducing potential risks of interface integration. One example of this is the International Deep Space Interoperability Standards (IDSIS) which focuses on deep space exploration. A goal of the Artemis program is to develop a sustained human presence on the lunar surface that would be a training ground for future Mars exploration. Therefore, it will be beneficial to identify interface standards between the surface assets which will help mitigate risk and reduce complexity in the harsh environments of space exploration. A key contribution to sustainability is commonality between hardware and software interfaces. Generic interfaces for data, power, and fluids will reduce risk, promote interoperability, and define standard interfaces across surface exploration projects and programs. Standardized interfaces would be advantageous for improving efficiency and reducing overall complexity, which are critical considerations for future space exploration. Furthermore, it will provide cost reductions to the Artemis programs over their life cycle (in Operations & Maintenance (O&M) and Logistics). Unique proprietary interfaces if considered or allowed would not only increase complexity but also add cost to the programs. Of course, understanding what will work and not work effectively in these unique environments such as the lunar surface is important. These unique environments require much needed intelligent design, prototyping, comprehensive testing, and field experience, utilizing consensus on common interface solutions.

Jaime Gomez↗

Functional Mobility Testing: Quantification of Functionally Utilized Mobility Among Unsuited and Suited Subjects

A novel approach was used in this test for the creation of mobility requirements to be fed into the Human-Systems Integration Requirements and Engineering Requirements Documents. Existing suits may not provide adequate mobility to perform all functional tasks required in future missions. Looking solely at maximum unsuited mobility could be unrealistic and unnecessary to design into a suit. The new approach focused instead on functional range of motion. Setting design requirements based on the mobility necessary to perform a broad spectrum of functional tasks should save resources while still providing a suit capable of performing all tasks that a suited crewmember is likely to encounter. Unsuited functional mobility testing revealed some interesting nuances of human movement including variances in mobility utilized when completing functional tasks as well as the impact of compound joint motions and the influence of joint loading on range of motion. Suited requirements must reflect the fact that altered movement strategies are utilized while wearing a space suit. Improved methods for the creation of space suit design requirements should lead to improved suit performance while maintaining crewmember safety and reducing overall costs.

Scott A. England↗

Quantum Technologies for UAS (QTech)

Recent advances in small Unmanned Aerial System (sUAS) technologies lower the barriers for use by both private and commercial entities. However, these advances are also likely to lead to greater vehicle densities, a more heterogenous mix of vehicles and equipment and greater levels of vehicle autonomy, which can increase the chance for communications disruptions. For the safe and secure operation of these vehicles, it is essential to have a robust communications network. This work is focused on harnessing the power of quantum technologies to enable this robust communications network by: (1) utilizing quantum optimization algorithms to design robust network with routing redundancy that can respond adaptively to dynamically changing real-time environment and disruptions, (2) utilize quantum optimization algorithms resource allocation for detection, localization, and tracking of mobile communication disruption agents and (3) utilize quantum key distribution (QKD) to execute secure key sharing in anti-jamming protocols for secure radio frequency (RF) communication. Efforts to map these quantum optimization algorithms to commercially available quantum annealers and soon to be available general-purpose gate-model quantum hardware architectures will be reviewed, and plans for testing the solutions to these algorithms through indoor sUAS flight tests will be discussed. Lastly, efforts to miniaturize and practically deploy Quantum Key Distribution (QKD) hardware, which could ultimately be used to securely exchange encryption keys, in sUAS networks will be reviewed.

Quantum Computing↗

Quantum Technologies for UAS (QTech)

Harness the power of quantum technologies to assure the availability of UAS communications against disruptions. Make use of quantum computing (e.g. quantum optimization) and quantum communication (e.g. quantum key distribution) to address the availability cybersecurity challenge. Our approach is three-fold: (1) Utilize quantum optimization algorithms to design robust network with routing redundancy that can respond adaptively to dynamically changing real-time environment and disruptions, (2) Utilize quantum optimization algorithms resource allocation for detection, localization, and tracking of mobile communication disruption agents, (3) Utilize quantum key distribution (QKD) to execute secure key sharing in high data rate optical communication and/or anti-jamming protocols for secure RF communication.

Quantum Computing↗

Urban Air Mobility Airspace Integration Concepts and Considerations

Urban Air Mobility (UAM) - defined as safe and efficient air traffic operations in a metropolitan area for manned aircraft and unmanned aircraft systems - is being researched and developed by industry, academia, and government. Significant resources have been invested toward cultivating an ecosystem for Urban Air Mobility that includes manufacturers of electric vertical takeoff and landing aircraft, builders of takeoff and landing areas, and researchers of the airspace integration concepts, technologies, and procedures needed to conduct Urban Air Mobility operations safely and efficiently alongside other airspace users. This paper provides high-level descriptions of both emergent and early expanded operational concepts for Urban Air Mobility that NASA is developing. The scope of this work is defined in terms of missions, aircraft, airspace, and hazards. Past and current Urban Air Mobility operations are also reviewed, and the considerations for the data exchange architecture and communication, navigation, and surveillance requirements are also discussed. This paper will serve as a starting point to develop a framework for NASA's Urban Air Mobility airspace integration research and development efforts with partners and stakeholders that could include fast-time simulations, human-in-the-loop (HITL) simulations, and flight demonstrations.

airspace integration↗

Mobile data buoy system

The Mobile Data Buoy System was conceived to serve the users requirement for obtaining water quality parameters from two separate watershed systems. In view of the cost constraints of the ERTS program it was obvious that the network of 10 sampling stations required could not be of the fixed installation type; therefore, it was decided to go to a system of battery powered buoys of a size that could be used in one watershed system for a period of time and then moved to another by use of a relatively small 6.7 m (22 foot) boat. The basic idea of the water quality measurement program was to establish the water quality pattern of change from the headwaters of the watersheds to and through the Mobile Bay. This would allow the investigator to develop a good picture of the state's major water resources and the pressures from pollution that are being imposed. At this point in deployment of this mobile system of buoys, it is too early to put a quantitative value on the system, however it appears less expensive than known fixed installations as to first cost. It has a basic advantage in that it can be moved, at very little expense, to alternate sites where it is desired to obtain water quality data. It is to be noted this buoy system which covers a 80 Km (50 mile) stretch of the Black Warrior River and then skips down 483 Km (300 miles) to Mobile Bay for the next measurements would not be feasible unless there is a satellite to collect and relay the data.

Morton, R. A.↗

Lunar In-situ Resource Utilization Concept to Reality

ISRU is a capability involving multiple elements to achieve final products (mobility, product storage and delivery, power, crew and/or robotic maintenance, etc.) ‘ISRU’ does not exist on its own. By definition, it must connect and tie to users/customers of ISRU products and services Living Off the Land: ISRU involves any hardware or operation that harnesses and utilizes ‘in-situ’ (local) resources to create products and services for robotic and human exploration. Resource Examples •Water •Oxygen •Hydrogen •Carbon •Metals •Silicon •Nitrogen •Regolith/Rock •Discarded materials Product Examples •Propellant •Life Support Consumables •Feed stock for •Additive manufacturing •Construction •Agriculture substrate and/or fertilizer

lunar↗

Lunar Resources Catalog (LRC): Viper Pathfinder Dataset

Introduction: A new era in lunar exploration has recently begun. Through NASA’s robotic Commercial Lunar Payload Services (CLPS) initiative, international and the human Artemis programs, multiple assets are being deployed to explore the Moon and at a rapid cadence. There will be a huge expanse in lunar surface exploration with mobility (e.g., rovers). Several missions are focused on collecting data for assessing lunar resources for potential In-Situ Resource Utilization (ISRU). With this expansion in exploration there will be a commensurate expansion in the volume and variety of data. Work has begun on establishing a measurement plan (i.e., what data is needed) for ISRU [1] but how to integrate these data into the broader Planetary Data Ecosystem (PDE) following FAIR (i.e., Findability, Accessibility, Interoperability, and Reuse) data practices has not been addressed. The VIPER team intends to engage this challenge.

VIPER↗

Analysis of Strategic Conflict Management Approaches as Applied to Simulated UAM Operations

This report presents the results of a comparison analysis of candidate Strategic Conflict Management (SCM) strategies as applied to Urban Air Mobility (UAM) operations. The SCM strategies investigated included: no SCM, resource scheduling (RS), resource flow rates (FR), area-based flow rates (AR), and conflict detection and resolution (CR). The study evaluated each strategy against the same 3 levels of flight demand in a representative airspace construct for the Dallas/Fort Worth region. The study also accounted for different levels of uncertainty in operational planning and equivalent levels of trajectory following error. In the analysis, we compared the SCM strategies’ effectiveness in reducing the need for the tactical conflict management layer to act and looked at the metrics of unmitigated losses-of-separation (LOS), flight delays imposed by strategic planning, and throughput of the overall airspace. The study results indicated that the CR strategy was the most effective at reducing LOS and percentage of flights with LOS, even in the presence of trajectory error when uncertainty is accounted for in planning. Thus, if the objective is to reduce the number of actions that the tactical conflict management layer will have to take, in terms of conflicts that may need to be resolved, CR is the strategy to use. The FR strategy was found to be the worst at reducing LOS and percentage of flights with LOS. Thus, it is not very effective at reducing the actions required by a tactical conflict management layer. In the airspace tested, the demand was high enough to produce unacceptable levels of flight delay and reductions of throughput when the SCM strategies were implemented. This was especially evident at the higher levels of trajectory uncertainty and error. The need to account for expected levels of uncertainty becomes more and more important as the demand level increases and as the level of trajectory error increases. This is because the likelihood of flights with LOS increases as the density of operations increases and as the level of trajectory error increases. Accounting for uncertainty in the SCM strategies improves the strategy effectiveness with respect to LOS but increases delays and reduces throughput. Thus, there is a tradeoff between scalability and allowable levels of uncertainty. That is, we can implement an air traffic management construct that allows high levels of uncertainty, but we can expect that same system to have limits on scalability that may be evident even at small demand levels, such as those used in this study. Therefore, the results in this study indicate that an air traffic system should attempt to implement mechanisms appropriate for reducing uncertainty where possible in order to increase the chances for scalability. And this increased level of predictability of operations needs to be balanced with mechanisms for ensuring flexibility when operational conditions and plans need to change, even though those types of changes should be the exception rather than the rule under normal conditions. The study also introduced a trade space that could serve as a mechanism for selecting the appropriate SCM strategy in a trade-off between uncertainty and error, mean flight delay, and the LOS metrics (which this study equates to the potential for tactical conflict management actions). The optimal solution for a given airspace, demand level, and other factors, could likely be a combination of SCM strategies, although this study only compared the use of a single SCM strategy at a time. The CR strategy appeared to have the best opportunity for scalability by limiting the number of potential tactical actions to nearly zero.

Strategic Conflict Management↗

Artemis program: Rover/Mobility Systems Workshop results

Information is given in viewgraph form on the Artemis Program Rover/Mobility Systems Workshop results. Topics covered include an outpost site survey and resource assessment for Mare Tranquillitatis (15 n, 22 E). Viable mobility systems appear to be capable of supporting a 1997 launch. Achieving the defined mission objectives within a 65 kg payload appears to be possible, although with limited capability.

Weaver, Dave↗