SEARCH · Search NASA

Results for “network automation”

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.

SourceResearch connectionFrom yearThrough year

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

At least 343 records · Page 19

All sources NASA NTRS DOE OSTI

NASA NTRS1997

Managing Satellites

Integral Systems, Inc.'s EPOCH 2000 forms the core of NASA's Near Earth Asteroid Rendezvous (NEAR) mission's command and control center. EPOCH 2000, which allows ground operators to monitor and control satellites over a wide area network, owes part of its heritage from work completed to support Goddard Space Flight Center. The software automates telemetry processing, commanding, anomaly detection, and archiving collected data. The NEAR spacecraft, launched in February 1996, will rendezvous in early 1999 and orbit the Asteroid Eros for a year. Integral Systems also provided Low Earth Orbit Autonomous Ground Terminals (LEO-Ts) to NASA. The LEO-T is designed to make it easier and less expensive for principal investigators to obtain telemetry, tracking and control services for their science missions. The company products have supported well over 70 satellite missions aimed at scientific research, meteorology, or communications applications.

Source record↗

NASA NTRS2017

Evolution of NASA's Earth Science Digital Object Identifier Registration System

NASA's Earth Science Data and Information System (ESDIS) Project has implemented a fully automated system for assigning Digital Object Identifiers (DOIs) to Earth Science data products being managed by its network of 12 distributed active archive centers (DAACs). A key factor in the successful evolution of the DOI registration system over last 7 years has been the incorporation of community input from three focus groups under the NASA's Earth Science Data System Working Group (ESDSWG). These groups were largely composed of DOI submitters and data curators from the 12 data centers serving the user communities of various science disciplines. The suggestions from these groups were formulated into recommendations for ESDIS consideration and implementation. The ESDIS DOI registration system has evolved to be fully functional with over 5,000 publicly accessible DOIs and over 200 DOIs being held in reserve status until the information required for registration is obtained. The goal is to assign DOIs to the entire 8000+ data collections under ESDIS management via its network of discipline-oriented data centers. DOIs make it easier for researchers to discover and use earth science data and they enable users to provide valid citations for the data they use in research. Also for the researcher wishing to reproduce the results presented in science publications, the DOI can be used to locate the exact data or data products being cited.

DOI; digital object identifier; mappin↗

NASA NTRS2022

National Campaign (NC)-1 Strategic Conflict Management Simulation (X4) Community Based Rules

Projected demand for transportation services in the urban environment has led to the development of several Concepts of Operation for Urban Air Mobility, or UAM. UAM is a concept for the transportation of people and goods in the metropolitan environment using small, efficient aircraft over short distances as part of an expanding multimodal transportation network. UAM will leverage emerging technologies including electric Vertical Takeoff and Landing (eVTOL) aircraft, increasing levels of automation and a new operational paradigm in dense airspace where a set of agreed-upon rules govern the procedures and interactions defining a cooperative environment in which operators are entrusted with a range of functions typically conducted by Air Traffic Control (ATC). These rules, proposed in the FAA NextGen Office’s UAM Concept of Operations [1], were originally termed Community Based Rules or Community Business Rules (CBRs), and will in the future termed Cooperative Operating Practices (COPs); this document uses the original term, CBR. CBRs are a set of rules, developed by the UAM community and (where necessary) approved by the FAA that govern the interactions between UAM entities and limit the need for ATC services including, but not limited to, separation control by ATC, addressing a fundamental challenge to scaling UAM operations. UAM community development of CBRs is anticipated to accelerate the adoption of new practices while retaining the regulatory authority of the FAA within required domains (e.g., NAS safety, security and equal access). However, there currently exists no agreed industry forum or defined procedures for CBR development. Investigation of best practices for the development of UAM CBRs was identified by NASA and the FAA NextGen Office as a research need. In collaboration with seven industry partners, NASA participated in a series of simulations that investigated elements of the envisioned UAM operations, with a primary focus on Strategic Conflict Management (SCM). The development and conduct of cooperative UAM simulations with seven industry partners provided a unique opportunity to investigate CBR development practices. Development of CBRs for the UAM SCM simulations was conducted in parallel with simulation capability development and was closely related to requirements definition for the simulations. As such, the CBR development effort presented herein had two objectives: explore CBR development practices in collaboration with the industry partners and develop an initial set of UAM CBRs to support simulation requirements definition and development. Consensus was achieved among NASA and the industry partners on 24 CBRs that were developed to support the cooperative simulation operations across five topic areas: General (related to test requirements), Operational Intent, Conformance Monitoring, Demand Capacity Balancing, and Airspace Constraint Management. Additional topic areas and CBRs were discussed but were deemed outside the scope of the simulation; these are included in the appendices. A collaborative, iterative process was employed for developing the CBRs engaging both NASA and Industry; because CBR development is envisioned to be community-driven, opportunities were sought that provided industry partners leadership roles in developing CBRs. The following key observations and recommendations may aid the UAM industry in future CBR development efforts: - The lack of a defined process proved challenging initially. Stakeholder engagement in the early stages of CBR development was intermittent and may have been due to the lack of a clear definition of roles and responsibilities of those involved in the effort. - Industry leadership of CBR topic areas proved successful. Discussions in these topic areas were engaging, with alternate viewpoints freely discussed and detailed CBRs resulting. This points to the importance of identifying the best-suited leadership in technical areas for CBR development. - Discussions within a CBR topic area were typically dominated by only a few participants. Whereas all industry partners contributed to CBR development, within each topic area, technical leadership was evident even when not formally established. This observation may indicate that smaller, focused groups may be more effective in initial CBR development than an open forum or large standards development effort (although both maybe required prior to FAA review and approval for some CBRs). - Identifying suitable forums for initial UAM CBR development and identifying the most effective industry participants and leadership will be crucial for successful CBR development. Although the operational need for UAM CBRs may not be immediate, establishing the forums and leadership to define the processes for CBR development is a prudent early step to UAM realization.

