User:Hassocks5489/Tickets

CS
https://historicengland.org.uk/listing/the-list/asset-type-terms/

BAPTIST CHAPEL BIBLE CHRISTIAN CHAPEL BRETHREN MEETING HOUSE CALVINISTIC METHODIST CHAPEL CATHOLIC APOSTOLIC CHURCH CHAPEL CHRISTADELPHIAN CHAPEL CHRISTIAN SCIENCE CHURCH CHURCH ARMY HOUSE CHURCH OF PECULIAR PEOPLE CONGREGATIONAL CHAPEL COUNTESS OF HUNTINGDONS CHAPEL DEPENDENT CHAPEL EASTERN ORTHODOX CATHEDRAL EASTERN ORTHODOX CHURCH EXCLUSIIVE BRETHREN MEETING HOUSE FRIENDS MEETING HOUSE GENERAL BAPTIST CHAPEL GREEK ORTHODOX CHURCH HUGUENOT CHURCH INDEPENDENT METHODIST CHAPEL INGHAMITE CHAPEL JEHOVAHS WITNESSES MEETING HOUSE LUTHERAN CHURCH METHODIST CHAPEL METHODIST NEW CONNEXION CHAPEL METHODIST REFORM CHAPEL MISSION CHURCH MISSION HALL MORAVIAN CHAPEL MORMON TEMPLE NEW CONNEXION OF GENERAL BAPTISTS CHAPEL NONCONFORMIST CHAPEL NONCONFORMIST CHURCH NONCONFORMIST MEETING HOUSE OPEN BRETHREN MEETING HOUSE ORTHODOX CHURCH PARTICULAR BAPTIST CHAPEL PENTECOSTALIST CHURCH PRESBYTERIAN CHAPEL PRESBYTERIAN CHURCH OF WALES CHAPEL PRIMITIVE METHODIST CHAPEL PROTESTANT METHODIST CHAPEL ROMAN CATHOLIC CHAPEL ROMAN CATHOLIC CHURCH ROMANIAN ORTHODOX CHURCH RUSSIAN ORTHODOX CHURCH SALVATION ARMY HALL SANDEMANIAN CHAPEL SCOTTISH PRESBYTERIAN CHAPEL SEAMENS CHURCH SEAMENS MISSION SERBIAN ORTHODOX CHURCH SEVENTH DAY ADVENTISTS CHAPEL SPIRITUALIST CHURCH STRICT BAPTIST CHAPEL SWEDENBORGIAN CHAPEL UNITARIAN CHAPEL UNITED METHODIST CHAPEL UNITED METHODIST FREE CHAPEL UNITED REFORMED CHURCH WESLEYAN ASSOCIATION CHAPEL WESLEYAN METHODIST CHAPEL WESLEYAN REFORM UNION CHAPEL

VC
<!--

It is now five years since validity codes, also known as restriction codes, started to be shown on certain types of National Rail travel tickets (Off-Peak day and period Singles and Returns, many Advance tickets and some promotional tickets). The alphanumeric codes, each of which defines a particular time restriction for the outward and/or return journey, first appeared in October 2011, initially on Shere FASTticket machines on the Southern network, and gradually spread to other systems thereafter. Codes have been around a lot longer than this, but previously they only appeared in internal systems and documents such as Fares Manuals and within ticket issuing systems. Over the years the number of codes has grown as rail fares have become more complex. "Anytime" (unrestricted tickets valid at all times) do not have validity codes - but see the note below.

The following is a system-by-system summary of when validity codes started to appear, based on analysis of a large number of tickets since 2011: - Shere FASTticket: October 2011 - Shere SMART Terminal: March 2012 - Assertis: July 2012 - TRUMPS (trainline.com): November 2012 - Cubic FasTIS: April 2013 - Scheidt & Bachmann Ticket XPress: May 2013 (see below) - Fujitsu STAR: August 2013 - TRIBUTE: September 2013 - Parkeon: March 2014 (see below) - Avantix Mobile: May 2014

