Home / Platform
One layer. Five disciplines.
Port-Systems isn't a chatbox bolted onto a database. It's a stack: connectors, a domain model, governance, a query interface, and the outputs your business actually consumes.
The data stack
From raw sources to auditable answers
Each layer has a distinct job. None can be skipped, and together they're what makes the answers safe to act on.
Layer 05
Aggregation
Connectors
APIs, databases, log files, spreadsheets, supplier portals, pull in everything that matters without forcing teams off their tools.
Layer 04
The Model
Normalisation & domain logic
Carbon factors, vessel taxonomies, asset hierarchies, the messy stuff is reconciled once, in code, with versioned logic.
Layer 03
Governance
The data boundary
Role-based access, lineage tracking and the local-first guardrails that keep operational data inside your boundary.
Layer 02
Query Interface
Plain-English Q&A
Anyone on your team can ask in plain English. The system translates intent into queries against your trusted internal data, never the open web.
Layer 01
Output
Recurring reports & insight
Monthly board packs, ESG submissions, ad-hoc questions, every answer carries a citation back to the source record.
Day in the life
Same platform. Two very different users.
Port-Systems serves the floor and the boardroom from the same trusted data, what each role sees is governed by access, not by buying a separate product.
Operational user
Estates Manager
Show me energy spikes in South Harbour yesterday.
Anomaly at 14:00. Shore power load exceeded baseline by 15%.
Cross-reference with vessel arrivals.
Two cruise vessels berthed 13:50–18:30. Citing AIS log #221, Meter A4.
Strategic user
Finance Director
Draft the monthly carbon report for the Board.
Drafting… Table 1: Scope 1 emissions, Table 2: Scope 2 by site.
Include source citations.
Citing Invoice #4401, Meter Log #B2, Vessel Log #M03 throughout.
Implementation
From signed-off scope to live monthly outputs in 12 weeks
Each node ships in a fixed three-month sprint. We pilot in parallel with your existing reporting so nothing breaks.
Weeks 1–2
Co-design
Confirm use cases, map workflows, lock KPIs.
Phase 1
Weeks 2–4
Discovery
Integration design, data owners, security protocols.
Phase 2
Weeks 4–8
Build
Ingestion pipelines, domain model, platform configuration.
Phase 3
Weeks 8–10
Pilot
Deploy, train champion users, run parallel reporting.
Phase 4
Weeks 10–12
Evaluation
Field trial, measure savings, plan the next node.
Phase 5