![]() ![]() ![]() The result is a single-page-view of maintenance activities. The information modelling technique with respect to data visualisation is emphasised. The occurrences are accumulated over time as historical information and represented in a visual format over a timeline based on an entity relationship diagram. In this paper, these events are occurrences which are classified and categorised into levels. This paper presents a proposed methodology for aggregate visualisation techniques and a 2D graphical plot method as well as a summary of events on a timeline. These different SLO’s are still displayed together in the SLD dashboard and SLD reports.This article introduces maintenance informatics dashboard design approach for visualising maintenance, repair and overhaul events on a timeline. In OpsMgr different SLO’s can be defined based upon what states are considered as downtime. Summary: Don’t get stuck in the mindset that an SLT can only contain a single SLO. Using the SLD dashboard, we can display both of these different SLO’s together as shown below. When we are creating the SLT we can define multiple SLO’s as shown in the graphics below: See the graphic below for an example of how not to name the SLO’s. ![]() ![]() It is more intuitive to see “Planned Maintenance – “ than to see “Operations Manager – P” on the dashboard. Only the first 22 characters are displayed on the dashboard. TIP: When naming your service level objectives, put the unique portion of the SLO in the front of the name. Another SLO which does include planned maintenance and has a 95% uptime requirement. One SLO which does not include planned maintenance and has a 99% uptime requirement. The example discussed in the blog entry shows a single SLT which has two different SLO’s. As an example, service levels may include or not include planned maintenance windows. A single SLT can be created which contains multiple Service Level Objectives (SLO’s). For a long time I got stuck in the mindset that a Service Level Tracking item (SLT) contained a single Service Level Objective (SLO). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |