ML20055E727

Ltr Contract NRC-39-89-133,Mod 3,providing Overtime & Extending Period of Performance,To NRC Sys Data Entry,Data Entry for Arm/Daf

ML20055E727
Person / Time
Issue date:	06/13/1990
From:	Stephen Bell NRC OFFICE OF ADMINISTRATION (ADM)
To:	Hutchens T DATA COMPUTER CORP. OF AMERICA
Shared Package
ML20055E715	List: ML20055E714 ML20055E727
References
CON-FIN-D-1920, CON-FIN-D-1920-0, CON-NRC-39-89-133 NUDOCS 9007120286
Download: ML20055E727 (18)

Text

-

i i

o'

'~,

gp A*rp

1. of UNIT ED ST ATES

'[

'j NUCLEAR REGULATORY COMMISSION 5

,E W AsHINGioN. D. C. 20555 i

JUN 131990

....+

Data Computer Corporation of America ATIN: Thomas E. Hutchens Executive Vice President P.O. Box 2665 Columbia, Maryland-21045

Subject:

Modification No. 3 to Task order No. 08 Under.

Contract No. NRC-39-89-133 This modification is issued to (1) confirm the vcrbal authorization of March 7, 1990 granted by the NRC Contracting Officer for thirty (30) hours of overtime beginning March 1, 1990 through April 13, 1990; (2) increase i

the level of effort of this task order as described in the attached Statements of Work, and (3) confirm the verbal authorization'of March 28, i

1990 granted by the NRC Contracting Officer which, effective March 30, l

1990, (a) extends the task order period of performance through May 31, i

)

1991; (b) establishes the total estimated ceiling amount for this extension at $162,217.58; and (c) provides incremental funds of $100,000.00.

j Therefore, the task order total estimated ceiling amount is increased by

$162,217.58 from $149,718.31 to $311,935.89 and the obligated amount is increased ty $100,000.00 from $149,718.31 to $249,718.31.

Accordingly, the following changes are hereby made:

1.

