shad0w/pelagia-portal
1
0
Fork 0
Code Issues 8 Pull requests Projects Releases 2 Packages Wiki Activity Actions

Update Crewing Design Document

shad0w 2026-06-21 20:19:21 +00:00
parent 24dc4c62c1
commit 9bcc43f460
1 changed files with 171 additions and 164 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
Crewing-Design-Document.md

@ -37,7 +37,7 @@ we don't issue).
| **MPO** | Manning / Personnel Officer in the office | existing `MANNING` role | | **MPO** | Manning / Personnel Officer in the office | existing `MANNING` role |
| **Accounts** | Finance team | existing `ACCOUNTS` role | | **Accounts** | Finance team | existing `ACCOUNTS` role |
| **Manager** | Department / crewing manager | existing `MANAGER` role | | **Manager** | Department / crewing manager | existing `MANAGER` role |
| **Candidate** | External applicant (ex-hand or new) | unauthenticated public form / lightweight `CANDIDATE` identity | | **Candidate** | External applicant (ex-hand or new) | unauthenticated public form |
| **Crew member** | Onboarded employee | data subject; not necessarily a portal login in v1 | | **Crew member** | Onboarded employee | data subject; not necessarily a portal login in v1 |
| Admin / Superuser / Auditor | as in PO module | existing roles | | Admin / Superuser / Auditor | as in PO module | existing roles |
@ -154,11 +154,18 @@ Manager**, and **sent to Accounts** for disbursement.
| # | Question | | # | Question |
|---|---| |---|---|
| Q1 | New role `SITE_STAFF`, or extend `TECHNICAL`/`MANNING`? | | Q1 | New role `SITE_STAFF`, or extend `TECHNICAL`/`MANNING`? |
| A1 | New role `SITE_STAFF_*` for the site heirarchy, MPO is "MANNING" |
| Q2 | Does the candidate self-apply form live inside the portal (public route) or on the marketing site posting to an API? | | Q2 | Does the candidate self-apply form live inside the portal (public route) or on the marketing site posting to an API? |
| A2 | Lives at the static site pelagiamarine.com |
| Q3 | EPFO verification — assisted-manual now, or build an EPFO proxy microservice like GstService? | | Q3 | EPFO verification — assisted-manual now, or build an EPFO proxy microservice like GstService? |
| A3 | EPFO proxy microservice like GstService would be better |
| Q4 | Should salary structures be versioned per assignment (raises mid-contract) in v1, or single-structure-per-assignment? | | Q4 | Should salary structures be versioned per assignment (raises mid-contract) in v1, or single-structure-per-assignment? |
| A4 | It is possible for the salary and entire contract to be changed mid assignment and salary must be calculated accordingly (days x amt 1 + days x amt 2) |
| Q5 | Is victualing part of the wage report total, or a separate accrual line? | | Q5 | Is victualing part of the wage report total, or a separate accrual line? |
| A5 | separate accrual line? |
| Q6 | Do we need crew self-service (view own docs/payslip) in v1 or v2? | | Q6 | Do we need crew self-service (view own docs/payslip) in v1 or v2? |
| A6 | No, only PM APM Site-incharge users needed from site, they will generate slips for other site crew members |
| Q7 | Attendance granularity — daily present/absent only, or shift/hours? | | Q7 | Attendance granularity — daily present/absent only, or shift/hours? |
| A7 | Shift/hours + overtime? |
See the requirement backlog in [Crewing User Stories](Crewing-User-Stories). See the requirement backlog in [Crewing User Stories](Crewing-User-Stories).