Layer 3 of 3REBUILT v3

Supply Chain Plan

ByteBurger — Single-Location Burger Shop

Plans expire and refresh. Unlike the Model and Framework — which are timeless in structure — this document is time-bound. The numbers, schedules, and thresholds defined here are the initial operating parameters and simulation parameters for ByteBurger's launch phase. They will be updated as actual data replaces assumptions.

This Plan is also the blueprint for the simulation and the software. Every number here becomes a configurable parameter in the system. The simulation will generate realistic demand, consume inventory, trigger reorder points, process orders, and measure KPIs — testing whether the Model → Framework → Plan logic holds under realistic conditions before reality does.

A plan fails not because it misunderstands the domain — that is a Model failure. Not because it uses the wrong organizing logic — that is a Framework failure. It fails because execution falls short of intent: forecast error, supplier failure, capacity constraint, or poor discipline. The simulation exists to find those failures before they cost anything.

The Plan operates within the structure the Framework defines and is grounded in what the Model says about reality. It does not skip layers. Every Plan element references the Framework domain (D-series) that governs it. The Framework's connection to the Model is inherited — it does not need to be re-stated here. This chain is the document's spine and must be preserved in all future edits:

Model (S-series) → Framework (D-series) → Plan (P-series)

This document is the Plan — the third and final layer of ByteBurger's supply chain system.

A plan is a time-bound, quantified sequence of decisions and actions. It does not describe what exists — that is the Model. It does not organize how we govern — that is the Framework. It specifies exactly what ByteBurger will buy, make, store, and serve — in what quantities, from which suppliers, on which days, and at what cost.

The Plan answers one question: "What specifically do we do, and when?"

Document Purpose & Dependency Architecture

This is the Plan — Layer 3 of ByteBurger's supply chain system. It specifies what ByteBurger will buy, make, store, and serve — in what quantities, from which suppliers, on which days, and at what cost. Every number in this document traces to either a supplier constraint, a BOM calculation, or a demand forecast. Nothing is assumed.

CHAIN OF COMMAND:

Each section of this Plan references the Framework (D-series) that governs it. The Framework in turn references the Model (S-series). The Plan does not skip to the Model directly — it relies on the Framework to define execution rules. This chain is non-negotiable and must be preserved in all future edits.

Plan (P-series) → references → Framework (D-series) → references → Model (S-series)

VALIDATION RULE: Before editing any Plan element, confirm which Framework rule (D-series) it follows. The Framework's Model foundation is inherited — it does not need to be re-stated in the Plan.

SectionTitleFramework DomainDepends On
P1Operating ParametersSpans all domainsModel S-series via Framework
P2Demand PlanD1 — Demand ManagementP1
P3Supplier PlanD3 — Sourcing & Supplier ManagementP2
P3.XBOM Cost AnalysisD3 + D4P3 (requires supplier prices to exist first)
P4Inventory PlanD2 — Inventory GovernanceP3 (ROP uses supplier lead time + C5 from P3)
P5Procurement PlanD4 — Procurement & OrderingP3 + P4
P6Logistics PlanD5 — Logistics & ReceivingP3 + P5
P7Production PlanD6 — Operations & TransformationP2 + P4
P8Performance TargetsD7 — Performance & RiskAll sections

DUAL-UNIT SYSTEM: Items are ordered in supplier units and consumed in kitchen units. All dual-unit items carry an explicit conversion factor defined in P1.5. The software applies these conversions in all calculations — procurement uses supplier units, production uses kitchen units.

OPEN ITEMS — ALL RESOLVED:

✅ G3 RESOLVED — Bun packaging unit confirmed with SUP-002: bag of 12, invoiced per bag. 1 bag = 12 pieces. Applied across P1.5, P2.4, P3.1, P4.2.
P1

Operating Parameters

Foundational configuration — feeds every downstream section

Framework: D1 through D7 (spans all domains) — these parameters are the physical and operational reality within which all Framework rules execute.

P1.1 — Shop Configuration

ParameterValueFramework Reference
LocationSingle location — UAE (GCC region)D3 (supplier geography), D5 (logistics)
Operating hours10:00 AM – 12:00 AM (midnight), 7 days/weekD6 (operations scheduling)
Receiving window7:00 AM – 10:00 AM daily. See P6.1 for late delivery protocol.D5.1 (inbound logistics)
Service periodsLunch peak: 12:00–14:00 · Dinner peak: 19:00–22:00 · Off-peak: all other hoursD1 (demand management)
Demand channelsWalk-in (dine-in + takeaway) · Delivery App · Catering / Pre-ordersD1.1
CurrencyAED (UAE Dirham) — all prices and budgets in AEDD4, D7

P1.2 — Capacity Parameters

▸ Counter / Serving capacity measures cashier throughput — transactions per hour (order taking, payment processing, receipt issuing, order handoff). A transaction may be a single water bottle or a full combo. Counter capacity is independent of production capacity. The actual throughput ceiling is determined by whichever production station runs out first, not the counter.

Capacity PointValueConstraint RefBottleneck Risk
Grill12 patties simultaneously · ~60 patties/hour at 5-min cook timeC2aLow at current volume
Fryer2 baskets · ~30 portions/hour at 4-min fry timeC2bFirst to bind as volume grows — primary scaling watch point
Assembly~40 burgers/hour (1.5 min per burger, 1 assembler)C2cModerate
Counter / Serving~50 customer transactions/hour (POS throughput — independent of production)C2dLow at current volume
Freezer1.5 m³ (~300 kg) — monitor when beef + fries orders coincideC1Monitor on combined bulk orders
Refrigerator2.0 m³ — fresh produce + dairyC1Monitor fresh produce accumulation
Dry storage4 shelf-metersC1Low risk
Serving cooler~100 cans/bottles — replenish throughout dayC1Low — managed by staging schedule

P1.3 — Staffing Plan

▸ Morning prep is not a separate shift. Persons A and B arrive at 07:00 for receiving and prep, then continue as the lunch service team when the shop opens at 10:00. Their full working day is 07:00–16:00.

▸ Person G is a defined part-time employee — not a floating resource. Their role is limited to counter and cashier only. They are rostered specifically for both peak windows. Their limited scope makes them easy to onboard and replace.

PersonShift LabelHoursTotal HoursRole
Person ADay shift (prep + lunch)07:00–16:009 hours07:00–10:00: receiving + prep · 10:00–16:00: grill/fryer
Person BDay shift (prep + lunch)07:00–16:009 hours07:00–10:00: receiving + prep · 10:00–16:00: assembly/service
Person CDay shift (lunch only)10:00–16:006 hoursCounter / POS / packaging
Person DEvening shift16:00–00:008 hoursGrill / fryer
Person EEvening shift16:00–00:008 hoursAssembly / service
Person FEvening shift16:00–00:008 hoursCounter / POS / packaging
Person GPart-time peak support12:00–14:00 + 19:00–22:00~5 hoursCounter / cashier only · easily replaceable · no kitchen responsibility

P1.4 — Menu Configuration

Selling prices are owner decisions set here. Food cost % is NOT set here — it is a live calculated output produced in P3.X after supplier prices are defined. Setting food cost % before knowing supplier prices produces an assumption, not a fact.

Menu ItemSelling Price (AED)BOM ReferenceFood Cost %
Classic Burger20Model BOM: Classic BurgerCalculated in P3.X
Classic Combo (Burger + Fries + Drink)32Model BOM: Classic ComboCalculated in P3.X
Fries (individual)10T2 output + MRO-C-007 (fry container)Calculated in P3.X
Soft Drink (individual)5FG-001 or FG-002 — pass-through (T5)Calculated in P3.X
Bottled Water3FG-003 — pass-through (T5)Calculated in P3.X

▸ Food cost % updates automatically when supplier prices change in P3.4. The owner sets the selling price. The software shows the consequence. If food cost % exceeds threshold → D7 investigation triggered.

P1.5 — Unit Convention Master (Dual-Unit System)

This table is the translation layer between the supplier world and the kitchen world. The software stores both units simultaneously and applies conversion factors in all calculations. If this table is wrong, every downstream calculation inherits the error silently.