The regular hours for computer technicians under this task order of 7,416 are decreased by 45 hours5.208333e-4 days <br />0.0125 hours <br />7.440476e-5 weeks <br />1.71225e-5 months <br /> to 7,371. The 45 hours5.208333e-4 days <br />0.0125 hours <br />7.440476e-5 weeks <br />1.71225e-5 months <br /> shall be used for 30 hours3.472222e-4 days <br />0.00833 hours <br />4.960317e-5 weeks <br />1.1415e-5 months <br /> of authorized overtime support not to exceed $389.40 (30 hours3.472222e-4 days <br />0.00833 hours <br />4.960317e-5 weeks <br />1.1415e-5 months <br /> X premium re e of $12.98) (refer to FAR Clause'52.222-2--Payment for Overtime Premiums ( APR 1984)), for March 1,1990 through April 13, i-1990 as delineated in the attached statement of work.

.w' 2.

The third paragraph of the definitization letter for this task order is revised and a fourth paragraph is added to read as follows:

" Task Order No. 08 shall be in ef fect from February 1,1989 through May 31, 1991 with a total cost ceiling of $311,935.89.

The amount of

$291,446.84 represents the total estimated reimbursable costs and the amount of $20,489.05 represents the fixed fee.

The total cost ceiling amount of $311,935.89 includes the $75,000.00 verbally authorized to you on March-28, 1990.

$ h 900615 e

NRC-39-g _;gg

L, p

Data Computer Corporation of America The amount presently obligated with respect to this task order is

.$249,718.31 of which $233,081.38 represents the total estimated reimbursable costs and the amount of $16,636.93 represents the fixed fee.

This obligated amount may be unilaterally increased from time to time by the Contracting Officer by written modification to this task order.

The obligated amount shall, at no time, exceed the task order ceiling. When and if the amount (s) paid and payable to the Contractor hereunder shall equal the obligated amount, the Contractor shall not be obligated to continue performance of the work unless and until the Contracting Officer shall increase the amount obligated with respect to this task order. Any work undertaken by the Contractor in excess of the obligated amount specified above is done so at the Contractor's sole risk.

The Contractor shall comply with the provisions of 52.232 Limitation of Funds for this incrementally funded task order."

3.

As a result of this extension through May 31, 1991, and the overtime authorized by this modification, the level of effort for this task order is hereby increased by 7,500 hours0.00579 days <br />0.139 hours <br />8.267196e-4 weeks <br />1.9025e-4 months <br /> from 7,371 hours0.00429 days <br />0.103 hours <br />6.134259e-4 weeks <br />1.411655e-4 months <br /> to 14,871 hours0.0101 days <br />0.242 hours <br />0.00144 weeks <br />3.314155e-4 months <br /> for regular hours and by 230 hours0.00266 days <br />0.0639 hours <br />3.80291e-4 weeks <br />8.7515e-5 months <br /> from 52 hours6.018519e-4 days <br />0.0144 hours <br />8.597884e-5 weeks <br />1.9786e-5 months <br /> to 282 hours0.00326 days <br />0.0783 hours <br />4.662698e-4 weeks <br />1.07301e-4 months <br /> for overtime.

Accounting Data for this Modification No. 3 to Task Order No. 08 are as follows:

B&R No.:

010-20-63-250 FIN No.:

D1920-0 APPN No.:

31X0200.010 Obligated Amount: $100,000.00 It is estimated that the funds provided by this modification are suf ficient

.,to cover performance through September 30, 1990.

All other terms and conditions of this task order remain unchanged.

Please indicate your acceptance of this Modification No. 3 to Task Order No. 08 by having an official, authorized to bind your organization, execute three copies of this document in the space provided and return two copies to the Contract Administrator.

You should retain the third copy for your records.

. 7. _

p :f,

~

ph,,;_ g., L.

s

.,s-

.y Q > y + ';.1.:p

[lj i 7

s im >

" s :.

p-Data. Computer Corporation- -

te of America i

ri-

}

'If you:have any questions regarding.the subject modification; please j

' contact 1 Edna Knox-Davin, Contract Administrator. on'(301)1492-4731.:

i.

.. Sincerely,L ci y

g

-i l

gg t

Sharon Bell,' Contracting Of.f.icer-f'.

' Contract Administration Branch 2-1 Division of.,Contr.'rts c--

l and Property.Ma.agement

.0ffice'of Administration

.1 q

Enclosure:

I

.As stated

~li s --

-(

'N ACCEPTED:

o j vr/Ao b Yu i

NAME.

4 s

Q.-P:

}

TITLE-i 3/kho j

4

-DATE t

}

s -

--J

c i

'k s*

j

- e d ;_'

