Long-Baseline Neutrino Facility LBNF Integration - Interfaces, Config Mgmt and Requirements Jeffrey Dolph LBNF/DUNE DOE/SC CD-1 Refresh Review July 14-16,

Long-Baseline Neutrino FacilityLBNF

Integration - Interfaces, Config Mgmt and Requirements

Jeffrey Dolph

LBNF/DUNE DOE/SC CD-1 Refresh Review

July 14-16, 2015

LBNF

Who am I? What have I done?

07.14.15 Jeff Dolph | Integration - Interfaces, Config Mgmt and Requirements2

Jeff Dolph, Principal Engineer at BNL Physics Dept.Registered Professional Engineer - MechanicalProfessional Experience:• 3 years – LBNE Systems Engineer• 2 years – Chief Engineer, LBNE Water Cherenkov Far Detector• 25 years – Mechanical Engineer - integration of major mechanical and

structural modifications:-Boeing Company-Northrop Grumman

- Consulting Engineer• 747 Special Freighter• US Marine Corps radar system

LBNF

Outline


• Integration Team• Interface Development and Management• Configuration Management and Change Control • Other Important Integration Tasks

-Requirements Development

-Value Engineering and Trade Studies

LBNF

Integration – Project Engineers and Systems Engineer


• Integration to assure complete design can be delivered within subprojects is the responsibility of the subproject Project Engineers

-Beamline: Salman Tariq

-Near Detector: Jan Boissevain

-Far Detector: Russ Rucinski, Terry Shaw

-FSCF: Josh Willhite

-NSCF: Tom Hamernik

-Cryogenic Infrastructure: Barry Norris

• Between Subprojects, this role is covered by the Systems Engineer with help from the Project Engineers & their teams

-Covers requirements, risk, interfaces, QA, configuration control

-This talk addresses interfaces, configuration control & requirements

LBNF

Interfaces between LBNF & DUNE and within Subprojects


• Interfaces are managed between major WBS elements using a matrix linked to Interface Control Documents (ICD) - ICDs define the interfaces and any parameters associated with them.

- ICDs signed by relevant managers on both sides

- ~150 ICDs expected to be developed across LBNF/DUNE Far Site and Near Site

• Matrix contains schedule for completion of interface definition

• Expect to complete by end of this year

• Highest priority is FSCF since that is critical path and needed for CD-3a this fall, to be completed by Sept. 3

• Interfaces are discussed in weekly subproject meetings that involve team members from associated subprojects - Example: NSCF engineers attend most Beamline meetings to assure

Beamline CF is being designed to meet Beamline requirements

LBNFJeff Dolph | Integration - Interfaces, Config Mgmt and Requirements6

ICD Matrices

07.14.15

• 5 matrices cover all LBNF to DUNE interfaces

-DUNE FD (internal)

-DUNE ND (internal)

-LBNF-DUNE Near Site (Beamline – ND – CF – Fermilab)

-Near Site – Far Site (alignment)

-LBNF-DUNE Far Site

• LBNF-DUNE Far Site interface documents are found on the Project Planning Documents review site linked in this matrix

https://web.fnal.gov/project/LBNF/ReviewsAndAssessments/LBNF_DUNE%20DOE%20CD-1%20Refresh%20Review/SitePages/Project%20Planning%20Documents.aspx

http://lbne2-docdb.fnal.gov:8080/cgi-bin/ShowDocument?docid=11212&asof=2015-7-14

LBNF07.14.15 Jeff Dolph | Integration - Interfaces, Config Mgmt and Requirements7

ICD Matrix example – Far Site Design/Construction

LBNF-DUNE Far Site Interface MatrixNote: Each cell will contain a hyperlinked ICD after the completion date.

Far Site Entity Design/Construction

CF, Far Site -

Surface

CF, Far Site - Shafts & Drifts

CF, Far Site -

Caverns

Far Detecto

r Design

Far Detecto

r Constru

ction

Cryostat

