Initial Infrastructure Review has found:

1. As-Is Consequence Solution Outcome Initial Infrastructure Review has found: • SAN: • Old and failing SAN (disk storage). • SAN is 9-10 years old and end of life/ Out of support • SAN storage at capacity. • Data corruption. • No disaster recovery or redundancy capability. • Current SAN does not support VMWare 4 or5 and Windows 2008. • Spares are becoming hard to source • No data replication between Data Centres for DR • Utilising additional rack space, ethernet & fibre ports, increased power usage costs , etc. • SAN • Loss of access to business data – LCC experienced a 5 day outage on their EVA 8100 as a result of a hardware failure • Point solutions have been put in place as capacity reached within SAN – not cost effective • Risk that systems cannot be restored due to support expiry • No DR capabilities • Cost savings within Data Centre cannot be achieved with current infrastructure (limitations stopping virtualisation and rationalisation) • New systems applications can not be deployed due to limitations of the SAN infrastructure • SAN • Procure SAN array with appropriate capacity/features and resilience/replication for platinum and gold services (capacity review needs to take place. • Current and future requirements catered for, provide more resilient solutions and allow for multi-tenancy • SAN • Risk mitigated against loss of business data • Supported platform to operate Mouchel business – fit for purpose • Enabler for Virtualisation and rationalisation programme, releasing efficiencies • Platform enabler for growth (within Mouchel and new clients – shared services platform etc) • Enabler for modernisation of systems (Windows 2008 rollout)

2. Outcome As-Is Consequence Solution • Backup • Critical business information is protected • Mouchel reputation is protected (Service and client delivery) • Server Estate • Supported environment that supports business systems • Modern environment with lower TCO • Up to date operating system that enables deployment of modern applications and features • Backup • Some critical Data isn’t protected and cannot be restored • Mouchel’s reputation is impacted • Inability to backup and restore reliably • No DR capabilities • Inconsistent sprawl of backup targets • Server Estate • The consequence of failure depends on the function of the server in question but in most instances there would be a loss of productivity due to the inaccessibility of connectivity, data or applications, and being a single point of failure. • Risk to business continuity • Risk to service delivery and reputation • Backup • Upgrade backup solution, standardising and re-utilising point storage solutions procured as a result of SAN capacity issues where appropriate. • Review backup policies for effectiveness (including replication to a secondary site) • Centralise as much data as possible to reduce network impact and improve reliability • Server Estate • Conduct Virtualisation and Rationalisation programme • Centralise Branch office servers where possible (consolidate onto virtual /distributed file platform) • Begin process of migration to Windows 2008R2 • Backup • Old and under-performing tape library • Inability to backup and restore reliably • Insufficient backup capacity • No Archive Strategy • Many point solutions to keep capacity issues temporarily at bay • Majority of data to be backed up is not local to the data centre and must come over the WAN • Server Estate • No. of Servers over 3 years old:  95.11% • No. of Servers over 5 years old: 87.97% • No hardware maintenance on some servers • Virtualisation process stalled due to lack of capacity/capabilities on the existing storage • Some sites have too many servers requiring more resilient accommodation which may not be available – for example air-conditioning Initial Infrastructure Review has found:

3. Outcome As-Is Consequence Solution • VMWare • Reduction in server hardware and therefore Rack & power requirements which has a direct effect on the cost of hosting • Increased responsiveness and flexibility to business need by allowing new systems to be rapidly provisioned in a virtual environment without the need to acquire new hardware • Modernise capabilities of Windows platforms from backend server through to desktop/mobile devices • Comms • Reduce business risk as a result of telephony failure • Resilience for business-critical systems • Centralising data removes majority of backup problems and uncouples the end user from a specific site when accessing their data • VMware • Unable to install modern/up to date Operating Systems – knock on affect to latest versions of applications which has risk for application compatibility issues for Win7/8, Exchange 2010, Citrix, MS SQL etc. • Last P1 as a result of the SAN controller crashing took 2 days to restore – resulting in loss of productivity and impact to service delivery • Comms • Risk to telephony service in the even of a problem • In some cases links over utilised when backing up data causing backups to fail/overrun meaning data is left at risk • Loss of a core switch will take down the entire primary data centre • VMware • Upgrade VMWare environment to take advantage of new features that enable improvements and efficiencies • Consolidate aging host servers to new environment • Resume virtualisation of server landscape • Comms • Central storage solution to overcome current sharing issues • Review telephony strategy for back office and call centre user groups • Comms strategy review • Eliminate SPoFs • VMware • Due to SAN age it’s not compatible with current supported versions of VMware products. • Can’t take advantage and adopt new features e.g. Thin Provisioning, deduplication • Due to inability to upgrade hosts no support for newer versions of Windows OS within Primary DC, i.e Windows Server 2008/2008 R2 • A controller failure on the EVA results in the entire Vmware virtual cluster crashing and have to manually be restarted and restored, taking down the entire virtualised estate • Comms • Telephony platform not within supported release • Inefficient use of comms links as some sites host data which is shared with other sites • Some single points of failure in core networking infrastructure • Reliance on third party support Initial Infrastructure Review has found:

4. Health Check Requirements: • Whilst within the quick Analysis of the current Infrastructure it is clear that the SAN is the root cause of a number of issues within the environment and its replacement will enable Mouchel to modernise, virtualise and rationalise its sever architecture and improve its backup and DR capabilities it is recommended that alongside a SAN replacement project a further health check be carried out to: • Assess the business objectives/ ambitions • Ensure IT support business • Create the right platform for growth • Private vs. hybrid vs. public cloud – where this fits • Assess the applications estate • Supportability, complexity and consolidation of platforms • Compatibility for Win7/8 • Underpinning infrastructure • Review the Infrastructure and Backup strategies • Deeper dive into this area – SAN will not only imperative to remove current risks to business operations but will form the foundation to facilitate further enhancements, efficiencies and future proofing within the infrastructure

5. Health Check Approach 2 weeks Direction Setting • Visioning • Strategic Review (SWOT) • Objective setting and “What’s Important Now?” from a business perspective 6 weeks As-Is Architecture Definition (Lightweight) Application Architecture Definition Mapping applications to business processes to assess non-standardisation opportunities and threats Started (but in isolation to other aspects) Technology Architecture Definition Mapping infrastructure variations between Mouchel sites, identifying Single Points of Failure,, review support Contracts, obsolescence & security threats, non-standardisation opportunities and threats 3 weeks Performance, Risk and Capability Baseline Assessment • Security capability assessment • IT Service Continuity capability assessment • Rough-cut (qualitative) balanced scorecard performance review 9 weeks 9Prioritise Actions 9 Plan, Do, Check, Act

6. Health Check Critical Success Factors, Challenges & Risks

7. Sound bytes & considerations: With the lack of DR if Mouchel have a catastrophic failure, resulting in widespread data corruption, the downtime could be considerable (weeks) and in some cases no longer have the in-house knowledge to reproduce some services. Most companies cannot tolerate more than a few hours or even minutes of downtime without serious impact to the bottom line. Beyond lost revenue, sporadic outages can cause adverse headlines, lower employee productivity, and negative impact on company valuation How long can Mouchel operate without access to key systems – e.g. email?

8. SAN ENABLER What do the following have in common? Nokia 6100 Nintendo Gamecube Mouchel’s core storage array They are all technology around in 2002 Platform For Change

9. SAN ENABLER This represents the data held on the SAN array that is backed up local to the data centre Remotely stored data adds risk (data loss, security of data) and operational issues (slow/incomplete backups, data ‘sprawl’ and duplicate copies) Only 20-25% of total data is local The rest is held on servers at remote sites and must be backed up across the WAN Platform For Change