Layer 2 of 3DRAFT v5

Supply Chain Framework

ByteBurger — Single-Location Burger Shop

The Framework is built on 7 governance domains (D1–D7). Each domain covers a cluster of related decisions and maps directly to the Model’s 8 primitives (S1–S8). Nothing in this Framework exists without a foundation in the Model. Nothing in this Framework schedules a specific action — that is the Plan. Nothing in this Framework exists without a foundation in the Model.

This document is the Framework — the organizing structure that defines how ByteBurger’s supply chain is governed. It provides the categories, responsibilities, processes, and decision rules that shape how supply chain work is organized. It does not describe what exists (that is the Model) nor what to do this week (that is the Plan). It answers one question: "How do we organize and govern this?"

How to read this document: Each domain defines what decisions are made, what rules govern those decisions, and what Model elements it covers. The Framework is timeless — it does not expire. It defines the organizing logic that remains stable even as specific plans, quantities, and suppliers change.

Framework Overview

The 7 governance domains and their relationship to the Model:

DomainGovernsModel Elements Covered
D1 — Demand ManagementHow we understand, anticipate, and respond to customer demandS8 (Availability), Demand Profile, S2 (F8 revenue, customer information)
D2 — Inventory GovernanceHow we decide what to hold, how much, where, and when to replenish; stock accuracy; classification; valuation; loss controlS5 (I1–I13), S6 (C1, C3), S7 (lead times)
D3 — Sourcing & Supplier ManagementHow we find, evaluate, select, contract, and manage supplier relationships including communication, forecasting, payments, and returnsS1 (N1–N3, N6), S2 (F1–F3 inbound goods, F5 orders/forecasts, F6 confirmations/schedules, F7 payments, F9 returns/credits), S6 (C4, C5, C7), S7, S3
D4 — Procurement & OrderingHow we execute buying — requisition, approval, order, confirm, receive, match, payS2 (F5, F6, F7), S6 (C4, C6)
D5 — Logistics & ReceivingHow goods physically move, how we receive/inspect, track shipments, handle transport and insuranceS2 (F1–F4, F6 confirmations/schedules, F9 waste/returns), S3, S6 (C5, C7, C8), S7
D6 — Operations & TransformationHow we manage production, prep, equipment, quality, and staff trainingS4 (T1–T6), S5 (I12, I13), S6 (C2a–d, C9, C10), BOM
D7 — Performance & Risk ManagementHow we measure, monitor, improve, and protect the supply chainS8 (metrics), all Composite Phenomena, all constraints

The domains follow a decision sequence: understand demand (D1) → decide what to hold (D2) → decide who to buy from (D3) → execute buying (D4) → manage physical movement (D5) → manage production (D6) → measure everything (D7). D7 feeds back into D1 as a continuous improvement loop.

THE 7 GOVERNANCE DOMAINS

D1

Demand Management

How we understand, anticipate, and respond to customer demand

Model foundation: S8 (Availability), Demand Profile, S2 (F8 revenue, customer information)

Everything in the supply chain exists to serve demand. If you do not understand demand, every other decision is a guess. Demand Management is the first domain because it feeds every domain that follows.

D1.1 — Demand Channels

ByteBurger serves customers through distinct channels. Each channel has different characteristics:

ChannelCharacteristicsVisibilityImpact on Supply Chain
Walk-inUnpredictable volume, real-time demand, no advance noticeLow — you see demand only when the customer is at the counterRequires ready inventory and fast transformation; safety stock absorbs variability
Delivery AppSlightly more predictable, orders arrive digitally before preparation beginsMedium — you see the order before the customer arrives; possible to see order trendsAllows short preparation lead time; packaging (I10) consumption increases
Catering / Pre-ordersKnown volume in advance, larger quantities, scheduled delivery timeHigh — demand is confirmed days or hours aheadAllows planned production; reduces waste; may require temporary capacity increase

D1.2 — Demand Forecasting

Forecasting estimates future demand based on historical patterns, known events, and judgment. For a small burger shop, it requires disciplined observation, not complex models.

Forecasting Inputs

  • Historical sales data — daily and weekly sales records by menu item.
  • Day-of-week pattern — Thursday–Saturday higher, Sunday–Wednesday lower.
  • Seasonal pattern — cooler months (October–March in GCC) higher; extreme summer lower.
  • Known events — public holidays, Ramadan, nearby events, promotions.
  • Delivery app trends — order volume and timing patterns from app dashboards.

Forecasting Method

Simple rolling average with adjustment: take average daily sales for the same day-of-week over the past 4 weeks, adjust for known events or seasonal factors. Produces a daily demand forecast by menu item feeding D2 and D6.

The forecast will always be wrong. The goal is to be wrong by a small, manageable amount. Safety stock (D2) absorbs the remaining error.

D1.3 — Demand Monitoring

Forecasting happens before the day. Monitoring happens during the day:

  • Pace tracking — compare actual sales at midday against forecast. If 20%+ above by lunch, trigger additional prep for dinner.
  • Stockout alerts — when any ingredient drops below quantity needed for remaining forecasted demand, flag immediately.
  • Channel shift — if delivery orders spike, packaging (I10) may deplete faster than planned.

D1.4 — Customer Node Governance (N5)

Model foundation: S1 (N5 — End Customer), S2 (F4 product outbound, F8 revenue)

The Model defines the customer as a node with its own characteristics. D3.6 governs supplier communication in detail — the customer node requires equivalent governance:

Customer Communication Protocols

ScenarioCommunication RuleWhoRecord
Menu item unavailableInform customer immediately. Offer substitute. Never let the customer discover it after ordering.Counter staffLogged as stockout event in D7
Order delay beyond 12 minProactive update to customer at the 10-minute mark with revised estimateCounter/delivery staffLogged against Order Cycle Time KPI
Quality complaintAcknowledge, replace immediately, log complaint with item, time, and nature of issueShift leadComplaint log feeds D6.4 and D7.3
Delivery app complaintRespond within platform's SLA. Root-cause: was it kitchen (D6) or handoff (D5.4) or driver?Shop managerTracked separately from walk-in complaints
Recurring complaint pattern3+ complaints on same item or issue in 7 days triggers root-cause investigationShop managerEscalated to D7.3 continuous improvement

Customer Feedback Loop

  • Daily — all complaints and compliments logged: item, channel, time, nature, resolution.
  • Weekly — complaint patterns reviewed in D7.3. Recurring issues trigger process correction.
  • Delivery app ratings — monitored weekly. Rating below platform threshold triggers investigation.
  • Feedback does NOT flow only through complaints — staff are trained to observe: which items sell out first (demand signal), which items get left uneaten (quality signal), which times see walkways (capacity signal).

D1.5 — Revenue Signal Governance (F8)

Model foundation: S2 (F8 — Financial Revenue), S8 (Availability)

The Model defines F8 (revenue flow from customer to shop) as a distinct flow. Revenue is not just a financial outcome — it is a supply chain signal:

  • Revenue per meal — tracked daily. A drop in revenue per meal with stable volume indicates a menu mix shift (customers ordering cheaper items) which changes ingredient demand patterns.
  • Revenue per hour by service period — identifies which periods generate the most value. Feeds staffing decisions (C9) and capacity prioritization.
  • Revenue vs. Cost of Goods Sold (COGS) — the food cost % calculated in the Plan (P3.X) must be governed here as a Framework rule: food cost % is a live calculated output, never a set target. When actual food cost % exceeds the alert threshold for any menu item, D7 investigation is triggered.
  • Revenue shortfall from stockouts — when a stockout occurs (D1.3 alert), the estimated revenue loss is calculated: (number of customers affected) × (average ticket price). This quantifies the cost of supply chain failure and feeds D7.3 priority-setting.

D1.6 — Seasonal & Ramadan Demand Governance

Model foundation: S8 demand profile (Ramadan/Eid, public holidays, seasonality)

The Model's demand profile now includes Ramadan/Eid and seasonal patterns. These reshape demand more than the standard weekly curve and must be governed, not improvised.

  • Ramadan — daytime trade falls to near-zero during fasting hours; a large, concentrated surge follows iftar (sunset) and runs late. Shift staffing, prep, and receiving to the evening; compress or suspend daytime operation. Reforecast the weekly pattern (D1.2) for Ramadan rather than applying the normal Thu–Sat shape.
  • Eid & public holidays — holiday peaks and catering/pre-order spikes. Build stock ahead of the holiday within shelf-life limits.
  • Seasonality — cooler months (Oct–Mar) and tourism lift volume; extreme summer dips. Adjust safety stock and ordering frequency by season.
  • This domain governs the Plan's seasonal demand adjustment (P2.6).
D2

Inventory Governance

How we decide what to hold, how much, where, and when to replenish

Model foundation: S5 (I1–I13), S6 (C1 storage capacity, C3 shelf life), S7 (lead times driving buffer needs)

Inventory Governance is where the Model’s 13 inventory categories become managed assets. This domain defines what to hold, how much, the rules that trigger replenishment, how stock is counted, classified, valued, and protected from loss.

D2.1 — Replenishment Rules by Inventory Category

The key decision tool is the ROP (Reorder Point):

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

Safety stock scale: Minimal (tightest — excess = same-day/next-day waste) → Low (some flexibility) → Moderate (meaningful buffer, manageable waste risk) → Comfortable (long shelf life, low waste risk).