Design

Cryostat

Construction

Cryogenics Ar System-Design

Cryogenics Ar System

-Constru

ction

Cryogenics N

System-Design

Cryogenics N

System-

Construction

Cryogenic

Fluids SURFCF, Far Site - Surface

CF, Far Site - Shafts & Drifts 3-Sep-15

CF, Far Site - Caverns 3-Sep-15 3-Sep-15

Far Detector Design 24-Jul-15 24-Jul-15 9625

Far Detector Construction 24-Jul-15 24-Jul-15 11240

Cryostat Design 24-Jul-15 11266 11243 3-Sep-15 3-Sep-15

Cryostat Construction 24-Jul-15 11268 11254 3-Sep-15 3-Sep-15 3-Sep-15

Cryogenics Ar System-Design 24-Jul-15 24-Jul-15 11256 3-Sep-15 3-Sep-15 11289 3-Sep-15

Cryogenics Ar System-Construction 24-Jul-15 24-Jul-15 11259 3-Sep-15 3-Sep-15 24-Jul-15 24-Jul-15 3-Sep-15

Cryogenics N System-Design 24-Jul-15 24-Jul-15 11258 3-Sep-15 3-Sep-15 11289 3-Sep-15 11289 3-Sep-15

Cryogenics N System-Construction 24-Jul-15 24-Jul-15 11261 3-Sep-15 3-Sep-15 24-Jul-15 24-Jul-15 3-Sep-15 11289 3-Sep-15

Cryogenic Fluids 24-Jul-15 24-Jul-15 24-Jul-15 3-Sep-15 3-Sep-15 3-Sep-15 3-Sep-15 3-Sep-15 3-Sep-15 3-Sep-15 3-Sep-15

SURF 3-Sep-15 3-Sep-15 3-Sep-15 3-Sep-15 3-Sep-15 11269 11270 24-Jul-15 24-Jul-15 24-Jul-15 24-Jul-15 24-Jul-15

indicates highest priority indicates draft itemization only

http://lbne2-docdb.fnal.gov:8080/cgi-bin/ShowDocument?docid=9625

















ICD Development

07.14.15

• Capture all technical and programmatic interfaces between stakeholders- Numerous technical

meetings with Project Engineers, Scientists, Managers to list interface items and “provider” if evident

- Draft ICD from input

- Review drafts with stakeholders with an eye toward determining “provider” for each item

• Seek stakeholder’s agreement and finalize


Experiment - Facility Interface Group (EFIG)

07.14.15

• Addresses high-level interfaces between DUNE and LBNF

• Charged with assessing formal Change Requests in which one Project affects the other & making recommendations for changes

• EFIG initiated Far Site underground modular reconfiguration- 4 equal-size free-standing cryostats for detectors

- Same cryostat for both single & dual-phase detectors

- 4 equal-size caverns

- Central utility cavern

- Considered competing schedule and funding programmatic requirements

• EFIG recommended recent change to larger target hall to include this scope, cost, and schedule in CD-1 Refresh


Configuration Management - in development

07.14.15

• Change to any controlled documentation- Requirements

- Deliverable(s) and/or ICD(s)

- Engineering drawing and/or specification

- Selected project plans such as PMP

• Change Request (CR) will be initiated in joint CR database

• Engineering documentation managed in Fermilab Teamcenter engineering document database

• Project documentation managed in project’s document database DocDB- Electronic BOEs, all project plans, other relevant documents

- Provides for versioning and approvals


Change Control – LBNF/DUNE Integrated Process

in development• Separate processes that

will be managed through each Project

• Converge when change affects both Projects

• Not required until CD-2, but will start process for FSCF at CD-3a

• Change thresholds based on impact to technical scope, cost and/or schedule and in accordance to Configuration Management Plan and DOE PPEP

http://lbne2-docdb.fnal.gov:8080/cgi-bin/RetrieveFile?docid=10760&filename=LBNF%20DUNE%20Configuration%20Management%20Plan.pdf&asof=2015-7-14

