Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “issues 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 451 records · Page 25
All sourcesNASA NTRSDOE OSTI
NASA NTRS2006

Adaptive and Adaptable Automation Design: A Critical Review of the Literature and Recommendations for Future Research

This report presents a review of literature on approaches to adaptive and adaptable task/function allocation and adaptive interface technologies for effective human management of complex systems that are likely to be issues for the Next Generation Air Transportation System, and a focus of research under the Aviation Safety Program, Integrated Intelligent Flight Deck Project. Contemporary literature retrieved from an online database search is summarized and integrated. The major topics include the effects of delegation-type, adaptable automation on human performance, workload and situation awareness, the effectiveness of various automation invocation philosophies and strategies to function allocation in adaptive systems, and the role of user modeling in adaptive interface design and the performance implications of adaptive interface technology.

Prinzel, Lawrence J., III↗
NASA NTRS2013

Precision Departure Release Capability (PDRC) Overview and Results: NASA to FAA Research Transition

NASA researchers developed the Precision Departure Release Capability (PDRC) concept to improve the tactical departure scheduling process. The PDRC system is comprised of: 1) a surface automation system that computes ready time predictions and departure runway assignments, 2) an en route scheduling automation tool that uses this information to estimate ascent trajectories to the merge point and computes release times and, 3) an interface that provides two-way communication between the two systems. To minimize technology transfer issues and facilitate its adoption by TMCs and Frontline Managers (FLM), NASA developed the PDRC prototype using the Surface Decision Support System (SDSS) for the Tower surface automation tool, a research version of the FAA TMA (RTMA) for en route automation tool and a digital interface between the two DSTs to facilitate coordination.

PDRC↗
NASA NTRS2014

Assessment of MSFCs Process for the Development and Activation of Space Act Agreements

A Space Act Agreement (SAA) is a contractual vehicle that NASA utilizes to form partnerships with non-NASA entities to stimulate cutting-edge innovation within the science and technology communities while concurrently supporting the NASA missions. SAAs are similar to traditional contracts in that they involve the commitment of Agency resources but allow more flexibility and are more cost effective to implement than traditional contracts. Consequently, the use of SAAs to develop partnerships has greatly increased over the past several years. To facilitate this influx of SAAs, Marshall Space Flight Center (MSFC) developed a process during a kaizen event to streamline and improve the quality of SAAs developed at the Center level. This study assessed the current SAA process to determine if improvements could be implemented to increase productivity, decrease time to activation, and improve the quality of deliverables. Using a combination of direct procedural observation, personnel interviews, and statistical analysis, elements of the process in need of remediation were identified and potential solutions developed. The findings focus primarily on the difficulties surrounding tracking and enforcing process adherence and communication issues among stakeholders. Potential solutions include utilizing customer relationship management (CRM) software to facilitate process coordination and co-locating or potentially merging the two separate organizations involved in SAA development and activation at MSFC.

Daugherty, Rachel A.↗
NASA NTRS2018

Next Generation Aircraft Design Considering Airline Operations and Economics

Traditional approaches to design and optimization of a new system often use a system-centric objective and do not take into consideration how the operator will use this new system alongside other existing systems. When the new system design is incorporated into the broader group of systems, the performance of the operator-level objective can be sub-optimal due to the unmodeled interaction between the new system and the other systems. Among the few available references that describe attempts to address this disconnect, most follow an MDO (Multidisciplinary Design Optimization)-motivated sequential decomposition approach of first designing a very good system and then providing this system to the operator who, decides the best way to use this new system along with the existing systems. This paper addresses this issue by including aircraft design, airline operations, and revenue management "subspaces"; and presents an approach that could simultaneously solve these subspaces posed as a monolithic optimization problem rather than the traditional approach described above. The monolithic approach makes the problem an expensive Mixed Integer Non-Linear Programming problem, which are extremely difficult to solve. To address the problem, we use a recently developed optimization framework that simultaneously solves the subspaces to capture the "synergy" in the problem that the previous decomposition approaches did not exploit, addresses mixed-integer/discrete type design variables in an efficient manner, and accounts for computationally expensive analysis tools. This approach solves an 11-route airline network problem consisting of 94 decision variables including 33 integer and 61 continuous type variables. Simultaneously solving the subspaces leads to significant improvement in the fleet-level objective of the airline when compared to the previously developed sequential subspace decomposition approach.

