SEARCH · Engineering Papers

Results for “operator support”

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 289 records · Page 16

All sources NASA NTRS DOE OSTI

NASA NTRS1987

Contingency support using adaptive telemetry extractor and expert system technologies

The 'telemetry analysis logic for operations support' prototype system constitutes an expert system that is charged with contingency planning for the NASA Hubble Space Telescope (HST); this system has demonstrated the feasibility of using an adaptive telemetry extractor/reformatter that is integrated with an expert system. A test case generated by a simulator has demonstrated the reduction of the time required for analysis of a complex series of failures to a few minutes, from the hour usually required. The HST's telemetry extractor will be able to read real-time engineering telemetry streams and disk-based data. Telemetry format changes will be handled almost instantaneously.

Bryant, Thomas↗

NASA NTRS2016

Unmanned Aircraft Systems Traffic Management (UTM) Safely Enabling UAS Operations in Low-Altitude Airspace

Unmanned Aircraft System (UAS) Traffic Management (UTM) Enabling Civilian Low-Altitude Airspace and Unmanned Aircraft System Operations What is the problem? Many beneficial civilian applications of UAS have been proposed, from goods delivery and infrastructure surveillance, to search and rescue, and agricultural monitoring. Currently, there is no established infrastructure to enable and safely manage the widespread use of low-altitude airspace and UAS operations, regardless of the type of UAS. A UAS traffic management (UTM) system for low-altitude airspace may be needed, perhaps leveraging concepts from the system of roads, lanes, stop signs, rules and lights that govern vehicles on the ground today, whether the vehicles are driven by humans or are automated. What system technologies is NASA exploring? Building on its legacy of work in air traffic management for crewed aircraft, NASA is researching prototype technologies for a UAS Traffic Management (UTM) system that could develop airspace integration requirements for enabling safe, efficient low-altitude operations. While incorporating lessons learned from the today's well-established air traffic management system, which was a response that grew out of a mid-air collision over the Grand Canyon in the early days of commercial aviation, the UTM system would enable safe and efficient low-altitude airspace operations by providing services such as airspace design, corridors, dynamic geofencing, severe weather and wind avoidance, congestion management, terrain avoidance, route planning and re-routing, separation management, sequencing and spacing, and contingency management. One of the attributes of the UTM system is that it would not require human operators to monitor every vehicle continuously. The system could provide to human managers the data to make strategic decisions related to initiation, continuation, and termination of airspace operations. This approach would ensure that only authenticated UAS could operate in the airspace. In its most mature form, the UTM system could be developed using autonomicity characteristics that include self-configuration, self-optimization and self-protection. The self-configuration aspect could determine whether the operations should continue given the current andor predicted windweather conditions. NASA envisions concepts for two types of possible UTM systems. The first type would be a Portable UTM system, which would move from between geographical areas and support operations such as precision agriculture and disaster relief. The second type of system would be a Persistent UTM system, which would support low-altitude operations and provide continuous coverage for a geographical area. Either system would require persistent communication, navigation, and surveillance (CNS) coverage to track, ensure, and monitor conformance. What is NASA doing to test the technologies? NASA's near-term goal is the development and demonstration of a possible future UTM system that could safely enable low-altitude airspace and UAS operations. Working alongside many committed government, industry and academic partners, NASA is leading the research, development and testing that is taking place in a series of activities called Technology Capability Levels (TCL), each increasing in complexity. UTM TCL1 concluded field testing in August 2015 and is undergoing additional testing at an FAA site.

UTM Low-altitude↗

NASA NTRS1985

Streamlining: Reducing costs and increasing STS operations effectiveness

The development of streamlining as a concept, its inclusion in the space transportation system engineering and operations support (STSEOS) contract, and how it serves as an incentive to management and technical support personnel is discussed. The mechanics of encouraging and processing streamlining suggestions, reviews, feedback to submitters, recognition, and how individual employee performance evaluations are used to motivation are discussed. Several items that were implemented are mentioned. Information reported and the methodology of determining estimated dollar savings are outlined. The overall effect of this activity on the ability of the McDonnell Douglas flight preparation and mission operations team to support a rapidly increasing flight rate without a proportional increase in cost is illustrated.

