mobiwallet - italian pilot

42
[ [ MobiWallet Italian Pilot Giuseppe Biasu- Intecs spa

Upload: giuseppe-biasu

Post on 12-Apr-2017

309 views

Category:

Presentations & Public Speaking


0 download

TRANSCRIPT

[ [

MobiWallet

Italian Pilot

Giuseppe Biasu- Intecs spa

2

INDEX

Part 1. RP2 developments and current status • Overview • Specific objectives and challenges • Developments • Role of the partners • Current status • Promotion & Recruitment • Problems & solutions. Lessons learnt.

Part 2. Pilot presentation: Demo

• Key elements • Services • How the systems works etc. • Videos.

Overview

3

Partners:

Modes involved:

Key Technologies: Web, QR-code, SMS, credit cards, mobile credit, PayPal.

Where: Pisa and Scandicci

(Florence) – Tuscany - Italy

Letters of support:

Scope

4

Urban bus

Bike sharing (Pisa)

Car parking area (about 100 slots)

near the Resistenza tram stop in

Scandicci-Florence (Park&Ride)

Car-pooling

(60+ shared journeys)

300+ registered users

230+ transactions

Feedback received from users

Key achievement

Modes Additional services

Bus traffic flow monitoring

Statistics

Trip planning

Integration with existing

services/Interoperability

Specific Objectives &

Challenges

5

• The pilot aims to propose an integrated platform which allows end-users to

access to a wide-set of transport services and related payment modes.

• Target users: commuters and tourists in Pisa and Florence.

• Users can buy public transports tickets as well as share their private car with

other registered users through an innovative car-pooling functionality.

• Several payment modes available (PayPal, user’s mobile credit, credit cards

etc.), different technologies (web, Android apps) and different types of tickets

(SMS, QR-code).

• The platform is web based and provides the payment services directly (via a

normal browser) or through specific Android apps developed by Italian

partners.

• The platform integrates also value added service like traffic flow control and

statistics retrieved during trial phase.

Overview

6 6

Developments

• Completion of all deployments in Scandicci and Pisa (beginning of July 2015).

• FAT/SAT campaign related to deployed components.

• Car-sharing: implementation of additional functionalities (user’s feedback).

• SIMIS Web APIs for integration with existing services & interoperability.

• 1st pilot demonstration (9-10 July 2015 Pisa & Florence).

• Development of additional functionalities i.e. security (https), Statistics in

SIMIS. Bug fixing+no regression test.

• Dissemination-user recruitment (on going): reached 200 end users by the end

of November 2015 (300 at the beginning of February).

• Interoperability with Serbian Pilot.

7

Developments

8

feb-15 mar-15 apr-15 mag-15 giu-15 lug-15 ago-15 set-15 ott-15 nov-15 dic-15 gen-16 feb-16

M13 M14 M15 M16 M17 M18 M19 M20 M21 M22 M23 M24 M25

Deployment (Pisa) including FAT/SAT testing phase

Implementation (bus traffic monitoring)

New functionalities (car-pooling functionalities, web APIs)

New functionalities (i.e. trip planning, statistics, dynamic fee etc.)

Deployment (Scandicci)

Implementation (Park&Ride app)

Test (FAT/SAT)

New functionalities (i.e. PIN code ticketing)

Bug fixing + overall no regression tests.

User recruitment/promotional initiatives

Serbian Pilot Interoperability

Spanish Pilot Interoperability

UK Pilot Interoperability

2nd Reporting period

I pilot demonstrationRP2 start II pilot demonstration

RP2 end

Role of the partners

9

Partner Role

Intecs spa

(Technical)

• Pilot coordination. • Technology provider (SIMIS, PisaBus app, HW). • Deployment (Pisa).

CNR

(Research)

• Car pooling functionalities. • Traffic flow sensors + deployment (Pisa). • Contact with stakeholders (i.e.PisaMO).

• Dissemination.

Aleph srl

(SME-Technical)

• Deployment in Scandicci (Florence). • MobiTickt Android app (Park&Ride). • Contact with Municipalities and other stakeholders

(Scandicci town hall, Park manager etc.).

Comune

Firenze

(Municipality)

• Contact with Florence transport company and stakeholders (tourism, sport).

• Dissemination. • Support in legal and administrative issues.

GEST Tramvia

spa

(Transport

company)

• Deployment in Scandicci tram stop (Resistenza),

• Dissemination and promotion. • Contacts with stakeholders (i.e. ticketing machine

service provider etc.).

Current status

November 2015 January 2016 February 2016

Modes involved:

• Urban bus ticket (Pisa)

• Park &Ride (Scandicci-

Florence). • Car pooling. • Bike sharing

(Pisa).

ALL ALL

Number of users:

194 256 332

Number of transactions:

109 181 229

10

Promotion &Recruitment

11

• GEST: Light Rail Awards (London 2015): best customer initiative award.

• Several press releases (CNR, GEST).on local newspapers.

• ComFI press release: Stefano Giorgetti, Councillor for public works, infrastructure projects, roads and

maintenance, local public transport (Florence Municipality).

• Involvement of ComFI mobility manager (target: ComFI employers), communications have been made to

more than 4,000 people.

• Intecs: Article on “Il Sole 24 ore” (Italian financial newspaper).

• Aleph/ComFI: Florence marathon: prepared a brochure (ENG/ITA) to invite participants and volunteers to

join the trial.

• ALL

• Dissemination on social networks (i.e. Facebook, LinkedIn, Twitter).

• Several planned promotional initiatives (i.e. free tickets) related to Pisa/Florence events.

Services

Additional

Services

Integration

with existing

Services/APP

• Touristic bus traffic flow monitoring (Pisa)

• Trip planning.

• Statistics.

Top-up &

clearing Validation

Fare

Calculation Interfaces

Core Services (Fare management

and validation)

• Pisa bus Android app.

Payment by PayPal

merchant account with

Credit Card or mobile

credit (cash as well).

Core Services

(Some) transaction

details are stored in

SIMIS DBMS (*).

Use transport mode.

Bike-sharing:

service provider’s

card is mandatory.

Clearing process provided by

entities not included in the

cluster (i.e. PayPal, mobile

operators, transport

companies) or user’s PayPal

account (car-sharing)...

Top-up &

clearing

(*) i..e type of ticket, date&time,

userId etc. IMPORTANT: No

financial data is stored in SIMIS

(ie.bank account, PayPal passwords,

PIN codes etc.).

Bus, tram, car-

parking: User

receives the ticket

(SMS, QR-code)

on his/her mobile.

User tops up his/her Smartphone, logs

in SIMIS and plans a journey selecting

the appropriate transport mode (or

alternatively launches the specific app).

Payment could be performed through

SIMIS itself or, depending by selected

service, through the apps.

14

User taps “Buy” button from SIMIS, launches PisaBus app and pays the ticket with his/her mobile credit..

Core Services Validation

Ticket is validated once received by user.

User shares his/her car or finds a user who already shared a journey and joins a shared travel.

Reimbursement can be performed through PayPal (or cash).

SMS ticket is verified by ticket inspector once user is on-board.

Driver pays parking time to PayPal merchant account through MobiTickt app or via the signage totem deployed in the car-parking area in Scandicci.

15

Core Services Validation

Payment is verified by parking staff through a version of MobiTickt app which checks car’s plate.

SMS tram ticket is purchased through MobiTickt app Car’s plate is stored in parking

operator system once user registers to the service.

Service is integrated within SIMIS. User rents the bike through his/her credit card on service provider’s payment area.

Core Services Fare

Calculation

• Public transports: fares are set by transport companies.

• SIMIS proposes an estimated cost which is automatically calculated when a user joins a

car-sharing journey.

• The estimation cost takes in account the distance, number of passengers on board and

considers also an (estimated) price of the fuel (€/lt.).

• However, since car-sharing it’s a private agreement between users, the actual price agreed

between the subjects involved (driver and passengers) could be different than the

estimated cost.

Core Services

Interfaces

Traveller Interface: car pooling

Traveller Interface: car pooling

Core services

Traveller Interface: Bike sharing service (Pisa)

Bike sharing service is available on SIMIS Trip planning. User can display station’s location on trip planning map.

Payment could be performed through the service provider’s payment web area and credit card.

Core Services

Interfaces

Traveller Interface: “Park &Ride” MobiTickt app

Core services: Park &Ride area

(Scandicci-Florence)

In collaboration with

Resistenza tram stop

Signage totem deployed in car-parking

Core Services

Interfaces

Other interfaces: Web REST APIs

Available functionalities :

• User registration.

• SMS ticket request (for Pisa and Scandicci urban

transports).

• User’s feedback about the transport service.

• Notification of purchased ticket (in case the end-

user have bought the ticket via his/her mobile’s

credit).

• A recovery mechanism in case the ticket (the

sms) has not been delivered to the end user due

technical issues.

All data exchanged with SIMIS are secured (via

https) and also available in JSON format.

SIMIS provides a full set of functionalities in order to allow 3rd part application to

easily access to Italian pilot services.

22

Using the system (1/3)

Urban bus (Pisa)

User taps “Buy bus ticket” button from SIMIS, launches the PisaBus app

User receives the SMS ticket on his/her mobile. Ticket details are stored in SIMIS,

User purchases the ticket via mobile credit.

23

Using the system (2/3)

User shares his/her car or …

Journey reimbursement through PayPal

Car pooling

… searches journeys shared by other users

Search results. Journey confirmation

24

Using the system (3/3)

Payment is verified by parking staff through a version of MobiTickt app which checks car’s plate.

User purchases a ticket (SMS) via mobile credit

Park & Ride (Scandicci- Florence)

User taps “Park&Ride” button from SIMIS, launches the Mobitickt app

15:4515:4515:45

Welcome!

Sign in

Sign In with Google

Email

Create password

or

Do you already have an account?

April 2015

Yesterday - 16:00 - € 3,000

15:45

Scandicci - Via dei Turri

Saturday, April 4th - 15:00 - € 2,000

Scandicci - Via dei Turri

15:45

Title

15:45

Parking Tickets

Drivers pay parking time to PayPal parking manager account via the signage totem deployed in the car-parking area in Scandicci.

Additional Services:

bus traffic flow monitoring

(Via Pietrasantina park-Pisa)

• Intermodal area (car-parking, urban bus stop, touristic parking slot and several facilities for tourists).

• Technologies: traffic sensors. M2M GW. Image detection.

• Scope: Touristic bus traffic flow monitoring for parking occupancy estimation. Parking pass payment via credit card through parking manager’s web site.

In collaboration with

Additional Services: trip planning

Step1 – Launch Trip planning from SIMIS main page.

Step 2– Set starting destination addresses and transport mode.

Step 3– Route details

Additional Services: statistics

Available functionalities:

- User’s statistics (n. of users, statistics about sex, ag, education etc.)

- Ticket’s statistics (tickets purchased in Pisa,& Scandicci, user’s

feedback etc,).

- Car-pooling statistics (shared km, agreed costs, user’s feedback

etc,).

[ [

Interoperability

Italian - Serbian Pilots

Interoperability between

Italian and Serbian pilots

29

General description:

• Italian and Serbian pilots interoperability is based on interaction through WEB remote

calls of specific functions implemented and provided by the payment platforms involved

(SIMIS and mTicketing).

• Modes involved: urban bus/tram transports in Pisa/Scandicci (Florence) and Novi Sad

urban bus ticket (JGSP karta).

• “Card-less” interoperability -> tickets are in electronic format (SMS for Italian pilot,

pkPass/ QR-code based for the Serbian pilot).

Interoperability between

Italian and Serbian pilots

30

Italian and Serbian

pilots interoperability

high level

architecture

All invoked functions (REST web APIs) exchange data in secured mode (https).

Interoperability

data adaptation

31

Data adaptation mainly involved SIMIS user’s registration

phase (from SIMIS towards mTicketing platform).

SIMIS user data mTicketing user data

UserId(*) Username(*)

Password(*) Password(*)

Name(*) First name(*)

Surname(*) Last name(*)

Address Address(*)

Email(*) Email(*)

Phone number Phone(*)

Other details (age, sex, education etc.)

City(*)

Postal Code(*)

(*) mandatory fields

Data have been adapted taking in account the

format of information required by each platform.

Mandatory fields:

SIMIS user data empty fields or not present (i.e. city,

postal code) are filled with a predefined string

(“MOBIWALLET_ITALIAN_USER”)

Password:

SIMIS password must be “at least” 4 char long

(mTicketing requires at least 6 chars). Password is

automatically generated by SIMIS during mTicketing

registration phase.

Main goals:

perform an automatic registration/login to

mTicketing platform without requiring any

additional input from SIMIS user.

Interoperability

new user registration

32

Interoperability

user checks tickets availability

33

Interoperability

user buys ticket

34

Interoperability

35

SIMIS GUI and mTicketing services

Interoperability

36

New user login attempt on mTicketing

Interoperability

37

User retrieves available bus tickets

Interoperability

38

User performs payment on selected ticket

Interoperability

39

Ticket successfully purchased. Notification to user

Interoperability

40

JGSP ticket (pkPass format)

42

www.mobiwallet-project.eu

Info: [email protected]

www.linkedin.com/company/mobiwallet

twitter.com/MobiWallet_EU

Stay tuned!