26.12.2014 Views

Zbornik radova Koridor 10 - Kirilo Savić

Zbornik radova Koridor 10 - Kirilo Savić

Zbornik radova Koridor 10 - Kirilo Savić

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

3rd International Scientific and Professional Conference<br />

CORRIDOR <strong>10</strong> - a sustainable way of integrations<br />

Figure 5: Interoperable Fare Management System [23]<br />

Figure 5 shows components and relations of an interoperable fare management system. The EN<br />

standard describes the components of the application necessary to support an interoperable<br />

environment:<br />

- accessing the Interoperable Public Transport Application,<br />

- data structure and presentation,<br />

- sizing and enumeration of data,<br />

- data access methodology,<br />

- security and access considerations and<br />

- dealing with legacy systems.<br />

The standard specifies sets of data in a structured form as well as the rules for dealing with those data<br />

to enable products such as tickets to be written and used on Machine Readable Card in a manner to<br />

minimize the amount of data to be held on a card.<br />

Associated with the data is the set of processes which applies to the data within the application. The<br />

inclusion of process provides for similar data to be treated in a similar way by all external services and<br />

terminals leading to true interoperability.<br />

Standard EN 15320 builds data model from data elements primarily originated in EN 1545. Data<br />

elements are grouped together in data structures of different types: mandatory (always presented),<br />

additional (data written at creation of product) and logging (changing data and log data). Data<br />

structures are combined to create 5 different types of data group: application environment, products,<br />

holder, event log and wrapper (intended specifically for migration of legacy systems). Using these 5<br />

data groups with 4 fundamental products (Stored travel rights, Charge to account, Customer<br />

entitlement, Ticket) all functionality of ticketing in public transport can be covered.<br />

The proposed common data model is very extensive and use of optional data elements and data<br />

structures in the processes define typical implementation of a ticketing system. While the EN 15320<br />

represents just a frame the final data model for the implementation can only be prepared after the<br />

common products and pertaining rules and processes have been defined by the public transport<br />

network manager.<br />

Using EN 15320 we must be aware that despite standardization of data elements, data structures and<br />

data groups the standard still allows partially different implementations due to optional data groups<br />

and data elements ensuing from its wide conception.<br />

At the moment there is no commercial implementation based on the EN 15320 standard but there is a<br />

long term commitment for the existing ticketing systems in Europe to migrate to EN 15320. For all<br />

these reasons we propose that Slovenia should apply the EN 15320 standard as a basis for<br />

interoperable ticketing system in public transport.<br />

Belgrade, 2012 181

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!