cadison rel. 6.0

Release Notes

CADISON

Release 6.0.2

Release on

June 4, 2004

© ITandFactory GmbH, D-65812 Bad Soden, Germany

1/27 ReleaseNotes_6_0_2_Englisch.doc ITandFactory GmbH

Table of contents 1 Basic information ................................................................................... 4

1.1 Global changes................................................................................................. 5 1.1.1 Database import and database export have been revised .............................5 1.1.2 The Network License Manager (NLM) Manual has been reworked................5 1.1.3 Backup license for the NLM server................................................................6 1.1.4 User names in CADISON...............................................................................6 1.1.5 Corrections in the supplemental program ITF -Tools .....................................6 1.1.6 Background colors with Windows XP and CADISON.....................................6

2 Installation............................................................................................... 7

2.1 Requirements ................................................................................................... 7 2.2 Updating existing installations .......................................................................... 7 2.3 Installation ........................................................................................................ 7 2.4 Multiple installation of CADISON clients........................................................... 8 2.5 Scope of delivery .............................................................................................. 8

3 PDM.......................................................................................................... 9

3.1 Errors corrected................................................................................................ 9 3.1.1 ObjectManager with document templates ......................................................9 3.1.2 Correct errors in table views...........................................................................9 3.1.3 Revise integration dialog ................................................................................9

3.2 New developments ......................................................................................... 10 3.2.1 Standard in the CADISON user management ..............................................10

4 Engineer ................................................................................................ 12

4.1 Errors corrected.............................................................................................. 12 4.1.1 Editing QUICKLINK data fields in template objects ......................................12 4.1.2 Corrections in the search path from the Analyser.........................................12

4.2 New developments ......................................................................................... 12 4.2.1 Improvement in the "Search and Replace" function .....................................12 4.2.2 LogicAnalayser dialog box expanded...........................................................12 4.2.3 Table build-up optimized ..............................................................................12

5 MATPIPE................................................................................................ 13

5.1 Errors corrected.............................................................................................. 13 5.1.1 Ball is not depicted properly. ........................................................................13 5.1.2 Storage problem corrected...........................................................................13 5.1.3 Not all values were taken over during copying .............................................13 5.1.4 Crash when object tables are added ............................................................13 5.1.5 Incorrect decimal separator ..........................................................................13

5.2 New developments ......................................................................................... 13 5.2.1 New "internal" characteristic for properties...................................................13 5.2.2 New "CATALOG_DATE" property ...............................................................13


5.2.3 "CATALOG_DATE" revision date ................................................................13 5.2.4 Linking of graphic entries via name in CSV import .......................................14 5.2.5 New catalog checker ....................................................................................14

6 2D-PIPE.................................................................................................. 15

6.1 Errors corrected.............................................................................................. 15 6.1.1 CADISON with AutoCAD2000i .....................................................................15 6.1.2 Error message in the Xref dialog .................................................................15

6.2 New developments ......................................................................................... 15 6.2.1 Signal lines ...................................................................................................15

7 3D-PIPE.................................................................................................. 16

7.1 Errors corrected.............................................................................................. 16 7.1.1 Previous routine "display.arx".......................................................................16 7.1.2 Problems with the 3D-PIPE in connection with AutoCAD 2000i ...................16 7.1.3 Container wizard ..........................................................................................16 7.1.4 Error message in the Xref dialog ..................................................................16

7.2 New developments ......................................................................................... 16

8 Modification and Tracing module........................................................ 17

8.1 Authorization for creating change notices....................................................... 17

9 Object model modifications ................................................................ 18

9.1 General........................................................................................................... 18 9.1.1 Reports in the secondary language..............................................................18 9.1.2 "Internal Works Standard" attribute extension ..............................................18 9.1.3 "Temporary Object Model" ...........................................................................18

9.2 Plant Construction object model ..................................................................... 18 9.2.1 German / English environment .....................................................................18

9.3 Electrical Engineering object model................................................................ 18 9.3.1 German / English environment .....................................................................18

10 Tips and tricks ................................................................................... 19

10.1 Sequential numbers of pipelines in the CAD layer.......................................... 19 10.2 Run-time behavior of ITF Tools when the server/client is called up............... 19 10.3 Merge objects in CADISON............................................................................ 19 10.4 Data "from-to" in CADISON............................................................................ 21 10.5 Adjust dialog terms (German/English) ............................................................ 25

