01 / The context
The problem behind the project.
Freight operations cross organizational and technical boundaries. Messages, manifests, scanner data, and task state had to travel between systems with different protocols and data models.
02 / The contribution
How I approached it.
- Built customs-messaging web services with a Windows Service receiving messages from IBM WebSphere queues.
- Modeled hierarchical task lifecycles and dependencies with recursive CTEs and SQL Server PIVOT.
- Built rich task and import interfaces, preserving grid position while refreshing collections in place.
- Extended the later generation with AMS batch handling, air-manifest XML parsing, scanner integration, and an interface Web API.
03 / The result
What the work made possible.
Delivered logistics and customs components across two technology generations, connecting operational workflows to external messaging and hardware-facing systems.
2technology generations
AMS + XMLcustoms and manifest data
Web APIhardware-facing integration

