ML20235U046
| ML20235U046 | |
| Person / Time | |
|---|---|
| Site: | Rancho Seco |
| Issue date: | 08/18/1987 |
| From: | SACRAMENTO MUNICIPAL UTILITY DISTRICT |
| To: | |
| Shared Package | |
| ML20235U032 | List: |
| References | |
| AP.2.06, TAC-44335, NUDOCS 8710130335 | |
| Download: ML20235U046 (21) | |
Text
'
~
4
- *) EFFECTIVE DATE 08-18-87 Original .i WP0960P 0-0028P AP.2.06 VALIDATION OF EMERGENCY OPERATING PROCEDURES i-1.0 PURPOSE 1.1 To ensure that the Emergency Operating Procedures (EOP) are compatible with the plant, operator training, and successfully mitigate emergency conditions.
2.0 REFERENCES
2.1 Emergency Operating Procedures Validation Guidelines INPO 83-006, July 1983 2.2 Component Verification and System Validation Program AP.53, Rev. 0 2.3 Verification of Emergency Operating Procedures G.2.05, Rev. O 2.4 Guidelines for the Preparation of Emergency Operating Procedures, l NUREG - 0899, August 1982 3.0 DEFINITIONS 3.1 E0P Operational Correctness - A characteristic of E0Ps that indicates the degree to which the E0Ps are compatible with plant responses, hardware, and the shift manpower to manage emergency conditions in the plant.
3.2 E0P Source Documents - Documents or records upon which E0Ps are based.
3.3 E0P Technical Accuracy - A characteristic of E0Ps that indicates the degree to which proper incorporation of generic and/or plant-specific technical information from E0P source documents and plant hardware has been made, i
3.4 E0P Usability - A characteristic of E0Ps that indicates the degree to which the E0Ps provide sufficient and understandable operator information to manage emergency conditions in the plant.
3.5 E0P Validation - The evaluation performed to determine that the actions specified in the E0P can be followed by trained operators to manage the emergency conditions in the plant.
t AP.2.06-1 -
8710130335 871002 PDR ADOCK 05000312 P PDR
1
.-\. ; [
6
' DEFINITIONS (Continued) 1 3.6 E0P Verification - The evaluation performed to confirm the written J correctness .of the'EOP and' to ensure .that the generic and/or- I plant-specific' technical aspects have been properly incorporated.
3.7 E0P Written Correctness - A characteristic of E0Ps that indicates the I degree to'which proper incorporation of information from the Rancho.Seco l Writer's Guide AP.2.10. Emergency' Operating Procedures . Description and- .j Format AP.2.24, and other appropriate administrative policies has been .?
made.
3.8 Mock-Up - Static device (e.g., models, photos, drawings) that portrays control room hardware 'and configuration.
3.9 Plant Hardware - Existing equiprient,' controls, indications, and' instruroentation in the plant.
3.10 Scenario . A stru~ctural plan of parameter and plant symptom changes that provide operating cues for the conduct of assessment.
3.11 Simulator Validation - Method of validation whereby licensed operators perform actual control functions on simulated equipment during a scenario for an observer / reviewer 3.12 Symptom - A plant characteristic .that directly or indirectly indicates plant status.
3.13 Table-Top Validation - Method of validation whereby personnel explain and/or discuss procedure steps for an observer / reviewer in response to a scenario or as part of an actual industry operating experience review.
3.14 Walk-Through Validation - Method of validation wreby licensed operators conduct a step-by-step enactment of .their actions during a scenario for an observer / reviewer without carrying out the actual-control functions, l t
1 4.0 PREREQUISITES - None 5.0 PRECAUTIONS - None I
6.0 PROCEDURE 1
'6.1 Validation of E0Ps, and changes to previously validated procedures may j be accomplished by one or more of the several validation methods, Table Top, Walk-Through, and/or Simulator. The complexity, scope, and purpose of a particular change determine the selection of the method (s), number i of scenarios to be run, and extent of evaluation, j
.l u
AP.2.06-2 l
1
(
]
. O O PROCEDURE (Continued) 6.2 Complex scenarios, adequate to bring critical safety functions into play, are necessary to fully challenge the validity of a proposed procedure or procedure change. The scope of the scenario,-its use, and even the need for it, are determined by the Projects / Procedures Operations Superintendent.
6.3 Through the validation process, the elements of the Control Room Design Review, Human Factor Consideration, specific equipment compatibility (e.g., SPDS, IDADS, EFIC), Operator Training, are all tested for proper interfacing as an integrated system with the E0Ps.
6.4 Validation may be performed before or after procedure approval (PRC, Nuclear Operations Manager) and validation can be performed in conjunction with AP.2.05 (Verification of Emergency Operating Procedure).
6.4 .1 Validation shall be re-performed on the.E0P anytime a discrepancy is found during the verification process (AP.2.05)', if verification was not completed prior to validation.
6.4 .2 If validation is performed before approval, validation comments may be incorporated into the draft procedure prior to approval. Final validation of the approved procedure is required and shall be appropriate to the nature of changes made since the pre-approval validation, per 6.1.
6.5 The Table Top Validation participants should consist of, but not be restricted to:
6.5 .1 Projects / Procedures Operations Superintendent, 6.5 .2 E0P author, 6.5 .3 SRO certified Training Dept. member, 6.5 .4 Shift Supervisor f rom an on-shif t crew, 6.5 .5 Assistant Shift Supervisor from an on-shift crew.
6.5 .6 Documentation of the Table Top Validation will be accomplished by completing Record 7.1. Record 7.1 will contain the title (s) of the i E0P being validated, a scenario, name of members participating in i validation, and the major points of the discussion. !
6.5 .7 The Projects / Procedures Operations Superintendent will lead the' ;
Table Top Validation. He is responsible for providing the scenario l that will properly exercise the E0P to completion. He may request the input of anyone that he feels could aid in developing a realistic scenario. '
6.5 .8 Each scenario will be listed on a separate Record 7.1. The ;
Projects / Procedures Operations Superintendent is responsible for '
the retention of all Record 7.ls for records.
AP.2.06-3 u_ _ __ _ _ _ _ _ _ _ _ _ _ _ _ _ -
0 )
j PROCEDURE (Continued) j J
6.6 The objective of the Walk-Through.is to see if the E0P is a functional l working procedure compatible with the physical layout of.the control and 1 instrumentation.
6.6 .1 The Walk-Through Validation is accomplished by completing Record -)
7.2. The Projects / Procedures Operations Superintendent,has the i responsibility of developing the scenarios, to direct,the exercise of the E0Ps, and to ensure that major changes or revisions are .
i exercised. He may chaose to use the same scenarios that were used in the Table Top Validation. 3 1
6.6 .1.1 The evaluation of the Walk-Through will be-conducted by: 1 6.6 .l.2 Projects / Procedures Operations Superin'tendent, l
6.6 .l.3 A member of Human Factors Engineering, 4 1
6.6 .l .4 SRO certified Training Dept. Member, l 1
6.6 .l.5 E0P author.
6.6 .2 Each member of the evaluation group will fill out a Record 7.2 on each scenario.
6.6 .3 A normal shift operating crew should be used for the Walk-Through Validation.
6.6 .4 The operating crew will be de-briefed after each scenario to discuss their comments and/or problems.
1 1
6.6 .4 All Record 7.2's and discrepancy resolutions will be retained for record files. '
6.7 Simulator Validation .
Unless the Simulator used is identical in all features addressed by the E0P, this method alone is not sufficient to consider the E0P Validation complete and the' procedure implemented.
.l 6.7 .1 The objective is to identify E0P deficiencies by actual execution of the E0P on the simulator using different scenarios.
6.7 .2 Validation will be documented by completing Record 7.3 for each j scenario and ensuring all E0Ps are exercised. It is the ;
responsibility of the Projects / Procedures Operations Superintendent. !
to choose scenarios which will thoroughly exercise all of the new -'
or revised E0Ps.
l
)
AP.2.06-4 i
1 i
?
a ,
l PROCEDURE (Continued) 6.7 .3 The validation should be conducted by three (3) observers as a I miniinum number (the Projects / Procedures Operations Superintendent i and/or his designees) and a Rancho.Seco licensed operating team. l 6.7 .4 Each scenario will be evaluated per Record 7.3. Each observer will conduct his own evaluation. ,
1 6.7 .5 The operating crew will not be informed of the scenario before the i exercise. After the simulator session is complete, the observer 1 and crew will meet and discuss and evaluate the E0P adequacy of I each scenario run during the simulator session. '
6.8 The E0P writer is responsible for the resolution of identified -
. deficiencies.
I 6.8 .1 The Projects / Procedures Operations Superintendent is responsible !
for ensuring all deficiencies and resolutions are documented and !
retained as a record of the Validation process. J 6.9 Verification and Validation will be considered complete upon completion of Record 7.4 in AP. 2.05 and Record 7.5 of AP. 2.06. Significant changes and/or revisions to any of the Emergency Responsibility -
Capability function (i.e., Physical Plant / Control Room, Training, EOF, !
E0P) in order to resolve a discrepancy may in itself require repeating I the previous Verification and Validation steps. This determination is j the responsibility of the Projects / Procedures Operations Superintendent. j 6.10 The Projects / Procedures Operations Superintendent has the. responsibility of completing Record 7.5. The following items, as applicable, will be attached to Record 7.5. 1 6.10 .1 Table Top Validation.
6.10 .2 Walk-Through validation.
6.10 .3 Simulator Validation.
6.10 .4 Discrepancy Resolutions 7.0 RECORDS !
7.1 Table Top Validation 7.2 Walk-Through Validation, pages 1 through 3 7.3 Simulator Validation, pages 1 through 7 AP.2.06-5
. .: ',)
)
. j RECORDS (Continued) !
7.4 Discrepancy Resolution i i
7.5 Validation Completion j i
l 8.0 ENCLOSURES - None 1
l l
l
\
l l
l i
AP.2.06-6
)
l _- - - - _ - - _ -
O O
. RECORD 7.1 TABLE TOP VALIDATION E0P Date Page of Scenario l
Names of Personnel Attending Discussion
$ :l Major Coments:
\
l l
i Coments Resolved / Table Top Validation Satisf actory Projects / Procedures Operations Superintendent Date RECORD 7.1 PAGE 1 of 1 AP.2.06-7
o o
~
8 RECORD 7.2-WALK-THROUGH VALIDATION E0P Date Scenario Evaluation Performed By i
Evaluators Crew l
.1 Is there sufficient information to perform the specified actions of each step?
Comments.
s 1
.2 Are the alternatives adequately described at each decision point?
Comments:
1 1
t RECORD 7.2 PAGE 1 0F 5 AP.2.06-8
b6 RECORD.7.2 (Continued)
WALK-THROUGH VALIDATION d ,
.3 At'e the labeling, abbrevi'ations, and location information as provided in "
the E0P sufficient to enable the operator to find the needed equipment?
Comments:
1 I
I
.4 Is the E0P missing information needed to manage the emergency condition?
Comments: !
t l
l
.5 Are the contingency actions sufficient to address the symptons? !
Comments: ;
t l
s l i I
l 1
.6 Are the titles and numbers sufficiently descriptive to enable the operator to find referenced and branched procedures?
Comments:
1 1
RECORD 7.2 PAGE 2 of 5 AP.2.06-9 s
\ .
h RECORD 7.2 (Contiri6ed)
')
I WALK-THROUGH VALIDATION ;
1
.7 Is the E0P easy to read and steps readily understandable? l I
Coments:
i i
l
.8 Are the figures and tables easy to read with accuracy?
Coments:
.9 Are caution and note statements readily understandable?
Coments:
s
.10 Can the actions specified in the procedure be performed in the designated sequence? . .
Coments :
i RECORD 7.2 PAGE 3 0F 5 AP.2.06-10
RECORD,7.2 (Continued)
WALK-THROUGH VALIDATION
.11 Are there alternate success paths that are not included in the E0Ps?
Comments:
i
.12 Can the information from the plant instrumentation be obtained as specified by the E0P?
Comments: _
l l
l .
.13 Is information or equipment not specified in the E0P required to accomplish the task?
Comments:
\
l 1
i
.14 If time. intervals are specified, can the procedure action steps be performed on the plant within or at the designated time intervals?
Comments:
l i
l -
1 1 1
RECORD 7.2 PAGE 4 0F 5 l AP.2.06-11 )
1 i
1
, J O O
' RECORD 7.2 (Continued) )
WALK-THROUGH VALIDATION
.15 Can the particular steps or sets of steps be readily located when required? j Comments: f I
i l
.16 Can the procedure exit point be returned to without omitting steps when i required?
Comments:
1 I
.17 Can procedure branches be entered at the correct point?
Comments:
~
\
l Resolution Satisfactory l (Evaluator) l Comments Resolved / Walk Through Validation Satisfactory Projects / Procedures Operations Superintendent Date l
l RECORD 7.2 PAGE S OF 5 AP.2.06-12 l
l E_._________________._________._.._____.._ . _ _ _ _ _ .____ __ _ _ _ _ ..J
RECORD 7.3 SIMULATOR VALIDATION E0P Date Page of Scenario (Operating Crew is not to know the scenario.)
Evaluation Performed By I Observer Crew ,
. i l
l l
1
.1 Are instructional steps sequenced so as to minimize operator shifting unnecessarily between panels? i Comments:
I l
l
.l i
l I
l I
\
RECORD 7.3 PAGE 1 0F 7 AP.2.06-13 !
1 il i
]
. h b REC 0kD7.3 (ContinuGd)
SIMULATOR VALIDATION ]
.2 Is shift manning adequate or is any operator overworked?
Coments:
.3 Are instructional steps logically written so they can be easily followed?
Coments:
l 1
i l
l .4 Are instructional steps clear, cannot be interpreted differently? i l i Coments: )
, l l
.5 Are Cautions and Notes clear, cannot be interpreted dif ferently? )
Coments:
RECORD 7.3 PAGE 2 0F 7 AP.2.06-14 1
. \
RECORD 7.3 (Continued)
SIMULATOR VALIDATION
.6 Is the intent or goal of the procedure clearly understood?
Comments:
.7 Is there smooth transition among procedures during referencing or branching?
- Comments:
.8 Are entry conditions and symptoms unique for the E0P so as to aid operator?
Comments:
1 i
.9 Do steps correspond to plant conditions?
Comments:
l RECORD 7.3 PAGE 3 0F 7 AP.2.06-15
_ . _ _ _ _ .__.-____m.__.____ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ . _ _ _ _ . _ _ _ _ _ _ _ _ . _ . _ _ _ . _ . _ . _ _ _ _
RECORD 7.3 (Continued)
O CD
^ SIMULATOR VALIDATf0N
.10 Do steps achieve. objective?
Comments:
.11 Is.information excessive? Is information too brief?
Comments:
.12 Does operator need information not found in the procedure?
Comments:
N 1
l
.13 Are alternatives explicit at discussion points?
Comments:
1 RECORD 7.3 PAGE 4 0F 7 AP.2.06-16
\
RECORD 7.3 (Continued)
O '3
'S1MULATOR VAL 1DATION
.14 Are figures and tables clear and easily understood?
Coments:
.15 Are abbreviations and nomenclature clear and easily understood?
Coments:
l l .16 Are instrument scales accurately and. appropriately specified when needed and are they in the same unit as the instrument and readable by the i , operator?
l l Coments:
- ___.
l 1 ,
l l
l i
.17 Are there any communication difficulties caused by the procedure?
Comments:
RECORD 7.3 PAGE 5 0F 7 AP.2.06-17
. 1 '
O RECORD 7.3 (Continued)
O SIMULATOR VAL 1DATION
.18 Did the procedure lead the operator through the event to a safe stable condition?
Comments:
.19 Are any significant actions required to be done that were not addressed in the procedure?
Comments:
l 1
.20 Are there any significant operational di f ficulties?
Comments:
N l
.21 Are there any steps that could not be accomplished due to procedure error ]
(i.e., pressurizer spray when RC pumps are not running)? l l
j Comments
- l l
l RECORD 7.3 PAGE 6 0F 7 AP . 2. 06-18
1 l '. O 'D
! RECORD 8.7 (Continued) l SIMULATOR VALIDATION .l
.22 Overall Coments:
i l
l 4
l l
Resolution Satisfactory
_ _ _ .(Evaluator)
Projects / Procedures Operations Superintendent Date l
RECORD 7.3 PAGE 7 0F 7 AP.2.06-19
O O RECORD 7.4 DISCREPANCY RESOLUTION For Record 4.2 , 4.3 , Item Number , Date Discrepancy Noted By Resolution:
l l
Resolution Performed By Resolution Acceptable Date (person noting discrepancy)
RECORD 7.4 PAGE 10F 1 A P . 2.' 06-20 l
O Q -
4 RECORD 7.5 VALIDATION COMPLETION E0P Title E0P Number Discrepancies Validation Initial No. OK No. OK No. OK No. OK Table Top-Control Room Walk-Through l
l l
l l
Simulator N
l Date this E0P Approved for use by PRC j All Validation has been satisfactorily completed for implementation.
Projects / Procedures Operations Superintendent Date RECORD 7.5 PAGE 1 0F 1 END AP.2.06-21