ML20095G766

Rev 3 to Administrative Procedure QL-2-100, Issue Reporting & Assessment

ML20095G766
Person / Time
Site:	Calvert Cliffs
Issue date:	02/27/1995
From:	Cruse C, Tietjen K BALTIMORE GAS & ELECTRIC CO.
To:
Shared Package
ML20095G750	List: ML20095G747 ML20095G755 ML20095G762 ML20095G766 ML20095G777 ML20095G778 ML20095G784
References
QL-2-100, NUDOCS 9512210272
Download: ML20095G766 (55)

Text

- . ._ . - . . . _ . - _ _ _ _ . . . ._.._ - _ . _. __. . _ . _ _ . _ . _ _ _

1ssue Reporting and Assessment QL 2100 Revision 3 Page 1 of 55 O

Calvert Cliffs Nuclear Power Plant Administrative Procedure ISSUE REPORTING AND ASSESSMENT l l

QL-2-100 Revision 3 U::S Effective Date FEB 2 61995 co:; m ou.s o O :mge;s'

~

Tech Spec Related X Management Related I

I Writer: K. G. Tietjen Sponsor: C. H. Cruse, Plant General Manag' r i

/ '

Approved //#f / /t6 / 2./27/9f ny 4,,n a an n O

9512210272 951215 PDR ADOCK 05000317 P PDR J

I QL 2-100 1ssue Reporting and Assessment Revision 3 Page 2 of 55 RECORD OF REVISIONS AND CHANGES Revision Change Summary of Revision or Change 2 0 Procedure was extensively revised M@ changes include;

1. Addition of the Single Issue Resolution Sponsor concept including requitanents to fully resolve an issue before it is considered closed, 4

2. Clarified requirements for the IRRG to make assignmmu to the responsible OS, Manager -

Direct Report or Staff member as approved by the Department Manger;

3. Changes to reflect differences in the two IR forms in use;

4. Strengthened requirements for clearirut MODE restraints and clari6ed responsibilities; l

5. Added requirements to Mmant changes in priority for Pri. 'A' MO's;

6. Added requirement to document use of CCI 315 O Operability Determmations as related documents in the Action Item Trackmg System; I

7. Added requirement to send resolution documentation to IAU for closure ofissues; and

8. Added guidance for what constitutes acceptabic closure documentation.

In addition, minor changes were incorporated to clarify the role of the IRRG, clarify the IR initiation process, clarified requirements for documentmg drawing problems, provided reference to QL-2 101 for determimag RCA requirements, and numerous minor changes resulting from user defined action items.

2 1 Changes incorporated include RPA from R.D.

Branch to support new Rover Maia'-a=w Concept per MN 1-101, clarified Sectmo 5.5 regardmg AT/AIS closure, change refereces to AIT and AIS to AT/AIS, RPA to incorporate SA 1-102 requirements, RPA to change reference from CCI-174 to PM 1-102, and changed reference to CCI-315 to NO-1-106.

l QL-2-100

Issue Reporting and Assessment Revision 3 Page 3 of 55 O 2 2 c8 2i erger 46 a ne^rr->.s.

Gilbert to revise MO priorities in Section 5.7, and to I

add definition for Operations Workaround.  ;

> 3 0 Formally incorporate and make permanent those I changes identified in Rev 2, Changes I and 2.

i c

N i

O O

QL-2-100 Issue Reporting and Assessment Revision 3 Page 4 of 55 TABLE OF CONTENT"3 SECTION TITLE PAGE

1.0 INTRODUCTION

. . . ... . . ... . . . . . . , , , . . , ,, .,,,,,,7 1.1 Purpose .... . . .. . . . . . . . . , , , , . . . . . , .,,,,,,,,,,,,7 1.2 Scope / Applicability . .. . . . ... . ..........,,.........,,....,,,,,,,,,.,,,...7

2.0 REFERENCES

. . . , . . . . . . . . . . , , ,,,,,....,,,,,,,,,,,,,,,,,,,,g 2.1 Developmental . . . . . .. . . . . . .... .................,,...........,,,,,,,,,,,,,,,,,,,,g 2.2 Performance . . .... . . . . . . . . . . . . . . , , . ... , , , , , , , , , , , , ,,, , , g 3.0 DEFINITIONS . . . . . . . . . . . . .................8 4.0 RESPONSIBILITIES . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 5.0 PROCESS . .. . . . . . . . . . . . . . . . .. . . . . . . .. . . 14 5.1 Issue Report Initiation . . . . .. . . . , , . . . . . . . . . . . . , , ,, . , . 14 5.2 Tagging Deficient Hardware or Equipment . .. . . . . . .. ... . .. 22 5.3 Resiewing Supervisor's Action . .. . . 23 5.4 Issue Repon Processing by the Issues Assessment Unit . . . . . . ..........29 5.5 Action Organization's Corrective Action . . . . . . . . . . . . 31 5.6 Mode Restraining Issue Repons . . , , , 34 5.7 Operations Maintenance Coordinator's Review of the Issue Report . . . 36 5.8 Back Shift and Weekend Processing ofIssue Reports 44 5.9 Procurement Related Deficiencies Having an Adverse Plant Impact .. 46 5.10 Issues Assessment Unit Closure ofIssue Reports . . .. . . 46 5.11 Action Item Tracking . . .. . , , . 47 5.12 Trending Issue Report Data . . .. .. . .. . . . . . . . . . . . . . . . ,, . . . , , , , 47 6.0 BASES . . .. .. . .. . 48 7.0 RECORDS ,

, 4g

QL-2-100 1ssue Reponing and Assessnient Rension 3 Page 5 of 55 TABLE OF CONTENTS (Continued)

SECTION TITLE PAGE Attachment 1, Issue Report Process Flow Overview . ... .. . .. . .. .. ........... . ...... .. ........ ............ 4 9 Attachment 2, hsue Report . .......................................................................... ... 51 Attachment 2A, issue Report (Rensed) ..... . ......... ....... .. ............... ............ .................... ........ 53 Attachment 3, BGE De6ciency Tag , BGE Control Panel De6ciency Tag, and BGE Control Panel Information Tag ..... ..... ........... ............................... ............................ ..... ... ....... 5 5 w

l

QL 2-100 1ssue Reporting and Assessment Revision 3 Page 6 of 55 LIST OF EFFECTIVE PAGES Page No. Change No. Page No. Change No. Page No. Change No.

1 0 24 0 47 0 2 0 25 0 48 0 3 0 26 0 49 0 4 0 27 <

0 50 0 5 0 28 0 51 0 6 0 29 0 52 0 7 0 30 0 53 0 8 0 31 0 54 0 9 0 32 0 55 0 10 0 33 0 11 0 34 0 O 12 l 0 35 0 13 0 36 0 14 0 l 37 0 15 0 38 0 16 0 39 0 17 0 40 0 18 0 41 0 19 0 42 0 20 0 43 0 21 0 44 0 22 0 45 0 23 0 46 0 0 .

i QL-2100 l Issue Reporting and Assessment Revmon 3 l Page 7 of 55

1.0 INTRODUCTION

1.1 Purpose  !

This procedure provides requirements for initiatmg, reviewmg, and processing ofIssue Reports (irs) and for resolution ofIssues. [B-1] 1 l

1.2 Scope / Applicability  ;

I A. This procedure controls initiation, review, and processing ofIRs; the methods of controlling hardware and equipment de6ciencies; and the process for resolving issues j

'Ilis procedure is applicable toall de6ciemmes and men- =S- ==e's required to be d~mmented on an IR.

NOTE Forms associated with this procedure are representative of the forms used by the issues Assessment Unit (IAU) and may be revised to incorporate i nprovements wnhout revising this procedure, provided the revision does not violate the intent of the procedure.

B. This procedure is applicable to work performed at Calvert Cliffs Nuclear Power Plant (CCNPP) with the following exceptions:

1. Fossil Energy Division, when working on the Main Turbine / Generators or Steam Generator Feed Pump (SGFP) Turbines inside the fenced boundaries around this equipment. (Work outside the fenced boundaries (the fence) shall be performed according to CCNPP procedures.)

a. FED personnel shall, however, initiate an Issue Report (IR), according to QL-2-100, Issue Reporting and Assessment, under any of the following Circumstances:

(1) For problems discovered by FED personnel during maintenance of the Main Turbine / Generator or SGTP Turbine, that are considered to be a result of activities performed by CCNPP personnel.

(2) When, during Turbine work, FED personnel discover a problem requiring resolution by CCNPP personnel.

(3) When a condition identi6ed by a Project Non-conformance Report (PNCR) will NOT be resolved prior to returning the equipment to service.

l 1

C. In the case of off-site organizations working in support of CCNPP, CCNPP sponsors shall establish responsibility regarding submission ofIRs in accordance with this procedure.

D. A complete overview of the IR process is depicted in Attachment 1, Issue Report Process Flow Overview. l O

QL-2-100 Issue Reporting and Assessment Revision 3

Page 8 of 55

2.0 REFERENCES

(V) 2.1 Developmental A. QL-2, Corrective Actions Program B. MN-1, Maintenance Program Directive

}

! C. PR-1 100, Preparation and Control of Calvert Cliffs Adnumstrative Procedures D. Administrative Procedures Writer's Manual E. TI-16, Simuhtnr Maia'===1MnMenhan n~=~=

F. Generic Letter 91-18, Information to Licensees Regarding Two NRC Inspection Manual Sections on Resolution of Degraded and Non<onforming Conditions on Operability 2.2 Performance A. CCI-l 18, Nuclear Operations Section Initiated Reporting Requirements B. PM 1 102, Processing and Control of Procurement Related De6ciencies C. CCI-707, Drawing and Technical Data Base Claug? Control j D. MN 1-101, Centrol of Maintenance Activities E. PR-3-100, Records Management F. QL-3-102, Program Deficiency Reporting I

G. NS 2-101, Conduct of the Plant Operations and Safety Review Committee (POSRC)/ Procedure Review Committee (PRC)/ Qualified Resiewer (QR)

H. QL-2-102, Activity Tracking

1. QL-2-101, Event Investigation and Root Cause Analysis J. MN 1200, Maintenance Order Planmng K. SA-1 102, Fire Protection / Appendix R Compensatory Actions l 3.0 DEFINITIONS A. Accept As-Is A disposition permitted for a non-confornung item when it can be established that the item will function satisfactorily for its int-dad use. The item will continue to meet all design and engineering functional requirements including performance, maintainability, fit, and safety. (Requires Responsible Design Organization (RDO) evaluation.)

B. Action Organization The organization responsible for resohing an issue documented by an IR.

QL-2-100 Issue Reporting and Assessment Revision 3 Page 9 of 55 3.0 DEFINITIONS (Continued)

C. Classification A deternunation of which Issues meet the entena of a Program De6ciency Report (PDR).

Those issues meetmg PDR criteria will be processed in accordance with QL-3 102. All other Issues will be processed by IAU using this procedure.

D. Closure Document A completed record of action taken to resolve an issue. Examples of Closure Da-=

whule completed M=W~- Orders (MO), approved Requests for Procedure Activity (RPA), and approved Requests for Drawing Changes (RDC).

E. Condition Adverse to Quality (CAQ)

An actual or suspected hardware, process, or program deficiency or nonconformance F. Corrective Action Action taken to halt, stabilize, or correct an adverse condition and its effect.

> G. Corrective Maintenance Repair and restoration of plant equipment that has failed or is malfunctioning and is not performing its intended function.

H. Corrected-on-the-Spot (COTS)

Minor, immediate corrective action taken by qualified personnel, pre-approved by the immediate work supervisor, authorized by designated personnel, and documented on an IR.

Implicit within this definition are Rover Maintenance Activities as defmed in MN-1-101.

1. Date of Discovery (As applied to 10 CFR 21)

The date the issues Assessment Unit identifies an Issue as being potentially reportable.

J. Deficiency A condition that results in a loss or change in function or characteristic.

K. Hardware A system, support equipment, component, part or material.

L Initiator He individual who initiates an IR as a result ofidentifying an issue.

O

)

i QL-2-100 Issue Reporting and Assessment Revision 3 Page 10 of $$

o 3.0 DEFINITIONS (Continued)

U M. Issue An actual or suspected Condition Adverse to Quality or a Significant Condition Adverse to Quality for which an IR should be initiated.

N. Issue Report (IR)

The form used to document a Condition Adverse to Quality and provide a method for i

notifying affected groups and initiatmg corrective action. l l

O. Issue Report Review Group (IRRG)

A multi disciplined group that meets periodically to review and screen selected irs. IRRG members and alternates are designated by the S-IAU and appointed by the Plant General Manager - CCNPP.

P. Issue Resolution Sponsor The Issue Resolution Sponsor is that individual who owns the business function which can best resolve the issue identified in the IR. The Supervisor - IAU, with concurrence of the Issue Report Review Group (IRRG), makes this determmation and will assign the General Supervisor (or higher), Manager - Direct Report, or person autimrized by a Department Manager, to act as issue Resolution Sponsor for the target orgaruzation. IAU will '

maintain a list ofindividuals so designated by the Department Managers.

O V Maintenance Order Q.

A document used to perform and record maintenance corrective action acti',ities on plant equipment or components, to ensure specific work controls are identified and that j

maintenance work history is maintained. Maintenance orders are considered as resolution '

documents.

R. Mode Restraining Issue Report i l

An Issue Report documenting an Issue that prevents transitioning to a higher (or lower) plant operating mode.

S. Nonconformance A condition in which one or more standards or requirements are not met.

T. Operator Workaround An equipment condition or deficiency which causes an operator to deviate from the normal means of accomplishing a function or task, and which may pose a significant challenge to the safe and reliable operation of the plant under abnormal operating conditions.

U. Process A series of actions, changes, or functions that achieve an end result. For example, Maintenance and Corrective Action.

l 1

QL-2-100 Issue Reporting and Assessment Revis:on 3 Page 11 of 55 3.0 DEFINITIONS (Continued)

V. Program Deficiency Report (PDR)

