itso development project - whatdotheyknow · pdf file0.3 document history . revision date...

© 2013 Cubic Transportation Systems Ltd. All rights reserved. This information is confidential.

of 12

AFC House, Honeycrock Lane Salfords, Surrey

RH1 5LA United Kingdom

Tel: +44(0) 1737 782200 Fax: +44(0) 1737 789759

ITSO on Prestige

ITSO Development Project

RSPS3002 Gap Analysis

Works Order Number: 3621-2180

Document Number: 9459-67129

Revision: A

01 August 2013 Release Priority: Urgent

UNCONTROLLED PRINT Unless Release Approval Signature present below

Author Project Manager Release Authority ... ...

Print: Andy Gray

Sign:

Date:

Print: JP Vibert

Sign:

Date:

Print:

Sign:

Date:

Print:

Sign:

Date:

Print:

Sign:

Date:

Authorising Manager Quality Assurance ... ... ...

Print: Warwick Mullan

Sign:

Date:

Print:

Sign:

Date:

Print:

Sign:

Date:

Print:

Sign:

Date:

Print:

Sign:

Date:

FTA-FR001-9459-67129

CUBIC Doc. No. 9459-67129 Rev A ITSO on Prestige ITSO Development Project RSPS3002 Gap Analysis


of 12

0 Preliminaries 0.1 Published By

Cubic Transportation Systems Limited, AFC House, Honeycrock Lane, Salfords, Surrey, UK, RH1 5LA Tel: +44 (0) 1737 782200, Fax +44 (0) 1737 789759

0.2 Copyright

© 2013 Cubic Transportation Systems Ltd

This document is the copyright of Cubic Transportation Systems Limited and the information therein may be the subject of a pending or granted patent. It may not be reproduced or used for any other purpose than for which it is supplied without the written permission of Cubic Transportation Systems Limited.

0.3 Document History

Revision Date Author Works Order Number DRM (where applicable)

A 2/8/13 Andy Gray 3621-2180

0.4 Reason for Change / Change Description

This Revision (Rev A): First release comparing IOP business rules implementation against RSPS3002 version 2.0.

0.5 Internal Distribution

Name Department Name Department

Chris Golding Project Engineering Warwick Mullan Programme Manager

Andrew Bohanna Systems Test Paul Monk Systems Engineering

JP Vibert Project Management

Mario Gallotta Project Management

0.6 External Distribution

Name Organisation Name Organisation

0.7 Change Marking

Where implemented, changes, relating to the content only, since the latest revision of this document have been marked by a vertical line in the left or right hand margin adjacent to the change.

0.8 Effective Pages

Main Document: 12

Attached Sheets 0

0.9 Bibliography

0.9.1 Referenced Documents

[1] RSPS3002, ITSO in National Rail – Specification, Version 02-00, June 2013

[2] ITSO/DGC0022, Developer Guidance – POST SETs Managing and Messaging

FTA-FR001-9459-67129



of 12

[3] 9459-67061 DfT IOP Business Rules Phase 3, IOP Ticket Logic Tests

[4] ITSO/TN0404D1, Technical Note ITSO – Part 6 – 0207/8 message & TY 24 IPE clarification

0.9.2 Associated Publications

0.9.3 Glossary

HOPS Host or Operator Processing System

IPE ITSO Product Entity

PAYG Pay As You Go

POST Reader with ITSO capability

PV Passenger validator

STR Stored Travel Rights

TIS Ticket Issuing System

0.9.4 Abbreviations / Acronyms

CTSL Cubic Transportation Systems Limited

TfL Transport for London

Note: The abbreviations for each document shall be compiled to reflect any used.

FTA-FR001-9459-67129



of 12

Table of Contents 0 Preliminaries............................................................................................................................. 2

0.1 Published By ....................................................................................................................................... 2

0.2 Copyright ............................................................................................................................................. 2

0.3 Document History ................................................................................................................................ 2

0.4 Reason for Change / Change Description .......................................................................................... 2

0.5 Internal Distribution ............................................................................................................................. 2

0.6 External Distribution ............................................................................................................................ 2

0.7 Change Marking .................................................................................................................................. 2

0.8 Effective Pages ................................................................................................................................... 2

0.9 Bibliography ......................................................................................................................................... 2

