1. Instrument Construction Phase 1 and beyond Rob Connatser Chief Instrument Project Engineer www.europeanspallationsource.se September, 2014

2. Outline Phase 1 Engineering Planning ESS Contributions In-Kind Agreements Interaction with Regulators General Information 2

3. Phase 1 resources and output 3 Resources FTE/value Lead Instrument Scientist 0.8 Lead Engineers1.0 Planner0.33 Chopper Team Member0.25 Detector Team Member0.5 Electr. Eng. Team Member0.25 Optics Team Member0.5 DMSC Team Member0.1 Travel budget 10k€ Equipment budget10k€ STAP review6k€ Tollgate 2 Review8k€ Baseline Documents Concept of Operations for the instrument PBS Instrument Work Package Specification P&ID of Instrument System Engineering (requirements & interface) documents Schedule Budget Work unit documents 3D CAD model of instrument envelope Technical Group design documents Draft Commissioning Plan

4. Roles – Phase 1 Lead Instrument Scientist Responsible for defining functional requirements of instrument including scientific case. Helps generate estimates on time and costs Lead Instrument Engineer Performs and manages engineering effort including 3D model Suggests technical solutions to requirements Helps generate estimates on time and costs. Planner Fills in WBS and makes initial schedule Assembles budget from provided details Technology Group Member Helps refine functional requirements. Proposes technical solutions in their area utilizing standards or development as necessary. Provide estimates. Neutron Instruments Division or Partner Integration and Design Support Division or Partner Project Support Division Instrument Technologies Division or other internal group

5. Roles – Phase 1 Lead Instrument Scientist Responsible for defining functional requirements of instrument including scientific case. Helps generate estimates on time and costs Lead Instrument Engineer Performs and manages engineering effort including 3D model Suggests technical solutions to requirements Helps generate estimates on time and costs. Planner Fills in WBS and makes initial schedule Assembles budget from provided details Technology Group Member Helps refine functional requirements. Proposes technical solutions in their area utilizing standards or development as necessary Provide estimates CORE TEAM Must be co-located Must interact often with Technology Groups

6. Organization & Roles – Phase 1 Lead Instrument Scientist Responsible for defining functional requirements of instrument including scientific case. Helps generate estimates on time and costs Lead Instrument Engineer Performs and manages engineering effort including 3D model Suggests technical solutions to requirements Helps generate estimates on time and costs. Planner Fills in WBS and makes initial schedule Assembles budget from provided details Technology Group Member Helps refine functional requirements. Proposes technical solutions in their area utilizing standards or development as necessary Provide estimates Support Works within the Technology Group to find solutions. Brings solutions from the Technology Groups area to the instrument project. Needs and capabilities vary by group.

7. How – Phase 1 7 ConOps & Requirements Scientist Refine Requirements Core Team iterates with Technology teams Solutions, PBS, P&ID Core Team Technology Teams Deliverables Work Units Core Team Technology Teams Estimates Schedules Core Team Technology Teams Set Scope Proj. Spec. ESS Managemet Core Team

8. Year 1Year 2Year 3Year 4Year 5Year 6 Instrument Lead Scientist80%67% 80% Lead Engineer100% Detector Group50%25% 100%150% Chopper Group25% 50% 100%50% Optics & Shielding50% 10% Motion Control & Automation 25% 50%100%50% Additional Engineering0100%250%150%100%50% General Technicians000025%100% Construction Manager0025%33% Initial DesignFinal DesignProcurement & Fabrication ConstructionInstallationCold Commissioning Single Instrument FTEs

9. Engineering Support ESS is using CATIA v6 – It will provide a long term solution for engineering and storing information Workstation provided from ESS – Connects via VPN to ESS network & engineering database – Training available – Support of machine & software from ESS Each Instrument Team can determine how to design and integrate their components, but need to input everything into CATIA v6 and ensure appropriate integration. ESS Plant Layout is managed in Catia. We will determine an upload schedule to manage interferences. 9

10. Planning ESS is using Primavera – aka P6 – High level tool for planning and integration – Used by ESS management and governing bodies to track progress and costs in the form of Earned Value – Not suitable (as currently configured) for the detailed plans necessary for a instrument project Each team will need to keep their own detailed schedule & plan in the software of their own choosing. There will be a P6 version, which is condensed from the detailed plan These need to be connected to ensure appropriate tracking. 10

