telematics business-to- telematics business-to ... - tca

www.tca.gov.au

Telematics Business-to-Business Data Exchange

Functional and Technical Specification Version 2.2

For Application Service Providers

TELEMATICS BUSINESS-TO-BUSINESS DATA EXCHANGE

www.tca.gov.au

JANUARY 2021

http://www.tca.gov.au/

www.tca.gov.au TCA-S11-2.2

i

© Transport Certification Australia Limited 2021.

This document has been published by Transport Certification Australia Limited.

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 Ltd T +61 3 8601 4600 E [email protected] W www.tca.gov.au

ABN 83 113 379 936

Document Details

Title Telematics Business-to-Business Data Exchange Functional and Technical Specification Document Number TCA-S11 Version 2.2 Version Date January 2021 Printing Instructions Colour printing, double-sided

Document History Version Date Description 1.0 July 2018 First published version, excluding Tier 1 Data Exchange. Content originally included in the Operating Model of the IAP

(i.e. National Telematics Framework), as defined in the first publication of the IAP Functional and Technical Specification (2006).

2.0 May 2019 Update to terminology throughout document; inclusion of Tier 1 Data Exchange; update to TDE Business Data Model, Tier 2 enrolment, enrolment models, XML schemas, data model diagrams, module names and file type extensions; and inclusion of form and report representations.

2.1 September 2019 Replaced ‘User’ with ‘Operator’, and ‘Producer’ with ‘Authority’. Added a Speed field to the Position Record Data Model. Added optional fields to Enrolment Form Data Model. Removed XML as a data extension option for the bulk transfer file system directory. Updated schemas in Appendices B, C and F, and updated UML diagrams accordingly.

2.2 August 2020 Replaced ‘telematics in-vehicle unit’ with ‘telematics device’, noting the former term continues to be used in the Intelligent Access Program. Added Positioning Service Availability field to data models for position and speed records, and updated associated schemas in Appendices B, C and E. Added optional fields Model and SRS (spatial reference system datum) at the ‘data record set’ level, and updated associated schemas in Appendices B and C, Table 3 and the Data Records Package Data Model. Minor editorial amendments.

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™, National Telematics Framework™, TCA Certified™, TCA Type-Approved™, Intelligent Access Program™, IAP®, IAP Service Provider™, IAP-SP™, In-Vehicle Unit™, IVU™, On-Board Mass™ OBM™, Telematics Monitoring Application™, TMA™, Road Infrastructure Management ™, RIM™, Intelligent Mass Monitoring™, IMM™, Intelligent Mass Assessment™, IMA™, Intelligent Location Monitoring™ and ILM™ are trademarks of Transport Certification Australia Limited.

This document is Commercial-in-Confidence


ii TCA-S11-2.2

www.tca.gov.au

ABOUT US

Transport Certification Australia (TCA) is a national organisation that provides assurance services relating to transport technologies and data to enable improved public purpose outcomes from road transport.

Priority outcome areas enabled by TCA services include improved road safety, transport efficiency, freight productivity, asset management and sustainability.

Key aspects of TCA include:

• An independent not-for-profit entity, with government oversight

• Administration of the National Telematics Framework, including its rules, specifications, agreements, digital infrastructure and other supporting services

• Assurance services that support but are appropriately separated from regulators, policy makers and enforcement activities, and underpin telematics applications and associated information and data services

• Advice that is based on evidence and a deep subject matter knowledge

• Trusted partner to both government and industry stakeholders, enabling a nationally consistent open market, with services covering all road vehicle types and associated digital infrastructure.



iii

Contents

1 INTRODUCTION ............................................................................................................... 1 1.1 Purpose of this Document ...................................................................................... 1 1.2 Nomenclature ......................................................................................................... 1 1.3 Comments and Feedback ...................................................................................... 1

2 BACKGROUND ................................................................................................................ 2 2.1 The National Telematics Framework ...................................................................... 2 2.2 National Telematics Framework – High-Level Architecture .................................... 2 2.3 Telematics Data Exchange Ecosystem .................................................................. 4 2.4 Data Exchange Tiers .............................................................................................. 5 2.5 IAP-Specific Terms and Corresponding NTF Terms .............................................. 7 2.6 Business Architecture of Telematics Applications .................................................. 8 2.7 Telematics Data Exchange Information Flows ..................................................... 11 2.8 Data Record Structure and Terminology .............................................................. 13

3 REFERENCES ................................................................................................................ 14

4 BUSINESS DATA MODEL AND ENCODING ................................................................. 15 4.1 Purpose ................................................................................................................ 15 4.2 Structure and Organisation of Business Data Model ............................................ 15 4.3 Data Records Data Model Package ..................................................................... 16 4.4 Common Data Model Package ............................................................................ 18 4.5 Conditions Data Model Package .......................................................................... 20 4.6 Enrolment Data Model Package ........................................................................... 22 4.7 Event Report Data Model Package ...................................................................... 34 4.8 Enrolment Report Data Model Package ............................................................... 36 4.9 Data Reporting Data Model Package ................................................................... 39 4.10 Data Exchange Formats and Encoding ................................................................ 40 4.11 XML Formatting .................................................................................................... 42 4.12 JSON Formatting ................................................................................................. 42

5 TIER 1 DATA EXCHANGE .............................................................................................. 43 5.1 Purpose of Tier 1 Data Exchange ........................................................................ 43 5.2 Overview of Tier 1 Data Exchange ....................................................................... 44 5.3 Notify Enrolment Service ...................................................................................... 46 5.4 Request Enrolment Service .................................................................................. 46 5.5 Request Enrolment Approval Service ................................................................... 46 5.6 Request Enrolment Replacement Service ............................................................ 47 5.7 Request Enrolment Cancellation Service ............................................................. 47 5.8 Notify Rejection Service ....................................................................................... 47 5.9 Notify Event Report Service ................................................................................. 48 5.10 Notify Enrolment Report Service .......................................................................... 48


iv TCA-S11-2.2

www.tca.gov.au

5.11 Notify Data Records Service ................................................................................ 48 5.12 Notify Data Report Service ................................................................................... 48 PART A: TIER 1 DATA EXCHANGE REQUIREMENTS ................................................ 49 A.1 Standards and Interoperability ............................................................................. 49 A.2 Network Security .................................................................................................. 49 A.3 RESTful Service Implementation ......................................................................... 50 A.4 Tier 1 Data Exchange Formats and Encoding ...................................................... 52 A.5 Tier 1 Data Exchange Digital Signatures .............................................................. 53 A.6 Logging ................................................................................................................ 53 A.7 Resource Discovery and Identity Management .................................................... 54

6 TIER 2 DATA EXCHANGE .............................................................................................. 55 6.1 Purpose of Tier 2 Data Exchange ........................................................................ 55 6.2 Tier 2 Communication Methods ........................................................................... 55 PART B: TIER 2 DATA EXCHANGE REQUIREMENTS ................................................ 56 B.1 Tier 2 Secure Email .............................................................................................. 56 B.2 Tier 2 Registered Mail .......................................................................................... 56 B.3 Tier 2 Secure Web Portal ..................................................................................... 56 B.4 Tier 2 FTPS .......................................................................................................... 57 B.5 Tier 2 Data Exchange Formats and Encoding ...................................................... 57 B.6 Tier 2 Logging ...................................................................................................... 58

7 TIER 3 DATA EXCHANGE .............................................................................................. 59 7.1 Purpose of Tier 3 Data Exchange ........................................................................ 59 7.2 Tier 3 Communication Methods ........................................................................... 59 PART C: TIER 3 DATA EXCHANGE REQUIREMENTS ................................................ 60 C.1 Data Reporting ..................................................................................................... 60 C.2 Data Selection ...................................................................................................... 60 C.3 Enrolment Form Data ........................................................................................... 61 C.4 Event Report Data ................................................................................................ 61 C.5 Enrolment Report Data......................................................................................... 61 C.6 Data Record Data ................................................................................................ 61 C.7 Data Reporting Manifest Data .............................................................................. 62 C.8 Tier 3 Data Exchange Formats and Encoding ...................................................... 63 C.9 Progressive Transfer Method ............................................................................... 63 C.10 Bulk Transfer Method ........................................................................................... 64 C.11 Tier 3 Data Exchange Digital Signatures .............................................................. 66

APPENDIX A ACRONYMS AND DEFINITIONS ................................................................ A-1 Acronyms ...................................................................................................................... A-1 Definitions ...................................................................................................................... A-2

APPENDIX B TELEMATICS DATA EXCHANGE XML SCHEMAS ................................... B-1 IAP XML Schemas ........................................................................................................ B-1



v

Common Types Schema ............................................................................................... B-1 Data Records Schema................................................................................................... B-8 Conditions Schema ..................................................................................................... B-19 Enrolment Schema ...................................................................................................... B-23 Event Report Schema ................................................................................................. B-30 Enrolment Report Schema .......................................................................................... B-34 Data Report Schema ................................................................................................... B-37

APPENDIX C TELEMATICS DATA EXCHANGE JSON SCHEMA ................................... C-1 Overview ....................................................................................................................... C-1 Telematics Data Exchange JSON Schema ................................................................... C-1

APPENDIX D TELEMATICS DATA EXCHANGE RESTFUL API ...................................... D-1 Overview ....................................................................................................................... D-1 Notify Enrolment ............................................................................................................ D-1 Request Enrolment ........................................................................................................ D-1 Request Enrolment Approval ......................................................................................... D-2 Request Enrolment Replacement .................................................................................. D-2 Request Enrolment Cancellation ................................................................................... D-3 Notify Response ............................................................................................................ D-3 Notify Event Report ....................................................................................................... D-4 Notify Enrolment Report ................................................................................................ D-4 Notify Data Records ...................................................................................................... D-5 Notify Data Report ......................................................................................................... D-5

APPENDIX E DATA RECORD REFERENCE ................................................................... E-1 Overview ....................................................................................................................... E-1 Contents ........................................................................................................................ E-1 Alarm Record Data Model ............................................................................................. E-2 Position Record Data Model .......................................................................................... E-3 Speed Record Data Model ............................................................................................ E-5 SD (Comments) Record Data Model ............................................................................. E-6 SD (Vehicle Type/TCM) Record Data Model ................................................................. E-7 Transfer Record Data Model ......................................................................................... E-8 Mass Record Data Model .............................................................................................. E-9 Mass Configuration Record Data Model ...................................................................... E-11 Mass Quality Record Data Model ................................................................................ E-12 Mass Alarm Record Data Model .................................................................................. E-13

APPENDIX F BUSINESS DATA MODEL MODULES AND SUPPRTING SCHEMAS ...... F-1 Overview ....................................................................................................................... F-1 Common – IAP Module.................................................................................................. F-2 Common – Mass Module ............................................................................................... F-3 Conditions – IAP Module ............................................................................................... F-5


vi TCA-S11-2.2

www.tca.gov.au

Conditions – Mass Module .......................................................................................... F-12 Enrolment Form – IAP Module .................................................................................... F-15 Enrolment Form – Mass Module .................................................................................. F-19 Event Report – IAP Module ......................................................................................... F-22 Event Report – Mass Module ...................................................................................... F-28

Enrolment Report – IAP Module .................................................................................. F-33 Enrolment Report – Mass Module ............................................................................... F-34

APPENDIX G FORM AND REPORT REPRESENTATIONS .............................................. G-1 Overview ....................................................................................................................... G-1 Enrolment Form ............................................................................................................. G-2 Event Report.................................................................................................................. G-8 Enrolment Report ........................................................................................................ G-11



1

1 INTRODUCTION

1.1 Purpose of this Document

1.1.1 This specification describes the standard methods and mechanisms for business-to-business (B2B) data exchange within the telematics applications of the National Telematics Framework (NTF), and the standard business documents and reporting artefacts that are exchanged. This specification therefore provides for interoperability and consistency in the deployment and usage of telematics applications.

1.1.2 This specification specifies the following data exchange mechanisms:

• Tier 1 Data Exchange: A web services solution where structured information is exchanged that complies with requirements such as authentication, security, privacy and certainty of delivery. It includes exchanges of information related to a vehicle’s enrolment in telematics applications, conditions and adherence to those conditions.

• Tier 2 Data Exchange: The human-initiated (rather than automated) exchange of business-related information and advice. Typical exchanges via this tier include reporting of issues and resolutions, correspondence regarding certification and re-certification, advice regarding information and communications technology (ICT), data assurance and other reporting.

• Tier 3 Data Exchange: The packaging and delivery of data packages, comprising data records and enrolment-related artefacts. Data packages have several uses which include data analysis by the recipient, data assurance, and for research purposes.

1.1.3 In addition, this specification describes the data model and formatting for all NTF data records, and for standard business documents and reporting artefacts that are exchanged by NTF participants.

1.2 Nomenclature

1.2.1 Requirements clauses within this specification that are denoted by:

• ‘shall’ are requirement that must be met;

• ‘should’ are requirements that should desirably be met;

• ‘may’ are requirements that are optional; and

• ‘will’ are obligations that will be met by other parties.

1.2.2 Notes are included by way of clarification and apply to the immediately preceding requirement.

1.3 Comments and Feedback

1.3.1 TCA welcomes your feedback on improvements to future editions of this specification. Please send any comments or suggestions to [email protected].


mailto:[email protected]

2 TCA-S11-2.2

www.tca.gov.au

2 BACKGROUND

2.1 The National Telematics Framework

2.1.1 The National Telematics Framework is a digital business platform with infrastructure and rules that aims to ensure an open marketplace of telematics and related intelligent technology providers.

2.1.2 The National Telematics Framework:

• provides a national platform for the use of telematics and related intelligent technologies;

• supports a number of applications across regulatory, contractual and commercial needs;

• supports different levels of assurance; and

• is outcome focussed and encourages innovation.

2.1.3 The National Telematics Framework was established following a series of decisions made by Responsible Ministers between 2003 and 2008, and was globally recognised as an International Standard (ISO 15638) in 2012.

2.2 National Telematics Framework – High-Level Architecture

2.2.1 Telematics B2B data exchange occurs within the context of the NTF. The high-level architecture of the NTF is illustrated in Figure 1.

Figure 1: NTF High-Level Architecture

Applications

Levels of Assurance

Business Rules

Analysis

Processing

Devices

Business Data



3

2.2.2 The architectural components of the NTF are as follows:

a. Applications – An application is a capability of the NTF that provides business value to stakeholders, delivered as an assembly of policy, business components and technical components, within the context of an intended level of assurance.

b. Levels of Assurance – Each level of assurance is determined by the intended use of a telematics application, the risks being managed, the availability and reliability of supporting contextual information, and the needs and expectations of consumers and other stakeholders. Three broad levels of assurance have been defined:

• Level 1: Self-assessment of data and no independent oversight of a telematics application.

• Level 2: Independent assessment of specific elements of a telematics application. Telematics data is combined with other data sources.

• Level 3: Certificate-based data and evidence. Independent assessment and oversight of all aspects of a telematics application and service provision.

For more information, refer to National Telematics Framework – Levels of Assurance.

c. Business Rules – A common set of business rules that ensure an open, robust, secure and interoperable marketplace of providers, and meet the requirements for defined levels of assurance (including evidentiary requirements associated with regulatory requirements).

For more information, refer to National Telematics Framework – Business Rules. d. Business Data – Data elements that are common to data analysis, processing and

telematics devices, which include the Telematics Data Dictionary and the National Telematics Map (NTM).

e. Analysis – Advanced analysis of data and information related to telematics devices and applications.

f. Processing – Processing components concerned with (generally) automated service provider functionality, comprising a framework of business domain documents.

g. Devices – Individual telematics capabilities that are typically able to exist independently, or within the context of broader telematics-based solutions. Each device or technology collects a defined set of data which is packaged in the form of data records.

2.2.3 Telematics Data Exchange facilitates the exchange of application data between NTF participants. It supports the delivery of applications as a composition of components from within this NTF architecture.


4 TCA-S11-2.2

www.tca.gov.au

2.3 Telematics Data Exchange Ecosystem

2.3.1 This specification defines the communications interfaces for B2B communication of telematics data and information between an Application Service Provider (ASP) and trading partners, as shown on the right-hand section of Figure 2. Examples of ASP trading partners include TCA, Authorities (or administrators appointed to perform Authority functions), other service providers and other commercial entities.

2.3.2 Figure 2 provides an overview of the environments within which telematics data and information is exchanged.

Figure 2: Telematics Data Exchange Environments

Connected Vehicle

Telematics Device

Data Service

Connected Device

Connected Device

GNSS

Application Service Provider

Trading PartnerRoadside Infrastructure

Trading Partner

Connected Vehicle

Mobile Device(e.g. TCA, Authority, Service Provider, other commercial entity)

Business-to-Business

Device-to-Device

2.3.3 For more information on the communications interface for the connection of a system or

device with a telematics device, refer to Interconnectivity of Telematics Device with Other Systems Functional and Technical Specification.

Note: The telematics device is the primary telematics unit which monitors parameters. In the Intelligent Access Program (IAP), the telematics device is referred to as the ‘telematics in-vehicle unit’.

2.3.4 Data and information are sent and received in different ways, using different levels of security and assurance (refer to Levels of Assurance), depending upon the type of data and information that is being sent.



5

2.3.5 Mechanisms for B2B data and information exchange are classified into three distinct tiers, referred to as Tier 1 Data Exchange, Tier 2 Data Exchange and Tier 3 Data Exchange.

2.3.6 Each trading partner must implement the data exchange tier(s) within the TDE B2B environment required by the telematics application(s) they support.

2.3.7 The choice to use one tier of data exchange over another for particular data or information may depend upon the level of assurance required, the attributes of the data to be exchanged and/or the volume of information. For example, information related to a telematics application enrolment may be transferred via Tier 1 or Tier 2 Data Exchange, depending on the requirements of the application.

2.3.8 An application may require that certain actions are completed using a specific data exchange tier. This depends on the level of assurance provided by that application.

2.4 Data Exchange Tiers

2.4.1 Tier 1 Data Exchange (Figure 3) is a web services solution where structured information is exchanged that complies with requirements such as authentication, security, privacy and certainty of delivery. It includes exchanges of information related to a vehicle’s enrolment in telematics applications, conditions and adherence to those conditions.

Figure 3: Tier 1 Data Exchange


Trading Partner

Web Service

Information, reports related to telematics applications, conditions and adherence

Server Server


6 TCA-S11-2.2

www.tca.gov.au

2.4.2 Tier 2 Data Exchange (Figure 4) is the human-initiated (rather than automated) exchange of business-related information and advice. Typical exchanges via this tier include reporting of issues and resolutions, correspondence regarding certification and re-certification, advice regarding information and communications technology (ICT), data assurance and other reporting. This occurs via secure email, registered mail, a web or API interface, or secure file transfer protocol.


Trading Partner

FTPS Registered Mail

Secure Web Interface

Information, reportsApplication Service Provider

Secure Email

Business Administrator

Business Administrator

2.4.3 Tier 3 Data Exchange (Figure 5) refers to the packaging and delivery of data packages, comprising data records and enrolment-related artefacts. Data packages have several uses which include data analysis by the recipient, data assurance, and for research purposes.



Trading PartnerData Packages

FTPSServer ServerWeb Service



7

2.5 IAP-Specific Terms and Corresponding NTF Terms

2.5.1 Terminology associated with NTF entities and artefacts was initially designed for use with the Intelligent Access Program (IAP).

2.5.2 Aspects of the business and operational architecture of telematics applications have been retained in keeping with the IAP. This provides a level of compatibility with existing implementations. Refer to Table 1 for IAP-specific terms and their corresponding NTF terms used within this specification.

Table 1: IAP-Specific Terms and Corresponding NTF Terms

IAP-Specific Term NTF Term

Jurisdiction Authority

Intelligent Access Condition (IAC)-issuing Jurisdiction

Authority

Transport Operator Operator

IAP-Service Provider (IAP-SP) Application Service Provider (ASP)

IAP Application scheme

Intelligent Access Condition (IAC) enrolment form

Non-Compliance Report (NCR) event report

Participants Report (PR) enrolment report

Note:

i. Wherever a requirement states responsibility for an Authority, it includes responsibility for any administrator that may have been appointed by the Authority to perform its functions.

ii. Refer to the Definitions table in Appendix A for the NTF distinction made between the terms ‘Jurisdiction’ and ‘Authority’. In the NTF, ‘jurisdiction’ is used only for the geographical area containing a road network (i.e. typically an Australian state or territory).


8 TCA-S11-2.2

www.tca.gov.au

2.6 Business Architecture of Telematics Applications

2.6.1 The NTF comprises applications that each deliver discrete business capability to stakeholders. A telematics application is classified as a monitoring application or an assessment application, as described in 2.6.4 and 2.6.6.

2.6.2 The business architecture of a monitoring application is shown in Figure 6.

Figure 6: Business Architecture of a Monitoring Application

obtains

Authority

Application

Operator

EnrolmentScheme

publishes

enrols inrequires enrolment

in

1

1...N

1...N

1

1

ASPTCA

National Telematics Framework

manages

1...N

Vehicle

operates

1...N

2.6.3 The business architecture of an assessment application is shown in Figure 7.

Figure 7: Business Architecture of an Assessment Application

obtains

Authority

Application

Operator

Enrolment

Operating Conditions

Scheme

publishes identifies

enrols in

requires enrolment

in

1

1...N

1...N

1...N

1...N

11

1 0...1

Event

ASPTCA

Off-the-Shelf Conditions

includes

(one of)

references

includes

0...1

1

1...N

reported to

National Telematics Framework

manages

1...N

Vehicle

operates

1...N

1...N



9

2.6.4 A monitoring application provides all collected data to TCA for analysis on behalf of the Authority. For an assessment application, the ASP processes collected data against a set of operating conditions specified by the Authority, reporting only events related to those operating conditions to the Authority.

2.6.5 A monitoring application is a telematics application where vehicles are enrolled in a scheme and monitored via installed type-approved telematics devices, with data records transferred to the ASP back office. The following apply:

• no operating conditions are specified, and no event reports are generated or provided to the Authority; and

• data packages containing relevant collected data and enrolment reports are provided via Tier 3 Data Exchange to TCA for processing.

2.6.6 An assessment application is a telematics application where vehicles are enrolled in a scheme and monitored via installed type-approved telematics devices, with data records transferred to the ASP back office. The following apply:

• operating conditions are specified, and vehicle data is assessed against these operating conditions to generate event reports (including alarm event reports);

• enrolment reports and event reports are provided to the Authority via Tier 1 Data Exchange; and

• all data pertaining to the application is provided to TCA via Tier 3 Data Exchange.

Note: Any application that is neither a monitoring application nor assessment application is out of scope of this version of this document, and will not use business documents described in this specification

2.6.7 Refer to Table 2 for a description of key particpants in telematics applications:

Table 2: Application Participants

Name Description

Authority

An Authority develops and publishes schemes which utilise a telematics application. A scheme is a specific use of the application linked to delivering a policy objective of the Authority. Each enrolment of a vehicle in the application must specify a scheme.

Note: An Authority is associated with a jurisdiction, which is a geographical area containing a road network.

An Authority may appoint an administrator to perform its functions. If delegation occurs, it applies across all schemes published by the Authority for a given application.

Note: Wherever a requirement states an operational responsibility for an Authority, it includes responsibility for any administrator that may have been appointed by the Authority to perform its functions.

Each scheme requires that vehicles enrol in a specific telematics application to ensure telematics monitoring and/or assessment of vehicle operation associated with the application.

An Operator operates one or more vehicles eligible to enter a scheme requiring a telematics application.


10 TCA-S11-2.2

www.tca.gov.au

Name Description

Operator An Operator may apply to enrol vehicles within a scheme by meeting the necessary conditions or agreements. The enrolment conditions or agreements require an Operator to utilise the services of an ASP in order to participate in a scheme offered by an Authority. Enrolment within a scheme simultaneously confirms enrolment in the application required by that scheme.

Note: In NTF documents, Operator is referred to as ‘consumer’.

Application

Service Provider (ASP)

An ASP is a private-sector entity that provides telematics services (e.g. hardware, software and associated processes) and is certified or approved by TCA for participation in one or more telematics applications (each subject to separate certification or approval assessments for service provision).

An ASP is responsible for installation of telematics devices and any other technologies required by applications, monitors vehicles in accordance with the application, and provides the level of assurance sought by Authorities .

• For a monitoring application, the ASP monitors vehicles via data sent by the telematics device to the ASP back office.

• For an assessment application, the ASP additionally assesses vehicle data against operating conditions, and identifies and reports any subsequent events.

Periodically the ASP summarises (in a report) the operation of all vehicles enrolled in the schemes operated by each Authority for the application, and makes this enrolment report available to the Authority and TCA.

Note: In NTF documents, ASP is referred to as ‘provider’.

TCA

TCA has oversight of all NTF applications, including their publishing, maintenance, data assurance and auditing (if required), and ensures they continue to operate in accordance with the NTF. Oversight includes certification of ASPs and the type-approval of telematics devices. Reporting and program coordination activities are undertaken in line with the Authority’s needs.



11

2.7 Telematics Data Exchange Information Flows

2.7.1 For monitoring applications, data and information flow between devices, ASPs and recipients as shown in Figure 8.

Figure 8: TDE Information Flows – Monitoring Application

Data Packages

Recipients

TDE

ASP

Tier 2 Tier 3

Operational Communication

EnrolmentReport

Enrolment Form

Tier 1 Tier 2

Note: Enrolment forms and enrolment reports should be sent via the highest mutually supported data exchange tier, or as specified by the application.

2.7.2 For assessment applications, data and information flow between devices, ASPs and recipients as shown in Figure 9.

Figure 9: TDE Information Flows – Assessment Application

Data Packages

Recipients

TDE

ASP

Tier 1 Tier 2 Tier 3

Operational Communication

EnrolmentReport

Enrolment Form

Off-the-Shelf Conditions

Event Report


12 TCA-S11-2.2

www.tca.gov.au

2.7.3 The business documents and reporting artefacts shown in Figure 8 and Figure 9 are defined as follows:

• off-the-shelf conditions – a set of operating conditions that is published by an Authority and that can be referenced in one or more enrolment forms;

• enrolment form – enrolment of a vehicle within a scheme (and by implication, enrolment within a telematics application), including attributes that affect applicability of enrolment (e.g. according to vehicle configuration);

• event report – report of an event identified through processing of vehicle telematics data in the context of a vehicle enrolment and any associated operating conditions;

• enrolment report – summary of enrolments relevant to a given Authority for a specified reporting period, including any aggregated data required by the application;

• data package – a summary of a package of data records and enrolment-related artefacts exchanged via Tier 3 Data Exchange.

2.7.4 The enrolment form describes key information about participation in a scheme. This includes several concepts detailing which information is provided and to whom:

• scheme name – links the enrolment to a specific scheme governing it;

• application name – links the telematics application required to support the scheme;

• application class – derived from the application name, describes the level of functionality of the telematics application as either:

o Monitoring – contains no operating conditions and requires delivery of relevant information via Tier 3 for processing; or

o Assessment – contains operating conditions assessed by the ASP with reporting occurring via Tier 1;

• operating conditions – the detailed condition set specifying the conditions that the participant in the scheme must adhere to.

2.7.5 A unique enrolment form is required for each combination of:

• Authority;

• vehicle;

• equipment;

• Operator;

• scheme; and

• ASP.

Note: A separate enrolment form is required for each distinct combination of these attributes. If any of these attributes change for an enrolment, the enrolment is no longer valid, and must be cancelled and reissued with the new details.



13

2.7.6 TCA holds, maintains and issues the master copy of trading partner details that all ASPs must reference, including support for various applications. This provides each trading partner the details needed to connect to each other via the data exchange tiers.

2.7.7 The standard format for business documents listed in 2.7.3 is XML version 1.0.

2.8 Data Record Structure and Terminology

2.8.1 Any record that originates from and is generated by a telematics device is referred to as a telematics device data record, as shown in Figure 10.

2.8.2 Any record generated by a connected device is called a connected device data record.

2.8.3 A connected device data record is a record that originates from a connected device and is sent to the telematics device. The telematics device may contain this within a data record, called a transfer data record, for transfer to the ASP back office.

Note: A transfer data record is a telematics device data record which contains content that originates from a connected device.

Figure 10: Data Record Structure and Terminology

Connected Device

Content

Telematics Device Data Record

Content

Transfer Data Record

Telematics Device

Connected Device Data Record

Content

Content


Connected Device Data Record

Telematics Device


contains


14 TCA-S11-2.2

www.tca.gov.au

3 REFERENCES

3.1.1 Documents referenced in this specification are listed below:

• Transport Certification Australia (TCA). (2020). Interconnectivity of Telematics Device with Other Systems Functional and Technical Specification. Transport Certification Australia. Melbourne, Australia.

• Transport Certification Australia (TCA). (2018). Intelligent Access Program Functional and Technical Specification. Transport Certification Australia. Melbourne, Australia.

• Transport Certification Australia (TCA). (2018). National Telematics Framework – Levels of Assurance. Transport Certification Australia. Melbourne, Australia.

• Transport Certification Australia (TCA). (2018). National Telematics Framework – Business Rules. Transport Certification Australia. Melbourne, Australia.

• Transport Certification Australia (TCA). (2018). Telematics Data Dictionary. Transport Certification Australia. Melbourne, Australia.

• [HTTP] Hypertext Transport Protocol 1.1, IETF RFC 2616, June 1999.

• [TLS] The Transport Layer Security (TLS) Protocol 1.2, IETF RFC 5246, August 2008.

• [CMS] Cryptographic Message Syntax, IETF RFC 5662, September 2009.

• [S/MIME] Secure/Multipurpose Internet Mail Extensions (S/MIME), IETF RFC 5751, January 2010.

• [BASE64] The Base16, Base32, and Base64 Data Encodings, IETF RFC 4648, October 2006.

• [XSLT] XSL Transformations (XSLT) 2.0 (Second Edition), W3C Proposed Edited Recommendation, 21 April 2009.



15

4 BUSINESS DATA MODEL AND ENCODING

4.1 Purpose

4.1.1 Telematics Data Exchange specifies two key aspects of telematics applications within the NTF:

• the business data model (and associated formats and encodings) supporting the standard business documents and reporting artefacts; and

• the data exchange mechanisms used to transfer those electronic business documents and data reporting artefacts between participants.

4.1.2 Both aspects are designed to support a variety of applications within the NTF by having sufficient flexibility to meet the differing requirements of each application (for example, supporting different enrolment workflows), and sufficient rigour to have consistency between applications in areas of commonality.

4.1.3 This section provides an overview of the structure and organisation of the TDE Business Data Model, a detailed description of each significant business document and reporting artefact, and technical details of the formatting and encoding of the Business Data Model.

4.2 Structure and Organisation of Business Data Model

4.2.1 The TDE Business Data Model is best understood in the context of the business architecture of telematics applications, as discussed in Section 2.6.

4.2.2 TDE business documents and data reporting artefacts are organised into packages that are aligned with significant business domain entities and processes. As shown in Figure 11, the TDE Business Data Model packages are either:

• core packages – which define the standard business documents and reporting artefacts used across all telematics applications; or

• module packages – which define additional and application-specific data elements or constructs at defined extension points identified within the core packages, and which cannot define new business documents or data reporting artefacts.

Figure 11: Data Model Schema Packages

Module

Conditions Enrolment Event Report

Enrolment ReportCommon

Module

Conditions Enrolment Event Report

Enrolment ReportCommon

Core

Common Conditions EnrolmentEvent

ReportData

RecordsEnrolment

ReportData

Reporting


16 TCA-S11-2.2

www.tca.gov.au

4.2.3 The TDE core packages are:

• data records (see 4.3) - the comprehensive definition of all data records used by the telematics applications of the NTF;

• common (see 4.4) – miscellaneous data structures, data types and enumerated values that are shared between all business documents and data reporting artefacts;

