First Draft of Technical Proposal - INDICO-FNAL (Indico)€¦ · • January 12th – finalize...
Transcript of First Draft of Technical Proposal - INDICO-FNAL (Indico)€¦ · • January 12th – finalize...
1
First Draft ofTechnical Proposal
Michael MooneyColorado State University
Single-Phase TPC Electronics Consortium Meeting
February 26th, 2018
2
A Step Toward the TDRA Step Toward the TDR
♦ Reminder: Technical Proposal (TP) is an intermediate milestone toward the TDR – principal focus is TDR
• Plan structure of TDR first, TP follows same structure
• TP to have nearly identical section headings as TDR, but in compressed format (approx. five times shorter)
• More information here
♦ Overall TDR Editors:• Tim Bolton
• Sam Zeller
♦ First draft of TP submitted to Sam and Tim• Today: brief overview of remainder items
3
TDR VolumesTDR Volumes
4
Overall TP StructureOverall TP Structure
5
Schedule for TPSchedule for TP
♦ Major milestones for TP:• January 12th – finalize table of contents (section
heading level)
• February 23rd – first rough draft of TP due
• March 16th – second rough draft of TP due– Drafts will be sent to external reviewers for comment
• April 13th – final version of TP due
• May 11th – TP submitted to LBNC
♦ First rough draft is submitted – now is the time to get feedback from the consortium as a whole
• Please read over draft (attached to Indico page), send comments no later than Friday, March 9th (EOB)
• First, discuss some remainder items in these slides
DONE
NEXT GOAL
6
TP High-Level OverviewTP High-Level Overview
♦ Most major material is there
♦ Missing:• QC section
• Calibration subsection in integration section
• WBS, cost and schedule subsections in organization section
♦ In total, 37 pages• Goal: 30-40
7
Points for Discussion (1)Points for Discussion (1)
♦ Need to polish up references/citations in next round• Easier to reference other chapters in TP moving forward
• Should not cite Doc DB, only external documents – interface/requirements documents? Need to address
• That being said, TP should be “self-contained” …
♦ What is our QC strategy? MSU dewars? Large-scale testing at one or more sites? Both? Need to address (in TP and in general)
♦ Calibration discussion in TP requires interfacing with Calibration Task Force
• Mike M. will serve as interface between groups
• May leave discussion for separate TP chapter
8
Points for Discussion (2)Points for Discussion (2)
♦ Tim/Sam mentioned that we should not focus on WBS or in-depth details about cost/schedule
• Instead, should have high-level discussion of “goal posts and decision points” – a very rough timeline
• Currently missing in TP, need to address this, and should include timeline for deciding between baseline and alternative option
♦ Initial text looks good, but one thing pointed out by Sam and Tim was the need to have “good introductions” for a non-expert audience
• Tried to address in system overview
• Should also address in each section/subsection – pivot to clear, non-technical explanations when possible
♦ Ensure consistency throughout chapter
9
Moving ForwardMoving Forward
♦ First draft of TP submitted, and looks good so far• Still some missing sections – will address in next round
• Needs some additional discussion in consortium, at least for QC strategy
♦ Next goal post: second draft of TP due Friday, March 16th
♦ Please send comments/suggestions about TP rough draft by EOB of Friday, March 9th
• Provides time for Mike to make updates to draft
• Sam and Tim will also be looking at draft concurrently
• As far as I know, no external reviewers involved until after second version of TP draft is in
10
BACKUPSLIDES
11
TP GuidelinesTP Guidelines
♦ Rough page length constraint is 150-200 pages for TPC Electronics section of TDR
• Factor of five: 30-40 pages for TP
♦ Given these section headers to follow if possible:• System Overview
• System Design
• Production and Assembly
• Interfaces
• Quality Control
• Installation, Integration, and Commissioning
• Safety
• Organization and Management
12
Preliminary TP OutlinePreliminary TP Outline