General

How to interpret KPIs

This report makes heavy use of the KPI style visualization. The KPIs have descriptions of what they are showing and also indicate if a higher or lower result is desirable based on the indicator color. A few examples:

KPI with a Relative calculation, note that this indicates that 266 is 88.7% of the new proof added for the month of September.

KPI with a Month-Over-Month calculation, comparing September to August. This indicates that there are 5 fewer labels with attached proof, which we deem a negative movement.

KPI with a Month-Over-Month calculation, comparing September to August. This indicates that there are 184 more closed requests, which we deem a positive movement.

Proof collection

This area contains the amount of proof collected in 4 key categories for the month noted: TaskSync proof, Hypersync proof, Livesync proof, and manually uploaded proof. Manually uploaded proof is always red because we view manual proof uploads as unfavorable.

Proof reuse

Labels with Proof - Active labels with at least one piece of attached proof
Labels linked to Controls - Percentage of labels that have a link to at least one control

Proof automation

This gauge denotes the amount of proof uploaded this month that was collected from automated sources. This includes any proof that was not manually uploaded.

Savings

This area explains how much time is saved with automated proof collection in Hyperproof and the estimated time to collect manual proof. The time savings/cost are calculated using separate rates for Hypersync, Livesync, Tasksync, and manual proof, multiplying that by the ‘blended rate’ of $125 per hour for the resource collecting manual proof.

Hourly savings with automation is generated by calculating the time saved for each automation type and adding the totals together. Use the following calculation methods to find the hourly savings with automation by automation type.

Task Sync

(number of new pieces of proof collected by task sync processes) * (an estimated .15 hours or 9 minutes per task.) = X hours rounded to the nearest whole number.

140 * (9 minutes) = 21.45 hours (rounded to 21)

LiveSync

(number of new pieces of proof collected by LiveSync processes) * (an estimated 0.5 hours or 30 minutes per LiveSync.) = X hours rounded to the nearest whole number.

20 * (30 minutes) = 10 hours

Hypersync

(number of new pieces of proof collected by Hypersync processes) * (an estimated 0.5 hours or 30 minutes per Hypersync.) = X hours rounded to the nearest whole number.

20 * (30 minutes) = 10 hours

Controls

Management

This section is specifically filtered only for Implemented Controls. When the KPI says of Controls it’s referring to implemented controls.

Multi-User Controls - Controls with 5 or more users who are members of the control
Controls with Hypersyncs - Controls that have a Hypersync linked directly to the control, or indirectly to a label where that label is linked to the control
Automatically Tested Controls - Controls with a Hyperproof automatic control test

The control automation KPIs are based on the automation status setting on the control
The control automation gauge displays the percentage of implemented controls that are at least partially automated

Risks

Risks with Mitigating Controls - Risks that have at least 1 linked control

Audits

All request statistics are based on requests attached to audits in any status other than completed in Hyperproof.

Completed Audits - Audits in the Completed status. Completed audits can't be Archived.
Requests linked to Controls - Active audit requests that have a direct link to at least one control or an indirect link via a label.
Incoming Requests - New requests that were added this month.
Open Requests - Requests that are currently Open. Open statuses include Internal Review, In Progress, Not Started, and Needs Revision.
Closed Requests - Requests that are Closed. Closed statuses include Submitted to Auditor, Approved, and Closed.