REG NASA-LLIS-0668-2000 Lessons Learned Pre-Ship Review.pdf

《REG NASA-LLIS-0668-2000 Lessons Learned Pre-Ship Review.pdf》由会员分享，可在线阅读，更多相关《REG NASA-LLIS-0668-2000 Lessons Learned Pre-Ship Review.pdf（6页珍藏版）》请在麦多课文档分享上搜索。

1、Best Practices Entry: Best Practice Info:a71 Committee Approval Date: 2000-03-07a71 Center Point of Contact: JPLa71 Submitted by: Wil HarkinsSubject: Pre-Ship Review Practice: Practice: Prior to shipment of hardware or software, conduct a pre-ship review at the completion of the fabrication or build

2、 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.Abstract: Preferred Practice for Design from NASA Technica

3、l Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-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 s

4、oftware 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 pro

5、duct 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 qualifi

6、cation 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

7、 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

8、 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 requirem

9、ent 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 missi

10、on 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 ag

11、enda specific to PSRs typically includes the items listed in Table 1.Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Table 1 - Pre-Ship Review Agenda 1. Prepare Final Compliance Matrix. Explain any incomplete requirements.2. 3. Review completeness of

12、 all drawing specifications, including incorporation of all engineering change requests (ECRs). Explain any drawings or specifications that are not complete.4. 5. Determine the status of required analyses- their completion or plans to complete, and identify any open issues. Discuss and classify any

13、residual risks.6. 7. 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.8. 9. Determine the status of required tests- their completion or plans to complete, and identify any open i

14、ssues. Discuss and classify any residual risks.10. 11. Specify the status of required documentation, including plans to provide any documents that are not complete and in the data package.12. 13. Provide plans to resolve any assurance liens.14. 15. Identify any ECRs that have not been implemented in

15、 the as-built product16. 17. 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

16、 resolution.18. 19. Assess any “red flag“ problem/failure reports (PFRs)- problems, residual risks, and actions taken to manage the risk of an in-flight occurrence.20. 21. Catalog any waivers of product requirements, including the risk assessment associated with each.22. Provided by IHSNot for Resal

17、eNo reproduction or networking permitted without license from IHS-,-,-23. Evaluate the readiness of hardware to be integrated with other hardware or the spacecraft.24. 25. Assess the readiness to ship hardware, including the adequacy of shipping containers, shipping methods, shipping environment con

18、trol, and monitoring.26. 27. Identify special instructions for item handling, testing, and training.28. 29. 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 Attitud

19、e Source: Reference 3 (Vol. 2, p XVI-E3) Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Technical Rationale:Pre-ship review provides a last opportunity for the supplier and the customer to review completion of development work before the product lea

20、ves 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 outsourc

21、ing plans.Related Practices:1. Hardware Review/Certification Requirement, Reliability Preferred Practice No. PD-ED-1215.22. Common Review Methods for Engineering Products, Reliability Preferred Practice No. PD-ED-1215.4.References:1. “JPL Standard for Reviews,“ Jet Propulsion Laboratory document JPL

22、-D-10401, May 5, 1995.2. “Cassini Project: Spacecraft System Review Program,“ Jet Propulsion Laboratory document JPL-D-9926, December 1992.3. “Orbiter Preship Review, (Book 2)“ Galileo Project, Jet Propulsion Laboratory document JPL-D-6358, May 10, 1989.4. “Launch Vehicle Review Milestones,“ NASA EL

23、V OI-12, April 1994.5. “Requirements and Procedures for Flight Project Forward Review within the Space Experiments Division,“ NASA SED OI-6700- 1, December 1989.Impact of Non-Practice: Evaluate the completeness and readiness of each item of hardware and, if applicable, any associated software or fir

24、mware, prior to release for shipment to another facility by performing a pre-ship review.Related Practices: N/AAdditional Info: Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Approval Info: a71 Approval Date: 2000-03-07a71 Approval Name: Eric Raynora71 Approval Organization: QSa71 Approval Phone Number: 202-358-4738Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-