Text

Rev 4 to 0AP-025, Bnp Integrated Scheduling
	ML20197A937
Person / Time
Site:	Brunswick
Issue date:	02/25/1998
From:	; CAROLINA POWER & LIGHT CO.
To:	;
Shared Package
ML20197A925	List: BSEP-98-0047, Forwards Response to Request for Addl Info Re DG Surveillance Requirements for Proposed Rev to Tss.Procedures Encl; ML20197A928; ML20197A937;
References
	0AP-025, AP-25, NUDOCS 9803100038
	Download: ML20197A937 (54)
	v • d • e

.

0 ENCLOSURE 3 BRUNSWICK STEAM ELECTRIC PLANT, UNIT NOS.1 AND 2 DOCKET NOS. 50 325 AND $0 324/ LICENSE NOS. OPR 71 AND DPR 62 RESPONSE TO REQUEST FOR ADDITIONAL INFORMATION DIESEL GENERATOR SURVEILLANCE REQUIREMENTS l

OAOP 025.0, REVISION 4 BNP INTEGRATED SCllEDULING fDR M 00 24 P PDR

@g CAROLINA POWER & LIGHT COMPANY information mummmmmmmmmu BRUNSWICK NUCLEAR PLANT use PLANT OPERATING MANUAL ,

i'0LUME I BOOK 1 ADMINISTRATIVE PROCEDURE UNIT 0

mm ,,,,

@ FEB 2 51998 IllIll'Illi lllilllIll IllII - -e=

OAP-025 BNP Ik YEGRATED SCHEDULING REVISION 4 EFFECTIVE DATE a la 7 /18 Sponsor / : S ~- 2 -2 P- 7/

