Hello Irete
There are two different tagging systems that can be used in combination to meet all your requirements:
Functional location tagging. This is the P&ID tag, which in your example will be P1501. This tag will be on the DCS and also shown in the field by means of a tag. The functional location tag denotes the position, i.e. that a pump of certain characteristics should be installed in that location on the export system.
Asset tagging. This is the tag that uniquely identifies a specific pump, e.g. ABC. The asset tag will not be shown in either the P&ID or the DCS. However, it will be on the pump itself. Of course, the s/n can also be used, but that will be messy, compared to a uniform coding method.
Hence, in the field there will be two tags:
- One (functional location tag) on the plinth where
a pump should be installed
- Second (asset tag ) corresponding to
this pump specifically
In this example, the CMMS equipment hierarchy will be built based on systems, one of which will be the export system. For that system and in the next level below, it will contain the export pump with the functional location P1501. The functional location will be a "parking space" where a specific pump will go, ABC.
When this pump fails and it needs to be overhauled, the specific ABC pump will be removed from the functional location P1501and transferred to the workshop. Another pump of similar characteristics, say DEF, will replace it in the functional location P1501. Note that the replacement will take place both in the physical location and in the CMMS hierarchy. When the ABC is overhauled, it will be returned to the Stores and it may have to be used in a different functional location.
In this way, the machine and failure history, as well as the corresponding costs, remain both with the functional location and the specific asset. The functional location P1501 will have the history of ABC and DEF, while they were in service in that functional location. Whereas the pumps ABC and DEF will retain their respective histories in every functional location or overhaul that they have ever been.
It can be seen that with this method, the P&IDs and DCS tags will always remain the same avoiding unnecessary stoppages, work and safety risks to operating personnel, while the maintenance records will be considerably more accurate.
It is worth mentioning that while every component in a system will have a functional tag, asset tags are only needed on the components where there is a value in going to the trouble of assigning them an asset tag.
For more information, you can also see: ISO 14224:2016 Petroleum, petrochemical and natural gas industries - Collection and exchange of reliability and maintenance data for equipment
Best regards
Michalis
------------------------------
Michalis Hadjiandreou
Manufacturing Reliability Engineer
Edinburgh
------------------------------
Original Message:
Sent: 01-21-2021 04:09 PM
From: Irete Olorunfemi
Subject: What's the Best practice for Asset Tagging, Update CMMS and P&ID's
Hello Everyone,
I lead the CMMS team in my department and some challenging questions on equipment tagging has come up in our on-going Asset Integrity Management project.
If an equipment is bad and replaced, do I have to assign a new physical tag for the new equipment or retain the tag used for the old equipment?
for example, an export Pump P 1501 with a 5yr maintenance history is replaced with a new Pump, do you assign a new tag for the new export pump or maintain P 1501 for the new pump?
If yes, does this apply to all equipment replaced on site?
If yes, that implies that our client will have to change the P&ID's to reflect the new tags installed, right?
Another major concern is the Distributed Control System DCS. I believe the plant has to be shutdown temporarily for the tags to be updated in the DCS.
The bone of contention is that tags on the P&ID document and DCS will not change even if an equipment is replaced with a new one, and that the new equipment maintains the physical tag of the old equipment replaced. We are also considering the cost implications, complicated procedure for management approval and other issues.
I will appreciate your valuable inputs to help us tackle this issue professionally and safely.
Thanks in advance.
@Jimmy Dean, @Richard Lamb @David Downs, @Manjish Naik, @Sarah Lukens, @Gregg Pacelli @Steve Stum, @Edward Espinosa I have read your article's/posts regarding CMMS, I'll appreciate your insights. Thanks
------------------------------
Irete Olorunfemi BEng
Cainergy International Limited
Abuja
------------------------------