Table of Contents
Planned Features
Work that is designed but not yet shipped — proposals, mockups, and post-MVP ideas. Nothing on these pages is wired to the database or live in the product; they exist to align on scope and UX before implementation. For what is shipped, see the Feature Catalogue. (Reports has since shipped — see Reports.)
Crewing / Manning
A post-MVP Crewing Module that extends PPMS from a purchasing system into a crew lifecycle system — auto-raised requisitions on sign-off, a gated candidate pipeline, onboarding, site HR (attendance, leave, PPE, documents), and a monthly wage report for Accounts. It reuses the PO module's state-machine, permission-map, audit-trail and file-storage patterns.
→ Crewing Implementation Spec — the authoritative, reconciled build instruction set (design handoff ⨝ wiki docs, with the CHANGELOG as tiebreaker): reconciliation decisions, codebase changes, the final roles/nav matrices, and the detailed screen spec.
→ Crewing Module — landing page with the full page map: design document, architecture, data model, workflows, use cases, roles & permissions, and user stories (Mermaid diagrams throughout).
Add new planned features here as they are designed. When a planned feature
ships, move its page out of Planned/ into the relevant section and record it in
the Changelog and Feature Catalogue.
Pelagia Portal (PPMS)
Overview
Build & Run
System
Product
- Feature Catalogue
- Pages and Navigation
- Workflows
- Purchase Orders
- Vendors and GST Lookup
- Inventory and Catalogue
- Inventory on Approval
- Notifications
- File Storage
- Design System
Planned
Quality
Ops
Engineering
Pelagia Portal (PPMS) — internal purchase-order management. Self-hosted on pms1, live at pms.pelagiamarine.com. This wiki tracks the shipped product; authoritative sources are the repo code, App/CLAUDE.md, Docs/, and CHANGELOG.md.