Pages

Tracking DCRs in the Model

As I've mentioned before, Tocci issues DCRs instead of RFIs in many cases.

Up until recently (well, today), we haven't been doing a great job of tracking them. They normally consist of a sheet created in Revit and a list created in Excel. The list is hard to manage unless you're familiar with the project, and it requires duplication of information input.

Going forward, we won't have that problem:

I have created an Generic Object in Revit (made of invisible lines), that uses Shared Parameters (such as Date Issued; Issue Description; Suggested Resolution) to facilitate the documentation of DCRs. Basically, I place the DCR object in a view, drag the view to a sheet and tag the DCR object using a modified Generic Object tag. The tag is based on the Shared Parameters, so the required information automatically populates.

To issue the DCR, I will still have to print the sheet to PDF and then email it to the designer; however, I can log their response in Revit, in the DCR object.

And of course, since the DCR object is a Generic Object, I can schedule it - exporting it to Excel for the list as needed.

I guess it's a little extra work, but it's worth it to have the information coordinated and organized so well!

2 comments:

Eric said...

That's a great idea. can you post a picture of what this looks like?

Laura Handler said...

Well - the actual DCR object doesn't really 'look like' anything - it's made of invisible lines. We are talking about making some kind of 'beacon' object, so that people can areas in question as they walk-through the model.
There is definitely value to a visible DCR. But before I do that, I want to play around with how we should control the visibility of the objects. We won't want to see them all the time and we will definitely want to isolate them at times.