As can be seen, all current ticket issuing systems issue tickets with validity codes - although the vast majority of Avantix Mobile machines still omit them. There is another important exception: where tickets are booked on certain trainline.com-linked websites and are collected through the ToD (Ticket on Departure) process at a self-service or booking office machine, a code will not be shown on the ticket even if it normally would be shown on a non-ToD ticket. No validity codes are shown on ToD tickets issued from the following NLCs: 1750, 3968, 4879, 6376, 6427, 6908, 7175 and 7991. Other trainline-based NLCs such as 1749 do show codes on ToD tickets, though. The reason for this anomaly is unknown at present, although some of the listed NLCs are known to be associated with mobile apps rather than conventional websites. [IDENTIFY NLCS FROM THE LIST] New layout S&B ticket number 67302 from Ashford International to London, illustrated here, lacks the code F4 which it would have if it not been booked online from xxxxx (NLC 6908 - this NLC is shown next to the ToD reference at the bottom of the ticket). Ticket numbers 69325 and 69327, issued just one minute apart at Hereford's S&B machine 2353 and for the same Cardiff-Hereford journey, clearly illustrate the contrast. The first ticket has no validity code and lacks the two accompanying lines of text ("This ticket can only be used at certain times...")

Codes are alphanumeric in one of three formats: number + letter, letter + number and letter + letter. It appears that all codes with a number relate to standard, generic "walk-up" (non-Advance) fares of one kind or another, while all Advance fares have two-letter codes - as do non-standard and TOC-specific walk-up fares, and tickets for which very specific time restrictions are needed. For example, code PB is used on Super Off-Peak Day Return tickets on Southern and Southeastern which were introduced in the late 1990s under the "Pricebuster" name; and code EF is used for the Network West Midlands Super Off-Peak "Evening Fare". Likewise, particular types of Advance ticket each have a code assigned. For example, a standard Virgin Trains West Coast advance ticket valid on that TOC and by connecting trains will have code VA, while the special Corporate Advance fare which can be booked 48 hours in advance will show VC. Ordinary Advance tickets on Virgin Trains East Coast show GA or GC, whereas a VTEC Advance ticket for a journey which also includes peak-time restrictions on a connecting Southeastern High Speed journey (e.g. Ramsgate to York) would have the code GD. As an illustration, here are all the different validity codes possible for a London Terminals-Colchester ticket:

B1	Off-Peak Day Return, First Class Off-Peak Day Return, Child Flat Fare Return D4	Super Off-Peak Day Return, Super Off-Peak Day Single 9A	Off-Peak Return FA	Greater Anglia Duo OA	Advance (all types: there are 12 different Advance fares for this journey)

B1 is a very generic code used for Off-Peak Day Return in many parts of the country. It prohibits travel between 0430 and 0930 on Mondays to Fridays on the outward and return legs. Some codes have much more detailed conditions attached to them: for example, the restrictions associated with code 9I (used for Off-Peak tickets on the West Coast Main Line) run to about 5,000 words.

Shere FASTtickets in particular give an indication of the staged rollout of validity codes. The first ticket ever seen with a code was issued at Brighton (machine 4671) on 14 October 2011. For the first three months, only tickets from Brighton, London Road (Brighton), Moulsecoomb, Falmer, Lewes and Newhaven Town showed validity codes; thereafter they "spread" across the Southern network's Shere FASTticket machines, but still to no others until London Kings Cross got in on the act in November 2012. Machines at other East Coast stations and London Overground stations followed, and by spring 2013 validity codes were shown on Shere FASTtickets across the country.

Likewise, Shere SMART Terminals became "validity coded" at different times. A Birmingham New Street ticket dated 3 March 2012 is the earliest seen so far; it was not until April 2013 that Thameslink and Southern stations' machines were downloaded with the codes.

Other systems do not show such date variation between TOCs. First examples are as follows: Fujitsu STAR: August 2013 Scheidt & Bachmann Ticket XPress: May 2013 (see below) Cubic FasTIS: April 2013 TRIBUTE: September 2013 TRUMPS (trainline.com): November 2012 Parkeon: March 2014 (see below) Assertis: July 2012 Avantix Mobile: May 2014

Ticket issuing systems introduced since 2014, such as ORTIS and Cubic NextAgent VTO, have shown validity codes from the beginning.

40: Anytime Single 41: Anytime Return 62: Super Off-Peak Single and Off-Peak Single 64: Advance 72: Super Off-Peak Return and Off-Peak Return 78: SWT Promo Day Return (Parkeon only) 80: Standard+Parking Return (Parkeon only) 81: Anytime Day Return 85: Super Off-Peak Day Return and Off-Peak Day Return 87: Anytime Day Single, Super Off-Peak Day Single, Child Flat Fare Single and High Speed Upgrade Single 88: Off-Peak Day Single 96: Off-Peak Single (*)

