Skip to content. | Skip to navigation

You are here: Home Managing Audits Repeating Audits-EnergyCAP Logic for Database Table Updates

Repeating Audits-EnergyCAP Logic for Database Table Updates

Audits may be run as frequently as desired in EnergyCAP.

When an audit is first run for a new bill, a failed audit result or results will populate the BillMessageLog table in the EnergyCAP database. Information from repeat audits is appended to the BillMessageLog table, with updates per the following logic. 

NOTE: The Status column indicates the status of the bill prior to running the repeat audit.

CONDITION STATUS RESULT
Audit X was run once, it passed. Now it is run again after the bill has been edited and it fails. N/A (passed) Bill(s) will get problem messages.
Audit X was run once, it passed. Now it is run again in a different Audit Group with a different setting.  It fails. N/A (passed) Bill(s) will get problem messages.
Audit X was run once, it failed.  Now it is run again with the same audit group, same settings. PROBLEM The audit results will be displayed. However no new bill messages are inserted into the database, as there were no changes to the audit messages.
Audit X was run once, it failed.  Its status is ‘problem.’  Now it is run again with the same audit group, different settings.  It fails again. PROBLEM Nothing happens as long as the problem message is the same. If the message is different, a new bill message is created. For example: Bill failed by 100% first time, second time it failed by 150%. This will create an additional bill message leaving the other message current and a ‘problem’.
Audit X was run once, it failed.  Its status is ‘problem.’  Now it is run again with the same audit group, different settings.  This time it passes. PROBLEM All the bill messages from before remain unaltered unless the actual message is different.
Audit X was run once, it failed. Now it is run again with the same audit group, same settings. IGNORE The same results are returned in the display window but the bill messages in the database remain ignored in the database.
Audit X was run once, it failed.  Now it is run again with the same audit group, different settings.  It fails again. IGNORE If you run the new settings and the audit fails, the failures display with no updates to bill messages. If you run with new settings and it passes, it does not update bill messages.
Audit X was run once, it failed.  Now it is run again with the same audit group, different settings.  This time it passes. IGNORE Nothing happens to the current bill messages but there are no errors displayed on the pop-up window.
Audit X was run once, it failed.  Now it is run again with the same audit group, same settings. FIXED If there are no changes made to the bill to actually ‘fix’ it the audit will re-mark that message as a problem. If they are actually fixed and the audit does not return the same results the problem remains fixed.
Audit X was run once, it failed. Now it is run again with the same audit group, different settings.  It fails – because it was edited. FIXED The problem remains fixed but a new bill message log is inserted with the new failure problem values.
Audit X was run once, it failed.  Its status is ‘fixed.’  Now it is run again with the same audit group, different settings.  It passes this audit group. FIXED Nothing happens. The problem remains fixed.
Add comment
(Required)
Tell us your name.
(Required)
(Required)
(Required)
Enter the word