01
Scope
Choose the pilot footprint, risk categories, regions, and operating owners.
Pilot scope
Prove operational value on a focused footprint.
A Caracal pilot should start narrow: one geography, product line, supplier group, market, or logistics lane. The goal is to test whether external signals can become useful exposure-linked actions for your team.
Pilot path
A focused pilot is meant to answer practical operating questions.
The process can be adapted to procurement and data requirements, but the structure should stay narrow enough to produce clear signal quality and value feedback.
02
Map
Create a lightweight exposure map from supplier, site, route, customer, or dependency data.
03
Monitor
Configure the focused risk areas and assumptions for the pilot.
04
Review
Assess alert relevance, false positives, actions generated, and production path.
Data inputs
Start with data your team can actually provide.
CSV or spreadsheet data is enough for an initial pilot. The first version should expose data gaps instead of hiding them.
Supplier list
Supplier names, sites, countries, criticality, and any tier or product assumptions.
Facility/site list
Factories, warehouses, offices, cloud regions, service regions, or other operating nodes.
Port/lane list
Ports, borders, routes, corridors, and logistics modes tied to priority operations.
Customer or market list
Priority customers, destination markets, delivery commitments, or escalation thresholds.
Pilot deliverables
What your team should receive.
Focused exposure map for the selected footprint.
Focused risk brief examples.
Sample alerts and operational impact briefs.
Scenario analysis with recommended actions.
Executive pilot summary and open assumptions.
Production handoff plan and integration recommendations.