Coder Legion - Recent posts tagged forecasting

S&OP Engineering II: Demand Planning from Guessing to Probability

Sat, 28 Mar 2026 16:18:34 +0000

Your Excel says "we'll sell 100 units." A round, clean, deterministic number. What if you sell 120? Stockout, unhappy customer, contractual penalty. What if you sell 50? 50 units sitting in your warehouse, immobilizing capital that could be generating returns.

The problem isn't the forecast itself. It's the arrogance of the single number.

In Chapter 1 we built a "Quality Valve" that filters ERP noise. Now that we have a pure signal, we're going to do something Excel can't: measure uncertainty.

Executive Summary: A probabilistic forecast doesn't tell you "you'll sell 100." It tells you "with 95% probability, you'll sell between 35 and 157." That uncertainty band is the mathematical foundation for calculating your Safety Stock without resorting to rules of thumb.

The Architecture: MLOps, Not Scripts

We haven't written a throwaway script. We've connected our mathematical brain (Python/Prophet) directly to our Single Source of Truth (Supabase/PostgreSQL).

The key design is the demand_forecasts table. Notice one column that separates this from a basic tutorial:

CREATE TABLE demand_forecasts (
    id              UUID PRIMARY KEY DEFAULT uuid_generate_v4(),
    execution_date  DATE NOT NULL,     -- ← When we ran the model
    ds              DATE NOT NULL,     -- Predicted future date
    yhat            NUMERIC NOT NULL,  -- Central prediction
    yhat_lower      NUMERIC NOT NULL,  -- Lower bound (Safety Stock)
    yhat_upper      NUMERIC NOT NULL,  -- Upper bound (Risk)
    model_version   TEXT NOT NULL,     -- Traceability
    UNIQUE(execution_date, ds)         -- One forecast per execution and date
);

Why execution_date? Because in 6 months, when you want to audit whether your model was accurate, you need to know when you made the prediction versus what actually happened. This is what MLOps calls Snapshotting: recording the context of each execution to evaluate model drift over time.

Without this column, you have a model. With it, you have an auditable system.

The Engineering: Why Prophet (and Not a Textbook ARIMA)

Prophet is a time series engine developed by Meta, designed for irregular business data: gaps, holidays, trend changes. Exactly what a real supply chain has.

Here's the core fragment from our ProphetPredictor class:

def train_model(self, country_code='ES'):
    """
    Trains Prophet with two key S&OP configurations:
    - interval_width: Confidence interval width
    - country_holidays: Country operational context
    """
    self.model = Prophet(
        interval_width=0.95,     # ← 95% confidence interval
        weekly_seasonality=True,
        yearly_seasonality=True
    )
    # Holidays that alter loading/unloading patterns
    self.model.add_country_holidays(country_name=country_code)
    self.model.fit(self.ts_df)

Two engineering decisions that separate us from a YouTube tutorial:

interval_width=0.95: This is not a decorative parameter. The upper bound (yhat_upper) represents the maximum probable demand with 95% confidence. This is literally your calculation basis for Safety Stock: Safety Stock = yhat_upper - yhat. Without this interval, your safety stock is a gut feeling; with it, it's mathematics.

add_country_holidays('ES'): In S&OP, holidays aren't "days off." They're operational anomalies: the factory closes, the warehouse doesn't dispatch, transportation stops. If the model doesn't know that August 15th is a national holiday in Spain, it will interpret the drop in orders as a downward trend. This corrupts the September prediction.

Translating Math into Business Decisions

Theory is nice. But a CEO doesn't approve budgets based on Python code. They need visual evidence.

The Probabilistic Forecast

The black dots are your actual historical demand. The central blue line is the prediction (yhat). The shaded band is the 95% confidence interval. The greater the historical volatility, the wider the band → the more Safety Stock you need → the more cash you immobilize. This band is the conversation you should be having with your CFO.

Explainability: Separating Trend from Seasonal Noise

This is XAI (Explainable AI) applied to business. The model separates Trend (is the business growing or shrinking?) from Seasonality (are there spikes by time of year?) and holiday effects. This is what the CEO needs to see to approve the operations plan: knowing whether growth is real or just a calendar effect.

Open Kitchen: Try It Yourself

I distrust articles I can't execute. That's why I've prepared an isolated environment where you can train the model on an anonymized snapshot of the data we just cleaned in Chapter 1.

You don't need to install Python, Prophet, or configure Supabase. You just need a browser:

Open the interactive Notebook on Google Colab

