Urjanet FAQs

For the latest Provider List, please download the attachment at the bottom of this page.

On all manage, track, and enroll pages on the Portal, there is the option to filter the data by one or multiple conditions using various types of logic. These filters can be used once to quickly find specific accounts, or saved for later use to establish a view of a subset of accounts.

Creating a filter

On the page, click show filter.

In the first drop-down, choose the relevant field.

In the second drop-down, choose the logic condition that applies to your filter.

Depending on the condition selected, the filter value box will remain. Enter the value by which to filter the data in the box.

To add more conditions to your filter and narrow down your search, press the + button. Multiple conditions can be added to a single filter.

To remove conditions from a filter, click the blue x icon.

Saving a filter

Click the floppy disk icon to save a filter you are currently using.

In the dialog that appears, enter the name for your new filter. The filter conditions are visible and can be edited here.

Press Save. The filter is now available via the drop-down menu.

Using existing filters

On the page, simply choose the desired filter from the filter drop-down menu.

Switch to another filter using the same drop-down.

To return to the full data list, you may need to reload the page.

Copying, editing, and deleting existing filters

On the page, click show filter.

Press the gear icon to manage filters.

By default, no filter is selected, and you can create a new filter from the dialog that appears.

In the Filters list on the left, click on the existing filter you want to manage.

To copy a filter, press the Copy button, and press Yes in the pop-up dialog. The filter copy now appears in the Filters list with a number in parentheses. Select the copy to rename it and edit its conditions.

To edit a filter, change the name and details as desired and press Save.

To delete a filter, press the Delete button, and press Yes in the pop-up dialog.

Field definitions for the Manage Account page

Station

A utility account will be in one of four different stations in the Urjanet Portal: Requests, Enrolled, Discovered, and Unsubscribed

Requests - When accounts are first submitted, they appear in the Request station. If a statement is successfully extracted for the account, it becomes an enrolled account. If a statement is not successfully extracted, it remains in Requests for follow up.

Enrolled - Accounts in the Enrolled station are monitored by Urjanet and serve as an inventory of accounts the customer expects to receive.

Discovered - Accounts in the Discovered station are accounts that have not been specifically submitted by the customer but found by the Urjanet system behind an existing extraction channel. Data for discovered accounts are not delivered to the customer.

Unsubscribed - Accounts in the Unsubscribed station have been removed from a customers inventory of accounts they expect to receive.

Delivery

Indicates if an account is set to deliver or not set to deliver

Provider Name

The public name of a utility provider

Service Types

The accounts commodity type (ex. Electric, water, natural gas)

Normalized Account Number

The account number given by the utility provider stripped of special characters, spaces, and leading zeros

History

Indicates if an account was submitted with the request for historical statement extraction.

Submit Date

The date an account is submitted to the Portal

Enroll Date

The date an account is enrolled in the Portal

Last Delivered

The date a statement for an account was last delivered

Latest Orphan Source Delivered Date

The date a statement for an account was last delivered as an orphan

Latest Source Type

The source type of the last statement extracted for an account (ex. PDF, HTML)

Latest Total Bill Amount

The total bill amount of the last statement extracted for an account

Latest Interval End

The interval end date of the last statement extracted for an account

Given Provider Name

The utility provider name submitted by the customer through an activation form

Account Number

The account number given by the utility provider

Summary Account Number

The summary account number given by the utility provider

Provider Alias

Urjanets internal utility provider name

Provider Classification

The provider classification is how Urjanet attempts to track the role a utility provider has played on invoices over the course of Urjanets history of extracting an account. The provider classification field is not intended to tell the difference between supply and delivery. A primary provider issues the invoice and a secondary provider is only mentioned or cited via pass-thru charges. If Urjanet has seen a provider play both of these roles for an account over time, its provider classification will be both.

Extraction Channel

Urjanets internal term for the means by which an account is extracted. It includes the username, password and utility providers URL

Extraction Channel Status

The status of the last extraction attempt

