MINERnA Main INjector ExpeRiment for vA

1
MINERnAMain INjector ExpeRiment for v-A
Minerva Reviews
2

The Big Picture
Directors Trial CD 12 Review First week of Dec.
2005 (focus on the project cost and schedule)
CD0 Oct. 2005 (project cost reporting begins)
3
How much time to freeze schedule?

• Directors review first week December
• Talks completed (posted) Dec. 1
• Practice talks Nov. 28/29
• Freeze schedule for talks ??

4
The Big Picture

• Hard to report costs/project status if we
  microsoft project (MSP) schedule does not reflect
  the work to be done
• Cant really do the MOUs/SOWs until we have the
  MSP relatively accurate
• Directors Trial Review for CD1 2s Focus is on
  the MSP cost and schedule and Basis of Estimates
  (BOEs)
• Main point of the reviews is to
• Consistently define the design specifications
• and assembly process for each WBS (how many
• and where they go) 80 there?
• Put this process and the associated costs/labor
• in MSP 70 there?
• BOEs go in the notes field in MSP or on a
  separate
• BOE form (use the BOE form for tasks gt10K)
  60 there?
• Get appropriate milestones into MSP xx there?

n
5
Review Status

• Table of WBS, name, review 1 date, review 2 date
  (final) and put in color green complete, red to
  go and big stars to schedule

6
Review talks morph to Directors Review Talks

• We all need to have a uniform template for the
  Directors Reviews talks.
• Cost, schedule, resource tables etc. extracted
  from MSP will be provided to each L2 to put in
  their talk.
• One talk per L2?
• Talks to cover
• Name, overall cost (total 7 MS vs. SWF)
• Scope of system (what your system is in one or
  two pages)
• Specifications for your system (what drives your
  designs)
• Cost and schedule drivers
• NuMI baseline template? Show?
• Pretty pictures of progress and what you have
  done so far.
• Doesnt hurt to make your internal Design/Cost
  Review talk to have most of these elements such
  that it will not be too much work for you to make
  your Directors Review Talk.

7
MOU/SOWs

• Table of Univ. then FY05, FY06 need MOU/SOW
  (order I will do/dates?)
• So much has changed in MSP, need new MOUs for
  FY06
• Need to determine those tasks in FY05 SOW
• Not done in FY05, but will be done in FY06 (need
  not to put in FY06 SOW)
• Done in FY05, but not in FY05 SOW (need to put in
  FY06 SOW)
• Need to make MSP reflect reality with these tasks
  and what was done in FY05 (and will be done in
  FY06)
• I will draft MOUs/SOWs for everyone but Rochester
  which Kevin will do (thank god as that is the
  most complicated one!)
• I can not do this until you have put into MSP the
  work you did in FY05 and plan to do in FY06
• We have to extract the tasks from a pretty
  accurate MSP schedule or we cant keep track of
  costs/invoices and progress. CD0 is upon us!!!
• You will need to review what I give you and make
  corrections asap (if you want the money asap)

8
Invoicing Cost Reporting

• Money in your FY05 SOW for work that you did not
  complete in FY05 will not go away, we just need
  to make sure we dont double-count it in the FY06
  SOW
• Suzanne has in the FY06 MOU
• The MINERvA group at Institution will invoice
  all MINERvA-related expenditures in each item of
  work by Work Breakdown Structure (WBS) category
  on monthly basis through the appropriate MINERvA
  Level 2 Manager to the MINERvA co-Project
  Managers. The MINERvA group at Institution agrees
  to furnish complete documentation of the quality
  control and performance checks.

9
Invoicing Cost Reporting

• The sooner you get MSP updated, the sooner we can
  get your MOU/SOW going.
• Monthly reporting has started (CD0 in October).
• Report at L2 (thus 1.2, 1.3.3.1, 3.2, etc) with
  a few words on status of each WBS at that level
• TJ will be giving you a MPS output with WBS tasks
  and you will have to status them each month (
  complete and update start and finish times as
  necessary)
• In monthly reports you should report any cost or
  schedule concerns you have in order to give us a
  heads up
• If something goes over the cost in MSP, you need
  to let us know. The threshold for when you need
  to do a change request is being determined.
  (amount????!!!!!)

10

• Oct. 2005 need to draft documents
• CDR (have, move to TDR, Jorge)
• Preliminary PMP, PEP (have Dave B.)
• Baseline Resource Loaded Schedule
• Preliminary Hazard Analysis Report
• (Mike Andrews)
• Value Management Document (need)
• Draft Configuration Management
• Document (need)
• Acquisition Strategy Document (need)

• March 2006 documents done
• Preliminary Design (TDR)
• Baseline Cost Estimate Resource
• Loaded Schedule
• Final PMP (PEP approval 12/05)
• NEPA Approved Safety Documents
• Final Design Procurement Packages
• Final Configuration Management Doc.
• Updated Value Management Document

11
Documents to be working on now

• CDR (have, move to TDR, Jorge)
• Preliminary PMP, PEP (have Dave B.)
• Baseline Resource Loaded Schedule
• Preliminary Hazard Analysis Report
• (Mike Andrews)
• Value Management Document (need)
• Draft Configuration Management
• Document (need)
• Acquisition Strategy Document (need)

n
12
L2 Project Work

• MSP Update MSP with TJ ASAP!!!!
• Design/Cost Review Schedule your final
  Design/Cost review with Nancy (before mid-Nov,
  after that it will be too late.)
• Address comments/recommendations
• Basis of Estimates Write BOEs for tasks with
  10K or more base cost
• MOU/SOW
• Check template on reviews page with your
  university, is it OK?
• When you get a draft MOU/SOW from FNAL,
  read/update it quickly and get it back to
  Nancy/Dave B.
• Monthly Report Do your Monthly reporting (first
  week of every month).
• Monthly Status also around the first week of
  every month (now on)
• Change Requests if costs are not as specified
  in MSP, over a certain dollar amount, you will
  need to get approval (a Change Request, CR)
• Then there is the real work.