# HAV Seafood — IT Infrastructure, Endpoints & Continuity Architecture

## Purpose

This workbook defines the static **IT Infrastructure, Endpoints & Continuity Architecture** for HAV Seafood.

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

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

The architecture defines the managed IT asset base, endpoint standards, logical network zones, network components, infrastructure services, system-to-infrastructure dependencies, backup requirements, recovery tiers, technical continuity requirements, patch/lifecycle standards and monitoring requirements.

It intentionally contains **no device history, patch events, network traffic, security alerts, backup executions, failed backups, outages, recovery events, hardware repairs or monitoring history**.

---

## Architecture scope at a glance

The workbook contains:

- **15 IT asset classes**;
- **103 static managed IT assets**;
- **8 reusable endpoint profiles**;
- **8 logical network zones**;
- **20 managed network components**;
- **99 asset-to-network-zone relationships**;
- **34 explicit Production-work-center-to-IT-asset bridges**;
- **14 infrastructure services**;
- **36 system-to-infrastructure dependency relationships**;
- **6 backup profiles** and **24 backup-applicability relationships**;
- **4 recovery/continuity tiers**;
- continuity requirements for all **13 existing `ESYS-*` enterprise systems**;
- continuity requirements for all **14 infrastructure services**;
- **7 patching/lifecycle profiles**;
- **12 monitoring profiles**.

The architecture is deliberately proportionate to a 92-person, single-site seafood manufacturer. It models important devices and infrastructure that can plausibly appear in later logs, incidents, support records and continuity datasets without tracking every monitor, cable, keyboard or other low-value peripheral.

---

## Core model

The main infrastructure relationship is:

`Enterprise Location`

`-> Network Zone / Infrastructure Service`

`-> IT Asset / Endpoint`

`-> Enterprise System Dependency`

The continuity relationship is:

`System / Infrastructure Service`

`-> Recovery Tier`

`-> Backup Requirement`

`-> Redundancy / Workaround Expectation`

`-> Future Recovery Execution`

The Production bridge is:

`Production Work Center`

`-> IT-managed Terminal / Label Workstation / Label Printer / Handheld`

Production remains authoritative for the work center itself.

---

## Current endpoint and asset approach

The architecture includes one managed office laptop for each of the **27 currently occupied office-based HR position seats**. The asset record references the HR position/seat and deliberately does not duplicate employee names.

Factory technology is modeled differently. Shared operational devices are attached to relevant Production work centers or enterprise locations rather than to individual Production employees. This supports later shift-based and shared-terminal activity without pretending each production operator has a dedicated PC.

The architecture also includes a dedicated privileged IT administration workstation that is structurally separate from ordinary user endpoints.

---

## Production boundary

A critical ownership distinction is:

`Production Equipment != IT Asset`

Production continues to own machinery, work centers, factory technical equipment and operational process structures.

This workbook may define an IT-managed terminal, label printer, gateway or network dependency that supports a Production work center, but it does not redefine the Production equipment itself.

Likewise:

`Factory Area / Work Center -> Production`

while:

`Network Zone / IT Endpoint / IT Server -> IT & Systems`

The `Production_IT_Bridges` sheet exists specifically to make this boundary explicit while supporting cross-domain joins.

---

## System boundary

The existing **13 `ESYS-*` systems** remain authoritative enterprise-system identities in Shared Enterprise.

The prior IT Systems, Applications & Integration Architecture remains authoritative for technical application profiles, environments, integrations and application-to-application dependencies.

This workbook adds the infrastructure underneath those applications.

Important distinction:

`Application Integration != Infrastructure Dependency`

For example, two applications may exchange business data through an integration while both separately depend on internet connectivity, enterprise identity and endpoint/network services.

---

## Network architecture

The logical network model uses **8 zones** covering corporate users, privileged IT management, infrastructure/server services, factory operations, warehouse/logistics, monitoring/IoT, managed printers/devices and guest access.

These are logical IT security/operational zones, not replacements for Shared Enterprise physical locations or Production factory areas.

The architecture intentionally excludes low-level implementation data such as:

- IP addresses;
- subnet values;
- MAC addresses;
- firewall-rule exports;
- Wi-Fi keys;
- VPN secrets;
- certificates or credentials.

Those are neither necessary nor appropriate for this Phase 1 business architecture.

---

## Backup and recovery model

Backup profiles distinguish critical hybrid/local recovery, high-importance systems, SaaS shared responsibility, infrastructure configuration recovery, named endpoints and operational endpoint rebuilds.

Important boundaries:

`Backup Requirement != Backup Job`

`Restore-Test Requirement != Restore-Test Event`

`Business Record Retention != IT Backup Retention`

IT backup architecture does not make IT the business owner of Finance, HR, Quality, Sales or other domain records.

---

## Continuity model

Four synthetic HAV Seafood recovery tiers are defined:

1. Critical operational;
2. High business importance;
3. Standard business;
4. Low / external convenience.

Every existing enterprise system receives a technical continuity classification based on the already-defined Shared Enterprise system criticality.

The workbook also defines manual-workaround expectations, but these remain high-level technology continuity statements.

**Business process continuity remains owned by the affected business domain.**

For example, IT may define that ERP has a limited temporary workaround, while Finance, Sales, Procurement or Logistics determine the actual business procedures that may be used during an outage.

---

## Monitoring and lifecycle

Monitoring requirements define what classes of health or availability should be observed for endpoints, operational devices, network infrastructure, servers, backup infrastructure, monitoring gateways, printers and power support.

Patching/lifecycle profiles define standard maintenance expectations and end-of-support treatment.

They do not contain actual:

- patches;
- software versions over time;
- firmware updates;
- monitoring metrics;
- alerts;
- device failures;
- replacements.

