ML20132D255

From kanterella
Jump to navigation Jump to search
Forwards Sys Design for Issue Mgt & Tracking Sys for Nuclear Waste, Per Request
ML20132D255
Person / Time
Issue date: 09/09/1985
From: Altomare P
NRC OFFICE OF NUCLEAR MATERIAL SAFETY & SAFEGUARDS (NMSS)
To: Head C
ENERGY, DEPT. OF
Shared Package
ML20132D260 List:
References
REF-WM-1 NUDOCS 8509300124
Download: ML20132D255 (51)
v • d • e


Text

-

DISTRIBUTION:

A :s/f 403 JGreeves NMSS: r/f J0 Bunting Section: r/f MKnapp Originator HMiller PAltomare REBrowning LETTER TO HEAD MKearney MJBell DMattson /'/> 4__

JSurmeier SEP S M5 LHigginbotham Mr. Charles R. Head RW-43 7F-089/FORS U.S. Department of Energy Washington, DC 20585

Dear Mr. Head:

In accordance with your request I am enclosing a draft copy of " Issue Management and Tracking Procedures" prepared by my staff. I am also enclosing a draft copy of " System Design for an Issue Management and Tracking System for Nuclear Waste" prepared by our contractor, Aerospace Corporation. Please note that these documents were prepared for internal review by the Division of Waste Management staff and are not used by or agreed to by the Division. There may, however, be information that could be useful to you.

We are still planning the Pilot Project status update meeting on September 18, 1985, 9:00 a.m., room 130 in our Silver Spring office. I look forward to seeing you then.

Sincerely,

/s Philip M. Altomare, Section Leader Program Planning Section Policy and Program Control Branch Division of Waste Management

Enclosures:

As Stated pc.f ;  ; 7,9 , .

j

-M 61_ _ _ i-u D MriN n

_---. 8 C/d jt) 8509300124 850909 fji:a f , j, '

. ca a , i, J PDR WASTE PDR

  1. I WM-1 .

1 1

0FC :WMPC r .  :

_ _ _ _ _ . _ _ _ _ .4, _ _ , _ _ . _ _y gp

__7_ . , , , ,

NAME :PAltomare:dh J0 Bunting DATE$85/09/04 $

f7 jfpi

l l

I

  • a 4

IMTS PROCEDURES 7/9/85 PILOT PROGRAM PROCEDURES FOR DWM ISSUE MANAGEMENT AND TRACKING SYSTEM (IMTS) 1.0 PURPOSE The Division of Waste Management (WM) is establishing interim policy and procedures for the identification and resolution of issues affecting the licensing of a high-level waste (HLW) repository and procedures by which the receipt, status, and disposition of issues are documented, thereby ensuring that:

o All issues rair-1 by DWM staff and sources external to DWM such as States and Trimes are given prompt and adequate consideration and their handling and disposition are recorded.

o All issues are screened to determine their significance to public health and safety.

o All issues are assigned appropriate priority and, actions required for resolution, o All issue-related activities are monitored throughout the process from issue identification to issue resolution.

o The activities of DWM staff and the milestones established for their accomplishments are in concert with the requirements for issue tracking and resolution.

o All data and documents that demonstrate and validate the progress achieved in the resolution of each issue are identified and accessible, o The licensee, Department of Energy, is fully informed of potential issues and provided adequate regulatory guidance concerning their resolution.

o All data and documents that demonstrate and validate the progress achieved in the resolution of each issue are identified and accessible.

1.1 BACKGROUND

As the people responsible for reviewing license applications and making licensing recommendations to the Nuclear Regulatory Commission, the NRC staff keenly recognize its responsibility to assure that the DOE high-level waste (HLW) repositories are constructed and operated without unreasonable risk to public health and safety. Consistent with the NWPA, NRC intends to work to ensure that, beginning as early as possible in the site selection. process, 1

IMTS PROCEDURES 7/9/85 potential licensing issues are identified, 00E is informed of every potential licensing issues, and that it has complete, well-validated documentation for each part of the license application that will eventually be submitted for NRC review.

To accomplish this goal and to meet the stringent NWPA schedule, NRC has adopted a strategy of actively identifying potential licensing issues as early as possible. Furthermore, NRC intends to ensure that each issue is addressed in a scientific and technically correct manner that can be demonstrated in the open forum of a licensing proceeding. To facilitate this strategy, the NRC has determined that it is in its interest to establish an Issue Management and Tracking System and to integrate such a system into its strategic planning process.

1.2 pilot Project Demonstration The purpose of conducting a pilot project is to test the IMTS using site specific NNWSI issues. This approach shall enable the DWM to incrementally build a complete system while minimizing potential burden on the. staff.

Building the data. base of issues to be tracked for the pilot program shall be a multibranch effort coordinated by WMPC. Once demonstrated successfully, the data base of issues will be expanded to include the remaining HLW and LLW/UR issues. Selection of the issue test sample is based on the need to use a manageable file size within current schedule and costs constraints.

2.0 DEFINITIONS The following definitions apply to the Issue Management and Tracking System.

2.1 Issue A situation, condition, or concern that if left unresolved could present undue risk to public health and safety.

2.2 Information Need -

Information required to resolve an issue.

2.3 Work Plan The series of milestones and activities required to gather information needs to resolve an issue or to monitor DOE's issue resolution activities.

2.4 Issue Management and Tracking System (IMTS)

A systematic and proactive process that governs the disposition of an issue from initiation through resolution. It includes both Issue Management functions and Issue Tracking functions. The relationship between NRC

~

work plans and issues is shown in Figure 1.

2

I

":" ' TRACKING PROCESS o.ne,.i Technical and -

Site Specific

- - - Positions -

Makr - NRC -

Information Work I'*"'8 Needs identified m m Plans , , Meetings j; Identified I I I I

