Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
Now we can add our own custom attributes for Issues. We also need the same methodology for RFI.
As an example: we want to categorize our RFI meaning that when creating a RFI the user can choose a RFI type and subtype. Another example is that we want to add an attribute to define the priority of the RFI (low, medium, high).
Hi Johan - We have a project to introduce several additional attributes, including Cost impact, schedule impact, category, priority, and spec section. We are standardizing these field because (1) these fields cover 90% of the requests we get, and (2) we want this information to feed into our analytics in a consistent way (as opposed to custom fields).
We do not intend to introduce Type and subtype for RFIs. I am curious as to what is the workflow you are trying to achieve.
(Custom) Type and subtype fields are important to make a distinction between the RFI's. We need them to filter them in the RFI list, to generate reports and so on.
Examples:
-Phase related usage: to make a distinction between design RFI's, preconstruction RFI's and RFI's during construction.
-Discipline related usage: to make a disctinction between Architectural, engineering and construction RFI's
-Project management related usage: to make a distinction between material related RFI's, cost related RFI's, ...
I agree this is a must for Type, sub-type, and root-cause. All of the other systems in the market have this and it allows us to gather more data intelligence. This is a must request.
I agree we need this Custom RFI Category field to differentiate pre-construction RFI's from Construction RFI's. We are working on a design-build where this distinction is crucial to separating costly items to their correct phase.
I can not agree more that we need custom attributes. Where I do understand you need to lock things down for data analysis I would hope it is possible to add additional attributes for sorting purposes that might need to be understandably excluded from the analytics. We really need to be able to categorize and sort RFI's like we would issues. The RFI is a very flexible means of communication. It would actually make a good means of document review since the review cycles are locked in to only certain reviewers and a time limit. Beyond just having more ability to catagorize RFI's in general we could use the tool for some types of reviews and be able to filter out RFI's for document reviews vs those from contractors, or even contractor vs external engineering or client RFI's.
I agree @johan.cantryn it would also be nice if we could set custom fields as a "required" field. Right now, we have custom fields that we need to have filled out and time and time again they aren't because people aren't prompted to fill it out. It's causing us headaches.
