Evaluate performance adjustments against workload behaviour
Robot Autotune is listed in the Robot portfolio for IBM i resource adjustment. Treat it as a controlled performance-management enquiry, not a promise that software can replace capacity planning. The useful question is which workload conditions justify a change and how the operator will determine whether that change helped.
Capture a baseline across ordinary work and relevant peaks, including batch periods and business deadlines. Identify the resource settings within the proposed scope and confirm supported operation for the installed IBM i release. Record existing manual tuning and other automation to avoid competing changes.
Agree observation, limits and reversal
Before allowing adjustments, define the measures that matter: response for a named service, completion of a batch window or another application-owner objective. A lower utilisation figure alone may not mean better business performance. Test in an approved environment or maintenance procedure and retain the original configuration.
Acceptance should document the conditions observed, settings changed and results, with explicit limits on any automatic action. Establish who reviews unexpected effects and how to return to a known state. UAE sites with overnight processing should include the actual shift and escalation arrangements in handover. Additional hardware or application optimisation remains a separate design decision.
Evidence to request for this scope
- Confirm the exact adjustable settings and current product compatibility for the proposed environment.
- Compare a representative workload baseline with the approved trial conditions and record the limitations.
- Retain change limits, rollback instructions and a named performance-review owner.