comos operations pqm 5 - siemens · 2015-01-21 · pqm operating manual, 08/2011, a5e03376726-01 9...

� �PQM

___________________

___________________

___________________

___________________

___________________

___________________

___________________

___________________

___________________

___________________

___________________

___________________

___________________

___________________

___________________

___________________

COMOS

Operations PQM

Operating Manual

08/2011 A5E03376726-01

Trademarks 1

Introduction 2

Definitions 3

Import 4

Using attributed search 5

Check out and check in function

6

Transmittals 7

DVM document package 8

Version history 9

Exporting and reloading documents

10

Bulk processing of documents

11

Working with xReferences 12

Workflow Management with PQM

13

Extended PQM functions 14

Administration 15

User interface reference 16

Legal information

Legal information Warning notice system

This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are graded according to the degree of danger.

DANGER indicates that death or severe personal injury will result if proper precautions are not taken.

WARNING indicates that death or severe personal injury may result if proper precautions are not taken.

CAUTION with a safety alert symbol, indicates that minor personal injury can result if proper precautions are not taken.

CAUTION without a safety alert symbol, indicates that property damage can result if proper precautions are not taken.

NOTICE indicates that an unintended result or situation can occur if the relevant information is not taken into account.

If more than one degree of danger is present, the warning notice representing the highest degree of danger will be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to property damage.

Qualified Personnel The product/system described in this documentation may be operated only by personnel qualified for the specific task in accordance with the relevant documentation, in particular its warning notices and safety instructions. Qualified personnel are those who, based on their training and experience, are capable of identifying risks and avoiding potential hazards when working with these products/systems.

Proper use of Siemens products Note the following:

WARNING Siemens products may only be used for the applications described in the catalog and in the relevant technical documentation. If products and components from other manufacturers are used, these must be recommended or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and maintenance are required to ensure that the products operate safely and without any problems. The permissible ambient conditions must be complied with. The information in the relevant documentation must be observed.

Trademarks All names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this publication may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.

Disclaimer of Liability We have reviewed the contents of this publication to ensure consistency with the hardware and software described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in this publication is reviewed regularly and any necessary corrections are included in subsequent editions.

Siemens AG Industry Sector Postfach 48 48 90026 NÜRNBERG GERMANY

A5E03376726-01 Ⓟ 09/2011

Copyright © Siemens AG 2011. Technical data subject to change

PQM Operating Manual, 08/2011, A5E03376726-01 3

Table of contents

1 Trademarks ............................................................................................................................................... 7

2 Introduction................................................................................................................................................ 9

3 Definitions................................................................................................................................................ 11

4 Import ...................................................................................................................................................... 13

4.1 Importing documents ...................................................................................................................13 4.1.1 Importing single documents into COMOS ...................................................................................13 4.1.2 Importing a document into a document template.........................................................................14 4.1.3 Importing documents with the "Include documents" plugin .........................................................15 4.1.4 Importing documents from MS Office ..........................................................................................16 4.1.5 Viewing metadata of the PQM document ....................................................................................17

4.2 Importing documents in bulk ........................................................................................................17 4.2.1 Metadata management using the "CPlugInFileTransAttribute.xls" file ........................................18 4.2.1.1 Basics...........................................................................................................................................18 4.2.1.2 Metadata management with Excel...............................................................................................18 4.2.1.3 FTA1 mode ..................................................................................................................................19 4.2.2 Metadata management using the "CPlugInFileTransAttribute.xml" file .......................................21 4.2.3 Metadata management using the "CPlugInFileTransAttribute.csv" file .......................................22 4.2.4 Performing bulk import.................................................................................................................23

4.3 Viewing.........................................................................................................................................23

5 Using attributed search............................................................................................................................ 27

5.1 Activating attributed search..........................................................................................................27

5.2 Displaying search results .............................................................................................................28

5.3 User-specific attributed search ....................................................................................................29

6 Check out and check in function .............................................................................................................. 31

6.1 Checking out a document ............................................................................................................31

6.2 Checking in a document ..............................................................................................................32

6.3 Lock mechanism in combination with working layers ..................................................................33

7 Transmittals ............................................................................................................................................. 35

7.1 Preparing to create transmittals ...................................................................................................35

7.2 Creating a transmittal...................................................................................................................35

7.3 Sending a transmittal ...................................................................................................................36

7.4 Receiving a transmittal.................................................................................................................37

7.5 Adding additional documents to a transmittal ..............................................................................38 7.5.1 Adding new documents outside of COMOS before receipt .........................................................38 7.5.2 Adding new documents within COMOS after receipt ..................................................................39

8 DVM document package ......................................................................................................................... 41

Table of contents

PQM 4 Operating Manual, 08/2011, A5E03376726-01

8.1 Creating a DVM document package ........................................................................................... 41

8.2 Importing DVM document packages........................................................................................... 42

9 Version history ......................................................................................................................................... 45

9.1 Opening the version history ........................................................................................................ 46

10 Exporting and reloading documents......................................................................................................... 49

10.1 Exporting documents .................................................................................................................. 49

10.2 Undo export................................................................................................................................. 49

10.3 Permanent export........................................................................................................................ 50

10.4 Reloading documents ................................................................................................................. 50

11 Bulk processing of documents ................................................................................................................. 53

11.1 Checking out documents in bulk ................................................................................................. 53

11.2 Checking in documents in bulk ................................................................................................... 54

11.3 Calling the "My most recent documents" query .......................................................................... 54

12 Working with xReferences ....................................................................................................................... 55

13 Workflow Management with PQM............................................................................................................ 57

13.1 "Checking documents in and out" workflow ................................................................................ 57 13.1.1 Checking out documents with workflow ...................................................................................... 58 13.1.2 Checking in documents with workflow ........................................................................................ 58

13.2 "Document request" workflow ..................................................................................................... 59

13.3 "Import documents" workflow...................................................................................................... 59

14 Extended PQM functions ......................................................................................................................... 61

14.1 Options ........................................................................................................................................ 61

14.2 Roles ........................................................................................................................................... 62

14.3 Tree structure and responsibilities .............................................................................................. 63

14.4 Configuring the tree structure and course................................................................................... 63

14.5 Creating and filling documents.................................................................................................... 65

14.6 Completing the phases ............................................................................................................... 65

14.7 Configuring the qualification evaluation ...................................................................................... 67

15 Administration.......................................................................................................................................... 69

15.1 Project settings for PQM ............................................................................................................. 69

15.2 Project settings for bulk import of documents ............................................................................. 71

15.3 Viewer settings............................................................................................................................ 73

15.4 Defining the check in dialog window ........................................................................................... 74

15.5 Connecting MS Office to COMOS .............................................................................................. 75

15.6 Defining the description for imported documents ....................................................................... 75

15.7 Defining the attributed search ..................................................................................................... 76

Table of contents


15.7.1 Base definition of the search dialog window................................................................................76 15.7.2 Define document base object (DVM)...........................................................................................77 15.7.3 Making the search dialog window available.................................................................................79 15.7.3.1 Creating a base object .................................................................................................................79 15.7.3.2 Copying a search dialog window .................................................................................................80

15.8 Adding documents to the transmittals on the master data side...................................................80

15.9 Administrating extended PQM functions......................................................................................81 15.9.1 Adapting base data ......................................................................................................................81 15.9.2 Updating the document catalog ...................................................................................................82

16 User interface reference .......................................................................................................................... 83

16.1 "DVM transmittal" user interface ..................................................................................................83

16.2 "Transmittal" window, "Head data" tab ........................................................................................84

16.3 "Navigator" window ......................................................................................................................86

16.4 "PQM project config" tab..............................................................................................................86

Table of contents



Trademarks 1Trademarks

Registered trademark: COMOS®

Trademarks



Introduction 2

Overview PQM (Project Quality Management) imports and manages external documents in COMOS. PQM here as a document management system (DMS) supports you throughout all key lifecycle phases of your project documents.

COMOS PQM covers the following DMS functionalities:

● Document check in and check out

● Document export

● Version management

● Import and management of metadata

● Import and management of XReferences

● Single and bulk import of documents

File formats COMOS PQM supports the import of all commonly used file formats, such as:

● DGN

● DWG

● PPT

● MSG

● DOC

● XLS

● PDF

Introduction



Definitions 3DVM document

DVM = Document Version Management

A DVM document is a COMOS document that is used to manage multiple versions of an external document.

To create a DVM document, select the "Create document with version management" option in the "Navigator" window when importing an external document. This will set the base object to the document base object that you specified on the "PQM options" tab in the project properties.

Definitions



Import 44.1 Importing documents

Introduction PQM allows you to import external documents into COMOS. You can import single documents or multiple documents in bulk into COMOS and assign metadata to them.

4.1.1 Importing single documents into COMOS You can import individual documents to COMOS and assign metadata specifically in the process.

Requirement Your administrator has activated the "Drag&drop import for PQM" option in the project properties.

See also section Project settings for PQM (Page 69).

Procedure 1. Drag&drop a document from a file folder or directory to a unit or location in the COMOS

Navigator.

2. To select import mode, choose the "Create document with version management" option

from the "Navigator" window.

3. Then click "OK".

Another window ("Mandatory fields") opens which contains several fields. Enter the metadata for your document in the input fields. Note that the fields highlighted in red are mandatory fields.



4. Enter the metadata for the document you want to import.

5. Then click "OK".

Note

The mandatory fields can be customized or extended by the administrator in the "PQM > @Y > 1 > 03 > 02 > Mandatory" object of the base project.

