Technical Standards & Data

Technical Standards

The technical standards advice and actions represent the working position of NSTAB on the core technical area of standards within Scotland, and considers this from a multi-modal timetable, fare and product/token perspective.

The advice and actions are based on two operational principles. Firstly, that wherever possible and appropriate, it is considered preferable to utilise and develop existing standards, rather than create new ones; and secondly it is considered preferable to integrate with existing platforms/services, where they are suitable and offer best value.

However, it also acknowledges that there may be a need for integrating services/software which may not presently exist through new approaches and standards.

Data and the Single Source of Truth (SST) Dataset

The data advice and actions represents the working position of NSTAB on the core area of Multi-Modal Journey & Product (including fares) data and considers this from a national muti-modal timetable development, timetable information, fares and retail perspective.

Central to this, is the recommendation to develop a “Single Source of Truth” (SST) multi-modal national transport dataset for Scotland to support Journey Planning, Customer Support, RTPI, Enhanced Customer Accessibility, Service Registrations and Product Retail. This approach aligns in part with the work being undertaken by Transport Scotland in this area.

Such a national SST dataset should include direct cross-border services including ferries to Northern Ireland; should support existing UK modal datasets where possible for bus, rail & coach services and support new modal datasets for Ferry, Metro and Tram services as applicable.

The national SST dataset should be capable of being available under open licence as a free national feed, as well as being ready to support commercial licensing with third party accredited product retailers.

It is considered essential that such an SST be developed and in place by the end of the Medium Term and desirable within 3 years.

Short Term Advisory Recommendations for Standards and Data

Project Reference Description Priority Cost Comments
STA1a Create and publish a Standards Guide for Ticketing including devices, and continually monitor developing standards to refresh Standards Guide as appropriate High No Not Applicable
STA2a Engage with Members to define process for a Single Source of Truth (SST) National Transport Dataset High Low Not Applicable

Medium Term Advisory Recommendations for Standards and Data

Project Reference Description Priority Cost Comments
STA1b Review and Refresh the Standards Guide for Ticketing based on developing standards and opportunities High Low Not Applicable
STA2b Develop the Single Source of Truth (SST) National Transport Dataset High Medium Not Applicable
STA2c Develop a Licensing Agreement of Single Source of Truth (SST) and issue for 3rd party product retail where commercially endorsed High Low Income generating

Long Term Advisory Recommendations for Standards and Data

Project Reference Description Priority Cost Comments
STA1c Review and Refresh the Standards Guide for Ticketing based on developing standards and opportunities High Low Not Applicable
STA2d Maintain the Single Source of Truth (SST) National Transport Dataset High Low Not Applicable
STA2e Maintain the Licensing Agreement of Single Source of Truth (SST) 3rd party product retail High Medium Not Applicable
STA3 Review National Transport Strategy with inclusion of NSTAB work High No Not Applicable

Standards and Advisory Recommendations for Individual Product Types

In relation to the retailing of individual product types, it is advised that for at least the Short to Medium Term, Customers should be supported to use their ‘token’ of choice – be it ITSO Smart / Other Smart / Barcode / QR Code / cEMV / ABT and Paper where this is the preference of the Scheme Owner.

To enable this, it is important that the standards to do so are defined, and in support of Action 1.1 are maintained over time. With many such standards either new or in development, it is important these are monitored and contributed to as applicable. As such, the required Technical Standards and the advisory recommendations for each of the main product types are shown below on a token by token basis.

Account Based Ticketing (ABT)

The Standards to underpin the ongoing support for and development of an ABT Back Office are as follows:

  1. Back office to back office APIs (open) – TBC - New
  2. Industry Standard Retail APIs for front office retail
  3. PCI (latest version) – PCI Council
  4. Entitlement validation APIs (open) – New with external system
  5. Front Office Device (FOD) Standard (Open APIs) – TBC New
  6. Reporting APIs and/ or reporting capabilities (open) – TBC - New
  7. A set of clear requirements & business rules covering as a minimum:
  • List Management
  • User-friendly names
  • Product Management
  • Settlement & Apportionment
  • Journey construction & product selection
  • Key management & business rules

For the ABT Middle Office, the Standards required include:

  1. Front Office Device (FOD) – TBC - New
  2. PCI (latest version) – PCI Council
  3. ITSO HOPS (ITSO only) - ITSO
  4. Retail APIs (open) – TBC – New
  5. A set of clear requirements & business rules covering as a minimum:
  • List Management
  • Monitoring APIs (open)
  • Key management

Short Term Advisory Recommendations for ABT

Project Reference

Description

Priority

Cost

Comments

ABT1

Work with ScotRail and operators of other modes to outline options to progress Barcode PAYG on additional modes via TF2 standard

Low

Low

Liaise with ScotRail

ABT2a

Map out core principles of Nationwide Shared Multi-operator / Multi-modal ABT Platform supporting multiple token types, multiple product owner products, discounted travel and entitlement based travel. Prepare procurement Specification.

