ML20148S731

Requests Approval to Enter Into Emergency Response Data Sys Implementation Contract.Approval of Contract Recommended. Proposed Statement of Work Encl

ML20148S731
Person / Time
Issue date:	03/27/1987
From:	Stello V NRC OFFICE OF THE EXECUTIVE DIRECTOR FOR OPERATIONS (EDO)
To:	Zech NRC COMMISSION (OCM)
Shared Package
ML20148S706	List: ML20148S702 ML20148S731 ML20148S753
References
FOIA-87-737 NUDOCS 8802030131
Download: ML20148S731 (21)

Text

,

DISTRIBUTION 'M EDO R/F ELHalman i

' SECY(3) MJMattia MAR 3 71987 VStello JTaylor

(/ JRoe EJordan t PNorry RThompson p PBird PSmith

/

I S',0RANDUM FOR: Chairman Zech -

FRO't: Victor Stello, Jr.

Executive Director for Operations

SUBJECT:

EHERGEP.'tY RESPONSE DATA SYSTEli D'.PLEMENTATION Your approval is requested to enter into the subject contract which exceeds

$750,000.00 My delegation cf authority requires your approval of such contracts.

Backgroug The NRC, as a regulator of comercial nuclear power plants, will be involved in monitoring any emergency at a licensed reactor that has the potential for affecting the public health and safety. In such an instance, the NRC's role is to suppcrt the licensee and state or local governments who have prinary responsibility for responding to ecergencies at nuclear power facilities. This support includes monitoring the licensee to assure that appropriate protective action recomendations are made offsite, confirming the licenste's reco rvndation to offsite authorities, infoming other Federal agencies and the media of the status of the incident, and providing technical analysis and logistic support to the licensee.

data on fcur types of During parameters: an(1) ercrgency, core and coolant the systm itRC conditices, requires accurate, tiwly(2) conditions e the containoent building, (3) radioactivity release rates, and (a) data from the plant's meteorological tower.

Currently, the licensee transmits data to the NRC by standard voice telephene corrur.ications. Two prinary phone links are used: the Emergency hotification Systec (EUS), a dedicated leased itne vtec prinarily for reactor data, and the llealth Physics betwork (HPN) used prir.arily fur rediological ar.d meteorulogic61

/ data.

E>..arience with a voice-only energency ecmur.ications lid, hes derenstratea that excessive enounts of tine are nc >ded fi.,r the ruutino ter.nsr.ission of data dhd VOrlf) Cation ur CorrtCtion of datd that aDpdr QU;*sticuablQ. (FrOr rktes have been excessive; ir.it16tions have been slew; and frequentf 4 updates have been unreliable. Ircorrect data nay ceuse tha imC to respond to offsite officials of with inaccurate inappropriate protective or outdeted dctiers. advict that results in the implenentation 88020*30131 080127 PDR FOIA SHOLLYO7-737 PDR Centact:

,,;,o Eduard L. Jordan IE c.e h M *" h . M [ _

m ==>

, . . ,1 P6tricia Snith

, AD!1

. .w,q yg .. . ... . ,/ I cc ronu m onomacu cm OFFICIAL RECORD COPY

2 1 1

. i

. Chairt.,5n Zerb - T. - '

i The C(.r..itsion hcs ceteruined th. t ir.pro ud c'an acquisitice. capabilitie s . r.,

% si.ritici tv cr.rbi. 'JC to adr4uutel," fulfill 1ts rup#,se role durires a rwocios. The Er.t rgce.cv P,.spyst Dete Syster (ETC3) it considered to h. th:-  ;

i best tyst c. cencspt for h.eC use in its repast rol. during erorge r.cy  !

sirutt f ans .a t re.acter sites, t

Pistutsiez '!

The Division of Cor.trccts pre.ites to cwpatitively eccuire th- hard.isre, I sot tnare, crd techr.ict 1 i.ssisti.nce s.+ci.s*,ery to ir.plcr.co.t the EE0! to ',upt ort t the f:RC irci6nt resicast tu' nctice. o ar.ticipatt implerentitido of th.* CFM to teke t iv.: pe-rs at an estiinsted cast of '0.370,000, i 4

Tis EPD*; design concept, apprcived by tht Cornniss10n in SECY-04-<01 is en l  ;

i eltetronic tr6nto.1%1cn link te N initiated b 11c.*r sees in on en,,.rgt t rv. Tr e  ;

4 link is to provide cutcrotic updetPg of a linited set of dotc recesser.s 6:r  !

the ! P.C to tr c(p-oder fly csst 55 .uiti pr.Qect the torcition ef th;. pleit ..r.d tu i

)

darunta bMther eppropricte. r cant detivris are t31'c r*ide to stata erd 1. col  :

officials regarding ratesurcs which should t,.. *.eken to prnti.ct th rublic ruris.6 i

6r. enorgency. Tht. EROS coes not it.cludi. eny significar t hardware cr st t tu. rt rocificeticrs tt. lict.rset equipi nt, l.icensets wfl1 use existing t.Isctror:ic i

dato systa.c4 te t r nstnit irduructicn.

4'  ;

Th, csr.t ractor will be. restcnsirle fc.r prccuricy. it.sulling, t r r tJstiat th-  ;

i hardeere and dtvaleping, ir. stalling, anc testing the sof tware besM m the l t

des fon pruc'uti.d by th E.". S rec;uirowls ti etysis. This inclucos equirr<nt

,. i other thari tha teleco 1..unitatio".s r cts.'cri for treirst issir of ti..: voti '.trian  !

f r .n the license tc tht. 'J C %drctiors C*nter. erd tke FeJtteuarters N,r6.t r.

l i.f.d tnf two rar 'or the receipt , referr4tting, display, end ri tren st issim f.f tN i 4

dsta. Thi contractor will .lso N repr.r tit,1. fr.r f.eir.t+r cr.ce o* thr. sys**t.  ;

i durii.g tN ct.ntruct p0riod neo fcr tric training cf s'/sv.r" users.

1

- l Tbs e s t i.me tro fud i ng f o r d i s t ro.i* c t i s s ur r.c ri:e rd hel c..' e nr., f c r FY W 7, j is prmidi.d fur seithin O!E's curr.ot hutet esttivta. TN CIE FY 109 thrcu"I,  ;

4 FY IM*: bucc.*t r,Kuests niill incluh fundit g for thir grt,,foct.

{

) F i n l't. . FY 1M 7 FY 12C FY 19'n J FY 1%0 FY 1"1 FY ltGS

WfT 1RF,VOC l',lECR' l9UQ'- 1 "?F.ItC !!?W.ItC W,U.F IDis pr; #/(

• h $ bc . 0 i'.P ri4 i ni l-f1 b) th i t... t h h r pi g{r f: *3# 1g-* *i. J S t ger hips t Olh .wi k. '*' c s 64.t Uto'. c e'i$ d il t 00% ic8 Is at f f if wr h. Ti . ( .. p r. ' es tl s' be

x. rhitwtc e.ir tipproved by in .(.r b;p C. .i rct.+. . k o t* '

• 't*,

I 1

4

! o" '" >l . . . . ................................................................................

P *^ ">>, ............ ............. ............. .............. ..... .......................

j ............ ............. ............. .............. ..... .......

pccecovmnosom:vono nerir iai orr e n ennv

?

., /

l

~( '

,f r.i i rt ',0. 7. C. 6 3 1

)j Tne Swrc, Fvuluativ Ftr +1 !cd the Csetr#ict int Officer t:ill considtr tis c i r.u. stici of tri,$'iii. iter...I cenflic t of interdi in eccrrdance with t'fC p.lir.y si-t.d. in Tit 14 C1. Ct.(14 ct FArcl fe r, ult tit't.s subk rt /C 1.54, 'and vill i

4 i

vi.succ. t%t oc ar m nire t it.n.1 c',nfitc t / 1r.ter.-:t o ists in the resul t i ir. l cute & rect 8.t'e rd.

f

Sl i uld r

: n.r4 of ,s cor s ta'? hw cv.u it..ib t. ... rdir.4 t .h pr r.ur. i m i M t i a.

6 tnn rv cur t.ict Cit ret t.

.ieroei 1 ' If s r r tricic I., b it t ii. It' . To e cr;.1 - l with vericus previslu's e' th, Fcd6 rel /cquisitiut F.-(ul.nivo which ere cir;ct:e tm:4 ri: sefecusrei:.9 thi ecquisitio. prccast, it is rstierstc d t b t r ll but'c..t in' rem tico ccoc+.rnitic this project t,c. re-0,'rci.d es roofidentit.1 until ef t r the u.i.t r.t t is cust6.d.

l'ac.vr e . ce t 1. r i

a i

isi.$

r.c.w i...r.e try t pu prov1(R rprew 1 u tt tr inn s cc..t r. c t fer th1' c.cc,vi.

j ,

0:igital sigt.ed 4 yictGE Stello e i Vict.,r 5ttile,.1r.

Eurutive Directcr f:.r Corr-ti.. s i C .cl e. s u re :

Propc:,m1 ",t j t z. t..:t M D.rk  :

\

cc: Cerr iss tecer i.. bris C a ise.itorr I.ss lstin-Ct. rini: nsr Cereabel Cu.isti...: r Cerr i i

NC l  ?.ECY l

j s

t

)

1 l EDO /[ E

• s

) \

JI3d V filo 7/ /87 i aM rr' i nz I{R /1 N 3/fl/87 l

cesi: > ADM:DC- 01 gI OIE) / 40- :00 AM: C:D ,4T- :00 ADM- l su w >, AT,h. opp...:.sj. r.d i .,.. hf f;rh ,. .

diA.... hk [ . , . . .

d., . .h[ hy . . l

>' 3/$!.87...... . . . . l.$.8?. . .3/. 3 . !/.87 . 3/.i.5 /.87. . . .3/!<.87.

. . . . . . . . . . . . .3/.'. /.87. . . . . . 3/a /.87. . . .

ocsomu si oso sacuca o OFFICIAL RECORD COPY

Enclosure 1 Section B - Supplies or Services and Pricts/ Costs 7

)

8.1 Brief Description of Work r

9 "Emergency Response Data System Implementation" i

j The objective of this pi'oject is to implement an Emergency Response l DataSystem(ERDS).TheERDSdesignconceptisanelectronictransmis.

{ sion link from the existing electronic data systems used by licensed nuclear power plants at their facilities. The link is to provide l automatic updating of a limited set of data necessary for the NRC to independently assess and project the condition of the, plant, and I

j to assess whether appropriate recomendations are being rade to state '

i and 1ccal officials with respect to measures which should be taken to i

protect the public during an emergency at a licensed nuclear power plant. l i

The contractor will be responsible for procuring, installing, and 4

testing the hardware; and developing, installing, and testing the i software necessary for the ERDS based on the design produced by the ERDS Requirements Analysis. This includes the equipment other than the telecomunications retwork for transmissien of the data stream frere 4

the licensee to the NRC Operations Center, and the Headquarters hardware and sof tware for the receipt, reformatting, display, and retransn.ission of the data. This does not include any significant new hardware or j software modifications to licensee equipeent.

\

. i j March 11, 1987 I

Section C - Description / Specifications / Work Statement C.1 Statement of Work

• C.1.1 Background i

This section describes the history and purpose of the Emergency l Response Data System (ERDS) and its function during an emergency

! at a licensed nuclear power facility. The program for developing and implementing ERDS is described and the contractor's role in that program is delineated.

C.1.1.1 Purpose of the ERDS

) '

The NRC, by virtue of its position as a regulator of commercial nuclear pcwer plants, will be involved in monitoring any erergency at a licensed reactor that has the potential of affecting the public health and i

safety. While the licensee is always responsible for operating the ,

i plant, the NRC has a role in assessing the overall adquacy of licensee actions and recorrendations for mitipeting the accident consequences and protecting the public. The hPC may also develop I independent analyses to assure that the public is fully protected, because experience indicates that Governors and other authorities j l i

j nay call upon the licensee and/or the NRC for advice. This NRC role I in protecting the health ar.d safety of the public requires access to i

certain data from plants during energencies that is as timely and 4

l I

4 accurate, though not nearly as extensive, as that available to the licensee. The current method of manual data collection and telephoned reports is marginal to unacceptable for the NRC to perform its role during emergencies. This process has frequently proven unreliable and inaccurate during events and exercises. Errors are frequently introduced during acquisitien, transcription and verbal transmission. The process has been burdensone to technical personnel '

at the plant site and at NRC. The Commission has determined that improved data acquisition capabilities are essential to enable the Commission to adequately fulfill its response role during '

emergencies.

C.1.1.2 History of EROS As a result of the March 28, 1979, accident at Three Mile Island Unit 2, and at numerous less serious events and exercises since that tire, the NRC recognized the need to substa'ntially irprove the NRC's i

capability to acquire data on plant conditions during emergencies.

The staff's response to this need innediately following the acci-4 dent at Three Nile Island included a proposal for a Nuclear Data link (HDL). A conceptual design for a NDL was prod,;ed under contreet l

with Sandia National Laboratories, ar.d. in April 1981, the Cornission directed the staff to proceed with an NDL prototype program. Hewever, beginning in June 1981, a series of Congressinrcl actions and requests

- caused the NRC to reassess releasing a Request for Proposal to conduct j a prototype study, in the FY 1983 Pay Raise Supplement and the FY 1984 l Apprnpriations Bills, the Congress took actions that effectively rejected several hRC requests to the Congress to allow the hDL to

.~__

proceed. However, the NRC's FY 1984-85 Authorization required that the NDL concept be included as part of any analysis of alternative treans for upgrading NRC data acquisition. -

The FY 1984-85 Authorization Act required the analysis of four issues 4

before an NDL or similar system could be implemented: (1)theappro-priate role of the Comission during an accident (2) the information l needed by the Commission to support that role, (3) the alternative means of acquiring that data, and (4) any changes in Comission author-ity necessary to enhance Comission response to nuclear emergencies.

, The Act also required a cost-benefit analysis of the alternatives considered for acquiring the data. The staff addressed these issues in SECY-84-481 dated December 26, 1984, and following Comission approval, provided a response to Congress. The response described the NRC role in an emergency, as defined by the Comission, as one l l

of monitoring the licensee to assure that appropriate recomendations are made with respect to offsite protective actions. The Comission, r

at this point, abandoned the NDL concept as being inappropriate to i this agency role. The response stated that the Commission had J

selected the Energency Response Data System (ERDS) cencept as the most appropriate means to support its emergency response role, j C.I.1.3 Program Plan l

C.1.1.3.1 - Phase 1. The first phase of the EPDS program was completed

! l J

with the selection of the FRDS concept as the appropriate data acquisi-tion system. Options considered included various means of acquiring l

l l

, the data: manually, autoratically f rom existing systems, or automati-cally with new systems. Options considered for transmitting the data to the Operations Center included electronically formatted data, trace facsimile, and voice coninunications between specially trained and qualified personnel. The criteria used to compare these options included accuracy, reliability, timeliness, completeness, cost, per-sonnel requirements, and backfitting requirements.

The ERDS design concept embodies automatic acquisition of a predeter-mined list of plant parameters, with electronic transmission of the data over standard telephone or other NRC provided contsnication line to a computer at the NRC Operations Center. The ERDS approach emphasizes utilization of licensees existing electronic data systems and minimizes the r.eed for licensees to backfit their systems. Any parameter on the l NRC's list which is not on a particular ifcensee's computer system

, will be transmitted by voice rather than requiring the licensee to 1

add the parameter to its system. In most cases data will be accepted  ;

in the licensee's format to minimize the licensee's software develop-l ment requirements. Transmissions will be manually initiated by the licensee af ter declaration of an emergency at the site. Open receipt at the Operations Center, the data will be automatically converted to a stardard format for display, logging and potential retransmission.

Previsions will be made for display of the converted data stream in the Incident Response Certer of the apprcpriate NRC regional office. l cn appropriate equiprent availt.ble to the NPC site team, and other l

l locations. This concept has been tested twice in exercises with Duke Power Corpany's McGuire facility and with Convnonwealth Edison's LaSalle facility. Both tests demonstrated r.ajor improveeents in assessments and consnunications due to the regular, accurate, time-tagged updating of a limited set of parameters. l C.1.1.3.2 - Phase 2. In the second phase, a contractor (the EROS I Requirenents Analyst) surveyed the existing parameter availability ,

and electronic, data systems at most of the operating or nearly conpleted nuclear power plants in order to detemine the appropriate ,

1 reans to acquire data from each facility and the variety of formats and conventions which must be acconrnodated by the receiving system at NRC headquarters. The contractor detemined the hardware require-ments at the sites, at the Operations Center, and at the Regional Incid,ent Response Centers. The contractor detemined software functional requirements for each site and for the reformatting, display, and retransmission operations at NRC headquarters. The detailed report of the requirements is provided as Attachrent 1.

C.).1.3.3 - Phase 3. In the third phase, a contractor (the ERDS Imple-nentation Contractor) will implerent the Erergency Response Data System. I Based on the system design produced in phase 2 the ERDS Implementation Centractor will procure, install, and test the necessary hardware; end i develop, install, and test the necessary software to produce a functieral EROS. The contracter will furnish a fully crerational system.

l l

)

C.1.1.4 Role of the NRC i

The NRC will provide overall program direction and review and approve all plans and deliverable documents. Plans and documents .

will be approved or disapproved by the NRC Project Officer.

The NRC is responsible for arranging and scheduling the participe-l tion of licensees with ERDS implementation. The hRC will snonitor the contracter-licensee interaction to help prevent any difficulties and i

to help resolve any problems which might arise. The hRC will arrange access to any existing NPC equipment which may interface with the ERDS.

l

C.1.1.5 Role of the Contractor The contractor shall assume complete technical and administrative respensibility for completion of work described in a plan that has j been approved by the NRC.

l The contractor shall notify the contracting officer as soon as pos- '

sible of any circumstances that may cause a "significant variation"  :

in the effort or schedule from that described in the approved plan.

Failure to meet a Scheduled milestone or ten percent or more overrun at the end of any month above the budget planced for that renth are l enrples of "significant variation.

i l

C.1.2 Objective i The objective of this effort is to implement the Emerge,ncy Response Data System.

C.1.3 Scope All efforts being sought by this solicitation constitute the third (implementation) phase of the ERDS progran described in Section C.1.1.3.3.

Offerers are required to propose an approach, costs, and a schedule for completion of all efforts described in Section C.1.4 The successful offeror will become the ERDS Implementation Contractor, and the contract will be awarded for all work described in the Work Statement.

1 C.1.4 Work Statement i

C.I.4.1 Familiarization l l

C.1.4.1.1 - The contractor shall becoet familiar with the NRC Inci-dent Pesponse Program, including the roles and responsibilities of the agency and its response personnel as described in the NRC Incident Response Plan (NRC Manual Chapter 0502) and other cocu-rents available in the NRC Public Docurent Room. See Section C.1.6.

I 1

l l

C.1.1.1.2 - The contractor shall become familiar with the functions,  ;

activities, end operational organization of the NRC's Reactor Safety Teen and Protective Measures Team, which directly utilize the data received from the site of the nuclear power plant during an event.

I The contractor is responsible for understanding the uses for which the data is to be acquired and the problems which are to be corrected by implementation of ERDS.

C.1.4.1.3 - The contractor shall become familiar with the design con-cept of ERDS and the reasons that this approach was selected.

I C.1.4.1.4 - The contractor shall become familiar with the results of the ERDS Requirements Analysis. This includes the information on the licensees' equipment contained in the survey report and the hardware l and software design specifications in the design report. In addition there may be additional design requirements, to be incorporated prior

, to implementation, which may have been added subsequent to completten l cf the Requirements Analysis.

l l

l C.1.4.2 leplementation of the ERDS Transmission Rtception, and Storage System j

C.I.4.2.1 - The contractor shall prept.re a detailed plan, schedule, and budget for establishing an EPOS connection with each plant on j

l l

1 l

i 1 l

the enclosed list (Attachment 2) as described below in sections C.1.4.2.2, C.1.4.2.3, and C.1.4.2.4. The plan shall address plant by plant and Headquarters implementation as separate and concurrent tasks. The plan shall be submitted to and reviewed by the NRC prior I to initiation of work by the contractor.

C.1.4.2.2 - The contractor shall determine the appropriate hardware

)

to satisfy the design specifications in the ERDS Requirements Analysis r

j Report (Attachment 1). Following approval by the NRC. the contractor shall procure, on behalf of the NRC, install and test the hardware i

specified.

I C.1.4.2.3 - The contractor shall develop, install, test, and ensure operability of the software necessary for reception, storage, use and j retransmission of the ERDS transmission from each plant as follows:

f i

In conjunction with the NRC, arrangements will be negotiated with i each plant to provide an ERDS output transmission from the site

.! to the NRC.

i i

As each licensee transmission design is finalized the contractor

} .

