# Supply Planning & Inventory Framework

## Purpose

This file describes the static **Supply Planning & Inventory Framework** for **HAV Seafood**. The accompanying workbook is:

`hav_seafood_supply_planning_inventory_framework_v1.xlsx`

It belongs to **Phase 1 — Business Architecture** and defines how purchased materials are structurally planned, replenished, stored and controlled as inventory. It does **not** contain historical or transactional inventory data.

The framework covers **132 purchased material items** already defined in the Supplier & Sourcing Architecture: seafood raw materials, ingredients/processing inputs, and packaging materials.

---

## Core architecture principles

- Existing item, procurement category, supplier, UOM, storage-location, role and system identifiers are reused rather than redefined.
- Supply Chain owns the reusable planning profiles, item planning assignments, reusable inventory-control profiles, item inventory assignments and stock-status vocabulary defined here.
- Procurement remains authoritative for supplier-item sourcing, preferred-source relationships, purchasing UOMs and standard supplier lead times.
- Production remains authoritative for technical item definitions, shelf-life/hold limits, detailed storage locations and storage compatibility.
- Logistics/ERP remains authoritative for actual inventory movements and stock positions.
- Quality remains responsible for operational release, quarantine, rejection and quality disposition decisions.
- Finance will own inventory valuation, costing and financial write-off structures when the Finance Architecture is built.
- Static planning assumptions are separated from actual forecasts, quantities and planning runs.
- No deliberate future business-story anomalies are seeded in this workbook.

---

## Workbook contents

### `Planning_Profiles`

Defines **8 reusable supply-planning profiles** for different material behaviors:

- Fresh chilled seafood
- Frozen seafood
- Chilled or frozen ingredients
- Standard ambient ingredients
- Specialty ambient ingredients
- Food-contact packaging
- Printed SKU-specific packaging
- Secondary and tertiary packaging

Each profile defines the normal demand basis, purchase-to-stock/near-term orientation, planning horizon, review frequency, time bucket, safety-stock methodology, reorder/min-max applicability, target coverage guideline, lead-time treatment, seasonality treatment, shortage priority and intended system.

The quantitative planning ranges are **synthetic internal architecture assumptions**, not historical measurements or calculated stock parameters.

### `Item_Planning_Assignments`

Contains one current planning assignment for each of the **132 purchased material items**.

Each row links:

`Item -> Procurement Category -> Planning Profile -> Preferred Supplier/Source -> Lead Time -> Purchase UOM -> Primary Storage Location`

The table also identifies the structural demand driver:

- raw seafood -> production plan and yield requirements;
- ingredients -> recipe/component demand;
- packaging -> SKU BOM demand.

All 132 items are therefore modeled as **dependent demand** in the current architecture.

Planning-profile distribution:

- `SPP-01` — Fresh Chilled Seafood: **5 items**
- `SPP-02` — Frozen Seafood: **8 items**
- `SPP-03` — Chilled or Frozen Ingredients: **4 items**
- `SPP-04` — Standard Ambient Ingredients: **11 items**
- `SPP-05` — Specialty Ambient Ingredients: **36 items**
- `SPP-06` — Food-Contact Packaging: **24 items**
- `SPP-07` — Printed SKU-Specific Packaging: **26 items**
- `SPP-08` — Secondary & Tertiary Packaging: **18 items**

### `Inventory_Control_Profiles`

Defines **8 reusable inventory-control profiles** covering chilled/frozen raw seafood, temperature-controlled ingredients, allergen-controlled ingredients, normal ambient ingredients, food-contact packaging, printed packaging, and secondary/tertiary packaging.

Profiles define static rules around:

- lot/batch control;
- expiry or shelf-life control;
- FIFO/FEFO stock rotation;
- quarantine capability;
- release/acceptance requirements;
- reservation principles;
- cycle-count class;
- slow-moving review;
- obsolete/expired disposition;
- segregation expectations.