Extraction Channel Modified

The date the last time an extraction channel was modified

Login

The username associated with an extraction channel

Submit ID

An Urjanet-generated ID that identifies the batch of accounts submitted in an activation form

First Extract Date

The first date an account is successfully extracted

Unsubscribe Date

The date an account is last unsubscribed

Enrollment Status

The status of an account as it progresses from a submitted Request to an enrolled account. Enrollment status can never move backwards - it is a record of the furthest this account has been in the enrollment flow over its entire history

Finalled

Indicates if a statement has clearly stated that the account is finalled

Last Extracted

The date an accounts last attempted extraction

Last Successful Extraction

The date of an accounts last successful extraction

Last Successful Channel

The last successful extraction channel

Last Extraction Status Date

The date an accounts last attempted extraction

Last Extraction Status

The status of the last extraction attempt.

Last Extraction Status Modified

The date the last time the Last Extraction Status field changed

Monitoring Status

The status of an account that is manually assigned by Urjanet operations employees.

Failing Event Name

An Urjanet-internal event name

Failing Event Code

An Urjanet-internal event code

Next Expected Post Date

An Urjanet-estimated date based on the Next Expected Confidence for when the next statement will be available on the website.

Next Expected Due Date

An Urjanet-estimated date based on the Next Expected Confidence for when the next statement will be due

Start To End Avg

The average number of days between the interval start date and interval end date for an account

End To Post Avg

The average number of days between the interval end date and post date for an account

Post To Due Avg

The average number of days between the post date and due date for an account

Next Expected Confidence

An Urjanet-estimated confidence level of an accounts posting predictability

Delivery Updated

The date the last time the Delivery field was updated

E-bill Enrolled

A manually maintained field that indicates if an account is enrolled in e-bill

Latest Due Date

The due date of the last statement extracted for an account

Latest Outstanding Balance

The outstanding balance of the last statement extracted for an account

Message

A message manually maintained by Urjanet operations employees while monitoring accounts

Support Last Modified

The date the Monitoring Status or Message field was last manually updated

Support Member

The last user that manually updated the Monitoring Status or Message field

Modified

The date any field was updated for an account

Modified By

The system or last user that updated a field for an account

Lapsed Days

The number of days since the interval end date from the last extracted statement

Post Days

An Urjanet-estimated number of days until the next estimated post date

Event History

A log of manual and system changes made to an account

CNBD 1-10

Custom fields available for customers to tag accounts with data points not found on statements (ex. region, facility type, etc). Other custom fields include Site Name, Site Code, Customer Name and Customer Code

ENROLLMENT STATUS

Enrollment status is a system-generated status and can never move backwards. It is a record of the furthest this account has been in the enrollment flow over its entire history. Once an account reaches the status "SUCCESSFUL_DELIVERED" its enrollment is complete.

#

Enrollment Status

Status Definition

Owner

Action

1

SUBMITTED

Initial state of account; should automatically proceed

Urjanet

Internal status

2

NEEDS_CREDENTIAL

Account does not have a credential associated with it

Urjanet

Internal status

3

NEEDS_TEMPLATE

Account has a credential but that credential does not have an assigned template

Urjanet

Internal status

4

NOMINATED

Account has a fully provisioned credential which has not yet been run

Urjanet

Internal status

5

FAILED_TO_ACCESS

Extraction returned nothing (could be new website or broken navigation)

Urjanet

Internal status

6

FAILED_LOGIN

The navigation failed at the login step specifically (check user/pass)

Urjanet

Internal status

7

ACCOUNT_MISSING

The credential ran and succeeded in some capacity, but there was no trace of this account

Urjanet

Internal status

8

STATEMENT_MISSING

The credential ran and succeeded, and the account was seen on the website, but we were unable to extract a statement

Urjanet

Internal status

9

STATEMENT_FAILED

A statement was extracted, but was not persisted because of audit failures, storage failures, etc.

Urjanet

Internal status

10

