Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “work 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 397 records · Page 22
All sourcesNASA NTRSDOE OSTI
NASA NTRS1999

Spacecraft Software Maintenance: An Effective Approach to Reducing Costs and Increasing Science Return

Flight software is a mission critical element of spacecraft functionality and performance. When ground operations personnel interface to a spacecraft, they are typically dealing almost entirely with the capabilities of onboard software. This software, even more than critical ground/flight communications systems, is expected to perform perfectly during all phases of spacecraft life. Due to the fact that it can be reprogrammed on-orbit to accommodate degradations or failures in flight hardware, new insights into spacecraft characteristics, new control options which permit enhanced science options, etc., the on- orbit flight software maintenance team is usually significantly responsible for the long term success of a science mission. Failure of flight software to perform as needed can result in very expensive operations work-around costs and lost science opportunities. There are three basic approaches to maintaining spacecraft software--namely using the original developers, using the mission operations personnel, or assembling a center of excellence for multi-spacecraft software maintenance. Not planning properly for flight software maintenance can lead to unnecessarily high on-orbit costs and/or unacceptably long delays, or errors, in patch installations. A common approach for flight software maintenance is to access the original development staff. The argument for utilizing the development staff is that the people who developed the software will be the best people to modify the software on-orbit. However, it can quickly becomes a challenge to obtain the services of these key people. They may no longer be available to the organization. They may have a more urgent job to perform, quite likely on another project under different project management. If they havn't worked on the software for a long time, they may need precious time for refamiliarization to the software, testbeds and tools. Further, a lack of insight into issues related to flight software in its on-orbit environment, may find the developer unprepared for the challenges. The second approach is to train a member of the flight operations team to maintain the spacecraft software. This can prove to be a costly and inflexible solution. The person assigned to this duty may not have enough work to do during a problem free period and may have too much to do when a problem arises. If the person is a talented software engineer, he/she may not enjoy the limited software opportunities available in this position; and may eventually leave for newer technology computer science opportunities. Training replacement flight software personnel can be a difficult and lengthy process. The third approach is to assemble a center of excellence for on-orbit spacecraft software maintenance. Personnel in this specialty center can be managed to support flight software of multiple missions at once. The variety of challenges among a set of on-orbit missions, can result in a dedicated, talented staff which is fully trained and available to support each mission's needs. Such staff are not software developers but are rather spacecraft software systems engineers. The cost to any one mission is extremely low because the software staff works and charges, minimally on missions with no current operations issues; and their professional insight into on-orbit software troubleshooting and maintenance methods ensures low risk, effective and minimal-cost solutions to on-orbit issues.

Shell, Elaine M.↗
NASA NTRSDate not supplied

A Model-Based Systems Engineering Evaluation of the Evolution to an In-Time Aviation Safety Management System

In 2018, as result of a recommendation from the National Academies, NASA began to prototype an In-Time Aviation Safety Management System (IASMS). The purpose of the IASMS is to enable innovative aviation operations and greater heterogeneity of the overall National Airspace (NAS) by automating much of the safety monitoring, assessment, and risk and hazard mitigation function present in today’s Safety Management Systems (SMS). NASA has worked together with early industry collaborators to understand how such a system might work and has published several early Concepts of Operation (ConOps) and other technical memoranda that illustrate the primary considerations for selected aviation domains. The shift from an SMS to an IASMS is predicated on several assumptions, including: 1.) automating safety functions will decrease the amount of time necessary for risk and hazard identification and analysis, making it more likely that safety concerns are understood ‘in-time’ to mitigate them, and 2.) an IASMS will allow easier tailoring of safety management processes to the particular risks and hazards inherent to that aviation operation. In this paper, we begin to validate these assumptions through the use of Model-Based Systems Engineering (MBSE).

IASMS↗
NASA NTRSDate not supplied

A Model-Based Systems Engineering Evaluation of the Evolution to an In-Time Aviation Safety Management System