### `Item_Inventory_Assignments`

Contains one inventory-control assignment for each purchased item.

Each row links the item to:

- an inventory profile;
- its Production-defined primary storage location;
- a permitted quarantine/hold location where available;
- lot/expiry control interpretation;
- FIFO/FEFO rule;
- technical shelf-life/maximum-hold reference where Production defines one;
- allergen-control applicability;
- food-contact-packaging classification.

Inventory-profile distribution:

- `INVP-01` — Chilled Raw Seafood: **5 items**
- `INVP-02` — Frozen Raw Seafood: **8 items**
- `INVP-03` — Temperature-Controlled Ingredient: **4 items**
- `INVP-04` — Allergen-Controlled Ambient Ingredient: **11 items**
- `INVP-05` — Ambient Ingredient: **36 items**
- `INVP-06` — Food-Contact Packaging: **24 items**
- `INVP-07` — Printed Packaging: **26 items**
- `INVP-08` — Secondary & Tertiary Packaging: **18 items**

### `Stock_Status_Disposition`

Defines **9 allowable stock statuses**:

- Available
- Reserved
- Quality Hold
- Quarantine
- Blocked
- Rejected
- Expired
- Obsolete
- Awaiting Disposition

These are controlled architecture states only. The workbook contains no actual inventory lots in any of these statuses.

### `Architecture_Notes`

Records the main architecture decisions, ownership boundaries, system assumptions and exclusions.

### `Data_Dictionary`

Defines the important fields, meanings, datatypes, source/ownership expectations and relationship notes for the workbook.

---

## Relationship with other architectures

### Supplier & Sourcing Architecture

The planning framework references the existing preferred supplier/source relationship, purchasing UOM and standard lead time for each item. It does not redefine sourcing.

### Shared Enterprise Architecture

The workbook reuses enterprise item classes, role references, UOM conventions and the enterprise system landscape. **ESYS-001 Core ERP** is the intended operational platform for purchasing, planning parameters, inventory and storage-location state.

### Production Architecture

Production remains authoritative for:

- raw-material, ingredient and packaging technical masters;
- recipes and SKU BOMs;
- yield standards;
- physical storage locations;
- storage compatibility;
- technical shelf-life/hold limits.

The framework uses these structures to define planning and inventory behavior without duplicating the technical masters.

### Quality

Quality release, quarantine, rejection and technical disposition criteria are not owned here. The stock-status framework merely provides the inventory states that later Quality workflows can reference.

### Logistics

The existing System & Data Ownership Model assigns actual **Inventory Movement** and **Inventory Balance / Stock Position** records to Logistics in **ESYS-001 Core ERP**. This workbook does not change that ownership.

### Finance

Inventory valuation, costing, provisions, financial write-offs and accounting treatment remain outside this architecture.

---

## Explicit exclusions

This workbook contains no:

- inventory balances or snapshots;
- stock movements;
- goods receipts;
- material issues or consumption;
- transfers;
- reservations;
- inventory adjustments;
- stock counts;
- write-offs;
- expiry events;
- obsolete-stock events;
- forecasts;
- MRP runs;
- reorder calculations;
- actual safety-stock quantities;
- shortage reports;
- purchase suggestions;
- planned purchase orders;
- production plans;
- historical stock-status changes.

These belong to **Phase 3 — Operational dataset generation** after the business stories have been selected.

---

## Recommended AI use

For quick context, an AI system should normally inspect this Markdown file first, then the workbook sheets in this order:

1. `Item_Planning_Assignments`
2. `Item_Inventory_Assignments`
3. `Planning_Profiles`
4. `Inventory_Control_Profiles`
5. `Stock_Status_Disposition`
6. `Architecture_Notes`
7. `Data_Dictionary`

When precise supplier, technical material, BOM, shelf-life or storage details are required, the referenced authoritative source workbook should be inspected rather than treating copied descriptive fields here as master data.
