Expanded Model and Asset Classes - Best Practices for Managing in ITSM Pro without EAM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-09-2025 10:34 AM
Issue: "Expanded Model and Asset Classes" (sn_ent) Plugin Installed in ITSM Pro Without EAM
Background: Currently running ITSM Pro without the Enterprise Asset Management (EAM) plugin. At some point, the "Expanded Model and Asset Classes" plugin (sn_ent) was installed in the instance. Unfortunately, these Asset classes appear unusable when creating new Assets. However, these EAM Model Categories can be used when creating new Models and Model Categories.
Steps to Reproduce
- Install sn_ent (“Expanded Model and Asset Classes”).
- Create a Model Category under an expanded sn_ent_* Asset Class.
- Create a Product Model using that category.
- Attempt to create an Asset using the model/category.
Result: The new model/category can't be selected during Asset creation since ITSM Pro’s asset interceptor filters out Expanded Asset classes.
That leads me to ask:
- Why is this plugin available for install without EAM?
- Now installed, how do you best configure ITSM Pro to manage these unusable Expanded Asset Classes?
- It seems to me that these Expanded Models and Asset Classes are likely to become problematic in a transform or confuse Asset Managers who think they can be readily used.
Appreciate your thoughts,
Jared
FYI, here are the installed tables as part of sn_ent:
Label | Name | Extends table | Extensible |
Information Asset | alm_information_asset | Asset | TRUE |
Information DNS Asset | alm_information_dns_asset | Information Asset | FALSE |
Enterprise asset | sn_ent_asset | Asset | TRUE |
Commercial lines insurance product model | sn_ent_b2b_ins_policy_model | Service Model | FALSE |
Personal lines insurance product model | sn_ent_b2c_ins_policy_model | Service Model | FALSE |
Cable model | sn_ent_cable_model | Enterprise good model | TRUE |
Card service model | sn_ent_card_service_model | Service Model | FALSE |
Construction asset | sn_ent_construction_asset | Enterprise asset | TRUE |
Construction model | sn_ent_construction_model | Enterprise good model | TRUE |
Deposit model | sn_ent_deposit_account_model | Service Model | FALSE |
Discovered firmware model | sn_ent_discov_firmware_model | Discovered SW component model | FALSE |
Drug model | sn_ent_drug_model | Medical model | TRUE |
Facility asset | sn_ent_facility_asset | Enterprise asset | TRUE |
Facility model | sn_ent_facility_model | Enterprise good model | TRUE |
Financial service model | sn_ent_financial_services_model | Service Model | FALSE |
Firmware model | sn_ent_firmware_model | Software component model | FALSE |
Group life insurance product model | sn_ent_group_life_ins_policy_model | Service Model | FALSE |
Individual life product model | sn_ent_indiv_life_ins_policy_model | Service Model | FALSE |
Industrial asset | sn_ent_industrial_asset | Enterprise asset | TRUE |
Industrial model | sn_ent_industrial_model | Enterprise good model | TRUE |
Investment model | sn_ent_investment_model | Service Model | FALSE |
Line of credit model | sn_ent_line_of_credit_model | Service Model | FALSE |
Loan model | sn_ent_loan_account_model | Service Model | FALSE |
Logical network connection model | sn_ent_logical_nw_connection_model | Network model | FALSE |
Medical asset | sn_ent_medical_asset | Enterprise asset | TRUE |
Medical device model | sn_ent_medical_device_model | Medical model | FALSE |
Medical insurance model | sn_ent_medical_insurance_model | Service Model | FALSE |
Medical model | sn_ent_medical_model | Enterprise good model | TRUE |
Medication model | sn_ent_medication_model | Drug model | FALSE |
Enterprise good model | sn_ent_model | Product Model | TRUE |
Enterprise model classification | sn_ent_model_classification | FALSE | |
Enterprise model classification source | sn_ent_model_classification_source | FALSE | |
Enterprise model classification type | sn_ent_model_classification_type | FALSE | |
Network topology model | sn_ent_network_topology_model | Topology model | FALSE |
Network card model | sn_ent_nw_card_model | Network model | FALSE |
Network equipment model | sn_ent_nw_equipment_model | Network model | FALSE |
Network holder model | sn_ent_nw_holder_model | Network model | FALSE |
Network interface model | sn_ent_nw_interface_model | Network model | FALSE |
Network model | sn_ent_nw_model | Hardware Model | TRUE |
Permit model | sn_ent_permit_model | Contract Model | TRUE |
Physical network connection model | sn_ent_physical_nw_connection_model | Network model | FALSE |
Retail asset | sn_ent_retail_asset | Enterprise asset | TRUE |
Retail model | sn_ent_retail_model | Enterprise good model | TRUE |
Social benefit model | sn_ent_social_benefit_model | Service Model | TRUE |
Strand model | sn_ent_strand_model | Enterprise good model | TRUE |
Tactical equipment asset | sn_ent_tactical_asset | Enterprise asset | TRUE |
Tactical equipment model | sn_ent_tactical_model | Enterprise good model | TRUE |
Topology model | sn_ent_topology_model | Product Model | TRUE |
Transportation asset | sn_ent_transportation_asset | Enterprise asset | TRUE |
Transportation model | sn_ent_transportation_model | Enterprise good model | TRUE |
Vaccination model | sn_ent_vaccination_model | Drug model | FALSE |
Wearable asset | sn_ent_wearable_asset | Enterprise asset | TRUE |
Wearable model | sn_ent_wearable_model | Enterprise good model | TRUE |
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
My team ended up resolving this by creating a custom “Create New Asset” catalog item with a dedicated Flow, rather than relying on the OOB asset form.
Highlights:
Abstracted complexity – Users interact with a simple Service Catalog form that gathers the required fields (including manufacturer, model, and category), instead of navigating the full Asset form and needing to understand which records do what and why.
Inline creation of related records – The Flow allows users to create Models and Manufacturers on the fly if they don’t exist, so they’re not blocked by missing references.
Bypassing restrictions – Because the Flow directly inserts the asset record, it’s able to reference the expanded sn_ent_* classes without hitting the OOB asset creation checks that normally block them.
Controlled access – We scoped the catalog item to the right audience.
Outcome:
This approach gives Asset Managers a clean and guided way to create records using otherwise-unusable sn_ent classes in ITSM Pro, while maintaining data quality. If anyone else is stuck with sn_ent installed but without EAM, a tailored catalog item + Flow is a low-impact way to bridge the gap.