(if,

l,

.r iif-.

'(f

' b _

['.

i i ll

.i

]

r

!-s j

4 r

l-9 t.

g I

y

[ ~* \\,

UNITEO STA788 NUCLEAR REGULATORY COMMISSION y

wwmeorow. o. c. ness

.k*****

NRC-39-89-133 DATA COMPUTE: CORPORATION OF AMERICA

[

To Be Completed By Task Manager TASK ORDER REQUEST FOR PROPOSAL l

l O

/ /'C. I/)/ [Ma.

/

Task Order Titie:

w

(/ (/

/

11 I

System Number /Name:

/

i User Contact / Phone / Organization: [. /b

/

/ N/?g Requested Period of Perfonnance: Fromh>/f7 Through f/ 9)

I k

TAC i:

STATEMENT Of WORK h-2

?

S0-W 4

/nW M/ % ~J 6 /10.

l y' @4 4 S ~.

6 l

i j

e

?' '

3??%

• /-

UNITED 8TATES NUCLEAR RECULATORY COMMIS$10N n

5 l

wAsHINGTow,0. c. 20sas Task Order Number

" g,

,,/

NRC-39-89-133 DATA COMPUTER CORPORATION OF AMERICA 0008-C To Be Completed By Task :4anager TASK ORDER REQUEST FOR PROPOSAL Task Order

Title:

Onorat innal ' %nnnet Fne NPC ADP Svet ons System Number /Name:

/

User Contact / Phone / Organization:

Anne Stracke

/ 492-9578

/

JRN Requested Period of Performance: From OP/01/89 Through 05/31/91 TAC #: A64079 STATEMENT OF WORK See Attachment I

~~

y

'. l, >.;, 3

.La

I

' ATTACHMENT'1:

er 2,

~. '

Task Ordsr 0008 4

, +

3 BACKGROUND:

~

P This task order is to provide data entry and operational support for various_.

system: activities to include:

1.

.RITS/MPS 4

2.

MPS Pay Tape Processing 3.-

SISOR-4.<

GIMCS=

5.

TAPSS.

6.

NSCS

• 7, 766 System Update.

8.

flodule Authority File 9.

Production of NRR's " Daily Report" g

The level of effort for this task is estimated to be 7500 hours0.0868 days <br />2.083 hours <br />0.0124 weeks <br />0.00285 months <br /> with no-more than 200 hours0.00231 days <br />0.0556 hours <br />3.306878e-4 weeks <br />7.61e-5 months <br /> at overtime rate.

l STATEllENT OF. WORK:

Subtask 1 - RITS/MPS l

q

=The contractor,shall provide data entry and operational support for the-1 following.RITS/MPS activities:

a)'

NRR Op'erational Support b)

'AE0D Operational Support s

c)

_t: MSS Operational Support j

-The data entry and operational support for the MPS activities is defined in F

the RITSCARD User's Guide.

,-j The data entry and operational support for the DB2 RITS activities (TAC, CASE, j

IRTS, Staff Table) is~ defined-in the RITS User's Guide.

-ij Subtask 2 - MPS-Pay Tape Processing

'Thf contractor shall perform the following functions for the MPS Pay Tape Processing:

Biweekly, the Pay Tape is delivered to ARM by Jerry Jenkins of RM/B on i

. Wednesday or Thursday after the end of a pay period.

If the Pay Tape is-not delivered by 2:00 p.m. on Thursday, call Jerry Jenkins or Shirley

~!

1 Fortuna to find out the status of the tape.

When the Pay Tape is received from Payroll, the cono:w tor shall copy the-tape number'on to NRC. MAN. STATS and fill out and attach a. tape label.

The tape label should be filled out as'follows:

Special Tape # nnnnnn Biweekly and date (001208)

Box Number Date MM/YY/DD Phone Number tttt i

Where nnnnnn is the tape number on the Pcy Tape and tttt is the telephone number of the sender.

+

'i'.,

T c

La

=.

4 e

I Task Order 0008 Page 2 t

Af ter the label is~ attached to the tape, the contractor shall deliver the.

tape to the NRC Mail Room. When it is at NIH, it'is copied to an NIH tape using the command procedure PAYCOPY.

This produces a listing by Social Security number of everyone on the Pay Tape. This procedure also updates the T. A. file using the Pay Tape. This adds new personnel and deletes anyone-from T. A. file who was not on the Pay Tape. The Staff /T.A. File compare program is also executed. This program compares the Staff File with the T.A. File.

The nutput of this program is used to manually check any variations between the two files. This program also changes the MPS organization codes on _the T.A. file to correspond with the Staff file. organization codes.

After the processing of the Pay Tape is complete, the Pay File can be created using the command procedure PAYFILE. This procedure will prompt for the month and day of the biweekly in the format HMDD. After the Pay-file has been created, notify the contractor that the Pay File is available so that office Pay Files can be created. The Time Allocation File listing should be sent to the Regions using the command procedure IE.TA. LIST. This procedure prompts for the end date of the biweekly in the format MM/DD/YY.

Subtask 3 - SISOR The contractor shall provide data entry support for SISOR as follows:

Each month a 2-page letter is received from each operating power utility which contains the utility's power statistics.

These letters are collected and forwarded to the data entry technician for input to the SISOR database following the instructions described in the SISOR User's Guide.

Subtask 4 - GIMCS The contractor shall provide data entry support for GIMCS as follows:

Quarterly the GIMCS Task Sheet Reports are updated. The updated reports are forwarded to the data entry technician.

The WYLBUR command procedure,

)

WDCIDXC.GIMCS. UPDATE on CAT, is executed to gather the information to a dataset.

Once all the changes have been entered, the NRC contact should j

be notified.

Subtask 5 - TAPSS L

The contractor shall provide data entry support for TAPSS as follows:

l l

Monthly information is gathered and forwarded to the data entry technician for update of the TAPSS system.

These updates are made following the directions found in the TAPSS User's Guide.

l

4

.v 4 -

a Task Order 0008 Page 3 l

Subtask 6 - NSCS The contractor shall provide data entry support for NSCS as follows*

-The NRC contact will send the input forms along with the one page instructions i

to the contractor data entry technician. 'A data set will be created.

This task is performed twice, annually.

Instructions for Data Entry l

1.

Logon to WYLBUR:

Initials:

XWW i

Account:

WDC6 Keyword:

XEY 2.

Use From &WDC6XWW.STD.MAINT on NRC001.

RESAVE as &WDC6XWW.STD.MAINT. PREV 10VS on NRC001.

Delete lines 2/last.

Note: Line 1 must contain

• • • NUCLEAR STANDARDS ***

with a "1" in columns 27, 32, 34, 36.

Begin entering the transactions as shown on the input forms.

3.

SAVE-AS &WDC6XWW.STD.MAINT on NRC001 LRECL=80(1).

4.

NRC contact when data entry is complete.

Subtask 7 - 766 System Update The contractor shall perform the following update ac tivities for the 766 System:

1. Receive phone calls from the regional offices (5) several times each week (about 10 calls) notifying headquarters of new 766

'datasets to be added to the database. Some of the regions may submit mail to 2MG of the name of their dataset(s).

2. Execute the command procedure to edit the new data.

3. Notify each regional office by phone if error (s) are found and the associated error message.

4. Execute the command procedure to update the database with the error free dataset.

l

A;i;3 n-27,s L. -:

, hijh' :.E

~O i s;.

1 4,. ei., f*.;

^' R.

4

• lC iTask Order 0008J Page 4 rs.a g;;): s I'

-5.~ Notify each regional office by phone.if any error (s)'are found--

in the. update,

6. Notify eachLregio al office by' phone _at the-completion of the n

m

!i '

- update.

ifl 17.1 Execute 'the command. procedure.to copy the update _ database to the MARKlV tape.'.

1 t.'

8. ; Maintain ailog of all datasets as outlined in the 766 processed for_ updating of-the master file.

9. All requests received by 3 p.m. each day will be processed for-

~

-updating.of.the master file.

10.JKeep.a record ofJall' calls and the length of each call.

The 766 Update Procedure and 766 Update Log _are attached. :(Attachment 7).

At

[.f

• q 4

+

lj s'

s.

k l

. h s

h l

1

'i b'),

Task Order 0008-Page 5 i

Sbbtask 8 - Module Authority File (MAF)

The contractor shall update the Module Authority File using the following procedures:

1,.

Create a WYLBUR dataset from the coded forms and-save the dataset as a temporary file on a temp pack.

2.

Copy the temporary dataset to line 38.001 of the updo.e procedure by entering these commands:

USE FROM &WDCDDRZ. MODULE (J2010VPD) ON FILE 46 COPY ALL FROM temp data set name) ON TMPool TO 38.001 3.

