Sector templates

Four sectors, pre-loaded and ready.

One click resets the device registry, the traffic simulator's payloads, and the downtime benchmark to match your industry, real vendor names, real protocols, real dollar figures.

Manufacturing
$32,500
Downtime / hour

Siemens S7-1500, Rockwell ControlLogix, Cognex Scanner, HMI TP1200, Packaging Unit.

Water / Wastewater
$85,000
Downtime / hour

Allen-Bradley MicroLogix, Schneider M340, Endress+Hauser Flow, WinCC SCADA.

Oil & Gas
$150,000
Downtime / hour

Honeywell C300, Emerson DeltaV, ABB AC800M, Yokogawa CENTUM.

Energy / Power Grid
$250,000
Downtime / hour

GE Multilin 650, SEL-421, Siemens SICAM, ABB RTU560.


Live calculator

The exact formula SILDA runs on every blocked event.

Pick your sector and an expected monthly block volume, this uses the same 15-minute exposure-window and $500 mitigation-cost assumptions written into anomaly_detector.py.

Formula: avoided loss = sector cost × 0.25 hr exposure. Net savings = avoided loss − $500 fixed mitigation cost per event.

$0
Net savings, per month
Avoided downtime loss$0
Mitigation cost$0
Projected annual net savings$0

Illustrative, based on the product's built-in ROI model and configurable sector benchmarks in config.yaml. Actual results depend on your site's real event volume.


Deployment effort

Match the connection mode to your rollout timeline.

ModeDescriptionDeployment effort
Inline ProxyOT devices route through SILDA:8080. Full break-and-inspect on every session.Change OT gateway or DNS to point to SILDA
Reverse ProxyMES server calls SILDA instead of the cloud directly.Change one URL in MES config
Passive TAPSPAN/mirror port copy. Monitor and alert only, cannot block.Switch port mirror configuration
Bring your own numbers

We'll build a sector-specific ROI model with your real event volume.