0.9.1 Referenced Documents ............................................................................................................... 2

0.9.2 Associated Publications ............................................................................................................... 3

0.9.3 Glossary ....................................................................................................................................... 3

0.9.4 Abbreviations / Acronyms ............................................................................................................ 3

1 Introduction .............................................................................................................................. 5

1.1 Requirement and Scope ..................................................................................................................... 5

2 Gap Analysis ............................................................................................................................ 6

FTA-FR001-9459-67129



of 12

1 Introduction 1.1 Requirement and Scope

This document contains a comparison of the DfT IOP Business Rules (see [3] and the contents of the RSPS3002 ITSO on National Rail specification (see [1]).

FTA-FR001-9459-67129



of 12

2 Gap Analysis The following table identifies sections of RSPS3002 which have potential gap issues against the current or planned IOP implementation.

Ref RSPS3002 Section RSPS3002 Detail IOP Implementation Gap Consequence(s)

G1 2.4.1 Cardholder no present RSPS3002 states that fulfilment actions shall

be supported by HOPS and POSTs within National Rail.

IPE Fulfilment Actions will not be supported until IDP3B.

Until IDP3B products may only be created using the CREATE IPE action with all the associated restrictions.

G2 2.4.3 Published POST Sets – agreed industry format

RSPS3002 states that “POST Set number zero” will be used to distribute hotlist items to all POSTs within an OID.

Although this is supported, there was an update made to Developer Guide 22 (see [2]) section 3.4 that states that set 0 :

“Indicates all Set addressed POSTs that are not currently allocated to a specific SET by the Set owner.”

This conflicts with the proposed usage in RSPS3002.

The TfL HOPS makes the assumption that SET 0 is as defined by by RSPS3002. However this conflicts with DG 22.

A SET ID of 0 will always cause actionlists to be distributed to all POSTs within an OID even though this was not intended by the third party operator.

It is recommended that a non zero SET ID is used for broadcasting of hotlists so there is no ambiguity.

G3 3.2 Rail products on TYP2 – OPTIONAL

Appendix C – Implementation of PAYG ticketing on national rail - OPTIONAL

RSPS3002 defines a Stored Travel Rights (Pay As You Go) product.

No support for TYP2 STR products. TYP2 products will not be able to be validated on Cubic devices.

However, Cubic do support the Southern PAYG season (TYP 22 PTYP 4) where charging is managed within the Southern Backoffice.

G4 3.4 Railcards or other discount entitlements on TYP14.

RSPS3002 provides a definition of TYP14 product to be used for railcards and other discount entitlements.

No check is made during validation for the existence of a railcard or discount entitlement product. The assumption is made that any checks are performed during the retailing of the product.

If no check for discount entitlement is made during the retail of the product, then a customer could travel without any entitlement..

A product will be able to be loaded via an action without checking for a railcard product. It is assumed a check is made vai the TIS.

A renewable product could potentially continue to be valid after a discount entitlement has expired.

G5 3.5 Personalisation using TYP16 or TYP 14 (TOC issued)

RSPS3002 provides a definition of TYP14 and TYP16 products to be used for identification purposes.

No validation are performed on TYP14 and TYP16 identification products.

A customer could potentially travel with someone else’s card as no identification checks are made.

FTA-FR001-9459-67129



of 12

G6 3.6 ConcessionaryPassIssueCostCentre RSPS3002 states that for ENCTS products, the ConcessionaryPassIssueCostCentre (CPICC) element may be used to identify validity at a location.

There is no checking of the CPICC element.

A customer may potentially be able to use their ENCTS product at an invalid location, if a POSTat that configured to accept the product OID/TYP/PTYP combination.

G7 3.6 ConcessionaryClass RSPS3002 defines a number of Concessionary Classes which implies that the element should be validated.

There is no checking of the ConcessionaryClass element.

Operators will be unable to configure POSTs to reject selected Concessionary Classes Customers.

TOC gates will have the capability of monitoring and rejecting passengers using Special Rules.

G8 3.7.3 TYP22 PassbackTime

3.8.3 TYP23 PassbackTime

RSPS3002 defines passback times for both TYP22 and TYP23 products.

POSTs always uses a single site specific passback time from the ITSO station Configuration table . Individual products can be disabled for passback using ITSO product Information table.

Any passback times defined by product owners will be ignored.

Avoids complexity of selecting a passback time when multiple products selected.

No consequence for Southern products as all are defined with 0 passback time meaning use the POST settings.

G9 3.7.3 TYP22 ValidOnDayCode RSPS3002 states that this field must match the TYP22Flags

No specific check is made to compare all the bits of ValidOnDay against the related TYP22Flags fields. However, at the point of validation the appropriate bit is matched against the relevant TYP22Flags field.

The product won’t be rejected if any of the bits/fields don’t match. It will only be rejected if the relevant bits/fields don’t match at the time of validation.

G10 3.7.6 TYP22 ValidityCode

3.8.6 TYP23 ValidityCode

RSPS3002 does not define how time restrictions are associated with Validity Codes or when they should be applied.

Validity Codes are associated with different time restrictions based on origin and destination station groups through base data configuration.

Operators must configure time restrictions associated with Validity Codes at each station location and all possible destination groups.

G11 3.7.4 TYP22 IIN data element present

3.8.4 TYP23 IIN data element present

3.9.4 TYP24 IIN present

RSPS3002 specifies the “IIN present” bit in each IPE bitmap must be set to 0 indicating that the IIN is not included in the IPE data group.

IOP Business Rules specifies it must be set to 1.

IOP Business rules stipulate this bitmap is always set to 1 indicating the IIN product is present.

IOP actually accepts products with the bit set to which means that the IIN has to be configured in the POST global settings table.

The current system will not support more than one IIN. As there is not expected to be any more IINs defined in the near future, this is not considered a problem.

FTA-FR001-9459-67129



of 12

G12 3.8.7TYP23/ CountRemainingJourneyRides

3.9.3 TYP24/NumberOfJourneysSold

For TYP23 products, RSPS3002 specifies that for a Carnet then alternate journeys will represent out and return journeys.

For TYP24 products, RSPS3002 defines the concept of single and Return Carnet but also defines bidirectional carnets under ProductTypeEncoding.

IDP2/3A only supports single carnets valid in one direction only.

IDP3B will support only bidirectional carnets so each product can be used in either direction.

Until IDP3B is available, passengers will only be able to travel in one direction with Carnets which does not meet with Southerns Trip Carnet product requirements.

After IDP3B only bdirectional carnets will be available. Single and Return carnets will not be supported.

G13 3.8.7 TYP23ValueFlags/UsedChecked bit RSPS3002 indicates this should always be set to zero and doesn’t use it for any validation.

This field in the same way as the TYP24 JourneyPartUsedFlag to record when a Break of Journey or OSI has taken place. It is used on re-entry to re-credit the journey count.

This potentially allows TYP23 products to be used in BoJ/OSI situations in the same way as TYP24 products. BoJ can still be switched off in base data for TYP 23 products.

G14 3.9.3 TYP24/RestrictionCode

3.9.3 TYP24/DaysTravelPermitted

3.9.3 TYP24/DaysRestrictionApplies

RSPS3002 defines a value of 11111111 for DaysTravelPermitted to indicate that travel is permitted every day, and a value of 00000000 to indicate that Restrictions are not to be applied any day. No rules are provided on how to use RestrictionCode

Only the TYP24 RestrictionCode field is used to look up time and day restrictions in base data based on the origin and destination of the products.

This provides a flexible solution to allow TYP 24 products to be restricted to certain times and days.

G15 3.9.3 TYP24/PermittedInterchangeTime RSPS3002 states :

“Interchange time permitted will not be stored in the IPE and will be configured in the Rail Validator “

The interchange time from the product will be used if it is defined. Otherwise a default time configured in base data will be used.

If a product is created with an interchange time against the RSPS3002 definition then the interchange time will be used in preference to the base data value.

This solution provides more flexibility to the product owner.

G16 3.9.3 TYP24/TransferEntitlementType

3.9.3 TYP24/NumbertOfTransfers

4.8 MU16 decrement of TransfersRemaining

RSPS3002 states that TransferEntitlementType must be set to 2 to enable Break of Journey and that NumberOfTransfers should be set to a value of 511 which is used to set the initial value of TransfersRemaining. TransfersRemaining should get decremented whenever a Break of Journey is performed.

Only the vaklue of TransferEntitlementType is checked (value=2) to determine if BoJ is allowed. TransfersRemaining does not get decremented.

Passengers are able to perform as many Break of Journeys as they wish between the origin and destination of a product. The RSPS3002 solution currently limits this to 511 which is effectively the same thing.

FTA-FR001-9459-67129



of 12

G17 4.1.1 Product Deletion RSPS3002 states

“The oldest expired product should be deleted where there are no free directory entries available by the relevant processing POSTS in the Rail environment. Product Deletions should only take place if the TT is closed, if it is not closed and can be closed during the current operation (e.g. as part of an Exit), then it should be closed before the deletion takes place. “

Cubic POSTS only attempts to delete products when a new product is being created

Expired products are only deleted during processing of Create IPE actions if there is no space for the new products. It is attempted to delete all expired products – not just the latest.

The method of deletion uses a more efficient ISAM option that doesn’t require the product to be verified or a seal generated for the empty sector. The ISAM provides authority to delete expired products. This method of deletion requires that the certified date of the ISAM must be greater than the product Expiry. The certified date must therefore be kept continually updated with Keep Alive messages.

The current method of deletion minimises the impact of deleting products during normal validations, ie. that don’t include product creations. However, if a number of expired products have accumulated then the impact on performance when deleting products during a Create IPE action will be more noticeable.

One consequence on using this strategy is that if other devices are not allowed to delete products then there will be no way to make space for new products except during actionlist processing.

TfL ISAMs are currently not profiled to allow ad hoc deletion of products. However, with the advent of fulfilment action support, there will be a requirement to be able to delete products on demand. The criteria on the ISAMs will therefore need to be re-profiled to allow deletion.

G18 4.3.11 Identification of half-used return RSPS3002 states that a half-used return cannot be distinguished from a single.

CUBIC posts use product information based data to identify TYP23 products as single or returns.

Allows TYP 23 products to be used in the same way as TYP 24 single and return products.

G19 4.6 Stored Travel Rights / Pay As You Go

4.7.7 OP20 to OP28

RSPS3002 specifies, and defines the operations for, an optional Stored Travel Right/PAYG scheme based on the TYP 2 IPE.

RSPS3002 STR/PAYG products are not supported.

Any TYP2 products on cards will be ignored

Only Southern, TYP 22 PAYG products will be supported but these are treated as any other TYP22 products. All STR charging is performed in the Southern backoffice.

G20 4.7.7 OP5 Reverse Decrement RSPS3002 defines an optional operation for undoing Check Outs on an attended device.

Reverse decrements are not supported. Reverse decrements are only applicable to attended devices so should not affect the operation of unattended devices such as PVs and gates.

G21 4.7.7 OP6 to OP8 RSPS3002 define a number of inspection operations intended for handheld inspection devices.

Inspection operations are not supported on gates and PVs.

Inspection operations are intended for gates and PV devices so this will have no impact.

Inspected ITSO cards (with TTTransactionType set to Inspected (0) will be validated according to the business rules.

FTA-FR001-9459-67129



of 12

G22 4.7.9 0006 messages Throughout the operations RSPS3002 indicates that 0006 messages should be generated when an IPE is amended

0006 messages are not supported as they only apply when a field in the fixed data group is amended.

According to ITSO Part 6, 0006 messages should only be generated when the fixed part of the IPE is modified.

0208 messages will contain details of any amendment to products so the absence of an 0006 message should have no impact and conforms to the ITSO spec.

G23 4.8 MU14 EEI Flag Validation RSPS3002 always sets the value of EEI flag to 0.

The EEI flag is current checked on Entry and Exit, together with the TTTransactionType field to control the business logic.

While there is this discrepancy then validation devices which conform with RSPS3002 will not be able to be mixed with IOP devices.

It is planned to remove any validation checks on the EEI flag for IDP3B to conform with RSPS3002. All entry/exit logic decisions will then be based solely on the value of TTTransactionType.

G24 4.8 MU20 update of ExpiryDateCurrent RSPS3002 states that ExpiryDateCurrent is calculated as the later of (ExpiryDateCurrent or Today’s date) plus the number of days defined by Passduration.

IOP devices always subtract 1 from the resulting expiry date so the pass expires actually at the end of the expiry date.

Misinterpretation of the specification by different suppliers will result in some devices interpreting the expiry dates differently and hence allowing an extra days validity in some case.

This is a general issue that could also affect other expiry dates calculations.

G25 5.3.4 0207 and 0208 messages RSPS3002 indicates that the all 0207 and 0208 messages should use message version 4.

To comply with technical note TN404 (see [4]) 0207 and 0208 for TYP24 products are generated using message version 5.

Operator backoffice systems will need to be able to accept and support Version 5 messages for TYP 24 products.

G26 5.4.2.3 Fulfilment Action and other action support

RSPS3002 states: “An ITSO POST device which supports action lists shall support an “Action To Take” type of “ Update Shell content: IPE Fulfillment Action” as specified in the ITSO specification version 2.1.4 in addition to all other mandatory “Action To Take” types. “

Fulfilment Actions are not currently supported and only actions which create ipe or amend fields in the IPE value group are supported.

The Create IPE action will need to be used for product creation until Fulfilment Actions are supported in IDP3B.

It is understood that Southern would like to use the TYP 22 AutoRenew enable/disable action (Action ID = 9). However, because this updates AutorenewQty1 which is part of the Fixed IPE this action is not supported.

FTA-FR001-9459-67129



of 12

G27 5.4.2.4 Fulfilment Action creation RSPS3002 states:

“An ITSO HOPS shall be capable creating action lists with an “Action To Take” type of “Update Shell:IPE Fulfillment Action”. The HOPS shall have the capability to group multiple “Detached” IPEs into a single action item to allow multiple products to be fulfilled on a shell. “

The TfL HOPS does not create fulfilment actions.

Without the capability to generate fulfilment actions, TfL would not be able to distribute their own products using the RSPS3002 defined fulfilment service. This is not currently an issue as TfL does not retail National rail ITSO products.

The Ecebs HOPS does provide the capability to create Fulfilment Actions for limited products using a Third Party Action and Hotlist interface.

G28 5.4.3.1 SET addressing RSPS3002 states that each station will be allocated one or more Set IDs to maps the POST to an NLC and POST type.

SET addressing is only supported down to NLC (Station Computer) level.

Not an issue as we are providing only Validation devices. IOP Retail devices will only provide “card read” functions for information – no product load or product validation to be supported on TfL TOMs and POMs.

Actionlists will go to all Cubic Validation devices associated with a location, including gates and PVs.

If different groups of devices need to be addressed separately then more than one station computer will be required per station and a Private SET assigned to each.

Where other HOPS devices are also installed in a station then these will be address independently by the third party HOPS.

G29 5.5.1 ServiceOperator RSPS3002 states this is derived from the RSP fares Data feed.

This is derived from POST base data Currently always set to “TFL “ for TfL managed POSTS.

Clarification only, as the TfL ServiceOperator identifier is not derived from the RJIS fares data feed.

G30 6 ITSO Fulfilment Service RSPS3002 contains a specification of a product fulfilment service include TIS and Flow Fulfilment Services.RSP ITSO Fulfilment Services are out of scope of the Cubic ITSO infrastructure.

TfL does not, and will not, operate an RSP fulfilment service, and will only receive Fulfilment Actions generated by third part Fulfilment Services.

Southern and other TOC operators will be responsible for operating any Fulfilment service and passing the resulting Fulfilment Action to the TfL HOPS. The TfL HOPS only needs to be capable of receiving Fulfilment Actions from the TOC Operators HOPS.

G31 B1.1 Multiple Zonal Schemes RSPS3002 discusses the zonal schemes outside London.

Currently onlyone zonal scheme is supported on each POST which must follow the same rules as London.

Only one set of Travelcard zones can be configured which means only out- boundary Travelcards to London can be supported.

Additional design of the base data configuration and functionality associated with zones will be required to support multiple zonal based schemes including London.

FTA-FR001-9459-67129



of 12

G32 Appendix D Implemenation of ITSO PlusBus RSPS3002 defines a solution for PluBus products.

PlusBus products will not be validated on IOP rail or bus devices.

Under IDP3A PlusBus products can be collected via Create IPE actions but only one product may be delivered at a time limiting its usefulness.

The collection of PlusBus products for IDP3A will be of limited use if there is more than one products involved.

Under IDP3B PlusBus products will be able to be collected using Fulfilment Actions allowing multiple products to be collected.

FTA-FR001-9459-67129