11 Closed problem reports (calls) ......................................................... 26

12 Concluding information .................................................................... 27


1 Basic information CADISON Release 6.0.2 is the latest release of the CADISON software. Changes made have been primarily error correction since Release 6.0.1. With CADISON Release 6.0.2, the automated update of older CADISON release statuses is now also possible. The change from Release 5.5 and 5.6 to Release 6.0.2 is made via the integrated update routines. Attention must be paid to the corresponding prerequisites. The backdrop for the required measures is the update to a new Versant database version of CADISON Release 6.0.x. or later.

This work may only be performed by CADISON administrators.

Measures before the update of CADISON Releases 5.5 and 5.6

You must run through the following steps before performing the update to CADISON Release 6.0.2. Data can be lost if these steps are not followed.

Update of CADISON Release 5.5 (SP1-SP8) or 5.6 to CADISON Release 6.0.x

• Read your documents into the database • Back up all your data, databases; export your user management, ... • In doing so, please make sure you follow the remarks on stopping the DBs from the Release

Notes 6.0.0 • Ensure the approved system prerequisites are available • Prepare the registration documents • If you have administrator rights, you can start Setup and follow the instructions of the

installation program

Measures before the update of CADISON Release 5.5 and older:

A direct update to Release 6.0.2 is not planned. Intermediate steps must be carried out. In all cases, all past actions must be carried out to reach at least CADISON Release 5.5. Then, update to CADISON Release 6.0.2 can be continued using the above procedure.

Notes about known problems (examples): X-Refs Document has no file (only from Release 5.4) Action: Reject read-outs .... Export of DBs from Rel. 5.4 Action: For large DBs, set Maxpagebuff higher, if necessary Please contact the responsible sales representative to be able to discuss the additional measures individually.

With CADISON Release 6.0.2, the English version is now available also.

This document can be found on the Internet pages of ITandFactory GmbH under www.ITandFactory.com/customer_care in PDF format.


http://www.triplan.com/customer_care

Notes on virus scanners and firewalls:

To use CADISON, TCP/IP communication via the intended ports is mandatory. Unfortunately, the ports (Standard 5019, ...) used by CADISON are repeatedly blocked due to the current problems (press releases) in this area. As a rule, a virus scanner/firewall can be set so that defined ports are available and security remains ensured. Alternatively, the port used by CADISON can be changed. You can request further information through our CADISON hotline.

1.1 Global changes

1.1.1 Database import and database export have been revised Category: Administration Previously, it was possible during database import for a Versant error to occur internally but not be noticed by CADISON. Normally, the problem showed up in that the imported database appeared empty, that is, did not contain a project. This problem could occur if the cache storage was defined too small for the newly created Versant database. If the storage is too small, the database service crashes, but this was not identified in CADISON. From CADISON 6.0.2 onward, a check is made during database import whether the process was ended without an internal error message. If not, a corresponding error message is displayed, which contains the remark that the setting for VERSANT_MAX_PAGE_BUFFS should be increased. This requires that the variable VERSANT_MAX_PAGE_BUFFS under the section [PHi-CADISON] in CDSN60.INI be defined as follows:

[PHi-CADISON] VERSANT_MAX_PAGE_BUFFS=8192

If VERSANT_MAX_PAGE_BUFFS is not available, CADISON uses a default value of 4096. Therefore, first the value 8192 should be entered here. If with this setting the database import continues to be interrupted, the value should be doubled to 16384. After this value has been changed, the incorrectly imported database should be deleted and the import process repeated. It could also occur that CADISON hangs up after a successful database import. CADISON then displayed the Wait dialog, but nothing else happened for several minutes (processor utilization in the Task Manager at under 2%). With Release 6.0.2, CADISON should no longer get stuck at this point. Both changes have also been taken over in the database export. There a check is also made whether the database export was ended successfully and a message output in case of an error. Whether the database process was terminated is checked more reliably here as well.

1.1.2 The Network License Manager (NLM) Manual has been reworked Category: Administration The documentation for use and administration has been updated to the status valid today. The document is contained on the CADISON installation CD as a PDF file.


