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 361 records · Page 20
All sourcesNASA NTRSDOE OSTI
NASA NTRS1979

Anti-reflection Coatings on Large Area Glass Sheets

The first quarter of a one-year program designed to research and perfect a method of producing antireflective coatings on large glass sheets through the use of sodium silicate hardened by exposure to acid is reported. The requirements for a linear motion device used to produce uniform sodium silicate films were determined. A search for a commercially available device is underway. Sodium silicate solutions of varying concentrations were prepared. Determinations of the physical properties relevant to film thickness are in progress. In addition, material costs are being recorded for later use in a cost analysis of the method. All tasks of the project are proceeding according to schedule. Of the tasks, only the sodium silicate solution preparation is complete.

Pastirik, E.↗
NASA NTRS1979

The Development of a Method of Producing Etch Resistant Wax Patterns on Solar Cells

The first quarter of a one-year program to investigate the production of patterned etch resistant wax coatings on solar cell substrates by printing is reported. Master molds for printing plates were produced for the plates. The resist wax is being studied to determine its relevant physical properties. A printing device is currently in design, and material costs are being compiled as first step in a cost analysis task. All phases of the project are proceeding according to schedule. No specific phases are yet completed.

Pastirik, E.↗
NASA NTRS1987

Large capacity cryopropellant orbital storage facility

A comprehensive study was performed to develop the major features of a large capacity orbital propellant storage facility for the space-based cryogenic orbital transfer vehicle. Projected propellant usage and delivery schedules can be accommodated by two orbital tank sets of 100,000 lb storage capacity, with advanced missions expected to require increased capacity. Information is given on tank pressurization schemes, propellant transfer configurations, pump specifications, the refrigeration system, and flight tests.

Schuster, J. R.↗
NASA NTRS1988

Development and demonstration of an on-board mission planner for helicopters

Mission management tasks can be distributed within a planning hierarchy, where each level of the hierarchy addresses a scope of action, and associated time scale or planning horizon, and requirements for plan generation response time. The current work is focused on the far-field planning subproblem, with a scope and planning horizon encompassing the entire mission and with a response time required to be about two minutes. The far-feld planning problem is posed as a constrained optimization problem and algorithms and structural organizations are proposed for the solution. Algorithms are implemented in a developmental environment, and performance is assessed with respect to optimality and feasibility for the intended application and in comparison with alternative algorithms. This is done for the three major components of far-field planning: goal planning, waypoint path planning, and timeline management. It appears feasible to meet performance requirements on a 10 Mips flyable processor (dedicated to far-field planning) using a heuristically-guided simulated annealing technique for the goal planner, a modified A* search for the waypoint path planner, and a speed scheduling technique developed for this project.

Deutsch, Owen L.↗
NASA NTRS1991

Software engineering ethics

Software engineering ethics is reviewed. The following subject areas are covered: lack of a system viewpoint; arrogance of PC DOS software vendors; violation od upward compatibility; internet worm; internet worm revisited; student cheating and company hiring interviews; computing practitioners and the commodity market; new projects and old programming languages; schedule and budget; and recent public domain comments.

Bown, Rodney L.↗
NASA NTRS1992

Advanced solid rocket motor project status

The objectives of the project are the following: (1) to improve system safety and reliability; (2) to improve Space Shuttle Payload performance - 12,000 lb; (3) to optimize program cost; and (4) to promote a competitive solid rocket motor industry. The topics are presented in viewgraph form and include the Advanced Solid Rocket Motor (ASRM) project team, ASRM design, design schedules, and technical issues.

Coates, Keith↗
NASA NTRS1992

Automation of closed environments in space for human comfort and safety

This report culminates the work accomplished during a three year design project on the automation of an Environmental Control and Life Support System (ECLSS) suitable for space travel and colonization. The system would provide a comfortable living environment in space that is fully functional with limited human supervision. A completely automated ECLSS would increase astronaut productivity while contributing to their safety and comfort. The first section of this report, section 1.0, briefly explains the project, its goals, and the scheduling used by the team in meeting these goals. Section 2.0 presents an in-depth look at each of the component subsystems. Each subsection describes the mathematical modeling and computer simulation used to represent that portion of the system. The individual models have been integrated into a complete computer simulation of the CO2 removal process. In section 3.0, the two simulation control schemes are described. The classical control approach uses traditional methods to control the mechanical equipment. The expert control system uses fuzzy logic and artificial intelligence to control the system. By integrating the two control systems with the mathematical computer simulation, the effectiveness of the two schemes can be compared. The results are then used as proof of concept in considering new control schemes for the entire ECLSS. Section 4.0 covers the results and trends observed when the model was subjected to different test situations. These results provide insight into the operating procedures of the model and the different control schemes. The appendix, section 5.0, contains summaries of lectures presented during the past year, homework assignments, and the completed source code used for the computer simulation and control system.