• conditions (see 4.5) – artefacts supporting specification of operating conditions, whether these are published as an off-the-shelf conditions document (also defined within this package), or as unique conditions within an enrolment form;

• enrolment (see 4.6) – artefacts supporting application-specific and flexible workflows for enrolment of a vehicle within a scheme and within an application, notably including the enrolment form;

• event report (see 4.7) – artefacts supporting identification and reporting of an event associated with the operation of an enrolled vehicle, including the assessment of telematics data against specific operating conditions;

• enrolment report (see 4.8) – artefacts supporting summary reporting of the enrolment of vehicles; and

• data reporting (see 4.9) – artefacts for periodic reporting of application data by the ASP to TCA via Tier 3 Data Exchange.

4.2.4 The TDE modules as specified in Appendix F are:

• iap – extends the TDE core with artefacts to support the IAP application, and that are applicable to other applications that encompass parameters of speed, location and time; and;

• mass – extends the TDE core and the packages within the iap module with artefacts to support the Intelligent Mass applications, and that are applicable to other applications that encompass parameters of mass and configuration.

4.2.5 Associated with each artefact within the TDE Business Data Model are business rules and constraints that guide the definition of workflows for the artefact.

4.3 Data Records Package Data Model

4.3.1 The data records package defines the data model for all data records used across all the telematics applications of the NTF, including all data elements required by any of those applications. Each application then identifies which of the defined data records and data elements apply to it, and which of the applicable data elements are mandatory.

4.3.2 The schemas for this package deliberately have no dependencies on other packages, and thus can be used independently for data record validation.

4.3.3 The high-level structure and contents of the data records package data model are illustrated in Figure 12.



17

Figure 12: Data Records Package Data Model

4.3.4 The significant data types within the data records package are listed in Table 3.

Table 3: Data Records Package – Significant Data Types

Data Type Description

Device Data Record An abstract data type from which all data records extend, and that includes core data elements including record date and time

Position Record The position record

Speed Record The speed record

Alarm Record The alarm record

SD (Comment) Record The SD (comment) record

SD (Vehicle Type/TCM) Record The SD (vehicle type/TCM) record

OBM System Data Record An abstract data type from which all OBM system data records extend, and that includes data elements common to all OBM system data records

OBM System Mass Record The OBM system mass record. Each instance may include one or more MSU sub-records

OBM System Configuration Record

The OBM system configuration record. Each instance may include one or more MSU sub-records

OBM System Quality Record The OBM system quality record


18 TCA-S11-2.2

www.tca.gov.au


OBM System Alarm Record The OBM system alarm record

Transfer Data Record The transfer record – used by the telematics device to transfer a connected device data record to the ASP

Received Data Record A wrapper around a data record received from the telematics device that includes the receipt date and time

Device Identity The identity of a device, comprising a unique identifier and optionally device type and device model. Most notably this is used to capture the telematics device that generated data records.

Data Record Set A group of received data records from a single telematics device, nominally for data records generated on a single UTC date (see C.6.2). Optionally, the data record set specifies the Spatial Reference System (SRS) datum used to record vehicle position (e.g. GDA94).

Data Record Batch A group of received data records from multiple telematics devices, nominally for data records generated on a single UTC date (see C.6.2). The data record batch includes a unique batch identifier.

4.3.5 The data records package data model is supported by the XML schema tde_core_data-record_2018-07.xsd (see Appendix B), and the JSON schema tde_core_data-record_2018-07.json (see Appendix C).

4.4 Common Package Data Model

4.4.1 The common package defines miscellaneous data types that are used by and across other TDE data model packages. The high-level structure and contents of the common package data model are illustrated in Figure 13.

Figure 13: Common Package Data Model



19

4.4.2 The significant data types within the common package are listed in Table 4.

Table 4: Common Package — Significant Data Types


Address A street address

Company Identification The identification of an Australian company

Vehicle Identification The identification of a vehicle using either the Vehicle Identification Number (VIN) or a non-VIN identifier

Abstract Document An abstract base type from which business documents can extend (see 4.4.3)

4.4.3 The abstract document is a base type from which the following key business documents within TDE extend: off-the-shelf conditions, the enrolment form, the event report, and the enrolment report. The abstract document type includes an explicit reference to the application to which the business document relates, as shown in the following XML fragment:

<?xml version="1.0" encoding="UTF-8"?>

<cond:offTheShelfConditions

xmlns:cond=http://www.tca.gov.au/schemas/tde/core/conditions/2018-07

<application>

<name>IAP</name>

<version>3.01</version>

</application>

… body of document here …

</cond:offTheShelfConditions>

4.4.4 The application version number reflects the specification version of the business logic used to form the contents of the document rather than the structure of the document, allowing ‘old data’ to be encoded within newer versions of the XML schema without semantic loss. The version of the XML schema is captured in the namespace of the root element, and of each document extension.

4.4.5 The common package data model is supported by the XML schema tde_core_common_2018-07.xsd (see Appendix B).


20 TCA-S11-2.2

www.tca.gov.au

4.5 Conditions Package Data Model

4.5.1 The conditions package models operating conditions that can be associated with an enrolment in an assessment application (monitoring applications do not have conditions). Operating conditions are specified as either unique conditions that are defined within the enrolment form, or as a standalone off-the-shelf conditions document referenced by the enrolment form. The high-level structure and contents of the conditions package data model are shown in Figure 14.

Figure 14: Conditions Package Data Model

4.5.2 The significant data types within the conditions package are listed in Table 5.

Table 5: Conditions Package – Significant Data Types


Off The Shelf Conditions The off-the-shelf conditions document – this extends the abstract document, and identifies the application and application version

Conditions The set of operating conditions, whether included within an enrolment form (unique conditions) or within an off-the-shelf conditions document

Operating Condition An abstract base type from which all operating conditions extend

Qualifying Condition Reference A reference to a qualifying condition (from a base condition)



21

4.5.3 Each set of operating conditions comprises one or more base conditions and optionally one or more qualifying conditions:

• Base conditions are operating conditions that are assessed to determine if the operation of the vehicle is consistent with the requirements of the scheme. Any identified inconsistencies are reported to the Authority within an event report.

• Qualifying conditions qualify a base condition, and are used to determine under what circumstances the base condition is in effect and therefore whether it should be assessed.

4.5.4 Structurally, base conditions and qualifying conditions are identical, allowing for a single type of operating condition to be used as either a base condition or qualifying condition according to the requirements of the application. Each module can extend the base type of operating condition to create operating conditions that relate to specific parameters of vehicle operation (e.g. location, time, speed, mass, configuration).

4.5.5 The qualifying condition is referred to from a base condition by using a condition identifier that is required to be unique within the context of any given set of operating conditions. The reference to the qualifying condition may be either Inverted or Standard, and this dictates how the qualifying condition is used to determine whether the base condition is in effect. For example, if a temporal condition qualifies a spatial condition, where the reference to the temporal condition is:

• Standard – the spatial condition is in effect during the times specified within the temporal condition; or

• Inverted – the spatial condition is in effect outside the times specified within the temporal condition.

4.5.6 The conditions package data model is supported by the XML schema tde_core_conditions_2018-07.xsd (see Appendix B).


22 TCA-S11-2.2

www.tca.gov.au

4.6 Enrolment Package Data Model

4.6.1 The enrolment package defines data types that model and support the enrolment of vehicles in NTF telematics applications. The high-level structure and contents of the data record package data model are illustrated in Figure 15.

Figure 15: Enrolment Package Data Model

4.6.2 The significant data types within the enrolment package are listed in Table 6.

Table 6: Enrolment Package – Significant Data Types


Enrolment Form The enrolment form business document. This extends the abstract document, and identifies the application and application version.

Authority Section Part 1 of the enrolment form, including details of the Authority, the scheme, and (for assessment applications) operating conditions

Operator Section Part 2 of the enrolment form, including details of the Operator and of the enrolled vehicle. An extension mechanism is provided to allow modules to define application-specific content within this section (e.g., enrolment applicability based upon vehicle configuration).



23


Service Provider Section Part 3 of the enrolment form, including details of the ASP and of the installation of telematics device(s). An extension mechanism is provided to allow modules to define application-specific content within this section (e.g. installation of connected devices).

Interim Approval Section The formal record of the interim approval of the enrolment

Approval Section The principal component of Part 4 of the enrolment form, being the formal record of the approval (or denial) of the enrolment

Cancellation Section An optional component of Part 4 of the enrolment form, being the formal record of the cancellation of the enrolment

Enrolment Cancellation Request A formal request to cancel an enrolment. This extends the abstract document, and identifies the application and application version.

4.6.3 The high-level components of the enrolment form are aggregated to form parts as follows:

• Part 1: Authority Details Authority, scheme, and (for assessment applications) operating conditions

• Part 2: Operator Details Operator details and vehicle details

• Part 3: ASP and Telematics Device Installation Details ASP and telematics device installation details

• Part 4: Approval/Cancellation

Formal enrolment approval and, as applicable, cancellation.

4.6.4 For all NTF applications, the enrolment directly identifies the Operator, the Authority, the ASP, the application, the scheme, the vehicle, and the installed telematics device(s). In addition, for assessment applications, the enrolment also specifies operating conditions, and may include application-specific enrolment applicability criteria (e.g. vehicle configuration).

4.6.5 At a minimum, each vehicle must have a separate enrolment for each scheme it participates in. However, it is feasible that some applications may allow for more complex situations where a vehicle requires multiple enrolments in a scheme – for example, where different operating conditions apply within a single scheme for different vehicle configurations.

4.6.6 The states of an enrolment are shown in Figure 16. Each transition from one state to another is formally recorded as occurring at a specific date and time, and is formally managed by a designated Enrolment Manager (i.e. only the Enrolment Manager may


24 TCA-S11-2.2

www.tca.gov.au

transition an enrolment between states).

Figure 16: Enrolment States

Interim Approved

DeniedInterim Cancelled

Lapsed Cancelled Ceased

Initial

[cancel] [deny] [cancel] [expire]

[approve]

4.6.7 While the Enrolment Manager has sole responsibility for formal transition of enrolments between states, other entities (e.g. the Authority, the ASP, the Operator, TCA) may be required or permitted to interact with the Enrolment Manager to request, support or facilitate specific enrolment state transitions.



25

4.6.8 Regardless of which party is the Enrolment Manager, the enrolment process is defined by the application. Different schemes within one application cannot have different enrolment processes, although they can have different requirements and obligations outside the scope of the application (e.g. different eligibility for enrolment). The enrolment process defined by the application will typically follow one of three models:

• ASP-managed enrolment (Figure 17), where the Enrolment Manager independently creates and approves an enrolment.

In this model, the ASP is the Enrolment Manager, and the enrolment is created as the result of out-of-scope business processes.

• Requested enrolment (Figure 18), where the Enrolment Manager creates and approves an enrolment, but with the enrolment process initiated by another party submitting an enrolment request.

Typically, this model would be applicable only where the ASP is the Enrolment Manager. The other party could be the Authority, the Operator, TCA or another entity.

• Authority-coordinated enrolment (Figure 19), where the Enrolment Manager creates and interim-approves an enrolment, another party provides prerequisite information to complete the enrolment, and the Enrolment Manager approves or denies the enrolment.

In this model, the Authority is the Enrolment Manager, and the other party is typically the ASP.

Figure 17: ASP-Managed Enrolment

Enro

lmen

t Man

ager

Oth

er P

arty

Create and Approve Enrolment

Enrolment Form [Approved]

Notify Enrolment


26 TCA-S11-2.2

www.tca.gov.au

Figure 18: Requested Enrolment

Enro

lmen

t Man

ager

Oth

er P

arty

Create Enrolment

Request

Enrolment Form - Authority Section - Service Provider Section

Enrolment Form [Approved]

Notify Enrolment

Request Enrolment

Create and ApproveEnrolment

Notify Rejection

[reject]

[accept]

* Note: This request is sent by the other party (i.e. not the Enrolment Manager) to trigger creation of an enrolment. It covers two scenarios:

• The ASP initiating the process to an Authority by providing Operator details and ASP details

• The Authority initiating the process to the ASP by providing condition details and Operator details

In either case, no enrolment identifier is included. This is added at the <Create Enrolment Form> step.



27

Figure 19: Authority-Coordinated Enrolment

Enro

lmen

t Man

ager

Oth

er P

arty

Create Interim Enrolment Form

Enrolment Form[Interim]

Notify Enrolment

[accept]

[reject]

Create Enrolment Form - Service Provider Section

Request Enrolment Approval

Notify Enrolment

Alternative flow:[Lapsed] or

[Interim-Cancelled]

Enrolment Form - Service Provider Section

Notify Rejection

Enrolment Form[Approved] or

[Denied]

Approve or DenyEnrolment


28 TCA-S11-2.2

www.tca.gov.au

4.6.9 Each application has the flexibility to define an enrolment process that meets the specific requirements of the application, and therefore is not required to support all the enrolment states. For example, an application may not require or support interim enrolment. Table 7 lists and describes all enrolment states, and notes those that might typically apply to an enrolment process.

Table 7: Enrolment States and Applicability

State Description Typical Applicability

ASP-Managed

Requested Authority-Coordinated

Interim The enrolment formally exists, but cannot be approved as it is incomplete (typically, an interim approved enrolment will be missing Part 3 data).

No No Yes

Lapsed This state is automatically entered where an interim enrolment is not approved or denied by the specified lapse date and time

No No Yes

Interim Cancelled

This state is explicitly entered where the Enrolment Manager cancels the interim enrolment in accordance with application-specific business rules

No No Yes

Denied This state is explicitly entered where a request for enrolment has been formally denied in accordance with application-specific business rules

No No Yes

Approved This state is explicitly entered where an enrolment is approved. The enrolment may have already existed in interim state, or may be created directly in this state.

Yes Yes Yes

Ceased This state is automatically entered where an approved enrolment has a cessation date and time, and that date and time is reached

Yes Yes Yes

Cancelled This state is explicitly entered where an enrolment is formally cancelled by the Enrolment Manager. This may occur because of a request for cancellation received from a second party.

Yes Yes Yes



29

4.6.10 Cancellation of an enrolment can be initiated by the Enrolment Manager (e.g. as a result of internal or out-of-scope business processes), or by a second party submitting a cancellation request to the Enrolment Manager. Where an enrolment is cancelled by the Enrolment Manager, the enrolment form should be notified to other participants. Where the Enrolment Manager rejects a cancellation request, the submitting party should be notified of that rejection.

4.6.11 Updates of the enrolment are necessary when details within the enrolment form change, and are actioned by simultaneously cancelling the existing enrolment form and issuing a new (replacement) enrolment form. The replacement of an enrolment may be initiated by the Enrolment Manager (e.g. as a result of internal or out-of-scope business processes), or by a second party submitting a prefilled replacement enrolment form to the Enrolment Manager.

4.6.12 A standard data model exists for the enrolment form that is used across all applications and enrolment processes. Different applications and enrolment processes may require completion of different parts of the enrolment form, potentially at different times during the enrolment process, and potentially by different parties. The enrolment form data model is shown in Table 8.

Table 8: Enrolment Form Data Model

Element Description Notes

Header

identifier Unique identifier for the enrolment Mandatory

previousEnrolmentIdentifier Identifies the prior enrolment identifier when an enrolment is updated (an update cancels the previous enrolment and creates a new one)

Optional

enrolmentProcess Describes the entity that is the Enrolment Manager – either the ASP or the Authority

Optional

Default is ASP

secondPartyReference Any identifiers known to be used by parties other than the Enrolment Manager to refer to this enrolment or the management of this enrolment. For example, the identifier of a request (received by the Enrolment Manager) to approve the enrolment.

Optional

statusCode Status of the enrolment – see Table 7 Mandatory

commencementDateTime Start date and time of the enrolment.

Once approved, the enrolment becomes active at whichever is latest of this date and time and the enrolment approval date and time.

Mandatory


30 TCA-S11-2.2

www.tca.gov.au


cessationDateTime Scheduled end date and time of the enrolment.

The enrolment becomes inactive at the earliest of this date and time (if specified) and the enrolment cancellation date and time (if specified).

Optional

Part 1: Authority Details

authority Identifies the Authority that operates the scheme that is being enrolled in

Mandatory

schemeName Name of the scheme that is being enrolled in

Mandatory

conditionsSection Description of the operating conditions associated with the enrolment

Mandatory

offTheShelfConditions Identifier

Reference to a set of operating conditions for the enrolment – applies only to assessment applications

Choice

uniqueConditions Unique conditions documented within the enrolment – applies only to assessment applications

Choice

Part 2: Operator Details

operatorSection Information regarding the vehicle and the Operator being enrolled

Mandatory

operator Information regarding the Operator Mandatory

identity Trading name of the Operator Mandatory

postalAddress Postal address of the Operator’s head office

Optional

businessHoursPhone Business hours phone number for the Operator

Optional

afterHoursPhone After hours phone number for the Operator

Optional

fax Fax number for the Operator Optional

emailAddress Email address for the Operator Optional

nominatedOfficer Officer nominated by the Operator as primary point of contact for the enrolment

Optional



31


primaryUnitInformation Prime mover/rigid truck information Optional

make Make of the vehicle Optional

model Model of the vehicle Optional

garagingAddress Garaging address of the vehicle Optional

bodyType Body type of the vehicle Optional

extension An extension point that allows applications to incorporate application-specific enrolment Operator and vehicle information, notably including advanced enrolment applicability criteria for assessment applications (e.g. based upon vehicle configuration)

Optional

comments Free form comments relating to the Operator or vehicle

Optional

InterimApprovalSection Information regarding the formal interim approval of the enrolment. Interim enrolment allows the Enrolment Manager to communicate to stakeholders that the enrolment exists, but that it cannot be approved or denied until missing information is obtained (e.g. telematics device installation details)

Note: Interim enrolment is not applicable to ASP-managed enrolment or requested enrolment.

Optional

lapseDateTime Date and time at which the interim approval of the enrolment expires

Mandatory

comments Free form comments relating to the interim approval

Optional

authorisingOfficer The officer under whose authority the enrolment was interim approved

Optional

issuedDateTime Formal date and time of interim approval

Mandatory


32 TCA-S11-2.2

www.tca.gov.au


Part 3: ASP and Telematics Device Installation Details

serviceProviderSection Information regarding the ASP, and the installation of telematics device(s). This data is prerequisite to enrolment approval (but not to enrolment interim approval).

Optional

serviceProvider Information regarding the ASP and the installation of telematics device(s) to the prime mover/rigid truck

Mandatory

identity Trading name of the ASP Mandatory

postalAddress Postal address of the ASP’s head office Optional

businessHoursPhone Business hours phone number for the ASP

Optional

afterHoursPhone After hours phone number for the ASP Optional

fax Fax number for the ASP Optional

emailAddress Email address for the ASP Optional

primaryUnitInstallation Information regarding the installation of telematics device(s) to the prime mover/rigid truck

Mandatory

vin 17-character vehicle identification number for the prime mover/rigid truck

VIN or non-VIN identifier must be specified

nonVinIdentifier Alternative identifier to VIN – only used if VIN is unavailable

VIN or non-VIN identifier must be specified

installedDevice Information regarding the installed telematics device(s)

Mandatory

deviceIdentity Identifier of the telematics device Mandatory

installationDateTime Date and time of telematics device installation

Mandatory

deviceLocation Location of the installed device (e.g. behind dashboard)

Mandatory

gpsAntennaLocation Location of the installed GPS antenna (e.g. top-left of roof)

Mandatory



33


extension An extension point that allows the ASP to include additional information, for example the installation of further telematics devices

Optional

comments Free form comments regarding the ASP or telematics device installation

Optional

issuedDateTime Date and time when Part 3 details are formally completed

Mandatory

Part 4: Approval and Cancellation Details

approvalSection Information regarding the formal approval of the enrolment form – only included when enrolment is approved or denied

Optional

approved Whether the enrolment was approved (true) or denied (false)

Mandatory

comments Free form comments regarding the approval or denial of the enrolment

Mandatory

authorisingOfficer The officer under whose authority the enrolment was approved or denied

Mandatory

issuedDateTime Date and time the completed enrolment form was formally approved or denied

Mandatory

cancellationSection Information regarding the formal cancellation of the enrolment. This is only included where the enrolment has been cancelled.

Optional

comments Free form comments regarding the cancellation of the enrolment

Optional

authorisingOfficer The officer under whose authority the enrolment was cancelled

Mandatory

issuedDateTime Date and time the enrolment was formally cancelled

Mandatory

4.6.13 The enrolment package data model is supported by the XML schema tde_core_enrolment_2018-07.xsd (see Appendix B).


34 TCA-S11-2.2

www.tca.gov.au

4.7 Event Report Package Data Model

4.7.1 The Event Report package defines data types that model and support the reporting of events identified through the assessment of operating conditions within assessment applications of the NTF. Event reporting is not relevant to monitoring applications. The high-level structure and contents of the Event Report package data model are shown in Figure 20.

Figure 20: Event Report Data Package Model

4.7.2 The significant data types within the event report package are listed in Table 9 .

Table 9: Event Report Package – Significant Data Types


Event Report The event report business document. This extends the abstract document, and identifies the application and application version.

Event Summary A summary of the event, including the type of the event, and the period of the event.

Primary Unit Information Information about the prime mover/rigid truck, including the identifier of the installed telematics device.

Enrolment Reference A reference to the applicable enrolment(s) against which the event has been identified.



35


Event Report Extension An extension mechanism provided to allow modules to define application-specific content within the event report (e.g. details of connected devices).

Report Record An abstract base type for all event report records. This is either a wrapper around a telematics device data record, or is a data record synthesised from telematics device data records within the ASP System.

Transfer Record A wrapper around a transfer data record.

Alarm Record A wrapper around an alarm record.

Derived Alarm Record A synthesised record representing an alarm condition identified through testing of telematics data records.

4.7.3 Event reports are related to one or more enrolments in a single application. Each application will describe for each event type whether it is assessed individually per-enrolment, or collectively across all enrolments in the application.

4.7.4 Event report data model packages within modules are able to define additional types of record that can be included within event reports (see Appendix F).

4.7.5 The event report package data model is supported by the XML schema tde_core_event-report_2018-07.xsd (see Appendix B).


36 TCA-S11-2.2

www.tca.gov.au

4.8 Enrolment Report Package Data Model

4.8.1 The enrolment report package defines data types that model and support the reporting of enrolments within telematics applications of the NTF. The high-level structure and contents of the Enrolment Report package data model are shown in Figure 21.

Figure 21: Enrolment Report Data Package Model

4.8.2 The significant data types within the enrolment report package are listed in Table 10.

Table 10: Enrolment Report Package – Significant Data Types


Enrolment Report The enrolment report business document. This extends the abstract document, and identifies the application and application version.

Enrolment Summary An enrolment summary for a given telematics device installed in a given vehicle.

Enrolment Summary Extension An extension mechanism provided to allow modules to define application-specific content within the enrolment summary.

Enrolment Reference A reference to an enrolment in the application for the installed telematics device.

Enrolment Reference Extension An extension mechanism provided to allow modules to define application-specific content within the enrolment reference.



37


Reported Event Counts A summary of the number of event reports raised during the enrolment reporting period.

4.8.3 An enrolment report is generated for each Authority for a defined reporting period, and summarises all enrolments in the application for the schemes of that Authority. A separate enrolment report is required for each Authority and application.

4.8.4 The enrolment report includes enrolment summaries. A separate enrolment summary is required for each unique combination of telematics device and vehicle. For example, where a telematics device fails and is replaced, a new enrolment summary must be created to report on operation of the vehicle with the new telematics device installed.

4.8.5 By default, each enrolment summary references a single enrolment, and therefore a separate enrolment summary is required for each enrolment even where two enrolments are for the same combination of telematics device and vehicle. This is shown in the following XML fragment:

<?xml version="1.0" encoding="UTF-8"?> <tde-enr:enrolmentReport xmlns:tde-enr="http://www.tca.gov.au/schemas/tde/core/enrolment-report/2018-07"> … document header information here … <enrolmentSummary> <vehicleIdentity> <vin>12345678901234567</vin> </vehicleIdentity> <enrolment> <enrolmentIdentifier>X0987654321</enrolmentIdentifier> <scheme>ABC-1</scheme> </enrolment> <entryDateTime>...</entryDateTime> <exitDateTime>...</exitDateTime> <installedDevice> <id>1234</id> <type>TD</type> </installedDevice> </enrolmentSummary> <enrolmentSummary> <vehicleIdentity> <vin>12345678901234567</vin> </vehicleIdentity> <enrolment> <enrolmentIdentifier>X1234567890</enrolmentIdentifier> <scheme>ABC-2</scheme> </enrolment> <entryDateTime>...</entryDateTime> <exitDateTime>...</exitDateTime> <installedDevice> <id>1234</id>


38 TCA-S11-2.2

www.tca.gov.au

<type>TD</type> </installedDevice> </enrolmentSummary> <comments/> <issuedDateTime>2007-02-26T01:02:03</issuedDateTime> </tde-enr:enrolmentReport>

4.8.6 However, where explicitly required by the application, each enrolment summary must list all enrolments that were active during the reporting period for that combination of telematics device and vehicle. This is shown in the following XML fragment:

<?xml version="1.0" encoding="UTF-8"?> <tde-enr:enrolmentReport xmlns:tde-enr="http://www.tca.gov.au/schemas/tde/core/enrolment-report/2018-07"> … document header information here … <enrolmentSummary> <vehicleIdentity> <vin>12345678901234567</vin> </vehicleIdentity> <enrolment> <enrolmentIdentifier>X1234567890</enrolmentIdentifier> <scheme>ABC-1</scheme> </enrolment> <enrolment> <enrolmentIdentifier>X0987654321</enrolmentIdentifier> <scheme>ABC-2</scheme> </enrolment> <entryDateTime>...</entryDateTime> <exitDateTime>...</exitDateTime> <installedDevice> <id>1234</id> <type>TD</type> </installedDevice> </enrolmentSummary> <comments/> <issuedDateTime>2007-02-26T01:02:03</issuedDateTime> </tde-enr:enrolmentReport>

4.8.7 Each enrolment summary specifies an application entry date and time and an application exit date and time, determined as follows:

• entry date and time – the earliest date and time during the reporting period when any of the referenced enrolments were active, with a blank/void value indicating the start of the reporting period; and

• exit date and time – the latest date and time during the reporting period when any of the referenced enrolments were active, with a blank/void value indicating the end of the reporting period.

4.8.8 The enrolment report package data model is supported by the XML schema tde_core_enrolment-report_2018-07.xsd (see Appendix B).



39

4.9 Data Reporting Package Data Model

4.9.1 The data reporting package defines data types that model and support the data reporting manifest required for Tier 3 Data Exchange (see Section 7). The high-level structure and contents of the data reporting package data model are shown in Figure 23.

Figure 22: Data Reporting Data Package Model

4.9.2 The significant data types within the data reporting package are listed in Table 11.

Table 11: Data Reporting Package Significant Data Types


Data Report The data reporting manifest business document– this does not extend the abstract document as it must be able to reference multiple applications.

Transferrable Item A base type for an application data item that is able to be transferred using the progressive transfer mechanism (refer to 7.2 and C.8).

Enrolment Item The reporting of an enrolment form.

Event Report Item The reporting of an event report.

Enrolment Report Item The reporting of an enrolment report.

Data Record Batch Item The reporting of a data record batch.

Device Data Records Item The reporting of a device data record set.

4.9.3 The data reporting manifest is concerned with summarising the data items within a Tier 3 Data Exchange data package for the purposes of data assurance.


40 TCA-S11-2.2

www.tca.gov.au

4.9.4 The data reporting package data model is supported by the XML schema tde_core_data-report_2018-07.xsd (see Appendix B).

4.10 Data Exchange Formats and Encoding

4.10.1 As required by the application, for the purposes of data exchange, the business documents and reporting artefacts defined by the TDE Business Data Model are formatted using either:

• XML (see 4.10.4); or

• JSON (see 4.12). 4.10.2 Unless otherwise required by the application, XML and JSON documents are encoded

using UTF-8.

4.10.3 Within the documents defined by the TDE Business Data Model, significant data elements of type date, time and dateTime have an implicit time zone as shown in Table 12.

Table 12: Non-Exhaustive List of Implicit Time Zones for Significant Data Elements

Document Document Section or Field Time Zone

Off-the-shelf conditions Main document • issuedDateTime

Authority

Main document • validFromDateTime • validToDateTime

Jursidiction

Temporal conditions • conditionPeriod/fromDateTime • conditionPeriod/toDateTime • conditionInterval/fromTime • conditionInterval/toTime

Jursidiction

Enrolment form Main document • commencementDateTime • cessationDateTime

Jurisdiction

Interim Approval section • lapseDateTime

Jurisdiction

Interim Approval section • issuedDateTime

Authority or ASP*

Service Provider section • issuedDateTime

ASP

Approval section • issuedDateTime

Authority or ASP*

Cancellation section • issuedDateTime

Authority or ASP*



41

Document Document Section or Field Time Zone

Enrolment form (‘Part 3’) Main document • issuedDateTime

ASP

Enrolment cancellation request Main document • issuedDateTime

ASP

Event report XML: eventReport

Main document • issuedDateTime

ASP

Main document • auditReferenceDateTime Main document - event summary • jurisdictionEventPeriod/

fromDateTime • jurisdictionEventPeriod/

toDateTime

Jurisdiction

Main document - event summary • deviceEventPeriod/fromDateTime • deviceEventPeriod/toDateTime

UTC

Report record • jurisdictionDateTime

Jurisdiction

Device record • deviceDateTime

UTC

Enrolment report Main document • issuedDateTime

ASP

Main document • reportPeriod/fromDateTime • reportPeriod/toDateTime

Jurisdiction

Enrolment summary • entryDateTime • exitDateTime

Jurisdiction

Note: In the Time Zone column, where ‘Authority or ASP’ is shown, the Authority’s time zone is used if the Authority is the Enrolment Manager, and the ASP’s time zone is used if the ASP is the Enrolment Manager.

4.10.4 Within XML and JSON format business documents and reporting artefacts, all data elements having an implicit time zone defined by 4.10.3 should be encoded without any time zone offset (e.g. 2018-12-03T11:54:00 rather than 2018-12-03T11:54:00+10:00, and 01:02:03 rather than 01:02:03+11:00). Where such a data element is encoded with a time zone offset, the date, time or dateTime should be translated to the implicit time zone defined by 4.10.3 prior to being used within business processing.


42 TCA-S11-2.2

www.tca.gov.au

4.11 XML Formatting

4.11.1 The TDE Business Data Model is supported by XML schemas as presented in Appendix B and Appendix F.

4.11.2 Each XML schema document has an XML namespace of the following form, where module is either core or one of the module names specified in Appendix F, and document is one of data, common, conditions, enrolment, event-report, enrolment-report, or data-report:

http://www.tca.gov/schemas/tde/<module>/<document>/2018-07

4.11.3 XML namespaces are referred to within each XML document by an XML namespace prefix. Within this specification the following XML namespace prefixes are used for clarity: data for data record, common for common, cond for conditions, enr for enrolment, evr for event report, and enr for enrolment report.

4.12 JSON Formatting

4.12.1 The TDE Business Data Model is supported by JSON schemas as presented in Appendix C.

4.12.2 JSON schemas are defined using JSON Schema Draft 7, and each has a schema id of the following form:

http://www.tca.gov/schemas/tde/<module>/<document>/2018-07

4.12.3 JSON schemas are defined only for the data records module. The JSON schemas enforce the name, data type and range of acceptable values for each data element. A supplementary JSON schema for data records may be defined by each application. Such JSON schemas enforce which data records and data elements are relevant to that application, and which of the relevant data elements are mandatory for that application.


http://www.tca.gov/schemas/tde/%3cmodule%3e/%3cdocument%3e/2018-07


43

5 TIER 1 DATA EXCHANGE

5.1 Purpose of Tier 1 Data Exchange