Roy, Satadru↗
NASA NTRS2017

Security Vulnerability Profiles of NASA Mission Software: Empirical Analysis of Security Related Bug Reports

NASA develops, runs, and maintains software systems for which security is of vital importance. Therefore, it is becoming an imperative to develop secure systems and extend the current software assurance capabilities to cover information assurance and cybersecurity concerns of NASA missions. The results presented in this report are based on the information provided in the issue tracking systems of one ground mission and one flight mission. The extracted data were used to create three datasets: Ground mission IVV issues, Flight mission IVV issues, and Flight mission Developers issues. In each dataset, we identified the software bugs that are security related and classified them in specific security classes. This information was then used to create the security vulnerability profiles (i.e., to determine how, why, where, and when the security vulnerabilities were introduced) and explore the existence of common trends. The main findings of our work include:- Code related security issues dominated both the Ground and Flight mission IVV security issues, with 95 and 92, respectively. Therefore, enforcing secure coding practices and verification and validation focused on coding errors would be cost effective ways to improve mission's security. (Flight mission Developers issues dataset did not contain data in the Issue Category.)- In both the Ground and Flight mission IVV issues datasets, the majority of security issues (i.e., 91 and 85, respectively) were introduced in the Implementation phase. In most cases, the phase in which the issues were found was the same as the phase in which they were introduced. The most security related issues of the Flight mission Developers issues dataset were found during Code Implementation, Build Integration, and Build Verification; the data on the phase in which these issues were introduced were not available for this dataset.- The location of security related issues, as the location of software issues in general, followed the Pareto principle. Specifically, for all three datasets, from 86 to 88 the security related issues were located in two to four subsystems.- The severity levels of most security issues were moderate, in all three datasets.- Out of 21 primary security classes, five dominated: Exception Management, Memory Access, Other, Risky Values, and Unused Entities. Together, these classes contributed from around 80 to 90 of all security issues in each dataset. This again proves the Pareto principle of uneven distribution of security issues, in this case across CWE classes, and supports the fact that addressing these dominant security classes provides the most cost efficient way to improve missions' security. The findings presented in this report uncovered the security vulnerability profiles and identified the common trends and dominant classes of security issues, which in turn can be used to select the most efficient secure design and coding best practices compiled by the part of the SARP project team associated with the NASA's Johnson Space Center. In addition, these findings provide valuable input to the NASA IVV initiative aimed at identification of the two 25 CWEs of ground and flight missions.

vulnerability↗
NASA NTRS1991

Lessons learned and their application to program development and cultural issues

The main objectives of space product assurance are, in effect, the same as those of Total Quality Management (TQM) or its many variants. The most significant ingredients are the lessons learned and their application to ongoing and future programs as they are affected by changes in the cultural environment. The cultural issues which affect almost everything done in technical programs and projects are considered. Understanding the lessons learned and the synergism which results from this combination of knowledge, culture, and lessons learned is identified as crucial. A brief discussion of the closed loop linkage that should exist between the world of hands on activities and that of educational institutions is presented.

Roth, Gilbert L.↗
NASA NTRS2005

Managed Development Environment Successes for MSFC's VIPA Team

This paper outlines the best practices of the Vehicle Design Team for VIPA. VIPA is the Vehicle Integrated Performance Analysis Team at MSFC. This team was created to reconnect the individual engineering disciplines to be able to perform system level technical assessments in support of program decisions. The functions of the VIPA Vehicle Design (VVD) discipline team are to maintain the controlled reference geometry and provide linked, simplified geometry for each of the other discipline analyses. The core of the VVD work, and the approach for VVD s first task of controlling the reference geometry, involves systems engineering, top-down, layout-based CAD modeling within a Product Data Manager (PDM) development environment. The topdown approach allcws for simple contrnl of very large, integrated assemblies and greatly enhances the ability to generate trade configurations and reuse data. The second W D task, model simplification for analysis, is handled within the managed environment through application of the master model concept. In this approach, there is a single controlling, or master, product definition dataset. Connected to this master model are reference datasets with live geometric and expression links. The referenced models can be for drawings, manufacturing, visualization, embedded analysis, or analysis simplification. A discussion of web based interaction, including visualization, between the design and other disciplines is included. Demonstrated examples are cited, including the Space Launch Initiative development cycle, the Saturn V systems integration and verification cycle, an Orbital Space Plane study, and NASA Exploration Office studies of Shuttle derived and clean sheet launch vehicles. The VIPA Team has brought an immense amount of detailed data to bear on program issues. A central piece of that success has been the Managed Development Environment and the VVD Team approach to modeling.

