Fare Device
Functional and Technical
Specification
June 2015
Note:
This is a Specification and subject to change. The information within this Specification is intended for use in
understanding the latest requirements for a Fare Device. Companies wishing to develop and/or operationally
deliver a Fare Device should contact Transport Certification Australia.
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
1
© Transport Certification Australia Limited 2015.
This document has been published by Transport Certification Australia, on behalf of the Taxi Services
Commission (TSC).
This document is copyright. Apart from any use as permitted under the Copyright Act 1968, no part may be
reproduced by any person or process without the prior written permission of Transport Certification Australia
Limited.
Transport Certification Australia
T +61 3 8601 4600
F +61 3 8601 4611
E tca@tca.gov.au
W www.tca.gov.au
ABN 83 113 379 936
P GPO Box 1716 Melbourne VIC 3001
Taxi Services Commission
T 1800 638 802
T +61 3 8683 0768 (international callers)
E contact@taxi.vic.gov.au
W www.taxi.vic.gov.au
Document Details
Title
Fare Device Functional and Technical Specification
Document Number
TSA-S05-1.00
Version
2.0
Version Date July 2015
Printing Instructions
Colour A4
Document History
Version
Date
1.0
June 2014
2.0
July 2015
Description
Draft for Consultation
Final
Transport Certification Australia Limited believes this publication to be correct at time of printing and does not
accept responsibility for any consequences arising from the use of information herein. Readers should rely
on their own skills and judgment to apply information to particular issues.
TCA™, Transport Certification Australia™, TCA National Telematics Framework™, TCA Certified™, TCA
Type-Approved™, Intelligent Access Program™, IAP®, IAP Service Provider™, IAP-SP™, In-Vehicle Unit™,
IVU™, Electronic Work Diary™, EWD™, On-Board Mass™ and OBM™ are trade marks of Transport
Certification Australia Limited.
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
2
1
2
3
INTRODUCTION ........................................................................................................................... 5
1.1
Scope ............................................................................................................................... 5
1.2
Specification Overview .................................................................................................... 6
OVERVIEW.................................................................................................................................... 8
2.1
Fare Device Overview ..................................................................................................... 8
2.2
Core Components of the Fare Device ............................................................................. 8
2.3
Fare Device Data Inputs .................................................................................................. 9
2.4
Core Functionality of the Fare Device ........................................................................... 10
2.5
Operational States of the Fare Device .......................................................................... 10
2.6
Nomenclature used in this Specification ....................................................................... 11
2.7
References .................................................................................................................... 11
REQUIREMENTS FOR FARE DEVICE TYPE-APPROVAL ...................................................... 12
FARE DEVICE TYPE-APPROVAL ............................................................................................ 12
A.1
Fare Device Type-Approval ........................................................................................... 12
A.2
Supporting Documentation ............................................................................................ 12
PHYSICAL CHARACTERISTICS .............................................................................................. 12
A.3
Fare Device ................................................................................................................... 12
A.4
Vehicle Connection ........................................................................................................ 13
A.5
External Power Supply Connection ............................................................................... 13
A.6
Fare Device Identifier (Fare Device ID) ......................................................................... 13
A.7
Security Seals ................................................................................................................ 13
ENVIRONMENTAL CHARACTERISTICS ................................................................................. 14
A.8
Suitability for Use in Vehicles ........................................................................................ 14
A.9
Fare Device GPS Capability .......................................................................................... 14
A.10
Other Functionality ........................................................................................................ 15
DATA COLLECTION ................................................................................................................. 15
A.11
Data Types .................................................................................................................... 15
A.12
Vehicle Identifier (Vehicle ID) Data ............................................................................... 16
A.13
Fare Device Identifier (Fare Device ID) Data ................................................................ 16
A.14
Speed and Distance Data .............................................................................................. 17
A.15
RTC Date and Time Data .............................................................................................. 18
A.16
GPS Quality Data .......................................................................................................... 18
A.17
GPS Position Data ......................................................................................................... 19
A.18
GPS Speed Data ........................................................................................................... 19
A.19
GPS Date and Time Data .............................................................................................. 19
A.20
Driver Current List Data ................................................................................................. 20
A.21
MPTP Member Current List Data .................................................................................. 20
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
3
A.22
Disable List Data ........................................................................................................... 20
A.23
Driver Identification and Authentication Data ................................................................ 20
A.24
MPTP Member Identification and Authentication Data ................................................. 21
A.25
Manual Selection and Input Data .................................................................................. 21
A.26
Fare Structure Data ....................................................................................................... 22
A.27
Tolling Data.................................................................................................................... 23
A.28
Booking Acceptance Data ............................................................................................. 23
A.29
Last Fare Data ............................................................................................................... 24
A.30
Driver Shift Data ............................................................................................................ 24
A.31
Vehicle Trip Data ........................................................................................................... 24
A.32
Alarm Status Data ......................................................................................................... 25
A.33
Functionality Status Data ............................................................................................... 25
A.34
Calibration Data ............................................................................................................. 26
FUNCTIONALITY ...................................................................................................................... 26
A.35
Driver Log On ................................................................................................................ 26
A.36
Driver Log Off ................................................................................................................ 27
A.37
Hire On .......................................................................................................................... 28
A.38
Hire Pause ..................................................................................................................... 29
A.39
Hire Off .......................................................................................................................... 30
A.40
MPTP Member Identification and Authentication .......................................................... 30
A.41
Provide Trip Receipt ...................................................................................................... 30
A.42
Repeat Audio Announcement........................................................................................ 31
A.43
Recall Last Fare ............................................................................................................ 31
A.44
Manual Selection and Input Lock .................................................................................. 32
A.45
Audio Output .................................................................................................................. 32
A.46
Display Functionality Status Data .................................................................................. 32
A.47
Display Calibration Data ................................................................................................ 32
DATA PROCESSING ................................................................................................................ 32
A.48
Driver Identification and Authentication Processing ...................................................... 32
A.49
MPTP Member Identification and Authentication Processing ....................................... 33
A.50
Fare Processing ............................................................................................................ 34
RECORD GENERATION .......................................................................................................... 36
A.51
Driver Shift Start Message (DSSM) Record .................................................................. 36
A.52
Driver Shift Message (DSM) Record ............................................................................. 36
A.53
Vehicle Trip Message (VTM) Record ............................................................................ 37
A.54
Vehicle Alarm Message (VAM) Record ......................................................................... 38
A.55
Vehicle Location Message (VLM) Record ..................................................................... 39
A.56
Record Numbering ........................................................................................................ 40
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
4
DATA STORAGE ....................................................................................................................... 40
A.57
Fare Device Data Record Storage Capability ............................................................... 40
A.58
Fare Device External Power Supply Failure/Shut Down ............................................... 40
DATA SECURITY ...................................................................................................................... 40
A.59
Data Security and Confidentiality Measures ................................................................. 40
A.60
Fare Device Communications Capability ...................................................................... 41
DATA TRANSFER ..................................................................................................................... 41
A.61
Transfer of Data from Fare Device to Authority............................................................. 41
PROVISION OF FARE DEVICE AUDIT INFORMATION.......................................................... 41
A.62
Fare Device Audit .......................................................................................................... 41
APPENDIX A – DEFINITION OF TERMS ........................................................................................... 1
APPENDIX B – ROLES AND RESPONSIBILITIES ........................................................................... 4
APPENDIX C – OPERATIONAL STATES OF THE FARE DEVICE .................................................. 5
APPENDIX D – REQUIREMENTS FOR THE PROVISION OF FARE DEVICES .............................. 6
APPENDIX E – DATA FORMATS FOR FARE DEVICE DATA RECORDS ...................................... 7
APPENDIX F – HIRING RATES TABLE ............................................................................................. 1
APPENDIX G – FIXED FEE AND EXTRAS TABLE ........................................................................... 1
APPENDIX H – ALARM CODES ........................................................................................................ 1
APPENDIX I – AUDIO ANNOUNCEMENTS....................................................................................... 1
APPENDIX J – ERROR MESSAGES FOR MPTP MEMBER SMARTCARD PROCESSING ........... 1
APPENDIX K – SMARTCARD SPECIFICATIONS ............................................................................ 2
1 INTRODUCTION
1.1 Scope
1.1.1
This Specification describes the functional and technical requirements for a Fare Device.
1.1.2
In addition to calculating fares, a Fare Device shall perform a range of functions when used in
a Vehicle, including:
a) Visually displaying and audibly conveying information inside the Vehicle;
b) Identifying and authenticating Drivers and Multi Purpose Taxi Program (MPTP) Members;
c) Supporting multiple Fare Structures;
d) Processing MPTP Member transactions;
e) Providing Trip Receipts; and
f)
Generating and transferring Data Records.
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
5
1.1.3
Within this Specification, there are roles and responsibilities assigned to the following
parties:

Authority – the Taxi Services Commission (TSC) of Victoria;

Administrator – Transport Certification Australia (TCA), which performs functions on behalf of the
Authority;

Fare Device Service Provider (FDSP) – the entity responsible for Fare Device installation, operation,
maintenance and calibration; and