4.1.2 Importing a document into a document template

Procedure 1. In the unit tree, create a new document by selecting "New > Document" from the context

menu.

2. Select an entry from the "Type" list on the "General" tab.

Example: Excel

3. On the symbol bar, click on the button "Show base object".

You will see the "Base object" field underneath the "Description" field.

4. Drag&drop the base object "PQM > @O > DVM > 02 Autom. readout of FileProperties" from the base data to the "Base object" field.

The base object "02 Autom. readout of FileProperties" is ready for you to use as an example in the COMOSDB. However, you can also use base objects you have defined yourself.

5. Click the "OK" button.

6. Open the context menu of the object that you have created.

7. Select the "Import" command.

8. Select an Excel file you want to import.

9. Enter the metadata in the "Mandatory fields" window.


Result You have imported a document into a document template.



4.1.3 Importing documents with the "Include documents" plugin By using the "Include documents" plugin, you can import up to ten documents at a time.

Procedure To import multiple documents, proceed as follows:

1. To open the file browser, click the "Plugins > PQM > Include documents" menu.

2. To select the source directory in which the to be imported documents are located, click on the "Select directory" button.

Your documents are then displayed in the file browser. You can display additional columns in the file browser by clicking the "File properties" button to the left of the question mark.

3. In the file browser, select the files that you want to import.

4. Activate one of the following options:

– "Selected files have the same check in values"

If you wish to store the same metadata for all selected documents.

– "Create DVM package"

Available if the option "Selected files have the same check in values" is activated. Creates a DVM document package with all the selected files.

On the tab "Mandatory attributes for all files > Mandatory fields", a table is displayed with all selected files which are included in the DVM package.

See chapter DVM document package (Page 41).

– "Selected files have different check in values"

If you wish to store separate metadata for each document.

5. Click "Next" to enter the metadata now.

The "Mandatory attributes for all files > Mandatory fields" tab is then displayed.

6. Enter the metadata for the documents you want to import.

7. If you have activated the "Create DVM package" option beforehand, enter a description for the files in the table and determine the printing order.

8. Click on the "Check in" button.

Result The imported documents are then displayed in the Navigator under the specified unit or location.



4.1.4 Importing documents from MS Office You can import documents directly from MS Office into COMOS. This function is available for the following applications:

● MS Word

● MS Excel

● MS PowerPoint

● MS Outlook

Requirements You have connected MS Office to COMOS. See also section Connecting MS Office to COMOS (Page 75).

Procedure To import a document from MS Office, proceed as follows:

1. Open one of the Office applications referred to above.

Example: MS Excel

2. Open the document you wish to import into COMOS.

"COMOS" is entered as an add-in in Excel.

3. Activate COMOS as an add-in.

The COMOS icon is visible on the symbol bar.

4. Click the COMOS icon.

COMOS opens, followed by the "Mandatory fields" window.

5. Enter the metadata for the document in the "Mandatory fields" window.


Result The document has been imported into COMOS.

Import 4.2 Importing documents in bulk


4.1.5 Viewing metadata of the PQM document After the import, you can view the metadata of the PQM document by way of the document properties.

Procedure To view metadata of the PQM document, double-click on the desired PQM document on the "Units" or "Locations" tab of the Navigator.

4.2 Importing documents in bulk With COMOS PQM can import a large number of existing documents in bulk including metadata to COMOS.

However, some prerequisites have to be fulfilled before you can import a larger number of documents.



Prerequisites ● Your administrator has carried out the project settings for the bulk import of documents.

See also section Project settings for bulk import of documents (Page 71).

● You have entered the metadata optionally in an Excel, XML or CSV file.

See also section Metadata management using the "CPlugInFileTransAttribute.xls" file (), Chapter Metadata management using the "CPlugInFileTransAttribute.xml" file (Page 21), Chapter Metadata management using the "CPlugInFileTransAttribute.csv" file (Page 22).

4.2.1 Metadata management using the "CPlugInFileTransAttribute.xls" file

4.2.1.1 Basics If you want to use an Excel file in order to store metadata from documents before the import to COMOS, use a separate Excel spreadsheet called CPlugInFileTransAttribute.xls.

Alternatively you can use a file called CPlugInFileTransAttribute.mdb.

One of the following modes is activated depending on the name of the first worksheet, FTA or FTA1.

4.2.1.2 Metadata management with Excel

Structure of the Excel table In FTA mode (old mode) all to be imported documents must be located in the same directory as the Excel table.

Example Example extract from Excel table CPlugInFileTransAttribute.xls:

The Excel table must have the following structure:

● Name of the Excel file: CPlugInFileTransAttribute.xls

● Name of the first worksheet: FTA

● All column headers of the table shown:



Column Meaning Mandatory field UniqueFileName Contains the unique name of the document you want to import. The

header must be written exactly as specified in the column on the left. internal

Anlagenkennzeichen Contains the label of the unit or location under which the document you want to import is to be created. If you want to create the to be imported documents on the unit tree, you must enter an equals sign (=) before the label. If you want to create the to be imported documents in the location tree, you must enter a plus sign (+) before the label.

Metadata

Dokumentengruppe Contains the name of the COMOS document group to which the document to be imported must be assigned. Under the topmost node "@NameSystem" document groups located lower in the structure are separated by a dot.

Metadata

Firma Name of the company that created the document. Metadata Betreff Title of the document. Metadata Autor Name of the author who wrote the document. Metadata Erstelldatum Date when the document was created. Metadata Schlagwort Keyword to classify the document by subject, e.g. chemicals or waste

disposal. Metadata

The sequence in which the documents are imported is determined by the sequence of the documents in the Excel table.

For your import to be successful, you must also assign all attribute values of the document to be imported alongside the column headers.

See also Project settings for bulk import of documents (Page 71)

4.2.1.3 FTA1 mode

Structure of the Excel table In FTA1 mode (new mode) the to be imported documents may be located in different drive and directory paths, independently of the Excel file.



Example Example extract from Excel table CPlugInFileTransAttribute.xls:

The Excel file must have the following structure:

● Name of the Excel file: CPlugInFileTransAttribute.xls

● Name of first worksheet: FTA1

● All column headers of the following table:

Column Meaning Mandatory

field MasterID May be identical for multiple versions of a document. If this is the case for two

documents, only one document is imported in two versions. The input may be alphanumeric.

internal

UniqueID Must always be unique. The input may be alphanumeric. internal FileName Contains the unique name of the document. internal DirPath Contains the absolute drive and directory path to the document. If there is no path

to an entered document here, the document is searched for in the directory containing the Excel table.

internal

RevIndex Numeric column in which only numeric values are allowed. To create a revision of the document, enter any number here. If you do not want to create a revision of the document, the column must be empty.

internal

RevFileName Here you can enter an existing revision file in the "<filename>.PDF" format. The revision file must be located in the directory that is specified in the "DirPath" column.

internal

Status Contains the "DONE" value after the import, if the import was successful, or in the event of an error the "ERROR" value. A new import can only be performed if this column is empty.

internal

Anlagenkennzeichen Contains the label of the unit or location under which the document that you want to import is to be created. If you want to create the to be imported document in the unit tree, you must enter an equals sign (=) before the label. If you want to create the to be imported document in the location tree, you must enter a plus sign (+) before the label.

Metadata

Dokumentengruppe Contains the name of the COMOS document group to which the document to be imported must be assigned.

Metadata

Firma Name of the company that created the document. Metadata Betreff Title of the document. Metadata Autor Name of the author who wrote the document. Metadata Erstelldatum Date when the document was created. Metadata Schlagwort Keyword to classify the document by subject, e.g. chemicals or waste disposal. Metadata

The sequence in which the documents are imported is determined by the sequence of the documents in the Excel table.

For your import to be successful, you must also assign all attribute values of the document to be imported alongside the column headers.


4.2.2 Metadata management using the "CPlugInFileTransAttribute.xml" file If you want to use an XML file in order to store metadata from documents before the import to COMOS, use a separate XML file called CPlugInFileTransAttribute.xml.

Example <FileTrans> <File UniqueID="1"> <MasterID>12</MasterID>  <FileName>Test.Docx</FileName>  <DirPath>D:\Test\</DirPath>  <RevIndex></RevIndex>  <RevFileName></RevFileName>  <Status></Status>  <Attributes> <Unit label>@U1</Unit label> <Document group>@NameSystem</Document group> <Subject>Test</Subject> <Company>Test</Company> <Author>Test</Author> <Keyword>Chemicals</Keyword> </Attributes> </File> <Package UniqueID="2"> <MasterID>13</MasterID>  <RevIndex></RevIndex>  <RevFileName></RevFileName>  <Status></Status>  <Attributes> <Unit label>@U1</Unit label> <Document group>@NameSystem</Document group> <Subject>Test</Subject> <Company>Test</Company> <Author>Test</Author> <Keyword>Chemicals</Keyword> </Attributes> <Files> <FileName>test1.doc

<DirPath>D:\Test</DirPath>  <Sequence>1</Sequence>  <Description>111</Description>  </FileName> <FileName>test2.xls  <DirPath>D:\Test</DirPath>  <Sequence>2</Sequence>  <Description>222</Description>  </FileName> </Files> </Package> </FileTrans>

The user can extend the node Attributes freely in accordance with his system.

The marked mandatory nodes have to exist and may not be renamed.

4.2.3 Metadata management using the "CPlugInFileTransAttribute.csv" file If you want to use a CSV file in order to store metadata from documents before the import to COMOS, use a separate CSV file called CPlugInFileTransAttribute.csv.