will develop, install, test, ano ensure operability of the software 4

recessary for receipt ted modification, if necessary, of the data <

stream on the Operations Center ERDS herdware in compliance with the design specificatiens in the EPDS Pequircrents Analysis Report.  !

6 i

l

The contractor shall develop, install, test, and ensure operability of the software for storage of the data in compliance with the design specifications in the EROS Requirerents Analysis Report.

t The irplementation shall be done in a manner that assures that '

the; completed portiens of the ERDS system are maintained in an operable condition, within design tolerances, over the duration  ;

of the project. The incorporation of each new plant transmission shall not affect the operability of the ERDS with the plants whose connections have been made. The contractor is l i

, responsible for all maintenance of the system from initiation to expiration of the contract.

l l

j C.1.4.2.4 - All sof tware will be documented in accordance with the criteria in NRC Manual Chapter CSO4 (Attachrent 3). I 1  :

C.1.4.3 Implerentation of the ERDS Display System

)

l C.1.4.3.1 - The contractor shall prepare a detailed plan, schedule, and monthly buoget for the inplementation of the ERDS display system

, as described in sections C.1.4.3.2 and C.I.4.3.3. The plan shall be submitted to and reviewed by the liRC prior to tritiation of work by the centractor. The NRC will complete its review within three weeks of receipt from the contrac1;or.

