Transportation & Logistics

Shipment Exception Copilot

Designed for Logistics coordinator

Give the logistics coordinator a grounded working surface for in-transit shipment exceptions: detect the milestone miss, explain the root cause from carrier EDI and telemetry evidence, quantify the delivery-promise impact, and draft the carrier and customer response without leaving the exception record.

Contract TRA-01 · primary aggregate ShipmentException · mode loading

Decision brief

Coordinator adjudication of recovery option: 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

Logistics coordinator

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

2 approval gates

Approval gates prevent the copilot from making consequential decisions.

Business problem

A 22-pallet refrigerated LTL shipment tendered under a 48-hour service level posts an EDI 214 AF status with reason code NS at the Memphis cross-dock after a 210-minute dwell.

Decision to make

Give the logistics coordinator a grounded working surface for in-transit shipment exceptions: detect the milestone miss, explain the root cause from carrier EDI and telemetry evidence, quantify the delivery-promise impact, and draft the carrier and customer response without leaving the exception record.

Outcome to show

CustomerNotification gives Logistics coordinator with TMS connector the evidence needed to begin the final governed business outcome, with the decision trail retained for review.

  1. 1Milestone deviation detection
  2. 2Root-cause evidence assembly
  3. 3Recovery option generation
  4. 4Coordinator adjudication of recovery option
  5. 5Carrier tender and consignee notification

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

Logistics coordinator 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 ShipmentException 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 the logistics coordinator a grounded working surface for in-transit shipment exceptions: detect the milestone miss, explain the root cause from carrier EDI and telemetry evidence, quantify the delivery-promise impact, and draft the carrier and customer response without leaving the exception record.
Primary aggregate
ShipmentException
Primary container
shipmentExceptions
Hierarchical key
/tenantId + /shipmentId
Schema version
1

Sample scenario

A 22-pallet refrigerated LTL shipment tendered under a 48-hour service level posts an EDI 214 AF status with reason code NS at the Memphis cross-dock after a 210-minute dwell. The copilot assembles the event timeline, cites the carrier's service guide clause that permits a single expedite tender without shipper pre-authorization under 900 USD, and proposes rerouting through the Nashville terminal for a 6-hour slip instead of a 19-hour slip. The coordinator approves the reroute, the revised delivery window is written to the shipment header, and the consignee receives a cited notification naming the new Thursday 06:00-10:00 window.

Physical Cosmos DB containers

Every container provisioned for this accelerator with its hierarchical partition key.
Container Role Hierarchical partition key Document types
shipmentExceptions Primary /tenantId + /shipmentId Shipment, TrackingEvent, ExceptionCase, RecoveryPlanDraft, CustomerNotification
carrierContractLibrary Reference /tenantId + /carrierScac CarrierPolicyChunk

Document types

Contract document types, their owning container, and their identifier pattern.
Type Container Partition key Identifier pattern Embedding fields
Shipment shipmentExceptions /tenantId + /shipmentId shipment::{shipmentId} None
TrackingEvent shipmentExceptions /tenantId + /shipmentId shipment::{shipmentId}::event::{eventTimestampUtc}::{carrierScac} None
ExceptionCase shipmentExceptions /tenantId + /shipmentId shipment::{shipmentId}::exception::{exceptionId} None
CarrierPolicyChunk carrierContractLibrary /tenantId + /carrierScac carrier::{carrierScac}::policy::{policyDocId}::{chunkOrdinal} chunkVector
RecoveryPlanDraft shipmentExceptions /tenantId + /shipmentId shipment::{shipmentId}::plan::{planId} rationaleVector
CustomerNotification shipmentExceptions /tenantId + /shipmentId shipment::{shipmentId}::notification::{notificationId} None

Query patterns