✅ G3 RESOLVED: Burger bun supplier unit confirmed with SUP-002 — bag of 12. 1 bag = 12 pieces.
ItemSupplier UnitKitchen UnitConversion FactorNotes
Beef Pattykgpiece1 piece = 0.150 kg · 1 kg = 6.67 piecesOrder in kg. Consume in pieces. Software always rounds pieces UP.
Burger Bunbag (12 pieces)piece1 bag = 12 pieces · 1 piece = 0.083 bagOrder in bags. Consume in pieces. Software rounds bags UP.
Lettucekgkg1:1Ordered and consumed by weight
Tomatokgkg1:1Ordered and consumed by weight
Onionkgkg1:1Ordered and consumed by weight
Cheese Slicepack (200 slices)piece1 pack = 200 piecesOrder in packs. Consume in individual slices.
Cooking Oilliterliter1:1Bulk — ordered and consumed by volume
Frozen Frieskgportion1 portion = 0.200 kg · 1 kg = 5 portionsOrder in kg from supplier. Kitchen tracks in portions at fryer.
Saltkgkg1:1Bulk — ordered and consumed by weight
Burger Sauceliterliter1:1Bulk — ordered and consumed by volume
Pickleskgkg1:1Ordered and consumed by weight
Soft Drinkcase (24 cans)can1 case = 24 cansOrder in cases. Serve in cans.
Bottled Watercase (12 bottles)bottle1 case = 12 bottlesOrder in cases. Serve in bottles.
Ketchup Sachetbox (1,000 pcs)piece1 box = 1,000 piecesOrder in boxes.
Mustard Sachetbox (1,000 pcs)piece1 box = 1,000 piecesOrder in boxes.
Mayo Sachetbox (1,000 pcs)piece1 box = 1,000 piecesOrder in boxes.
Wrapping Paperpack (500 sheets)sheet1 pack = 500 sheetsOrder in packs.
Takeaway Bagspack (500 pcs)piece1 pack = 500 piecesOrder in packs.
Fry Containerspack (500 pcs)piece1 pack = 500 piecesOrder in packs.
P2

Demand Plan

Forecasted demand — primary input to all downstream sections

Framework: D1 — Demand Management (D1.1 channel split · D1.2 forecasting · D1.3 real-time monitoring) The demand plan is the upstream input to P3, P4, P5, and P7. If the demand plan is wrong, every downstream section inherits that error.

P1.6 — Labor Cover & Hiring Plan (D8.2)

The roster (P1.3) lists who works. This section makes labor a replenished resource: a minimum-staffing floor per shift, absence cover, and a hiring pipeline.

ShiftMin Staff (floor)RosteredCover Source
Morning 07:00–16:002Persons A, BPerson C early call-in
Mid 10:00–16:00+1Person CCross-trained G
Evening 16:00–00:003Persons D, E, FOn-call / part-time pool
Peak cashier1Person G (12–14, 19–22)A/B or D/E cover register
  • Absence protocol — sick/no-show → call standby list. Falling below a shift floor is a business-continuity event (D7.8 Level 2): reduce menu rather than serve unsafely understaffed.
  • Hiring pipeline — maintain a part-time/standby pool. New-hire lead time = LT19 (2–6 weeks: recruit → visa/sponsorship → food-handler certification per D6.5). Trigger hiring when the standby pool drops below one person per shift.

P2.1 — Weekly Demand Forecast

Initial simulation parameters. System adjusts as actual sales data accumulates. Demand variability: ±30% daily swing around forecast per Model demand profile.

DayWalk-inDelivery AppCateringTotal MealsDemand Level
Sunday4020060Low
Monday4525070Low
Tuesday5025580Medium
Wednesday5530590Medium
Thursday704010120High
Friday804515140High
Saturday754010125High
Weekly Total41522545685Avg: 98 meals/day

▸ Average daily meals = 98. Average daily patties = 74 (98 × 75% menu mix). These are two different numbers serving two different purposes. Never mix them.

P2.2 — Intra-Day Demand Distribution

Service Period% of Daily DemandMeals (Thursday 120)Operational Implication
Morning (10:00–12:00)10%12Light. Prep window. Stations warming up.
Lunch peak (12:00–14:00)35%42Maximum throughput. All stations active. Person G on counter.
Afternoon (14:00–19:00)15%18Moderate. Re-prep for dinner. Restock cooler.
Dinner peak (19:00–22:00)30%36Second major rush. Person G on counter.
Late evening (22:00–00:00)10%12Tapering. Begin end-of-day assessment.

P2.3 — Menu Mix

Menu Item% of MealsMeals/Day (avg 98)Patty Included?Primary Demand Drivers
Classic Combo55%54YesBeef · buns · fries · drinks · all packaging
Classic Burger (alone)20%20YesBeef · buns · wrapping paper
Fries (alone)15%15NoFrozen fries · cooking oil · fry containers
Soft Drink (alone)8%8NoCanned drinks
Bottled Water (alone)2%2NoBottled water
Patty-inclusive meals75%74 pcs avgYesDrives all protein and bun demand calculations

P2.4 — Average Daily Ingredient Demand (Planning Reference Only)

IMPORTANT: These are average figures used for supplier negotiations, budget calculations, and storage sizing. The software does NOT use averages to decide daily staging or production quantities. Daily execution uses demand-level quantities defined in P2.5.

Item CodeItemAvg Daily UsageSupplier UnitKitchen UnitInv. Cat.Avg Weekly Usage
DM-001Beef Patty11.1 kg │ 74 pcskgpiece (÷0.150 kg)I2/I677.7 kg │ 518 pcs
DM-002Burger Bun6.2 bags │ 74 pcsbagpiece (×12/bag)I443.2 bags │ 518 pcs
DM-003Lettuce2.2 kgkgkgI115.4 kg
DM-004Tomato3.0 kgkgkgI121.0 kg
DM-005Cheese Slice74 pcspack (200 slices)pieceI3518 pcs
DM-006Cooking Oil2.1 LliterliterI714.7 L
DM-007Frozen Fries10.4 kg │ 52 portionskgportion (×0.200 kg)I272.8 kg │ 364 portions
DM-008Salt0.1 kgkgkgI70.7 kg
DM-009Burger Sauce1.5 LliterliterI510.5 L
DM-010Onion1.5 kgkgkgI110.5 kg
DM-011Pickles1.1 kgkgkgI57.7 kg
FG-001/002Soft Drinks62 canscase (24 cans)canI8434 cans │ 19 cases
FG-003Bottled Water10 bottlescase (12 bottles)bottleI870 bottles │ 6 cases
FG-004Ketchup Sachet148 pcsbox (1,000)pieceI81,036 pcs
FG-005Mustard Sachet40 pcsbox (1,000)pieceI8280 pcs
FG-006Mayo Sachet40 pcsbox (1,000)pieceI8280 pcs
MRO-C-005Wrapping Paper74 sheetspack (500)sheetI10518 sheets
MRO-C-006Takeaway Bags60 pcspack (500)pieceI10420 pcs
MRO-C-007Fry Containers69 pcspack (500)pieceI10483 pcs

P2.5 — Demand-Level Staging Quantities (Execution Reference)

These quantities drive daily kitchen decisions. The software calculates and prompts the correct row each morning based on that day's demand forecast. All quantities include a 15% operational buffer. Calculations: forecast meals × menu mix % × 1.15.

Demand LevelDaysForecast MealsPatties to StageFries to StageBuns to Stage
LowSun · Mon60–70 meals52–61 pcs (7.8–9.2 kg)7.0–8.1 kg (35–41 portions)52–61 pcs
MediumTue · Wed80–90 meals69–78 pcs (10.4–11.7 kg)9.4–10.5 kg (47–53 portions)69–78 pcs
HighThu · Fri · Sat120–140 meals104–121 pcs (15.6–18.2 kg)14.0–16.3 kg (70–82 portions)104–121 pcs

▸ Calculation basis: patties = forecast × 75% × 1.15. Fries = forecast × 70% × 1.15 × 0.200 kg/portion. Buns = patties (1:1 with patty-inclusive meals). No staging quantity is a fixed number — all are forecast-driven.

P3

Supplier Plan

Sourcing architecture — the foundation for all inventory and procurement logic

Framework: D3 — Sourcing & Supplier Management (D3.1 qualification · D3.2 categorization · D3.3 international · D3.4 contracts · D3.5 performance · D3.6 communication) ARCHITECTURAL NOTE: P3 precedes P4 by design. MOQ, lead time, and delivery schedule are all supplier-defined and must exist here before ROP can be calculated in P4. Supplier categorization follows the Kraljic Matrix logic embedded in D3.2.

P2.6 — Ramadan & Seasonal Demand Adjustment (D1.6)

