P051 Project Instruction - Approved Rev 3

8/2/2019 P051 Project Instruction - Approved Rev 3

1/24

P051

HODARIYAT BRIDGE

Aconex Project Instruction

NOTE

This is a live document.

It will require periodic updates to reflect the progress of the project.

Initial authorship by TDIC & Aconex


2/24

TABLE OF CONTENTS

1.0 INTRODUCTION ........................................................................................................... 3

1.1 Aconex 31.2 Getting Started with Aconex 31.3 Aconex System Terminology 4

2.0 ABOUT THIS DOCUMENT .............................................................................................. 5

2.1 Purpose 52.2 How to Use 52.3 Custodianship 5

3.0 PROJECT INFORMATION ...............................................................................................6

3.1 Project Details 63.2 The Project Team 7

4.0 CONTROLLED DOCUMENTS .......................................................................................... 9

4.1 Required Document Fields 104.2 Optional Document Fields 114.3 Disciplines 124.4 Numbering Convention 144.5 Title Convention 174.6 Status 174.7 Revision Convention 18

Other Document Field Values 18

4.8 Document Distribution 195.0 PROJECT MAIL ........................................................................................................... 20

5.1 Project Mail Numbering Convention 205.2 Project Mail Type 205.3 Project Mail Attributes 225.4 Time Constrained Project Mail 235.5 Subject Line Conventions 235.6 Project Mail Approval 235.7 Auto Mail Prefix 235.8 Project Correspondence Protocol 24

CONFIDENTIALITY AND INTELLECTUAL PROPERTY STATEMENT

The information contains confidential information and uses an Aconex proprietary template. This document must not be used ordisclosed for any purpose other than in connection with the implementation or use of the Aconex system (the Purpose). .

The intellectual property in this template (and any modification, enhancement, derivation or reproduction of it) is owned by Aconexand licensed solely for the Purpose and the licence of the original or modified document can be terminated by Aconex at any time at

its absolute discretion. The Aconex name, logos and URLs are the property and/or marks of Aconex.

Any modification, enhancement, derivation or reproduction of this document must contain this Confidentiality and Intellectual PropertyStatement and any other confidentiality and any other similar markings or legends contained herein.

Any questions based on the confidentiality or ownership of this document should be directed to [email protected]

P051-TDI-PW-GEN-PRC-0001 Rev 3 2
mailto:[email protected]:[email protected]:[email protected]


3/24

1.0 INTRODUCTION

1.1 AconexAconex have been engaged on this Project by TDIC as the online collaboration system for this project.

1.2 Getting Started with AconexTo access Aconex, you require an internet connection, the latest internet browser installed on your computer and toenrol in the Aconex training offered to all project participants.

Aconex does not require you to install any licensed software to access the system.

The Aconex Client Operations team will be available to guide the entire project team through Aconex implementationand support all project members throughout the project life.

1.2.1 Internet Access

Aconex recommends the use of broadband internet to optimise the Aconex experience, in particular wheredownloading and uploading of large files is required.

Broadband varies in download and upload speeds or bandwidth capacity. The optimal broadband bandwidth capacityfor your organisation will depend on the number of users and network configurations of your IT systems.

Please check with your local IT Manager or Internet Service Provider (ISP) to confirm the details of yourOrganisations broadband capacity.

1.2.2 Internet Browser

Aconex recommends using the latest version of Internet Explorer or Mozilla Firefox as your internet browser. Thelatest internet browsers are available free to download fromwww.microsoft.com/ie (PC) and www.mozilla.com(PC/Mac OSX).

Please check with your local IT Manager to confirm the version of your internet browser.

1.2.3 Implementation ProcessThe implementation process will be facilitated by Aconex. The process will require participation and input from keyproject stakeholders to assist in defining the appropriate system configuration for the project.

1.2.4 Training

Ongoing support and training is available to all project participants throughout the project life. To request trainingplease contact Aconex on 800 226639 (ACONEX) or submit details online athttp://www.aconex.com/Contact/Contact-Us/Request-Training.html or email [email protected]

Aconex provides 24/7 helpdesk support for all members globally. A list of Global Helpdesk numbers and officelocations can be found on www.aconex.com

The following training courses are available to all users. Please note that, wherever possible, the sessions will becustomised as per project/ group requirements.

TABLE 1 - ACONEX TRAINING COURSES

Course Name Course summary Duration

Basic Documents and Mail

