Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “program managers”

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

Use of Historical EM Practices and Policies for Management of Cleanup Program and Address GAO Concerns - 20222

As Department of Energy (DOE) Environmental Management (EM) program policies and management practices are revised over time, it might be useful to periodically reflect on the DOE EM program's past to identify practices that have worked and those that might be appropriate for possible reuse in the future. An added impetus to examine alternative approaches is the recent Government Accountability Office (GAO) report entitled 'Nuclear Waste Cleanup - DOE Could Improve Program and Project Management by Better Classifying Work and Following Leading Practices.' The February 2019 GAO report states that EM categorizes most of its work in a way that does not adequately involve independent experts and DOE senior leadership. It also noted that EM has not followed leading practices for program and project management that could help keep the cleanup efforts on schedule and control costs. The GAO report recommended that EM, working with DOE Office of Project Management (PM): - Establish requirements and then assess EM's ongoing operations activities to determine if some activities should be reclassified as capital asset projects based on these newly established requirements. - Review and revise EM's 2017 cleanup policy to include program management leading practices related to scope, cost, schedule performance, and independent reviews. - Update the cleanup policy to require that earned value management (EVM) systems be maintained and used in a way that follows EVM best practices. - Develop a policy to ensure that work is categorized as level of effort (LOE) only in appropriate, specified circumstances, such as when work is not measurable or when measurement is impractical. - Integrate EVM data into EM's performance metrics for operations activities. To assist with improving program performance and implementing audit recommendations, this paper reviewed past successful cleanups such as Weldon Springs, Rocky Flats, Fernald, Ashtabula, Battelle Columbus (abs, and other historical resources and people with experience during the early years of EM program. As such, there are several past practices which may well be suited for reuse today. Some of these practices include: - In 1990's, as the DOE EM cleanup program, known as Environmental Restoration came into effect, the known cleanup scope at each geographic location or site was organized into four levels ranging from overall site-wide cleanup effort to the individual 'release sites', providing high granularity to the program. - The cleanup program was organized by geography (Northwest, Southwest, Eastern Area Programs, etc.). These 'sub-program' managers provided a degree of Headquarters oversight and management allowing upper management (EM-1, 2, and 3) to focus on major decisions and issues. - Budget levels at selected cleanup sites were funded above 'minimum-safety' levels to accelerate actual cleanup work. - Past practice utilized EVM techniques and uniform EM oversight over all discrete project-like activities, providing for a coordinated cleanup effort. - EM managed LOE activities using benchmarking and best in class management practice techniques to help manage costs. - EM managed and reviewed entire site cleanup baselines, not only individual projects, focusing on a successful overall outcome. - Sites had a 'Road map' or 'Management Action Plan' that provided the overall strategy or plan for that site's cleanup - this helped with understanding and coordination of efforts. - EM had a robust lessons-learned program and database to capture and transmit worthy ideas. - EM had well-structured cleanup baseline change control policies to control cost and schedule changes, at the contractor and higher Headquarters levels. Finally, some of the GAO observations may be valid, however it is not clear as to their extent. For example, for some operation types of work, the use of the Level of Effort (LOE) earned value method to track progress may be appropriate. Also, to ensure independence of thought, and to obtain useful insight on past practices, it may be suitable to have former EM employees to assist with understanding past practices or to verify that activities have been properly identified. (authors)

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗

Issues in NASA Program and Project Management. Special Edition: A Collection of Papers on NASA Procedures and Guidance 7120.5A

A key aspect of NASA's new Strategic Management System is improving the way we plan, approve, execute and evaluate our programs and projects. To this end, NASA has developed the NASA Program and Project Management processes and Requirements-NASA Procedures and Guidelines (NPG) 7120.5A, which formally documents the "Provide Aerospace Products and Capabilities" crosscutting process, and defines the processes and requirements that are responsive to the Program/Project Management-NPD 7120.4A. The Program/Project Management-NPD 7120.4A, issued November 14, 1996, provides the policy for managing programs and projects in a new way that is aligned with the new NASA environment. An Agencywide team has spent thousands of hours developing the NASA Program and Project Management Processes and Requirements-NPG 7120.5A. We have created significant flexibility, authority and discretion for the program and project managers to exercise and carry out their duties, and have delegated the responsibility and the accountability for their programs and projects.

Edward J. Hoffman↗

Guidelines for development of NASA (National Aeronautics and Space Administration) computer security training programs

The report presents guidance for the NASA Computer Security Program Manager and the NASA Center Computer Security Officials as they develop training requirements and implement computer security training programs. NASA audiences are categorized based on the computer security knowledge required to accomplish identified job functions. Training requirements, in terms of training subject areas, are presented for both computer security program management personnel and computer resource providers and users. Sources of computer security training are identified.

Tompkins, F. G.↗

Advanced program development management software system. Software description and user's manual

The objectives of this project were to apply emerging techniques and tools from the computer science discipline of paperless management to the activities of the Space Transportation and Exploration Office (PT01) in Marshall Space Flight Center (MSFC) Program Development, thereby enhancing the productivity of the workforce, the quality of the data products, and the collection, dissemination, and storage of information. The approach used to accomplish the objectives emphasized the utilization of finished form (off-the-shelf) software products to the greatest extent possible without impacting the performance of the end product, to pursue developments when necessary in the rapid prototyping environment to provide a mechanism for frequent feedback from the users, and to provide a full range of user support functions during the development process to promote testing of the software.

Source record↗

Global Temperature and Salinity Pilot Project

Data exchange and data management programs have been evolving over many years. Within the international community there are two main programs to support the exchange, management and processing of real time and delayed mode data. The Intergovernmental Oceanographic Commission (IOC) operate the International Oceanographic Data and Information Exchange (IODE) program which coordinates the exchange of delayed mode data between national oceanographic data centers, World Data Centers and the user community. The Integrated Global Ocean Services System is a joint IOC/World Meteorological Organization (WMO) program for the exchange and management of real-time data. These two programs are complemented by mechanisms that have been established within scientific programs to exchange and manage project data sets. In particular TOGA and WOCE have identified a data management requirement and established the appropriate infrastructure to achieve this. Where GTSPP fits into this existing framework is discussed.

Searle, Ben↗

LeRC reduced gravity fluid management technology program

The program reviewed in the present paper has provided information of the reduced-gravity behavior of fluids, thermal control of cryogenic tankage, and fluid management system design. The studies are currently shifting from the utilization of in-house experimental facilities to the development of Spacelab experiments. The cryogenic fluid management experiment, currently undergoing detailed design, is expected to provide an orbital evaluation of a subcritical liquid hydrogen storage and supply system, as part of the Shuttle/Spacelab program. Efforts are continuing to develop computer techniques for simulating reduced-gravity fluid dynamic processes.

Aydelott, J. C.↗

Determinants of enrollment in public incentive programs for forest management and their effect on future programs for woody bioenergy: evidence from Virginia and Texas

Several federal- and state-sponsored programs, including cost-sharing arrangements, tax incentives, and technical assistance programs, are available to forestland owners, aiming to encourage desired forest management practices and outcomes. However, enrollment rates in such programs are low, and trends of forestland parcelization hint at an even smaller enrollment rate in the future. Therefore, it is important to understand how socioeconomic attributes of forestland owners and past experience with such programs affect the likelihood of enrollment in public incentive programs. Among others, this will help us provide tailored information to forestland owners who are less likely to use these opportunities through extension and outreach programs. Towards this end, we conducted a survey of 1800 forestland owners in Virginia and Texas. Our recursive partitioning, logistic regression, and Cochran–Armitage trend test results suggest that forestland owners who are less likely to enroll in such programs have relatively smaller forestland acreage, a lower level of education, and shorter land ownership tenure. We also find that forestland owners with experience in public incentive programs tend to attach higher importance to potential programs, including those that do not directly benefit them. Furthermore, we also identify threshold values for explanatory variables such as acreage and tenure length.

54 ENVIRONMENTAL SCIENCES↗

Human Systems Integration (HSI) Framework and Training - Shifting the View of HSI for Better Implementation

The Implementation of Human Systems Integration (HSI) presents challenges within the acquisition community for two reasons. The first is that misconceptions of HSI still exist, with many Program Managers (PMs) and leadership uncertain of the value or where to begin. The second is due to an unbalanced approach to HSI in its own framework. These implementation challenges lead to barriers in the early prevention of mishaps. Understanding HSI practices and how they should be implemented in the Acquisition Product Life Cycle (PLC) has been a challenge across the government, leaving the value of HSI unknown and misunderstood with Program Managers. In the case for many acquisition programs, HSI is not implemented in early design, losing the perspective on human capabilities and limitations, creating impacts on human-centered design. Expectations in human performance are not clearly set and operations are baselined with no margin for changes in technology and processes that will affect system performance. The HSI framework addresses total system performance holistically using collaboration as the primary tool. The goal is to create a system with efficiencies while minimizing risk to the operators, maintainers, and support personnel, as well as any collateral personnel and systems. To accomplish this, HSI should be implemented as part of preemptive measures to minimize potential human error and mishaps during the operation phase. Investigative and assessment tools exist that consider events, issues, and other outside influences of a system that may not fall under the current construct of the HSI domains, leaving gaps in early HSI implementation and affecting the prevention of human errors and mishaps. This presentation will outline what NASA HSI is doing to support Early HSI implementation and Operational Performance shifts that affect human performance.

Anthony T Thomas↗

The NASA cryogenic fluid management technology program plan

During the past three decades, NASA has been designing and using large quantities of cryogenic fluids for propulsion system propellants, coolants for experiments, and for environmental control systems. As a consequence, an erroneous conclusion has been drawn that the technology exists for using large quantities of cryogens in space for long periods of time. The attempt here is to dispel that myth and to present the technology needs that require development in order to support the NASA programs of the future. A NASA program, developed through the impetus of the Marshall Space Flight Center and the Lewis Research Center and supported by all NASA centers is outlined. The current state of the art is discussed along with specific needs for near future missions. Then, using the Space Exploration Initiative mission set, cost/benefit projections are made for the development of advanced cryogenic fluid management techniques. Earth based and space based test programs are discussed relative to the technology requirements for liquid storage, supply, and transfer for fluid transfer and advanced instrumentation.

Faddoul, James R.↗

Results of the automated power systems management /APSM/ program and future technology implementation

The APSM program was initiated in 1975. The purpose of this program was to develop and demonstrate the technology and benefits of autonomous operation of planetary spacecraft power systems to meet the projected requirements of future missions. Development of the APSM program was based on implementing a selected set of autonomous functions in a state-of-the-art breadboard power system. A distributed microcomputer system was developed to implement the functions. Several critical programmatic elements were identified as necessary to implement autonomous functions. These elements, including proper skill combination, well defined autonomous functions, and management of the software design and development task, were found to be more significant than hardware management. The incorporation of APSM technology in future space programs is also discussed.

Bridgeforth, A. O.↗

Documenting the Development of Software

Some routine supervisory functions performed automatically. Program Management Facility (PMF) computer program integrated software-development and control system. Applicable to large software systems involving as many as several hundred programmers and one million lines of codes, it ensures timely and orderly planning, development, implementation, and documentation of software. Designed as support tool. Has many features providing efficient processing and utilization of space for development programmer. Incorporates security system to prevent improper maintenance. Provides full set of cross-referenced reports and supervisory functions for detailed management information. Written in assembler. IBM program TSO required.

Source record↗

FEMP Facility Evaluation (Audit) Decision Tree

This document is a resource to be used in concert with FEMP Audit Definitions, FEMP Consolidated Facility Management Guidance, and agency best practices and expert judgment—for agencies to use to determine the best approaches to evaluate their facilities. It features a decision tree that provides a framework for agencies to interpret gathered facility data to understand the existing conditions; benchmark the facility against others in the portfolio to determine whether an on-site or remote audit is appropriate for a facility; determine the best remote or on-site audit level of detail to meet agency facility auditing goals, such as meeting Energy Independence and Security Act of 2007 requirements and developing projects; and improve their energy and water management programs.

auditing↗

Presenting Model-Based Systems Engineering Information to Non-Modelers

NASA’s Human Research Program’s (HRP) Exploration Medical Capability (ExMC) Element adopted Systems Engineering (SE) principles and Model Based Systems Engineering (MBSE) tools to capture the system functions, system architecture, requirements, interfaces, and clinical capabilities for a future exploration medical system. There are many different stakeholders who may use the information in the model: systems engineers, requirement engineers, clinicians (doctors, nurses, and pharmacists), scientists, and program managers. Many of these individuals do not have access to MBSE modeling toolsor have never used these tools. Many of these individuals (clinicians, scientists, even program managers)may have no experience with SE in general let alone interpreting a systems model. The challenge faced by ExMC was how to present the content in the model to non-modelers in a way they could understand with limited to no training in MBSE or the Systems Modeling Language (SysML) without using the modeling tool. Therefore, from the model, ExMC created an HTML report that is accessible to anyone with a browser. When creating the HTML report, the ExMC SE team talked to stakeholders and received their feedback on what content they wanted and how to display this content. Factoring in feedback, the report arranges the content in a way that not only directs readers through the SE process taken to derive the requirements, but also helps them to understand the fundamental steps in an SE approach. The report includes links to source information (i.e., NASA documentation that describes levels of care) and other SE deliverables (e.g., Concept of Operations). These links were provided to aid in the understanding of how the team created this content through a methodical SE approach. This paper outlines the process used to develop the model, the data chosen to share with stakeholders, many of the model elements used in the report, the review process stakeholders followed, the comments received from the stakeholders, and the lessons ExMC learned through producing this HTML report.

Jeff Cohen↗

The Ames Laboratory Annual Site Environmental Report: Calendar Year 2010

This report summarizes the environmental status of Ames Laboratory for calendar year 2010. It includes descriptions of the Laboratory site, its mission, the status of its compliance with applicable environmental regulations, its planning and activities to maintain compliance, and a comprehensive review of its environmental protection, surveillance and monitoring activities. In 2010, the Laboratory accumulated and disposed of waste under U.S. Environmental Protection Agency (EPA) issued generator numbers. All waste is handled according to all applicable EPA, State, Local regulations and DOE Orders. In 2006 the Laboratory reduced its generator status from a Large Quantity Generator (LQG) to a Small Quantity Generator (SQG). EPA Region VII was notified of this change. The Laboratory's RCRA hazardous waste management program was inspected by EPA Region VII in April 2006. There were no notices of violations. The inspector was impressed with the improvements of the Laboratory's waste management program over the past ten years. The Laboratory was in compliance with all applicable federal, state, local and DOE regulations and orders in 2010. There were no radiological air emissions or exposures to the general public due to Laboratory activities in 2010. See U.S. Department of Energy Air Emissions Annual Report in Appendix B. As indicated in prior SERs, pollution awareness, waste minimization and recycling programs have been in practice since 1990, with improvements implemented most recently in 2010. Included in these efforts were battery and CRT recycling, miscellaneous electronic office equipment, waste white paper and green computer paper-recycling and corrugated cardboard recycling. Ames Laboratory also recycles/reuses salvageable metal, used oil, foamed polystyrene peanuts, batteries, fluorescent lamps and telephone books. Ames Laboratory reported to DOE-Ames Site Office (AMSO), through the Laboratory's Performance Evaluation Measurement Plan, on its Affirmative Procurement Performance Measure. A performance level of 'A-' was achieved in 2010 for Integrated Safety, Health and Environmental Protection. As reported in Site Environmental Reports for prior years, the Laboratory's Environmental Management System (EMS) has been integrated into the Laboratory's Integrated Safety Management System since 2005. The integration of EMS into the way the Laboratory does business allows the Laboratory to systematically review, address and respond to the Laboratory's environmental impacts. The Laboratory's EMS was audited in April 2009 by DOE-CH. There were four 'Sufficiently in Conformity' findings as a result of the audit. All four findings were tracked in the Laboratory's corrective action database for completion. Beryllium was used routinely at Ames Laboratory in the 1940's and 1950's in processes developed for the production of highly pure uranium and thorium in support of the historic Manhattan Project. Laboratory metallurgists also worked on a process to produce pure beryllium metal from beryllium fluoride. In the early 1950's, beryllium oxide powder was used to produce shaped beryllium and crucibles. As a result of that work, beryllium contamination now exists in many interstitial spaces (e.g., utility chases) and ventilation systems in Wilhelm, Spedding and Metals Development buildings. Extensive characterization and remediation efforts have occurred in 2009 and 2010 in order to better understand the extent of the contamination. Analysis of extensive sampling data suggests that a fairly wide dispersion of beryllium occurred (most likely in the 1950's and 60's) in Wilhelm Hall and in certain areas of Spedding Hall and Metals Development. Area air-sampling results and work-area surface characterizations indicate the exposure potential to current workers, building visitors and the public remains extremely low. This information is now used to guide cleaning efforts and to provide worker protection during remodeling and maintenance activities. Results were shared with the DOE's Former Worker Program to support former worker medical testing and compensation programs. A complete discussion of the Laboratory's beryllium characterization and remediation efforts can be found at: http://www.ameslab.gov/operations/esha/beryllium-information.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

Presenting Model-Based Systems Engineering Information to Non-Modelers

NASA’s Human Research Program’s (HRP) Exploration Medical Capability (ExMC) Element adopted Systems Engineering (SE) principles and Model Based Systems Engineering (MBSE) tools to capture the system functions, system architecture, requirements, interfaces, and clinical capabilities for a future exploration medical system. There are many different stakeholders who may use the information in the model: systems engineers, clinicians (physicians, nurses, and pharmacists), scientists, and program managers. Many of these individuals do not have access to MBSE modeling tools or have never used these tools. Many of these individuals (clinicians, scientists, even program managers) may have no experience with SE in general let alone interpreting a systems model. The challenge faced by ExMC was how to present the content in the model to non-modelers in a way they could understand with limited to no training in MBSE or the Systems Modeling Language (SysML) without using the modeling tool. Therefore, from the model, ExMC created an HTML report that is accessible to anyone with a browser. When creating the HTML report, the ExMC SE team talked to stakeholders and received their feedback on what content they wanted and how to display this content. Factoring in feedback, the report arranges the content in a way that not only directs readers through the SE process taken to derive the requirements, but also helps them to understand the fundamental steps in an SE approach. The report includes links to source information (i.e., NASA documentation that describes levels of care) and other SE deliverables (e.g., Concept of Operations). These links were provided to aid in the understanding of how the team created this content through a methodical SE approach. This paper outlines the process used to develop the model, the data chosen to share with stakeholders, many of the model elements used in the report, the review process stakeholders followed, the comments received from the stakeholders, and the lessons ExMC learned through producing this HTML report.1Trade names and trademarks are used in this report for identification only. Their usage does not constitute an official endorsement, either expressed or implied, by the National Aeronautics and Space Administration.

Jeffrey R. Cohen↗

Presenting Model-Based Systems Engineering Information to Non-Modelers

NASA’s Human Research Program’s (HRP) Exploration Medical Capability (ExMC) Element adopted Systems Engineering (SE) principles and Model Based Systems Engineering (MBSE) tools to capture the system functions, system architecture, requirements, interfaces, and clinical capabilities for a future exploration medical system. There are many different stakeholders who may use the information in the model: systems engineers, clinicians (physicians, nurses, and pharmacists), scientists, and program managers. Many of these individuals do not have access to MBSE modeling tools or have never used these tools. Many of these individuals (clinicians, scientists, even program managers) may have no experience with SE in general let alone interpreting a systems model. The challenge faced by ExMC was how to present the content in the model to non-modelers in a way they could understand with limited to no training in MBSE or the Systems Modeling Language (SysML) without using the modeling tool. Therefore, from the model, ExMC created an HTML report that is accessible to anyone with a browser. When creating the HTML report, the ExMC SE team talked to stakeholders and received their feedback on what content they wanted and how to display this content. Factoring in feedback, the report arranges the content in a way that not only directs readers through the SE process taken to derive the requirements, but also helps them to understand the fundamental steps in an SE approach. The report includes links to source information (i.e., NASA documentation that describes levels of care) and other SE deliverables (e.g., Concept of Operations). These links were provided to aid in the understanding of how the team created this content through methodical SE approach. This paper outlines the process used to develop the model, the data chosen to share with stakeholders, many of the model elements used in the report, the review process stakeholders followed, the comments received from the stakeholders, and the lessons ExMC learned through producing this HTML report.

Jeffrey R. Cohen↗