OMV (Tunesien) Production GmbH

CONTENTS

1 PURPOSE AND OBJECTIVES ....................................................................... 4

2 RESPONSIBILITIES ........................................................................................ 5

2.1 ASSET DEVELOPMENT MANAGER (ADM) ..............................................................5

2.2 PROJECT MANAGER (PM) .......................................................................................5
2.3 INTERFACE MANAGER (IM) .....................................................................................6
2.4 PROJECT SERVICES MANAGER (PSM) ..................................................................7
2.5 PROJECT TEAM MEMBERS DISCIPLINE ENGINEERS .......................................7

3 INTERFACE MANAGEMENT PROCESS....................................................... 8

3.1 INTERFACES .............................................................................................................8

3.2 WORK PROCESS ......................................................................................................9
3.2.1STEP 1: INTERFACE REGISTER ..............................................................................9
3.2.2STEP 2: INTERFACE ALIGNMENT SHEETS ..........................................................10
3.2.3STEP 3: TRANSFER OF INTERFACE DATA INTO REGISTER..............................10
3.2.4STEP 4: TRANSFER OF INTERFACE DATA TO SUPPLIER ..................................10
3.2.5STEP 5: FEEDBACK FROM SUPPLIER ..................................................................10
3.2.6STEP 6: ALIGNMENT OF SUPPLIER DATA WITH REQUESTOR..........................11
3.2.7STEP 7: INTERFACE CLOSE-OUT AND DISTRIBUTION FIA ................................11

4 MANAGEMENT OF INTERFACE REGISTERS ........................................... 12

5 MANAGEMENT OF INTERFACE ALIGNMENT SHEET.............................. 12

6 INTERFACE ALIGNMENT PROCESS FLOW DIAGRAM ........................... 13

7 INTERFACE REGISTER TEMPLATE........................................................... 14

8 INTERFACE ALIGNMENT SHEET TEMPLATE .......................................... 15

2/15
 OMV (Tunesien) Production GmbH

REVISION RECORD
Revision Amendment
000 Issued for Use

001 Revised to reflect latest Project Changes and to optimize the interface alignment process

ABBREVIATIONS
Aconex Synonym for the Online Information Management System provided by the
company Aconex.
EPC Engineering, Procurement and Construction
FIA For Information and Action
IAS Interface Alignment Sheet
MOC Management of Change
RFI Request for Information Mail Type
RTRFI Response To Request for Information Mail Type
SOW Scope of Work

DEFINITIONS

Supplier Means "Supplier of Interface information" and represents the party responsible
with interface design and definition of design data, including the successful
execution of their part of WORK

Requestor Means "Requestor of Interface Information" and represents the party

responsible for alignment of own design with the definition of design data
provided by "SUPPLIER" including the successful execution of their part of
WORK.

External Means the physical or logical point of contact between two or more different
Interfaces organisational entities and their related scopes. Typical External interfaces are
Company EPC Contractor or EPC Contractor 1 EPC Contractor 2.

Internal Means the physical or logical point of contact between two or more entities
Interfaces managed by a single organisation and their related scopes. Typical Internal

3/15
 OMV (Tunesien) Production GmbH

interfaces are Vendor 1 Vendor 2 under EPC Contractor.

1 PURPOSE AND OBJECTIVES

This document defines the Interface Management Work Process for the Nawara
Development Projects, including EPC SOW 1, 2 and 3.

The purpose of this document is to ensure that interfaces between the Nawara
Projects, EPC Contractors and any other interconnected facilities are identified in an
early stage and pro-actively managed to eliminate interference, disruptions or surprises
in the execution of the work and to maintain technical integrity of the Nawara Facilities.
It also describes the methodology to monitor the status and close out of interface
agreements documented in Interface Alignment Sheets.

The Interface Management Process is fully aligned with the Nawara Project Execution
Plan (NA-OTP-PMT-0000-PM-PLA-0001).

The key objectives of this Interface management procedure are:

Establishing a structured process for early interface identification, definition,

updates and alignment;

Interface management roles and responsibilities are clearly defined and informed
to all, and understood;

