Search NASA⌕ Search

SEARCH · Search NASA

Results for “Operations Personnel”

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 55 records · Page 3

Automated Scheduling of Personnel to Staff Operations for the Mars Science Laboratory

Leveraging previous work on scheduling personnel for space mission operations, we have adapted ASPEN (Activity Scheduling and Planning Environment) [1] to the domain of scheduling personnel for operations of the Mars Science Laboratory. Automated scheduling of personnel is not new. We compare our representations to a sampling of employee scheduling systems available with respect to desired features. We described the constraints required by MSL personnel schedulers and how each is handled by the scheduling algorithm.

MSL↗

A report on SHARP (Spacecraft Health Automated Reasoning Prototype) and the Voyager Neptune encounter

The development and application of the Spacecraft Health Automated Reasoning Prototype (SHARP) for the operations of the telecommunications systems and link analysis functions in Voyager mission operations are presented. An overview is provided of the design and functional description of the SHARP system as it was applied to Voyager. Some of the current problems and motivations for automation in real-time mission operations are discussed, as are the specific solutions that SHARP provides. The application of SHARP to Voyager telecommunications had the goal of being a proof-of-capability demonstration of artificial intelligence as applied to the problem of real-time monitoring functions in planetary mission operations. AS part of achieving this central goal, the SHARP application effort was also required to address the issue of the design of an appropriate software system architecture for a ground-based, highly automated spacecraft monitoring system for mission operations, including methods for: (1) embedding a knowledge-based expert system for fault detection, isolation, and recovery within this architecture; (2) acquiring, managing, and fusing the multiple sources of information used by operations personnel; and (3) providing information-rich displays to human operators who need to exercise the capabilities of the automated system. In this regard, SHARP has provided an excellent example of how advanced artificial intelligence techniques can be smoothly integrated with a variety of conventionally programmed software modules, as well as guidance and solutions for many questions about automation in mission operations.

Martin, R. G.↗

History and Archives Contribute to the Success of Space Flight Programs

Final Paper, not the Abstract, is attached: This report discusses how history can be used by management, engineering, and operations personnel within space flight programs. Works by professional historians and sociologists inform key decision makers and policy specialists on lessons learned from space flight program management successes and failures, as well as from legislative affairs, policy making, and commercial space efforts. Vehicle engineering history written by engineers for an engineering or operations audience informs project management and technical personnel on lessons learned, best practices, and the rationale behind the design and operation of flight vehicles and supporting ground systems. Archives play a critical role in supporting the efforts of both professional historians and flight program personnel. Suggestions are made concerning how professional historians could leverage the interests and knowledge of flight program personnel to obtain more insight that is needed to support historical research efforts.

Archive↗

Operations planning and analysis handbook for NASA/MSFC phase B development projects

Current operations planning and analysis practices on NASA/MSFC Phase B projects were investigated with the objectives of (1) formalizing these practices into a handbook and (2) suggesting improvements. The study focused on how Science and Engineering (S&E) Operational Personnel support Program Development (PD) Task Teams. The intimate relationship between systems engineering and operations analysis was examined. Methods identified for use by operations analysts during Phase B include functional analysis, interface analysis methods to calculate/allocate such criteria as reliability, Maintainability, and operations and support cost.

Batson, Robert C.↗

New Directions in Space Operations Services in Support of Interplanetary Exploration

