ML19257B420
| ML19257B420 | |
| Person / Time | |
|---|---|
| Issue date: | 03/30/1978 |
| From: | Case E Office of Nuclear Reactor Regulation |
| To: | Boyd R, Harold Denton, Mattson R Office of Nuclear Reactor Regulation |
| Shared Package | |
| ML19257B421 | List: |
| References | |
| REF-GTECI-0000, REF-GTECI-AC, TASK-0000, TASK-OR NUDOCS 8001160112 | |
| Download: ML19257B420 (8) | |
Text
.
UNITED STATES
/*
NUCL'iAR REGULATORY COMMisslON 3'
W ASHINGTON, D. C. 20555 March 30, 1978 g
j MEMORANDUM FOR:
R. Boyd, Director, DPM H. Denton, Director, DSE R. Mattson, Director, DSS V. Stello, Director, D0R Edson G. Case, Acting Director FROM:
Office of Nuclear Reactor Regulation PROCEDURE FOR MAINTAINING GENERIC ISSUE FILES SUBJECT-The attached procedure describes the material related to each generic technical task (Category A, B, C or D) that should be routinely placed in the NRC's Central and PDR files.
In addition, the procedure describes how to routinely provide this material to the Division of Technical Information and Document Control for processing.
This procedure has been developed to assure the following:
A record of the history of the development of the staff conclusions (1) with regard to each technical issue is maintained and made avail-able to the public.
(2) Minimum staff time and cost for retrieval of documents related to each task is realized.
(Experience indicates that many F0IA re-Adherence quests can be expected related to our generic tasks.
to this procedure should greatly reduce the amount of professional staff time ' o respond to such requests.)
t This procedure is effective immediately for filing of current material.
Backfitting of material that was originated prior to this procedure should be completed on a best-efforts basis by September 30, 1978. Each Division should provide the necessary guidance and direction to its rocedure.
personnel to assure compliance with thi
[,.
. 'Edson G. Case,'-Acting Director Office of Nuclear Reactor Regulation 1750 228
Enclosure:
As stated cc:
See next page 80 neo ll2 0
cc:
NRR Deputy Directors _
- DeYoung, R.,
268
- Muller, D.,
P-202 Schroeder, F.,
P-1102
- Reece, J.,
528 NRR Assistant Directors
- Denise, R.,
266
- Eisenhut, D.,
542 Ernst, M., P-302 Gammill, W.,
P-328
- Goller, K.,
370 Knight, J.
P., P-932B
- Miller, J.,
216
- Moore, V.,
P-518
- Ross, D.,
P-1122
- Skovholt, D.,
340
- Tedesco, R.,
P,822
- Vassallo, D.,
110
- Vollmer, R.,
P-514 NRR Branch Chiefs
- Lainas, G.,
P-904
- Baer, R.,
516
- Lear, G.,
338
- Ballard, R.,
P-234 Novak, T.,
P-1132
- Benaroya, V.,
P-802
- Parr, 0.,
124
- Bosnak, R.,
P-924
- Pawlicki, S.,
P-1000
- Bunch, D.,
P-60S Regan, W.,
P-522 Butler, W., 416
- Reid, R.,
321
- Check, P.,
P-1114
- Rosa, F.,
P-822
- Clark, R.,
228 Rosztoc:y, 2., P-1030
- Collins, J.,
P-728 Saltzman, J.,
P-415
- Collins, P.,
358 Schwencer, A.,
316
- Davis, D.,
314
- Shao, L.,
440 Elliott, M.,
214
- Sihweil, I.,
P-1022
- Grimes, B., 238 Speis, T.,
268A
- Heltemes, J., 320 Stepp, J.
C.,
P-312 Houston, W.,
242 Stol, J.,
144A
- Hulman, L.,
P-214 Varga, S.,
116B Ippolito, T., P 722 Youngblood, B.J., P-302 Kniel, K., 148
- iemann, D.,
542
- Knighton, G.,
52S Kreger, W.,
P-712 1750 229
cc:
TASK htANAGERS FOR CATEGORY A TASKS J. Natt C. Graves J. Shapaker S. Hosford A. Szukiewicz J. Strosnider J. Calvo F. Almeter G. Zech B. D. Liaw J. Giannelli C. Anderson J. S. Bland A. Thadani T. M. Su R. Snaider R. Fitzpatrick R. Gamble D. Jeng J. Kovacs 0.D.T. Lynch, Jr.
U. Potapovs F. Hebdon P. O'Connor D. Mcdonald R. Woods J. Long J. Angelo M. Boyle S. Hou J. Costello L. Beltracchi H. Rood R. Watkins P,.,Baranowski_,,,
s d
f.,;g,g,,,
g
" ^ '
7 1'
%dWfhhM49.:p:4 Advisory Gr5up M. Aycock L. Crocker J. Guibert W. Minners D. Wigginton 1750 230
NRR PROCEDURE FOR MAINTAINING CENTRAL AND PDR FILES FOR GENERIC TECHNICAL ISSUES 1.0 Contents This procedure:
- Describes the types of material related to specific generic technical tasks that should be routinely placed in Central Files and in the NRC Public Document Room.
- Designates the originator as the individual reponsible for assur-ing that documents are properly designated with the generic task number ane distributed to the Task Manager, Central Files and the PDR.
- Designates the NRR Task Manager as the individual responsible for monitoring the files for his/her assigned task (s) to assure that material is being properly filed.
- Describes how to provide material to the Accession Unit, Division of Technical Information and Document Control for development of the computer file and approp-iate handling.
- Provides for an annual audit of active generic issue files by the NRR Divisions.
cop h E
h foks4kt 4$&!4&MC%%,%L%
This filina procedure applies to all Category A, Category 8, Category C and Cateoor,y D generic technical tasks as included in the "NRC Procram for the Resolution of Generic Issues Related to Nuclear Power Plants" and approved by the Technical Activities Steering Committee.
3.0 Material to be Placed in Files Central Files Central Files is the official NRC file. The types of documents re-lated to each generic technical task that should be routinely placed in Central Files are If sted below:
(1) Approved Task Action Plan and Task Action Plan Revisions.
(2) All NRR internal memoranda related to the task.
1750 231
. 3.0 (Continued)
(3) All memoranda to or from other NRC offices related to the task.
(4) Correspondence related to the task, including correspondence to and from members of Congress, vendors, architect / engineers, utilities, other government agencies, State and local officials and members of the public.
(5)
Industry topical reports reviewed as part of the task.
(6) Reports to and from the Advisory Committee on Reactor Safe-guards related to the task.
(7) Technical reports or other correspondence supplied by consultants or laboratories that are utilized as technical input to the task.
(8) The final version of NUREG reports, Branch Technical Positions, Standard Review Plan revisions or other technical reports that result from the task.
(9) Sumaries of meetings and trip reports for trips or meetings held as part of the task.
(These documents should be prepared based on factual information.)
'h+V PdbT120NtaneWRb5N'Ac.:.,4c: 44
~ ? 'i. 5 ' -V...
w W e -
,'$
- WA.%
-4,'.'*"
W.n. :u..,e y 4.. m,g.,.,.
.4..
-a The types of documents related to each generic technical task that should be routinely placed in the Public Document Room are the same as those listed above for Central Files with the following exceptions:
(1)
Internal memoranda that do not represent final documents should not be placed in the PDR prior to public release of the final document. As an example, technical input to an SRP revision from a reviewing branch to the Task Manager should not be placed in the PDR prior to releasing the finai (approved by RRRC) SRP revision to the public.
(2)
Internal documents that contain other than factual information, i.e., opinion, should not be placed in the POR.
1750 232
Providing Documents to the Accessions Unit, Division of Document. Control, 4.0 All documents generated within NRR including internal memoranda, cor-respondence and meeting and trip reports that relate to a specific ceneric technical task should have the task number in the upper left hand corner of the first page (in the.same location as the docket number on case related documents). The designation should read "Generi:
Task No. X-XX" where the specific task number is used in place of the The originator of the document has the responsibility for assurinq X's.
that this designation is included on the document and that the document is marked for distribution to Central Files and or the PDR in accordance The originator is also responsible with the guidance in Section 3.0.
for assuring that the Task Manager is placed on distribution for the The sample document correctly designated is provided as document..
Upon receipt of the document and prior to releasing the document to the PDR or placing it in Central Files, Accession Unit personnel will assign an accession number and input information related to the document into a computer. The information inputted to the computer will include such information as the accession number, the task number, the recipient, the originator, the physical location of'the document (Central Files and/or PDR) and a brief description of the subject of the document.
The Task Manaoer is responsible for monitoring the files for his/her task to assure.they are maintained in accordance with this procedure
-and'are complete'M.ecWmonth, the T sis Hanagen 91.1.1 the provide.d.a.
w,
,,['
- '["' 'cifinprits/* Ttstidtf 67 tMeNaccinents(that'.h.svebeery placed.;irg..the. Ce The Task Manager should ' period)6 ally or PDR files for that month.
check the computer listing against his/her working files to assure that all documents that should have been placed in the files have been.
Any documents that have not been should be transmitted to the Accession Unit by the Task Manager utilizing the form provided as Enclosure 2.
This monitoring activity is especially important in the first few If it becomes months following implementation of this procedure.
apparent that certain organizations or originators are not routinely placing the task number on documents they originate, the Task Manager should assure that they are aware of and are following this procedure.
f 1750 233
. The Task Manager should also use the form provided as Enclosure 2 to assure that incoming correspondence, technical repnrts, task action plans, etc., are provided to the Accessions Unit for proper filing.
The Task Manager should request outside organizations and other offices that are expected to be routinely corresponding with NRR on his/her task to designate such correspondence with the Task Number so that it can be properly handled by the Division of Document Control upon receipt.
5.0 Annual Audit of Active Files NRR Division Directors will be requested at least annually to assure that all pertinent material as described in Section 3.0 of this procedure has been entered into the appropriate NRC files.
For this annual audit Task Managers should compare their working files or branch files with the computer file for his/her task.
If this has been done periodically as described in Section 4.0 above, the yearly audit should require minimal effort. The Task Manager should certify to th,e Lead Supervisor that to the best of his knowledge all significant material related to his/her task has been properly entered into the Central and PDR files (as indicated by the computer file, not by a physical search of the files) up to the time of the audit.
The Lead Division should then make the same certification to the Deputy Director, NRR.
.,- ~.,.: e. - ;. i. _::,y., p.m.2 & :. -p: ~. 4 c p
p 2. gy...,.. g:....
- p. 4.;
Mv'?. M& wits, '+ tQ'.~& if }lW=. ~; Ayt.? -iya,.;c,.f y,,} &.y.(..,.,gy., pg s.Y ?%*
1750 234
.