Simple and Versatile Navigation – Tree View

The system can present a so-called ‘tree view’ of the Assets Register. The hierarchy of Client, Location, Assets and Parts, etc is presented on screen, enabling you to view all the interrelationships and navigate your way around your enterprise’s entire asset population. The tree view is the most convenient and intuitive way in which to explore and scrutinise the enterprise’s asset population, as well as its organisational structure.

And it’s interactive. You also have quick access to the compendium of information held for each location, system and equipment item. You can drill-down to find the information you need; click on any item to view its full details. For example, you can view the asset list at each location, a single asset’s assembly hierarchy down to part level, find out where any particular part is used, who supplies it, the technical specification, see a picture of it – and study any other information filed against it.

You can expand or collapse branches to drill down to your level of interest. Finding those haystack needles is easy peasy with Pirana.

The ‘Assets Tree’ is in essence a 2D model of the physical structure of your enterprise. It’s a hierarchical, branching representation of the inventory of physical assets present within the enterprise’s geographical locations and organisational units. A picture is worth a thousand words so, like the map of the London Underground, tree view is a boon to navigating your way around the system. You’re able to see at a glance where everything is located and the maintainable parts for each asset or sub-assembly.

A comprehensive assets register, with its tree view, should include all items of maintenance significance, that is, those items critical to the enterprise’s operations which require maintenance attention – the list will obviously include: estates, buildings, plant, machinery and equipment.

The pictorial model depicts the ‘where’ and the ‘what’ in relation to the enterprise’s assets. Moving down the tree, the hierarchy changes from being location-centred to item-centred. Prime locations, a Site for example, may have a multiplicity of sub-locations, each with many asset systems. Each prime asset system, for instance, a production line or manufacturing cell, will have a multiplicity of equipment assemblies and sub-assemblies, further decomposable into their discrete, maintenance-demanding parts. Pirana can provide all this information at a glance.

With Pirana, it’s easy to set up, track and control as many geographical and assembly levels – so-called asset indenture levels – as you want. You can add as many branches or levels in the structure as you like. However, as always, you should strive to keep everything as simple as possible. The most appropriate number of indenture levels for your particular circumstances will depend on the size of your organisation, its industrial sector, your own maintenance management strategy and, of course, where you are on the journey to best practice. You should only increase the number of levels when it’s really necessary for effective and efficient maintenance planning and control. Most organisations will gradually build their enterprise asset model over time – according to the flow of events and the Engineering Manager’s own needs. A few may well wish to build a comprehensive physical model of their asset-intensive enterprise from day one. It’s your choice.

Tree view saves you loads of precious time; everything’s so much clearer and moving around the system is simplicity itself. It’s a real boon when you’re facing the complexity of multiple locations, each one with a myriad of equipment items.