To gain access to the necessary operational processes and data in support of NASA's Lunar/Mars Exploration Initiative, new services, adequate levels of computing cycles and access to myriad forms of data must be provided to onboard spacecraft and ground based personnel/systems (earth, lunar and Martian) to enable interplanetary exploration by humans. These systems, cycles and access to vast amounts of development, test and operational data will be required to provide a new level of services not currently available to existing spacecraft, on board crews and other operational personnel. Although current voice, video and data systems in support of current space based operations has been adequate, new highly reliable and autonomous processes and services will be necessary for future space exploration activities. These services will range from the more mundane voice in LEO to voice in interplanetary travel which because of the high latencies will require new voice processes and standards. New services, like component failure predictions based on data mining of significant quantities of data, located at disparate locations, will be required. 3D or holographic representation of onboard components, systems or family members will greatly improve maintenance, operations and service restoration not to mention crew morale. Current operational systems and standards, like the Internet Protocol, will not able to provide the level of service required end to end from an end point on the Martian surface like a scientific instrument to a researcher at a university. Ground operations whether earth, lunar or Martian and in flight operations to the moon and especially to Mars will require significant autonomy that will require access to highly reliable processing capabilities, data storage based on network storage technologies. Significant processing cycles will be needed onboard but could be borrowed from other locations either ground based or onboard other spacecraft. Reliability will be a key factor with onboard and distributed backup processing an absolutely necessary requirement. Current cluster processing/Grid technologies may provide the basis for providing these services. An overview of existing services, future services that will be required and the technologies and standards required to be developed will be presented. The purpose of this paper will be to initiate a technological roadmap, albeit at a high level, of current voice, video, data and network technologies and standards (which show promise for adaptation or evolution) to what technologies and standards need to be redefined, adjusted or areas where new ones require development. The roadmap should begin the differentiation between non manned and manned processes/services where applicable. The paper will be based in part on the activities of the CCSDS Monitor and Control working group which is beginning the process of standardization of the these processes. Another element of the paper will be based on an analysis of current technologies supporting space flight processes and services at JSC, MSFC, GSFC and to a lesser extent at KSC. Work being accomplished in areas such as Grid computing, data mining and network storage at ARC, IBM and the University of Alabama at Huntsville will be researched and analyzed.

Bradford, Robert N.↗

Component-Based Visualization System

A software system has been developed that gives engineers and operations personnel with no "formal" programming expertise, but who are familiar with the Microsoft Windows operating system, the ability to create visualization displays to monitor the health and performance of aircraft/spacecraft. This software system is currently supporting the X38 V201 spacecraft component/system testing and is intended to give users the ability to create, test, deploy, and certify their subsystem displays in a fraction of the time that it would take to do so using previous software and programming methods. Within the visualization system there are three major components: the developer, the deployer, and the widget set. The developer is a blank canvas with widget menu items that give users the ability to easily create displays. The deployer is an application that allows for the deployment of the displays created using the developer application. The deployer has additional functionality that the developer does not have, such as printing of displays, screen captures to files, windowing of displays, and also serves as the interface into the documentation archive and help system. The third major component is the widget set. The widgets are the visual representation of the items that will make up the display (i.e., meters, dials, buttons, numerical indicators, string indicators, and the like). This software was developed using Visual C++ and uses COTS (commercial off-the-shelf) software where possible.

Delgado, Francisco↗

Failure environment analysis tool applications

Understanding risks and avoiding failure are daily concerns for the women and men of NASA. Although NASA's mission propels us to push the limits of technology, and though the risks are considerable, the NASA community has instilled within, the determination to preserve the integrity of the systems upon which our mission and, our employees lives and well-being depend. One of the ways this is being done is by expanding and improving the tools used to perform risk assessment. The Failure Environment Analysis Tool (FEAT) was developed to help engineers and analysts more thoroughly and reliably conduct risk assessment and failure analysis. FEAT accomplishes this by providing answers to questions regarding what might have caused a particular failure; or, conversely, what effect the occurrence of a failure might have on an entire system. Additionally, FEAT can determine what common causes could have resulted in other combinations of failures. FEAT will even help determine the vulnerability of a system to failures, in light of reduced capability. FEAT also is useful in training personnel who must develop an understanding of particular systems. FEAT facilitates training on system behavior, by providing an automated environment in which to conduct 'what-if' evaluation. These types of analyses make FEAT a valuable tool for engineers and operations personnel in the design, analysis, and operation of NASA space systems.

Pack, Ginger L.↗

Failure environment analysis tool applications

Understanding risks and avoiding failure are daily concerns for the women and men of NASA. Although NASA's mission propels us to push the limits of technology, and though the risks are considerable, the NASA community has instilled within it, the determination to preserve the integrity of the systems upon which our mission and, our employees lives and well-being depend. One of the ways this is being done is by expanding and improving the tools used to perform risk assessment. The Failure Environment Analysis Tool (FEAT) was developed to help engineers and analysts more thoroughly and reliably conduct risk assessment and failure analysis. FEAT accomplishes this by providing answers to questions regarding what might have caused a particular failure; or, conversely, what effect the occurrence of a failure might have on an entire system. Additionally, FEAT can determine what common causes could have resulted in other combinations of failures. FEAT will even help determine the vulnerability of a system to failures, in light of reduced capability. FEAT also is useful in training personnel who must develop an understanding of particular systems. FEAT facilitates training on system behavior, by providing an automated environment in which to conduct 'what-if' evaluation. These types of analyses make FEAT a valuable tool for engineers and operations personnel in the design, analysis, and operation of NASA space systems.

