# Shared Enterprise Architecture

## Purpose

This folder contains the static Shared Enterprise Architecture for **HAV Seafood**, the fictional Faroese seafood manufacturer used in the synthetic business dataset.

The files define the common structures, identifiers, classifications, ownership rules, systems, and cross-domain relationships that allow the different parts of the company to operate as one consistent enterprise model.

This architecture is designed to support later domain architectures such as HR, Procurement, Sales, Finance, IT, Quality, Logistics, Maintenance, and Administration without allowing those domains to independently redefine shared entities.

The architecture describes **what exists and how the company is structured**. It intentionally does **not** contain operational or transactional history.

The project follows the sequence:

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

This folder belongs to Phase 1.

---

## Core architecture principles

The Shared Enterprise Architecture follows these rules:

- Each important entity has one authoritative source.
- Shared identifiers must remain stable across all domains.
- Other domains may extend shared entities but should not redefine them.
- Existing authoritative Production identifiers are preserved where they already exist.
- Foreign keys must use the authoritative identifier and compatible datatype.
- Shared reference data is centralized only when it is genuinely cross-domain.
- Domain-specific classifications remain with the relevant domain.
- System ownership, business ownership, and conceptual entity ownership are treated as separate concepts.
- Derived reference workbooks never override authoritative master workbooks.
- If a derived file conflicts with an authoritative source, the authoritative source wins.

---

## Files in this folder

### `hav_seafood_company_organization_structure_v1.xlsx`

Defines HAV Seafood's formal organizational structure.

Contains:

- company identity
- enterprise departments
- organizational units
- management positions
- cost-center relationships
- mappings between Production team labels and the enterprise structure
- architecture notes and data dictionary

This workbook is authoritative for the core organizational structure.

---

### `hav_seafood_enterprise_locations_v1.xlsx`

Defines the enterprise-wide physical location hierarchy.

Contains:

- company site
- enterprise locations
- location types
- department-location relationships
- mappings to existing Production factory areas
- mappings to Production storage locations

Detailed Production factory areas, hygiene zones, and storage rules remain authoritative in the Production Architecture.

---

### `hav_seafood_enterprise_identifier_standards_v1.xlsx`

Defines identifier, datatype, naming, and relational conventions used across HAV Seafood.

Contains:

- identifier standards
- datatype standards
- field naming standards
- key rules
- status and boolean conventions
- domain prefixes
- cross-domain key rules
- legacy Production identifier reconciliation

Existing Production identifiers are generally preserved rather than reformatted.

---

### `hav_seafood_enterprise_entity_ownership_matrix_v1.xlsx`

Defines which business domain owns each important enterprise entity.

Contains:

- enterprise entity ownership
- domain registry
- ownership rules
- domain extension rules
- Production reconciliation
- ownership statuses

This workbook distinguishes conceptual business ownership from system-of-record ownership.

---

### `hav_seafood_employee_identity_organizational_reference_v1.xlsx`

Defines the enterprise-wide employee identity and current organizational assignment layer.

Contains:

- 92 employees
- 65 existing Production/Operations employees
- 27 additional enterprise employees
- department assignments
- organizational units
- roles
- management positions
- managers
- primary locations
- Production employee mappings

Detailed employment conditions, payroll, absence, recruitment, and employment history belong to the future HR Architecture.

---

### `hav_seafood_enterprise_job_roles_job_families_v1.xlsx`

Defines the enterprise role taxonomy.

Contains:

- job families
- enterprise job roles
- role levels
- role-to-department relationships
- role-to-position relationships
- employee-role mappings
- Production role reconciliation

Existing Production roles `R001-R030` are preserved. New enterprise roles continue the same sequence.

Production remains authoritative for production-specific skills, proficiency, cross-training, and work-center qualifications.

---

### `hav_seafood_enterprise_item_identity_model_v1.xlsx`

Defines the enterprise identity and classification layer for items bought, produced, stored, consumed, or sold by HAV Seafood.

Contains:

- item classes
- enterprise item registry
- identifier rules
- item relationships
- UOM relationships
- Production item reconciliation
- future item classes

The model currently references 175 enterprise items including finished goods, intermediate products, raw materials, ingredients, processing materials, and packaging materials.

Existing Production identifiers remain authoritative.

Recipes, BOM quantities, technical specifications, prices, and inventory balances remain outside this workbook.

---

### `hav_seafood_external_party_organization_identity_model_v1.xlsx`

Defines the shared identity layer for external organizations.

Contains:

- external organizations
- organization types
- party roles
- organization-role relationships
- address/contact structures
- domain-party mapping structure

The seeded organizations are synthetic. Supplier and partner names were designed to be realistic without intentionally using existing Faroese suppliers.

Supplier-specific and customer-specific master data will later be extended by Procurement and Sales.

---

### `hav_seafood_enterprise_reference_data_classifications_v1.xlsx`

Defines shared enterprise reference data and controlled classifications.

Contains:

- countries
- currencies
- languages
- units of measure
- market/region structures
- lifecycle statuses
- boolean conventions
- entity types
- shared location types
- shared organization types
- reference-data ownership

