Search NASA⌕ Search

SEARCH · Search NASA

Results for “Project Life Cycle”

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

Solar energy system economic evaluation final report for SEMCO-Loxahatchee, Loxahatchee National Wildlife refuge, Palm Beach County, Florida

Economic analysis of the solar energy system installed at Loxahatchee, was developed for Loxahatchee and four other sites typical of a wide range of environmental and economic conditions in the continental United States. This analysis was accomplished based on the technical and economic models in the f Chart design procedure with inputs based on the characteristics of the installed system and local conditions. The results are expressed in terms of the economic parameters of present worth of system costs over a projected twenty year life, life cycle savings, year of positive savings and year of payback for the optimized solar energy system at each of the analysis sites. The sensitivity of the economic evaluation to uncertainties in constituent system and economic variables was also investigated. The results demonstrate that the solar energy system is economically viable at all of the five sites for which the analysis was conducted.

Source record↗

Solar energy system economic evaluation for Elcam-Tempe, Tempe, Arizona and Elcam-San Diego, San Diego, California

The long term economic performance of the solar energy system at its installation site is analyzed and four additional locations selected to demonstrate the viability of the design over a broad range of environmental and economic conditions. The economic analysis of the solar energy systems that were installed at Tempe, Arizona and San Diego, California, is developed for these and four other sites typical of a wide range of environmental and economic conditions in the continental United States. This analysis is accomplished based on the technical and economic models in the f Chart design procedure with inputs based on the characteristics of the installed system and local conditions. The results are expressed in terms of the economic parameters of present worth of system cost over a projected twenty year life: life cycle savings; year of positive savings; and year of payback for the optimized solar energy system at each of the analysis sites. The sensitivity of the economic evaluation to uncertainites in constituent system and economic variables is also investigated. The results demonstrate that the solar energy system is economically viable at all of the sites for which the analysis was conducted.

Source record↗

Solar energy system economic evaluation for IBM System 3, Glendo, Wyoming

This analysis was based on the technical and economic models in f-chart design procedures with inputs based on the characteristics of the parameters of present worth of system cost over a projected twenty year life: life cycle savings, year of positive savings, and year of payback for the optimized solar energy system at each of the analysis sites. The sensitivity of the economic evaluation to uncertainties in constituent system and economic variables was also investigated.

Source record↗

Solar energy system economic evaluation for Seeco Lincoln, Lincoln, Nebraska

The economic analysis of the solar energy system that was installed at Lincoln, Nebraska is developed for this and four other sites typical of a wide range of environmental and economic conditions in the continental United States. This analysis is accomplished based on the technical and economic models in the f chart design procedure with inputs based on the characteristics of the installed system and local conditions. The results are expressed in terms of the economic parameters of present worth of system cost over projected twenty year life: life cycle savings, year of positive savings and year of payback for the optimized solar energy system at each of the analysis sites. The sensitivity of the economic evaluation to uncertainties in constituent system and economic variables is also investigated.

Source record↗

Solar energy system economic evaluation for Solaron Akron, Akron, Ohio

The economic analysis of the solar energy system that was installed at Akron, Ohio is developed for this and four other sites typical of a wide range of environmental and economic conditions. The analysis is accomplished based on the technical and economic models in the f chart design procedure with inputs based on the characteristics of the installed parameters of present worth of system cost over a projected twenty year life: life cycle savings, year of positive savings and year of payback for the optimized solar energy system at each of the analysis sites. The sensitivity of the economic evaluation to uncertainties in constituent system and economic variables is also investigated. Results show that only in Albuquerque, New Mexico, where insolation is 1828 Btu/sq ft/day and the conventional energy cost is high, is this solar energy system marginally profitable.

Source record↗

Functional description of the ISIS system

Development of software for avionic and aerospace applications (flight software) is influenced by a unique combination of factors which includes: (1) length of the life cycle of each project; (2) necessity for cooperation between the aerospace industry and NASA; (3) the need for flight software that is highly reliable; (4) the increasing complexity and size of flight software; and (5) the high quality of the programmers and the tightening of project budgets. The interactive software invocation system (ISIS) which is described is designed to overcome the problems created by this combination of factors.

Berman, W. J.↗

A study of System Interface Sets (SIS) for the host, target and integration environments of the Space Station Program (SSP)

