Attachment 12 - Quality Control Template

TA’AZ CONSTRUCTION

Quality Control

Document Issue Number Revision Number Original Issue Revision Date

Number Date
QC - PR-01 1.0 02 1 Aug 2017 01 Feb 2019
COPYRIGHT
This document contains confidential information. It may be copied in full or in parts only by TA’AZ
Construction personnel and only for the purpose of TA’AZ Construction related activities.
Disclosure of any information contained within this procedure to any person (s) outside the
employee of TA’AZ Construction without written permission of the Top Management is strictly
prohibited.
Document Origin
Originated By: QC Manager Approved By: Project Manager

Jawad Swadi Faiq Salih

Contents

1. PURPOSE 3

2. SCOPE 3

3. RESPONSIBILITIES 3

4. PROCEDURE 3

4.1 TQ TECHNICAL QUERY PROCEDURES 3

4.1.1 REGISTRATION 3
4.1.2 TECHNICAL QUERY FLOW PROCESS 3
TQ Transmittal Flow Chart ............................................................................................................... 7
4.2 TDR TECHNICAL DEVIATION REQUEST PROCEDURE 7
Technical Deviation Request Management ..................................................................................... 7
Suitable Subjects for Technical Deviation Requests ....................................................................... 8
Not suitable subjects for Technical Deviations Requests; ............................................................... 8
TDR Priority Levels .......................................................................................................................... 8
Registration ...................................................................................................................................... 8
Technical Deviation Flow Process ................................................................................................... 8
TDR Development (Part 1 of TDR Form) ........................................................................................ 8
Receipt and review of a Technical Deviation Request (Part 2 of TDR Form) ................................. 9
TDR Work Implementation (Part 3 of TDR Form) ........................................................................... 9
Post work verification (Part 4 of TDR Form) .................................................................................. 10
Closeout (Part 5 of TDR Form) ...................................................................................................... 10
TDR Transmittal Flow Chart shown; .............................................................................................. 10
4.3 RFC READINESS FOR CONSTRUCTION PROCEDURE 11
RFC PROCESS MAP .................................................................................................................... 12
READY FOR CONSTRUCTION PRE-MOB REQUIREMENTS ..................................................... 13
READY FOR CONSTRUCTION (RFC) AUDIT ELEMENTS......................................................... 13
READY FOR CONSTRUCTION ASSESSMENT (RFC) CRITERIA ............................................. 14
4.4 RFI PROCEDURE 15
4.5 RLMU RED LINE MARK UP PROCEDURE 16
4.6 INTERNAL INSPECTION PROCEDURE 17

5. RELATED DOCUMENTS AND RECORDS 17

1. PURPOSE

These procedures show the steps and the guidelines to be followed by the construction
contractor to ensure that performed service adheres to a defined set of quality criteria or
meets the requirements of the client or customer.

2. SCOPE
COMPANY develops and manages production of the Majnoon Oilfield on behalf of the Basra
Oil Company (BOC). The Development Production Service Contract (DPSC) is the contractual
basis between BOC and COMPANY. The first phase is the First Commercial Production (FCP)
of the Majnoon Field which is now complete, with a production capacity of 220,000 barrels
of oil per day.
The Growth Well Pads Preparation project is initiated to support the COMPANY drilling
programme at various Well Pad locations; the scope for this contract includes Greenfield
well pads and Brownfield well pads.
The WORK shall include, but not be limited to, access roads to well pads, site (well pad)
development, internal roads, in-situ and pre-cast concrete works for well cellars, rig slabs,
flow line culverts and pipe & cable tray sleepers, piling works for manifold foundations,
French drains, cable trenches, fencing and HDPE membrane lined pits for drill cuttings.

3. RESPONSIBILITIES

QA/QC Manager is responsible for roll out and awareness of the procedure within the
Project Team. Review queries and potential resolutions

QA/QC Inspector is responsible to make sure that these procedures are to be followed and
implemented on site in a proper manner

4. PROCEDURE

4.1 TQ Technical Query procedures

