FADHILI INDUSTRIAL SUPPORT

FACILITIES (ISF- PACKAGE 7)

BI-10-01900-0005, Contract No. 6600036437

June 19, 2017

Presentation

PROCEDURES FOR
REDLINE, REVISION, SHOP, AND
AS-BUILT DRAWINGS

June 19, 2017

 Safety

In case of any emergency do not panic, proceed to

Assembly Point

!! Do It Right At First Time !!

 Agenda
INTRODUCTION
PURPOSE AND SCOPE
DEFINITIONS AND ABBREVIATIONS
REFERENCES
DRAWING REVISION NUMBERING
ROLES AND RESPONSIBILITIES
PROCEDURE
REDLINE MARKUP
REVISION DRAWING.
SHOP DRAWING
AS-BUILT DRAWING
COMPANY REVIEW AND APPROVAL
CONTROL OF DELIVERABLE
FILING, STORAGE, AND IDENTIFICATION SYSTEM

4
Introduction

5
 1.INTRODUCTION
1.1. This procedure establishes the procedural
requirements and practices to be followed in preparation,
review, submittal, tracking, safe-keeping, distributing and
control of the following classification of drawings and
engineering deliverables
1. Redline Markup Drawings.
2. Revision of IFC drawings.
3. Shop Drawings.
4. As-built Drawings.
Contd
6
September 5, 2016
 1.INTRODUCTION
1.2. This procedural requirement applies to all
engineering deliverables generated by Thabat
Construction Company Ltd. and/or its
subcontractors and/or its suppliers and not
applicable to any informal sketches, schematics,
or instructions.

7
September 5, 2016 Al Muhaidib Contracting Co.
 2.PURPOSE AND SCOPE
2.1. In construction projects, it is common for changes to
be made during construction because of
circumstances that emerge on site. Hence, as-built
package is key submittal for the following purposes.
i) It represents the record from which future renovation,
expansion, system changes, and/or additions can be
designed more efficiently and accurately.
ii) It is a valuable basis for the operations and maintenance
staff.

8
 2.PURPOSE AND SCOPE
2.2 Significance of the changes occur during construction
varies from minor to significant and the measures to
control the impact on engineering deliverables can
presented as a redline markup on the drawings or
introducing it as shop drawing a revision of the
drawing. Hence, this procedure is established for
timely preparation, approval and control of all
changes which may take place to the engineering
deliverables generated after submittal of IFC
package in any form such as redline markup
drawings, revision of IFC drawings, and shop
drawings.

9
 2.PURPOSE AND SCOPE
2.3 COMPANY also requires As-Built package preparation to
go in parallel with the construction to reflect
accurately what has actually been built and to
enable CONTRACTOR to compile all types of changes
and to submit an accurate As-Built package to
COMPANY once construction is completed.

2.4 In addition to the 2D drawing deliverables, COMPANY

requires the building information 3D model to be
updated to reflect any changes to the design and
issued to COMPANY.

10
 2.PURPOSE AND SCOPE
2.3 COMPANY also requires As-Built package preparation to
go in parallel with the construction to reflect
accurately what has actually been built and to
enable CONTRACTOR to compile all types of changes
and to submit an accurate As-Built package to
COMPANY once construction is completed.

2.4 In addition to the 2D drawing deliverables, COMPANY

requires the building information 3D model to be
updated to reflect any changes to the design and
issued to COMPANY.

11
3.DEFINITIONS AND ABBREVIATIONS

Al Muhaidib Contracting Co. 12

 3.DEFINITIONS AND ABBREVIATIONS
As-Built Drawing : The final updated IFC drawing including any redline
markup and any additions, deletions, supplemental
or field requested changes or variations made
during construction of the project and deviates
from the approved design.

As-Built Package : Official record of the project deliverables to be

submitted at the time construction is completed.

Company : Saudi Arabian Oil Company/Saudi Aramco.

Contractor : Thabat Construction Company Ltd.

13
 3.DEFINITIONS AND ABBREVIATIONS
Deliverable Control List (DCL) : A log usually in XL format holding
information such as deliverable title, index, type,
number, revision and date of latest revision covering
all deliverables affected under a specific phase or
change.

Deliverable Revision Log (DRL) : A log in XL format prepared and

maintained by the engineering document
controller listing all the previous and current revision
anticipated on any deliverable.

14
 3.DEFINITIONS AND ABBREVIATIONS