Existing Production UOM labels are mapped non-destructively to canonical enterprise units.

Domain-specific classifications remain outside this workbook.

---

### `hav_seafood_enterprise_systems_landscape_v1.xlsx`

Defines the static business application landscape.

Contains:

- 13 enterprise systems
- system categories
- department-system usage
- system functions
- system/data-domain relationships
- system integrations
- deployment types
- criticality
- system-location relationships

The landscape is intentionally realistic and somewhat fragmented. Not every system is perfectly integrated, and some interfaces may rely on files or manual processes.

---

### `hav_seafood_system_data_ownership_model_v1.xlsx`

Defines where important data is mastered, maintained, consumed, and reported across HAV Seafood's systems.

Contains:

- master/reference data ownership
- transactional data ownership
- system-data roles
- reporting ownership
- synchronization rules
- conflict-precedence rules

The model currently governs 132 data objects.

This workbook distinguishes:

- business-domain ownership
- authoritative system ownership
- downstream copies
- reporting systems

Reporting platforms such as BI do not become authoritative merely because they contain copies of business data.

---

### `hav_seafood_cross_domain_relationship_tables_v1.xlsx`

Provides simplified cross-domain mappings derived from authoritative architecture files.

Contains:

- enterprise entity reference
- employee-organization relationships
- department-location relationships
- department-system relationships
- role/department/position relationships
- external-organization roles
- enterprise item reference
- entity-owner-system relationships
- data-object/system relationships
- Production-to-enterprise bridge records
- identifier reference
- relationship catalog

This workbook does not own master data. It is a derived navigation and joining layer.

---

### `hav_seafood_shared_enterprise_reference_v1.xlsx`

Provides a compact, AI-friendly overview of the Shared Enterprise Architecture.

Contains simplified reference views for:

- company
- departments
- employees
- locations
- items
- external organizations
- systems
- master-data ownership
- identifiers
- shared reference codes
- units of measure
- architecture sources

This workbook is intended as the main **front door** for quickly understanding the enterprise structure before opening more detailed authoritative files.

It is derived and should not be treated as a master-data source.

---

## Relationship with Production Architecture

The Production Architecture was created before the Shared Enterprise Architecture and already contains detailed authoritative production structures.

Shared Enterprise does not replace those structures.

Production remains authoritative for areas including:

- production lines
- work centers
- machinery and equipment
- production-specific roles and skills
- factory areas and hygiene zones
- detailed storage locations
- finished-product and material technical masters
- recipes and BOMs
- production routings
- process steps
- standard yields
- production capacity
- production staffing requirements
- shift structures
- quality and food-safety requirements currently defined in Production
- cleaning and changeover requirements
- maintenance requirements currently defined in Production

Shared Enterprise provides the common organization, identity, location, ownership, system, and reference-data framework around these Production entities.

Where ownership is intended to move to a future domain architecture, the transition is recorded explicitly rather than silently redefining the entity.

Examples include:

- Employee -> HR
- Job Role -> HR
- Cost Center -> Finance
- Quality requirements -> Quality & Food Safety
- Maintenance plans/tasks -> Maintenance & Engineering

Existing identifiers remain stable during these transitions.

---

## Authoritative versus derived files

Most architecture workbooks contain authoritative structures for their subject area.

Two workbooks are deliberately derived:

- `hav_seafood_cross_domain_relationship_tables_v1.xlsx`
- `hav_seafood_shared_enterprise_reference_v1.xlsx`

These exist to simplify navigation, joining, AI context, and later dataset generation.

They should be refreshed when authoritative architecture changes.

They must never be used to overrule an authoritative source.

---

## Architecture boundaries

This folder does **not** contain historical or transactional records such as:

- sales orders
- customer invoices
- purchase orders
- supplier invoices
- production orders
- production batches
- inventory movements
- employee attendance
- absences
- payroll transactions
- recruitment activity
- QC results
- customer complaints
- maintenance work orders
- equipment downtime
- IT incidents
- CRM interactions
- financial ledger entries
- historical system logs

Those belong to later operational datasets created after the architecture and business stories have been defined.

---

## Use in later domain architectures

Future domain architectures should use this folder as the enterprise backbone.

They should:

1. reuse existing IDs;
2. respect entity ownership;
3. reference shared departments and locations;
4. use enterprise employee and organization identities;
5. use shared reference classifications;
6. preserve Production identifiers where applicable;
7. use the Systems Landscape and Data Ownership Model when defining system-originated datasets;
8. extend entities only with domain-specific attributes;
9. avoid creating competing master records.

The `hav_seafood_shared_enterprise_reference_v1.xlsx` workbook should normally be the first file inspected for general context.

The detailed authoritative workbook should then be consulted whenever precise entity definitions, ownership rules, or mappings are required.

---

## Overall role of this architecture

Together, these files form the **shared enterprise backbone** of HAV Seafood.

They provide the stable structure required to design additional domain architectures, create cross-functional business stories, and eventually generate a large synthetic operational dataset without losing consistency between departments, systems, people, products, locations, organizations, and transactions.
