Introduction to the AAHK

project.
Table of contents
TRC building for the Area Codes
Numbering system
Modelling of laminated “Finger” shim packs
Plate / stiffener corner notching
Tongue Plate / Stiffener Plate modelling gaps & welding
HSFG Bolts
Material grades
Modelling “class” colours
Model Phasing.
Standard Part Naming
Standard Welds & Standard Tail Notes.
Static Component creation.
Importing of components to the tekla share model.
Model stick management.
New Team Member Checklist.

 TRC building for the Area Codes.

Areas codes are to be applied on to tekla stick members the AAHK, uda tab. (example below)

 Numbering system
Fitting prefix’s   (No phase number required on fittings, to reduce 2D drawing qty’s)

p = Plates, beams, general all parts, except purchased items & shim pack plates.
sp = Shim pack fitting prefix.
m = purchased modelled items i.e. special modelled bolts, modelled studs, nuts etc.    
Assembly prefix’s PDC are using phases to further break down the assembly locations in the building areas for
fabrication / installation packages.

Main Parts of Assemblys, (i.e. shim pack, bracing coverplates)

Secondary welded parts to the main part. (i.e. welded endplates, brace welded tongue plates)

 Modelling of laminated “Finger” shim packs

a. When the engineering drawings nominate 20mm MAX packing, provide a 10mm gap with 20mm thick
packing plate U.N.O.
b. Laminated “finger” shim packs are to be modeled to the nominated thickness as a single plate. Using the
“L_SHIM_PK” profile
(Note: if the shim packs are larger than a A3 sheet of paper split the shim in the center, leave a 1mm gap
between the shims)
 Prefixing of laminated shim packs

 Plate / Stiffener corner notching

Use 20mm fillet notch for plate copes, as pre AAHK project standard notes.
 Tongue Plate / Stiffener Plate modelling gaps & welding

Refer to the snap shot below for the approved modelling gaps and welding details for CHS & SHS Tongue
plates.

Refer to the snap shot below for the approved modelling gaps for Stiffener plates.
This gap is only required where the stiffener plate is to be welded into a sectional member.

Refer to the snap shot below for the approved welding details for Stiffener plates, when a CFW is required.
 HSFG Bolts
All HSFG bolts require the top washer to be turned on. As HSFG bolts require 2 washers.
(Note: We have allowed for the top washer to be a DTI “Squirter” washer which is the same thickness but
larger diameter than the standard HFW. The fabrication subcontractor and the HK Airport Authority, will
decide if they want to revert back to a HFW prior to construction)

The DTI “Squirter” washer has been setup to always be under the bolt head
The Bolt grades are generally noted as “Size” / “Grade” / “Tightening procedure” / “Threads in shear plane”

Grades

FG = General grade 8.8

FH = High Grade 10.9

Tightening procedure
B = Tensioned
NSF = Non slip

Threads in shear plane

N = Threads of bolt included in shear plane

X = Threads are to be excluded from shear plane
  Material grades
Plate grades

Open section & hollow section member grades

 Modelling “class” colours

Modelling Connection Class Status Colours

Stick members with Class 1 applied = Aecom stick geometry still work in progress by Aecom

Stick members with Class 13 applied = Aecom stick geometry Finalised, Sticks ready for connecting by PDC or
partially unconnected by PDC.

Stick members & fittings with Class 3 applied = PDC applied competed connection.

Stick members & fittings with Class 33 applied = Aecom Checked connection & stick members.

Communication Classes between Aecom and PDC

Stick members with Class 4 applied = Aecom additional sticks added to the share model

Stick members with Class 2 applied = PDC deleted stick members. (Note: do not delete, move sticks to Phase
9999)

 Model Phasing.
 The model phasing will be carried out by the Perth office for the following AAHK share models.
Façade
Main Concourse (ROOF)
Wings (ROOF)

The model phasing will be carried out by the Manila office for the following AAHK share models.
Node (ROOF)
Hotel (ROOF)

For a phasing plan please contact your model controller or project PM “Simon Schmitt”

 Standard Part Naming

Gusset plates = GUSSET PLATE

Seal Plates = SEAL PLATE

Endplate = ENDPLATE

Toe plate = TOE PLATE

Splice plate = SPLICE PLATE

Baseplate = BASEPLATE
Stiffener plates = STIFFENER PLATE

Bracing tab plate = TAB PLATE

Bracing tongue plate = TONGUE PLATE

Bracing Cover plate = COVER PLATE

Haunch = HAUNCH

The snap shot below shows the typical standard part naming used for a generic Plinth Mounted Connection. An
example of this type of connection is RWS-0241-STAT_00002.uel.
This connection has been checked and contains all standard part names and design notes.

 Standard Welds & Standard Tail Notes.

(Note: all welds to be modelled to 100% of real world locations)

FPBW = use bevel grove for type typ. u.n.o.

