User Acceptance Testing for MNSW Begins

User Acceptance Testing (UAT) for the Maldives National Single Window (MNSW) project began last week.

The Maldives National Single Window (MNSW) Project is a centralised digital platform designed to streamline international trade by enabling trade and transport parties to submit standard information and documents through a single entry point.

A key component of adopting this new system is UAT sessions. It is the final stage of software testing where real users check if the system works as expected and meets their needs before it is officially launched.

The MNSW UAT is aimed at the various cross-border regulatory authorities (CBRAs) of the Maldives along with key stakeholders in international trade such as shipping agents, freight forwarders, and traders.

A CBRA is a government agency responsible for overseeing and regulating the import and export of goods or products across the borders of our nation. These can include agencies such as Maldives Customs Service, Maldives Ports Limited, the Ministry of Defence, and so on. 

Cycle 1 of the UAT will occur from July 21 to August 11, followed by Cycle 2 from August 11 to August 15. Cycle 3 will be conducted off-site from August 18 to August 22.

Let’s go over a brief overview of the schedule for the UAT, taking a look at the target audience, timings, and what will be covered each day. 

For more details about the discussed topics and target groups, please consult the shared document.

Schedule for Cycle 1

Day 1 & 2 (21 - 22 July 2024)

These two days primarily focused on orientation, covering session overviews, goals, training schedules, participant roles, testing scenarios and execution instructions, preparation resources, and addressing participant questions, concerns, and input.

Day 3 (23 July 2024)

The third day of sessions included online modules for integration readiness across all endpoints, while the offline modules cover essential system components such as portal and dashboard configuration, as well as system configuration parameters and code maintenance.

Day 4 (24 July 2024)

On Day 4, the team focused on various aspects of registration, including registration itself, self-registration (with and without log in), role registration, user registration, and party registration approval.

Day 5 (25 July 2024)

Day 5 further explored different aspects of registration, including registration itself, self-registration (both with and without log in), role registration, user registration, and party registration approval.

Day 6 (28 July 2024)

On Day 6, both sessions covered topics including vessel management, vessel registration, amending vessel registration, applying for vessel registration, vessel termination, vessel registration approval, vessel assignment approval, searching for vessel agent assignment requests, and vessel registration amendment approval.

Day 7 (29 July 2024)

On Day 7, both sessions covered topics such as arrival reports, creating and searching ETA, creating and searching CDR, creating and searching Actual Arrival, creating and searching ADR, and approving ETA.

Day 8 (30 July 2024)

On Day 8, both sessions focused on various aspects of document management. Topics included document administration, document field configuration, creating and searching documents, and the CBRA Clearance Matrix. 

Additionally, sessions covered defining and searching the Clearance Matrix, as well as decision tree searches.

Day 9 & 10 (31 July, 01 August 2024)

On Day 8, both sessions addressed a range of topics. These include internal product management — such as creating, searching, and blocking internal products, and handling UCRs, including creation, child UCRs, and amendments. 

Additionally, the sessions covered application submissions, including submitting and amending consignment documents, searching documents and amendments, and creating and searching cancellations and extension requests (specific to MEDT). 

The topics also encompassed queries, application approval processes, referrals, approval escalations, and searching documents.

Day 11 - 13 (04 - 06 August 2024)

On Days 11 through 13, both sessions focused on various aspects of master manifest management. Topics included creating and searching general segments and master manifests, as well as amending, updating, and approving changes to master manifests. 

Additionally, the sessions covered registering master manifests, uploading XML files, searching for registered and additional manifests, cancelling manifests, and handling auto-registration of manifests through the backend.

Day 14 & 15 (07 - 08 August 2024)

On Days 11 through 13, both sessions focused on managing house manifests. Topics included creating, searching, amending, and updating house manifests. 

Additionally, the sessions covered uploading XML files for house manifests, cancelling house manifests, and searching for both additional house manifests and amended or updated master manifests.

Day 16 & 17 (11 - 12 August 2024)

The topics covered on days 16 and 17 included various aspects of delivery orders such as creating and searching them, handling extension requests, and managing cargo discrepancies. This involved details about cargo discrepancies, including those shared between MPL and MNSW, as well as searching for discrepancy details in MNSW. 

Gate exit topics covered creating and sharing gate exit details and searching for them in MNSW.

For the Tradenet Team specifically, the sessions addressed the audit trail, report generation, and mailbox management, including individual mails and integration. Additionally, they covered the master data API from all CBRAs, template creation and search, and notification transaction searches.

Cycle 2

Day 16 - 20 (11 - 15 August 2024)

These four days are specifically allocated for retesting any test scenarios that failed previously, ensuring that all issues are thoroughly addressed and resolved.

Schedule for Cycle 3 (Conducted Off-Site)

Dates: 18 - 22 August 2024)

These dates are dedicated to offline testing, with the agenda focusing on retesting all failed test scenarios, if any, over the course of four days.

The MNSW UAT is a crucial final step before the system is launched on a limited basis to select trade stakeholders and CBRAs as part of our phase 1 rollout.

The participation and input from all participants has been outstanding, significantly enhancing the process. 

Thank you all for your valuable contributions and engagement.