100 likes | 163 Views
Restructure of WP4 – provisional ideas and numbers to promote discussion. Ian Wilmut . Effort estimates/distribution from start of project. This table was created by Tim at start of project This section has gone (now in past)
E N D
Restructure of WP4 – provisional ideas and numbers to promote discussion Ian Wilmut
Effort estimates/distribution from start of project • This table was created by Tim at start of project • This section has gone (now in past) • This will not happen in the planned timescale (production preparation) • These are dramatically reduced by 130nm delay • This should probably be too much given 130 delay, but is harder than expected and perhaps should be left as is.
Effort estimates/distribution from start of project • This table was created by Tim at start of project • This section has gone (now in past) • This will not happen in the planned timescale (production preparation) • These are dramatically reduced by 130nm delay • This should probably be too much given 130 delay, but is harder than expected and perhaps should be left as is.
Effort estimates/distribution from start of project • This table was created by Tim at start of project • This section has gone (now in past) • This will not happen in the planned timescale (production preparation) • These are dramatically reduced by 130nm delay • This should probably be too much given 130 delay, but is harder than expected and perhaps should be left as is.
Effort estimates/distribution from start of project • This table was created by Tim at start of project • This section has gone (now in past) • This will not happen in the planned timescale (production preparation) • These are dramatically reduced by 130nm delay • This should probably be too much given 130 delay, but is harder than expected and perhaps should be left as is.
Effort estimates/distribution from start of project • This table was created by Tim at start of project • This section has gone (now in past) • This will not happen in the planned timescale (production preparation) • These are dramatically reduced by 130nm delay • This should probably be too much given 130 delay, but is harder than expected and perhaps should be left as is.
Sources for this effort • Already some effort expected to be used in WP4 has moved to WP2 and WP6 (mostly to WP2) • Of the remaining effort we have both “engineer” and “technician” effort available. • Two “new” tasks are identified as good applications of this effort • Tracker Alignment – originally conceived as strips only but should probably apply to pixels as well • HVCMOS mechanics – If CMOS is to be pursued we should consider the mechanics of it. • We must maintain core of WP4 to make and test staves and to populate them. Whatever additional tasks we consider this is necessary. • At TUMM on Monday we agreed that Alignment would be baseline activity, but we would consider this carefully over next few months.
Estimates of effort for Alignment • Probably 0.55 + 1.76 - 0.1 - 0.1 = 1.21 FTE available from production prep (yellow) • Probably 3.53 + 3.78 – 1 – 1 = 5.31 FTE available from stave QA (Red) • Probably 4.57 + 3.78 - 1.3 - 1.3 =5.75 FTE available from Stave core assembly (green) • Hard to understand effort available form module mounting, guess 1 FTE/year = 2 FTE (Purple) • So total effort that might be available =14.27FTE (7 full time people per year) • This is artificial as: • NM tech at Liverpool will not be funded • John Morris has left QMUL • Martin died and his replacement is yet to start. • IW estimate of effort made available is 5FTE/Yr for 2 year • But…
Some people have voted with their feet already. • We need to understand these figures accurately, but my estimate is: • Graham Beck 15->20% extra now in pixels • Peter Sutcliffe 5->10% extra effort now in pixels • Stephanie Yang 20->30% extra now in pixels • Tim Jones ???? • Georg Viehhauser ???? • Total perhaps another 1-2FTE year now in WP2 not WP4 • So we might have 3FTE/Yr in WP4 available to work on Alignment/HVCMOS • I think this number is high, but then I think a lot of the figures are high.
Conclusion • 130nm delay has hammered WP4 schedule • Implication is that we have effort that can now address other areas. Alignment and HVCMOS are most prommising. • The figures above are very provisional (more to give people something to shout at) • We must not stop the remaining part of the core WP4 programme, and we do need to have new deliverables within the programme.