Service Availability Management Reporting: In the last blog we talked about outages. Here we will discuss on how the outages can be processed.

Outages can have statuses like:

New – indicates newly created outages

In Process – being worked up on by an IT employee who is enriching or adjusting the outage details

To be reviewed – once the data is enriched, data is verified before it is confirmed

Confirmed – these outages are part of availability reporting

Rejected  – not considered for reporting

Service Availability is a result of all outages which happened during the related reporting period until current day of current reporting period, but occurred outside the agreed Contractual maintenance period.

How Service Availability is measured

Service Availability Management – Reporting

  • a)      „Maintenance Weekend“ on 3.16 time 08:00 – 18:00 ie.,   600 -> = 600min
  • b)      „Regular Contractual Maintenance period“: on  8.3.16 time 07:00 – 11:00 -> 240 min
  • Unplanned outage(SLA relevant)

    1. c)       „ABAP System Availability“ 02.3.2016 6:42 – 8:57 = 135 min

    DH = Total of all Downtimes 975 Min (a+b+c)

    SDH = 840 Min (a+b)

    TH = March = 31 days = 744h (=44640Min)

    TA= (1- (975min-840min)/44640min) = 99,69% for the system in march

    Here is a typical system availability chart :

    Service Availability Management – Reporting