Documentation Missions

DRAWINGS

Drawings are referred to as single sheet files (or multiple sheets if the same drawing is broken into several sheets). Single Drawings are more common in Construction Phases

AA100 - Site Analysis - A* - 210423

[Plan.Number] - [Plan Name] - [Rev]* - [Date.Issued]

SUB-SETS

Sub-Sets are multi-sheet files, scoping the same family, such as AI (Architectural Interior). In general, as Sub-set triggers of a Mission

AA - Analysis Set - 210423

[SubSet.Code] - [SubSet.Name] - [Date.Issued]

SETS

Sets are the combination of one or more drawings and/or Sub-Sets with a purpose or ISSUE which is to be the Title of the Set. A set carries the Cover page and hence the Drawings Index. Corrections and Markups are to be at the SET level

25.S.A - 1.PR - I1 - PRELIMINARIES - Draft

[Project.Code] - [Stage.Code] - [I.issue.Number] - [ISSUE] - [Status]*

PACKAGE

A Package is a group of one or more Sets, Reports, and Schedules issued both internal (ARCANARY) and external with a defined aim. Packages are closely related to the purpose of the stage (which normally has only one package). Packages require a transmittal in the Portal

25 South Ave - 3.DA - Development Application - Council Lodgement - WIP

[Project.Name] - [Stage.Code] - [Package.Name] - [Stakeholder, or sharing indication] * - [Status]*

MISSION Folder

We use the mission folder to develop each Sub-Set, there must be a mission for each Sub-Set or Document,

Different Sub-Set = Different Mission

• Create Mission Folder in:

[Project]/MISSIONS/... named as:

25.S.A* - 3.DA** - AA***

*: Project Code

**: Stage Code (Sequence+.+StageType.Code)

***: Sub-Set Code, Drawing or Document

ITERATION Folder

Iterations are steps in communication, types can be:

• Kickoff: The project Responsible create an overall plan, target, timeframe and transmittal for the subject mission.

• Markup ##: The Project responsible create a correction

• WIP [Scope]: Work in progress, need to specify what has been done

• Complete: Denotes that all items from the markup have been updated

• Create an Iteration folder named as:

210523 - MGP - FIV, PRM - Kickoff - Revision B

YYMMDD* - [Author/s]** - [Receiver/s]*** - [Type]**** - [Notes]*****

SET files

Set files sit in the Mission Root Folder, and link files as required

[Project] / MISSIONS / ...

17003 - 25 South Ave - 25.S.A

MISSIONS

3.DA - A

210322 - MGP - KICKOFF

210323 - TGT - ALL - Preliminary Set Setup

210324 - MGP - SVA - MARKUP 01

210325 - SVA, FIV - MGP - WIP- 200's and 100's

A - Architecturals - 210325

210326 - FIV - MGP - MARKUP 01 - COMPLETE

210327 - MGP - FIV - MARKUP 02

A - Architecturals - 210327

...

3.DA - AC

210326 - MGP - - KICKOFF

210328 - FIV - MGP

AC - Compliance Plans - 210328

The Files with Extension .bex (Set file from Blue Beam) are save in :

FILES / BEX / ....

...PROJETS / 17001 - 25 South Ave - 25.S.A / FILES / BEX / 25.S.A - 3.DA - Development Application - 210725 - WIP.bex

Remember to:

1. Create Set Categories as: AB, AD, AC, AE... So plans are Grouped by Category

2. Create page label as a combination of field regions from the plans: {Number} - {Name} - REV{Revision}. This will result in labeling every plans as: AE111 - Ground Floor Elements - REV A.

3. Modify Set so It is only the Page label that is displayed.

See Tutorial here:

BLUEBEAM - SETS

We use Bluebeam software to keep control of the documentation and to issue markups.

We try to achieve that the feedback is given only once and that we can have accountability and traceability of corrections as well as the subsequent amendments and questions to the project manager.

Take the Documentation development process as an iterative exercise between a designer and the project manager.

Objectives

PM - Give clear, concise instructions backed up with standards and examples. Keep track of changes, Revisions, Transmittals, and markup layers.

Designer - Clear on what has been achieved, and expose all concerns, clashes, and questions to the PM

Colour Coding

RED: Markup, Corrections to be amended

Highlighted in Yellow: Markup is completed

PURPLE: Drawing Notes to remain in the Set; Pending external input / Questions that need to be resolved by stakeholders. TO BE ADDED TO SOURCE FILE (DWG, BIM)

BLUE: Temporal note that has to be included in the drawings literally TO BE ADDED TO SOURCE FILE (DWG, BIM)

ORANGE: Internal questions from the designer to the PM = Pending internal Input

Light Green: Used to bubble up areas that have been updated from previous Revisions (only going back one revision) TO BE ADDED TO SOURCE FILE (DWG, BIM)

Light Blue: Used to bubble Tentative changes or Options TO BE ADDED TO SOURCE FILE (DWG, BIM)