In 2018, as result of a recommendation from the National Academies, NASA began to prototype an In-Time Aviation Safety Management System(IASMS). The purpose of the IASMS is to enable innovative aviation operations and greater heterogeneity of the overall National Airspace (NAS) by automating much of the safety monitoring, assessment, and risk and hazard mitigation functionspresent in today’s Safety Management Systems (SMS). NASA has worked together with early industry collaborators to understand how such a system might work and has published several early Concepts of Operation (ConOps) and other technical memoranda that illustrate the primary considerations for selected aviation domains. The shift from an SMS to an IASMS is predicated on several assumptions, including: 1.) automating safety functions will decrease the amount of time necessary for risk and hazard identification and analysis, making it more likely that safety concerns are understood ‘in-time’ to mitigate them, and 2.) an IASMS will allow easier tailoring of safety management processes to the particular risks and hazards inherent to that aviation operation. In this paper, we begin to validate these assumptions through the use of Model-Based Systems Engineering (MBSE).

In-time Aviation Safety Management System↗
NASA NTRS2011

Flexible Airspace Management (FAM) Research 2010 Human-in-the-Loop Simulation

A human-in-the-Ioop (HITL) simulation was conducted to assess potential user and system benefits of Flexible Airspace Management (FAM) concept, as well as designing role definitions, procedures, and tools to support the FAM operations in the mid-term High Altitude Airspace (HAA) environment. The study evaluated the benefits and feasibility of flexible airspace reconfiguration in response to traffic overload caused by weather deviations, and compared them to those in a baseline condition without the airspace reconfiguration. The test airspace consisted of either four sectors in one Area of Specialization or seven sectors across two Areas. The test airspace was assumed to be at or above FL340 and fully equipped Vvith data communications (Data Comm). Other assumptions were consistent with those of the HAA concept. Overall, results showed that FAM operations with multiple Traffic Management Coordinators, Area Supervisors, and controllers worked remarkably well. The results showed both user and system benefits, some of which include the increased throughput, decreased flight distance, more manageable sector loads, and better utilized airspace. Also, the roles, procedures, airspace designs, and tools were all very well received. Airspace configuration options that resulted from a combination of algorithm-generated airspace configurations with manual modifications were well acceptec and posed little difficuIty and/or workload during airspace reconfiguration process. The results suggest a positive impact of FAM operations in HAA. Further investigation would be needed to evaluate if the benefits and feasibility would extend in either non-HAA or mixed equipage environment.

Lee, Paul U.↗
NASA NTRS1991

Space transfer vehicle concepts and requirements study. Volume 3: Program cost estimates. Book 2: WBS and dictionary

This document describes the products and services to be developed, tested, produced, and operated for the Space Transfer Vehicle (STV) Program. The Work Breakdown Structure (WBS) and WBS Dictionary are program management tools used to catalog, account by task, and summarize work packages of a space system program. The products or services to be delivered or accomplished during the STV C/D phase are the primary focus of this work breakdown structure document.

Peffley, A. F.↗
NASA NTRS1993

Space Station Freedom (SSF) Data Management System (DMS) performance model data base

