Business overview

This section provides a business level overview of this capability.

In PLCS documents are handled using the same basic principles applied to any other type of product, which includes the fundamental requirements of; identification of Documents, versioning of Documents, and the definition of Documents. These fundamental concepts are described in the capabilities C001: assigning_identifiers and C002: representing_parts.

However, Documents are distinguished from other products in the representation of Document structure and consituent parts. In addition, documents can be assigned to many items, such as parts, products, resources, activities, tasks and events.

Information model overview

This section provides an overview of the information model that supports this capability.

Information Model Overview

As a Document is a type of product, its revision control is managed in a similar way - through using the entity Document_version. Revision control allows the various Document_definitions associated with a Document_version to be distinguished between. The Document_version represents the minimum identification of a managed document under revision control for referencing purposes. A Document_definition may be either a Digital_document_definition or a Physical_document_definition. The former of these may contain a number of Digital_files, whereas the latter may refer to a number of Hardcopy components. Document_definitions or Files may also be identified as an item of an externally referenced source.

Figure 1 —  Document Information Model

EXAMPLE - a configuration controlled managed paper document such as a drawing would generally map to a usage of the entity 'Document', with a Document_version and a Physical_document_definition representating the view definition according to the 'document as a type of product' approach.

External File s in the PLCS Schema are identified through a File_location_identification (a type of External_item_identification). The supertype, External_source_identification, allows the source to be associated with either a Document_definition or a File (Digital_file or Hardcopy ) through the external_identification_item select type. Although an external File is normally managed independently of the system - and hence no revision control or any representation definitions of external File s, this can be achieved via the document_defintion referenced through the select type. In this manner, version identification may optionally be associated with an external File , but this is for information only and is not used for managed revision control.

Documents may be associated with product data in a specified role, to represent some relationship between a Document and other elements of product data. Constraints may also be specified on this association, in order to distinguish an applicable portion of an entire Document or File in the association. With 'Document as Product', additional entities are required to relate a managed document to other product data - see Document_assignment described later.

Representing Documents

In PLCS documents are handled using the same basic principles applied to any other type of product, which includes the fundamental requirements of; identification of Documents, versioning of Documents, and the definition of Documents. However, Documents are distinguished from other products in the representation of Document structure and consituent parts. In addition, documents can be assigned to many items, such as parts, products, resources, activities, tasks and events.

• identification - Document identification is handled in the same manner as that afforded to other products - as described within C001: assigning_identifiers.
• versioning - Document versioning is handled through the Document_version entity, in a similar manner afforded to other products - as described within C002: representing_parts;
• definition - Documents are defined separately from the entities for versioning and identification, through the Document_definition entity, in a similar manner afforded to the definitions of other products - as described within C002: representing_parts.

Document Identification

The concepts of base identification, version identification, and definition are structurally distinct in Documents. The general recommendations given for identification apply to the Document master, except where differences are noted.

Base Document identification is always associated with at least one Document_version. Multiple Document_versions of a base Document identification may be related together to represent Document_version history.

With Documents the Document_definition is used to define a view of a particular representation of a Document_version. A Document_version, however, does not have to have an associated Document_definition.

The Document_definition is used for the association of document properties (see later), to build Document structures, or to associate a Document_version (and hence a Document) with the set of constituent Files that may make it up.

Document_version identification without an associated Document_definition represents the minimum requirements for Document identification. However, it also includes the use of identification_assignment, classification_assignment and organization_or_person_assignment to uniquely identify the Document_version and Document that it refers to.

The steps to identification are described in the C001: assigning_identifiers capability.

Document

A Document is a type of Product used to identify documentation data that is under configuration change management.

Document_version

A Document_version is a type of Product_version. A Document_version identifies a particular version of a Document. It is a collector of the definitions of this revision of the Document.

Context Information

Life-cycle information should be provided (as it is for parts or other products to identify the development life-cycle stages), through a Document_definition (see below). However, when this is not provided, for a Document_version, (but the Document is assigned to a part or other product with a definition), the life-cycle stage of the part may be extrapolated as relevant to the Document.

Document_definition

A Document_definition is a representation of a Document_version in a particular format. Each Document_definition is either a Digital_document_definition or a Physical_document_definition. The Document_definition entity denotes the definition of a particular view of a representation of a Document_version. There may be more than one Document_definition associated with a single Document_version. The Document_definition is used for the association of document properties, to build Document structures, or to associate a Document with the set of constituent external File s that make it up. type).

The subtypes Digital_document_definition and Physical_document_definition distinguish between types of Documents and are used to associate a representation of a Document_version on one hand, with the set of constituent File s that make it up on the other. A version of a logical Document, which contains a shape model, may be represented in the native formats of different CAD systems.

Document Properties

The entity Document_definition supports property association and Document structure. The Document_definition may be associated to the property described in an Assigned_document_property through the described_element attribute. The attribute is a document_property_item select type (which is a subtype of the property_assignment_select type). This allows an instance of Digital_document_definition or Physical_document_definition to be associated to a Property. The process and mechanism of assigning proprties is described more fully in the C087: assigning_document_properties capability.

