Entity Attribute File Name Conventions

All entity attribute data files transferred to Oracle Utilities must follow a standard naming convention. File name components enclosed in angle brackets (<>) must be populated. File name components enclosed in square brackets ([]) are optional and can be included or left out. Any components without brackets must be part of the file name and should not be changed.

Entity Attribute Definition File:

opwr_<utility>_[res_|non_res_]<specification version number>_core_entity_attribute_definition_<yyyyMMddHHmmss>.gz

Entity Attribute File:

opwr_<utility>_[res|non_res_]<specification version number>_core_entity_attribute_<yyyyMMddHHmmss>.gz

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.
  • Population Token: An abbreviation that indicates whether the data is applicable to residential (res) or non-residential (nonres) customer populations. For the non-residential category, there are additional segmentations available to designate Small and Medium Business populations (nonres-smb) or Large Commercial Industrial populations (nonres-lci). Consult your Service Delivery Manager to determine which is the most appropriate population token if you need to use additional segmentations.
  • 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 Entity Attribute Data Version History.
  • Data Type: The filename must contain the words core_entity_attribute or core_entity_attribute_definition to indicate the type of data it contains.
  • Date: The date that the file was generated, in the format yyyyMMddHHmmss.
  • File Extension: All data files must be sent in tab-delimited text in .tsv or .txt format. 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 Name Examples

Suppose the specification version number of the document is v1-0-0, your utility is named "The Great Energy Company”, and your data applies to a residential customer population. An example of your utility’s entity attribute definition specification file name would be as follows:

opwr_gec_res_v1-0-0_core_entity_attribute_definition_20210316131415.gz

An example of your utility’s entity attribute specification file name would be:

opwr_gec_res_v1-0-0_core_entity_attribute_20210316131415.gz

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

opwr_gec_ res_v1-0-0_core_entity_attribute_definition_20210316131415.pgp

An example of your utility’s entity attribute specification file name would be as follows:

opwr_gec_res_v1-0-0_core_entity_attribute_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.res.v1.0.0.core.entity.attribute.definition.20210316131415.gz

Back to Top