System interface sets (SIS) for large, complex, non-stop, distributed systems are examined. The SIS of the Space Station Program (SSP) was selected as the focus of this study because an appropriate virtual interface specification of the SIS is believed to have the most potential to free the project from four life cycle tyrannies which are rooted in a dependance on either a proprietary or particular instance of: operating systems, data management systems, communications systems, and instruction set architectures. The static perspective of the common Ada programming support environment interface set (CAIS) and the portable common execution environment (PCEE) activities are discussed. Also, the dynamic perspective of the PCEE is addressed.

Mckay, Charles↗

Advanced software development workstation. Comparison of two object-oriented development methodologies

This report is an attempt to clarify some of the concerns raised about the OMT method, specifically that OMT is weaker than the Booch method in a few key areas. This interim report specifically addresses the following issues: (1) is OMT object-oriented or only data-driven?; (2) can OMT be used as a front-end to implementation in C++?; (3) the inheritance concept in OMT is in contradiction with the 'pure and real' inheritance concept found in object-oriented (OO) design; (4) low support for software life-cycle issues, for project and risk management; (5) uselessness of functional modeling for the ROSE project; and (6) problems with event-driven and simulation systems. The conclusion of this report is that both Booch's method and Rumbaugh's method are good OO methods, each with strengths and weaknesses in different areas of the development process.

Izygon, Michel E.↗

Turning Operational Lessons Learned into Design Reality

The capabilities and limitations of a particular system design are well known by the people who operate it. Operational workarounds, operational notes and lessons learned are traditional methods for dealing with and documenting design shortcomings. The beginning of each new program brings the hope that hard-learned lessons will be incorporated into the next new system. But often operations personnel find their well-intentioned efforts frustrated by an inability to have their inputs considered by design personnel who have strictly-scoped requirements that are coupled with ambitious cost and schedule targets. There is a way for operational inputs to make it into the design, but the solution involves a combination of organizational culture and technical data. Any organization that utilizes this approach can realize significant benefits over the life cycle of their project.

Brady, David A.↗

NASA System Engineering Design Process

This slide presentation reviews NASA's use of systems engineering for the complete life cycle of a project. Systems engineering is a methodical, disciplined approach for the design, realization, technical management, operations, and retirement of a system. Each phase of a NASA project is terminated with a Key decision point (KDP), which is supported by major reviews.

Roman, Jose↗

Systems Engineering Awareness

The presentation will provide an overview of the fundamentals and principles of Systems Engineering (SE). This includes understanding the processes that are used to assist the engineer in a successful design, build and implementation of solutions. The context of this presentation will be to describe the involvement of SE throughout the life-cycle of a project from cradle to grave. Due to the ever growing number of complex technical problems facing our world, a Systems Engineering approach is desirable for many reasons. The interdisciplinary technical structure of current systems, technical processes representing System Design, Technical Management and Product Realization are instrumental in the development and integration of new technologies into mainstream applications. This tutorial will demonstrate the application of SE tools to these types of problems..

technical management↗

X-57 Static Structural Requirements and Airworthiness Approach

The National Aeronautics and Space Administration (NASA) Armstrong Flight Research Center (AFRC) (Edwards, California, U.S.A.) has been flying various types of aircraft, including experimental ones requiring structural modifications. Many of these aircraft aren’t typically certified by the Federal Aviation Administration (FAA) or the Department of Defense (DoD), but NASA can provide its own airworthiness certification utilizing a riskbased approach. The AFRC has established review processes and procedures to identify hazards, manage risks associated with flight programs, ensure safe flight operations, and satisfy programmatic requirements. The Aerostructures Branch at AFRC developed guidelines for the structural safety of flight, covering experimental aircraft, new components, payloads, and modifications. These guidelines detail structural design, analysis, instrumentation, ground testing, and flight-test operational aspects. The guidelines are followed for defining the airworthiness plan throughout the life cycle of a project. The guidelines can be tailored to the risk posture of each individual project. This paper documents the details of the structural airworthiness plan for the X-57 aircraft, including existing, modified, and newly developed structures. Additionally, it covers the design requirements and load cases specific to the X-57 aircraft.

Wesley W. Li↗

NASA Human Spaceflight Scenarios - Do All Our Models Still Say No?

