M. G. D. Gilchriese (LBNL) Interim Deputy Project Director . - CMB-S4

1y ago
1 Views
1 Downloads
1.15 MB
15 Pages
Last View : 1m ago
Last Download : 3m ago
Upload by : Vicente Bone
Transcription

Project UpdateM. G. D. Gilchriese (LBNL)Interim Deputy Project DirectorMarch 8, 2021

Who Am I Senior scientist at LBNLInvolved in scientific management and project management of DOE, NSF orboth DOE/NSF projects for last 35 years Superconducting SupercolliderATLAS@LHCDUSELLUX dark matter projectLZ dark matter project2

Outline Key Project Goals Over the Next YearProject OrganizationDesign Review PlansConfiguration Control PlansCost & Schedule Update PlansRisk Update PlansMOUs/MOAs/SOWsReportingProject DocumentationKey Project Technical IssuesConclusion3

Key Project Goals Obtain Funding Have 5M(FY21) carry-forward from FY20. Distributing.Made FY22 request. Overall DOE- SC- OHEP- CMB-S4 funding not known. Stimulus?MSIP & MSRI-1 support ongoing work through FY21Proposals to support FY22 and beyond to be submitted before FY21 endsComplete Status and Gate Reviews DOE NSF NSF-led MRSI-1 status review by about mid-May. Received charge, working on agenda.Tentative dates May 11-12DOE-led status review? Not decided but probable in summer.NSF Preliminary Design Review - CRITICAL milestone. End of CY21? Plan on this now.DOE Critical Decision 1(CD-1) Review - CRITICAL milestone. End of CY21? Challenging.Director’s Reviews will precede(by 6 weeks or so) DOE status, PDR and CD-1 reviewsMake Technical Progress Principal subject of this collaboration meeting4

Project Organization L2 under change control, approved by PDL3 well advanced, expect approval this month5

Upcoming Conceptual Design Reviews (CDRs) Design Review Policy/Procedure atcmbs4-doc-673 Describes planning/execution/closeoutDescribes Review Manager roleIncludes timeline before and after reviewReferences review report templateIncludes suggested charge and content ofreview materialsMore description at recent TechnicalMeetingsQuestions? Ask R. Besuner6

Configuration Control In process of implementing database tool - JAMA - tocapture requirements and point description(Current BestEstimate CBE) in a controlled wayJAMA training initiatedChange Control Board(CCB) definedBegin monthly CCB meetings April 7 Questions? AskR. BesunerJ. ZvickM. LeitnerStart with top-level science requirementsWork “downward”Ultimately capture CBEEstablish baseline and initiate Baseline Change ProcessGoals Establish and exercise system prior to NSF-led status reviewPreliminary baseline prior to NSF PDR and DOE CD-1This will be challenging, but necessary this year7

Spring/Summer: Update Cost and Schedule Documents ToPrepare For Potential Reviews By End of CY2021 May: NSF Progress ReviewTop-Level Schedule Guidance(Detector Frequency Dependent) Top-Level Schedule Defined Risk Analysis SoftwareImplemented Schedule Logic Improved April/May: L2/CAMs UpdateProject Detail Schedule May/June: L2/CAMs UpdateCost Estimates July: Risk WorkshopUpdateDetailed ScheduleRisk WorkshopL2/CAM TrainingUpdate Cost Estimates Aug/Sept: Cost ValidationSchedule likely to be tweaked tomatch actual agency reviewscheduleQuestions? Ask M. Leitner, J. Zivick8

A Risk Registry Database Linked To Monte Carlo AnalysisSoftware Will Establish NSF and DOE Contingency Requirements Implemented a Jira-based risk database Automated risk ranking calculation based on risk impacts Connects to Monte Carlo simulation softwareRisk Registry Implemented Acumen Risk Monte Carlo simulation software Next steps April: Prepare project schedule to run a full risk analysis workflow(project office) April/May: L2/CAMs update project schedule (L2/CAMs) May/June: Revisit and consolidate current risk entries (L2/CAMs andproject office)Risk EntryImpacted Schedule ActivitiesProbabilities of MissingSouth Pole SummerInstallation Windows(software demonstration only)Monte Carlo SimulationSoftware Interface9

MOUs/MOAs/SOWs MOUs(standard format) with LBNL Framework for potential in-kind contributions to CMB-S4 Harvard-Smithsonian: signed CCAT Prime Observatory, Inc: in progressLegal framework for work in Chile. U of Chicago: in progressMOAs(bespoke format) MOU: Memorandum of UnderstandingMOA: Memorandum of AgreementSOW: Statement of WorkDetector fab sites Intellectual Property Management: NIST concluded, rest in progressInstitutional MOAs(signed once) FY Appendix(update each FY): all institutions receivingfunds from LBNL. In progress over next few monthsSOWs Key part of contracts between LBNL and DOE funded institutionsIn progress. Driven by agreeing on technical scope and getting procurement entities engagedat LBNL(new person helping, Jessica Aguilar) and at each institutionQuestions? Ask M. Gilchriese(MOUs/MOAs)M. Leitner(SOWs)10

