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

TABLE OF CONTENTS
1.0 INTRODUCTION ...........................................................................................................3
1.1 Aconex 1.2 Getting Started with Aconex 1.3 Aconex System Terminology 2.1 Purpose 2.2 How to Use 2.3 Custodianship 3 3 4 5 5 5 6 7

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

3.0 PROJECT INFORMATION ...............................................................................................6 4.0 CONTROLLED DOCUMENTS..........................................................................................9

4.1 Required Document Fields 4.2 Optional Document Fields 4.3 Disciplines 4.4 Numbering Convention 4.5 Title Convention 4.6 Status 4.7 Revision Convention Other Document Field Values 4.8 Document Distribution 10 11 12 14 17 17 18 18 19 20 20 22 23 23 23 23 24 3.1 Project Details 3.2 The Project Team

5.0 PROJECT MAIL...........................................................................................................20

5.1 Project Mail Numbering Convention 5.2 Project Mail Type 5.3 Project Mail Attributes 5.4 Time Constrained Project Mail 5.5 Subject Line Conventions 5.6 Project Mail Approval 5.7 Auto Mail Prefix 5.8 Project Correspondence Protocol

CONFIDENTIALITY AND INTELLECTUAL PROPERTY STATEMENT The information contains confidential information and uses an Aconex proprietary template. This document must not be used or disclosed 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 Aconex and 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 Property Statement 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 legal@aconex.com

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

1.0 INTRODUCTION
1.1 1.2 Aconex Getting Started with Aconex
Aconex have been engaged on this Project by TDIC as the online collaboration system for this project.

To access Aconex, you require an internet connection, the latest internet browser installed on your computer and to enrol 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 implementation and 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 where downloading and uploading of large files is required. Broadband varies in download and upload speeds or bandwidth capacity. The optimal broadband bandwidth capacity for 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 your Organisations broadband capacity.

1.2.2

Internet Browser

Aconex recommends using the latest version of Internet Explorer or Mozilla Firefox as your internet browser. The latest internet browsers are available free to download from www.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 Process

The implementation process will be facilitated by Aconex. The process will require participation and input from key project 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 training please contact Aconex on 800 226639 (ACONEX) or submit details online at http://www.aconex.com/Contact/Contact-Us/Request-Training.html or email training-mea@aconex.com Aconex provides 24/7 helpdesk support for all members globally. A list of Global Helpdesk numbers and office locations can be found on www.aconex.com The following training courses are available to all users. Please note that, wherever possible, the sessions will be customised as per project/ group requirements. TABLE 1 - ACONEX TRAINING COURSES Course Name Basic Documents and Mail Course summary Designed for new users of Aconex. It covers fundamental aspects of the system including Aconex overview, general navigation project mail and document management within Aconex. This session covers the setup for a specific organisation of additional users, setting security levels and disabling users once they are no longer part of the project/ organisation Aimed at users who are required to upload, register, supersede and transmit multiple documents. Duration 2 hours

Organisation Administrator

1 hour

Multiple Document Upload

1.5 hours

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

Course Name Advanced Documents

Course summary Covers the use of more advanced features/ functionality within the Documents module. This session is often used in conjunction with the Multiple Document Upload session. Bulk processing enables mass uploading of documents and linking to the metadata information contained within an Excel spreadsheet. This is very useful where there is a large amount of historical documents to upload or where document numbers need to be reserved in the register for future document deliverables.

Duration 1 hour

Bulk Processing

1.5 hours

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

1.3

Aconex System Terminology