(*) This is the special "Saver Half" half-rate Off-Peak Single issued only in conjunction with an Advance ticket booked for the reverse journey as part of the same booking (xxx/2016). Code 62 was used for ordinary Off-Peak Singles.

Possible mapping relating to validity field:

40	TWO DAYS 64	BOOKDTRAINONLY 72	AS ADVERTISED 81	ON DATE SHOWN 85	SEE RESTRICTNS 88	SEE RESTRICTNS

41	FIVE DAYS

S&B: London Midland, London Overground, Abellio Greater Anglia, f Capital Connect, Southeastern and f Scotrail

They stopped appearing on S&B tickets in December 2014, being replaced by standard alphanumeric validity codes.

Parkeon: They stopped appearing on Parkeon tickets in April 2015.

ToD-only machines in all cases, on East Midlands Trains, f Great Western, Northern and South West Trains. -->

Rolltic machine

 * Commons pic of Rolltic machine

Carnets

 * NR website: East Coast Carnet 5
 * NR website: East Midlands Trains Carnet
 * NR website: Gatwick Express Carnet
 * NR website: Grand Central Carnet
 * MyTrainTicket website: Carnets
 * NR website: Scotrail Flexipasses
 * Scotrail website: Scotrail Flexipasses
 * Guardian blog about Carnets (NXEA in particular)
 * Thameslink website: Scotrail Flexipasses
 * NR website: Thameslink/Great Northern Carnets
 * Chiltern website: Carnets
 * Chiltern website: Carnet T&Cs
 * NR website: Chiltern Carnets
 * Grand Central website: Carnets
 * Grand Central website: Carnet T&Cs
 * AGA website: Greater Anglia Carnets
 * HEX Carnets
 * Passenger Focus: FCC Carnet Trial (undated PR)
 * RailAir Carnets
 * BBC News article on FCC Carnets (2012)

Check, use, archive, save as necessary

 * Trainline/Evolvi/TMCs generally: Jumping the Barriers: Driving more business travel onto the railway (report) (Archive)
 * TRIBUTE: TRIBUTE user guide!
 * LENNON: Good concise briefing sheet; Rail Demand Forecasting Using the Passenger Demand Forecasting Handbook (large PDF; mentions LENNON and MOIRA)
 * ORCATS: User guide Railforums discussion and examples; Info in The Grauniad; More info in a blog
 * RJIS: "ATOC signed a contract to provide the Rail Journey Information System (RJIS) in July 1998" (Key Point 12); More about it
 * BemroseBooth and Magnadata Group: Feb 2010 update; another; July 2010 update; Magnadata stuff
 * ATOC TSA Schedule 17 (ticket office stuff): Dec 2012 version and May 2013 version
 * Evolvi press releases: Move to Reading; GPS fares available from 12/12/2007; More on GPS, ToD etc; More on ToD etc
 * ATOC Guide to Settlement
 * Network Rail: Current Passenger Demand
 * "The report recommends removing staff from all category E stations"
 * ToD ticketing going in "the cloud" (loads of other links at the bottom of this article)
 * Newsrail Express 319 – are there others available at this URL?

FoI requests

 * Revenue staff training
 * Protected season ticket fares
 * RCI ticket guide
 * Regulated flows
 * Through ticketing (non-Travelcard)
 * Reason for withdrawal of easement
 * Avantix Mobile training material
 * Excesses
 * Passenger oriented display error (eh?)
 * NLCs
 * Concession agreement

Interesting stuff in Google searches

 * "TIS Accreditation" with quotes
 * "Nalco ATOC" with quotes
 * "Ticketing and Concessionary Travel on Public Transport" with quotes
 * "TICKETING AND SETTLEMENT AGREEMENT" with quotes
 * "Rail ticket printer" with quotes

Heathrow

 * Rickards story (8/4/1966)
 * Rickards story (8/9/1967)
 * Rickards story (9/6/1967)
 * Reading stats (2010)
 * FoI request: Oyster PAYG

Refs

 * This would be the citation for the Presidential Address:
 * Newsrail Express 319:
 * NMF thing:
 * NRG Data Feed Spec (SP0037):
 * Routeing Guide Easements:
 * Routeing Guide Easements:

Group stations

 * Stuff/notes hidden in here:

