0% found this document useful (0 votes)
233 views

Quarza Project Configuration (00) - Commented

The document details the configuration of the project management system for a mixed use development project. It includes information on document types, statuses, workflows and communication. Core fields for documents are defined along with project specific fields to classify documents.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
233 views

Quarza Project Configuration (00) - Commented

The document details the configuration of the project management system for a mixed use development project. It includes information on document types, statuses, workflows and communication. Core fields for documents are defined along with project specific fields to classify documents.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 16

Quarza Residence

Project Configuration
QUA-XXX-00-MAN-0001
Table of Contents
Title:

Project Configuration

Revision:

00

Document Number:

Revision Date:

01 Jul 2016

Project Name:

Status:

Draft

Aconex 2016

Project Configuration
1. Project Information..................................................................................................................... 3
1.1

Project Details..........................................................................................................................................................3

1.2

Project Key Contacts................................................................................................................................................4

2. High Level Communication Diagram (Design Phase).............................................................5


3. Document Module Configuration.............................................................................................. 6
3.1

Core Document Register Fields...............................................................................................................................6

3.2

Pinewood Iskandar Media Hub Specific Document Fields......................................................................................7

3.3

Document Types.......................................................................................................................................................8

3.4

Document Status....................................................................................................................................................11

3.5

Discipline................................................................................................................................................................12

3.6

Stage......................................................................................................................................................................13

3.7

Transmittals Reason for Issue.............................................................................................................................13

4. Workflow Module...................................................................................................................... 13
5. Mail Module Configuration....................................................................................................... 14
5.1

Mail Types...............................................................................................................................................................14

5.2

Mail Attribute 1 (Phases/ Building Zone)................................................................................................................15

6. Project Preferences.................................................................................................................. 16

CONFIDENTIALITY AND INTELLECTUAL PROPERTY STATEMENT


This document 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 [email protected].

Related Documents
This document must be read in conjunction with, but not limited to, other project specific manuals, plans
or procedures that are applicable to this project. The table below lists the relevant documents.
Document Reference

Title

Author

XXX-YYY-00-MAN-0002

Information Management Policy

Client & Aconex

Custodianship
The ongoing management of this document will reside with the nominated custodian who is Enter
Custodian Name from Client Organisation and will be supported by the Aconex Client Operations team. All
amendments must be submitted to the nominated custodian.

XXX-YYY-00-MAN-0001 Rev.00 Draft

Aconex 2016

Project Configuration

1. Project Information
In this section there are details about the Background of the project.

1.1

Project Details
Client Organisation*
Project Name*
Project Short Name* (max 20
characters)
Project Code* (max 8
characters)
Project Director*
Email*
Key Implementation Contact*
Email*
Phone Number*
Project Start Date*
Estimated Completion Date*
Project Type*
Project Address
Project Address 1*
City/Suburb*
Postcode*
Country*
Phone Number*
Fax Number
Project Description*

XXX-YYY-00-MAN-0001 Rev.00 Draft

Quarza Residence
Quarza Residence @ Melawati
QUA

John Ngi
[email protected]
+6012 2249 765
01/07/2016
31/12/2018
Mixed Use Development
KL East, Setapak
Kuala Lumpur
Malaysia

Mixed Development consisting of:


2 units of 38-storey towers with 508 units serviced
Apartments
6-storey Podium Retail Mall.

Aconex 2016

Project Configuration

1.2

Project Key Contacts


*note: key contact from each organization should inform Custodian Name from Pinewood Iskandar
Malaysia and Aconex for user request as well as removal
Key Contact Information
Organisation

Prefix*

Contact Name

Email

Contact Details

Role

Sime Darby Melawati

SDM

CL

Crest Builder

CBH

John Ngi

[email protected]

MC

Turner International
Malaysia

TIM

Doug Diercksen

[email protected]

PM

SA Architects

SAA

Siti Yusrin

Arup Jururunding

ARP

PCR Sdn Bhd

PCR

Azmizi Mukhlis

B & C Jurukur Bahan