Aconex 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 LIST Terminology Aconex Client Controlled Document Document Register Key Contact Mandatory Field Organisation Org Admin Project Admin Aconex Project Protocols Project Mail Register Supersede Training Coordinator Transmittal Unregistered File Definition The Organisation that engaged the services of Aconex for the project. A document which is registered with multifaceted, searchable metadata and a complete document, transaction history. An electronic registry of all documents that have been registered by your Organisation or received by transmittal from other Organisations. The primary point of contact for Aconex staff throughout the project lifecycle. This may be the Aconex Client or an Organisation delegated as key contact by the Aconex Client. A field which requires completion. All fields which require completion and are marked with a red asterisk (*). A registered entity in Aconex who manages their own Organisation members and project information. An Aconex role which performs administrative functions for their Organisation such as creating and administrating new member accounts and Organisation security. An Aconex role which administrates and manages project wide settings and updates Aconex and associated documents with any procedural changes decided upon. A document created to provide a record of agreed system configuration, protocols and procedures associated with using Aconex on the project. The document will also be used to facilitate the implementation process. Project correspondence which contains searchable metadata to assist with retrieval and reporting of all communication between project participants. The process of uploading (onto Aconex) and tagging an electronic file with appropriate properties and categories according to pre-defined fields. The process of updating a previously registered document with the latest version and placing the previous version in the document history. The Training Coordinator is responsible for organising and scheduling training sessions for project participants, at either for their Organisation or for all participants on the project. Method of issuing documents from your Organisations document register to another Organisations document register. An electronic file uploaded into the document register (unregistered tab) but not tagged with metadata as yet.

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

2.0 ABOUT THIS DOCUMENT

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

2.2

How to Use

This document is specific to the Aconex collaboration system and shall be read in conjunction with but not limited to all 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 configurations have been defined for their organization. Existing and new project participants that wish to refer to project procedures that have been mapped to Aconex. Org Admins and Project Admins that are required to perform the initial configuration or make amendments to the project setup.

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

2.3

Custodianship

This document is a live document. It is expected that project information requirements will change over the course of the project lifecycle as the project and participants change. This document will be required to be updated to reflect changes to system settings, processes, project participants and procedures. The ongoing management of this document will reside with the nominated custodian who is Mia Merrigan from TDIC and 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.

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

3.0 PROJECT INFORMATION

3.1 Project Details
GG101 Hodariyat Bridge
GG101 Hodariyat Bridge 02 4036200 02 4061500 1 October 2009 28 March 2012 TABLE 3 - PROJECT DETAILS Project Name* Project Short Name* Phone Number Fax Number Project Start Date* Estimated Completion Date* Project Address City/Suburb* Postcode* Country* Project Description Abu Dhabi 126888 UAE Cable Stayed Bridge from Abu Dhabi Island to Hodariyat Island

(*) Mandatory field required for project setup.

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

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

Client (TDIC)

Consultants

Engineer (Parsons)

Main Contractor (AVJ)

Sub-Contractor

Sub-Contractor

Sub-Contractor

General Project Communications/ Mail

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

3.2.2

Project Key Contacts

The following table lists the contact details of the key contacts for each organization and the relevant Aconex project information. 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 Organization Name Mia Merrigan David (Dai) Lewis Paul Wilson Amro Rafee Training Coordinator Bruno Thierry Project Director Role Project Administrator SR Project Manager Commercial Manager Account Manager Contact Details 02 4061672 056 105758 8 02 403651 6 050 3961207 050 272955 1 04 4287474 050 4531097 Org Prefix TDI TDI TDI ACX ACX AVJ IBT TGP Frederic Turlier Resident Engineer 050 817608 7 PIL-P051 Aconex Project Information Project Role CL CL CL CN CN MC CN CN LC AC KC PA TC OA

TDIC TDIC TDIC Aconex Aconex OVERSEAS AST / VSL MIDDLE EAST JV TBC TBC PARSONS INTERNATIONAL LIMITED

Code CL LC CN HC SC

Project Role Client Lead Consultant Consultant Head Contractor Subcontractor

Code AC KC PA TC OA

Aconex Role Aconex Client Key Contact Project Admin Training Coordinator Org Admin

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

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 the project. 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 with mandatory fields (denoted by red asterisks). FIGURE 2 SAMPLE PROJECT DOCUMENT REGISTRATION FORM

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

4.1

Required Document Fields

