Create New Recovery task form

Planned order of the recovery task. The sequence for the recovery task is automatically determined and populated in the Planned order field. This sequence is derived from the values in the Dependencies field, which outlines the task dependencies. For instance, if task 2 relies on task 1, then task 1 is assigned order 1, and task 2 is assigned order 2. In scenarios where a task depends on two other tasks, the task with the highest planned order among the dependencies is used. It's possible for two tasks to both have a planned order of 2 if each is dependent on task 1.

Note: To update the planned order of a recovery task, use the Refresh task order UI action.

Option to exclude specific event tasks from time calculations.

When this flag is checked, the selected task is excluded from time calculations during an event. In the Crisis management app, checking this flag confirms that the task is not included in the Actual time taken and Total effort field updates for both the asset and the activated plan associated with the event.

For scenarios with multiple tasks, you can exclude specific tasks from overall time calculations, effectively removing them from the total time estimate. This enables for more accurate time tracking by focusing only on relevant tasks. Any task that is excluded isn’t considered in the plan and asset time calculation.

Option to include the recovery task in exercises, actual events, or both. With this flag, you can prevent test tasks from coming into the events. Available options are in the order of priority:

• Both actual events and exercises
• Actual events only
• Exercises only

Option to associate all assets, no assets, or specific assets with a recovery task. The actual duration and effort recorded in the events are determined by how the assets are tagged as shown with these options:

• None: Associate no assets from the plan with the recovery task.
• Specific assets: Select this option to display the Asset scope field. It enables you to define the scope for the assets that are tagged within the plan.
• All: Associate all assets from the plan with the recovery task.

Once this configuration is established and the plan is activated during an event, the assets are tagged. The time and effort recorded in the events are determined by how the assets are tagged.

Option to enable clearer visual indicators for different levels of recovery progress for the asset. Available options are:

• None: The selected recovery or event task is not recovered.
• Partially recovered: The event asset is partially recovered after completing the associated recovery task.
• Recovered: The event asset is fully recovered after completing the associated recovery task.

Color coding in the Asset Recovery Level column provides clearer visual indicators for different recovery progress levels.

The "Asset Recovery Level" column has been added to both recovery tasks and event tasks, enabling you to select the recovery level for an asset. Once all associated tasks with the same recovery level are completed, the asset's state is auto-updated.

The existing recovery process required all steps to be completed before an asset could be marked as recovered. This functionality remains supported. Additionally, a new capability has been introduced, allowing you to mark an asset as "Partially recovered" after completing critical tasks. This enhancement provides better visibility into the recovery process, enabling teams to address smaller, ad-hoc tasks later.

For example, if a recovery process involves three steps, you can consider an asset recovered after completing step two, and defer step three to a later time. This provides greater flexibility in managing your recovery processes.

Planned duration of the recovery task shown in Days, Hours, Minutes, and Seconds. This field is crucial for determining several aspects: - Establishing the planned start and end times during execution. - Calculating any delays that occur during execution.

The default setting for this field is 00:00:00:00. The Completion deadline field, which was a reference field used previously for indicating time frames, is now removed from the plan task records.