Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Control and Management”

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 289 records · Page 16
All sourcesNASA NTRSDOE OSTI
NASA NTRS2016

EVA Wiki - Transforming Knowledge Management for EVA Flight Controllers and Instructors

The EVA Wiki was recently implemented as the primary knowledge database to retain critical knowledge and skills in the EVA Operations group at NASA's Johnson Space Center by ensuring that information is recorded in a common, easy to search repository. Prior to the EVA Wiki, information required for EVA flight controllers and instructors was scattered across different sources, including multiple file share directories, SharePoint, individual computers, and paper archives. Many documents were outdated, and data was often difficult to find and distribute. In 2011, a team recognized that these knowledge management problems could be solved by creating an EVA Wiki using MediaWiki, a free and open-source software developed by the Wikimedia Foundation. The EVA Wiki developed into an EVA-specific Wikipedia on an internal NASA server. While the technical implementation of the wiki had many challenges, one of the biggest hurdles came from a cultural shift. Like many enterprise organizations, the EVA Operations group was accustomed to hierarchical data structures and individually-owned documents. Instead of sorting files into various folders, the wiki searches content. Rather than having a single document owner, the wiki harmonized the efforts of many contributors and established an automated revision controlled system. As the group adapted to the wiki, the usefulness of this single portal for information became apparent. It transformed into a useful data mining tool for EVA flight controllers and instructors, as well as hundreds of others that support the EVA. Program managers, engineers, astronauts, flight directors, and flight controllers in differing disciplines now have an easier-to-use, searchable system to find EVA data. This paper presents the benefits the EVA Wiki has brought to NASA's EVA community, as well as the cultural challenges it had to overcome.

Johnston, Stephanie S.↗
NASA NTRS2016

EVA Wiki - Transforming Knowledge Management for EVA Flight Controllers and Instructors

The EVA (Extravehicular Activity) Wiki was recently implemented as the primary knowledge database to retain critical knowledge and skills in the EVA Operations group at NASA's Johnson Space Center by ensuring that information is recorded in a common, searchable repository. Prior to the EVA Wiki, information required for EVA flight controllers and instructors was scattered across different sources, including multiple file share directories, SharePoint, individual computers, and paper archives. Many documents were outdated, and data was often difficult to find and distribute. In 2011, a team recognized that these knowledge management problems could be solved by creating an EVA Wiki using MediaWiki, a free and open-source software developed by the Wikimedia Foundation. The EVA Wiki developed into an EVA-specific Wikipedia on an internal NASA server. While the technical implementation of the wiki had many challenges, the one of the biggest hurdles came from a cultural shift. Like many enterprise organizations, the EVA Operations group was accustomed to hierarchical data structures and individually-owned documents. Instead of sorting files into various folders, the wiki searches content. Rather than having a single document owner, the wiki harmonized the efforts of many contributors and established an automated revision control system. As the group adapted to the wiki, the usefulness of this single portal for information became apparent. It transformed into a useful data mining tool for EVA flight controllers and instructors, and also for hundreds of other NASA and contract employees. Program managers, engineers, astronauts, flight directors, and flight controllers in differing disciplines now have an easier-to-use, searchable system to find EVA data. This paper presents the benefits the EVA Wiki has brought to NASA's EVA community, as well as the cultural challenges it had to overcome.

Johnston, Stephanie↗
NASA NTRS1983

Flight testing the Digital Electronic Engine Control (DEEC) A unique management experience

The concept for the DEEC had its origin in the early 1970s. At that time it was recognized that the F100 engine performance, operability, reliability, and cost could be substantially improved by replacing the original mechanical/supervisory electronic control system with a full-authority digital control system. By 1978, the engine manufacturer had designed and initiated the procurement of flight-qualified control system hardware. As a precursor to an integrated controls program, a flight evaluation of the DEEC system on the F-15 aircraft was proposed. Questions regarding the management of the DEEC flight evaluation program are discussed along with the program elements, the technical results of the F-15 evaluation, and the impact of the flight evaluation on after-burning turbofan controls technology and its use in and application to military aircraft. The lessons learned through the conduct of the program are discussed.

Putnam, T. W.↗
NASA NTRSDate not supplied

Identifying Common Use Cases across Extensible Traffic Management (xTM) for Interactions with Air Traffic Controllers

NASA’s Extensible Traffic Management (xTM) builds on the foundation and the architecture of Unmanned Aircraft Systems (UAS) Traffic Management (UTM) concept and extends it broadly to other domains, such as Advanced / Urban Air Mobility (AAM/UAM) and Upper Class E Traffic Management (ETM). These xTM concepts assume the ability to fly in airspace that is authorized to operate solely under xTM services and mostly without any air traffic control (ATC) support. However, they also assume circumstances in which the xTM vehicles would need to operate in conventional ATC-managed airspace, both during nominal and off-nominal scenarios. Due to the vast differences in the xTM vehicle performances and missions, there is a concern that ATC may have difficulty in safely managing the xTM traffic and providing appropriate services to all vehicles, unless a consistent set of roles, procedures, and data exchange requirements are defined across the diverse set of xTM vehicle operations. In this paper, we describe a set of use cases that have been identified in UTM, AAM/UAM, and ETM operations that are related to ATC interactions, and we propose to categorize these use cases across xTM domains based on common trigger events. Organizing the use cases from the perspective of ATC roles per each trigger event is expected to provide the first step in discovering common procedures and data requirements across xTM domains that could help ease the controllers’ cognitive task load and allow them to manage these interactions more safely.

Extensible Traffic Management (xTM)↗
NASA NTRS2013

Simulations of Continuous Descent Operations with Arrival-management Automation and Mixed Flight-deck Interval Management Equipage

Air traffic management simulations conducted in the Airspace Operations Laboratory at NASA Ames Research Center have addressed the integration of trajectory-based arrival-management automation, controller tools, and Flight-Deck Interval Management avionics to enable Continuous Descent Operations (CDOs) during periods of sustained high traffic demand. The simulations are devoted to maturing the integrated system for field demonstration, and refining the controller tools, clearance phraseology, and procedures specified in the associated concept of operations. The results indicate a variety of factors impact the concept's safety and viability from a controller's perspective, including en-route preconditioning of arrival flows, useable clearance phraseology, and the characteristics of airspace, routes, and traffic-management methods in use at a particular site. Clear understanding of automation behavior and required shifts in roles and responsibilities is important for controller acceptance and realizing potential benefits. This paper discusses the simulations, drawing parallels with results from related European efforts. The most recent study found en-route controllers can effectively precondition arrival flows, which significantly improved route conformance during CDOs. Controllers found the tools acceptable, in line with previous studies.

arrival management↗
NASA NTRS2010

Model Transformation for a System of Systems Dependability Safety Case

Software plays an increasingly larger role in all aspects of NASA's science missions. This has been extended to the identification, management and control of faults which affect safety-critical functions and by default, the overall success of the mission. Traditionally, the analysis of fault identification, management and control are hardware based. Due to the increasing complexity of system, there has been a corresponding increase in the complexity in fault management software. The NASA Independent Validation & Verification (IV&V) program is creating processes and procedures to identify, and incorporate safety-critical software requirements along with corresponding software faults so that potential hazards may be mitigated. This Specific to Generic ... A Case for Reuse paper describes the phases of a dependability and safety study which identifies a new, process to create a foundation for reusable assets. These assets support the identification and management of specific software faults and, their transformation from specific to generic software faults. This approach also has applications to other systems outside of the NASA environment. This paper addresses how a mission specific dependability and safety case is being transformed to a generic dependability and safety case which can be reused for any type of space mission with an emphasis on software fault conditions.

Murphy, Judy↗
NASA NTRS1981

Flight test results for the F-8 digital fly-by-wire aircraft control sensor analytic redundancy management technique

This paper reviews the formulation and flight test results of an algorithm to detect and isolate the first failure of any one of twelve duplex control sensor signals being monitored. The technique uses like-signal differences for fault detection while relying upon analytic redundancy relationships among unlike quantities to isolate the faulty sensor. The fault isolation logic utilizes the modified sequential probability ratio test, which explicitly accommodates the inevitable irreducible low frequency errors present in the analytic redundancy residuals. In addition, the algorithm uses sensor output selftest, which takes advantage of the duplex sensor structure by immediately removing a highly erratic sensor from control calculations and analytic redundancy relationships while awaiting a definitive fault isolation decision via analytic redundancy. This study represents a proof of concept demonstration of a methodology that can be applied to duplex or higher flight control sensor configurations and, in addition, can monitor the health of one simplex signal per analytic redundancy relationship.

Deckert, J. C.↗
NASA NTRS1999

Reinventing The Design Process: Teams and Models

The future of space mission designing will be dramatically different from the past. Formerly, performance-driven paradigms emphasized data return with cost and schedule being secondary issues. Now and in the future, costs are capped and schedules fixed-these two variables must be treated as independent in the design process. Accordingly, JPL has redesigned its design process. At the conceptual level, design times have been reduced by properly defining the required design depth, improving the linkages between tools, and managing team dynamics. In implementation-phase design, system requirements will be held in crosscutting models, linked to subsystem design tools through a central database that captures the design and supplies needed configuration management and control. Mission goals will then be captured in timelining software that drives the models, testing their capability to execute the goals. Metrics are used to measure and control both processes and to ensure that design parameters converge through the design process within schedule constraints. This methodology manages margins controlled by acceptable risk levels. Thus, teams can evolve risk tolerance (and cost) as they would any engineering parameter. This new approach allows more design freedom for a longer time, which tends to encourage revolutionary and unexpected improvements in design.

Wall, Stephen D.↗
NASA NTRS2004

CTAS and NASA Air Traffic Management Fact Sheets for En Route Descent Advisor and Surface Management System

The Surface Management System (SMS) is a decision support tool that will help controllers, traffic managers, and NAS users manage the movements of aircraft on the surface of busy airports, improving capacity, efficiency, and flexibility. The Advanced Air Transportation Technologies (AATT) Project at NASA is developing SMS in cooperation with the FAA's Free Flight Phase 2 (FFP2) pro5ram. SMS consists of three parts: a traffic management tool, a controller tool, and a National Airspace System (NAS) information tool.

Lee, Katharine↗
NASA NTRS2016

Intelligent (Autonomous) Power Controller Development for Human Deep Space Exploration

As NASAs Evolvable Mars Campaign and other exploration initiatives continue to mature they have identified the need for more autonomous operations of the power system. For current human space operations such as the International Space Station, the paradigm is to perform the planning, operation and fault diagnosis from the ground. However, the dual problems of communication lag as well as limited communication bandwidth beyond GEO synchronous orbit, underscore the need to change the operation methodology for human operation in deep space. To address this need, for the past several years the Glenn Research Center has had an effort to develop an autonomous power controller for human deep space vehicles. This presentation discusses the present roadmap for deep space exploration along with a description of conceptual power system architecture for exploration modules. It then contrasts the present ground centric control and management architecture with limited autonomy on-board the spacecraft with an advanced autonomous power control system that features ground based monitoring with a spacecraft mission manager with autonomous control of all core systems, including power. It then presents a functional breakdown of the autonomous power control system and examines its operation in both normal and fault modes. Finally, it discusses progress made in the development of a real-time power system model and how it is being used to evaluate the performance of the controller and well as using it for verification of the overall operation.

Power Systems↗
NASA NTRS2013

Integrated Ground Operations Demonstration for Responsive Space Access

Integrated Ground Operations Demonstration Units (IGODU) project developed to mature, integrate and demonstrate advancements in cryogenics, system health management and command and control technologies. Two Distinct Testing Environments: a) GODU Integrated Refrigeration and Storage - GODU LH2; b) GODU Autonomous Control - GODU LO2. Scope: I. GODU LH2: a) Investigate alternative storage and distribution architecture for future cryogenic propellant operations. b) Demonstrate advanced cryogenic propellant handling operations (liquefaction, storage and distribution) of normal boiling point and sub-cooled cryogenic propellants. II. GODU L02: a) Develop and demonstrate advanced control and health management technologies and techniques to autonomously control cryogenic propellant servicing operations. b) Investigate modern COTS hardware and control systems in an effort to reduce the "standing army" of engineers associated with maintaining and operating ground systems through the use of health management and autonomous control technologies. Goals: a) Raise Technology Readiness Levels (TRL) and Integration Readiness Levels (IRL) of several key technology development areas. b) Reduce operations lifecycle costs of future test programs and launch complexes. c) Demonstrate technologies for future exploration beyond low earth orbit. d) Serve as test environments for extraterrestrial surface operations.

Johnson, Robert G.↗
NASA NTRS2009

Concepts for Life Cycle Cost Control Required to Achieve Space Transportation Affordability and Sustainability