1.1.3 Backup license for the NLM server Category: Administration We described the functioning types of the NLM server in Release Notes 6.0.1. Installation and administration were described under point 1.1.2. For customers who use an NLM server, the subject of new installation (e.g. change of the physical server, change of the server name, ...) of the NLM server comes up occasionally. A result of this is the need to request a new license code from the ITF. We also offer you the possibility of using an NLM backup server with a license that is available immediately. This lets you avoid "down-time" when you start up a backup server. You can request further information from your responsible sales representative or via our CADISON hotline.

1.1.4 User names in CADISON Category: Administration

The user names in CADISON must not contain blanks or special characters. Please observe this when creating new user names (see also Chapter 3.2.1.).

1.1.5 Corrections in the supplemental program ITF -Tools Category: Administration Some corrections were made in this supplemental program. The help text will now be shown with a larger font size. When the configured command was saved, a crash occurred if no file was selected. When the configured command is saved, the ending is changed to *.bat if it is different.

1.1.6 Background colors with Windows XP and CADISON Under Windows XP, the background was mostly white in the dialog boxes and window and did not have the background color set in the operating system. With CADISON Release 6.0.2., the right background color is now used under Windows XP.


2 Installation 2.1 Requirements This version of the CADISON software has been tested and approved for release under the following conditions:

Operating systems: Windows 2000 Prof. (SP1 – SP4) Windows 2000 Server (SP1 – SP4) Windows XP Prof. (SP1)

Windows 2003 Server for • Network License Manager (NLM service) • Versant service (database server) • Work directory (file server)

Partitions: CADISON is intended for use with an NTFS partition. Installation and use of

CADISON under a FAT partition can lead to undesired side effects. AutoCAD: ACAD 2000i ACAD 2002 ACAD 2004 CADISON: Rel. 6.0.2 Versant DB: 6.0.5.3. License query: Using "softkey" for workstation or license manager on Windows 2000, XP or

Windows 2003 server MS Office: MS Office 2000 / XP Notes: CADISON Version 6.0.2 can be operated with AutoCAD versions 2000i, 2002 and 2004. We recommend the use of CADISON 6.0.2, but only in a homogeneous environment. We recommend you do not mix use of AutoCAD 2000i, 2002 and 2004. The hotfixes issued by Microsoft for its various operating systems can sometimes cause problems for the use of CADISON. Please contact our hotline before installing a hotfix.

2.2 Updating existing installations Please make sure you follow the remarks in Chapter 1.

2.3 Installation Start the setup routine from the CD and follow the instructions provided by the setup program.

The setup routine for CADISON release 6.0.2. is the same as for release 6.0.1.


2.4 Multiple installation of CADISON clients Category: Administration

With the new setup routine from CADISON, it is also possible to log the installation and then have it run on one or more computers. The time spent on the installations can be reduced considerably with this method.

The automated installation with InstallShield runs according to the following pattern:

In the first installation, the setup routine is started with the option '-r' or '/r' (that is "setup.exe -r"). In the Windows directory is generated a "response file" named "setup.iss", in which the values are recorded that the user selects and/or enters in this interactive installation. If an installation with these settings should now run without user interaction, the setup routine is called up with the option '-s' or '/s'. In addition, the response file (-f1) to be used and the log file (-f2) to be written during installation can be specified with the options '-f1' and '-f2'. Example: setup.exe -r --> generates the file "C:\WINNT\setup.iss"

This file can now be copied into the CADISON installation directory on the server, for example, and/or renamed. On the clients, the "automatic installation" can then be performed via

setup.exe -s -f1 L:\CADISON.INSTALL\cadison.iss -f2 L:\CADISON.INSTALL\client1.log

. In module installations, confirmation may only need to be made with <RETURN>.

2.5 Scope of delivery With the delivery of CADISON Release 6.0.2, you will receive:

• A CADISON Rel. 6.0.2 program CD. • CADISON 6.0.2 release notes • CADISON call (fault) report sheets 6.0


3 PDM 3.1 Errors Corrected

3.1.1 Object Manager with document models In the Object Manager, it was previously possible to assign an external document to an object stored in the default database by using the Edit dialog with the function "Document management->Create new document..." from the context menu. But since a document in CADISON always requires a higher-level project, and no higher-level project is present in the default database, unforeseeable results came out. This function in the context menu is not available any more.