The 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 Document No*# Revision*# Title Type*# Status*# Discipline Revision Date Date Uploaded*#+ Attribute 1 Field Type Document Number Text Text List (Single Select) List (Single Select) List (Single Select) Date Date List (Multi Select) List (Multi Select) Description of Use/Application For tagging a document with the unique number required by the applicable document numbering convention. For tagging a document with a revision reference (applicable project convention) when it is updated. For tagging a document with the applicable title description associated with the document. For tagging a document to classify it with an appropriate document type. For tagging a document with the appropriate status reference that is relevant to the document lifecycle. For tagging a document with an appropriate discipline classification. For tagging a document with a date when the revision was created. System defined field. Date of when file was uploaded. For tagging a document with one or more values of information to assist with categorization. Example Zones within the project. For tagging a document with one or more values of information to assist with categorization Table 10 Table 14 Table 8 Table 9 Table 7 Table/Figure Reference Figure 3 Search Field Y Y Y Y Y Y Y Y Y Y

Job Code

For additional fields to tag your documents please discuss with your Project Administrator or Aconex Client Operations 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.

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

10

4.2

Optional Document Fields

The 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 Confidential# File# Print Size# Reference Date Created Author Comments Package Number Field Type Confidentiality Check Box File Text Text Date Text Text Area List (Multi Select) Description of Use/Application For defining who can have exclusive access to the registered document. For attaching the electronic file relevant to the registered document. For detailing the print size requirements to assist users when printing the document. For tagging a document with specific reference information relating to the document. For tagging a document with a date when it was first created. For tagging a document with details of the author. For entering comments relevant to the document. For tagging a document with one or more values of information. Example Package Numbers within the project (subcontractors) Table 15 Table/Figure Reference Search Field N N N Y N Y N 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.

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

11

4.3

Disciplines

The 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 DISCIPLINES Discipline Architectural Authorities & Government Departments Code ARC AUT Application/Use Ceiling Details, Door Schedule, Elevation, Floor Details, Floor Layouts, Reflected Ceiling Plans, Sections, Site Plans, Toilet Details, Wall Details Abu Dhabi Terminals, ADDC, ADNEC, ADNOC, ADSSC, ADWEA, Al Ain Wildlife, Building Directorate, Chamber of Commerce, Civil Aviation, Crown Prince, Cultural Foundation, Department of Social Services & Commercial Building, EAD, EMPOST, Environmental Agency, ETISALAT, Executive Affairs Authority, Executive Council, Finance Department, GASCO, General Authority for Health Services, License & Traffic Directorate, Military/Armed Forces, Ministry of Economy Under Secretary Office, Ministry of Transport, Petroleum Port Authority,Police Department, Port Authority, Presidential, TEBODIN, Town Planning Department, TRANSCO 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. Contracts, Variations, Notice of Claim, Variation Orders. Contracts, Variations. Concept Design, Design Workshops, Development Study, Master Planning, Planning Design Regulations, Satellite Imagery, Tender Presentations, Topographic Mapping Services, Urban Design Review, Urban Planning Archaeological Studies, Chemical Analysis of Soils, Construction Environmental Management Plan, Ecological Surveys, Environmental Impact Assessments, Marine Studies, Traffic Impact Studies Advance Payment Guarantee, Approved Variations, Control Budget, Employers Instructions, Estimates, Financial Reports, Performance Bond, Proposals/Claims, Valuations, Payment Certs. Meetings, Monthly Reports, Photography, Site Photographs, Transportation, Travel, Weekly Reports Irrigation, Parking Lots, Pedestrian Paving, Precincts, Roadways, Trees & Plants Health, Safety Claims, Contract Drafting, Insurance Certificate Abu Dhabi Municipality, Building Permits, Land Department, Park & Agriculture Section, Permits & Permissions, Roads Department, Saadiyat Municipality Master Schedule, Progress Reports, Project Management Plan, Scheduling, Technical Program 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 of Commencement, 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 Demobilization, Hazardous Waste Remediation, Labour Camps, Mobilization, Security Services, Service Tunnels, Site Administration, Site Clearing, Site Demolition, Site Earthworks, Site Electrical Items, Site Offices & Facilities, Site Preparation, Site Utilities Landscape Lighting, Street Lighting, Street Signage, Streetscape Furniture, Way finding Lighting, Way finding Signage CCTV, Lane Control Systems, Vehicle Management System, Signage, Public Address

Civil Works, Roads and bridges

