× Search

The Simcad^® Engine · 30 years of refinement

The engine that carries your model all the way to the live floor.

Most simulation tools were built to run a model and export a report. Simcad^® was built to run your operation — at simulation speed today, on the live floor tomorrow. The same patented 64-bit engine that powers a warehouse layout study powers real-time orchestration in Stage 4. That's not a product roadmap. That's how the architecture was designed 30 years ago, and why the model you build today doesn't have to be rebuilt when you're ready for more.

Talk to our team →

30+ years of
continuous refinement

1 continuous
codebase, four stages

64-bit multi-threaded
architecture

2 native AI engines
built in

Patented engine, connectivity
& analytics IP

The problem with legacy tools

Legacy DES engines were designed for the run, not the operation.

Discrete-event simulation has been around for decades. The leading tools are mature, capable, and well understood — and they stop at the simulation run. They're single-threaded or 32-bit, built before enterprise data scale was a real engineering problem. They have no native AI, no built-in database engine, no productized connectors to the live control stack. Integrating live data is custom code, per project. When you're ready to connect the actual WMS or monitor the floor in real time, you're starting over.

The model you spent months building doesn't carry forward. That's a tool constraint, not a physics problem.

The Simcad^® difference

One engine. Every stage of the twin.

Simcad^® is a 64-bit, multi-threaded engine with two AI engines, a built-in database layer, and patented native connectivity to WMS, ERP, SCADA, PLCs, and real-time location systems — all shipping in the same product used to run a warehouse simulation study. The architecture was built for operational continuity from the start: the same engine runs in simulation time and in real time, and the model you build in Stage 1 is the foundation of every stage that follows.

You're not buying a simulation tool with a live-data bolt-on. You're building on an engine designed for the full spectrum.

Under the hood

What the Simcad^® engine ships with — and what most don't.

These aren't roadmap items or partner integrations. Every capability in the Simcad^® column is productized, shipping today, and consistent across all four stages of Digital Twin Studio^®.

Capability	Simcad^® engine	Typical legacy engine
Architecture	64-bit, multi-threaded simulation and optimization engine built for enterprise-scale data.	Often single-threaded or 32-bit. Older address space limits performance at enterprise data volume.
AI engines	Two AI engines built natively into the platform — not a plugin, not an add-on.	No native AI. Reinforcement learning possible in some tools via custom Python scripting.
Neural network support	Native neural-network–driven optimization — runs within the simulation engine, not externally.	Not supported natively. External machine-learning integration is bespoke engineering per project.
Database engine	Built-in database engine with native, unlimited external database connectivity — no coding required.	No built-in database. External data connectivity requires custom code per project.
Out-of-the-box connectors	JSON, REST, ModBus, PLC, RFID — productized and configurable without engineering work per deployment.	None native. All integrations are bespoke code built for each project, owned by the project team.
Modeling language	Low-code, VB-like language with an AI Companion that auto-builds models from your operational data.	C++, C#, or Java — coding-heavy for anything non-trivial. Requires simulation specialists, not operations teams.
Runtime mode	Runs in real-time or simulation time on the same engine — no architectural change, no migration.	Simulation time only. Real-time operation requires a different product, a different data layer, or both.
Data scale	Unlimited dataset size — engineered from the ground up for enterprise-scale live operational models.	Constrained by 32-bit address space in older tools. Large SKU catalogs and live data volumes can exceed limits.
Dynamic modification	Modify the model while it is running — no stop, change, restart cycle. Continuous operational flow.	Stop the simulation, make changes, restart. Every modification interrupts the run and resets the clock.
Model evolution	Continuous, automated model evolution as operational data changes — models stay current without manual refresh cycles.	Manual maintenance and periodic rebuilds. Models drift from reality between refresh cycles.
IP status	Patented engine. 30+ years of refinement in one continuous codebase. Not a fork. Not open-source roots.	Largely open-source roots or academic lineage. No comparable engine-level patent estate.

Built-in, not bolted on

What the engine ships with for operators.

Most simulation tools require a separate BI layer to make results usable for operations teams. Simcad^® ships with these natively — built into the model, accessible to the people making the decisions.

Warehouse visual analysis

Heatmaps, spaghetti diagrams, congestion maps, and storage density — generated from your simulation run, not exported to a separate BI tool. See where the operation breaks before it does.

Inventory classification

Automatic ABC and XYZ (demand variability) classification computed across every SKU and item in the model. Item-level traceability included — no additional analysis required.

Predictive alerting

Built-in alerter module surfaces elevated alerts before predicted events occur — not just a report of what happened. Pairs with the AI engines to surface leading indicators, not just lagging ones.

Integrated dashboarding

In-model dashboards with drag-and-drop layout and role-based permissions — across SQL, Oracle, and external data sources. Web-based dashboarding expands in the live-data tiers of the platform.

Prebuilt module library

Large library of warehouse and manufacturing modules — conveyance, sortation, picking systems, AGV fleets, ASRS, and more. User-customizable and refreshed quarterly. Build faster; spend time on decisions, not modeling primitives.

AI Companion modeling

The AI Companion auto-builds models from your operational data — order history, inventory records, pick patterns. Operations teams and industrial engineers can build and modify models without a simulation coding background.

One model. Four stages.

The simulation you build today is the twin you run tomorrow.

Most digital twin programs stall because the platform decision was made too early — a simulation tool that can't connect to the live floor, or a monitoring platform that can't run what-ifs. The Simcad^® engine is the reason Digital Twin Studio^® doesn't have that problem.

The model you build in Stage 1 is the same model that can connect to live data in Stage 3 and receive prescriptive recommendations in Stage 4. You're not rebuilding. You're extending. The engine was designed to carry the model forward — because 30 years ago, that was the architectural bet CreateASoft made, and it's what the platform is built on today.

S1

Simulation — Simcad^®

Offline what-if. Layout design, slotting, automation sizing, capacity planning — on your real order data. The model is built here. This is where the Simcad^® engine is doing its primary job: behavioral simulation at data-driven fidelity.
S2

Emulation — Digital Twin Studio^® Desktop

The same model, extended. Your actual WMS, WCS, or PLC code runs in the loop — one-to-one fidelity with the real control stack. Go-live readiness validated before a single line of control code touches the live floor.
S3

Real-Time Monitoring — Digital Twin Studio^® Live

The twin wires to the live floor via patented smaRTLS® — RFID, GPS, RTLS, NFC. Plan vs. actual, every shift. The simulation model is now a live mirror of the operation.
S4

Real-Time Orchestration — Digital Twin Studio^® Intelligence

Regenerative AI on live operational data. Predictive forecasting, dynamic alerts, prescriptive recommendations — the twin is no longer just a mirror. It's driving decisions.

Want to see the engine in your operation?

The fastest way to understand what the Simcad^® engine can do for your program is to see it on a model that looks like yours. Tell us about the operation, and we'll show you what the simulation — and the path forward from it — actually looks like.

Talk to our team → See Simcad^® in action →