ML20199J571
| ML20199J571 | |
| Person / Time | |
|---|---|
| Site: | Brunswick  |
| Issue date: | 11/14/1997 |
| From: | CAROLINA POWER & LIGHT CO. |
| To: | |
| Shared Package | |
| ML20199J485 | List: |
| References | |
| 0AP-025, AP-25, NUDOCS 9802050346 | |
| Download: ML20199J571 (47) | |
Text
CP&L CAROLINA POWER & LIG'iT COMPANY information ammme - mens BRUNSWICK NUCLEAR PLANT use
)
PLANT OPERATING MANUAL i
VOLUMEI BOO",1 ADMINISTRATIVE PROCEDURE www UNIT t40V 141997 0
cog [EUpttuim eit Pg. OLLET) ll Il!I I:ll illllli!IllliI:lll!!Ill Ill 0AP-025 BNP INTEGRATED SCHEDULING REVISION 3 l
EFFECTIVE DATE II/If/99 Sponsor j,.d%u h --
// / t/ t2 Su
' ende, On. - Scheduling Date'
'/
//
I_/_
Concurrence
. _ _. _ tar <
ut es and S < duling Da[
M, lager -
Approval uego
&a l I - 1 3 '7 7 Director - Site Operations Date h0R DO K O O 324 p
PDR 0AP-025 Rev. 3 Page 1 of 56
1 l
REVISION
SUMMARY
Revision 3 of this procedure incorporates the following changes:
i FIGUREl 1
Designates approval authority for Figures 3 and 4 to the Operations Shift Superintendent on weekends, holidays, and backshifts.
Clarifies responsibilities associated with concurrence and approval signature of 4
Figure 3 (Step 5.2.1.12).
Extends the time that manual entries can be added to the schedule without a Figure 3 from Wednesday of week T 3 to Tuesday of week T 2.
Revises the format of Figure 3, Schedule Change Approval Form.
SAFETY SIGNIFICANCE Clarifies the definitions for low and high safety significant systems.
Adds system 2070, CAC, to the list of high safety significant systems identified on
-, and adds 2070 to weeks A and E of Attachment 1, Twelve Week Rolling Schedule.
- Clarifies that, if needed, Equipment Out of Service (EOOS) software and/or PSA group may be consulted to assist in determination of risk significance of emergent failures / changing plant conditions.
-- D 'letes the Approyal Matrix for concurrent On-Line System Outages (formerly Anachment 2) by incorporating this information into Suviion 5.6.3.
Revises the high safety significant function for tho Fire Protection System (Attachment 3) to reflect that diesel driven fire pump low pressure injection is only significant during Unit Shutdown conditions and adds that fire protection in the DG, RX, SW and Control buildings is high safety significant.
- Revises the high safety significant function for RB HVAC (Attachment 3) to ide.tify that room cooling is not high safety significant.
OAP-025 Rev.3 Page 2 of 56 i
-,,-,-,,.,r,-,.
,--..-,---,,,n,,,,,,--.---
m,,
REVISION
SUMMARY
LONG RANGE PLAN
- Adds steps to the Responsibilities section for Plant Work Units to include identifying activities to be incorporated into the LRP and reviewing / updating the LRP.
Changes titles from *LRP Responsible Manager" to ' Project Manager" to align with ADM NGGC 0102.
- includes cost breakdown requirements for the Long Range Plan.
- Revist.s Figure 5, Long Range Plan Process Overview.
- Revises Section 5.7, Long Range Planning, to emphasize applicability of ADM NGGC 0102.
&DMINISTRATIVE
- Replaces reference NGGM 305-05, Nuclear Generation Group Work Control Priority System with reference ADM NGGC 0104.
- Adds reference Application of Probabilistic Safety Assessment to Maintenance Rule Irnplementation, Brunswick Nuclear Plant
- Adds reference OPLP-01.2, Fire Protection System Operabihty, Action, and Surveillance Requirements.
- Deletes definition and reference to forced outage candidate list.
- Changes title from Superintendent, Outa e Management to Superintendent, w
Outages.
- Other miscellaneous administrative changes.
LIST OF EFFECTIVE PAGES Pages Revision 1-56 3
0AP-025 Rev.3 Page 3 of 56
l l
TABLE OF CONTENTS SECTION PAGE 1.0 PURPOSE............................................................................................................7 1.1 Purpose..........................................................................................................7 1.2.
Objective........................................................................................................7-1.3 Scope............................................................................................................7
2.0 REFERENCES
.......................................................................................................7 3.0-DEFlNITlONS.........................................................................................................8
-3.1 E xtended Wor k List (Forced Outage)............................................................. 8 3.2 Fragnet;.........................................................................................................B L
3,3 H ig h Sa fety S ig nifica nt S yste m....................................................................... 8 3.4 Lo ng R a ng e Pla n (L R P)...........................................................................,...... B 3.5 Low S a fety S ig nifica nt S ystem...................................................................... 8 3.0 ManualEntries...............................................................................................8 3.7
_ P a c k a g e R e a d y.............................................................................................. 8 3.8 P rio rit y Wo r k L i s t.......................................................................................... 9 3.9 S yste m C o nd itio n S t ate me nt....................................................................... 9 -
3.10 SystemOutage...,..........................................................................................9 3.11 TaskReady...................................................................................................9 3.12 Wo rk Li s t A cliv it ie s i................................................................ a...............
4.0 R E S P O N S t B I L IT I E Sa..............................................................................
4.1 Forced O ut a g e C oo rd in a to r......................................,.................................. 9 4.2 -
Implementor................................................................................................10
~ 4.3 O u t a g e s a nd S ch ed uling....................................................................10 4.4 P i a n t E n g i n e e r............................................................,................... 1 1 4.5 Pla nt Work U nits..........,..............
...........................12
- 4.6 Project Managor (Long Range Plan),........
.........................12 4.7 -
Project Manager (System Outages and Downpowers)............................13 4.8 Work Group Schedule Coordinator....
.13
- 4.9 Work Week Manager...........
.......14 0AP 025_
Rev.3 Page 4 of 56 P.ur
TABLE OF CONTENTS SECTION PAGE 5.0 1NSTRUCTlONS..................................................................................................15 5.1 Initial Scheduling of On line Activities.........................................................15 5.2 On line Sched ute Development...................................................................15 5.2.1 On.line Schedule Development Cycle..............................................15 5.2.2 Stage 1 System Outages and Unit Downpowers.............................19 5.2.3 Stage ll Final Work List (Week T 4)................................................ 20
)
5.2.4 Stage 111 - Preliminary Work Schedule (Week T 3)............................ 20 5.2.5 Stage IV - Final Work Schedule (Week T 2)...................................... 22 5.2.6 Stage V Schedule Review (Week T-1)............................................ 23 5.2.7 S t a g e VI Wo r k We e k (Wee k T-0)................................................... 2 3 5.3 Authorizath of Non Scheduled Priority 1, 2, or 3 Work............................... 24 5.4 Post Wo r k C ritiq u e s.................................................................................. 2 6 5.5 Schedule Development of Outage Activities............................................... 26 5.6 On line System Outages And Voluntary LCO Entry.................................. 27 5.6.1 System Outage & LCO General Guidance........................................ 27 5.6.2 System O utag e Pre Pla nning........................................................ 2 8 5.6.3 System Outag e Authorization........................................................... 2 8 5.6.4 Emergent Failures / Changing Plant Conditions.................................. 30 t
5.7 Long R a ng e Pla n nin g................................................................................ 3 2 5.7.1 L o n g R a ng e Pla n Scope............................................................... 3 2 5.7.2-Identification Of Activities To Be included in the LRP.......................,33 5.7.3 LR P / B usiness Pla n interf a ce.................................................. 34 5.7.4 Publication of the Long Range Plan....................................... 34 5.8 Forced Outage Scheduling..........
........ 34 5.8.1 Forced Outage Schedule Compositiort............
.................34 5.8.2 Forced Outage Schedule Preparation and Review..
............36 5.8.3 Forced Outage Schedule Approvaland Distribution....
.........37
'5.8.4 Forced Outage Schedule Revision.
........38 5.8.5 Forced Outage Schedule implementation..
.38 OAP-025 Rev.3 Page 5 of 56
- -.~.
l TABLE OF CONTENTS SECTION PAGE FIGURES 1
On line Schedule Development: Routine Deliverables......................................
39 2
On line Schedule Development: System Outage Deliverables......................... 40 3
S ched u te C h a ng e App rova l Fo rm.................................................................... 41 l
4 Risk Assessment of Schedule Changes / Emergent Activities............................
42 5
Long Ra nge Pla n ning Process Ove rview.......................................................... 43 6
Forced Outage Priority Ready To Work List.................................................. 44 ATTACHMENTS 1
Twe Ive Wee k Rolling Sch ed u te.................................................................., 45 2
Priority System C riteria S u mma ry................................................................
4 8 _
3 Hig h S a fe ty Sig nifica nt F u n ctio n s.................................................................. 50 1
4 Methodology For Assessing and Managing Plant Risk................................... 52 5
On Line Sched ule Ma n ual Entry Form............................................................. 55 6
BNP Long Range Plan Activity Identification Form......................................... 56 0AP-025 -
Rev.3 Page 6 of 56 i
I
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 safety regulations, Technical Specifications, Code requirements, and guidelines so that thc plant is maintained in a safe, reliable, economic, and environmentally sound manner.
1.3 Scope This procedure provides the administrative controls necessary to implement the scheduling functions identified in ADM NGGC 0104, Work Management Process.
2.0 REFERENCES
2,1 ADM NGGC-0101, Maintenance Rule Program 2.2 ADM-NGGC-0102, Project Review and Authorizat'v i 2.3 ADM NGGC-0103, Project Management 2.4 ADM NGGC-0104, Work Management Process 2,5 Application of Probabilistic Safety Assessment to Maintenance Rule Implementation, Brunswick Nuclear Plant 2.6 BSP-35, Outage Planning 2.7 0AP-022, BNP Outage Risk Management 2.8.
OPLP-01.2, Fire Piotection System Operability, Action, and Surveillance Requirements 2.9 OPLP-28, Startup And Power Ascension Management Plan For Unit Startup Following An Outage l
OAP-025 Rev.3 Page 7 of 56 l
~
3.0 DEFINITIONS 3.1 Extended Work List (Forced Outage)
A list of work activities 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 A detailed schedule of related work activities which includes logic relationships between the activities.
3.3 High Safety Significant System Those systems that nre significant contributors to safety based on their 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 Expert 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 Significant System Those systems that are noj significant contributors to safety based on their 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 Expert Panel.
3.6 Manual 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 activity from being implemented.
0AP-025 Rev.3 Page 8 of 56
.m
.-+ - -.
-,,s.
=, - -
+
e, - -,,
m-
3.0 DEFINITIONS 3.8 Priority Work List (Forced Outage)
A list of work activities identified by plant Operations as priority work which either requires Unit outage to work or should be worked 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 performed during a forced outage. The "Not Ready to Worr Tst should be utilized during non outage periods to identify those priorityitems that should be mado " Task ready" to support forced outage accomplishment.
3.9 System Condition Statement Conditions identified as " System Reliability" or ' System Economic Alert" 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.
3.10 System 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, 4.0 RESPONSIBILITIF.S 4.1 Forced Outage Coordinator The Forced Outage Coordinatoris responsible for:
4.1.1 Assembling recover / plan and schedule review comments and coordinating the resolution of those comments.
0AP-025 Pev.3 Page 9 of 56
_ _. _ _ ~ _ _
4.1 Forced Outage Coordinator 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 j
significantly enhance implementation.
4.1.7 Maintaining an " Extended Work List"which may be issued for management review if an extended forced outage should occur.
l 4.1,8 Updating schedule progress during periods of implementationto
' include analysis of the critical path recovery plan.
4.2 Implementor i-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,
- 4.3 Outages and Scheduling Outages and Scheduling is responsible for:
d 4.3.1 Developing, maintaining, and publishing worklist and schedules for the work activities governed by this procedure, including the following:
r Weekly Schedules On-line Schedule (Twelve Week Rolling Schedule)
Planned Outage Schedules and Forced Outage Fragnets System Schedules (as needed)
Long Range Plan 0AP 025 Rev.3 Page 10 of 56
4.3 Outages and Scheduling 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 management process.
4.3.5 Performing risk assessment of the schedule in accordance with 4.4 Plant Engineer The Plant Engineer is responsible for performing reviews of overall system material condition, including open items, and providi recommendations for work schedule and scope to ensure proper system performance. Thit, 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 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 syste n unavailability for maintenance rule in scope systems.
4.4.7 Participating in the development of a post system outage critique as i
requested by Outages and Scheduling Section.
1 4.4.8 Reviewing the Long Range Plan and providing recommendations on scheduled activities for future years.
0AP-025 Rev.3 Page 11 of 56
~
4.5 Plant Work 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 Coordinator of any changes to the " Ready to Work" list.
4.5.3 Reviewing and recommending items for addition to or deletion from the forced cutags " Priority"and " Extended" Work Lists.
4.5.4 Reviewing and approving the Forced Outage Schedule.
4.5.5 Notifying the Forced Outage Coordinator of changes to the schedule or the " Priority Ready To Work" list.
4.5.6 ldentifying activities to be incorporated into the Long Range Plan..
4.5.7 Reviewing the Long Range Plan and providing updates for assigned activities.
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.
0AP-025 Rev.3 Page 12 of 56
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 activities, such as unit downpowers and on line system outages. Typical tasks include:
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, i
4.7.4 Reviewing progress with Superintendent, On line Scheduling as requested.
l 4.7.5 Processing scope changes after scope is frozen utilizing Figure 3.
4.7.6 Ensuring radiation dose budget is identified and communicated to the site.
4.7.7 Briefing applicable 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.
4.8.2 Reviewing the schedule and worklist prior to the meeting, identifying and communicating conflicts, concerns and comments 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.
0AP-025 Rev.3 Page 13 of 56
4.8 Work Group Schedule Coordinator 4.8.4 Obtaining approval for items remaining on the schedule which are not
- package ready" or " task ready" 4.8.5 Assisting la reviews of system or component backlogs and emergent work to incorporate work activities into the t.ppropriate 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 unavailability of high safety significant systems through 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 Wesk Manager The Work Week Manager is responsible for:
4.9.1 Functioning as the Operations Work Group Coordinator.
4.9.2 Monitoring and expediting the preparation and implementation of the schedule, including system outages, plant evolutions, and individual work activities.
4.9.3 Review and resolution of Technical Specification compliance issues related to the schedule.
4,9.4 Obtaining approval for Operations items remaining on the schedule which are not " package ready" or " task ready".
4.9.5 Performing risk assessment of the schedule in accordance with.
4.9.6 Approval of the Weekly Schedule.
4.9./
Ensuring work is accomplished as scheduled.
0AP-025 Rev.3 Page 14 of 56
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 forced cutages.
The basis for the schedule for the operating cycle is the Twelve Week -
Rolling Schedule identified in Attachment 1 This rolling schedule is comprised of recurring " windows of opportunity" for implementing work on plant systems. The system windows are aligned to minimize the risk of challenging the unit (s)
~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 schcdule 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 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:
Figurr t 1 and 2 provide an overview of the deliverables contained in the steps below.
5.2.1 On line Schedule Development Cycle 1.
Outages and Scheduling will produce the work lists and schedules and coordinate the meetings identified below.
0AP-025 -
Rev.3 Page 15 of 56
5.2.1 On Line Schedule Development Cycle 2.
Outages and Scheduling may 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.
l S.
Post work tests required to support system operability will be l
coordinated by Operations and are not normally scheduled.
6.
During the development cycle On lir's Scheduling will monitor work window scope, development of work window and system outage schedules, and the completion of prerequisites including:
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, L
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 activities". Work List activities are authorized to be worked at any time during the scheduled work week.
0AP-025 Rev.3 Page 16 of 56
i 6.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.
I a.
System Outages on High Safety Significant systems.
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 system.
Activities which result in a Technical Specification system being hoperable.
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 !,nsient should be scheduled during the later part of the rnorning (starting at 1000 hours0.0116 days <br />0.278 hours <br />0.00165 weeks <br />3.805e-4 months <br />) or as coordinated with the System Dispatcher.
b.
During June, July, and August, evolutions which have the potential to initiate a plant transient shou!d be scheduled during the early part of the day (completed prior to 1300 hours0.015 days <br />0.361 hours <br />0.00215 weeks <br />4.9465e-4 months <br />) or as coordinated with the System Dispatcher.
11.
Manual entries to the online schedule will be requested and approved in accordance with Attachment 5, On line Schedule Manual Entry Form. Figure 3 will also be required for approval following the schedule development meeting on Tuesday of Week T-2.
0AP-025 Rev.3 Page 17 of 56
5.2.1 On Line Schedule Development Cycle -
-12.
Changes to the schedule will be requested and approved via Figure 3 as directed throughout Section 5.2. Signatures on the Figure 3 reptosent the following:
a.
The implementing Superintendent's signature represents concurrence that:
Resources are available to implement the activity as requested.
Actions required by others are accurately identified on the Figure 3.
Assessment of how the work scope will affect the component / system, if identified in the risk assessment, is accurate.
b.
The Engineering Superir tendent's signature represents concurrence that:
Engineering products, if applicable, are available to support the requested schedule.
Engineering resources,if required, are available to support the requested schedule.
The assessment of risk is accurate.
The requested change is consistent with system goals and/or perfonnance criteria, c.
The Operations Superintendent's signature represents concurrence that:
The assessment of risk is accurate.
Operations resources, if required, are available to support the requested schedule.
0AP 025 Rev:3 Page 18 of 56
5.2.1 On Line Schedule Development Cycle d.
E&RC Programs Superintendent's signature represente concurrence that:
E&RC support, if required, is available to support the requested schedule.
Impact of the change on ALARA goals has been evaluated and communicated to Supt. On Line Scheduling, e.
The On Line Scheduling Superintendent's signature represents concurrence that:
The assessment of risk is accurate.
The required concurrence signatures have been obtained.
Schedule development and authorization requirements identified in 0AP 025 have been achieved.
l 5.2.2 Stage 1 System Outages and Unit Downpowers 1
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 WeekT-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 Erigineer and Work Week Manager.
5.
06tages and Scheduling will normally issue a preliminary system outage schedule (fragnet) on Wednesday of Week T-5 for scheduled system outages.
0AP-025 Rev.3 Page 19 of 56 j
l 5.2.3 Stage ll. Final Work List (Week T-4) 1.
The Final Work List will be developed by incorporating PMs pts, MSTs, Models, Action Requests and WR/JOs.
2.
The Final Work List will normally be issued on Monday of Week T-4.
3.
The Final Work List will normally be reviewed on Thursday of Week i
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.
5.2.4 Stage lll Preliminary Work Schedule (Week T-3) l NOTE:
The Preliminary Work Schedule places the Final Work List in schedule format.
1.
The Preliminary Work Schedule will include WR/JOs with work status codes 02 through 20, Action Requests, and *rr.anual 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 normally be reviewed on Wednesday of Week T-3.
5.
The review of the Preliminary Work Sct.eduW on Wednesday of Week T 3 results in the " Scope Freeze" of the Work Schedule, including the system outage scope.
0AP-025 Rev.3 Page 20 of 56
5.2.4 Stage lli Preliminary Work Schedule (Week T 3) l 6.
To add a work activity to the schedule after the Wednesday review meeting the requestor will:
a.
Obtain concurrence via Figure 3, Schedule Change Approval Form.
b.
Deliver the Figure 3 and Figure 4 if applicable, to the Daily Schedule Review Meeting for review when feasible.
c.
Obtain approval from the Superintendent, On line Scheduling, or designee, via Figure 3, Schedule Change Approval Form.
7.
On line Scheduling will:
a.
Input the schedule change approved via Figure 3.
b.
Enter the reason for change (for schedule deletions) in the AMMS Scheduling Comments field.
c.
Enter the risk assessment informat on from Figure 4 in the AMMS Scheduling Comments field,if applicable.
8.
Schedulod work packages should be planned and reviewed by Wednesday of Week T 3. Packages not planned will be discussed at the schedule review meeting.
9.
The Superintendent On line Scheduling may assign action items to the work group schedule coordinators to provide clarification or
'xplanation of restraints and may request anticipated resolution dates 3 identified.
0AP 025 Rev.3 Page 21 of 56
5.2.5 Stage IV Final Work Schedule (Week T 2) 1.
Clearar ser thould be prepared for the scheduled activities by Sunda' >f Week T-2 at 24:00 houre.
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, 4.
The Fin?! Work Schedule will normally be approved by management on ThurMay 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 implementing Superintendent or above and the Work Week Manager via Figure 3, Schedule Change Approval Form.
7.
If a WR/JO is removed from the schedule because it is not task ready, On line Scheduling should enter appropriate comments in the AMMS Scheduling Comments field.
8.
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.
9.
Following issuance of the Final Work Schedule and prior to implementation of the schedule (Week T 0) a final risk assessment of the schedule will be performed by the Work Week Manager and On-line Scheduling using the methodology described in Attachment 4.
10.
Following the schedule development meeting on Tuesday of Week T 2, manual entries to the schedule will be requested and approved via Attachment 5 and Figure 3.
d 0AP-025 Rev.3 Page 22 of 56
5.2.6 Stage V - Schedule Review (Week T 1) 1.
The Final System Outage E:hedule 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.
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 adherence.
3.
Addition of carryover items for the subsequent week will be requested 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 AMh.
0AP-025 Rev.3 Page 23 of 56
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 nat 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 outages, the followinn shall take place:
On Line Work Activities 5.3.1 For on-line work activities the requesting unit representative will:
1.
Contact the Work Week Manager for preliminary review of impact to the schedule.
2.
Obtsin concurrence in accordance with Figure 3.
NOTE:
The Superintendent, On line Scheduling or his designee will determine which concurrence signatures are required and "N/A" those which are not.
3.
Obtain determination if the change impacts plant risk as described in and if so obtain a risk assessment via Figure 4.
4.
Deliver the work package attached to Figure 3, and Figure 4 if applicable, to the Daily Schedule Review Meetings for approval, when feasible.
5.
Obtain approval from the Superintendent, On-line Scheduling, or designee, via Figure 3, Schedule Change Approval Form.
NOTE:
The Operations Shift Superintendent may approve Figures 3 and 4 on weekends, holidays, or backshifts. Operations will then deliver the original Figures 3 and 4 to Online Scheduling.
6.
Return the dispositioned Work Package to the implementing organization.
0AP-025 Rev.3 Page 24 of 56
5.3 Authorization of Non 3cheduled Priority 1,2, or 3 Work 5.3.2 The 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.
5.3.4 For on line work the Discipline Schedulers will enter the risk assessments information from Figure 4 in the AMMS scheduling comments field,if applicable.
Outage Work Activities 5.3.5 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.
l 2.
The SOM will evaluate outage scope addition / change requirements in l
accordance with BSP-35.
3.
The SOM will annotate approval directly on the outage work package rather than using a Figure 3.
4.
The re uesting unit will return the outage work package to the impleinenting unit.
5.
~ he implementing unit will obtain WCC authorization for the outage
. rk package.
t 9
OAP-025 Rev.3 Page 25 of 56
5.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 -
4 Scheduler name Comparison of scheduled versus actual Work Window start and i
finieh dates and time.
Comparison of scheduled versus actual system unavailability time.
- Comparison of scheduled versus actual LCO time.
Original scope description.
Identification of scope changes.
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 BSP-35; Outage Planning.
5.5.2 The process for work scope control and scheduling for forced Unit outages is described in Section 5.8.
1 0AP-025 Rev.3 Page 26 of 56
5.6 On-line System Outages And Voluntary LCO Entry Planning or scheduling of on-line system outages on high safety significant systems or LCO entries during plant operations shall be performed in accordance with the following guidelines. This guidance is applicable to on-line operation including operation during ne" outage power ascension from Mode 2 through 100% stable power op".rm.s is.
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.
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 shutdown / decay heat removal systems or components.
3.
LCOs should not be entered if the work will not be completed prior to a planned reactor mode change.
4.
The total out-of service time for Technical Specifications required l
equipment and high safety signitrant systems or components should be minimized in order to balance systw availability and reliability.
5.
The following Figures and Attachments provide additionalinformation associated with the instructions below:
Figure 2, On-line Schedule Development: System Outage Deliverables
-, Twelve Week Rolling Schedule
-, High Safety Significant Functions
-, Methodology for Assessing and Managing Plant Risk OAP 025 Rev.3 Page 27 of 56
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 train %g 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 <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> per day basis and have a Project Manager assigned unless prior Superintendent, On-line Scheduling approval is obtained.
4.
Contingency plans and compensatory measures will be developed as deemed appropriate by the Project Manager. The Project Manager 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:
l 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, i
T 0AP-025 Rev.3 Pag of56
5.6.')
System Outage Authorization 2.
Work Week Manager and Superintendent, On-Line Scheduling approval is required prior to scheauling:
System outages.
Combinations of system outages.
More than two maintenance rule systems to be unavailable concurrently.
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.
EXAMFt.E:
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 system outage entry in accordance with these guidelines.
0AP-025 Rev. 3 Page 29 of 56
5.6.4.
Emergent Failures / Changing Plant Conditions 1.
If an emergent component failure occurs or plant conditions change, the Shift Superintendent shall determine if the failure or change in plant conditions impacts plant risk by using the methodology ider tified in Attachment 4.
2.
To manage the risk impact of emergent failures or changing plant conditions 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.
I d.
Minimize routine maintenance on the system during repair activities.
e.
Be aware of the risk significance of the emergent failure or 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.
f.
Delay scheduled system outages which have not started until plant conditions are favorable or until a risk assessment determines that beginning the system outage is acceptable, g.
Determine whether implementation of contingency plans or compensatory measures are warcanted for plant configuration to ensure that back-up systems are available and functional.
3.
When notifiea by the Unit SCO that a System Reliability or System Economics Alert has been issued by tlie 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.
0AP-025 Rev.3 Page 30 of 56 Jh h
5.6.4 Emergent Failures / Changing Plant Conditions b.
Identify those activities that may constitute a high risk evolution or condition. The foiiowing is a list of MSTs that have been identified as high risk evolutions:
Half Scram MSTs RPS270, 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.
1 d.
Perfonn 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.
e.
Perform necessary actions for a System Economic Alert including:
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.
0AP-025 Rev.3 Page 31 of 56
5.6.4 -
Emergent Failures / Changing Plant Conditions 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.
f.
Notify the Implementing Organization's Superintendent or scheduling 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.
5.7 Long Range Planning ADM-NGGC-0102 provides instructions and requirements 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 Plan Scope The BNP Long Range Plan (LRP) identifies the major activities proposed to be implemented through the end oflicensed 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 NP,C or INPO Assessments and Evaluations Corrective Maintenance Preventive Maintenance with a frequency greater than every refueling cycle r
10AP-025 Rev.3 Page 32 of 56 1.
5.7.2 Identification Of Activities To Be included in The LRP 1.
Addition of activities to the LRP should be proposed via Attachment 6, BNP Long Range Plan Activity identification Form, or via ADM-NGGC-0102 Form 1, Phased Project Authorization Form.
2.
The Outages and Scheduling (O&S) LRP Coordinator may add activities to the LRP without use of Attachment 6.
3.
" ~ESY analysis has not been performed the benefit to cost ratio and net present value may be omitted.
4.
The cost estir, ate should be identified by the following cost types:
Materials (GSM)
Contract services (LNC)
Company labor (GSL)
Other (GSO) 5.
Approval signature by Sponsor /lnitiator's Section Manager and by Section Managers impacted by the project (minor support involvement excluded)is required.
6.
The approved Attachment 6 should be submitted to the Outages &
Scheduling (O&S) LRP Coordinator.
I l
7.
I' 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 nurnber,if applicable 8.
The O&S LRP Coordinatorwill maintain a list of proposed additions and periodically obtain management review and approval.
9.
The O&S LRP Coordinatorwill update the LRP accordingly.
0AP-025 Rev.3 Page 33 of 56
5.7.3 LRP / Business Plan Interface Updates and publications of the LRP will be integrated with the l
Business Planning Calendar.
5.7.4 Publication of the Long Range Plan 1.
The LRP should be dynamically maintained throughout the year and periodically reviewed by the PRG.
2.
The LRP will be formally reviewed by toe PRG and approved by the Site Vice President twice a year as identified in ADM-NGGC-0102, 5.8 Forced Outage Schedulir g The following identifies the process to ' s :lsed for the preparation, review, a
approval, distribution,and revision of the BNP Forced Outage Schedule (s).
5.8.1 Forced Outage Schedule Composition I
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 Work List which are not task ready should receive attention during non-outage periods to be made
Task-ready" to support forced outage accomplishment.
0AP-025 Rev.3 Page 34 of 56 T
5.8.1 Forced Outage Schedule Composition 3.
The Schedule " Priority Ready to Work" list should consist of priority items identified by Operations which possesa the following attributes:
a.
Those packages identified by AMMS with a 1540 (Implementor l
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 satisfied 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 <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> should be excluded, unless approved by Management.
d.
The plant mode required for implementation should be 3 or 4.
e.
Work requiring vendor support or off site expertise which cannot be mobilized within 12 houis should be excluded, f.
Work which affects the corresponding operating unit should be 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 formatted to depict the following outage scenarios:
a.
Mode 3 Outege (3 day schedule).
b.
Mode 4 outage with no drywell entry (5 day schedule).
c.
Mode 4 outage with drywell entry (7 day schedule).
0AP-025 Rev.3 Page 35 of 56
5.8.1 Forced Outage Schedule Composition 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 t
outage),
b.
Previouslyidentified 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 current prior to leaving the applicable mode.
e.
Shutdown and startup sequences.
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.
The Forced Outage Coordinatorwill:
a.
Conduct forced outage planning /reviewmeetings as necessary to maintain current forced outage schedules.
b.
Ensure ( omments are incorporated into the schedule and the
" Priority i'eady to Work" list.
c.
Produce a schedule that conforms to Step 5.8.1.5 and the v
" Priority Ready to Work"lict.
0AP-025 Rev.3 Page 36 of 56 9
5.8.2 Forced Outage Schedule Preparation and Review d.
The " Priority Ready to Work " list should contain the attributes shown in Figure 6.
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.
5.8.3 Forced Outage Schedule Approval and Distribution 1.
The Superintendent, Outages will:
a.
Ensure that the Forced Outage Schedules are reviewed with the appropriatemanagers prior to issuing the schedules. Emphasis will be on changes since the previous schedule was issued.
b.
Issue the approved schedule on the first Monday of each month for Unit 2 and the third Monday of each month for Unit 1. The schedule will be issued electronically or manually to :
Plant GeneralManager Work Control Center Work Week Managers NRC Site Representative SuperintendentOn-line Scheduling Operations Manager Operations Shift Superintendent l&C and MechanicalSuperintendents Engineering Manager Maintenance Manager E&RC Manager Outage and Scheduling Manager 0AP-025 Rev.3 Page 37 of 56
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 numerical designator for the appropriate month (i.e.,97-5 for May).
c.
If issued manually include a cover letter identifying and explaining the changes from the previous Forced Outage 5.8.5 Forced Outage Schedule implementation 1.
The On-line Scheduling unit representativeon the Scram Incident inves N Team (Silt) Roster or the Operations Shift i
Supe
+ 'eut should call the Superintendent,on line Scheduling and the Supwnnendent, Outage Managementto notify them that the unit is in a forced outage, 2.
Upon notification of the forced outage, the Superintendent,on-line Schedu!!ng or the Superintendent, Outage Management should call the Unit Lead Scheduler, Forced Outage Coordinator, and the Discipline Scheduler and provide them with the direction required to effect unit recovery and startup.
3.
The Unit Lead Scheduler should develop a Recovery Plan that corrects the condition that placed the unit in a forced outage.
4 The Forced Outage Coordinator should coordinate the integration of items from the " Priority Ready To Work" list, with the appropriate -
Forced Outage Schedule, the Critical Path Recovery Plan, and activities from the On-line Weekly Schedule required to support startup into the Integrated Forced Outage Schedule.
4 0AP-025 Rev.3 Page 38 of 56
i FIGURE 1 Pageiof1
.On-line Schedule Development: Routine Deliverables i
WEEKS T-7/T-5 WEEK T-4 WEEK T-3 WEEK T-2 WEEK T-1 WEEK T-0 Monday; Monday:
' Sunday:
Final Risk Assessment completM l
Clearances prepared 1
Issue Final issue Preliminary Schedule Work List Work Schedule Monday:
mplementaten issue FinalWork Schedule Daily Schedule Review Meetings Tuesday:
Final Schedule Wednesday:
Review meeting Revised Weekly Preliminary WR/JOs Task Ready Schedule Schedule Review (restraints removed)
Issued as needed meeting or Figure 3 approved to WR/JO planning &
remain on the schedule reviews complete Wednesday:
(Maintenance)
Work Week Manager i
Thursday:
intema of S pe Frozen Final Work List Review meeting Thursday:
Management approval of Final Work schedule 0AP-025 Rev. 3 Page 39 of 56
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-0 Monday (Week T-7):
Monday:
Wednesday:
Monday:
Saturday Need for System Outage through Friday:
issue Final schedule Final Schedule identified Preliminary System for PGM review reviewed with PGM Schedute Project Manager assigned Engineering Outage Schedute.
implementation Complete'
- Review Meeting Monday (Week T-6):
To include But Not Coverage determined WR/JO planning &
Team perform final Original scope identified Limited to:
Tuesday:
review of outage reviews complete Begin schedule (fragnet)
- ESRs/ Minor Mod reediness:
development
-packages Final System Outage Parts Schedule Review ALARA.
Scope frozen F_riday (Week T-6):
- Special Procedures Meeting Schedule Project Manager, System Work package Manpower Engineer, and Work Week
- Review Team restraints identified WR/JOs Task Ready Clearances Manager initial review of Evaluations Complete (restraints removed)
PMTs/LCOs schedule or WR/JO scope Figure 3 approved to Compensatory Week T-6 & T-5:
remain ori the Measures Schedule comments schedule Pre-pb briefs 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.3 Page 40 of 56 E
FIGURE 3 Page 1 of 1 Schedule Change Approval Form SECTION 1: SCHEDULE ITEM SPECIFICS Unit:
Work Week (s):
Date:
Requester:
WR/JO-PM/JO System #
Current Scheduled Date Rescheduled Date Reason For Change:
Manpower Available?Y / N Support Available? Y/N/NA ALARA Planned?
Y /N /NA WRJO Planned?
Y/N/NA Materials Available? Y / N / NA LCO Required?
Y/N Clearance Prepared? Y / N / NA ESR Approved?
.Y/N/NA SECTION ll: RISK ASSESSMENT Does the change impact plant risk as described in Attachment 4.
Circle one:
Yes / No if yes, proceed tr, Figure 4. If no, provide explanation below.
I Determination by:
/
(Print Name)
/
(Sign Name)
Comments:
Concurrence:
/
/
Implementing Supt 3Date Engineering Supt.
/Date
/
/
Operatiorn. Supt./Date E&RC Programs Supt.
/Date Approval:
/
Supt., On-line Scheduling /Date 1
0AP-025 Rev.3 Page 41 of 56 x
FIGURE 4 Page 1 of 1 R!sk Assessment of Schedule Changes IEmergent Activities NOTE:
The risk assessment methodology identified in Attachment 4 shall be used to perform this assessment. 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:
/
Supt., On-Line Scheduling
/ Date OAP-025 Rev.3 Page 42 of 56
)
FIGURE 5 Page 1 of 1 Long Range Planning Process Overview IDENTWT PROFC%ED ADDITCN TO LRP
$PONSO*U PROKCT MANAGER m
qy IDENTIFIED OENTWY & 00TAIN APPROVAL OF REVISCNS PROKCT MANAOCR AND
$PON10HING SECTION MANAGER flus SS PLANI OGTAIN APPROVALOF
.lMi%CTED" BECTON MANAGERS CHALLENOE PROCESS 1DENTWIED REVtS6ONS SullMIT TO O&S LNP COORDINATOR 1P PERICOiC MANAGEMENT gqqWAfL%CIAL KHVCES UNfT FOR
- CLASSFICATON HUUNQ LRP HEVIFW lOENTWlEO
- FAW e ASSIGNMENT v
REVl.ONS
- AUTHotu1Af1ON REQUIREMENTS
- EVALunf10N OF IMPACT TO FINANCIAL TARGETS 1P 1P REQUEST PHASE AUTHOR 12ATION E
REQUEST PHASE ygg IS 13 yES ENT F AUTHORl2ATON PHASE PHASE 2
AUTHOR 11ATION AUTHOR 11ATION OM MAMGER &
REVISION I A W N
T ^*
ADM NOOC-103 REQUIRED?
REQUIRED 9
'DE C P PHASE AUTH PACKAGE NO NO iP 1P 1P 1P PROMANAGEMENT PRESENTATION & OtSPOUTCN 1P REVISE THE QNG RANCE PLAN 0AP-025 Rev. 3 Page 43 of 56
FIGURE 6 Page 1 of 1 Forced Outage Priority Ready To Work List BRUNSWICK NUCLEAR PLAST Page f 12,Jun-97 UNIT 2 EORCED OUTACE WORKLIST PRIORITY - READY TO WORK Trouble Description Location Status Network Crew Crw Sa Dw CR WRJO Unit Tag Numbw W '"*
- k A'tf**!'
S P' I M LS AMM8 8 '
Y WCD nwP Number 96ADT11 2 24r/D-vce TROUBLE DESC; EDB? TOC:TB2 ELC21 NE G/16A #JTER T32 ELC21 NE Cf16A 1540 X8 Z27 2 3YY STROK:NG CLOSED ON A SHUTDOWri OF THE 25 SJAE. 24WD-RED XCXXXXTT EL 3
NN l 1 j D
M V56 FAfLED TO OPEN WHEN THE 28 SL:AE WAS PLACED IN HALF LOAD. THE VALVE ALSO DrD NOT OPEN WHEN THE LOCAL gg CONTFCL SWITCH WAS USED AT THE SJAE PANEL THE BREAKE REPA R INST: SUMLiARY: VALVE 24r/D-V56 FAILED TOOPEN AUTOMATICALLY. AND FROM THE LOCAL CONTROL SWITCH.
VALVE HAD TO FC MANUAt LY BACKED OFF THE CLOSED SEAT.
TriEN IT OPERATED PROPERLY ELECTRONICALLY. THIS IS THE SECOND FAILURE OF THIS TYPE FOR TH:S VALVE.
96AHN01 2 2-MVD-TR-2 TROUBLE DESC-LOCATION 2S RFP ROOM UNDER GRATING.
154C. X8 Z53 2
3YY j
1 CLEAN THE STRAINER ON TMS TRAP DURING THE NEXT l 2 l H
3060 DOWNPOWER. THE SAME STEAM TRAP STRAINER ON THE 2A 2970M80 RED X0XXXXTT ME 3
NN
.j RFPT W AS Fouro CLOGGED WITH PIPE SCALE. Mf0ERING 97y g PROPER TRAP OPERATION.THE TR-2 AND TR-1 TPAPS WERE CLEANED A REPA:R INST: SL*tMARY: DISASSEMBLE TRAP, INSPECT, CLEAN AND REASSEMBLE.
M84 PiONORK N/A 9CAHND1 2 2-MVD-TR-2 TROUBLE DESC: LOCATION-29 RFP ROOM UNDER GRATING.
1540 Xe 263 2
eYY CLEAN THE STRAMER ON TRS TRAP DURING THE NEXT l3 l H
W DOWNPOWER. THE SAME STEAM TRAP STRAINER ON THE 2A 29700614 RED 1CD000tTT ME 3
NN
~
RFPT WAS FOUND CLOGGED W!TH PtPE SCALE, HNDERING ggg PROPER TRAP OPERATION.THE TR 2 AND TR-1 TRAPS WERE CLEANED A REPAIR INST: SWMARY: DISASSEMBLE TRAP, INSPECT, CLEAN AND REASSEMBLE.
M64 PREWORK N/A 0AP-025 Rev. 3 Page 44 of 56 o
ATTACHMENT 1 Page 1 of 3 Twelve Week Rolling Schedule WEEK "A" WE EK "B" WEEK "C" WE EK "D" ECCS ECCS ECCS ECCS DG1/CS/SLC DG2/RHR 'A" DG3/HPCl/SBGT DG4/RCIC PT 6.1 PT 81.3A/8/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-HPCl260 1 PT 40.2.9 UNIT 1 DIV 1 MST-RHR220 UNIT 2 DIV I 2-MST-ADS 21Q MST RHR230 2-MST-RCIC270 UNIT 1 DIV 11 UNIT 2 DIV ll High Safety Significant High Gafety Significant High Safety Significant High Safety Significant Systems Systems -
Systems Systems 1005,1070 1011,1080 2095 2100 2d35 (NOTE: 1) 2045 (NOTE:1) 4060 (2A NSW PUMP) 4060 (1A.CSW PUMP)-
2040,2070,3050,4060 3070 5065 5095 (DG 4) l 4060 (2C CSW PUMP) -
4060 (1C CSW PUMP) 5095 (DG 3) 5100 (DG 4) 5010 5095. 5100 (DG 2) 5100 (DG 3) 5105 (DG 4)
I 5095,5100,5105 (DG 1) 5105,5110 (DG 2) 5105 (DG 3) 5110 (DG 4) 5110,5111,5112 (DG 1) 5111,5112 (DG 2) 5110 (DG 3) 5111 (DG 4) 1 5113 (DG 1) 5113 (DG 2) 5111 (DG 3) 5112 (DG 4) 5145 -
5170 (NOTE:1) 5112 (DG 3)-
5113 (DG 4) 5175 01 DIV I 5175 U 1 OlV 11 5113 (DG 3) 5135 5240 (1 A-1,1 A-2) 5230 5175 U 2 DIVl 5175 U 2 DIV11 6175 (Dieselpump) 5240(10-1,18 2) 5240 (2A-1,2A-2) 5240 (28-1,2B 2) 8185 6175 (MDFP) 5245 BOP BOP BOP BOP 2010,3020,4010-3025,4015,5040 1050,2020,3030 1065.3040,4045 5035,5250,6060 5255.6070,6240 4040,5045,5259 5050,5185,5260 6160.7045,8055 7060,8065.8275 6075,6195,6245 6080,6180,6260 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 acceptable.
0AP-025 Rev.3 Page 45 of 56
ATTACHMENT 1 Page 2 of 3 Twelve Week Rolling Schedule l
WEEK *E" WEEK "F" WEEK "G" WEEK "H" ECCS ECCS ECCS
'ECCS-DG1/CS 'A*/SLC DG2/RHR *B' DG3/HPCl/SBGT DG4/RCIC PT. 6.1 PT. 8.1.3A/B/C 1 PT. 9.2 PT 10.1.1 A, PT 12.2D
. PT. 7.1.8 PT 8.1.4B PT. 9.3A PT-23.1, PT-23.1.3 PT. 7.2 4A PT. 8 2.28 PT. 8.2.4 PT-12 2C 2 PT 24.12 PT 12.2A PT 12.2R PT 15,6 MST RCIC210 UNIT 1 DIV 1 MST kHR210 2 MST-HPCl260 MST.9CIC220 MST-RHR240 UNIT 2 OlV I MST RCIC230 MST RHR260 MST RCIC260 UNIT 1 DIV 11 UNIT 2 OlV 11 High Safety Signiricant High Safety Signiricant High Safety Significant High Safety Significant Systems Systems Systems Systems 1005,1070 1011,1080 2095 2100 2035 (NOTE: 1) 2045 (NOTE:1) 4060 (2A NSW PUMP) 4060 (2B NSW PUMP) 2040,2070,3050.4060 3070 5065,5095,5100,5105 5095,5100,5105 (DG 4) 4060 (10 CSW PUMP) 4060 (IB NSW PUMP)
(DG 3) 5110,5111,5112 (DG 4) 5010
_5095, 5100, 5105 (DG 2) 5110,5111,5112 (DG 3) 5113 (DG 4) 5095,5100,5105 (DG 1) 5110,5111,5112 (DG 2) 5113 (DG 3) 5135 5110,5111,5112 (DG 1) 5113 (DG 2) 5175 U 2 DIV I 5175 U 2 DIV11 5113 (DG 1) 5170 (NOTE:1) 5240 (2A 1,2A-2) 5240 (2B-1,2B 2) 5145, 5175 U 1 DIV I 5175 U 1 DIV 11 5245 5240 (1A 1,1 A 2) 5230,5240(10 1,18-2) 6175 (Dieselpump) 6175 (MDFP) 8185 BOP BOP BOP BOP-2010,5055,5265 3060,4070,5060.
2020,4075 2055,3076,5005 6085,6165,6235 5200 5205,6005,6115.
5070,5210,6010 6"61,7095,8310 6004 (includes SPDS) 6202,6270,6281 6125,6205,6280 6095,6200.6265 7071 (NOTE: 1) 7110 7100,8195 7105,8065, 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 1
other than shown provided a risk assessment in accordance with Attachment 4 determines risk to be acceptable.
Page 46 of 56 l 0AP-025 Rev.3
ATTACHMENT 1 Page 3 of 3 Twelve Week Rolling Schedule WEEK *l" WEEK "J" WEEK "K" WEEK "L" ECCS ECCS ECCS ECCS DG1/ CS *B*/ SLC/ RWCU DG2/RHR DG3/ HPCl/ SBGT DG4/RCIC PT. 61 PT 8.1.3A/B/C PT. 4.1.1, PT. 9.3A PT 10.1.1 A PT 7.1.8 PT 8.2.4 PT 12.20, PT 15.6 2-PT 10.1.1 PT 7.2.48 PT 12 28 PT 15.7 PT 12.2D PT 12.2A MST-RHR250 MST-HPCl210 PT 23.1.3 PT 14 6 MST-RHR27Q MST-HPCl220 1 MST-ADS 21Q 1 PT-24.1 1 MST RHR280 MST HPCl23Q 1-MST-RCIC270 UNIT 1 DIV 1 UNIT 1 DIV ll MST HPCl270 UNIT 2 DIV 11 UNIT 2 DIV I High Safety Significant Hign Safety Signiricant High Safety Significant High Safety Significant Systems Systems Systems Systems 1005,1070 1011,1080 2095 2100 2035 (NOTE: 1) 2045 (NOTE: 1) 4060 (2A CSW PUva) 4060 (28 CSW PUMP) 2040,2070,3050,4060 W70 5065 5095 (DG 4) 4060(1 A NSW pump).
4000 (1C CSW PUMP) 5095 (DG 3) 5100 (DG 4) 5010 5095,5100 (DG 2) 5100 (DG 3) 5105 (DG 4) 5095,5100. (DG 1) 5105,5110 (DG 2) 5105 (DG 3) 5110 (DG 4) 5105,5110 (DG 1) 5111,5112 (DG 2) 5110 (DG 3) 5111 (DG 4) 5111,5112 (DG 1) 5113 (DG 2) 5111 (DG 3) 5112 (DG 4) 5113 (DG 1),5145 5170 (NOTE:1) 5112 (DG 3) 5113 (DG 4) l 5175 U 1 DIV I 5175 U 1 DIV11 5113 (DG 3) 5135 5240 (1 A 1,1 A.2) 5230 5175 0 2 DIV I 5175 U 2 DIV tl 6175 (Dieselpump) 5240 (1B-1,18 2) 5240 (2A-1,2A-2) 5240 (28-1,2B-2) 5245 3185 6175 (MDFP)
2010,3077 2115,3080,5020 2020,2117,3100 2190,4005,5030 5075,5215,6015 5080,5195,6020 5025,5085,6030 6040,6152,6225 6130,6210,6281 6135,6215,6282 6140,6220,6281,7005 7015,8045,8260 8020,8232,8340 8035.8240,8400 7071 (NOTE: 1) 8500,8580 8390 8040,8250,9300 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.3 Pape 47 of 56 i....
. 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 provides guidance 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
j BNP PRI #E Emergency (Work immediately)
Definition: Those items that have an immediate and direct impact on the health nd safety of the general public, pose a significant industrial hazard, or require immediate attention to prevent the deterioration of plant conditions to a possible unsafe or unstable level.
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 activ4ies that are accomplished shall bc 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 pubiic, the reliab;hty of power generation or industrial safety.
Examples: This classification includes: T/S LCOs s 7 days, loss of plant capacity t 50 MWe, or affects the abikty 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 requinng a power reduction Significant loss of public address (PA), security systems, or plant lighting Significant loss of fire protection capability
~
Action of # 7 days per the requirements of OPLP-01.2, Fire Protection System Operability, Action, and Surveillance Pequirements.
Work Control Response: Work authorized on a 24 hr/ day - 7 day / week basis required to support plant reliability, capacity, or availability. These items will be blocked as Urgent and worked after expedited planning and authonzation.
i 0AP-026 Rev.3 Page 48 of 56 i
ATTACHMENT 2 Page 2 of 2 Priority System Criteria Summary-BNP PRI #2 Emergent (Expedite Schedule)
Definition: Thost items which have a reasonable possibility of affecting safe, economical, reliable, and environmentally sound plant operations.
Examples: Those work items judged to have a possible impact on safe, reliable, and environmentally sound plant operation including activities that affect SALP indicators, mils /kWh, and plant capacity of15 MWe. Specific examples include:
Maintenance Rule A1 System Corrective Actions Loss of 2 5 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 days 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 scheduled work window. These items will be reviewed by Outages and Scheduling, Implementing organization and Operations for schedule impact and either approved via Figure 3 l
for work item addition or blocked for early completion.
BNP PRI #3 Routine (Plan and Schedule per 12 Week or Outage a edule)
Definition: Those items which do not have a significant impact on safe, economic, reliable, and environmentally sound plant operation, Examples: Those items that are routine activities which can be planned and scheduled in accordance with the norma) work control 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 exposure Preventive and corrective maintenance to improve reliability Backlog reduction items Items with Work 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 scheoule determines the work control process response of how rapidly these items 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 activitics 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. 3 Page 49 of 56
ATTACHMENT 3 Page 1 of 2 High Safety Significant Functions System Description High Safety Sig5 cant Function 1000 Containment This pseudo-system is referenced in the Maintenance Rule Program as 1
Isolation Valve a means to monitor reliability of containment isolation valves as -
Pseudo System measured by 10CFR50 Appendix J and the IST program. For the purposes of this procedure system 1011, PCIS, provides the high safety significant function.
1005 Nuclear Boiler Reclosure of SRVs following transients. Manual RPV pressure reduction with SRVs to allow low pressure system injection and ECCS instrumentation actuation. System must be Operable as per Technical Specifications to maintain system function.
1011 PCiS lso ation of HPCl/RCIC and prevent containment bypass / maintain containment integrity. Technical Specifications requirements must be met to maintain system function 1070 CRO Provide high pressure injection for transients. Removing one pump from service constitutes a system outage.
1080 RPS Shutdown reactor for all plant initiating events. System must be Operable as per Technical Specifications to maintain system function.
2035 Core Spray Provide low pressure injection.
2045 RHR Provide containment cooling and low pressure injection. One RHR pump per loop is required to mdatain system function. Also provides shutdown cooling dunng Unit outages.-
2045 RHR SW Provide cooling water for suppression pool cooling. One pump per loop is required to maintain system function.
2070 CAC Provide attemate source of ht." removal by venting through the hardened wet well vent path.
2095 HPCI Provide high pressure injection for transients and SBO.
2100 RCIC Provide high pressure injection for transients and SBO.
3050-Feedwater Provide a flow path for low pressure injection for decay heat removal and high pressure injection for transients. Both pumps are required to maintain system function.
3070 Condensate Provide low pressure injection Two Condensate pumps and two Condensate boosters pumps are required to maintain system function.
4060 Service Water Provide cooling water for RHR HX. vital header, EDGs and miscellaneous BOP loads. Removal of any two pumps per Unit from service disables system function 0AP-025 Rev.3 Page 50 of 56
ATTACHMENT 3 Page 2 of 2 High Safety Significant Functions System Description High Safety Significant Function 5010 EHC Ensure bypass valve operation for RPV pressure reduction during transients. Both pu..ips are required to maintain the system function.
One cooler is required to maintain system function.
5065 Generator Isolated Supports transmission of electncal power to UAT dunng normal Phase Bus Operations and from UAT during back feed configuration.
5095 EDGs and support Sitigate loss of offsite power. l.oss of one train of a support system
$100 sysicms disables the function of that system but does not disable the function of 5105 the diesel generator (5095).
5110 5111 5112 5113 5135 230KV Switch,.ard Provide electrical power to BOP and emergency buses. System must be Operable as per Technical Specifications to maintain system function.
5145 SAT, UAT Provide electncal power to BOP and emergency buses. System must be Operable as per Technical Specifications to maintala system function.
5170 4KVAC Provide electncal power to BOP and emergency buses. Systern must be Operable as per Technical Specifications to maintain system funchon.
5175 480VAC Provide electncal power for numerous safety related loads for various accident scenarios. E Busses are required to 5 Operable as per Technical Specifications to maintain system fuhetion.
5230 250VDC Provide power for HPCI, RCIC, EDGs. Both batteries are required to maintain system function.
5240 125VDC.
Provide power for HPCI, RCIC, EDGs. Both chargers are required to CHARGERS maintain system function.
5245 125VDC BATTERY Provide power for HPCI, RCIC, EDGs Both batteries are required to maintain system function.
6175 FPS Provide 4eSel-driven fire pump low pressure RPV injection during Shutdr i Provide fire protection in the Diesel Generatnt, Reactor, Service Water and Control Buildings FPS must bo operable or compensatory measures in accordance with OPLP 01.2 must be in place to maintain system function.
7071 SBGT Provide secondary containment protection during shutdown. System's high safety significant function not applicable dunng Unt: on line operation.
7110 Fuel Pool Cooling Remove decay heat in fuel pool with fuel off loaded System's high safety significant function not applicable during Unit on-line operation.
8180 RB HVAC Provide secondary containment during Unit outages System's high safety significant function not applicable during Unit on-line operation.
0AP-025 Rev.3 Page 51 of 56
ATTACHMENT 4 Page 1 of 3 Methodology for Assessing and Managing Plant Risk 1.
Maintenance will be scheduled in accordance with Attachment 1, Twelve Week Rolling Schedule when possible.
2.
On line syatem outages, voluntary LCO entries, and ECCS work windows willintegrate maintenance and testing activities.
l 3.
Risk impact of work ec0vities which could affect the availability of those systems used to l
ensure defense-in-depth for Technical Specification action statements or risk management will be evaluated. This includes surveillance tests that do not render equipment inoperable, but could result in a trip or other event.
4.
Risk impact of work activities that could initiate a plant transient if performed 8acorrectly will be evaluated. Maintenance Rule Scoping Questions may be used to id.entify potential transient initiators. Pre job briefs willinclude compen.,atory menures to guard the redundant train or system and contingency plans for anticipated failu'es.
S.
Risk impact of work activities which could affect reactivity management will be evaluated. Pre-job briefs willinclude actions to monitor reactivity charges and mitigating operator actions.
6.
System outages of more than one high safety significant system at a time shall be avoided unless determined acceptable by risk assessment.
t 7.
Scheduling more than two maintenance rule "in scope" systems to be unavailable at a time shall be minimized in order to reduce the cumulative risk impact of multiple systems out of service, 8.
Nuclear Service water pumps shall not be scheduled to be out of service unless all four EDGs are available.
9.
On line maintenance which requires entry into a voluntary LCO w;ll be scheduled to NOT EXCEED one half the allowable LCO time, unless prior Plant General Manager approvalis obtained.
10.
Impact to the opposite Unit will be evaluated for common sjstems. OPLP-28 1 may be used to identify common systems.
11.
ALARA and industrial safety issues should be evaluated.
12.
Work, such as visualinspecticas, which does not require a clearance or does not render equipment unable to perform its functions should be scheduled in accordance with the 12 week ro!!ing schedule to minimize the consequences associated with 'dentification of required maintenance.
0AP-025 Rev.3 Page 52 of 56 n
ATTACHMENT 4 Page 2 of 3 Methodology for Assessing and Managing Plant Risk 13.
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.
l 13.1 Station Blackout 13.1.1 Maintenanci
,o has a high potential of challenging the ability to malti. n off site power to Class 1E systems, should not be scheduled concurrent with system outages on Emergency Diesel Generators (EDG) or HPCI or RCIC.
l 13.1.2 Prior to starting a circulating water intake pump concurrent with E Bus or EDG work consider the effect on E Bus voltage.
13.2 Plant Transients 13.2.1 Maintenance / testing which has a high potential to cause a plant trip (high rkk evolutiona), in conjunction with system outages on Feedwater, CRD, HPCI or RCIC should be minimized.
13.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.
13.3 Loss of Decay Heat Removal System outages of more than one of the following systems at a time should be minimized:
2045 RHR 3070 Condensate 4060 Service Water 5010 EHC I
~
OAP 025 l
Rev.3 Page 53 of 56
i ATTACHMENT 4 Page 3 of 3 l
Methodology for Assessing and Managing Plant Risk 13.4 Small Break LOCA Defense in depth for the small break LOCA scenario is provided by Technical Specification requirements.
13.5 ATWS System outages on systems needed to controllevel during an ATWS, such as HPCl, RCIC, CRD, RHR, and Condensate /Feedwater in conjunction with maintenance on SLC should be minimized.
14.
Authorization for scheduled System Outages will be obtained in accordance with Section 5.6.3.
15.
If needed, Equipment Out Of Service (EOOS) software and/or the PSA group i
may be consulted to assist with determination of risk significance.
d 1
4 9
1 i
4 4
Page 54 of 56]
0AP-025 Rev. 3
ATTACHMENT 5 Page i of 1 On line Schedule Manual Entry Form Associated WR/JO #
(if applicable)
Activity Description l
Unit Unit 1 Unit 2 __
Both St: t Date & Time Crew Code Duration Shift D
(Days) N (Nights)
A (Around the clock)
Clearance Yes No.__.
LCO Yes No When Worked __
RWP Yes No.
Scaffold Yes N o.__ _
System Contact Person &
extension Requested by: _
Approved by:
Outages & Scheduling Representative 0AP-025 Rev.- 3 Page 55 of 56
ATTACHMENT 6 Page 1 of 1 HNP LONG RANGE PLAN ACTIVITY IDENTIFICATION l'ORM UNIT.;
SYSTEM 8.
FAIM NO :
ESR NO.:
PROJECT TYPE:
O&M OCAPITALD PROJECT MANAGER CUSTOMER PROJECT TITLE:
SCOPE DESCRIP110N CONTROLLABLE COSTS (80078) BY COST TYPE I
Phase FAIM #
Year 1:
Year 2. _
Year 3.,,,,,,
Year 4 _
Year $ _
TOTAL r
Study Design Implement Totals i
PROJECT ATTRIBUTES CATEGORY Regulatory Requirement O Economic Benefit O Management Discretion 0 BenW Cat Ratio (Hard Dollars)
D/E:
Net Present Value ($000's) (Hard Dollars)
SCHEDULE STUDY DESIGN IMPLEMENT is Unit Outage Required?
Start Start Start YES O
Compli te.
Complete Complete NO O
APPROVALS I
O Project Manager IMPACTED SECTION MANAGERS O Customer OBESS O initiating Section Manager O MAINTENANCE OOTHER 0AP 025 Rev.3 Page 56 of 56
--l
ENCLOSURE 3 BRUNSWICK STEAM ELECTRIC PLANT, UNIT NOS.1 AND 2 l
DOCKETNOS.50-325 AND 50 324 1
. LICENSE NOS DPR 71 AND DPR 62 t
RESPONSE TO REQUEST FOR ADDITIONAL INFORMATION AND t
SUPPLEMENT TO REQUEST FOR LICENSE AMENDMENTS l
DIESEL GENERATOR SURVEILLANCE REQUIREMENTS i
i a
f
(
- TECIINICAL SPECIFICATION PAGES - UNIT 1 I
,,,