SUCCESSFUL_NOT_ENROLLED

Extraction of account was successful, but the account in question is not subscribed

Urjanet

Internal status

11

SUCCESSFUL_ENROLLED

Extraction of account was successful

Urjanet

Internal status

12

SUCCESSFUL_DELIVERED

Extraction and delivery of account were successful

Urjanet

Internal status

EXTRACTION STATUS

Extraction Status is a system-generated status that is updated each time the Urjanet system polls the utility provider's website for the account.

#

Extraction Status

Status Definition

Owner

Action

1

EXISTS

Initial discovery

Urjanet

Internal status

2

SUCCESS

Extraction was successful

Urjanet

Internal status

3

FAILED_TO_ACCESS_DURING_LOGIN

Navigation failed around the login step, but itisn'ta confirmed login failure (template may not support confirmed login failure)

Urjanet

Internal status

4

FAILED_TO_ACCESS

Navigation wasnt even able to attempt to log in

Urjanet

Internal status

5

ACCOUNT_MISSING

Statements have been extracted before, but the account wasnt seen during the latest extraction

Urjanet

Internal status

6

STATEMENT_MISSING

Extraction saw the account, but the statement itself was missing or we were unable to reach it for some reason

Urjanet

Internal status

7

AUDIT_CHECKSUM

Charges in statement do not checksum correctly

Urjanet

Internal status

8

AUDIT_VALID_USAGE

There is an invalid usage group in the extracted data

Urjanet

Internal status

9

AUDIT_INVALID_INTERVAL

Invalid date interval in the extracted data

Urjanet

Internal status

10

AUDIT_OTHER

Another audit fired while post

Urjanet

Internal status

11

ERROR_DATA_TYPE

Some kind of formatting error occurred during extraction

Urjanet

Internal status

12

ERROR_MISSING_REQUIREMENT

A required field was not extracted (e.g. usage group with no unit)

Urjanet

Internal status

13

ERROR_STORAGE

Something went wrong when trying to store statement, such as a database timeout

Urjanet

Internal status

14

ERROR_MODEL_COLLISION

The grouping of the extracted data didnt make sense, or a group was created that was not part of our core model

Urjanet

Internal status

15

CUSTOMER_REJECTED_HTML

Customer-enabled audit to reject HTML caused the latest statement to be rejected

Urjanet

Internal status

16

LOGIN_FAILURE

Confirmed failure while attempting to submit credentials (check that user/pass are correct)

Urjanet

Internal status

17

TRACKED_ACCOUNT_SKIPPED

Account has been assessed against its Next Expected Post date and the system indicates that the newest statement is already in Urjanet's possession and doesn't need to be extracted again. This status only applies to accounts with a Next Expected Confidence of MEDIUM or HIGH.

Urjanet

Internal status

18

ACCESS_CHANNEL_SKIPPED

All accounts in an access channel have been assessed against their Next Expected Post dates and the system indicates that the newest statements are already in Urjanet's possession and don't need to be extracted again. This status only applies to accounts with a Next Expected Confidence of MEDIUM or HIGH.

Urjanet

Internal status

19

ERROR_WEBSITE_PROBLEM

The website is under maintenance or the website is inaccessible during the navigation process

Urjanet

Internal status

20

TRACKED_BILL_NOT_YET_AVAILABLE

The account and new statement date is available but the bill is not yet available on the website.

Urjanet

Internal status

MONITORING STATUS

Monitoring status is manually assigned by our internal operations employees while they monitor the health of accounts.

#

Monitoring Status

Status Definition

Message

Message Definition

Owner

Action

1

AGED_BILL

Account has not posted a recent bill

[0] Statements are current. No new statement available for over 45 days

Most recent bill has been acquired and no new bill has been posted for at least 45 days

Customer

Review account and unsubscribe the account if it no longer needs to be processed

2

AGED_BILL

Account has not posted a recent bill

[1] Statements are current. No new statement available for over 60 days

