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.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 343 records · Page 19

All sources NASA NTRS DOE OSTI

NASA NTRS2008

Reaching for the APEX at Ames

The multidimensional design of the APEX program is the result of an extensive research and development effort dating back nearly a decade. "In the late 1990s and early 2000, we were pretty successful at getting new research and technology projects here at the center," Johnson says, "and we had a lack of critical mass of project managers. We were taking people who were primarily researchers and putting them in the position of managing projects." Smith and Johnson held a series of workshops across the center during 2000 and 2001 to gather feedback about how to address this issue. When they briefed the center's senior management on their findings, one of the top recommendations was to establish a project manager development program at Ames. At that point, they cast a wide net for ideas and information. "We did centerwide needs assessment, we did focus groups, we did surveys," Smith says. "We came up with a proposal for what a program would look like, tying in what we knew about the Academy of Program1 Project Leadership (now the Academy for Program/Project and Engineering Leadership, or APPEL), what we've seen at other centers, what other centers have tried. We were always checking to make sure our program mapped to APPEL. We also looked at the PMI [Project Management Institute] model, INCOSE [International Council on Systems Engineering], CMMI [Capability Maturity Model Integration], you name it." "We had a lot of conversations with the Jet Propulsion Lab and Goddard," Johnson adds. "We saw those centers as models for what Ames was aspiring to be in terms of a center for managing space flight missions." Their research confirmed what they already knew-that strong practitioner involvement would be critical to their program design process. 'XPEX is for the practitioner by the practitioner," Smith says. "They have to be a part of designing it. Otherwise there's no way we could design a program that meets their needs." At the same time that they worked at the grassroots level, they also solicited feedback from the center's senior management. "We recognized that in order for anything to succeed here, we needed to have a champion at the center management level," Johnson said. "You have to have champions, and you have to listen to what the senior managers are saying. They have their own ideas." In the case of APEX, one of those ideas fundamentally reshaped the program. "When we originally started, it was a project management development program," Johnson says, "but in our meeting with our center director, he said, 'Project management is important, but we also need to strengthen our systems engineering.' So we basically added that component to the program based on what he wanted."

Kohut, Matthew↗

NASA NTRS1991

Information management challenges of the EOS Data and Information System

An overview of the current information management concepts that are embodied in the plans for the Earth Observing System Data and Information System (EOSDIS) is presented, and some of the technology development and application areas that are envisioned to be particularly challenging are introduced. The Information Management System (IMS) is the EOSDIS element that provides the primary interface between the science users and the data products and services of EOSDIS. The goals of IMS are to define a clear and complete set of functional requirements and to apply innovative methods and technologies to satisfy them. The information management functions are described in detail, and some applicable technolgies are discussed. Some of the general issues affecting the successful development and operation of the information management element are addressed.

Mcdonald, Kenneth R.↗

NASA NTRS1997

Flight Test Safety Considerations for Airborne Science Aircraft

Most of the scientific community that require scientific data or scientific measurements from aircraft do not understand the full implications of putting certain equipment on board high performance aircraft. It is the duty of the NASA Flight Operations personnel to ensure that all Principal Investigators who are given space on NASA flight research aircraft, comply with stringent safety requirements. The attitude of the experienced Flight operations personnel given this duty has been and remains one of insuring that the PI's experiment is allowed to be placed on the aircraft (facility) and can be operated in a manner that will obtain the expected data. This is sometimes a challenge. The success that NASA has in this regard is due to the fact that it is its own authority under public law, to certify its aircraft as airworthy. Airworthiness, fitness for flight, is a complex issue which pulls together all aspects of configuration management, engineering, quality, and flight safety. It is often the case at each NASA Center that is conducting airborne research, that unique solutions to some challenging safety issues are required. These solutions permit NASA to do things that would not be permitted by the Department of Transportation. This paper will use examples of various flight research configurations to show the necessity of a disciplined process leading up to flight test and mission implementation. All new configurations required engineering flight test but many, as noted in this paper, require that the modifications be flight tested to insure that they do not negatively impact on any part of the aircraft operational profiles. The success of these processes has been demonstrated over many years and NASA has accommodated experimental packages that cannot be flown on any other aircraft.