CIV

Commercial Contracts Administration Design & Master Planning

COM CTA DMP

Environment & Ecology

ETE

Financial Management General Hard and Soft Landscape Health & Safety Legal Municipality Liaison Program Management QA/QC

FNM GEN LAN HSE LGL MUN PMG QAC

Site Management

SMG

Streetscape Traffic Control

STS TRF

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

12

Discipline Utility Distribution

Code UDT

Application/Use District Cooling, Gas, HV Electrical, Irrigation Water, LV Electrical, MV Electrical, Potable Distribution, Reservoirs, Sewage Treatment, Sewerage, Storage Tanks, Utility Comms

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

13

4.4

Numbering Convention

All documents registered in Aconex are required to have a unique number assigned (i.e no duplicate numbers can be registered). 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 Microsoft Windows operating system. Please consult with your Aconex representative for additional information or assistance on how to implement a suitable 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 Project Code Organisation Code Location Discipline Document Unique Number

P051

PIL
See Table 4

U1
See Table 10

ADM
See Table 7

MOM
See Table 8

000x

4.4.2
Project Code -

Drawing, Calculations, Bar Bending Schedule Numbering

Organisation Code Location Detailed Doc Type Scope Element Unique Number

FIGURE 4 DRAWING NUMBER STRING

P05 1

PIL
See Table 4

U1
See Table 10

C
See table below

CO
See table below

AB
See table below

001

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

14

Detailed Document Type Calculations Drawing Method Statement Bar Bending General Reports & Manuals

Abrev C D M B G R

Element (Structure Pieces) Abutments Barriers & Curbs Expansion Joints & Bearings Footings Pier Columns Piles Standard Details Superstructure Temporary Works Formwork Existing Lighting Stormwater/Drainage Future Utilities General Notes Pylon Pier Segment Pier Caps Pier Table

Abrev AB BR EB FO PR PI ST SP TW FW EX LG SW FU GN PY PS PC PT

Scope (Sub Structure) Concrete outline External Tendons Longitudinal Tendons Reinforcement Transverse Tendons Incremental Launching Vertical Tendon Precast Marine Footings Travellers Plan & Profile Cross Sections Alignment Data Pavement Markings & Signs Cable Stay Bridge Building Equipment Structural Steel Kinematics Precast Units

Abrev CO ET LT RF TT IL VT PF TV PP CS AL PM CT BB SS KN PU

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 document distribution 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 below figure 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 are able to capitalize on the file name recognition feature in Aconex. The figure below provides examples of appropriate file 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 PDF (Default) AutoCAD DWG Word Examples of Computer file name P051-TDI-U1-C-AB-CO -0001_B.pdf P051-TDI-U1-C-AB-CO -0001-DWG_B.dwg P051-TDI-U1-C-AB-CO -0001-DOC_B.doc Registered Number on Aconex P051-TDI-U1-C-AB-CO -0001 P051-TDI-U1-C-AB-CO -0001-DWG P051-TDI-U1-C-AB-CO -0001-DOC Rev B B B

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

15

Types & File Formats

The following tables detail the Document Types available for use on the project relevant to their organizations role on the 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 Aconex Client. TABLE 8 DOCUMENT TYPES Document Type As Built Drawing Certificate Bar Bending Schedule Bill of quantities Calculation Contract Drawing Form Invoice Manual Method Statement Payment Certificates Permits Plan Presentations Procedure Program Purchase Order Report Code ASD CER BBS BOQ CAL CON DWG FRM INV MAN MET PCT PER PLN PRS PRC PRG LPO REP Suggested Documents Final As Built For all certificates except payment For Bar Bending Schedule Quantity and unit price listed for materials and labour All calculations sheets For Contracts between any parties relevant to the project For all drawings except shop & As built Any Forms For all Invoices All operating and maintenance manuals All method statements All Payment Certificates All project related permits For all plans i.e. safety, ITP, environmental. For all presentations For all procedures All project programmes, project scheduling For all LPO Reports including but not limited to Daily, Weekly, Flash, Monthly, PCG, Cost reports, Test Report All sketch design documentation All Snag List All Statements All working and shop drawings TDI PIL AVJV SC CN