Source record↗
NASA NTRS1991

Space transfer vehicle concepts and requirements study. Volume 3, book 1: Program cost estimates

The Space Transfer Vehicle (STV) Concepts and Requirements Study cost estimate and program planning analysis is presented. The cost estimating technique used to support STV system, subsystem, and component cost analysis is a mixture of parametric cost estimating and selective cost analogy approaches. The parametric cost analysis is aimed at developing cost-effective aerobrake, crew module, tank module, and lander designs with the parametric cost estimates data. This is accomplished using cost as a design parameter in an iterative process with conceptual design input information. The parametric estimating approach segregates costs by major program life cycle phase (development, production, integration, and launch support). These phases are further broken out into major hardware subsystems, software functions, and tasks according to the STV preliminary program work breakdown structure (WBS). The WBS is defined to a low enough level of detail by the study team to highlight STV system cost drivers. This level of cost visibility provided the basis for cost sensitivity analysis against various design approaches aimed at achieving a cost-effective design. The cost approach, methodology, and rationale are described. A chronological record of the interim review material relating to cost analysis is included along with a brief summary of the study contract tasks accomplished during that period of review and the key conclusions or observations identified that relate to STV program cost estimates. The STV life cycle costs are estimated on the proprietary parametric cost model (PCM) with inputs organized by a project WBS. Preliminary life cycle schedules are also included.

Peffley, Al F.↗
NASA NTRS1996

A global spacecraft control network for spacecraft autonomy research

The development and implementation of the Automated Space System Experimental Testbed (ASSET) space operations and control network, is reported on. This network will serve as a command and control architecture for spacecraft operations and will offer a real testbed for the application and validation of advanced autonomous spacecraft operations strategies. The proposed network will initially consist of globally distributed amateur radio ground stations at locations throughout North America and Europe. These stations will be linked via Internet to various control centers. The Stanford (CA) control center will be capable of human and computer based decision making for the coordination of user experiments, resource scheduling and fault management. The project's system architecture is described together with its proposed use as a command and control system, its value as a testbed for spacecraft autonomy research, and its current implementation.

Kitts, Christopher A.↗
NASA NTRS1999

JPL Institutional Parts Program

This viewgraph presentation focuses on the past, present, and future space parts environment. The past environment was characterized by long lead time flagship missions having substantial support from NASA and DOD. The future environment is characterized by many BFC missions, short development cycles, smaller projects and shorter part delivery schedules. These ideas are elaborated upon.

Clark, Kevin P.↗
NASA NTRS1995

Software Transition Project Retrospectives and the Application of SEL Effort Estimation Model and Boehm's COCOMO to Complex Software Transition Projects

The Multimission Image Processing Subsystem (MIPS) at the Jet Propulsion Laboratory (JPL) has managed transitions of application software sets from one operating system and hardware platform to multiple operating systems and hardware platforms. As a part of these transitions, cost estimates were generated from the personal experience of in-house developers and managers to calculate the total effort required for such projects. Productivity measures have been collected for two such transitions, one very large and the other relatively small in terms of source lines of code. These estimates used a cost estimation model similar to the Software Engineering Laboratory (SEL) Effort Estimation Model. Experience in transitioning software within JPL MIPS have uncovered a high incidence of interface complexity. Interfaces, both internal and external to individual software applications, have contributed to software transition project complexity, and thus to scheduling difficulties and larger than anticipated design work on software to be ported.

SEL Boehm COCOMO↗
NASA NTRS2005

Failure Assessment

