Procedural Knowledge Extraction from Industrial Troubleshooting Guides Using Vision Language Models

Guillermo Gil de Avalle, Laura Maruster, Christos Emmanouilidis
1/30/2026
cs.CVcs.AI

No confident code implementation found for this paper. 1 possible match can be shown below.

Abstract

Industrial troubleshooting guides encode diagnostic procedures in flowchart-like diagrams where spatial layout and technical language jointly convey meaning. To integrate this knowledge into operator support systems, which assist shop-floor personnel in diagnosing and resolving equipment issues, the information must first be extracted and structured for machine interpretation. However, when performed manually, this extraction is labor-intensive and error-prone. Vision Language Models offer potential to automate this process by jointly interpreting visual and textual meaning, yet their performance on such guides remains underexplored. This paper evaluates two VLMs on extracting structured knowledge, comparing two prompting strategies: standard instruction-guided versus an augmented approach that cues troubleshooting layout patterns. Results reveal model-specific trade-offs between layout sensitivity and semantic robustness, informing practical deployment decisions.

View on arXivView PDF

Code Implementations

No confident code match yet

We couldn't find an author-owned or strongly-evidenced community implementation for this paper. 1 weaker match is hidden by default — verify before relying on them.

No code implementations found yet.

Know of an implementation? Let us know in the comments below!

Similar Papers

Cite this paper

@article{avalle2026procedural,
  title  = {Procedural Knowledge Extraction from Industrial Troubleshooting Guides Using Vision Language Models},
  author = {Guillermo Gil de Avalle and Laura Maruster and Christos Emmanouilidis},
  year   = {2026},
  eprint = {2601.22754},
  archivePrefix = {arXiv},
  url    = {http://arxiv.org/abs/2601.22754v1}
}

Add a badge to your README

Shows whether official code is linked for this paper.

Code of Paper badge
[![Code of Paper](https://codeofpaper.com/badge/2601.22754.svg)](https://codeofpaper.com/paper/2601.22754)

Discussion