FareXChange Profile - Examples

Zonal Passes - Plusbus rail add-on

Zonal Pass fares - Plusbus rail add-on

This example, based on the plusbus website with PlusBus fares, encodes the PlusBus zonal pass add on for rail for Crawley and Thtree Bridges.

Contents :

  1. Fare Sheet.
  2. Features.
  3. Network
  4. XML example.
  5. Summary.

See also PlusBus zonal pass add-on

ZONES:

Zone Network Components in NeTEx - for PlusBus Netex

Each zone is a FARE ZONE

  • NaPTAN stops can be assigned to one or more FARE ZONEs.
  • An NPTG PlusBus zone can be referenced as a NeTEx FARE ZONE with a surrounding polygon of co-ordinates.

Go to Top

FARESHEET:



Image (c) Copyright First Group 2018

Go to Top

FEATURES:

> PlusBus Zonal pass - A day or season zone pass:

  • Available for any PlusBus station zone.
    • PlusBus zone are defined in NPTG.
    • There are exceptions as to which operators and which specific services are available in each zone
  • Requisite entitlement is have a rail ticket
    • Rail single or return ticket.
    • Rail season ticket.
  • Available for different duration periods.
    • 1 day
    • Season Pass duration, e.g.1 week, 1 month, 13 weeks, 1 year1.
  • Available for different types of user in line with ATOC categories:
    • Adult, child, railcardHolder.
  • Online, travel shop and at-station purchase.
    • Distribution channels depend on media type and pass duration.
  • Plusbus add-on may be bought separately or at the same time as therail ticket
  • Prices vary by zone, duration, user type or group.
  • Validity period for use

Go to Top

ZONES:

Zone Map for PlusBus Crawley

For Plusbus, the UK is broken up into separate zones around one or more railway stations.

  • Prices are given per zone.
  • Specific OPERATORs participate within the zone.
  • An OPERATOR may specify exceptions and inclusions.

Go to Top

XML example:

xmlXML document for >Crawley PlusBus Example.

NB the document also includes the Crawley Metrorider products and  other Concessionary scheme passes including Discovery, and Easit.

xmlXML document for JSP and Rail prerequisites

Network NETWORK - PlusBus stops, zones

