Not logged in - Login
< back

Assets

Resources are a hierarchy that must be allocated to a division. Resources must be defined, and should follow a hierarchical classification scheme. The default categories are: Equipment, Information, Peoples, Premises, Suppliers and Technology. Each of these can then be further expanded on to allow resources to be grouped together e.g. ‘Technology’ could be split into ‘Hardware’ and ‘Software’.

Resources should be defined before starting the BIA. This ensures that all activities pick resources from the same list. If a resource is initially missed, this can be added during the BIA. However, only an organisation administrator can add resources at this point.

Creating a New Resource

There are two ways to create a new resource. Either:
  • Click ‘Create New Resource’ (highlighted red in Figure 14 - Resource Hierarchy)
  • Navigate to the resource type then click ‘New Child Resource’ (highlighted red in Figure 15 – Add, Amend or Delete Resource Form) i.e. to create a new ‘People’ resource, click ‘People’ within the hierarchy and click ‘New Child Resource’.

Either approach will open the same ‘Resource form’.

BC Details

There are additional fields which need to be defined when an organisation is using the Abriska business continuity BIA module. Descriptions of each of these additional fields are provided below.

  • Multiple - Selecting 'yes' for this variable will mean that when activities specify that they use this resource, activities will need to indicate how many resources they use. When resources are flagged as ‘Multiple’ they will be highlighted with an asterisk on the hierarchy.
  • Limited - If a resource is flagged as a ‘Multiple’, there will be an additional option to flag this resource as ‘Limited’. This implies that there are a restricted number of these resources within the organisation and getting a replacement or adding to this number would be difficult.
  • Limited Number - If ‘Limited’ is set to 'yes', this allows the number of resources owned by the organisation to be set.
  • Recovery Point Objective (RPO) - This indicates that the resource contains information and any activity using this resource needs to enter the RPO.

@@infobox

Changing a resource from multiple to singular or vice versa can lead to possible issues if the BIA has been started. Refer to the following to understand the implications.
  1. Multiple -> Singular: If an activity has already indicated that this resource is used, then a number of resources will have been allocated to this activity. In making this modification, this multiple information will be lost.
  2. Singular -> Multiple: Each activity which has indicated that this resource is used will have been allocated one resource. In making this modification, ………………….@@………………….

Resource Dependencies

Resource Attributes