Saep 367
Saep 367
SAEP-367
Value Improving Practices
Document Responsibility: Project Management Office Standards Committee
Contents
SUMMARY OF CHANGES ..................................................................................................................................... 4
1 SCOPE ......................................................................................................................................................... 6
3 REFERENCES ................................................................................................................................................ 7
3.1 SAUDI ARAMCO REFERENCES ............................................................................................................................. 7
4 TERMINOLOGY ............................................................................................................................................ 7
13 RESPONSIBILITIES .................................................................................................................................. 38
13.1 PMOD........................................................................................................................................................ 38
13.2 IPT LEADER .................................................................................................................................................. 38
13.3 VIPS FACILITATORS ........................................................................................................................................ 40
13.4 OTHER DEPARTMENTS (INCLUDING PROPONENTS) ............................................................................................... 40
APPENDIX A - OPTIMUM IMPLEMENTATION TIMING FOR VIPS AND SUMMARY OF VIPS CRITERIA.................. 42
Summary of Changes
Paragraph Number Change Type
(Addition, Modification, Deletion, Technical Change(s)
New)
Previous Revision Current Revision
(03 May 2020) (22 December 2021)
Cover page Cover page Deletion Deleted reference to
procedure for non-CMS
projects.
3 3 Modification Included reference to
standards cut-off date per
SAEP-14
3.1 3.1 Deletion Removed references not
included in the body, added
required references
6.3 6.3 Clarification Clarified approved facilitator
requirements.
6.3 6.3 Addition Added requirement for
workshop feedback, new
reporting requirements (VIPIT)
and IPT Leader approval of
VIP deliverables.
7 7 Clarification Clarified approved facilitator
requirements.
7.2/7.3 7.2/7/3 Addition Added 30-day planning
requirement for DBSP and PP
VE.
7.4 7.4 Addition Added requirements for
Project Technical Package
brownfield Constructability.
7.5 7.5 Addition Added requirement for P&CSD
and CSD to review VE
proposals, as applicable.
7.6 7.6 Addition Added requirements for VE
Idea Log and justification
requirement for rejected high-
value VE proposals.
8.1 8.1 Clarification Embedded SCDR into PP&TA.
1 Scope
This procedure outlines the requirements of Value Improving Practices (VIPs)
during project planning and execution phases. The procedure is not intended to
give instructions on the engineering effort, but covers requirements for VIPs that
are applicable during FEL1/Business Case, FEL2/Study, FEL2/DBSP,
FEL3/Project Proposal, Detailed Design, and Construction phases. This
procedure is applicable only to projects using the new Capital Management
System (CMS). VIP requirements include:
• Best Practices (BP) regarding project cost, schedule and quality improving
techniques, during FEL2/DBSP, FEL3/Project Proposal, Detailed Design,
and Construction phases.
Any conflicts between this document and other applicable Mandatory Saudi
Aramco Engineering Requirements (MSAERs) shall be addressed to the
EK&RD Coordinator.
Any deviation from the requirements herein shall follow internal company
procedure SAEP-302.
3 References
The editions of the following MSAERs which are in effect on the project’s
standards cut-off date (see SAEP-14) are applicable to this procedure. All other
references shall use the latest edition:
4 Terminology
4.1 Acronyms
DD Detailed Design
EK Engineering Knowledge
ES Engineering Services
ID Inspection Department
IM Interface Management
OK Operations Knowledge
OP Operations
OS On-stream
PP Project Proposal
PS Process Simplification
VA Value Assurance
VE Value Engineering
VM Value Management
4.2 Definitions
Capital Management System (CMS): The general framework adopted by
Saudi Aramco for managing and controlling activities on Capital Projects. The
CMS covers the entire development process from business planning, through
project definition and execution to operations.
Front End Loading (FEL): A process that organizes the project life cycle into
phases, each with defined activities, deliverables and specific objectives. FEL
is applicable for all projects that apply the Capital Management System (CMS).
For more details, refer to SAEP-17.
6 Requirements/ Instructions
The approved AVIP Plan becomes the baseline for the AVIP plan to be
implemented for each project. Since best practices have the greatest impact on
a project during the FEL phases, it is recommended that their use be planned
early and repeated, as applicable. The Project Leader/Manager is responsible
for the implementation of the recommended practices for their projects. For
more details on responsibility, please refer to Section 13 of this document.
In case there is a need for revising or updating the approved AVIP Plan, the IPT
leader shall secure PMOD/POD’s approval for the revised AVIP plan and a
copy of the revised plan shall be submitted to PMOD/Value Assurance for
information and reference. The revised plan shall then be reflected in the Value
Improving Practices Automated System and the Project Execution Plan.
With the help of the facilitator, individual VIP deliverables shall be submitted to
PMOD for review and for value assurance, respectively. During the execution
phases (Detailed Design and Construction) all VIP sessions and deliverables
shall be led/conducted by approved value practice consultants or any qualified
SME from the execution-phase contractor or subcontractor who has been
approved by PMOD.
Upon the completion of all VIP workshops, participants shall provide feedback
on the VIP workshop and the facilitator’s performance.
information, and for the latest guidelines and updates on the VIP deliverables.
The IPT Leader shall approve the final VIP deliverables (including the VIP
Reports) upon completion of the draft VIP deliverables review by PMOD.
Post VIP workshops, the IPT is responsible to implement all accepted action
items/recommendations and shall VIPs action list (VIPIT Worksheet) to
PMOD/POD to be logged and tracked utilizing a tracking system identified by
PMOD. All action items logged in the system shall be implementd and their
status updated in the system. See Appendix C for the VIPIT Worksheet and
additional information.
IPT shall submit the draft VIPs Outcome Implementation Report to PMOD for
review at least one month prior to gate submittal. IPT lead shall demonstrate to
PMOD that all actions have been closed and status updated prior to each gate.
PMOD SME will follow up with IPT Lead or Project VIP Coordinator post
workshop to ensure that the process is well understood and that all action items
status are updated appropriately prior to VA Gate review. The PMOD SME will
identify any status gap and share the findings with IPT Lead prior to the
submittal of VIPs Outcome Implementation Report for VA Gate Review.
The final VIPs Outcome Implementation Report along with its attachment for the
different practices shall be submitted to PMOD for Value Assurance during the
Gate Reviews.
The VIPs reports and the implementation status reports submitted for each gate
will be used to calculate KPIs established to measure the performance of VIPs
implementations. Each project is required to implement the applicable VIPs for
the project and all recommendations resulting from the AVIPs workshops.
PMOD will monitor the implementation and trends of the KPIs and will use this
information to enhance VIPs process and report performance including
escalation of issues to Project Execution Agencies.
With the assistance of VIPs facilitators, IPT Leaders are required to document
and submit lessons learned from each session. This will allow PMOD to
improve future facilitation services and to use the captured lessons as input for
future sessions for each practice. The documented lessons learned will also be
used to create synergy between practices where the scope and identified
issues overlap.
7 Value Engineering
• Redundancy
• Over-design
• Manufacturing add-ons
• Environmental impact
IPT Leader shall approach PMOD for facilitation support prior to contacting 3rd
party facilitators. PMOD/POD will decide whether SA VE SME or 3rd party
consultant is to facilitate the VE study. VE shall only be facilitated by PMOD VE
SMEs or a Certified Value Specialist who has been approved by PMOD/POD.
The list of approved consultants can be obtained from PMOD/POD.
For C1-type projects, VE should be conducted once at 30% FEL3/PP stage. For
A, B, & C-type projects, VE will be conducted both at 60% FEL2/DBSP and 30%
FEL3/PP. Type A & B projects shall conduct at least two VE sessions unless
otherwise stated in the Approved VIP Plan.
During the Project Proposal phase, the Construction Agency initiates the VE
study which should be completed during the early phase of the Project Proposal
but not later than the 30% completion milestone date. The Construction
Agency is to start planning for the session at least one month prior to the 30%
of FEL3/PP milestone to ensure the availability of key stakeholders and
approved facilitator.
For scheduling purposes, the VE studies shall be coordinated with the Project
Management Office Department (PMOD/POD). The requirements for
conducting VE studies shall be identified in the Project Proposal contractor’s
scope of work and the Value Improving Practices Implementation Plan and
Project Execution Plan.
• Plot Plan Analysis for expansion and grass root process plant projects to
ensure that facilities are designed in the most efficient and cost-effective
manner.
During the FEL2/DBSP phase, the VE proposals that are accepted by FPD are
to be reviewed by the proponent organization, IPT Process & Control Systems
Department (P&CSD), and Consulting Services Department (CSD) if related to
standards’ requirements, before being incorporated into the FEL2/DBSP scope
of work. The status and resolution of all accepted and justification for the not
accepted VE proposals shall be documented in the Value Engineering section
of the FEL2/DBSP and the VIP Outcome Report for Value Engineering.
Moreover, a resolution should be reached in regards to the “Accepted for
Further Study” concepts. At the end of the FEL2/DBSP, all items should be
either accepted or not accepted.
During the FEL3/Project Proposal phase, the VE proposals that are accepted
by the proponent organization and the Construction Agency are to be reviewed
by FPD, Process & Control Systems Department (P&CSD), and Consulting
Services Department (CSD) if related to standards’ requirements, before being
incorporated into the Project Proposal scope of work. Any scope change
resulting from VE proposals shall be documented through SCDRs as per
SAEP-14. The status and resolution of all accepted and justification for the not
accepted VE proposals shall be documented in the Value Engineering section
of the Project Proposal and the VIPs Outcome Report for Value Engineering.
Moreover, a resolution should be reached in regards to the “Accepted for
Further Study” concepts. At the end of the Project Proposal, all items should be
either accepted or not accepted. All phases of the VE Study (Information,
Functional Analysis, Creativity, Evaluation, and Presentation) are mandatory
and shall be completed.
7.6 VE Deliverables
With the assistance of the VE SME, the IPT shall submit the following
deliverables after each VE study event as outlined in Appendix A - Optimum
Implementation Timing for VIPs and Summary of VIPs Criteria.
• List of attendees
1) Technical Description
1) List of attendees
The content of these deliverables should be relevant and address the objectives
of the respective gates. Gate objectives are outlined in SAEP-17.
Refer to the latest version of POD VE Guide for further details about the
workshop.
8 Best Practices
The use of industry best practices can significantly improve project performance
in terms of cost, schedule, and operability. However, the effectiveness of these
techniques depends on several factors, including the nature of the project, the
project phase at which the practices are applied, and the expertise of the
individuals responsible for implementing them. The elements of the best
practices are outlined in the Best Practices Guide. This includes the following
practices:
Under this practice, C1 type projects are conducted once on or at 10% Project
Proposal. For A, B, and C projects, PP&TA workshops are conducted at 10%
FEL2/DBSP phase and again at or before 10% FEL3/PP phase. If the same
design team is performing the FEL2/DBSP and FEL3/PP, there is no need to
On a typical Budget Item (BI), key stakeholders are the Proponent, FPD, IPT,
Loss Prevention, Inspection Department, other Project Execution Plan
approving organizations and contractor discipline leads. IPT team leads, and
particularly Proponent engagement, are a must to successfully implement this
practice. The workshops will be coordinated by the IPT Leader and will be
facilitated by PMOD or a PMOD-approved consultant.
• Review and align on draft Project Execution Plan (PEP), consider alternate
plans and identify critical issues/gaps to help revise document as needed.
For an effective session, the IPT lead is to share the below documents with the
facilitator.
• Attendance Sheet
Reference latest VPU, PP&TA Workshop Guide for more details on conducting
a PP&TA Workshop and its methodology. Reference Appendix A and contact
VPU Supervisor and SME for support.
BEAM outputs are binding to project and shall guide decision making in
planning Phase. All open issues identified during the workshop must be
actioned and closed in FEL2 Phase. For the BEAM workshop, please
contact POD/VPU Supervisor for latest information.
8.2 Constructability
During constructability workshops, the project team shall evaluate the outcome
of the Modular Design Assessment (MDA) Study. The buildability, logistics, and
ramifications of modularization on constructability of the project shall be
evaluated thoroughly. All issues noted during this assessment related to
modularization design and its impact on construction shall be reflected in the
Constructability Log under modularization sub-heading with specific
recommendations and actions for resolution.
During the study, the IPT shall review all aspects of constructability that could
be of a concern for the project including but not limited to spacing requirements,
proposed scope changes during Detailed Design, accessibility of the project or
equipment during construction and beyond. Potential issues should be flagged
including deviations of standard spacing requirements.
Also, during the constructability session, the project team shall assess the
impact and ramification of any new construction and design technology that the
project may be considering for utilization.
Prior to the Constructability sessions, the IPT shall conduct initial Project
Execution Technology (PET) study to illustrate the assessment of all potential
PET items listed in PXP & Technical Selection Report (TSR) for deployment in
all project phases as applicable. The assessment result shall be compiled in a
PET document including the safety, environmental, schedule and financial
rewards. IPT shall update the PET domain with the findings of the workshops”.
IPT shall present the PET study’s findings and recommendations to the
constructability’s team, and together they shall assess the impact and
ramification of PET’s proposed technologies. The PET study shall be updated
by IPT to reflect the assessment results.
Constructability Deliverables
With the assistance of the Constructability SME, the IPT should submit a
constructability report after each Constructability study event as outlined below.
• List of attendees
The content of these deliverables should be relevant and address the objectives
of the respective gates. Gate objectives are outlined in SAEP-17.
Refer to the latest version of POD Constructability Guide for further details
about the workshop.
The startup team, led by the Proponent, is responsible for getting the plant
safely and efficiently commissioned and started. Successful commercial
operations require successful startup and successful startup requires effective
planning for startup.
The key to a successful startup is to have an Operational Readiness and
Startup Plan that defines the roles and responsibilities of the startup team
explicitly and clearly identify the manpower need with a high level of accuracy.
The preparation of the Startup Plan, which includes a Responsibility
Assignment Matrix “Responsibility, Accountability, Consult, Inform (RACI)”, is
normally initiated late in the Design Basis Scoping Paper phase and is
elaborated during the early stages of Project Proposal and further refined
throughout the subsequent project phases.
The startup plan describes in detail the sequence of startup, integration with
shutdowns, turnover sequence, plans for commissioning procedures, training
program, list of issues and concerns that could be potential risks for startup,
plans for maintenance procedures, raw materials and supplies needed for
startup, plans for the preparation of operating manuals, documentation,
required spare parts and startup team structure including the responsibilities
and accountabilities for the Proponent, constructor, vendor representative,
Project Engineer, operations, and maintenance personnel.
The development of the Startup Plan (as an integral part of the Operational
Readiness Plan) is the responsibility of the Operations representative with input
from the Project Leader /Manager, design team, Safety and Industrial Security
(S&IS), Inspection, etc. It also relies upon information from the Pre-
commissioning & Mechanical Completion plan.
Note: The Operational Readiness Plan (ORP) is a document that defines how the project will
transition into an operating facility and will describe what “operational-type” steps must
be taken 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).
Implementation Criteria
The Planning for Startup tools can be utilized either web-based or offline. The
model recommends that about 50% of the startup planning effort should be
completed by the end of the Project Proposal phase. By the end of Detailed
Design the startup planning effort should be 80% complete.
The startup plan addresses the startup objective, roles and responsibilities of
key persons and organizations, the startup philosophy, startup scope and major
systems, startup risk, and any procurement related to startup as well as the
timing of startup planning and execution activities.
PFSU Deliverables
With the assistance of the PFSU facilitator, the IPT shall submit a Planning for
Startup report after each PFSU workshop event as outlined.
The content of these deliverables should be relevant and address the objectives
of the respective gates. Gate objectives are outlined in SAEP-17.
PDRI is a powerful and simple tool that helps the project team measure project
scope definition for completeness. This practice/workshop shall be conducted
twice (i.e. right before Gate 2 and Gate 3 Value Assurance reviews). The
optimum time for conducting these workshops is after receiving and resolving
all review comments raised during the 90% FEL2/DBSP, and 90% of Project
Proposal. PDRI workshops involve the IPT, Proponent, contractor, and other
parties as needed to measure level of project scope definition and Project
Proposal completeness and clarity. PDRI consists of approximately 70
elements that identify and very precisely describe each critical element in a
preliminary engineering scope definition package.
PDRI Deliverable
For all projects, PDRI reports shall be developed by the SME using the latest
PDRI worksheet (relevant to the project scope, i.e. industrial, infrastructure or
buildings) that is approved by PMOD/POD. Refer to the PDRI Guide for further
details or contact the PMOD/POD/VPU Supervisor for further information. For
industrial projects, the PDRI report shall show assessment scores of both the
maturity and accuracy of FEED deliverables.
With the assistance of the PDRI SME, the IPT shall submit the PDRI report
after each PDRI session as outlined in Appendix A - Optimum Implementation
Timing for VIPs and Summary of VIPs Criteria.
Using the PDRI tool and the outcome of the two sessions (90% FEL2/DBSP
and 90% FEL3/PP), the SME will generate the Front-End Loading Indexes for
FEL2 and FEL3.
The PDRI report shall indicate the low defined elements that negatively affect
the project scope definition. These items shall be sent to IPT for action and
resolution with due dates and assigned team members.
A copy of the final PDRI report shall be distributed to PMOD/POD no later than
four weeks from the completion of the PDRI session in the FEL2/DBSP, and the
FEL3/PP phase.
Refer to the latest version of POD PDRI Guide for further details about the
workshop.
Scope Control (SC) is a preventive, proactive process that starts with a detailed
project scope and ensures discipline in scope changes during execution.
Change Management (CM) involves establishing and communicating to all
project stakeholders a system for recognizing, evaluating, and implementing
changes during all phases of the project. SC&CM is a facilitated session and
shall be conducted only at 0-10% of Detailed Design.
The SC+CM workshop conducted during the DD reminds the project team of
the effectiveness of and discipline required for Scope Control and Change
Management during the Execution phase. This workshop will be facilitated by
the Design Contractor or PMOD-approved consultant.
The Project Leader shall be responsible to carry out the below listed workshops
as part of the Lessons Learned requirements in this procedure.
Implementation Criteria
LLI Deliverables
With the help of an LLI facilitator, the IPT shall submit the LLI Report
after each LLI Workshop as outlined in Appendix A - Optimum
Implementation Timing for VIPs and Summary of VIPs Criteria.
1. The title for each applicable lesson from all sources including lessons
from LL Knowledgebase, pitfalls from Pitfall Prevention Tool, ES
Implementation Criteria
LLC Deliverables
With the help of an LLC facilitator, the IPT shall submit the LLC report
within two weeks of each LLC workshop as outlined in Appendix A -
Optimum Implementation Timing for VIPs and Summary of VIPs Criteria.
2. Background
3. Root Causes/Benefits
4. Recommendations
Implementation Criteria
At least three weeks prior to FEL2/DBSP or FEL3/PP LLI workshop events, the
IPT Leader shall invite appropriate Engineering Services departments to allow
them to prepare the material to be delivered during the LLI workshop. The
invitation should include project type, phase, scope and any relevant
documents that may help respective ES departments to prepare for the
workshop.
For Type A projects, the responsible ES department shall identify and present
critical engineering topics from various functions and process areas (e.g., CSD:
corrosion, structural/piping vibration, burn pits, electrical, heat exchangers;
P&CSD: flaring, process automation, MEG issues, WGP foaming) per a mutual
agreement with the IPT that includes the following criteria:
• New technologies
• Lessons learned
• Innovative solutions
Implementation Criteria
Prior to FEL2/DBSP start, FPD shall review the PPA reports of previous
projects with similar scope and shall identify the lessons that could be
implemented on the current project. All potential lessons from PPA for
implementation shall be developed using the standard Project Management
LLC format and made available for implementation during the FEL2/DBSP LLI.
Implementation Criteria
At least three weeks prior to FEL2/DBSP LLI workshop events, the IPT Leader
shall invite relevant Operations Department(s) to allow them to prepare the
material to be delivered during the LLI workshop. The invitation should include
project type, phase, scope and any relevant documents that may help
department(s) to prepare for the workshop.
The OPs department shall deliver OPs knowledge or lessons that are relevant
to the project scope that should be addressed during the LLI workshop.
Six months after the project OS date, responsible Operations Department shall
coordinate with PMOD to conduct Post Project LLC Workshop.
10 Risk Management
The recommended optimum timing for the PRM Events is outlined in Appendix
A. It should be noted that the optimum timing is not a fixed date but a timeframe
that spans several weeks.
1. Plan
2. Identify
3. Qualify
4. Quantify
5. Respond
The PRM Events are facilitated by PMOD risk management SMEs or PMOD-
approved consultants
PRM uses a Risk Register as the core of its process, which provides the
justification for, and description of all activities required to manage the risks
identified. Implementation of risk responses and risk monitoring shall be done
following PRM Events.
The PRM process facilitates the efficient use of resources and the
determination of contingency reserves. The process is described in detail in the
Saudi Aramco Project Risk Management Guide.
The number of activities within the PRM process depends on the size and
complexity of the capital project as outlined in Appendices A and B.
The PRM Plan shall be drafted by the Risk Manager in collaboration with the
IPT, and then reviewed and finalized together with the facilitator prior to each
PRM Event. The scope of the PRM Event will then be jointly decided between
the Risk Manager and facilitator based on a review of the PRM Plan. PRM
Events shall be attended by senior IPT members representing key stakeholders
as outlined in Appendix A.
The table below outlines the different PRM requirements for projects of different
types.
A&B Enhanced
C & C1 Standard
No PRM activities are required for projects with capital budgets below $10MM.
Specific deliverables of the PRM Events for the four project types are fully
described in the Saudi Aramco PRM Guide.
Lessons Learned will be captured from the PRM Engine (PRIME) to benefit
future projects. The Risk Register shall be handed-over to Operations upon
construction completion. Recommended PRM process improvements will also
be captured by PMOD as part of the Lessons Learned process.
The IPT Lead is ultimately responsible for the implementation of the project risk
management. This includes assigning a Risk Manager to coordinate the
drafting of the PRM Plan and submission of relevant project documents for
PMOD’s review prior to PRM Events. The Risk Manager is also responsible for
scheduling PRM Events and IPT risk review meetings, inviting all key
stakeholders (including Value Assurance Team members), securing a
facilitator, coordinating and maintaining an up-to-date Risk Register, and for
monitoring risk responses for completion and effectiveness. For programs, the
program Risk Register will be administered by a program Risk Manager, with
similar responsibilities to the project Risk Manager, as mentioned above.
The facilitated PRM Events produce three key documents as described in the
Saudi Aramco PRM Guide. They are as follows:
1. PRM Plan
Defines the methods and depth of risk analysis required, including the risk
tolerance.
2. Risk Register
PRM Status Reports are outcomes of PRM Events, and shall also be
produced on a monthly basis following workshops. PRM Status Reports are
required to be endorsed by the IPT Leader. Implementation of risk
responses and conducting Risk Register updates in the PRIME on a
monthly basis is mandatory.
IM is required for all Type A and B projects and for all projects utilizing more
than one construction contractor. The process is defined by the combination of
specific project events outlined in Appendix A - Optimum Implementation
Timing for VIPs and Summary of VIPs Criteria, as well as a continuous process
of monitoring and control to ensure all parties are working towards the same
goal in a compatible manner. It is the responsibility of the IPT and their
contractors to hold IM meetings and implement IM.
11.2 IM Implementation
PMOD has deployed the IMS as the tool for capital projects to manage the IM
value practice. The PMOD IM team works closely with large capital projects to
support the implementation of IM points by utilizing the IMS. This enables the
management and tracking of all interface points where different contractors
need to integrate to realize the overall facility construction.
The IPT is responsible for establishing the number, type, and method of
interface points required for each project package and uploading the
information into the IMS.
The plan provides oversight of the interactions and information flow between
the major players. The main components of the document include the
following:
• Project Information
The roles and responsibilities of the three identified roles in the Interface
Management System are:
• Interface Manager is the single point of contact for each contractor and
approves electronic forms for the contractor
11.6 Deliverables
The IPT should submit the following deliverables after each IM event as
outlined in Appendix A - Optimum Implementation Timing for VIPs and
Summary of VIPs Criteria.
The content of these deliverables should be relevant and address the objectives
of the respective gates. Gate objectives are outlined in SAEP-17.
Capital Projects Handover Reviews shall be conducted for CMS projects at the
execution phase identified by three milestones, 60% detailed design, 30%
construction progress, and 70% construction progress. The objective of the
review is to provide a neutral perspective to management, including Project
Sponsor, of the current status of project handover readiness. It aims for early
identification and resolution of handover challenges, proper planning and
compliance and assurance of early stakeholder engagement and alignment for
smooth handover. For details see SAEP-17.
13 Responsibilities
13.1 PMOD
• At the beginning of each year or at the initiation of each project, assist the
IPT to identify the required VIPs to be implemented for the individual project,
Budget Item (BIs), etc.
• Issue the Applicable VIP report to the IPT and identify the strategy for
facilitation services.
• PMOD administers the VIP applications and provides access to the Value
Improving Practices Automated System. Projects should coordinate end-
user training requirements with PEDD or a qualified third party. As a last
resort, PMOD may be approached to facilitate systems training on an as-
needed basis.
• Approving the final VIP deliverables (including the VIP Reports) upon
completion of the draft VIP deliverables review by PMOD
• Review and validate the technical and commercial impact of all accepted
and implemented proposals
• The documentation and validation of all the cost avoidances generated from
applicable VIPs as per company policies including SABP-A-175.
• Document in the Value Engineering section of the FEL3/PP the status and
resolution of all accepted VE proposals and provide justification for the not
accepted VE proposals.
• Provide a copy of the final VE report to PMOD/POD no later than four weeks
from the completion of the VE session in the FEL3/PP or FEL2/DBSP
phase.
• Submit Applicable VIPs Outcome Reports to PMOD for review and Value
Assurance during Stage Gate.
• The IPT Leader, in conjunction with the VIP facilitator, shall determine the
key attendees and ensure that the appropriate stakeholders from
Engineering Services and other SME organizations from Saudi Aramco are
invited for the VIPs workshops. If any of the key attendees are unavailable,
the IPT shall reschedule the workshop.
• Ensure fulltime attendance of IPT members for the duration of the workshop
with meaningful engagement.
• Attend the Implementation Meeting and sign off on the final outcome.
• After completing any workshop, populate all generated action items using
the VIPs Action Items Implementation Tracking Data Input Template and
forwarded to the PMU/POD to log it into the VIPs automated tracking
application for needed follow-up (contact the PMU/POD for the latest Data
Input Template).
• Updating and closing all due action items in the PMOD Value Improving
Practices Automated System.
Ensure that the qualified participants attend the required facilitation sessions.
Conduct LLC six months after the project completion and coordinate with
PMOD/POD for facilitation services.
Appendix A - Optimum Implementation Timing for VIPs and Summary of VIPs Criteria
FEL 0 FEL 1 FEL 2 FEL 3 EXECUTION
INITIATION BUSINESS CASE STUDY DBSP PP DD CONSTRUCTION
VIP
0%- 0%- 90%- 0%- 90%- 0%- 90%- 0%- 90%- 0%- 90%- 0%- 90%-
30% 60% 100% 30% 60% 30% 60% 30% 60% 30% 60% 20% 60% 20% 60%
10% 10% 100% 10% 100% 10% 100% 10% 100% 10% 100% 10% 100%
A, B, C
1 LLI A, B, C
C1
A, B, C
A, B, C, A, B, C,
2
PP&TA A,B
C1
(BEAM) **
***
3
VE + A, B, C
A, B, C
(PS&DTC) C1
A, B, C, A, B, C,
4 PFSU C1 C1
A, B, C,
5 CONST. A, B, C
C1
A, B, C
A, B, C A, B, C A, B, C
6 PRM A, B, C A, B
C1 C1 C1
A, B, A, B,
7 PDRI C, C1 C, C1
8 IM A A, B A, B A, B
A,
9 SC&CM B, C
A, B, C
10 LLC* A, B, C A, B, C A, B, C
C1
* One LLC with Operations (OKW) shall be conducted six months after the project completion **Conduct BEAM *** PP&TA - conduct C1 and when the design team changes for A, B and C
Click the hyperlink <Action Items Worksheet> to download the editable version. Note,
each VIP has an individual tab on the worksheet, so ensure you are selecting the
appropriate form for submittal.
Document History
22 December 2021 Editorial revision.
15 July 2021 Major revision to reaffirm content.
3 May 2020 Editorial revision. Changed the contact person, CPED to PMOD, SABP-A-12 to
SABP-A-012, and removed cancelled SAES-N-004.
2 May 2019 Editorial revision to comply with content confirmation requirements
22 February 2018 Major revision that include alignment of Lesson Learned Program with Corporate
Knowledge Management Initiative, alignment of VIPs process with Operational
Excellence, tracking implementation and reporting of non-
performance/escalation, optimization of the timing and frequency of certain VIPs,
inclusion of C1-Type Projects to FEL 2 KPI calculations and additional
clarifications regarding project characterization and adding modularization and
construction and design technology into Constructability assessment
requirements.
16 September 2015 Major revision to incorporate ATP-CE’s Capital Management System (CMS).