confirmation and clearing 2013. contents approach to confirmation and clearing (c&c) ...
TRANSCRIPT
Contents
Approach to Confirmation and Clearing (C&C) Operational strategy Capacity management Delivery assurance
Changes to IT Applications Infrastructure
Process changes
Communications
Questions
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
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
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
Amazon Web Services – EC2
End to End (High Level)
Call Centre
UCAS @ Rosehill
Disaster Recovery
HEIs
Apply Onyx
Apply Onyx
Topaz On-PremiseTribal/SAP/etc.(also Weblink)
Applicants for Track
TrackAZURE
TrackAZURE
Internet
Microsoft Cloud Services
Amazon Web Services – EC2
Scenario: HEI confirmation decision
Call Centre
UCAS @ Rosehill
Disaster Recovery
HEIs
Apply Onyx
Apply Onyx
Topaz On-PremiseTribal/SAP/etc.(also Weblink)
Applicants for Track
TrackAZURE
TrackAZURE
Internet
Microsoft Cloud Services
HEI makes decision on application
Decision transferred to TOPAZ (via
Weblink)
TOPAZ replicatesTOPAZ
publishes decision to TRACK
Applicant receives decision
(via TRACK)
Amazon Web Services – EC2
Scenario: Applicant Clearing Choice
Call Centre
UCAS @ Rosehill
Disaster Recovery
HEIs
Apply Onyx
Apply Onyx
Topaz On-PremiseTribal/SAP/etc.(also Weblink)
Applicants for Track
TrackAZURE
TrackAZURE
Internet
Microsoft Cloud Services
Applicant logs in to track
Applicant makes clearing choice
Choice transferred to
TOPAZ
TOPAZ replicates choice
Choice transferred to
HEI
Changes to IT
Extensive IT testing through:
Application testing
Business event testing ABL Confirmation Results days Clearing
Dress rehearsals
‘Mob’ test – 10 July
Technology StrategyTesting
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 StrategyTrack
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 StrategyTimings
Embargo process
By 17 May 2013 By 14 June 2013 17 June-05 July 2013
• Information pack sent by UCAS. Contains letter, agreement and examples of good practice
Step 1
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