Port optimization systems: what they are, which types exist and where they do not check each other

Port optimization systems are not one product but a family: a port community system (PCS), a terminal operating system (TOS), vessel traffic services (VTS), ERP and weighbridge software. Each plans its own link of the port chain but none checks the others, so the discrepancies between them need a separate, independent control.

What are port optimization systems?

"Port optimization system" is not a precisely defined category. The term usually means any software that shortens the time a ship, wagon or truck spends in a port and reduces errors. A port has many independent parties: the port authority, stevedoring companies, ship agents, forwarders, customs and the rail carrier. Each uses its own system, so optimization happens in layers:

• ship arrival and traffic: just-in-time arrival (JIT) and vessel traffic services (VTS);
• cargo and declaration exchange: port community system (PCS), customs systems, eFTI from 2027;
• handling at the terminal: terminal operating system (TOS);
• weighing and accounting: weighbridge systems and ERP;
• money: contracts, tariffs and invoices.

None of these systems covers the whole chain on its own. This guide shows what each does, which data it holds and where a gap appears between them.

Port management systems: types compared

The table is our classification, built from public sources. Names are used inconsistently in the market, especially PMIS; in this guide it means the port manager's (authority's) systems.

Sources: PMIS data fields: data.gov.lt Klaipėda vessel register; PCS: IPCSA and KIPIS terms of use; TOS: Wikipedia and Kaleris; VTS: IMO; weighbridge: svarstykles.lt; ICS2: European Commission. The ERP row is a general description without a separate source.

Terminal operating system (TOS): what it does

A terminal operating system (TOS) aims to control the movement and storage of various types of cargo in and around a port or marine terminal, and helps use assets, labour and equipment better and plan the workload (Wikipedia). Vendors describe mixed-cargo TOS as covering vessel, yard, gate, truck, rail and barge operations, capturing billable activities and simplifying billing (Kaleris, vendor claim).

What matters for a buyer: a TOS is itself a source of data. It knows what operators enter or scan and calculates from that. Whether its data matches the carrier's, the port authority's or customs' data is usually not its purpose (INF).

Port community system (PCS) and KIPIS

The International Port Community Systems Association (IPCSA) describes a PCS as an electronic platform that connects the multiple systems operated by the organizations making up a sea or air port community (IPCSA). Typical services: electronic information exchange, customs declarations, cargo status tracking, dangerous goods processing and statistics.

In Klaipėda a similar purpose is served by KIPIS (Cargo and Goods Information System), operated by the port authority. According to its terms of use, KIPIS is meant for electronic information exchange between companies moving cargo through the port and the authorities supervising them. Digital Lithuania describes how declaration data is passed through a web interface directly to the customs system. This is our classification: KIPIS may be officially called something else, but its function is similar to a PCS.

Two clauses of the terms matter for control: clause 20, the user is liable for the correctness of data provided to other users; clause 24, the port authority does not verify and is not responsible for the correctness of data one user provides to others. The system passes data on but does not reconcile it with the terminal's own records. More, including the Latvian and Polish platforms (Lithuanian): port community system (PCS) and KIPIS.

Vessel traffic services (VTS)

According to the IMO, vessel traffic services are shore-side systems ranging from simple information messages to ships to extensive management of traffic within a port or waterway. Under SOLAS regulation V/12 governments may establish VTS where the volume of traffic or the degree of risk justifies it (IMO).

In Klaipėda the vessel traffic radar monitoring system was upgraded in July 2026 at a cost of almost EUR 2.2 million. The authority states that the upgraded system is linked to other information systems operating in the port and has stronger resilience to cyber threats (Atvira Klaipėda, Lithuanian). VTS is a maritime safety and traffic system, not a cargo-handling or invoicing system.

Terminal software: ERP, invoicing and weighbridge systems