Hit "Play" on the cells and watch a probabilistic forecast with uncertainty bands being generated. Modify the horizon, the country, the confidence interval. Do engineering, not faith.

Next Step: From Prediction to Decision

Now we know the probability of what we're going to sell. The question shifts from "how much will we sell?" to "what should we manufacture or purchase to maximize margin and minimize risk?".

In Chapter 3, we'll introduce Mathematical Optimization (PuLP) and Theory of Constraints to transform predictions into supply decisions: how much to buy, when to produce, and how to distribute finite resources while minimizing costs.

The difference between an Operations Director who reacts and one who decides is a mathematical model between the data and the action.

Forecast Kebutuhan Bahan & Produksi Konveksi dengan Python (Praktis + Template)

Sun, 08 Mar 2026 17:00:00 +0000

Di konveksi, “ramai order” bukan selalu kabar baik—kalau stok kain meleset, jadwal jahit jadi chaos, dan vendor bahan mulai susah diajak senyum. Industri manufaktur (termasuk apparel) makin banyak mengadopsi smart production planning untuk menekan biaya dan menaikkan akurasi keputusan, seperti dibahas dalam artikel tentang perencanaan produksi cerdas di FMIPA Unpad. Kalau Anda pernah “kehabisan kain 2 roll” atau “kebanyakan stok warna yang salah”, artikel ini akan jadi playbook yang bisa dipraktikkan—dan kita akan menutup paragraf ini dengan satu frasa yang akan jadi kompas SEO sekaligus kompas kerja: forecast kebutuhan bahan python.

Dari sisi ilmiah, praktik peramalan permintaan (demand forecasting) yang memadukan data historis dan fitur kontekstual sudah jadi fondasi kuat di supply chain modern; salah satu rujukan riset yang relevan bisa Anda jadikan landasan adalah artikel di ScienceDirect tentang demand forecasting. Kita mengangkat tema ini karena banyak developer (dan founder) membangun sistem order tapi lupa “otak belakangnya”: perencanaan bahan, capacity planning, dan jadwal produksi yang data-driven—padahal di lapangan, itu yang menentukan order selesai tepat waktu.

“Kalau data order sudah rapi, stok bahan seharusnya bisa diprediksi. Kalau stok bisa diprediksi, jadwal produksi bisa diatur. Kalau jadwal teratur, reputasi naik.”
Ringkasnya: kita tidak sedang membahas “sekadar analitik”, tapi cara membuat operasional konveksi terasa seperti product engineering—ada metrik, ada logika, ada iterasi.

1. Kenapa Konveksi Perlu Forecast, Bukan Tebak-Tebakan

Di banyak bisnis konveksi, pengambilan keputusan bahan masih mengandalkan intuisi: “bulan lalu laku, bulan ini pasti laku.” Masalahnya, pola permintaan seragam kerja, jersey event, sampai pakaian muslim sering dipengaruhi kalender (lebaran, wisuda, agenda HR, event olahraga), tren desain, bahkan lead time vendor. Di sinilah forecast kebutuhan bahan python jadi alat bantu: bukan untuk meramal masa depan secara mistis, tapi untuk mengurangi variance keputusan.

Apa yang Biasanya “Bocor” di Alur Produksi

Overstock: kain numpuk, cashflow ketahan.
Stockout: produksi berhenti, deadline kacau.
Mismatch spesifikasi: warna/gramasi salah karena reorder buru-buru.
Bottleneck jahit/finishing: bahan ada, kapasitas tidak siap.

Sinyal Data yang Sering Diabaikan

Tanggal PO vs tanggal delivery (indikator lead time real).
Ukuran dominan (S/M/L/XL) per klien/per industri.
Rasio reject/QC (pengaruh ke kebutuhan kain ekstra).

2. Data Minimal yang Anda Butuhkan (Dan Cara Menyusunnya)

Sebelum ngomong model, rapikan dulu datanya. Kabar baiknya: Anda tidak butuh data warehouse mewah. Cukup satu tabel order yang konsisten.

Struktur Tabel Data Order

Kolom	Contoh	Kenapa penting	Catatan praktis
order_id	ORD-2026-0021	identitas transaksi	unik dan konsisten
tanggal_order	2026-02-10	time series	gunakan ISO date
kategori	seragam kerja	segmentasi permintaan	bisa: seragam/jersey/muslim/merch
sku/desain	SPV-KIIC-01	pola demand per desain	opsional tapi bagus
qty	120	target produksi	integer
ukuran_mix	M:60,L:40,XL:20	estimasi konsumsi kain	bisa JSON
bahan	oxford 200gsm	konsumsi & substitusi	normalisasi nama
lebar_kain_cm	150	konversi meter	penting untuk yield
allowance_qc	0.03	buffer reject	3%–7% sesuai historis
tanggal_kirim	2026-02-25	SLA	untuk evaluasi jadwal

