|
I use the rich data within the FWV to do my own data and analytics – all of the data is open for our organisation’s projects and organisations within my region, so I can take it offline and undertake analysis, such as creating a heat map to show pinch points in the future. It’s also really useful having access to all of the contextual information surrounding us – this data is formatted with rich metadata making it so simple for us to access and use.
Example: I have set-up an automated process that extracts FWV data every month and checks for any roading projects which are occurring in advance of my organisation’s projects in the same area. Because my organisation has underground utility assets it’s important that we get the opportunity to work on them before the road is resealed – thereby avoiding risk and cost for everyone. |
|
We use the FWV to review any works coming up in the next six months to a year and the impacts on the local community. With this information, we can discuss with the Project Managers how any community disruption can be mitigated and develop a detailed communication plan. It also allows us to consult with local community groups proactively. This means we are front-footing potential issues, and building a good relationship with the community – they can see we care about them and that we are organised and proactive which they appreciate.
Example: Reviewing the FWV, we saw that one street was going to have a lot of works on it for two months, which would be frustrating and impactful to residents. First we met with the project managers to understand why the works had been planned this way, then we met with the local community group and held a hui to discuss the works and the impact they were going to have. The works had been sequenced to be the most efficient as possible – all of the works being done in a two month period rather than separately over a year which would have cost the ratepayers more money. Armed with the information we needed from the project managers as to why this decision had been made, we could communicate this to the residents who ultimately agreed with our decision and appreciated the effort we had gone to explain this to them. |
|
I use the FWV to analyse the project data of all of my organisations projects. I like to know that they are on track and that they are not going to conflict with other projects either internally or externally to my organisation. The FWV provides me with a dashboard summary that is easy to understand and allows me to assess the risks to my programme – how many clash interfaces I have to manage and which other PMO’s I need to speak to. I also use it to contact project owners to discuss their projects and ensure their data is up to date and accurate. It is really handy having all of the forward works programmes in the same format – my organisation has forward works programmes in a variety of forms and software, but the FWV combines all of the information into the same format and is downloadable as a CSV so I can analyse it how I want to. My team can set-up notification rules so that we aware of all change.
|
|
I use the FWV to answer customer queries. We receive phone calls from members of the public regarding road works and how long they will be there for, so I can quickly look up the project in the FWV and am able to answer customer queries. I can also look-up historic projects which helps me explain to the resident the story of activity on their street.
Example: I recently had a resident phone to ask why the road outside of their house was being dug up once again when works looked to have been wrapping up. I was able to check the FWV and could see that there was a Three Waters project to repair both the storm and potable water pipes, but because storm and potable water cannot be repaired at the same time in case of contamination, I was able to explain this to the resident who appreciated an answer. |
|
We use the FWV to input our events and check for any clashes with projects. We receive up to 300 event requests a year, and without the FWV it would be almost impossible to know if an event will clash with road works or a construction project. We input planned event routes in advance, and this means that we are not competing for space with other projects, and enables us to give Event Organisers a quick answer on whether their event can go ahead or not. We also input the traffic impacts associated with the event into the FWV which gives the Comms Team early notification as to what will be happening in the area and what they need to communicate out to the local community. The FWV allows us to automatically upload our events and because we deal with so many events throughout the year this saves us significant time and effort – making coordination simple.
Example: We put the city marathon route into the FWV a few years in advance, this way all organisations wanting to do any work in the area know exactly the dates, times and routes of the marathon and are able to schedule their works accordingly. |
|
My biggest headache is understanding all the work that is proposed across the network I am responsible for. There are dozens of stakeholders who could be doing work at any time. The FWV does the hard work of collating all my stakeholders’ programmes into one repository where I can view it, use it in meetings and ask others in my team to do analysis on the impacts. With this data I am better placed to advocate for my customers – making sure their journey is well managed and disruption is kept to a minimum.
Example: The FWV notified me that a major rehabilitation project was planned for a strategic route. I was able to notify other contractors that this would be an opportunity to undertake other work at the same time – taking advantage of the traffic management to get more work done in the same timeframe. Using the FWV also gave me confidence that my stakeholders know that this work is occurring – including my comms team colleagues who do the important work of notifying the public. |
|
Being responsible for a large asset network it is critically important for me to understand how the renewals and maintenance programme is affected by the work of others. The FWV allows me to deconflict my programme and identify major projects with which I need to coordinate. The FWV also helps me understand who is working close to my assets. My team uses the notification features to alert them when there is work occurring close to critical assets on my network. I also publish my asset network data to the viewer – this provides a simple reference for other design engineers and work contractors – knowing where my assets are helps protect my network allowing others to work confidently and productively.
Example: Every month my team uses the FWV to extract a list of projects which overlap with assets on my network that are due for renewal in the next three years. This alerts me to potential opportunities to accelerate these renewals – by either working with other projects or by expediting my renewal activities so my asset is resilient when other work is delivered close by. |
|
It’s a requirement from my road controlling authority (RCA) to input all work impacts into the FWV, so I use it to input the traffic impacts associated with my project. This allows my RCA to review the project well before I submit my traffic management plan (TMP), and provide pre-approval in advance of the works happening. This means there’s less TMP revisions, saving me time and money, and means that communications can go out to the public in a timely manner so they’re aware of any impact that the planned work will have on them.
|
|
I use the FWV to gather enough data around projects happening in the area so that I can schedule my own projects efficiently, logically and confidently. I know which major programmes are happening at the same time as my projects and I also benefit from the rich contextual information such as where underground services are, or protected trees – it means I can take these into account when planning my project. I also use the FWV to run reports on existing projects to see when they are scheduled to begin and end, and ensure my Project Managers are keeping the information up to date so it benefits all of the FWV users. By using the FWV I am confident that other stakeholders can see my projects and know who to speak to if they need to have coordination discussions. The notification feature alerts me when projects change and when I need to take action so my projects are delivered more efficiently.
|
|
The FWV is our go-to system for a view of what’s happening in the city. It allows us to schedule our works in around other projects and avoid clashes. Sometimes we’ve managed to join projects with other organisations and taken advantage of the existing traffic management plan, saving both of our organisations money and time. Being able to use the FWV to scope the project during the tender stage allows us to better anticipate impacts and coordinate risks. We know what utility services we’ll be working around, how we’ll impact parking and what other projects are happening at the same time.
Example: During the project establishment phase for a large infrastructure project, we regularly check the viewer for other projects that are planned to happen nearby. Keeping our data up-to-date in the viewer allows our client and our community engagement team to know what’s happening and when things change. Before the project even started the local electricity network provider contacted us, having identified that our work was close to key assets, asking to coordinate with them so they could upgrade their network. The client was happy because this meant less disruption to the community by getting all the work done at the same time. |
|
I use the FWV to mitigate risk. I use the contextual data provided to ensure that I know enough about the area so that I can comfortably plan my project, knowing all of the assets around me. I also use it to keep an eye on my projects, it’s handy seeing them spatially mapped out in context with the surrounding area and other projects nearby – our current system doesn’t do this. The notifications feature is very useful, allowing me to customise which alerts are important to me. Personally, I use the notification system to alert me to when my projects are due to finish, and when there is activity surrounding my project – such as a new clash or opportunity. The contextual data allows me to see things like whether my project is on an important public transport corridor, is close to heritage structures, or an earthquake prone building. I also use the FWV to indicate the traffic impacts caused by my project – this ensures that I get pre-approval to start the project from the Road Controlling Authority.
|
|
I get access to a public website of data which contains the most useful information from the FWV. I can quickly understand what work is planned in my community board area - so that if anyone from the community ask me questions, I have answers readily available. It also means that our internal teams are talking to each other more – previously they were quite siloed, which led to miscommunication and project clashes, infuriating me and the community. But now because all of the teams are loading their programmes to the FWV and can see what each other are doing, their projects may intersect, but they’ve sequenced them sufficiently that they don’t clash, and sometimes they even work together to share resources when it allows, saving us money and time. Being able to see projects proposed as part of the Long Term Plan is also great – I can see how it fits in with other development work in the region.
Example: I received a number of complaints from residents about a disruptive intersection upgrade which was causing delay and frustration for local businesses. Using the FWV I could see when the project was due for completion – so I could notify the community. I also saw that other work had been coordinated for the same time – fixing stormwater and laying new utility services. I let the community know that we had taken this opportunity to save disruption and costs in the future. |
|
I use the FWV to ensure that my vertical developments aren’t clashing with any horizontal projects. Access to my developments is important and so if a road is going to be closed or it’s being dug up when I am about to build something, it’s important I know that in advance so I can plan around it. It also enables me to share my work so that the Council know what my plans are and are better informed for issuing consents. It’s handy being able to view the contextual layers too, so I know what I am dealing with in terms of things like earthquake prone buildings, public transport routes I may potentially be blocking off when building my development, and what assets are underground in the area that I may be at risk of damaging. I also know that my architect and structural design engineers rely on the FWV to provide them with a good understanding of development risks including other parties we have to coordinate with.
Example: Using the FWV I saw that there was a waste water renewal project happening outside my new property that was being built. I knew that this was likely to cause disruption and impede access to my site – so I called the Project Manager and got agreement that his sequence of work would be modified to allow improved access for my property. I also noticed that there is a number of protected trees and an earthquake prone building across the street – so I added these to my risk register for my Project Manager to manage. |