Reynolds, Randolph S.↗

NASA NTRS2017

Autonomous, Context-Sensitive, Task Management Systems and Decision Support Tools II: Contextual Constraints and Information Sources

Recent advances in artificial intelligence, machine learning, data mining and sensor technology have resulted in the availability of a vast amount of digital data and information and the development of advanced automated reasoners. This creates the opportunity for the development of a robust dynamic task manager and decision support tool that is context sensitive and integrates information from a wide array of on-board and off aircraft sourcesa tool that monitors systems and the overall flight situation, anticipates information needs, prioritizes tasks appropriately, keeps pilots well informed, and is nimble and able to adapt to changing circumstances. This is the second of two companion reports exploring issues associated with autonomous, context-sensitive, task management and decision support tools. In the first report, we explored fundamental issues associated with the development of such a system. In this report, we extend this work to focus on two critical aspects of these systems: 1) the constraints and conditions that drive the dynamic prioritization and presentation of data and information to the pilots, and 2) specific data and information to be accessed, monitored, integrated, and displayed in such a system.

context-sensitive↗

NASA NTRS2018

Evaluation of Usability and Workload with Paper Strips as Compared to Virtual Flight Strips Used for Ramp Operations

This paper describes an experiment designed to compare the use of paper strips with the use of a new user interface, the Ramp Traffic Console (RTC), designed for use by ramp controllers to be used in place of paper strips. A Human-In-the-Loop (HITL) experiment was performed as the fifth study in a series of six HITL simulation experiments designed to evaluate a concept that provided advisories to the users. The RTC was designed to be used as a Decision Support Tool (DST) that provided advisories to ramp controllers regarding metering or pushback such that most of the delay was taken at the gate to save fuel and emissions. In addition to being a DST, an added benefit of the RTC is that it can provide real-time updates of flight data, airport and airspace status to the controller including Traffic Management Initiatives (TMI). The RTC was designed as new user interface that displays virtual strips on a terminal map drawn on a 27-inch touch screen monitor. The RTC was used in some conditions of the experiment by ramp controllers in place of paper strips and paper maps in the HITL environment. In other conditions the controllers were given paper strips and paper maps similar to what they currently use at Charlotte Douglas International Airport (CLT). The study described here, evaluated the use of the virtual strips displayed on the RTC as compared to the use of paper strips and paper map, using current ramp tower controllers at CLT as participants. The research question being asked was - How does management of ramp traffic affect user workload and usability ratings while using RTC to manage traffic in the ramp verses using paper strips? Workload for our purposes is defined by four components of the NASA-TLX (Task Load Index). Usability was assessed with two sets of usability questions - One set of usability questions addressed traffic management performance and the other set addressed issues of resources and efficiency. Both Post Run and Post Study questionnaire responses were gathered and the results were analyzed to assess controller workload and usability ratings under both conditions, virtual strips shown on RTC and Paper Strips. The results indicate that controllers perceived lower workload while using virtual strips displayed on RTC to manage ramp traffic. Usability ratings for Traffic management performance questions are lower in the virtual strip/RTC condition than in the paper strip condition showing a preference for RTC over Paper. Usability ratings for Resources and efficiency questions show mixed results. Additionally, the Post Study Questions show preference for RTC over paper strips. Results of this data analysis will be presented in this paper. This DST evaluation was an important step in researching and improving the tool, which was planned to be deployed in the field.

Aviation Decision Support Tools↗

NASA NTRS2008

Current Issues in Human Spacecraft Thermal Control Technology

