Skip to content
  • There are no suggestions because the search field is empty.

Assets Overview

Assets is the consolidated inventory view for a project. It shows every hardware and software record collected from all connected sources, plus the contracts and licenses uploaded to the project, before any application-specific analysis is applied.

Assets is the consolidated inventory view for a project. It shows every hardware and software record collected from all connected sources, plus the contracts and licenses uploaded to the project, before any application-specific analysis is applied.

Assets sits between your data sources and the application pipelines (SIM, MDM, OJDM, RDM, IFMP). Changes made here, such as exclusions, source priority and bulk edits, apply to the data every application reads, not to a single report.

  • Hardware: Contents: Devices from every source (SCCM, SIM and MDM templates, NinjaOne, BigFix, collectors); Actions available: Device Exclusions, Source Priority, Download Template and Upload
  • Software: Contents: Recognised products, grouped by product and vendor, plus unmatched and excluded installs; Actions available: Product Exclusions, Change mapping, Exclude, Modify product
  • Contracts: Contents: Contracts in the project, with a renewal timeline; Actions available: Add a contract, filter, download
  • Licenses: Contents: License entitlements in the project, with a renewal timeline; Actions available: Add a license, filter, download

Each section’s tab shows the number of records it holds in the project.

Hardware

The Hardware view opens with two charts and a device table.

Records by Vendor and Records by Source

  • Records by Vendor shows how many devices you have from each manufacturer, such as HP, Dell or VMware. Use it to see what your estate is made of, and to spot records with no manufacturer, which show as Unknown.
  • Records by Source shows how many devices each data source contributed, such as SCCM Queries, SIM - Template, Lansweeper Cloud or NinjaOne. Use it to confirm an integration or upload is delivering data, and to see which sources most of your devices come from.

The download icon on each chart exports its data.

The Hardware table

The table lists one device per row. Its default columns are Device Name, Device Type, Manufacturer, Operating System, Model, CPU Model, Total Number Of Cores, Total Number Of Processors, Serial Number and Sources, the data sources that reported the device. Filter, download, expand and configure the table from the icons at its top right.

Click the arrow at the start of a row to see more about the device. Each source that reported it is listed with the device’s name and type in that source, and when the data was received.

Edit or exclude a device

Click the ⋮ at the end of a row to open its menu:

  • Edit changes the device’s details.
  • Exclude takes the device out of analysis.

An excluded device stays in Assets but moves to the Excluded Hardware table, under the main Hardware table, and is no longer passed to the applications.

Device Exclusions

To exclude devices by rule rather than one at a time, use Device Exclusions. Excluded devices remain visible in Assets but are never passed to SIM, MDM, OJDM, RDM or IFMP.

Rules match against the device business key: the device identifier as it appears in the source data.

  • Exact: Excludes devices where the business key: equals the value; Example rule: test-vm-01; Matches: test-vm-01 only
  • Contains: Excludes devices where the business key: includes the value anywhere; Example rule: test; Matches: test-vm-01, uat-test-02, latest-build
  • Starts with: Excludes devices where the business key: begins with the value; Example rule: dev-; Matches: dev-web-01, dev-sql-03
  • Ends with: Excludes devices where the business key: ends with the value; Example rule: -lab; Matches: nyc-lab, ldn-01-lab

To add rules:

  1. Click Device Exclusions.
  2. Select a match type.
  3. Enter the business key or pattern.
  4. Click Add Rule. Repeat for additional rules.
  5. Click Save.

Rules are evaluated against all current and future records. Removing a rule restores the matched devices to the pipelines on the next analysis run.

Source Priority

When the same device is reported by more than one source, Source Priority decides which source’s values are used in the consolidated record.

  1. Click Source Priority.
  2. Drag the sources into order, highest priority first. Where two sources disagree, the higher one wins.
  3. Click Save.

Source Priority applies to all hardware records in the project. A typical order puts authoritative agent-based sources (SCCM, NinjaOne, BigFix) above manually maintained templates, so that a template upload can’t override live discovery data unless you intend it to.

Bulk edit via template

You can change hardware data in bulk by downloading a template, editing it and uploading it again. Licenseware keeps track of your changes and applies them on top of the data from your sources. Use it, for example, to:

  • standardise vendor names, so Dell Inc. and Dell count as one manufacturer
  • apply a naming convention to device names
  • add devices that no integration reports, or correct other attributes

  • 1: Click Download Template. It contains the hardware column schema.
  • 2: Add or edit rows. Don’t change the device identifier column: it’s the match key.
  • 3: Save as CSV, UTF-8.
  • 4: Click Upload and select the file.

How uploaded records rank against other sources is set by Source Priority.

Software

The Software view lists every product found in your project, the raw install entries behind it, and any Oracle data.

  • Records by Vendor shows how many software records you have from each vendor, such as Microsoft, Red Hat or Adobe.
  • Records by Source shows how many records each data source contributed, such as SCCM Queries, SIM - Template or NinjaOne.
  • Download Template and Upload let you add software records in bulk, and Product Exclusions excludes products across the whole project (see below).

Below the charts are the software tables. Each one can be filtered, downloaded, expanded or configured from the icons at its top right.

Bulk edit via template

Software works the same way: click Download Template, edit the data, and click Upload to send it back. Licenseware keeps track of your changes. Use it, for example, to standardise vendor or product names across your sources.

Software Products

