Configuring a project

Configuration parameters

After starting logicDCMS, navigate to Application Manager Menu -> Base Tables -> ... more -> Configuration

Check the parameters in the configuration table. Most of them are self explaining.

See the explanation in the column at the right.
Essential for your project are:

• projectName
• supplierName (must be your companies name)
• ClientName (must be your client's name)
• parameters pointing to specific projectfolders: Check and set according to your networkfolder names
• parameters pointing to specific template files: Will by default point to the proper files already.
• defaultDocID: determines if your primary document identification is on clientDocID (set parameter to client) or internalDocID (set parameter to internal)

any other parameter can be configured in a later stage and will be discussed in one of the next chapters.

Application users

Users of logicDCMS have to be registrated in the employees table.
Navigate to Application Manager Menu -> Base Tables -> Employees
The first line in the table defines the application administrator. Don't change this line, you might need help of the administrator later on.
The second line is reserved for the primary document controller on your project. Change it accordingly.
The network login Name should correspond to the windows login Name of the Document Controller. Assign the value PDC as the role.
Any further line can be used for other users participating in this project.

Companies table

Companies involved in the project need to be defined in the companies table.
Navigate to Application Manager Menu -> Base Tables -> Companies
The first line in the table defines your own company. Enter the company name, an abbreviation and a preferred company code. Don't change the fields in the other columns !.
The second line is reserved for the client company. Enter the company name, an abbreviation and a preferred company code. Don't change the fields in the other columns !.
Any further line can be used for other companies participating in this project.
By clicking in one of the cells, help texts in yellow will appear. Use these help texts for proper configurating of all parameters for each company.
Note that at the bottom of the table (the blue area) there are more company related properties. Most of these are needed to make a relation with the actual transmittal folders necessary for each of the companies.
Also these fields have an help text attached. Click on any field to see it. To make it even more easy some fields have a set button. Click on it for actually setting the parameter.

Templates for document numbers

when document files are imported in logicDCMS, f.i. when scanning tranmittal folders, validation of the received files takes place.
To be able to do this, logicDCMS must be able to distinguish between valid and not valid filenames.
The document template table is used to do this check. Multiple template formats can be defined here. Seperate sets for client documents, internal documents and vendor documents are supported.
Navigate to Application Manager Menu -> Base Tables -> Templates for document ID's
Add the template formats needed. In case of templates which differ in length but start with the same layout, start with the longest templates.
The templates can contain the special characters #, * and & and any other character.

• The character # represents a location for any of the characters 0 to 9 in the actual filename to check.
• The character * represents a location for any of the characters 0 to 9 or A to Z in the actual filename to check.
• The character & represents a substitution location

Example: template = PR001-***-#### any filename starting with PR-001, followed by a 3-letter code, followed by a - and finished with 4 digits will be consired 'valid' ( f.i.filename = PR001-DWG-0001.pdf )
The column template User indicates from which company a file according this template is to be accepted.

Define issue purposes

logicDCMS makes uses of issue purposes. Issue purpose indicate the reason why a document is distributed from one company to another company.
The following issue purposes are standard:

• IFR : Issue for Review
• IFA : Issue for Approval
• IFI : Issue for Information
• IFD : Issue for Design
• IFC : Issue for Construction
• IAB : Issue as Built
• CAN : Issue for Cancellation

It is possible to define additional issue purposes, but in that case the behaviour of these specials has also to be defined:

• Is a reply expected for this issue purpose ?
• What will be the next issue purpose ? ( can depend on review code and/or revision)
• For which project phase applicable

The behaviour can be controlled by the decision matrix explained later on.
Currently issue purposes can only be configurated by the application support manager, not by any logicDCMS user.
It has to be done before the first documents in the project are being distributed.

Define review codes

logicDCMS makes uses of review codes. Review codes are assigned by the company reviewing a document.
Review codes are also defined by the company reviewing a document. Sometimes the codes 1, 2 or 3 are used, sometimes codes like AC (accepted) , ACC (accepted with comments), NAC (not accepted).
logicDCMS internally makes use of:

• AC : Accepted
• ACC : Accepted with comments, proceed
• NAC : Not accepted, don't proceed
• CAN : Cancellation accepted
• RJ : Rejected

For a project these labels can be changed. Currently review codes can only be changed by the application support manager, not by any logicDCMS user.
It has to be done before the first documents in the project are being distributed.

Lifecycle behaviour due to issue purpsoses and review codes

As described earlier each document passes through a lifecycle.
For logicDCMS this means that each document can go through 3 phases : engineering, construction and as-built.
Not all phases have to be mandatory. Also that can be configured, on document type level or on document level.
logicDCMS is capable of determining the next revision, next issue purpose, next revision date and status
Partly this is implemented 'hard coded', but some project depended configuration is also possible.
In the so called Decision Matrix behaviour can be controlled.