Legacy data show either the imported data from 108 files or the converted 108 data from a OSDM to Legacy conversion:
On import:The data of 108.1 are not sufficient to provide a complete set of 90918-10 fare data. The missing data need to be added in the parameter section of the data set.
The missing data are added in the conversion parameter section as fare templates which serve as a copy template to create 90918-10 fares from the imported data. Missing data can be added to the template using the editing features. The template provides a factor to derive the fare price from the standard adult price provided in the 108.1 data.
Form the fare of one series in 108.1 two fares per template are created for the two travel directions. For different travel classes separate templates need to be defined and the service class needs to be set in the fare template.
Series listed in TCVL can be attributed a separated combination constraint in the fare template.
The station codes in 108.1 have been misused to other concepts like non-MERITS-stations, border points, fare reference stations and service brands. These codes need to be mapped to the appropriate entities. For this mappings can be defined in the conversion parameter area to map these codes o the proper entities.
Border points cannot be converted directly, so the needed border points will be converted into connection points and border point mappings but the station sets of the connection points might be incomplete and must be completed manually and the conversion needs to be started again.
| Data item | Description |
| Carrier | carrier of the data delivery (company code) |
|---|---|
| Start date | start of availability for sale for the data delivery |
| End date | end of availability for sale for the data delivery |
| Time zone | time zone to convert date and time values |
| Data item | Description | Values |
| Convert fare descriptions | Fare description will be converted into TCVP fare entries. For each different fare description a different fare table will be created. | check-box|
|---|---|---|
| Convert service constraint | Service constraints will be converted into TCVP fare entries. For each different fare description a different fare table will be created. | check-box |
| Country | Country to be used for station code conversion from 108.1 to 90918-10. | Select country |
| Station import filter | a list of counties that limits the station import to those countries | Selection of multiple countries |
| VAT Templates | Templates to create VAT tax information. Templates can be provided for different scope and countries. The template applies to regional constraints within the specified country. Templates with scope INTERNATIONAL are used additionally for regional constraints with connection points. | Add VAT details for different countries |
| Legacy border point mappings | Manual mapping of border points to connection points. In case the border point data are complete in the imported border point table this entry is not required. Otherwise it can be added manually. To add an entry manually the connection point must be added in the fare data first. | |
| Legacy station mappings | Mappings of station codes in 108.1 to merits codes. A manual mapping can be added for station codes not included in MERITS | Mapping station code 018.1 to MERITS station code. |
| Fare Templates | Template for a fare to be created based on 108.1 data. The fare | |
| Legacy fare station set mappings | Mapping of 108.1 station codes to fare station sets | Mapping of 108.1 stations to fare station sets. This mapping is generated from the 108.1 data. Additional mappings can be added manually. Fare station sets must be added in the fare data before the mapping. |
| Legacy to station to service constraint mappings | Mappings of 108.1 stations to service constraints. In 108.1 data virtual stations have been added to indicate a service constraint. | Mapping to a service constraint. The service constraint must be added in the fare data first. |
Data structures used in the fare template reference data in the final fare structure.
| Content | Description |
| Base Price Calculation Class | the class in the 108 data from which the base price for the calculation is taken. If it is empty the service class is used for this decision. E.g. this allows to base a price for a first class dog fare on a second class base price. |
|---|---|
| Conversion Restriction by Carrier | The template is only applied to series where the carriers listed in this filter. If e list is empty the template applies to all series. |
| Price factor | a factor to calculate the price depending on the price given in the 108.1 data. The factor is applied and the result is rounded to Euro-Cents |
| Price | A fixed price that can be defined manually in the fare structure. If this price is set the price factor will not be applied and the series price is replaced by this price. |
| Rounding mode | Rounding rule applied to the price.
|
| Data description | Text to name the fare template. This text as no effect on the final data. |
| Fare detail description | A detailed description can be added to the fare. The fare detail description is a text that must to be edited in the fare structure first. Then it can be selected in the fare template. |
| Fare constraint bundle | Fare constraint bundle holding the main constraints of this type of fare. |
| Separate contract fare constraint bundle | Fare constraint bundle to be used in case the series is listed in the 108.1 TCVL file. |
| Legacy Accounting Tariff Id | Tariff Id to be used in the 301 accounting data structures. Valued defined in IRS 30301. |
| Legacy Conversion | Indicates whether the fare template creates fares that allow a reconversion into 108.1 data. A fare might allow reconversion or even be only included for reconversion. |
| Passenger Constraint | The passenger constraint to be applied with the fare. The passenger constraint must be edited in the fare structure first and can then be selected in the fare template. |
| Reduction Constraint | The reduction constraint to be applied with the fare. The reduction constraint must be edited in the fare structure first and can then be selected in the fare template. |
| Reservation parameter | The reservation parameter to be applied with the fare. The reservation parameter must be edited in the fare structure first and can then be selected in the fare template. |
| Sales availability | The sales availability will be calculated from the validity in the 108.1 data. |
| Service class | The service class to be applied with the fare. The service class must be edited in the fare structure first and can then be selected in the fare template. |
| Service constraint | The service constraint to be applied with the fare. The service constraint must be edited in the fare structure first and can then be selected in the fare template. |
| Service Level | The service level to be applied with the fare. The service level must be edited in the fare structure first and can then be selected in the fare template. |
| Text | The text naming the fare. The text must be edited in the fare structure first and can then be selected in the fare template. |
| Travel validity | The travel validity to be applied with the fare. The travel validity must be edited in the fare structure first and can then be selected in the fare template. |
The Fare Constraint Bundle holds the main constraints for a type of fare. It needs to be created within the fare structure data and holds the following constraints:
| Content | Description |
| data Description | A descriptive text of the bundle which is used in the selection list to assign the bundle to a fare template |
|---|---|
| Combination constraint | The rules on how to combine fares with other fares. |
| Sales availability | The sales availability will be calculated from the validity in the 108.1 data. |
| Travel validity | The travel validity to be applied with the fare. The travel validity must be edited in the fare structure first and can then be selected in the fare template. |
| Passenger limits | The upper and lower limit of passengers to be combined on a ticket. |
| Fulfillment Constraint | A fulfillment constraint to be added to the fare. The fulfillment constraint must be edited in the fare structure first and can then be selected in the fare template. |
| Personal data constraint | The personal data constraint to be applied with the fare. The personal data constraint must be edited in the fare structure first and can then be selected in the fare template. |
Tariff data from 108.1 are included when needed for conversion.
| Data | Description |
| Series | Series data records |
|---|---|
| Stations | Station data |
| Distance fares | Prices based on distance |
| Route fares | Prices based on routes |
The fare data in the fare data section correspond exactly to the data specified within the IRS 90918-10 for the bulk data delivery, Data Ids to link the different data parts within the JSON export will be created automatically before the export of the data.
The data structure contains the complete set of defined data and is not restricted to data used in the conversion. Additional data might be added manually. Data that are also generated include a data source tag indicating whether it was created by conversion or by import or manually. All data marked as created by conversion will be replaced with the next conversion.