4. The value of government data
Scientific Instruments
% GDP
Textiles
Printing and Publishing
Public Sector Information
0 0,5 1,0 1,5 2,0
Source: Commercial Exploitation of Europe’s Public Sector Information - PIRA Study
dinsdag 25 januari 2011
5. Problem and Causes
Problem: The business potential of government owned transport and
geo-spatial data remains untapped in the Netherlands.
Causes:
Financial: the pricing strategies governments use prevent re-use of
data
Legal: law gives governments intellectual property, copyright and
database rights
Technical: there is no technical infrastructure to deliver the data
dinsdag 25 januari 2011
6. Problem and Causes
Problem: The business potential of government owned transport and
geo-spatial data remains untapped in the Netherlands.
Causes:
Financial: the pricing strategies governments use prevent re-use of
data
Legal: law gives governments intellectual property, copyright and
database rights
Technical: there is no technical infrastructure to deliver the data
We leave this one
alone
dinsdag 25 januari 2011
7. Methods
Is their an economic case for open data?
Literature Review How does government ICT architecture work?
Who is involved in open data?
Stakeholder What is their stake?
Indentification
How does open data infuence the business case
Business case
analysis
of the stakeholders?
How should the data be delivered to businesses?
Requirements
analysis
What solution should we design for the data
Datawarehouse
delivery?
design
What specifications should the data warehouse
have?
dinsdag 25 januari 2011
8. Solution
A new business model for the provisioning of public sector
information (Open Data)
A technical architecture to deliver public transport and geospatial
data to businesses (Data Warehouse)
dinsdag 25 januari 2011
9. Design: Business Model
structured, free,
machine Businesses Travellers
readable data
dinsdag 25 januari 2011
10. Design: Business Model
Change pricing
and legal
structured, free,
machine Businesses Travellers
readable data
dinsdag 25 januari 2011
11. Design: Business Model
Change pricing Create Data
and legal Warehouse
structured, free,
machine Businesses Travellers
readable data
dinsdag 25 januari 2011
12. Design: Data Warehouse
Source Data Raw Data Interpreted Data
Creation, Selection Storage, Processing & Packaging Delivery
Warehouse Design
Service
Operators
Railnetwork
Businesses
Operator (1..n)
Data
Warehouse Traveler
and Interface
Roadnetwork Transport
Operator (1..n) Authorities
Rail and Road
Data provider
management
dinsdag 25 januari 2011
13. Design: Data model
Location
(.GPS)
Location
Type
(.GPS)
has << Capacity
has << has << (.INT)
Name has
has <<
has Disabled Acces
is Available
has Toilet maintains <<
Stop Vehicle
(.code) Service Operator
(.code)
is Available
has <<
has Catering has
has <<
Platform
(.code)
uses << Direction
2 ... 1 (.STOP)
Name
bills for
2 ... 1
is served by ... during ...
maintains
Network
Connection Price
Operator
(.code) (.EUR)
(.code)
has << has <<
is Availible
contains <<
Name Distance Planning Item Route
(.KM)
(.code) (.code)
>> contains
has << has
has has has
Title
has <<
Exception Price
Description Departure Time Arrival Time
(.code) (.timestamp)
(.EUR)
(.timestamp)
has << has << has
*Derived fact type
from platform
*Derived fact type
Planning Note from planning item
Alternate Alternate Alternate Arrival price
Platform Departure Time Time
(.code) (.timestamp) (.timestamp)
dinsdag 25 januari 2011
14. Design: Data model
Location
(.GPS)
Location
Type
(.GPS)
has << Capacity
has << has << (.INT)
has
has Disabled Acces
has Toilet maintains <<
Stop Vehicle
(.code) Service Operator
(.code)
is Available
has Catering has
has <<
Direction
2 ... 1 (.STOP)
Name
bills for
is served by ... during ...
Connection Price
(.code) (.EUR)
dinsdag 25 januari 2011
15. Design: Data model
Location
Type
(.GPS)
has << has
Name
has <<
has Disabled Acce
is Available
has Toilet
Stop
(.code)
is Available
has <<
has <<
Platform
(.code)
uses << Direction
2 ... 1 (.STOP)
2 ... 1
maintains
Network
Connection
Operator
(.code)
(.code)
has << has <<
dinsdag 25 januari 2011 is Availible
16. is Available
has <<
has Catering has
has <<
uses << Direction
2 ... 1 (.STOP)
Name
2 ... 1 Design: Data model is served by ... during ... bills for
maintains
Connection Price
(.code) (.EUR)
has <<
is Availible
contains <<
Distance Planning Item Route
(.KM)
(.code) (.code)
>> contains
has << has
has has has
has <<
Exception Price
on Departure Time Arrival Time
(.code) (.timestamp)
(.EUR)
(.timestamp)
has << has << has
*Derived fact type
Planning Note from planning item
Alternate Alternate Arrival price
Departure Time Time
(.timestamp) (.timestamp)
dinsdag 25 januari 2011
17. Discussion
Findings: interviews are consistent with makro economic literature ->
businesses expect more competition and increase in innovation
Findings: cost structures change at the ‘government’ stakeholder,
data providing organizations need to be compensated for loss due to
different pricing strategies, or they are forced to drop certain activities
Legal: intellectual property of some businesses loses value (i.e.
Kadaster vs. Tele Atlas)
Legal: insuring coverage, quality, privacy and neutrality of data
provided by the government
Policy: governments need to be aware that data and services are two
different things, planning API’s compete with the market
dinsdag 25 januari 2011
