we are in the process of starting to use constructs/view/sheets and i would like to know the pros and cons of putting annotation in a view file and the pros and cons for annonation in sheet files. the coworker that is helping me setup our cad standards thinks that putting all annotation in the view files is the way to go. work flow would be construct (line work only) then view files (with annotation) then sheet files (plotting only). he also wants to put all details, sections, elevations, construction notes, etc. in view files. my problem with this is we rarely have only one item on a sheet. a typical sheet will have mulitple plans, sections, details, and notes. if we have a sheet that has 5 views and we need to change text on all views we would have to open the sheet file then open up all views one at a time to make the changes. to me that seems like a lot of back and forth. what i would like to do is have a work flow of construct (line work only) then view files (with only plans and a composite model - no sections, elevation, details, or annotation), then sheet views (with annotation, sections, elevations, and details). i think that this i a easier/cleaner way of doing it. i would appreciated any thoughts on this.
with the coworkers way, i'm concerned that there will be so many views people will be confused with what do to with them. i was just thinking that the only views would be only the files that are constructs. i want this to be as easy as possible for users.My coworker and i are going to try doing a small job both ways and see what we think is the easiest way. i'm also curious as to how other company's go about doing this. thanks for that info. so far 1 vote for views with annotation.
IMO, due to the fact that a single construct can be used in many different ways.
1)Put no annotation at all in constructs.
2)Put all annotation and tags in views.
3)Place views on sheets with titles. Some cross-reference keying can be put on sheets and some notes that link views can be put on sheets but annotation on sheets should be strictly limited.
Related, consider having a "Project Data View" which picks up every current level/division in the project (not those involved in design options). Will be a visual geometric nightmare but you never need look at it!
Means all whole project schedules can use the "Schedule External Drawing" Yes option specifying that view as the target and you know it will pick up all project wide data. We have schedules on sheets but know that if something is in the "Project Data View" it will be counted.
Can then use object/classification or layer wildcards to filter results if needed and group by levels/ divisions if needed.