Execute the update procedure.

4.

Check the output for errors and verify that the file was updated successfully and that the MARKlV table for regional users have been catalogued successfully.

5.

Print updated reports and notify the user that the file has been updated and that reports are available.

Instructions for Data Entry and Updating the Module Authority File are attached. (Attachment 8).

DELIVERABLES: Update of the Module Authority File.

A

L: -

n

% f ;:$,

n<

wy

,4 4?EL ' '

Mr L.I J I-Task Order '00C8f Page.6; Subtask 9 :- PRODUCT!0N OF NRR's '" DAILY REPORT" The contractor shall= perform.the following " DAILY REPORT" production-S

-activities:

_LI. - entering the textual-data provided by NRR staff 2.

retrieving " DAILY REPORTS"E rom the regions f

3.

preparing reproduction form to make copies ~of " DAILY REPORTS"-

- ;50 copies for the : Division of _0perational Events Assessment, NRR

--- 85: copies for. distribution by the Distribution Services Unit,1 Division.of-Information Support Services,1 ARM s

LDeliverables: -

' data entry for.NRR Headquarters." DAILY REPORT" (daily by.11:00 a.m.)!

- retrieval of regional " DAILY REPORTS".(daily by 2:00 p.m.)-

- preparation and transmittal of. reproduction: form for 135 copies

~

(daily by 3:00Lp.m.):

i 1

~

l

-i 1

.1

~!

a

- 1 l'

1

'I L

I

'I l,

o l

y i

1

is

'2 f~

0:

