Integration for Asset-EAM - Inventory

[Diego Peukert]

I am implementing EAM and in my use case, there is already an asset base controlled by another system, which is common because the SN is not always coming in to start digitizing a process or completely replacing another system.

In my case, both systems will coexist for at least two years, where part of the lifecycle is controlled in System 1 and, from the point of view of maintenance flows and asset write-offs, in ServiceNow.

That said, EAM assets will always be created outside of ServiceNow, where this system does not have a model equivalent to SN, in terms of Model Category and Model. When integrating, I am seeking to at least place medical assets in the correct category/table, as well as facility items and vehicles, but I am looking for a solution to:

1 - The asset model to be filled in later (for this I will need to adjust BRs in the system), I do not expect to downgrade or upgrade the class, leaving the record in the table where it was placed from the Transforme that underwent it, just inputting the model at a later stage, enriching the record already on the SN side. Is this correct?

2 - I noticed that there are blocks to prevent model adjustment (even in the same class), and it is common to have to adjust the model of something, especially if it will be done manually or via upload, after the assets themselves are inserted into the integration. How can this be done safely?

My impression is that the EAM module expects the asset to be 100% complete with the correct model definition and model category, but in the case of assets such as cars, power generators, furniture, medical equipment, among others, this information will not come from an OT Discovery in most cases, but rather from an existing database/system, being subsequently enriched on the SN side, and it seems that the system is not prepared for this, without seeing all the details I mentioned and adjusting BRs, ACLs, Client Scripts, and the like. Has anyone been through this and have any tips on this topic?

[outnoom]

Is it OK to defer setting the Model?

Yes — if you properly adjust Business Rules (BRs), UI Policies, and ACLs, you can enrich assets later (e.g., populate model/model category manually or through subsequent integration steps) without moving the record from one table to another.

Just make sure the asset is placed in the correct base table (e.g., alm_medical_device, alm_facility, etc.) via transform map logic, even if the Model is initially blank. You’re correct not to “downgrade” or shift class later.

---

2. How to safely allow Model adjustments post-creation?

Out-of-box, ServiceNow locks down model changes after creation (even same class) via:

Client scripts and

Business Rules like Prevent Model Update and Model is Required

To safely allow later model updates, you can:

Clone and modify Prevent Model Update BR to add logic:

e.g., allow changes if a flag like model_locked == false

Use a custom field like Enrichment Phase Complete to lock the model after it's reviewed.

Modify transform map to skip this BR during integration using a source == "integration" flag or script.

---