Applies to: - All Verticals
New Feature / Problem:
We really need to be able to "lock" revision clouds to a specific cell in a schedule.
Currently the cloud stays fixed at the same spot on the sheet, even if rows or columns are later added to the schedule, causing the cloud to be highlighting the wrong cell.
Why do you need this Feature / Why is it a Problem:
One of the main sales pitch´s for Revit is: "keep information better coordinated, and deliver more efficiently" - While having to manually keep track of the clouds are neither coordinated or efficient. It takes up too much time, and the risk of making human mistakes is huge.
Workflow:
Needed each time a revision is added to a sheet with a schedule on it, and there has been added components / rows to the schedule.
Only known workarounds is to cloud the entire schedule...
or not clouding schedules at all...
or to consequently turn of the Cloud and Tags for older revisions - If permitted by project managers, clients, etc.
Benefits:
Less human coordination, and less risk of errors in the manufactured building components.
Attachment comments:
And just to elaborate a little, here´s a picture of one of the scenarios - At best the Revision B would be confusing, and in worst case the doors are manufactured in the wrong color.
New Feature / Problem:
We really need to be able to "lock" revision clouds to a specific cell in a schedule.
Currently the cloud stays fixed at the same spot on the sheet, even if rows or columns are later added to the schedule, causing the cloud to be highlighting the wrong cell.
Why do you need this Feature / Why is it a Problem:
One of the main sales pitch´s for Revit is: "keep information better coordinated, and deliver more efficiently" - While having to manually keep track of the clouds are neither coordinated or efficient. It takes up too much time, and the risk of making human mistakes is huge.
Workflow:
Needed each time a revision is added to a sheet with a schedule on it, and there has been added components / rows to the schedule.
Only known workarounds is to cloud the entire schedule...
or not clouding schedules at all...
or to consequently turn of the Cloud and Tags for older revisions - If permitted by project managers, clients, etc.
Benefits:
Less human coordination, and less risk of errors in the manufactured building components.
Attachment comments:
And just to elaborate a little, here´s a picture of one of the scenarios - At best the Revision B would be confusing, and in worst case the doors are manufactured in the wrong color.
Attached Files
Comment