construction stage procedures - rev 1

PROJECT MANAGEMENTPO BOX 27642, DUBAI, UAE

This document is the property of edara LLC and must not be copied in part or full (except the forms appended with

EDA-04

CONSTRUCTION STAGE PROCEDURES

PROJECT MANAGEMENTPO BOX 27642, DUBAI, UAE

Shortcut to Contents

This document is the property of edara LLC and must not be copied in part or full (except the forms appended with


Doc No.

: EDA-04-01

Rev : 1

Date : 16 Oct 05

CONTENTS Page : 1 of 1

Document No. Document Title

EDA-04-01 Contents

EDA-04-02 Authorisation and Revision Schedule

EDA-04-03 Responsibility and Authority Limits

EDA-04-04 Meetings

EDA-04-05 #

EDA-04-06 Contractor Submittals

EDA-04-07 Contract Programme

EDA-04-08 Contractor Prepared Drawings

EDA-04-09 Method Statements

EDA-04-10 #

EDA-04-11 Request for Information

EDA-04-12 Contractor Request for Inspection

EDA-04-13 Change Management

EDA-04-14 #

EDA-04-15 Builders Work

EDA-04-16 Employer Supplied Materials

EDA-04-17 Field Instruction

EDA-04-18 Non-conformance Reports

EDA-04-19 Employer Complaints

EDA-04-20 #

EDA-04-21 Contractor’s Daily Activity Report

EDA-04-22 Consultant’s Monthly Progress Report

EDA-04-23 Monthly Progress Report to the Employer

EDA-04-24 Taking Over

EDA-04-25 Defects Liability

EDA-04-26 Consultant, QS, Contractor and Supplier Payments

EDA-04-27 #

EDA-04-28 Safety and Welfare

EDA-04-29 IT Guidelines and Recommendation for Sites

EDA-04-30 Construction Stage Records

# - Numbers reserved for introducing new documented procedures (as required) in the future.


Doc No.

: EDA-04-02

Rev : 1

Date : 16 Oct 05

SCOPE, AUTHORISATION AND REVISION SCHEDULE Page : 1 of 1

SCOPE

edara Construction Stage Procedures describe the responsibilities and requirements to be fulfilled and complied with by the Consultant(s), Contractor(s) and edara LLC in performing the tasks described herein. Should there be a difference between any part of this procedure document with the contract document, the later shall take precedence.

AUTHORISATION

Construction Stage procedures are authorised by the General Manager and apply when carrying out the activities described herein. Revisions may be issued from time to time as necessary via the Quality Assurance Manager with the authorisation of the General Manager.

REVISION SCHEDULE

DocRev No.

Date Subject of AmendmentReviewed by

and SignatureAuthorised by and Signature

0 12 Mar 05 Initial Issue Nishad A Rahim Zuhdi Al Rai

1 16 Oct 05

Procedure EDA-04-01 Rev 1

Nishad A Rahim Adel A Lootah

Procedure EDA-04-03 Rev 1Appendix EDA-04-03-C Rev 0Appendix EDA-04-04-A Rev 1Work Instruction WI EDA-04-06-A Rev 1Procedure EDA-04-07 Rev 1Procedure EDA-04-13 Rev 1Form EDA-04-13-A Rev 1Form EDA-04-13-B WithdrawnForm EDA-04-13-C Rev 1Form EDA-04-13-D Rev 1Form EDA-04-13-F Rev 1Form EDA-04-13-G Rev 1Form EDA-04-13-H Rev 1Procedure EDA-04-17 Rev 1Form EDA-04-17-A Rev 1Form EDA-04-17-B Rev 1Procedure EDA-04-18 Rev 1Form EDA-04-21-A Rev 1Procedure EDA-04-22 Rev 1Form EDA-04-22-A Rev 1Procedure EDA-04-23 Rev 1Form EDA-04-23-C Rev 0Form EDA-04-23-D Rev 0Procedure EDA-04-25 Rev 1Form EDA-04-25-A Rev 1Procedure EDA-04-30 Rev 1


Doc No.

: EDA-04-03

Rev : 1

Date : 16 Oct 05

RESPONSIBILITY AND AUTHORITY LIMITS Page : 1 of 1

1. PURPOSE AND SCOPE

1.1. To define the responsibility and authority to originate, review and authorise various types of documents raised by edara during the construction stage.

Note

2. DEFINITION

2.1. Correspondence – The word ‘correspondence’ used in the context of this procedure refers to letters/faxes. Such documents shall be used only to address issues of general nature that do not deal with technical issues, project schedules, scope change, claims or disputes.

Note

3. ABBREVIATIONS

3.1. None

4. PROCEDURE

4.1. The responsibility and authority limits applicable to the construction stage processes are defined in Appendix EDA-04-03-C.

Note

4.2. The personnel responsible to originate and review any document shall ensure that its contents are carefully examined and found suitable for the intended use prior to offering it for authorisation.

Note

4.3. A ‘Control Sheet’ (Form EDA-04-03-A) shall be used to demonstrate the review and approval process of various documents described in Appendix EDA-04-03-A. The Control Sheet shall be replaced by an ‘Employer Submittal Control Sheet’ (Form EDA-04-03-B) for documents requiring authorisation/decision from the Employer.

Note

4.3.1. The Control Sheet shall be assigned with a reference number as per following format:

Project No./Year/ Serial No./Rev X

Year – Write the last two digits of the year. For e.g. write 05 for the Year 2005

Serial Number – Is the sequential number assigned to the Control Sheet from a Control Sheet Log maintained.

Rev X – Denotes the revision status of the Control Sheet. The first submission shall carry Rev 0 status, and the status incremented by ‘1’ for every re-submission.

edara Secretary/Document Controller

5. RECORDS MAINTAINED BY EDARA

5.1. Signed Letters and Documents

5.2. Control Sheets (including Employer Submittal Control Sheets)


Doc No.

: EDA-04-04

Rev : 0

Date : 12 Mar 05

MEETINGS Page : 1 of 2


1.1. To describe the various types of meetings held at site, particularly the ‘Kick-off Meeting’ with the Contractor and the ‘Construction Progress Review Meetings’.

Note

2. DEFINITION

2.1. Contractor Kick-off Meeting: The meeting held with the successful Contractor immediately after the acknowledgement of the Letter of Acceptance by the Contractor and before commencement of their work at site.

Note

2.2. Construction Progress Meetings: Regular meetings held with the Contractor to review progress, performance and resolve any issues.

Note

3. ABBREVIATIONS

3.1. None Note

4. PROCEDURE

4.1. Contractor Kick-off Meeting

4.1.1. Within a week from the Contractor’s acknowledgement of the Letter of Acceptance, the Contractor, the Consultant and the QS (if employed) are called for a kick-off meeting allowing enough time for each party to prepare for the meeting.

edara PM

4.1.2. The meeting is chaired by edara Senior Project Manager and attended by the relevant edara Project Manager(s) and the other parties as described above.

Note

4.1.3. The meeting agenda shall be advised to all attendees in advance. The agenda for the meeting includes but not limited to the topics listed in the attached proforma (Appendix EDA-04-04-A).

edara PM

4.1.4. Minutes of the meeting shall be prepared and circulated to all parties within 3 working days from the date of the meeting. The minutes are prepared using the project management software where available. A sample format of the minutes is attached for reference (Appendix EDA-04-04-B).

edara PM

4.2. Construction Progress Meetings

4.2.1. Construction progress meetings are held on a weekly basis at the start of the project and later at a frequency determined by the edara Project Manager.

Note

4.2.2. The meeting is chaired by edara Project Manager and attended by the Contractor, the Consultant and the QS (as required).

Note

4.2.3. The agenda for the meeting includes but not limited to the topics listed in the attached proforma (Appendix EDA-04-04-C).

Note


Doc No.

: EDA-04-04

Rev : 0

Date : 12 Mar 05

MEETINGS Page : 2 of 2

4.2.4. Minutes of the meeting shall be prepared and circulated to all parties within 3 working days from the date of the meeting. The minutes are prepared using the project management software where available. A sample format of the minutes is attached for reference (Appendix EDA-04-04-B).

edara PM

4.3. Other Meetings

4.3.1. Other meetings held at site may include: Design co-ordination meetings (for design and build jobs) Ad hoc meetings Status review meetings Technical meetings Special meetings as required by edara, dependent on the nature of

the project.

Note

4.3.2. Such meetings are initiated by edara either by itself or at the request of the Employer, Consultant, QS or the Contractor.

Note

4.3.3. These meetings are chaired by edara and attended by the parties required to fulfil the objective of the meeting.

Note

4.3.4. The party that calls for the meeting prepares the agenda, and the minutes are prepared and circulated by edara.

Note


5.1. Meeting Agenda.

5.2. Minutes of Meetings.


Doc No.

: EDA-04-06

Rev : 0

Date : 12 Mar 05

CONTRACTOR SUBMITTALS Page : 1 of 3


1.1. To standardise the preparation of submittals made by the Contractor as required by the Contract for review and approval by the Consultant and edara.

Note

1.2. This procedure neither replaces nor supersedes the Contract, but provides guidance to the Contractor to implement the Contract.

Note

2. DEFINITION

2.1. Submittals: The word submittal used in the context of this procedure refers to submissions made by the Contractor that contain technical information (including technical queries), alternative proposals, drawings, manufacture’s data, certificates, test results and the like.

Note

3. ABBREVIATIONS

3.1. None

4. PROCEDURE

4.1. All submittals made by the Contractor shall comply with the requirements in table A:

Table A

Nature of Submittal

Documents required along with the Submittal

No. of Copies

Sub

mitt

al T

rans

mitt

al

She

et(F

orm

ED

A-0

4-06

-A)

Sub

mitt

al T

itle

Blo

ck(F

orm

ED

A-0

4-06

-B)

Dra

win

g T

itle

Blo

ck(F

orm

ED

A-0

4-06

-C)

Sam

ple

Tag

(For

m E

DA

-04-

06-D

)

Spe

cific

atio

n C

ompa

rison

She

et(F

orm

ED

A-0

4-06

-E)

Technical Submittals Yes Yes No No Yes 1 Original + 2 CopiesSamples Yes Yes No Yes Yes 2 OriginalsDrawings Yes No Yes No No 3 Prints

4.2. Submittal Transmittal Sheets shall be prepared as per the guidelines in the attached work instruction (WI EDA-04-06-A).

Contractor

4.3. All submittals are made to the edara Secretary at Site. Contractor

4.4. edara Secretary signs and records the receipt date on the Submittal Transmittal Sheet, registers it in the submittal log maintained under the respective Project Management Tool used (Supremacy, Expedition, etc) and forwards the submittal to the Consultant for review. The Secretary shall obtain the Consultants signature on a logbook maintained to record the delivery.

edara Secretary


Doc No.

: EDA-04-06

Rev : 0

Date : 12 Mar 05


4.5. Consultant’s Review

4.5.1. The Consultant reviews the submittal and returns the same to edara along with their comments/decision as follows:

Consultant

APP Approved Means that fabrication, manufacture, supply or construction can proceed

AAN Approved as Noted Means that fabrication, manufacture, supply or construction may proceed provided that the Contractor complies with the notations made in the submittal. If for any reason, the Contractor cannot comply with such notations, the Contractor shall make revisions and resubmit.

ANR Approved as Noted Resubmit

Means that fabrication, manufacture, supply or construction may proceed only for the approved items provided that the Contractor complies with the notations made in the submittal and resubmits the submittal for the non approved items incorporating the notations made.

NR Not Required Means that the submission is cancelled since the scope of work has been deleted or altered. Where the work is altered, the Contractor shall initiate a new submittal.

NA Not Approved Means that the submission does not comply with the contract and that fabrication, manufacture, supply or construction shall not proceed. The contractor shall revise and resubmit.

4.6. edara’s Review

4.6.1. edara Secretary receives the submittal from the Consultant, updates the submittal log maintained and forwards the submittal to the relevant edara Project Manager for review.

edara Secretary

4.6.2. edara Project Manager reviews the submittal and records his/her comments/decision (similar to clause 4.5.1) and return to edara Secretary for distribution.

edara Project Manager

4.6.3. edara Secretary copies the submittal to the Contractor, the Consultant, the QS (as required) and Others (as required) using a Transmittal generated using the Project Management Tool. The original Submittal is maintained by edara.

edara Secretary


Doc No.

: EDA-04-06

Rev : 0

Date : 12 Mar 05



5.1. Submittal Transmittal Sheets.

5.2. Submittal Title Blocks.

5.3. Drawings.

5.4. Samples with Sample Tags.

5.5. Specification Comparison Sheets.

5.6. Submittal Log maintained under the respective Project Management Tool (Soft Copy).

5.7. Log book maintained to record delivery of Submittals to the Consultant.

5.8. Transmittal used to distribute Submittals following Consultant and edara review and comments.

WORK INSTRUCTION

Doc No. : WI EDA-04-06-A

Rev : 1

Date : 16 Oct 05

GUIDELINES FOR PREPARING SUBMITTAL TRANSMITTAL SHEET

Page : 1 of 2

1. Submittal Transmittal Number

1.1. The format of Submittal Transmittal number shall be as follows:

Contract No./STS-XXX

Contract No. – This is the reference number assigned by edara to the particular contract against which the submittal is made. For project with only one contract, the contract number will be the project number itself.

STS – denotes Submittal Transmittal Sheet. XXX – denotes the serial number assigned by the Contractor.

2. Project No.

2.1. Is the identification number assigned to the project by edara.

3. Date

3.1. All dates shall be in the format “day – month – year”.

4. Submittal Number

4.1. This shall be a unique number assigned to each submittal by the Contractor. This number shall include the first five digits of the Project Master Format as below (or as approved by the concerned edara Project Manager) followed by a serial number assigned by the contractor:

Package Number Title

00100 - Shop Drawing - Structural00200 - Shop Drawing - Architectural00300 - Shop Drawing - Electrical00400 - Shop Drawing - Mechanical00500 - Shop Drawing - Builder’s Work00600 - Coordinated Services Layout00700 - Materials - Structural00800 - Materials - Architectural00900 - Materials - Electrical01000 - Materials - Mechanical02000 - Programmes and Schedules02500 - Test Reports02700 - Method Statements03000 - Waterproofing04000 - Landscaping05000 - Maintenance and Cleaning Equipment06000 - Aluminium and UPVC Works07000 - Elevator and Escalator08000 - As Built Drawings09000 - Operation and Maintenance Manual

5. Revision

5.1. Denotes the revision status of the Submittal. The first submittal shall carry Rev 0 status, and the status is incremented by ‘1’ for every re-submittal.

WORK INSTRUCTION


Rev : 1

Date : 16 Oct 05

GUIDELINES FOR PREPARING SUBMITTAL TRANSMITTAL SHEET

Page : 2 of 2

6. Submittal Title

6.1. This is the heading/title of each submittal.

7. Item No.

7.1. Number or letter assigned by the Contractor to individual within the items within the body of the submittal.

For example:ITEM NO. DESCRIPTION a. Manufacturer’s datab. Shop Drawings (list by number)c. Load Calculations

8. Drawings, Specification or BOQ Reference

8.1. This refers to the drawing, specification or BOQ item number under which the submittal is required.

9. Description

9.1. For Drawings: List the drawing numbers, along with its title and revision status.

9.2. For Manufacturer’s Data: Identify using the same name or description shown in the manufacturer’s information.

9.3. For Samples: Identify using the descriptive items in the specification and/or BOQ.

9.4. For Others: Include similar descriptions as to item 9.3 for all guarantees, test certificates, and any other documents.

10. Type

10.1. The types of submittals shall be: SD - Contractor produced shop drawings SM - Sample GT - Guarantee MD - Manufacturer’s data, catalogue, brochures, calculations CT - Certificates TT - Test results OT - Other

11. Subcontractor/Supplier/Manufacturer

11.1. List the name of the Subcontractor responsible for the material as well as the supplier’s and/or manufacturers name if applicable.


Doc No.

: EDA-04-07

Rev : 1

Date : 16 Oct 05

CONTRACT PROGRAMME Page : 1 of 5


1.1. To ensure that the Contractor has established a valid Programme in compliance with the Contract Documents and the Project completion requirements.

Note

2. DEFINITION

2.1. None Note

3. ABBREVIATIONS

3.1. None

4. PROCEDURE

4.1. The Contract Programme (Clause 14 of General Conditions of Contract) shall be submitted (one hard copy and one electronic copy) for review and approval by edara and the Consultant within 28 days from the acknowledgement of the ‘Letter of Intent' by the Contractor.

Contractor

4.2. Following approval by edara and the consultant, the Contract Programme will be “baselined” and will form the basis for comparison of planned and actual contract indicators (i.e. time, cost, resource and other indicators).

Note

4.3. The submission, review, approval and distribution of Contract Programme submittals shall be as described in the edara procedure for Contractor Submittals (Procedure EDA-04-06).

Note

4.4. The Contractor should bear in mind that the submissions may not necessarily achieve approved status at first submission and hence the programme should be designed with suitable contingency for such eventuality.

Note

4.5. The Contract Programme shall utilise the ‘Critical Path Method’ using specialised software such as Primavera Project Planner or equivalent (to be proposed to and approved by edara).

Contractor

4.6. The Contract Programme shall include the following components: Contractor

4.6.1. Work Breakdown Structure (WBS) 4.6.1.1. WBS shall be prepared encompassing every element of the

scope of works and agreed with edara prior to proceeding with the Contract Programme. A precise and unambiguous coding structure shall be used in its preparation.

4.6.2. Working Programme The working programme shall be represented in the form of a bar chart or a series of bar charts supported by durations, start and finish dates and amount of float resulting from the critical path analysis of the network for the contracted scope of works. A precedence network shall also be shown to support and explain the bar chart(s). The working programme shall consist of:


Doc No.

: EDA-04-07

Rev : 1

Date : 16 Oct 05


4.6.2.1. The Programme of Working Drawings, Method Statements and other Submissions (Shop Drawings).

The intended preparation, submission and review of each individual package of shop drawings or submissions for every element of the scope of works shall be clearly defined and separately identified.

The Contractor shall, when preparing this programme, take into account the physical and technical interfaces between every element of the scope of works for the contract and the scope of works for other contracts based on information provided by edara from time to time.

The programme shall consider phasing of submissions in order that edara is provided with an even flow of documents for review.

This programme shall also identify all items of information that the Contractor requires from the Project Manager and the time they are required.

In addition to indicating the essential relationships between each element or task of the programme, the programme should also clearly identify the relationship between the completion of review of each submission and any subsequent procurement, manufacturing, construction or other key element of the contract.

4.6.2.2. The Procurement Programme

This should clearly identify and define the intended preparation of shop drawings, fabrication schedules and the like, procurement of materials, the manufacture and/or fabrication of materials, items of plant or equipment required to complete the scope of works, any tests required, the preparation of goods for shipment, etc.

The procurement programme should consider the risks inherent in shipping (where applicable), and hence provide sufficient time periods for the unpacking and checking of delivered materials in additions to sufficient contingency to mitigate the effects of the type of event(s) that an experienced Contractor should anticipate.

This will be later developed into a comprehensive procurement schedule in a format agreed with edara.

4.6.2.3. The Construction Programme

This programme should include all testing and commissioning requirements including local authority inspections/approvals (such as Municipality, Water and


Doc No.

: EDA-04-07

Rev : 1

Date : 16 Oct 05


Electricity, Civil Defence, Telecommunications and the miles stone dates for “Water and Electricity Dept Power On”), the provision of deliverable documents prior to completion and due allowances for snagging.

It is essential when developing this programme, that the Contractor takes into account the requirement that all related design submissions, material submissions and method statements have achieved a suitable status before the associated element of work may commence.

This programme shall also identify all items of information and working areas, which the Contractor requires, the time that they are required and the elements and tasks within the programme that the Contractor considers will be affected and how they will be affected by the provision of such information and working locations.

The programme should highlight strategic planning for MEP installations that include, but not limited to the following:

- Submission of electrical drawings for Local Authority Approval.

- Registration for applications for service connections.

- Remittance of Local Authority charges for service connection.

- HV Substation construction and handing over to Local Authorities.

- Local Authority inspection of electrical installations.

- “Power On” target dates.

- Civil Defence inspections.

- Local Authority water connection.

- Drainage connection to public sewerage system.

- Telecommunication connections.

- Completion of substation building at an early stage of the project considering time impacts for Local Authority involvement and installation of equipment.

4.6.2.4. The Overall Programme

This is a summary of the above three programmes and will be used for monitoring and reporting purposes.

The overall programme shall indicate the means by which the Contractor intends to achieve any interim milestones or


Doc No.

: EDA-04-07

Rev : 1

Date : 16 Oct 05


handover dates required by the Contract.

All floats in the programme shall be accrued to the Employer.

4.7. In addition to the Contract Programme, the Contractor shall also submit the following:

Contractor

4.7.1. Man Power Loaded Programme 4.7.1.1. The working programme shall be loaded with the manpower (in

number of men) on weekly basis, as proposed to be utilised (Planned Manpower). The Manpower Loaded Programme shall be updated with the ‘Actual Manpower’ as work proceeds.

4.7.1.2. The Contractor shall provide an analysis of the manpower usage and productivity to explain and support the Manpower Loaded Programme.

4.7.1.3. In preparing the Manpower Loaded Programme, the Contractor shall:

Note that manpower shall be classified as Management personnel (Engineer, Engineers, Foreman, etc) and Workmen. The Workmen shall be further broken down as Direct Workmen (Skilled and Unskilled Labour) and Indirect Workmen (General. Drivers, Security, etc).

Present the Manpower Loaded Programme in graphical format with weekly planned manpower plotted on Y1-axis (histogram), and cumulative until end of week values on Y2-axis (‘S’ curve), with period on X-axis. The summary and breakdown of manpower by discipline against each week to be tabulated.

4.7.2. Planned Key Project Indicators

4.7.2.1. The Contractor shall provide, in tabular and graphical format an identification of the planned progress of major elements of the contract in a form and content to be agreed by edara. Depending on the scope of the Contract, this will indicate the likes of quantities of concrete to be placed over time, lengths of pipe or cable to be laid over time, square meters of tiling to be achieved over time, number of rooms to be tested and the like.

4.8. Revisions to the Contract Programme

4.8.1. Revision by the Contractor

4.8.1.1. If, for any reason during the execution of the Contract, the Contractor considers that the approved programme no longer reflects the periods and sequence which they intent to adopt for the remaining part of the contract, then they shall:

Contractor

Advise edara in writing.


Doc No.

: EDA-04-07

Rev : 1

Date : 16 Oct 05


Proceed to revise the programme to take account of current circumstances.

Advise edara of the intended submission date of the revised programme.

Ensure that the revised programme indicates a completion date in accordance with the latest approved contract completion date.

Submit the revised programmed to edara for consent in the manner outlined earlier in this procedure.

4.8.2. Revision by the Employer or edara

4.8.2.1. If, during the execution of the works, the Employer or edara considers that the current programme no longer represents a realistic forecast to completion of the works, they shall advise the Contractor accordingly in writing, with a requirement to revise the programme for submission and consent in accordance with the provisions of Clause 14.2 of the General Conditions of Contract

Employer/edara

4.8.2.2. Revised programme to be submitted within 7 days of being so requested by the Employer/edara.

Contractor

4.8.3. In the event that a revision to the programme is required, the specific activities of the approved programme that have been affected shall be clearly indicated in the revised submission, their impacts, if any, on interim and final completion dates.

Contractor


5.1. Approved Contract Programme.

5.2. Work Break Down Schedule.

5.3. Programme of Working Drawings, Method Statements and Other Submissions.

5.4. Procurement Programme.

5.5. Construction Programme.

5.6. Overall Programme.

5.7. Manpower Histograms.

5.8. Planned Key Project Indicators.

5.9. Revised Contract Programme (where applicable).


Doc No.

: EDA-04-08

Rev : 0

Date : 12 Mar 05

CONTRACTOR PREPARED DRAWINGS Page : 1 of 3


1.1. To describe the requirements for the preparation, submittal and revision of all drawings produced by or submitted on behalf of the Contractor. This applies to all drawings that are supplied to edara for approval/information as well as “as built drawings”.

Note


Note

2. DEFINITION

2.1. Drawings: The word drawing used in the context of this procedure refers to drawings, sketches, shop drawings, detail drawings, working drawings, or any other drawing required to supplement the contract documents.

Note

3. ABBREVIATIONS

3.1. None

4. PROCEDURE

4.1. Drawing Size

4.1.1. All Contractor produced drawings shall be of the following sizes only or as approved by edara:

Contractor

Size Identity Sheet Size (in mm)A0 840 x 1187A1 840 x 594A3 297 x 420A4 210 x 297

A4.2. Drawing Title Block

4.2.1. All drawings shall have a title block as per Form EDA-04-06-C. Contractor

4.3. Drawing Number

4.3.1. All drawings shall have the drawing number in the lower right hand corner in the space provided in the title block.

Contractor

4.3.2. The drawing number shall be as discussed in this procedure or as approved by edara.

Contractor

4.3.3. The drawing number shall contain 4 parts as follows: Contractor

First Part Source of DrawingA ArchitectM Mechanical EngineerE Electrical EngineerP PlumbingS Structural


Doc No.

: EDA-04-08

Rev : 0

Date : 12 Mar 05


4.3.4. Second Part Information TypeL Location DrawingsA Assembly DrawingsC Component DrawingsS Schedules

Third Part 2 digit or 3 digit sequential number

Fourth Part Revision Status

4.3.5. As an example, the drawing number of the drawing related to external wall sections submitted for the first time is as follows:

Drawing No. AA 101 Rev 0First Part A ArchitectSecond Part A Assembly DrawingThird Part 101 Sequential Number of the DrawingFourth Part 0 Revision Number

4.4. Drawing Co-ordination

4.4.1. The drawing co-ordination block shall include initials/stamps of each subcontractor whose trades are involved. This represents the co-ordination of all disciplines of any individual drawing.

Contractor

4.5. Drawing Scale

4.5.1. Contractor prepared drawings shall be to the following scales as a minimum to facilitate reviews and co-ordination:

Contractor

Floor Plan Layout 1:100Plant Room, core layouts 1:50Details 1:20

4.6. Drawing Orientation

4.6.1. In the event that the drawings contain reference to the compass, then all plans shall have the north arrow pointing upwards or to the right side of the drawing. The north arrow shall be shown in the upper right hand corner of the drawing.

Contractor

4.7. Drawing Revisions

4.7.1. Revisions shall be clearly indicated by making a cloud around the area that is revised. The cloud should contain a small triangle with the revision number written inside it.

Contractor

4.7.2. When making a new revision, the clouds from the previous revision will be removed.

Contractor

4.7.3. The new revision number is indicated in the space above the co-ordination block along with the date, the initials of the person making the revision and the initials of the person approving the revision. It is important to describe the revision and its location on the drawing. The preferred operative words are

Contractor


Doc No.

: EDA-04-08

Rev : 0

Date : 12 Mar 05


‘added’, ‘revised’, ‘deleted’. Sample revision description are:

Revised Section AAdded Detail 1Deleted Window in west elevation

It may also be useful to describe why the revision was made.

4.8. Drawing Submittals

4.8.1. All drawing shall be submitted to edara for approval using a Submittal Transmittal Sheet as described in the procedure for Contractor Submittals (Procedure EDA-04-06).

Contractor


5.1. Approved Drawings.

5.2. Submittal Transmittal Sheets.


Doc No.

: EDA-04-09

Rev : 0

Date : 12 Mar 05

METHOD STATEMENTS Page : 1 of 2


1.1. To describe the types of Method Statements required to be submitted by the Contractors and the situations in which they are required.

Note


Note

2. DEFINITION

2.1. None Note

3. ABBREVIATIONS USED

3.1. None

4. PROCEDURE

4.1. Overall Method Statement

4.1.1. An Overall Method Statement covering the general aspects of construction shall be submitted by the Contractor within one month from the Project Kick-off Meeting. This shall include an introduction describing the project and brief statements on:

Water and power for the works Access Information required schedule Site establishment/temporary facilities Excavation and dewatering Shoring Piling Concrete supply Reinforcement supply, cutting and bending Decking/Formwork systems Tower crane location Material handling, storage Working hours Subcontracted works Sequence of operations Programme Safety Quality Others

Contractor

4.2. Method Statement

4.2.1. Approved Method Statements are required prior to commencement of work where the quality and/or safety are likely to be affected in the absence of written instructions.

Note

4.2.2. Activities (or sub activities) that require Method Statements are determined by edara/Consultant and/or the Contractor themselves.

Edara/Consultant/Contractor


Doc No.

: EDA-04-09

Rev : 0

Date : 12 Mar 05

METHOD STATEMENTS Page : 2 of 2

4.2.3. The initial requirement for Method Statements are determined at the Project Kick off meeting and the need for more are determined during the course of construction as deemed necessary.

Note

4.2.4. Method Statements shall be prepared and submitted by the Contractor well in advance of the commencement of work to allow reasonable time for review and approval.

Contractor

4.2.5. The Method Statement shall list each step of operation concerned, the information required (drawings, specification, BOQ, product information, etc), the resources utilised (man, equipment) and the checks to be made before proceeding to the next step. Where appropriate, diagrams and sketches will be used to explain proposed working methods.

Contractor

4.3. The review, approval and distribution of the Overall Method Statement and Method Statements shall be as described in the edara procedure for Contractor Submittals (Procedure EDA-04-06).

Note


5.1. Approved Method Statements

5.2. Submittal Transmittal Sheets


Doc No.

: EDA-04-11

Rev : 0

Date : 12 Mar 05

REQUEST FOR INFORMATION Page : 1 of 2


1.1. To describe the method to be followed for raising technical clarifications required by the Contractor or their Subcontractors.

Note


Note

2. DEFINITION

2.1. Project Management Tool: This is the software (Supremacy, Expedition, etc.) used to register and track various documents generated in the Construction Stage.

Note


3.1. RFI – Request for Information.

4. PROCEDURE

4.1. Technical clarifications are raised by the Contractor using the attached ‘RFI” form (Form EDA-04-11-A).

Contractor

4.1.1. A reference number shall be assigned to all requests as per the following format:

Contract No./RFI-XXX.

Contractor

Contract No. – This is the reference number assigned by edara to the particular contract against which the RFI is raised. For projects with only one contract, the contract number will be the project number itself.

RFI – denotes Request for Information. XXX – denotes the serial number assigned by the Contractor.

4.1.2. The Contractor is encouraged to make the requests in the description section of the form. The requests shall be concise and within the space provided on the form.

Contractor

4.1.3. It is important to include the specific references to the specification, drawings, BOQ or other documents. Request may be of varying nature including discrepancies, document clarifications, site conditions, etc. However only one request should be included on each form.

Contractor

4.2. Completed forms shall be submitted to the edara Secretary at Site. Contractor

4.3. edara Secretary signs and records the receipt date on the request, and forwards the original request first to the Consultant and then to the QS with a copy maintained with edara at each stage. The Secretary also obtains the signatures of the Consultant and QS on a logbook maintained to record the delivery.

edara Secretary

4.4. Consultant and QS reviews the request and provides their feedback on the same form. Support documents if any shall be attached to the RFI form and the completed form returned to the edara Secretary.

Consultant/ QS


Doc No.

: EDA-04-11

Rev : 0

Date : 12 Mar 05

REQUEST FOR INFORMATION Page : 2 of 2

4.5. edara Secretary then forwards the request to the relevant edara Project Manager for review.

edara Secretary

4.6. edara Project Manager reviews the request and records his/her comments/decision and returns to edara Secretary for distribution.


4.7. edara Secretary distributes copies of the request to the Contractor, the Consultant, the QS and Others (as required) under the cover of a ‘Transmittal’ generated using the Project Management Tool. The original request is maintained by edara.

edara Secretary

4.8. A RFI log shall be maintained by edara under the respective Project Management Tool to track the various stages of review of the RFI.

edara Secretary


5.1. Request for Information

5.2. Request for Information Log (Soft Copy)

5.3. Log book maintained to record delivery of RFIs to the Consultant and QS.


Doc No.

: EDA-04-12

Rev : 0

Date : 12 Mar 05

CONTRACTOR REQUEST FOR INSPECTION Page : 1 of 3


1.1. To describe the format, preparation, process, administration and distribution of Site Inspections to allow the Consultant to maintain quality control over the Contractor’s activities and material/equipment used.

Note

1.2. This procedure specifically applies to the following: Inspections at the Control Hold Points, and Materials/equipment requiring Consultant inspection and clearance

as per the Project Specifications/BOQ.

Note

1.3. This procedure neither replaces nor supersedes the Contract, but provides guidance to the Contractor and the Consultant to implement the Contract.

Note

2. DEFINITION

2.1. Control Hold Points: These are the stages of construction that require inspection and clearance from the Consultant before proceeding to the next stage.

Note

3. ABBREVIATIONS

3.1. IRS – inspection Request Schedule Note

3.2. CRI – Contractor Request for Inspection

4. PROCEDURE

4.1. Control Hold Points

4.1.1. The Control Hold Points shall be agreed between the Consultant and the Contractor prior to start of each set of activities by the Contractor.

Note

4.1.2. A schedule of the Control Hold Points shall be submitted to the Consultant by the Contactor for approval.

Contractor

4.1.3. Following approval, copies of the approved Hold Points are distributed to edara and the Contractor.

Consultant

4.2. Inspection Request Schedule

4.2.1. The Contractor shall submit an IRS to the Consultant well in advance of the scheduled inspection (preferably one day in advance) using the attached form (Form EDA-04-12-A).

Contractor

4.2.2. The IRS shall be sequentially numbered as per the following format:Contract No./IRS - XXX Contract No. – This is the reference number assigned by edara to the

particular contract against which the IRS is submitted. For project with only one contract, the contract number will be the project number itself.

IRS – denotes Inspection Request Schedule. XXX – denotes the serial number assigned by the Contractor.

4.2.3. The schedule shall include the time of inspection, items to be inspected, the Contractor


Doc No.

: EDA-04-12

Rev : 0

Date : 12 Mar 05


type of inspection required (electrical, civil, mechanical, etc), the exact location by level and area, and the reference drawing/document.

4.2.4. The schedule shall be prepared in triplicate and signed by the Contractor and a copy each delivered to the Consultant’s Office and edara.

Contractor

4.2.5. By submitting the IRS, the Contractor shall ensure that the works stated are complete and ready for inspection by the Consultant at the specified time.

Contractor

4.2.6. All tools and equipment necessary to perform the inspection shall be made available at the time of inspection including adequate access and safety measures such as scaffolding, ladders gangways, lighting, safety rails, safety gear, cleanliness, etc.

Contractor

4.3. Inspection

4.3.1. All work shall be subject to review and clearance by the Contractor’s own QA Personnel prior to offering to the Consultant for inspection.

Contractor

4.3.2. Contractor shall prepare a CRI Form (Form EDA-04-12-B), signed by the Contractor’s Project Manager/Engineer and QA Personnel and submitted to the Consultant within reasonable time in advance of the inspection.

Contractor

4.3.3. The CRI Form shall be accurately completed, including the item(s) to be checked, location(s), level(s) and the reference drawing(s).

Contractor

4.3.4. The Contractor shall also secure the signatures of the concerned Subcontractors prior to submission to the Consultant where the inspection involves Subcontractors work.

Contractor

4.3.5. The CRI forms shall be sequentially numbered as per the following format:

Contract No./CRI – XXX Rev Y

Contractor

Contract No. – This is the reference number assigned by edara to the particular contract against which the Contractor Request for Inspections are submitted. For project with only one contract, the contract number will be the project number itself.

CRI – denotes Contractor Request for Inspection. XXX – denotes the serial number assigned by the Contractor. Y – Denotes the revision status of the CRI. The first submission shall

bear Rev 0 status.

4.3.6. The Consultant carries out the inspection and records the remarks on the CRI Form and distributes the form as below:

Consultant

White: To ContractorBlue: To ConsultantYellow: To edara

4.3.6.1. In the event where the work/material is accepted with comments, the Consultant shall follow up until all outstanding actions are closed out.

Consultant


Doc No.

: EDA-04-12

Rev : 0

Date : 12 Mar 05


4.3.6.2. In the event where any work/material is rejected, the Contractor shall carryout the required corrective measures and submit a new CRI Form with the same reference number as the original request, but with its revision number incremented by 1 (one).

Contractor

4.3.7. The Consultant shall record the inspections in a database system, and establish and maintain files for all site inspections including records of closure of outstanding actions.

Consultant

5. RECORDS

5.1. Records Maintained by edara: edara

Inspection Request Schedules

Contractor Request for Inspections

5.2. Records Maintained by the Consultant: Consultant

Inspection Request Schedules

Contractor Request for Inspections

CRI Data Base


Doc No.

: EDA-04-13

Rev : 1

Date : 16 Oct 05

CHANGE MANAGEMENT Page : 1 of 4


1.1. To establish a method to control the impact of changes generated as a result of additions, deletions, modifications and alternatives proposed by the Employer, the Operator, edara, the Consultants, the Contractor or any responsible 3rd Party.

Note

1.2. This procedure applies to the changes that arise during both the design and construction stages of the project.

Note

2. DEFINITION

2.1. Change – Change refers to any addition, deletion, modification or alternatives proposed by any party that causes a variation to the Employer agreed appearance/specification/cost/programme.

Note

2.2. Impacts – It is the consequence of effecting a change. Unless specifically mentioned, the word ‘impact’ used in the context of this procedure refers to cost, programme and functional consequences.

2.3. Change Proposal Form – Is a tool used to advise and seek written approval from the Employer on the estimated impacts of changes proposed. The last portion of the Change Proposal viz. ‘Special Permission to Proceed with Construction’ is used only in urgent situations to instruct the Contractor to proceed with the changes prior to an agreement of its impact between the Contractor and the Employer.

Note

2.4. Provisional Variation Order – Is a tool to seek the Contractor’s view of the cost and programme impacts and its review by the Cost Consultant/QS and edara. PVO also contains a provision to instruct the Contractor to proceed with the change(s) in urgent situations even prior to reaching an agreement between the Contractor and the Employer on the actual impacts

Note

2.5. Variation Order – Is a tool to confirm the impacts of the variation by the Contractor, Consultant, QS, edara and the Employer; and is an instruction issued to the Contractor in accordance with the Conditions of the Contract.

Note


3.1. CP - Change Proposal

3.2. PVO - Provisional Variation Order

3.3. VO - Variation Order

4. PROCEDURE

4.1. General

4.1.1. The Contractor can undertake a change only further to receipt of a VO approved by the Employer or a PVO with Project Manager’s “Instruction to Proceed with the Change” (issued by PM based on an Employer approved CP).

Contractor


Doc No.

: EDA-04-13

Rev : 1

Date : 16 Oct 05


4.2. Change Proposal

4.2.1. Following receipt of a request for change from any responsible party, the concerned edara Project Manager shall raise a CP (as per the attached Form EDA-04-13-A) and forward to the QS for providing the estimated cost impact.

edara ProjectManager

4.2.2. The QS shall return the CP to edara along with the estimated cost impacts and calculations.

QS

4.2.3. edara then forwards the CP to the Design Consultant to review the change(s) and advise on any impacts including cost of additional design and/or supervision required, if any, to be undertaken by the Design Consultant.

edara Project Manager/

Design Consultant

4.2.4. Once the impacts are estimated, the CP is forwarded to the Employer following review and signoff by edara Senior Project Manager.

Note: In situations that demand the Contractor to urgently proceed with the change(s), edara Project Manager shall obtain a specific approval from the Employer using the ‘Special Permission to Proceed with Construction’ portion of the CP form.


4.2.5. On approval of the CP by the Employer, the edara Project Manager shall proceed with the issue of a PVO.


4.2.6. Distribution of the CP signed by the Employer shall take place along with a transmittal form (generated using the Project Management Tool where available) as follows:Original - edaraCopies - Others (as required).


4.3. Provisional Variation Order

4.3.1. Following Employer’s approval of the CP, a PVO (Form EDA-04-13-C) is issued by the concerned edara Project Manager to the Contractor for providing the cost and programme impacts of the change.

Note: In urgent situations subject to Employer’s approval on the CP, edara may instruct the Contractor to proceed with the changes before agreement of its impacts between the Contractor and the Employer using the “Instruction to Proceed with Change Immediately” portion of the PVO.


4.3.2. The Contractor shall provide the cost and programme impacts to edara within 14 days by recording the details on Section 2 of the PVO form substantiated by supporting calculations/documents.

Contractor

4.3.3. The Contractor’s response is reviewed by the Cost Consultant/QS and edara and where necessary by the Design Consultant and the outcome is recorded in Section 3 of the form. Negotiations may be carried out with the Contractor until the cost and programme impacts are mutually agreed.

edara Project Manager/Cost Consultant/QS

4.3.4. Following agreement of the costs and programme impacts, the edara Project Manager shall proceed with the issue of a VO.


4.3.5. Distribution of a PVO following review and signature by the Cost Consultant/QS and edara shall take place along with a transmittal form


Doc No.

: EDA-04-13

Rev : 1

Date : 16 Oct 05


(generated using the Project Management Tool where available) as follows:Original - edaraCopies - Consultant, QS, Contractor and others (as required).

4.4. Variation Order

4.4.1. Following agreement of the cost and time impacts, a VO (Form EDA-04-13-D) is issued by QS based on instructions from edara to confirm any impacts with all parties.

Note: A VO can be issued directly without a prior CP in case of adjustments to Provisional Sum or Prime Cost Materials. In such cases, Section 2 and 3 of the VO form are not required to be filled.

edara Project Manager/Cost Consultant/QS

4.4.2. The VO shall then be issued to the following parties one by one for their review and signature:

First: To the ContractorSecond: To the ConsultantThird: To the QSFourth: To edara (to be signed by the concerned Project Manager and

the Senior Project Manager)Fifth: To the Employer


4.4.3. Distribution of the VO signed by the Employer shall take place along with a transmittal form (generated using the Project Management Tool) as follows:Original - edaraCopies - Consultant, QS, Contractor and others (as required).


4.5. Variations Summary and Anticipated Cost Report

4.5.1. Variations Summary Sheet (Form EDA-04-13-E) and Anticipated Cost Report (Form EDA-04-13-F) shall be submitted to the Employer along with every CP and VO.


4.5.2. The Cost Consultant/QS shall be responsible for preparing the Variations Tracking Sheet and Anticipated Cost Report.

Cost Consultant/QS

4.5.3. . Anticipated Cost Report is a document that illustrates the stages through which the project cost evolves. This is summarised as follows:

Proposed Budget: Gives rise to an Approved Budget.

Contract Sum: An amount committed by the Employer by signature of an agreement or contract.

Variations: These are costs generated after modifications / changes / risks / claims initiated by responsible parties take place. These are subdivided into the following:

o Potential Variations: An indicative cost issued through a CP after risk / change is identified.

o Provisional Variations: An estimated cost issued through a PVO


Doc No.

: EDA-04-13

Rev : 1

Date : 16 Oct 05


after the Employer approved the indicative cost.

o Claim: An estimated or actual/provision to cover identified and / or notified contractual claims cost.

o Issued Variations: It is the approved adjustment to the Contract Sum (price) issued through a VO to the Employer for signature.

4.6. Variation Status Log

4.6.1. A consolidated status log shall be maintained by edara as per the Form EDA-04-13-G for each contract to track the various stages of CPs, PVOs and VOs.


4.7. Variation Status - Graphical Representation

4.7.1. The status of variations shall be graphically represented for each contract as per the sample shown in Appendix EDA-04-13-H to provide the management with a bird’s-eye view of the status of variations.


4.7.2. Such graphs shall be submitted along with the monthly reports raised from the sites.



5.1. CPs, PVOs, VOs – all originals with the supporting documents.

5.2. Transmittals.

5.3. Variation Status Logs/Graphical Representations.


Doc No.

: EDA-04-15

Rev : 0

Date : 12 Mar 05

BUILDER’S WORK Page : 1 of 1

PURPOSE AND SCOPE

1.1. To describe the method followed by the Contractor to obtain the approval of edara and the Consultant for any builder’s work associated with the main works.

Note


Note

2. DEFINITION

2.1. Builder’s Work – refers to the ancillary work carried out by the Contractor usually in connection with the MEP installations, which includes leaving holes or apertures through structural floors, walls, beams; providing embedded bolts for fittings, and the like.

Note


3.1. None

4. PROCEDURE

4.1. Prior approval is required from edara and the Consultant to proceed with builder’s work.

Contractor

4.2. The approval is obtained by submitting the builder’s work drawings to edara along with a Submittal Transmittal Sheet as described in the edara procedure for Contractor Submittals (Procedure EDA-04-06).

Contractor

4.2.1. The builder’s work drawings shall be prepared as per the requirements described in edara procedure for Contractor Prepared Drawings (Procedure EDA-04-08).

Contractor

4.2.2. Any additional cutting, chipping, chases, etc required in due course shall be done only after approval by edara and the Consultant thought the submission of revised builder’s work drawings.

Contractor

4.3. The review, approval and distribution of the builder’s work drawing submittals shall be as described in the edara procedure for Contractor Submittals (Procedure EDA-04-06).

Note


5.1. Approved Builder’s Work Drawings

5.2. Submittal Transmittal Sheets


Doc No.

: EDA-04-16

Rev : 0

Date : 12 Mar 05

EMPLOYER SUPPLIED MATERIALS Page : 1 of 3


1.1. To define the responsibilities pertaining to procurement, receipt, storage, protection and issue of ‘Employer Supplied Materials’.

Note

1.2. This procedure neither replaces nor supersedes the Contract, but provides guidance to the Main Contractor and the Nominated Subcontractors to implement the Contract.

Note

2. DEFINITION

2.1. Employer Supplied Materials – The expression “Employer Supplied Materials” shall mean the items (including equipment), which are procured by the Employer and delivered to the Contractor at site, wherein the Contractor has to install, test and commission them as part of their contract, as described in the specification, the contractual drawings and the Bill of Quantities.

Note


3.1. None

4. PROCEDURE

4.1. Procurement of Employer supplied materials is done either directly by the Employer (through their own staff) or by edara under the approval of the Employer.

Note

4.2. In situations where the Employer directly procures the materials, edara shall be responsible to provide the Employer with the list of items required and the time they are required.


4.3. In situations where the procurement is done by edara under the approval of the Employer, the responsibilities of edara are as stated under clause 4.4.

Note

4.4. Responsibilities of edara

4.4.1. To short list potential suppliers based on any or a combination of the following criteria and obtain Employer’s approval of the same:

Prequalification (either in the Supplier’s own format or as per Form EDA-04-16-A)

Past experience Single source supplier Employer specified

4.4.2. To invite tenders from the Employer approved suppliers and adjudicate based on compliance with specification, price, ability to meet delivery schedule, etc.

4.4.3. To recommended the most suited supplier and obtain Employer’s approval.

4.4.4. To initiate Purchase Orders as per the procurement schedules agreed with the Contractor.


Doc No.

: EDA-04-16

Rev : 0

Date : 12 Mar 05


4.4.5. To ensure that the Purchase Orders contain adequate data to precisely define the product ordered including the need for the following as appropriate:

Source/test certificates. Special packaging/shipping/labelling instructions. Inspections required by edara. Delivery schedule and location.

4.4.6. To obtain Employer’s approval on all Purchase Orders.

4.4.7. To follow up throughout the procurement stages to ensure timely delivery to site.

4.5. Responsibilities of the Main Contractor

4.5.1. To submit the delivery schedule of Employer supplied material along with the Procurement Programme and obtain edara approval.

4.5.2. Verify quantity of materials from the BOQ/Drawings prior to placing of orders and advise edara if there are any discrepancies.

4.5.3. Notify edara in advance in the event of any delays in the delivery of materials that may affect the completion of works according to the contract programme.

4.5.4. To allow for builders work in connection with installation.

4.5.5. Receive samples of materials delivered to site and install them according to the manufacture’s recommendation or specification or as detailed in the drawings and obtain edara/Consultant approval on all materials included as fix only in the B.O.Q. E.g. Light Fittings, Sanitary Ware, Floor Tiles, Wall Tiles, etc.

4.5.6. To co-ordinate with suppliers to receive materials at site and check compliance of materials on arrival with the purchase order and the contract specification.

4.5.7. To notify edara in writing in case of any discrepancies in the materials delivered.

4.5.8. To forward the original delivery note to edara duly signed by the Contractor’s representative responsible for inspecting the materials on arrival.

4.5.9. To suitably protect and store materials as per the supplier/manufacture’s instructions to prevent any damage in due course of storage or movement within the site.

4.5.10. To maintain proper inventory and issue records and be responsible for the security of materials.

4.5.11. To co-ordinate with Subcontractors and issue materials as they are required on site, including addressing queries regarding identification of materials.


Doc No.

: EDA-04-16

Rev : 0

Date : 12 Mar 05


4.6. Responsibilities of Nominated Subcontractors

4.6.1. To verify the quantities as per approved shop drawings /specification prior to placing of orders with the Suppliers.

4.6.2. To issue complete set of shop drawings to edara via the Main Contractor to verify the final quantities of material in order to procure materials on time to suit the construction programme. Sufficient time shall be allowed for procurement, anticipating the delivery period of materials and obtaining approvals of shop drawings.

4.6.3. To co-ordinate with the Main Contractor and receive all materials and distribute on site during the installation stage

4.6.4. To check delivery orders at the time of delivery and advise the Main Contractor if there are any additional/missing items required for the installation.

4.6.5. To take responsibility for any loses, breakages and damages to material during distribution or installation.

4.6.6. To allow for builders work in connection with installation.

4.6.7. To install samples of materials to the satisfaction of the Main Contractor, Consultant and edara.

4.6.8. To test and commission fixtures and equipment and notify edara through the Main Contractor of any defects found.

4.6.9. Handover installed items to the Main Contractor.


5.1. Supplier Pre qualifications

5.2. Procurement Programme for Employer Supplied Materials

5.3. Employer’s Approval of Short Listed Suppliers

5.4. Supplier Tender and Adjudication Records

5.5. Employer’s Approval of the Supplier

5.6. Purchase Orders

5.7. Delivery Notes

5.8. Inspection Records (where relevant)


Doc No.

: EDA-04-17

Rev : 1

Date : 16 Oct 05

FIELD INSTRUCTIONS Page : 1 of 2


1.1. To define the method of issuing instructions to the Contractor based on routine observance of activities to maintain compliance with the project requirements and accepted practices within the construction industry.

Note

1.2. Field instructions shall not be used in the following cases: For instructing changes to the Contractor – irrespective of whether

the change involves time/cost or not. Where the contractor’s work is rejected – in which case a Non-

conformance Report shall be raised

Note

2. DEFINITION

2.1. None Note

3. ABBREVIATION USED

3.1. FI – Field Instruction

4. PROCEDURE

4.1. FIs are raised using the Form EDA-04-17-A and issued to the Contractor with copies to edara and the QS along with a transmittal form (generated using the Project Management Tool).

Consultant

4.1.1. FIs are sequentially numbered and registered in an FI Log (use Form EDA-04-17-B or the format prescribed in the Project Management Tool where such facility is available). The numbering of FIs shall be:

Contract No./FI-XXX.

Consultant

Contract No. – This is the reference number assigned by the Consultant to the particular contract against which the FI is issued. For project with only one contract, the contract number will be the project number itself.

FI – denotes Field Instruction. XXX – denotes the serial number assigned by the Consultant.

4.1.2. The FI contains a reference to the location and the relevant drawing or the contract document/specification that the instruction refers along with the description of the required actions.

Consultant

4.2. A written response from the Contactor is not required unless otherwise specified by the Consultant in the FI.

Note

4.3. The Consultant shall monitor the Contractor’s site activities to ensure compliance with the FI and accordingly signs off the FI.

Consultant

4.4. Distribution of the FI subsequent to follow-up shall take place along with a transmittal form (generated using the Project Management Tool) as follows:

Original - edaraCopies - Consultant, Contractor and Others (as required).

Consultant


Doc No.

: EDA-04-17

Rev : 1

Date : 16 Oct 05

FIELD INSTRUCTIONS Page : 2 of 2

5. RECORDS

5.1. Records Maintained by edara:

Field Instructions

5.2. Records Maintained by the Consultant:

Field Instructions

Field Instruction Log


Doc No.

: EDA-04-18

Rev : 1

Date : 16 Oct 05

NON-CONFORMANCE REPORTS Page : 1 of 2


1.1. To define the method of notifying the Contractor of work(s): not in compliance with Project Requirements (specification, drawings,

BOQ, edara procedures or other mutually agreed Procedures), undertaken without adequate safety precautions or where the Contractor fails to comply with any instructions given by

consultant/edara/Client.

Note

1.2. Non-conformance report shall be raised for any work that is rejected or involves repair/rework.

Consultant

1.3. Payment of the non-compliant work shall be withheld until the work is accepted by the Consultant.

Note

2. DEFINITION

2.1. Work – The term ‘Work’ used in the context of this procedure includes materials purchased by the Contractor or Sub Contractors.

Note


3.1. NCR – Non-Conformance Report

4. PROCEDURE

4.1. Consultant themselves or following advice from edara raises NCRs (as per Form EDA-04-18-A) in situations cited under clause 1 of this procedure. NCRs are issued to the Contractor (original) with copies to edara and the QS.

Consultant

4.1.1. NCRs are sequentially numbered and registered in a NCR Log (use Form EDA-04-18-B or the format prescribed in the Project Management Tool where such facility is available). The numbering of NCRs shall be as:

Contract No/NCR-XXX.

Consultant

Contract No. – This is the reference number assigned by edara to the particular contract against which the NCR is raised. For project with only one contract, the contract number will be the project number itself.

NCR – denotes Non Conformance Report. XXX – denotes the serial number assigned by edara.

4.1.2. The NCR contains description of the non-conformity along with reference to the location and the relevant drawing/contract document/specification against which the non-conformity is raised.

Consultant

4.2. If the Contractor agrees with non-conformity, they shall return the NCR form (original) with the corrective action proposed to dispose the non-conformity and actions required to prevent its recurrence.

Contractor

4.2.1. If the Contractor disagrees with the non-conformity, they shall return back the NCR form (original) to the Consultant and copy to edara with their justification in writing; and the Consultant together with edara reviews the

Note


Doc No.

: EDA-04-18

Rev : 1

Date : 16 Oct 05

NON-CONFORMANCE REPORTS Page : 2 of 2

Contractor’s justification in light of the supportive documentation to decide on the appropriate instruction to be issued to the Contractor in order to maintain the quality of works as per the Project requirements. Where required, the Employer’s involvement may also be sought in settling disagreements in a mutually amicable manner.

4.3. Any work against which an NCR is raised shall be stopped until corrective measures are agreed by the Consultant. Non-conforming materials shall be segregated and suitably identified to prevent inadvertent use.

Contractor

4.4. Consultant reviews the actions proposed by the Contractor and provide comments or approval to the Contractor to proceed with the corrective measures.

Consultant

4.5. Consultant shall then monitor the Contractor’s site activities and closeout the NCR subject to implementation of the corrective actions.

Consultant

4.5.1. Where corrective actions are not taken by the Contractor in a reasonable time, edara may opt to correct the non-conformities and back charge the Contractor for such corrections as per the Conditions of Contract.

Note

4.6. Distribution of the NCR subsequent to follow-up and closeout by edara shall be as follows:

Original - edara Copies - Consultant, QS, Contractor and Others (as required).

Consultant

4.7. The NCR log shall be updated to show the various stages until close out of the NCR.

Consultant

5. RECORDS

5.1. Records Maintained by edara: edara

NCRs and supporting documents

5.2. Records Maintained by the Consultant: Consultant

NCRs and supporting documents

NCR Log


Doc No.

: EDA-04-19

Rev : 0

Date : 12 Mar 05

EMPLOYER COMPLAINTS Page : 1 of 2


1.1. To describe the method of handling complaints brought to the attention of edara by the Employer.

Note

1.2. This procedure applies to any complaint received by edara LLC other than snagging.

Note

2. DEFINITION

2.1. None Note


3.1. ECR – Employer Complaint Record

4. PROCEDURE

4.1. Complaints received from the Employer shall be registered and corrected where justified under the project requirements (Specifications, Drawings, BOQ, etc). There shall also be an enquiry into its cause and appropriate measures shall be taken to prevent future recurrence.

Note

4.2. The edara Manager receiving the complaint shall review it and confirm its genuineness against the project requirements. Where justified, the complaint is recorded on an ECR Form (EDA-04-19-A).

edara Manager

4.2.1. Employer complaints are sequentially numbered and registered in an Employer Complaint Log (Form EDA-04-19-B) maintained by the site secretary. The numbering of Employer Complaints shall be as per the following format:

Project No./ECR-XXX.

edara Secretary

Project No. – This is the reference number assigned by edara to the Project.

ECR – denotes Employer Complaint Record. XXX – denotes the serial number assigned by edara.

4.3. The Manager shall take the necessary action(s) to address the complaint and provide a written response to the Employer regarding the action(s) taken. Prior to informing the Employer, the Manager shall discuss the actions with the General Manager. The actions shall also be recorded on the ECR.

Where the corrective actions are not taken immediately due to valid reason(s), the Employer shall be informed accordingly (in writing).

edara Manager

4.4. The Manager shall also investigate the cause of the complaint with a view to preventing future recurrence of the same. The results of the review and actions arising shall be recorded on the ECR.

Manager


Doc No.

: EDA-04-19

Rev : 0

Date : 12 Mar 05

EMPLOYER COMPLAINTS Page : 2 of 2

4.5. The Employer Complaint Record Forms shall then be forwarded to a Senior Manager (edara Senior Project Manager or edara General Manager) for review and Distributed as follows:

Original - edara Site FileCopies - edara GM, edara QA Manager and Others (as required).

edara Manager


5.1. Employer Complaint Records

5.2. Employer Complaint Log


Doc No.

: EDA-04-21

Rev : 0

Date : 12 Mar 05

CONTRACTOR’S DAILY ACTIVITY REPORT Page : 1 of 1


1.1. To describe the Daily Activity Report issued by the Contractor to edara. Note

2. DEFINITION

2.1. None Note


3.1. None

4. PROCEDURE

4.1. The Contractor shall prepare and submit a Daily Activity Report as per Form EDA-04-21-A to summarise the main activities engaged at the site during the day.

Contractor

4.2. This report shall be submitted at the edara Site Office prior to 09.00 a.m. for the previous day’s activities.

Contractor

4.3. Daily Activity Reports are sequentially numbered as per the following format:

Contract No./DAR-XXX.

Contractor

Contract No. – This is the reference number assigned by edara to the particular contract against which the DAR is raised. For project with only one contract, the contract number will be the project number itself.

DAR – denotes Daily Activity Report. XXX – denotes the serial number assigned by the Contractor.

4.4. The various topics included in this report are as follows: Note

4.4.1. General Information: Project reference, names of parties involved in the Project.

4.4.2. Contractor’s Manpower: Staff, direct labour and indirect labour.

4.4.3. Equipment: Type, quantity, hours worked and status (i.e. idle or repair)

4.4.4. Subcontractor’s Manpower: Staff, direct labour and indirect labour. Separate entries are required for each Subcontractor.

4.4.5. Materials Delivered to Site

4.4.6. Visitors to Site

4.4.7. Construction Activities: Description of work ongoing and completed during the day including those of the subcontractors. Specifics of concrete pour shall also be provided including the axis and levels.


5.1. Contractor’s Daily Activity Reports


Doc No.

: EDA-04-22

Rev : 1

Date : 16 Oct 05

CONSULTANT’S MONTHLY PROGRESS REPORT Page : 1 of 2


1.1. To describe the Monthly Progress Report issued by the Consultant to edara. Note

2. DEFINITION

2.1. None Note


3.1. None

4. PROCEDURE

4.1. The Consultant shall prepare and submit Monthly Progress Reports to summarise activities engaged during the month.

Consultant

4.2. This report shall be submitted to edara on or before the 10th of every month (e.g. Progress report for Jan should be submitted on or before 10th Feb).

Consultant

4.3. Contents of the Report

4.3.1. Executive Summary:

This shall contain the following information:

4.3.1.1. Progress Summary – As per the table in Appendix EDA-04-22-A.

4.3.1.2. Main events during the month – Summarise them as shown below:

1. Package 1

A. Designi. …………………………ii. …………………………

B. Construction Progressi. …………………………ii. …………………………

C. Tendering Processi. …………………………ii. …………………………

2. Package 2

4.3.1.3. Matters of Concern (In brief)) – Summarise them as shown below:

1. Package 1

i. …………………………ii. …………………………

2. Package 2


Doc No.

: EDA-04-22

Rev : 1

Date : 16 Oct 05

CONSULTANT’S MONTHLY PROGRESS REPORT Page : 2 of 2

i. …………………………ii. …………………………

4.3.2. Progress Compared to Programme (In Detail):

Provide the status of various activities as they appear in the programme whether they are ahead, behind programme, reasons why and recommendations to recover lost time as appropriate.

4.3.3. Matters of Concern (In Detail):

Specify actual and potential problems faced at site along with recommendations to overcome the problems.

4.3.4. Consultant’s Manpower on the Project.

Provide name and designation of all consultants’ personnel engaged in the project.

4.3.5. Summary of Request for Information as follows:

Received From(Add/delete rows as

necessary)

REQUEST FOR INFORMATIONDuring Previous Month Nos. Outstanding

To DateNos. Received Nos. Replied

4.3.6. Summary of Contractor Submittals as follows:

Received From(Add/delete rows as

necessary)

SUBMITTALSDuring Previous Month Nos. Outstanding

To DateNos. Received Nos. Replied

4.3.7. Summary of Field Instructions as follows:

Issued To(Add/delete rows as

necessary)

FIELD INSTRUCTIONSDuring Previous Month Nos. Outstanding

To DateNos. Issued Nos. Closed

4.3.8. Summary of Non Conformance Reports as follows:

Issued To(Add/delete rows as

necessary)

NON-CONFORMANCE REPORTSDuring Previous Month Nos. Outstanding

To DateNos. Issued Nos. Closed

4.3.9. Attachments Field Instruction Log Non-Conformance Report Log


5.1. Consultant’s Monthly Progress Reports


Doc No.

: EDA-04-23

Rev : 1

Date : 16 Oct 05

MONTHLY PROGRESS REPORT TO THE EMPLOYER Page : 1 of 4


1.1. To describe the format, content and preparation of the monthly progress reports issued to the respective Employers by edara.

Note

1.2. The purpose of the monthly progress report is to provide information that is significant to the Employer in terms of cost, programme, variations and raise areas of concern if any for Employer’s action/information.

Note

1.3. Minor projects like the fit out works performed for Emirates Bank are exempted from the scope of this procedure.

Note

2. DEFINITION

2.1. None Note


3.1. None

4. PROCEDURE

4.1. Reporting Cycle

4.1.1. Progress reports are issued on or before the 15th of every month to summarise the progress until the end of the previous month.

Note

4.1.2. The Project Managers originate this report with inputs from various personnel within the Project Management team, consultant and the QS, as appropriate.

edara Project Managers

4.1.3. Any information assumed or estimated in the report, shall be explicitly specified as such and adjusted in the reports generated in the month(s) that follow.


4.1.4. The report shall be completed and issued to the Senior Project Manager well in advance (at least 2 working days in advance) for review and approval.


4.1.5. Approved monthly reports are distributed to the Employer along with a Transmittal (generated using the Project Management Tool, where available). Two additional copies shall also be generated – one for edara General Manager and the other maintained at Site.


4.2. Layout and Format

4.2.1. Page headers shall contain the logo of the Employer and the footers contain the page numbers, the month for which the report is issued and the logo of edara.

4.2.2. Main headings shall be in BOLD UPPER CASE, Arial size 14; sub headings in bold Title Case, Arial size 12. All other text to be Arial size 10 or 11 with 1.5 line spacing and aligned as “justified”.

4.2.3. All date formats shall be day (2 digit), month (in words), year (4 digit) format. E.g. 01 January 2004.


Doc No.

: EDA-04-23

Rev : 1

Date : 16 Oct 05


4.2.4. The cover page shall contain an appropriate image of the project along with the Employer and edara logos. The cover page shall not contain headers and footers. Refer Appendix EDA-04-23-A for a sample Cover Page.

4.3. Contents of the Report

4.3.1. Cover Page

Described in clause 4.2.4

4.3.2. Authorisation Page

Contains the signatures of the various people involved in the preparation, review and authorisation of the progress report.

Also shows the distribution of the progress report.

Refer Appendix EDA-04-23-B for a sample Authorisation Page.

4.3.3. Table of Contents

Lists the contents of the report along with the relevant page numbers.

4.3.4. Introduction

Description of the project, its locations, its features and special characteristics if any – to be as brief as possible and restricted to one page where possible.

4.3.5. Executive Summary

This shall contain the following information:

4.3.5.1. Financial Summary – As per the table in Form EDA-04-23-C.

4.3.5.2. Progress Summary – As per the table in Form EDA-04-23-D.

4.3.5.3. Main events during the month – Summarise them as shown below:

Package 1

o Design …………………

……… …………………

………

o Construction Progress …………………

……… …………………

………


Doc No.

: EDA-04-23

Rev : 1

Date : 16 Oct 05


o Tendering Process …………………

……… …………………

………

Package 2

4.3.5.4. Matters of Concern (In brief)) – Summarise them as shown below:

