PV Reliability Development Lessons from JPL's Flat Plate Solar Array Project
No abstract available
flat plate solar arrays project↗
SEARCH · Search NASA
Results for “JPL 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.
PV Reliability Development Lessons from JPL's Flat Plate Solar Array Project
Key reliability and engineering lessons learned from the 20-year history of the Jet Propulsion Laboratory's Flat-Plate Solar Array Project and thin film module reliability research activities are presented and analyzed. Particular emphasis is placed on lessons applicable to evolving new module technologies and the organizations involved with these technologies. The user-specific demand for reliability is a strong function of the application, its location, and its expected duration. Lessons relative to effective means of specifying reliability are described, and commonly used test requirements are assessed from the standpoint of which are the most troublesome to pass, and which correlate best with field experience. Module design lessons are also summarized, including the significance of the most frequently encountered failure mechanisms and the role of encapsulate and cell reliability in determining module reliability. Lessons pertaining to research, design, and test approaches include the historical role and usefulness of qualification tests and field tests.
photovoltaics↗
Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challenge
The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), manages the project and is responsible for flight operation; Orbital Sciences Corporation (OSC), is the spacecraft builder and is responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), is responsible for science planning and operations. As a cost-capped mission, one of Dawn's implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL's ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL's GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project's commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to fundamental systems engineering practices: decomposition of the project request into manageable requirements; integration of multiple ground disciplines and experts into a focused team effort; definition of a structured yet flexible development process; definition of an in-process risk reduction plan; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.
Ground Data System (GDS)↗
Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challange
The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), responsible for project management and flight operations; Orbital Sciences Corporation (OSC), spacecraft builder and responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), responsible for science planning and operations. As a cost-capped mission, one of Dawn s implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL s ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL s GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project s commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to an overall systems engineering process and fundamental systems engineering practices: decomposition of the project request into manageable requirements; definition of a structured yet flexible development process; integration of multiple ground disciplines and experts into a focused team effort; in-process risk management; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.
systems engineering↗
Improving operations: Metrics to Results
As a result of the mission failure of the Mars Climate Orbiter (MCO) spacecraft in 1999, the Jet Propulsion Laboratory (JPL) initiated the development of a Mission Operations Assurance (MOA) program to be implemented across all flight projects managed by JPL. One of the initiatives undertaken in 2001 was the collection of data on command file errors occurring in the operational phase of the mission. This paper defines command file errors and how and where they occur in the operations process. It also describes the problem reporting system (PRS) in use for mission operations at JPL. We examine the recent modifications to the PRS that enable the collection of metrics, specifically on command file errors. This paper discusses what the data show us since metrics have been collected for the operational missions conducted by JPL. We examine the evolution of an operational working group initiative to evaluate proximate, contributing, and root causes for the errors. As part of this discussion we see what the metrics have indicated over a decade. At the macro level, we can say that the aggregate command file error rate has been cut to roughly one third of the initial 2001 level by the end of 2011. Additionally, we explore efficient and innovative means to continually integrate the findings and recommendations from the working group back into the flight operations environment.
command file errors↗
The Space Flight Operations Center first phase - Lessons learned
This paper is a retrospective look at the Space Flight Operations Center Project; a large, complex, multimission ground data system which is currently under development at the Jet Propulsion Laboratory (JPL), Pasadena. The Project was established in February 1984 and will be completed in April 1992 when the Magellan, Voyager, Ulysses, Galileo and Mars Observer Projects will be fully supported. The first phase of this project covers the development of a subset of multimission Baseline subsystems, the development of the mission-specific adaptations to this Baseline set for the Magellan Project, the development of a Magellan-specific high rate processor together with the delivery of these subsystems to operations. This first phase became operational in January 1989 in readiness for the Magellan launch in May 1989.
Gainsborough, A. J.↗
A Virtual Collaborative Environment for Mars Surveyor Landing Site Studies
Over the past year and a half, the Center for Mars Exploration (CMEX) at NASA Ames Research Center (ARC) has been working with the Mars Surveyor Project Office at JPL to promote interactions among the planetary community and to coordinate landing site activities for the Mars Surveyor Project Office. To date, CMEX has been responsible for organizing the first two Mars Surveyor Landing Site workshops, web-archiving resulting information from these workshops, aiding in science evaluations of candidate landing sites, and serving as a liaison between the community and the Project. Most recently, CMEX has also been working with information technologists at Ames to develop a state-of-the-art collaborative web site environment to foster interaction of interested members of the planetary community with the Mars Surveyor Program and the Project Office. The web site will continue to evolve over the next several years as new tools and features are added to support the ongoing Mars Surveyor missions.
Gulick, V.C.↗
A Virtual Collaborative Environment for Mars Surveyor Landing Site Studies
Over the past year and a half, the Center for Mars Exploration (CMEX) at NASA Ames Research Center (ARC) has been working with the Mars Surveyor Project Office at JPL to promote interactions among the planetary community and to coordinate landing site activities for the Mars Surveyor Project Office. To date, CMEX has been responsible for organizing the first two Mars Surveyor Landing Site workshops, web-archiving resulting information from these workshops, aiding in science evaluations of candidate landing sites, and serving as a liaison between the community and the Project. Most recently, CMEX has also been working with information technologists at Ames to develop a state-of-the-art collaborative web site environment to foster interaction of interested members of the planetary community with the Mars Surveyor Program and the Project Office. The web site will continue to evolve over the next several years as new tools and features are added to support the ongoing Mars Surveyor missions.
Gulick, V. C.↗
Mariner Jupiter/Saturn 1977 - The mission frame.
Following the cancellation of the Outer Planet Grand Tour Project, NASA and JPL examined less ambitious, alternative missions for exploring the outer planets. The mission that proved most attractive scientifically and fits within the projected NASA budget constraints embraces dual flights to Jupiter and Saturn, with launch in 1977. NASA has implemented it as the Mariner Jupiter/Saturn 1977 (MJS77) Project. The MJS77 mission covers exploratory investigations of the Jupiter and Saturn planetary systems and the interplanetary medium out to Saturn. Items of special interest include Jupiter's great red spot, the question of Io's anomalous brightening and phenomena associated with its EM behavior. After Saturn encounter, the spacecraft will escape the solar system in the general direction of the solar apex.
Bourke, R. D.↗
JPL, NASA and the Historical Record: Key Events/Documents in Lunar and Mars Exploration
This document represents a presentation about the Jet Propulsion Laboratory (JPL) historical archives in the area of Lunar and Martian Exploration. The JPL archives documents the history of JPL's flight projects, research and development activities and administrative operations. The archives are in a variety of format. The presentation reviews the information available through the JPL archives web site, information available through the Regional Planetary Image Facility web site, and the information on past missions available through the web sites. The presentation also reviews the NASA historical resources at the NASA History Office and the National Archives and Records Administration.
Hooks, Michael Q.↗
Technology Assessment of Doe's 55-we Stirling Technology Demonstrator Convector (TDC)
The Department of Energy (DOE), Germantown, Maryland and the NASA Glenn Research Center (GRC), Cleveland, Ohio are developing a Stirling Convertor for an advanced radioisotope power system as a potential power source for spacecraft on-board electric power for NASA deep space science missions. The Stirling Convertor is being evaluated as an alternative high efficiency power source to replace Radioisotope Thermoelectric Generators (RTGs). Stirling Technology Company (STC), Kennewick, Washington, is developing the highly efficient, long life 55-We free-piston Stirling Convertor known as the Technology Demonstrator Convertor (TDC) under contract to DOE. GRC provides Stirling technology expertise under a Space Act Agreement with the DOE. Lockheed Martin Astronautics (LMA), Valley Forge, Pennsylvania is the current power system integrator for the Advanced Radioisotope Power System (ARPS) Project for the DOE. JPL is responsible for the Outer Planets/Solar Probe Project for NASA.
Furlong, Richard↗
EPOXI and Stardust NExT: The Management Challenges of Two Comet Flybys in Three Months
The EPOXI and Stardust NExT missions were missions of opportunity utilizing the Deep Impact and Stardust spacecraft, respectively. These new missions took advantage of the cost savings of utilizing spacecraft that were already flying for new science investigations. Both were retargeted to fly by an additional comet. EPOXI visited Hartley 2, significantly smaller than the other Jupiter family comets visited previously. Stardust NExT flew by Tempel 1, providing a second look at the comet previously studied by Deep Impact in 2005. Both projects were part of NASA's Discovery Program. In order to further save costs, the projects were combined into a single project office at JPL. This provided some efficiencies due to the similarity of the missions, but having the flybys space only three months apart posed challenges for the project management team to ensure each project was ready for its critical event and ensuring each received the proper support from the management team. The project office relied on an integrated calendar for tracking and scheduling meetings, reviews, and other key events. The project management team also coordinated their availability for both projects to maintain involvement with each team to ensure effective risk identification and management.
NExT (New Exploration of Tempel 1)↗
STS-99 / Endeavour SRTM Science Briefing and Applications from JSC
The primary objective of the STS-99 mission was to complete high resolution mapping of large sections of the Earth's surface using the Shuttle Radar Topography Mission (SRTM), a specially modified radar system. This radar system produced unrivaled 3-D images of the Earth's Surface. This videotape shows a science press briefing. The panel members are Michael Kobrick, the SRTM Project Scientist at JPL; Thomas Henning, SRTM Program Manager at the National Imagery and Mapping Agency; Diane Evans, the Director of the Earth Sciences Program at NASA; and Marian Werner, XSAR Project Manager for the DLR, Deutschen Zentrum fur Luft- und Raumfahrt, Germany's National Aerospace Research Center. Michael Kobrick explained the mechanics of interferometric measurements of the Earth. He explained and demonstrated with a scale model the deployable mast's use. He also explained the importance of the attitude and orbit determination avionics. A brief animated video showing how four beams would give a 225 km wide swath of the Earth topography was viewed. Thomas Henning discussed some of the usage of the digital terrain elevation data for flood relief planning, cell phone station placement, military planning for command and control centers, and flight simulation. He explained that public access to the most precise data would be limited. Diane Evans described data usage in flood prediction, earthquake fault identification and archeology. Marian Werner described the German and Italian input to the project. The questions from the press concerned the time to process this data, and the reasons for the limited access to the more precise data.
Source record↗
Compendium of Critiques of JPL Report SP-43-17: Automotive Technology Status and Projections Project
Almost 50 critiques of the Jet Propulsion Laboratory report SP-43-17 are presented together with the JPL responses.
Williams, A. N.↗
JPL's Space Flight Operations Center: Development project overview
The topics are covered in view graph form and include the following: (1) major elements of deep space flight programs; (2) development schedule; (3) primary design goals; (4) Space Flight Operations Center (SFOC) data systems architecture; (5) technical guidelines; (6) SFOC data system functional architecture; (7) typical SFOC node; (8) SFOC components; (9) SFOC software categories; (10) planned subsystem core diagram for Mars observer; (11) SFOC use of public domain/3rd party software; (12) SFOC hardware; (13) SFOC target six mission configuration; and (14) SFOC development status and plans.
Ebersole, M.↗
JPL's Real-Time Weather Processor project (RWP) metrics and observations at system completion
As an integral part of the overall upgraded National Airspace System (NAS), the objective of the Real-Time Weather Processor (RWP) project is to improve the quality of weather information and the timeliness of its dissemination to system users. To accomplish this, an RWP will be installed in each of the Center Weather Service Units (CWSUs), located in 21 of the 23 Air Route Traffic Control Centers (ARTCCs). The RWP System is a prototype system. It is planned that the software will be GFE and that production hardware will be acquired via industry competitive procurement. The ARTCC is a facility established to provide air traffic control service to aircraft operating on Instrument Flight Rules (IFR) flight plans within controlled airspace, principally during the en route phase of the flight. Covered here are requirement metrics, Software Problem Failure Reports (SPFRs), and Ada portability metrics and observations.
Loesh, Robert E.↗
Nonlinear Dynamic Behavior in the Cassini Spacecraft Modal Survey
In October 1997, the 6-ton robotic spacecraft, Cassini, will lift off from Cape Canaveral atop a Titan IV B rocket, beginning a 7-year journey to Saturn. Upon completion of that voyage, Cassini will send the Huygens probe into the atmosphere of Saturn's largest moon, Titan. Cassini will then spend years studying Saturn's vast realm of rings, icy moons, and magnetic fields. The size and complexity of this endeavor mandates the involvement of many organizations. The Jet Propulsion Laboratory (JPL) manages the project for NASA and is responsible for the spacecraft design, development, and assembly. The NASA Lewis Research Center is the launch system integrator. As is typical for such a spacecraft, a test-verified finite element model is required for loads analysis. JPL had responsibility for the Cassini modal survey and the development of the spacecraft test-verified finite element model. Test verification is a complex and sometimes subjective process. Because of this, NASA Lewis independently verified and validated the Cassini spacecraft modal survey.
Carney, Kelly S.↗
1393 Ring Bus at JPL: Description and Status
Completed Ring Bus IC V&V Phase - Ring Bus Test Plan Completed for SIM Project - Applicable to Other Projects Implemented a Avionics Bus Based upon the IEEE 1393 Standard - Excellent Starting Point for a General Purpose High-Speed Spacecraft Bus - Designed to Meet SIM Requirements for - Real-time deterministic, distributed systems. - Control system requirements - Fault detection and recovery Other JPL Projects Considering Implementation F'light Software Ring Bus Driver Module Began in 2006, Continues Participating in Standard Revision. Search for Earth-like planets orbiting nearby stars and measure the masses and orbits of the planets it finds. Survey 2000 nearby stars for planetary systems to learn whether our Solar System is unusual, or typical. Make a new catalog of star position 100 times more accurate than current measurements. Learn how our galaxy formed and will evolve by studying the dynamics of its stars. Critically test models of exactly how stars shine, including exotic objects like black holes, neutron stars and white dwarfs.
time synchronization↗