Search NASA⌕ Search

SEARCH · Search NASA

Results for “collaborative systems”

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 253 records · Page 14

Roles for Agent Assistants in Field Science: Understanding Personal Projects and Collaboration

A human-centered approach to computer systems design involves reframing analysis in terms of the people interacting with each other. The primary concern is not how people can interact with computers, but how shall we design work systems (facilities, tools, roles, and procedures) to help people pursue their personal projects, as they work independently and collaboratively? Two case studies provide empirical requirements. First, an analysis of astronaut interactions with CapCom on Earth during one traverse of Apollo 17 shows what kind of information was conveyed and what might be automated today. A variety of agent and robotic technologies are proposed that deal with recurrent problems in communication and coordination during the analyzed traverse. Second, an analysis of biologists and a geologist working at Haughton Crater in the High Canadian Arctic reveals how work interactions between people involve independent personal projects, sensitively coordinated for mutual benefit. In both cases, an agent or robotic system's role would be to assist people, rather than collaborating, because today's computer systems lack the identity and purpose that consciousness provides.

Clancey, William J.↗

How Discipline-Oriented DAACs Collaborate to Support Interdisciplinary Earth Science

The Earth system is made of multiple complex subsystems. While scientists tend to specialize in single subsystems or even portions of a subsystem, to fully understand the physical, chemical and biological processes occurring on the Earth, we must understand how these systems interact. Thus, scientists need to be able to expand beyond their chosen field and collaborate across disciplines. The NASA Earth Observing System Data and Information System (EOSDIS) is focusing on new capabilities to make interdisciplinary science easier. The EOSDIS DAACS are responsible for archiving and distributing NASA’s rapidly growing collection of satellite, airborne and field data. Like the scientists they serve, the DAACs are discipline oriented. This has many advantages. Scientists are able to interact with experts on data in their domain and receive data appropriate for their research. However, discipline-oriented services may be confusing to cross-disciplinary users who may not know how to get started. Fortunately, collaboration across scientific communities is a specialty of the DAACs who support interdisciplinary users with a collaborative culture and technology that empowers the open sharing of data, information, and knowledge within the scientific community and the wider public to accelerate scientific research and understanding. This presentation will discuss the capabilities of a discipline-oriented approach to support future Earth science goals including those of Open Science and cross-disciplinary collaboration.

Sara Lubkin↗

Solar System Exploration Technology Requirements and Planning Process

The NASA Office of Space Science, in alliance with the Office of Advanced Concepts and Technology, has developed an Integrated Technology Strategy to guide its investment in technology for space science missions. This strategy establishes goals and strategic objectives that ensure that NASA and the nation derive the greatest possible scientific and economic benefits from investments in space science missions and technologies. Within the Office of Space Science, the Solar System Exploration Division in collaboration with the Office of Space Access and Technology, is developing a Technology Plan to implement these goals and to identify specific goals and to identify specific technology needs for solar system missions. This paper describes the philosophy, processes, and preliminary results of the systematic process being established for the identification and prioritization of solar system exploration technology needs.

space↗

A Contrast in Use of Metrics in Earth Science Data Systems

