10 CAD Management Problems You May Not Know You Have
Most CAD Managers have a good handle on their environment. Most have a good “feel” for what shape their files are in. Most have a positive perspective on things going well.
But what about the things that you may not know about. What about those hidden things that pop up at the most inopportune times. What is happening that you don’t know about…
By keeping your radar tuned into the things that you may overlook, you can find and fix some of the unspoken troubles that may come up. Stay on your toes and don’t let smooth sailing lull you into a sense of “everything is alright”. There may be an iceberg just under the surface looming on the horizon.
Click on the links below to read the list… in two parts…
Ten CAD Management Problems – the First Five
Ten CAD Management Problems – The Second Five
I have been waiting for this a long time…
From the Autodesk site
Upcoming Release of AutoCAD Revit Architecture Suite to Include AutoCAD Architecture
The latest release of AutoCAD® Revit® Architecture Suite software is scheduled for shipping on September 15. This release expands the software applications that comprise the suite to include AutoCAD® 2009, AutoCAD® Architecture 2009, and Revit® Architecture 2009 under a single license. There are no changes to the features and functionality in the products themselves.
Autodesk is including AutoCAD Architecture 2009 software in the AutoCAD Revit Architecture Suite 2009 product to make it easier and more cost-effective for AutoCAD Architecture customers to transition to building information modeling (BIM) using Revit Architecture software.
As part of their Autodesk® Subscription benefits, AutoCAD Revit Architecture Suite 2009 subscription customers will automatically receive the release of AutoCAD Revit Architecture Suite 2009 that includes AutoCAD Architecture software when it becomes available. Customers who are not on subscription will not be entitled to this benefit and will need to purchase subscription to gain access to the new product offering.
AutoCAD Revit Architecture Suite is a Subscription Only product.
Chances are you already have a significant investment in AutoCAD® or AutoCAD® Architecture software, but you also want the competitive advantage of building information modeling (BIM). With AutoCAD® Revit® Architecture Suite software, migration is easy.
- Add a state-of-the-art BIM solution to your tried and true AutoCAD or AutoCAD Architecture software, and allow your project teams to choose the right tools for the job.
- Implement BIM using Revit® Architecture gradually, while not disrupting your existing AutoCAD or AutoCAD Architecture software projects.
- Reduce your license subscription fees by purchasing a single license that includes AutoCAD, AutoCAD Architecture, and Revit Architecture.
HELP ME DEVELOP MY CLASS FOR AUTODESK UNIVERSITY
I am putting together a survey of BIM Managers and BIM Support staff.
Do you have the title of BIM Manager, BIM Coordinator or anything with BIM in the title? Do you oversee your BIM software use at your firm? Do you coordinate BIM project efforts or standards?
I would like your help with a few short surveys about BIM Support and software use.
I will use the data collected to develop a class for Autodesk University that is focused on BIM Managers.
Here is the class outline:
BIM Manager – The Newest Position – BIM Manager, BIM Leader, BIM Coach, BIM Coordinator. Just some of the titles being handed out to those forward thinking BIM leaders. There is a new position that is developing as BIM progresses. It is one dedicated to overseeing BIM projects. Is it different that CAD Manager? Is it the same? What duties should a BIM Manager be doing? What are the same? Is this a short term evolution or is the CAD Manager being replaced? Discover what it takes to be a BIM Manager.
Want to participate in the surveys?
– join my BIM Manager Group on Google
– or just send me an email asking to be involved.
Take our Poll on the right hand side of the home page…
Often we forget to train ourselves. Staying ahead of the curve is not easy. Have you forgotten to keep your skills current?
Standards are a compilation of rules…
But some things need to float free for a while until you have enough information to make a call on the best practice. When a new tool or feature presents itself, let users fiddle with it until they figure out some optional ways of using it. Let them play around and try it out. Work it through a few files or even a project or two.
Once you have a few people who have tried a few ways at doing one thing, get them together for a discussion. Ask them what method should be used by all. Let them defend or sell their way. Let them knock off the rough edges and come away with a unified method. Have them all test it out and then if they all agree – put it into the standard.
There will be a time when no rule applies to new tools. Embrace that time and use it to your firms advantage.
If you have a rule for most things – people will expect a rule for everything.
I am surprised from time to time when I tell people “do whatever you want” when asked how something should be dne to standard. I say this because the standard does not cover the subject in question. My perspective is that when the standard is silent, you can do whatever you want. Understanding that you need to use common sense and do the best you can to figure out what others would do in the same situation. When you do this, then others can understand your methods and techniques. They make sense.
When asked if I want to make a rule, I take the perspective that you should make a rule “only if needed”.
“Only when needed” for me means that if there is not a real problem with people doing different things, then don’t worry about making a rule for it. Making people do thing in a specific way takes more time than just doing what they want.
This does not mean that you just let users do whatever they want on everything. You made quite a few rules in your standard. They have to follow those. But there must be some limit to what you create rules for. You cannot make a rule for every last thing that will come up.
Some things need to be free flowing. Or at least free flowing for a while until you have enough information to make a rule…
More coming on this…
I was interviewed on an AU Beat podcast and it was posted today. It is all about what AUGI is doing at Autodesk University and beyond.
Give a listen…
AU Beat: AUGI…It’s More Than the Beer Bust!
From the site…
Mark Kiker, president of Autodesk User Group International (AUGI), explains that AUGI is much more than the beer bust at AU. Do you know about all the benefits of this free membership? How about in-person and online networking, AUGI Cad Camp, and much, much more…. [7:27 mins]
For more information, visit the AUGI website.
I have long wanted Autodesk to suggest best practices…
Kyle Bernhardt of Autodesk wrote on his blog… under the heading of Required reading
Revit Platform 2009 Technical Notes – Direct from Autodesk
“it is a comprehensive paper that discusses best practices for optimal performance and productivity within the Revit 2009 family of products. It is required reading for all Revit users interested to know this information straight from the Product Teams themselves.
It is the result of a comprehensive effort among the Designers, Developers, Quality Assurance, Consulting, Customer Success Engineers, and Product Managers, and we are excited to get this information straight to users.”
Some major topics that are discussed:
- Project Structuring
- Worksharing
- Linked Files
- Hardware Optimization
- Large Model Performance
He list where you can get it – but it used to be a subscription only location. Now it is available to everyone.
Click here to see… Revit Platform 2009 Technical Notes
For more info – go to the AUGI thread that started this whole thing…
I came up with another one…
Add Time to the four T’s and you get success. What appears to be failures or stuttering starts end up being success when you add time.
How does this work? What make bad things into good? What allows the planning of yesterday become the foundation of tomorrow and the expansion into the future?
Time – just give it some time…
Give Tools time to mature
New and exciting tools are being developed, but they cannot do everything you want them to do. None of them can. Because as soon as they do – you want them to do more. But look backwards and see that the troubles of yesterday are being addressed by the tools today. Just give the developers time (and let them know what to work on) and they will mature the tools they offer.
Give Talent time to play
Talented people need tools and they need time to play with them. They need some space to fail and room to experiment. Allow those who are the best and brightest to just fiddle with new things, try out new software and push the limits of your efforts. When you do this, they will not always succeed. But they will learn and find new approaches to old problems. They will help you get past the hurdles of Tools that are not mature yet.
Give Technology time to catch up
When Talented people push technology they attempt things that the developers never thought they would try. I have heard developers tell me that they never thought users would try to do what they are trying to do. I have seen the light bulbs turn on in their minds as users mention options that they never thought of before. This means that the real world of design is always setting the bar higher and the developers are playing catch up. So give them some time and they usually get the technology focused on your needs.
Give Training time to sink in
Finishing a class does not make someone an expert. It begins the path to expertise, but the job is not completed. Add time to training and you end up with a ever increasing level of users who can operate on their own. Sometimes management thinks that when training is done, the users are up to speed and can do everything needed. But give them a little time and some project work and they will develop into advanced users.
Loading ...