Skip to main content

Switch Release Note Q4 2025

Updated over 3 months ago

New Feature releases

  1. Documentation DA - Internal Invoice

We have introduced internal invoice service for the Documentation DA Type, this will help us in creating billing for our other services such as PDMS.

2. Legal Entity & Trading Company selection logic at PC creation revision

Legal Entity & Trading Company selection logic at Port Call (PC) creation has been revised to reduce manual intervention and ensure consistent mappings between TMS and Switch. The system now supports linking Legal Entities (LE) to users, vessels, and trading companies, and automatically derives the correct LE/Trading Company on PC creation based on vessel and mapping rules.

Key changes include:

  • Trading Company now takes precedence over Legal Entity when enabled on the Port Call creation screen.

  • New two-way mapping between Legal Entities and Trading Companies in TMS, with visibility of linked entities on both the Trading Company and Legal Entity pages.

  • Updated selection logic to handle vessels with only LE, only Trading Company, both, or manually set combinations, including filtering of available lists based on the selected entity.

  • Many-to-many mappings are supported; in such cases the system filters options but does not prefill values, while one-to-one mappings are auto-prefilled where applicable.

These changes align DIS and UI behaviour, reduce manual selection, and provide more flexible and accurate configuration of Legal Entity and Trading Company relationships.

3. Unified Approval Workflow 1.0 (MVP)

Introduced a unified approval workflow engine for DA-Desk that standardizes existing approval processes (1/2 tier approvals, multiple owner approvals, auto-approvals, EPDA/SPDA approvals, and Camunda-based approvals). The MVP focuses on core approve/reject functionality with approval rights controlled by DA status and user groups, while still allowing users from any department to view and edit DAs (e.g. comments, cost splits, advances) without introducing department-level approval restrictions yet.

4. Resolution comment type in PDA Query stage

Added a mandatory resolution comment field at the PDA query stage, ensuring each individual query must have a resolution comment before a DA can be marked as Phase Complete and sent for approval. The system validates that all PDA queries are resolved, flags any missing comments, stores comments with user and timestamp for audit purposes, and aligns the PDA query handling with the existing FDA query resolution workflow.

5. Copy DA Details from Landing Page

Copy DA details from DA landing page to clipboard via a single button, formatting the information as:

DAD Ref / Vessel / Voyage / Country / Port / Agent / ETA / Legal Entity

so BO users can quickly paste it into emails and other documents without manual copy-paste or extra formatting.

6. Enable search by nomination types and CNA/ OPA/ ONA on the landing page

Enable operators to search port calls on the Switch landing page by Nomination Type and Owner’s Protective Agent (OPA), display the Nomination Type and Owner’s Protective Agent as configurable columns (including in file downloads), and support sorting on these fields—while removing the separate Charterer’s Nominated Agent search/column in favor of the existing Agent field.

7. Contracts Revamp

We have completely revamped the Contracts experience to support new business requirements and reduce the need to maintain multiple duplicate contracts. A single contract can now cover multiple Countries, Ports, and Agents, with an updated UI and workflows for both back-office users and Principals

The new contract has the following additional components:

  • Parent contract function (Hub agent or corporate office)

  • Sub-contract function (Agents per Port)

  • Unified expiry date for the contracts (a single email per parent contract, with no duplicate emails)

  • Vessel Group selection

  • Single Contract, Multiple Applicability: A single contract can now be tagged to multiple:

  • Countries

  • Ports

  • Agents

Back-office users see contracts based on exact applicability criteria (Country, Port, Agent, etc.).

Principals see a single consolidated contract entry even when the contract applies to multiple Countries/Ports/Agents.

Applicability-specific entries are shown per service when multiple matching applicability exist (each applicability appears as a separate radio button option).

Revamped Contracts Tab (Switch)

Search & listing

  • Improved contract search with sorting and filters.

  • Results can be exported as CSV and Excel for both contracts and their applicability.

Contract lifecycle

  • Create, update, delete, and archive contracts via the new UI.