Community Based Rules↗

NASA NTRSDate not supplied

Gateway Command and Data Handling Network Implementation and Validation

As initial Lunar Gateway modules approach design maturity, the Artemis Network Validation and Integration Lab (ANVIL) has begun demonstrations to validate avionics network dataflows. The flight architecture design includes utilizing Time-Triggered Ethernet (TTE) and layer-3 switching capabilities to enable greater automation and flexibility of critical and best effort traffic. Critical traffic is considered as Time-Triggered (TT), Rate Constrained (RC) and prioritized Best Effort (BE) traffic classes. End systems, such as mission computers, power control, and robotics, use three planes and all traffic classes while other devices interface via Best Effort. Typical best effort devices include video, laptops, wireless access points, and payloads. Other devices have a various hybrid approach of interfaces including alarms, telemetry/logging, and communication units. In the paper, we will present an update of the Gateway network architecture and how the system will operate nominally and during a stack topology reconfiguration. We will also discuss the network risks, and trade-offs of performance, flexibility, and redundancy. Finally, we will show the process for validation, demonstration, and verification approaches to the vehicle network.

Gateway↗

NASA NTRSDate not supplied

Initial Development and Integration of a Vertiport Automation System for Advanced Air Mobility Operations

The High Density Vertiplex Sub-Project, as part of NASA’s Advanced Air Mobility (AAM) Project, has been developing a reference Vertiport Automation System (VAS) to support the management of arrival and departure operations in the terminal area of a vertiport or network of inter-connected vertiports known as a vertiplex. The VAS is potentially a key element of an integrated AAM architecture that will enable greater levels of coordination and predictability for vertiport users through its integration and sharing of information, and greater control of vertiport resources for managing operators. This paper provides an overview of the VAS and a description of an initial implementation that has been integrated into a broader reference architecture as part of ongoing research. Examples from recent simulations are presented with an outline for next steps and considerations.

vertiport↗

NASA NTRS1993

A fault-tolerant intelligent robotic control system

This paper describes the concept, design, and features of a fault-tolerant intelligent robotic control system being developed for space and commercial applications that require high dependability. The comprehensive strategy integrates system level hardware/software fault tolerance with task level handling of uncertainties and unexpected events for robotic control. The underlying architecture for system level fault tolerance is the distributed recovery block which protects against application software, system software, hardware, and network failures. Task level fault tolerance provisions are implemented in a knowledge-based system which utilizes advanced automation techniques such as rule-based and model-based reasoning to monitor, diagnose, and recover from unexpected events. The two level design provides tolerance of two or more faults occurring serially at any level of command, control, sensing, or actuation. The potential benefits of such a fault tolerant robotic control system include: (1) a minimized potential for damage to humans, the work site, and the robot itself; (2) continuous operation with a minimum of uncommanded motion in the presence of failures; and (3) more reliable autonomous operation providing increased efficiency in the execution of robotic tasks and decreased demand on human operators for controlling and monitoring the robotic servicing routines.

