Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “interoperability and control”

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 91 records · Page 5
All sourcesNASA NTRSDOE OSTI
NASA NTRS2010

Use of Dynamic Models and Operational Architecture to Solve Complex Navy Challenges

The United States Navy established 8 Maritime Operations Centers (MOC) to enhance the command and control of forces at the operational level of warfare. Each MOC is a headquarters manned by qualified joint operational-level staffs, and enabled by globally interoperable C41 systems. To assess and refine MOC staffing, equipment, and schedules, a dynamic software model was developed. The model leverages pre-existing operational process architecture, joint military task lists that define activities and their precedence relations, as well as Navy documents that specify manning and roles per activity. The software model serves as a "computational wind-tunnel" in which to test a MOC on a mission, and to refine its structure, staffing, processes, and schedules. More generally, the model supports resource allocation decisions concerning Doctrine, Organization, Training, Material, Leadership, Personnel and Facilities (DOTMLPF) at MOCs around the world. A rapid prototype effort efficiently produced this software in less than five months, using an integrated process team consisting of MOC military and civilian staff, modeling experts, and software developers. The work reported here was conducted for Commander, United States Fleet Forces Command in Norfolk, Virginia, code N5-0LW (Operational Level of War) that facilitates the identification, consolidation, and prioritization of MOC capabilities requirements, and implementation and delivery of MOC solutions.

Grande, Darby↗
NASA NTRSDate not supplied

Gateway - A Communications Platform for Lunar Exploration

As stated by a NASA administrator, “NASA, International Partners, and commercial partner are going forward to the moon. With Artemis, we will be exploring more of the Moon than ever before, and this time we are planning to stay. We will be demonstrating new technologies, capabilities, and business approaches needed for future exploration of Mars.” To support the complex, Artemis exploration campaign envisioned, the Gateway program is developing a communication network orbiting the Moon. Gateway will provide relay communication paths and radiometric tracking between crewed and robotic systems on the lunar surface or in cis-lunar space to mission control on the Earth. This paper is a high-level description of Gateway’s communication and ranging capabilities, the motivation and use of internationally developed interoperability standards, potential upgrade opportunities, and challenges as Gateway enables technology to support future Mars exploration.

Artemis↗
NASA NTRSDate not supplied

ICARTT File Format Enhancements: Supporting FAIRness of Airborne and Field Campaign Data

The ICARTT (International Consortium for Atmospheric Research on Transport and Transformation) standards were developed to fulfill data management needs for the ICARTT campaign in 2004. The ICARTT file format is text-based and composed of a header with important data description information and the data section. The ICARTT format, built on the NASA Ames and GTE data formats, was created to facilitate data exchange and promote collaborations among the science teams for achieving the ICARTT campaign goals. Due to the success of the ICARTT campaign, the ICARTT file format was exposed to a broad range of airborne researchers and was adopted for use in many other field campaigns sponsored by NASA and other partner agencies. The ICARTT format standards became a NASA standard in 2010 and was amended in January 2017 providing many enhancements, including the requirement for variable standard names. Primarily designed for airborne field studies, ICARTT has been further utilized for ground-based studies. The ICARTT format can host metadata that is critical for proper use of the data, especially for in-situ measurements. However, the information that needs to be included is often in free text, meaning the information are human readable, but not machine interpretable. Furthermore, the amount and type of information provided can vary substantially between principal investigators and campaigns. To support interoperability and FAIR principles, further enhancements to the ICARTT standards are recommended. Possible recommendations include standardizing timestamps for easier data comparisons and analysis; potential use of controlled and consistent vocabulary for variable short name and certain common metadata elements; and providing guidance on variable measurement units and how they are reported.

Megan Buzanowicz↗
NASA NTRS1993

Repository-Based Software Engineering Program: Working Program Management Plan

