2. 2

3. 3

4. 4

5. In MCM database In Scheduler database 5

6. 6

7. MC production requests SchedulingViews Conversion of requests data Scheduling of converted requests data Displaying scheduled data 7

8. Different sources Translator Database Scheduler Web page Data sources either a database like MCM with non-converted data in it or csv file uploaded in a server. Conversion of requests data from different sources. Data either saved in database or given directly to scheduler depending on source of data. Database of converted requests data from other databases like MCM. Scheduling of converted data to be displayed in a timetable. Interactive web interface, displays timetable and allows to pass different configurations or more data to scheduler. 8

9. 9

10. 10

11. 11

12. 12

13. 13

14. 14

15. Y axis X axis Coloring Developed by Julius Skripkauskas 15 https://cms-pdmv.cern.ch/scheduler/

16. 16

17. Colored by Member of Campaign option Label shows that “Spring14dr” is brown, requests with “Spring14dr” are also colored brown. 17

18. Drop down lists to change displayed part of X axis. Input fields: “Slots” – number of slots available, after entering number and clicking “Redraw” everything is recalculated with new Y axis. “Keywords” – filtering requests by keywords in them, after entering keywords like status “new” and clicking “Redraw” everything is recalculated just by using requests that have that keyword. Data source configuration window – allows to upload data within csv files to server. Csv data uploaded with label provided by user. Source of data may be configured by user by clicking on a checkbox. After configuration and reload of page data is scheduled and displayed from previously chosen sources. 18

19. Scheduled by filtering request only to those of “Spring14dr” campaign. As we see production of all requests of “Spring14dr” takes about 4-5 days. 19

20. 20

21. 21

22. 22