Most recent bill has been acquired and no new bill has been posted for at least 60 days

Customer

Review account and unsubscribe the account if it no longer needs to be processed

3

AGED_BILL

Account has not posted a recent bill

[2] Statements are current. No recent activity. Candidate for INACTIVE

Most recent bill has been acquired and no new bill has been posted in over 90 days

Customer

Review account and unsubscribe the account if it no longer needs to be processed

4

NAVIGATION_FAILURE

An issue with the navigation template prevented successful extraction

Event ID:

Ticket has been opened to resolve issue

Urjanet

5

NAVIGATION_FAILURE

An issue with the navigation template prevented successful extraction

Temporarily using DAQ methods

Using alternative methods to retrieve data

Urjanet

6

BLOCKED

Access to the account is blocked by the website

Provider Acquistion/navigation error:

Website issues prevent acquisition of bill

Customer

Review account and follow up with utility provider about website issue

7

BLOCKED

Access to the account is blocked by the website

Provider source type rejected from delivery

Bill source type available on the website is blocked from delivery

Customer

Review account and follow up with utility provider about website issue

8

DEACTIVATED

Account not required in delivery

Confirmed AccessChannel is disabled ID:

Account is no longer getting extracted and will not be delivered

Urjanet

9

DEACTIVATED

Account not required in delivery

User deactivation ID:

Account will no longer be delivered per user request

Urjanet

10

DEACTIVATED

Account not required in delivery

Paper restored/Ebill disabled ID:

Account will no longer be processed via web job

Urjanet

11

DEACTIVATED

Account not required in delivery

Account Number was submitted in error

Account was initialy submitted in error and will no longer be delivered

Urjanet

12

DEACTIVATED

Account not required in delivery

Account Number change

Account number has changed and will no longer be delivered

Urjanet

13

ACCOUNT_MISSING

Requested account is missing from the website

No record of account under login

Account number cannot be found under the login

Customer

Verify account exists on website and unsubscribe the account if it no longer needs to be processed

14

ACCOUNT_MISSING

Requested account is missing from the website

No record of account in Site

Account number cannot be found on the website

Customer

Verify account exists on website and unsubscribe the account if it no longer needs to be processed

15

FINALLED

Account is closed

Confirmed; Finalled status on website. Processed the lastest read date.

Account has been closed and there are no new bills available

Customer

Review account and unsubscribe the account if it no longer needs to be processed

16

INACTIVE

Account exists but is inactive (no bills or activity for >100 days)

Confirmed; No new statement available for over 90 days:

Most recent bill has been acquired and no new bill has been posted in over 90 days

Customer

Review account and unsubscribe the account if it no longer needs to be processed

17

INACTIVE

Account exists but is inactive (no bills or activity for >100 days)

Inactive status on website

Provider considers the account inactive; ost recent bill has been acquired and no new bill has been posted in over 90 days

Customer

Review account and unsubscribe the account if it no longer needs to be processed

18

LOGIN_FAILURE

A login failure is confirmed for this account

ID:

Account cannot be accessed due to a login failure

Customer

Login credentialsdon'twork, change login credentials in portal

19

LOGIN_FAILURE

A login failure is confirmed for this account

Security question (answer) required.

Account cannot be accessed due to incorrect or incomplete security question(s)

Customer

Login credentialsdon'twork, change login credentials in portal

20

LOGIN_UPDATED

The credentials have been updated after failing but have not been tested since

ID:

Credentials have been updated after failing but have not yet been tested

Urjanet

21

ENROLLMENT_EVENT

Requested account is the enrollment stage

[0] Currently In Template Development ID:

New template being developed to enroll the requested account

Urjanet

22

ENROLLMENT_EVENT

Requested account is the enrollment stage

[0] Pending. Template exists. Request submitted.

Requested account to be reviewed

Urjanet

23

ENROLLMENT_EVENT

Requested account is the enrollment stage

[1] Credential and Provider mapped. Awaiting run results.

