Professional Documents
Culture Documents
SAEP-14
Project Proposal
Document Responsibility: Project Management Office
Contents
Summary of Changes ................................................................................................................ 3
1 Introduction............................................................................................................................ 5
2 Conflicts and Deviations...................................................................................................... 6
3 References ............................................................................................................................ 6
5 Project Proposal Contents .................................................................................................. 9
6 Project Improvement Requirements................................................................................27
7 Reporting and Review Requirements .............................................................................28
8 Approvals and Waivers .....................................................................................................31
9 Contract Bid Package ........................................................................................................34
EXHIBIT I – Project Proposal Checklist................................................................................37
EXHIBIT II.A – SCDR Approval Form (Format) ..................................................................39
EXHIBIT II.B – SCDR’s Routing ............................................................................................40
EXHIBIT II.C – List Of Approved Scdrs ................................................................................41
EXHIBIT III – Project Proposal Approval Routing (Typical)...............................................42
Exhibit Iv – Contract Development Checklist .......................................................................43
EXHIBIT V Bid Quantification Summary Sheet ...................................................................45
Summary of Changes
Paragraph Number
Previous Revision Current Revision Change Type Technical Change(s)
2 M ay 2019 25 November 2020
Doc. Resp. M odification Changed to: PM O Standards Committee.
1.1 1.1 Clarification Clarified:
• Project Proposal (PP) roles and responsibilities shall
be per CM S-RAPID matrix.
• CM S-RAPID matrix’s required deliverables which
are subset of Project Proposal shall not be duplicated.
• Accelerated Capital Projects’ shall follow SAEP-38
requirements.
• Digital Projects requirements shall refer to SAEP-17.
8 2 M odification Affirmed addressing conflicts and deviations per SAEP-
302.
2 3 Clarification Added M SAERs cut-off-date. Also, added relevant or
removed unrelated references (added: SAEP-17, -38, -74, -
88, -134, -331 and GI-0202.305 as well as removed:
SAEP-127, -148, CM S M anuals and Saudi Aramco Cost &
Scheduling M anual).
1.5 4 Clarification Replaced FEL definition with its parent system, the
“Capital M anagement System” and elaborated definition of
“Construction Agency”, Project Leader & Project M anager
etc.
3.2.2 5.2.2 M odification/ Added requirements for:
Addition • Detailed Site Investigation (underground and above
ground including modification/demolition for
brownfield projects [5.2.2.8/9]
• Project shutdown window considerations (OSPAS
endorsed/approved) [5.2.2.10]
• Work permit plan [5.2.2.17]
• Technology Selection Report (see section 5.2.14)
[5.2.2.24]
• Creation/maintenance of Plant Functional Locations
[5.2.2.36]
3.2.3.B/C 5.3.3.B/C M odification For Scope Change from DBSP Requests (SCDRs), added
requirements for:
• PM OD’s review of schedule for all and estimate if
SCDR relates to Offshore work or exceeds 2% of
archived Budget Estimate value.
• Scope development while considering Shutdown,
Construability requirements etc.
3.2.6. 5.2.6 M odification Under required Studies and Assessments:
• Deleted redundant roles for BRA as those are covered
in CM S-RAPID matrix per SAEP-17. [5.2.6.3]
• Added requirement isolation philosophy document
[5.2.6.5]
• Added new requirements for Electrical Systems
Design and Analysis (ESD&A) per SAES-P-100 to
assure that the design basis for the project is firmly
established. [5.2.6.6]
3.2.14 5.2.14 Addition Added new requirements for Technical Selection Report
per SAEP-74.
3.4.1 5.4.1 Clarification Deleted redundant scheduling requirement and referred to
SAEP-331.
3.6 5.6 Addition Added new requirement for Creation/M aintenance of Plant
Functional Locations in accordance with GI-202.305.
3.8 and 5.4.1 5.8 and 7.4.1 Deletion Deleted obsoleted requirement of:
• Obtaining ASC TPP Series (Numbers assigned by the
Technical Services Dept/Engineering Unit, Houston).
[5.8]
• Distributing and Storing Approved Project Proposals
at ASC. [7.4.1]
4 6 Clarification For Project Improvement Requirements (VIPs),
Benchmarking, Target Setting, M arket Outlook Study,
Energy Optimization Study, Corrosion M anagement
Program, etc.) referenced relevant M SAERs.
5 7 Clarification Added Project Proposal (PP) reviews requirements i.e.,
number of reviews and their timing as well as the system.
6.1.1 8.1.1 M odification Added approval requirement from M anager, Information
Technology (IT) Engineering Department (for all projects
involving IT and Communications)
6.2.2 8.2.2 Clarification Clarified PP waiver approval roles for C1 projects.
7.0 9.0 Clarification Clarified that IFB Package design notes shall not be
utilized to add or delete scope for the LSTK or EPC
Contractor.
M isc. M isc. M odification Incorporated editorial changes resulted from above in the
whole procedure and Exhibits.
1 Introduction
This procedure outlines the requirements for preparing the Project Proposal. The procedure
is not intended to give instructions on the engineering effort, but to cover requirements that
are important during the FEL3 Project Proposal phase. In summary, it covers:
The intent of the checklist(s) is to ensure compliance with key requirements. They are
not intended to cover all detailed requirements of this procedure.
Notes:
1. Unless specified elsewhere in this procedure, for stak eholders’ roles and
responsibilities related to Project Proposal (PP) and its required Capital Management
System (CMS) deliverables as well as their issuance timing, please refer to CMS-
RAPID matrix.
2. To fulfill requirements of respective PP’s contents and to avoid duplicate efforts, once
FEL3 PP phase related CMS-RAPID’s required deliverables are prepared and
approved, those shall be included in the PP as appendices.
4. For requirements and responsibilities regarding Digital Capital Projects, refer to SAEP -
17.
1.1 Definition
1.2 Purpose
Project Proposals must be completed and approved in time before the 56D
submission deadline in order to support the Expenditure Request Approval
(ERA).
1.4 Application
Saudi Aramco requires a Project Proposal for all Type A, B, C and C1 projects
(for project characterization, refer to SAEP-17).
Any conflicts between this document and other applicable Mandatory Saudi Aramco
Engineering Requirements (MSAERs) shall be addressed in writing to the EK&RD
Coordinator.
Any deviation from the requirements herein shall follow internal Company procedure
SAEP-302, Waiver of a Mandatory Saudi Aramco Engineering Requirement.
3 References
The editions of the MSAERs which are in effect on the project’s standards cut-off
date are applicable to this procedure. Saudi Aramco References:
4 Important Terms
1) Capital Management System (CMS) is the general framework adopted by Saudi
Aramco for managing project activities, clarifying stakeholders’ roles and
responsibilities, and enabling timely and informed decision making for Capital
Projects. CMS manages the Front-End Loading (FEL) of capital projects through a
Stage Gate. Wherein, RAPID (Recommend, Agree, Perform, Input, Decide)
matrix defines roles and responsibilities in the work process related to the CMS and
development of FEL deliverables in each Stage Process. For more details, refer to
SAEP-17.
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. This list may be optimized by the IPT
based on the Project Type & Sub Type:
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 proposal phase.
The ORP is a document that defines how the project will transition
into an operating facility and will describe what “operational-type”
steps must be tak en along the project planning and execution path
to have a flawless startup and initial operations. The ORP also
highlights and describes activities and resources aiming to ensure
the optimization of Operations and Maintenance activities over the
facility lifetime (starting after handover).
27) List of items exceeding (over-specification) Saudi Aramco
standards’ minimum requirements (see, Section 5.2.13)
28) Requesting/returning of drawings/tag numbers per SAEP-334
29) Identifying Operating Instructions for New Facilities and Project
Records requirements (see SAEP-121 and SAEP-122)
30) Compliance with security and control of Engineering Data
requirements (see SAEP-134)
31) Compliance with Value Assurance (VA) requirements (see SAEP-40)
32) Compliance with Value Improving Practices (VIPs) requirements
(see SAEP-367)
33) Compliance with Project Closeout Report requirements
(see SAEP-329)
For all projects scope shall be considered frozen on the date of approved
DBSP available at the approval of FEL2 Gate. Scope changes after
DBSP approval shall be avoided.
Note: The above shall be facilitated by ensuring the DBSP approval includes
all approvers’ commitment to eliminate scope changes after DBSP
approval.
etc. All other deliverables which are part of the Value Assurance
Review Plan shall be updated in accordance with the approved
SCDR and shared with PMOD.
D) Recording of Scope Change
All approved SCDRs shall be included in the Project Proposal and
ER Estimate Packages. The required documentation shall include
the summary list included in Exhibit II.c and all supporting
documents required for SCDR approval. The complete summary
list shall be included in the Project Proposal approval package as
indicated in Section 6.1.1.
Any cost impact as a result of the studies must be identified and included
in the ER Estimate package.
The impact of changes on the project shall be reviewed by the IPT and
other stakeholders to determine applicability and extent of
implementation. Only changes approved by the Project Manager and
concurred by the Project Sponsor shall be implemented to the project.
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, 3D CAD and
other necessary drawings that are required to establish the design basis
and assist in producing an ER quality estimate.
Project Manager shall also ensure that the specific requirements for
inspection are included in Schedule “Q” for all applicable contracts.
All projects shall adhere to security measures and controls for all
systems and solutions, including process automation systems, to comply
with security requirements in line with IPSAG and SAEP-99.
Note: IT/ICS Security Architecture Assessment (initial) for is completed
during the FEL2 DBSP phase (see, CMS-RAPID matrix).
At the end of the FEL3 Project Proposal phase and subsequent phases,
progressive Project Closeout Reports are to be submitted by the Project
Manager (see SAEP-329). Therefore, it is recommended that SAPMT
includes the requirements in the Project Proposal contract and in the
contract(s) for later phases of the project to ensure that the requisite
information is provided by the contractor(s).
The report(s) shall be included in the Project Proposal package and shall
also be distributed to the Project Sponsor and PMOD.
5.3.1 General
The purchase order transferred to the Contractor will cover the complete
scope involving engineering and manufacture. Use of novated purchase
orders should be approved as per Supply Chain Management Manual
(Volume I: Saudi Aramco Procurement Manual (see, Section relevant to
Services Review Committee “SRC”).
Novated purchase order terms and conditions shall include all relevant
contract Schedule Q requirements related to material procurement and
manufacturing activities to ensure a smooth transition from the FEED
contractor to the project contractor.
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.
For LSTK and LSPB contracts, start-up spares responsibility for “free
issue” equipment provided by Saudi Aramco shall be stated clearly in the
contract.
SAPMT and the respective Contractors are responsible for the spare
parts information as outlined under SAEP-31. In all cases, the
© Saudi Arabian Oil Company, 2021 Page 24 of 47
any details that may assist Proponent in preparation of the TRS. The Proponent
will provide the completed TRS to the Training & Development’s Early BI
Training Planning Team (EBTP) to complete a Training Impact Assessment
(TIA). If training is to be required, EBTP shall submit TIA’s Knowledge &
Skills Matrix’ (KSM) data to SAPMT for inclusion in the Project Proposal, in
accordance with SAEP-140. SAPMT is responsible for incorporating the
findings of the Training Impact Assessment in the final 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:
• Providing the vendor training plans and quotes for the equipment identified
for training to the EBTP team for analysis. After the initial analysis of the
vendor training plans and quotes, the EBTP team will provide training
recommendations to SAPMT for considerations during the vendor selection
process.
After vendors have been selected, SAPMT will provide the EBTP team a list of
the specific equipment required for training, general vendor data information,
training scope, cost and schedule required for training prior to commissioning.
Creation/maintenance of the this Master data at project proposal stage will also
enable the integration, and ensure compliance & completeness of asset records
in the following Enterprise Project Management (EPM) business processes:
• MPCS+.
5.7 Appendix
The Appendix shall include letters, minutes, land use permits and other pertinent
documents written during Project Proposal development.
All Project Proposals’ cover sheet shall carry the APP Series (Numbers assigned
by the Saudi Aramco’s Technical Information Center, Dhahran).
This section consists of practices/studies that when implemented would optimize project
cost, schedule & quality and enhance the efficiency of project planning and execution.
Budgeting for conducting value practices is included in the Preliminary Engineering
funds.
6.2 Benchmarking
The purpose of this study is to render optimized process and utility capital as
well as the efficient use of thermal and electrical energy. Per CMS-RAPID
matrix (see, SAEP-17), Energy Optimization studies are completed and reports
are issued during the FEL stages. For further details, refer to SAEP-367.
7.1 Project Proposal Reviews and Distribution for Review and Meetings
The IPT Leader (SAPMT’s Project Manager) and Proponent (Senior Operations
Representative) 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.;
- Refining & NGL Fractionation
- Northern Area Oil Operations
- Southern Area Oil Operations
- Pipeline, Distribution & Terminals
- Gas Operations
- Petroleum Engineering and Development (for production-related projects)
General Management:
- Industrial Security Operations
- Proponent organization
- Environmental Protection (EP)
Management:
- Oil Supply Planning and Scheduling Department
(for all proposals related in any way to hydrocarbon products movement and
handling)
- Information Technology Engineering Department
(for all projects involving IT and Communications)
- Projects Procurement Department
- Transportation & Equipment Services Department
- Power Systems Engineering 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)
- Facilities Planning Department (mandatory)
- Consulting Services Department
- Inspection Department
- Process & Control Systems Department
- Industrial Security Support Department
- Loss Prevention Department
- Fire Protection Department
- Project Management Office Department (for Value Assurance Reviews)
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 changes from the
DBSP/Project Proposal as originally prepared. Refer to Section 5.2.3 for
definition of scope change and its approval process.
The subject of critical plant equipment unit spares (capital spares) per Section 5.3.4
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.
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, with the concurrence of the
Proponent and FPD. In this case, the reviewing organizations should send
personnel authorized to make decisions to attend the meeting. 7.4 Distribution
and Storage of Approved Project Proposals
Following the approval of the Project Proposal, SAPMT (Project Manager) shall
send copies of the approved Project Proposal to:
- Facilities Planning Department (FPD) - one electronic copy and one hard
copy, to be used as a “working” document for five years or for the duration
of the project, whichever is longer.
- Technical Information Center (TIC) - one electronic copy for archival
purpose.
- Project Management Office Department (PMOD) - one electronic copy, for
Estimating Services’ use and record.
The electronics file submissions shall contain an index at the beginning of each
file medium to facilitate retrieval of stored data. The electronic text,
spreadsheet, and graphical data shall be in native format, and drawings shall be
in accordance with Saudi Aramco standards and formats. Scanned documents
shall be in accordance with the corporate standard maintained by
EK&RD/Drawing Management Unit.
8.1.1 Approvals
6) List of scope changes from the approved DBSP (see Exhibit II.c),
and
7) Other applicable documents (up to four numbers).
For a project with an approved Project Proposal which has not yet
received Expenditure Request (ER) approval, scope change(s) shall be as
per Section 5.2.3.
8.2.1 Request
8.2.2 Approval
Head, if Department Manager does not exist) shall prepare a formal letter
(concurred by the Project Sponsor) requesting approval to carry out
detailed design during Project Proposal. The letter shall be addressed to
Executive Heads of the Construction Agency, and Proponent
organization (for C1 projects this may be a same person). The letter
should state the present situation, scope of work, justification for the
waiver and identify what project proposal requirements, if any that will
be performed during detailed design. Approval is accomplished once
request is accepted and signed by the addressees.
Note: The Construction Agency shall communicate approved waivers to
PMOD (see SAEP-17).
As applicable, the Contract Bid Package will be developed in close coordination with
the Contracting Department. For guidance, refer to Contract Development Checklist
(Exhibit IV), for key activities in developing Contract Bid Package.
A complete Contract Bid Package shall be prepared in accordance with Supply Chain
Manual (SCM) and may contain the following:
Issue for Bid (IFB) package typically includes drawings, specifications, applicable
reports, and other relevant documents necessary to define the project requirements and
clearly describes the contract scope of work. SAPMT shall 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.
Note: The IFB Pack age design notes shall not be utilized to add or delete scope for the
LSTK or EPC Contractor.
The following sections in the Project Proposal package shall be reviewed carefully to
determine if they are applicable for inclusion in the bid package. If they are to be
included, SAPMT shall modify as required to ensure that Contractor’s scope of work is
clearly defined in the “Issue for Bid” Package:
© Saudi Arabian Oil Company, 2021 Page 34 of 47
• Project Schedule
• Training requirements
• Land Permits
• Operating Variables and project shutdown window (as required by OSPAS)
• Strategy for projects compliance with quality requirements
• Project- Risk Management Plan, Risk Assessment Report and Risk Register
• Temporary construction and communications
Document History
25 November 2020 Major revision.
21 February 2021 Editorial Revision to remove cancelled reference SAEP-72
EXHIBITS
TABLE OF CONTENTS
Complied Remarks
Ref.
Item Description (Justification of non-
Section (Yes/No)
compliance)
INITIATOR
SAPMT (Construction Agency) ------------------------------------- Date: --------------------
Yes No
PROJECT LEADER (Facilities Planning Department “FPD”)
Scope change related to original scope and project intent
Scope change relates to offshore work or it is greater than +/- 2% (for A, B and C Yes No
projects) and +/- 5% (for C1 projects) of archived budget estimate value (SAPMT):
PMOD REPRESENTATIVES: Indicate cost and schedule impacts, if different than above.
FPD evaluates SCDR and determines if change is related to Project’s original scope &
intent?
PMOD reviews schedule for all scope changes and estimate, if scope change relates to offshore
work or it is greater than +/- 2% (for A, B and C projects) and +/- 5% (for C1 projects) of archived
budget estimate value
No
Should scope change be STOP
processed? Return SCDR-
Form to Initiator
Yes
STOP
Project Sponsor approves SCDR Don’t process
No scope change
Yes
FPD provides approved SCDR and DBSP addendum/amendment to SAPMT and a copy to
PMOD, within 2-weeks of SCDR approval by the Project Sponsor
IPT implements approved Scope Change into the Project’s scope, cost and schedule
SAPMT maintains all records and include approved SCDRs and their consolidated list in
Project Proposal package, Project Proposal Approval package and ER Estimate package.
Note: For CMS compliant projects, SAPMT shall add Project Sponsor (PS) as Project Proposal approver before
VP/ED of the Construction Agency.
Ensure that the Contract is structured correctly (for lump sum, three
13 items – lump sum price, change orders, and other expenditures; and
use of value “VAL” with the amount in the “quantity” column).
PROJECT TITLE : BI :
CONTRACT NUMBER : JO :
CONTRACT 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
TOTAL DEMOLITION WORST L $ $
(SCA 007)
SITE PREPARATION /
DEVELOPMENT
(PLOT SIZE) SM $ $
CONCRETE CM $ $
CIVIL / STRUCTURE
(SCA 200 & 400) FENCE LM $ $
ACTIVITY IN MONTH(S)
DETAIL DESIGN DURATION
SCHEDULING
CONSTRUCTION DURATION
EQUIPMENT WITH MORE THAN 6 MONTHS LEAD-TIME
DELIVERY