Sie sind auf Seite 1von 13

J.

Ray McDermott Asia Pacific Engineering

ENGINEERING PROCEDURE

LEVEL 2

ADVANCE REVISION NOTIFICATION

JRM-AP-ENG-4010
Page

S
M
J. Ray McDermott Asia Pacific Engineering 3 of 13
Procedure number Procedure title Rev No. Date

JRM-AP-ENG-4010 Advance Revision Notification 1 31/03/06

REVISION INDEX

AUTHORISED BY
REV REVISION PREPARED
AFFECTED SECTION ENG. MANAGER ENG.
NO. DATE BY QA
JKT SING DIRECTOR

0 23/11/01 Initial Issue Handoko CK Mohan A. Pollack

1 31/03/06 General Revision M. Setiawan Handoko S. Kumar S. Banerjee M. Wilson


Page

S
M
J. Ray McDermott Asia Pacific Engineering 4 of 13
Procedure number Procedure title Rev No. Date

JRM-AP-ENG-4010 Advance Revision Notification 1 31/03/06

TABLE OF CONTENTS

REVISION INDEX.....................................................................................................................3
1 INTRODUCTION & SCOPE .............................................................................5
2 OBJECTIVES .....................................................................................................5
3 REFERENCES....................................................................................................6
4 DEFINITIONS & ABBREVIATIONS...............................................................6
5 RESPONSIBILITIES..........................................................................................7
6 PROCESSES.......................................................................................................8
7 INTERFACES...................................................................................................10
8 STORAGE ........................................................................................................10

FLOWCHART 4011 Advance Revision Notification

APPENDIX A Advance Revision Notification Form (ARN)


APPENDIX B Typical Advance Revision Notification Log
Page

S
M
J. Ray McDermott Asia Pacific Engineering 5 of 13
Procedure number Procedure title Rev No. Date

JRM-AP-ENG-4010 Advance Revision Notification 1 31/03/06

1 INTRODUCTION & SCOPE

This document is a Level II procedure for J. Ray McDermott Asia Pacific


Engineering (JRMAPE), and forms part of the management system as
described in the J. Ray McDermott Asia Pacific (JRMAP) Level I
Management System Manual.

This Level II standard operating procedure outlines the Advance Revision


Notification process as applied to projects undertaken by JRMAPE.
Detailed work instructions and other relevant Level II procedures are
referenced as applicable.

2 OBJECTIVES

The purpose of this Procedure is to detail and clarify the methods by which
Document Changes, prior to an overall revision are identified and
implemented in advance, to ensure that the changes are properly and
thoroughly evaluated by all necessary engineering interfaces.

The objective is to assure that:

Changes to all frozen documents are detailed

All recipients / holders of key documents are notified and


advised regarding the changes without reissuing the entire
document

Supplier / Construction site are advised that a modification /


alteration will be incorporated in the next issue of an
AFD/AFC document

This procedure will be subject to audit as part of the ongoing review of the
quality management system. It is not the intent of JRMAPE to vary these
processes for projects unless contractual reasons dictate otherwise. In those
instances, any contractually agreed changes will be outlined in the project
execution plan.
Page

S
M
J. Ray McDermott Asia Pacific Engineering 6 of 13
Procedure number Procedure title Rev No. Date

JRM-AP-ENG-4010 Advance Revision Notification 1 31/03/06

3 REFERENCES

a) 17-01-001, Level I Procedure Management System Manual J. Ray


McDermott Asia Pacific

b) JRM-AP-ENG-0100, Organisation & Responsibilities

c) JRM-AP-ENG-1700, Document Control

d) JRM-AP-ENG-1800, Document Review & Verification

e) JRM-AP-ENG-2000, Change Order

f) JRM-AP-ENG-2300, Interface Control

g) JRM-AP-ENG-2600, Specifications and Data Sheets

h) Level II procedures, as applicable

4 DEFINITIONS & ABBREVIATIONS

AFC Approved For Construction

AFD Approved For Design

ARN Advance Revision Notes