Document_assignment

A Document is assigned to a part or product (amongst others) through the Document_assignment entity. The Document_assignment may be used to relate the Document_definition to a part. A Document_assignment may be applied to an instance of Document, Document_definition, Document_version or File .

Digital_document_definition

A Digital_document_definition is a type of Document_definition. It identifies a collection of File s that are archived on an optical computer disc, magnetic, electronic storage, or a combination thereof. A Digital_document_definition may consist of one or many component Digital_files.

Physical_document_definition

A Physical_document_definition is a type of Document_definition. A Physical_document_definition may consist of one or many component Hardcopy File s. Paper plots of technical drawings, micro fiche, or paper documents such as calculations or test reports are examples of Physical_document_definition.

Type Classification

Type classification is provided through a combination of mechanisms in PLCS. Firstly, the model makes several explicit distinctions in the use of Digital_document_definition and Physical_document_definitions. Secondly, the Digital_file and Hardcopy concepts inherit an attribute named "contained_data_type" where the type of data contained in the file can be categorized (through reference data). Thirdly, reference data can be used to provide a classification of the Document.

More than one classification can be applied, hence a Document may be classed as a "packaging guide", a "technical packaging guide", and a "users packaging guide". Likewise, a Digital_file may be a "technical drawing" and a "detail drawing". Others may have a single or simpler set of classes defined.

Relationship Between Documents and Constituent Files

In PLCS, the Document_definition is used to represent a definition of a particular Document representation. There may be more than one representated definition associated with a Document_version. The Document_definition may be associated with the constituent File s that make it up. The association of constituent File s with the definition of a document representation is optional.

If a File is under configuration control, it should be represented as a constituent File (or component) of a Document_definition. In this case it is actually the managed Document that is under direct configuration control, the File is in this way indirectly under configuration management. A change to the File results in a change to the managed Document (i.e., a new version) - the changed File would be mapped as a constituent File (or component) of a definition of the new Document_version. A simple reference to a File alone is not configuration controlled; it is just an File reference to product data.

While managed revision control representing multiple versions and version history is not available for external File s, external File s may have an optional version identification providing a string labeling the version of the File .

Constituent files

One or more Files may be related to a Document_definition, allowing the association of the File occurrences making up the definition to be identified.

However, the actual identification of each instance of File is done using an instance of Identification_assignment. This is applied to the File using the template assigning_identification as defined within the capability C001: assigning_identifiers. The identification data should be provided in the context of a "Document identification code" (urn:plcs:rdl:std:Document identification code).

File

A File is a file stored on a computer system or in a stack of non-digital Documents. A File is either a Hardcopy or a Digital_file . A File may be specified as an external source through the external_identification_item select type.

Digital_file

A Digital_file is a type of File . A Digital_file contains computer interpretable data and is stored on an electronic device. A Digital_file may be a constituent of a Digital_document_definition.

Hardcopy

A Hardcopy is a type of File that represents a non-digital Document. For example, an actual stack of paper consisting of one or more sheets, on which some product data is written, printed or plotted.

External Documents

Document_definitions and/or their constituent File s may be identified externally. In the PLCS Schema these are identified by a simple External_source_identification to either a File or a Document_definition. The external File identified may be a Digital_file or a physical, 'Hardcopy ' File . The external Document_definition may be either a Digital_document_definition or a Physical_document_definition. As opposed to a managed 'Document, an external File is not managed by the system. However - there is a capability for managed revision control for a Document_definition which may or may not have constituent Digital_files or Hardcopy components.

An external File may simply be an external reference that may be associated with other product data. Document/File properties may be associated with an external File as with a managed Document. In the case where properties differ with different versions, the managed 'Document' approach is recommended.

Although a File can exist and be referenced independantly, if it is under configuration control, it should be represented as a constituent of a Document_definition view/representation. In this case, it is actually the managed Document that is under direct configuration control; the File is, in this way, indirectly under configuration control. A change to the File results in a change to the managed Document (i.e., a new version) - the changed File would be mapped as a constituent of a Document_definition of the new Document_version. A simple external reference alone is not configuration controlled, it is just an external File reference to product data.

While managed revision control representing multiple versions and version history is not available for external Files, Files identified as external may have an optional version identification providing a string labeling the version of the File itself.

Identification of an external source is achieved through the external_identification_item select type via the item attribute of the External_source_identification entity. If a File is identified, it may be a constituent of a Document_definition, thereby allowing an association of properties to the external File , or a type of Document_definition.

Figure 10 —  External Source Identification SubModel

External source identification

An External_source_identification is the identification of the source where an item, that is not fully represented in a population of instances of EXPRESS entity data types but is only referred to, or the components of such an item, can be found.

The Instance Model: EXPRESS entities and attributes

The instantiation of the EXPRESS entities and attributes used to support the requirements of External Source Identification are shown in the figure below.

Figure 11 —  External Source Identification Instance Diagram

Note - organization and identification assignment information has been removed from the figure above for the purposes of clarity.

