Author: admin

  • Markup Model with Tekla BIMSight

    Tekla BIMSight is a free tool provided by Tekla to view and markup up Tekla model. We use this too extensively for highlighting and resolving model issues. It will be very convenient if you can download and install this software on your machine and have some basic skills on using the tool

    Where to download the software.

    You may download the software from https://www.teklabimsight.com. It is free to use as of today (04/04/2018).

    What type of models can be viewed with Tekla BIM Sight?

    You can view at least the following types of CAD formats using Tekla BIMSight

    • Tekla BIM exported models
    • IFC Models
    • Autocad 2d and 3d Models

    How to view IFC and Autocad files with Tekla BIMSight.

    Create a project and simply add the files to the project.

    How to markup and send the marked up Tekla BIM model?

    There are one or two things to know about this. Please watch the videos below to get a handle on this. The key thing is make your comment public, and also save as package so that others can view your markups.

    Here are the links to the video

    Here is Video from Tekla itself

    https://youtu.be/A7Ud_RcTwe0

  • Jigging with SHIFT, CTRL and Mouse Wheel Functionality (AutoCAD .net API)

    If writing software then make it easy for your users.
    User Input is critical. You gotta make the user experience amazing.

    Any AutoCAD programmer knows that things which an algorithm may take a million years and infinite computational power to do can sometimes be easily done by a human being instantly. In the same way it is sometimes much easier to give a human being the ability to choose: then you can get an optimum result without complex algorithms.

    This post is a code snipped of how you can utilise the CTRL + SHIFT + Mouse Wheel (up/down) mechanisms in order to produce different desired results when operating a custom jig.

    Here is the code:

     

    So when the appropriate user input happens, then the jig can respond accordingly. Yes it’s true – the OOP purists will say: “you’re passing a concrete type in there” – I can always change it later if I want.

  • Offsetting Truss Lines from Intersecting Fire Collars (Bubble Deck + Video Demo)

    The effective point of this blog is to demonstrate the use of a jig – not just any old jig – but a jig which accepts user inputs using the CTRL + SHIFT + MOUSE-WHEEL (up or down) to change the jig’s behaviour. When the jig is finished running, everything returns back to normal.

    This is best demonstrated with a video:

    Move Intersecting Truss by Panel Thickness (with Jig) from Tek1 on Vimeo.

    We use this jig and command as part of our Bubble Deck tools dll.

    The reason we utilise tools like this:

    This allows us to turn over shop drawings faster, more efficiently. This allows our precast fabricator to massively improve their working capital position:

    • Their factory staff is always utilised – they don’t have massive overheads of 50 guys sitting on the factory floor twiddling their thumbs,
    • They can get in and out of jobs quickly – minimising their liabilities and expenses and also collecting revenues faster,
    • Faster revenue has huge benefits in terms of interest saved vs interest earned – especially for the developer. If you can allow the developer to finish the job a couple of weeks earlier you save on: construction costs, and also, as before, their interest expenses and their liquidity also improves. That’s worth its weight in gold.
    • There is nothing worth more than: accurate drawings, done quickly. That’s what we strive for.
  • Speed up the Shop Drawing Process – Order Dimensioning Tool (Bubble Deck)

    Dimensions are critical
    A nice photo of a scale.

    I’ve made a tool which allows you to order dimensions faster.

     

    Here it is below:

    Order Dimension Command from Tek1 on Vimeo.

     

    For those who want to read my philosophy of the benefits of improving productivity and how I approach detailing – see below. If that bores you, then you may safely skip it with no loss.

    An Approach to Detailing: Make things Easier and make them faster

    Productivity is what makes the world go round faster. It’s why you can fly from Melbourne to London in less than 24 hours. 500 years ago it might take you a few months – and that too at a break neck speed. Today, anything over 2 days is a painful delay.

    Improving Shop Drawing Productivity

    It’s the same with shop drawings. We found that our detailers were spending too much time ordering dimensions. That’s something that can be sped up. We want to smash something which had taken over an hour down to 5-10 minutes. And if possible, we want to reduce that time to zero. This allows our detailers to turn around shop drawings quickly to their Precaster – which will in turn massively improve the Precasters turn around time, and working capital situation, and will allow a continual throughput of panels being cast on the factory floor. In other words you will never have a situation where you have 30 guys on the shop floor twiddling their thumbs because their drawings weren’t brought to them quick enough. And if you can get out of a project earlier, that means you can get paid earlier. That in term will allow developers to quickly build and get out of a project ASAP, which would have monumental impacts to their working capital positions and overall profitability. In short, doing things quickly and accurately is worth a lot………………..Time is money.

    Small improvements have big impacts.

    That’s how I approach detailing.

     

  • Thoughts About the AutoCAD API (AutoCAD .net API)

     

    Get your API working hard for you. Like worker bees.
    Get your API working hard for you. Like worker bees.

    I got thinking about the AutoCAD APIs (ObjectARX/.NET) – they’re virtually the same – the .NET API is basically a wrapper to the ObjectARX API (with some differences). If you want the full power of low level calls then you gotta go with ObjectARX. But then using .NET comes with a very powerful benefit – a host of libraries and code readily available to utilize. If you’re talking UI then WPF is waiting for you if you go down the .NET path, but not so with ObjectARX.

    Anyways, when you think about the API  there are a few issues that you gotta manage:

    1. The opening and closing and disposing of Objects.

    And the main operations that come to mind are the following:

    1. Adding Items to the database.
    2. Removing Items from the database.
    3. Editing existing items from the database.
    4. Getting Items from the database.
    5. If this happens do that (Events) which ties into all of the above.

    Is it just me or does smack of a RESTful API? Well not quite, because we can store state in variables, both within the drawing, and in variables within our classes (temporary).

    These are the steps:

    1. Identify a resource.
    2. Operate on that resource.

    We can go about this in a few ways:

    1. Using extension methods. This means that we have already identified the relevant resource and we act on it.
    2. Static Methods where then operate on those resource. (I use resource in the sense that Fielding uses it).
    • GetResource( parameters)
    • Action(parameters)

    We shouldn’t have to worry about all the lower level stuff.

    Perhaps a better wrapping API can be written incorporating this. I know Mr Wolfgang Tertinek has wrote about it extensively in his blog. It’s a good approach, but perhaps common tasks e.g. changing a layer of an object can be incorporated in this model. Ideally this should be written simply with core level logic without direct use of a particular dll.

    • .e.g something like this: SelectionFilter.Create(layer: “test”, types: [BlockReference, Mtext]) – without going into the specifics of setting type filters etc. A DSL much like Active Record for handling these types of queries.
  • WPF User Interface for Precast Panel Comparison

    This utilises WPF to compare panels, isolate changes and make better decisions.

     

    See below for a demonstration:

    WPF – Eliminating Errors using Cross Checking from Tek1 on Vimeo.

     

     

     

  • 3d Steel Estimation

    Estimate accurately 3d Model

    Click to Download Sample take-off

    Accurate estimation from people with takeoff experience, highly skilled in the use of Autocad, Tekla, and Excel. You save your estimators time. We provide you low-cost accurate takeoffs.

    How do we do it?

    We prepare a cad file in Autocad cad suitable for conversion to Tekla.

    Then with a single button Click, We convert All the members to Tekla native members which is Col, Beams, Bracings. Base Plates.

    Deliverables

    1. Tekla Stick Model
    2. Linear Footage of Balustrades and handrails
    3. KISS file from Tekla model (If done in Tekla)
    4. Excel Sheet summary of the take-off of items that are not stick modelled.
    5. Grating Summary
    6. Tread Summary

    Benefits

    • Fast turn around – We have the tools, the skills and the man power.
    • Low Cost
    • 3d Model
    • Better Information to GC Contractor via 3d Model

    Our Office Locations

    Head Office in Melbourne, Australia. Back office, Chennai, India

    Our Contact Details

    email: koshy@tek1.com.au

    Phone +61 3 9560 6397

    web: www.tek1.com.au

  • The Connect Handrail Command – Demo (BubbleDeck)

    A lovely picture of handrails.
    A lovely picture of handrails.

    This is a little utility which connect handrails. It does so if:

    1. The handrail block references are parallel to the panel edges, and
    2. If they are a minimum 560 mm away from the edges and
    3. If they are colinear with each other.

    Here is a demo:

    Demo – Connect Handrails Command in AutoCAD` from Tek1 on Vimeo.

  • On Line Equality (AutoCAD .net API)

    Some lines may be more equal than other lines? The AutoCAD .net API's EqualTo method may disagree with your interpreation of equality. Here are the results;
    Some lines may be more equal than other lines? The AutoCAD .net API’s EqualTo method may disagree with your interpretation of equality. Here are the results;