Repository-Based Software Engineering Program (RBSE) is a National Aeronautics and Space Administration (NASA) sponsored program dedicated to introducing and supporting common, effective approaches to software engineering practices. The process of conceiving, designing, building, and maintaining software systems by using existing software assets that are stored in a specialized operational reuse library or repository, accessible to system designers, is the foundation of the program. In addition to operating a software repository, RBSE promotes (1) software engineering technology transfer, (2) academic and instructional support of reuse programs, (3) the use of common software engineering standards and practices, (4) software reuse technology research, and (5) interoperability between reuse libraries. This Program Management Plan (PMP) is intended to communicate program goals and objectives, describe major work areas, and define a management report and control process. This process will assist the Program Manager, University of Houston at Clear Lake (UHCL) in tracking work progress and describing major program activities to NASA management. The goal of this PMP is to make managing the RBSE program a relatively easy process that improves the work of all team members. The PMP describes work areas addressed and work efforts being accomplished by the program; however, it is not intended as a complete description of the program. Its focus is on providing management tools and management processes for monitoring, evaluating, and administering the program; and it includes schedules for charting milestones and deliveries of program products. The PMP was developed by soliciting and obtaining guidance from appropriate program participants, analyzing program management guidance, and reviewing related program management documents.

Source record↗
NASA NTRS2016

UAV Research at NASA Langley: Towards Safe, Reliable, and Autonomous Operations

Unmanned Aerial Vehicles (UAV) are fundamental components in several aspects of research at NASA Langley, such as flight dynamics, mission-driven airframe design, airspace integration demonstrations, atmospheric science projects, and more. In particular, NASA Langley Research Center (Langley) is using UAVs to develop and demonstrate innovative capabilities that meet the autonomy and robotics challenges that are anticipated in science, space exploration, and aeronautics. These capabilities will enable new NASA missions such as asteroid rendezvous and retrieval (ARRM), Mars exploration, in-situ resource utilization (ISRU), pollution measurements in historically inaccessible areas, and the integration of UAVs into our everyday lives all missions of increasing complexity, distance, pace, and/or accessibility. Building on decades of NASA experience and success in the design, fabrication, and integration of robust and reliable automated systems for space and aeronautics, Langley Autonomy Incubator seeks to bridge the gap between automation and autonomy by enabling safe autonomous operations via onboard sensing and perception systems in both data-rich and data-deprived environments. The Autonomy Incubator is focused on the challenge of mobility and manipulation in dynamic and unstructured environments by integrating technologies such as computer vision, visual odometry, real-time mapping, path planning, object detection and avoidance, object classification, adaptive control, sensor fusion, machine learning, and natural human-machine teaming. These technologies are implemented in an architectural framework developed in-house for easy integration and interoperability of cutting-edge hardware and software.

Davila, Carlos G.↗
NASA NTRSDate not supplied

Impact of NASA’s Entry Systems Modeling Project on Planetary Mission Design

Planetary missions continue to grow larger and more complex. Furthermore, the current focus on human exploration of the Moon and Mars, as well as Mars Sample Return(MSR), place increas-ingly stringent requirements on the reliability of the entry, descent, and landing (EDL) system that ensures the safe delivery of payload or crew to their destination. Planetary EDL is an area in which mission designers are critically reliant on modeling and simulation to demonstrate the reliability of the system, as there are no ground facilities that are able to fully test these systems in a flight-relevant environment. NASA’s state-of-the-art modeling and simulation capability must continually evolve to meet the needs of the next generation of planetary EDL. To accomplish this aim, NASA’s Entry Systems Modeling (ESM) Project was formed in 2013and is funded bythe Space Technology Mission Directorate(STMD) and Science Mission Directorate (SMD). ESM is the Agency’s only cross-cutting effort for advancing entry systems modeling and simulation capabilities across a range of technical disciplines and Solar System destinations. ESM is a portfolio project covering a variety of mid-TRL research efforts within four core EDL-related areas of investment: (1) Thermal protection material modeling, (2) Shock layer kinetics and radiation, (3) Aerosciences, and (4) Guidance, navigation, and con-trol. The material modeling group creates detailed material response modelsof thermal protection systems (TPS)from the micro to macro scale, and at the fun-damental and engineering levels. Shock layer kinetics and radiation focuses on radiative heating of space-craft, quantum chemistry and benchmark experiments for validation.Aerosciences is a broad research area that impacts many aspects of entry systems, including parachutes, aerodynamics, and turbulent heating augmentation due to TPS roughness.The guidance, navigation,and control effort under ESM is expanding the capabilities of NASA’s main flight mechanics tool, POST2, for use on high-performance computing architectures and to generalize interoperability with external applications for more detailed end-to-end simula-tion.In addition, several focusedresearch topics have been approvedto augment ESM’s core portfolio. These include efforts for deep post-flight analysis of Mars 2020/MEDLI2 flight data; development ofTPS failure models; improvement of hypersonic wakeflow models; and a recently concluded effort to provide material response models for NuSil-coated PICA heat-shield material. This presentation will discuss each of these investment areas and demonstrate via real mission examples how advances to the state-of-the-art enabled by ESM are directly impacting the missions of today and tomorrow, including InSight, Mars 2020, Mars Sample Return, Orion, and Dragonfly.

