Need to be able to add the full project name to document numbers
Currently when I add the project number to a document numbering syntax, only the project ID section is used, not the full project folder name, including the project type code.
Project IDs are based on the building number, and a 3 digit sequnce that is manually entered. Therefore we will have the same project ID across multiple project types.
e.g. under AUTOMATION projects, the first project in building 04 would be 04-001. The project folder name is therefore AUTO-04-001.
Under the MANUFACTURING project type, the first building 04 project would be 001 and therefore the project folder name would be MFG-04-001 however, again the project ID would be 04-001.
This means when the documents end up MASTERS there is no way of knowing what project type the document related to, only that it cames from one of the projects with the 04-001 project ID.
-
Guest
- Mar 22 2021
- Already exists
Related ideas
I disagree that this already exists since the document number can only contain the Project ID not the full Project Name. However I also agree that putting project numbers into the document number, is not the optimal solution.
I am happy to go back and tell the customer that this is not possible in Cloud and that we need to reconsider their document numbering for this document type.
Attachments Open full size
I agree, digital transformation is not just about creating digital data document and data, it's also about changing the way you used to work in the paper based, file based era. I'm fine with project names in Project Type documents, however Facility Type documents only have facility and discipline classification information.
Attachments Open full size
I agree, using the project number in the document numbering is something we always advise against for these exact reasons. However they are trying to port across a numbering schema they've had in place for some 15 years and are not wanting to change. Although I have had this conversation with them, explaining why we generally advise against it, they are still looking to keep the numbering schema they are familiar with. However without making the Project Type code available either as an individual property, or making the Project Folder Name property available they are unable to correctly number their documents.
An additional confusion would come in since they are migrating 15 years worth of documents, with numbering they do not want to change, and do not want to have the migrated content in one numbering schema, and new content in another schema.
Attachments Open full size
Hi Nick,
This is an interesting way of document numbering. Let me try to understand what you try to achieve here.
For Facility Document Types we don't recommend to include Project Names or Project ID's to the Numbering Syntax. The reason is that Facility Documents will be released to As-Built Master document at a given time. Facility Documents usually have Facility and/or Classification information in the Naming Syntax.
For Project Document Types you might want use Project Name or Project ID in the Numbering Syntax, although this is not strictly necessary to be able find documents in a project, because the Project Name and Project ID is already stored as meta-data. Maybe you can extend the Project ID with the Project Type to create the requested Naming Syntax.
Another possibility would be to create the Naming Syntax with other available Document Properties i.e. Classification Code, Business Unit or Building Code.
Kind regards,
Coen Vromans
Attachments Open full size