In previous paragraphs, the term engineered system was underlined. Many organizations erroneously require that all systems on site require a URS. This is a mistake and demonstrates a poor understanding of the purpose of a URS. In light of using a URS for QbD it does not make sense to generate a URS for a piece of equipment or an instrument purchased from a catalogue or off-the-shelf. It is difficult to design quality into something that is not being designed. The appropriate approach for off-the-shelf equipment is to employ a risk or impact assessment in lieu of a URS. Another approach is to use a general purchase policy to identify requirements for items such as laboratory instrument. Such a policy might include Part 11 requirements, purchased qualification packages and/or specific FDA requirements.
Retrospection Many organizations decided to retrospectively generate URSs for equipment and systems that are already in place or which are already designed and built to “check the box” on the regulatory requirement. Retrospectively generating a URS signals to an auditor that QbD was accidental and that the organization has not fulfilled the intent of QbD. Retrospection is non-value-added, so if a project is already past design/build, it makes more sense to perform risk and impact assessments. This is a check on commissioning and qualification documentation to verify each CTQ item. Policies and procedures that allow risk and impact assessments for existing systems and URS and DQ at the beginning of a new project saves time and stays true to the intent of a DQ and URS.
An Overview to User Requirement Specifications and Design Qualification
这个各位老师是如何理解的呢????
|