Inv. CategoryReplenishment LogicROP DriverSafety Stock
I1 — Fresh Inputs (Refrigerated, 1–10 day life)Order frequency depends on each item’s shelf life within the 1–10 day range. Lettuce (3 days): order every 1–2 days. Tomatoes (5 days): every 2–3 days. Onion (7 days, dry storage): order every 3–4 days. Aligned with supplier delivery schedule (C5).ROP = next delivery cycle’s forecasted need, adjusted for item-specific shelf lifeMinimal — excess becomes waste within days.
I2 — Frozen InputsOrder in larger batches. Lead time 1–2 days local, weeks international.ROP = (daily usage × lead time) + safety stockModerate — longer shelf life allows meaningful buffer.
I3 — Purchased Inputs (Refrigerated, up to 14 days)Order aligned with usage rate and 14-day shelf life.ROP = (daily usage × lead time) + safety stockLow — shelf life gives some flexibility.
I4 — Purchased Inputs (Ambient, 1–2 day life)Order daily or every other day.ROP = tomorrow’s forecasted needMinimal — freshness paramount.
I5 — Inputs (Refrigerated, Long Life)Order weekly or bi-weekly.ROP = (weekly usage × lead time) + safety stockComfortable — long shelf life, low waste risk.
I6 — Staged Inputs (Thawed)Not ordered — staged internally from I2.Stage = today’s forecast + 15% bufferMinimal — over-staging = waste within 1–3 days.
I7 — Inputs (Ambient, Long Life)Order monthly or bi-monthly.ROP = (monthly usage × lead time) + safety stockComfortable — very low waste risk.
I8 — Finished Goods for ResaleOrder weekly. Long shelf life.ROP = (weekly usage × lead time) + safety stockComfortable — main constraint is storage (C1).
I9 — MRO EquipmentReplaced on failure or scheduled lifecycle.Trigger: age, condition, or failureN/A — managed via D6.3.
I10 — MRO Consumable SuppliesOrder weekly or bi-weekly.ROP = (weekly consumption × lead time) + min stockModerate — stockout disrupts operations.
I11 — MRO Spare PartsCritical spares on hand; non-critical on failure.Binary: keep spare or accept riskBinary — 1 spare or 0.
I12 — Working Stock (Daily Prep)Prepared internally from I1, I3, I4, I5, I6.Prep = today’s forecast + 10–20% bufferMinimal — over-prepping = end-of-day waste.
I13 — Work-in-ProgressExists only during active cooking.Driven by real-time ordersN/A — managed by D6.

D2.2 — Inventory Staging Rules

Staging is the planned movement between inventory categories:

Staging MovementTriggerTimingQuantity Rule
I2 (Frozen) → I6 (Thawed)Daily production forecast for next dayEnd of shift, day before useNext day’s forecast + 15% buffer. Never thaw more than 1.5 days of expected use.
I1 (Fresh) → I12 (Working Stock)Start of shift prep routineBefore each service periodForecast for upcoming service period + 10% buffer.
I3, I4, I5 → I12 (Working Stock)Start of shift prep routineSame as aboveForecast-driven. Cheese sliced, buns counted, sauces portioned.
I8 (Resale) → CoolerCooler stock drops below serving levelThroughout day as neededRefill cooler to capacity from ambient back stock.

D2.3 — Waste Management

  • Daily expiry check — inspect all short-shelf-life categories (I1, I3, I4, I6, I12) and remove items past use-by date.
  • FIFO (First In, First Out) — oldest stock used first. Applies to I1 through I8.
  • Waste logging — every discard recorded: item code, quantity, reason (expired, damaged, overproduction, quality). Feeds D7.
  • Disposal compliance — per local health regulations (C7).

FIFO = First In, First Out — oldest inventory used before newer, minimizing expiry risk.

D2.4 — Stock Accuracy & Cycle Counting

Stock accuracy ensures system records match physical reality. Without it, every ROP calculation is based on false data.

Cycle counting frequency is driven by the SKU classification matrix (D2.5). Items with higher combined value and movement scores are counted more frequently:

Classification CellCount FrequencyRationale
High Value / High MovementDaily or every 2–3 daysHighest cost and operational impact. Errors cause stockouts or significant waste.
High Value / Medium or Low MovementEvery 2–3 daysHigh cost per unit — even small discrepancies are expensive.
Medium Value / High MovementEvery 2–3 daysHigh consumption rate means errors compound quickly.
Medium Value / Medium MovementWeeklyBalanced control. Weekly catches discrepancies before they compound.
Medium Value / Low Movement; Low Value / High MovementWeeklyEither moderately costly or fast-moving. Weekly is sufficient.
Low Value / Medium or Low MovementMonthlyLow per-item impact. Monthly catches trends.
MRO Equipment (I9)QuarterlyLong-life assets. Physical presence verified periodically.
MRO Spare Parts (I11)MonthlyMust verify critical spares are actually on hand.

Discrepancy Investigation

  • Any discrepancy must be investigated — not just corrected. Causes: unlogged waste, theft, receiving errors, measurement errors, items used but not recorded.
  • Root cause identified before system adjustment. Process corrected to prevent recurrence.
  • Stock accuracy KPI — target: 98%+. Tracked in D7.

D2.5 — SKU Classification (Value × Movement Matrix)

SKU classification uses two independent axes — Value (cost per unit) and Movement (consumption rate) — creating a 9-cell matrix. This provides more precise control than simple ABC ranking, and the system supports all 9 cells even if a small operation like ByteBurger currently uses only some of them:

High MovementMedium MovementLow Movement
High ValueHV/HM — Tightest control. Daily counts, per-item forecasting, rigorously tracked supplier performance. Examples: Beef patties (DM-001)HV/MM — Tight control. Counts every 2–3 days, monitored closely. Examples: Cooking oil (DM-006)HV/LM — High cost but rare use. Keep critical stock, count every 2–3 days. Examples: Critical spare parts if expensive
Medium ValueMV/HM — Fast-moving, moderate cost. Counts every 2–3 days, standard ROP. Examples: Buns (DM-002), frozen fries (DM-007)MV/MM — Balanced control. Weekly counts, standard ROP. Examples: Cheese (DM-005), burger sauce (DM-009)MV/LM — Moderate cost, slow use. Weekly counts, longer reorder cycle. Examples: Pickles (DM-011)
Low ValueLV/HM — Cheap but consumed fast. Weekly counts, bulk ordering, higher safety stock acceptable. Examples: Sachets (FG-004/005/006), wrapping paper (MRO-C-005)LV/MM — Simplified control. Monthly counts, bulk ordering. Examples: Cleaning chemicals (MRO-C-001), paper towels (MRO-C-002)LV/LM — Lowest attention. Monthly counts, bulk ordering, high safety stock fine. Examples: Salt (DM-008), light bulbs (MRO-S-004)

Classification is not fixed — reviewed quarterly as consumption patterns change. An item moving from MV/MM to MV/HM (e.g., a new popular menu item increases fries consumption) needs upgraded control.

D2.6 — Inventory Valuation

Inventory valuation determines the financial value of stock on hand. The Framework uses FIFO costing — consistent with physical FIFO (D2.3):

  • When goods are received, purchase cost recorded (including landed cost for international — D3.3).
  • When consumed/sold, cost of oldest batch used first.
  • Remaining inventory valued at most recent batch costs.
  • Monthly valuation report — total value by category (I1–I11). Feeds D7 and D4 for budget tracking.

D2.7 — Loss & Damage Control

Loss control governs inventory shrinkage — the gap between system records and physical reality:

  • Waste — expired or spoiled (D2.3).
  • Damage — items broken during handling, storage, or receiving.
  • Theft — items taken without authorization.
  • Administrative errors — items received but not recorded, used but not logged.
  • All losses recorded: item code, quantity, date, loss category. Feeds D2.4 cycle counting.
  • Damage at receiving — on GRN, reported to supplier, claimed for credit (D5.1).
  • Suspected theft — investigated via cycle count discrepancies. Pattern = escalate.
  • Shrinkage KPI — target: below 2% of inventory value. Tracked in D7.

D2.8 — Storage Layout & Organization

Storage ZoneInventory CategoriesOrganization Rules
FreezerI2 (Frozen inputs)By item type. FIFO. Temperature monitored continuously. Capacity tracked (C1).
RefrigeratorI1 (Fresh), I3 (Cheese), I5 (Sauces, pickles), I6 (Thawed beef)Separate shelves per category. Raw meat below ready-to-eat (food safety). FIFO. Temperature monitored.
Dry storageI4 (Buns in basket, away from heat), I7 (Oil, salt, spices)Labeled shelves. Buns away from heat sources. Heavy items lower. FIFO.
Cooler (serving)I8 (Drinks — serving stock)Replenished from ambient. Customer-facing. By product type.
Ambient back storageI8 (Drinks — bulk), I10 (MRO consumables), I11 (Spare parts)Labeled shelves/bins. Designated locations. Marked minimum stock levels.
Kitchen / Prep areaI12 (Working stock), I13 (WIP)By station: grill, fryer, assembly. Labeled containers with prep date/time.
  • Every item has a designated location — eliminates searching, speeds put-away and picking, enables accurate counting.
  • Labeling — locations labeled with item name/code. Items labeled with receipt date and expiry date.
  • Space utilization — reviewed monthly. Over-capacity = adjust orders or reorganize. Under-used = consider reallocation.

