FareXChange Profile - Examples

Zone-to-zone Trip - Metrobus Line 1

This examples comprises a simple zone-to-zone tariff for a single line that can be visualised as a simple "fare triangle" of origin/destination pairs, as in the fare sheet shown below. The example is coded in a modular fashion so that common components can be shared with other tariffss and products.

Contents :

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

FARESHEET:

    Line 1
Image (c) Copyright Metrobus 2018

Go to Top

FEATURES:

  • Network defined as a number of zones, each with some stops
  • Available for different types of user:
    • Adult, Child, , .
    • 50% discount rule for children.
  • paper ticket only.
  • On-board purchase only.

Go to Top

ROUTE:

Route Map

The Metrobus Line 1 route runs between Bewbush and Broadfield.

  • The stops on the route have NaPTAN identifiers
  • The stops on the route reference NPTG localities.

Route

Image (c) Copyright Metrobus 2018


Route - Network components

A Line and Fare Zones are specified.

  • The route is broken up into zones.
  • Prices are given as zone-to-zone fares.
Network components

Go to Top

XML example:

xmlXML document for Metrobus Crawley LINE 1 example

Go to Top




Network NETWORK - Metrobus Line 1, stops, zones

Declared in separate "Metrobus Network" SERVICE FRAME and FARE FRAMEs:

  • The LINE is declared.
  • SCHEDULED STOP POINTs are declared for each stop using their NaPTAN stop identifiers and names.
  • FARE ZONEs are defined for each zone along the route. Each zone references NaPTAN stop identifiers of the stops in it. .

Go to Top

Tariff TARIFF - Metrobus Line 1: zone-to-zone

Declared in a "Metrobus Trip Product" FARE FRAME.

  • The TARIFF is for the specified LINE.
  • DISTANCE MATRIX ELEMENTs are specified for each zone-to-zone combination, corresponding to the cells in the fare triangle.
  • The TARIFF for Line 1 has FARE STRUCTURE ELEMENTs for each of the tariff features:
    1. Eligibility: Permitted USER PROFILEs Adult & Child.
    2. Lines: Permitted LINE is Line 1.
    3. Access: Zone-to-zone combinations as  DISTANCE MATRIX ELEMENTs for each origin/destination pair.

Go to Top

TripPRODUCTS - Metrobus Single trip

Declared in a "Metrobus Trip Product" FARE FRAME alongside the TARIFF. Note that if the same product is offered for other lines then it could be placed in a sepaate frame and reused with different tariffs.

  • A PREASSIGNED FARE PRODUCT is defined for the single trip.
  • It has a VALIDABLE ELEMENT that references the FARE STRUCTURE ELEMENTs above as valid choices.

Go to Top

SP SALES OFFERS - Metrobus single trip, paper ticket

Declared in a "Metrobus Trip Product" FARE FRAME.

  • A SALES OFFER PACKAGE is defined for the cash single trip.
  • It has a SALES OFFER PACKAGE ELEMENT that references the Single Trip FARE PRODUCT .
    • The TYPE OF TRAVEL DOCUMENT is 'paper ticket'.
  • A BRAND is assigned - Metrobus.
  • DISTRIBUTION ASSIGNMENTs specify on-board and at stop DELIVERY CHANNELs, with specific PAYMENT METHODs.

The SALES OFFER PACKAGE is summarised thus:

FARE PRODUCT SALES OFFER PACKAGE
single trip paper ticket

Go to Top

Prices PRICES - Metrobus Single trip prices for an Adult

Declared in a separate "Metrobus Trip Prices" FARE FRAME.

  • A nested FARE TABLE holds the adult fare prices.
    • There is a nested FARE TABLE for each column of origin/destination pairs.
    • Each nested table contains a CELL for each row, i.e. corresponding to a DISTANCE MATRIX PRICE for the specific origin/destination pair.
  • In this example, only two prices are used (1.00 and 1.60) ; these can themselves be regarded as shared  price bands. Rather than repeating the amounts, two additional GEOGRAPHICAL INTERVAL PRICEs are declared (A = $1.00, B = 1.60) and referenced as appropriate in each cell instead of repeating the same  amount in each cell.
  • A DISCOUNTING RULE is declared for deriving the Child price from the the Adult price.

Thus prices depend on :

PREASSIGNED FARE PRODUCT

 x 

DISTANCE MATRIX ELEMENT

 x 

USER PROFILE

Go to Top

operator COMMON OPERATOR COMPONENTS

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 (National Operator Code: METR)
    • BRAND - Metrobus
    • DATA SOURCE originating data

Go to Top


transactions SAMPLE TRANSACTIONS

Declared in a separate separate SALES TRANSACTION FRAME. In practice sales transactions, which are generated by sales of products, are generated by different systems and are exchanged separately. Examples are included here only to help understand the use of NeTEx.

  • 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. On-board purchase of a single adult trip ticket on Metrobus Line 1 from >Bewbush to Pease Pottage.
    2. On-board purchase of a single child trip ticket on Metrobus Line 1 from >Gossops Green to West Green.

Specific examples of parameters representing ticket purchases

Description Reference
Element Value

On-board purchase of a single adult trip ticket on Metrobus Line 1 from >Bewbush to Pease Pottage.

SalesOfferPackage:

mb:Trip@single-SOP@p-ticket:

TypeOfTravelDocument:

fxc:printed_ticket

PreassignedFareProduct:

mb:Trip@single

TypeOfFareProduct:

fxc:standard_product@trip@single

ValidableElement:

mb:Trip@single@travel

Operator:

noc:METR

Line:

mb:Line_1

DistanceMatrixElement:

mb:Bewbush+Pease_Pottage

UserProfile:

mb:adult

StartOfValidity:

2017-07-08T01:07:00

GeographicalIntervalPrice:

mb:price_band_B@adult

Amount:

2.40

PaymentMethod:

cash

DistributionChannel:

mb:on_board

At stop purchase of a single child trip ticket on Metrobus Line 1 from Gossops Green to West Green.

SalesOfferPackage:

mb:Trip@single-SOP@p-ticket:

TypeOfTravelDocument:

fxc:printed_ticket

PreassignedFareProduct:

mb:Trip@single

TypeOfFareProduct:

fxc:standard_product@trip@single

ValidableElement:

mb:Trip@single@travel

Operator:

noc:METR

Line:

mb:Line_1

DistanceMatrixElement:

mb:Gossops_Green+West_Green

UserProfile:

mb:Trip@child_with_adult

StartOfValidity:

2017-07-08T01:07:00

GeographicalIntervalPrice:

mb:price_band_A@child

Amount:

0.80

PaymentMethod:

cash

DistributionChannel:

fxc:self_service_ticket_machine

Go to Top

common COMMON FAREXCHANGE COMPONENTS

Declared within a separate "FareXChange Common Resource" COMPOSITE FRAME. Declares UK Profile TYPEs of FRAME, NaPTAN and other CODESPACES and a number of recommended code values (e.g. for user types) for the UK. These are the same for all UK Profile Fares. We include it here so data values can be validated automatically against the given values, but external references to the values could also be used.

Go to Top

SUMMARY

The offering can be summarised as follows:

Summary  

Go to Top

 

logo

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