In recent years there has been a surge in the number of systems for processing, archiving and distributing remotely sensed data. Such systems, working independently as well as in collaboration, have been contributing greatly to the advances in the scientific understanding of the Earth system, as well as utilization of the data for nationally and internationally important applications. Among such systems, we consider those that are developed by or under the sponsorship of NASA to fulfill one of its strategic objectives: "Study Earth from space to advance scientific understanding and meet societal needs." NASA's Earth science data systems are of varying size and complexity depending on the requirements they are intended to meet. Some data systems are regarded as NASA's "Core Capabilities" that provide the basic infrastructure for processing, archiving and distributing a set of data products to a large and diverse user community in a robust and reliable manner. Other data systems constitute "Community Capabilities". These provide specialized and innovative services to data users and/or research products offering new scientific insight. Such data systems are generally supported by NASA through peer reviewed competition. Examples of Core Capabilities are 1. Earth Observing Data and Information System (EOSDIS) with its Distributed Active Archive Centers (DAACs), Science Investigator-led Processing Systems (SIPSs), and the EOS Clearing House (ECHO); 2. Tropical Rainfall Measurement Mission (TRMM) Science Data and Information System (TSDIS); 3. Ocean Data Processing System (ODPS); and 4. CloudSat Data Processing Center. Examples of Community Capabilities are projects under the Research, Education and Applications Solutions Network (REASON), and Advancing Collaborative Connections for Earth System Science (ACCESS) Programs. In managing these data system capabilities, it is necessary to have well-established goals and to measure progress relative to them. Progress is measured through "metrics", which can be a combination of quantitative as well as qualitative assessments. The specific metrics of interest depend on the user of the metrics as well as the type of data system. The users of metrics can be data system managers, program managers, funding agency or the public. Data system managers need metrics for assessing and improving the performance of the system and for future planning. Program managers need metrics to assess progress and the value of the data systems sponsored by them. Also, there is a difference in the metrics needed for core capabilities that tend to be more complex, larger and longer-term compared to community capabilities and the community capabilities that tend to be simpler, smaller and shorter-term. Even among community capabilities there are differences; hence the same set of metrics does not apply to all. Some provide data products to users, some provide services that enable better utilization of data or interoperability among other systems, and some are a part of a larger project where provision of data or services is only a minor activity. There is also a contrast between metrics used for internal and external purposes. Examples of internal purposes are: ensuring that the system meets its requirements, and planning for evolution and growth. Examples of external purposes are: providing to sponsors indicators of success of the systems, demonstrating the contributions of the system to overall program success, etc. This paper will consider EOSDIS, REASON and ACCESS programs to show the various types of metrics needed and how they need to be tailored to the types of data systems while maintaining the overall management goals of measuring progress and contributions made by the data systems.

Ramapriyan, Hampapuram↗

A Collaborative Decision Environment for UAV Operations