PPBW = use as shown on design sketches
SEAL WELD = use for seal welds to closure plates.
  Static Component creation.
(Note: All component creation is to be carried out in a single user copy of the AAHK models, Do not create
components in the Tekla share live model.)

Step 1. Contact model controller to advise for list of static connections.

Step 2. Review engineers design & model connection. (If modelling queries are required create a Trimble connect
“To DO”)

*Ensure all plate grades, numbering prefixing fields are correct & filled on the all of the connection plates prior to
creating the static component.

Step 3. Fill in the static connection register

Wings = J:\19-0086\600 QA and QC\608 Internal Documents\AAHK - Static component HUB\Excel Registers\Wings

Node = J:\19-0086\600 QA and QC\608 Internal Documents\AAHK - Static component HUB\Excel Registers\Node

Hotel = J:\19-0086\600 QA and QC\608 Internal Documents\AAHK - Static component HUB\Excel Registers\Hotel

Main Concourse = J:\19-0086\600 QA and QC\608 Internal Documents\AAHK - Static component HUB\Excel
Registers\Main Concourse
Once filled in the connection register will generate the required static component name in column F, this code will
be used for the component "name" & column G will create the required "component identifier" field. Copy and paste
the codes from the register to the custom component to the custom component wizard, during creation of the
component. (see below)

Step 4. Create custom component.

a. Select all of the parts, cuts & welds, required for the connection. But not the main stick members, as we do not
want them to be re-created by the component.

b. Open the define custom component tool

a. Once open on the first tab (TYPE/Notes) copy and past the required component name & component idetifier
from the register in to the component creation tool.

b. On the third tab (Advanced) tick the “Allow multiple instances of parts connection between same parts”
(this allows a component to be used on the other end of the member sticks) & Press next to to select the
parts winch will be created by the component.
c. Select the parts, cuts, welds, bolts which you wish the component to create and press next. (Note if selected
at start just press next)
d. Select the main part, this will be the first member pick required to apply the component, in the model.
(Generally the main part of a connection will prefer a main member which is vertical of flat member if
possible) Press next to the select secondary parts of the component.
e. Hold down “Ctrl” on your keyboard & select the secondary members of the component, this sets the second,
third, fourth & so on members required to apply the component. Press finish. (Note: it is not possible to add
a extra member to the component after finish is pressed, you will need to re-create the component, ensure
all required incoming stick members are selected.)
f. In the model select the component (right click) select edit custom component.