Pack, Ginger L.↗

Lightning instrumentation for warning and measurement

A presentation of instrumentation techniques used at Kennedy Space Center for assessing the hazards of lightning, measure lightning currents, induced voltage effects and assess the probability of lightning strikes to launch structures. The electric field and sferics are measured to determine the lightning hazard from the clouds. Measurements are made on launch structures to determine the magnitude of lightning currents and the induced voltages. Photographs are taken to ascertain the location of lightning strikes. Data is analyzed and presented on operations personnel and the Weather Office for assessment of impact on launch critical electromechanical systems and industrial operations.

Wojtasinski, R. J.↗

Payload integration and operations

Integration and operation of Spacelab payloads presents major challenges to engineering disciplines in areas of ground operations and flight mission operations. The integration of ground operations encompasses activities performed by the instrument developers and principal investigators and by the centralized payload integration site and launch site. The payload will be operated on orbit by a payload crew trained in payload experimentation and by a payload operations control center where investigator science groups and operations personnel are prepared to provide support. The payload mission planning, control center, data processing facility and operations are developed and verified prior to realtime flight operations. The mission management approach to minimize program costs and impacts to payloads and the Space Transportation System/Spacelab accommodations is presented.

Hall, R. R.↗

Intelligent user interface concept for space station

The space station computing system must interface with a wide variety of users, from highly skilled operations personnel to payload specialists from all over the world. The interface must accommodate a wide variety of operations from the space platform, ground control centers and from remote sites. As a result, there is a need for a robust, highly configurable and portable user interface that can accommodate the various space station missions. The concept of an intelligent user interface executive, written in Ada, that would support a number of advanced human interaction techniques, such as windowing, icons, color graphics, animation, and natural language processing is presented. The user interface would provide intelligent interaction by understanding the various user roles, the operations and mission, the current state of the environment and the current working context of the users. In addition, the intelligent user interface executive must be supported by a set of tools that would allow the executive to be easily configured and to allow rapid prototyping of proposed user dialogs. This capability would allow human engineering specialists acting in the role of dialog authors to define and validate various user scenarios. The set of tools required to support development of this intelligent human interface capability is discussed and the prototyping and validation efforts required for development of the Space Station's user interface are outlined.

Comer, Edward↗

Satellite Servicer System flight demonstration program

The major hardware elements, demonstration objectives, and technical approaches, as well as existing and developing technologies for applicability to the Satellite Servicer System (SSSFD) program are presented. In a project to develop the capability of servicing satellites in remote locations, NASA and SDI have planned a series of flights to demonstrate autonomous rendezvous and docking, supervised autonomous fluid transfer, and supervised autonomous orbital replacement unit exchange. Program objectives, design reference mission, and flight demonstrations are described. The expanded capability demonstrated by the SSSFD program will provide alternatives to excessive dependence on ground operations personnel and training, increase the reach into unique space environments, and decrease the costs of managing and operating space assets.

Moore, James S.↗

TOPEX NASA Altimeter Operations Handbook, September 1992

This operations handbook identifies the commands for the NASA radar altimeter for the TOPEX/Poseidon spacecraft, defines the functions of these commands, and provides supplemental reference material for use by the altimeter operations personnel. The main emphasis of this document is placed on command types, command definitions, command sequences, and operational constraints. Additional document sections describe uploadable altimeter operating parameters, the telemetry stream data contents (for both the science and the engineering data), the Missions Operations System displays, and the spacecraft and altimeter health monitors.

Hancock, David W., III↗

AirSTAR Hardware and Software Design for Beyond Visual Range Flight Research

