3 D

P L A N T

D E S I G N

A N D

E N G I N E E R I N G

S O F T W A R E

Before conversion in V4 Check that it is possible to convert SDE binaries without any error messages. Check that it is possible to rebuild the whole model without any errors. Check that specification data is valid in the model (CheckShortCodes.mac). It is recommended to convert only projects without any documents (PM drawing or isos). If it is necessary to convert also documents, then all design areas must be archived in V4.

19/11/2013

3 D

P L A N T

D E S I G N

A N D

E N G I N E E R I N G

S O F T W A R E

Converting V4.4 to V5.0.0 - 1st step - copy is created

Original V4.4.x project Target directory for the converted project and library

At the same time library is copied to the same location.

19/11/2013 2

3 D

P L A N T

D E S I G N

A N D

E N G I N E E R I N G

S O F T W A R E

What is the conversion OLD files from library and project are converted to COS objects After the conversion there are two databases: library & project Some files from old project are moved to new library database It is VERY IMPORTANT that during the conversion process administrator tries to create the best possible environment whenever there appears errors, then return back, fix errors in V4 or V5 and continue from the same point remove unnecessary attributes and keys (old notes) merge duplicate attributes and keys merge old attributes to fixed attributes whenever possible convert old names of GD-directories to attributes define attributes according to old GD-directories Run default conversion first for checking of all error messages
19/11/2013 3

3 D

P L A N T

D E S I G N

A N D

E N G I N E E R I N G

S O F T W A R E

Convert Library - Workspace is created if doesnt exist

This is the only correct order. Library must be converted first.

19/11/2013

3 D

P L A N T

D E S I G N

A N D

E N G I N E E R I N G

S O F T W A R E

DM profile Check configuration directory & profile.

Save > Done

Conversion of library begins - Project is connected to server

19/11/2013

3 D

P L A N T

D E S I G N

A N D

E N G I N E E R I N G

S O F T W A R E

COS server ready to import data Check server & port before next step

If PMs attributes used for Groups, enable them as instructed.

19/11/2013 6

3 D

P L A N T

D E S I G N

A N D

E N G I N E E R I N G

S O F T W A R E

Mapping of attributes If same abbreviation is used for 2 attributes with different names, it is possible to map 2nd one to the 1st (existing) attribute. If meaning of both attributes is same it is recommended to map attributes.

Extra confirmation is asked if type of attributes is different. In these cases more consideration is required if mapping makes sense or not.

19/11/2013

3 D

P L A N T

D E S I G N

A N D

E N G I N E E R I N G

S O F T W A R E

Library GD-files are converted

Before each step you have several alternatives how to continue QUIT conversion and continue later from the same point. BROWSE existing COS database. SETTINGS of mapping are modified BEFORE GDs are imported. ERROR LOG is viewed or printed.

BACK to previous step.

IMPORT current data. SKIP current data if already converted or for later conversion.

Old directory path is automatically converted to attribute equip_type

19/11/2013 8

3 D

P L A N T

D E S I G N

A N D

E N G I N E E R I N G

S O F T W A R E

Attributes for directories

Names of sub-directories can be converted to attribute values. This button is naturally active only if activated directory contains sub-directories.

Attributes and their values can be defined directly too. New attributes can be created during the conversion. Next step is to convert keywords (old notes) of GD-files to COS attributes.

19/11/2013

3 D

P L A N T

D E S I G N

A N D

E N G I N E E R I N G

S O F T W A R E

Mapping of keys (GDL-file notes)

Merge duplicate keys and Clear unnecessary keys

ident is mapped to Description

19/11/2013 10

3 D

P L A N T

D E S I G N

A N D

E N G I N E E R I N G

S O F T W A R E

Mapping of attributes
Same as with keys. Try to avoid duplicate and unnecessary attributes.

19/11/2013

11

3 D

P L A N T

D E S I G N

A N D

E N G I N E E R I N G

S O F T W A R E

Conversion of dimension tables