BNC

Abdul Aziz Hilmy

QS

Geoffrey Thomas
Associates

GTA

Geoffrey Thomas

CN

PTA Design

PTA

CN

Integrated
GeoPlanning

IGP

CN

Aconex

ACX

LC
CN

Ong Tan Ling


Hajrah Ibrahim

[email protected]

[email protected]

CN

+603-9236 7401

CN

*Used in mail and document numbering.


Code

Role

CL

Client

PM

Project Manager

LC

Lead Consultant

CN

Consultant

QS

Quantity Surveyor

MC

Main Contractor

NSC

Nominated Subcontractor

XXX-YYY-00-MAN-0001 Rev.00 Draft

Aconex 2016

Project Configuration

1. High Level Communication Diagram


The expected flow of communication on the project is detailed in the figure below:

Client
Sime Darby Melawati

Contractors

XXX-YYY-00-MAN-0001 Rev.00 Draft

Quantity Surveyor
B&C

Consultants

Aconex 2016

Project Configuration

2. Document Module Configuration


This section details the document register configuration and information associated with managing the
documents within the documents register on Aconex.

2.1

Core Document Register Fields

The following table details the standard document register fields recommended by Aconex.
Label

Require
d

Type

Description of use

Text

For tagging a document with the unique number required by


the applicable document numbering convention.

Yes

For tagging a document with a revision reference (applicable


project convention) when it is updated.

Yes

For tagging a document with the applicable title description


associated with the document.

Yes

For tagging a document to classify it with an appropriate


document type.

Yes

Section
2.3

For tagging a document with the appropriate status reference


that is relevant to the document lifecycle.

Yes

Section
2.4

(50 chars)

For tagging a document with an appropriate discipline


classification.

Yes

Section
2.5

Date

For tagging a document with a date when the revision was


created.

Yes

For tagging a document with details of the author or originator.


By default, the organization name is entered.

Yes

(1024 chars)

For entering comments relevant to the document to assist in


searching and retrieval (e.g. changes between revisions).

No

Confidential

Check Box

For defining who can have exclusive access to the registered


document.

No

File

File

For attaching the electronic file relevant to the registered


document.

No

(15 chars)

For detailing the print size requirements to assist external print


shops when printing the document.

No

Date Modified

Date

System controlled field. The date when the document changes


via uploading or on receipt of a transmittal.

n/a

System
Controlled

Review Status

n/a

Displays the review outcome for a document (e.g. workflow


review outcome).

n/a

System
Controlled

Review Source

n/a

Displays the source of the review outcome (e.g. workflow).

n/a

System
Controlled

Document No
Revision
Title
Type
Status
Discipline
Revision Date
Created By
Comments

Print Size

(50 chars)

Text
(15 chars)

Text
(255 chars)

List, single
(50 chars)

List, single
(40 chars)

List, single

Text
(60 chars)

Text Area

Text

XXX-YYY-00-MAN-0001 Rev.00 Draft

Aconex 2016

Note

Project Configuration

2.2

Quarza Residence Specific Document Fields

The following table lists additional document register fields that have been included to suit the specific
information management requirements of this project.
Label
Stage
Building Zone
Submission
Stages

Description of use

List, single

For tagging a document with one or more values of


information to assist with categorization.

Yes

For tagging a document with one or more values of


information to assist with categorization.

Yes

For tagging a document with one or more values of


information to assist with categorization.

No

(50 chars)

List, single
(50 chars)

List, multi
(60 chars)

Text
(120 chars)

For tagging a document with specific reference information


(e.g. an internal organization or system reference).

Scale

Text

For tagging a document with its scale (e.g. drawing scale)

Percent Complete

Text
(60 chars)

For tagging a document with its completion percentage (e.g.


100% DD)

Reference

Require
d

Type

XXX-YYY-00-MAN-0001 Rev.00 Draft

Aconex 2016

Note

No
No
No

Project Configuration

2.3

Document Types