1. Package 1

………………………… …………………………

2. Package 2

………………………… …………………………

4.3.6. Progress Compared to Programme (In Detail)

Provide the status of various activities as they appear in the programme, whether they are ahead, or behind schedule, reasons why and recommendations to recover lost time as appropriate.

4.3.7. Matters of Concern (In Detail)

Specify actual and potential problems faced at site along with recommendations to overcome the problems.

4.3.8. Project Photographs

Include a maximum of 6 photographs per package. The exact number is however left to the discretion of the concerned Project Manager based on the scope and stage of the project.

Provide a brief against the photos to familiarise the reader with the areas photographed.

4.3.9. Safety

A brief description of the safety statistics shall be provided, preferably in a tabular form which includes:

Number of reportable accidents since the last report, Number of mandays achieved since the last lost time accident, Accident frequency rates and severity rates, and Any other relevant information related to safety.

4.3.10. Attachments

4.3.10.1. Updated Programme


Doc No.

: EDA-04-23

Rev : 1

Date : 16 Oct 05


4.3.10.2. Key Progress Indicators: Planned versus actual value of work Planned versus actual key activities

4.3.10.3. Anticipated Cost Report:4.3.10.4.

4.3.10.5. Variations Summary

4.3.10.6. Payment Summary

4.3.10.7. Graphical representation of the status of variations (as described in change management procedure).

