Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “software infrastructure”

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 343 records · Page 19

The Small Aircraft Transportation System (SATS), Higher Volume Operations (HVO) Off-Nominal Operations

The ability to conduct concurrent, multiple aircraft operations in poor weather, at virtually any airport, offers an important opportunity for a significant increase in the rate of flight operations, a major improvement in passenger convenience, and the potential to foster growth of charter operations at small airports. The Small Aircraft Transportation System, (SATS) Higher Volume Operations (HVO) concept is designed to increase traffic flow at any of the 3400 nonradar, non-towered airports in the United States where operations are currently restricted to one-in/one-out procedural separation during Instrument Meteorological Conditions (IMC). The concept's key feature is pilots maintain their own separation from other aircraft using procedures, aircraft flight data sent via air-to-air datalink, cockpit displays, and on-board software. This is done within the Self-Controlled Area (SCA), an area of flight operations established during poor visibility or low ceilings around an airport without Air Traffic Control (ATC) services. The research described in this paper expands the HVO concept to include most off-nominal situations that could be expected to occur in a future SATS environment. The situations were categorized into routine off-nominal operations, procedural deviations, equipment malfunctions, and aircraft emergencies. The combination of normal and off-nominal HVO procedures provides evidence for an operational concept that is safe, requires little ground infrastructure, and enables concurrent flight operations in poor weather.

Baxley, B.↗

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↗

SCOSII: ESA's new generation of mission control systems: The user's perspective

In 1974 ESOC decided to develop a reusable Mission Control System infrastructure for ESA's missions operated under its responsibility. This triggered a long and successful product development line, which started with the Multi Mission Support System (MSSS) which entered in service in 1977 and is still being used today by the MARECS and ECS missions; it was followed in 1989 by a second generation of systems known as SCOS-I, which was/is used by the Hipparcos, ERS-1 and EURECA missions and will continue to support all future ESCO controlled missions until approximately 1995. In the meantime the increasing complexity of future missions together with the emergence of new hardware and software technologies have led ESOC to go for the development of a third generation of control systems, SCOSII, which will support their future missions up to at least the middle of the next decade. The objective of the paper is to present the characteristics of the SCOSII system from the perspective of the mission control team; i.e. it will concentrate on the improvements and advances in the performance, functionality and work efficiency of the system.

Kaufeler, P.↗

LANDO: Developing Autonomous Payload Offloading Capabilities for Lunar Surface Operations

Introduction: The Lightweight Surface Manipulation System (LSMS) AutoNomy capabilities Development for surface Operations and construction (LANDO) project is an Early Career Initiative selected for funding by NASA Space Technology Mission Directorate. LANDO is developing a general-purpose autonomy framework applicable to serial and tension-actuated manipulation agents, that will be validated using an existing prototype of the LSMS-L35 (35-kg wrist lift capacity on the lunar surface [Fig. 1], sized for a Commercial Lunar Pay-load Services (CLPS) mission). The autonomous LSMS-L35 will be used to demonstrate autonomous payload handling capabilities for Lunar and other planetary surfaces, directly addressing STMD capability gaps in autonomous excavation and construction operations, advanced robotics and spacecraft autonomy technologies, and technologies supporting emerging space industries including the In-Space Servicing, Assembly and Manufacturing national strategy. LSMS: The LSMS is a tension actuated robotic agent that is scalable (reach and lifting capacity in different gravity environments), versatile (types of surface operations), and reusable. Compared to serial arms, the LSMS provides significantly higher structural efficiency and mechanical advantage, enabling a greater payload lift capacity at a lower system mass. The LSMS is envisioned to be a crucial part of the excavation and construction portfolio, capable of supporting a variety of activities on the lunar surface. Autonomous payload handling is one of the first activities the LSMS can support that develops capabilities that are extensible to other surface operations. Payload handling is required to: remove payloads from a lander; place payloads on mobile agents for transport from a lander to construction site/assembly point; emplace payloads in their operational configuration, and aggregate components to create an asset. As an example of this critical gap, manifested CLPS missions do not currently have a ubiquitous payload offloading capability; payloads (excluding rovers) are designed to remain on the lander. Why Autonomy? Autonomous robotic systems capable of carrying out excavation and construction operations are a fundamental and critical capability required for realizing the NASA Artemis program vision to “emplace and build the infrastructure, systems, and robotic missions that can enable a sustained lunar surface presence.” While teleoperation is still feasible for lunar surface operations, increased latency at Mars will require validated supervised autonomous technologies capable of operating with minimal human involvement (human-on-the-loop) unless an unexpected event occurs requiring human intervention. Autonomy reduces operator burden, allows operations to continue during uncrewed periods, in-creases the safety of operations by automatically detecting and handling faults, and allows operating in high latency environments. Development Activities: LANDO is extending critical autonomous operations to the manipulation domain and creating an integrated system, based on reusable software modules, that is capable of planning and executing payload handling and autonomous surface operations without requiring hu-man intervention beyond a supervisory role. The priority features under development are 1) autonomously offload payloads from a tilted lander deck without buckling the LSMS; 2) sensing whether a payload is safe to lift and handle; and 3) integrate with Astrobotic’s CLPS lander. The poster presentation will highlight current development activities over the past year on LSMS-L35 prototype hard-ware design, and autonomy software.