l l

l l

l 1

C.I.4.3.2 - The contractor shall develop, install, test, and ensure operability of the software for the ERDS displays at the Operatiers Center in accordance with the design specifications in the ERDS Requirements Analysis Report.

C.1.4.3.3 - All software will be documented in accordance with the criteriainNRCManualChapter0904(Attachment 3).

C.1.4.4 Implementation,of the ERDS Re-transmisssion System C.I.4.4.1 - The contractor shall prepare a detailed plan, schedule, and monthly budget for the implementation of the ERDS re-transmis-sion system as described in section C.1.4.4.2 and C.I.4.4.3. The plan shall be submitted to and reviewed by the NRC prior to initiation of work by the contractor. The NRC will cceplete its review within three weeks of receipt from the centractor.

C.I.4.4.2 - The contractor shall develop, install, test, and ensure operability of the software at the Operations Center for the re-trans-mission of the ERDS data to the Regional Incident Response Center, the Regional Site Team, and other locations in accordance with the design specifications in the ERDS Requirements Analysis Report.

C.I.4.4.3 - All sof tware will t'e documented in accordance with the criteria in NRC Panual Chapter C904 (Attachment 3).

i .

C.1.4.5 Produce a Users Manual and Provide Training C.1.4.5.4 - Following completion of the efforts described in Section C.1.4.3, the contractor will produce a Users Manual for that portion of the system and provide training sessions for the intended users.

