24.10.2012 Views

CONTENTS - Central Public Works Department

CONTENTS - Central Public Works Department

CONTENTS - Central Public Works Department

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

112 SECTION 18<br />

SECTION 18<br />

SALE OF TENDER DOCUMENTS<br />

18.1 General<br />

(1) The tender documents should be prepared and kept ready for sale to the tenderers before the<br />

Notice is actually sent to the press or is pasted on the Notice Board. Every contractor desiring to<br />

purchase the tender documents shall be asked to give a written application. It is the responsibility<br />

of the Executive Engineer/Assistant Engineer to see that tender documents are made available<br />

to the contractors as soon as the application is made. The application may be made by the<br />

contractors in the prescribed form shown at Appendix 21.<br />

(2) The tender documents should be sold to only those contractors who fulfill the eligibility criteria set<br />

out in the notice, and who are not near relatives of the Divisional Accountant or the Superintending<br />

Engineer or Executive Engineer or Assistant Engineer/Junior Engineer of the Circle in which the<br />

work is to be executed.<br />

Note: A near relative includes wife, husband, parents, in-laws, children, brothers, sisters, uncles, aunts<br />

and cousins.<br />

(3) Any tender form that is issued, either for sale or for office use, should be issued under the signature<br />

of the Divisional Officer or the Sub-Divisional Officer, as the case may be.<br />

(4) Para 17.1 may be seen regarding posting of tender notice on the website.<br />

18.2 Sale of tender documents to registered contractors (for normal works)<br />

18.2.1 Tenders shall be sold to eligible contractor those fulfill the criteria as stipulated in the tender<br />

Document.<br />

18.2.2 Sale of tenders to contractors with a blemished record<br />

(1) (i) If the Executive Engineer concerned receives adverse report against any non-CPWD<br />

contractor, either from the <strong>Department</strong> in which he is enlisted or from any other <strong>Department</strong>,<br />

he should stop issue of tenders to that contractor on the basis of such a report. The<br />

Executive Engineer should, however, communicate the information to his Superintending<br />

Engineer for record and for approval of the action taken or proposed to be taken by him.<br />

(ii) On receipt of a case of adverse performance/ misbehaviour/threatening of site<br />

staff or any other such reasons, the CE, shall issue show cause to such contractors<br />

and after considering their reply, he shall have full powers to debar non-CPWD<br />

contractor for a period as decided by him. Such debarred non-CPWD contractor<br />

shall be ineligible to take up any work in CPWD, MoEF, PWD (Govt. of Delhi) etc.<br />

all over India during the period of debarring.<br />

The Chief Engineer shall endorse a copy of such order to CE(CSQ) who shall post names<br />

of such contractors on CPWD website so that every field unit of CPWD/MoEF/ PWD<br />

(Govt. of Delhi) becomes aware and does not issue tender to such debarred contractors.<br />

(Modified as per OM/MAN/233)<br />

(2) In case a contractor is removed from the approved list of contractors maintained by CPWD<br />

for any reason including that of inactivity, such a contractor shall not be eligible to take up<br />

works in CPWD on the basis of his enlistment in any other Engineering <strong>Department</strong>. However,<br />

if the NIT approving authority not lower than the rank of Superintending Engineer is satisfied<br />

that it is in the interest of the Government to allow a contractor who has been removed from<br />

the approved list for reason of inactivity, to participate in the tendering process for getting<br />

competitive tenders, he may do so.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!