REG NASA-LLIS-0789--2000 Lessons Learned Subsystem Inheritance Review (SIR).pdf

《REG NASA-LLIS-0789--2000 Lessons Learned Subsystem Inheritance Review (SIR).pdf》由会员分享，可在线阅读，更多相关《REG NASA-LLIS-0789--2000 Lessons Learned Subsystem Inheritance Review (SIR).pdf（5页珍藏版）》请在麦多课文档分享上搜索。

1、Best Practices Entry: Best Practice Info:a71 Committee Approval Date: 2000-04-17a71 Center Point of Contact: JPLa71 Submitted by: Wilson HarkinsSubject: Subsystem Inheritance Review (SIR) Practice: Conduct a formal design inheritance review at the system, subsystem, or assembly level prior to, or in

2、 conjunction with, the corresponding subsystem Preliminary Design Review (PDR). The purpose of the inheritance review is to identify those actions which will be required to establish the compatibility of the proposed inherited design, and any inherited hardware or software, with the subsystem functi

3、onal and design requirements.Abstract: Preferred Practice for Design from NASA Technical Memorandum 4322A, NASA Reliability Preferred Practices for Design and Test.Use of inherited flight hardware or software may reduce cost and allow a spacecraft designer to avoid the risk of launching unproven equ

4、ipment. However, the designer often lacks full information on the many design decisions made during development, including some which may cause incompatibility with current spacecraft requirements. Subsystem inheritance review (SIR) probes inheritance issues to help assure that the proposed inherite

5、d item will result in an acceptable and reliable product with minimal mission risk.The inheritance review evaluates the compatibility of the inherited or commercial-off-the-shelf (COTS) item with project requirements. It assesses potential risk associated with item use and the need for modification

6、or additional testing. It is held at the earliest possible time prior to the equivalent level PDR. For complex and critical items or where the preponderance of the hardware or software is inherited, the SIR may replace a PDR or critical design review (CDR) for the inherited item. In other cases, dis

7、cussion of inherited items can be included in another review- typically, the preliminary requirements review or the PDR. For smaller projects or tasks, the inheritance review and the PDR may be combined into a single review to obtain the benefit at minimum expense. The higher the level of inherited

8、item criticality, technical complexity, and technical risk, the more likely the inheritance review will be held at the subsystem level, or even the assembly level.Responsibilities:The responsible task manager identifies the need for a formal review and initiates the action by contacting the convenin

9、g authority, usually the next higher management level. The convening authority, in consultation with the responsible task manager, appoints the review board and a chair, and defines the board charter and schedule.The review board, under the direction of the chair, conducts the review and prepares a

10、written report to the responsible manager stating the findings and recommendations. The board may elect to use the JPL Recommendation for Action (RFA) form to document recommendations. All such recommendations are advisory only. The responsible manager prepares a written response to the convening au

11、thority addressing the disposition of the review board findings and recommendations for action. The convening authority reviews and approves these dispositions.Inheritance Review Agenda:The SIR agenda items to be addressed match the subsystem PDR agenda items. The PDR agenda is described in the NASA

12、 Preferred Reliability Practice, Preliminary Design Review, Practice No. PD-ED-1215.1. If an existing hardware, software, or design element is being inherited, then the Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-subsystem CDR agenda items also n

13、eed to be considered. The CDR agenda is described in the NASA Preferred Reliability Practice, Critical Design Review, Practice No. PD-ED-1215.3.In addition to these common review agenda items, the SIR may address the topics listed in Table 1. Selection of topics from this list should be tailored in

14、accordance with product complexity and project needs.refer to D descriptionD SIR Tools:Typical tools which may be effective in support of a productive SIR include:Compliance Matrix. Typically, the specifications of an inherited design or configured item do not precisely match current requirements. A

15、 compliance matrix is a very useful SIR tool for matching the requirements of the inherited design against the requirements of the target subsystem. Each requirement line item in the current project is checked off against the corresponding inherited item requirement, permitting visual identification

16、 of requirement deltas. The product of this analysis is a proposed plan for achieving inherited item compliance with current requirements.Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Detailed Technical Review. Agenda items and issues which have a

17、potentially significant impact on the cost, performance, and reliability of the inherited design or equipment merit special emphasis. A detailed technical review (DTR) of a single product may be held to make use of specialized expertise; it permits a more in-depth, detailed, technical review of the

18、compatibility, simplicity, and testability of interfaces than is feasible at the SIR. The DTR is organized as an informal, but structured, mini-review held prior to the formal inheritance review to discuss significant issues such as:1. A comparison of the functional and design requirements for the i

19、nherited items with those for the current project, including single point failure policy (and any exceptions), design margins, operating life, and mission flight profile.2. Environmental design requirements, including margin requirements and their justification, and the associated qualification (or

20、protoflight) and acceptance test requirements for the target application.3. Comparison of piece part standards for the current and prior projects. This issue must be addressed early in the inheritance review process in consideration of the long lead time for procurement of piece parts.4. Design asse

21、ssment or reliability analyses, such as failure modes, effects, and criticality analyses (FMECAs), worst case analyses, and part stress analyses, including the method of determining and combining variables. Also of importance are the requirements for dispositioning analysis discrepancies, and the hi

22、story of such activity on the prior project.5. Problem/failure history associated with the hardware or software during ground test and flight operations on the prior project, and the applicability of the problems/failures and their resolution to the requirements of the current project.SIR allows for

23、 an assessment of the proposed inherited design and, if applicable, the inherited hardware, software, or firmware by a group of knowledgeable persons not directly involved in the activity under review. A formal review can focus many years of experience on inheritance issues which may affect product

24、reliability.Inheritance review aids the responsible manager in early identification of potential inheritance problems and in developing optimal solutions.References:1. JPL Standard Practice Instruction (SPI) 4-16-1.2. Guidelines for Planning and Conducting Formal Reviews, JPL D-10401 (Office of Engi

25、neering and Mission Assurance).3. “TOPEX Modular Power Subsystem (MPS) Inheritance Review,“ Jet Propulsion Laboratory Memorandum 5131-87-636 (J. Quinn to E. Costogue), December 15, 1987.4. Preliminary Design Review, Reliability Preferred Practice No. PD-ED-1215.1.5. Critical Design Review, Reliabili

26、ty Preferred Practice No. PD-ED-1215.3.Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Impact of Non-Practice: In the absence of inheritance review, one or more potential problems adversely impacting the system, subsystem, or project may not be ident

27、ified in a timely manner. This oversight may later result in a condition having a significant adverse effect on quality, reliability, capability, schedule, or cost, accompanied by an increased risk of diminished performance or mission failure.Related Practices: N/AAdditional Info: Approval Info: a71 Approval Date: 2000-04-17a71 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-,-,-