Your free source for specifications, standards, and handbooks
NASA - JPL
982-R120461, PROMETHEUS PROJECT FINAL REPORT
982-R120461, PROMETHEUS PROJECT FINAL REPORT. The Prometheus Project was an element of the NASA Prometheus Nuclear Systems and Technology Theme. (It was previously known as the Jupiter Icy Moons Orbiter (JIMO) Project, and its pre-project work was performed under the NASA Nuclear Systems Initiative.) The Project was authorized by the Formulation Authorization for the Project Prometheus Program, signed by the NASA Associate Administrator for Space Science, Dr. Ed Weiler, on March 18, 2003. (The Project was subsequently transferred to the NASA Exploration Systems Mission Directorate upon its establishment in February 2004.) The Agency funding unique project number for the Prometheus Project was UPN 982-00. Additional funding was provided through FY 04 on a technology development number, UPN 973-80. Work was authorized at NASA’s Jet Propulsion Laboratory (JPL) via formal Task Order from NASA. To guide the work in Phase A of the Project, a Preliminary Project Plan was executed in October 2003 by the JPL Center Director, Dr. Charles Elachi, and the Project Manager, John Casani, and the NASA Prometheus Director, Al Newhouse, and Associate Director, Ray Taylor. The Preliminary Project Plan was updated after addition of DOE Office of Naval Reactors (DOE NR) and Northrop Grumman Space Technologies (NGST) to the Project team. The updated plan was not signed by all parties due to notice that the Project would be discontinued.
Ident. Num:
982-R120461
Rev. Num:
-
982-R120461, PROMETHEUS PROJECT FINAL REPORT. The Prometheus Project was an element of the NASA Prometheus Nuclear Systems and Technology Theme. (It was previously known as the Jupiter Icy Moons Orbiter (JIMO) Project, and its pre-project work was performed under the NASA Nuclear Systems Initiative.) The Project was authorized by the Formulation Authorization for the Project Prometheus Program, signed by the NASA Associate Administrator for Space Science, Dr. Ed Weiler, on March 18, 2003. (The Project was subsequently transferred to the NASA Exploration Systems Mission Directorate upon its establishment in February 2004.) The Agency funding unique project number for the Prometheus Project was UPN 982-00. Additional funding was provided through FY 04 on a technology development number, UPN 973-80. Work was authorized at NASA’s Jet Propulsion Laboratory (JPL) via formal Task Order from NASA. To guide the work in Phase A of the Project, a Preliminary Project Plan was executed in October 2003 by the JPL Center Director, Dr. Charles Elachi, and the Project Manager, John Casani, and the NASA Prometheus Director, Al Newhouse, and Associate Director, Ray Taylor. The Preliminary Project Plan was updated after addition of DOE Office of Naval Reactors (DOE NR) and Northrop Grumman Space Technologies (NGST) to the Project team. The updated plan was not signed by all parties due to notice that the Project would be discontinued.
JPL Pub 00-06, An Introduction to Space Radiation Effects on Microelectronics
The use of microelectronic devices in spacecraft requires that these devices preserve their functionality in the radiation environment found in space. This introductory course presents a summary of the current understanding of the effects of radiation on microelectronic devices.
Ident. Num:
JPL Pub 00-06
The use of microelectronic devices in spacecraft requires that these devices preserve their functionality in the radiation environment found in space. This introductory course presents a summary of the current understanding of the effects of radiation on microelectronic devices.
JPL-D-1348 (REV. F), STANDARD ELECTROSTATIC DISCHARGE CONTROL
JPL-D-1348 (REV. F), STANDARD ELECTROSTATIC DISCHARGE CONTROL., This standard implements the requirements of JPL SPI 4-11-7, Control of Electrostatic Discharge, JPL D-560, Flight Systems Safety Requirements, paragraph 4.2.9.1, and JPL D-5357, Electronic Parts Program Requirements for Flight Equipment, paragraph 7.5 of Appdx. A and B. Ionizers shall be calibrated by the JPL Calibration Lab (4-2981) using a charge plate monitor and the method described in Calibration Procedure SL0168, Bench Top Air Ionizer Performance Procedure.
Ident. Num:
JPL-D-1348
Rev. Num:
F
JPL-D-1348 (REV. F), STANDARD ELECTROSTATIC DISCHARGE CONTROL., This standard implements the requirements of JPL SPI 4-11-7, Control of Electrostatic Discharge, JPL D-560, Flight Systems Safety Requirements, paragraph 4.2.9.1, and JPL D-5357, Electronic Parts Program Requirements for Flight Equipment, paragraph 7.5 of Appdx. A and B. Ionizers shall be calibrated by the JPL Calibration Lab (4-2981) using a charge plate monitor and the method described in Calibration Procedure SL0168, Bench Top Air Ionizer Performance Procedure.
JPL-D-15129, ANALOG-TO-DIGITAL CONVERTER PARTS EVALUATION FOR SPACE APPLICATIONS (31 OCT 1997)
JPL-D-15129, ANALOG-TO-DIGITAL CONVERTER PARTS EVALUATION FOR SPACE APPLICATIONS (31 OCT 1997). A variety of analog-to-digital converters (A/Ds) including the COTS (commercial-off-theshelf) parts were evaluated. They can be divided into four distinct groups as distinguished by their speed, power and resolution: high speed, low power; ultra high speed, low resolution; very high resolution, low power; and general purpose, low power. The details of the evaluation performed and results obtained are summarized in section 2.0 with a brief description of each evaluated part given in section 3.0.
Ident. Num:
JPL D-15129
Rev. Num:
-
JPL-D-15129, ANALOG-TO-DIGITAL CONVERTER PARTS EVALUATION FOR SPACE APPLICATIONS (31 OCT 1997). A variety of analog-to-digital converters (A/Ds) including the COTS (commercial-off-theshelf) parts were evaluated. They can be divided into four distinct groups as distinguished by their speed, power and resolution: high speed, low power; ultra high speed, low resolution; very high resolution, low power; and general purpose, low power. The details of the evaluation performed and results obtained are summarized in section 2.0 with a brief description of each evaluated part given in section 3.0.
JPL-D-15378, THE JPL SOFTWARE DEVELOPMENT PROCESS DESCRIPTION (REV. D) (15 NOV 1999)
JPL-D-15378, THE JPL SOFTWARE DEVELOPMENT PROCESS DESCRIPTION (REV. D) (15 NOV 1999)., This description of JPL’s Software Development Process Description (SDPD) contains general requirements, guidelines, and suggestions for defining and managing a software-intensive project1, project element, or task consistent with ISO 9001, as interpreted by ISO 9000-3, “Quality Management and Quality Assurance Standards — Part 3: Guidelines for the Application of 9001 to the Development, Maintenance, and Supply of Software.” The SDPD is consistent with NASA Policy Directive (NPD) 2820.1, NASA Software Policies, which identifies compliance with ISO 9001 (as described in 9000-3) as acceptable evidence that this policy directive has been implemented.
Ident. Num:
JPL-D-15378
Rev. Num:
D
JPL-D-15378, THE JPL SOFTWARE DEVELOPMENT PROCESS DESCRIPTION (REV. D) (15 NOV 1999)., This description of JPL’s Software Development Process Description (SDPD) contains general requirements, guidelines, and suggestions for defining and managing a software-intensive project1, project element, or task consistent with ISO 9001, as interpreted by ISO 9000-3, “Quality Management and Quality Assurance Standards — Part 3: Guidelines for the Application of 9001 to the Development, Maintenance, and Supply of Software.” The SDPD is consistent with NASA Policy Directive (NPD) 2820.1, NASA Software Policies, which identifies compliance with ISO 9001 (as described in 9000-3) as acceptable evidence that this policy directive has been implemented.
JPL-D-16307 (REV. 7), FACILITIES DESIGN STANDARDS (31 JUL 2006)
JPL-D-16307 (REV. 7), FACILITIES DESIGN STANDARDS (31 JUL 2006)., The goal of the Facility Design Standards is to maintain coordinated and consistent facility systems throughout the JPL institutional environment. This document is intended to: · Facilitate the construction process through a uniform set of standards; · Organize and maintain consistent materials, methods and equipment for construction projects; · Expedite equipment maintenance, repair, or replacement associated with facilities at JPL. The Standards are not intended to regulate or cover all areas of facility design and construction, but to address those institutional concerns important to JPL.
Ident. Num:
JPL-D-16307
Rev. Num:
7
JPL-D-16307 (REV. 7), FACILITIES DESIGN STANDARDS (31 JUL 2006)., The goal of the Facility Design Standards is to maintain coordinated and consistent facility systems throughout the JPL institutional environment. This document is intended to: · Facilitate the construction process through a uniform set of standards; · Organize and maintain consistent materials, methods and equipment for construction projects; · Expedite equipment maintenance, repair, or replacement associated with facilities at JPL. The Standards are not intended to regulate or cover all areas of facility design and construction, but to address those institutional concerns important to JPL.
JPL-D-17868 (REV.1), DESIGN, VERIFICATION/VALIDATION AND OPERATIONS PRINCIPLES FOR FLIGHT SYSTEMS
JPL-D-17868 (REV.1), DESIGN, VERIFICATION/VALIDATION AND OPERATIONS PRINCIPLES FOR FLIGHT SYSTEMS ., These principles apply to spacecraft, and to major payload/instruments. They apply to system contractor/partner as well as in-house/ sub-system project implementation modes.
Ident. Num:
JPL-D-17868
Rev. Num:
1
JPL-D-17868 (REV.1), DESIGN, VERIFICATION/VALIDATION AND OPERATIONS PRINCIPLES FOR FLIGHT SYSTEMS ., These principles apply to spacecraft, and to major payload/instruments. They apply to system contractor/partner as well as in-house/ sub-system project implementation modes.
JPL-D-20348A, JPL INSTITUTIONAL PARTS PROGRAM REQUIREMENTS
JPL INSTITUTIONAL PARTS PROGRAM REQUIREMENTS. Printed copies of this document may not be current and should not be relied on for official purposes. This document is the JPL baseline Institutional Parts Program Requirements (IPPR). This document shall act as a template for preparing and tailoring1 the Project Parts Program Requirements (PPPR) for Spacecraft, JPL Facility Science Instruments, and PI Science Instruments in conformance with Project requirements. Every Electrical, Electronic and Electromechanical (EEE) part intended for use in space flight shall be reviewed and approved for compatibility with the intended space environment and mission life. This document defines the baseline parts program requirements for all JPL missions1 including both spacecraft and instruments. Additional parts requirements may be necessary as a function of mission success requirements. Deviations resulting in the elimination or reduction of the parts requirements specified herein shall be documented in the Project Implementation Plan (PIP) accompanied with the IPPR Compliance Matrix, (JPL Rules! DocID 59353). Once the PPPR has been approved by both the Electronic Parts Engineering Office and Project organizations, deviations from the PPPR shall be documented via a Category B waiver. The current version is in the DMIE Information System at http://dmie *
Ident. Num:
JPL-D-20348
Rev. Num:
A
JPL INSTITUTIONAL PARTS PROGRAM REQUIREMENTS. Printed copies of this document may not be current and should not be relied on for official purposes. This document is the JPL baseline Institutional Parts Program Requirements (IPPR). This document shall act as a template for preparing and tailoring1 the Project Parts Program Requirements (PPPR) for Spacecraft, JPL Facility Science Instruments, and PI Science Instruments in conformance with Project requirements. Every Electrical, Electronic and Electromechanical (EEE) part intended for use in space flight shall be reviewed and approved for compatibility with the intended space environment and mission life. This document defines the baseline parts program requirements for all JPL missions1 including both spacecraft and instruments. Additional parts requirements may be necessary as a function of mission success requirements. Deviations resulting in the elimination or reduction of the parts requirements specified herein shall be documented in the Project Implementation Plan (PIP) accompanied with the IPPR Compliance Matrix, (JPL Rules! DocID 59353). Once the PPPR has been approved by both the Electronic Parts Engineering Office and Project organizations, deviations from the PPPR shall be documented via a Category B waiver. The current version is in the DMIE Information System at http://dmie *
JPL-D-28444, SOFTWARE FAULT ANALYSIS HANDBOOK - [SOFTWARE FAULT TREE ANALYSIS (SFTA) & SOFTWARE FAILURE MODES, EFFECTS AND CRITICALITY ANALYSIS (SFMEC
JPL-D-28444, SOFTWARE FAULT ANALYSIS HANDBOOK - [SOFTWARE FAULT TREE ANALYSIS (SFTA) & SOFTWARE FAILURE MODES, EFFECTS AND CRITICALITY ANALYSIS (SFMECA)] (2 MAY 2005)., The purpose of this document is to describe a standard process for use in performing Software Fault Tree Analysis (SFTA) and Software Failure Modes, Effects and Criticality Analysis (SFMECA) at JPL. The use of this document is not required and is meant only to aid in the creation and implementation of a standard project software analysis process. This document is intended to provide guidance for doing analyses for development of both flight and ground software. These mission and safety critical software analyses are techniques for validation of the software and hardware requirements and design through a systematic evaluation of potential failures and their impacts. The benefit of using these techniques is more reliable performance of the software through improved requirements, less re-design, mitigation for potential problems, and plans for corrective actions prior to failures.
Ident. Num:
JPL-D-28444
Rev. Num:
-
JPL-D-28444, SOFTWARE FAULT ANALYSIS HANDBOOK - [SOFTWARE FAULT TREE ANALYSIS (SFTA) & SOFTWARE FAILURE MODES, EFFECTS AND CRITICALITY ANALYSIS (SFMECA)] (2 MAY 2005)., The purpose of this document is to describe a standard process for use in performing Software Fault Tree Analysis (SFTA) and Software Failure Modes, Effects and Criticality Analysis (SFMECA) at JPL. The use of this document is not required and is meant only to aid in the creation and implementation of a standard project software analysis process. This document is intended to provide guidance for doing analyses for development of both flight and ground software. These mission and safety critical software analyses are techniques for validation of the software and hardware requirements and design through a systematic evaluation of potential failures and their impacts. The benefit of using these techniques is more reliable performance of the software through improved requirements, less re-design, mitigation for potential problems, and plans for corrective actions prior to failures.
JPL-D-5703, RELIABILITY ANALYSES HANDBOOK
JPL-D-5703, RELIABILITY ANALYSES HANDBOOK. This document provides guidelines for performing and reviewing reliability analyses associated with flight equipment. It is responsive to the analysis requirements of JPL D-1489 (Ref. 1). In addition, it provider procedures for identifying, preparing, processing, tracking and resolving deficiencies in the analyses and/or design. This document does not address analyses required in direct response to safety concerns.
Ident. Num:
JPL-D-5703
JPL-D-5703, RELIABILITY ANALYSES HANDBOOK. This document provides guidelines for performing and reviewing reliability analyses associated with flight equipment. It is responsive to the analysis requirements of JPL D-1489 (Ref. 1). In addition, it provider procedures for identifying, preparing, processing, tracking and resolving deficiencies in the analyses and/or design. This document does not address analyses required in direct response to safety concerns.
