Background: CargoSignal provides GPS trackers that are placed within our shipping containers (from Factory to DC).
This is an existing practice.
Currently, this is only done in North America coming from certain key factories, but will expand.
The Tracker is used as a mitigation against theft.
Infor Nexus is our supply chain tool for tracking Trade shipments, and they have a feature that can consume the Tracker information & post it to our existing Shipment.
Pre-scoping was reviewed in February. Progress was put on hold till this formal request
Problem Statement: The bulk of shipment tracking is done via Nexus UI & Reporting, but these Sensor data elements are tracked offline/manually, causing redundancy & hours of manual efforts by the inbound shipping team. The manual process was initiated 6 months ago, and it is expected to grow, which becomes unsustainable.
Use Case:
Decrease manual data tracking
Increase data accuracy
Create a single, digital source-of-truth for shipment tracking.
Note: This is not a revenue driver, but will reduce man-hours.
Andy Clark is the primary requestor on this enhancement, and I am acting as his medium.
Outcome | 1) Decrease manual data tracking 2) Increase data accuracy 3) Create a single, digital source-of-truth for shipment tracking. |
Objective Alignment | Data Driven Product Journey, Build the Future Platform, Delivery Excellence |
Region | NORTH AMERICA |
Compliance | No |
Value - Revenue/Savings | $22,002 |
Is a Project Manager Required | No |
Further discussion is being had on ROI. Currently no budget in digital and data. But can be considered in Budgets for 2027. We need to emphasis on the inventory transparency gain as a part of building a global control tower for inventory.
Per Fio:
Current State
Market Dynamics:
- From port discharge to destination average transit with dwell is ~14 days. Domestic in transit status visibility is limited
- Rail dwell varies even during nonpeak. On average 10-20% of inbound exceed average inland transit
Deckers Impact:
- Internal partners (Customer Experience, Planning, Logistics, DC’s) all work out of Nexus, when data is unavailable, emails/Teams exchanges increase
- Device visibility lives in Cargo Signal platform. Logistics has to run data from Nexus and match to manual spreadsheets to summarize to internal partners
Future State
Market Dynamics (no change):
- From port discharge to destination average transit with dwell is ~14 days. Domestic in transit status visibility is limited
- Rail dwell varies even during nonpeak. On average 10-20% of inbound exceed average inland transit
Deckers Impact (ROI):
- Internal partners (Customer Experience, Planning, Logistics, DC’s) all work with Nexus data. Cargo Signal integration would allow for all parties to access under one platform
- No separate tracking, reporting and emails needed to obtain status and provide updates
Avg time spent weekly:
1) Analysts data entry efforts marking containers with tracking devices: 2 hr
2) Origin team support tracking manually in excel: 2 hr
2) Logistics Coordinators/Analysts following up with forwarders on inbound containers due to missing rail visibility: 3 hr
3) Analysts summarizing data to business partners or updating internal logs: 2 hr
4) Analyst/manager involvement in researching gaps in data: 2 hr
5) Analysts double checking for proper billing auditing: 0.5 hr
6) DC Labor optimization efforts (when ETA changes due to missing visibility): 2 hr
Total: 13.5 hrs per week ($40/hr)*52 =$28,080/yr