Sample checks
Compliance / Compositional Compliance Presence
Verify every tray, item and temperature before it reaches the aircraft.
An on-ground visual compliance presence that validates composition against the live flight plan, alerts operators immediately and preserves evidence for every exception.
See how it works07 / 09
01
The operational shift
Tray-type models
Configurable item rules
Cloud dependency
On-ground decisions
Presence in the workflow
Every tray receives the same compositional check.
Compliance / Compositional Compliance Presence02
What this presence does
Item composition
Checks expected items, counts and approved variants against the flight-specific tray configuration.
Placement validation
Normalises the tray view and verifies configurable item zones and placement tolerances.
Temperature assurance
Associates thermal readings with the relevant item and merges them into one verdict.
Immediate intervention
Shows an annotated failure, audible alert and clear reason at the belt within the decision window.
Flight reconciliation
Compares validated counts with the belt plan and produces a completion report.
Config Studio
Onboards a new tray using a golden image and item configuration—without a new tray-specific model.
Validate every tray against the flight-specific configuration in the belt plan, never a generic tray type. Check item presence, count, approved variant and placement zone, and merge each item's thermal reading into one verdict. Show pass or fail at the belt within the decision window, with the failing item annotated and the reason stated. Keep judging locally if the WAN drops and queue evidence for sync. Log model version, config version and operator response with every exception. Fail any unrecognised tray; never pass it.
From the presence brief
03
How Ananta achieves it
One intelligence loop.
Built around the work.
- 01
Plan
Load flight, belt and candidate tray configurations from the operational plan.
- 02
Detect
Select the best frames and identify the stable vocabulary of physical items.
- 03
Validate
Apply counts, attributes, placement zones and thermal thresholds.
- 04
Intervene
Render the verdict locally and alert the operator even during WAN loss.
- 05
Trace
Sync evidence, model version, config version and operator actions to the audit plane.
04
Deployment architecture
Ananta Presence Runtime
Connect the physical environment to enterprise action.
On-ground plane
Optical + thermal cameras · NVR · Edge GPU · Local alerts · Evidence buffer
Management plane
Belt plans · Tray Config Studio · Alerts · Reports · Model registry
AI composition
Item detector · Attribute matcher · Zone engine · Thermal merge · Exception referee
Enterprise integration
Flight plan · Service bus · Evidence store · SSO/RBAC · Audit
05
Prove the value
Measure what changes.
- Anomaly detection accuracy
- Verdict latency
- Trays validated
- Exception closure
- New tray onboarding time
06
Enterprise controls
Governed from the start.
- On-ground inferenceIncluded
- Offline continuityIncluded
- Model/config versioningIncluded
- Evidence under enterprise controlIncluded
07
Boundaries by design
- Never stops the belt or releases a cart; the line operator clears every exception.
- Does not identify or rate individual workers; cameras see the tray, not the person.
- Only validates against the approved configuration; it does not certify ingredients, allergens or halal status.
- Does not hold passenger names or seat numbers; only flight, meal codes and counts.
08
Before you buy
Deployment questions.
What hardware goes on the tray line?
One optical and one thermal camera over each belt checkpoint, an NVR and an edge GPU in a rack near the line, and a screen with an audible alert at the belt. Nothing is fitted to trays or carts.
Who approves a hold or a release?
The line operator, every time. The presence shows pass or fail with the reason on screen; the operator corrects the tray, overrides with a logged reason, or escalates to the quality supervisor.
Where is tray evidence stored, and for how long?
Frames, verdicts and thermal readings stay on the on-ground NVR and evidence buffer, then sync to an evidence store in the caterer's own tenancy. Default retention is 30 days for passes and 12 months for exceptions; the caterer sets both.
How does an operator take over?
A line operator pauses validation at the checkpoint screen and switches the belt to manual check, and the log marks every tray from that point as operator-cleared. If the WAN drops, verdicts keep rendering locally and evidence queues until the link returns.
What does a 90-day pilot cover?
One belt and one airline's tray set, with cameras and edge box installed by week two. Weeks three to six run shadow mode beside your sample checks; weeks seven to twelve run live alerts, with accuracy and verdict latency reported weekly against the agreed threshold.
How are outcomes counted?
Every tray gets a verdict record, so counts are exact: trays validated, exceptions raised, exceptions closed before cart seal, and flights reconciled against the belt plan. The report scores accuracy against operator-confirmed outcomes, not the model's own confidence.
Food & Aviation Catering