Operator – the entity responsible for the Vehicle and the operation of the Fare Device.
1.2 Specification Overview
1.2.1
The philosophy guiding the creation of this Specification has been that it focuses on required
outcomes, without being overly prescriptive or solution oriented.
1.2.2
Applicants for Type-approval are encouraged to develop innovative ways of meeting the
functional and technical requirements of this Specification, and to submit them for
consideration.
1.2.3
The Applicant shall submit for Type-approval a Fare Device that satisfies the requirements of
this Specification, including:
a) Physical characteristics;
b) Environmental characteristics;
c) Data collection;
d) Functionality;
e) Data processing;
f)
Record generation;
g) Data storage;
h) Data security;
i)
Data transfer; and
j)
Provision of Fare Device audit information.
1.2.4
The Specification begins with this Introduction, followed by:
Section 2 – which provides an overview of the Fare Device; and
Section 3 – which details the requirements for Fare Device Type-approval.
1.2.5
This Specification includes the following Appendices:
Appendix A:
Definition of Terms;
Appendix B:
Roles and Responsibilities;
Appendix C:
Operational States of the Fare Device;
Appendix D:
Requirements for the Provision of Fare Devices;
Appendix E:
Data Formats for Fare Device Data Records;
Appendix F:
Hiring Rates Table;
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
6
Appendix G:
Fixed Fee and Extras Table;
Appendix H:
Alarm Codes;
Appendix I:
Audio Announcements;
Appendix J:
Error messages for MPTP Member Smartcard processing; and
Appendix K:
Smartcard specifications.
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
7
2 OVERVIEW
2.1 Fare Device Overview
2.1.1
This section provides an overview of:
a. The core components of the Fare Device;
b. Fare Device data inputs;
c. Core functionality of the Fare Device;
d. Operation states of the Fare Device; and
e. Nomenclature used in this Specification.
2.2 Core Components of the Fare Device
2.2.1
The Fare Device shall comprise the following components:
a. A Global Positioning System (GPS) receiver and GPS Antenna;
b. Mobile data communications transceiver and antenna (e.g. cellular radio);
c. Smartcard reader (if internal to the Fare Device);
d. Visual display;
e. Manual selection and input interface;
f.
Internal Power Supply;
g. Real Time Clock;
h. Non-volatile memory;
2.2.2
i.
Audio speaker (if internal to the Fare Device); and
j.
Printer (if internal to the Fare Device).
The Fare Device shall connect to the following external components:
a. External Power Supply;
b. Speed and Distance Sensor;
c. Smartcard reader (if external to the Fare Device);
d. Audio speaker (if external to the Fare Device);
e. Printer (if external to the Fare Device); and
f.
Booking System (if applicable).
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
8
2.2.3
Where components in the Vehicle are used, they shall meet the performance requirements of
this Specification. For example, in the case of the audio output being provided by the
Vehicle’s audio system: “The ability of the Fare Device to audibly convey information shall
not be able to be disabled, or have its function reduced in any way” (refer A.45.2).
2.2.4
Other devices approved by the Authority may be connected to the Fare Device. If connected,
they shall not interfere with the normal operation of the Fare Device as defined in this
Specification (refer A.10).
2.2.5
The method and location of the installation of all components shall be secure and tamper
evident. A failure of a monitored component shall generate the appropriate alarm,
irrespective of whether the Fare Device is operating from the External Power Supply, or
Internal Power Supply.
2.3 Fare Device Data Inputs
2.3.1
The Fare Device shall obtain data inputs from the following sources:
(1) Data
from the
FDSP
Vehicle ID
(2) Data
from the
GPS
(3) Data
from the
Vehicle
(4) Data
from the
Authority
(5) Data from
Smartcards
(6) Data
from other
sources
(7) Data
generated
by the Fare
Device
GPS quality
data
Speed and
distance (if
obtained
from the
Vehicle)
Driver
Current List
data
Driver
identification
and
authentication
data
Tolling data
(if obtained
from an
external
source)
RTC date
and time
data (from
the Real
Time Clock
internal to
the Fare
Device)
MPTP
Member
identification
and
authentication
data
Booking
acceptance
data (if
obtained
from a
Booking
System)
Manual
selection
and input
data
Fare Device
ID
GPS
position data
MPTP
Member
Current List
data
Calibration
data
GPS speed
data
Disable List
data
Fare
Structure
data
GPS date
and time
data
Functionality
status data
Last fare
data
Audio
announcement
updates
Driver shift
data
Software
updates
Vehicle trip
data
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
9
Firmware
updates
Alarm status
data
2.4 Core Functionality of the Fare Device
2.4.1
The Fare Device shall calculate fares.
2.4.2
The Fare Device shall visually display and audibly convey information inside the Vehicle.
2.4.3
The Fare Device shall identify and authenticate Drivers and MPTP Members.
2.4.4
The Fare Device shall process MPTP Member transactions.
2.4.5
The Fare Device shall be able to provide a Trip Receipt.
2.4.6
The Fare Device shall generate Data Records:
i.
Driver Shift Start Message (DSSM) Record;
ii.
Driver Shift Message (DSM) Record;
iii.
Vehicle Trip Message (VTM) Record;
iv.
Vehicle Alarm Message (VAM) Record; and
v.
Vehicle Location Message (VLM) Record.
2.4.7
The Fare Device shall be able to disable Driver and MPTP Member Smartcards.
2.4.8
The Fare Device shall receive remote updates to Fare Structures from the FDSP periodically.
The updates shall not interfere with the normal operation of the Fare Device.
2.5 Operational States of the Fare Device
2.5.1
The ability to perform functions defined in this Specification shall depend on the operational
state of the Fare Device.
2.5.2
The operational state of the Fare Device is determined by:
a. Whether power is derived from the Internal or External Power Supply;
b. Whether a Driver is logged on or off;
c. Whether the Vehicle is moving; and
d. Whether the Fare Device is hired on, hire paused or hired off.
Details of the operational states of the Fare Device are defined in Appendix C.
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
10
2.6 Nomenclature used in this Specification
2.6.1
In this Specification:
a. All references to Global Positioning System (GPS) include all TCA-approved Global
Navigation Satellite Systems (GNSS);
b. All references to software include software in any form or medium, including firmware,
unless otherwise qualified; and
c. Where the context so requires it, references to the ‘FDSP’ shall, before the FDSP has
obtained Type-approval of a Fare Device, be a referred to as an Applicant for
Type-approval.
2.6.2
Requirements clauses within this Specification that are denoted by:
a. ‘shall’ are requirements that must be met;
b. ‘should’ are requirements that should desirably be met; and
c. ‘will’ are obligations that will be met by other parties.
2.6.3
Notes are included by way of clarification and apply to the preceding requirement.
2.7 References
2.7.1
Documents which relate to this Specification are listed below:
a. Commission Directive 2004/104/EC of 14 October 2004 adapting to technical
progress Council Directive 72/245/EEC relating to the radio interference
(electromagnetic compatibility) of vehicles and amending Directive 70/156/EEC on
the approximation of the laws of the Member States relating to the Type-approval of
motor vehicles and their trailers;
b. Degrees of protection provided by enclosures (IP code), AS 60529-2004, Standards
Australia;
c. Information technology equipment – Radio disturbance characteristics – Limits and
methods of measurement, AS/NZS CISPR22:2004, Standards Australia;
d. Radiocommunications (Communication with Space Object) Class Licence 1998,
Australian Communications Authority;
e. Security seals – Classification, AS/NZS 4255.1:1994, Standards Australia; and
f.
Vehicle immobilizers, AS/NZS 4601:1999, Standards Australia.
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
11
3 REQUIREMENTS FOR FARE DEVICE TYPE-APPROVAL
FARE DEVICE TYPE-APPROVAL
A.1
Fare Device Type-Approval
A.1.1
To facilitate Type-approval, the Applicant shall provide two Fare Devices to the
Administrator.
A.1.2
The Applicant shall adhere to the requirements detailed by the Administrator in supplying
Fare Devices.
A.1.3
Subsequent to Type-approval, the FDSP shall not, without prior written approval of the
Administrator by way of re-Type-approval make any changes to its Fare Device(s).
A.2
A.2.1
Supporting Documentation
The FDSP shall document, to the satisfaction of the Administrator, the Fare Device and
its cabling and interfaces.
PHYSICAL CHARACTERISTICS
A.3
A.3.1
Fare Device
The Fare Device shall include:
a. A Global Positioning System (GPS) receiver and GPS Antenna;
b. Mobile data communications transceiver and antenna (e.g. cellular radio);
c. Visual display;
d. Manual selection and input interface;
e. Internal Power Supply;
f.
Real Time Clock;
g. Non-volatile memory;
h. Smartcard reader (if internal to the Fare Device);
A.3.2
i.
Audio speaker (if internal to the Fare Device); and
j.
Printer (if internal to the Fare Device).
The Fare Device shall include compatible cabling, plugs and sockets enabling connection
to the following external components:
a. External Power Supply;
b. Speed and Distance Sensor;
c. Smartcard reader (if external to the Fare Device); and
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
12
d. Audio speaker (if external to the Fare Device).
A.3.3
The Fare Device shall not include cabling, plugs and sockets enabling connection to the
following external components:
a. Printer (if external to the Fare Device); and
b. Booking System (if applicable).
A.4
Vehicle Connection
A.4.1
The Fare Device shall be associated with a Vehicle.
A.4.2
The Vehicle Identifier (Vehicle ID) shall be accessible to the Fare Device.
A.4.3
The operation of a Fare Device, as defined by this Specification, requires an association
to a Vehicle.
Note: The definition of a Vehicle is contained in Appendix A.
A.5
External Power Supply Connection
A.5.1
Vehicle Alarm Message (VAM) Record data collection, record generation and record
transmission shall be performed independent to the connection status of the External
Power Supply.
A.5.2
Noting A.4.3 and A.5.1, the operation of a Fare Device, as defined by this Specification,
requires a connection to the External Power Supply.
Note: It is recognised that the Fare Device may be one of many connections to the
External Power Supply which consume power. The design and subsequent
installation of the Fare Device in the Vehicle will need to be cognisant of this.
A.5.3
Noting A.5.2 the External Power Supply shall be charged through the normal operation of
the Vehicle.
A.5.4
All Fare Device functionality, other than that outlined in A.5.1, contained in this
Specification shall be disabled if the External Power Supply fails or is disconnected from
the Vehicle.
A.5.5
If the connection to the power supply of the Vehicle fails or is disconnected during
operation, the Fare Device shall retain all data for fourteen (14) days.
A.6
A.6.1
Fare Device Identifier (Fare Device ID)
A unique identifier (Fare Device ID) shall be assigned to each Fare Device. It identifies:
a. The Fare Device; and
b. Data from that Fare Device.
A.6.2
The Administrator shall provide each FDSP with a unique, three-character identifier that
shall be used as a prefix to the Fare Device ID.
A.6.3
The Fare Device ID shall be visible and in a manner that cannot be modified or removed.
A.6.4
The Fare Device ID shall be visible when installed in the Vehicle.
A.7
Security Seals
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
13
A.7.1
The Fare Device shall be protected by security seal(s) to ensure detection of any
unauthorised removal or opening of the Fare Device, and in accordance with AS/NZS
4255.1:1994 Security Category 10, Grade A.
A.7.2
Opening of the Fare Device shall be possible only by breaking the security seal(s) and
the security seal(s) shall be such that if broken, they cannot be reinstated.
A.7.3
The security seal(s) shall be placed in a position that facilitates inspection.
A.7.4
The security seal(s) shall clearly display signs of any unauthorised access visually and/or
physically.
ENVIRONMENTAL CHARACTERISTICS
A.8
A.8.1
Suitability for Use in Vehicles
The FDSP shall provide to the Administrator, evidence of compliance with the following,
or equivalent(s) as approved by the Administrator:
a. The Fare Device complies with all performance requirements in this Specification
when subjected to the vibration tests specified in AS/NZS 4601:1999 Type 1
paragraph 3.3.4;
b. The Fare Device complies with all performance requirements in this Specification
when subjected to the impact tests specified in AS/NZS 4601:1999 paragraph 3.3.5;
c. The Fare Device complies with all of the performance requirements in this
Specification when subjected to the temperature and humidity tests specified in
AS/NZS 4601:1999 paragraphs 2.2.5.2 and 3.3.2;
d. The Fare Device complies with the electromagnetic compatibility conditions specified
in AS/NZS 4601:1999 paragraph 3.3.7 Clauses (a) to (c);
e. The Fare Device components are tolerant to radio frequency and electrical
interference as defined in 2004/104/EC, sections 6.7 and 6.8 with functional status
‘A’, Table 1;
f.
Electromagnetic emissions from the Fare Device shall not exceed the limits in
2004/104/EC, sections 6.9 using the pulse amplitude levels for either 12 or 24 volt
systems as appropriate, Table 2; and
g. Electromagnetic emissions from the Fare Device shall not exceed the limits in
AS/NZS CISPR22:2006 (CISPR 22:2003), Class B, Table 6.
A.8.2
The Fare Device shall be resistant to water and dust ingress commensurate with the
installation position of the device within the Vehicle.
A.8.3
Security seals shall remain intact when exposed to vibration and impact tests (refer
A.8.1).
A.9
A.9.1
Fare Device GPS Capability
The Fare Device GPS Receiver and GPS Antenna shall comply with the
Radiocommunications (Communication with Space Object) Class Licence 1998 Australian Communications Authority (the Class Licence).
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
14
A.9.2
The Fare Device GPS Antenna shall be mounted in a position that meets the
manufacturer’s specification, and such that it optimises signal strength from the GPS
satellites.
A.9.3
Other forms of Global Navigation Satellite System (GNSS) may be proposed and
adopted, subject to the approval of the Administrator.
A.10 Other Functionality
A.10.1 It shall be permissible for additional functionality to be accommodated within the Fare
Device, subject to Type-approval.
Note: Type-approval shall not be provided if the additional functionality could degrade
the integrity of the Fare Device.
A.10.2 The FDSP shall document, to the satisfaction of the Administrator, any additional
functionality to be provided by the Fare Device.
A.10.3 The functionality defined in this Specification shall be isolated from any additional
functionality such that Fare Device performance is not hindered or degraded below the
requirements of this Specification.
A.10.4 The FDSP shall document, to the satisfaction of the Administrator, the design features of
the Fare Device which isolate and protect Fare Device functionality from any additional
functionality.
DATA COLLECTION
A.11 Data Types
A.11.1 The Fare Device shall collect and store the following data:
a. Vehicle ID data;
b. Fare Device ID data;
c. Speed and distance data;
d. RTC Date and time data;
e. GPS quality data;
f.
GPS position data;
g. GPS speed data;
h. GPS date and time data;
i.
Driver Current List data;
j.
MPTP Member Current List data;
k. Disable List data;
l.
Driver identification and authentication data;
m. MPTP Member identification and authentication data;
n. Manual selection and input data;
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
15
o. Fare Structure data;
p. Tolling data;
q. Booking acceptance data (if applicable);
r.
Last fare data;
s. Driver shift data;
t.
Vehicle trip data;
u. Alarm status data;
v. Functionality status data; and
w. Calibration data.
A.11.2 The Fare Device shall process data to generate the following Fare Device Data Records
for transmission to the Authority:
a. Driver Shift Start Message (DSSM) Records (A.51);
b. Driver Shift Message (DSM) Records (refer A.52);
c. Vehicle Trip Message (VTM) Records (refer A.53);
d. Vehicle Alarm Message (VAM) Records (refer A.54); and
e. Vehicle Location Message (VLM) Records (refer A.55).
A.12 Vehicle Identifier (Vehicle ID) Data
A.12.1 The Fare Device shall collect and store Vehicle ID.
A.12.2 Vehicle ID shall be stored in non-volatile programmable read-only memory of the Fare
Device.
A.12.3 The Vehicle ID shall not be able to be set or altered by any person other than the FDSP,
or otherwise tampered with.
A.12.4 The Fare Device shall not enable Functionality, Data Processing and Record Generation
until the Vehicle ID is input.
A.12.5 The Fare Device shall include Vehicle ID data in:
a. Fare Processing; and
b. The generation of all Fare Device Data Records (refer A.51 - A.55).
A.13 Fare Device Identifier (Fare Device ID) Data
A.13.1 The Fare Device shall collect and store Fare Device ID.
A.13.2 Fare Device ID shall be stored in non-volatile programmable read-only memory of the
Fare Device.
A.13.3 The Fare Device ID shall not be able to be set or altered by any person other than the
FDSP, or otherwise tampered with.
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
16
A.13.4 The Fare Device shall not enable Functionality, Data Processing and Record Generation
until Fare Device ID is input.
A.13.5 The Fare Device shall include Fare Device ID in:
a. Fare Processing; and
b. The generation of all Fare Device Data Records (refer A.51 - A.55).
A.14 Speed and Distance Data
A.14.1 The Fare Device shall collect and store speed and distance data.
A.14.2 The Fare Device shall obtain speed and distance data from the Speed and Distance
Sensor, which shall incorporate:
a. A device that converts the angular speed of a rotating driveline component (via a
fixed mechanical connection to the Vehicle’s road wheel(s), either directly or through
a fixed-ratio gearset); or
b. An independent system retrofitted to the driveline and configured as described in
A.14.2a; or
c. The Vehicle’s engine-management system (if it can be demonstrated that the output
obtained from the sensor uses the method described in A.14.2a.); or
d. A signal derived from the Vehicle’s speedometer/odometer; or
e. A signal derived from an interface to the Vehicle’s CAN bus, or equivalent, if fitted; or
f.
A signal derived from any other method that can reliably demonstrate the direct
correlation to the Vehicle’s speed and distance travelled.
A.14.3 The Fare Device shall convert the output from the Speed and Distance Sensor into
kilometres per hour (km/h) and distance travelled in kilometres (km).
A.14.4 The resolution of Speed Data recorded by the Fare Device shall be to 0.1 km/h.
A.14.5 The Speed and Distance Sensor shall allow the Fare Device to calculate the speed of the
Vehicle within 5 km/h of the Vehicle’s actual speed for 95% of observations.
A.14.6 The Fare Device shall collect and store speed and distance data when a Driver is logged
on.
A.14.7 The Fare Device shall include speed and distance data in:
a. Fare Processing (refer A.50);
b. The generation of Driver Shift Message (DSM) Records (refer A.52); and
c. The generation of Vehicle Trip Message (VTM) Records (refer A.53).
A.14.8 The Fare Device shall use speed and distance data to trigger the generation of Vehicle
Location Message (VLM) Records (refer A.55).
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
17
A.15 RTC Date and Time Data
A.15.1 The Fare Device shall collect and store RTC date and time data.
A.15.2 RTC date and time data shall be obtained from the Real Time Clock in UTC.
A.15.3 The RTC date and time shall be stored with a resolution of 1 second.
A.15.4 The accuracy of the Real Time Clock shall not deviate by more than one (1) second from
the GPS date and time while connected to the External Power Supply.
A.15.5 The Real Time Clock shall be powered by the Internal Power Supply when the External
Power Supply is disconnected.
A.15.6 The Real Time Clock shall continue to operate for at least fourteen (14) days after the
Fare Device has been disconnected from the External Power Supply (refer A.58).
A.15.7 The accuracy of the Real Time Clock shall not deviate by more than 10 seconds per day
from the UTC date and time after the Fare Device has been disconnected from the
External Power Supply.
A.15.8 The Fare Device shall only make corrections to the Real Time Clock when hired off.
A.15.9 The Fare Device shall include RTC date and time data in:
a. Fare Processing; and
b. The generation of all Fare Device Data Records except Vehicle Location Message
(VLM) Records (refer A.51 - A.54).
A.16 GPS Quality Data
A.16.1 The Fare Device shall collect and store GPS quality data.
A.16.2 GPS quality data shall be obtained from the GPS Receiver by measuring the number of
satellites acquired and the Horizontal Dilution of Precision (HDOP).
A.16.3 The Administrator shall compare the Fare Device’s GPS quality with a Reference System
during Type-approval testing.
A.16.4 The Fare Device GPS Receiver shall demonstrate signal quality to the level exhibited by
the Reference System, Specifically:
a. The HDOP shall deviate by no more than ‘plus 0.1’ (+0.1) or better from that of the
Reference System for at least 95% of the observations when acquiring:
i.
At least four satellites; and
ii.
The same number of satellites as the Reference System.
b. The number of satellites acquired by the Fare Device GPS Receiver shall be ‘minus
one’ (-1) or better than the total number acquired by the Reference System for 95% of
observations, at a mask angle of 15 degrees.
A.16.5 The HDOP from the Fare Device GPS Receiver shall be measured and stored to a
resolution of 0.1 or better.
A.16.6 The Fare Device shall include GPS quality data in the generation of all Fare Device Data
Records (refer A.51 - A.55).
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
18
A.17 GPS Position Data
A.17.1 The Fare Device shall collect and store GPS position data.
A.17.2 GPS position data shall be obtained from the GPS Receiver by calculating the
latitude/longitude position in WGS84 or GDA94 coordinates.
A.17.3 The latitude/longitude position calculated by the Fare Device GPS Receiver shall not
deviate by more than 13 metres from the absolute horizontal position Australia wide
average for 95% of the observations when using at least four satellites and a HDOP of
less than four (<4).
A.17.4 The resolution of the stored latitude/longitude position calculated by the Fare Device
GPS Receiver shall be to 0.00001 degrees, or better.
A.17.5 In the event of interruption to and subsequent re-acquisition of GPS satellite signals, the
Fare Device GPS Receiver shall, on re-acquisition of GPS satellite signals, commence to
collect and store GPS position data:
a. If the interruption has been for a period of less than seven (7) days:
within 60 seconds of re-acquiring GPS satellite signals; and
b. If the interruption has been for a period of seven (7) days or more:
within five minutes of re-acquiring GPS satellite signals.
A.17.6 The Fare Device shall include GPS position data in the generation of all Fare Device
Data Records (refer A.51 - A.55).
A.18 GPS Speed Data
A.18.1 The Fare Device shall collect and store GPS speed data.
A.18.2 GPS speed data shall be obtained from the GPS Receiver by measuring GPS speed
using a GPS Doppler-derived method.
A.18.3 The GPS reported speed between 60 km/h and 250 km/h shall be accurate to within 3.0
km/h for 99.9% of observations when using at least four satellites and a HDOP of less
than four (< 4).
A.18.4 The GPS speed data shall be recorded with a resolution of 0.1 km/h.
Note: GPS speed data captured in units other than km/h shall be converted to km/h.
A.18.5 The Fare Device shall include GPS speed data in the generation Vehicle Location
Message (VLM) Records (refer A.55).
A.19 GPS Date and Time Data
A.19.1 The Fare Device shall collect and store GPS date and time data.
A.19.2 GPS date and time data shall be obtained from the GPS Receiver in UTC with a
resolution of one (1) second.
A.19.3 The Fare Device shall include GPS date and time data in the generation of Vehicle
Location Message (VLM) Records (refer A.55).
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
19
A.20 Driver Current List Data
A.20.1 The Fare Device shall collect and store Driver Current List data.
A.20.2 The Driver Current List shall be obtained from the Authority.
A.20.3 The Driver Current List will contain:
a. A current list of Driver Numbers; and
b. A current list of Driver Licence Numbers.
A.20.4 The Fare Device shall utilise Driver Current List data for Driver identification and
authentication processing.
A.21 MPTP Member Current List Data
A.21.1 The Fare Device shall collect and store MPTP Member Current List data.
A.21.2 The MPTP Member Current List shall be obtained from the Authority.
A.21.3 The MPTP Member Current List will contain a current list of MPTP Member Card
Numbers.
A.21.4 The Fare Device shall utilise MPTP Member Current List data for MPTP Member
identification and authentication processing.
A.22 Disable List Data
A.22.1 The Fare Device shall collect and store Disable List data.
A.22.2 The Disable List shall be obtained from the Authority.
A.22.3 The Disable List will contain:
a. Driver and MPTP Member Card Numbers to be disabled; and
b. Security keys to disable Driver and MPTP Member Smartcards.
A.22.4 The Fare Device shall utilise Disable List data for Driver and MPTP Member identification
and authentication processing.
A.23 Driver Identification and Authentication Data
A.23.1 The Fare Device shall collect and store Driver identification and authentication data.
A.23.2 The Fare Device shall interact with a Driver Smartcard (refer Appendix K), which is
inserted into the Smartcard reader.
A.23.3 The Fare Device shall support the Driver Smartcard which is the Motorola SC41
Microprocessor Card.
A.23.4 The Fare Device shall collect and store from a Driver Smartcard:
a. Driver Number;
b. Valid From Date and Expiry Date; and
c. Personal Identification Number (PIN).
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
20
A.23.5 The Fare Device shall allow for the manual input of a Driver Number and Driver Licence
Number.
Note: Manual input of the 18-digit Driver Number and Driver Licence Number manually is
intended to be used only when a Driver Smartcard is not available.
A.23.6 The Fare Device shall collect and store the method of Log On (i.e. Driver Smartcard or
manual input of Driver Number).
A.23.7 The Fare Device shall include Driver identification and authentication data in:
a. Fare Processing; and
b. The generation of all Fare Device Data Records (refer A.51 - A.55).
A.24 MPTP Member Identification and Authentication Data
A.24.1 The Fare Device shall collect and store MPTP Member identification and authentication
data.
A.24.2 The Fare Device shall interact with a MPTP Member Smartcard (refer Appendix K),
which is inserted into the Smartcard reader.
A.24.3 The Fare Device shall support the MPTP Member Smartcard which is the Motorola SC45
Microprocessor Card.
A.24.4 The Fare Device shall collect and store from a MPTP Member Smartcard:
a. MPTP Card Number; and
b. Valid From Date and Expiry Date.
A.24.5 The Fare Device shall include MPTP Member identification and authentication data for:
a. Fare Processing; and
b. The generation of Vehicle Trip Message (VTM) Records (refer A.53).
A.25 Manual Selection and Input Data
A.25.1 The Fare Device shall collect and store manual selection and input data.
A.25.2 The Fare Device shall be able to collect and store manual selection and inputs:
a. Driver Log On (refer A.35);
b. Driver Log Off (refer A.36);
c. Hire On (refer A.36.6);
i. Fare Structure (Hiring Rate or Fixed Fee) (refer A.26); and
ii. Form of Vehicle Engagement (refer A.36.6).
d. Hire Pause (refer A.38);
e. Hire Off (refer A.38.4);
f.
Add or remove Extras (refer A.50.7);
g. MPTP Member processing (refer A.40);
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
21
h. Repeat audio announcement (refer A.42);
i.
Provide Trip Receipt (refer A.41);
j.
Recall last fare (refer A.43);
k. Manual selection and input lock (refer A.44);
l.
Display functionality status (refer A.46); and
m. Display calibration data (refer A.47).
A.25.3 The Fare Device shall include manual selection and input data in:
a. Fare Processing; and
b. The generation of Driver Shift Start Message Records (DSSM), Driver Shift Message
(DSM) Records and Vehicle Trip Message (VTM) Records (refer A.51, A.52 and
A.53).
A.26 Fare Structure Data
A.26.1 The Fare Device shall collect and store Fare Structure data.
A.26.2 Fare Structure data shall be obtained from the FDSP.
A.26.3 The Fare Device shall support at least 128 different Fare Structures.
A.26.4 The Hiring Rate is defined by Hiring Rate Codes and elements contained in the Hiring
Rates Table (refer Appendix F).
A.26.5 Fixed Fees and Extras are defined by codes and elements within the Fixed Fee and
Extras Table (refer Appendix G).
A.26.6 A Fare Structure may consist of Hiring Rates, Fixed Fees and Extras.
Note: Each Fare Structure may consist of a combination of Hiring Rate Codes, Fixed Fee
Codes and Extra Codes, as demonstrated by way of example below:
Fare Structure 1 = set of {M1, M2, MX1, MX2, MX3, MX4, MX5, MX6, MX7, MX8, MX9}
Fare Structure 2 = set of {M3, MX1, MX2, MX3, MX4, MX5, MX6, MX7, MX8, MX9}
Fare Structure 3 = set of {M4, MX10, MX11}.
A.26.7 A Fare Structure may be based on any combination of the following:
a. Time of day when Hire On is selected;
b. Day of week when Hire On is selected;
c. Date when Hire On is selected;
d. Time elapsed between the selection of Hire On and Hire Off;
e. Distance travelled between the selection of Hire On and Hire Off;
f.
Start position when Hire On is selected;
g. End position when Hire Off is selected;
h. Route taken by the Vehicle;
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
22
i.
Zone of Vehicle operation; and
j.
Extras recorded between the selection of Hire On and Hire Off.
A.26.8 A Fare Structure shall define those elements that are to be:
a. Automatically applied;
b. Manually applied;
c. Applied at a certain time;
d. Applied at a certain location; and/or
e. Not applied in combination with other elements.
A.26.9 The Fare Device shall receive and apply updated Fare Structures automatically (as
transmitted by the FDSP).
A.26.10 The Fare Device shall include Fare Structure data in:
a. Fare Processing (refer A.50); and
b. The generation of Driver Shift Message (DSM) Records and Vehicle Trip Message
(VTM) Records (refer A.52 and A.53).
A.27 Tolling Data
A.27.1 The Fare Device shall collect and store tolling data.
A.27.2 Tolling data shall be obtained from a method approved by the Administrator.
A.27.3 The Fare Device shall automatically add to the Extras the applicable Toll Charge for each
Toll Road Segment traversed, as defined from time to time by the Authority.
A.27.4 The Fare Device shall be capable of calculating the Toll Charge that results from each, or
across more than one, Toll Road Segment.
Note: For example, individual toll segments may apply a Toll Charge of $5 each, but
when travelling across two toll segments, the Toll Charge may total $7 (rather than
$10).
A.27.5 The Fare Device shall collect and store tolling data when hired on.
A.27.6 The Fare Device shall include tolling data in:
a. Fare Processing (refer A.50); and
b. The generation of Driver Shift Message (DSM) Records and Vehicle Trip Message
(VTM) Records (refer A.52 and A.53).
A.28 Booking Acceptance Data
A.28.1 The Fare Device shall collect and store booking acceptance data.
A.28.2 Booking acceptance data shall be obtained from the Booking System (if connected).
A.28.3 The Fare Device shall collect and store booking acceptance data when a Driver is logged
on.
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
23
A.28.4 The Fare Device shall include booking acceptance data in the generation of Vehicle Trip
Message (VTM) Records (refer A.53).
A.29 Last Fare Data
A.29.1 The Fare Device shall collect and store data from the last fare.
A.29.2 Last fare data shall be retained when hired off until Hire On is next selected.
A.29.3 The Fare Device shall clear last fare data when Hire On is selected.
A.30 Driver Shift Data
A.30.1 The Fare Device shall collect and store Driver shift data.
A.30.2 Driver shift data shall include the following:
a. RTC date and time at Driver Log On and Log Off;
b. GPS position at Driver Log On and Log Off;
c. GPS quality at Driver Log On and Log Off;
d. Accumulated value of Total Fares in dollars and cents between Driver Log On and
Log Off;
e. Accumulated value of Extras in dollars and cents between Driver Log On and Log Off;
f.
Accumulated value of MPTP Member Subsidies in dollars and cents between Driver
Log On and Log Off;
g. Total distance travelled in kilometres (km) between Driver Log On and Log Off;
h. Total distance travelled in kilometres (km) while the Fare Device is hired on, between
Driver Log On and Log Off;
i.
Total number of Trips between Driver Log On and Log Off; and
j.
Total number of MPTP Member Trips between Driver Log On and Log Off.
A.30.3 The Fare Device shall include Driver shift data in the generation of Driver Shift Start
Message (DSSM) and Driver Shift Message (DSM) Records (refer A.51 and A.52).
A.30.4 The Fare Device shall reset Driver shift data after a Driver logs off.
A.31 Vehicle Trip Data
A.31.1 The Fare Device shall collect and store Vehicle trip data.
A.31.2 Vehicle trip data shall include:
a. RTC date and time of booking acceptance (if applicable);
b. GPS position at booking acceptance (if applicable);
c. GPS quality at booking acceptance (if applicable);
d. RTC date and time of Hire On;
e. GPS position at Hire On and Hire Off;
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
24
f.
GPS quality at Hire On and Hire Off;
g. RTC date and time of MPTP Member identification and authentication (if applicable);
h. Total distance travelled in kilometres (km) between Hire On and Hire Off; and
i.
Total value of MPTP Member Subsidy in dollars and cents between Hire On and Hire
Off.
A.31.3 The Fare Device shall include Vehicle trip data in the generation of Vehicle Trip Message
(VTM) Records (refer A.53).
A.32 Alarm Status Data
A.32.1 The Fare Device shall collect and store alarm status data.
A.32.2 The Fare Device shall collect and store alarm status data in response to events that
could indicate a malfunction, an attempt to tamper with the Fare Device or an event
associated with MPTP Member Smartcards (as defined by the Authority) (refer A.54).
A.32.3 The connection of the GPS Antenna shall be monitored and reported on in accordance
with A.54.1c and A.54.1d.
A.32.4 Unauthorised access to the data in the Fare Device shall be monitored and reported on
in accordance with A.54.1a.
A.32.5 Unauthorised access to Fare Device software shall be monitored and reported on in
accordance with A.54.1b.
A.32.6 The connection of the Speed and Distance Sensor shall be monitored and reported on in
accordance with A.54.1e and A.54.1f.
A.32.7 Events associated with MPTP Member Smartcards shall be monitored and reported on in
accordance with A.54.1g.
A.32.8 The Fare Device shall include Alarm status data in the generation of Vehicle Alarm
Message (VAM) Records (refer A.54.2).
A.33 Functionality Status Data
A.33.1 The Fare Device shall collect and store functionality status data.
A.33.2 Functionality status data refers to the operational or non-operational status of Fare
Device functions.
A.33.3 The Fare Device functions shall include, as a minimum:
a. Communications;
b. GPS Receiver;
c. Smartcard reader (if internal to the Fare Device);
d. Data storage; and
e. Fare Device status due to data storage capacity.
A.33.4 The Fare Device shall enable the display of functionality status data to be manually
selected.
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
25
A.34 Calibration Data
A.34.1 The Fare Device shall collect and store Speed and Distance Sensor calibration data.
A.34.2 Speed and Distance Sensor calibration data shall include, as a minimum:
a. RTC date and time of Calibration; and
b. Calibration Factor(s).
A.34.3 The Fare Device shall enable the display of Speed and Distance Sensor calibration data
to be selected when hired off.
FUNCTIONALITY
A.35 Driver Log On
A.35.1 The Fare Device shall allow a Driver to Log On by two methods:
a. Inserting a Driver Smartcard into the Smartcard reader (refer A.23.2) and entering a
Personal Identification Number (PIN) (refer A.23.2); or
b. Manually inputting a Driver Number and Driver Licence Number (refer A.23.5).
A.35.2 The Fare Device shall allow a Driver to Log On when:
a. Another Driver is logged on (automatically logging off the previous Driver) when the
Fare Device is hired off; or
b. No Driver is logged on.
A.35.3 When a Driver logs on, the Fare Device shall:
a. Collect and store the date and time that a Driver logs on;
b. Collect and store the Driver Number;
c. Collect and store the Driver Licence Number (if applicable);
d. Collect and store GPS position data; and
e. Collect and store GPS quality data.
A.35.4 If the Fare Device used zero satellites, or was unable to determine GPS position when a
Driver logs on, GPS position data shall be blank/void.
A.35.5 While a Driver is logged on, the Fare Device shall:
a. Collect and store the distance travelled in kilometres (km) between a Driver Log On
and Log Off;
b. Collect and store the distance travelled in kilometres (km) when hired on, between
Log On and Log Off;
c. Collect and store the value of all Total Fares in dollars and cents between Driver Log
On and Log Off;
d. Collect and store the value of all Extras in dollars and cents between Driver Log On
and Log Off;
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
26
e. Collect and store the value of MPTP Member Subsidies in dollars and cents between
a Driver Log On and Log Off;
f.
Collect and store the number of Trips between a Driver Log On and Log Off;
g. Collect and store the number of MPTP Trips between a Driver Log On and Log Off;
and
h. Generate a Driver Shift Start Message (DSSM) Record (refer A.51).
A.35.6 The Fare Device shall be able to disable a Driver Smartcard (refer A.48.7).
A.36 Driver Log Off
A.36.1 The Fare Device shall allow a Driver to Log Off.
A.36.2 For a Driver to be logged off, the Fare Device shall be hired off.
A.36.3 The Fare Device shall allow three options for a Driver to be logged off:
a. Select Log Off; or
b. Another Driver successfully logs on (refer A.35), which will Log Off the previously
logged on Driver; or
c. If a period of more than 14 hours has elapsed since the last Log On, the Fare Device
shall automatically Log Off a logged on Driver.
A.36.4 If the Fare Device is not hired off, it shall not permit the current Driver from logging off.
A.36.5 When a Driver logs off, the Fare Device shall:
a. Collect and store the time that a Driver logs off;
b. Collect and store GPS position data;
c. Collect and store GPS quality data;
d. Calculate the total distance travelled in kilometres (km) between Driver Log On and
Log Off;
e. Calculate the total distance travelled in kilometres (km) when hired on, between a
Driver Log On and Log Off;
f.
Calculate the total value of all Total Fares in dollars and cents between Driver Log On
and Log Off;
g. Calculate the total value of all Extras in dollars and cents between Driver Log On and
Log Off;
h. Calculate the total value of MPTP Member Subsidies in dollars and cents between a
Driver Log On and Log Off;
i.
Calculate the total number of Trips between a Driver Log On and Log Off;
j.
Calculate the total number of MPTP Trips between a Driver Log On and Log Off; and
k. Generate a Driver Shift Message (DSM) Record (refer A.52).
A.36.6 If the Fare Device used zero satellites, or was unable to determine GPS position when a
Driver logs off, GPS position data shall be blank/void.
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
27
A.37 Hire On
A.37.1 The Fare Device shall allow Hire On to be selected when the Fare Device is hired off or
hire paused.
A.37.2 When Hire On is selected from hired off, the Fare Device shall default to:
a. The Authority Published Fare Structure;
b. The Price Notified Fare Structure for the Vehicle in which the Fare Device is installed
(if applicable); or
c. An alternate Fare Structure selected prior to the selection of Hire On.
Note: The Fare Device shall not permit any change to the selected Fare Structure after
Hire On is selected. A new Fare Structure may be selected after a Trip is finished
(i.e. after Hire Off is selected).
A.37.3 The Fare Device shall:
a. Apply the selected Fare Structure, inclusive of any Hiring Rate, Fixed Fee and/or
Extras for Fare Processing (refer A.50);
b. Store the Fare Structure Code;
c. Store the Hiring Rate Code (if applicable);
d. Store the Fixed Fee Code (if applicable); and
e. Store the Extra Code(s) (if applicable).
A.37.4 When Hire On is selected, the Fare Device shall request the Form of Vehicle
Engagement to be selected (i.e. ‘rank’, hailed or ‘booked’).
A.37.5 When the Form of Vehicle Engagement is selected, the Fare Device shall collect and
store the selection.
A.37.6 When Hire On is selected from hired off, the Fare Device shall:
a. Visually display and audibly convey Vehicle ID, Driver Accreditation Number and Fare
Information (refer Appendix I);
Note: The Driver Accreditation Number is a subset of the Driver Number.
b. Collect and store RTC date and time data;
c. Collect and store GPS quality data;
d. Collect and store GPS position data;
e. Start accumulating the Metered Fare (if applicable);
f.
Enable the automatic accumulation of Extras and Tolls; and
g. Start accumulating the distance travelled in kilometres (km).
A.37.7 If the Fare Device used zero satellites, or was unable to determine GPS position when
Hire On is selected, GPS position data shall be blank/void.
A.37.8 When hired on, the Fare Device shall concurrently display:
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
28
a. Metered Fare (if applicable);
b. Fixed Fee (if applicable);
c. Extras (if applicable);
d. High Occupancy Fee (if applicable);
e. Hiring Rate Code (if applicable);
f.
Fixed Fee Code (if applicable); and/or
g. Extra Code(s).
Note: The High Occupancy Fee is contained in the Fixed Fee and Extras Table contained
within Appendix G.
Note: The Fare Device may also display the Cumulative Fare concurrently with the
Metered Fare (if applicable), Fixed Fee (if applicable) and Extras (if applicable).
A.37.9 The Fare Device shall increment the value of the Metered Fare by 10 cent increments, or
other increments as declared by the Authority, and Type-approved by the Administrator.
A.37.10 The Fare Device shall audibly convey the automatic accumulation of an Extra when hired
on.
A.38 Hire Pause
A.38.1 The Fare Device shall enable Hire Pause to be selected when the Fare Device is hired
on.
A.38.2 When Hire Pause is selected the Fare Device shall:
a. Visually display and audibly convey that Hire Pause has been selected;
b. Stop accumulating the distance travelled in kilometres (km);
c. Stop the automatic accumulation of Extras;
d. Enable the manual selection of Extras;
e. Enable MPTP Member Smartcard processing; and
f.
Calculate the Total Fare.
A.38.3 When hire paused, the Fare Device shall concurrently display:
a. Total Fare;
b. High Occupancy Fee (if applicable); and
c. Hiring Rate Code (if applicable); or
d. Fixed Fee Code (if applicable).
A.38.4 The Fare Device shall audibly convey the manual selection of an Extra when hire
paused.
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
29
A.39 Hire Off
A.39.1 The Fare Device shall enable Hire Off to be selected when the Fare Device is hired on or
hire paused.
A.39.2 When Hire Off is selected, the Fare Device shall:
a. Visually display and audibly convey that Hire Off has been selected (refer
Appendix I);
b. Visually flash the following at a frequency of no greater than 1 hz:
i.
Total Fare;
ii.
Metered Fare (if applicable);
iii.
Fixed Fee (if applicable);
iv.
Type and value of each Extra;
v.
High Occupancy Fee (if applicable);
vi.
MPTP Member Subsidy (if applicable); and
vii.
Hiring Rate Code
until a manual selection or input is made, which shall clear the display.
c. Enable a Trip Receipt to be provided;
d. Collect and store RTC date and time data;
e. Collect and store GPS quality data; and
f.
Collect and store GPS position data.
A.39.3 If the Fare Device used zero satellites, or was unable to determine GPS position when
Hire Off is selected, GPS position data shall be blank/void.
A.40 MPTP Member Identification and Authentication
A.40.1 The Fare Device shall enable MPTP Member identification and authentication when:
a. The Fare Device is hired on or hire paused; and
b.
A MPTP Member Smartcard is inserted into the Smartcard reader.
A.40.2 The Fare Device shall determine if a subsidy should be applied to the Total Fare (refer
A.49).
A.40.3 The Fare Device shall clear MPTP Member identification and authentication Data after it
has been used for Fare Processing and Data Record generation.
A.40.4 The Fare Device shall be able to disable the MPTP Member Smartcard (refer A.49.7).
A.41 Provide Trip Receipt
A.41.1 The Fare Device shall enable a Trip Receipt to be provided when hired off.
A.41.2 The content of the Trip Receipt is defined by the Authority, and shall include as a
minimum:
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
30
a. Vehicle ID;
b. Fare Device ID;
c. Driver Accreditation Number;
Note: The Driver Accreditation Number is a subset of the Driver Number.
d. Metered Fare (if applicable);
e. Fixed Fee (if applicable);
f.
Total value of the Extras for the Trip;
g. Hiring Rate Code;
h. Fixed Fee Code;
i.
Extra Code(s);
j.
Total Fare; and
k. RTC date and time when the Trip Receipt was provided.
A.41.3 For MPTP Member Trips, the Trip Receipt shall also contain:
a. MPTP Member Number;
Note: The MPTP Member Number is a subset of the MPTP Card Number.
b. MPTP Member Subsidy applied to the Total Fare; and
c. The value of the Total Fare less the MPTP Member Subsidy.
A.42.4
The Fare Device shall enable a Trip Receipt to be provided any number of times prior to the next
selection of Hire On.
A.42 Repeat Audio Announcement
A.42.1 The Fare Device shall enable the selection of audio announcements to be repeated,
when the Fare Device is hired on, hire paused or hired off.
A.43 Recall Last Fare
A.43.1 The Fare Device shall enable a recall of information from the last fare to be selected
when hired off.
A.43.2 Information from the last fare shall be visually displayed and audibly conveyed, and
include as a minimum:
a. Total Fare (after MPTP Member Subsidy, if applicable);
b. Value of Metered Fare (if applicable);
c. Value of Fixed Fee (if applicable);
d. Value of all Extras (if applicable);
e. Value of High Occupancy Fee (if applicable); and
f.
Value of MPTP Member Subsidy (if applicable).
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
31
A.44 Manual Selection and Input Lock
A.44.1 The Fare Device shall enable the manual selection and input lock to be selected when
the Fare Device is:
a. Hired off;
b. Hired on; or
c. Hire paused.
Note: The manual selection and input lock prevents deliberate or unintended manual
selections and/or inputs from occurring when a Driver is logged on.
A.44.2 Noting A.44.1, the manual selection and input lock shall not effect the Fare Device from
meeting the requirements in this Specification.
Note: The Fare Device shall, when the manual selection and input lock is applied,
continue to accumulate Metered Fares (if applicable) and automatic Extras (if
applicable) when hired on.
A.44.3 The Fare Device shall allow the manual selection and input lock to be locked and
unlocked by any method deemed suitable by the Administrator.
A.45 Audio Output
A.45.1 The Fare Device shall audibly convey information in English through speech-synthesis.
A.45.2 The ability of the Fare Device to audibly convey information shall not be able to be
disabled, or have its function reduced in any way.
A.46 Display Functionality Status Data
A.46.1 The Fare Device shall enable the display of functionality status data to be selected when
the Fare Device is hired off.
A.47 Display Calibration Data
A.43.1 The Fare Device shall enable the display of calibration data to be selected when the Fare
Device is hired off.
DATA PROCESSING
A.48 Driver Identification and Authentication Processing
A.48.1 The Fare Device shall perform Driver identification and authentication to enable a Driver
to Log On.
A.48.2 Driver identification and authentication shall be performed by accessing data contained
in:
a. The Driver Current List; and
b. The Driver Smartcard.
A.48.3 When a Driver Smartcard is inserted into the Smartcard reader, the Fare Device shall
confirm:
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
32
a. The Driver Number is contained on the Driver Current List;
b. The Driver Smartcard is valid;
c. The Driver Smartcard is authentic^;
d. The Driver Smartcard is not disabled^; and
e. The Driver Smartcard is not listed on the Disable List.
Note: Items denoted above with ^ are read from the Driver Smartcard.
A.48.4 A Driver Smartcard is valid if the date of a Driver Log On is inclusive of the Valid From
Date and Expiry Date contained in the Driver Smartcard.
A.48.5 A Driver Smartcard is authentic if the Fare Device and Driver Smartcard successfully
pass mutual authentication, as described within Appendix K.
A.48.6 A Driver Smartcard is disabled if the Disable Counter within the Smartcard is equal to
zero.
A.48.7 If the Driver Smartcard is listed on the Disable List and is not currently disabled, the Fare
Device shall disable the Driver Smartcard using the Card Disable Key, as described in
Appendix K.
A.48.8 The Fare Device shall enable a Personal Identification Number (PIN) to be input if the
requirements of A.48.3 are met.
A.48.9 If the PIN input matches the PIN read from the Smartcard, the Fare Device shall Log On
the Driver, as described in Appendix K.
A.48.10 When a Driver Number and Driver Licence Number is manually input (i.e. a Driver
Smartcard is not inserted into the Smartcard reader), the Fare Device shall Log On a
Driver if:
a. The Driver Number and Driver Licence are contained on the Driver Current List; and
b. The Driver Number is not contained on the Disable List.
A.48.11 The Fare Device shall leave a Driver logged off if any of the conditions in A.48.3, A.48.9
or A.48.10 are not met.
A.49 MPTP Member Identification and Authentication Processing
A.49.1 The Fare Device shall perform MPTP Member identification and authentication
processing.
A.49.2 MPTP Member identification and authentication shall be performed by accessing data
contained in:
a. The MPTP Member Current List; and
b. The MPTP Member Smartcard.
A.49.3 When a MPTP Member Smartcard is inserted into the Smartcard reader, the Fare Device
shall confirm:
a. The MPTP Member Card Number is contained on the MPTP Member Current List;
b. The MPTP Member Smartcard is valid;
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
33
c. The MPTP Member Smartcard is authentic^;
d. The MPTP Member Smartcard is not disabled^; and
e. The MPTP Member Smartcard is not listed on the Disable List.
Note: Items denoted above with ^ are read from the MPTP Member Smartcard.
A.49.4 A MPTP Member Smartcard is valid if the date of a MPTP Member processing is
inclusive of the Valid From Date and Expiry Date contained in the MPTP Member
Smartcard, as described within Appendix K.
A.49.5 A MPTP Member Smartcard is authentic if the Fare Device and MPTP Member
Smartcard successfully pass mutual authentication, as described within Appendix K.
A.49.6 A MPTP Member Smartcard is disabled if the Disable Counter within the Smartcard is
equal to zero.
A.49.7 If the MPTP Member Smartcard is contained on the Disable List and is not currently
disabled, the Fare Device shall disable the MPTP Member Smartcard, as described
within Appendix K.
A.49.8 The Fare Device shall deduct the MPTP Member Subsidy from the Total Fare as detailed
in Section A.50, if all conditions contained in A.49.3 are met.
A.49.9 The Fare Device shall adjust the value of the MPTP Member Subsidy to the Balance
Counter file contained on the MPTP Member Smartcard, as described in Appendix K.
A.49.10 The Fare Device shall not process the MPTP Member Subsidy if any of the conditions in
A.49.3 are not met.
A.49.11 The Fare Device shall visually display and audibly convey error messages for MPTP
Member MPTP Member Smartcard processing, as described in Appendix J.
A.50 Fare Processing
A.50.1 The Fare Device shall perform Fare Processing when hired on and hired paused.
A.50.2 Fare Processing shall be performed by accessing data contained from:
a. The Authority Published Fare Structure; or
b. The Price Notified Fare Structure for that Vehicle (if applicable); or
c. An alternate Fare Structure selected prior to the selection of Hire On.
A.50.3 In conjunction with A.50.2, Fare Processing shall obtain:
a. Speed and distance data;
b. RTC date and time data;
c. GPS position data; and/or
d.
Tolling data.
A.50.4 Where a Fare Structure includes a Metered Fare component, the Fare Device shall:
a. Use speed and distance data; and
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
34
b. Apply the relevant distance value from the selected Hiring Rate when the Vehicle
travels at speeds not less than the Speed Threshold Parameter; or
c. Apply the relevant time value from the selected Hiring Rate when the Vehicle travels
at speeds less than the Speed Threshold Parameter.
A.50.5 Where a Fare Structure includes time, day or date elements, the Fare Device shall:
a. Use RTC date and time data;
b. GPS position data (if applicable); and
c. Apply the relevant time, day or date value(s) from the selected Hiring Rate to the
data.
A.50.6 Where a Fare Structure includes geographic locations, zones and/or routes, the Fare
Device shall:
a. Use GPS position data;
b. Use RTC date and time data (if applicable); and
c. Apply the geographic locations, zones and/or routes(s) from the selected Hiring Rate,
Fixed Fees and/or Extra(s).
A.50.7 Where a Fare Structure includes Extras, the Fare Device shall:
a. Use manual selection and input data (for the manual selection of Extras, if
applicable);
b. Use RTC date and time data (if applicable);
c. Use GPS position data (if applicable); and
d. Apply or remove the relevant Extras value(s) from the selected Fixed Fee and Extras
Table to the data.
Note: Only those Extras that can be manually selected shall have the ability to be
removed (through a subsequent manual selection).
A.50.8 Where a Fare Structure includes Tolls, the Fare Device shall:
a. Use tolling data and/or GPS position data (if applicable); and
b. Apply the relevant Toll value(s) from the selected Fixed Fee and Extras Table to the
data.
A.50.9 The Fare Device shall calculate the value of the Total Fare when hire paused.
Note: The selection of any Extra when hire paused shall automatically recalculate the
Total Fare.
A.50.10 The Total Fare shall be the total of the following amounts:
a. Metered Fare (if applicable);
b. Accumulated Extras and Tolls (if applicable); and
c. Accumulated value of other data (if applicable).
A.50.11 The Total Fare shall be displayed while the Fare Device is hire paused and hired off.
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
35
A.50.12 The Fare Device shall also perform simultaneous Fare Processing using the Standard
Fare Structure for the purpose of calculating a MPTP Member Subsidy.
A.50.13 The Fare Device shall:
a. Determine the MPTP Member subsidy (as declared by the Authority) of the Total Fare
based upon the Standard Fare Structure;
b. Discount the value of the Total Fare (refer A.50.11) by the value of the MPTP
Member Subsidy; and
c. Limit the value of the MPTP Member Subsidy to the approved trip limit (or other
applicable value as declared by the Authority).
RECORD GENERATION
A.51 Driver Shift Start Message (DSSM) Record
A.51.1 The Fare Device shall generate a DSSM Record when a Driver logs on.
A.51.2 The DSSM Record shall consist of:
a. Record number;
b. Record type;
c. RTC date and time of generation;
d. Vehicle ID;
e. Fare Device ID;
f.
Driver Number;
g. Driver Log On method;
h. GPS quality at Driver Log On; and
i.
GPS position at Driver Log On.
A.51.3 If the Fare Device used zero satellites, or was unable to determine GPS position when a
Driver logs on, GPS position data shall be blank/void.
A.52 Driver Shift Message (DSM) Record
A.52.1 The Fare Device shall generate a DSM Record when a Driver logs off.
A.52.2 The DSM Record shall consist of:
a. Record number;
b. Last DSSM Record number;
c. Record type;
d. RTC date and time of generation;
e. Vehicle ID;
f.
Fare Device ID;
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
36
g. Driver Number;
h. GPS quality at Driver Log Off;
i.
GPS position at Driver Log Off;
j.
Accumulated value of Total Fares in dollars and cents between Driver Log On and
Log Off;
k. Accumulated value of all Extras between in dollars and cents between Driver Log On
and Log Off;
l.
Accumulated value of MPTP Member Subsidies in dollars and cents between Driver
Log On and Log Off;
m. Total distance travelled in kilometres (km) between Driver Log On and Log Off;
n. Total distance travelled in kilometres (km) while hired on, between Driver Log On and
Log Off;
o. Total number of Trips between a Driver Log On and Log Off; and
p. Total number of MPTP Trips between a Driver Log On and Log Off.
A.52.3 If the Fare Device used zero satellites, or was unable to determine GPS position when a
Driver logs off, GPS position data shall be blank/void.
A.53 Vehicle Trip Message (VTM) Record
A.53.1 The Fare Device shall generate a Vehicle Trip Message (VTM) Record.
A.53.2 A VTM Record shall be generated when Hire Off is selected.
A.53.3 The VTM Record shall consist of:
a. Record number;
b. Record type;
c. RTC date and time of generation;
d. Vehicle ID;
e. Fare Device ID;
f.
Driver Number;
g. RTC date and time of booking acceptance (if applicable);
Note: This field is optional. Fare Devices that are integrated with Booking Systems may
populate this field.
h. GPS quality at booking acceptance (if applicable);
Note: This field is optional. Fare Devices that integrate with Booking System may
populate this field.
i.
GPS position at booking acceptance (if applicable);
Note: This field is optional. Fare Devices that are integrated with a Booking System may
populate this field.
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
37
j.
RTC date and time when Hire On is selected;
k. GPS quality when Hire On is selected;
l.
GPS position when Hire On is selected;
m. GPS quality when Hire Off is selected;
n. GPS position when Hire Off is selected;
o. MPTP Member Number (if applicable);
p. RTC date and time of MPTP Member identification and authentication (if applicable);
q. The total distance travelled in kilometres (km) while the Fare Device between Hire On
and Hire Off;
r.
Total Fare in dollars and cents;
s. Metered Fare in dollars and cents;
t.
Total value of all Extras in dollars and cents;
u. Hiring Rate Code used;
v. Fixed Fee Code used;
w. Extra Code(s) used;
x. Form of Vehicle Engagement (i.e. ‘rank’, ‘hailed’ or ‘booked’);
y. Value of MPTP Member Subsidy (if applicable); and
z. Total Fare less the value MPTP Member Subsidy (if applicable).
A.53.4 If the Fare Device used zero satellites, or was unable to determine GPS position when
Hire Off is selected, GPS position data shall be blank/void.
A.54 Vehicle Alarm Message (VAM) Record
A.54.1 The Fare Device shall generate Vehicle Alarm Message (VAM) Records for each of the
following:
a. Unauthorised access to data in the Fare Device is detected;
b. Unauthorised access to Fare Device software is detected;
c. The GPS Antenna is disconnected from the Fare Device;
d. The GPS Antenna is reconnected to the Fare Device;
e. The Speed and Distance Sensor is disconnected from the Fare Device;
f.
The Speed and Distance Sensor is reconnected to the Fare Device; or
g. An event associated with a MPTP Member Smartcard (refer Appendix K).
A.54.2 A Vehicle Alarm Message (VAM) Record shall consist of the following data:
a. Record number;
b. Record type;
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
38
c. Date and time of generation;
d. Vehicle ID;
e. Fare Device ID;
f.
Driver Number (if a Driver is logged on);
g. MPTP Member Number (if applicable);
h. GPS quality;
i.
GPS position; and
j.
The alarm code that corresponds to the event that triggered the VAM Record as per
Appendix H.
A.54.3 If the Fare Device used zero satellites, or was unable to determine GPS position when a
VAM Record is generated, GPS position data shall be blank/void.
A.54.4 Any individual VAM Record that is generated more than 10 times in 10 seconds shall be
suppressed.
A.54.5 If the Fare Device has suppressed an Alarm, the Fare Device shall be considered
malfunctioning, stopping further Fare Processing until the issue is rectified.
A.55 Vehicle Location Message (VLM) Record
A.55.1 The Fare Device shall generate Vehicle Location Message (VLM) Records.
A.55.2 VLM Records shall be continuously generated and stored at time intervals of 10 (± 0.2)
seconds when the Vehicle is, at a minimum, moving.
Note: As an example, a connection to the Vehicle’s ignition, identifying when the Ignition
is on, would achieve this requirement.
A.55.3 A VLM Record shall consist of at least the following data:
a. Record Number;
b. Record Type;
c. GPS date and time of generation;
d. Vehicle ID;
e. Fare Device ID;
f.
Driver Number (if a Driver is logged on);
g. GPS quality;
h. GPS position;
i.
GPS speed;
j.
Form of Vehicle Engagement; and
k. Occupancy (Hired on, hired off, Hire paused)
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
39
A.55.4 The GPS date and time of generation shall be populated by the date and time from the
Real Time Clock when GPS date and time is unavailable.
A.55.5 If the Fare Device used zero satellites, or was unable to determine GPS position when a
VLM is generated, GPS position data shall be blank/void.
A.55.6 If the Fare Device is unable to determine the speed of the Vehicle, GPS speed data shall
be blank/void.
A.56 Record Numbering
A.56.1 All Fare Device Data Records shall be assigned record numbers from the same
numbering sequence, with consecutive and increasing numbers assigned to successive
Fare Device Data Records in order of generation.
A.56.2 The Fare Device Data Record numbering sequence shall be large enough such that the
same record number shall not be issued more than once every twelve months.
DATA STORAGE
A.57 Fare Device Data Record Storage Capability
A.57.1 The Fare Device shall be capable of storing not less than 50,000 Fare Device Data
Records.
A.57.2 If the volume of data collected and generated prior to transfer to the Authority exceeds
the data storage capacity of the Fare Device:
a. New data shall not overwrite stored data; and
b. The Fare Device will only be able to transfer data, with all other data collection
and functionality disabled.
A.58 Fare Device External Power Supply Failure/Shut Down
A.58.1 In the event that the External Power Supply for the Fare Device fails or is disconnected,
the Fare Device shall retain stored data and Fare Device Data Records for at least
fourteen (14) days.
DATA SECURITY
A.59 Data Security and Confidentiality Measures
A.59.1 It shall not be possible for collected or stored data or software memory within the Fare
Device to be accessible or capable of being manipulated by any person, device or
system, other than that authorised by the FDSP. Security and confidentiality of data
stored in the Fare Device shall be maintained at all times.
A.59.2 Data security measures shall be consistent with those that would meet the Payment Card
Industry – Data Security Standard (PCI-DSS).
A.59.3 Data security for the transfer of Fare Device Data Records to the Authority shall be in
accordance with the guide provided by the Administrator.
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
40
A.60 Fare Device Communications Capability
A.60.1 The Fare Device shall be capable of communicating with the Administrator. The
transmission of Fare Device Data Records to the Authority shall be secure and guarantee
standards for privacy and data integrity and minimise the risk of interception by third
parties, at a level consistent with services provided by Australian licensed
telecommunications carriers.
DATA TRANSFER
A.61 Transfer of Data from Fare Device to Authority
A.61.1 Fare Device Data Records shall be transferred to the Authority.
A.61.2 The Fare Device shall transfer the Fare Data Records to the Authority in accordance with
the guide provided by the Authority.
A.61.3 The Fare Device shall receive the Driver Current List in accordance with the guide
provided by the Authority.
A.61.4 The Fare Device shall receive the MPTP Member Current List in accordance with the
guide provided by the Authority.
A.61.5 The Fare Device shall receive the Disable List in accordance with the guide provided by
the Authority.
A.61.6 The transfer of stored data from a Fare Device to the Authority shall be performed within
10 seconds of the Fare Device’s Data Record generation provided that a Fare Device is
in a communications coverage area.
A.61.7 If at the time of the scheduled data transfer the Vehicle is out of communication
coverage, then data transfer shall commence within 60 seconds of when the
communication network becomes available.
Note: The performance requirements above shall be considerate of delays within the
communications network.
A.61.8 Each Fare Device Data Record stored in the Fare Device shall only be deleted after the
record is transferred from the Fare Device and successful receipt is confirmed by the
Authority.
PROVISION OF FARE DEVICE AUDIT INFORMATION
A.62 Fare Device Audit
A.62.1 For the purposes of audit, on receipt of each update, the Fare Device shall provide to the
FDSP system a positive confirmation of any:
a. Software updates;
b. Firmware updates;
c. Audio announcement updates; and
d. Fare Structure updates.
www.tca.gov.au
Fare Device Functional and Technical Specification
Error! Unknown document property name.
41
APPENDIX A – DEFINITION OF TERMS
Administrator
The entity responsible for the type-approval and audit of Fare Devices.
Authority
Taxi Services Commission (TSC) of Victoria.
Authority Published Fare Structure
The Fare Structure set by the Essential Services Commission (ESC).
Booking System
A system which enables the booking and dispatch of Vehicles.
Calibration Factor
The value used in the conversion between a measurement and an accurate desired output.
CAN
An acronym Controller Area Network – a common automotive communication standard for
information exchange between electronic modules.
Driver
A person authorised or accredited to drive a Vehicle.
Driver Accreditation Number
The unique identifier assigned to each Driver by the Authority.
Driver Number
The unique identifier assigned to Driver Smartcards by the Authority.
Note: There is a relationship between the Driver Number and Driver Accreditation
Number.
The Driver Accreditation Number consists of the 6 consecutive digits starting
from the third least significant digit to the eighth least significant digit of the
Driver Number. For example, if the Driver Number was
999999999965432199 then the Driver Accreditation Number is 654321.
External Power Supply
The External Power Supply is a power supply from the Vehicle.
Fare Device Data Record
A record generated by the Fare Device from data collected by the Fare Device.
Fare Device Service Provider (FDSP)
The entity responsible for Fare Device installation, operation, maintenance and calibration.
Fixed Fee
The Total Fare of a Trip which is calculated by means other than obtaining time and
distance inputs from the Trip.
GNSS
The Global Navigation Satellite System (GNSS) comprises several networks of satellites
that transmit high-frequency radio signals containing time and distance data that can be
picked up by a receiver, allowing the user to identify the location of the receiver anywhere
around the globe.
GPS
A form of GNSS controlled by the US Department of Defense.
Taxi Services Commission
Level 23, 80 Collins Street, Melbourne VIC 3000
GPO Box 1716, Melbourne VIC 3001 Phone: 1800 638 802 (toll-free) www.taxi.vic.gov.au
July 2013
DOT7670_S061_07/13
1
GPS Antenna
The antenna used to receive GPS Signals.
GPS Receiver
A GPS unit connected to the Fare Device.
GPS Signal
GPS satellites transmit two low power radio signals, designated L1 and L2. The Fare Device
utilises civilian GPS which usually uses the L1 frequency.
Hirer
The person being transported during a Trip in a Vehicle.
Hire Off
A manual selection made to the Fare Device to finish a Trip.
Hired off
An operational state of the Fare Device (which enables and restricts specific functions),
after Hire On has been selected.
Hire On
A manual selection made to the Fare Device to start a Trip.
Hired on
An operational state of the Fare Device (which enables and restricts specific functions),
after Hire On has been selected.
Hire Pause
A manual selection made to the Fare Device to pause a Trip.
Hire paused
An operational state of the Fare Device (which enables and restricts specific functions),
after Hire Pause has been selected.
Hiring Rate
The monetary value applied for Fare Processing during hired on – as contained in the
Hiring Rate Table.
Hiring Rate Code
A unique code applied to each Hiring Rate in the Fare Structure.
Internal Power Supply
A secondary power supply if the External Power Supply is disconnected, which enables the
Fare Device to continue operation for at least 7 days
Metered Fare
The Flag Fall plus the charge for distance travelled and/or time elapsed, calculated
according to the Hiring Rate, exclusive of Extras.
Multi Purpose Taxi Program (MPTP)
The MPTP is a government program that subsidises the Total Fare for people with severe
and permanent disabilities.
MPTP Card Number
The unique identifier assigned to MPTP Member Smartcards by the Authority.
MPTP Member Number
The unique identifier assigned to each MPTP Member by the Authority.
Note: There is a relationship between the MPTP Member Number and the MPTP
Card Number.
The MPTP Member Number consists of the 6 consecutive digits starting from
the third least significant digit to the eighth least significant digit of the MPTP
Taxi Services Commission
Level 23, 80 Collins Street, Melbourne VIC 3000
GPO Box 1716, Melbourne VIC 3001 Phone: 1800 638 802 (toll-free) www.taxi.vic.gov.au
July 2013
DOT7670_S061_07/13
2
Card Number. For example, if the MPTP Card Number was
999999999965432199 then the MPTP Member Number is 654321
MPTP Member Subsidy
A co-payment by the Victorian Government which reduces the value of fares for MPTP
Members.
Operator
A person or organisation maintaining and operating a Vehicle.
Price Notified Fare Structure
A Fare Structure notified to the Authority by an Operator.
Real Time Clock
A computer clock that keeps track of the current time and date.
Smartcard
A secure card with an embedded integrated circuit.
Fare Device Identifier
A unique identifier assigned to each Fare Device.
Speed Threshold Parameter
The speed of the vehicle whereby the calculation of a fare switches from a time to a
distance based charge and vice versa.
Toll Charge
The charge applied for travelling on a specific section of road. This is usually a Toll Road
but could also refer to other locations such as an airport.
Toll Road
A road managed by a Toll Road operator.
Toll Road Segment
A section of a Toll Road on which a Toll Charge applies. In some instances, a reduced
charge may apply for driving on consecutive sections of a Toll Road as compared to the
sum of the individual sections.
Trip
The period between when the Fare Device is selected to Hire On and Hire Off.
Trip Receipt
A receipt provided at the end of a trip.
Type-approval
Formal confirmation by the Authority that a ‘type’ of Fare Device satisfies all requirements
contained in this Specification.
UTC
An abbreviation for Coordinated Universal Time.
Vehicle
A Motor Vehicle in relation to which a commercial passenger vehicle licence (issued under
the Transport (Compliance and Miscellaneous) Act 1983) then subsists, being a licence
allowing for the operation of the Motor Vehicle as a Taxi-Cab (within the meaning of the
Transport (Compliance and Miscellaneous) Act 1983).
Vehicle Identifier (Vehicle ID)
The registration number of the Vehicle.
Taxi Services Commission
Level 23, 80 Collins Street, Melbourne VIC 3000
GPO Box 1716, Melbourne VIC 3001 Phone: 1800 638 802 (toll-free) www.taxi.vic.gov.au
July 2013
DOT7670_S061_07/13
3
APPENDIX B – ROLES AND RESPONSIBILITIES
1.
The Authority:
a. Receives records from Fare Devices;
b. Is notified of Fare Structure changes;
c. Administers the Multi Purpose Taxi Program (MPTP); and
d. Distributes Driver and MPTP Member Lists.
a. The Administrator:
Manages Type-approvals of Fare Devices, on behalf of the Authority.
2.
Fare Device Service Provider (FDSP):
a. Installs, monitors, and maintains Fare Devices;
b. Communicates with Fare Devices; and
c. May provide commercial services to Operators.
3.
Hirer:
a. Pays for service; and
b. May be an MPTP Member.
4.
Driver:
a. Operates the Fare Device;
b. Receives and processes payments; and
c. Drives the Vehicle.
5.
Operator:
a. Operates and maintains the Vehicle;
b. Engages Driver(s) and/or is also a Driver; and
c. Operates a Fare Device that conforms with all requirements contained in this
Specification.
Taxi Services Commission
Level 23, 80 Collins Street, Melbourne VIC 3000
GPO Box 1716, Melbourne VIC 3001 Phone: 1800 638 802 (toll-free) www.taxi.vic.gov.au
July 2013
DOT7670_S061_07/13
4
APPENDIX C – OPERATIONAL STATES OF THE FARE
DEVICE
Power
Driver logged
on/logged off
Hired on/
hire paused/
hired off
X
X
X
Alarm Status Data
X
X
X
Date and Time Data
External
X
X
Display Calibration Data
External
X
OFF
OFF
Driver Identification and
Authentication
3
External
X
X
Driver Log On
4
External
On
X
Booking Acceptance Data (if
applicable)
4
External
On
X
MPTP Member Identification
and Authentication
4
External
On
X
Manual Selection and Input
Lock
5
External
On
On
Metered Fare
5
External
On
On
Hire Pause
6
External
On
Off
Driver Log Off
6
External
On
Off
Select Fare Structure
6
External
On
Off
Display Last Fare
6
External
m
Off
Produce Trip Receipt
6
External
On
Pause
Total Fare
7
External
On
Pause
Hire Off
8
External
On
On/Pause
Extras Data
9
External
On
On/Pause
Hire On
10
X
X
X
State
1
2
3
Function/Data
Collected/Report Generated
GPS Quality, Position, Speed,
Date and Time Data
Taxi Services Commission
Level 23, 80 Collins Street, Melbourne VIC 3000
GPO Box 1716, Melbourne VIC 3001 Phone: 1800 638 802 (toll-free) www.taxi.vic.gov.au
July 2013
DOT7670_S061_07/13
5
APPENDIX D – REQUIREMENTS FOR THE PROVISION OF
FARE DEVICES
1.
The requirements contained in this Appendix shall apply to Applicants as well as
FDSPs unless otherwise stated.
2.
The requirements contained in this Appendix shall apply to all Fare Devices
submitted to the Administrator for:
a. Type-approval assessment (as applicable);
b. Ongoing audit and review; and
c. Re-certification (as applicable).
3.
The Administrator will, if requested, complete and return to the Applicant a signed
confidentiality agreement in reasonable terms for the protection of the Applicant’s
intellectual property in the Fare Device.
4.
The Applicant/FDSP shall be responsible, at its cost, for the installation, calibration,
operation and maintenance of all Fare Devices provided to the Administrator.
5.
The Applicant/FDSP shall provide to the Administrator all Services reasonably
required to enable the Administrator to carry out the activities specified in 2.
Taxi Services Commission
Level 23, 80 Collins Street, Melbourne VIC 3000
GPO Box 1716, Melbourne VIC 3001 Phone: 1800 638 802 (toll-free) www.taxi.vic.gov.au
July 2013
DOT7670_S061_07/13
6
APPENDIX E – DATA FORMATS FOR FARE DEVICE
DATA RECORDS
Note: In describing the format of fixed length record structures, the format of each field is specified
as “YYYYMMDD” (date), “HHMMSS” (time), “D” (fixed decimal), “AN (alphanumeric) or “N” (numeric);
the latter two formats include an associated field length. The format for decimal has an associated
length number of decimal places (e.g. 9.2 is a total field length of 9 characters with 2 decimal places).
Records fields where the value does not occupy the full length allocated shall be padded by trailing
spaces (for alphanumeric data) or leading zeros (for numeric and decimal data) in order to maintain
the fixed length record structure. Blank/void values for optional fields shall be specified by padding the
entire field with spaces.
Driver Shift Start Message (DSSM) Record Format
Number
Name
Use
Format
Notes
DSSM01
Record Number
Mandatory
N(10)
Value from 0000000000 - 9999999999
DSSM02
Date of record
generation
Mandatory
YYYYMMDD
RTC Date of generation of the record i.e.
20141205
DSSM03
Time of record
generation
Mandatory
HHMMSS
RTC Time of generation of the record i.e.
221436
DSSM04
Fare Device ID
Mandatory
AN (12)
Fare Device identifier i.e. 12AB56CD91EF
DSSM05
Vehicle ID
Mandatory
AN (6)
Vehicle identifier i.e. AB1234
DSSM06
Driver Number
Mandatory
AN (18)
18 character identifier
DSSM07
Driver Card Number
manually entered;
Mandatory
N(1)
DSSM08
Log On Latitude
Mandatory
D (9.5)
Signed decimal degrees (GDA94) from
-90.00000 to +90.00000, for example
-12.34567
DSSM09
Log On Longitude
Mandatory
D (10.5)
Signed decimal degrees (GDA94) from
-180.00000 to +180.00000, for example
+123.45678
DSSM10
Number of Satellites
(at Log On)
Mandatory
N (2)
Value from 0-99
DSSM11
HDOP (at Log On)
Mandatory
D (4.1)
Decimal value from 0.0 to 99.9
0 = Automatically entered
1 = Manually entered
Taxi Services Commission
Level 23, 80 Collins Street, Melbourne VIC 3000
GPO Box 1716, Melbourne VIC 3001 Phone: 1800 638 802 (toll-free) www.taxi.vic.gov.au
July 2013
DOT7670_S061_07/13
7
Driver Shift Message (DSM) Record
Number
Name
Use
Format
Notes
DSM01
Record Number
Mandatory
N(10)
Value from 0000000000 - 9999999999
DSM02
Last Record Number
of DSSM
Mandatory
N(10)
Value from 0000000000 - 9999999999
DSM03
Date of record
generation
Mandatory
YYYYMMDD
RTC Date of generation of the record i.e.
20141205
DSM04
Time of record
generation
Mandatory
HHMMSS
RTC Time of generation of the record i.e.
221436
DSM05
Fare Device ID
Mandatory
AN (12)
Fare Device identifier i.e. 12AB56CD91EF
DSM06
Vehicle ID
Mandatory
AN (6)
Vehicle identifier i.e. AB1234
DSM07
Driver Number
Mandatory
AN (18)
18 character identifier
DSM08
Log Off Latitude
Mandatory
D (9.5)
Signed decimal degrees (GDA94) from
-90.00000 to +90.00000, for example
-12.34567
DSM09
Log Off Longitude
Mandatory
D (10.5)
Signed decimal degrees (GDA94) from
-180.00000 to +180.00000, for example
+123.45678
DSM10
Number of Satellites
(at Log Off)
Mandatory
N (2)
Value from 0-99.
DSM11
HDOP (at Log Off)
Mandatory
D (4.1)
Value from 0.0 to 99.9
DSM12
Total distance
travelled between Log
On and Log Off
Mandatory
D(5.1)
Value 0.0 to 999.9
DSM13
Total distance
travelled while hired
between Log On and
Log Off
Mandatory
D(5.1)
Value 0.0 to 999.9
DSM14
Accumulation of Total
Fares
Mandatory
D(7.2)
Value 0.00 to 9999.99
DSM15
Accumulation of all
Extras
Mandatory
D(7.2)
Value 0.00 to 9999.99
DSM16
Total number of trips
between Log On and
Log Off
Mandatory
D(2)
Value 00 to 99
DSM17
Total number of MPTP
Trips between Log On
and Log Off
Mandatory
D(2)
Value 00 to 99
Taxi Services Commission
Level 23, 80 Collins Street, Melbourne VIC 3000
GPO Box 1716, Melbourne VIC 3001 Phone: 1800 638 802 (toll-free) www.taxi.vic.gov.au
July 2013
DOT7670_S061_07/13
8
Vehicle Trip Message (VTM) Record Format
Number
Name
Use
Format
Notes
VTM01
Record Number
Mandatory
N(10)
Value from 0000000000 9999999999
VTM02
Date of record
generation
Mandatory
YYYYMMDD
RTC Date of generation of the
record i.e. 20141205
VTM03
Time of record
generation
Mandatory
HHMMSS
RTC Time of generation of the
record i.e. 221436
VTM04
Fare Device ID
Mandatory
AN (12)
Fare Device identifier i.e.
12AB56CD91EF
VTM05
Vehicle ID
Mandatory
AN (6)
Vehicle identifier i.e. AB1234
VTM06
Driver Number
Mandatory
AN (18)
18 character identifier
VTM07
Booking acceptance
date
Optional
YYYYMMDD
RTC Date of Log On
VTM08
Booking acceptance
time
Optional
HHMMSS
RTC Time of Log On
VTM09
Booking acceptance
Latitude
D (9.5)
Signed decimal degrees
(GDA94) from -90.00000 to
+90.00000, for example
-12.34567
VTM10
Booking acceptance
Longitude
Optional
D (10.5)
Signed decimal degrees
(GDA94) from -180.00000 to
+180.00000, for example
+123.45678
VTM11
Number of Satellites
(at booking
acceptance time)
Optional
N (2)
Value from 00 – 99
VTM12
HDOP (at booking
acceptance time)
Optional
D (4.1)
Decimal value
VTM13
Date when Hire On is
selected from hired off
(start of Trip)
Mandatory
YYYYMMDD
RTC date of Fare Device when
Hire On is selected from hired off
VTM14
Time when Hire On is
selected from hired off
(start of Trip)
HHMMSS
RTC time of Fare Device when
Hire On is selected from hired off
moving from Hire Off to Hire On
after Fare Structure selection.
VTM15
Latitude when Hire On
selected from Hired
Off (start of Trip)
D (9.5)
Signed decimal degrees
(GDA94) from -90.00000 to
+90.00000, for example
-12.34567
Optional
Mandatory
Mandatory
Taxi Services Commission
Level 23, 80 Collins Street, Melbourne VIC 3000
GPO Box 1716, Melbourne VIC 3001 Phone: 1800 638 802 (toll-free) www.taxi.vic.gov.au
July 2013
DOT7670_S061_07/13
9
VTM16
Longitude when Hire
On selected from
hired off (start of Trip)
Mandatory
D (10.5)
Signed decimal degrees
(GDA94) from -180.00000 to
+180.00000, for example
+123.45678
VTM17
Number of Satellites
when Hire On
selected from hired off
(start of Trip)
Mandatory
N (2)
00 to 99
VTM18
HDOP when Hire On
selected from hired off
(start of Trip)
Mandatory
D (4.1)
0.0 to 99.9
VTM19
Latitude when Hire Off
is selected (end of
Trip)
D (9.5)
Signed decimal degrees
(GDA94) from -90.00000 to
+90.00000, for example
-12.34567
VTM20
Longitude when Hire
Off is selected (end of
Trip)
Mandatory
D (10.5)
Signed decimal degrees
(GDA94) from -180.00000 to
+180.00000, for example
+123.45678
VTM21
Number of Satellites
when Hire Off is
selected (end of Trip)
Mandatory
N (2)
00 to 99
VTM22
HDOP when Hire Off
is selected (end of
Trip)
Mandatory
D (4.1)
0.0 to 99.9
VTM23
Total distance
travelled between the
selection of Hire On
and Hire Off
Mandatory
D(5.1)
0.0 to 999.9
VTM24
Total Fare
Mandatory
D(7.2)
0.00 to 9999.99
VTM25
Metered Fare
Mandatory
D(7.2)
0.00 to 9999.99
VTM26
Total of the Extras for
the Trip
Mandatory
D(6.2)
0.00 to 999.99
VTM27
Hiring Rate Code
Optional
AN(5)
A1B2C
VTM28
Fixed Fare or Extras
Code #1
Optional
AN(5)
A1B2C
VTM29
Fixed Fare or Extras
Code #2
Optional
AN(5)
A1B2C
VTM30
Fixed Fare or Extras
Code #3
Optional
AN(5)
A1B2C
VTM31
Fixed Fare or Extras
Code #4
Optional
AN(5)
A1B2C
Mandatory
Taxi Services Commission
Level 23, 80 Collins Street, Melbourne VIC 3000
GPO Box 1716, Melbourne VIC 3001 Phone: 1800 638 802 (toll-free) www.taxi.vic.gov.au
July 2013
DOT7670_S061_07/13
10
VTM32
Fixed Fare or Extras
Code #5
Optional
AN(5)
A1B2C
VTM33
Fixed Fare or Extras
Code #6
Optional
AN(5)
A1B2C
VTM34
Fixed Fare or Extras
Code #7
Optional
AN(5)
A1B2C
VTM35
Fixed Fare or Extras
Code #8
Optional
AN(5)
A1B2C
VTM36
Fixed Fare or Extras
Code #9
Optional
AN(5)
A1B2C
VTM37
Fixed Fare or Extras
Code #10
Optional
AN(5)
A1B2C
VTM38
Form of vehicle
engagement
Mandatory
N(1)
1 = Rank
2 = Hail
3 = Booking
VTM39
MPTP Member
number
Optional
AN(18)
18 character identifier
VTM40
MPTP Member
Subsidy value
Optional
D(5.2)
0.00 to 99.99
VTM41
Total Fare less the
MPTP Member
Subsidy
Optional
D(7.2)
0.00 to 9999.99
Vehicle Location Message (VLM) Record Format
Number
Name
Use
Format
Notes
VLM01
Record Number
Mandatory
N(10)
Value from 0000000000 9999999999
VLM02
Date of record
generation
Mandatory
YYYYMMDD
GPS Date of generation of the
record
VLM03
Time of record
generation
Mandatory
HHMMSS
GPS Time of generation of the
record
VLM04
Fare Device ID
Mandatory
AN (12)
Fare Device identifier i.e.
12AB56CD91EF
VLM05
Vehicle ID
Mandatory
AN (6)
Vehicle identifier i.e. AB1234
VLM06
Driver Number
Optional
AN (18)
18 character identifier
Taxi Services Commission
Level 23, 80 Collins Street, Melbourne VIC 3000
GPO Box 1716, Melbourne VIC 3001 Phone: 1800 638 802 (toll-free) www.taxi.vic.gov.au
July 2013
DOT7670_S061_07/13
11
VLM07
GPS Latitude
Mandatory
D (9.5)
Signed decimal degrees (GDA94)
from -90.00000 to +90.00000, for
example -12.34567
VLM08
GPS Longitude
Mandatory
D (10.5)
Signed decimal degrees (GDA94)
from -180.00000 to +180.00000, for
example +123.45678
VLM09
GPS Speed
Mandatory
D(5.1)
000.0 to 999.9
VLM10
Number of Satellites (at
Alarm activation)
Mandatory
N (2)
00 to 99
VLM11
HDOP (at Alarm
activation)
Mandatory
D (4.1)
0.0 to 99.9
1 = Rank
Form of vehicle
engagement
VLM12
Mandatory
N(1)
2 = Hail
3 = Booking
1 = Hire Off
VLM13
Occupancy
Mandatory
N(1)
2 = Hire On
3 = Hire Pause.
Vehicle Alarm Message (VAM) Record Format
Number
Name
Use
Format
Notes
VAM01
Record Number
Mandatory
N(10)
Value from 0000000000 9999999999
VAM02
Date of record generation
Mandatory
YYYYMMD
D
RTC Date of generation of the
record i.e. 20141205
VAM03
Time of record generation
Mandatory
HHMMSS
RTC Time of generation of the
record i.e. 221436
VAM04
Fare Device ID
Mandatory
AN (12)
Fare Device identifier i.e.
12AB56CD91EF
VAM05
Vehicle ID
Mandatory
AN (6)
Vehicle identifier i.e. AB1234
VAM06
Driver Number
Optional
AN (18)
18 character identifier
VAM07
MPTP Member Number
Optional
AN(18)
18 character identifier
VAM08
GPS Latitude at Alarm
activation
Mandatory
D (9.5)
Signed decimal degrees (GDA94)
from -90.00000 to +90.00000, for
example -12.34567
Taxi Services Commission
Level 23, 80 Collins Street, Melbourne VIC 3000
GPO Box 1716, Melbourne VIC 3001 Phone: 1800 638 802 (toll-free) www.taxi.vic.gov.au
July 2013
DOT7670_S061_07/13
12
VAM09
GPS Longitude at Alarm
activation
Mandatory
D (10.5)
Signed decimal degrees (GDA94)
from -180.00000 to +180.00000, for
example +123.45678
VAM10
Number of Satellites (at
Alarm activation)
Mandatory
N (2)
00 to 99
VAM11
HDOP (at Alarm
activation)
Mandatory
D (4.1)
0.0 to 99.9
VAM12
Alarm Code
Mandatory
N(2)
0 to 99
Taxi Services Commission
Level 23, 80 Collins Street, Melbourne VIC 3000
GPO Box 1716, Melbourne VIC 3001 Phone: 1800 638 802 (toll-free) www.taxi.vic.gov.au
July 2013
DOT7670_S061_07/13
13
APPENDIX F – HIRING RATES TABLE
In describing the Hiring rates, the format of each field is specified as “YYMMDD” (date), “MMDD” (day), “HHMMSS” (time), “D” (fixed decimal), “AN”
alphanumeric or “N” numeric; the latter two formats include an associated field length. The format for decimal has an associated field length and number of
decimal places (e.g. 9.2 is a total length of 9 characters with 2 decimal places).
Note:
Hiring rates within this table have been provided as an example only
Metropolitan
Melbourne, Frankston,
Dandenong and Port
Phillip
20140
701
20140
701
0900
00
1700
00
1659
00
0859
32
Peak Rate (10pm – 4am Friday
and Saturday)
20140
701
2200
00
0400
32
Fixed Fee - Refer Fixed Fee
and Extras Table
20140
701
0000
00
U1
Standard
20140
701
U2
High Occupancy
20140
701
M1
Day Rate (9am – 5pm)
M2
Overnight Rate (5pm – 9am)
M3
M4
4.2
0
5.2
0
100
0
100
0
1.62
2
1.80
4
0000111
6.2
0
100
0
1.98
6
2359
32
1111111
-
0
0
0000
00
2359
59
1111111
3.6
0
100
0
0000
00
2359
59
1111111
3.6
0
100
0
1111111
1111111
M..n
Urban (Geelong
Ballarat Bendigo)
U..n
Taxi Services Commission
Level 23, 80 Collins Street, Melbourne VIC 3000
GPO Box 1716, Melbourne VIC 3001 Phone: 1800 638 802 (toll-free) www.taxi.vic.gov.au
July 2013
DOT7670_S061_07/13
1
Comment AN(40)
Cost per Distance
increment ($)
D(5.3)
Time increment
(min) N(2)
Cost per time
increment
($)D(5.3)
Speed threshold
km/h N(2)
Distance increment
(metres) N (4)
0110000 =
Tuesday and
Flagfall
$ D(4.2)
Wednesday
0000001 = Sunday
1000000 = Monday
To Time HHMMSS
Applicable Day of
Week N (7)
From Time
HHMMSS
To Date
YYYYMMDD
From Date
YYYYMMDD
Description AN
(40)
Hiring Rate Code
AN (5)
Zone AN (40)
HIRING RATES TABLE
0.5
68
0.6
31
2
1
2
1
Exam
ple
Exam
ple
1
0.6
95
2
1
Exam
ple
0
0
0
Exam
ple
1
1
Country
C1
Standard
20140
701
0000
00
2359
59
1111111
3.7
0
C2
High Occupancy
20140
701
0000
00
2359
59
1111111
3.7
0
CPN
1
CPN
2
CPN
3
Price Notification - Company 1 Hiring Rate 1
Price Notification - Company 1 Hiring Rate 2
Price Notification - Company 1 Hiring Rate 3
20140
701
20140
701
20140
701
0000
00
0600
00
0000
00
2359
59
2359
59
0559
59
CPN
4
Price Notification - Company 2 Hiring Rate 1
20140
701
0000
00
2359
00
1111100
CPN
5
CPN
..n
Price Notification - Company 2 Hiring Rate 2
20140
701
0600
00
2359
00
0000011
100
0
100
0
C..n
Taxi Services Commission
Level 23, 80 Collins Street, Melbourne VIC 3000
GPO Box 1716, Melbourne VIC 3001 Phone: 1800 638 802 (toll-free) www.taxi.vic.gov.au
July 2013
DOT7670_S061_07/13
1111100
0000011
0000011
2
6.0
0
7.0
0
8.0
0
6.5
0
7.7
0
500
0
100
00
200
00
600
0
900
0
Comment AN(40)
Cost per Distance
increment ($)
D(5.3)
Time increment
(min) N(2)
Cost per time
increment
($)D(5.3)
Speed threshold
km/h N(2)
Distance increment
(metres) N (4)
0110000 =
Tuesday and
Flagfall
$ D(4.2)
Wednesday
0000001 = Sunday
1000000 = Monday
To Time HHMMSS
Applicable Day of
Week N (7)
From Time
HHMMSS
To Date
YYYYMMDD
From Date
YYYYMMDD
Description AN
(40)
Hiring Rate Code
AN (5)
Zone AN (40)
HIRING RATES TABLE
APPENDIX G – FIXED FEE AND EXTRAS TABLE
In describing the Fixed Fares and Extras, the format of each field is specified as “YYMMDD” (date), “MMDD” (day), “HHMMSS” (time), “D” (fixed decimal),
“AN” alphanumeric or “N” numeric; the latter two formats include an associated field length. The format for decimal has an associated field length and number
of decimal places (e.g. 9.2 is a total length of nine characters with two decimal places).
Note:
Fixed Fares and Extras within this table have been provided as an example only.
MX3
MX4
MX5
20140701
000000
235959
1111111
2.70
Y Start
Example
20140701
000000
235959
1111111
3.00
N Start
Example
20140701
000000
235959
1111111
14.00
N
Durin
g
Example
20140701
000000
235959
1111111
5.30
Y
Durin
g
Example
Amount $ D(5.2)
1
Longitude end
D(10.5)
Comment AN(40)
Example
Longitude start
D(10.5)
Latitude end D(9.5)
N Start
Taxi Services Commission
Level 23, 80 Collins Street, Melbourne VIC 3000
GPO Box 1716, Melbourne VIC 3001 Phone: 1800 638 802 (toll-free) www.taxi.vic.gov.au
July 2013
DOT7670_S061_07/13
Applied at Trip Stage
Start/During/End:
(Start,
During,
End)
Latitude
start D(9.5)
2.00
IsAutoOnly AN(1)
1111111
Usage Cancels:
AN (5), AN (5)…..
235959
Specific Days Only
MMDD, MMDD, ..
000000
To Date YYYYMMDD
20140701
From Date
YYYYMMDD
Applicable Day of
Week N (7)
1000000 = Monday
0000001 = Sunday
0110000 = Tuesday
and Wednesday
Metropolitan
Melbourne,
Frankston,
Dandenong and
Port Phillip
To Time HHMMSS
MX2
Booking
Fee
Airport Fee
Airport
Booking
Fee
High
Occupancy
Charge
CityLink Toll
Charge Western
Link
From Time HHMMSS
MX1
Description AN (40)
Extras Code AN (5)
Zone AN (40)
FIXED FEE AND EXTRAS TABLE
MX9
MX10
MX11
Applied at Trip Stage
Start/During/End:
(Start,
During,
End)
Latitude
start D(9.5)
Durin
g
Example
20140701
000000
235959
1111111
7.80
MX5,
Durin
Y
MX6
g
Example
20140701
000000
235959
1111111
2.68
Y
Durin
g
Example
20140701
000000
235959
1111111
2.53
Y
Durin
g
Example
20140701
000000
235959
1111100
55.00
ALL
N Start
Example
20140701
000000
235959
0000011
45.00
ALL
N Start
Example
20140701
000000
235959
1111111
2.10
N Start
Exam
ple
Amount $ D(5.2)
Longitude end
D(10.5)
Comment AN(40)
Y
Longitude start
D(10.5)
Latitude end D(9.5)
5.30
IsAutoOnly AN(1)
1111111
Usage Cancels:
AN (5), AN (5)…..
235959
Specific Days Only
MMDD, MMDD, ..
000000
To Date YYYYMMDD
20140701
From Date
YYYYMMDD
Applicable Day of
Week N (7)
1000000 = Monday
0000001 = Sunday
0110000 = Tuesday
and Wednesday
MX8
To Time HHMMSS
MX7
CityLink Toll
Charge Southern
Link
Citylink Toll
Charge Both Links
Eastlink Toll
Charge Tunnel
Eastlink Toll
Charge Non-Tunnel
Trip
Fixed Fee Airport to
City Weekdays
Fixed Fee Airport to
City Weekend
From Time HHMMSS
MX6
Description AN (40)
Extras Code AN (5)
Zone AN (40)
FIXED FEE AND EXTRAS TABLE
MX..n
Urban (Geelong
UX1
Booking
Taxi Services Commission
Level 23, 80 Collins Street, Melbourne VIC 3000
GPO Box 1716, Melbourne VIC 3001 Phone: 1800 638 802 (toll-free) www.taxi.vic.gov.au
July 2013
DOT7670_S061_07/13
2
Applied at Trip Stage
Start/During/End:
(Start,
During,
End)
Latitude
start D(9.5)
1111111
3.40
Y Start
Example
UX3
Airport Fee
Holiday Fee
- Christmas
Period
Holiday Fee
- New
Year's Eve
Holiday Fee
- New
Year's Day
20140701
000000
235959
1111111
3.00
N Start
Example
20140701
000000
235959
0
1225,
1226
4.20
UX2
Y Start
Example
20140701
180000
235959
0
1231
4.20
UX2
Y Start
Example
20140701
000000
235959
0
0101
4.20
UX2
Y Start
Example
CX1
Booking
20140701
000000
235959
1111111
2.10
N Start
Example
CX2
Late Night
20140701
000000
060000
1111111
3.40
Y Start
Example
CX3
Airport Fee
Holiday Fee
- Christmas
Period
Holiday Fee
- New
Year's Eve
Holiday Fee
- New
Year's Day
20140701
000000
235959
1111111
3.00
N Start
Example
20140701
000000
235959
0
1225,
1226
4.20
CX2
Y Start
Example
20140701
180000
235959
0
1231
4.20
CX2
Y Start
Example
20140701
000000
235959
0
0101
4.20
CX2
Y Start
Example
UX4
UX6
UX7
Amount $ D(5.2)
Longitude end
D(10.5)
Comment AN(40)
060059
Longitude start
D(10.5)
Latitude end D(9.5)
Applicable Day of
Week N (7)
1000000 = Monday
0000001 = Sunday
0110000 = Tuesday
and Wednesday
000000
IsAutoOnly AN(1)
To Time HHMMSS
20140701
Usage Cancels:
AN (5), AN (5)…..
From Time HHMMSS
Late Night
Specific Days Only
MMDD, MMDD, ..
From Date
YYYYMMDD
UX2
To Date YYYYMMDD
Description AN (40)
Ballarat
Bendigo)
Extras Code AN (5)
Zone AN (40)
FIXED FEE AND EXTRAS TABLE
UX..n
CX4
Country
CX5
CX6
Taxi Services Commission
Level 23, 80 Collins Street, Melbourne VIC 3000
GPO Box 1716, Melbourne VIC 3001 Phone: 1800 638 802 (toll-free) www.taxi.vic.gov.au
July 2013
DOT7670_S061_07/13
3
CXN1
CXN2
DOT7670_S061_07/13
Taxi Services Commission
Level 23, 80 Collins Street, Melbourne VIC 3000
GPO Box 1716, Melbourne VIC 3001 Phone: 1800 638 802 (toll-free) www.taxi.vic.gov.au
July 2013
Price
Notification
- Company
1 Booking
Fee
Price
Notification
- Company
1 Late Night
4
Longitude end
D(10.5)
Comment AN(40)
Longitude start
D(10.5)
Latitude end D(9.5)
Applied at Trip Stage
Start/During/End:
(Start,
During,
End)
Latitude
start D(9.5)
IsAutoOnly AN(1)
Usage Cancels:
AN (5), AN (5)…..
Amount $ D(5.2)
Specific Days Only
MMDD, MMDD, ..
Applicable Day of
Week N (7)
1000000 = Monday
0000001 = Sunday
0110000 = Tuesday
and Wednesday
To Time HHMMSS
From Time HHMMSS
To Date YYYYMMDD
From Date
YYYYMMDD
Description AN (40)
Extras Code AN (5)
Zone AN (40)
FIXED FEE AND EXTRAS TABLE
CX..n
2.05
N Start
Example
3.30
Y Start
Example
APPENDIX H – ALARM CODES
AlarmCode
Alarm Description
1
External Power Supply disconnected
2
External Power Supply reconnected
3
Unauthorised access to data in Fare Device detected
4
Unauthorised access to Fare Device software detected
5
GPS antenna disconnected from IVU
6
GPS antenna reconnected to IVU
7
Disconnection of the Speed and Distance Sensor
8
Reconnection of the Speed and Distance Sensor
APPENDIX I – AUDIO ANNOUNCEMENTS
1. When Hire On is selected from hired off, the Fare Device shall audibly convey the
following:
“Your Driver’s Accreditation number is <Drivers Accreditation Number>. This Vehicle
is number <Vehicle ID>.”
2. When Hire Off is selected from hire paused, the Fare Device shall audibly convey
the following:
“Your Driver’s Accreditation number is <Drivers Accreditation Number>. This Vehicle
is number <Vehicle ID>.”
“The Total Fare for your Trip is <Total Fare>. This consists of a Metered Fare of
<value of Metered Fare>, Extras totalling <total value of Extras>, less the MPTP
Member Subsidy (if applicable) of <value of MPTP Member Subsidy>.”
APPENDIX J – ERROR MESSAGES FOR MPTP
MEMBER SMARTCARD PROCESSING
1. The Fare Device shall have the ability to visually display and audibly convey the following
MPTP-related data:
a. Where the MPTP Member Smartcard has expired, the Fare Device shall visually
display and audibly convey:
Taxi Services Commission
Level 23, 80 Collins Street, Melbourne VIC 3000
GPO Box 1716, Melbourne VIC 3001 Phone: 1800 638 802 (toll-free) www.taxi.vic.gov.au
July 2013
DOT7670_S061_07/13
1
“CARD EXPIRED.”
or other words as approved by the Administrator that communicate an equivalent
message.
b. Where the MPTP Member Smartcard is disabled, the Fare Device shall visually
display and audibly convey:
“CARD CANCELLED.”
or other words as approved by the Administrator that communicate an equivalent
message.
c.
Where the member’s subsidy cap has been reached the Fare Device shall visually
display and audibly convey:
“SUBSIDY CAP $99999
SUBSIDY USED $99999.”
or other words as approved by the Administrator that communicate an equivalent
message.
d. Where the MPTP Member Smartcard is faulty, the Fare Device shall visually display
and audibly convey:
“CARD FAULTY RETURN CARD TO THE TSC.”
or other words as approved by the Administrator that communicate an equivalent
message.
e. Where the Fare Device’s MPTP facility is not functioning, the Fare Device shall
visually display and audibly convey:
“SYSTEM ERROR CONTACT THE TSC”
or other words as approved by the Administrator that communicate an equivalent
message.
f.
Where the card is not an MPTP Member Smartcard, the Fare Device shall visually
display and audibly convey:
“NOT A VALID CARD. REMOVE CARD.”
or other words as approved by the Administrator that communicate an equivalent
message.
APPENDIX K – SMARTCARD SPECIFICATIONS
Driver Smartcard and MPTP Member Smartcard specifications.
Taxi Services Commission
Level 23, 80 Collins Street, Melbourne VIC 3000
GPO Box 1716, Melbourne VIC 3001 Phone: 1800 638 802 (toll-free) www.taxi.vic.gov.au
July 2013
DOT7670_S061_07/13
2