Finckenor, Jeff↗
NASA NTRS2005

Managed Development Environment Successes for MSFC's VIPA Team

This paper outlines the best practices of the Vehicle Design Team for VIPA. The functions of the VIPA Vehicle Design (VVD) discipline team are to maintain the controlled reference geometry and provide linked, simplified geometry for each of the other discipline analyses. The core of the VVD work, and the approach for VVD s first task of controlling the reference geometry, involves systems engineering, top-down, layout-based CAD modeling within a Product Data Manager (PDM) development environment. The top- down approach allows for simple control of very large, integrated assemblies and greatly enhances the ability to generate trade configurations and reuse data. The second VVD task, model simplification for analysis, is handled within the managed environment through application of the master model concept. In this approach, there is a single controlling, or master, product definition dataset. Connected to this master model are reference datasets with live geometric and expression links. The referenced models can be for drawings, manufacturing, visualization, embedded analysis, or analysis simplification. A discussion of web based interaction, including visualization, between the design and other disciplines is included. Demonstrated examples are cited, including the Space Launch Initiative development cycle, the Saturn V systems integration and verification cycle, an Orbital Space Plane study, and NASA Exploration Office studies of Shuttle derived and clean sheet launch vehicles. The VIPA Team has brought an immense amount of detailed data to bear on program issues. A central piece of that success has been the Managed Development Environment and the VVD Team approach to modeling.

Finckenor, Jeff↗
NASA NTRS2000

Do-It-Yourself: A Special Library's Approach to Creating Dynamic Web Pages Using Commercial Off-The-Shelf Applications

Many librarians may feel that dynamic Web pages are out of their reach, financially and technically. Yet we are reminded in library and Web design literature that static home pages are a thing of the past. This paper describes how librarians at the Institute for Defense Analyses (IDA) library developed a database-driven, dynamic intranet site using commercial off-the-shelf applications. Administrative issues include surveying a library users group for interest and needs evaluation; outlining metadata elements; and, committing resources from managing time to populate the database and training in Microsoft FrontPage and Web-to-database design. Technical issues covered include Microsoft Access database fundamentals, lessons learned in the Web-to-database process (including setting up Database Source Names (DSNs), redesigning queries to accommodate the Web interface, and understanding Access 97 query language vs. Standard Query Language (SQL)). This paper also offers tips on editing Active Server Pages (ASP) scripting to create desired results. A how-to annotated resource list closes out the paper.

Relational databases↗
NASA NTRS2009

Human Research Program Human Health Countermeasures Element Extravehicular Activity (EVA) Risk Standing Review Panel (SRP)

The Extravehicular Activity (EVA) Risk Standing Review Panel (SRP) was favorably impressed by the operational risk management approach taken by the Human Research Program (HRP) Integrated Research Plan (IRP) to address the stated life sciences issues. The life sciences community at the Johnson Space Center (JSC) seems to be focused on operational risk management. This approach is more likely to provide risk managers with the information they need at the time they need it. Concerning the information provided to the SRP by the EVA Physiology, Systems, and Performance Project (EPSP), it is obvious that a great deal of productive activity is under way. Evaluation of this information was hampered by the fact that it often was not organized in a fashion that reflects the "Gaps and Tasks" approach of the overall Human Health Countermeasures (HHC) effort, and that a substantial proportion of the briefing concerned subjects that, while interesting, are not part of the HHC Element (e.g., the pressurized rover presentation). Additionally, no information was provided on several of the tasks or how they related to work underway or already accomplished. This situation left the SRP having to guess at the efforts and relationship to other elements, and made it hard to easily map the EVA Project efforts currently underway, and the data collected thus far, to the gaps and tasks in the IRP. It seems that integration of the EPSP project into the HHC Element could be improved. Along these lines, we were concerned that our SRP was split off from the other participating SRPs at an early stage in the overall agenda for the meeting. In reality, the concerns of EPSP and other projects share much common ground. For example, the commonality of the concerns of the EVA and exercise physiology groups is obvious, both in terms of what reduced exercise capacity can do to EVA capability, and how the exercise performed during an EVA could contribute to an overall exercise countermeasure prescription.