Applicability management

  • Applicability records inherit all fields from the main contract; Agent/Supplier can be maintained independently per applicability.

  • A warning is shown when the same Agent/Supplier is selected more than once in applicability to prevent duplicates.

File management

  • Upload and download contract documents directly from the Contracts tab

Once the contract mapping task is completed by the MDM team, users will be able to view the Parent > Sub Agent mapping.

After the release, all contracts were migrated in the same format as before. The MDM team then began removing duplicates and consolidating them as sub-contracts under a single parent, as suggested by the business.

Port call Draft Integration

Contract discovery in Port call draft:

  • Contracts are listed based on exact match criteria (Port and Location).

  • Supports different port call types, including VSR.

Dynamic updates

Contract list is automatically refreshed when any of the following change:

  • Port

  • Location

  • ETA

  • Vessel

  • Agent

  • Activity

The revamp includes several usability and data-quality improvements derived from follow-up enhancement tasks:

• Mandatory main contract currency to ensure consistent financial data.

• Main Contract Agent scope expanded to include all Agents, not just parent Agents.

• Field inheritance:

  • All fields are inherited from the main contract to its applicability.

  • Agent/Supplier remains configurable per applicability.

• Duplicate protection

  • Warning indicator when the same Agent/Supplier is selected multiple times on the applicability page.

• Improved exports

  • Comma-separated Countries and Ports are now included in contract download files.

• Service filtering

  • Services are filtered based on the selected Agents on both:

  • Main contract page

  • Applicability page

User Impact

  • Cleaner view with one consolidated contract entry where applicable.

8. MCI/Profile Improvement for Husbandry

This epic delivers a set of enhancements around MCIs, annotations, and the DA Profile to make husbandry profiles more accurate, flexible, and easier to maintain across BO, TMS, Switch and related services.

Key Changes:

Richer Annotation Model for MCIs

  • Annotations per MCI

  • Introduced support for defining annotations at MCI level in TMS and DA Profile.

  • Ensures annotations are available where MCIs are configured and consumed.

Company-level vs Global annotations

  • New ability to create annotations per company or globally in TMS.

  • Allows more granular configuration where some annotations are shared and others are company‑specific.

Multi‑MCI support

  • Annotations can now be applied to Multi MCI items, improving consistency when multiple cost items are grouped.

Safer, Cleaner Annotation Data

  • Unique constraint on Annotation name + parent

  • Enforced a unique constraint on the combination of annotation name and parent, preventing accidental duplicates and improving data integrity.

  • Information bar on create annotation page

  • Added an information bar on the annotation creation page to guide users on correct usage and constraints.

DA Profile Model & Search Improvements

  • Enhanced DA Profile model

  • Expanded the DA Profile model to better represent MCIs and their annotations, supporting new husbandry scenarios.

Partial search for BO

Implemented partial search capabilities for BO around MCIs/annotations, making it easier to find relevant items without exact matches.

Workflow & UI Changes in BO, TMS and Switch

  • Handling annotations in Add / Split / Relabel / Reallocate flows

  • Updated BO, TMS and Switch (EDGE) flows so that Add, Split, Relabel and Reallocate operations correctly handle annotations, preserving and updating them as MCIs are modified.

Cost Item profile updates for annotations

  • Adjusted the Cost Item profile screens in TMS to accommodate both company-level and MCI-level annotations, ensuring the configuration is visible and manageable from one place.

9. Payments Tab Enhance Status Names

Payments tab for PP customers has been updated to correctly reflect payments settled directly by operators or agents.

What’s changed:

  • Payments that are approved and paid, whether via PPL or operator, now consistently show status “Payment approved, paid”.

  • When a payment is settled manually by an operator, the “Payment Processed” column now displays “Settled by Operator”.

  • Existing behaviour for payments settled through PPL remains unchanged (document generated as today).

  • The update applies to all DA types (SDA, VI, ADR, APR, PSDA, PDA, etc.), improving transparency for users reviewing payment status.

Did this answer your question?