Petersburg, R. K.↗

NASA NTRS2021

Concept of Operations for OSIRIS-REx Optical Navigation Image Planning

Optical navigation (OpNav) is a critical subsystem of the OSIRIS-REx asteroid sample return mission, which operated in the vicinity of near-Earth asteroid (101955) Bennu from August 2018 through April 2021. A substantial amount of mission resources across multiple subsystems and institutions is required to ensure that the OpNav data are successfully acquired. The KinetX OpNav team, part of the Flight Dynamics System (FDS), is responsible for performing required analysis to develop the OpNav operations plans; requesting, reviewing and verifying the plans; and ultimately using the image data for critical navigation operations. The FDS team, responsible for the mission navigation, is operated by KinetX Aerospace with management and operations support from NASA’s Goddard Space Flight Center. The Science Processing and Operations Center (SPOC), located at the University of Arizona’s Lunar and Planetary Laboratory, is responsible for generating the planning products for all science and most OpNav data. These plans are integrated into the spacecraft sequences, tested, and commanded by the Mission Support Area (MSA) at Lockheed Martin Space. To ensure mission-critical navigation image data are successfully acquired, the plan is developed through a waterfall of planning cycles over the course of 3 months prior to onboard plan execution. During the initial strategic planning for a mission phase, detailed analysis is performed by the OpNav team to conceptualize the concept of operations (ConOps) for image data collection. This phase OpNav Narrative is included along with other strategic planning documents for the key ground segment stakeholders to review and provide feedback. The detailed OpNav plans get defined in the tactical planning cycle, which spans 8 to 3 weeks before the week-long integrated sequence is executed on-board the spacecraft. During the tactical cycle, the initial OpNav Request is submitted along with the science requests, kicking off development of the science and OpNav plans. Once the initial plan is drafted, interfaces are exercised so that the plan can be reviewed and iterated, if necessary. A rigorous schedule is followed by the planning teams during the implementation cycle, spanning the last 18 days before uplink, to ensure all the necessary integration, testing, and reviewing can occur on time. The development of the OpNav planning ConOps, including responsibilities, interfaces, timelines, and procedures, took extensive collaboration across mission elements and institutions. The process was robust throughout the 137 weeks of continuous Optical Navigation Operations at Bennu, which concluded on April 9th, 2021.

Coralie D. Adam↗

NASA NTRS1975

Large Space Telescope Mission analysis

The total mission scenario from Shuttle/LST (Large Space Telescope) integration to ground return is described. The LST is to contain near-diffraction-limited, 2.4-m optics and a variety of instruments that will allow it to make observations from the ultraviolet to the infrared regions. Particular attention is given to the most important aspect of the LST development planning, which consists in the design for change in both configuration and operation. The discussion covers mission objectives, planning for scientific observation, and support operations. The inherent characteristics of the periodic Space Shuttle revisits and earth return capability provide the LST with a capability for growth that should be incorporated into every phase of its development.

Friedlaender, F. M.↗

NASA NTRS2014

Behavioral Health and Performance at NASA JSC: Recent Successes and Future Plan for BHP Research and Operations

