Professional Documents
Culture Documents
1
1.1.1
Purpose
X-Y Time (Work-in-view) is the time when Gammon Skanska first gain knowledge of
a prospective project until the time of a more or less formal pricing exercise
Gammon Skanska has an opportunity to influence the Client and create a preferred
position. This may be done by convincing the Client to package the works in a
certain structure, assisting with financing solutions, design developments etc.
1.1.2
Timing
X-Y time may span years, especially when alternative finding arrangements are
being considered by the Client. It is the time before the Client selects the
procurement route for a project.
Frequency -
---
1.1.3
Participants:
1.1.4
Distribution:
---
1.1.5
Guidelines:
(1)
Jun-2004
(2)
The Bid Manager shall develop the pre-Bid Strategy and summarize in the
Preliminary Tender Summary (PTS), which should be regularly updated as to
reflect changes in information.
Sample of PTS
"1-1_App_Sample
of PTS.pdf"
Jun-2004
1.2
1.2.1
Purpose
To establish a smooth transition / continuity between tender and construction stages
in order to have an effective transfer of ownership of all project related information to
the project team.
1.2.2
Timing
To be held within one week after confirmation of contract award.
Frequency -
---
1.2.3
Participants:
1.2.4
Distribution:
1.2.5
Guidelines:
(1)
Appendix
Due to the importance to ensure the smooth transfer of costing data from
Causeway to ERP, it is recommended that when a tender has a high potential
for a contract award, the responsible Estimator shall liaise with the responsible
QS/PM to finalise the packaging before uploading the tender to the JDE taking
into account any post tender amendments.
Sample of Agenda
1-2_App_Agenda.
doc
Jun-2004
1.3
1.3.1
Purpose
After the contract award, the Contracts Director (CD) or Contracts Manager (CM) will
set up a project team to run the project. The purpose of this meeting is to brief the
project team on the scope of the project, the method of construction and particular
areas needing special concern/attention. The CD/CM with the presence of Bid
Manager will highlight the key issues and the details from the tender stage. Bid
Manager should assist the CD/CM mainly to explain the pricing strategy, commercial
and technical risks register in the tender and to provide information of updated
Client/Consultant Key person contacts to extend the customer relationship build up
during the X-Y Time.
1.3.2
Timing
This is the first project team meeting and is therefore called the Project Initiation
Meeting and should be held within 2 weeks after Contract Award. Other meetings
required to review issues related to the project shall be scheduled during Project
Initiation.
Frequency -
---
1.3.3
Participants:
1.3.4
Distribution:
All participants
1.3.5
Guidelines:
---
Appendix
Agenda
1-3_App_Agenda.
doc
Jun-2004
1.4
1.4.1
Purpose
The purpose of the meeting is to review the risk and opportunities register prepared
during tender with the site management team.
This register can also be used in open forum during partnering workshop as
obstacles & opportunities identification.
1.4.2
Timing
Within one month after the award of the contract
1.4.3
Frequency -
Participants:
1.4.4
Distribution:
1.4.5
Guidelines:
All participants
Client Representatives / Consultant Team subject to CM / PM
discretion
(1)
The process allow all the site management staff to have quick start-up in
familiarity with the nature and complexity of the job by exploring those risks
and opportunities and continue to monitor them via proposed mitigation
measures.
(2)
Regular updates are necessary during the construction period which promote
incorporation of newly identified risks / opportunities and the removal of
redundant items because of increased knowledge on the project details.
Appendix
1-4_App.pdf
Jun-2004
1.5
1.5.1
Partnering Workshop
Purpose
The purpose of the Partnering Workshop is find out what each contracted partner
wants to achieve from the project and the partnering, the hindrances and the
strengths each would bring to the project. It is then identifies how problems could be
overcome and agrees a range of strategies for effective partnering in the form of a
Pledge, which was documented in a Chater that was agreed and signed by all
contracted parties. By signing into the Chater, such partner committed to achieve all
aspects of the Pledge so as to deliver an excellent project and a successful outcome
for all parties.
1.5.2
Timing
1st Partnering Workshop - is to be arranged and conducted within two months after
contract award or at a period as determined by the CM with the Client
Mid Project Workshop - for job lasts more than a year
Final Review Workshop - at the end of the project
Frequency -
1.5.3
Participants:
1.5.4
Distribution:
1.5.5
Guidelines:
(1)
(2)
Jun-2004
(3)
Process
A Mid Project Workshop is also recommended for job lasts more than a year to
re-energise the partnership agreement and ensure new customers buy-in to
the partnering concept and address up coming issues.
The regular meeting is called Champions meeting. The Champions are
representatives from Key consultants and major contractors who meet to
examine the progress of the project in relationship with the common objectives
in pledge. Any shortfalls in performance monitoring matrix will be immediately
addressed and investigated so that continuous improvement can be
maintained
At the end of the project, a Final Review Workshop should be arranged to
review what was learnt, mange the knowledge created to take forward to future
projects, and celebrate the success of the project.
Appendix
1-5_App.pdf
Jun-2004
2.A.1
Master Programme
2.A.1.1 Purpose
The purpose of the Master Programme is to determine activity sequence, duration
and utilization of plant, materials and labour resources, statutory submissions and
inspections from project commencement until completion for use by the project team
in planning, managing and controlling the works. It shall address all known project
requirements in accordance with the contract (e.g. milestone dates, submissions,
handover dates, authority inspections, permit issues, etc.). Special care is necessary
in sequencing the statutory submissions and inspection dates and reference may be
made to Box 3.A.2, Statutory Submissions Checklist. The Master Programme is
used as the baseline for progress performance measurement and reporting.
2.A.1.2 Timing
The Rev. O Master Programme is required to be submitted in accordance with the
time period stated within the contract. The CM and PM are to lead the preparation
and submission of the Rev. O Master Programme, which is normally handled by an
Engineer.
Frequency -
2.A.1.3 Participants:
2.A.1.4 Distribution:
2.A.1.5 Guidelines:
---
Jun-2004
2.A.2
2.A.2.1 Purpose
The 3-Months Rolling Programme is used to breakdown the master Programme into
further detail as necessary and in a more convenient format for use by production
staff providing focused attention on the work ahead for the next 3 months. The
rolling programme may be used to highlight any programme slippage to those areas
/ activities that require special attention or deployment of additional resources. It
may also be used to show minor changes in sequence or advance work not
necessarily reflected on the Master Programme.
The 3-Months Rolling Programme may also be included into the Contractors Report
2.A.2.2 Timing
To be prepared in time for discussion during the 1st Monthly Site Progress Meeting. It
is to be reviewed and updated monthly to show the required activities to be
completed in the coming 3 months based on the progress achieved so far and the
milestones ahead.
Frequency -
2.A.2.3 Participants:
2.A.2.4 Distribution:
2.A.2.5 Guidelines:
---
Appendix
A-
2A2_App.pdf
Jun-2004
2.A.3
2.A.3.1 Purpose
The Bi-Weekly or Monthly Programme is used to closely plan and monitor site
progress, in particular plant and labour resources. It may also be used to highlight
any programme slippage and areas / activities that require detailed attention.
Other Short-term Programmes (e.g. Weekly Programme, Mobilisation Schedule,
Milestone Target Programme) may also be prepared as and when required as
decided by the Project Manager to suit the anticipated job control and site
management requirements.
2.A.3.2 Timing
The Bi-Weekly / Monthly or Short Term Programmes are to be prepared and issued
ahead of the work activities under consideration.
Frequency -
2.A.3.3 Participants:
2.A.3.4 Distribution:
2.A.3.5 Guidelines:
It is preferable to prepare some Short-Term programmes in Chinese to facilitate
better communication. In any event the latest programmes should be distributed to
discussed with affected Sub-contractors during meetings.
Appendix
ABC
"2A3_App A.pdf"
"2A3_App B.xls"
"2A3_App C.xls"
Jun-2004
Project :_________________________
Area :
Date :
Bi-Weekly Schedule
Description of Works
Prepared By :
Day
16
Distribution :
Reviewed By :
Endorsed By :
17
S/Cs :
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Description
WO No
Bill Element
Specification
Reference
Tender
Award
Issue Date
Return Date
Award Date
Issue Documents
Submission Date
Comment Date
Submission Date
Comment Date
Status
Approval Date
Order
RF Date
PO Date
Supplier /
Subcontractor
Delivery
Off/On Site
Fabrication
Required on Site
Page 1 of 2
Commence on Site
Page 2 of 2
2.B.1
2.B.1.1 Purpose
The External Procurement Schedule is prepared in conjunction with the tender
budget and Master Programme to ensure the timely appointment of suppliers and
subcontractors for the materials, equipment and services planned to be procured
from external sources for the project. The schedule is also used to indicate
submissions required for approval, the status of approvals received and ordering and
delivery. Appendix A provides a sample format for the schedule. This control tool is
particularly relevant in highlighting items with long lead-in times and in identifying and
tracking alternative proposal opportunities.
It is expected that sub-contractors supplying materials and equipment will prepare
and update their own schedules for checking and monitoring by the project team.
2.B.1.2 Timing
The External Procurement Schedule is to be prepared within 28 days after contract
award or as determined by the PM. Appendix C helps show how this activity fits into
the overall procurement process.
Frequency -
2.B.1.3 Participants:
2.B.1.4 Distribution:
2.B.1.5 Guidelines:
---
Appendix
AB-
Sample Form
Diagram of Subcontract Procurement: Overall Process
"2B1_App
A_Schedule Sample
"2B1_App B.pdf"
Jun-2004
2.B.2
2.B.2.1 Purpose
During Resource Requirement Planning (RRP), Internal Supply Schedules are
prepared in conjunction with the tender budget and contract programme. These
Internal Supplies refer to the resources planned to provided by internal Production
and Supply Services departments; Eg Plant & Equipment, Concrete Services & Steel
Fabrication. The schedules identify the duration for key items of plant & equipment
required as well as quantities of concrete and steel. The Schedules assist in both
resources and procurement planning as well as in monitoring progress.
2.B.2.2 Timing
The RRP Internal Supply Schedules are to be prepared and updated at the work in
view stage (depending on availability of tender information). At tender stage, the
Schedules are to be completed within 7 days of the tender closing. The frequency for
review after a contract award is given below.
Frequency -
2.B.2.3 Participants:
2.B.2.4 Distribution:
2.B.2.5 Guidelines:
The RRP is a data package in soft copy format. To access the RRP, open the Excel
master file from the following locations and follow the Instructions Worksheet to
generate the Schedules. Prior to tender handover to operations, the cost elements to
be incorporated in the Schedules are to be provided to Planning by Estimating.
Internal
Supplier
Location
Plant
Excel Master
File
Plant
Schedule.
Concrete
Schedule
Steel
Steel
Schedule
Appendix
Instruction
Worksheet
Procedure No.
1-30
1-12
Method 1, 1-9
Method 3, 1-10
1-11
Method, 1-9
---
Jun-2004
2.B.3
Manpower Schedule
2.B.3.1 Purpose
The Manpower Schedule is prepared to plan staff and direct labour requirements for
the project based on the tender budget and Master Programme.
The manpower schedule is also used for the comparison of tender budgets against
actual costs and for forecasting future requirements and expenditure. It can also be
used company wide to better utilize resources between projects.
2.B.3.2 Timing
The Manpower Schedule is to be prepared and issued internally within 14 days after
contract award and shall be regularly reviewed.
Frequency -
2.B.3.3 Participants:
2.B.3.4 Distribution:
2.B.3.5 Guidelines:
When reviewing the manpower requirements reference should be made to the
summary in the tender budget allowance for the project staff and direct labour
obtained from the Excel Tender Work-up Top Sheet and also viewed from the JDE.
Appendix
ABCDEF-
"2B3_App A.pdf"
"2B3_App D.pdf"
"2B3_App B.pdf"
"2B3_App C.pdf"
"2B3_App E.pdf"
"2B3_App F.pdf"
Jun-2004
2.B.4
2.B.4.1 Purpose
The Project budget is prepared to allocate the Contract Sum to the job specific
activities to be carried out inclusive of site, on costs, overheads and margin and
based on the tender allowances is spread on a monthly basis against the project
programme. The Project budget, which remains unchanged, is used for making
regular comparisons of actual against anticipated cost. The Project Forecast is
prepared to take into account the latest information in respect of financing and
planning for making regular comparisons of anticipated with actual performance.
2.B.4.2 Timing
The Project budget is prepared when the contract is awarded and includes tender
finalization adjustments, post tender negotiated omissions and additions if any.
The initial Project Forecast is the first forecast undertaken for that particular project
and is prepared in accordance with the forecast timetable.
Frequency -
The Project budget is prepared during JDE upload and fixed for
the duration of the project
Project Forecasts are carried out quarterly
2.B.4.3 Participants:
2.B.4.4 Distribution:
2.B.4.5 Guidelines:
The BQ is exported from Causeway and imported into the JDE. The Project
budget/Forecast is prepared in a fixed format under the JDE. A fully detailed
breakdown of individual resources at path GMD > Project Manager > Tender budget
> BQ budget. Initial Project forecast at path GMD > Project Manager > Project
Enquiries > Tender budget > Project Forecast Enquiry.
Appendix
---
Jun-2004
2.B.5
2.B.5.1 Purpose
Throughout the whole procurement process from invitation to tender, tender
interview, cost analysis and so on, numerous discussions are carried out by different
parties and a stock of information is generated that flows between the parties but
may not be well organized and presented for mutual understanding.
This finalisation occurs at the last stage of the process just before the formal award.
It is intended to review, finalise and agree the full and final scope of work and all
parties responsibilities related to each sub-contract to be placed. The PM, Site
Team, Procurement and Sub-contractor all need to be involved so as to minimize
any unexpected / disagreed events and/or missing items.
2.B.5.2 Timing
To be carried out before a decision is made on the award for each sub-contract.
Frequency -
2.B.5.3 Participants:
2.B.5.4 Distribution:
All Participants + CM
2.B.5.5 Guidelines:
---
Appendix
---
Jun-2004
2.B.6.1 Purpose
There is a commitment from EXCO/ Business Unit Directors not to take short cuts to
improve productivity, but there will be occasions on site when works will be required
to be undertaken on an urgent basis. This procedure to ensure that works requiring
urgent action are carried without compromising safety or quality.
2.B.6.2 Timing
Any time requiring to deal with urgent works, which include: i)
ii)
Frequency -
As required
2.B.6.3 Participants
2.B.6.4 Distribution
All Participants
2.B.6.5 Guidelines:
Any work of an emergency nature must be planned and controlled to the fullest
extent possible given the circumstances. The PM will be responsible for issuing
necessary instructions and assigning personnel, from existing site or other Gammon
resources. Close control and supervision by GCL staff is essential for all works of an
emergency nature.
Works that must be carried out in a shorter time frame than normal require a higher
degree of planning and control, not least to avoid the undesirable consequences of
short-cuts. Enhanced control and supervision and by GCL staff is again a
prerequisite.
Where works are being undertaken by sub-contractors, the procedure to be adopted
is as follows: 1)
In the first instance, always try to use existing subcontractors whose workers
have already been through our workers registration process and who have
previously been given site-specific inductions. Any additional workers
committed by the sub-contractors (or approved sub-sub-contractors) must
have valid Workers Registration cards and must be given site-specific
inductions.
Sep 2006
2)
3)
4)
Urgent works require the standard (or enhanced) risk assessment, method
statements and safety controls, which are to be reviewed by the site safety
advisor, prior to commencing the works.
5)
All urgent works must be subject to close GCL supervision to ensure full
compliance with applicable safety and technical procedures.
Appendices
---
Sep 2006
2.C.1
2.C.1.3 Participants:
2.C.1.4 Distribution:
2.C.1.5 Guidelines:
A Code of Practice for a revised approach is currently under preparation by the
HKSAR Government whereby it is planned to combine both plans into a unified
Integrated Supervision Plan System. The requirements under this Section is
therefore likely to change and should be checked before implementation.
Appendix
"2C1_App IA.pdf"
IA
I
II
III
IV
V
VI
"2C1_App I.pdf"
"2C1_App IV.pdf"
"2C1_App II.pdf"
"2C1_App V.pdf"
"2C1_App III.pdf"
"2C1_App VI.pdf"
Jun-2004
2.C.2
Safety Plan
2.C.2.1 Purpose
A Safety Plan is prepared to set out the safety and health risk management system
for the project. The plan identifies the health and safety rules and regulations
applicable and defines how it is intended to manage, control and coordinate the
operations in order to protect the health and safety of all persons engaged on the
project as well as the public who may be affected. The need for and content of
safety plans also aims to satisfy the F&IU (Safety Management) Regulations as well
as OHSAS 18001 requirements.
2.C.2.2 Timing
The Safety Plan is to be prepared and submitted in accordance with the contract,
regulatory and HSE system requirements.
Frequency -
2.C.2.3 Participants:
2.C.2.4 Distribution:
2.C.2.5 Guidelines:
Further details on health and safety planning matters can be found under the HSE
Management System including Operational Control Procedures. For development of
project specific Safety Plans reference shall be made with the project Safety Officer /
HS&E Engineer or HSE Department for assistance.
Appendix
"2C2_App Project
Safety Plan Sample
Jun-2004
2.C.3
2.C.3.1 Purpose
The purpose of preparing and implementing an Environmental Management Plan (or
Project Environmental Plan) is to assist the project team to comply with all relevant
legislation, contract requirements and the companies HSE Management System,
HSE Policy and Environmental Objectives. To achieve this goal the plan typically
sets out the responsibilities for environmental matters and includes sections
describing environmental monitoring, promotion, internal and external
communication. The plan also identifies potential environmental impacts and
mitigation plans, contingency plans and applicable Operational Control Procedures.
2.C.3.2 Timing
The Environmental Management Plan is to be prepared within 28 days and
submitted in accordance with the contract requirements.
Frequency -
2.C.3.3 Participants:
2.C.3.4 Distribution:
2.C.3.5 Guidelines:
(1)
(2)
Appendix
"2C3_App Project
Environmental Plan
Jun-2004
2.C.4
2.C.4.1 Purpose
The Waste Management Plan aims to describe the arrangements for avoidance,
reuse, recovery and recycling, storage, collection and handling different categories
of waste in order to minimize the overall waste generated on site and to ensure its
proper treatment and disposal. It also aims to comply with any contractual
requirements, the company HSE Policy, HSE management system and
environmental objectives.
2.C.4.2 Timing
The Waste Management Plan is to be prepared and submitted within 21 days after
contract award or in accordance with the contract requirements.
Frequency -
2.C.4.3 Participants:
2.C.4.4 Distribution:
2.C.4.5 Guidelines:
(1)
Reference should be made to ETWB Technical Circular 15/2003 and any later
controls for issues governing construction and demolition waste for public
works.
(2)
Appendix
"2C4_App Waste
Management Plan S
Jun-2004
2.C.5
2.C.5.1 Purpose
The Traffic Management Plan shall be prepared to outline the arrangements for
temporary traffic measures (TTM) when necessary to accommodate the project
construction works. TTM are required to enable the road diversions and closures to
be implemented in accordance with the governing rules and regulations before the
relevant works commence.
2.C.5.2 Timing
A Traffic Management Plan is to be prepared within 28 days after contract award or
as determined by PM to allow sufficient time to process the necessary authority
applications for approval before commencing the works.
Frequency -
2.C.5.3 Participants:
2.C.5.4 Distribution:
Representatives
Necessary
2.C.5.5 Guidelines:
(1)
In most geographic areas, the TTM works are generally subject to comment
and approval by both the TD and the HKPF before review, comment and
approval by HyD.
(2)
For projects where significant impact may occur due to the TTM works,
additional approval routes including Working Groups, Traffic Management
Liaison and Site Groups and consultations with external parties may also be
required.
Appendix
---
Jun-2004
2.C.6
Security Plan
2.C.6.1 Purpose
The purpose of the Security Plan is to manage, control and co-ordinate the works in
order to protect persons engaged on the project. Its implementation shall minimize
loss incurred in the project and also prevent the entry / presence of illegal workers
on site.
The Security Plan is applicable to all activities carried out by Gammon Skanska
Limited including all the activities carried out by subcontractors.
The Project Manager is to determine and adjust parts of the guidelines and formats
of the Security Plan to suit the respective job requirements and nature. e.g. Building,
Civil and Foundation work.
2.C.6.2 Timing
The Security Plan is to be prepared within 28 days after contract award or as
determined by the PM.
Frequency -
2.C.6.3 Participants:
2.C.6.4 Distribution:
2.C.6.5 Guidelines:
(1)
Appendix
Note: this is optional and is subject to the individual contract requirement and
Clients requirement.
A - Sample Site Security Plan
"2C6_App
Security Plan Samp
Jun-2004
2.D.1
2.D.1.1 Purpose
The Project Quality Plan (PQP) is used to identify the planned resources necessary
for delivery of the project, the allocation of the responsibilities, the project quality
objectives, and processes and method statements to be established, the applicable
procedures, the Inspection and Test Plans (ITPs) to be prepared and records
generated.
2.D.1.2 Timing
The PQP is to be prepared, reviewed and approved internally within 28 days of
contract commencement.
The ITPs should be prepared 1-2 months ahead of work commencement or as
required for submission under the contract. For early start activities the plans and
associated checklists would need to be established sooner.
Frequency -
2.D.1.3 Participants:
2.D.1.4 Distribution:
2.D.1.5 Guidelines:
(1)
(2)
(3)
Appendix
"2D1_App
A_Q-Policy.pdf"
"2D1_App B PQP
Cover.doc"
"2D1_App B
PQP.doc"
Jun-2004
2.D.2
2.D.2.1 Purpose
The review, approval and implementation of a Survey Quality Plan aims to help
ensure that the required dimensional controls are achieved. The plan systematically
identifies the planned resources, the procedures or methods to be adopted and the
controls to be applied to the setting out and related survey activities. The plan also
identifies the drawings and records to be established in the process.
2.D.2.2 Timing
The Survey Quality Plan should be produced by the responsible Senior Surveyor /
Site Surveyor as soon as practicable after site handover with initial record drawings
prepared and distributed to the relevant parties within 7 days after site handover.
Frequency -
2.D.2.3 Participants:
2.D.2.4 Distribution:
2.D.2.5 Guidelines:
Survey drawings, plans and records shall clearly record all necessary survey data
and information. Any deviations in dimensions, levels, design layouts or aspects are
recorded and the Architect / Engineer notified for clarification before proceeding with
the works. The initial record drawings shall include;
a)
b)
c)
d)
e)
f)
g)
Appendix
"2D2_App A.pdf"
"2D2_App B.pdf"
Jun-2004
2.D.3
2.D.3.1 Purpose
The Design / Temporary Works Submission Schedule is a management tool for
planning, monitoring and controlling the design submission and approval processes.
This is achieved by scheduling the dates by which each detailed design package
must be prepared and issued to enable works to proceed in accordance with the
Master Programme and monitoring submission and approval status.
2.D.3.2 Timing
The Design / Temporary Works Submission Schedule is to be prepared within 7 days
after contract award or at a period determined by the PM.
Frequency -
2.D.3.3 Participants:
2.D.3.4 Distribution:
2.D.3.5 Guidelines:
(1)
(2)
(3)
Appendix
Sample of Schedule
"2D3_App_Submis
sion Sample (Queen
Jun-2004
{Project Name}
CUT-OFF DATES SCHEDULE FOR INFORMATION RELEASE (PROVISIONAL
Ref.
No.
Type of Information
PROVISIONAL SUMS
Latest Issue of
Info for
Coordination &
Construction
Actual Issue
Date
Submission &
Initial
Coordination Approval of
Subletting/
Shop Dwg's /
After
Sourcing Period
Samples
Subleting
Material
Fabrication/ Planned Start
Date On Site
Delivery &
Mobilization
Remarks
2.D.4
2.D.4.1 Purpose
The purpose of the Design Information Release Schedule is to indicate the latest
date required for issue of information by the Architect / Consultant to ensure
construction works, including production of any shop drawings and material
procurement activities, are progressed in accordance with the Master Programme.
Requests for Information are raised to expand or clarify existing design information.
The status of these requests may be added to the above schedule or catalogued
separately for tracking responses as decided by the PM.
2.D.4.2 Timing
The Design Information Release Schedule is to be prepared and issued to the
Architect / Consultant within 28 days after contract award or at a period determined
by the PM. Requests for Information are issued when necessary following drawing
reviews or at another times ahead of construction works.
Frequency -
2.D.4.3 Participants:
2.D.4.4 Distribution:
2.D.4.5 Guidelines:
(1)
(2)
Appendix
"2D4_App A.pdf"
"2D4_App B.pdf"
Jun-2004
3.A.1
Site Diary
3.A.1.1 Purpose
A site dairy is to be completed to note the actual activities, quantities and types of
different plant and labour resources and any issues affecting the site works. This
information is necessary in order to ensure that an accurate and complete history of
resources and events is available on record. The information is essential for proper
verification and collation of daily progress reports, providing information on
productivity and wastage, and for future reference in correctly interpreting actual site
situations when assessing the sequence of past events that have influenced the
project outcome.
3.A.1.2 Timing
To take these records throughout the whole project period
Frequency -
Daily
3.A.1.3 Participants:
3.A.1.4 Distribution:
3.A.1.5 Guidelines:
(1)
(2)
(3)
(4)
Appendix
Project manager shall establish a project specific cost code system among the
project quantity surveyor, the site agent / superintendent and the cost clerk.
The cost code system shall be able to reflect the budget and costs for each
construction element in the ERP.
Capture and verify the actual resource expenditures by foreman/TA.
Record any events other than scheduled in the Site Dairies by the foreman/TA.
Combine all foremens site diaries to form the Site Diary for submission to the
Client/Engineer.
Sample of Daily Record
3A1_App.pdf
Jun-2004
3.A.2
3.A.2.1 Purpose
The Statutory Submissions Checklist summarises the statutory applications,
notifications, registrations, submissions, reports, certificates, permits and approvals
required by the HKSAR Government Departments before undertaking and during the
execution of typical works carried out by the company in Hong Kong. Use of the
checklist helps ensure that the company discharges all its obligations within the
prescribed timeframes.
3.A.2.2 Timing
Reference to the Statutory Submissions Checklist is to be made at contract
commencement, during project mobilisation and initiation and then regularly during
project execution and upon completion.
Frequency -
3.A.2.3 Participants:
3.A.2.4 Distribution:
All Participants + CM
3.A.2.5 Guidelines:
---
Appendix
3A2_App.pdf
Jun-2004
3.B.1.
3.B.1.1 Purpose
Starting from the time of award the purpose is to establish an effective working
relationship between Gammon Skanska as the main contractor and/or employer, and
the sub-contractor. This is achieved by setting out, explaining and ensuring a clear
understanding of all the rules and procedures laid down for the proper execution of
the subcontract work package within the whole project.
3.B.1.2 Timing
To be held within one week after confirmation of a subcontract award.
Frequency -
---
3.B.1.3 Participants:
3.B.1.4 Distribution:
All participants
3.B.1.5 Guidelines:
---
Appendix
Agenda
"3B1-App_Subcon
tractor Initiation Me
Jun-2004
3.B.2
3.B.2.1 Purpose
Most of our projects will receive variation orders (V.O.) issued by the
Engineer/Client. These V.O.s are resulted from changes to the original Scope of
Works specified in the Contract. More than often, changes have not been recorded
or logged properly. In order to reduce the possible loses arising from recording
changes, a systematic approach is required to screen all possible areas that may
generate V.O.s
3.B.2.2 Timing
To conduct weekly review on the request for Information, Instruction from
Engineer/Client, Confirmation of verbal instruction and the relevant responses as
well as any observed changes during site walks.
Frequency -
Weekly review
3.B.2.3 Participants:
3.B.2.4 Distribution:
---
3.B.2.5 Guidelines:
(1)
To properly register not only the date of issue but also the date of response of
the prime sources of V.O.s (e.g. Request for Information, Instruction issued
by the Engineer/Client, CVL, etc).
(2)
The site team shall conduct regular reviews of these documents and the
associated responses to ensure notification to the Engineer/Client are issued
in the manner stated in the Contract.
(3)
During weekly site walk carried out by the site team, any changes to the scope
of works shall be observed, discussed and recorded.
(4)
Any impact on the programme or budget shall be verified by the PM who will
then notify the Engineer/Client of these impact and any possible claims.
Appendix
---
Jun-2004
Appendix A
Instruction to Sub-contractor
Ref. No. :
Date :
Project :
Job No. :
Sub-contractor :
Trade :
Contents
e. Labour requirement :
Acknowledged By
_______________________
Project Manager
___________________________
Sub-contractor's Representative
3.B.3
3.B.3.1 Purpose
To provide controls to prevent labour being taken on or deployed without prior
agreement and to issue instructions to sub-contractors in a standard format, any
variation to the scope of sub-contracts shall be covered with Instruction to Subcontractor.
3.B.3.2 Timing
To be carried out throughout the whole project period
Frequency -
3.B.3.3 Participants:
3.B.3.4 Distribution:
CM + PM / PQS + filing
3.B.3.5 Guidelines:
(1)
In the cases that any additional work to the sub-contractors is identified, the
relevant staff, the Foreman, the Site Agent/Superintendent or the site engineer
shall complete a draft Instruction to Sub-contractor for the Project Managers
approval.
(2)
(3)
Appendix
A - Instruction to Sub-contractor
"3B3_App A.xls"
Jun-2004
3.B.4
3.B.4.1 Purpose
To control the additional expenditure incurred in undertaking overtime work through
a process of review against limits established and through higher level authorisation
of cases exceeding allowances made. This is also intended to help ensure that
overtime is carried out on essential works only and during working hours permitted
under law.
3.B.4.2 Timing
Project managers shall review the O.T. expenditures from the ERP everyday.
However the specific controls described herein are applicable every 2 weeks prior to
approval of the Worker Time Entry.
Frequency -
Daily
3.B.4.3 Participants:
3.B.4.4 Distribution:
3.B.4.5 Guidelines:
(1)
Project manager shall establish a suitable cost code system among the
project quantity surveyor, the site agent / superintendent and the cost clerk.
The cost code system shall be able to reflect the budget of labour costs for
each construction element in the ERP.
ii. In the cases of O.T. expenditure approaches the project managers predetermined limits, he shall re-visit his planning of project execution and
setup means to reduce / avoid any further O.T. working.
Appendix
---
Jun-2004
Project Name :
Block :
Floor:
Location
QS
On-Site
Measurement per
floor
Piece per
Package
Approved
Quantity per
floor to be
Appendix C
No :
Date :
Project Name :
Name of Sub-Contractor :
Requisition Form for Material
Description
Item
Location
Remarks :
Signed by
Sub-Contractor's
Representative
Signed by
GCL Site Storekeeper
Signed by
GCL Foreman
:
unit
Quantity
Appendix D
Project Name :
Sub-contractor's Material Distribution Schedule
Floor
Location
Size
10
11
12
13
14
15
16
17
18
19
20 TR UR
Total No.
Quantity
of Floor to be
per floor
Distributed
Unit
3.B.5
3.B.5.1 Purpose
All materials need to be controlled to minimise wastage and therefore costs.
Concrete and reinforcement consumption needs to be monitored continuously to
ensure meeting targets. Long lead in materials need tighter controls to help avoid
delays to ordering, material shortages, material distribution errors, uncontrolled
wastage or take off errors. Whilst Section 2.C.4 covers waste management in
general, a consistent approach for tracking and control of finishing materials
purchased and commonly distributed to subcontractors is shown on the flow chart
attached as App A and has been defined under a Material Management Control
System as summarized under 3.B.5.5.
3.B.5.2 Timing
To be carried out throughout the whole project period.
Frequency -
As required
3.B.5.3 Participants:
3.B.5.4 Distribution:
3.B.5.5 Guidelines:
(1)
Before ordering
Ordering
After approval, BQ quantities are reassessed based on the selected and approved
materials/samples and the latest drawings, finishing door/ironmongery/sanitary ware
schedules, tile pattern details and other relevant information. A wastage allowance
for ordering is agreed which would not normally exceed the tender provision, a
delivery schedule is worked out and any special packaging and handling
requirement considered before processing the order.
A Finishing Material
Schedule (see App B) is prepared according to the measured material quantities for
each floor.
Jun-2004
(3)
All approved samples are to be kept securely and labeled with the submission serial
number. All materials on site should be stored in a designated area suitably
protected and with access control. Offloading and handling is to be supervised and
storage conditions maintained properly. Material distribution is controlled and
recorded as Sub-Contractors need to complete a Requisition Form for Material
(see App C) for endorsement before the Storekeeper releases materials and records
details into a Sub-contractors Material Distribution Schedule (see App D).
(4)
A
B
B2
C
D
"3B5_App A.pdf"
"3B5_App B.pdf"
"3B5_App C.xls"
"3B5_App B2.xls"
"3B5_App D.xls"
Jun-2004
3.C.1
3.C.1.1 Purpose
The intent of operating a Safe Working Cycle regime on site is to enhance the safety
awareness, measures, systems and culture of all those engaged on the project in
order to improve the working environment and safety performance.
3.C.1.2 Timing
The Safety Working Cycle can be a combination of daily, weekly and monthly
routines.
Frequency -
3.C.1.3 Participants:
3.C.1.4 Distribution:
---
3.C.1.5 Guidelines:
(1)
(2)
(3)
PM shall direct the workers / personnel to recruitment centre for receiving the
formal safety induction training so as to cater for the forthcoming legislation on
workers registration and safety management policy.
Appendix
3C1_App.pdf
Jun-2004
3.C.2
3.C.2.1 Purpose
To minimise employees compensation claims arising from injuries by keeping close
track of the details, investigating selected claims and by introducing actions to
eliminate the cause of actual and potential risks
3.C.2.2 Timing
Frequency
As required
3.C.2.3 Participants:
3.C.2.4 Distribution:
---
3.C.2.5 Guidelines:
(1)
Methods
Follow the Workers Injury Risk Management (WIRM) Procedures to control the
amount of injury claims. This is by ensuring that any of our employees /subcontractors employees that do sustain a work related injury receive high level medical
treatment and management of their injury at the earliest possible time in order to assist
them to return to work at the earliest opportunity.
(2)
Project Management Controls (Refer also Box 5.C.1 Monthly HS&E Report)
The PM will receive a monthly report providing details of each injury to individuals
having site accidents during the preceding month and days of sick leave abstracted
from the sick leave certificate. HS&E will also provide an updated summary table of
the total EC Claims arising on each job including the individuals names and
subcontractors involved and the number of sick leave days against each registered
claim. PMs should enter the JDE system for details of accidents in the HS&E Module
under HS&E \ HS&E Reports \ Accident Summary. It should be noted that costs arising
from any accident claims will be charged to the relevant project.
Use the information provided to control further accidents by discussing each case
during safety meetings, determining likely causes of accidents arising and working out
actions to be taken to avoid recurrence of similar events. Also review sick leave claims
that appear exceptionally long based on the nature of the reported injury. Any
suspicious cases shall be highlighted to the HS&E Department for referring to the
insurance company for investigation and / or further action.
Appendix
---
Jun-2004
3.C.3
3.C.3.1 Purpose
To establish an effective system for refuse collection and disposal thus ensuring
good housekeeping and hygiene, health and safety. Effective control also includes
keeping track on costs and where possible to reduce the volumes of refuse arising
by good planning and by adopting recycling where practicable.
3.C.3.2 Timing
To be carried out throughout the whole project period
Frequency -
---
3.C.3.3 Participants:
3.C.3.4 Distribution:
---
3.C.3.5 Guidelines:
(1)
Methods
The PM shall identify appropriate Refuse Disposal Control measures prior to project
commencement and shall also periodically review the effectiveness of the measures
set and provide for continuous improvement. Details of specific controls are normally
incorporated into the Environmental or Waste Management Plans described under
Boxes 2.C.3 and 2.C.4 respectively.
(2)
a)
b)
c)
d)
e)
f)
g)
h)
i)
Appendix
---
Jun-2004
3.C.4
Anti-II Control
3.C.4.1 Purpose
The employment of an illegal immigrant/worker by GSL and all GSL appointed subcontractors including sub-sub-contractors of all tiers for the purpose of any contract
works in conjunction to the project is strictly prohibited. Anti-II checking is carried to
minimise the risks of illegal immigrants from working and trespassing on our sites
and to ensure compliance with the law.
3.C.4.2 Timing
To be carried out throughout the whole project period
Frequency -
As shown in guidelines
3.C.4.3 Participants:
3.C.4.4 Distribution:
---
3.C.4.5 Guidelines:
Various actions are recommended and details will be included within the applicable
Security Plan. The following checking methods are typical. In all cases, records shall
be maintained to demonstrate that we are executing strict controls and monitoring
compliance.
a)
b)
c)
Surprise Check
Carried out monthly by the Site Management such as Site Agent / Foreman at
random. Records of personnel checked have to be kept.
Jun-2004
d)
e)
Sub-Contractors Responsibilities
The Project Manager shall take measures to ensure that all Sub-contractors
verify that their employees and any visitors, including their suppliers, are under
legitimate employment and abide by site access and Working Pass requirements.
f)
Appendix
A-
"3C4_App A.doc"
Illegal Labour
IS NOT ALLOWED
Jun-2004
3.D.1
Quality Control
3.D.1.1 Purpose
To establish a system whereby the quality of materials, equipment and works carried
out is defined and standards are monitored and controlled to ensure all requirements
are met consistently from project commencement to completion of the maintenance
period. The system of control shall be based on the Quality Management System, as
summarised under the guidelines below, contract requirements and if applicable, the
Detailed Site Safety Supervision Plan and Quality Supervision Plan.
3.D.1.2 Timing
To be carried out throughout the whole project period
Frequency -
Daily
3.D.1.3 Participants:
3.D.1.4 Distribution:
---
3.D.1.5 Guidelines:
(1)
Planning
Jun-2004
(3)
There are many other opportunities for project team members or other staffs to
identify actions to improve quality on site which may arise during site walks, visits or
audits. Subcontractors should also be involved with inspections of works and
completion of checklists. In such cases checks will be conducted according to an
agreed ITP. It is still necessary however to establish that the subcontractor is
carrying out this role effectively and to maintain a degree of scrutiny to ensure
consistent implementation.
(5)
Defects and issues identified during inspection & testing and other visits including
those from the Client are identified and immediately resolved on the spot or brought
to the attention of project management for review and resolution. Corrective actions
shall be initiated for those cases where we can identify opportunities to avoid
repeating the problem. Non-conformance Reports shall be used to record the
causes, approvals, actions taken and costs involved.
Follow-up rectification measures shall be planned and if necessary approvals
obtained before remedial work is undertaken. Such works shall be closely
supervised and check off to ensure compliance with agreed repair methods.
(6)
The levels of control shall be under constant review to ensure they are suitable and
effectively achieving the desired results with the resources available.
(7)
Further Reference
QMS Manual and Procedures, PQP, ITPs, specifications, DSSP and Quality
Supervision Plans (if any).
Appendix
---
Jun-2004
3.D.2
3.D.2.1 Purpose
a)
b)
c)
d)
e)
3.D.2.2 Timing
As shown in the Guidelines below
Frequency -
3.D.2.3 Participants:
3.D.2.4 Distribution:
---
3.D.2.5 Guidelines:
(1)
All setting out dimensions either on drawings or set out on site should be
checked in one way or another to ensure there are no discrepancies or
conflicts with the original design and to minimise as much as possible both
human error, design errors, instrument errors and inaccuracies arising from
setting out methods and environmental conditions prevalent at the time of
setting out.
(2)
(3)
For each surveying session, additional control points shall be incorporated for
verification of the fieldwork. In addition, a copy of the surveyors fieldwork data
shall be maintained for quality checking purposes. Chief / Senior surveyors
shall from time to time perform routine checking of the surveyors fieldwork
data to ensure the quality of the surveying work.
(4) Methods
a) The main reference points should be checked from government stations at
Site Handover Stage or as soon as practicable after commencement. Any
deviations must be verified and clarified immediately.
Jun-2004
Appendix
---
Jun-2004
3.D.3
3.D.3.1 Purpose
Project Managers shall ensure their project teams adopt a systematic method of
drawing registration and status tracking so as to allow effective and efficient
registration, distribution, management and reporting on all drawings received and
issued including part-copies. The same principles apply to other project documents.
3.D.3.2 Timing
During the tender stage or at project commencement, PM shall determine which
system is to be adopted for the project. If the Drawing Registration and Tracking
System is selected, he shall make arrangements with IT for installation of relevant
software and for subsequent operator training. Alternative arrangements will be
necessary for other options.
Frequency -
Regularly
3.D.3.3 Participants:
3.D.3.4 Distribution:
---
3.D.3.5 Guidelines:
(1)
Appendix
Methods
(a)
(b)
"3D3_App A.pdf"
"3D3_App B
(Drawings 1 & 2).xl
Jun-2004
3.D.4
3.D.4.1 Purpose
In order to better control the quality of shop drawings produced by subcontractors, a
systematic method of checking their content and providing feedback should be
introduced to ensure drawing standards are consistent and meet requirements so as
to improve the chances of approval when making submissions. Shop drawings that
consider the process and go beyond copying consultants details, may also reduce
errors and delays from arising during fabrication and installation thereby improving
output and product quality.
3.D.4.2 Timing
Checklists should be completed when drawings are first reviewed and any comments
should be incorporated before submission for consultant approval.
Frequency -
Regularly
3.D.4.3 Participants:
3.D.4.4 Distribution:
---
3.D.4.5 Guidelines:
(1)
Method
(a)
(2)
The degree of detail and checking will depend on the nature, complexity and
importance of the work involved.
Jun-2004
Appendix
"3D4_App - SD01
Checklist for P&D, F
"3D4_App - SD04
Checklists for Fire R
"3D4_App - SD07
Checklist for Curtain
"3D4_App - SD02
Checklists for Metal
"3D4_App - SD05
Checklist for Structu
"3D4_App - SD08
Checklist for Carpen
"3D4_App - SD03
Checklists for Windo
"3D4_App - SD06
Checklist for Formw
"3D4_App - SD09
Checklist for Metal R
Jun-2004
4.A.1
4.A.1.1 Purpose
This meeting is to review the status of different factors affecting the project
throughout the contract life to help maintain good communications within the site
team and ensure timely decisions on actions and priorities. Prior to the meeting
monitoring data is collected or updated by responsible team members in order to
accurately report the current situation in the areas of safety and environment, quality,
progress, technical areas, procurement, commercial matters and other relevant
factors.
During the review issues of concern will be discussed to determine the best course
of action and team members will be assigned actions to take as necessary to
correct, prevent, control or improve deviations or potential problems envisaged. The
project team use the meeting to look ahead at future works and issues in order to
make preparations to ensure efficient and effective management control. A copy of
the suggested Agenda of the meeting is enclosed.
4.A.1.2 Timing
This meeting is set up in order to best cope with the changing nature of the work and
management issues affecting the project.
Frequency -
To be determined by PM
4.A.1.3 Participants:
4.A.1.4 Distribution:
All participants
4.A.1.5 Guidelines:
---
Appendix
Agenda
"4A1_App_Agend
a (Site Mgt Meeting
Jun-2004
4.A.2
4.A.2.1 Purpose
These meetings are convened before reaching key project milestones to provide a
forum for focused attention on all relevant issues associated with achieving the
milestone. The reviews are intended to enhance communication amongst personnel
in-charge, Employer, Engineer & Architect when necessary, sub-contractors and
operatives to smooth out any conflicts and misunderstandings. Discussions will
center around the detailed scope of works of each trade, the identification of work
interfaces, the setting up of coordination links, the review of applicable procedures,
the need for milestones amendment, the detailed programme of work, consideration
of commercial issues that may influence the outcome, or further items deemed
relevant or arising from other reviews.
4.A.2.2 Timing
Meetings will be held before commencement of each phase of works.
Frequency -
by stage
4.A.2.3 Participants:
4.A.2.4 Distribution:
All participants
4.A.2.5 Guidelines:
(1)
The Project Manager will take the leading role during these meetings to
coordinate all parties involved in the interfacing work between phases and in
making decisions.
Works will be sequenced according to the latest
programme however adjustments, and fine-tuning may be necessary to
overcome unavoidable situations. Guidelines for each review are provide
under the Appendix.
Jun-2004
Appendix
"4A2_App 1.doc"
"4A2_App 2.doc"
"4A2_App 4.doc"
"4A2_App 5.doc"
"4A2_App 3.doc"
"4A2_App 6.doc"
"4A2_App 7.doc"
Complete 1
trade before next
trade starts
Jun-2004
Appendix B
QS SITE WALK
TOPICS NOTED
POSSIBLE EXTENSION OF TIME ENTITLEMENTS
RESPONSIBLE
PERSON
____________________
Description
Period of Delay
Reason for Delay (Consider planned / actual sequence)
Effect (Time)
Effect Cost
Records to be kept (What Records / By Whom)
Further Information to be obtained / Checked (What Information? / By Whom)
Description
Records to be kept (What Records / By Whom)
Further Information to be Obtained / Checked (What Information / By Whom)
Any Other Reasons to Approach Possible Claim
_______________
Description of Item Identified
Proposal for Saving
Implementation / Follow Up Action
Contract Title:
Contract No:
Date:
Names
QS
Operations
Other Information
4.B.1
4.B.1.1 Purpose
To review all commercial matters related to the project, including programme,
NODs, EOTs, claims, potential delays, resources, site walk issues, risks and
opportunities, budget forecast, outstanding information, V.O.s and costs associated
with defects.
4.B.1.2 Timing
To be held after contract commencement (to be determined by PM)
Frequency -
4.B.1.3 Participants:
4.B.1.4 Distribution:
---
4.B.1.5 Guidelines:
---
Appendix
"4B1_App
A_Agenda (Monthly
"4B1_App B QS
Site Walk.doc"
"4B1_App C.xls"
Jun-2004
4.B.2
Sub-contractor Meeting
4.B.2.1 Purpose
To maintain a regular dialogue between project team and subcontractors on all
project related matters including site safety & environmental issues, quality matters,
interfaces and coordination, work mobilisation and site progress, commercial issues
and other areas deemed necessary.
4.B.2.2 Timing
To be held after the Subcontractor Initiation Meeting
Frequency -
4.B.2.3 Participants:
4.B.2.4 Distribution:
---
4.B.2.5 Guidelines:
---
Appendix
Agenda
"4B2_App_Agend
a (SC Meeting) .doc
Jun-2004
Appendix C
Poor
Fair
Average
Good
1.2
3.4
5.6
7.8
9.10
Excellent
Some specified
requirements not
achieved without
significant rework or
acceptance of
waivers/deviations
Generally meets
specified requirements.
Any waivers/deviations
acceptable to
Contractor.
Meets specified
requirements. No
Waivers/deviations
Meets specified
requirements. Has
capability to exceed
requirements, if required
Contractor intervention
Non-compliances
detected by own system
and repair/rework
effectively addressed.
No consideration of
improvement process.
Proactive in identifying
implementing
and implementing
improvements, with
improvements, without
Contractor input
Contractor input
Achieved agreed
delivery dates with
limited Contractor
intervention
Completed on schedule
without Contractor
intervention
Pro-active in
demonstrating excellent
planning & delivery
control. No intervention
necessary by the
Contractor.
Slow to respond to
enquiries and
clarifications
necessitating
occasional Contractor
intervention to expedite
activities
Documentation (e.g.
shipping advice,
delivery schedules)
produced with some
prompting. Problems
with clarity /applicability.
Meets specified
requirements. Has
capability to exceed
requirements, if required.
Limited commitment by
management to
develop and promote a
safety culture
throughout the
organization
Management shows
commitment to develop
and promote a safety
culture but needs
guidance.
Minimum input to
comply with main
contractor's basic
requirements
1 Product Quality
Consistently unable to
comply with specified
requirement
occasionally required to
identify and resolve
deficiencies not
detected internally.
3 Co-operation /Attitude
Poor response to
enquiries and
clarifications, frequent
intervention needed by
Contractor.
4 Delivery logistics
Documentation (e.g.
shipping advice,
delivery schedules not
usually provided, even
after repeated requests.
5 HS&E Issues
Obvious lack of
commitment from
management for
developing and
promoting a safety
culture.
Negligent or
disinterested. Poor
working practices likely
to cause pollution.
Appendix C
Poor
Fair
Average
Good
1.2
3.4
5.6
7.8
9.10
Excellent
Generally meets
deadlines but needs
chasing.
Consistently always
meets deadlines in any
circumstances.
Adequate packing
provided for general
protection of the goods
protection provision
lead to damage of
goods.
protection provision
provided
4.B.3
4.B.3.1 Purpose
The systematic on-going evaluation of the performance of vendors engaged on
different projects against set criteria facilitates communication relating to actual
capabilities. Performance results are used in comparing and selecting preferred
partners, when determining the need for suspension, delisting or improvement
actions. Proper use of such feedback should lead to reduce risk of engaging poor
performers who fail to meet requirements, and lead to improve overall performance
by use of more capable organizations. Guidelines for vendor appraisal reporting
executed on the ERP are given below. With this platform performance data,
including latest subcontractor safety results, can be accessed for review at any time.
4.B.3.2 Timing
Frequency -
4.B.3.3 Participants:
4.B.3.4 Distribution:
4.B.3.5 Guidelines:
1)
2)
Following data entry vendors overall performance call be viewed using the
JDE.
Appendix
"4B3_App A
"4B3_App B
Appraisal business p Appraisal Dump Scr
"4B3_App C
Vendor indicator .xl
"4B3_App D
Vendor Performanc
Jun-2004
4.B.4
Staff Gathering
4.B.4.1 Purpose
To provide an informal environment for all the site staff to share their views on all
areas and also to improve communication links amongst site management,
operatives and others. To encourage participation gatherings should be held
regularly in an informal atmosphere and any notable outcomes or useful ideas
should be handled and followed up properly to demonstrate that views are taken into
account.
4.B.4.2 Timing
As determined by PM
Frequency -
Occasional
4.B.4.3 Participants:
4.B.4.4 Distribution:
---
4.B.4.5 Guidelines:
(1)
(2)
Committee should be formed with all levels including PM, SA, Engineer, Site
Administrator or Site Clerk.
(3)
(4)
(5)
Gatherings should be informal and in the form of a BBQ, buffet lunch, dinner or
similar.
(6)
(ii)
Jun-2004
Jun-2004
4.C.1
4.C.1.1 Purpose
A Site Safety Committee will be set up in accordance with the project Safety Plan or
Contract requirement in order to review the implementation and performance of the
safety management system on site. During the meeting the Safety Officer will
generally report on the safety conditions on the site including the results of physical
inspections and safety records. He will also report on training conducted, risk
assessments and other relevant issues. The Committee discusses the matters
reported and areas of concern to determine actions necessary in order to maintain
good safety standards on site and/or to make improvements where necessary.
4.C.1.2 Timing
To be held throughout the whole project period
Frequency -
4.C.1.3 Participants:
4.C.1.4 Distribution:
All participants
4.C.1.5 Guidelines:
---
Appendix
Agenda
"4C1_App_Agend
a (Monthly Site Safe
Jun-2004
4.C.2.
4.C.2.1 Purpose
Internal Safety Audits are carried out in accordance with the F&IU (SM) Regulations
and OHSAS 18001 HS&E management system to independently monitor the
effectiveness of system implementation. Audits also serve to enhance safety
awareness and through the implementation of actions and recommendations arising
can improve the overall effectiveness of the site safety management system.
4.C.2.2 Timing
For projects over $100M or 100 people, Safety Audits must be carried out within 6
months of project commencement and not longer than 6 months intervals thereafter
or in accordance with contract and/or Statutory requirements. For other projects the
time and frequency of audits to be undertaken in accordance with the HS&E
management system, contract or statutory requirements.
Frequency -
4.C.2.3 Participants:
4.C.2.4 Distribution:
---
4.C.2.5 Guidelines:
(1)
Audit Administration
Safety audits are usually conducted using staffs who are not directly involved in the
project. Audit procedures are described under the HS&E Management system
Procedure HSEMSP - 13.
Appendix
"4C2_App_Sample
Audit Report.doc"
Jun-2004
4.D.1
4.D.1.1 Purpose
Internal Audits are conducted to monitor the implementation and effectiveness of the
quality and environmental management systems. They also serve to demonstrate
internal control for certification purposes or to fulfil contract requirements. Audit
results can be used to assess performance and identify areas for improvement. The
Certification Body and some Clients also conduct system audits.
4.D.1.2 Timing
Internal Audit Schedules are published by the Quality Management Dept / HS&E
Dept and distributed during the year. Audit plans are coordinated with contract and
regulatory requirements and occasionally separate project audit schedules are also
developed. The exact timing of each audit is checked with projects beforehand to
minimize inconvenience.
Frequency -
4.D.1.3 Participants:
4.D.1.4 Distribution:
---
4.D.1.5 Guidelines:
(1)
(3)
Appendix
"4D1_App A.pdf"
"4D1_App B.pdf"
Jun-2004
Report date:
Project Title:
Client:
Consultant/architect:
Contracts Director:
Date of award:
Contracts Manager:
Contract commencement:
Project Manager:
Contractual completion:
Senior QS:
Duration:
Progress status:
Monthly
milestone/
critical
activity
Description
Progress notes:
Planned
progress
Actual
progress
+/- days
+/- days
5.A.1
5.A.1.1 Purpose
To accurately assess the current position of work done on the project and give a
brief overview of the commercial position. It should report the status with reference
to the applicable Master Programme and budget. The report shall highlight any key
issues that might affect the success of the project including any planning, quality,
commercial or HS&E issues that the site management consider relevant.
5.A.1.2 Timing
The report should be submitted to the Head Office by the Project Manager before
the 5th of each month for consideration and incorporation in the Green Book for
senior management circulation
Frequency -
Monthly
5.A.1.3 Participants:
5.A.1.4 Distribution:
CM / Senior Management
5.A.1.5 Guidelines:
(1)
The content should be agreed with the relevant Contracts Manager to suit the
individual project requirements. Please find an attached sample report as
guideline.
Note: Monthly Progress Reports prepared and submitted to Clients may differ from
internal reports in terms of format, content and detail.
Appendix
5A1_App.xls
Jun-2004
5.A.2.
5.A.2.1 Purpose
This meeting serves as an overall performance update and communication bridgeover between the senior operations management, supporting functions and site staff.
Items arising from the discussions may need to be conveyed to Project Managers at
site level and to functional staff to seek views, reinforce policies, implement actions
or avoid misunderstandings.
The purpose of this meeting is to discuss operation issues giving a perspective view
on key matters that might affect the successful execution of site works.
5.A.2.2 Timing
To be decided by the top management
Frequency -
Bi-monthly
5.A.2.3 Participants:
5.A.2.4 Distribution:
---
5.A.2.5 Guidelines:
---
Appendix
Agenda
5A2_App.doc
Jun-2004
0
/
#DIV/0!
0
Latest Forecast
Tender Budget
Contract Value
Contract GP
Profit Margin
Cumulative-to-Date
#DIV/0!
#DIV/0!
Claims Income
Total Amount Submitted
Less : Amount Agreed
Outstanding
Contract Number:
Contract Title:
Client:
Director:
Contracts Manager:
Project Manager:
Senior QS:
#DIV/0!
Note: GD applies
-
Current
Month
Cumulative
to-Date
/ 20
/ 19
%
on
TO
Cash Position
Cash Receipt
Internal Valuation
Less : WIP
Uncertified Value
Contract Receivable
Retention Receivable
####
####
####
####
####
####
####
Contract Title :
Job No. :
Claim No
[A]
Description
[B]
Date
Notified
[C]
Value in
Application
[D]
Certifications made
Month
Cumulative
Value to
Value to
Gross
Others
Gross
Others
[G]
[H]
[I]
[J]
Submission
Date
Value
[E]
[F]
Gross
Claims
taken
in Value
[K]
-
Totals :
Location : P\Mgt Report\Report to RB\5B1_App 2_Claim and Dispute Item Schedule (Blank Form)\Claims & Disputed
5.B.1
5.B.1.1 Purpose
This report is prepared to provide the required information on the financial
performance of the project for the period, the cumulative performance since
commencement and the projected financial outcome. The report is intended to
summarize the liabilities, exposures, risks and opportunities for control purposes
5.B.1.2 Timing
As required by the Commercial Manager, MQS and CM
Frequency -
Monthly
5.B.1.3 Participants:
5.B.1.4 Distribution:
5.B.1.5 Guidelines:
The content of this report may vary depending on the project requirements. Below is
an example of what is recommended to submit and review on a monthly basis. It
should be read in conjunction with the Monthly Progress Report outlined under Box
5.A.1 of this Handbook.
(1)
Executive summary
Excel sheet as per attached example. Should also contain the schedules
concerning Claims and Disputed Item Schedule, VO Schedule, SC/Supplier
Claims Schedule, Insurance Claims Schedule
(2)
(3)
(4)
SC Payment Status
QS Module > QS Activities > SCL&P > SCLR > SCLSR (R58310)
(5)
Jun-2004
(6)
(7)
(8)
(9)
Appendix
"5B1_App
1_Executive Summa
"5B1_App 2.xls"
Jun-2004
5.B.1
5.B.1.1 Purpose
This report is prepared to provide the required information on the financial
performance of the project for the period, the cumulative performance since
commencement and the projected financial outcome. The report is intended to
summarize the liabilities, exposures, risks and opportunities for control purposes
5.B.1.2 Timing
As required by the Commercial Manager, MQS and CM
Frequency -
Monthly
5.B.1.3 Participants:
5.B.1.4 Distribution:
5.B.1.5 Guidelines:
The content of this report may vary depending on the project requirements. Below is
an example of what is recommended to submit and review on a monthly basis. It
should be read in conjunction with the Monthly Progress Report outlined under Box
5.A.1 of this Handbook.
(1)
Executive summary
Excel sheet as per attached example. Should also contain the schedules
concerning Claims and Disputed Item Schedule, VO Schedule, SC/Supplier
Claims Schedule, Insurance Claims Schedule
(2)
(3)
(4)
SC Payment Status
QS Module > QS Activities > SCL&P > SCLR > SCLSR (R58310)
(5)
Jun-2004
(6)
(7)
(8)
(9)
Appendix
"5B1_App
1_Executive Summa
"5B1_App 2.xls"
Jun-2004
5.B.2.
Green Book
5.B.2.1 Purpose
This is a monthly management report of all the business performance results that is
used by senior management for review and control purposes. The range of reports
included in the Green Book is attached for information purposes
5.B.2.2 Timing
--Frequency -
Monthly
5.B.2.3 Participants:
Senior Management
5.B.2.4 Distribution:
5.B.2.5 Guidelines:
(1)
Appendix
The Green Book is compiled and published on a monthly basis using the
inputs provided by the Directors, PMs and CMs, Commercial Managers and
Department Managers according to the monthly cut off dates published by the
Accounts Department.
5B2_App.pdf
Jun-2004
Project:
Job No.:
Please attach records of non-conformance such as environmental monitoring/measurement data, site inspection results (i.e. environmental checklist),
complaint proforma, audit report or minutes of site management review meeting where applicable.
Valid Licenses / Permits issued by the EPD or Notifications submitted to the EPD:
Type of Licenses/Permits
Further Environmental Permit
(Form 6 under EIA Ordinance)
Quantity
Reference No.
Issued/submitted on
Expired on
Prepared by SER:
Name:
Signature:
Date:
Rev. 2
20/11/00
5.C.1.
HS&E Report
5.C.1.1 Purpose
These reports shall be made regularly in order communicate incidents and accidents
that have occurred, to summarise the environmental performance and data on
projects, to indicate license and permit status, identify corrective/preventive actions,
mitigation or control measures and to give information on safety training provided.
These reports collectively allow the company to assess overall company and
subcontractor HS&E performance.
5.C.1.2 Timing
To be carried out throughout the whole project period.
Frequency -
5.C.1.3 Participants:
5.C.1.4 Distribution:
5.C.1.5 Guidelines:
(1)
b)
(enter
Jun-2004
c)
JDE Reports: The following reports can be accessed using the Crystal
Reporting System through:
-
Complaint Proforma
Conviction Report
Security Report
Accident Summary
Incident Summary
(2)
(3)
Appendix
"5C1_App
A_Project Environm
"5C1_App B_
Environmental Perfo
Jun-2004
Appendix
SAMPLE
MONTHLY PROJECT QUALITY REPORT
Job No. : JXXXX
No.
1.
2.
2.1
2.2
2.3
2.4
2.5
2.6
2.7
3.
3.1
3.2
3.3
3.4
4.
5.
Description
Most significant Nonconformance / Client Complaint this month is.
a.
b.
c.
d
e.
Typical current problem areas affecting quality performance (circle)
Substandard material
2.8
Inadequate control of workmanship
Not following work procedure /
2.9
Insufficient training
method statement
2.91 Unclear client standard / acceptance level
Inadequate resources
/ requirements
Inaccurate or outstanding design
2.92 Human error
information
2.93 Design fault
Insufficient planning or scheduling 2.94 Fast construction
Poor co-ordination
2.95 Others :
Poor internal or external
communication
Improvements carried out during the period (circle)
Tighter supervision
3.5 More resources
Subcontractor briefings/training
3.6 Better methods
More inspections
3.7 Others :
More samples
Potential problems Main concerns in coming months
a. Description b. Potential Cause c. Preventive Action Planned
Signed by :
Original Signed
(PM)
Date :
Page 1 of 1
5.D.1
5.D.1.1 Purpose
A Monthly Project Quality Report serves the purpose of communicating any
significant quality issues, complaints and non-conformances arising during the
month and to identify typical current problem areas affecting quality, any
improvements carried out and future concerns.
5.D.1.2 Timing
To be completed by the Project Quality Representative and signed off by the Project
Manager for distribution within the first week of each month
Frequency -
Monthly
5.D.1.3 Participants:
5.D.1.4 Distribution:
5.D.1.5 Guidelines:
---
Appendix
"5D1_App_Monthl
y Quality Report.do
Any
Improvements?
Current
Problems
Jun-2004
6.1
6.1.1
Purpose
To capture the key successes and lessons learnt on the project to facilitate
knowledge management and future improvement. During the process the overall
performance of the project including productivity, planning, sub-contractor
performance, HS&E, Quality and commercial aspects shall be reviewed and
compared to what was assumed at tender stage.
6.1.2
Timing
Meeting to be held within three months of issuance of substantial completion
certification by the client.
Frequency -
Once
6.1.3
Participants:
6.1.4
Distribution:
6.1.5
Guidelines:
(1)
Appendix
Agenda
"6-1_App Wrap
Up Agenda.doc"
Jun-2004