REG NASA-LLIS-0655--2000 Lessons Learned Preliminary Design Review.pdf

1、Best Practices Entry: Best Practice Info:a71 Committee Approval Date: 2000-03-03a71 Center Point of Contact: JPLa71 Submitted by: Wil HarkinsSubject: Preliminary Design Review Practice: Practice: Conduct a formal Preliminary Design Review (PDR) at the system and subsystem levels prior to the start o

2、f subsystem detail design, to assure that the proposed design and associated implementation approach will satisfy the system and subsystem functional requirements.Abstract: Preferred Practice for Design from NASA Technical Memorandum 4322A, NASA Reliability Preferred Practices for Design and Test.Be

3、nefits:The Preliminary Design Review (PDR) will provide for increased assurance that the proposed design approach, and the manufacturing and test implementation plans, will result in an acceptable product, with minimal project risk.Implementation Method:The responsible project/task manager defines t

4、he need for, and initiates the action for conducting a formal review by contacting the convening authority (generally the next higher management level). The convening authority, in consultation with the responsible manager, appoints the review board and a chair, and defines the board charter and sch

5、edule.The review board, under direction of the chair, will conduct the review, and will prepare a written report to the responsible manager of the findings and recommendations. The board may elect to use the JPL Recommendation For Action form (RFA) to document recommendations, which are advisory and

6、 are not direction to the manager. The responsible manager will prepare a written response to the convening authority addressing the disposition of the review board findings and recommendations for action. The convening authority will review and approve these dispositions.PDR Agenda. The following i

7、tems and issues should be addressed at the PDR. (It should be noted that all items may not apply in all cases, and that additional items may apply in some cases.)1. Functional description and block diagram2. Functional requirements and compliance of the design3. Subassembly/subsystem Functional Requ

8、irements Review Action Items and disposition4. Accuracy requirements and compliance of the design5. Interface requirements and compliance of the design6. Mass requirements and compliance of the design7. Memory requirements and compliance of the design8. Environmental requirements and compliance of t

9、he design9. Project single point failure (SPF) policy and compliance of the design10. Reliability requirements and compliance of the design11. Safety requirements and compliance of the design12. Maintainability requirements and compliance of the design13. Electronic piecepart requirements and compli

10、ance of the designProvided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-14. Make or buy decision and rationale15. Inherited hardware/software and compliance with project requirements16. Spares requirements and plans for compliance17. Quality Assurance requ

11、irements and plans for compliance18. Software Assurance requirements and plans for compliance19. Reliability analyses requirements and plans for compliance20. Safety analyses requirements and plans for compliance21. Documentation requirements and plans for compliance22. Support equipment requirement

12、s and plans for compliance23. Structural analysis requirements and plans for compliance24. Thermal analyses requirements and plans for compliance25. Calibration requirements and plans for compliance26. Testability requirements and plans for compliance27. Qualification test requirements and plans for

13、 compliance28. Acceptance test requirements and plans for compliance29. Development schedule and constraints30. Long-lead parts requirements and procurement plans31. Manufacturing and test facility requirements, availability, and acceptability32. Environmental test facility requirements, availabilit

14、y, and acceptability33. Hazardous operations facility requirements, availability, and acceptabilityThe PDR allows for an assessment of the design and plans by a group of knowledgeable persons not directly involved in the activity being reviewed. A formal review can focus many years of experience on

15、the subject at hand.Technical Rationale:The PDR aids the responsible manager in evaluating the quality of the work, and in making important decisions, including those concerning completion of critical milestones. The review process should aid in the identification of problems, and the evaluation of

16、design approaches and options.References:1. JPL Standard Practice Instruction (SPI) 4-16-1.2. JPL D-363 Guidelines for Planning and Conducting Formal Reviews.Impact of Non-Practice: Impact of Nonpractice: One or a number of potential problems which could result in an adverse impact on the system, Pr

17、ovided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-subsystem, and/or project might not be identified in a timely manner. This oversight might later result in a condition having a significant effect on quality, reliability, capability, schedule, and/or cost.Related Practices: N/AAdditional Info: Approval Info: a71 Approval Date: 2000-03-03a71 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-,-,-