RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF. RLNG-000-PM-PP-1105
CONTRACTOR DOC. REF.
215122C-000-PP-1105
REVISION: 0A
PAGE 1 OF 53
ADNOC GAS
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY Contract No.
4700022871
JV TJN RUWAIS Contract No
215122C
Document Class Document Category (for Class 1)
Class 2
OPERATING CENTER Contract No.
OPERATING CENTER Doc Ref.
0A
ICR - Issued for Client Review
30-Sep-2024 D.Sivaprakasam A.De-Vandiere
T.Sakamoto M.Vallivel
0
ICR - Issued for Client Review
02-Jul-2024 D.Sivaprakasam
F.Peron
S.Deilles A.De-Vandiere
S.Deilles A.De-Vandiere
Rev.
Revision Purpose
Date
Prepared by
Checked by
Approved by
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF. RLNG-000-PM-PP-1105
CONTRACTOR DOC. REF.
215122C-000-PP-1105
REVISION: 0A
PAGE 2 OF 53
Contents
Page
Table of Contents
1.0
INTRODUCTION… 5 Project Objective and Location … 5 1.1 Purpose and Scope of the Document … 5 1.2 1.3 Holds List … 6 1.4 References … 6 1.5 Definitions and Abbreviations … 6 2.0 FUNCTIONS & RESPONSIBILITIES … 7 2.1 Document Control Centre … 7 Preparation and checking of documents … 8 2.2 2.3 Approval of documents … 8 2.4 Writer/Checker/Approver Signature of YOC … 8 Issue of CDR on a monthly basis … 9 2.5 3.0 ELECTRONIC DOCUMENT MANAGEMENT SYSTEM (EDMS) … 9 3.1 Document Control Centre … 9 Engineering Document Workflow for POC Documents … 10 3.2 Engineering Document Workflow for YOC Documents … 11 3.3 3.4 Engineering Document Workflow for ADOC Documents … 12 Engineering Module … 14 3.5 3.5.1 General Presentation … 14 3.5.2 Document Preparation … 14 3.6 Internal Review Process … 14 Internal Approval Process … 15 3.7 3.8 Conformity Check … 15 3.9 Distribution Management Process … 15 3.9.1 Document Distribution Matrix … 15 3.9.2 Transmission to CONTRACTOR … 16 3.9.3 Transmission to COMPANY … 16 3.10 Document States in GAIA … 16 3.11 Confidentiality Levels … 17 4.0 COMPANY COMMENTS MANAGEMENT on CONTRACTOR DOCUMENTS … 17 4.1 COMPANY Comments Process … 17 4.2 COMPANY Review Period … 18 4.3 COMPANY Comments Receipt … 18 4.4 CONTRACTOR Response … 18 4.5 COMPANY Comments Review Codes … 19 4.6 Comments Response Sheet Management … 19 4.7 Comments Response Sheet Distribution … 19 4.8 YOC/ADOC Engineering Documents Comments Management … 19 4.9 COMPANY Comments and CONTRACTOR Response (CRS) Workflow for POC Documents … 20 4.10 COMPANY Comments and CONTRACTOR Response (CRS) Workflow for YOC Documents … 21 4.11 COMPANY Comments and CONTRACTOR Response (CRS) Workflow for ADOC & NMDC Documents … 22 5.0 RESPONSE TO CRS BY DISCIPLINES … 24 Principles … 24
5.1
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF. RLNG-000-PM-PP-1105
CONTRACTOR DOC. REF.
215122C-000-PP-1105
REVISION: 0A
PAGE 3 OF 53
8.1
8.3
5.2 Recording of CRS in GAIA while issuing a document … 24 5.3 Recording of CRS in GAIA for a document not reissued … 24 6.0 COMPANY COMMENT CATEGORIZATION (INTERNAL FOR CONTRACTOR) … 24 6.1 Principles … 24 6.2 Critical Documents … 24 6.3 Categorization of Comments (for Critical Documents) … 25 6.4 Recording of Comments Category in GAIA … 25 7.0 EXTERNAL MODULE … 25 7.1 COMPANY Comment Management for TQ/DCA/RFI … 26 TQ/DCA/RFI Document and Comments Workflow for CONTRACTOR (TJN) … 27 7.2 8.0 VENDOR MODULE … 28 Vendor Document Workflow for POC Documents (POC Requisitions-Leader) (This workflow is continued in the next page):TYPE - 1 REQUISITIONS … 29 8.2 Vendor Document Workflow for YOC Documents (YOC Requisitions-Leader): TYPE - 1 REQUISITIONS - FOR COMPANY REVIEW … 31 Vendor Document Workflow for YOC Documents (YOC Requisitions-Leader): TYPE - 1 REQUISITIONS - FOR COMPANY INFORMATION … 32 Vendor Document Workflow for ADOC Requisitions (NMDC Requisitions managed by ADOC): TYPE - 1 REQUISITIONS … 33 Vendor Document Workflow for POC Documents (POC Requisitions-Leader) (This workflow is continued in the next page): TYPE - 2 & 3 REQUISITIONS … 35 Vendor Document Workflow for YOC Documents (YOC Requisitions-Leader): TYPE -2 & 3 REQUISITIONS: FOR COMPANY REVIEW … 37 Vendor Document Workflow for YOC Documents (YOC Requisitions-Leader): TYPE -2 & 3 REQUISITIONS - FOR COMPANY INFORMATION … 38 Vendor Document Workflow for ADOC Documents (ADOC Requisitions-Leader) (This workflow is continued in the next page): TYPE -2 & 3 REQUISITIONS … 39 8.9 COMPANY’s Comment on Vendor Documents/Comments Transmission from CONTRACTOR to VENDOR – Workflow with Steps … 41 9.0 CONTRACTOR DOCUMENT REGISTER … 45 10.0 DOCUMENT AND DRAWING TEMPLATES … 45 APPENDIX 1 – CDR TEMPLATE … 46 APPENDIX 2 – CRS TEMPLATE … 47 APPENDIX 3 – DOCUMENT TEMPLATES … 48 WORD/EXCEL/DRAWING/TQ/DCA/RFI SPECIMEN … 48
8.7
8.5
8.6
8.4
8.8
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF. RLNG-000-PM-PP-1105
CONTRACTOR DOC. REF.
215122C-000-PP-1105
REVISION: 0A
PAGE 4 OF 53
Table of Changes compared to previous revision (for Procedures and Job Specifications only)
Paragraph
Modification description
Remarks / Origin
Added Vendor Document Workflows of POC, YOC, ADOC for Type 1 Requisitions
Added Vendor Document Workflows of POC, YOC, ADOC for Type 2 & 3 Requisitions
Added COMPANY’s Comment on Vendor Documents/Comments Transmission from CONTRACTOR to VENDOR – Workflow with Steps
Added Template Specimens of TQ/RFI/DCA
Engineering Documents Workflows Updated
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF. RLNG-000-PM-PP-1105
CONTRACTOR DOC. REF.
215122C-000-PP-1105
REVISION: 0A
PAGE 5 OF 53
1.0
INTRODUCTION
1.1 Project Objective and Location
The ADNOC Ruwais LNG Project is a two train, near net-zero electrically driven LNG facility, targeting international markets. The feed gas for the project is supplied from the Habshan Gas Processing Plant via a new export gas pipeline. The plant will have two 4.8 MTPA (nominal capacity) electric driven LGN Trains with associated LNG storage/marine export facilities and utilities.
The ADNOC Ruwais LNG Project foresees the following main components at the facility:
➢ Onshore LNG Liquefaction facilities for 2 x 4.8 MTPA electrically driven LNG Trains
(9.6MTPA total)
➢ Common facilities including inlet receiving facilities, LNG storage, BOG handling, flare,
refrigerant storage and support buildings.
➢ Utilities to support the facilities including import power from the national grid.
➢ Marine facilities for LNG export and bunkering.
1.2 Purpose and Scope of the Document
The purpose of this document is to provide the principles as well as the simple instructions relevant to the managing and control, distribution and recording of all Project & Engineering Documents, Vendor and Subcontractor documents through GAIA EDMS (Electronic Document Management System) for ADNOC Ruwais LNG Project.
This Procedure and its requirements apply to documents listed below:
➢ Project Management procedures
➢ Engineering deliverables
➢ COMPANY comments on Engineering and Project documents ➢ VENDOR documents (these are produced by Equipment/Material manufacturers or
suppliers)
➢ SUBCONTRACTOR documents (these are documents required from SUBCONTRACTOR
in accordance with the SUBCONTRACTOR exhibits requirements)
➢ Approval documents (approved documents from the Regulatory Authorities, typically
permits, certificates, inspection results, etc.)
This procedure excludes :
➢ Project correspondence and Minutes of Meetings, whether external or internal (these are managed through the Correspondence Module in GAIA and are managed by the T.EN Secretary)
➢ Cost control documents (budget control report etc.) ➢ Commercial documents
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF. RLNG-000-PM-PP-1105
CONTRACTOR DOC. REF.
215122C-000-PP-1105
REVISION: 0A
PAGE 6 OF 53
1.3 Holds List
HOLD
DESCRIPTION
1
YOC/ADOC/NMDC CDR Management Workflows
1.4 References
Document Number Project Documents RLNG-000-PM-PP-1102 RLNG-000-PM-PP-2003 RLNG-000-PM-NM-1105 RLNG-000-PM-SP-2302 RLNG-000-PM-SP-2303 RLNG-000-PM-SP-2402
215122C-000-WI-1106 215122C-000-WI-2101
Document Title
Document Identification and Numbering Procedure Equipment and Component Numbering Procedure Contractor Document Register Instructions concerning Vendor Documents Management and Review Final Vendor Documentation Requirements Procedure Instructions concerning Subcontractor Documents Management and Review Management of COMPANY Comments Issue of Deviation Concession Request (DCA), Technical Query (TQ) and Request for Information (RFI)
Agreement Annexures 10F-04-00-0A-Annexure 10F-4 Document Control Procedure 10F-01-00-0A-Annexure 10F-1 Reviews, Comments & Approvals
1.5 Definitions and Abbreviations
Abbreviation/Acronyms COMPANY
CONTRACTOR
LNTP EPC ADOC POC YOC Project
EDMS
COMPANY EDMS DCC DCM IT Manager IM LDE PM DIC IDC TN AVEVA Engineering EPC Business JANUS
Meaning
COMPANY - ABU DHABI NATIONAL OIL COMPANY (ADNOC) P.J.S.C. CONTRACTOR - TJN Ruwais, Joint Venture of Technip Energies France-Abu Dhabi, JGC Corporation and National Marine Dredging Company (NMDC) Limited Notice to Proceed Engineering Procurement Construction Abu Dhabi Operating centre - National Marine Dredging Company (NMDC) Paris Operating Centre - Technip Energies Yokohama Operating Centre - JGC Corporation Ruwais LNG Project
Electronic Document Management System (GAIA)
ACONEX Document Control Centre Document Control Manager Information Technology Manager Information Management Lead Discipline Engineer Project Manager Discipline Internal Check Inter Discipline Check Transmittal Note CONTRACTOR Internal Electronic tool for CDR Generation Web application tool for communication between Procurement and VENDORS Progress Measurement Software
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF. RLNG-000-PM-PP-1105
CONTRACTOR DOC. REF.
215122C-000-PP-1105
REVISION: 0A
PAGE 7 OF 53
Abbreviation/Acronyms SMARTPLANT CDR MDI CRS VENDOR MR
MR-Type Requisition
1-Single
MR-Type Requisition
2-Multiple
MR-Type 3-Consolidated Requisition
Meaning
Requisition Follow-up Software (SPMAT) CONTRACTOR Document Register Master Document Index Comment Response Sheet Manufacture and / or Supplier of Equipment or Material Material Requisition Single Requisition means the requisition for inquiry/purchase which covers only Equipment and/or Material of one Partner i.e. TEN, JGC or NMDC. The corresponding Engineering and Procurement activities related to this Single Requisition shall be handled by this Partner. Multiple Requisition means the requisition for inquiry/purchase which covers Equipment and/or Tagged Material of two or multiple Partners. One Partner will lead the MR and will issue the Main MR which include Secondary MR(s). The other Partner(s) not leading will issue Secondary MR(s) specific to their scope to the MR lead and will support Requisition Leader for pre-order and post order activities such as but not limited to: Requisition preparation, Clarifications, TBE, Vendor Documentation Review related to its own scope of works. Consolidated Requisition means the requisition for inquiry/purchase which covers Equipment or Bulk Material (other than steel structure) of multiple Partners consolidated in one single Requisition. Designated Partner Requisition Leader is responsible to consolidate input data from the other Partner(s). The other Partner(s) not leading the MR will issue Equipment specific documents (such as Data Sheet, etc…) only or Bulk Material BOM of its scope to this Partner Requisition Leader. The corresponding Procurement activities shall be handled by this Partner Requisition Leader.
2.0
FUNCTIONS & RESPONSIBILITIES
2.1 Document Control Centre
The CONTRACTOR DCC is responsible to:
➢ Define workflows to fulfil both project and COMPANY requirements for document
management,
➢ Set-up GAIA for project team use, ➢ Write document control procedures, ➢ Ensure that the defined parameters are in accordance with the Project needs, ➢ Manage the access rights in GAIA, ➢ Manage the distribution matrices in GAIA in coordination with disciplines, ➢ Support Project team to use GAIA following their needs, ➢ Create document masters in GAIA and support the Originator of a document in importing the
final deliverables list with document references in document master in GAIA
➢ Check that the Quality of the documents received with regards to a specific check list and to
be transmitted are signed and follow the Project rules,
➢ Register the documents (PDF, native files and CRS) in GAIA for transmittal, ➢ Prepare the transmittals in GAIA, ➢ Send the electronic notifications from GAIA Engineering Document module to both CONTRACTOR Recipients and COMPANY. Upload the documents to COMPANY EDMS (ACONEX) with all required attributes supporting documents (and CRS where necessary), and initiate Workflow Transmittal for COMPANY’s review,
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF. RLNG-000-PM-PP-1105
CONTRACTOR DOC. REF.
215122C-000-PP-1105
REVISION: 0A
PAGE 8 OF 53
➢ Centralise and record in GAIA the receipt and transmittal of COMPANY comments (and
replies when needed),
➢ Centralise the receipt and transmittal of the Interfaces documents (if applicable in the Project). CONTRACTOR DCC is responsible to manage document to/from CPY. Each OC DCC is responsible to manage the document flow within the OC.
2.2 Preparation and checking of documents
The Originator of a document manages the creation of document masters and creation of document in GAIA. DCC Supports the Originator in importing the final deliverables list with document references in document master in GAIA.
He/she checks the documents before issuance. He/she is also generally identified as the checker of the documents, and sometimes the approver also when necessary.
The Originator is responsible for:
➢ Respecting COMPANY Specifications and Project Procedures to create documents ➢ Register the document (native, PDF file, CRS Reply, as applicable, for upper revisions) in
GAIA while creating the Engineering document,
➢ Send the PDF file for electronic signature to the checker and the approver of the document, ➢ Send the signed PDF file, as well as native files through GAIA for Conformity Check and for
its official issuance to COMPANY.
2.3 Approval of documents
An Approval Team is in charge to approve the deliverables before issuance. This team is typically composed of:
➢ Project Team Members (PMTs), ➢ Project Discipline Lead Engineers (LDEs), ➢ Head of Departments (HODs) or by delegation Subject Matter Experts (SMEs) or group
leaders.
The Approval Team composition is set-up according to Contractor internal quality system and procedures.
Each approver is responsible of the following:
➢ Verify that the document was duly checked by a qualified person before being submitted to approval (qualification of checker being according to Contractor’s quality system and procedures),
➢ Verify that the document is matching the COMPANY and CONTRACTOR expectations and in line with general CONTRACTOR quality requirements in terms of format and content,
➢ Approve the document before issuance, ➢ Send back the document to the issuing discipline with comments if not approved for
submission.
2.4 Writer/Checker/Approver Signature of YOC
For YOC documents, Writer/Checker/Approver signature shall be replaced by JDMS stamp which confirms that Writing/Checking/Approving cycle has been completed. A document with JDMS stamp implies : The document is authorized by YOC.
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF. RLNG-000-PM-PP-1105
CONTRACTOR DOC. REF.
215122C-000-PP-1105
REVISION: 0A
PAGE 9 OF 53
2.5 Issue of CDR on a monthly basis
Document Control is in charge of:
➢ Set-up AVEVA Engineering with IM support to manage CDI for CDR generation, ➢ Collect OC CDR other than the one of POC which will be already directly managed through
AVEVA Engineering
➢ Support disciplines in the registration of document in the CDR, ➢ Set-up Power BI for Project reporting, ➢
Issue CDR to COMPANY
3.0
ELECTRONIC DOCUMENT MANAGEMENT SYSTEM (EDMS)
3.1 Document Control Centre
All documents produced by CONTRACTOR, VENDOR, SUBCONTRACTOR and COMPANY will be in English.
GAIA is the Electronic Document Management System used by CONTRACTOR . It manages all project documentation related to Engineering, Vendor, External Parties and Correspondences within one application.
GAIA is a web-based document management system and can be accessed from anywhere through Edge, Google Chrome and Firefox, as long as the user is equipped with the proper system requirements.
GAIA users need to be equipped with high-speed internet connection.
(Each OC will manage their own EDMS before transmitting the documents to GAIA)
Link to GAIA is given below: Login to GAIA_TPPLM_PROD - Lascom PLM (technipenergies.com)
The Documents modules created in GAIA for this Project are the following:
➢ Engineering Document Module ➢ Comments and Transmission which is part of Engineering module: it allows comments storage, transmission, follow-up of COMPANY Comments and CONTRACTOR Replies.
➢ Vendor Module ➢ Subcontractor Module ➢ External Module – Technical Queries and Deviation Requests are managed in External
Module
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF. RLNG-000-PM-PP-1105
CONTRACTOR DOC. REF.
215122C-000-PP-1105
REVISION: 0A
PAGE 10 OF 53
3.2 Engineering Document Workflow for POC Documents
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF. RLNG-000-PM-PP-1105
CONTRACTOR DOC. REF.
215122C-000-PP-1105
REVISION: 0A
PAGE 11 OF 53
3.3 Engineering Document Workflow for YOC Documents
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF. RLNG-000-PM-PP-1105
CONTRACTOR DOC. REF.
215122C-000-PP-1105
REVISION: 0A
PAGE 12 OF 53
3.4 Engineering Document Workflow for ADOC Documents
ADOC documents will be Managed through GAIA for NT Energies Document and through NMDC EDMS for documents produced by NMDC.
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF. RLNG-000-PM-PP-1105
CONTRACTOR DOC. REF.
215122C-000-PP-1105
REVISION: 0A
PAGE 13 OF 53
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF. RLNG-000-PM-PP-1105
CONTRACTOR DOC. REF.
215122C-000-PP-1105
REVISION: 0A
PAGE 14 OF 53
3.5 Engineering Module
3.5.1 General Presentation
The engineering module in GAIA will store all CONTRACTOR Project and Engineering documents related to CONTRACTOR scope of work, as identified in the CDR.
The DCC will manage Engineering module to provide every authorized person with an access and will update their access during project life.
The relevant documents will be officially issued to COMPANY through GAIA, and COMPANY will have access to both Native and PDF versions of all Documents issued under transmittals to COMPANY through GAIA Notification.
In addition to GAIA notification, CONTRACTOR shall upload the officially issued documents from GAIA to ACONEX (COMPANY EDMS) and initiate Workflow Transmittal for COMPANY review.
The documents are basically Project Management and Engineering deliverables, with the following exceptions:
➢ Cost control documents (budget control report etc.), ➢ Commercial documents (including support documents like technical bid tabulation…), ➢ External or internal progress reports, ➢ Vendor Documents (Managed in Vendor module in GAIA, refer to Section 8), ➢ Project Correspondence, whether external or
internal (these are managed by
correspondence module in GAIA that are managed by CONTRACTOR secretary).
The main functions of the Engineering module are as follows:
➢ Logging of all documents, to allow an easy retrieval and an efficient follow-up of their status
(different revisions),
➢ Prepare their formal dispatch: internal or external by means of transmittal notes, ➢ Store the document in electronic format to allow authorized parties to view them from their
computer,
➢ Prepare Final Engineering Project documentation.
3.5.2 Document Preparation
In GAIA Engineering Doc, a discipline can see only documents from its own discipline before documents are officially issued. Once documents have the state “Issued” (transmitted officially with a transmittal), they are visible to all disciplines.
Document cards are created by the DCC and are available in the “Engineering Doc. Masters” object. Once documents are created by the discipline issuer, they will be available in the “Engineering Doc.” Object and its state will show as “Under Preparation”.
3.6 Internal Review Process
Prior to COMPANY issue, each document will be subject to an internal review process:
➢ Discipline Internal Check (DIC) ➢ ➢
Inter-Discipline Check (IDC) if applicable, as per each Operating Centre Quality System Inter Operating Centre Check (IOCC), if applicable, as per Internal Rules of Approval for Engineering Documentation (215122C-000-PP-2020)
Comments can be stored in GAIA or in the discipline folder managed by the disciplines as applicable.
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF. RLNG-000-PM-PP-1105
CONTRACTOR DOC. REF.
215122C-000-PP-1105
REVISION: 0A
PAGE 15 OF 53
3.7 Internal Approval Process
Each document in PDF format is electronically signed by 3 persons at least:
➢ The document originator, who signs in the tab “Prepared By” or “Written By”; ➢ The document checker, who signs in the tab “Checked By”; ➢ The document approver, who signs in the tab “Approved By”.
The originator (Writer) and the checker shall be two different people. Approval/Checking shall be as per each OC’s Quality Management System.
3.8 Conformity Check
Once document is signed, it should be sent by Discipline to DCC for Conformity Check (CC) . Note that the document can also be signed outside of GAIA and sent to Conformity Check directly.
On receipt of the signed document, DCC will check:
➢ That the electronic files received reflects the correct information (metadata) defined in the document card and that all the data are in accordance with the CDR and Document Identification and Numbering Procedure;
➢ That the native files and the CRS reply in addition to one full PDF are attached to the
document card.
➢ That the electronic files are saved under the correct reference Number and Revision. ➢ That the PDF file is electronically signed. ➢ The File naming convention for PDF/Native/CRS are followed as per the below examples:
a) RLNG-000-PM-TOR-2100_1.pdf b) RLNG-000-PM-TOR-2100_1_CRS c) RLNG-000-PM-TOR-2100_1 (single native file) d) RLNG-000-PM-TOR-2100_1_Native File. Zip (If there are multiple native
attachments, to zip the native)
If the document is not in compliance with the requirements, it will be rejected. The document originator will have to reissue it correctly.
If the document is compliant, it is validated inside GAIA.
DCC will then issue the document in GAIA as follows:
➢
the document is sent under the cover of a transmittal note internally and to COMPANY according to their recipients list for information only.
3.9 Distribution Management Process
3.9.1 Document Distribution Matrix
The Document Matrix defines the recipients of each document. It is the guarantee of a consistent document distribution also completed by individual electronic notifications.
The matrix is a transmission grid applicable to the project, defining the recipients and the transmittal addresses for each type of document.
The matrices implemented in GAIA by the DCC are:
➢ The Engineering Document Distribution Matrix ➢ The Vendor Document Distribution Matrix
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF. RLNG-000-PM-PP-1105
CONTRACTOR DOC. REF.
215122C-000-PP-1105
REVISION: 0A
PAGE 16 OF 53
The matrix is updated when necessary to reflect the project life.
3.9.2 Transmission to CONTRACTOR
Once the document is electronically signed, the Transmittal Note is prepared by DCC and is transmitted internally and for information, based on the distribution matrix defined for the Project.
The Transmittal Notes are notified electronically only, and 1 email is generated (and automatically sent to all the recipients) for each Transmittal Note. The Notification contains a weblink to each Document Card and the document inside GAIA.
The Transmittal Note may contain one or several documents.
The Internal Transmittal Prefixes in GAIA are:
a) 215122C-TEN-TN-XXXXX for Engineering documents issuance b) 215122C-TEN-TN-C-XXXXX for Comments transmittal c) 215122C-TEN-TN-RC-XXXXX for Replies transmittals
3.9.3 Transmission to COMPANY
When COMPANY shall be notified of the Document, the DCC add a specific transmittal prefix (dedicated to COMPANY) in the Internal Transmittal Note and sends the Transmittal Note to COMPANY directly from GAIA for COMPANY information only. In addition to the notification from GAIA, CONTRACTOR uploads the document in COMPANY EDMS (ACONEX) and initiate Workflow Transmittal for COMPANY review. CONTRACTOR to ensure to put correct attributes into ACONEX and attach the required documents prior to issuance of document for COMPANY review. COMPANY will consider the official submission of deliverables once CONTRACTOR sends it to COMPANY EDMS (ACONEX) only.
The Specific transmittal prefixes are:
215122C-TEN-ADNOC-TN-XXXXX for Engineering documents issuance
3.10 Document States in GAIA
Throughout a document’s lifecycle, the State attribute will change to indicate the current step. For example, an Engineering Doc. that is currently being signed through a Sign/CC will have the state “Under Signature”.
States can be viewed from the layout and in the document card.
The states used in GAIA are the following:
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF. RLNG-000-PM-PP-1105
CONTRACTOR DOC. REF.
215122C-000-PP-1105
REVISION: 0A
PAGE 17 OF 53
3.11 Confidentiality Levels
In Ruwais Project EDMS (GAIA), documents are classified with the following labels :
Labels in EDMS (GAIA)
Classification Associated Document Class
Level 2.2-Confidential Particular Restriction Confidential
Class 1(For Approval)
Class 2 (For Review)
Class 3 (For Information)
Level 2.3-Confidential Particular Restriction Confidential
Class 4 (Internal JV)
Level 3-Internal Confidential
Confidential
Class 5 (Internal-POC)
4.0
COMPANY COMMENTS MANAGEMENT ON CONTRACTOR DOCUMENTS
4.1 COMPANY Comments Process
All COMPANY comments are stored, distributed and accessed in GAIA, under Engineering Comments and Transmissions.
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF. RLNG-000-PM-PP-1105
CONTRACTOR DOC. REF.
215122C-000-PP-1105
REVISION: 0A
PAGE 18 OF 53
Required Action:
Documents are transmitted to COMPANY with a required action, indicated in the field ‘Required Action’ in GAIA.
The 2 different kinds of actions required from COMPANY are the following:
➢ For Review – Class 1/2 documents ➢ For Information only – Class 3 documents
The required action is also indicated in the Transmittal Note issued via GAIA.
Comments are received from COMPANY under the format of mark-up on the PDF file and are transferred to CRS under Excel by the DCC. DCC distributes the CRS to the LDE in charge as per Section 4.9 -COMPANY Comments and Contractor Response (CRS) Workflow for T.EN Documents For critical documents, each comment from the CRS is analysed and categorized by the comment’s owner. The categorization values are indicated in the CRS.
For non-critical documents, analyze and categorization of comments in the CRS is not required.
All COMPANY comments (both critical and non-critical) are captured and then replied in the CRS. The filled-in CRS is sent back to COMPANY no later than at the time of reissuance of the document.
4.2 COMPANY Review Period
COMPANY Review period is 10 Working days from the date of receipt, unless otherwise specified in the agreement.
4.3 COMPANY Comments Receipt
Upon submission of documents and after comments have been consolidated by COMPANY in PDF documents are returned to DCC through ACONEX notification in DCC Mailbox. CONTRACTOR DCC shall download the comments from ACONEX, extracts COMPANY Comments in CRS Excel file, records in GAIA and notifies to CONTRACTOR recipients.
Each delivery sent by COMPANY to CONTRACTOR will include a weblink, leading to a zip folder, named after the COMPANY Transmittal reference, and containing:
➢ The related documents commented in PDF format as “mark-ups”, containing the
COMPANY review code on the first page of the document
The PDF containing COMPANY review are named with their original COMPANY document reference and revision, with the addition of the letter C.
Example: RLNG-000-PM-PP-1102_0_C
The CRS containing COMPANY review are named with their original COMPANY document reference and revision, with the addition of the COMPANY review code (Code 1/2/3/4) and the prefix “_CRS”.
Example : XXXXX-XX-000-PM-PP-1102_0_CRS_CODE X
4.4 CONTRACTOR Response
Contractor Response shall be provided along with the revised/new revision of the document.
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF. RLNG-000-PM-PP-1105
CONTRACTOR DOC. REF.
215122C-000-PP-1105
REVISION: 0A
PAGE 19 OF 53
4.5 COMPANY Comments Review Codes
The Review Codes from COMPANY are detailed in the following table:
Codes
Meaning
Action
Code 1 Rejected
Revise and resubmit
Code 2 Comments as noted Work may proceed subject to compliance with and incorporation
of comments
Code 3 No Comments
Work may proceed
Code 4
Information only
Accepted for information only
Contractor shall be responsible to transfer company comments provided as mark-up through transmittal, handwritten in review/specialist review meetings, Comments captured in MOM/Action list of review meeting. In the form of comments resolution sheet with appropriate references, to address company comments for its resolution and approval by company.
4.6 Comments Response Sheet Management
The CRS is generated by TEN DCC from commented PDF received from Company: Contractor discipline shall fill in replies to COMPANY comments for each individual comment.
The CRS generated is renamed by CONTRACTOR by adding the suffix “_R” when replied.
Example : RLNG-000-PM-PP-1102_CRS_CODE X_Reply.xlsx
4.7 Comments Response Sheet Distribution
At the update of the Project or Engineering document in upper revision, the CRS responded is attached as an additional document within the “native file” section in GAIA before the sending of the document in electronic signature workflow.
It is then transmitted to COMPANY along with the document in upper revision.
4.8 YOC/ADOC Engineering Documents Comments Management
On receipt of COMPANY Comments notification from ACONEX for Partners documents, TEN DCC extracts COMPANY comments in CRS Excel file and records the COMPANY Commented PDF and CRS in GAIA Engineering Comments and Transmission object and transmits the comments to the Partners recipients.
For critical documents, each comment from the CRS is analysed and categorized by the comment’s owner. The categorization values are indicated in the CRS.
For non-critical documents, analyses and categorization of comments in the CRS is not required.
All comments (both critical and non-critical) are then replied in the CRS. The filled-in CRS is sent back to COMPANY no later than at the time of reissuance of the document.
Refer Working Instruction 215122C-000-WI-1106 for details on COMPANY Comment Categorization and the process of submission to TEN DCC.
Refer Section 4.10, 4.11 & 4.12 - Comments and Response (CRS) Workflow for YOC, ADOC, NMDC Documents, for Comments Management Workflows for Partners.
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF.
CONTRACTOR DOC. REF.
RLNG-000-PM-PP-1105
215122C-000-PP-1105
REVISION: 0A
PAGE 20 OF 53
4.9 COMPANY Comments and CONTRACTOR Response (CRS) Workflow for POC Documents
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF.
CONTRACTOR DOC. REF.
RLNG-000-PM-PP-1105
215122C-000-PP-1105
REVISION: 0A
PAGE 21 OF 53
4.10 COMPANY Comments and CONTRACTOR Response (CRS) Workflow for YOC Documents
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF.
CONTRACTOR DOC. REF.
RLNG-000-PM-PP-1105
215122C-000-PP-1105
REVISION: 0A
PAGE 22 OF 53
4.11 COMPANY Comments and CONTRACTOR Response (CRS) Workflow for ADOC & NMDC Documents
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF.
CONTRACTOR DOC. REF.
RLNG-000-PM-PP-1105
215122C-000-PP-1105
REVISION: 0A
PAGE 23 OF 53
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF. RLNG-000-PM-PP-1105
CONTRACTOR DOC. REF.
215122C-000-PP-1105
REVISION: 0A
PAGE 24 OF 53
5.0
RESPONSE TO CRS BY DISCIPLINES
5.1 Principles
COMPANY comments on deliverables are formally answered even if all COMPANY comments are incorporated in the next revision of the deliverable.
As per ACONEX requirement, the CRS shall be provided along with the revised document. Thus, CRS shall be loaded in GAIA and ACONEX at same time as the revised document.
In case some clarifications are required on the content of the CRS, it shall be managed by LDE directly with their COMPANY counterpart, preferably during weekly meeting (or by e-mail) prior to formal re-issue of updated document.
5.2 Recording of CRS in GAIA while issuing a document
For POC, the replied CRS shall be attached along with the native and PDF files in the Related file tab in GAIA.
For ADOC and YOC, the replied CRS shall be provided along with the native and PDF files through SharePoint to T.EN Doc Control, who will record them in Gaia.
The file naming convention that are to be followed for CRS Replies are as follows:
Company document reference_Rev_CRS_Code X_Reply
Example: RLNG-000-PP-1102_0_CRS_Code 2_Reply
5.3 Recording of CRS in GAIA for a document not reissued
In case it is agreed with COMPANY not to reissue the document, a specific work process shall be followed to record the CRS REPLY in GAIA by Disciplines.
The CRS shall be attached to the Comments Card in GAIA using the Related Files tab :
➢ For POC, Discipline shall open the concerned document in GAIA Comments Module with a filter Comments Transmitted, attached the CRS and send it to CC (Conformity Check by the Doc Control) – refer to Working Instruction on how to record CRS Reply in GAIA : 215122C-000-WI-1106
➢ For ADOC and YOC, Discipline shall provide the CRS through the SharePoint to POC Doc Control, who will record it in Gaia. However, YOC discipline has to send this CRS Reply to their COMPANY counterpart as explained in Section 15.4.- Comments and Response (CRS) Workflow for JV Partners Documents.
6.0
COMPANY COMMENT CATEGORIZATION (INTERNAL FOR CONTRACTOR)
6.1 Principles
Throughout the project, Project Management Team needs to monitor the commenting process which may impact the performance of the Project. This monitoring is performed for critical documents only. Such categorization of COMPANY comments enables to know if COMPANY comments are acceptable and if they will involve many changes about the cost or the planning of the project.
6.2 Critical Documents
Documents considered as critical for comments’ categorization are:
➢ Class 1 documents.
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF. RLNG-000-PM-PP-1105
CONTRACTOR DOC. REF.
215122C-000-PP-1105
REVISION: 0A
PAGE 25 OF 53
➢ Project Procedures (document code PP) ➢ Job Specifications for Design (document code JSD) ➢ Piping and Instrument Diagrams (document code PID) ➢ Overall layout (document code DW-0051) ➢ General Single Line Diagrams ➢ Any other critical document identified by Operating Centre / Discipline within its Quality Plan.
6.3 Categorization of Comments (for Critical Documents)
As part of the technical analysis of the client’s comments, the originator(s) of the technical deliverable identifies the nature of the comments and categorizes them as:
➢ Code A: Non-Conformity identified by the COMPANY - Non-compliance with contractual
specifications or codes, technical error found on a released deliverable.
➢ Code B: Valid Comment (technically valid and contractually acceptable) - The comment is technically valid and is to be considered but does not involve change in contractual scope
- no change request but may be the subject of further exchanges.
➢ Code C: Not Contractual - The comment is contractually not valid. It implies requested change in contractual scope: addition or deletion, “nice to have improvement”, with cost and/or schedule impact.
➢ Code D: Minor - Relatively Minor (superficial) comments or erroneous comments or non- understandable comment or question from client or comments concerning form rather than technical substance but does not identify a non-compliance with contractual requirements (Category A).
This categorization should be done when the comments are first received and analysed, not later.
6.4 Recording of Comments Category in GAIA
After Categorization of Comments in CRS, Disciplines shall record this information in GAIA Engineering Comments Module as per Working Instruction : 215122C-000-WI-1106 – Management of COMPANY Comments.
7.0
EXTERNAL MODULE
External module is dedicated to track, check and store documents issued by External parties or documents that are not part of the ENGINEERING Module.
On the project, the External Module will be used to record documents such as the Technical Queries (TQ) and Concession and Deviation Requests (DCA).
The DCC will manage External module in order to provide every authorized person with an access and will update their access during project life.
External module main purposes are:
➢
➢
➢
➢
to register all documents provided by External parties and their revisions,
to provide a place where documents electronic files can be stored,
to ensure the distribution of the documents in the project team and easy access to the documents,
to provide facilities for follow-up of comments status and for electronic annotation of documents submitted for review.
Refer to Working Instruction : 215122C-000-WI-2101 – Issue of Technical Query (TQ), Deviation Concession Request (DCA), Request for Information (RFI).
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF. RLNG-000-PM-PP-1105
CONTRACTOR DOC. REF.
215122C-000-PP-1105
REVISION: 0A
PAGE 26 OF 53
7.1 COMPANY Comment Management for TQ/DCA/RFI
Upon submission of TQ/DCA/RFI to COMPANY through ACONEX and after responses have been provided by COMPANY, responded TQ/DCA/RFI are returned to DCC through ACONEX notification in DCC Mailbox. CONTRACTOR DCC shall download responded TQ/DCA/RFI from ACONEX, records in GAIA and notifies to CONTRACTOR recipients.
Refer Section 7.2 for TQ/DCA/RFI Document and Comments workflow for CONTRACTOR (TJN)
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF.
CONTRACTOR DOC. REF.
RLNG-000-PM-PP-1105
215122C-000-PP-1105
REVISION: 0A
PAGE 27 OF 53
7.2 TQ/DCA/RFI Document and Comments Workflow for CONTRACTOR (TJN)
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF. RLNG-000-PM-PP-1105
CONTRACTOR DOC. REF.
215122C-000-PP-1105
REVISION: 0A
PAGE 28 OF 53
8.0
VENDOR MODULE
VENDOR module is dedicated to track, check and store documents issued by VENDORS and SUBCONTRACTORS.
VENDOR module main purposes are:
➢
➢
➢
➢
to register all VENDOR and SUBCONTRACTOR documents and their revisions,
to provide a place where documents electronic files can be stored,
to ensure the distribution of the documents in the project team and easy access to the documents,
to provide facilities for follow-up of comments status and for electronic annotation of documents submitted for review.
The Forecast List SUBCONTRACTORS.
identifies all
the documents
that are
to be sent by VENDORS and
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF.
CONTRACTOR DOC. REF.
RLNG-000-PM-PP-1105
215122C-000-PP-1105
REVISION: 0A
PAGE 29 OF 53
8.1 Vendor Document Workflow for POC Documents (POC Requisitions-Leader) (This workflow is continued in the next page):TYPE - 1
REQUISITIONS
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF.
CONTRACTOR DOC. REF.
RLNG-000-PM-PP-1105
215122C-000-PP-1105
REVISION: 0A
PAGE 30 OF 53
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF.
CONTRACTOR DOC. REF.
RLNG-000-PM-PP-1105
215122C-000-PP-1105
REVISION: 0A
PAGE 31 OF 53
8.2 Vendor Document Workflow for YOC Documents (YOC Requisitions-Leader): TYPE - 1 REQUISITIONS - FOR COMPANY REVIEW
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF.
CONTRACTOR DOC. REF.
RLNG-000-PM-PP-1105
215122C-000-PP-1105
REVISION: 0A
PAGE 32 OF 53
8.3 Vendor Document Workflow for YOC Documents (YOC Requisitions-Leader): TYPE - 1 REQUISITIONS - FOR COMPANY INFORMATION
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF.
CONTRACTOR DOC. REF.
RLNG-000-PM-PP-1105
215122C-000-PP-1105
REVISION: 0A
PAGE 33 OF 53
8.4 Vendor Document Workflow for ADOC Requisitions (NMDC Requisitions managed by ADOC): TYPE - 1 REQUISITIONS
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF.
CONTRACTOR DOC. REF.
RLNG-000-PM-PP-1105
215122C-000-PP-1105
REVISION: 0A
PAGE 34 OF 53
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF.
CONTRACTOR DOC. REF.
RLNG-000-PM-PP-1105
215122C-000-PP-1105
REVISION: 0A
PAGE 35 OF 53
8.5 Vendor Document Workflow for POC Documents (POC Requisitions-Leader) (This workflow is continued in the next page): TYPE - 2 & 3
REQUISITIONS
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF.
CONTRACTOR DOC. REF.
RLNG-000-PM-PP-1105
215122C-000-PP-1105
REVISION: 0A
PAGE 36 OF 53
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF.
CONTRACTOR DOC. REF.
RLNG-000-PM-PP-1105
215122C-000-PP-1105
REVISION: 0A
PAGE 37 OF 53
8.6 Vendor Document Workflow for YOC Documents (YOC Requisitions-Leader): TYPE -2 & 3 REQUISITIONS: FOR COMPANY REVIEW
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF.
CONTRACTOR DOC. REF.
RLNG-000-PM-PP-1105
215122C-000-PP-1105
REVISION: 0A
PAGE 38 OF 53
8.7 Vendor Document Workflow for YOC Documents (YOC Requisitions-Leader): TYPE -2 & 3 REQUISITIONS - FOR COMPANY INFORMATION
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF.
CONTRACTOR DOC. REF.
RLNG-000-PM-PP-1105
215122C-000-PP-1105
REVISION: 0A
PAGE 39 OF 53
8.8 Vendor Document Workflow for ADOC Documents (ADOC Requisitions-Leader) (This workflow is continued in the next page): TYPE -2 & 3
REQUISITIONS
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF.
CONTRACTOR DOC. REF.
RLNG-000-PM-PP-1105
215122C-000-PP-1105
REVISION: 0A
PAGE 40 OF 53
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF.
CONTRACTOR DOC. REF.
RLNG-000-PM-PP-1105
215122C-000-PP-1105
REVISION: 0A
PAGE 41 OF 53
8.9 COMPANY’s Comment on Vendor Documents/Comments Transmission from CONTRACTOR to VENDOR – Workflow with Steps
VENDOR DOCUMENTS TO BE REVIEWED BY COMPANY
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF. RLNG-000-PM-PP-1105
CONTRACTOR DOC. REF.
215122C-000-PP-1105
REVISION: 0A
PAGE 42 OF 53
General
Step #1
Time for review is given for information and Guideline / target to return comments to Vendor within 15 working days VENDOR Document is submitted to CONTRACTOR for review
CONTRACTOR to comment the document in red lining and transfer to COMPANY COMPANY to review and comment if any CONTRACTOR to review COMPANY ‘s comments if any, COMPANY’s comment are discussed with COMPANY CONTRACTOR transfer commented document to VENDOR All COMPANY comments will be transmitted to VENDOR. No COMPANY comments will be removed However, CONTRACTOR to clearly indicate the COMPANY Comment which are closed and not to be considered by VENDOR : “CLOSED BY CONTRACTOR – NOT TO BE CONSIDERED BY VENDOR ” and to answer comments using the .pdf text box of the comments (Picture to be added) In case of Code 3 (no comment), the review is completed and document has to be issued as final In case of Code 1 or 2, VENDOR to review comments and to answer them in the .pdf text box of the commented document (picture to be added) if any, comments are reviewed between VENDOR, CONTRACTOR and COMPANY VENDOR to update and to revise document VENDOR to transfer revised document + answer to comment on previous revision to CONTRACTOR Answer to comments are formalized on the previous revision of the documents by directly answering within text box created for the comment itself. CONTRACTOR to review and comment the new revision of document as well as the answer to comment given by Vendor on previous revision of document (formalized on the previous revision of document) CONTRACTOR to transfer new revision of document + previous revision of document with the comments and the answers to COMPANY COMPANY to review and comment if any CONTRACTOR to review COMPANY ‘s comments if any, COMPANY’s comment are discussed with COMPANY CONTRACTOR transfer commented document to VENDOR All COMPANY comments will be transmitted to VENDOR. No COMPANY comments will be removed However, CONTRACTOR to clearly indicate the COMPANY Comment which are closed and not to be considered by VENDOR : “CLOSED BY CONTRACTOR – NOT TO BE CONSIDERED BY VENDOR ” and to answer comments using the .pdf text box of the comments (Picture to be added) In case of Code 3 (no comment), the review is completed, and document has to be issued as final In case of Code 1 or 2, cycle resumes to step #2
Step #2
Step #3
Step #4
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF.
CONTRACTOR DOC. REF.
RLNG-000-PM-PP-1105
215122C-000-PP-1105
VENDOR DOCUMENTS FOR COMPANY INFORMATION
REVISION: 0A
PAGE 43 OF 53
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF. RLNG-000-PM-PP-1105
CONTRACTOR DOC. REF.
215122C-000-PP-1105
REVISION: 0A
PAGE 44 OF 53
General
Step #1
Step #2
Step #3
Step #4
from
the ones
to VENDOR
together with
Time for review is given for information and Guideline / target to return comments to Vendor within 15 working days VENDOR Document is submitted to CONTRACTOR for review CONTRACTOR to comment the document in red lining and send it back to Vendor for implementation + to COMPANY for information COMPANY comments will be submitted CONTRACTOR or in a second set of comments depending on the timing In case COMPANY would like to comment, comments should be received within 5 working days not to disturb too much VENDOR production In case of Code 3 (no comment), the review is completed, and document has to be issued as final In case of Code 1 or 2, VENDOR to review comments and to answer them in the .pdf text box of the commented document (picture to be added) if any, comments are reviewed between VENDOR, CONTRACTOR and COMPANY VENDOR to update and to revise document VENDOR to transfer revised document + answer to comment on previous revision to CONTRACTOR Answer to comments are formalized on the previous revision of the documents by directly answering within text box created for the comment itself. CONTRACTOR to review and comment the new revision of document as well as the answer to comment given by Vendor on previous revision of document (formalized on the previous revision of document) CONTRACTOR to transfer new revision of document + previous revion of document with the comments and the answers to COMPANY for information CONTRACTOR to send it back its comments to Vendor for implementation In case COMPANY has some comments the “for Review” workflow applies COMPANY comments will be submitted CONTRACTOR or in a second set of comments depending on the timing In case of Code 3 (no comment), the review is completed, and document has to be issued as final In case of Code 1 or 2, cycle resumes to step #2
together with
to VENDOR
the ones
from
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF. RLNG-000-PM-PP-1105
CONTRACTOR DOC. REF.
215122C-000-PP-1105
REVISION: 0A
PAGE 45 OF 53
9.0
CONTRACTOR DOCUMENT REGISTER
CONTRACTOR develops and maintains a Contractor Document Register (CDR) that lists all the documents to be produced by the CONTRACTOR.
The main objectives of the CDR are to:
Identify all deliverables to be issued by CONTRACTOR during the project,
➢ ➢ Follow up the revisions, statuses and comments.
The CDR will provide as a minimum the following Information (As per the CDR Template in Annex 1):
Column Description
A B C D E F G H I J
Track Record: D-Deleted/N-New/M-Modified CONTRACTOR Document Reference COMPANY Document Reference Document Title Operating Centre COMPANY Discipline CONTRACTOR Discipline Document Class Document Category for Class 1 Remarks
The CDR is sent to COMPANY on a monthly basis as a Project Document, and changes between 2 subsequent revisions are marked off by populating related field(s).
10.0 DOCUMENT AND DRAWING TEMPLATES
Document Templates:
The document templates are as per COMPANY guidelines.
➢ The templates are stored in SharePoint for YOC/ADOC(NMDC) :
TEMPLATES
The snapshots of Templates specimen are in Appendix 3.
➢ FOR POC : The templates are also recorded in GAIA and can be found in Projects under Template Files Folder. Whenever there are updates in the templates, the new revisions of the templates will be replaced in GAIA.
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF. RLNG-000-PM-PP-1105
CONTRACTOR DOC. REF.
215122C-000-PP-1105
REVISION: 0A
PAGE 46 OF 53
Drawing Templates:
The drawings templates are adapted according to COMPANY requirements.
TQ/DCA and RFI Templates:
The TQ/DCA and RFI Templates are adapted according to COMPANY requirements.
APPENDIX 1 – CDR TEMPLATE
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF. RLNG-000-PM-PP-1105
CONTRACTOR DOC. REF.
215122C-000-PP-1105
REVISION: 0A
PAGE 47 OF 53
APPENDIX 2 – CRS TEMPLATE
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF. RLNG-000-PM-PP-1105
CONTRACTOR DOC. REF.
215122C-000-PP-1105
REVISION: 0A
PAGE 48 OF 53
APPENDIX 3 – DOCUMENT TEMPLATES
WORD/EXCEL/DRAWING/TQ/DCA/RFI SPECIMEN
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF. RLNG-000-PM-PP-1105
CONTRACTOR DOC. REF.
215122C-000-PP-1105
REVISION: 0A
PAGE 49 OF 53
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF. RLNG-000-PM-PP-1105
CONTRACTOR DOC. REF.
215122C-000-PP-1105
REVISION: 0A
PAGE 50 OF 53
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF. RLNG-000-PM-PP-1105
CONTRACTOR DOC. REF.
215122C-000-PP-1105
REVISION: 0A
PAGE 51 OF 53
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF. RLNG-000-PM-PP-1105
CONTRACTOR DOC. REF.
215122C-000-PP-1105
REVISION: 0A
PAGE 52 OF 53
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
RUWAIS LNG PROJECT
PROJECT DOCUMENT MANAGEMENT PROCEDURE
COMPANY DOCUMENT REF. RLNG-000-PM-PP-1105
CONTRACTOR DOC. REF.
215122C-000-PP-1105
REVISION: 0A
PAGE 53 OF 53
The terms of Contract / Agreement No: CON22-146 shall apply for any disclosure of this document to any third party.
Project: Q-32859 - NMDC - Ruwais Folder: RFQ Files