Account Data File Name Conventions

All account data files transferred to Oracle Utilities must follow a standard naming convention. Your Delivery Team will work with you to define the appropriate file names for any files that must be transferred.

File name components enclosed in angle brackets (<>) must be populated. Any components without brackets must be part of the file name and should not be changed.

Main Account File:

opwr_<utility>_<specification version number>_billing_account_<yyyyMMddHHmmss>.<gz or zip>

Person Address File:

opwr_<utility>_<specification version number>_billing_account_address_<yyyyMMddHHmmss>.<gz or zip>

Service Agreement Service Points File:

opwr_<utility>_<specification version number>_billing_account_sa_sp_<yyyyMMddHHmmss>.<gz or zip>

This naming convention is made up of the following components:

  • Prefix: The opwr prefix, which is the standard abbreviation for Oracle Utilities Opower.
  • Utility Identifier: A three- or four-character code that identifies the utility sending the file. Your Delivery Team will work with you to choose the utility code early in the implementation process. The code needs to be a unique identifier for the utility in the Oracle Utilities Opower system. For example, “The Great Energy Company” might have an identifier of gec.
  • Specification Version Number: A three-digit version number of the data transfer specification. Each digit must be separated by a hyphen (-) and not a period or an underscore. This must match the latest number shown in the Specification Version Number column in Account Data Version History.
  • Data Type: The filename must contain the phrase billing_account to indicate the type of data it contains. As shown in the file name examples above, additional data type components may be required depending on which account file is being sent.
  • Date: The date that the file was generated, in the format yyyyMMddHHmmss.
  • File Extension: All files should be gzipped and should end with .gz, or be zipped and end with .zip. If you choose to PGP encrypt your files, then the .pgp extension should be used. In the case of PGP encryption, compression is not required since the encryption process includes file compression. Files can be up to one gigabyte compressed, or up to four gigabytes uncompressed.

Back to Top

File Naming Example

Suppose the specification version number of the document is v2-0-0 and your utility is named "The Great Energy Company.” An example of your utility’s file name would be as follows:

opwr_gec_v2-0-0_billing_account_20210316131415.gz

Suppose your utility is using PGP-encrypted files. An example of your utility’s file name would be as follows:

opwr_gec_v2-0-0_billing_account_20210316131415.pgp

Back to Top

Additional Notes

The filename must not exceed 183 characters and must not contain a period (.) unless the period comes right before the file extension. The Oracle Utilities Opower file reception system considers the first period in the file name to be the beginning of a file extension. For example, the following file name is invalid and cannot be processed:

opwr.gec.v2.0.0.billing.account.20210316131415.gz

Back to Top