Document Change Notice (DCN) : An interim status of an engineering
deliverable indicating it is under revision and also refers
to a form to be issued indicating the intention of putting
the deliverable in a revision status.

Engineering Deliverable : Document, which discloses sufficient engineering

requirements, characteristics, function, and information
of an item by means of pictorial and/or textual
presentations, and contains proper approvals such as
(Calculations, Datasheet, Descriptive Literature Design
Basis, Diagrams, Drawing, Layouts, Illustrations, Manuals,
Reports, Schematics, Scope Of Work, Schedules,
Specifications, Studies, Performance Data, etc...)
15
 3.DEFINITIONS AND ABBREVIATIONS
Field Redline Markup: A hard copy of a drawings where color coded markup
is initiated by the respective discipline engineer to reflect
deviation that already took place at site

Issued for Construction (IFC): A status of an engineering deliverable

indicating that it is certified by COMPANY to be issued to
the construction team.

Lead Engineer: Experienced engineer whose is qualified to lead other

engineers in a specific discipline selected by CONTRACTOR
and approved by COMPANY.

Redline Markup : A hard copy of a drawing where color coded markup is

initiated by the respective discipline engineer to reflect a
proposed deviation from the current drawing revision.
16
 3.DEFINITIONS AND ABBREVIATIONS
Revision Drawing : A drawing edited electronically in CADD or Microstation to
reflect changes, additions or deletions from the current IFC
drawing.

Shop Drawing : A diagram, drawing, illustration, layout, mockup,

performance data, sample, schematics, schedule, and test
data produced by the CONTRACTOR, supplier, manufacturer,
subcontractor, or fabricator that shows more details than
the Issued for Construction Drawing.

17
4.REFERENCES

Al Muhaidib Contracting Co. 18

 4. REFERENCES
The following references are considered as an integral part of this procedure.

SAES-A-202 : Saudi Aramco Engineering Drawing Preparation.

SAEP-334 :Retrieval, Certification and Submittal of Saudi Aramco Engineering & Vendor

Drawings

SAEP-127 : Security and Control of Saudi Aramco Engineering Data

SAEP-303 : Engineering Reviews of Project Proposal and Detail Design Documentation.

SAEP-110 : Saudi Aramco Standard Drawings

SAEP-305 : Saudi Aramco Library Drawings

SAEP-A-1154 : Guidelines for Contractors Quality Plan.

G.I. 0710.002 :Classification and Handling of Sensitive Information

ASME-Y14.100 Engineering Drawing Practices

19
 5. DRAWING REVISION NUMBERING

5.1 Revision number shall be a three alpha-numeric characters (partial as-built

in SAEP-334) as follows:

a) Uppercase letter (A, B, C, etc...) for all issues before As-Built submittal.
b) Two digits number (00 to99) until the submission of As-Built.

20
 5. DRAWING REVISION NUMBERING
5.2 Revision number, date and description shall be recorded on the assigned
cell in the title block below.

21
 6. ROLES AND RESPONSIBILITIES
6.1 E NGINEERING MANAGER :
6.1.1 Engineering Manager shall assure conformance with the provisions covered in this
procedural requirements and shall assure integrity and suitability of its output.

6.1.2 Engineering Manager shall assign a CADD supervisor and an engineering document
controller.

6.1.3 Engineering Manager shall orchestrate the effort of discipline engineers and CADD
operators in the Engineering Department to achieve and maintain the production of
any type of engineering deliverable in a team environment. While the responsibility for
achieving and maintaining the production environment rests on all engineering and
CAD personnel who make up the Engineering Team.

6.1.4 Engineering manager shall provide a suitably furnished lockable room with adequate
size to house and archive the originals of all engineering deliverables such as early
issues of IFCs, redline markup, recent revisions, superseded revisions, shop).
22
 6. ROLES AND RESPONSIBILITIES
6.1 E NGINEERING MANAGER :

6.1.5 Engineering manager shall provide a separate lockable filing area could
be in the form of a heavy duty cabinets or small room to store any sensitive or
confidential documentation (such as HCIS security systems and approvals).

6.1.6 Engineering manager shall provide steel plan chests with drawers and
locks will be used to store original drawings. Each drawer in a plan chest will be
assigned either a number or a name to indicate its contents

23
 6. ROLES AND RESPONSIBILITIES
6.2 Q UALITY ASSURANCE AND CONTROL MANAGER

