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

SIM Bulk Edit

Learn how to use the SIM Bulk Edit feature to alter, enhance, and manage software recognition results with CSV uploads.

Overview

The Product Override feature in SIM allows analysts to manually adjust software recognition results without altering the raw source data. Overrides help ensure reporting accuracy, enhance categorization, and improve decision-making.

Typical use cases include:

  • Recognizing previously unrecognized software
  • Correcting product, vendor, or category details
  • Setting product attributes (type, pricing, licensing, deployment)
  • Adding end-of-life dates
  • Excluding non-business or personal software from reports

👉Download template here 👈

 How it works
  • The template is downloaded pre-filled from the Verification Needed table — it already lists the products waiting to be reviewed.
  • You can also superimpose the software inventory data table onto this template if you need to alter recognition results for products beyond those in the Verification Needed table.
  • Edit only the cells you want to change, leave the rest blank, and re-upload the CSV.
  • Only the cells you fill in are applied. Blank cells never overwrite existing values.
  • Each edit is matched back to your data by raw_vendor_name + raw_product_name (case-insensitive). Do not change those two columns — they are the match keys.
  • Bulk edits are applied on top of the analyzed results. Your edits always take precedence over system recognition, and if the same product is uploaded again, the most recent upload wins.

Verifying a product

Set the mandatory fields as a minimum to remove the software having verification needed, this will make the software available for LCM to allocate against. Any other fields added will be populated in the software inventory schema.

Excluding a product

Set excluded = true to remove the product from the analysis, and add an exclusion_reason. When excluded is true, the other attribute edits on that row are ignored.

End-of-life dates: per-version vs. all-versions

raw_version is used only for end-of-life date rows (support_end_date, extend_support_end_date, discontinued_date). All other edits apply to the product as a whole (matched by raw vendor + product name).

Leave raw_version blank → the dates apply to all versions of the product.
Put a version in raw_version (e.g. 2019) → the dates apply to that version only. Add one row per version.


CSV column reference

Match keys — required, do not edit

Column Notes
raw_vendor_name Original vendor name. Used to match your data.
raw_product_name Original product name. Used to match your data.
raw_version Optional. Version key for end-of-life date rows only (see above).

Context — read-only, ignored on upload

current_vendor_name, current_product_name, total_installs are shown to help you decide. They are ignored when you upload.

Editable attributes

Column Accepted values
vendor_name Free text. Setting this re-identifies the product as recognized.
product_name Free text. Setting this re-identifies the product as recognized.
product_category Free text.
product_subcategory Free text.
product_type Application, Operating System, SDK / Toolchain, Runtime / Framework, Driver / Firmware, Utility / Agent, Component, Other
product_description Free text.
pricing_tier Free, Paid
deployment_type On-Prem, SaaS, Hybrid, Other
license_type Perpetual, Subscription, Open-Source, Freeware
metric Free text (e.g. per user, per device, per core).
price_information Free text (e.g. $200/year, Starts from $5/user/month).

End-of-life dates

Column Accepted values
support_end_date A date — 2027-10-12, 2027-10, or 2027.
extend_support_end_date A date (same formats).
discontinued_date A date (same formats).

Exclusion

Column Accepted values
excluded true or false. true removes the product from the analysis.
exclusion_reason Free text. Only used when excluded is true.
Example rows

Recognize previously unrecognized software

raw_vendor_name,raw_product_name,vendor_name,product_name,product_category Adobe Inc,custom_tool.exe,Adobe,Custom Internal Tool,Development Tools

Exclude non-business software

raw_vendor_name,raw_product_name,excluded,exclusion_reason Games Inc,Solitaire Game,true,Personal / gaming software

Update licensing information 

raw_vendor_name,raw_product_name,pricing_tier,license_type Microsoft,Office,Paid,Subscription

Set an end-of-life date for all versions

raw_vendor_name,raw_product_name,raw_version,support_end_date Microsoft,Windows,,2025-10-14

Set an end-of-life date for one version only

raw_vendor_name,raw_product_name,raw_version,support_end_date Microsoft,Windows,10,2025-10-14
Bringing back an excluded product

How you bring a product back depends on who excluded it.

If the system excluded it (it appears under Excluded Software — e.g. flagged as noise or not relevant):

  • Add a row using its Raw Vendor Name and Raw Product Name (copy them from the Excluded Software export), and fill in the corrected vendor_name and/or product_name. That re-identifies it as a recognized product.
  • You do not need to touch excluded — there is no exclusion of yours to undo.
  • Filling in only other attributes (category, type, dates…) without a vendor_name/product_name does nothing: the product stays excluded. A name is required to bring it back.

If you excluded it earlier (a previous upload set excluded = true):

  • Set excluded to false on its row. Leaving excluded blank does not undo a previous exclusion — the old true is kept, and any other edits on that row are ignored while it stays excluded.
  • To bring it back as a recognized product, also fill in vendor_name and/or product_name on the same row.
  • Setting only excluded = false (with no name) lifts the exclusion but returns the product to its original state — so one that was never recognized comes back as unrecognized, not recognized.
Upload process
  1. Open the Verification Needed table and download the pre-filled template.
  2. Edit the cells you want to change. Leave everything else blank.
  3. Do not edit raw_vendor_name or raw_product_name.
  4. Save as a .csv file.
  5. Upload via SIM Bulk Edit.
  6. Changes apply immediately across all reports.
Things to know
  • Columns with a fixed set of values are case-insensitive. For product_type, pricing_tier, deployment_type, and license_type, casing doesn't matter — saas, SaaS, and SAAS all become SaaS.
  • An unrecognized value is ignored, not rejected. If you put deployment_type = cloud (not one of the accepted options), that one cell is skipped and the rest of the row still imports. Ignored values are listed as a warning in the upload history so you can see what was skipped.
  • Invalid dates or a bad excluded value reject the whole file, with a message telling you which column and value to fix.
  • A row with no raw_vendor_name/raw_product_name is skipped.