The standard forecast (P2.1) assumes the normal weekly curve. These periods override it.

PeriodDemand Shift vs NormalPlan Action
Ramadan — daytime (fasting hours)−70% to −90% on daytime tradeSuspend or minimize daytime prep; move staff to evening; shift receiving earlier/later around fasting
Ramadan — post-iftar (sunset to late)Large surge, often above normal dinner peakHeavy evening staffing + pre-prep; consider extended hours
Eid (≈3 days)Holiday peak + catering pre-ordersBuild stock ahead within shelf-life limits; confirm catering volumes early
Cooler season / tourism (Oct–Mar)Volume upliftRaise safety stock and order frequency
Peak summerVolume dipTrim order quantities to limit waste

▸ During Ramadan, reforecast the weekly demand (P2.1) on the Ramadan pattern — do not apply the standard Thu–Sat shape. This is the single largest seasonal reshaping of demand.

P3.1 — Supplier Register

Kraljic Matrix applied via D3.2: suppliers classified by supply risk × profit impact. Protein supply ring-fenced exclusively to SUP-001 and SUP-011 — no cross-category contamination. This is a strategic risk decision, not a convenience.

IDSupplierKraljic CategoryItems SuppliedDelivery Schedule (C5)Lead TimePaymentMOQ
SUP-001Al Jazeera MeatsCritical (Strategic)DM-001 Frozen beef patties — PRIMARY exclusive protein supplierMon · Wed · Fri1–2 daysNet 3011 kg min (≈73 pcs)
SUP-002Fresh Bakery Co.Critical (Bottleneck)DM-002 Burger bunsDaily (7 days)Same dayCOD7 bags/day (≈84 pcs)
SUP-003Green Valley ProduceImportant (Leverage)DM-003 Lettuce · DM-004 Tomato · DM-010 OnionDaily (Mon–Sat)Same dayNet 155 kg per item
SUP-004Gulf DairyImportant (Leverage)DM-005 Cheese slicesTuesday only (standing order 3 packs/600 slices) · Thursday = emergency only1–2 daysNet 151 pack (200 slices)
SUP-005National BeveragesImportant (Leverage)FG-001 FG-002 Soft drinks · FG-003 Bottled waterWeekly (Tuesday)3–5 daysNet 301 case (24 units)
SUP-006Gulf Frozen & Dry GoodsRoutine (Non-critical)DM-007 Frozen fries · DM-006 Cooking oil · DM-008 Salt · DM-009 Burger sauce · DM-011 Pickles · FG-004 FG-005 FG-006 All sachetsWeekly (Wednesday)3–5 daysNet 30Varies — see P3.3
SUP-007Kitchen Supplies LLCRoutine (Non-critical)MRO-C-001→C-008 All consumables including packagingBi-weekly (1st & 15th)2–5 daysNet 30Varies by item
SUP-008Pro Kitchen EquipmentServiceMRO-E series Equipment · MRO-S series Spare partsOn order1–4 weeksPer invoice1 unit
SUP-009CleanTech ServicesServicePest control · Deep cleaningMonthly scheduledN/AMonthly invoiceN/A
SUP-010Waste Management Co.ServiceWaste disposal · Used oil collectionWeekly (Sunday)N/AMonthly invoiceN/A
SUP-011Brazil Beef ExportsImportant (Strategic reserve)DM-001 Frozen beef — international bulk backup. Activated when local price spikes or SUP-001 fails.Monthly shipment6–8 weeks sea freightLC at sight75 kg (500 pcs min)

P3.2 — Supplier Delivery Schedule Matrix (C5)

This matrix is a direct input to P4 ROP calculations. The maximum gap between deliveries determines worst-case exposure for each item.

SupplierSunMonTueWedThuFriSatMax Gap
SUP-001 Beef—✓—✓—✓—3 days (Fri→Mon)
SUP-002 Buns✓✓✓✓✓✓✓1 day (daily)
SUP-003 Produce—✓✓✓✓✓✓2 days (Sat→Mon)
SUP-004 Dairy——✓—Emergency only——Standing order Tuesday only
SUP-005 Beverages——✓————7 days (weekly)
SUP-006 Frozen & Dry———✓———7 days (weekly)
SUP-007 MRO—1st———15th—~14 days (bi-weekly)
SUP-010 Waste✓——————7 days (weekly)

P3.3 — SUP-006 Item-Level MOQ Register

Item CodeItemSupplier UnitMOQKitchen Unit EquivalentSupply Days at MOQ
DM-007Frozen Frieskg25 kg125 portions~2.4 days avg
DM-006Cooking Oilliter20 L20 L~9.5 days — order monthly
DM-008Saltkg5 kg5 kg~50 days — order quarterly
DM-009Burger Sauceliter5 L5 L~3.3 days
DM-011Pickleskg5 kg5 kg~4.5 days
FG-004Ketchup Sachetbox (1,000 pcs)1 box1,000 pieces~6.8 days
FG-005Mustard Sachetbox (1,000 pcs)1 box1,000 pieces~25 days
FG-006Mayo Sachetbox (1,000 pcs)1 box1,000 pieces~25 days

P3.4 — Pricing Schedule

All prices in AED. The software always uses LANDED COST for international sourcing calculations — never the raw supplier price. Using raw price instead of landed cost makes international sourcing appear more attractive than it actually is.

▸ How to read the beef price: SUP-001 charges 16.70 AED per kg. Since 1 patty = 0.150 kg, the cost per patty = 0.150 × 16.70 = 2.51 AED. The ≈2.50/pc figure is the same price expressed in kitchen units for staff visibility. It is not a separate price.

