Saep 381ppt
Saep 381ppt
Saep 381ppt
1Scope……………………………………………... 2
2Purpose…………………………………………… 2
3 Conflicts and Deviations………………………… 2
4 Applicable Documents………………………….. 3 5D
efinitions…………………………………………
3
6Violations Definitions……………………………. 4
7Instructions……………………………………….. 5
8 Responsibilities………………………………….. 8
9 Cancelled Quality Notifications……………….. 10
1 Scope
2 Purpose
2. Clearly define the corporate process for project quality issue escalation
including its documentation, requirements and definition of violation
categories, systems and procedures.
3. Ensure roles and responsibilities for project quality issue escalation are
well defined and auditable.
2.2 The intent of quality issue notification is to report and record quality or technical
deficiencies, determine the root cause of the problem, record the actions taken to
correct non-conformities, avoid recurrence and enhance overall project quality.
1. Any conflict between this procedure and other applicable Mandatory Saudi
Aramco Engineering Requirement (MSAER) shall be resolved in writing
through the Chairman, Inspection Engineering Standards Committee (IESC).
2. Direct all requests to deviate from this procedure in writing to the Manager,
Inspection Department of Saudi Aramco, Dhahran.
Page 2 of 17
Document Responsibility: Inspection Engineering Standards Committee SAEP-381
Issue Date: 17 March 2013
Next Planned Update: 28 January 2017 Project Quality Issues Escalation Process
4 Applicable Documents
The applicable requirements in the latest edition of the following Saudi Aramco
Engineering Procedures, Schedule “Q” and General Instructions (GIs) shall be
considered an integral part of this procedure.
5 Definitions
LBE: Logbook Entries (First level of reporting quality deficiency using Manual
Logbook or the Quality Management Information System, QMIS)
Page 3 of 17
Document Responsibility: Inspection Engineering Standards Committee SAEP-381
Issue Date: 17 March 2013
Next Planned Update: 28 January 2017 Project Quality Issues Escalation Process
NCR: Non Conformance Report (Issued by Saudi Aramco through SAP QM).
6 Violations Definitions
Page 4 of 17
Document Responsibility: Inspection Engineering Standards Committee SAEP-381
Issue Date: 17 March 2013
Next Planned Update: 28 January 2017 Project Quality Issues Escalation Process
the structural integrity of the next phase will be jeopardized. Such violation if not
corrected in a timely manner will lead to more severe damage or complexity.
2) Any violation to Schedule Q.
Commentary Note:
Minor violations related to Schedule Q listed in Appendix D are excluded from this
definition.
7 Instructions
Page 5 of 17
Document Responsibility: Inspection Engineering Standards Committee SAEP-381
Issue Date: 17 March 2013
Next Planned Update: 28 January 2017 Project Quality Issues Escalation Process
1. PID PQM, SAPMT Senior Project Engineer or Lead Project Engineer and
the Contractor Quality Representative are responsible for determining the
initial Agreed Completion Date (ACD) for LBEs, NCRs and Worksheets.
2. When no agreement on the ACD of any type/category of Quality
Notification could be reached, the ACD shall be decided mutually by the
next level of authority from ID and PMT, depending on the Quality
Notification category.
Page 6 of 17
Document Responsibility: Inspection Engineering Standards Committee SAEP-381
Issue Date: 17 March 2013
Next Planned Update: 28 January 2017 Project Quality Issues Escalation Process
Page 7 of 17
Document Responsibility: Inspection Engineering Standards Committee SAEP-381
Issue Date: 17 March 2013
Next Planned Update: 28 January 2017 Project Quality Issues Escalation Process
3. Repeat of Moderate or Major violation within six (6) months will result
to a Quality Notification starting at the next higher level of Violation
Category and Notification. Repeat of a Minor violation due to
negligence shall be considered as Moderate violation.
7. Once the project reaches its MCC stage, all open LBEs, NCRs,
Worksheets and DWS shall be transferred to MPCS. Items required for
start-up or impacting safety are to be marked as ‘YES’ Items. All other
items shall be designated as ‘No’ Items.
8 Responsibilities
Page 8 of 17
Document Responsibility: Inspection Engineering Standards Committee SAEP-381
Issue Date: 17 March 2013
Next Planned Update: 28 January 2017 Project Quality Issues Escalation Process
4. Decides cases of violations not clearly defined in Section 6 and not listed
in Appendix D “Examples of Violations and Escalation Steps”
4. SAPMT
Page 9 of 17
Document Responsibility: Inspection Engineering Standards Committee SAEP-381
Issue Date: 17 March 2013
Next Planned Update: 28 January 2017 Project Quality Issues Escalation Process
Submitted quality notifications in SAP QM shall not be marked for deletion without
proper justification approved by PID Division Head. The approved justification shall
be attached in the quality notification being “marked for deletion”.
Revision Summary
28 January 2012 New Saudi Aramco Engineering Procedure.
17 March 2013 Minor revision to provide clarification on selected sections.
Page 10 of 17
Document Responsibility: Inspection Engineering Standards Committee SAEP-381
Issue Date: 17 March 2013
Next Planned Update: 28 January 2017 Project Quality Issues Escalation Process
Page 11 of 17
Document Responsibility: Inspection Engineering Standards Committee SAEP-381
Issue Date: 17 March 2013
Next Planned Update: 28 January 2017 Project Quality Issues Escalation Process
Contractor’s INCR
Yes
Yes
One-time
Repeat INCR? Completed on
No No No
w/in 6 Months ACD?
extension
granted?
Yes
Yes Yes
Completed
Reported by
No No on Extension
Contractor?
Date? Yes
Yes
Completed on Yes
ACD?
No
One-time
Completed on
Yes Yes
Extension date?
extension
granted?
No
No
Follow the
Quality Issue
Close INCR & QMIS
Reporting
Process
Page 12 of 17
Document Responsibility: Inspection Engineering Standards Committee SAEP-381
Issue Date: 17 March 2013
Next Planned Update: 28 January 2017 Project Quality Issues Escalation Process
Page 13 of 17
Document Responsibility: Inspection Engineering Standards Committee SAEP-381
Issue Date: 17 March 2013
Next Planned Update: 28 January 2017 Project Quality Issues Escalation Process
ESCALATION MATRIX
Recommended Phase for Violation Category
S/N Sample Violation Proactive Notification
Contractor’s Internal NCR not resolved at the approved Kick off Meetings /
12. Moderate
completion date Weekly QC meetings
Failure of the Contractor to control and implement the
quality requirements of its batch plants, subcontractors
and other service providers as required per Schedule Kick off Meetings /
13. Q. (e.g., Not assigning his own QC inspectors at the Moderate
Weekly QC meetings
manufacturer and service provider locations per
Schedule Q, and relying only on the In-House QC)
Page 14 of 17
Document Responsibility: Inspection Engineering Standards Committee SAEP-381
Issue Date: 17 March 2013
Next Planned Update: 28 January 2017 Project Quality Issues Escalation Process
ESCALATION MATRIX
Recommended Phase for Violation Category
S/N Sample Violation Proactive Notification
20. Insufficient QC Manpower (Deficiency < 10% of Plan) Job X / Kick-off Meetings Minor
Page 15 of 17
Document Responsibility: Inspection Engineering Standards Committee SAEP-381
Issue Date: 17 March 2013
Next Planned Update: 28 January 2017 Project Quality Issues Escalation Process
Page 16 of 17
Document Responsibility: Inspection Engineering Standards Committee SAEP-381
Issue Date: 17 March 2013
Next Planned Update: 28 January 2017 Project Quality Issues Escalation Process
Appendix F - Index
1Scope………………………………………………………………………..…………… 2
2Purpose……………………………………………………..…………………………… 2
3Conflicts and Deviations………………………..……………………………………… 2
4Applicable Documents……………………………………………………………..…… 3
5Definitions……………………………………………………………………...………… 3
6Violations Definitions…………………………………………………………………… 4
7Instructions……………………………………………………….……………………… 5
8Responsibilities…………………………………………….…………………………… 8
9Cancelled Quality Notifications………………….…………………………………… 10
Page 17 of 17