5.1.1 Tier 1 Data Exchange defines a set of RESTful services used to support the automated transfer of telematics application data between participants (the Authority, ASP or TCA) in a manner that is secure, reliable and interoperable.

5.1.2 Each Tier 1 Data Exchange service represents a business domain functions. These business domain functions are used in sequence to support higher-level business domain processes and reporting as described in Section 4 Business Data Model and Section 7 Tier 3 Data Exchange.

5.1.3 Each Tier 1 Data Exchange service involves two participants:

• one in the role of the client that invokes the service, and

• the other in the role of the server that hosts the service and thus accepts calls on the service by the client.

Dependent upon the intent of the RESTful service, the participants will be the Authority, ASP or TCA.


44 TCA-S11-2.2

www.tca.gov.au

5.2 Overview of Tier 1 Data Exchange

5.2.1 Tier 1 Data Exchange services are:

a. Notify Enrolment (see 5.3);

b. Request Enrolment (see 5.4);

c. Request Enrolment Approval (see 5.5);

d. Request Enrolment Replacement (see 5.6);

e. Request Enrolment Cancellation (see 5.7);

f. Notify Rejection (see 5.8);

g. Notify Event Report (see 5.9);

h. Notify Enrolment Report (see 5.10);

i. Notify Data Records (see 5.11);

j. Notify Data Report (see 5.12);

5.2.2 Services prefixed with ‘Request’ are concerned with one participant requesting a second participant to create or update a business document. For such services, the second participant may:

a. perform synchronous processing, and as a result of that processing, synchronously reject the request;

b. synchronously accept the request, and as a result of asynchronous (offline) processing later asynchronously reject the request using the Notify Response service; or

c. synchronously accept the request, and as a result of asynchronous (offline) processing complete the request and notify the requesting participant of the outcome of the service using an appropriate notify service.

5.2.3 Services prefixed with ‘Notify’ are concerned with one participant notifying a second participant of a business event or the creation/update of a business document, and include (as payload) the relevant business document. Such services are considered complete once the second participant has received and stored the business document.

5.2.4 Tier 1 Data Exchange services are realised by RESTful operations as specified in Appendix D, and in accordance with the requirements of Part A.



45

5.2.5 As shown in Table 13, dependent upon the requirements of the application, each participant may be required to invoke and/or host specific Tier 1 Data Exchange services for the purposes of:

a. enrolment – telematics applications will have varied enrolment business processes, and some applications use Tier 1 Data Exchange services to support those business processes (see 4.6);

b. event reporting for assessment applications;

c. enrolment reporting; and

d. data reporting to TCA – periodic reporting of application data to TCA may include enrolment forms, event reports, enrolment reports, data records, and data reports.

Table 13: Applicability of Tier 1 Data Exchange Services

Tier 1 Data Exchange Service

Enrolment Event/ Enrolment Reporting

Data Reporting

Authority to ASP

ASP to Authority

ASP to Authority

ASP to TCA

Notify Enrolment Y Y Y

Request Enrolment Y Y

Request Enrolment Approval Y Y

Request Enrolment Replacement Y Y

Request Enrolment Cancellation Y Y

Notify Rejection Y Y

Notify Event Report Y Y

Notify Enrolment Report Y Y

Notify Data Records Y

Notify Data Report Y

Note: Tier 1 Data Exchange participants for each service are as described by a telematics application.


46 TCA-S11-2.2

www.tca.gov.au

5.3 Notify Enrolment Service

5.3.1 The Notify Enrolment service is used by a participant to notify another participant of an update to an enrolment in a telematics application (e.g. interim approval, approval, cancellation). This service takes the enrolment form as input, completed in accordance with the requirements of the application.

5.4 Request Enrolment Service

5.4.1 The Request Enrolment service is used by a participant to request that another participant (in the role of Enrolment Manager) creates an enrolment in a telematics application. This service takes an enrolment form as input, completed in accordance with the requirements of the application.

Example: If an Authority was to request that an ASP enrols a vehicle in an application, the input enrolment form may contain Part 1 (Authority details) and Part 2 (Operator details), but would not contain Part 3 (ASP details) or Part 4 (Approval/Cancellation details).

5.4.2 Upon receiving the request, the second participant may then:

a. reject the request, using the Notify Rejection service to advise the first participant of the rejection; or

b. accept the request, and create an enrolment in a state allowed by the application (e.g. interim, approved), using the Notify Enrolment service to advise the first participant that an enrolment has been created.

5.4.3 If the request is accepted, the Enrolment Manager includes the request identifier within the enrolment (as a second party reference). This allows the first participant to identify the created enrolment as having resulted from their request.

5.5 Request Enrolment Approval Service

5.5.1 The Request Enrolment Approval service is used by a participant to request another participant (in the role of Enrolment Manager) to approve an existing (and interim approved) enrolment. This service takes the enrolment form as input, completed in accordance with the requirements of the application.

Example: Where an Authority is the Enrolment Manager and has already created an interim approved enrolment, the ASP may submit an enrolment form that contains only Part 3 (ASP details).



b. accept the request, and then either approve or deny the enrolment in accordance with relevant business rules, using the Notify Enrolment service to advise the first participant that the enrolment has been updated.

Note: A request for enrolment approval might be rejected for various reasons, for example an invalid enrolment reference, or missing or incomplete data. Once the request has been accepted by the Enrolment Manager, the enrolment may still be denied, for example because prerequisite obligations for enrolment in the scheme have not been met (e.g. payment of fees, lodgement of maintenance records).



47

5.5.3 If the request is accepted, the Enrolment Manager includes the request identifier within the enrolment (as a second party reference). This allows the first participant to identify the enrolment as having been approved or denied as a result of their request.

5.6 Request Enrolment Replacement Service

5.6.1 The Request Enrolment Replacement service is used by a participant to request another participant (in the role of Enrolment Manager) to cancel an approved enrolment, and to replace it with a new enrolment. This service takes an enrolment form as input, completed in accordance with the requirements of the application. Typically, such requirements will relate to the replacement of a telematics device.



b. accept the request, simultaneously cancelling the existing enrolment and creating an approved replacement enrolment. This action uses the Notify Enrolment service to advise the first participant of the creation of the replacement enrolment (implicitly this advises the first participant that the original enrolment has been cancelled).

5.6.3 If the request is accepted, the Enrolment Manager includes the request identifier within both the cancelled and created enrolments (as a second party reference). This allows the first participant to identify changes to both enrolments as being associated with their request.

5.7 Request Enrolment Cancellation Service

5.7.1 The Request Enrolment Cancellation service is used by a participant to request another participant (in the role of Enrolment Manager) to cancel an existing approved enrolment. This service takes an enrolment cancellation request as input.



b. accept the request, and cancel an enrolment, using the Notify Enrolment service to advise the first participant that an enrolment has been cancelled.

5.7.3 If the request is accepted, the Enrolment Manager includes the request identifier within the cancelled enrolment (as a second party reference). This allows the first participant to identify the enrolment as being associated with their request.

5.8 Notify Rejection Service

5.8.1 The Notify Rejection service is used by a participant to inform another participant that a previous request to another service has been rejected as a result of asynchronous (offline) processing. This service and the original request are correlated by a request identifier.


48 TCA-S11-2.2

www.tca.gov.au

5.9 Notify Event Report Service

5.9.1 The Notify Event Report service is used by a participant (an ASP) to notify a second participant of the creation of an event report. This service takes an event report as input, completed in accordance with the requirements of the application.

5.10 Notify Enrolment Report Service

5.10.1 The Notify Enrolment Report service is used by a participant (an ASP) to notify a second participant of the creation of an enrolment report. This service takes an enrolment report as input, completed in accordance with the requirements of the application.

5.11 Notify Data Records Service

5.11.1 The Notify Data Records service is used by one participant (n ASP) to notify a second participant of the creation of a data record batch. This service takes the data record batch as input, assembled in accordance with the requirements of the application, and the constraints specified in Section 7 Tier 3 Data Exchange.

5.12 Notify Data Report Service

5.12.1 The Notify Data Report service is used by a participant (an ASP) to notify a second participant of the creation of a data report. This service takes a data reporting manifest as input, completed in accordance with the requirements of the application.



49

PART A TIER 1 DATA EXCHANGE REQUIREMENTS

A.1 Standards and Interoperability

A.1.1 The B2B interface shall be implemented against the following standards and technologies:

a. HTTP 1.1 [HTTP];

b. Transport Layer Security version 1.2 [TLS]; and

c. Cryptographic Message Syntax [CMS]; and

A.2 Network Security

A.2.1 The participant shall use the public Internet as the transmission network for Tier 1 Data Exchange.

A.2.2 The participant shall configure its network infrastructure to only accept Tier 1 Data Exchange connections from counterpart participant Internet addresses as advised by TCA.

A.2.3 The participant shall use HTTPS (i.e. HTTP 1.1 over TLS 1.2 or higher) for Tier 1 Data Exchange, such that:

a. Tier 1 Data Exchange clients shall not invoke Tier 1 Data Exchange services except via HTTPS;

b. Tier 1 Data Exchange services shall not accept client invocations except via HTTPS; and

c. the cryptographic algorithms negotiated between Tier 1 Data Exchange client and service shall use at least SHA-256.

Note: Further information concerning accepted encryption protocols may be obtained from TCA.

A.2.4 When hosting a Tier 1 Data Exchange service, the participant shall configure its system to use a current and unrevoked SSL/TLS certificate issued by a reputable commercial authority for the purpose of authenticating that service to clients.

A.2.5 When invoking a Tier 1 Data Exchange service, the participant shall configure its client system to trust the issuing commercial authority used by that service (as advised by TCA) for the purpose of authenticating that service to their client.

A.2.6 As required by the application, when hosting a Tier 1 Data Exchange service, the participant shall configure its system to require and trust a current and unrevoked TCA-signed client certificate for authenticating clients to that service.

A.2.7 As required by the application, when invoking a Tier 1 Data Exchange service, the participant shall configure its client system to use a current and unrevoked TCA-signed client certificate for authenticating their client system to that service.


50 TCA-S11-2.2

www.tca.gov.au

A.2.8 As required by the application, when hosting a Tier 1 Data Exchange service, the participant shall:

a. configure its system to use and require basic authentication for the purpose of authenticating clients to that service; and;

b. issue, to each participant invoking that service, valid credentials comprising a user name and non-expiring password.

A.2.9 As required by the application, when invoking a Tier 1 Data Exchange service, the participant shall configure its client system to use basic authentication for authenticating its client system to that service.

A.3 RESTful Service Implementation

A.3.1 The participant shall host Tier 1 Data Exchange services required by the application as RESTful operations relative to a base URL nominated by the participant, and advised to TCA.

Note: For example, the ASP may host the Notify Enrolment service using the URL http://ntf-tde.some-provider.com.au/services/enrolment/{enrolment-id}.

A.3.2 When hosting a Tier 1 Data Exchange service, the participant shall configure its system to return one of the following HTTP status codes in response to a client invocation of that service:

a. 202 Accepted – where a request has been received and accepted, but has not yet been acted upon (e.g. a later notification may occur to advise the outcome of processing);

b. 204 No Content – where a notification or request has been received, accepted and requires no further interaction;

c. 400 Bad Request – where the notification or request could not be understood by the server due to errors in the data;

d. 404 Not Found – where the business entity the notification or request pertains to does not exist (or is not visible as the participant making the invocation is not authorised to access it);

e. 409 Conflict – where the business entity the request pertains to is not in a state that is would allow the request to be actioned;

f. 412 Precondition Failed – where the application requires that the input data (payload) be digitally signed, but it has not been digitally signed;

g. 429 Too Many Requests – where the client has sent too many notifications or requests in a given period; or

h. 5xx1 Server Error – where the server encountered an unexpected condition that prevented it from receiving, storing or actioning the notification of request.

A.3.3 Upon receipt of a 400-series HTTP status code, the participant shall attempt to resolve the issue outside the scope of Tier 1 Data Exchange.

1 The convention ‘xx’ in this context is used for any number between 500 and 599.



51

A.3.4 Upon receipt of a 500-series HTTP status code, the participant shall reinvoke the Tier 1 Data Exchange service at intervals of not less than 1 hour until such time that one of the following conditions is met:

a. an HTTP status code is received that is not a 500-series status code; or

b. eight consecutive attempts to send the request have occurred, in which case the participant shall attempt to resolve the issue outside the scope of Tier 1 Data Exchange.

A.3.5 The participant shall support HTTP-level data compression, with support for at least the gzip algorithm.

Note: HTTP-level data compression is negotiated between client and server using the ‘Content-Encoding’ HTTP request header (e.g. Content-Encoding: gzip).

A.3.6 The participant shall support the following content types for the body of Tier 1 Data Exchange service requests and responses:

a. application/xml – for XML data meeting the requirements of A.4.1a; and

b. application/json – for JSON data meeting the requirements of A.4.1b.

A.3.7 Where required by the application, the participant shall digitally sign the business document or data within the HTTP request body in accordance with the requirements of A.5, and include this digital signature in Base64-encoded form as the HTTP header Content-Signature.

Note: The digital signature is formed over the content of the HTTP request prior to (and independently of) transmission via HTTP, and for that reason the signed content must not be altered in any way by the transmission process (as this will cause signature verification to fail). Other than the inclusion of the Content-Signature header, the resultant HTTP request is identical to an equivalent request that does not include a digital signature. The following is an example of an HTTP request that includes a digital signature.

PUT /tde/rest/data-records/ABC20190803 HTTP/1.1

Host: example-server.example-asp.com.au

Content-Type: application/json

Content-Signature: MIIHXgYJKoZIhvcNAQcCoIIHTzCCB0sCAQExDzANBglghkgBZQMEAgEFADALBgkqhkiG9w0BBwGgggReMIIEWjCCA0KgAwIBAgIJAJHXqamAKYZwMA0GCSqGSIb3DQEBCwUAMHQxCzAJBgNVBAYT AkFVMTQwMgYDVQQKEytUcmFuc3BvcnQgQ2VydGlmaWNhdGlvbiBBdXN0cmFsaWEgUHR5LiBMdGQuMRcwFQYDVQQLEw53d3cudGNhLmdvdi5hdTEWMBQGA1UEAxQNVENBIFJvb3QgQ0HCoDAgFw0xODAyMTkyMDI5MjBaGA8yMTE4MDIxOTIwMjkyMFowdDELMAkGA1UEBhMCQVUxNDAyBgNVBAoTK1

… signature data omitted for brevity …

bo6hCarW3Ejj6NBGigq/7UV/PZHNCDgAooy0bPwpFKS7NBrPI5G0gFpPDoxigg11K0IfRDRZYtkJqT

Content-Length: 1054


52 TCA-S11-2.2

www.tca.gov.au

{

"tdeVersion" : "2.0",

"batchId" : "ABC20190803",

"deviceRecords" : [{

"tdeVersion" : "2.0",

"device": {

"id" : "1234"

},

"records" : [

… data records omitted for brevity … ]

}]

}

A.3.8 Where business documents or data received by a participant via Tier 1 Data Exchange are required to be digitally signed by the application, the participant shall:

a. where a digital signature is not present or is not able to be read, reject the request with status code 412;

b. where a digital signature is present, but the signature fails verification (e.g. the signature does not match the data), reject the request with status code 400;

c. where a digital signature is present and verified, but the signing certificate is not yet in force, expired, untrusted, revoked, does not support non-repudiation or does not contain an ABN, reject the request with status code 400; or

d. where a digital signature is present and verified, the signing certificate is valid and contains an ABN, but the ABN in the certificate does not match that of the invoking participant, reject the request with status code 400.

A.3.9 The participant shall ensure that all hosted Tier 1 Data Exchange services are idempotent.

Note: An idempotent service has the same effect irrespective of how many times it is called with the same data. For example, multiple calls to the Request Enrolment service with the same data must not result in multiple enrolments being created.

A.4 Tier 1 Data Exchange Formats and Encoding

A.4.1 The participant shall format and encode all business documents and reporting artefacts exchanged using Tier 1 Data Exchange in accordance with 4.10 such that:

a. as applicable and as required by the application, business documents and reporting artefacts are formatted as XML in accordance with the XML schemas specified in Appendix B and Appendix F;

b. as applicable and as required by the application, business documents and reporting artefacts are formatted as JSON in accordance with the JSON schemas specified in Appendix C;



53

c. unless otherwise required by the application, all business documents are artefacts are encoded in accordance with 4.10.2; and

d. date, time and dateTime values are formatted and encoded in accordance with 4.10.3 and 4.10.4.

Note: If the option exists to format data as either XML or JSON, the participant should liaise with TCA to determine a preferred format, for example, considering the nature of the application and the participants with whom data is being exchanged.

A.5 Tier 1 Data Exchange Digital Signatures

A.5.1 Where required by the application, the participant shall digitally sign business documents or data for Tier 1 Data Exchange using the Cryptographic Message Syntax (CMS) such that:

a. the signature is created as a signed-data content type, and without the signed data itself being encapsulated within the signed-data content;

b. the signature is created using the RSA with SHA-256 algorithm;

c. the signed-data content includes the signing digital certificate; and

d. the signed-data content includes the signing-time attribute.

Note: Generation of a digital signature that does not encapsulate the data being signed is termed ‘clear signing’.

A.5.2 The participant shall use an ABN-DSC device (Type 3) digital certificate containing an ABN to create the digital signature required by A.5.1.

A.6 Logging

A.6.1 As required by the application, each Tier 1 Data Exchange service request and response shall be logged, including:

a. the date and time of receipt of the request or response;

b. the Tier 1 Data Exchange service (by name or by URL);

c. the identity of the authenticated counterpart participant, including the ABN of that participant where known;

d. the request identifier or business document identifier if and as applicable; and

e. the full body of the request or response as received from the counterpart participant.

Note: For the purposes of digital signature verification, the request and response body shall not be altered in any way prior to being logged in accordance with this requirement.


54 TCA-S11-2.2

www.tca.gov.au

A.7 Resource Discovery and Identity Management

A.7.1 The participant shall have the capability to configure its Tier 1 Data Exchange services to reflect counterpart participant details including:

a. name;

b. ABN;

c. base URL for Tier 1 Data Exchange services;

d. SSL/TLS certificate-issuing commercial authority used by the participant;

e. source and target Internet addresses; and

f. as required by the application, basic authentication credentials.



55



6.1.1 The purpose of this section is to specify methods by which entities such as ASPs, Authorities and TCA can communicate formally outside of Tier 1 and Tier 3 communications.

6.1.2 Tier 2 Data Exchange is used for business communication that is typically human-initiated rather than automated. Typical exchanges via Tier 2 include the reporting of issues and resolutions, correspondence regarding certification and re-certification, advice regarding ICT, data assurance and other reporting.

6.1.3 Tier 2 Data Exchange also supports enrolment forms and enrolment reports if the referenced application(s) require or permit it.

Note: This information is distributed by TCA along with information about trading partners.

6.1.4 Enrolment via Tier 2 is constrained to monitoring applications.

6.2 Tier 2 Communication Methods

6.2.1 Tier 2 Data Exchange sets requirements for the following communication methods:

• Secure email

• Registered mail

• Secure web portal

• File Transfer Protocol Secure (FTPS). Note: Communications outside of Tier 1, Tier 2 or Tier 3 might not be considered binding, depending on the telematics application.


56 TCA-S11-2.2

www.tca.gov.au

PART B TIER 2 DATA EXCHANGE REQUIREMENTS

B.1 Tier 2 Secure Email

B.1.1 When using Tier 2 secure email, the following requirements apply:

a. The sender and recipient shall use a specific email address within its organisation;

b. Secure email shall be digitally signed using, at a minimum, the S/MIME secure email format and a 1024-bit RSA digital certificate from a Certificate Authority approved by TCA;

c. Electronic registers of transmissions to and from other parties shall be maintained; and

d. Receipt of email shall be acknowledged.

B.2 Tier 2 Registered Mail

B.2.1 When using Tier 2 registered mail, the following requirements apply:

a. Sent mail shall be appropriately registered with the selected mail service to provide a ‘chain of custody’, which includes:

i) recording of the details of the posted item in a register;

ii) a return receipt that provides notification of the date of delivery and recipient signature; and

iii) restricted delivery to only a specified person or agent. b. Copies of sent and received registered mail shall be maintained for a period of time

specified by the associated application, or for 7 years by default.

B.3 Tier 2 Secure Web Portal

B.3.1 When using Tier 2 secure web portal, the following requirements apply:

a. Server-side functionality shall be provided by TCA or a TCA-approved Authority web portal;

b. When accessing the secure web portal as a client, the client shall:

i) Ensure only approved users are provided access to login credentials where applicable; and

ii) Access the secure web portal only via an up-to-date web browser or via the ASP System (for example, by an API provided by a server).

Note: Internet Explorer is not considered an up-to-date web browser, as it does not adequately support JavaScript. ASPs and Authorities may contact TCA for a list of supported web browsers and minimum browser versions.



57

B.4 Tier 2 FTPS

B.4.1 When using Tier 2 FTPS, the technical requirements specified for Tier 3 FTPS shall apply (refer to Section C.3) with the addition of the following:

a. Tier 2 FTPS shall be used to deliver technical data, reports, software, etc., that are not otherwise sent by Tier 1 or Tier 3 communication methods;

b. data provided via Tier 2 FTPS shall be delivered in a separate directory for each transaction; and

c. Tier 2 FTPS shall use basic authentication for the client.

B.5 Tier 2 Data Exchange Formats and Encoding

B.5.1 Except where otherwise approved by TCA, where the business documents and reporting artefacts defined by Section 4 are exchanged using Tier 2 Data Exchange, those business documents and reporting artefacts shall be formatted and encoded in accordance with 4.10 such that: a. as applicable and as required by the application, business documents and reporting

artefacts are formatted as XML in accordance with the XML schemas specified in Appendix B and Appendix F;





B.5.2 Where applicable, the enrolment form shall be contained in a file named as a catenation of the following data items:

a. two- or three-character Authority code;

b. underscore character (i.e. ‘_’);

c. enrolment identifier;

d. underscore character (i.e. ‘_’);

e. enrolment status as one of ‘interim’, ‘lapsed’, ‘interim-cancelled’, ‘denied’, ‘approved’, ‘ceased’ or ‘cancelled’;

f. full-stop character (i.e. ‘.’); and

g. file extension indicating the data format of the enrolment form (e.g. ‘.xml’).


58 TCA-S11-2.2

www.tca.gov.au

B.5.3 Where applicable, the enrolment report shall be contained in a file named as a catenation of the following data items:

a. two- or three-character Authority code;

b. underscore character (i.e. ‘_’);

c. enrolment report identifier;

d. full-stop character (i.e. ‘.’); and

e. file extension indicating the data format of the enrolment form (e.g. ‘.xml’).

B.6 Tier 2 Logging

B.6.1 The ASP shall keep records of all messages delivered and received concerning Tier 2 enrolment, including copies of any documents sent.



59



7.1.1 This section defines the requirements for Tier 3 Data Exchange to support data reporting for telematics applications. Depending upon the nature of the ASP System, Tier 3 Data Exchange may be human-initiated, fully-automated, or partially automated.

7.1.2 Data reporting is concerned with the periodic provision of bulk application data by the ASP to TCA for the purposes of data analysis and reporting, data assurance and application auditing. The application data provided by the ASP to TCA for a given data collection period is termed a data package.

7.1.3 Tier 3 Data Exchange requirements include:

• the selection of application data for inclusion in the data package;

• the formatting of application data within the data package; and

• the transfer of application data within the data package to TCA.

7.2 Tier 3 Communication Methods

7.2.1 Tier 3 Data Exchange supports two communication methods. Each item of application data within the data package must be transferred to TCA via one of these two methods:

• progressive transfer – items may be transferred progressively during the data collection period (as they become available) by reusing the services of the RESTful API defined for the purposes of Tier 1 Data Exchange (see Section 5); or

• bulk transfer – items may be transferred in bulk at the end of the data collection period by combining the items into a single file that is transferred to TCA using FTPS.

Note: The use of the bulk transfer method at the end of the data collection period applies only to items that have not been progressively transferred during the data collection period, and is not required where all items within the data package have already been transferred via the progressive transfer method. If no progressive transfer of items has occurred during the data collection period, bulk transfer will include all application data items within the data package.


60 TCA-S11-2.2

www.tca.gov.au

PART C TIER 3 DATA EXCHANGE REQUIREMENTS

C.1 Data Reporting

C.1.1 The ASP shall report to TCA application data for the data collection period as specified by the application.

Note: The data collection period will encompass a whole number of UTC days, and successive data collection periods are contiguous and non-overlapping. For example, the data collection period for an application may be per calendar month, per fortnight, or per week.

C.1.2 If an ASP reports data for multiple applications, and subject to the approval of TCA, the ASP may report data for some or all those applications (the combined applications) in combination such that:

a. the data collection period is the shortest of the data collection periods specified by the combined applications;

b. the content of the application-specific items of data is unaffected by the combined data reporting;

c. data records relevant to more than one combined application are reported once only (not once per application), and include all data elements required by at least one of the combined applications; and

d. if a data reporting manifest is required by at least one of the combined applications, a single data reporting manifest is generated encompassing all of the data reported for all of the combined applications.

Note:

i) For example, where an ASP combines data reporting for three applications with respective data collection periods of per calendar month, per fortnight, and per week, the ASP would meet the requirements of all three applications through a data collection period of per week.

ii) Application-specific items of data are enrolment forms, off-the-shelf conditions, event reports, and enrolment reports. These items of data are included in combined data reporting, but their content is unaltered and they remain application-specific. Data records are not considered application-specific, even if required by only one of the combined applications.

C.2 Data Selection

C.2.1 Subject to the requirements of the application, the ASP shall include in the data package for the application the following reportable data items from the data collection period, including:

a. enrolment forms and off-the-shelf conditions (refer to C.3); b. event reports (refer to C.4); c. enrolment reports (refer to C.5); d. data records (refer to C.6); and e. a data report manifest (refer to C.7).

Note: Some application data items apply only to assessment applications.



61

C.3 Enrolment Form Data

C.3.1 Unless stated otherwise by the application, the ASP shall include in the data package all versions of all enrolment forms for the application that:

a. were active at the commencement of the data collection period, and that have not been reported for a prior data collection period; or

b. were formally issued during the data collection period.

Note: A version of an enrolment form is the formal representation of the enrolment in a specific state – for example, interim approved, approved, or cancelled. The date and time that the version of the enrolment form was issued is the effective date and time that the enrolment transitioned to that state. For example, where a version of an enrolment form represents the cancellation of an enrolment, the issue date and time of that version of the enrolment form is the date and time when the enrolment was formally cancelled.

C.3.2 The ASP shall include in the data package all off-the-shelf conditions that are referenced by any reported enrolment form, including all revisions of the off-the-shelf conditions that were active for any part of the data collection period.

Note: Off-the-shelf conditions are only relevant to assessment applications.

C.4 Event Report Data

C.4.1 The ASP shall include in the data package all event reports for the application which have an audit reference date and time that falls within the data collection period. Note: Event reports are relevant only to assessment applications. To meet this requirement, the ASP must translate the audit reference date and time to UTC so that a determination can be made whether it falls within the data collection period.

C.5 Enrolment Report Data

C.5.1 The ASP shall include in the data package all enrolment reports for the application for which the enrolment reporting period ends during the data reporting collection period.

C.6 Data Record Data

C.6.1 The ASP shall include in the data package all data records required by the application for which the record date and time is both: a. during the data reporting collection period; and

b. during a period where there was at least one active enrolment in the application for the vehicle.

C.6.2 For the purposes of reporting data records in accordance with C.6.1, the ASP shall group reported data records as either: a. device data record sets (refer to C.6.3); or

b. data record batches (refer to C.6.4).

Note: The ASP must not combine data record grouping mechanisms specified in subclauses (a) and (b) within a single data package. Where data packages are combined for multiple applications, a consistent approach to data record grouping must be employed across those applications.


62 TCA-S11-2.2

www.tca.gov.au

C.6.3 If the ASP groups reported data records as device data record sets, each device data record set shall contain all reported data records generated by a single telematics device on a single UTC date (as determined by record date and time).

C.6.4 If the ASP groups reported data records as data record batches, the ASP shall form data record batches such that each: a. is assigned a unique identifier by the ASP using a prefix allocated by TCA;

b. contains data records from one or more telematics devices;

c. contains only data records from a single UTC date (as determined by record date and time);

d. contains no more than 1,000 data records; and

e. if required by the application, does not include any reported data record unless all prior reported data records from the same telematics device and same record numbering sequence are included within the same data record batch or a prior data record batch.

Note: Subclause (e) ensures that TCA receives data records in order and has confidence that gaps in reported data records represent missing data records. This requirement is strictly per device and does not apply across multiple devices.

C.7 Data Reporting Manifest Data

C.7.1 If required by the application, the ASP shall include a data reporting manifest in the data package, comprising: a. the identity of the ASP;

b. the data collection period;

c. the application(s) for which data is being reported;

d. the identifier of each enrolment form within the data package;

e. the identifier of each event report within the data package;

f. the identifier of each enrolment report within the data package;

g. details of each group of data records within the data package, being either the identifier for each data record batch, or the device identifier and UTC date for each device data record set; and

h. as applicable, to each item of application data listed in the data reporting manifest, the date and time when that item was transferred to TCA using the progressive transfer method (refer to C.8).

Note: The function of the data reporting manifest is to ensure that all application data items within the data package have been transferred to (and received by) TCA. Therefore, all application data items meeting the requirements of C.2.1 must be listed within the data reporting manifest irrespective of whether they have been successfully transferred to TCA.



63

C.8 Tier 3 Data Exchange Formats and Encoding

C.8.1 The participant shall format and encode all business documents and reporting artefacts exchanged using Tier 1 Data Exchange in accordance with 4.10 such that: a. as applicable and as required by the application, business documents and reporting

artefacts are formatted as XML in accordance with the XML schemas specified in Appendix B and Appendix F;





C.9 Progressive Transfer Method

C.9.1 Subject to the agreement of TCA, the ASP may transfer data package items to TCA individually and progressively (as they become available) by reusing the services of the RESTful API defined for the purposes of Tier 1 Data Exchange as follows: a. enrolment forms – using the Notify Enrolment service (refer to 5.3);

b. event reports using – the Notify Event Report service (refer to 5.9);

c. enrolment reports – using the Notify Enrolment Report service (refer to 5.10);

d. data record batches – using the Notify Data Records service (refer to 5.11); and

e. data reporting manifest – using the Notify Data Report service (refer to 5.12).

Note:

i) Data records grouped as device data record sets cannot be transferred via the progressive transfer method. If using the progressive transfer method, the ASP must group reportable data records as data record batches.

ii) Where TCA has agreed to the use of progressive data transfer for data reporting, the ASP is not required to provide off-the-shelf conditions in accordance with the requirements of C.3.2; TCA will source the conditions from the Authority in this case.

C.9.2 Where an item of application data is transferred in accordance with C.9.1, the ASP shall ensure the transfer occurs no later than the equivalent bulk transfer of the item would have occurred (refer to C.10). Note: The intention of the progressive transfer method is to allow for timely delivery of data to TCA, and for efficient load management by both the ASP and TCA. Therefore, it is expected that transfer of application data by this method will occur at (or soon after) the time when the data becomes available to the ASP.


64 TCA-S11-2.2

www.tca.gov.au

C.9.3 The ASP shall not transfer the data reporting manifest in accordance with C.9.1 unless all other application data items from the data package have already been transferred in accordance with C.9.1. Note: If any item of application data within the data package is not transferred via the progressive transfer method (i.e. is transferred by the bulk transfer method), then the data reporting manifest must be transferred via the bulk transfer method.

C.10 Bulk Transfer Method

C.10.1 At the end of the data collection period, the ASP shall package the application data items that comprise the data package such that: a. items that have already been transferred using the progressive transfer method