Besides a TOS, a terminal usually runs an ERP or accounting system (contracts, tariffs, invoices) and weighbridge software. A Lithuanian weighbridge supplier describes automated scales that record weight, vehicle number and time and, where needed, integrate them into an ERP or accounting system (svarstykles.lt, vendor claim).

So the same cargo is recorded in several places: the carrier's consignment note, weighing tickets, the TOS, the ERP invoice, the declaration. When nobody reconciles these records, the differences surface only in a dispute. What exactly to compare (Lithuanian): TOS and ERP data reconciliation.

Ship arrival optimization: JIT and the port call process

The IMO describes that a port call today is often not optimized: ships "hurry" only to find the berth occupied and wait at anchorage or maneuver at very low speed. Just in Time (JIT) describes a ship that has sailed with the least bunker fuel consumed but still arrives in time (IMO JIT portal).

• Benefits according to the IMO: less fuel and emissions, shorter anchorage time, better navigational safety, and better capacity planning of berths and nautical services.
• A number, with a caveat: a study commissioned by the Low Carbon GIA found that in container shipping JIT could result in an average CO2 reduction of 14.16% per voyage; optimizing only the last 24 hours saves on average 5.90% (IMO JIT portal). This is a modelled potential, not an achieved result.
• Barriers: contracts (for example a voyage-charter due-despatch clause), port procedures, data and standards, and stakeholder cooperation. The IMO stresses that JIT needs strong cooperation between authorities, cargo services and the ship operator, and data exchange with other port service providers.

The port of Klaipėda publishes the expected and actual arrival and departure times of international ships and the berth number as open data (data.gov.lt, licence CC BY 4.0). Such data lets a terminal compare the time the port registered with its own records.

Port digitalization and digital twins

A digital twin is a digital model of a real object or process that is continuously fed with data. The Klaipėda port authority takes part in DigiTechPort2030 (decarbonization of small and medium ports in the southern Baltic): the "Energy Twin" pilot supplements existing digital models with at least one layer to improve environmental and port performance efficiency and to model renewable energy integration (Klaipėda, Ystad and Rostock). The software development investment is EUR 645 thousand from the port authority and EU funds (Klaipėda port authority, Lithuanian).

Our inference (INF): a model is only as reliable as the data feeding it. If vessel, wagon or weight records differ between systems, the twin will show one of them and not notice the other. More on projects and dates (Lithuanian): port digitalization in Lithuania and the Baltics.

2027 rules: eFTI, EMSWe and ICS2

• eFTI (Regulation (EU) 2020/1056): from 9 July 2027 the authorities of all EU Member States must accept information shared electronically through certified eFTI platforms. The Commission plans to adopt the remaining implementing specifications by December 2026 (European Commission). Through the eFTI4EU project the Klaipėda port authority is building additional KIPIS functions so that it can be integrated into the common European eFTI system (Atvira Klaipėda, Lithuanian).
• EMSWe (Regulation (EU) 2019/1239): applicable since 15 August 2025; harmonizes ship reporting for arrival, stay and departure, establishes the once-only principle and repeals Directive 2010/65/EU (European Commission). It concerns ship reporting, not cargo handling at the terminal.
• ICS2: since 1 June 2026 every consignment entering the EU territory by any means of transport should have a valid entry summary declaration (ENS) (European Commission).

What this means for a terminal: data has to be structured, machine-readable and consistent with what the terminal itself recorded. Whether your company needs an eFTI platform depends on its role in the chain; discuss that with a legal or customs adviser.

Where the systems do not check each other: money and time losses

Each system above does exactly what it was built for. The gap arises because the same information is entered several times in different places and reconciling it is nobody's task. Public references support this:

• The description of the Latvian ports project says cargo data and documents circulate in different formats and information systems, and coordinating documents and collecting data takes a large allocation of time and resources (Freeport of Riga Authority).
• The IMO lists data and standards among the barriers to JIT (IMO JIT portal).
• The KIPIS terms state that the port authority does not verify the data users provide (KIPIS terms, clause 24).

