# HR Employment Terms & Contract Framework

## Purpose

`hav_seafood_hr_employment_terms_contract_framework_v1.xlsx` defines the **static employment terms and contract architecture** for HAV Seafood. It is part of Phase 1 business architecture and provides reusable contract profiles, contractual term categories, current employee-to-contract assignments, probation/notice structures, agreement coverage, and profile applicability rules.

It does **not** contain historical contract amendments, renewals, signed-document events, terminations, payroll transactions, or other operational history.

## Main contents

- **Contract_Profiles** — 12 reusable HCP-* contract profiles. Eight are currently used by the 92-person workforce and four are reserved for future fixed-term, seasonal and trainee scenarios.
- **Contract_Profile_Terms** — reusable profile-specific contractual framework terms across working time, location, shifts, overtime, confidentiality, information security, food safety, equipment, travel, remote work, training, benefits, pension, expenses, IP and duties.
- **Employee_Contract_Assignments** — one current HRC-* contract relationship for each of the 92 existing employees, linked to Employee_ID, Position_Seat_ID, Position_ID and Contract_Profile_ID.
- **Employment_Term_Categories** — controlled categories used by Contract_Profile_Terms.
- **Probation_Rules** — reusable synthetic HPR-* probation structures.
- **Notice_Rules** — reusable synthetic HNR-* notice structures.
- **Agreement_Coverage** — internal HAP-* company/management/executive terms frameworks. No real collective agreement or union agreement is named.
- **Contract_Applicability** — default rules mapping HR employee groups/employment classifications to contract profiles.
- **Source_Mappings** — ownership, foreign-key and source relationships.
- **Architecture_Notes** — modeling assumptions and boundaries.
- **Data_Dictionary** — field definitions and logical datatypes.

## Current contract-profile distribution

- `HCP-001` Permanent Salaried Executive — 1 employee
- `HCP-002` Permanent Salaried Management — 9 employees
- `HCP-003` Permanent Salaried Professional — 20 employees
- `HCP-004` Permanent Hourly Operations Supervisor / Lead — 10 employees
- `HCP-005` Permanent Hourly Operations Full-Time — 39 employees
- `HCP-006` Permanent Hourly Operations Part-Time — 6 employees
- `HCP-007` Permanent Hourly Technical — 6 employees
- `HCP-008` Permanent Hourly Office Part-Time — 1 employee

The four additional profiles `HCP-009`–`HCP-012` are available architecture structures with no current employee assignments.

## Relationships with existing HR architecture

The workbook references and does not redefine:

- employee identity and current employment classifications from `hav_seafood_hr_employee_employment_master_v1.xlsx`;
- `Position_ID` and `Position_Seat_ID` from `hav_seafood_hr_positions_workforce_establishment_v1.xlsx`;
- enterprise/Production-preserved Employee, Role, Department and Position identifiers.

Each current employee receives one current `Contract_ID` (`HRC-001`–`HRC-092`). `Contract_ID` represents the current contractual relationship in the architecture, not a historical event or a generated signed document.

## Legal and agreement boundary

Probation durations, notice periods and agreement structures in this workbook are **synthetic company assumptions designed for the fictional dataset**. They are not presented as Faroese statutory law, verified collective-agreement terms, or legal guidance.

No real union or collective agreement is named. This avoids creating false real-world legal claims while still giving the later synthetic dataset enough structure to generate realistic internal HR records and documents.

## Boundaries with later HR architecture

This workbook does not own detailed:

- salary bands, wage rates, premiums, allowances or benefit values — **Compensation Structure**;
- calendars, working-time schedules, overtime calculations or break rules — **Working Time Framework**;
- leave entitlements or absence rules — **Leave & Absence Framework**;
- training records or detailed competency requirements — **Competency & Training Framework**;
- HR policy text — **Policy & Employee Relations Framework**;
- signed contracts, amendments, renewals or termination events — later operational/history datasets.

Production remains authoritative for production shift definitions, crew structures, skills, work-center qualifications and operational staffing requirements.

## Identifier decision

New HR-local identifiers use `HRC-`, `HCP-`, `HPR-`, `HNR-`, `HAP-`, `HCA-`, `HTC-` and `HPT-` prefixes. These are provisional HR-local conventions to be registered in Shared Enterprise identifier standards during a later architecture refresh.

`HCP-` is deliberately used for Contract Profile rather than `CP-`, because the existing Production Architecture already uses `CP-*` identifiers for HACCP/control points.

## Architecture principle

This is a **current-state framework**, not an effective-dated contract history model. Later transactional datasets can generate contract documents, amendments, renewals and terminations against these stable IDs and rules without redefining the underlying employment architecture.
