Evolvi Rail - Support for 'Split Ticketing' V23

Dolphin now supports interfacing of Evolvi V23 handoff files containing 'Split Tickets'.

**IMPORTANT**  Agencies must upgrade to Dolphin's V20.058 before enabling Evolvi's split ticketing (V23) in their Booking Portal.  Once the BMM is upgraded, new V23 handoff files and older versions will interface successfully.

Evolvi will provide documentation describing their portals split ticketing configuration and interface changes.

BMM changes to support split ticketing:

1. When a handoff file containing split tickets is interfaced, the BMM checks if the passenger/s must change trains or remain on the same train when 'changing split tickets'.  This information is presented in the printing notes of the ticket the passenger is changing to.

   Example 1:  Passenger is travelling London to Leeds.  The journey is split in Peterborough, and consists of two tickets.  London/Peterborough and Peterborough/Leeds.  The change of ticket does not require the passenger to change trains.  ie the ticket change occurs at a calling point. 

   Printing notes for Peterborough/Leeds ticket: Change ticket but remain on train at calling point: Peterborough.

   Example 2:  Passenger is travelling from Inverness to Sheffield.  The journey is split in Durham and Leeds, and consists of three tickets.  Inverness/Durham and Durham/Leeds and Leeds/Sheffield.  The passenger remains on the train in Durham (calling point) when changing to the second ticket, and changes trains in Leeds when changing to the third ticket. 

   Printing notes for Durham/Leeds ticket: Change ticket but remain on train at calling point: Durham

   Printing notes for Leeds/Sheffield ticket: Change ticket and train at: Leeds

2. New Journey Type dropdown has been introduced in the rail segment, indicating if a ticket is one way (OW), return (RT) or a split one way (SOW).  Please note that Evolvi do not support split return tickets. 

3.  Unfortunately, Evolvi only provide 'Distance' per 'Journey' and not per 'Ticket'. Because we do not get individual ticket distances in the case of split journeys, the distance will be equally divided across all split tickets, with any rounding difference added to the first ticket.

Example one:  Passenger is travelling London to Leeds.  The journey is split in Peterborough, and consists of two tickets.  London/Peterborough and Peterborough/Leeds.  Evolvi provide the distance for London/Leeds only at 289km.  Ticket 1 Journey Distance = 145, Ticket 2 Journey Distance = 144

Example two: Passenger is travelling London to Bristol.  The journey is not split and therefore consists of one ticket.  London/Bristol of 125kms.  Evolvi provide the distance for London/Brighton.  Ticket 1 Journey Distance = 125

It is critical to advise any organisations who receive your CO2e or distance reports of these changes.  The "total" distance will always be accurate, but the allocation of distance to individual split tickets will not be.

Reporting:

1. The friendly name "Journey Type" is now available in the following reporting views via the BMM ->Reports:

FoldsAndFIsWithFVend_VW

FoldsAndFIsWithFVendAndFPs_VW

FoldsAndFIsAllAndFPs_VW

FoldsAndFIsAll_VW

    2.       For customers with access to their own database, 'Journey Type' (OW, RT, SOW, 'blank') is being stored in dba.folditems_TB -> strFiJourneyType_FD.    This is the same table and column used for Air Ticket journey type.

Dolphin support will be in touch to arrange a Dolphin upgrade.    Any questions, please contact support@dolphind.com