Oil, Gas & Mining

Operations Knowledge Copilot

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

Approve any deviation from limits: evidence ready for review

This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.

Decision signals

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.

Business problem

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..

Decision to make

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.

Outcome to show

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.

  1. 1Ask an operations question in context
  2. 2Retrieve procedures, diagrams, and tags
  3. 3Correlate recent shift history
  4. 4Answer within the operating envelope
  5. 5Approve any deviation from limits

Step 1 of 5

Ready: Start with the business question, then use the single button above.

The output appears here immediately. More technical evidence remains available below.

System logic, GenAI, and human accountability

The demonstration keeps deterministic controls, AI assistance, and approval separate.

System logic

Source systems enforce identity, workflow order, policy filters, and record updates.

GenAI contribution

Retrieval and generation assemble relevant evidence into a cited recommendation or draft.

Human accountability

Area authority or operations superintendent verifies material claims and approves the consequential action.

Workflow stages

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.

Seeded record
Loading
Document type
Loading
Container
Loading
Partition key
Loading
Current stage
Loading

API demonstration guidance

Run a stage to see its explanation, evidence, full request, and full response.

Grounded chat

Ask a question and receive an answer grounded in retrieved OperationsQuery evidence.

Answer and evidence

Select a starter question or enter your own.

Evidence

Domain implementation workspace

Loaded live from /api/config, /api/domain/model, and /api/domain/sample.

Domain objective
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.
Primary aggregate
OperationsQuery
Primary container
operationsQueries
Hierarchical key
/tenantId + /facilityId
Schema version
1

Sample scenario

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.

Physical Cosmos DB containers

Every container provisioned for this accelerator with its hierarchical partition key.
Container Role Hierarchical partition key Document types
operationsQueries Primary /tenantId + /facilityId OperationsQuery, ProcessDiagramAsset, EquipmentTagRecord, ShiftLogEntry, DeviationRequest
operatingProcedureLibrary Reference /tenantId + /procedureId OperatingProcedure

Document types

Contract document types, their owning container, and their identifier pattern.
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

Query patterns