Abstract:
Preferred Practice for Design & Test. Pre-ship review ensures the completeness and readiness of each item of hardware and, if applicable, any associated software or firmware, prior to release for shipment to another facility. Pre-ship review of the fabricated item to be shipped is held at the supplier or NASA facility where the item was made and tested.
Description of Driving Event:
This Lessons Learned is based on Reliability Practice No. PD-ED-1215.5; from NASA Technical Memorandum 4322A, NASA Reliability Preferred Practices for Design and Test. Benefits: Pre-ship review ensures the completeness and readiness of each item of hardware and, if applicable, any associated software or firmware, prior to release for shipment to another facility. By imposing this requirement, any discrepancies or unresolved problems may be identified and corrected while the item remains under supplier purview. This review is beneficial because it provides an independent assessment of product readiness by knowledgeable people not directly involved in the fabrication and test activity. Implementation Method: The purpose of pre-ship review (PSR) is to determine whether the required work on a planned deliverable is complete and acceptable and, where applicable, whether the flight qualification criteria have been attained. This includes checking that all required analyses and tests were performed and that the data package contains all the required documentation. Action is taken to assess the actual performance of the item against the performance requirements. Differences between the designed versus the built hardware are identified, and any additional risks associated with the differences are assessed. Any liens, concerns, unresolved problems, and open issues with the hardware or software are cataloged, and plans to resolve such open issues and complete any unfinished work are assessed. PSR requirements may apply to system contractors, subcontractors, and NASA centers; they are held prior to shipment to an integration or installation facility, a NASA center, the sponsor, or the launch site. System contractor requirements are written to specify PSR and to pass the requirement down to subcontractors. The PSR is performed by a review board and is a customer-controlled review. The review board assesses the status of the deliverable item, recommends whether or not to ship it, makes an independent judgement of the risks, and identifies any concerns which would affect mission success. A representative of the receiving organization is usually present at the review. The planning and documentation process for pre-ship and other technical reviews is described in Reliability Preferred Practice No. PD-ED- 1215.4, Common Review Methods for Engineering Products. The review agenda specific to PSRs typically includes the items listed in Table 1. Table 1 - Pre-Ship Review Agenda
- Prepare Final Compliance Matrix. Explain any incomplete requirements.
- Review completeness of all drawing specifications, including incorporation of all engineering change requests (ECRs). Explain any drawings or specifications that are not complete.
- Determine the status of required analyses-- their completion or plans to complete, and identify any open issues. Discuss and classify any residual risks.
- Determine the completion status of hardware assembly and verify that the hardware reflects the final completed drawings. Explain each discrepancy in the as-built hardware.
- Determine the status of required tests-- their completion or plans to complete, and identify any open issues. Discuss and classify any residual risks.
- Specify the status of required documentation, including plans to provide any documents that are not complete and in the data package.
- Provide plans to resolve any assurance liens.
- Identify any ECRs that have not been implemented in the as-built product..
- Identify any problem/failure reports (or equivalent, customer-approved, supplier report formats) on the subject hardware (including electrical and mechanical ground support equipment) or software, as well as on other equipment which could affect it. Provide the plans for resolution.
- Assess any "red flag" problem/failure reports (PFRs)-- problems, residual risks, and actions taken to manage the risk of an in-flight occurrence.
- Catalog any waivers of product requirements, including the risk assessment associated with each.
- Evaluate the readiness of hardware to be integrated with other hardware or the spacecraft.
- Assess the readiness to ship hardware, including the adequacy of shipping containers, shipping methods, shipping environment control, and monitoring.
- Identify special instructions for item handling, testing, and training.
- Review plans for supplier participation after shipment.
| A sample compliance matrix indicating the open item status of a sample subsystem is provided as Table 2. Table 2 - Galileo Orbiter Attitude & Articulation Control System (AACS) Compliance Matrix
![refer to [D] description](/offices/oce/llis/llis_lib/images/1009039main1_0668.jpg "refer to [D] description") [D]
* Details on work remaining were explained in the PSR package; Source: Reference 3 (Vol. 2, p XVI-E3)
Technical Rationale: Pre-ship review provides a last opportunity for the supplier and the customer to review completion of development work before the product leaves the facility. Correction of liens after this milestone usually has a major schedule impact. The planned increase in supplier participation in NASA programs will likely cause an increase in hardware built at supplier sites. Effective pre-ship controls will help ensure the success of NASA outsourcing plans. Related Practices: - Hardware Review/Certification Requirement, Reliability Preferred Practice No. PD-ED-1215.2
- Common Review Methods for Engineering Products, Reliability Preferred Practice No. PD-ED-1215.4.
References: - "JPL Standard for Reviews," Jet Propulsion Laboratory document JPL-D-10401, May 5, 1995.
- "Cassini Project: Spacecraft System Review Program," Jet Propulsion Laboratory document JPL-D-9926, December 1992.
- "Orbiter Preship Review, (Book 2)" Galileo Project, Jet Propulsion Laboratory document JPL-D-6358, May 10, 1989.
- "Launch Vehicle Review Milestones," NASA ELV OI-12, April 1994.
- "Requirements and Procedures for Flight Project Forward Review within the Space Experiments Division," NASA SED OI-6700- 1, December 1989.
Lesson(s) Learned:
Evaluate the completeness and readiness of each item of hardware and, if applicable, any associated software or firmware, prior to release for shipment to another facility by performing a pre-ship review.
Recommendation(s):
Practice:
Prior to shipment of hardware or software, conduct a pre-ship review at the completion of the fabrication or build and testing of the item to be shipped. This review is scheduled as part of the overall technical review program as defined in a project review plan. Pre-ship review is held at the supplier or NASA facility where the item was made and tested.
Evidence of Recurrence Control Effectiveness:
This practice has been used on Viking, Voyager, Magellan, Galileo, Atlas Centaur, Titan Centaur, and various instrument and space experiment projects.
Documents Related to Lesson:
N/A
Mission Directorate(s):
- Exploration Systems
- Science
- Space Operations
- Aeronautics Research
Additional Key Phrase(s):
- Administration/Organization
- Aircraft
- Computers
- Configuration Management
- Facilities
- Flight Equipment
- Ground Equipment
- Hardware
- Launch Vehicle
- Lifting Devices
- Packaging Handling Storage
- Payloads
- Safety & Mission Assurance
- Spacecraft
- Transportation
Additional Info:
|