in-space assembly↗

NASA Platform for Autonomous Systems (NPAS)

NASA Platform for Autonomous Systems (NPAS) is a disruptive software platform and processes being developed by SSC Autonomous Systems Laboratory (ASL). Autonomous operations are critical for the success, safety and crew survival of NASA deep space missions beyond low Earth orbit, including Lunar Orbital Platform-Gateway, and for the future of cost-effective ground mission operations. NPAS represents the embodiment of an innovative implementation for "thinking" autonomy in contrast to brute-force autonomy. It also uniquely addresses the requirements and integrates five primary functionalities for autonomous operations including: (1) Integrated System Health Management (ISHM), (2) autonomy, guided by health and system concepts of operations; (3) knowledge models of applications; (4) infrastructure to create, schedule, and execute mission plans; and (5) infrastructure to integrate distributed autonomous applications across networks.

Figueroa, Fernando↗

Applied Space Systems Engineering: Manage Technical Data - Chapter 17

Effective space systems engineering (SSE) is conducted in a fully electronic manner. Competitive hardware, software, and system designs are created in a totally digital environment that enables rapid product design and manufacturing cycles, as well as a multitude of techniques such as modeling, simulation, and lean manufacturing that significantly reduce the lifecycle cost of systems. Because the SSE lifecycle depends on the digital environment, managing the enormous volumes of technical data needed to describe, build, deploy, and operate systems is a critical factor in the success of a project. This chapter presents the key aspects of Technical Data Management (TDM) within the SSE process. It is written from the perspective of the System Engineer tasked with establishing the TDM process and infrastructure for a major project. Additional perspectives are reflected from the point of view of the engineers on the project who work within the digital engineering environment established by the TDM toolset and infrastructure, and from the point of view of the contactors who interface via the TDM infrastructure. Table 17.1 lists the TDM process as it relates to SSE.

Kent, Peter↗

Monitoring and analysis of data from complex systems