The following table indicates the document types available for use on the project. An X indicates that the
project role has been configured with the ability to create that document type in the register.
Type

Code*

Description of use

CL

PM

L
C

QS

CN

MC

NS
C

AGD

All meeting and programme


agendas

Contract Docs

CON

For all registration and


distribution of all agreements
including confidentiality /
consultancy & contract
agreements, Agreed Variation
Order, Memorandum of
Understanding (MOU), Letter of
Award/Acceptance (LOA), Letter
of Intent (LOI)

Bill of Quantities

BOQ

Quantity and unit price listed for


materials and labour

Bond

BND

For performance bonds, tender


bonds, guarantee bond,
insurance, warranty, etc.

Brief

BRF

All project briefing documents

Calculation

CAL

For all registration and


distribution of all Design
Calculations, Data Sheet

Catalogue

CAT

For the registration of company


catalogues, brochures, marketing
materials, advertisements etc.

Certificate

CRT

For all design certificates,


handover or taking-over
certificates including Defect &
Liabilities

Data Sheet

DST

For all material / product data


sheets

Delivery Note

DNO

For all delivery notes of any items


received

Drawing

DWG

Drawings including floor, site and


roof plans, elevations, sections,
details and layouts.

Estimate

EST

For registration of all estimates

Inspection & Test


Plan

ITP

For issuing Inspect and Test Plan


for review

Invoice

INV

For the registration and


distribution for all invoices

List

LST

Our
terms in and
PQP - Materials/Fittings
For the
registration
submission=MFSS
distributionSample
of lists e.g.,
Table of
X
X
Contents, Attendance
Sheets/Records etc.

Manual

MAN

Manuals including O&M manuals


for plant and equipment, project
procedures manual.

Material
Submittal

MTS

To be used for all Material sample


submittal & approval

Agenda

XXX-YYY-00-MAN-0001 Rev.00 Draft

Aconex 2016

X
X

X
X

X
8

Project Configuration

Meeting Minutes

Method
Statement

Material/Work
Testing Results

MOM

For all Minutes of Meetings


including their associated
agendas.

MST

For the registration and


distribution of all method
statements

MWT
R

Our terms in PQP Work Method


Statement=WMS
X

To submit any material testing


results i.e cube test, Tensile

Organisation
Charts

ORG

To be used for all org charts

Payment
Certificate

PAY

To be used for all payment


certificates

Permit

PER

To be used for all permits


associated to the projects

Photographs,
Images and
Videos

IMG

To be used for all photographs,


images, & videos, etc

Policy

PLY

For all project-related and


relevant external or third party
policies and guidelines.

Pre-qualification

PRQ

To be used for all pre-qualification


documents

Presentation

PRN

To be used for all Presentations

Proposal

PPS

For all proposals

Report

RPT

example: progress reports, month


end reports, accident/incident or
investigation report

Request for
Proposal

RFP

For the registration and


distribution of all RFPs

Schedule

SCH

For all project planning schedules

Shop Drawing

SHD

All shop drawings produced by


the subcontractors and Main
Contractor.

Specification

SPC

All specifications including


hardware, equipment and design
specifications.

Variation Order

VOR

For registering all Variation


Orders

Warranty

WRT

For registering all Warranty and


Guarantees

Our terms in PQP Shop


For the registration and
Drawing=DS
distribution of ALL Reports; AsBuilt=DA

*Used in document numbering (see Information Management Policy document).


Code

Role

CL

Client

PM

Project Manager

LC

Lead Consultant

QS

Quantity Surveyor

CN

Consultant

MC

Main Contractor

XXX-YYY-00-MAN-0001 Rev.00 Draft

Aconex 2016

Project Configuration

NSC

Nominated Subcontractor

XXX-YYY-00-MAN-0001 Rev.00 Draft

Aconex 2016

10

Project Configuration

2.4

Document Status

The following table indicates document statuses available for use on the project. An X indicates that the
project role has been configured with the ability to create or update a document with that status.
LC

QS

CN

MC

NS
C

For documents which reflect as-constructed or