Marzwell, Neville I.↗

NASA NTRS1985

Radar wind profilers

Continuous, automated measurement of tropospheric wind profiles with UHF and VHF Doppler radars has been demonstrated. Ground-based networks of these radars will be available as part of a global wind measurement system, and remote single stations could be built to further complement a spaceborne measurement device. A number of ground-based wind profilers will be in place by the time a space system is tested so the global wind measurement system should be designed with these ground-based profilers providing part of the picture.

Strauch, R. G.↗

NASA NTRS1998

A Survey of Applications and Research in Integrated Design Systems Technology

The initial part of the study was begun with a combination of literature searches, World Wide Web searches, and contacts with individuals and companies who were known to members of our team to have an interest in topics that seemed to be related to our study. There is a long list of such topics, such as concurrent engineering, design for manufacture, life-cycle engineering, systems engineering, systems integration, systems design, design systems, integrated product and process approaches, enterprise integration, integrated product realization, and similar terms. These all capture, at least in part, the flavor of what we describe here as integrated design systems. An inhibiting factor in this inquiry was the absence of agreed terminology for the study of integrated design systems. It is common for the term to be applied to what are essentially augmented Computer-Aided Design (CAD) systems, which are integrated only to the extent that agreements have been reached to attach proprietary extensions to proprietary CAD programs. It is also common for some to use the term integrated design systems to mean a system that applies only, or mainly, to the design phase of a product life cycle. It is likewise common for many of the terms listed earlier to be used as synonyms for integrated design systems. We tried to avoid this ambiguity by adopting the definition of integrated design systems that is implied in the introductory notes that we provided to our contacts, cited earlier. We thus arrived at this definition: Integrated Design Systems refers to the integration of the different tools and processes that comprise the engineering, of complex systems. It takes a broad view of the engineering of systems, to include consideration of the entire product realization process and the product life cycle. An important aspect of integrated design systems is the extent to which they integrate existing, "islands of automation" into a comprehensive design and product realization environment. As the study progressed, we relied increasingly upon a networking approach to lead us to new information. The departure point for such searches often was a government-sponsored project or a company initiative. The advantage of this approach was that short conversations with knowledgeable persons would usually cut through confusion over differences of terminology, thereby somewhat reducing the search space of the study. Even so, it was not until late in our eight-month inquiry that we began to see signs of convergence of the search, in the sense that a number of the latest inquiries began to turn up references to earlier contacts. As suggested above, this convergence often occurred with respect to particular government or company projects.

Source record↗

NASA NTRS2000

NASA Information Technology Implementation Plan

NASA's Information Technology (IT) resources and IT support continue to be a growing and integral part of all NASA missions. Furthermore, the growing IT support requirements are becoming more complex and diverse. The following are a few examples of the growing complexity and diversity of NASA's IT environment. NASA is conducting basic IT research in the Intelligent Synthesis Environment (ISE) and Intelligent Systems (IS) Initiatives. IT security, infrastructure protection, and privacy of data are requiring more and more management attention and an increasing share of the NASA IT budget. Outsourcing of IT support is becoming a key element of NASA's IT strategy as exemplified by Outsourcing Desktop Initiative for NASA (ODIN) and the outsourcing of NASA Integrated Services Network (NISN) support. Finally, technology refresh is helping to provide improved support at lower cost. Recently the NASA Automated Data Processing (ADP) Consolidation Center (NACC) upgraded its bipolar technology computer systems with Complementary Metal Oxide Semiconductor (CMOS) technology systems. This NACC upgrade substantially reduced the hardware maintenance and software licensing costs, significantly increased system speed and capacity, and reduced customer processing costs by 11 percent.

Source record↗

NASA NTRS2002

A Ground Systems Architecture Transition for A Distributed Operations System