Interface requirements are clearly defined and agreed, including deliverables and
due dates.

Identified interface requirements are resolved in support of Project objectives and

validated before close out.

It is the responsibility of any Project Team Member from Company and Contractors
organisations to actively contribute and participate in the Interface Alignment process, in line
with responsibilities set and outlined in this procedure.

The effectiveness of the Interface Management process is verified by means of audits.

4/15
 OMV (Tunesien) Production GmbH

2 RESPONSIBILITIES

2.1 ASSET DEVELOPMENT MANAGER (ADM)

The ADM is responsible for the following:

Ensure that the Project Managers implement the Interface Management

Procedure.

Ensure that Interface Managers are appointed.

Ensure that Interface Management responsibilities are assigned to individuals

within the Projects organizations as necessary to ensure pro-active and thorough
communications with other Interface Parties.

Ensure that the Interface Management process works efficiently and effectively.

Ensure that all Stakeholders provide pro-active support and assistance,

individually and organizationally, to the Interface Manager to ensure successful
achievement of the Interface Management objectives.

Assist Interface Manager in facilitating resolution of interface matters.

Assist and expedite non-performing interface matters escalated by Interface

Manager to promote expeditious resolution.

Escalate and steward critical issues for steering and closure

2.2 PROJECT MANAGER (PM)

The Project Manager is responsible for the following

Ensure that the individual Project Management Teams and their Contractors and
Vendors implement the Interface Management Procedure.

Assign Interface Owners and single points of contact for the defined interfaces and
ensure that interface alignment sheets contains sufficient definition to enable
interfacing parties to proceed with execution of the works;

5/15
 OMV (Tunesien) Production GmbH

Act as Requestor or Supplier of Interface information for the external interfaces

with projects stakeholders;

Participate in the Interface Alignment Meeting and facilitate resolutions on interface

alignment process;

2.3 INTERFACE MANAGER (IM)

The Interface Manager is responsible for managing the Interface process and ensures
interfaces are identified, resolved and validated within the requested time and
according with the Interface deliveries schedule.

The Interface Manager responsibilities and functions include the following:

Verify that single points of contact are assigned to perform interfacing

responsibilities.

Identify critical interfaces, assess their importance, and assist in determining how
these will be managed.

Define the scope of work for each Interface Alignment Sheet and establish an
appropriate action plan.

Elevate non-performing interfaces to the Project Manager

Preparation and maintenance of the Interface Registers with interface and

schedule information.

Assess progress and status for Project Monthly Reporting

Call for Interface Meetings when required.

Coordinate, review, and provide input to the Program Schedule to reflect

performance of interface issues.

Ensure that the Interface Alignments are being executed as planned and steer the
performance of contactors and facilitate communication.

6/15
 OMV (Tunesien) Production GmbH

Monitor performance and effectiveness of Interface action plans.

Keep Project Manager informed of status, progress and performance

Prepare, review and obtain endorsement/approval and close out approval of

Interface Alignment Sheets. Raise MOC when requirement is identified by
interface issue

Communicate with Contacts and other Interface Managers to coordinate issues.

Drive the Project Team to supply agreed deliverables on schedule.

Drive interface issues to resolution.

Update and maintain the interface deliveries schedule

After the Requestor and Supplier reached a preliminary agreement, the Interface
Manager should communicate this to all relevant/concerned third and obtain
written confirmation of acceptance or request for amendments to that preliminary
agreement.

2.4 PROJECT SERVICES MANAGER (PSM)

The Project Services Manager will maintain this procedure in line with the Project
requirements and will schedule audits to verify its effectiveness.

2.5 PROJECT TEAM MEMBERS DISCIPLINE ENGINEERS

Depending on their position in accordance with the Interface Alignment Sheets

Project Team Discipline Engineers can either be Requestor or Supplier of
interface information;

The Receiver represents the party that issued the Interface Alignment Sheet
requesting the interface information and is responsible with the definition of
interface parameters;

7/15
 OMV (Tunesien) Production GmbH

The Supplier represents the party that received the Interface Alignment Sheet
requesting the interface information and is responsible for providing the required
interface information;

