Reporting an element's phase information

[LieuxArchitects]

Hi there, here is what I'd like to be able to accomplish. Does anyone know how to do this / if it's possible / what some workarounds might be?

For any given element (wall / door / window / floor / roof / etc), I'd like to be able to automate the following:

1) if "phase created" = EXISTING and "phase demolished" = NONE, tag element with "existing to remain"

2) if "phase created" = EXISTING and "phase demolished" = NEW WORK, tag element with "demolish existing"

3) if "phase created" = NEW WORK, tag element with "new"

If I'm willing to assign the note manually, I know I I can create a special text parameter for this purpose (or re-purpose one of the out-of-the-box parameters). This could even be done with a user keynote. What frustrates me is having to assign the appropriate note to each object manually when REVIT already has the phasing information.

Here's a thought that might lead to something.... but I havent been able to figure out how. If I set up a "demolition" or "proposed" plan view, the object graphics can be overridden based on essentially the same "IF-THEN" statements above. Is there a way to tag based on the object graphic override? Or some other way to output an object's phasing information?

any input appreciated!

Elisa

[Alfredo_Medina]

What is the usefulness of tagging elements in this way? This information is usually presented in drawings. One view can show the existing conditions, another view shows the elements to be demolished, and another view shows the proposed design, including the new elements. Revit can also create schedules for each phase. 

[LieuxArchitects]

While trying to answer this question, I realized that I should probably go with user keynotes. 

As to why I would want to do this, I'm trying to convince my office to switch to REVIT by showing as a first step that we can more or less duplicate the existing office standards, which involve a lot of annotation (some of it redundant). Also, not all demolition / new work scope is clear from the graphics alone. As two examples, if we remove the flooring  and subfloor throughout a given floor plate, while leaving the structure intact, that won't be clear in plan or elevation. If we remove and replace a window in an existing masonry opening, or replace a piece of mechanical equipment in the same location, that won't be sufficiently clear with graphics alone.

I was just trying to see how far I could take things in terms of automating the annotations. I was imagining some way to automatically concatenate a descriptive parameter (ie "floor finish" or "window" or "furnace") with a property somehow based on the created / demolished phases of the instance, which would result in automatic notes like:

"furnace, existing to remain" 

"floor finish to be removed"

"floor plate structure to remain"

"remove window" "masonry opening to remain" etc.

This would be very cool, and would prevent inconsistencies, but I realize that it won't cover salvaging, relocation, or replacement of objects in existing locations, etc.... so.... user keynotes it is! 

[Alfredo_Medina]

Yes, it has to be in another way. "Phase" is not on the list of available parameters that we can add to tags. Also, in schedules, "phase" is not an available field, but you can create a schedule of elements by phase. The method that you have suggested has the risk that is not automatic, it's just annotation. If the element changes phases, the annotation would need to be updated manually.

[ToanDN · Accepted solution]

• Create a Multi-category Schedule.  Add [Comments] fields.  Sort by [Comments].  Uncheck [Itemize every instance] box.  The result should be one single [Comments] cell.
• Set it to New Phase, Show Previous Only.  Type in [Comments] cell:  "Existing to remain"
• Set it to Show Demolition Only.  Type in [Comments] cell: "Existing to be demolished"
• Create a Multi-category tag family.  Add a label = [Any parameter describe the object  such as: Type Comments, Description, Assembly Code, etc...] + Comments (add prefix/suffix and format as needed so that the final tag to read:  e.g. Sliding Door: Existing to be demolished.
• Start tagging stuff in your project.
• Profit

Important:  Check the schedule regularly.  Make it the startup View so you will not miss any changed objects.

[LieuxArchitects]

thanks ToanDN, an excellent response.

[Alfredo_Medina]

Be aware that the advantage of Revit is the "bi-directionality", "one change anywhere is a change everywhere", not having to do so many manual updates as we have to do in other programs. As I commented above, any annotation about phase is not going to update automatically when the phase of the element changes. 

[LieuxArchitects]

hi Alfredo_Medina, thanks for your comments. Here is my frustration with them:

1) upon hearing my idea, you responded with a polite version of "why would anyone bother to do it that way".

2) when someone else offered a workaround idea, you went to the effort of pointing out the inherent downsides (which were already apparent) even though you had no better alternative to offer.

Posts like yours, which can be summarized in "your idea / method / office standards suck, just stop trying that", really frustrate me to no end. We're all here to share ways to make this tool (REVIT) more useful for us. That comes with acknowledging that we've all got slightly different needs, and that we're all going to use the tool a little differently. If "stop doing things that way" is truly the only thing you can think of offering.... simply don't post! 

[Alfredo_Medina]

What I am saying in my previous posts in this thread, is that any annotation that you add to an element indicating its phase, it's just annotation that will not update if the element changes to another phase, which creates the risk of indicating something in your drawings that is not correct. However, If the workaround provided is what you need, fine. I am just making the comment for your own benefit.

I think I always write here in a way that is respectful and polite. If you interpret that in another way, that is out of my control. 

[Ruben.CastroQLD4K]

Sorry, I'm late to the party. Is there still no solution for a Window tag info to change from Existing to New Construction automatically when we change the window's created phase from Existing to New Construction ??? If the answer is no, then Revit is the problem because that should be an option. 2cents-RC

[ToanDN]

---

@Ruben.CastroQLD4K wrote:

Sorry, I'm late to the party. Is there still no solution for a Window tag info to change from Existing to New Construction automatically when we change the window's created phase from Existing to New Construction ??? If the answer is no, then Revit is the problem because that should be an option. 2cents-RC

---

It can be done more easily now with a Dynamo script.

[timMGPWM]

Surely it is not difficult for Autodesk to make Phase Created and Phase Demolished to be available for tagging and to be available for use in formulae.  This would just seem logical.

[davidjimm]

Finally created a solution for this! We show both existing and new steel on many plans, and we used to have to model it by phase, and then go back and have 2 different tags for it. I decided I needed it to work with just one tag. This solution simply requires you to run the dynamo regularly.

I hope this helps all the other designers out there with the same problem!!

I'm posting this here and on the Dynamo forum. It's a big help for us.

With a combination of Dynamo and creating a custom tag family for beams and columns I was able to use one tag to mark both existing beams/cols(E) and new beams/columns. A real game changing for us. I will be happy to give any help on recreating this.
My first post so hopefully I do it correctly.
The dynamo code looks at the phase and if it’s existing it adds “(E)” to the value “Mark” on the member.
The tag then reads this value.
Of course, you can use any parameter of the member that is not in use. We weren’t using the “Mark” parameter.

https://forums.autodesk.com/t5/revit-api-forum/beam-and-column-tag-automatically-detect-existing-wit...