The National Aeronautics and Space Administration (NASA) Airborne Subscale Transport Aircraft Research (AirSTAR) Unmanned Aerial System (UAS) is a facility developed to study the flight dynamics of vehicles in emergency conditions, in support of aviation safety research. The system was upgraded to have its operational range significantly expanded, going beyond the line of sight of a ground-based pilot. A redesign of the airborne flight hardware was undertaken, as well as significant changes to the software base, in order to provide appropriate autonomous behavior in response to a number of potential failures and hazards. Ground hardware and system monitors were also upgraded to include redundant communication links, including ADS-B based position displays and an independent flight termination system. The design included both custom and commercially available avionics, combined to allow flexibility in flight experiment design while still benefiting from tested configurations in reversionary flight modes. A similar hierarchy was employed in the software architecture, to allow research codes to be tested, with a fallback to more thoroughly validated flight controls. As a remotely piloted facility, ground systems were also developed to ensure the flight modes and system state were communicated to ground operations personnel in real-time. Presented in this paper is a general overview of the concept of operations for beyond visual range flight, and a detailed review of the airborne hardware and software design. This discussion is held in the context of the safety and procedural requirements that drove many of the design decisions for the AirSTAR UAS Beyond Visual Range capability.

Laughter, Sean↗

Human Performance Considerations for Remotely Piloted Aircraft Systems (RPAS)

Successful integration of Remotely Piloted Aircraft Systems (RPAS) into civil airspace will not only require solutions to technical challenges, but will also require that the design and operation of RPAS take into account human limitations and capabilities. Human factors can affect overall system performance whenever the system relies on people to interact with another element of the system. Four types of broad interactions can be described. These are (1) interactions between people and hardware, such as controls and displays; (2) human use of procedures and documentation; (3) impact of the task environment, including lighting, noise and monotony; and lastly, (4) interactions between operational personnel, including communication and coordination. In addition to the human factors that have been identified for conventional aviation, RPAS operations introduce a set of unique human challenges. The purpose of document is to raise human factors issues for consideration by workgroups of the ICAO RPAS panel as they work to develop guidance material and additions to ICAO annexes. It is anticipated that the content of this document will be revised and updated as the work of the panel progresses.

ICAO↗

A real-time navigation monitoring expert system for the Space Shuttle Mission Control Center

The ONAV (Onboard Navigation) Expert System has been developed as a real time console assistant for use by ONAV flight controllers in the Mission Control Center at the Johnson Space Center. This expert knowledge based system is used to monitor the Space Shuttle onboard navigation system, detect faults, and advise flight operations personnel. This application is the first knowledge-based system to use both telemetry and trajectory data from the Mission Operations Computer (MOC). To arrive at this stage, from a prototype to real world application, the ONAV project has had to deal with not only AI issues but operating environment issues. The AI issues included the maturity of AI languages and the debugging tools, verification, and availability, stability and size of the expert pool. The environmental issues included real time data acquisition, hardware suitability, and how to achieve acceptance by users and management.

Wang, Lui↗

Controlled Rest on the Flight Deck: Profile of Use, Challenges, and Best Practices

Managing fatigue in 24/7 operations is complex; fatigue and performance degradation can have health and safety consequences for the workers and can have economic and community consequences. We will present new findings on sleep, circadian misalignment, and performance in operational personnel. The presentations will shed light on how sleep and circadian misalignment affect workers' performance, safety, and health across multiple operations, and their application in fatigue risk management.As part of this symposium, I will discuss how pilots can use short naps (controlled rest) as a countermeasure to elevated sleepiness in-flight. My presentation will describe how and when controlled rest is used operationally and outline best practice guidelines for maximizing the benefits while managing the associated risks.

aviation↗

Turning Operational Lessons Learned into Design Reality

The capabilities and limitations of a particular system design are well known by the people who operate it. Operational workarounds, operational notes and lessons learned are traditional methods for dealing with and documenting design shortcomings. The beginning of each new program brings the hope that hard-learned lessons will be incorporated into the next new system. But often operations personnel find their well-intentioned efforts frustrated by an inability to have their inputs considered by design personnel who have strictly-scoped requirements that are coupled with ambitious cost and schedule targets. There is a way for operational inputs to make it into the design, but the solution involves a combination of organizational culture and technical data. Any organization that utilizes this approach can realize significant benefits over the life cycle of their project.

Brady, David A.↗