NCSX Web Pages  

Project | Management | Physics | Procurement | Manufacturing

NCSX FTP Sites  

Project FTP Server | Supplier FTP Server

Navigation Trail  

Engineering > Meeting Records > 12 January 2004 (SIT)

Handouts  

CD-2 Preparation Plan (Simmons)

Summary  

1.  Critical Issues  (Wayne)
The critical issues list will be used for week-to-week risk management by the SIT. Three categories of issues are defined:

  1. Requires weekly SIT attention until there is a mitigation plan

  2. Mitigation plan is in place, actions to resolve the issue are under way.

  3. Issue has been resolved, listed for historical reference.

Among the Category 1 issues, the following were highlighted:

  • Gaps and anomalies in the composite materials properties data. Urgency of this issue has been elevated by recent L. Myatt analysis calling into question previous test results.   ACTION: Brad to develop the SOW for needed testing, taking into account Myatt’s analysis.

  • A comprehensive list of modular coil and vacuum vessel final design deliverables does not yet exist. Without that we cannot assess the validity of our schedule or measure progress reliably. ACTION: Brad, with WBS 12 and 14 managers, develop comprehensive list of deliverables and schedule due dates.

  • System analysis tasks.  Demands for system analyses have grown rapidly, but task definitions, priorities, schedules, and resource requirements for accomplishing them have not been identified. ACTION: Wayne develop a plan.

  • Metrology.  There is a concern that we need more comprehensive strategic planning to identify and meet metrology requirements.  RESPONSIBILITY: Wayne.

Among the Category 2 issues, the following was highlighted:

  • Modular coil deflections.  A plan is in place with parallel paths, but needs careful watching to ensure availability of fallbacks if needed.

2.  CD-2 preparations
New developments:

  • DOE has now provided baseline funding profile guidance: flat in 05, ramping up in 06. TEC=$86.3M, CD-4 in May, 2008.

  • ESAAB will be scheduled for the week of Feb. 2, due to conflicts the preceding week.

  • The PDR--->CD2 ECP (ECP-004) is not needed for the CD-2 ESAAB; it can be approved afterward. Changes to be incorporated in ECP-004 are documented in minutes of 1/5/04 SIT meeting.

  • A second ECP (ECP-xxx) will be needed soon after ECP-004 to bring the baseline fully up to date, picking up any changes not incorporated in ECP-004. (For examples, changes resulting from detailed FY04 WAF planning and technical progress.)


A revised CD-2 preparation schedule was developed (attached). Key dates:

  • Jan. 12- GRD approved.  Responsibility: Wayne.

  • Jan. 12- Draft ECP-004 due.

  • Jan. 20- Change Control Board. (Approve revised PEP and, if possible, ECP-004)  ACTION: Bob to arrange.

  • Jan. 23- Submit ESAAB materials to Greg, including PEP,  final input to his ESAAB presentation, and any revisions to the disposition plans that might be required.

  • Jan. 29- ECP-004 ready to submit to DOE.  Draft ECP-xxx due.

  • week of Feb.  3-  CD-2 ESAAB meeting. (Exact date being determined by OFES)


A concern was raised about the plan to submit an ECP (ECP-004) which will include only a subset of the changes that the project is aware of at the time of submission.  This is being done to limit the scope of ECP-004 to changes resulting from review recommendations, DOE-directed changes in scope and CD-4 definition, and DOE funding profile changes which have been agreed to with OFES. The concern is that the project could be faulted for omitting other changes that have come to light in the normal course of execution since the PDR baseline was established. This concern is being addressed by the plan to produce a second ECP (ECP-xxx) to capture all remaining changes needed to bring the baseline fully up to date in a timely fashion. I have discussed the concern that was raised and our plan with Greg Pitonak, who concurs in our planned course of action.

3.  Next SIT Meeting: Monday, January 19, 2004 at 11:00 a.m.  Wayne to issue announcement and chair the meeting.

Summary by:
Hutch Neilson

Privacy and Security Notice

Please forward comments and questions to the Webmaster