How should a plant verify evidence provenance in an AI assisted maintenance recommendation?
An AI recommendation is reviewable only when its supporting evidence can be traced to a source, asset, timestamp and authorized user context. Fluent explanations are not substitutes for verified records.
Define the evidence envelope
Require each cited observation to identify the source system, record or document identifier, asset mapping, observation time, retrieval time and revision where applicable. Distinguish original measured data from derived features and model interpretation.
Check identity and time context
Validate that the historian tag, alarm, work order and document refer to the same physical asset and relevant operating mode. Compare time zones, clock quality, units, sensor health and data gaps. A shutdown trend must not be interpreted using steady state limits without explicit context.
Enforce permissions at retrieval
Apply source permissions before evidence is returned to the user or model. A generated citation must not bypass document access controls. Keep audit records of retrieval and any subsequent human approval or correction. Separate read only recommendations from changes to CMMS or control systems.
Separate observation, inference and action
Present what was measured, what the model inferred, alternative hypotheses and what is still unknown. Link directly to original records for authorized reviewers. Require an identified person to approve consequential work orders, operating changes or procurement decisions under site policy.
Test failure cases
Deliberately test stale manuals, conflicting tags, missing trend segments, renamed assets and revoked permissions. Reject or flag recommendations when evidence is unavailable. Track citation accuracy and unsupported claims as quality measures rather than only response speed.
Example: bearing temperature alarm
The system links a temperature rise to historian samples, equipment operating state, a recent lubrication work order and the current bearing manual. It flags a missing vibration interval and offers hypotheses for the planner to investigate. It does not assert bearing failure or release a work order on incomplete evidence.
Implementation checklist
- Assign an accountable technical owner and define the asset boundary.
- Identify required evidence, acceptance criteria and approval authority.
- Record deviations and unresolved questions before action.
- Verify completion with documented evidence and follow up.
Use site specific engineering judgment, OEM instructions, applicable regulations and authorized approvals. This guidance does not replace established safety or engineering procedures.
Explore KANE consulting
Discuss practical maintenance and reliability improvements for your facility.
Request a consultation →Related answers: Related guidance · Additional guidance
Technical reference
NIST SP 800-82 Rev. 3, Guide to Operational Technology Security