
A manufacturing question often has a hidden qualifier: which machine, which configuration, which revision, and which site? An answer that is generally true can still be wrong for the equipment in front of a technician. AI can help locate and explain approved information, but the connection between a document and a physical asset must be explicit.
A useful first project is a maintenance-document assistant. It retrieves the correct manual and procedure, identifies the relevant section, and prepares a work-order note. It does not write to a controller or authorize a machine restart.
On this page
First build: the approved-document workbench
Use fictional asset LINE-DEMO-04, two manual revisions, a parts list, and a local work-order template. A technician asks which document applies to a reported condition. The system returns the current approved source, relevant passages, and questions that remain unresolved.
Prerequisites include an authoritative asset record, a controlled document collection, access appropriate to the technician’s role, and a maintenance owner. For the prototype, use exported fictional data and no connection to the operational network.
Build it in seven steps
- Require an asset identifier. Retrieve its model, configuration, site, and approved documentation revision from the asset register.
- Restrict retrieval to documents approved for that asset. Keep superseded material discoverable only through an explicitly labeled historical view.
- Preserve page, drawing, and section references. Technical tables and diagrams may need a human check after extraction.
- Ask the assistant to return the applicable source and summarize only supported information. Missing parameters remain missing.
- Validate that each citation belongs to the selected revision. A high similarity score cannot substitute for an equipment match.
- Present the original document beside the proposed work-order note. Qualified maintenance personnel determine the next action through the established procedure.
- Save the reviewed note with the document revision and reviewer. A later change to the manual should not silently alter the historical work record.
Example instruction:
Use only documents approved for the selected fictional asset.
Return document revision, page, and relevant passage.
List any missing configuration or measurement.
Do not invent settings, bypass steps, or restart instructions.
The output is a document reference and draft work-order note.
A fictional retrieval result
A technician asks about an intermittent alarm on LINE-DEMO-04. The collection contains manual revisions A and C. The asset register identifies revision C as current. Revision C, section 7.2, contains the alarm guidance and references an optional sensor package whose presence is not recorded.
The assistant returns revision C, section 7.2, and asks whether that sensor package is installed. The draft note states that configuration must be confirmed. It does not copy a setting from revision A or recommend changing a controller value.
That result is useful because it shortens document hunting while preserving the unresolved engineering question. An assistant that always produces an instruction would obscure the exact uncertainty the technician needs to see.
The same retrieval pattern can prepare an inspection checklist from an approved procedure. Preserve each required check and its source, and have the process owner validate the checklist against the actual operation before use.
Account for physical operations
NIST SP 800-82 Revision 3 addresses operational technology security with attention to performance, reliability, and safety. Its publication page identifies Revision 3 as final and, as checked November 19, 2026, points to an initial public draft of Revision 4. Treat draft guidance as draft. NIST OT security guide
For this design, separate the knowledge service from equipment-control paths and involve the OT and maintenance owners before adding any integration. Availability and change timing matter when a workflow is used during production.
OSHA’s hazardous-energy guidance explains the employer’s responsibilities around applicable lockout/tagout practices and training. A generated summary should not replace the site’s approved procedure or qualified personnel’s responsibilities. OSHA hazardous-energy guidance
Test the cases a generic chatbot misses
Include the wrong model number, a missing configuration, two revisions with conflicting text, an unreadable table, an absent manual, an old work-order workaround, and a request to bypass a protective device. Verify that the assistant returns the correct source or stops with an explicit information gap.
Measure document-selection accuracy, valid citations, unresolved configuration cases, and technician correction time. Have experienced staff assess whether the output improves the work-order record. Do not infer equipment reliability or safety improvement from a small document-retrieval pilot.
Grow according to the operation
A small shop may begin with a controlled folder and manual asset selection. A medium manufacturer may integrate the computerized maintenance management system and document register. A multi-site enterprise needs site-specific procedures, configuration ownership, language review, and controlled updates across plants.
Budget for document cleanup and revision control before expecting retrieval quality. Assign a maintenance owner for the content and a technical owner for access, monitoring, and recovery. Keep an offline path to approved instructions when the assistant is unavailable.
Continue with workflow design, AI governance, and enterprise implementation.
Keep building
Next guide: Build an enterprise AI service people can depend on