You are on page 1of 20

Government Infrastructure as a Service (IaaS)

Infrastructure services for Government

Whitepaper Brian More


Chief Architect,
Government Technology Services.

Contributors: Danny Mollan (GTS)


Scott Rodgers (GTS)
Andy Gray (MED)
Graeme Davies (LINZ)

14th May 2010

Commercial: In Confidence Not Government Policy – For Discussion Purposes Only


Contents

• Our Vision ………... 3

• Desired outcomes ………... 4

• Principles ………... 5-7

• Our Infrastructure as a Service in context ………... 8-9

• The expected IaaS components ………... 10-15

• Value Add Services and Evolution ………... 16

• Achieving our IaaS vision ………... 17

2
Commercial: In Confidence Not Government Policy – For Discussion Purposes Only
Our Vision

A sustainable Government Common ICT Infrastructure


capability that achieves increased efficiency and effectiveness.

3
Commercial: In Confidence Not Government Policy – For Discussion Purposes Only
Desired outcomes

 Reduced Government ICT Infrastructure and management costs

 Reduced demand on capital expenditure

 Improved capability for agencies to deliver better services

 Improved resilience and security of government infrastructure

 Improved ability to upgrade services through both standardisation and virtualisation

 Be a catalyst for further innovation from infrastructure suppliers

 Better utilisation of expert resources in a “denser” core

 Agency managed demand with cost transparency through use-based charging

 Improved agency ability to focus on business, and less on infrastructure provision

4
Commercial: In Confidence Not Government Policy – For Discussion Purposes Only
Principles (1
(1 of
of 3)
3)

Our vision is underpinned by several key principles:

• Membership

– The service is available to New Zealand Government agencies and local authorities

– All members will have a voice (e.g. a vote) regarding changes in the scope and
characteristics of the service, overarching governance will remain with GTS

– Members only pay for what they use and receive scale benefits in-line with growth

• Shared

– Services (and associated users) share a pool of resources for economies of scale

– Dedicated resource pools (e.g. Top Secret security classifications) may exist

– Sharing implies a high degree of service commoditisation

5
Commercial: In Confidence Not Government Policy – For Discussion Purposes Only
Principles (2
(2 of
of 3)
3)

• Scalable and Elastic

– The service can scale up and down in response to changes in demand

– Scalability and elasticity apply to the economic model as well as the underlying
resources

• Metered by Use

– Pay-as-you-go e.g. a utility model rather than the cost of hardware / software

– Multiple price plans may be appropriate. These may include different allocation
models, and plans for different levels of service

– Agency specific and transparent charging

6
Commercial: In Confidence Not Government Policy – For Discussion Purposes Only
Principles (3
(3 of
of 3)
3)

• Service Based

– The service is defined in terms of outcomes (quality, response time, price etc.)
rather than in terms of technology and its associated capability

– The implementation details are hidden

• Industry Standard Quality

– The underlying infrastructure, it’s qualities, and overall services provided meet
industry standard quality

– The capability will meet Government Security standards

7
Commercial: In Confidence Not Government Policy – For Discussion Purposes Only
Our Infrastructure as a Service in context (1
(1 of
of 2)
2)

People, Devices and Things


Citizens, Agencies, Employees, e.g. End User Computing
and Partners
The networks that connect
our citizens, agencies,
employees and partners,
ONE.Govt Other with each other and to the
Network Networks Networks services we supply and
aggregate e.g. the one.govt
Network
Government Infrastructure as a Service (IaaS)
 Common Government Infrastructure environment
A Government
 Flexible on-demand Infrastructure capability Infrastructure capability to
accommodate all of our
 Pay-as-you-go infrastructure needs
 Housing, Servers, Storage, and Networking
 Fit for purpose, Secure, Robust, DR capable
 Industry-grade Service Management

 Positioned for incremental Value Added Services


 Common application services e.g. Email

Image Source: Green Data Center flicker.com

8
Commercial: In Confidence Not Government Policy – For Discussion Purposes Only
Our Infrastructure as a Service in context (2
(2 of
of 2)
2)

Citizens, Agencies, Employees,


and Partners

