NGN already have the capability to electronically capture, draw and map assets in the field, albeit in a standalone system with limited capability (Collector). The current process for capturing and integrating data from the field is inefficient, error prone and there are issues with Collector that have impacted take-up of the app with the field crews. So much so, that some crews have reverted to recording information on paper.
As a result, NGN and 1Spatial have embarked on a project to develop a solution to improve user experience, increase data quality and streamline the data collection process to increase overall end-to-end data management productivity. The purpose of the Phase 2 project is to build upon the successful Proof of Concept (POC) which was delivered as Phase 1.
Testing in Phase 1 identified a number of new user requirements, as well as the need to refine some existing requirements.
These will be delivered as part of Phase 2 whilst the solution is developed from a simple proof of concept (TRL4) to a qualified production ready system (TRL8). Although Phase 2 will not mark the end of development for the full myDart project, it aims to provide NGN with a production ready application so that NGN can realise the benefit of this innovation as quickly as possible.
Objectives
This project will progress the POC Demonstrator developed in NIA_NGN_229 and release it into 1Spatials Function Test Environment at TRL8. Phase2 will focus on:
- An app designed for and by the end users themselves
- Enhanced, automated data validation, correction and creation
- Connected and disconnected data capture
- Integration with existing GIS platforms (e.g. Esri)
- Simple, easy to use application
- Integration with GNSS devices for accurate location
- 3D enabled (for future 3D requirements)
- Full DR4 recording (Pipe Geography & Plant) & reporting
- DR4 rules validation to ensure compliance
- Full MRD reporting and D30 tracking
- Recording and documenting dual services & multiple span information
- In built service digitisation rules ensuring compliance
- GD2 reporting ready
- 1 click approval / rejection
- Street & Project completion recording
- Capture of all on site documentation – RO/NRO, Test Certificates, Permits, Forms of
- Authority & Site Audits
- Revised data model to support integration with S4
- Enhanced spatial validation rules
- Full reporting suite
- Enable de-commissioning of Collector
- Remove the reliance of ArcGIS online for data returns
- Reduced back office QA/QC effort
Learnings
Outcomes
As indicated, the project has successfully delivered against the objectives of phase 2 and NGN are now in a position to plan the implementation of myDart into the network.
Outcomes:
Be commercially ready: Phase 2 has successfully delivered a commercially ready production ready application configured with spatial and non-spatial data validation rules.
An app designed for and by the end users themselves: Our users have been at the forefront of the design (UX and User Journeys) from the outset. Today we have an app that guides the user through the various process, allowing any user to access the app and complete their work with minimal guidance.
‘Right First Time’ field data capture: We’ve been successful in greatly reducing the number of free text data entry fields within the POC app, ensuring users can only enter appropriate information for the work being carried out. The app has been delivered with a number of conditionally driven fields to further aid the user journey and remove the possibility of entering incorrect information. Furthermore, the data within the app has been aligned to the master system to ensure data quality is at a premium and provide the steppingstone for future integration.
Automated data validation, correction and creation: Using spatial rules based technology we have successfully embedded spatial business rules within the application ensuring that ‘floating assets’ are a thing of the past and included the concept of ‘Snapping’ to ensure users can digitize successfully in the field and therefore delivering the time saving efficiency’s within the back office validation teams and reducing the number of re-visits.
Connected and disconnected data capture: The application is capable of capturing GIS information in areas of little or no phone signal. Any edits made whilst out of signal are captured and retained until the device regains signal at which point any stored edits are transmitted.
Simple, easy to use application: Today we have an app that guides the user through the various process, allowing any user to access the app and complete their work with minimal guidance. As a result of the Integration with HNSS devices for accurate location: The application holds functionality to allow the engineer to plot their location. The aim as part of future phases is to build on this foundation with a view to utilize this feature to further aid the user journey.
3D enabled (for future 3D requirements): The app is fully 3D enabled, although we are currently unable to exploit this function.
1 click approval / rejection: Following engineers’ submissions from the mobile application, NGN’s validation team receive ‘real time’ notification of a submission. On review, the validation team can conduct a ‘1 click’ approval / rejection of the submission. In future phases, the 1 click approval will automatically update NGN’s asset records and GIS applications. In addition, field engineers will be notified, via push notification, of any rejected submission, allowing for instant validation and correction where required.
DR4 and MRD Reporting: Phase 2 has delivered enhanced automated DR4 record capture, driven by the DR4 rules suite embedded in the mobile application, with full DR4 reporting suite available in the web application. Furthermore, phase 2 has delivered further enhancements to NGN’s MRD reporting, ensuring this is now available in ‘real time’.
Enable De-commission of Collector: Following successful UAT and business sign off, NGN will look to decommission their Collector application following implementation of myDart within the GIS eco system.
Lessons Learnt
Avoid lengthy delays between phases to ensure end user knowledge isn’t lost. Due to lengthy contract / legal discussions, we saw a 3-month delay in the project start date. This delay meant that the project team weren’t as close to the requirements as they would have been should the original start date been possible.
Despite developer review of the requirements, there were still some gaps in understanding. Therefore, moving forward, we will be looking to ensure we have a ‘face to face’ run through of all requirements to avoid any misunderstanding which could impact on delivery timelines.
