Setting dependency levels
Setting up dependency values
The mapping process creates a relationship between all the components that have been mapped or allocated to each other. In this way processes are mapped to products & services and assets and resources are mapped to processes. The level of dependency that one component has on a mapped component is also recorded as part of this process. When a new item is mapped to another component the system assigned a "very high" dependency rating automatically. If the User disagrees with this rating then the User can then set an alternative rating using the dropdown list box at the foot of the "allocated to" screen. Clicking on this dropdown arrow will cause the following pop-up to appear.
For each mapped process or activity, set a suitable dependency rating that reflects the level of dependency of each product, service or other critical objective on each allocated process or activity. Five dependency levels are available through the dependency dropdown list box. The chosen dependency level will affect the BIA values being transferred from the product, service or other critical objective to the mapped process or activity. Information of these BIA value changes will appear in the dropdown list box.
Very high dependency
The top row in the list box (beneath the headings) relates to a "very high" dependency rating. This will pass the same BIA values to the mapped component as has been applied to the product or service through the BIA process. A very high dependency rating indicates that any serious disruption to the process or activity being allocated is likely to completely disrupt the dependent product, service or other critical objective.
High dependency
The second row relates to a "high" dependency level rating and therefore the RTO and MTPD values being passed from the product, service or other critical objective to the allocated process or activity have moved to the next larger value in the time period look up table. This new value is to reflect the slightly lower level of dependency. A "high" dependency rating indicates that any serious disruption to the process or activity being allocated is likely to have a fairly serious impact on the dependent product, service or other critical objective.
Medium dependency
The third row relates to a "medium" dependency level rating and the RTO and MTPD values being passed on the process or activity have been extended by two time periods in the look up table. This new value reflects the medium level of dependency of the product, service or other critical objective on the related process or activity. A "medium" dependency rating indicates that any serious disruption to the process or activity being allocated is likely to have a measurable but not serious impact on the dependent product, service or other critical objective.
Low dependency
The fourth row relates to a "low" dependency level rating and the RTO and MTPD values being passed on the process or activity have been extended by three time periods in the look up table. These new values reflect the low level of dependency of the product, service or other critical objective on the related process or activity. A "low" dependency rating indicates that any serious disruption to the process or activity being allocated is not likely to have that much of an impact on the dependent product, service or other critical objective.
Very low dependency
The bottom row relates to a " very low" dependency level rating and the RTO and MTPD values being passed on the process or activity have been extended by four time periods in the look up table. These new values reflect the very low level of dependency of the product, service or other critical objective on the related process or activity. A " very low" dependency rating indicates that any serious disruption to the process or activity being allocated will have only very minimal impact on the dependent product, service or other critical objective.
Reference material: