Run an event to load the impact score.
Supply chain risk demo
Port strike in China
China electronics to US retail · Modeled scenario
- Affected part or site
- Port of Shanghai
- Time to act
- Now, before carrier and terminal cutoffs
- First action
- Identify shipments routed through Chinese gateways.
World map
Selected chain
Step 3
Scenario effects
No event has been run yet.
Select a network and disruption to show the scenario impact.
Representative modeled USD range
Generate the brief to load a modeled cost range.
This is not a customer result, forecast, or price quote.
- Source links and timestamps
- Loading scenario source Loading source record. The public demo uses modeled events.
- Reliability classification
- Loading the selected event classification.
- Confirmed versus inferred
- Loading the selected graph relationship.
- Last model update
- Loading the selected model profile.
- Assumptions
- Select a network to show its fixed operating assumptions.
- What changes confidence
- Loading confidence factors for the selected event.
Company-specific demo
Want this mapped against your actual suppliers, ports, routes, and customers?
Send your email and we will follow up to schedule a company-specific walkthrough or focused pilot scope.
Map potential disruption before it occurs.
Caracal is an operational risk intelligence software platform. It models potential disruptions against company-specific suppliers, sites, routes, systems, and customer commitments. It then monitors risk signals continuously and recommends mitigation strategies when exposure changes.
Product architecture
A finished workflow from exposure model to operating decision.
Map potential disruptions before they occur. Monitor emerging risks continuously. Act with exposure-linked mitigation strategies.
Exposure model
Structures suppliers, sites, routes, systems, materials, and customer commitments as an operating network.
Continuous monitoring
Collects and groups relevant external signals from approved public, commercial, and client sources.
Relationship and impact layer
Separates confirmed relationships from inferred ones, then scores timing, proximity, criticality, and confidence.
Decision layer
Produces exposure briefs, mitigation strategies, verification tasks, alerts, and integration events for the correct owner.
Inputs
What the platform uses.
Operating footprint
- • Supplier and site records
- • Facilities and warehouses
- • Ports, lanes, and routes
- • Systems and third-party services
Business context
- • Critical materials and SKUs
- • Lead times and inventory cover
- • Customer commitments
- • Escalation owners and thresholds
Risk evidence
- • Official authority notices
- • Weather and hazard feeds
- • Port, carrier, and infrastructure updates
- • News, research, and approved client sources
Outputs
What the operating team receives.
Integrations
Start with files. Connect when value is clear.
Start
Files
CSV, spreadsheet, and JSON intake for a focused pilot.
Connect
Business systems
Scoped connectors for ERP, TMS, procurement, supplier-risk, continuity, ticketing, and BI systems.
Deliver
Workflow endpoints
Email, webhook, JSON export, dashboard, and client-defined operating handoffs.
User workflows
One risk picture. Different operating decisions.
Supply chain
Question: Which suppliers, lanes, and orders are exposed?
Decision: Verify stock, reroute, buffer, or escalate.
Procurement
Question: Which direct or tier-2 relationship needs validation?
Decision: Contact the supplier, qualify an alternative, or revise terms.
Operations
Question: Which site, line, or customer promise can be affected?
Decision: Resequence work, activate continuity actions, or notify leaders.
Risk and compliance
Question: What is confirmed, inferred, or still uncertain?
Decision: Request evidence, start formal review, or maintain monitoring.
Evidence controls
Every material output must show its evidence and limits.
A decision brief is not complete when it shows only a score. It must show where the evidence came from, how current it is, what is confirmed, and what could change the assessment.
Source link
Direct link to the official notice, dataset, or approved source record.
Source timestamp
Publication time and the most recent time Caracal checked the source.
Reliability classification
Primary official, primary operational, established secondary, or unverified signal.
Relationship status
Confirmed, inferred, or unknown. The output does not present an inference as a fact.
Last model update
The version time for the exposure graph, rules, and scoring configuration used in the result.
Assumptions
Operating facts that the analysis uses but has not independently verified.
Confidence movement
The evidence that would raise or lower confidence in the event, relationship, timing, or impact.
Evidence record example
Port disruption signal
- Relationship:
- Confirmed lane-to-port link; inferred delay range.
- Last model update:
- Shown with the analysis result.
- Assumption:
- No usable alternate port inside the current delivery window.
- Raise confidence:
- Carrier notice, terminal closure, or verified supplier delay.
- Lower confidence:
- Confirmed alternate capacity or resolved labor action.
Deployment options
Choose the boundary before data intake.
Hosted pilot
Fast validation with a limited dataset and an agreed hosting region.
Required boundary: Data scope, retention, subprocessors, and access are documented before intake.
Dedicated VPC
For clients that need dedicated cloud boundaries and client-specific controls.
Required boundary: Identity, networking, encryption, logging, backups, and support access are designed with the client.
On premise
For high-sensitivity workloads that must stay inside the client environment.
Required boundary: The client and Caracal agree update, support, monitoring, and recovery responsibilities.