Revit Architecture Forum
Welcome to Autodesk’s Revit Architecture Forums. Share your knowledge, ask questions, and explore popular Revit Architecture topics.
abbrechen
Suchergebnisse werden angezeigt für 
Anzeigen  nur  | Stattdessen suchen nach 
Meintest du: 

Phase controls don't work when the new/demo/temp is put on hold or there are overlapping/concurrent works

3 ANTWORTEN 3
Antworten
Nachricht 1 von 4
Anonymous
535 Aufrufe, 3 Antworten

Phase controls don't work when the new/demo/temp is put on hold or there are overlapping/concurrent works

Phases can't be re-ordered or made inactive/active...

Long term facility maintenance requires many work orders over time, but may get put on hold or even dropped later.  So defining the new, demo, and temp by phase is inadequate.  Is there another workflow?  I know I can do new work in separate file with existing linked...then bind the new to the existing later.  How would you handle possible demolition and temporary works associated with such a work order?  Parameters identifying something as demo or temp and custom view filters?

Thanks.

Beschriftungen (3)
3 ANTWORTEN 3
Nachricht 2 von 4
ToanDN
als Antwort auf: Anonymous

If you want to shuffle phases freely then put them in different worksets so that you can close/ turn off/ create view filters from worksets.

Nachricht 3 von 4
Anonymous
als Antwort auf: Anonymous

Thanks.  I've got to think on this.  I've been using worksets to further group building systems...worksets for each discipline.  Not tied at the hip though. 

So within a workset, we'd define new, demo and temp.  Filters would control how they look and whether they are displayed.  current phase controls wouldn't work here as this is independent of Revit's phase management.  Showing other workset stuff classified as new, demo or temp...hmm.   Still seems to require some mechanism to identify something as demo or temp...and everything else is new (do I still need new parameters regardless)....if work is in another workset, then the filter would show it as past work or future work.  Not so clean I'm thinking as I'd have to declutter the file of demolished and temporary works over time.  If they have parameters to mark them as demo or temp to work with filters anyway...do I even need the worksets.  I suppose I could parameters to everything...checkboxes in ID for Existing, Demolition, Temporary.  I could prep run a script to check the box for all elements as Existing.  Then in new work I can mark what is demolished or temp...then when future change is initiated in the files I could run a script to purge out demolished and prior temporary items.  seems like a lot.

Nachricht 4 von 4
ToanDN
als Antwort auf: Anonymous

Yes you can create a parameter for phase identification and use it to create filter.  Using worksets is just another way and I find it has some advantages such as you can close or turn off worksets via its own settings more quickly without creating filters, or you can delete an entire workset without having to delete every element in it (great for archiving a portion of your model to another file).  There are more work than using the native Phasing but still less than using an user parameter.

 

Sure there are always pros saying you should never use worksets to control visibility so it is entirely up to you.  I personally don't buy that argument.

 

Sie finden nicht, was Sie suchen? Fragen Sie die Community oder teilen Sie Ihr Wissen mit anderen.

In Foren veröffentlichen  

Autodesk Design & Make Report