(refer to C.9.1) are excluded from this requirement;

b. each item is packaged in an individual file, with the content of that file meeting the data format and encoding requirements of this specification and of the application for that data item; and

c. individual files are organised in accordance with the file naming conventions and directory structure shown in Figure 23.

Figure 23: File System Directory Structure

data

either (but not both)

<yyyymmdd>

<batch-identifier>.(xml | json)

<telematics-device-identifier>

data

<yyyymmdd>.(xml | json)

enrolment

<authority-code>_<enrolment-identifier>.xml

event-report

<authority-code>_<event-report-identifier>.xml

conditions

<authority-code>_<conditions-identifier>_<revision>.xml

enrolment-report

<authority-code>_<enrolment-report-identifier>.xml

manifest.xml



65

Note:

i) XML and JSON files are populated in accordance with XML and JSON schema definitions presented within this specification, and in accordance with the requirements of the application.

ii) Where reported data records are grouped as data record batches, the data record batches are grouped in subdirectories by UTC date (as a mechanism for reducing the number of files per directory).

iii) Where multiple versions of a single enrolment form are provided in accordance with C.3.1, the specified packaging will result in each subsequent version overwriting previous versions. The above packaging will therefore only include the most recent version of each enrolment form reported.

C.10.2 If the ASP packages data in accordance with C.10.1, the ASP may compress individual data files such that: a. file compression is achieved using any software application that allows the original

source file to be recovered by the open source program gunzip, version 1.2.4 or later; and

b. compressed files are named identically to the original source file, but with an added extension of either ‘gz’ or ‘zip’.

C.10.3 If the ASP packages data in accordance with C.10.1 and the resultant directory structure is not empty, the ASP shall transfer the packaged data such that: a. the packaged data is first combined into a single file and compressed using any

software application that allows the original source files to be recovered by the open source program gunzip, version 1.2.4 or later; and

b. data transfer is achieved using FTPS according to IETF RFC 4217 using client certificate authentication.

Note: To support the transfer of data via FTPS, TCA will provide the ASP with the address and port number with which to establish a connection, and user name and password credentials.

C.10.4 In meeting the requirements of C.10.3b, the ASP shall support PKI certificate-based authentication of the TCA server by trusting the Certificate Authority that issued the PKI certificate used by TCA. Note: TCA will provide details of the Certificate Authority using Tier 2 Data Exchange.


66 TCA-S11-2.2

www.tca.gov.au

C.11 Tier 3 Data Exchange Digital Signatures

C.11.1 If required by the application, the ASP shall digitally sign all individual data package items in accordance with A.3.6 and A.5. Note: Digital signatures are formed prior to any compression of data package items.

C.11.2 If data package items are signed in accordance with C.11.1, the ASP shall transfer the digital signature with the digitally signed data, such that: a. the digital signal is DER-encoded;

b. if the ASP packages and transfers data in accordance with C.8, digital signatures shall be transferred in accordance with A.3.6; and

c. if the ASP packages and transfers data in accordance with C.10, each digital signature shall be stored in the same directory as the signed file, in a file having the same name as the signed file with the suffix ‘.p7s’ appended.



A-1

Appendix A Acronyms and Definitions

Acronyms

Acronym Definition

API application programming interface

ASCII American Standard Code for Information Interchange

ASP Application Service Provider

B2B business to business

CMS Cryptographic Message Syntax

DER Distinguished Encoding Rules

FTPS File Transfer Protocol Secure

GDA94 Geocentric Datum of Australia 1994

IAP Intelligent Access Program

ISO International Standards Organisation

IVU in-vehicle unit

NTF National Telematics Framework

S/MIME Secure/Multipurpose Internet Mail Extensions

SOAP Simple Object Access Protocol

SRS spatial reference system

SSL Secure Sockets Layer

TCM total combination mass

TDE Telematics Data Exchange

TLS Transport Layer Security

UML Unified Modeling Language

UTC Coordinated Universal Time

XML Extensible Markup Language

XSLT Extensible Stylesheet Language Transformations


A-2 TCA-S11-2.2

www.tca.gov.au

Definitions

Term Definition

applicable vehicle category

The matching of the last known configuration against the vehicle configurations associated with applicable vehicle categories of the enrolment form.

application A capability of the NTF that provides business value to stakeholders, delivered as an assembly of policy, business components and technical components, within in the context of an identified level of assurance.

Application Service Provider (ASP)

A service provider that has been certified by TCA as meeting the requirements of one of more applications.

ASP Trading Partner

An entity that conducts business with an ASP; for example, TCA, Authorities, service providers and other commercial entities.

assessment application

A telematics application where the vehicle is enrolled in a scheme and monitored via installed type-approved telematics device(s), with data records transferred to the ASP back office. The following apply:

• operating conditions are specified, and vehicle data is assessed against these operating conditions to generate event reports (including alarm event reports);

• enrolment reports and event reports are provided to the Authority via Tier 1 Data Exchange; and

• all data pertaining to the application is provided to TCA via Tier 3 Data Exchange.

Authority An entity, associated with a jurisdiction, responsible for the administration of one or more NTF applications. An Authority may appoint an administrator to perform its functions. See also: jurisdiction.

business data Data elements that are common to data analysis, processing and telematics devices, which include the Telematics Data Dictionary, National Telematics Map, Vehicle Categories and Alarm Codes.

business documents

The set of generic documents for the enrolment and reporting of a telematics application. Includes: off-the-shelf conditions, enrolment form, event report, and enrolment report.

connected device Any device or technology connected to a telematics device.

connected device data record

A record generated by a connected device.

data package A package of information sent via Tier 3 Data Exchange for a data collection period.

data record A discrete and defined set of data elements, generated by a device.

data record batch A group of up to 1,000 data records from one or more telematics devices from a single UTC date, organised by device identifier.



A-3

Term Definition

data record set A group of all data records generated by a single device for a single UTC day.

data reporting manifest

A data integrity artefact used within data reporting that lists all items of application data nominally provided to TCA by the ASP for the data collection period.

device A telematics capability (i.e. telematics device or connected device), able to produce data records, that can exist independently or within the context of broader telematics solutions.

enrolment Both the process and outcome by which an Operator enters an Authority’s scheme. Each vehicle must be enrolled for each scheme it participates in. Enrolment also confirms the application and conditions (if applicable) that the vehicle is monitored under.

enrolment form An electronic document that formally and simultaneously records the enrolment of a vehicle within a scheme, and within the application required by that scheme.

Enrolment Manager

The entity responsible for the formal transition of enrolments between states. Other entities (e.g. the Authority, the ASP, the Operator, TCA) may be required or permitted to interact with the Enrolment Manager to request, support or facilitate specific enrolment state transitions.

enrolment report A summary of enrolments relevant to a given Authority for a specified reporting period, including any aggregated data required by specific modules.

event report A report of an event identified through processing of vehicle telematics data in the context of a vehicle enrolment and any associated operating conditions.

framing data Supplementary information associated with transferred data for purposes that include identification and security.

idempotence A property of a function or service such that the function or service has the same effect irrespective of how many times it is called with the same data.

in-vehicle unit (IVU)

The name of a telematics device in the Intelligent Access Program (IAP). See also: telematics device.

jurisdiction A geographical area containing a road network (i.e. typically an Australian state or territory). See also: Authority.

level of assurance An assurance level that supports telematics applications, structured around the intended use of a telematics application, risks being managed, and the needs and expectations of consumers and other stakeholders.


A-4 TCA-S11-2.2

www.tca.gov.au

Term Definition

monitoring application

A telematics application where the vehicle is enrolled in a scheme and monitored via installed type-approved telematics device(s), with data records transferred to the ASP back office. The following apply:

• no operating conditions are specified, and no event reports are generated or provided to the Authority; and

• a data package containing relevant collected data and enrolment reports is provided via Tier 3 Data Exchange to TCA for processing.

off-the-shelf condition

A set of operating conditions that is published by an Authority and that can be referenced in one or more enrolment forms.

operating condition A rule, placed on an enrolment, which codifies the environment in which a vehicle is used with respect to specific telematics parameters for all of part of a journey.

Operator An entity that operates one or more vehicles eligible to enter a scheme.

payload The part of transmitted data that is the intended message.

scheme A specific use of the application linked to delivering a policy objective of the Authority. Each enrolment of a vehicle in the application must specify a scheme.

telematics device The primary telematics unit which monitors parameters.

telematics device data record

A record that originates from and is generated by a telematics device.

transfer data record

A telematics device data record which contains a connected device data record.



B-1

Appendix B Telematics Data Exchange XML Schemas

IAP XML Schemas For XML schemas related to the IAP, refer to Intelligent Access Program Functional and Technical Specification, Appendix H.

Common Types Schema <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:tns="http://www.tca.gov.au/schemas/tde/core/common/2018-07" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.tca.gov.au/schemas/tde/core/common/2018-07" elementFormDefault="unqualified" version="2018-07" > <xs:annotation> <xs:documentation> <name>tde_core_common_2018-07.xsd</name> <version>2018-07</version> <description>Telematics Data Exchange - common types</description> </xs:documentation> </xs:annotation> <xs:simpleType name="PhoneNumberType"> <xs:annotation><xs:documentation> Data type for phone numbers </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:minLength value="1" /> <xs:maxLength value="20"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="VehicleBodyTypeType"> <xs:annotation><xs:documentation> Data type for vehicle body types </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:minLength value="1" /> <xs:maxLength value="20"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="VehicleMakeType"> <xs:annotation><xs:documentation> Data type vehicle make </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:minLength value="1" /> <xs:maxLength value="20"/> </xs:restriction> </xs:simpleType>


B-2 TCA-S11-2.2

www.tca.gov.au

<xs:simpleType name="VehicleModelType"> <xs:annotation><xs:documentation> Data type vehicle model </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:minLength value="1" /> <xs:maxLength value="30"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="RegistrationNumberType"> <xs:annotation><xs:documentation> Data type registration number </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:minLength value="1" /> <xs:maxLength value="10"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="VinType"> <xs:annotation><xs:documentation> Data type for VIN </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:minLength value="17" /> <xs:maxLength value="17"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="NonVinIdentifierType"> <xs:annotation><xs:documentation> Data type non-VIN identifier </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:minLength value="1" /> <xs:maxLength value="25"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="StateEnum"> <xs:annotation><xs:documentation> Australian states </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:enumeration value="NSW"/> <xs:enumeration value="VIC"/> <xs:enumeration value="QLD"/> <xs:enumeration value="SA"/> <xs:enumeration value="NT"/> <xs:enumeration value="ACT"/>



B-3

<xs:enumeration value="WA"/> <xs:enumeration value="TAS"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="RegistrationStateEnum"> <xs:annotation><xs:documentation> List of vehicle registration Jurisdictions </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:enumeration value="NSW"/> <xs:enumeration value="VIC"/> <xs:enumeration value="QLD"/> <xs:enumeration value="SA"/> <xs:enumeration value="NT"/> <xs:enumeration value="ACT"/> <xs:enumeration value="WA"/> <xs:enumeration value="TAS"/> <xs:enumeration value="FIRS"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="AuthorityCodeType"> <xs:annotation><xs:documentation> Data type for Authority codes - this allows an open-ended set of Authorities </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:pattern value="[A-Z][A-Z0-9]{1,2}" /> </xs:restriction> </xs:simpleType> <xs:simpleType name="StateAuthorityEnum"> <xs:annotation><xs:documentation> This pre-defined list is provided for convenience, but is not exhaustive as all references are to the base type AuthorityCodeType </xs:documentation></xs:annotation> <xs:restriction base="tns:AuthorityCodeType"> <xs:enumeration value="NSW"/> <xs:enumeration value="VIC"/> <xs:enumeration value="QLD"/> <xs:enumeration value="SA"/> <xs:enumeration value="NT"/> <xs:enumeration value="ACT"/> <xs:enumeration value="WA"/> <xs:enumeration value="TAS"/> <xs:enumeration value="TCA"/> </xs:restriction> </xs:simpleType>


B-4 TCA-S11-2.2

www.tca.gov.au

<xs:simpleType name="DayTypeEnum"> <xs:annotation><xs:documentation> Data type for days of week, and standard groupings of days of week </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:enumeration value="ALL"/> <xs:enumeration value="WEEKDAY"/> <xs:enumeration value="WEEKEND"/> <xs:enumeration value="SUNDAY"/> <xs:enumeration value="MONDAY"/> <xs:enumeration value="TUESDAY"/> <xs:enumeration value="WEDNESDAY"/> <xs:enumeration value="THURSDAY"/> <xs:enumeration value="FRIDAY"/> <xs:enumeration value="SATURDAY"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="AcnType"> <xs:annotation><xs:documentation> Data type for ACN (Australian Company Number) </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:pattern value="[0-9]{9}"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="AbnType"> <xs:annotation><xs:documentation> Data type for ABN (Australian Business Number) </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:pattern value="[0-9]{11}"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="PersistentIdentifierType"> <xs:annotation><xs:documentation> Data type for persistent identifier (synthetic key for database table, predominantly used for map features) </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:minLength value="1" /> <xs:maxLength value="20"/> </xs:restriction> </xs:simpleType>



B-5

<xs:complexType name="DateTimePeriodType"> <xs:annotation><xs:documentation> A date and time period </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="startDateTime" type="xs:dateTime"/> <xs:element name="endDateTime" type="xs:dateTime"/> </xs:sequence> </xs:complexType> <xs:complexType name="TimePeriodType"> <xs:annotation><xs:documentation> A period of time within a given day </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="startTime" type="xs:time"/> <xs:element name="endTime" type="xs:time"/> </xs:sequence> </xs:complexType> <xs:complexType name="VehicleIdentityType"> <xs:annotation><xs:documentation> Identification of a vehicle (prime mover, rigid truck, bus, trailer) through VIN or non-VIN identifier </xs:documentation></xs:annotation> <xs:choice> <xs:element name="vin" type="tns:VinType"/> <xs:element name="nonVinIdentifier" type="tns:NonVinIdentifierType" /> </xs:choice> </xs:complexType> <xs:complexType name="VehicleRegistrationType"> <xs:annotation><xs:documentation> Identification of a vehicle (prime mover, rigid truck, bus, trailer) through registration. </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="number" type="tns:RegistrationNumberType"/> <xs:element name="stateCode" type="tns:RegistrationStateEnum"/> </xs:sequence> </xs:complexType> <xs:complexType name="VehicleInformationType"> <xs:annotation><xs:documentation> Identification of a vehicle (prime mover, rigid truck, bus, trailer) through combination of data elements. </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="registration" type="tns:VehicleRegistrationType"/> <xs:element name="identity" type="tns:VehicleIdentityType"/> </xs:sequence> </xs:complexType>


B-6 TCA-S11-2.2

www.tca.gov.au

<xs:complexType name="AddressType"> <xs:annotation><xs:documentation> General Australian address </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="lineOne" type="xs:string" /> <xs:element name="lineTwo" type="xs:string" minOccurs="0" /> <xs:element name="locality" type="xs:string"/> <xs:element name="stateCode" type="tns:StateEnum"/> <xs:element name="postCode" type="xs:string"/> </xs:sequence> </xs:complexType> <xs:complexType name="CompanyOfficerType"> <xs:annotation><xs:documentation> Officer name and position </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="officerName" type="xs:string"/> <xs:element name="positionName" type="xs:string"/> <xs:element name="businessHoursPhone" type="tns:PhoneNumberType" /> </xs:sequence> </xs:complexType> <xs:complexType name="CompanyIdentificationType"> <xs:annotation><xs:documentation> Identity of an Australian company </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="companyName" type="xs:string"/> <xs:element name="abn" type="tns:AbnType"/> <xs:element name="acn" type="tns:AcnType" minOccurs="0"/> </xs:sequence> </xs:complexType> <xs:simpleType name="NtmVersionType"> <xs:annotation><xs:documentation> Data type for version of the NTM (e.g., TCA-IAM-MAY18) </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:maxLength value="15"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="NumberVersionType"> <xs:annotation><xs:documentation> Data type for version of the format n.nn (e.g., 1.02, 3.43) </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:pattern value="[0-9]+\.[0-9]{2}" /> </xs:restriction> </xs:simpleType>



B-7

<xs:simpleType name="ReferenceIdentifierType"> <xs:annotation><xs:documentation> A second party's reference, for example for a request or an enrolment </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:pattern value="[A-Za-z0-9\-_\.]{1,20}" /> </xs:restriction> </xs:simpleType> <xs:simpleType name="ApplicationNameType"> <xs:annotation><xs:documentation> Data type for telematics application name </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:pattern value="[A-Z_][A-Z0-9_\-]*" /> </xs:restriction> </xs:simpleType> <xs:complexType name="ApplicationReferenceType"> <xs:annotation><xs:documentation> Reference to a telematics application by application name and version </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="name" type="tns:ApplicationNameType" /> <xs:element name="version" type="tns:NumberVersionType" /> </xs:sequence> </xs:complexType> <xs:complexType name="AbstractDocumentType" abstract="true"> <xs:annotation><xs:documentation> Base type for any telematics application document (e.g. enrolment, event report, enrolment report). Every document corresponds to a single telematics application. </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="application" type="tns:ApplicationReferenceType" /> </xs:sequence> </xs:complexType> </xs:schema>


B-8 TCA-S11-2.2

www.tca.gov.au

Data Records Schema <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://www.tca.gov.au/schemas/tde/core/data-record/2018-07" targetNamespace="http://www.tca.gov.au/schemas/tde/core/data-record/2018-07" elementFormDefault="unqualified" version="2018-07" > <xs:annotation> <xs:appinfo> <xs:documentation> <name>tde_core_event-report_2018-07.xsd</name> <version>2018-07</version> <description>Telematics Data Exchange - data record definitions </description> </xs:documentation> </xs:appinfo> </xs:annotation> <xs:simpleType name="SpatialReferenceSystemType"> <xs:annotation><xs:documentation> Data type for specifying the spatial reference system (SRS) datum used to describe vehicle position </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:enumeration value="GDA94"/> <xs:enumeration value="GDA2020"/> <xs:enumeration value="WGS84"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="LocationDegreesType"> <xs:annotation><xs:documentation> Data type for latitude and longitude values </xs:documentation></xs:annotation> <xs:restriction base="xs:decimal"> <xs:totalDigits value="8" /> <xs:fractionDigits value="5" /> <xs:maxInclusive value="180" /> <xs:minInclusive value="-180" /> </xs:restriction> </xs:simpleType> <xs:simpleType name="HeadingType"> <xs:annotation><xs:documentation> Data type for direction (bearing) in degrees </xs:documentation></xs:annotation> <xs:restriction base="xs:decimal"> <xs:totalDigits value="4" /> <xs:fractionDigits value="1" /> <xs:maxExclusive value="360" /> <xs:minInclusive value="0" /> </xs:restriction> </xs:simpleType>



B-9

<xs:simpleType name="HdopValueType"> <xs:annotation><xs:documentation> Data type for horizontal dilution of precision (HDOP) </xs:documentation></xs:annotation> <xs:restriction base="xs:decimal"> <xs:totalDigits value="3" /> <xs:fractionDigits value="1" /> <xs:maxExclusive value="100" /> <xs:minInclusive value="0" /> </xs:restriction> </xs:simpleType> <xs:simpleType name="PositioningServiceAvailabilityType"> <xs:annotation><xs:documentation> Data type for the availability of the system used to determine vehicle position </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:enumeration value="UNKNOWN"/> <xs:enumeration value="UNAVAILABLE"/> <xs:enumeration value="DEGRADED"/> <xs:enumeration value="AVAILABLE"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="GenericCodeType"> <xs:annotation><xs:documentation> Data type for generic code set values </xs:documentation></xs:annotation> <xs:restriction base="xs:int"> <xs:minInclusive value="1" /> </xs:restriction> </xs:simpleType> <xs:simpleType name="DeviceIdentifierType"> <xs:annotation><xs:documentation> Data type for identifier of a device </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:minLength value="1" /> <xs:maxLength value="20"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="DeviceTypeType"> <xs:annotation><xs:documentation> Data type for type of a device, for example TD (for telematics device), IVU (in-vehicle unit), ECU (for OBM system). Note that TD and IVU are equivalent, and TD should be used except where the term IVU is explicitly used within the application specification rather than telematics device </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:enumeration value="IVU"/> <xs:enumeration value="TID"/> <xs:enumeration value="ECU"/> <xs:enumeration value="TD"/> </xs:restriction> </xs:simpleType>


B-10 TCA-S11-2.2

www.tca.gov.au

<xs:complexType name="DeviceIdentityType"> <xs:annotation><xs:documentation> Full identity of a device, including type and identifier </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="id" type="tns:DeviceIdentifierType" /> <xs:element name="type" type="tns:DeviceTypeType" minOccurs="0" /> <xs:element name="model" type="tns:DeviceModelType" minOccurs="0" /> </xs:sequence> </xs:complexType> <xs:simpleType name="SpeedUnitEnum"> <xs:annotation><xs:documentation> Data type for speed unit (always KMH in Australia) </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:enumeration value="KMH"/> <xs:enumeration value="MPH"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="SpeedValueType"> <xs:annotation><xs:documentation> Data type for speed value </xs:documentation></xs:annotation> <xs:restriction base="xs:decimal"> <xs:totalDigits value="4" /> <xs:fractionDigits value="1" /> <xs:maxExclusive value="1000" /> <xs:minInclusive value="0" /> </xs:restriction> </xs:simpleType> <xs:complexType name="SpeedType"> <xs:annotation><xs:documentation> Vehicle speed (used for speed thresholds and speed data) </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="unit" type="tns:SpeedUnitEnum" default="KMH" /> <xs:element name="value" type="tns:SpeedValueType" /> </xs:sequence> </xs:complexType> <xs:complexType name="PointType"> <xs:annotation><xs:documentation> A geographic point (e.g. for vehicle location) </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="longitude" type="tns:LocationDegreesType"/> <xs:element name="latitude" type="tns:LocationDegreesType"/> </xs:sequence> </xs:complexType>



B-11

<xs:complexType name="DeviceDataRecordType" abstract="true"> <xs:annotation><xs:documentation> Base type for a data record collected by a telematics device (including a connected device). Note that the date time is a UTC date time. </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="deviceId" type="tns:DeviceIdentifierType" minOccurs="0" /> <xs:element name="number" type="xs:long" minOccurs="0" /> <xs:element name="dateTime" type="xs:dateTime" /> </xs:sequence> </xs:complexType> <xs:complexType name="DeviceTransferRecordType"> <xs:annotation><xs:documentation> A data transfer record (i.e., data record that wraps another data record for the purposes of getting it back to base). The wrapped data record is generated by a connected device. </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="tns:DeviceDataRecordType" > <xs:sequence> <xs:element name="connectedDevice" type="tns:DeviceIdentityType" /> <xs:choice> <xs:element name="obmSystemMassRecord" type="tns:ObmSystemMassRecordType" /> <xs:element name="obmSystemConfigurationRecord" type="tns:ObmSystemConfigurationRecordType" /> <xs:element name="obmSystemAlarmRecord" type="tns:ObmSystemAlarmRecordType" /> <xs:element name="obmSystemQualityRecord" type="tns:ObmSystemQualityRecordType" /> </xs:choice> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="DeviceAlarmRecordType"> <xs:annotation><xs:documentation> An alarm record collected from a device. Optionally the alarm record can include the details of a connected device where the alarm relates to (but was not collected on) that connected device (e.g. the alarm indicates that the connected device was not responding). </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="tns:DeviceDataRecordType"> <xs:sequence> <xs:element name="code" type="tns:GenericCodeType" /> <xs:element name="connectedDevice" type="tns:DeviceIdentityType" minOccurs="0" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:simpleType name="IgnitionStatusEnum" > <xs:annotation><xs:documentation> Ignition status values </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:enumeration value="ON" /> <xs:enumeration value="OFF" /> <xs:enumeration value="DISCONNECTED" /> </xs:restriction> </xs:simpleType>


B-12 TCA-S11-2.2

www.tca.gov.au

<xs:simpleType name="MovementSensorStatusEnum" > <xs:annotation><xs:documentation> Movement sensor values </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:enumeration value="MOVEMENT" /> <xs:enumeration value="NO_MOVEMENT" /> <xs:enumeration value="DISCONNECTED" /> </xs:restriction> </xs:simpleType> <xs:simpleType name="VehicleLoadStatusEnum"> <xs:annotation><xs:documentation> Vehicle load status values </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:enumeration value="LOAD"/> <xs:enumeration value="NO_LOAD"/> </xs:restriction> </xs:simpleType> <xs:complexType name="DevicePositionRecordType"> <xs:annotation><xs:documentation> Position record as collected by the telematics device </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="tns:DeviceDataRecordType"> <xs:sequence> <xs:element name="position" type="tns:PointType" minOccurs="0" /> <xs:element name="direction" type="tns:HeadingType" minOccurs="0" /> <xs:element name="speed" type="tns:SpeedType" minOccurs="0" /> <xs:element name="satelliteCount" type="xs:int" minOccurs="0" /> <xs:element name="service" type="tns:PositioningServiceAvailabilityType" minOccurs="0" /> <xs:element name="hdop" type="tns:HdopValueType" minOccurs="0" /> <xs:element name="ignition" type="tns:IgnitionStatusEnum" minOccurs="0" /> <xs:element name="movementSensor" type="tns:MovementSensorStatusEnum" minOccurs="0" /> <xs:element name="tidId" type="tns:DeviceIdentifierType" minOccurs="0" maxOccurs="unbounded" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="DeviceSpeedRecordType"> <xs:annotation><xs:documentation> Speed record as collected by the telematics device </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="tns:DeviceDataRecordType"> <xs:sequence> <xs:element name="position" type="tns:PointType" minOccurs="0" /> <xs:element name="speed" type="tns:SpeedType" minOccurs="0" /> <xs:element name="satelliteCount" type="xs:int" minOccurs="0" /> <xs:element name="service" type="tns:PositioningServiceAvailabilityType" minOccurs="0" />



B-13

<xs:element name="hdop" type="tns:HdopValueType" minOccurs="0" /> <xs:element name="tidId" type="tns:DeviceIdentifierType" minOccurs="0" maxOccurs="unbounded" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:simpleType name="SdCodesetVersionType"> <xs:annotation><xs:documentation> Verison of the SD codeset </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:minLength value="1"/> <xs:maxLength value="10"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="SdCommentTextType"> <xs:annotation><xs:documentation> Data type for SD comment text </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:maxLength value="256"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="SdVehicleMassType"> <xs:annotation><xs:documentation> Data type for SD vehicle mass </xs:documentation></xs:annotation> <xs:restriction base="xs:decimal"> <xs:totalDigits value="4" /> <xs:fractionDigits value="1" /> <xs:minInclusive value="0" /> <xs:maxExclusive value="1000.0" /> </xs:restriction> </xs:simpleType> <xs:simpleType name="SdVehicleCategoryType"> <xs:annotation><xs:documentation> Data type for SD vehicle category </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:minLength value="1"/> </xs:restriction> </xs:simpleType>


B-14 TCA-S11-2.2

www.tca.gov.au

<xs:complexType name="DeviceSdCommentRecordType"> <xs:annotation><xs:documentation> SD (comment) record as collected by the user interface </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="tns:DeviceDataRecordType"> <xs:sequence> <xs:element name="version" type="tns:SdCodesetVersionType" minOccurs="0" /> <xs:element name="comment" type="tns:GenericCodeType" minOccurs="0" /> <xs:element name="commentName" type="xs:string" minOccurs="0" /> <xs:element name="commentText" type="tns:SdCommentTextType" minOccurs="0" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="DeviceSdTcmRecordType"> <xs:annotation><xs:documentation> SD (vehicle type/TCM) record as collected by the user interface </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="tns:DeviceDataRecordType"> <xs:sequence> <xs:element name="version" type="tns:SdCodesetVersionType" minOccurs="0" /> <xs:element name="category" type="tns:GenericCodeType" minOccurs="0" /> <xs:element name="categoryName" type="tns:SdVehicleCategoryType" minOccurs="0" /> <xs:element name="axleCount" type="xs:int" minOccurs="0" /> <xs:element name="load" type="tns:VehicleLoadStatusEnum" minOccurs="0" /> <xs:element name="mass" type="tns:SdVehicleMassType" minOccurs="0" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:simpleType name="VehicleMassType"> <xs:annotation><xs:documentation> Data type for a vehicle mass or axle group mass reading </xs:documentation></xs:annotation> <xs:restriction base="xs:int"> <xs:minInclusive value="0" /> <xs:maxInclusive value="999999" /> </xs:restriction> </xs:simpleType> <xs:simpleType name="VehicleMassListType"> <xs:annotation><xs:documentation> Data type for a list of vehicle masses </xs:documentation></xs:annotation> <xs:list itemType="tns:VehicleMassType" > </xs:list> </xs:simpleType>



B-15

<xs:simpleType name="LiftAxleStatusEnum" > <xs:annotation><xs:documentation> Movement sensor values </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:enumeration value="NONE" /> <xs:enumeration value="FITTED" /> <xs:enumeration value="RAISED" /> <xs:enumeration value="LOWERED" /> </xs:restriction> </xs:simpleType> <xs:complexType name="ObmSystemRecordType" abstract="true"> <xs:annotation><xs:documentation> Base type for data records collected by an OBM system (which will always be connected via the telematics device) </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="tns:DeviceDataRecordType"> <xs:sequence> <xs:element name="version" type="xs:int" minOccurs="0" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="ObmSystemConfigurationSubRecordType"> <xs:annotation><xs:documentation> Per-MSU sub-record of the configuration record as collected by an OBM system </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="msuSequence" type="xs:int" minOccurs="0" /> <xs:element name="msuId" type="tns:DeviceIdentifierType" /> </xs:sequence> </xs:complexType> <xs:complexType name="ObmSystemConfigurationRecordType"> <xs:annotation><xs:documentation> Configuration record as collected by an OBM system </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="tns:ObmSystemRecordType"> <xs:sequence minOccurs="0" > <xs:element name="msuCount" type="xs:int" /> <xs:element name="msuRecord" type="tns:ObmSystemConfigurationSubRecordType" maxOccurs="unbounded" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>


B-16 TCA-S11-2.2

www.tca.gov.au

<xs:complexType name="ObmSystemMassSubRecordType"> <xs:annotation><xs:documentation> Per-MSU sub-reocrd of the mass record as colelcted by an OBM system </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="msuSequence" type="xs:int" minOccurs="0" /> <xs:element name="msuId" type="tns:DeviceIdentifierType" /> <xs:element name="liftAxle" type="tns:LiftAxleStatusEnum" minOccurs="0" /> <xs:element name="mass" type="tns:VehicleMassType" minOccurs="0" /> </xs:sequence> </xs:complexType> <xs:complexType name="ObmSystemMassRecordType"> <xs:annotation><xs:documentation> Mass record as collected by an OBM system </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="tns:ObmSystemRecordType"> <xs:sequence> <xs:element name="mass" type="tns:VehicleMassType" minOccurs="0" /> <xs:sequence minOccurs="0" > <xs:element name="msuCount" type="xs:int" /> <xs:element name="msuRecord" type="tns:ObmSystemMassSubRecordType" maxOccurs="unbounded" /> </xs:sequence> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="ObmSystemQualityRecordType"> <xs:annotation><xs:documentation> Quality record as colelcted by an OBM system </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="tns:ObmSystemRecordType"> <xs:sequence> <xs:element name="msuCount" type="xs:int" minOccurs="0" /> <xs:element name="msuSequence" type="xs:int" minOccurs="0" /> <xs:element name="msuId" type="tns:DeviceIdentifierType" /> <xs:element name="liftAxle" type="tns:LiftAxleStatusEnum" minOccurs="0" /> <xs:element name="dataFrequency" type="xs:int" minOccurs="0" /> <xs:element name="dataCount" type="xs:int" minOccurs="0" /> <xs:element name="massData" type="tns:VehicleMassListType" minOccurs="0" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>



