ML20207F831
| ML20207F831 | |
| Person / Time | |
|---|---|
| Issue date: | 03/09/1999 |
| From: | Pool S NRC OFFICE OF ADMINISTRATION (ADM) |
| To: | Rodriguez E PURDUE RESEARCH FOUNDATION |
| References | |
| CON-FIN-W-6749, CON-NRC-04-97-046, CON-NRC-4-97-46 NUDOCS 9903110338 | |
| Download: ML20207F831 (8) | |
Text
A 4
2 u:
,5 w
L
_w A
3+4.--Ag sa L4
.m a
a m
T>c0 y
1 UNITED STATES g
j
' NUCLEAR REGULATORY COMMISSION f
WASHINGTON, D.C. 2008H001 e% *****/
MAR 59 NH Purdue Research Foundation ATTN: Ed Rodriguez 1021 Hovde Hall, Purdue University
)
West Lafayette, IN 47907-1021
Dear Mr. Rodriguez:
SUBJECT:
MODIFICATION NO. 4 TO TASK ORDER NO. 2 ENTITI 'cD "MODULARIZATION OF TRAC-P" UNDER CONTRAC,T NO. NRC-04-97-04S in accordance with Section G.4, Task Order Procedures, of the subject contract, this letter definitizes Task Order No. 2 Modification No. 4. Lis effort shall be performed in accordance with the enclosed Statement of Work.
The period of performance for Task Order No. 2 is changed to run from September 30,1997 to November 30,1999. The tota' estimated cost for full performance of this task order is increased by $423,445 from $755,510 to $1,178,955. (The $257,001 decrement in the subcontractor's cost proposal has not i,een applied to the proposed $423,445 cost to complete because task 7 of this task o' der has been postponed at this time, but not deleted from this task order.)
i
$150,477 in incre;nental funding is hereby allotted to Task Order No. 2. This action changes the total cumulativr. funds obligated for performance of this task order from $755,510 to $905,987.
l The Contractor shall not incur costs for this task order which exceed the cumu'ative obligated amount of $905,987. All other terms and conditions of Task Order No. 2 remain unchanged.
Accouriting data for Task Order No. 2 is as follows:
B&R No.: 96015110105
' Job Code: W-6749 n
9 BOC Code: 252A V
RES ID: RES-C99-377 Appropriation No.: 31X0200 Amount Obligated by This Action: $150,477 FY 97 Obligated Amount:$ 162,000 FY 98 Obligated Amount:$ 300,012 FY 99 Obligated Amount:$ 443,975 Total Cumulative Obligations:$905,967 -
l s
m,.
9903110338-990309 PDR CONTR NRC-04-97-046 PDR l
l Purdue Contract No. NRC-04-97-046 Task Order No. 2 Mod 4 -
Page 2 of 2 e
The issuance of this task orrier does not amend any terms or conditions of the subject contract.
Your contacts during the course of this task order are:
i l
Technical Matters:
Jennifer Uhle, Project Officer (301) 415-6023 l
Contractual Matters:. Stephen Pool, Contract Specialist (301) 415-8168 Sincerely,
[
M-tephe ool, Con actir g Officer Contract Management Bradch No.1 Division of Contracts and Property Management Office of Administration 9
P
l MODIFICATION TO TASK ORDER 2, MODULARIZATION OF TRAC-P WORK STATEMENT
~
The contract end date shall be extended to November 30,1999.
Task 6: Intercomponent Communication Upgrade To ensure that the external component shall be incorporated into TRAC-M in a manner that will not hamper the potentiai for maximizing the parallelization effort, modifications to the "do-loops" at the component level shall be made. Essentially, wherever possible, the component loops shall be s to allow the distribution of work to different processors. This effort shallincrease the a
level of effort of Subtasks 6.10: External Component SDID and 6.12: Extemal Component Code Modifications. All deliverables associated with the External Component, delineated under Subtasks 6.9-6.12 remain the same.
Note that the originallevel of effort for Task 6 was 16 s/m for work on Subtasks 6.1-6.4 (Heat Structures, Control Systems and External Component). The revised value of 19 s/m reflects the additional effort required by this modification.
Revised Estimated Level of effort: 19 s/m Estimated Completion Date: May 31,1999 Task 7: Numerics Benchmark As a result of toth changes in staffing and in turn, the NRC development plan for TRAC-M, the numerics of the code will not be the focus of any research until an undesignated time after the consolidation effort has been completed. Therefore, the work originally designated Task 7, Numerics Benchmark, set up to identify the optimum numerical technique for incorporation into TRAC-M as a replacement for the currently operating SETS and semi-implicit scheme, shall be postponed and the estimated completion date shall be modified.
Task 9 Accumulator Component The goal of this task is to create an external component in TRAC-M that emulates the functionality of the accumulator component in RELAP5. The manner in which this component will be available to TRAC-M shall be through the interface developed under Task 6, denoted the External Component (Subtasks 6.9-6.12).
Subtask 9.1: SRD Prepare an SRD as per the draft NRC SQA plan. Once reviewed and accepted by NRC, work on Subtask 9.2 may begin.
Deliverable: letter report in both text and electronic format Subtask 9.2: SDID
_m Prepare an SDID as per the draft NRC SQA plan. This document will be a living document until the coding work of Subtask 9.4 is finalized. Therefore, the final version of the SDlD must accurately reflect the coding submitted as the deliverable for Subtask 9.4. Modifications to the SDID must be reported in the monthly progress reports and the corresponding changes must be made to the SDID on a monthly basis. These changes shall be made using red-lining and L
bolding options of the word processing package, so that these modifications will be highlighted.
l NRC will then save a clean version of the SDID once these modifications are reviewed.
(
Deliverable: letter report in both text and electronic format i
Subtask 9.3: Test Plan l
l-Prepare a Test Plan as per the draft NRC SQA plan. Once reviewed and accepted by NRC, work on Subtask 9.4 may begin.
Deliverable: letter report in both text and electronic format Subtask 9.4: Code Modification l
l Modify the code as described in the SDID and ensure its operability by following the test plan l
developed under Subtask 9.3.' The results of the testing shall be summarized in a completion report. The mod;fications that meet the requirements of the test plan shall be submitted to NRC in a format that is consistent with the NRC Configuration Control System.
l l
Deliverables: Program containing the Accumulator model, capable of communicating with l
TRAC-M via the exterior component interface.
l completion letter report l
Estimated Level'of Effort: 4 s/m Estimated Completion Date: May 31,1999 Task 10: Time Step Back-Up Procedure l
Currently in TRAC-M, the procedure that is followed when a time step back-up is required is not clearly implemented. The resulting path taken through the subroutines is torturous and does not follow the subroutine hierarchy that helps to define the code's overall structure. Additionally, when a back-up does occur, some variables that should be re-evaluated are not, causing some inconsistent time-levels in some of the var ibles. Therefore, the logic of the back-up needs to be improved and implemented in a manner that is clear to follow. The implementation shall be l
done in the most modular way as is feasible so that all operations associated with the back up are isolated in specific routines. Documentation shall also be written so that both the logic and path can be learned by other developers.
. Subtask 10.1! SRD I
Prepare an SRD as per the draft NRC SQA plan. Once reviewed and accepted by NRC, work on Subtask 10.2 may.begin.
i Deliverable: letter report in both text and electronic format L
L Subtask 10.2: SDID
,7 Prepare an SDID as per the draft NRC SbA plan. This document will be a living document until the coding work of Subtask 10.4 is finalized. Therefore, the final version of the SDID must accurately reflect the coding submitted as the deliverable for Subtask 10.4. Modifications to the SDlD must be' reported in the monthly progress reports and the corresponding changes must be made to the SDlD on a monthly basis. These changes shall be made using red-lining and bolding options of the word processing package, so that these modifications will be highlighted.
NRC will then save a clean version of the SDID once these modifications are reviewed.
Deliverable: letter report in both text and electronic format Subtask 10.3: Test Plan
- Prepare a Test Plan as per the draft NRC SQA plan. Once reviewed and accepted by NRC, work on Subtask 10.4 may begin.
Deliverable: letter report in both text and electronic format Subtask 10.4: Code Modification Modify the code as described in the SDlD and ensure its operability by following the test plan developed under Subtask 10.3. The results of the testing shall be summarized in a completion report. The modifications that meet the requirements of the test plan shall be submitted to NRC in a format that is consistent with the NRC Configuration Control System.
Deliverables: patch files for code modifications completion letter report Estimated Level of Effort: 4 s/m Estimated Completion Date: May 31,1999 Task 11: 3-D and Plenum Specific Routines TRAC-M utilizes different sets of subroutines to drive and perform the solution procedure for the one-dimensional components (pipe, valve, tee, etc.), the plenum, and three-dimensional hydraulic (vessel) components. Examples include: 1-D subroutines tfids and stbme for 1-D, tf3ds and stbme3 for 3-D and corresponding plenum routines tfptn, tfpibk and stbmpi. This approach shall be modified with the aim of minimizing such a division of functionality while still adhering to the principles of modula,ity currently followed in the code development activities.
Subtask 11.1: SRD Prepare an SRD'as'per the draft NRC SQA plan. Once reviewed and accepted by NRC, work on Subtask 11.2 may begin.
l' Deliverable: letter report in both text and electronic format f
Subtask 11.2: SDID
Prepare an SDID as per the draft NRC SQA plan. This document will be a living document until h
the coding work of Subtask 11.4 is finalized. ' Therefore, the final version of the SDID must
- accurately reflect the coding submitted as the deliverable for Subtask 11.4. Modifications to the l -
.SDID must be reported in the monthly progress reports and the corresponding changes must be l
. made to the SDID on a monthly basis. These changes shall be made using red-lining and l
bolding options of the word processing package, so that these modifications will be highlighted.
NRC will then save a clean version of the SDID once these modifications are reviewed.
Deliverable: letter report in both text and electronic format l
Subtask 1'.3: Test Plan 1
Prepare a Test Plan as per the draft NRC SQA plan. Once reviene' and accepted by NRC, d
work on Subtask 11.4 may begin.
Deliverable: letter report in both text and electronic format Subtask 11.4: Code Modification -
Modify the code as described in the SDID and ensure its operability by following the test plan developed under Subtask 11.3. The results of the testing shall be summarized in a completion l
report. The modifications that meet the requirements of the test plan shall be submitted to NRC in a format that is consistent with the NRC Configuration Control System.
i l
Deliverables: patch files for code modifications completion letter report Estimated Level of Effort: 4 s/m Estimated Completion Date: August 1,1999 Task 12: Development Error Resolution l-Under Task Order #2, the solution procedure as well as the component communication has L
been revamped in a more modularized and parallelizable manner. During these drastic j.
modifications, a number of long standing code bugs were located and corrected. It is highly l
probable that some others were introduced in these tasks and a number of other long standing bugs exist in areas not touched by this effort. Given the high level of testing thus far, these two classes of bugs can be expected to be relatively subtle, and careful interpretation of final test j
results will be necessary to locate and correct such bugs, in addition the final round of testing can be expected to reveal various modeling deficiencies and coding inefficiencies that should be
- corrected before final release. This Task is dedicated to the detection and resolution of these
- problems. Resolution reports and code modifications shall be submitted to the NRC configuration control as per the currently invoked procedures.
' Deliverables: patch files for code modifications resolution reports / dev. docs test plan and results Estimated 1.evel of Effort: 6 s/m
n l
Estimated Completion Date: November 30,1999 l
Task 13: General Momentum Source Termse; Currently TRAC-M ' oes not determine the momentum source term value once and utilize this d
value in both the stabilizer and semi-implicit momentum equations. As a result, there is j
duplication of effort in subroutines such as StbVel10, tf1ds1 as well as StbVeix, StbVely and StbVelz. This duplication of effort shall be eliminated as well as reference to components at j
these low level subroutines.
r Subtask 13.1: SRD i
Prepare an SRD as per the draft NRC SQA plan. Once reviewed and accepted by NRC, work on Subtask 13.2 may begin.
Deliverable: letter report in both text and electronic format Subtask 13.2: SDID Prepare an SDlD as per the draft NRC SOA plan. This document will be a living document until the coding work of Subtask 13.4 is finalized. Therefore, the final version of the SDID must accurately reflect the coding submitted as the deliverable for Subtask 13.4. Modifications to the SDlD rest be reported in the monthly progress reports and the corresponding changes must be rnade to the SDID on a monthly basis. These changes shall be made using red-lining and bolding options of the word processing package, so that these modifications will be highlighted.
NRC will then save a clean version of the SDID once these modifications are reviewed.
Deliverable: letter report in both text and electronic forrnat Subtask 13.3: Test Plan Prepare a Test Plan as per the draft NRC SQA plan. Once reviewed and accepted by NRC, work on Subtask 13.4 may begin.
Deliverable: letter report in both text and electronic format Subtask 13.4: Code Modification Modify the code as described in the SDID and ensure its operability by following the test plan developed under Subtask 13.3. The results of the testing shall be summarized in a completion report. The modifications that meet the requirements of the test plan shall be submitted to NRC in a format that is consistent with the NRC Configuration Control System.
Deliverables: patch files for code modifications l
completion letter report Estimated Level of Effort: 4 s/m
(
Estimated Completion Date: October 31,1999
z.:
i i
Task 14: Documentation' J A great deal of documentation has been generated under'this Task Order. NRC has reviewed l
' this work as it has been generated but has not currently incorporated these documents into the i
. code Programmer's Guide or Theory Manual. Assistance shall be provided to NRC so that L
' these documents can be merged properly (outdated information in the old Programmer's Guide i
I~
and Theory Manual identified, the proper location in the manuals selected) and when necessary, H
further documentation shall be produced to ensure that a coherent set of explanations and guidelines are contained in the manuals.
Deliverablesf documentation in both text and electronic format Estimated Level of Effort: 2 s/m Estimated Completion Date: November 30,1999 Task 15: Assessment As a means of measuring the success of the BWR consolidation activity and the improvements made to the TRAC-M code under this contract, code simulation fidelity must be assessed and l
compared to that of TRAC-B. An example report will be provided to the contractor to serve as-L an example of the information required in the letter reports generated under this task. The
. following simulations will be performed and documented as per the NRC SQA procedures:
BWR/6 Small Break on Ta29zl BWR/6 Simplified Model of MSIV w/o Scram-Steady State BWR/6 Simplified Model of MSIV w/o Scram-Transient BWR/6 Simplified Model of MSIV w/o Scram-Restart BWR/6 Large Break on Ta29xl Deliverables: Letter reports in both text and electronic fomat Input decks in electronic format Estimated Level of Effort: 10 s/m-Estimated Completion Date: November 30,1999 :
^
MEETINGS AND TRAVEL i
- For successful completion of the work required in'this contract, it is anticipated that the I
contractor shall travel to the NRC office in Rockville, MD on three occasions for a two-day.
period The contractor may propose additional travel deemed necessary for the successful L completion of this effort.J All travel shall be approved in advance by the Project Manager, be specifically performed in support of this contract ans be in compliance with Federal i Transportation Regulations.
3-1' 1
+
k
.e. I r
u
.,u
.e
~v y
y
-