Decision owner
Area authority or operations superintendent
The named role remains accountable for the consequential decision.
Oil, Gas & Mining
Designed for Operations engineer
Give operations engineers on a facility or mine site instant, cited access to operating procedures, P&ID diagrams, and shift history so process decisions follow the approved envelope, with area-authority approval for any deviation.
Contract OIL-01 · primary aggregate OperationsQuery · mode loading
Decision brief
This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.
The evidence and control points that shape this recommendation.
Decision owner
Area authority or operations superintendent
The named role remains accountable for the consequential decision.
Governed evidence
6 record types
Structured records and cited text ground the recommendation.
Workflow
5 controlled stages
Each transition records its input, output, status, and audit context.
Human controls
1 approval gate
Approval gates prevent the copilot from making consequential decisions.
An engineer asks why a separator is running above its normal level; the copilot cites the current procedure limit, shows the P&ID region with the upstream inlet and its control valve, surfaces two night-shift entries noting a bypassed level controller, and routes the requested setpoint change as a deviation for the area authority to approve..
Give operations engineers on a facility or mine site instant, cited access to operating procedures, P&ID diagrams, and shift history so process decisions follow the approved envelope, with area-authority approval for any deviation.
Approved or refused deviation with compensating controls gives Area authority or operations superintendent the evidence needed to begin the final governed business outcome, with the decision trail retained for review.
Step 1 of 5
| Field | Value |
|---|
| Field | Value |
|---|
The output appears here immediately. More technical evidence remains available below.
The demonstration keeps deterministic controls, AI assistance, and approval separate.
Source systems enforce identity, workflow order, policy filters, and record updates.
Retrieval and generation assemble relevant evidence into a cited recommendation or draft.
Area authority or operations superintendent verifies material claims and approves the consequential action.
Run the stages in order before using the Copilot. Every stage explains what happens, why it matters, the evidence it uses, and the complete API request and response.
Automated stage
What happens: Operations engineer performs ask an operations question in context using Question with equipment tag and operating mode and produces OperationsQuery bound to the facility and area. The transition is deterministic and does not require autonomous model approval.
Why it matters: OperationsQuery bound to the facility and area gives Retrieval agent the evidence needed to begin Retrieve procedures, diagrams, and tags, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/ask-an-operations-question-in-context
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Retrieval agent performs retrieve procedures, diagrams, and tags using Question, tag, and current revision filters and produces Current-revision evidence set. The transition is deterministic and does not require autonomous model approval.
Why it matters: Current-revision evidence set gives Shift context agent the evidence needed to begin Correlate recent shift history, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/retrieve-procedures-diagrams-and-tags
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Shift context agent performs correlate recent shift history using Shift log entries referencing the tags and produces Recent changes and abnormal conditions. The transition is deterministic and does not require autonomous model approval.
Why it matters: Recent changes and abnormal conditions gives Operations copilot the evidence needed to begin Answer within the operating envelope, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/correlate-recent-shift-history
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Operations copilot performs answer within the operating envelope using Procedure limits and equipment design data and produces Cited answer stating the applicable limits and authority. The transition is deterministic and does not require autonomous model approval.
Why it matters: Cited answer stating the applicable limits and authority gives Area authority or operations superintendent the evidence needed to begin Approve any deviation from limits, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/answer-within-the-operating-envelope
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Human approval required
What happens: Area authority or operations superintendent performs approve any deviation from limits using DeviationRequest with risk assessment and produces Approved or refused deviation with compensating controls. A named human approver must review the evidence before the transition completes.
Why it matters: Approved or refused deviation with compensating controls gives Area authority or operations superintendent the evidence needed to begin the final governed business outcome, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/approve-any-deviation-from-limits
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Run a stage to see its explanation, evidence, full request, and full response.
Ask a question and receive an answer grounded in retrieved OperationsQuery evidence.
Select a starter question or enter your own.
Loaded live from /api/config, /api/domain/model, and
/api/domain/sample.
operationsQueries/tenantId + /facilityIdAn engineer asks why a separator is running above its normal level; the copilot cites the current procedure limit, shows the P&ID region with the upstream inlet and its control valve, surfaces two night-shift entries noting a bypassed level controller, and routes the requested setpoint change as a deviation for the area authority to approve.
| Container | Role | Hierarchical partition key | Document types |
|---|---|---|---|
operationsQueries |
Primary | /tenantId + /facilityId |
OperationsQuery, ProcessDiagramAsset, EquipmentTagRecord, ShiftLogEntry, DeviationRequest |
operatingProcedureLibrary |
Reference | /tenantId + /procedureId |
OperatingProcedure |
| Type | Container | Partition key | Identifier pattern | Embedding fields |
|---|---|---|---|---|
OperationsQuery |
operationsQueries |
/tenantId + /facilityId |
query::{facilityId}::{queryId} |
questionVector |
OperatingProcedure |
operatingProcedureLibrary |
/tenantId + /procedureId |
procedure::{procedureId}::{stepIndex} |
stepVector |
ProcessDiagramAsset |
operationsQueries |
/tenantId + /facilityId |
diagram::{facilityId}::{diagramId} |
diagramSummaryVector |
EquipmentTagRecord |
operationsQueries |
/tenantId + /facilityId |
tag::{facilityId}::{equipmentTag} |
None |
ShiftLogEntry |
operationsQueries |
/tenantId + /facilityId |
shiftlog::{facilityId}::{entryId} |
entryVector |
DeviationRequest |
operationsQueries |
/tenantId + /facilityId |
deviation::{facilityId}::{deviationId} |
None |
Read equipment master, related diagrams, and recent shift entries for a tag in one partition query.
operationsQueries
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.facilityId = @facilityId AND c.type IN ('EquipmentTagRecord','ProcessDiagramAsset','ShiftLogEntry') AND ARRAY_CONTAINS(c.referencedTags, @equipmentTag) ORDER BY c.loggedUtc DESC
Knowledge-container query against operatingProcedureLibrary (partition-aligned to /tenantId + /procedureId): return only the current approved revision of the operating procedure steps, read as a single partition query on the procedure.
operatingProcedureLibrary
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.procedureId = @procedureId AND c.type = 'OperatingProcedure' AND c.revisionStatus = 'current' ORDER BY c.stepIndex ASC
Show shift log entries in the area that flagged abnormal operation.
operationsQueries
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.facilityId = @facilityId AND c.type = 'ShiftLogEntry' AND c.areaId = @areaId AND c.loggedUtc > @lookbackUtc ORDER BY c.loggedUtc DESC
List deviations awaiting authority decision or still active with compensating controls.
operationsQueries
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.facilityId = @facilityId AND c.type = 'DeviationRequest' AND c.authorityDecision IN ('pending','approvedActive') ORDER BY c.deviationId ASC