Concrete examples where a difference turns into money or time:

Rail invoice check: LTG wagon charges

In the LTG Cargo 2026 additional services price list the use of a carrier's inventory and reserve wagon costs EUR 2.16 per wagon-hour, and cargo storage organization costs EUR 46.60 per wagon-day; the latter is charged when the consignee does not accept the cargo within 24 hours of the arrival notice (LTG Cargo price list, excl. VAT, Lithuanian). The charge depends on points in time. The carrier counts from its own recorded times while the terminal's rail desk records its own. If they differ, the terminal pays the difference unless someone recomputes every wagon (INF). How this is done: rail statement audit.

Port infrastructure charge

From 1 July 2026 Klaipėda port dues are called the Port Infrastructure Charge and are calculated under the Minister of Transport's order No. 3-306 and the Lithuanian Transport Safety Administration's order No. 2BE-95; the port authority states that the amounts are unchanged and only the name and legal basis changed (Klaipėda port authority). The rates are set in an annex to the administration's order; in our research they appear as rates per gross tonnage (GT) unit by vessel and operation type (INF; we do not reproduce the annex table on this page). A wrongly classified vessel type or tonnage can therefore become an invoice error, and the terminal's vessel-call records are worth comparing with the port register (INF).

Weight differences: scales, consignment note, invoice

Article 43 of SMGS sets how much loss of cargo mass in transit the carrier treats as natural and is not liable for: 2% for liquid or raw (wet) cargoes, 1% for dry cargoes, with the norms for cargo carried loose, in bulk or poured increased by 0.3% for each transhipment, and 0.2% for cargo whose mass does not decrease naturally (SMGS text, Lithuanian). To separate normal loss from shortage you must compare weights from the consignment note, the weighbridge and the warehouse records, and these sit in three different systems.

Stock and revenue leakage in general

The UK port operator Peel Ports, investing GBP 4 million in a digital bulk-cargo programme with TBA, expects to halve stock losses and reduce revenue leakage by up to 3% (Port Strategy). This is the company's expectation, not an achieved result, and it shows that a company treats revenue leakage as a quantifiable problem.

How an independent control layer works

An independent control layer does not run port operations. It reconciles data from other systems:

• Data from your systems: file import (Excel, CSV, PDF, XML), mailbox, SFTP and the other paths listed on the How it connects page. Data is read; nothing is written to your systems.
• Rules: deterministic, with effective dates, each citing its source (tariff, contract, regulation). A rule computes the number, not an AI model.
• Provenance: every record keeps its source system, file, row, content hash, user and time.
• Evidence: every discrepancy is shown with the source rows from both sides.
• Action and verification: a case is assigned to an owner and closed only when a later check run confirms it and a person approves the result. Nothing leaves your company without the responsible person's approval.

The full catalogue of checks is on What Outturn checks; the running application on synthetic data is in the product tour.

Where Outturn fits: what it does and does not do

Outturn is not a PMIS, PCS, TOS, VTS or ERP, it is not a certified eFTI platform, and it replaces none of your systems. It works on top of existing systems: it compares their data, finds a financial or operational discrepancy, proves it, creates an action and verifies the result.

You can start with one concrete question, the free 5-day rail billing check: you send up to three months of carrier statements and your wagon records, and within 5 working days you receive a written report by e-mail. Link to the full solution description.

What to ask before choosing or connecting port systems

These are our recommendations, not statements from the sources:

• Does the system let you export event times (arrival, placement, release, removal) with time zone, not just the current view?
• Which time is the "source of truth" for each charge, and is it recorded in the same system where the charge is calculated?
• Who is responsible for data correctness when it travels from one system to another (see clauses 20 and 24 of the KIPIS terms)?
• Are tariffs and tolerances stored with an effective date and a source, or typed in by hand?
• Is there an independent check that does not depend on the system it checks?