Requested account is mapped to the correct provider and is awaiting the next extraction run

Urjanet

24

ENROLLMENT_EVENT

Requested account is the enrollment stage

[2] Failed to access. Cannot confirm credentials or account(s).

Requested account cannot be accessed

Customer

Verify account exists on website and send us navigation steps to view that account if it already exists

25

ENROLLMENT_EVENT

Requested account is the enrollment stage

[3] Requires Ebill Enrollment

Requested account requires Ebill enrollment to be processed

Customer

Ebill enrollment required to view the bills. So please enroll to ebill

26

ENROLLMENT_EVENT

Requested account is the enrollment stage

[4] Confirmed Login failure ID:

Requested account cannot be accessed due to a login failure

Customer

Login credentialsdon'twork, change login credentials in portal

27

ENROLLMENT_EVENT

Requested account is the enrollment stage

[5] No record of account under login.

Requested account cannot be found under provided login

Customer

Not able to view account under login, if you can then give us navigation steps

28

ENROLLMENT_EVENT

Requested account is the enrollment stage

[6] Account discovered, no statement accessible.

Requested account found but statement cannot be accessed

Customer

No new bill. Intimate us when a new bill is posted or resubmit account when a new bill is posted

29

ENROLLMENT_EVENT

Requested account is the enrollment stage

[7] First statement run. Blocked by extraction events.

Attempted extraction for requested account and follow up is needed

Urjanet

30

ENROLLMENT_EVENT

Requested account is the enrollment stage

[8] First statement successful, account not yet enrolled.

Extraction of the first bill is successful but follow up is needed to enroll the account

Urjanet

31

ENROLLMENT_EVENT

Requested account is the enrollment stage

[9] First statement successful, account enrolled. Account not yet delivered.

Extraction of the first bill is successful but account needs to be delivered

Urjanet

32

ENROLLMENT_EVENT

Requested account is the enrollment stage

[10] First statement successful, account enrolled. Account delivered.

Extraction of the first bill is successful and account has been delivered

Urjanet

33

ENROLLMENT_EVENT

Requested account is the enrollment stage

[11] Login updated.

Credentials have been updated after failing but have not yet been tested

Urjanet

34

DAQ_PRODUCTION

Account is in production via direct acquisition (DAQ)

Account will serviced indefinately via direct acquisition (DAQ)

Account will serviced indefinately via direct acquisition (DAQ) as opposed to a web job

Urjanet

35

PRODUCTION

Account is in production

Statements are current. Processed the latest statement.

Most recent bill available has been processed

Urjanet

36

PRODUCTION

Account is in production

Statements are current. Processed the latest statement. 60 day read cycle.

Most recent bill available has been processed and has a 60 day read cycle

Urjanet

37

PRODUCTION

Account is in production

Statements are current. Processed the latest statement. 90 day read cycle.

Most recent bill available has been processed and has a 90 day read cycle

Urjanet

38

PRODUCTION

Account is in production

Statements are current. Processed the latest statement. 365 day read cycle.

Most recent bill available has been processed and has a 365 day read cycle

Urjanet

39

PRODUCTION

Account is in production

Statements are current. Processed the latest statement. Abnormal day read cycle.

Most recent bill available has been processed and has an abnormal read cycle

Urjanet

40

PRODUCTION

Account is in production

Statement presented under alternate account number:

There is a change in account number and we provide with an alternate account number extracted for the existing account number in case the alternate accounts are easily traceable.

Urjanet

41

PRODUCTION

Account is in production

Temporary navigation interruption. Retry within 24hrs. No other action required.

Will attempt to process the most recent bill again within 24 hours

Urjanet

42

PRODUCTION

Account is in production

Exclusively a DAQ account; no polling schedule exists

Most recent bill provided has been processed via direct acquisition (DAQ)

Urjanet

43

PRODUCTION

Account is in production

Redundant enrollment

Deprecated

Urjanet

44

TEMPLATE_FAILURE

An issue with the template prevented successful extraction

