用Navisworks做碰撞必须知道的10件事
After 3 years and hundreds of clash meetings, I have compiled a list of the top 10 things every coordinator should know before starting out. The list is in reference to using Navisworks Clash Detective. In no particular order:1.Learn the software – Ever watched your grandmother try to check email? It’s like that watching you search for buttons. You just really want to take over the mouse.
2.Try appending all the new models before the meeting – Do not get me wrong. I love watching you get insertion points corrected and correct models inserted for an hour.
3.Review the clashes and isolate “REAL” issues ahead of time – Going through every single clash one by one is almost as fun as jamming a pen in my eye.
4.Know the design flaws – If the design is trying to jam 10,000 lbs into a 5,000 lb building, send it back.
5.Slow down to speed up – Meetings can be much more productive if issues are addressed with a progressive approach. Get the big items fixed first before sending everyone to work on the little items and generate more problems. Don’t be afraid to take your time to get it right the first time. You will save the time in the end.
6.Break the silence – The negotiation technique “Whoever speaks first loses” comes to mind. When solutions are not volunteered, push the meeting along and decide for them.
7.Assign responsibility, record it and hold accountable – Don’t make a clash report and say “Here ya go. See you next week.” Measureable tasks must be assigned to make progress
8.Maintain a viewpoint trail – Don’t overwrite the old viewpoints with every new report. Keep them in dated folders as a history. Not only does it create accountability, but it is encouraging to look back and see how far you’ve come.
9. Consider the end viewer - You should create and redline viewpoints so that someone who was not in the meeting would know what you are trying to show. I was there, and, sometimes, I still have no idea.
10.Break the tests up into digestable portions –“Duct vs Plumbing”, “Lights vs Sprinkler”, etc. “Everyone vs Everyone” is just depressing.
So, there’s my current list. A light hearted look at some real advice. What do you think? Any more to add?
click here to get more information 简单的网页翻译
3年后，数以百计的冲突会议,我汇编了一列顶端10东西每个协调员将知道在做.之前表关于使用欧特克成功收购冲突侦探.在任何特定的顺序:
1.学习软件�c源文件曾经看你的祖母希图检查电子邮件?它’s喜欢那看你搜索按键.你刚真想接管鼠标.1.学习软件�c源文件曾经看你的祖母希图检查电子邮件?它’s喜欢那看你搜索按键.你刚真想接管鼠标.
2.尝试附加所有新的模型前会议�c源文件你搞错了.我爱看你获得插入点纠正，正确的模型插入为一小时.2.尝试附加所有新的模型前会议�c源文件你搞错了.我爱看你获得插入点纠正，正确的模型插入为一小时.
3.回顾冲突，孤立“雷阿3.回顾冲突，孤立“真正”问题提前�c源文件经历每个单的冲突一个接一个几乎由于乐趣由于湮一枝笔在我的eye.L”问题提前�c源文件经历每个单的冲突一个接一个几乎由于乐趣由于湮一枝笔在我的眼睛.
4.知道设计缺憾�c源文件如果设计在希图干扰10,000英镑到一个5,000英镑建立,发送它回来.4.知道设计缺憾�c源文件如果设计在希图干扰10,000英镑到一个5,000英镑建立,发送它回来.
5.缓慢下至加快�c源文件会议能是更加生产如果问题被讲话同一个进步态度.获得大项目固定先在做每个人之前工作小项目，生成更多问题.唐’吨害怕慢慢来获得它你第一句说得对.你将保存时间最后.5.缓慢下至加快�c源文件会议能更加生产如果问题被讲话同一个进步态度.获得大项目固定第一在做每个人之前工作小项目，生成更多问题.唐’吨害怕慢慢来获得它你第一句说得对.你将保存时间最后.
6.打破沉默�c源文件谈判技术“无论谁先说失去”回忆起.当解不是志愿者,推会议沿，决定他们.6.打破沉默�c源文件谈判技术“无论谁先说失去”回忆起.当解不是志愿者,推会议沿，决定他们.
7.分配任务,记录它，保持有责任的�c源文件唐’吨使一个冲突调查报告和发言权“这里亚去.见你下week.”可衡量的任务必定指派进步7.分配任务,记录它，保持有责任的�c源文件唐’吨使一个冲突调查报告和发言权“这里亚去.见你下week.”可衡量的任务必定指派进步
8.保持一个主张线索�c源文件唐’吨覆盖旧主张同每个新报告.保持他们在迄今夹由于一个历史.不仅欺诈它制定责任,然而它在鼓励回顾，见多远你’ve来.8.保持一个主张线索�c源文件唐’吨覆盖旧主张同每个新报告.保持他们在迄今夹由于一个历史.不仅欺诈它制定责任,然而它在鼓励回顾，见多远你’ve来.
9.考虑结束观众-你将创建，红线主张以便某人谁不是在会议将知道你在希图什么显示.我那里,,有时,我还不知道.9.考虑结束观众-你将创建，红线主张以便某人谁不是在会议将知道你在希图什么显示.我那里,,有时,我还不知道.
10.打破测试起来到digestable一部分�c源文件“管比探测”,“光比洒水”,等等.“每个人比每个人”刚压抑.10.打破测试起来到digestable一部分�c源文件“管比探测”,“光比洒水”,等等.“每个人比每个人”刚压抑.
所以,有’s我的当前表.一盏灯心脏观一些真正的忠告.你怎么认为?任何更多加?所以,那里’s我的当前表.一盏灯心脏观一些真正的忠告.你怎么认为?任何更多加?
点击在这里显示软件包信息点击在这里显示软件包信息 感谢楼主！！辛苦了！！ 支持一下。谢谢精品。 请问大家！为什么没有人回贴的呢？？？ 真是高手啊。。发的帖子全都是英文的 辛苦啦 软件翻译的？ 术语 ？ 不易啊 {:smile:}
页:
[1]