DCA Document Control Aide

PMT Project Management Team

Document Change

A document change is defined as any alteration to, addition to, or deletion


from all approved documents or drawings that have attained Frozen
document status.

Frozen Document

A Frozen document is a document that has achieved an agreed project


status and, thereafter, will be subjected to change. In general, documents
Page

S
M
J. Ray McDermott Asia Pacific Engineering 7 of 13
Procedure number Procedure title Rev No. Date

JRM-AP-ENG-4010 Advance Revision Notification 1 31/03/06

will be frozen as soon as they are AFD or AFC unless otherwise agreed
by Project Engineering Manager.

5 RESPONSIBILITIES

a) Project Engineering Manager

The Project Engineering Manager is responsible for the final


approval of all ARNs and issue to fabrication site, PMT, Customer
and all Disciplines.

b) Project Engineer

The Project Engineer is responsible for:

Appraising the site of, and seeking site comments on ARNs

Initial approval of ARNs and issue to Project Engineering


Manager and Engineering Office Manager for final approval

Determining if a change order is required

Issuing an Instruction Memo to determine which other


engineering groups are affected and collecting the ARN
backup documents

c) Lead Discipline Engineer

Lead Discipline Engineer will have prime responsibility for raising


ARNs and the review of the technical impact of all changes to
documentation including requisitions and issue to Project Engineer
for approval.

d) Project Secretary

The Project Secretary is responsible for preparing a complete ARN


log.
Page

S
M
J. Ray McDermott Asia Pacific Engineering 8 of 13
Procedure number Procedure title Rev No. Date

JRM-AP-ENG-4010 Advance Revision Notification 1 31/03/06

6 PROCESSES

The activities involved in the development of ARN are as detailed in


Flowchart 4011.

6.1 OVERVIEW

An ARN shall be raised to cover any change to frozen documents, even if


there is not any implication to design costs related to the change. In every
case the reason for such change shall be identified. The purpose of issuing
an ARN is to limit revisions to the Frozen documents.

6.2 INITIATION

An ARN is initiated to document changes prior to overall revision of a


Frozen document to ensure that the changes are properly and thoroughly
evaluated by all necessary engineering interfaces.

The Lead Discipline Engineer shall initiate an ARN after assessing the
changes on the Frozen document and its impact on the other affected
disciplines and groups. If the changes do not call for an immediate revision
of the document, the Lead Discipline Engineer shall raise an ARN.

6.2.1 Contents

A typical ARN form is attached in Appendix A. An ARN shall


illustrate or have as an attachment the proposed revised portion of
the document (i.e. an affected drawing, specification and / or data
sheet).

ARNs as a minimum, shall provide the following information:

Document Number
Document Revision Number
Sequence Number
ARN Number
Date
Weight Impact (if applicable)
Advance Weight Change Note (if applicable)
Change order cross reference (if applicable)
Page

S
M
J. Ray McDermott Asia Pacific Engineering 9 of 13
Procedure number Procedure title Rev No. Date

JRM-AP-ENG-4010 Advance Revision Notification 1 31/03/06

Material Requisition Impact (if applicable)


Material Summary Sheet (if applicable)

The control / assignment of sequence numbers and ARN numbers


will be the responsibility of the Lead Discipline Engineer and the
Project Secretary respectively. Each ARN shall have the discipline
identity code along with a unique sequential numerical ID.

Discipline identity codes are as follows:

E Electrical
I Instruments
M Mechanical
O Process
D Telecoms
S Structural
R Pipelines

6.3 APPROVAL AND ISSUE

The Lead Discipline Engineer shall submit the completed ARN to the
Project Engineer for review, approvals and issue to PMT, with a copy to
the Fabrication Site Construction Manager.

All ARNs will be reviewed and approved in accordance with the Project
Execution Plan. The Project Engineering Manager shall ensure that the
Customers approved ARNs are distributed to all the concerned parties,
through the Document Control.

The Lead Discipline Engineer is responsible to resolve any queries or


clarifications on the ARNs after their issue.