D2.9 — Staging Governance Principles

Model foundation: S5 (Inventory Staging concept), S4 (Transformation), S6 (C3 shelf life, C1 storage type)

The Model defines inventory staging as a general principle: the same SKU moves between storage states as it approaches the point of use (e.g. frozen → thawed → prepped). D2.2 lists specific staging movements. This section governs staging as a system:

  • Staging is a managed transition, not a passive event — every staging movement changes the item's shelf life clock, storage requirements, and waste risk profile. Moving beef from I2 (30-day frozen) to I6 (1–3 day thawed) starts a new, shorter countdown. The person performing the staging must understand this transition.
  • Staging quantity validation — staging quantities are driven by demand forecasts (D1). The accuracy of staging directly reflects the accuracy of the forecast. When staging waste exceeds 10% of staged quantity for 3 consecutive days, the staging formula or the underlying forecast must be reviewed (D7.3).
  • Adding new staging steps — before introducing a new staging movement (e.g. pre-portioning cheese slices from I3 to I12), the following must be evaluated: (a) does it create a new shelf life window shorter than the current one? (b) does it require additional storage space (C1)? (c) does it require additional staff time (C9)? (d) does the waste risk of the new stage outweigh the prep time saved? Shop manager decides; reviewed quarterly.
  • Staging never creates more waste than it prevents — this is the governing principle. If end-of-day waste from staged items (I6, I12) consistently exceeds 15% of the day's staged quantity, the staging quantities must be reduced even if that means slightly longer prep-to-serve times.

D2.10 — Cost & Margin Governance

Model foundation: cost attribute (Model Extensions); S8 Food Cost % / Gross Margin metric

The Model now treats cost as a tracked attribute. This section governs how it is monitored.

  • Unit and landed cost — every item carries a unit cost and a landed cost (unit + inbound freight + customs duty + handling). For imports, D3.3 and D5.2 feed the landed cost.
  • Food cost target — ingredient + packaging cost held at ≤ 30–35% of menu price; reviewed monthly against the Plan's BOM cost (P3.X) and pricing (P3.4).
  • Waste cost — the landed cost of discarded stock, rolled into waste reporting (D2.3).
  • Margin erosion trigger — a supplier price increase, rising yield loss, or rising waste triggers a review: re-tender (D3.1), re-engineer the BOM, or reprice.

D2.11 — Allergen & Halal Segregation

Model foundation: I16 (segregated stock); C19 (segregation constraint)
  • Halal and allergen-sensitive items are physically separated in storage and handling (dedicated shelf/zone defined in D2.8).
  • No cross-contact between non-halal and halal goods or contact surfaces. Segregation is checked in quality control (D6.4) and recorded for compliance (D7.7).
D3

Sourcing & Supplier Management

How we find, evaluate, select, contract, and manage suppliers — both local and international

Model foundation: S1 (N1–N3, N6), S2 (F1–F3 inbound goods, F5 orders/forecasts upstream, F6 confirmations/schedules downstream, F7 payments, F9 returns/credits), S6 (C4, C5, C7), S7, S3

Sourcing is the strategic domain — it decides who we buy from, on what terms, and how the ongoing relationship is managed. Distinct from Procurement (D4), which executes the buying transactions.

D3.1 — Supplier Identification, Qualification & Tendering

Qualification Criteria

CriterionWhat It ChecksApplies To
Legal complianceValid trade license, food handling permits, halal certification (GCC)N1, N2
Quality standardsProduct samples, consistency, certifications (HACCP, ISO)N1, N2
CapacityCan the supplier meet volume consistently?N1, N2, N3
Delivery reliabilityOn-time history, frequency options, proximityN1, N2, N3
Financial stabilityStable enough for long-term supply?N1, N2, N3
Payment termsCredit period, payment methods, early payment discountsN1, N2, N3
MOQ compatibility (C4)Does MOQ fit storage (C1) and usage?N1, N2
Delivery schedule (C5)Aligns with receiving window (C8: 7–10am)?N1, N2, N3

Tendering Process (RFQ / RFP / RFI)

ProcessFull NameWhen UsedWhat It Asks
RFIRequest for InformationExploring the market — what suppliers exist and offerGeneral: products, capabilities, certifications. No pricing.
RFQRequest for QuotationYou know what you need, want comparable pricingSpecific items, quantities, schedule. Suppliers respond with pricing, MOQs, lead times, terms.
RFPRequest for ProposalComplex need or want full solution proposalOpen-ended: suppliers propose approach, pricing, SLAs, value-add. Used for N6 services and N3 equipment.

D3.2 — Supplier Categorization

CategoryDefinitionExamplesManagement Approach
CriticalSingle/limited-source for core menu itemsMeat supplier, bun supplierClose relationship, backup identified, weekly monitoring, favorable terms
ImportantSupport operations, alternatives availableProduce, dairy, beverage distributorMonthly monitoring, 1–2 alternatives identified, standard terms
RoutineEasily replaceable commoditiesCleaning supplies, packaging, sachetsPrice-driven, switch easily, minimal relationship management
ServiceNon-material service providersEquipment maintenance, pest control, waste disposal (N6)Contract-based, annual review, SLA-driven

D3.3 — International Sourcing

  • Supplier identification — same criteria as D3.1, plus: export licenses, international shipping capability, customs track record.
  • Incoterms — FOB (buyer pays freight from port), CIF (seller pays freight/insurance to destination port), DDP (seller handles everything to buyer’s door).
  • Customs clearance (التخليص الجمركي) — commercial invoice, packing list, bill of lading/airway bill, certificate of origin, health certificates, halal certificate, HS code.
  • Customs duties (رسوم جمركية) — based on HS Code (Harmonized System Code) and declared value.
  • Landed cost — purchase price + freight + insurance + duties + broker fees + local delivery. Compared against local pricing.

International Lead Time

ComponentDurationVariability
Supplier preparation1–4 weeksMedium
Sea freight2–6 weeksMedium-high
Air freight2–5 daysLow (expensive)
Customs clearance1–7 daysHigh
Local delivery1–2 daysLow
Total (sea)4–13 weeksHigh
Total (air)1–2 weeksMedium

D3.4 — Negotiation & Contract Management

Negotiation Elements

  • Pricing — unit price, volume discounts, price validity, review mechanism.
  • Payment terms — Net 15, Net 30, COD (Cash on Delivery). Early payment discounts.
  • Delivery terms — schedule (C5), location, transit risk (Incoterms for international).
  • Quality standards — agreed specifications, acceptable quality level, rejection/return procedure.
  • MOQ and flexibility — minimum quantities (C4), order size adjustments, emergency provisions.

Contract Structure

  • SLA (Service Level Agreement) — measurable commitments: on-time rate, quality rate, response time. Consequences for failure.
  • Duration — annual for critical/important, renewable. Routine may be PO-based without formal contract.
  • Termination clause — conditions for ending, notice period.
  • Review — annually or when performance falls below SLA. Feeds D3.5.

D3.5 — Supplier Performance Monitoring

MetricDefinitionTargetFrequency
On-Time Delivery Rate% of deliveries on schedule95%+Every delivery
Quality Acceptance Rate% passing receiving inspection98%+Every delivery
Order Accuracy% matching PO in item and quantity99%+Every delivery
Lead Time ConsistencyActual vs. promisedWithin ±1 dayMonthly
ResponsivenessSpeed of response to inquiries/complaintsQualitativeQuarterly
Contract ComplianceAdherence to SLA termsFull complianceQuarterly

D3.6 — Supplier Communication & Relationship Governance

Supplier management is not just evaluation and contracts — it is the ongoing governance of information, financial, and return flows between ByteBurger and its suppliers:

Forecast & Demand Sharing (F5)

  • Critical suppliers receive a weekly demand forecast so they can plan capacity. This reduces the risk of the supplier being unable to fulfill a sudden increase.
  • Important suppliers receive monthly volume estimates for planning purposes.
  • Routine suppliers receive no forecast — orders placed as needed.
  • All forecast sharing is documented — date, supplier, forecast shared, any supplier response.

Expected Supplier Information (F6)

  • Price updates — suppliers must give advance notice (minimum 2 weeks) of any price changes. Part of SLA (D3.4).
  • Supply disruption alerts — suppliers must proactively notify ByteBurger of any issue that may affect delivery (raw material shortage, production problems, logistics delays). Part of SLA.
  • Delivery confirmations — supplier confirms delivery date and time after PO is placed. Non-confirmation triggers follow-up.

Payment as Relationship Tool (F7)

  • On-time payment tracking — ByteBurger tracks its own payment performance to suppliers. Target: 100% on-time per agreed terms.
  • Early payment discounts — utilized when cash flow allows, especially with critical suppliers to strengthen the relationship.
  • Payment disputes — when invoice doesn’t match PO/GRN (three-way match failure in D4), dispute is communicated to supplier with documentation. Resolution tracked.

Supplier Returns & Credits (F9)

  • Return authorization — before returning goods, supplier must agree to accept the return. Return reason documented.
  • Credit process — agreed credit (refund, replacement, or credit on next invoice) documented and tracked until resolved.
  • Impact on performance — every return counts against the supplier’s Quality Acceptance Rate in D3.5.

