Project

General

Profile

Actions

Task #71

open
SG

Task #1: Product Improvement

Task #3: ULIP application/Integration

9. ACMES Cargo Verification Framework

Task #71: 9. ACMES Cargo Verification Framework

Added by Srishti Ghosh about 1 month ago. Updated 18 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
Start date:
07/24/2026
Due date:
% Done:

100%

Estimated time:
8:00 h

Description

User Story
As a Canofy user, I want to verify export and import air-cargo shipments through the ACMES service so that I can retrieve shipment information using AWB or HAWB references.

Description
Implement the ACMES cargo verification module within the Canofy ULIP integration application.
The module integrates the ACMES service through the common cargo verification framework and supports export/import shipment searches using AWB and HAWB numbers.
The current implementation uses simulated ULIP responses to validate the complete integration workflow, including request handling, response processing, shipment information display and error handling.
The module supports retrieval of shipment information such as AWB, HAWB, shipment status, origin, destination, flight number, airline, shipment date and last updated timestamp.

Configuration / Prerequisites
Common cargo verification framework completed.
ULIP client/service layer configured.
ACMES service method implemented.
Import/export selection available.
AWB and HAWB search options available.
Mock ACMES responses configured for success, failure and server-error scenarios.

Acceptance Criteria
User can select Export or Import cargo.
User can search for a shipment using a supported AWB number.
User can search using a supported HAWB number where applicable.
A successful ACMES response is processed and displayed correctly.
The shipment result displays relevant information including:
AWB Number
HAWB Number
Shipment Status
Origin
Destination
Flight Number
Airline
Shipment Date
Last Updated
Invalid shipment references produce a clear "No shipment found" response.
ACMES service/server errors are handled without crashing the application.
The module follows the common cargo verification workflow and does not require separate UI architecture.
The mock implementation can be replaced with the actual ACMES ULIP API once government approval and API credentials/access are provided.

Test Cases
TC01 – Export AWB Verification
Select Export → AWB and enter:
123-45678901
Expected Result:
ACMES returns the simulated export shipment with status In Transit, Bengaluru as origin and London Heathrow as destination.

TC02 – Import AWB Verification
Select Import → AWB and enter:
098-76543210
Expected Result:
The import shipment is retrieved successfully with status Customs Clearance, Dubai as origin and Bengaluru as destination.

TC03 – HAWB Verification
Select HAWB search and enter:
HAWB-EX-45821
Expected Result:
The associated export shipment is retrieved successfully and the corresponding AWB and HAWB information is displayed.

TC04 – Shipment Not Found
Enter:
000-00000000
Expected Result:
The application displays an appropriate No shipment found message and remains usable.

TC05 – ACMES Server Error
Enter:
ERROR500
Expected Result:
The simulated ACMES service exception is handled gracefully and an appropriate service-unavailable/error message is displayed.

Actions

Also available in: PDF Atom