On completion of the Cost Reduction process, the final workload becomes the base-line against which future change can be measured. This is critical for understanding the impact of change on processing. Without having something to compare, it will not be obvious or clear as to why a system has slowed down, behaves differently or costs more to run and operate.
Change occurs in many different ways. For example a fix to a defect; a change to accommodate a new business requirement; a change in business processing due to seasonal fluctuation. The Risk Management process is used to identify the impact of the change at a resource level,comparing the resource consumption of key areas between the base-line and the new workload.
The Risk Management process, shown below, is similar to the Cost Reduction process, except that there are no change recommendations. This reduces the time to deliver, and the cost of the service.
Collect
|
The collect phase runs on the client side and consists of extracting run-time metrics from Db2 into flat files. The files, which can be anonymised as part of the process, are provided to MetricsAnalysis. |
Analyse |
The analyse phase consists of processing the files through a bespoke data warehouse and data mart, built on best practice and industry standards. This involves adding 9000+ calculations to the extracted metrics to provide a comprehensive multi-dimensional analysis of the data. The analysis phase ends in the production of multiple documents, to be used by a MetricsAnalysis Db2 specialist to analyse the workload and identify discrepancies in the use of Db2 and its configuration. |
Report
|
The end product is a document detailing a comprehensive analysis of the workload presented, comparing it to the base-lined workload. This provides a comprehensive analysis of the impact of any change in the application or business processing and the effect on resources. |
Evaluate
|
A report is provided to the client, who can choose whether or not further analysis is required. The purpose of the report is to provide assurance on the impact of change on resource consumption. Any unexpected peaks in resource consumption can be analysed without any further collection of data. |
Repeat |
As systems evolve the volume of data and use of applications evolve. This means that the way in which Db2 processes may change. A low cost analysis can quickly identify changes in resource consumption. Managing this change proactively will help keep costs down by identifying and addressing discrepancies sooner. |
||
Are you ready to understand how your system affects and is affected by Db2 processing? Book a low-cost 100% money-back guaranteed analysis now..