search.noResults

search.searching

saml.title
dataCollection.invalidEmail
note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
PRODUCT NEWS


Water Company extraction.


This provides the user all abstractions undertaken perwater companywith all the data attributes andmapping of activities.


Log in user reports


This provides sight ofwho is logging inwithin the organisation and helps ensure supervisors andmanagers are checking the information provided and identifying any anomalies that need actions, such as field users requiring additional supportwith use of the App.


User tracker Status.


need to bemade, such as additional plant brought in. This can potentially save costs and carbon footprint of additional vehicles, alternative vehicles such as recyclers, or additional travel.


FAULTYHYDRANT REPORTING


Whilst the App brings a benefit to thewater company to identify if their hydrants are leaking, seized,missing cover etc, it also helps the contractor to knowif the hydrantworks before travelling to site andwasting a journey. The hydrant can then be flagged ‘not to use’.With thewater company using the system, they can then instigate a repair and have all the details required to allocate the task. Once the hydrant is repaired, the flag is removed, and the operatives can then knowthe hydrant is available for use again.


HISTORICDATA ANDACTIVITY


All the data captured is held in the cloud and easily retrieved at any time. Powered by eviFile’s highly secure data architecture, access to the extraction data can be controlled by the contractor’s support teamor the appropriate water company. This permissions flexibility ensures that anywater company can have free access to their hydrant data and the extractions being carried out by the NADCmembers. Power BI reporting also allows the contactor’s support teamto easily see the activity of their users in real time, ensuring that they know when the teams are logged in and using the App. The historic data also provides insight into faults associatedwith types of hydrants asmore extractions and hydrants are added to the App.


INTUITIVEUSER INTERFACE


The App is designed to be easy to use and a desktop Portal application provides clear and simple access fromthe office to identify all activity and track compliant operations. It also


50


helps in the proactivemanagement of standpipe allocations forwater usage reporting. Using the photos shows the actualmeter reads that are time and date stamped, should there be any issueswith other systems providing incorrect usage data and possibly incorrect charges.


The App can be used to ensure all abstractions are being logged andwhen they are undertaken,which hydrant andwhichwater company. Each abstraction is allocated a unique number as an identifier. The abstractions can be searched viawater company, hydrant number, serial number, operative or date/time. The information is reported through Power BI of the abstraction undertaken and can be exported very easily in pdf format through email or reports exported into excel.


There are a number of standard reports and client specific reports can be developed.


THE CURRENT SUITEOF REPORTS SHOWS:


Abstractions by field user.


This provides reporting by operativewithin any hierarchical process you define. For instance, a specific teamor contact can be set up so the supervisor ormanager can see only their teams, allowing ease of identification of activities and any performance reporting that is required.


Standpipe read reports.


This allows the user to abstract all information ofmeter reads fromthe individual standpipes to enable accuratemonthly returns to the standpipe licencing organisations, allowing correct charges ofwater use. Thiswill also identify stoppedmeters. Under the terms and conditions of the standpipe licence, stopped meters are not to be used. This therefore reduces the risk of a contractor’s non- compliancewith the licence.


| June 2021 | www.draintraderltd.com


This report allows easy sight of howmany users within the organisation are live and helps ensure the number of Apps purchased are not oversubscribed or any that are no longer being used.


Commenting on the App, Leah Lynas, FM Conway Co-ordinator said ‘The EviFile app has made every aspect of extractingwater easier not only for the crews but for us behind the scenes too. Itmakes collatingmeter reading datamore accurate and timely and the auditing of extractions quicker and simpler. It has enabled us to be able to add newWO hydrants which are found by the crews, report any faulty hydrants in a timelymanner and edit any existing ones, keeping any restricted access up to date. The app shows us an accurate description of every single extraction undertaken by the crews,with photographs taken and the data that has been inputted, which can then be sharedwith theWater Supplier on request. This in turn creates an excellentworking relationshipwith our suppliers.’


DEMONSTRATINGCOMPLIANCE


Using the App and the tools availablewith the systemcan demonstrate compliance to customers, clients and standpipe licensing. It can be used to ensure appropriate use and in turn prevent fines for unauthorised usage.With the potential fine for illegal use of £1000 per infringement, (althoughmany successful prosecutions bywater companies reach £7500 or greater), the App is a good investment to avoid these costs aswell as the reputational damage that can result frombeing fined.


There are also indirect cost and carbon savings fromreduced travel to hydrants andmore proactivemanagement of field operations.


Looking forward, once hydrant data is available across the UK, NADC expects to be able to offer the App to other hydrant users outside of the drainage sector. NADCwill continue towork withwater companies and Aquamto understand howthe App could provide them


Page 1  |  Page 2  |  Page 3  |  Page 4  |  Page 5  |  Page 6  |  Page 7  |  Page 8  |  Page 9  |  Page 10  |  Page 11  |  Page 12  |  Page 13  |  Page 14  |  Page 15  |  Page 16  |  Page 17  |  Page 18  |  Page 19  |  Page 20  |  Page 21  |  Page 22  |  Page 23  |  Page 24  |  Page 25  |  Page 26  |  Page 27  |  Page 28  |  Page 29  |  Page 30  |  Page 31  |  Page 32  |  Page 33  |  Page 34  |  Page 35  |  Page 36  |  Page 37  |  Page 38  |  Page 39  |  Page 40  |  Page 41  |  Page 42  |  Page 43  |  Page 44  |  Page 45  |  Page 46  |  Page 47  |  Page 48  |  Page 49  |  Page 50  |  Page 51  |  Page 52  |  Page 53  |  Page 54  |  Page 55  |  Page 56  |  Page 57  |  Page 58  |  Page 59  |  Page 60  |  Page 61  |  Page 62  |  Page 63  |  Page 64  |  Page 65  |  Page 66  |  Page 67  |  Page 68  |  Page 69  |  Page 70  |  Page 71  |  Page 72  |  Page 73  |  Page 74  |  Page 75  |  Page 76  |  Page 77  |  Page 78  |  Page 79  |  Page 80  |  Page 81  |  Page 82  |  Page 83  |  Page 84