Choosing port operations management software starts with the work your port needs to coordinate. For a Harbour Master replacing an ageing system or a collection of spreadsheets and separate applications, the important question is how information will move between teams when the vessel schedule changes.
A Port Management Information System (PMIS) connects the operational information behind vessel visits and port services. The term “port management system” is also used, but the scope varies by supplier. Some ports need berth planning, some need marine services planning, and others need both within a wider PMIS implementation.
This checklist helps you define that scope, test a supplier’s solution against a realistic port call and prepare for the people and process changes involved.
1. Start with your port’s responsibilities
Write down which activities your port manages directly and which belong to agents, terminal operators or marine service providers. Then identify where teams re-enter information, wait for confirmation or work from different versions of the schedule.
For example, a port that allocates berths but does not operate pilotage or towage needs a different solution from one that schedules the berth, pilot, tugs and transfers. A wider PMIS project may also need to connect bookings, movement records and charges across operations and finance.
Separate what is needed for the first rollout from later requirements. Ask each supplier to identify the modules, interfaces and configuration included in its proposal. This makes the comparison more useful than a long list of features marked “available”.
2. Follow a vessel visit from order to billing
Use one representative vessel visit to test the handoffs between teams. The following is an evaluation framework: responsibilities and approval routes will vary by port and service provider.
Stage | Confirm who is responsible | Ask the supplier to demonstrate |
|---|---|---|
Request or order | Agent, customer or internal operations team | How vessel, visit and service requirements are captured, and how an amendment is recorded. |
Review and approval | The authorised port or service-provider team | Who can approve the request, what happens when information is incomplete and how the requester sees its status. |
Berth and marine services planning | Berth and nautical-service planners, where applicable | How the proposed movement fits the berth window, vessel constraints and required resources. |
Dispatch and execution | Coordinators, pilots, tug crews and supporting teams | How assignments reach the people doing the work and how progress returns to planning. |
Completed-service records | Operations staff responsible for confirming the work | Which actual activities and timestamps are retained, and how corrections are controlled. |
Billing | Finance and authorised operational reviewers | How recorded services support charges under configured tariffs and billing rules, including exceptions requiring review. |
A demonstration of this complete sequence is more informative than separate screens for each department. In marineM PMIS, vessel bookings, movement coordination and billing form part of the connected operational workflow. The precise module and interface scope should be agreed for your port.
3. Change the ETA during the demonstration
A workable plan must account for the resources needed to move a vessel. A free berth alone does not establish that the movement can take place.
Use an illustrative scenario: a vessel expected at 14:00 is now due at 16:00. Ask the supplier to show what needs to be reconsidered, rather than simply moving a bar on a timeline.
Is the berth still available, and do the applicable tidal and air-draft constraints permit the movement?
Is a pilot with the appropriate licence and class available within the required rest rules?
Are suitable tugs available, including the required bollard pull and any repositioning time?
Can pilot boats, vehicle transfers, mooring teams and line boats support the revised time where needed?
Which alternatives can the planner compare, accept or adjust?
Marine Services Planner generates assignment plans around the required vessel time at the jetty or SPM. Planners can accept recommendations or make manual overrides. When used with Berth Planner, the aim is to consider vessel space and nautical-service readiness together.
For a practical explanation of that dependency, see what happens when a berth plan changes. If your port handles SPM or ship-to-ship operations, include those workflows in the demonstration and confirm the roles, resource requirements and rules that must be configured.
4. Make the module and interface boundaries clear
The names of software modules do not tell you everything about their scope. Ask the supplier to map each requirement to a product capability, configuration task or interface.
Within the marineM Maritime Operations Platform:
PMIS connects information across vessel visits, port movements and billing.
Berth Planner addresses berth allocation and scheduling; Marine Services Planner coordinates nautical resources and their supporting logistics.
PilotCommand includes add-on modules for Pilotage Orders and Billing that work with Marine Services Planner, connecting order and approval workflows with planning, dispatch, execution and billing.
TugCommand includes add-on modules for Towage Orders and Billing that work with Marine Services Planner across the equivalent towage workflow.
Port Community System modules support community-facing activities such as vessel registration, service requests, approvals, documents and status communication.
For interfaces with terminal operating systems, finance applications or stakeholder systems, agree what information is exchanged, which system owns each record and how errors or changes are handled. Do not assume that a PMIS replaces a terminal operating system, a customs platform or every application used by the port community.
For a comparison of system responsibilities, read our guide to PMIS, PCS, terminal and port agency software scope.
5. Evaluate implementation and the supplier’s support
Changing a PMIS affects more than the planning desk. Operations, finance and external participants may all need to change how they submit, approve or use information.
Ask how the supplier will help you map the future workflow before deployment. Process workshops, role-based training, local champions and phased rollout should be discussed alongside data preparation and software configuration. For multiple locations, confirm which processes are shared and which need local variation.
Request references relevant to your operational scope. A berth-only implementation and a project covering marine services, external requests and finance are different undertakings. Ask what users were trained to do, how the rollout was supported and how readiness was assessed.
Agree acceptance criteria, responsibilities and support arrangements before the project starts. Include access controls, backup and recovery arrangements, incident handling, interface support and the process for requesting changes. These are matters to verify in the proposed solution and contract, rather than capabilities to infer from the word “cloud” or “AI”.
6. Compare total cost and establish a baseline
Compare the cost of delivering the same agreed scope. Include licences or subscriptions, implementation, data preparation, interfaces, training, equipment where needed, support and future changes. Make assumptions about users, locations and transaction volumes visible in each proposal.
Define how you will evaluate operational results before rollout. Useful measures may include vessel turnaround time, waiting time, calls handled, tug fuel use and pilot productivity. Agree the definitions, reporting periods and data sources, and record factors such as traffic mix and resource availability that affect comparisons.
Where a reliable before-implementation baseline is unavailable, establish one rather than claiming a saving that cannot be demonstrated. The port KPI guide provides a starting point for selecting and defining measures.
7. Bring these questions to the supplier demonstration
Can you follow one vessel visit through its orders, approvals, plan, dispatch, completed services and billing?
What happens when its ETA or berth changes after services have been assigned?
How are pilot qualifications, rest requirements, tug capability and transfer logistics considered?
Which recommendations can planners review or override, and how do changes reach the affected teams?
Which requirements are included, which need add-on modules and which depend on interfaces or configuration?
How will agents, customers and service providers participate in the agreed workflow?
What data, training, local ownership and acceptance checks are needed for rollout?
How will we measure results and support the operation after go-live?
Choose port software by testing how it supports your operation, including the exceptions and changes that occur during a working day. A clear scope, a realistic demonstration and an agreed implementation plan give the Harbour Master a stronger basis for the decision.
Request a marineM PMIS demonstration to review your vessel-visit workflows, planning requirements and implementation priorities.