3.1.2 Errors in table views corrected Two problems can occur in the CADISON table views. One problem was that, after a new table was built up, CADISON was sometimes in a multiple selection mode, which is normally triggered only after the Caps Lock key is pressed. As a result, when a line was clicked on, CADISON marked everything from the already marked line up to the newly clicked-on line. A second error then usually occurred. If the user clicked on the table again, a very wide table was built up with numerous columns, all of which were empty. This process could last up to several minutes. Both errors were corrected in CADISON Release 6.0.2.

3.1.3 Integration dialog revised The dialog box of the "Working copy->Integrate working copy" function can now be changed in size and permanently stores the last dialog position and size.


3.2 New developments

3.2.1 Standard in the CADISON user management Category: Administration

The CADISON User Management was completely revised in Release 6.0.2. Now, a prepared CADISON User Management is available immediately after installation is completed. The user names and roles are listed subsequently. User management takes place over the PDM and should be activated for every CADISON application.

Roles and status of independent users:

• Administrator (ITF administrator) • Admin (CADISON standard administrator) • User (users cannot create) • Project manager (users can create)

Roles and status of dependent users:

These are also assigned to an appropriate user group and receive their rights from the user group and role.

There are only two statuses, "editing" and "reading". These are contained in each role, but have different standard rights and possibly class rights depending on the role. The ending "RS" in the users' names is meant to make clear the dependence on Role and Status. • GuestRS (may only read, not delete anything, e.g. in the "reading" status with additional restrictions

