A complex public transport ticketing system project involves many devices out in the field, and these devices need to be managed and upgraded constantly. If a device is not functioning, this needs to be dealt with quickly and efficiently. The TapNGo Back Office has a Device Management features that simplifies this task. An intuitive user interface makes device management even easier than before. This web based GUI is easy to learn, and provides granularity at unprecedented detailed levels.
The TapNGo Back Office device management feature controls all of the features of the Ticketing Machines, Validators, Ticket Vending Machines, Ticket Kiosks and other related products. This includes controling their settings and parameters. For example, it is possible to change the amount of time until the Ticket Machine, (driver’s console) screen goes into sleep mode from the TapNGo Back Office. Through device management, it is also possible to control if the Ticket Dispensing Machine (driver’s console) will beep or not if a passenger card is left in the slot for a certain amount of time, and to even decide that specific amount of time. Certain transit company’s policies can be enforced through the device management feature of the TapNGo back office.
Firmware updates and managing access to the ticketing machine devices can all be easily performed from the Device Management Station of the Ticket Management System. The changes are granular to the degree that individual ticketing machines can be managed, defined groups of ticketing machines can receive certain parameters and other groups of ticketing machines can be defined differently. A singular ticketing machine in the field can also be managed, and its parameters defined through the Transway Back Office System. The same concept holds true for controling other devices, such as the Ticket Dispensing Machines, Valdiators, Ticket Kiosks, and Handheld Devices, such as handheld Inspector devices or Conductor Ticket Printer Machines. WiFi and Cellular technologies can be used for these communications and actions.
All of the events that occurred during the last shift are sent from the Ticket Machine, or Driver’s Console, through the External Driver Terminal (EDT) to the server. This includes the time that the line was opened, which line or lines were opened, ticket sales, transit card validations, inspections and even mistakes and other events.
When executing updates to the machines in the field, you are automatically informed of which ticket machines have been updated, and which have not. All ticket machines should receive the updates within a few minutes, but in case of any mishaps, you will know which ticket machines did not get the update.