Technical Query Management

4.1.1 Registration
TQs are registered in the Technical Query database, which is maintained by Company Site
Document Control.

4.1.2 Technical Query flow process

Originator completes Part 1. It is the responsibility of the Originator to complete ALL boxes
(including the ‘check’ boxes) on the TQ form. It is the responsibility of the COMPANY Site
Representative to check and confirm that the Originator has completed this Part correctly
and stated the correct affected documentation. If Originator is COMPANY, their Line
Manager / Supervisor shall act as the COMPANY Site Representative. It is the responsibility
of the TQ Administrator to assign the next sequential number and revision to each TQ that is
being transmitted from all parties prior to forwarding to the EPSC Contractor.

Example shown below of completed Part 1

EPSC Discipline Engineer and Engineering Lead Complete Part 2 and 3. It is the responsibility
of the Discipline Engineer to review, develop a proposed resolution to the query, and gain
support from Engineering Lead. The Discipline Engineer may have to in some circumstances
consult with Company and initiate a study or design change if required. The Engineering
Lead is responsible to review and endorse the proposed resolution by Discipline Engineer.

Example shown below of completed Parts 2 and 3.

COMPANY Representative completes Part 4. Is responsible if applicable, to insert a S.I, F.I,
V.O or Work pack Engineering number. TQ number shall also be added to the relevant
instruction notification so all documentation align with each other. This will allow the work
to be documented, tracked and checked for quality and possibly commercial purposes. If TQ
is rejected sections 4 and 5 do not need to be completed but Section 6 does.

Two examples shown below of completed Part 4.

If recommendation is to be implemented from Engineering, COMPANY Representative to

check the box ‘Follow Engineering Recommendations’. TQ Administrator transmits TQ to
Originator.

Originator and COMPANY Site Representative Complete Part 5. It is the responsibility of the
Originator to track, monitor, expedite the closure of the work and notify COMPANY
representative to inspect / verify that the work has been completed.
Example shown below of completed Part 5.
COMPANY Representative and TQ Administrator Complete Part 6. It is the responsibility of
the COMPANY Representative to verify, sign and notify TQ Administrator that TQ can be
closed out. TQ Administrator receives signs and updates TQ Register once closed out by
COMPANY Representative. Site Document Control scans and distributes closed out TQ to
the relevant parties.
Example shown below of completed Part 6.
TQ Transmittal Flow Chart

4.2 TDR Technical Deviation Request Procedure

Technical Deviation Request Management

Project Technical Deviations Requests (TDR’s) may be raised by personnel in all
departments. The process is described in section 7.3.

All deviations shall be raised using the Project TDR Form (Appendix A). TDR Administrator of
sufficient competence shall be nominated to ensure that deviation requests are given the
appropriate priority and a realistic required response time. The form should include
sufficient information for TDR Administrator to act upon and identify prime disciplines
involved; any relevant supplementary information and/or documents should be attached to
the form. The TDR Administrator should also be in a position to review priorities of
outstanding deviations on behalf of the Project team, especially where delays to their
resolution may occur.

Any TD that has an impact on cost and / or schedule may require having a Variation initiation,
if the TD is approved.
Suitable Subjects for Technical Deviation Requests
Acceptable examples of technical deviation requests may include:

 Request For deviations to Basis for Design (BFD) and Project Specifications.
 Material changes from approved design.
 Change to an appropriate code or standard.

Not suitable subjects for Technical Deviations Requests;

 Contractual Matters
 Material Purchase Requests
 Organisational Changes
 Planning Matters
 Management of plant & process change to plant which has already been commissioned
and handed over
A Technical Deviation Request (TDR) will be made if the Project Team or Contractor is unable
to comply with the Codes, Standards or Project Technical Specifications.

TDR Priority Levels

To assist those raising Project Technical Deviation Request to set priorities, the following
categories are provided for guidance:

High: Has a high potential to compromise project schedules, or HSE performance;

requires a response from Engineering Contractor within 4 working days or
sooner after receipt of the query.

