System Guides

Dependency to Service Mapping is a crucial process within the AMSS (Andy Management System Suite) that enables organizations to identify and understand the interdependencies between their various business services. It provides a comprehensive overview of how different services within the organization rely on each other to function effectively. In this tutorial, users will understand how to identify and assess dependencies for business services, evaluate their potential risks and impacts, and determine appropriate strategies/ response measures for ensuring continuity in the event of disruptions. Below is a brief description of the fields for dependency mapping:

1. Dependency ID: This field represents the identifier or unique reference number for the dependency mapping. It helps in tracking and referencing the specific dependency. Demo-DEP-09062023693: This is an example of a Dependency ID, showcasing the format and structure of the identifier.

2. Date: This field captures the date when the dependency mapping was conducted. It helps in tracking the timeline of the mapping process.

3. Process: This field specifies the process for which the dependency mapping is being done. It establishes the link between the process and its dependencies.

4. Dependency Type: This field indicates the type of dependency for the business service. It can include options such as people, internal services, external services, IT/Communications, etc. It helps in categorizing and understanding the nature of dependencies.

5. Description: This field allows for providing a brief description of the dependency. It helps in documenting any specific details or characteristics of the dependency.

6. Single Point of Failure: This field indicates whether there is a single point of failure present or not for the dependency. It helps in identifying vulnerabilities and risks associated with the dependency.

7. BC Capability: This field assesses the business continuity (BC) capability of the dependency and can be categorized as inadequate, adequate, or somewhat adequate. It helps in evaluating the preparedness of the dependency for disruptions.

8. Likelihood of a Disruption: This field assesses the likelihood of a disruption occurring for the dependency and can be categorized as very low, low, medium, high, or very high. It helps in understanding the risk level associated with the dependency.

9. Impact of Disruption: This field assesses the impact of a disruption occurring for the dependency and can be categorized as marginal, acceptable, high, or catastrophic. It helps in evaluating the severity of the impact on business operations.

10. Normal Requirement: This field captures any specific requirements or expectations related to the dependency. It helps in documenting the normal functioning or performance expected from the dependency.

11. Response Timeline in an Event of a Disruption: This field indicates the expected response time in the event of a disruption for the dependency. It can be categorized as immediately, 1 hour, 4 hours, 8 hours, 24 hours, 1 week, 2 days, over 1 week, less than 1 hour, or not applicable. It helps in setting expectations for resolving disruptions and restoring the dependency.

12. Attachment: This field allows for attaching relevant files or documents related to the dependency mapping.

13. Additional Details: This field provides space for capturing any additional information or specific details relevant to the dependency mapping.

Continue

Process Mapping is a critical component of Business Service Mapping within the AMSS (Andy Management System Suite) that enables organizations to visualize and analyze their business processes in relation to the overall delivery of business services. By mapping out the step-by-step activities, interactions, and dependencies of each process, Process Mapping provides a comprehensive understanding of how different processes contribute to the successful execution of business services.

This tutorial is a brief description of the feature called "Process Mapping" and the different options available within this feature to help the users gain a better understanding of how to navigate and utilize the "Process Mapping" feature in order to map processes effectively.

1. Process ID: This field represents the unique identification code or number assigned to the process. It helps in linking the process mapping to a specific process within the service. 

2. Review Date: This field indicates the date when the process mapping will be reviewed or assessed for any updates or changes. It helps in ensuring the mapping remains up-to-date and aligned with the process.

3. Business Service ID: This field captures the identification code or name of the business service to which the process belongs. In this example, "Training services" is selected. It provides context and linkage between the process and the service.

4. Process Description: This field allows you to provide a description or summary of the process being mapped. It should provide an overview of the steps involved and the purpose of the process.

5. Process Owner: This field captures the name or designation of the person or department responsible for owning and managing the process. It helps in assigning accountability for the process.

6. Business Criticality: This field indicates the level of importance or criticality of the process to the business operations. It helps in prioritizing processes based on their impact.

7. Process Provider: This field captures the name or designation of the external or internal entity responsible for providing or executing the process. It helps in identifying the entity responsible for delivering the process.

8. Agreement: This field refers to any agreements or contracts associated with the process. It could include service level agreements (SLAs) or any other contractual obligations.

9. Continuity Plan: This field indicates whether a continuity plan exists for the process. It refers to a plan that outlines steps to ensure the process can continue uninterrupted in the event of disruptions or emergencies.

10. Attachment: This field allows for attaching any relevant files or documents related to the process mapping, such as process flowcharts or supporting documentation.

11. Additional Details: This field provides space for any additional information or details regarding the process mapping that may be relevant or important to note.

Continue