Customisation 15.4.x DE Attributes

  • Joel Allsop

We’ve been working on some big changes in the TfNSW Customisation, and they will start rolling out from V15.4.1 onwards.

Please read below, as these changes may affect any current projects.

If needed, V15.3.7 will still be available for download.  However, there will be no more V15.3.x updates.

15.4.2 – Updates

Below are some of the main updates for 15.4.2.  For more info, use the links below to refer individual pages.

Design – Pavements (FULL Version)

Design – Signs (FULL Version)

  • added additional attributes to meet BIM Schema.
  • added IfcEntity attribute for signs, post, and footings.

BIM – IFC (FULL Version)

  • added attributes for IfcEntityParameters – Pavements and Signage
  • added attributes for Drainage pits (Lat, Long) for more info refer to Attribute Pipe Coordinates

Survey – SUI Export (FULL Version)

  • added GAS – TfNSW_CADD.dwt; TfNSW_ORD.dwt; TfNSW_SUI.dwt

Survey – Metadata and Schema

TfNSW_Survey attributes will be exported as ‘Model’ (IfcProject) attributes.  Meaning these attributes will no longer be copied onto each ‘Object’.  These attributes are now stored under;

  • TfNSW_DE/IFCProject/TfNSW_Survey

Validating TfNSW_Project and TfNSW_Survey

15.4.1

Digital Engineering – TfNSW_Project

There are changes to how Digital Engineering (DE) attributes are managed and created.

The three groups will still apply;

  • TfNSW_Project
  • TfNSW_Location
  • TfNSW_Asset

However, as per the various TfNSW DE Schemas, attributes under TfNSW_Project will be exported as ‘Model’ (IfcProject) attributes.  Meaning these attributes will no longer be copied onto each ‘Object’.  This has resulted in changes to the structure of Project Attributes, which are now stored under;

  • TfNSW_DE/IFCProject/TfNSW_Project

Project Attributes created via the Digital Engineering Toolbar have been updated to reflect this change, along with MetaConnex files and other tools dealing with TfSNW_Project attributes.

Note: As the TfNSW_Project attributes will no longer be assigned to each Object, for now they can no longer be validated using MetaConnex.  We are working on a possible solution.

Existing 12d Projects

Where existing attributes are stored under TfNSW_DE/TfNSW_Project, an Attribute Manipulator file is provided;

  • $USER_LIB\TfNSW_DE_Att_Move_TfNSW_Project.12dattmf

that will copy the existing attributes;

  • from:  TfNSW_DE/TfNSW_Project
  • to:  TfNSW_DE/IFCProject/TfNSW_Project

The existing TfNSW_DE/TfNSW_Project attributes will not be removed.

Design – MTF Snippets (FULL Version)

After talking to a few users, we’ve decided to provide the original, un-complied, Snippets.  These will be available in the $User_Lib.

An additional Snippet is provided for applying extra pavement attributes:  TfNSW_DE_ATTR_PAVEMENT.mtfsnippet

If you have been using Snippets directly from the $User_Lib, the compiled Snippets will still be provided so that existing MTF’s don’t break.  After 15.4.1 the compiled Snippets will not be updated.  So we do recommend copying Snippets to the 12d Project Working Folder.

BIM Schema (FULL Version)

We have identified some Location and Asset attributes that are for Transport use only, but are still required to be provided.  When applying the appropriate MetaConnex file, the attributes are copied onto each Object.  These are created with a dash (-) as the default value, and stored as Project Attributes under;

  • TfNSW_DE/TfNSW_Location
  • TfNSW_DE/TfNSW_Asset

To help convert Schema Information into something useful that can be taken into 12d, a new spreadsheet is has been created.  Please see the Spreadsheet ReadMe tab for more info;

  • $USER_LIB\TfNSW_DE_SchemaToAttribute.xlsm
IfcEntity Attributes (FULL Version Only)

The IfcEntity attribute allows for correct ‘grouping’ of elements in the IFC file.  Some typical element types are;

  • IfcEarthworksElement
  • IfcKerb
  • IfcPavement
  • IfcRailing
  • IfcRoadPart
  • IfcSign
  • IfcFlowSegment
  • IfcFlowStorageDevice

Files shipped with the customisation that now include the IfcEntity attribute;

  • $USER\drainage.4d
  • $USER_LIB\TfNSW_Example_Pavement_Management.12dpmn

Additional files will be updated in future releases.

IFC 4×3

To allow use of IfcEntity types available for Infrastructure, the default version for exporting IFC files will be set to: IFC4x3

Previous IFC versions may still be used, however some IfcEntity will be shown as BuildingProxy.

Sample Data

The .12da and IFC files below contain example data that makes use of the updated Schema and IfcEntity attributes.
(Note: Some data does not contain all attributes)