The Marshall Space Flight Center (MSFC) Ground Systems Department (GSD) recently undertook an architecture change in the product line that serves the ISS program. As a result, the architecture tradeoffs between data system product lines that serve remote users versus those that serve control center flight control teams were explored extensively. This paper describes the resulting architecture that will be used in the ISS payloads program, and the resulting functional breakdown of the products that support that architecture. It also describes the lessons learned from the path that was followed, as a migration of products cause the need to reevaluate the allocation of functions across the architecture. The result is a set of innovative ground system solutions that is scalable so it can support facilities of wide-ranging sizes, from a small site up to large control centers. Effective use of system automation, custom components, design optimization for data management, data storage, data transmissions, and advanced local and wide area networking architectures, plus the effective use of Commercial-Off-The-Shelf (COTS) products, provides flexible Remote Ground System options that can be tailored to the needs of each user. This paper offers a description of the efficiency and effectiveness of the Ground Systems architectural options that have been implemented, and includes successful implementation examples and lessons learned.

Sellers, Donna↗

NASA NTRS2003

A Ground Systems Architecture Transition for a Distributed Operations System

The Marshall Space Flight Center (MSFC) Ground Systems Department (GSD) recently undertook an architecture change in the product line that serves the ISS program. As a result, the architecture tradeoffs between data system product lines that serve remote users versus those that serve control center flight control teams were explored extensively. This paper describes the resulting architecture that will be used in the International Space Station (ISS) payloads program, and the resulting functional breakdown of the products that support this architecture. It also describes the lessons learned from the path that was followed, as a migration of products cause the need to reevaluate the allocation of functions across the architecture. The result is a set of innovative ground system solutions that is scalable so it can support facilities of wide-ranging sizes, from a small site up to large control centers. Effective use of system automation, custom components, design optimization for data management, data storage, data transmissions, and advanced local and wide area networking architectures, plus the effective use of Commercial-Off-The-Shelf (COTS) products, provides flexible Remote Ground System options that can be tailored to the needs of each user. This paper offers a description of the efficiency and effectiveness of the Ground Systems architectural options that have been implemented, and includes successful implementation examples and lessons learned.

Sellers, Donna↗

NASA NTRS2006

Use of Virtual Mission Operations Center Technology to Achieve JPDO's Virtual Tower Vision

The Joint Program Development Office has proposed that the Next Generation Air Transportation System (NGATS) consolidate control centers. NGATS would be managed from a few strategically located facilities with virtual towers and TRACONS. This consolidation is about combining the delivery locations for these services not about decreasing service. By consolidating these locations, cost savings in the order of $500 million have been projected. Evolving to spaced-based communication, navigation, and surveillance offers the opportunity to reduce or eliminate much of the ground-based infrastructure cost. Dynamically adjusted airspace offers the opportunity to reduce the number of sectors and boundary inconsistencies; eliminate or reduce "handoffs;" and eliminate the distinction between Towers, TRACONS, and Enroute Centers. To realize a consolidation vision for air traffic management there must be investment in networking. One technology that holds great potential is the use of Virtual Mission Operations Centers to provide secure, automated, intelligent management of the NGATS. This paper provides a conceptual framework for incorporating VMOC into the NGATS.

Ivancic, William D.↗

NASA NTRS2011

Software Architecture to Support the Evolution of the ISRU RESOLVE Engineering Breadboard Unit 2 (EBU2)

The In-Situ Resource Utilization (ISRU) Regolith & Environmental Science and Oxygen & Lunar Volatiles Extraction (RESOLVE) software provides operation of the physical plant from a remote location with a high-level interface that can access and control the data from external software applications of other subsystems. This software allows autonomous control over the entire system with manual computer control of individual system/process components. It gives non-programmer operators the capability to easily modify the high-level autonomous sequencing while the software is in operation, as well as the ability to modify the low-level, file-based sequences prior to the system operation. Local automated control in a distributed system is also enabled where component control is maintained during the loss of network connectivity with the remote workstation. This innovation also minimizes network traffic. The software architecture commands and controls the latest generation of RESOLVE processes used to obtain, process, and quantify lunar regolith. The system is grouped into six sub-processes: Drill, Crush, Reactor, Lunar Water Resource Demonstration (LWRD), Regolith Volatiles Characterization (RVC) (see example), and Regolith Oxygen Extraction (ROE). Some processes are independent, some are dependent on other processes, and some are independent but run concurrently with other processes. The first goal is to analyze the volatiles emanating from lunar regolith, such as water, carbon monoxide, carbon dioxide, ammonia, hydrogen, and others. This is done by heating the soil and analyzing and capturing the volatilized product. The second goal is to produce water by reducing the soil at high temperatures with hydrogen. This is done by raising the reactor temperature in the range of 800 to 900 C, causing the reaction to progress by adding hydrogen, and then capturing the water product in a desiccant bed. The software needs to run the entire unit and all sub-processes; however, throughout testing, many variables and parameters need to be changed as more is learned about the system operation. The Master Events Controller (MEC) is run on a standard laptop PC using Windows XP. This PC runs in parallel to another laptop that monitors the GC, and a third PC that monitors the drilling/ crushing operation. These three PCs interface to the process through a CompactRIO, OPC Servers, and modems.

