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 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 ZIP file containing all previous SQA documentation collected for this 5 months after start of 1.1 task project 5 months after start of 1.1 A tabulated list of all SQA documents contained in the ZIP file project 10 months after start of 1.2 Draft TLR on Previous SQA and V&V Assessment project 2 weeks after receiving 1.2 Final TLR on Previous SQA and V&V Assessment comments from COR 6 months after start of 1.3 FAVOR User KM Workshop Outline project 6 months after start of 1.3 Outline for the FAVOR KM User Manual project FAVOR User KM Workshop supporting materials (slides, other visual 15 months after start of 1.3 aids, and hands-on exercises) project 15 months after start of 1.3 Draft FAVOR KM User Manual project 1 month after receiving 1.3 Final FAVOR KM User Manual comments from COR 1 week before knowledge transfer Materials developed for Developer KM Workshop, including slides, 1.4 session, and no later other visual supports, and any hands-on activities than 24 months from the start of the project Written responses to NRC staff questions about FAVOR and related to 1 week after receipt of 1.5 the development of the SRD for FAVOR a question from COR 1.5 References used to develop the responses to NRC staff questions 1 week after receipt of 4
NRC-HQ-25-14-E-0004 NRC-HQ-60-17-T-003 M0006 Subtask Deliverable Estimated Due Date a question from COR 1 month after receipt of 1.5 Reviews of the draft SRD, using tracked changes in MSWord draft SRD 1 month after writing 1.5 Draft written sections of the SRD as directed by the COR assignment by COR 2 weeks after receipt 1.5 Revised draft sections of the SRD comments from COR 1.6 Review of the IV&V plan, with tracked changes and comments in 1 month after receipt of (OPTION) MSWord the IV&V plan 1.6 Written answers to written inquiries generated by the FAVOR IV&V 1 week after receipt of (OPTION) Group, relating to the IV&V effort inquiry from the COR Draft analysis matrix with loading conditions, WPS models, and all 12 months after start of 2.1 other conditions pertinent to the analysis project Final analysis matrix with loading conditions, WPS models, and all 2 weeks after receiving 2.1 other conditions pertinent to the analysis comments from COR 18 months after start of 2.1 Draft subtask 2.1 TLR project 1 month after receiving 2.1 Final subtask 2.1 TLR comments from COR Modified FAVOR code that allow for WPS modeling (source and 18 months after start of 2.1 executables) project 18 months after start of 2.1 Updated FAVOR Theory and Users Manuals, as applicable project 18 months after start of 2.1 Input decks and FAVOR outputs for all subtask 2.1 analyses project Draft analysis matrix with loading conditions, clad residual stress 18 months after start of 2.2 models, and all other conditions pertinent to the analysis project Final analysis matrix with loading conditions, clad residual stress 2 weeks after receiving 2.2 models, and all other conditions pertinent to the analysis comments from COR 24 months after start of 2.2 Draft subtask 2.2 TLR project 1 month after receiving 2.2 Final subtask 2.2 TLR comments from COR Modified FAVOR code that allow for clad residual stress modeling 24 months after start of 2.2 (source and executables) project 24 months after start of 2.2 Updated FAVOR Theory and Users Manuals, as applicable project 24 months after start of 2.2 Input decks and FAVOR outputs for all subtask 2.2 analyses project 24 months after start of 2.3 (OPTION) Draft analysis matrix with all conditions pertinent to the analysis project 2 weeks after receiving 2.3 (OPTION) Final analysis matrix with all conditions pertinent to the analysis comments from COR 24 months after start of 2.3 (OPTION) Draft subtask 2.3 TLR project 1 month after receiving 2.3 (OPTION) Final subtask 2.3 TLR comments from COR 24 months after start of 2.3 (OPTION) Input decks and FAVOR outputs for all subtask 2.3 analyses project Within Monthly Letter Status Report to the NRC: complete list of users, 20th Calendar day of 3.1 identification of new users added during the period, and significant the following month issues identified, and their resolution Within Monthly Letter Status Report to the NRC: summary of any new 20th Calendar day of 3.2 reports received that month and documentation of their entry into REAP 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 1 month from award of 3.4 List of contents of the existing REAP legacy archive Modification M0003 5
NRC-HQ-25-14-E-0004 NRC-HQ-60-17-T-003 M0006 Subtask Deliverable Estimated Due Date 3 months from award 3.4 Functional REAP database and public website of Modification M0003 All digital files associated with the REAP database, web application, 3.5 03/31/2019 and website as hosted on the contractor controlled servers Written responses to IT questions related to REAP migration, as 1 week after receipt of 3.5 requested by the COR a question from COR To be agreed upon 3.5 Source code related to the migration of REAP to NRC servers when requested by COR Viewgraphs and Other Supporting Materials for kickoff and annual 1 week before the 4.1 review meetings meeting 2 weeks before draft 4.2 Draft technical paper submittal deadline 1 week before final 4.2 Final technical paper submittal deadline Draft TLR that includes analysis results and/or other information as 1 month after 5 (OPTION) requested by the COR commensurate with the issue being addressed completion of work and the needs of the COR required by COR 2 weeks after receiving 5 (OPTION) Final TLR comments from COR 20th Calendar day of All MLSR per Section F.3 of the Base Contract 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.
6