as-built information

Final

Documents that are deemed to be final and do


not necessarily require review (e.g. not drawings).

For Construction

For documents which are for construction


purposes

For Co-ordination

Documents that a required for coordination


purposes.

For Design

For all design documentation.

For Handover

For documents that are required for handover


and/or O&M purposes.

Information Only

For documents to be issued for information only

Not Started

Documents that have not yet been started or are


being prepared (e.g. placeholder documents).

Preliminary

For documents to be issued for initial review or


that are currently in progress.

Status

Description of use

As-Built

CL

PM

Use the following values if workflows are NOT being used otherwise delete them and use Section
2 instead.

2.5

Issued for Approval/


Review

Indicates that a document is currently awaiting review.


ONLY if workflows are not being used.

Approved

Indicates that a document has been approved. ONLY if


workflows are not being used.

Approved with
Comments

The document has been approved and comments


added. ONLY if workflows are not being used.

Revise and
Resubmit

The document requires resubmission after being


reviewed. ONLY if workflows are not being used.

Rejected

The document has been rejected. ONLY if workflows are


not being used.

Code

Role

CL

Client

PM

Project Manager

LC

Lead Consultant

QS

Quantity Surveyor

CN

Consultant

MC

Main Contractor

NSC

Nominated Subcontractor

Discipline

The project disciplines used on this project are detailed in the following table.
XXX-YYY-00-MAN-0001 Rev.00 Draft

Aconex 2016

11

Project Configuration

Discipline

Code
*

Description of use

00 - Non Specific

00

For all non-discipline specific documentation

Architectural

AR

For all Architectural design documentation including but not limited to


sketches, reports, drawings, specifications, plans and schedules.

Civil & Structural

CS

For all Civil design documentation including but not limited to sketches,
reports, drawings, specifications, plans and schedules.

Mechanical &
Electrical

ME

For all Mechanical and Electrical design documentation including but not
limited to sketches, reports, drawings, specifications, plans and schedules.

Quantity Survey

QS

For all documentation associated with Cost Control including but not limited to
reports, recommendations, schedules and BOQs.

Environmental,
Health & Safety

HS

For all Health & Safety documentation including but not limited to reports,
notices, lists, plans, forms and schedules.

Interior Design

ID

For all Interior Design documentation

Land Survey

SV

For all Land Survey design documentation including but not limited to
sketches, reports, drawings, specifications, plans and schedules.

Landscape

LS

For all Landscape design documentation including but not limited to sketches,
reports, drawings, specifications, plans and schedules.

Other

OT

For all other Specialist Process & design documentation including but not
limited to sketches, reports, drawings, specifications, plans, schedules,
manuals, datasheets & calculations.

Project Management

PM

For all Project Management documentation including but not limited to reports,
plans, forms, procedures, schedules and instructions.

Quality Assurance

QA

For all Quality Assurance and Control documentation including but not limited
to manuals, procedures, forms, notices and reports.

Signage &
Wayfinding

SG

For all Signage & Wayfinding process and documentation but not limited to
sketches, reports, drawings, specifications, plans, schedules, manuals,
datasheets & calculations.

Traffic

TR

For all Traffic design documentation including but not limited to sketches,
reports, drawings, specifications, plans and schedules.

Vertical
Transportation

VT

For all Vertical Transportation design documentation including but not limited
to sketches, reports, drawings, specifications, plans and schedules.

*System requirement used in document numbering (see Information Management Policy document).

XXX-YYY-00-MAN-0001 Rev.00 Draft

Aconex 2016

12

Project Configuration

2.6

Stage (optional)

The project configured values are detailed in the following table.


Code

2.7

Value
00

00 - Non Specific

CD

01 - Concept Design

SD

02 - Schematic Design

DD

03 - Design Development

TD

05 - Tender Documentation

CT

04 - Contract Documentation

CN

06 - Construction Documentation

AB

07 - As Built

Transmittals Reason for Issue

The table below indicates the reasons for issue used on this project.
Reason

Role

