VIPRATECH LABS

Maintenance Log and SOP Assistant

A shop-floor assistant that answers technicians' questions from breakdown history, OEM manuals and SOPs, in Hindi or English, with the source page or work order behind every answer.

Industry:
Manufacturing

Who it is for

  • Maintenance Head
  • TPM Coordinator
  • Shift Maintenance Engineer
  • Plant Head

The problem

When a press loses hydraulic pressure in the middle of the night shift, the technician on duty needs to know what fixed it last time. That answer usually sits in a handwritten breakdown register, a free-text SAP PM notification or a senior colleague's memory.

History locked in registers

Breakdown logs, PM checklists and why-why analyses are handwritten or typed as free text, so nobody can search them by machine or symptom.

Manuals nobody reads at the machine

OEM manuals for CNCs, presses, compressors and moulding machines are long, in English, and kept in a cupboard or a shared drive.

Knowledge leaving with people

Senior technicians who know each machine's quirks retire or move on, and their experience is not written down.

Repeat breakdowns

Without quick access to past root causes, the same fault gets a temporary fix again and again and MTTR stays high.

What we build

We digitise your maintenance history and build an assistant on top of it. Handwritten registers and free-text work orders become structured records of machine, symptom, alarm code, root cause, action and spares used. OEM manuals, SOPs and one-point lessons are indexed by machine. A technician asks by typing or speaking, in Hindi, Hinglish or English, on a phone or shop-floor tablet. The assistant answers only from your approved documents and history, cites the page or work order behind each statement, and says clearly when it finds nothing. Safety steps are quoted word for word from the approved SOP.

  • Digitises handwritten breakdown registers and PM checklists into structured records
  • Indexes OEM manuals, SOPs, one-point lessons and alarm-code tables by machine
  • Answers in Hindi, Hinglish or English by text or voice, citing the source page or work order
  • Finds similar past breakdowns by machine, symptom and alarm code, with root cause and spares used
  • Quotes lockout-tagout and other safety steps verbatim from the current SOP revision
  • Drafts work order closure notes and one-point lessons for engineer approval

How it works

  1. 01Digitise historyBreakdown registers, PM sheets and CMMS exports are read and converted into structured records.
  2. 02Index documentsManuals, SOPs and OPLs are split into sections, tagged by machine and revision, and indexed.
  3. 03Technician asksA technician asks by voice or text, naming the machine or scanning its QR tag.
  4. 04Retrieve and check sourcesThe assistant retrieves matching history and document sections and checks whether they answer the question.
  5. 05Answer or say not foundIt answers with citations, or states that the sources do not cover the question and suggests whom to call.
  6. 06Engineer approves new knowledgeClosure notes and OPLs drafted from the fix go to the maintenance engineer for approval before indexing.
Maintenance Log and SOP Assistant: workflow diagram
Open full size

Architecture

  1. Knowledge capture
    • Handwritten register and PM sheet digitiser
    • CMMS or SAP PM notification export
    • Manual, SOP and OPL loader with revision tags
  2. Index and retrieval
    • Machine-tagged document index
    • Similar-breakdown search by symptom and alarm code
  3. Assistant
    • LLM answer generator restricted to retrieved sources
    • Speech-to-text and text-to-speech for Hindi and English
    • Not-found and safety-quote rules
  4. Review
    • Engineer approval queue for logs and OPLs
    • Answer feedback from technicians
  5. Access and audit
    • Role-based access by plant and department
    • Question and answer log for review
Maintenance Log and SOP Assistant: architecture diagram
Open full size

Inputs and outputs

Inputs

  • Handwritten breakdown registers and PM checklists
  • CMMS or SAP PM notifications and work orders
  • OEM manuals, alarm-code lists and spare-part catalogues
  • SOPs, one-point lessons and why-why analyses
  • Machine list with tags and locations

Outputs

  • Structured breakdown history by machine, symptom and root cause
  • Cited answers to technicians' questions
  • Similar-incident lists with actions taken and spares used
  • Draft closure notes and one-point lessons for approval
  • Log of unanswered questions that shows documentation gaps

Where people stay in control

Technicians decide what to do at the machine; the assistant only points to what the documents and history say. Maintenance engineers approve digitised records, closure notes and new OPLs before they enter the knowledge base.

Integrations

  • SAP PM, Maximo or another CMMS
  • Shared drives or DMS holding manuals and SOPs
  • Shop-floor tablets or Android phones
  • Microsoft Teams or WhatsApp for access
  • Single sign-on for role-based access

Guardrails

  • Answers only from indexed, approved sources, with citations
  • Explicit not-found response instead of a guess
  • Safety and lockout-tagout steps quoted verbatim from the current SOP
  • Superseded SOP revisions excluded from answers
  • Question logs reviewed for wrong or unsafe answers

Compliance notes

  • Answering only from the current approved revision of each SOP supports document control expectations under ISO 9001.
  • The assistant does not replace your lockout-tagout procedure or permit-to-work system.

A typical pilot

Duration: 4 weeks

One machine group, such as the CNC cell or the press shop, with twelve months of breakdown history and the manuals and SOPs for those machines.

Deliverables

  1. 01Digitised breakdown history for the pilot machines
  2. 02Indexed manuals, SOPs and OPLs
  3. 03Assistant on tablet or phone in Hindi and English
  4. 04Evaluation on a question set written by senior technicians
  5. 05Roll-out plan for other machine groups

What we measure

Answer accuracy
Senior technicians grade answers to a prepared question set and to real questions from the floor.
Citation correctness
Share of answers whose cited page or work order actually supports the statement.
Digitisation field accuracy
Structured records checked against the original registers on a sample.
Not-found rate
Share of questions the sources could not answer, used to find documentation gaps.

FAQs

01Our logbooks are handwritten in a mix of Hindi and English. Can you read them?

Yes, for most legible handwriting. Entries the system cannot read with confidence are flagged for a maintenance engineer to confirm, and the pilot report shows accuracy on your actual registers.

02What stops it from inventing a fix?

It answers only from retrieved documents and history, cites each source, and is designed to say it does not know when the sources do not cover the question. Technicians grade answers during the pilot, and the logs are reviewed.

03Can technicians use it in a noisy shop?

Voice works with a headset or a phone held close, and a machine QR tag opens the right context in one tap. In very noisy areas short typed queries are often more reliable, so we test both on the floor.

04Does it connect to SAP PM?

It can read notifications and work orders from SAP PM or another CMMS through an export or API, and draft closure notes for engineers to post. It does not create or close work orders on its own.

Related use cases

Akhilesh Mittal

Founded by Akhilesh Mittal. 8 years building a security platform for a New Zealand company. IIT ISM Dhanbad and IMT Ghaziabad. Builds production agentic AI.

Start with one line, one document or one region

Book a discovery call and we will pick a narrow pilot with your quality, finance or sales team, run it alongside your current process and report what we measured.