Professional Documents
Culture Documents
PROCEDURES FOR
REDLINE, REVISION, SHOP, AND
AS-BUILT DRAWINGS
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.
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.
11
3.DEFINITIONS AND ABBREVIATIONS
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.
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.
17
4.REFERENCES
SAEP-334 :Retrieval, Certification and Submittal of Saudi Aramco Engineering & Vendor
Drawings
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
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.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
27
7. PROCEDURE 7.1 R EDLINE M ARKUP
28
7. PROCEDURE 7.1 R EDLINE M ARKUP
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
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.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.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.
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.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.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:
42
7. PROCEDURE 7.5 COMPANY REVIEW AND APPROVAL
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