Maintenance Log Retrieval in Heavy Industry

A mechanical head asked for ChatGPT on twenty years of breakdowns. What he needed was to find, in ten minutes, the last time that make of seal had failed on that unit, and the OEM page that forbade a shortcut someone was about to take. He did not need a model to raise a work order in the EAM system because it felt confident.

Heavy-industry maintenance corpora are uneven: scanned registers, SAP notifications, OEM PDFs with bad OCR, WhatsApp photos, and a few honest incident reports. Similarity search can help. Similarity search can also retrieve another unit's outage and present it as this morning's truth.

This guide is for the SI who will be blamed for the wrong retrieval. Keep the agent in IT. Keep access as tight as the paper file. Keep the work-order button human.

What to index, and what to leave in the cupboard

Index signed maintenance histories, approved OEM manuals, standing orders, and closed notifications you are allowed to see. Prefer text that has an identifier: notification number, equipment number, revision date.

Leave out live OT tags, engineering-workstation backups, uncleared photos of injured people, and another plant's arbitration files that happened to sit on the same share. Leave out draft RCA notes marked privileged until counsel says otherwise.

OCR is a project. If the 2004 register is unreadable, say so in the UI. A model that guesses a bearing number from a smudge is a hazard.

Access is the product

If a fitter on unit 2 could not walk into unit 1's cupboard, the index must not do it for him. Collection-level isolation by plant, unit and contractor status is not optional elegance.

OEM manuals often carry licence and export-control markings. Your contract with the OEM may already limit copies. Do not helpfully embed a restricted manual into a vendor's cloud to improve recall.

Contractors who see the retrieval UI are a data-class decision. Default to employees. Add contractors with a named owner.

Citation or silence

Every answer should show the notification number or the manual revision it used. If it cannot, it should refuse. Paraphrase without a handle is how shortcuts become folklore.

When two manuals disagree, show both. Do not average them. Averaging torque values is not intelligence.

No write to the EAM from the chat

Creating a notification can be a later, gated workflow. It is not a week-one tool. A hallucinated equipment number in a live SAP notification is worse than a slow search.

If you ever add a write tool, it creates a draft only, in the user's own name, with the retrieved identifiers attached, and an independent accept in the EAM. Until then, copy-paste by a human is acceptable and safer.

Objections you will hear — and what to do with them

These are the lines that stall the file. Answer them in the room, then put the answer in the note.

One index is simpler to run

Simpler for you. More dangerous for the plant. Split by unit at least. Operations convenience is not a safety case.

The OEM PDF is watermarked, we will retype it

Retyping can violate the licence and will introduce errors. Get a usable official file or link the official portal. Do not create a shadow manual.

Fitters will not use a system that refuses

They already use a cupboard that sometimes has nothing. A honest refusal is better than a wrong torque.

We need multimodal on the oil photo

Then build a separate, narrower workflow with a vision model you can isolate. Do not dump every WhatsApp image into the same store as OEM manuals.

Four weeks on one equipment family

1. Week 1: pick one family and one unit. List the official manuals and the EAM extract you are allowed to take. Get OT to confirm you are not pulling live tags.
2. Week 2: index with unit-scoped credentials. Build citation-mandatory answers. Add the prefix-collision test.
3. Week 3: give five engineers ten real hunt tasks from last year. Score handles retrieved, not fluency.
4. Week 4: write the standing order: no EAM write, no cross-unit default, no OEM file in a public cloud. Only then talk about a second family.

How this shows up in the file

Subject: Maintenance-log retrieval — scope and isolation.

Retrieval shall be limited to signed histories and approved manuals for a defined unit and equipment family. Answers without a document handle shall refuse. The agent shall not create EAM notifications or touch OT.

Cross-unit default search is prohibited. This note is an internal aid. It is not legal or OEM-licence advice.

OCR honesty is a safety control

