The frequency of automatic runs is scheduled using the Manifest run schedule set in InfoWorks ICM Ultimate or ICMLive Configuration Manager.
Full runs can also be scheduled to occur more frequently in the case of an event occurring that raises an alert. The scheduling of variant simulations or 'child' runs can also be triggered by an alert.
The status of the Alert Trigger can be viewed in the Server Simulation Schedule Window. Alert Trigger status may be one of the following:
Once the schedule has been triggered, it will continue to be used, even if alerts stop occurring.
If the user has appropriate permissions, the alert trigger can be manually reset or changed in the Server Simulation Schedule Window or from the Manifest toolbar.
Simulations of a 'child' manifest may be triggered by the occurrence of an event in a run from a 'parent' manifest.
The intended use of this functionality is that runs in the parent manifest will be scheduled to run more frequently than the child manifest runs. Runs from the child manifest will initially be at a low frequency and will be used to generate initial state information. When an event occurs in the parent run that raises an alert, the triggered full run frequency in the child manifest schedule will be initiated scheduling the child manifest runs at a higher frequency.
For example, a parent manifest containing a 1D model could be used to trigger a higher run frequency for a child manifest containing a more detailed 2D model of the same area in the event of a flooding alert.
The Parent-child manifest relationship is set up in the Manifest object in InfoWorks ICM Ultimate or ICMLive Configuration Manager.