Medium: Failure to resolve could have medium term implications with respect to
project schedules, or HSE performance; requires a response from Engineering
Contractor within 5 working days.

Low: Has little impact on project schedules or HSE performance, but may provide
an improvement in operating efficiency; requires a response from
Engineering Contractor within 6 working days.

Registration
TDR’s are registered in the Technical Deviation database, which is maintained by TDR
Administrator.

Technical Deviation Flow Process

TDR Development (Part 1 of TDR Form)

When a requirement to raise a TDR has been identified, the Originator shall ascertain the
need for, and compile all relevant information:

 Deviation description
 Reference number of Procedure, Specification or standard applicable to proposed
deviation.
 Status of Deviation (permanent or temporary).
 Plant and Unit of Equipment
 Information on initiator (Name, Position)
 Details of Deviation Request (proposal, justification)
 Risk assessment (mitigation and control measures).

All the relevant associated documents must be attached to the TDR prior to submission.
Each TDR shall be given a unique number by TDR administrator.
TDR’s shall be categorised as priority rating mentioned in 7.1.2

Receipt and review of a Technical Deviation Request (Part 2 of TDR Form)

Originator liaises with COMPANY Site Field Engineering Lead once Originator generates TDR,
COMPANY Site Field Engineering Lead is responsible to check and confirm that the
Originator has completed Part 1 correctly and stated and submitted the correct
documentation. It is the responsibility of the TDR Administrator to assign the next
sequential number and revision to each TDR that is being transmitted from all parties prior
to forwarding to the EPSC Contractor. A register shall be kept and maintained, reference to
the project Identifier, discipline sequential number.

SDC forwards the completed form to EPSC focal point for input to the review and approval
or rejection. In all instances of a TDR being assessed, care should be taken to ensure that it
does not compromise, health, safety and/or the environment.

Once the TDR is considered valid, the TDR must be forwarded to the appropriate COMPANY
Technical Authority, who shall review all comments, decide on their acceptability, and
recommend approval, or rejection of the TDR.

Once the TDR is approved and commented by appropriate TA and any other required
parties i.e. Safety, Project Engineer, and Project Manager. It shall be endorsed or rejected
and issued for implementation.

TDR Work Implementation (Part 3 of TDR Form)

COMPANY Field Engineer receives returned TDR. Liaises with TDR administrator for
registering deviation in the system. COMPANY Representative completes Part 3 and is
responsible if applicable, to insert a S.I, F.I, V.O or Work pack Engineering number. TDR
number shall also be added to the relevant instruction notification (if applicable) so all
documentation align with each other. This will allow the work to be documented, tracked
and checked for quality / commercial purposes. If TDR is rejected Part 3 and 4 do not need
to be completed but Part 5 does.

If recommendation is to be implemented from Engineering, COMPANY Representative to

check the box ‘Follow Engineering Recommendations’. TDR Administrator transmits TDR to
Originator.
Post work verification (Part 4 of TDR Form)
Originator and COMPANY Site Representative complete Part 4. It is the responsibility of the
Originator to track, monitor, expedite the closure of the work and notify COMPANY
representative to inspect / verify that the work has been completed.

Closeout (Part 5 of TDR Form)

COMPANY Representative and TDR Administrator complete Part 5. It is the responsibility of
the COMPANY Representative to verify, sign and notify TDR Administrator that TDR can be
closed out. TDR Administrator receives signs and updates TDR Register once closed out. Site
Document Control scans and distributes closed out TDR to the relevant parties.

TDR Transmittal Flow Chart shown;

4.3 RFC Readiness for Construction procedure

The RFC process starts after contract award with the KOM. The Contract Holder, Area
HSE Lead, HSE RFC Engineer and the contractor agree a date for screening the RFC
requirements against the contract scope. This occurs during a Clarification/
Expectation meeting. Within 7 days from the KOM the contractor shall develop and
submit project specific contract pre-mobilization documentation.

