Before · fragmented operations
Every handoff resets the search.
- 01Carrier portal holds one status.
- 02Email holds the exception context.
- 03Spreadsheet holds the customer promise.
- 04Operations reconciles them manually.
Enterprise logistics platform that unified fragmented operations into one real-time shipment record, with carrier and warehouse events normalized across every handoff and exception.
Evidence boundary: this public case study demonstrates the architecture and workflow. It does not assert performance outcomes without published baselines.
Project architecture summary
Demonstrated capabilities from the case study. Mock dashboard values are illustrative and are not project results.
The operating shift
The interface concept turns fragmented updates into a shared event trail. Operations sees what moved, what changed, and what needs intervention without chasing carrier portals or status messages.
Before · fragmented operations
After · unified event record
Interactive product concept
A redesigned demo dashboard · fixed synthetic dataset · no account connection
Synthetic event stream · Updated Aug 13, 2026 14:32 PHT
| Reference | Lane | Mode | Status | Progress | ETA / Actual | Delta |
|---|---|---|---|---|---|---|
| Manila → Cebu | Sea | In transit | 72% | Aug 14 · 16:30 | On time | |
| Shenzhen → Manila | Sea | Exception | 48% | Aug 15 · 11:00 | +9h | |
| Davao → Cagayan de Oro | Road | Out for delivery | 89% | Aug 13 · 18:40 | +1h | |
| Singapore → Manila | Air | Arrived hub | 64% | Aug 14 · 09:15 | On time | |
| Cebu → Iloilo | Sea | Watch | 32% | Aug 15 · 14:20 | +4h | |
| Manila → Batangas | Road | Delivered | 100% | Aug 13 · 10:12 | -1h | |
| Hong Kong → Clark | Air | Linehaul | 56% | Aug 14 · 05:50 | +2h | |
| General Santos → Manila | Sea | Port loading | 18% | Aug 17 · 20:00 | On time | |
| Subic → Laguna | Road | Exception | 41% | Aug 14 · 19:30 | +13h | |
| Bangkok → Cebu | Air | At origin | 12% | Aug 15 · 07:30 | On time |
Selected PMJ-24081, synthetic shipment from Manila to Cebu. In transit with 72% progress.
Signal architecture
A conceptual view of how the published stack can turn source events into an operations-ready interface. This diagram demonstrates product logic, not production architecture verification.
Scans, milestones, proofs, and exception updates enter the record.
API · EDI · WEBHOOKInputs are validated and normalized into one event language.
NODE.JS · TYPESCRIPTCurrent state and event history stay joined to one reference.
POSTGRESQLOperational changes reach connected views without a manual refresh loop.
REDIS · WEBSOCKETSRoutine movement stays quiet; delayed handoffs move to the top.
REACTPublished technology stack
The stack below is retained exactly from the live project page. The role descriptions explain the redesign concept and should not be read as audited implementation details.
Operations interface and shipment inspection views.
Typed event contracts across interface and services.
Service layer for ingestion and integrations.
Shipment state, history, and relational records.
Fast access to operational state and event coordination.
Connected status updates across the control tower.