Sup int nd [O cheduling Cate l

Concurrence 2@ 9- f M6 nager ut ges d Sche . g Date Approval _

2 - Z f-f 6

5. erations Ar csh' Date :

0AP-025 Rev. 4 Page 1 of 53

REVISION

SUMMARY

Revision 4 of this procedure incorporates the following changes:

I Deletes Attachment 3. High Safety Significant (HSS) functions. The Maintenance Rule data base now identifies the HSS functions of each system.

Adds Attachment 5, Guidance for System Outage Determinations; this attachment contains information (previously included in Attachment 3) to assist in determining it work constitutes a system outage.

- Revises Figure 3 te transfer responsibility for approval signature to the Work Week Manager.

Deletes the requirement to enter the risk assessment information from Figure 4 into it.e AMMS scheduling comments field. Figure 4 provides adequate traceability of risk assessment.

- Deletes the requirement to schedule r; more than 2 Maintenance Rule systems to be out of service at a time. The safety significance of disabling Maintenance Rule system function is evaluated via EOOS evaluation of the final schedule.

- Replaces reference to BSP-35 with 0AP-023, Outage Planning and Implementation

- Revises Attachment 1,12-Week Rolling Schedule, and body of the procedu.e to reflect changes in system high safety significant determinations.

LIST OF EFFECTIVE PAGES Paaes Revision 1-53 4 0AP-025 Rev. 4 Page 2 of 53

-O TABLE OF CONTENTS SECTION PAGE 1.0 PURPOSE.........................................................................................................6 1.1 Purpose..... ..... ....................................................................................6 1.2 Objective................................................................................................6 1,3 Scope.....................................................................................................6

2.0 REFERENCES

.................................................................................................6 3.0 D E F I N I TI O N S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.1 Extended Work List (Forced Outage) ....... ... . ... ....... ................ ... . .. .. .... .. .. . 7 l 3.2 Fragnet....................................................................................................7- ,

! 3.3 H ig h S afoty S ig nifica nt System.. . .... .. . . . . . .... . . . .. .. .. ..... .. .. ... . . . . . .. . . .. . . .. ... .. ...... . . 7 I 3.4 Long R a ng e Pla n (LR P).. . . . .. . . . .. . . . .. . . . . . . . . . . . . . ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .. . . . . . .. . .. 7 3.5 Low Sa fety S ig nifica nt System . . . . . . . . . . . . .. . . . . . . . . . . . .. . . .... . . . . . . . .. . . . .. . . .. . . . . . . .. ... . . . . . 7 3.6 Manual Entries ....... ..........., ..... ............... ..... ........ ... ......................... ... 7 3.7 Pa ck a g e R e a d y. . . . . . . . . . . . . . . . . . . . . . . . . . . , . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 3.8 P ri o rity Wo rk L i s t . . . . . . . . . . . . . . . . . , . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 3.9 Syste m C o nditio n Sta teme nt . . . ... .... . . . .. . .. .. . .... .. . ... . . . ... . . . . . . . . . .. . . . . .. . ... . . .. . . 8 3.10 SystemOutage....................................................................................8 3.11 Ta s k R e a d y . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 3.12 Werk List Activities . . . ... . ... . . . . . .. . .... . .. . .... . . . . .. . . . ....................................8 4.0 R E S P O N S I B I L I TI E S. . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4.1 Fo rced O utag e C oo rdinato r.. . . . .. .. . . .. . . . .. ... .. ... .. ... . . . . . .. . .. . . .. . . . . . . . .... . . .. . .. .. 9 4.2 . I m p le m e n t o r . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 4.3 O uta g e s a nd S ch ed uling . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . 10 4.4 P ia nt E n g i n ee r. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 4.5 Pla nt Wo rk Units . ... .. . .. ... ... ... . . . . . . ... .. ... . ............................................11 4.6 Project Manager (Long Range Plan) ... ...... ........... ....... .... ....... .. .... . .... 12 4.7 Project Manager (System Outages and Downpowers). ..... . ..................... 12 4.8 Work Group Schedule Coordinator..... . .................... .............. .. ............. . 12 4.9 Wo rk Wee k M a n a g e r . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 OAP-025 Rev.4 Page 3 of 53

TABLE OF CONTENTS SECTION PAGE 5.0 i N STR U C Tl O N S . . . . . . . . . . . . . . . . . . . . . . ... . . . . . . . . . .. . . . . . . ..........................14 5.1 initial Scheduling of On-line Activities........................ . ... .. . .. ..... ... ... ......14 5.2 i On-line Schedule Development.. . ...... ....... . . ...... ...................14 5.2.1 On-line Schedaie Development Cycle. .... ...... . ...... . ..... . . ..... . 14 l 5.2.2 Stage 1 - System Outages and Unit Downpowers....... . ....... ..... 17 '

5.2.3 Stage II - Final Work List (Week T-4).. ... . .. ... ...... . ....... .... .. .. 17 5.2.4 Stage lli - Preliminary Work Schedule (Week T-3).... ...... ....... . .. 18 5.2.5 Stage iV - Final Work Schedule (Week T-2).. . . . . . . . . . . . . .. 19 5.2.6 Stage V - Schedule Review (Week T-1)........ .................... ....... 20 5.2.7 Stage VI - Work Week (Week T-0) ..... ..................................20 5.3 Authorization of Non Scheduled Priority 1,2, or 3 Work.. . . ........... . ........ 21 5.4 Post Work Critigues . ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . .....................23 5.5 Schedule Developmentof Outage Activities... .... .. ..... . . . . . .... .. 23 5.6 On-line System Outages and Voluntary LCO Entry. . .. .. .............24 5.6.1 System Outage & LCO General Guidance... .. .. .. ... ..... ...... .. 24 5.6.2 System Outage Pre-Planning., ... , ... . ..... ... . .. . ..... ... 25 5.6.3 System Outage Authorization. ... ... .... .. . . . . . . . . . . . ... 25 5.6.4 Emergent Failures / Changing Plant Conditions... . .. ... . . .. . .. . 27 5.7 Long Range Planning . .. . . . . ....... ... ... . . . . . . . . . . . . . . .............30 5.7.1 Long Range Plan Scope.... ... ....... . . . . . .. ... . . . .. 3 0 5.7.2 Identification of Activities to be included in the LRP...... ...... ..... . 30 5.7.3 LRP / Business Plan Interface.. . ... . . ........................31 6.7.4 Publication of the Long Range Plan .. . . .... .. .. .. ...........32 5.8 Forced Outage Scheduling........ ... .... ...... ... .... . .. .... ..... ....... 32 5.8.1 Forced Outage Schedule Composition.... . ... . ... .... . .. . . . . 32 5.8.2 Forced Outage Schedule Preparation and Review. .............34 5.8.3 Forced Outage Schedule Approval and Distribution., .. . . .. . 35 5.8.4 Forced Outage Schedule Revision... .... . . . . . . . . . . . . . . ... .. 35 5.8.5 Forced Outage Schedule implementation....... .................36 OAP-025 Rev.4 Page 4 of 53 m

TABLE OF CONTENTS FECTION PAGE FlmMES 1 On-line Schedule Development: Routine Deliverables .......................... ....... ......... 37 2 On-line Schedule Development: System Outage Deliverables..... ...................... ... 38 3 Sched ule C h a ng e Ap p roval Fo rm . . . . . . . . . .. .. . . . . .. . . . . .. . . . .. . . .. . .. . . . . . . .... . . . . . . . .. . . . . . . . . . .. . . . 3 9 4 Risk Assessment of Schedule Changes / Emergent Activities .... ...... ................ .. .. 40 5 Long Range Planning Process Overview........................... .. ........ . . ... ... ............ 41 l 6 Forced Outage Priority Ready to Work List ....................................................42 ATTACHMENTS 1 Twelve Week Rolling Sched ule . . . . . . . . . . . . ... . . . .. . . . ... .. . ... . . .. . . . .. . .. . . . . . . . . . . , . 43 -

l' l 2 Priority System Criteria Summary... ...... . .. .......... . ........... .. ............., . ... . 46 l

3 On Line Schedule Manual Entry Form ...... .. . ............... ............. ... ... ....... .. . 48 i-4 Methodology For Assessing and Managing Plant Risk ....... ... .. ................... 49 5 Guidance for System Outage Determinations .. .... .. ....... ....... .. ....... ... . .. .. 52 6 BNP Long Range Plan Activity Identification Form ........... .. .. . .... ..... ....... 53 OAP-025 Rev. 4 Page 5 of 53 x

1.0 PURPOSE 1.1 Purpose The purpose of this procedure is to provide additionalinstructions to identify the method by which the scheduling function identified in ADM-NGGC-0104, Work Management Process, is accomplished.

1.2 Objective The objective of this procedure is to ensure that work is scheduled in

accordance with cafety regulations, Technical Specifications, Code requirements, and guidelines so that the plant is rnaintained in o safe, reliable, economic, and environmentally sound manner.

l l 1.3 Scope i

This procedure provides the administrative controls necessary to implement j the scheduling functions identified in ADM NGGC-0104, Work Management Process.

2.0 REFERENCES

2.1 ADM-NGGC-0101, Maintenance Rule Program j 2.2 ADM-NGGC-0102, Project Review and Authorization l

2.3 ADM-NGGC-0103, Project Management !

2.4 ADM-NGGC-0104, Work Management Process i

- 2.5 Application of Probabilistic Safety Assessment to Maintenance Rule implementation, Brunswick Nuclear Plant 2.6 0AP-022, BNP Outage Risk Management 2.7 - 0AP-023, Outage Planning and implementation 2.8 OPLP-01.2, Fire Protection System Operability, Action, and Surveillance Requirements 2.9 OPLP-28, Startup And Power Ascension Management Plan For Unit Startup Following An Outage 0AP-025 Rev.4 Page 6 of 53 j

3.0 DEFINITIONS 3.'i Extended Work List (Forced Outage)

A list of work activiths not on the Priority Work List which require a unit outage to implement. The list is used as a " pick" list should the unit have an extended forced outage. Activities are identified (sorted) by " Ready to Work" or "Not Ready to Work".

3.2 Fragnet

/ Jetailed schedule of related work activities which includes logic relationships between the activities.

3.3 High Safety Significant System Those systems that are significant contributors to safety based on their 8 importance and contribution to nuclear safety as calculated in the Probabilistic Safety Assessment (PSA) for the Brunswick Nuclear Plant, and/or as determined by the Exper' Panel.

3.4 Long Range Plan (LRP)

The site plan consisting of the major projects, modifications,and maintenance activities scheduled in the ten year planning window.

3.5 Low Safety SignificantSystem Those systems that are D_oj significant contributors to safety based on their importance and contribution to nuclear safety as calculated in the Probabilir.'.ic Safety Assessment (PSA) for the Brunswick Nuclear Plant, and/or as determined by the Expert Panel.

3.6 PAanual Entries A work activity in the schedule which does not exist in AMMS but is required to support a WR/JO, or warrants schedule visibility. Due to the nature of these activities a sequentialWR/JO is not warranted.

3.7 Package Ready A work package that is complete in all respects, and ready for release to the field except for parts or other restraints which keep the activit, from being implemented.

0AP-025 Rev. 4 Page 7 of 53 I

_ a

3.8 Priority Work List (Forced Outage)

A list of work activities identified by plant Operations ?e oriority work which either requires Unit outage to work or should be workeo before returning the Unit to service. Activities are identified (sorted) by " Ready to Work" or "Not Ready to Work". The " Ready to Work" list identifies" Task Ready" items and should be utilized to determine work which will be performeo during a forced outage. The "Not Ready to Work" list should be utilized during non-outage periods to identify those priority items that should be made " Task ready" to support forced outage accomplishment.

3.9 Systern Condition Statement Conditions identified as " System Reliability" or " System Economic Alert" l within the CP&L Distribution System that requires specific actions by the WCC SCO to limit high risk plant evolutions during either of the alert conditions.

NOTE: The maintenance rule database identifies the high safety significant functions for each system. Attachment 5 provides guidance for determining if work or an emergent failure constitutes a system outage.

3.10 Syctem Outage System outage refers to the condition in which a system's high safety significant function (s) is disabled and not recoverable.

3.11 Task Ready A work package that is complete in all respects, availability of required parts and materials verified, and ready for release to the field when scheduled.

3.12 Work List Activities Preventive or corrective work activities which do not impact system or plant operation. These work activities require minimal coordination between work groups and do not conflict with other scheduled work.

l 0AP-025 Rev.4 Page 8 of 53

.4 4.0 RESPONSIBILITIES 4.1 Forced Outage Coordinator The Forced Outage Coordinatoris responsible for:

4.1.1 Assembling recovery plan and schedule review comments and coordinating the resolution of those comments.

4.1.2 Developing, reviewing and preparing preliminary (draft) schedules.

4.1.3 Recommending the release of the preliminary schedule and work list for plant review.

4.1.4 Producing the forced outage schedule and the corresponding work list (s).

4.1.5 Distributing the approved schedule and any subsequent revisions.

4.1.6 Developing individual"fragnets"when greater detailin scheduling will sig nificantly enhance implementation.

4.1.7 Maintaining an " Extended Work List" which may be issued for management review if an extended forced outage should occur.

4.1.8 Updating schedule progress during periods of implementationto include analysis of the critical path recovery plan.

f 4.2 Implementor The implementor is responsible for:

4.2.1 Providing work progress / status to Outages and Scheduling.

4.2.2 Notifying Outages and Scheduling if a WR/JO must be rescheduled.

0AP-025 Rev. 4 Page 9 of 53

4.3 Outages and Scheduling Outages and Scheduling is responsible for:

4.3.1 Developing, maintaining, and publishing worklist and schedules for the work activities governed by this procedure, including the following:

- Weekly Schedules On-line Schedule (Twelve Week Rolling Schedule)

Planned Outage Schedules and Forced Outage Fragnets

- System Schedules (as needed) 1.ong Range Plan 4.3.2 Improving plant safety and reliability by aligning scheduled work activities on a plant component basis, within the scheduling constraints allowed by the Technical Specifications and this procedure, so that the frequency of placing equipment out of service for routine maintenance is minimized.

4.3.3 Performance monitoring of the work management process.

4.3.4 Providing feedback to site management regarding the work j management process.

4.3.5 Performing risk assessment of the schedule in accordance with l

Attachment 4.

4.4 Plant Enginoer The Plant Engineer is responsible for performing reviews of overall system material condition, including open items, and providing recommendations for ,

work schedule and scope to ensure proper system performance. This includes participating in the development of weekly schedules and on-line system outage plans and schedules by:

4.4.1 Identifying the system outage scope.

4.4.2 Requesting a system outage schedule be developed.

4.4.3 Participating in the development of the system outage schedule.

0AP-025 Rev.4 Page 10 of 53

4.4 Plant Engineer 4.4.4 Recording the out of service time for high safety significant systems into the Maintenance Rule database.

4.4.5 Evaluating the total out of service time against Maintenance Rule unavailability performance criteria.

4.4.6 Providing recommendations to the BESS work group schedule coordinator with respect to scheduling system unavailability for maintenance rule in-scope systems.

4.4.7 Participating in the development of a post-system outage critique as requested by Outages and Scheduling Section.

4.4.8 Reviewing the Long Range Plan and providing recommendations on scheduled activities for future years.

4.5 PlantWork Units The plant work units, such as Operations, BESS, Maintenance, E&RC, and Outages and Scheduling, are responsible for:

4.5.1 Maintaining a file of Forced Outage " Priority Ready to Work" packages and verifying that the packages have no restraints for implementation.

" Priority Ready To Work" packages requiring clearances will have a copy of the clearancein the package.

4.5.2 Notifying the Forced Outage Coordinatorof any changes to the " Ready to Work" list.

4.5.3 Reviewing and recommending items for addition to or deletion from the forced outage " Priority"and " Extended" Work Lists.

4.5.4 Reviewing and approving the Forced Outage Schedule.

4.5.5 Notifying the Forced Outage Coordinatorof changes to the schedule or the "Friority Ready To Work" list.

4.5.6 Identifying activities to be incorporated into the Long Range Plan.

4.5.7 Reviewing the Long Range Plan and providing updates for assigned activities.

0AP-025 Rev. 4 Page 11 of 53

_J

4.6 Project Manager (Long Range Plan)

The LRP Project Manager is the individual responsible for ensuring schedule, cost, and supporting information as shown in the LRP for assigned activities is accurate.

4.7 Project Manager (System Outages and Downpowers)

The Project Manager is responsible for the development, execution, and post activity critique of the plan and schedule for assigned activitios, such as unit downpowers and on-line system outages. Typical tasks include:

3 4.7.1 Conducting initial scope meetings to identify WR/JOs, Engineering

, documents, LCOs, Operator Workarounds, RTGBs, pts, MSTs, PMs, etc., which are proposed for the system outage or downpower.

4.7.2 Reviewing lessons learned from previous system outages or downpowers.

4.7.3 Tracking and ensuring compliance to milestones. Initiating a Condition Report for non-compliance.

4.7.4 Reviewing progress with Superintendent, On-line Scheduling as requested.

4.7.5 Processing scope changes after scope is trozen utilizing Figure 3.

4.7.6 Ensuring radiation dose budget is identified and communicated to the i site.

4.7.7 Briefing applicabic site personnel on the schedule and expectations prior to implementation.

4.7.8 Participating in Readiness Challenge meetings.

4.7.9 Conducting and documenting formal post-work critiques.

4.8 Work Group Schedule Coordinator The work group schedule coordinators for on-line schedule development are responsible for:

4.8.1 Ensuring their work group is properly represented at each on-line schedule development meeting.

0AP-025 Rev.4 Page 12 of 53 j l

l

_ .____j

4.8 Work Group Schedule Coordinator 4.8.2 Reviewing the scheoule . o.) worklist prior to the meeting, identifying and cammunicating conflicts, concerns and c 'mments prior to the meeting.