Three questions to which software developers want accurate, precise answers are "How can the software system fail?", "mat bad things will happen if the software fails?t', and "How many failures will the software experience?". Numerous techniques have been devised to answer these questions; three of the best known are: 1) Software Fault Tree Analysis (SFTA) 2) Software Failure Modes, Effects, and Criticality Analysis (SFMECA 3) Software Fault/Failure Modeling. SFTA and SFMECA have been successfully used to analyze the flight software for a number of robotic planetary exploration missions, including Galileo, Cassini, and Deep Space 1. Given the increasing interest in reusing software components from mission to mission, one of us has developed techniques for reusing the corresponding portions of the SFTA and SFMECA, reducing the effort required to conduct these analyses. SFTA has also been shown to be effective in analyzing the security aspects of software systems; intrusion mechanisms and effects can easily be modeled using these techniques. The Bi- Directional Safety Analysis (BDSA) method combines a forward search (similar to SFMECA) from potential failure modes to their effects, with a backward search (similar to SFTA) from feasible hazards to the contributing causes of each hazard. BDSA offers an efficient way to identify latent failures. Recent work has extended BDSA to product-line applications such as flight-instrumentation displays and developed tool support for the reuse of the failure-analysis artifacts within a product line. BDSA has also been streamlined to support those projects having tight cost and/or schedule constraints for their failure analysis efforts. We discuss lessons learned from practice, describe available tools, and identi@ some future directions for the topic. A substantial amount of research has been devoted to estimating the number of failures that a software system will experience during test and operations, as well as the number of faults that have been inserted into that system during its development. One of us has found that the amount of structural change to a system during its development is strongly related to the number of faults inserted into it. Using techniques requiring no additional effort on the part of the development organization, the required measurements of structural evolution can be easily obtained from a development effort's configuration management system and readily transformed into an estimate of fault content. So far, structure-fault relationships have been identified for source code; current work seeks to examine artifacts available earlier in the lifecycle to determine if similar relationships between structure and fault content can be found. In particular, relationships between requirements change requests and the number of faults inserted into the implemented system would provide a significant improvement in our ability to control software quality during the early development phases.

fault tree↗
NASA NTRS2006

Developing Formal Correctness Properties from Natural Language Requirements

This viewgraph presentation reviews the rationale of the program to transform natural language specifications into formal notation.Specifically, automate generation of Linear Temporal Logic (LTL)correctness properties from natural language temporal specifications. There are several reasons for this approach (1) Model-based techniques becoming more widely accepted, (2) Analytical verification techniques (e.g., model checking, theorem proving) significantly more effective at detecting types of specification design errors (e.g., race conditions, deadlock) than manual inspection, (3) Many requirements still written in natural language, which results in a high learning curve for specification languages, associated tools and increased schedule and budget pressure on projects reduce training opportunities for engineers, and (4) Formulation of correctness properties for system models can be a difficult problem. This has relevance to NASA in that it would simplify development of formal correctness properties, lead to more widespread use of model-based specification, design techniques, assist in earlier identification of defects and reduce residual defect content for space mission software systems. The presentation also discusses: potential applications, accomplishments and/or technological transfer potential and the next steps.

requirements engineering↗
NASA NTRS2005

MSL Project Update

Mars Science Lab (MSL) Project activities over the last 3-4 months focused on: a) Payload accommodation; b) Flight system architecture definitization; c) Program architecture support. Baseline project concept is to develop and fly two identical vehicles with launches in 2009 and 2011: a) Significant programmatic uncertainty remains due to NASA strategic issues (Shuttle Return to flight, Hubble servicing, CEV, etc.); b) Final "decisions" on future program not likely for 3-4 months; c) To maintain viability for a 2009 launch, the project must rapidly move into implementation mode despite this uncertainty. Near term activities: a) Converge baseline flight system architecture & instrument accommodation - June; b) Instrument accomodation reviews (IARs) are completed for DAN, MSSS instruments; c) Develop project-wide implementation plan & integrated schedule - June; d) Conduct grassroots cost exercise - July/August; e) Hold Preliminary Mission System Review - September.

Mars↗
NASA NTRS2007

Program Management Tool

The Program Management Tool (PMT) is a comprehensive, Web-enabled business intelligence software tool for assisting program and project managers within NASA enterprises in gathering, comprehending, and disseminating information on the progress of their programs and projects. The PMT provides planning and management support for implementing NASA programmatic and project management processes and requirements. It provides an online environment for program and line management to develop, communicate, and manage their programs, projects, and tasks in a comprehensive tool suite. The information managed by use of the PMT can include monthly reports as well as data on goals, deliverables, milestones, business processes, personnel, task plans, monthly reports, and budgetary allocations. The PMT provides an intuitive and enhanced Web interface to automate the tedious process of gathering and sharing monthly progress reports, task plans, financial data, and other information on project resources based on technical, schedule, budget, and management criteria and merits. The PMT is consistent with the latest Web standards and software practices, including the use of Extensible Markup Language (XML) for exchanging data and the WebDAV (Web Distributed Authoring and Versioning) protocol for collaborative management of documents. The PMT provides graphical displays of resource allocations in the form of bar and pie charts using Microsoft Excel Visual Basic for Application (VBA) libraries. The PMT has an extensible architecture that enables integration of PMT with other strategic-information software systems, including, for example, the Erasmus reporting system, now part of the NASA Integrated Enterprise Management Program (IEMP) tool suite, at NASA Marshall Space Flight Center (MSFC). The PMT data architecture provides automated and extensive software interfaces and reports to various strategic information systems to eliminate duplicative human entries and minimize data integrity issues among various NASA systems that impact schedules and planning.