Both, Receiver and Supplier will ensure that all the information requested,
respectively provided in the Interface Alignment Sheet is delivered within the
requested quality, level of detail, without confusion and/or inadvertences and within
the agreed delivery time.

Both, Receiver and Supplier shall formalize the communications and the close-
out of interface alignment process through signed-off Interface Alignment Sheets.

3 INTERFACE MANAGEMENT PROCESS

3.1 INTERFACES

Interfaces occur where the work of two or more organizations or functions meet and
there is a need to describe who does what, when, and how, and the communication
flow involved.

These require coordination across organisational or physical boundaries to ensure

alignment and consistency between both sides of the boundary.

For the External Interfaces, which normally occur between Company and other
Organisations, the overall Interface Management is under Company responsibility,
which shall serve as a focal point between multiple Contractors and/or Organisations.

For the Internal Interfaces (interdisciplinary interfaces, inter-packages interfaces, etc.),

the Interface Management is under related Party responsibility, including the Project
Management Teams, EPC Contractors, 3rd party providers, etc.

Examples of interfaces are:

Physical interfaces, such as piping systems and tie-in points

8/15
 OMV (Tunesien) Production GmbH

System or functional interfaces, where systems go through several areas such as

SCADA (Supervisory Control and Data Acquisition), Telemetry and Emergency
Shutdown Systems

Logical Information interfaces, requiring exchanges and agreement on documents

or contracts between two organizations, such as design parameters, legal and
commercial agreements.

Organisational interfaces

Logistics Interfaces

For the Nawara Development Project the types of documents generated are the
following:

Interface Registers

Interface Alignment Sheets (IAS)

Interface Alignment Minutes of Meetings

The Interface Register and the Interface Alignment Sheets will be maintained and
periodically updated as documents on Aconex.

3.2 WORK PROCESS

In order to identify, record and close-out all Project Interfaces requiring alignment, a
specific project Interface Work Process was established. The process is described
below and pictured in the flow diagram present as Section 6 of this document:

3.2.1 STEP 1: INTERFACE REGISTER

IM will establish and update interface registers. These registers will contain all
interfaces identified in controlled documents such as specifications and drawings. All
controlled documents are maintained in Aconex. Changes to these input documents are
captured and included in the relevant interface registers. Interface registers are being
maintained and distributed to the individuals responsible for the timely completion of
interface alignment sheets.
9/15
 OMV (Tunesien) Production GmbH

3.2.2 STEP 2: INTERFACE ALIGNMENT SHEETS

Project Team Discipline Engineers generate the appropriate interface alignment sheets
(IAS). These will be developed describing commitments to be made by the Supplier
and Requestor with respect to the relevant deliverables such as engineering
information, requisitions or other pertinent project data as well as implementation of
new commitments and instructions.

The generated IAS is sent afterward to Interface Manager through an Aconex RFI.

3.2.3 STEP 3: TRANSFER OF INTERFACE DATA INTO REGISTER

The IM reviews the requested information and transfer the IAS content into the
Interface Register ensuring that one Interface is covered by a single discipline. In this
process, the related interface is given a code and the interface is set on IDENTIFIED.

3.2.4 STEP 4: TRANSFER OF INTERFACE DATA TO SUPPLIER

The IM reviews the interface required definitions from Requestor, sets interface status
on OPEN and seeks clarification from the Supplier of interface information. For this
purpose, a new IAS with revised status (OPEN) is generated and sent to Supplier. The
interface alignment sheets shall be discussed and finalized with the two parties involved
before sign off.

The Interface Manager facilitates in this process and establishes an action plan to
close out the work involved.

3.2.5 STEP 5: FEEDBACK FROM SUPPLIER

The Supplier of the interface information will review the IAS and either accepts or
rejects it.

a) In case of rejection the Supplier will make all required annotations,

changes or comments on the native IAS (xls) and return the IAS via a
RTRFI to the Interface Manager.

10/15
 OMV (Tunesien) Production GmbH

The Interface Manager will set the Interface to REJECTED and seek
clarification with the Requestor.

b) In case of acceptance the Supplier will prepare a response providing the

