• During implementation, to clone a 'gold' configuration to another environment.

• During implementation, to clone an environment with converted data to another environment for System Integration testing or User Acceptance Testing.

• Once live, to clone Production data to a Test environment.

• The source environment version must be compatible with the target environment version. Compatibility is defined as the source version being either the same version or one version lower than the target version. For example, a source environment version 23B can be cloned to a target environment version 23C, but not to a target environment version 24A.

• Cross-product clones are also supported from Meter Solution Cloud Service (MSCS) to Customer Cloud Service (CCS).

• Non-Mandatory: Any information you have on your target environment that you want to keep (including message senders, user information, etc) can be preserved using the following procedure:

• Before you submit the clone request, extract the information you want to preserve using CMA Export.

• After the clone procedure was successfully completed, import the preserved data using CMA Import.

• During the implementation phase, a customer can request:

• A Dev-sized environment to be cloned to another Dev, Test or Prod environment.

• A Test-sized environment can be cloned to another Dev, Test or Prod environment as long as the source environment size is within the usage limits of the target environment.

• A Production environment can be cloned to another Dev or Test environment as long as the source environment size is within usage limits of the target environment.

• Refer to the Usage Limits section in the Oracle Energy and Water Cloud Services document.

• Once the customer is live, a non-prod environment will not be cloned to the Prod environment.

• Hot clone (in which the source environment will be online during the cloning activity)

• Cold clone (in which the source environment will not be available for certain duration of the cloning activity)

• Process automation configuration, used for running CMA between environments

• Configuration related to how the target environment is identified by name is preserved in the clone. For example, if the target environment is called "DEV01"

• Environment specific Oracle Object Storage configurations are preserved during the clone and not overwritten by source data.

• Configuration related to outbound integrations with external systems are NOT preserved if the source environment is a production environment (including message senders, external system references). Customer must reconfigure these as post cloning steps. Please refer to Oracle Utilities Cloud Services - Customer Instructions after a Clone Request (Doc ID 2832335.1).Customers can use Content Migration Assistant (CMA) to preserve custom message senders and apply them after the clone has been created to save time.

• Identity Cloud Service (IDCS) or Oracle Cloud Infrastructure Identity and Access Management (IAM) users are not migrated from source to target IDCS or IAM. Therefore, users that exist as IDCS or IAM Users with rights to access the source environment will not automatically have IDCS or IAM rights to access the target environment. Customers may need to adjust this manually as needed (please refer to Identity and Access Management and Identity and Access Management with Identity Domains in the Oracle Utilities Cloud Services Administration Guide for details).

• If a user exists in the target environment IDCS or IAM instance, but is not defined in the original source application environment, the user will be created upon access with minimal access.

• When the activity gets scheduled

• Interim update to announce that source environment is back - on the day of the activity for the cold clone approach

• Irrespective of clone approach (hot/cold), an interim update to notify bringing down of the target environment.

• Completion notification once the activity gets completed.

• Extension notification in case the activity is taking more time to complete, there on interim updates every three hours until completion of the activity

• The customer needs to specify the desired date/ time of the cut of the source environment if needed.

• The customer must submit one service request per cloning request.

• The scheduling of the clone activity for multiple clone requests made during same day or same week will be scheduled as per available slots, and the 7 business day service level objective may not be met for all requests

• There are pre- and post-cloning steps that the customer must understand and follow to complete the clone. Refer to Oracle Utilities Cloud Services - Customer Instructions after a Clone Request (Doc ID 2832335.1) for instructions.

• Acknowledge and schedule the execution of the service request.

• Inform the customer about the clone activity date/ time and ETA of activity via Service Request (SR) response.

• If the customer requested schedule is not available, propose alternative available schedule.

• Once the schedule is confirmed, send scheduled maintenance notification to the customer prior to its execution.

• Provide the status updates as detailed in the Customer Notifications section

• Once the clone activity has been performed, it will not be possible to revert the environment to a prior state before the activity.

• If for any reason, the customer wishes to postpone the clone to a different date OR wish to change the environment (source or target), it will require the following:

• Customer will need to create a new service request ticket. The ticket will be counted as a fresh request by Oracle and will follow the SLA for the new request.

• Customer will intimate this change on the existing Service request ticket providing reference of the new service request created and will then close the ticket

• Oracle will acknowledge the new service request, perform pre-checks listed in the Pre-requisites for Requesting Environment Clones section above and availability of the requested schedule.

• Oracle will update the Service request Ticket and confirm schedule.

• Advanced Notice: 7 business days (exception if the customer makes multiple clone requests at once, only the highest priority clone request will target this service level objective)

• Acknowledge/Schedule: 2 business days

• Execution Time: Based on the size of the source environment. Please see the table in Business Impact section above.

• Outage Expected: See the Business Impact section above