[Rulemaking I I

% CA s s f j

- m -- y -

m - --

- ~ y -

DOE Requirements Monitoring Specific End Products

! 10 CFR 80.10 CFR 900 40 CFR 191, e.g.. ISTP's and Guldence NRC Procedures .,

Resolution /New issues Identification 1

t IMTS PROCEDURES 7/9/85 2.5 Issue Management c

All functional requirements to effectively implement.the IMTS, including processes and procedures of issue identification and resolution.

2.6 Issue Tracking That portion of the IMTS concerned directly with the design, maintenance, and use of an automated data base that will facilitate storage retrieval and i

reporting of all requisite information concerning issues, 2.7 Strategic Planning trategy, The formulation, implementation, and evaluation of the DWM mission, and plans.

2.8 Issue Review Board (IRB)

An interdisciplinary administrative peer review body, nominally consisting of the five DWM Branch Chiefs or their designees and a representative from ELD,-

chaired by an appointee of the Director, NMSS, andThe supported, as required, by IRB shall be other disciplines from within and without the DWM.

responsible for review-and approval of staff recommended issues to be tracked by the system and for concurrence on all issues considered to be resolved To at There are several options for conducting the IRB meeting.

the staff level.

achieve the greatest accountability the chairman shall makeLesserallaccountability final decisions with the remaining members acting in an advisory role.

would be achieved by all members having veto power.

2.9 Issue Administrator (IA)

The individual responsible for the operation and maintenance of the Information This person shall be appointed from the staff Management and Tracking System.

of the Policy and Program Control Branch. The Issue Administrator shall function as an executive secretary at each IRB meeting but shall not be involved in the IRB decisions other than to answer questions on procedure.

2.10 Issue Data Form (IDF)

The form into which the staff shall enter information on individual candida issues for subsequent entry into the automated Issue Tracking System, if i

approved by the IRB. l 3.0 Issue Management and Tracking Process (IMTP)

The basic steps in the The IMTS issue handling process is shown in Figure 2. issue identification; IMTS process are:

publication, updating, and resolution all of which are closely linked to the DWM work plan system.

3

( .ses eway

('s.-stesaltal Ocw twscs ihma Coru;amse. ice f ,

  • Cooedniase Witti Sta!I DCC l d'"I" M# "9"*

.3 Nm ess.,

wl DWM Duett w's Offnes l 1 f 4l tw.m Aihe musteasim issue Review Hoaed De i me= =g p ,, ,,

  • tlIn s k IDL les e Pa,luem A(seswussoaseve neview tasaan At a e.sm y Staff Assayeuseest (Descisduiest

. ,,,,, m g ,

, ,[

  • Se.wi t. mal ficten ve Preusity Assagaweieses

.......m. ~

g,,j/

  • s .s a. Cl m aen km
e. .._

Need so Is.stk in Ldimeiwtui y C_.s . .

i r

g inata ti.sse Necti Ordyl-

  • PeaaiDI A' hun Hequeeti(Wask Plad I r-

,/

  • De-scenwie Corrmuulity 6 .s.se y

%

  • 4 susaan W.n6mus
  • E =.usw (M sd Dasa Ingme l Iww Adsewusseaum ,

'*"~' h*"'""'"5

+ / . A igwove Permus.c l>>uance of . Pensinni Off.cul kgius

. he.md A Me.agement Reposts so pai,gase

+ Muswoos Peugerss . (;e ,c.ge p.,,n

+

  • Aasvese OWM Mewgemens of pies.nas Psos)sess e bescegwet hd.enues.we Osus*6d ete 88 U lmLese aoe

. .se. .w r.u ,ess

. n.,u... ,,d n.~ a. ..

c Figure 1. Issue Manage:nent and Tracking System Process .., my y .,

0 m

IMTS PROCEDURES 7/9/85 3.1 Issue Identification Issues shall be identified by WM staff from numerous sources both internal and external to WM, including but not limited to the following:

o State and Tribal participation o Document review; o Technical positions; o Correspondence; o Meetings and wc.4 shops; o Regulations and legislation; or o Public media.

3.1.1 Externally Generated Issues The Docket Control Center (DCC) presently receives and logs in all incoming mail and documents, icentifies staff to receive ticketed action items, and makes distribution to the WM staff. As an extension of their normal duties, the DCC staff will note potential issue items for ticketed action and forward a copy to the appropriate technical staff with information copy to the Issue Administrator. The DCC staff will, however, only perform thei'r normal review of incoming documents and will not make a special effort to identify issues.

The identification of licensing issues is primarily the responsibility of the technical and policy staff. It is incumbent upon staff to seriously consider and evaluate all incoming correspondence. Every question or concern received frem a source external to WM such as State and Indian Tribal organizations shall be treated as a candidate issue. Every document that comes into WM must be considered as a potential set of issues, whether or not so intended by the originator. Although all questions, concerns, and other correspondence coming into DWM are to be treated as candidate issues, not every item requires storage in the IMTS. It-is likely that many will be requests for' information and others will be questions and concerns that are entirely trivial or totally irrelevant to the licensing process. However, any potential issue / concern that requires a formal NRC reply, or those deemed by the staff to be significant to the licensing process, shall be documented in a disposition file (See section 3.2).

3.1.2 Internally Generated Issues The primary source of licensing issues will continue to be from the staff j through the normal performance of their duties. Potential issues identified by

the staff shall be brought to the attention of their supervisors for purposes of planning appropriate follow-up actions and resource allocation.

l

l IMTS PROCEDURES 7/9/85 (

l 3.1.3 Allegations f

! I An allegation is a special form of issue and is defined as a declaration, statement, or assertion of impropriety or inadequacy associated with an NRC regulated activities, the validity of which has not been established. This [

4 includes all safety concerns identified by sources such as the media,  !

individuals or organizations outside the NRC, and technical audit efforts from  !

federal, state, or local government offices regarding activities at a licensee's site.

Allegations received or made by the staff must be handled in accordance with NRC Manual Chapter 0517 and a completed Allegation Data Form sent to the NMSS i Office Allegation Coordinator (Bob 0'Connell). Copies are also to be provided

! to the Issue Administrator.

. Allegations will be tracked in the IMTS for information and cross referenced to i

  • he NRC allegation system.

I i

l 3.2 Evaluation of Issues to be Tracked

WM staff will evaluate potential issues to determine that they are not duplicative and represent a significant licensing concern that should be j tracked in the IMTS. IRB approved criteria will be applied in determining

)

whether an issue will be tracked in the IMTS. After staff has concluded that an issue should or should not be tracked in the IMTS, an Issue Data Form (IDF) will be prepared identifying the decision and submitted to the Issue Administrator for processing. The Administrator will then log in an IMTS disposition file all issues raised and monitor their status. The disposition file will contain the status of all issues . including those that are not i approved for tracking by the IRB.

Criteria for stating and evaluating whether issues are candidates for tracking or whether they are information needs required to resolve an issue shall be ,

prepared during the Pilot Project Demonstration.  :

I

{

Staff may independently submit an IDF for consideration by the IRB when there are differing professional opinions on the significance of an issue. Differing

! professional opinions may also be formally expressed in accordance with the 4

procedures of Manual Chapter 4125. It is the staff's responsibility to ensure  !

i that legitimate concerns are identified and recorded in order that they may be ,

addressed early in the program and not result in costly delays and design
modifications for the licensee at a later date.

An obvious requirement for tracking is that there may be significant delay in j the licensing hearing if the issue is not resolved prior to license

application. Concern has been expressed that, if the definition of an issue is i broadly applied, it would include a very large number of less important j technical problems or questions which would render the tracking system useless
in a practical sense and expend resources in maintaining the system rather than i

i 5 l

1 f

l

- . ~ . - - - -- - _. -. .-- -g - ,

IMTS PROCEDURES 7/9/85 resolving the critical issues. This potential problem will be evaluated during the Pilot Program and alternative approaches recommended to insure that the system is tractable and accomplishes its purpose without being overly burdensome.

3.3 Peer Review The IRB shall perform a periodic administrative review of the status and action taken on issues which includes items identified in Section 4.3. r 3.4 Reports  ;

The Issue Tracking System will be automated to enable issue search, review, and f print capability. The system will identify information needs, references,  ;

work plans, and other information pertinent to the issue and will be linked to j a document storage, search, and retrieval system. Special reports and ad-hoc  :

inquiries may be produced by the staff. However, a standard computer report i suitable for internal / external distribution will be prepared by the Issue  ;

Acministrator listing open issues and their status, recently resolved issues, i the basis for resol.ution, and documentation reference. A sample report format _  !

is provided in Appendix A. During the Pilot Project the items to'be tracked and their level of detail will be identified. l 3.5 Issue Updates f

i Staff are assigned issue responsibility at the time the IDF is prepared and  !

shall be provided a copy of the most recently updated IDF. The staff so  !

j assigned will be the primary contact point for questions related to the issue  ;

and are those individuals responsible for the appropriate NRC work plans i with which the issues have been correlated and are intimately familiar with the ,

4 activities that must lead to issue resolution. Because work plan activities

[

are issue-oriented, it will be possible to identify progress towards resolution l of individual issues as a part of the normal staff work effort. When new i i

information is provided by the staff, the updated IDF is transmitted through I the normal pathway of information flow through the branch to the Issue  !

i Administrator.

3.6 Issue Resolution [

! I Determination of issue resolution shall be made by the NRC staff or through the j hearing process. The basis for resolution will be documented, referenced in  ;

the IMTS and reviewed and concurred on by the IRB. Notice of resolution will L be included in the IMTS reports. l 3.7 Issue Data Form l For each issue identified or updated, an Issue Data Form (IDF) shall be  !

initiated. The IDF and specifications for all of the data fields contained in [

the data base are presented in Appendix A. The IDF shall be completed i incrementally by the staff, as information becomes available. Some fields (see Appendix A) shall be activated through software internal to the data base. (

0 i

. - , , , - - - _ , , , - . - - . - - v-. ,- -y ,. - - - - - - - , - . - . - . ,,-.,..,,.-__,-,,..,--,y----.y- -

. - - - , - &~ , - - - , , ,+- . - - - - - - --

"a IMTS PROCEDURES 7/9/85 Basic information that shall be provided during the issue initiation phase include:

o title; o originator; o source; o source data; o site; o waste type; o licensing stage; o statement; and o descr'iptors.

Additional information can be provided or the IDF when available during the initial phase or during later updates including:

o assignment; o resolution required by; o priority; o date initiated; o associated DOE work elements; o associated NRC work plan number (s);

o applicable CFR citation (s);

o common issue (s);

o pacing issue (s);

o issue status; and o action required for resolution.

When the IDF has been completed, it shall be transmitted through standard pathways of information and work flow within the Branch. The Branch Chief or his designee will forward it to the Issue Administrator who will check the IDF for completeness and accuracy. The Issue Administrator will provide staff 7

"a IMTS PROCEDURES 7/9/85 assistance in preparation of the IDF or in searching the data base for common issues, using descriptors provided. This information and a print-out of the IDF following initial data entry will be returned to the issue initiator. The l IA will forward IDF's to the IRB, prior to their meetings.

4.0 RESPONSIBILITIES AND AUTHORITIES 4.1 The staff shall:

A. Identify issues significant to the licensing of a HLW repository and  ;

bring them to the attention of their supervisors or other management as appropriate.

B. Analyze and interpret all information that can form the basis for.

generating an issue. This information can be from within DWM or external to the NRC and may arise from correspondence, meetings, reports, etc.

C. -Complete the ICF and recommend for.IRB approval..with supporting evidence as required, the tracking or resolution of issues.

D. Ensure that all NRC actions identified to resolve issues are adequately covered in DWM Work Plans.

E. Monitor, review, and record progress towards issue resolution.

-F. Update the IDF as required.

4.2 The Issue Administrator shall:

A. Have overall responsibility for the day to day operation of the issue management and tracking system. ,

B. Maintain the software and hardware that comprise the automated data base.  ;

C. Oversee the entry of all data into the data base.

D. Assist the staff and IRB in the writing of issues (consistent form l and content) and in preparation of the IDF. '

E. Extract working summaries from the data base to support the activities of the IRB.

F. Coordinate with staff, as required, in completing the IDF.

G. Prepare the material for the IRB meeting.

8 l

"O IMTS PROCEDURES 7/9/85 H. Attend working group meetings of the IRB and support them, as required.

I. Generate periodic status reports.

J. Coordinate with DCC, as required, in the flow of information concerned with issues.

K. Act as focal point for all external queries concerning contents of the data base.

L. Inform the IRB of any system operation or issue handling problems requiring their attention.

4.3 The Issue Review Board shall: ,

A. Review and approve the actions related to the identification or  ;

resolution of issues.

B. Exercise quality control over all issues generate'd with particular attention devoted to eliminating duplication, ensuring a consistent f level of detail, and proper attention to actions required to reach resolution.

C. Review issue status reports.

D. Coordinate with staff and/or management, as required, in the event of questions concerning an issue. l l

E. Solicit the support of other staff members, as required, during their i reviews.

I F. Direct the IA to officially enter data into the data base.  ;

G. Direct the IA to. publish periodic summary reports for management, /#

staff, and external organizations. I i

I t

i I

6 i.

i f

1

b IMTS PROCEDURES 7/9/85 APPENDIX A.

SAMPLE REPORT ISSUE DATA FORM IMTS DATA FIELD SPECIFICATIONS 10

b

--T 15-l' s

m g m 3 ,

r-:1.

E - Ess e8: e _E 8 3 e

c

=

  • u g3g I =_ e-I e w

a- 5

. al:s m

=e

==

4 ...$2 _i ; 8 _55 .-- O!Es gsss 5

e

. * = _,w gg aq - t -

" l e =

4 - 3 3... '55 l ,

R -. =s v -

co I

_ 18

-=5 EWs;_  :-

e nj!**=!

EU8.-r l

E E 1R 8 gK4 og 5 a ga x_j:

.. a - -

=c. .

s -

a 3

w

=#

Er2 5 #

1 <$- ; Y M u 8 . .

g 5 ~ E 5 l m t s.a ls

n

= =g

g v

.Ig

-M i,

v e..n l" . -

_ m

  • =g3.

8E W =

gf A

$ I 2 I's fy!*

8!-

  • a lx  !

w I.Is85s

R"'8

+ _n'<a W E s I : j' m

.:. s m sg'. - g-= -

- . .i < 8 s-

.u

--= 5 m =

g8,

<m XEC

- u g ag%Wgl $

s a 2=w es ir

$ b 3;haas NE b o

8 b 35$3EE b

E w 3 -

=

smaa 85. Baz --

s

=

??vvey

<<<<=< a .

d _#

W5tusge- ua Er d "5"555 .D m

d W .

b w -  : .

E ar. 5d3 5

c

=

E-

=

m 5 N "D8 s = a W 3-u555EC'I

=3 E j -

021g= M 0 g 3%

WE a 4 -

=

g j0 5g e

= 3g{_ja30 g g s . : 8-s

g=

=_

sr

=

=

Il - m .  :- _c a_

EE<1:3 m = 8

  • 5 y:: a3 - g 883g:IcS W

- =, = -

3

- 8c .

<wa,

$ I

  • 8*32 g *- 3a< MD 2 2 8-  ! -

=E g E J-g5- y 2I"8 .

y a qs .

. g

"= 5 w *1 4 s ga 2 -

W 8 _g C

_- = l2*s:.mM a v -

E = = a 4<--:=

Nas= _I rI -x 8

sr: - 9

-5 a se g e g e s sx 2 - aE kENIg

=f

NNW51 WASIITAfKAGE

~~TRifei1 CAL SAMPtf REPORT #2 TECHk! CAL PIRIINfMI INIIIAL ACTIVITIES IN PROGRESS FORESEEABLE C0hCEhe REGULATION (s) IDENTIFICATION TOWARO RE50tuil0N J N t EST00eES DOE may not be 60.113 (300 - 1000 10/18-19/83 Workshop LLNL Metal-Barrier Testing C&rrosion mechanises are year containment Summary Notes; see also (WB5 2.2.3.2.L) addresses on agenda for Need51/NRC adequately considering workshop to be held non-unifore corrosion performance objective) NRC Yucca Mt. (A Review corrosion rates and fillure mechanises for Comment 10 and comment mechanises 7/23-24/85 the waste package 6-114 (3/20/85) 00E approach to 60.113 (controlled 3/20/85 NRC Yucca Mt. EA LLNL Waste-Foru Testing Waste-form testing is cciculating dissolution release of radionuclides Review Comment 10 and (WB5 2.2.3.1.L) addresses on agenda for NNW51/NRC performance objective) comment 6-118 radionuclide release rates workshops to be held cf the waste form as 7/23-24/85 007 monolith is for various waste forms staplistic and may lead to underestimate Cf radionuclide releases DOE use of average 60.113 (300 - 1000 year 11/23/83 tetter. Coplan LLNL Waste Package environmental conditions containment performance to Vieth, transmitting Environment (145 2.2.2.L) ,

as the waste package cbjective) 10/18-19/83 Workshop addresses determination design of a significant Summary Notes and modeling of the actual namwr of packages where weste package envirorment ,

actual environmental * ' '

conditions exceed the * *

  • design basis . . .

l etc. EEC-etc. etc. etc.

85/07/25 seed 51 WA5TE PACKAGE TECHNICAL 1 ,

-e b

'8SSUE DATA FCRM

, Accession Number: (System Assigned) /

Title:

(2091 Source:

Source Date: / /

Originator: Individual Organization NRC Staff (check onel Name: Title / Chapter:

Address: Affil/

Contact:

Phone Number:

Site: (check onel BWIP NNWSI SRPO Generic Other: Specify Loc (Name. County, State) l waste Type: (check onel Licenstng Stage: (check onel HLW LLW Site Character 12ation UR Construction Operational Assignment:

Lead Branch:

Lead Section: Resolution Req. by: __/__/__

Priority: 1 2 3 4 5 Staff Member:

Date Asstgned: __/__/__

Date Instaated: / /

Date Entered: System Ass 19 Statement:

4 Descriptors: (1069)

Date Last Revised: System Assig.

"b ISSUE DATA FORM tcont)

Issue Related Informatton:

DRJf' Issue Status:

Associated DOE Work Element (s): Duplicate D Associated NRC Work Plan Nots): Active A Applicable CFR Citations: Resolve 4 R Common Issues Accession Nos:

Pacing Issues:

Action Requtred for Resolution: Baseline Current Actual

/ / / /

__/__/__

_,,_/ _ / _ / / / /_

/ /

_/_/_ _/_/_

Current Status:

(704) i Physical Accesston Re+erenced Documents Location Number (50) (8) till Date L ast Revised: System Assig.

IMTS DATA FIELD SPECIFICATI00tS ACCESSION NUMBER (:y: tem-assigned) will provide historical record (Julian date and sequence on a day). Every issue will receive, regardless of decision to track or not track. This is the link between files.

TITLE Brief issue title indicating the subject of the issue.

ORIGINATOR Specifies whether individual or organization. If individual, field includes name, address, title (if any), affiliation (if any), and phone number. If organization, field includes organization name, address, chapter (if any), contact (e.g., name of person sending letter), and phone number. If NRC staff originator, field will include NRC division as name, branch and section as chapter, staff member name as contact, and phone number. All names will be provided last name first.

SOURCE Letter, workshop, teleconference, meetings, etc.

SCURCE DATE Date of workshop, teleconference, etc., leading to issue.

SITE Site to which issue applies, or generic if issue applies to all sites. For BWIP, NNWSI, and SRPO, site location will be compute r-prov id ed . For "other" sites, site name, county, and l state will be entered on data form.

I WASTE TYPE:

Indicates HLW, LLW, or UR.

LICENSING STAGE Indicates stage to which issue applies--site characterization, construction, or operational.

ASSIGNMENT Indicates the primary uranch, sc,ction, and staff member responsible for resolving the issue.

RESOLUTION REQUIRED BY Date by which resolution is required. Must take into account priority and pacing issues.

PRIORITY Indicates priority on a scale of 1 (highest) to 5 (lowest).

Priority is expected to take into account critical path consideration as well as ease of and time required for work towards resolution.

DATE INITIATED Date data form is sent forwrd.

DATE ENTERED (system-assigned)

Data the issue is entered into the IMTS.

STATEMENT Explanation of or rationale for the issue.

OCSCRIPTORS Key words or phrases (separated by semi-colons) suitable for searching.

. I DR/'f!;

ASSOCIATED 00E WORK ELEMENTS Indicates applicable DOE work element numbers, if any. Will '

indicate N/A if none available or applicable. This field is for information only.

ASSOCIATED NRC WORK PLAN NUM8ERS  ;

Every issue must be associated with one or more work plans the achievements of which will result in resolution of the issue. N/A in this field will indicate that none exists initially.

l 1

APPLICA8LE CFR CITATIONS ,

Any CFR parts addressed by the issue will be indicated, as in much ,

detail as known, e.g., 10 CFR 60.122(c)(6). }

i COMMON ISSUE (S) l Accession numbers of all other known similar issues. f k

PACING ISSUE (S)  ;

Accession numbers of issues that must be resolved or on which work must be accomplished before this one can be addressed.

ISSUE STATUS Indication of broad status--O (Ouplicate), A ( Active), i R (Resolved) .

ACTION REQUIRE 0 FOR RESOLUTION Specific actions required to resolve this issue -including plans for workshops, data reviews, research (NRC or DOE), and position pa pe rs . Must be correlated with work plans. Baseline is initial date of expected completion. Current is present date of expected completion (action slippage or acceleration will be the difference i between baseline and current). Actual is date of completion. .

i k

i

, 't CURRENT STATUS Brief statement of recent accomplishments and communications (including those with originator) regarding resolution of this issue. Final entry will cite the action that resolves (closes) issue.

REFERENCED DOCUMENTS Complete citations (title (including document I.D. No.),

author (s), physical location (in DWM) and accession number) for all documents used to aid in resolution of this issue. Final entry will be the document (rule, position paper) that certifies resolution.

DATE LAST REVISED (systen-assigned)

Indicates date latest revision made in the IMTS. Appears on all pages.

DATA ENTRY CLERK IDENTIFICATION Internal record for quality control. Provided each time information added to IDF.

ISSUE ADMINISTRATOR CERTIFICATION Internal Record for quality control.

IRB CERTIFICATION Internal record for quality control. IRB chairperson initials form signifying concurrence. The final step before data are considered official and valid for public consumption.

1 l

T l

4 I

is a sample of the screen that would be displayed for an originator  ;

1 who is an individual. These screens will be different depend 2ng on t the originator type. i i

t

The next block of data is the site-specific data. It consists of the site, waste type, and licensing stage. All options r

are presented on a screen. Figure 8 'l I

t i

i i

6 r 3  ?

n: as t- :as:= .7v.t: i 4
= M .* 9f en Level La site be*act.**tatten

?* .an.s: 2* .as i.evel 1

t 2> 1A*2 23 .eanw 8ec.ven l' !aast.ractten 2*  :.ee ttoaal 1 4D ISRE** t 4D Jnanumst i

$* 2130* f

{ '

. inst 4 *leree It fit W I4W"ttfy'at 2.99 Ille, .e.te *ype 88. .f tspetag stag .

4 1 n aw.r.: zu , .st. -p i t.  :.ee.11ea.i a2 J

w sit.

ret's..ct ,.

, t. set.: ,:, .s c .acat

, a.4.: = :mt ..  ;  !

i i g I

f

' t i

f

, I i  !

. m .. . 4, :4,ctem ne i 1 t

~

J Figure 3 \

/F l

. i-l I l

y I

is a sample display c: available options. Selection from the options  ;

l list is made by entering the three-digit number that indicates the t applicable option.  !

4 i After the site-specific data have been input, the system will l present a screen to enter the issue source data. This screen,

i.  !

t

! I i

l

! 23

} r 4 )

, _ _ . _ . _ , , . _ - . _ - . . _ , - _ _ _ - - _ _ . . . _ _ . _ . _ .. . , _ . , , , _ . _ _ _ . , - - , , , . . _ _ _,.1

- - .. ._ _ ~ . . . . . _ - . . - - .. -. .-

I l

1 Figure 9, seres :ssex - i e t

, n sort.at tr : i e I

u. - ,, .' -

, t i

l 4

h i ,

t i

(

j i

Figure 9 prompts for the date on the original source document, the source of

~

l 1 -

the issue, the title, and the issue statement.-

i 1

I To complete the issue initiation process, the data entry l

clerk is prompted for the descriptor phrases. The entry techniques l

are similar to those for entering an originator; the first prompt is for the stem of the descriptor phrase (Figure 10'), ,

5 f 3 1

f ist :eee stae (se stami m j

!  : t

! 6 i 4 I

i l

i e

i ( ,

.  ! t i i r

. i t

I t

t j J

4 Figure 10 a i i 8

', 24 4

i i

i

_ _ . _ _ _ _ . , _ _ , _ _ _ - _ _ , . _ _ _ , _ _ - _ _ . _ _ . , _ _ , . _ _ . - _ . , . _ . ~ . . . . . _ _

-the system will accept the characters that have been input and compare them with the descriptor phrases that are currently in the file. All phrases that are in the file which match the input. string will then be presented on the screen along with their reference number. (Figure 11).

(

g te e es. 2 esc ** sts" l

g avsaccAa00n f 3 *v08tMG' i I a'DaCm10: I

  • eec-* ster is an t.ie .'st Irusut *ume L3 '*P w =org) 3 j 3eec-* s see- t >yers lys t s l ,

t i

f s aos wee- :ese- st:- (-ta. .ar tan -It :ene t-te- 3

% )

Figure 11 The input string will be matched no matter where it appears within a phrase, for example; if the word WASTE is input all descriptor phrases containing the characters WASTE will be displ.syed, such as:

PACKAGED WASTE WASTE FORM WASTE MECHANICS WASTE PACYJCE.

The data entry clerk then has the opportunity'to select one of the phrases currently in the system, or enter the phrase if it is not in the file. Again, the intent is to use the exact' spelling of phrases that are currently active (no plurals or extraneous suffixes), and not introduce redundant phrases.

On all data input screens, the data entry clerk is given the opportunity to review and make the necessary corrections to the input before the system updates the data files.

25

3.4.2 Update an Issue

, This option allows the data entry clerk to change any of the data that have been input or add new data for an existing issue. If data exist for an issue, the current contents of the fields are displayed and the modifications to the data can be made by directing

) ,

the cursor to the area to be changed and then eatering the changes.

Because the data reside on multiple files and there are more data in the data base than can be presented on a single screen, the system is designed to initially present a screen that enables one to edit predefined blocks of data. Figure 12 f

)  ;

l  : ara su:cx c:-  !

. e-s n== t

. . ,.,3....3.,,1.

,  :~,., ,,,,.co,.,,:.u.,u,,,

3

r. c om.e
  • -,, e..,

ne :ua 3

...,,,,,a.,-

p ;,,c gyg

s. 2.- we.
n eiste ap :ss.e I

I i

. %g :st'en

., ; .* twee*

ts t tag 2're n's '.ss.e s wets 1

E J Figure 12 is an illustration of the menu options that can be invoked. The data base is logically partitioned into nine blocks of data, each block of data addressing a specific subset of the data base.

Originator Data: This procedure generates a series of screens that allow ' modification of the originator type or any of the data fields that define the originator.

Site-Seecific Data: This procedure permits modification of the site, the waste type, and the licensing stage assigned to the 26

, - ~. . _ . - . - _ _ _ - - . . - . . . . _ _ . _ . _ - _ - - _ .

t o .

I issue. The current values of the data are presented and the data entry clerk is prompted for changes in the same manner as in the issue l

I initiation procedure.

i .

! Assignment Information: This procedure permits modification or initial input of all information associated with the issue -

j assignment. The specific data included in this category are; Lead Branch, Lead Section, staff Member, the date that resolution is i

required, the priority, the date the assignment was made, and the date a

j the issue was initiated by NRC.

i-f, Title and Statement: -This procedure permits modification of

, the source data. The specific data fields included in this category 1 .

j are the date of the source, th.e source of the issue, the issue title, i I

and the issue statement. '

l Descriptor Phrases: This procedure permits deletion from and/or addition to the descriptor phrases assigned to an issue. If I

this procedure is invoked, the data entry clerk is first' presented with the phrases currently assigned to the issue and is then given the opportunity to delete any of the phrases or add new phrases to the issue.

{

Current Status: This procedure appends.the new data to the r

j current status file. These data do not replace the previous entries, but introduce the new record to the file. The procedure automatically assigns the accession number of the issue and the date the file _was i

7 updated. Although only the most recent entry will appear on the IDF, a report can be generated that will print all the records for an issue j in reverse chrcnological order.

l Required Action: This procedure permits modification of any

] of the milestones assigned to an issue. All milestones are presented i and the data entry clerk indicates which is to be modified. The i ,

I

  • 27 '

7 i

i

milestone to be edited is then presented on the screen anc the data entry clerk. directs the cursor to the field to be modified and ef fects the changes. This procedure also allows new milestones to be introduced to the issue.

1 Issue-Related Data: This procedure permits adding to, or modifying the following data: Associated DOE Work Elements, Associated NRC Work Plans, Applicable CFR Citations, Common Issues Accession Numbers, Pacing Issues, and Issue Status. When an issue is introduced to the system, it is automatically assigned a status of

" Initial." As the issue is processed, it can be assigned a status of Active, Duplicate, or Resolved.

i

Reference Documents
This procedure appends new data to the
document reference file, i.e., title, location, anc accession number t

of the document. The documents in this file are documents the staff members reviewed to make a deter =ination of issue resolution.

Delete an Issue: If this procedure is invoked, the indicated issue will be deleted from the data base.

3.4.3 Search an Issue The search option is intended to be used by a staff member to determine if there are issues in the system that are similar to the issue currently being worked on, one reason being to gain insight on how to resolve that current issue. When the search procedure is invoked (option 3 on the main menu) a screen will be presented that lists the search options (Figure 13).

l

18 l

... _ , _ _ . _ . _ . _ . . . ._. u_ _ __

f .3 1

i : speci aa cus  :

a tit.  :

.- > w aters .

. > ittle .

l . e Stetasept =

l l

_ l (Mae Oetten w se : *a w ts % n moms t )

Figure 13 The four search parameters, Site, Descriptors, Title, and Statement, are considered to be the minimum set of parameters. The intent is to initially choose only the most important parameters to be implemented rather than provide an indiscriminate list, which may make the system too cumbersome. However, as the system is used, other parameters may be added to the list. The options can be entered in any order and the results of a previous search are available to the next search option.

The search strategy is to satisfy a single criterion at a time. The system, therefore, queries the user to determine whether to concatenate the results of the current search with a previous subset or to search within the previous subset. For example:

Case'1 The user wishes to find all issues that have either a descriptor phrase of WASTE PACKAGE or CORROS10N. In this case, the user would first search the entire data base for-the first phrase and the system would respona with the number of issues that satisfy that criterion. Then', the user would direct the system to search on the second descriptor.

Because the system knows that there is a subset of issues that satisfy a previous search it would inquire whether the  ;

user wishes to search the main file and add to the' previous '

subset all issues that satisfy the second criterion, or whether the user wishes to find the second phrase within the first subset. in this example , the user would select the 29 1

option to add to the subset. The system would then determine which issues satisfi' ed the second criterien, add the accession numbers of those issues to the list, and process the list to eliminate redundant accession numbers.

Case 2 The user wishes to find all issues that have both descriptor phrases si.ewn in Case 1. In this case, the first step would be the samm , but when satisfying the second criterion the user would indicate to stay within the subset of issues that satisfied the first criterion. The system woule then search within the subset and retain only the accession numbers of those issues that also satisfy the second criteria.

Site Search: This procedure presents to the user a site criteria screen that lists the site acronyms (Figure 14),

," T asiu. ecs stu u were on

u,Wn n =c:

l > 3m

= unut:  ;

s. pp i

( u* w = 3 u -ers= u leare %

! i l

t f

I

[

i

\  ;

Figure 14 The user indicates the site of interest and a search is performed on that site. The site criteria screen is then re presented for additional searches on other sites.

Descrictor Search: In this procedure, the user is first prompted for the descriptor phrase (or stem). The system will then display all descriptor phrases that match the input anc the user then indicates which descriptor should be used for the search criterion (Figure 15).

30

i i

1' r a j- De.t :escrasser (or stasi m i

. . . sees- ,,or .

3 s evoAccAAege i I 3 *TOAOLMY I

j l .  ! *YOnget:3 i

j tw 4ererence ausser af 3estm 3ese** ster i

! i 1 1 3 i e 4

l 1 i

)

i i

J L- )

Firre 15 4

1 1

After each criterion is satisfied, the system returns to prompt for I

j another descriptor phrase. Wen all searches are completed, the user .,

),

enters a "Q" to return to the search option screen.

t i

i 1

i Title Search: This procedure does a string search on all the i

j words in the title field of the issues that satisfy the user input.

! The input need not be a full word because the search will be satisfied  !

} when the system finds a string of characters in the title field that i

j matches the input string. The match may be found in the beginning of

{ a werd, at the end of a word, or embedded within a word. Uppercase j and lowercase characteristics of data will be ignored by the system J

ti for both the input string and the contents of the title field.

i ,

) Statement Search: This procedure will search the statement i 4

i 1

data fields in the same manner as a title search.

I i

l' 3.4.4 Extended Search Features

/.

I j As each search function .is completed, the system returns to  !

j the Search Parameters menu screen, which recognizes that the user has t

31 l

1 4

4 y e ,.-,.-,,..-.-.,wr.. , ,p-,,,--,w-,.,,pc,. --ve-, ,. %..,ww---e.py.,_ -%,,, . , . . _ ,. -y - w.. -,-gm.m,-e-m-__,c.,,.,,wgew,-w&www

! l generated a search subset. The menu screen is modified to include the number of issues that have satisfied the search and lists two additional options (Figure 16). i i

i

( 3 1 l .

i *

! .. speci a.msetts i ,

. t. si . ,

. >m .

=

s. : .

se,. 'StsPt .

. p 4e...itiai.,t at re .

Neo are 3 ascent settityW a seevious neerts.

4 I

tn w w .P : a w , a %i. %, t t

4

'\

1 J Figure 16 l

i Display Issues Feature: As the user proceeds through the i

t search options, the -only thing the system retains is the accession numbers of the issues that have satisfied the search criteria. This option allows the user to print out portions of the data base for 1

review.

4 I

i As indicated, each of the data fields will be filled in

, acccrding to the data content of the issue. If there is only one line in the title , for instance, only one line will be printed. If a field j is blank in the issue, the system will generate dashes. Because the search options can be entered in any order, the user can perform a j search and then display the issues captured so far, review them, and then return to a search function to further eliminate the issues that i

are not of interest. The display feature will allow display on the i

i screen only, or,on both the screen and the printer.

32 4

f I

i

- - - , < - , - - - e, n,,r y eg - , - , - --+-~a---.~,-----g .,~.----=-r,-,,yv,- , , - , -,- w e -r-, ---------w,s. - - - - - . - , - - .w-n-y - nenn-- --m

d Reinitialize Option: This option eliminates the current subset of issues from the system in order to start a new search strategy. If a search has been initiated and the user then leaves the I

system, the subset remains in the system so that it can be continued.

Therefore, one must either reinitialize before signing off the system or reinitialize wh'en starting a new search.

In addition to the display feature included in this option, the subset of accession numbers are preserved and passed to the " Print an Issue" option of the main menu. Invoking this option will print the entire set of issues in the " ISSUE DATA FORMAT" discussed next. ,

4

) 3.4.5 Print an Issue This option is designed to print the IDF for any issue in the i

system. The user has the option of entering an incividual accession number or indicating that there is a list of accession numbers in the system as a result of a search. For an issue, all data currently residing in the system will be included on the IDF. If there are no r

data for a particular field, the system will print the field titles and supply dashes for the field length. The IDF is automatically generated when an issue is introduced to the system and should be generated after any data changes have been made to an issue.

3.4.6 Generate a Report This option allows the user to select from a menu of specific reports that the system can produce. Each report will be preformatted

anc have a standard set of hierarchical sorts built in. Reports will
be designed as management summary reports, staff information needs reports, and reports that are available to the public. As the system i

matures, format changes can be implemented and new reports can be '

designed and included. The preliminary formats for the initial set of reports, included as Appendix C, will include the f ollowing.

33 i >

1

Issue Accession Report: This report will contain two main sections. The first section will be a listing of all issues in the system, sorted by their accession numbers. All information pertinent to an issue will be included. The second section will consist of a listing of the issue title and accession number indexed on Site, Branch, and Descriptors.- The descriptors index will consist of an alphabetic sort of each descriptor phrase and the issues that have been assigned that descriptor phrase. It is intended that this report be used as a cursory look at the issues in the system to determine the type of issues currently defined, or as a preliminary search ' f or redundancy without having to go to the data base system.

Site Su= mary Report: This report will summarine for each site the total number of issues that are duplicate, active, or resolved; the number of issues initiated in the reporting period; the number of issues resolved in this period; and the number of issues that have milestones that are overdue. Each site vill be further broken down by sections or disciplines. The totals for each category also will be included.

Action Recuired Summary Report: This report will list, in the first section, the accession numbers and titles of all issues for which the due date of a milestone has passed. The second section will include all issues for which action is required within the next reporting period.

3.4.7 Ad Hoc Oueries This option, when invoked, will terminate the IMTS system and return to the host DBMS. At this point the users, the 1A staf f, have available all functions and capabilities of the host system. All data files can be accessed and special ac hoc searches and reports can be generated. This option also accommodates all maintenance functions, redefinition of cata fields, and global data changes. To take full 34

l advantage of this option, the users must be well versed in the host system and computer systems.

i 3.5 DATA VALIDATION 2

Because all normal input into the system is controlled by the system software, the system also can be developed to monitor the various data fields. All data fields that require the input to be upper case, such as the name of an organization or an individual's name, will be changed internally. All data fields can be checked for the correct format, and explicit instructions can be given to the user to input the data in the correct form. As each of the input data screens is completed, the system will present the data to the user for verification. If changes are required, the user can so indicate and recycle through the screen before it is accepted by the system to update the files. Data integrity also can be preserved by having the system present to the user data currently available, such as discussed previously under entering descriptor phrases. If a term is currently t

in the system, it need not be reentered, thereby avoiding input errors.

3.6 SYSTEM MAINTENANCE

(

Essentially, all system maintenance functions are external to the IMIS. Those functions involve maintenance of the sof tware i procedures monitoring of the data files, redefining the data files (if l l

necessary), generating new reports, etc. This capability is a i

function of the resident DBMS and available to the data base  !

administrator.

i t

i i

[

33 ,

1

m - .-

h O 4

1 APPENDIX A.

ISSUE DATA FORM

and IMIS DATA FIELD SPECIFICATIONS l

4 A-1

l

?

a i ISSUE DATA FCRM

}

} Ac=ession Number: (System Assignect  !

I 1

I

Title:

4 l (209) 4, I

snur=e:  :

1 seu,.e sate: _/_< _

I l Originator: Indivicual ___ Organization NRC Staff (check onel l Name: Titie/ Chapter:

l Address: Aff11/

Contact:

i Phone Number:

1 1

Site
tcheck onel l t sW:R ___ l'

] NNWS!

j 3RFC _

j Geneate

} Cther: Specify Loc (Name, County, State) i 1 i WCste Type: Icheck one) Licensing Stage: (check one) 1 HLW ___ ,

31te Characterization i LLW Construction *

. l J UR Operational j ACsignment:

Lead Branch
Resciution Reg. Dy: __/__/__
Lone Section
Priority: 1 234 5 j Staf+ memoer: Date Assignee: _./__/__

i

! Date Initiated: __/__/__ Date F.ntered: System Assig i

Statement: 3 i '

i I

1 1

4 4 t

)

  • I i  ?

i

! [

I i (toes Desc.=tst=rs: I i

Date Last Revised: System Assig.

A-2

?

.. - - - - . . _ = . _ . . _ - . - . - . - . - . . - . - - - _ . . _ _ _ - - - _ - _ - __- .

i * -

t 1

1 l I l Issue Relatec In4cemation: Issue Status: '

l Associatec DCE Werk Element (s): Duplicat'e 3 i i

Aescciatet NRC Weau Plan Nets): Actave A l Acclicaele OFR Citations: Resolvec R r l

i

=comen :ssues Accession Nes:  !

Pacing Issues:

i i  !

]

Action Requirec +ce Resciution: Baseline Current Actual  ;

j. ______________________________________________________________________

I __/__/__ __/__/__ __/__/__

4  ;

1 4 __/__/__ __/__/__ __/__/__ l

! __/__/__ __/__/__ __/__/__ .

I e i i-j i

Ourrent. Status: (

1 i

i  :

i

)

'l 1

I i  !

l ,

i

i. .

l (704) t 1  !

u  !

i  !

j

~

Physical Accessicn l Re4erencee Decuments Lccaticn Nuncer [

, _______________________________________________________________________ t i

L i

r i i

k i (Sol (8) 1113 l 1

t I {

f I  !

I

) ;

I<

f j i I

I i

l i

i 3

I Oate Last Revised: System Assig.  !

l. -

i

\ \

! A-3 i t i  !

1 IMTS DATA FIELD SPECIFICATIONS ACCESSION NUMEER (system afsigned) l Will provide historicpl record (Julian date and sequence on a

, day). Every issue wisl receive, regardless of decision to track l or not track. This is the link between files.

TITLE Brief issue title indicating the subject of the issue.

ORIGINATOR Specifies whether individual or organization. If individual, field includes name, adoress, title (if any), affiliation (if any), and phone number. If organization, field includes

! organization name, address, chapter (if any), contact (e .g. , name

( of Person sending letter), and phone number. If NRC staff i

originator, field will include NRC division as name, branch and section as chapter, staff member name as contact, and phone number. All names will be provided last name first.

SCUACE Letter, workshop, teleconference, meetings, etc.

SOURCE DATE I Date of workshop, teleconference, etc., leading to issue.

I SITE Site to which issue applies, or generic if issue applies to all sites. For BWIP, UUWSI, and SRPO, site location will be computer provided. For "other" sites, site name, county, and state wil. be entered on data form.

l l

I 1

A-*

.. .. _ ~.- - . . - _ . . . - - _ _ . . . - . . . _ - . _ - - _ _ _ . - . _ _ - ~._. -

1 i

1 ' WASTE TYPE

, Indicates HLW, LLW, or UR.

i l

LICENSING STAGE j Indicates stage to which issue applies--site characterization, j
construction, or operational. ,

! i ASSIGNHINT Indicates the primary branch, section, and staff member i responsible for resolving the issue.

1 1.

RESOLUTION REOUIRED BY Date by which resolution is required. Must take into account

{ priority and pacing issues.

)

PRIORITY

) Indicates priority on a scale of 1 (highest) to $ (lowest).

Priority is expected to take into account critical path consideration as well as ease of and time required for work toward re s olut ion .

j l

j DATE INITIATED i

{ Date Issue Data Form is sent forward.

}

DATE ENTERED (system assigned) 1 Date the issue is entered into the IMTS.

}

! 1 1

STATEFENT i l Explanation of or rationale for the issue.

1 i

DESCRIPTCRS I

4 i Key words or phrases (separated by semicolons) suitable for

! se arch ing .

i I

q 4

A-5

ASSOCIATED DOE WORK ELEMENTS Indicates applicable DOE work element numbers, if any. Will indicate N/A if none available or applicable. This field is for information only.

ASSOCIATED NRC WORK PLAN NUMBERS Every issue must be associated with one or more work plans; the achievements of which will result in resolution of the issue. N/A in this field will indicate that none exists initially.

P APPLICAELE CFR CITATIONS Ary CFR parts addressed by the issue will be indicated, as in much detail as known, e.g. ,10 CFR 60.122(c)(6).

COMMON ISSUE (S)

Accessien numbers of all other, known similar issues.

PACING IJSUE(S)

Accession numbers of issues that must be resolved or on which work must be accomplished before this one can be addressed.

ISSUE STATUS Indication of broad status--D (duplicate), A (active),

R (resolved).

ACTIO!P REOUIRED FOR RE 3OLUTION Specific actions required to resolve this issue incluaing plans for workshops, data reviews, research (NRC or DOE), and position papers. Must be correlated with work plans. Baseline is initial date of expected completion. Current is present date of expected completion (action slippage or acceleration will be the dif ference between baseline and current). Actual is date of completion.

A-6

~ _ _ _ _ __ _ ___.-_ __ _ _. _ _ _ _ _ _ _ _ . . _ _ _ _ _ - _ _ . . _ . . _ _ . . _ . _ _ - -

. f 1 +

i f CURRENT STATUS

  • i Brief statement of recent accomplishments and communications [

i (including those with originator) regarding resolution of this  !

4

! issue. Final entry will cite the action enat resolves (closes) issue.

T f k

REFERENCED DOCUMENTS --

l Complete citations (title, including document I.D. No., author (s),

physical location (in DWM) and accession number) for all documents

] used to aid in resolution of this issue.- Final entry will be the document (rule, position paper) that certifies resolution.

t

{ DATE LAST REVISED ( system assigned) i l

Indicates date latest revision made in the IMTS. Appears on all ,

j pages of the IDF.

f l

> t "ATA ENTRY CLERK IDENTIFICATION  !

! c l Internal record for quality control. Provided at initial entry {

(

] and each time information is added to IDF.

l j ISSUE ADMINISTRATOR CERTIFICATION j Internal record for quality control.

f b

j .

IRB CERTIFICATION ,

i -

1 j internal record for quality control. IRB chairperson initials l form signifying concorrence. The final step before data are t I

i considered official and valid for public consumption.  ;

! l i l i ,

t I

i t l  !

l 1

A-7 fi

1

r1 --J+*e-ha--e4 4- 4h==M45Ehaa-4*- *- 4--M M-h- --**W-6 * -M,---*1- A*i4 ^& *4M--*0-44------e*A++v --e--h 4-*--h--AA'-~'44--AA'M"+$J4 4 +n4----+ --+ =-+-*u--* - - - +4 " ' -M*44+4 ha-j e e 1 (

j  !

a >

I i

$ o I [

J

.i

)

i.

i I

I i

APPENDIX B.

i j DETAILED FILE STRUCTURE l l i, i

t I

l  !=

i t

4

$ l i I 5

t I

{

} i J.

i  !

1 I i i

". i i

i l 4

I

)

t t

i f i

i e i i

I h i

I

(,

i [

t I

t-1 1

I I

l 1

l Structure for database : ISSUE.0BF Field Field name Type width Description 1 ACCESSION Numeric 6 Unique numoer assigned to each issue.

2 ORGANCD Character 10 Code numoer to interface wita :ne names and address of an Organi:ation.

3 INOCD Character 10 Code numoer to interface witn :ne names and aodress of an Individual.

4 NRCCD Character 10 Code numoer to interface wita :ne NRC Staff Member as Originator.

5 ENT DATE Date 8 Date issue entered into ne system.  ;

6 INT 0 ATE Date 8 Date issue aas originated.

7 REVI DATE Date 8 Date of last revision to an issue.

3 SITE ~ Character 10 Site Acronynm. l 9 SITE LOC Character 20 Site location - County, State.

l 10 WSTE T'fPE

, Cnarac:er 6 Type of waste - Hign Level, Low Level

' or Urainium Recovery 11 NRC SRNCH Character 17 Lead branen responsible for resolution.

12 SECTICN Character 17 Lead section of resonsibility. i l 13 TSTMSF Character 17 Lead staff memoer of resconsibility.

I 14 ASSIG 0*E Date 8 Date issue assigned to staff memoer.

I 15 STATUI Character 1 Issue status flag:

I = Initial

' A = Active (tracked) 0 = Duplicate R = Resolved.

16 REO RES OT Date 8 Date that resolution is recuired by. '

17 PRIURIT7 Character 9 Priority rating 1-5 highest to lowest.

13 LIC_STGE Character 21 Licensing stage:

Site Characteri:ation, Construction er Operational.

19 00E WE Charscter 25 00E wort elements.

20 NRC aP Character 25 NRC work plan.

21 PACE _ISS Character 25 Pacing issue. An issue that must be resolved before this 1:, sue can ce addressed.

22 CFR CIT Character 25 Acolicace CFR citation.

23 CM'_ISS Charsc:er 25 Accession Numoer of :ne issue. :na: is being tracked anica anen resolved will resolved nis issue.

2A ENTERIO Charscter 3 Data clerk's initials.

    • Total ** 323 l

B-2 1

1 - -

i i

{

Structure for dataease : TEXT.0BF Field Field name Type Width Descriction ,

1 ACC Character 6 Accession Numeer commen to main file. [

' 2 ORG DATE Date 8 Date of the criginal source.  ;

} 3 SOURCE Character 64 Source of issue, letter EA etc '

! 4 TITL1 Character 64 Three lines for the issue title i

! 5 TITL2 Character 72 (209 characters).  !

! 6 TITL3 Character 72 I

{ 7 STMT1 Character 60 Fifteen lines for issue statement 8 STMT2 Character 72 (1069 characters). l 9 STMT3 Character 72 10 STMT4 Character 72 l 11 STMT5 Character 72  !

12 STMT6 Character 72

! 13 STMT7 Character 72 i j 14 STMT8 Character 72 2

15 STMT9 Character 72 16 STMT10 Character 72 l 17 STMill Character 72 l 18 STMT12 Character 72 i 19 STMT13 Character 72 t 20 STMT14 Character 72 l I 21 STMT15 Character 72 i

) " Total " 1358 l l l

)  !

i 4

Structure for database : CSTS.CBF  :

1 Field Field name Type Wid:n Description  ;

) 1 ACC Character 6 Accession Numeer commen to main file.  !

! 2 RCDTE Date 8 Date of entry. l

} 3 LNE1 Character 56 Ten lines to record current status.  ;

1 4 LNE2 Character 72 (704 characters) l 5 LNE3 Character 72  !

6 LNE4 Character 72

7 LNES Character 72  ;

( 8 LNE6 Character 72 l 1 9 LNE7 Character 72 l

i 10 LNES Charseter 72 11 LNE9 l J Character 72  ;

i 12 LNE10 Character 72

" Total " 719 l

J i

I

l B3 1 I l

1  !

Strue:ure for catabase : NAMES.DSF Field Field name Type Wid:n Descrio: ion 1 NAME Character 25 Name of one originator, last, first mi.

2 LINEl Character 25 Title of the originator (optional).

l 3 LINE2 Character 25 Street address 4 LINE3 Character 25 City, State, :10 code 5 LINE4 Character 25 extra line for adcress 6 LINES Character 25 Affiliation 7 LINE6 Character 25 Phone numoer

" Total " 176 Strue:ure for catabase : CRGAN.0BF Field Field name T/ce Widtn Descriotion 1 NAME Character 25 Name of :ne Organi:stien 2 LINE1 Character 25 Chapter or eranen.

3 LINE2 Character 25 Street address a LINE3 Character 25 City, State :10 code

! LINE4 Character 25 Extra line for acdress 6 LINES Character 25 Point of contac:

7 LINE6 Charactitr 25 Phone numoer

    • Total ** 176 Structure for ca:acase : NRCST.08F Fiele Field name Tyoe Width Descriotion  !

1 NAME Character 25 Name of tne NRC stafe memoer initiating the issue.

2 SENCH Character 4 Srsnch of the staff memcer (a je..er acronyrm) 3 DHCNE Charact!r la :none nuncer :p :ne 5:3f, meen,,

" Total " aa 1

1 3=d

Structure for datacase : OSCR.08F Field Field name Type Widtn Description l

I 1 REF Numeric 10 Referance num:er for cescrio: r phrase.

WORD Character 50 Descrictor nrase.

    • Total ** 61 Structure for database : XREF.DBF Field Field name Type Wicth Description

{  ! REF Numeric 4 i Referance numcer of descriptor 2 ACCNO Character :nrase in DSCR.0BF.

6 Accession Number of issue for

    • 70:31 ** the descriotor Unrase.

11 i

i

's Structure for dataease : ML3T.DBF Fiele Field'name Tyce s Wictn Descriction i

1 ACC Character 6 2 BASELINE Cate Accessien Numbe c:mmen :: main file.

3 1

3 C'JRRENT Date Base line date of ex:ected c:moletion.

3 Carrent date of excected c:mpletien.

4 ACTUAL Date 5 LNEl 3 Actual date of c:esletion.

Character 43 Tao lines to cerine miles::ne.

6 LNE2 Character 40

    • Tc:a1 -' 114 1

l l Structure f r da:3 case : OCMT.08 F Field riele name Ty:e Wid:n Oe cription 1 ACC Character 6

! 2 TITLE Charactea Accession Numcer ::mmen c main file.

50 Occumen: title l

3 LCC Character 3 L:catien of document, 4 CACCN Charsc:er 11

    • Total ** 00cument ac:ession numcer at loca:4cn.

79 l

l l

B5

P I

e

?

L l

I l

l l

t, t

APPENDIX C. '

i

, PRELIMINARY REPCRT FORMATS ,

t l

L i

e l

t l

l '

k I

e t

k e

k l

i a

Y r

l I

r n

f t

t t

t t

l c

C-1 t I

i i

i ISSUE ACCESSION REPORT '

t 1

, SECTION I: ISSUE LIST l  ;
Accession Numcer: '

Title:

4 I

9 1

1 S:stetent:

! r

) -

r b

I

t.

Lead Section: Site: 'i Staff Memoer: NRC Wor < Plan:  ;

Revs. Date: / /_ 5:stus: (

1 Ac:1cn Required for Resolutien Baseline Carren: Actual s

1 1

/_._/ / / /_/

l NII!1 a Sse i.

[

t I

r I

i j

1 i

2 +

l i

i l

I '

a 4 .

4

)

e I

r i

i i j C-2 i i

I I

I I

i

I i

, ISSUE ACCESSION REPORT - >

j SECTION II: INDEXES t i

Partial Sample of Incex Format '

I i

I I

t t

[

Site Index 1

BWIP j iitle of every issue that has a site designation of 8WIP........ 503701 '

i i

NNWSI j Title of every issue that has a site designation of NNWSI....... 503702 l SRPO j Title of every issue tnat has a site designation of SRPO ........ 504103 i  ;

i GENERIC i i i

T i t l e o f ev e ry generi c i ssu e . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510201 i

) The fermat for eacn of the inces subsections will be the same. A break j will ec ur wnen the index cnanges.  ;

In the Descriptor Phrase index.  ;

a break will occur for eacn cescrictor phrase.

a i

i f

i i

l l

4 l

1 i

l r

l i

C-3 I 1

1 l I*

l

. . 1 1

J l

5 i

i SITE

SUMMARY

REPORT t

Total to Oa:e Initiated Resolved j this this Categories Duplicate Active Resolved Period Period Overdue i BWIP j WM?C

] WMGT

WMRP

! WMEG l WMLU j NNWSI WMPC l

WMGT l WMRP ,

.l WMEG

, WMLU l

I SPRO I WMPC  ?

WMGT WMRP j WMEG WMLU l

1, GENERIC l WMPC WMGT [

t WMRP l

l WMEG ,

, WMLU l i

l OTHER j WMPC WMGT 4

WMRP -

! WMEG j WMLU j TOTALS 1'

5 f

j 1

i i

j C-4 I

l

ACTION REQUIRED

SUMMARY

REPORT Section I ACTIONS OVEROUE AS OF May 1, 1985 BWIP Accession Number: 503701

Title:

Milestene current completion date: 03/01/85 Milestene current completion date: 04/01/85 Accession Numcer: 503901

Title:

Milestene current completion date: 05/01/85 NNWSI Accession Number: 504704

Title:

Milestene current completion date: 03/15/85 Secticn II ACTIONS REQUIRED WITHIN ONE MONTH OF May 1, 1985 BWIP Accessien Number: 503301

Title:

Milestene current ccmpletion date: 05/15/85 Accession Numeer: 503302

Title:

Milestene current ccmpletion date: 05/31/85 NNWSI Accession Number: 503505

Title:

Miles:ene current ccmpletien date: mc/da/yr C-5

Retrieved from "https://kanterella.com/w/index.php?title=ML20132D255&oldid=2885436"