4.8.3 Notifying Outages and Scheduling prior to changing the scope of corrective action or duration of work and assisting in the review of possible schedule impact.

4.8.4 Obtaining approval f'or items remaining on the schedule which are not

" package ready" or " task ready".

4.8.5 Assisting in reviews of system or component backlogs and emergent work to incorporatt work activities into the appropriate work windows.

4.8.6 Incorporating schedule changes resulting from implementor walkdowns, such as work duration, interference removal, support requirements, clearances, etc.

4.8.7 Providing manpower resource availability to Outages and Scheduling at least 7 weeks ahead of the work week initially and subsequent resource availability changes as they occur.

4.8.8 Minimizing unavailabili'y of high safety significant systems therugh effective coordination of work activities.

4.8.9 Reviewing ESF system / train outages in accordance with the 12 week schedule and/or Attachment 4 for on-line system outages.

4.9 Work Weck Manager The Work Week Manager is responsible for:

4.9.1 Monitoring and expediting the preparation and implementation of the schedule, including system outages, plant evolutions, and individual wnrk activities.

4.9.2 Review and resolution of Technical Specification compliance issues related to the schedule.

4.9.3 Performing risk assessment of the schedule in accordance with Attachment 4.

4.9.4 Approval of the Weekly Schedule.

4.9.5 Ensuring work is accomplished as scheduled.

0AP-025 Rev.4 Page 13 of 53

~ .

5.0 INSTRUCTIONS 5.1 Initial Scheduling of On-line Activities During the WR/JO initiation and review process WR/JOs are classified into categories, prioritized, and approved for scheduling, These categories include refuel outages, on-line system / train windows, and im :ed outages. ,

The basis for the schedule for the operating cycle is the Twelve Week Rolling Schedule identified in Attachment 1. This colling schedule is comprised of recurring " windows of opportunity" for implementing work on plant systems. T' , system windows are aligned to minimize the risk of challenging the L '-)

5.1.1 Outages and Scheduling will review the maintenance backlog and identify the appropriate work week for the WR/JOs and Action Requests in AMMS in accordance with the twelve week rolling schedule or outage schedule.

5.1.2 Outages and Scheduling will review and revise the WR/JO priority and work condition code in AMMS as necessary to ensure the codes l are appropriate.

5.1.3 Outages and Scheduling will align schedule dates for related work activities to minimize the number of times equipment is taken out of service and system or component unavailability.

5.2 On-line Schedule Development Beginning seven weeks prior to the implementation week, schedule development begins for on-line activities. This is accomplished in six stages by utilizing a team approach. The team consists of work group schedule coordinators for Maintenance, Operations, BESS, E&RC, Materials, and Scheduling.

NOTE: Figures 1 and 2 provide an overview of the deliverables contained in the steps below.

5.2.1 On-line Schedule Development Cycle l

1. Outages and Scheduling wi!! nroduce the work lists and schedules and coordinate the meetings identified below.

0AP-025 Rev. 4 Page 14 of 53

5.2.1 On line Schedule Development Cycle

2. Outages and Scheduling rany deviate from the schedule identified below if deemed appropriate based on factors such as holidays, and alternate work schedules.

3. Superintendent, Online Scheduling may authorize omission of deliverables identified below, if deemed appropriate.

4. Work group coordinators and Outages and Scheduling will review and develop the schedule for the implementation week in accordance with the methodology identified in Section 5.6 and Attachment 4

5. Post work tests required to support system operability will be coordinated by Operations and are not normal!y scheduled.

6. During the development cycle, On-line Scheduling will monitor work window scope, development of work window and system outage schedules, and the completion of prerequisites including:

l a. Evaluation of total duration available for the work window.

b. Time and resource requirements to complete the scheduled work.

c. Risk associated with work scope expansion and meeting plant conditions.

7. Common work activities will be evaluated for impact to both units by the work group coordinators and On-line Scheduling.

NOTE: OPLP-28, STARTUP AND POWER ASCENSION MANAGEMENT PLAN FOR UNIT STARTUP FOLLOWING AN OUTAGE, Attachment 11 can be used to identify common systems.

8. The Final Work Schedule will:

a. Include approved carryover items from the previous work week. Approval of these items will be requested by the Work Group Schedule Coordinator via Figure 3.

b. Include " Work List activiCes". Work List activities are authorized to be worked at any time during the scheduled work week.

4 0AP-025 Rev. 4 Page 15 of 53

5.2.1 On-line Schedule Development Cycle

c. Contain a cover sheet, on-call roster, schedule, resolution report, and system fragnets as needed,

d. Include status 02,10 and 11 activities on the resolution report.

9. A Project Manager should be assigned for the following types of

- activities unless deemed unnecessary by the Superintendent, On-line Scheduling.

a. System Outages on High Safety Significant systems.

l b. Unit downpowers involving the following:

- Non-routine unit downpowers which include maintenance activities requiring external coordination, such as vendors, contractors and consultants.

Activities which result in the unavailability of a High Safety Significant syst'm.

Activities which result in a Technical Specification system being inoperable.

10. Due to increased potential for System Reliability or Economics Alerts:

a. During December, January, and February, evolutions which have the potential to initiate a plant transient shculd be scheduled during the later part of the morning (starting at 1000 hours0.0116 days 0.278 hours 0.00165 weeks 3.805e-4 months ) or as coordinated with the System Dispatcher.

b. During June, July, and August, evolutions which have the potential to initiate a plant trannient should be seneduled during the early part of the day (completed prior to 1300 hours0.015 days 0.361 hours 0.00215 weeks 4.9465e-4 months ) or as coordinated with the System Dispatcher.

11. Manual entries to the online schedule will be requested and approved in accordance with Attachment 3, On-line Schedule Manual Entry Form. Figure 3 will also be required for approval or additions ;

following the schedule development meeting on Tuesday of I Week T-2.

0AP-025 Rev. 4 Page 16 of 53 I

n -

l

5.2.2 Stage 1 - System Outages and Unit Downpowers

1. The Work Group Schedule Coordinators will provide manpower resource availability to Outages and Scheduling at least 7 weeks ahead of the work week.

2. The Plant Engineer will normally identify the need for a system outage by Monday of Week T-7.

3. A Project Manager will normally be assigned for the system outage by Monday of Week T 7.

4. In Week T-6 the Project Manager will normally:

Identify the preliminary scope of the System outage.

Initiate schedule development and initial schedule reviews by the Plant Engineer and Work Week Manager.

5. Outages and Scheduling will normally issue a preliminary system outage schedule (fragnet) on Wednerday of Week T-5 for scheduled system outages.

5.2.3 Stage 11 - Final Work List (Week T 4)

1. The Final Work List will be developed oy incorporating PMs, pts, MSTs, Models, Action Requests and WR/JOs.

I

2. The Final Work List will normally be issued on Monday of Week T-4.

3. The Final Work List will normally be rewewed on Thursday of Week T-4.

4. For system outages the Project Manager should receive resolution of Engineering issues for activities in the system outage by Monday of Week T-4.

0AP-025 Rev. 4 Page 17 of 53

5.2.4 . Str.ge lli - Preliminary Work Schedule (Week T-3)

NOTE: The Preliminary Work Schedule places the Final Work List in schedule format.

I

1. The Preliminary Work Schedule will include WR/JOs with work status codes 02 through 20, Action Requests, and " manual entries".

2. The Preliminary Work Schedule will normally be issued on Monday of Week T-3.

3. The Preliminary Work Schedule will normally be reviewed on Wednesday of Week T-3,

4. The preliminary system outage schedule will norma;ly be reviewed on Wednesday of Week T-3.

S. The review of the Preliminary Work Schedule on Wednesday of Week T-3 results in the " Scope Freeze" of the Work Schedule, including the system outage scope.

6. To add a work activity to the schedule after the Wednesday review meeting the requestor will deliver the Figure 3 and Figure 4 if applicable, to the Work Week Manager for approval.

7. On-line Sclieduling will input the schedule change approved via Figure 3. 4

8. Scheduled work packages should be planned and reviewed by '

Wednesday of Week T-3. Packages not planned will be discussed at the schedule ' view meeting.

9. The Superintendent, On-line Scheduling may assign action items to the work group schedule coordinators to provide clarification or explanation of restraints and may request anticipated resolution dates be identified.

0AP-025 Rev. 4 Page 18 of 53

. . . . . _ . . ___ J

5.2.5 Stage IV - Final Work Schedule (Week T-2)

1. Clearances should be prepared for the scheduled activities by l Sunday of Week T-2 at 24:00 nours.

2. The Final Work Schedule will normally be issued on Monday of Week T-2.

3. On Wednesday of Week T-2 Work Week Managers will normally perform an internal review of the Final Work Schedule. l

4. The Final Work Schedule will normally be approved by management on Thursday of Week T-2.

5. After approval of the Final Work Schedule deletions from the schedule will be requested via Figure 3.

6. To remain on the schedule after the schedule development meeting on Tuesday of Week T-2, WR/JOs shall be " task ready" or approved at or before the meeting by the Work Week Manager via Figure 3, l Schedule Change Approval Form.

7. The Work Week Manager and Work Group Schedule Coordinators shall track work package development for WR/JOs which are not

" task ready" after Tuesday to ensure no scheduling conflicts arise.

8. Following issuance of the Final Work Schedule and prior to implementation of the schedulc (Week T-0) a final risk assessment of the schedule will be performed by the Work Week Manager and On-lina Scheduling using the methodology described in Attachment 4.

9. Following the schedule development meeting on Tuesday of Week T-2,mc antries to the schedule will be requested and approved via At* .t 3 and Figure 3.

0AP-025 Rev. 4 Page 19 of 53 s -

5.2.6 Stage V - Schedulo Review (Week T-1)

1. The Final System Outage Schedule will normally be reviewed with the Plant General Manager during Week T-1.

