--- title: "Unified Data Model" slug: "unified-data-model" status: "update" updated: 2026-11-18T07:51:16Z published: 2026-11-18T07:51:16Z canonical: "help.symphonysummitai.com/unified-data-model" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.symphonysummitai.com/llms.txt > Use this file to discover all available pages before exploring further. # Unified Data Model Use Unified Data Model, **Asset Model Studio** to define reusable asset attributes, manage inheritance, and organize the fields displayed in category-specific asset forms. The UDM configuration workflow combines a shared model hierarchy with a form builder for individual categories. The following section covers, reviewing the model, editing sections, creating attributes, defining a category and its asset code, selecting a form layout, and verifying the saved configuration. It is intended for ITAM administrators and implementation teams. ### **Use cases** - Standardize shared asset information such as asset identity, ownership, and warranty details across categories. - Add category-specific data such as keyboard connection details or a custom date field without duplicating the shared model. - Create a new fixed-asset category and build its form from inherited attributes. - Apply consistent asset-code components and choose a readable two-column or three-column layout. #### Understanding the Model Hierarchy The **Model** tab displays the entity hierarchy. The form builder adds a category level beneath the selected asset type. An inherited section retains its association with the level where it was defined. > [!NOTE] > Note > > UDM is the best in-class well-architected Intelligent Asset Management. You will see out-of-the-box (OOTB) default system defined attributes, which are a must for all asset types. Hence, these assets are by factory default available at Level L1. Examples include: Asset ID, Asset Code, User, etc…System defined attributes inherit from parent to all subsequent child hierarchy levels.Morevover, System defined attributes are displayed in Grey background color and these are view-only attributes, which means these cannot be edited or removed from child levels. | Level | Entity | Purpose and Examples | | --- | --- | --- | | L1 | Universal | Shared root model which is inherited by subsequently all levels. Examples include Asset Code, identity, location, ownership, and asset details. | | L2 | IT or Non-IT | Branch-specific model beneath Universal. The IT branch includes device identity and discovery information. While the Non-IT branch includes Facilities (firealarm system, generators, water pumps), Accessories (office chairs, book shelves, whiteboard), and consumables (paper, notebooks, pen…). | | L3 | Asset Types | Examples under IT include Fixed, Accessories, Consumables, Software, Service, Cloud-CI, and On-Premises-CI. Examples under Non-IT include: Accessories, Consumables, Facilities, and Fixed assets. | | L4 | Category | Category-specific sections and attributes, such as Laptop, Desktop, or Keyboards. You need to click Form layout to configure the Category. | Table: UDM Asset Levels Refer the following links, for configuring: - [Level 1 to Level 3 Entities: Model Tab](/apex/docs/unified-data-model#model) - [Level 4 - Category: Form layout Tab](/apex/docs/form-layout) ### UDM Configuration screen overview As shown in the following figure, the **Model** tab is used to configure L1-L3 levels, whereas **Form layout** tab is used to configure **L4 Category**. Department indicates for which department, you want to configure the Asset levels or a category. Configurations are specific to the Department, which you have selected. For editing levels L1-L3 or creating an attribute in L1-L3, you need to select **Model**. For editing any categories, which is at L4 level or adding attributes at L4 level, you need to click **Form layout**. Further, using **Edit model** you can make changes to the respective model, which you have selected from the left panel. The left panel is where you first need to select the L1-L3 levels. For better UI experience, you can also use **Collapse All** and **Expand All** buttons, which will be useful to easily spot and conifgure the appropriate attributes at the specific category, you desire. Using **Search**, you can also quickly search for the respective attribute within the selected section. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/Annotated%20model%20configuration%20interface.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A41%3A52Z&se=2026-11-20T22%3A41%3A52Z&sr=b&sp=r&sig=Pl5J8xK5PzL5fL%2BYXFC49RnQPYMlmBosF0CcrOwQ2ns%3D) Figure: UDM Configuration Screen Overview ## System Defined Factory Default Attributes **A consistent foundation, inherited automatically.** System-defined factory-default attributes are built-in fields supplied with SummitAI’s Unified Data Model (UDM). These attributes provide a consistent structure for essential asset information and are non-editable in the model configuration. Factory default attributes automatically pass from their defining parent level to applicable child levels. Administrators do not need to recreate them for each asset type or category form. For attributes defined at **Level 1 — Universal**, inheritance extends through both branches: - **IT:** Universal → IT → Asset Type → Category Form. - **Non-IT:** Universal → Non-IT → Asset Type → Category Form. Attributes defined specifically within a branch pass only to that branch’s applicable children. #### Understanding the Screenshot The screenshot shows **Edit model** at **Level 2 — IT**, identified by the path **Universal > IT**. The inherited **Universal — L1** area appears as a read-only section in grey non-editable chips. Within its **Identity** section, the following attributes (few examples for reference) appear as gray chips without removal controls. Similarly, you will find other sections as well, where you will have non-editable attributes in grey chips. Editable attributes are displayed in blue chips. Attributes in blue chips, can be removed as well from the respective section. If you click the cross icon, the attribute will be moved towards the left section as **unused**. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/Edit%20Model%20l2%20level1.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A41%3A52Z&se=2026-11-20T22%3A41%3A52Z&sr=b&sp=r&sig=%2BxxL1ZrY3jRp9LHTCHATQ27ZSvLxAiFOO5IuRcczL3Q%3D) Figure: Edit Model | Factory Default Attribute | Purpose | | --- | --- | | **Asset code** | Provides a code used to identify and reference an asset. | | **Asset ID** | Identifies an individual asset record. | | **Discovery reference ID** | Holds a reference associated with discovery information for the asset. | | **Tracking type** | Identifies the tracking approach associated with the asset. | These factory default attributes remain part of the inherited structure. Their definitions ***cannot be edited or excluded*** through model configuration. **Note:** The screenshot also displays **Description** and **Serial number** with a different appearance and removal controls. Do not assume that every attribute in the Identity section has the same factory default restrictions. ### Example Inheriting Common Identity Attributes Sam, an ITAM administrator, manages laptops, desktops, and office furniture. The factory default identity attributes already exist at the Universal level. | Asset Category | Inheritance Path | Example Asset Record | | --- | --- | --- | | **Laptop** | Universal **L1** → IT **L2** → Fixed **L3** → Laptop **L4** | Asset code: **LAP-NY-001**; Asset ID: **10001** | | **Desktop** | Universal **L1** → IT **L2** → Fixed **L3** → Desktop **L4** | Asset code: **DESK-NY-001**; Asset ID: **10002** | | **Office Chair** | Universal **L1** → Non-IT **L2** → Fixed **L3** → Office Chair **L4** | Asset code: **CHR-NY-001**; Asset ID: **20001** | All three category forms inherit the applicable Universal identity attributes. Sam does not create separate Asset code or Asset ID definitions for Laptop, Desktop, and Office Chair. Each asset record has its own values, even though the records share the same inherited attribute definitions. #### Example Viewing Parent Attributes at Level 2 While configuring **Level 2 — IT**, Sam reviews the inherited Universal Identity section. Asset code, Asset ID, Discovery reference ID, and Tracking type are already available. Sam cannot modify these factory default definitions to create IT-specific versions. Their inheritance also continues to applicable Level 3 asset types and Level 4 category forms. If Sam needs an additional field that applies only to IT assets, such as **Network Domain**, he creates a custom attribute at **Level 2 — IT**. Applicable IT children inherit that custom field, while the Non-IT branch remains unaffected. **Important:** Attribute inheritance shares field definitions, not asset values. A non-editable factory default definition does not, by itself, establish whether users can edit its value on an asset record. Value entry and updates depend on the individual field’s behavior. *Asset codes and IDs in these examples are illustrative.* #### Editing or Adding Custom Attributes To edit an attribute or add custom attribute at the L1-L3 level, perform the following steps: 1. Log in as an Admin. 2. Select **Worksapce > Admin > Infrastructure > Platform Master > Form Designer**. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/Accessing%20Form%20Designer.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A41%3A52Z&se=2026-11-20T22%3A41%3A52Z&sr=b&sp=r&sig=0Pqjms3IGo3UparrgBTzScjuaQEUd95eykGj4DiLE1g%3D) Figure: Accessing Form Designer 3. Click **Form Designer**. The following screen is displayed. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-1IBCR07C.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A41%3A52Z&se=2026-11-20T22%3A41%3A52Z&sr=b&sp=r&sig=tuzy%2BPXDAhNqGDApEVyyZebCT9wG2MQd8y8R0zIHTtM%3D)Figure: Model Studio 4. By default, only 1 department will be available. Example IT department or HR department. 5. Identify at which level you want to edit attributes. Example, to edit an attribute or add an attribute at L2 level, you need to click either IT or Non-IT. Let’s presume you want to add an attribute at L2 level. Click IT L2 on the left panel. 6. Click **Edit Model**, which will edit the L2 level attributes. If you are adding a new attribute at L2 level, it will be available to the IT and the child levels underneath IT only and not under Non-IT. 7. A confirmation dialog box is displayed. Click **Continue** to edit the model. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-CI1VF1TG.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A41%3A52Z&se=2026-11-20T22%3A41%3A52Z&sr=b&sp=r&sig=egf5quR47aCeidH1CfOoFJmM33JK2eWBhlfc0cieuTA%3D) Figure: Edit Model 8. Click **Create new custom attribute** under IT in the left panel, to add a new attribute under IT. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-RV1FQV5U.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A41%3A52Z&se=2026-11-20T22%3A41%3A52Z&sr=b&sp=r&sig=RW7N0MIndBk%2F8gcsUVgKbtWbRPUyZgcsmMxvzLc7fiM%3D) Figure: Create new attribute 9. Enter **Attribute name** and select **Field type**. Fields marked with an asterisk are required. 10. Complete the settings displayed for the selected field type, including **Validation type** when required. Configure **placeholder text, filter inclusion, help text**, and **internal-use** selection as needed. 11. Click **Create**. Locate the attribute in the available or unused list and drag it into a section at its own level. 12. Click **Save** on the Edit model page, then verify the field in Model. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-KSMHVIHI.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A41%3A52Z&se=2026-11-20T22%3A41%3A52Z&sr=b&sp=r&sig=YuQhTbQsWPaDSETPn4HqKzgo%2B9z%2FJTEv%2BW5twq5dy78%3D) Figure: Create a custom attribute Creates a Date field named custom attribute at Universal. For your implementation, use a descriptive name, such as Contract Review Date, and choose the level according to who needs that information. | Field name | Description | | --- | --- | | Attribute name | Label used to identify the attribute. Use a clear name that describes the information to collect. | | Field type | Field Types include Textbox, Integer, Textarea, Date, Date and time, User search, Dropdown, Tree, and Checkbox. Choose an appropriate type before completing its dependent settings. | | Used in | Select the applicable usage context. Options shown are Asset Code, QR Code, and Gate Pass. This selection alone does not demonstrate a complete QR-code or gate-pass workflow. > [!NOTE] > Note > > First 3 characters of Asset code are taken as part of Asset Code. Maximum you can only have only 5 attributes to be configured in the Asset Code. : | | Placeholder Text | Prompt displayed in the field to guide the user before a value is entered. | | Include in filter | Toggle for including the attribute in filtering. Verify its availability in the intended operational view after saving. | | Validation type | This drop-down is available only if you select Field Type as Date or Date and Time. Following options are available: - Current time window: Restricts the field to the current date and time range as defined by the application. - Don’t allow future date and time: Prevents users from selecting a date and time later than the current system date and time. - Don’t allow past date and time: Prevents users from selecting a date and time earlier than the current system date and time - Free date and time: Allows users to select any valid date and time without restrictions. | | Enable help text | Enable when additional guidance is needed. Supply the relevant guidance in any help-text control exposed by the application. | | Is the attribute for internal use | Select Yes or No according to the intended audience. Verify visibility with the relevant user role. If selected as Yes, the attribute is not displayed on UI, but is primarily used for some backend work. | | **Validation Tab** | | | Validation Type | Two options are available. Disable or Mandatory. **Disabled**: If you select Disabled, the attribute is disabled and you can also select ‘When’ you want the attribute to be disabled. Such as Everytime Disabled or when specific conditions are met. - **Everytime**: If selected, the attributes remains disabled all the time. - **Below conditions met**: If selected, you can specify for which conditions met, you want the attribute to be disabled. Selecting **Below conditions met**, will display ‘Attribute’, ‘Operator‘, and ‘When’ parameter values. **Example**: Disable the attribute when: Attribute Antivirus status with operator condition ‘Does not equal’ to value ‘In store’ | | Attribute | Select the Attribute for which you want to conditions to be configured. Example: Asset Code Contains ‘LAP’, if you want the attribute to be displayed, wthen select Attribute as ‘Asset code’. > [!NOTE] > Note > > You can configure a maximum of 5 conditions using a combination of OR and AND operators. To add more conditions, use the + icon. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-4I6VM0ZM.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A41%3A52Z&se=2026-11-20T22%3A41%3A52Z&sr=b&sp=r&sig=0QmGI88WGYzyw4P%2B0Jm%2FI6vMFQ7aWAyqzPi5k9oyLsw%3D) Figure: Configuring Conditions | | Operator | Below options will be available based on the Attribute you select: - Contains: Returns true when the attribute value includes the specified text or value. - Does not contain: Returns true when the attribute value does not include the specified text or value. - Equals: Returns true when the attribute value exactly matches the specified value. - Does not equal: Returns true when the attribute value differs from the specified value. - Is empty: Returns true when no value has been entered for the attribute. - Is not empty: Returns true when the attribute contains any value. - Unique: Validates that the attribute value does not already exist in another record. - Is any of: Returns true when the attribute value matches **any one** of the selected values. This operator is used to evaluate multiple acceptable values within a single condition. - Is none of: Returns true when the attribute value does **not match any** of the selected values. This operator is used to exclude one or more values from satisfying the condition. | | Value | Specify the value for the selected condition to check. Example: ‘LAP’ in value. | | **Security** | Used to restrict or allow the access part of the custom attribute. This ensures that attribute data is accessible only to authorized users according to their responsibilities. | | Restrict field access | Enables role-based access control for the attribute. When selected, access permissions can be configured to determine how different user roles can view or modify the field. Select the user persona for which you want to control and govern the access. For example, for end user persona you want to give only ‘View access’. The other possible access types are ‘hidden’ and ‘View and edit’. | | Access type | Use the following access types to control, how you wish to hide, view only or view and edit persmissions you want to give to selected user persona role. - Hide: The attribute is not displayed to users assigned to the role. - View and edit: Users can view and update the attribute value. - View only: Users can view the attribute value but cannot modify it. | | Cancel | Click **Cancel,** if you want to revert and skip attribute creation. Data and values entered will be lost, if you can **Cancel**. | | Create | Click **Create**, to create the custom attribute with the configured values. | Table: Create Custom Attribute 13. Click **Create** to create the Custom attribute with the specified values. ### Working with Inherited Sections and Attributes Inherited sections are displayed beneath their owning level. They are read-only for structural changes when a different level is being edited. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-9VFGNRTV.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A41%3A52Z&se=2026-11-20T22%3A41%3A52Z&sr=b&sp=r&sig=Y59XC4Tix4noDsSFb7Yuj9ELuFkbyyZIOGuhP4gtFRY%3D) Figure 5 L3 editing restriction for inherited IT sections #### Changing an inherited definition at its source As shown in the above figure, few sections mention that ‘You are at L3 level and you cannot edit or delete this section. The form builder similarly instructs administrators to edit inherited sections at their respective entity level and allows section rearrangement within a level. To edit or change the inherited attributes, perform the following steps: 1. Log in as an administrator. 2. Click **Admin > Infrastructure > Platform > Form Designer**. The Model screen is displayed. 3. To edit, click **Edit Model**. 4. A confirmation dialog box is displayed, as shown in the following figure. Click **Continue** to edit the respective level. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-I6OL4F4T.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A41%3A52Z&se=2026-11-20T22%3A41%3A52Z&sr=b&sp=r&sig=nrs571VAWq7txKVxOoirpO1murFcLASO0348j4E9tmA%3D) Figure: Confirmation dialog box to edit 5. For easier navigation and identifying, which attributes are at which Level, use the **Collapse All** button. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-M3XENEKP.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A41%3A52Z&se=2026-11-20T22%3A41%3A52Z&sr=b&sp=r&sig=sPcvHac2IjJ8FgF5iZR%2F6ZY7bLj3TtrirBbo9SdD%2F%2BY%3D) Figure: Collapse and Expand All. 6. As illustrated in above figure, you can identify sections added expicitly at the IT level and sections inherited from the Universal level. > [!NOTE] > Note > > You cannot delete sections from Univesal level or any parent level. 7. Click the pencil icon to edit the section name of the level, in which you are present. 8. You can also remove attributes in blue chips from the parent attributes, but you cannot remove attributes in grey color chips (which are required) for all subsequent child levels. Example: You can remove ‘Description’ which is in blue color chips from Universal > Identity. However, you cannot remove ‘Asset Code’, Asset ID in grey chips from the Universal > Identity section. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-8C22LSDG.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A41%3A52Z&se=2026-11-20T22%3A41%3A52Z&sr=b&sp=r&sig=p9wUSt8TNO3099S8xi6KMtU4toTLF8BC2Elk4aln7jg%3D) Figure: Removing inherited attributes 9. In addition, if you want to edit an inherited attribute, you can only edit validations of the respective attribute. You cannot rename the attributes inherited from parent Level. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-O8IG15U8.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A41%3A52Z&se=2026-11-20T22%3A41%3A52Z&sr=b&sp=r&sig=UB0j3gksr2L5sPXfbP%2FClubFKqiyTcFqO3TGR0oLQBI%3D) Figure: Only validations can be edited for Inherited attributes 10. Removed attributes will be displayed in the left panel under ‘Unused attributes’. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-8HCD482J.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A41%3A52Z&se=2026-11-20T22%3A41%3A52Z&sr=b&sp=r&sig=FqTMt%2FkCs159xSLTCNsV1%2BnoFm5geoQMQpUdU%2FfWjtY%3D) Figure: Unused attributes 11. Click **Save**, once you are done with the changes. The following dialog box is displayed. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-6ZM18ULA.png?sv=2026-02-06&spr=https&st=2026-11-20T21%3A41%3A52Z&se=2026-11-20T22%3A41%3A52Z&sr=b&sp=r&sig=mvsu%2FdNdbMN1EmLrRZ71n9eZdSr36dq0lu7BXhC3cZk%3D) Figure: Save model changes **Checkbox selected**: **Applying Complete Universal model changes**: Selecting this checkbox ensures that the complete set of Universal Model changes—both custom attribute changes and updates to existing OOTB attributes—is applied across all applicable categories and asset types. Select the checkbox ‘**Apply all Universal model attributes**’, which will apply all Universal Model changes across all categories and action forms, including newly added or modified attributes and updates to previously added out-of-the-box (OOTB) attributes. This ensures all explicitly configured changes and existing OOTB attribute updates are propagated across all applicable asset types, except Asset ID. **Checkbox not selected**: **Applying only changes done explicitly for new or updated attributes:** Applies only explicitly added or modified Universal Model attributes across all applicable categories and action forms. Updates to previously added out-of-the-box (OOTB) attributes are excluded. **Behavior at a Glance:** | Attribute changes | Checkbox Selected | Checkbox Not Selected | | --- | --- | --- | | Newly added attributes | Included | Included | | Modified attributes | Included | Included | | Previously added OOTB attribute updates | Included | Excluded | | Asset ID | Excluded | Excluded | ### ###