Tivoli Asset Discovery for Distributed, Version 7.2    

Audit reports

Audit reports provide information pertaining to processor value unit (PVU) capacity per product under full and subcapacity licensing terms for a specific period of time. Customers using PVU-based products are obliged by a license contract to generate and sign audit reports regularly (at least every three months) and store them for auditing purposes.

By default, audit reports are generated every month, but you can also change this schedule at anytime by setting the start date and reporting frequency in the IBM PVU Audit Reports > Reporting Options window. Moreover, you can create reports only for a time period that has already occurred. Note that if you create a report, for example for yesterday, according to the default configuration the report will be in the Running state because there is no aggregated data available for yesterday (you will not be able to view the report).

Note: When data has been verified and the report is Ready, sign the report to certify that the data is complete and accurate. Signed audit reports can only be deleted after they are two years old. Subcapacity terms require you to keep the reports for at least two years to support and document the customer's ongoing compliance with subcapacity licensing terms. They would be produced in the event of an audit, for example a compliance audit by IBM or an internal customer audit. There is no specific format the reports should be kept in. They can be either hard copy or software copy files.

Audit report timeline

Timeline that shows what happens after the period covered by an audit report

  1. An audit report presents the information about PVU capacity per product collected from the agents during the period of time that is determined by the audit report start (A) and end (B) date. See: Viewing audit reports.
  2. A finalization period (from B to C) is a number of calendar days (between 1 and 10) after the audit report end date (B) during which agents can continue to gather and report information relevant to the report in case they were not able to contact the server right away. See: Setting the finalization period.
  3. A grace period (from B to D) is a number of days (bigger than the finalization period but not bigger than 30 days) after the audit report end date. The report is expected to be signed after the end of the finalization period but before the end of the grace period. When the grace period lapses (D), audit report notification subscribers will receive daily notifications until the report is signed. See: Setting the grace period, Adding e-mail subscribers.
  4. Once the report is ready to be signed, you should verify its correctness. See: Verifying audit reports.
  5. Sign the report if it matches the processor core capacity, as measured in PVUs, available to the licensed products. See: Signing audit reports.
  6. Once the report is signed, it is archived, and it can be deleted only after two years. See: Deleting audit reports.

Topic type Concept topic    
To locate this topic in the table of contents, click Show in Table of Contents on the toolbar  (Show in Table of Contents)