3 Replies Latest reply on Nov 3, 2011 2:31 PM by Diana Caballero

    SLM,  Planned Downtime and the Blackout KM

      Share This:


      How does one accommodate Planned outages on Out of Compliance and SLO reports?

        • 1. Re: SLM,  Planned Downtime and the Blackout KM
          Andy Spiers


          Hi Llewllyn,

          In SLA Admin, when you define the Performance SLO, there is the Outage
          Column.
          (From the Help)
          The Outage column of the Performance Thresholds table indicates whether
          outages will occur or not.
          Select yes or no from the drop-down list.
          Yes means that an outage will occur at the time specified in the From and To
          columns on the day indicated in the Weekday column. When you have an outage
          scheduled, you should enter 0 as your threshold value for that row. If you
          enter a value other than 0, that value will be disregarded and plotted as a
          0 on your report.
          No means that no outages are permitted. If an outage occurs, the SLA is out
          of compliance.
          Note
          Use the Description column to describe the outage

          Andy Spiers
          BMC Software UK

          "Llewellyn Daniels" <llewellyn.daniels@cpt.mgxgroup.com> wrote in message
          news:5763.2205@devcon.bmc.com...
          > How does one accommodate Planned outages on Out of Compliance and SLO
          reports?
          >

          • 2. Re: SLM,  Planned Downtime and the Blackout KM


            Andy,

            Thanks. I was hoping there would be some way where one could
            programmatically set the appropriate columns
            in the right tables to reflect the planned outages. If you only have a few
            parameters in your performance threshold
            definitions then it's no problem doing it the way you suggest.

            In this case we have a performance threshold for the E2E (end-to-end
            response time) of every SAP transaction executed
            in different geographical locations. These values are loaded into the SR
            database using the Open Data Retriever. Currently
            there are SLA's negotiated for the response times of 20 of these
            transactions, but this will increase. Every time there is a planned outage,
            the performance threshold of all these SAP transactions needs to be changed.
            This could potentially become an administration
            burden.

            Let's assume the following ideal situation. The planned outage is captured
            centrally via Vantive or Peregrine Service Centre or Remedy AR like in our
            case.
            The components affected are automatically flagged via information stored in
            the asset register or some other database. All components that has
            performance
            threshold definitions in the SR database are identified and the outage is
            programmatically recorded in the database along the same principles as
            stated
            by your post.

            Is this possible or are we over-complicating things a bit?

            Llewellyn Daniels








            "Andy Spiers" <aspiers@bmc.com> wrote in message
            news:5778.2205@devcon.bmc.com...
            > Hi Llewllyn,
            >
            > In SLA Admin, when you define the Performance SLO, there is the Outage
            > Column.
            > (From the Help)
            > The Outage column of the Performance Thresholds table indicates whether
            > outages will occur or not.
            > Select yes or no from the drop-down list.
            > Yes means that an outage will occur at the time specified in the From and
            To
            > columns on the day indicated in the Weekday column. When you have an
            outage
            > scheduled, you should enter 0 as your threshold value for that row. If you
            > enter a value other than 0, that value will be disregarded and plotted as
            a
            > 0 on your report.
            > No means that no outages are permitted. If an outage occurs, the SLA is
            out
            > of compliance.
            > Note
            > Use the Description column to describe the outage
            >
            > Andy Spiers
            > BMC Software UK
            >
            > "Llewellyn Daniels" <llewellyn.daniels@cpt.mgxgroup.com> wrote in message
            > news:5763.2205@devcon.bmc.com...
            > > How does one accommodate Planned outages on Out of Compliance and SLO
            > reports?
            > >
            >

            • 3. Re: SLM,  Planned Downtime and the Blackout KM

              Hi Llewellyn,

               

              I'm interested in learning how you captured your planned outages in Remedy AR. Could you provide some assistance?

               

              Thanks,

               

              Diana