The Behavioral Health and Performance discipline at NASA Johnson Space Center is organized into two distinct Divisions (Biomedical Research and Environmental Science Division and Space and Clinical Operations Division) but is integrated and interrelated in its day‐to‐day work. Ongoing operations supporting NASA's spaceflight goals benefit from the research portfolios that address risks to mission success. Similarly, these research portfolios are informed by operations to ensure investigations stay relevant given the dynamic environment of spaceflight. There are many success stories that can be presented where initial work begun as a BHP Research project, and funded through the Human Research Program, was fully implemented in operations or addressed an operational need. Examples include improving effectiveness of the debriefings used within Mission Control by the Mission Operations Directorate and countermeasures for fatigue management. There is also ongoing collaboration with research and operations for developing selection methods for future generation astronauts, and to enhance and inform the current family support function. The objective of this panel is to provide examples of recent success stories, describe areas where close collaboration is benefitting ongoing research and operations, and summarize how this will come together as NASA plans for the one year ISS mission - a unique opportunity for both BHP operations and research to learn more about preparing and supporting crewmembers for extended missions in space. The proposed panel will be comprised of six presentations, each describing a unique aspect of research or operations and the benefits to current and future spaceflight.

Leveton, L. B.↗

NASA NTRS2018

Innovative Development of a Cross-Center Timeline Planning Tool

The Payload Operations Integration Center (POIC) at Marshall Space Flight Center (MSFC) is the United States focal point to support operations controllers and payload developers conducting payload science operations for the National Aeronautics and Space Administration (NASA) aboard the International Space Station (ISS). Some of the key functions are planning, coordination and scheduling of science activities. This effort occurs in coordination with other NASA centers, international partners, and payload developers. The ability to efficiently plan and re-plan in response to change is critical to the flight planning teams. Additionally, in Fall 2017, NASA will increase its ability to perform payload science operations aboard the ISS with a fourth crew member. In order to support this, there will be an increasing need to quickly plan and schedule more activities. In the past, it was cumbersome and time-consuming to consolidate copious amounts of planning and change request data from various sources. Planners would summarize information from the Johnson Space Center (JSC) Operations Planning Timeline Integration System (OPTIMIS) and manually integrate it with other data in order to produce a Timeline Planning Summary (TPS). This lengthy process of updating static documents while planning and re-planning was cumbersome, introduced human error, and was inflexible to last minute changes. There was a need for a dynamic, more efficient, less erroneous, and more concise way of building a report that could be readily updated as fast as payload science plans change.

Pedoto, Ramon W.↗

NASA NTRS2013

Tethered Satellites as an Enabling Platform for Operational Space Weather Monitoring Systems

Tethered satellites offer the potential to be an important enabling technology to support operational space weather monitoring systems. Space weather "nowcasting" and forecasting models rely on assimilation of near-real-time (NRT) space environment data to provide warnings for storm events and deleterious effects on the global societal infrastructure. Typically, these models are initialized by a climatological model to provide "most probable distributions" of environmental parameters as a function of time and space. The process of NRT data assimilation gently pulls the climate model closer toward the observed state (e.g., via Kalman smoothing) for nowcasting, and forecasting is achieved through a set of iterative semi-empirical physics-based forward-prediction calculations. Many challenges are associated with the development of an operational system, from the top-level architecture (e.g., the required space weather observatories to meet the spatial and temporal requirements of these models) down to the individual instruments capable of making the NRT measurements. This study focuses on the latter challenge: we present some examples of how tethered satellites (from 100s of m to 20 km) are uniquely suited to address certain shortfalls in our ability to measure critical environmental parameters necessary to drive these space weather models. Examples include long baseline electric field measurements, magnetized ionospheric conductivity measurements, and the ability to separate temporal from spatial irregularities in environmental parameters. Tethered satellite functional requirements are presented for two examples of space environment observables.

Gilchrist, Brian E.↗

NASA NTRS2011

A Possible Approach for Addressing Neglected Human Factors Issues of Systems Engineering

The increasing complexity of safety-critical applications has led to the introduction of decision support tools in the transportation and process industries. Automation has also been introduced to support operator intervention in safety-critical applications. These innovations help reduce overall operator workload, and filter application data to maximize the finite cognitive and perceptual resources of system operators. However, these benefits do not come without a cost. Increased computational support for the end-users of safety-critical applications leads to increased reliance on engineers to monitor and maintain automated systems and decision support tools. This paper argues that by focussing on the end-users of complex applications, previous research has tended to neglect the demands that are being placed on systems engineers. The argument is illustrated through discussing three recent accidents. The paper concludes by presenting a possible strategy for building and using highly automated systems based on increased attention by management and regulators, improvements in competency and training for technical staff, sustained support for engineering team resource management, and the development of incident reporting systems for infrastructure failures. This paper represents preliminary work, about which we seek comments and suggestions.