B-17

<xs:complexType name="ObmSystemAlarmRecordType"> <xs:annotation><xs:documentation> Alarm record as colelcted by an OBM system </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="tns:ObmSystemRecordType"> <xs:sequence> <xs:element name="code" type="tns:GenericCodeType" /> <xs:sequence > <xs:element name="msuId" type="tns:DeviceIdentifierType" /> <xs:element name="msuSequence" type="xs:int" minOccurs="0" /> </xs:sequence> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="ReceivedDataRecordType"> <xs:annotation><xs:documentation> </xs:documentation></xs:annotation> <xs:sequence> <xs:choice minOccurs="0" maxOccurs="unbounded" > <xs:element name="positionRecord" type="tns:DevicePositionRecordType" /> <xs:sequence> <xs:element name="speedRecord" type="tns:DeviceSpeedRecordType" /> <xs:element name="speedThreshold" type="tns:SpeedType" minOccurs="0" /> </xs:sequence> <xs:element name="alarmRecord" type="tns:DeviceAlarmRecordType" /> <xs:element name="sdCommentRecord" type="tns:DeviceSdCommentRecordType" /> <xs:element name="sdTcmRecord" type="tns:DeviceSdTcmRecordType" /> <xs:element name="transferRecord" type="tns:DeviceTransferRecordType" /> <xs:element name="obmAlarmRecord" type="tns:ObmSystemAlarmRecordType" /> <xs:element name="obmConfigurationRecord" type="tns:ObmSystemConfigurationRecordType" /> <xs:element name="obmMassRecord" type="tns:ObmSystemMassRecordType" /> <xs:element name="obmQualityRecord" type="tns:ObmSystemQualityRecordType" /> </xs:choice> <xs:element name="receiptDateTime" type="xs:dateTime" /> </xs:sequence> </xs:complexType> <xs:complexType name="ReceivedDataRecordsType"> <xs:annotation><xs:documentation> </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="device" type="tns:DeviceIdentityType" /> <xs:element name="srs" type="tns:SpatialReferenceSystemType" minOccurs="0" default="GDA94" /> <xs:element name="record" type="tns:ReceivedDataRecordType" minOccurs="0" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> <xs:simpleType name="ReceivedDataRecordsBatchIdentifierType"> <xs:annotation><xs:documentation> Data records batch identifier </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:pattern value="[a-zA-Z0-9]{3}[0-9]{12}" /> </xs:restriction> </xs:simpleType>


B-18 TCA-S11-2.2

www.tca.gov.au

<xs:complexType name="ReceivedDataRecordsBatchType"> <xs:annotation><xs:documentation> </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="batchId" type="tns:ReceivedDataRecordsBatchIdentifierType" /> <xs:element name="deviceRecords" type="tns:ReceivedDataRecordsType" minOccurs="0" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> <xs:element name="dataRecords" type="tns:ReceivedDataRecordsType" /> <xs:element name="dataRecordsBatch" type="tns:ReceivedDataRecordsBatchType" /> </xs:schema>



B-19

Conditions Schema <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:tns="http://www.tca.gov.au/schemas/tde/core/conditions/2018-07" xmlns:common="http://www.tca.gov.au/schemas/tde/core/common/2018-07" xmlns:data="http://www.tca.gov.au/schemas/tde/core/data-record/2018-07" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.tca.gov.au/schemas/tde/core/conditions/2018-07" elementFormDefault="unqualified" version="2018-07" > <xs:annotation> <xs:documentation> <name>tde_core_conditions_2018-07.xsd</name> <version>2018-07</version> <description>Telematics Data Exchange - conditions definition</description> </xs:documentation> </xs:annotation> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/common/2018-07" schemaLocation="tde_core_common_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/data-record/2018-07" schemaLocation="tde_core_data-record_2018-07.xsd"/> <xs:simpleType name="SchemeNameType"> <xs:annotation><xs:documentation> Data type for name of a scheme </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:minLength value="1" /> <xs:maxLength value="50"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="OffTheShelfConditionsIdentifierType"> <xs:annotation><xs:documentation> Data type for off-the-shelf conditions identifier </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:minLength value="1" /> <xs:maxLength value="15"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="OffTheShelfConditionsRevisionType"> <xs:annotation><xs:documentation> Data type for off-the-shelf conditions revision </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:minLength value="1" /> <xs:maxLength value="10"/> </xs:restriction> </xs:simpleType>


B-20 TCA-S11-2.2

www.tca.gov.au

<xs:complexType name="OffTheShelfConditionsReferenceType"> <xs:annotation><xs:documentation> Reference to a specific revision of an off-the-shelf conditions document </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="identifier" type="tns:OffTheShelfConditionsIdentifierType" /> <xs:element name="revision" type="tns:OffTheShelfConditionsRevisionType" /> </xs:sequence> </xs:complexType> <xs:simpleType name="OperatingConditionIdentifierType"> <xs:annotation><xs:documentation> Data type for the identifier for a single operating condition. Generally used for qualifying conditions such that they can be referenced from a base condition, but also useful to name base conditions to enhance readability. </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:minLength value="1" /> </xs:restriction> </xs:simpleType> <xs:complexType name="QualifyingConditionReferenceType" > <xs:annotation><xs:documentation> References a qualifying condition, optionally inverted (but not by default) </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="identifier" type="tns:OperatingConditionIdentifierType" /> <xs:element name="inverted" type="xs:boolean" minOccurs="0" default="false" /> </xs:sequence> </xs:complexType> <xs:complexType name="OperatingConditionType" abstract="true"> <xs:annotation><xs:documentation> Base type for operating conditions, including references to qualifying conditions. Note that conditions are not structurally base conditions or qualifying conditions </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="identifier" type="tns:OperatingConditionIdentifierType" minOccurs="0" /> <xs:element name="description" type="xs:string" minOccurs="0" /> <xs:element name="qualifyingCondition" type="tns:QualifyingConditionReferenceType" minOccurs="0" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> <xs:complexType name="ConditionsExtensionType" abstract="true"> <xs:annotation><xs:documentation> Allows modules and applications to extend conditions with application-specific content. </xs:documentation></xs:annotation> </xs:complexType> <xs:complexType name="AbstractBoundaryType" abstract="true"> <xs:annotation><xs:documentation> Base type for boundary (used for area of interest) - where a boundary exists, monitoring or assessment only considers that portion of the Jurisdiction within this boundary. </xs:documentation></xs:annotation> </xs:complexType>



B-21

<xs:complexType name="CircleBoundaryType"> <xs:annotation><xs:documentation> Boundary defined by a centre point and a radius (in metres) </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="tns:AbstractBoundaryType"> <xs:sequence> <xs:element name="centre" type="data:PointType" /> <xs:element name="radius" type="xs:double" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="RectangleBoundaryType"> <xs:annotation><xs:documentation> Boundary defined by four sides </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="tns:AbstractBoundaryType"> <xs:sequence> <xs:element name="north" type="data:LocationDegreesType" /> <xs:element name="south" type="data:LocationDegreesType" /> <xs:element name="west" type="data:LocationDegreesType" /> <xs:element name="east" type="data:LocationDegreesType" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="PolygonBoundaryType"> <xs:annotation><xs:documentation> Boundary defined by a closed polygon, with an implicit edge between each adjacent pair of verticies, and between the first and the last vertices. </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="tns:AbstractBoundaryType"> <xs:sequence> <xs:element name="vertex" type="data:PointType" minOccurs="2" maxOccurs="unbounded" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="ConditionsType"> <xs:annotation><xs:documentation> Specification of conditions, as used within unique conditions (with enrolment) or within off-the-shelf conditions. </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="qualifyingCondition" type="tns:OperatingConditionType" minOccurs="0" maxOccurs="unbounded" /> <xs:element name="baseCondition" type="tns:OperatingConditionType" maxOccurs="unbounded" /> <xs:element name="extension" type="tns:ConditionsExtensionType" minOccurs="0" maxOccurs="unbounded" /> <xs:element name="comments" type="xs:string" minOccurs="0"/> </xs:sequence> </xs:complexType>


B-22 TCA-S11-2.2

www.tca.gov.au

<xs:complexType name="OffTheShelfConditionsType"> <xs:annotation><xs:documentation> off-the-shelf conditions document. </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="common:AbstractDocumentType"> <xs:sequence> <xs:element name="identifier" type="tns:OffTheShelfConditionsIdentifierType"/> <xs:element name="revision" type="tns:OffTheShelfConditionsRevisionType"/> <xs:element name="scheme" type="tns:SchemeNameType" /> <xs:element name="validFromDateTime" type="xs:dateTime"/> <xs:element name="validToDateTime" type="xs:dateTime" minOccurs="0" /> <xs:element name="authorityCode" type="common:AuthorityCodeType"/> <xs:element name="conditions" type="tns:ConditionsType"/> <xs:element name="authorisingOfficer" type="common:CompanyOfficerType" /> <xs:element name="issuedDateTime" type="xs:dateTime" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:element name="offTheShelfConditions" type="tns:OffTheShelfConditionsType"/> </xs:schema>



B-23

Enrolment Schema <?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="http://www.tca.gov.au/schemas/tde/core/enrolment/2018-07" xmlns:tns="http://www.tca.gov.au/schemas/tde/core/enrolment/2018-07" xmlns:common="http://www.tca.gov.au/schemas/tde/core/common/2018-07" xmlns:data="http://www.tca.gov.au/schemas/tde/core/data-record/2018-07" xmlns:cond="http://www.tca.gov.au/schemas/tde/core/conditions/2018-07" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="unqualified" version="2018-07" > <xs:annotation> <xs:documentation> <name>tde_core_enrolment_2018-07.xsd</name> <version>2018-07</version> <description>Telematics Data Exchange - enrolment form definition </description> </xs:documentation> </xs:annotation> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/common/2018-07" schemaLocation="tde_core_common_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/data-record/2018-07" schemaLocation="tde_core_data-record_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/conditions/2018-07" schemaLocation="tde_core_conditions_2018-07.xsd"/> <xs:simpleType name="EnrolmentIdentifierType"> <xs:annotation><xs:documentation> The format of this string is either AXXNNNNNNNN or AAANNNNNNNN, where: * AXX represents a TCA-assigned identifier for the Enrolment Manager and is of the format 1 alpha followed by 2 digits * AAA represents a TCA-assigned identifier for the Enrolment Manager and is of the format 3 alpha * NNNNNNNN is a number assigned by the Authority or ASP (service provider) </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:pattern value="(([a-zA-Z]{1}[0-9]{2})|([a-zA-Z]{3}))[0-9]{8}"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="EnrolmentProcessEnum"> <xs:annotation><xs:documentation> Standard enrolment statuses </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:enumeration value="AUTHORITY"/> <xs:enumeration value="ASP"/> </xs:restriction> </xs:simpleType>


B-24 TCA-S11-2.2

www.tca.gov.au

<xs:complexType name="DeviceInstallationType"> <xs:annotation><xs:documentation> Describes the installation of a telematics device </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="deviceIdentity" type="data:DeviceIdentityType"/> <xs:element name="installationDateTime" type="xs:dateTime"/> <xs:element name="deviceLocation" type="xs:string"/> <xs:element name="gpsAntennaLocation" type="xs:string" minOccurs="0"> </xs:element> </xs:sequence> </xs:complexType> <xs:complexType name="VehicleInstallationType"> <xs:annotation><xs:documentation> Describes the installation of one or more telematics devies on a vehicle </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="vehicleIdentity" type="common:VehicleIdentityType" /> <xs:element name="installedDevice" type="tns:DeviceInstallationType" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> <xs:complexType name="PrimaryUnitInstallationType"> <xs:annotation><xs:documentation> Describes the installation of one or more telematics devies on a prime mover/rigid truck </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="tns:VehicleInstallationType"> </xs:extension> </xs:complexContent> </xs:complexType> <xs:simpleType name="EnrolmentStatusEnum"> <xs:annotation><xs:documentation> Standard enrolment statuses </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:enumeration value="INTERIM"/> <xs:enumeration value="INTERIM_CANCELLED"/> <xs:enumeration value="LAPSED"/> <xs:enumeration value="DENIED"/> <xs:enumeration value="APPROVED"/> <xs:enumeration value="CEASED"/> <xs:enumeration value="CANCELLED"/> </xs:restriction> </xs:simpleType>



B-25

<xs:complexType name="PrimaryUnitInformationType"> <xs:annotation><xs:documentation> Information about the prime mover/rigid truck </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="common: VehicleInformationType"> <xs:sequence> <xs:element name="make" type="common:VehicleMakeType" minOccurs="0" /> <xs:element name="model" type="common:VehicleModelType" minOccurs="0" /> <xs:element name="garagingAddress" type="common:AddressType" minOccurs="0"/> <xs:element name="bodyType" type="common:VehicleBodyTypeType" minOccurs="0"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="AuthorityInformationType"> <xs:annotation><xs:documentation> Identity and contact information for the Authority </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="authorityCode" type="common:AuthorityCodeType"/> <xs:element name="postalAddress" type="common:AddressType" /> <xs:element name="businessHoursPhone" type="common:PhoneNumberType" /> <xs:element name="fax" type="common:PhoneNumberType" minOccurs="0" /> <xs:element name="emailAddress" type="xs:string" minOccurs="0" /> </xs:sequence> </xs:complexType> <xs:complexType name="AuthoritySectionType"> <xs:annotation><xs:documentation> Conditions only include operating conditions (including via off-the-shelf conditions) where the application is an assessment application. </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="authority" type="tns:AuthorityInformationType"/> <xs:element name="scheme" type="cond:SchemeNameType" /> <xs:choice minOccurs="0" > <xs:element name="offTheShelfConditionsIdentifier" type="cond:OffTheShelfConditionsIdentifierType"/> <xs:element name="uniqueConditions" type="cond:ConditionsType"/> </xs:choice> </xs:sequence> </xs:complexType> <xs:complexType name="OperatorIdentificationType"> <xs:annotation><xs:documentation> Information about the Operator's company identity </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="common:CompanyIdentificationType"> <xs:sequence> <xs:element name="name" type="xs:string" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>


B-26 TCA-S11-2.2

www.tca.gov.au

<xs:complexType name="OperatorInformationType"> <xs:annotation><xs:documentation> Identity and contact information for the Operator </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="identity" type="tns:OperatorIdentificationType" /> <xs:element name="postalAddress" type="common:AddressType" /> <xs:element name="businessHoursPhone" type="common:PhoneNumberType" /> <xs:element name="afterHoursPhone" type="common:PhoneNumberType" minOccurs="0" /> <xs:element name="fax" type="common:PhoneNumberType" minOccurs="0"/> <xs:element name="emailAddress" type="xs:string" minOccurs="0" /> </xs:sequence> </xs:complexType> <xs:complexType name="OperatorSectionExtensionType" abstract="true"> <xs:annotation><xs:documentation> Base type for additional information regarding the Operator or vehicle (e.g., requirements for additional type-approved devices). </xs:documentation></xs:annotation> </xs:complexType> <xs:complexType name="OperatorSectionType"> <xs:annotation><xs:documentation> Information about the Operator and the vehicle </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="operator" type="tns:OperatorInformationType" /> <xs:element name="nominatedOfficer" type="common:CompanyOfficerType" minOccurs="0" /> <xs:element name="primaryUnitInformation" type="tns:PrimaryUnitInformationType"/> <xs:element name="extension" type="tns:OperatorSectionExtensionType" minOccurs="0" maxOccurs="unbounded" /> <xs:element name="comments" type="xs:string" minOccurs="0"/> </xs:sequence> </xs:complexType> <xs:complexType name="ServiceProviderInformationType"> <xs:annotation><xs:documentation> Identity and contact information for the ASP </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="identity" type="common:CompanyIdentificationType" /> <xs:element name="postalAddress" type="common:AddressType"/> <xs:element name="businessHoursPhone" type="common:PhoneNumberType" /> <xs:element name="fax" type="common:PhoneNumberType" minOccurs="0" /> <xs:element name="emailAddress" type="xs:string" minOccurs="0" /> </xs:sequence> </xs:complexType> <xs:complexType name="ServiceProviderSectionExtensionType" abstract="true"> <xs:annotation><xs:documentation> Base type for additional information regarding the ASP and/or telematics device installation </xs:documentation></xs:annotation> </xs:complexType>



B-27

<xs:complexType name="ServiceProviderSectionType"> <xs:annotation><xs:documentation> Information about the ASP and/or telematics device installation </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="serviceProvider" type="tns:ServiceProviderInformationType" /> <xs:element name="primaryUnitInstallation" type="tns:PrimaryUnitInstallationType"/> <xs:element name="extension" type="tns:ServiceProviderSectionExtensionType" minOccurs="0" maxOccurs="unbounded" /> <xs:element name="comments" type="xs:string" minOccurs="0"/> <xs:element name="issuedDateTime" type="xs:dateTime" /> </xs:sequence> </xs:complexType> <xs:complexType name="InterimApprovalSectionType"> <xs:annotation><xs:documentation> The formal interim approval (not relevant to ASP-managed approval) </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="lapseDateTime" type="xs:dateTime" /> <xs:element name="comments" type="xs:string" minOccurs="0"/> <xs:element name="authorisingOfficer" type="common:CompanyOfficerType" minOccurs="0" /> <xs:element name="issuedDateTime" type="xs:dateTime" /> </xs:sequence> </xs:complexType> <xs:complexType name="ApprovalSectionType"> <xs:annotation><xs:documentation> The formal approval/denial of the enrolment </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="approved" type="xs:boolean" /> <xs:element name="comments" type="xs:string" minOccurs="0"/> <xs:element name="authorisingOfficer" type="common:CompanyOfficerType" /> <xs:element name="issuedDateTime" type="xs:dateTime" /> </xs:sequence> </xs:complexType> <xs:complexType name="CancellationSectionType"> <xs:annotation><xs:documentation> Information about the cancellation of the enrolment </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="comments" type="xs:string" minOccurs="0"/> <xs:element name="authorisingOfficer" type="common:CompanyOfficerType" /> <xs:element name="issuedDateTime" type="xs:dateTime" /> </xs:sequence> </xs:complexType>


B-28 TCA-S11-2.2

www.tca.gov.au

<xs:complexType name="EnrolmentFormType"> <xs:annotation><xs:documentation> The enrolment form </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="common:AbstractDocumentType"> <xs:sequence> <xs:element name="identifier" type="tns:EnrolmentIdentifierType"/> <xs:element name="previousEnrolmentIdentifier" type="tns:EnrolmentIdentifierType" minOccurs="0"/> <xs:element name="secondPartyReference" type="common:ReferenceIdentifierType" minOccurs="0" maxOccurs="unbounded" /> <xs:element name="enrolmentProcess" type="tns:EnrolmentProcessEnum" default="ASP" /> <xs:element name="authoritySection" type="tns:AuthoritySectionType" minOccurs="0" /> <xs:element name="statusCode" type="tns:EnrolmentStatusEnum"/> <xs:element name="commencementDateTime" type="xs:dateTime"/> <xs:element name="cessationDateTime" type="xs:dateTime" minOccurs="0"/> <xs:element name="conditionsSection" type="tns:ConditionsSectionType"/> <xs:element name="operatorSection" type="tns:OperatorSectionType" minOccurs="0"/> <xs:element name="interimApprovalSection" type="tns:InterimApprovalSectionType" minOccurs="0" /> <xs:sequence minOccurs="0"> <xs:element name="serviceProviderSection" type="tns:ServiceProviderSectionType"/> <xs:element name="approvalSection" type="tns:ApprovalSectionType"/> </xs:sequence> <xs:element name="cancellationSection" type="tns:CancellationSectionType" minOccurs="0"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="ServiceProviderEnrolmentType"> <xs:annotation><xs:documentation> Information about ASP and telematics device installation. Applicability of this type depends upon enrolment process. </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="common:AbstractDocumentType"> <xs:sequence> <xs:element name="enrolmentIdentifier" type="tns:EnrolmentIdentifierType"/> <xs:element name="serviceProviderSection" type="tns:ServiceProviderSectionType"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>



B-29

<xs:complexType name="EnrolmentCancellationRequestType"> <xs:annotation><xs:documentation> Request from ASP to Enrolment Manager to cancel enrolment. Only applicable to certain enrolment flows. </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="common:AbstractDocumentType"> <xs:sequence> <xs:element name="enrolmentIdentifier" type="tns:EnrolmentIdentifierType"/> <xs:element name="comments" type="xs:string" minOccurs="0"/> <xs:element name="authorisingOfficer" type="common:CompanyOfficerType"/> <xs:element name="issuedDateTime" type="xs:dateTime"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:element name="enrolmentForm" type="tns:EnrolmentFormType" /> <xs:element name="enrolmentCancellationRequest" type="tns:EnrolmentCancellationRequestType" /> </xs:schema>


B-30 TCA-S11-2.2

www.tca.gov.au

Event Report Schema <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:common="http://www.tca.gov.au/schemas/tde/core/common/2018-07" xmlns:data="http://www.tca.gov.au/schemas/tde/core/data-record/2018-07" xmlns:cond="http://www.tca.gov.au/schemas/tde/core/conditions/2018-07" xmlns:enrol="http://www.tca.gov.au/schemas/tde/core/enrolment/2018-07" xmlns:tns="http://www.tca.gov.au/schemas/tde/core/event-report/2018-07" targetNamespace="http://www.tca.gov.au/schemas/tde/core/event-report/2018-07" elementFormDefault="unqualified" version="2018-07" > <xs:annotation> <xs:appinfo> <xs:documentation> <name>tde_core_event-report_2018-07.xsd</name> <version>2018-07</version> <description>Telematics Data Exchange - event report definition </description> </xs:documentation> </xs:appinfo> </xs:annotation> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/common/2018-07" schemaLocation="tde_core_common_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/data-record/2018-07" schemaLocation="tde_core_data-record_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/conditions/2018-07" schemaLocation="tde_core_conditions_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/enrolment/2018-07" schemaLocation="tde_core_enrolment_2018-07.xsd"/> <xs:simpleType name="EventIdentifierType"> <xs:annotation><xs:documentation> The format of this string is SSSNNNNNNNNNNNN, where: * SSS is a TCA-assigned ASP identifier * NNNNNNNNNNNN is an ASP-assigned unique number </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:pattern value="[a-zA-Z0-9]{3}[0-9]{12}"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="DerivedAlarmTypeEnum" > <xs:annotation><xs:documentation> Different categories of derived alarms </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:enumeration value="2A" /> <xs:enumeration value="2B" /> <xs:enumeration value="2C" /> </xs:restriction> </xs:simpleType>



B-31

<xs:simpleType name="EventTypeType"> <xs:annotation><xs:documentation> Data type for event types </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:pattern value="[A-Z][A-Z0-9_]*" /> </xs:restriction> </xs:simpleType> <xs:simpleType name="EventTypeEnum"> <xs:annotation><xs:documentation> Event types defined within core - each application will also define its own event types </xs:documentation></xs:annotation> <xs:restriction base="tns:EventTypeType"> <xs:enumeration value="ALARM" /> </xs:restriction> </xs:simpleType> <xs:complexType name="ReportRecordType" abstract="true" > <xs:annotation><xs:documentation> This is the base type for records that appear within the event report. Some report records will be generated in back-office processing, and others will wrap (and decorate) telematics device data records. </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="jurisdictionDateTime" type="xs:dateTime" /> </xs:sequence> </xs:complexType> <xs:complexType name="TransferRecordType"> <xs:annotation><xs:documentation> The event report wrapper around a data transfer record. </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="tns:ReportRecordType"> <xs:sequence> <xs:element name="deviceRecord" type="data:DeviceTransferRecordType"/> <xs:element name="connectedDeviceJurisdictionDateTime" type="xs:dateTime" minOccurs="0"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="AlarmRecordType"> <xs:annotation><xs:documentation> The event report wrapper around an alarm record. </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="tns:ReportRecordType"> <xs:sequence> <xs:element name="deviceRecord" type="data:DeviceAlarmRecordType"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>


B-32 TCA-S11-2.2

www.tca.gov.au

<xs:complexType name="DerivedAlarmRecordType"> <xs:annotation><xs:documentation> An event report derived (Type 2) alarm. These are alarms that generated within the back office, and do not directly wrap a single device record. </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="tns:ReportRecordType"> <xs:sequence> <xs:element name="dateTime" type="xs:dateTime"/> <xs:element name="alarmType" type="tns:DerivedAlarmTypeEnum" /> <xs:element name="code" type="data:GenericCodeType"/> <xs:element name="connectedDevice" type="data:DeviceIdentityType" minOccurs="0" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="EventSummaryType"> <xs:annotation><xs:documentation> A summary of the event. </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="eventTypeCode" type="tns:EventTypeType"/> <xs:element name="eventSubTypeCode" type="tns:EventTypeType" minOccurs="0" maxOccurs="unbounded" /> <xs:sequence minOccurs="0"> <xs:element name="deviceEventPeriod" type="common:DateTimePeriodType"/> <xs:element name="jurisdictionEventPeriod" type="common:DateTimePeriodType"/> </xs:sequence> <xs:sequence minOccurs="0"> <xs:element name="initialPosition" type="data:PointType"/> <xs:element name="finalPosition" type="data:PointType"/> </xs:sequence> </xs:sequence> </xs:complexType> <xs:complexType name="PrimaryUnitInformationType"> <xs:annotation><xs:documentation> Information about the prime mover/rigid truck the event relates to, including telematics device installation. </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="common:VehicleInformationType"> <xs:sequence> <xs:element name="installedDevice" type="data:DeviceIdentityType"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="EnrolmentReferenceType"> <xs:annotation><xs:documentation> Summary of the enrolment of the prime mover/rigid truck against which the event is being reported (all events reference one or more enrolments). This includes the identifier and revision of any off-the-shelf conditions. </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="enrolmentIdentifier" type="enrol:EnrolmentIdentifierType" /> <xs:element name="scheme" type="cond:SchemeNameType" minOccurs="0" /> <xs:element name="offTheShelfConditions" type="cond:OffTheShelfConditionsReferenceType" minOccurs="0" /> </xs:sequence> </xs:complexType>



B-33

<xs:complexType name="EventReportExtensionType" abstract="true"> <xs:annotation><xs:documentation> Base type for application specific extensions to the event report. </xs:documentation></xs:annotation> </xs:complexType> <xs:complexType name="EventReportType"> <xs:annotation><xs:documentation> The event report. </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="common:AbstractDocumentType"> <xs:sequence> <xs:element name="identifier" type="tns:EventIdentifierType"/> <xs:element name="previousEventIdentifier" type="tns:EventIdentifierType" minOccurs="0"> <xs:annotation> <xs:documentation> This element is used to indicate that this event report represents a continuation of a previous event report (used for spatial non- compliance that exceeds 72 hours). </xs:documentation> </xs:annotation> </xs:element> <xs:element name="auditReferenceDateTime" type="xs:dateTime"> <xs:annotation> <xs:documentation> This is a date and time in the Jurisdiction's time zone that results from a deterministic algorithm being applied to the raw telematics device data records that caused the event report to be issued - in other words the same value for this date and time will result no matter how many times the event report is generated, and no matter when it is generated. </xs:documentation> </xs:annotation> </xs:element> <xs:element name="ntmVersion" type="common:NtmVersionType"/> <xs:element name="authorityCode" type="common:AuthorityCodeType"/> <xs:element name="enrolmentReference" type="tns:EnrolmentReferenceType" maxOccurs="unbounded"/> <xs:element name="serviceProvider" type="enrol:ServiceProviderInformationType"/> <xs:element name="primaryUnit" type="tns:PrimaryUnitInformationType"/> <xs:element name="extension" type="tns:EventReportExtensionType" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="eventSummary" type="tns:EventSummaryType"/> <xs:element name="record" type="tns:ReportRecordType" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="comments" type="xs:string" minOccurs="0"/> <xs:element name="issuedDateTime" type="xs:dateTime"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:element name="eventReport" type="tns:EventReportType" /> </xs:schema>


B-34 TCA-S11-2.2

www.tca.gov.au

Enrolment Report Schema <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:common="http://www.tca.gov.au/schemas/tde/core/common/2018-07" xmlns:tns="http://www.tca.gov.au/schemas/tde/core/enrolment-report/2018-07" xmlns:data="http://www.tca.gov.au/schemas/tde/core/data-record/2018-07" xmlns:cond="http://www.tca.gov.au/schemas/tde/core/conditions/2018-07" xmlns:enrol="http://www.tca.gov.au/schemas/tde/core/enrolment/2018-07" xmlns:evr="http://www.tca.gov.au/schemas/tde/core/event-report/2018-07" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.tca.gov.au/schemas/tde/core/enrolment-report/2018-07" elementFormDefault="unqualified" version="2018-07" > <xs:annotation> <xs:appinfo> <xs:documentation> <name>tde_core_pr_2018-07.xsd</name> <version>2018-07</version> <description>Telematics Data Exchange - enrolment report definition </description> </xs:documentation> </xs:appinfo> </xs:annotation> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/common/2018-07" schemaLocation="tde_core_common_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/data-record/2018-07" schemaLocation="tde_core_data-record_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/conditions/2018-07" schemaLocation="tde_core_conditions_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/enrolment/2018-07" schemaLocation="tde_core_enrolment_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/event-report/2018-07" schemaLocation="tde_core_event-report_2018-07.xsd"/> <xs:simpleType name="EnrolmentReportIdentifierType"> <xs:annotation><xs:documentation> The format of this string is SSSNNNNNNN, where: * SSS is a TCA-assigned ASP identifier * NNNNNNN is an ASP-assigned unique number </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:pattern value="[a-zA-Z0-9]{3}[0-9]{7}"/> </xs:restriction> </xs:simpleType> <xs:complexType name="EventCountType"> <xs:annotation><xs:documentation> Recording how many events of a single given type or sub-type were recorded </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="typeCode" type="evr:EventTypeType" /> <xs:element name="count" type="xs:int" /> </xs:sequence> </xs:complexType>



B-35

<xs:complexType name="ReportedEventCountType"> <xs:complexContent> <xs:extension base="tns:EventCountType"> <xs:sequence> <xs:element name="subTypeCount" type="tns:EventCountType" minOccurs="0" maxOccurs="unbounded" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="ReportedEventCountsType"> <xs:annotation><xs:documentation> Summary of all reported events of all types. </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="typeCount" type="tns:ReportedEventCountType" minOccurs="0" maxOccurs="unbounded" /> <xs:element name="totalCount" type="xs:int"/> </xs:sequence> </xs:complexType> <xs:complexType name="EnrolmentReferenceExtensionType" abstract="true" > <xs:annotation><xs:documentation> Base type for application-specific extension to the summary for each enrolment (e.g. summary of activity, resource usage, etc.) </xs:documentation></xs:annotation> </xs:complexType> <xs:complexType name="EnrolmentReferenceType"> <xs:annotation><xs:documentation> Summary of an enrolment into the application that was active at some stage during the reporting period. </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="evr:EnrolmentReferenceType"> <xs:sequence> <xs:element name="operator" type="enrol:OperatorIdentificationType" minOccurs="0" /> <xs:element name="extension" type="tns:EnrolmentReferenceExtensionType" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="EnrolmentSummaryExtensionType" abstract="true" > <xs:annotation><xs:documentation> Base type for any application-specific extension to the summary for the reporting for any single vehicle + telematics device combination (i.e., this summary applies across all enrolments). </xs:documentation></xs:annotation> </xs:complexType>


B-36 TCA-S11-2.2

www.tca.gov.au