For proposal purposes assume two training sessions at NRC Headquarters.  !

C.1.4.5.2 - Following completion of the efforts described in section C.1.4.4, the contractor will produce a Users Manual for that portion of the system and provide training sessions for the intended users.

For proposal purposes assume two training sessions at NRC Headquarters l

and one at each of five regional offices, i

C.1.5 References q

! a. USdRC Manual Chapter 0502, NRC Incident Resperse Program l I

b. Criteria for Preparation and Evaluation of Radiological Errergency l Response Plans and Preparedness in Support of Nuclear Power Plants, ,

I UShRC Report NUREG-0654, Revision 1. November 1980 l l

l

c. Functional criteria for Emergency Response Facilitics, USNRC 1

Report NUREG-0696, February 1901 1

References are available ir the NRC Public Document Room at 1717 H Street.

N.W., Washington D.C.

i l

Section F - Deliveries and Performance F.1.1 Monthly Letter Report 1

i A monthly letter status report shall be submitted by the 15th of each renth to the NRC Project Officer with copies to the following: '

, s. Program Assistant Division of Operational Assessrent, AE00.

l l

b. Chief, Incident Response Branch. AE00.  !

l

c. Administrative Contracting Officer, Division of Contracts, ADM.

l The monthly report will sunmarize the following as a minimum: l l -

