Loop Checking and Field Instrument Testing Procedure

Loop Checking and Field Instrument Testing Procedure
1 of 7
http://www.controlglobal.com/blogs/controlling-interests/loop-checkin...
LOGIN | REGISTER
MENU
Control's editors weigh in with timely insights and tidbits on goings-on in the process automation world,
mostly news and technology but also interesting perspectives gleaned from our daily conversations with
end users and the challenges of the craft.
Category: Implementation Loop Analysis Loop Performance Usability

Submitted by Katherine Bonfante on Thu, 10/04/2012 - 10:00
Everybody knows that loop checking and field instrument testing is the last piece of the puzzle in each project
before commencing the commissioning of any system. It is time-consuming and depends upon the
completion of other systems like piping, electrical equipment, control valves etc.
Each contractor or company has its own procedure and common practices for instrument loop checking and
functional testing. I found this forum is good place to discuss this topic in more detail, for example:
1. Can we have a common or guide line procedure for loop checking?
2. Can we illustrate all the required drawings, specification and forms required for loop checking?
3. Can we build a flow chart for loop checking which illustrates the rule of operation, maintenance,
engineering and inspection for example?
Login or register to post comments

52895 reads
Permalink
7 Comments
We welcome your thoughtful comments. Please comply with our Community rules.
All comments will display your user name.
Want to participate in the discussion?
29-10-2015 11:42
2 of 7
REGISTER FOR FREE
Log in for complete access.
Submitted by santhiraj sathanna on Fri, 09/06/2013 - 08:58

This is a very good topic for discussion. We do the following in our organisation 1.A
detailed loop check format is prepared for each project 2.Above is based on latest I/O list , P&ID and
process narrative. 3.For each I/O point, all connected details/elements like PLC/DCS I/O module,Panel
Terminal Block, Marshalling panel Terminal Block, Junction Box Terminal Block,Instrument/Final Control
element tag, Service description,calibration range,cable tag.... 4.We do this testing by involving owner's as
well as prime EPC bidder's Engineer as witnesses. After successful completion, the document gets signed by
them. We follow the same procedure for commissioning the logic as well as to demonstrate the same
to end user! This is time consuming and we do it religiously to eliminate last minute surprises.
Reply
Submitted by on Tue, 10/29/2013 - 12:24
I fully agree with all 3 points. A guide is really needed. I takes much time to get agreed such procedure in
every new project and a unified approach would be very effective here. To the second point I may add that a
list of such documents would be very useful as well to avoid creating of a huge dossier and got all needed
papers in place. Templates for certificates would be fine. As to the third point I'd a recommended list of
personal of performing and witnessing parties. Mikhail Aravin, Senoir Instrument Commissioning Engineer.

Reply
Submitted by Edward Smigo on Fri, 12/27/2013 - 10:45
The loop testing procedure can vary depending on the instrumentation and I/O infrastructure. A
foundation fieldbus or Profibus PA based system would be different from a system using conventional or
HART instrumentation on a system with HART I/O cards. While one can perform a loop test with a
handheld communicator when HART I/O is not present on the automation system that process would require
multiple people similar to performing loop tests with conventional instruments. One benefit HART
instrumentation has over conventional is the non intrusive nature of the testing. One does not need to break
the loop to insert a mA simulator. HART instruments have a Loop Test method that allows the tester to drive
the mA output of the instrument from a hand held communicator or an Asset Management Software
application, When using Asset Management software, testing can be done more efficiently because a single
person can be commanding devices from one window and observing results on another. An additional benefit
when using Asset Management software is that multiple instruments can be put into loop test simutaneously
which allows one to incorporate interlock logic checks along with the loop tests which further streamlines the
comissioning process. Since loop tests are often the final step before start-up, and projects
schedules often slip, there is always pressure on the loop testing team to gain efficiencies to pull in the plant
startup milestone.
Reply
Submitted by Tom Dotts on Tue, 12/30/2014 - 08:30
Unfortunately, even today's large manufacturers have lost qualified process control specialists and
engineers, leaving sometimes, unqualified personnel to decide how a "system" should be validated. A
systematic approach is necessary and a legitimate step towards ensuring the "completeness" of even the
smallest of project, upgrade or change to or within a BPCS or SIS on the plant floor. Of course regulations
apply to safeties, but many times the even the fundamentals of instrumentation go unchecked and now
become a liability. Standardization is needed - especially within chemical and petro-chemical applications.
29-10-2015 11:42
3 of 7
T.Dotts, Contract EI&C Technician / Project manager.