Most important thing is to check all cases where it is possible to convert names of directories to COS attributes by using command Set subdirectory attributes. If e.g. one level of the old directory structure defines the manufacturer of component, this is the easiest way to convert these names of manufacturers to COS attribute values. It is not so important to use command Set Attributes and Values here, because same can be done later by using object browser and amount of work is about same.

Library is now converted.

19/11/2013

12

3 D

P L A N T

D E S I G N

A N D

E N G I N E E R I N G

S O F T W A R E

Convert Project

configuration tables, text-configuration tables, GDL-objects, dimension tables, catalog parts, piping specifications, beam specifications, drawing sheets, ICGDs, icons, formats, 2D symbols, labels, scripts, custom menus, diagram startup scripts, diagram object templates, pd diagram files, integration rules, pipeline objects are converted.

19/11/2013

13

3 D

P L A N T

D E S I G N

A N D

E N G I N E E R I N G

S O F T W A R E

Add COS server to managed servers

Name of schema Address Name of server

19/11/2013

14

3 D

P L A N T

D E S I G N

A N D

E N G I N E E R I N G

S O F T W A R E

Some common error types - library

Cannot read directory <C:/Cadmatic/c50/V5/pms500.lib/src/pm/gdlcmp/strc> - no directory for structurals under the main library. Doesnt cause any problems. Warning: No dimtbl using GDL 'FA10001'. - component is converted correctly. Default parameters are set to 100, which can cause weird previews. No any other problems. Error: Value 100000 is not within the limits (0, 10000) of integer attribute Sorting order. Failed to create COS object(s). Probably attribute not configured, or value out of range, for Dimension Table C:/Cadmatic/c50/V5/pms500.lib/src/dm/dimtbl/Others/PenetrMark1.di

- component is NOT converted. This can cause very serious problems if not fixed.
C:/Cadmatic/c50/V5/pms500.lib/src/dm/dimtbl/PipeSupport/T_ABB_SUP_1.di: Failed to lookup GDL object via name 'T_ABB_SUP'.

- dimension table refers to non-existing GDL. Component is NOT converted. This can cause very serious problems if not fixed.
19/11/2013 15

3 D

P L A N T

D E S I G N

A N D

E N G I N E E R I N G

S O F T W A R E

Some common error types - project

Cannot read directory <c:/Cadmatic/c50/V5/proj500.pms/sde/src/pm/gdlcmp/stdc> - no directory for standard components under the project. Doesnt cause any problems. Warning: SDE name 'PenetrMark1' did not match to any COS object. Can't read dimension table: TempPenetrMarker Can't read dimension table: catalog part TempPenetrMarker - catalog part refers to non-existing dimension table. Component is NOT converted. This can cause very serious problems if not fixed. Duplicate or bad node id numbers fixed - old GD-files with duplicate node id numbers are fixed. Doesnt cause any problems. Syntax error Error in source Illegal definition - component is NOT converted. This can cause very serious problems if not fixed.

19/11/2013

16

3 D

P L A N T

D E S I G N

A N D

E N G I N E E R I N G

S O F T W A R E

Conversion reports stored

Conversion reports are stored under the workspace where conversion was executed.

Tag mapping data is stored under sde/src/sde_to_cos directory. List of managed COS servers is stored to C:\Documents and Settings\CurrentUser\Local Settings\Temp\.ManageCOS\CosServers.txt

19/11/2013

17

3 D

P L A N T

D E S I G N

A N D

E N G I N E E R I N G

S O F T W A R E

GD mapping files under the converted library

19/11/2013

18

3 D

P L A N T

D E S I G N

A N D

E N G I N E E R I N G

S O F T W A R E

Starting the converted project Archive all design areas in V4 before conversion to V5 After Library and Project is converted to V5 Get the area from Archived Areas and start it Answer yes to the following

Check In all objects of each design area. It is important to open every design area, because only owned objects (V4) are checked in.

19/11/2013

19