High

Low

Not Applicable 

ABT3

Engage with Schemes which already support cEMV to develop trials of interoperable areas

Medium

Medium

Not Applicable 

ABT4

Continue engagement with RDG re: Tap Aggregator on rail, and Project Coral - Tap Aggregator on Bus

High

No

Not Applicable 

ABT7a

Procure, develop and maintain the ABT Back Office in line with the following Standards: 1. Back office to back office APIs (open) – TBC - New
2. Industry Standard Retail APIs for front office retail
3. PCI (latest version) – PCI Council
4. Entitlement validation APIs (open) – New with external system
5. FOD Standard (Open APIs) – TBC - New6. Reporting APIs and/ or reporting capabilities (open) – TBC - New
7. A set of clear requirements & business rules covering as a minimum:
• List Management
• User-friendly names
• Product Management
• Settlement & Apportionment
• Journey construction & product selection
• Key management & business rules

High

No/Low

 Not Applicable

ABT8a

Procure, develop and maintain the ABT Middle Office in line with the following Standards: 1. FOD – TBC - New
2. PCI (latest version) – PCI Council
3. ITSO HOPS (ITSO only) - ITSO
4. Retail APIs (open) – TBC – New
5. A set of clear requirements & business rules covering as a minimum:
• List Management
• Monitoring APIs (open)
• Key management
• List Management

High

No/Low

 Not Applicable

Medium Term Advisory Recommendations for ABT

Project Reference

Description

Priority

Cost

Comments

ABT2b

Procure and Implement a Nationwide Shared Multi-operator / Multi-modal ABT Platform supporting multiple token types, multiple product owner products, discounted travel and entitlement based travel. Also - See PCR2

High

Medium / High

 Not Applicable

ABT5

Integrate with RDG re: Tap Aggregator on rail, and Project Coral - Tap Aggregator as relevant or develop own based on BCR's

High

Medium

 Not Applicable

ABT7b

Continue to maintain and develop the Technical Standards of the ABT Back Office in line with ABT7a.

High

No/Low

 Not Applicable

ABT8b

Continue to maintain and develop the Technical Standards of the ABT Middle Office in line with ABT8a.

High

No/Low

 Not Applicable

Long Term Advisory Recommendations for ABT

