Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “projects”

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 127 records · Page 7
All sourcesNASA NTRSDOE OSTI
NASA NTRS2008

The Herschel Oxygen Project: Herschel Space Observatory Open Time Key Project

Topics include: Why oxygen and why at submillimeter wavelengths; gas phase chemistry for water, oxygen, and carbon monoxide is relatively simple; molecular oxygen structure; lower rotational levels and transitions of oxygen; oxygen abundance in interstellar clouds; SWAS spectra of terrestrial oxygen; what Herschel offers HOP; key regions for probing oxygen in the dense interstellar medium; HOP sources and strategy; and HOP data and analysis.

astrochemistry↗
DOE OSTI2024

Carbon Management Projects (CONNECT) Database and Explorer

Overview The Carbon Management Projects (CONNECT) Toolkit is an online exploratory visualization tool developed by the U.S. Department of Energy's (DOE) Office of Fossil Energy and Carbon Management (FECM) with support from other federal agencies such as the U.S. Environmental Protection Agency (EPA) and the U.S. Department of Transportation (DOT). It provides a single point of access to authoritative information on federal agency investment in a portfolio of research, development, and demonstration (RD&D) projects that have been publicly announced to advance technologies for point source carbon capture, carbon dioxide removal, transport, storage, and conversion, collectively referred to as carbon management. The RD&D programs covered in this tool are authorized by annual congressional appropriations ("Base Program") and the 2021 Infrastructure Investment and Jobs Act (IIJA). The tool also incorporates public information on other federal initiatives, such as the Regional Clean Hydrogen Hubs, and public information released by other government agencies, such as the Environmental Protection Agency's (EPA) and Primacy States’ Underground Injection Control Class VI permits and EPA’s facility level greenhouse gas (GHG) emissions. Developed in a geographic information system, the tool organizes carbon management projects into five groups based on the primary technology that a project aims to advance, each visually represented as a digital layer ("carbon management project layer"). Only federally funded projects are included, which can be awarded projects that are completed or ongoing, or projects that have been selected but are currently under negotiation. Project information can be viewed in the map or in the attribute table below it when turned on. In the map view, each project is displayed at either its host site (for field work), where available, or its performer site (project lead's location, further explained in the table below). Host sites and performer sites are represented in distinct icons. Several reference layers offer additional public information on infrastructural and natural resource environment for carbon management. These reference layers, combined with multiple geographical basemaps, enable users to visualize the carbon management project layers in context. Carbon management project information will be updated monthly based on feedback and information availability. Carbon management project layers Point Source Carbon Capture (PSC) This layer contains DOE-funded projects focused on capturing carbon dioxide (CO2) from power plants or industrial facilities. Carbon Dioxide Removal (CDR) This layer contains DOE-funded projects focused on capturing CO2 from the atmosphere, including direct air capture (DAC) and DAC hubs, direct ocean capture, enhanced mineralization, and biomass carbon removal and storage. For projects with multiple host sites, each of the sites are displayed individually with the project cost and cost sharing information representing the total for the entire project. Carbon Transport This layer contains DOE- and DOT-funded projects focused on CO2 transport. The Transport Research and Development sublayer contains projects that do not involve physical infrastructure; the Proposed Transport Corridor sublayer contains projects for which either a route for the transport infrastructure has been proposed or a general area for the transport infrastructure has been identified. Carbon Storage This layer contains DOE-funded key projects focused on CO2 storage. For projects with multiple field-work sites, each of the sites are displayed individually on the map with the project cost and cost sharing information representing the overall total for the entire project. Carbon Conversion This layer contains DOE-funded projects focused on converting CO2 into economically valuable products. Reference layers The following layers provide additional information in the geographic proximity of carbon management projects. Users should reference the original sources for more details (weblinks provided below and in pop-up windows on the map). Regional Clean Hydrogen Hub and Facility These layers illustrate the approximate areas of the Regional Clean Hydrogen Hubs announced by DOE's Office of Clean Energy Demonstrations (OCED) and the approximate locations of individual facilities that constitute the hubs (see "Where are the H2Hubs located?" on the webpage linked above). EPA Facility Level GHG Emissions (direct emitter) This layer shows direct CO2 emissions from stationary sources in 2022, using data extracted from EPA's Facility Level Information on GreenHouse gases Tool (FLIGHT). Captured and injected CO2 are not deducted from direct emitters’ total emissions. Contact EPA for additional details. Underground Injection Control Class VI permit/permit application This layer shows the locations of CO2 injection wells that are granted or in the process of applying for an Underground Injection Control Class VI permit by EPA or a Primacy State (currently Louisiana, North Dakota, and Wyoming). The URLs for the permits or permit applications are provided in the pop-up windows associated with the well locations. Contact EPA for additional details. Carbon Storage Resource This layer contains information on prospective CO2 storage resources in saline formations and oil and gas reservoirs provided by the National Carbon Sequestration Database and Geographic Information System (NATCARB) spatial database. Contact NETL for additional details. Existing CO2 pipeline This layer shows active CO2 pipelines based on information digitized from the map issued by the Pipeline and Hazardous Materials Safety Administration (PHMSA). Contact PHMSA for additional details.

Carbon Conversion↗
NASA NTRS2004

Improving Project Management with Simulation and Completion Distribution Functions

Despite the critical importance of project completion timeliness, management practices in place today remain inadequate for addressing the persistent problem of project completion tardiness. A major culprit in late projects is uncertainty, which most, if not all, projects are inherently subject to. This uncertainty resides in the estimates for activity durations, the occurrence of unplanned and unforeseen events, and the availability of critical resources. In response to this problem, this research developed a comprehensive simulation based methodology for conducting quantitative project completion time risk analysis. It is called the Project Assessment by Simulation Technique (PAST). This new tool enables project stakeholders to visualize uncertainty or risk, i.e. the likelihood of their project completing late and the magnitude of the lateness, by providing them with a completion time distribution function of their projects. Discrete event simulation is used within PAST to determine the completion distribution function for the project of interest. The simulation is populated with both deterministic and stochastic elements. The deterministic inputs include planned project activities, precedence requirements, and resource requirements. The stochastic inputs include activity duration growth distributions, probabilities for events that can impact the project, and other dynamic constraints that may be placed upon project activities and milestones. These stochastic inputs are based upon past data from similar projects. The time for an entity to complete the simulation network, subject to both the deterministic and stochastic factors, represents the time to complete the project. Repeating the simulation hundreds or thousands of times allows one to create the project completion distribution function. The Project Assessment by Simulation Technique was demonstrated to be effective for the on-going NASA project to assemble the International Space Station. Approximately $500 million per month is being spent on this project, which is scheduled to complete by 2010. NASA project stakeholders participated in determining and managing completion distribution functions produced from PAST. The first result was that project stakeholders improved project completion risk awareness. Secondly, using PAST, mitigation options were analyzed to improve project completion performance and reduce total project cost.

Cates, Grant R.↗
NASA NTRS2011

Project Management Using Modern Guidance, Navigation and Control Theory

Implementing guidance, navigation, and control (GN&C) theory principles and applying them to the human element of project management and control is not a new concept. As both the literature on the subject and the real-world applications are neither readily available nor comprehensive with regard to how such principles might be applied, this paper has been written to educate the project manager on the "laws of physics" of his or her project (not to teach a GN&C engineer how to become a project manager) and to provide an intuitive, mathematical explanation as to the control and behavior of projects. This paper will also address how the fundamental principles of modern GN&C were applied to the National Aeronautics and Space Administration's (NASA) Constellation Program (CxP) space suit project, ensuring the project was managed within cost, schedule, and budget. A project that is akin to a physical system can be modeled and managed using the same over arching principles of GN&C that would be used if that project were a complex vehicle, a complex system(s), or complex software with time-varying processes (at times nonlinear) containing multiple data inputs of varying accuracy and a range of operating points. The classic GN&C theory approach could thus be applied to small, well-defined projects; yet when working with larger, multiyear projects necessitating multiple organizational structures, numerous external influences, and a multitude of diverse resources, modern GN&C principles are required to model and manage the project. The fundamental principles of a GN&C system incorporate these basic concepts: State, Behavior, Feedback Control, Navigation, Guidance and Planning Logic systems. The State of a system defines the aspects of the system that can change over time; e.g., position, velocity, acceleration, coordinate-based attitude, and temperature, etc. The Behavior of the system focuses more on what changes are possible within the system; this is denoted in the state of the system. The behavior of a system, as captured in the system modeling, when properly done will aid in accurately predicting future system performance. The Feedback Control system understands the state and behavior of the system and uses feedback to adjust control inputs into the system. The feedback, which is the right arm of the Control system, allows change to be affected in the overall system; it therefore is important to not only correctly identify the system feedback inputs, but also the system response to the feedback inputs. The Navigation system takes multiple data inputs and based on a priori knowledge of the inputs, develops a statistically based weighting of the inputs and measurements to determine the system's state. Guidance and Planning Logic of the system, complete with an understanding of where the system is (provided by the Navigation system), will in turn determine where the system needs to be and how to get it there. With any system/project, it is critical that the objective of the system/project be clearly defined -- not only to plan but to measure performance and to aid in guiding the system or the project. The system principles discussed above, which can be and have been applied to the current CxP space suit development project, can also be mapped to real-world constituents, thus allowing project managers to apply systems theories that are well defined in engineering and mathematics to a discipline (i.e., Project Management) that historically has been based in personal experience and intuition. This mapping of GN&C theory to Project Management will, in turn, permit a direct, methodical approach to Project Management, planning and control providing a tool to help predict (and guide) performance and an understanding of the project constraints, how the project can be controlled, and the impacts to external influences and inputs. This approach, to a project manager, flows down to the three bottom-line variables of cost, schedule, and scope ando the needed control of these three variables to successfully perform and complete a project.

Hill, Terry R.↗
NASA NTRS2008

The Project Manager Who Saved His Country

George Meade defeated Robert E. Lee, one of the greatest military leaders of all time. How did he do it? By using the skills he had learned as a project manager and outperforming Lee in all aspects of project management. Most project managers are familiar with the Project Management Institute's "Guide to the Project Management Body of Knowledge" (PMBOK), which identifies the skills and knowledge crucial to successful project management. Project managers need to make sure that all the elements of a project work together. They must develop and execute plans and coordinate changes to those plans. A project manager must define the scope of the work, break it into manageable pieces, verify and control what work is being done, and make sure that the work being done is essential to the project. Every project manager knows the challenges of schedule and the value of schedule slack. Project managers must get the resources they need and use them effectively. Project managers get the people they need and use their talents to achieve mission success. Projects generate huge amounts of information. A key to project success is getting sufficient and accurate information to the people who need it when they need it. Project managers must identify and quantify the risks that jeopardize project success and make plans for dealing with them. Studying Meade and Lee's performances at Gettysburg can help modern project managers appreciate, develop, and use the skills they need to be good project managers. The circumstances may be different, but the basic principles are the same. This dramatic event in American history shows how the skills of project management can be used in almost any situation. Former project manager George Meade used those skills to change the tide of the Civil War.

Baniszewski, John↗
NASA NTRS2015

Underestimation of Project Costs

Large projects almost always exceed their budgets. Estimating cost is difficult and estimated costs are usually too low. Three different reasons are suggested: bad luck, overoptimism, and deliberate underestimation. Project management can usually point to project difficulty and complexity, technical uncertainty, stakeholder conflicts, scope changes, unforeseen events, and other not really unpredictable bad luck. Project planning is usually over-optimistic, so the likelihood and impact of bad luck is systematically underestimated. Project plans reflect optimism and hope for success in a supposedly unique new effort rather than rational expectations based on historical data. Past project problems are claimed to be irrelevant because "This time it's different." Some bad luck is inevitable and reasonable optimism is understandable, but deliberate deception must be condemned. In a competitive environment, project planners and advocates often deliberately underestimate costs to help gain project approval and funding. Project benefits, cost savings, and probability of success are exaggerated and key risks ignored. Project advocates have incentives to distort information and conceal difficulties from project approvers. One naively suggested cure is more openness, honesty, and group adherence to shared overall goals. A more realistic alternative is threatening overrun projects with cancellation. Neither approach seems to solve the problem. A better method to avoid the delusions of over-optimism and the deceptions of biased advocacy is to base the project cost estimate on the actual costs of a large group of similar projects. Over optimism and deception can continue beyond the planning phase and into project execution. Hard milestones based on verified tests and demonstrations can provide a reality check.

Cost estimation↗
NASA NTRS2005

Proposed Project Selection Method for Human Support Research and Technology Development (HSR&TD)

The purpose of HSR&TD is to deliver human support technologies to the Exploration Systems Mission Directorate (ESMD) that will be selected for future missions. This requires identifying promising candidate technologies and advancing them in technology readiness until they are acceptable. HSR&TD must select an may of technology development projects, guide them, and either terminate or continue them, so as to maximize the resulting number of usable advanced human support technologies. This paper proposes an effective project scoring methodology to support managing the HSR&TD project portfolio. Researchers strongly disagree as to what are the best technology project selection methods, or even if there are any proven ones. Technology development is risky and outstanding achievements are rare and unpredictable. There is no simple formula for success. Organizations that are satisfied with their project selection approach typically use a mix of financial, strategic, and scoring methods in an open, established, explicit, formal process. This approach helps to build consensus and develop management insight. It encourages better project proposals by clarifying the desired project attributes. We propose a project scoring technique based on a method previously used in a federal laboratory and supported by recent research. Projects are ranked by their perceived relevance, risk, and return - a new 3 R's. Relevance is the degree to which the project objective supports the HSR&TD goal of developing usable advanced human support technologies. Risk is the estimated probability that the project will achieve its specific objective. Return is the reduction in mission life cycle cost obtained if the project is successful. If the project objective technology performs a new function with no current cost, its return is the estimated cash value of performing the new function. The proposed project selection scoring method includes definitions of the criteria, a project evaluation questionnaire, and a scoring formula.

Jones, Harry↗
DOE OSTI2025

Design Basis Document / Owner’s Technical Specification for Nitrate Salt Systems in CSP Projects (Final Technical Report)

The number of commercial coal, gas, and nuclear projects built over the past 100 years number in the thousands. As such, there is a large database, available to a wide range of commercial engineering contractors, on proven designs. In essence, unsuccessful designs have, through generations of iterations, been identified and then deleted from further consideration. In contrast, the number of commercial parabolic trough projects using nitrate salt for the thermal storage media is perhaps 60. Further, the number of commercial central receiver projects using nitrate salt as the working fluid is on the order of 20, including estimates for China. Given the relative immaturity of salt technology, and commercial pressures to successfully bid new solar projects into a mature electricity market, solar projects often promise more than has been delivered. The Design Basis Document / Owner’s Technical Specification is a first step in the iteration process. The report describes the successful features of commercial projects, outlines a range equipment and system failures in projects that didn’t operate as intended, and provides a draft set of design changes intended to correct the known problems. The product of the study is 3 volumes of technical material; one volume is on parabolic trough technologies; a second is on central receiver technologies, and the third is on potential design changes to parabolic trough and central receiver projects. The 3 volumes, which total some 590 pages, can be found at https://www.solardynllc.com/csp-plant-technologies. One of the principal topics in the report is the use of functional or prescriptive specifications. Functional specifications describe what the equipment needs to do, consistent with the minimum legal requirements of the local jurisdictions. The details of how this is to be accomplished is developed by the engineering contractor. Prescriptive specifications, which are developed by the Owner, prescribe to the engineering contractor how the functional requirements are to be met. This arrangement ensures that the favorable experience from a previous project is repeated. One example is the design code for the hot salt tank in central receiver projects. The closest design basis is API Standard 650 Welded Steel Tanks for Oil Storage. However, the maximum design temperature in API 650 is 260 °C. As such, solar projects have typically adopted a hybrid Code approach, in which allowable material stresses are taken from ASME Section II Materials. Further, since the tanks experience daily changes in temperature and in (static) pressure, and since portions of the tank can operate at stresses beyond the elastic range, the low cycle fatigue life of the tank is conducted using the rules of Section VIII Division 2. However, in a recent study by NREL, the principal damage mechanism was identified as creep rather than fatigue. Further, design stresses permitted under Section VIII Division 2, corresponding to a fatigue life of 30 years, result in projected creep lifetimes of only 2 to 5 years. An alternate design approach, prescribed by the Owner, would be based on Code sections intended for high temperature service in the creep regime. A candidate is Section III Division 5. Granted, this is a nuclear code section, and it’s use would not likely be mandated by local jurisdictions. However, the effects of creep have been deemed to be of sufficient importance that one nuclear project developer, and one central receiver project developer, have stipulated in the tank design specification that the equipment be designed to the requirements of Section III Division 5.

14 SOLAR ENERGY↗
NASA NTRS2008

Guidance and Control Software Project Data - Volume 4: Configuration Management and Quality Assurance Documents

The Guidance and Control Software (GCS) project was the last in a series of software reliability studies conducted at Langley Research Center between 1977 and 1994. The technical results of the GCS project were recorded after the experiment was completed. Some of the support documentation produced as part of the experiment, however, is serving an unexpected role far beyond its original project context. Some of the software used as part of the GCS project was developed to conform to the RTCA/DO-178B software standard, "Software Considerations in Airborne Systems and Equipment Certification," used in the civil aviation industry. That standard requires extensive documentation throughout the software development life cycle, including plans, software requirements, design and source code, verification cases and results, and configuration management and quality control data. The project documentation that includes this information is open for public scrutiny without the legal or safety implications associated with comparable data from an avionics manufacturer. This public availability has afforded an opportunity to use the GCS project documents for DO-178B training. This report provides a brief overview of the GCS project, describes the 4-volume set of documents and the role they are playing in training, and includes configuration management and quality assurance documents from the GCS project. Volume 4 contains six appendices: A. Software Accomplishment Summary for the Guidance and Control Software Project; B. Software Configuration Index for the Guidance and Control Software Project; C. Configuration Management Records for the Guidance and Control Software Project; D. Software Quality Assurance Records for the Guidance and Control Software Project; E. Problem Report for the Pluto Implementation of the Guidance and Control Software Project; and F. Support Documentation Change Reports for the Guidance and Control Software Project.

Hayhurst, Kelly J.↗