6.2.1 Quality assurance and control manager shall conduct

biannual internal audit to assure the procedure is being
implemented. First audit shall be conducted no later
than six weeks from date of issue of the procedure.

6.2.2 Quality assurance and control Manager shall conduct monthly

validation of the Deliverable Revision Log to confirm it is properly
initiated and maintained.

24
 6. ROLES AND RESPONSIBILITIES
6.3 CADD SUPERVISOR

6.3.1 CADD supervisor shall supervise the preparation of CADD and/or Microstation files.

6.3.2 CADD supervisor shall create a password controlled folder at the CONTRACTOR
server to house the electronic file of all and only the latest revision of all engineering
deliverables and provide access to personnel on need to know basis.

6.3.3 CADD Supervisor shall issue the deliverable control list (DCL) covering all
deliverables affected in each change to be used as a cover page for every submittal
to COMPANY.

6.3.4 CADD supervisor shall archive all previous revisions of all engineering deliverables
on a folder accessible only to him to assure no earlier revisions of any deliverables
will find its way to the construction team where it may create confusion.

25
 6. ROLES AND RESPONSIBILITIES
6.4 ENGINEERING DOCUMENT CONTROLLER

6.4.1 Engineering document controller shall establish a comprehensive filing and

deliverables control system to ensure that the project data in any form (hardcopies,
softcopies, media, etc...) can be traced and retrieved in an efficient manner.

6.4.2 Engineering document controller shall prepare and maintain the Deliverable
Revision Log and issue the next revision number to the key discipline lead upon
their request.

6.4.3 Engineering document controller shall assure all originals are securely stored and
shall create and maintain a suitable and easily accessible archiving system.

6.4.4 Engineering document controller shall assure that a Deliverable Control List (DCL)
is attached to every submittal of deliverable to COMPANY so that it can be used as
a quick and comprehensive reference for its contents.

26
 7. PROCEDURE
7.1 R EDLINE M ARKUP

7.1.1 Redline Markups will be generated on black line (Grayscale)

prints of the most current drawing (latest IFC revision). Each
change will be identified using a triangle with a sequence
number posted clearly inside it. The markup shall be clear from
ambiguity and easily understood by others using the redline
markup color coding below.

27
7. PROCEDURE 7.1 R EDLINE M ARKUP

28
7. PROCEDURE 7.1 R EDLINE M ARKUP

7.1.2 Upon an expected initiation of a redline markup or revision of any

engineering deliverable, the engineering document controller will assure
that the drawing is not currently under a DCN and provide the latest
revision to the CADD supervisor. The CADD Supervisor shall plot/print a
fresh, suitable size print of the latest revision of the subject drawing and
provide it to the engineering manager.

7.1.3 Engineering manager shall provide the print/plot to the lead engineer
of the key discipline for markup as per the revision required and show any
particular arrangements or changes as per the color coding system shown
above.

29
7. PROCEDURE 7.1 R EDLINE M ARKUP

7.1.4 Lead engineer of the key discipline shall fill the design change notice
(DCN) (see attached form) and route it for signature of other disciplines, if
needed, as well as obtain approval of the engineering manager on initiating
a revision and/or redline markup and hand the design change notice (DCN)
to engineering document controller to obtain a unique log number and next
revision.

7.1.5 Lead engineer of the key discipline shall arrange a meeting (could be just
an on-table discussion for minor changes) with other discipline leads to
identify the impact of the redline markup or revision on other disciplines
and systems and to identify all engineering deliverable affected by the
change and need to be revised as a result of the change introduced.

30
7. PROCEDURE 7.1 R EDLINE M ARKUP

7.1.6 Where unusual situations are encountered, such as existing utilities,

pipeline, cavities, shall be explained on the appropriate sheets and Notes
shall be added in RED.

7.1.7 A notification of the proposed change shall be issued to COMPANY for

information and preliminary acceptance. A joint visit between COMPANY and
CONTRACTOR may be carried out for verification. If necessary, an advance review
workshop shall be carried out in presence of the COMPANY to avoid
misinterpretation and rejection at later phase. COMPANY shall review the
proposed deviation and provide its acceptance whether the deviation can be
further developed or abandoned.

31
7. PROCEDURE 7.1 R EDLINE M ARKUP

7.1.8 In case the COMPANY didnt accept the change, then the process shall
stop and the respective markup shall be marked as abandoned.

