[0001] This invention relates to a fare collection and processing system and apparatus therefor
particularly for use on railway systems such as the London Regional Transport Underground
System, and a particular but not exclusive feature of the present invention is to
provide an automatic fare collection system in which tickets are checked to verify
the data thereon or determine their validity.
[0002] The system and apparatus of the present invention includes ticket issue machines
operated by a passenger (hereinafter termed passenger operated machines or POMs),
and such POMs include few fare machines (FFMs) and multi-fare machines (MFMs) both
hereinafter described. The system and apparatus of the present invention also includes
ticket office machines (TOMs). All three types of ticket issue machines produce standard
tickets printed on one face and magnetically encoded with data on the reverse side.
[0003] At each station of the system, a number of ticket issue machines (TOMs, FFMs and
MFMs) are installed and linked to a station computer (SC). The station computer system
includes station control units (SCUs) which provide local control and monitoring of
the ticket issue machines and enable printed accounting reports to be produced for
the benefit of supervisory staff. Each station computer (SC) is linked via a communications
system e.g. a telephone system to control computers for the transmission of accounting
and statistical data and for the receipt of control commands and fare tables/commercial
rules.
[0004] Additionally at each station there is provided a facility to verify the data recorded
on a ticket or to determine its validity. In one embodiment of the invention such
a facility comprises a verifier, a version of which may be hand held and which is
employed to read data recorded magnetically on the reverse side of each ticket and
to display the information read. Such a verifier allows supervisory personnel to verify
that the printed data recorded on the face of the ticket corresponds with data magnetically
encoded on the reverse side of the ticket such as to detect any attempt to fraudulently
amend the printed data or magnetically encoded data. Such a portable verifier is not
linked to the station computer system.
[0005] Alternatively, each station may be provided with one or more automatic passenger
gates which are arranged to accept tickets originating from the ticket issue machines
and presented to a slot in the gate by a passenger, and to determine the validity
of the ticket. If valid, the ticket coding is arranged to be updated by the gate mechanism
and the gate barrier, which may be in the form of paddles, operated to allow a passenger
to proceed therethrough. The ticket may normally be returned to the passenger but
at the termination of a journey for which the ticket is valid, the ticket may be captured.
The gating devices are arranged to communicate with the station computer. With such
a system each station computer supports the station control units (SCU's), the respective
TOMs, the POMs and the passenger gates; with the TOM'
S, POM's and passanger gates operating independently of the station computer (SC),
but all devices send details of transactions to the station computer. The SCU's remain
dependent on the SC.
[0006] Thus, according to one aspect of the present invention there is provided a fare collection
and processing system wherein there is provided at each of a plurality of stations,
at least one passenger operated ticket issue machine and at least one ticket office
ticket issue machine all arranged to communicate with a station computer, said machines
operating independently of the station computer and sending details of transactions
thereto, means for verifying data on tickets issued by said ticket issue means and
operating independently of said station computer and said station computer of each
station communicating with a central system computer arranged to collect data from
all stations for storage and processing.
[0007] In an embodiment of the invention, the ticket data verifying means comprises a verifier
device arranged to compare data printed on one side of a ticket with data magnetically
encoded on the reverse side of the ticket, said verifier being in one version, hand
held.
[0008] According to a further aspect of the present invention there is provided an automatic
fare collection and processing system wherein there is provided at each of a plurality
of stations, at least one passenger operated ticket machine, at least one ticket office
ticket issue machine and at least one automatic passenger gating device, all arranged
to communicate with a station computer, said machines and said at least one gating
device operating independently of the station computer, and sending details of transactions
thereto, said at least one gating device performing a validity check on any ticket
presented thereto and operating to allow a passenger to pass therethrough only on
presentation thereto of a valid ticket, and the station computer of each station communicating
with at least one central computer arranged to collect data from all stations for
storage and processing.
[0009] In an embodiment of the invention, a station control unit (SCU) is linked via the
station computer to the passenger operated machines and to the gating devices for
the monitoring of these machines and devices from the station ticket offices.
[0010] According to a'still further aspect of the present invention there is provided an
automatic fare collection and processing system including 'open' and 'closed' type
stations, and wherein there is provided at each of a plurality of 'closed' stations
in the system, at least one ticket"office ticket issue machine and at least one passenger
operated ticket issue machine and at least one automatic passenger gating device,
all arranged to communicate with a station computer linked with a central computer
and said stations having means at each entry and exit point for validating tickets
presented thereto either forming part of the gating device, or in lieu thereof whereby
no journey which commences or terminates within a closed station can be completed
on the system without validation of a ticket at both entry and exit points of the
system.
[0011] The invention will now be described by way of example only with particular reference
to the accompanying drawings wherein:
Figure 1 is a block schematic diagram of the general layout of the system;
Figure 2 is a functional block diagram of a ticket office ticket-issue machine;
Figure 3 is a functional block diagram of a multi-fare machine;
Figure 4 is a functional block diagram of a multi-fare machine;
Figure 5 is a block diagram of the arrangement of machines and gates at station level;
Figure 6 is a block diagram showing the layout of an automatic gating device;
Figure 7 is a flow diagram of a logical audit trail;
Figure 8 is a diagram of the physical audit trail;
Figure 9 is a block diagram of the computer system network; and
Figure 10 is a general schematic diagram of an underground ticketing system of the
present invention.
[0012] The fare collection and processing system of the present invention is illustrated
in Figure 1 which shows the main components of the system and their inter-relationship.
Only one station of the system is illustrated for clarity. The system illustrated
is a distributed network of ticket issue machines, computer systems and associated
gating devices and which provides automatic ticket issue, ticket checking and centralised
accounting and statistical data.
[0013] At each station as shown in Figure 5, a number of ticket issue machines (TOMs, FFMs,
MFMs) are installed together with ticket checking devices such as gates, all linked
to a station computer (SC). The station computer system includes station control units
(SCUs) which provide local control and monitoring of the various machines and enable
printed accounting reports to be produced- The station computers are linked via a
telephone system (shown in Figure 1 by dot-dash lines X,Y) to a remote central computer
system which provides a secure storage in its front end processors of all revenue
and statistics data received from each station. This data is then converted by a data
and protocol conversion system and transmitted to a central reporting system (CRS)
which is a mainframe system external to the system of the present invention.
[0014] The status of station equipment is monitored by central supervisory facilities and
information made available on VDU terminals to an operations control centre (OCC)
and to an engineering report centre (ERC) (Figure 1) as hereinafter described.
[0015] The external central reporting system is supplied with accounts and statistics data
to allow various reports to be produced for management.
[0016] Updates to the system and new fares/commercial rules are developed on a system development/support
centre (SD/RC) and when fully tested are loaded down to the Computer Centre under
strict control.
[0017] The system report centre (SRC) is used by the computer operators and data network,
and to perform any computer system housekeeping necessary to effect a smooth running
of the overall system.
[0018] In Figure 1, the station computer (SC) is linked to the central computers (CC) which
pass information to the central reporting system (CRS). Reports and interogation data
pass between the CRS and an accounts office 0 via link R/I and the office 0 supplies
operations reports (OR) planning reports (PR) and engineering reports (ER). The office
0 also receives cash and statements from the bank from link A. The
CRS supplies fares, book transactions, accounts and statistics data to the System Development/Support
Centre via link J which also receives software system maintenance data and rules from
a commercial office over links G and H respectively- The System Report Centre (SRC)
supplies and receives data to and from the central computers (CC) which receives control
data from the operation control centre (CCC) which in turn receives status, alarms
and reports from an operations centre over link L and supplies data thereto.
[0019] Fault and diagnostics data is supplied from the central computers (CC) to the engineering
report centre (ERC) via link E and link D enables interrogation of the ERC and the
transmission of status, alarms and reports data.
[0020] The station computer as controlled and controls the ticket hall SCC(a) and the ticket
office SCU(b) over links 1 and 2 respectively and SCU(a) supplies control data to
allow a travelling inspector to verify the data printed and encoded on a ticket by
means of a portable verifier V; link 4 indicates the passing of tickets between the
verifier V and the inspector. The gate G is linked to the inspector for ticket checks
via link 5 and with the station computer-(SC) via link 6. Link 7 indicates tickets
and credits from the gate G. The FFM's are linked to the SC via link 8 and supply
tickets and cash via links 9, 10. Similarly, the..MFM's, along with the FFM's receive
and transmit transaction accounts, statistics and status data to and from the SC via
links 8 and 12 and the tickets and cash from the MFM's are shown by links 10, 13.
The TOM's are linked to the SC via link 17 for rules and fare data and supplier tickets
over link 14 to a clerks position who receives cash from the MFM's and FFM's and tickets
from the TOM's. Link 15 indicates the communication between the clerks position and
the booking hall SCU(b) and cash from the clerks position is supplied to a supervisor
via link 16 who receives accounts summary and operating status data from the SCU(b).
Cash from the supervisor is transmitted to the bank via joint A.
Ticket Office Ticket Issue Machine (TOM)
[0021] The TOMs of the system of the invention, are used by booking office clerks to serve
passengers through the window of a ticket office, with any of the types of tickets
available on the system. Each clerk has his individual account records maintained
by the TOM and tickets can only be issued after a clerk has identified himself to
the TOM using a personal identity card and identification number (PIN). The clerk
is presented with a printed account report at the end of each spell of duty, at the
end of his shift and whenever an abnormal event has occurred or a ticket value or
period has changed- The functional block diagram of a TOM is shown in Figure 2. The
TOM consists of an issuing unit and a console for use by the clerk.
[0022] Two types of partially preprinted ticket stock material are used, the appropriate
type being automatically determined by the machine depending on the ticket requested
by the operator. This allows a durable stock to be used for long-term tickets such
as seasons, whilst a lower cost material may be used for short-term tickets such as
singles and returns. The low-cost material is roll fed, whilst the durable material
is pre-cut, and manually inserted for each such issue as required. The tickets are
supplied from a ticket office window and a screen on the console indicates what is
being transacted. The ticket issuing unit issues the ticket and a visual display available
to the passenger provides data indicative of the fare at the time the ticket is issued
or the value of a transaction made.
[0023] A tally roll provided on the console prints in duplicate any flagged transaction,
that is a non-standard transaction such as one where the fare has been keyed in. It
also prints the accounts which are displayed concurrently on the screen and the summary
accounts for clerk specifications and traffic days.
[0024] Each TOM relies on the station computer (SC) for all its fare and ticket format data,
but then having received this data, it can then operate independently of the SC until
the audit data collected exceeds the capacity of the machine, at which point it will
go out of service.
[0025] The TOM console consists of a keyboard, a display screen and a tally roll printer.
A bank of keys relate to the most commonly used fares and depression of a key causes
the ticket to be issued. A mother bank of keys allow tickets of any type to be printed
and issued. Ten numeric keys are used to input such entries as station code, expiry
dates and fares, if necessary. Further keys enable clerk accounts to be displayed
(or printed) and tickets to be interpreted. This last mentioned function enables a
ticket to be inserted in the ticket issuing unit, its magnetic data read off and displayed
on the screen. Other keys on the keyboard are for operating change dispensing apparatus.
[0026] The display provides an indication of the type of ticket being prepared including
its serial number and price- If keys are depressed in an illogical order then a warning
legend is displayed on the screen-Accounts are also displayed as are records at sign
on and sign off.
[0027] The tally roll printer is an ink ribbon needle type printer and prints whenever a
sign on or sign off occurs, it prints accounts when requested or automatically and
prints transactions when the 'value as keyed' key is depressed e.g. when a fare is
manually entered, so that the validity of such transactions can be checked. The printer
can, on request, print any screen display.
[0028] The TOM issuing unit produces the ticket and delivers it to a counter. Before producing
tickets from the TOM, the operator must first sign on by turning a key to 'OPERATE'
as appropriate, "swiping" his I.D. card in the slot and entering his personal identification
number on the panel. To sign off, the key is turned to NORMAL. This panel will also
display the state the machine is in and error codes relating to the machine.
[0029] The tickets are cut from a roll mounted on the ticket issuing unit of the machine.
[0030] When a ticket is requested, the cut ticket passes under a print head that prints
the information one one side of the stock. It is then magnetically encoded. The code
on the ticket is then read to check that the encoding is correct. If it is correct
the ticket is sent forward to the operator. If the read after write check indicates
that the coding is unsatisfactory the ticket is returned via a diverter into a capture
bin and a second ticket is produced. If the second ticket fails a third is produced,
but if that fails the machine shuts down. This arrangement is intended to cope in
the event of a local imperfection in the oxide coating of the ticket stock.
[0031] The information for the printing and encoding resides in the TOM for each transaction-
For each transaction a message is sent to the SC to indicate that a ticket has been
produced. A record is kept in a power-loss protected battery protected Audit Register
in the TOM of the total value of travel sold and at the end of his shift the operator
obtains a record of this total that he must reconcile with cash taken. This information
is also available at the SCU. A supervisor can use his card to obtain each operator's
account on request and also a summary of accounts for all operators for any traffic
day up to 6 days previously
[0032] A display positioned at the window faces the passenger and indicates the value for
the current transaction.
Passenger Operated Machines (POMS)
[0033] These consist of few fare machines (FFMs) and multi-fare machines (MFMs). The FFM
is a passenger operated machine (POM) designed for use by the experienced passenger
who knows the ticket/fare he wants and has valid coins to meet the.value of the ticket.
Ticket selection is from one of ten buttons on the front panel of the machine. It
is able to accept five coin denominations and issue change when available. The functional
block diagram of a multi-fare machine is shown in Figure 3 and that of a few-fare
machine in Figure 4. The multi-fare machine (MFM) is also a passenger operated machine
(POM) but is intended for use by passengers who do not know their fare and who are
unable to obtain a ticket from the FFM. The MFM allows the passenger to select from
a number of destinations and ticket types. The fare to be paid is displayed to the
passenger and it is able to accept five coins and one note denomination and issue
change when available.
[0034] Both types of POMs use the same identity card and personal identification number
system to ensure that only authorised staff can gain access for cashing up the machines.
Fewfare Machine
[0035] In operation, the passenger presses the button corresponding to the ticket he wishes
to purchase. The amount to pay is displayed on a red LED display and he is invited
to insert coins; 5p, lOp, 20p, 50p and 100p coins are accepted- As money is inserted
the "amount to pay" display is decremented and when zero the machine will issue the
ticket. The machine is able to supply 5p, lOp, 20p, 50p coins in change when a predetermined
number of coins is available in the tubes. These tubes capture inserted coins. If
more than the required money is inserted in "change given" mode, then the appropriate
change is dispensed with the ticket- If it is in "exact money" mode, and more than
the required amount of money is inserted, no ticket is issued and all the money is
returned. The machine changes automatically between "change given" and "exact money"
modes when the correct conditions exist.
[0036] If the passenger chooses to insert money before pressing a button, the display will
show the amount paid until a button is pressed, when it continues as before.
[0037] A "Cancel" button will stop a transaction, clear the display and return the value
of cash inserted, provided production of the ticket has not started.
[0038] A "Call Assistance" button indication is provided at the SCU and sounds a warning
buzzer in the ticket office. A flashing light asks the passenger to wait by the machine.
The warning is cancelled by pressing a button fitted on top of the machine.
[0039] A "CLOSED" sign indicates when the machine is not in service and coins cannot be
inserted when this condition prevails.
[0040] The ticket and change are delivered to a bowl. The paper is mounted in a similar
fashion to the TOM. The printing and encoding processes are identical with the TOM
and most parts are interchangeable.
[0041] The fewfare machine does not rely on the SC and will stand alone if the SC has failed.
However, in normal operation the machine will send transaction data to the SC at intervals
and at sign on, and will receive new fares table information. If the SC is not operating
properly then up to 28 sign-ons can be achieved. In this case transaction data and
the vital data is stored in the Audit Register. A display on the service panel will
indicate the number of sign-ons that remain before the store is filled.
[0042] At each sign on, whatever the state of the SC, a printout at the local printer provides
details of cash contents and value of tickets sold at the machine since the last service.
This is reconciled by the operator against the money removed.
[0043] The information concerning what tickets to produce for each button is contained in
the fares data received from the SC. At a fare change this is automatically replaced,
through communication with the SC. This command can be programmed in advance and requires
no operating or maintenance staff action at the time of implementation, and at the
same time button legends have to be altered.
Multi Fare Machine
[0044] The multi-fare machine is designed for the passenger who does not know his fare or
perhaps wishes to pay with five pound notes. It has a button for every station and
eight buttons for eight types of ticket. It is twice the width of the fewfare machine
The tickets produced are identical in format to the fewfare and TOM day tickets.
[0045] The passenger first presses the button corresponding to the station he wishes to
travel to and its name is displayed on a plasma display. He then presses one of the
eight ticket type buttons and this is displayed similarly. The fare is displayed and
a shutter across the coin insertion slot is opened. Illuminated legends are provided
to assist the passenger to follow the correct sequence of operation.
[0046] The passenger can now insert either 5p, lOp, 20p, 50p or 100p coins into the slot
or five pound notes into the note acceptor. As coins or notes are accepted, the "amount
to pay" display is decremented and change is given and tickets are issued in the same
manner as the fewfare machine.
[0047] Unlike the fewfare machine, the passenger cannot insert money before selecting a
ticket type.
[0048] "Exact Money"/"Change Given" signs and "Cancel"/"Call Assistance" buttons are similar
to the fewfare, as is the ticket/change bowl.
[0049] Insertion of five pound notes has to be one of two particular ways round as shown
on the entry mouth. If the acceptor does not recognise the colour distribution pattern
it is returned by reversing it out of the mouth. If accepted it is held in escrow
and if the transaction is cancelled the note is returned through a slot lower down
the machine. If the transaction is completed, it is passed from the escrow into a
note vault. The machine is able to supply 5p, 10p, 50p and 100p coins in change when
a predetermined number of coins is available in the tubes; as with the fewfare machine.
[0050] The coin acceptor holds coins for change giving in tubes. These can be emptied to
the coin vault when cash servicing if required.
[0051] The ticket producing hardware is again similar to that of the fewfare machine as
are many of the electronic components including the Audit Register.
[0052] The multi-fare machine can operate without a station computer (SC) but will then
accept up to 28 sign-ons before going out of service, like the fewfare. The printouts
that are produced by the multifare machine appear on the same printer as the fewfare
machine.
[0053] When first switched on the multi-fare machine relies on the SC for the fare tables
that it requires to operate. When a fare change occurs, these tables are replaced
by a new set on command from the SC. This command can be programmed in advance and
normally requires no operating or maintenance staff action at the time of implementation.
Central Supervisory Facilities
[0054] A number of centralised facilities are provided to alow staff to monitor, control
and maintain various elements of the system. These facilities include the operations
control centre (OCC) (Figure 1) which monitors and controls the functions operation
of the overall system, the engineering report centre (ERC) which controls the maintenance
and repair of the various components of the system including station computers (SC's)
peripherals and devices but excluding modems and communications lines, and a system
report centre (SRC) which controls the maintenance and repair of the computer systems
and peripherals at a central site but excluding modems and communications lines.
[0055] To meet these operational requirements, the computer systems log all significant
status changes of major components and maintain a data base containing the current
status of each component along with its immediate history. This information is available
to OCC and ERC staff on an enquiry basis and also as a series of regular reports-
When status changes occur that require prompt attention from the staff, alarms and
warning messages are produced automatically.
[0056] The system provides centralised facilities to update commercial rules and fare tables
via a system development facility and to update staff black-lists and station aliasing
across the whole network via the operations control centre (OCC).
(a) Operations Control Centre (OCC)
[0057] The Operations Control Centre (OCC Figure 1 monitors and controls the functional
operations of the system through the computer terminals and printers. The OCC monitors
the TOM's, the MFM's, the FFM's, the Station Computers (SC's) and associated Station
Control Units (SCU's), the central computers and associated peripherals and the communications
links. In addition, the (OCC) monitors and controls the TOM's, MFM's, FFM's and any
gating units of the system.
[0058] Each of the components of the system is able to signal any significant status change
to the Control Centre (OCC), and these changes are used to update a database which
contains the current status of each component of the system, a log of all status changes
for the current day, a log of all status changes for the previous day, and a log of
all status changes for the day before the previous day.
[0059] Significant status changes are status changes detected by a particular station level
device e.g. ticket stock low, door of machine open, status changes detected by a station
computer failure, and status changes in the central computer configuration e.g. failure
to communicate with a particular station, terminal failure. Significant status changes
also include text input from the Engineering Report Centre (ERC) e.g. action taken
to repair a device, cause of fault, and messages sent from stations to the centre
or from the centre to stations on user command.
(b) Engineering Report Centre (ERC)
[0060] The ERC (Figure 1) has a number of computer terminals and printers through which
it monitors error conditions in the components of the system, and provides a logging
mechanism for engineers to record maintenance and repair details for individual components
of the system.
(c) System Report Centre
[0061] The System Report Centre (SRC) (Figure 1) has a number of system consoles for the
central site computers- These consoles are used by the system to report significant
hardware or software conditions and to accept operator commands to control the central
and station computer (SC) systems (e.g. to load magnetic tape).
Revenue Audit Trail
[0062] The system of the present invention provides a secure primary audit path from station
devices to the central computer centre. Audit data is passed to the Management Information
System for processing and report generation. A back-up path via an adjacent station
is provided to allow collection of essential accounting data in the event of a failure
of the direct communications between the station level and the computer centre.
[0063] The logical audit trail is shown in Figure 7.
[0064] At the station level the ticket machines retain essential accounting data in secure
audit registers. Each ticket machine keeps at least two independently calculated totals
for value of tickets issued. In the case of POMs, records are kept of total cash accepted,
kept cash where no ticket was issued and cash by denomination. As a result, the ticket
machine can perform an internal account reconciliation and in a POM, a cash reconciliation.
The account details are only made available to authorised personnel at station level
through use of identity cards and personal identification numbers. Only booking clerks
and supervisors would be authorised in this context.
[0065] The full details of each individual transaction and the summary accounts are sent
to the Computer Centre and acknowledged back to the ticket machines. Only when an
acknowledgement has been received from the Centre and from the supervisor locally
will the ticket machine discard the accounts data.
[0066] Passengers present cash to the POMs or booking clerk and receive tickets in return.
[0067] The booking clerk receives cash from passengers in exchange for tickets and from
servicing the POMs. The booking clerk receives accounts from the ticket machines against
his identity card and personal identification number (PIN). These accounts are used
to reconcile with cash collected from each POM servicing and TOM spell/duty. The accounts.and
cash are passed to the supervisor.
[0068] The supervisor receives cash and accounts from the booking clerks and also receives
Accounts Summaries from the ticket machines (via the SCU Printer) against his identity
card and PIN. The supervisor reconciles the accounts/cash at station level and banks
the cash.
[0069] Accounts and transaction data received at the Data Output Centre can be used to reproduce
an internal reconciliation of the accounts.
[0070] The Accounts Office receives the accounts reports from the CRS statements from the
bank and control of the cash banked by all the supervisors. The Accounts Office reconciles
the accounts against the bank statements and produces management accounting reports
as appropriate.
[0071] Note that individual transaction records are created by the ticket issue machines
for each ticket issued. These are stored in a non-volatile memory and where possible
are transmitted to the central computers. In the event that the transaction store
for the machine becomes full the subsequent transaction records overwrite previously
stored records 'oldest first'. The transaction store sizes for each type of ticket
issue machine have been estimated to be sufficient for a worst case 48 hours use.
[0072] The Logical Trail described is implemented physically as a Primary Trail and a Secondary
Trail. These are illustrated in Figure 8.
[0073] (a) Primary Trail: The Primary Trail is marked (1) in Figure 8 and is the path taken
by audit data when the end-to-end connection is available.
[0074] (b) Secondary Trail: The optional Secondary Trail is marked (2) in Figure 8. Secondary
Trails are available in the case of failures of the following:
device to Station Computer link failed (either)
Station Computer failed (either)
device to Station Computer link failed (either and Station Computer failed (other)
Front End Processor to Station Computer link failed
Front End Processor failed (one only).
[0075] Summarising the above, the POMs and TOMs communicate with the station computer (SC).
Passenger gates are arranged to open to provide entry to or exit from the system only
when a valid ticket is presented thereto. The TOM's the passenger gates and the POM's,
send details of transactions to the SC. The SC in turn communicates with the central
computers which collect data from all stations and store the data for the preparation
of reports. The central computers are also used to down line load programs and tables
to the TOMs and multi-fare machines (MFMs) of the POMs via the station computer (SC).
[0076] As shown in Figure 1, terminals are provided representing the control centres from
which operators could monitor the system and individual stations.
[0077] Station Control Units (SCU's) are provided at each station (SCU(b) of Figure 1) and
communicate through the SC with the POM's and passenger gates to enable them to be
monitored and controlled from the clerk's position in the ticket office, or from another
SCU in the ticket hall (SCU(a) of Figure 1) by a supervisor. In addition a printer
is installed to provide a printout of TOM's and POM audit data for local reconciliation
of the station level accounts.
Passenger Gates
[0078] The passenger gates are designed to open only when a valid ticket is inserted (although
the Operator can open them manually via the SCU's). The reversible gate can be operated
in entry or exit mode using a different transporter and set of doors in each case.
A plurality of infra-red photocells monitor the passage of people through the gates.
The gates and gating mechanism may be of the type described in GB Patents Nos. 1436712
and 1397186. A typical gating device layout is shown in Figure 6.
[0079] The passenger inserts the ticket in the entry slot on the right hand stanchion as
he enters. The ticket is taken by the first set of rollers into the transporter where
it is read by a head. The ticket data is extracted and the gate uses its internal
logic tables to determine whether the ticket is valid or not. If invalid, the gate
returns the ticket to the passenger through the far slot, illuminates a sign reading
"Seek Assistance" and sounds an audible warning. To aid staff a two digit code on
the side of the gate indicates why the ticket was rejected and the gates remain closed.
If the gate finds the ticket valid, however, the gate generates a credit and causes
the encoded data to be rewritten on the ticket. The gate confirms that the data has
been written correctly by performing a read-after-write check. If this is the case,
the ticket is returned to the passenger via the far slot and a sign is illuminated
saying "Take Ticket". When the ticket is taken the doors open enabling the passenger
to walk through. At this point the error display shows "00" indicating no error.
[0080] The infra-red beams ensure that the gate closes only when the passenger has passed.
Up to three credits can be stored which would keep the gates open for the passage
of three people and then close. If no-one goes through, the gate will close after
a predetermined time e.g. 15 seconds (table loadable parameter). The infra-red beams
pass through the perspex windows in the casing to reflectors mounted on the other
side of the walkway.
[0081] If the ticket inserted is recognised as a Child Ticket a lamp above the gate is illuminated
and an audible warning sound generated to identify passengers using Child Tickets.
[0082] The logic employed to use the photocell data to control the doors is complex. Should
a person try to push through a gate in either direction the warning will sound and
a ticket entry shutter closes to prevent tickets from being inserted and hence prevent
theft of credit. The ticket entry shutter also closes between the time a ticket is
inserted and removed, this prevents two tickets from being in the transporter at the
same time. The shutter also closes when three credits have been accumulated.
[0083] The doors, when closed are locked in place such that reasonable pressure against
them will not force them open. A high force, equivalent to a person hitting them very
heavily will just open them; this feature is intended to prevent injury to passengers
using the gates, say in an unruly crowd.
[0084] On the exit side, valid tickets which give a credit and have no further validity
are captured in a ticket bin.
Station Control Unit (SCU) & Printer
[0085] To enable station staff to monitor and control the operation of gates and POMs and
to provide a POM local audit printout it is necessary to employ Station Control Units
(SCU's) supported by the SC which is connected by multi-dropped lines to the POM's
and gates. Its interface with the operators is by means of two display terminals,
one in the ticket office near the booking clerks position and one in the ticket hall
for supervisory staff to use. These are standard V
DU's with adapted keyboards. A printer produces the POM cash service reports and prints
error messages including POM power failures.
Operation of Ticket Office Station Control Unit
[0086] The Ticket Office SCU indicates vandalism (back door opened without a valid sign),
Out of Service or Fault, in test mode, in exact fare mode, cash servicing in progress,
cash full (vault 80% full), change low, paper low (one roll out), assistance required,
link between the POM and the SC not functioning.
[0087] For each gate the SCU shows when a gate is out of service or has a fault, or when
it is in test mode. The keyboard enables the operator to change the gate from entry
to exit (or vice versa) or off (all doors shut) or released (which opens them for
as long as the appropriate key is depressed).
[0088] Another set of keys can be used to change the level or logic checks made on each
ticket. For instance, "accept all tickets inwards" will give credit to any ticket
presented provided it is coded. Thus it will not check for date, re-use, etc. and
is useful when the correct tables are unavailable or faulty tickets are known to be
in the system.
[0089] Another facility is the ability to prevent Child Tickets from operating the gates.
[0090] The separate emergency open control removes the air from the gates and allows passengers
to push past-This feature is for emergencies requiring passengers to pass unhindered
at times of failure or emergency.
Operation of Ticket Hall Station Control Units
[0091] The Ticket Hall SCU(a) Figure 1, is similar to the Ticket Office SCU(b) but being
in the passenger area, it has a lockable cover. Also, the facilities are somewhat
different.
[0092] There are a number of status indications for each POM e.g. Preparations, Change Low,
Cash Full and Cash Service) but the keyboard enables supervisors to monitor tickets
through the gates- To achieve this a selection of keys are pressed corresponding to
the type of ticket the supervisor wishes to monitor, such as privilege tickets. Eight
types of ticket can be monitored and more than one can be monitored at once if required.
When a ticket of the type selected is used in a gate a small arrow is illuminated
pointing to the relevant gate from the side where the passenger leaves it. Thus, when
the light is illuminated the supervisor is aware of the type of ticket being used.
Printer
[0093] The printer, housed in the POM enclosure, will print an account for a POM whenever
a valid sign-on is completed by an operator. Total cash and total ticket sales are
included in the statement as are details for cash make-up and for sales by ticket
types. This printout will also occur automatically at each "End-of-Day" to show the
account state of each machine after each traffic day.
[0094] This printer will also record the state of the POM accounts after that occur on the
POM's.
Engineering Aspects
[0095] The machines have been designed around a modular system whereby most of the mechanisms
and all the electronics are contained in units that can easily be unplugged, removed,
replaced and reconnected to the body of the machine. Furthermore, many of these modules
are common between different types of machines. The principle of repair is to use
the error code or codes as displayed on the SP to identify which unit is faulty and
to replace it in order to return the machine quickly to service. The faulty unit is
then repaired off site.
[0096] It is possible to use the SPP to carry out diagnostics checks on such items as photocells
and jammed buttons.
Operating Aspects
[0097] The booking office operator's task is made simpler by being able to produce all tickets
and complete other transactions from one machine, rather than rely on card stocks-
Hence no ticket is produced until required so there are no value stocks in the office
that have to be accounted for.
Tickets and Ticket Logic
[0098] The tickets used and produced by the system are of a standard, credit-card size with
printing on a coloured face and a magnetic coating on the back. Paper is used as the
base material in POMs as those tickets are used for only one or two journeys. The
TOMs normally use a stock based on plastics material, designed to be more durable
when made as a season or travelcard.
[0099] The station of origin (or zone details), date, serial number and machine number are
all printed in clear in order that they can be read at barriers and by travelling
ticket inspectors. The format varies slightly between types of tickets. Up to four
lines of text can be printed to indicate availability of the ticket, i.e. travelcard,
rail season, daily or test.
[0100] The magnetic data is stored on a track 8mm wide at a density of 75 bits/inch. This
data is of two types:
(a) fixed data set at time of issue and corresponding to the information printed on
the front of the ticket; and
(b) variable data used to detect fraud. Although the whole code is rewritten by a
gate it is only the variable data that changes. The information covered by the magnetic
data includes the following: Ticket Type, Station of Origin, Fare Value in pence concession
types, e.g. Child, Station of Destination, routing, end of validity and day and time
last processed- Other bits are used to control how often a ticket is used and to prevent
pass back frauds.
[0101] At the gate the ticket is checked to see:
(a) that it is valid at that station at that time; and
(b) that it has not been used to perpetuate an apparent fraud.
[0102] Allowance has to be made for Out of Station Interchanges where a passenger using
an exit barrier may require to re-enter another barrier to interchange between lines.
Computer System Network
[0103] Figure 9 is a block diagram of the computer system network. Reference is made to
both Figures 1 and 9 to illustrate the functions of the station computers (SC), the
computer system network and the station control units (SCUs) and the inter-relationship
therebetween.
Station Computer (SC)
[0104] Each Station Computer (SC) may consist of duplicated processors. Each machine contains
the software necessary to support the SCU fares table loading of devices, and to pass
the transactions and accounts data up to the Central Computers. One machine would
perform all these functions, but should it not operate correctly, its partner machine
would come into use.
[0105] The SC communicates with each device through a multi-drop communications link as
shown in Figure 5.
[0106] Communications with the central computers is via a modem and a 4-wire telephone-type
link.
[0107] The Central Supervisory Computer (CSC) (Figure 9) collects and records on disc and
tape the data transmitted from site and will downline load a halted SC. In a full
system the CSC would be linked to all sites. In addition the CSC can communicate faulty
station and "aliasing" (in which a station assumes the logical identity of another
as well as itself when a nearby station is closed in an emergency, for instance) and
allow gate modes to be set up remotely. Several remote VDU's are used to monitor system
and device status at the operating control centre and engineering report centre. The
data collected at the centre is used to complile;
(a) event logs describing all changes of state of devices at the station;
(b) revenue reports; and
(c) statistical reports as required by various departments.
Station Computer & Station Control Unit
[0108] The Computer system equipment of the overall system at station level supports a number
of distributed, intelligent ticketing devices capable of such operation, these devices
are required to have the ability to communicate on line with the computer centre,
such devices being the ticket office machines (TOMs), fewfare machines (FFMs), and
the multi-fare machines (MFMs).
[0109] The Computer systems are also required to interface to the automatic gates and manual
gates where provided.
[0110] The Computer system equipment for both phases includes Station Control Unit (SCU)
terminals and associated printers for local report and control functions.
[0111] The functions of the computer system equipment at station level are to:
collect data (e.g. status, accounts, transactions) from station devices and pass this
to the computer centre;
collect gate statistics from all gates at the station when requested by the centre
and pass these statistics to the centre;
monitor those elements of this collected data concerned with the status of station
level equipments (attached station devices and computer system elements) and report
locally at station control unit (SCU) terminals;
maintain data tables received from the centre, downloading them to station devices
as required;
forward controls received from the centre or an SCU terminal to station devices as
appropriate;
maintain station accounts by the collection of accounts data and summaries for devices
and by the production of reports on command from an SCU terminal;
manage and control attached SCU terminals and associated printer; and
support secure and efficient data communications to/from station level devices and
to/from the computer centre.
[0112] Each station computer (SC), must be capable of supporting a number of attached station
devices. In addition, the equipment must have the capability for supporting a duplicated
system of SCs and communications links to station devices. Such duplication is optional-
The software required to support duplicated SCs is provided even though no duplicate
systems are configured into the initial network.
[0113] At very large or geographically diverse stations more than one SC (or duplicated
set of SCs) are required to handle the station devices to be supported.
Normal Mode Operation
[0114] Each SCU is required to provide the following commands in normal mode:
- automatic gate emergency open
- emergency open reset
- automatic gate release
- automatic gate closed mode (entry mode gates only)
- automatic gate entry mode
- automatic gate exit mode
- automatic gate array open (array = group of gates)
- automatic gate array closed
- override child alarm (entry mode gates only)
- automatic gate ticket return (outward gates only)
- manual gate open (unlocks gate)
- manual gate close (locks gate when next closed)
- POM closed mode.
Functions
[0115] The SC equipment for station device monitoring and control provides the following
functions:
(a) Data Collection
The SC collects data from ticket issuing and ticket checking station devices on a
regular basis. All data is required to be onward transmitted to the Computer centre
via local buffering at the SC.
This process is also required to cater for failure situations where a station device
has been operating autonomously for some period and thus where data for collection
has been buffered by the device itself.
(b) Status Monitoring and Report
The SC is required to monitor status change information collected from station devices
in order that such changes may be reported locally for SCU display and output to an
associated printer as appropriate.
In addition, the SC is required to monitor the status of the other, locally attached
SC (in the case of duplicated SCs) and the status of communication links between the
station and the centre, the station and a partner station, and the links with devices
at station level. These statuses are reported to the centre but are reported locally
only when requested by a supervisor logged on at an SCU.
(c) Data Table Maintenance and Management
The SC is required to maintain copies of that dynamic data needed to reload a station
device following a device failure and return to service. Copies of both current data
and alternative data applicable following a fares revision or system update) must
be maintained.
The types of dynamic data held are: fares tables, date and time details, and identity
card blacklist information, ticket printing and coding data.
The SC is required to recognise a device request for reload, determine the data set
applicable, and perform the request download whilst continuing to monitor the other
devices.
(d) Station Device Controls
Station devices may receive controls from the centre or from any local station Control
Unit.
The SC is required to validate the command received given current knowledge of the
device status, implement the command if valid, respond to the command initiator appropriately
indicating any reason for failure, and if appropriate, reflect the new device status
at the SCU terminals.
(e) Station Account Maintenance and Report
The SC is required to monitor all accounts data collected from station devices in
order that up to date summary accounts are available for each connected TOM and POM
station device.
TOM Accounts
[0116] Whilst each individual TOM maintains its own accounts for the production of summaries
requested by either clerk or supervisor, the SC is required to have access to that
information of 'Supervisor Interrogate' and 'Supervisor Final' accounts for any specific
TOM, or all TOMs, monitored by this SCU.
End of Day Accounts
[0117] The end of day accounting functions carried out by a supervisor require both the
production of 'Supervisor Final' accounts for all associated TOMs and similar final
accounts for all associated POMs.
(f) SCU Management Control
[0118] Each set of computer system equipment at a station is required to support two types
of SCU VDU terminal. One type is identified as the Ticket Office SCU; the other as
the Ticket Hall SCU. The Ticket Office SCU is required to have two associated hard
copy printers. Dependent upon the identified usage of an SCU, different functions
and display facilities are required. However, it must be possible for either SCU to
provide both sets of functions and facilities as required except for printing functions.
(g) Data Communications
[0119] The SC is required to support secure and efficient, two way data communications between
the station and the computer centre, and within the station, between an SC and station
level devices including SCU terminals. The SC may support both a direct route between
the station and the centre and an alternative route via a partner station.
[0120] The communication links at station level will not be affected by the failure of any
supported device i.e. communication between the SC and other devices in service will
remain available. Similarly, it will be possible to add, remove or replace any device
or SCU terminal without affecting the normal operation of the remainder of the system.
[0121] All data collected from station level devices requires end to end acknowledgement
from a secure data capture point at the Central Computer. However, due to the SC functions
of account summary reporting, status monitoring and report, and so on, the link between
station devices and SC requires a high level of error detection since the SC requires
accurate data upon which to operate.
[0122] An SCU is required to have two modes of operation - normal and supervisor. Station
staff do not need to be logged onto an SCU terminal for normal mode operation. A supervisor
is required to log on by keyboard entry of an identity and an assigned password for
supervisor mode operation.
[0123] The ticket office SCU is required to have two associated hard copy printers: one
for TOM information, and one for POM information. These printers provide mutual backup
capabilities and report on the following: sign on details, power failure recovery,
out of service faults, unauthorised access, TOM supervisor interrogate and final accounts,
and end of day accounts.
[0124] Text message transmitted from the Operations Control Centre are displayed on a nominated
SCU.
[0125] The following station device status indications are available on the SCU terminal
display: gate modes of operation and/or fault codes, gate capture bin 80% full, gate
ticket monitoring and checking level setting, manual gate status, POM modes of operation
(Passenger, Clerk, supervisor, engineer or fault code), POM ticket stock low (50%),
POM exact money only, POM no notes mode (MFM only), POM coin vault greater than 80%
full, POM note vault greater than 80% full (MFM only), POM passenger calling for assistance,
POM unauthorised access, and TOM modes of operation (clerk, supervisor, engineer or
fault code).
[0126] All the above are available at a ticket office SCU terminal whereas only a limited
display is available at a ticket hall SCU terminal. An audible warning is required
with certain of the above status changes.
[0127] The following ticket checking level settings are available for the automatic gates:
normal (cancel selections below), accept all tickets inward, accept all tickets outward,
no geography checks, all other stations faulty, set/accept emergency bit, and reject
child tickets.
[0128] All automatic gates under the control of the SCU are set at the same checking level,
by barrier line groups.
[0129] Ticket type monitoring is required via an indicator on each gate. The setting of
which types of ticket are to be monitored is made from a Ticket Hall SCU only. The
following settings are available: normal (no indication required), child, pass, privilege,
document required, travelcard or season, short distance travelcard or season, and
platform or permit.
Supervisor Mode Operation
[0130] The supervisor is required to sign on at a ticket office SCU terminal using his identity
number and assigned password in order to employ supervisor commands. Whilst signed
on in this mode, all normal mode commands must also be available.
[0131] The ticket office SCU is required to provide the following commands in supervisor
mode: TOM supervisor interrogate and final accounts, end of day accounts, local blacklisting,
station computer system equipment and communications links status enquiry.
Input Data from Devices
[0132] The following data is sent by the TOM, MFM, FFM and automatic gate station level
devices to the computer centre: machine status, plinth identity, machine identity,
type machine, held table revision levels (for current and alternative tables), unauthorised
access details, diagnostic error codes, sign on details, accounts and transaction
data (not automatic gates), statistical data (automatic gates only), staff identity
blacklist details, system messages (TOM only), and alarm messages. The manual gate
device sends status information only.
Output Data to Devices
[0133] The following data is sent by the computer centre to the TOM, MFM, FFM and automatic
gate station level devices: fare tables, date and time details, identity card blacklist
information, and system message delivery acknowledgement (TOM only). In addition,
the computer centre or a local SCU terminal can send controls to the above devices
and also to the manual gate device. Text messages can also be sent by the centre to
the SCU.
Data Concentrators and Safer Storage at Network End
Processors
[0134] The central system collects transaction data from all of the stations, safe-stores
it at the central site and then sends it on to Central Reporting Systems computers
where various data processng and reporting functions are performed. In addition, status
information and user generated messages and data is safe-stored at the central site
and then sent on to either the supervisory facilities or to the stations. In this
context safe-storage of data is defined as having a copy of the data on two separate
disc packs.
End-to-End Acknowledgement
[0135] To ensure data integrity, end-to-end acknowledgement is required for each message.
The message source only discards the message after an acknowledgement has been received
from the destination, signifying that the data has been successfully received and
safe-stored. This means, for example, that station devices will not discard data until
a positive acknowledgement has been received from the central computers. However,
in the case of transactions, data may be discarded if the local storage within a device
becomes full.
Link Failure
[0136] In the event of a link failure between a station and the central computers, the computer
systems will attempt to find an alternative communications path. In some cases this
alternative path will be via an adjacent station, it may be provided as a second direct
link, or there may be no alternative.
Validation
[0137] Referring to Figure 10 there is shown in diagrammatic form an automatic fare collection
system for use on a Railway Underground system which ensures that for any journey
undertaken by a passenger, any ticket purchased by the passenger is validated at both
entry and exit points of the journey. The system is divided into 'closed' stations
and 'open' stations. The closed stations are under the control of a central computer
linked to front-end processors and data concentrators which are in turn an area computer
which is in turn linked to the respective station computer. In each 'closed' station
there is provided the passenger operated machines (POMs) and ticket office machines
(TOMs), the POMs including multi-fare machines and fewfare machines previously referred
to, and these are shown in the diagram for both the 'entry' station and the 'exit'
station and the 'exit' station is provided with automatic passenger gating devices
at entry and exit points and each gating device will have inbuilt ticket validation
facilities.
[0138] For 'open' stations of the system, there is no validation check and any validation
check is carried out by ticket inspectors. The 'open' station equipment is linked
to the station computer and via this to the data concentrators and front end processors
and central computers. Thus, as shown in Figure 5, any passenger entering the system
and leaving via a 'closed' station will be subject to a validation check on the ticket
at both entry and exit points of the system.
[0139] It must be clear at all times whether the passenger is within or outside the 'paid'
area of the station (i.e. the area in which each passenger must hold a correctly validated
ticket.
[0140] The system of the present invention provides ticket issue facilities, accounting
facilities and communications facilities.
(a) Ticket Issue Facilities include:
[0141] Passenger Operated Ticket Machines (POM's) Ticket Office Machines (TOM's)
[0142] Magnetic encoding of all tickets in all machines Ticket printing in all machines
[0143] Automatic distribution to stations of fare tables, commercial rules and operational
changes.
(b) Accounting Facilities include:
[0144] Individual Accountability of booking clerks Station level data gathering
[0145] Central level data gathering/consolidation
(c) Communications Facilities include:
[0146] Station level communications Station to centre communications
[0147] As a result of these facilities, the following objectives can be achieved:
Improved passenger self service ticketing Improved ticket office ticketing facilities
Reductions in fraud
[0148] Establishment of individual accountability for clerks
[0149] Improved security for staff Centralised accounting and statistics Automatic ticket
checking including:
[0150] Abolition of routine manual ticket checking at stations
[0151] Entry/exit automatic gate ticket checking.