Norfleet, William↗
NASA NTRS2012

Leveraging Independent Management and Chief Engineer Hierarchy: Vertically and Horizontally-Derived Technical Authority Value

In the development of complex spacecraft missions, project management authority is usually extended hierarchically from NASA's highest agency levels down to the implementing institution's project team level, through both the center and the program. In parallel with management authority, NASA utilizes a complementary, but independent, hierarchy of technical authority (TA) that extends from the agency level to the project, again, through both the center and the program. The chief engineers (CEs) who serve in this technical authority capacity oversee and report on the technical status and ensure sound engineering practices, controls, and management of the projects and programs. At the lowest level, implementing institutions assign project CEs to technically engage projects, lead development teams, and ensure sound technical principles, processes, and issue resolution. At the middle level, programs and centers independently use CEs to ensure the technical success of their projects and programs. At the agency level, NASA's mission directorate CEs maintain technical cognizance over every program and project in their directorate and advise directorate management on the technical, cost, schedule, and programmatic health of each. As part of this vertically-extended CE team, a program level CE manages a continually varying balance between penetration depth and breadth across his or her assigned missions. Teamwork issues and information integration become critical for management at all levels to ensure value-added use of both the synergy available between CEs at the various agency levels, and the independence of the technical authority at each organization.

Barley, Bryan↗
NASA NTRS1999

New challenges for Life Sciences flight project management

Scientists have conducted studies involving human spaceflight crews for over three decades. These studies have progressed from simple observations before and after each flight to sophisticated experiments during flights of several weeks up to several months. The findings from these experiments are available in the scientific literature. Management of these flight experiments has grown into a system fashioned from the Apollo Program style, focusing on budgeting, scheduling and allocation of human and material resources. While these areas remain important to the future, the International Space Station (ISS) requires that the Life Sciences spaceflight experiments expand the existing project management methodology. The use of telescience with state-the-art information technology and the multi-national crews and investigators challenges the former management processes. Actually conducting experiments on board the ISS will be an enormous undertaking and International Agreements and Working Groups will be essential in giving guidance to the flight project management Teams forged in this matrix environment must be competent to make decisions and qualified to work with the array of engineers, scientists, and the spaceflight crews. In order to undertake this complex task, data systems not previously used for these purposes must be adapted so that the investigators and the project management personnel can all share in important information as soon as it is available. The utilization of telescience and distributed experiment operations will allow the investigator to remain involved in their experiment as well as to understand the numerous issues faced by other elements of the program The complexity in formation and management of project teams will be a new kind of challenge for international science programs. Meeting that challenge is essential to assure success of the International Space Station as a laboratory in space.

NASA Discipline General Space Life Sciences↗
NASA NTRS1987

Theory underlying CRM training: Psychological issues in flight crew performance and crew coordination

What psychological theory and research can reveal about training in Cockpit Resource Management (CRM) is summarized. A framework is provided for the critical analysis of current approaches to CRM training. Background factors and definitions critical to evaluating CRM are reviewed, followed by a discussion of issues directly related to CRM training effectiveness. Some of the things not known about the optimization of crew performance and the research needed to make these efforts as effective as possible are described.

Helmreich, Robert L.↗
NASA NTRS1989

Piloted-simulation evaluation of escape guidance for microburst wind shear encounters

Numerous air carrier accidents and incidents result from encounters with the atmospheric wind shear associated with microburst phenomena, in some cases resulting in heavy loss of life. An important issue in current wind shear research is how to best manage aircraft performance during an inadvertent wind shear encounter. The goals of this study were to: (1) develop techniques and guidance for maximizing an aircraft's ability to recover from microburst encounters following takeoff, (2) develop an understanding of how theoretical predictions of wind shear recovery performance might be achieved in actual use, and (3) gain insight into the piloting factors associated with recovery from microburst encounters. Three recovery strategies were implemented and tested in piloted simulation. Results show that a recovery strategy based on flying a flight path angle schedule produces improved performance over constant pitch attitude or acceleration-based recovery techniques. The best recovery technique was initially counterintuitive to the pilots who participated in the study. Evidence was found to indicate that the techniques required for flight through the turbulent vortex of a microburst may differ from the techniques being developed using classical, nonturbulent microburst models.

