# HAV Seafood — HR Positions & Workforce Establishment

## Purpose

This workbook defines the static HR position and workforce-establishment architecture for HAV Seafood. It describes **what positions and approved seats currently exist, how they relate to the organization, and who currently occupies them**. It is part of Phase 1 business architecture and is not an operational or historical staffing dataset.

## Workbook

`hav_seafood_hr_positions_workforce_establishment_v1.xlsx`

## Core model

The architecture separates four concepts:

`Job Role -> Position Definition -> Position Seat -> Employee Incumbent`

- **Job Role** describes a reusable type of work and remains defined in the enterprise job-role architecture.
- **Position Definition** describes the structural organizational position, reporting line and organizational home.
- **Position Seat** represents an individual approved headcount/FTE seat under a position definition.
- **Position Incumbency** links a current employee to a current approved seat.

This seat layer is necessary because the existing Shared Enterprise architecture already contains multi-seat management positions. For example, `POS-PROD-SHIFT` is one structural Shift Supervisor position definition with two approved seats. The new model preserves that existing `Position_ID` rather than replacing it with competing identifiers.

## Current establishment

- **56 structural position definitions** — one for every active enterprise job role.
- **95 approved position seats**.
- **92 current employee incumbents**.
- **90.2 occupied FTE** based on the existing HR employment-hours architecture.
- **93.2 approved FTE**.
- **3 approved vacant seats**.

The three current approved vacancies are:

- Fish Processing Operator (`R009`)
- Mechanical Maintenance Technician (`R026`)
- Key Account Manager (`R037`)

These vacancies are neutral architecture assumptions intended to distinguish approved establishment from current employee headcount. They are not recruitment events, historical records or embedded business stories.

## Sheets

### `Positions`
Authoritative structural position definitions. Reuses all existing Shared Enterprise management `POS-*` identifiers and extends the same convention to all remaining enterprise roles. Defines role, department, organizational unit, structural reporting position, location, cost center, level, type and current structural status.

### `Position_Seats`
Authoritative individual approved seats beneath each structural position definition. Includes seat-level approved FTE and current occupied/vacant availability.

### `Position_Incumbency`
Authoritative current-state relationship between the 92 employees and their approved position seats. Contains current occupancy only; there is no assignment history.

### `Workforce_Establishment`
Derived position-level summary of approved seats/FTE, occupied seats/FTE and vacant seats/FTE.

### `Department_Summary`
Derived department-level summary of the current establishment. This is a navigation/reporting view, not a master-data source.

### `Position_Statuses`
Controlled structural, seat-control and availability statuses.

### `Position_Types`
Controlled position-type definitions such as executive, management/lead and regular established positions.

### `Position_Role_Mappings`
Simplified position-to-role relationship table.

### `Position_Org_Mappings`
Simplified position-to-department, organizational unit, location, cost center and reporting-position relationship table.

### `Source_Mappings`
Documents authoritative ownership and how existing enterprise/Production structures are treated.

### `Control_Parameters`
Contains the 40-hour full-time baseline and current architecture counts used by the model.

### `Architecture_Notes`
Documents modeling decisions, boundaries and assumptions.

### `Data_Dictionary`
Defines fields, datatypes and relational rules.

## Ownership and boundaries

HR owns:

- structural HR position extensions beyond the Shared Enterprise seed;
- individual approved position seats;
- approved seat FTE;
- current position incumbency;
- current workforce establishment.

Shared Enterprise remains authoritative for:

- employee identity IDs;
- departments and organizational units;
- enterprise locations;
- the existing management-position IDs;
- shared identifier conventions.

Enterprise Job Roles remains authoritative for `Role_ID` and role taxonomy. Finance may later extend the existing cost-center structure.

Production remains authoritative for:

- work-center staffing requirements;
- production shifts and crew groups;
- work-center qualifications;
- production skills and cross-training;
- line capacity and staffing rules.

The uploaded Production staffing workbook contains 71 work-center staffing-requirement records. Their role references were validated against the enterprise role master. The HR establishment **does not replace or reinterpret those work-center minimum/typical staffing requirements**.

## Reporting hierarchy

The structural reporting hierarchy uses `Reports_To_Position_ID`, not only person-to-person manager references. This allows the organization design to remain valid when a seat becomes vacant or the incumbent changes. Current `Manager_Employee_ID` relationships remain person-level current-state references elsewhere in the architecture.

## Relationship with Employee Employment Master

The Employee Employment Master was created before this full position model and therefore contains only the earlier partial `Position_ID` references inherited from Shared Enterprise. This workbook is now authoritative for **complete current position occupancy** through `Position_Incumbency`.

## Architecture boundary

This workbook intentionally does **not** contain:

- historical position assignments;
- promotions or transfers;
- historical vacancies;
- recruitment requisitions or applicants;
- hiring activity;
- reorganizations over time;
- budget transactions;
- payroll data;
- attendance or absence records;
- actual production staffing by shift/date.

Those belong to later Phase 3 operational/history datasets after the business stories are designed.