Johnson, Christopher W.↗

NASA NTRS2007

Constellation Program Mission Operations Project Office Status and Support Philosophy

The Constellation Program Mission Operations Project Office (CxP MOP) at Johnson Space Center in Houston Texas is preparing to support the CxP mission operations objectives for the CEV/Orion flights, the Lunar Lander, and and Lunar surface operations. Initially the CEV will provide access to the International Space Station, then progress to the Lunar missions. Initial CEV mission operations support will be conceptually similar to the Apollo missions, and we have set a challenge to support the CEV mission with 50% of the mission operations support currently required for Shuttle missions. Therefore, we are assessing more efficient way to organize the support and new technologies which will enhance our operations support. This paper will address the status of our preparation for these CxP missions, our philosophical approach to CxP operations support, and some of the technologies we are assessing to streamline our mission operations infrastructure.

Smith, Ernest↗

NASA NTRSDate not supplied

HAT m:N Cognitive Task Analysis (CTA)

This Cognitive Task Analysis (CTA) study was designed to understand the capability of the m:N Tactical Operator (TO) interfaces developed by the Human-Autonomy Teaming Laboratory at NASA Ames to support operators responsible for simplified pilot operations of 100 independently operated small UAS (sUAS) in a constrained geographic area. The m:N sUAS TO interface includes a central Tactical Situation Display (TSD) digital map with moving icons reflecting the sUAS location and planned flight route. The interface also has two side panels. The left panel includes a tabular list of UAS assets and mission tasking, a list of recently viewed assets, and a list of events and alerts. The right panel includes a tabular list of UAS assets and their associated telemetry, text-based chat communication window, and a tabbed checklist window. This CTA was adapted from the incident-based applied cognitive task analysis (Militello & Hutton, 1998) and included demographics questions, scenario-based simulations, a task diagram and knowledge audit methods. In addition to examining the support provided by this m:N sUAS TO interface, this CTA study, conducted with aviation subject matter experts in analogous roles to the future tactical operator, was designed to illuminate and project likely cognitive requirements of the tactical operator. Interviewees participated in two scenario-based simulations using the m:N sUAS TO interfaces. In the first simulation, the interviewees supervised 12 sUAS operating in downtown San Diego, California transiting to and from a central sUAS Hive, restaurant locations, and customer drop off locations. Interviewees were asked to react to a UAS Volume Reservation (UVR) event with a two-phase impact on food delivery operations. In the second scenario, the interviewees supervised 100 sUAS operating in the same airspace and with the same mission. Interviewees used the interfaces to recognize and react to two sUAS air vehicle problems. After each scenario, we asked the interviewees a semi-structured list of questions to elicit their reflections about using the interfaces. Interviewees were confident in their ability to respond to two off-nominal situations in each simulation. Interviewees felt that, given high levels of automation on the sUAS, they would be able to manage the events without requiring additional support or handing off the sUAS to a colleague or supervisor in both the n=12 or n=100 sUAS settings. In the n=12 sUAS condition, interviewees used the center map to understand the asset location and progress along with mission tasking. An additional display window, Asset Telemetry, helped interviewees understand battery state and sUAS altitude. When the number of sUAS increased, interviewees altered their behavior. Rather than maintaining awareness of individual assets, interviewees appeared to become more reactive, managing exceptions. Interviewees reported that they spent less time looking at the nominal aircraft, and focused their attention primarily on the off-nominal aircraft. In addition, in the second simulation with n=100 sUAS, interviewees reported that they relied more on the side panels (Mission Timeline and Asset Telemetry) to gather information.

human-autonomy teaming↗

NASA NTRS1986

Space station science lab module