{-

,3-

.g.

page 1-1 IW2, INTRODUCTION The.766' COMMAND PROCEDURE performs three (3) f unctions;- the -

e RDIT,. UPDATE and COPY.

^

4 c

. The EDIT option.is initially;run by.the regions.

Once a-dataset'is is then called into headquarters.

A log is kept'

-it

' free of:orrors,1 Another containing all the" update -datasets to the 766 database.;

'This Edit = creates the

Edi--t-is.run using the regional-dataset; The

, transactions which-are then used as input to the update.run.

UPDATE. option < should not be executed if any errors are ' encountered The-COPY option is executed once the update has - been-:

e

'in? the edit.

q checked out.

To execute-the 766 COMMANDsPROCEDURE, enter the following to. perform

any'of the above, functions:

EXEC'FR &WDC7DCU.PGMSLIB(IESWRUN) ON CAT-j l

-q a

s-

.l t

l'-

P

-)

l, I) i-1 u

6

> -., '~

page 2 f

II.,766 EDIT The edit job consists of-three steps.

The first-step is the EDSIN.

The EDSIN reads an edit format WYLBUR file and converts it into a formatted file to be read by the second step.

The second step, EDIT 766C, validates the format of each transaction, performs edit checks on each field, and creates i

the edited transaction for updating the 766 database.

The last step, the dummy update, checks the transactions against the database to ensure:

1)

On an insert, the record does not already exist on the database l

2)

On a modify or delete, the keys exist within the database (i.e., able to find the record to_ update) 3)

On an insert for a module (B transaction), duplicate modules are not found within an inspection report except:

a) the module is 92701B b) the module is phase 2 and the module priority is-different c) the module has several violations or deviations.

included in the transaction 4)

Duplicate docket-reports are not file.

Run Procedure:

A call is received from the region stating that a 766 update 1.,

dataset is ready.

Enter the necessary information into the update log.

2.

Execute the Wylbur command procedure IESWRUN.

EXEC FR &WDC7DCU.PGMSLIB(IESWRUN) ON CAT 3.

The command procedure will ask you which option you want.

Select option one (1); it will then prompt you for the month 1

and week (dataset name called in by regions), region number and volume of the dataset to be edited.

If the dataset exists,

-l the command procedure will run the job.

4.

The command procedure will then ask if you want to run another edit job (edit another dataset); if you do not wish to con-1 tinue, you will be asked to chose another option or to end the

' procedure.

- c.

page 3 l

3.

Once the job is run, -check the output f rom the edit and the dummy update to make sure that no errors were found.

the output'from the edit consists of:

a) _

EDIT 766C DIAGNOSTICS:

TOTAL CARDS EDITED 000197 TOTAL INSERT TRANSACTIONS 000010 TOTAL MODIFY TRANSACTIONS 000000 i

TOTAL DELETE TRANSACTIONS 000000 l'

- TOTAL REPLACE TRANSACTIONS 000000 TOTAL TRANSACTIONS EDITED 000207 TOTAL ERRORS ENCOUNTERED 000000 DATA-IS VALID FOR PROCESSING The last message shoud read as above (TOTAL ERRORS ENCOUNTERED 000000 DATA IS VALID FOR PROCESSING).

b) the output from the dummy update should consist of:

BEGIN 766 DUMMY UPDATE PROGRAM i

NO ERRORS FOUND 4

END OF 766 DUMMY UPDATE PROGRAM If errors are found in either stop, call the appropriate region to inform them of the problem; otherwise, the update-job is ready to be run.

If you have several datasets to apply to the database, then each regional dataset should be checked individually in case errors are found.

Once each regional dataset has been

checked, they should be combined into one dataset.

The edit should again be run using the combined dataset as input.

This edit run creates the transaction file which will then be'used as input to the update run.

The update can then be run.

To perform the combined dataset edit (merge), select option three (3) of the command procedure.

The command procedure will ask you to select one of several options.

Select option two (2) to merge several datasets to-You wil then be prompted for the gether for one edit run.

month and week, region number and volume for each individual dataset to be edited.

After the just noted information is entered for a dataset, vou will be asked if you want to merge another dataset; if you enter

'N' (no), the edit job will be e

run and you will be asked to select another option or to end 1

the command procedure.

1 4.

l page 4 III.

766 UPDATE The 766 update job consists of two steps.

The first stop, the actual update step, applies the edited transactions to the The second step creates the MARKIV image tape of 766 database.