Some of the methods, systems, and prototypes that have been tested for monitoring and analyzing the data from several spacecraft and vehicles at the Marshall Space Flight Center are introduced. For the Huntsville Operations Support Center (HOSC) infrastructure, the Marshall Integrated Support System (MISS) provides a migration path to the state-of-the-art workstation environment. Its modular design makes it possible to implement the system in stages on multiple platforms without the need for all components to be in place at once. The MISS provides a flexible, user-friendly environment for monitoring and controlling orbital payloads. In addition, new capabilities and technology may be incorporated into MISS with greater ease. The use of information systems technology in advanced prototype phases, as adjuncts to mainline activities, is used to evaluate new computational techniques for monitoring and analysis of complex systems. Much of the software described (specially, HSTORESIS (Hubble Space Telescope Operational Readiness Expert Safemode Investigation System), DRS (Device Reasoning Shell), DART (Design Alternatives Rational Tool), elements of the DRA (Document Retrieval Assistant), and software for the PPS (Peripheral Processing System) and the HSPP (High-Speed Peripheral Processor)) is available with supporting documentation, and may be applicable to other system monitoring and analysis applications.

Dollman, Thomas↗

Web Design for Space Operations: An Overview of the Challenges and New Technologies Used in Developing and Operating Web-Based Applications in Real-Time Operational Support Onboard the International Space Station, in Astronaut Mission Planning and Mission Control Operations

The International Space Station (ISS) Operations Planning Team, Mission Control Centre and Mission Automation Support Network (MAS) have all evolved over the years to use commercial web-based technologies to create a configurable electronic infrastructure to manage the complex network of real-time planning, crew scheduling, resource and activity management as well as onboard document and procedure management required to co-ordinate ISS assembly, daily operations and mission support. While these Web technologies are classified as non-critical in nature, their use is part of an essential backbone of daily operations on the ISS and allows the crew to operate the ISS as a functioning science laboratory. The rapid evolution of the internet from 1998 (when ISS assembly began) to today, along with the nature of continuous manned operations in space, have presented a unique challenge in terms of software engineering and system development. In addition, the use of a wide array of competing internet technologies (including commercial technologies such as .NET and JAVA ) and the special requirements of having to support this network, both nationally among various control centres for International Partners (IPs), as well as onboard the station itself, have created special challenges for the MCC Web Tools Development Team, software engineers and flight controllers, who implement and maintain this system. This paper presents an overview of some of these operational challenges, and the evolving nature of the solutions and the future use of COTS based rich internet technologies in manned space flight operations. In particular this paper will focus on the use of Microsoft.s .NET API to develop Web-Based Operational tools, the use of XML based service oriented architectures (SOA) that needed to be customized to support Mission operations, the maintenance of a Microsoft IIS web server onboard the ISS, The OpsLan, functional-oriented Web Design with AJAX

Khan, Ahmed↗

Rapid Lightweight Firmware Architecture of the Mobile Metamaterial Internal Co-Integrator Robot

The Mobile Metamaterial Internal Co-Integrator (MMIC-I) is a structure assembly and servicing robot for in-space servicing, assembly, and manufacturing of primary structures and infrastructure. MMIC-I is a battery-powered crawling robot that can travel through periodic structures such as trusses and open framework mechanical metamaterials. It does this through sequences of component extension, contraction, and gripping. This paper provides a detailed discussion of MMIC-I’s lightweight and rapidly developed firmware architecture, to enable demonstration of robot locomotion, secondary operations, and communications with a central command source. The rationale for the lightweight rapid development approach is to allow for assessment of long term system requirements in parallel with the mechatronics development, including optimization of system and subsystem power densities, to inform a future choice of flight ready software frameworks. MMIC-I system computing and I/O requirements are much lower than what is provided by proven baseline computing hardware for existing flight ready software frameworks such as the core Flight System, F prime, and the Robot Operating System. Development of earth gravity ground demonstration of the robotic systems is greatly benefited by limited power and mass factors for computing hardware. Here, we implement inter-process communication, commanding, and telemetry with the Espressif ESP32 module running the Arduino OS.

Damiana Catanoso↗

Reference Avionics Architecture for Lunar Surface Systems