l i

a. Relate actual efforts to those plannedt I

1 i 4

i b. Describe anticipated delays or other problems;

c. Show actual expenditures (for labor, travel, and other costs i

i separately) for the month of the report and cumulative to the i

j date of the report for each rajor eierent identified in the l

approved plan; l

)

I

d. Shcw approxiriate prcjected (>penditures for the following month.

i 1

)

)

4

F.1.2 The effort described in Section C.1.4.2.1 shall be completed within three months after contract award.

F.1.3 The effort described in Section C.1.4.2.2 shall be completed on a ,

schedule agreed upon between the NRC and the contractor based on the  !

delivery schedule agreed upon with the equipeent supplier, j i

F.1.4 The effort described in Sections C.1.4.2.3 and C.1.4.2.4 shall be i completed on a, schedule agreed upon between the NRC and the contractor based on arrangements negotiated with the licensees.

F.1.5 The effort described in Sections C.1.4.3.2 and C.1.4.3.3 shall be corpleted within six months after receipt of the hardware obtained l

under Section C.I.4.2.2.

F.1.6 The effort described in Sections C.1.4.4.2 and C.1.4.4.3 shall be completed within one year af ter receipt of the hardware obtained under Section C.1.4.2.2.

F.1.7 The effort described in Section C.I.4.5.1 will be completed within three ronths af ter C.1.4.3 is coepleted. The effort described ir Section C.1.4.5.2 will be completed within three renths after C.1.4.4 is corpleted.

