# HAV Seafood — Enterprise Locations

## Purpose

This workbook defines the static company-wide location architecture for HAV Seafood. It establishes the main site, enterprise location hierarchy, location types, department-to-location relationships, and mappings to the detailed factory and storage structures already defined in Production Architecture.

It describes **what locations exist and how they relate**, not operational activity occurring at those locations.

## Workbook contents

- **Sites** — Defines HAV Seafood's main physical site and company/site identifiers.
- **Enterprise_Locations** — Authoritative enterprise-level locations, including the shared office area, factory building, and enterprise references for the nine top-level Production factory sections.
- **Location_Types** — Controlled classifications used by enterprise locations.
- **Department_Location_Map** — Maps each enterprise department to its primary or supporting locations.
- **Production_Location_Map** — Crosswalk from all existing Production factory-area and storage-location IDs to the appropriate enterprise location.
- **Architecture_Notes** — Key scope, ownership, compatibility, and modeling decisions.
- **Data_Dictionary** — Field definitions, datatypes, keys, and usage notes.

## Relationship to Production Architecture

This workbook is authoritative for enterprise `Site_ID` and `Location_ID` values. Production Architecture remains authoritative for detailed `SEC-*`, `FA-*`, and `SL-*` entities and for hygiene zones, temperatures, capacities, room details, storage rules, and operational flows.

The Production IDs are preserved and mapped rather than replaced. This allows HR, IT, Finance, Quality, Logistics, and other future domains to reference a common enterprise location structure while retaining detailed Production architecture where necessary.

## Boundaries

This workbook does not contain inventory balances or movements, employee location history, access events, environmental readings, maintenance events, or other dated operational data. Detailed office rooms and IT infrastructure locations are also intentionally deferred until another domain requires them.