A document initiated by the Quality Audits Unit (QAU) to track and resolve Significant Conditions Adverse to Quality (SCAQ's).

W. Reject Disposition of an item that is unsuitable for use and is either diW of or returned to the supplier.

X. Repair The process of restoring a non-confornung or de6cient item to a ecodition such that the capability of the item to function reliably and safely is imi== ired.

Y. Resolution Document Correspondence signed and dated by the appropriate level Action OrFanation Supervisor, identifying action taken to resolve an Issue. A resolution he shall provide all information necessary to close an IR and provide a hstag of any closure himents generated during resolution of the Issue.

Z. Reviewing Supervisor The Initiator's immediate work group supervisor, a knowledgeable supervisor in the J initiator's chain of command, a supenisor knowledgeable in the area of the Issue, or an individual within the work group pre authorized by the work group supenisor to perform the Reviewing Supenisor function of the IR process.

AA. Rework Repetitive maintenance or modification activities resulting from unsatisfactory repairs or modifications.

BB. Significant Condition Adverse to Quality An actual hardware, process, or program deSciency or nonconformance which, ifleft uncorrected, could have a serious effect on nuclear safety. A condition more serious in nature than a CAQ. The determmation of a condition being either a CAQ or a SCAQ is ,

purely a judgment call. '

CC. Simulator Issue Report (SIR)

A form used to report simulator deficiencies.

. - - - . - . - . - - . . . _ - ~ . - - - . . . . . - - . . - - . - - . . - . .-..- -~.. . - - -

QL-2-100 Issue Reporting and Assessment Revision 3 Page 12 of 55 p 4.0 RESPONSIBILITIES v 4.1 Plant General Manager The Plant General Manager is responsible for the followmg A. Overall responsibility for the Issue Reporting and Assessment Program B. Appointing the IRRG chairman, members, and alternates 4.2 Supervisor -Issues Assessment Unit pU)

De Supervisor -IAU is responsible for supervising the Issues Assessment Unit and for designating Unit personnel to serve as Chairman IRRG.

4.3 Issues Assessment Unit The Issues Assessment Unit is responsible for the following:

1 A. Implementing the Issues Assessment Program by reviewmg, screenmg, classifying, and processing irs.

B. Transmitting irs to appropriate Action Orgamzations for initiation of corrective action.

C. Maintammg a list of persons designated to act as Issue Resolution Sponsors, by their respective Department Managers. '

D. Compiling and transmitting a complete issue resolution documentation package (from original issue report to resolution documents) and forwarding to Plant History within 30 '

days of receipt of the resolution documents.

4.4 Chairman - Issue Report Review Group (IRRG)

The Chairman of the IRRG is recommended by the S-IAU and appointed by the Plant General Manager and is responsible for convening / facilitating meetmgs of the IRRG to review, discuss, and provide input into the screening ofIssue Reports.

l l

4.5 OMC/ Shift Supervisor / Control Room Supervisor l The Operations Maintenance Coordinator (OMC)/ Shift Supenisor/ Control Room Supenisor is responsible for the following:

A. Reviewing irs that document hardware problems.

B. Assigning Work Accomplishment Priority.

C. Initiating MOs for correctmg hardware deficiencies. -

D. Reviewing applicable irs for Operability and Reportability concerns.

E. Accurately completing Part C of the IR form as applicable.

O

_ . . _ _ _ _ _ . _ . . _ _ _ . _ _ . _ . . _ . _ . _ _ . _ _ _ _ . _ _ _ _ _ _ _ . . _ _ _ - _ . _ ~ _ _ _ _ _ _

QIe2-100 Issue Reporting and Assessment Revision 3 Page 13 of 55 4.6 Issue Report Review Group He Issue Report Review Group (IRRG) members and alternates are responsible for attedmg IRRG meetings when requested by the Chairman - IRRG and providing expertise in their discipline for screening, classifying, and recommendmg disposition ofIRs.

4.7 Reviewing Supervisors Reviewing Supemsors are responsible for the followmg A. Reviewing irs promptly followmg artistion of the IR.

B. Verifymg accuracy ofinformation in Part A of the1R.

C. Completing Part B of the IR.

D. Taking the IR to the Shift Supervisor if there is an operability, reportability, or immediate safety concem.

E. Ensuring irs are received by IAU for processing within three working days of being tnitiated.

4.8 Quality Audits Unit The Quality Audits Unit is responsible for the following:

0 A. Independent detemunation of PDRs from irs in addition to those that are detenmned by the IRRG.

B. Verifying resolution of PDRs according to QL-3-102, Program De6ciency Repertmg 4.9 Issue Resolution Sponsor issues Assessment, with concurrence of the Issue Report Review Group (IRRG), will determme the line organization which owns the business function that can best resolve the issue. The General Supenisor (or higher), Manager - Direct Report, or person authorized by a Department Manager responsible for this organization will be designated as the Issue Resolution Sponsor, and shall be responsible for initiating and verifying completion of all actions necessary tofully resohr the issue described on the IR. Full resolution means that all actions (including all physical work) needed to correct the programmatic aspects of the issue and prevent its recurrence are complete.

Closure of Action items to other processes is not pemutted A. He IR Sponsor is responsible for, as a muumum:

1. Evaluation of the issue.

2. Deternunation of cause (when applicable to the issue at hand).

O

_ _ _ . _ _ . _ _ _ . _ _ . _ _ _ . _ _ . _ - . . . ~ _ . _ __ __ _ _ _ ._ ____ _._._

Issue Reporting and Assessment Ql-2-100

< Revision 3 l

Page 14 of 55 i 4.9 Issue Resolution Sponsor (Continued) 3.

Determmation of corrective actions (both Wate corrective actions and additional long-term actions taken to prevent recurrence) as appropriate.

4. Ensuring generic implicatens are consulered

5. Soliciting assistance from other orgamzabons when such action is needed forfull i

solution of the issue and opening appropriate user-defined acten items.

6.

Verifying all required actions are completed tohlly resolw the issue in a timely manner, developing tY Resolution E-:= =-E and fu. w.4-g this daenmant to 1ssues Assessment Usit per this procedure d

If after evaluation of the issue by the targeted IR Sponsor, the target determines that he/she is not the appropriate owner of the business function best suited to correctmg the issue, the target may reject (or reassign) the milestone according to Section $.$.A.2 and r= - - =' that the IR be reassigned to a more appropriate sponsor to correct the problem. It is the responsibility of the initial target to communicate with the new target and obtain concurrence with the proposed transfer of responsibilities. If concurrence is not obtamed, the issue will be eseshtad for resolution.

In some cases more than one milestone may be issued e.g., for MODE Restraints or reportability concerns, but only one sponsor will be assigned. )

4.10 Supervisors of Action Organizations Supervisors of Action Organizations are responsible for the following:

A. Evaluating irs assigned to them by lAU. Reviewing 1AU rece im.caded actions and determming and implementing corrective actions as appropriate with a priority determined by the significance of the Issue.

B. ResoMng Issues according to existing CCNPP Corrective / Investigative / Notification Programs.

C. Tracking and maintaining status of assigned actions to completion.

4.11 All Personnel l All personnel at CCNPP are responsible for identifymg and promptly documenting de6ciencies and non<onformance's on irs. Personnel who serve as sponsors for off-site organirations, are responsible to determine when this procedure is required to be implemented and ensure implementation is effected within the required time constramts.

5.0 PROCESS l

5.1 Issue Report Initiation l

A.

An issue is characterized by one of the following two types of deficiencies. The key factor is that a deficient condition exists or is highly probable.

1.

O Actual. Existing in fact or reality. For example, a broken component or a personnel error.

l

' QI-2-100 Issue Reporting and Assessment Revision 3 Page 15 of 55 2

5.1 Issue Report Initiation (Continued)

O 2. Suspected: Thought to be true or probable. For example, an unident Sed fastener installed in an application that requires specific markmg to identify nwhanical properties.

EXAMPLES:

Examples of what should et D be considered Issues include:

Recommendations. Rm- .= 4= dons provide ideas to improve processes, programs, or matenal conditions beyond an already acceptable and ==63=@ry status Pi -- =4=6ces sha!! be processed within their own admmistrative programs such as the Facihty Change Request Program, Requests for FCRs, MCRs, Procedure Activity (RPA), and Survallwa Reports.

Plant Betterment. Improvements, good ideas, or better ways ofdoing business are not Issues.

Just as with a recommendation, no deficient condition exists. These types ofimprovements should be captured by normal administrative processes, e.g., FCRs, MCRs, ALARA suggestions or Quality Circle recommendations.

Simulator Issue Report (SIR) Items. Issues concermng simulator hardware or its dynamic response shall be reported using a Simulator Issue Report (SIR) according to Traming Instruction TI-16, Simulator Maintenance / Modification Requests. The SIR should be forwarded to the Simulator Instructor or Supervisor Simulator Support.

B. Issues shall be promptly identified and provide clear and lucid documentation of the issue.

C. irs should be limited to describing a single Issue. A sinnie IR shall not be used to document deficiencies or non-conformance's on both units (with the exception of generic concems), multiple systems, or unrelated deSciencies within a system or process D. The individual identifying the issue shall become the initiator of the IR. The initiator shall immediately notify the work group supervisor if, in the initiator's opinion, an immediate personnel or equipment safety concern, or an operability or reportability concern exists. I For off site organizations, the CCNPP sponsor shall ensure irs are initiated as required by this procedure. [B-4) [B 5)

NOTE Each preprinted IR Form contains a unique Ik number which is also captured in the pre-printed bar code. No change to the IR number shown on the IR Form is permitted.

O

i_. _ _ .__ _.._.__ _ _ .._. _ __ .-  !

I QL-2-100

) Issue Reporting and Assessment Revision 3 Page 16 of 55 j 5.1 issue Report laitiation (Continued)

l. He initiator shall complete PART A of the IR, (Arrachment 2 and 2A) by i perfornung the following:  ;

NOTE l Dere are currently two versions of the issue report form in use. These are shown as Attachment 2 and 2A. PART A of these forms is identical. 1 i

a. Obtain sufBcient information to substantiate validity of the Issue. [B-4]

{B-5] (B-6]

b. irs shall be subnutted for all cases where a conflict exists between drawings or between a drawing and the structure, system, or component t as it exists in the 6 eld. If the IR documents a minor drawing de6ciency, a marked-up drawing shall re=r=y the IR. De need for larger, more <

global, changes does not require a marked-up drawing be attached j

c. For hardware or equipment issues, complete and attach a BGE DeSciency Tag to deficient installed plant equipment acwi4 to instructions  ;

contamed in Section 5.2, Tagging De6cient Hardware or Equipment.

d. Using permanent b',ack or dark blue ink, per PR-2-100, Document and Drawing Control, complete Part A of the IR according to instructions on l the reverse side of the IR and as follows: [B-4] [B-5] [B-6] )

j O NOTE l

Each line on the IR form does not have to be completed ifinformation requested will not contribute i to identification. review, or resolution of the issue. 1 1

(1) Line 1. Is the issue an immediate Personnel or Equipment Safety l Concern? [B-4] [B-5) [B-6]

l If any of the following problems could occur, circle YES and immediately notify the Initiator's supervisor:

(a) Personnel injury or an naevW radiation or hazardous matenal exposure.

(b) Fire, flood, or hazardous material spill.

(c) Safety or Radiological violation.

(d) Damage to plant equipment.

(e) Failure of a :ife support system or safety equipment.

O

t

1ssue Reporting and Assessment QL-2-100 Revision 3 Page 17 of 55 5.1 Issue Report Initiation (Continued)

(f) Security rule violation. Contact the Security Supervisor l st Ext. 4024.

(2) Line 2. Is the Issue an Operability Concern? [B 4] [B-5] [B4]

If the problem or concern could affect Plant / Process Evipmaat; Power Generatag EM- and associated Auxiliaries; Tech Spec hWt or Tech Spec-Related Support Equipment;

} Appendix R Fire Safety Shutdown Equipment as described in the i Interactiw Cable Analysis (ICA), andifany ofthe followung i

conditmas exist, circleYES:

l

} (a) Exhibits excessive vibration, noise, leakage, smoke, etc.

4 j Does not operate as vaA (b)

(c) May not be capable of perfornung its intended safety function.

4 i

(d) Does not or could not meet operational or functional

, requirements.

4 (3) Line 3. Is the Issue a Reportability Concern? [B-4] [B-5] [B-6]

b

! Oj If the problem or concern meets the following guidelines, circle

' V YES and immediately notify the Initiator's supervisor (if more 4

detail is required, refer to CCI-l 18, Nuclear Operations Section j Initiated Reporting Requirements, and Technical Speci6 cations):

l (a) Could cause errors in the information displayed to

i. Operators by process instrumentation, plant computer, etc., which could adversely impact safe plant operation.

(b) Mistakenly modifies a system, or makes it operate improperly.

(c) Makes or modifies a pathway for radioactive gas or

) liquid to escape from the plant.

l l

(d) Needs to be reported to BGE Management or to the NRC (refer to CCI-l18, Nuclear Operations Section Initiated Reportmg Requirements, and Technical SpeciScations).

(e) An automatic trip should have occurred but did not (for power plant or associated safety systems only).

l i

4 O

9

)

Issue Reporting and Assessment QIr2-100  ;

Revision 3 Page 18 of 55 S.1 1ssue Report Initiation (Continued)

(f) May cause an unplanned shutdown of a system or unit or an unplanned reduction in power generation.

(g) A plant communications system needed in a plaut emergency is not working.

(b) A system which is made to protect people or equipment is not working properly and ifit fails, may cause a senous injury or unit shutdown.

\

(i) Likely to cause me&a mterest  !

i I

Iflines 1,2, or 3 are circled YES, unmediately contact the  :

