Open Architectures- Lessons from the Public Sector

33
www.linuxit.com Open Architectures Lessons From the Public Sector

description

A look at how the private sector can get best practice advice, learn from the public sector and avoid the vicious cycle of vendor lock-in while benefiting from the transformation towards open architectures.

Transcript of Open Architectures- Lessons from the Public Sector

Page 1: Open Architectures- Lessons from the Public Sector

www.linuxit.com

Open Architectures Lessons From the Public Sector

Page 2: Open Architectures- Lessons from the Public Sector

www.linuxit.com

Open Standards: Open Opportunities - flexibility and efficiency in government IT

From 1st November 2012 Francis Maude, Minister for Cabinet Office, announced that all government bodies must comply with Open Standards Principles, an agreed set of standards to make government IT more open, more cost-effective and better connected.

Page 3: Open Architectures- Lessons from the Public Sector

www.linuxit.com

Open Standards: Open Opportunities - flexibility and efficiency in government IT

Government must be better connected to the people it serves and partners who can work with it - especially small businesses, voluntary and community organisations. Having open information and software that can be used across government departments will result in lower licensing costs in government IT, and reduce the cost of lock-in to suppliers and products.

- Francis Maude

Page 4: Open Architectures- Lessons from the Public Sector

www.linuxit.com

DefinitionsAn Open Standard is a publicly available standard - often for interfaces - such that systems that comply with it should be able to interoperate appropriately.

Page 5: Open Architectures- Lessons from the Public Sector

www.linuxit.com

DefinitionsAn Open Standard is a publicly available standard - often for interfaces - such that systems that comply with it should be able to interoperate appropriately.

An Open Architecture applies to a system in which the architecture is published in sufficient detail to enable change and subsequent evolution through the introduction or replacement of modules and/or components from any supplier.

Page 6: Open Architectures- Lessons from the Public Sector

www.linuxit.com

A world without standards

Page 7: Open Architectures- Lessons from the Public Sector

www.linuxit.com

A world without standards

What would the world be like without standards? Imagine if when you bought a car you could only use fuel from a certain garage. You have a Shell garage within a couple of miles of your house so you buy a car that can run on Shell fuel.

Page 8: Open Architectures- Lessons from the Public Sector

www.linuxit.com

A world without standards

What would the world be like without standards? Imagine if when you bought a car you could only use fuel from a certain garage. You have a Shell garage within a couple of miles of your house so you buy a car that can run on Shell fuel.

Now what happens if Shell decide to push their prices up out of line with the other fuel vendors? Well you could change your car in protest but the cost of change would likely outweigh the benefit you might yield from an alternative vendor.

Page 9: Open Architectures- Lessons from the Public Sector

www.linuxit.com

A world without standards

What would the world be like without standards? Imagine if when you bought a car you could only use fuel from a certain garage. You have a Shell garage within a couple of miles of your house so you buy a car that can run on Shell fuel.

Now what happens if Shell decide to push their prices up out of line with the other fuel vendors? Well you could change your car in protest but the cost of change would likely outweigh the benefit you might yield from an alternative vendor.

And what if you wanted to move house and the nearest Shell station was 50 miles away? The hassle and expense of incorporating a 100 mile round trip to fill the car up, or the cost of changing the car might be enough to persuade you not to move. You’re locked in.

Page 10: Open Architectures- Lessons from the Public Sector

www.linuxit.com

Locked inVendor lock-in is when customers are dependent on a single manufacturer or supplier for products and cannot move to another vendor without substantial costs and/or inconvenience.This dependency is typically a result of standards that are controlled by the vendor.

Page 11: Open Architectures- Lessons from the Public Sector

www.linuxit.com

Locked inVendor lock-in is when customers are dependent on a single manufacturer or supplier for products and cannot move to another vendor without substantial costs and/or inconvenience.This dependency is typically a result of standards that are controlled by the vendor.

The term is commonly used in the computer industry to refer to the situation that can occur due to a lack of compatibility between different hardware, operating systems or file formats. Such incompatibility can be intentional or unintentional.

Page 12: Open Architectures- Lessons from the Public Sector

www.linuxit.com

The costs of lock-in can be severe. They can include:

Page 13: Open Architectures- Lessons from the Public Sector

www.linuxit.com

The costs of lock-in can be severe. They can include:

Substantial inconvenience and expense of converting data to other formats and converting to more efficient, secure and inexpensive application programs and operating systems.

Page 14: Open Architectures- Lessons from the Public Sector

www.linuxit.com

A lack of bargaining ability to reduce prices and improve service.

The costs of lock-in can be severe. They can include:

Substantial inconvenience and expense of converting data to other formats and converting to more efficient, secure and inexpensive application programs and operating systems.

Page 15: Open Architectures- Lessons from the Public Sector

www.linuxit.com

Vulnerability to forced upgrades.

A lack of bargaining ability to reduce prices and improve service.

The costs of lock-in can be severe. They can include:

Substantial inconvenience and expense of converting data to other formats and converting to more efficient, secure and inexpensive application programs and operating systems.

Page 16: Open Architectures- Lessons from the Public Sector

www.linuxit.com

The corruption, or even loss, of critical data while attempting to convert it.

Vulnerability to forced upgrades.

A lack of bargaining ability to reduce prices and improve service.

The costs of lock-in can be severe. They can include:

Substantial inconvenience and expense of converting data to other formats and converting to more efficient, secure and inexpensive application programs and operating systems.

Page 17: Open Architectures- Lessons from the Public Sector

www.linuxit.com

The corruption, or even loss, of critical data while attempting to convert it.

