Conventional Facilities integration: Approach and Issues

1. Conventional Facilities integration: Approach and Issues Daniel Piso Fernández WP Leader (WP13 ConventionalFacilities Integration Support) November 5, 2014 www.europeanspallationsource.se November 12, 2013

2. The charge • Is the scope of Conventional Facility controls integration properly defined? • Are the work package activities properly derived from and aligned with CF planning?

3. Some Context - CF Systems • Scope of Control & Monitoring CF • Different locations • Approx. 39 buildings • Different types of systems • HVAC control, Access and security, Process control, CCTV…and more • Different types of users • Personnel for maintenance, Security personnel …and more • Different types of requirements • Performance, reliability …and more

4. Some context - CF Systems Controls • Power SCADA • Operation of the electrical power system, medium and low voltage • Building Management System (BMS) • Operation for maintenance • HVAC (ventilation, comfort heating/cooling, tap water, waste water etc.) • Process systems (water cooling, process water and compressed air etc.) • Electrical systems (lighting, transport etc.) • Sec-Net, Supervisory security system • Operation of safety and security • Fire alarm, intrusion alarm, CCTV, access control

5. Some context - Time Frame • Relevant milestones • First Draft Specification of controls for conventional facilities (end of Q4-2014) • End of construction for HO5 (Q2-2016) • First access to accelerator building. Test Stand building GO4 (Q3-2016) • Full access to accelerator building GO2 (end of Q1-2018) • Full Access to Target building ( Q2-2018)

6. WP Scope - WP Definition The Work Package description is • The WP is intended to develop integration support activities for CF systems and to build the interfaces between them and ICS. • The goal is to provide a set of tools and infrastructure for control and monitoring of CF systems that are relevant to the machine operation.

7. WP Scope - Interface design principles • The daily operation of the CF control systems that are required for the machine operation and processes around shall be done with EPICS. • Signal/data from CF systems shall be made available to ICS for reading and writing. • The BMS system shall manage those systems that are not relevant for the machine operation and for the maintenance of all the systems. • The CF controls systems shall be generally based on PLCs • The communication between CF and ICS shall be done through EPICS supported protocols • All PLCs with interfaces with EPICS will be synchronized via an NTP server provided by ICS.

8. Activities - Integration Sessions • One person from ICS (WP 13) one person from CF (in charge of the CF controls), at least one person from the design team and people from AD when required • The goal is to deliver a first interface document within 2014. • Information to capture for each system • Milestones of the design along 2014 (ICS/BMS) • Is the system PLC based or not? • Physical location of the CF system (ICS/BMS) • Where do we need to operate/interact with the system (ICS/BMS)? • What information/signals do we need to operate the CF system (ICS)? And for maintaining it (BMS) • What information should be monitored for the CF system (ICS)? • What information should rise an alarm (ICS/BMS)? • What information/signals are important for ESS machine operation?(ICS) + biweekly coordination meetings with the design coordinator

9. Activities – Re-evaluation • At some point the designers were not able to deliver the information needed because the design of different systems evolved at different paces. • There were different concepts about what needed to be delivered for a preliminary design and detailed design. • CF had to change internally their design strategy because of the reasons above, as well as changes in their teams and the collaboration with Skanska. • ICS Seminars (every 3-4 months): • Planning • Products • System Engineering • Joint Activities organization • Seminars • C&M Meetings • Integration Sessions

10. Activities…Priorities in 2015 • HO5 (Primary Substation Building), HO6 (Distribution Substation Building), HO1 (Central Utility Building), GO1 (Tunnel Building), GO2 (Gallery Building) are the priorities (in this exact order) for next year.

11. Activities – How do we plan activities from now on… • The plan for 2014 is to deliver the first CF-ICS interface (HO5,HO6). • After the CF-ICS seminar we started re-evaluation of planning activities. • CF is also reorganizing their planning. HO1, HO5, HO6, GO1, GO2 have detailed planning already. The detailed planning for other building is still to be developed. • We developed a new approach for the planning that will be applied to the 2015 planning in the following weeks. HO5 and HO6 will serve as a test for this approach Interface Design Installation Design Installation Procurement Commissioning Network cables Power Supply Space Requirements

12. Activities - Products Interface Design • Installation Design. The products for this phase will be defined in the next CF-ICS Seminar. January 2015. Design Document

13. Typical Objects

14. Issues • Central Utility Building (HO1) • Water Leak Risk under mitigation. Risk session in one week. • Dimensioning of the cooling water system, could affect the concept of the building. • Decision about the water plant controls in January (next CF-ICS seminar) • Process Systems Controls • Controls design not progressing at the same pace. • Affected by the changing requirements from AD.

15. What do we have… • Planning • CF has updated planning • As a result of the CF-ICS Seminar we collected relevant milestones • With that we have a way to derive the planning for 2015 and onwards. • We will apply this to detailed 2015 planning and develop the planning until 2019. • We will test the results for HO5, HO6 and HO1 if this approach needs refinement • System Engineering • The system engineering team has set up an ICD in DOORS with sections for different types of requirements (monitoring & control, electrical interfaces and mechanical domain) • Interface Design Principles going to the Top Level ICD. • First Round of requirements for the Server Hall. • Requirements have started to flow into the tool • Products • Design Document • Installation Design Products to be agreed in January • Integration Sessions Materials • Design Principles of the interface that we agree on • CF is using the ESS Naming Convention • High-level matrices with the systems and buildings with interfaces CF-ICS • Matrices with systems per building (all the information needed available, construction in progress) • Systems with interfaces to PSS defined. • Information about the HVAC equipment to interface for HO5,HO6, GO1, GO2. • Information about Electrical Power Supply Systems equipment almost ready for GO1, GO2

16. What is next • Provide requirements for power supply, network and space for HO1, HO5 and HO6 (following weeks) • Keep on progressing in the gathering of information and try to provide the design document for HO5 and HO6 by the end of this year. • Keep progressing in the gathering of information for HO1, GO1, GO2. • Next CF-ICS seminar (installation design products and water plant controls are the main topics, so far…) • Validation of the location of the Server Hall (risk session next week). • Collaborate with AD for them to provide requirements to CF for the CF Systems Controls. • Once we understand our activities, we think that this WP is ready to ramp up. A new hiring is planned for next year.