The semicolon (;) is used as the separator for the CSV files.

The uppermost line of the CSV file contains:

MasterID;UniqueID;FileName;DirPath;RevIndex;RevFileName;Status;Attribute1;Attribute2. The listed columns are mandatory fields with the exception of the Attribute columns. Additional Attribute columns can be used.

The Status column has to remain empty.

See also section FTA1 mode (Page 19).

Importing a DVM document package In order to check in a DVM document package, create a further CSV file called CPlugInFileTransPackages.csv in addition to the CSV file described above:

The uppermost line of this CSV file contains:

UniqueID;FileName;DirPath;Sequence;Description

The specified columns are mandatory fields. Additional columns are not processed.

Import 4.3 Viewing


4.2.4 Performing bulk import

Requirements After you have completed all preparations, start the import.

Procedure To import documents in bulk, proceed as follows:

1. Click the "Plugins > PQM > File transfer" menu.

The "File transfer" window opens.

2. To start the import, click the "Start" button in the "File transfer" window.

The "Import messages" section shows whether the import was successful or erroneous.

After the successful import, the documents and the corresponding metadata from the Excel table are created under the unit or location you specified in the Excel table. See also section Metadata management with Excel (Page 18).


4.3 Viewing You can view the documents you imported in Viewing mode. If you have acquired an add-on license for AutoVue, COMOS opens your documents directly in AutoVue. This means the applications in which the documents were created do not have to be installed on your computer. Under "Plugins > PQM > Viewer settings" you specify which program is run when opening a document that was imported into PQM. See also section Viewer settings (Page 73).

To open a document, double-click on it or right-click on it and choose the "Open" command from the context menu.

Import 4.3 Viewing


Example The following example shows a DNG file that was opened with AutoVue:

Import 4.3 Viewing



Using attributed search 5

Requirements To run an attributed search in the current project, make the following preparations:

● Creating the full-text index

As full-text search works project-specific, you must generate a full-text index once in each project. For more information on this subject refer to the "Document Management" manual keyword "Creating a full-text index".

● Publishing a search dialog window

To select a search dialog window for PQM as a full-text search, it must first be defined and published as a full-text search. See also section Making the search dialog window available (Page 79).

5.1 Activating attributed search COMOS saves documents that you imported using version management together with the metadata you entered. In COMOS, you can specifically search your documents for metadata. When searching for metadata, a result list is created with links to the documents where the metadata is located.

Procedure To run a search for metadata, proceed as follows:

1. Click the "Plugins > Basic > Full-text search" menu.

2. From the "Active search dialog window" list select "Attributed search".

The "Attributed search" tab is displayed.

3. Enter the metadata you want to search for in the fields.

The attributed search contains the same fields as the form you used for storing metadata of your documents when you checked them in. See also section Importing documents (Page 13).

4. To start the search click the "Search" button.

Result The hit list containing the found documents is displayed in the "Search results" window.

Using attributed search 5.2 Displaying search results


See also Defining the attributed search (Page 76)

5.2 Displaying search results

Overview For the attributed search the hits are displayed in a separate window. The window displays the search results in the same way as for a standard search:

Structure of search results The hit list displays all documents that contain your search term. The field names of the metadata are displayed as column headers for all entered search terms.

The following columns are displayed by default:

Column Description "Document" Contains the name and symbol of the document. "Unit revisions" Contains the name of the released unit revision. "Project revisions" Contains the name of the released project revisions. "Unit versions" Contains the name of the checked in DVM version of the documents. "Project versions" Contains the name of the checked in DVM versions of documents.

Document details You can superimpose detailed information on the documents in the search results in COMOS. You can enable the display of detailed information through the Options tab above the search results.

● "Document preview" option

When you enable the option, on the right next to the search results a document preview is displayed for the document that you selected in the search results. However, first you should enable Document preview in the Project options: Project properties, "Options" tab, "Documents" tab, "AutoVue - to be used to view documents" checkbox. To use the document preview function you need a separate license.

● "Document properties" option

If you activate this option, part of the properties window for the document you selected from the search results is displayed on the right of the search results. If required, you can change the properties directly from the window.

Using attributed search 5.3 User-specific attributed search


Build search result separately The search results are structured like a normal object query. You can configure them to your needs. For example, you can show or hide columns in the search results, apply filters on a column or search area.

To insert a new column, proceed as follows:

1. Right-click on a column header.

2. Select the "New > Timestamp > Date" command from the context menu.

The "Date" column is then displayed in the hit list.

3. Right-click on a column header.

4. Select the "Setting > Save" command from the context menu.

Scrolling in the search results When the search result exceeds the maximum value of the matches to be displayed you can scroll in the search results. The scroll function is located in the lower right area of the search results. Clicking the right arrow displays a new page in the search results that lists the remaining hits.

Searching for documents across different working layers When you are working in a project with several working layers, you can search for documents across different working layers. This means that with the full-text search you can not only find the documents that you imported to the working layer, but also documents that are in the preceding layers.

5.3 User-specific attributed search You define the user-specific attributed search yourself. This means that you can define a search using your own search criteria that are only available for your user login information.

The user-specific attributed search is used and defined in exactly the same way as the attributed search, with the exception that you create a user-specific base object which acts as a template for your search dialog window.

You create this template on the "Base objects" tab in the engineering project, under the "@System > @Profiles > <Current user> > FTSearch > FTSearchTemplates" node. See also section Making the search dialog window available (Page 79). If the objects in this path do not exist in your database, create them.

To enable a template to be recognized, you must have the name "FTSearch<Name_Search dialog window>" and be in the current project.

Using attributed search 5.3 User-specific attributed search



Check out and check in function 6

Introduction With the check out and check in function in PQM you can monitor the editing and updating of your documents. Documents are checked out by a user during editing and consequently locked so that only one user can work on a document at a time. When the user finishes editing, he checks in the document again. Regardless of how many users are editing or updating a document, in this way it is guaranteed that each user always has the latest version.

6.1 Checking out a document COMOS PQM gives you two possibilities to check out and edit a document:

Requirement To be able to edit the document the application in which you created the document must be installed on your computer.

Procedure To check out a document, proceed as follows:

1. Right-click on the document you want to check out.

2. Select the "Check out" command from the context menu.

The "Check out comment" window opens.

3. Enter a comment on the check-out process.

4. Click "OK" to confirm your selection and close the "Check out comment" window.

5. Right-click on the checked out document in the Navigator.

6. Select the "Open" command in the context menu.

7. In the "Show / Edit" window select the "Edit document that is checked out" option.

8. Click "OK" to confirm your selection.

Result The document is opened and you can edit it. In the Navigator you can identify checked out documents by the lock symbol that is displayed on the left below the document.

Check out and check in function 6.2 Checking in a document


Alternative procedure To check out a document, proceed as follows:

1. Right-click on the document you want to check out.

2. Select the "Open" command in the context menu.

3. In the "Show / Edit" window select the "Check out and edit documents" option.

4. Click "OK" to confirm your selection.

The "Check out comment" window opens.

5. Enter a comment on the check-out process.

6. Click "OK" to confirm your selection and close the "Check out comment" window.

Result The document is opened and you can edit it.

6.2 Checking in a document

Overview When you have successfully completed the checkout process and the editing of the document, you can check in the document or discard the changes that you made to the document.

Discard changes If you do not want to apply the changes you made to a checked-out document, proceed as follows:

1. Right-click in the Navigator on the document you checked out.

2. Select the "Undo check out" command in the context menu.

In this case, no new version of the document is created.

Procedure To check in a document, proceed as follows:

1. Right-click in the Navigator on the document you checked out.

2. Select the "Check in" command in the context menu.

The "Check in comment" window opens:

3. In the "Check in comment" window enter a commentary on the check-in process.

Check out and check in function 6.3 Lock mechanism in combination with working layers


4. Click "OK" to save your input and close the "Check in comment" window.

The "Mandatory fields" window opens, where you can edit the metadata of the document if required.

5. To check in the document, click the "OK" button in the window.

Result The changes to the previously checked out documents are applied when they are checked in.

6.3 Lock mechanism in combination with working layers

Overview It is not possible to edit the same document simultaneously in parallel working layers. If a user tries to check out a document that is already checked out in a parallel layer, the user is informed that it is not possible to edit the document.

You can only edit the document again when the document has been checked in and its working layer is released.

Check out and check in function 6.3 Lock mechanism in combination with working layers



Transmittals 7

Transmittals are versioned packages in which you compile documents and queries for the purpose of exporting them from COMOS in a bundle. You can edit the documents externally and then import the bundled package back into COMOS under a different version.

7.1 Preparing to create transmittals

Procedure To prepare for creating transmittals, proceed as follows:

1. Open the "Documents" tab in the Navigator.

2. Create a folder named "@Transmittals" directly underneath the project node.

3. Open the project properties.

4. Open the "Options > PQM options" tab.

5. Drag&drop the transmittal base objects into the fields provided for this purpose. See also section Project settings for PQM (Page 69).

6. In the "Directory" field, specify the directory in which the transmittal is to be stored.

Result You can now create the transmittal.

7.2 Creating a transmittal

Procedure To create and send a transmittal, proceed as follows:

1. Click the "Plugins > PQM > DVM transmittal" command in the menu.

The "DVM transmittal" user interface opens. See also section "DVM transmittal" user interface (Page 83).

2. Click the "New folder" button.

3. On the "General" tab in the "New folder" window, enter a name for the folder and confirm with "OK".