Sketch Snag List Statement Shop Drawing

SKH SNG STT SPD

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

16

4.5

Title Convention

The Document Title is important and all team members must use coherent titles when registering documents. This field is an important element in searching for and retrieval of historical information within the database. The following are 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 Team Meeting Minutes. DONT duplicate document titles DONT use vague titles like: Drawing 1, Drawing 2, Drawing 3 etc.

4.6

Status

The following table details the document status available for use on the project relevant to their organizations role on the 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 Aconex Client. TABLE 9 DOCUMENT STATUS Document Status Approved Approved with comments Use/Explanation For documents which have been approved in accordance with project approval procedures For documents which have been approved in accordance with project procedures. These have been approved in principle with some comments For As Built Documents For cancelled documents For documents to be issued for Approval For documents ready for construction stage. For documents to be issued for information only For documents requiring review by one or more parties For documents which have been reviewed in accordance with project procedures and have been rejected For documents reviewed For documents reviewed with comments TDI PIL AVJV SC CN

As Built Cancelled Issued for Approval Issued for Construction Issued for Information Issued for Review Rejected

Reviewed Reviewed With Comments Revise and Resubmit

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

17

4.7

Revision Convention

The document revision practices adopted on the project are detailed in the following table. TABLE 10 - REVISION CONVENTION Revision Convention Numeric Numeric Numeric Numeric Numeric Numeric Numeric Numeric Numeric Alpha Applicable Document Status Approved Approved with comments Rejected Cancelled For Approval For Construction For Information For Coordination For Review As-Built Revision Triggers 01, 02, 03, 01, 02, 03, 01, 02, 03, 01, 02, 03, 01, 02, 03, 01, 02, 03, 01, 02, 03, 01, 02, 03, 01, 02, 03, A, B, C

Other Document Field Values

All documents must be tagged with the appropriate metadata/information. This section details the metadata in use on this 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 Connection Road Laydown Area Earthworks Traffic Management Project Wide Unit 1 - Substructure Unit 1 - Superstructure Unit 2 - Substructure Unit 2 - Superstructure Unit 3 - Substructure Unit 3 - Superstructure Unit 1 - Approach Unit 3 Approach Units 1, 2, 3 Unit 2 Cable Stayed Bridge Description Connection to existing roads on Abu Dhabi Site Compound All Earthworks on site Traffic Mgmt on existing roads Entire Project South Approach Substructure (A1 to P9) South Approach Superstructure (A1 to P9) Cable Stayed Bridge Substructure (P9 to P12) Cable Stayed Bridge Superstructure (P9 to P12) North Approach Substructure (P12 to P21) North Approach Superstructure (P12 to P21) South Approach Sub/Superstructure (A1 to P9) North Approach Sub/Superstructure (P12 to A21) Cable Stayed Bridge, South & North Approach Cable Stayed Bridge Sub/Superstructure (P9 to P12) Code CR LA EW TM PW U1 U1 U2 U2 U3 U3 UA UB UX UM

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

18

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 TBC Code

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 Hodariyat Bridge Code 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 A01 C01 C02 C03 C04 C05 C06 D01 D02 D03 D04 D05 I01 O01 Description All Govt. Authorities Bridge Construction Geotech Invest, Topo & Bathymetric Surveys Pre construction Works - Tunnel Construction of Bridge Temp. Power to Laydown Area Main Construction Works Design Environmental Impact Assessment Tunnel Access Feasibility Study Design & Construction Supervision Design Check Invoices for Finance Department (LPO) 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.

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

19

TABLE 16 TRANSMITTAL REASON FOR ISSUE Reason for Issue Issued for Approval Issued for Information Issued for Review Issued for Comment Definition of Use Issuing documents which require approval from authorised project participants Documents which are to be used for information purposes. Documents which require review by another project participant 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 Convention

All Project Mail generated in Aconex is automatically assigned with the next available number associated with the selected project mail type.

5.2

Project Mail Type

