# HAV Seafood — System & Data Ownership Model

## Purpose

This workbook defines where important HAV Seafood master data, operational/transactional data and reporting data is authoritatively maintained across the enterprise systems landscape.

It separates **business-domain ownership** from **system-of-record ownership**. A business domain owns the meaning and rules of an entity, while this workbook identifies which application or platform holds the authoritative record.

This is static Phase 1 architecture. It defines where future records belong but contains no actual operational history.

## Workbook contents

- **Data_Object_Ownership** — Canonical register of 132 master, transactional and reporting data objects with one authoritative system for each.
- **System_Data_Roles** — 402 mappings describing which systems master, create, consume, replicate, report or retain each data object.
- **Master_Data_Register** — System-of-record assignments for all 66 enterprise/master entities from the Entity Ownership Matrix.
- **Transactional_Data_Ownership** — 54 future operational/transaction record types and their authoritative, creation, downstream and retention systems.
- **Reporting_Data_Ownership** — 12 derived reporting datasets and their source systems. All are explicitly non-authoritative for underlying business records.
- **Data_Synchronization_Rules** — 32 static synchronization rules covering important cross-system handoffs and ownership after copying.
- **Data_Conflict_Rules** — 31 precedence rules defining which system wins when replicated/shared data disagrees.
- **Ownership_Statuses** — Controlled status vocabulary for confirmed, transitional, provisional, legacy and unresolved ownership decisions.
- **Architecture_Notes** — Key system/data ownership principles and boundaries.
- **Data_Dictionary** — Field definitions, logical datatypes and key relationships.

## Key architecture decisions

- **Core ERP** is authoritative for finance, procurement transactions, confirmed customer/supplier masters, sellable/purchased item identities, inventory, storage locations and confirmed sales orders.
- **Production Execution System (MES)** is authoritative for production execution, batches, recipes, routings, process steps, intermediate products and core production equipment/line/work-center identity.
- **Quality Management System (QMS)** is authoritative for quality/food-safety requirements, control points, QC results, hold/release decisions, nonconformance and related quality records.
- **Maintenance Management System (CMMS)** is authoritative for maintenance plans/tasks, work orders, calibration and service history while referencing Production-owned `Equipment_ID`.
- **People & Payroll** is authoritative for employees, enterprise job roles/families, organizational assignments, working-time patterns and HR operational records.
- **Sales CRM** is authoritative for opportunities, quotations, activities, market/segment classifications and relationship-management extensions; ERP remains authoritative for confirmed Customer_ID and sales transactions.
- **Microsoft Entra ID** is authoritative for user accounts/authentication.
- **Microsoft 365 / SharePoint** holds controlled shared registers where HAV Seafood has no dedicated MDM/facilities/catalog system, such as enterprise locations, the external-organization registry and the enterprise IT-system register.
- **Temperature & Cold-Chain Monitoring** retains authoritative raw sensor readings and alarms; QMS owns the subsequent quality review/disposition.
- **Online Banking Portal** is authoritative for actual bank movements/statements; ERP remains authoritative for accounting and reconciliation.
- **Power BI is never authoritative for underlying business records.** Corrections are made in source systems and reports are refreshed.

## Important splits

A copied record does not transfer ownership. For example, MES receives SKU/item information from ERP but ERP remains the item master. QMS may hold supplier-quality information while ERP remains the supplier commercial master. CMMS extends equipment with maintenance data while MES retains the core production equipment identity.

Production orders are also deliberately split: ERP owns the planning/order header used for supply and inventory coordination, while MES owns shop-floor execution, batches, material consumption and production outputs.

## Relationship to other architecture

This workbook complements:

- `hav_seafood_enterprise_entity_ownership_matrix_v1.xlsx` for conceptual business-domain ownership.
- `hav_seafood_enterprise_systems_landscape_v1.xlsx` for system identities, functions and integrations.
- `hav_seafood_enterprise_identifier_standards_v1.xlsx` for identifiers and cross-domain key rules.

It does not replace domain master workbooks or define database-table implementation.

## Boundaries

The workbook contains no actual invoices, orders, batches, QC results, work orders, absence records, security logs, bank statements or reporting values. Those records will be generated only in the later operational-dataset phase.