4. On the symbol bar of the "DVM transmittal" user interface, click the "New transmittal" button.

Transmittals 7.3 Sending a transmittal


5. On the "General" tab in the "Transmittal" window, enter a name for the transmittal.

6. In the "Transmittal" window, open the tab "Attributes > Head data".

See also section "Transmittal" window, "Head data" tab (Page 84).

7. Select a type from the "Transmittal type" list.

The transmittal behaves differently depending on which transmittal type is selected.

The transmittal is created in the transmittal table. See also section "DVM transmittal" user interface (Page 83).

8. Open the "Documents" tab in the "Version content" area.

9. Drag&drop documents or queries from the Navigator to the tab.

These documents and queries are part of the transmittal.

10. To add additional documents, open the "Additional documents" tab and drag&drop documents from the Navigator to the "Additional version documents" section.

See also section "DVM transmittal" user interface (Page 83).

Result You have created a transmittal that you can send. See also section Sending a transmittal (). The transmittal has the status "New".

7.3 Sending a transmittal

Procedure To send a transmittal, proceed as follows:

1. Once you have added all the required documents to the transmittal, use the list within the "Actions" column to select for each document an action that is to be executed on sending.

2. On the symbol bar, click on the button "Send transmittal".

The transmittal is stored in the form of a ZIP file in the directory you specified in the project properties. See also section Preparing to create transmittals (Page 35).

The ZIP file is given an index as a suffix.

Example The name of the transmittal in COMOS is "TR1". The ZIP file created is called "TR1_0001.zip".

Transmittals 7.4 Receiving a transmittal


Result You have sent a transmittal. It is given the status "Sent".

You can edit the transmittal files outside of COMOS by extracting the ZIP file. Following extraction, you will receive an XML file which defines the assignments between the actual documents and the corresponding documents in COMOS, as well as a "DOCUMENTS" folder containing all the documents.

7.4 Receiving a transmittal

Requirements You can only receive new versions of a transmittal if it is of type "Revision transmittal" or "Document transmittal".

Procedure To receive a transmittal, proceed as follows:

1. Create a ZIP file containing the documents that you previously sent from COMOS and edited outside of COMOS.

2. Create the ZIP file in the same directory where you stored the ZIP file you sent.

3. Add all or some of the files you sent previously to this ZIP file.

If you want to add additional files, you first need to edit the XML file of the transmittal before you receive a transmittal. See also section Adding new documents outside of COMOS before receipt (Page 38).

4. Give the ZIP file you create the same name as the ZIP file that was created on sending, but set the index number to one higher.

Example: If the ZIP file created after sending is called "TR_0001.zip", then the ZIP file for receiving must be called "TR_0002.zip" in order for it to be recognized.

5. In the "DVM transmittal" user interface, click the "Receive transmittal" button.

The new version is displayed in the "Version view" area.


7. For each document, select an entry from the "Action" column.

8. Open the context menu of the documents and select the "Execute action" command.

The "Mandatory fields" window opens in the case of document transmittals, as a new version of the documents is created. If required, you can change the properties of the documents here.

Transmittals 7.5 Adding additional documents to a transmittal


Result You have received a new version of the transmittal. The transmittal is given the status "Partially received" or "Completely received". You are no longer able to edit it.

7.5 Adding additional documents to a transmittal

7.5.1 Adding new documents outside of COMOS before receipt To add additional documents to a transmittal outside of COMOS after sending, edit the XML file that was stored in the ZIP file when the transmittal was sent.

Procedure To add new documents prior to receipt, proceed as follows:

1. Open the XML file.

2. Copy the last element ("Document") in the XML file to the same layer.

3. Replace the "Dummy" wildcard of the "FileName" attribute with the exact name of the file you wish to add.

4. Replace the "Dummy" wildcard of the "FileType" attribute with the file type you wish to create in COMOS. Set one of the following values:

– "COMOS_REPORT": Creates a report during receipt.

– "DVM_DOC": Creates a document with version management during receipt.

– "QUERIES": Creates a query during receipt.

– "GENERAL_DOC": Creates a copy of the document during receipt. The document does not have version management.

– "UNKNOWN_DOC": No action.

5. Store the new document in the "DOCUMENTS" folder and create a ZIP file containing this folder and the edited XML file.

6. Give the ZIP file for the new version an appropriate name.

See also section Receiving a transmittal (Page 37).

7. In the "DVM transmittal" user interface, click the "Receive" button.

The new version is displayed in the "Version view" area.


9. For each document, select an entry from the "Action" column.

10. Open the context menu of the documents and select the "Execute action" command.

For the newly added document, in the "Unit location label" field of this window you must specify the node under which the new document is to be created in COMOS.



Result You have added a new document to a transmittal outside of COMOS and imported the document into COMOS.

See also Adding documents to the transmittals on the master data side (Page 80)

7.5.2 Adding new documents within COMOS after receipt

Procedure To add additional documents to a sent or received transmittal in COMOS, proceed as follows:

1. Double-click on a transmittal in the transmittal table.

The properties of the transmittal open.

2. Open the "Attributes > Head data" tab.

3. Select "New" from the "Status" list.


A new version of the transmittal is created in the "Version view" area.

If a new version is not displayed, update the "Version content" area by, for example, selecting a different transmittal and then selecting the one you want again.

5. Open the "Documents" tab.

6. Drag&drop additional documents to the tab.

Result You have extended the transmittal and can re-send it.


DVM document package 8

A DVM document package is used for bundling together multiple documents and compiling them in a package. You cannot edit individual documents in a package; you can only specify settings and processes for the package as a whole. Different versions of the package are created as part of this.

You can carry out the following actions in the usual way for document packages:

● Check in and check out

● Version management

● Export

The process of importing a document package is different from the standard bulk import process. See also section Importing DVM document packages (Page 42).

8.1 Creating a DVM document package

Procedure To create a DVM document package, proceed as follows:

1. Drag&drop a document to the Navigator.

2. In the "Navigator" window, activate the options "Create document with version management" and "Create package".

See chapter "Navigator" window (Page 86).

3. Complete the fields marked in red in the "Mandatory fields" window. When doing this, select the "Units" node in the "Unit location label" field.

A package is created under the "Units" node. The file you inserted in the Navigator is part of the package.

4. Click on the "Package configurator" entry in the context menu for the package.

The "Configurator" user interface opens.

5. To add additional files to the package, click the "Add file" button in the package configurator.

The documents that have just been added are included in the package configurator.

DVM document package 8.2 Importing DVM document packages


6. To change the sequence of the documents in the package, click on one of the arrow buttons.

The sequence in the package determines the following:

– The sequence in which the documents are printed

– The sequence of the documents in a PDF when the PDF is created

– The sequence in which the documents are revised.

7. Click "OK" to save the package.

"Include documents" plugin You can also create a DVM document package using the "Include documents" plugin. See chapter Importing documents with the "Include documents" plugin (Page 15).

8.2 Importing DVM document packages The process of importing DVM document packages is the same as importing documents in bulk. FTA1 mode is used for this purpose. See also section FTA1 mode (Page 19). The import varies according to the data you have entered in the Excel table CPlugInFileTransAttribute.xls .

Procedure To enter the data for importing a document package, proceed as follows:

1. Open the Excel table CPlugInFileTransAttribute.xls.

2. Open sheet "FTA1".

3. Create a new entry in the sheet.

4. Enter the value "Package" in the "FileName" column.

5. In the remaining columns, enter the relevant values as normal.

Do not use the same MasterID for a package as you have used for a document on the same sheet.

6. Open sheet "Package".

7. Create an entry for each document that you want to include in the document package.

8. For all documents, enter the same value in the "MasterID" column that you have entered for the document package on sheet "FTA1".

The documents are assigned to a package by means of the MasterID.

9. In the "FileName" column, enter the exact file names of the documents including their file type.

10. In the "DirPath" column, enter the path to the directories in which the documents are located.

11. In the "Sequence" column, enter a number for each document in ascending order.



12. Enter a description for the documents in the "Description" column.

13. Save the Excel table.

14. Import the documents.

See also section Performing bulk import (Page 23).

Result The document package is created at the point you specified in the Excel file.


Version history 9

Introduction When you check in or check out a document, COMOS saves many versions of the document. Each version is saved physically in the COMOSDB.

Note

Do not change the DVM documents outside of COMOS. This can lead to loss of data.

By way of the version history you can view the various versions of the document and roll back to the earlier versions if necessary.

You can

● view

● open

● print earlier versions

Version history 9.1 Opening the version history


9.1 Opening the version history

Procedure To open the version history, proceed as follows:

1. Right-click in the Navigator on the document whose version history you want to view.

2. Select the "Version history" command from the context menu.

The "Version history" window opens:

3. To open a version of a document in the version history, double-click on an entry in the

"Version" column.

"Version history" tab When you select the "Version history" tab the following information is available:

Control elements Meaning "Project versions" option The "Project versions" option is only visible when you are in a

working layer. When the "Project versions" option is selected, only the versions that were created in the current layer are displayed.

"Unit versions" option The "Unit versions" option is only visible when you are in a working layer. When the "Unit versions" option is selected, only the versions from the released area and the latest project version are displayed in the version history.

"Version" column Displays the version number.



Control elements Meaning "Check in date" column Displays the date when the document was checked in. "Check out date" column Displays the date when the document was checked out. "User" column Displays the name of the user who checked the document in or out. "Revision" column Displays the number of revisions of a version. "Mandatory fields" option If the "Mandatory fields" option is selected, the version-related

