Technical Checklist for Instrum.

Instrument Index + I/O list

Client init. sign date

Project Originator
Project no. Checker
Drawing/doc. no. Lead Eng
Item/tag/line no. Vendor/Contractor

Checked by Remark no.

(Y/N/NA) (see below)
No. Description of item to be checked Orig. Check
General
1 Is the form (the titles of the columns, layout, format) in accordance with the project
specifications
2 Is the tagnumbering system in accordance with the project specifications
3 Are the tagnumbers unique (only used once)
4 Are the columns completed with the relevant data for each tagnumber, i.e. Service
description, location, instrument type, instrument size, pipe class, tracing
requirements, I/O type, line size, range, etc…)

5 Does the information appear only in one column and always in the same column (no
double information)
6 Are all tagged instruments, shown on the P&ID's (or package P&ID’s), listed
7 Are all tagged instruments and instrument signals shown on vendor documents
(instrument schemes) listed (This also applies to software signals that require
handling by the instrument group (mapping and testing)
8 Have all tagnumbers been allocated
9 Are RATS (=Ranges, Alarms and Trip Settings) indicated
10 Are Package supplied instruments and signals included and marked as such
11 Are notes applicable to instruments covered by a remark in the remarks field
12 Are tags grouped correctly by loopnumber
13 Are all instrument items on the P&ID's accounted for with a correct “Status” field, i.e.
“New”, Demolition” or “Replace”, etc) entered

Lessons learned previous projects

14 Define template at start

Please define special items to be checked

15 Package unit instruments + Battery Limits

Note: this sheet shall be stapled to the check print and filed in the appropriate hardcopy folder

REMARKS & HOLDS

Released
No. Description Date By

Page 1of 1
________________________________________________________________________________________________________________
465837090.xls