01
Release
What enters the floor right now?
240 candidates180 released
60 deferred - each with a reason
Decision Intelligence Layer
OPTIMIZE THE SHIFT,
NOT JUST THE PICK.
Tessera sits on top of your WMS and decides what work to release, how to group it, and what to prioritize - every constraint on the floor, one optimization.
The Problem
VISIBILITY ISN'T THE GAP. THE RESPONSE IS.
Your WMS can see the problem. It cannot tell you what to do about it given everything else happening on the floor.
Zone A22/30
Zone B31/40
Zone C18/40
Zone D19/25
priority_override: ORDER-4210
▸ One hot order. One simple rule.
The Product
FOUR DECISIONS. ONE PASS.
Give Tessera your open work and floor state. It returns a complete execution plan - solved jointly, because the answer to each decision depends on all the others.
02
Batching
How is released work grouped?
180 tasks → 12 batches · zone caps respected
03
Routing
What sequence does each batch follow?
total travel11.4 km
−14% travel · aisle rules · zone crossings
04
Prioritization
What gets worked first?
1BATCH-007cutoff 13:40
2BATCH-002cutoff 15:10
3BATCH-011cutoff 16:00
4BATCH-004cutoff 18:30
→ 1 executable plan · 180 tasks · 12 batches · 0 late-risk orders - solved jointly, in one optimization pass
One model solves all four. A release decision never creates work that batching can't feasibly group, and a priority ranking never contradicts the deadlines the batcher already accounted for. Hard constraints are enforced inside the model - not as post-hoc checks.
EXPLAIN, DECIDE, PREDICT, EMPOWER.
One model. Four capabilities. Every decision grounded in the same optimization that reasons about all constraints simultaneously.
Explain
Trace why the floor looks the way it does. Not alerts - causal reasoning grounded in the model.
Release pushes 38 tasks to Zone C
max_zone_load hits 95%
Batching concentrates aisles C3–C5
Picks per hour drop 18%
Decide
One optimization pass over every objective and constraint at once - not one rule at a time.
deadline_compliance✓
travel_efficiency✓
zone_congestion✓
congestion_minimization✓
zone caps · cart limits✓
→ 1 executable plan · 12 batches · 0 late orders
Predict
The same model that decides also predicts. Drag the wave size - Tess runs the scenario without touching the live plan.
what_if · non-persistent simulation
orders in next wave100
total_distance vs plan+0%
n_predicted_late_orders1
Empower
Operators set shift-level posture, not individual alerts. Your intuition sets the weights - the optimizer handles the rest.
max throughputdeadline safety
posture: Tess's Choice
deadline_compliance 45%travel_efficiency 30%zone_congestion 15%congestion_min 10%
OPERATOR INTENT, OPTIMIZER EXECUTION.
Your experience makes the system better, not the other way around. Operators speak in operational language - the optimizer turns it into posture, plans, and trade-offs.
The operator says
The optimizer runs with
deadline_compliance60%
travel_efficiency20%
zone_congestion10%
congestion_minimization10%
Alternatives this cycle
Tess’s Choicetravel +6%0 late-risk
minimize_traveltravel −18%3 late-risk
reduce_latenesstravel +22%0 late-risk
▸ posture set per shift · alternatives recomputed every cycle
AI Copilot
TALK TO YOUR OPTIMIZER. TALK TO TESS.
Tess doesn't query a dashboard. It invokes the optimizer - modifying inputs, running scenarios, and tracing every answer to a specific constraint or metric in the model.
Tess · operator console
Translate intent into action
Say the outcome you want - Tess finds the optimizer inputs that produce it.
Explain every decision
Every answer traces to a binding constraint or an actual optimizer run - including counterfactuals.
Guide through disruptions
Short picks, blocked zones, station outages - local repair or full re-optimization, Tess tells you which.
Brief every shift
Starting conditions and a suggested posture before. What happened, and why, after.
INTEGRATION SCALES TO YOUR NEEDS.
Tessera connects to your existing WMS. No rip-and-replace. Start simple - go deeper when you're ready.
POST /orchestrator/v1/runs
{"facility_id": "ATL1",
"workflow": "heartbeat",
"mode": "advisory",
"job_config": {"max_batches": 12,
"max_tasks_per_zone": 40,
"weights": { "tardiness": 0.5, "throughput": 0.4, "zone_congestion": 0.1 }},
"release_selector": { "job_ids": ["MHT-JOB-ATL1-1001"] }}
Your WMS
Oracle · SAP EWM · BC
tasks · waves · inventory · events →
← hold · release · priority · sequence
Tessera
one model · every cycle
advisory: plan to dashboardclosed-loop: write back to WMSguardrails: hard constraints · anomaly fallback to advisory · full audit trail
▸ no custom hardware, no sensor feeds, no worker GPS - just data your WMS already tracks
| Platform | Read Surface | Write Surface | Closed-Loop Viability |
|---|---|---|---|
| Oracle WMS Cloud | Tasks, waves, replenishment, inventory | Tasks (hold, release, priority), waves | Strong |
| SAP EWM | Warehouse Tasks, Orders, bin content | Task creation, confirmation | Viable |
| Business Central | Activity Lines, Shipment Lines | Pick creation/re-sequencing | Viable |
| Others | Varies | Often limited or undocumented | Advisory mode |
RIGOR YOU CAN MEASURE.
−0%
Travel distance
−0%
Pick time
+0%
Throughput at same labor
0%
Constraint compliance
Placeholder metrics. Replace with observed facility data when available.
READY TO SEE IT RUN?
Bring one facility. We'll produce an executable plan.