Within 28 days from the KOM, the Pre-mobilization documents are to be submitted by
the contractor through Document Management System (ASSAI) for COMPANY review.
When submitted contract documentation is approved in code-1 or code-2, the RFC
Report shall be prepared by RFC HSE Engineers and endorsed by Contract Holder,
Contract Owner and Area HSE Lead. This provides approval for the contractor to start
mobilizing activities.

RFC Checklist elements are given a “green” or “amber” status, which indicates whether
the elements are fully in place, or need further work before allowing an activity to take
place. The RFC shall be signed by CH, CO, Area HSE Lead, RFC Engineer and Contractor
PM. An RFC Verification Audit will take place after 30 days of issuing the RFC and will
evaluate the effectiveness and the implementation of the approved documents,
arrangement and agreements listed into
the RFC Matrix. Additionally, pending items of the signed RFC Checklist will be tracked to
completion.

The Verification Audit is to be carried out by an assigned COMPANY Team, which

includes relevant SMEs. The RFC HSE Engineer shall perform the role of Audit
Coordinator. RFC HSE Engineer shall liaise with audit team members and follow-up on
documents throughout the audit. If contractor fails to achieve a minimum of Code 2 for
any document/requirement or fails to provide evidence during the desktop review, the
Contract Holder has the right to
start a corrective action process which can be additional coaching or may lead to cancellation
of the contract.
RFC PROCESS MAP
READY FOR CONSTRUCTION PRE-MOB REQUIREMENTS

The required pre-mobilization elements are the following:

 Social Performance plan

 HSE plan
 HSE MS
 Subcontractor selection process
 Security plan
 Security interface documents
 Journey management Procedures
 Road safety plan
 Drug and alcohol protocol
 Emergency response plan
 Medical Facility (Proposal)
 PPE procedure
 Environmental management procedure including Environmental plan, Waste
management plan and Spill plan.
 Working at height procedure
 Working in hot climate procedure
 Electricity procedure
 Hot work procedure
 Excavation procedure
 Confined entry space procedure
 Scaffolding procedure
 Isolation procedure
 Quality plan

The pre-mobilization phase process is mainly about documentation.

Review of the HSSE & SP and QA/QC Documentation will be against COMPANY procedures
and standards that include CSSS and 7 Pillars coaching.

RFC HSE Engineer shall issue weekly updates to Contract Holder and HSSE&SP Lead until the
process is completed.

READY FOR CONSTRUCTION (RFC) AUDIT ELEMENTS

 Preparation
 Road Transportation and Journey Management
 Medical Emergency Response
 Training and HSSE Resources
 (Toxic) SIMOPS & H2S (brownfield only)
 PPE
  Environmental Management
 Camp facility and infrastructure
 Worksite Hazard Management
 HSE Management System

Each of the above elements is further divided into sub-elements specific to the area of
focus. Some of the elements do not need to be fully in place at the time of completing the
RFC e.g. ongoing training programs.

The RFC Checklist is issued with a Rev. Number for tracking purposes.

It is imperative that submitted documentation is contract specific, reflects current

requirements and is of auditable quality.

The assigned RFC Team shall review and assign review Code into ASSAI within 2 weeks of
receiving the document. It is recommended to carry our regular meetings with the
contractor to close any gaps and achieve conformance.

READY FOR CONSTRUCTION ASSESSMENT (RFC) CRITERIA

The assessment criteria for the RFC Audit is based on the attached RFC Matrix Document
provided in Appendix 1. All elements are applicable to the project unless excluded during
the expectation meeting.
RFC HSE Engineer will fill the RFC Matrix and assign the colour code according to the
reviewed document code.

If a particular element is not relevant to the scope of services, it can be excluded from the
RFC during the clarification meeting.

If the assessment results in Red, contractor shall not be permitted to commence the works,
Contract Holder shall start corrective actions as per contract.

If the assessment results in Amber, it is subject to COMPANY’s derogation process whether

the contractor may proceed with limited scope and action plan.

All mandatory requirements have to be either Green of Amber for the contract to proceed.

