Eindpresentatie ba scriptie

18
Open Data: a design for the provisioning of Dutch public and geo-spatial transport data. Bachelor Thesis: Stef van Grieken dinsdag 25 januari 2011

Transcript of Eindpresentatie ba scriptie

Page 1: Eindpresentatie ba scriptie

Open Data: a design for the provisioning of Dutch public and geo-spatial transport data.Bachelor Thesis: Stef van Grieken

dinsdag 25 januari 2011

Page 2: Eindpresentatie ba scriptie

The problem

Government Businesses

dinsdag 25 januari 2011

Page 3: Eindpresentatie ba scriptie

Wat we would like to see

dinsdag 25 januari 2011

Page 4: Eindpresentatie ba scriptie

The value of government data

0 0,5 1,0 1,5 2,0

Scientific Instruments

Textiles

Printing and Publishing

Public Sector Information

% GDP

Source: Commercial Exploitation of Europe’s Public Sector Information - PIRA Study

dinsdag 25 januari 2011

Page 5: Eindpresentatie ba scriptie

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 dataLegal: law gives governments intellectual property, copyright and database rights Technical: there is no technical infrastructure to deliver the data

dinsdag 25 januari 2011

Page 6: Eindpresentatie ba scriptie

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 dataLegal: 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

Page 7: Eindpresentatie ba scriptie

MethodsIs their an economic case for open data?How does government ICT architecture work?

Who is involved in open data?What is their stake?

How does open data infuence the business case of the stakeholders?

How should the data be delivered to businesses?

Literature Review

Stakeholder Indentification

Business case analysis

Requirements analysis

What solution should we design for the data delivery?What specifications should the data warehouse have?

Datawarehouse design

dinsdag 25 januari 2011

Page 8: Eindpresentatie ba scriptie

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

Page 9: Eindpresentatie ba scriptie

Design: Business Model

structured, free, machine

readable dataBusinesses Travellers

dinsdag 25 januari 2011

Page 10: Eindpresentatie ba scriptie

Design: Business Model

structured, free, machine

readable dataBusinesses Travellers

Change pricing and legal

dinsdag 25 januari 2011

Page 11: Eindpresentatie ba scriptie

Design: Business Model

structured, free, machine

readable dataBusinesses Travellers

Change pricing and legal

Create Data Warehouse

dinsdag 25 januari 2011

Page 12: Eindpresentatie ba scriptie

Design: Data Warehouse

Railnetwork Operator (1..n)

Data Warehouse

and Interface

Service Operators

Businesses

Transport Authorities

Roadnetwork Operator (1..n)

Traveler

Rail and Road management

Source Data Raw Data Interpreted Data

Creation, Selection

Warehouse Design

Storage, Processing & Packaging Delivery

Data provider

dinsdag 25 januari 2011

Page 13: Eindpresentatie ba scriptie

Service Operator

Route(.code)

Network Operator(.code)

Vehicle(.code)

Connection(.code)

Stop(.code)

maintains

Distance(.KM)

2 ... 1

Name

Name

Type

Name

Capacity(.INT)

maintains <<

Planning Item(.code)

is served by ... during ...

Departure Time(.timestamp)

Arrival Time(.timestamp)

Direction(.STOP)

Price(.EUR)

Location(.GPS)

Location(.GPS)

is Availible

is Available

is Available

has Disabled Acces

has Toilet

Price(.EUR)

Exception(.code)Description

Planning NoteAlternate

Departure Time(.timestamp)

Alternate Arrival Time

(.timestamp)

*Derived fact type from planning item

price

has << has <<

has <<

has << has

>> containshas has has

has

has

has <<

has << has <<has <<

has

contains <<

Platform(.code)

2 ... 1

has Cateringhas <<

uses <<

has <<

Alternate Platform(.code)

has <<*Derived fact type

from platform

bills for

Title

has <<

Design: Data model

dinsdag 25 januari 2011

Page 14: Eindpresentatie ba scriptie

Service Operator

Route(.code)

Network Operator(.code)

Vehicle(.code)

Connection(.code)

Stop(.code)

maintains

Distance(.KM)

2 ... 1

Name

Name

Type

Name

Capacity(.INT)

maintains <<

Planning Item(.code)

is served by ... during ...

Departure Time(.timestamp)

Arrival Time(.timestamp)

Direction(.STOP)

Price(.EUR)

Location(.GPS)

Location(.GPS)

is Availible

is Available

is Available

has Disabled Acces

has Toilet

Price(.EUR)

Exception(.code)Description

Planning NoteAlternate

Departure Time(.timestamp)

Alternate Arrival Time

(.timestamp)

*Derived fact type from planning item

price

has << has <<

has <<

has << has

>> containshas has has

has

has

has <<

has << has <<has <<

has

contains <<

Platform(.code)

2 ... 1

has Cateringhas <<

uses <<

has <<

Alternate Platform(.code)

has <<*Derived fact type

from platform

bills for

Title

has <<

Design: Data model

dinsdag 25 januari 2011

Page 15: Eindpresentatie ba scriptie

Service Operator

Route(.code)

Network Operator(.code)

Vehicle(.code)

Connection(.code)

Stop(.code)

maintains

Distance(.KM)

2 ... 1

Name

Name

Type

Name

Capacity(.INT)

maintains <<

Planning Item(.code)

is served by ... during ...

Departure Time(.timestamp)

Arrival Time(.timestamp)

Direction(.STOP)

Price(.EUR)

Location(.GPS)

Location(.GPS)

is Availible

is Available

is Available

has Disabled Acces

has Toilet

Price(.EUR)

Exception(.code)Description

Planning NoteAlternate

Departure Time(.timestamp)

Alternate Arrival Time

(.timestamp)

*Derived fact type from planning item

price

has << has <<

has <<

has << has

>> containshas has has

has

has

has <<

has << has <<has <<

has

contains <<

Platform(.code)

2 ... 1

has Cateringhas <<

uses <<

has <<

Alternate Platform(.code)

has <<*Derived fact type

from platform

bills for

Title

has <<

Design: Data model

dinsdag 25 januari 2011

Page 16: Eindpresentatie ba scriptie

Service Operator

Route(.code)

Network Operator(.code)

Vehicle(.code)

Connection(.code)

Stop(.code)

maintains

Distance(.KM)

2 ... 1

Name

Name

Type

Name

Capacity(.INT)

maintains <<

Planning Item(.code)

is served by ... during ...

Departure Time(.timestamp)

Arrival Time(.timestamp)

Direction(.STOP)

Price(.EUR)

Location(.GPS)

Location(.GPS)

is Availible

is Available

is Available

has Disabled Acces

has Toilet

Price(.EUR)

Exception(.code)Description

Planning NoteAlternate

Departure Time(.timestamp)

Alternate Arrival Time

(.timestamp)

*Derived fact type from planning item

price

has << has <<

has <<

has << has

>> containshas has has

has

has

has <<

has << has <<has <<

has

contains <<

Platform(.code)

2 ... 1

has Cateringhas <<

uses <<

has <<

Alternate Platform(.code)

has <<*Derived fact type

from platform

bills for

Title

has <<

Design: Data model

dinsdag 25 januari 2011

Page 17: Eindpresentatie ba scriptie

Discussion

Findings: interviews are consistent with makro economic literature -> businesses expect more competition and increase in innovationFindings: 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 activitiesLegal: 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 governmentPolicy: governments need to be aware that data and services are two different things, planning API’s compete with the market

dinsdag 25 januari 2011

Page 18: Eindpresentatie ba scriptie

Questions

dinsdag 25 januari 2011