Layer 3 of 3REBUILT v2

Supply Chain Plan

The time-bound, quantified operating parameters (P1–P8): what ByteBurger buys, makes, stores, and serves — in what quantities, from which suppliers, on which days, and at what cost. Every Plan element references the Framework domain (D-series) that governs it.

Dependency Architecture

The Plan operates within the Framework and is grounded in the Model. It does not skip layers — every number traces to a supplier constraint, a BOM calculation, or a demand forecast.

Chain of command (non-negotiable): Plan (P-series) → references → Framework (D-series) → references → Model (S-series). Before editing any Plan element, confirm which Framework rule governs it.
SectionTitleFramework DomainDepends On
P1Operating ParametersSpans all domainsModel S-series via Framework
P2Demand PlanD1 — Demand ManagementP1
P3Supplier PlanD3 — Sourcing & Supplier MgmtP2
P3.XBOM Cost AnalysisD3 + D4P3 (needs supplier prices first)
P4Inventory PlanD2 — Inventory GovernanceP3 (ROP uses lead time + C5)
P5Procurement PlanD4 — Procurement & OrderingP3 + P4
P6Logistics PlanD5 — Logistics & ReceivingP3 + P5
P7Production PlanD6 — Operations & TransformationP2 + P4
P8Performance TargetsD7 — Performance & RiskAll sections

Plans expire and refresh. Unlike the timeless Model and Framework, this document is time-bound — the numbers, schedules, and thresholds here are the initial operating and simulation parameters for ByteBurger's launch phase, updated as actual data replaces assumptions. Open items G1, G2, and G3 are all resolved.

P1

Operating Parameters

Foundational configuration — the physical and operational reality within which all Framework rules execute

Framework: D1–D7 (spans all domains). Feeds every downstream section.

P1.1 — Shop Configuration

ParameterValueFramework Ref
LocationSingle location — UAE (GCC region)D3, D5
Operating hours10:00 AM – 12:00 AM (midnight), 7 days/weekD6
Receiving window7:00 AM – 10:00 AM daily (late protocol: P6.1)D5.1
Service periodsLunch 12:00–14:00 · Dinner 19:00–22:00 · Off-peak otherwiseD1
Demand channelsWalk-in (dine-in + takeaway) · Delivery App · Catering / Pre-ordersD1.1
CurrencyAED (UAE Dirham)D4, D7

P1.2 — Capacity Parameters

Capacity PointValueRefBottleneck Risk
Grill12 patties simultaneously · ~60/hour at 5-min cookC2aLow at current volume
Fryer2 baskets · ~30 portions/hour at 4-min fryC2bFirst to bind as volume grows
Assembly~40 burgers/hour (1 assembler)C2cModerate
Counter / Serving~50 transactions/hour (POS — independent of production)C2dLow at current volume
Freezer1.5 m³ (~300 kg)C1Monitor on combined bulk orders
Refrigerator2.0 m³ — fresh produce + dairyC1Monitor produce accumulation
Dry storage4 shelf-metersC1Low risk
Serving cooler~100 cans/bottlesC1Low — managed by staging

P1.3 — Staffing Plan

7 defined people. Persons A & B arrive at 07:00 for receiving and prep, then continue as the lunch team. Person G is a defined part-time cashier rostered for both peak windows — limited scope, easy to replace.

PersonShiftHoursRole
Person ADay (prep + lunch)07:00–16:00 (9h)07:00–10:00 receiving + prep · 10:00–16:00 grill/fryer
Person BDay (prep + lunch)07:00–16:00 (9h)07:00–10:00 receiving + prep · 10:00–16:00 assembly/service
Person CDay (lunch only)10:00–16:00 (6h)Counter / POS / packaging
Person DEvening16:00–00:00 (8h)Grill / fryer
Person EEvening16:00–00:00 (8h)Assembly / service
Person FEvening16:00–00:00 (8h)Counter / POS / packaging
Person GPart-time peak12:00–14:00 + 19:00–22:00 (~5h)Counter / cashier only · easily replaceable

P1.4 — Menu Configuration

Selling prices are owner decisions. Food cost % is NOT set here — it is a live calculated output produced in P3.X after supplier prices are defined.

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

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