4.3.10.8. Schedule of agreements issued with dates of validity, amounts, etc of Bonds, Insurances, etc.

4.3.10.9. Schedule of Project Participants and Contacts


5.1. Monthly Progress Reports


Doc No.

: EDA-04-24

Rev : 0

Date : 12 Mar 05

TAKING OVER Page : 1 of 3


1.1. To describe the method of taking over completed sections of the Project from the Contractor.

Note

1.2. The procedure applies to both partial and complete take over as specified in the General Conditions of Contract.

1.3. This procedure neither replaces nor supersedes the Contract, but provides guidance to implement the Contract.

Note

2. DEFINITION

2.1. Snags – Unfinished items that need to be completed by the Contractor e.g. unfinished skirting boards, missing door knobs, unpainted parts etc.

Note

2.2. Defects – The non-conformity of the result of a test with the specification for a characteristic (ISO 2071). It indicates a deviation from some (perceived) standard, which may, but will not necessarily result in a failure.

Note

2.3. Outstanding works – Works to be completed by the Contractor to rectify any snags reported.


3.1. TOC – Taking Over Certificate.

3.2. CRI – Contractor Request for Inspection

4. PROCEDURE

4.1. General

4.1.1. As soon as the Contractor becomes confident that the Project has achieved substantial completion and the works have satisfactorily passed any tests on completion prescribed by the Contract, the Contractor may give a notice to edara with a copy to the Employer for substantial completion inspection, accompanied a written undertaking to finish any outstanding works during the Defects Liability Period.

