# HR Working-Time Framework

## Purpose

This workbook contains the static **HR Working-Time Framework** for HAV Seafood.

It defines how working time is structurally organized and classified across the current workforce without creating operational attendance history.

The workbook belongs to **Phase 1 — Business Architecture**. It contains no timesheets, clockings, actual overtime, absence events, remote-work days, schedule changes or payroll calculations.

## Files

- `hav_seafood_hr_working_time_framework_v1.xlsx` — authoritative HR working-time architecture described here.
- `hav_seafood_hr_working_time_framework_v1.md` — this compact AI-friendly description.

## Main model

The architecture separates employment rules from operational shift definitions:

`Employee / Position -> HR Working-Time Model -> HR rules`

For office employees:

`HR Working-Time Model -> HR Weekly Schedule Pattern`

For Production/Operations employees:

`HR Working-Time Model -> existing Production Shift Group / Shift Pattern`

This prevents HR from copying or redefining the existing `SH-*` and `SG-*` structures.

## Workbook sheets

### `Working_Time_Models`
Defines 10 reusable HR working-time arrangements covering production shift workers, part-time production, flexible operations, technical coverage, night sanitation, office work and salaried production support.

### `Weekly_Schedule_Patterns`
Defines HR-owned weekly schedules for office employees only. The current architecture contains three pattern families:

- standard full-time office;
- flexible full-time office;
- 24-hour fixed part-time office.

Production shift schedules are deliberately not duplicated here.

### `Employee_WT_Assignments`
Contains one current working-time assignment for each of the **92 employees**.

For the **65 employees** already represented in Production `Employee_Default_Shifts`, the existing `Shift_Group_ID` and `Shift_Pattern_ID` values are preserved exactly.

Current assignment counts by HR working-time model are:

- `HWTM-001`: 38 employees
- `HWTM-002`: 3 employees
- `HWTM-003`: 8 employees
- `HWTM-004`: 6 employees
- `HWTM-005`: 3 employees
- `HWTM-006`: 3 employees
- `HWTM-007`: 17 employees
- `HWTM-008`: 9 employees
- `HWTM-009`: 1 employees
- `HWTM-010`: 4 employees

### `Role_Position_Defaults`
Defines the default working-time model for all 56 enterprise job roles, including permitted alternative models where part-time or mixed Production coverage is structurally expected.

### `Time_Categories`
Defines controlled future time classifications such as normal working time, overtime tiers, evening/night/weekend/holiday work, on-call availability, call-out work, training, travel and absence bridge categories.

Working Time owns the classification. Compensation owns the monetary premium values.

### `Overtime_Rules`
Defines synthetic company overtime-classification structures for hourly, salaried and technical/call-out populations.

These are internal fictional assumptions, not statements of Faroese law or collective agreements.

### `Break_Rules`
Defines office break structures and a Production pointer rule. Production break minutes and paid hours remain sourced from existing `SH-*` patterns.

### `Time_Registration_Rules`
Defines how time is structurally recorded for different populations. All time/attendance records are intended to be mastered in `ESYS-005` People & Payroll.

### `Holiday_Calendar_Rules`
Defines structural treatment of company-designated holidays and weekends but intentionally contains no dated annual holiday calendar.

### `Production_Shift_Mappings`
Maps HR working-time models to eligible existing Production `SH-*` shift patterns while retaining Production values for start time, end time, paid hours and break minutes as source references.

### `Flex_Remote_Rules`
Defines synthetic flex-time and remote-work eligibility rules for office, management, operational and technical populations.

### `Control_Parameters`
Records core architecture assumptions and counts.

### `Source_Mappings`
Documents relationships to the existing HR, Production, Compensation, Systems and Data Ownership architecture.

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

### `Data_Dictionary`
Defines fields used throughout the workbook.

## Ownership boundaries

### HR Working Time owns

- working-time model definitions;
- HR-owned office schedules;
- working-time/time-category classification;
- overtime classification logic;
- office break rules;
- time-registration rules;
- holiday/weekend classification framework;
- flex-time and remote-work rules;
- current employee-to-working-time-model mapping;
- HR interpretation/mapping of existing Production shift structures.

### Employee Employment Master owns

- current weekly hours;
- FTE;
- time-registration-required flag;
- overtime-eligible flag;
- shift-worker flag.

### Employment Terms & Contract Framework owns

- contractual working-hours basis;
- contractual overtime eligibility;
- shift-work eligibility.

### Compensation Structure owns

- overtime premium percentages;
- evening/night/weekend/holiday premium amounts;
- on-call allowance values;
- other monetary compensation rules.

### Production Architecture owns the existing architectural definitions for

- `SH-*` shift patterns;
- `SG-*` shift groups;
- current Production employee default shift assignments;
- Production work-center shift coverage.

The enterprise System & Data Ownership Model separately identifies `ESYS-005` People & Payroll as the authoritative system for standard shift masters and operational time/attendance. This is treated as **system ownership**, while the existing Production workbook remains the current authoritative **architecture source** for the seeded `SH-*` / `SG-*` definitions. The two concepts are deliberately kept separate.

## Phase 3 boundary

This architecture intentionally contains no:

- clock-in/out records;
- timesheets;
- attendance events;
- late arrivals;
- missed punches;
- actual overtime hours;
- actual night/weekend/holiday hours;
- schedule changes;
- shift swaps;
- remote-work days;
- actual call-outs;
- absence records;
- payroll calculations or payments.

Those will be generated later after the business stories are designed.

## Legal boundary

The office schedules, flex windows, remote-work limits and overtime-tier logic are **synthetic HAV Seafood assumptions**. They are not presented as Faroese statutory requirements, collective-agreement terms or legal advice.