Several subtypes of External_source_identification are provided to constrain the item to a specific type of File or Document_definition. All behave similarly to that of the External_source_identification, however, these subtypes are to be prefered over the more general External_source_identification as they are more explicit.

The External_item_identification_assignment entity is a general purpose entity which is provides contraints through it's subtypes. Where possible, a subtype should be used in preference to this entity.

External item identification

An External_item_identification is a type of External_source_identification that provides the identifier of an item in the context of an external source where it can be found.

The Instance Model: EXPRESS entities and attributes

The instantiation of the EXPRESS entities and attributes used to support the requirements of External Item Identification are shown in the figure below.

Figure 12 —  External Item Identification Instance Diagram

Note - the filename is provided within the same instance (#51, #52, #53), rather than implicitly as before. This method is prefered when the filename is known. This also requires less processing to retrieve the full path information.

File location identification

A File_location_identification is a type of External_item_identification that identifies the location of a File in an external storage system where it can be found.

Attribute Population

File_location_identification is a type of External_item_identification, hence it inherits all the attributes of it's supertype. There are no additional attributes for this entity.

NOTE    A File_location_identification entity restricts the type of items to be types of File . Hence Digital_file and Hardcopy are the only legal instances that can be referenced as items from an instance of File_location_identification .

The Instance Model: EXPRESS entities and attributes

The instantiation of the EXPRESS entities and attributes used to support the requirements of File Location Identification are shown in the figure below.

Figure 13 —  File Location Identification Instance Diagram

Note - organization and identification assignment information has been removed from the figure above for the purposes of clarity.

Document location identification

A Document_location_identificationis a type of External_source_identification that identifies the location of the components of a Document_definition in an external storage system where they can be found.

Attribute Population

Document_location_identificationis a type of External_source_identification, hence it inherits all the attributes of it's supertype. There are no additional attributes for this entity.

NOTE    The Document_location_identificationentity restricts the items that are allowed to be only of type Document_definition. Hence Digital_document_definition and Physical_document_definition are the only legal instances that can be referenced as items from an instance of Document_location_identification.

The Instance Model: EXPRESS entities and attributes

The instantiation of the EXPRESS entities and attributes used to support the requirements of Document location identification are shown in the figure below.

Figure 14 —  Document location identification Instance Diagram

NOTE    The instances of Document_location_identificationonly apply to types of Document_definitions, which explains why there are fewer than those (above) that apply to types of File - which are more numerous in this and the examples above.

Document and File Relationships

This section discusses relationships between File s, Documents and structure relationships between versions of managed Documents.

The PLCS Schema supports the definition of corresponding relationships between Document File instances via the entity File_relationship. The schema also supports the definition of document structure by defining relationships between the Document_definitions using the Document_definition_relationship entity. In addition, the schema supports the definition of relations between versions of a managed Document to model Document history using the Product_version_relationship entity.

Figure 15 —  File and Documemt Relationships SubModel

File_relationship

A File_relationship is a relationship between two instances of File . The semantics of the relationship are defined by the attributes relation_type and description of the entity Document_definition_relationship. The relation_type attribute of File_relationship defines the type of relationship between the two instances.

Attribute Population

The entity (File_relationship) and attributes (relation_type, description, relating_document_file and related_document_file) describe the different values that are expected to be populated for each attribute.

NOTE    The Document_definition_relationship entity ensures that the relating_document and the related_document are not the same.

The Instance Model: EXPRESS entities and attributes

The instantiation of the EXPRESS entities and attributes used to support the requirements of File_relationship are shown in the figure below.

Figure 16 —  File_relationship Instance Diagram

NOTE    The instances of File_relationship only apply to types of Document_definitions, which explains why there are fewer than those (above) that apply to types of File - which are more numerous in this and the examples above.

Document_definition_relationship

A Document_definition_relationship is a relationship between two instances of Document_definition. The semantics of the relationship are defined by the attributes relation_type and description of the entity relationship. The relation_type attribute defines the type of relationship between the two instances.

Attribute Population

The entity (Document_definition_relationship) and attributes (relation_type, description, relating_document_definition and related_document_definition) describe the different values that are expected to be populated for each attribute.

NOTE    The Document_definition_relationship entity ensures that the relating_document and the related_document are not the same.

The Instance Model: EXPRESS entities and attributes

The instantiation of the EXPRESS entities and attributes used to support the requirements of Document_definition_relationship are shown in the figure below.

Figure 17 —  Document_definition_relationship Instance Diagram

NOTE    In this example, the instance of Document_definition_relationship relates two Digital_document_definitions, where one (#61) is the substitution of the other (#29). In this case the Document_definition for version 3.3 is replacing the definition for 3.2. The newer version is an enhanced version and includes more drawings.

Document version relationships

Document_version relationships are handled through the Product_version_relationship entity is a relationship between two types of Product_version. This is applicable to Documents since the entity Document_version is a subtype of Product_version. Hence, the relationship may be between two Document_version instances. The semantics of the relationship are defined by the attributes relation_type and description of the entity relationship. The relation_type attribute defines the type of relationship between the two instances.

Attribute Population

The entity (Product_version_relationship) and attributes (relation_type, description, relating_version and related_version) describe the different values that are expected to be populated for each attribute.

NOTE    The Product_version_relationship entity is a generic relationdhip that can be applied to all of it's subtypes. The Product_version_relationship entity ensures that the relating_version and the related_version instances are not the same.

The Instance Model: EXPRESS entities and attributes

The instantiation of the EXPRESS entities and attributes used to support the requirements of Product_version_relationship are shown in the figure below.

Figure 18 —  Product_version_relationship Instance Diagram

NOTE    In this example, the instance of Product_version_relationship relates two Document_versions, where one (#60) is the derivation of the other (#28). In this case the Document_version 3.3 is derived from 3.2.

Capability templates

The following sections define a set of templates for the capability, where a template is a specification of a set of entities that need to be instantiated to represent a given set of information.

This section specifies the template assigning_document.

NOTE  An explanation of a template and the associated instantiation path is provided in the Template overview section.

Figure 1 —  An EXPRESS-G representation of the Information model for assigning_document

Figure 2 —  The graphical representation of the assigning_document template

Figure 3 —  Entities instantiated by assigning_document template

	
				#2 = DOCUMENT_ASSIGNMENT(#7,#8,'/IGNORE');
				#7 = DOCUMENT('/IGNORE','/IGNORE','/IGNORE');
				#8 = PART_VERSION('/IGNORE','/IGNORE',$);		
				#10 = CLASSIFICATION_ASSIGNMENT(#12,(#2),'/IGNORE');
				#12 = EXTERNAL_CLASS('/NULL','Document_reference','/IGNORE',#13);
				#13 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:sample',$);
			

Figure 4 —  Invocation of assigning_document template example - graphical presentations

Figure 5 —  Possible characterizations of the assignment of a document.

This section specifies the template assigning_document_reference.

NOTE  An explanation of a template and the associated instantiation path is provided in the Template overview section.

Figure 1 —  An EXPRESS-G representation of the Information model for assigning_document_reference

Figure 2 —  The graphical representation of the assigning_document_reference template

Figure 3 —  Entities instantiated by assigning_document_reference template

          #1 = TASK_METHOD_VERSION('/IGNORE','/IGNORE','/IGNORE','/IGNORE',$,$);
          #2 = DOCUMENT('/IGNORE','/IGNORE','/IGNORE');
          #3 = DOCUMENT_VERSION('/IGNORE','/IGNORE',#2);
          #5 = IDENTIFICATION_ASSIGNMENT('BICYCLEXXXAAA-AAA-DA1-00-00-0000-341A-A','/IGNORE',$,(#2));
          #7 = CLASSIFICATION_ASSIGNMENT(#8,(#5),'/IGNORE');
          #8 = EXTERNAL_CLASS('/NULL','Data_module_code','/IGNORE',#9);
          #9 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:sample','/IGNORE');
          #12 = ORGANIZATION('/IGNORE','/IGNORE');
          #14 = IDENTIFICATION_ASSIGNMENT('ASD','/IGNORE','/IGNORE',(#12));
          #16 = CLASSIFICATION_ASSIGNMENT(#17,(#14),'/IGNORE');
          #17 = EXTERNAL_CLASS('/NULL','Organization_name','/IGNORE',#18);
          #18 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:std','/IGNORE');
          #20 = ORGANIZATION_OR_PERSON_IN_ORGANIZATION_ASSIGNMENT(#12,'/IGNORE',(#5,#26));
          #22 = CLASSIFICATION_ASSIGNMENT(#23,(#20),'/IGNORE');
          #23 = EXTERNAL_CLASS('/NULL','Owner_of','/IGNORE',#18);
          #26 = IDENTIFICATION_ASSIGNMENT('1','/IGNORE',$,(#3));
          #28 = CLASSIFICATION_ASSIGNMENT(#29,(#26),'/IGNORE');
          #29 = EXTERNAL_CLASS('/NULL','Issue_number','/IGNORE',#9);
          #47 = DOCUMENT_ASSIGNMENT(#3,#1,'/IGNORE');
          #49 = CLASSIFICATION_ASSIGNMENT(#50,(#47),'/IGNORE');
          #50 = EXTERNAL_CLASS('/NULL','Document_reference','/IGNORE',#18);
        

Figure 4 —  Instantiation of assigning_document_reference template

Figure 5 —  Possible characterizations of the referenced document.

This section specifies the template assigning_partial_document.

NOTE  An explanation of a template and the associated instantiation path is provided in the Template overview section.

Figure 1 —  An EXPRESS-G representation of the Information model for assigning_partial_document

Figure 2 —  The graphical representation of the assigning_partial_document template

Figure 3 —  Entities instantiated by assigning_partial_document template

Figure 4 —  Instantiation of assigning_partial_document template

This section specifies the template assigning_partial_document_reference.

NOTE  An explanation of a template and the associated instantiation path is provided in the Template overview section.

Figure 1 —  An EXPRESS-G representation of the Information model for assigning_partial_document_reference

Figure 2 —  The graphical representation of the assigning_partial_document_reference template

Figure 3 —  Entities instantiated by assigning_partial_document_reference template

Figure 4 —  Instantiation of assigning_partial_document_reference template

This section specifies the template referencing_document.

NOTE  An explanation of a template and the associated instantiation path is provided in the Template overview section.

Figure 1 —  An EXPRESS-G representation of the Information model for referencing_document

Figure 2 —  The graphical representation of the referencing_document template

Figure 3 —  Entities instantiated by referencing_document template

          #1 = DOCUMENT('/IGNORE','/IGNORE','/IGNORE');
          #2 = DOCUMENT_VERSION('/IGNORE','/IGNORE',#1);
          #4 = IDENTIFICATION_ASSIGNMENT('BI-2410','/IGNORE','/IGNORE',(#1));
          #6 = CLASSIFICATION_ASSIGNMENT(#7,(#4),'/IGNORE');
          #7 = EXTERNAL_CLASS('/NULL','Feedback_form_identification_code','/IGNORE',#8);
          #8 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:sample','/IGNORE');
          #11 = ORGANIZATION('/IGNORE','/IGNORE');
          #13 = IDENTIFICATION_ASSIGNMENT('Bike Ltd','/IGNORE','/IGNORE',(#11));
          #15 = CLASSIFICATION_ASSIGNMENT(#16,(#13),'/IGNORE');
          #16 = EXTERNAL_CLASS('/NULL','Organization_name','/IGNORE',#17);
          #17 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:std','/IGNORE');
          #18 = ORGANIZATION_OR_PERSON_IN_ORGANIZATION_ASSIGNMENT(#11,'/IGNORE',(#4,#24));
          #20 = CLASSIFICATION_ASSIGNMENT(#21,(#18),'/IGNORE');
          #21 = EXTERNAL_CLASS('/NULL','Owner_of','/IGNORE',#17);
          #24 = IDENTIFICATION_ASSIGNMENT('1','/IGNORE','/IGNORE',(#2));
          #26 = CLASSIFICATION_ASSIGNMENT(#27,(#24),'/IGNORE');
          #27 = EXTERNAL_CLASS('/NULL','Issue_number','/IGNORE',#8);
        

Figure 4 —  Instantiation of referencing_document template

This section specifies the template representing_document.

NOTE  An explanation of a template and the associated instantiation path is provided in the Template overview section.

Figure 1 —  An EXPRESS-G representation of the Information model for representing_document

Figure 2 —  The graphical representation of the representing_document template

Figure 3 —  Entities instantiated by representing_document template

Figure 4 —  Entities instantiated by representing_document template

The following characterizations may apply:

Characterization Assigning time

NOTE   this characterization is optional.

Dates and time can be associated with either Document or Document_version by using one of the templates assigning_time, or assigning_calendar_date as shown in Figure 5

Figure 5 —  Characterization by time of Document

A creation date is commonly assigned to the template representing_document. The date and time assignment is classified as: "Date actual creation" (urn:plcs:rdl:std:Date actual creation) to indicate that it is the date (and time) when the Document or Document_version was actually created.

This section specifies the template representing_digital_document.

NOTE  An explanation of a template and the associated instantiation path is provided in the Template overview section.

Figure 1 —  An EXPRESS-G representation of the Information model for representing_digital_document

Figure 2 —  The graphical representation of the representing_digital_document template

Figure 3 —  Entities instantiated by representing_digital_document template

DATA;
#15 = EXTERNAL_CLASS('/IGNORE','Organization_name','/IGNORE',#16);
#14 = CLASSIFICATION_ASSIGNMENT(#15,(#12),'/IGNORE');
#12 = IDENTIFICATION_ASSIGNMENT('Parts R Us Ltd','/IGNORE','/IGNORE',(#10));
#10 = ORGANIZATION('/IGNORE','/IGNORE');
#8 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:std',$);
#7 = EXTERNAL_CLASS('/IGNORE','Document_identification_code','/IGNORE',#8);
#6 = CLASSIFICATION_ASSIGNMENT(#7,(#4),'/IGNORE');
#4 = IDENTIFICATION_ASSIGNMENT('DOC-PH-001-001','/IGNORE',$,(#2));
#2 = DOCUMENT('/IGNORE','/IGNORE','/IGNORE');
#30 = ORGANIZATION('/IGNORE','/IGNORE');
#28 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:std',$);
#27 = EXTERNAL_CLASS('/IGNORE','Version_identification_code','/IGNORE',#28);
#26 = CLASSIFICATION_ASSIGNMENT(#27,(#24),'/IGNORE');
#24 = IDENTIFICATION_ASSIGNMENT('0.3','/IGNORE',$,(#22));
#22 = DOCUMENT_VERSION('/IGNORE','/IGNORE',#2);
#21 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:std',$);
#20 = EXTERNAL_CLASS('/IGNORE','Owner_of','/IGNORE',#21);
#19 = CLASSIFICATION_ASSIGNMENT(#20,(#17),'/IGNORE');
#17 = ORGANIZATION_OR_PERSON_IN_ORGANIZATION_ASSIGNMENT(#10,'/IGNORE',(#4));
#16 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:std',$);
#47 = EXTERNAL_CLASS_LIBRARY($,$);
#46 = EXTERNAL_CLASS('/IGNORE','Support_stage','/IGNORE',#47);
#45 = CLASSIFICATION_ASSIGNMENT(#46,(#43),'/IGNORE');
#43 = VIEW_DEFINITION_CONTEXT('/IGNORE','/IGNORE','/IGNORE');
#42 = DIGITAL_DOCUMENT_DEFINITION('/IGNORE','/IGNORE','/IGNORE',#43,(),#22,());
#41 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:std',$);
#40 = EXTERNAL_CLASS('/IGNORE','Owner_of','/IGNORE',#41);
#39 = CLASSIFICATION_ASSIGNMENT(#40,(#37),'/IGNORE');
#37 = ORGANIZATION_OR_PERSON_IN_ORGANIZATION_ASSIGNMENT(#30,'/IGNORE',(#24));
#36 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:std',$);
#35 = EXTERNAL_CLASS('/IGNORE','Organization_name','/IGNORE',#36);
#34 = CLASSIFICATION_ASSIGNMENT(#35,(#32),'/IGNORE');
#32 = IDENTIFICATION_ASSIGNMENT('Parts R Us Ltd','/IGNORE','/IGNORE',(#30));
#51 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:std',$);
#50 = EXTERNAL_CLASS('/IGNORE','Maintenance','/IGNORE',#51);
#49 = CLASSIFICATION_ASSIGNMENT(#50,(#43),'/IGNORE');

ENDSEC;

Figure 4 —  Entities instantiated by representing_digital_document template

This section specifies the template representing_physical_document.

NOTE  An explanation of a template and the associated instantiation path is provided in the Template overview section.

Figure 1 —  An EXPRESS-G representation of the Information model for representing_physical_document

Figure 2 —  The graphical representation of the representing_physical_document template

Figure 3 —  Entities instantiated by representing_physical_document template

DATA;
#15 = EXTERNAL_CLASS('/IGNORE','Organization_name','/IGNORE',#16);
#14 = CLASSIFICATION_ASSIGNMENT(#15,(#12),'/IGNORE');
#12 = IDENTIFICATION_ASSIGNMENT('Parts R Us Ltd','/IGNORE','/IGNORE',(#10));
#10 = ORGANIZATION('/IGNORE','/IGNORE');
#8 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:std',$);
#7 = EXTERNAL_CLASS('/IGNORE','Document_identification_code','/IGNORE',#8);
#6 = CLASSIFICATION_ASSIGNMENT(#7,(#4),'/IGNORE');
#4 = IDENTIFICATION_ASSIGNMENT('DOC-PH-001-001','/IGNORE',$,(#2));
#2 = DOCUMENT('/IGNORE','/IGNORE','/IGNORE');
#30 = ORGANIZATION('/IGNORE','/IGNORE');
#28 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:std',$);
#27 = EXTERNAL_CLASS('/IGNORE','Version_identification_code','/IGNORE',#28);
#26 = CLASSIFICATION_ASSIGNMENT(#27,(#24),'/IGNORE');
#24 = IDENTIFICATION_ASSIGNMENT('0.3','/IGNORE',$,(#22));
#22 = DOCUMENT_VERSION('/IGNORE','/IGNORE',#2);
#21 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:std',$);
#20 = EXTERNAL_CLASS('/IGNORE','Owner_of','/IGNORE',#21);
#19 = CLASSIFICATION_ASSIGNMENT(#20,(#17),'/IGNORE');
#17 = ORGANIZATION_OR_PERSON_IN_ORGANIZATION_ASSIGNMENT(#10,'/IGNORE',(#4));
#16 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:std',$);
#47 = EXTERNAL_CLASS_LIBRARY($,$);
#46 = EXTERNAL_CLASS('/IGNORE','Support_stage','/IGNORE',#47);
#45 = CLASSIFICATION_ASSIGNMENT(#46,(#43),'/IGNORE');
#43 = VIEW_DEFINITION_CONTEXT('/IGNORE','/IGNORE','/IGNORE');
#42 = PHYSICAL_DOCUMENT_DEFINITION('/IGNORE','/IGNORE','/IGNORE',#43,(),#22,());
#41 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:std',$);
#40 = EXTERNAL_CLASS('/IGNORE','Owner_of','/IGNORE',#41);
#39 = CLASSIFICATION_ASSIGNMENT(#40,(#37),'/IGNORE');
#37 = ORGANIZATION_OR_PERSON_IN_ORGANIZATION_ASSIGNMENT(#30,'/IGNORE',(#24));
#36 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:std',$);
#35 = EXTERNAL_CLASS('/IGNORE','Organization_name','/IGNORE',#36);
#34 = CLASSIFICATION_ASSIGNMENT(#35,(#32),'/IGNORE');
#32 = IDENTIFICATION_ASSIGNMENT('Parts R Us Ltd','/IGNORE','/IGNORE',(#30));
#51 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:std',$);
#50 = EXTERNAL_CLASS('/IGNORE','Maintenance','/IGNORE',#51);
#49 = CLASSIFICATION_ASSIGNMENT(#50,(#43),'/IGNORE');

ENDSEC;

Figure 4 —  Entities instantiated by representing_physical_document template

This section specifies the template representing_digital_file.

NOTE  An explanation of a template and the associated instantiation path is provided in the Template overview section.

Figure 1 —  An EXPRESS-G representation of the Information model for representing_digital_file

Figure 2 —  The graphical representation of the representing_digital_file template

Figure 3 —  Entities instantiated by representing_digital_file template

DATA;
#1 = DIGITAL_FILE('/IGNORE','/IGNORE','/IGNORE');
#3 = IDENTIFICATION_ASSIGNMENT('FIG1-C005-T005-001','/IGNORE','/IGNORE',(#1));
#5 = CLASSIFICATION_ASSIGNMENT(#6,(#3),'/IGNORE');
#6 = EXTERNAL_CLASS('/NULL','File_identification_code','/IGNORE',#7);
#7 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:std','/IGNORE');
#10 = ORGANIZATION('/IGNORE','/IGNORE');
#12 = IDENTIFICATION_ASSIGNMENT('Bike Ltd','/IGNORE','/IGNORE',(#10));
#14 = CLASSIFICATION_ASSIGNMENT(#15,(#12),'/IGNORE');
#15 = EXTERNAL_CLASS('/NULL','Organization_name','/IGNORE',#7);
#17 = ORGANIZATION_OR_PERSON_IN_ORGANIZATION_ASSIGNMENT(#10,'/IGNORE',(#3));
#19 = CLASSIFICATION_ASSIGNMENT(#20,(#17),'/IGNORE');
#20 = EXTERNAL_CLASS('/NULL','Owner_of','/IGNORE',#7);
#23 = CLASSIFICATION_ASSIGNMENT(#24,(#1),'/IGNORE');
#24 = EXTERNAL_CLASS('/NULL','Drawing','/IGNORE',#25);
#25 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:sample','/IGNORE');
ENDSEC;

Figure 4 —  Entities instantiated by representing_digital_file template

This section specifies the template representing_hardcopy_file.

NOTE  An explanation of a template and the associated instantiation path is provided in the Template overview section.

Figure 1 —  An EXPRESS-G representation of the Information model for representing_hardcopy_file

Figure 2 —  The graphical representation of the representing_hardcopy_file template

Figure 3 —  Entities instantiated by representing_hardcopy_file template

				DATA;
				#15 = EXTERNAL_CLASS('/IGNORE','Organization_name','/IGNORE',#16);
				#14 = CLASSIFICATION_ASSIGNMENT(#15,(#12),'/IGNORE');
				#12 = IDENTIFICATION_ASSIGNMENT('Parts R Us Ltd','/IGNORE','/IGNORE',(#10));
				#10 = ORGANIZATION('/IGNORE','/IGNORE');
				#8 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:std',$);
				#7 = EXTERNAL_CLASS('/IGNORE','File_name','/IGNORE',#8);
				#6 = CLASSIFICATION_ASSIGNMENT(#7,(#4),'/IGNORE');
				#4 = IDENTIFICATION_ASSIGNMENT('Hardcopy Print of FIG1-C005-T005-001','/IGNORE',$,(#2));
				#2 = HARDCOPY('/IGNORE','/IGNORE','/IGNORE');
				#31 = IDENTIFICATION_ASSIGNMENT('Parts R Us Ltd','/IGNORE','/IGNORE',(#29));
				#29 = ORGANIZATION('/IGNORE','/IGNORE');
				#27 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:std',$);
				#26 = EXTERNAL_CLASS('/IGNORE','Version_identification_code','/IGNORE',#27);
				#25 = CLASSIFICATION_ASSIGNMENT(#26,(#23),'/IGNORE');
				#23 = IDENTIFICATION_ASSIGNMENT('Print 1','/IGNORE',$,(#2));
				#21 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:std',$);
				#20 = EXTERNAL_CLASS('/IGNORE','Owner_of','/IGNORE',#21);
				#19 = CLASSIFICATION_ASSIGNMENT(#20,(#17),'/IGNORE');
				#17 = ORGANIZATION_OR_PERSON_IN_ORGANIZATION_ASSIGNMENT(#10,'/IGNORE',(#4));
				#16 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:std',$);
				#44 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:std',$);
				#43 = EXTERNAL_CLASS('/IGNORE','Drawing','/IGNORE',#44);
				#42 = CLASSIFICATION_ASSIGNMENT(#43,(#2),'/IGNORE');
				#40 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:std',$);
				#39 = EXTERNAL_CLASS('/IGNORE','Owner_of','/IGNORE',#40);
				#38 = CLASSIFICATION_ASSIGNMENT(#39,(#36),'/IGNORE');
				#36 = ORGANIZATION_OR_PERSON_IN_ORGANIZATION_ASSIGNMENT(#29,'/IGNORE',(#23));
				#35 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:std',$);
				#34 = EXTERNAL_CLASS('/IGNORE','Organization_name','/IGNORE',#35);
				#33 = CLASSIFICATION_ASSIGNMENT(#34,(#31),'/IGNORE');
				ENDSEC;
        

Figure 4 —  Entities instantiated by representing_hardcopy_file template

The following characterizations may apply:

Characterization Assigning time

NOTE   this characterization is optional.

Dates and time can be associated with a Hardcopy by using one of the templates assigning_time, or assigning_calendar_date (deprecated).

Figure 5 —  Characterization by time of Hardcopy

A creation date is commonly assigned to the template representing_hardcopy_file. The date and time assignment is classified as: "Date actual creation" (urn:plcs:rdl:std:Date actual creation) to indicate that it is the date (and time) when the Hardcopy was actually created.

This section specifies the template representing_file_relationships.

NOTE  An explanation of a template and the associated instantiation path is provided in the Template overview section.

Figure 1 —  An EXPRESS-G representation of the Information model for representing_file_relationships

Figure 2 —  The graphical representation of the representing_file_relationships template

The following classes and their sub-classes can be used:

classifications: "File_relationship" (urn:plcs:rdl:std:File_relationship), [References]
Error RDL1: The class References does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
[Originates]
Error RDL1: The class Originates does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
[Derivation]
Error RDL1: The class Derivation does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml

Figure 3 —  Entities instantiated by representing_file_relationships template

				DATA;
				#7 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:std',$);
				#6 = EXTERNAL_CLASS('/IGNORE','References','/IGNORE',#7);
				#5 = CLASSIFICATION_ASSIGNMENT(#6,(#1),'/IGNORE');
				#3 = DIGITAL_FILE('/IGNORE','/IGNORE','/IGNORE');
				#2 = DIGITAL_FILE('/IGNORE','/IGNORE','/IGNORE');
				#1 = FILE_RELATIONSHIP('/IGNORE','/IGNORE',#2,#3);
				ENDSEC;
        

Figure 4 —  Entities instantiated by representing_file_relationships template

This section specifies the template representing_document_history.

NOTE  An explanation of a template and the associated instantiation path is provided in the Template overview section.

Figure 1 —  An EXPRESS-G representation of the Information model for representing_document_history

Figure 2 —  The graphical representation of the representing_document_history template

The following classes and their sub-classes can be used:

classifications: [Sequential_version_relationship]
Error RDL1: The class Sequential_version_relationship does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
[Derived_version_relationship]
Error RDL1: The class Derived_version_relationship does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml
[Hierarchical_version_relationship]
Error RDL1: The class Hierarchical_version_relationship does not exist in RDL at urn urn:plcs:rdl:std. Check the dexlib/data/refdata/rdl_index.xml

Figure 3 —  Entities instantiated by representing_document_history template

				DATA;
				#8 = EXTERNAL_CLASS_LIBRARY('urn:plcs:rdl:std',$);
				#7 = EXTERNAL_CLASS('/IGNORE','Document','/IGNORE',#8);
				#6 = CLASSIFICATION_ASSIGNMENT(#7,(#1),'/IGNORE');
				#4 = DOCUMENT('/IGNORE','/IGNORE','/IGNORE');
				#3 = DOCUMENT_VERSION('/IGNORE','/IGNORE',#4);
				#2 = DOCUMENT_VERSION('/IGNORE','/IGNORE',#4);
				#1 = PRODUCT_VERSION_RELATIONSHIP('/IGNORE','/IGNORE',#2,#3);
				ENDSEC;
        

Figure 4 —  Entities instantiated by representing_document_history template

The following characterizations may apply:

Characterization Assigning time

NOTE   this characterization is optional.

Dates and time can be associated with a historical version of a document by using one of the templates assigning_time, or assigning_calendar_date (deprecated).

Figure 5 —  Characterization by time of document version history

A creation date is commonly assigned to the template representing_document_history. The date and time assignment is classified as: "Date actual creation" (urn:plcs:rdl:std:Date actual creation) to indicate that it is the date (and time) when the document version was actually created.

Related capabilities

This capability "Representing Documents" is related to the following capabilities:

• C079: representing_properties_numerically
• C016: representing_person_organization
• C002: representing_parts

Dependent capabilities

This capability "Representing Documents" is dependent on the following capabilities:

• C001: assigning_identifiers
• C010: assigning_reference_data

Related standards

There might be the need to classify product data items according to a classification system with explicit reference to the classification criteria and related properties of the product data items. This classification mechanism is called general classification. The PDM Schema only supports specific classification of product data items via assigned categories, which are defined by labeling them with a name. PLCS provides the general classification.

Model reference data

The following classes of reference data are required for this capability:

© OASIS 2010 — All rights reserved