Entry Systems Modeling↗
NASA NTRS2022

Overview of NASA’s Extensible Traffic Management (xTM) Research

NASA’s Unmanned Aircraft Systems (UAS) Traffic Management (UTM) project introduced a new Air Traffic Management (ATM) architecture that utilizes industry’s ability to supply industry-developed, third-party services that work complementarily with the FAA-provided Air Traffic Service (ATS) to exchange relevant air vehicle information among the UAS operations and between the UTM and the conventional ATM system. The UTM architecture was used to successfully demonstrate the feasibility of safe, efficient, and scalable small UAS operations in low altitudes below 400 feet above ground level. Following the success and adoption of UTM architecture, the foundational UTM requirements and core properties were generalized to become Extensible Traffic Management (xTM) requirements to support operations of new entrants beyond small UAS, such as operations in high altitudes over 60,000 feet, designated as upper Class E in the United States National Airspace System (NAS). In this paper, the generalization of UTM to xTM and NASA’s approach for developing an xTM system for upper Class E Traffic Management (ETM) are discussed. The paper also discusses the planned research to examine the potential xTM-Air Traffic Control (ATC) interactions across multiple xTM systems and identify common coordination procedures, ATC roles/responsibilities, and data exchange requirements. This work is one of the steps for improving interoperability between the xTM systems and ATS, which is critical for safe and efficient sharing of the airspace among the new entrants served by the xTM systems and conventional ATS-serviced operations.

air traffic management↗
NASA NTRSDate not supplied

Overview of NASA’s Extensible Traffic Management (xTM) Work

NASA’s Unmanned Aircraft Systems (UAS) Traffic Management (UTM) project introduced a new Air Traffic Management (ATM) architecture that utilizes industry’s ability to supply industry-developed, third-party services that work complementarily with the FAA-provided Air Traffic Service (ATS) to exchange relevant air vehicle information among the UAS operations and between the UTM and the conventional ATM system. The UTM architecture was used to successfully demonstrate the feasibility of safe, efficient, and scalable small UAS operations in low altitudes below 400 feet above ground level. Following the success and adoption of UTM architecture, the foundational UTM requirements and core properties were generalized to become Extensible Traffic Management (xTM) requirements to support operations of new entrants beyond small UAS, such as operations in high altitudes over 60,000 feet, designated as upper Class E in the United States National Airspace System (NAS). In this paper, the generalization of UTM to xTM and NASA’s approach for developing an xTM system for upper Class E Traffic Management (ETM) are discussed. The paper also discusses the planned research to examine the potential xTM-Air Traffic Control (ATC) interactions across multiple xTM systems and identify common coordination procedures, ATC roles/responsibilities, and data exchange requirements. This work is one of the steps for improving interoperability between the xTM systems and ATS, which is critical for safe and efficient sharing of the airspace among the new entrants served by the xTM systems and conventional ATS-serviced operations.

air traffic management↗
NASA NTRS1999

High-Speed TCP Testing

Transmission Control Protocol (TCP) is the underlying protocol used within the Internet for reliable information transfer. As such, there is great interest to have all implementations of TCP efficiently interoperate. This is particularly important for links exhibiting long bandwidth-delay products. The tools exist to perform TCP analysis at low rates and low delays. However, for extremely high-rate and lone-delay links such as 622 Mbps over geosynchronous satellites, new tools and testing techniques are required. This paper describes the tools and techniques used to analyze and debug various TCP implementations over high-speed, long-delay links.

Brooks, David E.↗
NASA NTRS2011

Motion Imagery and Robotics Application (MIRA)

