• Confirm batch stability, day over day execution according to your production schedule, and that performance is within acceptable production window

• Leverage production converted data, along with actual production files for critical batch inputs, including usage/reads, payments and other billing input files when testing batch execution

• Confirm stable batch execution for a full month of bill cycles, plus the first three (3) cycles of the subsequent month to ensure consistency in batch execution across all bill cycles

• Execute bill comparison of bills generated in this Cloud Service to your legacy customer information system ("CIS") bills, with majority of differences explained and determined acceptable for multiple consecutive cycles.

• Review and confirm that key output files, minimally bill print and letters, are acceptable

• Review daily To Do entry volumes and confirm them to be acceptable based on available staffing

• Update database partitioning prior to go live. See Go-Live Checklist in the Information Lifecycle Management chapter of the Oracle Utilities Cloud Services Implementation Guide.