<!--[if !mso]><style>v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);} w\:* {behavior:url(#default#VML);} .shape {behavior:url(#default#VML);} </style><![endif]--><!--[if gte mso 9]><xml> <o:shapedefaults v:ext="edit" spidmax="1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext="edit"> <o:idmap v:ext="edit" data="1" /> </o:shapelayout></xml><![endif]-->
Hi all
Apologies for the delay in responding. Rest assured however that in the meantime Tom has been following up on the various strands of work that have been identified and will send you an email about that soon!
I think it's easiest if I just respond to the points you've raised in the order you raised them but I'll first make a few general comments about where I see things sitting from our perspective.
As I see it much of the frustration and last-minute nature of things thus far, which has not been ideal for either of us, comes down to two (related) things.
1. Trying to meet EECA milestones in order to secure your central govt funding and
2. Trying to line things up with Council budgeting and decision making timelines, which are largely set in legislation so not able to be moved, as well as processes which include public consultation phases which must be carried out in good faith and with no pre-determination of outcome.
On the first matter I reiterate that had we been included in the development of your EECA bid (or even been told about it) then we could have ensured realistic alignment with Council's statutory decision making timeline. Every other private sector entity we've worked with on EECA bids has included us as a partner and shared all information accordingly. We only knew about your bid because you asked Justin for a letter of support on the day it was due and he rang me for advice. This is despite your ability to deliver being heavily dependent on Council providing significant public space within the CBD which is why I remain surprised that you didn't include us in its development. I can see how you might think allowing "six months for Council process on a project with a signed letter of support from the Council" is adequate but budgeting decisions for the annual plan begin far in advance of that and had we been consulted I could've told you that! And nothing in that letter of support committed us to a six month timeframe - and nor could it. I agree that we need to not dwell on the past but this point seems to keep being glossed over and from our perspective it's at the heart of most of our challenges as a Council to meet your requests. And again we have had no input into the development of your milestones with EECA, which have now been agreed, despite numerous offers to participate in those discussions so that EECA doesn't put unrealistic expectations on you to deliver in timeframes that simply aren't possible.
On the second matter - because the scale of your ambitions is such that it can’t be met out of existing budgets it has to go through our annual plan process for Councillor approval. As I've said before - had we known the scale of your intentions a year ago when Council passed the Low Carbon Capital Plan we could have incorporated the costs of meeting that scale into the budget at that point but hindsight is 20:20. We are doing all we can to facilitate your requests through those processes but as I'm sure you appreciate we are not the only Council officers trying to progress projects that we deem important and add value to the City. And with our Mayor taking a very firm position on limiting rates increases we are working within very tight fiscal constraints. And as I fed back to you our Councillors definitely see a Council commitment to Mevo of 27 car parks in the first year to be a significant commitment.
In response to your specific comments:
First off notwithstanding my earlier comments thanks for sending through the EECA milestones. That’s really helpful. Just as a matter of interests when exactly were these agreed to and signed off? Also I'm not
entirely clear what you mean by this not being the schedule you're working to - does this mean 30 September is actually 31 July in terms of what you're working to in reality?
If that's the case then the only sites we could get approved by the end of July are the 21 sites we've already consulted on for you. We can get the traffic resolutions done for the first ten on 14 September so that
would meet the 30 September milestone. In terms of the 31st October milestone, the Traffic Resolutions for these would also need to be lodged by 30
June (and that's TRs completed not just sites selected) in order to go through on September 14. For the 30 January milestone these would need to go through in the November 16 round (TRs lodged August 1). For the
31 October and 30 January sites these would also need to be outside of the CBD metered parking in order to stay within the budget and agreed 3 year cap on CBD car park allocation agreed to by Council.
In terms of the discussion we had on the 31st – on a slightly minor point my understanding was we put the TRs on hold not that we had pulled them entirely so in terms of the status of those particular TRs we'll just need to square that off process wise. But
yes I can confirm we do not consider that we are legally obligated to offer them to any other providers. Obviously this doesn't mean we can't offer them to other providers but you are correct that we are not obligated to do so. Just FYI we will most likely
offer the non-CBD car parks that you've said you don't want to other car share providers as we've spent quite a bit of resource on the TR process so it would be a shame if they went nowhere. This won’t impact the 30 CBD parks 3-year cap (and is well below
the 70 parks across the rest of the City 3-year cap) so won’t affect your other requests.
In terms of your wish to get cars down in June versus November - we are limited in how much we can truncate the TR process. There is a lot of work that goes in behind the scenes and Tom can run through that process with you this afternoon. We've looked to where
we can truncate timeframes but at best we're talking a matter of weeks not months. Also bear in mind that our traffic team deals with large numbers of traffic resolutions and every applicant sees their particular project as being critically important and in
need of prioritisation or a dedicated process (and the September 14 meeting is actually already a special process). In saying that they’ve been really great lately in accommodating last minute changes to committee
papers etc which has been really helpful.
I would strongly reject your assertion that you have had no fit for purpose car parks offered to you by the Council. I was under the impression that the six waterfront sites we've given you were operating well. If not then please let me know as we have plenty of demand for waterfront access and I certainly don't want to keep you locked into car parks that aren't working. In terms of the on-street parks as far as I'm aware 12 of the 21 traffic resolutions that you asked to be put on hold are for parks that are shovel ready and we could send to the next committee meeting and get started on right away.
And while I could list all the admirable qualities I think we've displayed as well I actually don't think it's a problem, or even unusual, that we haven't always agreed on everything. There's been mutual frustration on both sides from time to time - it hasn't been all sweetness and light. But nor should it be. You're behaving exactly as I would expect a small start-up business trying to extract the best deal possible out of Council to behave, and in turn I hope you would appreciate that we have many competing demands to balance both within our team and as a Council and are reacting accordingly. Demands for public space are constant right across Council and we are mere custodians of that space on behalf of the City and I personally take that responsibility very seriously. That is why I have been grateful that you have up till now been prepared to work with us to find spaces that meet that mutual balance. "Fit for purpose" cannot mean you simply get every site you ask for without us questioning the impact on other users on or near that site and the cost to Council of doing so.
And yes you are a small business, as are all the car share providers that we are working with, and we want to reduce the costs to you as much as possible. But please remember that we are also a very small team with far fewer resources than people assume. We have committed a disproportionate amount of those resources (human, financial, and personal capital) on this venture because we believe in it so strongly and we will continue to do so. As an example we were happy to cover the $17k cost to get the last round of TRs drafted but that took quite a chunk out of what's left of my budget and so when you say you now no longer want those sites it makes it much harder for me to justify covering the cost of the next round of TRs (which again will have to be contracted out in order to meet the June 30 deadline).
I'd be interested to know when you consulted on your budget with WE and how those discussions played out? I assume it was before your EECA application was lodged so you could include those costs? It would be really helpful from our perspective to have more information about those discussions. Bear in mind we have no idea where WEs 400V cables are so we were/are relying on you to factor the requisite infrastructure requirements into your due diligence as we have done with all our EV partners. If you have a map of where they are that would be enormously helpful! And I totally understand trenching adds to your costs but that also needs to be viewed against of the cost of getting new TRs drafted by 30 June for new sites vs taking the ones we've already consulted on for you and paid for.
I can see that I have more emails from you guys so maybe some of this stuff has been covered off already! In any case we can talk this afternoon but hopefully this helps set the context from our perspective.
M.
Sent from my iPad
Moana Mackey Strategy Policy and Research Wellington City Council | Me Heke ki
Pōneke
|
|
From: Erik Zydervelt [mailto:[email address]]
Sent: Tuesday, 13 June 2017 1:55 p.m.
To: Moana Mackey
Cc: Tom Pettit; Finn Lawrence
Subject: Re: New Mevo Traffic Resolutions
Hi Tom and Moana
Thanks for the notes.
Please see attached a summary of our EECA Milestones. It's worth noting that we deliberately drafted these with EECA to be two months behind schedule and should be considered as such, not the timeframe we are working towards. Finn will follow up with the locations that have been sent to WE for review.
Let's look at how to move this faster for a mutual success story.
A quick point requiring clarity: on the evening of the 31st, Moana and I have discussed pulling all traffic resolutions and the legal checks have already been made regarding WCC not having to offer these locations to other providers. Moana, if you can confirm this I would be most appreciative.
As for not being able to get cars down until potentially November, we need to look at how this can be moved forward significantly. This is a partnership and we had aimed to find suitable locations by June.
We need to be crystal clear on this point: we have been pragmatic, responsive, thorough, and communicative, and the result we have from the City Council is zero fit-for-purpose parking spaces after six months. We're a small business and we don't have the resources to cover long lead times on this.
We discussed a process in January that wasn't followed, and we've ended up with a jumble of parks near old hardware, none of which are near enough to 400V cabling to keep within the budget that we consulted on with WE. We have $8-12k per site allowed for a grid connection, and with trenching sitting at $500-$1000 / meter, the result of moving every parking space is a blowout of over $250k, and one site where we can't get power at all.
We want to be constructive and see this project as a great success for the residents of Wellington, the City Council, central government and Mevo, We do not want to dig into what went wrong with the last TRs; having every site moved on us and less than two working days to approve them isn't a recipe for success. Even if Mevo had been doing 100% of the consultation with WE (which doesn't seem like what WCC wants, based on the above email), to think that we could have consulted on 7 sites (that had no room for discussion anyway) in that timeframe is unreasonable, and we made comment of this at the time.
It is worth noting that every month of delay costs Mevo roughly $30k, plus additional losses in revenue. We were planning to have the first vehicles down in June which allowed 6 months for council process on a project with a signed letter of support from the Council. As a project backed by EECA's Low Emission Vehicles Contestable Fund, this is taxpayer money that's going to waste.
As I am aware, TRs require an 18 day consultation period. So, following the timeline we agreed on two weeks ago at our meeting of WCC and Mevo completing site selection by the 30th of this month, I can see realistically an end of July approval is pragmatic and appropriate with a couple of weeks being allowed for contractors if we book the job in today conditional on the TR going through.
What steps do we need to make this happen before Septembers? In what way can we escalate this?
We simply would like to celebrate our mutual success and need your support to do so.
Cheers
Erik
ᐧ
Erik Zydervelt
Mevo Co-founder // CEO
+64 20 4059 1485 | [email address] | www.mevo.co.nz | LinkedIn | Skype: erikzydervelt |
CAUTION: This email message and attachments are confidential to Mevo Limited and may be subject to legal privilege or copyright. If you have received this email in error, please advise the sender immediately and destroy the message and any attachments. If you are not the intended recipient you are notified that any use, distribution, amendment, copying or any action taken or omitted to be taken in reliance of this message or attachments is strictly prohibited.
ᐧ
On Mon, Jun 12, 2017 at 4:58 PM, Moana Mackey <[email address]> wrote:
Also just following up on the milestones that you guys have agreed to and signed off with EECA? Would help us if we could get a copy of those.
Moana Mackey Strategy Policy and Research Wellington City Council | Me Heke ki Pōneke
|
|
From: Tom
Pettit
Sent: Monday, 12 June 2017 3:46 p.m.
To: 'Erik Zydervelt'; Moana Mackey
Cc: Finn Lawrence
Subject: RE: New Mevo Traffic Resolutions
Hi guys,
Please provide us with the areas you have sent to WE?
They had indicated to us that they would need roughly 1km around any given point to work with, but keen to see what has eventuated as a workable process from their end.
To reconfirm the process will have to be WE indicates what is available within a very large area (again 1km radius is appropriate) and WCC will then select options that we believe fit well with our parking requirements in that area. We have to have flexibility to select parking bays that suit WCC from what WE makes available.
If you new traffic resolutions must be authored and consulted on the earliest we can promise a vote is September 14th, with signage and painting at least a month or two after.
How many of the existing traffic resolutions are you planning on taking up? Four of the 7 sites had adequate electricity for 4 3kw EV chargers as you have on the waterfront.
In the instance you decline to take up a significant portion of those resolutions I’ll have to investigate whether we need to offer them to other car sharing providers given the time and money invested in preparing and consulting on those TRs.
Cheers,
Tom
Tom Pettit Wellington City Council P 04.803.8697
| M 021.227.8697 |
|
From: Erik
Zydervelt [mailto:[email address]]
Sent: Monday, 12 June 2017 2:17 p.m.
To: Moana Mackey; Tom Pettit
Cc: Finn Lawrence
Subject: Re: New Mevo Traffic Resolutions
Just cc'ing Finn in :)
ᐧ
Erik Zydervelt
Mevo Co-founder // CEO
+64 20 4059 1485 | [email address] | www.mevo.co.nz | LinkedIn | Skype: erikzydervelt |
CAUTION: This email message and attachments are confidential to Mevo Limited and may be subject to legal privilege or copyright. If you have received this email in error, please advise the sender immediately and destroy the message and any attachments. If you are not the intended recipient you are notified that any use, distribution, amendment, copying or any action taken or omitted to be taken in reliance of this message or attachments is strictly prohibited.
ᐧ
On Mon, Jun 12, 2017 at 2:15 PM, Erik Zydervelt <[email address]> wrote:
Hi Moana and Tom
I hope you both had a great weekend and welcome back Tom.
As a quick update for you; we have sent city block scale areas through to Wellington Electric to review and let us know where in these areas they have the capacity for charging stations and will keep the pedestrian disturbance and civil works costs as low as possible.
We hope to have a selection of locations for each area by the end of the week for WCC to review, input on, select from and agree to move into the new Traffic Resolutions process by the end of the month as discussed.
In parallel, can we begin setting a timeline on moving the council approval of these new traffic resolutions as close as possible to the end of this month? I understand we will need to allow operational time for consultation which I believe is 18 days following our current end of the month timeline. Could this be signed off so we can begin works by, say the mid-July? This would allow all of us to not to experience any further significant delays from our existing timelines and have the project back on track.
Kind regards
Erik Zydervelt
Mevo Co-founder // CEO
+64 20 4059 1485 | [email address] | www.mevo.co.nz | LinkedIn | Skype: erikzydervelt |
CAUTION: This email message and attachments are confidential to Mevo Limited and may be subject to legal privilege or copyright. If you have received this email in error, please advise the sender immediately and destroy the message and any attachments. If you are not the intended recipient you are notified that any use, distribution, amendment, copying or any action taken or omitted to be taken in reliance of this message or attachments is strictly prohibited.
ᐧ
ᐧ
ᐧ