l 1

l 1

, i

. . t F.1.8 Once every two months briefings will be conducted for the NRC on project status. The location may vary between NRC and contractor offices. However, for cost proposal purposes, assume six trips per year to fethesda, Maryland fcr two persons and one day each.

1 F.1.9 Occasional brief papers, oral briefings, and consultatiens may

te required by the NRC Whenever possible, the NRC will give at least j one week notice of such requests. For cost proposal purposes, assume  ;

two trips per year to Bethesda, Maryland, for two persons and one day  !

each.

1 I F.2 Duratica of Contract Period '

l l

i This contract shall become effective on either the date of award or l the effective date as othentise specified, and shell continue for a j five year period of performance. However, possible action by Congress i may require completion of the effort within three years and at the sare time ensure licensee cooperation with that tire frame. Therefore,

] the Contract may be acceleratec and completed af ter a shorter period t l of performance. Any such alteration shall be made under the Changes clause of this centract (FAR 52.243.2) which provices for negotiation

) of an equitable adjustment to the contractor as necessery.

)

1 -

I i 1

\ l l

I 1

,1 I

I i

a 1

4 Attachment 2 Arkansas 1 Nine Mile Point 1 Arkansas 2 Nine Mile Point 2 Beaver Valley 1 North Anna 1 '