requested information, print, and sign and send it via RTRFI to the
Interface Manager.

When the signed IAS is received the Interface Manager sets the status to
SUBMITTED.

The Interface Manager is responsible for tracking all IAS and for expediting the delivery
of the requested information.

3.2.6 STEP 6: ALIGNMENT OF SUPPLIER DATA WITH REQUESTOR

The Interface Manager reviews the submitted IAS verifies that the received response
is acceptable. He then submits the IAS to the Requestor, who also checks the IAS. In
case that the submitted IAS is fully accepted the Requestor signs the IAS and submits it
to Step 7. In case the submitted and signed IAS is not accepted by the Requestor, the
Interface Manager sets the IAS status to OPEN and submits it via an RFI to the
Supplier for further processing. This is an iterative process and it may take more rounds
until the parties agree on the interface definition.

3.2.7 STEP 7: INTERFACE CLOSE-OUT AND DISTRIBUTION FIA

When all Interface Information is complete as agreed and signed by Requestor and
Supplier, the Interface Manager sets the interface status to CLOSED, updates the
Interface Register and sends a fully signed IAS to Supplier and Receiver, for
information and action.

All IAS files (pdf) need to be registered as documents in Aconex and all document
transmissions need to be performed using Aconex.

11/15
 OMV (Tunesien) Production GmbH

4 MANAGEMENT OF INTERFACE REGISTERS

The Overall Nawara Projects Interface Register is a MS Excel Spread sheet stored in
Aconex. It provides information regarding all Interfaces and their individual parameters.
The Aconex Document Number is NA-OTP-PMT-0000-PM-REG-0006 Nawara
Development Interface Register. This is a Company internal document, periodically
maintained and updated by IM.

Each stand-alone project, part of Nawara Development Projects, will have a dedicated
interface register, to be used in the alignment process with each of the external
interfaces parties (i.e. LLI Suppliers, EPC Contractors, etc.). These registers shall be
derived from the Overall Register and shall serve as a base for each Contractors own
Interface Management Process and shall be part of each Contractors Monthly Report.

Interface Manager is responsible for the alignment of the individual registers with
Nawara Development Overall Interface Register.

The Interface Register template to be used in the Interface Management Process is

presented in Section 7 of this document.

5 MANAGEMENT OF INTERFACE ALIGNMENT SHEET

The Nawara Development Project maintains a template for the IAS as part of the MS
Excel based Interface Database file on. Whenever an interface requiring clarification is
identified a new IAS is created based upon this template and stored on Aconex as a
new document with the number automatically generated based upon the Interface
Database entries.

The Interface Alignment Sheet template to be used in the Interface Management

Process is presented in Section 8 of this document.

12/15
 OMV (Tunesien) Production GmbH

6 INTERFACE ALIGNMENT PROCESS FLOW DIAGRAM

INTERFACE MANAGEMENT
INTERFACE ALIGNMENT PROCESS FLOW DIAGRAM

Requestor Interface Manager Supplier

ESTABLISH
1 Interface Register

Generate the IAS and

2 Send xls file it through RFI
Request for Information (RFI)

Transfer Information into

3 Interface Register
SET Status: IDENTIFIED
RTRFI

Check if Interface
Clarify with Requestor NO data is OK?

YES

4 1. Set Status OPEN

2. Re-issue IAS IAS content OK?
RFI
3. Send IAS to Supplier (xls file)
(xls file)

5a
NO
Set Status
IAS returned
REJECTED YES
with comments

NO 5b
Signed Pdf Set Status Signed Pdf Prepare Response
6 Response OK?
via RFI SUBMITTED via RTRFI and sign IAS

YES
7
Update Interface
Signed Pdf
Sign IAS Register
Via RTRFI
Set Status: CLOSED

Signed Pdf
Via FIA

Issue signed IAS to all parties via Aconex

13/15
 OMV (Tunesien) Production GmbH

7 INTERFACE REGISTER TEMPLATE

14/15
 OMV (Tunesien) Production GmbH

8 INTERFACE ALIGNMENT SHEET TEMPLATE

15/15