Developing and delivering infrastructure capable of supporting long-term manned operations to the lunar surface has been a primary objective of the Constellation Program in the Exploration Systems Mission Directorate. Several concepts have been developed related to development and deployment lunar exploration vehicles and assets that provide critical functionality such as transportation, habitation, and communication, to name a few. Together, these systems perform complex safety-critical functions, largely dependent on avionics for control and behavior of system functions. These functions are implemented using interchangeable, modular avionics designed for lunar transit and lunar surface deployment. Systems are optimized towards reuse and commonality of form and interface and can be configured via software or component integration for special purpose applications. There are two core concepts in the reference avionics architecture described in this report. The first concept uses distributed, smart systems to manage complexity, simplify integration, and facilitate commonality. The second core concept is to employ extensive commonality between elements and subsystems. These two concepts are used in the context of developing reference designs for many lunar surface exploration vehicles and elements. These concepts are repeated constantly as architectural patterns in a conceptual architectural framework. This report describes the use of these architectural patterns in a reference avionics architecture for Lunar surface systems elements.

Somervill, Kevin M.↗

Information architecture for a planetary 'exploration web'

'Web services' is a common way of deploying distributed applications whose software components and data sources may be in different locations, formats, languages, etc. Although such collaboration is not utilized significantly in planetary exploration, we believe there is significant benefit in developing an architecture in which missions could leverage each others capabilities. We believe that an incremental deployment of such an architecture could significantly contribute to the evolution of increasingly capable, efficient, and even autonomous remote exploration.

middleware messaging IT infrastructure web service↗

NASA Platform for Autonomous Systems (NPAS)

NASA Platform for Autonomous Systems (NPAS) is a disruptive software platform and processes being developed by the NASA Stennis Space Center (SSC) Autonomous Systems Laboratory (ASL). Autonomous operations are critical for the success, safety and crew survival of NASA deep space missions beyond low Earth orbit, including the Gateway, and for the future of cost-effective ground mission operations. NPAS represents the embodiment of an innovative paradigm for “thinking” autonomy in contrast to brute-force autonomy. NPAS uniquely addresses the requirements and integrates the primary functionalities for autonomous operations, in one platform that includes: (1) Integrated System Health Management (ISHM); (2) autonomy strategies, guided by system health and concepts of operations; (3) domain objects (system elements) and infrastructure to create complete application domain knowledge models (4) infrastructure to create, schedule, and execute mission plans; (5) infrastructure to develop user interfaces for comprehensive awareness; and (6) infrastructure to integrate distributed autonomous applications across networks. NPAS is a single platform that can be used to make any system operate with any desirable degree of autonomy, as well as provide comprehensive system awareness to operators and users.

Figueroa, Fernando↗

NASA GES DISC Giovanni: Current and Future

Giovanni (Geospatial Interactive Online Visualization and Analysis Infrastructure), developed by the NASA Goddard Earth Sciences Data and Information Services Center (GES DISC), has established a reputation among NASA users for easy access, analysis, and visualization of NASA Earth science data. Currently, Giovanni supports over 1900 variables in eight disciplinary areas. Like any other enterprise application, Giovanni faces big data challenges, such as servicing increasingly large data volumes and more complex data types, while at the same time addressing the demands of a more diverse user community, e.g., placing requests for long-term time series from multiple spatially and temporally dense data records. I will present how Giovanni has been evolving from an on-premises, monolithic software application towards a cloud-enabled implementation to address these challenges.

Analytics↗

Space Transformation -- Localizing the Remote and Connecting the Isolated

