Overview of Current Status: Shared Services Canada

1. Overview of Current Status:Shared Services Canada Presentation to the Information Technology Infrastructure Roundtable November 22, 2012 LiseanneForand, President

2. Context • Purpose • To provide an overview of the current status of Shared Services Canada (SSC) • Outline • SSC – A new organization • Mandate • Current state • A Year of Experience • Maintaining Operations • Planning Transformation • Stakeholder Relationships • The Way Forward • People • Process • Technology 2

3. A New Organization with an IT Focus Budget 2011 Standardize Consolidate Re-engineer • Shared Services Canada • Created on August 4, 2011 • Mandated to deliver email, data centre and network/telecom services to 43 Government of Canada institutions representing 95% of the federal IT infrastructure spending • Budgets, people, assets and contracts transferred to SSC in November 2011 • Full accountability for the infrastructure on April 1, 2012 • Shared Services Canada Act, Royal Assent, June 29, 2012 • Raison d’être • Reduce costs • Improve Security • Maximize Efficiencies • Minimize Risks 3

4. Current State of IT across Government of Canada Highly complex, costly and less secure than desired Mission-critical programs highly dependent on infrastructure Issues persist and are barriers to government priorities • 63 email systems • 19 large data centres • 65 medium-sized data centres of varying quality, security and energy efficiency; • hundreds of smaller “closets”; • 50 wide area networks connecting over 3000 buildings and data centres –over 1000 firewalls; • less than 100 buildings with wireless WAN services; • over 110,000 people with 2 phones; • over 1000 PBX and key systems; • largely in-sourced • 2100 mission-critical, mandate-specific systems that span: • key benefits programs (e.g. employment and pension benefits) • security (e.g. national defence and national policing systems and provincial police force databases, CBSA border systems, and Public Safety cyber security and Emergency Response); • safety and health (e.g. food monitoring, health science labs, weather systems, seismic systems); • farmers and students (agriculture innovation, student loan programs) • finance systems (e.g federal-provincial tax and benefit systems, money laundering) • connectivity that ensures safe access to government, programs, citizens and protects information • Current state of IT infrastructure: • is complex, old and expensive • is a long-term unfunded liability • is vulnerable to availability and performance issues • is a barrier to business system renewal, modernization and agility • has uneven quality of service • has some resiliency soft spots • is not service oriented • Procurement practices that limit innovation. 4

5. A Year of Experience • Mandate • Maintain operations • Transform IT infrastructure services • Generate savings • Year One • Establish new department • Consolidate people, money, assets, contracts and projects • Keep the lights on: 2100 mission critical systems • Initiate three transformation programs • New legislation, including procurement authorities • Establishing governance and partner relationship management

6. Maintaining Operations • Status • Wide diversity: capacity, infrastructure and support • Vulnerabilities across the system • Lessons being learned • Incident analysis • Change management requirements • Interdepartmental linkages • Moving to • Problem management – root cause analysis • Tilting: from vertical to horizontal

7. Planning Transformation • Email Transformation Initiative (ETI) • Industry engagement phase completed in July 2012 • Procurement phase underway • Email solution to be identified in March 2013 followed by implementation and migration • Data centre consolidation and telecommunications transformation • Identifying the current state • Designing the end state • Scope, scale, pace and sequencing of change • Videoconferencing and Travel Policy • Follow-up to Budget 2012 • Industry Day on November 30 (TBD) 7

8. Stakeholder Relationships • Business Continuity Framework Agreements • Business Arrangements • Service level monitoring and reporting • Governance • Engagement

9. The Way Forward: Continuity but not Status Quo • Over the next year, focus will be on accelerating enterprise driven activities • People • More intense and structured ICT sector engagement • Work with federal partners on readiness for implementation of new email system • Proactively engaging employees in designing future • Process • Procurement best practices • Staging an agile change management • Technology • Greater focus on transformation agenda • Greater emphasis on root cause analysis and resolution with respect to operational issues