metadata is displayed to you in the lower area of the version history. "Comments" option If the "Comments" option is selected, a list is displayed below the

option. When you select the "Check in comment" command from the list, the check in messages of the marked version are displayed in the lower area of the version history. To view check out messages, select the "Check out comment" option from the list.


Exporting and reloading documents 10

Introduction COMOS enables the export of documents with all their components, e.g. to a local file directory of the user or an FTP upload folder. You select the corresponding destination directory prior to the export. With this you can make documents managed in COMOS accessible to your customers and subcontractors.

10.1 Exporting documents

Procedure To export a document, proceed as follows:

1. Right-click on the document you want to export.

2. Select the "Export" command in the context menu.

3. In the "Export" window you enter the export directory directly in the "Export directory" field or select it via the "Directory selection" button.

4. In the "Subcontractor" field you enter the name of the subcontractor who you want to access the document.

5. Enter a comment in the "Comment" field.

6. Click "OK" to start the export.

Result The document is checked out during export and hence is automatically locked. The lock is removed as soon as you reload the document.

10.2 Undo export

Procedure To discard changes you made to a checked out document, proceed as follows:

1. Right-click on the checked out document.

2. Select the "Undo export" command in the context menu.

Exporting and reloading documents 10.3 Permanent export


Result No new version of the document is created.

See also Reloading documents ()

10.3 Permanent export

Procedure To export documents permanently, proceed as follows:

1. Right-click in the Navigator on the document you want to export.

2. Select the "Export" command in the context menu.

3. In the "Export" window you enter the export directory directly in the "Export directory" field or select it via the "Directory selection" button.

4. In the "Subcontractor" field you enter the name of the subcontractor who you want to access the document.

5. Enter a comment in the "Comment" field.

6. Select the "Permanent export" option.

Result When you select this option, COMOS immediately exports the document again after the reload operation.

See also Reloading documents (Page 50)

10.4 Reloading documents

Procedure To reimport an exported document, proceed as follows:

1. Right-click on the document you exported.

2. Select the "Reload" command from the context menu.

The "Import comment" window opens:

3. In the window enter a comment on the import process.

Exporting and reloading documents 10.4 Reloading documents


4. Click "OK" to confirm your input.

Another window opens in which you can edit the metadata of the document as required.

5. To import the document, click on "OK" in the window.

Result The exported document is reimported.

Exporting and reloading documents 10.4 Reloading documents



Bulk processing of documents 11

Introduction With the help of queries, you can check in or check out documents in bulk in COMOS.

11.1 Checking out documents in bulk

Procedure To check out documents in bulk, proceed as follows:

1. Click the "Extra > Query > DVM queries > Bulk checkin / checkout" menu.

2. In the Navigator, drag&drop the node under which the documents are located into the "Start object(s)" field.

Then all the documents under the node are listed in the table.

3. From the table select the documents that you want to check out.

4. Right-click on the selected documents.

5. Select the "Check out" command in the context menu.

6. In the "Check out comment" window, click one of the following options:

– "Yes"

To enter a single comment for multiple checked-out documents.

– "No"

To enter a separate comment for each checked-out document.

– "Cancel"

To cancel the check out procedure.

7. In the next window, depending on your choice of "Yes" or "No", enter one or more comments and click "OK" to confirm your input.

Bulk processing of documents 11.2 Checking in documents in bulk


11.2 Checking in documents in bulk

Procedure To check back in the documents you checked out, proceed as follows:

1. In the window, select the documents that you want to check in.

2. Right-click on the selected documents.

3. Select the "Check in" command in the context menu.

4. In the "Check in comment" window, click one of the following options:

– "Yes"

To enter a single comment for multiple checked-out documents.

– "No"

To enter a separate comment for each checked-out document.

– "Cancel"

To cancel the check in.

5. In the "Check in comment" window, enter one or more comments on the check in process and click "OK" to confirm your input.

Another window opens where you can edit the metadata for each to be checked in document as required.

6. To check in the document, click the "OK" button in the window.

11.3 Calling the "My most recent documents" query

Procedure COMOS allows you to display the last ten imported documents. To view the last documents, click the "Extra > Query > DVM queries > My most recent documents" menu.


Working with xReferences 12Introduction

If you are importing DGN or DGW drawings to COMOS that contain references to other files, COMOS checks if the references already exist in the system. If the references already exist, COMOS creates the links to the references along with the import of the drawings.

If the references do not yet exist, COMOS asks if the references to the files should also be imported.

Viewing DGN or DGW drawings When you open DGN or DGW drawings with references to other files in COMOS, the references of the drawings are also automatically opened.

Editing DGN or DGW drawings When you open DGN or DGW drawings with references to other files in COMOS for editing, the references of the drawings are also automatically opened but cannot be edited.

Working with xReferences



Workflow Management with PQM 13

Introduction The following section requires that you are familiar with the basic functionalities of COMOS workflow management. You find more information on this topic in the "Workflow" manual.

PQM supports the following workflows:

● Checking documents in and out

● Document request

● Importing documents

Requirement To be able to work with workflows, you must first enable workflow management in the project properties.

Procedure To enable workflow management, proceed as follows:

1. To open the project properties, double-click on the current project in the Navigator.

2. On the "Workflows" tab choose the "Activate workflows" option.

3. Click "OK" to save your settings and close the project properties.

13.1 "Checking documents in and out" workflow

Procedure Workflow allows you to check documents in and out in bulk. To work with workflow, proceed as follows:

1. Right-click on the current project in the Navigator units tree.

2. Select the "New > @Project management Project Management Template" command in the context menu.

3. Switch to the "Base objects" Navigator tab.

4. Select the "Checking documents in and out" object under the "@WF Workflow management > WF Workflows > DRW document requirement workflow" object structure and drag&drop it as a new tab in the "Details" window.

5. Switch back to the "Units" tab in the Navigator.

Workflow Management with PQM 13.1 "Checking documents in and out" workflow


6. Now drag&drop the "Check COI documents in and out" object from the "Details" window to the "@ProjectManagement" object in the Navigator.

The "Checking WF1 documents in and out" object is created.

7. Double-click on the "Checking WF1 documents in and out" object.

8. Click in the "Checking WF1 documents in and out" window on the "Start workflow" button.

Result In the Navigator under the "Checking WF1 documents in and out" node the object "T01 check out documents" is created to check out documents.

13.1.1 Checking out documents with workflow

Procedure To check out the documents in bulk, proceed as follows:

1. Double-click on the "T01 check out documents" object to open the "Data" tab of the task object.

2. Drag&drop one PQM document from the Navigator into a field of the "Document" column.

3. Click the "Check out documents" button.

Result The documents are checked out. At the same time, the output object "T02 check in documents" is created to check in documents.

13.1.2 Checking in documents with workflow

Procedure To check in the documents in bulk, proceed as follows:

1. Double-click on the "ACT - T02 check in documents" object to open the "Data" tab of the task object.

2. To suppress the mandatory fields during the check in, activate the "Do not show mandatory fields" option.

3. Click the "Check in documents" button.

Result The documents are checked in. The task object is marked by the prefix "Done", meaning completed.

Workflow Management with PQM 13.2 "Document request" workflow


13.2 "Document request" workflow

Overview This workflow enables you to map a subcontractor scenario. It automatically sends E-mails to subcontractors with order descriptions and document attachments and schedules the orders. Moreover, the workflow monitors if deadlines for the orders have been adhered to and if the deadlines have passed, reacts with E-mails that are sent as reminders to subcontractors.

13.3 "Import documents" workflow

Importing documents The workflow imports documents to COMOS in bulk using the "File transfer" plugin.

Workflow Management with PQM 13.3 "Import documents" workflow



Extended PQM functions 1414.1 Options

Requirement You dispose of a license for the extended PQM functions.

With the extended PQM functions additional options are available to you:

Support during qualification planning ● Defining the project area of application (system parts / systems)

● Defining project phases

● Specifying responsibilities and user roles

● Specifying the document catalogs to be used

● Defining copy templates to be used for the internal and external documentation

● Defining the documentation requirement per system and planning phase

● Determining the qualification requirement

Support for qualification management ● System-supported creation of document types depending on the planning phases

(DEP=Document Execution Plan)

● System-supported creation of qualification documents for relevant systems

(Q-DEP=Qualification Document Execution Plan)

● Tracking of documents (who has to supply what by when?)

● Overview of the job status with the Job Manager

● Document viewing and acceptance in accordance with the workflow

● Information to the user via e-mail

● Checking of the completeness before phase completion

● Creation of overview documents for the phase completion

Extended PQM functions 14.2 Roles


14.2 Roles

Basics Roles with different responsibilities were implemented for the utilization of the extended functions of a PQM project. When required you can deviate from the task distribution presented here. One person can carry out multiple tasks.

Roles ● Administrators

– Adapting base data

– Updating the document catalog

See also section Adapting base data (Page 81), Chapter Updating the document catalog (Page 82), Chapter "PQM project config" tab (Page 86).

● Configurators

– Configuration Tools module license required

– Setting up a PQM project

– Team setup, creating roles and assigning the team members

– Selecting phases

See also section Configuring the tree structure and course (Page 63), Chapter Configuring the qualification evaluation (Page 67).

● Persons responsible for project / qualification

– Configuration Tools module license required

– Specifying the area of application of the PQM project (system selection)

– Carrying out quality evaluations of the system

– Specifying the documentation requirement (DEP, Q-DEP)

– Monitoring the status of the documentation creation

– Carrying out a phase transition

