Engineering Procedure

SAEP-206 12 May 2016

Instructions for Establishing and Maintaining Corporate Technical Alert
Document Responsibility: Engineering Knowledge & Resources Division /
Technical Knowledge Sharing Unit

Content
1 Scope……...................................................... 2
2 Applicable Documents.................................... 2
3 Definitions and Acronyms............................... 2
4 Corporate Technical Alert Criteria….............. 3
5 Instructions…………………………………...… 4
6 Roles and Responsibilities............................. 5

Appendix A - Flow Diagram of

Corporate Technical Alert............... 6
Appendix B - CTA Form........................................ 7

Previous Issue: New Next Planned Update: 12 May 2019

Page 1 of 7
Contacts: Amjad Al-Monzer on +966-13-8801112 or Ahmad Abdullah on +966-13-8801233

Copyright©Saudi Aramco 2016. All rights reserved.

Document Responsibility: EK&RD/Technical Knowledge Sharing Unit SAEP-206
Issue Date: 12 May 2016
Next Planned Update: 12 May 2019 Instructions for Establishing and Maintaining Corporate Technical Alert

1 Scope

This SAEP describes the instructions for establishing and maintaining Corporate
Technical Alerts (CTAs). The purpose of this procedure is to establish CTA criteria,
roles and responsibilities for Saudi Aramco organizations responsible for the initiation,
approval, and implementation of Technical Alerts. The CTA objective is to allow
proactive action to flag, expedite mitigations, monitor and report on the state of
identified technical deficiencies that have a potential to significantly impact Health,
Safety, Security or Environment.

2 Applicable Documents

The requirements contained in the following documents apply to the extent specified in
this procedure:

 Saudi Aramco Engineering Procedures

SAEP-125 Preparation of Saudi Aramco Engineering Standards
SAEP-301 Instructions for Establishing and Maintaining
Mandatory Saudi Aramco Engineering Requirements

3 Definition and Acronyms

Corporate Technical Alert (CTA): A structured SAP framework including set of

engineering recommendations, addressed to specific End-User(s), to proactively alert
system technical deficiencies that have a potential to significantly impact Health,
Safety, Security or Environment.

Issuer: A SAP authorized user from ES, Operating Facilities, Materials Supply, or
PMT who has the privilege to initiate a technical alert proposal through SAP System.

Reviewer: A representative from the Issuer organization who reviews and processes
recommended alerts to his/her Department Head.

Department Head: A manager from the Issuer or Processor organization who concurs
on the CTA for Approver, and/or EK&RD actions.

Approver: The Engineering Chief Engineer who has the authority to approve
Corporate Technical Alert (CTA).

Coordinator: An End-User representative who assigns CTA’s recommendations to a

Processor and follows up on the implementation.

Page 2 of 7
Document Responsibility: EK&RD/Technical Knowledge Sharing Unit SAEP-206
Issue Date: 12 May 2016
Next Planned Update: 12 May 2019 Instructions for Establishing and Maintaining Corporate Technical Alert

Processor: A representative from End-User who are responsible for identifying actions
with expected time of completion and reporting the implementation progress to mitigate
the identified technical deficiencies at his/her facility.

End-User: Organization (Operating Facilities or PMT) responsible for implementing

recommendations of approved CTAs.

MSAERs: Mandatory Saudi Aramco Engineering Requirements defined in SAEP.

Non-Standards Organization: The organization that issues CTA related to MSAERs

not under its jurisdiction.

Reviewing Department: The organization that has the MSAERs addressed by CTA
under its jurisdiction.

Engineering Knowledge & Resources Division (EK&RD): Standards Coordination

Unit (SCU) verifies CTA prior to Approver action, dispatches CTAs from
non-standards organization Issuer to appropriate reviewing department to review and
validate the content, provides status reports to BOE and publishes approved CTA on
eStandards website. Technical Knowledge Sharing Unit (TKSU) shares CTA among
other corporate organizations for information.

4 Corporate Technical Alert Criteria

The Corporate Technical Alert shall be initiated and processed to address, but not
limited to, the following:

4.1 Retroactive Safety Requirements mandated by revisions to MSAER as defined

by SAEP-125 and SAEP-301.

4.2 Recommendations of internal/external technical reports that are related to

Health, Safety, Security or Environment impact.

