Following our series from last month, we continue discussing the benefits of Location Based Modeling, or creating a Location Hierarchy with a 1:1 relationship to Assets. If you missed the first article, check out EDI’s Blog for April, Using Location Hierarchy with a 1:1 Relationship to Assets (Part 1). There are multiple benefits to creating Functional, Geographic, and Electrical Systems, based on Location Hierarchies, over maintaining a simple Asset parent/child relationship in an EAM system.
*Written by Scott Yates, Senior VP, EDI
|Benefit of Location Based Modeling||Details*|
|1. Maintains EAM records automatically||Due to our one to on relationship between the “Functional Location” and the Asset, we can actually assign PMs and Routes to the “Functional Location” instead of the Asset record. What this means is that when an Asset is installed or swapped, it automatically takes on the PM schedule and routines set for the “Functional Location”. There is no need to update any PM, Route or Job Plan records when Assets are moved or swapped.|
|2. Capture of Spare Parts (Bill of Materials, BOM)||Location Based Modeling would allow you to navigate and present System, Subsystem, and Asset structures. For example, I could “get to” the Spare Parts list for an Asset by doing a direct attribute search, descending the Geographic Hierarchy, or descending the Functional Hierarchy. I could also easily present a comprehensive Bill of Materials utilizing any of these contexts.
One related concept is how Location Based Modeling supports more flexible “Like for Like” replacement of Assets. Utilizing the one to one relationship of the “Functional Location” to the Asset, you can define System-Based requirements for any Asset to be installed on the “Functional Location” that can be used as the criteria for replacement when replacement is needed. For example, if there is “diameter” requirement for an Asset that is to be installed at a certain spot on a specific system, you could define that on the “Functional Location” and know that a number of replacement Assets could be used at that location as long as they meet the requirements. You may not have to replace the identical make and model that is there right now. This can also help fight the “Parts Ratcheting Effect” which happens when components are simply replaced with some “better” than what was there before versus truly understanding the needs of the system.
|3. Budgeting, Forecasting, and Capital Planning||Where Location Based Modeling again differentiates itself is its ability u to organize the historical and static cost data and PM schedules/forecasts by the various contexts of the Location systems. For example, the ability to easily isolate the PMs for a specific functional system and run a forecast report or easily compile the PMs for all systems of that type in a building and run the report. At EDI, we can also specify primary roll-up points.|
|4. Captures Enterprise Criticality ratings for Asset, Subsystem, and System levels of the hierarchy||This is another win for Location Based Modeling. The Criticality of an Asset is primarily driven by the function it performs, not just what it functionally is. For example, an electrical breaker that feeds an FPLS System would be inherently more critical than one that simply feeds some basic office equipment. This context is provided by the Functional Location.
In most cases, you would define and set criticality once across the System components and then never have to make any criticality updates manually in the system again, as that information stays with the Location and is inherited by the Asset upon moves.
|5. Supports planning and scheduling work on all Assets requiring work, at a Location||For the same reasons that navigation and reporting are more robust, scheduling and planning are more robust in a Location based model as well. Any of the system contexts can be utilized to query for and package work together. For example, you could use query leveraging the Geographic System to identify all work in a specific Geographic Location or area. You could use the Electrical Hierarchy to easily isolate all equipment tied to particular circuit or breaker when you know you need to lock out/tag out that area anyways. You could isolate and package all Work Orders outstanding for a particular Functional System (e.g. FPLS) when you know you are taking that System offline already anyways. This includes identifying and, potentially, short-cycling upcoming PMs based on window of opportunity.
In a very similar way, the Location Hierarchies can be utilized for understanding impact of a failure or planned outage based on the relationships of the “Functional Location” to other “Functional Locations” that it is connected or related to on the various hierarchies. This can be very powerful in notifications for planned maintenance or failure response as well as in simply trouble-shooting undiagnosed failures.