Efficient thermal management of Earth-orbiting human spacecraft, lunar transit spacecraft and landers, as well as a lunar habitat will require advanced thermal technology. These future spacecraft will require more sophisticated thermal control systems that can dissipate or reject greater heat loads at higher input heat fluxes while using fewer of the limited spacecraft mass, volume and power resources. The thermal control designs also must accommodate the harsh environments associated with these missions including dust and high sink temperatures. The lunar environment presents several challenges to the design and operation of active thermal control systems. During the Apollo program, landings were located and timed to occur at lunar twilight, resulting in a benign thermal environment. The long duration polar lunar bases that are foreseen in 15 years will see extremely cold thermal environments. Long sojourns remote from low-Earth orbit will require lightweight, but robust and reliable systems. Innovative thermal management components and systems are needed to accomplish the rejection of heat from lunar bases. Advances are required in the general areas of radiators, thermal control loops and equipment. Radiators on the Moon's poles must operate and survive in very cold environments. Also, the dusty environment of an active lunar base may require dust mitigation and removal techniques to maintain radiator performance over the long term.

Ungar, Eugene K.↗

NASA NTRS2002

Space Debris: Its Causes and Management

Orbital debris is internationally recognized as an environmental issue which needs to be addressed today to preserve near-Earth space for future generations. All major space agencies are committed to mitigating the growth of the debris environment. Many commercial space system operators have responded positively to orbital debris mitigation principles and recommendations. Orbital debris mitigation measures are most cost-effective if included in the design development phase.

Johnson, Nicholas L.↗

NASA NTRS2009

Ares I-X Roll Control System Development

Project Managers often face challenging technical, schedule and budget issues. This presentation will explore how the Ares I-X Roll Control System Integrated Product Team (IPT) mitigated challenges such as concurrent engineering requirements and environments and evolving program processes, while successfully managing an aggressive project schedule and tight budget. IPT challenges also included communications and negotiations among inter- and intra-government agencies, including the US Air Force, NASA/MSFC Propulsion Engineering, LaRC, GRC, KSC, WSTF, and the Constellation Program. In order to successfully meet these challenges it was essential that the IPT define those items that most affected the schedule critical path, define early mitigation strategies to reduce technical, schedule, and budget risks, and maintain the end-product focus of an "unmanned test flight" context for the flight hardware. The makeup of the IPT and how it would function were also important considerations. The IPT consisted of NASA/MSFC (project management, engineering, and safety/quality) and contractors (Teledyne Brown Engineering and Pratt and Whitney Rocketdyne, who supplied heritage hardware experience). The early decision to have a small focused IPT working "badgelessly" across functional lines to eliminate functional stove-piping allowed for many more tasks to be done by fewer people. It also enhanced a sense of ownership of the products, while still being able to revert back to traditional roles in order to provide the required technical independence in design reviews and verification closures. This presentation will highlight several prominent issues and discuss how they were mitigated and the resulting Lessons Learned that might benefit other projects.

Unger, Ronald J.↗

NASA NTRS2017

Work Term Assignment Spring 2017

