Главная Обратная связь

Дисциплины:






Triggers, inputs, outputs and interfaces



Many events may trigger Availability Management activity. These include:

  • New or changed business needs or new or changed services
  • New or changed targets within agreements, such as SLRs, SLAs, OLAs or contracts
  • Service or component breaches, availability events and alerts, including threshold events, exception reports
  • Periodic activities such as reviewing, revising or reporting
  • Review of Availability Management forecasts, reports and plans
  • Review and revision of business and IT plans and strategies
  • Review and revision of designs and strategies
  • Recognition or notification of a change of risk or impact of a business process or VBF, an IT service or component
  • Request from SLM for assistance with availability targets and explanation of achievements.

The key interfaces that Availability Management has with other processes are:

  • Incident andProblem Management: in providing assistance with the resolution and subsequent justification and correction of availability incidents and problems
  • Capacity Management: with the provision of resilience and spare capacity
  • IT Service Continuity Management: with the assessment of business impact and risk and the provision of resilience, fail-over and recovery mechanisms
  • Service Level Management: assistance with the determining of availability targets and the investigation and resolution of service and component breaches.

4.4.6.1 Inputs

A number of sources of information are relevant to the Availability Management process. Some of these are as follows:

  • Business information: from the organization’s business strategy, plans and financial plans, and information on their current and future requirements, including the availability requirements for new or enhanced IT services
  • Business impact information: from BIAs and assessment of VBFs underpinned by IT services
  • Previous Risk Analysis and Assessment reports and a Risk Register
  • Service information: from the Service Portfolio and the Service Catalogue,
  • Service information: from the SLM process, with details of the services from the Service Portfolio and the Service Catalogue, service level targets within SLAs and SLRs, and possibly from the monitoring of SLAs, service reviews and breaches of the SLAs
  • Financial information: from Financial Management, the cost of service provision, the cost of resources and components
  • Change andreleaseinformation: from the Change Management process with a Change Schedule, the Release Schedule from Release Management and a need to assess all changes for their impact on service availability
  • Configuration Management: containing information on the relationships between the business, the services, the supporting services and the technology
  • Service targets: from SLAs, SLRs, OLAs and contracts
  • Component information: on the availability, reliability and maintainability requirements for the technology components that underpin IT service(s)
  • Technology information: from the CMS on the topology and the relationships between the components and the assessment of the capabilities of new technology
  • Pastperformance: from previous measurements, achievements and reports and the Availability Management Information System (AMIS)
  • Unavailability andfailureinformation: from incidents and problems.

4.4.6.2 Outputs



The outputs produced by Availability Management should include:





sdamzavas.net - 2019 год. Все права принадлежат их авторам! В случае нарушение авторского права, обращайтесь по форме обратной связи...