Initiator's Supervisor who shall take action on Part B per paragraph 5.3, Reviewing Supervisor's Action. (Contact the Shift i

Supervisor if the Initiator's supervisor is not available.) [B-4]

If a Technical Specification violation has occurred or is immment, contact the Shift Supervisor, then the Initiator's supervisor for action on Part B.

(4) Line 4. Describe the issue. [B-5)

Describe the problem or concem in suf6cient detail so it can be p

sd casily understood. Do not use terms or acronyms unique to specific crafts or disciplines, or that are not in common use at CCNPP.

(5) Line 5. Enter Date and Time the problem or concem was discovered.

(6) Line 6. Activity in Progress when Discovered.

Indicate the activity in progress when the problem or concem was discovered. For example, during Post Maintmance Testing, a Surveillance Test Procedure, or an evolution, test, or inspection.

Indicate the system or component status; that is, runnmg, shutdown, pressure, or temperature.

i

1 Issue Reporting and Assessment QL-2-IO0 Revision 3 Page 19 of SS 5.1 Issue Report laitistion (Continued)

(7) Line 7. Was the problem or concern Corneted-On The-Spot?

Personnel are encouraged to imme&ately cornet minor problems and M- their actmas on the IR.

(8) Line 8. ImM* Actions Taken.

List immediate actions performed by the Imtiator to halt, stabilize, or correct the problem. If the probicsn was Corrected-On 'Ibe-Spot, indicate corrective action taken.

(9) Line 9. Apparent Cause Indicate probable cause of the Issue. Examples include:

madequate controls, madequate h==*=% de6cient workmanship, faulty design, naa=% to procedures, personnel error, etc.

(10) Line 10. Effect ofIssue.

Describe how the problem or concern is affectag or could affect other plant systems, g--e;= =n, or adirC.iive processes.

(11) Line 11. Extent ofIssue. [B-5)

Describe the known or suspected boundary of the problem or concern. For example, could affect all STPs or may affect all MOVs in the system Indicate if the problem or concern could have generic implications; that is, it could have an affect en additional components for which the problem or concern has not yet been I identified. l Include the number or type of components affected. Be as specific as possible because information provided may be used to determine the root cause of the problem or concern, the urgency of the problem or concern, and actions taken to prevent recurrence.

(12) Line 12. Is this a Recurring Issue? [B-5)

Circle YES if, to the Initiator's knowledge, this problem or concern or a sinular Issue is repetitive or has occurnd more frequently than previously observed or cw*r-M Give details

in the Recommendations section.

O

___m - . _ _ - _ . . .__ _ . . . . _ _ _ _ _ _ _ - _ _ _ _ _ . . _ . _ _ _ . .

4 QL-2-100 1

, Issue Reporting and Assessment Revision 3  !

Page 20 of 55 5.1 Issue Report Initiation (Continued)

(13) Line 13. rem %. l 1

Recommend actmas or ideas that will address, mitigate, or resolve the Issue. Recommmiations may include the action process, e.g., ,

an MO, PDR, or LER, or the Disposition category (for hardware de6ciencies): Rework, Reject, Repair, or Accept-As-Is.

NOTE Lines 14 thru 20 are applicable to HardEare or E-Lar-a* Issues only.

(14) Line 14. Hardware or Equipment Noun Name. l Provide the noun name of the components, sub-system, etc., I involved. l I

(15) Line 15. Unit. l Indicate the Unit number: 0 = Both Units I = Unit 1 2 = Unit 2 l l

(16) Line 16. System.

Enter the system number or letter designation.

Line 17. Hardware or Equipment Number. I (17)

Enter the identification number indicated on the hardware or equipment.

location: Describe where equipment is located. Use building, elevation, floor, compass direction, room number, grid, or column number in the area.

(18) Line 18. Tags Placed?

l NOTE Refer to section 5.2 for additional guidance on taggmg deficient equipment.

Indicate if BGE Deficiency Tags or Control Panel DeSciency Tags were placed.

(a) Print the IR number on the Control Room Deficiency tags.

O

QL-2-100 Issue Reporting and Assessment Revision 3 Page 21 of 55 5.1 Issue keport Initiation (Continued)

(b) Describe the tag types, that is, BGE DeSciency Tag or Control Panel Deficiency Tag, and how many were placed.

(c) Indicate Tag locations.

(19) Line 19. IfNO(Tags) Explain.

Whenever practical, deficient or non ccefocndag hardware or gdament shall be tagged. Ifa M% Tag is not placed on the hardware or q2W. place the tag in an appropnate location. For example, on the eastry way near the apt or outside of the equipment or personnel hatch; and explain why the tag was not placed directly on the item (Egh Radiation Area, No Access, Contamment, or Personal Safety).

(20) Line 20. P.O. Number (if known):

1 If available, enter the purchase order (P.O.) number or part '

number for the system or wuycecat.

NOTE Lines 21 and 22 are used to describe Nonhardware problems.

(21) Line 21. Title & ID Number of Controlling Document (include l revision number).

Enter the procedure, specification, drawing, etc., title, number, l and revision that controls the activity having the problem or l concern. If the issue concerns a drawing discrepancy, a marked- l up drawing shall accompany the IR. (See Section 5.1.D.l.b.)

If the problem or concem is with computer softwwe, indicate the application name, module name, screen number, etc.

(22) Line 22. Requirement Violated (if known).  :

Enter the requirement that is not being complied with. Indicate the specific requirement when possible by paragraph number, page number, and a brief description of the requirement, if known.

O

QI 2-100 Issue Reporting and Assessment Revision 3 Page 22 of 55 5.1 Issue Report Initiation (Continued)

NOTE If the Initiator desires anonymity, the Initiator may leave the Initiator's Name, Phone Extension, and Group entries blank and send the IR directly to IAU without a Reviewing Supervisor's review.

If the Initiator desires con 6dentiality, the Instaator may call the Nuclear Hotline. (Ext. 4141)

(23) Line 23. Initiator's Name.

Print Initiator's name (unless Instaator & sires anonymity). Also enter the following information:

(a) Initiator's phone extension.

(b) Date and time.

(c) Initiator's group designator.

(d) Indicate under the IR Number in the top right of the form if a continuation sheet was used.

2. Take the IR to a knowledgeable Reviewing Supervisor for review, preferably one in the Initiator's cham of command.

3. If the initiator is a Supervisor or above, then he/she may also complete Part B (the Reviewing Supervisor's Section).

5.2 Tagging Deficient Hardware or Equipment A. The IR Initiator shall use deficiency tags to identify de6cient hardware or equipment:

1. BGE Deficiency Tag: ' Ibis tag (Green, Attachment 3) shall be used to identify deficient material, parts, or components for which an IR has been initiated.

2. Control Panel De6ciency Tag: This tag (small Green, Attachment 3) shall be used on deficient control or instrument panel equipment where lack of space warrants a small tag.

NOTE I l

Deficiency tags should be hung on equipment only to identify a hardware related deficiency. 'Ibese '

tags should not be used when a orocrammatic deficiency is identified O

I l

_ _ . _ _ - _ _ _ _ _ _ . _ . _ _ _ _ . _ _ . _ _ _ _ _ _ _ _ . _ . _ . . . _ . . . ~ . _ _ _ . _ _ . _ _ _ _ _ _

Issue Reporting and Assessment QL-2-100 Revision 3 Page 23 of 55 5.2 Tagging Deficient Hardware or Equipment (Continued)

B. Control Panel Information Tags (small Brown, Attachment 3) are used to identify de6cient l

items remote from the Control Room This tag provides Operations with information on use of equipment, e.g., a pump with a packing leak. These tags are controlled by Plant Work Control in conjunction with Control Room de6ciency tracking C. The IR Initiator shall clearly mark deficient hardware or equipment with BGE W Tags, Control Panel Deficiency Tags, or Control Panel Information tags, as applicable, contaimng the followmg information:

1. IR number.

2. Date tag was put in place.

3. Description of the Issue.

4. Equipment involved.

D. The Initiator shall place the tags in a manner that will not obstruct operation or observation of any installed plant instrumentation, controls or labels. Neatly affixmg tags on walls or cabinets at the point of entry into normally inaccessible, cramped or emironmentally unsuitable areas is an acceptable practice.

1.

Do not place tags on equipment inside containment (generates equipment operability concerns due to lost tags, pnmarily clogged sumps). [B 7)

2. Do not place tags on security barriers, accesses, or alarm equipment.

E. BGE Deficiency Tags, Control Panel Deficiency Tags, and Control Panel Information Tags shall be removed according to MN-1-101, Control of Maintenance Actisities, or in the case of a Not Approved IR, according to Section 5.3, Reviewing Supervisor's Action, of this procedure 5.3 Reviewing Supervisor's Action A. Immediately upon receipt of an IR, the Reviewing Supersisor shall perform the following:

l. Notify the Shift Supervisor if the IR presents an Immediate Personnel or Equipment Safety Concern, or an Operability or Reportability Concern. [B-4)

[B-5) [B-6]

2. If there is doubt regarding operability of the item (s) documented on the~ IR, contact the System or Design Engineer for consultation. This must be done in an expeditious manner so as to allow the IR to still be received by IAU within three working days of being initiated.

3. Review Part A for accuracy and completeness. Contact Imtzator ifinformation in Part A is inaccurate or unclear and modify the IR to correct the discrepancies.

Initial and date all changes.

O

Ql-2100 Issue Reporting and Assessment Revision 3 Page 24 of 55 p 5.3 Reviewing Supervisor's Action (Continued)

G NOTE He Reviewing Supervisor has the option to request additional information in order to deternune the validity of the Issue. The Reviewing Supervisor may consider the p-tial need for Wi='a action on the problem or concern when requesting additional information.

B. He Reviewing Supervisor shall, using permanerw black or dark blue ink, per PR-2-100, Document and Drawing Control, complete Part B accordmg to instructions on the reverse side of the IR and outlined below, [B-4] [B.5] [B-6]

1. If additional space is required, provide the additional information along with the IR number on a continuation sheet.

NOTE If the Reviewing Supervisor approves the IR, that Supervisor becomes the Co lmtiator and is accountable for content and validity ofinformation in Parts A and B.

NOTE The reviewing supervisor should complete all information requested in PART B.

NOTE O~ raere are e tre tiv t-e versiens of the issne revert ferm i >e. ne e are se = a ^ttacame 12 and 2A. Part B of these forms differ slightly. Wnere differences exist, the step will indicate to which form the step applies.

2. Line 1. Is the problem or concern an Immediate Personnel or Equipment Safety Concem? [B-41 [B-51 [B-6)

a. If the problem or concem involves one of the following situations or conditions that requires immediate notification of the Shift Supervisor, circle YES:

(1) Personnel injury or an unexpected radiation or hazardous material exposure.

(2) Fire, flood, or hazardous material spill could occur.

(3) Safety or Radiological rule violation could occur.

(4) Damage to plant equipment could occur.

(5) Failure oflife support system or safety equipment could occur.

O

Issue Reporting and Assessment QL-2-100 Revision 3 Page 25 of 55

( 5.3 Reviewing Supervisor's Action (Continued)

(6) Security rule violabou could occur, if so, contact the Security Supervisor at Extension 4024.

1 3.

Line 2. Is there an Operability Concern (Tech Spec or Other)? [B-4] [B-5] (B-6]

a. Consideration should be given to the affect of the Issue on the speci6e safety function of the followmg structures, systems, and souversts (SSCs) under the scope ofGeneric letter 91-18:

(1) Safeth-RelatedSSCs.

(2) Systems and y- i=-% suyyuriing Safety-Related SSC's (N All Tech Spec-Related Equipment.

(4) SSCs describedin the UFSAR.

(5) Appendix R Fire Safe Shutdown Equipment as described in the Interactive Cable Analysis (ICA)

b. If the problem or concern could affect the structures, systems , or components under the scope of Generic Letter 91-18, Tech Spec Equipment or Tech Spec-Related Support Equipment; and if any of the following conditions exist, circle YES:

O (1) Exhibits excessive vibration, noise, leakage, smoke, etc.

l 1

(2) Does not operate as expectai (3) May not be capable of performmg its intended safety function.

l (4) Does not or could not meet operational or functional I requirements.

c.

If the Operability Concern differs from that of the initiator, the Reviewing Supervisor shallinclude a briefjusti6 cation for the 'N0' deternunation on his/her part. An additional sheet may be used if necessary.

4.

Line 3. Is the problem or concern a Reportability Concern? [B-4] [B-5] [B-6)

a. If the problem involves a situation or condition listed below, or one that requires immediate noti 6 cation of the Shift Supervisor, circle YES:

(1) Could cause errors in the information displayed to Operators by process instrumentation, plant computer, etc., which could adversely impact safe plant operation.

O

Ql-2-100 1ssue Reporting and Assessment Revision 3 Page 16 of 55 5.3 Reviewing Supervisor's Action (Continued)

(2) Mistakenly modifies a system or causes a system to operate improperly.

(3) Makes or modifies a pathway for radioactive gas or liquid to escape from the plant.

(4) Needs to be reported to BGE Management or to the NRC (refer to CCI-l l8, Nuclear Operations Section Initiated Reporting Requirements).

(5) An automatic trip should have occurred but did not. (For power -

plant or =W='~4 safety systems only.)

(6) May cause an unplanned shutdown of a system or unit, or an unplanned reduction in power generation.

(7) A plant communications system needed in a plant emergency is not working.

(8) A system made to protect people or equiprnent is not working properly and ifit fails it may cause serious injury or unit shutdown.

(9) Likely to cause media interest.

5. Iflines 1,2, or 3 are circled YES, immediately contact the Shift Supervisor. He Shift Supervisor will evaluate the concern and fill in the Shift Supervisor's Name and Date Contacted portions of the IR. [B-41

a. Contact the Control Room if the problem is an emerBency.

b. Contact the Shift Supervisor if and when the reviewer is reasonably sure that any of the situations described in Lines 1,2, or 3 are YES.

c. Follow the Shift Supervisor's directions.

d. De Shift Supervisor shall complete the appropriate section PART B (for Attachment 2) or, completing PART C of Attachmant 2A. All requested information on either Attachment shall be filled in where knows

6. If the Reviewing Supervisor circles NO on lines 1,2, or 3 when the Imtiator circles YES, an explanation shall be provided by the Reviewing Supervisor.

7. Line 4. Is a Root Cause Analysis Rswnmaded? If YES, explain why. If j assistance is required, contact Plant Engmeermg for hardware problems, or the Operating Experience Review Unit for non-hardware problems. Root Cause Analysis requirements can be found in QL-2-101.

O l

l 1

1 QL-2-100 Issue Reporting and Assessment Revision 3 Page 27 of 55 5.3 Reviewing Supervisor's Action (Continued)

8. Line 5. Was Problem Corrected-on-the-Spot? If YES, are further actions required? Indicate in Line 6, Recommended Actions, as follows:

NOTE Corrected-On ne-Spot (COTS) is minor, immediate corrective action taken by quahfied personnel.

His applies to both programmatic issues and Rover M=i*a== Activities as defined in MN 101.

a. The Reviewing Supervisor shall vahdate ennm taken by obsemog, reviewing, inspectmg, etc., the work performed by the Initiator. Ensure actions described in Part A, Line 8 corrected the problem and that no further corrective aedon is required. i

b. Indicate if any follow-on actions are necessary even though the initial problem was corrected.

EXAMPLES.

Procedural problems that are identified and corrected by an immediate change.

When an individual performing a procedure makes a mistake that is immediately caught by the work Supenisor. The Supenisor counsels the individual and ensures correct action is taken. No further corrective action is required.

In both examples, however, an IR is required for documentation and trending purposes.

9. Line 6 (Attachment 2). Recommended Actions To Resolve Issue:

a. Enter recommendations for corrective action.

l l

b. For hardware problems, recommendations should include disposition of '

Rework, Repair, Reject, or Accept-As-Is.

10. Line 6 (Attachment 2A). Recommend group (s) to resolve issue:

a. Enter the work group whose business function can best resolve this issue.

NOTE No matter which attachment is being used, the Reviewing Supenisor is encouraged to discuss the issue with the Supenisor of the target organization to obtain the target's agreement to accept sponsorship of the issue's resolution.

I 1. Line 7 (Attachment 2). Approve IR?

a. Indicate ifIR is Approved.

b. Circling YES means the Reviewing Supervisor agrees that the IR O documents a valid problem or concern and that the Reviewing Supenisor V accepts responsibility as the Co-Initiator of the IR.

QL-2169 Issue Reporting and Assessment Revision 3 Page 28 of 55 s

. 5.3 Reviewing Supervisor's Action (Continued)

c. Circling NO means that the Reywwmg Supemsor considers the problem i

or concern invalid and does not accept responsibility as the Co Initiator.

If the IR is not approved, explain why in the Recommended Actions to Resolve Issue Line (6).

d. If the Imtiator and Revwwing Supemsor disagree on the vah&ty of the Issue, and no agreemmt is obtamed withm a r==aanhle time (as detemuned by the Revwwmg Supemsor), the Revwwmg Supemsor shall document disapproval of the IR indicating the basis for &sapproval, then sign and date the IR and forward it to IAU so that IAU receives it withm three workmg days ofistiation (1) If the IR is a hardware IR, the Imtiator shall remove assmated tags and give them to the Reviewmg Supemsor.

(2) The removed tags shall be =*=rh At o the IR and forwarded to IAU by the Renewing Supemsor.

12. Line 7 (Attachment 2A). Rw ;+=W Actions to Resolve Issue:

a. Enter recommendations for corrective action.

b. For hardware problems, recomn=Adons should include disposition of Rework, Repair, Reject, or Accept-As Is.

O 13. Line 8 (Attachment 2). Signature: Date:

a. Print last Name. Sign and date the IR to indicate completion of Supervisor's Review and that the information in Part A and Part B is accurate.

14. Line 8 (Attachment 2A). Approve IR7

a. Indicate ifIR is Approved.

b. Circling YES means the Reviewing Supervisor agrees that the IR documents a valid problem or concern and that the Resiewing Supervisor ,

accepts responsibility as the Co Imtxator of the IR. I 1S. Line 9 (Attachment 2A Only). Name: Date:

a. Print last Name. Sign and date the IR to indicate completion of Supervisor's Review and that the information in Part A and Part B is l

accurate.

16. Hardware issues should be forwarded to the OMC for imtiation of a Maintenance Order. hsues that are programatic should be forwarded to IAU and must be received by IAU within three working days of the date ofIR initiation. The Supv-IAU should be notified if this tuneframe can not be met.

O

Issue Reporting and Assessment Qle2-100 Revision 3 Page 29 of 55

~ 5.4 issue Report Processing by the Issues Assessment Unit A.

IAU shall perform the following upon receipt of an IR: [B-2] [B 3) (B-5] [B-6]

1.

Verify if a hardware deSciency exists and, if not previously reviewed by the OMC, transmit the origmal IR to the OMC for completion of Part C, lines 9 through 19. Hardware deficiencies corrected using Rover Mai'*=== are handled by the OMC and RMG. The OMC shall return the completed IR to IAU for processing.

NOTE 1AU may perform the IR screaning prior to, or in parallel with, forwar m as theIR to the OMC.

2. Invalid irs are closed by lAU.

l 3.

Valid programatic irs that are Corrected-On The-Spot and require no further action are also closed byIAU.  !

4.

IfIAU retums the IR to the Reviewing Supervisor for clarification or revision, the Reviewing Supervisor shall promptly clarify or revtse the IR and return it to IAU for further processing.

5. Screen the IR as follows:

a.

p s

Screen the IR for operability, mode change restraint, reportability, and safety significance, and immediately notify the Shift Supervisor, if not previously noti 5ed by the Initiator or Reviewing Supervisor, if the IR 1 identifies an immediate personnel or equipment safety concern, or an ,

operability or reportability concern. I

b. i If the Issue involves a possible security concern, contact the Secunty Supervisor. ,

i

c. If the issue identiSes a challenge to Appendix R compliance, refer to SA-1-102 for appropriate compensatory measures and instructions,

d. All irs screened as Nuclear Safety Significant shall be presented to POSRC according to NS 2-101, Conduct of the Plant Operations and Safety Review Committee (POSRC)/ Procedure Review Committee (PRC)/ Qualified Revieur(QR).

6.

Classify the IR, based on pre-established criteria, according to disposition of the issue:

a.

L-1 Classification is applied to irs meetmg the criteria for a PDR per QL-3-102, Program DeSciency Reporting. QAU will make the final determmation regarding which irs meet the Qle3-102, criteria.

b. L-2 classification is applied to all irs not classified L-1.

O

1 Q1e2-100 Issue Reporting and Assessment Revision 3 Page 30 of 55 5.4 Issue Report Processing by the Issues Assessment Unit (Contmued)

c. Deternune appropriate action that should be implemented to resolve the Issue. An Issue Resolution Sponsor will be rec ~.r ..cr.ded based on the business function most likely to be able to correct the problem.

7. The Supervisor-1AU, or his designee, shall act as Chairman - IRRG and present the issue to the Issue Report Review Group (IRRG) for the purpose of providin8 additional insight into the final disposition ofIRs with p e r-.r. tic concerns

a. The IRRG is responsible for reviewing the resuhs of the IR screen and ma=rms with the proposed corrective actions w=rnanded by the IR screener. The IRRG shall also review the recom ==hnen for the Issue Resolution Sponsor to ensure that this individual has cognizance of the business function that can best resolve the issue.

J

b. A current or past CCNPP SRO shall always be present at IRRG meetmgs. [B-8)

c. If agreement cannot be reached between the Chairman -IRRG and a majority of the members, the issue shall be brought to the attention of the l POSRC Chairman by the Chairman -IRRG. 'Ibe fmal decision shall rest with the POSRC Chairman l 1

d. If an individual member of the IRRG is dissatis6ed with classification or l assignment of an IR, the member may appeal the decision to the POSRC O Chairman for resolution.

8. Supervisor - IAU shall have Part C, Lines I through 7 completed, as appropriate.

[B-2] [B 3] [B 5] [B-6]

9. irs identifying Mode Restraints shall be processed according to Section 5.6, Mode Restraining Issue Reports.

l

10. For L-1 non-maintenance irs, process the IR in accordance with QL-3-102, Program Deficiency Reporting.

l

11. Process L-2 irs as follows:

a. Enter all non-maintenance L-2 irs on AT/AIS.

b. Transmit a copy of the L-2 IR to the appropriate Action Organization if an IR documents a plant program or process deSciency and is not being implemented as a Program Deficiency Report (PDR): [B-9]

12. Actions necessary to resolve the IR shall be assigned to the responsible Action Organization's General Supervisor, Manager - Direct Report, or person authorized by a Department Manager to act as a Issue Resolution Sponsor for the target organization.

O

QL-2100 1ssue Reporting and Assessment Revision 3 Page 31 of 55 5.5 Action Organization's Corrective Action A. Upon receipt of an IR, Action Organizations shall review the IR and determine its appropriate disposition based on the safety significance of the issue. Possible dispositions i include Invalidation, Rejection, or Acceptance.

1. If the assigned Action Organization determines no Corrective Action is required or that the process and controls are already adequate, then the IR shall be considered invalid. Invalidation of an IR requires a Resolution Document which describes why the issue is believed to be innlid. The AT/AIS milestone shall then be updated to indicate why the IR was invalid or reference the appropriate closure

&nmat The AT/AIS mile willihen be updatM o tDISCONTINUED

2. If the assigned Action Orgamntion deternunes it is not the organization responsible to correct the issue, the assigned Action Orgamzation shall reject IAU's AT/AIS entry and recommend the group to which the Issue should be assicned and whv. Rejection of an IR requires the General Supervisor, Superintendent, or Manager - Direct Report, of the rejectmg orgamration to provide written approval and justification for the rejection to IAU. Tbc action taken section of the milestone should be updated to reflect this justification and reference the rejection memo. The AT/AIS milestone will be updated to reject-acknowledged (RA) by lAU.

1 If a disagreement arises between IAU and the Action Orgamzation concerning 1 appropriate corrective action or IR disposition, IAU and the Action Organization shall attempt to resolve the disagreement. If the disagreement cannot be resolved y within a reasonable penod, the IR and supporting documentation shall be l

escalated to the next higher level of management until the appropriate IR )

corrective action is agreed upon.

NOTE It is the responsibility of the targeted issue Resolution Sponsor to communicate with the proposed new sponsor to obtam concurrence with the propo:ed assignment before notifying lAU of the proposed change Failure to obtain agreement will be escalated to the next level of Management.

3. Action Organizations shall, upon accepting ownership responsibility, evaluate the safety and economic significance of the issue, and develop a plan for its resolution The Issue Resolution Sponsor will update the Action item milestone to OPEN and provide an Estimated Completion Date within three weeks of the milestone initiation.

4. Issue Resolution Sponsors and supporting action orgamzations must strive to resolve issues within 90 days of acceptance. In the event this requirement can not be met, justification for longer resolution periods shall be documented in terms of the risks (nuclear, personnel, and economic) of having the issue recur before corrective actions are taken, and approved by the sponsor's General Supervisor (or above) or Manager Direct Report. (This requirement applies to programatic issues only, Hardware issues are corrected under a separate priority assigned by O

U the Operations Maintenance Coordinator [OMC].)

Ql-2-100 Issue Reporting and Assessment Revision 3 l Page 32 of 55 i

5.5 Action Organization's Corrective Action (Continued)

5. He Action Organization shall resolve the issue by the completion date. If an ,

extension to the completion date is necessary, the responsible Action Orgamzation l General Supervisor, Manager - Direct Report, or person designated by a  :

depanment manager to act as issue Resolution Sponsor for the Action

)

Orgamzation, shall consider the request, based on the safety and economic 1 signi6cance of the issue, and may authorize the extension if appropriate. His approved extension shall be communicated, in wntmg, to IAU. IAU shall then update the AT/AIS and extend by opening a new milesione rMae the new extended due date. ,

j 6.

If, during resohition of an Issue, an operability concern arises for any reason, e.g.,

as a result ofnew information, the Action Orgamzation Supemsor shall notify the Shift Supervisor for operability reevaluation.

B. Closure of action items to other established processes is not peruutted.

C. He Action Organization's General Supervisor has the authority to close an IR by deciding not to take action on the IR. The General Supervisor may decide that an Issue is of such low nsk and priority when compared to other work that it does not rate application of resources within a reasonable planmng horizon. In this case, the resolution Maw

• hall .

reflect this management decision, the issue shall be closed on AT/AIS, and the resolutr n

{

document distributed as required by paragraph 5.5.D below.  !

D. Upon completion of all required actions, the issue Resolution Sponsor shall proside a O Resolution Document to describe actions taken to resolve the issue. His document shall provide sufficient detail to ensure a reasonable understandmg of the issue, its cause, and l its resolution. The required information shall be documented according to Ql-2-102 and will include the following:

1. References to the IR and AT/AIS number of the issue being resolved, and a statement of work to be performed per the Al Required Action.

2. Definition of the problem if found to be different from the original description.

3. What the cause was determined to be (when applicable to the issue at hand). (Can be by deduction or formal Root Cause Analysis).

4. A description of what was done to resolve the issue.

5. A description of what measures were put in place to prevent recurrence of the i

issue (when appropriate to the issue at hand).

O

. _ _ _ _ . . . . . . . __ _ _ . ._ ._ . _ _ _ _ _ . _ . . _ _ _ ~ _ _ . _ _ _ . .

Issue Reporting and Assessment -

QL-2-100 Revision 3 Page 33 of 55 5.5 Action Organization's Corrective Action (Contmued) 6.

Reference to the IR numbers, AT/AIS numbers, and appropriate closure documents, e.g , an MO or FCR, for subordmate milestones 7.-

Operability determmations hmented according to NO 1-106, Functional Evalur. tion / Operability Deternunation, shall be identified as a RELATED DOCUMENT.

8.

For Accept-As Is or Repair dispositions, an RDO shall rniew and approve or revise the disposition 'and determine if disposition constitutes a design change.

[B-10]

a.

If the IR requires an Accept As-Is or Repair disposition, and the assigned engineer is not a member of an RDO, the assigned engineer may provide the disposition with RDO approval.

E.

On completion of the Resolution Docummt, the Issue Re.<olution Sponsor shall update AT/AIS with the actions taken, the Depannent Close Date, and change the Milestone Status to "C" F.

The Action Organization shall transmit the Rbalution Document to IAU within tlurty (30) calendar days of changing AT/AIS status to "C". The Action Organuation shall provide a copy of the Resolution Document to the IR Initiator and Reviewing Supervisor. [B 9]

G 1AU will forward the complete IR package to Records Management within 30 days of receipt accordmg to PR 3100, Records Management.

O

QL-2-100 1ssue Reporting and Assessment Revision 3 Page 34 of 55

)

5.6 Mode Restraining issue Reports A. If an IR documents a non-hardware issue that the IRRG believes must be resolved prior to the plant entering a particular MODE, the IR shall be coded as MODE Restrauung Mode Restraming Codes are as follows:

1. Sample Mode Restrammg Code: MRUIRO7

a. MR = Mode Restrammg Designator

)

b. Ul = Unit Designator

=

l U1 Unit 1 U2 = Unit 2 UlU2 =

Unit I and Unit 2

c. RO = Type of Outage RO =

Refueling Outage Carsidis.ent or Requirement SD = Any Unit Shutdown Commitment or Requirement

d. 7 =

Mode to which the Unit is Restramed 7 =

No Fuel can be reloaded into the Core O -

6 5

=

=

Plant cannot enter Mode 5 Plant cannot enter Mode 4 4 =

Plant cannot enter Mode 3 3 =

Plant cannot enter Mode 2 2 =

Plant cannot enter Mode 1

~

ELIMPLE. MRUIR07 This is a Mode Restrammg IR for Unit l's next or current refueling outage. Fuel cannot be reloaded into the core until the issue is resolved EXAMPLE: MRU2SDS.

This is a Mode Restraining IR for Unit 2's next or current cold shutdown outage. He Unit cannot enter Mode 4 until the Issue is resolved NOTE There may be unusual cases when it is necessary to enact Mode Restramt when going from a higher mode to a lower mode. For this situation, the codes listed above can still be used, but should be annotated accordingly.

O

_ _ _ ~ _ _ . _ _ _ _ . _ _ _ _ . _ - _ . _ . _ _ _ _ . - _ . - . _ . _ _ _ _ _ _ _ _ . _ _ _ _ _ . _

l 1ssue Reporting and Assessment QI-2-100 Revision 3 l Page 35 of 55 I 5.6 Mode Restraining issue Reports (Continued)

B. The person having responsibility for the business function that can most effectively resolve l the MODE Restraimng issue shall be assigned as the IR Resolution Sponsor. De AT/AIS action required text will clearly specify the MODE Restramt and what the res...i..er.ded corrective actions are. The IR Resolution Sponsor has the responsibility for evalu.tmg the  ;

issue and ensuring that corrective actions necessary to resolve the MODE Restramt are i fully implemented and documented in time to allow MODE change.

1. This requirement does not permit the closure of a MODE Restramt to another process, e.g., initiation of an MO to have some action performed. %e responsible l indisidual must ensure ihat actions _=~==7 to fully resolve the MODE n,.emim are actually complete. '

2. The IR Resolution Sponsor is responsible for imtiatmg any additional actions l beyond those recommended to ensure the MODE Restramt is fully resolved and documented.

1

3. He IR Resolution Sponsor shall document the resolution of the MODE Restramt and communicate this fact to Outage Management when the MODE Restramt is fully resolved a If the IR Resolution Sponsor determmes that the recommended MODE l

Restramt is not valid, the reasons for this decision shall be documented  !

and copies forwarded to Outage Management and to the IAU.

C in adition to assigning a milestone to the Issue Resolution Sponsor, the IAU will assign a separate milestone to Outage Management to trag]; the MODE Restraint and ensure the MODE Restraining portions of the issue are resolved prior to the plant entering the restrained MODE on completion of the outage.

1.

When the need for a MODE restraint is identified, IAU shall ensure prompt notification of this fact to both the IR Resolution Sponsor and Outage Management. This may include phone notification with documentation to follow (by FAX or Mail).

2 Outage Management shall clear the MODE Restramt on notification from the issue Resolution Sponsor responsible for resolving the MODE Restraint issue.

D.

When an IR documents a hardware issue which must be resolved prior to the plant entering a particular MODE, the OMC will assign an appropriate priority (usually Pri A) and indicate the MODE to which the plant is restrained. He maintenance activity must be completed before entering the restrained MODE.

1.

The IAU will not issue a MODE Restramt for hardware issues unless the issue has some programmatic implication. If such a condition exists then IAU will issue an additional MODE Restraint to ensure the programmatic issue is resolved prior to the plant entering the restrained MODE.

O

l Issue Reporting and Assessment QL-2100 Revision 3 Page 36 of 55 l

, 5.6 Mode Restraining Issue Reports (Continued) 2.

Changes to the assigned 'A' priority to work associated with the current outage will be approved by the OMC.

3. " Hardware Only" MODE restramts will not be tracked by Outage Management.

5.7 Operations Maintenance Coordinator's Review of the issue Report [B-5] [B-6]

NOTE The following steps apply to the form shown in Attachment 2.

A. The Operations Maintenance Coordinator (OMC) (or designee) shall, upon receipt of an i IR, perform the following:  !

1. Review the IR to determine if an MO is required.

2. Complete Part C, Lines 9 through 19 as follows:

1 a The Shift Supenisor or Control Room Supervisor may, as needed, l conduct the OMC review.

b. Line 9. Is an MO Required? Indicate if an MO is required to resolve the  ;

problem. If an MO is not required, circle NO, sign, date, and retum the l

IR to IAU for further processing

{

c. Line 10. Pnority. Enter the Work Accomplishment Priority associated with performing maintenance. Priorities shall be indicated as follows:

(1) Priority E - Immediate l Maintenance that is needed immediately to protect structures, systems, components, plant personnel, health and safety of the general public, or to avoid unnecessary or undesirable plant transients. Immediate maintenance can be declared only by the Shift Supenisor and must be within the boundary of the current Tech Specs and other license conditions. The maintenance order and associated documentation shall be completed concurrent with or after performance of the maintenance activity as spectfied in 1 MN-1-101, Control of Maintenance Activities:  !

D V.

QL-2100 issue Reporting and Assessment Revision 3 Page 37 of 55 5.7 Operations Maintenance Coordinator's keview of the Issue Report [B-5] [B-6] (Continued)

NOTE 1mmediate maintenance to CCNPP's power plants does not necessarily imply invoking 10 CFR 50.54(x). However, under extreme circumstances, emergency maintenance may be performed 1 outside of Technical Specification or other license conditions if all of the following three 10 CFR 4 50.54(x) conditions are met:

1. He action is required to protect the health and safety of the general public.

2. Ne action consistent with license Wid- or idaie=1 vine = dons that can provide adequate er equivalent protection is imm~Iialy apparent

3. He action is authorized by the Shift Supemsor. If the Shift Supenisor is unavailable or cannot be notified and immediate action is required, a licensed Senior Reactor Operator may authorize this action.

NOTE 10 CFR 50 54 (x) does not apply to the Independent Spent Fuel Storage Installation (ISFSI).

(2) Priority 1 - Urgent Maintenance that should be started immediately to correct i p problems that seriouslyjeopardize plant availability or reliability.

t Required paperwork shall be initiated prior to commencing hands-on work. Includes emergent maintenance activities invohing l

Limiting Conditions for Operation (LCOs) which require power reduction within 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br />. The job will work around-the-clock.

(3) Priority 2 - Operational Concerns Priority maintenance to address deteriorating or failed safety or reliability equipment. Includes regulatory issues or management concems requiring priority maintenance actisity. Work package preparation shall start and a target completion date established on l the first work day. OMC notification is required if field work will not begin within 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> (24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> for 7-day LCO actions which require power reductions). Includes emergent maintenance actisities invohing LCOs which require power reduction within seven days. Certain jobs may work around-the-clock as determined by the OMC.

O

.- - . - - .-. . - - - . - - _ = . - - . - - . . - - - . - . . .

QL-2100 1ssue Reporting and Assessment Revision 3 Page 38 of $5 5.7 Operations Maintenance Coordinator's Review of the Issue Report [B-5) [B-6] (Continued)

O (4) Priority 3 - Priority Maintenance Maintenance requiring priority planning and support (e.g.,

Control Room deficiencies, out-of senice annunciators, Operator workarounds, T-mods greater than 90 days old, chemistry concerns, RAD concerns, regulatory commitments, thermal performance concerns, STP alerts, personnel safety concerns, and system performance restoration). This applies to equipment designated as Appendix R Fire Safety Shutdown Equipment (FSSE). For Appendix R FSSE, the OMC should establish a completion date IAW SA 1-102. Priority 3 jobs should normally be worked within 30 days.

(5) Priority 4 - Quarterly System Schedule Maintenance Maintenance to restore degraded or deficient power plant equipment, and repetitive maintenance such as preventive maintenance, Surveillance Test Procedures, and performance evaluations. Priority 4 jobs should normally be worked within 2 QSS cycles. Jobs that can not or should not be done within 2 QSS cycles (e g., yearly PM's, minor or major modifications) will be scheduled in the appropriate QSS cycle.

(6) Priority 5 - Other Maintenance Maintenance such as Rover Maintenance, enhancements, shop spares, non-critical systems, and other work that will be completed as resources become available.

NOTE The purpose of the following priorities is to define which activities should be accomplished prior to Mode 1 operations.

(7) Priority A - Outage Maintenance Maintenance required to be completed prior to retunting a unit to senice.

(a) Plant Safety Maintenance or other actaities that shall be performed to correct failure or degradation of nuclear safety-related equipment.

(b) Technical Specifications Maintenance or other activities that shall be accomplished to comply with Technical Specifications.

O

QL-2-100 1ssue Reporting and Assessment Revision 3 Page 39 of 55 5.7 Operations Maintenance Coordinator's Review of the Issue Report [B 5) [B-6] (Continued)

(c) System Availability hhintemnce or other activities that shall be accomplished to declare a system operable as defmed by Technical Specifications.

(d) Equipment Reliability Maintenance or other activities that shall be performed to

' prevent or correct fadure or degradatson ofequipment that could contribute to a plant trip.

(c) Commitments Management imposed mode restrauung commitments that shall be completed prior to mode change or start-up.

(f) Surveillance test procedures or preventive maintenance activities Surveillance test procedures or preventive maintenance  !

that can only be performed during an outage and are being performed to satisfy technical specification requirements or management imposed mode restrammg O '""~"""'

(8) Priority OP - Outage Priority Maintenance Maintenance requiring priority planning and support in order to prepare that work for completion during the next power reduction or unscheduled outage (e g., Control Room deficiencies, out of-service annunciators, operator workarounds, T-mods which are greater than 90 days old, chemistry concerns, RAD concerns, regulatory commitments, thermal performance concerns, personnel safety concerns, and system performance restoration).

Priority OP maintenance should normally be ready to work within 30 days of prioritization by the OMC.

(9) Priority B - Routine Outage Maintenance Maintenance and modifications which support safe, efficient operation (a) System Availability Maintenance or other activities that shall be accomplished to make a system operable as defmed by Operations, e g.,

second tram availability.

~

(b) Equipment Reliability

. _ . . . _. . .. ~ _ _ _ _ . __ . _ _ _ _ _ _ _ . ._ . ._ _ _ _ _. . . _ ,

QL-2-100 issue Reporting and Assessment Revision 3 Page 40 of 55 p Maintenance or other actisities that are necessary to

\ correct equipment deficiencies (c) Public or Plant Safety Implementation oflong-term modifications or enhancements that do not have imd'a impact on public cr plant safety.

(d) Plant Efficiency

' Neat a- or other actisities that aculd merease plant efficiency with a high cost benefit.

(e) Comnutments Mamtenance or other activities required to fulfill management-imposed non-mode-restrammg comnutments.

(f) Preventive Maintenance Actisities Maintenance or other activities associated with preventive maintenance.

(10) Priority C - Other Maintenance Mamtenance or other activities that are dependent upon manpower availabihty, and do not rate assignment of a higher pnonty.

(11) Maintenance preparation activities (e g., plannmg, engmeermg, etc.,) should normally be pursued in the following order: Pri 1; Pri 2, Pn A; Pn OP; Pri 3; Pri 4; Pri 5; Pri B, and; Pri C.

d. Line 11. Mode to Work.

Enter the highest mode to which the MO can be worked.

NOTE MODE Qualifiers as shown in MN 2100 may be added to the MODE as needed.

c. Line 12. RMG.

Enter the Responsible Maintenance Group (RMG). The RMG has overall responsibility for performance of the MO.

f. Line 13. Operability Concem?

If YES notify the Shift Supervisor. Enter the Technical Specification paragraph number for affected systems or components involved

-. . .-. _ _ _ - . - = . _ - . . __- . . . - .

QL-2100 Issue Reporting and Assessment Resision 3 Page 41 of 55 5.7 Operations Maintenance Coordinator's Review of the Issue Report [B-5] [B-6] (Continued) g Line 14. Mode Change Restramt? If YES Describe Below.

(1) Circle YES if a mode change restriction exists (or will exist) until corrective maintenance is performed and the component or system is returned to senice. Indicate the mode Affected by the mode Change Restramt per Section 5.6, Mode Restrammg Issue Reports, paragraph A.

(2) Describe any restrictions under Work Considerations or cmmenn

b. Line 15. CCI-ll8 Report Needed?

Circle YES if a CCI-l18 Report is needed. Notify the Shift Supervisor if not previously contacted

i. Line 16. Shift Supervisor Approval Required Prior to Startmg Work?

Circle YES or NO, as appropriate.

J. Line 17. Work Considerations or Comments.

Enter Work Considerations or Comments applicable to the problem or concern and its resolution Following are several examples:

(1) Technical Specification Limitations.

(2) Power generation considerations.

(3) Work package considerations.

(4) Work completion deadlines, including those required for Appendix R hardware impairments.

(5) Appendix R work restriction / Compensatory Measures (6) Cautions.

k. Line 18. OMC Signature: Date:

Sign the IR, indicating the OMC review is complete and information contained on Part C is correct.

1. Line 19. OMC Clerk: MO Number:

(1) The OMC Clerk shall enter appropriate information into NUCLEIS if the IR is Approved, that is, YES was circled in Part C, Line 9 m Enter the MO Number in the space prosided (2) f]

QL-2-100 Issue Reporting and Assessment Revision 3 Page 42 of 55 5.7 Operations Maintenatee Coordinator's Review of the Issue Report [B-5] [B-6] (Continued)

4. If an MO is required, provide the IR to the OMC Clerk for data entry into NUCLEIS and retum the original IR annotated with the MO number to IAU.

5. If an MO is not required, circle NO and sign, date, and return the IR to IAU.

NOTE Ifit is determined that the identi6ed de6ciency does not require maintenance action, and de6ciency tags were hung, the OMC will indicate on the IR that the tags should be removed and provide a copy of the IR to the initient.

NOTE The following steps apply to the form shown in Attachment 2A.

B. (For Attachment 2A) ne Operations Maintenance Coordinator (OMC)(or designee) shall, upon receipt of an IR, perform the following:

1. Review the IR to determme if an MO is required.

2. Complete Part D, Lines I through iI as follows:

a. He Shift Supervisor or Control Room Supervisor may, as needed, conduct the OMC review.

V b. Line 1. Is an MO Required? Indicate if an MO is required to resolve the problem. If an MO is not required, circle NO, sign, date, and retum the IR to IAU for further processing.

c Line 2. Priority. Enter the Work Accomplishment Priority associated with performing maintenance Priorities shall be indicated as shown in Section 5.7.A.2.c steps I though 9.

d Line 3. Mode to Work Enter the highest mode to which the MO can be worked.

NOTE MODE Qualifiers as shown in MN-2-100 may be added to the MODE as needed.

c. Line 4. RMG.

Enter the Responsible Maintenance Group (RMG). He RMG has overall responsibility for performance of the MO.

O

QL-2-100 Issue Reporting and Assessment Revision 3 Page 43 of 55 S.7 Operations Maintenance Coordinator's Review of the Issue Report [B-5] [B-6] (Continued)

f. Line 5. Operability Concern?

i If YES notify the Shift Supervisor. Enter the Technical SpeciScation paragraph number for affected systems or components involved.

g. Line 6. Mode Change Restramt? If YES Describe Below.

(1) Circle YES if a mode change restriction exists (or will exist) until corrective maintenance is performed and the wpt or system is returned to service. Indiemte the mode MesM bythe mode Change Restraint per Section 5.6, Mode Restrauung issue Reports, paragraph A.

(2) Describe any restrictions under Work Considerations or Comments.

h Line 7. CCI-l18 Report Needed?

Circle YES if a CCI l18 Report is needed Notify the Shift Supervisor if not previously contacted.

i. Line 8. Shift Supervisor Approval Required Prior to Startmg Work?

_. Circle YES or NO, as appropriate.

P j Line 9. Work Considerations or Comments.

Enter Work Considerations or Comments applicable to the problem or concem and its resolution. Following are several examples:

(1) Tecluucal Specification Limitations.

(2) Power generation considerations.

(3) Work package considerations.

(4) Work completion deadhnes.

(5) Cautions.

k Line 10. OMC Signature: Date:

Sign the IR, indicating the OMC review is complete and information contained on Part C is correct.

O

QL-2100 Issue Reporting and Assessment Revision 3 Page 44 of 55 5.7 Operations Maintenance Coordinator's Review of the Issue Report [B-5) [B-6] (Contmued)

3. If an MO is not required, circle NO and sign, date, and return the IR to IAU.

NOTE Ifit is determined that the identified de6ciency does not require maintenance action, and de6eiency tags were hung, the OMC will indicate on the IR that the tags should be removed and prowde a copy of the IR to the initiator.

4. If an MO is required, provide the IR to the OMC Clerk for data entry into NUCLEIS and sturn the ongmal IR annotated with the MO number to IAU.

a. Line 11. OMC Clerk: MO Number:

(1) he OMC Clerk shall enter appropriate information into NUCLEIS if the IR is Approved, that is, YES was circled in Part D Line 1.

(2) Enter the MO Number in the space prosided.

5. Retum the IR to IAU.

5.8 Back Shift and Weekend Processing ofIssue Reports p A. Personnel who initiate irs on the back shift or on weekends when personnel typically assigned to review and process irs are not on site, shall perform the following' actions:

t]

1. Operations Shift personnel a Part A -Initiator. He initiator shall:

(1) Complete Part A of the IR (refer to Section 5.1, Issue Report Initiation).

(2) Take the IR to the Shift Supenisor or Control Room Supenisor.

b. Part B - Reviewing Supenisor, ne Shift Supervisor or Control Room Supenisor shall:

(1) Complete Part B of the IR (refer to Section 5.3, Resiewing Supenisor's Action).

l (2) If high priority maintenance is needed, complete the OMC section of Part C, lines 9 through I8, of the IR. (Refer to Section 5.7, Operations Maintenance Coordinator's Review of the issue Report ) and notify appropriate maintenance personnel of the need for high priority maintenance. Obtain an MO number (line 19) for this activity on the next normal work day.

O

1ssue Reporting and Assessment Ql-2-100 Revision 3 Page 45 of 55 5.8 Back Shift and Weekend Processing ofIssue Reports (Continued)

(3) If the identified deficiency is a can@ta for Rover or Manual l MO maintenance per MN-1-101, the ShiA Supenisor or Control Room Supenisor shall complete lines 9 thru 18 and forward the IR to appropriate mamtmance personnel for corrective actions l per MN-1 101. '

I

c. Part C - OMC. %e ShiA Supervisor or Control Room Supervisor shall:

(1) If maintenance personnel have been called-in, complete the OMC ponion of Pan C, lines 9 through 18, (refer to Section 5.7, j Operations Maint== ace Coordmatofs Review of the issue j

Report) and provide a copy of the IR to the mamtenance craA. l (2) Forward the original IR to IAU for processing.

f

2. Personnel other than Operations ShiA personnel:

a. Part A -Initiator. He Initiator shall:

(1) Complete Part A of the IR (refer to Section 5.1, Issue Repon Initiation). l (2) Take the IR to a knowledgeable Resiewing Supenisor, preferably in the initiator's chain of command, who will complete Part B of O (3)

If a knowledgeable Reviewing Supenisor is not on site, and high priority maintenance is needed, or the IR is an immediate personnel or equipment safety, operability or reportability concem, contact a knowledgeable Resiewing Supenisor (preferably the Initiator's work group supenisor) by phone and discuss the problem.

(a) If a Reviewing Supenisor was contacted by phone, the initiator shall complete Part B of the IR and sign the IR per telecon with (Reviewing Supervisofs name).

1 (b) If a Reviewing Supenisor cannot be contacted, the Initiator shall take the IR to the Shin Supenisor or Control Room Supenisor who will complete Part B. l (4) If a knowledgeable Reviewing Supenisor is not on site and high priority maintenance is not needed or the IR is not an immediate personnel or equipment safety, operability or reportability concem, provide the IR to the Initiator's immediate work group supenisor, when available, for processing.

O

Ql-2-100 issue Reporting and Assessment Revision 3 Page 46 of 55 5.8 Back Shift and Weekend Processing ofIssue Reports (Contmued)

b. Part B - Reviewing Supenisor. %e Reviewing Supervisor (if not available, then the ShiA Supervisor or Control Room Supenisor), shall:

(1) Complete Part B of the IR (refer to Section 5.3, Reviewing I Supenisor's Action).

(2) If high priority maintenance is necessary, take the IR to the ShiA Supervisor or Control Room Supervisor.

(3) Ifhigh priority amat=rwis not neaW forward , 1 heir 2oIAU.

c. (For Attachment 2) Part C - OMC. De ShiA Supervisor or Control Room Supenisor shall:

(1) Complete the OMC portion of Part C (refer to Section 5.7.A, and 5.8.A.I.b & c, Operations Maintenance Coordinator's Review of the issue Report) and provide a copy of the IR to the called in maintenance craft.

(2) Forward the original IR to IAU for processing. I

d. (For Attachment ,2A) Part D - OMC. The Shin Supervisor or Control Room Supenisor shall:

(1) Complete the OMC portion of Part D (refer to Section 5.7.B, and O- 5.8.A.I.b & c, Operations Maintenance Coordinator's Resiew of the issue Report) and provide a copy of the IR to the called-in maintenance craA (2) Forward the orictnal IR to IAU for processing 5.9 Procurement Related Deficiencies Having an Adverse Plant Impact A An IR shall be initiated to document deficiencies identified during the pr~:urement process l that could have an adverse impact on plant equipment, programs, or processes.

B Procurement deficiencies not having an adverse impact on plant equipment, programs, or processes, shall be documented and processed according to PM 1 102, Processing and Control of Procurement Related Deficiencies 5.10 Issues Assessment Unit Closure ofissue Reports A. IAU shall close irs according to IAU admmistrative procedures when an IR has been evaluated to be one of the following:

1. Invalid 2 A duplicate issue.

O

QL-2-100 Issue Reporting and Assessment Revision 3 Page 47 of 55 5.10 1ssues Assessment Unit Closure ofissue Reports (Conunued)

3. Not requiring additional action; that is,it was Corrected On nc Spot or no correedve action is required.

B. irs closed by 1AU and associated heion shall be transmitted to Records Management according to PR 3 100, Records Management C. Valid irs will be closed according to Action item Trackmg Guidelines and procedures.

D. lAU shall transmit a copy ofnonmamtenance irs to the Imtiator and Reviewing Supervisor for information ifno acuan was saken byanacuan orgamzation. (B-9]

5,11 Action item Tracking A. Action Organizations shall track and status assigned IR actions to completion using the AT/AIS number.

B. NUCLEIS tracks and pro 5 ides the status of MOs resultmg from irs that identify plant hardware deficiencies.

C. When all actions necessary tofully resolve an issue are completed, the IR Resolution Sponsor will change the status code to 'C' on the assigned action item milestone. He resolution document, describing action taken to correct and prevent recurrence of the issue, I

shall be sent to the Supervisor-1AU for inclusion in the IR file and subsequent transfer to Records Management.

D On receipt of the resolution document,lAU will change the milestone status code to Y to indicate that the resolution has been received and the issue is closed.

1 E. If there is a request for an OPERABILITY evaluation according to NO 1-106, AT/AIS l

will be updated to reflect the NO 1 106 document as a RELATED DOCUMENT, and a RESOLUTION DOCUMENT. IAU will also include this cross reference in the IR Tracking Database.

5.12 Trending Issue Report Data A. IR information shall be entered by lAU onto a computerized data base for access by l organizations performing trend analysis.

B Adverse trends shall be documented on irs and provided to IAU for processing.

I l

. ...= . -. - . - - - . . - - -. -. . - - - - . - -

QL-2100 Issue Reporting and Assessment Revision 3 Page 48 of 55 6.0 BASES

[B1] Basis for the issues Management System is the Performance Improvement Plan Task 4.10- 1 0 (transferred from QAP 38, Issues Assessment System).

[B2] Nuclear Hotline Investigation 5-90 (Al number CT9015748): Addresses the orgamzation, responsibilities, and acdvities ofIAU (replaces the Problem Report Review Group).

[B3] INSR 91-80/80-00/00, Page 21 (Al number CT9015748): Addresses the orF*ai" tion, responsibilities, and activities ofIAU (replaces the Problem Report Review Gmup).

(B-4] INSR 90-23/23-00/00, Page 6 (Al number CT9015748): Improve the abilitysofully assess and communicate safety consequences of dc6cicut equipment when iw41og an IR.

[B5] POSRC 0191-001-011: Ensure the IR process addresses MR process weaknesses (problem description details, operabihty of other or associated equipment, pronyt )

evaluation of operability, timely evaluation by OMC, reviewing supervisor's review for operability, shop generated MOs receiving OMC review, and spinH=I problems reviewed for operability impact)

[B-6] POSRC 0190-142-02: Implement means to evaluate safety significance of de6cient equipment.

[B7] NCR 8821, Do Not Place Tags inside Containment.

[B8] INSR (Inspecdon . Report) 9l-82/82-03/03 (Al number CT9200012): Requirement for I

currently licensed SRO to be present at IRRG meetings. (C09200057)

[B9] Nuclear Hotline Investigation 5 90: lAU provides a copy of valid nonmamtenance IR to Initiator and Reviewing Supervisor.

[B 10] Calvert Cliffs UFSAR, Appenda IB, Paragraph 18.15, Non-conforming Materials, Prm or Components.

[B 11] Response to IPAT,INSR 91-82/82-03/03- Change the way IR data is entered on AT/AIS in order to improve the ability to readily analyze data while at the same time reducing the adnumstrative workload devoted to IR actnity.

7.0 RECORDS r

Ihe ollowing records are generated by use of this procedure:

Original irs.

IR screening documents.

Resolution documents.

AT/AIS 1R acceptance or rejection documents.

Records are maintained accordmg to PR-3 100, Records Management.

O

t QL-2-100  !

Revision 3 hsue Reporting and Assessment Page 49 of 55

/%

l t

Qg A'ITAClIMENT 1, ISSUE REPORT PROCESS FLOW OVERVIEW (Page 1 of 2) i 1

I ATTACHMENT l (PAOg i OP 3)

Issue naponT Pnocess Plow OVEnVIEW INITZATOR - -

155Ut REPORT e 00CUWIW15 A CON 0lil0N ADVEAlt  ;

to CUAL! f f Om PAA T A 0F Am IR - GelflAtleft e DOTIFitt WOAA SUPIRV1504 0F IMutCIAff e Olvil IR TO AtVituluG C PEA 50matL OR 80VIPetWT SAf fTY ConCtAs SUPtAvl50R - OR AN OPERA 81LliY OR REPO4f AalLiff CONCtRN e 10tuilf!El acaCONFORuthG Iftg

....................................S...........~... , . " " ' . . * " " * * . " " * " " * ' * " * " " * * * * * " * * ** " * " " " * " * * * " * " * "

• REVIEWZNG SUPERV2SOR "

SUPIAy!SOR  ;

e AtVltw5 PART A .... ... e h0ftFtts SN!Fi SUPIRYl504 0F AN e CCW* Lift 1 PART 0 Rtytts C Ihat01Af t PER50mNil 04 80UlPMENT SAf tfY CON (tRN a 5!GN5 IR OR An CetRAalLITY OR REPO4f A8ttltY ConctAn e F0 AWARDS 1 A 101 AU -

255UES A55E55 MENT

................. ~........ .......... ....." -....."...." ".." .. ~.""*" - """ .."""" "-

UNIT I h FROW AECilP! lN5PECIl0N UN!I

~

IAU IWwt0!Aff AtYttw o C0uwNICAf ts 155Uf 10 tnt $NIFT SUPERY150R And SOA l ' FOR INFoaE4110N 04 thW101 Af t ACil0N (IF ktC155 ART) 1 pj

,j 0

AtulmiltRAtlVI ,

o At50LVt1 LtCillLITY OR CONitaf PRoettus l

Rivitu ' slin Atvitelms SuPtRY150R OR,lF ktCil5 ART.

Rt1 URN 5 IR 10 AIYltelhG SVPE AV1504 FOR CORR (C110N e cetRAalltfY

') -

e E!'OA1AJitty IR SCAttN!kG ,

o INf tRF Aff stf M Cut FOR kARDWAR( 155y(5 e mXLE AR Sart1T SIGhlFICAkCt .. ..

e WO:t ChahLt Atlf Ratht e Paou'a!

e noc t C A.'51 Ah Alf 515 FUNCfl0N 4 5CRtt !>GN011f!CAflom AtSVLT5 kAOL last0 On s Ct5104 lu'ACI e ==

~

t 1

4

~*

1 - ,

l ISSU( REPORT REVlts CROUP i...........>

e RIVitel SELECT irs 4

e PACV10t $ ItCNRICA( A5515f AhCE i =

1 1

1 e

i  ?

IR CL A15tFICATION -.*

a CLASSIFICAflCN 8Asto CM FUNC110N CRittAla ContAlht0 Im lAU ,

e L*l N0f!FY IN! SUPYalAU lk*Ltuthf n.nn. (.) e L*2 No HoflFICA110N AND CL*).lN$162. PAOCtDURES 04 1,.2 e RISOLU110m PAOCESS 10tullFit0 (Wo, POR. (TC. )

- ' e ACI!0N e CtOSI 1R ORGAN!!All0NS 30tuftF!!0 (Impoau Iblilat0R 4RivltulhG$UPV.yg.3) e ACfl04 lifu 1RACalm Emist i

, e tatR.O CATA tuftRIO O!STA!8Utt COPY 07 IR 10 ACitou CAGAk t! Afl0M 5

()

O

, , , A C.< , , 4 PAGE 2 0F 2

QL-2-100 Revision 3 Issue Reporting and Assessment

/v,)

ATTACIIMENT 1, ISSUE REPORT PROCESS FLOW OVERVIEW (Page 2 of 2)

ATTACHMENT I (PAGE 2 OP 2)

ISSUE REPORT PROCESS PLOW OVERVIEW Facet Aff ACMulti 1 PAGE t of 2 155Ut REPOAf Olsf A!BUTED TO APPA0PAI Af t ACflom ORGAN 11Af!CNS

! i

) d ,

CORAtCf!VE ACTION N0f!FICAfl04 PAcctS5 INYtsf!Gai!0N PROClis PA0 Cts 5 (IAh8L(5 0F TWA(I CAGAh!!ATIcks t R AWL L :

INAT COULD AEC(Ibt (1AMPLta (IAWLti AM 1R 70A AC110= Pts P[RFORu kVCitAA REGULAT0Af Istu PA!-) ROO T hAff(A5 CAvit PERFOAmi N*ts PAtPAM5 AN LtR IVALUafton

{'

\ ,/

ACTION OFtGANZZATIONS i

) ~.

I luPLththf EIlst!NG CCAA(Cf!v( A(!!ONS, N0flFICAflCw,

!NYt5flGAflVI PA00Mk1 o o  !

UFCAft Alis AN0/04 COW'L111 kwS/rVCLtts ' ACf!0M5 INDICAfinG ACfl0N TO Rt10Ly[

5tAful TMC 15501 ACilem ORGAhllaflons vtRIFY Ano CLO5t intlR RESPECityt 00CVW!hf5

(

%)

Issue Reporting and Assessment QL-2-100 Revision 3 Pege 51 of 55 ATTACIIMENT 2, ISSUE REPORT'(Page 1 of 2) l O V/ / PLEAsE PRINT ALL,NFCAMA,cN

/ ISSUE REPORT msnuenouson nivsase moc

1. PART A - INITIATOR gen;isirrant AInduAugNadsartasile,Non Hardar$cc etsits Asphtani

/ ,. c. y n .a n.u IEEl3EEBREIERIO p .a o. p., n. .. .roun w sw. , s.w

, ar, ri.cn s s ev e.a wat

) con.un, s

p.

in.

m s ,.a me s i . No.

. o. y.w h. . m..wta s., ceae n,. . .u  %.

rti se r=

8 C** e.tAsi sed. vn N.

..o. -

A,

........ _. , , .,~ _ - h-g . . . . . . _

/p/

, . . . . . _ . _ . ~ , . . . .

,i

...,,,c...

, , . ~ . _ , ..

p p

/,/

,/- ,...--,_m.c,.~,.c................e,_

/

i, y

p f ,....,.,.... ..... . , , - . m.....,,,

/

/

/

. . . . . ~ ,

/

/

O j,/,,' ......

s c ~.,me- , .m.11,3~ .

..........-,___._,_,m-.~.-., j/p#

/ ........-

/

p r ,,,-.... ~.-.1 .

m o.,. , ,

4

,~.......,.-,........._-.....,_,.......,.............s.,.,c...........

i,,lr...,c....... . ... - .-.., .. . . . . . . . . . . . . . . ,

,~...~...-

. . . . _ , _ , _ ,.. ..,- p/

p

/ .....

. . . . . . . . . . . . . . . . . , - , . . . . . . , . . . . . . _ . . - . ~ , . . . . . . . , . . . . . . . . . . . . . . _ . . . . . _ . ./

/_ ,

/

s'/ . . . _ , . , ... .. ._. _ _ .. _..._ . _

. , ,_ h g

/*

/

,/

$,/p,/,i

...-~... _

, - .....,u.,

y

......,m c .s.,,......,._,.,

c. - . -

$,/

/,p ,. _ .. _ ...., .. _

, , , , , , ...c._,,

_ y,/

,, ... c-._ . ,- .

/

O$ - - -

V A

_ _ _ _ _ _ _ _ _ - - - - - - - - - - ---- --- - - - "- ~~~ ~

@X-Mr^

I.ssue Reporting and Assessment Revision 3 Page 52 of 55 A'ITACHMENT 2, ISSUE REPORT (Page 2 of 2)

ISSUE REPORTINSTRUCTIONS CONTINUATION SHEE'TS CAN BE USED WHEN ADDITIONAL SPACE IS NECESSARY I e- tCLE FA E STATUS CODE SYSTEnd EFFECT CODE tontts y gesca y FAILURE DETECTION CODE susua op SYSTEW LEVEL (For single train / channel eystem) A " A OPERATIONAL ABNORMAUTY B INSPECT 10N B E DPEMTMN A SYSTE M IN SERYlCE (OPERATING / STAND 8Y) q B SYSTEM IN TEST C LDS$ OF TRAIN / CHANNEL 0 MAI 4ANCE SPECIAL NSPECTION D I,,

N UN ECTED C F SERVICE (NOT IN MAINTENANCE)

PLANT EFFECT CODES esuiulLais to s) K CmRECWEMAINTENANCE CHANNEL LEVEMFormutttple treIn/ttiennet erstem)

A RESULTED IN REDUCE 3 POWER OPERATION E TRAJN / CHANNELIN SERVICE (OPERATING / FAILURE SYMPTOM CODE STAN DSY) 8 RESULTED lN UNfT OFF LINE ttuacLA 11 F TRAIN / CMANNEL l'd TEST C RESULTEDIN REACTCIt TRIP A Pths#CALFAULT O TRAIN / CMA%NELIN MAINTENANCE D RESULTEDIN PERSDANELINJURY B OW OF SPECRCATION j E RESULTED IN OFF SITI RADLATION CN H TPAIN / CMANNELOUT OF SERVICE ABNORMAL CHAAACTER1STIC (NOT IN MANTENANCE) F RESULTED IN DAMAGE TO OTHER EOUtPMENT prt s aun L.EAXAGE -

O RESULTEDIN NO $1GVF1 CANT EFFECT F CONTAJNEDLEAKAGE e i..e e e .e u.oe .,.i. : e.m

. e.em, a ... . ...e.a ,u me wewei, semni yee seem.ese ei.e ie e iun e som s.emiset i e.easee e.emer t ee sse eeee . n e ee rsee e r ie row new es so.me.a I 1

1 IMMEDiATE SERSONNEL SAFETY / EQUIPMENT SAFETY CONCERNS: Answe"ES* tt, en yovt opinion, any of tne followeig could ocCWr:

& perturw em er en ame pected redeten er hasarcots ma*Aal *=I-e eched eena & De des to plet esimmwW cihAf eans t F4 kaod e er.poma snaia6al see tumed em.e o Feha of bee a6cport eyeeen er of saie'y oodpreerd tunJd emna e Es'eS er fianecae nae consima comM teev

( leire, mAe violation ce6Af errur Conteo ese Leewey * -- - at(Jtacts 2.

OPE AAstr f CONCE RNS: Answer 'Yes' et.in yowr opinion, the problem or co .:ern affects Plant / Process Equioment end auociated a (Jatts esceuwe ebretion. neese.neskees, smoke.ettAusharles; Tech Spec Equipment and/or Tech Spe: related Support Eqwipment. AND ANY of th b 000 enol 0:4 Pe as e404Cl4d e.Wea.: not be capable ef penorming Ra intended Nnchen a Does 404 er gewief nel meef operateenaf te $wnctensiree ,eements 3.

REPORTAE .lTV CONCERNS; Answer "Yes* If,in your opanson, the problem of cancern meets any of the followmg cond$cas:

a C4W tsuse e-ers in the informstren erspie ed r te Operators by process ta n'#.meme' q *, piant gerneuler, ett., wheCh towed eaversfiy knpact 64fe

. t War tavse en unp8enned shutsown of a system er urwi es en unpisened ele *: coe'4;: s #essrien M power gener81so8b

(

t W siaeen't

• Wws e erslem er mehes it coerste emeroorty g a t a*t commwn6tabens srstem noteed in s plant emergency 6s not everting

(Ke'+'to CCI.t t 6) a heet a to te uened to eGat maaagement er to tne mac(aeteprewy te CCt.11a)W e+ ei er m:: tes a peta-sy toe rs s.eachve o es of bow.e to and n u is4 may sowie a so.sve irwey or vna sswoowes e An a . corr. ant e o showed nave oc4 weed, but esen1 tier power piant er L Like) to sawee Mees (TV, Newspapee) interest e ssee.ater tre*, systems onM i

AC'""JTY IS MOGRESS WHEN DtSCOVEAED . Descnbe actrrsty b.ortcass when greenem descovered te g. P'M; STP. emivoorViest/re-*m; j etc4 L _

CO AECTC-)N-THE. SPOT CR. TERA; a CC"5 nur r me ere mew end emocF41, em ecom areen CCT5 can be A,w as aww spogrn and hawes desownea Aa of me k*>eg arte,a aust be ne to penwm CC4 r a CCTS a at en te pw9ews f a $assey teppris )

t6 Nse.w %s :e evans +4 pre emrood e,d siAnarued to s Lei.ssmet eperste enarr am be oderseer aaected eurony m.as tee,ec h ace ees crersbaed ey be hr W crogram setem CC"1 M te emmere er setxess t Loupmm1 %dt be &# sense oceaed bom og sywsred Dy CCT1 c Ia.a:r wr ceswes esd toss mas be entnedse$ arenata sevce er es ce CCTS e as acrmed so Os' t CCT5 har te emcwsad an am P kyrn atC 4 Fep wM :.e7 %st fut to 6 sed (es.ect pois cewof ee CCT5 m:swey we sus etsu en smAcanebc

>ce- ree re a c'en secucemers pais per c ;l 200k speewec py yms s.corwaar seen es meet soon er severne4 ene ts pe' opersinors pewseeCCr5mes w e IM Y E DiATE A TONS TAKEN . Lrst action (if any) performed by the irutator to mhsra or resoNe the assve S

AN AAEh*T CAUSE .lf possible, Docurnentat,on; etc asdicate

). what caused the problem (e g, Fersorine' E :r. Fasty De segn, Lack of Procad.re s; inadequete Contr iD f rTIOT CF SSUE Describe the eqwipment/setML,esimpacted by the problem I

11. EXTINT OF ESUE . Des &e Itroan of suspected boundary of prob &em(t g.,"Cc#. enect e4 STP s*,etc.)Ind4aie I tse prot %em cow have GENERIC '

tMPUCATCNS or a9ect the Operabiny of other assocsated eoscment/ systems /processet inchase as vo.n esarrp6es, types, and number of dancaencae 8 (e-0,3 of 5 head boRs; etc.) Se as s:ecune and detahd as posabe.

12. IS TMS A RE OJ8tRING tSSUE7. Indicate r condiban described is 16ncian to be a repeh or recumng prob 6erts 13 RECOMMEC.ATIONS Recommend actors t any,which wel oddrees/mibgete/res:Ae concerrt include who show resoNe the cercem t 4. TAC.S PW.C . bd cate 5 Tags were pieced and enter the identr6caben number fror* De tag (Teg f) and the tag Type (*-0, BGM Denceency T BGAE Hold for OC Oearance Tag, etc) indicate the Locaben where te tags were pl. aced.

21.TTT' E AND C NVMBER OF CONTROLLING DOCUMDIT. bdicate what procedure s:ec/drs=4ng/etc,has the probieres er contreds tse actMty w the problem If the prob 6e a weth computer software, mdica'e the applicanon name,rnodate name, and/or screen nwr ,:ec 2 2. R!OUIRE VE'.T VIOLATED.whenever possibLe Est spec 6: perogeoph or sectron c' re requement viciated.

2 3. IN1"J. TOR . rccate y conterwabon sheetis) were used. Take promptly to your anmese's superwsor #

taas to another supervisor. preferabPy b your chain of command. It no Sreewsion is avsaatSedake to t'e Shr't SupernsccWwr saperwe:>r cannot be

1. ls asue an WDIATE PERSONNEL SATETY / EOutptAD(f SAFTTY HA2ARD7

2. Do ycu have r OPEAASIUTY(Tech Spec or Other)Corcem? e yo6 e e a concem with 1.2 and/cr 3 BAMEDLATELY cordact the Shst Supv.

3 Do yo.r haw a *EJORTABluTY concem? Occar ert the name of the SNft Swervsor ccrit. acted,date and eme.

4 Usag the fo&.MT19 critena deta- e I e ROOT CAUSE ANALY5LS Wsotad- be ; ...- --4.

a AM ee sonatie xcwerences t T=e e more 6 m.tv fanwees of a component wahin the s'esettbed swevemance treewenti t A se unerie~ Jt procesa tangre mechem6sm is ne=/wnespecies sesee on prenews swet er nevntry escenence

e. A seN+oa o a marer aushly concern to SG4E semer raa^*gement (a t.G S. le**' and amen t T>e a we+it e rt en atineernal trend a8tectsag p8 ant sa'ety or ewehry i REC 4 VME rC ACTIONS necessary to cornpletely tesoNe the aswe Thrs may nchree a a spositso L ADpG ta; 1) OW 49C it" = y9utodon 4 *Ehes IR, 1 approve the IR, espaen why Tour emplaneten ms!! be prow to the indtsa'or The trwtator removes associa'ed M f S'GS av CM the IR then forwaad to the LAU

Neporting and Assessment , QL-2 100 l

Revision 3 Page 53 of 55 A'ITACIIMENT 2A, ISSUE REPORT REVISED (Page 1 of 2)

O Y /

1. eatu ~ m - w.

ISSUE REPORT e.=c=.c a.a i PART 1.

A - DanATOR c:ngnese PART A secsueng Hardware ander Mdware waere) as applater Do you have en IWWEDaTE Personnoi safety / Equipment safety Conoem? NO VES N 1. Ien@er 3 are WF, gggggggggggg j 2. Do you have an Operabary (Tecti spec or Other) Concem?

NO YES i nWMfDIAmY sarsact 3 Do you have a Reportabety Concem? gg g

/g 4.

DESCRIBE THE ISSUE-NO YES tow SweMsar

6. Date/Teme Dwevered. i f_ _ AWPM 2_M ki ^ sy = When Dueseered

7. Was issue Corrected &NSgc? NO YES s. Immedete Amons TaAen:

9. AppareniCasse:_ ,

10. E#ect of lasue:

11. Estent of Isave - *

13. Recommencat.ons - 12. h The a Recumrg issue? NO YES H A RDWA R E INeORV ATION g 14. Equipment Noun Name

15. Unrt -

/ 17. Eosepme*:Nsmeet 18. Srsteri LOCJten:

/ 18 Tagfs)pta:ed' No Y!i Tags,7ype 1.

Y Location of Tag (s): 1.

2.

19. If *NO* Erz:aa- 2. '

20. P.O. e (d known) l i NON.H A RDW A D E tN 21 rO AV s *1CN e g ,1nadeque's Procedurest)ccwmentshonSeece1 WetmansNpf swery Tme & 10 Number of Co- viing Document (nclude Rev. No.)' se e Fakse Procedure *c.)

/ 22 Reoverement ve a:ec c . cwys)

O/// 23 INITIATOR S N AME (F

• NT):

PARTS - HEVIEWINGSRIPERVISOR E st.: Date L, / Time: ARPM Group:-

I

1. Is issse a .immed.a:e Fe wner Safery/Eavipment Safe'y Hazard NO YEScomyseermis escuess.Fensuresm N 1.2 an&or 3 are *YES',IWe*m ATnY contact the Shift Supennsor 2 Do yos ha.e an Operabit" Tech Spec or Other) Concem?

NO YES 3 Do you ha.e a Reportabi:*. Ooncem?

NO YES

a. Roc:Casse Anatys s Rect mended? NO YES ff "YES* exp'ain wh y

/ 5 Was inwe Coneclee On ~N Spot? NO YES E Recommended G'osp'sl': Eesolve issse: af "YES* are further acacns requeed? NO YES (md< ale in

• Recommended Aoons* below)

7. Recommended Ac* ions t: *esoNeissue

/

8 App'ove IRS YES NO P .O*.

E pla'n in

• Recommended Actcns* above 9. NAME(Print).

Est,; ,,,,_ Date:,,_,,,j_,,,_ L

/

1. Is issue an tMMEDIATE FewnelSatety/Equement Safety Haza,d?

NO YES 2 Do you have an Operabilt y Tech Spec or Otwr) Concem?

NO YES TSs. -

3 Do yos have a Reportabil y Concem?

4 NO YES CCl 116e-Operauty Determ.nat>on 8 . cess impsemented NO YES

5. Comments t['

NAME(PRINT)

Ert: Date: _ t. f h Time:- AMPM-

/ 5

1. MO Requered' YES NO

• NO. Sgn.date, & retum to LAU) 2. Pnonty:

OperaMty Concem- NO '!S TSs. -

/7. CCI 118 Re;cd Needed'

3. Mooe to work:

6. Mode Change Restrarit? NO YES N *YES* Descrt>e Below'-

'.O YES (If YES notdy SMt Supemsor)

_ 4. R4 h sa.u avowsc S

Wo* Cons ceraison5Com .e-ts 8 SMt Semsor Apptwa: Requwed Prwr to Startry Work? NO YES

/ .e O $ ,_ S,C~. - Da,e , ,

,, - C _ O.

/

/

WMHMM/M/M/MM/M A

we Revision 3 Issue Reporting and Assessment Page 54 of 55 ATTACHMENT 2As ISSUE REPORT REVISED (Page 2 of 2) '

ISSUE REPORTINSTRUCTIONS CONTINU ATION SMEETS CAN BE USED wwEN ADDITios4AL BPACE IS MECESSAM a no superasen ns evanabio, corna r. Shm Supemsorw quesucra i,2 ma 3 are anew.,ed Yes s

1. IMMEDLATE PERSONNEL SAFETY / EQUIPMENT SAFETY CONCERNS Answrer"YES* omng could ocar:

lf,ln your openso a Pesmei injury or ati unexpected redaton or haran$ous metena! espasure could occur. ,

tL Dema0e to pnert a@lpmurt cenM ocne.

b Fra Nod,orhawdousrnatena!spdcoddoccur.

c Savy or Resological rule violaton codd occur. et Faaure of we opport system or seiery equipmart coJd ca:ur.

1. Secutly rule m codd occw Cornact tie Secmry Smervisor r Ert a024 1 OPERASALITY CONCEftNS: . A a *TES" N,in your opinion, the pt h or wh anecas PtarCa Equipmert; Power Generatsng Equement and aE Nbits escossrve vibrabon, noise, leakage, smoke, etc.mamated AuxE anes; Tech Spec equipment ard'or Tech S eng exist.

b Does not oporte as expected c. Would not be capable of periorrrung rts intended functon

d. Does not or could not aneet opershonal or functional requnements 3 aREPORTABILfTY CONCERNS: Answer 'YES* if,in your op nion, the pw.m or w w meets any of the tonowmg mndi Coud cause errors in the information displayed to Operators by process mstsmentahon, plant cornputer, etc. wtuch could adversely impact sate f. May cause an urplanned shutdown of a system or unit or an unplanned plan: uperabon. ,

reducbon in powe' Generabon b

M.sm enly modifies a system or rnakes it operate improperly g A plant communscahorts system needed in a plant emerge cy is not (Refer to CCI 118) c Ma= n.s or modAes a pathway for rad.oactive gas or liquid to escape Itom the d h. plant e

Nee:s to be reponed to BG&E management or to the NRC (Refer to CCl-118) A system which a made to protect peop6e or equipmeniis n: wonung p Ar a;tomane tnp should have occurred but 6dn1 (for power plant or associated and if it fads may cause a senous intury or urut shutdown sa'e . systems only)

E 7 ACTMTY IN PROGRESS WHEN OtSCOVERED Desenbe actmty m. process when probem escovered {e g PMT STP e CORRECTED-ON THE SPOT CRf7ERIA: COTS can only be pedormed on program defioenoes , volutiorviesMnspection n c )

e 9 IMMEDtATE ACT10NS TAKEN bst actons (if any) pedormed by the initiator to truttgate or resoNo the usve tC APPARENT CAUSE it poss.uo, indicate what caused the provem(e g ,PersonnelError; .

u Faulty Design Lack of Procec re 1i EFFICT OF ISSUE Desenbe the equipmentactvides impacted by the provem. nadequate Controis,D:Nmentapon.etc )

i EXTENT OF ISSUE Desenbe known or suspected boundary of problem (e g ,"Couldv a'tect re all STP si etc.) Indic g GENEot fWUC ATI%S or s'tect the Operability of other assocated equipment / systems e. process 12 and number of defoenoes (e g . 3 of S head bolts; etc ) Be as spoofic ami detailed as poss<b6e .

13 IS THis A RECURRtNG ISSUE 7 lndcate it cond. hon described es knowri to be a repetsteve or recumng prouem.

ie RECOMMEND ATIONS Recommend actons. it any, which wil address /mibgaie/ resolve concem include who should res l o ve tne conce n T ACS PLACED Ind.cate rf Tags were placed and emer the ioentitcahon number fromebciency the tag (TAG d) and the t Ta; BG&E Hold for OC C6earance Tag etc ) Indicate the LOCATION where the Tags were placed 21 TITLE AND 10 NUMBER OF CONTROLLING DOCUMENT Ind case what procedure /: spec . ,

/drawinyetc. has th ery

• re concem if the problem is mth computer software, endiCUe the appLcahon name, rnodule name a%or screen number 22 23 REQUtREMENT VIOOTED Whenever possible, kst the speofic paragraph or section of the Requirement Violated IN:TI A TOR - ind.cate at continuahon sheet (s) were used. T ake promptly to your imme6 ate somnnsor if your supems e cea' acted. taae to a other knowledgeable supemsor preferably m your chain of command tf no supennsson is ava;lable, take to the Sn.ft Supem t.

2 Is Ishe an IMMEDIATE PERSONNEL SAFETY /EOU1PMENT SIf you AFETY H AZARD7-have a concem em 1,2 s dor 3. lMMEDIATELY conta: the Do yo. aa re an OPER ABILITY (Tech Spec or Other) Conoem?

3 Do yo. are a REPORTABILTTY Concern? Shift Supemsor.

4 5

Usq re cniena m CCn 16$ to detemune il a ROOT C AUSE ANALYSIS should be rocav+ 4,G 6 Was IWe CORRECTED OH THE SPOT (COTS)? COTS can only be pedormed on program derocoes.

RECOuuEND GROVptS) that you feel should resoNe this issue 7

8 RECouuEND ACTIONS necessary W completeiy resoNe the issue Trus may incevde , i, a esposition of Rework Repa r Acc ept asas, or Relect APPROVE and a*.ames to IRIR? If you don 1 approve the IR, erplam why. Your emptanabon will be provided to the Inthator The instaator rem 9

ves as.socated de6ciency ta; s) t PRINT NAME and DATE the IR then forward to the MU. l NOTE:

With regard to the instrucuons in PART A Item 7 and PART B, item 5, Conecuve maintenance Can be performed as COTS prD$iding that the maintenance aCusides saus Rover Maintenance or Manual MO maintena:e acuvides speCified in MN-1-101.

s.

~

QL-2-100 Issue Reporting tnd Assessment Revision 3

. Page 55 of 55 e ATTACIBIENT 3, B G E DEFICIENCY TAG, B GE CONTR OL PANEL DEFICIENCY TAG, AND (s BGE CONTROLPANELINFORMATION TAG (TAOS SHOWN BELOW ARE NOT TO SCALQ i7/3 si Wro.nWSm WaE@omi0liidi??e2DMgqg kE R '"

TIMORE4ASTYll:CTRICICOMPA " ' .J 7 Mane hill I k,,% J $Ni NtMNWWWtheNEAMN*W N [G i--8f$$

h souiRMsW e?*

g  % m fmamweamer m erasa w amen s a g.J M p $ pwssiimeasemawrenwammerswemgj E

suh phxamemmasemenearesmews MI$kMMW[@5@56$$MM8TMtIANdNMW$$$A k'f

.f Y h$Y$i'!$t$$ A'Y Yb 5 S S W $ h NS$ A 5*# k h 5 % AE!N 5 n@nAME.SEBi!@R$g$$$,,MMygy 3 , ~s;gy ,y Q ,. ; esM.pg$gg$$;3.;,gep.g.,@;;333@. g yR TBEM y

i#

BCE Denclency Tag (light Cre+n)

(Sample) *

'~ . . < . , . + . . . . , n eu~ . . .

<<.se. .di&s wr :;r;?v.s , , ., ,

fl'R Non ^ ^ 'q f y"ev+1T vf:' 4 < 4" JMjs "p < %l!.M  ?.%jij

= 5. 4

', i DATE:tv{C a G.,*;f,2.n

[EQhl'Ph ' f6 4^ >

+  ; '

2% W--

m ja^okgy ':so cr:2 +s a;- +

n

- / r q

b *

- 04) (A) -

BCE Control Panet Denciency Tag (11;ht Green)

(Sample)

Circle (M) to indicate Main tag or (A) to ind;cate an Au:dliary (supporQ ta;

.LL:HQ M%'A%D I.1R.H,o.O... M;M,pdKR&Y;h;gn ,.934:%.DA.gTEfMUNWe'. castq;g.:<., $ht9Q&@:

• *' . 4 Mi* ?- 2.VW W " Ym (E Q U,lP p > * ^ > + ' : C^ J ^MM&c+ #

LPROBLIM:j m' ~ /w *

- .= .' V '

9-:vr se + -

E -:5< 3 + .

- .y: , s,-s., wwe+ 2,;. c. % v.:9.p.c .. r:

T , o, _%fs sa .w,%.2 cm a ..

, ,a

% 2D4: < n;4, ' w c3,i , ; < y

> ~p .; + . . 'n y

),p~ iry; ,

. < - -~ .. .

BGE Contiof Pan *Iinformation Tog (Brovm)

(Sample)

Circle (M) to Indicate Main tag or (JQ to indicate an Aux!!iary (support tag b