Event ID:

Most recent bill available has not been processed due to a template issue

Urjanet

45

TEMPLATE_FAILURE

An issue with the template prevented successful extraction

Mapping event ID:

Most recent bill available has not been processed due to a template issue

Urjanet

46

TEMPLATE_FAILURE

An issue with the template prevented successful extraction

Not polling regularly ID:

Deprecated

Urjanet

47

TEMPLATE_FAILURE

An issue with the template prevented successful extraction

Template ticket; using DAQ methods

Most recent bill provided via direct acquisition (DAQ) has not been processed due to a template issue

Urjanet

48

UNKNOWN

Account's status is not yet set

Awaiting initial review

Account awaiting initial review

Urjanet

49

SOURCE_FORMAT_CHANGE

The invoice source changed its format

Event ID:

A ticket has been created to follow up

Urjanet

50

ACCOUNT_NUMBER_CHANGE

The account number has changed

Account Number change

Extraction should continue under the new account number

n/a

Default filters to help aid in maintaining accounts on the Requests and Account Status pages

Saved Filters on the Requests page

Login Failures - Requests with monitoring status of ENROLLMENT_EVENT and Message that starts with "4 Confirmed Login failure ID:..."eBill Enrollment - Requests with monitoring status of ENROLLMENT_EVENT and Message that starts with "3 Requires Ebill Enrollment"Account Missing - Requests with monitoring status of ENROLLMENT_EVENT and Message that starts with "5 No record of account under login."No Bill - Requests with monitoring status of ENROLLMENT_EVENT and Message that starts with "6 status in enrollment event"

Saved Filters on the Account Status page

Login Failures - Monitoring status of LOGIN_FAILUREAccount Missing - Enrolled accounts with monitoring status of ACCOUNT_MISSINGInactive Accounts - Enrolled accounts with monitoring status of INACTIVEFinalled - Enrolled accounts with monitoring status of FINALLEDAGED_BILL - Enrolled accounts with monitoring status of AGED_BILLBLOCKED - Enrolled accounts with monitoring status of BLOCKED

Access the Portal at portal.urjanet.net.

Navigate to the Enroll page.

this guide

Click on Forms.

Find your form in the list (by default, they are sorted with the most recent submission at the top).

Check the Status field for the Activation Form. Some accounts may still need validation from the user, which means they have not been enrolled yet. For more details on validating Activation Forms, see .

IN-PROGRESS indicates missing credential fields, required provider mapping, or duplicate accounts that need resolving.

INCOMPLETE indicates missing account fields that are required to enroll accounts.

PROCESSED indicates the accounts in the form were enrolled successfully, or the Activation Form was manually finalized by the user.

Click on the Submit ID and copy it.

Click on requests.

Click show filter.

Choose Submit ID, Equals, paste the Submit ID, and press enter.

If the accounts are still being enrolled, they will appear here. If there is a problem with the accounts, the Message column will have more information.

If the Message column does not appear, either press All and scroll to the right in the list, or press Configure and select Message.

If the accounts do not appear here, navigate to the account status page under the manage tab.

Repeat steps 8 10 to find your accounts in the list and see any Messages associated with them.

The columns in this list provide a wealth of information regarding the status of accounts including the enroll date, import history, first delivery date, most recent delivery date, and more.

Accounts can be unsubscribed via the Portal or using an Activation Form. The steps below are for using the Portal. To use an Activation Form, follow this guide and be sure to properly fill out the Request Type and Deactivate Instructions fields properly.

Steps

Access the Portal at portal.urjanet.net

Click on the number below enrolled.

use a filter

Check the box next to the relevant accounts in the list and click the Edit button. To quickly narrow down the list of accounts by a given attribute, .

In the dialog that appears, press Unsubscribe. A second dialog will appear; press Unsubscribe again to confirm.

A confirmation will appear at the top of the page. The accounts can now be found in the unsubscribed section of the Account Status page.

Access the Portal at portal.urjanet.net

