Cocktails on the Titanic

Get Started. It's Free
or sign up with your email address
Cocktails on the Titanic by Mind Map: Cocktails on the Titanic

1. PErfect STorm

1.1. Political

1.1.1. Cross party drive for Open & Transparent Govt

1.1.2. Making Public Data Public OS OpenData

1.1.3. Encourage Scrutiny, accountability and innovation

1.1.4. Much of this has geographic context

1.1.5. Increased demand for tools and skills to analyse

1.2. Economic

1.2.1. Pressure on budgets unlike anything seen in last 2 decades

1.2.2. Status quo will be challenged

1.2.3. Increased willingness to consider lower cost solutions

1.3. Social Trends

1.3.1. Culture of Free Internet has brought expectation of free 90+% of 18-24 yr olds have illegal downloads

1.3.2. Spread into the work place - not illegal downloads but attitudes

1.4. Suggest OSS, Open Data and Free or Freeish API's all respond to these trends and combine to to challenge established GI business models

1.4.1. Disaster or Opportunity?

2. Open Data

2.1. Nov 2009, GB Making Public Data Public

2.1.1. TBL & NS

2.2. OS Bombshell

2.2.1. Geonames quote

2.3. Emergence of volunteered GI as fit for many purposes

2.3.1. Responsive to user needs

2.3.2. Depth, breadth and flexibility of attribution

2.3.3. Not authoritative

2.4. Vendors response

2.4.1. Base data will not be enough to sustain a data business (except perhaps a centrally funded OS)

2.4.2. More specialism

2.4.3. Accuracy, currency

2.4.4. DaaS

3. What's going to happen

3.1. Increase in demand for Geoinformation, tools and applications

3.2. Some businesses will adapt and prosper

3.3. New businesses will evolve

3.3.1. Cloud

3.3.2. Open Source

3.3.3. Services more than licenses

3.4. Flurry of innovation and creativity

3.5. Almost certainly some of todays players and leaders will sip Cocktails on the Titanic when they should be remodelling their business

4. Introduction

4.1. What do you do when your market looks like it might be shrinking 10-20%?

4.2. Austerity agenda

4.2.1. Govt represents 50% or more of GI spend for many companies

4.2.2. CSR 25-40% cuts in unprotected depts

4.2.3. Important for people who work in these companies as well as their managers

4.2.4. Important for their customers too!

4.3. Perfect storm for GI coming

4.3.1. Austerity agenda

4.3.2. Collision of business models

4.3.3. Changing social attitudes

4.4. How will you respond?

5. Free

5.1. Expectation of free data and services

5.2. Free or freeish API's from G, M & OSM have responded to or created this demand

5.2.1. Created enormous usage & awareness of geo

5.2.2. Spawned new applications, new businesses & expectations of usability, performance & scalability

5.2.3. Business model does not depend on direct revenue from the service

5.3. Challenge to providers of data s/ware & svcs

5.3.1. This may not be "proper" GI as we know it but it more than does the job

5.3.2. Data & software combined as a service. No infrastructure

5.3.3. Storefinder example

5.4. Vendors response

5.4.1. Will they be stranded in the on premise segment? Security Interoperability with other on premise based systems Inertia

5.4.2. Most vendors responding (albeit late) with cloud based offers Can they match usability, scalability etc? Can they differentiate sufficiently to sustain revenue models?

6. OSS

6.1. Not the Office of Strategic Services that preceded the CIA

6.2. OSS now recognised as viable and cost effective solution in many areas of IT

6.2.1. Feb 2009 UK Govt announces OSS friendly policies Encourage open standards based procurements Reuse of IT systems

6.2.2. Accenture say subscription & mtce costs can be reduced by 70-90% with OSS

6.3. UK implementation of INSPIRE will be OSS based

6.3.1. Developed by OS

6.3.2. Reused by others in PS

6.3.3. Major switch in thinking within govt geo procurement

6.4. Vendor Response

6.4.1. Potentially biggest threat to current business models Attacks on premise stronghold Challenges stable maintenenance revenues that underpin many geo businesses Perhaps leaves desktop as the last stronghold

6.4.2. Switch to more of a services and project based business model Support not maintenance

6.4.3. Move to cloud SaaS model, charge for usage not license