Dr. Josef Withalm

1

• Dr. Josef Withalm
• Siemens Austria
• Program and System Engineering
• Brussels, 12. May 2003

2
MOJO-WorkshopOverview

• Part 1 PTA
• Part 2 SAPA
• Part 3 SPIRIT-ASA
• Part 4 Travel Angel
• Part 5 Suggested Architecture

3
MoTiV-PTA

• MoTiV Program (Mobility and Transport in
  Intermodal Traffic)http//www.motiv.de/
• PTA (Personal Travel Assistance)
• Participants
• Car Manufacturer BMW, DaimlerChrysler, Opel, VW
• Suppliers Bosch, VDO (earlier Philips)
• Systems Software debis, IBM, Siemens ZT
• Volume DM 120 Mio.
• Sponsored German Ministry of Technology (50)
• Duration May 1996 - April 2000

4
PTA Goals (I)

• Remove the overload from certain travel means
  (road, trains, ... )
• Distribute travelers over time, space, and
  carriers
• Definition of a common infrastructure for travel
  planning and guidance
• Individual support of travelers
• Door 2 door travel planning (route planning,
  reservation, booking )
• Travel guidance (user tracking, route monitoring)
• Integration of
• Public and individual transport (railways,
  airlines, PUT, cabs, rental cars, ...)