4.3 Any directions received from the government for immediate implementation.

4.4 Lack of proper interpretation of MSAERs or international code requirements

that could have significant impact on Health, Safety, Security or Environment.

4.5 Findings and recommendations captured from plant incident investigations.

4.6 Reported manufacturing defects or potential equipment failures.

4.7 Major and critical project lessons learned.

Page 3 of 7
Document Responsibility: EK&RD/Technical Knowledge Sharing Unit SAEP-206
Issue Date: 12 May 2016
Next Planned Update: 12 May 2019 Instructions for Establishing and Maintaining Corporate Technical Alert

5 Instructions

5.1 Issuer requests the required SAP role detailed in section 6 in order to access
SAP/CTA system. Then, he enters information about description, summary,
findings, and recommendations. Issuer shall attach all supporting CTA
documents. A sample of CTA template is available in Appendix B.

5.2 Once CTA is created, SAP notification email will be sent to the Reviewer to
evaluate it and enable processing to next management level. Reviewer shall
insert his remarks in SAP System to indicate his position from the proposed
CTA.

5.4 Once processed by the Reviewer, the Department Head will receive SAP
notification email to concur or return to the Issuer.

5.5 If the CTA is issued by non-Standards department, it will go to EK&RD for

verification prior to Approver action. EK&RD may assign to another reviewing
department in case the CTA requires multidisciplinary review. Within reviewing
department, it will follow the same approval levels until it gets finally approved
by Approver.

5.6 Once approved by Approver, the CTA will be disseminated to the End-User’s
Department Head.

5.7 SCU will receive a copy of approved CTA to be published on the eStandards
website.

5.8 TKSU will receive another copy of approved CTA to be shared companywide
through Knowledge Sharing process.

5.9 The End-User’s Department Head reviews the CTA for necessary action items
and assign a Coordinator. SAP notification email will be sent to the
Coordinator.

5.10 In SAP, the Coordinator can assign a Processor for each recommendation.
SAP notification email will be sent to Processor.

5.11 The Processor will work to determine the action items along with Expected
Time of Completion (ETC) and submit them to his manager for approval and
implementation. In addition, he will work to provide progress reports to the
coordinator and document the action items to be part of the plant permanent
records.

Page 4 of 7
Document Responsibility: EK&RD/Technical Knowledge Sharing Unit SAEP-206
Issue Date: 12 May 2016
Next Planned Update: 12 May 2019 Instructions for Establishing and Maintaining Corporate Technical Alert

6 Roles and Responsibilities

Action by R&R

Issuer - Apply for issuer SAP Role QM:EKRD:CTA_IOI:0001.

- Initiate technical alert proposal through SAP System.

Reviewer - Review, evaluate and process recommended alerts to his/her Department Head.

Department Head - Concur on the CTA for Approver, and/or EK&RD actions.

Approver - Approve CTA.

Coordinator - Apply for coordinator SAP Roles QM:EKRD:CTA_PCO:0001.

- Assign CTA’s recommendations to a Processor.
- Follow up on the implementation.

Processor - Apply for processor SAP roles QM:EKRD:CTA_PPR:0001.

- Report the implementation progress of CTA approved recommendations.

EK&RD - Verify CTA prior to Approver action.

- Dispatch CTAs from non-standards organization to appropriate reviewing
department.
- Publish approved CTA on eStandards website.
- Share CTA among corporate organizations.
- Share corporate CTA monitoring report with BOE.
- Provide technical support to CTA system and users.

Revision Summary
12 May 2016 New Saudi Aramco Engineering Procedure developed to define the Corporate Technical
Alert (CTA) and the roles and responsibilities of all organizations involved in the process.
It also describes the cases and applications that require the CTA initiation.

Page 5 of 7
Document Responsibility: EK&RD/Technical Knowledge Sharing Unit SAEP-206
Issue Date: 12 May 2016
Next Planned Update: 12 May 2019 Instructions for Establishing and Maintaining Corporate Technical Alert

Appendix A - Flow Diagram of Corporate Technical Alert

Page 6 of 7
Document Responsibility: EK&RD/Technical Knowledge Sharing Unit SAEP-206
Issue Date: 12 May 2016
Next Planned Update: 12 May 2019 Instructions for Establishing and Maintaining Corporate Technical Alert

Appendix B - CTA Form

Page 7 of 7