Navigate to the credentials page under the manage tab.

Check the box next to the account in the list and click the Edit button. To quickly narrow down the list of accounts by Credential ID, Provider, or Username, use a filter.

In the dialog that appears, scroll down until you see the Username and Password fields.

Toggle Show Passwords to on. The username and password login credentials are now visible and can be edited.

To save changes to the credentials, press the Update button

September 16, 2019

Urjanet has made an update to its data load scripts for customers using MySQL. This is a small change to prevent incomplete data loads in the event of an error during the load process. If you are using MySQL, we recommend updating the Urjanet MySQL Data Load Post script to the latest version attached to this article ( UrjanetDataLoad_Post.sql ).

Urjanet discovered that data values could exceed a SQL field length constraint without causing the import to fail or presenting data load errors. This resulted in an unpredictable data load for the entire delivery file when a constraint violation existed.

Urjanet has updated the MySQL load script to error out if an issue exists during the load process. This script features error messages to provide some visibility into the reason for failure.

Adding meters to the data feed is simple. With the information below, Urjanet can begin accessing interval data on the Utility Provider's website. All aggregated data will automatically be included in the scheduled delivery.

Utility Provider

Account Number

Meter Number

Utility URL*

Username

Password

There are 2 options for providing this data to Urjanet:

API

New credentials can be submitted electronically via the Utility Data Service API. Additional instructions on how to use the Urjanet API can be provided upon request. Activation of individual meters must be completed via a Zendesk support ticket at this time.

Customers: Contact your project manager

Non-Customers: Contact your sales representative

Activation Form

Activation can also be completed manually via an Excel spreadsheet. This spreadsheet can be sent securely via a support ticket on urjanet.zendesk.com. See attachments for a sample form.

Deactivating Meters

For instructions on how toremove meters from your data plan, please visit Deactivating Meters.

Notes:

Utility URL: A utility may have several different URLs which can be used. Specifying this URL helps identify the specific portal containing your interval data.

Interval Data Flag:Indication that the data requested is Interval Data.

Attachments:

Overview

All new and modified data is delivered once daily via a standard CSV file. Data is delivered directly to an FTP/sFTP location, which can be hosted by the Customer or Urjanet. From there, data is available for ingestion at the customer's discretion.

Customer FTP Setup

Customers often prefer to have Urjanet deliver data directly to their own FTP server. The following data is required to enable this delivery:

FTP Address

Filepath

Username

Password

Urjanet FTP Setup

Instructions on how to setup delivery to an Urjanet hosted sFTP location can be found Here.

Data Contents

The fields below make up the Utility Interval Data file. All fields are mandatory, and will be populated for every interval data record.

Provider:Urjanet's alias for the utility provider.

Account Number: Billing identifier for the meter. A single billing identifier can have many distinct meters.

Meter Number:Service identifier for the measurements.

Timezone:Timezone for the utility's operations.

End Timestamp:Date/time of the interval reading.

Duration:Length of time between readings in seconds (s).

Unit& Value: Column named by Unit of Measure for the meter reading. Value indicates reading for the period. For Example:

Unit (Column) = kW

Value = 12.8

(For the current set of available units, contact [email protected])

Maintenance Window

Urjanet reserves each Sunday for system maintenance. Any data collected on Sunday will be included in the Monday delivery file.

Sample Data (CSV)

We are making a change to our interval data delivery to address situations where a utility updates readings for different units at different times.This may result in the same data intervals being sent more than once.Urjanet will implement this change onTuesday, September 4.

Background:Currently, our system identifies the most recent interval for which we have extracted data for a unique combination of Provider, Account, and Meter (PAM). During extraction, we check our database to find this "latest interval end" of the most recent data for that PAM. Then, we look for any newer data on the provider's website after this most recent interval.

Issue:If a given PAM contains multiple units of measure, and values are only present through a given interval for a subset of those units, our system is currently using the maximum interval end for any unit as the latest interval end. When we next extract data for that PAM, we will look for data from this max interval end. This means we are not currently backfilling previous intervals with readings that were provided later by the utility.

