The inspectors identified a Green
NCV of operating license condition 3.F,
Fire Protection Program, because Entergy did not implement and maintain in effect all provisions of the NRC approved
fire protection program. Specifically, Entergy did not implement and maintain the required compensatory
continuous fire watch in the east and west switchgear rooms when the fire detection and suppression systems were not functional for planned maintenance. Entergys corrective actions included stationing separate continuous fire watches in the east and west switchgear rooms, initiating condition report CR-VTY-2014- 4019, communicating and reinforcing the
fire watch requirements with all operating crews and maintenance personnel, and initiating additional training. This finding is more than minor because it is associated with the protection against external factors attribute of the
Mitigating Systems cornerstone and affected the cornerstone objective of ensuring the reliability of systems that respond to
initiating events to prevent undesirable consequences (i.e., core damage). Specifically, the east and west switchgear rooms are separate fire areas each containing separated trains of Appendix R
safe shutdown equipment which are required to respond to
initiating events to prevent undesirable consequences and the implemented compensatory fire watches were less than required by the
fire protection program. The inspectors used
IMC 0609, Appendix F, Fire Protection
Significance Determination Process, to analyze this finding because the condition had an adverse effect on the Fire Prevention and Administrative Controls Program element in accordance with the degradation rating guidance. The inspectors determined that the finding screened as Green because the impact of the fire finding was limited to no more than one train of equipment important to safety at any given time. This finding has a cross-cutting aspect in the area of Problem Identification and Resolution, Resolution, because Entergy did not take effective corrective actions when this issue was self-identified in a condition report on January 5, 2013.