Historically, NASA human spaceflight planning has included healthy doses of life cycle cost analysis. Planners put projects and their cost estimates in a budget context. Estimated costs became expected budgets. Regardless, real budgets rarely matched expectations. So plans would come and go as NASA canceled projects. New projects would arise and the cycle would begin again. Repeatedly, NASA schedule and performance ambitions come up against costs growing at double-digit rates while budgets barely rise a couple of percent a year. Significant skepticism greets proposed NASA programs at birth, as cost estimates for new projects are traditionally very high, and worse, far off the mark for those carried forward. In this environment the current "capability driven framework" for NASA human spaceflight evolved, where long term life cycle cost analysis are even viewed as possibly counter-productive. Here, a space exploration project, for example the Space Launch System, focuses on immediate goals. A life cycle is that of a project, not a program, and for only that span of time to a near term milestone like a first test launch. Unfortunately, attempting to avoid some pitfalls in long-term life cycle cost analysis breeds others. Government audits have noted that limiting the scope of cost analysis "does not provide the transparency necessary to assess long-term affordability" making it difficult to understand if NASA "is progressing in a cost-effective and affordable manner." Even in this short-term framework, NASA realizes the importance of long-term considerations, that it must "maximize the efficiency and sustainability of the Exploration Systems development programs", that this is "critical to free resources for re-investment...such as other required deep space exploration capabilities." Assuming the value of long-term life cycle cost analysis, where due diligence meets reconnaissance, and accepting past shortcomings, the work here approaches life cycle cost analysis for human spaceflight differently. 1) If costs have traditionally been so high that adding them up is discouraging, are there any new facts on the ground offering paths to significantly lower costs? 2) If NASA's spaceflight budget and process is an over-arching constraint, with its planning limitations favoring short-term outlooks, is there a way to step outside the budget box? 3) If life cycle answers have historically been too uncertain to be useful, is there a process where stakeholders gain valuable insights merely from emphasizing a common understanding around questions? We analyze the potential life cycle cost of assorted NASA human spaceflight architectures - an architecture as a sum of individual systems, working together. With the prior questions of high costs, limited budgets and uncertainties in mind, public private partnerships are central in these architectures. The cost data for current commercial public private partnerships is encouraging, as are cost estimates for future partnership approaches beyond low Earth orbit. Private capital, directly or indirectly, an ingredient of public private partnerships, may be a significant factor in finding a path around the limits of the NASA spaceflight budget. Also, understanding and reviewing the pros, cons and uncertainties of assorted architectures can assist in developing a common understanding around key questions as important if not more so than the numbers and answers. Lastly, a scenario planning technique is briefly explored that can mature a common understanding about the agencies situation at hand and how diverse stakeholders can go forward together. Scenario planning, rather than focusing on answers, places emphasis on stakeholders developing a common understanding about the future. Putting aside costs, this is especially true of questions about sustainability and growth, results, benefits and expectations. While efficiency exercises or analysis look to reduce resources in one place to apply them elsewhere, moving around slices in a pie, scenario planning can get at the heart of the matter, growing the pie, transforming it, and making the pieces relevant. Especially important is the question of sustainability for different scenarios in the broad sense of the word - not just the narrow ability to survive or continue, but also the ability to adapt, prosper and grow.

space systems life cycle costs↗

NASA Standing Review Board Handbook

This handbook provides guidance based on best practices for the planning, preparation, review, reporting, and closeout of Standing Review Board (SRB) activities. Revision C updates the Revision B version of the SRB Handbook published in 2016 to incorporate updates to NASA Procedural Requirements (NPR) 7120.5F, NASA Space Flight Program and Project Management Requirements. These updates include: - Changing the Dissenting Opinion process to the Formal Dissent process, which retains the current process augmented with an expedited escalation path. - Updates to requirements for establishing an Agency Baseline Commitment (ABC) and for performing Joint Cost and Schedule Confidence Level (JCL) analyses for tightly coupled programs. - Additional requirements for performing a JCL analysis for single-project programs and projects over $1B Life-Cycle Cost (LCC). - Use of initial capability cost estimates instead of LCC estimates in specific, identified instances for single-project programs and projects that plan continuing operations and production, including integration of capability upgrades, with an unspecified Phase E end point. These single-project programs and projects define an initial capability during Phase A and develop an initial capability cost that establishes the ABC at Key Decision Point (KDP) C. Initial capability is the first operational mission flight (or as defined in the KDP B Review Plan) and is documented in the KDP B Decision Memorandum. Initial capability cost includes operations cost for the initial capability. The Phase E cost estimate for continuing operations and production is established separately as part of the Operational Readiness Review (ORR) and KDP E for the 5 years after initial capability and subsequently updated and documented annually for the next 5-year period. Upgrades during Phase E that meet the Agency criteria for a major project for external reporting are treated as projects for the purposes of establishing their own development ABC outside the Phase E cost estimate. The Phase E cost estimate is updated to include production and operations costs associated with these upgrades. Development, production, and operations costs of other (i.e., non-major) upgrades are included in the Phase E cost estimate. (See NPR 7120.5, Sections 2.4.1.5 and 2.4.1.6 and the NASA Space Flight Program and Project Management Handbook (PM Handbook), Section 5.5.4 for additional information.) The scope of the SRB’s assessment with respect to initial capability, Phase E cost estimate, and major upgrades for these single-project programs and projects is defined in the Terms of Reference (ToR).

