Model your supply network. Optimize it. Prove it.

Who designed this supply chain?

For most companies the honest answer is: no one — it accreted. ERP, TMS and planning systems run the network you have efficiently. None of them tell you whether it's the right network. Design sets the ceiling on cost, service, and risk — and tariff and trade-policy shifts are moving that ceiling under everyone's feet right now.

Build, optimize, prove

1. Build. Lay out your network as a click-connect graph — suppliers, plants, DCs, customers, lanes. The model is the database; no double-entry, no drift.
2. Optimize. Solve for the best sourcing and footprint — facility location, flow paths, landed cost, capacity and site-count constraints.
3. Prove. Simulate the optimized design on the same model — variability, lead times, stockouts — so you know it holds before you act.

Most tools stop at optimize. The proof is the point.

One platform. The tools share one model.

SCModeling isn't a toolkit you assemble. These are its parts — and the whole point is that they work on the same model.

• The model. Your network as an editable graph. The model is the database — no import/export, no second copy to drift.
• AMOS — the optimizer. Facility location, sourcing, flow paths, landed cost, capacity and site-count constraints. The class of optimization the largest network studies have always used — now headless and fast.
• Supply Chain Builder — the simulator. Runs the optimized design as a discrete-event simulation on the same model, so you watch it survive reality before you commit. SDI built and sold Supply Chain Builder for years.
• + The agent. Ask in plain language — "re-source under a 25% duty and show me what breaks." Scriptable and agent-ready, not a click-through.

Why SCModeling

The proof step others skip

Optimize and validate, one model, no hand-off, no re-modeling. Optimization tells you what the network should be; simulation proves it survives reality.

Your model never leaves your machine

SCModeling is a desktop tool. Sites, costs, contracts, margins, sourcing strategy — your most sensitive data stays local. The category went to the cloud; for network and tariff work, local-first isn't a preference, it's the requirement.

Consultant-grade method, built in

Decades of network-design practice — data validation, base-case calibration, scenario analysis — productized, not improvised.

The tariff door is open now

Tariffs are just another cost in the model. Re-optimize sourcing and footprint under the new duty rates, then simulate the redesign — so you commit capital to a network that survives reality, not a spreadsheet's best guess. You don't need a tariff dashboard. You need to redesign the network, and prove it before you move a plant.

Stop inheriting your supply chain. Design it.

Bring your network. We'll show you a better one — and prove it before you bet on it.

Talk to us