http://lbne2-docdb.fnal.gov:8080/cgi-bin/RetrieveFile?docid=10760&filename=LBNF%20DUNE%20Configuration%20Management%20Plan.pdf&asof=2015-7-14

http://lbne2-docdb.fnal.gov:8080/cgi-bin/RetrieveFile?docid=10762&filename=PPEP_LBNFDUNE_draft_refresh_v5.pdf&asof=2015-7-14

LBNF

Object Heading Object Text Rationale

Far Detector System components

Neutrino Interactions target material

The far detector shall use liquid argon time projection chamber as the neutrino interactions target. (LAr)

This decision triggers the requirements regarding the cryogenic storage vessels, handling and purity. The top level engineering requirements are in a separate L2 branch with links to the requirements in this branch. It also triggers the requirments regarding the dimension of the liquid argon volume.

Object Heading Object Text RationaleFar Detector Measurements

Identification of Electron Neutrino and Anti-neutrino Events

Far detector shall be capable of identifying electron neutrino and anti-neutrino charged current beam events in sufficient numbers within the fiducial volume of the detector. The neutrino flavor of the event will be identified by clearly identifying the primary final state charged electron.

This event selection is expected to have high efficiency for the electron neutrino events. To keep the background low the final state electron must be clearly identified to emerge from the main vertex. The main vertex and the electron must be determined in the presence of any number of other final state particles including pions and photons. The energy spectra of electron neutrinos and anti-neutrinos over a broad energy range (0.5-10 GeV) with sufficient statistics will allow scientifically competitive measurements of the CP violating phase and the mass ordering (sign of delta m_32^2).


LBNF/DUNE RequirementsScience objectives flow down to science and engineering requirements

Object Heading Object Text RationaleLBNF/DUNE Global Physics Objectives

Primary Science Program

Precision measurements of oscillations in the νμ→νe and anti-νμ→anti-νe appearance channel

Precision measurements in both Near and Far detectors which are necessary to determine the parameters that govern νμ→νe (muon-neutrino to electron-neutrino) appearance, and similarly, anti-νμ→anti-νe appearance

These will allow accurate measurements of the third mixing angle theta13, and simultaneous measurement of the CP violating phase delta, and the mass-hierarchy (sign of delta m232).

http://lbne2-docdb.fnal.gov:8080/cgi-bin/RetrieveFile?docid=10873&filename=LBNF-DUNE-req-REV6.5-L1-L2.xlsx&version=22

LBNF

Object Heading Object Text RationaleFar Site Conventional Facilities

Design Life The design life of conventional facilities shall be 30 years.

The operational life of the detector is 20 years; therefore, the CF components and enclosures must have a longer design life.


LBNF/DUNE Requirements

High level programmatic requirements flow down to the deliverables’ programmatic requirements

Object Heading Object Text RationaleExperiment Sites Site Decision for the far detector

The far detector shall be stationed at the Sanford Underground Research Facility in Lead, South Dakota. The detector shall be stationed at the so called 4850 ft level (actual overburden is dependent on the exact location at that level.)

Alternatives that satisfy the baseline length requirements have been examined, and this site was chosen for both scientific and programmatic reasons.


Summary

07.14.15

• Robust Integration approach for LBNF/DUNE - Interfaces - being defined within and between subprojects

- Configuration Management with Change Control – in development

- High level requirements developed and managed

• Configuration Management to be implemented now to CD-3a for Far Site Facilities design and for LBNF Far Site - DUNE interfaces

• Engineering team in place to manage systems across and between subprojects


Backup


Ensuring all scope is covered through interface management

• Partners define work scope of intended Deliverable(s) by defining limits re: Interfaces

• Work scope of each Deliverable (one WBS item per Deliverable for non-DOE)

• Deliverables, ICD’s and Interface Matrices evolve with Partnership Development

• Compile Deliverables Lists for full scope of LBNF and DUNE