Contractor

4.1.2. edara shall within 21 days of receipt of the Contractor’s notice, either issue to the Contractor a TOC or submit a List of Outstanding Snags (Form EDA-04-24-A) to be remedied by the Contractor for issuing a TOC.


4.1.3. Prior to issuing the TOC, edara shall arrange for an inspection along with the Consultant and the Contractor (and Employer and/or Operator also where required).


4.1.4. The Consultant records snags noted during the inspection on the attached form (Form EDA-04-24-A) and forward a copy to edara. The list of snags will also include any defects noted during such inspections.

Consultant

4.1.5. If the snags are minor in nature, a TOC may be issued to the Contractor at the sound judgement of edara and the Consultant, based on the Contractor’s



Doc No.

: EDA-04-24

Rev : 0

Date : 12 Mar 05


undertaking to complete the outstanding works.

4.1.6. If the event of major snags, the Contractor shall be issued with a TOC within 21 days from the date the snags are remedied to the satisfaction of edara and the Consultant.


4.1.7. It is required to consult with the Project’s Contracts Administrator where the date of completion specified in the TOC could lead to any contractual disputes with the Contractor.


4.2. Preparation and Issue of TOC

4.2.1. TOCs are prepared by edara (as per Form EDA-04-24-B), subject to the conditions stated under clause 4.1 of this procedure.


