Avoiding LDAR Tagging/Documenting Pain Points, from the Blog Formerly Known as A Better Blog (Part 1 of 2)

This week’s LDARProjects two-part blog is all about avoiding pain points during LDAR tagging/ documentation and pays tribute to the late singer/songwriter, Prince. How many song references can you spot? Hint: the answer is not “7” (that’s one  … ). Also, if you’ve been reading our blog, you know that every week we’re giving something away. This week, it’s an SOP for documenting LDAR in GuideWare™. Scroll to the end to get it delivered to your inbox today.

It's just hanging tags and documenting components into LeakDAS® -- at least that’s how one refinery described their LDAR inventory project to us. It’s a common thing to hear in industry circles, but to us it sounds a lot like “When Doves Cry.”

Managing tags and documenting LDAR equipment may not seem challenging on the surface, but the process of consistently tagging and documenting tens (if not hundreds) of thousands of LDAR components is time intensive, and traditional means leave room for error. Potential pain points include things like hanging tags in illogical route order or inconsistent with site SOPs and minimal use of “temp-tags” (or “A-tags”).

Opportunities for slip-ups abound. Take, for example, the flow transmitter pictured at right. Facility regulations combined with site-specific procedures could result in one of over a dozen possible instructions for how to hang tags properly on this single piece of equipment. Without proper planning, questions remain: How should tags be hung on the valves to not obstruct their use? Should a tag also be hung for the flow transmitter itself?..

But these questions, and many more, can be addressed with two, straight-forward (but time-consuming) steps to ensure that LDAR tags are hung in “good route order” according to site-specific procedure.

1. Develop Tagging SOPs with Pictures. This week, we spent considerable time with the site LDAR contractor and coordinator to review our tagging SOP and ensure hanging and routing according to site-specific SOPs. Nevermind that we had to strip and re-hang 232 tags after Day 1 of tagging, as well as another 100 tags after Day 2 of tagging. It’s our job to ensure that the site LDAR contractor is happy with our tagging, routing, and documenting at the end of the project. Take our word for it, there’s nothing like the feeling of looking at a newly tagged process that adheres to site-specific protocol and saying to oneself: “U Got The Look.”

2. Prepare Training and Utilize Tagging SOPs for QA/QC. A Tagging SOP is great-and-all, but it has to be read, understood, and implemented in order to be effective. This is why we suggest incorporating your Tagging SOP into training slides for the team. During a project kickoff, one can usually secure a camera and/or hot work permit to take pictures of typical equipment, as well as incorporate the pictures into training and QA/QC resources for the team.

This leads us to documentation, but we’ don’t want to overwhelm, so we’ll check back in tomorrow with Part 2 where we’ll show you how we avoid pain points during documentation for LDAR inventory projects. Oh, and click below and we’ll send you the freebie SOP. See you tomorrow!

Get a Go-By Documentation SOP, Click Here!