The Science Lab Module (SLM), a key component of the proposed Space Station (SS) orbiting complex, is undergoing intensive study during the project design phase which is currently underway. The SLM is one of the two laboratory modules which, together with two habitation modules, comprise the core elements of the SS reference configurations. Current project emphasis is to configure the SLM as a national science laboratory module facility which would have four major functions: maximize life sciences research potential, support operations of attached payloads, provide shirtsleeve environment for other payload instrument servicing, and support other science requirements. The design studies are focusing on outfitting a common module basic design to accommodate the four specific functions. Although design work for outfitting the SLM for life sciences research is underway, science requirements for the other sciences and functions are not as well developed.

Devincenzi, D. L.↗

NASA NTRS1994

Spacecraft On-Board Information Extraction Computer (SOBIEC)

The Jet Propulsion Laboratory is the Technical Monitor on an SBIR Program issued for Irvine Sensors Corporation to develop a highly compact, dual use massively parallel processing node known as SOBIEC. SOBIEC couples 3D memory stacking technology provided by nCUBE. The node contains sufficient network Input/Output to implement up to an order-13 binary hypercube. The benefit of this network, is that it scales linearly as more processors are added, and it is a superset of other commonly used interconnect topologies such as: meshes, rings, toroids, and trees. In this manner, a distributed processing network can be easily devised and supported. The SOBIEC node has sufficient memory for most multi-computer applications, and also supports external memory expansion and DMA interfaces. The SOBIEC node is supported by a mature set of software development tools from nCUBE. The nCUBE operating system (OS) provides configuration and operational support for up to 8000 SOBIEC processors in an order-13 binary hypercube or any subset or partition(s) thereof. The OS is UNIX (USL SVR4) compatible, with C, C++, and FORTRAN compilers readily available. A stand-alone development system is also available to support SOBIEC test and integration.

Eisenman, David↗

NASA NTRS2004

Range Commanders Council Meteorology Group 88th Meeting: NASA Marshall Space Flight Center Task Report, 2004

Supported Return-to-Flight activities by providing surface climate data from Kennedy Space Center used primarily for ice and dew formation studies, and upper air wind analysis primarily used for ascent loads analyses. The MSFC Environments Group's Terrestrial and Planetary Environments Team documented Space Shuttle day-of-launch support activities by publishing a document in support of SSP Return-to-Flight activities entitled "Space Shuttle Program Flight Operations Support". The team also formalized the Shuttle Natural Environments Technical Panel and chaired the first special session of the SSP Natural Environments Panel meeting at KSC, November 4-7,2003.58 participants from NASA, DOD and other government agencies from across the country attended the meeting.

Roberts, Barry C.↗

NASA NTRS2010

NASA UAS Update

Last year may prove to be a pivotal year for the National Aeronautics and Space Administration (NASA) in the Unmanned Aircraft Systems (UAS) arena, especially in relation to routine UAS access to airspace as NASA accepted an invitation to join the UAS Executive Committee (UAS ExCom). The UAS ExCom is a multi-agency, Federal executive-level committee comprised of the Federal Aviation Administration (FAA), Department of Defense (DoD), Department of Homeland Security (DHS), and NASA with the goals to: 1) Coordinate and align efforts between key Federal Government agencies to achieve routine safe federal public UAS operations in the National Airspace System (NAS); 2) Coordinate and prioritize technical, procedural, regulatory, and policy solutions needed to deliver incremental capabilities; 3) Develop a plan to accommodate the larger stakeholder community at the appropriate time; and 4) Resolve conflicts between Federal Government agencies (FAA, DoD, DHS, and NASA), related to the above goals. The committee was formed in recognition of the need of UAS operated by these agencies to access to the National Airspace System (NAS) to support operational, training, development and research requirements. In order to meet that need, technical, procedural, regulatory, and policy solutions are required to deliver incremental capabilities leading to routine access. The formation of the UAS ExCom is significant in that it represents a tangible commitment by FAA senior leadership to address the UAS access challenge. While the focus of the ExCom is government owned and operated UAS, civil UAS operations are bound to benefit by the progress made in achieving routine access for government UAS. As the UAS ExCom was forming, NASA's Aeronautics Research Mission Directorate began to show renewed interest in UAS, particularly in relation to the future state of the air transportation system under the Next Generation Air Transportation System (NextGen). NASA made funding from the American Recovery and Revitalization Act available in order to continue addressing the issue of routine civil UAS access.

