# HAV Seafood — Logistics & Distribution Reference Tables

## Purpose

This workbook is the **derived, AI-friendly navigation and joining layer** across the complete static Logistics & Distribution architecture for HAV Seafood.

It belongs to **Phase 1 — Business Architecture** of the synthetic business dataset project:

**1. Business architecture -> 2. Stories -> 3. Operational dataset**

The workbook does **not** own Logistics master data. Its purpose is to provide compact cross-workbook views so an AI system or human analyst can quickly identify the relevant Logistics entity, relationship, rule, owner and authoritative source without opening every detailed workbook first.

If this workbook conflicts with an authoritative Logistics or upstream source, **the authoritative source wins**.

## Authoritative Logistics sources

The reference workbook is derived primarily from three authoritative Logistics workbooks:

1. `hav_seafood_logistics_distribution_network_carrier_framework_v1.xlsx` — ship-to locations, carriers, transport services, outbound lanes, lane/carrier eligibility and delivery-network requirements.
2. `hav_seafood_logistics_outbound_fulfilment_dispatch_framework_v1.xlsx` — fulfilment profiles, SKU fulfilment references, inventory eligibility, stock rotation, picking, handling units, staging, dispatch readiness and dispatch-document requirements.
3. `hav_seafood_logistics_process_service_control_framework_v1.xlsx` — shipment object/lifecycle architecture, delivery-service rules, exceptions, returns, Logistics processes, authority, controls, escalation, metric definitions, systems and cross-domain interfaces.

Upstream Sales, Production, Quality, HR and Shared Enterprise facts remain authoritative where those domains own the underlying entity.

## Architecture counts represented

The current reference layer contains:

- **4** customer ship-to locations;
- **2** Logistics carrier extensions represented through **10** carrier/service capability relationships;
- **5** transport service classes represented through the capability and lane views;
- **12** outbound lanes;
- **24** lane/carrier/service applicability relationships;
- **73** active Customer + SKU Logistics relationships;
- **24** active Production SKUs in the Logistics fulfilment reference;
- **5** fulfilment profiles;
- **32** combined delivery/dispatch requirement records;
- **20** Logistics exception types plus **9** return rules in the combined exception/return view;
- **22** Logistics processes in the high-level process/control reference;
- **10** Logistics service-metric definitions.

These counts describe static architecture, not operational history.

## Workbook sheets

### `Architecture_Overview`
Provides workbook purpose, authoritative sources, major counts, Phase 1 boundaries and AI navigation shortcuts.

### `Ship_To_Reference`
Compact reference for the four customer delivery destinations, including customer, city/country, market, ship-to type, receiving pattern, delivery-window class and supported temperature regimes.

### `Carrier_Service_Reference`
Joins carrier extensions to transport-service capability. Useful for identifying which carrier can support which service, temperature regime and geography.

### `Outbound_Lane_Reference`
Compact view of all 12 temperature-specific outbound lanes, including ship-to, customer, market, service class, primary carrier, transit assumption, dispatch pattern and delivery window.

### `Lane_Carrier_Reference`
Shows the 24 eligible Lane + Carrier + Service relationships and preference ranking.

### `Customer_SKU_Logistics_Ref`
The principal AI navigation sheet for product/customer distribution questions. It joins the existing 73 Customer + SKU listings to ship-to, lane, service, primary carrier, fulfilment profile, storage, staging, stock-rotation rule, picking rule, shelf-life rule and dispatch-readiness profile.

This sheet is **derived and non-authoritative**. Sales remains authoritative for the customer/SKU commercial relationship, Production for SKU technical characteristics, and the detailed Logistics workbooks for Logistics rules.

### `SKU_Logistics_Reference`
One row for each of the 24 active Production SKUs with storage regime, shelf life, case/pallet structure, finished-goods storage, QA-hold and staging locations, fulfilment profile and default fulfilment rules.

`Customer_Listing_Count` is a workbook formula derived from `Customer_SKU_Logistics_Ref`.

### `Fulfilment_Dispatch_Ref`
High-level summary of the five fulfilment profiles and their assigned rotation, picking, shelf-life and staging structures.

The SKU and Customer/SKU assignment counts are formulas derived from the corresponding reference sheets.

### `Dispatch_Requirements_Ref`
Combined navigation view of:

- network delivery requirements;
- dispatch-readiness requirements;
- dispatch document/data requirements.

Detailed rule interpretation remains in the authoritative source workbook.

### `Shipment_Service_Reference`
Combined reference across shipment objects, shipment lifecycle statuses and delivery-service rules. It provides semantic navigation without copying detailed status-transition logic.

### `Exception_Return_Reference`
Combines Logistics exception types, normal routing/escalation, and reverse-logistics return rules. It preserves the distinction between an **exception type**, a future **exception case**, a **return reason**, and final Quality/commercial disposition.

