10.09.2013 Views

AGENDA 3.1.2 - Board of Engineers Malaysia

AGENDA 3.1.2 - Board of Engineers Malaysia

AGENDA 3.1.2 - Board of Engineers Malaysia

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

RECOMMENDATION<br />

BY THE INVESTIGATING COMMITTEE TO THE BOARD<br />

CASE : Cadangan Projek Penjara Reman (Tegar) Fasa 2 di Mukim Pulai Daerah<br />

Johor Bahru, Johor Darul Takzim<br />

COMPLAINANT<br />

: AHAR Consultants Sdn Bhd<br />

RESPONDENT : AYA <strong>Engineers</strong> Sdn Bhd<br />

INVESTIGATING<br />

COMMITTEE<br />

FACT OF THE<br />

CASE<br />

: Ir. Fong Tian Yong (Chairman)<br />

YBhg. Dato’ Ir. Kok Soo Chon<br />

Ir. Rocky HT Wong<br />

<strong>AGENDA</strong> <strong>3.1.2</strong><br />

: Background<br />

The complainant AHAR is the M&E consultant for phase 1 <strong>of</strong> the above<br />

project appointed by the D&B Contractor ISTS-JV on 2007. Before the<br />

construction works for phase 1 ended on April 2011, they claimed to have<br />

received instruction from JKR, the project Director to proceed with phase 2<br />

M&E design on June 2010. They claimed to have completed the design<br />

and tender documentation by Dec 2010 and submitted to JKT HODT<br />

(Head <strong>of</strong> Design Team).<br />

However, on Mac 2011, they were informed that phase 2 project was<br />

awarded to the same Contractor as D&B contract and the contractor has<br />

submitted new M&E consultant, AYA as the M&E consultant.<br />

As such, AHAR regarded that such appointment as supplanting as they<br />

are sure that AYA would have known AHAR involvement during phase 1.<br />

They regard such action as supplanting and/or attempt to supplant and this<br />

has contravened the BEM pr<strong>of</strong>essional etiquette.<br />

IC’s findings<br />

a) There was no dispute that the D&B contractor has only appointed one<br />

M&E consultant for phase 2 i.e. AYA. AYA has also sought the<br />

reconfirmation from D&B contractor that they are the only M&E<br />

consultant appointed for phase 2 <strong>of</strong> the project in writing before<br />

accepting the appointment.<br />

b) JKR pro-active step in assuming the method <strong>of</strong> future contract (phase<br />

2) and requesting informally the Complainant in performing some the<br />

M&E design works for phase 2 may have mis-led them into thinking that<br />

they will be appointed eventually. The Complainant admitted that they<br />

assumed some risk when they perform the design works before any<br />

<strong>of</strong>ficial appointment.<br />

c) It is very clear from the above that the element <strong>of</strong> supplanting does not<br />

exist at all since the client has not appointed any one before appointing<br />

the Respondent AYA for M&E works for phase 2. Appointment <strong>of</strong> phase<br />

1 cannot be linked to Phase 2 as far as design works is concerned as<br />

they are separate matter.<br />

____________________________________________________________________________<br />

IC’s RECOMMENDATION<br />

The IC recommended that there shall be no charge to be taken against the Respondent,<br />

namely AYA <strong>Engineers</strong> Sdn Bhd.


Page 1 <strong>of</strong> 22


Page 2 <strong>of</strong> 22


Page 3 <strong>of</strong> 22


Page 4 <strong>of</strong> 22


Page 5 <strong>of</strong> 22


Page 6 <strong>of</strong> 22


Page 7 <strong>of</strong> 22


Page 8 <strong>of</strong> 22


Page 9 <strong>of</strong> 22


Page 10 <strong>of</strong> 22


Page 11 <strong>of</strong> 22


Page 12 <strong>of</strong> 22


Page 13 <strong>of</strong> 22


Page 14 <strong>of</strong> 22


Page 15 <strong>of</strong> 22


Page 16 <strong>of</strong> 22


Page 17 <strong>of</strong> 22


Page 18 <strong>of</strong> 22


Page 19 <strong>of</strong> 22


Page 20 <strong>of</strong> 22


Page 21 <strong>of</strong> 22


Page 22 <strong>of</strong> 22

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

Saved successfully!

Ooh no, something went wrong!