Working with Custom Reports
Your organization may use a suitable strategy to create a set of custom reports. The following are some example strategies that could be used to create a set of custom reports.
Demand-based reporting
You can create a set of reports to meet the demands of one or more users such as a software asset manager. The following list provides a set of example questions that you can ask yourself before building a set of reports:
-
What type of reports are required to provide data on current license position?
-
Which reports should be good to better prepare for software audits or true-ups?
-
Which reports should be helpful in accessing CALs usage?
Software asset management maturity level-based reporting
Reports can be used to measure software compliance against a specific Software Asset Management (SAM) maturity level (SAML). For each additional level of compliance, you may need to produce additional reports. For example,
-
For the first level, you may need some reports reflecting software installations on various inventory devices within your organization.
-
The second level may require additional reports on license compliance and unlicensed application installations.
-
The third level may require some advanced reports like unrecognized evidence or scheduled payments.
Task-based reporting
You can also create reports based on the software license optimization tasks that are performed on a regular basis. For example:
-
A Monthly Tasks folder might have the following set of reports:
-
Devices in storage for over three months
-
Multiple assets assigned to a user
-
-
A Weekly Tasks folder might have the following set of reports:
-
Assets assigned to terminated employees
-
License compliance changes for a publisher
-