Set Up and Access AMI Data in Object Storage
Oracle Utilities Data Intelligence comes with an AMI Publisher feature that allows you to extract AMI usage data from your connected Customer Cloud Service or Meter Solution Cloud Service and publish it to your Oracle Cloud Infrastructure (OCI) object storage. From there, Oracle Utilities will copy it and transform it to iceberg table format, a high performance open-source format for large datasets. Oracle Utilities will then deliver the iceberg-formatted data as parquet files back to your object storage, where you can access it directly to support custom data science use cases. For example, data scientists at your organization can use the data to create feature sets and machine learning models, or run analyses in support of your business goals.
You must configure and run a Run a Specialized Data Export Job job to publish new AMI data to your object storage. When the job is run, Oracle Utilities will provide an initial load of 13 months of historical data. The job will start by loading the most recent day, and work its way back to the oldest day by day. During this period, the data will be available to query once the first day has arrived, and subsequent days will be available for querying as they flow in. If new data becomes available from the source system while initial load is still running, the new data will be prioritized and loaded once available. The initial load will then continue backfilling until finished.
About V Model Data
In addition to AMI data, the AMI Publisher also delivers V model data from your connected source application. V model data refers to data objects that form the core of the system: Person, Account, Premise, Service Agreement, and Service Point. These objects hold demographic, geographic, and financial information about your customers and properties. When V model data is combined with AMI usage data, you can gain deeper insights into your customers and your business operations. See Understanding the V for more information about this data.
Run a Specialized Data Export Job
Provide Oracle Utilities Access to Your Object Storage
After your AMI data has been copied to your object storage, Oracle Utilities will need access so the data can be copied and transformed to iceberg table format. If you have not already provided this access, see Provide Oracle Energy and Water with Access to Object Storage in the Administrator Guide for steps.
Access Your Transformed AMI Data
After Oracle Utilities has copied and transformed your AMI data to iceberg format, it will be delivered to your OCI object storage in the following directory: /AMI_PUBLISHER. If applicable, there will be partitions organized under each table prefix.
The list below is an example of the directories which may appear under /AMI_PUBLISHER. This list is not exhaustive.
- /AMI_PUBLISHER
- /CISADM
- /data
- /CI_TIME_ZONE
- /D1_ACTIVITY
- /D1_ACTIVITY_TYPE
- ...
- /D1_MSRMT
- /YEAR=2025
- /MONTH=1
- /DAY=1
- /MONTH=1
- /YEAR=2025
- /D1_MEASR_COMP/
- ...
- /data
- /CISADM
The columns in the files follow a standard structure. See Measurement Data Export, under the File Format section, for details about the columns and the data they contain.
The data provided is based on the core data objects from your connected cloud service: Person, Account, Premise, Service Agreement, and Service Point. For more information about this data, see Understanding the V.
Your Data Responsibilities
It is recommended that you not perform any actions on the AMI data other than reading it. You can copy the data to another location for further modification, but any changes or custom solutions built on top of this data are your sole responsibility. Keep in mind the scenarios below.
| Customer Action | AMI Publisher Response or Impact |
|---|---|
| Deletes data from the table | The AMI Publisher will attempt to recover deleted data. Large deletions may cause job failure and require technical support. |
| Adds data to the table independently | The AMI Publisher will not interact with customer-added data. |
| Updates data in the table independently | Updates will remain unless the source system provides new updates, in which case the AMI Publisher will overwrite it with the latest value. |
| Deletes the table entirely | The AMI Publisher may try to rebuild the table, but large data volumes can cause job failure. |
| Deletes the object storage bucket | The AMI Publisher job will fail. |
| Deletes the user or changes user permissions | The AMI Publisher job will fail. |
| Needs to reload the entire table | Full table reload is possible, but a support ticket must be opened. |
| Needs regular backups of delivered data | Not required unless customer has advanced or specific needs, such as protection against rare regional outages. |
| Builds custom solutions or modifies data in another copy | All customer-built solutions or data modifications are solely the customer’s responsibility. |