Conversion Details 108.1 to IRS 90918-10

Parameters required for the import of 108.1 data

Parameter Description
Country Country used to assign the station codes provided without country in 108.1
Character Set Character set to read the local characters in 108.1 station names
Time zone Time zone used to transfer the date fields in 108.1 into complete date information

Parameters required for the conversion of 108.1 data

Conversion Parameters

Parameter Description
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.
Station Mapping Mapping of nonstandard stations into real MERITS station codes.
Fare station set mappings Mapping of 108.1 station codes to fare reference stations. This will be created automatically in case the fare reference codes are properly contained in the 108.1 data.
Station to service constrained mapping Mapping of 108.1 station codes to service constraints.
Fare template

Template to create a fare in the 90918-10 data. The template must provide service class and price factor to create a fare. All required data for the final fare must be created except the regional validity and the price which come from 108.1 series and fares.

A fixed price can be set, the all fares converted from series will have the same price.
The referenced data items must be defined in the OSDM fare structure first. They can then be assigned to a fare template.

Fare Template

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.
  • Up: rounding up to one cent
  • Down: rounding down to one cent
  • Half-Up: rounding up to one cent for 0.5 to 0.9 cents and down for 0.1 to 0.4 cents
  • Half-Down: rounding up to one cent for 0.6 to 0.9 cents and down for 0.1 to 0.5 cents
  • Half-Even: rounding half up if the left digit is odd, half down otherwise (preserves the mean value)
  • Up to 5 Cent: rounding to multiples of 5 cent: up to 5 cent for 0.01 to 5.0 cents and up to 10 for 5.01 to 9.99 cents
  • Down to 5 Cent: rounding to multiples of 5 cent: down to 0 cents for 0.01 to 4.99 cents, down to 5 cents for 5.01 to 9.9 cents
  • Up to 2 Cent: rounding up to multiples of 2 cent
  • Down to 2 Cent: rounding down to multiples of 2 cent
  • Up to 10 Cents: rounding up to one cent
  • Down to 10 Cents: rounding down to 10 cents
  • Half-Up to 10 Cents: rounding up to 10 cents for 0.5 to 0.9 cents and down for 0.1 to 0.4 cents
  • Half-Down to 10 Cents: rounding up to 10 cent for 0.6 to 0.9 cents and down for 0.1 to 0.5 cents
  • Half-Even to 10 Cents: rounding half up to 10 cents: if the left digit is odd, half down otherwise (preserves the mean value)
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 DescriptionA descriptive text of the bundle which is used in the selection list to assign the bundle to a fare template
Combination constraintThe rules on how to combine fares with other fares.
Sales availabilityThe sales availability will be calculated from the validity in the 108.1 data.
Travel validityThe 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 limitsThe upper and lower limit of passengers to be combined on a ticket.
Fulfillment ConstraintA 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 constraintThe 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.

Data structures for after sales rules and legacy accounting identifiers can be added to the fare template via the context menu (add child...).

The legacy accounting identifiers are not needed for conversion but can be used to set an tariff id per fare template to be used in the accounting. If the accounting identifier is missing the ids will be allocated automatically.

The after sales templates should be added to define after sales rules. The rules can provide a factor to calculate the fee depending on the rule. The fee is calculated from the price of the fare multiplied by the fee factor and rounded to Euro-Cent.

Conversion

convert
Convert the data.

Conversion has the following steps:

  1. deleting old conversion results
  2. creating fare station sets from the fare reference code in the 108.1 station data
  3. creating connection points and border point mappings
  4. updating the station reference data with case sensitive station names and border point codes
  5. creating sales validity constraints - all from/end dates in series and fares are connected, the set of intersections is created. Each intersection results in a sales availability constraint.
  6. creating carrier constraints for all carriers contained in the series
  7. conversion of series into fares

Converting a Series

A series is converted into a regional validity and a corresponding regional validity for the return. For each regional validity and sales availability and fare template a fare is created using the 108.1 fare data.

Converting of a series has the following steps:

  1. converting the series into a regional validity and a second regional validity for the reversed direction.
    1. identifying the connection points in case of transit series or series from a border point
    2. replacing stations by real stations, service constraints or fare descriptions using the mappings provided in the conversion parameter
    3. adding the service constraints and fare descriptions to the fare data
    4. converting the departure station, the via station list and the arrival station into a regional validity.
  2. creating the fare based on the fare template.
  3. calculating the price for each fare template and sales availability constraint.
  4. adding legacy accounting information to the fare
  5. adding the price to the fare data set if it is not yet there
  6. adding the fare to the fare data set