A continuous execution engine designed to maintain system state, support live input changes, and operate without predefined execution boundaries.
Traditional simulation engines execute predefined studies: inputs are set, calculations are run, results are produced, and execution ends. The runtime simulation engine operates differently.
Execution persists.
System state is maintained.
Changes occur within the running system.
This allows simulations to evolve in real time as conditions change, without restarting or reinitializing the model.
The runtime simulation engine operates within the broader platform architecture that defines how simulation systems are structured and applied.
The engine maintains an internal representation of system state throughout execution.
This state:
By preserving state, the engine supports scenarios where how the system arrived at a condition is as important as the condition itself.
The runtime engine is designed to accept input changes while the simulation is running. These inputs are incorporated into the active execution context rather than triggering a reset or new study.
This supports:
Inputs modify behavior, not execution structure.
Despite supporting live input changes and concurrent contexts, the engine is designed for deterministic behavior. Given the same state and inputs, execution follows the same path.
This predictability is essential for:
Determinism is a structural property, not a tuning parameter.
Maintaining deterministic behavior under concurrent execution depends on a compute architecture that aligns execution flow with system structure.
The runtime simulation engine operates independently of user interface, visualization, or delivery mechanism. Interfaces interact with the engine, but do not define its behavior.
This separation ensures that:
Training, operations, or simulation architecture—start with a focused discussion on requirements and deployment context.