Under certain circumstances, contractor mobilization to site may proceed while other
documentation is still being prepared. Derogation shall apply in these circumstances. E.g.
Mobilization of site facilities may proceed while SIMOPS procedure is still being prepared.
4.4 RFI procedure

 Requirements for COMPANY to inspect the contractor’s works shall be defined in the
contractors ITP when submitted for approval. Those items nominated by COMPANY as
either Witness or Hold points shall require the contractor to raise and submit a RFI.
 RFI shall be submitted to COMPANY as defined in this procedure and must be received in
COMPANY DC a minimum of 24 hours prior to contractor planned inspection time,
exceptions to be discussed and approved by COMPANY Field Quality Team.
 When work is complete the contractor construction supervisor shall raise the RFI, sign
and date and pass manually to the relevant COMPANY construction representative for
verification of readiness to inspect. COMPANY construction representative shall sign and
date the RFI.
 Contractors QC inspector and COMPANY inspector shall jointly agree the readiness for
inspection to proceed and sign and date the RFI form.
 Contractor shall then submit the RFI complete with all relevant design drawings and
documents through contractors document control function to COMPANY DC.
 COMPANY DC will forward the RFI package by email in a timely manner to the assigned
COMPANY discipline inspector so he can plan his inspection and coordinate with the
contractor’s inspector.
 In most cases the COMPANY and contractors’ inspector will carry out a joint inspection,
but there may be occasions when inspections are completed separately.
 A Witness point is not a mandatory inspection point. However; if the COMPANY inspector
does not attend the inspection within a one-hour period after the time on the RFI then
the contractor may continue the work.
 A Hold point is mandatory and cannot be passed before the COMPANY inspector and
contractor’s inspector have accepted the work in alignment with Clause 7.2.
 The work being inspected shall be either accepted or rejected.
 For accepted work the contractors’ QC inspector and COMPANY QC inspector shall sign
and date the RFI form to verify their acceptance.
 Contractor shall retain the original accepted RFI package for inclusion in the final
construction handover dossier.
 For work rejected the contractor QC inspector and COMPANY QC inspector shall agree
the disposition and annotate the RFI form accordingly clearly stating the reason(s) for
cancellation/rejection/not ready for inspection.
 Rejected work shall be subject to a new RFI.
 Rejected RFI forms shall be retained by contractor alongside the final accepted RFI form
for the work and included in the final construction handover dossier.
 Contractor shall send copies of completed RFI forms for both accepted and rejected work
through COMPANY DC for company records.
 COMPANY inspectors shall make sure the records of all inspections are retained for ready
reference during contract duration.

COMPANY DC will pass a copy of the completed accepted/rejected RFI forms to the
discipline COMPANY inspector and QC clerk to allow traceability records to be maintained.
4.5 RLMU Red Line Mark Up procedure
The scope of the procedure covers the drawings/documents that are used by
Construction Contractor and is limited to the list of drawings/documents type enclosed as
per Appendix A – that defines which document/drawing types are to be Redline marked-
up, produced As-Built, then used for 3D model update (where applicable) and finally
returned to COMPANY as approved As-Built drawings.
Document types are also referenced to the Tier number from “The Production Standard
Critical Documents and Drawings (OE)”. Tier 1 documents shall always be maintained
in 2 hard copies (master and slave).
It is the responsibility of the Engineering Manager to make sure all these documents are
undergone the RLMU and, where necessary, As-Built.
Project manager is accountable for ensuring that this process is carried out in a
controlled manner prior to FAC (Facility Acceptance Certificate) is issued.
The drawing/document list shall be maintained and matured throughout the project
execution. The As-built Package (DCAF ID 435) requires a QA check of the following
elements on the list:
 completeness of as-built drawings, records and specifications;
 availability of vendor documentation for all equipment; and
 operating and maintenance procedures against experience gained during
commissioning.

As an example, such list for FCP Gas is referenced to as “List of Critical Documents for
FCP Gas (Sweet)”, document number TGRS-GEN-SIP-JA-6611-0001.