Designed for new users of Aconex. It covers fundamentalaspects of the system including Aconex overview, generalnavigation project mail and document management withinAconex.

2 hours

Organisation AdministratorThis session covers the setup for a specific organisation ofadditional users, setting security levels and disabling users oncethey are no longer part of the project/ organisation

1 hour

Multiple Document UploadAimed at users who are required to upload, register, supersede

and transmit multiple documents.1.5 hours

http://www.microsoft.com/iehttp://www.microsoft.com/iehttp://www.mozilla.com/http://www.aconex.com/Contact/Contact-Us/Request-Training.htmlmailto:[email protected]://www.aconex.com/http://www.microsoft.com/iehttp://www.mozilla.com/http://www.aconex.com/Contact/Contact-Us/Request-Training.htmlmailto:[email protected]://www.aconex.com/


4/24

Course Name Course summary Duration

Advanced DocumentsCovers the use of more advanced features/ functionality withinthe Documents module. This session is often used inconjunction with the Multiple Document Upload session.

1 hour

Bulk Processing

Bulk processing enables mass uploading of documents and

linking to the metadata information contained within an Excelspreadsheet. This is very useful where there is a large amountof historical documents to upload or where document numbersneed to be reserved in the register for future documentdeliverables.

1.5 hours

When delivering to a specific project team, this document will be referenced to reflect the agreed projectconfigurations are implemented.

1.3 Aconex System TerminologyAconex staff utilise terms which will also be utilised throughout this document and are specific to the Aconex system,training and implementation. Heavily used Aconex terminology is detailed and defined in the table below.

TABLE 2 - ACONEX SYSTEM TERMINOLOGY LISTTerminology Definition

Aconex Client The Organisation that engaged the services of Aconex for the project.

Controlled Document A document which is registered with multifaceted, searchable metadata and a completedocument, transaction history.

Document Register An electronic registry of all documents that have been registered by your Organisation orreceived by transmittal from other Organisations.

Key Contact The primary point of contact for Aconex staff throughout the project lifecycle. This may bethe Aconex Client or an Organisation delegated as key contact by the Aconex Client.

Mandatory Field A field which requires completion. All fields which require completion and are marked witha red asterisk (*).

Organisation A registered entity in Aconex who manages their own Organisation members and projectinformation.

Org Admin An Aconex role which performs administrative functions for their Organisation such ascreating and administrating new member accounts and Organisation security.

Project Admin An Aconex role which administrates and manages project wide settings and updatesAconex and associated documents with any procedural changes decided upon.

Aconex ProjectProtocols

A document created to provide a record of agreed system configuration, protocols andprocedures associated with using Aconex on the project. The document will also be usedto facilitate the implementation process.

Project Mail Project correspondence which contains searchable metadata to assist with retrieval andreporting of all communication between project participants.

Register The process of uploading (onto Aconex) and tagging an electronic file with appropriateproperties and categories according to pre-defined fields.

Supersede The process of updating a previously registered document with the latest version andplacing the previous version in the document history.

Training Coordinator The Training Coordinator is responsible for organising and scheduling training sessions forproject participants, at either for their Organisation or for all participants on the project.

Transmittal Method of issuing documents from your Organisations document register to anotherOrganisations document register.

Unregistered File An electronic file uploaded into the document register (unregistered tab) but not taggedwith metadata as yet.



5/24

2.0 ABOUT THIS DOCUMENT

2.1 PurposeThe purpose of this document is to assist with the implementation process and record the agreed systemconfigurations, protocols and procedures associated with the use of Aconex on the project.

2.2 How to UseThis document is specific to the Aconex collaboration system and shall be read in conjunction with but not limited toall other project specific manuals, plans or procedures applicable to the project.

In general this document is to be used in the following but not limited to the following scenarios:

Existing and new project participants that wish to familiarize themselves with what system configurationshave been defined for their organization.

Existing and new project participants that wish to refer to project procedures that have been mapped toAconex.

Org Admins and Project Admins that are required to perform the initial configuration or make amendments tothe project setup.

Aconex will also use this document in training situations and when performing periodic health checks.

2.3 CustodianshipThis document is a live document. It is expected that project information requirements will change over the course ofthe project lifecycle as the project and participants change.

This document will be required to be updated to reflect changes to system settings, processes, project participantsand procedures.

The ongoing management of this document will reside with the nominated custodian who is Mia Merrigan from TDICand will be supported by the local Aconex Client Operations team.

