# Supplier Governance & Commercial Framework

## Purpose

This file describes the static **Supplier Governance & Commercial Framework** for **HAV Seafood**.

The companion workbook is:

`hav_seafood_procurement_supplier_governance_commercial_framework_v1.xlsx`

The architecture defines **how HAV Seafood structurally governs suppliers, what qualification evidence is expected, which functions own reviews, which commercial relationship profiles are used, and which agreement structures may apply**.

It belongs to **Phase 1 — Business Architecture**:

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

It does **not** contain supplier approval history, audits, certificates received, signed contracts, quotations, negotiations, actual prices, purchase orders, invoices, or supplier-performance events.

---

## Core ownership boundaries

- **Shared Enterprise** remains authoritative for common external-organization identity.
- **Procurement** owns the commercial supplier master, supplier governance profiles/assignments, commercial supplier classifications and sourcing/commercial relationship structure.
- **Core ERP (`ESYS-001`)** is the authoritative system for commercial supplier master data and later purchasing transactions.
- **Quality** owns detailed supplier-quality evaluation, food-safety evidence, certificates, audits and technical quality approvals.
- **QMS (`ESYS-003`)** is the authoritative operational system for supplier-quality records.
- **Maintenance** owns technical competence review for external maintenance service providers; maintenance service records belong to the maintenance system landscape.
- **Finance** will own enterprise payment-term master data. Payment-term values in this workbook are explicitly synthetic/provisional commercial assumptions and are not Finance master codes.

The framework deliberately separates:

`Supplier commercial identity -> Procurement governance -> Technical/quality approval -> Commercial profile -> Agreement structure`

from later operational records such as:

`Review event -> Approval decision -> Contract -> Purchase Order -> Receipt -> Invoice -> Supplier performance`

---

## Workbook contents

### `Supplier_Governance_Profiles`

Defines **5 reusable governance profiles** covering:

- seafood raw-material suppliers;
- food-ingredient suppliers;
- food-contact/critical packaging suppliers;
- technical maintenance service providers;
- calibration service providers.

Each profile defines governance depth, review cycle, quality/technical involvement, alternative-source expectations, responsible roles and authoritative systems.

---

### `Supplier_Governance_Assignments`

Contains one current governance assignment for each of the **13 suppliers** already present in the Supplier & Sourcing Architecture.

The assignments preserve the existing supplier IDs and approved-category relationships. They describe current static governance status only and do not represent dated approval events.

---

### `Qualification_Requirements`

Defines **20 reusable supplier qualification/governance requirements**.

The requirements cover areas such as:

- organization/master-data verification;
- commercial onboarding;
- Finance interface validation;
- specification acceptance;
- traceability;
- food-safety management evidence;
- COA/conformance documentation;
- origin and species evidence;
- cold-chain capability;
- histamine and parasite-control evidence;
- cooked-shrimp microbiological evidence;
- ingredient allergen declarations;
- food-contact packaging compliance;
- label/artwork change control;
- supplier change notification;
- technical service competence;
- calibration competence/traceability;
- insurance/liability evidence;
- document currency/requalification readiness.

Where requirements reference existing `QR-*` or `CP-*` records, the Production Quality & Food-Safety architecture remains authoritative for the technical requirement itself.

---

### `Qualification_Profile_Map`

Contains **50 relationships** assigning qualification requirements to the reusable governance profiles.

This allows governance rules to be defined once rather than repeating the full qualification checklist for every supplier.

Actual evidence, completed reviews, missing documentation, expirations and findings belong to Phase 3.

---

### `Commercial_Term_Profiles`

Defines **9 reusable commercial profiles** for domestic seafood, Nordic/EU ingredients, Nordic packaging and specialist services.

Profiles include synthetic structural assumptions for:

- currency;
- payment-term class;
- delivery/service term;
- price basis;
- freight/travel responsibility;
- agreement type;
- ordering model;
- price-review mechanism;
- volume-commitment class;
- commercial review cycle.

These are architecture defaults for later synthetic data generation, not actual negotiated supplier terms.

Payment terms remain explicitly **provisional** pending the Finance Architecture.

---

### `Supplier_Commercial_Assignments`

Maps each of the **13 current suppliers** to a normal commercial profile and agreement structure.

No contract number, effective date, negotiated clause, actual price or historical change is stored.

---

