Imported Software Usage

IT Asset Management (Cloud)

The ImportedInstalledInstallerEvidenceUsage table is a staging table used to collect records of actual use of applications related to installation evidence found on inventory devices. From here, de-duplicated and normalized records are merged into the InstalledSoftwareUsageData table.

There are two listings below. The first maps what is imported from Data Platform v5. The second lists values that IT Asset Management expects to load into the ImportedInstalledInstallerEvidenceUsage table, that are not available from Data Platform v5, and the impact of these gaps on license reconciliation calculations where these rely on data from only this source.

Data mapping for imported usage related to installer evidence

The following listing matches the source data from Data Platform v5 with the equivalent column in the ImportedInstalledInstallerEvidenceUsage table. Other columns from the ImportedInstalledInstallerEvidenceUsage table cannot be populated from Data Platform v5, and so are omitted here (and shown below). For more details on the database tables and columns within IT Asset Management, please see IT Asset Management Schema Reference.

Data Platform (Table)/Column FNMS (Table)/Column Notes

(MATCH_SOFTWARE_METERING) / USAGE_YEAR and USAGE_MONTH_N

Failover to (MATCH_SW_RECENTLY_USED_APPS) / LASTUSEDDATE

 (ImportedInstalledInstaller EvidenceUsage) / StartDate

The start date is set to a string formatted similarly to ISO 8601 (except for the slash separator: 2019/04/01) by conjoining the year and month-number from Data Platform, and adding an assumed day for the first of the month. Only if there is no value available by this path, we use the date available from the alternate table shown.

Fabricated from:

(MATCH_TASK_DET) / PROCESS_ID

(MATCH_TASK_DET) / TASK_NAME and the checksum for the same

(MATCH_SOFTWARE_METERING) / HOST_ID

 (ImportedInstalledInstaller EvidenceUsage) / ExternalID
The format is of this form (shown with nonsense values): 
PID123|TheTask|654321:Host789
An external ID is fabricated from the various details shown (truncated as required and joined with various separator characters). This is then mapped through the ImportedStringMapping table to convert string IDs to integer IDs.
Tip: If the MATCH_SOFTWARE_METERING table cannot provide a host ID, it is taken from MATCH_SW_RECENTLY_USED_APPS.
(MATCH_SOFTWARE_METERING) / CAT_SW_UUID (ImportedInstalledInstaller EvidenceUsage) / ExternalInstallerID
The identifier used in Data Platform for the installer evidence.
Tip: If the MATCH_SOFTWARE_METERING table cannot provide an external ID, it is taken from MATCH_SW_RECENTLY_USED_APPS.
(MATCH_SOFTWARE_METERING) / USAGECOUNT plus TSUSAGECOUNT (ImportedInstalledInstaller EvidenceUsage) / NumberOfSessions

If the number of sessions in which the evidence was in use cannot be calculated by this method, the default value 1 is inserted.
(MATCH_SOFTWARE_METERING) / LASTUSEDDATE

Failover to (MATCH_SW_RECENTLY_USED_APPS) / LASTUSEDDATE

 (ImportedInstalledInstaller EvidenceUsage) / LastUsedDate

The last known date when usage of the application is recorded (in one table or the other).

(MATCH_SW_RECENTLY_USED_APPS) / LASTUSERDOMAIN, then a backslash \, then LASTUSERLOGON (ImportedInstalledInstaller EvidenceUsage) / ExternalUserID

The end-user identified in the source as using the software. The identifier is fabricated by conjoining the flat domain name and logon name (separated by a backslash).

Data not imported from Data Platform v5

These columns in the ImportedInstalledInstallerEvidenceUsage table cannot be populated by inventory imports from Data Platform v5. These missing data points do not impact license compliance calculations. For further details about these columns, please see the schema reference.
  • ComplianceConnectionID — internally generated
  • ExternalInstanceID (used only for Oracle).

IT Asset Management (Cloud)

Current