All proposed changes/amendments to details or procedures detailed in this document must be submitted to the

nominated custodian for approval prior to implementation.



6/24

3.0 PROJECT INFORMATION

3.1 Project DetailsTABLE 3 - PROJECT DETAILS

Project Name* GG101 Hodariyat Bridge

Project Short Name* GG101 Hodariyat Bridge

Phone Number 02 4036200

Fax Number 02 4061500

Project Start Date* 1 October 2009

Estimated Completion Date* 28March 2012

Project Address

City/Suburb* Abu Dhabi

Postcode* 126888

Country* UAE

Project Description Cable Stayed Bridge from Abu Dhabi Island to Hodariyat Island

(*) Mandatory field required for project setup.



7/24

3.2 The Project Team

3.2.1 Communications Flow Diagram

The expected flow of communication on the Project is detailed in the figure below.

FIGURE 1 - PROJECT COMMUNICATIONS FLOW DIAGRAM

P051-TDI-PW-GEN-PRC-0001 Rev 3

Client(TDIC)

Engineer(Parsons)

Sub-Contractor

Main Contractor(AVJ)

General Project Communications/ Mail

Sub-ContractorSub-Contractor

ConsultantsConsultants

7


8/24

3.2.2 Project Key Contacts

The following table lists the contact details of the key contacts for each organization and the relevant Aconex projectinformation.

Project participants are to contact their respective key contact for all matters relating to the use of Aconex.

TABLE 4 PROJECT KEY CONTACTS

Key Contact Information Aconex Project Information

Organization Name Role ContactDetails

Org

Prefix

Project

Role

AC KC PA TC OA

TDICMiaMerrigan

ProjectAdministrator

02 4061672 TDI CL

TDICDavid (Dai)Lewis

SR ProjectManager

056 1057588 TDI CL

TDIC Paul WilsonCommercial

Manager0 2 4 03 65 16

050 3961207TDI CL

Aconex Amro RafeeAccountManager

050 2729551 ACX CN

AconexTrainingCoordinator

04 4287474 ACX CN

OVERSEAS AST /VSL MIDDLEEAST JV

BrunoThierry

ProjectDirector

050 4531097

AVJ MC

TBC IBT CN

TBC TGP CN

PARSONSINTERNATIONALLIMITED

Frederic

Turlier

Resident

Engineer

050 8176087

PIL-P051 LC

Code Project Role

CL Client

LC Lead Consultant

CN Consultant

HC Head Contractor

SC Subcontractor

Code Aconex Role

AC Aconex Client

KC Key Contact

PA Project Admin

TC Training Coordinator

OA Org Admin



9/24

4.0 CONTROLLED DOCUMENTS

This section details the fields and values associated with managing project documents using Aconex.

All project participants when registering documents must apply the appropriate document tags defined by for theproject. The document tags are the key information or metadata fields that are used to identify the document such

as Number, Title, Date Created. As a minimum Aconex requires all registered documents to be tagged withmandatory fields (denoted by red asterisks).

FIGURE 2 SAMPLE PROJECT DOCUMENT REGISTRATION FORM



10/24

4.1 Required Document FieldsThe following table details the mandatory Document Fields applicable to the project. When registering a document,all of following fields must be completed.

TABLE 5 REQUIRED DOCUMENT FIELDS

Field Label Field Type Description of Use/Application Table/Figure

Reference

Search

Field

DocumentNo*#

DocumentNumber

For tagging a document with the unique numberrequired by the applicable document numberingconvention.

Figure 3 Y

Revision*# Text For tagging a document with a revision reference(applicable project convention) when it is updated.

Y

Title Text For tagging a document with the applicable titledescription associated with the document.

Y

Type*# List (SingleSelect)

For tagging a document to classify it with anappropriate document type.

Table 8Y

Status*# List (Single

Select)

For tagging a document with the appropriate status

reference that is relevant to the document lifecycle. Table 9 Y

Discipline List (SingleSelect)

For tagging a document with an appropriatediscipline classification.

Table 7 Y

Revision Date Date For tagging a document with a date when therevision was created.

Y

DateUploaded*#+

Date System defined field. Date of when file wasuploaded.

Y

Attribute 1 - List (MultiSelect)

For tagging a document with one or more values ofinformation to assist with categorization. ExampleZones within the project.

Table 10 Y