2. The system outage " team" should perform a final review of outage readiness and prepare pre-job briefs by Friday of Week T-1.

3. A risk assessment using methodology such as Equipment Out of Service (EOOS) of the Final Work Schedule should be performed.

This assessment will evaluate the cumulative risk impact of scheduling multiple systems out of service as well as removal of high safety significant equipment from service.

5.2.7 Stage VI - Work Week (Week T-0)

1. During Week T-0 the Work Schedule will be updated and published as deemed appropriate by the Superintendent, On-line Scheduling, based on the impact of emergent changes.

2. Operations will conduct a Daily Schedule Review Meeting to facilitate schedule adhererice.

3. Addition of carryover itemt for the subsequent week will be req':ested by the Work Group Schedule Coordinator via Figure 3, for approval no later than the Friday Daily Schedule Review Meeting.

4. Publication of a revised work schedule, if needed will:

a. Include changes approved since the last publication.

b. Exclude items that are field work complete,

c. Reflect status changes from AMMS.

0AP-025 Rev. 4 Page 20 of 53

5.3 Authorization of Non-Scheduled Priority 1,2, or 3 Work On occasion windows of opportunity will exist that will allow the accomplishment of priority 1,2, or 3 work that is not on the Work Schedule.

In order to accommodate this work and ensure the impact has been reviewed by the Work Week Manager and On-line Scheduling Unit or the Shift Outage Manager during ot.. ages, the following shall take place:

On-Line Work Activities 5.3.1 For on-line work activities the requesting unit representative will:

1

1. Obtain determination if the change impacts plant risk as described in Attachment 4 and if so obtain a risk assessment via Figure 4. ,

2. Deliver the work package attached to Figure 3, and Figure 4 if applicable, to the Daily Schedule Review Meetings for approval, when feasible.

l 3. Obtain approval from the Work Week Manager or designee, via 1 Figure 3, Schedule Change Approval Form.

NOTE: The Operatio, s Shift Superinundent may approve Figures 3 and 4 on f weekends, holidays, or backshifts. Operations will then deliver the original j Figures 3 and 4 to Online Scheduling.

g

4. Return the dispositioned Work Package to the implementing organization.

0AP-025 Rev. 4 Page 21 of 53

5.3 Authorization of Non-Scheduled Priority 1,2, or 3 Work 5.3.2 Ti>o Discipline Scheduler will schedule approved work activities in the on-line schedule.

5.3.3 Work packages not approved for schedule addition are retained by the implementing organization until scheduled.

Outage Work Activities 5.3.4 For outage work packages, the requesting unit will deliver the work package to the Shift Outage Manager (SOM) for disposition. Figure 3 is not required.

1. The SOM will evaluate if the proposed work is significant to safety in accordance with 0AP-022 Section 8.0.

2. The SOM will evaluate outage scope addition / change requirements in i

accordance with 0AP-023.

3. The SOM will annotate approval directly on the outage work package rather than using a Figure 3.

4. The requesting unit will return the outage work package to the -

Implementing unit.

5. The Implementing unit will obtain WCC authorization for the outage work package.

0AP-025 Rev.4 Page 22 of 53

_ _ . . _ . .. . . _ _ _ _ _ _ _ _ . A

4 S.4 Post Work Critiques 5.4.1 Post Work critiques will be performed by the Project Manager following System Outages and Unit Downpowers as deemed appropriate by the Superintendent, On-Line Scheduling.

5.4.2 The critique will include each work group involved.

5.4.3 The critique will include the following information:

Unit number System number Division and Train Scheduler name

- Comparison of scheduled versus actual Work Window start and finish dates and time.

Comparison of scheduled versus actual system unavailability

, time.

Comparison of scheduled versus actual LCO time.

Original scope description, j Identification of scope changes.

L -

Identification and explanation of scope not completed.

Identification of lessons learned.

Identification of applicable CRs 5.5 Schedule Development of Outage Activities 5.5.1 Work scope and schedule development for planned Unit outages will be controlled in accordance with 0AP-023, Outage Planning.

5.5.2 The process for work scope control and scheduling for forced Unit outages is described in Section 5.8.

0AP-025 Rev.4 Page 23 of 53

0 5.6 On-line System Outages and Voluntary LCO Entry Planning or scheduling of on-line system outages on high safety significant systems er LCO entries during plant operations shall be performed in accordance with the folicwing guidelines. This guidance is applicable to on-line operation including operation during post outage power ascension from Mode 2 through 100% stable power operations.

5.6.1 System Outage & LCO General Guidance

1. The intent of this guideline is to enhance the reliability and availability of Maintenance Rule systems, structures, and components.

2. The intent of this guideline is to enhance safety by considering initiating events, mitigating capability and containment integrity when removing equipment from service for monitoring or maintenance.

3. It is acceptable to enter an LCO or an on-line system outage, when the intent is to increase reliability or to reduce shutdown risk associated with safe ahutdown/ decay heat removal systems or components.

4. LCOs should not be entered if the work will not be completed prior to a planned reactor mode change.

5. The total cut-of-service time for Technical Specifications required equipment and high safety significant systems or components should be minimized in order to balance system availability and reliability.

6. The following Figures and Attachments provide additionalinformation associated with the instructions below:

Figure 2, On-line Schedule Development: System Outage Deliverables Attachment 1, Twelve Week Rolling Schedule Attachment 4, Methodology for Assessing and Managing Plant Risk Attachment 5, Guidance for System Outage Determination 0AP-025 Rev. 4 Page 24 of 53

5.6.2 System Outage Pre-Planning

1. Pre-planning shall be conducted to identify related preventive maintenance, corrective maintenance, inspections, testing, major / minor modifications, and commitments that could be performed during the out-of-service time frame. The identified system outage scope will enhance system reliability and maximize system availability.

2. Preplanning should assure procedures, parts, permits, clearances, manpower and tools required for the work activity are ready and special training performed prior to removing the equipment from service.

3. On-line system outages on high safety significant systems will be worked on a 24 hour2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months per day bas:s and have a Project Manager assigned unless prior Superintendent, On-line Scheduling soprovalis obtained.

I 4. Contingency plans and compensatory measures will be developed as l deemed appropriate by the Project Manager. The Project Manager L

will evaluate worst-case scenarios and discuss during pre-job briefings how Operators would respond given the unavailability of certain equipment.

5.6.3 System Outage Authorization

1. Plant General Manager approval is required prior to scheduling:

System outages on HPCI.

HPCI outages concurrent with another system outage.

EDG outages concurrent with a RCIC outage or Service Water outage More than two high safety significant systems to be out of service concurrently.

Activities which exceed one half the allowable LCO time.

0AP-025 Rev. 4 Page 25 of 53

O 5.6.3 System Outage Authorization

2. Work Week Manager and Superintendent, On-Line Scheduling approval is required prior to scheduling:

System outages.

Combinations of system outages.

3. PSA guidance is required prior to entering system outage combinations exceeding 7 days in length.

NOTE: Combinations of a system and/or the support systems required to provide the high safety significant function are considered as one high safety significant system.

EXAMPLE: Combinations of the following systems for one diesel generator would be considered one high safety significant system outage:

- 5095, Diesel Generators 5100, Diesel Fuel Oil

- 5105, Diesel Lube Oil 5110, Diesel Jacket Water

- 5111, DG Service Water & Demineralized Water 5112, Diesel Generator Starting Air

- 5113, Diesel Generator intake / Exhaust

4. On-line Scheduling will ensure the appropriate level of management has approved systam outage entry in accordance with these guidelines, j 0AP-025 Rev. 4 Page 26 of 53

5.6.4 Emergent Failures / Changing Plant Conditions

1. If an emergent component failure occurs or plant cotiditions change, the Shift Superintendent shall determine if the failure or change in plant conditions impacts plant risk by using the methodology identified in Attachment 4.

2. To manage the risk impact of emergent failures or changing plant canditions the Shift Superintendent will:

a. Ensure applicable Technical Specification requirements are met.

b. Ensure the plant is maintained in a safe and stable condition.

c. Return the component or system to service as soon as possible.

d. Minimize routine maintenance on the system during repair activities.

e. Be aware of the risk significance of the emergent failure or l

change in plant conditions, including severe weather conditions, and the impact on the Operator's ability to control the plant, mitigate events, or place and maintain the unit in a shutdown condition.

NOTE: Equipment Out of Service (EOOS) software and/or the PSA group may be consulted to assist with determination of risk significance, if needed.

NOTE: The Maintenance Rule database and reports can be used to identify '

high safety significant functions for each system. Attachment 5 provides guidance to assist in determining if a failure constitutes a system outage.

f. Delay scheduled system outages which have not started until plant conditions are favorab!e or until a risk assessment determines that beginning the system outage is acceptable.

g. Determine whether implementation of contingency plans or compensatory measures are warranted for plant configuration to ensure that back up systems are available and functional.

0AP-025 Rev.4 Page 27 of 53

i 5.6.4 Emergent Failures / Changing Plant Conditions

3. When notified by the Unit SCO that a System Reliability or System Economics Alert has been issued by the System Dispatcher, the WCC SCO will:

a. Review authorized work activities. The Weekly Schedule, AMMS, logs and the FIN team SCO may be used to identify authorized work activities.

b. Identify those activities that may constitute a high risk evolution or condition. The following is a list of MSTs that have been ider,tified as high risk evolutions:

Half Scram MSTs RPS27Q, Scram Discharge Volume Half Scram (also valving on reference Leg)

Valving on Critical Reference Leg MSTs FWC210, FWC RSDP RPV Channel Calibration RSDP210, RSDP and RTGB Panel RPV Water Level Indication RCIC270, RCIC High Water Level RSDP Trip

c. Identify the necessary actions to be taken relative to the risk associated with each activity.

d. Perform necessary actions for a System Reliability Alert including Monthly, quarterly, and refueling frequency half scram and half Group 1 MSTs should be delayed based on not exceeding the over due date.