in the case of straight fittings, tab 401 Manufacturer shall be suppressed) • UserRS (may create, change, delete, in the "editing" status he may create an order (an example), in

the "reading" status only read)) • Project ManagerRS (in addition to the UserRS, may create users and always change everything

independently of the status. This makes role and status obsolete, but it is stated for demonstration to the other users, and one can add restrictions quickly.

Predefined passwords for the users are as follows:

User name Code word

Administrator ******

Admin Admin

User User

Project Leader Projektleiter

GuestRS GastRS

UserRS UserRS

ProjectManagerRS ProjektleiterRS

These predefined passwords should be changed by the "Admin" user immediately after the installation.


Screen shot of User Management with our default settings:

Changes from CADISON Release 6.0.2. onward for existing users

Beginning with CADISON Release 6.0.2, the above default is still read in before login if there is no system database. As a result, the above users are immediately available in the case of a new installation.

As a result of this requirement, the following processes have been changed for software-related reasons:

• Initialization of the databases before login. In the client-server environment, this means that initialization of databases, as previously, can be made either by the server or by one client! Meanwhile, no CADISON applications may be started on other clients in the same server domain!

• The administrator login is available only for ITandFactory GmbH employees and the customer's management. The previous standard password "cadison" has been removed.

• The "Admin" login is available for customers' administrators. All new users have a predefined password (see above table), which must be changed by customers' administrators. After each new installation, the "Administrator" login no longer appears, but the "Admin" instead.

• Templates exist for German and English. They can be found under ..\CADISON\Config\german or ..\CADISON\Config\english and are called "Cadison_User_Management.txt". You can therefore also import these manually in the PDM. As before, this deletes an exiting user management.


4 Engineer 4.1 Errors corrected

4.1.1 Editing QUICKLINK data fields in default objects Editing of QUICKLINK data fields of default objects stored in the default database has been changed, since access to other objects of the higher-level project object is possible via QUICKLINK fields. Of course, there is no project object in the default database, so processing of such a data field in the default database has previously resulted in destruction of the default object. Therefore, beginning with this release, it is no longer possible to edit these QUICKLINK fields in default objects. This change also affects the 2D/3D PIPE areas.

4.1.2 Corrections in the search path from the Analyser Category: Administration The analyzer tools "Analyser" and "Analyser LT" from the program group CADISON->Administration searched in the incorrect Versant program directory for the Versant file "SYSINFO". Now the search for this file is made in the right directory ..\CADISON\System\Versant\vds605, so the analyzer tools can show this file properly. The error has been corrected..

4.2 New developments

4.2.1 Improvement in the "Search and Replace" function The "Search/Replace dialog" for tables has been expanded. This holds both for "searching " and for "replacing". In the Search dialog, pressing on the "Search" button in the table selects the next matching element, but the dialog box is not closed, so the search can continue. In the Replace dialog box, there is no longer just the "Replace" button, but "Next" and "Replace All" buttons as well. "Replace All" replaces all matching elements in the table and ends the dialog. The other buttons leave the dialog open.

4.2.2 Logic Analyser dialog box expanded Category: Administration A definition file for the Logic Analyser can be used to define additional properties that can also be shown in the Logic Analyser. Previously, the user had to add these properties manually to the table configuration. Beginning with this release, the specified properties are automatically displayed in the results table. In addition, the results dialog can be changed in size so that the additional columns can be made more visible.

4.2.3 Table build-up optimized Previously, some of the tables in the main window of the Engineer and also the tables in the Object Manager were built up several times in succession, so the table often flickered briefly. The table is now built up just once, so the flickering is avoided and the build up is faster.


5 MATPIPE 5.1 Errors corrected 5.1.1 Ball is not depicted properly A graphic was not correctly generated in MATPIPE of CADISON 6.0.x. All variants containing the primitive ball could no longer be generated. The problem has now been solved. 5.1.2 Storage problem corrected During longer, intensive work with MATPIPE (with switched-on viewer) and the parametric variant modeler, increasing storage consumption could result in a system crash. This problem has now been solved. 5.1.3 Not all values were taken over during copying Not all values were taken over during copying. Now all values are taken over. 5.1.4 Crash when object tables are added MATPIPE crashed when object tables were added to a catalog. This error has now been fixed. 5.1.5 Wrong decimal separator When object tables are exported, an incorrect decimal separator is output for floating decimal values. This error has now been corrected.

5.2 New developments 5.2.1 New "internal" characteristic for properties Category: Administration Many properties are only needed for administration of components in the catalog (supplemental fields such as SORTPOS). These are often useless for CAE systems and should not be passed on. The new "internal" characteristic is deactivated by default and can be activated via the Properties dialog. Internal properties are not transferred via the selector interface. Care should be taken that only those properties whose presence is not essential for the CAE system are set to "internal" (e.g. DN). 5.2.2 New property "CATALOG_DATE" Category: Administration To the objects of the standard catalogs has been added the "CATALOG_DATE" property. By default, the property has been set to write protected to activate automatic revision. 5.2.3 Revision date "CATALOG_DATE" Category: Administration


If the "CATALOG_DATE" property("Catalog entry created on") is present and set to write-protected, its value is set automatically to the date of the last change when the object is changed. This automatic action can be switched off if the write protection is removed from the property (such as for manual setting of the last change). With this it is now possible to directly recognize changes in the catalogs. 5.2.4 Linking of graphic entries via name in CSV import Category: Administration CSV import previously offered the opportunity when importing to link existing graphic entries with the imported components using the object type (object class). To this function was added the possibility to specify in the CSV file a column named "GRAPHIC_NAME" containing the name of the existing graphic entry and the one to be linked. This feature solves the problem during the import of objects of the same type, such as flange (PHI-PVLS) with different graphic representation (welding-neck flange, reducing flange, blind flange, etc.). 5.2.5 New catalog checker Category: Administration A catalog checker is available for the first time with CADISON Release 6.0.2. The description and functioning is documented in the separate document "Catalog Checker". Note: The document for the "Catalog Checker" is available to our CADISON service-contract customers in the download area on our Internet site www.ITandFactory.com.


http://www.itandfactory.com/

6 2D-PIPE 6.1 Errors corrected

6.1.1 CADISON with AutoCAD2000i CADISON Rel. 6.0.1. 2D-PIPE did not work with AutoCAD 2000i. This resulted in crashes when a drawing was saved. In addition, no elements from MATPIPE were displayed in 3D-PIPE. Both problems have been corrected with Release 6.0.2.

6.1.2 Error message in the Xref dialog An error message could occur when the XRef dialog is called up (components not found). This message no longer appears.

6.2 New Developments

6.2.1 Signal lines Signal lines can now be generated with CADISON in any desired presentations and colors. "CADISON.LIN" was adapted and expanded for this purpose. The user himself can change the signal lines. In the object classes

o Signal line o Working line

the colors and line types can be changed or preset via tab 804 Graphics.


7 3D-PIPE 7.1 Errors corrected

7.1.1 Previous routine "display.arx" In CADISON Release 5.5, there was the routine "display.arx". This aided stability with regard to the AutoCAD 3D display driver on many computers. Since CADISON 6.0.0, this routine is no longer necessary.

7.1.2 Problems with 3D-PIPE in connection with AutoCAD 2000i CADISON 3D-PIPE did not run properly under AutoCAD 2000i. The MATPIPE elements were not depicted under AutoCAD 2000i and another AutoCAD error message was output when CADISON was ended. These two problems have now been resolved.

7.1.3 Container wizard If the "Foot" dialog was used in the Container wizard, AutoCAD could not be terminated properly. After the AutoCAD window was closed, another "Unhandled Exception" error message appeared. This message no longer appears. In addition, the end of the dialog always had the remark that no fastening and no wall thickness are undefined, even when these values were defined. This message no longer appears.

7.1.4 Error message in the Xref dialog An error message could occur when the XRef dialog is called up (components not found). This message no longer appears.

7.2 New Developments No new developments were made in this module.


8 Modification and Tracing module 8.1 Authorization for creating change notices The authorizations for preparation of change notices have been internally fixed. If a user may only create certain object classes in a project through a User Management with switched-on Modification and Tracing, the result is an error message that the change notice may not be created.

If a standard authorization is defined, a class authorization for the class VCS-MODI (change notice) is automatically added internally. This additional (not visible) class authorization takes over all settings of the standard authorization up to the "Create object" right. This right is set internally to "Create". As a result, the system can always add change notices. This cannot be changed, even if one additionally defines a class authorization extra for change notices via the User Management.


9 Object model modifications 9.1 General

9.1.1 Reports in the secondary language

Until now, the actual report object was not supported when a report was generated in the set secondary language. Starting with this version, the report object is also translated. The new property "PNAME_INT" was introduced for this purpose in the object model for report, document and document-revision objects. As a result, the report name can be translated through specification of "$REPORT.P_name$" in the report's .RTF file if the translation text is filed accordingly in a dictionary file.

9.1.2 "Internal Works Standard" attribute extension

With this new attribute, the internal standard or component specification, e.g. "Internal Works Standard", can be described.

9.1.3 "Temporary object model" Some users work with the possibility of changing online the values set in the object model. This can happen, in particular, if work is done in CADISON without real User Management. We would like to point out the sometimes serious problems that such short-term ("temporary") changes in settings have caused.

9.2 Plant Construction object model

9.2.1 German / English environment

No changes have been made.

9.3 Electrical Engineering object model

9.3.1 German / English environment

No changes have been made.


10 Tips and tricks 10.1 Sequential numbers of pipelines in the CAD layer This is an example and may only be used by experienced CADISON administrators!

How can sequential numbers of the pipelines be depicted in the layer structure?

No program change is necessary for this since the layer name in CAD is defined via the object model so that object model modifications are needed here. The layer name of the pipeline is defined in the tab "804 Graphic". There you find the definition:

Property "Layer name" (internal name "LAYER"): Type: "CALCULATE" Formula: "LAYERPREFIX+P_loid2"

This means that the object ID of the pipeline is currently attached after the layer prefix. Thus you receive a layer designation with the following build-up:

P---PLINB-1101154074

You can change the formula so that, instead of the database object ID, the pipeline number is used.

Formula: "LAYERPREFIX+PIPE_NO"

The property PIPE_NO (= "line number") is from the tab "101-DIN" and consists of the code letter of the pipeline and the sequential number. The formula would then deliver into the following layer designation:

P---PLINB-FA111

In principle, you can perform these changes yourself in the object model, provided that the necessary know-how is available.

We would also be happy to offer you our service to meet the described requirements. Give us a call.

10.2 Run-time behavior of ITF Tools when the server/client is called up Category: Administration

The run-time behavior of the ITF tools with various options (e.g.: -CLEAN) is influenced considerably by the location (server or client) of call up. The optimal run-time behavior is achieved when the ITF tools are started on the database server. If the ITF tools are called up from the client, the transfer times for network communication are added and thus delay the execution of the individual commands.

10.3 Merge objects in CADISON The function of "Merge objects" was reworked with delivery of CADISON Release 5.6. In the following, the application of this function is described, depending on the release status. Procedure with use of current version < CADISON R5.6

Here it is very important to read the entries in the AutoCAD command line.

After "Merge objects" was selected, the order appeared in the command line:

Select objects that are to be merged graphic/list “Graphic”. This means that the graphic selection is preset. With "Enter", a pickbox opens that allows element selection. If all desired objects are marked and their selection confirmed with "Enter"/a click of the right


mouse button, the order appears List selection / “select target object”: It offers the possibility to immediately select the TARGET object. If the TARGET is clicked on or after "LI .... ENTER" has been typed in the selected list, the question is asked whether:

If this inquiry is confirmed, the objects will be merged. The data record, of course, comes from the TARGET object. The order of the selection is thus important.

Procedure with use of current version >= CADISON R5.6

Here, the procedure is identical up to the point that "Merge CADISON objects" is requested. But after its selection, a list showing the objects to be merged (source and target object(s)) is opened.

The object selected here supplies the data record that is carried in the database in place of all graphic depictions.


10.4 Data "from-to" in CADISON Functional description of "data from" / "data to"

If a pump is drawn in an R&I diagram, for example, templates can also be selected that contain subordinate objects (in the case of a pump, that would be its drive, for example):

These subordinate components are referred to before placement on the drawing:


If "Yes" is selected, subordinate objects can also be drawn in the following. The result of the drawing could look as follows:

The related database entry appears as follows:

If during further project processing the transition is completed from the diagram drawing to the installation plan, a catalog entry is normally assigned to the diagram object (and to the related data record) to make manufacturing data and a 3D graphic variant available.


The catalog entry can be assigned in the CADISON tree, for example:

The selector is opened and permits selection of the desired entry:


Since the catalog pump now already contains its drive and the connection between the drive and pump, the system requests whether existing "subordinate components" (whereby the data records for drive and drive shaft are meant) should be deleted:

If "Yes" is chosen here, a list appears with the components to be deleted

with which, in this case, the drive shaft as subordinate object of the drive would also be deleted.

If, in contrast, "No" is selected (standard case), the structures remain intact.

All data provided in the catalog are brought in. Data is not passed on to subordinate components unless data transfer has been defined for these objects (calculated fields = adaptation of the standard).

And so the result is:

1. A main object data record corresponding to the entries of the catalog 2. The connection of the graphics variant for drawing/drawing alignment in 3D 3. Maintenance of the object structure 4. Maintenance of the data records for subordinate objects

If a pump equipped with a catalog entry is now used as reference for the "data to" function, and if the target object is of the same type (that is, also a pump), its subordinate objects are found:


Ignoring provides a solution in accordance with the reference

Copying provides a data record in accordance with the reference but causes a deletion of the graphic components of the subordinate objects (since these are ignored in the catalog entry).

Cancel terminates the function without transferring data.

The same applies correspondingly for "data from".

10.5 Adjust dialog terms (German/English) Depending on the selected language, the dialogs in CADISON are built up dynamically according to the directory structure and names.

The English user environment is set in the following example. The term "German" is visible in the right folding menu. This is read out of the directory structure on the hard disk and integrated directly in the folding menu.

A program change is not needed to change this term. Instead, you can rename the corresponding directory and thus achieve the desired "German" dialog process.


11 Closed problem reports (calls) 10255

10278

10385

10389

10512

10858

10875

10890

10893

10935

10940


12 Concluding information CADISON Version 6.0.3 will be issued as a follow-up version of CADISON Release 6.0.2. The release date is planned to be June 30, 2004. We have included our modified CALL report forms with this CADISON Release 6.0.x. Please use these effective immediately. The CADISON Helpdesk is available for you at the usual times (Mon – Thu 8:30 a.m. – 5:00 p.m. and Fri 8:30 a.m. – 3:00 p.m. Telephone: +49 / 6196 / 6092 - 500 Fax: +49 / 6196 / 6092 - 202 E-mail: [email protected]

You can also contact our employees directly for specific questions:

CADISON training: Frau Asquino Telephone: +49 / 6196 / 6092 - 511 Fax: +49 / 6196 / 6092 - 206 E-mail: [email protected] CADISON sales: Sales office Telephone: +49 / 6196 / 6092 - 118 Fax: +49 / 6196 / 6092 - 206 E-mail: [email protected] Additional information can be found on our Internet homepage:

www.ITandFactory.com and [email protected]

We wish you every success in your work with the new CADISON 6.0.2. The CADISON team


mailto:[email protected]



http://www.triplan.com/


cadison rel. 6.0

Documents