In this article, we will see the best practices and tips to configure your issue library on our Finalcad One platform.
Finalcad is first and foremost a communications tool. It is essential to configure your project clearly, explicitly, and simply to facilitate fluid communications between the different companies working at your site.
When creating an observation, you need to configure three types of elements:
- The trades at your site
- The issue types (a list of standard defects)
You can also assign a company to resolve the observation.
Let’s look at the differences between these elements and the best practices for an optimal library.
Note that a standard library is already available by default in all FC One projects.
- Understanding issue types (or issue example)
- Differentiating between an issue type and a comment
- Limiting the number of issue types
- Limit editing rights to 1 or 2 users
1. Understanding issue types (or issue example)
An issue type may be compared to a situation that needs to be dealt with, a defect in the works. Issue types will be recorded in the issue library. They allow the user to select the defect directly in the list without needing to type it in. This saves time at the site and allows the user to focus on added-value activities instead.
The list of issue types is specific to each trade. Standard defects are different, from painting to plumbing.
Here are some examples of typical issues:
- “Repainting second coat” for the painters
- “Removing the valve” for the plumbers
- “Replacing the fixture” for the lighting crew
We suggest formulating the issues using an action word and the designated term for the object in question. This will make the defect to be corrected clearly identifiable.
After selecting the issue type, the issue will be created in your project and you can then add photos or comments in the activity flow.
2. Differentiating between an issue type and a comment
Issue types will allow you to pre-define a list of standard issues from the most common issues in each trade. When a user wants to create a new issue, they just need to choose from the list (step 4 on the picture below).
Each issue type list is independent and specific to each company. The “Plumbing” list will be different from the “Framing” list.
On the other hand, a comment is a more detailed description of the issue completed directly by the user. It will not be added to the issue type list and must be manually completed each time an issue is created.
Photos may accompany the comment. The number of comments per issue is unlimited.
3. Limiting the number of issue types
In order to facilitate issue creation, best practice consists of limiting the list of issue types per company/trade pair to 20 entries maximum.
This ensures the list is sufficiently exhaustive without being too long. For example, it’s often not necessary to state the location of the issue. The location will be indicated by the mark on the blueprint.
A few examples:
Paint to be redone
Streak to be cleaned up
Streaks to clean up
Streak to be cleaned up
4. Limit editing rights to 1 or 2 users
Restricting editing will help you control and maintain fluid communication between the different stakeholders. The ability to edit the library allows each user to add, delete, or modify the companies and their associated issue types.
The more users are allowed to add issue types, the greater the risk of getting a confusing, unusable issue library.
In order to harmonize and analyze the data of your project, we, therefore, advise you to restrict this option to 1 or 2 users in charge of supervising the consistency of the list.
Library editing rights are available to users who have at least one of the following rights:
- Organization administrator
- Project Administrator
- Project Editor
To change rights or add new members, see this article.
Please sign in to leave a comment.