Objectives include: I. Prototype a camera service leveraging the CCSDS Integrated protocol stack (MIRA/SM&C/AMS/DTN): a) CCSDS MIRA Service (New). b) Spacecraft Monitor and Control (SM&C). c) Asynchronous Messaging Service (AMS). d) Delay/Disruption Tolerant Networking (DTN). II. Additional MIRA Objectives: a) Demo of Camera Control through ISS using CCSDS protocol stack (Berlin, May 2011). b) Verify that the CCSDS standards stack can provide end-to-end space camera services across ground and space environments. c) Test interoperability of various CCSDS protocol standards. d) Identify overlaps in the design and implementations of the CCSDS protocol standards. e) Identify software incompatibilities in the CCSDS stack interfaces. f) Provide redlines to the SM&C, AMS, and DTN working groups. d) Enable the CCSDS MIRA service for potential use in ISS Kibo camera commanding. e) Assist in long-term evolution of this entire group of CCSDS standards to TRL 6 or greater.

Martinez, Lindolfo↗
NASA NTRS1988

Orbital Maneuvering Vehicle space station communications design

The authors present an Orbital Maneuvering Vehicle space station communications systems design approach which is intended to satisfy the stringent link requirements. The operational scenario, system configuration, signal design, antenna system management, and link performance analysis are discussed in detail. It is shown that the return link can transmit up to 21.6 Mb/s and maintain at least a 3-dB link margin through proper power and antenna management control at a maximum distance of 37 km. It is suggested that the proposed system, which is compatible with the space station multiple-access system, can be a model for other space station interoperating elements or users to save the development cost and reduce the technical and schedule risks.

Arndt, D.↗
NASA NTRSDate not supplied

Some Aeronautical Communications Experiments

Classically there has existed an asymmetry between the computing and communicating sides of aerospace systems. Over the past few decades, this asymmetry has shifted to favoring communication link technologies, meaning that advancements in available central processing units (CPUs), storage devices, and internal data buses have stagnated. Indeed, the increased emphasis placed on refining subsystem performance such as with antenna bandwidth in phased arrays, amplifier power efficiency, software defined radio (SDR) flexibility and encoding for data compression and error correction has given rise to successful debuts of multi-gigabit-per-second data return from long space-link distances. These accomplishments are easily quantifiable through link budgets and illustrate what is possible, but also reveal the deficiencies in overall communications capabilities. In particular, the ever-accelerating presence of aerospace vehicles gives rise to newer and larger classes of challenges to address the needs of 21st century systems. Furthermore remote sensing and imaging capabilities have far outpaced our ability to transmit their products to the ground, so we are increasingly dependent on pre-processing and downselection to contend with the communications bottleneck. No longer may we depend upon the constrained logistics in delivering end-to-end data delivery through manual reconfigurations, static event scheduling and execution on a per-vehicle basis, for these methods do not scale and therefore must give way to dynamic, networked approaches with an overall systems view in mind. Emerging mission requirements exhibit a trend toward multiple smaller-scale vehicles working together to perform dissimilar observations. Such operations necessitate sensor fusion across a constellation, and where data processing may be distributed throughout a fairly disconnected network whose topology changes over time in non-deterministic manners. Individual communications link performance is still very relevant to deploying an effective communications system, but now must be embedded within a greater architecture of capability to optimally utilize the bandwidth available from each link to generate an ultimate end-to-end quality of service. The deleterious effects of timing uncertainty across the arrangement presents a challenge to measurement synchronization and delivery, so a successful deployed system needs to be tolerant to the delays inherent in time-of-light between elements and digital processing latencies existing at each node. In this presentation we share the flight test results from a high performance Gbps laser communications terminal evaluated with a suite of store and forward capabilities called High-rate Delay Tolerant Networking (HDTN). The communications payload is operated over Lake Erie across a range of configurations including several convergence layers, and is evaluated to determine recovery time after link disruptions, information loss, efficiency and speed. The effectiveness of utilizing a flying laboratory to increase the Technology Readiness Level (TRL) of an integrated system in relevant environments is discussed, as well as the value of conducting aeronautics experiments to retire risk for technology infusion into space missions. Upcoming flight campaigns will be presented, including opportunities to demonstrate secure command and control, data intensive hyperspectral imaging, quantum link characterization, 4k High Definition (HD) video streaming and internetworked space-ground-aero relay operations. These experiments will pave the way for future missions which will depend upon interoperability across disparate government and privately owned networks, involve contention with uncertain and dynamic timing, and require agility to autonomously configure optimal parameters across networks of ever-increasing size and complexity to ensure data delivery. https://www1.grc.nasa.gov/space/scan/acs/tech-studies/dtn/