This procedure supports RLMU preparations for Start-Up from Mechanical Completions
through Commissioning and As-building of the selected drawings/documents after Start-up
until Transfer of Ownership to the Asset, as illustrated in Figure1 Handover Flow Diagram

Figure1 Handover Flow Diagram

Note that this procedure is specifically intended to manage the documents after
construction of an appropriate area of work has been completed. This procedure shall
NOT be used as a method of making construction changes to documentation before
installation. Where changes are to be made before construction or installation, the Design
House is expected to release a revised AFC document, a Construction Contractor would
be expected to agree any changes with Construction Management or use Majnoon IM
Systems to gain agreement and approval prior to construction or installation.

4.6 INTERNAL INSPECTION PROCEDURE

This procedure covers the process steps of completing the work on site through closing the
RFI and getting the final acceptance from the client
The first step of this procedure starts with the QC inspector on site, who is observing the
progress of all the activities on site on daily basis, once an activity is completed 100% the
inspector checks the work thoroughly to make sure that the work has been done according
the required specification, in case there are some remarks, the QC inspector informs the site
engineer to fix it, after getting the work completed 100%, the QC inspector fills a check list
record on site and then hand over this list to the QC department manager to attach this list
with the RFI (request for inspection) and submit to the client’s document control officially
for the external final inspection
Check list records are attached

5. RELATED DOCUMENTS AND RECORDS

Excavation, filling and backfilling inspection record
Field concrete pouring record
Reinforced concrete pouring record
Road work inspection record
 MAJNOON OIL FIELD ITR No: C-0205E
SOUTHERN IRAQ Project document number
P4A-GEN-TAZ-QA-5733-0002
INSPECTION TEST RECORD Rev. : 001
Earth Works
Project No: BOC-1694

(SITE PREPARATION, EXCAVATION, FILLING AND Record No :

BACKFILLING )

Drawing No: Rev:

RFI #: Record # Date:

Structure/member
Area

Sl.no Description of Inspection Activity Result

1 Underground (UG) services drawing checked and all UG services locations

marked.

2 Inspection of setting out/ grid reference/ bench mark and steel/wood pegs
indicating various elevations
3 Inspection of clearing backfilling area from construction debris
4 Inspection of soft spots if any
5 Verification of fill material test reports
6 Inspection of excavation area setting out and mark up
7 Inspection of formation level
8 Inspection of impermeable membrane if any
9 Inspection of concrete protective system
10 Verification of protective coating thickness report if applicable
11 Verification of compaction test reports
12 Inspection of finish level
Remarks:

Record Acceptance
Contractor QC COMPANY QC
Name

Signature

Date
 ITR No: C-0302X
INSPECTION AND TEST PLAN Project document no:
CONCRETE WORKS P4A-GEN-TAZ-QA-5733-
0001
BOC-1694
INSPECTION TEST RECORD Rev.: 001
REINFORCED CONCRETE PRE-POUR Contract no: BOC-1694
Drawing no: Rev.:
RFI no: Record: Date:
Structure/member:
Area:
Sl Description of Inspection Activity Result
no:
1 Formation level inspection (visual)

2 Verification of compaction test report for formation level

3 Blinding concrete thickness is as per IFC drawing

4 Formwork dimensions are as per IFC drawing

5 All setting out verified by Surveyor including anchor bolts and blinding concreting
level and all dimensions checked and correct within tolerances (Survey Report
attached as necessary)
6 Form surface cleanliness verified

7 Reinforcement number, size, spacing and binding inspection. Binding wire shall be
tucked inside.
8 Reinforcement is free of loose rust, grease, oil, paint or any other deleterious
material
9 Reinforcement cover shall be in accordance with IFC drawing

10 Anchor bolts dimension in plan and elevation verification

11 Form work cleaned to remove dust and binding wire cut pieces. Form work
cleaning pocket closed
12 Fresh concrete sampling and testing inspection

Remarks:

Record TAAZ QC COMPANY QC

Acceptance
Name:
Signature:
Date:
 ITR No: C-0303X
