How to capture AI-friendly Pipe Inspection Footage

How to capture AI-friendly Pipe Inspection Footage

As VAPAR’s CTO, it’s safe to say I’ve got a good familiarity with which inspection footage works well (and which doesn’t) for automated pipe inspections using artificial intelligence (AI).

Over the last few years, the capability of image recognition AI models have improved significantly, meaning automation is a universally serious time-saver for many organisations looking to optimise or streamline their image based assessments. 

Although accuracy of artificial intelligence has improved over this time, the results which AI models are able to produce can sometimes be limited by the characteristics of the inspection footage which they are fed. If Contractors are looking to maximise the results they can achieve for themselves and their clients using AI, there’s definitely some recommendations I’ve observed which should be followed.

As different AI vendors may have different ways of handling challenges and developing solutions. I’ve tried to cover each point with a generalist approach. Many of these challenges would also be true of a person trying to provide a condition assessment based on the footage alone.

Challenges and Limitations

Firstly, to get some better context around the recommendations, I’ll outline the main challenges and limitations of AI for automated CCTV coding I’ve observed during my time with VAPAR.

Granularity

Generally, pipe inspection standards will define a number of codes to be used which require granular detail which is not reliably achievable for operators or software without quantitative computer vision and tracking of camera telemetry.

Sizing of Features

Determining the size of features within millimeter accuracy is a challenging task for software and human operators alike.

‘Clock’ Positioning

Using 12 segments (named to align with clock references) can be challenging depending on the amount of panning, tilting and zooming that the operator undertakes during the inspection.

Defects that look similar

There is a level of subjectivity in many of the inspection codes that are expected in the reports. If the inspection footage does not clearly show the issue, it is very hard for anyone reviewing it to produce an accurate report.

Start & Finish Nodes

Start nodes may not always be present in footage captured by CCTV contractors. Furthermore, the type of maintenance hole used to access pipes can be difficult for AI to ascertain. Inspection footage is typically started from the centreline of the maintenance hole pointed directly down the barrel of the pipe to be inspected. These nodes are typically evident to the CCTV operator as they require entry to perform the inspection. The other tricky thing about nodes is they often contain defects we would code in pipes, but would not code in the node (such as debris or cracking). I think more needs to be done around the inspection and reporting of node defects.

Continuous Defects

It can be difficult to determine whether defects are discrete or continuous when a CCTV camera is moving through a pipe. This is due to the capture of the defects jumping in and out of frame during camera operation (sometimes we see panning and tilting without the camera stopping).

Multiple Assets in a Single Video

Where a CCTV camera travels through more than one asset, AI will need a way of identifying this distinction and handling the condition assessment of the assets separately. Otherwise the defects detected would all be assumed to be part of a single pipe asset which is incorrect. It can be tricky to know if the node between 2 pipes is expected or unexpected, especially in locations where GIS does not have a full picture of the underground assets.

Multiple inspection time frames captured in a Single Video 

Where a camera operator approaches an issue that needs to be immediately resolved (such as a blockage), they can stop the recording of the footage, clear the issue, and resume recording again. Where the halted inspection footage and completed inspection footage for the same asset are in a single video, AI needs a way of identifying this distinction between previous or ‘abandoned’ footage vs.‘completed’, and then overriding the abandoned condition assessment with that of the completed footage.

Shape or Dimensions Change

Where pipe shape or dimensions change, quantifying the extent of this change can be difficult to determine when using visual inspection footage alone.

Smooth operator 🎵 (Smooth camera operation)

Not so much of an issue in standard pan/tilt/zoom footage, but in “push rod” footage where the speed of the camera moving affects the quality of the footage, it can give AI and human reviewers alike a headache when trying to review.

Poor visibility

Cleaning while capturing inspection footage can “mystify” the vision. We recommend cleaning first and then carrying out the inspection as, firstly, the inspection video is a lot shorter, and secondly, the defects are a lot easier to see in the pipe after cleaning. (There are also things that are less in operators control such as splashing from water inside the pipe and steam that make footage hard to review.)

Recommendations

Now that I’ve outlined the core problems we’ve encountered with AI for automated CCTV coding, let’s cover some tips to ensure you’re capturing AI-friendly pipe inspection footage:

Standardisations 

There are a number of standard procedures that operators can apply to ensure inspection footage is optimised for use with AI pipe assessments. Areas where standardised procedure can be introduced to great effect are:

  • Standardising the asset information block at the start of footage capture (on-screen display)
  • Standardising the chainage on-screen display positioning.
  • Standardising a requirement for the CCTV camera head to be centered within the pipe and field of view also centered (to see equally the top and bottom of the pipe).

Restrictions

There are also a number of procedural restrictions which CCTV operators can observe in order to create footage optimised for AI-based pipe assessments. These include:

  • Restriction of cleaning during capture of inspection footage (i.e. CCTV capture during jetting, where the jetting head is visible throughout the footage and obscures the field of view) used for condition assessment.
  • Restriction on reversing significant distances through the pipe – this can cause offsets in the chainage measurement and also cause problems for the AI, which will duplicate the detection of defects and features.
  • Restriction on zooming whilst moving (either driving forward or panning), as this can make this camera movement difficult to track.
  • Restriction on stopping and starting the capture of footage within a single video, i.e. where cleaning is performed or the camera is moved without recording, the inspection should be taken in a single pass.

These recommendations are some of the main components we’ve identified that have the ability to impact the post processing of video files – either by AI or by an inspector.

Add a Comment

Your email address will not be published. Required fields are marked *