Idalia includes first-class support to store and manage relationships between asset components. This lets asset managers build libraries of assemblies and subassemblies into their asset registers.Assemblies can be used directly in Idalia’s workflows. For example, assemblies can be allocated to projects and transport orders.
In Idalia, an assembly is any asset type that is composed of one or more “child” asset types.A component is just an asset type that does not have child components. These are like base-level “units” of your register that you can’t or don’t want to break down further.Assemblies can have other assemblies as children. We call these child assemblies “subassemblies”.
Each asset type that is part of an assembly—either as a child component or subassembly or as the top-level assembly itself—can be visualized in the asset register.Each asset type page has a Relationships section that shows these graph. Each node represents an asset type, and the edges represent the relationships between them. Parents are above children. Each edge has a label displaying the quantity of the particular component/subassembly in the assembly.