6.4 CLOSE-OUT

The Lead Discipline Engineer shall ensure that all the changes notified on
the ARN issued after a previous revision of a document are incorporated in
the subsequent revision of the Document.

The Project Engineer shall maintain a log/ status register of all ARNs and
ensure that any issue of the affected documents includes a reference of all
corresponding ARNs.
Page

S
M
J. Ray McDermott Asia Pacific Engineering 10 of 13
Procedure number Procedure title Rev No. Date

JRM-AP-ENG-4010 Advance Revision Notification 1 31/03/06

Upon the issue of the revised documents, the Project Engineer notifies all
the concerned parties and ensures that the ARNs are closed.

A typical ARN log is attached in Appendix B.

7 INTERFACES

All interface control requirements shall be in accordance with Procedure


No. JRM-AP-ENG-2300, Interface Control.

8 STORAGE

The Project Engineer / Document Control Aider is responsible for proper


storage of the ARNs during the course of the project. They are archived at
the end of the project as per Project / Company archiving requirements.
Page

S
M
J. Ray McDermott Asia Pacific Engineering 11 of 13
Procedure number Procedure title Rev No. Date

JRM-AP-ENG-4010 Advance Revision Notification 1 31/03/06

Advance Revision
Notification
FLOWCHART 4011
Work Process

Discipline Engineer Project Other Discipline

Identify changes
Mark documents
Fill-in ARN Form

Project Secretary
ARN No. 1

Yes

C/O

No

Project Engineer
Change Notification Change Order Input
Approval

PMT
Engineering Manager
C/O Proposal
Approval
Material Requisition
Supplement Fabrication Site
Construction Manager

Client Approval

Document Control
Distribution
Page

S
M
J. Ray McDermott Asia Pacific Engineering 12 of 13
Procedure number Procedure title Rev No. Date

JRM-AP-ENG-4010 Advance Revision Notification 1 31/03/06

APPENDIX A
ADVANCE REVISION NOTIFICATION FORM (ARN)

PT. McDERMOTT INDONESIA


Project: ARN No.
ADVANCE
REVISION NOTE
(ARN) DATE:

DOCUMENT NO: ___________REV: ____ SEQUENCE No.: ________________

DOCUMENT TITLE: ____________________________________________________________

REASON FOR CHANGE:

DESCRIPTION & SKETCH OF CHANGE:

CHANGE ORDER: YES/NO ADVANCE WEIGHT CHANGE NOTE: ..ATTACHED


WEIGHT IMPACT: YES/NO MATERIAL SUMMARY SHEET: ATTACHED
MATERIAL IMPACT: YES/NO

ORIGINATOR LEAD. ENG. PROCESS MECHANICAL ELECTRICAL INSTRUMENT STRUCTURAL


APPROVAL

PIPELINE HSE PE PEM EOM PM CUSTOMER


DISTRIBUTION

CUSTOMER PROCESS STRUCTURAL INSTRUMENT DRFT


PMT MECHANICAL PIPELINE STRUCTURAL DRFT
FAB ELECTRICAL PIPING DRFT PIPELINE DRFT
HSE INSTRUMENT ELECT. DRFT PDMS
Page

S
M
J. Ray McDermott Asia Pacific Engineering 13 of 13
Procedure number Procedure title Rev No. Date

JRM-AP-ENG-4010 Advance Revision Notification 1 31/03/06

APPENDIX B
TYPICAL ADVANCE REVISION NOTIFICATION LOG

PT. McDERMOTT INDONESIA Project:

Close-Out Record
Sequence C/O Approved
ARN No. Issue
No. Originator Yes or Date by
(*) Date Lead Project Customer Date
(*) No Customer
Engineer Eng.
Mgr.

REMARK:

(*) ARN No. is based on Project Secretary Log i.e. RXXXX-ARN-YYY, whereas XXXX is Project No.
and YYY is serial number. Sequence No. is based on Discipline Log i.e. ARN-M-ZZZ, whereas M is
Discipline Code and ZZZ is serial number.