<xs:complexType name="EnrolmentSummaryType"> <xs:annotation><xs:documentation> Summary of all enrolments for a single vehicle + telematics device combination. </xs:documentation></xs:annotation> <xs:sequence> <xs:choice> <xs:element name="vehicleIdentity" type="common:VehicleIdentityType" /> <xs:element name="vehicleRegistration" type="common:VehicleRegistrationType" /> <xs:element name="vehicle" type="common:VehicleInformationType" /> </xs:choice> <xs:element name="enrolment" type="tns:EnrolmentReferenceType" maxOccurs="unbounded" > <xs:annotation><xs:documentation> 1. For IAP only there may be multiple enrolments listed. Other applications must have only one enrolment listed (i.e. have a separate enrolment summary for each enrolment). 2. For IAP the enrolment reference is not required to list the scheme, but for other applications the scheme must be listed. </xs:documentation></xs:annotation> </xs:element> <xs:element name="entryDateTime" type="xs:dateTime" minOccurs="0" /> <xs:element name="exitDateTime" type="xs:dateTime" minOccurs="0" /> <xs:element name="installedDevice" type="data:DeviceIdentityType"/> <xs:element name="reportedEventCounts" type="tns:ReportedEventCountsType" minOccurs="0" /> <xs:element name="extension" type="tns:EnrolmentSummaryExtensionType" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> <xs:complexType name="EnrolmentReportType"> <xs:annotation><xs:documentation> Summary of all enrolments for all vehicles for this application during one reporting period. </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="common:AbstractDocumentType"> <xs:sequence> <xs:element name="identifier" type="tns:EnrolmentReportIdentifierType"/> <xs:element name="authorityCode" type="common:AuthorityCodeType"/> <xs:element name="reportPeriod" type="common:DateTimePeriodType"/> <xs:element name="serviceProvider" type="enrol:ServiceProviderInformationType"/> <xs:element name="enrolmentSummary" type="tns:EnrolmentSummaryType" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="reportedEventCounts" type="tns:ReportedEventCountsType" minOccurs="0" /> <xs:element name="comments" type="xs:string" minOccurs="0"/> <xs:element name="issuedDateTime" type="xs:dateTime"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:element name="enrolmentReport" type="tns:EnrolmentReportType" /> </xs:schema>



B-37

Data Report Schema <?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:common="http://www.tca.gov.au/schemas/tde/core/common/2018-07" xmlns:tns="http://www.tca.gov.au/schemas/tde/core/data-report/2018-07" xmlns:data="http://www.tca.gov.au/schemas/tde/core/data-record/2018-07" xmlns:cond="http://www.tca.gov.au/schemas/tde/core/conditions/2018-07" xmlns:enrol="http://www.tca.gov.au/schemas/tde/core/enrolment/2018-07" xmlns:evr="http://www.tca.gov.au/schemas/tde/core/event-report/2018-07" xmlns:enr="http://www.tca.gov.au/schemas/tde/core/enrolment-report/2018-07" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.tca.gov.au/schemas/tde/core/data-report/2018-07" elementFormDefault="unqualified" version="2018-07" > <xs:annotation> <xs:appinfo> <xs:documentation> <name>tde_core_pr_2018-07.xsd</name> <version>2018-07</version> <description>Telematics Data Exchange - data report definition </description> </xs:documentation> </xs:appinfo> </xs:annotation> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/common/2018-07" schemaLocation="tde_core_common_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/data-record/2018-07" schemaLocation="tde_core_data-record_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/conditions/2018-07" schemaLocation="tde_core_conditions_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/enrolment/2018-07" schemaLocation="tde_core_enrolment_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/event-report/2018-07" schemaLocation="tde_core_event-report_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/enrolment-report/2018-07" schemaLocation="tde_core_enrolment-report_2018-07.xsd"/> <xs:simpleType name="DataReportIdentifierType"> <xs:annotation><xs:documentation> The format of this string is SSSNNNNNNN, where: * SSS is a TCA-assigned ASP identifier * NNNNNNN is an ASP-assigned unique number </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:pattern value="[a-zA-Z0-9]{3}[0-9]{7}"/> </xs:restriction> </xs:simpleType> <xs:complexType name="EventCountType"> <xs:annotation><xs:documentation> Recording how many events of a single given type or sub-type were recorded </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="typeCode" type="evr:EventTypeType" /> <xs:element name="count" type="xs:int" /> </xs:sequence> </xs:complexType>


B-38 TCA-S11-2.2

www.tca.gov.au

<xs:complexType name="ReportedEventCountType"> <xs:complexContent> <xs:extension base="tns:EventCountType"> <xs:sequence> <xs:element name="subTypeCount" type="tns:EventCountType" minOccurs="0" maxOccurs="unbounded" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="ReportedEventCountsType"> <xs:annotation><xs:documentation> Summary of all reported events of all types. </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="typeCount" type="tns:ReportedEventCountType" minOccurs="0" maxOccurs="unbounded" /> <xs:element name="totalCount" type="xs:int"/> </xs:sequence> </xs:complexType> <xs:complexType name="EnrolmentExtensionType" abstract="true" > <xs:annotation><xs:documentation> Base type for application-specific extension to the summary for each enrolment (e.g. summary of activity, resource usage, etc) </xs:documentation></xs:annotation> </xs:complexType> <xs:complexType name="EnrolmentReferenceType"> <xs:annotation><xs:documentation> Summary of an enrolment into the application that was active at some stage during the reporting period. </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="evr:EnrolmentReferenceType"> <xs:sequence> <xs:element name="extension" type="tns:EnrolmentExtensionType" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="EnrolmentSummaryExtensionType" abstract="true" > <xs:annotation><xs:documentation> Base type for any application-specific extension to the summary for the reporting for any single vehicle + telematics device combination (i.e., this summary applies across all enrolments). </xs:documentation></xs:annotation> </xs:complexType>



B-39

<xs:complexType name="TransferableItemType" abstract="true"> <xs:annotation><xs:documentation> Base type for data package items that can be transfered ahead of the data package using Tier 1 Data Exchange services </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="transferDateTime" type="xs:dateTime" minOccurs="0" > <xs:annotation><xs:documentation> Populate this field if and only if the item has been transfered via Tier 1 Data Exchange service </xs:documentation></xs:annotation> </xs:element> </xs:sequence> </xs:complexType> <xs:complexType name="EnrolmentItemType"> <xs:annotation><xs:documentation> </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="tns:TransferableItemType"> <xs:sequence> <xs:element name="identifier" type="enrol:EnrolmentIdentifierType" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="EventReportItemType"> <xs:annotation><xs:documentation> </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="tns:TransferableItemType"> <xs:sequence> <xs:element name="identifier" type="evr:EventIdentifierType" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="EnrolmentReportItemType"> <xs:annotation><xs:documentation> </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="tns:TransferableItemType"> <xs:sequence> <xs:element name="identifier" type="enr:EnrolmentReportIdentifierType" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="DataRecordBatchItemType"> <xs:annotation><xs:documentation> </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="tns:TransferableItemType"> <xs:sequence> <xs:element name="identifier" type="data:ReceivedDataRecordsBatchIdentifierType" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>


B-40 TCA-S11-2.2

www.tca.gov.au

<xs:complexType name="DeviceDataRecordsItemType"> <xs:annotation><xs:documentation> </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="deviceId" type="data:DeviceIdentifierType" /> <xs:element name="date" type="xs:date" /> </xs:sequence> </xs:complexType> <xs:complexType name="DataReportItemsType"> <xs:annotation><xs:documentation> </xs:documentation></xs:annotation> <xs:sequence> <xs:choice minOccurs="0" maxOccurs="unbounded" > <xs:element name="enrolment" type="tns:EnrolmentItemType"/> <xs:element name="eventReport" type="tns:EventReportItemType"/> <xs:element name="enrolmentReport" type="tns:EnrolmentReportItemType"/> <xs:element name="dataRecordBatch" type="tns:DataRecordBatchItemType"/> <xs:element name="deviceDataRecords" type="tns:DeviceDataRecordsItemType"/> </xs:choice> </xs:sequence> </xs:complexType> <xs:complexType name="DataReportType"> <xs:annotation><xs:documentation> Summary of all enrolments for all vehicles for this application during one reporting period. </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="application" type="common:ApplicationReferenceType" maxOccurs="unbounded" /> <xs:element name="identifier" type="tns:DataReportIdentifierType"/> <xs:element name="serviceProvider" type="enrol:ServiceProviderInformationType"/> <xs:element name="reportPeriod" type="common:DateTimePeriodType"/> <xs:element name="items" type="tns:DataReportItemsType" /> <xs:element name="issuedDateTime" type="xs:dateTime"/> </xs:sequence> </xs:complexType> <xs:element name="dataReport" type="tns:DataReportType" /> </xs:schema>



C-1

Appendix C Telematics Data Exchange JSON Schema

Overview The JSON schema provided in this appendix specifies the JSON encoding for all data records defined across telematics applications, and is equivalent to the XML schema tde_core_data_records_2018-07.

This schema does not specify each data element as being mandatory or optional. Instead, each telematics application may provide a complimentary set of data record tables in an appendix that lists:

• the data elements that are relevant to the application (with those not listed being considered not relevant); and

• whether elements that are relevant to the application are mandatory or optional.

Application data record tables do not respecify the data type or range of valid values for each data element. Thus, this schema and the application data record tables must be used in combination during the software development process to ensure valid data records are generated.

Note: The device type ‘TD’ (for telematics device) and ‘IVU’ (for in-vehicle unit) are equivalent. TD should be used except where the term IVU is explicitly used within the application specification rather than telematics device.

Telematics Data Exchange JSON Schema { "$id": "http://www.tca.gov.au/schemas/tde/core/data-record/2018-07", "$schema": "http://json-schema.org/draft-07/schema#", "title": "Telematics Data Exchange (TDE) - data record definitions", "oneOf": [ {"$ref": "#/definitions/struct.data-record.set"}, {"$ref": "#/definitions/struct.data-record.batch"} ], "definitions": { "enum.tde-version" : { "description" : "version number of the TDE specification defining the data model", "type" : "string", "enum" : ["2.0"] }, "type.iso8601.dateTime" : { "description" : "ISO-8601 UTC date and time", "type": "string", "pattern": "^[0-9]{4}-((0[1-9])|(1[0-2]))-((0[1-9])|([1-2][0-9])|(3[0-1]))T(([0-1] [0-9])|(2[0-3])):[0-5][0-9]:[0-5][0-9]Z" }, "enum.srs-name" : { "description" : "Spatial Reference System datum name", "type" : "string", "enum" : ["GDA94", "WGS84", "GDA2020"] },


C-2 TCA-S11-2.2

www.tca.gov.au

"enum.device.type" : { "description" : "type of a device", "type": "string", "enum": [“TD”, "IVU", "TID", "ECU"] }, "type.device.model" : { "description" : "model of a device as agreed by TCA", "type": "string", "minLength": 1, "maxLength": 20 }, "type.device.identifier" : { "description" : "identifier of a device", "type": "string", "minLength": 1, "maxLength": 20 }, "struct.device.identity" : { "description" : "identity of a device (identifier and optionally type and model)", "type" : "object", "properties" : { "type" : {"$ref" : "#/definitions/enum.device.type"}, "id" : {"$ref" : "#/definitions/type.device.identifier"} "model" : {"$ref" : "#/definitions/type.device.model"} }, "required" : ["id"] "additionalProperties" : false }, "type.device.sequence" : { "description" : "sequence of a device, where the first device is numbered 1", "type": "integer", "minimum": 1 }, "type.device.alarm-code" : { "description" : "an alarm code", "type": "integer", "minimum" : 1 }, "struct.data.point" : { "description" : "a latitude and longitude - where optional omit entire object", "type": "object", "properties": { "latitude" : { "type" : "number", "minimum" : -90.0, "maximum" : 90.0, "multipleOf" : 0.00001 }, "longitude" : { "type" : "number", "minimum" : -180.0, "maximum" : 180.0, "multipleOf" : 0.00001 } }, "required" : ["latitude", "longitude"] "additionalProperties" : false },



C-3

"type.data.heading" : { "description" : "bearing as number of degrees", "type" : "number", "minimum" : 0.0, "exclusiveMaximum" : 360.0, "multipleOf" : 0.1 }, "type.data.hdop" : { "description" : "horizontal dilution of precision", "type" : "number", "minimum" : 0.0, "exclusiveMaximum" : 100.0, "multipleOf" : 0.1 }, "enum.data.service-availability" : { "description" : "GNSS (or other positioning system) service availability", "type": "string", "enum": ["UNKNOWN", "UNAVAILABLE", "DEGRADED", "AVAILABLE"] }, "type.data.satellite-count" : { "description" : "number of satellites used, by convention 0 meaning insufficient number available to allow for use", "type" : "integer", "minimum": 0 }, "type.data.speed" : { "description" : "speed", "type" : "number", "minimum" : 0.0, "multipleOf" : 0.1 }, "type.data.mass" : { "description" : "mass - either as integer kg or as decimal tonne (decision to use each is contextual - see application)", "anyOf" : [ { "description" : "mass as kg", "type": "integer", "minimum" : 0 }, { "description" : "mass as tonne", "type": "number", "minimum" : 0.0, "multipleOf" : 0.1 } ] }, "enum.data.load-status" : { "description" : "load status", "type": "string", "enum": ["LOAD", "NO_LOAD"] },


C-4 TCA-S11-2.2

www.tca.gov.au

"type.sd.version" : { "description" : "version of SD codeset", "type": "string", "minLength" : 1, "maxLength" : 10 }, "type.sd.category-code" : { "description" : "SD code used to describe a vehicle category", "type": "integer", "minimum" : 1 }, "type.sd.category-name" : { "description" : "SD standard name for a vehicle category", "type": "string", "minLength" : 1, "maxLength" : 256 }, "type.sd.comment-code" : { "description" : "SD code used to describe a standard comment", "type": "integer", "minimum" : 1 }, "type.sd.comment-name" : { "description" : "SD standard comment name", "type": "string", "minLength" : 1, "maxLength" : 256 }, "type.sd.comment-text" : { "description" : "SD free format comment as collected the user interface", "type": "string", "minLength" : 1, "maxLength" : 256 }, "enum.data-record.type" : { "description" : "standard record types", "type": "string", "enum": ["POSITION", "SPEED", "ALARM", "SD_TCM", "SD_COMMENT", "TRANSFER", "OBM_ALARM", "OBM_CONFIG", "OBM_MASS", "OBM_QUALITY"] }, "struct.data-record.common" : { "description" : "common fields for all data records", "type" : "object", "properties" : { "type" : {"$ref" : "#/definitions/enum.data-record.type"}, "deviceId" : {"$ref" : "#/definitions/type.device.identifier"}, "dateTime" : {"$ref" : "#/definitions/type.iso8601.dateTime"}, "number" : {"type" : "integer"} }, "required" : ["type", "dateTime"] },



C-5

"struct.data-record.received" : { "description" : "common fields for data records that are received by ASP back office", "type" : "object", "properties" : { "receiptDateTime" : {"$ref" : "#/definitions/type.iso8601.dateTime"} }, "required" : ["receiptDateTime"] }, "enum.data.ignition-status" : { "description" : "enumerated values for ignition status", "type": "string", "enum": ["ON", "OFF", "DISCONNECTED"] }, "enum.data.movement-sensor-status" : { "description" : "enumerated values for independent movement sensor status", "type": "string", "enum": ["MOVEMENT", "NO_MOVEMENT", "DISCONNECTED"] }, "struct.data-record.position" : { "description" : "position data record", "allOf" : [ {"$ref" : "#/definitions/struct.data-record.common"} ], "properties" : { "type" : {"const" : "POSITION"}, "position" : {"$ref" : "#/definitions/struct.data.point"}, "direction" : {"$ref" : "#/definitions/type.data.heading"}, "speed" : {"$ref" : "#/definitions/type.data.speed"}, "satelliteCount" : {"$ref" : "#/definitions/type.data.satellite-count"}, "service" : {"$ref" : "#/definitions/enum.data.service-availability"}, "hdop" : {"$ref" : "#/definitions/type.data.hdop"}, "ignition" : {"$ref" : "#/definitions/enum.data.ignition-status"}, "movementSensor" : {"$ref" : "#/definitions/enum.data.movement-sensor-status"} } }, "struct.data-record.speed" : { "description" : "speed data record", "allOf" : [ {"$ref" : "#/definitions/struct.data-record.common"} ], "properties" : { "type" : {"const" : "SPEED"}, "position" : {"$ref" : "#/definitions/struct.data.point"}, "speed" : {"$ref" : "#/definitions/type.data.speed"}, "satelliteCount" : {"$ref" : "#/definitions/type.data.satellite-count"}, "service" : {"$ref" : "#/definitions/enum.data.service-availability"}, "hdop" : {"$ref" : "#/definitions/type.data.hdop"} } }, "struct.data-record.alarm" : { "description" : "alarm data record", "allOf" : [ {"$ref" : "#/definitions/struct.data-record.common"} ], "properties" : { "type" : {"const" : "ALARM"}, "code" : {"$ref" : "#/definitions/type.device.alarm-code"}, "connectedDevice" : {"$ref" : "#/definitions/struct.device.identity"} }, "required" : ["code"] },


C-6 TCA-S11-2.2

www.tca.gov.au

"struct.data-record.sd-tcm" : { "description" : "SD (vehicle type/TCM) data record", "allOf" : [ {"$ref" : "#/definitions/struct.data-record.common"} ], "properties" : { "type" : {"const" : "SD_TCM"}, "version" : {"$ref" : "#/definitions/type.sd.version"}, "category" : {"$ref" : "#/definitions/type.sd.category-code"}, "categoryName" : {"$ref" : "#/definitions/type.sd.category-name"}, "axleCount" : { "type" : "integer", "minimum" : 0 }, "load" : {"$ref" : "#/definitions/enum.data.load-status"}, "mass" : {"$ref" : "#/definitions/type.data.mass"} } }, "struct.data-record.sd-comment" : { "description" : "SD (comment) data record", "allOf" : [ {"$ref" : "#/definitions/struct.data-record.common"} ], "properties" : { "type" : {"const" : "SD_COMMENT"}, "version" : {"$ref" : "#/definitions/type.sd.version"}, "comment" : {"$ref" : "#/definitions/type.sd.comment-code"}, "commentName" : {"$ref" : "#/definitions/type.sd.comment-name"}, "commentText" : {"$ref" : "#/definitions/type.sd.comment-text"} } }, "enum.obm.lift-axle-status-code" : { "description" : "enumerated values for lift axle status", "type": "string", "enum" : ["NONE", "FITTED", "RAISED", "LOWERED"] }, "struct.data-record.obm-common" : { "description" : "common fields for all OBM system data records", "allOf" : [ {"$ref" : "#/definitions/struct.data-record.common"} ], "properties" : { "version" : { "type" : "integer", "minimum" : 1 } } }, "struct.data-record.obm-alarm" : { "description" : "an OBM system alarm record", "allOf" : [ {"$ref" : "#/definitions/struct.data-record.obm-common"} ], "properties" : { "type" : {"const" : "OBM_ALARM"}, "code" : {"$ref" : "#/definitions/type.device.alarm-code"}, "msuId" : {"$ref" : "#/definitions/type.device.identifier"}, "msuSequence" : {"$ref" : "#/definitions/type.device.sequence"} }, "required" : ["code"] },



C-7

"struct.data-record.obm-configuration.msu" : { "description" : "an OBM system configuration record MSU sub-record", "properties" : { "msuId" : {"$ref" : "#/definitions/type.device.identifier" }, "msuSequence" : {"$ref" : "#/definitions/type.device.sequence" } }, "required" : ["msuId"] }, "struct.data-record.obm-configuration" : { "description" : "an OBM system configuration record", "allOf" : [ {"$ref" : "#/definitions/struct.data-record.obm-common"} ], "properties" : { "type" : {"const" : "OBM_CONFIG"}, "msuCount" : { "type" : "integer", "minimum" : 0 }, "msuRecords" : { "type" : "array", "minItems" : 0, "items" : {"$ref" : "#/definitions/struct.data-record.obm-configuration.msu" } } } }, "struct.data-record.obm-mass.msu" : { "description" : "an OBM system mass record MSU sub-record", "properties" : { "msuId" : {"$ref" : "#/definitions/type.device.identifier" }, "msuSequence" : {"$ref" : "#/definitions/type.device.sequence" }, "liftAxle" : { "$ref" : "#/definitions/enum.obm.lift-axle-status-code" }, "mass" : {"$ref" : "#/definitions/type.data.mass" } }, "required" : ["msuId"] }, "struct.data-record.obm-mass" : { "description" : "an OBM system mass record", "allOf" : [ {"$ref" : "#/definitions/struct.data-record.obm-common"} ], "properties" : { "type" : {"const" : "OBM_MASS"}, "mass" : { "$ref" : "#/definitions/type.data.mass" }, "msuCount" : { "type" : "integer", "minimum" : 0 }, "msuRecords" : { "type" : "array", "minItems" : 0, "items" : {"$ref" : "#/definitions/struct.data-record.obm-mass.msu" } } } },


C-8 TCA-S11-2.2

www.tca.gov.au

"struct.data-record.obm-quality" : { "description" : "an OBM system quality record", "allOf" : [ {"$ref" : "#/definitions/struct.data-record.obm-common"} ], "properties" : { "type" : {"const" : "OBM_QUALITY"}, "msuCount" : { "type" : "integer", "minimum" : 0 }, "msuId" : {"$ref" : "#/definitions/type.device.identifier" }, "msuSequence" : {"$ref" : "#/definitions/type.device.sequence" }, "liftAxle" : { "$ref" : "#/definitions/enum.obm.lift-axle-status-code" }, "dataFrequency" : { "type" : "integer", "minimum" : 1 }, "dataCount" : { "type" : "integer", "minimum" : 1 }, "massData" : { "type" : "array", "items" : { "$ref" : "#/definitions/type.data.mass" } } }, "required" : ["msuId"] }, "struct.data-record.transfer" : { "description" : "a telmeatics data record that contains a data record received from a connected device", "allOf" : [ {"$ref" : "#/definitions/struct.data-record.common"} ], "properties" : { "type" : {"const" : "TRANSFER"}, "connectedDevice" : {"$ref" : "#/definitions/struct.device.identity"}, "connectedDeviceRecord" : { "oneOf" : [ {"$ref" : "#/definitions/struct.data-record.obm-alarm"}, {"$ref" : "#/definitions/struct.data-record.obm-configuration"}, {"$ref" : "#/definitions/struct.data-record.obm-mass"}, {"$ref" : "#/definitions/struct.data-record.obm-quality"} ] } }, "required" : ["connectedDevice", "connectedDeviceRecord"] },



C-9

"struct.data-record.device-set" : { "description" : "a batch of data records from a single telematics device", "type" : "object", "properties" : { "tdeVersion" : {"$ref" : "#/definitions/enum.tde-version"}, "device" : {"$ref" : "#/definitions/struct.device.identity"}, "srs" : {"$ref" : "#/definitions/enum.srs-name"}, "records" : { "type" : "array", "items" : { "allOf" : [ {"$ref" : "#/definitions/struct.data-record.received"}, { "oneOf" : [ {"$ref" : "#/definitions/struct.data-record.position"}, { "allOf" : [ {"$ref" : "#/definitions/struct.data-record.speed"}, { "properties" : { "speedThreshold" : {"$ref" : "#/definitions/type.data.speed"} } } ]}, {"$ref" : "#/definitions/struct.data-record.alarm"}, {"$ref" : "#/definitions/struct.data-record.sd-tcm"}, {"$ref" : "#/definitions/struct.data-record.sd-comment"}, {"$ref" : "#/definitions/struct.data-record.transfer"}, {"$ref" : "#/definitions/struct.data-record.obm-alarm"}, {"$ref" : "#/definitions/struct.data-record.obm-configuration"}, {"$ref" : "#/definitions/struct.data-record.obm-mass"}, {"$ref" : "#/definitions/struct.data-record.obm-quality"} ]} ] } } }, "required" : ["device"], "additionalProperties" : false }, "struct.data-record.set" : { "description" : "document (top) level - a batch of data records from a single device", "allOf" : [ { "$ref" : "#/definitions/struct.data-record.device-set"}, { "required" : ["tdeVersion", "device"] } ] },


C-10 TCA-S11-2.2

www.tca.gov.au

"struct.data-record.batch" : { "description" : "document (top) level - a batch of data records from multiple devices organised by device identity", "type" : "object", "properties" : { "tdeVersion" : {"$ref" : "#/definitions/enum.tde-version"}, "batchId" : { "type" : "string", "minLength" : 1 }, "deviceRecords" : { "type" : "array", "items": {"$ref" : "#/definitions/struct.data-record.device-set"} } }, "required" : ["tdeVersion", "batchId" ], "additionalProperties" : false } } }



D-1

Appendix D Telematics Data Exchange RESTful API

Overview This appendix specifies the RESTful services that realise the Tier 1 Data Exchange services described in Section 5: Tier 1 Data Exchange. The behaviour of RESTful services, including allowed and expected responses and status codes, is described in A.3.

Notify Enrolment The Notify Enrolment operation is used by a participant to advise a second participant of a change to an enrolment.

URL Path /enrolment/{enrolment-id}

Method PUT

Parameters enrolment-id – the identifier of the enrolment

Request Headers Content-Type: application/xml