Data Konsumsi Kain per Item

Buat tabel kecil lain (bisa spreadsheet) untuk “konsumsi standar” per kategori/ukuran.

kategori	ukuran	konsumsi_meter	catatan
seragam kerja	M	1.6	termasuk kampuh
seragam kerja	L	1.7
jersey	M	1.3	tergantung pola
gamis	L	2.6	termasuk rok

Di titik ini, Anda sudah siap menjalankan forecast kebutuhan bahan python dengan cara yang realistis: mulai dari demand (qty) → convert ke meter kain → tambahkan buffer QC → hasilkan rencana pembelian.

3. HowTo Scheme: Dari Data Order ke Rencana Beli Kain

Bab ini sengaja dibuat seperti engineering playbook—biar bisa Anda copy ke repo internal.

Step-by-step (Skema Praktis)

Ambil data order per hari/minggu dan segmentasi per kategori atau bahan.
Konversi qty → kebutuhan meter kain (berdasarkan ukuran mix + konsumsi standar).
Buat time series kebutuhan kain (meter) per bahan.
Forecast 4–8 minggu ke depan (pilih metode sederhana dulu).
Hitung reorder point = forecast demand selama lead time + safety stock.
Generate purchase plan: tanggal pesan, jumlah meter, prioritas supplier.

Template Python (Ringkas Tapi Siap Jalan)

Fokus contoh ini: forecasting mingguan untuk satu bahan. Anda bisa loop untuk semua bahan.

import pandas as pd
import numpy as np

# 1) Load data order yang sudah dikonversi ke kebutuhan meter per bahan
# kolom minimal: tanggal_order, bahan, kebutuhan_meter

df = pd.read_csv("order_kebutuhan_meter.csv")
df["tanggal_order"] = pd.to_datetime(df["tanggal_order"])

bahan_target = "oxford 200gsm"
ts = (
    df[df["bahan"] == bahan_target]
    .set_index("tanggal_order")["kebutuhan_meter"]
    .resample("W")
    .sum()
    .asfreq("W", fill_value=0)
)

# 2) Baseline forecast: moving average 4 minggu (simple & stable)
window = 4
forecast_horizon = 8

ma = ts.rolling(window=window, min_periods=1).mean()
last_ma = float(ma.iloc[-1])
forecast = pd.Series(
    [last_ma] * forecast_horizon,
    index=pd.date_range(ts.index[-1] + pd.Timedelta(weeks=1), periods=forecast_horizon, freq="W")
)

# 3) Reorder point (ROP)
lead_time_weeks = 2
service_factor = 1.65  # ~95% service level

hist = ts.tail(12)  # 3 bulan terakhir
sigma = float(hist.std(ddof=0))

expected_demand_lt = float(forecast.head(lead_time_weeks).sum())
safety_stock = service_factor * sigma * np.sqrt(lead_time_weeks)
rop = expected_demand_lt + safety_stock

print("Bahan:", bahan_target)
print("Forecast 8 minggu (meter/minggu):")
print(forecast.round(2))
print("\nROP (meter):", round(rop, 2))

Kenapa baseline ini cukup masuk akal? Karena di operasional, forecast yang “sedikit salah tapi stabil” sering lebih berguna daripada model kompleks yang susah dipelihara. Setelah baseline, baru naik level: feature engineering (musiman, event), atau model time series lain.

Tip: Di CoderLegion ada contoh yang relevan untuk memahami pola forecasting dari data historis—lihat Weather Service Project (Part 3): Predicting the Future with AI and OpenWeatherMap untuk gambaran alur “data → model → keputusan”.

Dalam praktik, Anda bisa menyebut pipeline ini sebagai forecast kebutuhan bahan python versi MVP.

4. Metrik yang Harus Anda Pantau (Biar Forecast Tidak Jadi Pajangan)

Forecast yang bagus itu bukan yang terlihat keren di notebook, tapi yang memperbaiki keputusan pembelian dan produksi.

KPI Operasional yang Nyambung

Fill rate: % order yang dipenuhi tanpa stockout.
Lead time aktual: dari PO ke bahan datang (per supplier).
Waste rate: sisa kain/lembar cutting.
On-time delivery: ketepatan kirim.