The purpose of this document was originally to be a working document summarizing Space Station Freedom (SSF) Data Management System (DMS) hardware and software design, configuration, performance and estimated loading data from a myriad of source documents such that the parameters provided could be used to build a dynamic performance model of the DMS. The document is published at this time as a close-out of the DMS performance modeling effort resulting from the Clinton Administration mandated Space Station Redesign. The DMS as documented in this report is no longer a part of the redesigned Space Station. The performance modeling effort was a joint undertaking between the National Aeronautics and Space Administration (NASA) Johnson Space Center (JSC) Flight Data Systems Division (FDSD) and the NASA Ames Research Center (ARC) Spacecraft Data Systems Research Branch. The scope of this document is limited to the DMS core network through the Man Tended Configuration (MTC) as it existed prior to the 1993 Clinton Administration mandated Space Station Redesign. Data is provided for the Standard Data Processors (SDP's), Multiplexer/Demultiplexers (MDM's) and Mass Storage Units (MSU's). Planned future releases would have added the additional hardware and software descriptions needed to describe the complete DMS. Performance and loading data through the Permanent Manned Configuration (PMC) was to have been included as it became available. No future releases of this document are presently planned pending completion of the present Space Station Redesign activities and task reassessment.

Stovall, John R.↗
NASA NTRS1971

MAPS - a computerized management analysis and planning system

Program lists work structure of projects at all levels. System integrates work item, its schedule, its status against the schedule, responsible personnel, and explanatory comments. structure of MAPS promotes natural organization of project work elements, project features and uses are given.

Packe, D. R.↗
NASA NTRS2011

NASA Goddard Space Flight Center Supply Chain Management Program

This slide presentation reviews the working of the Supplier Assessment Program at NASA Goddard Space Flight Center. The program supports many GSFC projects to ensure suppliers are aware of and are following the contractual requirements, to provide an independent assessment of the suppliers' processes, and provide suppliers' safety and mission assurance organizations information to make the changes within their organization.

Kelly, Michael P.↗
NASA NTRS2019

Magnet Architectures and Active Radiation Shielding Study (MAARSS)

This report describes the analysis of several magnetic radiation shield architectures and the spacecraft systems associated with them, such as quench detection, thermal management, and compensation coils. This work was performed as part of the NASA Institute of Advanced Concepts (NIAC) Grant Phase II effort. Because radiation exposure during long duration space missions poses a significant risk for crewed space-flight, Advanced Magnetic Lab, Inc. (AML) and NASA are studying magnetic radiation shielding, which may generate low-mass protection. Recent technological developments in high-temperature superconducting technology suggest the possibility of such shielding. This report analyzes some of the technical difficulties involved in such a system and identifies technology areas where further investment would be warranted. Most analysis was performed on a baseline configuration (8-meter diameter coils, with 1 tesla field). However, a baseline design with an expandable coil configuration (16 meter diameter coils, 1.5 tesla field) has a significant potential to increase shielding efficiency. The magnetic forces on the magnetic shield's components are large enough to require detailed structural design. Analysis of the thermal structural response of a yttrium-barium-copper-oxide (YBCO) high-temperature, superconducting (HTS) tape in a large-scale solenoid magnet showed that structural and thermal performance improved by replacing Hastelloy® with graphene in the tape. Integrating graphene into the high-strength fiber (HSF) support structure brings even greater benefits. The energy stored in a shield system's magnetic field must be safely dissipated if a quench-type failure occurs. Analysis of quench detection by fiber-optic thermal sensing and improvement of quench characteristics using graphene showed quench is manageable. Low-temperature superconductors can quench when subjected to movement, but lab tests of coil expansion testing showed that HTS materials do not quench when subject to the movement associated with coil expansion. Compensation coils are necessary to reduce the magnetic field in the crew habitat. Analysis showed that subdividing the compensation coil into individually controlled sections allows for a robust, adjustable system. AML analyzed the forces on an approaching capsule that were a result of eddy currents in its structure induced by its motion through the magnetic field from the coils. AML also analyzed coil-to-coil forces. Thermal control to maintain the HTS material at a suitable temperature is challenging. The sunshield technology review revealed a greater possibility of thermal insulation of the coils and use of passive cooling. The availability of suitable cryocoolers was also reviewed. A parametric graph estimating mass and shielding effectiveness for strength and thickness was developed, and allows spacecraft designers to assess the tradeoffs of using a magnetic radiation shield.

Spacecraft↗
NASA NTRSDate not supplied

Connecting Federal Agencies to Satellite Earth Observations: NASA’s Satellite Needs Working Group Assessment Process

The Satellite Needs Working Group (SNWG), part of the U.S. Group on Earth Observations (USGEO), surveys agencies across the U.S. Government to identify the satellite Earth observations each agency needs to fulfill its high-priority objectives and responsibilities. Around 20 civilian agencies participate in the SNWG survey every two years. After receiving the surveys, the National Aeronautics and Space Administration (NASA) conducts an in-depth evaluation of each agency's needs in collaboration with fellow satellite Earth data providers, the National Oceanic and Atmospheric Administration (NOAA) and the U.S. Geological Survey (USGS). This assessment process, which takes place over an eight-month period, is divided into distinct phases. NASA first assembles an assessment team with the necessary subject matter expertise to evaluate each submitted need. An in-depth interview with each submitting agency then follows, featuring discussion of current and upcoming satellite missions as well as potential new activities that NASA, NOAA, and/or USGS could undertake to meet the agency's needs. The assessment teams then further evaluate these potential activities or solutions to identify how many agencies would benefit and estimate how much their level of satisfaction would increase. Solutions expected to have broad-reaching and significant agency benefits are proposed by NASA for funding. SNWG agencies receive an assessment report for each submitted need, in which the tri-agency assessment teams provide a detailed evaluation of the agency need, information on relevant satellite missions, and links to specific datasets or training resources. The SNWG Management Office at NASA’s Interagency Implementation and Advanced Concepts Team (IMPACT) contributes to NASA’s SNWG assessment in a variety of capacities, including statistical analysis of the survey responses to identify trends and similar needs across multiple agencies. The Management Office also provides analytics for the new proposed solutions, demonstrating and quantifying their potential value. For activities that receive funding, the Management Office manages the implementation process and works to maximize the benefit to SNWG agencies via a Stakeholder Engagement Program.

Katrina Virts↗
NASA NTRS2016

IDEAS and App Development Internship in Hardware and Software Design

In this report, I will discuss the tasks and projects I have completed while working as an electrical engineering intern during the spring semester of 2016 at NASA Kennedy Space Center. In the field of software development, I completed tasks for the G-O Caching Mobile App and the Asbestos Management Information System (AMIS) Web App. The G-O Caching Mobile App was written in HTML, CSS, and JavaScript on the Cordova framework, while the AMIS Web App is written in HTML, CSS, JavaScript, and C# on the AngularJS framework. My goals and objectives on these two projects were to produce an app with an eye-catching and intuitive User Interface (UI), which will attract more employees to participate; to produce a fully-tested, fully functional app which supports workforce engagement and exploration; to produce a fully-tested, fully functional web app that assists technicians working in asbestos management. I also worked in hardware development on the Integrated Display and Environmental Awareness System (IDEAS) wearable technology project. My tasks on this project were focused in PCB design and camera integration. My goals and objectives for this project were to successfully integrate fully functioning custom hardware extenders on the wearable technology headset to minimize the size of hardware on the smart glasses headset for maximum user comfort; to successfully integrate fully functioning camera onto the headset. By the end of this semester, I was able to successfully develop four extender boards to minimize hardware on the headset, and assisted in integrating a fully-functioning camera into the system.

CSS↗
NASA NTRS2017

To Meet or Not To Meet Physical vs. Virtual Configuration Control Board

This presentation will define the CCB, discuss its functions and members. We will look into traditional processes of managing change control via the CCB meeting and advanced practices utilizing enhanced product tools and technologies. Well step through a summary of the feedback from the community of CM professionals at NASA Goddard Space Flight Center of best practices as well as pros and cons for facilitating both a physical CCB and managing stakeholder approvals in a virtual environment. Attendees will come away with current industry strategies to determine if process for managing change control and approvals can be streamlined within their local work environments.

tools↗
NASA NTRS1986

Procedures and tools for building large Ada systems

Some of the problems unique to building a very large Ada system are addressed. This is done through examples from experience. In the winter of 1985 and 1986, Intermetrics bootstrapped the Ada compiler, which was being built over the last few years. This system consists of about one million lines of full Ada. Over the last few years a number of procedures and tools were adopted for managing the life cycle of each of the many parts of an Ada system. Many of these procedures are well known to most system builders: release management, quality assurance testing; and source file revision control. Others are unique to working in an Ada language environment; i.e., recompilation management, Ada program library management, and managing multiple implementations. First a look is taken at how a large Ada system is broken down into pieces. The Ada definition leaves unspecified a number of issues that the system builder must address: versions, subsystems, multiple implementations, and synchronization of branched development paths. Having introduced how the Ada systems are decomposed, a look is taken, via a series of examples, at how the life cylces of those parts is managed. The procedures and tools used to manage the evolution of the system are examined. It is hoped that other Ada system builders can build upon the experience of the last few years.

Hyde, Ben↗
NASA NTRS1987

Instructions to working groups

The key to the success of this workshop is your active participation in the working group process. The goals of this workshop are to address four major questions regarding Cockpit Resource Management (CRM) Training. To some extent the working group topic areas parallel these issues, but in some cases they do not. However, it is important for all of the working groups to keep these general questions in mind during their deliberations: (1) What are the essential elements of an optimal CRM Training program; (2) What are the strengths and weaknesses of current approaches to CRM Training; (3) How can CRM Training best be implemented, and what barriers exist; and (4) Is CRM Training effective, do we know, and if not, how can we find out.

Foushee, H. Clayton↗
NASA NTRS2004

Information Technology Support in the 8000 Directorate

My summer internship was spent supporting various projects within the Environmental Management Office and Glenn Safety Office. Mentored by Eli Abumeri, I was trained in areas of Information Technology such as: Servers, printers, scanners, CAD systems, Web, Programming, and Database Management, ODIN (networking, computers, and phones). I worked closely with the Chemical Sampling and Analysis Team (CSAT) to redesign a database to more efficiently manage and maintain data collected for the Drinking Water Program. This Program has been established for over fifteen years here at the Glenn Research Center. It involves the continued testing and retesting of all drinking water dispensers. The quality of the drinking water is of great importance and is determined by comparing the concentration of contaminants in the water with specifications set forth by the Environmental Protection Agency (EPA) in the Safe Drinking Water Act (SDWA) and its 1986 and 1991 amendments. The Drinking Water Program consists of periodic testing of all drinking water fountains and sinks. Each is tested at least once every 2 years for contaminants and naturally occurring species. The EPA's protocol is to collect an initial and a 5 minute draw from each dispenser. The 5 minute draw is what is used for the maximum contaminant level. However, the CS&AT has added a 30 second draw since most individuals do not run the water 5 minutes prior to drinking. This data is then entered into a relational Microsoft Access database. The database allows for the quick retrieval of any test@) done on any dispenser. The data can be queried by building number, date or test type, and test results are documented in an analytical report for employees to read. To aid with the tracking of recycled materials within the lab, my help was enlisted to create a database that could make this process less cumbersome and more efficient. The date of pickup, type of material, weight received, and unit cost per recyclable. This information could then calculate the dollar amount generated by the recycling of certain materials. This database will ultimately prove useful in determining the amounts of materials consumed by the lab and will help serve as an indicator potential overuse.

FROM↗
NASA NTRS1977

Modeling and Analysis of Power Processing Systems (MAPPS), initial phase 2

The overall objective of the program is to provide the engineering tools to reduce the analysis, design, and development effort, and thus the cost, in achieving the required performances for switching regulators and dc-dc converter systems. The program was both tutorial and application oriented. Various analytical methods were described in detail and supplemented with examples, and those with standardization appeals were reduced into computer-based subprograms. Major program efforts included those concerning small and large signal control-dependent performance analysis and simulation, control circuit design, power circuit design and optimization, system configuration study, and system performance simulation. Techniques including discrete time domain, conventional frequency domain, Lagrange multiplier, nonlinear programming, and control design synthesis were employed in these efforts. To enhance interactive conversation between the modeling and analysis subprograms and the user, a working prototype of the Data Management Program was also developed to facilitate expansion as future subprogram capabilities increase.

Yu, Y.↗
NASA NTRS1978

Space power for space

The total energy demanded by space missions of the future is expected to exceed past needs by orders of magnitude. The unit costs of this energy must be reduced from present levels if these missions are to be carried out at projected budget levels. The broad employment of electric propulsion and the capability to utilize novel high power sensors hinge on the availability of systems lighter by factors of ten or more than have flown to date. The NASA program aimed at providing the technological basis to meet these demands is described in this paper. Research and technology efforts in areas of energy conversion, storage and management are covered. In addition, work aimed at evolving the understanding necessary to cope with space environment interactions and at advanced concepts is described.

Mullin, J. P.↗