The authorised Project Mail types which an Organisation may initiate are detailed in the following table. For additional Project Mail types please seek approval from the Aconex Client. TABLE 17 CONTRACTUAL MAIL Project Mail Type Letter Transmittal Use For general informal communication between participants from different organizations. Cover sheet to notify when documents i.e. drawings are issued to organisations updating their registers. For Time & Cost implications due to additional work, NOD, expense For confirmation on site verbal instructions. For construction queries For answer queries for information. For inspection / testing requests For all Inspection checklist & records For all meeting minutes For material submittals For all NCRs All variation to contract. All site modification sheets To send Instruction from TDIC To send site verbal advice TDI PIL AVJV SC CN

Claim Confirm Verbal Instruction Request For Information Response to RFI Inspection & Testing Request Inspection Record Meeting Minutes Material Approval Request Non Conformance Report Variation Order Site Modification Sheet Employers Instruction Engineers Instruction

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

20

TABLE 18 GENERAL MAIL Project Mail Type Memorandum Informal Mail Project Invitation Use For general informal communication between project participants within own organization. For informal correspondence To Send Project Invitations TDI PIL AVJV SC CN

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

21

5.3

Project Mail Attributes

The following tables detail the attributes applicable to the project. All project mail must be tagged with the following attributes, 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 Connection Road Laydown Area Earthworks Traffic Management Project Wide Unit 1 - Substructure Unit 1 - Superstructure Unit 2 - Substructure Unit 2 - Superstructure Unit 3 - Substructure Unit 3 - Superstructure Approach for Unit 1 Approach for Unit 3 All Approaches & Units Main Bridge Description Connection to existing roads on Abu Dhabi Site Compound All Earthworks on site Traffic Mgmt on existing roads Entire Project South Approach Substructure (A1 to P9) South Approach Superstructure (A1 to P9) Cable Stayed Bridge Substructure (P9 to P12) Cable Stayed Bridge Superstructure (P9 to P12) North Approach Substructure (P12 to P21) North Approach Superstructure (P12 to P21) South Approach Sub/Superstructure (A1 to P9) North Approach Sub/Superstructure (P12 to A21) Cable Stayed Bridge, South & North Approach Cable Stayed Bridge Sub/Superstructure (P9 to P12) Code CR LA EW TM PW U1 U1 U2 U2 U3 U3 UA UB UX 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 Architectural Authorities & Government Departments Civil Works, Roads and bridges Commercial Contracts Administration Design & Master Planning Environment & Ecology Financial Management General Hard and Soft Landscape Health & Safety Legal Municipality Liaison Program Management QA/QC Site Management Code ARC AUT CIV COM CTA DMP ETE FNM ADM LAN HSE LGL MUN PMG QAC SMG

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

22

Attribute 2 Description Streetscape Traffic Control Utility Distribution

Code STS TRF UDT

5.4

Time Constrained Project Mail

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

5.5

Subject Line Conventions

It is vitally important that all team members use coherent titles when preparing Project Mail and Transmittals. The Subject Line field is an important element in Searching for & Retrieval of historical information within the project database. 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 Approval

Aconex allows organizations to implement mail approval to prevent unauthorized distribution of selected project mail types 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 Operations Representative to assist with setting up this function.

5.7

Auto Mail Prefix

Aconex will automatically add an organisational prefix to each mail item created (see section 3.2 for a list of the participating organisations). This helps to distinguish correspondence from each organisation. This prefix is managed 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
Refer to Table 4

MEMO
Refer to Table 17 & 18

000001

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

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

23

5.8

Project Correspondence Protocol

This table notes any special requests by an organisation of where specific mail should be addressed to in order for them to be actioned appropriately. FIGURE 5 - PROTOCOAL Organisation TDIC TDIC TDIC Mail/Doc Type Project related (Financial) Project related (Construction) Commercial TO CC TO CC TO CC CC Users Andrew Seymour David Lewis David Lewis Andrew Seymour Paul Wilson David Lewis Andrew Seymour

Organisation PIL

Mail/Doc Type Project related (Construction) Commercial TO CC CC TO CC CC

Users Frederic Turlier Eddie Scott Victor Hamlig Frederic Turlier Paul Marsh Christopher Round

PIL

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

24