Reporting Regular reporting to the NSF and DOE began months ago DOENSF Quality and detail of DOE and NSF reports expected to improve as designsmature, test results come in, etc Financial reporting (specifically for the DOE but similar for NSF) Required monthly from all institutions that receive fundingExperience suggests will be painful initially but it’s essentialDown the road will feed into EVMS systemsPlease respect this reporting need11

Project Documentation Update Policy and procedures for using CMB-S4’s official document repository,DocDB, is posted to cmbs4-doc-664. Accessible using your CMB-S4credentials.Project Configuration Management Plan, defining approval and revisionprocesses for project documentation is posted to cmbs4-doc-238.Technical requirements are loaded to management tool, Jama. Project Design Review Policy and Procedures posted to cmbs4-doc-673. Still a lot of work required to update and approve requirements and interfaces.L2 Conceptual Design Reviews scheduled for May and June (dates listed here)Review Recommendations tracked in this google sheetMeeting materials and links to relevant information are in Confluence.Project CAD Policy and Procedures posted to cmbs4-doc-661.12

Key Project Technical Issues There are many, many design and technical issues to be addressed at thiscollaboration meetingKeys to moving forward with the Project are given belowScope. Is it right and can we, project management, defend it?Technical readiness pass conceptual design reviews(or better)Cost containment. Cost growth at this stage of a project is a norm. Must keepcosts(including risks) at forefront of technical development Interplay among requirements flowdown, detectors, readout and modulesManufacturability, minimize complexity of detectors/readout.think cheapFlowdownModulesDetectorsMeetings organized by B. FlaugherParallel sessions at this collab. mtg.Readout Other area of potential concern now: cost of working at the Pole, how accounted by NSF13

Conclusions Substantial progress in developing the CMB-S4 Projectstructure since August 2020 when LBNL was designated aslead laboratory Project “machinery” now coming together and will be used toprepare for agency status and gate reviews later this year orearly 2022 Formal technical design reviews for all major elements to becompleted by this summer Cost and schedule to be updated this summer Critical to advance Preliminary Baseline Design and relatedReport in time for upcoming reviews14

15

MOUs(standard format) with LBNL Framework for potential in-kind contributions to CMB-S4 Harvard-Smithsonian: signed CCAT Prime Observatory, Inc: in progress Legal framework for work in Chile. U of Chicago: in progress MOAs(bespoke format) Detector fab sites Intellectual Property Management: NIST concluded, rest in progress

Related Documents:

Lab-Wide Geologic Section LBNL Citizens’ Advisory Group, 8 July 2010. . Caldera Hypothesis Map LBNL Citizens’ Advisory Group, 8 July 2010 MW91.4 – 140’ deep, no volcanics. . Slope stability is a concern at LBNL, as it is throughout the Berkeley Hills

50 complex on the LBNL site, NERSC staff at OSF (about 70 persons), and UC Berkeley/LBNL CSE staff (about 50 persons) into the new building. Relocation of LBNL staff from other buildings on the LBNL site into the space that would be vacated by the CRD staff in the Building 50 complex. This would involve moving the offices of approximately

LBNL Earned Value Management System Introduction Revision 5.4 February 2009 1 of 56 INTRODUCTION Lawrence Berkeley National Laboratory (LBNL), a U.S. Department of Energy (DOE) national laboratory operated by the University of California (UC), uses an Earned Value Management System (EVMS) to integrate project management elements required for

The EVMS provides for effective project planning and control and is designed around the integration of technical scope, schedule, and budget with existing LBNL policies and procedures as defined in the Earned Value Management System (LBNL-EVMS) Description. The primary objective of the EVMS is to verify that all elements of a project are

RWTH Aachen - Dezember 2007 System Philosophy 4 Bro is being developed at ICSI & LBNL since 1996 LBNL has been using Bro operationally for 10 years It is one of the main components of the lab’s network security infrastructure Bro provides a real-time network analysis framework Primary a network intrusion detec

ST AR O ine Computing Requiremen ts T ask F orce Rep ort (Star Note SN0327) G. Eppley (Rice), P. Jacobs (LBNL), P. Jones (Birmingham), S. Klein (LBNL), T. LeCompte (ANL), W. Llop

Guest House 10 14 2 2 Source: Fehr & Peers, 2010. 1 As documented in the LBNL 2006 LRDP EIR and stated on page 4.11‐4, the current 4,000 employees at the LBNL main hill campus generate 5,700 daily t

automotive climate systems, today, are an integrated part of the vehicle’s comfort and safety. Over the last years, Nissens has invested a significant amount of resources in research on and development of climate system components for the automotive segment. Years of thermal know-how and manufacturing experience mean that we are able