PortVerse and Port Community System integration for Pakistani terminals
PortVerse is the Port Community System developed by Pakistan Single Window. A PCS connects the parties around a port so each publishes what it knows once and the community reads it, instead of every pair exchanging documents bilaterally. This page explains where the terminal sits in that picture, what it publishes, what it gets back, and what PCS integration software has to do to make it work.
A port is not one organisation. It is a dozen organisations that all hold one piece of the truth about the same box, and spend a remarkable amount of time telephoning each other to assemble it.
Each participant contributes what only it can know and consumes what others contribute. The terminal knows where the box physically is. The line knows when it releases it. Customs knows when it clears it. Nobody has to be told twice.
Terminals and off dock facilities, shipping lines and their agents, clearing agents, transporters, warehouses and the authorities. A PCS is only as good as the least reliable reporter in it.
PortVerse is the Pakistani Port Community System, developed by Pakistan Single Window, the same body delivering the national trade single window that is taking over WeBOC functions in phases.
References: the Port Community System is published at pcs.gov.pk, and Pakistan Single Window documents the phased migration of WeBOC functions at psw.gov.pk.
This confuses procurement conversations more than any other point in Pakistani port digitisation, so it is worth being blunt about it. The two systems answer different questions and a terminal needs both.
It is the connective layer. It answers the question "what does the community agree is true about this consignment right now".
It is the operation. It answers the question "what is my terminal actually doing, and what does it owe and get paid".
PCS integration is worth doing for a terminal because the traffic runs both ways. The events you publish are ones you were already reporting; the data you receive is paperwork you were already chasing.
The container or the export cargo physically entered the facility. This is the first moment the community can stop guessing where the consignment is.
The box is in a slot, and the slot is known. This is what makes examination planning and truck dispatch possible without a phone call.
For CFS cargo the container stops being the unit and the cargo inside it becomes the unit. Tally sheet and per index detail are what the consignee side actually needs.
Weighment and CBM captured at the terminal, sourced from the weighbridge rather than typed in from a slip.
Which Goods Declaration went into which container, and the service completion that follows it.
The consignment left, against a gate pass. The movement is closed and everybody downstream can act on it.
Vessel arrival with the IGM or VIR, and the indexes under it carrying BL, packages, weight, seal and line. Records the terminal would otherwise create by hand.
Instructions such as examination arrive attached to the consignment rather than as a separate instruction to be chased and transcribed.
Whether a consignment is cleared to move. The single most valuable status in the yard, and the one most often communicated informally today.
The shipping line authority to release cargo to the consignee. Arriving as data, it can gate the release automatically instead of being verified at a counter.
Notified export cargo arrival updates the loading program by itself, which is the clearest single example of integration removing work rather than adding it.
A PCS is judged by the people who are not inside the terminal. These are the questions they currently answer by telephone.
Grounding, release status and delivery order together answer whether a box is genuinely collectable. Published in real time, they stop wasted trips, which is the cost that irritates the transport side most.
For LCL consignments the tally sheet and index level detail settle short landing and damage arguments with a record, rather than with two parties recalling the same afternoon differently.
Storage and detention disputes are timestamp disputes. When gate in, grounding, release and gate out are all published as they happen, the timeline is evidence instead of an assertion.
Connecting a terminal to a community platform is mostly a data discipline project wearing a technical hat.
Decide what each terminal event means, what it must carry and which screen raises it. A community platform will amplify whatever the terminal publishes, including the mistakes.
IGM and index on the import side, GD number on the export side, container and seal number across both. Community sharing fails at the joins, and the joins are the reference numbers.
The event fires when the clerk completes the movement, not when somebody later opens a portal. Anything else produces timestamps that cannot be defended in a demurrage dispute.
Inbound data has to create and update terminal records directly. If it lands in a report that a clerk reads and re-types, the integration has added a step instead of removing one.
An integration status panel per partner, a message log, queued retries and controlled re-processing, with the duplicate risk on manual resend understood by whoever operates it.
Customs, the community platform and the shipping lines are separate channels for the same underlying events. Keeping them independent is what lets one change without disturbing the others.
STOS is the system of record for what physically happens in the terminal, and the source of the events the community depends on.
STOS raises a terminal event once from the operational screen and delivers it to the partner channels enabled for that facility, each with its own integration status panel and retry queue. Which connections are enabled depends on the terminal and is confirmed during onboarding.
The message level detail: which EDI message flows at gate in, grounding, de-stuffing, stuffing and gate out, and how failures are handled.
WeBOC integrationPSW is taking over WeBOC functions in phases. What that means for terminal reporting, parallel channels and vendor selection.
PSW integrationCargo, gate, shed and examinations, financial and analytics modules for Pakistani and international terminals, with EDI integration built in.
Explore STOSPortVerse is Pakistan’s Port Community System, developed by Pakistan Single Window. A Port Community System is a shared digital platform for the parties around a port: terminals, shipping lines, clearing agents, transporters and the authorities. Instead of every pair of parties exchanging documents bilaterally, each party publishes what it knows once and the community reads it.
A Port Community System connects parties. A terminal operating system runs a terminal. The PCS is where the community agrees what is true about a consignment; the TOS is where gate, yard, shed, examination, billing and cash actually happen. A PCS does not ground a container, produce a tally sheet, calculate storage or print a gate pass. The two are complementary, and the TOS is what feeds the community with the physical truth only the terminal holds.
The events only the terminal can know: that a container or cargo entered the gate, where it was grounded, what came out of it when it was de-stuffed and in what quantities, weights captured at the weighbridge, what was stuffed into an export container against which Goods Declaration, and when the box finally left the gate. These are the same events reported to customs, which is why the event model rather than the channel is the thing to get right.
Chiefly the paperwork it currently chases. Vessel and manifest data, declaration status, release and examination outcomes, delivery orders and transport bookings all originate elsewhere in the community. Every one of those that arrives as data instead of a phone call or an emailed PDF removes a manual record from the terminal and removes a re-keying error with it.
The practical gain is knowing the state of a consignment without calling the terminal. When gate in, grounding, de-stuffing detail, release and gate out are published as they happen, an agent can see whether a box is actually available before dispatching a truck. That only works if the terminal is reporting accurately and in real time, so the quality of the terminal operating system directly sets the quality of what an agent sees.
PCS PSW is listed among the STOS partner integrations, alongside Customs EDI, Maersk, Hapag Lloyd, CODECO and weighbridge systems. STOS generates a terminal event once from the operational screen and delivers it to the partner channels enabled for that facility, each with its own integration status panel and retry queue. The exact set enabled for a given terminal is confirmed during onboarding.
A community platform is only as good as what the terminal publishes into it. STOS is built in Karachi for Pakistani port and terminal operations, with customs and partner integration as part of the platform.