1. Control Software Integration German Schumacher T&S Software Lead

2. Integration Context 2 The Observatory Control System (OCS) is the primary high level master control system that schedules, commands, coordinates and monitors the observatory, for conducting the survey. LSE-72LSE-71LSE-73 LSE-70 LSE-209

3. Telescope & Site Integration 3

4. Integration Process Periodic workshops and telecons – Timeline established The agenda and minutes can be found at: – https://confluence.lsstcorp.org/display/SYSENG/C CS-DAQ-OCS-DM+Workshops 4

5. Workshop I 2014 Nov 11 – 14: SLAC – Review state of ICDs between principal LSST subsystems. – Plan for locations and calendar of the subsystems integration process. – Commanding and Sequencing Commanding protocol Component Interface model 5

6. Workshop II 2015 Feb 19 20: TUCSON – Software infrastructure – Commanding – Software components 2015 Apr 07: Telecon – LSE-71 OCS CCS ICD timing – SAL API 6

7. Communications Protocol Interface 7

8. Component Interface Base 8

9. Component Interface Extension 9

10. Workshop III 2015 May 06-08: SLAC – Component Interface model refined – EFD large files system – Common IT infrastructure Linux CentOS – Refine Software/Hardware handoff milestones 10

11. Workshop IV 2015 July 8 – 10: NCSA – Communication integration between OCS-CCS- DMCS software platforms, using the SAL package. C/C++, Java, Python – Configuration – Common infrastructure 11

12. Future Milestones 2015 Oct – ICDs status review 2015 Dec – ICDs updates – Simulators delivery 2016 Jan – OCS – CCS Communications tests 2016 June – EFD Camera telemetry population 2016 Aug – Middleware V3.5 – Simulators with full capacity 2016 Nov – OCS – CCS – TCS – DMCS Start/End of night tests – EFD replication – Middleware V4 12