7.1.9 In case the COMPANY provided its acceptance for the deviation to be
further developed, the CADD Supervisor shall furnish the latest revision of
impacted drawings to the discipline leads for their markup. Lead engineers
of the key discipline shall collect the markup of all affected engineering
deliverables as well as the next revision number from the engineering
document controller, if applicable.

7.1.10 Lead engineers of all involved disciplines will ensure that all associated changes
(e.g., sections, details, plans, profiles, elevations, etc...) are revised accordingly,
including those on other drawing or sheets. In addition, it may be necessary to
revise legends, schedules, notes and callout designations.
32
7. PROCEDURE 7.1 R EDLINE M ARKUP

7.1.11 When revisions require deletions, Lead engineers of all involved

disciplines will ensure that all features and associated data and captions
that relate to the deletion are marked accordingly.

7.1.12 Upon completion of markup on all affected deliverables, the lead engineer of the
key discipline shall identify the review departments (construction team, quality,
procurement, etc) to review the changes and shall collect their comments and
perform an initial evaluation to identify if any comments will not be implemented.
Engineering manager along with the discipline leads will review the comments that
shall not be implemented and decide a final conclusion on its implementation.

33
7. PROCEDURE 7.1 R EDLINE M ARKUP

7.1.13 Engineering manager shall submit the redline markup drawings to COMPANY for
review and comments. COMPANY will provide its comments, if any and will provide
the conclusion on whether drawings shall be developed further as an IFC revision
drawing or it can utilized as a redline markup.

7.1.14 Originals of Redline markup shall be archived under the custody of engineering
document controller and copies of it shall be distributed to all affected disciplines
for information. Engineering document controller shall scan the original in PDF
format prior to its distribution and shall archive the scanned copy in the server for
backup.

34
7. PROCEDURE 7.2 REVISION DRAWING

7.2.1 Preparation of revision drawings usually follow the redline markup

process as per the COMPANY discretion at its review to the redline
markup phase. It represents the phase of editing the CADD
/Microstation files to reflect the deviations and changes.

7.2.2 Each new revision of a drawing should provide clouds marking to show
the modifications incorporated since the previous issue and on further
revisions, the previous set of clouds will be removed. Date of revision
shall be posted on the drawing upon issuing it officially to COMPANY.

35
7. PROCEDURE 7.2 REVISION DRAWING

36
7. PROCEDURE 7.2 REVISION DRAWING

37
7. PROCEDURE 7.2 REVISION DRAWING

7.2.4 Lead engineer of the key discipline shall collect all redline markup
prepared by affected discipline leads and hand it over along with their
respective revision numbers to the CADD supervisor for further processing.

7.2.5 The CADD supervisor shall distribute the redline markup to CADD
operators and once the CADD operator completes editing the revised
drawing they shall produce a check plot of all deliverables to be checked by
the lead discipline engineers.

Superseded revisions of drawing shall be retained for history and tracking

purposes but shall be annotated as SUPERSEDED ".

38
 7. PROCEDURE 7.3 SHOP DRAWING

7.3.1 Shop drawings are engineering deliverable drawn to explain the fabrication,
erection, installation, location, sizing, material, dimension of a specific element of
the project. Shop drawings can also include Samples and Product Data

7.3.2 Shop drawing due to its function, emphasizes on a particular element of the
project and/or installation, thus it focuses on the proposed material, shape, size, and
assembly of that element and how the entire unit will be installed and pay less or no
attention to other products and installations. For these reasons, an integration
review with other elements and components and installation shall be conducted
during the preparation and review of all Shop Drawings.

7.3.3 The process of reviewing the shop drawings is vital to smooth construction, hence
all shop drawings shall have an ample review without fail and it may even be
extended to include the subcontractors.

39
 7. PROCEDURE 7.3 SHOP DRAWING

7.3.4 Upon receiving shop drawings from subcontractor, vendors, or suppliers,

engineering manager shall assign a key discipline lead and shall identify the
disciplines involved for review. Thereafter, engineering document controller shall
distribute the package to the discipline leads along with a blank form of comments
log to capture their review comments. The key discipline lead shall collect, clarify, and
evaluate the comments log. Engineering manager shall authorize issuance of the
comments log to the subcontractor, vendors, or suppliers via a transmittal for
correction, if any. Similarly, shop drawings prepared by the CONTRACTOR shall have
an in-house review.