INSPECTION AND TEST PLAN Project document no:
CONCRETE WORKS P4A-GEN-TAZ-QA-5733-
0001
BOC-1694
INSPECTION TEST RECORD Rev.: 001
REINFORCED CONCRETE POST-POUR Contract no: BOC-1694
INSPECTION RECORD
Drawing no: Rev.:
RFI no: Record: Date:
Structure/member:
Area:
Sl Description of Inspection Activity Result
no:
1 Inspection of concrete top surface finishing

2 Inspection of top surface curing and protection method

3 Inspection of vertical surface finishing after striking form work

4 Inspection of vertical surface curing and protection method

5 Curing compound application verified (if any)

6 Anchor bolts in plan and elevation verified

7 Defects like cracks, honeycomb or damage to concrete noticed

8 Protective coating application is satisfactory

9 7 days concrete compression test result verification

10 28 days concrete compression test result verification

Remarks:

Record TAAZ QC COMPANY QC

Acceptance
Name:
Signature:
Date:
 ITR No: C-0306X
INSPECTION AND TEST PLAN CONCRETE Project document no:
WORKS BOC-1694 P4A-GEN-TAZ-QA-5733-
0001
INSPECTION TEST RECORD Rev.: 001
HOT WEATHER CONCRETING INSPECTION Contract no: BOC-1694
RECORD
Drawing no: Rev.:
RFI no: Record: Date:
Structure/member:
Area:
Sl Description of Inspection Activity Result
no:
1 Ambient temperature at pouring time is < 45C0

2 Formwork cleanliness checked before pouring concrete

3 Fresh concrete temperature at batching plant

4 Fresh concrete temperature at pouring location

5 Ice or chilled water used for concrete production

6 Cast concrete surface is covered with polythene sheet and wet hessian after
surface finishing
7 Wet hessian is kept continuously wet by spraying water post concrete set

8 Curing compound application is completed

9 Evidence of surface cracks if any after 24 hours post pour

10 Evidence of surface cracks if any during form work striking

11 7 days compressive strength report verification

12 28 days compressive strength report verification

Remarks:

Record TAAZ QC COMPANY QC

Acceptance
Name:
Signature:
Date:
 ITR No: C-0305X
INSPECTION AND TEST PLAN CONCRETE WORKS Project document
BOC-1694 no:
P4A-GEN-TAZ-QA-
5733-0001
INSPECTION TEST RECORD Rev.: 001
FIELD CONCRETE POURING RECORD Contract no: BOC-
1694
Drawing no: Rev.:
RFI no: Record: Date:
Structure/member:
Area:
Sl no: Truck no: Ticket Concrete Cumulative Batch time: Pouring Pouring Slump Temperatur Number of Remarks
no: Volume Volume Start time: Finish time: (mm): e (C0): cubes :
supplied: supplied: made:

Record Acceptance Tested by Taaz QC COMPANY QC

Name:
Signature:
Date:
 MAJNOON OIL FIELD ITR No: C-403R
SOUTHERN IRAQ Project Doc No:
P4A-GEN-TAZ-QA-5733-0003
INSPECTION AND TEST PLAN FOR ROAD Rev. : 001
WORKS & ASPHALT WORKS
Project No: 1694
Road Works Inspection Record
Page : 18

Drawing No: Rev:

RFI #: Record # Date:

Structure/member
Area

Sl.No Description of Inspection Activity Results

1 Survey report verified
2 Sub-grade material certificates verification
3 Sub-grade compaction surface preparation verified
4 Sub base test certificates verification
5 Sub base material thickness verified
6 Road base material test certificate verified
7 Road base material thickness verified
8 Sub-grade, sub base and road base compaction test reports verified
9 Prime coat application verified
10 Tack coat application verified
11 Asphalt mix design approval verified
12 Base course asphalt thickness verified
13 W earing course asphalt thickness verified
14 Asphalt compaction test reports verified and is satisfactory
15 Road marking and road signs installation verified and is satisfactory
Remarks :

Record Acceptance
TAAZ QC COMPANY QC
Name

Signature

Date