I am new to Sheet Set Manager altogether. Can someone with experience please explain to me what the advantages of sheet set manager is and an example of when we would use it? Is it a system for a large project where a few members of staff can work on multiple drawings at the same time? Can someone please explain what Sheet set manager is for please?
Ross (The newbie lol)
At its most basic level, it serves as a drawing organization tool. You can open the SSM and see your sheets in order, with a logical name - regardless of where the actual DWG files are stored or named.
The next step is using this to publish the set. We have sets anywhere from 10 to 200 sheets, and they all can be published with two clicks. If you've ever had to open 20, 40, 80, 190 drawings to plot them, you will realize the value of the feature alone.
The next step is creating fields in your drawings that link to the SSM. Things like the sheet number, sheet name, and anything else that changes on a per sheet basis. You can edit this information inside the SSM without opening each drawing. With a 3rd party tool, you can even do it on a machine without AutoCAD installed (i.e. an Admin could update sheet properties)
The next step is using the tools in SSM to link views to callouts. For example, you may have a callout on sheet 7 that says "See detail A-3 on sheet 68" - and then later on let's say you insert 10 new sheets in at sheet 60. Then sheet 68 becomes sheet 78. If you placed the callouts using SSM, they will be updated automatically to say "See detail A-3 on sheet 78"
Thanks to you both for your prompt replies and help.
I like the sheet set manager. But to be honest, I have to say, if you use it FULLY (and you don't necessarily have to) it certainly can change the entire way you draw... for better or worse. We implemented it here where I work (at my suggestion) and it changed everything, from our standard layering system to my job description. I think it is a change for the better but there are many here resistant to change who do not agree - in fact, they would emphatically disagree. Just sayin' - investigate this thoroughly so you get exactly what you want and nothing you don't. Best of luck to you, either way!
How does it help you with standard layering?
I personally am concerned for when we send files to either clients or consultants that there will be issues. I know you can remove the association, but it's just another stumbling block for them to complain about.
We use publish from the command line and a VB prorgam I coded for generating a sheet index, so those features really don't stand out for me, but I do like the organizational features such as labling the list with sheet titles. I just wish it could populate it from the drawings or at least use a template for standard type drawings.
When creating views, visibility becomes a huge issue, which we use layers to manipulate. We work in construction and one part of what we do is the curtainwall system, another part is the panel system - these systems integrate so we have some details that are used in more than one submittal and are fleshed out more in one submittal than the other. We used to get 2 different details of the same area (each submittal set created it's own)... now we use one model drawing (2D model) and each submittal creates it's own views with pertinent dimensions and notes turned on/ off. I realized our old layering system was rather complex without providing any functionality so we switched over so that each submittal gets its own layers and we have std layers that are "shared" for the basic geometry. I.e. we no longer have a dim layer (we never used it to manipulate objects - and objects can now be manipulated in ways other than with layers anyways).... sorry this is really confusing I know....
As far as sending drawings out, I have only done it once (we usually send pdfs) and it worked fine with etransmit.
I absolutely love the printing capabilities, it is so simple to print just details or elevations or a whole set with just a click and absolutely no searching...
Maybe we went about it wrong but it just opened up a huge can of worms... if i had known then what i know now, i never would have told anyone about it - not that it is not a good tool; it's just that people are difficult and don't like anything new, even if you end up with a better product.
Oh- and did i mention - it is not uncommon for it to take 1-2 minutes to place a view.... unacceptable in my mind.
If I can be of any assistance, please do not hesitate to reply!
Ok, so if I understand you correctly, it's not that you manage layers within the SSM, it's the view configuration you set for the viewports and then manage the view in SSM.
The printing I will aggree with since there is an extra step in publisher to browse for the drawings. With SSM you are looking at the drawings already and a published set is just a click away. Same for etransmit and archive.
One of my greatest concerns is management of the SSM. Like you, we have some people set in their ways and fail to recognize the necessity for increasing efficiency even for the sake of the company. My philosophy has always been "if the return is not greater than the effort, it's not worth it" and from what I can see, for our firm, SSM may barely be over that edge of being not worth it.
I am still going to research this to either debunk or validate my theory, but for now the jury is still out. If we decide to use Vault that will probably be a whole other variable to add into this equation...how well do they work together.
I apprecate your input and response.
well we used the SSM with full functionality, including views. You can use it at a lesser level, but it hardly seemed worth the effort.
You are right about Vault, it does have it's own limitations; we don't use it but i have heard the stories.
I read Heidi Hewett's sheet set manager stuff and found it helpful.
Good luck, I see you on these boards a lot, and probably will cross paths again!
I haven't used 2012 SSM, are there any enhancements from 2011? And now that 2013 is just around the corner, does anyone know if there are any changes for this release? I keep hoping for a printing feature or a export to .doc or .xls..
I changed jobs as many of us have, and my new company hasn't embraced SSM. Since I fully used it before, and know the advantages and dissadvantages of at least the 2011 version, I may be in a situation where I may want to encourage SSM use here if there are some worthy improvements, or there appears to be a push from our users to embrace it. I just feel that I would need to implement some STRONG standards with severe punishments (such as DON'T EVER CHANGE FILE NAMES, OR I SET YOU ON FIRE), and I would recommend a whole different approach to file naming standards, as well as SSM hierarchy, such as creating folders by company or jobsite instead of project number, then creating SSM for the job description and include projects under that, say.But when I contemplate this, The llittle angel on my shoulder reminds me of the original engineering premis; "Keep it simple, stupid"...
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register
Start with some of our most frequented solutions to get help installing your software.