I am inviting you to a crazy brainstorming session Monday, the 1st of February, in Dallas.
If you would answer YES to any of these questions, please meet me at 10:30 am in Ballroom C1 at SOLIDWORKS World.
- Do you drink a lot of coffee waiting for your assemblies to load?
- Have you seen rebuild icons glued on components in the feature tree?
- Do you need to simplify any complex geometry fast, without loosing visual details?
- Do you participate in design reviews?
- Do you need to visually locate and open component files fast?
- Do you have many configurations in your assemblies?
- Do you need to protect your intellectual property (IP) when sending files to your customers and suppliers (give them only what they need)?
Session ID: 1682
Session Title: Best Practices for Large Assembly Management
in SOLIDWORKS 2016
Session Category: CREATE - Modeling Essentials
Session Type: Breakout Session
Session Level: Intermediate
Session Length: 90 Minutes
Session Description: Did you know that SOLIDWORKS has to go through 5 (five) distinct phases when opening an assembly? The opening time is impacted by specific factors in each phase. Attend this presentation and learn about all the tools and techniques for predicting, troubleshooting and drastically reducing slowdowns.
Attendee Benefits: SOLIDWORKS users who applied the unique set of best practices included in this presentation reported time savings of 50-90% when working with large assemblies. If you have read all the relevant books and forum threads and still are not 100% satisfied with your performance, attend this session.
I'm sorry, but I find the response to S. Casale from SW Tech Support to be insulting to him and to all of us users!
Here is an acknowledged issue by Tech Support themselves, yet their instruction is for the user to take a separate action to go through their VAR and report it as a bug??????!!!!!!! This is unnecessary effort and delay, and sometimes the VAR doesn't follow through.
I think there should be a mechanism for Tech Support to elevate/transfer this issue and get it reported as a bug on behalf of the the user, Scott Casale, in this case. This would be: a) faster and a more accurate way to get the bug reported, b) carry the weight of pre-verification by an accredited source (Tech Support) that it actually is a bug, and c) be the courteous and respectful thing to do for the customer. We are busy! Scott went to the trouble to use the inconvenient ER system and now he is being told to hang up and call back asking for a different extension. Come on! Tech Support should just transfer the call!
I'm tagging you, Matthew Lorono, in this post since you are looking for ways to improve the problem reporting system. Do you agree that my suggestion is reasonable and should be implemented ASAP?