4.2.2. A certificate number shall be assigned to all TOCs as per the following format:

TOC/Project No./ Contract No./ XXX.

edara Secretary

TOC – denotes Taking Over Certificate. Project No. – Is the reference number assigned by edara to the

particular project. Contract No. – Is the reference number assigned by edara to the

particular contract against which the TOC is issued. For projects with only one contract, the contract number will be the project number itself.

XXX – denotes the serial number assigned by edara. A separate register shall be maintained to facilitate this.

4.2.3. Date of completion of the Section(s) taken over and the Defects Liability Period shall be stated in the TOC.


4.3. TOC shall be signed by the Consultant and edara Senior Project Manager and distributed as follows along with a transmittal form (generated using the Project Management Tool):Original – to ContractorCopies – Employer, edara, Consultant and QS

edara Secretary

4.4. Follow up of Snags

4.4.1. The Consultant shall re-inspect and sign-off the ‘List of Outstanding Snags’ subject to rectification of all snags by the Contractor. Outcome of the re-inspection shall be copied to edara for information and appropriate action, which may include instructing the Contractor to carry out further remedial actions.

Consultant/edara Project

Manager

4.5. Handover to the Employer

4.5.1. The following documents/items shall be handed over to edara by the Contractor at the time of Substantial Completion and prior to the issue of the TOC (unless in the event of urgent tenant occupancy, where some of these shall be provided within 28 days from the issue of the TOC).

Contractor

4.5.1.1. As built drawings.4.5.1.2. Operation and Maintenance Manuals and Catalogues.


Doc No.

: EDA-04-24

Rev : 0

Date : 12 Mar 05


4.5.1.3. Keys.4.5.1.4. Guarantees and Warranties.4.5.1.5. List of contact names and telephone numbers.4.5.1.6. Options on Maintenance Agreements.4.5.1.7. No Objection Certificates (NOCs) from Local Authorities.4.5.1.8. Identification of the Security Systems to be used and its

mechanism.4.5.1.9. Any other as required by the Contract.

4.5.2. edara shall handover the above items/documents to the Employer and maintain records of the handover.



5.1. Contractor’s Notice of Substantial Completion.

5.2. List of Outstanding Snags

5.3. Taking Over Certificates.

5.4. Record of hand over of documents/items to the Employer as per clause 4.5.


Doc No.

: EDA-04-25

Rev : 1

Date : 16 Oct 05

DEFECTS LIABILITY Page : 1 of 2


1.1. To describe the method of:

Correcting deficient workmanship or materials discovered during the Defects Liability Period and

Issuing the Defects Liability Certificate to the Contractor at the end of the Defects Liability Period.

Note

1.2. This procedure neither replaces nor supersedes the Contract, but provides guidance to implement the Contract.

Note

2. DEFINITION

2.1. Defects Liability Period – It is a period specified in the contract starting from the date of completion of works as stated in the TOC, during which the Contractor is liable to rectify any defects as defined in the Conditions of Contract. Such remedial works shall be undertaken at the Contractor’s cost and in compliance with the Contract specifications.

Note

2.2. Defects – The non-conformity of the result of a test with the specification for a characteristic (ISO 2071). It indicates a deviation from some (perceived) standard, which may, but will not necessarily result in a failure.

Note

2.3. Outstanding Works – Works to be completed by the Contractor to rectify any snags reported.


3.1. TOC – Taking Over Certificate.

3.2. DLP – Defects Liability Period

3.3. DLC – Defects Liability Certificate

4. PROCEDURE

4.1. Correction of Defects During the Defects Liability Period

4.1.1. The responsibilities of edara pertaining to the management of defects shall be in accordance with the contract with the Employer.

Note

4.1.2. Defects brought to the attention of edara (by Tenant, Operator, Employer, etc) are recorded on a “Defects Notice” (either use Form EDA-04-25-A or an appropriate form approved by the Senior Project Manager). A copy of the Defects Notice is issued to the concerned Contractor for taking the required corrective actions. Also, a copy is forwarded to the Consultant to follow up corrective actions taken by the Contractor.


4.1.3. “Defects Notices” are numbered as per the following format:Contract No./ DN – XXX


Contract No. – Is the reference number assigned by edara to the particular contract against which the Defects Notice is issued. For


Doc No.

: EDA-04-25

Rev : 1

Date : 16 Oct 05

DEFECTS LIABILITY Page : 2 of 2

projects with only one contract, the contract number will be the project number itself

DN – denoted Defects Notice XXX – denotes the serial number assigned by edara.

4.1.4. The Consultant shall follow up and sign off the Defects Notice subject to rectification of the defects by the Contractor. Outcome of the inspections are copied to edara for information and appropriate action which may include instructing the Contractor to carry out further remedial actions.

Consultant

4.1.5. edara shall maintain an up-to date Defects Notice Log (Form EDA-04-25-B) to register and track Defect Notices issued.


4.2. Conditions for Issue of Defects Liability Certificate

4.2.1. DLC is issued to the Contractor upon expiration of the DLP subject to the Contractor’s fulfilment of all the following:


Completion of all outstanding works notified to the Contractor along with the issue of ‘Taking Over Certificates’.

