A TransXChange operating profile can be defined on (in order of specificity, most → least):

  1. A vehicle journey
  2. A journey pattern
  3. A service

Passenger will use most specific operating profile it can for each journey, it will not merge operating profiles across the above elements.

If a vehicle journey does not have an operating profile, then the operating profile from the journey pattern will be used if present, and finally the service.

If no operating profile is present, a journey is assumed to be running Monday through Friday.

There are 5 elements to an operating profile (in order of precedence): 




Which days of the week does this service run? e.g. Monday to Friday



The weeks of the month on which the service is operated for the given day types; for example, “first and third weeks of the month”.

Passenger does not currently support PeriodicDayType.


Inclusions or exclusions of pre-defined date ranges for an organisation, such as a school’s term times.

In the below example, the type references the serviced organisation’s working days within a DaysOfOperation element; so the service is operating during the working days of the organisation.

If this type instead used DaysOfNonOperation, the service would not run on the working days of the organisation, unless overridden by BankHolidaysOperation or SpecialDaysOperation.



Inclusions or exclusions of specific bank holidays by name. e.g. ChristmasDay, ChristmasDayHoliday (a displacement holiday), SpringBank etc.

    <BoxingDay />
    <ChristmasEve />
    <NewYearsEve />
    <ChristmasDay />
    <NewYearsDay />
      <Description>Platinum Jubilee Extra Bank Holiday</Description>


Absolute date ranges, either as DaysOfOperation (inclusive) or DaysOfNonOperation (exclusive).



They take precedent in this order, starting with RegularDayType being the most generalised, and SpecialDaysOperation being the most specific and therefore the most authoritative. 

Continue to the next article on Managing Journey Data: Serviced Organisations.