The translation layer between the supplier world and the kitchen world. Items are ordered in supplier units and consumed in kitchen units. If this table is wrong, every downstream calculation inherits the error silently.

ItemSupplier UnitKitchen UnitConversion
Beef Pattykgpiece1 pc = 0.150 kg · 1 kg = 6.67 pcs
Burger Bunbag (12 pieces)piece1 bag = 12 pcs (G3 resolved)
Lettuce / Tomato / Onionkgkg1:1 by weight
Cheese Slicepack (200 slices)piece1 pack = 200 slices
Cooking Oil / Sauceliterliter1:1 by volume
Frozen Frieskgportion1 portion = 0.200 kg · 1 kg = 5 portions
Soft Drinkcase (24 cans)can1 case = 24 cans
Bottled Watercase (12 bottles)bottle1 case = 12 bottles
Sachets (ketchup/mustard/mayo)box (1,000 pcs)piece1 box = 1,000 pcs
Wrapping / Bags / Fry Containerspack (500)sheet/piece1 pack = 500
P2

Demand Plan

Forecasted demand — the upstream input to P3, P4, P5, and P7. If the demand plan is wrong, every downstream section inherits the error

Framework: D1 — Demand Management (D1.1 channels · D1.2 forecasting · D1.3 real-time monitoring). Demand variability: ±30% daily swing per Model demand profile.

P2.1 — Weekly Demand Forecast

DayWalk-inDeliveryCateringTotalLevel
Sunday4020060Low
Monday4525070Low
Tuesday5025580Medium
Wednesday5530590Medium
Thursday704010120High
Friday804515140High
Saturday754010125High
Weekly Total41522545685Avg 98/day
Average daily meals = 98. Average daily patties = 74 (98 × 75% menu mix). Two different numbers for two different purposes — never mix them.

P2.2 — Intra-Day Demand Distribution

Service Period% of DayMeals (Thu 120)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. End-of-day assessment.

P2.3 — Menu Mix

Menu Item% of MealsMeals/Day (avg 98)Patty?
Classic Combo55%54Yes
Classic Burger (alone)20%20Yes
Fries (alone)15%15No
Soft Drink (alone)8%8No
Bottled Water (alone)2%2No
Patty-inclusive meals75%74 pcs avgYes — drives protein/bun demand

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

Average figures for supplier negotiations, budgets, and storage sizing. The software does NOT use averages for daily staging — execution uses P2.5 demand-level quantities.

ItemAvg Daily UsageInv. CatAvg Weekly
Beef Patty11.1 kg │ 74 pcsI2/I677.7 kg │ 518 pcs
Burger Bun6.2 bags │ 74 pcsI443.2 bags │ 518 pcs
Lettuce2.2 kgI115.4 kg
Tomato3.0 kgI121.0 kg
Onion1.5 kgI110.5 kg
Cheese Slice74 pcsI3518 pcs
Cooking Oil2.1 LI714.7 L
Frozen Fries10.4 kg │ 52 portionsI272.8 kg │ 364 portions
Burger Sauce1.5 LI510.5 L
Pickles1.1 kgI57.7 kg
Soft Drinks62 cansI8434 cans │ 19 cases
Bottled Water10 bottlesI870 bottles │ 6 cases

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

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

Demand LevelDaysForecastPattiesFriesBuns
LowSun · Mon60–7052–61 pcs (7.8–9.2 kg)7.0–8.1 kg (35–41 port.)52–61 pcs
MediumTue · Wed80–9069–78 pcs (10.4–11.7 kg)9.4–10.5 kg (47–53 port.)69–78 pcs
HighThu · Fri · Sat120–140104–121 pcs (15.6–18.2 kg)14.0–16.3 kg (70–82 port.)104–121 pcs
P3

Supplier Plan

Sourcing architecture — the foundation for all inventory and procurement logic. P3 precedes P4 by design: MOQ, lead time, and delivery schedule must exist before ROP can be calculated

Framework: D3 — Sourcing & Supplier Management. Supplier categorization follows the Kraljic Matrix. Protein supply is ring-fenced exclusively to SUP-001 and SUP-011 — a strategic risk decision.

P3.1 — Supplier Register

