All case studies / Case study 02 / 12

Novaferr Industries

“Vulcan”, maintenance AI assistant

Vulcan: a maintenance assistant that knows every manual and every past repair

In short

Vulcan connects the technical documentation (manuals, SOPs, P&ID drawings, warranties) to live CMMS data (work orders, parts, failure codes, run-hours). At the machine, a technician asks by voice and gets a troubleshooting guide citing the exact manual page and the past work order. Everything runs on a server inside the plant: no cloud, no external API, and it keeps working offline.

Client
Novaferr Industries
Sector
Industrial manufacturing
Size
1,100 staff, 2 plants, 640 machines

The context

Novaferr runs 640 machines across two plants. The answers exist, but they are split in two: thousands of pages of manuals and SOPs in three languages on one side, nine years of work orders and technician notes in the CMMS on the other. At night, a technician facing a broken press calls the senior technician, or searches through PDFs while the line is stopped.

The challenge

  1. 01

    Manuals, P&ID drawings and SOPs are scattered PDFs, often scanned, in French, English and German.

  2. 02

    The best knowledge is in the CMMS history and free-text technician notes, which no one can search.

  3. 03

    On the shop floor, hands are busy, gloves are on and it is noisy: no time to type on a keyboard.

  4. 04

    A wrong answer is dangerous: every step must come from an official source, never be invented.

  5. 05

    Drawings, procedures and maintenance data are confidential, and the plant network is isolated: nothing may leave for the cloud.

Our approach

Manuals, SOPs, P&ID drawings and warranties are split into passages (with OCR for scans), turned into vector embeddings by a local embedding model and stored in PostgreSQL with pgvector. A read-only connector on the plant network syncs the CMMS (direct database read or scheduled export, no cloud service): work orders, parts used, failure codes, run-hours and technician notes. For each question, the agent queries both sources in parallel, filtered on the exact asset: the official repair steps, and how the same fault was fixed on this same machine. An open-source language model (Llama, Qwen or Mistral) running on a GPU server in the plant then writes a short guide citing the manual page and the work-order number, and can draft the new work order with its parts. Speech-to-text (Whisper) also runs locally: no question, document or data ever leaves the site, and the assistant keeps working without internet. Thumbs up / down and a weekly evaluation pipeline flag outdated manuals and parts lists.

The solution, step by step

  1. 01

    Manuals & SOPs, indexed

    Manuals, P&ID drawings, warranties and procedures become passages searchable by meaning.

  2. 02

    The CMMS, connected

    Past work orders, parts, failure codes and technician notes, synced on the plant network, read-only.

  3. 03

    A question at the machine

    The technician scans the QR code on the press and asks by voice.

  4. 04

    Two sources, one answer

    The official repair steps, and how the same fault was fixed on this exact asset.

  5. 05

    A guide and a work order

    A cited guide, then the work order drafted with its parts: all computed on-site, no cloud.

Results

What we deliver

  • Indexing pipeline for manuals, SOPs, P&ID drawings and warranties (multilingual, OCR)
  • Read-only connector to the CMMS / EAM on the plant network (SAP PM, Maximo, Odoo)
  • On-premise GPU server: local LLM, embeddings and speech-to-text, works offline
  • Hybrid retrieval: vector search + history of the exact asset
  • Mobile and voice app, with a QR code on each machine
  • Work-order drafting with parts and estimated time
  • Feedback loop, evaluation pipeline and audit log

Technologies

  • Python
  • LangGraph
  • PostgreSQL + pgvector
  • Local LLM (Ollama / vLLM)
  • Whisper (local)
  • React Native

Timeline

8 to 12 weeks

Team

1 AI engineer, 1 electromechanical maintenance engineer

A similar project? Let’s talk
Next case · Veltaro IndustriesA knowledge engine that connects Jira, Confluence and Teams

Illustrative cases: clients and figures are fictional, representative of the solutions we deliver.