Page:
Glossary
Pages
Architecture
Changelog
Crewing Architecture
Crewing Data Model
Crewing Design Document
Crewing Implementation Spec
Crewing Module
Crewing Roles and Permissions
Crewing Use Cases
Crewing User Stories
Crewing Workflows
Data Model
Deployment and Operations
Design System
E2E Test Framework
E2E Test Plan
Environment Variables
Feature Catalogue
File Storage
Getting Started
Glossary
Home
Inventory and Catalogue
Inventory on Approval
Issue to Deploy Pipeline
Notifications
Open Questions
PO Lifecycle
Pages and Navigation
Planned Features
Playwright Test Design
Purchase Orders
Reports Mockup
Reports
Roles and Permissions
Tech Debt
Test Plan
Test
Testing
Vendors and GST Lookup
Workflows
No results
Table of Contents
This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
Glossary
Domain vocabulary for Pelagia Portal (PPMS). Several terms shifted from the original design — the definitions below are the shipped meanings.
| Term | Meaning |
|---|---|
| PPMS | "Pelagia Payment Management System" — the in-UI brand for Pelagia Portal (login, sidebar, title). |
| Purchase Order (PO) | The central record: a request to buy goods/services, tracked through its lifecycle from DRAFT to CLOSED. |
| Cost Centre | A Vessel. Every PO is raised against a Vessel (PurchaseOrder.vesselId, required). Surfaced as "Cost Centre" everywhere in the UI (/admin/vessels → "Cost Centre Management"). The earlier Vessel-or-Site cost-centre model was removed. |
| Vessel | A ship; the cost centre a PO is charged to. Has a unique code used in PO numbers. |
| Accounting Code | A budget head: a leaf in the 3-level Account hierarchy (Top Category → Sub-Category → Leaf), 6-digit numeric. Only leaf codes are PO-selectable. Previously labelled "Account". |
| Company | The sister company a PO is billed under (e.g. PMS, HNR, DEI). Its GST/address details appear on the exported PO. Optional per PO. |
| PO Number | Auto-formatted COMPANY/VESSEL/ID/FY (e.g. PMS/HNR1/9000/2024-25). System IDs start at 9000; imported POs keep their original number. |
| FY | Indian financial year (Apr–Mar), rendered YYYY-YY in PO numbers. |
| Vendor | A supplier. Submitter-created vendors are unverified until a PO closes/pays with them, on import, or a Manager/Accounts/Admin verifies. The formal vendorId is the verified code. |
| GSTIN | 15-char Indian GST identification number; looked up via the GST microservice to auto-fill vendor details. |
| Site | A port/depot/office that holds inventory; used for delivery and vendor-distance sourcing. Not a cost centre. |
| Product / Item | A catalogue entry (code, name). Tracks lastPrice/lastVendor and per-vendor prices, updated on payment. |
| Line Item | A row on a PO: name, qty, unit, unit price, GST rate; optional product link and per-line accounting code. |
| Submitter | The user who raised a PO (Technical / Manning / Manager / SuperUser). |
| Partial payment / receipt | PARTIALLY_PAID / PARTIALLY_CLOSED states that loop until the full amount/quantity is settled. |
| POAction | An audit-trail row recording one event/transition on a PO (actor, type, note, metadata). |
| Receipt | Proof-of-delivery record (file + notes) confirming a PO; closes it. |
| Import PO | Uploading a Pelagia-format Excel PO straight into CLOSED as a historical record. |
| Inventory flag | NEXT_PUBLIC_INVENTORY_ENABLED — gates site stock/consumption surfaces. |
| pms1 | The single Ubuntu server hosting the app, DB, Forgejo, and CI runner. |
ppms |
The pm2 process running the production app on port 3000. |
pelagia / pelagia_test |
Production DB / its daily mirror used for staging + autofix verification. |
| Report Issue | Header button that files a Forgejo issue, kicking off the issue-to-deploy pipeline. |
| Staging | A deployed instance of latest master (pm2 ppms-staging, port 3200, SSH-tunnel only) for pre-release smoke testing. |
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.