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:
| Domain | Governs | Model Elements Covered |
|---|---|---|
| D1 — Demand Management | How we understand, anticipate, and respond to customer demand | S8 (Availability), Demand Profile, S2 (F8 revenue, customer information) |
| D2 — Inventory Governance | How we decide what to hold, how much, where, and when to replenish; stock accuracy; classification; valuation; loss control | S5 (I1–I13), S6 (C1, C3), S7 (lead times) |
| D3 — Sourcing & Supplier Management | How we find, evaluate, select, contract, and manage supplier relationships including communication, forecasting, payments, and returns | S1 (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 & Ordering | How we execute buying — requisition, approval, order, confirm, receive, match, pay | S2 (F5, F6, F7), S6 (C4, C6) |
| D5 — Logistics & Receiving | How goods physically move, how we receive/inspect, track shipments, handle transport and insurance | S2 (F1–F4, F6 confirmations/schedules, F9 waste/returns), S3, S6 (C5, C7, C8), S7 |
| D6 — Operations & Transformation | How we manage production, prep, equipment, quality, and staff training | S4 (T1–T6), S5 (I12, I13), S6 (C2a–d, C9, C10), BOM |
| D7 — Performance & Risk Management | How we measure, monitor, improve, and protect the supply chain | S8 (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
Demand Management
How we understand, anticipate, and respond to customer demand
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:
| Channel | Characteristics | Visibility | Impact on Supply Chain |
|---|---|---|---|
| Walk-in | Unpredictable volume, real-time demand, no advance notice | Low — you see demand only when the customer is at the counter | Requires ready inventory and fast transformation; safety stock absorbs variability |
| Delivery App | Slightly more predictable, orders arrive digitally before preparation begins | Medium — you see the order before the customer arrives; possible to see order trends | Allows short preparation lead time; packaging (I10) consumption increases |
| Catering / Pre-orders | Known volume in advance, larger quantities, scheduled delivery time | High — demand is confirmed days or hours ahead | Allows 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)
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
| Scenario | Communication Rule | Who | Record |
|---|---|---|---|
| Menu item unavailable | Inform customer immediately. Offer substitute. Never let the customer discover it after ordering. | Counter staff | Logged as stockout event in D7 |
| Order delay beyond 12 min | Proactive update to customer at the 10-minute mark with revised estimate | Counter/delivery staff | Logged against Order Cycle Time KPI |
| Quality complaint | Acknowledge, replace immediately, log complaint with item, time, and nature of issue | Shift lead | Complaint log feeds D6.4 and D7.3 |
| Delivery app complaint | Respond within platform's SLA. Root-cause: was it kitchen (D6) or handoff (D5.4) or driver? | Shop manager | Tracked separately from walk-in complaints |
| Recurring complaint pattern | 3+ complaints on same item or issue in 7 days triggers root-cause investigation | Shop manager | Escalated 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)
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
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).
Inventory Governance
How we decide what to hold, how much, where, and when to replenish
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):
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. Category | Replenishment Logic | ROP Driver | Safety 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 life | Minimal — excess becomes waste within days. |
| I2 — Frozen Inputs | Order in larger batches. Lead time 1–2 days local, weeks international. | ROP = (daily usage × lead time) + safety stock | Moderate — 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 stock | Low — shelf life gives some flexibility. |
| I4 — Purchased Inputs (Ambient, 1–2 day life) | Order daily or every other day. | ROP = tomorrow’s forecasted need | Minimal — freshness paramount. |
| I5 — Inputs (Refrigerated, Long Life) | Order weekly or bi-weekly. | ROP = (weekly usage × lead time) + safety stock | Comfortable — long shelf life, low waste risk. |
| I6 — Staged Inputs (Thawed) | Not ordered — staged internally from I2. | Stage = today’s forecast + 15% buffer | Minimal — over-staging = waste within 1–3 days. |
| I7 — Inputs (Ambient, Long Life) | Order monthly or bi-monthly. | ROP = (monthly usage × lead time) + safety stock | Comfortable — very low waste risk. |
| I8 — Finished Goods for Resale | Order weekly. Long shelf life. | ROP = (weekly usage × lead time) + safety stock | Comfortable — main constraint is storage (C1). |
| I9 — MRO Equipment | Replaced on failure or scheduled lifecycle. | Trigger: age, condition, or failure | N/A — managed via D6.3. |
| I10 — MRO Consumable Supplies | Order weekly or bi-weekly. | ROP = (weekly consumption × lead time) + min stock | Moderate — stockout disrupts operations. |
| I11 — MRO Spare Parts | Critical spares on hand; non-critical on failure. | Binary: keep spare or accept risk | Binary — 1 spare or 0. |
| I12 — Working Stock (Daily Prep) | Prepared internally from I1, I3, I4, I5, I6. | Prep = today’s forecast + 10–20% buffer | Minimal — over-prepping = end-of-day waste. |
| I13 — Work-in-Progress | Exists only during active cooking. | Driven by real-time orders | N/A — managed by D6. |
D2.2 — Inventory Staging Rules
Staging is the planned movement between inventory categories:
| Staging Movement | Trigger | Timing | Quantity Rule |
|---|---|---|---|
| I2 (Frozen) → I6 (Thawed) | Daily production forecast for next day | End of shift, day before use | Next day’s forecast + 15% buffer. Never thaw more than 1.5 days of expected use. |
| I1 (Fresh) → I12 (Working Stock) | Start of shift prep routine | Before each service period | Forecast for upcoming service period + 10% buffer. |
| I3, I4, I5 → I12 (Working Stock) | Start of shift prep routine | Same as above | Forecast-driven. Cheese sliced, buns counted, sauces portioned. |
| I8 (Resale) → Cooler | Cooler stock drops below serving level | Throughout day as needed | Refill 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 Cell | Count Frequency | Rationale |
|---|---|---|
| High Value / High Movement | Daily or every 2–3 days | Highest cost and operational impact. Errors cause stockouts or significant waste. |
| High Value / Medium or Low Movement | Every 2–3 days | High cost per unit — even small discrepancies are expensive. |
| Medium Value / High Movement | Every 2–3 days | High consumption rate means errors compound quickly. |
| Medium Value / Medium Movement | Weekly | Balanced control. Weekly catches discrepancies before they compound. |
| Medium Value / Low Movement; Low Value / High Movement | Weekly | Either moderately costly or fast-moving. Weekly is sufficient. |
| Low Value / Medium or Low Movement | Monthly | Low per-item impact. Monthly catches trends. |
| MRO Equipment (I9) | Quarterly | Long-life assets. Physical presence verified periodically. |
| MRO Spare Parts (I11) | Monthly | Must 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 Movement | Medium Movement | Low Movement | |
|---|---|---|---|
| High Value | HV/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 Value | MV/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 Value | LV/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 Zone | Inventory Categories | Organization Rules |
|---|---|---|
| Freezer | I2 (Frozen inputs) | By item type. FIFO. Temperature monitored continuously. Capacity tracked (C1). |
| Refrigerator | I1 (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 storage | I4 (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 storage | I8 (Drinks — bulk), I10 (MRO consumables), I11 (Spare parts) | Labeled shelves/bins. Designated locations. Marked minimum stock levels. |
| Kitchen / Prep area | I12 (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
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
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
- 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).
Sourcing & Supplier Management
How we find, evaluate, select, contract, and manage suppliers — both local and international
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
| Criterion | What It Checks | Applies To |
|---|---|---|
| Legal compliance | Valid trade license, food handling permits, halal certification (GCC) | N1, N2 |
| Quality standards | Product samples, consistency, certifications (HACCP, ISO) | N1, N2 |
| Capacity | Can the supplier meet volume consistently? | N1, N2, N3 |
| Delivery reliability | On-time history, frequency options, proximity | N1, N2, N3 |
| Financial stability | Stable enough for long-term supply? | N1, N2, N3 |
| Payment terms | Credit period, payment methods, early payment discounts | N1, 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)
| Process | Full Name | When Used | What It Asks |
|---|---|---|---|
| RFI | Request for Information | Exploring the market — what suppliers exist and offer | General: products, capabilities, certifications. No pricing. |
| RFQ | Request for Quotation | You know what you need, want comparable pricing | Specific items, quantities, schedule. Suppliers respond with pricing, MOQs, lead times, terms. |
| RFP | Request for Proposal | Complex need or want full solution proposal | Open-ended: suppliers propose approach, pricing, SLAs, value-add. Used for N6 services and N3 equipment. |
D3.2 — Supplier Categorization
| Category | Definition | Examples | Management Approach |
|---|---|---|---|
| Critical | Single/limited-source for core menu items | Meat supplier, bun supplier | Close relationship, backup identified, weekly monitoring, favorable terms |
| Important | Support operations, alternatives available | Produce, dairy, beverage distributor | Monthly monitoring, 1–2 alternatives identified, standard terms |
| Routine | Easily replaceable commodities | Cleaning supplies, packaging, sachets | Price-driven, switch easily, minimal relationship management |
| Service | Non-material service providers | Equipment 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
| Component | Duration | Variability |
|---|---|---|
| Supplier preparation | 1–4 weeks | Medium |
| Sea freight | 2–6 weeks | Medium-high |
| Air freight | 2–5 days | Low (expensive) |
| Customs clearance | 1–7 days | High |
| Local delivery | 1–2 days | Low |
| Total (sea) | 4–13 weeks | High |
| Total (air) | 1–2 weeks | Medium |
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
| Metric | Definition | Target | Frequency |
|---|---|---|---|
| On-Time Delivery Rate | % of deliveries on schedule | 95%+ | Every delivery |
| Quality Acceptance Rate | % passing receiving inspection | 98%+ | Every delivery |
| Order Accuracy | % matching PO in item and quantity | 99%+ | Every delivery |
| Lead Time Consistency | Actual vs. promised | Within ±1 day | Monthly |
| Responsiveness | Speed of response to inquiries/complaints | Qualitative | Quarterly |
| Contract Compliance | Adherence to SLA terms | Full compliance | Quarterly |
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
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 Type | Definition | Risk Level | Governance Rule |
|---|---|---|---|
| Sole source | Only one supplier can provide this item | Critical | Backup supplier must be identified and pre-qualified (D3.1). If no backup exists, safety stock increased to cover supplier lead time x 2. |
| Dual source | Two suppliers available, one primary | Moderate | Secondary supplier relationship maintained: annual qualification check, test order at least once per year. |
| Multi-source | Three or more suppliers available | Low | Price-driven selection. Switch on performance or cost. |
| Internal dependency | Item produced internally (I12, I13) from upstream inputs | Inherited | Risk 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
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)
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.
Procurement & Ordering
How we execute the buying cycle — from need identification to payment
Procurement is transactional. D3 decides who and on what terms. D4 executes the buying.
D4.1 — The Procurement Cycle
| Step | Action | Trigger | Output |
|---|---|---|---|
| 1. Need identification | Inventory hits ROP (D2) or specific need arises | Inventory monitoring or manual request | Purchase Requisition (PR): what, how much, by when |
| 2. Approval | PR reviewed against budget (C6) and authorization thresholds (D4.2) | PR created | Approved or rejected PR |
| 3. Purchase Order (PO) | Approved PR converted to PO, sent to supplier | Approved PR | PO sent (F5): item, quantity, price, delivery date, location, PO number |
| 4. Confirmation | Supplier confirms fulfillment | PO received by supplier | Confirmation (F6). If unable, escalate. |
| 5. Goods receipt | Delivery inspected, accepted/rejected (D5) | Physical delivery | GRN: what received, quantity, condition, discrepancies |
| 6. Invoice matching | Three-way match: PO vs. GRN vs. invoice | Invoice received | Matched = approved for payment. Mismatch = flagged. |
| 7. Payment | Payment per agreed terms | Approved invoice + terms met | Payment (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 Value | Authorization | Rationale |
|---|---|---|
| Below routine threshold (standing orders, consumables) | Auto-approved within standing order parameters | High frequency, low value, pre-negotiated. |
| Above routine, within monthly budget | Shop manager approval | Budget compliance and need validation. |
| Exceeds budget or non-standard purchase | Owner / senior management | Prevents overrun, ensures strategic alignment. |
| Emergency orders | Shop manager + documented justification | Speed + 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).
Logistics & Receiving
How goods physically move, how they are received, tracked, transported, and insured
Logistics governs physical movement. Uses inbound (coming in) and outbound (going out) from ByteBurger’s perspective.
D5.1 — Inbound Logistics (Local Suppliers)
| Step | What Happens | Who | Rules |
|---|---|---|---|
| Delivery arrival | Supplier vehicle arrives during receiving window | Supplier driver | C8 window (7–10am). Outside = refused unless pre-arranged. |
| Receiving inspection | Inspect against PO: items, quantity, quality, temperature | Shop staff (receiver) | Temp check for I1, I2, I3, I5, I6. Reject above threshold. |
| Documentation | GRN completed. Discrepancies recorded. | Shop staff | GRN refs PO. Discrepancies communicated same day. Damage logged (D2.7). |
| Put-away | Goods to correct storage per D2.8 | Shop staff | FIFO maintained. Items labeled with receipt/expiry date. |
D5.2 — Inbound Logistics (International Suppliers)
| Step | What Happens | Who | Key Documents |
|---|---|---|---|
| Freight booking | Arrange sea/air freight | Forwarder or supplier (per Incoterm) | Booking confirmation, schedule |
| In-transit tracking | Monitor shipment location, ETA | Buyer or forwarder | Bill of lading / airway bill, tracking number |
| Port arrival | Goods arrive at destination | Port authority | Arrival notice |
| Customs clearance (التخليص الجمركي) | Submit docs, pay duties, clear | Customs broker | Commercial invoice, packing list, CoO, health certs, halal cert, HS code |
| Local delivery | Cleared goods to ByteBurger | Local transport | Delivery note |
| Receiving at shop | Same as D5.1 | Shop staff | GRN 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)
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.
| Channel | Process | Packaging | Quality Rules |
|---|---|---|---|
| Walk-in (dine-in) | Assembled at counter, served directly | Tray, wrapping, fry containers | Served within 2 min of assembly. Temperature maintained. |
| Walk-in (takeaway) | Packaged for transport | Takeaway bag, secure packaging | + packaging integrity check before handoff |
| Delivery app | Packaged, handed to driver | Sealed bag, drink secured | Temperature 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
| Scenario | When | Decision Rules | Requirements |
|---|---|---|---|
| Emergency supplier pickup | Stockout risk, supplier can’t deliver outside schedule | Cost of lost sales vs. trip cost. Only for high-value/high-movement items. | Vehicle, staff assigned, fastest route, receipt collected |
| Equipment transport for repair | Equipment 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 pickup | Urgent MRO need not available through normal delivery | Only when stockout impacts today’s operations | Staff assigned, receipt collected, logged as emergency (D4.2) |
| Catering delivery | Customer orders delivery to their location | Delivery pricing, route, timing commitment | Suitable vehicle, insulated packaging, delivery confirmation |
D5.6 — Insurance
| Type | Covers | When Required |
|---|---|---|
| Goods in transit (int’l) | Loss/damage during international shipping | All international shipments. Coverage per Incoterm. |
| Goods in transit (local) | Loss/damage during supplier delivery or own pickup | Supplier delivery: supplier covers. Own pickups (D5.5): business insurance. |
| Stored inventory | Loss from fire, flood, theft, equipment failure | Business insurance. Coverage set by D2.6 valuation. |
| Equipment | Damage/breakdown of MRO equipment (I9) | Business policy. Critical equipment specifically covered. |
| Liability | Third-party claims from food safety or delivery incidents | Required 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
- 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
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
- 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).
Operations & Transformation
How we manage production, preparation, equipment, quality, and staff training
D6.1 — Production Workflow
| Stage | Activity | Input | Output | Constraint |
|---|---|---|---|---|
| Pre-shift prep | Thaw beef (I2→I6), chop veg (I1→I12), portion sauces, count buns | I1,I2,I3,I4,I5 | I6, I12 | C9 (staff) |
| Grill (T1) | Cook thawed patties | I6 | Cooked patty | C2a |
| Fryer (T2) | Deep fry fries and other fried items | I2 (frozen fries) | Cooked fries | C2b |
| Toasting (T3) | Toast buns | I4 | Toasted bun | Grill/toaster |
| Assembly (T4) | Assemble burger from components | Cooked patty + bun + I12 | Complete burger | C2c |
| Pass-through (T5) | Stage drinks/sachets to counter | I8 | Ready for sale | Near-zero (LT10,LT11) |
| Bundling (T6) | Combine into combo with packaging | Burger+fries+drink+I10 | Customer meal | C2d |
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
| Type | Covers | Frequency | Who |
|---|---|---|---|
| Preventive maintenance | Scheduled cleaning, inspection, servicing | Daily clean, weekly deep clean, monthly professional for critical equipment | Daily: kitchen staff. Monthly: N6 |
| Reactive maintenance | Repair of broken equipment | On failure | N6 or N3. Critical: 4-hour SLA. |
| Spare parts | Ensure critical spares (I11) available | Monthly via cycle count (D2.4) | Shop manager |
| Equipment lifecycle | Track age, plan replacement | Annual review | Compare against Item Master lifespan |
D6.4 — Quality Management
| Quality Point | Checked | Standard | On Failure |
|---|---|---|---|
| Incoming (D5) | Temperature, freshness, packaging, correct items | Cold chain: ≤4°C refrigerated, ≤-18°C frozen. No damage. | Reject. GRN. Notify supplier. Log D2.7. |
| Storage (D2) | Temperature, FIFO, shelf life | Fridge/freezer in range. No expired items. | Remove expired. Adjust or escalate D6.3. |
| Prep (D6) | Freshness, cleanliness, portion accuracy | I12 passes visual/smell test. Portions match quantities defined in the Bill of Materials (BOM). | Discard substandard. Re-prep. |
| Cooking (D6) | Temperature, time, appearance | Patty ≥74°C internal. Fries golden. Bun toasted evenly. | Discard, re-cook. Investigate if recurring. |
| Assembly (D6) | Correct components, presentation, packaging | Every component listed in the Bill of Materials present. Clean packaging. | Reassemble. Coach staff. |
| Service (D1/D6) | Speed, accuracy, temperature | Cycle time ≤12 min (S8). Correct order. Hot food hot. | Remake. Track in D7. |
D6.5 — Staff Training & Certification
| Area | Covers | Who | Frequency |
|---|---|---|---|
| Food safety & hygiene | HACCP, hygiene, cross-contamination, temperature, allergens | All kitchen and receiving staff | On hire + annual. Certification where required (C7). |
| Receiving & inspection | Inspect deliveries, GRN, discrepancies, temperature checks | Receiving-duty staff | On hire + SOP changes |
| Storage & FIFO | Put-away, FIFO, labeling, storage zones (D2.8) | All inventory handlers | On hire + quarterly |
| Equipment operation | Safe use of grill, fryer, toaster, fridge, POS | All kitchen staff | On hire + new equipment |
| Emergency procedures | Equipment failure response, emergency ordering (D4.2), fire, power outage | All staff | On hire + semi-annual drill |
| Waste management | Waste logging, expiry checks, disposal, FIFO | All kitchen and storage staff | On 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
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
| Interaction | Constraints | Conflict | Resolution Rule |
|---|---|---|---|
| MOQ vs Storage | C4 + C1 | Supplier requires more than storage allows | Negotiate 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 Schedule | C3 + C5 | Item expires before next delivery | Calculate 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 Staff | C2a-d + C9 | Equipment capacity exceeds staff ability to operate it | Actual 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 Receiving | C8 + C5 | Deliveries arrive after receiving window closes | Late 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 Stock | C6 + C1 + C3 | Budget cannot support the safety stock that shelf life and storage require | Prioritize 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
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)
- Process improvement — can the bottleneck station work faster without new equipment? (batch differently, pre-stage more, reduce motion waste)
- Staffing — can an additional person be assigned to the bottleneck during peak? (C9)
- Schedule — can demand be smoothed away from the bottleneck peak? (promotions for off-peak, pre-ordering incentives)
- 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
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.
Performance & Risk Management
How we measure, monitor, improve, and protect the supply chain
D7.1 — Key Performance Indicators (KPIs)
| KPI | Definition | Target | Source | Freq. |
|---|---|---|---|---|
| Menu Availability Rate | % hours all menu items available | 98%+ | D2 | Daily |
| Item Fill Rate | % orders fulfilled completely | 99%+ | D2+D6 | Daily |
| Order Cycle Time | Avg order to meal served | <12 min | D6 | Per order |
| Quality Compliance | % meals meeting standard | 99%+ | D6 | Daily |
| Waste Rate | % inventory discarded unused | <5% | D2 | Weekly |
| Supplier On-Time Rate | % deliveries on schedule | 95%+ | D3+D5 | Per delivery |
| Supplier Quality Rate | % deliveries passing inspection | 98%+ | D3+D5 | Per delivery |
| Forecast Accuracy | Deviation forecast vs actual | Within ±15% | D1 | Daily |
| Budget Adherence | Actual spend vs budget | Within 5% | D4 | Monthly |
| Equipment Uptime | % hours critical equipment functional | 99%+ | D6 | Daily |
| Stock Accuracy | % items where count matches system | 98%+ | D2.4 | Per count |
| Shrinkage Rate | Total loss as % of inventory value | <2% | D2.7 | Monthly |
| Inventory Turns | Times inventory consumed/replaced per month | By category | D2.6 | Monthly |
| Food Cost % | BOM ingredient cost as % of selling price, per menu item | Per P3.X alert thresholds | D1.5+D3 | Monthly (live in software) |
| Revenue per Meal | Average revenue per meal served | Tracked, not targeted | D1.5 | Daily |
| Order Accuracy Rate | % of outbound orders with correct items and quantities | 99%+ | D5.4 | Daily |
| Peak Station Utilization | Highest utilization % among production stations during peak | Monitor; alert at 70%+ | D6.7 | Daily |
| Outbound Lead Time (LT12) | Avg time from customer order to meal served | <12 min | D7.6 | Per order |
| Staging Waste Rate | % of staged items (I6, I12) discarded unused | <10% | D2.9 | Daily |
| Supplier Capacity Alert Count | Number of supplier capacity signals detected | 0 preferred | D3.8 | Monthly |
| Dependency Concentration | % of critical items with sole-source supply | Decreasing trend | D3.7 | Quarterly |
D7.2 — Risk Register
| Risk | Model Element | Prob. | Impact | Mitigation |
|---|---|---|---|---|
| Critical supplier failure | S1 + Supply Risk | Low | Critical | Backup supplier (D3). 3–5 day buffer I2. |
| Equipment breakdown | S6 (C10) + Bottleneck | Med | Critical | Preventive maint (D6.3). Spares (I11). 4-hr SLA. |
| Refrigeration failure | S6 (C10) + Waste | Low | Critical | Temp alarm. Emergency SLA. Insurance (D5.6). |
| Demand spike | S8 + Stockout | Med | Moderate | Safety stock (D2). Pace tracking (D1.3). Emergency orders (D4.2). |
| Customs delay | S7 + S6 (C7) | Med | Moderate | Order ahead. Larger safety stock. Air freight backup. |
| Staff shortage | S6 (C9) | Med | Moderate | Cross-train (D6.5). Reduce menu. Pre-prep more I12. |
| Food safety incident | S6 (C7) + Quality | Low | Critical | Quality checks (D6.4). FIFO. Temp monitoring. Recall protocol. |
| Power outage | S6 (C10) | Low | Critical | UPS for refrigeration. Generator. Emergency closure. |
| Theft / shrinkage | S5 + D2.7 | Low-Med | Moderate | Cycle counting (D2.4). Loss tracking. Investigation. |
| Insurance lapse | D5.6 | Low | High | Annual review. Calendar reminders. Coverage vs D2.6 value. |
| Tier 2 supply disruption | S3 + S1 (upstream network) | Med | High | Tier 2 visibility protocol (D3.7). Disclosure clause in critical supplier SLAs. |
| Shop total loss (fire/flood) | S3 (single convergence point) | Very Low | Catastrophic | Business continuity protocol (D3.7). Insurance (D5.6). Supplier pause protocol. |
| Bottleneck shift undetected | S6 + S4 (Bottleneck phenomenon) | Med | Moderate | Weekly peak utilization tracking (D6.7). Re-measure after any capacity change. |
| Outbound quality failure | S2 (F4) + S8 | Med | Moderate | Outbound quality gate (D5.4). Order accuracy tracking. Delivery complaint root-cause analysis. |
| Waste disposal non-compliance | S2 (F9) + S6 (C7) | Low | High | Waste disposal governance (D3.9). Provider certification verified annually. |
| Constraint interaction unresolved | S6 (multiple constraints) | Med | Moderate | Constraint 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
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)
| Input | Contributing Primitives | Governing Domain | When This Input Fails |
|---|---|---|---|
| Inventory levels | S5 | D2 | Stockout → Item Fill Rate drops |
| Supplier reliability | S1 + S2 + S7 | D3 + D5 | Late/short delivery → cascading stockout |
| Lead times | S7 | D7.6 | Extended lead time → safety stock insufficient |
| Storage capacity | S6 + S5 | D2 | Cannot hold required buffer → forced under-ordering |
| Production capacity | S4 + S6 | D6 + D6.7 | Bottleneck → Order Cycle Time exceeds target |
| Staff availability | S6 (C9) | D6.5 | Understaffed → reduced throughput at all stations |
| Equipment uptime | S6 (C10) | D6.3 | Equipment down → partial or total production stop |
| Demand accuracy | S8 feedback loop | D1 | Forecast 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
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 Time | Process | Target | Monitoring | Escalation |
|---|---|---|---|---|
| LT7 | Thawed patty to cooked patty | 5–8 min | Spot-check during peak | >10 min consistently: investigate grill condition (D6.3), staff technique (D6.5) |
| LT8 | Frozen fries to cooked fries | 3–5 min | Spot-check during peak | >6 min: investigate fryer condition, oil quality, batch size |
| LT9 | Ingredients to assembled burger | 1–2 min | Tracked via Order Cycle Time | >3 min: investigate station layout, ingredient accessibility, staff training |
| LT10 | Drink: storage to counter | <1 min | No formal tracking | If delayed: cooler restocking missed (D2.2 staging) |
| LT11 | Sachets: storage to counter | <1 min | No formal tracking | If delayed: restocking missed |
| LT12 | Customer order to meal served | 8–15 min | Every 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
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:
| Regulation | Requirement | Applies To | Evidence | Renewal | Owner |
|---|---|---|---|---|---|
| Food safety (HACCP) | Hazard analysis and critical control points documented and followed | Kitchen operations, storage, receiving | HACCP plan document | Annual review | Shop manager |
| Health inspection | Premises pass local health authority inspection | Entire shop | Inspection certificate | Per local schedule (typically annual) | Shop manager |
| Halal certification | All meat and relevant products halal-certified | Meat supplier (SUP-001, SUP-011), dairy | Supplier halal certificates | Per certificate expiry | Shop manager via D3.1 |
| Food handler certification | All kitchen and receiving staff certified | Persons A–G | Individual certificates | Per local requirement (typically annual) | D6.5 training records |
| Waste disposal compliance | Waste handled and disposed per local regulations | Waste provider (N6), kitchen waste processes | Provider permits, segregation audit | Annual provider cert check (D3.9) | Shop manager |
| Trade license | Valid business license to operate | ByteBurger entity | License document | Per local renewal schedule | Owner |
| Fire safety | Fire extinguishers, exits, suppression system compliant | Premises | Fire inspection certificate | Annual | Owner |
| Insurance validity | All required insurance policies current | D5.6 insurance types | Policy documents | Annual review per D5.6 | Owner |
- 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
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
| Level | Definition | Examples | Response |
|---|---|---|---|
| Level 1 — Degraded | One 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 Degraded | Multiple 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 minimum | Assess all perishable inventory. Implement emergency SLA. Reduce to minimal menu. Consider temporary closure for safety. Notify suppliers to pause next delivery. |
| Level 3 — Total Shutdown | Cannot operate at all. | Fire, flood, power outage >2 hours with no generator, health authority closure order, multiple critical equipment failures | Close 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.
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
- 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
- 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
- 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:
| Element | Count | Description |
|---|---|---|
| Governance domains | 8 | D1–D8 |
| Demand channels | 3 | Walk-in, delivery app, catering |
| Customer governance (NEW) | 5 protocols | Communication, feedback loop, complaint escalation (D1.4) |
| Revenue signals (NEW) | 4 | Revenue per meal, per hour, vs COGS, stockout cost (D1.5) |
| Replenishment rules | 13 | Per inventory category, consistent safety stock scale |
| Staging rules + governance (NEW) | 4 + principles | Movement triggers + staging governance (D2.9) |
| Stock accuracy method | 1 | Cycle counting with matrix-driven frequency |
| SKU classification | 9 cells | Value x Movement matrix (2 independent axes) |
| Inventory valuation | FIFO | Aligned with physical FIFO rule |
| Loss control categories | 4 | Waste, damage, theft, admin error |
| Storage zones | 6 | Freezer, fridge, dry, cooler, back storage, kitchen |
| Supplier qualification | 8 criteria | Legal, quality, capacity, reliability, financial, terms, MOQ, schedule |
| Tendering processes | 3 | RFI, RFQ, RFP |
| Supplier categories | 4 | Critical, Important, Routine, Service |
| Contract elements | 4 | Negotiation, SLAs, duration, review |
| Supplier communication | 4 flow types | F5 forecasts, F6 expected info, F7 payment governance, F9 returns/credits |
| Network visibility (NEW) | 3 protocols | Tier 2 visibility, dependency mapping, shop continuity (D3.7) |
| Node capacity monitoring (NEW) | 3 levels | Critical supplier, important supplier, shop self-monitoring (D3.8) |
| Waste disposal governance (NEW) | 5 rules | Provider as managed supplier, performance, compliance, oil, segregation (D3.9) |
| International sourcing | 5 processes | Identification, Incoterms, customs, duties, landed cost |
| Procurement cycle | 7 steps | Need > Approval > PO > Confirm > Receipt > Match > Payment |
| Authorization levels | 4 | Auto, manager, senior, emergency |
| Logistics types | 7 | Inbound local/int'l, tracking, outbound (expanded), transport, insurance, reverse |
| Outbound quality gate (NEW) | 4 checks | Order accuracy, packaging integrity, temperature, delivery SLA (D5.4) |
| Insurance types | 5 | Transit int'l/local, stored, equipment, liability |
| Production stages | 7 | Pre-shift through bundling |
| Constraint interactions (NEW) | 5 documented | MOQ/storage, shelf/schedule, equipment/staff, hours/receiving, budget/stock (D6.6) |
| Bottleneck governance (NEW) | 4 thresholds | Comfortable/monitor/warning/critical utilization bands (D6.7) |
| Capacity investment rules (NEW) | 5 criteria | Trigger, evaluation, authority, demand-first, pass-through relief (D6.8) |
| Quality points | 6 | Incoming, storage, prep, cooking, assembly, service |
| Training areas | 6 | Food safety, receiving, storage, equipment, emergency, waste |
| KPIs | 22 (was 13) | Expanded: revenue, outbound, staging waste, bottleneck, dependency (D7.1) |
| Risks registered | 17 (was 10) | Expanded: Tier 2, shop loss, bottleneck shift, outbound, waste, constraint (D7.2) |
| Availability equation (NEW) | 8 inputs | Traced to primitives with cascade analysis and feedback loop (D7.5) |
| Lead time governance (NEW) | 13 elements | External + internal with decomposition rules (D7.6) |
| Regulatory register (NEW) | 8 regulations | HACCP, health, halal, food handler, waste, license, fire, insurance (D7.7) |
| Business continuity (NEW) | 3 severity levels | Degraded, severely degraded, total shutdown with recovery (D7.8) |
| Seasonal & Ramadan governance (NEW) | 3 patterns | Ramadan, Eid/holidays, seasonality (D1.6) |
| Cost & margin governance (NEW) | 4 controls | Unit/landed cost, food-cost target, waste cost, erosion trigger (D2.10) |
| Allergen & halal segregation (NEW) | 1 rule | Physical separation of halal/allergen stock (D2.11) |
| Cold chain integrity (NEW) | 3 checkpoints | Dispatch, dock, storage with excursion handling (D5.8) |
| Receiving inspection (NEW) | accept/quarantine/reject | Dock gate before stock is usable (D5.9) |
| Traceability & recall (NEW) | batch/lot + FEFO | Lot capture and recall procedure (D5.10) |
| Utilities, facilities & workforce (NEW) | D8 domain | Utilities, labor, and waste as managed inputs (D8.1–D8.3) |
| Review cadences | 4 | Weekly, monthly, quarterly, after-incident |
| SOPs | All domains | Every 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.
Page 2 of 2