1 / 21

Public Outreach Application

Public Outreach Application. IMWG Meeting, 02.07.2013. Jan Janke , Ladislav Fialka (GS-AIS-GDI). 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

cooper-kirk
Download Presentation

Public Outreach Application

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  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 Planned

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

  4. Public Visits Service • Ca. 85,000 visitors from ≈ 60 countries in 2012 • Ca. 400 active CERN guides • Managed by < 10 people We are a group of 50 Toomanypeple! Split visit! Requests Atlas isclosed! Bus? Requestexpired Restaurant? I wanttovisit CERN myself Qualification? I wantto be a guide! Group of 200! Guides?

  5. Public Visits Service • Ca. 85,000 visitors from ≈ 60 countries in 2012 • Ca. 400 active CERN guides • Managed by < 10 people We are a group of 50 Toomanypeple! Split visit! Requests Atlas isclosed! Oh damnit, I can’tgo Create new Bus? Requestexpired Restaurant? I wanttovisit CERN myself Plan Itinerary Qualification? I wantto be a guide! Group of 200! Guides?

  6. Public Visits Service • Ca. 85,000 visitors from ≈ 60 countries in 2012 • Ca. 400 active CERN guides • Managed by < 10 people We are a group of 50 Toomanypeple! Split visit! Requests Atlas isclosed! Oh damnit, I can’tgo Create new Bus? Requestexpired Restaurant? I wanttovisit CERN myself Plan Itinerary Qualification? I wantto be a guide! Group of 200! Guides?

  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!

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

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

  10. Visits Agenda Notes Visits Itineraries

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

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

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

  14. “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 Global visit status? Visit Bldg. 33 No Status: ok Impact required? Status: Impact? ATLAS UG Yes Create Impact Status: ok Globe No Status: Impact? CMS UG Yes Create Impact R1 No Status: ok

  15. “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 Global visit status?Not OK Visit Bldg. 33 No Status: ok Impact required? Approved ATLAS UG Yes Create Impact Status: ok Globe No Not approved CMS UG Yes Create Impact R1 No Status: ok

  16. “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 Global visit status?OK Visit Bldg. 33 No Status: ok Impact required? Approved ATLAS UG Yes Create Impact Status: ok Globe No Approved CMS UG Yes Create Impact R1 No Status: ok

  17. PO/Impact Workflow Edited/deleted visits or programmeitems also trigger interaction w. Impact. Create visit Check for Impact relevant visit parts Impact? no Visit status ‘ok’ yes Impact creation Request “Impact” Integrate Intervention ID Check approval status Approval/Refusal 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) Still under discussion. Depends on the experiments.

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

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

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

More Related