Alert Triggered Runs

The frequency of automatic runs is scheduled using the Manifest run schedule.

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.

To specify the alert that will cause a run schedule to be triggered, select an Alert Definition List in the Manifest Setup page and select the alert name from the relevant trigger field in the Run schedule.

The following triggers can be specified:

• Full run trigger - when full run trigger alert occurs suspend full run and observed run frequency intervals. Run full runs at Triggered full run frequency.
• Variant run trigger - when variant run trigger alert occurs, suspend full run and observed run frequency intervals. Run full runs including variant simulations at Triggered full run frequency.
• Parent run trigger - when parent run trigger alert occurs in parent run, suspend full run and observed run frequency intervals. Run full runs of child run at Triggered full run frequency. See below for further details.

Once the schedule has been triggered, it will continue to be used, even if alerts stop occurring. The alert trigger can be manually reset in the Operator in the Server Simulation Schedule Window or from the Manifest toolbar. Alternatively, you can specify in the manifest, the number of minutes after an alert of a certain category has been triggered, for that trigger to expire, and for the run to return to its normal run schedule. The trigger expiry time is compared to the run origin when InfoWorks ICM evaluates resetting the trigger.

Triggering full runs for a child manifest from a parent manifest

The parent-child manifest relationship allows runs associated with a 'child' manifest to be triggered by the occurrence of an event in a run from the '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.

Use the Setup page of the child manifest to schedule a child run to be triggered from a parent manifest:

• Select the Parent manifest that will provide the trigger
• Select the Alert that will initiate the Triggered full run frequency of the child manifest in the Parent run trigger field of the Run Schedule.
  Note: The Parent run trigger refers to an Alert in the Alert definition list specified in the parent manifest, not the Alert definition list specified in the child manifest.

The parent manifest must be included in the same Manifest deployment as the child manifest.