My tour in the Engineering Robotics directorate exceeded my expectations. I learned lessons about Creo, manufacturing and assembly, collaboration, and troubleshooting. During my first tour, last spring, I used Creo on a smaller project, but had limited experience with it before starting in the Dynamic Systems Test branch this spring. I gained valuable experience learning assembly design, sheet metal design and designing with intent for manufacturing and assembly. These skills came from working both on the hatch and the floor. I also learned to understand the intent of other designers on models I worked with. While redesigning the floor, I was modifying an existing part and worked to understand what the previous designer had done to make it fit with the new model. Through working with the machine shop and in the mock-up, I learned much more about manufacturing and assembly. I used a Dremel, rivet gun, belt sander, and countersink for the first time. Through taking multiple safety training for different machine shops, I learned new machine shop safety skills specific to each one. This semester also gave me new collaborative opportunities. I collaborated with engineers within my branch as well as with Human Factors and the building 10 machine shop. This experience helped me learn how to design for functionality and assembly, not only for what would be easiest in my designs. In addition to these experiences, I learned many lessons in troubleshooting. I was the first person in my office to use a Windows 10 computer. This caused unexpected issues with NASA services and programs, such as the Digital Data Management Server (DDMS). Because of this, I gained experience finding solutions to lockout and freeze issues as well as Creo specific settings. These will be useful skills to have in the future and will be implemented in future rotations. This co-op tour has motivated me more to finish my degree and pursue my academic goals. I intend to take a machining Career Gateway Elective in the Fall to improve my skills in building as well as designing with manufacturing intent. I am also inspired to take more mechatronics CGE courses before I graduate to learn more about the crossover between mechanical and electrical engineering. This semester, I worked on multiple projects and had the opportunity to learn from engineers of different disciplines. I became proficient in Creo 2.0, a program I had not used significantly before. I finished modifying the hatch for 3D print and made sizeable modifications to the nose floor support design. I also gained hands-on experience that will be useful in my engineering career in the future. I would consider all of these major achievements from this spring semester. Lastly, I learned to ask more questions and to search for the right people to find answers which I know will be a valuable skill in the future. This summer, I will be completing my last rotation in the Flight Operations Directorate at Ellington Air Field. After this last tour, I will be returning to school for the Fall, Spring and Summer. I will graduate in August of 2018. I am looking forward to learning more about the different jobs available to engineers. This division works directly with many different types of aircrafts and I am excited to learn more about this focus of engineering. The Aircraft Operations Division values team work greatly and I intend to improve my interpersonal skills by working with them this summer.

Sico, Mallory↗

NASA NTRS2018

Mobile Device Application for Monitoring Cyanobacteria Harmful Algal Blooms Using Sentinel-3 Satellite Ocean and Land Colour Instruments

Cyanobacterial harmful algal blooms (cyanoHAB) cause human and ecological health problems in lakes worldwide. The timely distribution of satellite-derived cyanoHAB data is necessary for adaptive water quality management and for targeted deployment of water quality monitoring resources. Software platforms that permit timely, useful, and cost-effective delivery of information from satellites are required to help managers respond to cyanoHABs. The Cyanobacteria Assessment Network (CyAN) mobile device application (app) uses data from the European Space Agency Copernicus Sentinel-3 satellite Ocean and Land Colour Instrument (OLCI) in near real-time to make initial water quality assessments and quickly alert managers to potential problems and emerging threats related to cyanobacteria. App functionality and satellite data were validated with 25 state health advisories issued in 2017. The CyAN app provides water quality managers with a user-friendly platform that reduces the complexities associated with accessing satellite data to allow fast, efficient, initial assessments across lakes.

Harmful Algal Bloom↗

NASA NTRS2003

Case Study of "Engineering Peer Meetings" in JPL's ST-6 Project

This design process error-proofing case study describes a design review practice implemented by a project manager at NASA Jet Propulsion Laboratory. There are many types of reviews at NASA: required and not, formalized and informal, programmatic and technical. Standing project formal reviews such as the Preliminary Design Review (PDR) and Critical Design Review (CDR) are a required part of every project and mission development. However, the engineering peer reviews that support teams technical work on such projects are often informal, ad hoc, and inconsistent across the organization. This case study discusses issues and innovations identified by a project manager at JPL and implemented in "engineering peer meetings" for his group.

Tumer, Irem Y.↗

NASA NTRS2004

Case Study of 'Engineering Peer Meetings' in JPL's ST-6 Project

Chao, Lawrence P.↗

NASA NTRS2017

Contamination Mitigation Strategies for Long Duration Human Spaceflight Missions