Proposed change:Urjanet will include the Unit as part of a unique Provider-Account-Meter combination. If a given interval is missing data for any unit of measure, Urjanet will consider the prior interval to be the "latest interval end" for that PAM and look for updated data during our subsequent extraction.This will result in the same data interval being delivered more than once with updated datato fill in the remaining units of measure.

Our aim is to provide more complete, gap-free data, even when the utility website updates readings for different units of measure at different times.

Please reach out to your Urjanet Project Manager if you have any questions.

Monitoring

Urjanet keeps track of your meters. If a meter fails to report data for 72 hours or more, Urjanet's operations team will investigate to assess the root cause. Failures are broken into 3 categories:

Utility: A factor related to the utility's behavior is preventing capture of data. This includes website maintenance periods and missing data from the utility.

Customer: Urjanet needs customer action to restore the data feed. This could include login failures or additional authorizations needed to access data online.

Urjanet: Urjanet is actively working to restore the data feed. This could include changes to the provider's website or data format.

A reportdetailing the status of each meter can be provided upon request.

If 72 hours have elapsed and the cause of a delay is still unknown, please contact Urjanet Support by emailing [email protected].

Gaps

On occasion, interval data published by the utility will contain gaps. This could be due to failures in the meter infrastructure or downtime in the utility's website. At a later date, the utility may fill gaps in historical data. When this occurs, the utility does not notify Urjanet or the customer.

Urjanet's automation is always looking for the most recent data. Each day, the system will pull data for the newest period. When a historical gap is filled, there is no way for Urjanet to automatically pull this data.

If this situation occurs, a special request can be made to extract all historical data. Urjanet will perform a one-time look-back and deliver any new data in the regularly scheduled delivery.

To remove meters from your Urjanet Utility Interval Data plan, you will need to turn off the login used to access the data online. This can be accomplished in 2 ways:

Zendesk Ticket

Submit a request to Urjanet containing the following information:

Provider

Provider URL

Username

API

Isolate the Credential ID (ex. Customer_1-GeorgiaPower_1)

Post an Update to this credential

Set Enabled to 'FALSE'

Note: This action will turn off the data feed for all meters contained within the utility login.

Urjanet Utility Interval Data is a Data-as-a-Service solution that provides automated daily deliveries of prior-day interval meter readings for electricity, natural gas, and water usage.

The data is provided in intervals determined by the utility, which can range from 5 seconds to 60 minutes. Data is accessed directly from the utility providers customer portal and delivered in a CSV file format to a designated FTP/sFTP location, hosted by either the customer or by Urjanet.

Urjanet Utility Interval Data supports 70 electricity, natural gas, and water utilities worldwide, providing more coverage than the Green Button Standard. Urjanet Interval Data requires no hardware installation, making it a cost-effective energy and facilities management solution.

Data Access

Urjanet accesses interval data using the customers Utility Portal login information. Using the username and password, Urjanets automated integrations download and process new data on a daily basis.

There are 2 basic requirements for Urjanet to access interval data:

Smart Meter: Traditional meters are measured on a monthly cycle. Interval data is made up of many small incremental readings. Collection of this data requires a Smart Meter, which automatically transmits these readings to the utility.

Web Accessible: While most utilities use smart meters to collect interval data from their customers, a limited number make this data available to their customers. A utility must post interval data either on its website or through a web service for Urjanet to access.

Data Availability

Urjanet aggregates data from utilities 1x per day. All new data is collected, stored in Urjanet's platform, and delivered in the daily delivery file.

While new data is sought daily, utilities can be inconsistent in their data posting habits.Posting interval data is ancillary to a utilitys core business. New data is typically published once per day, but posting times are not guaranteed, updates are made without notification, and service outages can last for long periods.

If you have a question about specific data that Urjanet has missed, please submit a request via [email protected].