Post on 11-Mar-2018
CCTV in InfoNet(or InfoMaster)
Ann Pugh
Often data is provided as Plans, PDF and Excel
Build the Network
CCTV
Defects Table – video can be replayed
And defects reviewed & edited
Changed Defect and Structural Score
Corrected Survey Length
But only one survey lined up with pipe information
Split the surveys to match the asset information
Reviews Codes in CCTV defects table
605622 Inconsistent coding, 89.5m is a connection not a junction
586159
Start manhole digitised in wrong location so asset lengths
don’t match recorded CCTV lengths
Side Entry Pit Location confirmedwith Google Street View
586156
• Add defect for small tree roots
• JN at 24m is only a Connection – code changed
CCTV lines up with all assets
Calculate CCTV Scores from Defect Codes
Uses WSAA3 (or WSAA2)
Progress can be tracked via a dashboardWhat results am I getting back from my CCTV?
Asset Management
Update Pipes with “Current” CCTV information
Updates the Structural, Service and Likelihood Scores
View these on the map
View select CCTV defect codes
Understand in context – this Void is under a driveway
This could be on an intersection
Scheduling Action
Schedule a Pipe Repair
Each action is tied to a recorded defect
or CCTV
Means:
Justification of expense
and Transparency in Asset Management
process
Assign an urgency and planned date (and estimated cost)
Understand and Report on Budget
Review Future Estimated Spend to fix known (observed) issues
Understand and Report on Budget
Review Historic Actions – estimated costs and actual costs
Understand and Report on Budget
Summary of specific actions
X
Risk
Use Spatial Queries
Consequence of failure can be customised via SQL
queries. This example is a spatial query using
underlying GIS data.
InfoMaster provides Wizards to simplify this process.
Assign a consequence of failure based on road type
Queries can be customised by users, and different scenarios analysed
Risk Assessment, combine likelihood and consequence
Simplistic Exercise for those pipes with CCTV, but can be extrapolated to other pipes via use of cohorts
Lifetime Estimator: Defining cohorts
• Pipe Class is User Defined
• Populated via Query
CCTV Results can then be used to predict failure
More data will lead to better prediction
Remaining Useful life (and Likelihood) can be calculated
Can then undertake scenario analysis
• What if we have to replace every asset at end of estimated lifetime ?
What if all the “unknown” age concrete pipes only last 25 years ?
What if they last 40 years?
Or 60?
For more details:
• Innovyze Websitehttp://www.innovyze.com/products/infonet/
http://www.innovyze.com/products/infomaster/
• Local Client Services Manager
Questions ?