AI Diagnosis Overview
Overview
Section titled “Overview”AI Diagnosis helps an operator investigate an alarm using the documentation delivered for that machine. The workflow retrieves relevant passages from manuals and service knowledge before an answer is written, so the result can present a likely cause, a remedy and links to the supporting PDF pages.
The diagnosis can include project context such as the fault code, current machine context and shared operator comments. It is an advisory aid: verify the cited source and follow the machine’s approved safety and service procedures before taking action.
How the diagnosis is grounded
Section titled “How the diagnosis is grounded”- Machine documents provide the searchable manuals, datasheets and service information.
- Fault context identifies the active error or PLC signal associated with the request.
- Retrieved passages ground the answer in relevant source text instead of relying on a general response.
- Source links open the supporting document at the cited page when that reference is available.
- Operator comments can preserve useful service experience across later diagnoses when shared notes are configured.
In a CONNECT-based deployment, the documents, search index and embeddings stay on the CONNECT backend. Only the required text excerpts are sent to the configured language model, and the model provider can be an EU-hosted service or a fully local OpenAI-compatible endpoint. The language-model API key does not need to reach the browser.
Quick Start
Section titled “Quick Start”- Open an alarm or diagnostic entry that offers Ask AI.
- Start the diagnosis and wait for the document search and response to complete.
- Read the proposed cause and remedy together with the current fault context.
- Open the listed source and verify the cited PDF page before following a recommendation.
- Add an operator comment when the deployment provides shared history and the note will help future service work.