11. DRAFT ESS Contributions Nuclear Shielding Specifications: General shielding, Cave shielding, beamstop Instrument Shielding Analysis and Report Instrument Control Systems: Chopper Control System, Instrument Control and Automation, Sample Environment Control, DMSC, connections to ICS, integration of external control systems to the instrument control system Detectors and Data Collection: Detector Systems Readout, Data Collection to DMSC Safety System: Personnel Safety System and associated certification 11

12. DRAFT ESS Contributions The Chief Instrument Project Engineer’s office will manage the construction and installation effort on the site via Construction Managers, whose costs are outside the instrument project budget. These construction managers will administer and manage the construction labor force and purchase of construction materials. The cost of this labor and materials will be billed back to the instrument project. Additionally, ESS shall provide to the instrument projects the following items outside of the instrument project budget. Instrument Control Software Instrument Data Analysis Software Bunker Shielding –starting at appr. 1.5 m above Target Center line (final value TBD) to the necessary height (TBD) and 1.0 m below Target Center line (final value TBD) to a radius of 15m in the North, South, and East sectors, and to a radius of 30m in the West sector. ICS hardware (2 ICS boxes and the data cable back to the ICS network) 12

13. In-Kind Agreements Model for In-Kind Agreements for ESS is centered on Deliverables – Examples include reports, designs, manufacture and installation. ESS and Partner work together to define what is being “delivered” Agreement is reached on the value and schedule for these deliverables. Formal Agreement taken before the In-Kind Review Committee – Responsibility for ensuring appropriate value received for credit given 13

14. In-Kind Agreements Planning Phase Agreements – Informal agreement between ESS and partner on what is to be done and the value – Import the agreement to the formal in-kind agreement template, agreed upon by all parties – ESS brings this agreement to the In Kind Review Committee for approval Detailed Design Phase Agreement – Plan for agreements made during Phase 1 – Deliverables (from the PBS) aggregated into Work Units 14

15. Integration with Licensing Current plan for ESS is that the facility receives a license to operate as a whole, no individual licenses for instruments. NSS team is working with ES&H (and Target and Accelerator) to develop the proposal for operating and safety schemes. 15

16. A Graded Approach SSM - ESS General and conceptual information, enabling SSM to set the requirements Permit and conditions for building a spallation source Permit for installation of equipment that can generate ionising radiation Permit for test operation Permit for permanent operation Permit for De- commissioning Reports and analyses showing that ESS is expected to fulfill the requirements Experience from test operation and maintenance incorporated in verifying analyses Reports and analyses verifying that ESS fulfills the requirments Experience from operation incorporated in the de- commissioning plan 1 1 2 2 3 3 4 4 5 5 ESS SSM Phase Complementary information 2013/2014 PSAR (2015/2016) PSAR/MKB 2012-03 (CDR) SAR Ground break 2014-xx-xx Installation of Equipment 2015-xx-xx Commissioning - Acc 2016-2025 - Target 2019-2025 Commissioning - Acc 2016-2025 - Target 2019-2025 Operation 2025 - 2065 Operation 2025 - 2065 Decomm. 2065-2070 Decomm. 2065-2070 FSAR 2015 2016-2019 SAR-Av. 2064 ? 2025 2065

17. Timeline 2016-2017Installation of base of the bunker 2017Installation of bunker stacked shielding (to load the floor) 2017Start of construction of individual instrument infrastructure 2018Start of installation of instrument technical components 2019Instruments 1-3 finish installation and cold commissioning, begin hot commissioning 2020-28Instrument construction and installation continues for the 22 initial instruments 17

18. Beam Extraction/Target Interface Exact configuration still unknown due to uncertainties in the the moderator design. This includes port design, angular separation, viewing angles. Target will make plugs, each instrument is responsible for their own insert. Standard design is intended for outside to ensure appropriate interfaces. Instrument responsible for installing optics into the insert and alignment. Target is responsible for the installation and removal of plugs and inserts and will have the appropriate tooling and casks. NSS involved and sets some requirements. 18

19. Construction and Installation NSS will provide a construction work force for building the physical infrastructure of the instruments. This contract should also provide all construction materials. This effort is managed by a team of local construction managers. Build Partners should generally provide technical installation personnel for technical components. Technology Groups have also anticipated having installation personnel. 19

20. Hot Commissioning Partners should plan on participating in the hot commissioning of the instrument. Engineering and other resources will be available, from the operations budget. Formal plan for hot commissioning is required and should be finished prior to entering user operations. 20