7.3.5 Once the shop drawing package has passed the engineering review without any
major comments, it can then be submitted to COMPANY via a transmittal similar to
the redline markup submittal and following the same procedure.

40
7. PROCEDURE 7.4 AS-BUILT DRAWING

7.4.1 As-built drawings (deliverable) package that demonstrate how the CONTRACTOR
has built the project and what changes were made during the construction process,
this can be achieved by transferring revisions took place on the drawings and by
reflecting the redline markup, if any.

7.4.2 All revision information shall be removed and the code reset to 0 (zero) at the time
of issuing the drawing As-Built.

7.4.3 Upon completion of construction, CONTRACTOR shall collect all revisions and
redline markups of all engineering deliverable and reflect these changes in the
CADD/Microstation files. This process is recommended to go side by side with the
construction to achieve better accuracy of the as-built.

41
7. PROCEDURE 7.5 COMPANY REVIEW AND APPROVAL

7.5.1 Official channels of communications in relation to this procedure shall be the

sequential numbered transmittals, however, emails can be used with regards to
notifications and unofficial communications.

7.5.2 Prior to issuing any Redline markup, Revised, or Shop drawing to construction
team, CONTRACTOR shall obtain the No Objection from COMPANY on a dedicated
submittal for this purpose. COMPANY shall provide, at its own discretion, its final
response as one of the following responses:

1. No objection if COMPANY found the package acceptable and can be released to

the construction team without any further comments.
2. No objection as noted if COMPANY found the package acceptable and can be
released to the construction team with minor comments.

42
7. PROCEDURE 7.5 COMPANY REVIEW AND APPROVAL

3. Correct and Resubmit if COMPANY found the package not

acceptable and cant be released to the construction team and
COMPANY have major comments to be implemented prior to
accepting it.
4. Rejected if COMPANY found the proposed modifications are not
acceptable and shall not be developed any further. In that case all
revision numbers of drawings shall be cancelled and indicated
as not used in the deliverable revision log.

43
 7. PROCEDURE 7.5 COMPANY REVIEW AND APPROVAL

7.5.3 Engineering manager, upon receiving from COMPANY either No objection or No objection as
noted response will authorize the deliverable to be stamped by IFC stamp and dated as per the date.

7.5.4 CADD supervisor, upon receiving the authorization shall print the required number of hard copies
along with the associated DCL and hand it over to engineering document controller for a live stamp and
live date. CADD supervisor shall also digitally stamp and date the respective electronic files of the
deliverable.

7.5.5 Engineering document controller shall distribute the stamped and dated copies of the drawing to the
respective project department.

Quality document controller shall collect 7 copies of the subject package from engineering document
controller and stamp them with associated control number using the controlled copy stamp. Quality
document controller shall distribute the controlled copy assigned to COMPANY recipients and obtain the
receipt signature on the distribution log. (This paragraph shall be revisited upon revising the controlled
copy requirements, if any)
44
 8. CONTROL OF DELIVERABLE
8.1 Control of project documents will be carried out by the engineering document controller with the
following responsibilities:

a. Create and maintain an identification system which ensures that data can be easily retrieved.
b. Receive and register new and revised deliverables.
c. Store and protect original deliverables.
d. Distribute all incoming deliverables.
e. Maintain a record of all incoming and outgoing correspondence and deliverable.
f. Ensure trackability and salvage of deliverables and retrieve stored ones on request.
g. Replace the current drawings with the redline markups in all respective disciplines (Quality, Procurement,
construction zones, etc.).
h. Replace the current drawings with the revised drawings in all respective disciplines (Quality, Procurement,
construction zones, etc.).
i. Distribute the shop drawings to all respective disciplines (Quality, Procurement, construction zones, etc.).

45
9. FILING, STORAGE, AND IDENTIFICATION SYSTEM
9.1 Engineering document controller shall store and file any punchable
documents (two or three holes) in clearly labeled box files with separators
and indices as per a common pattern such as:

i. Each box file will be assigned a number or a name to indicate its contents
ii. An Index Summary Sheet shall register the file content.
iii. Bulky sections shall be subdivided into smaller sections and placed in
separate box files where indices of the current file will be in bold black color
font and rest of related files in regular grey color font.

9.2 Engineering document controller shall assure that original sets are not to
be marked-up nor to be used as working drawings for subsequent revisions

46
 THANK YOU
Continuing to be Proud in What We Build

Wish you all long life with good health

Biggest room in the world is the room of improvement