Beaver Valley 2 North Anna 2 Braidwood 1 Oconee 1 Braidwood 2 Oconee 2 Browns Ferry 1 Oconee 3 Browns Ferry 2 Oyster Creek 1 Browns Ferry 3 Palisades Brunswick 1 Palo Verde 1

Brunswick 2 Palo Verde 2 Byron 1 Palo Verde 3 tyren 2 Peach lottom 2 Callaway 1 Peach tottom 3 Calvert Cliffs 1 Perry 1 Calvert Cliffs 2 Pilgrim 1

Catewta 1 Point Beach 1 l

, Catawba 2 Point Beach 2 Clinton 1 l l

Prairie Island 1 i Coeanche Peak 1 Prairie Island 2 Cook 1 Ouad Cities 1 Cook 2 Quad Cities 2

{

Cooper Station Rancho Seco 1 i . Crystal River 3 River Dend 1 -

i Davis-Bessse 1 Rcbinson 2 i i -

Diablo Canyon 1 Salem 1  :

1 Diablo Canyon 2 Salem 2 i Dresden 2 San Onofre 1 j Dresden 3 San Onofre 2  ;

1 Duane Arnold San Onofre 3 -

! Ferwit 2 Seabrook 1  !

Farley 1 Sequoyah 1 Farley 2 l Sequoyah 2 l Fittratrick Shoreham 1 j Fort Calhoun 1 South Teras 1 i Ginna St. Lucie 1 -

Grand Gulf 1 St. Lucie 2 i

I l l l

}

4 i

l I

\

w e .

Haddam Neck Summer 1 I Harris 1 Surry 1 .

j Hatch 1 Surry 2 I l Hatch 2 Susquehanna 1 Hope Creek 1 Susquehanna 2 j Indian Point 2 Three Mile Island 1

- Indian Point 3 Trojan Kewaunee Turkey Poir.t 3 i

k"f,8j{'j Turkey Point 4  ;

li

Limerick 1 Vermont Yankee 1 yngg),g

Maine Yankee Washington Nuclear 2

McGuire 1 Waterford 3 i McGuire 2 Watts Bar 1 i

Millstone 1 Wolf Creek 1 Millstone 2 y,ng,,,,,,,3 i Millstone 3 Zion 1 i Monticello -

Zion 2 ,

I I i

?

(

t

[

i i

f l l 1 i l

i i i

! r 4

l <

i l

l i

1 i

4 1