ML19161A040
| ML19161A040 | |
| Person / Time | |
|---|---|
| Issue date: | 06/07/2019 |
| From: | Mike Williams Acquisition Management Division |
| To: | Edelstein P Numark Associates |
| References | |
| NRC-HQ-25-14-E-0004 | |
| Download: ML19161A040 (6) | |
Text
NRC-HQ-25-14-E-0004 NRC-HQ-60-17-T-003 M0006 4
SECTION 6. DELIVERABLES/MILESTONE SCHEDULE AND REPORTING REQUIREMENTS, is deleted in its entirety and replaced as follows:
The contractor shall provide the deliverables stated in the table below in electronic format unless otherwise directed by the COR. The electronic format shall be provided using a Microsoft-based product, (e.g., Outlook, Word, Excel, PowerPoint) unless the COR and the contractor specifically agree on another format, such as PDF for example. All deliverables, with the exception of the Monthly Letter Status Report (MLSR) shall be in the format of draft version, revision version with redline/strikeout with a change-control appendix, and a revised version which shall become the final version. The contractor shall maintain appropriate version control in an electronic format. The contractor shall explicitly state in its submittal(s) that the product provided is the deliverable for Task/Subtask XX, as further described below.
The deliverables below shall be submitted to the task order COR. The COR will review all draft deliverables (and coordinate any internal NRC staff review, if needed) and provide comments back to the contractor. The contractor shall revise the draft deliverable based on the comments provided by the COR and then deliver a revised version of the deliverable, which will then be considered the Final Version. When mutually-agreed upon between the contractor and the COR, the contractor may submit preliminary or partial drafts to help gauge the contractors understanding of the particular work requirement. More than one round of drafts may be needed if the contractor does not successfully incorporate the CORs comments on the previous draft.
The contractor shall develop (as necessary), maintain, and control data, files, information, and deliverables pursuant to this task order.
Subtask Deliverable Estimated Due Date 1.1 ZIP file containing all previous SQA documentation collected for this task 5 months after start of project 1.1 A tabulated list of all SQA documents contained in the ZIP file 5 months after start of project 1.2 Draft TLR on Previous SQA and V&V Assessment 10 months after start of project 1.2 Final TLR on Previous SQA and V&V Assessment 2 weeks after receiving comments from COR 1.3 FAVOR User KM Workshop Outline 6 months after start of project 1.3 Outline for the FAVOR KM User Manual 6 months after start of project 1.3 FAVOR User KM Workshop supporting materials (slides, other visual aids, and hands-on exercises) 15 months after start of project 1.3 Draft FAVOR KM User Manual 15 months after start of project 1.3 Final FAVOR KM User Manual 1 month after receiving comments from COR 1.4 Materials developed for Developer KM Workshop, including slides, other visual supports, and any hands-on activities 1 week before knowledge transfer session, and no later than 24 months from the start of the project 1.5 Written responses to NRC staff questions about FAVOR and related to the development of the SRD for FAVOR 1 week after receipt of a question from COR 1.5 References used to develop the responses to NRC staff questions 1 week after receipt of
NRC-HQ-25-14-E-0004 NRC-HQ-60-17-T-003 M0006 5
Subtask Deliverable Estimated Due Date a question from COR 1.5 Reviews of the draft SRD, using tracked changes in MSWord 1 month after receipt of draft SRD 1.5 Draft written sections of the SRD as directed by the COR 1 month after writing assignment by COR 1.5 Revised draft sections of the SRD 2 weeks after receipt comments from COR 1.6 (OPTION)
Review of the IV&V plan, with tracked changes and comments in MSWord 1 month after receipt of the IV&V plan 1.6 (OPTION)
Written answers to written inquiries generated by the FAVOR IV&V Group, relating to the IV&V effort 1 week after receipt of inquiry from the COR 2.1 Draft analysis matrix with loading conditions, WPS models, and all other conditions pertinent to the analysis 12 months after start of project 2.1 Final analysis matrix with loading conditions, WPS models, and all other conditions pertinent to the analysis 2 weeks after receiving comments from COR 2.1 Draft subtask 2.1 TLR 18 months after start of project 2.1 Final subtask 2.1 TLR 1 month after receiving comments from COR 2.1 Modified FAVOR code that allow for WPS modeling (source and executables) 18 months after start of project 2.1 Updated FAVOR Theory and Users Manuals, as applicable 18 months after start of project 2.1 Input decks and FAVOR outputs for all subtask 2.1 analyses 18 months after start of project 2.2 Draft analysis matrix with loading conditions, clad residual stress models, and all other conditions pertinent to the analysis 18 months after start of project 2.2 Final analysis matrix with loading conditions, clad residual stress models, and all other conditions pertinent to the analysis 2 weeks after receiving comments from COR 2.2 Draft subtask 2.2 TLR 24 months after start of project 2.2 Final subtask 2.2 TLR 1 month after receiving comments from COR 2.2 Modified FAVOR code that allow for clad residual stress modeling (source and executables) 24 months after start of project 2.2 Updated FAVOR Theory and Users Manuals, as applicable 24 months after start of project 2.2 Input decks and FAVOR outputs for all subtask 2.2 analyses 24 months after start of project 2.3 (OPTION)
Draft analysis matrix with all conditions pertinent to the analysis 24 months after start of project 2.3 (OPTION)
Final analysis matrix with all conditions pertinent to the analysis 2 weeks after receiving comments from COR 2.3 (OPTION)
Draft subtask 2.3 TLR 24 months after start of project 2.3 (OPTION)
Final subtask 2.3 TLR 1 month after receiving comments from COR 2.3 (OPTION)
Input decks and FAVOR outputs for all subtask 2.3 analyses 24 months after start of project 3.1 Within Monthly Letter Status Report to the NRC: complete list of users, identification of new users added during the period, and significant issues identified, and their resolution 20th Calendar day of the following month 3.2 Within Monthly Letter Status Report to the NRC: summary of any new reports received that month and documentation of their entry into REAP 20th Calendar day of the following month 3.3 (OPTION)
Upgraded REAP web-application 08/31/2019 3.3 (OPTION)
List of development steps performed as part of subtask 3.3 08/31/2019 3.4 List of contents of the existing REAP legacy archive 1 month from award of Modification M0003
NRC-HQ-25-14-E-0004 NRC-HQ-60-17-T-003 M0006 6
Subtask Deliverable Estimated Due Date 3.4 Functional REAP database and public website 3 months from award of Modification M0003 3.5 All digital files associated with the REAP database, web application, and website as hosted on the contractor controlled servers 03/31/2019 3.5 Written responses to IT questions related to REAP migration, as requested by the COR 1 week after receipt of a question from COR 3.5 Source code related to the migration of REAP to NRC servers To be agreed upon when requested by COR 4.1 Viewgraphs and Other Supporting Materials for kickoff and annual review meetings 1 week before the meeting 4.2 Draft technical paper 2 weeks before draft submittal deadline 4.2 Final technical paper 1 week before final submittal deadline 5 (OPTION)
Draft TLR that includes analysis results and/or other information as requested by the COR commensurate with the issue being addressed and the needs of the COR 1 month after completion of work required by COR 5 (OPTION)
Final TLR 2 weeks after receiving comments from COR All MLSR per Section F.3 of the Base Contract 20th Calendar day of the following month The contractor shall submit all raw and processed data and worksheet and/or input files used in testing and analyses with the corresponding Draft TLR, and with the Final TLR, in a tabulated Excel format or other format as directed by the COR.
All other terms and conditions of the task order remain the same.