Contamination control issues are particularly challenging for long-term human spaceflight and are associated with the search for life, dynamic environmental conditions, human-robotic-environment interaction, sample collection and return, biological processes, waste management, long-term environmental disturbance, etc. These issues impact mission success, human health, planetary protection, and research and discovery. Mitigation and control techniques and strategies may include and integrate long-term environmental monitoring and reporting, contamination control and planetary protection protocols, habitation site design, habitat design, and surface exploration and traverse pathways and area access planning.

enviroment↗

NASA NTRS2013

Flight-Deck Strategies and Outcomes When Flying Schedule-Matching Descents

Recent studies at NASA Ames Research Center have investigated the development and use of ground-based (air traffic controller) tools to manage and schedule air traffic in future terminal airspace. An exploratory study was undertaken to investigate the impacts that such tools (and concepts) could have on the flight-deck. Ten Boeing 747-400 crews flew eight optimized profile descents in the Los Angeles terminal airspace, while receiving scripted current day and futuristic speed clearances, to ascertain their ability to fly schedulematching descents without prior training. Although the study was exploratory in nature, four variables were manipulated: route constraints, winds, speed changes, and clearance phraseology. Despite flying the same scenarios with the same events and timing, there were significant differences in the time it took crews to fly the approaches. This variation is the product of a number of factors but highlights potential difficulties for scheduling tools that would have to accommodate this amount of natural variation in descent times. The focus of this paper is the examination of the crews' aircraft management strategies and outcomes. This includes potentially problematic human-automation interaction issues that may negatively impact arrival times, speed and altitude constraint compliance, and energy management efficiency.

Flight Management System↗

NASA NTRS2014

Data Preservation, Information Preservation, and Lifecyle of Information Management at NASA GES DISC

Data lifecycle management awareness is common today; planners are more likely to consider lifecycle issues at mission start. NASA remote sensing missions are typically subject to life cycle management plans of the Distributed Active Archive Center (DAAC), and NASA invests in these national centers for the long-term safeguarding and benefit of future generations. As stewards of older missions, it is incumbent upon us to ensure that a comprehensive enough set of information is being preserved to prevent the risk for information loss. This risk is greater when the original data experts have moved on or are no longer available. Preservation of items like documentation related to processing algorithms, pre-flight calibration data, or input-output configuration parameters used in product generation, are examples of digital artifacts that are sometimes not fully preserved. This is the grey area of information preservation; the importance of these items is not always clear and requires careful consideration. Missing important metadata about intermediate steps used to derive a product could lead to serious challenges in the reproducibility of results or conclusions. Organizations are rapidly recognizing that the focus of life-cycle preservation needs to be enlarged from the strict raw data to the more encompassing arena of information lifecycle management. By understanding what constitutes information, and the complexities involved, we are better equipped to deliver longer lasting value about the original data and derived knowledge (information) from them. The NASA Earth Science Data Preservation Content Specification is an attempt to define the content necessary for long-term preservation. It requires new lifecycle infrastructure approach along with content repositories to accommodate artifacts other than just raw data. The NASA Goddard Earth Sciences Data and Information Services Center (GES DISC) setup an open-source Preservation System capable of long-term archive of digital content to augment its raw data holding. This repository is being used for such missions as HIRDLS, UARS, TOMS, OMI, among others. We will provide a status of this implementation; report on challenges, lessons learned, and detail our plans for future evolution to include other missions and services.

data management↗

NASA NTRS2014

A Multifaceted Approach to Modernizing NASA's Advanced Multi-Mission Operations System (AMMOS) System Architecture