Daniel Raible↗
NASA NTRSDate not supplied

Simulating Secure Data Exchange and Storage for Urban Air Mobility Environments

Urban Air Mobility (UAM) defines an environment for managing operations of vertical takeoff and landing (VTOL) and short takeoff and landing (STOL) vehicles in an urban environment. Within a UAM environment, UAM operators manage fleets of vehicles, relying on Providers of Services for UAM (PSUs) for managing flights in a region of airspace. Flight plan deconfliction is primarily performed by the Discovery and Synchronization Service (DSS), and the Federal Aviation Administration (FAA) maintains control over the UAM space via the FAA-Industry Exchange Protocol (FIDXP). UAM is a federated environment with many different entities owning and operating vehicles, PSUs, and other services. These entities often need to interoperate or access data generated by other organizations. This paper demonstrates the feasibility of using blockchain to facilitate a secure data exchange and storage for this flight information in a UAM environment. In particular, this paper is focused on flight plans and telemetry data. A blockchain network was developed with a set of smart contracts for managing relevant flight data. Hyperledger Fabric was chosen as it is performent, scalable, and allows organizations to reuse existing public key infrastructure (PKI) for identity management. A set of simulated UAM services were also developed. These services propose flight plans and negotiate with other UAM services for airspace access. All interactions between UAM services, as well as vehicle telemetry data, is recorded onto the blockchain. Vehicle telemetry data is generated by a vehicle flight simulation service. This paper successfully demonstrates the feasibility of using blockchain as a secure data exchange and storage mechanism in a UAM environment.

UAM↗
NASA NTRS2018

Model-Driven Development For PDS4 Software And Services

Software and services that access Planetary Data System (PDS) PDS4 data products need to parse product labels to retrieve, interpret, and process the referenced digital objects. Under PDS4 a driving principle is that the product label provide all of the information necessary for these functions to be performed accurately. However, significantly more information is available in the PDS4 Information Model (IM)[1], the controlling document used to define, create, and syntactically and semantically verify the product labels. This additional information in the IM is made available for use, by both software and services, to configure, promote resiliency, and improve interoperability.

Padams, Jordan↗
NASA NTRS1992

Deep Space Network information system architecture study

The purpose of this article is to describe an architecture for the Deep Space Network (DSN) information system in the years 2000-2010 and to provide guidelines for its evolution during the 1990s. The study scope is defined to be from the front-end areas at the antennas to the end users (spacecraft teams, principal investigators, archival storage systems, and non-NASA partners). The architectural vision provides guidance for major DSN implementation efforts during the next decade. A strong motivation for the study is an expected dramatic improvement in information-systems technologies, such as the following: computer processing, automation technology (including knowledge-based systems), networking and data transport, software and hardware engineering, and human-interface technology. The proposed Ground Information System has the following major features: unified architecture from the front-end area to the end user; open-systems standards to achieve interoperability; DSN production of level 0 data; delivery of level 0 data from the Deep Space Communications Complex, if desired; dedicated telemetry processors for each receiver; security against unauthorized access and errors; and highly automated monitor and control.

Beswick, C. A.↗
NASA NTRSDate not supplied

Evolving the SpaceFOM: Lessons Learned and Future Development

