Controlled Industrial Intelligence · Engineering example
Contextual Operator Knowledge
Bring approved procedures, equipment revision, qualified live state, maintenance history, and the current shift handoff together for an authorized operator. Answer with cited evidence and visible uncertainty, while established people and control systems retain operating authority.
The operating challenge
The procedure is only useful when it matches the equipment and the moment.
An operator starting a shift may find a maintenance PDF but still need to know whether the machine was modified, which alarm remains active, what a technician inspected, and what the prior shift already tried. A search result without asset identity, revision, access role, and current state can be dangerously persuasive. Contextual operator knowledge links approved instructions to the situation and says clearly when the available evidence is not enough.
Right source
Only effective, approved procedures and authorized records belong in an answer. Drafts and superseded revisions need clear exclusion.
Right context
Site, equipment serial, configuration, operating mode, alarm, and current work status determine what is relevant.
Right authority
An assistant can organize facts and suggest who to ask. It cannot approve a restart, bypass an interlock, or substitute for required training.
Why modernize: New and experienced staff can find the same approved evidence faster and prepare more complete shift handoffs, without moving safety and operating decisions into a conversational tool.
Illustrative operating example
A compressor returns from service before the evening shift.
This compressor-handoff scenario is illustrative. It is not a claim about a completed customer installation or an instruction for operating a specific machine. Site-approved procedures and trained personnel govern real work.
Imagine a plant compressor was inspected after repeated high-temperature alarms. Maintenance closed a work order in the afternoon, but the evening operator sees another alert and asks, “What changed, and what should I check?” A generic chatbot might quote an old manual or give a restart sequence. A contextual assistant first confirms the asset and user's role, retrieves the current approved alarm-response procedure, shows the latest qualified alarm and maintenance summary with timestamps, and notes if a follow-up inspection is still open. If the configuration or records disagree, it stops and directs the operator to the supervisor or maintenance lead.
- Establish identity and role.Resolve the exact compressor, site, equipment revision, operator role, and permitted question type.
- Retrieve approved instruction.Filter by effective date, revision, asset applicability, and access before extracting a relevant passage.
- Attach current evidence.Show qualified alarms, last service work, open holds, and prior-shift note with source and time.
- Answer narrowly.Summarize what the records say, cite each source, state what remains unknown, and point to the approved escalation path.
- Keep action controlled.The operator follows site procedure; qualified staff verify equipment condition and authorize any restart or maintenance action.
What the reviewer would see
Compressor C-4: shift evidence
Evidence and handoff, not an autonomous operating order.
- Scope
- Asset, site, configuration, role, and current operating mode.
- Approved source
- Procedure title, revision, effective date, and cited section.
- Current state
- Alarm time, data quality, work-order status, and shift note.
- Next person
- Named function or on-call role under the approved escalation path.
Other high-priority situations
Good context prevents confident but irrelevant answers.
Changeover after a product revision
Show only the effective work instruction for that product and line configuration, along with the latest setup check and unresolved quality hold. An older instruction stays visible as superseded, not silently quoted.
Useful report: revision match, retrieval path, missing setup evidence, and escalation.
Maintenance troubleshooting at shift change
Bring approved diagnostic references, recent work, current alarms, and parts availability together. If an action needs isolation or a qualified technician, the assistant routes the question instead of giving step-by-step improvisation.
Useful report: evidence cited, open work, responsible team, and handoff completeness.
What a modernization would connect
Retrieve by authority, applicability, and live operating context.
This is more than semantic search. It requires an approved source register, access controls, asset and document version maps, qualified operational events, and a response contract that cites evidence or abstains. The source owner remains responsible for procedures; the assistant cannot edit them merely because a user asks.
Required operating evidence
- User role, site, purpose, asset, serial, and configuration
- Document owner, status, revision, effective date, and applicability
- Qualified current alarms, mode, holds, and maintenance work
- Shift note, author, timestamp, and unresolved question
- Retrieved passage, citation, confidence, and excluded conflicts
- Escalation, feedback, and source correction history
Permissions are applied before retrieval; a citation does not grant access to a document the user may not see.
Connected technical layers
- Identity and least-privilege access
- Approved procedure and version repository
- Read-only qualified operating and maintenance context
- Scoped retrieval with citation and abstention checks
- Handoff, feedback, and audit workflow
No natural-language answer executes a command or changes a protected control state.
If the exact asset or effective procedure cannot be established, the safer answer is an explicit uncertainty and handoff, not a best-guess instruction.
Where automation and AI fit
Automate evidence assembly, not authority.
Deterministic automation
Enforce access, revision, asset applicability, source status, and allowed response type before the assistant receives context. Route unresolved safety or configuration questions to the correct role.
Analytical methods
Measure retrieval quality, citation coverage, repeated unresolved questions, and documentation gaps. Review whether a faster answer was also correct and actionable.
Evidence-linked AI assistance
Summarize approved passages and recent events with explicit citations and timestamps. It must resist conflicting instructions in retrieved text and abstain when evidence is incomplete.
Human operating authority
Procedure owners approve content; supervisors and qualified operators authorize consequential actions; maintenance and safety teams handle protected work.
How we examine a proposed solution
AI advisors test relevance, source control, and escalation.
These Adaptiv Stratum AI advisory roles support bounded design review and do not operate equipment.
Argus
Checks document, asset, and event identity.
Hephaestus
Tests physical relevance of the cited procedure.
Pythia
Examines repeated questions and knowledge gaps.
Aegis
Challenges stale records and unsupported instructions.
Clio
Measures citation quality and handoff resolution.
Themis
Reviews access, source ownership, and approval boundaries.
What becomes visible
Track whether an answer was grounded, useful, and safely bounded.
A good report does not count every chat answer as a resolved operating issue. It shows which approved sources were used, whether the equipment and revision matched, and whether the operator still needed a person.
Per-question record
- Authorized role, site, asset, and purpose
- Approved source, revision, passage, and event timestamps
- Answer, citations, and explicit uncertainty
- Conflict or missing-context reason
- Escalation, feedback, and actual resolution
Knowledge-system health
- Time to find approved information
- Citation, revision, and asset-match coverage
- Unresolved and safely abstained questions
- Frequently missing procedures or unclear ownership
- Incorrect or stale answers caught in review
- Handoff completion and source corrections
Usage volume is not a quality measure. A safe refusal can be the correct outcome when the source or equipment identity is uncertain.
Operating safeguards
Keep instructions authoritative and answers accountable.
- Role and purpose checked before retrieval
- Only effective, approved revisions used
- Asset and configuration applicability verified
- Every operational assertion linked to a source
- Qualified current-state data with visible age
- Conflicts and unknowns produce abstention or escalation
- No command, bypass, restart, or safety approval by chat
- Feedback goes to source owners under change control
A practical first phase
Pilot one equipment family and ten recurring shift questions.
- Set the boundary.Choose one equipment family, roles, safe question types, and the handoff path for action requests.
- Curate sources.Confirm owners, current revisions, asset applicability, and access for a small procedure set.
- Connect bounded context.Add qualified alarms, work orders, and shift notes in read-only form.
- Test hard cases.Include a superseded manual, ambiguous asset, missing alarm, and conflicting maintenance record; verify abstention.
- Review with operators.Score citation correctness, time saved, escalation quality, and whether approved decisions remained with people.
Begin with a shift question
Which recurring question forces operators to search three systems before calling the right person?
A focused pilot can make that evidence easier to assemble without replacing the person.
Evidence and further reading
Connected information still needs approved source control.
These sources inform the integration and risk approach. The compressor example is illustrative, not an Adaptiv Stratum customer case study.
- NIST: Digital Thread for Smart Manufacturing describes the challenge of connecting authoritative manufacturing information across silos.
- NIST: AI Risk Management Framework offers a framework for governing and evaluating AI-enabled assistance.
- NIST: Guide to Operational Technology Security addresses reliability, safety, and security requirements for connected physical systems.