Execution of all works of amendment, reconstruction, and remedying defects, shrinkages or other faults notified to the Contractor:- During the DLP, and- As a result of a final inspection made by or on behalf of edara prior

to the expiration of the DLP.

4.3. Preparation of Defects Liability Certificate

4.3.1. DLC is prepared by edara (as per Form EDA-04-25-C) subject to the conditions stated under clause 4.2.1 of this procedure.


4.3.2. DLCs are numbered as per the following format:DLC/Project No./Contract No.

edara Secretary

DLC – denotes Defects Liability Certificate. Project No. – Is the reference number assigned by edara to the project. Contract No. – Is the reference number assigned by edara to the

particular contract against which the DLC is issued. For Projects with only one contract, the contract number will be the Project number itself.

4.4. DLC shall be signed by the Consultant, edara Senior Project Manager and the Employer and distributed as follows along with a transmittal form (generated using the Project Management Tool):Original – Contractor; Copies – Employer, edara, Consultant and QS

edara Secretary


5.1. Defects Notices

5.2. Defects Notice Log

5.3. Defects Liability Certificate


Doc No.

: EDA-04-26

Rev : 0

Date : 12 Mar 05

CONSULTANT, QS, CONTRACTOR AND SUPPLIER PAYMENTS

Page : 1 of 3


1.1. To describe the method of raising payment applications by Consultants (including QS), Contractors and Suppliers and its review and approval by edara and the Employer.

Note

1.2. The currency used in the Application for Payments and Payment Certificates shall be UAE Dirhams, unless the Consultancy Agreement/ Contract specifically states otherwise.

Note

2. DEFINITION

2.1. None. Note


3.1. AFP – Application for Payment.

4. PROCEDURE

4.1. Payments to Consultants

4.1.1. edara shall in accordance with the respective Consultancy Agreements review AFPs received from the Consultants/QS and make recommendations to the Employer for payment.

Note

4.1.2. The Consultants/QS shall submit an AFP in a format to be jointly agreed with edara.

Consultant/QS

4.1.3. edara Project Manager reviews the AFP, seek clarifications if any and prepares the Payment Certificate (Form EDA-04-26-A). The Payment Certificate shall then be presented to the Senior Project Manager for authorisation and issued to the Employer.

edara PM

4.1.4. The Payment Certificate shall be forwarded to the Employer along with a copy to the Consultant/QS within 5 working days from the receipt of AFP from the Consultant/QS.

edara PM

4.2. Payments to Contractors

4.2.1. Payments are made for the value of works erected satisfactorily and materials stored on or off-site in accordance with the stipulations of the Contract.

Note

4.2.2. Before submitting the AFP to edara, the Contractor shall meet with the QS to review a draft Payment Application. They shall review this in conjunction with the Consultant and agree as to what work is in place projected to the end of the month and the materials located onsite and offsite. At this stage the QS specifically reviews the quantities and the Consultant reviews the quality.

Contractor/QS

4.2.3. Subject to the approval of the draft AFP, the Contractor shall submit to edara, an itemised Application for Payment.

Contractor


Doc No.

: EDA-04-26

Rev : 0

Date : 12 Mar 05


Page : 2 of 3

4.2.3.1. The Contractor shall ensure that each AFP is accompanied by all supporting data substantiating the Contractor’s right to payment.

Contractor

4.2.3.2. Starting from the AFP No. 2 onwards, the Contractor shall submit letters from each nominated Subcontractor that they have received all their due payments up to the last payment certificate received by the Contractor.

4.2.4. Following receipt of the AFP, the edara Secretary shall attach a “Checklist for Contractor Payments” (Form EDA-04-26-C) and the documents required by the Checklist under section 1, and forwards it to the QS.

edara Secretary

4.2.5. The QS shall review and ensure that the Contractor’s Application is in line with the earlier draft agreed between both parties and accordingly certifies the AFP. The QS shall also check and ensure the validity and availability of various documents as stated under Section 2 of the “Checklist for Contractor Payments” and return the AFP, the Checklist and all attachments to edara.

QS

4.2.6. The edara Secretary shall then forward the AFP, the Checklist and all attachments to the Consultant.

edara Secretary

4.2.7. The Consultant shall review and endorse the AFP subject to the acceptance of the workmanship and materials specified in the AFP. The Consultant shall also check and verify Section 3 of the “Checklist for Contractor Payments” and return the AFP, the Checklist and all attachments to edara.

Consultant

4.2.8. The edara Secretary shall check and ensure that all documents as per Section 1, 2 and 3 of the Checklist are available and forwards the entire set to the edara Project Manager.

edara Secretary

4.2.9. edara Project Manager reviews the AFP, the Checklist and the attachments and accordingly prepares a Payment Certificate (Form EDA-04-26-B). The Payment Certificate shall then be presented to the Senior Project Manager for authorisation and issued to the Employer.

edara PM

4.2.10. edara Project Manager shall ensure that the Payment Certificate is issued to the Employer within 28 days from the date of receipt of the AFP from the Contractor.

edara PM

4.2.11. Copies of the Payment Certificate are forwarded to the Consultant, the QS and the Contractor.

edara PM

4.3. Payments to Supplier

4.3.1. Payments are made to the Supplier as per the supply contract. Note

4.3.2. The procedure of supplier payment is similar to that of the Contractor’s payments described under Clause 4.2 of this procedure with the following changes:

Note

4.3.2.1. Suppliers can issue AFP without prior consultation and agreement with the QS.

Note


Doc No.

: EDA-04-26

Rev : 0

Date : 12 Mar 05


Page : 3 of 3

4.3.2.2. The “Checklist for Contractor Payments” is replaced with “Checklist for Supplier Payments’ (Form EDA-04-26-D).

Note

4.3.2.3. Distribution of the Payment Certificate shall be as follows:Original: EmployerCopies: Consultant, QS and Supplier.

Note

4.4. Payments Summary Report

4.4.1. A summary of payments shall be maintained by the Project Manager/ Senior Project Manager as per the attached format (Form EDA-04-26-E & EDA-04-26-F) and updated on a monthly basis to show the status of payments to all parties.

edara PM/ Senior PM


5.1. Application for Payments

5.2. Payment Certificates

5.3. Checklist for Contractor Payments

5.4. Checklist for Supplier Payments

5.5. Payment Summary Reports


Doc No.

: EDA-04-28

Rev : 0

Date : 12 Mar 05

SAFETY AND WELFARE Page : 1 of 2


1.1. To describe the minimum safety practices deployed by the Contractor at site and the reports submitted to edara.

Note


Note

2. DEFINITION

2.1. Accident – Is an incident that results in fatality, injury (minor or major), property damage, fire/explosion, environmental impact or occupational illness.

Note


3.1. None

4. PROCEDURE

4.1. Site Safety Plan and Procedures

4.1.1. The Site Safety Plan and Procedures to be implemented by the Contractor shall be submitted to edara for approval within a month from the Project Kick-off Meeting. The Contractor shall ensure that the Safety Plan/Procedures takes into account the prevalent Municipality/local regulations and the minimum safety and welfare requirements stipulated in the attached instruction WI EDA-04-28-A.

Contractor

4.2. Reporting of Near Miss/Hazards and Accidents

4.2.1. Near miss/hazardous incidents and accidents that happen at site, if any, shall be reported to edara using the attached formats respectively:

Near Miss/ Hazard Report– Form EDA-04-28-A Accident Report and Investigation– Form EDA-04-28-B

Contractor

4.2.2. The above reports shall be sequentially numbered as follows:

Contract No./NMHR - XXX – for Near Miss/Hazard Reports Contract No./ARI - XXX – for Accident Report and Investigation

Forms.

Contract No. – This is the reference number assigned by edara to the particular contract against which the report is raised. For project with only one contract, the contract number will be the project number itself.

NMHR – denotes Near Miss/Hazard Report. ARI – denotes Accident Report and Investigation XXX – denotes the serial number assigned by edara.

4.2.3. The concerned edara Project Manager shall review these reports and ensure that adequate corrective and preventive measures are taken by the Contractor to correct the damages caused by the accident (where possible) and prevent recurrence.



Doc No.

: EDA-04-28

Rev : 0

Date : 12 Mar 05

SAFETY AND WELFARE Page : 2 of 2

4.3. Monthly Project Safety Statistics

4.3.1. The Contractor shall submit Project Safety Statistics on a monthly basis as per the attached format (Form EDA-04-28-C).

Note

4.3.2. This report shall be submitted to the site office of edara prior to the 10th of the following month.

Contractor

4.4. Safety Inspections

4.4.1. The Safety Officer of Union Properties conducts safety audits at the sites on an adhoc basis using the attached checklist (Form EDA-04-28-D) and reports to edara. Should there be more than one main contractor operating at site, separate checklists shall be raised for each main contractor’s area, to ease corrective action and follow up.

UP Safety Officer

4.4.2. The concerned edara Project Manager shall review the reports and liaise with the concerned Contractor(s) regarding the required corrective actions and follow up its implementation. For any violation from the safety plan/procedures and local regulations, the edara Project Manager shall issue a Non-Conformance Report to the Contractor. Areas requiring improvement are intimated to the Contractor via a Site Instruction.



5.1. Near Miss/ Hazard Reports

5.2. Accident Report and Investigation Forms

5.3. Monthly Project Safety Statistics

5.4. Safety Audit Checklists

WORK INSTRUCTION


Rev : 0

Date : 12 Mar 05

MINIMUM SAFETY AND WELFARE REQUIREMENTS Page : 1 of 8

1. Safe Access

1.1. Access to work locations to be safe from obstructions.

1.2. Site hoardings to be well maintained and kept clean.

1.3. Edge protection for walkways above 2 m from the ground level.

1.4. Holes to be protected with fences/barriers or suitably covered.

1.5. Remove or hammer down nails from timber.

1.6. Safe lighting for dark and poor light areas.

1.7. Adequate ventilation shall be ensured at the work areas, especially those involving dusts, fumes, mists, vapours or gases.

1.8. Props for shores in place to secure structures, where required.

1.9. Official to manage site traffic

1.10. Visitors to the construction and storage areas to be provided with hard hats (with visitors label).

2. Signs, Signals and Barricades

2.1. Appropriate signs, signals and barricades shall be provided to warn the employees and site visitors of hazards and to prevent accidents.

3. Scaffolding

3.1. Design calculations to be submitted for Consultant’s approval. Design to take account of all possible loads including wind, materials, equipment, men, etc.

3.2. To provide proper access to scaffold platform.

3.3. All uprights to be fitted with base plates.

3.4. To contain strong ties to the building to prevent collapse and braced for stability.

3.5. To contain load bearing fittings where required.

3.6. Uprights, ledgers, braces and struts not to be removed during use.

3.7. The working platforms shall be free from defects (i.e. broken, split, cut, worn, warped, twisted, etc) and arranged in a manner that avoid tripping.

3.8. To fix Guard Rails (Handrails and Mid Rails) and Toe Boards where the scaffold is more than 2 meters from the ground level.

3.9. Securely fix the working platforms against strong winds.

WORK INSTRUCTION


Rev : 0

Date : 12 Mar 05


3.10. To provide barriers or warning notices for incomplete scaffolding – e.g. not fully boarded. A suitable tagging system (that reads “Ready to Use”, “Do Not Use – Incomplete Scaffolding”, etc) shall be implemented. The actual system to be used shall be included as a part of the Contractor’s Safety Plan/Procedures.

3.11. To avoid over stacking of materials on the scaffold platforms.

3.12. To inspect the scaffold on a weekly basis and after any bad whether conditions; and maintain records of inspections.

3.13. Scaffolds to be erected/dismantled only by competent (trained) personnel or a specialised third party.

3.14. Lightweight scaffolding shall not be used.

4. Formwork/False Work

4.1. Design calculations to be submitted for Consultant’s approval.

4.2. To produce method statement dealing with preventing fall of workers.

4.3. Appointment of a person to co-ordinate formwork or false work.

4.4. Props shall be properly set out on level bases.

4.5. Use correct pins in the props.

4.6. To be inspected by a competent person, against agreed design criteria before pouring concrete.

5. Ladders

5.1. To be used where ever required

5.2. To be in good condition and properly positioned.

5.3. To be located on firm and level ground.

5.4. Suitable secure ladders to prevent sliding.

5.5. Top of the ladder to be at least 1 m above the landing.

5.6. Deploy colour coded inspection system (different coloured tags for different months).

6. Excavation

6.1. Underground services to be located and marked and precautions taken to avoid them.

6.2. To deploy safe method for erecting/removal of timber supports.

6.3. Sides to be sloped or battered to prevent collapse.

6.4. To inspect daily after use of explosives or after unexpected fall of materials.

WORK INSTRUCTION


Rev : 0

Date : 12 Mar 05


6.5. Provide safe access to excavations (e.g. sufficiently long ladder).

6.6. To provide barriers to restrict personnel/plant.

6.7. Ensure stability of neighbouring buildings.

6.8. Take adequate measures to prevent risk of flooding.

6.9. Do not stack materials or drive/park vehicles near the excavation.

6.10. Provide stop blocks for vehicles to prevent tipping into excavations.

6.11. Ramp to be used only for equipment not for pedestrian.

6.12. Provide safe access for men and materials.

6.13. To have an emergency evacuation plan.

6.14. To provide excavation safety signs.

7. Roof Work

7.1. To use crawling ladders or boards on roofs inclined more than 10 degrees. Also use lifelines and safety harness in such cases.

7.2. To provide safe and recognised access to the workforce.

7.3. Provide edge protection before commencement of work.

7.4. Provide safe handhold and foothold for sloppy and slippery roofs.

7.5. To provide crawling boards for working on fragile roof materials such as asbestos cement sheets or glass.

7.6. Sky lighting areas to be properly covered or provided with barriers during sheeting operations.

7.7. Take precautions to prevent fall of debris onto others working under the work roof.

8. Transport and Mobile Plant

8.1. All plant to be in good repair (e.g. steering, hand brake, foot brake).

8.2. Drivers and operators to be trained on safe use of plant. Maximum speed limit inside the site shall be 20kph

8.3. Loading shall be as certified by a competent third party or as per the manufacturer’s recommendation.

8.4. Passengers are prohibited from riding in equipment/ plant.

8.5. To prop raised bodies of tipping lorries prior to inspection.

WORK INSTRUCTION


Rev : 0

Date : 12 Mar 05


8.6. Control on-site movements to avoid danger to pedestrians, etc.

8.7. Control of reversing vehicles by properly trained banksmen. Reverse horn is mandatory.

8.8. Drivers shall hold a valid Driving Licence.

8.9. All equipment shall carry a valid Registration Certificate.

9. Machinery and Equipment

9.1. Dangerous parts like exposed gears, chain drives, shaft, etc to be protected to prevent injury to the operatives.

9.2. All operatives shall have the necessary competency to safely operate the machinery/equipment.

10. Cranes, Hoists and Lifting Gears

10.1. To inspect on a weekly basis and maintain records of inspection.

10.2. Lifting work shall not commence without valid test certificate from a competent third party for all lifting equipment including gears (slings, belts, shackles, hooks, etc).

10.3. Tower cranes design calculations shall be submitted for Consultant’s approval.

