100% Employee Owned, Founded 1954

855.889.0092

100% Employee Owned, Founded 1954

855.889.0092

100% Employee Owned, Founded 1954

855.889.0092

Commissioning For Process Controls: The Pursuit of Excellence

Randy Goff | August 23rd, 2017

Commissioning is a team effort to document the continuity of a project as it moves from one project phase to the next. To achieve commissioning excellence requires that the testing documents be accurate and written in an orderly fashion. The Documentation Gatekeeper, a.k.a the Commission Lead, is responsible to develop, teach, implement, and guard the integrity of the process to produce accurate testing documents.

If a device to be tested gets checked incorrectly or missed altogether, the likely cause is a mistake on the testing document. We have all heard and used clichés like: “Let’s not let anything fall through the cracks,” or “I want to make sure that we are all on the same page.” These clichés are perfectly appropriate for this discussion on commissioning excellence. But one cliché is more appropriate, “We are ALL human.” If we were more than human, there would be no need for testing. Therefore, one goal that is necessary through all phases of commissioning should be to minimize the “human-ness” in document management.

Documenting and Minimizing Errors

It is a fact of life that we all make mistakes and that there are costs involved with each one made. With incorrectly tested or missed devices, the cost is an unhappy customer when he finds the error himself. When the mistake is found by the tester, the price is time. Time to research the discrepancy and determine the path for correction, e.g. “Is the mistake in the document or in the field?” But for now, let’s focus on document errors and minimizing them.

At some point, we must trust a commissioning document at 100%, like a design specification, standard operating procedure, P&ID, or I/O list. Even though a mistake in one of the base documents will permeate through to the testing documents, those mistakes are not in the scope of this blog. The base documents have been approved as accurate and issued to the test team. Once issued, data must be extracted from these documents and inserted into the test documents.

Appropriately Value the Commissioning Process

It is this process that must be guarded for errors. During commissioning there is little to no time to go back and verify if the test documents are still accurate or if the testers are qualified to test. “On the other side of that coin,” the document gatekeeper cannot wait too long to hit the PRINT button and hand out the test documents. Otherwise, you have testers waiting in the field for their tests. Yet in some cases, the least experienced engineers on the team (the new guys) are given the task of creating the test documents. With the significance of the process of creating, maintaining, and proofing the commissioning documentation, should the new guys be excluded? Hold that thought…we were all the new guy at one time!

Now that the test documents are complete, it is time to hit that PRINT button. But the process is still vulnerable because we all know that design specs can change mid project. How does a single change make its way full circle through the new design, the drawings, the design specification documents, the FAT & SAT, and be implemented without “slipping through the cracks”? The Documentation Gatekeeper. The Gatekeeper will not allow a design change to be implemented without first passing it through the process of documentation management and proofing.

What is the role of the Gatekeeper, a.k.a. the Commissioning Lead? To develop, teach, implement, and guard the integrity of the process. He/she will train and qualify all other engineers (including the new guys) who will be issued these tasks. Cross Company is ready to put our commissioning expertise to work for you. Contact us to discuss your upcoming projects.

Cross Group - Process Control Integration

Case Study: APACS DCS Migration to Siemens PCS 7

Josh Dalzell | November 30th, 2018 An industrial utility service company in Kentucky needed to upgrade and migrate its distributed control system (DCS), which came with a few challenges. DTE Calvert City (DTECC) made the decision three years ago to upgrade their obsolete Process Suite HMI to APACS OS. For 15 years, APACS DCS had been

Read More »
Cross Group - Process Control Integration

How To Evaluate a Systems Integrator for Your Distillery

John Loose | October 30th, 2018 Evaluating a Systems Integrator for upcoming projects is an important part of the project process and the decision typically affects more than one project. This will end up being a relationship that lasts over a number of projects and multiple years. Documentation A well-established documentation system is a key to

Read More »
Cross Group - Process Control Integration

8 Factors For Process Automation Project Success

Robbie Peoples, P.E. | September 24th, 2018 Complex integration projects can present a level of ambiguity even for seasoned project managers. Keeping a close watch on budget and schedule are critical for success, but are not enough to ensure the project is a success in the eyes of a customer. Maintaining customer satisfaction can be the most

Read More »
Scroll to Top