SummitAI’s Unified Data Model (UDM) reimagines IT and non-IT asset management with a unified architecture built for consistency, flexibility, and growth. Its predefined 3-level hierarchy connects Universal, IT and Non-IT, Asset Types, along with provision to create Category Forms at level-4. Thus, enabling organizations to define shared attributes once and inherit them across applicable levels downstream. By combining reusable definitions with category-specific configuration, UDM reduces repetitive setup and gives teams greater control as their asset landscape expands.
ITAM, revolutionized with UDM. One foundation. Greater possibilities.
With UDM, administrators define attributes at the appropriate level and make them available to applicable child levels through inheritance. Common information stays consistent across the hierarchy, while custom attributes capture specific business requirements. This reduces repetitive configuration and simplifies the introduction of new asset categories.
Shared by design. Flexible by category.
Standard and custom attributes flow down their respective branches according to where they are configured and remain available. Administrators can exclude inherited custom attributes where they do not apply, tailoring category forms without changing unrelated branches.
UDM also provides the foundation for reusable asset models, configurable lifecycles, dynamic forms, and unified inventory views. Together, these capabilities connect administrative configuration with the information and actions teams need throughout asset operations.
One foundation for diverse assets. More consistency with less configuration.
Why UDM Matters
Configure once and reuse across the hierarchy. Reduce duplicate attribute setup through inheritance.
Extend asset coverage through configuration. Add category-specific information within a shared structure.
Keep forms relevant. Present applicable attributes and exclude inherited custom fields where unnecessary.
Simplify ongoing administration. Manage shared definitions at the appropriate parent level.
Support consistent asset operations. Connect asset definitions with forms, lifecycle behavior, and inventory views.

Traditional ITAM vs Newly Architectured UDM
Traditional ITAM often requires repeated attribute setup across asset categories, increasing administrative effort. SummitAI’s Unified Data Model (UDM) replaces repetitive configuration with a shared hierarchy that lets attributes inherit across applicable levels. Reusable models, dynamic forms, and configurable lifecycles help teams manage IT and non-IT assets with greater consistency and flexibility.

Let’s explore the following use-case briefly, which will be expanded in subsequent pages:
Use Case User Persona: ITAM Admin | Solution |
Sam manages assets for the New York office, including laptops, desktops, and office furniture. All assets require Location and Department. However, Network Domain applies only to IT assets, and Battery Capacity applies only to laptops. Sam needs to capture the following information: Laptop LAP-001: Location = New York; Department = Finance; Network Domain = corp.example.com; Battery Capacity = 65 Wh. Desktop DESK-001: Location = New York; Department = Finance; Network Domain = corp.example.com. Battery Capacity is not applicable. Office Chair CHR-001: Location = New York; Department = Finance. Network Domain and Battery Capacity are not applicable. Sam wants to configure common fields once while ensuring that each category form contains only relevant attributes. | To achieve this use-case, perform the following steps: 1. Configure common attributes at Level 1 — Universal. Make Location and Department available at the Universal level. Both the IT and Non-IT branches inherit these attributes through Level 3 and into their Level 4 category forms. Users can therefore enter New York and Finance for the laptop, desktop, and chair records. 2. Configure the IT-specific attribute at Level 2 — IT. Add the custom attribute Network Domain as a text field under IT. Applicable child asset types at Level 3 and category forms at Level 4 inherit this attribute. Users enter corp.example.com for LAP-001 and DESK-001. Because the attribute originates in the IT branch, it is unavailable in the Non-IT branch and does not appear on the Office Chair category form. 3. Inherit attributes through Level 3 — Asset Types. Under IT → Fixed, retain the inherited Location, Department, and Network Domain attributes for the Laptop and Desktop category forms. Under Non-IT → Fixed, the Office Chair category form inherits Location and Department, but not Network Domain. 4. Configure the laptop-specific attribute at Level 4 — Category Form. Add Battery Capacity to the Laptop category form as a numeric field with the unit Wh. Users enter 65 for LAP-001. Because the attribute is configured specifically for Laptop, it is unavailable on the Desktop and Office Chair category forms. Result: LAP-001 captures all four attributes, DESK-001 captures three, and CHR-001 captures two. Shared fields remain consistent, while branch-specific and category-specific fields appear only where applicable. Important: Inheritance makes attribute definitions available to child levels. Values such as New York, Finance, and corp.example.com are entered for each asset record; attribute inheritance does not automatically populate those values. |