Identification of Affected Hardware and Document

DOESTD107393

First, a determination should be made regarding the desirability of design engineering support. Design

support may be desired for many reasons. If the organization performing the design envelope review

determines that design engineering support is desired for the design envelope review (e.g., based on

known changes to the design requirements or technical complexity), a request for design engineering

assistance should be made. Requests for design assistance may be made through the systems

engineer, the facility technical support organization (or other interfacing entity) or directly to the design

authority.

If the reviewing organization does not desire design support, the reviewer should determine if the

necessary design requirements or design envelopes are available for the review to proceed. If not,

assistance from the design authority is needed and should be requested. If requested, the design

authority could search the applicable information sources (such as the CM equipment database,

calculations of record, and design basis information) and provide this information to the requesting

organization to allow them to proceed with the design envelope review. If the design requirements are

not available, the design authority may need to develop new information, which will be included in the

CM equipment database. The design authority may also define design envelopes for future use.

If the design requirements are available, the proposed change should be compared to the design

requirements to determine if it is within the existing design envelope. The proposed change is ready for

additional technical reviews upon determination and documentation that the change is within the

bounds of the applicable design requirements. Organizations outside the design authority should be

conservative in their review of design requirements. The design engineering organization should be

consulted when there is any doubt as to whether the proposed change is within the design envelope.

If the proposed change is not within the design envelope, it involves a design change and design

engineering assistance is necessary to proceed. In some cases, the revised design requirement is

within the current design basis and, therefore, could be approved with relative ease. If the proposed

change is beyond the current design basis, the development of a new or revised design basis is

necessary to support the change. The new or revised design basis generally involves significant efforts

by the design authority and potentially includes external evaluations and approvals. In such a case, the

facility management would weigh the development time and investment against the benefits of the

proposed change. An adjusted, more cost-effective change might be possible that could accomplish

the objectives of the original change within the current design basis. Administrative review and approval

to develop the proposed design change should be obtained. The design authority can recommend

three general courses of action: (1) change the design requirements after reviewing applicable design

basis information; (2) suggest that the change request be canceled; or (3) suggest that the proposed

change be revised, if possible, to stay within the limits of the existing design requirements. The

requesting organization should select the option. For physical changes that are to be implemented, the

design authority should prepare a design change package consistent with the design process and

controls. The design change package may accomplish the additional technical reviews and should

facilitate outstanding technical reviews, management review, and implementation (i.e., with no further

action by the requesting organization).

Identification of Affected Hardware and Documents. Once it is determined that a change can be made

within the defined design envelope or within new or revised design requirements, each affected SSC or

document within the CM program needs to be identified. This includes the documents that are directly

affected by the change, such as drawings. It also includes those that are indirectly affected by the

change, such as the SAR or a procedure containing a system drawing that will no longer be accurate.

By complete and thorough review, each affected item may be identified, thereby maintaining the basic

CM relationships during implementation of the change process. Examples of affected items that are

sometimes overlooked are design basis information, safety analysis reports, CM databases, operating

and maintenance procedures, and training lesson plans. The CM equipment database and the

II-45