Vulnerability to forced upgrades.

A lack of bargaining ability to reduce prices and improve service.

The costs of lock-in can be severe. They can include:

The best way for an organisation to avoid becoming a victim of vendor lock-in is to use products that conform to free, industry-wide standards.

Substantial inconvenience and expense of converting data to other formats and converting to more efficient, secure and inexpensive application programs and operating systems.

Page 18: Open Architectures- Lessons from the Public Sector

www.linuxit.com

Vendor Lock-in Vicious Cycle

Page 19: Open Architectures- Lessons from the Public Sector

www.linuxit.com

Vendor Lock-in Vicious Cycle

Evaluate closed standards software from Vendor X without consideration of switching costs

Page 20: Open Architectures- Lessons from the Public Sector

www.linuxit.com

Vendor Lock-in Vicious Cycle

Evaluate closed standards software from Vendor X without consideration of switching costs

Buy closed standards software from Vendor X

Page 21: Open Architectures- Lessons from the Public Sector

www.linuxit.com

Vendor Lock-in Vicious Cycle

Evaluate closed standards software from Vendor X without consideration of switching costs

Buy closed standards software from Vendor X

Organisational requirements change/develop

Page 22: Open Architectures- Lessons from the Public Sector

www.linuxit.com

Vendor Lock-in Vicious Cycle

Evaluate closed standards software from Vendor X without consideration of switching costs

Additional functionality required from Vendor X is very expensive and/or not best fit £££££

Buy closed standards software from Vendor X

Organisational requirements change/develop

Page 23: Open Architectures- Lessons from the Public Sector

www.linuxit.com

Vendor Lock-in Vicious Cycle

Evaluate closed standards software from Vendor X without consideration of switching costs

Preferable solution from Vendor Y is not interoperable with Vendor X software

Additional functionality required from Vendor X is very expensive and/or not best fit £££££

Buy closed standards software from Vendor X

Organisational requirements change/develop

Page 24: Open Architectures- Lessons from the Public Sector

www.linuxit.com

Vendor Lock-in Vicious Cycle

Evaluate closed standards software from Vendor X without consideration of switching costs

Preferable solution from Vendor Y is not interoperable with Vendor X software

Switching costs to Vendor Y + Vendor Y software costs > than Vendor X software costs

Additional functionality required from Vendor X is very expensive and/or not best fit £££££

Buy closed standards software from Vendor X

Organisational requirements change/develop

Page 25: Open Architectures- Lessons from the Public Sector

www.linuxit.com

Vendor Lock-in Vicious Cycle

Evaluate closed standards software from Vendor X without consideration of switching costs

Preferable solution from Vendor Y is not interoperable with Vendor X software

Switching costs to Vendor Y + Vendor Y software costs > than Vendor X software costs

Additional functionality required from Vendor X is very expensive and/or not best fit £££££

Add to that a reluctance to change due to incumbent skills and relationships

Buy closed standards software from Vendor X

Organisational requirements change/develop

Page 26: Open Architectures- Lessons from the Public Sector

www.linuxit.com

It’s not about the mandate

The mandate has doubtless caught the attention of many government organisations but most are motivated by the

carrot not the stick.

Simon Mitchell, Executive DirectorStrategy & Transformation at Linux consulting firm LinuxIT

Page 27: Open Architectures- Lessons from the Public Sector

www.linuxit.com

BenefitsIndependent research* into the specific benefits of the policy identified the following:

* Centre for Intellectual Property & Policy Management at Bournemouth University

Page 28: Open Architectures- Lessons from the Public Sector

www.linuxit.com

BenefitsIndependent research* into the specific benefits of the policy identified the following:

01. Reduction in lock-in and associated switching costs

* Centre for Intellectual Property & Policy Management at Bournemouth University

Page 29: Open Architectures- Lessons from the Public Sector

www.linuxit.com

BenefitsIndependent research* into the specific benefits of the policy identified the following:

01. Reduction in lock-in and associated switching costs

02. Reduction in the

size and duration of

IT projects and the

sharing and reuse of

IT across departments

* Centre for Intellectual Property & Policy Management at Bournemouth University

Page 30: Open Architectures- Lessons from the Public Sector

www.linuxit.com

BenefitsIndependent research* into the specific benefits of the policy identified the following:

01. Reduction in lock-in and associated switching costs

02. Reduction in the

size and duration of

IT projects and the

sharing and reuse of

IT across departments

03. Encouraging innovation and opportunities for smaller companies to participate in contracts

* Centre for Intellectual Property & Policy Management at Bournemouth University

Page 31: Open Architectures- Lessons from the Public Sector

www.linuxit.com

BenefitsIndependent research* into the specific benefits of the policy identified the following:

* Centre for Intellectual Property & Policy Management at Bournemouth University

01. Reduction in lock-in and associated switching costs

02. Reduction in the

size and duration of

IT projects and the

sharing and reuse of

IT across departments

03. Encouraging innovation and opportunities for smaller companies to participate in contracts

04. Improving

business and

consumer interface

with government.

Page 32: Open Architectures- Lessons from the Public Sector

www.linuxit.com

Private Sector Benefits

The private sector has no mandate, but never have organisations been more motivated to reduce costs, drive innovation and improve their customers’ experience. These benefits are all available with transformation towards Open Architectures. Councils, Police forces, NHS Trusts and academic institutions are already on the journey.

Page 33: Open Architectures- Lessons from the Public Sector

www.linuxit.com

To find out more about open architectures, download our free eGuide: Open architectures - is your organisation ready?

Download Now