Professional Documents
Culture Documents
Standard Specification
R1116010-TOSS-10-006
ADOE
Amendment Record
Issue/revision Date Remarks Signature
0 01/06/16 First issue CFPA/ADSC-Narongsak
Note: This CFP Project Specific Standard/Specification has been developed from original Corporate
Standard TOSS-10-006 Revision 0, Dated 30/11/13
This document is confidential. Neither the whole nor any part of this document may be disclosed to any third party without the prior
written consent of Thai Oil Company Limited Thailand.
The copyright of this document is vested in Thai Oil Company Limited
All rights reserved. Neither the whole nor any part of this document may be reproduced, stored in any retrieval system or transmitted
in any form or by any means without the prior written consent of the copyright owner.
Issue No: 1 Revision No: 0 Issued on: 01/06/16 Code No: R11116010-TOSS- 10-006
Page No: 1 of 30. Originator : CFPA/ADSC-Narongsak Approved by: ADOE
General Project Control Requirements
Doc. No.: TOSS-10-006 Rev.: 0
INDEX
Issue No: 1 Revision No: 0 Issued on: 01/06/16 Code No: R11116010-TOSS- 10-006
Page No: 2 of 30. Originator : CFPA/ADSC-Narongsak Approved by: ADOE
General Project Control Requirements
Doc. No.: TOSS-10-006 Rev.: 0
1.0 INTRODUCTION
1.1 SCOPE
This document identifies the specification to be followed by the CONTRACTOR as appropriate
in the application of the project control. This document provides the minimum requirements for
fulfilling in understanding of general requirements in terms of project control to be implemented
on Thai Oil project. The scope is required on EPC/EPCm and FEED/BDEP phase where any
requirements in this document are applicable. This document defines the requirements on
contents and their reporting of major functions of project control below:
Where necessary, CONTRACTOR’s standard plans and procedures shall allow for any
revisions and modifications to incorporate OWNER’s requirements that may be required from
time to time throughout the execution of the Work. This document describes the essential
requirements of OWNER to be incorporated into CONTRACTOR’s plans and procedures, but
does not exclude the addition of enhancements by CONTRACTOR. The requirements
described in this document is general requirement only, the specific plans and procedures
which are appropriate for each project phase, type and scope shall be prepared by the
CONTRACTOR and approved by OWNER in-line with this documentation.
CONTRACTOR shall provide OWNER with native files and access to all relevant planning,
schedule, progress, estimate, change, and cost control documents at all times during the work.
CONTRACTOR shall also provide copies of all SUBCONTRACTORS’ and VENDORS’
schedules, progress and relevant planning and cost data/information.
CONTRACTOR shall ensure that all reporting schedule, progress, cost, and change
information is an accurate record of the PROJECT status as determined from the Project
Controls procedures and system. All such information shall be subject to audit by OWNER.
CONTRACTOR shall provide the necessary computer hardware and software to allow
electronic transfer of CONTRACTOR’s Project Controls data, for analysis and verification by
OWNER.
Any deviations from this document shall let OWNER review and approve before use.
1.2 DEFINITIONS
For the purpose of this specification, the following definitions shall hold :
SHALL
: is to be understood as mandatory to comply with the requirements of this specification.
SHOULD
: is to be understood as strongly recommended to comply with the requirements of this
specification.
CONTRACT
Issue No: 1 Revision No: 0 Issued on: 01/06/16 Code No: R11116010-TOSS- 10-006
Page No: 3 of 30. Originator : CFPA/ADSC-Narongsak Approved by: ADOE
General Project Control Requirements
Doc. No.: TOSS-10-006 Rev.: 0
: mean the CONTRACT between the OWNER and CONTRACTOR for the Works to
realize the project.
CONTRACTOR
: mean FEED/BDEP CONTRACTor and/or EPC/EPCm CONTRACTor. CONTRACTor
shall have the meaning assigned to it in the CONTRACT and shall, where the context
so requires, include CONTRACTor's employees, agents, workmen and/or
representatives, successors, permitted assignees and SUBCONTRACTORS.
CRITICAL PATH METHOD (CPM) NETWORK
: mean a computerized logically linked critical path method schedule network.
WORK BREAKDOWN STRUCTURE (WBS)
: is the structured hierarchical system by which the project work scope is broken down
into discrete units for project management and control purposes. CONTRACTOR
shall propose and apply the WBS to all levels of planning, scheduling, progress
measurement.
COST BREAKDOWN STRUCTURE (CBS)
: is the structured hierarchical system by which the project cost is broken down into
discrete units for project management and control purposes. CONTRACTOR shall
propose and apply the CBS to all levels of planning, budgeting, cost controlling.
BASIC DESIGN ENGINEERING PACKAGE (BDEP)
: Activities after Approval for Development up to Design Verification, which include
Process Design, Basic Engineering Design, Cost Estimation, etc. to perform EPCm on
next phase.
FRONT END ENGINEERING DESIGN (FEED)
: Activities after Approval for Development up to Design Verification, which include
Process Design, Basic Engineering Design, Cost Estimation, etc. to perform EPC on
next phase.
CHANGE IN THE WORK
: mean any modification or alteration of, amendment or addition to, or deletion from the
Work, in accordance with the provisions of the CONTRACT.
Issue No: 1 Revision No: 0 Issued on: 01/06/16 Code No: R11116010-TOSS- 10-006
Page No: 4 of 30. Originator : CFPA/ADSC-Narongsak Approved by: ADOE
General Project Control Requirements
Doc. No.: TOSS-10-006 Rev.: 0
CONTRACTOR’s Project Controls procedures shall provide a detailed project controls plan
cover CONTRACTOR’s project controls and administration activities from the effective date
through the completion of project. The project controls plan and procedures shall fully meet the
requirements of the Technical Requirements set forth herewith.
Issue No: 1 Revision No: 0 Issued on: 01/06/16 Code No: R11116010-TOSS- 10-006
Page No: 5 of 30. Originator : CFPA/ADSC-Narongsak Approved by: ADOE
General Project Control Requirements
Doc. No.: TOSS-10-006 Rev.: 0
CONTRACTOR shall be responsible for the detailed planning and scheduling of all
engineering, procurement, construction, pre-commissioning/commissioning, an any third
parties activities required to carry out the work in accordance with the CONTRACT scope and
with the project specification. CONTRACTOR shall ensure that the work is so planned as to
meet the schedule dates required by the CONTRACT.
The level of planning shall be such that OWNER can be assured that the schedule can be met
and that any significant delay can be identified, evaluated, controlled, and accommodated
within the overall schedule.
The planning and scheduling system shall be based on detailed logic networks software, using
Primavera Project Planner for Windows – Version 6.0 or later, for critical path analysis during
the execution of the Work. The detail shall support and be compatible with the WBS and the
higher levels of planning used for management reporting both to OWNER and within
CONTRACTOR’s organization.
All schedules submittals are to be provided in a native, as well as Adobe Acrobat (.pdf) format.
The format, coding, activity ID numbering and reporting criteria shall be identified in
CONTRACTOR’s Project Controls Procedure.
After the schedule has been mutually agreed to by OWNER to become the baseline Project
Schedule, It will be updated monthly to show forecast and actual completion dates against
baseline.
CONTRACTOR shall apply construction geographical area codes to all applicable schedule
activities as defined by OWNER in the Site Plan / Plot Plan Construction Areas or as agreed
with the OWNER.
The WBS shall be consistently applied in all planning documents, time schedules, progress
control, and progress reporting documents. The WBS shall be used as the basis of all
reporting during the life of project, progress shall be reported according to hierarchy WBS
figure from work package, discipline, project phase, up to overall project WBS level.
Issue No: 1 Revision No: 0 Issued on: 01/06/16 Code No: R11116010-TOSS- 10-006
Page No: 6 of 30. Originator : CFPA/ADSC-Narongsak Approved by: ADOE
General Project Control Requirements
Doc. No.: TOSS-10-006 Rev.: 0
The Level I Project Milestone Schedule shall consist of a complete list of project milestones
and showing the planned in accordance with the CONTRACT. All milestone dates will be
generated and updated from the lower level schedules. In order to allow subsequent schedule
control at management level, it shall identify sufficient milestones within the various phases of
the work. Key components of the Level I schedule will include:
- Agreed Project Milestones and Key Activities
- Discipline level
- Current bar line showing status and remaining duration versus target
- Target, Actual and Forecast Dates for Milestones
Once established as a baseline, the Level I schedule shall not be changed without OWNER
approval. Actual and forecast variances from the schedule shall be shown clearly in a format
acceptable to OWNER.
The assessment of the actual status and forecast inclusive schedule exceptions and proposed
remedial actions shall be carried out monthly and this shall be superimposed on the Project
Milestone Schedule. The schedule shall be included in the monthly progress report.
Intermediate assessment may be required for critical activities.
The Level II Project Summary Schedule shall be in sufficient detail to demonstrate how the
CONTRACTOR plans to execute the PROJECT within the target dates contained in the Project
Milestones. It shall be based on the WBS structure. Additional activities, key dates and
interfaces shall be shown where this aids the demonstration of critical or high-risk elements of
the PROJECT.
Key components of the Level II schedule will include:
- Clearly defined relationships between each Project phase
- A defined framework from which the Level III Network Schedules and resource
analysis can be developed
- Identification of key review activities involving OWNER, e.g.:
Issue No: 1 Revision No: 0 Issued on: 01/06/16 Code No: R11116010-TOSS- 10-006
Page No: 7 of 30. Originator : CFPA/ADSC-Narongsak Approved by: ADOE
General Project Control Requirements
Doc. No.: TOSS-10-006 Rev.: 0
o HAZOP Review
o Plot Plan Reviews
o 3D CAD Model Reviews
o Complete CAEPEX +/- 10%
o Constructability Review
o Any other reviews agreed during the project.
- Identification of critical and high-risk activities through all phases of the project
and shall include engineering, long lead items, subcontracts and construction
related activities
- Work packages level which are:
o Document type for engineering
o Commodity type for procurement
o Work type for construction
Typically, the Level II Project Summary Schedule shall be a logical presentation on a single
sheet, suitable for reduction to A3 or A4 format, containing no more than 60 lines. It shall
summarizes for each Level I WBS element the main phases of the Level II WBS. The format
of the Level II Project management schedule shall be agreed with OWNER. The Level II shall
be updated monthly included in the monthly progress report, as an attachment if necessary.
The Engineering, Procurement, and Construction (EPC) Network Schedule Level III shall be a
responsive and up to date model of the PROJECT and shall be the tool for schedule analysis,
providing identification of float, critical path(s) and resource shortages. They shall be
developed to cover the total scope of the PROJECT and shall provide the schedule basis for
the Level IV detailed schedules and control documents. All Project and Payment Milestones
shall be clearly identified and integrated into the network logic, as shall SUBCONTRACTORS’
and VENDORS’ schedules, ensuring the inclusion of all activities necessary to achieve
completion. Specifically, the Level III planning networks shall emphasize Engineering,
Procurement and any early Site activities, showing Construction and Commissioning in
sufficient detail to establish the major interfaces between Engineering disciplines and
Procurement. The level of detail shall enable identification of Required on Site dates for
design deliverables and materials. Typically the size of this network will be in the region of
1,000 – 3,000 activities.
The Level III Schedule shall be in direct alignment with the Level I CONTRACT Milestone
Schedule and Project Management Schedule.
CONTRACTOR shall issue the Level III schedule in the form of detailed precedence CPM
networks and based on the WBS for OWNER review and comment as soon as reasonably
practical but in no event later than 2 months after CONTRACT award date. OWNER agrees to
provide any such comments to CONTRACTOR within ten (10) business days of receipt of such
schedule from CONTRACTOR, and CONTRACTOR agrees to consider in good faith any and
all comments made by OWNER. OWNER’s review or comment on such schedule (or its failure
to do so) shall not in any way affect or reduce CONTRACTOR’s obligations to complete the
project in a timely manner in accordance with this CONTRACT. The key dates must conform to
the Level I CONTRACT Milestones Schedule. Once agreed with OWNER, this schedule shall
be “baseline” and set as a target against the current schedule which CONTRACTOR shall
compare all subsequent reporting. This “baseline” schedule shall also form the basis for the
production of progress and quantity analyses as described in CONTRACTOR’s proposed
Project Controls Procedure.
Issue No: 1 Revision No: 0 Issued on: 01/06/16 Code No: R11116010-TOSS- 10-006
Page No: 8 of 30. Originator : CFPA/ADSC-Narongsak Approved by: ADOE
General Project Control Requirements
Doc. No.: TOSS-10-006 Rev.: 0
The Construction section of the Level III schedule shall be further developed and expanded in
detail throughout the execution of the Work to be consistent with the baseline schedule. This
shall be structured on the basis of construction trade and construction area. The Construction
work in each work area/ work site execution schedule shall be submitted for review and
approval 3 months prior to commencement of work at that location.
Issue No: 1 Revision No: 0 Issued on: 01/06/16 Code No: R11116010-TOSS- 10-006
Page No: 9 of 30. Originator : CFPA/ADSC-Narongsak Approved by: ADOE
General Project Control Requirements
Doc. No.: TOSS-10-006 Rev.: 0
The Level III CPM network shall be updated at least monthly and issued to OWNER. Every
issue shall include an electronic issue of native file to enable OWNER to review using
Primavera software. CONTRACTOR shall prepare standard reports from the network, which
clearly demonstrate the current performance against the approved PROJECT baseline
schedule. These shall include bar charts and tabulations, the format of which shall be agreed
with OWNER. The minimum bar chart report shall be presented as a comparison of the agreed
baseline schedule and the current schedule showing actual/forecast with tabulation showing
activities ID, activities name, duration, early plan date, actual/forecast date, and total float.
CONTRACTOR shall analyze the schedule to identify the critical path and shall, throughout the
duration of the PROJECT, update the critical path. All changes made to the networks as part
of the monthly biweekly update shall be reported to OWNER together with the critical path
analysis.
The Master Baseline Schedule shall be supported with a concise description of the schedule
basis and assumptions used in development of the schedule. This description shall address, at
a minimum:
Scope, basis and assumption included in the baseline schedule
Critical Path Analysis identify schedule risk and mitigation action
Progress curves
Procurement lead times for all major equipment and packaged units.
Brief Construction execution and methodology (e.g. stick build vs
modularization, etc.)
Work patterns and holiday schedules by Work Area/Work Site.
Weather windows and allowances.
External interfaces and constraints.
WBS or activity codes used in formatting the schedule
Definition of resources used in the resource loading
Level IV Detailed Schedules & Control Documents shall be prepared by CONTRACTOR and
issued to OWNER as indicated below. These documents and/or their supporting databases
shall describe in detail the scope of work in terms of quantity and schedule. They shall be
CONTRACTOR’s principle control tools. The schedule shall allow time for OWNER review and
shall provide the basis for the day-to-day implementation of the PROJECT as well as being the
mechanism for progress measurement.
Level IV Detailed schedules and Control Documents shall be compatible with the WBS and
shall fully support the Level III CPM networks. CONTRACTOR will be expected to
demonstrate that Level IV scheduling is directly related to Level III CPM network and illustrate
interfaces between levels.
Level IV Detailed schedules and Control Documents shall comprise as a minimum the
following and include their supporting databases:
Deliverable List
Requisition Index
Purchase Order Index
Packages Purchasing and Awarding Plan
Issue No: 1 Revision No: 0 Issued on: 01/06/16 Code No: R11116010-TOSS- 10-006
Page No: 10 of Originator : CFPA/ADSC-Narongsak Approved by: ADOE
30.
General Project Control Requirements
Doc. No.: TOSS-10-006 Rev.: 0
Note
Level IV schedule required no later than 2 months before first activity planned to
commence. The format and content of the above shall be agreed with OWNER no later than 4
weeks after CONTRACT award. Planned, actual and forecast data shall be detailed and
reports provided both in full and on an exception basis. Additional schedules and documents
will be provided by CONTRACTOR where requested by OWNER to demonstrate effective
control of the PROJECT.
CONTRACTOR shall notify OWNER within 24 hours after any occurrence which will
adversely affect the Mechanical Completion. CONTRACTOR shall also notify OWNER, at least
once a week, during construction the status of the Critical Action Items which could affect the
completion of the PROJECT. In addition, CONTRACTOR shall include an action plan of
proposed remedial actions for expediting these items to achieve the completion date. Upon
review and permission to proceed by OWNER, CONTRACTOR shall implement the remedial
actions.
All levels of planning and scheduling shall be submitted to the OWNER for review.
The 90 Days Schedule shall be issued for OWNER’s review and approval within 14 days after
CONTRACT award to control the PROJECT during the development of the Level III network. It
shall detail specific mobilization activities and initial engineering and procurement activities.
After approval, all subsequent issues to OWNER shall be every one (1) week, with current
progress and status date indicated.
The 90 Days Schedule shall include, but not be limited to:
The provision of CONTRACTOR and OWNER facilities.
Issue No: 1 Revision No: 0 Issued on: 01/06/16 Code No: R11116010-TOSS- 10-006
Page No: 11 of Originator : CFPA/ADSC-Narongsak Approved by: ADOE
30.
General Project Control Requirements
Doc. No.: TOSS-10-006 Rev.: 0
This schedule shall follow the WBS and it shall be structured identically to the Level III CPM
Network. It shall be updated and reissued every week using a ‘Time-now’ line to show actual
progress achieved until such time that the Level III CPM schedule is ready for use.
CONTRACTOR shall prepare, maintain and issue Lookahead Schedule(s) for each work Area/
work Site. The format shall show previous week’s actual status against previously reported
planned activities, activities planned for the coming period and a preview of work to be
completed against the baseline plan. CONTRACTOR shall propose the exact period(s) to be
shown on the Lookahead Schedule(s). OWNER reserves the right to further define these
period(s) as the work progresses. The schedule data shall be in direct alignment with the
relevant work area/ work site execution and clearly indicate Critical Path activities.
Issue No: 1 Revision No: 0 Issued on: 01/06/16 Code No: R11116010-TOSS- 10-006
Page No: 12 of Originator : CFPA/ADSC-Narongsak Approved by: ADOE
30.
General Project Control Requirements
Doc. No.: TOSS-10-006 Rev.: 0
Progress will be assessed against an agreed gate system and specified at individual
deliverable level. Each deliverable or task will have a component budget weighting. Gate
system is indicator for percent completion of deliverable in each revision step.
The Control Schedule will be monitored monthly and will be used as the baseline against which
progress is reported as part of the Project monthly report. The project controls will liaise with
the activity to review any area of specific progress variances. The project controls will liaise as
necessary to highlight any potential slippage to the overall schedule and to recommend any
corrective actions required.
The key to performance measurement is the objective assessment of the level of completion of
work in progress. All work is either completed, in progress or not yet started. Completed work
presents no performance measurement problem since those work packages have been
closed, the budget has been earned and progress been reported. Future work will not be
measured until the work gets underway. The only work elements to be concerned about are
those that are planned to be or are actually in progress. The method of measuring progress is
the earned value method.
4.1.2 Procurement
Procurement Progress is primarily assessed in terms of progress on each
Requisition/Purchase Order, weighted based on their value budgets. A gate system will be
implemented to establish a percentage completion based on the current step in the
procurement process (e.g. purchasing requisition, request for quotation, quotation received
from vendor, commercial bid evaluation, purchase order, receipt of key vendor document,
materials received, etc.).
4.1.3 Construction
Fabrication and construction shall be determined based on the measurement of physical
quantity of work done against total volume of work. Construction progress is measured as the
actual % progress of production work steps for work item. CONTRACTOR shall utilize the
spreadsheet to determine the progress against each category off work (eg cubic metres of
concrete, tonnes of steel erected, equipment items installed, etc).
Issue No: 1 Revision No: 0 Issued on: 01/06/16 Code No: R11116010-TOSS- 10-006
Page No: 13 of Originator : CFPA/ADSC-Narongsak Approved by: ADOE
30.
General Project Control Requirements
Doc. No.: TOSS-10-006 Rev.: 0
The Production Status of Construction Key Quantities shall present a comparison of actual
progress with the scheduled figures for a number of controllable items in representative
categories such as:
- Number of Piles driven
- Cubic metres of concrete poured
- Number of spols fabricared/installed
- DB of Fabrication and Erection completed
- Metre of Steam Tracing erected
- Number of Hydrotest Package completed
- Tonnage of steelwork fabricated/installed
- Number of equipment items installed
- Number of instruments and control elements installed and connected
- Cable metres or square meters or conduit length installed
- Square metres of area painted
- Number of Motor Test Run completed
- Number of Loop Check completed
The weekly report package will be reviewed and discussed in weekly progress meeting to be
held on a day to be agreed, and the CONTRACTOR is reminded that this information must be
prepared in time for such meetings. Notes of the meeting shall be prepared by
CONTRACTOR.
The reports required from CONTRACTOR to be submitted on weekly basis are as follows:
Weekly Progress Summary Table and S-Curve
Major achievements this week
Major work planned to commence and/or accomplish on next two weeks
Slippage and Action plan for major activities lagging behind schedule
Three Week Schedule
Critical Activities
Area of concern
Procurement status
Production Status of Construction Key Quantities (during Construction)
Issue No: 1 Revision No: 0 Issued on: 01/06/16 Code No: R11116010-TOSS- 10-006
Page No: 14 of Originator : CFPA/ADSC-Narongsak Approved by: ADOE
30.
General Project Control Requirements
Doc. No.: TOSS-10-006 Rev.: 0
Executive summary
Area of Concern
Achievements this month
Goals next month
Slippage and Action plan for major activities lagging behind schedule
HSE statistics (during construction)
QA/QC activities (during construction)
Engineering narrative
Procurement narrative
Construction narrative
Production Status of Construction Key Quantities (during Construction)
Level-II/III Schedule Update
Critical Path Analysis
Summary schedule/project milestones status
Progress Summary Table and S-curve
Progress Evaluation Sheet
Procurement status
Deliverable Status of Engineering/Vendor/Contractor Documents and Drawings
QC Summary Report
Manpower Histogram (during construction)
Manday and Manhour Summary (during construction)
Labour Productivity (during construction)
Major Construction Equipment Loading (during Construction)
Arrival of any major materials/equipment
Photographs of work site
The reports shall be supplemented with a brief narrative description to explain the area of
concern, issues, CONTRACTOR requirements, and other limitations obstructing the works.
Above mentioned reports are the minimum necessary documents only, the additional or
supplementary reports may be also required to provide an assessment of actual
CONTRACTOR performance e.g. production progress report, system turnover status, etc.
Issue No: 1 Revision No: 0 Issued on: 01/06/16 Code No: R11116010-TOSS- 10-006
Page No: 15 of Originator : CFPA/ADSC-Narongsak Approved by: ADOE
30.
General Project Control Requirements
Doc. No.: TOSS-10-006 Rev.: 0
personnel will be identified prior to the meeting. Notes of the meeting shall be prepared by
CONTRACTOR and agreed by OWNER.
CONTRACTOR shall brief the overall project progress status, the content in presentation slide
shall cover topics below as a minimum.
Overall Progress Summary
Major Achievements This Month
Major Goals Next Month
Summary Level-I Bar Chart Schedule Status
Critical Path Analysis
Engineering Status Summary and Area of Concern
Procurement Status Summary and Area of Concern
Construction Status Summary and Area of Concern
Manpower Plan and Status
Progress Photos
Major Delay Items and Recovery Actions
CONTRACTOR shall early identify for any potential schedule delay, any issues shall be raised
for discussion with OWNER to agree on solutions.
Issue No: 1 Revision No: 0 Issued on: 01/06/16 Code No: R11116010-TOSS- 10-006
Page No: 16 of Originator : CFPA/ADSC-Narongsak Approved by: ADOE
30.
General Project Control Requirements
Doc. No.: TOSS-10-006 Rev.: 0
The CONTRACTOR shall have a cost control system in order to identify the budget allocated
to specific CONTRACTs and purchase orders to control costs against a predetermined
estimate or budget, provide information to facilitate OWNER decision-making and identify the
out of scope project commitments.
The Cost Budget shall be submitted for OWNER review and approval before further use for
cost monitoring and control, this shall provide a link to the estimating commodity code and
shall be directly related to activities contained in the CAPEX estimation detail sheets in order to
maintain budget, forecast and actual cost and to ensure progress achieved aligns with the
CAPEX estimation. Budgets for each package of work shall be settled and made available to
procurement/CONTRACT prior to placing any commitment
The budget allocations are held by the CONTRACTOR and shall clearly identify:
The CBS to be used for budget allocation
The scope of each purchase order or CONTRACT package
The estimating commodity code related to each budget
The cost items outside of the project scope
The required additional budget due to recognized scope changes
The escalation budget to be used
The contingency budget to be used
The CBS shall be consistently applied in all cost budgeting, cost posting, controlling, and
reporting documents. The CBS shall be used as the basis of all cost reporting during the life of
project, cost summary shall be reported according to hierarchy CBS figure from lower to
highest overall level.
Issue No: 1 Revision No: 0 Issued on: 01/06/16 Code No: R11116010-TOSS- 10-006
Page No: 17 of Originator : CFPA/ADSC-Narongsak Approved by: ADOE
30.
General Project Control Requirements
Doc. No.: TOSS-10-006 Rev.: 0
CONTRACTOR shall early identify OWNER for any significant trends in the forecast final cost
on potential cost overrun/underrun and then discuss with the OWNER in a timely manner to
establish remedial action plans.
If for some unexpected reason this is not the case and the CONTRACTOR becomes aware of
unexpected cost variances (where the current budget is either known to or believed to have
been exceeded), the OWNER should be notified immediately and it is recommended that all
work should be paused pending for clarification.
There are common terms to be used for controlling cost, those are:
Original Budget : A baseline budget, approved budget or control budget is
derived from CAPEX estimate with approval from OWNER.
Change/Transfer : An additional/decrease or re-allocate of cost between control
cost account.
Current Budget : A summation of Original Budget and Change/Transfer to be
Current Budget. This to be referred in cost comparistion to calculate variance
during execution.
Commitment This Period : Value of awarded services CONTRACT on EPCm
services scope, value of purchase order on materials/equipment, and the value
of signed CONTRACT for awarded SUBCONTRACTORS. This also includes
approved changes, P.O. amendment, and CONTRACT amendment occurred on
reporting period.
Commitment To Date : Cumulative value of awarded services CONTRACT on
EPCm services scope, value of purchase order on materials/equipment, and the
value of signed CONTRACT for awarded SUBCONTRACTORS. This also
includes approved changes, P.O. amendment, and CONTRACT amendment
occurred from project commence up to reporting date.
Expenditure This Period : The actual cost or spent value on services,
purchasing materials/equipment and hiring SUBCONTRACTORS occurred on
reporting period.
Expenditure To Date : The actual cost or spent value on services, purchasing
materials/equipment and hiring SUBCONTRACTORS occurred from project
commence up to reporting date.
Forecast To Complete : The estimate value to complete on each
purchasing/awarding packages.
Forecast At Complete : The estimate value at completion on each
purchasing/awarding packages. This is necessary to calculate cost variance,
cost overrun, cost underrun on each package led to total variance for overall
project.
Variance : The different value between Current Budget and Forecast At
Complete amount.
There are fundamental obligations that the CONTRACTOR must meet in regard to cost
control:
Issue No: 1 Revision No: 0 Issued on: 01/06/16 Code No: R11116010-TOSS- 10-006
Page No: 18 of Originator : CFPA/ADSC-Narongsak Approved by: ADOE
30.
General Project Control Requirements
Doc. No.: TOSS-10-006 Rev.: 0
In summary while there are a number of facets to the Cost Control process, there are three key
underlying objectives:
Ensure that the Committed Cost never exceeds the Current Budget, without
prior OWNER approval.
Regularly use an assessment of Actual Cost to date together with sound
forecasting, to accurately calculate the Forecast Final Cost, and provide early
warning of variances from budget and potential overruns.
Ensure that no cost commitments are made on the project without correct
approval and budget allocation.
The reports shall be supplemented with a brief narrative description to explain the area of
concern, issues, CONTRACTOR requirements, and other limitations obstructing the works.
Above mentioned reports are the minimum necessary documents only, the additional or
supplementary reports may be also required to provide an assessment of actual cost status.
identified prior to the meeting. Notes of the meeting shall be prepared by CONTRACTOR and
agreed by OWNER.
CONTRACTOR shall brief the overall project cost status, the content in presentation slide shall
cover topics below as a minimum.
Overall Cost Summary
Commitment Status
Summary Cost Variance shows Major Cost Saving/Overrun
Invoicing and Cashflow Status
Change Status
Recommendation Actions
CONTRACTOR shall early identify for any potential and any issues and discuss with OWNER
to agree on solutions.
Issue No: 1 Revision No: 0 Issued on: 01/06/16 Code No: R11116010-TOSS- 10-006
Page No: 20 of Originator : CFPA/ADSC-Narongsak Approved by: ADOE
30.
General Project Control Requirements
Doc. No.: TOSS-10-006 Rev.: 0
6.1 GENERAL
In order to maintain a complete check on the effect of the change on the cost involved and on
the completion time, it is necessary to introduce a uniform procedure for identifying and
controlling changes
Scope changes shall be processed following the procedure as described below. A change shall
only be effected after OWNER consent has been obtained.
A procedure shall be prepared for the handling of implementation changes and field changes.
In exceptional cases and to be the basis of a preliminary cost evaluation, it may be decided
that a change is to be performed immediately, in order not to delay activities. This instruction
shall be given in writing by OWNER. The issue of an official change in the work proposal shall
follow.
a) Scope Changes
A change in the definition of the Project which involves substantial changes of key documents,
such as process engineering flow schemes, plot plans, requisitions, forming part of the
CONTRACT.
b) Implementation Changes
Alterations to the detailed execution of the Work which do not alter the scope of the Work as
originally defined but occur normally "out of phase", e.g. a change requiring substantial
modifications of detailed engineering drawings after the detailed engineering work was
adequately completed.
c) Field Changes
A change normally proposed during the construction phase to attain easier construction, better
operation or maintenance. It may not involve changes of substances to documents but may
imply/require/necessitate extra cost and delay.
At any time during the implementation of the Work OWNER may issue a request for a change
in the work proposal. OWNER's written change in the work request will contain:
Issue No: 1 Revision No: 0 Issued on: 01/06/16 Code No: R11116010-TOSS- 10-006
Page No: 21 of Originator : CFPA/ADSC-Narongsak Approved by: ADOE
30.
General Project Control Requirements
Doc. No.: TOSS-10-006 Rev.: 0
• Request for order of magnitude estimate and the estimated effect on project timing.
• The request for order of magnitude quotations from third parties, if applicable and submission
of a "draft change in the work proposal".
Issue No: 1 Revision No: 0 Issued on: 01/06/16 Code No: R11116010-TOSS- 10-006
Page No: 22 of Originator : CFPA/ADSC-Narongsak Approved by: ADOE
30.
General Project Control Requirements
Doc. No.: TOSS-10-006 Rev.: 0
Change in the work requests, notifications, and proposals as well as approved change in the
works shall be given sequential identification numbers. Numbers assigned to rejected changes
shall not be reused.
Identify any risks, overlaps, gaps, omissions and errors in the Project Schedule
Plan and CAPEX Cost Estimate with the OWNER Project Team.
Validate the Project Schedule and CAPEX Cost based on the study
documentation performing at each project phase.
Ensure the Scope of Work for the Project and the Project Execution Plan are
represented by the Project Schedule and CAPEX Cost.
Ensure Compliance with OWNER Schedule and Cost Assurance requirement.
On projects with estimated Total CAPEX Cost is higher than 300 MTHB is required to carry out
Schedule and Cost Risk Review. CONTRACTOR shall perform and facilitate Schedule and
Cost Risk Analysis at the end of FEED/BDEP phase for projects. During Detailed Engineering
phase, the Schedule and Cost Risk Analysis shall be performed degree of engineering
development and support deliverables is enough which normally Detailed Engineering has
reached 20-30% approximately.
Issue No: 1 Revision No: 0 Issued on: 01/06/16 Code No: R11116010-TOSS- 10-006
Page No: 23 of Originator : CFPA/ADSC-Narongsak Approved by: ADOE
30.
General Project Control Requirements
Doc. No.: TOSS-10-006 Rev.: 0
Schedule Risk. The results below are minimum output required after running the Schedule
Risk Review Meeting.
8.1 GENERAL
In order to earn the benefit of valuable data after project completion, project closeout statistical
figure shall be performed in systematic pattern. It provides linkage to form the basis of
benchmarking data in term of Planning, Cost Control and Estimate. The CONTRACTOR is
required to prepare project closeout statistics data to OWNER by one month after RFSU date.
Issue No: 1 Revision No: 0 Issued on: 01/06/16 Code No: R11116010-TOSS- 10-006
Page No: 24 of Originator : CFPA/ADSC-Narongsak Approved by: ADOE
30.
General Project Control Requirements
Doc. No.: TOSS-10-006 Rev.: 0
Appendix A
Project Control Required Deliverables
Issue No: 1 Revision No: 0 Issued on: 01/06/16 Code No: R11116010-TOSS- 10-006
Page No: 25 of Originator : CFPA/ADSC-Narongsak Approved by: ADOE
30.
General Project Control Requirements
Doc. No.: TOSS-10-006 Rev.: 0
Issue No: 1 Revision No: 0 Issued on: 01/06/16 Code No: R11116010-TOSS- 10-006
Page No: 26 of Originator : CFPA/ADSC-Narongsak Approved by: ADOE
30.
General Project Control Requirements
Doc. No.: TOSS-10-006 Rev.: 0
# Deliverable List 1 mth. after contract award 3.6 # Isometric Drawing Production Status Weekly, before weekly meeting 3.6
# Requisition Index 1 mth. after contract award 3.6 # Detailed Construction Schedules 2 mths. before Construction commence 3.6
# Purchase Order Index 1 mth. after contract award 3.6 # Fabrication & Erection Production Status Weekly, before weekly meeting 3.6
# Packages Purchasing and Awarding Plan 2 mth. after contract award 3.6 # Vendor Site Visits Schedule 2 mths. before activity commence 3.6
# Equipt. and Material Delivery Plan 2 mth. after contract award 3.6 # Heavy Lift Schedule 2 mths. before activity commence 3.6
# Detailed Shut Down Schedule 2 mths. before S/D, update & report daily3.6
# Detailed Testing Schedules 2 mths. before activity commence 3.6
# Detailed System Completion Status Daily, Morning of following day 3.6
# Pre-Com./Commissioning Schedule 2 mths. before commence, 3.6
update & report daily
# Cost Control Procedure 1 mth. after contract award 2.0 # Monthly Cost Report Monthly, 7th day of each month 5.3.1 # Asset Captalized Data RFSU Date TOSS-10-003
CONTROL
# CBS 1 mth. after contract award 5.2 # Monthly Cost Presentation Monthly, 12th day of each month 5.3.2 # Project Closeout Statistics 1 mth. after RFSU 8.0
COST
(Cost Data)
# Change Management Procedure 1 mth. after contract award 2.0 # Change Register Update Weekly, before weekly meeting 5.0
CHANGE
# Schedule Risk Analysis 3 mths. after Detailed Eng. 7.1 # Schedule Risk Analysis last mth of FEED/BDEP7.1
RISK MGT.
# Cost Risk Analysis 3 mths. after Detailed Eng. 7.2 # Cost Risk Analysis last mth of FEED/BDEP7.2
Issue No: 1 Revision No: 0 Issued on: 01/06/16 Code No: R11116010-TOSS- 10-006
Page No: 27 of Originator : CFPA/ADSC-Narongsak Approved by: ADOE
30.
General Project Control Requirements
Doc. No.: TOSS-10-006 Rev.: 0
Appendix B
Project Closeout Statistics Template
Issue No: 1 Revision No: 0 Issued on: 01/06/16 Code No: R11116010-TOSS- 10-006
Page No: 28 of Originator : CFPA/ADSC-Narongsak Approved by: ADOE
30.
General Project Control Requirements
Doc. No.: TOSS-10-006 Rev.: 0
Issue No: 1 Revision No: 0 Issued on: 01/06/16 Code No: R11116010-TOSS- 10-006
Page No: 29 of Originator : CFPA/ADSC-Narongsak Approved by: ADOE
30.
General Project Control Requirements
Doc. No.: TOSS-10-006 Rev.: 0
Issue No: 1 Revision No: 0 Issued on: 01/06/16 Code No: R11116010-TOSS- 10-006
Page No: 30 of Originator : CFPA/ADSC-Narongsak Approved by: ADOE
30.