ItemSupplierSupplier UnitUnit Price (AED)Landed Cost (int'l)Valid Until
Beef Patty (local)SUP-001per kg16.70 / kg (≈ 2.51 / pc)N/AQuarterly review
Beef Patty (int'l)SUP-011per kg12.00 / kg (≈ 1.80 / pc)~16.00 / kg landed (≈ 2.40 / pc) — USE THIS for food cost calculationPer shipment
Burger BunSUP-002per bag (12 pcs)9.60 / bag (≈ 0.80 / pc)N/AMonthly review
LettuceSUP-003per kg8.00 / kgN/AWeekly (market price)
TomatoSUP-003per kg5.00 / kgN/AWeekly (market price)
OnionSUP-003per kg3.00 / kgN/AWeekly (market price)
Cheese SliceSUP-004per pack (200 slices)120.00 / pack (0.60 / slice)N/AQuarterly
Frozen FriesSUP-006per kg8.00 / kg (1.60 / portion)N/AQuarterly
Cooking OilSUP-006per liter12.00 / LN/AQuarterly
Burger SauceSUP-006per liter18.00 / LN/AQuarterly
PicklesSUP-006per kg10.00 / kgN/AQuarterly
Ketchup SachetSUP-006per piece0.10 / pcN/AAnnual
Mustard SachetSUP-006per piece0.10 / pcN/AAnnual
Mayo SachetSUP-006per piece0.10 / pcN/AAnnual
Soft Drink (can)SUP-005per can1.20 / canN/AAnnual contract
Bottled WaterSUP-005per bottle0.80 / bottleN/AAnnual contract

P3.X — BOM Cost Analysis (Live Calculated Output)

This section exists because food cost % cannot be calculated before supplier prices are defined. It appears here — after P3.4 — for the first time. The software calculates these values automatically. When supplier prices change in P3.4, this table updates instantly.

Menu ItemBOM Ingredient Cost (AED)Selling Price (AED)Food Cost %Alert Threshold
Classic BurgerBeef: 2.51 · Bun: 0.80 · Lettuce: 0.24 · Tomato: 0.20 · Cheese: 0.60 · Onion: 0.06 · Sauce: 0.27 · Wrapper: 0.05 TOTAL: ~4.73 AED20.0023.7%Alert if > 35%
Classic ComboBurger BOM: 4.73 · Fries (0.200 kg × 8.00): 1.60 · Drink (1 can × 1.20): 1.20 · Fry container: 0.10 · Bag: 0.12 TOTAL: ~7.75 AED32.0024.2%Alert if > 35%
Fries (alone)Fries (0.200 kg × 8.00): 1.60 · Oil (allocated): 0.10 · Fry container: 0.10 TOTAL: ~1.80 AED10.0018.0%Alert if > 30%
Soft Drink (alone)1 can × 1.20 AED TOTAL: 1.20 AED5.0024.0%Alert if > 25%
Bottled Water (alone)1 bottle × 0.80 AED TOTAL: 0.80 AED3.0026.7%Alert if > 25%

▸ These calculations use current supplier prices from P3.4. They are simulation starting values. The software recalculates in real time as prices change.

P3.5 — Supplier Forecast Sharing Schedule (D3.6)

SupplierCategoryForecast TypeFrequencyMethod
SUP-001 MeatsCriticalWeekly demand forecast + 2-week volume outlookEvery Sunday by 5 PMEmail + phone confirmation
SUP-002 BakeryCriticalWeekly volume estimate by day (peak days flagged) + next-day order confirmationEvery Sunday + daily by 3 PMSunday: messaging app · Daily: phone
SUP-003 ProduceImportantMonthly volume estimate by item1st of each monthEmail
SUP-004 DairyImportantMonthly volume estimate1st of each monthEmail
SUP-005 BeveragesImportantWeekly order quantityEvery FridayEmail
SUP-011 Int'l BeefImportantQuarterly order plan with monthly volume breakdown10 weeks before needed stock dateFormal PO

P3.6 — International Sourcing Plan (SUP-011)

ActionTimingResponsibleDocuments / Notes
Place quarterly PO10 weeks before needed stock dateShop managerFormal PO · Incoterm: CIF Dubai · LC at sight payment
Pre-submit customs documents1 week before port arrivalCustoms brokerCommercial invoice · Packing list · CoO · Health cert · Halal cert · HS code · Bill of lading
Weekly shipment trackingEvery Monday from dispatchShop manager / forwarderTrack: dispatch → departure port → arrival port → customs → local delivery ETA
Customs clearanceOn port arrival — allow 1–7 daysCustoms brokerDuties per HS code. All fees included in P3.4 landed cost.
Receive at shop1–2 days post-clearanceMorning prep staffCold-chain inspection ≤ -18°C · GRN · FIFO put-away to I2

P3.7 — Supplier Performance Targets (D3.5)

MetricTargetFrequencyEscalation → feeds D7 / P8
On-Time Delivery Rate≥ 95% per supplierEvery delivery + monthly rollup< 90% in any calendar month → formal supplier review
Quality Acceptance Rate≥ 98% of deliveries pass inspectionEvery delivery3 rejections from one supplier in 30 days → escalate
Order Accuracy≥ 99% match to POEvery deliveryMismatch → GRN discrepancy note + supplier credit tracked
Lead Time ConsistencyActual vs promised within ±1 dayMonthlyConsistent deviation → contract review
Cheese Weekend CoverStock ≥ 220 slices on Friday eveningWeekly check (Friday)Below threshold → emergency order to SUP-004 Thursday delivery
P4

Inventory Plan

Opening stock · ROP · Safety stock · Staging — all sourced from P3

Framework: D2 — Inventory Governance (D2.1 ROP rules · D2.2 staging · D2.3 waste · D2.4 cycle counting · D2.5 SKU classification · D2.6 valuation · D2.7 loss control) TRACEABILITY: Every value traces to a source. Lead times from P3.1. Delivery schedules (C5) from P3.2. MOQs from P3.1/P3.3. Daily usage from P2.4. Nothing assumed.

P3.8 — Utility & Facilities Register (D8.1)

Utilities are critical managed inputs (Model N13/F11/C14). An outage stops refrigeration and production regardless of stock on hand.

UtilityProviderAccount / ContactEst. Monthly Cost (AED)Outage Contingency
PowerDEWAAccount no. + 24h fault hotline2,000–3,500 (AC + refrigeration dominant)Refrigeration is priority load; generator or rapid-response. Outage > 2h → D7.8 Level 3
WaterDEWA(same account)included aboveStored water for cleaning; halt prep if prolonged
Gas / LPGLocal LPG supplierSupplier contact400–700Keep one spare cylinder on hand
Internet / POS connectivityTelecom providerAccount + support line~300Mobile hotspot fallback so POS and platform orders continue

▸ Utility cost is tracked as overhead and flows into margin governance (D2.10). Figures are simulation starting values.

P3.9 — Single-Source Risk & Second-Source Register (D3.7)

Implements the Model substitutability attribute: which items have only one supplier, and the plan to qualify a second.

ItemPrimary SupplierSingle / MultiBackup / 2nd SourceOnboarding Status
BeefSUP-001 (local) + SUP-011 (int'l)MultiDual local + internationalOK
Burger BunsSUP-002SingleQualify a backup bakery (LT19)GAP — priority
ProduceSUP-003SingleLocal wholesale market fallbackPartial
CheeseSUP-004SingleAlternate dairy distributorGAP
BeveragesSUP-005SingleCash-and-carry fallbackOK (commodity)
Frozen / dry / saucesSUP-006SingleAlternate distributorGAP

▸ Single-source criticals (buns, cheese, frozen inputs) are the priority for second-source qualification (LT19). Reviewed under D3.7.

P4.1 — Shelf Life Classification (Category A vs Category B)

Every SKU is tagged with a shelf life category. This tag determines safety stock logic, ordering strategy, and which protection mechanism is primary. The software applies these rules automatically.

CategoryDefinitionPrimary ProtectionSafety Stock LogicItems
Category AShelf life > 14 days · storage risk near zeroOrder more — structural bufferMinimal safety stock (2–3 days) · Emergency triggers are safety net onlyFrozen beef (I2) · Frozen fries · Cooking oil · Cheese · Sachets · Canned drinks · MRO consumables
Category BShelf life < 7 days · waste risk if over-orderedStaging discipline + emergency triggersSafety stock held carefully · Cannot buffer by ordering moreFresh produce (I1) · Burger buns (I4) · Thawed beef (I6) · Prepped working stock (I12)

▸ I6 (thawed beef) is a staging location — not a procurement category. It has no ROP or safety stock. It is governed entirely by the staging schedule in P4.3 and production rules in P7.

P4.2 — Safety Stock Scale

ScaleDefinitionApplied To
MinimalTightest buffer. Category B items. Excess spoils same day or next.I1 (fresh produce) · I4 (buns) · I12 (prepped working stock)
LowSmall buffer. Short shelf life but days available.I3 (cheese — prepped/open packs)
ModerateMeaningful buffer. Category A items with weekly or bi-weekly supply.I2 (frozen) · I10 (MRO consumables)
ComfortableLong shelf life. Category A. Generous buffer — waste risk very low.I5 (sauces/pickles) · I7 (ambient dry) · I8 (resale goods)

P4.3 — ROP Formula

ROP = (Average Daily Usage × Lead Time in Days) + Safety Stock

Lead time = supplier lead time from P3.1. Where delivery schedule (C5/P3.2) creates a gap longer than lead time, the gap is used. Ordering frequency decisions (how often we choose to order) are documented in P5 — they do not change the ROP formula.

P4.4 — Opening Stock, ROP & Order Quantities

Opening stock is always set at or above ROP to ensure simulation starts in a stable, non-triggered state. All quantities in primary kitchen unit. Order quantities are consciously derived from storage capacity, shelf life, demand patterns, and procurement effort — not inherited from supplier defaults.

ItemCatAvg Daily UsageLead TimeMax Delivery Gap (C5)Safety StockROPOpening StockOrder Qty (MOQ)Supplier
Beef PattyI274 pcs (11.1 kg)1–2 days3 days (Fri→Mon)3 days = 222 pcs (33.3 kg)370 pcs (55.5 kg)500 pcs (75 kg)~144 kg (~960 pcs) every 10 days — see P5SUP-001
Burger BunI474 pcsSame day1 day (daily)1 day = 74 pcs148 pcs200 pcsOrder daily ≈7 bags (84 pcs) — bag of 12SUP-002
LettuceI12.2 kgSame day1 day (Mon–Sat)0.5 day = 1.1 kg3.3 kg6 kgPer shelf life — order every 1–2 daysSUP-003
TomatoI13.0 kgSame day1 day (Mon–Sat)0.5 day = 1.5 kg4.5 kg8 kgPer shelf life — order every 2 daysSUP-003
OnionI11.5 kgSame day1 day (Mon–Sat)0.5 day = 0.75 kg2.25 kg5 kgPer Framework D2 shelf life spec — order every 3–4 days (7-day shelf life)SUP-003
Cheese SliceI374 pcs1–2 daysStanding Tue order only5 days = 370 pcs444 pcs700 pcs (3.5 packs)3 packs (600 slices) every TuesdaySUP-004
Cooking OilI72.1 L3–5 days7 days (Wed)7 days = 14.7 L29.4 L40 L20 L monthlySUP-006
Frozen FriesI252 portions (10.4 kg)3–5 days7 days (Wed)3 days = 31.2 kg52 kg80 kg25 kg weeklySUP-006
SaltI70.1 kg3–5 days7 days (Wed)30 days = 3.0 kg3.7 kg5 kg5 kg quarterlySUP-006
Burger SauceI51.5 L3–5 days7 days (Wed)7 days = 10.5 L18.0 L20 L5 L per ROP triggerSUP-006
PicklesI51.1 kg3–5 days7 days (Wed)7 days = 7.7 kg13.2 kg15 kg5 kg per ROP triggerSUP-006
Soft DrinksI862 cans3–5 days7 days (Tue)3 days = 186 cans496 cans864 cans (36 cases)528 cans (22 cases) weeklySUP-005
Bottled WaterI810 bottles3–5 days7 days (Tue)3 days = 30 bottles70 bottles144 bottles (12 cases)Per ROP triggerSUP-005
Ketchup SachetI8148 pcs3–5 days7 days (Wed)7 days = 1,036 pcs1,776 pcs2,000 pcs (2 boxes)1,000 pcs (1 box) per ROPSUP-006
Mustard SachetI840 pcs3–5 days7 days (Wed)7 days = 280 pcs480 pcs1,000 pcs (1 box)1,000 pcs (1 box) per ROPSUP-006
Mayo SachetI840 pcs3–5 days7 days (Wed)7 days = 280 pcs480 pcs1,000 pcs (1 box)1,000 pcs (1 box) per ROPSUP-006
Wrapping PaperI1074 sheets2–5 days14 days (bi-weekly)5 days = 370 sheets592 sheets1,000 sheets (2 packs)500 sheets (1 pack) per ROPSUP-007
Takeaway BagsI1060 pcs2–5 days14 days (bi-weekly)5 days = 300 pcs480 pcs600 pcs500 pcs (1 pack) per ROPSUP-007
Fry ContainersI1069 pcs2–5 days14 days (bi-weekly)5 days = 345 pcs552 pcs800 pcs500 pcs (1 pack) per ROPSUP-007

▸ Soft drinks: opening stock 864 cans. ROP = 496 cans. Days until first reorder = (864-496)÷62 = ~5.9 days. Stock on delivery day = 496-(62×5) = 186 cans = 3-day buffer. System breathes — no Day 1 panic ordering.

▸ Cheese: opening stock 700 pcs covers full week + buffer. Tuesday-only standing order of 600 slices (3 packs). Thursday delivery removed as standing order — retained as emergency only. Friday check: if stock < 220 slices → trigger emergency Thursday delivery.

▸ Beef: ROP and safety stock calculated here. Ordering cycle (every 10 days, ~144 kg) is a P5 procurement decision — documented there, not here.

P4.5 — Daily Staging Schedule

Framework: D2.2 staging rules. Quantities reference P2.5 demand levels — not fixed averages. The software calculates and prompts staging quantities each morning based on that day's forecast demand level.

▸ I2→I6 thaw time is 07:00–07:30 AM during morning prep. Thawing in the morning gives 3 hours before service, maximizes safe usage window, and is controlled by staff already on site. Previous-evening thawing is discontinued.

Staging ActionFrom → ToTimingQuantity LogicRule / Cap
Thaw beef pattiesI2 (Freezer) → I6 (Fridge)07:00–07:30 AM (morning prep — Persons A & B)From P2.5: Low=52–61 · Med=69–78 · High=104–121 pcs. System prompts correct quantity.Hard cap: never thaw > 1.5 days usage for demand level. Over-thawing = waste within 1–3 days.
Prep lettuceI1 (Fridge) → I12 (Prep area)07:00–08:00 AM lunch prep · 16:00 dinner re-prepP2.5 demand level × 50% lunch + 40% dinner + 10% buffer. Discard unused after service.Category B — discard if not used. Never carry overnight.
Prep tomatoesI1 → I1207:00 AM + 16:00 PMSame logic as lettuce.Same rule.
Prep onionsI1 → I1207:00 AM + 16:00 PMSame logic.Same rule.
Count and stage bunsI4 → I12 (Assembly)07:00 AMP2.5 demand level quantity. Verify freshness first — discard stale.Category B. 1–2 day shelf life. Count confirmed before service opens.
Refill sauce dispensersI5 (Fridge) → I1207:00 AMCheck remaining from prior day first. Top up only — do not overfill.Dispenser capacity ~2 L. Top up to full.
Restock serving coolerI8 → CoolerThroughout dayTrigger: cooler drops below 30 units. Refill to 100.Keep cooler at capacity for serving.

P4.6 — SKU Classification Matrix (ABC-XYZ Analysis + Kraljic)

This section applies ABC-XYZ analysis — combining consumption value (ABC) with movement frequency (XYZ) — to determine cycle count priority. Supplier risk classification follows Kraljic Matrix logic documented in P3.1. The software tags each SKU with both classifications and applies the corresponding control rules automatically.

High Movement (daily)Medium Movement (several/week)Low Movement (weekly or less)
High Value (>5 AED/unit)HV/HM: Beef patties (DM-001) Tightest control. Daily counts. Rigorous supplier tracking.HV/MM: Cooking oil · Burger sauce Count every 2–3 days.HV/LM: Expensive critical spare parts Count every 2–3 days despite low movement.
Medium Value (1–5 AED/unit)MV/HM: Buns · Frozen fries · Cheese Count every 2–3 days.MV/MM: Pickles · Soft drinks Weekly counts.MV/LM: Bottled water Weekly counts.
Low Value (<1 AED/unit)LV/HM: Sachets · Wrapping paper · Bags · Fry containers Weekly counts. Higher safety stock acceptable.LV/MM: Cleaning chemicals · Paper towels Monthly counts.LV/LM: Salt · Light bulbs Monthly counts.

P4.7 — Cycle Count Frequency Schedule

ClassificationCount FrequencyRationale
HV/HM (Beef patties)DailyHighest cost + highest movement. Errors cause stockouts or significant financial loss.
HV/LM (Expensive critical spares)Every 2–3 daysHigh value even if rarely used. A missing critical spare stops production entirely.
HV/MM · MV/HM (Oil, sauce, buns, fries, cheese)Every 2–3 daysEither high cost or high movement — errors compound quickly.
MV/MM · LV/HM (Pickles, drinks, sachets, packaging)WeeklyBalanced. Weekly catches discrepancies before they compound.
MV/LM · LV/MM · LV/LM (Water, cleaning, salt)MonthlyLow per-item financial impact.
MRO Equipment (I9)QuarterlyLong-life assets. Physical verification.
MRO Spare Parts (I11) — standardMonthlyMust verify spares are actually on hand.
MRO Spare Parts (I11) — critical high-valueEvery 2–3 daysSame as HV/LM — absence stops production.
P5

Procurement Plan

Order calendar · Budget · Authorization — derived from P3 + P4

Framework: D4 — Procurement & Ordering (D4.1 buying cycle · D4.2 authorization rules · D4.3 records · D4.4 SOPs) D3 decided who supplies and on what terms. D4 executes the buying cycle from need identification to payment. The order calendar is a direct output of combining P3.2 (supplier delivery schedules) with P4.4 (ROP triggers).

P4.8 — Batch/Lot Tracking, FEFO & Recall Procedure (D5.10)

  • Capture — at receiving (P6.4), record batch/lot number and expiry date for perishables (beef, dairy, produce, sauces/pickles).
  • Rotation — FEFO (earliest expiry used first) across stock; FIFO within an open case.
  • Recall procedure — on a supplier or authority alert: identify the affected lot → locate it in I2/I3/I6 stock and the last few days of production → quarantine (I15) → withdraw via F13 → notify the authority → log the event. Target: affected lot located within 1 hour.
  • KPI: Traceability Coverage = 100% for perishables (P8.1).

P5.1 — Ordering Principles

The order calendar is trigger-based — not a rigid daily schedule. Two triggers drive orders:

Trigger 1 — Shelf life forces it: Category B items (lettuce, buns) must be ordered frequently because they cannot be stockpiled.

Trigger 2 — ROP breach: When stock hits ROP, order immediately regardless of day.

▸ Beef ordering cycle: every 10 days · ~144 kg per order (~960 pcs). SUP-001 delivers on their Mon/Wed/Fri schedule — we order on the day that falls closest to our 10-day cycle. This reduces procurement effort from 3 orders/week to ~3 orders/month for our most critical item.

▸ SUP-003 (Produce) ordering is split by item shelf life: Lettuce — order every 1–2 days. Tomato — order every 2 days. Onion — order every 3–4 days (7-day shelf life per Framework D2).

P5.2 — Weekly Order Calendar

DayOrders Placed TodayExpected Deliveries TodayKey Actions
SundaySUP-001: Beef if 10-day cycle falls this week SUP-002: Buns (weekly volume estimate + next-day confirmation) Send weekly forecast to SUP-001 and SUP-002SUP-010: Waste collection SUP-002: Buns (if Sunday arrangement active)Weekly forecast review. Confirm all Monday deliveries. Plan next week demand.
MondaySUP-002: Buns (daily — shelf life forces this) SUP-003: Lettuce (daily) · Tomato (if 2-day cycle due) · Onion (every 3–4 days per D2)SUP-001: Beef (if Monday falls on 10-day cycle) SUP-003: Produce SUP-002: BunsReceive + GRN all Monday deliveries. Verify beef temperature ≤ -18°C.
TuesdaySUP-002: Buns SUP-003: Lettuce · Tomato if due SUP-004: Cheese standing order (3 packs / 600 slices) SUP-005: Beverages — check against ROP (496 cans). Order if at or below.SUP-002: Buns SUP-003: Produce SUP-004: Cheese (standing Tuesday delivery) SUP-005: Beverages (if ordered last week)Receive + GRN. Verify dairy temperature ≤ 4°C. Confirm cheese = 3 packs received.
WednesdaySUP-001: Beef if 10-day cycle falls this week SUP-002: Buns SUP-003: Lettuce · Tomato if due SUP-006: Frozen & Dry — check all items against ROP. Order any at/below threshold.SUP-001: Beef (if Wednesday falls on cycle) SUP-002: Buns SUP-003: Produce SUP-006: Frozen & Dry GoodsBusiest receiving day. Verify freezer space BEFORE SUP-006 frozen delivery. GRN all.
ThursdaySUP-002: Buns SUP-003: Lettuce · Tomato if due Friday prep: verify ALL stock levels for peak weekend. Emergency order any item at risk.SUP-002: Buns SUP-003: ProduceHigh-demand eve. Stock verification critical. Any item below comfortable level — order today. Do not wait for ROP on a Thursday before a Friday peak.
FridaySUP-001: Beef if 10-day cycle falls this week SUP-002: Buns SUP-003: Lettuce · Tomato if dueSUP-001: Beef (if Friday falls on cycle) SUP-002: Buns SUP-003: ProducePeak day. Minimal admin. Receive deliveries quickly. Evening: Friday stock check — report any weekend risk.
SaturdaySUP-002: Buns SUP-003: Lettuce if due Friday cheese check: if stock < 220 slices → emergency SUP-004 orderSUP-002: Buns SUP-003: ProduceWeekly KPI review (P8). Waste report. Supplier performance check. Confirm Sunday orders. Assess weekend waste.

P5.3 — Monthly Procurement Budget

CategorySupplierMonthly Estimate (AED)% of TotalNotes
Proteins (beef — local)SUP-0015,500–6,50030–35%Largest single cost. HV/HM. A-class. 10-day ordering cycle.
Bakery (buns)SUP-0021,800–2,000~10%Daily ordering forced by shelf life.
Produce (vegetables)SUP-0032,000–2,500~12%Variable market pricing. Trigger-based ordering per shelf life.
Dairy (cheese)SUP-0041,300–1,500~7%Tuesday-only standing order. 3 packs/600 slices per week.
Frozen & Dry GoodsSUP-0062,500–3,000~14%Weekly. Consolidated supplier.
BeveragesSUP-0051,500–2,000~9%Weekly ordering. ROP-triggered.
MRO ConsumablesSUP-007800–1,200~5%Bi-weekly.
MRO Equipment & MaintenanceSUP-008 + SUP-009500–1,0003–5%Variable. Service contracts.
TotalAll Suppliers~16,000–19,700 AED100%Target food cost: 30–35% of revenue. Monitor via P3.X.

P5.4 — Authorization Thresholds

Order TypeAmount (AED)AuthorizationProcess
Standing orders (pre-approved daily items: buns, produce)< 500 per orderAuto-approvedWithin standing order parameters. No additional approval.
Routine orders within monthly budget500–3,000Shop managerBudget compliance check. Same-day approval.
Large or budget-exceeding orders> 3,000Owner approvalStrategic alignment check. Prevents overrun.
Emergency ordersAny amountShop manager + written justificationSpeed + accountability. Logged as emergency in D4.3. Reviewed monthly.
P6

Logistics Plan

Receiving schedule · Shipment tracking · Emergency transport

Framework: D5 — Logistics & Receiving (D5.1 local inbound · D5.2 international · D5.3 tracking · D5.4 outbound · D5.5 transport · D5.6 insurance · D5.7 reverse logistics)

P6.1 — Daily Receiving Schedule (07:00–10:00 AM)

The 7–10 AM window is the operational standard. Late delivery protocol is stock-aware — not a blanket refusal rule. Refusing goods when stock is at or below ROP is self-harm, not discipline.

Late Delivery Protocol — Three Scenarios

ScenarioStock PositionActionSupplier Consequence
Late delivery — stock healthyStock well above ROPRefuse delivery. Reschedule.Log as late delivery against D3.5 KPI. Issue formal notification. Counts against on-time rate.
Late delivery — stock at or near ROPStock at ROP or approachingAccept delivery. Do not refuse.Log as late delivery — full documentation. Issue non-conformance notice. Require written explanation within 24 hours.
Late delivery — stock in safety stock or criticalStock in safety stock territoryAccept immediately. No delay.Escalate to urgent non-conformance. Emergency surcharge claim if applicable. Triggers supplier review if 3rd incident this month.

▸ The receiving window exists to protect kitchen operations — not as a punishment mechanism. Whether goods are accepted outside the window depends entirely on stock position. All late deliveries are logged regardless of acceptance decision.

Time SlotExpected Supplier / ItemsInspection StandardPut-Away
07:00–08:00 AMSUP-003 — Fresh produce daily Lettuce · Tomato · OnionFreshness visual check. No wilting, bruising, off-smell. Weigh vs. delivery note.I1 Refrigerator · FIFO · Label with receipt date
08:00–09:00 AMSUP-001 — Beef (Mon/Wed/Fri or 10-day cycle day) SUP-004 — Cheese (Tuesday standing order)Beef: ≤ -18°C frozen. Reject if above -15°C. Cheese: ≤ 4°C. Reject if above 6°C.Beef → I2 Freezer · Cheese → I3 Refrigerator · Both: FIFO · Label receipt + expiry date
09:00–10:00 AMSUP-002 — Buns daily SUP-005 — Beverages (Tuesday) SUP-006 — Frozen & Dry (Wednesday) SUP-007 — MRO (1st & 15th)Buns: freshness, count, no damage. Beverages: seals intact. Frozen goods: ≤ -18°C on delivery. MRO: quantity vs. PO.Buns → I4 · Beverages → I8 + cooler top-up · Frozen → I2 · Dry goods → I7 · MRO → I10/I11

P6.2 — International Shipment Calendar (SUP-011)

ActionTiming (relative to stock need date)ResponsibleDocuments / Notes
Place quarterly POWeek −10Shop managerFormal PO with monthly volume breakdown · CIF Dubai · LC at sight
Pre-submit customs documentsWeek −1 (before port arrival)Customs brokerInvoice · Packing list · CoO · Health cert · Halal cert · HS code · Bill of lading
Weekly trackingEvery Monday from dispatchShop manager / forwarderMilestones: dispatch → departure → arrival → customs → local ETA
Customs clearanceOn port arrival — allow 1–7 daysCustoms brokerDuties per HS code. All fees in P3.4 landed cost.
Receive at shop1–2 days post-clearanceMorning prep staffCold-chain inspection ≤ -18°C · GRN · FIFO to I2

P6.3 — Emergency Transport Triggers

ScenarioTrigger ConditionActionCost Threshold
Beef stockout riskI2 + I6 combined < 74 pcs (1 day) AND next SUP-001 delivery > 1 day awayStaff pickup from SUP-001 warehouse. Manager authorizes.Up to AED 200 — justified vs. ~AED 2,500+ lost sales on peak day
Bun stockoutI4 < remaining today's forecast AND SUP-002 cannot deliverStaff pickup from SUP-002 or pre-identified alternative bakery.Up to AED 100
Critical equipment failureGrill or fryer down · spare not in I11 · SLA not met within 4 hoursEmergency collect from SUP-008 or N6 provider.No upper limit — production is stopped
Cheese weekend gapStock < 220 slices on Friday eveningEmergency order to SUP-004 Thursday emergency delivery.Up to AED 300
P7

Production Plan

Daily schedule · Station assignments · Staging quantities

Framework: D6 — Operations & Transformation (D6.1 production workflow · D6.2 scheduling · D6.3 equipment · D6.4 quality · D6.5 training)

P6.4 — Receiving Inspection, Quarantine & Disposition (D5.9)

Extends P6.1 with the explicit accept / quarantine / reject decision and batch/lot capture. Goods are not usable stock until dispositioned.

CheckStandardFail Action
TemperatureChilled ≤ 4–6°C; frozen ≤ −18°C (reject beef above −15°C)Quarantine (I15) → assess → reject/return (D5.7)
Quantity vs POMatch delivery note and POShort delivery → log, partial accept, claim
Expiry / shelf lifeMinimum remaining life per category (P4.1)Reject if below threshold
Damage / sealsPackaging intactReject damaged units
Compliance docs (F12)Halal cert, invoice, batch/lot presentHold until provided
Batch/lot captureRecord lot + expiry for perishablesFeeds P4.8 / FEFO

▸ Quarantined stock (I15) is segregated and not released until dispositioned (accept / return / destroy). Repeat failures feed supplier performance (P3.7 / D3.5). Receiving Acceptance Rate and Cold-Chain Compliance are tracked in P8.1.

P7.1 — Hour-by-Hour Daily Production Schedule

TimeActivityResponsibleOutput / Standard
07:00–07:30THAW BEEF: Move from I2 (freezer) to I6 (fridge). Quantity from P2.5 demand level for today. System prompts correct quantity. Label with thaw time. 3 hours until service — sufficient for 0.150 kg patties.Persons A & BI6 loaded. Quantity correct for demand level. Temperature log started.
07:30–09:00Receive and GRN all deliveries per P6.1. Prep: chop lettuce, tomatoes, onions (I1→I12) per P2.5 lunch quantities. Count and verify buns (I4→I12). Refill sauce dispensers (I5→I12). Verify I6 thaw progress.Persons A & BAll I12 ready for lunch service. Discrepancies reported immediately.
09:00–10:00Complete lunch prep. Verify all stations: · Grill: I6 patties at arm's reach · Fryer: frozen fries (I2) accessible — correct portion scoop (0.200 kg) in place · Assembly: I12 toppings, buns counted, wrappers loaded · Counter: I8 cooler stocked to 100 · sachets and bags ready · Person G briefed on today's forecast and any special ordersPersons A & B + Person C arrivesAll stations confirmed ready. Shop opens 10:00 AM.
10:00–12:00Light service (~10% daily demand). Cook to order. Monitor pace vs. forecast. Early surge > forecast + 20% by 11:00 → flag to shift lead, consider additional I12 prep.Persons A · B · C~10% daily demand served. Pace tracking active.
12:00–14:00LUNCH PEAK — 35% daily demand. All stations active. Person G on counter — handles transactions, payments, handoffs. Real-time stockout monitoring per D1.3. If actual > forecast + 20% by 12:30 → trigger additional I12 prep immediately.Persons A · B · C + Person G~20–25 meals/hour. No stockouts. Cycle time ≤ 12 min.
14:00–16:00Post-lunch moderate service. Re-prep for dinner: chop additional vegetables (I1→I12) per P2.5 dinner quantities. Recount buns — discard stale. Restock cooler (I8→Cooler). Verify I6 sufficient for dinner forecast — it was thawed this morning, 3+ hours old, check remaining.Persons A · B · CDinner I12 replenished. Cooler restocked. I6 status confirmed.
16:00–16:30Shift handover brief (Persons A/B/C → D/E/F): Yesterday KPIs · current stock levels · any issues · tonight's forecast · delivery schedule tomorrow. Person G departs after lunch peak.All shift staffClean handover. Evening team fully briefed.
16:30–19:00Dinner prep. Stations restocked. Verify I6 — thawed this morning, now ~9 hours old, check condition and quantity. If I6 insufficient for dinner forecast: NOTE — cannot thaw more and have it ready. Escalate to manager immediately.Persons D · E · FDinner stations ready. I6 status logged.
19:00–22:00DINNER PEAK — 30% daily demand. Same protocol as lunch peak. Person G on counter. Monitor delivery app order surge — packaging (I10) may deplete faster than planned on high-delivery nights.Persons D · E · F + Person G~15–20 meals/hour. No stockouts. Cycle time ≤ 12 min.
22:00–23:30Tapering service. End-of-day assessment: · I6 (thawed beef): assess remaining — if within safe window store, if end of window discard. Log waste (D2.3). · I12 chopped produce: assess freshness — store if safe, discard if not. · Cheese, sauces: days remaining — store. · Record all waste: item · quantity · reason · value. Begin kitchen cleanup.Persons D · E · FWaste log completed. Reusable I12 stored. Kitchen cleaning started.
23:30–00:00Final service. Complete cleanup. Verify tomorrow's delivery schedule. Submit any outstanding orders due tonight. Note: beef for tomorrow is already thawing from 07:00 this morning — check I6 status and confirm sufficient for tomorrow's demand level. If I6 depleted: flag to morning team to thaw immediately at 07:00.Persons D · E · FOrders confirmed. Shop secured. Morning team notes left if any.

P7.2 — Station Capacity Utilization at Peak

Both peak scenarios modeled. Binding case: Friday lunch (140 meals × 35% = 49 meals in 2 hours = ~25 meals/hour).

StationConstraintCapacity/HourRequired: Fri LunchRequired: Fri DinnerUtilization (Lunch)Status
GrillC2a60 patties/hr25 patties14 patties42%Comfortable
FryerC2b30 portions/hr18 portions10 portions60%Moderate — first to bind as volume grows
AssemblyC2c40 burgers/hr25 meals14 meals63%Moderate
Counter (transactions)C2d50 transactions/hr25 transactions14 transactions50%Comfortable — Person G covers peak

▸ Friday dinner (30% of 140 = 42 meals in 3 hours = 14 meals/hour) is significantly lighter than Friday lunch. Lunch remains the binding peak case. No station exceeds 65% utilization at current volumes — meaningful headroom exists before production becomes a constraint.

P8

Performance Targets & Simulation Criteria

KPIs · Review calendar · Risk register · Software validation

Framework: D7 — Performance & Risk Management (D7.1 KPIs · D7.2 risk register · D7.3 review cadence · D7.4 expansion readiness)

P8.1 — KPI Targets & Escalation Triggers

KPITargetReview FrequencyData SourceEscalation Trigger
Menu Availability Rate≥ 98%DailyD2 inventory system< 95% for 2 consecutive days
Item Fill Rate≥ 99%DailyD2 + D6< 97% for 3 consecutive days
Order Cycle Time≤ 12 min avgPer order / daily avgD6 production logAverage exceeds 15 min on any day
Quality Compliance≥ 99%DailyD6 quality log< 97% OR any food safety incident — immediate
Waste Rate< 5% of purchased inventory valueWeeklyD2.3 waste log + D2.6 valuation> 7% in any single week
Supplier On-Time Rate≥ 95% per supplierPer delivery + monthlyD3.5 + D5 GRN log< 90% for any supplier in a calendar month
Supplier Quality Rate≥ 98% passing inspectionPer delivery + monthlyD5 receiving log3 rejections from one supplier in 30 days
Forecast Accuracy±15% deviationDaily check + monthly trendD1 forecast vs. actualConsistently ±25%+ for 2 consecutive weeks
Budget AdherenceWithin 5% of monthly budgetMonthlyD4.3 procurement recordsExceeds budget by > 10%
Equipment Uptime (critical)≥ 99% grill · fryer · fridge · freezerDailyD6.3 equipment logAny critical equipment down > 4 hours
Stock Accuracy≥ 98%Per cycle count (P4.7 schedule)D2.4 cycle count records< 95% on any count
Shrinkage Rate< 2% of inventory valueMonthlyD2.7 loss log + D2.6> 3% in any month
Food Cost %Per P3.X targets by menu itemMonthly (live in software)P3.X BOM calculation vs. actual supplier pricesExceeds alert threshold in P3.X
Beef Unit Cost≤ 16.70 AED/kg local · ≤ 16.00 AED/kg landed int'lMonthlyP3.4 pricing vs. actualsThreshold exceeded → supplier review or source mix adjustment

P8.2 — Review Calendar

CadenceWhenParticipantsAgenda
Daily standupEvery morning 09:30 AM (after receiving, before service)Shop manager + shift leadYesterday KPIs · Today forecast · Stockout risks · Delivery issues · Equipment status · Person G scheduling confirmed
Weekly reviewEvery Saturday evening or Sunday morningShop managerWeek KPIs · Waste report · Supplier performance · Forecast accuracy · Next week demand plan · Confirm Sunday orders · Cheese Friday check result
Monthly review1st week of each monthShop manager + ownerSupplier spend vs. budget · Stock accuracy trends · Shrinkage · Contract reviews due · Equipment lifecycle · Price validity check (P3.4) · SKU classification review (P4.6) · Food cost % review (P3.X)
Quarterly review1st week of Jan/Apr/Jul/OctOwner + shop managerSupplier categorization (Kraljic review) · SKU matrix reclassification · Contract renewals · Equipment replacement · Insurance · SUP-011 PO placement · Framework fitness check · Beef source mix review (local vs. int'l)

P8.3 — Risk Register (D7.2)

RiskProbabilityImpactMitigation (Plan Reference)
Critical supplier failure — beef (SUP-001)LowCriticalSUP-011 strategic reserve (P3.1). 3-day safety stock in I2 (P4.4). 10-day ordering cycle reduces frequency of order-cycle exposure. Weekly forecast sharing (P3.5).
Equipment breakdown — grill or fryerMediumCriticalPreventive maintenance schedule (D6.3). Critical spares in I11. 4-hour SLA with SUP-008 (P3.1). HV/LM cycle count every 2–3 days (P4.7).
Refrigeration or freezer failureLowCriticalTemperature alarm. Emergency SLA. Insurance (D5.6). If > 2 hours unresolved: assess all perishables individually per shelf life.
Cheese weekend gapLow (mitigated)ModerateOpening stock 700 pcs + 600-slice Tuesday standing order eliminates structural gap. Friday check ≥ 220 slices (P3.7). Thursday emergency option retained (P6.3).
Demand spike > +30%MediumModerateP2.5 demand-level staging buffers. D1.3 pace tracking. Emergency ordering protocol (P5/P6.3). Person G available for counter surge.
Customs delay — SUP-011MediumModerateOrder 10 weeks ahead (P6.2). Maintain 3-day I2 local buffer. Air freight if delay > 2 weeks.
Staff shortageMediumModerateCross-training (D6.5). Person G role is simple and replaceable. Reduce menu temporarily if below minimum staff.
Food safety incidentLowCriticalQuality checks at receiving (P6.1) and 6 production points (D6.4). FIFO enforced. Temperature monitoring. Recall protocol documented.
Soft drink stock miscalculationVery Low (corrected)LowROP corrected to 496 cans. Opening stock 864 cans. System breathes — ~6 days before first reorder. Category A shelf life logic applied.
Bun packaging unit errorResolvedModerateG3 RESOLVED — SUP-002 confirmed bag of 12 (1 bag = 12 pcs). Conversion locked in P1.5; propagates correctly through P2, P3, P4, P5.

P8.4 — Simulation Success Criteria

The software simulation is validated when ALL criteria below are confirmed operational:

#CriterionTest Method
1All 14 KPIs in P8.1 calculable and displayed from simulated dataRun 30-day simulation. Verify all KPIs output values within expected ranges.
2ROP triggers generate automatic purchase requisitionsSimulate consumption until any item hits ROP. Confirm PR generated with correct supplier, MOQ-compliant quantity, and urgency flag.
3Dual-unit system works without errorsOrder beef in kg. Verify system converts to pieces using 0.150 kg/pc. Verify no rounding errors accumulate over 30 days.
4Demand-level staging works correctlyConfirm P2.5 staging quantities are prompted each morning based on demand level. Verify Low/Medium/High quantities are correctly calculated.
5Thaw timing is correctVerify system prompts beef thaw at 07:00–07:30 AM. Verify quantity matches P2.5 demand level for today — not a fixed average.
6Shelf life categories enforcedCategory B items (lettuce, buns) flag waste at end of service. Category A items use structural buffer logic. No category confusion.
7Waste tracking is automaticExpired items flagged, removed from inventory, logged as waste with item · quantity · reason · value. Waste rate KPI updates.
8Supplier delay scenarios tested3 simulated delays: SUP-001 missed delivery · SUP-006 late delivery · SUP-011 customs delay. Verify correct scenario (P6.1 protocol) fires for each.
9Financial tracking accuratePO costs, FIFO inventory valuation, and budget vs. actual calculated correctly. Food cost % in P3.X updates when supplier prices change.
10External data inputs receivableArchitecture accepts real-time data feeds (inventory levels, supplier prices, demand signals) via API. Simulation switches between internal and live data without architecture change.
11Late delivery protocol fires correctlySimulate a late delivery. Verify system checks stock position before recommending refuse vs. accept. Verify KPI logged regardless of outcome.
12ABC-XYZ + Kraljic tags appliedEvery SKU tagged with both classifications. Cycle count schedule (P4.7) applied automatically per tag. No manual override needed.

Plan Summary

This Plan defines what ByteBurger will specifically do, in what quantities, and when. Every number traces to a source. Nothing is assumed.

ElementFinal Decision
ArchitectureP3 before P4. Food cost % moves to P3.X. Full D-series chain in every section header.
Staffing7 defined people. Persons A+B: 07:00–16:00. Person C: 10:00–16:00. D/E/F: 16:00–00:00. Person G: part-time peak cashier 12:00–14:00 + 19:00–22:00.
Unit systemDual-unit. Beef: order kg, consume pieces (1 pc = 0.150 kg). Fries: order kg, consume portions (1 portion = 0.200 kg). Cheese: order packs (200 slices). Bun: order bags of 12, consume pieces (1 bag = 12 pcs).
Demand planningAverage (98 meals/day, 74 patties/day) = planning reference only. Execution uses P2.5 demand-level quantities (Low/Med/High). Never mix the two.
Beef thawing07:00–07:30 AM daily. Quantity = next demand level forecast + 15% buffer (from P2.5). System prompts automatically. Previous-evening thawing discontinued.
Beef orderingEvery 10 days · ~144 kg per order. Reduces procurement effort from 3 orders/week to ~3/month. Freezer capacity confirmed safe (144 kg beef + 80 kg fries = 224 kg < 300 kg capacity).
CheeseTuesday-only standing order: 3 packs (600 slices). Thursday removed as standing order. Friday check: if < 220 slices → emergency Thursday delivery. Opening stock 700 pcs.
Soft drinksROP corrected to 496 cans. Opening stock 864 cans (36 cases). First reorder at ~Day 6. 3-day buffer on delivery day. Category A shelf life logic applied.
Receiving protocolStock-aware. Three scenarios: healthy stock → refuse late delivery · at/near ROP → accept + log · in safety stock → accept immediately + escalate. All late deliveries logged against D3.5.
Produce orderingTrigger-based by shelf life. Lettuce: every 1–2 days. Tomato: every 2 days. Onion: every 3–4 days (7-day shelf life — G2 resolved).
SKU classificationABC-XYZ analysis named explicitly. Kraljic Matrix named in P3.1. Software tags every SKU with both. HV/LM added to P4.7 cycle count schedule.
Reality-layer additions (NEW)Labor cover & hiring (P1.6) · Ramadan/seasonal demand (P2.6) · Utilities register (P3.8) · Single-source register (P3.9) · Batch/lot, FEFO & recall (P4.8) · Receiving inspection & quarantine (P6.4). Trace to Model Reality Layer and Framework D1.6/D2.10/D5.8–10/D8.
Open items before software lockG3: RESOLVED — bun packaging confirmed with SUP-002 (bag of 12). G1/G2: RESOLVED — Model + Framework fresh produce range updated (1–10 days) + onion shelf life specified (7 days).
Status: REBUILT v3 — Extended to the Model Reality Layer (cost, cold chain, receiving/traceability, utilities, workforce, seasonal demand) · Traceable · Ready for review

All open items resolved (G1 · G2 · G3) — ready for final software lock.