ONE.Govt Other
Network Networks Networks

Government Infrastructure as a Service (IaaS)


 Agency  Environment:  Service
Provided  Virtual Servers Management:
Hardware  High
Availability  Infrastructure
 Disaster Management
 Virtual Multi-Tier Storage Recovery  Transition
 Security  Reporting
 Facilities  Billing
 Housing / Data Centre Management

Networking …. ….

9
Commercial: In Confidence Not Government Policy – For Discussion Purposes Only
The expected IaaS components (1
(1 of
of 6)
6)

Infrastructure Environmentals Service


Management
1 2 3
The foundation The non-
capabilities functionals and Industry
standard
Relationship qualities of the service
environment management
4
The relationship
qualities

Government Infrastructure as a Service (IaaS)


 Agency  Environment:  Service
Provided  Virtual Servers Management:
Hardware  High
Availability  Infrastructure
 Disaster Management
 Virtual Multi-Tier Storage Recovery  Transition
 Security  Reporting
 Facilities  Billing
 Housing / Data Centre Management

Networking …. ….

10
Commercial: In Confidence Not Government Policy – For Discussion Purposes Only
The expected IaaS components (2
(2 of
of 6)
6)

We envisage several key components will comprise Government IaaS:

1. Infrastructure:

1. Housing / Data Centre: NZ Data centres will be provided to host the underlying IaaS components and any
Agency Provided Hardware. Production, Development, and Test environments (etc.) are supported. We desire
an infrastructure capability aligned to good practices standard such as TIA-942* Data Centre Standards.

2. Virtual Multi-Tier Storage: The core offering will implement a virtual storage platform.

3. Virtual Servers: The core offering will implement a virtual server platform.

4. Agency Provided Hardware: Appropriate caged areas and facilities management is provided to support
specialised Agency Provided Hardware that can not be moved into the native IaaS environment.

5. Networking: Foundation networking is provided. This includes specialised cabling and patching into Agency
Provided Hardware and network providers as requested. We desire our IaaS environment is also capable of
supporting timely transition to IPv6.

* Telecommunications Industry Association (TIA) Data Centre Standard.


Provided only as an example of the level of quality standard we desire.
Please refer Appendix 11 for further detail.

11
Commercial: In Confidence Not Government Policy – For Discussion Purposes Only
The expected IaaS components (3
(3 of
of 6)
6)

2. Environmentals:

1. High Availability: We expect built in resiliency and a fault tolerant environment for our production
environments. We desire High Availability as an optional quality for servers and storage. This includes a
geographically diverse High Availability option.

2. Disaster Recovery: We expect a Disaster Recovery capability able to rapidly recover from component failure,
a primary data centre failure, or localised geographic disaster.

3. Security: We expect conformance to Government Security Standards.

4. Facilities Management: We desire comprehensive facilities management with optimised energy efficiency
and facility performance - facilities that are well operated and with a level of Green Technology thinking.

12
Commercial: In Confidence Not Government Policy – For Discussion Purposes Only
The expected IaaS components (4
(4 of
of 6)
6)

3. Service Management:

1. Service and Infrastructure Management: The service provider will provide quality service and infrastructure
management aligned to industry practices such as COBIT* and ITIL**. The provider’s approach to
infrastructure and service management must support the seamless integration of agency processes such as
fault and incident management i.e. can support seamless end-to-end service management. Example sub-
practices should include but are not limited to;

1. Server Management
2. Data and Storage Management (including Backup / Restore)
3. Network Management (including Topology Management)
4. Service Desk
5. Configuration and Patch Management
6. Change and Release Management
7. Incident and Problem Management
8. Provisioning Management
9. User and Account Management (i.e. server access)
10. Capacity Management
11. Performance Management
12. Security Management
* Control Objectives for Information and related Technology (COBIT).
** Information Technology Infrastructure Library (ITIL)

13
Commercial: In Confidence Not Government Policy – For Discussion Purposes Only
The expected IaaS components (5
(5 of
of 6)
6)

3. Service Management (continued):

