ARMADA application
PilotKitchen Display
Kitchen Display covers receiving, ordering, and updating restaurant preparation work, with explicit device, station, integration, and interruption scope.
Kitchen operating scope
Contract-based preview — not connected to live data
Kitchen Display
Outcomes
What changes in your operation?
Understandable ticket states
Visible exceptions instead of hidden failures
Operating journey
From start to outcome
- 1
Receive
Show preparation items at the relevant station.
- 2
Prepare
Let an authorised team member update the state.
- 3
Complete
Send a clear state to the hand-off point.
Application scope
Core capabilities
A practical scope that explains what this application covers and where its current boundary sits.
Understandable preparation queue
Show order items at the relevant station and organise the kitchen team's work.
- Defined preparation station
- Visible state for every ticket
Authorised state updates
Move a ticket through received, preparing, and complete using the responsible role.
- Clear responsibility
- Understandable hand-off
Exceptions do not disappear
Keep delayed or unsynchronised work visible under the agreed review path.
- No silent completion
- A state that needs a decision
Control and governance
How does the work stay controlled?
Operating controls that preserve context, permission, and a reviewable trail.
Station assignment
The operating configuration defines which items reach each station and device.
Role-based updates
Preparation state changes only through an authorised action in the correct context.
Tested interruption scenario
Connectivity and interruption cases follow the accepted operating path.
One shared core
How does it connect to other applications?
Intended connections to the shared ARMADA core. Only the integrations covered by the approved scope are enabled.
Kitchen DisplayKitchen operating scope
Point of Sale
Receives included orders through the accepted point-of-sale journey.
Inventory
Ingredient and movement effects are assessed in the approved restaurant scope; no automatic link is assumed.
Reports
Preparation states provide operating sources for approved measure definitions.
Implementation approach
From operating study to acceptance
A practical sequence that starts with the real operation and ends with clear acceptance of the agreed scope.
- 1
Map kitchen stations
Define stations, devices, and the order path from checkout to hand-off.
Clear distribution of work - 2
Validate one controlled shift
Run normal and exception tickets with the responsible team.
Evidence from the real kitchen - 3
Accept operating states
Confirm states, alerts, and interruption behaviour before expansion.
A measurable operating scope
Designed for
Fits different teams and operating models
RestaurantsCafesCentral kitchens
Before you decide
Common questions about this application
How is the Kitchen Display scope defined?
The scope follows each restaurant's stations, devices, order journey, and connectivity scenarios.
How does an order reach the right station?
Item-to-station distribution is fixed in the operating setup and matched to the restaurant's menu and kitchen.
What happens when connectivity is lost?
Each operating scope adopts explicit behaviour; an unresolved state remains visible for review and is not treated as complete.