ML20204J042
| ML20204J042 | |
| Person / Time | |
|---|---|
| Issue date: | 03/05/1999 |
| From: | NRC OFFICE OF NUCLEAR MATERIAL SAFETY & SAFEGUARDS (NMSS) |
| To: | |
| Shared Package | |
| ML20204G858 | List: |
| References | |
| PROC-990305, NUDOCS 9903290256 | |
| Download: ML20204J042 (20) | |
Text
.._
A 4
Draft Procedures Guidance Consolidation Project March 5,1999 9903290256 990323 PDR ORG NOMA
i l
Draft Procedures Guidance Consolidation Project Table of Contents 1
PROJECT DESCRIPTION AND RESOURCES:
...... 1 2
D E FI N ITI O N S:................................................ 1 A.
Th e P roce ss............................................. 1 B.
Project Manager:........................................ 2 C.
W ritin g Tea m........................................... 2 D.
R evie w Te a m s......................................... 2 1.
Pink Team....................................... 2 11.
R ed Te a m......................................... 2 3.
RESPONSIBILITIES:...............
..........................3 A.
Division Management..................................... 3 8
Project Manatsr.
....... 3 i
Broad responsibilities include:.......................... 3 II.
Specific responsibilities.............................. 3 C.
Writing Team Leader responsibilities:......................... 5 D.
Writing Team Member responsibilities:........................ 7 E.
Review Team Member Responsibilities:........................ 8 4.
G e n e ral G uidance............................................. 9 A.
Docum ent Development.................................... 9 B
Current administrative standards for consolidating the guidance..... 9 C.
Editorial lssues....................................... 11 APPENDIXA.........................................................
NUREGS PLANNED FOR DEVELOPMENT...................... :.. A 1 APPENDIXB....,.....................................................
REGULATORY PRODUCT DEVELOPMENT CENTER (RPDC).......... B 1 1.
Responsiblo Individuals:............................. B 1 A
Regulatory Product Development Center (RPDC)
Manag e r:.......................
...........B1 B
Facilitator..........
...B1 C.
Document Manager / Editor:.....................B1 2.
Uso of RPDC resources........................... B2 A
Use of meeting rooms....................... B 2 8.
Equipment.....
................82 3.
REGULATORY PRODUCT DEVELOPMENT CENTER
- Floo r Pla n.................................... B 4 APPENDIXC.......................................................
The Guidance NUREG Development Process........................ C 1 l
l 1
l 1
PROJECT DESCRIPTION AND RESOURCES:
The Division of Industrial and Medical Nuclear Safety (IMNS), has undertaken an ambitious program for updating and consolidsting all existing Division 10 guidance documents over the next three years. The project is managed by the Rulemaking and Guidance Branch (RGB). Within the 3-years, a series of NUREGs will be developed that will update and consolidate the existing guidance into subject specific documents for use by both regulators and licensees / applicants. Thereafter, guidance documents will be updated on a 3-year revision cycle. For the initial 3-year cycle, IMNS has scheduled the development of 22 licensing guidance documents. A schedule of the 1
NUREGs being developed is provided in Attachment 1. The work will be accomplished using the model and approach developed during the Business Process Re-engineering initiative commencing with the development of NUREG-1556, Vol.1, which utilized a team approach to both the development of the product, and the management review and concurrence process, using self-managed teams consisting of NRC Headquarters j
and regional resources, and when available, Agreement State personnel.
The sche jule provides an estimate of one-year duration for completion of each of the licensing guidance documents (final NUREGs). The guidance will be published in draft for a 90-day comment period, then revised and published in final. The scheduled first phase (to draft) has a duration of 5-months, and the second phase (to final),
approximately four months. The duration of the second phesc is expected to vary e
depending upon the extent of revision needed.
To assist the teams in accomplishing their task, NMSS has provided a " Regulatory Product Development Center, (RPDC)" best described as a dedicated work environment consisting of project management, team building, document management, and computer support (See Appendix B).
The 1998 budget, C-3 schedule, lists resources for this project under " Materials Regulatory Guidance Program Development" for Headquarters and each region.
2 DEFINITIONS:
The Process:
The process for developing the guidance NUREGs includes the use of self-managed writing teams, consisting of individuals from NRC's regional and Headquarters Offices, and from NRC's Agreement States. The collaborative process includes activities designed to enhance the effectiveness of the team, and includes identification of the ro!as team members fill on the team, development of specific team " rules" for effective participation, and identifies the responsibilities of each member in completing the task. A step-by step description of this process is provided in Appendix C.
I
l E
Project Manaaer:
l Functions as the central point of contact for activities assodated with the project.
C Writina Team:
A group of individuals, selected for their subject specific knowledge, who will work together to develop the written guidance document. Each team will consist of a Team Leader and three to four Team Members.
R Review Teams:
Each document is reviewed by a Pink Team and a Red Team. Review Teams consist of NRC (and Agreement State) managers or senior technical staff.
When Review Team responsibilities are delegated to senior staff, the delegativ should include the authority to concur on the contents of the document. Pink ar.d Red Teams will have defined periods of time to conduct their reviews, and willinterface as an organized team in conducting their respective reviews.
l.
Pink Team:
A Pink Team is a technical review team consisting of key managers and/or senior technical staff charged with guiding the Writing Team in developing a regulatory product. A Pink Team gives guidance to a Writing Team prior to seeking senior management concurrence and provides early adjustments to the guidance. The emphasis for a Pink Team review is on technical and regulatory issues. Pink Teams normally consist of no more than three or four individua!s, typically consisting of HQ Section Leaders, Regional and HQ Branch Chiefs, or their delegates, and when possible, Agreement State representatives. Each Pink Team has appropriate representation from the Office of the General Counsel.
II.
Red Team:
A Red Team is a management review team that consists of upper level managers from HQ and the regions. The Red Team reviews the complete document late in the development process. The emphasis of a Red Team review is on policy issues. The purpose of a Red Team is to provide parallel management review of the document and concurrence on a completed product.
Red Teams typically consist of Headquarters and Regional Division Directors or delegates. In addition, each Red Team has appropriate representation from the Office of the General Counsel.
2
3.
RESPONSIBILITIES:
Division Manaaement:
The Division of Industrial and Medical Nuclear Safety (IMNS), through the Rulemaking and Guidance Branch (RGB), has the responsibility for completion of this project.
B Prole::t Manauer:
1 Broad responsibilities include:
a.
Planning for the project b.
Developing, maintaining, and tracking the project schedule.
c.
Working closely with management to assure that appropriate resources are available.
d.
Scheduling all activities, including team members, meeting space, and equipment.
e.
Providing guidance to the Team Leader (and indirectly to Team Members) for developing the guidance NUREG f.
Monitoring the progress of the project.
g.
Reporting:
expendituies resources lessons learned licensing findings h.
Maintaining procedures ii.
Specific responsibilities:
a.
Approximately four months before the start date, the project manager prepares a memo, under Division signature, identifying the topic and starting date, requesting writing and review team
- members, a.
Approximately two months before the start date, The Project Manager; i.
Provides a brief review of the subject project to the Branch Chief, Rulemaking and Guidance Branch, including:
Topic of the NUREG Documents identified for review and possibla consolidation The project schedule Writing Team Leader and Members, Pink and Red Team Members, 3
-. -. - -. - ~... -
ii.
Contacts the Team Leader and Team members to verify l
their participation.
lii.
Provides the following to the Team Leader:
I A copy of these procedures for developing a guidance NUREG.
A list of the writing Team Members.
The project schedule (calendar).
The Team Leader reviews the schedule with the Team Members. Changes to the schedule should be negotiated before the project begins, and must be approved by the Project Manager.
iv.
Provides a detailed schedule to the RPDC manager to verify availability of the meeting rooms, equipment, and contractor support (facilitation, editing, graphics, formatting).
v.
Arranges for assignment of RITS code and TAC number for each specific guidance document.
c.
Approximately one month before the project begins:
The Project Manager will provide te following to the Team Leader:
1.
A specific use template for developing the assigned guidance NUREG provided in Lotus Notes, ii.
A subject specific Lotus Notes file containing the appropriate documents for review and possible incbsion (P& gds, TARS, ins, etc.), and a paper copy of the list of documents to be reviewed, it is the Team's responsibility to review the documents and assure that the status of each is resolved. This means that the NUREG will contain a list of those documents considered (included), and which documents have not been included. the Team must ill The current Rulemaking Status Tab!e. This Table is developed by IMNS' Rulemaking and Guidance Branch, it is the Team's responsibility to review the list of rulemakings to ensure that the developed guidance is in compliance with the regulations.
l l
1
(
i l
l iv.
When needed, the name of a Subject Matter Expert (SME) and phone number. Early discussions with this individual 4
will provide invaluable information and guidance in order to be prepared br the upcoming task.
v.
The names, phone numbers, and E-mail addresses of those individuals who will be providing services to the team (RPDC Manager, Lotus Notes database administrator, f
facilitator, etc.)
vi.
A list of those individuals scheduled to serve on Pink (technical review) and Red (policy review) teams.
c.
Time spent on th6 various guidance documents should be charged to the RITS code and TAC number provided by the project manager at the start of the project.
C Writina Team Leader Responsibilities:
1.
Confer regularly with the Project Manager to ensure the necessary support needed for the success of the project; and Provide copies of all pertinent communications to the Project Manager.
a.
Approximately two months before the first meeting:
Discusses the schedule with his/her immediate supervisor.
Ensures that the supervisor understands, and agrees to, the resource commitmen' If necessary,. sets up a conference call with the supervisor self, and the Project Manager to discuss the resource commitment.
Contacts each of the Team Members to:
i.
Review the schedule. Resolves scheduling conflicts with the Project Manager, ii Assures that each team member will be available to work on the project during the specified times. If not, contact the Project Manager.
b.
At least one month before the Team meeting, The Team Leader should:
i.
Contact team members to assure that each team member continues to be available to work on the projec'. during the specFied times. If not, contact the Project Ma 1ager.
5 l
ii.
Arrange a Team conference call with team members and the PM to discuss:
The project schedule, The start time of the first meeting, ( inform the Project Manager to ensure that all resources that are needed will be available at the specified start time),
The documents identified for inclusion in the specific guidance NUREG, Work hours, team rules, etc.
iii.
Review the documents that were identified for inclusion in the specific guidance NUREG. From a preliminary viewpoint, begin to identify those documents (or topics) that will be included in the NUREG.
iv.
Assure that each Team Member has Lotus Notes on their regular duty station computer.
v.
For Team Members who are not stationed at HQ, ensure that they know how to log onto their regular duty station computer remotely. Their local LAN administrator can provide this information.
vi.
Prepare, or have a team member bring, a sample license (on the team's subject) on a diskette to the first meeting which will be used as an Appendix in the NUREG.
c.
Day 1 of Team Meeting:
Team Leader has the following responsibilities:
1 Ensure that Team Members are aware that time spent on the guidance documents is charged to the RITS code and TAC number provided by the prcject manager at the start of the project.
ii.
Establish start times for all meeta..,
iii.
Establish when breaks and lunch can be expected to be
- observed, iv.
Request Team Mernbers commit to the following responsibilities:
Attendance at meetings Completing Tasks on time l
Adherence to team rules l
l 6
_._ _. _ _ _ ~ _ _.. _. _.
l l
l d.
Pink and Red Team reviews:
1.
Be available to participate in the review of the document to help ensure that review team's changes are clearly understood. Participation may be accomplished either by physical attendance at the review team meeting, or by conference call.
l ii.
Ensure that the Review Team's changes to the document t
are made, and notes are added to the comment section in the Lotus Notes database documenting the response, e.
Completion of Draft and Final Documents:
i.
Provide a final review of the camera ready document prior to publication.
ii.
Provide any " lessons learned" to the Project Manager after the draft and final documents are published, D
Writino Team Member Responsibilities:
a 1.
Approximately two months before the first meeting:
a.
Discuss the schedule for the project (provided by the Team Leader) with your immediate supervisor. Ensure that the supervisor understands, and agrees to, the resource commitment.
If necessary, set up a conference call with the supervisor, yourself, the Team Leader, and the project manager to discuss the resource commitment.
b.
Review the schedule. Rosolve scheduling conflicts with the Team Leader.
II.
At least one month before the Team meeting:
Team Members should:
a.
Charge time spent on the various guidance documents to the RITS code and TAC number provided by the Team Leader at the start of the project, b.
Participate in a Team conference call, scheduled by the Team Leader, with the Team Leader, PM, and other team members to discuss:
The Project schedule, l
7
i The documents identified for inclusion in the specific guidance NUREG Preliminary assignments, a
i l
c.
Review the documents that were identified for inclusion in the specific guidance NUREG. From a preliminary viewpoint, begin to identify those documents (or topics) that will be included in the NUREG.
d.
Have Lotus Notes loaded on their home station computer.
e.
Ensure that they know how to log onto their regular duty station computer remotely. Their local LAN administrator can provide this information.
f.
If assigned, bring an electronic copy of a sample license (on the team's subject) on a diskette, to the first meeting.
g.
Provide any " lessons learned" to the Team Leader at the completion of both the draft and final NUREGs, E
Review Team Member Responsibilities:
l.
At least 5 working days before the Review Team meets:
a.
Review the document on line, if possible, after notification from the PM that the Lotus Notes document is open, enter your comments into the Lotus Notes " comment" section before the review team meeting.
If computer access is not possible, provide written comments to the Project Manager at least 1-day before the review team meets.
Comments must t,e in the Lotus Notes database no later than 8:00 a.m. on the morning of the Team Review.
Ensure, to the extent possible, that the guidance reflects a performance-based approach b.
For Review Team meeting:
1.
Commit the time to review the document. Do not schedule other meetings Juring the committed time.
ii.
Be prepared to concur upon the document, or concur with the assurance of specific changes, at the completion of the
- review, l
l c
8
iii.
If the Review Team believes that the document should be j
re-reviewed before it is published, arrangements should be made before the Review Team disbands.
iv.
Policy issues, identified during the review, should be flagged for the attention of the project manager in the comments section of the Lotus document.
l 4.
General Guidance:
The guidance NUREGs will update / consolidate approximately 150 specific guidance documents (i.e., Policy and Guidance Directives),600 to 700 technical assistance requests, a number of Information Notices, and Bulletins, as well as, standard licensing conditions.
in developing each NUR.'G, writing and review teams should adopt, as appropriate, a risk informed / performance oriented approach while maintaining consistency with current regulation.
A Document Development:
The document will be developed and reviewed in a Lotus Notes database.
A topic specific template will be provided in Lotus Notes at the first team m9eting. All writing will be accomplished in the Lotus Notes database (template) provided.
The document will be formatted in Lotus Notes and printed for Pink and Red Team members, one week before the Pink and Red team meetings.
The final format for publishing will be in Word Perfect.
B Current administrative standards for consolidatina the auidance:
Ensure that there is a regulatory basis for asking for all of the info requested in the guidance NUREG under development.
For those guidance requirements that are not specifically addressed in regulatory space, but that have safety implications, add a sentence citing 10 CFR 30.34(e).
Do not include record-keeping requirements that are not supported by a regulation (include the regulation).
Cut and Paste from other draft NUREGs to keep guidance as consistent as possible.
l l
The approach should be risk informed / performance-based.
I 9
. _ _ ~. _ _ _ _ _
I Changes to the document should be shown in bold blue strikeout.
e When the document is given to the editors, there should be no text in red.
The guidance found in the existing subject documents (TARS, SRPs, P& gds, etc.) should be incorporated into the document (not referenced).
ins may be referenced if the information is broad, and applies to many licensees. When in doubt, discuss the issue with the Project Manager.
Include a list of the documents that were reviewed and reference in, or incorporated into, the guidance NUREG.
Include a list of the documents that were reviewed and not incorporated into the guidance NUREG.
The Appendices in each document should include:
A list of documents considered in development of the NUREG A Form 313 The suggested format for providing the information requested in items 5 through 11 of Form 313 A sample license Sample inspection Audit Checklist Standard License Conditions Reviewers Checklist Notifications i
e For the " Final" document, include an addendum at the end of the i
document that lists the comments received in response to the 90 day comment period, and the staffs response to the comment, Additional Appendix topics will be identified by the writing team. The e
Appendices may include, but are not limited to the following topics:
Training Facilities and equipment Radiation monitoring instruments Waste management Decommissioning Funding Plan and financial assurance Transportation Control, change of control, and ownership issues Radiation Safety Radiation Safety Of.'icer Training Duties and responsibilities Operating and Emergency procedures 10
[
Q Editorial Issues:
The following items have been identified by writirg and review teams as common to many of ihe NUREGs:
Use " plain" language whenever possible. Guidance for using plain language is provided in draft "A Plain English Handbook," By the Office of Investor Education and Assistance, U.S. Securities and Exchange Commission currently available through NRC's internal homepage.
When identifying a basis or reference for a subject, use
" documents"in the following order: AEA, regulations, Regulatory Guides, NUREGs, other NRC documents, standard setting groups (e.g., ANSI), then recommendations from outside organizations like NCRP/ICRP Be sure that all documents listed include title and date (e.g.,
NUREGs, Regulatory Guides, Information Notices, Policy and j
Guidance Directives)
Metrication policy is to use SI units followed by conventional units in parentheses [ e.g., X Sv (Y mrem)); there should be NO EXCEPTIONS.
The first time a unit is used, spell out the full name of the unit and give its abbreviation [e.g., XX Becquerel (Bq)). Subsequently, use the abbreviation.
Sievert, Gray, Curie, and Becquerel are capitalized becauss they are people's names; for other units use lowercase for entire word or phrase.
Elements are written: carbon-14 (not capitalized, with hyphen): C-14 (note use of hyphen)
Avoid use of the second person (you, your)
Be careful about the use of the terms " applicant" and " licensee" 11
APPENDIX A NUREGS PLANNED FOR DEVELOPMENT Volume 1:
Program-Specific Guidance About Portable Gauge Licenses, Volume 2:
Program-Specific Guidance About Industrial Radiography Licenses, Volume 3:
Applications for Sealed Source and Device Evaluation and Registration, Volume 4:
Program-Specific Guidance About Fixed Gauge Licenses, Volume 5:
Program-Specific Guidance About Self-Shielded Irradiator Licenses, Volume 6:
Program-Specific Guidance About Part 36 Irradiator Licenses, Volume 7:
Program-Specific Guidance About Academic, Research and Development, and Other Licenses of Limited Scope, Volume 8:
Program-Specific Guidance About Licenses for Exempt Distribution, Volume 9:
Program-Specific Guidance About Medical Use Licenses, Volume 10:
Program-Specific Guidance About Master Materials Licenses Volume 11:
Program-Specific Guidance About Specific Licenses of Broad Scope, volume 12:
Program-Specific Guidance About Manufacturing and Distribution Volume 13:
Program-Specific Guidance About Radiopharmacy Volume 14:
Program-Specific Guidance About Well-Logging Volume 15:
Ownership and Bankruptcy Filings Volume 16:
Program-Specific Guidance About General Licensing Volume 17: Guidance About Service Providers Volume 18:
Program-Specific Guidance About Special Nuclear Material of Less Than Critical Mass Licensing Volume 19:
Guidance About Administrative Procedures Volume 20:
Guidance About 10 CFR Part 20 Volume 21:
Guidance About Reciprocity issues Volume 22:
Program Specific Guidance About Source and Special Nuclear Material Licensing A1
~~
APPENDIX B REGULATORY PRODUCT DEVELOPMENT CENTER (RPDC) l The RPDC is a laboratory for the development of materials licensing, inspection, and rulemaking products. Managed by the Rulemaking and Guidance Branch, IMNS/NMSS, the RPDC providts a dedicated work environment which includes team facilitation, document development, and computer support. The Teams are provided the ability to work together, both within the RPDC and in distributed NRC locations. Using Lotus Notes computer software, team members may j
participate in writing and/or reviewing the same document from remote NRC locations. The RPDC is designed to support most Team needs.
j 1.
Rcsponsible Individuals::
Reaulatery Product Development Center (RPDC) Manaaer:
The RPDC manager is available Monday through Friday from 9 a.m. to 5 p.m., and can ta reached by calling (301) 415-7809.
The manager is responsible for:
1.
The RPDC physical facility, the equipment, and the computer hardware and
- software, 11.
Management of the contiact for support services, Ill.
Scheduling, direction and supervision of the contracted support staff, B
Facilitator:
Facihtation is provided primarily through contracted services. Arrangements for facilitation must be made through the RPDC manager. Responsibilities include:
1.
Team building 11.
Consensus building 111.
Conflict resolution IV.
Assisting in direction setting V.
Familiarizing the team members with tne process C
Document Manaaer/ Editor:
Document support is provided through contracted services. This support is arranged through the RPDC manager. Responsibilities include:
1.
Assisting in developing formats for the Lotus Notes database or document.
II.
Assisting in editing and finalizing the document.
t B1 l
i l
1 2.
Use of RPDC resources:
Requests for the use of RPDC rooms, equipment, or contracted services must be made by the Team Leader or Project Manager to the RPDC Project Manager, if the RPDC Manager is unavailable, requests may be made to the Section Leader, Section A, IMNS/RGB.
Requests for services must not be made directly to the contractor.
Currently, the priority for scheduling is: (1) IMNS Guidance Consolidation project, (2) rulemaking and associated guidance, (3) other IMNS projects, (4) IMPEP Teams, (5) other requested projects. These projects are scheduled several months in advance, and resources are limited. When requesting space, a project plan, including: start and end dates, the dates of the meetings, the objectives for each meeting, and the support needed must be provided.
A Use of Meetina Rooms;
- The main conference room in the RPDC is available for use by teams participating in guidance, rulemaking, and other activities that benefit from a participatory process. This room is equipped with a Polycom Conference unit and laptop computer with a docking station for group work. It may also be used for other meeting purposes on a space available basis.
Room A is used by teams engaged in document drafting. This room contains a Polycom Conference Unit; 4 computers; 4 telephones, and a laptop computer with a docking station for group work. As with the Main Room, Room A may be used for other meeting purposes on a space available basis.
If, upon request, rooms within the center are found to be unavailable to support a team on a specific day, the Team Leader is responsible for scheduling a meeting room elsewhere.
The RPDC, when possible will provide equipment. However, the Team Leader is responsible for room set-up and break down. The Team Leader is responsible for equipment that is borrowed.
- A diagram of the RPDC is on page 3 of this Appendix.
B Eauioment:
The following equipment is available for use by team members:
I Computers in the RPDC are equipped with a LAN connection, Lotus Notes software, and access to the LAN printer in the Main Room.
II.
Laptop computers, equipped with PC anywhere, Lotus Notes, and WP 6.1 are available for use by individuals participating in writing teams at HQ.
When available, the laptops may be used by other NMSS staff. Requests to borrow equipment must be made to the RPDC manager.
B2
=. - - _.
1 lil.
Liquid Crystal Displays (LCD) are available for use by individuals participating in writing teams at HQ. On a space available basis, LCDs may be used by other NMSS staff.
IV.
Vugraph machines and Laser Pointers are also availaole for team use upon request of the RPDC nanager, Individuals who wish to borrow equipment from the RPDC must make a request to 4
the RPDC Manager, complete NRC Form 466, " Property Pass," and obtain the IT coordinator's signature in advance of removing equipment from the RPDC. It should be noted that the individual borrowing equipment will assume responsibility for the equipment untilit is returned to the RPDC. All equipment removed from the RPDC must be returned to the RPDC manager by the individual borrowirg the equipment immediately following the conclusion of the purpose for which it was borrowed. No equipment is to remain in unlocked rooms.
4 B3
l 1
l l
l 3.
REGULATORY PRODUCT DEVELOPMENT CENTER
- Floor Plan i
l
, The-RPDC ~ Lab
(
i
}
e g
m,.
f Room A -#[
'/
Main Room Room B
~
p[
j Uc-T e
~
C_.D l
0
-c j
8-C-5
-X l
6 1
i i
4 e
B4 i
1
+
APPENDIX C The Guidance NUREG Development Process Week 1 & 2:
Project Kick-off: L.otus Notes Training, Team development exercises, Develop Story boards (if needed), Begin Writing, Meet with " Visualizer" for graphics Week 3:
Continue writing remotely (at "home" duty station)
Week 4:
Team meets to review and finalize the DRAFT Week 5:
The Team is " locked-out" of the document, and the document is edited.
Week 6:
The Team Leader reviews the edited document with the Team's assistance.
Week 7:
The document is finalized, authors are " locked-out," and the document is sent to ths Pink Team members for review.
Week 8:
The Pink Team meets on the Wednesday and Thursday of this week to review the guidance document. The Team Leader is present during the review.
Weeks 9 and 10:
The Team resolves the Pink Team's comments.
Week 11:
The document is edited. The edited document is returned to the Team Leader on the third day of this week for review.
Week 12:
The document is prepared and sent to the Red Team members (by COB Monday).-
Week 13:
The Red Team meets on the Wednesday and Thursday of this week to review the guidance document. The Team Leader is present during the review.
Weeks 14 and 15:
The Team resolves the Red Team's comments.
i 1
Week 16:
The document is edited. The edited document is returned to the Team Leader on the fourth day of this week for review.
Week 17:
The Draft document is finalized, and a camera ready copy is sent to Administrative Services to be published as a NUREG.
Week 18:
The document is prepared and provided to IRM to be placed on the Internet.
l An FRN is prepared announcing that the document is being published for a 90-day comment period.
At the end of S0 days the process is repeated. However, the schedule is adjusted based on the number of comments received, and the changes to the document that are needed.
I C1
THE GUIDANCE NUREG DEVELOPMENT PROCESS Schedule for 10 CFR Part 20 Guidance 6/7-6/25:
Project Kick-off: Lotus Notes training, team development e>.srcises, development of story boards (if needed), writing begins.
6/28-7/9:
Continue writing remotely (at "home" duty station) 7/12-7/16:
Team meets to review and finalize the DRAFT 7/16 Team is locked-out of the document until 8/20 8h 8-19:
The Pink Team meets to review the guidance document. The Team Leader is present during the review.
S/20-9/3:
The Team resolves the Pink Tearn's comments.
9/3 Team is locked-out of the document until 9/24 9/22-23 The Red Team meets to review the guidance document. The Team Leader is present during the review.
9/24-10/8:
The Team resolves the Red Team's comments.
10/29:
The Drafi dccument is finalized, and a camera-ready copy is sent to the Publishing Servicos Branch of the Office of the Chief Inforrnation Officer to be published as a NUREG.
. The document is prepared and provided to the Office of the Chief Information Officer to be placed on the Internet. A Federal Reaister notice is prepared announcing that the document is being published for a 90-day comment period.
At the end of 90 days the ccmments are resolved and the document is revised and published as final. However, the scl.edule is adjusted based on the number of comments received, and the changes to the document that are needed.