2. Transition: It is envisaged the IaaS provider could provide each participating agency with transition consulting
and migration services onto the platform e.g. we expect the supplier to complete a transition plan for all
identified agencies. We also desire options that may include vendor procurement; the ability to transfer existing
assets into the service including purchase of agency assets by supplier.

3. Reporting: We desire simple and transparent reporting on key aspects of our IaaS operations. This is in
terms of use, provision response, and operational performance.

4. Billing: This includes the transparent invoicing of services provided to agencies.

14
Commercial: In Confidence Not Government Policy – For Discussion Purposes Only
The expected IaaS components (6
(6 of
of 6)
6)

4. Relationship:

1. Relationship Management: We desire a provider who can form long term relationships with the participating
agencies and their authorised 3rd party providers. We envisage three key models:

• Agency Managed: A provider relationship / interface with the authorised agency management team

• 3rd Party: A provider relationship / interface with the authorised 3rd party management team (of the agency)

• Hybrid: A provider relationship / interface combination of agency and identified 3rd party resources

2. Financial Management: We desire absolute transparency in our providers financial management discipline.
In particular ensuring that the IT infrastructure is obtained at the most effective price.

3. Governance and Compliance: We desire a governance model that supports the dynamic needs of individual
agencies while ensuring overarching Government unity, solution compliance to standards and agreements, and
clarity for the long term common capability evolution.

15
Commercial: In Confidence Not Government Policy – For Discussion Purposes Only
Value Added Services and Evolution

• Transformation: As a potential Value Added Service to our IaaS base-case we are


open to further suggestions inside this environment. As an example other providers
may potentially supply Common Application Services such as Email, Web, or Enterprise
Applications.

• Innovation: While we desire scope-control on delivery of IaaS we are however open to


further innovative solutions / services that may be provided as part of the proposition.

16
Commercial: In Confidence Not Government Policy – For Discussion Purposes Only
Achieving our IaaS vision

 We seek supplier/s that can demonstrate their ability to achieve our vision

 We desire a relationship that can sustain the test of time

 We desire an economic approach that considers scale and scope and reduces cost to
agencies as volume increases

 We require a quality transition that rapidly implements the identified agency capabilities
into the new Government IaaS environment

 Our next steps are to refine our Request For Information and progress to market

17
Commercial: In Confidence Not Government Policy – For Discussion Purposes Only
Appendices

18
Commercial: In Confidence Not Government Policy – For Discussion Purposes Only
Appendix 1: TIA-942 Data Centre standards
• TIA-942 Data Centre Standard provided as example only. We desire an infrastructure capability aligned to similar best practice standards.

Tier Level TIA-942 qualities summary


1 • Susceptible to disruptions from both planned and unplanned activity
• Single non-redundant distribution path serving the equipment
• Basic site infrastructure guaranteeing 99.671% availability (28.8 hours annual downtime)
2 • Achieves all Tier 1 requirements
• Less susceptible to disruption from both planned and un-planned changes
• Single path for power and cooling disruption, includes redundant components
• Redundant site infrastructure capacity components guaranteeing 99.741% availability (22 hours annual downtime)
3 • Achieves all Tier 1 and 2 requirements
Our minimum desired quality level

• Enables planned activity without disrupting computer hardware operation, but unplanned events will still impact
• Multiple independent distribution paths serving the equipment
• All equipment must be dual-powered and fully compatible with the topology of a site's architecture
• Concurrently maintainable site infrastructure guaranteeing 99.982% availability (1.6 hours annual downtime)
4 • Achieves all Tier 1, 2, and 3 requirements
• Planned activity does not disrupt critical load and data centre can sustain at least one worse-case unplanned event
• Multiple active power and cooling distribution paths, includes redundant components
• Fault tolerant site infrastructure with electrical power storage and distribution facilities guaranteeing 99.995% availability (0.4 hours
annual downtime)
Further Information: http://www.adc.com/us/en/Library/Literature/102264AE.pdf

19
Commercial: In Confidence Not Government Policy – For Discussion Purposes Only
Appendix 2: IaaS Document Hierarchy

Government
Infrastructure as a Service
- Service Vision

Government IaaS high level


Whitepaper (this document) requirements document

20
Commercial: In Confidence Not Government Policy – For Discussion Purposes Only