Those belong to Phase 3.

---

## Important conceptual boundaries

`Production Equipment != IT Asset`

`IT Asset != IT Asset Class`

`Endpoint Profile != Endpoint`

`Position Assignment != Employee Identity`

`Network Zone != Physical Location`

`System != Infrastructure Service`

`Integration != Infrastructure Dependency`

`Backup Requirement != Backup Execution`

`Recovery Target != Recovery Event`

`Monitoring Requirement != Alert`

`Lifecycle Standard != Patch / Replacement Event`

`Technical Continuity != Business Process Continuity`

---

## Workbook sheets

### `IT_Asset_Classes`
Defines reusable categories for managed endpoints, peripherals, servers, network infrastructure, backup, monitoring gateways and IT power support.

### `Endpoint_Profiles`
Defines reusable endpoint configuration/security standards for office laptops, restricted Finance/HR devices, privileged IT administration, shared factory terminals, warehouse handhelds, rugged specialist tablets and label workstations.

### `IT_Asset_Register`
Defines the current static managed IT asset identities. Important devices receive stable `ITA-*` identifiers so future operational data can reference them consistently.

### `Network_Zones`
Defines the logical IT network/security segmentation model.

### `Network_Components`
Defines the important managed switching, firewall/gateway and wireless infrastructure.

### `Asset_Network_Assignment`
Maps managed network-connected assets to logical network zones.

### `Production_IT_Bridges`
Maps selected Production work centers to the IT-managed devices that support them. Production remains authoritative for work-center identity.

### `Infrastructure_Services`
Defines common technical services such as internet, LAN, identity/network access, endpoint management, endpoint security, backup, monitoring, print services and local hybrid-system services.

### `System_Infrastructure_Depend`
Maps enterprise systems to their important technical infrastructure dependencies. It complements rather than replaces the application integration/dependency model in the prior IT workbook.

### `Backup_Profiles`
Defines reusable technical backup/recovery requirements.

### `Backup_Applicability`
Maps systems and infrastructure services to the relevant backup profile.

### `Recovery_Continuity_Tiers`
Defines the four reusable recovery-priority tiers.

### `System_Continuity_Requirements`
Maps all existing enterprise systems to recovery tiers, high-level workaround expectations and ownership.

### `Infrastructure_Continuity`
Defines resilience and restoration expectations for the shared infrastructure services.

### `Patching_Lifecycle_Profiles`
Defines lifecycle, patching and end-of-support rules by technology class.

### `Monitoring_Requirements`
Defines what classes of technical health/availability should be monitored and who is responsible.

### `Source_Precedence`
Defines authoritative-source boundaries across Shared Enterprise, HR, Production and IT.

### `Architecture_Notes`
Records the major modeling assumptions and boundaries.

### `Data_Dictionary`
Provides field-level interpretation for AI and human users.

---

## Source precedence

Key authoritative relationships are:

- Shared Enterprise remains authoritative for enterprise system identity and physical enterprise locations.
- HR remains authoritative for employees, positions, position seats and incumbency.
- Production remains authoritative for work centers, machinery and production equipment.
- IT Systems & Integration remains authoritative for technical system/application and integration architecture.
- Identity, Access & Information Security remains authoritative for system access/security requirements.
- This workbook is authoritative for IT-managed asset identity, logical network architecture, endpoint standards, infrastructure services and technical backup/recovery requirements.

If a derived or copied field in this workbook conflicts with its authoritative upstream source, the upstream source wins.

---

## Phase 1 exclusions

This workbook contains no operational history such as:

- procurement or purchase history for IT devices;
- serial-number change history;
- employee device-assignment history;
- device check-in/check-out events;
- break/fix incidents;
- support tickets;
- software installations;
- software-version history;
- patch installation records;
- vulnerability findings;
- endpoint-security detections;
- network sessions or traffic;
- firewall events;
- Wi-Fi connection logs;
- VPN sessions;
- device-health history;
- monitoring alerts;
- backup executions;
- failed backups;
- restore operations;
- outage records;
- uptime history;
- recovery events;
- lost or stolen devices;
- disposal/replacement history.

These are Phase 3 operational datasets.

---

## Recommended AI use

For fast AI navigation:

- What IT assets exist? -> `IT_Asset_Register`
- What standard applies to an endpoint? -> `Endpoint_Profiles`
- Which logical network does a device use? -> `Asset_Network_Assignment` + `Network_Zones`
- Which IT device supports a Production work center? -> `Production_IT_Bridges`
- What infrastructure does a system depend on? -> `System_Infrastructure_Depend`
- How should something be backed up? -> `Backup_Applicability` -> `Backup_Profiles`
- What is the recovery priority for a system? -> `System_Continuity_Requirements` -> `Recovery_Continuity_Tiers`
- What infrastructure has continuity requirements? -> `Infrastructure_Continuity`
- What should be monitored? -> `Monitoring_Requirements`
- What lifecycle/patching standard applies? -> `Patching_Lifecycle_Profiles`
- Who owns the underlying identifier or concept? -> `Source_Precedence`

When exact application integration, system identity, HR position or Production work-center details are needed, consult the relevant upstream authoritative workbook rather than treating the copied reference fields here as a replacement.

---

## Overall role of this architecture

Together, these sheets form HAV Seafood's **static IT infrastructure, endpoint, network and technical continuity layer**.

They connect the existing enterprise systems and physical business locations to realistic managed endpoints, shared factory technology, network zones, hybrid infrastructure, backup requirements and recovery priorities while preserving the ownership boundaries of Shared Enterprise, HR, Production and the earlier IT architecture.

This gives later synthetic IT operational data a stable structure for device records, support tickets, monitoring, outages, backup activity, patching, security events and cross-functional continuity stories without seeding those events during Phase 1.