g. Once the component is open, search for the "STATIC COMPONENT DATA" component, in the “Applications &
components toolbar” (if it’s missing import it from the following location. J:\19-0086\600 QA and QC\608
Internal Documents\AAHK - Static component HUB\Instructions
h. Apply the component to your main part in the component & explode the "STATIC COMPONENT DATA"
component.

k. Delete the plate that the "STATIC COMPONENT DATA" created

l. Press the button shown below on the custom component editor ribbon.

m. The "STATIC COMPONENT DATA" has imported the data in to your component.
n. Mapping the "CHECKING CLASS" to the plates. (Coppy the text, as below)

o. Open the custom component browser.

p. Click on the plate and navigate to the "class" field of the selected plate.

o. Right click on "class" and add equation.

q. Paste the "CHECKING_CLASS_dont_edit" rule. (Note: the rule will need to be manually added to all plates
within the connection.)

r. Save and close the component.

s. You will notice that the checking switches have now been added to your component, it controls the class.
Toggling the switches will change the "class" field on the plates.

t. Testing of Component is now required. Copy the stick members that require the connection to the side of
the model, apply the componentto the copied member sticks, check that all required objects are contained
with in the connection & the component works as desired.
u. After Testing & self check, Publish the component to the following apropriate directory

Wings = J:\19-0086\600 QA and QC\608 Internal Documents\AAHK - Static component HUB\UEL static
components\Wings\UEL Ready For Checking
 Node = J:\19-0086\600 QA and QC\608 Internal Documents\AAHK - Static component HUB\UEL static
components\Node\UEL Ready For Checking

Hotel =J:\19-0086\600 QA and QC\608 Internal Documents\AAHK - Static component HUB\UEL static
components\Hotel\UEL Ready For Checking

Main Concourse = J:\19-0086\600 QA and QC\608 Internal Documents\AAHK - Static component HUB\UEL
static components\Main Concourse\UEL Ready For Checking

Step 5. Creating Static Component pick order snapshots

a. Create a pick order snapshot via a screen shot, and edit via bluebeam adding a number overlay over the
incoming members. (As example below)

b. Save the PDF in the following directory area apropriate location & save the PDF with the connection
name & pick sketch number.
 Wings = J:\19-0086\600 QA and QC\608 Internal Documents\AAHK - Static component HUB\UEL static
components\Wings\UEL Pick order snapshots

Node = J:\19-0086\600 QA and QC\608 Internal Documents\AAHK - Static component HUB\UEL static
components\Node

Hotel =J:\19-0086\600 QA and QC\608 Internal Documents\AAHK - Static component HUB\UEL static
components\Hotel\UEL Pick order snapshots

Main Concourse = J:\19-0086\600 QA and QC\608 Internal Documents\AAHK - Static component HUB\UEL
static components\Main Concourse\UEL Pick order snapshots

Step 6. Update Static excel register “Ready for checking”

Toggle the “connection. Uel created?” & the “ .uel ready for checking cell to Yes.

Step 7. Send email to checkers

Send email to the following project checkers advising component is complete.

Dave.Briggs@dbmvircon.com

Dave.Corner@dbmvircon.com

 Importing of components to the tekla share model.

Note: During the process of importing or updating the static components to the share model ensure the
following
1. Ensure only a single user is in the model.
2. Prior to importing the components “Reserve the next write out”
After import/ update complete write out the model. After the write out other users can enter the model.
  Model stick management.

AECOM Product codes

AECOM Product codes are unique to each stick member in the model & are not to be removed or duplicated from
any of the main members of the model. Modification of the product code requires to be managed by a senior project
lead, as all modifications to the product code require to be tracked & reported to AECOM so they can update their
Grasshopper programming script.
(The product codes are used by AECOM in to map the member sticks to their grasshopper program, which is used to
update the following. Member sizes, Member geometry)

Management of product code due to split member

Step 1. Approval to split.

Modeller to seek approval to split member. (Modeller to provide the DBMV senior model controller with the Aecom
member “Product Code” required to be split & the connection code which requires the member to be split. The
senior model controller will then seek approval from Aecom to split the member.)

Step 2. Splitting of the member

Once approval from AECOM is received, the model controller is to split the member using the following method.

a. Split the member

b. Inquire the split members, One of the parts will be owned by Aecom (Original part) on this member, select
the member & go to the go to the “AAHK” UDA tab, leave the AECOM “Product Code” as is & toggle the split
beam switch to “YES”.

c. For the new member created & owned by PDC, select the member & go to the “AAHK” UDA tab, adjust the
AECOM “Product Code” as follows “DBM-[AECOM PRODUCT CODE]-1” & toggle the split beam switch to
“YES”.
Management of product code due to Relocated member

Step 1. Approval to relocate member

Modeller to seek approval to relocate member. (Modeller to provide the DBMV senior model controller with the
Aecom member “Product Code” required to be relocated & the connection code which requires the member to be
relocated. The senior model controller will then seek approval from Aecom to relocate the member.)

Step 2. Relocation of the member

Once approval from AECOM is received, the model controller is to relocate the member using the following method.

a. Prior to relocating the member, select the member & go to the “AAHK” UDA tab, adjust the AECOM “Product
Code” as follows “DBM-[AECOM PRODUCT CODE]-2” & toggle the “Modified Member Node Location”
switch to “YES”
Management of Member due to localized member End Offsets (Static connections for the Node & Hotel Model
only)

If the situation arises where connection requires a localized member end offset to be applied follow the steps below.

Step 1.

i. Prior to applying a localized offset select the member & go to the “AAHK” UDA tab, leave the AECOM
“Product Code” as is & toggle the “Localized Offset” switch to “YES”

Step 2.

j. Select the member and apply required localized offset to the required End Offset field.

Stick Management tracking tools.

New View Object Representation’s created.

New AAHK - DBM REVISED MEMBER TRACKING - 3D VIEW
New Selection filter created.

New Tekla Organizer template created for correspondence to Gary @ AECOM & Tracking.
Excel report, that is exported from Tekla organizer.
 New Team Member Checklist.
New team member is to ensure the following
1. Tekla 2018i with service pack 4 in installed on their PC
2. The tekla warehouse add on “US custom variables” is installed to tekla 2018i
3. Do not download a new version of any of the share models, contact your model controller or the project
PM to arrange an up to date copy of the model to be copied to your D: drive.
 4. The AAHK share models are required to be stored in a typical location, on all team members PC’s for the
components to work correctly with tekla model sharing.
5. Invited to the share model via the model controller ( Note: that team members only creating static
component, do not require access to the share model, Only a single user copy of the model)

Correct model folder pathing (Red part is the model folder)

Façade = D:\TeklaStructuresModels\AAHK SHARE MODELS\FACADE\3133-ACM-PCTR-ST-NE-FAÇADE

Main Concourse = D:\TeklaStructuresModels\AAHK SHARE MODELS\MAIN_CONCOURSE\3133-ACM-PCTR-ST-NE-

MAINCONCOURSE

Wings = D:\TeklaStructuresModels\AAHK SHARE MODELS\WINGS\3133-ACM-PCTR-ST-NE-WING

Node = D:\TeklaStructuresModels\AAHK SHARE MODELS\NODE\3133-ACM-PCTR-ST-NE-NODE