10.4. Drivers to possess valid operating license.

10.5. All controls to be clearly marked.

10.6. Banksman/Slinger to be adequately trained to provide signals to the operator, attached loads in correct and safe manner and should be knowledgeable about the lifting limitations of the crane.

10.7. For cranes with varying operating radius, clearly mark safe working loads against the operating radii.

10.8. Lifting equipment above 1 ton to be fitted with automatic Safe Load Indicator.

10.9. There shall be a routine preventive maintenance programme for the equipment. Maintenance records to be maintained.

10.10. There shall be suitable communication accessories made available where appropriate like walky-talky.

11. Electricity

11.1. To the extent possible, electricity operated equipment to be 110 V.

11.2. Adequate measures to be taken to protect portable electric tools and equipment from mechanical damage and wet conditions.

11.3. Power cables to be routed either overhead or underground to avoid any damages/ tripping hazard.

WORK INSTRUCTION


Rev : 0

Date : 12 Mar 05


11.4. Damaged cables shall be removed from the site.

11.5. Joining cables with insulation tapes is prohibited - to use industrial sockets instead.

11.6. Use proper plugs to connect to power points – inserting naked wire directly to the socket is prohibited.

11.7. Take adequate precautions to prevent power cables interfering with the operation of construction equipment and vehicles.

11.8. To have a documented procedure for obtaining “Hot Work Permits’ and comply with the same.

11.9. Electrical Safety Signs must be provided with all electrical facilities on site such as Distribution Panels or Generators etc.

12. Risks to the Public

12.1. To identify all risks to members of the public on and off site, e.g. materials falling from scaffold etc., site plant and transport (access/egress) and implement precautions, e.g. scaffold, fans/nets, banks men, warning notices, etc.

12.2. Provide barriers to protect/isolate persons and vehicles.

12.3. To provide adequate site perimeter fencing to keep out the public and particularly children.

13. Work in Public Area

13.1. All risk involved to be identified and suitable measures taken to counter them.

13.2. Method statement to be submitted to edara for approval prior to commence such work.

13.3. Obtain approval from local authorities (traffic dept for any road closures – in such cases temporary diversions must be in place, municipality, etc).

13.4. Safety barriers shall be erected/maintained.

13.5. Safety signs and lighting shall be installed/maintained.

13.6. Changes made if any shall be reinstated to the satisfaction of the local authorities within the shortest possible time.

14. Cartridge Operated Tools

14.1. The manufactures instruction shall be strictly complied with in operating and maintaining/cleaning the equipment.

14.2. No person may operate, clean, maintain or repair any cartridge operated tool without possessing a certificate of competency (from the relevant tool vendor) which identifies the particular model that the person is qualified to handle.

14.3. The operators shall wear suitable safety gadgets (goggles, ear muffs, safety belts).

WORK INSTRUCTION


Rev : 0

Date : 12 Mar 05


14.4. A secure place shall be provided for storing guns and cartridges when not in use. Storage shall be fireproof, dry and be capable of being locked and situated in a clear and easily accessible location where constant supervision can be maintained.

14.5. A documented inventory system of issuing and returning cartridges and tools against signatures shall be maintained.

14.6. Where tools are used in high-risk areas, a Hot Work Permit shall be obtained before work commences.

15. Fire - General

15.1. Provide sufficient number and types of fire extinguishers.

15.2. Escape routes shall be kept clear.

15.3. Provide a fire assembly area.

15.4. Provide workers with adequate training on what to do in the event of a fire emergency.

15.5. Do not over stock combustible materials at site.

15.6. Waste materials shall be removed regularly from site.

16. Fire – Flammable Liquids

16.1. Provide proper storage area for flammable liquid away from any source of ignition and in a no smoking areas, with appropriate signage that reads “flammable liquids”, “no smoking”.

16.2. Amount of flammable liquid issued from the store to be kept to a minimum (issue quantity for the day’s work only).

16.3. Only store in containers approved for the storage of inflammable liquids.

17. Fire – Compressed Gases, e.g. Oxygen, LPG, Acetylene

17.1. Compressed gas cylinders shall be used and stored only in an upright position. They shall not be exposed to sparks, hot slag, or flames unless provided with fire shields.

17.2. Compressed gas cylinder valves shall be closed completely whenever: 1) work is finished, 2) the cylinders and empty, or 3) the cylinders are moved.

17.3. Gauges shall be removed and valve protection caps put in before moving cylinders, except when the cylinders are secured in a carrier designed for such use.

17.4. Cylinders shall be stored in well-protected, ventilated, dry locations and separated at least 6 m (or by 1.5 m high barrier with a 1-hour fire rating) from highly combustible materials, and away from egress routes such as stairways and elevators.

17.5. Compressed gas cylinders will not be used as, or placed where they may become part of an electrical circuit.

WORK INSTRUCTION


Rev : 0

Date : 12 Mar 05


17.6. Compressed gas cylinders shall not be hoisted by the valve cap or by means of magnets or slings.

17.7. Damage and defective cylinders shall not be accepted – they shall be tagged and returned to the vendor.

17.8. To have a documented procedure for obtaining “Hot Work Permits’ and comply with the same.

18. Noise

18.1. Noise levels shall be within industry norms and local regulations. At Dubai, the permissible noise exposure levels are defined in the Code of Construction Safety practise issued by Dubai Municipality.

18.2. To assess noise levels and provide adequate ear protection wherever necessary.

18.3. Workers shall use ear protection where they work in noisy surroundings for extended periods of time.

18.4. Noise producing plant and machinery shall be fitted with silencers/mufflers, where required.

19. Radiation

19.1. Any activity that involves the use of radioactive materials, X-rays or laser shall be performed by competent persons specially trained in the proper and safe operation of such equipment.

20. Health

20.1. Identify hazardous substances, e.g. asbestos, lead, solvents, etc. and assess the risk.

20.2. To the extend possible avoid the use of substances that are harmful to health.

20.3. Safety information from the supplier/manufacturer shall be obtained for hazardous materials and the supplier’s/manufacture’s safety instructions shall be complied.

20.4. Use suitable equipment to protect the head, eyes, hands and feet where appropriate.

20.5. Wear adequate protective clothing/accessories when engaged with substances/equipment likely to pose a health hazard.

20.6. Keep other workers who are not protected out of danger areas.

20.7. Provide fresh air supply artificially where required.

20.8. Emergency procedures to in place for rescue from confined spaces.

21. Manual Handling

21.1. To be supervised by the Contractor.

21.2. Avoid manual handling where there is a risk of injury. If unavoidable, assess and reduce risks.

WORK INSTRUCTION


Rev : 0

Date : 12 Mar 05


22. Waste Disposal

22.1. Adequate waste collection and disposal facilities to be provided.

22.2. Provide chutes for waste disposal, where required.

23. Storage and Housekeeping

23.1. Materials to be stored in a safe manner, especially the inflammable and volatile materials.

23.2. To engage an ongoing housekeeping programme.

24. Induction, Tool Box Talks and Training

24.1. All new arrivals including employees of the subcontractors shall be inducted on the site safety requirements.

24.2. There shall be a regime of regime of continuous toolbox talks and training.

24.3. Records of induction, tool box talks and training to be maintained and made available to edara on request.

25. Welfare

25.1. Provide adequate toilet and washroom facilities including soap and tissues/towels.

25.2. Provide wet weather gear for those working in wet conditions.

25.3. Air-conditioned site hut or shaded area where workers can take shelter and have meals to be provided.

25.4. Provide first aid facilities.

25.5. Provide prayer area and ablution facility.


Doc No.

: EDA-04-29

Rev : 0

Date : 12 Mar 05

IT GUIDELINES AND RECOMMENDATIONS FOR SITES Page : 1 of 12


1.1. To provide guidelines and recommendations related to procurement of IT products and its safe usage.

Note

1.2. This procedure has been prepared by the IT Dept of Union Properties and changes to this procedure require consent of the IT Manager of Union Properties.

Note

1.3. Topics covered by this procedure are as follows: Note

1.3.1. Hardware – Guidelines and RecommendationsA. General GuidelinesB. Recommendations

1.3.2. Software – Guidelines and RecommendationsA. General GuidelinesB. Recommendations

1.3.3. Server Room Security GuidelinesA. Checklist - Physical Security B. Checklist - Environmental Security

1.3.4. Virus Prevention Guidelines1.3.5. Backup Guidelines

A. Backup Schedule B. General Recommendations for Backup and RestoreC. Performing Backup and Restore Operations

1.3.6. Physical and Logical Security Recommendations1.3.7. Computer Usage – Health and Safety Recommendations

2. DEFINITION

2.1. None Note


3.1. SPM – Senior Project Manager

3.2. PM – Project Manager

3.3. UPG IT – Union Properties Group Information Technology Dept.

4. PROCEDURE

4.1. Hardware – Guidelines and Recommendations

4.1.1. General Guidelines

All requests for purchase of any IT Equipment should be forwarded to the respective IT Support personnel before passing them onto the local Purchase Dept – in the case of Projects, technical approval of items would suffice, as the procurement is normally done through the Contractors or other 3rd parties involved.

edara SPM/PM

All requests for purchase of any IT Equipment shall be granted only after it has been technically approved by UPG IT – in the case of Projects an

Note


Doc No.

: EDA-04-29

Rev : 0

Date : 12 Mar 05


initial technical review and approval would suffice

All purchase decisions for IT equipment are based on a variety of parameters including, but not limited to, performance, reliability, effectiveness, cost, support, warranty issues & group contract discounts.

Note

All critical hardware equipments to be insured against theft, damage etc. Note

All critical hardware to be supported by valid Annual Maintenance Contracts.

Note

All hardware should be placed in a dust free area, away from water sources, fire sources, excess moisture & humidity.

Note

All hardware devices should be placed in a proper manner, so that they are easily accessible to staff at the site office.

Note

Ensure that there is enough room around the equipment and that it is not placed into cramped spaces. Cramped spaces hamper heat dissipation which in turn affects device performance in the log run.

Note

Unless absolutely necessary, do not leave laptops or portable computers unattended, especially during non-working hours.

Note

Store removable media such as Floppy Drives, CD Drives, Disk Drives & PCMCIA (Personal Computer Memory Card International Association) cards in a secure environment.

Note

4.1.2. Recommendations

Hardware purchase recommendations are provided in Appendix EDA-04-29-A attached herewith.

Note

4.2. Software – Guidelines and Recommendations

4.2.1. General Guidelines

All requests for purchase of any software should be forwarded to the respective IT Support personnel before passing them onto the local Purchase Dept - in the case if Projects, Technical approval of items would suffice, as the procurement is normally done through the Contractors or other 3rd parties involved.

edara SPM/PM

All requests for purchase of any software shall be granted only after it has been technically approved by UPG-IT - in the case of Projects, an initial technical review and approval would suffice.

Note

All Corporate software used at site should be licensed and legal. Note

All critical software and data to be insured against theft, damage etc. Note

All critical software, applications and data to be supported by valid Annual Maintenance Contracts.

Note


Doc No.

: EDA-04-29

Rev : 0

Date : 12 Mar 05


For computers that are connected to the corporate network via dial-up, non-standard software may be used only in the following cases:

Note

- The software is not pirated or unlicensed.

- The Non-Standard Software Request form (Form EDA-04-29-B) has been filled by the requestor & duly signed by the necessary authorities (edara Project Manager, edara Senior project Manager and UPG IT Manager)

- The software has been tested under test environment conditions before moving into production.

- The Application Pre-Purchase Checklist (EBI Format) (Form EDA-04-29-C) has been duly signed by the IT Support in-charge of the testing & all results logged onto the form.

- IT Support in-charge of the respective business unit shall test the software & get the test results approved by the Manager - UPG IT

4.2.2. Recommendations

Software purchase recommendations are provided in Appendix EDA-04-29-A attached herewith.

Note

4.3. Server Room Security Guidelines

Server Room security is the responsibility of the Site Administrator/IT-in-charge at the site office. It is extremely vital that sound physical & environmental controls are in place in the server room where critical equipment that runs the business, are installed. Below are two checklists (4.3.1 & 4.3.2) that the Project Manager & Site Administrator can use for assistance in ensuring controls for the Server Room at site offices. The objective shall be to minimize any business risks

Site Administrator/IT-in Charge

4.3.1. Checklist – Physical Security

Is there adequate security for the building/site office, where the server room is located? For example, main door of the building/site office is being monitored, main door is electronically controlled using cards, security guards are guarding the site at all times, etc.

Are entry & exit points to the server room protected by electronic access control systems or other any other suitable methods?

If Access control systems are used, are access cards controlled?

Are doors secured?

Are windows (if any) secure?

Is the server room access monitored using CCTV camera systems?

Are keys & combinations controlled?


Doc No.

: EDA-04-29

Rev : 0

Date : 12 Mar 05


Are combinations, if any, changed frequently?

Is an access log book available for monitoring activity (all traffic) into & out of the server room?

Is access to the server room by 3rd parties (for maintenance or support) supervised by the Site Administrator or IT-in-charge?

Is the work area secured during non-working hours?

Are intruder detection systems activated during non-working hours?

Are hardware devices secured against theft of the equipment itself or against removal of internal/attached components?

Is storage media stored securely (safe lockable and fire resistant cabinet/chubb)

Is the hardware placed near a window where people can view the materials being processed or sight of it might tempt theft?

Have personnel controls been established for the use of each hardware device? For example, only Network Administrators may work on routers but IT Support may not , Non-IT personnel are not permitted to change/remove components connected to the router/leased line modem, etc.

Is an access log book available for monitoring activity on hardware usage? (Who operated which critical hardware & when) For example, when was the data server last shutdown (time & date), who switched the server off, what was the reason for a server shutdown, how long did this exercise take, when was the router switched off (for maintenance reasons) etc.

Has the management/site manager selected the man-in-charge for controlling IT operations?

Has the Management/Site Manager notified the IT Department of the personnel delegated for IT Operations at site?

Have policies & procedures been developed for Access control?

Have the policies & procedures been communicated to all users via emails/memos?

Are physical emergency procedures tested and documented?

Are network diagrams/important documents of reference stored securely (safe lockable and fire resistant cabinet/chub)?

4.3.2. Checklist – Physical Security

Is there proper lighting?


Doc No.

: EDA-04-29

Rev : 0

Date : 12 Mar 05


Are alarm systems installed?

Are alarm systems regularly tested?

Is access to electrical power controlled & secure?

Are temperature controlling instruments installed?

Are temperature controlling maintained & tested regularly?

Are humidity metering instruments installed?

Are humidity metering instruments maintained & tested regularly?

Have spike guards & UPS devices been installed to prevent against spikes/surges and dips/blowouts/interruptions in voltage?

Have electrical control devices been installed to protect against noise interference?

Are electrical control devices maintained & tested regularly?

Have water alert systems been installed?

Are water alert systems maintained & tested regularly?

Are protective covers available for the hardware equipment and other electrical equipment?

Is static electricity controlled?

Is carpeting/and or floor wax anti-static?

Are floors & ceilings watertight?

Is the floor raised?

Is there sufficient ventilation around hardware equipment?

