<< Click to Display Table of Contents >> Example of user defined document codes |
In this topic, a complete example of user defined document codes is discussed in detail.
As has already been explained, you can define an arbitrary number of arbitrary complex document code trees.
In the full implementation of IEC1355, which is used in the Demo IEC1355 English project, three document code trees are used to define the document type. Please refer to the IEC1355 implementations topic for a detailed description of that.
The example of user defined document codes that is discussed here, is an extension of the full IEC1355 implementation.
1.Document kinds, like "circuit diagram" or "cabinet layout", are defined using the same document codes as in the full IEC1355 implementation. Three document code trees are used for that.
2.A fourth document code is added in the example, to define the functional location within a plant structure. The plant structure has four levels. In principle you can handle any number of levels, but a practical limitation to 9 is currently valid. If needed an extension can be made.
In the example, a compete implementation of a function oriented document code tree that can be used in combination with IEC1355 Document kind Classification Codes, with links to title field and all other project parameter settings that are needed, has been created as an example of the flexibility and usefulness of document codes.
•A sample plant structure is used as foundation for the example. In the Sample plant structure sub-topic, that structure is described.
•A complete set of document codes for the sample plant structure are described in the Document codes for the sample sub-topic.
•Together with the document codes themselves, the file name composition constitutes the very foundation of any document code implementation. In the File name composition sub-topic, you will find a detailed description for the example.
•In this implementation, document codes are used partly to define document kinds according to IEC1355, partly to define a position in the plant structure. Both affects the file names. The position in the plant structure also affects the function oriented reference designation in the upper left corner of the drawing frame, which defines the default for all symbols within a drawing sheet. That link is described in the Title field links sub-topic.
•Sheet numbering is made with respect to both plant position and document kind, which results in multiple drawing sheets both within the same position in the plant structure but of different document kinds, and of the same document kind but within the different positions in the plant structure, to share the same sheet number. In other words, to make a cross-reference unique and thereby unambiguous, it must contain information of both the function designation ("plant") and document kind, besides sheet number and possibly position within the sheet. A detailed discussion of sheet numbering and cross-references in the example is found in the Sheet numbering and cross-references sub-topic.
•Finally, practical examples of the use of the implementation are described in a sub-topic named Using the example.