See also section Completing the phases (Page 65).

● User

– Creating and evaluating documents

– If required, approving documents

See also section Creating and filling documents (Page 65).

Extended PQM functions 14.3 Tree structure and responsibilities


14.3 Tree structure and responsibilities The structure of the PQM node is adapted to the workflow:

Path in the Navigator Description "PQM PQM nodes" Is specified by the configurator. "PQM > P001 PQM project" Is specified by the configurator. "PQM > P001 > CONF Configuration" Is created automatically when the project is created. "PQM > P001 > CONF > SOB Search objects" Is created automatically when the project is created. "PQM > P001 > CONF > SOB >SQ1 Definition of the planning objects"

Is created automatically when the project is created. Settings are carried out by the configurator.

"PQM > P001 > CONF > PHC Phase configuration" Is created automatically when the project is created. Phases are created by the configurator via the user interface.

"PQM > P001 > CONF > PHC > IN Initial phase" "PQM > P001 > CONF > PHC > CD Process engineering" "PQM > P001 > CONF > PHC > BD Basic Design" "PQM > P001 > CONF > PHC > DD Detail Design" "PQM > P001 > CONF > PHC > C&I Construction and installation" "PQM > P001 > CONF > PHC > COM Commissioning" "PQM > P001 > CONF > PHC > DQ Design qualification" "PQM > P001 > CONF > PHC > IQ Installation qualification" "PQM > P001 > CONF > PHC > OQ Function qualification" "PQM > P001 > CONF > PHC > PQ Performance qualification" "PQM > CONF > PHC > QHO Qualification transfer phases"

The user creates documents in the phases below the document type folder and fills them. Each phase is completed by the person responsible for the project.

"PQM > P001 > CONF > MQS Management queries" Are created automatically when the project is created. "PQM > P001 > CONF > MQS > 020 Assign a user" Roles can be created by the configurator automatically

or depending on the configuration manually at the master object.

"PQM > P001 > CONF > MQS > 040 Creating / Updating a document catalog"

Is carried out by the administrator.

"PQM > P001 > CONF > MQS > 050 Quality risk analysis" Is carried out by the configurator.

14.4 Configuring the tree structure and course As a configurator you create the tree structure for the extended PQM functions and configure the course. See also section Roles (Page 62).

Detailed configuration options are available to you when editing individual phases.

Settings for the course of the qualification process are carried out later on. See also section Configuring the qualification evaluation (Page 67).

Extended PQM functions 14.4 Configuring the tree structure and course


Requirement You have created users in the "USERS" project.

You can find additional information about this topic in the "Rights" manual, keyword "Creating a person in the "USERS" project".

Procedure 1. In the Navigator select your planning project and in the shortcut menu select the

command "Create PQM nodes".

The PQM node is created.

2. Select the "PQM node" and then the command "New > PQM project" in the shortcut menu.

The PQM project is created.

3. In order to compile the desired objects of your system in a query select the node "PQM > P001 > CONF > SOB Suchobjekte > SQ1 Definition of the planning objects" and open the query SQ1.

The name of queries in this node must always begin with "SQ".

Further information about this topic is available in the "Queries" manual, keyword "Standard query planning objects".

4. Open the properties of the project and select the "Attributes > Project course" tab.

5. In the "Phase configuration" control group select the phases that your project should contain.

6. Select the desired catalog in the "Document catalog" field. The standard entry is "Document catalog".

7. Use the "Assign users" button to assign predefined roles to the users.

Use an object from the "USERS" project as the start object.

You can find additional information about this topic in the "Rights" manual, keyword "USERS".

Extended PQM functions 14.5 Creating and filling documents


8. In order to call up the document requirements list (DEP) or qualification document requirements list for individual phases, click the line of the respective phase in the DEP/QDEP control group.

The "DEP document requirements list" tab opens.

9. Activate the desired document types line-by-line for an object and subsequently activate

the "Execute" option.

After the "Execute" option has been selected, the activated document type folders are created in the Navigator at the corresponding object of this phase.

Note

You cannot undo the creation of the selected document type folders.

Result: The preparations for the editing of individual phases by the user are then completed.

14.5 Creating and filling documents As a user you fill the document type folders with documents that you want to edit subsequently. See also section Roles (Page 62).

Procedure 1. In the Navigator select the document type folder and in the shortcut menu select the

command ""New > <Respective document>.

The new document is created below the document type folder in the Navigator.

2. Open the new document by double-clicking it and edit it.

Optional: View the assignment of the document type folder If you want to view the assignment of the document type folder, select a document type folder, open its properties and change to the "Phase assignment" tab.

14.6 Completing the phases As the person responsible for the project you complete the respective phase. See also section Roles (Page 62).

Extended PQM functions 14.6 Completing the phases


Requirement The required documents have been created and filled.

Procedure Select the desired phase in the Navigator and select the "Complete phase" command in the shortcut menu.

Result If there are relevant documents under the system (engineering) these documents from the engineering are stored as a reference when the phase is closed.

Note Effect of the phase completion

The phase is locked. You can no longer edit it.

Extended PQM functions 14.7 Configuring the qualification evaluation


Graphical overview After the "Complete phase" has been selected, the following system sequence is carried out automatically:

NoIs the PQM project option"Print summary"

active?

14.7 Configuring the qualification evaluation As the configurator you carry out the settings for the "Qualification risk analysis". See also section Roles (Page 62).

Example: You decide to realize a risk analysis for contact surfaces in the foodstuff processing area.

Extended PQM functions 14.7 Configuring the qualification evaluation


Requirement Your project has reached a state in which the qualification evaluation can be carried out.

Procedure 1. Open the properties of the project and select the "Attributes > Project course" tab.

2. Click the "Specify qualification requirement" button.

The "Qualification risk assessment" query is displayed.

The selected object quantity is displayed in the first columns.

3. In order to answer the questions for the displayed objects click in the cells of the respective columns and select "Yes" or "No" from the selection.

If you reply "Yes" to at least one question for the displayed objects, the activation is displayed in the "System is Q-relevant" column.

4. If the activation is displayed in the "System is Q-relevant" column, specify the assignment to the individual qualification phases by activating the options in the columns "Design qualification", Installation qualification", "Function qualification", "Performance qualification" and "Qualification transfer phase".

5. Save your settings.

Result You have specified the object quantity of the engineering objects to be qualified.

These are available to you for further editing in the qualification document requirements lists of the quality phases. In the individual quality phases you can create document type folders as in other phases.

The user can create and fill documents in the document type folders. See also section Creating and filling documents (Page 65).


Administration 15

Requirements To launch PQM you will need the following requirements:

● PQM license

● NTFS drive NTFS drive for managing metadata.

Additional functions You can expand PQM with the following functions:

● eSign The "eSign" function allows you to control the individual document revision steps based on an electronic signature. You find additional information on this topic in the "Revisions" manual, keyword "eSign".

● eStamp The "eStamp" function is a constituent part of "eSign", and enables the eSign signature to be visualized on the printed document. You find more information on this topic in the "Revisions" manual, keyword "eStamp".

● AutoVue license Permits direct opening of imported documents (such as CAD documents) in COMOS without having to install the applications with which the documents were created on your computer.

15.1 Project settings for PQM Before you can work with PQM, you first need to make a number of project settings.

Procedure To make project settings for PQM, proceed as follows:

1. To open the project properties, double-click on the current project in the object structure of the Navigator.

2. Select the "Options > PQM options" tab.

Administration 15.1 Project settings for PQM


"PQM Options" tab The following table gives you an overview of the project settings you can select on the "PQM Options" tab:

Control element Description "Check in mechanism" list By way of this list you define how many versions of a document are to be saved

when it is checked in or imported into the system: "Only current version"

Only one file is saved "All versions"

All versions of the file are saved "Number of versions is project-dependent"

If you choose this option you can define the number of versions yourself in a window of the same name.

"Number" field If you select the "Number of versions is project-dependent" entry from the "Check in mechanism" list, the entered value is displayed in the "Number" field.

"Default working folder" field This directory is an optional directory for local copies of checked out documents. By default, COMOS identifies the directory path from the "TEMP" environment variable of the current user. If this environment variable does not exist, the "Default working directory" is applied. You can select the directory by clicking the "..." button.

"DragDrop-import for PQM" option If this option is active, the PQM version and metadata management is triggered. "Document base object" field Click the [...] button to select the base object that is to be assigned to the PQM

documents during the import. "Create temporary docs under" field "..." Set pointer button

Clicking the button opens a window to select an object under which COMOS can create temporary wildcards during the import of documents. The wildcard is used to save metadata for the document to be imported before it has been imported to COMOS. After the import is complete, the wildcard becomes a document that is arranged in the COMOS Navigator according to the unit label.

"Remove pointer" button

Click this button to remove the object reference. "Navigate, Properties" button

This button is only active when an object reference is entered. It opens a context menu with functions enabling you to get more information on the entered object reference.

"Email sender" field If you want to use the PQM E-mail plugin, you need to store the E-mail address of the sender here.

"Email server (SMTP)" field If you want to use the PQM E-mail plugin, you need to store the address of the E-mail server via which the E-mails will be sent.

"Folder base object" field Drag&drop the base object on which the transmittal folder object is to be based into this field. The master object is located under "@02 > 130 > TR01 Transmittal structure folder".

"Container base object" field Drag&drop the base object on which the transmittal container object is to be based into this field. The master object is located under "@02 > 130 > TR02 Transmittal container".

Administration 15.2 Project settings for bulk import of documents