<!-- Interavailability of tickets across sets of stations is not a new concept: members will be familiar with Edmonson tickets issued to long lists of stations in the same geographical area, or to "any destination not exceeding x miles". The practice became standardised in the late British Rail era as computerised ticket issuing systems took over: official "station groups" were created in nearly 100 towns and cities which had more than one station. These pseudo-locations, also known as "group stations", were given their own National Location Codes (NLCs) and a standard name format (the town name plus the suffix "BR"), and were used as the basis for fare-setting and ticket-issuing to and from the town - except in exceptional cases.

Like all aspects of fare setting and ticket issuing, the station group concept has been subject to gradual change in scope and appearance. New exceptions have come and gone; stations have been removed from or added to groups - sometimes for brief periods - new groups have been created; and others have been abandoned. Privatisation brought a new dimension to the station group concept: in many cases, revenue now had to be divided between different Train Operating Companies. Stations with automatic ticket gates need to be able to deal correctly with tickets issued to group stations - especially in the London "super-group", the largest and most complicated example of a group station. New wording had to appear on tickets, as the former "BR" suffix was obsolete.

Why were group stations created? - Competition in early days of railway: competing stations/lines instead of joint town-centre stations (London, Maidstone, Canterbury) - Towns with major station on a main line and a suburban station on a branch line (Bedford, Reading, Tunbridge Wells) - Allow choice of routes to/from town (most examples)

But some places which would seem to "qualify" have never had a station group. Cases could be made for Acton (Central and Main Line, and possibly South Acton as well), Bicester (North and Town), Bromley (North and South) and Hackney (Central and Downs, and possibly Hackney Wick as well), among others; members may be able to think of other examples.

Exceptions - Early days: sometimes the specific station was used for local journeys (Maidstone West examples, eg... and also stuff like Battersea Park-London Victoria and South Bermondsey-London Bridge, which persisted a lot later) - Gatwick Airport in respect of London - Promo fares, esp post-privatisation, and certain TOC-specific fares: Price Buster, Northern Duo, Special Day Rtn, Chiltern-only fares from BHM to LDN etc. (note also that Southern have introduced Season Tkts to e.g. London Victoria that are cheaper than the London Terminals equivalent - refs are http://www.southernrailway.com/tickets-and-fares/season-tickets/ and http://www.southernrailway.com/download/300.3/season-ticket-fares-to-london-victoria/) - Non-travel tickets relating specifically to the station of issue: Pfm, Car Park, Receipt etc (ODTCs are sometimes an exception, sometimes not!) - Heathrow RailAir fares to/from Reading - Tickets between individual group stations (e.g. Colchester to Colchester Town) - East Croydon to other S London stations in 2011 - Scotrail Flexipasses to/from Glasgow (although Chiltern Carnets show LONDON TERMINALS!) - Tickets from Portsmouth to Isle of Wight destinations -->


 * Refs from Journal...
 * Feb 2003: Brief mention of London group and the Gatwick Airport exception
 * Oct 2004: KXT Ascom EasyTicket oddity
 * Feb 2005 (p71): some promo tickets are issued point-to-point rather than to station groups (e.g. Northern Duo)
 * Apr 2005 (p142): Anomalies re. group stations to London, esp. involving Penge


 * Journal 565 (Feb 2011) p63: "Standard priced tickets were only issued to specific London termini. This changed with the fares increase of 26 April 1970 when the destination LONDON (SR) came into use."


 * Note to self on Station group (railway): refs needed
 * Second para of lead: cite Pontefract example in September 2011 Journal.
 * Each station group was also allocated its own National Location Code (NLC)—a four-digit code used for accounting and to attribute revenue to locations on the railway network: bound to be a ref in a Journal somewhere. (Could also be used on the NLC article.)
 * The solution, introduced gradually from November 1997 and uploaded to all ticket issuing systems by January 1998: find a ref in a contemporary Journal and in the Fares Manuals.
 * The NLC appeared on PORTIS/SPORTIS tickets...: may be a ref in the manual?
 * but APTIS tickets (and those from later systems) always showed the NLC of the actual station of issue, even where a ticket was issued from a "station group".: check Journals.
 * The London group was changed three times.: Check early 1998 Journals and Fares Manuals.
 * As GAINSBOROUGH is 12 characters in length...: Check Journal indexes for mentions of Gainsborough.