- MST FWC210, RSDP210, and RCIC270 should be delayed based on not exceeding the over due date.

Based on its urgency, critical or high risk evolutions identified by the WCC SCO or defined in OPLP-17 should be delayed.

0AP-025 Rev. 4 Page 28 of 53 r .

. - 4.

3.6.4 Emergent Failures! Changing Plant Conditions

e. Perform necessary actions for a System Economic Alert

!ncluding:

With the exception of RPS270, monthly, and quarterly frequency half scram and half Group 1 MSTs should be performed as scheduled.

Refueling frequency half scram and half Group 1 MSTs should be delayed based on not exceeding the over due date.

- MST FWC910, RSDP210, and RCIC270 should be :

delayed based on not exceeding the over due date.

- Based on its urgency, critical or high risk evolutions identified by the WCC SCO er defined in OPLP-17 should be delayed.

f. Notify the implementing Organization's Superintendent or s heduling coordinator of the following:

- Impending alert condition

- Anticipated length or changes in length of alert condition

- Scheduled activities which should be stopped, if feasible

- Scheduled activities which should be delayed

g. Notify the Control Room of the status of work activities that ;

constitute a high risk evolution or condition.

0AP-025 Rev. 4 Page 29 of 53

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

l 5.7 Long Range Planning !

l

ADM NGGC-0102 provides instructions and reouirements for long range planning. This procedure should be used in conjunction with ADM NGGC-0102.

NOTE: Figure 5 provides an overview of the long range planning process.

5.7.1 Long Range P!an Scope The BNP Long Range Plan (LRP) identifies the major activities j proposed to be implemented through the end of licensed plant life. '

This includes pending and authorized Projects (as defined in ADM NGGC-0102) as well as major maintenance activities. The following types of major maintenance activities may be included:

- Major programs / initiatives (include those with defined durations, exclude ongoing baseload items)

- Refueling Outages

- Annual Emergency Preparedness Exercises

- Activities consuming significant resources or dose

- Significant NRC or INPO Assessments and Evaluations

- Corrective Maintenance

- Preventive Maintenance with a frequency greater than every refueling cycle 5.7.2 Identification of Activities to be included in the LRF

1. Addition of activities to the LRP should be proposed via Attac.hment 6,

,1NP Long Range Plan Activity Identification Form, or t.a ADM-NGGC-0102 Form 1, Phased Project Authorization Form.

2. The Outages and Scheduling (O&S) LRP Coordinator may odd activities to the LRP without use of Attachment 6.

3. If EESY analysis has not been performed the benefit to cost ratio and net present value may be omitted.

0AP-025 Rev. 4 Page 30 of 53

5.7.2 Identification of Activities to be included in the LRP

4. The cost estimate should be identifieo by the following cost types:

Materials (GSM)

Contract services (LNC)

Company labor (GSL)

Other (GSO)

5. Approval signature by Sponsor / Initiator's Section Manager and by Section Managers impacted by the project (minor support

! involvement excluded)is required. !

i i

6. The approved Attachment 6 should be submitted to the Outages &

Scheduling (O&S) LRP Coordinator.

7. If cost estimate 2 $50k, the O&S LRP Coordinator will coordinate with Financial Services Unit to obtain:

Authorization requirements (phased or routine)

Classification ruling (O&M or capital)

Assignment of FAIM number,if applicable

8. The O&S LRP CoordinatorwlIl maintain a list of proposed additions and periodically obtain management review and approval.

9. The O&S LRP Coordinatorwill update tne LRP accordingly.

5.7.3 LRPl Business Plan interface I

Updates and publications of the LRP will be integrated with the Business Planning Calendar.

0AP-025 Rev.4 Page 31 of 53 I

5.7.4 Publication of the 1.ong Range Plan

1. The LRP should be dynamically maintained inroughout the year and i periodically reviewed by the PRG.

2. The LRP will be formally reviewed by in. m 3 and approved by the Site Vice President twice a year as identified in ADM NGGC 0102.

6.8 Forced Outage Scheduling i

The following identifies the process to be used for the preparation, review, I approval, distribution,and revision of the BNP Forced Outage Schedule (s).

5.8.1 Forced Outage Schedule Composition

1. The Forced Outage Schedule should be based on those activities on the PriorityWork List which are task ready.

2. Those activities on the Priority Erk List which are not task ready should receive attention during ilon-outage periods to be made l

" Task ready" to support forced outage accomplishment.

3. The Schedule " Priority Ready to Work" list should consist of priority items identified by Operations which possess the following attributes:

4

a. Those packages %ntified by AMMS with a 1540 (Implementor Review Complete) status through a 20 status with support items (clearance, RWP, scaffolding plan, etc.) complete should be included.

NOTE: Status 1540 indicates that prerequisites for work have been satisfisd and when plant conditions allow, work may proceed immediately.

b. The ready to work status of each activity has been verified by the Forced Outage Coordinator.

c. Work activities whose duration is greater than 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months should be excluded, unless apprnved by Management.

0AP.025 Rev.4 Page 32 of 53

5.8.1 Forced Outage Sch.dule Composition

d. The plant mode required for implementation snould be 3 or 4.

e. Work requiring vendor support or off site expertise w..ich car.not be mobilized within 12 hours1.388889e-4 days 0.00333 hours 1.984127e-5 weeks 4.566e-6 months should be excluded.

f. Work which affects the corresponding operating unit should be i excluded (i.e., work should not be scheduled that would place the operating unit in an LCO or in anyway jeopardize its ability to maintain an operating status).

g. Work which requires a " Safe Shutdown" Risk Assessment or decreases safe shutdown " defense in depth" should be excluded, unless approved by management.

4. The Forced Outage Schedule should be formattedio depict the following outage scenarios:

I

a. Mode 3 Outage (3 day t chedule).

b. Mode 4 outage with no drywell entry (5 day schedule),

c. Mode 4 outage with drywell entry (7 day schedule).

5. Each scenario identified in Step 5.8.1.4 should include:

a. Items required to return the unit to an operating status (i.e.,

critical path recovery plan to be incorporated at the time of the outage).

b. Previously identified items that are required by Technical Specifications or a Regulatory Commitment to be corrected prior to Mode ascension once in that mode,

c. Those work items identified by Operations that would affect future plant operationsif they failed subsequent to restart.

d. Periodic Tests (pts) and Maintenance Surveillance Tests (MSTs) that are required to be curreat prior to leaving the applicable mode.

e. Shutdown and startup sequences.

0AAO?S Rev. 4 Page 33 of 53 emvm

5.8.2 Forced Outage Schedule Preparation and Review

1. The Superintendent, Outages will:

a. Ensure that comments received from the Plant General Manager, Operations, Maintenance, E&RC and Engineering are incorporated into the forced outage program by the Forced Outage Coordinator.

2. l'he Forced Outage Coordinatol will:

a. Conduct forced outage planning /reviewmeetings as necessary to maintain current forced outage schedules. ;

l l

b. Ensure comments are incorporated into the schedule and the

" Priority Ready to Work" list.

c. Produce a schedule that conforms to Step 5.8.1.5 and the

" Priority Ready to Work" list.

d. The " Priority Ready to Work " list should contain the attributes shown in Figure 6. t

e. Maintain an " Extended Work" list to be used in the event that an extended forced outage should occur. This includes verifying the ready to work status of each activity on the " Extended Ready To Work" list.

0AP-025 Rev.4 Page 34 of 53 cv e

5.8.3 Forced Outage Schedule Approval and Distribution

1. The Superintendent, Outages will:

a. Ensure, that the Forced Oaiage Schedules are reviewed with the appropriate managers prior to issuing the schedW3. Emphasis will be en changes since the previous schedule was issued.

j

b. Issue the approved schedule on the first Monday of each month fo Unit 2 and the third Mondayof each month for Unit 1. The schedule will be issued electronically or manually to :

- Plant General Manager

- Work ControlCenter

. Work Week Managers

! . NRC Site Representative 4 - SuperintendentOn-line Scheduling

. Operations Manager Operations Shift Supcintendent

. I&C and MechanicalSuperintendents

. Engineering Manager

. Maintenance Manager E&RC Manager

- Outage and Scheduling Manager 5.8.4 Forced Outage Schedule Revision

1. The Forced Outage Coordinatorwill;

a. Between revisions, receive proposed changes to the schedule anytime during the month, review the proposed changes and incorporate the necessary changes into the next schedule revision.

b. Identify revisions to the schedule beginning with the year and followed by a numericaldesignator for the appropriate month (i.e.,97 5 for May).

c. Ifissued manuallyinclude a coverletteridentifying and explaining the changes from the previous Forced Outage i P-025 Rev. 4 Page 35 of 53

5.8.5 Forced Outage Schedule implementation

1. The On line Scheduling unit representativeon the Scram incident Investigation Team (Silt) Roster or the Operations Shift Superintendentshuuld call the Superintendent,on line Scheduling and the Superintendent, Outage Mcnagement to notify them that the unit is in a forced outage.

2. Upon notification of the forced outage, the Superintendent,on-line Schedulingorthe Superintendent, Outage Management shouldcall the Unit Lead Scheduler, Forced Outage Coordinator, and the Discipline Scheduler and provide them with the direction required to i effect unit recovery and startup.

3. The Unit Lead Scheduler should develop a Recovery Plan that corrects the conditicn that placed the unit in a forced outage.

4. The Forced Outage Coordinator should coordinate the integration of l items from the " Priority Ready To Work" list, with the appropriate Forced Outage Schedule, the Critical Path Recovery Plan, and s-activities from the On line Weekly Schedule required to support startup into the Integrated Fe'ced Outage Schedule.

0AP-025 Rev 4 Page 36 of 53