Control element Description "Version base object" field Drag&drop the base object on which the transmittal version object is to be based

into this field. The master object is located under "@02 > 130 > TR03 Transmittal version".

"Directory" field Here you define a folder on your drive in which the transmittal is to be saved following sending. In this folder, you also create new versions of transmittals that you have sent and wish to re-import into COMOS.

15.2 Project settings for bulk import of documents

Procedure To make project settings for importing documents in bulk, proceed as follows:

1. Open the project properties.

2. Select the "Configuration file transfer" tab.

Administration 15.2 Project settings for bulk import of documents


"Configuration file transfer" tab The following table provides an overview of the project settings you can make on the "Configuration file transfer" tab:

Control elements Description "Source folder with documents" field Before starting the document import, click the "..." button to define the transfer

directory for the import. This directory has to contain one of the following files: The file CPlugInFileTransAttribute.xls or

CPlugInFileTransAttribute.mdb. Depending on the name of the first worksheet of the Excel table (FTA or FTA1), the following differences apply: – FTA mode (old mode):

The documents and the Excel spreadsheet with the metadata of the documents must be located in the selected folder. The folder is the transfer directory from which the documents will later be imported. See also section Metadata management with Excel (Page 18).

– FTA1 mode (new mode):

In this case only the Excel spreadsheet is required in this folder. The documents can be imported from different paths. You set the path to the document in the DirPath column of the Excel table. See also section FTA1 mode (Page 19).

The CPlugInFileTransAttribute.xml file. The CPlugInFileTransAttribute.csv file. The

CPlugInFileTransPackages.csv file has to be located additionally in the transfer directory In order to import the DVM document package.

See also section Importing documents in bulk (Page 17). "Folder for protocol file" field COMOS creates an import log during the document import. You select the

directory in which the import log is to be saved via the [...] button. Format of the log file in case of a successful import: "<project name>-CPlugInFileTrans_ Successes.CSV" Format of the log file in case of an erroneous import: "<project name>-CPlugInFileTrans_ Errors.CSV"

"Folder for MDB" field COMOS creates an Access database during the import of the documents which contains information on which documents have already been imported. For each document that you import, COMOS checks if it has already been imported in the Access database. If is has, a new version is created for the existing document. You select the directory in which the Access database is to be stored via the [...] button.

"Structure separator" list From the list you select the structure separator which separates the unit label and document group nodes in the Excel table. Example for the "Dot" structure separator: 00.H1.T1

"Script user defined separator" field Click the "..." button to open a Navigator window and select a self-written script file in the object structure.

"Standard tables for mapping" field Shows the object path to the mapping tables for the Excel table CPlugInFileTransAttribute.xls, under the "Standard tables" object in the base project.

"Chosen table for mapping" list Selection of the mapping table by which the the columns in the Excel table and the mandatory attributes in COMOS are linked.

Administration 15.3 Viewer settings


Control elements Description "Standard tables for MDB" field Shows the object path to the mapping tables for the Access database, below

the "Standard tables" object in the base project. "Chosen table for MDB" list Selection of the mapping table by which the the columns in the Access

database and the mandatory attributes in COMOS are linked. "Groups" list From the list you select the user group that is allowed to perform the import.

15.3 Viewer settings Here you specify the viewer program in which the to PQM imported documents are opened.

Procedure To call the settings, click the "Plugins > PQM > Viewer settings" menu.

The viewer settings open.

The following table describes the columns of the list in the viewer settings:

Column Description "File type or extensions"

Contains the name of the file type.

"Description" Contains the description of the file type. "Program" Contains the name of the calling program. To change the program of the

current file link, click the "…" button. A window opens in which you can select a different program from the "Display mode" list: "AutoVue"

All documents of the current file type are opened with AutoVue. "Adobe PDF"

This setting may be useful for PDF documents. "External program"

Activate this option to link an external program. Then you can directly enter the path or by clicking the "…" button in the file selection.

"Default" All documents of this file type are opened with the program entered in the Windows registry.

"Default" Labels the default setting of the administrators, as long as this option is active. If the user configures an own viewer, the option is deactivated. Right-click on the row and choose "Reset" to restore the default setting of the administrator.

Administration 15.4 Defining the check in dialog window


15.4 Defining the check in dialog window If you have defined the "Mandatory fields" check in dialog window at a document base object (DVM), it will open whenever you import a document with version management or check in a document. It also serves as the basis for the search dialog window during the attributed search.

During check in, all the values (among others) that you enter in the mandatory fields are applied at the following points:

● Properties of the document in COMOS

● File properties of the document in the Windows Explorer

To view the file properties, right-click on a version of a document in the Windows Explorer. The versions are stored in the following directory, for example:

"<Database directory> > <Project folder> > AA"

Open the properties, followed by the "User defined" tab.

Note

Do not change the DVM documents outside of COMOS. This can lead to loss of data.

In the COMOSDB, the base definition of the check in dialog window is made by way of the catalog attributes, in the base project below the "PQM > @Y > 1 > 03 > 02 > Mandatory fields" object node.

Procedure To edit the check in dialog window, proceed as follows:

1. Open the base project.

2. Switch to the "Base objects" tab in the Navigator.

3. Double-click in the object structure on the "PQM > @Y > 1 > 03 > 02" object.

4. Switch to the "Attributes > Mandatory fields" tab.

In design mode, you can add new attributes, label mandatory fields, or store scripts for the import here.

Mandatory fields:

Edit mode "Values in XML (limited functionality) - high priority" or "Editable - high priority"

The search will run faster if you select the edit mode "Values in XML (limited functionality) - high priority".

Normal fields:

Edit mode "Values in XML (Limited functionality)" or "Editable - normal"

Administration 15.5 Connecting MS Office to COMOS


Result ● The "Mandatory fields" search dialog window applies as the base definition for further

variants of the check in dialog window in the document base object.

● In addition, the "Mandatory fields" check in dialog window is used as a stripped copy, without mandatory fields and scripts, for the "PQM > @Y > 1 > 03 > 06 > Mandatory search criteria" search dialog window.

15.5 Connecting MS Office to COMOS

Procedure To prepare the connection between MS Office and COMOS, proceed as follows:

1. Double-click the "MsoAddInInstaller.exe" file in the "Bin > OCX > PQM" folder of your COMOS installation.

2. Click the "Register" button.

3. In the "config" COMOS subfolder, open file "Comos.Pqm.MsoAddIn.config".

4. Enter the absolute path to your database in the "Value" attribute under "key="Database".

5. Enter the exact name of the project into which you wish to import Office documents in the "Value" attribute under "key="Project".

6. If you use a working overlay enter the ID of the working overlay in the "Value" attribute under "key="WorkingOverlay".

Result An add-in of COMOS was installed in Office applications.

15.6 Defining the description for imported documents When importing DVM documents, you can take the description of the document concerned either from the "Subject" field in the "Mandatory fields" window or from the document name.

The subject is used as the description by default. This is defined in the "OnDocumentCheckIn (Document)" script of the document base object.

Procedure To use the document name as the description, proceed as follows:

1. In the base project, open the "OnDocumentCheckIn (Document)" script at the document base object.

2. Comment out the code section under the comment Use subject entry of Mandatory tab as description.

Administration 15.7 Defining the attributed search


3. Change to the engineering project.

4. Select the entry "DQM options" from the context menu of an imported document.

5. In the "DQM options" window, select the option "Use file name as description".

6. In the "Save settings" window, select the project and user to which this setting should apply.

Result The file name will be used as the description for all documents you import in future.

15.7 Defining the attributed search

Requirements If you import documents into PQM via version management, you enter the metadata of the document defined as mandatory fields in the "Mandatory fields" window.

In COMOS the possible input fields for metadata are defined and the mandatory fields are labeled in the check in dialog window.

To search documents for metadata via the attributed search in COMOS, a copy of the check in dialog window is used as the search dialog window. Usually the search dialog window here represents a version of the check in window stripped of scripts and mandatory fields.

To define the attributed search, the following steps are required in the base project:

● Define check in dialog window

See also section Defining the check in dialog window (Page 74).

● Define search dialog window

● Define document base object (DVM)

● Make search dialog window available

15.7.1 Base definition of the search dialog window In the COMOSDB the base definition of the search dialog window is made by way of the catalog attributes in the base project under the "PQM > @Y > 1 > 03 > 06 > Mandatory" object node.



Procedure To open the search dialog window (mandatory), proceed as follows:

1. Double-click in the object structure on the "PQM > @Y > 1 > 03 > 06" object.

2. Switch to the "Attributes > Search criteria" tab.

The search dialog window is a stripped copy of the check in dialog window "PQM > @Y > 1 > 03 > 02 > Mandatory". Here all mandatory fields and scripts have been removed.

Result The search dialog window "PQM > @Y > 1 > 03 > 06 > Mandatory search criteria" defined here applies as the base definition for the attributed search.

15.7.2 Define document base object (DVM)

Procedure You define the document structure to be applied by PQM when importing documents by way of version management in the PQM options. See also section Project settings for PQM (Page 69). The document base object is used to determine which check in dialog window is called for the import and which for the document properties. These check in dialog windows represent expandable and adaptable variants of the catalog attributes in the COMOSDB. See also section Defining the check in dialog window (Page 74).



"Mandatory fields" check in dialog window When you import documents to PQM by way of version management, this check in dialog window is opened as the input dialog window for the metadata.

To open the check in dialog window for the import, proceed as follows:

1. Double click in the object structure on the "PQM > @O > DVM >02" object.


