Skip to main content
MAN-03 · Manufacturing

Factory Operations Shift Copilot

Outcome​

Give a shift supervisor a single grounded view of the running shift by fusing MES production events, downtime reasons, quality alerts, and handover notes into prioritized actions and an auto-drafted handover the supervisor signs.

Portfolio attributeValue
Primary personaShift supervisor
Primary aggregateProductionShift
Cosmos DB containers1
Grounding dataMES events, downtime, alerts, shift notes
Development estimateUSD 60-220 monthly dev estimate
Runtime optionsPython FastAPI and C# ASP.NET Core

Productivity hypothesis​

These measures reflect the workflow, evidence, decision boundary, and industry risk for this use case.

Impact typeMeasureConservative internal assumptionCustomer measurement
ProductivityHandover or recovery cycle time8-15% reduction(baseline median handover or recovery minutes - assisted median minutes) / baseline median minutes * 100
Quality or riskEvidence discovery time10-20% reduction(baseline median evidence-search minutes - assisted median evidence-search minutes) / baseline median evidence-search minutes * 100
Business outcomeOn-time recovery or schedule attainment3-8% relative improvement(assisted on-time shifts per eligible shift - baseline rate) / baseline rate * 100

Important: Conservative internal pilot assumptions only; not public benchmarks, commitments, or expected customer results. Validate against a comparable baseline or matched control cohort with mandatory human review.

Rationale: MES, PLC, ERP, QMS, and CMMS reconciliation supports faster shift decisions and a cautiously measurable recovery outcome.

Pilot guardrail: Do not bypass supervisor sign-off, safety controls, or source-system authority.

Customer validation plan​

  1. Baseline the current workflow with representative users and tasks.
  2. Run the accelerator on the same task mix with human review retained.
  3. Measure handover or recovery cycle time and evidence discovery time with the documented formulas.
  4. Replace internal assumptions with customer-observed results before a business case.

Why Azure Cosmos DB​

This AI solution needs an operational data plane, not only a vector index:

  • Hybrid vector and full-text retrieval combines semantic recall with exact identifiers, codes, names, and domain language.
  • Hierarchical partition keys and metadata predicates keep tenant and domain boundaries in the normal query path.
  • Operational JSON, source chunks, workflow and agent state, feedback, and audit records remain together for low-latency reads and governed writes.
  • Change feed reacts to source and operational updates without polling.
  • Autoscale throughput, configurable consistency, and multi-region distribution support variable demand and enterprise availability.

Domain workflow​

Domain workflow

StageActorInput → outputApproval
1. Open the shift and load the planShift supervisorShift schedule, crew roster, and order sequence → ProductionShift with targets and constraintsPolicy controlled
2. Stream production and downtime eventsMES integration serviceMachine counts, stoppages, and reason codes → Live output and downtime event streamPolicy controlled
3. Rank losses and quality risksAnalytics agentDowntime minutes, scrap, and quality alerts → Prioritized loss list with probable causesPolicy controlled
4. Recommend the next line actionsShift copilotLoss ranking, order due times, crew availability → Cited action list such as changeover resequencingPolicy controlled
5. Sign the shift handoverShift supervisorDrafted handover with open issues and commitments → Signed ShiftHandoverNote passed to the next crewHuman required

Technical architecture​

Technical architecture

Cosmos DB data model​

ContainerHierarchical partition keyDocumentsSearch paths
productionShifts/tenantId, /plantLineIdProductionShift, DowntimeEvent, ProductionOrderStatus, QualityAlert, ShiftHandoverNote/operatorCommentVectorEmbedding, /narrativeVectorEmbedding, /operatorCommentVector, /narrativeVector

Query contract​

QueryContainerScopePurpose
Live shift dashboardproductionShiftssingle-partitionRead shift state, orders, downtime, and alerts for the line in one partition query.
Top downtime reasons this shiftproductionShiftssingle-partitionRank stoppage reason codes by lost minutes to focus the crew.
Orders at risk of missing due timeproductionShiftssingle-partitionFlag orders whose remaining quantity cannot finish before the due time at current rate.
Undispositioned quality alertsproductionShiftssingle-partitionList open quality alerts that must be resolved before handover.

Python and C# services route each document type to its declared container and hierarchical partition key. ETag-based writes protect mutable aggregates, while append-only records and bounded cross-partition queries preserve scale.

Azure deployment​

Azure deployment

Clone the source repository, authenticate with Azure, and run:

Set-Location accelerators/manufacturing/factory-operations-shift-copilot
az login
./Deploy.ps1 -Runtime python -Location eastus2

Change python to csharp to deploy the .NET implementation.

Explore the implementation​

Return to all accelerators