1. Confirmation and Clearing 2013

2. Contents  Approach to Confirmation and Clearing (C&C)  Operational strategy  Capacity management  Delivery assurance  Changes to IT  Applications  Infrastructure  Process changes  Communications  Questions

3. Approach to C&C Capacity Strategy Assurance Operational Strategy  Critical national infrastructure  Customer centric design  Stabilise existing systems  Focus on whole IT capability Capacity  Demand unknown  Over-supply of operational capacity Delivery assurance  Extensive systems testing  Dress rehearsals  ‘Mob’ testing

4. Changes to IT Scalability Resilience Performance Design principles  Minimised points for failure  All core products autonomous (failure in one does not impact others)  Move core systems to supported software and hardware  “Always on” core systems (no need to “switch over”)  All systems designed to scale to meet demand

5. Changes to IT System Changes  IT architecture in the ‘cloud’  Go-live end of June  Extended contingency/DR capability  Link products optimised  New version of Track  Go-live early July  Capability augmentation  Enhanced monitoring  Clearing vacancies via Search tool Technology Strategy High performance systems

6. Core activities on results day 2012

7. Core activities on results day 2013

8. Amazon Web Services – EC2 End to End (High Level) Call Centre UCAS @ Rosehill Disaster Recovery HEI s ApplyOnyx Apply Onyx Topaz On-Premise Tribal/SAP/etc. (also Weblink) Applicants for Track Track AZURE Track AZURE Internet Microsoft Cloud Services

9. Amazon Web Services – EC2 Scenario: HEI confirmation decision Call Centre UCAS @ Rosehill Disaster Recovery HEI s ApplyOnyx Apply Onyx Topaz On-Premise Tribal/SAP/etc. (also Weblink) Applicants for Track Track AZURE Track AZURE Internet Microsoft Cloud Services HEI makes decision on application Decision transferred to TOPAZ (via Weblink) TOPAZ replicates TOPAZ publishes decision to TRACK Applicant receives decision (via TRACK)

10. Amazon Web Services – EC2 Scenario: Applicant Clearing Choice Call Centre UCAS @ Rosehill Disaster Recovery HEI s ApplyOnyx Apply Onyx Topaz On-Premise Tribal/SAP/etc. (also Weblink) Applicants for Track Track AZURE Track AZURE Internet Microsoft Cloud Services Applicant logs in to track Applicant makes clearing choice Choice transferred to TOPAZ TOPAZ replicates choice Choice transferred to HEI

11. Changes to IT Extensive IT testing through:  Application testing  Business event testing  ABL  Confirmation  Results days  Clearing  Dress rehearsals  ‘Mob’ test – 10 July Technology Strategy Testing

12. Changes to IT  Redeveloped for performance  One system not two  Cloud-based  New user interface  Fantastic feedback  New branding  Comms throughout June  Screen shots to members soon Technology Strategy Track

13. Track screen shots

17. Process changes Results day timings  2012 timings worked well  Minimal changes for 2013  Clearing vacancies published  18:00 P Day-1  Track go-live on A Level day  07:00 Technology Strategy Timings

19. Scottish clearing Results Tues 06Wed 07Thu 08Fri 09 2013 2012 Results Tues 07 Wed 08

20. Embargo process By 17 May 2013By 14 June 2013 17 June-05 July 2013 Information pack sent by UCAS. Contains letter, agreement and examples of good practice Step 1 Members sign and return agreement Plan and implement any process changes Step 2 UCAS chase non returns Step 3

21. Communications Members Applicants Stakeholders  Transparency with members  C&C briefings  Daily log – regular updates  Multi-media approach for summaries  SMS ‘urgent’ channel  Social media to reach applicants  Social media to scan the environment  Escalation mechanism for issues

22. Questions Philip Blaker Head of Admissions Services p.blaker@ucas.ac.uk