In motivating the Space Transformation theme for this year’s 4S symposium, the organizers provided the following context, “Transformation of economies are driven by a change in values and accelerated by new technologies.” These words rang particularly true when I read them at the beginning of the holiday season. Like so many others, I was in the early phases of my Christmas shopping procrastination campaign, and I’d just been reflecting on how Amazon Prime was the transformational tool I’d been waiting for. Basic limiting principles of time and space, supply and demand, were all but erased by the Amazon Prime phenomenon. Coupled with emerging 3D printing and other adaptive manufacturing technologies, a transformation from deliberate planning to “think it … have it” had occurred, empowering me to procrastinate longer than I’d ever dreamed possible. The organizers went on to ponder, “Will space transformation also affect society?”, just as our team at the Air Force Research Lab’s (AFRL) Center for Rapid Innovation (CRI) were working alongside partners within our larger Integrated Capabilities Directorate, NASA’s Flight Opportunities and Small Spacecraft Technology programs, and DARPA’s Luna-10 program to develop technologies and execute demonstration missions that leverage the space domain to genuinely connect even the most remote and austere domains on the timeline of need. Picking apart the miracle that is Amazon prime, where does the model fail, and why? More relevantly to the theme of this year’s symposium, how can the space domain be used to overcome its limitations and minimize its weaknesses? Perhaps it is best assessed in the context of Use Cases. What are the Amazon delivery cost, schedule, and cargo limiters to the Amundsen-Scott South Pole Research Station, or the Lunar South Pole Research Station? This paper will explore enabling infrastructure that allows Amazon prime to thrive and assess the transformational enabling technologies that would be necessary to extend that miracle to the truly remote or the truly austere. Localizing the Remote • First, it will evaluate the ability of the on-going AFRL Rocket Cargo and Space Initiatives Ringside Seats systems, coupled with Astrobotic’s Xodiak and Xogdor capabilities, developed to support the NASA Flight Opportunities Program (FOP), to supply orbital/suborbital delivery to both improved and austere sites on the Earth and Moon. • Then, it will add the surface terminal distribution leg, with an examination of Lunar Outpost’s Mobile Autonomous Prospecting Platform (MAPP), equipped with Mobile Autonomous Robotic Swarm (MARS) software, and Intuitive Machine’s Hopper, developed with support of AFRL and NASA’s Commercial Lunar Payload Services (CLPS) program. Connecting the Isolated From there, it will focus on the destination, asking what implied destination services are required to support highly assured autonomous delivery. • Specifically, it will highlight Astrobotic’s Skymage mesh-networked publish and subscribe communication and navigation service, as well as AFRL’s on-going developments of radioisotope and reactor nuclear-sourced thermoelectric power generation and distribution systems under development under the Joint Emergent Technology Supplying On-orbit Nuclear Power (JETSON) program by Lockheed Martin, Westinghouse, Intuitive Machines, and Zeno Power, to provide the power service to locations well off the grid. • Finally, the paper will connect to the “human machine”. What connects the remote or in-situ human consumer to the remote domain? What connects the diverse international government and commercial services to each other? The former will focus on AFRL’s OraCloud feeding their Space Defense Control and Characterization System (SDCCS) and Lunar Station’s MoonHacker systems, while the latter will focus on the BlueHalo/Tensor LunX Technology Platform for the Cislunar Commodity Marketplace. In 1984, Krafft Ehricke famously remarked that, “If God wanted man to become a spacefaring species, He would have given man a Moon.” This paper is not about the Moon, but is about humans as a spacefaring species, shedding the pesky land/air limitations of the Amazon Prime model … so that we can all live a procrastinator’s “think it … have it” existence.

Charles Finley↗

Names Don't Fly: Smart Filters for Profanity Detection and Classification in User-Generated Content

Generally, names associate with a person’s identity. But what if in the pretext of a legitimate name and given the opportunity, users of software provide names to online web forms that carry along offensive language, slurs, and other profanity that is then sent to Mars ? The answer is simple: they don’t fly. In this paper,we perform model explorations to detect and classify inappropriate content in the names submitted from people across the world to ‘Send Your Names to MARS’ public engagement campaign.We propose a novel pipeline approach, that can effectively overcome the issues of lack of negative samples, noisy labels by gathering expert knowledge over time with human(s) in the loop and data augmentation, and achieve high accuracy in classifying inappropriate names with very little or no context. We describe cloud-based infrastructure to deploy our application and run predictions on large-scale data through our pipeline and achieve significant speedup over offline processes, with enhanced reliability and security.