Gawadiak, Yuri↗
NASA NTRS2011

DXL: A Sounding Rocket Mission for the Study of Solar Wind Charge Exchange and Local Hot Bubble X-Ray Emission

The Diffuse X-rays from the Local galaxy (DXL) mission is an approved sounding rocket project with a first launch scheduled around December 2012. Its goal is to identify and separate the X-ray emission generated by solar wind charge exchange from that of the local hot bubble to improve our understanding of both. With 1,000 square centimeters proportional counters and grasp of about 10 square centimeters sr both in the 1/4 and 3/4 keV bands, DXL will achieve in a 5-minute flight what cannot be achieved by current and future X-ray satellites.

Galeazzi, M.↗
NASA NTRS2012

An Overview of MODIS On-orbit Operation, Calibration, and Lessons

Two nearly identical copies of the Moderate Resolution Imaging Spectroradiometer (MODIS) have successfully operated onboard the Terra and Aqua spacecraft for more than II years and 9 years since their launch in December 1999 and May 2002, respectively. MODIS is a key instrument for the NASA's Earth Observing System (EOS) missions. MODIS observations have produced an unprecedented amount and a broad range of data products and significantly benefited the science and user community. Its follow-on instrument, the Visible/Infrared Imager Radiometer Suite (VIIRS) on-board the NPOESS Preparatory Project (NPP) spacecraft, is currently scheduled for launch in late October, 2011. The NPP serves as a bridge mission between EOS and the Joint Polar Satellite System (JPSS). MODIS collects data in 36 spectral bands, covering spectral regions from visible (VIS) to long-wave infrared (L WIR), and at three different spatial resolutions. Because of its stringent design requirements, MODIS was built with a complete set of onboard calibrators, including a solar diffuser (SO), a solar diffuser stability monitor (SDSM), a blackbody (BB), a spectroradiometric calibration assembly (SRCA), and a space view (SV) port. Except for tbe SRCA, VIlRS carries the same set of onboard calibrators as MODIS. The SD/SDSM system is used together to calibrate tbe reflective solar bands (RSB). The BB is designed for the thermal emissive bands (TEB) calibration. Similar to Terra and Aqua MODIS, VIlRS will also make regular lunar observations to monitor RSB radiometric calibration stability. In this paper, we provide an overview of MODIS on-orbit operation and calibration activities and present issues identified and lessons learned from mission-long instrument operations and implementation of various calibration and characterization strategies. Examples of both Terra and Aqua MODIS instrument on-orbit performance, including their similarities and unique characteristics, are discussed in tbe context of what might be expected from and benefited to tbe NPP VIlRS operation and calibration. It is anticipated that MODIS experience and lessons will also provide valuable information for other earth observing missions/sensors.

Xiong, Jack↗
NASA NTRS2014

America's Next Great Ship: Space Launch System Core Stage Transitioning from Design to Manufacturing

The Space Launch System (SLS) Program is essential to achieving the Nation's and NASA's goal of human exploration and scientific investigation of the solar system. As a multi-element program with emphasis on safety, affordability, and sustainability, SLS is becoming America's next great ship of exploration. The SLS Core Stage includes avionics, main propulsion system, pressure vessels, thrust vector control, and structures. Boeing manufactures and assembles the SLS core stage at the Michoud Assembly Facility (MAF) in New Orleans, LA, a historical production center for Saturn V and Space Shuttle programs. As the transition from design to manufacturing progresses, the importance of a well-executed manufacturing, assembly, and operation (MA&O) plan is crucial to meeting performance objectives. Boeing employs classic techniques such as critical path analysis and facility requirements definition as well as innovative approaches such as Constraint Based Scheduling (CBS) and Cirtical Chain Project Management (CCPM) theory to provide a comprehensive suite of project management tools to manage the health of the baseline plan on both a macro (overall project) and micro level (factory areas). These tools coordinate data from multiple business systems and provide a robust network to support Material & Capacity Requirements Planning (MRP/CRP) and priorities. Coupled with these tools and a highly skilled workforce, Boeing is orchestrating the parallel buildup of five major sub assemblies throughout the factory. Boeing and NASA are transforming MAF to host state of the art processes, equipment and tooling, the most prominent of which is the Vertical Assembly Center (VAC), the largest weld tool in the world. In concert, a global supply chain is delivering a range of structural elements and component parts necessary to enable an on-time delivery of the integrated Core Stage. SLS is on plan to launch humanity into the next phase of space exploration.

Birkenstock, Benjamin↗