The Advanced Multi-Mission Operations Systems (AMMOS) is NASA's premier space mission operations product line offering for use in deep-space robotic and astrophysics missions. The general approach to AMMOS modernization over the course of its 29-year history exemplifies a continual, evolutionary approach with periods of sponsor investment peaks and valleys in between. Today, the Multimission Ground Systems and Services (MGSS) office-the program office that manages the AMMOS for NASA-actively pursues modernization initiatives and continues to evolve the AMMOS by incorporating enhanced capabilities and newer technologies into its end-user tool and service offerings. Despite the myriad of modernization investments that have been made over the evolutionary course of the AMMOS, pain points remain. These pain points, based on interviews with numerous flight project mission operations personnel, can be classified principally into two major categories: 1) information-related issues, and 2) process-related issues. By information-related issues, we mean pain points associated with the management and flow of MOS data across the various system interfaces. By process-related issues, we mean pain points associated with the MOS activities performed by mission operators (i.e., humans) and supporting software infrastructure used in support of those activities. In this paper, three foundational concepts-Timeline, Closed Loop Control, and Separation of Concerns-collectively form the basis for expressing a set of core architectural tenets that provides a multifaceted approach to AMMOS system architecture modernization intended to address the information- and process-related issues. Each of these architectural tenets will be further explored in this paper. Ultimately, we envision the application of these core tenets resulting in a unified vision of a future-state architecture for the AMMOS-one that is intended to result in a highly adaptable, highly efficient, and highly cost-effective set of multimission MOS products and services.

Estefan, Jeff A.↗

NASA NTRS1993

Intelligent systems and advanced user interfaces for design, operation, and maintenance of command management systems

Historically, command management systems (CMS) have been large and expensive spacecraft-specific software systems that were costly to build, operate, and maintain. Current and emerging hardware, software, and user interface technologies may offer an opportunity to facilitate the initial formulation and design of a spacecraft-specific CMS as well as to develop a more generic CMS system. New technologies, in addition to a core CMS common to a range of spacecraft, may facilitate the training and enhance the efficiency of CMS operations. Current mission operations center (MOC) hardware and software include Unix workstations, the C/C++ programming languages, and an X window interface. This configuration provides the power and flexibility to support sophisticated and intelligent user interfaces that exploit state-of-the-art technologies in human-machine interaction, artificial intelligence, and software engineering. One of the goals of this research is to explore the extent to which technologies developed in the research laboratory can be productively applied in a complex system such as spacecraft command management. Initial examination of some of these issues in CMS design and operation suggests that application of technologies such as intelligent planning, case-based reasoning, human-machine systems design and analysis tools (e.g., operator and designer models), and human-computer interaction tools (e.g., graphics, visualization, and animation) may provide significant savings in the design, operation, and maintenance of the CMS for a specific spacecraft as well as continuity for CMS design and development across spacecraft. The first six months of this research saw a broad investigation by Georgia Tech researchers into the function, design, and operation of current and planned command management systems at Goddard Space Flight Center. As the first step, the researchers attempted to understand the current and anticipated horizons of command management systems at Goddard. Preliminary results are given on CMS commonalities and causes of low re-use, and methods are proposed to facilitate increased re-use.

Potter, William J.↗

NASA NTRS1987

NASA Uniform Files Index

This handbook is a guide for the use of all personnel engaged in handling NASA files. It is issued in accordance with the regulations of the National Archives and Records Administration, in the Code of Federal Regulations Title 36, Part 1224, Files Management; and the Federal Information Resources Management Regulation, Subpart 201-45.108, Files Management. It is intended to provide a standardized classification and filing scheme to achieve maximum uniformity and ease in maintaining and using agency records. It is a framework for consistent organization of information in an arrangement that will be useful to current and future researchers. The NASA Uniform Files Index coding structure is composed of the subject classification table used for NASA management directives and the subject groups in the NASA scientific and technical information system. It is designed to correlate files throughout NASA and it is anticipated that it may be useful with automated filing systems. It is expected that in the conversion of current files to this arrangement it will be necessary to add tertiary subjects and make further subdivisions under the existing categories. Established primary and secondary subject categories may not be changed arbitrarily. Proposals for additional subject categories of NASA-wide applicability, and suggestions for improvement in this handbook, should be addressed to the Records Program Manager at the pertinent installation who will forward it to the NASA Records Management Office, Code NTR, for approval. This handbook is issued in loose-leaf form and will be revised by page changes.

Source record↗