ML20092H005
| ML20092H005 | |
| Person / Time | |
|---|---|
| Site: | Vogtle  |
| Issue date: | 04/11/1989 |
| From: | GEORGIA POWER CO. |
| To: | |
| Shared Package | |
| ML20092F288 | List:
|
| References | |
| CON-IIT05-129-90, CON-IIT5-129-90, RTR-NUREG-1410 VEGP-29537-C, NUDOCS 9202200422 | |
| Download: ML20092H005 (15) | |
Text
.. _. _ _.
.y.
... ~. _.....
+
- 4 (-
{f-Appttd N
" [ wg" o ^ Electric Generating Plant
~
3 roc 404*G No.
8.y.
~
NUCLEAR OPERATIONS 29537-C y 'e
- n...., n..
b.i. <
- 1 g //.-gy Ur't Col @!ON Georgia Bower fr eo." a u t
wA F(JR1NFC)RiMTION ONDi c
O P l W lo OUTAGE SCHEDULING READ AND DESTROY
- 1. 0
_ PURPOSE 1,1 ~
The purpose of this procedure is to identify the various outage schedules-and-the relations between these schedules (i.e., Planned Outage, !!aineenance Outage, Forced Outage, and Long Range Schedules).
1.2 This procedure identifies the sources of data, tools i
-and methodologies to be used, and the core reporting
- requirements for varioue. schedules.
1.3 This procedure identifies the organizations, telationships, and-responsibilities associated with Outage-Scheduling..
4
,f y NOTE This procedure'does not address the efforts required to support rapid-recovery trips.
1 1.0 DEFINITIONS u.-
- 2.1.
SCHEDULE DATABASE 4
A co;nputer resident accumulation of data for use in the calculation:and, analysis of various schedules, s
4 2.-2 ;
FRAGNET LA graphic representation.of. activities and relacionships ast<ociated with the components of-- a job.
?2,31 OUTAGE WORK PACKAGE
.y
'ALwork-order package which requires.an outage to perform.-
w-O 9202200422 920116 PDR ADOCK 05000424 S
?U3101A sACSuu 1
}
. np
--,_i-+-.,-
~
.,w' m.ie
~ ~'~
PROCEDURE N Miyou
~~
pg' g ng o
i' VEGP 29537-C 1
2 of 15 2.4 REFUELING OUTAGE SCOPE The scope of a refueling outage is the list of all major activities that are tc be performed during the associated outage.
This list includes the planned work on all major components, programs, and significant inspections /surveillances.
The list will also identify the number of approved design changes and anticipated i
f corrective maintenance MWO's, preventative maintenance MWO's, and technical specification surveillances.
./. 5 REFUELING OUTAGE BUDGET The " refueling ootage budget" is the estimated cost of the outage scope activities for inclusion in the 0 & M Budget.
The estimate is prepared by the Outages and Plenning Manager and submitted to Financial Services
+
for inclusion in the budgeting proraso.
3.0 RESPONSIBILITIES g
3.1 VICE-l' RESIDENT, V0GTLE PROJECT
.g
'l The scope of refueling outages and changes thereto are approved by the Vice-President, Vogtle Project.
Typically, this approval is granted 12 montns-prior to O.'
the affected unit being shut down for the outage.
Approvals may be granted by telephone, but should be fotlowed up by written correspondence to enhance communication accuracy.
3.2 GENERAL MANAGER, NUCLEAR PLANT (GMNP)
The GMNP, or designee, has responsibility for:
3.2.1 Overall responsibility for all outage management, t j planning, and scheduling.
3.2.2 Approval of the scope of planned maintenance outages.
P t
3.2.3 Approval of refueling and planned outage schedules.
3.2.4 Development of refueling outage scope, i
l 3.3 ASSISTANT GENERAL MANAGER, PLANT OPERATIONS (AGM)
The AGM has responsibility for:
3.3.1 Froviding direction and setting policy to ensure cifective outage management, planning, and scheduling.
3.3.2 Approval of the scope of planned maintenance outages.
+
v-----
v
--r w--
P OCEoVRE No.
REVISidW PAGENO.
VEGP 29537-C 1
3 of 15 g
r ~w 3.3.3 Aparoval of refueling and planned mdintenance outage
( )
schedules.
3.3.4 Development of the refueling outage scope.
3.4 PLANT SUPPORT MANAGER (PSM)
The PSM has responsibility for 3.4.1 Approval of the scope of planned maintenance outages.
3.4.2 Approval of refueling and planned maintenance outage schedules.
3.5 OUTAJES AND PLI.NNING MANAGER (OPM)
The OPM has responsibility for:
3.5.1 Establishing guidelines for developing the scope of all planned outages as well as approval authority for outage scope.
3.5.2 Approval authority for all Planned Outage, Maintenance Outage, Forced Outage, and Long Range Schedules.
3.3.3 Establishing goals for development and implementation g
of long-range and outage schedules.
3.5.4 Ensuring that all departments support the goals established for the development and implementation of long-range and outage schedules.
3.5.5 Obtaining upper-management approval for significant scope changes for refueling outages.
3.6 0UTAGE SCHEDULING SUPERINTENDENT (OSS)
The OSS has responsibility for:
3.6.1 Ensuring development and implementation of schedules for all outages other than those related to rapid-recovery trips.
3.6.2 Determining the scope of the five-year plan and coordinating efforts required to meet the goals set forth in the five-year plan.
3.6.3 The OSS and the Work Planning & Controls Superinr.endant
}
determine the specific scope of an outage.
l 3.6.4 Reviewing Outage Schedule Change Requests (Figure 1) for impact on outage schedules and identifying
,s(,)
potential scope changes to the OPM.
75s
3 PoocEDUT.E No, REVISloN PAGE No.
~
~ ~ ~
- VEGP 29537-C 1
4 of 15 3.7 PLANNING / SCHEDULING SUPPORT SUPERVISOR (PSSS)
The PSSS has. responsibility fori 3,7.1 Supervising data assembly and conversion activities required to develop a schedule.
-3.7.2 Development and issuance of schedules and reports designed-to support the pre-outage and outage requirements of all cognizant departments and management.
3.7.3 Preparation of post-outage analysis reports.
3.8 WORK PLANNING & CONTROLS SUPERINTENDENT (WPCS)
The WPCS has responsibility for 3.8.1 Development of Outage Work Packages.
3.8.2 Development of fragnets for the execution of Maintenance Work Orders.
3.8.3
' Processing Outage Schedule Change Requests (Figure 1) to. identify resources and materials needed, and assessing the risk of delaying them to future system or refueling outages.
4.0 OUTAGE SCHEDULING 4.1 GENERAL There are four principal categories of schedules covered by the term " Outage Scheduling": Long-Range, Maintenance, Planned Outage, and Forced Outage.
The-Maintenance, Planned -and Forced-Outage Schedules are comprised of-details at the working level and can be used by supervisors and foremen for identifying and assessing daily work requirements.
The long-range schedules are summary-level schedules used for
- coordination of Engineering, Procurement, and other preparatory activities required to support the planc's cutages.
All of the schedules addressed in this procedure are compilations of data provided to the Outage Scheduling Superintendent.in the form of'fragnets or reports.
Development of these fragnets is the responsibility of-various departments.
U)on receipt ot fragnets, Outage Scheduling-integrates them into the appropriate schedule database with the appropriate relationships.
f(r 3 The resulting database is then used in producing the 1
,)
schedules and analyses required to support all users from foremen to senior management.
, ~..
PROCEDURE No.
REVISloN PAGE No.
VEGP 29537-C 1
5 of 15 4.1.1 Schedules are structured in a hierarchical manner both
()
within a particular schedule and between the various schedules.
The hierarchical position (levell of any schedule is governed by the amount of detail include'd in the schedule.
There are four levels of schedules:
4.1.1.1 A Level I Schedule is a Milestone Sched.ile which establishes targets for plant-wide activities (i.e.,
Start Planned Outage) and is used principally at the managenent level for external coordination.
4,1.1.2 A Level II Schedule is a System-Level Summary Schedule which identifies che general time frame in which work is being accomplished on any particular system but does not provide any detail about what work is being accomplished or of the intensity of the work.
This level of schedule is targeted at Supervision / Management and provides a broad view of the progress of an outage.
4.1.1.3 A Level III Schedule is a Job-Order-Level Summary Schedule which identifica all work authorizing documents to be accomplished during the outage and the time frame in which work is to be performed but does not provide information about the detailed steps required to accomplish the task.
This level of schedule is targeted at department-level supervision and contractor organizations, and provides a
(
comprehensive picture of the scope and progress of an outage without the intricate decails of each task.
4.1.1,4 A Level IV Schedule is the Base Schedule and represents all of the detail included in the schedule database.
This schedule is the basis for all of the above and is the source of analyses related to critical path, manpower requirements, etc.
This schedule is intended for use ut the foreman level of supervision and is issued only as window working schedules because of the extensive work detcil included in this level of schedule.
4.1.1. 5.
All four levels of schedule apply to Planned, l
Maintenance, and Forced-outage Schedules, but only Levels I & II apply to long-range schedules because of their underlying summary nature.
l i
l L
l l0, l
mms 5
! i PHoCEWAE No.
REvlSION
'PAGE NO
^*~~ ~
VEGP 29537-C 1
6 of 15 Tr S 4.1.2 Long-Range and Outage Scheduling inVb1ve the i
i,) ~
identification, analysis, and planning of major non-operating activities related to uni
.utages.
They also involve the compilation of information on tasks from numerous sources.
The principal sources of tasks which are included in these schedules are:
1 a)
Nuclear fuela analysis which governs the time between refuelings, b)
Inservice inspection plan which identifies major inspection and testing requirements, c)
Design Change Requests Log which identifies approved and prospective modificaricas to the design of the plant, d)
Surveillance testing program which identifies testing commitments defined in the plant technical specifications, e)
Commitment tracking which identifies external commitments,
(/
N f)
Nuclear Plant Maintenance Information System N--
(NPMIS) which identifies preventive maintenance and corrective maintenance tasks which must be accomplished to ensure plant reliability.
As data is accumulated from these various sources, it is input to the schedule database where it is used to generate both long-range and outage schedules, 4.2
. FORCED OUTAGE SCMEDULE 4.2.1 During the course of normal plant operations, certain tasks must be deferced while the plant is operating at powers some of these can be accomplished in relatively short periods of time or would preclude the unit from l'
returning to power in the event of a unit trip.
Tha forced-outage schedule is a vehicle for the contingency l
ylans required to accomplish this work and is intended t
I_
to maximize the use of any unplanned unit down time.
.GV
[
rwn
. ~. - -
~..-
~..
PROCEDURE No.
REVISloN PAGE No'~
VEGP 29537-C 1
7 of 15 4.2.2 Work Planning and Controls has responsibility for O
-identifying those Maintenance Work Orders (MWO's) which require an outage to perform.
Once an MWO has been identified as " Outage", it is preplanned and a work order package 14 developed which includes all of
-the information required to perform the work (example:
I drawings, material staging location, procedures)
For comalex work, a detailed fragnet is also provided by WorX Planning which delineates the steps required to complete the tasks, the duration and manpower required by each step, and any support requirements.
The-information provided on the fragner, along with information on material requisitions, clearances, radiological work pennit requirements, and other associated data are added to the scheduling database by the Outage Planning Department.
4.2.3 Use of the schedule database allows a routine analysis of the available outage work and results tu the issue of a forced-outage schedule on a weekly basis.
This schedule identifies a)1 outage MWO's which could be performed during an unscheduled outage based on the plant-mode requirements (e.g., all work which would be performed if the plant were brought to mode 4),
A Level III Schedule is approved by the Outage
(,
Scheduling Superintendent and issued each week taking into consideration any additional work which is identified, 4,2,4 When a forced-outage begina, a determination is made on f
the expected duration r.nd what p ant conditions will be maintained during the outage.
This information is then used by the OPM to decide upon limitations to be placed on the outage work scope.
Once the limitations have been set, a revision of the current-week-Level III Schedule is issued and working rehedujes (Level IV) are issued.
During the course of the outage, Outage Planning maintains the status of work via information obtained during shift turnover meetings between key individuals identified by appropriate departments.
The information gathered in.these turnover meetings is compiled and input to the schednle database which in turn is used to recalculate the schedule to provida current forecasts and analyses of progress against the original targets.
O
PAoCEDURF No.
REVIStoN PAGE No.
VEGP 29537-C 1
8 of 15 4.2.5 (7-)
At the concl6sion of the outage, a pouc-outage report is compiled by the appropriate unit Scheduling Supervisor which identifies:
a)
Reason for the outage, b)
Scope cf the outage as defined when it commenced (the initial scope includes the work associated with the repairs required as a result of the units's forced outage and any MWO's pulled from the contingency schedule),
c)
Scope. growth during the course of the outage, NOTE Scope growth for forced outa;es means the additional MWO's that were worked which were aeither on the original schedule, nor contained in the contingency schedule, nor part of the repair work orders required to affect repairs required as a result of the outage.
4(']/
d)
Description / analysis of events which extended / altered the expected crit ical path, s,
e)
Lessone learned during the outage.
f)
Assignment of action items, when required.
4.3 MAINTENANCE OUTAGES 4.3.1 When the requirements for a maintenance outage are 5
identified, Obtages and Planning begins the planning process required to prepare for it.
This planning phsso consists of a review of the tasks precipitating the re work. quirement for an outage and all pending outage This review is done by the Outage Planning Department.
The results of this review are used to establish the primary scope, preliminary duration, and start of the outage.
/~(
L l
mus
~'
~
PMcEDURE No. '
REVISloN PAGE No.
~
VEGP 29537-C 1
9 of 15
_I'.h After the preliminary analysis is completed, a Work
\\~s' Planning effort similar to that described in 4.2.2 is performed.
As the planning progresses, MWO's currently included in the forced-outage schedule are identified for deferral to tho-Maintenance Outage and rolled into the Maintenance Outage Database.
In addition to MWO's, a review of surveillance tracking and Design Change Request Logs are conducted by the departments responsible for maintenance of the logs to identify any tasks wnich, by addition to the outage, me.y enhance future plant availability.
The review is triggered by a request from Outage Planning, when required.
4.3.2 The Outage Scheduling Superintendent will conduct meetings during the planning phase to refine the scope of the outage and ensure coordination of the preparatory tasks associated with the outage being planned.
These preparatory tasks include identification, scheduling, and tracking of pre-outage work activities.
The commencement and frequency of these meetings, along with the various scope cutoff limits, are designated by the OPM.
4.3.3 Development of the schedule is an iterative process based in pre-established milestones (e.g., open generator _ circuit breakers & close generator circuit O,
breakers), where preliminary information is used until a greater level of detail becomes available through the planning process.
As the start of the Maintenance Outage approachen, the level of detail found in the schedule increases and a more clear representation of l
the key areas and resource requirements becomes L
available.
4.3.4 At the conclusion of the outage, a post-outage report is compiled by the Outage Scheduling Su which identifies the same items address.nerintendent ed in 4.2.5.
4.4 PLANNED OUTAGES 4.4.1 Maintenance Outages, as discussed in 4.3, are generally of short to moderate length with limited time available for pre-outage planning.
Planned outages are cyclic and can be reliably scheduled.
The ability to schedule an outage for a particular time irame with a moderate to long duration allows for an outage with extensive scope-and the use of manpower not normally available l
for short lead cime outages.
An extensive olanning and scheduling effort is emoloyed to maximize t,e amount and diversity of work which can be accomplished during the outage.
i 3
- +. - -
- - ~ - - -
PRdCE6 eke No! ^
^
^
REVISION PAGE No~
VEGP 29537-C 1
10 of 15 F
4.4.2 The process of developing s planned outage schedule O-begins with eatablishing a core schedule with those activities which muet be accomplished during every planned outage and decisions on the methodology to be i
used for certain tasks.
The following items are examples of those contained in the core schedule:
a)
Fuel Shuffle Incore or in Fuel Pool b)
Generic System Clearance Scheme c)
RCS Cleanup Method d)
Long-Cycle PM's and Surveillance Tests e)
Inservice Inspection Requirements f)
Shutdown, Layup, and Restart Scheme The planning / scheduling of a Planned Outage starts well h'
in advance of the outage to allow an appropriate lead time for engineering and procurement of materials and services for the major tasks, auch as Design Changes and Majcr Maintenance.
4.4.3 Development of the schedule is an iterative process
('
where preliminary information is used until a greater level of detail becomes available through the planning process.
As the start of the outage approaches, the level of detail found in the achedule increases and a better representation et the key areas and resource requirements becomes available, f
A preliminary schedule is issued approximately six months prior to the start of the outage or at the F
direction of the OPM.
This is c Level III Schedule identifying tha expected scope of the outage and allows concerned marties to perform a preliminary evaluation of the viability and expected scope of the outage.
At this point, the schedule should include all Preventative Maintenance Tasks, Surveillance Tasks, Design Change Packages, and Outage Corrective Maintenance Tasks identified to date in preliminary form.
At the time the preliminary schedule is issued. the scope of the outage should be well defined and more detailed planning of the identified work becomes the key focus.
Work Order Planning Shtets are prepared by Work Planning & Contro'!.s and submitted to Outage Planning.
These planning sheets are used to update and enhance the existing activities in the schedule l) database.
mm
?M443 b."
MtOCEDUCE NO.
HEVISloN PAGE No-3 VEGP 29537-0 1
11 of 15 Prior to the' scheduled start of a planned outage, r-(g~)
Outage Plannir.g, and Work Planning and Controls, jointly conduct a review of the jobs which are pending in the forced-outage schedule.
All jobs which are selected during this review are then added to the Planned Outage database and included in the schedule.
At this time, the schedule is issued for review and the deta11ed work scope of the outage is frozen.
Approximately two weeks are allowed for review and comment, after which the schedule is revised for approval by the OPM and department managers prior to final cpproval by the GMNP.
4.4.4 The Outage Scheduling Superintendent will conduct meetings during the planning phase to define the detailed work scope of the outage and ensurs coordination of the preparatory tasks associated with the outage being planned.
These preparatory tasks include identification, scheduling, and tracking of pre-outage work activities.
The commencement and frequency of these meetings,-along with the various scope cuteff limits, are designated by the OPM.
4.4.5 At-the conclusion of the outage, a post-oatage report is compi1.ed by the Outage Scheduling Superintendent which identifies the same items addressed in 4.2.5.
4.3 LONG-RANGE SCHEDULES 4.5.1 Unlike the outage schedules discussed above, the Long-Range Schedule is not a detailed schedule.
The main purpose of the Long-Range Schedule is to coordinate outages within Georgia Power Company (GPC) and to ensure that preparations for significant outages are properly coordinated.
4.5.2 The Lcval I Long-Range Schedule consists of milestones for each refueling and other plant-wide evolutions.
This document ie-issued semiannually and is used-principally for coordinaticn of outages by GPC.
4.5.3 The Level II Long-Range Schedule consists of summary-activities for:
major items which must be completed during a1 refueling, major capital budget activities which will be performed during normal plant operation, engineering recuired to support capital or outage activities, anc, coordination events such as emergency preparedness drills.
Level II~Long-Range Schedules are issued at the request of management.
(M
\\.)
m.$
WIoEiviiEB.~ ~ -
nevisson paae no.
VEGP 29537-C 1
12 of 15
~s 4.6 SCOPE CONTROL
()
4.6.1
-Scope Control for Forced-Outage Schedules consists of two separate phases.
4.6.1.1 The first phase of scope control associated with Forced Outage Schedules is performed by Work Planning and Controls during the work order preplanning process.
This control is a determination of the workability of i
the taak based upon the availability of materials, engineering, and other support requirements.
4.6.1.2 The second phase is performed after the outage has commenced based upon the plant conditions to be maintained and the expected duration of the outage.
Recommendations en scope limitations in the second phase are made to the OPM b Work Planning and Controls,y Operations, Maintenance, Engineering, and Outage Planning.
4.6.1.3 Once the scope has been approved by ene OPM, all reqcasts for additions to the scope of the outage must be submitted to the OPM via Work Planning & Centrols, and Outage Pisaning, on an Outage Schedule Change Request (OSCR) (Figure 1).
Work Planning & Controls will review the job to determine if it can be
('T accomplished from a technical standpoint and is of
\\m /
significant importance to warrout addition to the work scope of the outage.
Work Planning & Controls determines the resources and materials needed, and assesses the risk of delaying the work to a future system or refueling outage.
The Work Planning &
Controls Superintendent either disapproves thc schedule j
change requent and returns it to the. originator or recommends approval and forwards the request to Outage Planning for schedule analysis.
Outage Planning reviews the request for relation to the critical path and impact on resource requirements.
After analyois, U
the-Outage Scheduling Superintendent ensures appropriate analyses are noted on the form, recommendu either approval or disapproval, and forwards the form to the OPM, If Work Planning & Controls and the Outage Planning Superintendent concur, the OSCR does not require OPM approval.
4.6.2 Scope control for Maintenance and Planned Outages follows the same orocess as for Forced Outages except Phase 2 is implem'ented prior to the start of the outage at the direction of the OPM.
Although the scope control for refueling outages is the same as described above, the refueling outage scope and major changes 7s thereto-are approved by the Vice-President, Vogtle Project.
\\-.
taun
l ggp
..:n. -
z.
VEGP 25537-C 1
13 of 15 1
r 4.6.3 Scone control as defined in 4.6.1 does not apply to
. Oc-Long-Range Schedules.
The only limitations on scope cor.:rol in Long-Range Schedules are in the general guidelines established for inclusion in the Long-Range i
Schedule.
4.7 SCHEDULE STATUS 4.7.1 After an outage commences, the schedule is statused on a daily basis and reports are issued to s apervision and management.
A shift urnover status meeting will be conducted in the outu.a war room at each shift turnover.
This meetrug will. be chaired 'uy the Outage Scheduling Superintendent or the Duty Outage Supervisor.
Ropresentatives of each department / discipline are requited to attend and be prepared to report the status of all activities which are in-progress, scheduled to start / finish but not yet started / finished, and problems encountered / expected, l -
This status should consist of a start / finish time and i
remaining time required to cottplete the. task for each detailed activity within their respective responsibilities.
L 4.7.2 Daily, or at the direction of the OPM, Outage Planning
)
will prepare status reports with an analysis of the 8
progress made against the original targets catablished for the outage, identify problem areas which have arisen or been resolved since the previous
- report, and generate a summary of the scope growth which takes place.
F 4.7.3 After an outage.has been completed, Outage Planning will compile a Post-Outage Report to address schedule performance (target vs actual), scope growth, and lessons learned based upon input from all concerned y
- parties, r
4.7.4 Long-Range Schedules are updated as events occur or on r-a quarterly basis at a minimum.
~
1 R
O 70W5
-, J N4.
PROCEDURn No.
kifVl'SI.)N PAGE No.
-VEGP 29537-C.
1 14 of 15
.,, ~
5.0 REFERENCES
. (
s 5.1 PROCEDURES 5.1,1 01000-C,
" Management of Outages" l
l 5.1.2 00350-C,
" Maintenance Program" i
5.1.3 00460-C,
" Plant Modifications" 5.1.4 00404-C,
" Surveillance Test Program" 5.1.5 29402-C, "WPG Work Order Processing" 5.1.6 29536-C, "Outags Manageraent Program" i
5.1.7 29539-C, "Long-Range Planni..g" END OF PROCEDURE TEXT nU x
l i
r
. p rwe
r PROCEDURE NO.
REVISION PAGE NO VEGP 29537.c 1
15 of 15 l
\\
I' OSCR e OUTAGE SCHEDULE CH ANGE REQUEST DATE
/
p OR10!NAT OR ASSOCIATED DOCUMENTS a
ADO JOB NWO S
DELETE JOB NAME s
SURU
.z. CHANGE DETAIL PHONE DCP o.,
aO SYSTEM - ConP04ENT.
cn DESCRIPTION UT uuRK r
w
.4 a
Cg w
g3 O
REASON FOR CHAMBE TO SCHEDULE was WORX PLANNER DATE _ _ e.
/
e
.z. RESOURCES REQUIRED...
zz gg
.Jn RISK CONSIDERATION w
cx 03 j....
met e
2 SCHEDULCR DATE
/
/
h INPACT TO SCHEDULE wIg w
e3 c
w S
MAJOR SCOPE A00! TION Y
H REQUIRES UICE-PRES!OENT MAPROVAL m
TITLE SIGNATURE APPROVAL DATE RENARKS aw w
UK PLN SUPT Y
N
/ /
w a
SCHED SUPT c
Y N
/ /
a u
Otp MOR Y
H
/ /
w m
o SCHEDULE CHANGE COMPLETCO BY DATE:
FIGURE 1 l
_ _ - - - _ - - - - - - - - _ - - - - - - - - - - - - - - - - - " - - - ~ ~ ~ ' ^ ~ ~ ^~ '