### `Agreement_Framework`

Defines **6 reusable agreement structures**:

- framework supply agreement;
- annual supply agreement;
- spot purchase arrangement;
- technical service agreement;
- calibration service agreement;
- emergency source arrangement.

The framework defines what agreement structures may exist; it does not assert that a particular signed agreement currently exists.

---

### `Architecture_Notes`

Records important architecture decisions, source boundaries, system ownership, Finance/Quality boundaries, story neutrality and identifier conventions.

---

### `Data_Dictionary`

Provides field-level definitions, formats and ownership notes for all workbook sheets.

---

## Relationship to Supplier & Sourcing Architecture

The previous workbook answers:

> **Who can supply what under what normal sourcing parameters?**

This workbook answers:

> **What governance and qualification structure applies to that supplier, and what commercial framework normally governs the relationship?**

The two layers connect primarily through `Supplier_ID`.

No supplier identities or sourcing relationships are independently recreated here.

---

## Relationship to Quality & Food Safety

The workbook references existing Production Quality controls where supplier governance depends on them, including receiving traceability, incoming packaging/ingredient controls, seafood cold-chain controls, histamine controls, parasite controls and cooked-shrimp microbiological controls.

Procurement does **not** become authoritative for these technical controls.

The intended operational division is:

- Procurement/ERP: supplier commercial master and purchasing relationship;
- Quality/QMS: supplier-quality approval, certificates, audits and technical evidence;
- shared IDs connect the records.

---

## Relationship to Finance

The Shared Enterprise ownership model reserves the enterprise Payment Terms master for Finance.

Therefore this workbook deliberately contains fields such as `Default_Payment_Term_Assumption` rather than creating authoritative payment-term IDs.

When the Finance Architecture is created, these assumptions can be mapped to the Finance-owned payment-term master without changing supplier governance identities.

---

## Architecture boundaries — explicitly excluded

This workbook does **not** contain:

- completed supplier onboarding cases;
- approval requests or decisions;
- temporary approval events;
- supplier suspensions/reactivations;
- supplier audits;
- audit findings;
- supplier scorecards;
- certificates received;
- certificate expiry history;
- corrective-action records;
- supplier complaints;
- RFQs;
- supplier quotations;
- negotiations;
- executed contracts;
- contract numbers or effective dates;
- actual supplier prices;
- price histories;
- rebates or discounts actually earned;
- purchase orders;
- receipts;
- supplier invoices;
- supplier performance measurements;
- commercial disputes;
- insurance claims;
- dated governance-review history.

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

---

## Story neutrality

All current suppliers are structurally shown as approved because the existing Supplier & Sourcing Architecture already treats them as approved suppliers/sources.

The framework does not deliberately seed:

- failed qualification;
- expired certification;
- audit problems;
- supplier suspension;
- weak supplier performance;
- commercial disagreement;
- price escalation;
- contract lapse;
- governance-control failures.

These may be introduced deliberately in Phase 2 stories and Phase 3 operational data.

---

## Identifier conventions

This workbook introduces Procurement-local identifiers:

- `SGP-*` — supplier governance profiles;
- `SGA-*` — supplier governance assignments;
- `QREQ-*` — qualification requirements;
- `QPM-*` — governance-profile / qualification-requirement mappings;
- `CTP-*` — commercial term profiles;
- `SCA-*` — supplier commercial assignments;
- `AGT-*` — agreement types.

Existing supplier IDs, role IDs, system IDs, quality IDs and currency codes are preserved.

---

## Recommended AI use

For fast context, an AI system should normally:

1. read this Markdown file;
2. inspect `Supplier_Governance_Assignments` to identify the supplier's governance profile;
3. inspect `Qualification_Profile_Map` and `Qualification_Requirements` to understand required governance/technical evidence;
4. inspect `Supplier_Commercial_Assignments` and `Commercial_Term_Profiles` for normal commercial structure;
5. consult the authoritative Quality, Finance, Shared Enterprise or Supplier & Sourcing source where the relationship crosses a domain boundary.

---

## Overall role

Together, the workbook and this reference file form the static **supplier governance and commercial-rules layer** for HAV Seafood.

They provide enough structure to later generate realistic supplier onboarding, quality approvals, documentation, agreements, negotiations, purchasing and supplier-management records without mixing those operational histories into Phase 1 architecture.