Request Body XML document for schema element {http://www.tca.gov.au/schemas/ tde/core/enrolment/2018-07}enrolmentForm

Response Body None

Request Enrolment The Request Enrolment operation is used by a participant to request a second participant to enrol a vehicle.

URL Path /enrolment-request/{request-id}

Method PUT

Parameters request-id – a request identifier assigned by the invoking participant


Request Body XML document for schema element {http://www.tca.gov.au/schemas/ tde/ core/enrolment/2018-07}enrolmentForm

Response Body None


D-2 TCA-S11-2.2

www.tca.gov.au

Request Enrolment Approval The Request Enrolment Approval operation is used by a participant to request that a second participant approve an interim approved enrolment.

URL Path /enrolment/{enrolment-id}/approval-request/{request-id}

Method PUT

Parameters • enrolment-id – the identifier of the enrolment

• request-id – a request identifier assigned by the invoking participant



Response Body None

Request Enrolment Replacement The Request Enrolment Replacement operation is used by a participant to request that a second participant cancel an existing and approved enrolment, and create and approve a replacement enrolment. This may be used where allowed and supported by the application – for example, where a faulty telematics device has been replaced.

URL Path /enrolment/{enrolment-id}/replacement-request/{request-id}

Method PUT





Response Body None



D-3

Request Enrolment Cancellation The Request Enrolment Cancellation operation is used by a participant a request that a second participant cancel an existing and approved enrolment.

URL Path /enrolment/{enrolment-id}/cancellation-request/{request-id}

Method PUT




Request Body XML document for schema element {http://www.tca.gov.au/schemas/ tde/ core/enrolment/2018-07}enrolmentCancellationRequest

Response Body None

Notify Response The Notify Response operation is used by a participant to advise a scond participant that a previously submitted request has been considered and rejected.

URL Path /request/{request-id}/response

Method PUT

Parameters request-id – the request id identifying the original request

Request Headers Content-Type: text/plain

Request Body An HTTP status code indicating why the request has been rejected, populated in accordance with A.3.2

Response Body None


D-4 TCA-S11-2.2

www.tca.gov.au

Notify Event Report The Notify Event Report operation is used by an ASP to advise a second participant of an event report.

URL Path /event-report/{event-report-id}

Method PUT

Parameters event-report-id


Request Body XML document for schema element {http://www.tca.gov.au/schemas/ tde/core/event-report/2018-07}eventReport

Response Body None

Notify Enrolment Report The Notify Enrolment Report operation is used by an ASP to notify a second participant of an enrolment report.

URL Path /enrolment-report/{enrolment-report-id}

Method PUT

Parameters enrolment-report-id


Request Body XML document for schema element {http://www.tca.gov.au/schemas/ tde/core/enrolment-report/2018-07}enrolmentReport

Response Body None



D-5

Notify Data Records The Notify Event Report operation is used by an ASP to provide a second participant (nominally TCA) with a data record batch.

URL Path /data-records/{batch-id}

Method PUT

Parameters batch-id – the unique batch identifier assigned by the ASP

Request Headers • application/xml

• application/json

Request Body • XML document for schema element {http://www.tca.gov.au/ schemas/tde/core/data-record/2018-07}dataRecordBatch

• JSON document formed against schema http://www.tca.gov.au/ schemas/tde/iap/data-record/2018-07

Response Body None

Notify Data Report The Notify Data Report operation is used by an ASP to provide another participant (nominally TCA) with a data report. This is the manifest for data reporting.

URL Path /data-report/{data-report-id}

Method PUT

Parameters data-report-id – the unique data report identifier assigned by the ASP

Request Headers application/xml

Request Body XML document for schema element {http://www.tca.gov.au/schemas/ tde/core/data-report/2018-07}dataReport

Response Body None



E-1

Appendix E Data Record Reference

Overview This appendix presents the data model for all data records that may be reported by the ASP to the Authority or to TCA. This data model is aligned with the Telematics Data Dictionary and is independent of any specific encoding or format. XML and JSON encodings of this data model are described in Appendix B and Appendix C respectively.

The data record data models support the requirements of applications, noting that each application:

• must explicitly identify the data records used by the application (as not all data records are relevant to all applications); and

• must not use data records that are not described in this specification.

For each data record used by an application, the application:

• must explicitly identify the data elements that are used by the application, noting that the data elements marked with an asterisk ( * ) must be used by all applications that require the data record;

• must not use data elements that are not described in this specification;

• must indicate whether each data element used by the application is mandatory or otherwise (e.g. optional, conditional) within the context of the application, noting that the data elements marked with an asterisk ( * ) must be indicated as mandatory by all applications that require the data record;

• must not remove or relax the constraints on data values for a data element used by the application; and

• may increase the constraints on data values for a data element used by the application.

The data model described for each data record assumes that the data record has been received and stored by an ASP System.

Where a data element has a range of values, interval notation describes the range. A square bracket indicates an inclusive value and a round bracket (parenthesis) indicates an exclusive value.

Examples: The notation [1,100] indicates that numbers 1 through 100 are valid. The notation [1,100) indicates that numbers 1 through 99 are valid.

Contents Alarm Record Data Model ........................................................................................................... E-2 Position Record Data Model ........................................................................................................ E-3 Speed Record Data Model .......................................................................................................... E-5 SD (Comments) Record Data Model ........................................................................................... E-6 SD (Vehicle Type/TCM) Record Data Model ............................................................................... E-7 Transfer Record Data Model ....................................................................................................... E-8 Mass Record Data Model ............................................................................................................ E-9 Mass Configuration Record Data Model .................................................................................... E-11 Mass Quality Record Data Model .............................................................................................. E-12 Mass Alarm Record Data Model ................................................................................................ E-13


E-2 TCA-S11-2.2

www.tca.gov.au

Alarm Record Data Model Each alarm record shall have the data model detailed in Table 14.

Table 14: Alarm Record Data Model

ID Name Data Type Data Values Remarks

ALM001 Record Date Time*

DateTime Not applicable UTC date and time of record generation as recorded by the telematics device

ALM002 Record Number Integer [0,9999999999] As recorded by the telematics device

ALM003 Alarm Code Integer [0,999] Event that triggered the alarm record (mapping of value from telematics device to alarm code of 1 to 12)

ALM004 Connected Device Type

Integer [0,99] Where the alarm record pertains to a connected device, the type of the connected device

ALM005 Connected Device ID

String 10–20 characters Where the alarm record pertains to a connected device, the ID of the connected device

ALM006 Receipt Date Time*

DateTIme Not applicable UTC date and time of record receipt by receiving system



E-3

Position Record Data Model Each position record shall have the data model detailed in Table 15.

Table 15: Position Record Data Model


POS001 Record Date Time*


POS002 Record Number Integer [0,9999999999] As recorded by the telematics device

POS003 Latitude Decimal [-90.00000, +90.00000]

Relative to the datum GDA94

POS004 Longitude Decimal [-180.00000, +180.00000]


POS005 Direction of Travel

Decimal [0.0,360.0) Decimal degrees from 000.0 to 359.9 (always one decimal place)

POS006 Satellite Count Integer [0,99]

POS007 Horizontal Dilution of Precision

Decimal [0.0,99.9] Decimal value

POS0098 Ignition Switch Status

Enumerated Not applicable Values: • Disconnected • Off • On

POS009 Movement Sensor Status

Enumerated Not applicable Values: • Disconnected • No Movement • Movement

POS010 Trailer ID #1 String 10–20 characters Trailer ID from first connected trailer

POS011 Trailer ID #2 String 10–20 characters Trailer ID from second connected trailer

POS012 Trailer ID #3 String 10–20 characters Trailer ID from third connected trailer

POS013 Trailer ID #4 String 10–20 characters Trailer ID from fourth connected trailer

POS014 Trailer ID #5 String 10–20 characters Trailer ID from fifth connected trailer

POS015 Trailer ID #6 String 10–20 characters Trailer ID from sixth connected trailer


E-4 TCA-S11-2.2

www.tca.gov.au


POS016 Trailer ID #7 String 10–20 characters Trailer ID from seventh connected trailer

POS017 Trailer ID #8 String 10–20 characters Trailer ID from eighth connected trailer

POS018 Trailer ID #9 String 10–20 characters Trailer ID from ninth connected trailer

POS019 Trailer ID #10 String 10–20 characters Trailer ID from tenth connected trailer

POS020 Receipt Date Time*

DateTIme Not applicable UTC date and time of record receipt by receiving system

POS021 Speed Decimal [000.0,999.9] Kilometres per hour

POS022 Positioning Service Availability

Enumerated Not applicable Values: • Unknown • Unavailable • Degraded • Available



E-5

Speed Record Data Model Each speed record shall have the data model detailed in Table 16. The speed threshold is extracted from the framing data and added to the record.

Table 16: Speed Record Data Model


SPD001 Record Date Time*


SPD002 Record Number Integer [0,9999999999] As recorded by the telematics device

SPD003 Latitude Decimal [-90.00000, +90.00000]


SPD004 Longitude Decimal [-180.00000, +180.00000]


SPD005 Speed Decimal [000.0,999.9] Kilometres per hour

SPD006 Satellite Count Integer [0,99]

SPD007 Horizontal Dilution of Precision

Decimal [0.0,99.9] Decimal value

SPD008 Trailer ID #1 String 10–20 characters Trailer ID from first connected trailer

SPD009 Trailer ID #2 String 10–20 characters Trailer ID from second connected trailer

SPD010 Trailer ID #3 String 10–20 characters Trailer ID from third connected trailer

SPD011 Trailer ID #4 String 10–20 characters Trailer ID from fourth connected trailer

SPD012 Trailer ID #5 String 10–20 characters Trailer ID from fifth connected trailer

SPD013 Trailer ID #6 String 10–20 characters Trailer ID from sixth connected trailer

SPD014 Trailer ID #7 String 10–20 characters Trailer ID from seventh connected trailer

SPD015 Trailer ID #8 String 10–20 characters Trailer ID from eighth connected trailer

SPD016 Trailer ID #9 String 10–20 characters Trailer ID from ninth connected trailer


E-6 TCA-S11-2.2

www.tca.gov.au


SPD017 Trailer ID #10 String 10–20 characters Trailer ID from tenth connected trailer

SPD018 Speed Threshold Decimal [000.0,999.9] Speed threshold setting stored in the telematics device, if applicable

SPD019 Receipt Date TIme*

DateTime Not applicable UTC date and time of record receipt by receiving system

SPD020 Positioning Service Availability

Enumerated Not applicable Values: • Unknown • Unavailable • Degraded • Available

SD (Comments) Record Data Model Each SD (comments) record shall have the data model detailed in Table 17.

Table 17: SD (Comments) Record Data Model


SDC001 Record Date Time*


SDC002 Record Number Integer [0,9999999999] As recorded by the telematics device. A value of 0 indicates generation by a non-user interface device.

SDC003 Version Number String 1–10 characters The version of the release of the code data set (e.g. National Telematics Map) against which the declaration was made

SDC004 Comment Code Integer [0,999] Predefined code to identify comment

SDC005 Comment Name String 1–100 characters Predefined comment text

SDC006 Comment Text String 1–256 characters Manually entered free-form text

SDC007 Receipt Date TIme*




E-7

SD (Vehicle Type/TCM) Record Data Model Each SD (vehicle type/TCM) record shall have the data model detailed in Table 18.

Table 18: SD (Vehicle Type/TCM) Record Data Model


SDM001 Record Date Time*


SDM002 Record Number Integer [0,9999999999] As recorded by the telematics device. A value of 0 indicates entry of SD data directly to the ASP System by the Operator (i.e. as an alternative to entry of SD data in a user interface).

SDM003 Version Number String MMMYY The version of the release of the code data set (e.g. National Telematics Map) against which the declaration was made

SDM004 Vehicle Category Code

Integer [0,99] Predefined code to identify vehicle category

SDM005 Vehicle Category Name

String 1–100 characters Predefine vehicle name and description

SDM006 Axle Count Integer [0,99] The value 0 is used to indicate the field is not applicable

SDM007 Mass Status Enumerated Not applicable Values: • Load • No Load

SDM008 Total Combination Mass

Decimal [000.0,999.9] Mass in tonnes. This should be blank where mass status is ‘N’, and should not be blank where mass status is ‘L’

SDM009 Receipt Date Time*



E-8 TCA-S11-2.2

www.tca.gov.au

Transfer Record Data Model Each transfer record shall have the data model detailed in Table 19. The transferred connected device record must be a data record as presented in this document.

Table 19: Transfer Record Data Model


TRF001 Record Date Time*


TRF002 Record Number Integer [0,9999999999] As recorded by the telematics device

TRF003 Connected Device Record

Not applicable

Not applicable The full connected device record

TRF004 Connected Device Type

Integer [0,99] A predefined code for the type of connected device as known by the telematics device. Values: 1 = OBM system

TRF005 Connected Device ID

String 10–20 characters The identifier of the connected device as known by the telematics device

TRF006 Receipt Date Time*




E-9

Mass Record Data Model Each mass record shall have the data model detailed in Table 20.

Note: Mass records are always transferred to the receiving system within transfer records, and thus do not include the data element Receipt Date Time.

Table 20: Mass Record Data Model


MSR001 Record Version Integer [0,99] Fixed value of 01

MSR002 Record Type Integer [0,99] Fixed value of 02

MSR003 Record Date Time*

DateTime Not applicable UTC date and time of record generation as recorded by the OBM system device

MSR004 ECU Record Number*

Integer [0,9999999999] As recorded by the OBM system

MSR005 ECU ID* String 10–20 characters The ID of the OBM system

MSR006 Gross Vehicle Mass

Integer [0,999999] Whole number of kilograms

MSR007 MSU Count Integer [0,99] Number of connected MSU. This data element must be present if MSU sub-records are present.

MSR008 Mass Record MSU Sub-Record

Not applicable

Not applicable One per MSU


E-10 TCA-S11-2.2

www.tca.gov.au

Each mass record MSU sub-record shall have the data model detailed in Table 20.1.

Table 20.1: Mass Record MSU Sub-Record Data Model


MSR100 MSU Sequence Number*

Integer [0,99] Sequence number of the MSU the record relates to, as applicable

MSR101 MSU ID* String 10–20 characters Identifier of the MSU the record relates to, as applicable

MSR102 Lift Axle Status Enumerated Not applicable Values: • axle group does not include a lift

axle, or is not capable of determining lift axle position;

• axle group includes a lift axle, but the position is currently unknown;

• axle group includes a lift axle, and the lift axle is detected as raised;

• axle group includes a lift axle, and the lift axle is detected as lowered

MSR103 Axle Group Mass Integer [0,99999] Whole number of kilograms



E-11

Mass Configuration Record Data Model Each mass configuration record shall have the data model detailed in Table 21.

Note: Mass configuration records are always transferred to the receiving system within transfer records, and thus do not include the data element Receipt Date Time.

Table 21: Mass Configuration Record Data Model


CON001 Record Version Integer [0,99] Fixed value of 01

CON002 Record Type Integer [0,99] Fixed value of 01

CON003 Record Date Time*


CON004 ECU Record Number*


CON005 ECU ID* String 10–20 characters The ID of the OBM system

CON006 MSU Count Integer [0,99] The number of connected MSUs. This data element must be present if MSU sub-records are present.

CON007 Mass Record MSU Sub-Record

Not applicable

Not applicable One per MSU

Each mass configuration record MSU sub-record shall have the data model detailed in Table 21.1.

Table 21.1: Mass Configuration Record MSU Sub-Record Data Model


CON100 MSU Sequence Number*


CON101 MSU ID* String 10–20 characters Identifier of the MSU the record relates to, as applicable


E-12 TCA-S11-2.2

www.tca.gov.au

Mass Quality Record Data Model Each mass quality record shall have the data model detailed in Table 22.

Note: Mass quality records are always transferred to the receiving system within transfer records, and thus do not include the data element Receipt Date Time.

Table 22: Mass Quality Record Data Model


QUA001 Record Version Integer [0,99] Fixed value of 01

QUA002 Record Type Integer [0,99] Fixed value of 03

QUA003 Record Date Time*

DateTIme Not applicable UTC date and time of record generation as recorded by the OBM system device

QUA004 ECU Record Number*


QUA005 ECU ID* String 10–20 characters The ID of the OBM system

QUA006 MSU Count Integer [0,99] Number of connected MSUs

QUA007 MSU Sequence Number


QUA007 MSU ID String 10–20 characters Identifier of the MSU the record relates to, as applicable

QUA007 Lift Axle Status Enumerated Not applicable Values: • axle group does not include a lift

axle, or is not capable of determining lift axle position;

• axle group includes a lift axle, but the position is currently unknown;

• axle group includes a lift axle, and the lift axle is detected as raised;

• axle group includes a lift axle, and the lift axle is detected as lowered

QUA010 Frequency of Axle Group Mass Data

Integer [0,999] Number of samples per second

QUA011 Number of Axle Group Mass Data

Integer [0,9999] Number of samples taken

QUA012 Axle Group Mass Data

<Integer>[n] [0,99999] High frequency mass readings



E-13

Mass Alarm Record Data Model Each mass alarm record shall have the data model detailed in Table 23.

Note: Mass alarm records are always transferred to the receiving system within transfer records, and thus do not include the data element Receipt Date Time.

Table 23: Mass Alarm Record Data Model


MAL001 Record Version Integer [0,99] Fixed value of 01

MAL002 Record Type Integer [0,99] Fixed value of 04

MAL003 Record Date Time*


MAL004 ECU Record Number*


MAL005 ECU ID * String 10–20 characters The ID of the OBM system

MAL006 Alarm Code Integer [0,99] Alarm code as defined in the On-Board Mass System Functional and Technical Specification

MAL007 MSU Sequence Number


MAL008 MSU ID String 10–20 characters Identifier of the MSU the record relates to, as applicable



F-1

Appendix F Business Data Model Modules and Supporting Schemas

Overview The structure of the TDE Business Data Model (as discussed in Section 4) allows for modules to be defined to support specific applications or groups of applications by extending the data types within the core packages. This appendix describes the currently defined TDE modules:

• iap – comprises artefacts to support the IAP application, and that are applicable to other applications that encompass parameters of speed, location and time; and

• mass – comprises artefacts to support the Intelligent Mass applications, and that are applicable to other applications that encompass parameters of mass and configuration.

The description of each module is presented by TDE Business Data Model package: common, conditions, enrolment form, event report, and enrolment report. The TDE core packages data records and data reporting are not extended by modules.

Included in the description of each module are the XML schemas that are used to encode the data types defined by the module.

Contents

Common – IAP Module.................................................................................................. F-2 Common – Mass Module ............................................................................................... F-3 Conditions – IAP Module ............................................................................................... F-5 Conditions – Mass Module .......................................................................................... F-12 Enrolment Form – IAP Module .................................................................................... F-15 Enrolment Form – Mass Module .................................................................................. F-19 Event Report – IAP Module ......................................................................................... F-22 Event Report – Mass Module ...................................................................................... F-28 Enrolment Report – IAP Module .................................................................................. F-32 Enrolment Report – Mass Module ............................................................................... F-33


F-2 TCA-S11-2.2

www.tca.gov.au

Common – IAP Module The iap module common package extends the core common package.

IAP Module Common Schema <?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="http://www.tca.gov.au/schemas/tde/iap/common/2018-07" xmlns:tns="http://www.tca.gov.au/schemas/tde/iap/common/2018-07" xmlns:common="http://www.tca.gov.au/schemas/tde/core/common/2018-07" xmlns:cond="http://www.tca.gov.au/schemas/tde/core/conditions/2018-07" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="unqualified" version="2018-07" > <xs:annotation> <xs:appinfo> <xs:documentation> <name>tde_iap_common_2018-07.xsd</name> <version>2018-07</version> <description>Telematics Data Exchange - IAP application </description> </xs:documentation> </xs:appinfo> </xs:annotation> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/common/2018-07" schemaLocation="tde_core_common_2018-07.xsd"/> <xs:simpleType name="TrailerTypeType"> <xs:annotation><xs:documentation> Data type for trailer type </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:minLength value="1" /> <xs:maxLength value="20"/> </xs:restriction> </xs:simpleType> <xs:simpleType name="TrailerNumberListType"> <xs:annotation><xs:documentation> Data type for list of trailer numbers (e.g. "1 3 5") </xs:documentation></xs:annotation> <xs:list itemType="xs:int"/> </xs:simpleType> </xs:schema>



F-3

Common – Mass Module The mass module common package extends the core common package.

Mass Module Common Schema <?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="http://www.tca.gov.au/schemas/tde/mass/common/2018-07" xmlns:tns="http://www.tca.gov.au/schemas/tde/mass/common/2018-07" xmlns:common="http://www.tca.gov.au/schemas/tde/core/common/2018-07" xmlns:cond="http://www.tca.gov.au/schemas/tde/core/conditions/2018-07" xmlns:enrol="http://www.tca.gov.au/schemas/tde/core/enrolment/2018-07" xmlns:evr="http://www.tca.gov.au/schemas/tde/core/event-report/2018-07" xmlns:enr="http://www.tca.gov.au/schemas/tde/core/enrolment-report/2018-07" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="unqualified" version="2018-07" > <xs:annotation> <xs:appinfo> <xs:documentation> <name>tde_mass_common_2018-07.xsd</name> <version>2018-07</version> <description>Telematics Data Exchange - mass application extensions to common types</description> </xs:documentation> </xs:appinfo> </xs:annotation> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/common/2018-07" schemaLocation="tde_core_common_2018-07.xsd"/> <xs:simpleType name="VehicleConfigurationType"> <xs:annotation><xs:documentation> Data type for vehicle configuration "axle group pattern" where: o each trailer is preceded by a hyphen and a single character indicating the type of trailer (P=pig D=dog S=semi L=lead Y=dolly X=unknown) o each trailer is described by a sequence of single digits, which each digit indicating how many tyres/wheels on each axle (e.g. 444 meaning 3 axles with 4 tyres on each) o each axle's wheel count can be followed by a lift axle status character (L=fitted and status unknown, U=up, D=down ... no character means not fitted) </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:pattern value="([2468][LUD]?)+(-([2468][LUD]?)+)+(/[PDSLYX]([2468][LUD]?)+ (\-([2468][LUD]?)+)*)*" /> </xs:restriction> </xs:simpleType> <xs:simpleType name="VehicleCategoryNameType"> <xs:annotation><xs:documentation> Data type for vehicle category name </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:minLength value="1" /> </xs:restriction> </xs:simpleType>


F-4 TCA-S11-2.2

www.tca.gov.au

<xs:simpleType name="VehicleCategoryCodeType"> <xs:annotation><xs:documentation> Data type for vehicle category code </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:minLength value="1" /> </xs:restriction> </xs:simpleType> <xs:simpleType name="VehicleCategoryDatasetNameType"> <xs:annotation><xs:documentation> Data type for vehicle category data set name </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:minLength value="1" /> </xs:restriction> </xs:simpleType> <xs:simpleType name="VehicleCategoryDatasetVersionType"> <xs:annotation><xs:documentation> Data type for vehicle category data set version number </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:minLength value="1" /> </xs:restriction> </xs:simpleType> <xs:complexType name="VehicleCaetgoryDatasetType"> <xs:annotation><xs:documentation> Description of a vehicle category data set (including name and version number) </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="name" type="tns:VehicleCategoryDatasetNameType" /> <xs:element name="version" type="tns:VehicleCategoryDatasetVersionType" /> </xs:sequence> </xs:complexType> </xs:schema>



F-5

Conditions – IAP Module The iap module conditions package extends the core conditions package.

The content of this package is concerned with operating conditions defined by the IAP and other telematics applications that consider vehicle parameters of speed, location and time. The high-level structure and contents of this package are shown in Figure 24.

Figure 24: IAP Module Conditions Package Data Model


F-6 TCA-S11-2.2

www.tca.gov.au

The significant data types within this package are listed in Table 24.

Table 24: IAP Module Conditions Package – Significant Data Types


Background Condition A condition that specifies whether the IAP background is Exclusion or Inclusion

Spatial Condition A base type from which spatial conditions are extended. Each instance specifies an access rule as Inclusion, Exclusion or Absolute Inclusion.

All Of Jurisdiction Condition A spatial condition that applies to the entire Jurisdiction. This spatial condition is generally qualified with a qualifying condition, for example to allow full Jurisdiction access during specific hours or while the vehicle is operating below a certain mass.

Route Condition A spatial condition that defines a road network route where access is allowed or not allowed

Bounded Zone Condition A spatial condition that defines a zone bounded by a road network where access is allowed or not allowed

Temporal Condition An operating condition that is always used to qualify base conditions, and that indicates when those base conditions are in effect

Speed Condition An operating condition that defines a speed threshold

SD TCM Condition An operating condition that specifies an operational mass limit based upon self-declared mass and vehicle category

SD Vehicle Category Threshold For SD TCM conditions, lists the mass limits for each possible total axle count for a specific self-declared vehicle category

SD TCM Threshold For SD TCM conditions, lists the mass limits for a single total axle count for a specific self-declared vehicle category

SD Comment Condition An operating condition that requires or allows SD comments to be captured



F-7

IAP Module Conditions Schema <?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="http://www.tca.gov.au/schemas/tde/iap/conditions/2018-07" xmlns:tns="http://www.tca.gov.au/schemas/tde/iap/conditions/2018-07" xmlns:common="http://www.tca.gov.au/schemas/tde/core/common/2018-07" xmlns:cond="http://www.tca.gov.au/schemas/tde/core/conditions/2018-07" xmlns:enrol="http://www.tca.gov.au/schemas/tde/core/enrolment/2018-07" xmlns:iap-common="http://www.tca.gov.au/schemas/tde/iap/common/2018-07" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="unqualified" version="2018-07" > <xs:annotation> <xs:documentation> <name>tde_iap_conditions_2018-07.xsd</name> <version>2018-07</version> <description>Telematics Data Exchange - iap module extensions to conditions types</description> </xs:documentation> </xs:annotation> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/common/2018-07" schemaLocation="tde_core_common_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/conditions/2018-07" schemaLocation="tde_core_conditions_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/enrolment/2018-07" schemaLocation="tde_core_enrolment_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/event-report/2018-07" schemaLocation="tde_core_event-report_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/enrolment-report/2018-07" schemaLocation="tde_core_enrolment-report_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/iap/common/2018-07" schemaLocation="tde_iap_common_2018-07.xsd"/> <xs:simpleType name="BackgroundRuleEnum"> <xs:annotation><xs:documentation> Background condition rule </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:enumeration value="EXCLUSION"/> <xs:enumeration value="INCLUSION"/> </xs:restriction> </xs:simpleType>


F-8 TCA-S11-2.2

www.tca.gov.au

<xs:simpleType name="SpatialRuleEnum"> <xs:annotation><xs:documentation> Spatial condition precedence rules </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:enumeration value="ABSOLUTE_INCLUSION"/> <xs:enumeration value="EXCLUSION"/> <xs:enumeration value="INCLUSION"/> </xs:restriction> </xs:simpleType> <xs:complexType name="SegmentType"> <xs:annotation><xs:documentation> Data type for link/segment within route and zone spatial conditions </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="pid" type="common:PersistentIdentifierType" /> <xs:element name="label" type="xs:string"/> </xs:sequence> </xs:complexType> <xs:complexType name="BackgroundConditionType"> <xs:annotation><xs:documentation> Background condition </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="cond:OperatingConditionType"> <xs:sequence> <xs:element name="backgroundRuleCode" type="tns:BackgroundRuleEnum" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="TemporalConditionType"> <xs:annotation><xs:documentation> Temporal condition - note that this is always a qualifying condition </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="cond:OperatingConditionType"> <xs:sequence> <xs:element name="dayTypeCode" type="common:DayTypeEnum" maxOccurs="unbounded"/> <xs:element name="conditionPeriod" type="common:DateTimePeriodType" minOccurs="0"> <xs:annotation> <xs:documentation> If no period is specified then this temporal condition applies to every day covered by the unique or off-the-shelf conditions. </xs:documentation> </xs:annotation> </xs:element>



F-9

<xs:element name="conditionInterval" type="common:TimePeriodType" minOccurs="0" maxOccurs="unbounded"> <xs:annotation> <xs:documentation> If no condition interval is specified then this temporal condition applies to every hour of every day that it covers (see conditionPeriod). </xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="SpatialConditionType" abstract="true" > <xs:annotation><xs:documentation> Base type for spatial conditions </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="cond:OperatingConditionType"> <xs:sequence> <xs:element name="spatialRuleCode" type="tns:SpatialRuleEnum"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="RouteConditionType"> <xs:annotation><xs:documentation> Route spatial conditions </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="tns:SpatialConditionType"> <xs:sequence> <xs:element name="startPoint" type="common:PointType" minOccurs="0" /> <xs:element name="endPoint" type="common:PointType" minOccurs="0" /> <xs:element name="segment" type="tns:SegmentType" maxOccurs="unbounded"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="BoundedZoneConditionType"> <xs:annotation><xs:documentation> Zone spatial conditions </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="tns:SpatialConditionType"> <xs:sequence> <xs:element name="segment" type="tns:SegmentType" maxOccurs="unbounded"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>


F-10 TCA-S11-2.2

www.tca.gov.au

<xs:complexType name="AllRoadsConditionType" > <xs:annotation><xs:documentation> All roads spatial condition </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="tns:SpatialConditionType"> <xs:sequence> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="SpeedConditionType" > <xs:annotation><xs:documentation> Speed condition </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="cond:OperatingConditionType"> <xs:sequence> <xs:element name="unit" type="common:SpeedUnitEnum" default="KMH" /> <xs:element name="value" type="common:SpeedValueType" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="SdTcmThresholdType"> <xs:annotation><xs:documentation> TCM threshold for a given vehicle type (being the variant of a vehicle category with a specific axle count) </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="axleCount" type="xs:int" /> <xs:element name="tcmThreshold" type="iap-common:SdVehicleMassType" /> </xs:sequence> </xs:complexType> <xs:complexType name="SdTcmVehicleCategoryThresholdType"> <xs:annotation><xs:documentation> TCM limits for all vehicle types associated with a given vehicle category </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="vehicleCategoryCode" type="common:GenericCodeType"/> <xs:element name="vehicleCategory" type="iap-common:SdVehicleCategoryType"/> <xs:element name="threshold" type="tns:SdTcmThresholdType" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType>



F-11

<xs:complexType name="SdTcmConditionType"> <xs:annotation><xs:documentation> SD (vehicle type/TCM) condition </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="cond:OperatingConditionType"> <xs:sequence> <xs:element name="vehicleCategoryThreshold" type="tns:SdTcmVehicleCategoryThresholdType" maxOccurs="unbounded"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="SdCommentConditionType"> <xs:annotation><xs:documentation> SD (comment) condition </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="cond:OperatingConditionType"> </xs:extension> </xs:complexContent> </xs:complexType> </xs:schema>


F-12 TCA-S11-2.2

www.tca.gov.au

Conditions – Mass Module The mass module conditions package extends the core conditions package.

The content of this package is concerned with operating conditions defined by Intelligent Mass and other telematics applications that consider vehicle parameters of mass and vehicle configuration. The high-level structure and contents of this package are shown in Figure 25.

Figure 25: Mass Module Conditions Package Data Model


Table 25: Mass Module Conditions Package – Significant Data Types


Mass Condition An operating condition for specifying a gross vehicle mass limit and per-axle group mass limits for nominated vehicle configurations. This operating condition can be used as a base condition or as a qualifying condition.

Vehicle Category Limits For mass conditions, specifies the gross vehicle mass limit and per-axle group mass limits for a given vehicle category

Vehicle Category For mass conditions, a vehicle category



F-13

Mass Module Conditions Schema <?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="http://www.tca.gov.au/schemas/tde/mass/conditions/2018-07" xmlns:tns="http://www.tca.gov.au/schemas/tde/mass/conditions/2018-07" xmlns:common="http://www.tca.gov.au/schemas/tde/core/common/2018-07" xmlns:cond="http://www.tca.gov.au/schemas/tde/core/conditions/2018-07" xmlns:enrol="http://www.tca.gov.au/schemas/tde/core/enrolment/2018-07" xmlns:evr="http://www.tca.gov.au/schemas/tde/core/event-report/2018-07" xmlns:enr="http://www.tca.gov.au/schemas/tde/core/enrolment-report/2018-07" xmlns:mass-common="http://www.tca.gov.au/schemas/tde/mass/common/2018-07" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="unqualified" version="2018-07" > <xs:annotation> <xs:appinfo> <xs:documentation> <name>tde_obm_conditions_2018-07.xsd</name> <version>2018-07</version> <description>Telematics Data Exchange - mass module extensions to conditions types</description> </xs:documentation> </xs:appinfo> </xs:annotation> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/common/2018-07" schemaLocation="tde_core_common_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/conditions/2018-07" schemaLocation="tde_core_conditions_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/enrolment/2018-07" schemaLocation="tde_core_enrolment_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/event-report/2018-07" schemaLocation="tde_core_event-report_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/enrolment-report/2018-07" schemaLocation="tde_core_enrolment-report_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/mass/common/2018-07" schemaLocation="tde_mass_common_2018-07.xsd"/> <xs:complexType name="VehicleCategoryType"> <xs:annotation><xs:documentation> Description of a vehicle category including code, name and axle group count </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="code" type="mass-common:VehicleCategoryCodeType" /> <xs:element name="name" type="mass-common:VehicleCategoryNameType" /> <xs:element name="axleGroupCount" type="xs:int" /> </xs:sequence> </xs:complexType>


F-14 TCA-S11-2.2

www.tca.gov.au

<xs:complexType name="VehicleCategoryLimitsType"> <xs:annotation><xs:documentation> Mass limits for a given vehicle category, comprising gross combination mass limit and per-axle group mass limit </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="category" type="tns:VehicleCategoryType" /> <xs:element name="vehicleMassLimit" type="mass-common:VehicleMassType" /> <xs:element name="axleGroupMassLimit" type="mass-common:VehicleMassType" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType> <xs:complexType name="ConditionsExtensionType" abstract="true"> <xs:annotation><xs:documentation> Mass application-specific extension to conditions that indicates the vehicle category dataset from which vehicle categories were taken. </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="cond:ConditionsExtensionType"> <xs:sequence> <xs:element name="vehicleCategoryDataset" type="mass-common:VehicleCaetgoryDatasetType" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="MassConditionType" > <xs:annotation><xs:documentation> Mass condition - can be used as either a base condition or a qualifying condition </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="cond:OperatingConditionType"> <xs:sequence> <xs:element name="vehicleCategoryLimits" type="tns:VehicleCategoryLimitsType" maxOccurs="unbounded" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> </xs:schema>



F-15

Enrolment Form – IAP Module The iap module enrolment package extends the core enrolment package. The content of this package is concerned with vehicle applicability based upon the identification of trailers and trailer combinations using Level 2 IVU capabilities. The high-level structure and contents of this package are shown in Figure 26

Figure 26: IAP Module Enrolment Package Data Model


Table 26: IAP Module Enrolment Package – Significant Data Types


Operator Section Extension A module-specific extension to the Operator section of the enrolment form, used for specifying trailers and trailer combinations for which the enrolment is applicable

Trailer Information Information about trailers and trailer combinations for which the enrolment is applicable

Trailer Unit Information Information about a specific trailer

Service Provider Section Extension

A module-specific extension to the ASP section of the enrolment form, used for providing information about installation of a trailer identification device (TID) to trailers

Trailer Unit Installation Information about installation of a TID to a specific trailer


F-16 TCA-S11-2.2

www.tca.gov.au

IAP Module Enrolment Form Schema <?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="http://www.tca.gov.au/schemas/tde/iap/enrolment/2018-07" xmlns:tns="http://www.tca.gov.au/schemas/tde/iap/enrolment/2018-07" xmlns:common="http://www.tca.gov.au/schemas/tde/core/common/2018-07" xmlns:cond="http://www.tca.gov.au/schemas/tde/core/conditions/2018-07" xmlns:enrol="http://www.tca.gov.au/schemas/tde/core/enrolment/2018-07" xmlns:iap-common="http://www.tca.gov.au/schemas/tde/iap/common/2018-07" xmlns:iap-cond="http://www.tca.gov.au/schemas/tde/iap/conditions/2018-07" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="unqualified" version="2018-07" > <xs:annotation> <xs:appinfo> <xs:documentation> <name>tde_module_iap_2018-07.xsd</name> <version>2018-07</version> <description>Telematics Data Exchange - iap module extensions to enrolment types</description> </xs:documentation> </xs:appinfo> </xs:annotation> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/common/2018-07" schemaLocation="tde_core_common_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/conditions/2018-07" schemaLocation="tde_core_conditions_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/enrolment/2018-07" schemaLocation="tde_core_enrolment_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/event-report/2018-07" schemaLocation="tde_core_event-report_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/enrolment-report/2018-07" schemaLocation="tde_core_enrolment-report_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/iap/common/2018-07" schemaLocation="tde_iap_common_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/iap/conditions/2018-07" schemaLocation="tde_iap_conditions_2018-07.xsd"/> <xs:simpleType name="TrailerIdentificationLevelEnum"> <xs:annotation><xs:documentation> IVU type (Level 1 or Level 2) </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:enumeration value="LEVEL_1"/> <xs:enumeration value="LEVEL_2"/> </xs:restriction> </xs:simpleType>



F-17

<xs:complexType name="TrailerUnitInstallationType"> <xs:annotation><xs:documentation> Details for installation of TIDs on a specific trailer </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="enrol:VehicleInstallationType"> <xs:sequence> <xs:element name="trailerNumber" type="xs:int" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="TrailerUnitInformationType"> <xs:annotation><xs:documentation> Details of a specific trailer </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="common:VehicleInformationType"> <xs:sequence> <xs:element name="make" type="common:VehicleMakeType"/> <xs:element name="model" type="common:VehicleModelType"/> <xs:element name="trailerNumber" type="xs:int"/> <xs:element name="garagingAddress" type="common:AddressType" minOccurs="0"/> <xs:element name="trailerType" type="iap-common:TrailerTypeType"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="TrailerInformationType"> <xs:annotation><xs:documentation> Details for trailer combinations that are applicable for a given enrolment </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="trailerCount" type="xs:int"/> <xs:element name="trailerUnitInformation" type="tns:TrailerUnitInformationType" maxOccurs="unbounded"/> <xs:element name="trailerUnitCombination" type="iap-common:TrailerNumberListType" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType>


F-18 TCA-S11-2.2

www.tca.gov.au

<xs:complexType name="OperatorSectionExtensionType"> <xs:annotation><xs:documentation> IAP extension to Operator section to include applicable trailer combinations </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="enrol:OperatorSectionExtensionType"> <xs:sequence> <xs:element name="trailerIdentificationLevelCode" type="tns:TrailerIdentificationLevelEnum"/> <xs:element name="trailerInformation" type="tns:TrailerInformationType" minOccurs="0"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="ServiceProviderSectionExtensionType"> <xs:annotation><xs:documentation> IAP extension to ASP section to include TID installation details </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="enrol:ServiceProviderSectionExtensionType"> <xs:sequence> <xs:element name="trailerUnitInstallation" type="tns:TrailerUnitInstallationType" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> </xs:schema>



F-19

Enrolment Form – Mass Module The mass module enrolment package extends the core enrolment package.

The content of this package is concerned with the enrolment applicability based upon the identification of vehicle configuration using data collected by an OBM system. The high-level structure and contents of this package are shown in Figure 27.

Figure 27: Mass Module Enrolment Package Data Model


Table 27: Mass Module Enrolment Package – Significant Data Types


Operator Section Extension A module-specific extension to the Operator section of the enrolment form, used for specifying vehicle categories associated with identified vehicle configurations


F-20 TCA-S11-2.2

www.tca.gov.au

Mass Module Enrolment Form Schema <?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="http://www.tca.gov.au/schemas/tde/mass/enrolment/2018-07" xmlns:tns="http://www.tca.gov.au/schemas/tde/mass/enrolment/2018-07" xmlns:common="http://www.tca.gov.au/schemas/tde/core/common/2018-07" xmlns:cond="http://www.tca.gov.au/schemas/tde/core/conditions/2018-07" xmlns:enrol="http://www.tca.gov.au/schemas/tde/core/enrolment/2018-07" xmlns:mass-common="http://www.tca.gov.au/schemas/tde/mass/common/2018-07" xmlns:mass-cond="http://www.tca.gov.au/schemas/tde/mass/conditions/2018-07" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="unqualified" version="2018-07" > <xs:annotation> <xs:appinfo> <xs:documentation> <name>tde_module_obm_2018-07.xsd</name> <version>2018-07</version> <description>Telematics Data Exchange - mass module extensions to enrolment types</description> </xs:documentation> </xs:appinfo> </xs:annotation> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/common/2018-07" schemaLocation="tde_core_common_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/conditions/2018-07" schemaLocation="tde_core_conditions_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/enrolment/2018-07" schemaLocation="tde_core_enrolment_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/event-report/2018-07" schemaLocation="tde_core_event-report_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/enrolment-report/2018-07" schemaLocation="tde_core_enrolment-report_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/mass/common/2018-07" schemaLocation="tde_mass_common_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/mass/conditions/2018-07" schemaLocation="tde_mass_conditions_2018-07.xsd"/> <xs:complexType name="VehicleCategoryInformationType"> <xs:annotation><xs:documentation> Mapping between a vehicle category and a vehicle configuration (as described by an axle group pattern) </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="category" type="mass-cond:VehicleCategoryType" /> <xs:element name="forConfiguration" type="mass-common:VehicleConfigurationType" maxOccurs="unbounded" /> </xs:sequence> </xs:complexType>



F-21

<xs:complexType name="OperatorSectionExtensionType" > <xs:annotation><xs:documentation> Extension to enrolment that maps vehicle categories for which the enrolment is applicable </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="enrol:OperatorSectionExtensionType"> <xs:sequence> <xs:element name="vehicleCategoryDataset" type="mass-common:VehicleCaetgoryDatasetType" /> <xs:element name="vehicleApplicability" type="tns:VehicleCategoryInformationType" maxOccurs="unbounded"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> </xs:schema>


F-22 TCA-S11-2.2

www.tca.gov.au

Event Report – IAP Module The iap module event report package extends the core event report package.

The content of this package is concerned with the reporting of events that result from assessment of operating conditions pertaining to parameters of location, time, speed and self-declared mass and configuration. The high-level structure and contents of this package are shown in Figure 28.

Figure 28: IAP Module Event Report Package Data Model



F-23


Table 28: IAP Module Event Report Package – Significant Data Types


Event Report Extension A module-specific extension to the event report used for the purposes of listing trailers detected during the identification of the reported event

Trailer Unit Information A trailer detected during the identification of the reported event, including details of the installed TID

Position Record An event report record that wraps a position record

Speed Record An event report record that wraps a speed record

SD Comment Record An event report record that wraps an SD (comment) record

SD TCM Record An event report record that wraps an SD (vehicle type/TCM) record

Last Known Position The last known position of the vehicle, and the time at which that last known position was valid

Location The location of the vehicle relative to the NTM


F-24 TCA-S11-2.2

www.tca.gov.au

IAP Module Event Report Schema <?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="http://www.tca.gov.au/schemas/tde/iap/event-report/2018-07" xmlns:tns="http://www.tca.gov.au/schemas/tde/iap/event-report/2018-07" xmlns:common="http://www.tca.gov.au/schemas/tde/core/common/2018-07" xmlns:cond="http://www.tca.gov.au/schemas/tde/core/conditions/2018-07" xmlns:enrol="http://www.tca.gov.au/schemas/tde/core/enrolment/2018-07" xmlns:evr="http://www.tca.gov.au/schemas/tde/core/event-report/2018-07" xmlns:enr="http://www.tca.gov.au/schemas/tde/core/enrolment-report/2018-07" xmlns:iap-common="http://www.tca.gov.au/schemas/tde/iap/common/2018-07" xmlns:iap-cond="http://www.tca.gov.au/schemas/tde/iap/conditions/2018-07" xmlns:iap-enrol="http://www.tca.gov.au/schemas/tde/iap/enrolment/2018-07" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="unqualified" version="2018-07" > <xs:annotation> <xs:appinfo> <xs:documentation> <name>tde_module_iap_2018-07.xsd</name> <version>2018-07</version> <description>Telematics Data Exchange - iap module extensions to event report types</description> </xs:documentation> </xs:appinfo> </xs:annotation> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/common/2018-07" schemaLocation="tde_core_common_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/data-record/2018-07" schemaLocation="tde_core_data-record_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/conditions/2018-07" schemaLocation="tde_core_conditions_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/enrolment/2018-07" schemaLocation="tde_core_enrolment_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/event-report/2018-07" schemaLocation="tde_core_event-report_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/enrolment-report/2018-07" schemaLocation="tde_core_enrolment-report_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/iap/common/2018-07" schemaLocation="tde_iap_common_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/iap/conditions/2018-07" schemaLocation="tde_iap_conditions_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/iap/enrolment/2018-07" schemaLocation="tde_iap_enrolment_2018-07.xsd"/> <xs:simpleType name="IgnitionStatusEnum" > <xs:annotation><xs:documentation> Ignition status values </xs:documentation></xs:annotation>



F-25

<xs:restriction base="xs:string"> <xs:enumeration value="ON" /> <xs:enumeration value="OFF" /> <xs:enumeration value="DISCONNECTED" /> </xs:restriction> </xs:simpleType>

<xs:simpleType name="MovementSensorStatusEnum" > <xs:annotation><xs:documentation> Movement sensor values </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:enumeration value="MOVEMENT" /> <xs:enumeration value="NO_MOVEMENT" /> <xs:enumeration value="DISCONNECTED" /> </xs:restriction> </xs:simpleType>

<xs:simpleType name="VehicleLoadStatusEnum"> <xs:annotation><xs:documentation> Vehicle load status values </xs:documentation></xs:annotation> <xs:restriction base="xs:string"> <xs:enumeration value="LOAD"/> <xs:enumeration value="NO_LOAD"/> </xs:restriction> </xs:simpleType>

<xs:simpleType name="EventTypeEnum"> <xs:annotation><xs:documentation> IAP device event types </xs:documentation></xs:annotation> <xs:restriction base="evr:EventTypeType"> <xs:enumeration value="SPATIAL" /> <xs:enumeration value="SPEED" /> <xs:enumeration value="SD_TCM" /> <xs:enumeration value="TEMPORAL" > <xs:annotation><xs:documentation>This is an event subtype</xs:documentation> </xs:annotation> </xs:enumeration> </xs:restriction> </xs:simpleType>

<xs:complexType name="LocationType"> <xs:annotation><xs:documentation> Location as described by NTM data </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="pid" type="common:PersistentIdentifierType" /> <xs:element name="roadName" type="xs:string"/> <xs:element name="locality" type="xs:string"/> <xs:element name="stateCode" type="common:StateEnum"/> </xs:sequence> </xs:complexType>


F-26 TCA-S11-2.2

www.tca.gov.au

<xs:complexType name="LastKnownPositionType"> <xs:annotation><xs:documentation> Last known position as "remembered" from the most recent position (or speed) record that meets certain quality constraints </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="deviceDateTime" type="xs:dateTime" /> <xs:element name="position" type="common:PointType" /> <xs:element name="satelliteCount" type="xs:int"/> <xs:element name="hdopValue" type="common:HdopValueType"/> <xs:element name="jurisdictionDateTime" type="xs:dateTime" /> <xs:element name="location" type="tns:LocationType" minOccurs="0"/> </xs:sequence> </xs:complexType> <xs:complexType name="PositionRecordType"> <xs:annotation><xs:documentation> The event report container around a position record </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="evr:ReportRecordType"> <xs:sequence> <xs:element name="deviceRecord" type="data:DevicePositionRecordType"/> <xs:element name="location" type="tns:LocationType" minOccurs="0"/> <xs:element name="compliant" type="xs:boolean"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="SpeedRecordType"> <xs:annotation><xs:documentation> The event report wrapper around a speed record </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="evr:ReportRecordType"> <xs:sequence> <xs:element name="deviceRecord" type="data:DeviceSpeedRecordType"/> <xs:element name="speedCondition" type="data:SpeedType"/> <xs:element name="location" type="tns:LocationType" minOccurs="0"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>



F-27

<xs:complexType name="SdCommentRecordType"> <xs:annotation><xs:documentation> The event report wrapper around an SD (comment) record </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="evr:ReportRecordType"> <xs:sequence> <xs:element name="deviceRecord" type="data:DeviceSdCommentRecordType"/> <xs:element name="fromDevice" type="xs:boolean"/> <xs:element name="lastKnownPosition" type="tns:LastKnownPositionType" minOccurs="0" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="SdTcmRecordType"> <xs:annotation><xs:documentation> The event report wrapper around an SD (vehicle type/TCM) record </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="evr:ReportRecordType"> <xs:sequence> <xs:element name="deviceRecord" type="data:DeviceSdTcmRecordType"/> <xs:element name="fromDevice" type="xs:boolean"/> <xs:element name="lastKnownPosition" type="tns:LastKnownPositionType" minOccurs="0" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="TrailerUnitInformationType"> <xs:annotation><xs:documentation> Information about a single trailer being reported in an event report </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="common:VehicleInformationType"> <xs:sequence> <xs:element name="installedDevice" type="data:DeviceIdentityType"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="EventReportExtensionType"> <xs:annotation><xs:documentation> IAP extension to event report that allows reporting of which trailers (with TIDs fitted) were considered in determining applicable enrolments </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="evr:EventReportExtensionType"> <xs:sequence> <xs:element name="trailerUnit" type="tns:TrailerUnitInformationType" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> </xs:schema>


F-28 TCA-S11-2.2

www.tca.gov.au

Event Report – Mass Module

The mass module event report package extends the core event report package.

The content of this package is concerned with the reporting of events that result from assessment of operating conditions pertaining to parameters of mass and configuration. The high-level structure and contents of this package are shown in Figure 29.

Figure 29: Mass Module Event Report Package Data Model



F-29


Table 29: Mass Module Event Report Package – Significant Data Types


Event Report Extension A module-specific extension to the event report used for the purposes of listing trailers detected during the identification of the reported event

Trailer Unit Information A trailer detected during the identification of the reported event, including details of the installed MSU

Last Known Vehicle Mass The last known gross vehicle mass and per-axle group mass, and the date and time when that mass was known

Last Known Vehicle Configuration The last known vehicle configuration, and the date and time when that vehicle configuration was known

Applicable Vehicle Category A cross-reference to an enrolment form that was applicable based upon the determined vehicle configuration, and the vehicle category against which enrolment form applicability was determined


F-30 TCA-S11-2.2

www.tca.gov.au

Mass Module Event Report Schema <?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="http://www.tca.gov.au/schemas/tde/mass/event-report/2018-07" xmlns:tns="http://www.tca.gov.au/schemas/tde/mass/event-report/2018-07" xmlns:common="http://www.tca.gov.au/schemas/tde/core/common/2018-07" xmlns:cond="http://www.tca.gov.au/schemas/tde/core/conditions/2018-07" xmlns:enrol="http://www.tca.gov.au/schemas/tde/core/enrolment/2018-07" xmlns:evr="http://www.tca.gov.au/schemas/tde/core/event-report/2018-07" xmlns:mass-common="http://www.tca.gov.au/schemas/tde/mass/common/2018-07" xmlns:mass-cond="http://www.tca.gov.au/schemas/tde/mass/conditions/2018-07" xmlns:mass-enrol="http://www.tca.gov.au/schemas/tde/mass/enrolment/2018-07" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="unqualified" version="2018-07" > <xs:annotation> <xs:appinfo> <xs:documentation> <name>tde_module_mass_2018-07.xsd</name> <version>2018-07</version> <description>Telematics Data Exchange - mass module extensions to event report types</description> </xs:documentation> </xs:appinfo> </xs:annotation> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/common/2018-07" schemaLocation="tde_core_common_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/conditions/2018-07" schemaLocation="tde_core_conditions_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/enrolment/2018-07" schemaLocation="tde_core_enrolment_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/event-report/2018-07" schemaLocation="tde_core_event-report_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/enrolment-report/2018-07" schemaLocation="tde_core_enrolment-report_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/mass/common/2018-07" schemaLocation="tde_mass_common_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/mass/conditions/2018-07" schemaLocation="tde_mass_conditions_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/mass/enrolment/2018-07" schemaLocation="tde_mass_enrolment_2018-07.xsd"/> <xs:simpleType name="EventTypeEnum"> <xs:annotation><xs:documentation> Data type for event types defined by mass application </xs:documentation></xs:annotation> <xs:restriction base="evr:EventTypeType"> <xs:enumeration value="MASS" /> </xs:restriction> </xs:simpleType>



F-31

<xs:complexType name="ApplicableVehicleCategoryType"> <xs:annotation><xs:documentation> Reference to an applicable enrolment, and the applicable vehicle category within the enrolment against which the vehicle configuration (axle group pattern) was matched </xs:documentation></xs:annotation> <xs:sequence> <xs:element name="enrolmentIdentifier" type="enrol:EnrolmentIdentifierType" /> <xs:element name="category" type="mass-cond:VehicleCategoryType" /> </xs:sequence> </xs:complexType> <xs:complexType name="LastKnownVehicleConfigurationType"> <xs:annotation><xs:documentation> The last known configuration. In the case that no vehicle configuration can be determined (i.e. is blank/void), the vehicleConfiguration element is omitted (through the enclosing sequence having minOccurs="0") </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="evr:ReportRecordType"> <xs:sequence minOccurs="0" > <xs:element name="vehicleConfiguration" type="mass-common:VehicleConfigurationType" /> <xs:element name="applicableVehicleCategory" type="tns:ApplicableVehicleCategoryType" minOccurs="0" maxOccurs="unbounded" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="LastKnownVehicleMassType"> <xs:annotation><xs:documentation> The last known mass. In the case that no reliable vehicle mass can be determined (i.e. is blank/void), all elements are omitted (through the enclosing sequence having minOccurs="0") </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="evr:ReportRecordType"> <xs:sequence minOccurs="0"> <xs:element name="grossVehicleMass" type="data:VehicleMassType" /> <xs:element name="axleGroupMass" type="data:VehicleMassType" maxOccurs="unbounded" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>


F-32 TCA-S11-2.2

www.tca.gov.au

<xs:complexType name="TrailerUnitInformationType"> <xs:annotation><xs:documentation> Trailer information that allows trailer registration, VIN and MSU identifier can be correlated) </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="common:VehicleInformationType"> <xs:sequence> <xs:element name="installedDevice" type="data:DeviceIdentityType"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="EventReportExtensionType"> <xs:annotation><xs:documentation> Mass application-specific extension to event report that allows correlation of trailer details with MSU installation details </xs:documentation></xs:annotation> <xs:complexContent> <xs:extension base="evr:EventReportExtensionType"> <xs:sequence> <xs:element name="trailerUnit" type="tns:TrailerUnitInformationType" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> </xs:schema>



F-33

Enrolment Report – IAP Module The iap module enrolment report package extends the core enrolment report package.

IAP Module Enrolment Report Schema <?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="http://www.tca.gov.au/schemas/tde/iap/enrolment-report/2018-07" xmlns:tns="http://www.tca.gov.au/schemas/tde/iap/enrolment-report/2018-07" xmlns:common="http://www.tca.gov.au/schemas/tde/core/common/2018-07" xmlns:cond="http://www.tca.gov.au/schemas/tde/core/conditions/2018-07" xmlns:data="http://www.tca.gov.au/schemas/tde/core/data-record/2018-07" xmlns:enrol="http://www.tca.gov.au/schemas/tde/core/enrolment/2018-07" xmlns:evr="http://www.tca.gov.au/schemas/tde/core/event-report/2018-07" xmlns:enr="http://www.tca.gov.au/schemas/tde/core/enrolment-report/2018-07" xmlns:iap-common="http://www.tca.gov.au/schemas/tde/iap/common/2018-07" xmlns:iap-cond="http://www.tca.gov.au/schemas/tde/iap/conditions/2018-07" xmlns:iap-ae="http://www.tca.gov.au/schemas/tde/iap/enrolment/2018-07" xmlns:iap-evr="http://www.tca.gov.au/schemas/tde/iap/event-report/2018-07" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="unqualified" version="2018-07" > <xs:annotation> <xs:documentation> <name>tde_module_iap_2018-07.xsd</name> <version>2018-07</version> <description>Telematics Data Exchange - iap module extensions to enrolment report types</description> </xs:documentation> </xs:annotation> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/common/2018-07" schemaLocation="tde_core_common_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/conditions/2018-07" schemaLocation="tde_core_conditions_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/enrolment/2018-07" schemaLocation="tde_core_enrolment_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/event-report/2018-07" schemaLocation="tde_core_event-report_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/enrolment-report/2018-07" schemaLocation="tde_core_enrolment-report_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/iap/common/2018-07" schemaLocation="tde_iap_common_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/iap/conditions/2018-07" schemaLocation="tde_iap_conditions_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/iap/enrolment/2018-07" schemaLocation="tde_iap_enrolment_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/iap/event-report/2018-07" schemaLocation="tde_iap_event-report_2018-07.xsd"/> </xs:schema>


F-34 TCA-S11-2.2

www.tca.gov.au

Enrolment Report – Mass Module The mass module enrolment report package extends the core enrolment report package.

Mass Module Enrolment Report Schema <?xml version="1.0" encoding="UTF-8"?> <xs:schema targetNamespace="http://www.tca.gov.au/schemas/tde/mass/enrolment-report/2018-07" xmlns:tns="http://www.tca.gov.au/schemas/tde/mass/enrolment-report/2018-07" xmlns:common="http://www.tca.gov.au/schemas/tde/core/common/2018-07" xmlns:cond="http://www.tca.gov.au/schemas/tde/core/conditions/2018-07" xmlns:enrol="http://www.tca.gov.au/schemas/tde/core/enrolment/2018-07" xmlns:evr="http://www.tca.gov.au/schemas/tde/core/event-report/2018-07" xmlns:enr="http://www.tca.gov.au/schemas/tde/core/enrolment-report/2018-07" xmlns:mass-common="http://www.tca.gov.au/schemas/tde/mass/common/2018-07" xmlns:mass-cond="http://www.tca.gov.au/schemas/tde/mass/conditions/2018-07" xmlns:mass-enrol="http://www.tca.gov.au/schemas/tde/mass/enrolment/2018-07" xmlns:mass-evr="http://www.tca.gov.au/schemas/tde/mass/event-report/2018-07" xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="unqualified" version="2018-07" >

<xs:annotation> <xs:appinfo> <xs:documentation> <name>tde_module_mass_2018-07.xsd</name> <version>2018-07</version> <description>Telematics Data Exchange - mass module extensions to enrolment report types</description> </xs:documentation> </xs:appinfo> </xs:annotation>

<xs:import namespace="http://www.tca.gov.au/schemas/tde/core/common/2018-07" schemaLocation="tde_core_common_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/conditions/2018-07" schemaLocation="tde_core_conditions_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/enrolment/2018-07" schemaLocation="tde_core_enrolment_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/event-report/2018-07" schemaLocation="tde_core_event-report_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/core/enrolment-report/2018-07" schemaLocation="tde_core_enrolment-report_2018-07.xsd"/>

<xs:import namespace="http://www.tca.gov.au/schemas/tde/mass/common/2018-07" schemaLocation="tde_mass_common_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/mass/conditions/2018-07" schemaLocation="tde_mass_conditions_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/mass/enrolment/2018-07" schemaLocation="tde_mass_enrolment_2018-07.xsd"/> <xs:import namespace="http://www.tca.gov.au/schemas/tde/mass/event-report/2018-07" schemaLocation="tde_mass_event-report_2018-07.xsd"/>

</xs:schema>



G-1

Appendix G Form and Report Representations

Overview This section contains ‘human-readable’ versions of the enrolment form, event report, and enrolment report, which correspond to TDE XML schemas in Appendix B.

Note that what is presented here is only the base form of the document. These will be extended by one or more modules as required by the application. Any extensible part of these documents is indicated by <extended by module(s)>.

Contents

Enrolment Form ............................................................................................................. F-2 Event Report.................................................................................................................. F-8 Enrolment Report ........................................................................................................ F-11


G-2 TCA-S11-2.2

www.tca.gov.au

Enrolment Form The enrolment form sets out the data that is collected and contained within the enrolment. The following is a representation of an enrolment form, showing where additional fields may be extended by one or more modules.

A pro forma document may be used to collect enrolment data from an Operator, but completed parts of the enrolment form are transmitted between the Authority and the ASP.

Responsibility for completion of parts of the enrolment form, and notification upon completion, depend upon whether the enrolment is managed by the ASP or the Authority, and the enrolment process required by the application.



G-3

* An asterisk indicates required information

Enrolment Form

Indicate the telematics application that governs the production and interpretation of this document and include the version of the appropriate functional and technical specification. Application name:* Functional and technical

specification version:

Enrolment ID:* If this enrolment replaces a cancelled enrolment, provide details of the previous enrolment in the box below. Previous enrolment ID: Indicate the party that is responsible for management of this enrolment.

Enrolment Manager:* ASP Authority

Indicate the enrolment status. Note: Some status values are not applicable to some applications.

Enrolment status:* Interim Approved Interim Cancelled

Approved Denied

Cancelled

Indicate any identifiers known to be used by parties other than the Enrolment Manager to refer to this enrolment or the management of this enrolment. Second party reference(s):

NOTE Second party references are provided to allow parties other than the Enrolment Manager to correlate the enrolment (and changes to the enrolment) with their own business processes and systems.

Enrolment commencement time and date:* hrs / / (hrs dd/mm/yyyy) Enrolment cessation time and date: hrs / / (hrs dd/mm/yyyy)

N O T E Operation under this enrolment cannot occur until approved by the Enrolment Manager.


G-4 TCA-S11-2.2

www.tca.gov.au

PART 1 – Authority Details and Conditions

Authority Details

Details of the Authority for which this enrolment is being issued Name of Authority:*

Postal address Enquiries

Address 1:* Address 2: City/Suburb:* State:* Postcode:*

Phone:* ( ) Fax:* ( ) Email:*

Scheme and Operating Conditions

Name of scheme:*

Operating conditions are (select ONE only): Off-the-shelf Unique

Not applicable (select for a monitoring application)

NOTE

Off-the-shelf conditions are referenced: Off-the-shelf conditions ID:

Unique conditions are specified below.

Operating conditions are left blank for a monitoring application.

Unique qualifying operating conditions – extensions

<extended by module(s)>

Unique base operating conditions – extensions




G-5

PART 2 –Operator Details

Details of the Operator applying for this enrolment

Operator:* Company name:* ABN:* ACN:

Postal address Enquiries


Phone (bus. hours):* ( ) Phone (after hours): ( ) Fax: ( ) Email:

Nominated officer for Operator

Name: Title/Position: Contact phone:

Comments / further information:

Prime mover/rigid truck details

Make: Model: Body type: Registration No:* State:* Vehicle Identification Number (VIN): OR Non-VIN ID (if no VIN available):* VIN: Non-VIN:

Garaging address Street address: City/Suburb: State: Postcode:

N O T E If using non-VIN ID, use chassis number, and if this is unavailable, use engine number. When issued to the Operator, the interim enrolment does not include the vehicle VIN or vehicle non-VIN ID.

Part 2 – Extension



G-6 TCA-S11-2.2

www.tca.gov.au

PART 3 – ASP and Telematics Device Installation Details

ASP details

Company name:* ABN:* ACN:

Postal address: Enquiries:


Phone:* ( ) Fax:* ( ) Email:*

Comments / further information:

Time and date:* hrs / / (hrs dd/mm/yyyy)

Details of prime mover/rigid truck in which the telematics device is installed

Vehicle Identification Number (VIN) OR Non-VIN ID (if no VIN)* VIN: Non-VIN:

N O T E Either the VIN or non-VIN ID must be supplied so that the Authority can verify that the equipment has been installed in the prime mover/rigid truck as listed in Part 2 of the enrolment form. If using non-VIN ID use the chassis number, and if this is unavailable, use the engine number.

Details of the installed telematics device

Telematics device ID:* Time and date telematics device installed:* hrs / / (hrs dd/mm/yyyy) Telematics device location:*

GPS antenna location:*



G-7

Part 3 Extension – Details of installed connected devices (if any)


Part 3 Extension - Details of installed trailer identification device (if any)


PART 4 – Completed by the Enrolment Manager

Approval of enrolment

This application to enter the telematics application is:* Approved Denied

Comments/further information:

Enrolment approved/denied time and date:* hrs / / (hrs dd/mm/yyyy)

Authorised by:* Title/position:* Phone:*

For ASP or Authority use only

If the ASP or Authority cancels this enrolment, then the following information must be supplied Comments/further information:

Enrolment cancelled time and date:* hrs / / (hrs dd/mm/yyyy) Authorised by:* Title/position:* Phone:*

Note: Once the ASP or Authority has considered all submitted details and approved or denied the enrolment application:

• the ASP or Authority issues the entire enrolment (Parts 1 to 4) to the other party (Authority or ASP) within the B2B environment; and

• communication between the Authority and the Operator proceeds outside of the B2B environment as specified in the Authority’s guidelines.


G-8 TCA-S11-2.2

www.tca.gov.au

Event Report The following is a representation of an event report, which sets out the supporting data that is provided by the ASP to an Authority when reporting events. The detail in this representation provides a sample report layout for an event report, showing where additional fields may be extended by one or more modules.

Event Report

Details of the event report

Event report ID: If this event report is a continuation event report, supply the ID for the previous event report:

Event report was generated by the service provider on (ASP local time): hrs / / (hrs dd/mm/yyyy)

Audit reference date/time stamp (Authority local time): At the time of the audit reference date/time stamp the following versions were implemented in the ASP System Application name: Application version: National Telematics Map version:


Details of applicable enrolment(s)

Name of Authority for which this enrolment was issued:

Enrolment ID: Name of scheme: Off-the-shelf conditions ID (if applicable): Off-the-shelf conditions revision number (if applicable):

Enrolment ID: Name of scheme: Off-the-shelf conditions ID (if applicable): Off-the-shelf conditions revision number (if applicable):

All applicable enrolments over the period of this event report are listed.



G-9

Details (current) of the Application Service Provider (ASP) forwarding this event report

Company name: ABN: ACN:


Address 1: Address 2: City/Suburb: State: Postcode:

Phone (bus. hours): ( ) Fax: ( ) Email:

Nature of event

Event type: Each telematics application will define its own events, and for condition events, any conditions that qualify condition events. The first column contains the nature of the event: either alarm or the base condition of a condition event. For a condition event, the second column contains any qualifying conditions against which the event was identified.

Nature of event (select ONE only)

For a condition event, list any conditions that qualify the event

Alarm Qualifying Condition(s):

Condition:

Summary of event (where applicable)

Event began: (Authority local time) hh:mm:ss dd/mm/yyyy (UTC time) hh:mm:ss dd/mm/yyyy UTC

Initial position: latitude and longitude (decimal degrees) Event ended: (Authority local time) hh:mm:ss dd/mm/yyyy

(UTC time) hh:mm:ss dd/mm/yyyy UTC Final position: latitude and longitude (decimal degrees) Total duration of the event was: hours minutes seconds

Prime mover/rigid truck details

Details of the prime mover/rigid truck being operated by the Operator during the non-compliant activity

Registration No: State:

Vehicle Identification Number (VIN) OR Non-VIN ID (if no VIN)* Telematics Device ID VIN: Non-VIN:


G-10 TCA-S11-2.2

www.tca.gov.au

Trailer details continue for all trailers which were connected to the prime mover/rigid truck.

Event details

Event report alarm records will be output (as defined in the application functional and technical specification) in substantiation of reportable activity.

Records for other types of event reports will be output in substantiation of reportable activity as defined by the applicable application functional and technical specification. Examples include event report position record, event report speed record, event report self-declared records, event report mass record and event report connected device record.

The format of the respective records is guided by the XML schema within Appendix B. The records for alarm event reports are briefly described below.

Event report alarm record type 1

Event report alarm record Type 1

Authority local date and time

Record number UTC date/time generated

Alarm code Connected device type (if relevant)

Connected device ID

(if relevant)

Event report derived alarm record

Event report derived alarm record (e.g. Type 2A, Type 2B)

Authority local date and time

Alarm code

Alarm type (e.g. 2A, 2B)

UTC date/time of last generated telematics device data record that

contributed to the alarm being identified

Connected device type (if relevant)

Connected device ID

(if relevant)

Additional record




G-11

Enrolment Report The following is a representation of an enrolment report, which sets out the aggregated data that is provided by the ASP to an Authority. The detail in this representation also provides a sample report layout for an enrolment report.

Enrolment Report

Details of the enrolment report

Report for period starting (Authority local time): ending: Enrolment report ID: Enrolment report was generated by the ASP on (ASP local time): hrs / / (hrs dd/mm/yyyy)

Application name: Application version:


Details of the Authority

Name of Authority:

Details of the Application Service Provider (ASP) forwarding this enrolment report

Company name: ABN: ACN:


Address 1: Address 2: City/Suburb: State: Postcode:

Phone (bus. hours): ( ) Fax: ( ) Email:


G-12 TCA-S11-2.2

www.tca.gov.au

Vehicle details Enrolment details Enrolments Number of event reports issued

VIN or non-VIN

ID

Telematics device

ID

Entered during period on hh:mm:ss

dd/mm/yyyy

Exited during period on hh:mm:ss

dd/mm/yyyy

Enrolment identifier

Enrolled scheme

Type Count Subtype Count

(e.g. Spatial) (e.g. Temporal)

(e.g. Alarm)

Total number of vehicles monitored during the period: Notes: 1. Details for ‘Entered during period’ are only required if the vehicle had its first enrolment issued during the period

being reported upon by the enrolment report. If the vehicle was already operating at the commencement of the reporting period, then ‘Entered during period’ is left blank.

2. Details for ‘Exited during period’ are only required if the vehicle had its last enrolment ‘ceased’ or ‘cancelled’ during the period being reported upon by the enrolment report. If the vehicle was still operating at the end of the reporting period, then ‘Exited during period’ is left blank.

3. Telematics device identifier shows the most recently installed telematics device.

4. The count of enrolment reports of a given type may not always match the sum of the count of subtypes as subtypes are not required to be discrete (i.e. some enrolment reports may simultaneously be of multiple subtypes).



G-1