D3.7 — Network Visibility & Dependency Mapping

Model foundation: S3 (Network — tiers, distributed control, limited visibility, single-point dependency)

The Model warns: "No single node can see or control the full network." It identifies three structural risks: limited Tier 2 visibility, single-point convergence on the shop, and high dependency with few suppliers per category. This section governs how ByteBurger manages network-level risks that no single supplier relationship (D3.1–D3.6) can address.

Tier 2 Visibility Protocol

ByteBurger interacts directly with Tier 1 suppliers. Tier 2 (supplier's suppliers) is usually invisible. A disruption at Tier 2 — a cattle farm disease outbreak, a wheat harvest failure, a packaging factory fire — propagates to ByteBurger through delayed or failed Tier 1 deliveries, often without warning.

  • Critical suppliers (per D3.2) — the SLA (D3.4) must include a Tier 2 disclosure clause: the supplier must name their primary sources for the items they supply to ByteBurger, and must proactively notify ByteBurger of any Tier 2 disruption that may affect supply within 24 hours of the supplier becoming aware.
  • Important suppliers — asked (not contractually required) to share Tier 2 source information annually. Documented in supplier file.
  • Routine suppliers — no Tier 2 visibility required. Easily replaceable.
  • Tier 2 register — for Critical suppliers, maintain a record: supplier name, their primary source(s), geographic location of source, known risks (seasonal, political, environmental). Reviewed quarterly.

Item-to-Supplier Dependency Map

The Model says: "with few suppliers per category, losing one supplier can mean losing that entire product line." This requires a structured dependency view:

Dependency TypeDefinitionRisk LevelGovernance Rule
Sole sourceOnly one supplier can provide this itemCriticalBackup supplier must be identified and pre-qualified (D3.1). If no backup exists, safety stock increased to cover supplier lead time x 2.
Dual sourceTwo suppliers available, one primaryModerateSecondary supplier relationship maintained: annual qualification check, test order at least once per year.
Multi-sourceThree or more suppliers availableLowPrice-driven selection. Switch on performance or cost.
Internal dependencyItem produced internally (I12, I13) from upstream inputsInheritedRisk inherits from the upstream input's dependency type. Chopped lettuce (I12) is only as secure as lettuce supply (I1).
  • Dependency map reviewed quarterly — as part of D7.3. Any item moving from dual-source to sole-source triggers immediate backup identification.
  • Dependency map includes service providers (N6) — a sole-source equipment maintenance provider is as risky as a sole-source ingredient supplier if the equipment is critical.

Single Point of Convergence — Shop Continuity

The Model identifies the shop as the single node where all flows converge. If the shop cannot operate, the entire customer-facing supply chain fails regardless of supplier readiness.

  • Business continuity scenarios — fire, flood, extended power failure, forced regulatory closure, major equipment failure affecting multiple critical systems simultaneously.
  • Continuity protocol — for each scenario: (a) immediate actions (safety, communication, insurance notification per D5.6), (b) inventory preservation actions (perishable assessment, emergency transfer if possible), (c) supplier notification (pause deliveries to avoid waste), (d) customer communication (delivery app pause, signage, social media), (e) recovery steps and timeline, (f) insurance claim initiation.
  • Continuity plan reviewed annually — as part of quarterly D7.3 review. Updated after any incident.

D3.8 — Node Capacity Monitoring

Model foundation: S1 (Node — capacity as key property), S6 (constraints)

The Model says each node has a capacity ceiling. D3.5 monitors supplier delivery performance after the fact. This section governs proactive capacity awareness:

  • Critical suppliers — during weekly forecast sharing (D3.6), ask: "Can you handle this volume?" Document supplier response. If the supplier indicates they are approaching their own capacity limits, escalate: consider increasing safety stock, alerting backup supplier, or adjusting order timing.
  • Capacity signals to watch for — supplier requesting longer lead times, supplier unable to fulfill emergency orders they previously could, supplier reducing delivery frequency or available delivery days, supplier raising MOQs. Any of these may indicate the supplier is capacity-constrained. Logged and tracked in D3.5.
  • Shop capacity (N4) self-monitoring — the shop is also a node with capacity. When production utilization exceeds 70% at any station during peak (tracked via D7.1 KPIs), the Framework triggers a capacity review: can the bottleneck be relieved through process improvement (D6), staffing adjustment (C9), or does it require equipment investment? Decision rules in D6.8.

D3.9 — Waste Disposal Governance (N6/F9)

Model foundation: S1 (N6 — Service Provider), S2 (F9 — Waste/Return flow), S6 (C7 — Regulatory)

The Model defines F9 (waste/return flow) and N6 (service providers including waste disposal). D2.3 governs waste logging. D5.7 mentions waste disposal. This section governs the waste disposal relationship with the same rigour applied to inbound supplier relationships:

  • Waste disposal provider treated as a managed supplier — included in D3.2 categorization (Service category). Subject to SLA (D3.4) with measurable commitments: collection schedule reliability, compliance certification, response time for ad-hoc collections.
  • Performance tracked in D3.5 — on-time collection rate (target: 100%), compliance certificate validity, responsiveness to ad-hoc requests.
  • Regulatory compliance (C7) — waste disposal provider must hold valid waste handling permits. Certificates verified annually. Expired certification = immediate escalation and alternative provider activation.
  • Used oil collection — tracked separately. Collection frequency, volume, and any revenue from used oil sale documented.
  • Waste segregation rules — food waste, used oil, general waste, and recyclables must be segregated per local regulations. Staff trained on segregation (D6.5). Non-compliance logged and corrected.
D4

Procurement & Ordering

How we execute the buying cycle — from need identification to payment

Model foundation: S2 (F5 purchase orders, F6 confirmations, F7 payments), S6 (C4 MOQ, C6 budget)

Procurement is transactional. D3 decides who and on what terms. D4 executes the buying.

D4.1 — The Procurement Cycle

StepActionTriggerOutput
1. Need identificationInventory hits ROP (D2) or specific need arisesInventory monitoring or manual requestPurchase Requisition (PR): what, how much, by when
2. ApprovalPR reviewed against budget (C6) and authorization thresholds (D4.2)PR createdApproved or rejected PR
3. Purchase Order (PO)Approved PR converted to PO, sent to supplierApproved PRPO sent (F5): item, quantity, price, delivery date, location, PO number
4. ConfirmationSupplier confirms fulfillmentPO received by supplierConfirmation (F6). If unable, escalate.
5. Goods receiptDelivery inspected, accepted/rejected (D5)Physical deliveryGRN: what received, quantity, condition, discrepancies
6. Invoice matchingThree-way match: PO vs. GRN vs. invoiceInvoice receivedMatched = approved for payment. Mismatch = flagged.
7. PaymentPayment per agreed termsApproved invoice + terms metPayment (F7). Record updated.

D4.2 — Ordering Rules & Authorization

  • MOQ compliance (C4) — orders meet supplier minimum. Below MOQ = batch for multiple days.
  • Budget compliance (C6) — spend within monthly budget.
  • Delivery schedule alignment (C5) — ordered with lead time for next delivery day within C8 window.
  • Standing orders — pre-agreed daily quantity for high-frequency items (I1, I4), adjusted weekly.
  • Emergency orders — outside normal cycle when stockout risk identified. Logged with reason.

Authorization Thresholds

Order ValueAuthorizationRationale
Below routine threshold (standing orders, consumables)Auto-approved within standing order parametersHigh frequency, low value, pre-negotiated.
Above routine, within monthly budgetShop manager approvalBudget compliance and need validation.
Exceeds budget or non-standard purchaseOwner / senior managementPrevents overrun, ensures strategic alignment.
Emergency ordersShop manager + documented justificationSpeed + accountability.

D4.3 — Procurement Records

  • PO log — every PO: date, supplier, items, quantities, prices, expected/actual delivery.
  • GRN log — every delivery: date, supplier, PO ref, items, quantities, condition, discrepancies.
  • Invoice/Payment log — every invoice: amount, PO ref, GRN ref, payment date, method.
  • Supplier spend analysis — monthly/cumulative per supplier, per category. Feeds D7.
  • Emergency order log — date, reason, items, cost, outcome. Reviewed monthly.

D4.4 — Procurement SOPs

All procurement processes must be documented as SOPs (Standard Operating Procedures):

  • SOP: Daily ordering — check levels, compare ROP, generate PR, convert to PO.
  • SOP: Receiving & GRN — inspect, document, handle discrepancies.
  • SOP: Invoice matching & payment — three-way match, process payment, handle mismatches.
  • SOP: Emergency ordering — when, how, who approves, documentation.

SOPs reviewed when Framework changes. Staff trained before executing procurement tasks (D6.5).

D5

Logistics & Receiving

How goods physically move, how they are received, tracked, transported, and insured

Model foundation: S2 (F1–F4 goods flows, F6 confirmations/delivery schedules, F9 waste/returns), S3 (network paths), S6 (C5, C7, C8), S7 (transit times)

Logistics governs physical movement. Uses inbound (coming in) and outbound (going out) from ByteBurger’s perspective.

D5.1 — Inbound Logistics (Local Suppliers)

StepWhat HappensWhoRules
Delivery arrivalSupplier vehicle arrives during receiving windowSupplier driverC8 window (7–10am). Outside = refused unless pre-arranged.
Receiving inspectionInspect against PO: items, quantity, quality, temperatureShop staff (receiver)Temp check for I1, I2, I3, I5, I6. Reject above threshold.
DocumentationGRN completed. Discrepancies recorded.Shop staffGRN refs PO. Discrepancies communicated same day. Damage logged (D2.7).
Put-awayGoods to correct storage per D2.8Shop staffFIFO maintained. Items labeled with receipt/expiry date.

D5.2 — Inbound Logistics (International Suppliers)

StepWhat HappensWhoKey Documents
Freight bookingArrange sea/air freightForwarder or supplier (per Incoterm)Booking confirmation, schedule
In-transit trackingMonitor shipment location, ETABuyer or forwarderBill of lading / airway bill, tracking number
Port arrivalGoods arrive at destinationPort authorityArrival notice
Customs clearance (التخليص الجمركي)Submit docs, pay duties, clearCustoms brokerCommercial invoice, packing list, CoO, health certs, halal cert, HS code
Local deliveryCleared goods to ByteBurgerLocal transportDelivery note
Receiving at shopSame as D5.1Shop staffGRN ref international PO

D5.3 — Shipment Tracking & Visibility

  • Local — tracked via expected delivery date on PO confirmation (F6). No arrival within window = contact supplier.
  • International — tracked via bill of lading / airway bill. Milestones: dispatch, departure port, arrival port, customs status, local delivery.
  • Exception handling — Delay: assess stock + safety stock coverage. Insufficient = emergency order (D4.2) or air freight.
  • Exception handling — Damage in transit: document with photos, file carrier/insurance claim (D5.6), order replacement.
  • Exception handling — Lost shipment: escalate to carrier, file insurance claim, trigger emergency procurement.

D5.4 — Outbound Logistics (F4 — Product Outbound)

Model foundation: S2 (F4 — Product Outbound), S8 (Availability — order cycle time, quality compliance)

F4 is the primary value-delivery flow — the moment everything the supply chain built reaches the customer. Inbound flows (F1–F3) receive multi-domain governance across D3, D4, and D5. F4 requires equivalent rigour because a failure here wastes all upstream effort.

ChannelProcessPackagingQuality Rules
Walk-in (dine-in)Assembled at counter, served directlyTray, wrapping, fry containersServed within 2 min of assembly. Temperature maintained.
Walk-in (takeaway)Packaged for transportTakeaway bag, secure packaging+ packaging integrity check before handoff
Delivery appPackaged, handed to driverSealed bag, drink securedTemperature maintained for transit. Handoff within platform wait time.

Outbound Quality Gate

Every outbound order passes through a final verification before leaving the counter:

  • Order accuracy check — verify all items match the order (correct burger, correct sides, correct drink, correct sachet count). Counter staff performs this; not optional.
  • Packaging integrity — takeaway and delivery orders checked for: bag sealed, drinks upright and secured, hot items separated from cold items, no leaking.
  • Temperature compliance — hot food must be served hot (>60C). If order has been sitting >3 minutes since assembly, assess temperature. Remake if below threshold.
  • Order accuracy failures — logged: date, time, channel, what was wrong, root cause (kitchen error, counter error, labeling error). Feeds D7.3. Target: <1% order error rate.

Delivery App SLA Monitoring

  • Platform SLA — each delivery app has a maximum acceptable preparation time. ByteBurger tracks its own performance against this SLA.
  • Handoff log — time of order receipt, time of preparation complete, time of driver pickup. Gap between prep complete and driver pickup is not ByteBurger's control — but excessive waits (>10 min) with hot food sitting affect quality. If pattern emerges, escalate to delivery platform.
  • Delivery complaints traced to source — when a delivery customer complains, root-cause: (a) kitchen error (D6), (b) packaging/handoff error (D5.4), (c) driver error (outside ByteBurger's control). Only (a) and (b) are actionable internally.

D5.5 — Transportation & Route Management

ScenarioWhenDecision RulesRequirements
Emergency supplier pickupStockout risk, supplier can’t deliver outside scheduleCost of lost sales vs. trip cost. Only for high-value/high-movement items.Vehicle, staff assigned, fastest route, receipt collected
Equipment transport for repairEquipment fails, must go to N3 (MRO supplier) or N6 (service provider)Based on equipment criticality. Critical = same-day.Proper handling, documentation of what sent/received
MRO supply pickupUrgent MRO need not available through normal deliveryOnly when stockout impacts today’s operationsStaff assigned, receipt collected, logged as emergency (D4.2)
Catering deliveryCustomer orders delivery to their locationDelivery pricing, route, timing commitmentSuitable vehicle, insulated packaging, delivery confirmation

D5.6 — Insurance

TypeCoversWhen Required
Goods in transit (int’l)Loss/damage during international shippingAll international shipments. Coverage per Incoterm.
Goods in transit (local)Loss/damage during supplier delivery or own pickupSupplier delivery: supplier covers. Own pickups (D5.5): business insurance.
Stored inventoryLoss from fire, flood, theft, equipment failureBusiness insurance. Coverage set by D2.6 valuation.
EquipmentDamage/breakdown of MRO equipment (I9)Business policy. Critical equipment specifically covered.
LiabilityThird-party claims from food safety or delivery incidentsRequired by regulation. Reviewed annually.

D5.7 — Reverse Logistics

  • Supplier returns — defective/incorrect items returned. Documented with reason, PO ref. Credit tracked. Return decision and credit governance in D3.6.
  • Equipment returns for repair — failed MRO equipment sent to N3 (MRO supplier) under warranty/repair agreement or N6 (service provider) for independent repair. Tracked with expected return date.
  • Waste disposal — expired food, used oil, general waste. Per regulations (C7). Service provider (N6) manages collection.

D5.8 — Cold Chain Integrity

Model foundation: C13 (temperature integrity); F1–F3 transport mode; T7 (receiving)
  • Every chilled/frozen inbound flow specifies a temperature regime (chilled 2–8°C; frozen ≤ −18°C) and an ownership / risk-transfer point (supplier-delivered vs shop-collected) that fixes who bears in-transit loss.
  • Temperature is verified at three points: supplier dispatch (where available), the receiving dock (D5.9), and storage (continuous monitoring under D2.8).
  • Excursion handling — out-of-band stock is quarantined (I15) and assessed; confirmed loss is logged to waste (D2.3) and the supplier scored (D3.5).
  • KPI: Cold-Chain Compliance ≥ 99% (D7.1).

D5.9 — Receiving Inspection & Acceptance

Model foundation: T7 (receiving inspection); I15 (quarantine/hold); S8 Receiving Acceptance Rate

Incoming goods are not stock until they pass inspection. This formalizes the accept/reject gate at the dock.

  • Inspect every delivery — temperature, quantity vs PO, expiry / shelf-life remaining, damage, and compliance documents (F12).
  • Decision — accept → release to storage; condition/quantity issue → quarantine (I15) pending decision; fail → reject and return (D5.7).
  • Discrepancies are logged and matched in procurement (D4); repeat issues feed supplier performance (D3.5).
  • KPI: Receiving Acceptance Rate ≥ 97% (D7.1).

D5.10 — Traceability, Batch/Lot & Recall

Model foundation: F12 (compliance/traceability), F13 (recall); batch/lot identity; S8 Traceability Coverage
  • Batch/lot capture — perishable receipts are recorded with batch/lot number and expiry, enabling First-Expiry-First-Out rotation (extends staging D2.2) and recall.
  • Recall procedure — on a supplier or authority alert: identify the affected lot, locate it in stock and recent production, quarantine (I15), withdraw via F13, notify the authority, and log the event.
  • KPI: Traceability Coverage = 100% for perishables (D7.1).
D6

Operations & Transformation

How we manage production, preparation, equipment, quality, and staff training

Model foundation: S4 (T1–T6), S5 (I12, I13), S6 (C2a–d, C9, C10), BOM (Bill of Materials)

D6.1 — Production Workflow

StageActivityInputOutputConstraint
Pre-shift prepThaw beef (I2→I6), chop veg (I1→I12), portion sauces, count bunsI1,I2,I3,I4,I5I6, I12C9 (staff)
Grill (T1)Cook thawed pattiesI6Cooked pattyC2a
Fryer (T2)Deep fry fries and other fried itemsI2 (frozen fries)Cooked friesC2b
Toasting (T3)Toast bunsI4Toasted bunGrill/toaster
Assembly (T4)Assemble burger from componentsCooked patty + bun + I12Complete burgerC2c
Pass-through (T5)Stage drinks/sachets to counterI8Ready for saleNear-zero (LT10,LT11)
Bundling (T6)Combine into combo with packagingBurger+fries+drink+I10Customer mealC2d

D6.2 — Production Scheduling

  • Pre-shift prep quantity — D1 forecast for upcoming service period + 10–20% buffer.
  • Cook-to-order (patties, fries) vs. stage-to-stock (prep ingredients I12). Minimizes cooked food waste.
  • Peak pre-staging — additional I12 before lunch (12–14:00) and dinner (19–22:00).
  • End-of-day assessment — all remaining I12 (working stock) assessed individually. Each item’s remaining usable life depends on its source category: thawed beef (from I6) has 1–3 days in fridge — fine for tomorrow; chopped fresh produce (from I1) has hours to 1 day — assess freshness; cheese (from I3) has days — fine; sauces (from I5) have weeks — fine. Items that will not be usable by the next service period are recorded as waste (D2.3). Items with remaining life are stored properly for next-day use. I13 (WIP — food actively cooking) should not exist at closing; if it does, it is served or discarded.

D6.3 — Equipment Management

TypeCoversFrequencyWho
Preventive maintenanceScheduled cleaning, inspection, servicingDaily clean, weekly deep clean, monthly professional for critical equipmentDaily: kitchen staff. Monthly: N6
Reactive maintenanceRepair of broken equipmentOn failureN6 or N3. Critical: 4-hour SLA.
Spare partsEnsure critical spares (I11) availableMonthly via cycle count (D2.4)Shop manager
Equipment lifecycleTrack age, plan replacementAnnual reviewCompare against Item Master lifespan

D6.4 — Quality Management

Quality PointCheckedStandardOn Failure
Incoming (D5)Temperature, freshness, packaging, correct itemsCold chain: ≤4°C refrigerated, ≤-18°C frozen. No damage.Reject. GRN. Notify supplier. Log D2.7.
Storage (D2)Temperature, FIFO, shelf lifeFridge/freezer in range. No expired items.Remove expired. Adjust or escalate D6.3.
Prep (D6)Freshness, cleanliness, portion accuracyI12 passes visual/smell test. Portions match quantities defined in the Bill of Materials (BOM).Discard substandard. Re-prep.
Cooking (D6)Temperature, time, appearancePatty ≥74°C internal. Fries golden. Bun toasted evenly.Discard, re-cook. Investigate if recurring.
Assembly (D6)Correct components, presentation, packagingEvery component listed in the Bill of Materials present. Clean packaging.Reassemble. Coach staff.
Service (D1/D6)Speed, accuracy, temperatureCycle time ≤12 min (S8). Correct order. Hot food hot.Remake. Track in D7.

D6.5 — Staff Training & Certification

AreaCoversWhoFrequency
Food safety & hygieneHACCP, hygiene, cross-contamination, temperature, allergensAll kitchen and receiving staffOn hire + annual. Certification where required (C7).
Receiving & inspectionInspect deliveries, GRN, discrepancies, temperature checksReceiving-duty staffOn hire + SOP changes
Storage & FIFOPut-away, FIFO, labeling, storage zones (D2.8)All inventory handlersOn hire + quarterly
Equipment operationSafe use of grill, fryer, toaster, fridge, POSAll kitchen staffOn hire + new equipment
Emergency proceduresEquipment failure response, emergency ordering (D4.2), fire, power outageAll staffOn hire + semi-annual drill
Waste managementWaste logging, expiry checks, disposal, FIFOAll kitchen and storage staffOn hire + SOP changes
  • Training records — date, staff member, topic, trainer, result. Maintained for compliance (C7).
  • Certification tracking — expiry dates tracked. Renewals scheduled before expiry.

D6.6 — Constraint Interaction Management

Model foundation: S6 (all constraints — interactions between C1–C10)

The Model documents that constraints interact: C4 (MOQ) conflicts with C1 (storage), C3 (shelf life) conflicts with C5 (delivery schedule), C2a (grill capacity) conflicts with C9 (staff). Each constraint is governed individually across different domains. This section governs the interactions:

Known Constraint Interactions

InteractionConstraintsConflictResolution Rule
MOQ vs StorageC4 + C1Supplier requires more than storage allowsNegotiate lower MOQ, arrange more frequent deliveries, or expand storage. Never accept MOQ that exceeds storage — goods will be damaged or improperly stored.
Shelf Life vs Delivery ScheduleC3 + C5Item expires before next deliveryCalculate coverage: (shelf life remaining at delivery) must exceed (days until next delivery + 1 day safety). If not, arrange intermediate delivery or find daily-delivery supplier.
Equipment vs StaffC2a-d + C9Equipment capacity exceeds staff ability to operate itActual throughput = minimum of (equipment capacity, staff capacity). When calculating production capacity, always use the lower number. Cross-training (D6.5) to increase effective staff capacity.
Operating Hours vs ReceivingC8 + C5Deliveries arrive after receiving window closesLate delivery protocol (governed by Plan P6.1). Framework rule: the receiving window exists to protect operations, not to punish suppliers. Accept or refuse based on stock position, not on principle.
Budget vs Safety StockC6 + C1 + C3Budget cannot support the safety stock that shelf life and storage requirePrioritize safety stock for critical items (HV/HM per D2.5). Reduce safety stock for non-critical items before cutting critical stock. Budget shortfall for safety stock is escalated to owner.

Interaction Detection

  • When any constraint is changed (e.g., supplier changes MOQ, storage is reduced, new staff schedule), the interaction table above must be checked for cascading effects.
  • New constraint interactions discovered during operations are added to this table and reviewed in D7.3.

D6.7 — Bottleneck Identification & Response

Model foundation: S6 (Constraint) x S4 (Transformation) x S1 (Node) — Bottleneck as composite phenomenon

The Model defines a bottleneck as "the single constraint that limits the entire system's output." The Framework must define how to identify and respond to bottlenecks — not leave it to the Plan to discover them.

Bottleneck Detection Rules

  • The bottleneck is the station with the highest utilization percentage during peak — tracked via D7.1. If grill is at 42%, fryer at 60%, and assembly at 63%, assembly is the current bottleneck.
  • Utilization thresholds:
    • Below 50%: comfortable. No action.
    • 50–70%: monitor. Track trend over 4 weeks.
    • 70–85%: warning. Begin evaluating relief options (process, staffing, equipment).
    • Above 85%: critical. Implement relief before the station becomes a hard constraint. Options: add parallel capacity (second unit), increase staff at station, simplify the process at that station, or reduce demand arriving at that station.
  • The bottleneck can shift — if fryer capacity is added, assembly may become the new bottleneck. After any capacity change, re-measure all stations to identify the new binding constraint.

Response Options (in order of cost and disruption)

  1. Process improvement — can the bottleneck station work faster without new equipment? (batch differently, pre-stage more, reduce motion waste)
  2. Staffing — can an additional person be assigned to the bottleneck during peak? (C9)
  3. Schedule — can demand be smoothed away from the bottleneck peak? (promotions for off-peak, pre-ordering incentives)
  4. Equipment — is a second unit justified? Decision requires: cost of unit, installation downtime, space requirement (C1), and projected volume growth. Owner decision.

D6.8 — Capacity Investment Decision Rules

Model foundation: S4 (Transformation — capacity), S6 (C2a-d production capacity), S1 (N4 — shop capacity)

The Framework must define when current capacity needs expanding vs. when to manage demand within existing capacity. These rules prevent both premature investment and capacity-constrained service failures:

  • Investment trigger — when any production station exceeds 70% utilization during peak for 4 consecutive weeks AND demand trend is upward, begin formal capacity evaluation.
  • Evaluation criteria: (a) projected payback period — equipment cost divided by additional revenue enabled, (b) space availability — will the new unit fit within current C1?, (c) staff impact — does the new unit require additional staff (C9) or can existing staff operate it?, (d) installation disruption — how many days of reduced capacity during installation?
  • Decision authority — equipment purchases above the routine threshold (D4.2) require owner approval. Must include projected utilization at current and forecasted demand.
  • Manage demand first — before investing in capacity, exhaust demand-side options: smooth peak demand through pricing, promote off-peak ordering, reduce menu complexity at the bottleneck station. Capacity investment is the last resort, not the first response.
  • Pass-through items (T5) as capacity relief — the Model distinguishes pass-through (retail) from manufacturing (T1–T4). Pass-through items consume zero production capacity — only counter/serving capacity (C2d). If production stations are constrained, increasing the proportion of pass-through items on the menu (adding more drink options, snack items) generates revenue without adding production load. This is a capacity management strategy, not just a menu decision.
D7

Performance & Risk Management

How we measure, monitor, improve, and protect the supply chain

Model foundation: S8 (availability metrics), all Composite Phenomena, all constraints as failure points

D7.1 — Key Performance Indicators (KPIs)

KPIDefinitionTargetSourceFreq.
Menu Availability Rate% hours all menu items available98%+D2Daily
Item Fill Rate% orders fulfilled completely99%+D2+D6Daily
Order Cycle TimeAvg order to meal served<12 minD6Per order
Quality Compliance% meals meeting standard99%+D6Daily
Waste Rate% inventory discarded unused<5%D2Weekly
Supplier On-Time Rate% deliveries on schedule95%+D3+D5Per delivery
Supplier Quality Rate% deliveries passing inspection98%+D3+D5Per delivery
Forecast AccuracyDeviation forecast vs actualWithin ±15%D1Daily
Budget AdherenceActual spend vs budgetWithin 5%D4Monthly
Equipment Uptime% hours critical equipment functional99%+D6Daily
Stock Accuracy% items where count matches system98%+D2.4Per count
Shrinkage RateTotal loss as % of inventory value<2%D2.7Monthly
Inventory TurnsTimes inventory consumed/replaced per monthBy categoryD2.6Monthly
Food Cost %BOM ingredient cost as % of selling price, per menu itemPer P3.X alert thresholdsD1.5+D3Monthly (live in software)
Revenue per MealAverage revenue per meal servedTracked, not targetedD1.5Daily
Order Accuracy Rate% of outbound orders with correct items and quantities99%+D5.4Daily
Peak Station UtilizationHighest utilization % among production stations during peakMonitor; alert at 70%+D6.7Daily
Outbound Lead Time (LT12)Avg time from customer order to meal served<12 minD7.6Per order
Staging Waste Rate% of staged items (I6, I12) discarded unused<10%D2.9Daily
Supplier Capacity Alert CountNumber of supplier capacity signals detected0 preferredD3.8Monthly
Dependency Concentration% of critical items with sole-source supplyDecreasing trendD3.7Quarterly

D7.2 — Risk Register

RiskModel ElementProb.ImpactMitigation
Critical supplier failureS1 + Supply RiskLowCriticalBackup supplier (D3). 3–5 day buffer I2.
Equipment breakdownS6 (C10) + BottleneckMedCriticalPreventive maint (D6.3). Spares (I11). 4-hr SLA.
Refrigeration failureS6 (C10) + WasteLowCriticalTemp alarm. Emergency SLA. Insurance (D5.6).
Demand spikeS8 + StockoutMedModerateSafety stock (D2). Pace tracking (D1.3). Emergency orders (D4.2).
Customs delayS7 + S6 (C7)MedModerateOrder ahead. Larger safety stock. Air freight backup.
Staff shortageS6 (C9)MedModerateCross-train (D6.5). Reduce menu. Pre-prep more I12.
Food safety incidentS6 (C7) + QualityLowCriticalQuality checks (D6.4). FIFO. Temp monitoring. Recall protocol.
Power outageS6 (C10)LowCriticalUPS for refrigeration. Generator. Emergency closure.
Theft / shrinkageS5 + D2.7Low-MedModerateCycle counting (D2.4). Loss tracking. Investigation.
Insurance lapseD5.6LowHighAnnual review. Calendar reminders. Coverage vs D2.6 value.
Tier 2 supply disruptionS3 + S1 (upstream network)MedHighTier 2 visibility protocol (D3.7). Disclosure clause in critical supplier SLAs.
Shop total loss (fire/flood)S3 (single convergence point)Very LowCatastrophicBusiness continuity protocol (D3.7). Insurance (D5.6). Supplier pause protocol.
Bottleneck shift undetectedS6 + S4 (Bottleneck phenomenon)MedModerateWeekly peak utilization tracking (D6.7). Re-measure after any capacity change.
Outbound quality failureS2 (F4) + S8MedModerateOutbound quality gate (D5.4). Order accuracy tracking. Delivery complaint root-cause analysis.
Waste disposal non-complianceS2 (F9) + S6 (C7)LowHighWaste disposal governance (D3.9). Provider certification verified annually.
Constraint interaction unresolvedS6 (multiple constraints)MedModerateConstraint interaction table (D6.6). Checked on any constraint change.

D7.3 — Continuous Improvement

  • Weekly — daily KPIs reviewed. Below target = root cause + corrective action.
  • Monthly — supplier performance, spend, waste, forecast accuracy, stock accuracy, shrinkage. Adjust ROP, safety stock, forecasting.
  • Quarterly — supplier categorization, SKU classification matrix, contracts, equipment lifecycle, insurance. Assess Framework fit.
  • After-incident — what happened, why, impact, what changes. Update Risk Register.

D7.4 — Future Expansion Considerations

  • Network design — when a second location opens: warehouse location, DC strategy, buffer stock allocation.
  • 3PL (Third-Party Logistics) — at scale, outsourcing storage/delivery may be cost-effective.
  • WMS — our software IS the WMS. At scale, dedicated multi-location system may be needed.
  • Carrier management — if own delivery fleet: carrier selection, route optimization, fleet management.

D7.5 — Availability Equation Governance

Model foundation: S8 (Availability — the output of all primitives working together)

The Model traces availability to 8 inputs, each mapped to contributing primitives. D7.1 tracks the metrics. This section governs how the inputs interact to produce the availability output:

The Availability Inputs (from Model S8)

InputContributing PrimitivesGoverning DomainWhen This Input Fails
Inventory levelsS5D2Stockout → Item Fill Rate drops
Supplier reliabilityS1 + S2 + S7D3 + D5Late/short delivery → cascading stockout
Lead timesS7D7.6Extended lead time → safety stock insufficient
Storage capacityS6 + S5D2Cannot hold required buffer → forced under-ordering
Production capacityS4 + S6D6 + D6.7Bottleneck → Order Cycle Time exceeds target
Staff availabilityS6 (C9)D6.5Understaffed → reduced throughput at all stations
Equipment uptimeS6 (C10)D6.3Equipment down → partial or total production stop
Demand accuracyS8 feedback loopD1Forecast error → over-staging (waste) or under-staging (stockout)

Cascade Analysis

When any KPI drops below target, the root cause must be traced through the availability equation:

  • Menu Availability dropped? → check: was it inventory (D2)? Was inventory low because of supplier failure (D3/D5) or because demand exceeded forecast (D1)? Was demand underforecast because the forecast method failed (D1.2) or because an unknown event occurred?
  • Order Cycle Time exceeded? → check: was it a production bottleneck (D6.7)? Was the bottleneck caused by equipment failure (D6.3), staff shortage (C9), or demand spike beyond capacity?
  • The cascade trace is mandatory — when investigating a KPI failure, the investigation must follow the chain through the availability equation, not stop at the first symptom. "We ran out of beef" is a symptom. The root cause might be: forecast under-estimated Thursday demand (D1) → staged too few patties (D2.2) → could not restock because next delivery is Monday (D3, C5).

Feedback Loop Governance (S8 → D1)

  • Every availability failure feeds the next forecast — when a stockout, delay, or quality failure occurs, the circumstances (day, time, demand level, what failed) are recorded and become an input to D1.2 forecasting. This closes the feedback loop that the Model describes.
  • Monthly availability review — which inputs were binding this month? Rank by frequency and impact. The most frequently binding input gets priority improvement investment in D7.3.

D7.6 — Lead Time Governance

Model foundation: S7 (Lead Time — LT1 through LT13)

The Model defines 13 lead time elements with variability ratings. D3.5 tracks supplier lead time consistency. This section governs lead time as a managed system — including internal lead times that D3 does not cover.

External Lead Times (LT1–LT6, LT13)

  • Monitored via D3.5 — actual vs. promised, within +/-1 day, monthly.
  • Lead time change triggers — when a supplier's actual lead time consistently exceeds the promised lead time by more than 1 day for 3 consecutive deliveries: (a) safety stock must be recalculated using the actual (longer) lead time, not the promised one, (b) supplier is notified formally, (c) if the new lead time creates a shelf life conflict (D6.6 constraint interaction C3+C5), alternative sourcing or delivery frequency must be evaluated.
  • LT13 (Equipment failure to repair) — variability is "very high" (1 hour to 2 weeks). Governance beyond the 4-hour SLA: if repair is not complete within 4 hours, escalation tiers activate: (a) 4–8 hours: alternative production method identified (e.g. can burgers be served without fries if fryer is down?), (b) 8–24 hours: menu reduction implemented, customer communication issued, (c) >24 hours: emergency equipment procurement or rental evaluated, insurance claim initiated, (d) >1 week: temporary closure of affected production line, full insurance claim.

Internal Lead Times (LT7–LT12)

These are production and service lead times inside the shop. They are not supplier-dependent — they are operationally dependent:

Lead TimeProcessTargetMonitoringEscalation
LT7Thawed patty to cooked patty5–8 minSpot-check during peak>10 min consistently: investigate grill condition (D6.3), staff technique (D6.5)
LT8Frozen fries to cooked fries3–5 minSpot-check during peak>6 min: investigate fryer condition, oil quality, batch size
LT9Ingredients to assembled burger1–2 minTracked via Order Cycle Time>3 min: investigate station layout, ingredient accessibility, staff training
LT10Drink: storage to counter<1 minNo formal trackingIf delayed: cooler restocking missed (D2.2 staging)
LT11Sachets: storage to counter<1 minNo formal trackingIf delayed: restocking missed
LT12Customer order to meal served8–15 minEvery order (primary KPI)>15 min: decompose into LT7+LT8+LT9+queue time to identify which segment is slow
  • LT12 decomposition — when Order Cycle Time exceeds target, it must be broken down into its component lead times to identify the binding segment. LT12 = queue time + max(LT7, LT8) + LT9 + handoff time. The segment that contributes most to the overrun gets targeted.

D7.7 — Regulatory Compliance Register

Model foundation: S6 (C7 — Regulatory constraints)

The Model defines C7 (regulatory constraints: food safety, health inspections, halal certification). The Framework references C7 across D3.1, D5, D6.4, and D6.5. This section creates a single compliance register so regulatory obligations are not scattered and lost:

RegulationRequirementApplies ToEvidenceRenewalOwner
Food safety (HACCP)Hazard analysis and critical control points documented and followedKitchen operations, storage, receivingHACCP plan documentAnnual reviewShop manager
Health inspectionPremises pass local health authority inspectionEntire shopInspection certificatePer local schedule (typically annual)Shop manager
Halal certificationAll meat and relevant products halal-certifiedMeat supplier (SUP-001, SUP-011), dairySupplier halal certificatesPer certificate expiryShop manager via D3.1
Food handler certificationAll kitchen and receiving staff certifiedPersons A–GIndividual certificatesPer local requirement (typically annual)D6.5 training records
Waste disposal complianceWaste handled and disposed per local regulationsWaste provider (N6), kitchen waste processesProvider permits, segregation auditAnnual provider cert check (D3.9)Shop manager
Trade licenseValid business license to operateByteBurger entityLicense documentPer local renewal scheduleOwner
Fire safetyFire extinguishers, exits, suppression system compliantPremisesFire inspection certificateAnnualOwner
Insurance validityAll required insurance policies currentD5.6 insurance typesPolicy documentsAnnual review per D5.6Owner
  • Compliance calendar — all renewal dates entered into a calendar with 30-day advance reminders. Expired compliance = immediate escalation to owner.
  • Inspection readiness — the shop must be inspection-ready at all times, not just before a scheduled inspection. D6.4 quality checks ensure ongoing readiness.

D7.8 — Business Continuity

Model foundation: S3 (Network — single point of convergence), S6 (C10 equipment downtime), all critical constraints

Detailed governance for scenarios where the shop (the single convergence node) cannot operate normally. D3.7 identifies business continuity as a network-level risk. This section defines the response protocols:

Severity Levels

LevelDefinitionExamplesResponse
Level 1 — DegradedOne production station down but others operational. Can serve partial menu.Fryer failure (no fries), toaster failure (untoasted buns)Reduce menu to items that can still be produced. Notify customers of unavailable items. Activate D6.3 reactive maintenance. Log in D7.2.
Level 2 — Severely DegradedMultiple systems affected. Can serve very limited menu or at reduced capacity.Refrigeration failure affecting I1/I3/I5/I6, OR grill failure (no burgers), OR staff shortage below minimumAssess all perishable inventory. Implement emergency SLA. Reduce to minimal menu. Consider temporary closure for safety. Notify suppliers to pause next delivery.
Level 3 — Total ShutdownCannot operate at all.Fire, flood, power outage >2 hours with no generator, health authority closure order, multiple critical equipment failuresClose immediately. Secure premises. Notify: insurance (D5.6), all suppliers (pause deliveries), delivery platforms (suspend listing), customers (signage + social media). Owner notified immediately. Perishable inventory assessed within 4 hours.

Recovery Protocol

  • Level 1 — target recovery: same day. Normal operations resume when the failed station is restored. After-incident review in D7.3.
  • Level 2 — target recovery: 24–48 hours. If recovery exceeds 48 hours, escalate to Level 3 protocol. Owner involved in recovery decisions.
  • Level 3 — recovery timeline depends on cause. Insurance claim initiated immediately. Recovery plan created within 24 hours: what must be replaced, what can be salvaged, timeline to reopening. All inventory with expired shelf life during closure is written off (D2.3).
  • Post-incident — every Level 2 or 3 event triggers a formal after-incident review (D7.3): what happened, what failed, what would have reduced impact, what changes to make. Risk Register (D7.2) updated.
D8

Utilities, Facilities & Workforce

Inputs that are not ingredients but without which the shop cannot operate. The Model adds these as nodes (N13, N16), flows (F11, F14), and constraints (C14, C15); this domain governs them.

D8.1 — Utilities & Facilities

Model foundation: N13 (utility provider); F11 (utility flow); C14 (utilities reliability)
  • Utilities (power, water, gas, connectivity) are treated as critical managed inputs. Provider accounts, contacts, and outage hotlines are maintained.
  • Contingency — refrigeration is the priority load. A backup/generator or rapid-response plan covers outages beyond a defined threshold, linked to business continuity (D7.8, Level 2/3).
  • Utility cost is tracked as overhead and feeds margin governance (D2.10).

D8.2 — Workforce & Labor Management

Model foundation: N16 (labor source); F14 (labor flow); C15 (labor regulation); LT19 (onboarding)
  • Labor is a replenished resource, not just a limit. The roster covers all shifts with a defined minimum-staffing floor; falling below it is a business-continuity event (D7.8, Level 2).
  • Absence cover — a plan for sickness and no-shows; cross-training (D6.5) ensures no station depends on a single person.
  • Hiring pipeline — respects the onboarding lead time (LT19: qualify, onboard, sponsor) and UAE labor-law working-hours and visa/sponsorship compliance (D7.7).

D8.3 — Waste & Used-Oil Disposal

Model foundation: N15 (waste collector); C17 (waste/environmental); T8 (waste handling)
  • Governed jointly with D3.9. Used cooking oil and waste streams are segregated and handed to a licensed collector (N15) per C17, with documentation retained for compliance (D7.7).

Framework Summary

This Framework defines how ByteBurger’s supply chain is organized and governed:

ElementCountDescription
Governance domains8D1–D8
Demand channels3Walk-in, delivery app, catering
Customer governance (NEW)5 protocolsCommunication, feedback loop, complaint escalation (D1.4)
Revenue signals (NEW)4Revenue per meal, per hour, vs COGS, stockout cost (D1.5)
Replenishment rules13Per inventory category, consistent safety stock scale
Staging rules + governance (NEW)4 + principlesMovement triggers + staging governance (D2.9)
Stock accuracy method1Cycle counting with matrix-driven frequency
SKU classification9 cellsValue x Movement matrix (2 independent axes)
Inventory valuationFIFOAligned with physical FIFO rule
Loss control categories4Waste, damage, theft, admin error
Storage zones6Freezer, fridge, dry, cooler, back storage, kitchen
Supplier qualification8 criteriaLegal, quality, capacity, reliability, financial, terms, MOQ, schedule
Tendering processes3RFI, RFQ, RFP
Supplier categories4Critical, Important, Routine, Service
Contract elements4Negotiation, SLAs, duration, review
Supplier communication4 flow typesF5 forecasts, F6 expected info, F7 payment governance, F9 returns/credits
Network visibility (NEW)3 protocolsTier 2 visibility, dependency mapping, shop continuity (D3.7)
Node capacity monitoring (NEW)3 levelsCritical supplier, important supplier, shop self-monitoring (D3.8)
Waste disposal governance (NEW)5 rulesProvider as managed supplier, performance, compliance, oil, segregation (D3.9)
International sourcing5 processesIdentification, Incoterms, customs, duties, landed cost
Procurement cycle7 stepsNeed > Approval > PO > Confirm > Receipt > Match > Payment
Authorization levels4Auto, manager, senior, emergency
Logistics types7Inbound local/int'l, tracking, outbound (expanded), transport, insurance, reverse
Outbound quality gate (NEW)4 checksOrder accuracy, packaging integrity, temperature, delivery SLA (D5.4)
Insurance types5Transit int'l/local, stored, equipment, liability
Production stages7Pre-shift through bundling
Constraint interactions (NEW)5 documentedMOQ/storage, shelf/schedule, equipment/staff, hours/receiving, budget/stock (D6.6)
Bottleneck governance (NEW)4 thresholdsComfortable/monitor/warning/critical utilization bands (D6.7)
Capacity investment rules (NEW)5 criteriaTrigger, evaluation, authority, demand-first, pass-through relief (D6.8)
Quality points6Incoming, storage, prep, cooking, assembly, service
Training areas6Food safety, receiving, storage, equipment, emergency, waste
KPIs22 (was 13)Expanded: revenue, outbound, staging waste, bottleneck, dependency (D7.1)
Risks registered17 (was 10)Expanded: Tier 2, shop loss, bottleneck shift, outbound, waste, constraint (D7.2)
Availability equation (NEW)8 inputsTraced to primitives with cascade analysis and feedback loop (D7.5)
Lead time governance (NEW)13 elementsExternal + internal with decomposition rules (D7.6)
Regulatory register (NEW)8 regulationsHACCP, health, halal, food handler, waste, license, fire, insurance (D7.7)
Business continuity (NEW)3 severity levelsDegraded, severely degraded, total shutdown with recovery (D7.8)
Seasonal & Ramadan governance (NEW)3 patternsRamadan, Eid/holidays, seasonality (D1.6)
Cost & margin governance (NEW)4 controlsUnit/landed cost, food-cost target, waste cost, erosion trigger (D2.10)
Allergen & halal segregation (NEW)1 rulePhysical separation of halal/allergen stock (D2.11)
Cold chain integrity (NEW)3 checkpointsDispatch, dock, storage with excursion handling (D5.8)
Receiving inspection (NEW)accept/quarantine/rejectDock gate before stock is usable (D5.9)
Traceability & recall (NEW)batch/lot + FEFOLot capture and recall procedure (D5.10)
Utilities, facilities & workforce (NEW)D8 domainUtilities, labor, and waste as managed inputs (D8.1–D8.3)
Review cadences4Weekly, monthly, quarterly, after-incident
SOPsAll domainsEvery process documented as Standard Operating Procedures

This is the organizing logic. The Model describes what exists. This Framework defines how we manage it. Nothing here schedules a specific action — that is the Plan (Layer 3).

Decision flow: D1 → D2 → D3 → D4 → D5 → D6 → D7 → back to D1.

A Framework that fits the Model will make good plans easy to create and execute. A Framework that contradicts the Model will make every plan a struggle.

Status: DRAFT v5 — Extended to the Model Reality Layer (cost, cold chain, receiving/traceability, utilities, workforce, seasonal demand). Awaiting review.

Page 2 of 2