{"id":1320,"date":"2016-02-23T06:52:04","date_gmt":"2016-02-23T14:52:04","guid":{"rendered":"https:\/\/blogs.ssi-corporate.com\/waveform\/?p=1320"},"modified":"2020-10-23T09:39:50","modified_gmt":"2020-10-23T16:39:50","slug":"automate-generation-of-multiple-navisworks-models","status":"publish","type":"post","link":"https:\/\/www.ssi-corporate.com\/ja\/blog-waveform\/automate-generation-of-multiple-navisworks-models\/","title":{"rendered":"Automate Generation of Multiple Navisworks Models"},"content":{"rendered":"\n
\"AutomateNavisworksModelGeneration2\"<\/a><\/figure>\n\n\n\n

Automating our current activities is the easiest way to improve the way we use our time and become more efficient. It does not require any additional education. Neither does it require implementing any new processes or Standard Operating Procedures. Just recently I was asked what is the best way to automate the generation of several Navisworks models which are used for different purposes throughout the organization. The request came requiring 6 specific Navisworks models that all referenced the exact same project but needed different information to be visually communicated depending on who was to consume it. This approach of having multiple Navisworks models for the same project is considered our best practice which is why I thought I would write a blog post and provide all the necessary setup you need to create multiple Navisworks models with a single double click<\/em>.<\/p>\n\n\n\n

In the below examples I am automatically creating 4 different Navisworks models. These are just some examples but there is a virtually infinite amount of combinations you could create such as:<\/p>\n\n\n\n

  1. Model of only parts that have changed in the last week<\/li>
  2. Model used to visually identify what has been installed<\/li>
  3. Model with certain compartments removed to protect IP when sharing model<\/li>
  4. Model with ShipConstructor information stripped out to protect IP<\/li>
  5. Model to be used as a 4D simulation of the assembly sequence<\/li>
  6. Models combining files from other CAD applications or just pure native AutoCAD<\/li><\/ol>\n\n\n\n\n\n\n\n
    \n\n\n\n

    Included in this post<\/h2>\n\n\n\n

    Management Only<\/h3>\n\n\n\n
    \"NavisworksManagement\"<\/figure><\/div>\n\n\n\n

    A virtual model is key for management or department leads to see progress of the project. However, in some cases the view that you want to provide to management is not the raw work in progress model but some \u201cclean\u201d version of it.<\/p>\n\n\n\n

    There are several ways to create this management friendly Navisworks model. One of the easiest ways is to have a production drawing which is only updated with the current work in progress when it is determined appropriate and then cleaned up.<\/p>\n\n\n\n

    In the example I provide below I am using Product Hierarchy drawings as my clean version.<\/p>\n\n\n\n

    <\/div>\n\n\n\n

    Engineering \u2013 Entire Project<\/h3>\n\n\n\n
    \"NavisworksEngineering1\"<\/figure><\/div>\n\n\n\n

    This is the most obvious and what the majority of companies are, or should, be doing. The Navisworks model created in this version will be linked to the source ShipConstructor drawings allowing any designer to be able to select a part in Navisworks and switch to the ShipConstructor drawing automatically.<\/p>\n\n\n\n

    I use PublisherLT to allow me to generate this model and ensure all my parts are visible as well as have the drawing options that I want (solids, bevels, no marking text, no flow direction, no free ends, etc.)<\/p>\n\n\n\n

    <\/div>\n\n\n\n

    Welds<\/h3>\n\n\n\n
    \"NavisworksWelds\"<\/figure><\/div>\n\n\n\n

    Visually seeing the welds in Navisworks provides so much value to ensure all welds have been applied with the correct standard. It also is used to visually see progress of the production of welds on the shop floor.<\/p>\n\n\n\n

    A separate Navisworks model is created in the example which can be combined with any other Navisworks model if required.<\/p>\n\n\n\n

    <\/div>\n\n\n\n

    Engineering \u2013 Per Unit\/Zone\/Person<\/h3>\n\n\n\n
    \"NavisworksUnit\"<\/figure><\/div>\n\n\n\n

    It is often that you or a specific designer will require only a subset of the entire project. This can be a specific unit or grand block, a combination of systems, or a model for each person of the area they are currently working in. The possibilities are endless.<\/p>\n\n\n\n

    In this example I have created a Navisworks Model per Unit.<\/p>\n\n\n\n

    \n\n\n\n

    Naviswork Batch Utility Vs. PublisherLT<\/h2>\n\n\n\n

    I know there are some of you who use Navisworks Batch Utility to generate your Navisworks models and even though it is a very powerful and useful tool there are some limitations which is why I decided not to use it. The main reason is that by using PublisherLT I am able to set up the files the way I want them before generating the Navisworks model automatically. I can ensure all parts are unhidden, or specific layers are on\/off or even change the display options of parts to get the solid and bevel representation. All this setup is configured in the PublisherLT operation so I never need to worry about doing any pre-setup.<\/p>\n\n\n\n

    \n\n\n\n

    How To Get Started<\/h2>\n\n\n\r\n <\/span>\r\n
    \r\n