NASA is developing Intelligent Mission Management (IMM) technology for science missions employing long endurance unmanned aerial vehicles (UAV's). The IMM groundbased component is the Collaborative Decision Environment (CDE), a ground system that provides the Mission/Science team with situational awareness, collaboration, and decisionmaking tools. The CDE is used for pre-flight planning, mission monitoring, and visualization of acquired data. It integrates external data products used for planning and executing a mission, such as weather, satellite data products, and topographic maps by leveraging established and emerging Open Geospatial Consortium (OGC) standards to acquire external data products via the Internet, and an industry standard geographic information system (GIs) toolkit for visualization As a Science/Mission team may be geographically dispersed, the CDE is capable of providing access to remote users across wide area networks using Web Services technology. A prototype CDE is being developed for an instrument checkout flight on a manned aircraft in the fall of 2005, in preparation for a full deployment in support of the US Forest Service and NASA Ames Western States Fire Mission in 2006.

D'Ortenzio, Matthew V.↗

Streamlining Collaborative Planning in Spacecraft Mission Architectures

During the past two decades, the planning and scheduling community has substantially increased the capability and efficiency of individual planning and scheduling systems. Relatively recently, research work to streamline collaboration between planning systems is gaining attention. Spacecraft missions stand to benefit substantially from this work as they require the coordination of multiple planning organizations and planning systems. Up to the present time this coordination has demanded a great deal of human intervention and/or extensive custom software development efforts. This problem will become acute with increased requirements for cross-mission plan coordination and multi -spacecraft mission planning. The Advanced Architectures and Automation Branch of NASA's Goddard Space Flight Center is taking innovative steps to define collaborative planning architectures, and to identify coordinated planning tools for Cross-Mission Campaigns. Prototypes are being developed to validate these architectures and assess the usefulness of the coordination tools by the planning community. This presentation will focus on one such planning coordination too], named Visual Observation Layout Tool (VOLT), which is currently being developed to streamline the coordination between astronomical missions

Misra, Dhariti↗

MODIS-HIRIS ground data systems commonality report

The High Resolution Imaging Spectrometer (HIRIS) and Moderate Resolution Imaging Spectrometer (MODIS) Data Systems Working Group was formed in September 1988 with representatives of the MODIS Data System Study Group and the HIRIS Project Data System Design Group to collaborate in the development of requirements on the EosDIS necessary to meet the science objectives of the two facility instruments. A major objective was to identify and promote commonality between the HIRIS and MODIS data systems, especially from the science users' point of view. A goal was to provide a base set of joint requirements and specifications which could easily be expanded to a Phase-B representation of the needs of the science users of all EOS instruments. This document describes the points of commonality and difference between the Level-II Requirements, Operations Concepts, and Systems Specifications for the ground data systems for the MODIS and HIRIS instruments at their present state of development.

Han, D.↗

NASA's Advanced Information Systems Technology (AIST): Combining New Observing Strategies and Analytics Frameworks to Build Earth System Digital Twins

NASA's Advanced Information Systems Technology (AIST) Program is one of several Technology programs managed by the Earth Science Technology Office (ESTO) in the Earth Science Division (ESD). The AIST Program focuses on advanced information systems and novel computer science technologies that will be needed by NASA Earth Science in the next 5 to 10 years. The three main thrusts of the AIST Program deal with New Observing Strategies, Analytic Collaborative Frameworks and Earth System Digital Twins. This paper describes these three thrusts and how they work together to create future Earth Science information systems.

Jacqueline Le Moigne↗

Nasa's Advanced Information Systems Technology (AIST): Combining New Observing Strategies And Analytics Frameworks To Build Earth System

NASA's Advanced Information Systems Technology (AIST) Program is one of several Technology programs managed by the Earth Science Technology Office (ESTO) in the Earth Science Division (ESD). The AIST Program focuses on advanced information systems and novel computer science technologies that will be needed by NASA Earth Science in the next 5 to 10 years. The three main thrusts of the AIST Program deal with New Observing Strategies, Analytic Collaborative Frameworks and Earth System Digital Twins. This paper describes these three thrusts and how they work together to create future Earth Science information systems.

Jacqueline Le Moigne↗

A Collaborative Analysis Tool for Integrating Hypersonic Aerodynamics, Thermal Protection Systems, and RBCC Engine Performance for Single Stage to Orbit Vehicles

Presented is a computer-based tool that connects several disciplines that are needed in the complex and integrated design of high performance reusable single stage to orbit (SSTO) vehicles. Every system is linked to every other system, as is the case of SSTO vehicles with air breathing propulsion, which is currently being studied by NASA. The deficiencies in the scramjet powered concept led to a revival of interest in Rocket-Based Combined-Cycle (RBCC) propulsion systems. An RBCC propulsion system integrates airbreathing and rocket propulsion into a single engine assembly enclosed within a cowl or duct. A typical RBCC propulsion system operates as a ducted rocket up to approximately Mach 3. At this point the transitions to a ramjet mode for supersonic-to-hypersonic acceleration. Around Mach 8 the engine transitions to a scram4jet mode. During the ramjet and scramjet modes, the integral rockets operate as fuel injectors. Around Mach 10-12 (the actual value depends on vehicle and mission requirements), the inlet is physically closed and the engine transitions to an integral rocket mode for orbit insertion. A common feature of RBCC propelled vehicles is the high degree of integration between the propulsion system and airframe. At high speeds the vehicle forebody is fundamentally part of the engine inlet, providing a compression surface for air flowing into the engine. The compressed air is mixed with fuel and burned. The combusted mixture must be expanded to an area larger than the incoming stream to provide thrust. Since a conventional nozzle would be too large, the entire lower after body of the vehicle is used as an expansion surface. Because of the high external temperatures seen during atmospheric flight, the design of an airbreathing SSTO vehicle requires delicate tradeoffs between engine design, vehicle shape, and thermal protection system (TPS) sizing in order to produce an optimum system in terms of weight (and cost) and maximum performance.

Stanley, Thomas Troy↗

A Model Based Systems Engineering Approach Towards Developing a Rapid Analysis and Trades Environment

In this work, an integrated and end-to-end modeling environment was developed to assess the system-level impacts of evolving requirements and design parameters. Researchers at the Georgia Institute of Technology's Aerospace Systems Design Laboratory (ASDL) collaborated with JPL engineers to develop, implement, and test a modeling environment to assess design changes to a notional Europa Mission called the Jupiter Europa Buzzer (JEB). This environment was developed using a Model-Based Systems Engineering (MBSE) approach and consists of three major components: the Systems Model, the Mission Simulator, and the Web Based Interactive Dashboard. In summary, utilizing this environment in a representative notional end-to-end scenario, performance margins were calculated in hours while maintaining consistent analytical, hardware, and operational assumptions.

Model Based System Engineering↗

Project-domain Science Traceability and Alignment Framework (P-STAF): Analysis of a Payload Architecture

Large science-focused space missions often have multiple instruments working together to address broad science goals. Systems engineers on these types of projects must work with the project scientists to evaluate trades and make decisions that result in a system that efficiently serves the mission science goals. This collaboration is more effective if the systems engineers understand both the traceability from the L1 customer requirements to the selected instruments and the contributions of each instrument in the context of the whole payload suite. These relationships might be understood implicitly by the science team on a project, but there is value in formally codifying them so this understanding can be accessed and formally analyzed by a broader systems engineering effort. We first described a framework for this communication, called the Project-domain Science Traceability and Alignment Framework (P-STAF), in the IEEE 2017 paper “A Framework for Extending the Science Traceability Matrix: Application to the Planned Europa Mission.” This paper shows how that basic framework can be leveraged to not only formally capture these relationships between the instruments and the customer needs, but also how that information can be codified in an analyzable graph that can be queried to provide a better understanding of mission risks and scope. This work was drawn from the application of P-STAF to the Europa Clipper mission, but generic example networks are used to illustrate the power of this technique.

Reinholtz, Kirk↗

A Model-Based Systems Engineering Evaluation of the Evolution to an In-Time Aviation Safety Management System

In 2018, as result of a recommendation from the National Academies, NASA began to prototype an In-Time Aviation Safety Management System (IASMS). The purpose of the IASMS is to enable innovative aviation operations and greater heterogeneity of the overall National Airspace (NAS) by automating much of the safety monitoring, assessment, and risk and hazard mitigation function present in today’s Safety Management Systems (SMS). NASA has worked together with early industry collaborators to understand how such a system might work and has published several early Concepts of Operation (ConOps) and other technical memoranda that illustrate the primary considerations for selected aviation domains. The shift from an SMS to an IASMS is predicated on several assumptions, including: 1.) automating safety functions will decrease the amount of time necessary for risk and hazard identification and analysis, making it more likely that safety concerns are understood ‘in-time’ to mitigate them, and 2.) an IASMS will allow easier tailoring of safety management processes to the particular risks and hazards inherent to that aviation operation. In this paper, we begin to validate these assumptions through the use of Model-Based Systems Engineering (MBSE).