Cost control must be implemented through the establishment of requirements and controlled continually by managing to these requirements. Cost control of the non-recurring side of life cycle cost has traditionally been implemented in both commercial and government programs. The government uses the budget process to implement this control. The commercial approach is to use a similar process of allocating the non-recurring cost to major elements of the program. This type of control generally manages through a work breakdown structure (WBS) by defining the major elements of the program. If the cost control is to be applied across the entire program life cycle cost (LCC), the approach must be addressed very differently. A functional breakdown structure (FBS) is defined and recommended. Use of a FBS provides the visibifity to allow the choice of an integrated solution reducing the cost of providing many different elements of like function. The different functional solutions that drive the hardware logistics, quantity of documentation, operational labor, reliability and maintainability balance, and total integration of the entire system from DDT&E through the life of the program must be fully defined, compared, and final decisions made among these competing solutions. The major drivers of recurring cost have been identified and are presented and discussed. The LCC requirements must be established and flowed down to provide control of LCC. This LCC control will require a structured rigid process similar to the one traditionally used to control weight/performance for space transportation systems throughout the entire program. It has been demonstrated over the last 30 years that without a firm requirement and methodically structured cost control, it is unlikely that affordable and sustainable space transportation system LCC will be achieved.

Rhodes, Russel E.↗
NASA NTRS1997

The Challenges of Field Testing the Traffic Management Advisor (TMA) in an Operational Air Traffic Control Facility

The Traffic Management Advisor (TMA), the sequence and schedule tool of the Center/TRACON Automation System (CTAS), was evaluated at the Fort Worth Center (ZFW) in the summer of 1996. This paper describes the challenges encountered during the various phases of the TMA field evaluation, which included system (hardware and software) installation, personnel training, and data collection. Operational procedures were developed and applied to the evaluation process that would ensure air safety. The five weeks of field evaluation imposed minimal impact on the hosting facility and provided valuable engineering and human factors data. The collection of data was very much an opportunistic affair, due to dynamic traffic conditions. One measure of the success of the TMA evaluation is that, rather than remove TMA after the evaluation until it could be fully implemented, the prototype TMA is in continual use at ZFW as the fully operational version is readied for implementation.

Hoang, Ty↗
NASA NTRS1981

Generic waste management requirements for a controlled ecological life support system /CELSS/

Regenerative life support systems for future space missions will require closure of the waste-food loop. Each mission application will generate specific requirements for the waste management system. However, there are generic input and output requirements that can be identified when a probable scenario is chosen. This paper discusses the generic requirements when higher plants are chosen as the primary food source. Attention is focused on the quality and quantity of nutrients necessary for culturing higher plants. The types of wastes to be processed are also discussed. In addition, requirements generated by growing plants on three different substrates are presented. This work suggests that the mineral composition of waste materials may require minimal adjustment to satisfy the plant requirements.

Hoshizaki, T.↗
NASA NTRS1974

Space shuttle program: Shuttle Avionics Integration Laboratory. Volume 7: Logistics management plan

The logistics management plan for the shuttle avionics integration laboratory defines the organization, disciplines, and methodology for managing and controlling logistics support. Those elements requiring management include maintainability and reliability, maintenance planning, support and test equipment, supply support, transportation and handling, technical data, facilities, personnel and training, funding, and management data.

Source record↗
NASA NTRS1975

Report of the facility definition team spacelab UV-Optical Telescope Facility

Scientific requirements for the Spacelab Ultraviolet-Optical Telescope (SUOT) facility are presented. Specific programs involving high angular resolution imagery over wide fields, far ultraviolet spectroscopy, precisely calibrated spectrophotometry and spectropolarimetry over a wide wavelength range, and planetary studies, including high resolution synoptic imagery, are recommended. Specifications for the mounting configuration, instruments for the mounting configuration, instrument mounting system, optical parameters, and the pointing and stabilization system are presented. Concepts for the focal plane instruments are defined. The functional requirements of the direct imaging camera, far ultraviolet spectrograph, and the precisely calibrated spectrophotometer are detailed, and the planetary camera concept is outlined. Operational concepts described in detail are: the makeup and functions of shuttle payload crew, extravehicular activity requirements, telescope control and data management, payload operations control room, orbital constraints, and orbital interfaces (stabilization, maneuvering requirements and attitude control, contamination, utilities, and payload weight considerations).

Source record↗