Asset Hierarchy

in many industrial operations, asset structure information is spread across erps, mes systems, historians, spreadsheets, and individual edge devices there is no single source of truth, asset ids differ between systems, and local definitions on edge devices can drift from enterprise standards asset hierarchy gives you a central place to define and govern your enterprise asset structure you manage it in one place and deploy models and instances to your litmus edge devices an asset hierarchy organizes your physical operations into a structured tree, from the enterprise level down to individual work units litmus edge manager includes a hierarchy based on the isa 95 standard enterprise > region > site > plant > area > work center > work unit use the asset id field on each work unit instance to map litmus assets to records in external systems such as microsoft fabric note asset hierarchy is available in litmus edge manager 2 34 0 and later you must enable industrial asset hierarchy management in settings > experimental features before using this feature key concepts hierarchy template defines the allowed levels and structure for your enterprise litmus edge manager includes system templates based on the isa 95 standard see manage hierarchy templates hierarchy node a single item in your hierarchy, such as a site, plant, or work center work unit the leaf level of the hierarchy, representing an individual physical asset work unit nodes cannot have child nodes work unit type a classification for work units, such as boiler or spray dryer work unit model a reusable model definition used to create work unit instances each model belongs to one type, and one type can have many models work unit instance an actual asset created from a work unit model and placed at the work unit level in the hierarchy one model can create many instances asset id an external identifier on a work unit instance used to map it to records in another system, such as microsoft fabric approaches you can build your hierarchy in two ways hierarchy first define the enterprise structure first, then create work unit instances and place them in it recommended for new deployments model first create work unit models and instances first, then assign them to hierarchy locations useful if your models already exist you can also import hierarchy data and work unit instances from a csv file access asset hierarchy to access asset hierarchy, in the left navigation under modeling , click asset hierarchy next steps create an asset hierarchy manage hierarchy templates experimental features