Professional Documents
Culture Documents
Saep 14
Saep 14
Saep 14
1 Introduction………………………………......... 2
2 Applicable Reference Documents……..….… 3
3 Proposal Contents and ER Estimate……...... 5
4 Project Improvement Effort……………….… 22
5 Reporting and Review Requirements…....... 27
6 Approvals and Waivers…………………....... 30
7 Contract Bid Package…………………….…. 33
8 Exhibits……………………………………...... 34
1 Introduction
This procedure outlines the requirements for preparing the Project Proposal and
Expenditure Request (ER) Estimate package. The procedure is not intended to give
instructions on the engineering effort, but to cover requirements that are important
during the Project Proposal process. In summary it covers:
Engineering specifications, standards and selected design requirements
Quality, cost reduction and schedule improvement techniques, i.e., benchmarking,
value engineering and value practices
Project Proposal reporting, review, approval & waiver requirements
ER Estimate preparation requirements
Project Proposal, ER Estimate Package & Contract Development Checklists
Contract Bid Packages
The intent of the checklists is to insure compliance with key requirements. They are not
intended to cover all detailed requirements of this procedure.
1.1 Definition
1.2 Purpose
The Project Proposal documents the agreement on, and commitment to, the
project scope, the project cost and design basis by the Saudi Aramco Project
Management Team (SAPMT), Facilities Planning Department, Project Support
& Controls Department, Proponent and other technical support groups. This is
accomplished through careful evaluation of the project objectives during Project
Proposal preparation to ensure the optimum results. The Project Proposal
establishes the basis for Expenditure Request (ER) funding and is the baseline
from which all subsequently considered scope changes are measured.
Page 2 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
1.4 Application
Page 3 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
General Instructions
GI-0005.002 Loss Prevention Policy Implementation
GI-0020.500 Expenditure Control – Expenditure Request
Forms
GI-0020.520 Project Change Request
GI-0202.309 Allocation of Costs – New Facilities Start-up
GI-0202.451 Engineering Work Order Authorization for
Preliminary Engineering Preparation
GI-0400.001 Quality Management Roles & Responsibilities
Page 4 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
The following sections outline the items normally included in Project Proposals.
This section provides scope and design information that establishes the
performance specifications for the facilities, process, waivers or
limitations. It shall address details concerning the design basis, proposed
facilities including equipment design, capacities, location/layouts and
other project related information. The list below provides common
elements found in a typical scope.
1) Facility/plant layout and location
Note: The project scope boundaries and interfaces with other related
facilities must be clarified prior to developing the scope of the
project in the project proposal phase.
Page 5 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
Page 6 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
Page 7 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
Page 8 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
Page 9 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
Page 10 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
This section provides a list and copies of the drawings that define the
scope of the project. It shall include key drawings such as PFDs, P&IDs,
plant and equipment layouts, electrical one-line diagrams and other
necessary drawings that are required to establish the design basis and
assist in producing an ER quality estimate.
3.3.1 General
Page 11 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
The purchase order transferred to the LSTK Contractor will cover the
complete scope involving engineering and manufacture. Use of novated
purchase orders should be approved by Services Review Committee
(SRC) either as part of the contracting plan or as an individual item.
The materials source list identifies major equipment and material items.
Where possible, an estimated dollar value and quantity required shall be
indicated. Also indicate responsibility for inspection, expediting, traffic
and transportation. The Project Proposal effort shall develop Quotation
Requests (QRs) for major engineered equipment and critical items, and
issue these QRs to vendors on a “For Development Only” basis to
determine prices and delivery schedules. For purpose of preparing the
ER Estimate, the major equipment list shall include account number, the
item number, a brief description, the data sheet, a requisition number if
available, the estimated value and other pertinent information. The
following areas shall be segregated:
Page 12 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
The Surplus Inventory and the Excess Cataloged Materials Listings shall
be reviewed to prepare the listing and estimated values of possible
surplus and excess usage. During the Project Proposal development, this
list shall be further refined to set the target values for use-up of those
items that shall be reported during the life of the project. LSTK or LSPB
contracts shall use the same format and shall estimate total commodity
(9CAT) and engineered (9COM) material costs (regardless of originator)
as the basis for determining use-up values. The target values are goals
requiring extra effort to achieve rather than just a restatement of the
original major items listed in section 3.3.2.
A list of proposed installed spares for critical plant unit equipment and a
list of non-installed capital spares proposed for entry into Saudi Aramco
stores custody shall be provided along with the estimated cost for each
item and justification for purchase. Comparison shall be made between
spares specified in the Design Basis Scoping Paper and spares specified
in the Project Proposal.
Page 13 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
SAPMT and the respective Contractors are responsible for the spare
parts as outlined under SAEP-31. In all cases, the SAPMT/Contractors
shall provide complete and accurate spare parts data packages necessary
to support Saudi Aramco procurement of operating spare parts.
This section contains a Level III project summary schedule that shall be
developed during the Proposal phase based on information from the
Project Milestone Schedule, WER Schedule and other data as they
become available during the DBSP and Project Proposal.
Page 14 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
Project Summary Schedule addresses all the project life cycle activities
in a summary format. It must be logic driven, based on the Critical Path
Method (CPM). The Schedule should contain sufficient detail to show
potential material or equipment “novation”, long lead items, contract
procurement activities, detailed engineering by discipline leading to
major deliverables, mobilization, early works, shutdown, tie-ins, testing,
loop checks, pre-commissioning, start-up, interface with Proponent and
other projects.
The schedule shall form the basis for the original (Rev.0) Project
Completion Schedule (PCS). The Project Summary Schedule further
expands the level of detail while still supporting critical and key
milestone dates defined and prescribed in the contract (Schedule “B”).
Project Summary Schedule is expanded to include critical milestone
dates as well as any other key milestones that are provided by
Contractors. If “novation” material and equipment is included in the
execution plan, the date of purchase order and required delivery date
should be incorporated in the schedule. The schedule shall include
review time requirements specified in SAEP-303 (Engineering Reviews
of Project and Detail Design Engineering Documentation). Contact
Scheduling Engineering Group of PS&CD/PCED for more detailed
information on Project Summary Schedule.
Page 15 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
Minimum one (1) week prior to the review meeting, SAPMT shall
provide a complete set (hardcopy and electronic file) of the ER
Estimate with support documents to PS&CD for review.
Page 16 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
Page 17 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
SAPMT shall prepare and provide all attendees with a complete list
of accepted scope changes and relevant supported documents for
the Scope Compliance Review meetings. PS&CD shall be
responsible for validation of cost and schedule impacts for all
scope changes.
Page 18 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
Page 19 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
Package Checklist.
3.5 Appendix
The Appendix shall include letters, minutes, land use permits and other pertinent
Page 20 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
SAPMT may also be required to implement the findings of the Training Impact
Assessment as included in the approved Project Proposal. These may include:
Page 21 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
This section comprises of activities that on implementation would optimize project cost &
schedule, improve quality of the Project Proposal and assure project execution success.
Page 22 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
The status and resolution of all accepted and pending VE proposals shall
be documented in the Value Engineering Section of the Project Proposal.
4.2 Benchmarking
Page 23 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
The analysis starts as early as the study phase and DBSP, or at any
appropriate stage of the Project Proposal development, but no later than
90% Project Proposal progress, comparing key parameters of the project
with an external industry-wide database. The analysis would address
key project outcomes and associated risk based on the Project Proposal
effort to date. As a minimum, the following areas should be addressed
and compared to industry norms, the Gulf Region and Best in Class:
Status of front-end loading (FEL), i.e., project definition, at the time
the benchmark analysis is prepared
Use of value improvement practices
The projected total installed cost (TIC) of the project
An analysis of the contingency requirement based on project scope
and FEL
Engineering as a percentage of TIC
Time required for total project execution (ERA through Onstream)
Time required for the construction phase
Expected time required for start-up
Long lead material deliveries comparison
General or specific requirements included in the Project Proposal
Scope of Work that are non- industry standards
Execution strategies
Page 24 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
For purposes of the energy study, an industrial process is defined as one that
includes fired heaters, boilers, pumps, compressors, steam turbines, or gas
turbines. Non-industrial facilities such as buildings, roads, warehouses, storage
depots, and non-process operations such as IT or instrumentation upgrades are
excluded.
The technical approach and work scope for the energy study should address one
or more of the following issues:
Process Integration, using Pinch Analysis techniques
Equipment Load Management policies
Adjustable Speed Drives
Driver Selection
4.3.4 Rotating machinery with individual power loads of 5000 HP and higher
shall be evaluated for selection of optimum driver type – electric motor,
steam turbine, or gas turbine.
Page 25 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
The optimum time to conduct such a study is the earliest possible date after
preliminary PFDs, including heat and material balances, are available, and the
plant fuel/power consumption estimates have been determined. Generally, this
would be after 30% completion of the Project Proposal, but no later than 60%
Project Proposal completion.
The full energy optimization study report, including all supporting data and
calculations, must be submitted to the Energy Systems Unit of Consulting
Services Department for review.
SAPMT shall implement applicable Saudi Aramco and other industry value
practices during Project Proposal development to optimize project planning and
execution. PS&CD/CPOD is available to assist SAPMT in selecting the
appropriate value practices and facilitating their implementation.
The following value practices have shown proven payback for Saudi Aramco
projects.
Constructability
Page 26 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
Extensive set of tools and techniques used by all Project Stakeholders, PMT,
Proponent, Contractors, etc., to help facilitate a successful facility start-up
and stable long term operation.
Scope Control & Change Management
PS&CD will identify and implement other value practices that become
available between revisions of SAEP-14 that offer value improvement to the
project.
The E-Review electronic review system is the Company’s standard method for
review of engineering drawings and documents. SAPMT should submit review
Page 27 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
The SAPMT and proponent are responsible for determining the recipients. As a
minimum, the following represents a list of various organizations that shall be
considered for receipt of the Project Proposal. However, only those
organizations with direct involvement shall receive the Project Proposal.
Executive Management:
- Proponent Organizations, i.e.
Ras Tanura Refining
Northern Area Producing
Southern Area Producing
Jeddah/Riyadh Refining
Yanbu Refining
Distribution Operations
Abqaiq Plants & Pipelines
Gas Operations
Medical Services
Employee Relations
- Petroleum Engineering and Development
(for production-related projects)
General Management:
- Industrial Security Operations
- Proponent organization
Management:
- Oil Supply Planning and Scheduling Department
(for all proposals related in any way to oil, gas, NGL and/or refined product
movement and handling)
- Computer & Communications Engineering Department
(for all projects involving communications)
- Purchasing Department
- Power Distribution Department
(for all projects related to power facilities at 2.4 kV and above)
- Abqaiq, Dhahran or Ras Tanura Utilities Department
(for the area community projects only)
Page 28 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
The Technical Review Meeting shall be held no sooner than ten (10) working
days after distribution of the Project Proposal for review. Location, date, and
time of the meeting shall be announced in the cover letter distributed with the
Project Proposal. The Technical Review Meeting shall discuss all technical
aspects of the Project Proposal, resolve technical questions, address
environmental issues and review the Project Summary Schedule. Interim
technical review meetings shall be conducted as required by SAPMT depending
upon the type and complexity of the project. Items not resolved at the final
technical review meeting shall be addressed in the Project Proposal Meeting.
Substantive changes resulting from the technical review meeting shall be
incorporated as appropriate into the Project Proposal documents.
SAPMT shall prepare minutes of the Technical Review Meetings and distribute
the minutes, electronically whenever possible, to all persons who either received
the Project Proposal or attended the Technical Review Meeting. The minutes
shall include the estimated cost and schedule effects of major changes from the
DBSP/Project Proposal as originally prepared. Refer to 3.2.3 for definition of
major scope change.
The subject of critical plant equipment unit spares (capital spares) per section
3.3.5 shall be addressed, and proposed purchases shall be reviewed.
The purpose of the Project Proposal Meeting is to resolve any outstanding items
remaining after the Technical Review Meeting and to finalize the project scope.
The Project Proposal Meeting shall be scheduled no sooner than five (5)
working days after distribution of the minutes of the Technical Review Meeting.
Page 29 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
SAPMT shall be responsible for preparing and distributing the minutes of the
Project Proposal Meeting to those persons who either received a copy of the
Project Proposal or attended the Project Proposal Meetings.
For selected small projects, the Technical Review and Project Proposal
Meetings can be combined into one meeting if concurred by Proponent and
FPD. In this case, the reviewing organizations should send personnel authorized
to make decisions to attend the meeting.
Following the approval of the Project Proposal, a final approved copy shall be
distributed as follows:
5.4.1 ASC
Page 30 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
6.1.1 Approvals
The Project Proposal minutes shall show the estimated cost and schedule
effects of any changes from the DBSP/Project Proposal as originally
prepared.
Page 31 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
For a project with an approved Project Proposal which has not yet
received Expenditure Request (ER) approval, scope changes shall be as
follows:
SAPMT will document and estimate all scope changes approved by
FPD and submit the revised ER estimate to PS&CD as an addendum
to the approved Project Proposal
The proposed change in the meeting minutes or an addendum shall
include justification and the cost/schedule impact
The required minimal approval authority for the proposed change is
Project Manager level
SAPMT shall distribute the approved changes to PS&CD and all
those that received the original Project Proposal
6.2.1 Request
6.2.2 Approval
Page 32 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
The Contract Bid Package will be developed in close coordination with the Contracting
Department. Refer to Exhibit III, Contract Development Checklist, for key activities in
developing Contract Bid Package.
Issue for Bid package (normally prepared by Engineering Contractor) which includes,
but is not limited to, drawings, specifications, applicable reports, and other relevant
documents necessary to define the project requirements and clearly describes the
contract scope of work. SAPMT should take into consideration the current project
execution plan and responsibilities of all contractual parties when revising the Project
Proposal package to “Issue for Bid” Package.
Page 33 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
Land Permits
Operating Variables (as required by OSPAS)
Strategy for projects compliance with quality requirements
Project Risk Assessment
Temporary construction and communications
8 Exhibits
The intent of the checklists is to facilitate the review and ensure all key requirements
are considered, but not to cover all detailed requirements as stated in this procedure.
Revision Summary
28 June 2000 Major revision.
29 January 2003 Editorial revisions.
15 August 2006 Major revision.
20 September 2006 Editorial revision to paragraph 3.7.
18 January 2009 Editorial revisions.
Page 34 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
EXHIBITS
TABLE OF CONTENTS
Page 35 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
Ref.
Item Section Description Included
Page 36 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
Ref.
Item Section Description Included
1. Constructability Study
3. Lesson Learned
5. Schedule Optimization
Page 37 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
Control system (DCS) scope with I/O counts, Block Flow Diagrams and Vendor
10
Quotations
15 DC Surplus, etc,
Page 38 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
23 Exploratory Trenching
35 Recent (valid for 3 months) quotations for major equipment & material
Page 39 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
Following are the list of key activities for developing the contract package.
Contracting Strategy
Enter and maintain data on all contract action covered by the Contracting
2 Strategy in to the PMIS Contracting Action Development and Administration
(CADA) module.
Secure approvals for all singe source procurement and included appropriate
4
language in Schedule “H.”
Complete Schedule “Q” language in accordance with approved Quality Plan (GI
5
400.001) and review proposed language with Inspection as needed.
8
Include requirements for bidder price breakdowns as part of the Commercial
Proposals and quantity lists as part of the Technical Proposals.
Prepare, in conjunction with other members of the Bid Review Team, data to be
10
used for allowed bid conditioner (e.g., different PMT cost for various locations).
Page 40 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
Review of Contract and Contract Supplement as Part of the Bid Review Team
Ensure the Contract is structured correctly for SAP SRV releases (for lump
11 sum, three items – lump sum price, change orders, and other expenditures; and
use of “VAL” with the amount in the “quantity” column).
Ensure that that AEL includes reasonable amounts for all applicable “Other
Expenditures” (e.g., incidental services, Saudi manufacturer equalization, stand-
12
by time, reimbursable start-up and commissioning assistance, variations from
target quantities, etc.).
After award of the contract, provide copies of the bidders’ price breakdowns
14
and quantity lists to PS&CD.
Note: For a project using an LSTK contracting strategy, these actions are required during or just after the Project
Proposal period. For other strategies (e.g., GES + LSPB) some of the activities take place at later stages of
the project.
Page 41 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
UNIT
AREA NAME PARAMETER UOM QUANTITY COST COST
Page 42 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
CRUDE
STABILIZATION UNIT CAPACITY MBD $ $
COGENERATION
FACILITY ISO RATING MW $ $
SITE PREPARATION SM $ $
CONCRETE CM $ $
STRUCTURAL STEEL TONS $ $
FENCING LM $ $
Page 43 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
Page 44 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
VALUE
LIST OF VALUE PRACTICES IMPLEMENTED
PRACTICES
Page 45 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
PROJECT TITLE : BI :
CONTRACT
NUMBER : JO :
CONRTACT TYPE :
:
SUMMARY OF COST
BY WORK BREAKDOWN STRUCTURE (WBS)
BULK
AREA OF WORK ENGINEERING CONSTRUCTION TOTALS
MATERIALS
AREA OF WORK 1 $ $ $ $
AREA OF WORK 2 $ $ $ $
AREA OF WORK 3 $ $ $ $
AREA OF WORK 4 $ $ $ $
TOTAL PROJECT COST $ $ $ $
DEMOLITION
(SCA 007)
TOTAL DEMOLITION WORK COST LUMPSUM $ $
SITE PREPARATION /
DEVELOPMENT
(PLOT SIZE) SM $ $
CONCRETE CM $ $
Page 46 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
LENGTH OF PIPERACK LM $ $
TONNAGE CARBON STEEL
(PIPERACK) TONS $ $
UNDERGROUND CARBON STEEL
PIPING PIPING LM $ $
(SCA 600) ABOVEGROUND CARBON STEEL
PIPING LM $ $
TONNAGE CARBON STEEL PIPES TONS $ $
TOTAL PIPING MANHOURS &
COST MHRS $ $
Page 47 of 48
Document Responsibility: Project Support and Controls Dept. SAEP-14
Issue Date: 18 January 2009
Next Planned Update: 15 August 2011 Project Proposal
ACTIVITY IN MONTH(S)
DETAIL DESIGN DURATION
SCHEDULING
CONSTRUCTION DURATION
EQUIPMENT WITH MORE THAN 6 MONTHS LEAD-TIME
DELIVERY
Page 48 of 48