• Analyze Deliverables Lists and ICD’s for gaps and overlaps looking for missed or duplicated scope

• Negotiated adjustments to Deliverable scope and interfaces

• Partners can generate Statements of Work (SOW) from Deliverables Lists and ICDs and incorporate into agreements

ALL DELIVERABLES AGREEMENTS = FULL LBNF/DUNE SCOPE


Configuration Management Data Flow

Deliverables’ Data

Interface Control

Documents (ICD)

Deliverables Data List

Interface Matrices

LBNF/DUNE Config. Mgr.(SE acting)

Change Control

Data Management

Systems

LBNF/DUNE Science &

Engineering

Configuration Status

Accounting

Configuration Verification

Process of creating defined-scope deliverables starts here


Interfaces Between Partners to Start Far Site Construction (Excavation)

• Far Site interface requirements already developed for kick-off with A&E, are under revision to the new configuration

• Scope Interface Review to be held soon with scientists, engineers and managers having interfaces to Far Site Conventional Facilities (CF)

• LBNF Far Site CF design and construction has priority, CD-3a before CD-2 for all of LBNF/DUNE:- Some level of “baseline” of the interfacing deliverables within:

• LBNF Near Site – Beamline and CF (Far Detector alignment)

• LBNF Far Site facility (ES&H, SURF throughout the schedule, utilities…)

• DUNE Far Detector (ES&H, schedule, utilities, installation…)

• LBNF Cryostats (ES&H, schedule, space via FD interface, construction..)

• LBNF Cryogenics Systems (ES&H, schedule, surface, shaft, caverns…)

- After CD-3a changes affecting LBNF Far Site CF will be under Change Control


Configuration Management Development

• Planning for CD-2 needs to begin now and develop with Partnership development

• Each Deliverable to be a Configuration Item (CI), have a Work Breakdown Structure (WBS) ID, and dictionary definition

• Level 4 CI’s roll up into Level 3 End Items and so on up to the (4) End Items described earlier

• (4) integrated deliverables lists, formally called Configuration Items Data Lists(CIDL) all have associated ICD’s

1.DUNE Near Site

2.DUNE Far Site

3.LBNF Near Site

4.LBNF Far Site

= LBNF/DUNE scope


LBNF/DUNE – Configuration Management - Data Management Systems

• LBNF/DUNE Science and Engineering Requirements available to all (read only), controlled by Systems Engineer (SE), approval by DUNE and LBNF

• CI data is controlled by Owner/Partner in their Data Management System-Current CI engineering – CF or electro-mechanical CAD models and drawings with

PDF’s

-Specifications, including Suppliers’ specifications (verified to meet requirements)

-Copies of current CIDL and ICD’s (access via web, described later)

-Copies of Change Control data (access via web)

• LBNF/DUNE Project Offices:-Each CI must have a unique TeamCenter (TC) Design Item ID, named appropriately

-Each End Item must have a unique TC Design Item (Assembly of CI’s), named appropriately

-CIDL, controlled by SE, contains list of controlled documentation that fully describe each CI (deliverable)


LBNF/DUNE – Configuration Management - Data Management Systems

• Partners upload current engineering and specifications with ID of Change Control items completed, to its TeamCenter Design Item on a regular schedule (TBD) and at data-freeze milestones for reviewsNote: Fermilab performs this for A/E

• SE designated Configuration Manager (CM) converts and assembles CAD models in TC/NX into current Near Site and Far Site configurations

• In a regularly schedule process CM performs:-Configuration verification

-Configuration status accounting

-Updates CIDL’s and ICD’s

-Reports results to SE, PM and TC


Value Engineering & Trade Studies

• Value Engineering is a continuous process

• Will be performed for FSCF final design with A/E before CD-3a

• Value engineering & trade studies have already produced major design decisions:

-Beamline on embankment vs. underground

-Waste rock handling

-Major Far Site underground reconfiguration February-March 2015