Establishing a measurement and evaluation plan

For some installations, a measurement and evaluation plan might be suitable. A measurement and evaluation plan is a structured way to measure, evaluate, and monitor the performance of the system.

To set up a measurement and evaluation plan, perform the following steps:
  1. Devise the plan.
  2. Review the plan.
  3. Implement the plan.
  4. Revise and upgrade the plan as necessary.
To use the plan, perform the following major activities:
  • Collect information periodically to determine:
    • Whether objectives have been met
    • Transaction activity
    • Resource utilization
  • Summarize and analyze the information. For this activity:
    • Plot volumes and averages on a chart at a specified frequency
    • Plot resource utilization on a chart at a specified frequency
    • Log unusual conditions on a daily log
    • Review the logs and charts weekly
  • Make or recommend changes if objectives have not been met.
  • Relate past, current, and projected transaction activity and resource utilization to determine if objectives continue to be met, and whether resources are being used beyond an efficient capacity.
  • Keep interested parties informed with informal reports, written reports, and monthly meetings.
A typical measurement and evaluation plan might include the following items as objectives, with statements of recording frequency and the measurement tool to be used:
  • Volume and response time for each department
  • Network activity:
    • Total transactions
    • Tasks per second
    • Total by transaction type
    • Hourly transaction volume (total, and by transaction)
  • Resource utilization examples:
    • DSA utilization
    • Processor utilization with CICS®
    • Paging rate for CICS and for the system
    • Channel utilization
    • Device utilization
    • Data set utilization
    • Line utilization
  • Unusual conditions:
    • Network problems
    • Application problems
    • Operator problems
    • Transaction count for entry to transaction classes
    • SOS occurrences
    • Storage violations
    • Device problems (not associated with the communications network)
    • System outage
    • CICS outage time


dfht3k6.html | Timestamp icon Last updated: Monday, 5 June 2017