A confidence score on a smudged 2004 register is not a bearing number. If the page is unreadable, the UI should say the cupboard is empty for that year. Engineers will then walk to the real cupboard. That walk is cheaper than a wrong torque.

Prcept AI will isolate collections by unit. We will refuse hosted embeddings on OEM manuals. We will not wire SAP write in week one. If recall without a handle is your demo, we will fail the demo.

Contractors on the search bar

A contractor who can search unit 1's history can also walk that history off site. If your paper file already required an escort, the index requires a named sponsor, a time-bound account, and no download of OEM PDFs. Default deny is not hostility. It is how you still have a licence to hold the manuals.

Night-shift 'just this once' accounts are how collections merge. The SI should not be able to widen a collection from the chat UI. Widening is a CAB change with OT and the mechanical head in the room. If that feels slow, good. Wrong torque is slower.

When two OEM revisions disagree, the UI must not pick the friendlier torque. Show both revisions and the dates. The engineer signs the job card. The model does not average. Averaging is how a shortcut becomes a standing practice.

This article is informational field guidance for Indian public institutions, not legal, procurement, security-accreditation, engineering or board advice. Confirm against the live Gazette, GFR, GeM term, CVC instruction, CERT-In direction, UIDAI regulation, DPE guideline, DPDP text, departmental charter, plant safety manual and your counsel before you file it.

How this clears vigilance and the board

A P4 System Integrator in a PSU will meet CVC-shaped questions even when there is no special 'AI circular'. “Maintenance Log Retrieval in Heavy Industry” has to survive a technical committee, a cost centre, and a union conversation if jobs appear threatened.

The job is to find the 2018 seal failure and the right OEM page. The job is not to invent a work order from a neighbour unit's log. OT networks stay off-limits. Navratna autonomy speeds buying; it does not waive DPDP or data classification. IREPS is not GeM. RBI-shaped rules still localise payment data.

• Classify data before the POC.
• Keep agents off OT.
• Write the board memo with residual risk.
• Engage unions on retrieval vs replacement.

Close this loop before the next CAB

Put “Maintenance Log Retrieval in Heavy Industry” on the next change-advisory or bid-opening agenda as a single line item with an owner. If it cannot earn a line item, it will not earn a control. The owner should be a P4 System Integrator, not “the vendor.”

Revisit the item when the model, the GeM term, the region, or the SI changes. “maintenance records AI search” is not a one-time workshop. It is a watch item. Date the last check. Unsigned watch items are souvenirs.

What must be true before you file this

If “Maintenance Log Retrieval in Heavy Industry” is only a heading, it will not survive a file inspection. A P4 System Integrator should be able to attach one artefact that proves “maintenance records AI search”: a log export, a clause, a scored row, a dated notice, or a refusal rule.

Write three dated sentences: what was decided, who owns it, and when it will be re-checked. Unsigned sentences are souvenirs. Dated sentences are controls.

• Name the owner of “maintenance records AI search” inside the institution.
• Attach one artefact a stranger can open next year.
• Revisit when the model, the notice, or the SI changes.
• Do not treat a vendor slide as evidence.

What the next file must contain

“Maintenance Log Retrieval in Heavy Industry” earns a line in the noting only if a P4 System Integrator can attach proof of “maintenance records AI search.” A heading is not proof. A vendor slide is not proof. A workshop photograph is not proof.

Write three dated sentences: what was decided, who owns it after the next posting order, and when it will be re-checked. If you cannot write the three sentences, you are not ready to buy, to sell, or to go live.

Leave unsourced percentages out of the note. DPDP is not a blanket localisation statute. The November 2025 AI governance text is guidance, not an Act. CERT-In’s 28 April 2022 directions still set specified incident and log clocks. A PAC, when lawful, lives in GFR Rule 166.

• Name the designation that owns “maintenance records AI search.”
• Attach one artefact a stranger can open next year.
• Record the instrument you are actually using.
• Revisit when the model, the SI, the notice or the posting changes.