Hinton, David A.↗
NASA NTRS1991

Modelling parallel programs and multiprocessor architectures with AXE

AXE, An Experimental Environment for Parallel Systems, was designed to model and simulate for parallel systems at the process level. It provides an integrated environment for specifying computation models, multiprocessor architectures, data collection, and performance visualization. AXE is being used at NASA-Ames for developing resource management strategies, parallel problem formulation, multiprocessor architectures, and operating system issues related to the High Performance Computing and Communications Program. AXE's simple, structured user-interface enables the user to model parallel programs and machines precisely and efficiently. Its quick turn-around time keeps the user interested and productive. AXE models multicomputers. The user may easily modify various architectural parameters including the number of sites, connection topologies, and overhead for operating system activities. Parallel computations in AXE are represented as collections of autonomous computing objects known as players. Their use and behavior is described. Performance data of the multiprocessor model can be observed on a color screen. These include CPU and message routing bottlenecks, and the dynamic status of the software.

Yan, Jerry C.↗
NASA NTRS1995

Managing the space sciences

In April 1994 the National Research Council received a request from NASA that the NRC's Space Studies Board provide guidance on questions relating to the management of NASA's programs in the space sciences. The issues raised in the request closely reflect questions posed in the agency's fiscal year 1994 Senate appropriations report. These questions included the following: Should all the NASA space science programs be gathered into a 'National Institute for Space Science'? What other organizational changes might be made to improve the coordination and oversight of NASA space science programs? What processes should be used for establishing interdisciplinary science priorities based on scientific merit and other criteria, while ensuring opportunities for newer fields and disciplines to emerge? And what steps could be taken to improve utilization of advanced technologies in future space scienc missions? This report details the findings of the Committee on the Future of Space Science (FOSS) and its three task groups: the Task Group on Alternative Organizations, Task Group on Research Prioritization, and the Task Group on Technology.

Source record↗
NASA NTRS1996

Archiving Microgravity Flight Data and Samples

To obtain help in evaluating its current strategy for archiving data and samples obtained in microgravity research, NASA's Microgravity Science and Applications Division (MSAD) asked the Space Studies Board's Committee on Microgravity Research for guidance on the following questions: What data should be archived and where should it be kept? In what form should the data be maintained (electronic files, photographs, hard copy, samples)? What should the general format of the database be? To what extent should it be universally accessible and through what mechanisms? Should there be a period of time for which principal investigators have proprietary access? If so, how long should proprietary data be stored? What provisions should be made for data obtained from ground-based experiments? What should the deadline be for investigators placing their data in the archive? How long should data be saved? How long should data be easily accessible? As a prelude to making recommendations for optimum selection and storage of microgravity data and samples, the committee in this report briefly describes NASA's past archiving practices and outlines MSAD's current archiving strategy. Although the committee found that only a limited number of experiments have thus far been archived, it concluded that the general archiving strategy, characterized by MSAD as minimalist, appears viable. A central focus of attention is the Experiment Data Management Plan (EDMP), MSAD's recently instituted data management and archiving framework for flight experiments. Many of the report's recommendations are aimed at enhancing the effectiveness of the EDMP approach, which the committee regards as an appropriate data management method for MSAD. Other recommendations provide guidance on broader issues related to the questions listed above. This report does not address statutory or regulatory records retention requirements.

Source record↗
NASA NTRS1995

Data management, archiving, visualization and analysis of space physics data

A series of programs for the visualization and analysis of space physics data has been developed at UCLA. In the course of those developments, a number of lessons have been learned regarding data management and data archiving, as well as data analysis. The issues now facing those wishing to develop such software, as well as the lessons learned, are reviewed. Modern media have eased many of the earlier problems of the physical volume required to store data, the speed of access, and the permanence of the records. However, the ultimate longevity of these media is still a question of debate. Finally, while software development has become easier, cost is still a limiting factor in developing visualization and analysis software.

Russell, C. T.↗