IDSupplierKraljicItemsScheduleLeadPaymentMOQ
SUP-001Al Jazeera MeatsCritical (Strategic)Frozen beef — primary proteinMon·Wed·Fri1–2dNet 3011 kg (~73 pcs)
SUP-002Fresh Bakery Co.Critical (Bottleneck)Burger bunsDailySame dayCOD7 bags/day
SUP-003Green Valley ProduceImportant (Leverage)Lettuce · Tomato · OnionDaily (Mon–Sat)Same dayNet 155 kg/item
SUP-004Gulf DairyImportant (Leverage)Cheese slicesTuesday only1–2dNet 151 pack
SUP-005National BeveragesImportant (Leverage)Soft drinks · WaterWeekly (Tue)3–5dNet 301 case
SUP-006Gulf Frozen & DryRoutineFries · Oil · Salt · Sauce · Pickles · SachetsWeekly (Wed)3–5dNet 30See P3.3
SUP-007Kitchen Supplies LLCRoutineAll consumables / packagingBi-weekly2–5dNet 30Varies
SUP-008Pro Kitchen EquipmentServiceEquipment · Spare partsOn order1–4 wkPer invoice1 unit
SUP-009CleanTech ServicesServicePest control · Deep cleaningMonthlyN/AMonthlyN/A
SUP-010Waste Management Co.ServiceWaste · Used oil collectionWeekly (Sun)N/AMonthlyN/A
SUP-011Brazil Beef ExportsImportant (Strategic reserve)Frozen beef — int'l backupMonthly6–8 wk seaLC at sight75 kg (500 pcs)

P3.2 — Supplier Delivery Schedule Matrix (C5)

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

SupplierSunMonTueWedThuFriSatMax Gap
SUP-001 Beef3 days (Fri→Mon)
SUP-002 Buns1 day (daily)
SUP-003 Produce2 days (Sat→Mon)
SUP-004 DairyEmerg.Tue standing order
SUP-005 Beverages7 days (weekly)
SUP-006 Frozen/Dry7 days (weekly)
SUP-007 MRO1st15th~14 days (bi-weekly)
SUP-010 Waste7 days (weekly)

P3.4 — Pricing Schedule

All prices in AED. The software always uses LANDED COST for international sourcing — never the raw supplier price. Beef: SUP-001 charges 16.70/kg; at 0.150 kg/patty = 2.51/pc.