Error Metric (Untuk Model)

MAE (Mean Absolute Error): mudah dipahami tim ops.
MAPE: hati-hati kalau demand sering nol.
Bias: apakah forecast cenderung over/under.

Kalau Anda baru mulai, cukup pantau: MAE + bias. Jalankan forecast kebutuhan bahan python mingguan, lalu review tiap akhir minggu.

5. Studi Kasus Mini: Seragam Industri dengan Size Mix

Misal ada 3 klien industri minggu ini, total 420 pcs. Komposisi ukuran dan konsumsi standar memengaruhi kebutuhan kain.

Contoh Perhitungan Cepat

Ukuran mix: M 50%, L 35%, XL 15%
Konsumsi (meter): M 1.6, L 1.7, XL 1.85
Allowance QC: 4%

Kebutuhan meter (tanpa QC):

M: 210 × 1.6 = 336
L: 147 × 1.7 = 249.9
XL: 63 × 1.85 = 116.55
Total = 702.45 m

Dengan QC 4%: 702.45 × 1.04 = 730.55 m

Kalau Anda merekam perhitungan ini per minggu, Anda akan punya time series yang siap untuk forecast kebutuhan bahan python tanpa ribet.

6. FAQ (Yang Sering Ditanya Developer & Owner Konveksi)

Apakah harus pakai model machine learning?

Tidak. Mulai dari baseline (moving average / exponential smoothing) dulu. ML masuk kalau Anda sudah punya data stabil dan ingin memanfaatkan fitur kontekstual.

Data saya bolong-bolong, bisa?

Bisa, asal Anda konsisten “mengisi nol” untuk periode tanpa order. Time series butuh kontinuitas.

Berapa horizon forecast yang realistis?

Untuk konveksi: 4–8 minggu biasanya paling actionable. Di atas itu, ketidakpastian naik (event/seasonality/negosiasi klien).

Bagaimana kalau ada order mendadak besar?

Tambahkan mekanisme override: forecast baseline + “known future orders”. Ini lebih jujur daripada memaksa model mengerti kejutan.

Apa kaitannya dengan produksi (bukan cuma beli kain)?

Forecast bahan bisa diturunkan ke capacity planning: estimasi jam jahit, kebutuhan operator, urutan produksi per deadline.

7. Closing yang Lebih “Engineering” dari Sekadar Operasional

Sebagai penutup, menarik mengingat analogi dari Andrew Ng: “AI is the new electricity.” Artinya: AI (dan praktik data-driven) akan menjadi utility yang meresap ke banyak industri—bukan cuma tech company. Dalam konteks konveksi, “listrik” itu bisa berupa pipeline sederhana: data order → metrik → keputusan pembelian → jadwal produksi. Anda tidak harus mulai dari model canggih; yang penting adalah kebiasaan membuat keputusan berdasarkan data, lalu mengiterasinya.

Kalau Anda ingin melihat implementasi nyata di lapangan (seragam kerja, jersey, pakaian muslim, hingga merchandise) dan bagaimana kebutuhan produksi diterjemahkan jadi eksekusi yang rapi, Anda bisa cek profil layanan kami di akhir tulisan ini—dan jadikan artikel ini sebagai fondasi forecast kebutuhan bahan python yang dapat Anda adaptasi ke proyek internal.

Backlink (narasi yang wajar): Jika Anda sedang mencari mitra produksi seragam/konveksi yang siap diajak kolaborasi berbasis data—mulai dari estimasi kebutuhan bahan sampai penjadwalan produksi—kunjungi Konveksi Karawang — CV Mitra Mandiri Design.

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Forecast Kebutuhan Bahan & Produksi Konveksi dengan Python (Praktis + Template)",
  "description": "Panduan praktis forecasting kebutuhan bahan dan perencanaan produksi konveksi dengan Python: dari data order, konversi konsumsi kain, baseline forecast, hingga reorder point.",
  "inLanguage": "id-ID",
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://coderlegion.com/"
  },
  "author": {
    "@type": "Organization",
    "name": "CV Mitra Mandiri Design",
    "url": "https://www.konveksikarawang.co.id/"
  },
  "publisher": {
    "@type": "Organization",
    "name": "CV Mitra Mandiri Design",
    "url": "https://www.konveksikarawang.co.id/",
    "logo": {
      "@type": "ImageObject",
      "url": "https://www.konveksikarawang.co.id/wp-content/uploads/"
    }
  },
  "about": [
    {"@type": "Thing", "name": "forecast kebutuhan bahan python"},
    {"@type": "Thing", "name": "demand forecasting"},
    {"@type": "Thing", "name": "production planning"},
    {"@type": "Thing", "name": "python"},
    {"@type": "Thing", "name": "konveksi"}
  ],
  "isAccessibleForFree": true
}

