Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
I agree. if the clash testing functions in 360 Glue are to compete with the same functions in Navisworks, they will need to export reports as well as other updates to the configuration functions containing more detail. Clash tests, viewpoints, markups from Navisworks should flow into the 360 Glue tools with the model and the reverse as well.
There needs to be the freedom to create clashing, views and markups in either platform depending on the skillset of the user and availability of platform.
Once in a web service long time ago, there was an idea... that nobody listened to... I gave up this forum way back, looks like its not getting any better. I´m not asking that they implement anything, but at least reply & keep the discussion going.
Once the data was more free, but now it cannot roam as far or as well. The analytics are wonderful but there is more we need to do.
in the Old Days, sure we had to travel to different systems to accomplish our tasks. Glue was in one quadrant, Field in another. Team was deep in the center and Docs was a mysterious system far out at the edge.
i once traveled with one who did the Glue - Field - Docs run in a 14 hrs.....
For documentation purposes, clash report is very important. BIM 360 workflow in Model Coordination module is flawed. The items in the Docs Issues is useless - it only shows 1 link model which is not very helpful to understand the clash.
seriously, data that is locked in a container is not useful. if the NextGen platform is built on a goal of collaboration; then make it collaborative .. beyond itself.
The export feature is much needed in this world, clients are more and more requiring reports indicating not only that clash detection was thoroughly ran on the models, but also that all discovered clashes are resolved. It's difficult to pitch this much better method without the ability to export those reports. Please get this feature in the pipeline.
McCoy87 makes a good point. Clients beyond government entities are starting to request broader forms of output documentation so export functions will become the go/no go pivot for this platform very soon.
I've just raised this with our customer success manager and support at Autodesk and had no idea these were all known issues already and have been for what is quite clearly an eternity. It's disappointing and no wonder we're being encouraged away from B360 so much, it does some things wonderfully but then the basics are just not there at all, it needs to keep up with industry needs.
The ability to run interference checking in BIM360 is an obvious progression. Only being able to make a report from identified issues isn't even that bad. But having to manually create an "issue" for each individual clash is a real pain.
A large project may have hundreds if not thousands of clashes early on. The project I'm currently testing on has over 2500 clashes currently and I don't even have all the scenarios I have in Navisworks setup yet. That means you almost have to have some dedicated to identifying and assigning Issues. that's not going to happen.... there needs to be a way to create issues of all clashes, or at least groups of clashes, so they can be selected in groups and assigned to team members.
