# HAV Seafood — Enterprise Systems Landscape

## Purpose

This workbook defines the static application/system landscape for HAV Seafood. It describes which enterprise systems exist, their primary purposes, business and technical owners, departmental usage, major functions, high-level data-domain involvement, integrations, deployment types, criticality and location/use relationships.

It describes **how the system environment is designed**, not system activity or operational history.

## Workbook contents

- **Systems** — Authoritative register of 13 enterprise systems using `ESYS-*` identifiers.
- **System_Categories** — Controlled classification of ERP, MES, QMS, CMMS, HR/payroll, CRM, collaboration, identity, BI and specialist systems.
- **System_Department_Map** — Shows which HAV Seafood departments use or support each system.
- **System_Functions** — Major business/technical capabilities provided by each system.
- **System_Data_Domains** — High-level mapping of systems to business domains and information subjects; this does not designate systems of record.
- **System_Integrations** — Static designed interfaces, including API, scheduled, cloud-native and deliberately manual/file-based handoffs.
- **Deployment_Types** — Cloud SaaS, cloud platform, on-premises, hybrid and external-portal classifications.
- **System_Criticality** — Static business criticality classifications.
- **System_Locations** — Enterprise locations where systems are primarily used or operationally deployed.
- **Architecture_Notes** — Scope, boundaries and major design decisions.
- **Data_Dictionary** — Field definitions and key/reference rules.

## Architecture approach

HAV Seafood is modeled with a realistic, moderately fragmented system landscape rather than one platform doing everything. Core ERP supports finance, procurement, sales, inventory and basic warehouse administration; separate systems support production execution, quality, maintenance, HR/payroll and CRM. Microsoft 365, Entra ID and Power BI provide shared productivity, identity and reporting capabilities. Specialist systems handle label printing, cold-chain monitoring, security/backup and online banking.

Several interfaces remain scheduled or manual/file-based. This is intentional and will later allow realistic Excel/CSV/PDF/email workflows in the operational synthetic dataset.

## Boundaries

This workbook does not contain user accounts, devices, permissions, software versions, system logs, incidents, support tickets, backup jobs, integration events or business transactions. It also does not determine the final system of record for each business entity; that belongs to the separate **System & Data Ownership Model**.

Production lines that use legacy `SYS-*` identifiers remain Production entities. Enterprise IT systems use `ESYS-*` to avoid identifier collision.
