1. Public Outreach Application IMWG Meeting, 02.07.2013 Jan Janke, Ladislav Fialka (GS-AIS-GDI)

2. Overview Common visits agenda Visit conflict detection/handling For all of CERN’s Public Outreach activities Public Visits Press Office Media Visits Protocol Office VIP Visits Experiment Visits Globe Events Partly in Production, full v1 deployment in July Work in Progress Scheduled for Implementation Planned 2

3. Public Visits Service Ca. 85,000 visitors from ≈ 60 countries in 2012 Ca. 400 active CERN guides Managed by < 10 people 3 Restaurant? Bus? Guides? I want to be a guide! I want to visit CERN myself Requests We are a group of 50

4. Public Visits Service Ca. 85,000 visitors from ≈ 60 countries in 2012 Ca. 400 active CERN guides Managed by < 10 people 4 Restaurant? Bus? Guides? I want to be a guide! Too many peple! Split visit! I want to visit CERN myself Requests We are a group of 50 Group of 200! Qualification? Atlas is closed! Request expired

5. Public Visits Service Ca. 85,000 visitors from ≈ 60 countries in 2012 Ca. 400 active CERN guides Managed by < 10 people 5 Restaurant? Bus? Guides? I want to be a guide! Too many peple! Split visit! I want to visit CERN myself Requests We are a group of 50 Group of 200! Qualification? Create new Plan Itinerary Atlas is closed! Oh damn it, I can’t go Request expired

6. Public Visits Service Ca. 85,000 visitors from ≈ 60 countries in 2012 Ca. 400 active CERN guides Managed by < 10 people 6 Restaurant? Bus? Guides? I want to be a guide! Too many peple! Split visit! I want to visit CERN myself Requests We are a group of 50 Group of 200! Qualification? Create new Plan Itinerary Atlas is closed! Oh damn it, I can’t go Request expired

7. Public Visits Service Ca. 85,000 visitors from ≈ 60 countries in 2012 Ca. 400 active CERN guides Managed by < 10 people → Automation is needed! 7

8. End to End Workflow Open Visits Reservation by client Handling fully automated No human intervention Group Visits Semi-automatic Requires human approval 8

9. End to End Workflow Verification, scheduling, confirmation by the Visits Service Back Office 9 Visit Type Proposed slots (quick selection) Propose alternative date List of all requests

10. Visits Agenda 10 Visits Itineraries Notes

11. Many Other Tools Itinerary management Guides management incl. payments Guides / visit subscription Control of request workflow … 11

12. Integration of Other Services Media visits organized by the Press Office Work in progress (almost finished) First to be integrated with “Impact” 12 PRESS

13. A Typical Visit 13 33/R-009 ATLAS Globe Underground Area: → Requires Impact

14. Global visit status? “Impact” Creation Uses Impact REST API For every controlled location (facility) 1 visit can contain N programme items Impacts will be created per programme item 14 Visit Bldg. 33 ATLAS UG Globe CMS UG R1 Impact required? No Yes No Yes No Status: ok Create Impact Status: Impact?

15. Global visit status? Not OK “Impact” Creation Uses Impact REST API For every controlled location (facility) 1 visit can contain N programme items Impacts will be created per programme item 15 Visit Bldg. 33 ATLAS UG Globe CMS UG R1 Impact required? No Yes No Yes No Status: ok Create Impact Approved Not approved

16. Global visit status? OK “Impact” Creation Uses Impact REST API For every controlled location (facility) 1 visit can contain N programme items Impacts will be created per programme item 16 Visit Bldg. 33 ATLAS UG Globe CMS UG R1 Impact required? No Yes No Yes No Status: ok Create Impact Approved

17. PO/Impact Workflow 17 Create visit Check for Impact relevant visit parts Impact? Request “Impact” Impact creation Integrate Intervention ID Check approval status Approval/Refusal yes Visit status ‘ok’ no Edited/deleted visits or programme items also trigger interaction w. Impact. Regular polling (e.g. twice per day)

18. Content of “Impact” Location (facility) Title Responsible → Head of Press/Protocol Office Activity type → Visit Date/time Priority Participants → Guide, participants System ? (should not be mandatory for visits) 18 Still under discussion. Depends on the experiments.

19. Impact Feedback 19 33/R-009 ATLAS Globe Underground Area: → Requires Impact Intervention ID Link to Impact Impact Status

20. User Roles ADMIN OPEN_VISITS_ADMIN GROUP_VISITS_ADMIN DUTY_ADMIN GUIDE_ADMIN GUIDE [PRESS|VIP]_ADMIN [PRESS|VIP]_VIEWER 20 Visibility restrictions only for Protocol/VIP Visits. Respect of booking priorities 1. Protocol 2. Press 3. Public

21. Summary Different visit types Integrated agenda Automation Conflict detection Impact integration 21

22. Technology Stack 22 AIS fwk mvp4gGINGXT Dozer + DTOs GWT Grails Quartz HibernateSpring