Is the hardware equipment placed away from water & steam pipes?

Is the hardware area & equipment kept clear of fire sensitive materials like paper & wood residue?

Is excess stationery (more than daily use requirement) stored in the server room?

Are hazardous/combustible materials stored in the server room?

Are only small amounts of cleaning solvents allowed in the area? (Cleaning solvents in excessive quantities can be hazardous)

Are wastebaskets emptied outside the computer area to reduce dust in the air?


Doc No.

: EDA-04-29

Rev : 0

Date : 12 Mar 05


Are eatables prohibited in the server room?

Is smoking prohibited in the server room?

Are liquids prohibited in the server room?

Is the Computer room protected by FM 200 or any other standard anti-fire system?

Are Carbon Dioxide or Halon fire extinguishers strategically located? Consult the Safety Officer for tips.

Are Carbon Dioxide or Halon fire extinguishers properly marked? Consult the Safety Officer for tips

Are Carbon Dioxide or Halon fire extinguishers easily accessible? Consult the Safety Officer for tips

Are personnel trained on the use of fire extinguishers?

Have fire/smoke sensors been placed in areas where critical hardware is located?

Are the fire/smoke sensors maintained & tested regularly?

Have the fire extinguishers been inspected lately?

Are there fire escapes located & marked clearly?

Are the storage racks (if any) in the server room fire resistant?

Are environmental emergency procedures documented?

Are environmental emergency procedures tested?

Are all critical equipments used for environmental controls supported by valid annual maintenance contracts?

4.4. Virus Prevention Guidelines

4.4.1. By using simple, easy-to-follow precautions, users at site offices can ensure that their computers are less prone to virus attacks, thus enhancing system performance & productivity. Following are a few pointers that can help reduce the chances of virus attacks:


All Corporate PC’s and Servers to be installed with Corporate Antivirus package.

Note

Alerts to be automated to the IT support staff in case of virus issues. Note

Pattern file update to be automated. Note

All users should manually scan any media (for viruses) that is received for Note


Doc No.

: EDA-04-29

Rev : 0

Date : 12 Mar 05


copying/moving purposes from outside the company. Media would include CD’s, Floppies or USB Drives. IT Support Staff can be contacted for assistance.

Execution of files on storage media without first scanning them is NOT PERMITTED, as an infected file on the media, would trigger a virus and affect the performance of network at site. This leads to loss of productivity for the company.

Note

Usage of personal media to transfer data is not allowed. Personal media, if requested for use by higher authorities, should be scanned for viruses. No exceptions are recommended, however critical the urgency. Scanning is mandatory at all times.

Note

E-mails are the biggest carriers of viruses & cause maximum damage. Do not open emails that look suspicious or contain attachments ending with PIF, BAT, SCR, and EXE. As a standard though, these attachments are normally filtered using the parent anti-virus server. If a suspicious mail is encountered, contact IT Support Staff immediately for assistance BEFORE opening the e-mail.

Note

Do not allow external contractors, consultants to use their laptops to connect to the site network. Allowing it would endanger security of data & could also cause a virus outbreak.

Note

4.5. Backup Guidelines

4.5.1. Backup Schedule

Backup guidelines help to ensure compliance to UPG-IT standards & availability of data at all times.

The Grandfather-Father-Son (GFS) media rotation scheme is recommended to be followed with a full data backup taken on separate tapes on a daily, weekly, monthly and yearly basis, in order to ensure that a copy of the latest data is available at all times. The standard backup scheme is explained below which uses daily (Son), weekly (Father) & monthly (Grandfather) backup sets.


Daily Backups – Son: (Optional – Left to the discretion of the Senior Project Manager/Project Manager)

- Typically, individual backup media are labelled for each day of the week and full data backups are taken daily; for example, from the 1st

day of the week i.e.; Saturday to the day previous to the last working day of the week (possibly Wednesday in case of sites or Tuesday in the case of Corporate offices).

- At least one-week retention is maintained for the daily backup data & each tape is overwritten every week on the backup day. For example this week's Sunday tape would not be overwritten for 1 week, until the next Sunday.

Weekly Backups – Father: (Mandatory)


Doc No.

: EDA-04-29

Rev : 0

Date : 12 Mar 05


- Follow a similar scenario. A set of up to five weekly backup media is labelled "Week1", "Week 2", and so on.

- Full backups are recorded on a weekly basis, on the day that a "Son" media is not used. i.e. the weekly tape is used on the last working day of the week.

- The "Father" media is re-used on a monthly basis. Five weekly tapes are required in order to maintain @ least one-month retention of data, as some months have 5 weeks.

Monthly backups – Grandfather: (Mandatory)

- The final set of the three media is the monthly backup ones known as the Grandfather labelled "January", "February", and so on till December, according to which month of the year they would be used. Ideally, twelve tapes which correspond to the 12 months of the year are labelled. This "Grandfather" media records full data backups on the last business day of each month with a data retention period of @ least one year.

Yearly backups: (Optional – Left to the discretion of the Senior Project Manager/Project Manager)

- In addition to the “Grandfather” media set used above, a provision for 5 yearly backup tapes (or as per the business data retention policy) is recommended. The yearly backup tapes would be used for taking a full backup on the last working day of each year with a retention period of @ least 5 years (or as per the business retention policy). This tape would be archived for future restoration.

- If your backup plan follows a corporate fiscal calendar, then your monthly tape will take the place of the week 4 or week 5 weekly/Father tapes, depending on the month. If your backup schedule follows calendar months, then your monthly backup will vary throughout the year, replacing a daily or weekly tape. Typically, monthly tapes are overwritten yearly (recommended).

Project Backups: (Mandatory)

- A full backup of data is required upon completion of the project and forwarded to edara General Manager’s Office for safe keeping.

4.5.2. General Recommendations for Backup and Restore Site Administrator

Cleaning/Spare Tapes - To make a provision for a cleaning tape (for cleaning the backup drive) & 2 spare tapes (for contingency) should be made for any backup plan.

/IT-in Charge

Labelling - All backup tapes have to be clearly labelled, so as to allow recognition & documentation of the same.

Repetition - Sole backup must not be repeatedly used; i.e. the only copy of a backup should not be overwritten with a new backup - ideally use 5


Doc No.

: EDA-04-29

Rev : 0

Date : 12 Mar 05


tapes for daily backup, 5 for weekly, 12 for monthly, 5 for yearly, 2 for spare and 1 for cleaning.

Storage - Backups should be stored in secure areas that are accessible by authorized personnel only. All backup tapes to be stored in a fire resistant chub, as a safety measure. This recommendation is mandatory.

Restore/Catalogue - All backup tapes have to be tested for cataloguing/restoration at least once a month, in order to ensure successful restoration of the backed up data – this needs to be logged for records.

Off site storage - A copy of the latest data backup needs to be “off-sited” to a remote location ideally on a daily basis (or as per business standards). An off-siting log register has to be maintained & filed for records.

Transportation - During transportation to & from offsite storage locations, backup media should be adequately protected in fire resistant, shock resistant, water proof containers.

Backup Media - All site offices (that do not contain dedicated DAT/DLT/Ultrium backup drives) will use ZIP Drives (with reference to the current Technology standards) for executing backups on a regular basis. Ideally, the GFS system of backup would be followed but backup frequency decisions can be made by the business based on criticality.

Site Administrators/IT-in-charge/Backup Operators at site offices are responsible for the backup, restoration, storage & off-siting of data.

The Business/IT Support personnel should make sure that Site Administrators/IT-in-charge/Backup Operators at site offices follow standard Backup, Restore & Tape Off-Siting procedures.

4.5.3. Performing Backup and Restore Operations Site Administrator

All servers used by UPG-IT (whether at HO or sites) are either installed using Windows Server 2003 or Windows Server 2000 as the primary operating system – as per the current IT Technology standards.

/IT-in Charge

It is the job of the Site Administrator or IT-in-charge, who will be designated henceforth as Backup Operator, to execute backup & restore operations using the backup guidelines mentioned above.

The backup operator will be given a username & password for logging onto the server locally & executing the backup. In order to ensure logical security at all times, the backup operator shall strictly comply with the following rules.

Lock server console when not in use by pressing the Ctrl Alt Delete keys all at once & then clicking on Lock Computer.

Unlock workstations when required by pressing the Ctrl Alt Delete keys all at once & then key in the logon password.

The password should not be written down or passed on to anybody under


Doc No.

: EDA-04-29

Rev : 0

Date : 12 Mar 05


any circumstances. Do not write passwords on Post-It notes and stick them on tables, monitors, walls or anywhere else.

The password should be changed at least once every 30 days.

IT Support has to be updated of the passwords in use by the Backup Operator whenever it is changed.

Kindly refer to the Backup & Restore Manual for detailed procedures execution on Windows 2003 & Windows 2000 Server computers.

4.6. Physical and Logical Security Recommendations Site Administrator

The following recommendations have been prepared to help users to understand the importance of IT Assets. Confidentiality, Integrity & Availability of assets at all times is an important factor that helps users carry out their daily activities effectively.

/IT-in Charge

Visitors to the office should be escorted by the employee concerned & supervised at all times.

Lost or stolen IT assets should be reported to the Business in-charge immediately.

Dispose official company documents only by shredding.

Documents that are deemed sensitive must be subjected to controlled distribution. Each copy of the document must be numbered and that number must be recorded and signed for by the recipient.

Collect printed documents from network printers as soon as they are printed, especially for confidential documents.

Do not leave media such as CD’s/Floppies etc. unattended. Keep them locked away safely in a drawer.

Any media (soft or hard copy) should not be given to people outside the Group without appropriate management and originator authorization.

Lock workstations when not in use by pressing the Ctrl Alt Delete keys all at once (for Windows 2000 & Windows XP PC’s) & then clicking on Lock Computer.

Unlock workstations by pressing the Ctrl Alt Delete keys all at once (for Windows 2000 & Windows XP PC’s) & then key in the logon password.

Always save all data on the designated folder on the server & never on the desktop, my documents or any other folder on the local PC as the data backup would be setup only for the data on the centralised server.

If a workstation holds sensitive work-in-progress information, power-on and screen saver passwords can be used to restrict access to authorized users only. These passwords should be sent to IT Support Staff on a monthly basis (or as and when modified) for records.


Doc No.

: EDA-04-29

Rev : 0

Date : 12 Mar 05


Shutdown & switch off computers & monitors before leaving the office premises for the day.

Never use a dial up connection from a PC connected to the network. Network & dial up connections should never be used simultaneously. If a connection is required, disconnect the PC from the network prior to using dial-up or vice-versa.

Recommended Password Length: Minimum - 8 characters Maximum -14 characters.

Password must preferably have a special character like! @ # $ % & () Etc.

Password must preferably have alphanumeric characters.

Passwords are preferred not to have any personal identification details like users name, spouse’s name, children’s name and so on.

The password should be easy to remember but difficult to guess.

The password should not be written down or passed on to anyone else under any circumstances. Do not write passwords on Post-It notes and stick them on tables, monitors or walls.

4.7. Computer Usage – Health and Safety Recommendations

Health & Safety tips will help users get more comfortable when working with computers. If not followed, it can lead to health hazards such as muscle pain, tendon fractures (due to incorrect use of the keyboard), bad eyesight & the like. Following are a few tips to keep users relaxed but at the same time cautious.

Note

Health Tips

The head & the neck always have to upright when working.

The top of the monitor screen should be at or below eye level so it can be read without bending the head or neck.

Monitor screen distance should be such that you don’t have to read by moving your head back & forth.

Shoulders should be relaxed. Do not elevate your shoulders when typing or using the phone.

Forearms, wrists & hands should always be in one straight line. Use the armrests on the chair for supporting the forearms.

Thighs should have sufficient clearance space (enough to move around comfortably) between the chair & the computer table.

Feet should be placed flat on the floor & always rested.


Doc No.

: EDA-04-29

Rev : 0

Date : 12 Mar 05


Ensure that glare from lights & windows do not reflect on your screen, as this could cause damage to the eyes. Use a screen filter or window blinds to reduce glare.

Safety Tips

Ensure that there are no wires are hanging around or below your desk which could hamper movement or cause accidents.

Do not stack equipment on top of each other if storing in an open area. Use closed cabinets if required to avoid hazards.

Avoid bringing any liquids (like tea, water, etc) onto your desk, as spilling them might damage computer components or cause power short circuits.

Do not switch off the PC directly by switching off the mains power switch. Always shutdown from the operating system. Call IT Support for help, if in doubt.


5.1. Technical approval from UPG IT for all IT Purchases

5.2. Backups


Doc No.

: EDA-04-30

Rev : 1

Date : 16 Oct 05

CONSTRUCTION STAGE RECORDS Page : 1 of 2


1.1. To describe the controls needed for the identification, storage, protection, retrieval, retention time and disposition of records maintained by edara.

Note

1.2. This procedure shall apply to records generated during the construction stage including those pertaining to the defects liability period.

Note

1.3. The formats of file index and file labels described in this procedure are recommended samples only.

Note

2. DEFINITION

2.1. None Note


3.1. None

4. PROCEDURE Note

4.1. An up-to-date index of site records shall be maintained by the Site Secretary/ Document Controller. Refer Appendix EDA-04-30-A for the recommended format for the Index of Records.

Site Secretary / Doc Controller

4.2. All records shall be maintained in proper files and stored in a suitable environment to minimize the risk of deterioration and to prevent loss.


4.3. Each file shall be labelled as per the sample appended herewith (Appendix EDA-04-30-B). The label shall contain:

Project Name, Contract Name and Number, Description of the Contents of the File, File reference number (drawn from the Index of Records) and Volume Number.


4.4. Following completion of the Project, the records are archived at the Stores of Union Properties. This is done in co-ordination with the Human Resources Department of Union Properties.

Senior PM/ PM

4.5. Movement of records to and from the Archive Stores is controlled by an Archives Document Form (to be obtained from the HR Dept).

Note

4.6. ThThe records shall be neatly arranged in boxes provided by the HR Dept. and each box identified (by paint or permanent parker) with an unique identification number obtained from the HR Dept.


4.7. A List of Archived Files (format to be obtained from the HR Dept) shall be prepared for each box and pasted inside the box. A copy of the List of Archived Files shall be forwarded to the HR Dept and edara Head Office along with the keys and duly filled Archives Document Form.

Senior PM/ PM

4.8. Retrieval of records once archived is possible only with the approval of the Note


Doc No.

: EDA-04-30

Rev : 1

Date : 16 Oct 05

CONSTRUCTION STAGE RECORDS Page : 2 of 2

General Manager on the Archived Document Form.

4.9. The Site records shall be retained for a minimum period of 10 years from the completion of the Defects Liability Period of the project or until resolution of disputes if any (which ever is greater).

Note

4.10. Disposition of Site records will only occur with the approval of the General Manager.

Note


5.1. Index of Records (and the records referred therein)

5.2. Archives Document Forms & List of Archived Files.

construction stage procedures - rev 1

Documents

appendix eda

uae eda

rahim eda

wi eda

withdrawn rev

rev date page

rev x year

revision scheduledoc