Issued for Approval

Issuing documents that require approval from authorized project participants

Issued for Construction

Documents that are to be used for construction purposes

Issued for Information

Documents that are to be used for information purposes.

Issued for Review

Documents that require review by another project participant

Issued for Tender

Documents that are to be used for tendering purposes

3. Workflow Module
The following table details the review outcomes (Review Status) being used in workflows for this project.
Review Status

Description of use

Status*

For documents that are currently being reviewed in accordance with


project procedures.

Not Reviewed

Approved

For documents that have been reviewed in accordance with project review
procedures and have been approved.

Reviewed

Approved with
Comments

For documents that have been reviewed in accordance with project


procedures. These have been approved in principle with some comments.

Reviewed

Reject & Resubmit

For documents that have been reviewed in accordance with project


procedures and have been rejected and require resubmission with
comments

Reviewed

No Comments

For documents that have been reviewed in accordance with project review
procedures without comment.

Reviewed

In Progress Label
Pending
Review Outcomes

*Indicates how the Document Status will be changed by the workflow.

XXX-YYY-00-MAN-0001 Rev.00 Draft

Aconex 2016

13

Project Configuration

4. Mail Module Configuration


This section details the configuration of the mail types in the Mail module for this project.

4.1

Mail Types

The mail types that an organization can create are detailed in the following table. An X indicates that the
project role has been configured with the ability to create and send that mail type.
Type
Clients
Instruction
PMs Instruction

Code*

Description of use

CI

For the Client to provide direction


or instruction as appropriate.

PMI

For the Project Manager to


provide direction or instruction as
appropriate.

Architects
Instruction

AI

For the Architect to provide


direction or instruction as
appropriate.

Engineers
Instruction

EI

For the Engineer to provide


direction or instruction as
appropriate.

Consultant Advice
Notice

CAN

Design Query

DQ

General
Correspondence
Letter

PM

LC

Q
S

CN

MC

NS
C

X
X

For the Consultants to provide


advice and/or respond to
requests or queries.

For the Client and Design team to


raise queries relating to the
design.

GCOR

For all correspondences sent


internally or cross organizations

LETTER

For registering and distributing


official project letters

Request For
Information

RFI

For the Main Contractor/ NSC to


raise all request information
and/or clarification related to the
plans, specifications, drawings
and other project.

Inspection
Request

INR

For all Inspection Requests and


Approvals

Non Conformance
Report

NCR

For issuance of all Non


Conformance Reports

Response to RFI

RTRFI

For all response to RFI

Response to NCR

RNCR

For all response to NVR

Transmittal

CL

TRANSMI
T

For all documents transmittals

X
X

X
X

X
X

*Used in mail numbering.

XXX-YYY-00-MAN-0001 Rev.00 Draft

Aconex 2016

14

Project Configuration

Cod
e
CL

4.2

Role
Client

PM

Project Manager

LC

Lead Consultant

QS

Quantity Surveyor

CN

Consultant

MC

Main Contractor

NSC

Nominated Subcontractor

Mail Attribute 1 (Phases/ Building Zone)

The project configured values are detailed in the following table.


Value

Code

Usage / Description

00 - Non Specific

00

For non-zone specific matter

Project Wide

PJW

For project wide matters

XXX-YYY-00-MAN-0001 Rev.00 Draft

Aconex 2016

15

Project Configuration

5. Project Preferences
This section details the project level preferences for this project.
Preference

Value

Select project invitation method

Open

Maintain review status when superseding document

No

Enable project wide auto-numbering of documents

No

Make Response Required compulsory when creating RFIs

Yes

Make 'Reason for Issue' compulsory for Transmittals

Yes

Use project mail auto-numbering scheme by default for new organizations

Mail type with org prefix

Lock project mail auto-numbering scheme across all organizations so only the
project owner can change these settings

Yes

Lock mail and document types across all organizations so only the project owner
can change these settings

Yes

XXX-YYY-00-MAN-0001 Rev.00 Draft

Aconex 2016

16

You might also like