IEC 62023:2011 pdf – Structuring of technical information and documentation
IEC 62023:2011 pdf – Structuring of technical information and documentation.
• a part listing the constituents of the object (object list body).
Annex A shows an example of a main document containing these parts.
For the administrative part, see IEC 82045-1:2001 and IEC 82045-2:2004 dealing with document management.
5.2.2 Document part containing complementary documents This part shall contain a list of the complementary documents.
The part should be prepared in the form of a document list body, in which the document list items specify documents by means of essential metadata for the documents in order to make them unambiguously identified and traceable.
The following metadata Is mandatory:
The following metadala are optional:
• language code
• revision index
• document kind code
• document kind
These metadata are further specified in IEC 82045-2:2004, from which the metadata identifiers shown within angle brackets (< >) have been taken.
5.2.3 Document part containing characteristic properties
This part shall contain a specification or description of the object by means of its characteristic properties.
The part should be prepared in the form of a property list body in which the properties are specified by means of essential metadata for the properties in order to make them unambiguously identified and traceable. Use should preferably be made of relevant data element type definitions in international standards such as IEC 61360 and ISO 13584.
The values of the properties are normally associated with a specific life cycle phase of the oblect, for example as supplied, i.e. the property values as manufactured and supplied to the customer.
if values associated with several life cycle phases are supplied, the properties shall be individually qualified. For further information, see IEC/PAS 62569.1. See also example in Annex A.
5.2.4 Document pert containing constituent objects
This document part shall contain a list of the sub-objects In accordance with the chosen aspect.
The part should be prepared in the form of an ‘object list body”, in which the list items specify sub-objects by means of essential metadata for the sub-objects in order to make them unambiguously identified and traceable. For further information, see IEC 62027.
The method to include this document part in the main document makes it possible to trace the sub-ordinate objects more easily than in any of the other methods, and therefore recommended.
A main document can be used to specify an object Iron, many aspects by inclusion of one object list body for each relevant aspect. How this can be done is illustrated in the Annex A.
5.3 RelatIonship between main document and complementary documents
5.3.1 Main document
As a consequence of 5.2, main documents are commonly based on the following document kinds:
• single document. e.g. component drawing, In which the property list body Is predominant. This document kind is especially used for purchased components, specified by means of a list of requested characteristic properties, sometimes supplemented by a textual description or an Illustration;
• object list, see Figure 4b). In which the object list body Is predominant. For more Information on object lists, including parts lists, see IEC 62027:–: or
• list of documents, see Figure 4c). In which the document list body is predominant. The scope of such a list Is limited to the actual object.
NOTE Documents ot the above krnds are not always main documents, The requirements with reçard to idenlilication and reterencing to the complementary documents have IC be lull iiled as weli.
A main document may also lake the form of a single composite document containing the whole set ot information about the technical object concerned (see Figure 4a).
The opposite to that Is the List of documents, with its scope limited to the actual object, and listing all the documents that contain actual information, including the parts list document (see Figure 4c).
5.3.2 Complementary documents
The complementary documents for an object are usually many and of different document kinds. The type of object determines which document kinds need to be used.