Prospective case study blueprint
Port disruption mapped to production and customer exposure.
This is not a customer result. It is a validation plan for a future pilot with a manufacturer that imports critical components through one or more exposed ports.
Operating question
Can early port and labor signals change a production decision?
The pilot tests whether Caracal can identify exposed parts, lanes, plants, and customer orders before the disruption is visible in normal shipment status.
Proposed scope
One plant, one component family, and two inbound lanes.
A narrow scope makes the result testable and keeps customer, supplier, and route data limited.
Pilot period
Six weeks of setup, monitoring, and review.
Week one maps the footprint. Weeks two to five monitor and review events. Week six measures decisions and evidence quality.
Data inputs
Minimum data for a useful test.
- Supplier site, ship-from site, and criticality for the selected component family.
- Ports, terminals, carriers, inland legs, and alternate route assumptions.
- Plant, production line, part coverage, lead time, and substitute status.
- Priority orders, delivery windows, escalation owners, and cost thresholds.
Evidence inputs
Sources that can change the assessment.
- Union, port authority, terminal, customs, and government notices.
- Carrier advisories, vessel schedules, dwell time, and congestion evidence.
- Supplier confirmations, shipment status, inventory records, and alternate capacity.
- Each source link, publication time, check time, and reliability class.
Test workflow
Five checks from signal to mitigation.
Detect
Identify an early labor, port, or congestion signal.
Verify
Classify the source and confirm the event state.
Map
Connect the port to lanes, parts, plant work, and orders.
Decide
Compare stock, delay, route, cost, and customer thresholds.
Act
Verify, reroute, reserve capacity, resequence, or notify.
Success measures
Evidence needed before publication.
Publish only after validation
Claims the case study can make.
- • Measured warning-time difference.
- • Confirmed exposure relationships.
- • Documented decisions and mitigation actions.
- • Measured alert volume and review time.
Do not publish without proof
Claims that need stronger evidence.
- • Avoided loss or downtime without a documented counterfactual.
- • Predictive accuracy without a defined test set and method.
- • Customer endorsement without written approval.
- • Security or compliance status without independent evidence.