Kevin Michael Gilligan↗

Problem Reporting System

The Problem Reporting System (PRS) is a Web application, running on two Web servers (load-balanced) and two database servers (RAID-5), which establishes a system for submission, editing, and sharing of reports to manage risk assessment of anomalies identified in NASA's flight projects. PRS consolidates diverse anomaly-reporting systems, maintains a rich database set, and incorporates a robust engine, which allows tracking of any hardware, software, or paper process by configuring an appropriate life cycle. Global and specific project administration and setup tools allow lifecycle tailoring, along with customizable controls for user, e-mail, notifications, and more. PRS is accessible via the World Wide Web for authorized user at most any location. Upon successful log-in, the user receives a customizable window, which displays time-critical 'To Do' items (anomalies requiring the user s input before the system moves the anomaly to the next phase of the lifecycle), anomalies originated by the user, anomalies the user has addressed, and custom queries that can be saved for future use. Access controls exist depending on a user's role as system administrator, project administrator, user, or developer, and then, further by association with user, project, subsystem, company, or item with provisions for business-to-business exclusions, limitations on access according to the covert or overt nature of a given project, all with multiple layers of filtration, as needed. Reporting of metrics is built in. There is a provision for proxy access (in which the user may choose to grant one or more other users to view screens and perform actions as though they were the user, during any part of a tracking life cycle - especially useful during tight build schedules and vacations to keep things moving). The system also provides users the ability to have an anomaly link to or notify other systems, including QA Inspection Reports, Safety, GIDEP (Government-Industry Data Exchange Program) Alert, Corrective Actions, and Lessons Learned. The PRS tracking engine was designed as a very extensible and scalable system, able to support additional applications, with future development possibilities already discussed, including Incident Surprise Anomalies (for anomalies occurring during Operations phases of NASA Flight projects), GIDEP and NASA Alerts, and others.

Potter, Don↗

Why Don't They Just Give Us Money? Project Cost Estimating and Cost Reporting

Successful projects require an integrated approach to managing cost, schedule, and risk. This is especially true for complex, multi-year projects involving multiple organizations. To explore solutions and leverage valuable lessons learned, NASA's Virtual Project Management Challenge will kick off a three-part series examining some of the challenges faced by project and program managers when it comes to managing these important elements. In this first session of the series, we will look at cost management, with an emphasis on the critical roles of cost estimating and cost reporting. By taking a proactive approach to both of these activities, project managers can better control life cycle costs, maintain stakeholder confidence, and protect other current and future projects in the organization's portfolio. Speakers will be Doug Comstock, Director of NASA's Cost Analysis Division, Kristin Van Wychen, Senior Analyst in the GAO Acquisition and Sourcing Management Team, and Mary Beth Zimmerman, Branch Chief for NASA's Portfolio Analysis Branch, Strategic Investments Division. Moderator Ramien Pierre is from NASA's Academy for Program/Project and Engineering Leadership (APPEL).

Comstock, Douglas A.↗

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↗

Technical Requirements Analysis and Control Systems (TRACS) Initial Operating Capability (IOC) documentation

The Technical Requirements Analysis and Control Systems (TRACS) software package is described. TRACS offers supplemental tools for the analysis, control, and interchange of project requirements. This package provides the fundamental capability to analyze and control requirements, serves a focal point for project requirements, and integrates a system that supports efficient and consistent operations. TRACS uses relational data base technology (ORACLE) in a stand alone or in a distributed environment that can be used to coordinate the activities required to support a project through its entire life cycle. TRACS uses a set of keyword and mouse driven screens (HyperCard) which imposes adherence through a controlled user interface. The user interface provides an interactive capability to interrogate the data base and to display or print project requirement information. TRACS has a limited report capability, but can be extended with PostScript conventions.

Hammond, Dana P.↗