Moss, Thomas↗

NASA NTRS2002

The Micro-Pulse Lidar Network (MPL-Net)

In the early 1990s, the first small, eye-safe, and autonomous lidar system was developed, the Micro-pulse Lidar (MPL). The MPL has proven to be useful in the field because it can be automated, runs continuously (day and night), is eye-safe, can easily be transported and set up, and has a small field-of-view which limits multiple scattering concerns. The MPL acquires signal profiles of backscattered laser light from aerosols and clouds. The signals are analyzed to yield multiple layer heights, optical depths of each layer, average extinction-to-backscatter ratio of each layer, and profiles of extinction in each layer. The MPL has been used in a wide variety of field studies over the past 10 years, leading to nearly 20 papers and many conference presentations. In 2000, a new project using MPL systems was started at NASA Goddard Space Flight Center. The MPL-Net project is currently working to establish a worldwide network of MPL systems, all co-located with NASA's AERONET sunphotometers for joint measurements of optical depth and sky radiance. Automated processing algorithms have been developed to produce data products on a next day basis for all sites and some field experiments. Initial results from the first several sites are shown, along with aerosol data collected during several major field campaigns. Measurements of the aerosol extinction-to-backscatter ratio at several different geographic regions, and for various aerosol types are shown. This information is used to improve the construction of look up tables of the ratio, needed to process aerosol profiles acquired with satellite based lidars.

Welton, Ellsworth J.↗

NASA NTRSDate not supplied

1D-Convolutional Neural Network Architecture for Generalized Time-Segmentation Tasks

Time segmentation of experimental data is a common and often difficult task. Consequently, it is of interest to automate this type of segmentation to reduce manual inputs, which are labor intensive and less consistent. However, simple thresholding algorithms are often insufficiently robust due either to noise or inconsistent data. This paper proposes a simple 1D CNN architecture as a generalized solution for typical time segmentation tasks. The layer architecture, training methods, and methods for simple customization are described as well as the results of application to three separate arc jet data streams: facility condition segmentation, video highlight segmentation, and calorimeter time-series segmentation.

Machine learning↗

NASA NTRSDate not supplied

1d-Convolutional Neural Network Architecture for Generalized Time-Segmentation Tasks

Machine learning↗

NASA NTRSDate not supplied

1D-Convolutional Neural Network Architecture for Generalized Time-Segmentation Tasks

Time segmentation of experimental data is a common and often difficult task. Consequently, it is of interest to automate this type of segmentation to reduce manual inputs, which are labor intensive and less consistent. However, simple thresholding algorithms are often insufficiently robust due either to noise or inconsistent data. This paper proposes a simple 1D convolutional neural net (CNN) architecture as a generalized solution for typical time segmentation tasks. The layer architecture, training methods, and methods for simple customization are described as well as the results of application to three separate arc jet data streams: facility condition segmentation, video highlight segmentation, and calorimeter time-series segmentation.

Machine learning↗

NASA NTRSDate not supplied

1D-Convolutional Neural Network Architecture for Generalized Time-series Segmentation

Time segmentation of experimental data is a common and often difficult task. Consequently, it is of interest to automate this type of segmentation to reduce manual inputs, which are labor intensive and less consistent. However, simple thresholding algorithms are often insufficiently robust due either to noise or inconsistent data. This paper proposes a simple 1D convolutional neural net (CNN) architecture as a generalized solution for typical time segmentation tasks. The layer architecture, training methods, and methods for simple customization will be described as well as the results of application to three separate data streams: facility condition segmentation, video highlight segmentation, and calorimeter time-series segmentation. In all three test cases the 1D-CNN performs better than tailored integral/derivative/thresholding algorithms across a range of signal-to-noise levels.

CNN↗