Discovery-to-prototype architecture
Supply Resilience, Production Visibility & Operational Accountability
Capital Catering does not need another ERP. It needs an intelligence and accountability layer that reads from the platforms it already owns, creates one operational truth, detects variance, and turns exceptions into owned actions — across 20+ locations and all seven Emirates. Prepared for Areef Mohammed Ismail, Supply Chain Manager. Operating cycle Friday, 21 August 2026.
IOTx is an overlay architecture: existing applications continue to transact; IOTx interprets, connects, measures and coordinates. ERP = record · IOTx = intelligence + accountability.
Every step writes events → measures expected versus actual → triggers accountable action.
Every finding below is addressed by a working surface in this prototype.
Task ownership and status are not visible without asking
Evidence: 70% of staff time spent chasing updates and making status calls
IOTx: IOB flow engine assigns owner, backup owner and SLA to every task
Decision numbers are manually assembled from multiple sources
Evidence: Management spends ~20 hours per month preparing reports
IOTx: Canonical operational data model plus GLASS visibility dashboards
The same information is re-entered across disconnected tools
Evidence: Attendance re-keyed across Sheets, WhatsApp, ERP and paper
IOTx: Signal capture connectors with source, timestamp and confidence
Work execution is coordinated informally and re-planned during the day
Evidence: Mid-day replans driven by WhatsApp and verbal handoffs
IOTx: Versioned production plan with mandatory change reason and approver
Operational completion and billing are loosely connected
Evidence: Delivered work sits unbilled; disputes surface weeks later
IOTx: Completion-to-invoice reconciliation on the same evidence chain
Scheduling depends heavily on one person's spreadsheet
Evidence: Planner absence causes disrupted work plans and customer embarrassment
IOTx: Shared planning workspace with named backup owner and audit trail
Ward attendance and diet data reaches the kitchen late
Evidence: Final attendance and diet data changes at the last minute
IOTx: Demand lock windows, freshness scoring and change-impact analysis
Wrong data and miscommunication create meal-count errors
Evidence: ~20% of orders require rework or correction
IOTx: Expected-vs-actual engine with root-cause tagging
Approximately 500 productive hours are lost per week
Evidence: Coordination overhead across 500+ employees and 20+ locations
IOTx: Exception-based management replaces status chasing
Approximately 20% of deliveries are late
Evidence: Loads not ready by cut-off; site confirmation missing
IOTx: Dispatch readiness board and route risk with acknowledgement SLA
Stock accuracy is patchy
Evidence: Inventory confidence below 60% on several materials
IOTx: Inventory intelligence overlay with confidence and freshness per metric
Supplier delays affect production weekly
Evidence: PO ETA slips hit locked plans at Dubai and Al Ain
IOTx: Supplier disruption rule links PO events to affected plans and sites
Finance and cash visibility are delayed
Evidence: Finance view is monthly; disputes discovered late
IOTx: Completion-to-billing gap rule with receivables ageing