Project Reference Description Priority Cost Comments
ABT2c Maintain and enhance Nationwide Shared Multi-operator / Multi-modal ABT Platform supporting multiple token types High Medium Not Applicable
ABT6 Reduce token types as they become inefficient / no longer desired by the customer based on monitoring and research of token types High No Not Applicable
ABT7c Refine, Reduce, Enhance the ABT Back Office Technical Standards applicable under ABT7b. High No/Low Not Applicable
ABT8c Refine, Reduce, Enhance the ABT Middle Office Technical Standards applicable under ABT8b. High No/Low `Not Applicable

Barcode and QR Code Ticketing

The Standards to underpin the ongoing support for and development of Barcode and QR Code Ticketing are as follows:

  • National Multi modal barcode/QR code standard – TF2
  • Rail barcode - RDG
  • Bus barcode - TBC
  • List Management (accept and deny) – Requirement
  • Near real-time comms - Requirement

Short Term Advisory Recommendations for Barcodes / QR Codes

Project Reference Description Priority Cost Comments
BAR1a Promote / Support a White Label shared approach for all SME modes to retail via Barcodes Medium Low Brand at RTP Level
BAR2a Develop & Test TF2 interoperable Barcode Specification available to all Suppliers on an open licence basis including throughput timing tests High Low Not Applicable
BAR3a Promote consolidated App(s) offering Multiple single modal or operator product retailing - as data suitability improves High Low / Medium Not Applicable
BAR4 Research ability for Barcodes to acquire and manage entitlement (concessions) eligibility digitally High Low Not Applicable
BAR5a Work with Transport Scotland / NECPO to develop Business Case & Legal Amendments for Rolling out Barcode based entitlement (concessions) supported by BAR2 where possible Medium Low Not Applicable
BAR6 Increase Barcode scanning capability across operators and modes within Scotland Medium Medium Not Applicable
BAR7 Develop PlusBus on Barcodes based on TF2 Specification. Low No ScotRail are working on this - but not necessarily on TF2 standard.

Medium Term Advisory Recommendations for Barcodes / QR Codes

Project Reference Description Priority Cost Comments
BAR1b Roll out White Label approach for all SME modes to retail via Barcodes High Low Not Applicable
BAR2b Make BAR2 interoperable Barcode Specification available to all Suppliers on an open licence basis High Low / Medium Not Applicable
BAR3b Encourage the uptake of consolidated App(s) offering Multiple single and multi-modal product retailing based on SST dataset via Traveline Scotland and/or others and utilising TF2 Standard High Low Not Applicable
BAR5b Support the Rolling out of Barcode based entitlement (concessions) where desired High Low Not Applicable

Contactless Europay Mastercard Visa (cEMV) Ticketing

The Standards to underpin the ongoing support for and development of cEMV Ticketing are as follows:

  1. RDG EMV Tokenisation - RDG
  2. EMV Level 1-2 (3 as part of overall solution) - EMV
  3. PCI (latest version) – PCI Council
  4. Mass Transit Ticketing (MTT) - EMV
  5. UKCA Models 2 and 3 – UKCA
  6. Front Office Device interface standards – TBC – New
  7. List Management (accept and deny) – Requirement

Short Term Advisory Recommendations for cEMV

Project Reference

Description

Priority

Cost

Comments

EMV1

Consult upon & develop a business case for a support programme to equip vehicles and stations with cEMV and Tap Off Readers across modes including rail

High

No

 Not Applicable

EMV2

Develop and Implement a support programme to equip vehicles and stations with cEMV and Tap Off Readers across modes including rail

High

Low

Not Applicable 

EMV3

Investigate and align with emerging standards and processes, and to work with existing cEMV-based schemes and operators

High

Low

 Not Applicable

EMV4a

Identify opportunities for efficiency gain - such as shared / single PSP provision

High

Low

Not Applicable 

EMV5a

Monitor current developments of cEMV token registration for discounted travellers

Medium

No

Not Applicable 

EMV6

Research & Develop ability for cEMV to acquire and manage entitlement (concessions) eligibility digitally

High

Low

Not Applicable 

EMV7

Engage with Schemes to develop trials of interoperable areas

Medium

Medium

Not Applicable 

EMV9a

Maintain and develop cEMV in line with the following Standards: 1. RDG EMV Tokenisation - RDG
2. EMV Level 1-2 (3 as part of overall solution) - EMV
3. PCI 4 (latest version) – PCI Council
4. Mass Transit Ticketing (MMT) - EMV
5. VISA MTT
6. Front Office Device interface standards – TBC – New
7. List Management (accept and deny) – Requirement

High

No/Low

Not Applicable 

Medium Term Advisory Recommendations for cEMV

Project Reference Description Priority Cost Comments
EMV4b Deliver identified efficiency gains - such as shared / single PSP provision High Medium Not Applicable
EMV8 Use emerging standards and processes as basis for open cEMV platform across modes High Medium Not Applicable
EMV9b Continue to maintain and develop the Technical Standards for cEMV in line with EMV9a. High No/Low Not Applicable

Long Term Advisory Recommendations for cEMV

Project Reference Description Priority Cost Comments
EMV4c Enhance shared efficiency gains - such as single PSP provision etc High No Not Applicable
EMV5b Open cEMV platform across modes for ABT - aligned with ABT2 High Medium / High Not Applicable
EMV9c Refine, Reduce, Enhance the cEMV Technical Standards applicable under EMV9b. High No/Low Not Applicable

ITSO Smartcard Ticketing

The Standards to underpin the ongoing support for and development of ITSO Smartcard Ticketing are as follows:

  1. Upgrade to 1.5 of the ITSO Specification
  2. Upgrade to V4 ISAMs as a minimum
  3. Maintaining rail ITSO standards – such as RSP3002

ITSO is already the core platform for entitlement ticketing on bus and ferry services, and with the new ITSO Specification available, as well as ITSO on Mobile opportunities, it is considered there is no need to include longer term advisory recommendations at this time.

Short Term Advisory Recommendations for ITSO Smartcards

Project Reference Description Priority Cost Comments
ITS1a Review the ITSO supply arrangements for the concessions scheme to ensure continuity of supply Low No Not Applicable
ITS2a Fully identify and implement where appropriate realistic plans for ITSO on Mobile on both Android and iOS platforms for all product types High Medium Not Applicable
ITS3a Ensure upgrade to ITSO Spec v2.1.5 across all ITSO estate elements High Low / Medium Not Applicable
ITS4a Upgrade ISAMs to v4 High Low / Medium Not Applicable
ITS5 Source / Build IP67 Readers for ITSO use on Ferries Medium Low Not Applicable
ITS6a Encourage migration of remaining non-ITSO Smartcards to ITSO Smartcards High Low Not Applicable
ITS7 Encourage migration to cEMV / Barcode where viable and suitable Low No Not Applicable

Medium Term Advisory Recommendations for ITSO Smartcards

Project Reference Description Priority Cost Comments
ITS1b Secure through effective standards led procurement the ITSO supply arrangements for the entitlement Scheme to ensure continuity of supply High No Not Applicable
ITS2b Business Case and BCR roll out of ITSO on Mobile (Android & Apple) for entitlement and commercial product types Medium Low / Medium Not Applicable
ITS3b Upgrade to ITSO Spec v2.1.5 across all elements and deliver value from the upgrade. High No / Low Not Applicable
ITS4b Maximise value from upgrading ISAMs to v4 High No / Low Not Applicable
ITS6b Conclude migration of non-ITSO Smartcards to ITSO Smartcards High No / Low Not Applicable