FIGURE 1 Page 1 of 1 On-line Schedule Development Routine Deliverables WEEKS T-7/T4 WEEK (-4 WEEK T-3 WEEK T-2 WEEK T-1 WEEKT4 i R$onday: R$onday: Sunday: Final Risk Assessment Clesances prepared compW issue Final issue Preliminary Schedule W ork List Work Schedule W: .cAn witation issue FinalWork i Schedule Daily Schedule Review

!ac;;oss Tuesday:

Final Schedule Wednesday: Review rneeting Revised Weekly Preliminary WR/JOs Task Ready Schedule Schedule Review (restraints removed) meetrig or isW as W Figure 3 approved to WR/JO planning & remain on the schedule reviews complete .

(Mainte) gg Thursday:

intemalrevew of Scope Frozen 9g FinalWork List Review meeting .

MewTwit approval of Fina: Work schedule OAP-025 Rev.4 Page 37 of 53

FIGURE 2 Page 1 of 1 On-line Schedule Development: System Outage Deliverables WEEKS T-7/T-5 WEEK T-4 WEEK T-3 WEEK T-2 WEEK T-1 WEEK T-4 Monday (Week T-7): _ Monday: Wednesday: Monday: Saturday Need for System Ou' age through Friday:

icentMed Preliminary System issue Final sche *M Final Schedule Project Manager assigned Engineering gg, gyg for PGM review revewed with PGM Schedule Complete- Review Meeting implementaten Monday (Week T-6): To include But Not Coverage determinec Original scope identified Limited to: Team perfonn final WR/JO planning &

reviews comp!ete T h ar review of outage Begin schedule (fragnet) - ESRs/ Minor Mod read: ness:

development packages Final System Outage Parts Scope frozen Schedule Reven A1. ARA Fr' day (Week T-6): - Special Procedures Meeting Schedule Project Manager, System Work oackage Manpower Engineer, and Work Week - Review Team WR/JOs Task Ready Clearances restraints identified Managerinitial review of Eva!uations Complete (restraints removed) PMTs.tCOs schedule er WR/JO scope Figure 3 approved to Compensatory Week T-6 & T-5: remain on the Measures Schedule comments schedule Pre-job brefs prepared incorporated Wednesday (Week T-5):

Issue Preliminary System Outage Schedule NOTE: Superintendent, On-line Scheduling may authorize omission of deliverables if deemed appropriate.

0AP-025 Rev. 4 Page 38 of 53

FIGURE 3 Page 1 of 1 Schedule Change Approval Form SECTION I: SCHEDULE ITEM SPECIFICS Unit: Work Week (s): Date:.__ Requester:

i WR/JC PM/JO System # Current Scheduled Date Rescheduled Date Reason For Change:

/

Requestor Date SECTION ll: RISK ASSESSMENT Does the change impact plant risk as described in Attachment 4.

Circle one: Yeo / No if yes, proceed to Figure 4. If no, provide explanation below.

Comments:

Approval: /

Work Week Manager or - /Date Shift Superintendent

=_

0AP-025 Rev. 4 Page 39 of 53 a

FIGURE 4 Page 1 of 1 Risk Assessment of Schedule Changes / Emergent Activities

! NOTE: The risk assessment methodology identified in Attachment 4 shall be I

used to perform this assessa.9nt. Equipment Out of Service (EOOS) software and/or the PSA group may be consulted to assist with risk assessment if needed.

WR/JO PM/JO# __ System #

RISK ASSESSMENT

.=

Prepared by: /

Title:

/Date Approval: /

Work Week Manager or /Date Shift Supenntendent 0AP-025 Rev.4 Page 40 of 53

_J

4 FIGURE 5 Page 1 of 1 Long hnge Planning Process Overview IDENTWY PROPOSED Adelfl0N TO LflP 6PONsORI PROJE CT tsANAGER & 1 I (DENTiflCD F REVISONS OfMTifY & OBTAfN APPR(WAL Et

! PROJECT tlANAMR AND

$PON90feNO DECTION IaANAOut i OBTAI aus ss law wo.N AM'ROVAL stCi m eOrns CHALLE , Rom N.o.t -

4 IDENTrito REVISIONS SUBast 4 048 LHP 000RDWATOR 1 F MA (NT I LRP Rtyltw '

D""I" N 7

FAltp 9 ASSIONRL M IDE NTIFIL D REVillONS *,AUTHOPLJATION,Ad,QulfERENTS gygg og y ggg ggg 1F 1F RtwutST PHA$t AUTHOR 12ATION REOutST PHASC Yt 3 18 18 DH 1031FCLIJDING AUTHOR 12 A10N -

PHA$t PHAlt YES r REVIllON S A W . AUTHORilATION AUTHORI2Afl0N PROJECT 88ANAOCR & .

ADM NOOC 103 REQUIRC09 REQUIRED?

F '*

OEV PHASE AUTH PACMAGE NO No 1 r 1r ,. 1r PRolill ANAOC AIENT PRES (NTATION & DISPO$1 TON l

1P REVISC THE LONG RANGE PLAN

=-

0AP-025 Rev 4 Page 41 of 53

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

FIGURE 6 Page 1 of 1 Forced Outage Priority Re ady to Work List BRUNSWICK NUCdAR PLANT Pepe f fr w r UNTT2 FORCED OUTACE WORKLIST PRIORITY. READY'IT) ?'ORK Trombie Desedption Lococon Samese Neeport Crew CrwSa Der CR WRJO Unit Tag Number N'*D*f glect M 3W3 g g gg j Aasses syn 8'Pd in W uc9ene wCD nwP Nummer TROUBLE DESC: EDB* LOC:TB2 ELO21 NE Grt6A AFTER TB2 ELD 21 NE Of16A 15e0 33 227 2 8YY 96ADTI1 2 24dvD-vse STROICMG CLOSEi, ON A SHUTDOWN OF THE 25 SJAE 248VD-D 3080 RED XtD000lTT EL 3 NN l 1 l V56 FAILED TO OPEN WHEN TFE 28 SJAE WAS PLACED N HA:I toad. THe vAtvE AtsO Do uT OPEN WHEN THE wCAL gig CONTROL SWITCH WAS USED AT THE S.ME PANEL. THE BREAKE REPA!R NST: SUhMAARY: VALVE NfVD V58 FAILED TO OPEN AUTOMATICALLY, ANO FROed THE LOCAL CONTROL SWITOL !

VALVE HAG TO BE MANUALLY 37CKED OFF THE f1 fm SEAT.

TNEN fT OPERP TED P8tOPERLY ELECTPOpeMY THtS IS THE SECOND FMUJRE OF TMS TYPE FOR TMS VALVE.

TROUBLE DESC: LOCATM 2B RFP ROOM UNDER GRATING- 1540 XR ZS3 2 3YY 96AHNO1 2 2-WVD-T42 CLEA;4 TNE STRAMER ON TMS TRAP DUFUNG THE NEXT MN H 3000 DOWMPOWER. THE SAME STEAM TRAP STRAlpiER Ces THE 2A 2M0(M80 RED X3T00CTT ME 3 RFPT WAS FOUND CLOGGED WITH PIPE SCALE, MNDEResG gg PROPER TRAP OPERATKP(THE TR2 AM)TR 1 TRAPS WEM Q.EANED A REPA!R INST:

SUMMARY

OtSASSEnGLE TRAP, NSPECT. Q.EAN AND REASSEMBLE.

M94 PREWORK: NfA 2 2MTR2 TN.E DESC: LOCATN 29 RFP ROOM UNDER ORAT1NP 1540 XB 253 2 8YY 96AHND1 CLEAN THE STRA!NER ON TMS TRAP DUFUNG THE NEXT RED XED000tTT ME 3 NN H 3000 DOWC *N THE SAME STEAM TRAP STRADIER Oet THE 2A 29700614 RrPT WAC FOUND CLOGGED Wm4 PIPE SCALE, HpeERnG W1064 PROPER TRAP OPERATION.TE TR-2 ANDTR-1 TRAPS WEPE CLEANED A REPAIR INST: SUMMA,8 W: DISASSEMBLE TRAP. INSPECT, CLEAN n o RsAssEMets.

MS4 PREWORIC IWA ,

0AP-025 Rev.4 Page 42 of 5; t_ __ _ ____-

l 4

ATTACHMENT 1 Page 1 of 3 Twelve Week Rolling Schedule WEEK "A" WEEK"B" WEEK "C" WEEK "D" ECCS ECCS ECCS ECCS DG1/CS/SLC DG2/RHR *A* DG?/HPCl/SBGT DG4/RCIC PT 6.1 PT. 8.1.3A/B/C 2 PT. 9.2 PT 10.1.1 A,1 PT 10.1.1 PT 7.1.8 PT 8.1.4A, PT. 8 2 2C PT. 9.3A PT 12.20, PT 23.1.3 PT 12.2A PT 8.2.4, PT 12.28 PT 12.2C 1 PT-40.2.5 MST.CS210 2-PT 40 2.5, 2 PT 40.2.8 PT 15 6 1 PT 40.2.8 MST CS220 2-PT-40 2.9 1 MST HPCl26Q 1 PT 40.2.0 LNIT 1 DIV 1 MST RHR220 UNIT 2 DIV I 2 MST ADS 210 MST RHR2?Q 2 MST-RCIC270 -

UNIT 1 DIV 11 UNIT 2 OlV 11 High Safety Significant High Safety Significant High Safety Significant High Safety Significant Systems Systems Systems Systems 1005,1070,2010 1011,1080 2020,2095,2117 2055,2100,2190 2035 (NOTE: 1) 204:i (NOTE: 1) 4060 (2A NSW PUMP) 4060 (1 A CSW PUMP) 2040,2070,3050,4060 4060 (1C CSW PUMP) 5065 5095 (DG 4) 4060 (2C CSW PUMP) 5095,5100 (DG 2) 5095 (DG 3) 5100 (DG 4) 5010 $105,5110 (DG 2) 5100 (DG 3) 5105 (DG 4) 5095,5100,5105 (DG 1) 5111,5112 (DG 2) 5105 (DG 3) 5110 (DG 4) 5110,5111,5112 (DG 1) 5113 (DG 2) 5110 (DG 3) 5111 (DG 4) 5113 (DG 1) 5170 (NOTE:1) 5111 (DG 3) 5112 (DG 4) 5145 5175 01 DIV11 5112 (DG 3) 5113 (DG 4) 5175 U 1 DIV I $230 5113 (DG 3) 5135 5240 (1 A 1,1 A-2) 5240(18 1,18-2) 5175 U 2 DIVl 5175 U 2 DIV 11 6175,6235 6175 (MDFP) 5240 (2A-1,2A 2) 5240 (28-1,2B-2) 6240 9300 $245 6205 BOP BOP BOP BOP 3020,4010 3025,3070,4015,5040 1050,3030 1065,3040,4045 5035,5250,6060 5255,6070, 4040,5045,5259 5050,5185,5260 6160,7045,8055 7060,8065,8275 6075,6195,6245 6080,6180,6260 S185,8270 6281,7070 7075,8110,8290 7071 (NOTE: 1) 8580 8075,8280 NOTES:

1: Divisionalized within the week.

2: BOP, High Safety Significant and ECCS work may be performed during weeks other than shown provided a risk assessment in accordance with Attachment 4 determines risk to be acceDtable, 0AP-025 Rev, 4 Page 43 of 53

1 ATTACHMENT 1 Page 2 of 3 Twelve Weck Rolling Schedule WE E V, "E" WE EK "F" WEED "G" WEEK "H" ECCS ECCS EOCS ECCS DG1/CS 'A*/SLC DG2/RHR *B" DG3/HPCl/SBCT DG4/RCIC i PT 6.1 PT 8.1.3A/B/C 1 PT 9.2 PT 10,1.1A, PT 12.2D l PT. 7.1.8 PT 8.1.48 PT. 9.3A PT 23 T. PT 23.1.3 PT. 7.2 4A PT 8 2.28, P T. 8.2.4 PT 12.2C 2 PT 24.12 PT 12.2A PT 12.20 PT 15 6 MST RCIC210 UNIT 1 DIV 1 MST.RHR210 2- MST.HPCl260 MST RCIC220 MST-RHR240 UNIT 2 DIVI MST-RCIC230 MST RHR260 MST RCIC260 UNIT 1 OlV 11 UNIT 2 DIV 11 High Safety Significant Hig5 Safety Significant High Safety Significant High Safety Significant Systems Sy:tems Systems Systems 1005,1070,2010 1011,1080 2020,2095,2117 2055,2100,2190 2035 (NOTE: 1) 2045 (NOTE:1) 4060 (2A NSW PUMP) 40GO (20 NSW PUMP)

.J40,2070,3050,4060 4060 (18 NSW PUMP) 5065,5095,5100,5105 5095,5100, $105 (DG 4) 4060 (15 CSW PUMP) 5005,5100,5105 (DG 2) (DG 3) 5110,5111,5112 (DG 4) 5010 5110,5111,5112 (DG 2) 5110,5111,5112 (DG 3) 5113 (DG 4) 5095,5100,5105 (DG 1) 5113 (DG 2) 5113 (DG 3) 5135 5110,5111,5112 (DG 1) 5170 (f30TE:1) 5175 0 2 OlVl 5175 U 2 DIV ll 5113 (DG 1) 5175 U 1 DIV11 5240 (2A 1,2A 2) 5240(28 1,20 2) 5145, 5175 U 1 DIVl 5230,5240 (1B 1,18-2) 9300 5245 5240 (1 A 1,1 A 2) 6175 (MDFP) 6175,6235 6240 BOP BOP BOP BOP

~

5055,5265 3060,3070,4070, 4075 3076,5005 a 6085,6165, 5060,5200 5205,6005,6115 5070,5210,6010 020l,7095,- 6004 (includ>s SPDS) 6202,6270,6281 6125,6280 8185,3310 6095,6200,6265 7071 (NOTE: 1) 7110 7100,8195 7105,8005, 8220 8230,8370,8580 8275, 8355 NOTES:

1: Divisionalized within the week, 2: BOP, High Safety Significant and ECCS work may be performed during weeks other than shown provided a risk assessment in aCCordance with Attachment 4 oetermines risk to be acceptable, 0AP-025 Rev, 4 Page 44 of 53 k .

ATTACHMENT 1 Page 3 of 3 Twelve Week Rolling Schedule

~

WE E K "l" WEEK "J" WEEK "K" WEEK "L" ECCS ECCS ECCS ECCS DG1/ CS *B*/ SLC/ RWCU DG2/RHR DG3/ HPCl/ SBGT DG4/RCIC l PT. 6.1 PT. 8.1.3A/B/C PT. 4.1.1, PT. 9.3A PT 10.1.1 A PT. Y.1.5 PT. 8 2.4 PT 12.20, PT.15.6 2-PT.10.1.1 PT. 7.2.48 - PT 12.20 PT.15.7 PT.12.2D PT.12.2A MST RHR200 MST.HPCl210 PT 23.1.3 PT.14 6 MST RHR270 MST HPCl220 1 MST ADS 21Q 1 PT 24.11 MST.RHR280 MST.HPCl230 1 MST RCIC27Q UNIT 1 DIV 1 UNIT 1 DIV ll MST HPCl270 UNIT 2 DIV 11 l

l UNIT 2 OlV i

( High Safety Significant Hi-h Safety Significtat High Safety Signiricant High Safety Significant Systems Systems Systems Systems 1005,1070,2010 1011,1080 2020,2095,2117 2055,2100,2190 2035 (NOTE: 1) 2045 (NOTE:1) 4060 (2A CSW PUMP) 4060 (28 CSWPUMP) 2040,2070,3050,40GO 4060 (1C CSWPUMP) 5065 5095 (DG 4) 4060(1 A NSW pump) 5095,5100 (DG 2) 5095 (DG 3) 5100 (DG 4) 5010 5105,5110 (DG 2) 5100 (DG 3) 5105 (DG 4) 6095,5100, (DG 1) 5111,5112 (DG 2) 5105 (DG 3) 5110 (DG 4) 5105 5110 (DG 1) 5113 (DG 2) 5110 (DG 3) 511? (DG 4) 5111,5112 (DG 1) 5170 (NOTE:1) 5111 (DG 3) 6112 (DG 4) 5113 (DO ;),5145 5175 U 1 DlV 11 5112 (DG 3) 5113 (DG 4) 5175 01 DIVI $230 5113 (DG 3) 5135 5240 (1 A 1,1 A-2) 5240 (1B-1,18 2) 5175 U 2 DIVl $175 U 2 CtVll 6175,6235. 6175 (MDFP) 5240 (2A 1,2A 2) 5240 (2B 1,2B-2) 5245 6240 9300 6205 BOP BOP BOP BOP 3P77 2115,3070, 3080,5020 3100,5025,5085,6030 4005,5030 5075,5215,6015- 5080,5195,6020 6140,6220,6281,7005 6040,6152,6225 i 6130,6210,6281 6135,6216,6282 7071 (NOTE:1) 7015,8045,8260 8020,S185,8232, 8035,8240,8400 8040,8250 8500,8580 8340.8390 NOTES:

1: Divisionalized within the week.

2: BOP, High Safety Significant and ECCS work may be performed during weeks other than shown provided a risk assessment in aCCordance with Attachment 4 determines risk to be acceptable.

0AP-025 Rev,4 Page 45 of 53

4 ATTACHMENT 2 Page 1 of 2 Priority System Criteria Summary The Nuclear Generation Group Work Control Priority System is provided in ADM NGGC 0104. This attachment pr'vides guHance specific to the implementation of this system at Brunswick Nuclear Plant. The examples provided in this attachment take precedence over ADM-NGGC-0104,

~

PRIORITY BRUNSWICK CRITERIA

SUMMARY

BNP PRI #E Emergency (Work Immediately)

Definition: Those items that have ad immediate and direct impact on the health and l safety of the general public, pose a significant industrial hazard, or require l immediate attention to prevent the deterioration of plant conditions to a possible l unsafe or unstable level.

1 1

Examples: This classification includes work activities required to support mitigation of plant conditions defined in Tech. Spec 3.0.3, plant shutdowns required by Tech Spec 3.0.5, Emergency Operating Procedures, and at the discretion of the Shift Superintendent, emergency activities associated with Abnormal Operating Procedures.

Work Control Response: Begin work immediately and notify management, planning shall be performed in parallel with work activity. The activities that are accomplished shall be documented after the fact or when parallel paperwork development catches up with the work being performed. Activities should receive the same degree of review as if they were preplanned.

BNP PRI #1 Urgent (Plan and Work immediately)

Definition: Those items that have a near-term direct impact on the health and safety of the general oublic, the reliability of power generation, or industrial safety.

Examples: This classification includes: T/S LCOs 5 7 days, loss of plant capacity 3 50 MWe, or affects the ability of the plant to respond to emergency or accident conditions. Specific examples include:

T/S LCO of 5 7 days

- UAT/ SAT Overheating T/S Action Step requiring a power reduction Significant loss of public address (PA), secunty systems, or plant lighting Significant loss of fire protection capability Action of s 7 days per the requirements of OPLP-01.2, Fire Protection System Operability, Action, and Surveillance Requirements.

Work Control Response: Work authorized on a 24 hr/ day 7 day / week bas!S required to support plant reliability, capacity, or availability. These items will be blocked as Urgent and worked after expedited planning and authorization.

0AP-025 Rev. 4 Page 46 of 53

0 4

ATTACHMENT 2 Page 2 of 2 Priority System Criteria Summary BNP PRI #2 2mergent (Expedite Schedule)

Lefinition: Those items which have a reasonable possibility of affecting safe, economical, reliable, and envirorimentally sound plant operations.

Examples: Those work items judged to have a possible impact on safe, reliable, and environmentally sour.d plant operation including activ!!ies that affect SALP indicators, mils /kWh, and plant capacity of >.5 MWe. Specific exemples include:

i -

Maintenance Rule Ai System Corrective Actions l -

Loss of15 MWe (i e., CWIPs, FW HTR LVL CNTLS)

Surveillance test support work identified during testing LCO conditions > 7 days Personnel safety issues Action of > 7 da) s per the requirements of OPLP 01.2 and OPLP 01.5, Alternative Shutdown Capability Controls.

Release of CFCs from refrigeration units, excluding process chillers (Turbine Building chillers)

Work Control Response: Expedite schedule; plan and work as soon as possible.

Generally, work activities that cannot be delayed until the next schedulert work window. These items will be reviewed by Outages and Scheduling, implementing organization and Operations for schedule impact and either approved via Figure 3 for work stem addition or blocked for early completion.

I BNP.PRI #3 Routine (Plan and Schedule per 12 Week or Outage Schedule)

)

Definition: Those items wnich do not have a signihcant impact on safe, economic, ieliable, and environmentally sound plant operation.

Examp!es: Those items that are routine ac'.ivities which can be planned and scheduled in accordance with the normal work contiol process for developing the rolling on line schedule and outage schedule. Specific examples include:

- BOP equipment repair

- Items not causing active LCO conditions

- Chronic radiation exposuro Preventive and corrective maintenance to improve reliability

- Backlog reduction items

- ltems with Worx Condition Codes of D, E, or F

- Most major / minor modifications Work Control Response: Plan and schedule per the rolling on-line schedule or planned outage scope. Operations review of the schedule determines the work control process response of how rapidly ti,ek sms are worked. >

BNP PRI #4 Nonscheduled Definition: Work items which are not scheduled and not priority E or 1 3.

Examples: These items are either Minor Work, Operational Support, or Maintenance Support related activities that do not require the activity to be

-scheduled in order to work the activity.

Work Control Response: This work will not be scheduled; it will be worked as

fill-in" and controlled by the Work Group responsible for implementation.

0AP-025 Rev. 4 Page 47 of 53

, , )

ATTACHMENT 3 Page 1 of 1 On-line Schedule Manual Entry Form Assochted WR/JO # (If applicable) j Activity Description 1

i l

Unit Unit 1 Unit 2 _. Both l ___ _ !

Start Date & Time !

Crew Code Duration !

Shift D (Days) N (Nights) ,

A (Around the clock)

Clearance Yos No _

LCO Yes No _ ,_ When Worked _.

RWP Yes No ,_

i Scaffold Yes No _

System Contact Person &

extension Requested by: Approved by: _

Outages & Scheduling Representative OAP-025 Rev, 4 Page 48 of 53

O 1

ATTACHMENT 4 Page 1 of 3 Methodology for Assessing and Managing Plant Risk

i. Ma3ntenance will be scheduled in acccedance with Attachment 1, Twelve Week Rolling Schedule when pnssible.

2. On-line system outages, voluntary LCO entries, and ECCS work windows will integrate maintenance and testing activiti',s.

3. Risk impact of work activities which could affect the availability of those systems used to ensuia defense-in-depth for Technical Specification action statements or risk

, management will be evalaated. This includes surveillance tests that do not render i equipment inopsrable, but could result in a trip or other even'.

4. Risk impact of work activities thr' could initiate a plant transient if performed incorrectly will be evaluated. Maintenance Rule Scoping basis information may be used to identify potential transient initiators. Pre job briefs willinclude compensatory measures to guard the redundant train or system and contingency plans for anticipated failures.

S. Risk impact of work activities which could affect reactivity management will be evaluated. Pre-job briefs willinclude actions to monitor reactivity changes and mitigating operator actions.

C. System outages of more than one high t,afety significant system at a time shall be avoided unless determined acceptable by risk assessment.

7. Nuclear Service water pumps shall not be scheduled to be out of service unless all four EDGs are available.

i

8. On-line maintenance whLh requires entry into a voluntary LCO will be scheduled to NOT EXCEED one half the allowable LCO time, unless prior P! ant General Manager approvalis obtained.

9. Impact to the opposite Unit will be evaluated for common systems. OPLP-28 Attachment 11 may be used to identify common systems.

c 10. ALARA and industrial safety issues should be evaluated.

11. Work, such as visual inspections, which does not require a clearance or does not render equipment unablo to perform its functions should be scheduled in accordance with the 12 wc t % -) schedule to minimize the consequences associated with identification of requii .aaintenance. .

0AP-025 Rev. 4 Page 49 of 53 i

4 ATTACHMENT 4 Page 2 of 3 Methodology foi Assessing and Managing Plant Risk

12. Based upon probabilistic safety assessment (PSA) insights the dominant accidents types for BNP include station blackout, transients at high pressure, loss of decay heat removal, small break LOCA, and ATWS. Provided below are guidelines specific to the dominant accident type.

12.1 Station Blackout 12.1.1 Maintenance which has a high poten'.lal of challenging the ability to maintain off-site power to Class 1E systems, should not be scheduled concurrent with systern outages on Emergency Diesel Generators (EDG) or HPCI or RCIC.

12.1.2 Prior to starting a circulating water intake pump concurrent with l E-Bus or EDG work consider the effect on E-Bus voltage.

12.2 Plant Transients 12.2.1 Maintenance / testing which has a high potential to cause a plant j trip (high risk evolutions), in conjunction with system outages on Feedwater, CRD, HPCI or RCIC should be minimized.

12.2.2 Maintenance should be scheduled to prevent system outage overlap which would result in entry into Tech. Spec. 3.0.3 or 3.0.5.

12.3 Loss of Docay Heat Reinoval System outages of more than one of the following systems at a timo shoula be minimized:

2045 RHR t

4060 Service Water 5010 EHC 0AP 025 Rev. 4 Page 50 of 53 ,

ATTACHMENT 4 Page 3 of 3 Methodology for Assessing and Managing Plant Risk 12.4 Small Break LOCA Defense in depth for the small break LOCA scenario is provided by Technical Specification requirements.

12.5 ATWS System outages on systems needed to controllevel during an ATWS, such as HPCI, RCIC, CRD, RHR, and Condensate /Feedwater in conjunction with main'enance on SLC should be minimized.

13. Authorization for scheduled System Outages will be obtained in accordance with

, Section 5.6.3.

l

14. If needed, Equipment Out Of Service (EOOS) software and/or the PSA group may be consulted to ast.!st with determination of risk significance, t

AP 025 Rev. 4 Page 51 of 53

4 4

1 ATTACHMENT 5 Page 1 of 1 Guidance for System Outage Determinations System Description Guidance 1005 Nuclear Boiler System must be Operable as per Technical Specifications to maintain HSS function.

1011 PCIS Technical Specifications requirements must be met to maintain HSS function.

)

1070 CRD Removing one pump from service constitutes a system outage.

1080 RPS System must be. Operable as per Technical Specifications to maintain ,

HSS function 2045 RHR One pump per loop is required to maintain HSS function.

2045 RHR SW One pump per loop is required to maintain HSS function.

3050 Feedwater Both pumps are required to maintain HSS function.

4060 Service Water Removal of any two pumps per Unit from service constitutes a system outage.

5010 EHC Both pumps are required to maintain the HSS function. One cooler is required to maintain HSS function.

5135 230KV Switchyard System must be Operable as per Technical Specifications to maintain HSS function.

J 5145 SAT, UAT System must be Operable as per Technical Specifications to maintain HSS function.

5170 4KVAC System must bc Operable as per Technical Specifications to maintain HSS function.

f,175 480VAC 2-Busses are required to be Operable as per Technical Specifications to maintain HSS function.

. 5230 250VDC Both batteries are required to maim - 9 function.

i 5240 125VDC Both char 0ers are required to maintain H., _ action.

, CHARGERS 5245 125VDC BATTERY Both batteries are required to maintain HSS function.

6175 FPS FPS must be operable or compensatory measures in accordance with OPLP-01.2 must be. in place to maintain HSS function.

1 4

i s

4 OAP-025 Rev. 4 Page 52 of 53 er -

vww --- *r- uw e --em----Mem '- s-+.-m r--.-m ,.- et w i w- - . - + - .l-.errx- -r e -

w

e o

ATTACHMENT 6 Page 1 of 1 BNP LONG RANGE PLAN ACTIVITY IDENTIFICATION FORM ,

UNIT; SYSTEM #. FAIM NO.: ESR NO.: PROJECT TYPE:

O&M O CAPITALD PROJECT MANAGER. CUSTOME'r:

3,y,7,.g v PROJECT TITLE:

SCOPE DESCRIPTION CONTROLLABLE CO6TS (6000*$) BY COST TYPE Phase FAIM # Year 1: _ Year 2. _ Year 3 _ Year 4 _ Year S. _ TOTAL Study Design implement Totals PROJECT ATTRIBUTES CATEGORY: Regulatory Requirement O Economic Benefd O Management Discretion O Benefit Cost Ratio (Hard Dollarst B/E: Net Present Value (5000's) (Hard Dollars):

SCHEDULE STUDY DESIGN IMPLEMENT is Unit Outage Required?

Start Start. Start. YES O Complete: Complete. Complete: NO O APPROVALS O Project Manager IMPACTED SECTION MANAGERS-.

O Customer OBESS O Indiating Secten Manager O MAINTENANCE OOTHER 0AP-025 Rev. 4 Page 53 of 53

- _ .

ML20197A937

Contents

Text

SUMMARY

2.0 REFERENCES

2.0 REFERENCES

Title:

SUMMARY

SUMMARY

Navigation menu

ML20197A937

Text

SUMMARY

2.0 REFERENCES

2.0 REFERENCES

Title:

SUMMARY

SUMMARY

Navigation menu

Search