"Man1 Mandatory fields" check in dialog window When you call the properties of a PQM document, the metadata is displayed in this non-editable check in dialog window.

To open the check in dialog window for the document properties, proceed as follows:



1. Double click in the object structure on the "PQM > @O > DVM >02" object.


Note

The name and description of the following tabs must not be changed in the document base object, as otherwise they could no longer be accessed in PQM: "Mandatory fields" "Man1 Mandatory fields"

15.7.3 Making the search dialog window available

15.7.3.1 Creating a base object

Procedure 1. Right-click in the object structure on the "@System > @Profiles > @AllUsers >FTSearch

> FTSearchTemplates" object.

Search dialog windows that were published under the "FTSearchTemplates" object are subsequently selectable in the full-text search.

2. Select the "New > Base object" command in the context menu.

Administration 15.8 Adding documents to the transmittals on the master data side


3. Enter "PQM" as the name.

4. Enter "Attribute search" as the description.

The description is offered subsequently for selection in the full-text search.


Result You have created the base object "PQM attribute search" for a new search dialog window. The search dialog window can be copied under the base object in the next step.

15.7.3.2 Copying a search dialog window

Procedure 1. Right-click in the object structure on the "PQM > @Y > 1 > 03 > 06 > Mandatory search

criteria" object.

2. Select the "Copy" command in the context menu.

3. Right-click in the object structure on the "@System > @Profiles > @AllUsers > FTSearch> FTSearchTemplate > PQM attribute search" object.

4. Select the "Paste" command from the context menu.

Result All preparations have now been made to call the attribute search by way of the "Plugins > Basic > Full-text search" menu option in a new PQM engineering project.

15.8 Adding documents to the transmittals on the master data side Carry out the default settings in the master project in order to supplement transmittals by default with predefined standard documents.

Administration 15.9 Administrating extended PQM functions


Procedure 1. Change in the master project to the node "@02 > 130 > TR03 Transmittal version".

This contains the following folders:

– TR01 Transmittal structure folder

– TR02 Transmittal container

– TR03 Transmittal version

2. In order to add documents to the transmittals insert documents into one of these folders by using the shortcut menu or by dragging-and-dropping external documents.

Depending on the folder under which you create the documents, the documents are available at different points later.

– Folder "TR01 Transmittal structure folder":

Documents that you create under the "Transmittal structure" master object, are displayed in the "Folder view" of the "DVM Transmittal" tab and can also be edited there. This is the only possibility of creating documents in the "Folder view" of the "DVM Transmittal" tab.

– Folder "TR02 Transmittal container":

Documents that you create under the "Transmittal container" master object are also created as a supplementary document "Additional transmittal documents" when a new transmittal container is created.

– Folder "TR03 Transmittal version":

Documents that you create under the "Transmittal version" master object are also created as a supplementary document "Additional transmittal documents" when a new transmittal container is created.

15.9 Administrating extended PQM functions

15.9.1 Adapting base data As an administrator you can adapt the base data of your PQM project to the utilization of the extended PQM functions. See also section "PQM project config" tab (Page 86), Chapter Roles (Page 62).

See also Extended PQM functions (Page 61)

Administration 15.9 Administrating extended PQM functions


15.9.2 Updating the document catalog

Procedure 1. Open the properties of the project and change to the "Attributes > PQM project config"

tab.

2. Click the "Create / update document catalog" button.

A query for updating the document catalog opens.

3. Combine the document type folders for the document catalog.

You find additional information on this topic in the "Queries" manual.

4. In order to execute the displayed script block click the "Execute" button.

After the script block has been executed, the document catalog set at the project is updated.

Note

The "Document catalog" selection list has to be located in the current project.

After updating only the document types selected above are contained in the document catalog.

5. Save your settings.


User interface reference 1616.1 "DVM transmittal" user interface

The "DVM transmittal" user interface consists of the following areas:

● Symbol bar

● Transmittal table

● "Folder view" area

● "Version view" area

● "Version content" area

Symbol bar The symbol bar is located at the upper edge of the user interface. It contains the following buttons for editing transmittals:

Button Description "New transmittal" Use this button to create a new transmittal. It is created in the

transmittal table. "Delete transmittal" If you select a transmittal in the transmittal table, you can delete it using

this button. "Send transmittal" Use this button to create a ZIP file containing the transmittal, in the

folder you have specified in the project properties. See also section Preparing to create transmittals (Page 35).

"Receive transmittal" Use this button to import a new version of a transmittal in the form of a ZIP file from the folder you specified in the project properties.

Transmittal table In this table you can see all the transmittals and their metadata that are in the folder you have selected in the "Folder view" area.

"Folder view" area The "Folder view" area contains all the folders you have created for transmittals. The folders are used for compiling and sorting transmittals.

"Version view" area The "Version view" area displays all the versions of a selected transmittal. New versions are created if, for example, you receive a transmittal that has been sent or set the status of a sent or received transmittal to "New" in its properties.

User interface reference 16.2 "Transmittal" window, "Head data" tab


"Version content" area The "Version content" area shows the properties, documents, and additional documents of a transmittal version on tabs.

Tab Description "Properties" This tab shows the properties of a version. The head data under the

"Attributes" tab is automatically entered by the program. However, you can also define it yourself.

"Documents" This tab contains documents and queries that are part of a transmittal version. You add documents or queries by moving them to the tab using drag&drop. You can only add new documents to a transmittal if the status of the transmittal is set to "New".

"Additional documents" Additional documents are part of the ZIP file that is created during the sending process. However, version management is not available for them. Examples of these documents are items of correspondence, a table of contents for the transmittal, or work instructions that relate to the transmittal documents. If you drag a document to the "Additional version documents" section, it is only added to the current version when sending is carried out. If you select the command "Move upward" from the context menu of a document in the "Additional version documents" section, then the document is moved to the "Additional transmittal documents" section. This document is added to every version of the transmittal.

16.2 "Transmittal" window, "Head data" tab The "Transmittal" window contains the "Attributes > Head data" tab. With the exception of the "Transmission type" list, the values of all the control elements are set automatically. However, you can also define the values yourself.

Once you have created a transmittal, you can also edit its head data at a later point. To do this, double-click a transmittal in the transmittal table in the "DVM transmittal" user interface. See also section "DVM transmittal" user interface (Page 83). Select the "Attributes > Head data" tab.

This tab contains the following control elements:

Control element Description "Author" field Enter the author of the transmittal in this field. "Date of creation" field In this field, you enter a date using the button "Set current date" or the

button "Select date".

User interface reference 16.2 "Transmittal" window, "Head data" tab


Control element Description "Transmittal type" list The following types of transmittal are available:

"Informative transmittal"

This type defines a transmittal that you can only send, not receive. "Revision transmittal"

This type defines a transmittal for carrying out revision checks or releasing documents. It automatically creates a new revision of documents if a new version of the transmittal has been created. You find additional information on this topic in the "Revisions" manual, keyword "Revisioning documents".

To use this type, activate the option "Create PDF file at first step" in the project settings on the "Options > Revision options" tab. You can only use this type for the most recent open revision.

"Document transmittal"

This type defines a transmittal that contains documents or queries to be changed. You can send and receive transmittals.

"Subject" field Enter the subject of the transmittal in this field. If you do not enter anything, "Transmittal container" will be entered automatically.

"Status" list The status of the transmittal is usually set automatically. However, you can also define it yourself. The following statuses are available: "New"

You can only add new documents within COMOS in transmittals with the status "New", and it is only these transmittals that you can send.

"Sent"

Blocks the transmittal. You cannot add any new documents or re-send the transmittal.

"Check"

Blocks the transmittal. You cannot add any new documents or re-send the transmittal. This status is set during receiving.

"Partially received"

If a transmittal that was sent previously does not contain all the documents that it did during sending, it is given the status "Partially received" when you receive it again. You cannot add any new documents or re-send the transmittal.

"Completely received"

If a transmittal that was sent previously contains all the documents that it did during sending, it is given the status "Completely received" when you receive it again. You cannot add any new documents or re-send the transmittal.

"Versions" field In this field, enter how many versions of a transmittal exist.

User interface reference 16.3 "Navigator" window


16.3 "Navigator" window The "Navigator" window opens when you drag an external document to the Navigator. You can define the import mode here.

Options Description "Create copy" This option creates a copy of the document in COMOS. "Create link" This option creates a link to the document. "Create document with version management"

This option creates a copy of the document in COMOS and saves it as a DVM document. You can manage different versions of the document. You cannot create a DVM document under another DVM document.

"Create package" You can only activate this option if you have already activated the option "Create document with version management". This option creates a DVM document package and stores the document in the package.

16.4 "PQM project config" tab As an administrator you can adapt the base data of your PQM project to the utilization of the extended PQM functions. See also section Extended PQM functions (Page 61).

In order to change the default settings open the properties of the project and change to the "Attributes > PQM project config" tab.

"Project settings" control group Control element Description "LLO base object" field Mandatory field. Link object that represents the engineering object in

the PQM- project. If appropriate, select a different base object.

"Document catalog" field Mandatory field. If appropriate, select a different document catalog. "Copy templates for references" field

Mandatory field. If necessary, change the template of the reference document that is created n-times in the reference folder.

"Folder for references" field Mandatory field. If necessary, change the base object of the reference folder.

"Print summary" option" When this option has been activated, the contained documents are printed out when a phase is closed.

"Create / Update document catalog" button

To call up the query "Create / update document catalog". See also section Updating the document catalog (Page 82).