Reply
Submitted by Charles Palmer on Wed, 01/14/2015 - 03:23
I would like to share some perspectives : Loop testing and plant commissioning done in-house is one
aspect. Naturally the requirement for policies and procedures is mandatory ( as in both cases) Things change
slightly when this work is been done under contract by a 3rd party. Once again the policies and procedures
are required. FAT and SAT procedures should be issued to the supplier/contractor within 30 days of contract
signature. As a Consultant, I have witnessed so many poor FAT and SAT company procedures in many
different countries ( Cultures if you like). This has compounded poor FAT testing into total SAT failures as the
fault could not be isolated to Panel or Field . Many hours could have been saved if the bookwork had been
done up front.
Reply
Submitted by Sankar Kumar R on Tue, 02/24/2015 - 03:43
I would like to summarize the requirement prior to start the loop check activity as follows: 1. SAT
of DCS/ESD/F&G and IAMS system shall be completed and ready with all pre-requisites completed. 2.
Total IO's shall be divided into loops & Loop Folder shall be prepared and approved from PMC/Client. 3.
Loop folder shall contain the following documents as a minimum : a) Loop test record format (To enter the
details of the Instrument subjected to loop check and the master instrument used). b) Instrument Data
sheet(s) related with the loop. c) P&ID sheet related to the Instrument(s) d) Instrument(s) loop drawing
(derived from Intools which shall contain termination details from Field through JB's to Rack Room) e)
C&E sheet (For logic checks) f) IO Point Database (To refer : Ranges, Alarm Points, Controller action
etc) g) Calibration sheet of Instruments in loop. h) Observation sheet (To note down any observations during
loop check/logic check activity for necessary corrective action). 4. Prerequisites like HVAC, Utilities shall be
ensured 5. Loop check shall be carried with Handheld communicator / Calibrators or from IAMS system (For
both FF & HART devices). 6. The checks shall be witnessed & loop folder documents shall be
signed by DCS contractor, EPC contractor, PMC & Client. The preparation of above said
document is time consuming but these will ease the loop / logic checks as all data's will be available in a
single folder. This is the procedure we are following in our Greenfield Petrochemical Project.
Reply
Submitted by jberge on Tue, 09/08/2015 - 11:44
The details of 4-20 mA loop checking is slightly different for each device but the general principle is the
same. The basics of the loop testing procedure is explained in the loop checking tutorial found here: <a
href="http://www.eddl.org/DeviceManagement/">http://www.eddl.org/DeviceManagement/</a>
Reply
RSS feed for comments on this page | RSS feed for all comments
29-10-2015 11:42
4 of 7
E-Newsletters
Digital Editions
Biweekly updates delivering feature articles, headlines with direct links to the top news stories that are critical
to staying up to date on the industry company news, product announcements, technical issues and more.
Subscribe Today.
Past 7 Days
Past 30 Days
Past 6 Months
All Time
29-10-2015 11:42
5 of 7
Contact Us
Advertise
Media Kit
Rates & Spec
29-10-2015 11:42
6 of 7
Privacy Policy
Legal / T&C
Voices
Blogs
Out of Control Cartoons
White Papers
Multimedia
Events
Products
Technology Roundups
E-lits
Subscribe
Digital Edition
Issue Archive
Reprints
Jobs
Knowledge Center
Microsites
Company Profiles
Site Map
My Account
Newsletters
Social Media
RSS
Contact Us | Advertise | Privacy Policy | Legal Disclaimers, Terms & Conditions

Copyright 2004 - 2015 Control Global. All rights reserved.
P: 630-467-1300 | 1501 E. Woodfield Road, Suite 400N, Schaumburg, IL 60173
Chemical Processing | Control | Control Design | Food Processing | Industrial Networking | Pharmaceutical Manufacturing |
29-10-2015 11:42
7 of 7
Pharma QBD | Plant Services | Wellness Foods
29-10-2015 11:42

Loop Checking and Field Instrument Testing Procedure

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Loop Checking and Field Instrument Testing Procedure

Uploaded by

Copyright:

Available Formats

Loop Checking and Field Instrument Testing Procedure

Category: Implementation Loop Analysis Loop Performance Usability

Login or register to post comments