Soderstrom, Tomas↗

NASA Tech Briefs, February 2006

Topics discussed include: Nearly Direct Measurement of Relative Permittivity; DCS-Neural-Network Program for Aircraft Control and Testing; Dielectric Heaters for Testing Spacecraft Nuclear Reactors; Using Doppler Shifts of GPS Signals To Measure Angular Speed; Monitoring Temperatures of Tires Using Luminescent Materials; Highly Efficient Multilayer Thermoelectric Devices; Very High-Speed Digital Video Capability for In-Flight Use; MMIC DHBT Common-Base Amplifier for 172 GHz; Modular, Microprocessor-Controlled Flash Lighting System; Generic Environment for Simulating Launch Operations; Modular Aero-Propulsion System Simulation; X-Windows Socket Widget Class; Infrastructure for Rapid Development of Java GUI Programs; Processing Raman Spectra of High-Pressure Hydrogen Flames; X-Windows Information Sharing Protocol Widget Class; Simulating Humans as Integral Parts of Spacecraft Missions; Analyzing Power Supply and Demand on the ISS; Polyimides From a-BPDA and Aromatic Diamines; Making Plant-Support Structures From Waste Plant Fiber; Large Deployable Reflectarray Antenna; Periodically Discharging, Gas-Coalescing Filter; Ion Milling On Steps for Fabrication of Nanowires; Neuro-Prosthetic Implants With Adjustable Electrode Arrays; Microfluidic Devices for Studying Biomolecular Interactions; Studying Functions of All Yeast Genes Simultaneously; Polarization Phase-Compensating Coats for Metallic Mirrors; Tunable-Bandwidth Filter System; Methodology for Designing Fault-Protection Software; and Ground-Based Localization of Mars Rovers.

Source record↗

Defining Medical Levels of Care for Exploration Missions

NASA medical care standards establish requirements for providing health and medical programs for crewmembers during all phases of a mission. These requirements are intended to prevent or mitigate negative health consequences of long-duration spaceflight, thereby optimizing crew health and performance over the course of the mission. Current standards are documented in the two volumes of the NASA-STD-3001 Space Flight Human-System Standard document, established by the Office of the Chief Health and Medical Officer. Its purpose is to provide uniform technical standards for the design, selection, and application of medical hardware, software, processes, procedures, practices, and methods for human-rated systems. NASA-STD-3001 Vol. 1 identifies five levels of care for human spaceflight. These levels of care are accompanied by several components that illustrate the type of medical care expected for each. The Exploration Medical Capability (ExMC) of the Human Research Program has expanded the context of these provided levels of care and components. This supplemental information includes definitions for each component of care and example actions that describe the type of capabilities that coincide with the definition. This interpretation is necessary in order to fully and systematically define the capabilities required for each level of care in order to define the medical requirements and plan for infrastructure needed for medical systems of future exploration missions, such as one to Mars.

Hailey, M.↗

An expert system for simulating electric loads aboard Space Station Freedom

Space Station Freedom will provide an infrastructure for space experimentation. This environment will feature regulated access to any resources required by an experiment. Automated systems are being developed to manage the electric power so that researchers can have the flexibility to modify their experiment plan for contingencies or for new opportunities. To define these flexible power management characteristics for Space Station Freedom, a simulation is required that captures the dynamic nature of space experimentation; namely, an investigator is allowed to restructure his experiment and to modify its execution. This changes the energy demands for the investigator's range of options. An expert system competent in the domain of cryogenic fluid management experimentation was developed. It will be used to help design and test automated power scheduling software for Freedom's electric power system. The expert system allows experiment planning and experiment simulation. The former evaluates experimental alternatives and offers advice on the details of the experiment's design. The latter provides a real-time simulation of the experiment replete with appropriate resource consumption.

Kukich, George↗