Bauer, Jeffrey Ervin↗

NASA NTRS2015

Software Testbed for Developing and Evaluating Integrated Autonomous Subsystems

To implement fault tolerant autonomy in future space systems, it will be necessary to integrate planning, adaptive control, and state estimation subsystems. However, integrating these subsystems is difficult, time-consuming, and error-prone. This paper describes Intelliface/ADAPT, a software testbed that helps researchers develop and test alternative strategies for integrating planning, execution, and diagnosis subsystems more quickly and easily. The testbed's architecture, graphical data displays, and implementations of the integrated subsystems support easy plug and play of alternate components to support research and development in fault-tolerant control of autonomous vehicles and operations support systems. Intelliface/ADAPT controls NASA's Advanced Diagnostics and Prognostics Testbed (ADAPT), which comprises batteries, electrical loads (fans, pumps, and lights), relays, circuit breakers, invertors, and sensors. During plan execution, an experimentor can inject faults into the ADAPT testbed by tripping circuit breakers, changing fan speed settings, and closing valves to restrict fluid flow. The diagnostic subsystem, based on NASA's Hybrid Diagnosis Engine (HyDE), detects and isolates these faults to determine the new state of the plant, ADAPT. Intelliface/ADAPT then updates its model of the ADAPT system's resources and determines whether the current plan can be executed using the reduced resources. If not, the planning subsystem generates a new plan that reschedules tasks, reconfigures ADAPT, and reassigns the use of ADAPT resources as needed to work around the fault. The resource model, planning domain model, and planning goals are expressed using NASA's Action Notation Modeling Language (ANML). Parts of the ANML model are generated automatically, and other parts are constructed by hand using the Planning Model Integrated Development Environment, a visual Eclipse-based IDE that accelerates ANML model development. Because native ANML planners are currently under development and not yet sufficiently capable, the ANML model is translated into the New Domain Definition Language (NDDL) and sent to NASA's EUROPA planning system for plan generation. The adaptive controller executes the new plan, using augmented, hierarchical finite state machines to select and sequence actions based on the state of the ADAPT system. Real-time sensor data, commands, and plans are displayed in information-dense arrays of timelines and graphs that zoom and scroll in unison. A dynamic schematic display uses color to show the real-time fault state and utilization of the system components and resources. An execution manager coordinates the activities of the other subsystems. The subsystems are integrated using the Internet Communications Engine (ICE). an object-oriented toolkit for building distributed applications.

Testbed↗

NASA NTRS1964

Launch vehicle support.

Criteria for power, weight, personnel, cost and development requirements of launch vehicle support operations

PRELAUNCH PROBLEM↗

NASA NTRS1999

Autonomous Command Operation of the WIRE Spacecraft

This paper presents the end-to-end design architecture for an autonomous commanding capability to be used on the Wide Field Infrared Explorer (WIRE) mission for the uplink of command loads during unattended station contacts. The WIRE mission is the fifth and final mission of NASA's Goddard Space Flight Center Small Explorer (SMEX) series to be launched in March of 1999. Its primary mission is the targeting of deep space fields using an ultra-cooled infrared telescope. Due to its mission design WIRE command loads are large (approximately 40 Kbytes per 24 hours) and must be performed daily. To reduce the cost of mission operations support that would be required in order to uplink command loads, the WIRE Flight Operations Team has implemented an autonomous command loading capability. This capability allows completely unattended operations over a typical two-day weekend period.

Prior, Mike↗