System Guides

Dependency ID: Automatically generated by the system for dependency identification. System-generated; no manual entry required.

Date: Default is the current date. Automatically populated with the current date; no manual entry required.

Dependency Type: Choose the type of dependency from predefined options.

• Data/ Information: The dependency involves critical data or information necessary for business operations.

• Environment/ Climate: The dependency relates to climate conditions or environmental factors that impact operations.

• Power Infrastructure: The dependency is associated with the power infrastructure essential for business activities.

• Public Infrastructure: The dependency is linked to public infrastructure, such as transportation or utilities.

• Internal Support Services: The dependency is tied to internal support services crucial for daily operations.

• Partners and Suppliers: The dependency relies on services provided by external third parties.

• Finance/ Working Capital: The dependency involves the availability and management of working capital.

• Physical Infrastructure: The dependency pertains to the physical buildings or office facilities essential for business operations.

• IT and Communication: The dependency is associated with Information Technology (IT) and communication infrastructure.

• Other Dependency: The dependency falls into a category not explicitly listed. Users may provide additional details.

• People/ Workforce: The dependency is related to the workforce, including skilled personnel necessary for operations.

Description: Additional description of the dependency. Provide any necessary details to further describe the dependency.

Single Point of Failure/Weak Link: Choose the status of being a single point of failure or a weak link.

• YES: The dependency is currently identified as a single point of failure or a weak link in the system. A disruption to this dependency could significantly impact overall operations.

• NO: The dependency is not identified as a single point of failure or a weak link. Measures are in place to mitigate risks, and the dependency's failure is less likely to cause widespread disruptions.

• Not Applicable: The concept of being a single point of failure or a weak link is not applicable to this particular dependency. This may be because the dependency is redundant, has built-in fail-safes, or its failure wouldn't significantly impact overall operations.

Business Continuity Capability: Choose the level of business continuity capability associated with the dependency.

• Adequate: The business continuity capabilities for this dependency are considered sufficient and well-prepared to address potential disruptions. Adequate measures are in place to ensure continuity.

• Some capabilities exist but need improvement: While there are existing business continuity capabilities, there is room for improvement. Enhancements and additional measures may be needed to strengthen the overall preparedness.

• Inadequate: The current business continuity capabilities for this dependency are insufficient or lacking. Immediate attention and significant improvements are necessary to ensure effective continuity planning.

Normal Requirement: Choose the normal requirement status of the dependency.

• Standard Quantity: Represents the typical or standard quantity of the dependency required to support the business process.

• Baseline Condition: Indicates the base or standard condition necessary for the dependency to effectively contribute to the business process.

• Routine Configuration: Describes the routine or standard configuration needed for the dependency to function as expected.

• Usual State: Captures the typical or common state of the dependency that is normally required for the business process.

• Base Capacity: Refers to the standard capacity or level of the dependency that is typically necessary for supporting the business process.

• Nominal Performance: Represents the normal or nominal performance level required from the dependency.

• Default Setting: Refers to the default or standard setting needed for the dependency to fulfill its role in the business process.

• Everyday Requirement: Signifies the everyday or common requirement for the dependency in supporting routine business activities.

• Common Scenario: Describes a scenario that is commonly encountered and represents the typical requirement for the dependency.

• Baseline Quantity: Represents the base or standard quantity needed for the dependency to fulfill its role in the business process.

• Steady State: Describes a stable and consistent state of the dependency that is typically required.

• Conventional Setting: Refers to a setting or condition that is conventionally applied to the dependency for supporting the business process.

• Regular Demand: Represents the regular or usual demand for the dependency in the context of the business process.

• Ordinary State: Describes an ordinary or usual state that is required for the dependency to effectively contribute to the business process.

• Common Use: Indicates the common use or application of the dependency in the standard operation of the business process.

Attachment: Attach any relevant documents or files related to the dependency.

Additional Details: Provide any supplementary information about the dependency.