Server Simulation Schedule Window

This window contains information provided by the Innovyze Live Server about the current state of automatic runs, trigger state and mode of operation settings, on a per manifest basis. This information is updated dynamically, when information on the server changes, therefore, a connection to the Innovyze Live Server is required.

To turn display of the window on/off, select Server sim schedule from the Window menu.

Tip: This window shows information for all manifests in the database, not just the current manifest deployment selected in the Operator Client. Disabled manifests (manifests that exist in a un-deployed Manifest Deployment object) may also be included in the display. It is possible to hide or show disabled manifests.

To display the window, click the Server Sim Schedule tab in the middle of the Overview page, or select Server Sim schedule from the Window menu.

Simulation Schedule Window

Window description

Field Description

Manifest

Read-only field.

Name of the manifest.

Tip: If the manifest name (as well as all data on the same row) is displayed in grey text, this indicates that the manifest is disabled.

Mode

Current mode of operation.

This provides the exact same functionality as the Mode of Operation dropdown in the Manifest toolbar of the Network page. If the manifest is enabled and the server is connected, then this field can be modified.

Available modes of operation are:

Normal - Manifest schedule to run as specified.

Manual runs only - Runs can only be generated manually by the user.

Ignore alert triggers - Alert triggers will be ignored. Users may wish to select this option if there is a spurious alert that keeps triggering full model runs unnecessarily.

Tip: One key feature of the Simulation Schedule Window is the replication of functionality to set the manifest mode of operations and to toggle the alert full model runs trigger state for the entire database from a single location. (These actions can also be performed individually by navigating to each network page and changing the settings there by using the relevant toolbar options).

Alert Trigger

Current alert trigger state.

This provides the same functionality as the Modify alert trigger toggle of the Manifest toolbar (Network page). If the manifest is enabled and the server is connected, this field can be modified.

The Alert Trigger may be set to:

Off - the alert trigger is not set. Baseline simulations will be scheduled at the Full run frequency specified in the Manifest in InfoWorks ICM Ultimate or ICMLive Configuration Manager.

Baseline runs only - the alert trigger is set. Baseline simulations will be scheduled at the Triggered full run frequency specified in the Manifest in InfoWorks ICM Ultimate or ICMLive Configuration Manager.

Baseline and variant runs - the alert trigger is set. Baseline and variant simulations will be scheduled at the Triggered full run frequency specified in the Manifest in the configuration manager. (It is not possible to set this alert trigger state if the run variants property in the manifest run schedule is set to Never.)

Tip: One key feature of the Simulation Schedule Window is the replication of functionality to set the manifest mode of operations and to toggle the alert (full model runs) trigger state for the entire database from a single location. (These actions can also be performed individually by navigating to each network page and changing the settings there by using the relevant toolbar options).

The current status of the full run and variant run triggers are as displayed as tooltips in the Alert Trigger column. See the full run trigger and variant run trigger descriptions in the Summary Window for further information.

Next Scheduled Simulation

Next scheduled simulation.

Field Description

Time

Read-only field.

Time that the next simulation is scheduled to be dispatched.

Type

Read-only field.

Type of run that has been dispatched:

Full - full baseline simulation will be run

Full + Variants - full run of both baseline and variant simulations

Observed - observed run of baseline simulation carrying out only rainfall runoff calculations

Current Automatic Simulation

Active simulation.

This simulation has been dispatched by the server scheduler to the server factory.

Field Description

Time

Read-only field.

Time that the current simulation was scheduled to be dispatched, which is usually the time at which the simulation was indeed dispatched.

Tip: In cases where the server is running late simulations immediately after startup, the actual time that the simulation was dispatched may be later than the scheduled time.

Type

Read-only field.

Type of run that has been dispatched:

Full - full baseline simulation

Full + Variants - full run of both baseline and variant simulations

Observed - observed run of baseline simulation carrying out only rainfall runoff calculations

Event

Read-only field.

Type of event that initiated the automatic simulation:

  • Scheduled - Automatic simulation either regularly scheduled or scheduled per the alert trigger schedule.
  • Externally triggered - Automatic simulation initiated by a third party application that modifies the external trigger file (The trigger file is specified in the Manifest object in InfoWorks ICM Ultimate or ICMLive Configuration Manager).

Run Status

Read-only field.

Status of the overall status of all the jobs in the run transaction. When all of the jobs in the run transaction complete (Success, Success - Warning, Success - Incomplete, or Failed - See below for more details) the overall status will always be set to the highest level contained in any one individual job.

The status may be one of the following:

  • Licensing (with tooltip error text) – The server has generated a simulation request and has sent the request to the server run factory, but the factory is unable to process the run because the server is not currently licensed. The server will process the run when the server becomes licensed.
  • Creating (with tooltip error text) – The server has generated a simulation request and has sent the request to the server run factory, but the factory is unable to process the run because the Workgroup Data Server is not currently available. The server will process the run when the Workgroup Data Server becomes available.
  • Submitting (with tooltip error text) – The server has generated a simulation request and has sent the request to the server run factory, but the factory is unable to process the run because the InfoWorks Agent server is not currently available. The server will process the run when the InfoWorks Agent server becomes available.
  • Waiting - The server factory has created the run object and successfully sent all jobs in the run transaction to the job server.
  • Note: This does not imply any status about the result of the simulation.
  • Succeeded – All jobs in the run transaction completed successfully.
  • Succeeded – Warning – All jobs in the run transaction completed successfully, but one or more jobs completed with warnings.
  • Succeeded – Incomplete – All jobs in the run transaction completed successfully, but one or more jobs are incomplete
  • Failed (with tooltip error text) - The server factory is unable to complete the requested simulation request or at least one job in the run transaction failed.

Additionally this field is colour coded to give the user a visual cue:

Colour coding

Job Status

Status of the current job with respect to the server local job agent, including job lists and optional error text available by tooltip. The status may be of one or more of the following values:

  • Waiting – The server factory has successfully dispatched one or more jobs (i.e. Sim, Alert, Export) associated with the current simulation, but the job is either waiting to be processed by the InfoWorks agent server, or it is currently in progress.
  • Succeeded – Indicates that a job has successfully completed.
  • Succeeded – Warning – Indicates that a job has successfully completed with warnings.
  • Succeeded – Incomplete – Indicates that a job has successfully completed, as incomplete.
  • Failed - Indicates that a job has failed. Further information about the failed job is available by tooltip.

The status is displayed as a string of status, indicating the number of associated jobs that have that status:

n Waiting, n Succeeded, n Succeeded – Warning, n Succeeded – Incomplete, n Failed

Where n is the number of jobs that the status applies to. If n = 0 then the status is omitted from the status string.

Similarly to run status, this field is colour coded to give the user a visual cue:

Colour coding

Additionally, clicking the Job Status cell displays the Current automatic simulation job status dialog.

Current automatic simulation job status dialog

This dialog lets you view more details about the current automatic simulation and to open logs, when available:

  • Right-click a simulation and select Open log from the context menu to open the related simulation / job log in a new tab.
  • Click Refresh to manually update the current agent job status information.
  • Click Done to close the dialog.

Context menu

The following operations can be carried out via the context menu: