PLQ2.3 – Object Naming (cont.) & House Layout

Hello BIMfans,
After starting to author my Architectural graphical model last week.  This week I have continued its development resulting in a model which while work in progress is starting to really come together!

3D
As with last week, you can access this model here through Autodesk’s A360 portal.

I was very happy to see that after last week’s blog, a lively debate started on LinkedIn around object naming; as I also had some questions of my own.  As you might have saw last week, when I named my walls I did not put the thickness of layers into my subtype. so for example a wall might have been called:

BBH_SolidWall_PlasterBrickwork

I did this because within BS8541-1, table 1 states that the subtype should not capture attribute data.  However, while authoring my model I quickly needed to distinguish between walls with the same build up but different thicknesses.  Unfortunately,  Revit doesn’t allow duplicate family names I couldn’t use ‘BBH_SolidWall_PlasterBrickwork’ for walls with the same layers at different thicknesses, so a solution was required.

BBH_SolidWall_PlasterSingleSkinBrickwork

Initially I described the number of brick skins to avoid recording attribute data within the name, but quickly realised that that was stupid, and I was describing the thickness of the wall, just in a very awkward way.  So I was led back to using the thickness of each layer within the subtype.

BBH_SolidWall_15Plaster225Brickwork

Now to make sure my reasoning was sound, I decided to ask Twitter.  Interestingly (but not very helpful) the majority of people who participated in my poll thought that both options were wrong.

VoteTweet
In fact the correct answer is that ‘both’ are correct.  As the wall does not have a predefined subtype, anything goes so long as it has no attribute data, and uses no special characters other than an underscore ( _ ).

To make matters worse, I added some new objects to my model this week that had to use BS8541-1‘s other naming convention for unclassified objects.  Basically, if you are using an object without a classification field then the unclassified object naming convention is required, which is a tad more complex:

BS8541NamingUnclassified
To use this convention I did what all great men do in times of strife.  Ignore the optional fields, in this case it is ‘presentation’.  Also why is BS8541-1 now telling me to use hyphens(-) instead of underscores( _ ) between each field in the example object?…

To make sure that I complied with the original Employer’s Information Requirements and my BIM Execution Plan, I needed to use this naming convention for the following objects:

  • Kitchen worktops;
  • Bespoke window sills; and
  • Top of small units which also acts as a shelf.

This meant I needed to find out some extra information.  We already have my role, in this instance it is Architectural, classification means we need to rely on a Uniclass 2015 table (see example below), we have skillfully skipped presentation, source is my organisation (BBH) as the object creator, type relates to the corresponding IFC type, and subtype will allow me to differentiate between any other similar objects.

UniclassWorktop
Uniclasss 2015:  Those underscores will look great inside my kitchen worktop family name…

Meaning that I named my kitchen worktop like this:

A-Pr_40_50_21_45-BBH-Worksurface-Kitchen

Note:  Because of the underscore ( _ ) within the classification codes I have used a hyphen (-) as a field separator which doesn’t comply with the text but does comply with the example provided within BS8541-1.  This inconsistency isn’t very helpful, so I have chosen a solution that suits my situation best.

Objects such as kitchen worktops and shelves have been added for a reason.  Each of these were needed to accurately reproduce my floor layout, as required to satisfy my next Plain Language Question “What is the Layout of my house?”.  So now that they have been modelled, the result is a set of floor plans built into a graphical model that’ll be used for its own purposes as well as capturing what assets I have in order to answer my next Plain Language Question.  Once completed I was able to set up suitable views of my floor plans, and transfer them to a title block to complete this deliverable.

Plans
The full size .pdf plans can be accessed here.

And there you have it, after putting in the objects I needed I have now been able to produce a drawing containing my ground and first floor plans which has been derived directly from my graphical model.  Using this information I now know the layout of my house; therefore Plain Language Question PLQ2.3 is complete!

Model Generation:
2.1 What existing information is available?
2.2 Is there sufficient information to produce a BEP?
2.3 What is the layout of the house?
2.4 What assets are contained within?
2.5 What asset information can be linked to the graphical model?

Now that I have a pretty strong Architectural model, it’s time to start creating some of my other models to record the electrical and mechanical objects

Note:  If you have any comments or opinions regarding the Layout of my House, please let me know either on twitter, or commenting below.

Advertisements

4 thoughts on “PLQ2.3 – Object Naming (cont.) & House Layout

  1. The bs8541-1 alternative is for applications that use symbols (instead of objects) that don’t carry classification (and so on) attributes and so need them in the name. Surely work tops are objects?

    The hyphen/dash debate was protracted. In the end we made a choice. The important thing is to eliminate special characters and dustinguish between in-field and between-field delimiters.

    Like

    • Thank you Nick,
      My WIP model currently does not include any classification information for my work top (not even an omniclass number), that is why I used the unclassified naming convention.

      Thinking about I will need to include classification when I do my final deliverables; so by next week I will have included classification and renamed my kitchen worktop to suit.

      In regards to the BS8541-1 naming convention, I believe there are some inconsistencies in the standard but i’ll discuss with you outside of the blog.

      Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s