Every recognised product, one row per product and version, with its Vendor Name, Version, Device Count, Product Type, Product Category and Subcategory, Product Description, License Type, Deployment Type, Pricing Tier and licensing metric.

  • See what’s mapped to a product: click the arrow at the start of a row to see the raw install entries from your sources that were recognised as that product.
  • Open the product: click its name to open its detail page (see Modify product).
  • Change mapping or exclude it: click the ⋮ at the end of a row.

Change mapping maps the entry to a different product in the Licenseware catalog. Search for the vendor, pick the product, and click Save. The new mapping applies everywhere that exact name, vendor and version combination occurs.

Exclude removes the product from every licensing calculation. Choose the versions to exclude, or tick Exclude all versions to exclude the product whatever its version, including versions found later. Then click Exclude.

Software Usage

How recently each product has been used, from the usage data your sources provide. For each product it shows the number of devices that used it in the last 30, 60 and 90 days, how many haven’t used it in 90+ days, an overall Usage rating (Used, Rarely used or Not used), and its total Devices. Use it to find installed software nobody uses.

Excluded Software Products

Products that have been excluded, with the Reason (such as Excluded by user) and who excluded them, Excluded By. Excluded products stay listed here but are left out of every licensing calculation.

Unmatched Software Installs

Raw install entries from your sources that Licenseware couldn’t match to a catalog product, with their Raw Product Name, Raw Vendor Name, Raw Version, Device Count, Last Used date and Sources. Review these to map them to the right product.

Excluded Software Installs

Raw install entries that are left out of analysis, with the Reason they were excluded (such as .NET framework component) and who or what excluded them, Excluded By, such as catalog or user.

Oracle Databases

Each Oracle database option and management pack found, per database: Database Name, Device Name, Edition, Version, Instance Status, the Option or pack, its Product Type, the usage Result (such as Verify or Not used), the Features used, First and Last Usage Date, and Source.

Oracle Middleware

Oracle Middleware installations per device: Product Name, Product Category, Product Type (product or component), whether it’s Licensable, Version, Install Location and Components.

Product detail page

Click a product name to open its detail page.

  • Header: Product name, vendor, Type, Category, Subcategory, device count and contributing sources
  • Description: The catalog description of the product
  • Devices table: Every device where the product was found: Device Name, Sources, Identity Source, Product Name, Vendor Name, Version, Product Type, Product Category, Product Subcategory
  • Modify product: Opens the product edit dialog (see below)

Product Exclusions

To exclude products without finding them in the table first, use the Product Exclusions button. Excluded products are ignored by every licensing calculation across all applications. Use this for personal, freeware or out-of-scope software that shouldn’t appear in compliance results.

  1. On the Software tab, click Product Exclusions at the top right.
  2. Select a vendor. The product list shows each product with its known versions, for example WiX Toolset - 3, 3.11, 3.14. rolling means a continuously updated product with no fixed version.
  3. Select a product, then either:
  • Select individual versions: Only the chosen versions are excluded; other versions continue to be analysed
  • Tick Exclude all versions: The product is excluded regardless of version, including versions discovered later

Products and versions that are already excluded aren’t shown in the dialog.

Modify product

Edits made here overlay the Licenseware software catalog for your organisation only, and apply everywhere the attribute is read: Assets, SIM, and any report that references the product.

  • Product fields: Fields: Type, Category, Description; Applies to: The product and all of its versions
  • Version fields: Fields: License type, Deployment, Pricing, Metric, Price; Applies to: One selected version only
  1. Open the product detail page and click Modify product.
  2. Choose Product fields or Version fields.
  3. Edit the values and click Save.

Catalog updates from Licenseware don’t overwrite your changes.

Contracts

The Contracts view shows every contract in the project and when each one is up for renewal.

Renewal Timeline

Renewal Timeline - Next 12 months plots each contract renewal by month, with the number of renewals and the total value at risk above the chart, for example 11 renewals · $2.65M at risk. The timeline is shaded by renewal window, ≤30d, 31–60d, 61–90d, 91–120d and 121d+, with the number of renewals in each window at the top right.

Contracts table

One row per contract, with its Contract Name, Contract Type (such as Enterprise Agreement or Subscription Agreement), Vendor, Status (Active or Expired), Start Date and End Date, Days Remaining until it ends (negative once it has expired), Number of Licenses, Total Value and Currency.

Click + at the top right of the table to add a contract, and use the other icons to filter, download or configure the table. Contracts are managed in the License and Contracts Manager.

Licenses

The Licenses view shows every license entitlement in the project and when each one is up for renewal.

Renewal Timeline

The same Renewal Timeline - Next 12 months as on Contracts, for licenses: each license renewal by month, the number of renewals and value at risk, and the count in each renewal window.

Licenses table

One row per license, with its License Name, the Contract Name it belongs to (or - for a license that isn’t under a contract), License Type, Vendor, Status, Start Date and End Date, Days Remaining, Total Quantity, Total Value and Currency.

Click + at the top right of the table to add a license, and use the other icons to filter, download or configure the table. Licenses are managed in the License and Contracts Manager.

Relationship to SIM Bulk Edit

  • SIM Bulk Edit: Where: SIM application; Key: raw_vendor_name + raw_product_name; Scope: Recognition results for products in Verification Needed
  • Modify product: Where: Assets > Software; Key: Catalog product / version; Scope: Catalog attributes for recognised products, all applications
  • Product Exclusions: Where: Assets > Software; Key: Vendor > product > version; Scope: Removes the product from all licensing calculations

Use SIM Bulk Edit to fix what a raw string is recognised as. Use Assets to change what is true about the recognised product.