• Travel services (parking, hotels, entertainment,
  ... Travel services

5
PTA Goals (II)

• Taylored to individual requirements
• Travel typesBusiness trip, private trip, single
  traveler, group of travelers
• User profiles and user preferences(Non) smoker,
  handicaps, drivers license, favorite carrier
  hotel, special rates, ...
• Adaption to changing user preferences
• System access
• In the office, at home (PC / Internet, ISDN)
• In the car (car based navigationsystem / GSM,
  SMS, GPS)
• In the train, anywhere (subnotebook, PDA, PIC /
  GSM, SMS)

6
PTA/Cooperation Between Agents
7
PTA Architecture
8
PTA End User Devices
9
PTA Characteristics

• Distribution of users, services over time and
  space
• Heterogeneous system and autonomous components
• Coordination of various services
• Strongly communication dependent
• Informations and service retrieval
• User specific profiles and preferences
• Mobile user devices

Agent-based implementation of the PTA system
10
MOJO-WorkshopOverview

• Part 1 PTA
• Part 2 SAPA
• Part 3 SPIRIT-ASA
• Part 4 Travel Angel
• Part 5 Suggested Architecture

11
Agent TechnologyProject SAPA / 1

• PMS without allotments offered to CRSVacancy
  Query
• Prototype since 6/2000
• patent submitted

Property Management System (PMS)
Computerised Reservation System (CRS)
12
SAPA/Architektur ?-Version CRS zu PMS
Existing components
-
13
Approach / 3Communication process
Hogatex server
Existing components
Agent factory
New developed
Hotelagent
Hogatex client
New components
ODBC
ACL
JDBC
URL
CORBA Interface
Hogatex client
ES client
Filter
ES server
SQL
Hogatex client
Progress
INFORMIX
14
Agent TechnologyProject SAPA / 2

• PMS without allotments offered to CRS
• PMS with automated allotments

15
Agent TechnologyProject SAPA / 3

• PMS without allotments offered to CRS
• PMS with automated allotments
• direct access to the PMS by the customer

Agent Technology including CRS functionality
16
MOJO-WorkshopOverview

• Part 1 PTA
• Part 2 SAPA
• Part 3 SPIRIT-ASA
• Part 4 Travel Angel
• Part 5 Suggested Architecture

17
Agent TechnologyProject ASA / 1
Components
EU-Spirit API (ESP - API)
Travel Planners (TP)
EU-Spirit-TPR provider receives no compensation
18
Agent TechnologyProject ASA / 2
Components
ASA - API
ASA-API
ASA provider
ASA provider
Ring
Data
Service provider
SPIRIT Travel Planning Ring (TPR)
19
Prerequisites/ 1Relationships Between Different
Providers
Service
Service
Provider A
Provider B
Proposal
Proposal
Customers
20
Prerequisites/2

• Several autonomous providers offer particular
  services
• Such services are offered via particular web
  portals
• Services can have simple or highly complex
  internal structures
• hotel or train schedule
• Each service offered by a provider has a unique
  interface

21
Prerequisites/4System Organization

• There is a transparent connection between all the
  providers
• This allows a free exchange of information

22
Prerequisites/5 Architecture
Service
WWW
Customer
Internet
Provider A
Clearing
IDL_P
IDL_C
CORBA
Provider B
IDL_P
WWW
Internet
Customer
Service
23
Registration CenterRequirements/1

• Every provider can offer every service to any
  other provider
• The system must be freely expandable
• if a new provider is added to the system, the
  services offered by that provider will be
  automatically made available to others
• The system provides for mutual clearing
• Old providers are free to offer new services to
  new providers

24
Registration CenterRequirements/2

• Every provider is registered
• The database of the Registration Center contains
  the addresses of the providers and their services
• When a provider needs a special service for its
  customers, a search in the Registration Center
  will reveal whether or not such a service is
  available

25
Registration CenterRequirements/3
Clearing Centre
Provider
register provider
register services
Clearing Center
Provider A
Provider B
Provider C
Provider D
26
Registration CenterStructure

• Simple database containing the following elements
• Destination (station)
• IIOR Internet Interoperable Object Reference
• IDL type (e.g. hotel reservation)
• Description

27
Scenario/1
Provider B Rimini
Provider A OBB
Customer
Registration Center
connect to WWW server
enter data for service A source
Vienna destination Rimini
1
processing
show result
2
get list of services for destination Rimini
show proposal mask
3
enter data for service B hotel type price
1000
4
send request
processing
receive result
show result
5
28
MOJO-WorkshopOverview

• Part 1 PTA
• Part 2 SAPA
• Part 3 SPIRIT-ASA
• Part 4 Travel Angel
• Part 5 Suggested Architecture

29
Travel Angel Personal Travel Assistant
Process Optimisation
Payment / Fulfilment
Notification
Tracking
Localisation
Communication
30
Never be lost again - Mobile Travel Management
Services
Time
31
Siemens Mobile Travel Solutions-Next Generation
Travel Applications
32
Travel Angel logic layers model
33
OnTrip Solution Products Travel Angel V.1
Re-Booking
Flight Schedule Access

• Itinerary view - Trip Stage Aware Flight select
• Flight sooner/later, same Airline
• Booking Acknowledgement by SMS

• Trip Stage aware Flight schedule select

Airport Services
Destination Information

• Trip Stage Aware Flight delay info
• WAP access for Boarding-Time

• Trip Stage aware Weather information select

Personal / Corporate Travel Information

• Trip Reminder - Itinerary Push
• Agency Information (Sites, Services)
• Contacts, Addresses of Locations, How to
  reach...
• Travel Support Services, Emergency, Medical Care
• Trip Stage and Location aware Information
  Presentation

Travel Angel - Personal Trip Organisation Platform

• Personalisation
• Read-In of Personal Name Record (PNR)
• User Profile Management
• Configuration of Information Push by Traveller

• Backend
• GDS, CRS Interface
• Airport Information System
• Weather Info

• Mobile Device Support
• WAP Display Management
• Session Management

• Operator Services
• Logging - Data Warehouse Export
• Operation Maintenance

34
MOJO-WorkshopOverview

• Part 1 PTA
• Part 2 SAPA
• Part 3 SPIRIT-ASA
• Part 4 Travel Angel
• Part 5 Suggested Architecture

35
ITS-net Service Provider
36
Trip-Analysis

• Pre-Trip
• Information
• Booking
• Billing
• Time Scheduling
• On-Trip
• Online-Info
• Local Based Services
• change Booking
• Post-Trip
• Billing-Info
• Storage Passenger Datas
• Statisics

37
Agent Market Place