### `Process_Control_Reference`
One row for each of the 22 Logistics processes, joining process ownership, system, input/output, authority requirements, cross-functional review requirements and applicable control IDs.

The detailed **110 process steps** are intentionally not duplicated here.

### `Responsibility_Authority`
Position-based Logistics responsibility and authority reference, linked to the existing HR authority backbone. It does not create employee-specific authority or activity.

### `Service_Metric_Reference`
The 10 defined Logistics service metrics, including On-Time Dispatch, On-Time Delivery and OTIF. This sheet contains definitions only — no targets, historical values or performance results.

### `System_Ownership_Relations`
Combined navigation layer covering:

- system/process mappings;
- cross-domain interfaces;
- source-precedence rules;
- a compact relationship catalog across the three Logistics workbooks.

This is the best sheet for questions such as **who owns this object?**, **which system is authoritative?**, or **which source workbook should be opened next?**

### `Data_Dictionary`
Field-level guidance for every visible reference sheet.

## Main architecture relationships

At a high level:

`Sales Customer -> Logistics Ship-To -> Outbound Lane -> Carrier / Transport Service`

`Production SKU -> Fulfilment Profile -> Finished-Goods Storage -> Picking / Handling Unit -> Dispatch Staging`

`Customer + SKU Listing -> Ship-To + Lane + Service + Fulfilment Rules`

`Confirmed Sales Order -> Fulfilment -> Shipment -> Transport Booking -> Dispatch -> Delivery -> Proof of Delivery`

Alternative execution paths include:

`Shipment / Delivery -> Logistics Exception -> Routing / Escalation`

and:

`Delivered Product -> Return Authorization / Physical Return -> Quality / Commercial Disposition`

## Source precedence

The reference workbook must not be used as a competing master.

Important precedence examples include:

- customer and commercial-order structure -> **Sales & Commercial**;
- SKU identity and technical product/storage facts -> **Production**;
- ship-to, outbound lane, carrier and transport-service architecture -> **Logistics Distribution Network & Carrier Framework**;
- picking, fulfilment, staging and dispatch-readiness rules -> **Logistics Outbound Fulfilment & Dispatch Framework**;
- shipment lifecycle, Logistics exceptions, returns, Logistics process authority and controls -> **Logistics Process, Service & Control Framework**;
- technical product release and Quality disposition -> **Quality**;
- positions, incumbency and enterprise authority backbone -> **HR**;
- enterprise system identity and shared entities -> **Shared Enterprise**.

## AI navigation shortcuts

- **Where does Customer X receive goods?** -> `Ship_To_Reference`.
- **Which carrier/service can serve a lane?** -> `Lane_Carrier_Reference`, then `Carrier_Service_Reference`.
- **How does SKU X normally reach Customer Y?** -> `Customer_SKU_Logistics_Ref`.
- **How is SKU X normally fulfilled?** -> `SKU_Logistics_Reference`, then `Fulfilment_Dispatch_Ref`.
- **What must be true before dispatch?** -> `Dispatch_Requirements_Ref`.
- **What are the shipment/delivery concepts and statuses?** -> `Shipment_Service_Reference`.
- **How should a Logistics exception or return be routed?** -> `Exception_Return_Reference`.
- **Who owns/approves a Logistics process?** -> `Process_Control_Reference` and `Responsibility_Authority`.
- **How is Logistics performance defined?** -> `Service_Metric_Reference`.
- **Which system/source owns a data object?** -> `System_Ownership_Relations`.

For precise interpretation, open the authoritative source workbook named in the relevant row.

## Phase 1 boundaries

This workbook contains no operational or historical Logistics records such as:

- shipments or shipment lines;
- handling-unit instances or pallet IDs;
- warehouse picks or allocations;
- transport bookings or carrier confirmations;
- loading or dispatch events;
- shipment tracking events;
- actual delivery records;
- proof-of-delivery files;
- transport temperature readings;
- Logistics exception cases;
- return cases or returned quantities;
- carrier claims;
- actual approvals or escalations;
- control executions;
- freight costs or carrier invoices;
- OTIF, on-time delivery or other KPI results.

Those belong to Phase 3 after the Phase 2 business stories have been deliberately designed.

## Recommended use

For fast Logistics context, inspect files in this order:

1. Logistics folder README once created.
2. `hav_seafood_logistics_distribution_reference_tables_v1.xlsx` — this workbook.
3. The authoritative Logistics workbook identified by the relevant reference row.
4. The relevant upstream Sales, Production, Quality, HR or Shared Enterprise source if the underlying fact belongs outside Logistics.

## Overall role

This workbook is the compact **front door to the Logistics & Distribution architecture**. It makes cross-workbook joins explicit while preserving authoritative ownership boundaries and keeping Phase 1 separate from future operational data.