For over fifty years, simulation has been a cornerstone technology for space missions. In many cases, one single simulator, developed by one team, is not enough to meet the simulation objectives. Astronaut crew training, docking, vehicle testing and complex mission planning all require several simulations to be connected and to interoperate, in order to achieve the goal of the simulation. To facilitate the development of interoperable simulations, an open standard, the SISO SpaceFOM was developed in collaboration between government, industry and academia. The standard was released in 2020. The initial release of SpaceFOM focuses on the core interoperability topics for space simulation: (i) specifying spatial data using several, well defined reference frames, (ii) managing time (including real-time, hard real-time, and as-fast-as-possible execution), (iii) composition of systems with subsystems such as space vehicles, and (iv) execution control, such as initializing, running, pausing, and terminating simulations. A number of requirements for the next version of SpaceFOM have been identified and proposed solutions are already under development. One key area is the object classes used for data exchange, where a richer set of classes have been proposed, based on practical use cases. For time management, the use of variable time resolutions and variable time steps is also proposed. For execution control, save and restore of simulations is considered as well as improved robustness, to handle failing components. A number of clarifications are also under consideration. This paper provides both a forward-looking view of the technical developments underway and a retrospective on the standard's evolution. The authors emphasize that prioritizing core challenges and delivering a practical first version were crucial steps. While not every idea was implemented in the initial release, the timely delivery of a functional standard enabled real-world applications, the growth of a user community, and the collection of valuable insights to shape future versions. The authors look forward to working with the next version of SpaceFOM together with the growing user community.

FOMs↗
NASA NTRS2010

Space Communications and Navigation (SCaN) Integrated Network Architecture Definition Document (ADD): Executive Summary - Volume 1

The SCaN Program has defined an integrated network architecture that fully meets the Administrator s mandate to the Program, and will result in a NASA infrastructure capable of providing the needed and enabling communications services to future space missions. The integrated network architecture will increase SCaN operational efficiency and interoperability through standardization, commonality and technology infusion. It will enable NASA missions requiring advanced communication and tracking capabilities such as: a. Optical communication b. Antenna arraying c. Lunar and Mars Relays d. Integrated network management (service management and network control) and integrated service execution e. Enhanced tracking for navigation f. Space internetworking with DTN and IP g. End-to-end security h. Enhanced security services Moreover, the SCaN Program has created an Integrated Network Roadmap that depicts an orchestrated and coherent evolution path toward the target architecture, encompassing all aspects that concern network assets (i.e., operations and maintenance, sustaining engineering, upgrade efforts, and major development). This roadmap identifies major NASA ADPs, and shows dependencies and drivers among the various planned undertakings and timelines. The roadmap is scalable to accommodate timely adjustments in response to Agency needs, goals, objectives and funding. Future challenges to implementing this architecture include balancing user mission needs, technology development, and the availability of funding within NASA s priorities. Strategies for addressing these challenges are to: define a flexible architecture, update the architecture periodically, use ADPs to evaluate options and determine when to make decisions, and to engage the stakeholders in these evaluations. In addition, the SCaN Program will evaluate and respond to mission need dates for technical and operational capabilities to be provided by the SCaN integrated network. In that regard, the architecture defined in this ADD is scalable to accommodate programmatic and technical changes.

Younes, Badri A.↗
NASA NTRS2010

Reinventing User Applications for Mission Control

In 2006, NASA Ames Research Center's (ARC) Intelligent Systems Division, and NASA Johnson Space Centers (JSC) Mission Operations Directorate (MOD) began a collaboration to move user applications for JSC's mission control center to a new software architecture, intended to replace the existing user applications being used for the Space Shuttle and the International Space Station. It must also carry NASA/JSC mission operations forward to the future, meeting the needs for NASA's exploration programs beyond low Earth orbit. Key requirements for the new architecture, called Mission Control Technologies (MCT) are that end users must be able to compose and build their own software displays without the need for programming, or direct support and approval from a platform services organization. Developers must be able to build MCT components using industry standard languages and tools. Each component of MCT must be interoperable with other components, regardless of what organization develops them. For platform service providers and MOD management, MCT must be cost effective, maintainable and evolvable. MCT software is built from components that are presented to users as composable user objects. A user object is an entity that represents a domain object such as a telemetry point, a command, a timeline, an activity, or a step in a procedure. User objects may be composed and reused, for example a telemetry point may be used in a traditional monitoring display, and that same telemetry user object may be composed into a procedure step. In either display, that same telemetry point may be shown in different views, such as a plot, an alpha numeric, or a meta-data view and those views may be changed live and in place. MCT presents users with a single unified user environment that contains all the objects required to perform applicable flight controller tasks, thus users do not have to use multiple applications, the traditional boundaries that exist between multiple heterogeneous applications disappear, leaving open the possibility of new operations concepts that are not constrained by the traditional applications paradigm.

Trimble, Jay Phillip↗