Search NASA⌕ Search

SEARCH · Search NASA

Results for “Project Schedule”

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 37 records · Page 2

The Development of Project Orion Ground Safety Requirements

In spite of a very compressed schedule, Project Orion's AFT safety team was able to pull together a comprehensive set of ground safety requirements using existing requirements and subject matter experts. These requirements will serve as the basis for the design of GSE and ground operations. Using the above lessons as a roadmap, new Projects can produce the same results. A rigorous set of ground safety requirements is required to assure ground support equipment (GSE) and associated flight hardware ground operations are conducted safety

Kirkpatrick, Paul↗

GCS plan for software aspects of certification

As part of the Guidance and Control Software (GCS) research project being sponsored by NASA to evaluate the failure processes of software, standard industry software development procedures are being employed. To ensure that these procedures are authentic, the guidelines outlined in the Radio Technical Commission for Aeronautics (RTCA/DO-178A document entitled, software considerations in airborne systems and equipment certification, were adopted. A major aspect of these guidelines is proper documentation. As such, this report, the plan for software aspects of certification, was produced in accordance with DO-178A. An overview is given of the GCS research project, including the goals of the project, project organization, and project schedules. It also specifies the plans for all aspects of the project which relate to the certification of the GCS implementations developed under a NASA contract. These plans include decisions made regarding the software specification, accuracy requirements, configuration management, implementation development and verification, and the development of the GCS simulator.

Shagnea, Anita M.↗

Mars Reconnaissance Orbiter, Ground Data System, Receivables and Deliverables (REC/DELs)

This paper presents one JPL element manager's approach to describe a complex Ground Data System (GDS) with its receivables and deliverables (REC/DEL). The Mars Reconnaissance Orbiter (MRO) Ground Data System is the integrated set of ground software, hardware, facilities and networks that support mission operation. REC/DEL is a powerful tool for specifying hierarchy of commitments among systems and teams. Receivable of a system is a deliverable of another system. Focusing on tangible products enables the manager to objectively measure progress in a schedule. Jet Propulsion Laboratory mandates the use of REC/DEL for flight projects. Tutorial and training is provided for managers to create integrated REC/DEL database using automated systems. Project schedules are based on REC/DELs. This paper is not focusing on the mechanics of REC/DEL database creation, but it provides a guideline how one systematically creates categories of deliverables and receivables for ground data system components.

guidelines↗

The Lawrence Berkeley Laboratory geothermal program in northern Nevada

The Lawrence Berkeley Laboratory's geothermal program began with consideration of regions where fluids in the temperature range of 150 to 230 C may be economically accessible. Three valleys, located in an area of high regional heat flow in north central Nevada, were selected for geological, geophysical, and geochemical field studies. The objective of these ongoing field activities is to select a site for a 10-MW demonstration plant. Field activities (which started in September 1973) are described. A parallel effort has been directed toward the conceptual design of a 10-MW isobutane binary plant which is planned for construction at the selected site. Design details of the plant are described. Project schedule with milestones is shown together with a cost summary of the project.

Mirk, K. F.↗

Development of a funding, cost, and spending model for satellite projects

The need for a predictive budget/funging model is obvious. The current models used by the Resource Analysis Office (RAO) are used to predict the total costs of satellite projects. An effort to extend the modeling capabilities from total budget analysis to total budget and budget outlays over time analysis was conducted. A statistical based and data driven methodology was used to derive and develop the model. Th budget data for the last 18 GSFC-sponsored satellite projects were analyzed and used to build a funding model which would describe the historical spending patterns. This raw data consisted of dollars spent in that specific year and their 1989 dollar equivalent. This data was converted to the standard format used by the RAO group and placed in a database. A simple statistical analysis was performed to calculate the gross statistics associated with project length and project cost ant the conditional statistics on project length and project cost. The modeling approach used is derived form the theory of embedded statistics which states that properly analyzed data will produce the underlying generating function. The process of funding large scale projects over extended periods of time is described by Life Cycle Cost Models (LCCM). The data was analyzed to find a model in the generic form of a LCCM. The model developed is based on a Weibull function whose parameters are found by both nonlinear optimization and nonlinear regression. In order to use this model it is necessary to transform the problem from a dollar/time space to a percentage of total budget/time space. This transformation is equivalent to moving to a probability space. By using the basic rules of probability, the validity of both the optimization and the regression steps are insured. This statistically significant model is then integrated and inverted. The resulting output represents a project schedule which relates the amount of money spent to the percentage of project completion.

Johnson, Jesse P.↗

Mars Reconnaissance Orbiter, Ground Data System, Receivables and Deliverables (REC/DELs)

This paper presents one JPL element manager's approach to describe a complex Ground Data System (GDS) with its receivables and deliverables (REC/DEL). The Mars Reconnaissance Orbiter (MRO) Ground Data System is the integrated set of ground software, hardware, facilities and networks that support mission operation. REC/DEL is a powerful tool for specifying hierarchy of commitments among systems and teams. Receivable of a system is a deliverable of another system. Focusing on tangible products enables the manager to objectively measure progress in a schedule. The Jet Propulsion Laboratory mandates the use of REC/DEL for flight projects. Tutorial and training is provided for managers to create an integrated REC/DEL database using automated systems. Project schedules are based on REC/DELs. This paper is not focusing on the mechanics of REC/DEL database creation, but it provides a guideline how one systematically creates categories of deliverables and receivables for ground data system components...

ground data system (GDS)↗

X-ray satellite (ROSAT)

With regards to technical performance, the project is running according to plan. An increase in total cost outlay was required. The new Dornier Systems schedule projects ROSAT launch readiness for April 27, 1988. However, as a result of the Challenger accident, no binding launch date has been received from NASA. The thirteenth status review was conducted at the prime contractor in March, 1986. Assembly of the FM mirror system has been interrupted due to irregularities in the gold damping; in addition, mission operation and simulator development are effected by understaffing. Postponements have been announced in the data transmission and components acquisition subsystems.

Source record↗

Keeping Promises

Commitments are between people, not schedules. Project management as practiced today creates a "commitment-free zone," because it assumes that people will commit to centrally managed schedules without providing a mechanism to ensure their work can be done. So they give it their best, but something always seems to come up ..."I tried, but you know how it is." This form of project management does not provide a mechanism to ensure that what should be done, can in fact be done at the required moment. Too often, promises reliable promise. made in coordination meetings are conditional and unreliable. It has been my experience that at times trust can be low and hard to build in this environment. The absence of reliable promises explains why on well-run projects, people are often only completing 30-50 percent of the deliverables they d promised for the week. We all know what a promise is; we have plenty of experience making them and receiving them from others. So what s the problem? The sad fact is that the project environment-like many other work environments- is often so filled with systemic dishonesty, that we don t expect promises that are reliable. Project managers excel when they manage their projects as networks of commitments and help their people learn to elicit and make reliable promises.

Howell, Gregory A.↗

Integrated Test Approach

This paper describes a testing methodology undertaken on the Facilities Development and Operations Contract (FDOC) by Lockheed Martin. The methodology was defined with the intent of reducing project schedule time to enable NASA's Johnson Space Center (JSC) to be able to deliver the Mission Control Center (MCC) 21 project as quickly as possible. 21 represents the 21st century where NASA JSC is updating its control center with new technology and operational concepts in order to support NASA customers wanting to use control center assets to support space vehicle operations. In collaboration with the NASA customer, a new test concept was conceived early during MCC21 project planning with the goal of reducing project delivery time. One enabler that could help reduce delivery time was testing. Within the project, testing was performed by two entities, software development responsible for subsystem testing and system test responsible for system integration testing. The MCC21 project took a deliberate review of testing to determine how it could be performed differently to realize an overall reduction in test time to support the goal of a more rapid project delivery.

Cotton, Will↗

NASA Aerosciences Perspective on Proposed De-Scope of Ares I-X Development Flight Instrumentation

This position paper is written as a result of a number of emails and a presentation that have recently been circulated concerning the potential reduction of Development Flight Instrumentation (DFI) to be included on the Ares I-X flight test vehicle. A reduction in instrumentation has been proposed presumably to reduce project costs and relieve project schedule pressures. This proposal has generated a significant amount of discussion on both sides of the issue, primarily from those within the project. The intention here is to provide a perspective on this issue from outside the mainline project.

Schuster, David M.↗

Software Schedules Missions, Aids Project Management

NASA missions require advanced planning, scheduling, and management, and the Space Agency has worked extensively to develop the programs and software suites necessary to facilitate these complex missions. These enormously intricate undertakings have hundreds of active components that need constant management and monitoring. It is no surprise, then, that the software developed for these tasks is often applicable in other high-stress, complex environments, like in government or industrial settings. NASA work over the past few years has resulted in a handful of new scheduling, knowledge-management, and research tools developed under contract with one of NASA s partners. These tools have the unique responsibility of supporting NASA missions, but they are also finding uses outside of the Space Program.

Source record↗

Successful Completion of the JWST OGSE2 Cryogenic Test at JSC Chamber-A While Managing Numerous Challenges

The James Webb Space Telescope (JWST) Optical Telescope Element (OTE) assembly is the largest optically stable infrared-optimized telescope currently being manufactured and assembled, and scheduled for launch in 2018. The JWST OTE, including the primary mirrors, secondary mirror, and the Aft Optics Subsystems (AOS) are designed to be passively cooled and operate at near 45 degrees Kelvin. Due to the size of its large sunshield in relation to existing test facilities, JWST cannot be optically or thermally tested as a complete observatory-level system at flight temperatures. As a result, the telescope portion along with its instrument complement will be tested as a single unit very late in the program, and on the program schedule critical path. To mitigate schedule risks, a set of 'pathfinder' cryogenic tests will be performed to reduce program risks by demonstrating the optical testing capabilities of the facility, characterizing telescope thermal performance, and allowing project personnel to learn valuable testing lessons off-line. This paper describes the 'pathfinder' cryogenic test program, focusing on the recently completed second test in the series called the Optical Ground Support Equipment 2 (OGSE2) test. The JWST OGSE2 was successfully completed within the allocated project schedule while faced with numerous conflicting thermal requirements during cool-down to the final cryogenic operational temperatures, and during warm-up after the cryo-stable optical tests. The challenges include developing a pre-test cool-down and warm-up profiles without a reliable method to predict the thermal behaviors in a rarified helium environment, and managing the test article hardware safety driven by the project Limits and Constraints (L&C's). Furthermore, OGSE2 test included the time critical Aft Optics Subsystem (AOS), a part of the flight Optical Telescope Element that would need to be placed back in the overall telescope assembly integrations. The OGSE2 test requirements included the strict adherence of the project contamination controls due to the presence of the contamination sensitive flight optical elements. The test operations required close coordination of numerous personnel while they being exposed and trained for the 'final' combined OTE and instrument cryo-test in 2017. This paper will also encompass the OGSE2 thermal data look-back review.

JWST OGSE2 Cryogenic Test↗

Development of High Temperature (>700°C) Molten Salt Pump Technology for Generation 3 Solar Power Tower Systems

Bearings are required for long-shafted pumps historically used in concentrating solar thermal power applications. For molten chloride salts, bearings for such service conditions are not commercially available, nor has a design been demonstrated to work. Therefore, a project was sponsored by the Department of Energy’s Solar Energy Technologies Office for the development and demonstration of a submerged bearing for use in chloride salt pumps. This project’s tasks covered the tribological testing of candidate materials and the design, fabrication, testing, and post-test analysis of full-scale salt-compatible bearings. This work expands upon previous work. The effects of potential particulate in the salt were investigated through tribological bench testing. Through 11 tests, the MgO particulate size and concentration in a molten chloride salt were varied, and the effects on friction, wear rate, and wear characteristics were recorded. Novel journal bearings for chloride salt service were designed and fabricated based on these results. The bearings were of a relevant scale (i.e., for a 1.5 in. pump shaft) to demonstrate the technology with respect to further scale-up. The bearings were made of Haynes 244 and Yttria Partially Stabilized Zirconia. A custom bearing test rig, salt tanks, and associated infrastructure (e.g., heaters, tanks, transfer lines, gas flow control) were designed, procured, and installed. A few issues were encountered in the system fabrication process, resulting in delay of the project schedule. The system was successfully fabricated and assembled. Heating, cover gas, and pump motor systems were integrated into the control logic. This progress of the bearing test system represents a significant step forward towards demonstrating this promising technology. Nevertheless, the project ended before testing of the full-scale bearings could be performed.

14 SOLAR ENERGY↗

Independent Verification and Validation (IV and V) - Adding Mission Assurance to NASA Flight Software

The NASA Independent Verification and Validation (IV&V) Facility objective is to identify potential defects in flight software using independent analysis techniques. This paper describes the tailored IV&V techniques that have been developed in support of critical interactions on the Mars Science Laboratory (MSL) project, scheduled to launch in November, 2011. The IV&V techniques for interface analysis use independently developed sequence diagrams of critical scenarios. The results from these analyses have had a positive impact on the requirements flow down, consistency amongst MSL requirements and identification of missing requirements. The results of these analyses and the positive impact to the MSL project are provided.

performance evaluation↗

The StarLight formation-flying interferometer system architecture

The StarLight Project, scheduled for a 6-month mission in 2006, will demonstrate the new technologies of spaceborne long-baseline optical interferometry and precision formation flying necessary for the Terrestrial Planet Finder and other future astropohysics missions.

StarLight Project interferometers↗

(abstract) FASTER -- A Tool for DSN Forecasting and Scheduling

FASTER, the Forecasting And Scheduling Tool for Earth-based Resources is a suite of software tools developed at JPL to aid in the process of allocating DSN 70 and 34 meter antennas and equipment to support deep space satellites and ground based astronomy. FASTER has been designed for use by a diverse user community, including mid-level managers, data entry and analysis teams, and project scheduling personnel. The system helps to automate many of the previously labor intensive tasks and ensure proper analysis and consistency throughout all phases of the allocation process. FASTER implements an interactive environment for both forecasting and scheduling. This paper will discuss technical aspects of the FASTER system, including forecasting and scheduling algorithms, issues related to large scale use of a scheduling and forecasting system, implications to the process in which a forecasting and scheduling system is embedded, and lessons learned and implications to similar systems.

forecasting↗

Surface Hold Advisor Using Critical Sections

The Surface Hold Advisor Using Critical Sections is a system and method for providing hold advisories to surface controllers to prevent gridlock and resolve crossing and merging conflicts among vehicles traversing a vertex-edge graph representing a surface traffic network on an airport surface. The Advisor performs pair-wise comparisons of current position and projected path of each vehicle with other surface vehicles to detect conflicts, determine critical sections, and provide hold advisories to traffic controllers recommending vehicles stop at entry points to protected zones around identified critical sections. A critical section defines a segment of the vertex-edge graph where vehicles are in crossing or merging or opposite direction gridlock contention. The Advisor detects critical sections without reference to scheduled, projected or required times along assigned vehicle paths, and generates hold advisories to prevent conflicts without requiring network path direction-of-movement rules and without requiring rerouting, rescheduling or other network optimization solutions.

Law, Caleb Hoi Kei↗

When is Testing Sufficient

The Software Assurance Technology Center (SATC) at NASA Goddard Space Flight Center has been investigating how projects can determine when sufficient testing has been completed. For most projects, schedules are underestimated, and the last phase of the software development, testing, must be decreased. Two questions are frequently asked: "To what extent is the software error-free? " and "How much time and effort is required to detect and remove the remaining errors? " Clearly, neither question can be answered with absolute certainty. Nonetheless, the ability to answer these questions with some acceptable level of confidence is highly desirable. First, knowing the extent to which a product is error-free, we can judge when it is time to terminate testing. Secondly, if errors are judged to be present, we can perform a cost/benefit trade-off analysis to estimate when the software will be ready for use and at what cost. This paper explains the efforts of the SATC to help projects determine what is sufficient testing and when is the most cost-effective time to stop testing.

Rosenberg, Linda H.↗