Attribution & Forecasting: Uncovering Insights & Predicting the Future Like a Pro!

Tue, 24 Jun 2025 04:30:18 +0000

✨ Attribution & Forecasting: Uncovering Insights & Predicting the Future Like a Pro!

In the age of data-driven decisions, understanding where your results come from (Attribution) and predicting what’s next (Forecasting) are your ultimate power moves! Whether you run a business, manage ads, or analyze trends — mastering these will help you win big.

Let’s break it down: What, Why, How, and the Best Ways to Do It — with algorithms and examples!

What is Attribution?

Attribution means figuring out which touchpoints, channels, or actions deserve credit for a desired outcome (like a sale or sign-up).

Example:
Imagine you run an online store. A customer sees your Google ad, reads your blog, then clicks your Instagram post before buying. Which channel deserves the credit? Attribution answers this!

Why Do We Need Attribution?

✅ Better Budgeting: Know which channels work best and invest more wisely.
✅ Boost ROI: Stop wasting money on low-impact channels.
✅ Customer Journey Insights: Understand how people interact with your brand at each step.

⚙️ How Do We Do Attribution?

There are several models — from simple to advanced:

1️⃣ Rule-Based Models:

First Touch Attribution: 100% credit to the first interaction.
Last Touch Attribution: 100% credit to the last interaction.
Linear Attribution: Equal credit to all touchpoints.
Time Decay: More credit to recent touchpoints.

When to use: Small businesses or when you need quick insights without heavy data crunching.

2️⃣ Algorithmic / Data-Driven Models:

Advanced methods use data science to assign credit more accurately.

✨ Popular Algorithm: Markov Chain Attribution

How it works: It treats each touchpoint as a state and calculates the probability that removing a touchpoint affects conversions.

Example:
If removing Instagram causes a big drop in sales, Instagram gets high credit!

Best For: Medium to large businesses with lots of customer data.

What is Forecasting?

Forecasting predicts future trends based on historical data. From sales to website traffic to stock prices — forecasting helps you plan ahead. ️

Why Do We Need Forecasting?

✅ Demand Planning: Avoid stockouts or overstocking.
✅ Revenue Prediction: Plan budgets and growth.
✅ Resource Allocation: Allocate manpower and money efficiently.

How Do We Do Forecasting?

There are tons of methods — choose based on your data size and goal.

✅ Best Algorithms for Forecasting:

1️⃣ ARIMA (AutoRegressive Integrated Moving Average)

Great for time series data with trends & seasonality.
Example: Monthly sales prediction.

2️⃣ Exponential Smoothing (ETS)

Smooths out fluctuations, good for stable trends.

3️⃣ Prophet by Facebook

Handles holidays & seasonality well, easy to use.

4️⃣ Machine Learning Methods:

XGBoost Regression
LSTM (Long Short-Term Memory Neural Networks) for deep learning with complex patterns.

The Secret Sauce: Combining Attribution & Forecasting

Pro Tip: Use attribution insights to build better forecasts!

Example:
If attribution shows Instagram drives 40% of your sales, and you forecast sales will double during the holiday season — you can plan a bigger Instagram budget in advance!

✅ Best Practices for Precise Results

✨ Collect clean, reliable data.
✨ Use multiple models and compare results.
✨ Regularly update your models with new data.
✨ Visualize results for easy decision-making.

Let’s See an End-to-End Example

Business: Online Shoe Store

Attribution: Use Markov Chain to find that Instagram & Google Ads are key drivers.
Forecast: Use ARIMA to predict next quarter’s sales based on seasonality and trends.
Action: Increase Instagram ads budget before peak season to maximize ROI.

Result: Smarter spending, higher sales, and no surprises!

Wrapping Up

Attribution = Who gets the credit?
Forecasting = What’s coming next?

Master these, and you’re not just analyzing the past — you’re shaping the future!

✅ What’s Next?

Ready to supercharge your data strategy?
Start small, test models, visualize results, and make smarter decisions every day.

Feel free to share this blog if you found it useful!
Got questions? Drop them in the comments — let’s decode data together! ✨