Declared in separate "Metrorider Network" FARE FRAMEs

  • Available for any PlusBuz Zone.
    • NPTG  FARE ZONEs are defined for each PlusBus zone . Each zone references NaPTAN stop identifiers of the stops in it .

    • Go to Top

    Tariff TARIFF - Plusbus zonal

    Declared in a "PlusBasPass Product" FARE FRAME.

    • There are TIME INTERVALS for each of the available duration periods.
      •   1  day,  & Season ticket durations (1m, 1quarter 1 Year).
    • There are two TARIFFs
      • PlusBus@Day applies to day tickets.
      • PlusBus@Season  applies to PlusBus season tickets
    • Each TARIFF  has FARE STRUCTURE ELEMENTs for each of the tariff features: These reference USAGE PARAMETERs and NETWORK ELEMENTs
      1. Eligibility: Permitted USER PROFILEs;
        • Adult.
        • Child.
        • RailcardHolder (discounts apply)
      2. Modes::
        • bus.
        • tram.
      3. Access:  Permitted FARE ZONEs.
      4. Prequisites.
        • Reuuisited prequisite products as ENTITLEMENT REQUIRED elements referencing National Rail products.

    Go to Top

    TripPRODUCTS - PlusBus Period Pass

    Declared in a "Metrobus Pass Product" FARE FRAME alongside the TARIFF.

    • Separate  SUPPLEMENT  PRODUCTs are defined for the day  pass and Season pass.
    • Each has a VALIDABLE ELEMENT that references the FARE STRUCTURE ELEMENTs above as valid choices.

    Go to Top

    SP SALES OFFERS - PlusBus passes for different media

    Declared in a "PlusBus Pass Product" FARE FRAME alongside the FARE PRODUCT. .

    • There are three types of TYPE OF TRAVEL DOCUMENT is 'paper ticket'.
      • Paper ticket.
      • M App.
      • Smartcard.
    • There are twelve separate SALES OFFER PACKAGES for each combination of FARE ZONE and TYPE OF TRAVEL DOCUMENT (4 x 3 ). as each has slight differences as to what is offered by way of durations,  group tickets, etc.
    • Each SALES OFFER PACKAGE has a set of GENERIC PARAMETER ASSIGNMENTS specifying:
      • Which FARE ZONE applies.
      • Which TIME INTERVALs are available
    • The SALES OFFER PACKAGES for each type of media are very similar: to describe these properties without repetition, three GROUP OF SALES OFFER PACKAGEs are specified to hold the respective common properties,
    • Each GROUP OF SALES OFFER PACKAGEs specifies:
      • A SALES OFFER PACKAGE ELEMENT indicating the PREASSIGNED FARE PRODUCT - a Metrorider zone pass.
        • and a TYPE OF TRAVEL DOCUMENT; one of the three values.
      • A BRAND - Metrobus.
      • DISTRIBUTION ASSIGNMENTs specifying the available DELIVERY CHANNELs, with specific PAYMENT METHODs.
        • on-board, with cash or contactless card.
        • at stop, with cash or card.

    The twelve SALES OFFER PACKAGES are summarised thus:



    		ZONES - SALES OFFER PACKAGEs
    FARE PRODUCT GROUP OF SALE OFFER PACKAGES Crawley Horsham Redhill & Reigate Metrovoyager
    zonal pass printed ticket ?. ?. ?. ?.
    zonal pass mobile app ?. ?. ?. ?.
    zonal pass smartcard ?. ?. ?. ?.

    Go to Top

    Prices PRICES - Plusbus Zone and media prices for different types of user

    Declared in a separate "Plusbus Pass Prices" FARE FRAME.

    • There are two main FARE TABLE, one for PlusBus day and one for PlusBus Season ticket prices.
    • Each FARE TABLE contains separate nested sub-tables for each TYPE OF TRAVEL DOCUMENT.
      • Paper ticket.
      • Mobile App.
      • Smartcard.
    • For each nested FARE TABLE for each TYPE OF TRAVEL DOCUMENT, there is a sub-table for each category of USER PROFILE or  that is allowed.
      • Adult.
      • Child.
      • Senior.
      • Student.
        • family.
      • duo.
    • For each nested sub-table has a column of permitted TIME INTERVAL for the combination.
    • Each nested table contains a CELL for each TIME INTERVAL pair with a TIME INTERVAL PRICE in it for the specific combination of parameters thus.

      PREASSIGNED FARE PRODUCT

       x 

      TYPE OF TRAVEL DOCUMENT

       x 

      USER PROFILE or GROUP TICKET

       x 

      TIME INTERVAL.

    Go to Top

    operator COMMON OPERATOR COMPONENTS for Metrobus

    Declared in a separate separate "Metrobus Common Operator " FARE FRAME and RESOURCE FRAMEs.

    • A RESOURCE FRAME containing the common operator definitions for Metrobus including:
      • OPERATOR Metrobus, with contact details . Identified by NOC code
      • BRAND - Metrobus
      • DATA SOURCE originating data
      • RESPONSIBILITY SET indicating ORGANISATIONs responsible for managing data.

    Go to Top

    transactions SAMPLE TRANSACTIONS for single trip ticket purchases

    Declared in a separate separate SALES TRANSACTION FRAME.

    • A SALES TRANSACTION FRAME containing examples of the data elements referenced to make various types of purchase:
      • FARE CONTRACT indicating the user.
      • SALES TRANSACTION for each purchase.
      • TRAVEL SPECIFICATION indicating the scope of each purchase.
    • Sample transactions:
      1. At station purchase of a 1 day adult Metrorider pass for the Crawley zone; paper ticket.

    Specific examples of parameters representing ticket purchases

    Description Reference
    Element Value

    1.

    At station purchase of a 1 day adult Plusbus pass for the Crawley zone; paper ticket.

    SalesOfferPackage:

    jsp:Pass@PlusBus-SOP@p-ticket@CrawleyThreeBridges

    TypeOfTravelDocument:

    jsp:cash-ticket

    SupplementProduct:

    jsp:Pass@PlusBus@1day

    ValidableElement:

    jsp:Pass@PlusBus@travel

    TypeOfFareProduct:

    fxc:standard_product@pass@day

    Operator:

    		 jsp:JSP

    UserProfile:

    jsp:adult

    FareZone:

    jsp:PlusBus@CrawleyThreeBridges

    TimeInterval:

    jsp:Tariff@PlusBus@Day@1day

    StartOfValidity:

    2020-07-08T01:07:00

    TimeIntervalPrice:

    jsp:Pass@1day@CrawleyThreeBridges

    Amount:

    3.70

    PaymentMethod:

    cash

    DistributionChannelmb:

    mb:on_board

    Go to Top

    commonCOMMON FAREXCHANGE COMPONENTS

    Declared in a separate "FareXChange Common Resource" COMPOSITE FRAME.  In practice sales transaction, which are generated by sales of products, are exchanged separately. Examples are included here only to help understand the use of NeTEx. 

    Go to Top

    SUMMARY

    The offering can be summarised as follows:

    Product elements in NeTExfor PlusBus



    Modularisation for a large scale product

    The PlusBus product is not of itself complex - it is a simple zonal pass for a specified period. It is complex for several reasons.

    • Many stakeholders are involved -The core product is defined by a consortium,who agree the prices.
    • It has prerequisite products that give the ENTITLEMENT to buy PlusBus.
      • A National Rail Trip ticket, single or return.
      • A National Rail Season Ticket.
    • Multiple operators may participate, each in different zones.
    • Each operator can specify exceptions as to the LINEs and/ or times of operation (peak, off-peak, etc) included
    • There are a large number of PlusBus zones in the country.

    Thus, to specify the product a modular encoding is desirable, placing common definitions in shared files and segregating differences for each zone into an area specific file which can be updated independently of the others. Similarly the definitions of the Rail products can be separated from those of plus bus itself.This can be achieved using the normalmechanisms.

    Go to Top

     
    logo

    © Crown Copyright  2018-20
    Page last updated: 2020/09/16