Project deficiencies and Punchlist Management

This article was originally published on LinkedIn, March 2018.

Introduction

“A problem well put is half solved” – John Dewey (classical pragmatist philosopher) . Great quote for this article.

Processing the deficiencies (or punchlists) of an ongoing work is a key activity in any successful project completion. The goal of this processing should be to provide a dynamic “identify-fix-accept” cycle and not to merely list failures.

But as it happens with many data management processes in projects (Test packs, Turnover Dossiers, Materials, Instrument Loops, Contracts, etc.), they could become a nightmare if not properly managed.

Typical Punchlist Management problems

Some of the common problems during the punchlist processing are illustrated below.

Although some of these occurrences might be detected and diluted by the Punchlist Team (or Coordinator), others are intrinsically related to the data management process itself; they could be prevented or substantially reduced by a good database application.

Example

As they say, “examples and actions speak more than only words” so here is a 90 sec video-demo that shows an example of how practical and intuitive is to process punchlists using “Effective,” an MS Access/SQL/VBA Database application that I’ve developed for this purpose.

The example shows a QAQC Piping user that reviews a fictitious System Turnover Dossier: 100-XYZ-PI-0220: “Acid Gas Enrichment Train 2 “, then creates a 7 item-punchlist, generates the punchlist document and transmit it to the contractor within the same application.

Although the previous example shows punch lists originated from a dossier review process, it is more common that they come from a system walkdown as part of the Project completions process.

the goal should be to provide a dynamic“identify-fix-accept” cycle and not to merely list failures..

“Effective” could be used in other industries that require a “deficiency-solution” processing and tracking (i.e. Construction, let’s say system 100-XYZ- WND-01: “Front Windows of Building”).

A typical punchlist cycle includes the following processes:

1.- Walkdown or Review Turnover Package Dossier. ( Identification)

2.- Punchlist. (Description and details provided)

3.- Upload into the Punchlist Database. ( Recording)

4.-Transmit (Communication)

5.- Fix ( Solution)

6.-Clear -Accept (Confirmation – Tracking)

The video-demo showed the first 4 processes, where the process #6 “clear-acceptance” could be done either electronically (electronic signature or nip) or with a traditional punchcard/punchlist; it all depends on the project procedure..



It is worth to mention that the bulk upload function should be exclusive to the Punchlist or Completions Administrator Team due to the risks implicit in the operation itself.

Conclusions

Punchlist processing should not only be a static list but a dynamic mechanism that facilitates the identification, tracking, and solution of deficiencies in a project.

Regardless of the responsibilities of the punchlist or completions team (or coordinator), a database system should be able to facilitate the process.

“Effective” is a database I developed based on my experience as System Completions Database Administrator, with easy and intuitive screens and commands that reduce focus dispersion. “Multi-tasking” within a “Single-tasking” process.

As the American philosopher John Dewey cited almost 80 years ago “A problem well put is half solved”.

This article was originally published on LinkedIn, March 2018.

Introduction

“A problem well put is half solved” – John Dewey (classical pragmatist philosopher) . Great quote for this article.

Processing the deficiencies (or punchlists) of an ongoing work is a key activity in any successful project completion. The goal of this processing should be to provide a dynamic “identify-fix-accept” cycle and not to merely list failures.

But as it happens with many data management processes in projects (Test packs, Turnover Dossiers, Materials, Instrument Loops, Contracts, etc.), they could become a nightmare if not properly managed.

Typical Punchlist Management problems

Some of the common problems during the punchlist processing are illustrated below.

Thanks for your feedback and comments to my previous post “Test Pack management.” Spring is just around the corner, but temperature is still around -10 C it seems Winter is still refusing to wave goodbye.

EO

ericocampo@ericocampo.com

www.ericocampo.com

Eric Ocampo is a Project Management Professional and Microsoft Access Certified Specialist with an Electronic Sciences Degree. He is a proactive Database Administrator/Developer that has worked in Construction, Oil & Gas projects in North and South America, and the Middle East since 2001. He has worked in Mechanical Completions as SCDBA of QEDI and WinPCs systems, and as a Database Developer, he has developed applications for Project Turnover, Completions, Materials, Preservation, Dossier reviews, Weld Tracking, Instrument loops, etc.

His early experience includes a role as MWD (Measure While Drilling) Operator with Anadrill Schlumberger.

Leave a Reply

Your email address will not be published. Required fields are marked *