ItemSupplierUnit Price (AED)Landed (int'l)
Beef Patty (local)SUP-00116.70 / kg (≈2.51 / pc)N/A
Beef Patty (int'l)SUP-01112.00 / kg (≈1.80 / pc)~16.00 / kg landed — use this
Burger BunSUP-0029.60 / bag (≈0.80 / pc)N/A
LettuceSUP-0038.00 / kgN/A
TomatoSUP-0035.00 / kgN/A
OnionSUP-0033.00 / kgN/A
Cheese SliceSUP-004120.00 / pack (0.60 / slice)N/A
Frozen FriesSUP-0068.00 / kg (1.60 / portion)N/A
Cooking OilSUP-00612.00 / LN/A
Burger SauceSUP-00618.00 / LN/A
Soft Drink (can)SUP-0051.20 / canN/A
Bottled WaterSUP-0050.80 / bottleN/A

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

Food cost % cannot be calculated before supplier prices are defined — so it appears here, after P3.4. The software recalculates instantly when prices change.

Menu ItemBOM Cost (AED)PriceFood Cost %Alert
Classic Burger~4.73 (beef 2.51 · bun 0.80 · veg/cheese/sauce/wrap)20.0023.7%> 35%
Classic Combo~7.75 (burger 4.73 · fries 1.60 · drink 1.20 · pkg 0.22)32.0024.2%> 35%
Fries (alone)~1.80 (fries 1.60 · oil 0.10 · container 0.10)10.0018.0%> 30%
Soft Drink (alone)1.20 (1 can)5.0024.0%> 25%
Bottled Water (alone)0.80 (1 bottle)3.0026.7%> 25%

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

SupplierForecast TypeFrequencyMethod
SUP-001 MeatsWeekly forecast + 2-week outlookSunday by 5 PMEmail + phone
SUP-002 BakeryWeekly volume + next-day confirmationSunday + daily by 3 PMApp + phone
SUP-003 ProduceMonthly volume by item1st of monthEmail
SUP-004 DairyMonthly volume estimate1st of monthEmail
SUP-005 BeveragesWeekly order quantityEvery FridayEmail
SUP-011 Int'l BeefQuarterly plan + monthly breakdown10 wks before stock dateFormal PO

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

ActionTimingResponsibleNotes
Place quarterly PO10 weeks before needShop managerCIF Dubai · LC at sight
Pre-submit customs docs1 week before arrivalCustoms brokerInvoice · CoO · Health + Halal cert · HS code · B/L
Weekly shipment trackingEvery Monday from dispatchManager / forwarderDispatch → port → customs → ETA
Customs clearanceOn arrival — allow 1–7 daysCustoms brokerDuties per HS code (in landed cost)
Receive at shop1–2 days post-clearanceMorning prep staff≤ -18°C · GRN · FIFO to I2

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

MetricTargetEscalation → P8
On-Time Delivery Rate≥ 95% per supplier< 90% in a month → formal review
Quality Acceptance Rate≥ 98% pass inspection3 rejections / 30 days → escalate
Order Accuracy≥ 99% match to POMismatch → GRN note + credit tracked
Lead Time ConsistencyWithin ±1 dayConsistent deviation → contract review
Cheese Weekend Cover≥ 220 slices Friday eveBelow → emergency Thursday order
P4

Inventory Plan

Opening stock · ROP · Safety stock · Staging — every value traces to a source. Lead times from P3.1, delivery schedules from P3.2, MOQs from P3.1/P3.3, usage from P2.4

Framework: D2 — Inventory Governance. ROP = (Average Daily Usage × Lead Time in Days) + Safety Stock. Where the C5 delivery gap exceeds lead time, the gap is used.

P4.1 — Shelf Life Classification

CategoryDefinitionPrimary ProtectionItems
Category AShelf life > 14 days · storage risk near zeroOrder more — structural buffer (2–3 day SS)Frozen beef · fries · oil · cheese · sachets · cans · MRO
Category BShelf life < 7 days · waste risk if over-orderedStaging discipline + emergency triggersFresh produce · buns · thawed beef · working stock

P4.2 — Safety Stock Scale

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

P4.4 — Opening Stock, ROP & Order Quantities

Opening stock is set at or above ROP so the simulation starts stable and non-triggered. Order quantities derive from storage, shelf life, and demand — not supplier defaults.

ItemCatDaily UsageLead/GapSafety StockROPOpeningOrder Qty
Beef PattyI274 pcs3d gap222 pcs (33.3 kg)370 pcs500 pcs (75 kg)~144 kg / 10 days (P5)
Burger BunI474 pcsSame day74 pcs148 pcs200 pcsDaily ~7 bags
LettuceI12.2 kgSame day1.1 kg3.3 kg6 kgEvery 1–2 days
TomatoI13.0 kgSame day1.5 kg4.5 kg8 kgEvery 2 days
OnionI11.5 kgSame day0.75 kg2.25 kg5 kgEvery 3–4 days
Cheese SliceI374 pcsTue only370 pcs444 pcs700 pcs3 packs Tuesday
Cooking OilI72.1 L7d gap14.7 L29.4 L40 L20 L monthly
Frozen FriesI252 port.7d gap31.2 kg52 kg80 kg25 kg weekly
Burger SauceI51.5 L7d gap10.5 L18.0 L20 L5 L per ROP
Soft DrinksI862 cans7d gap186 cans496 cans864 cans528 cans weekly
Ketchup SachetI8148 pcs7d gap1,036 pcs1,776 pcs2,000 pcs1 box per ROP
Wrapping PaperI1074 sheets14d gap370 sheets592 sheets1,000 sheets1 pack per ROP
Soft drinks: opening 864 cans, ROP 496, first reorder ~Day 6, 3-day buffer on delivery day — the system breathes, no Day-1 panic ordering. Cheese: opening 700 pcs covers a full week; Friday check < 220 slices triggers an emergency Thursday delivery.

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

Value ╲ MovementHigh (daily)Medium (several/wk)Low (weekly−)
High Value (>5 AED)Beef patties — daily countsOil · Sauce — every 2–3dCritical spares — every 2–3d
Medium Value (1–5 AED)Buns · Fries · Cheese — every 2–3dPickles · Drinks — weeklyBottled water — weekly
Low Value (<1 AED)Sachets · Paper · Bags — weeklyChemicals · Towels — monthlySalt · Bulbs — monthly

P4.7 — Cycle Count Frequency

ClassificationFrequencyRationale
HV/HM (Beef)DailyHighest cost + movement. Errors → stockouts or loss.
HV/LM (Critical spares)Every 2–3 daysA missing critical spare stops production.
HV/MM · MV/HM (Oil, sauce, buns, fries, cheese)Every 2–3 daysHigh cost or movement — errors compound fast.
MV/MM · LV/HM (Pickles, drinks, sachets)WeeklyCatches 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.
P5

Procurement Plan

Order calendar · Budget · Authorization — a direct output of combining P3.2 supplier schedules with P4.4 ROP triggers

Framework: D4 — Procurement & Ordering. The order calendar is trigger-based, not a rigid schedule. Two triggers: shelf life forces it (Category B), or stock hits ROP.

P5.1 — Ordering Principles

Beef cycle: every 10 days · ~144 kg (~960 pcs). We order on the Mon/Wed/Fri day closest to the 10-day cycle, cutting effort from 3 orders/week to ~3/month for our most critical item.

Produce by shelf life: lettuce every 1–2 days · tomato every 2 days · onion every 3–4 days (7-day shelf life per D2).

P5.2 — Weekly Order Calendar

DayOrders PlacedDeliveriesKey Actions
SundayBeef (if cycle) · Buns · send weekly forecastWaste collection · BunsWeekly review. Confirm Monday deliveries.
MondayBuns · Lettuce · Tomato/Onion if dueBeef (if cycle) · Produce · BunsGRN all. Verify beef ≤ -18°C.
TuesdayBuns · Produce · Cheese standing (3 packs) · Beverages if ≤ ROPBuns · Produce · Cheese · BeveragesVerify dairy ≤ 4°C. Confirm 3 packs cheese.
WednesdayBeef (if cycle) · Buns · Produce · SUP-006 vs ROPBeef · Buns · Produce · Frozen & DryBusiest receiving day. Verify freezer space first.
ThursdayBuns · Produce · Friday prep stock checkBuns · ProduceHigh-demand eve. Order any item at risk now.
FridayBeef (if cycle) · Buns · Produce if dueBeef · Buns · ProducePeak day. Evening Friday stock check.
SaturdayBuns · Produce if due · Friday cheese checkBuns · ProduceWeekly KPI + waste report. Confirm Sunday orders.

P5.3 — Monthly Procurement Budget

CategorySupplierMonthly (AED)% of Total
Proteins (beef local)SUP-0015,500–6,50030–35%
Bakery (buns)SUP-0021,800–2,000~10%
ProduceSUP-0032,000–2,500~12%
Dairy (cheese)SUP-0041,300–1,500~7%
Frozen & Dry GoodsSUP-0062,500–3,000~14%
BeveragesSUP-0051,500–2,000~9%
MRO ConsumablesSUP-007800–1,200~5%
MRO Equipment & Maint.SUP-008/009500–1,0003–5%
TotalAll Suppliers~16,000–19,700100% (food cost target 30–35%)

P5.4 — Authorization Thresholds

Order TypeAmount (AED)Authorization
Standing orders (buns, produce)< 500Auto-approved
Routine within budget500–3,000Shop manager (same-day)
Large / budget-exceeding> 3,000Owner approval
Emergency ordersAny amountShop manager + written justification
P6

Logistics Plan

Receiving schedule · Shipment tracking · Emergency transport. The 7–10 AM window protects kitchen operations — it is not a punishment mechanism

Framework: D5 — Logistics & Receiving. The late-delivery protocol is stock-aware: refusing goods when stock is at or below ROP is self-harm, not discipline.

P6.1 — Late Delivery Protocol (Stock-Aware)

Stock PositionActionSupplier Consequence
Well above ROPRefuse. Reschedule.Log as late vs D3.5 KPI. Formal notification.
At or near ROPAccept. Do not refuse.Log late + non-conformance notice. Written explanation in 24h.
Safety stock / criticalAccept immediately. No delay.Urgent non-conformance. Supplier review if 3rd incident this month.

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

TimeSupplier / ItemsInspection StandardPut-Away
07:00–08:00SUP-003 fresh produce (daily)Freshness visual. Weigh vs note.I1 Fridge · FIFO · date label
08:00–09:00SUP-001 beef · SUP-004 cheese (Tue)Beef ≤ -18°C (reject > -15°C) · Cheese ≤ 4°C (reject > 6°C)Beef → I2 · Cheese → I3 · FIFO
09:00–10:00SUP-002 buns · SUP-005 bev · SUP-006 frozen/dry · SUP-007 MROBuns: freshness/count · Frozen ≤ -18°C · MRO: qty vs POBuns → I4 · Bev → I8 · Frozen → I2 · Dry → I7

P6.3 — Emergency Transport Triggers

ScenarioTriggerActionCost Threshold
Beef stockout riskI2+I6 < 74 pcs AND next delivery > 1 dayStaff pickup from SUP-001. Manager authorizes.Up to AED 200 vs ~2,500 lost sales
Bun stockoutI4 < today's forecast AND SUP-002 can't deliverPickup from SUP-002 or alternative bakery.Up to AED 100
Critical equipment failureGrill/fryer down · no spare · SLA missed > 4hEmergency collect from SUP-008.No upper limit — production stopped
Cheese weekend gapStock < 220 slices Friday eveningEmergency SUP-004 Thursday delivery.Up to AED 300
P7

Production Plan

Daily schedule · Station assignments · Staging quantities. Beef thaws 07:00–07:30 AM daily — previous-evening thawing is discontinued

Framework: D6 — Operations & Transformation. Morning thawing gives 3 hours before service, maximizes the safe usage window, and is controlled by staff already on site.

P7.1 — Hour-by-Hour Daily Schedule

TimeActivityResponsibleOutput
07:00–07:30Thaw beef I2 → I6, quantity per P2.5 demand level. Label thaw time.Persons A & BI6 loaded. Temp log started.
07:30–09:00Receive + GRN deliveries (P6.1). Prep produce I1→I12. Count buns. Refill sauce.Persons A & BAll I12 ready for lunch.
09:00–10:00Complete prep. Verify all stations. Brief Person G on forecast.A · B + C arrivesStations confirmed. Shop opens 10:00.
10:00–12:00Light service (~10%). Cook to order. Monitor pace vs forecast.A · B · CPace tracking active.
12:00–14:00LUNCH PEAK (35%). All stations. Person G on counter. Stockout monitoring.A · B · C + G~20–25 meals/hr. Cycle ≤ 12 min.
14:00–16:00Re-prep for dinner. Recount buns. Restock cooler. Verify I6.A · B · CDinner I12 replenished.
16:00–16:30Shift handover (A/B/C → D/E/F). KPIs · stock · forecast. Person G departs.All staffClean handover.
16:30–19:00Dinner prep. Verify I6 (~9h old) — escalate if insufficient (cannot re-thaw).D · E · FDinner stations ready.
19:00–22:00DINNER PEAK (30%). Person G on counter. Watch delivery-app packaging draw.D · E · F + G~15–20 meals/hr. Cycle ≤ 12 min.
22:00–23:30Tapering. Assess I6/I12 — store or discard. Log all waste (D2.3). Cleanup.D · E · FWaste log complete.
23:30–00:00Final service. Confirm tomorrow deliveries. Note I6 status for morning team.D · E · FShop secured.

P7.2 — Station Utilization at Peak (Friday Lunch — binding case)

StationCapacity/hrReq. (Fri Lunch)UtilizationStatus
Grill (C2a)60 patties25 patties42%Comfortable
Fryer (C2b)30 portions18 portions60%Moderate — first to bind
Assembly (C2c)40 burgers25 meals63%Moderate
Counter (C2d)50 transactions25 transactions50%Comfortable — Person G covers

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. These targets define when the simulation and the live operation are healthy — and when escalation fires.

P8.1 — KPI Targets & Escalation

KPITargetFrequencyEscalation Trigger
Menu Availability Rate≥ 98%Daily< 95% for 2 consecutive days
Item Fill Rate≥ 99%Daily< 97% for 3 consecutive days
Order Cycle Time≤ 12 min avgPer orderAverage > 15 min on any day
Quality Compliance≥ 99%Daily< 97% OR any food safety incident
Waste Rate< 5% of inventory valueWeekly> 7% in any week
Supplier On-Time Rate≥ 95% per supplierPer delivery< 90% in a calendar month
Forecast Accuracy±15% deviationDaily + monthly±25%+ for 2 consecutive weeks
Budget AdherenceWithin 5% of budgetMonthlyExceeds budget by > 10%
Equipment Uptime (critical)≥ 99%DailyCritical equipment down > 4 hours
Stock Accuracy≥ 98%Per cycle count< 95% on any count
Shrinkage Rate< 2% of inventory valueMonthly> 3% in any month
Beef Unit Cost≤ 16.70/kg local · ≤ 16.00/kg int'lMonthlyThreshold exceeded → source review

P8.2 — Review Calendar

CadenceWhenAgenda
Daily standup09:30 AM (after receiving)Yesterday KPIs · today forecast · stockout risks · equipment status
Weekly reviewSat eve / Sun morningWeek KPIs · waste · supplier performance · next-week demand · cheese check
Monthly review1st week of monthSpend vs budget · stock accuracy · shrinkage · price validity · food cost %
Quarterly reviewJan/Apr/Jul/OctKraljic review · SKU reclassification · contracts · SUP-011 PO · beef source mix

P8.3 — Risk Register (D7.2)

RiskProb.ImpactMitigation
Critical supplier failure — beef (SUP-001)LowCriticalSUP-011 reserve · 3-day I2 buffer · weekly forecast sharing
Equipment breakdown — grill/fryerMedCriticalPreventive maintenance · spares in I11 · 4-hr SLA
Refrigeration / freezer failureLowCriticalTemp alarm · emergency SLA · insurance · perishable triage
Cheese weekend gapLowModerate700 pcs opening + Tue standing · Friday ≥ 220 check
Demand spike > +30%MedModerateP2.5 staging buffers · pace tracking · emergency ordering
Customs delay — SUP-011MedModerateOrder 10 wks ahead · 3-day local buffer · air freight backup
Staff shortageMedModerateCross-training · Person G replaceable · reduce menu temporarily
Food safety incidentLowCriticalReceiving + 6 production quality points · FIFO · recall protocol

P8.4 — Simulation Success Criteria (sample)

#CriterionTest Method
1All 14 KPIs calculable from simulated dataRun 30-day simulation. Verify outputs in range.
2ROP triggers generate automatic purchase requisitionsSimulate to ROP. Confirm PR with correct supplier + MOQ qty.
3Dual-unit system works without errorsOrder beef in kg, convert to pcs (0.150). No rounding drift over 30 days.
4Demand-level staging prompts correctlyVerify Low/Med/High quantities prompted each morning.
5Thaw timing correctVerify 07:00–07:30 prompt, qty per P2.5 not fixed average.
6Shelf life categories enforcedCategory B flags end-of-service waste; Category A uses buffer logic.
11Late delivery protocol fires correctlySimulate late delivery; verify stock-position check before refuse/accept.
12ABC-XYZ + Kraljic tags appliedEvery SKU tagged; cycle count schedule applied automatically.

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 header.
Staffing7 defined people. A+B 07:00–16:00 · C 10:00–16:00 · D/E/F 16:00–00:00 · G part-time peak cashier.
Unit systemDual-unit. Beef order kg/consume pcs · fries kg/portions · cheese packs · buns bags of 12.
Demand planningAverages (98 meals, 74 patties) = reference only. Execution uses P2.5 Low/Med/High.
Beef thawing07:00–07:30 AM daily. Qty = next demand level + 15% buffer. Evening thawing discontinued.
Beef orderingEvery 10 days · ~144 kg. Freezer safe (144 kg beef + 80 kg fries = 224 kg < 300 kg).
CheeseTuesday-only standing order (3 packs). Friday check < 220 slices → emergency Thursday.
Soft drinksROP 496 cans · opening 864 · first reorder ~Day 6 · Category A logic.
Receiving protocolStock-aware: healthy → refuse · at ROP → accept + log · safety stock → accept + escalate.
Open itemsG1 · G2 · G3 all RESOLVED — ready for final software lock.
A plan fails not because it misunderstands the domain (a Model failure) nor because it uses the wrong organizing logic (a Framework failure) — it fails when execution falls short of intent. The simulation exists to find those failures before they cost anything. Status: REBUILT v2 — traceable, ready for software development.