AECOSim Clash detection markup

All

I want to be able to create PDF Markups within AECOsim's Clash detection tools similar to what you can do in Navigator.

Is this possible?

Ian 

ABD version 08.11.09.747

Parents
  • Ian, AECOsim Building Designer does not have the built-in markup capabilities that Bentley Navigator contains.



  • Hi Paul

    That I agree with (limited). However, this would be a massive benefit to the design workflow. A user will be able to create, view, review live markups and dynamically change the model. Why restrict AECOsim functionality!!!!!

    So is there no other way to do this?

    Ian
  • Hi Ian,

    The process in Navigator creates saved views that get referenced into sheet models in the overlay file. And it ties it all together in the Markup dialog box where you can assign values to the various properties for tracking, etc.

    I suppose  you could create a saved view from the Clash Detection results and create a sheet model, reference in the saved view - a very manual process. You wouldn't get the tie in with  the markup dialog box for that 'intelligence'.

    So, to take advantage of the 'intelligence' behind the markup process the recommended workflow is to utilize imodels, overlay files for the clash detection jobs and markups and review the markups back in AECOsim.

    Keep in mind the MS_MARKUPPATH configuration variable is used to point to the various project directories to 'harvest' markups.  Any markups found in those directories are shown in the Markups dialog in the originating software, in this case AECOsim BD.

    One thing done to take it to another step is to reference the overlay file, with no live nesting, back to the working models to get the markup 'markers' show up in my views at  the location of the markup.

    Paul



  • Paul

    I think I am right in saying, if we use i-models with Navigator to run the clashes and each week we create a new i-model, Navigator will no longer display the history of the clashes, thus there is no audit trail of the clashes ie each week it only shows the current clashes

    This is the reason for my initial posting. AECOsim does maintain the history of clashes.

    Ian .
  • bump...

    Other problems:

    1. Activating a Ref attachment when clash detection mode causes a clash crash.

    2. Seed file needs to have SWA with a UOR of 1000/mm or there will be lots of false clashes.

  • Hi Paul et al,

    It would be good to look at enhancing Aecosim to allow markups to be generated and managed internally. Seems like an easy win.

    Clash detection is a major workflow for anyone required to deliver BIM deliverables. Any help from Bentley would be welcome.

    SR?

    Regards

    Dominic
  • HI Ian,


    the clash detection feature in aecosim is there for a designer to check their own work as part of due diligence and good practice. Since this is being carried out in live files or files that can be activated relatively easily, any necessary changes can be made quickly before it is presented to any formal design review process.
    The navigator workflow is designed for formal review processes where audit trails are required. The markups are stored in an overlay file ( not the i-model) this the facilitates periodic reviews and a new i model is generated , replacing the previous version and the clash is re run. any resolved clashes will be trapped as will persistent and new clashes . This is the intended workflow for iterative review.

    rgds
    Brenden

    Brenden Roche

    Applications Engineer

    Bentley Systems, Manchester UK


    This is a test

Reply
  • HI Ian,


    the clash detection feature in aecosim is there for a designer to check their own work as part of due diligence and good practice. Since this is being carried out in live files or files that can be activated relatively easily, any necessary changes can be made quickly before it is presented to any formal design review process.
    The navigator workflow is designed for formal review processes where audit trails are required. The markups are stored in an overlay file ( not the i-model) this the facilitates periodic reviews and a new i model is generated , replacing the previous version and the clash is re run. any resolved clashes will be trapped as will persistent and new clashes . This is the intended workflow for iterative review.

    rgds
    Brenden

    Brenden Roche

    Applications Engineer

    Bentley Systems, Manchester UK


    This is a test

Children
No Data