What is the Assets common data model?
The Assets common data model is currently only available to customers enrolled in the Beta program. Some details may change before general availability.
The Assets common data model is a set of ready-to-use schemas in Assets that give you a standardised way to structure enterprise data - without designing schemas from scratch.
When you enable the Assets common data model, you get preconfigured system schemas, object types, and attributes that model the data most organisations need: the people who use your assets, the locations where they're deployed, the organisations that supply them, and the assets themselves.
Because the data follows a known, consistent structure, features like automation rules, request type fields, and AI can work with it immediately.
Why use the Assets common data model?
Without the Assets common data model, you'd need to design your own schemas for every type of data you want to track, manually create relationships between them, and maintain consistency as your needs grow.
With the Assets common data model, you get:
Schemas that work immediately — enable them, import your data, and start managing assets.
Built-in connections — your assets automatically link to the people who use them, the locations where they're deployed, and the organisations that supplied them.
Automations and AI ready from day one — because your data follows a known structure, automation rules and AI features can work with it without additional configuration.
A foundation you can extend — add your own custom attributes to any schema, or wait for new schemas to become available as they're released.
How to get started
Enable the Assets common data model from Assets settings > Common data model.
Import your existing data into the pre-configured schemas and object types.
Customise (optional) by adding custom attributes or object types to fit your organisation.
Use your data across automations, request types, and AI without additional setup.
What's included
The Assets common data model includes the following system schemas out-of-the-box:
Schema | What it helps you do |
|---|---|
People | Connect assets and services to the humans who own, use, or manage them. |
Geography | Model where your assets and people are — from regions down to specific rooms. |
External organisations | Track your vendors, manufacturers, and resellers in one place. |
How the Assets common data model connects data
Foundational schemas reduce duplicate data. Instead of each solution schema defining its own version of people, locations, or organisations, solution schemas reference common, shared objects.
This means:
A hardware asset can carry its own lifecycle and technical details while connecting to shared context. This could be the person assigned to it, the building where it's located, and the vendor that supplied it.
If a person's details change, every asset referencing that person reflects the update automatically.
New solution schemas (such as future software or cloud asset schemas) can plug into the same foundational data without rebuilding shared concepts.
How to identify Assets common data model schemas
On the Schemas page in Assets, schemas that are part of the Assets common data model appear with aSYSTEM label. Custom schemas you create yourself appear with the CUSTOM type label.
You can't delete or rename schemas that are part of the Assets common data model, but you can add custom attributes and object types to extend them.
Was this helpful?