RG Solutions Service Level reports help you to manage and improve the quality of services that are to be delivered by IT to the Business.
When reporting Service Levels in RG Solutions, we look at the systems from the perspective of the services that are being provided. In some cases, there might be a single service running on a single machine. In others, there might be multiple services running on a single machine. RG Solutions can handle all of these scenarios.
Quite often, the Service(s) being provided run in either Interactive (online) or Update (batch) processing modes. Each of these modes of processing is very different from the other, and therefore, measurement of service levels in an interactive environment is treated very differently to that in an update environment.
In an interactive workload where activity on the system will largely be driven by transactions, the primary concern is that those transactions are serviced in accordance with your Service Level Agreement (SLA). Agreements reached in your SLA can be incorporated into RG Solutions for this measurement.
Update environments are largely concerned with turning round high intensity processing as quickly as possible. Therefore, the approach RG Solutions takes is to measure the batch processing elapsed time against a deadline (usually the start of interactive processing).
The following charts provide some examples of how RG Solutions can address Service Level reporting.
Interactive Service Levels
The example below shows the response times for real-time services for a financial institution with a service level agreement (SLA) of 99% less than 1 second. The “Business Banking” service is highlighted in red to show its service level was 97%, which is below the required service level of 99%.

Interactive Service Level Trend
As a result of the Business Banking service falling below its target, the next example shows how the Interactive Business Banking service was delivered over the last 12 months.
Quite clearly, this was the first month when the service target had not been realised. Closer investigation of this system revealed there had been a step change in Online Capacity on the system where this service runs due to new functionality being added. Due to this the online system was now out of capacity and unable to deliver the service required.

Update Service Levels
The next example shows the turnaround time for overnight updates for a financial institution within a service window of 18:00 to 08:00.
Click on the chart to see that “Business Banking” ran over its window and did not finish until 8:40, preventing the online service from being available.

Click here to download a copy of this page in printer friendly format
..more...