Trigger a simulation run

Select an option below to trigger a simulation run.

• Manually: Initiate a simulation run by selecting ▶ on a simulator routine.

• Scheduled: Set a schedule for the simulation routine. The associated connector automatically initiates the simulation based on this predefined schedule.

• Programmatically: Use the Simulators API to start a simulation programmatically. You can override a series of parameters:

  • Run-time: The timestamp when the simulation should take place. The default value is the current timestamp.
  • Model Revision External Id: An identifier for the model revision to use. The default value is the latest revision.
  • Routine Revision External Id: An identifier for the routine revision to use. The default value is the latest revision.
  • Inputs: A list of inputs to override. You can dynamically change input values, both constant and time series, on each run. The constant, sampled and overridden inputs are stored in the simulation data associated with the simulation run and then fed into the simulation model. The simulation is executed according to the routine's script.

When the simulation is complete, the output values are saved in the simulation data associated with the simulation run. For numeric scalar outputs, data can also optionally be saved in time series. The results are associated with the simulation time timestamp.

Best practices for simulation runs

• Keep your simulation models up-to-date to ensure they accurately reflect the current state of your assets.
• Balance the frequency of simulation runs with system resources. More frequent runs provide more up-to-date results but require more computational power and in some cases more license usage.
• Use data validation methods to ensure input data quality.
• Use the versioning capabilities for models and routines to track changes over time.
• If you have multiple routines, distribute them across different connectors to balance the load and avoid dropping simulations due to connector timeouts.