IASMS↗

A Model-Based Systems Engineering Evaluation of the Evolution to an In-Time Aviation Safety Management System

In 2018, as result of a recommendation from the National Academies, NASA began to prototype an In-Time Aviation Safety Management System(IASMS). The purpose of the IASMS is to enable innovative aviation operations and greater heterogeneity of the overall National Airspace (NAS) by automating much of the safety monitoring, assessment, and risk and hazard mitigation functionspresent in today’s Safety Management Systems (SMS). NASA has worked together with early industry collaborators to understand how such a system might work and has published several early Concepts of Operation (ConOps) and other technical memoranda that illustrate the primary considerations for selected aviation domains. The shift from an SMS to an IASMS is predicated on several assumptions, including: 1.) automating safety functions will decrease the amount of time necessary for risk and hazard identification and analysis, making it more likely that safety concerns are understood ‘in-time’ to mitigate them, and 2.) an IASMS will allow easier tailoring of safety management processes to the particular risks and hazards inherent to that aviation operation. In this paper, we begin to validate these assumptions through the use of Model-Based Systems Engineering (MBSE).

In-time Aviation Safety Management System↗

Integrated Demand Management: Minimizing Unanticipated Excessive Departure Delay while Ensuring Fairness from a Traffic Management Initiative

This paper introduces NASA's Integrated Demand Management (IDM) concept and presents the results from an early proof-of-concept evaluation and an exploratory experiment. An initial development of the concept was focused on integrating two systems - i.e. the FAA's newly deployed Traffic Flow Management System (TFMS) tool called the Collaborative Trajectory Options Program (CTOP) and the Time-Based Flow Management (TBFM) system with Extended Metering (XM) capabilities to manage projected heavy traffic demand into a capacity-constrained airport. A human-in-the-loop (HITL) simulation experiment was conducted to demonstrate the feasibility of the initial development of the concept by adapting it to an arrival traffic problem at Newark Liberty International Airport (EWR) during clear weather conditions. In this study, the CTOP was utilized to strategically plan the arrival traffic demand by controlling take-off times of both short- and long-haul flights (long-hauls specify aircraft outside TBFM regions and short-hauls specify aircraft within TBFM regions) in a way that results in equitable delays among the groups. Such strategic planning allows less airborne delay to occur within TBFM by feeding manageable long-haul traffic demand while reserving sufficient slots in the overhead streams for the short-haul departures. The manageable traffic demand indicates the TBFM scheduler assigns no more airborne delay than its assigned airspace is capable of absorbing. TBFM then uses its time-based metering capabilities to deliver the desirable throughput by tactically rescheduling the TBFM entered long-haul flights and short-haul departures. Additional research was also performed to explore use of Required Time of Arrival (RTA) capabilities as a potential control mechanism for the airborne flights to improve arrival traffic delivery accuracy of scheduled long-haul traffic demand. The study results show that both short- and long-haul flights received similar ground delays. In addition, there was a noticeable reduction in the total amount of excessive unanticipated last-minute ground delays, i.e. delays that are frequently imposed on the short-haul flight in current day operations due to saturation in the overhead stream, commonly referred to as 'double penalty'. Furthermore, the concept achieved the target throughput while minimizing the expected cost associated with overall delays in arrival traffic. Assessment of the RTA capabilities showed that there was indeed improvement of the scheduled entry times into TBFM regions by using RTA capabilities. However, with respect to reduction in delays incurred within TBFM, there was no observable benefit of improving the precision of long-haul flights entry times.

Collaborative Trajectory Options Program (CTOP)↗

Portable Laser Guided Robotic Metrology (PLGRM) System

This paper introduces the new Portable Laser Guided Robotic Metrology (PLGRM) system at the National Aeronautics and Space Administration's (NASA) Glenn Research Center. Previous work used industrial robots in fixed facilities to characterize antennas and required fixtures that do not lend themselves to portable applications. NASA's PLGRM system is designed for in-situ antenna measurements at a remote site.The system consists of a collaborative robot arm mounted on a vertical lift and a laser tracker, each on a mobile base. Together,they enable scanning a surface larger than the robot's reach.To accomplish this, the robot first collects all points within its reach, then the system is moved and the laser tracker is used to relocate the robot before additional points are captured. The PLGRM implementation will be discussed including how safety and planning are combined to effectively characterize antennas.Software defined triggering is a feature, for flexible integration of vector network analyzers and antenna controllers. Lastly, data will be shown to demonstrate system functionality and accuracy.

Slater, Peter A.↗