Integrated Fares
Project Control Group Meeting
Wednesday 19th August 2015
Family offering – AT Metro recommendation
School bus routes impacted by zones
Technical work-stream update
Ferry integration update
Schedule and budget status
2
Decisions required
1. Family offering- Select preferred technical
option/proposition
2. School bus trips – select option to mitigate 1 stage to 2
zone fare impacted passengers
3
Family offering - proposition
•
Proposition – in our public consultation, the family offering was described as:
Family weekender
2 children free with every AT HOP paying adult on weekends and public holidays
•
Proposition very positively received during the consultation
•
Important we don’t refer to this as a “pass” as this has connotations that you have
to purchase something
•
What is a “AT HOP paying adult”
•
Does this apply to Super Gold passengers (Grandad travelling with grand-
children on weekends)?
•
Does this apply to Students (uni student with brother/sister)?
•
Does this apply to a Day Pass or Month Pass user?
•
Does this apply to a cash ticket purchaser?
•
No specific development is being done by Thales for a family offering, so we must
utilise existing (or upcoming) system capabilities
4
Family offering – options
• 2 potential technical approaches have been identified:
# Option
Description
Positive
Negative
1
Children off
Children travel with an adult
Revenue loss limited to
No origin destination data
system
-
Bus – adult tags on,
accompanied children
Operational issues around rail
child gets “count key”
Children supervised
stations
-
Rail – adult goes
Consistent with consultation
Potential dwell time impact on bus
through gate, kids go
messaging
(count key)
around
Lost patronage
No way to monitor capacity,
utilisation
No ability to measure accurately
Impacts families with more than 2
children (lower socio-economic)
2
Kids free with
Children must have an AT
Encourages AT HOP uptake
Potential additional revenue loss
AT HOP
HOP card, with child profile
May encourage further PT usage
(unaccompanied children)
loaded (registered) – then
during paid periods
Different proposition than consulted
can use PT
Supports Innnovate Project in south
on
Auckland
Families have to buy HOP card and
Full OD & patronage data
register before can benefit
No additional overhead for bus
May encourages unsupervised
operators or rail network
children to travel around Auckland
Potential to get corporate
(BUT children will be registered)
sponsorship to fund
Significant uptake could impact
No additional HOP infrastructure
network capacity
required
•
DECISION – Select preferred option.
5
School bus trips (1)
•
Based on our zonal map there are a number of school bus routes where school
students will have increases from 1 stage to 2 zone fares
•
Significant feedback was received during the public consultation by impacted schools
(particularly North Shore schools)
•
The impacted schools are from 3 zonal boundaries:
•
Lower North Shore / Upper North Shore
•
Isthmus / Manukau North
•
Isthmus / Waitakere
•
The top schools impacted (by numbers of impacted students):
6
School bus trips (2)
• 5 options have been identified by the Project Team on how we address the
school bus trip issue:
1.
Apply standard fares and make no changes
2.
Align boundaries to school zones (only for school bus trips)
3.
Where dedicated school bus stops in schools (school bus bay) – make
these in 2 zones
4.
Tweak zone overlaps for all services (school and commercial)
5.
Apply a separate fare structure for schools
7
School bus trips (3)
• See below our analysis of the pros and cons of each of the options:
Option
Simplicity
Dev / config
$$$$
Public
Comment
impact
Do nothing -
Consistent with public
Standard fares
consultation
Align to school
Inconsistent with urban services
zones
Complex messaging
On-going data maintenance
School bus bay in
Only partial mitigation – not all
overlap
schools have these
Tweak overlap for
Big revenue impact
all services
Separate fare
Inconsistent with urban services
structure (stages)
On-going data maintenance
Complex messaging
•
DECISION – Select preferred option.
8
Technical work-stream update
•
Technical design
o
Draft technical design documents from TCS and OSL have now been reviewed
and provided back to Thales.
•
Thales have yet to respond with regards to the TCS release 7.1, including:
o
Changes to the BDC to support display of zones for each stop
o
TCS changes to support paper ticket apportionment
•
Thales have had initial discussions on an option to release customer facing changes
on top of the existing VS6.4 release to mitigate the risk of two major releases VS7.0
and VS7.1 over a short timeframe
•
The next Thales/OSL Teleconference is scheduled for August 20 to review the updated
OSL Apportionment Whitepaper
•
The next TCS workshop which Evelyne Furui will attend will be held from September
21 through to September 25, it will be primarily focused on the proposed EOD design
•
Work has commenced on building four prototypes to validate one of the proposed
Ferry integration options and also the intended product offerings
•
An initial workshop was held to consider options for the proposed Web changes
•
School Bus technical session held to review technical options available
9
Ferry integration update
• Technical investigation of ferry options ongoing.
• 3 technical options identified:
1. Water-based zones
2. Utilise CityLink development by Thales
3. Build originating and terminating zone into Ferry
Monthly Pass products
•
Will be adding to agenda for Evelyne visit in September
•
Project Team pushing hard to ensure a solution is found
10
Schedule and Budget status
SCHEDULE
BUDGET
Projected Go-live 6 June 2016
Tracking ON-BUDGET, but 15/16 fiscal
•
Release 7.0 (zone lite ticketing) on-track
allocation not aligned
for delivery by Thales 31 October
•
NZTA funding approval given in July
•
Release 7.1 estimated delivery by
•
$1M spent 14/15 fiscal against budget of
Thales (for commencement of UAT) 31
$2M due to Thales costs moving to
Mar 2016.
current fiscal
•
Thales have an alternate plan for
•
$5M provisioned this fiscal – need $1M
Release 7 that is under review
carry-over from last fiscal to ensure $6M
available
•
Opex - $1.35M in current fiscal while
approved budget requires $1.9M ($550K
gap)
•
Limited ability to mitigate with 3 main
costs being operator training, contact
centre and marketing/comms