Agreed, the Document Numbering Syntax option is covered.
However, take the following example:

A normal FACILITY document has the number PLANT-BUILDING-SEQUENCENUMBER.
However a FACILITY document with the disicipline Loop Diagram has PLANT-BUILDING-INSTRUMENT_TYPE-INSTRUMENT_NUMBER-SEQUENCENUMBER.

How can I make INSTRUMENT_TYPE and INSTRUMENT_NUMBER visible AND required for FACILITY documents with the discipline of Loop Diagrams, but not for other disciplines where the values are irrelevant?

Also, how can I give one FACILITY document one list of Disciplines as reference data, but give another FACILITY document a different list of Discipline? Our customer has one list for FACILITY documents, another for P&IDs, and another for Loop Diagrams.

This still requires us to have multiple document types.

The Document Types for FACILITY documents and PROJECT documents already exist in the default configuration.

The additional requirement to feed document numbering per document classification is also standard available with the Document Number Syntax for the Document Type - Discipline - Classification.

There are a number of reasons you may need to split this out to multiple document types.

Currently we are working with a customer that requires the ability to create have each of their drawings go on either an APPROVAL workflow and go to MASTERS, or have no review/approval and remain in the PROJECT without the option of releasing to MASTERS.

Additionally they have properties that feed into document numbering that need to be mandatory on some documents (such as Instrumentation Type on Loop Diagrams) but are not valid on other document types like P&IDs therefore each of these instances need a new distinct document type.

Also they have different reference data, for different document types. For example their P&IDs and LOOPs and Design Documents all have different Discipline/Classification values which can only be achieved with distinct document types.

These factors combined can lead to requiring significantly more document types than we would ideally like and therefore lead to additional effort when configuring templates.

Hi Nick,

I would like to understand this requirement a bit more. What is the reason to use 4 different document types for a drawing?

Kind regards,

Coen Vromans