Automotive & Mobility

Fleet Operations Copilot

Designed for Fleet manager

Keep a mixed combustion and electric fleet running by fusing telemetry, route plans, charging availability, and maintenance status into ranked interventions, with the fleet manager approving vehicle swaps and route changes.

Contract AUT-03 · primary aggregate FleetOperationsDay · mode loading

Decision brief

Approve the dispatch change: 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

Fleet manager

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

On a cold morning the copilot detects four electric vans whose state of charge will not cover their planned routes with a 20 percent winter derate, finds two depot chargers already occupied, recommends swapping two routes to diesel units and adding a midday top-up for the rest, and the fleet manager approves the plan before the 06:30 departure wave..

Decision to make

Keep a mixed combustion and electric fleet running by fusing telemetry, route plans, charging availability, and maintenance status into ranked interventions, with the fleet manager approving vehicle swaps and route changes.

Outcome to show

Committed dispatch update sent to drivers gives Fleet manager the evidence needed to begin the final governed business outcome, with the decision trail retained for review.

  1. 1Build the depot day plan
  2. 2Ingest vehicle telemetry and charger state
  3. 3Detect range, maintenance, and capacity exceptions
  4. 4Recommend swaps, charging, or re-routes
  5. 5Approve the dispatch change

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

Fleet manager 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 FleetOperationsDay 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
Keep a mixed combustion and electric fleet running by fusing telemetry, route plans, charging availability, and maintenance status into ranked interventions, with the fleet manager approving vehicle swaps and route changes.
Primary aggregate
FleetOperationsDay
Primary container
fleetOperationsDays
Hierarchical key
/tenantId + /fleetDepotId
Schema version
1

Sample scenario

On a cold morning the copilot detects four electric vans whose state of charge will not cover their planned routes with a 20 percent winter derate, finds two depot chargers already occupied, recommends swapping two routes to diesel units and adding a midday top-up for the rest, and the fleet manager approves the plan before the 06:30 departure wave.

Physical Cosmos DB containers

Every container provisioned for this accelerator with its hierarchical partition key.
Container Role Hierarchical partition key Document types
fleetOperationsDays Primary /tenantId + /fleetDepotId FleetOperationsDay, VehicleStatus, RoutePlan, ChargingSessionPlan, MaintenanceDueItem, OperationalException

Document types

Contract document types, their owning container, and their identifier pattern.
Type Container Partition key Identifier pattern Embedding fields
FleetOperationsDay fleetOperationsDays /tenantId + /fleetDepotId operationsday::{fleetDepotId}::{operationsDate} None
VehicleStatus fleetOperationsDays /tenantId + /fleetDepotId vehiclestatus::{fleetDepotId}::{vehicleId} None
RoutePlan fleetOperationsDays /tenantId + /fleetDepotId route::{fleetDepotId}::{routeId} None
ChargingSessionPlan fleetOperationsDays /tenantId + /fleetDepotId charging::{fleetDepotId}::{sessionId} None
MaintenanceDueItem fleetOperationsDays /tenantId + /fleetDepotId maintenance::{fleetDepotId}::{itemId} None
OperationalException fleetOperationsDays /tenantId + /fleetDepotId exception::{fleetDepotId}::{exceptionId} remedyVector

Query patterns