1. DUNE-LBNF Configuration Management Jeff Dolph, LBNF interim Systems Engineer BNL

2. DUNE-LBNF Configuration and Change Management  “Integrate many stakeholders into an effective team” Scope packages defined (grossly at first) Package interfaces defined (grossly at first, but Far Site has refined interface requirements now)  Requirement for a readily accessible but tightly controlled environment Change must show existing configuration accurately Change request makes proposal of a “to” configuration

3. DUNE-LBNF Change Management Example  Change to free-standing cryostat – LBNF change affects DUNE (uncontrolled recent change).  Proposed controlled process would be: LBNF discusses change at L2/L3/L4 and assesses internal impacts Identifies change impacts by checking off list of changes to the Cryo-FD interface requirements and sends descriptive proposal to DUNE TC[?] DUNE identifies affected scope packages, distributes change proposal, makes assessment of impacts to science, engineering, cost and schedule DUNE TC, RC and Spokes. decide, based on impact thresholds (TBD), whether EFIG considers change proposal

4. Cryostat change interface requirements

5. DUNE-LBNF Change Management Example  (Continued) Proposed controlled process would be: EFIG decides whether proposed change becomes change request in both LBNF and DUNE change systems - Considers ALL ramifications of change in light of current conditions – EFIG is best suited body for this and has open communication lines