the online database, Run Procedure:

1.

Once the edit job has run with no errors, the update is ready to be run.

The update job is a "C" class job.

Only one-update should be submitted a night.

2.

To perform the UPDATE option of this command procedure, select option three (3) and the command procedure will submit a batch job to update the 766 database.

3.

Once the job has finished, check the JES2 LOG and the output to soe if the job-ran properly.

The JES2 LOG should not

~

have any data checks (DCK) against any of the tapes or any ABEND codes.

The output should be checked for the following four items:

a)

The backup of the online database should appear as:

PAGES SAVED - FILE 1 FILE 2 FILE 3 FILE 4 FILE 5 FILE 6 000007 000151 000001 000358 001137 003119

-572-SAVEFILE DSN=WDCDSSW.IES.SAVE, VOL SER:013998 -

-559-SAVED.

.IENF766 7

11361 05/05/82 20:29:33 This will be on a page by itself.

b)

The message, 'BEGIN IE 766 UPDATE PROGRAM', should be a page by itself.

If any errors were encountered in the update step, they would appear following this message.

- = --

. n...

page 5 c)

The run statistics:

=

38920' STARTING SEG3-KEY 10 NUMBER OF INSPECTIONS ADDED

=

91 NUMBER OF HODULES ADDED 0

NUMBER OF SEGMENT 1 MODIFIED 0

NUMBER OF SEGMENT 2 MODIFIED 0-NUMBER OF INSPECTIONS DELETED :=

38934 LAST SEG3-KEY USED The last SEG3-KEY used should be entered onto the update log.

5.

.If the job did not run properly, notify the NRC Systems Analyst in charge of this system.

If you do no receive the output from the 766 update NOTE:

run the edit job then before running anymore updates, and make sure that all the updates were applied.

(You

'ON INSERT, DOCKET REPORT should get-the message, ALREADY ON FILE').

If you do not get this message for the last "I" transaction in the edit transaction file, restore the database using the backup tape from the first step in the update job.

(See Section VII for an explanation of the procedure to follow in restoring the database).

submit the copy job Once the update job has run properly,

- 6.

selecting option four (4) of the command procedure.

by G

1. t

,- e[

~

1 4

4

+

4 5

-' ATTACHMENT P.

TASK' ORDER 0008 en 1

l

r C.

. '4

- g JN_S_TRUCTIONS FOR DATA ENTRY AND UEDAIlFG THE MODULE AUTHO (1).

After receiving coded data entry forms, logon to WYLBUR.

' * - (For logon ' instruction see the NIH User's Guide)

The modulo number coded in the top line titled "MODULEn",

must be coded for all transaction lines in column 3 - 9.

(2).

After logon, create a dataset of.all data on the coded f orms.

(For instructions on how to create a dataset, see NIH User's Guide)

(3).

Upon completion of entering the data, save the data as a 1

SAVE AS temporary' data set on a temporary pack.(ex.

WDCDDRZ.MODTEMP ON TMP001 (cr) )

(4).

Enter "USE FROM &WDCDDRZ. MODULE (J20100PD) ON FILE 46" (cr),

(5).

Copy your temporary data set to line 38.001 using the following command:

" COPY ALL FROM < temp data set name> ON TMP001 TO 38.001 (cr)

(NEVER RESAVE to data set you USE FROM in "4" above) i Enter "RUN UNN HOLD NOTIFY" (cr)

(6).

this job will update the Module Authority File and then l

Note:

the last step will submit another batch job to update l

a MARKIV table for regional users; check the second job by fetching it and listing ' VALID AND HAS BEEN CATALOGED'.

j l

(7).

Check the first job to see that it ran successfully and then print j

discarding the job.

Keep the job on file for 2-3 months before I

it.

i TO PRINT A COPY OF THE MODULE AUTHORITY FILE U

)

(8).

Obtain a copy of the Module Authority File reports -- enter:

!l "RUN FROM &WDCDDRZ. MODULE (J2010NRR) ON FILE 46" (CR).

I The procedure is now executing and will print the report at NIH g

to be delivered to the White Flint Building on the 2nd floor the next day.

(9).

Call Jerry Klingler, NRR, extension 21247 and report that update _s i

available for him have-been completed and that new reports are to pick up.

l