Job Code List (Multi

Select)

For tagging a document with one or more values of

information to assist with categorizationTable 14 Y

For additional fields to tag your documents please discuss with your Project Administrator or Aconex ClientOperations Representative.

(*) System mandatory field and cannot be disabled (i.e they must be used).(#) Field label can not be renamed.(+) Field with specific function controlled automatically by Aconex system.



11/24

4.2 Optional Document FieldsThe following table provides optional document fields available for tagging documents with additional information.When registering a document, the following fields can be completed if required.

TABLE 6 OPTIONAL DOCUMENT FIELDS

Field Label Field Type Description of Use/Application Table/FigureReference

SearchField

Confidential# ConfidentialityCheck Box

For defining who can have exclusive access to theregistered document.

N

File# File For attaching the electronic file relevant to theregistered document.

N

Print Size# Text For detailing the print size requirements to assistusers when printing the document.

N

Reference Text For tagging a document with specific referenceinformation relating to the document.

Y

Date Created Date For tagging a document with a date when it was first

created. N

Author Text For tagging a document with details of the author. Y

Comments Text Area For entering comments relevant to the document. N

PackageNumber

List (MultiSelect)

For tagging a document with one or more values ofinformation. Example Package Numbers within theproject (subcontractors)

Table 15 Y

(*) System mandatory field and cannot be disabled (i.e they must be used).(#) Field label can not be renamed.(+) Field with specific function controlled automatically by Aconex system.

For additional fields to tag your documents please discuss with your Project Administrator or Aconex Client

Operations Representative.



12/24

4.3 DisciplinesThe document disciplines in use for this project are detailed in the following table. When registering a document,select discipline most suitable from the drop down list.

If a discipline does not exist on Aconex and is required by your organisation, submit a request to the Aconex Client.

TABLE 7 DOCUMENT DISCIPLINESDiscipline Code Application/Use

Architectural ARC Ceiling Details, Door Schedule, Elevation, Floor Details, Floor Layouts,Reflected Ceiling Plans, Sections, Site Plans, Toilet Details, Wall Details

Authorities & GovernmentDepartments

AUT Abu Dhabi Terminals, ADDC, ADNEC, ADNOC, ADSSC, ADWEA, Al AinWildlife, Building Directorate, Chamber of Commerce, Civil Aviation, CrownPrince, Cultural Foundation, Department of Social Services & CommercialBuilding, EAD, EMPOST, Environmental Agency, ETISALAT, ExecutiveAffairs Authority, Executive Council, Finance Department, GASCO, GeneralAuthority for Health Services, License & Traffic Directorate, Military/ArmedForces, Ministry of Economy Under Secretary Office, Ministry of Transport,Petroleum Port Authority,Police Department, Port Authority, Presidential,TEBODIN, Town Planning Department, TRANSCO

Civil Works, Roads andbridges

CIV Bridges, Civil, Contours, Grading, Infrastructure, Islands & roundabouts,Krebs, Parking Bays, Ramps, Retaining Walls, Road Centerlines, Roads,Spot Elevation Heights, Survey Equipment & Supply, Survey Information,Traffic Impact Studies, Tunnels.

Commercial COM Contracts, Variations, Notice of Claim, Variation Orders.

Contracts Administration CTA Contracts, Variations.

Design & Master Planning DMP Concept Design, Design Workshops, Development Study, Master Planning,Planning Design Regulations, Satellite Imagery, Tender Presentations,Topographic Mapping Services, Urban Design Review, Urban Planning

Environment & Ecology ETE Archaeological Studies, Chemical Analysis of Soils, ConstructionEnvironmental Management Plan, Ecological Surveys, Environmental ImpactAssessments, Marine Studies, Traffic Impact Studies

Financial Management FNM Advance Payment Guarantee, Approved Variations, Control Budget,Employers Instructions, Estimates, Financial Reports, Performance Bond,Proposals/Claims, Valuations, Payment Certs.

General GEN Meetings, Monthly Reports, Photography, Site Photographs, Transportation,Travel, Weekly Reports

Hard and Soft Landscape LAN Irrigation, Parking Lots, Pedestrian Paving, Precincts, Roadways, Trees &Plants

Health & Safety HSE Health, Safety

Legal LGL Claims, Contract Drafting, Insurance Certificate

Municipality Liaison MUN Abu Dhabi Municipality, Building Permits, Land Department, Park &Agriculture Section, Permits & Permissions, Roads Department, Saadiyat

MunicipalityProgram Management PMG Master Schedule, Progress Reports, Project Management Plan, Scheduling,Technical Program

QA/QC QAC 3rd Party Labs, Audit, Check Lists, Confirmation of Verbal Instruction (CVI),Field Change Request, Forms, Inspection & Test Plan, Material Approval,Method Statements, Mock-ups, Non-Conformance Report (NCR), Notice ofCommencement, On Site Labs, Organization Chart, Project Quality Plan,Project Quality Procedure, QA/QC Procedures, RFI's, Site Instruction,Supervision, Suspensions/Stop of Work, Test Equipments, Water Main

Site Management SMG Demobilization, Hazardous Waste Remediation, Labour Camps, Mobilization,Security Services, Service Tunnels, Site Administration, Site Clearing, SiteDemolition, Site Earthworks, Site Electrical Items, Site Offices & Facilities,Site Preparation, Site Utilities

Streetscape STS Landscape Lighting, Street Lighting, Street Signage, Streetscape Furniture,

Way finding Lighting, Way finding SignageTraffic Control TRF CCTV, Lane Control Systems, Vehicle Management System, Signage, PublicAddress



13/24

Discipline Code Application/Use

Utility Distribution UDT District Cooling, Gas, HV Electrical, Irrigation Water, LV Electrical, MVElectrical, Potable Distribution, Reservoirs, Sewage Treatment, Sewerage,Storage Tanks, Utility Comms



14/24

4.4 Numbering ConventionAll documents registered in Aconex are required to have a unique number assigned (i.e no duplicate numbers can beregistered).

The Aconex document number field is flexible and can support a variety of numbering conventions commonly

adopted on projects. The document number field supports text, numbers and characters permitted by MicrosoftWindows operating system.

Please consult with your Aconex representative for additional information or assistance on how to implement asuitable document numbering convention.

4.4.1 Numbering String

All documents produced on this project must be numbered in accordance with the number string defined below.Please refer to the relevant reference tables for codes applicable to the number string.

FIGURE 3- DOCUMENT NUMBER STRING

ProjectCode

- OrganisationCode

- Location - Discipline - Document - UniqueNumber

P051 PIL U1 ADM MOM 000x

See Table 4 See Table 10 See Table 7 See Table 8

4.4.2 Drawing, Calculations, Bar Bending Schedule Numbering

FIGURE 4 DRAWING NUMBER STRING

ProjectCode

- OrganisationCode

- Location - DetailedDoc Type

- Scope - Element - UniqueNumber

P05

1

PIL U1 C CO AB 001

See Table 4 SeeTable 10

See tablebelow

See tablebelow

See tablebelow



15/24

DetailedDocument Type Abrev Element (Structure Pieces) Abrev Scope (Sub Structure) Abrev

Calculations C Abutments AB Concrete outline CO

Drawing D Barriers & Curbs BR External Tendons ET

Method Statement M Expansion Joints & Bearings EB Longitudinal Tendons LT

Bar Bending B Footings FO Reinforcement RFGeneral G Pier Columns PR Transverse Tendons TT

Reports & Manuals R Piles PI Incremental Launching IL

Standard Details ST Vertical Tendon VT

Superstructure SP Precast Marine Footings PF

Temporary Works TW Travellers TV

Formwork FW Plan & Profile PP

Existing EX Cross Sections CS

Lighting LG Alignment Data AL

Stormwater/Drainage SW Pavement Markings & Signs PM

Future Utilities FU Cable Stay CT

General Notes GN Bridge Building Equipment BB

Pylon PY Structural Steel SS

Pier Segment PS Kinematics KN

Pier Caps PC Precast Units PU

Pier Table PT

Document & drawing numbers to be generated by originators and not auto numbering

4.4.3 File Types

Whilst native files are required for coordination at certain stages/phases of the project the agreed project documentdistribution format is PDF.

Where more than one file extension with the same document number is required, it must be registered as a new

document number with a file format acronym appended to the end of the document number string (refer to the belowfigure for a sample).

4.4.4 File Name Recognition

Files named and saved in local/network drives in accordance with the project document numbering convention areable to capitalize on the file name recognition feature in Aconex. The figure below provides examples of appropriatefile names and how the elements of the file name will be imported into Aconex as the document number and revision.

FIGURE 5 MULTIPLE FILE FORMAT & FILE NAME RECOGNITION EXAMPLE

File Format Examples of Computer file name Registered Number on Aconex Rev

PDF (Default) P051-TDI-U1-C-AB-CO -0001_B.pdf P051-TDI-U1-C-AB-CO -0001 B

AutoCADDWG

P051-TDI-U1-C-AB-CO -0001-DWG_B.dwg P051-TDI-U1-C-AB-CO -0001-DWG B

Word P051-TDI-U1-C-AB-CO -0001-DOC_B.doc P051-TDI-U1-C-AB-CO -0001-DOC B



16/24

Types & File Formats

The following tables detail the Document Types available for use on the project relevant to their organizations role onthe project. When registering a document, select most suitable type from the drop down list.

If a document type does not exist on Aconex and is required by your organisation, submit a request to the AconexClient.

TABLE 8 DOCUMENT TYPES

Document

Type

Code Suggested Documents TDI PIL AVJV SC CN

As BuiltDrawing

ASD Final As Built

Certificate CER For all certificates except payment

Bar BendingSchedule

BBS For Bar Bending Schedule

Bill of quantitiesBOQ Quantity and unit price listed for

materials and labour

Calculation CAL All calculations sheets

Contract CON For Contracts between any partiesrelevant to the project

Drawing DWG For all drawings except shop & As built

Form FRM Any Forms

Invoice INV For all Invoices

Manual MAN All operating and maintenance manuals

MethodStatement

MET All method statements

PaymentCertificates

PCT All Payment Certificates

Permits PER All project related permits

PlanPLN For all plans i.e. safety, ITP,

environmental.

Presentations PRS For all presentations

Procedure PRC For all procedures

ProgramPRG All project programmes, project

scheduling

Purchase Order LPO For all LPO

Report REP Reports including but not limited toDaily, Weekly, Flash, Monthly, PCG,

Cost reports, Test Report

Sketch SKH All sketch design documentation

Snag List SNG All Snag List

Statement STT All Statements

Shop Drawing SPD All working and shop drawings



17/24

4.5 Title ConventionThe Document Title is important and all team members must use coherent titles when registering documents. Thisfield is an important element in searching for and retrieval of historical information within the database. The followingare guidelines on good practice use of the title field:

DO make the title the same as the hardcopy

Titles should typically be very specific, e.g.Building A Ground Floor Reflected Ceiling Layout or Design TeamMeeting Minutes.

DONT duplicate document titles

DONT use vague titles like: Drawing 1, Drawing 2, Drawing 3 etc.

4.6 StatusThe following table details the document status available for use on the project relevant to their organizations role onthe project. When registering a document, select most suitable type from the drop down list.

If a document status does not exist on Aconex and is required by your organisation, submit a request to the AconexClient.

TABLE 9 DOCUMENT STATUS

Document Status Use/Explanation TDI PIL AVJV SC CN

Approved For documents which have been approved inaccordance with project approval procedures

Approved withcomments

For documents which have been approved inaccordance with project procedures. Thesehave been approved in principle with somecomments

As Built For As Built Documents

Cancelled For cancelled documents

Issued for Approval For documents to be issued for Approval

Issued forConstruction

For documents ready for construction stage.

Issued forInformation

For documents to be issued for informationonly

Issued for Review For documents requiring review by one ormore parties

Rejected For documents which have been reviewed inaccordance with project procedures and havebeen rejected

Reviewed For documents reviewed

Reviewed WithComments

For documents reviewed with comments

Revise andResubmit



18/24

4.7 Revision Convention

The document revision practices adopted on the project are detailed in the following table.

TABLE 10 - REVISION CONVENTION

Revision Convention ApplicableDocument Status

Revision Triggers

Numeric Approved 01, 02, 03, Numeric

Approved withcomments

01, 02, 03,

Numeric Rejected 01, 02, 03, Numeric Cancelled 01, 02, 03, Numeric For Approval 01, 02, 03, Numeric For Construction 01, 02, 03,

Numeric For Information01, 02, 03,

Numeric For Coordination 01, 02, 03,

Numeric For Review 01, 02, 03,

Alpha As-Built A, B, C

Other Document Field ValuesAll documents must be tagged with the appropriate metadata/information. This section details the metadata in use onthis project.

4.7.1 Attribute 1 [Location]The primary attributes applicable to this project are detailed in the following table.

TABLE 10 ATTRIBUTE 1 LOCATION

Primary Attribute Description Code

Connection Road Connection to existing roads on Abu Dhabi CR

Laydown Area Site Compound LA

Earthworks All Earthworks on site EW

Traffic Management Traffic Mgmt on existing roads TM

Project Wide Entire Project PW

Unit 1 - Substructure South Approach Substructure (A1 to P9) U1

Unit 1 - Superstructure South Approach Superstructure (A1 to P9) U1

Unit 2 - Substructure Cable Stayed Bridge Substructure (P9 to P12) U2

Unit 2 - Superstructure Cable Stayed Bridge Superstructure (P9 to P12) U2

Unit 3 - Substructure North Approach Substructure (P12 to P21) U3

Unit 3 - Superstructure North Approach Superstructure (P12 to P21) U3

Unit 1 - Approach South Approach Sub/Superstructure (A1 to P9) UA

Unit 3 Approach North Approach Sub/Superstructure (P12 to A21) UB

Units 1, 2, 3 Cable Stayed Bridge, South & North Approach UXUnit 2 Cable Stayed Bridge Cable Stayed Bridge Sub/Superstructure (P9 to P12) UM



19/24

4.7.2 Attribute 2

The secondary attributes applicable to this project are detailed in the following table.

TABLE 11 ATTRIBUTE 2 [TBD]

Secondary Attribute Description Code

TBC

4.7.3 Job Code

The Job Number values in use on the project are detailed in the following table.

TABLE 14 JOB CODE

Job Code Description Code

Hodariyat Bridge P051

4.7.4 Package Numbers

The Package Numbers applicable to this project are detailed in the following table

TABLE 15 PACKAGE NUMBER

Package Number Description

A01 All Govt. Authorities

C01 Bridge Construction

C02 Geotech Invest, Topo & Bathymetric Surveys

C03 Pre construction Works - Tunnel

C04 Construction of Bridge

C05 Temp. Power to Laydown Area

C06 Main Construction Works

D01 Design

D02 Environmental Impact Assessment

D03 Tunnel Access Feasibility Study

D04 Design & Construction Supervision

D05 Design Check

I01 Invoices for Finance Department (LPO)

O01 Security Services to HB Laydown Area

4.8 Document Distribution

4.8.1 Transmittal Reason for Issue

The applicable Reason for Issue for transmittals on the project are detailed in the following table.



20/24

TABLE 16 TRANSMITTAL REASON FOR ISSUE

Reason for Issue Definition of Use

Issued for Approval Issuing documents which require approval from authorised project participants

Issued for Information Documents which are to be used for information purposes.

Issued for Review Documents which require review by another project participant

Issued for Comment Documents issues for comments

5.0 PROJECT MAIL

This section details the specifications for the use of the Project Mail module on Aconex, for this project.

5.1 Project Mail Numbering ConventionAll Project Mail generated in Aconex is automatically assigned with the next available number associated with the

selected project mail type.

5.2 Project Mail TypeThe authorised Project Mail types which an Organisation may initiate are detailed in the following table. For additionalProject Mail types please seek approval from the Aconex Client.

TABLE 17 CONTRACTUAL MAIL

Project Mail Type Use TDI PIL AVJV SC CN

Letter For general informal communication betweenparticipants from different organizations.

Transmittal Cover sheet to notify when documents i.e.drawings are issued to organisations updating

their registers.

Claim For Time & Cost implications due to additionalwork, NOD, expense

Confirm VerbalInstruction

For confirmation on site verbal instructions.

Request ForInformation

For construction queries

Response to RFI For answer queries for information.

Inspection & TestingRequest

For inspection / testing requests

Inspection Record For all Inspection checklist & records

Meeting Minutes For all meeting minutes

Material ApprovalRequest

For material submittals

Non ConformanceReport

For all NCRs

Variation Order All variation to contract.

Site ModificationSheet

All site modification sheets

Employers Instruction To send Instruction from TDIC

Engineers Instruction To send site verbal advice



21/24

TABLE 18 GENERAL MAIL

Project Mail Type Use TDI PIL AVJV SC CN

Memorandum For general informal communication betweenproject participants within own organization.

Informal MailFor informal correspondence

Project InvitationTo Send Project Invitations



22/24

5.3 Project Mail AttributesThe following tables detail the attributes applicable to the project. All project mail must be tagged with the followingattributes, as appropriate to the project mail.

5.3.1 Attribute 1

The attribute 1 values in use on the project are detailed in the following table.

TABLE 19 - PROJECT MAIL ATTRIBUTE 1 (AREA)

Primary Attribute Description Code

Connection Road Connection to existing roads on Abu Dhabi CR

Laydown Area Site Compound LA

Earthworks All Earthworks on site EW

Traffic Management Traffic Mgmt on existing roads TM

Project Wide Entire Project PW

Unit 1 - Substructure South Approach Substructure (A1 to P9) U1

Unit 1 - Superstructure South Approach Superstructure (A1 to P9) U1

Unit 2 - Substructure Cable Stayed Bridge Substructure (P9 to P12) U2

Unit 2 - Superstructure Cable Stayed Bridge Superstructure (P9 to P12) U2

Unit 3 - Substructure North Approach Substructure (P12 to P21) U3

Unit 3 - Superstructure North Approach Superstructure (P12 to P21) U3

Approach for Unit 1 South Approach Sub/Superstructure (A1 to P9) UA

Approach for Unit 3 North Approach Sub/Superstructure (P12 to A21) UB

All Approaches & Units Cable Stayed Bridge, South & North Approach UX

Main Bridge Cable Stayed Bridge Sub/Superstructure (P9 to P12) UM

5.3.2 Attribute 2

The attribute 2 values in use on the project are detailed in the following table.

TABLE 21 - ATTRIBUTE 2 (DISCIPLINE)

Attribute 2 Description Code

Architectural ARCAuthorities & Government Departments AUT

Civil Works, Roads and bridges CIV

Commercial COM

Contracts Administration CTADesign & Master Planning DMP

Environment & Ecology ETE

Financial Management FNM

General ADM

Hard and Soft Landscape LAN

Health & Safety HSE

Legal LGL

Municipality Liaison MUN

Program Management PMG

QA/QC QAC

Site Management SMG



23/24

Attribute 2 Description Code

Streetscape STS

Traffic Control TRF

Utility Distribution UDT

5.4 Time Constrained Project MailProject mail which have time constraints (eg RFIs) can be managed by using response required and setting a duedate when creating project mail. It is recommended where time constraints apply the project team should define theapplicable types and agree on the timeframe to respond.

5.5 Subject Line ConventionsIt is vitally important that all team members use coherent titles when preparing Project Mail and Transmittals. TheSubject Line field is an important element in Searching for & Retrieval of historical information within the projectdatabase. Please avoid the following vague Subject Lines:

"Query"

"Re: Drawings"

"Clash" etc.

Please use meaningful subject lines to facilitate efficient Project Mail retrieval and reporting in Aconex.Example of subject line convention

Design Team Meeting Request

5.6 Project Mail ApprovalAconex allows organizations to implement mail approval to prevent unauthorized distribution of selected project mailtypes to other organizations. This feature allows the nominated approvers to view the mail before it is issued

externally.

Mail approval is configured by each organisation on the project. Please contact your Aconex Client OperationsRepresentative to assist with setting up this function.

5.7 Auto Mail PrefixAconex will automatically add an organisational prefix to each mail item created (see section 3.2 for a list of theparticipating organisations). This helps to distinguish correspondence from each organisation. This prefix ismanaged by each organisation administrator and must be setup by each organisation for this project.Additionally, each mail item has an additional code to indicate what the mail type is.

FIGURE 4 - MAIL USING ORG PREFIX OPTION

Organisation Prefix Mail type Unique number

TDI - MEMO - 000001

Refer to Table 4 Refer to Table 17 & 18

The Aconex system will automatically assign the unique number for each piece of mail that is created and sent.



24/24

5.8 Project Correspondence ProtocolThis table notes any special requests by an organisation of where specific mail should be addressed to in order forthem to be actioned appropriately.

FIGURE 5 - PROTOCOAL

Organisation Mail/Doc Type Users

TDIC Project related

(Financial)

TO

CC

Andrew Seymour

David Lewis

TDIC Project related

(Construction)

TO

CC

David Lewis

Andrew Seymour

TDIC Commercial TO

CC

CC

Paul Wilson

David Lewis

Andrew Seymour

Organisation Mail/Doc Type Users

PIL Project related

(Construction)

TO

CC

CC

Frederic Turlier

Eddie Scott

Victor Hamlig

PIL Commercial TO

CC

CC

Frederic Turlier

Paul Marsh

Christopher Round