Use the functionality to route a pipe along the curve of a hull plate at a certain distance and offset.

Surfaces
Surface Selection
Use to select the surface(s) upon which a routing curve is to be created. Prompt is displayed ‘Identify element’ selected panels are highlighted in red. Press Esc once the hull panels are selected/deselected. Also use to deselect panel(s).
Note:
Only UPANEL or IPLATE are currently supported.
Route
Route Current Element
Use to align the currently selected element (CE) with the hull.
Note:
If the CE is not a bend or elbow this functionality is not available.
Route Next Component
Use to position the next component created or copied at the curve of the hull.
Note:
Switching between route modes updates the graphical aids and coordinates axis in the 3D graphical view.
Note:
It is not possible always to position or copy the CE against the hull curve, however it is possible to draw the hull curve graphical aids.
Routing Direction
Route With Flow
Use to route the pipe in the head to tail direction.
Route Against Flow
Use to route the pipe in the tail to head direction.
Create/Modify Component
Angle
If the CE is an elbow or bend, use to modify the angle of the elbow or bend (a maximum and minimum angle can be specified).
Direction towards pick
If the CE is an elbow or a bend, use to modify the angle of the CE so that the leave or arrive is pointing towards a picked element in the 3D graphical view.
Position at Curve
If the CE is an elbow or a bend use to position the P0 of the CE on the defined curve. A red translucent tube draw aid is displayed.
Note:
It is not possible to use the position functionality when the current element is not an elbow or a bend. But the curve will display if the current element is another piping component or branch.
Copy, Orientate and Position Current Component
This functionality is only available when using the route next component functionality.
If the CE is a bend or elbow, the CE can be copied and then orientated and positioned accordingly. A red translucent tube draw aid is displayed.
If it is not possible the CE at the curve, then the CE is copied and can be orientated but not positioned.
Note:
It is not possible to use the copy functionality when the current element is not an elbow or a bend. But the curve will display if the current element is another piping component or branch.
Graphical Aids
Intersection
Coordinates
The directions available for selection are based on a coordinate system:
Local - Based on the leave/arrive direction of the CE (elbow or bend)
Orthogonal - Based on the leave/arrive direction of the CE (elbow or bend), these are projected in the horizontal plane
World - World coordinate system: X,Y,Z and -X, -Y, -Z.
Direction
The intersection direction is the direction of the hull plate in comparison to the CE and routing direction. The options available for selection are based on the coordinate system selected.
The available directions are demonstrated by the graphical aid axes in the 3D graphical view.
For example:
In the screen shot, the routing direction is the leave of the elbow is Y. So the routing line goes from the leave of the elbow in the Y direction. In relation to the routing line, the direction of the hull is either Y or -Z.
So in the example an intersection direction of -Z has been chosen. The blue lines show how this direction is used to calculate the graphical curve.
Each spine is calculated by going along the routing direction (Leave direction (Y)) and at each gap interval (in this case 100mm), using the intersection direction to create a curve spine of a given length (In this case a distance of 250mm)
A curve is then produced by joining up the ends of each of the spine lines.
Show
Use to toggle the graphical aids and hull curve in the 3D graphical view on or off.
Show Helper Aids
Use to display the blue graphical aid lines which can help to understand how the curve is being constructed.
Projection Plane
The red plane graphical aid is displayed in the 3D graphical view (vertically or horizontally) is only available when the Normal Line Type functionality is selected. Refer to Line Type for further information.
Used to project the normal direction from the hull into the pipe or routing plane so that the component or next component can be routed against the curve.
Clear Aids/Surface Elements
Use to clear the 3D graphical view of all graphical aids, for example - hull curve and selected surfaces).
Line Type
Normal
Use to set the orientation of the spines coming from the hull to Normal.
Draws the spines in the normal direction coming from the hull face. The normal direction is projected into the projection plane so that they are in line with the routing direction thus allowing the current or next component to be routed against the hull.
Note:
In the normal mode, the spines are yellow with a green curve.
Orthogonal
Draws the spines in the opposite direction to the intersection direction. Only the local coordinate system is available.
Note:
In the orthogonal mode, the spines are red with a yellow curve.
Line Offsets
Distance
Use to set the length of the spines coming from the hull plate (which sets the position of the curve).
Gap
Use to set the spacing between the blue graphical aid lines (These are positioned along the arrive/leave direction of the CE and are projected in the intersection direction until the shell plate is hit).
Component Sequence List
Use to scroll through and select individual components within the currently selected branch, refer to Component Sequence List for further information.
Surfaces

Surface Selection
Use to select the surface(s) upon which a routing curve is to be created. Prompt is displayed ‘Identify element’ selected panels are highlighted in red. Press Esc once the hull panels are selected/deselected. Also use to deselect panel(s).
Route

Route Current Element
Use to align the currently selected element (CE) with the hull.

Route Next Component
Use to position the next component created or copied at the curve of the hull.
Routing Direction

Route With Flow
Use to route the pipe in the head to tail direction.

Route Against Flow
Use to route the pipe in the tail to head direction.
Create/Modify Component

Angle
If the CE is an elbow or bend, use to modify the angle of the elbow or bend (a maximum and minimum angle can be specified).

Direction towards pick
If the CE is an elbow or a bend, use to modify the angle of the CE so that the leave or arrive is pointing towards a picked element in the 3D graphical view.

Position at Curve
If the CE is an elbow or a bend use to position the P0 of the CE on the defined curve. A red translucent tube draw aid is displayed.

Copy, Orientate and Position Current Component
This functionality is only available when using the route next component functionality.
If the CE is a bend or elbow, the CE can be copied and then orientated and positioned accordingly. A red translucent tube draw aid is displayed.
If it is not possible the CE at the curve, then the CE is copied and can be orientated but not positioned.
Graphical Aids

Intersection

Coordinates
The directions available for selection are based on a coordinate system:

Direction
The intersection direction is the direction of the hull plate in comparison to the CE and routing direction. The options available for selection are based on the coordinate system selected.
The available directions are demonstrated by the graphical aid axes in the 3D graphical view.
For example:

In the screen shot, the routing direction is the leave of the elbow is Y. So the routing line goes from the leave of the elbow in the Y direction. In relation to the routing line, the direction of the hull is either Y or -Z.
So in the example an intersection direction of -Z has been chosen. The blue lines show how this direction is used to calculate the graphical curve.
Each spine is calculated by going along the routing direction (Leave direction (Y)) and at each gap interval (in this case 100mm), using the intersection direction to create a curve spine of a given length (In this case a distance of 250mm)
A curve is then produced by joining up the ends of each of the spine lines.

Show
Use to toggle the graphical aids and hull curve in the 3D graphical view on or off.

Show Helper Aids
Use to display the blue graphical aid lines which can help to understand how the curve is being constructed.
Projection Plane

The red plane graphical aid is displayed in the 3D graphical view (vertically or horizontally) is only available when the Normal Line Type functionality is selected. Refer to Line Type for further information.
Used to project the normal direction from the hull into the pipe or routing plane so that the component or next component can be routed against the curve.

Clear Aids/Surface Elements
Use to clear the 3D graphical view of all graphical aids, for example - hull curve and selected surfaces).
Line Type

Normal
Use to set the orientation of the spines coming from the hull to Normal.
Draws the spines in the normal direction coming from the hull face. The normal direction is projected into the projection plane so that they are in line with the routing direction thus allowing the current or next component to be routed against the hull.

Orthogonal
Draws the spines in the opposite direction to the intersection direction. Only the local coordinate system is available.
Line Offsets

Distance
Use to set the length of the spines coming from the hull plate (which sets the position of the curve).

Gap
Use to set the spacing between the blue graphical aid lines (These are positioned along the arrive/leave direction of the CE and are projected in the intersection direction until the shell plate is hit).
Component Sequence List
Use to scroll through and select individual components within the currently selected branch, refer to Component Sequence List for further information.

Surfaces
Surface Selection
Use to select the surface(s) upon which a routing curve is to be created. Prompt is displayed ‘Identify element’ selected panels are highlighted in red. Press Esc once the hull panels are selected/deselected. Also use to deselect panel(s).
Note:
Only UPANEL or IPLATE are currently supported.
Route
Route Current Element
Use to align the currently selected element (CE) with the hull.
Note:
If the CE is not a bend or elbow this functionality is not available.
Route Next Component
Use to position the next component created or copied at the curve of the hull.
Note:
Switching between route modes updates the graphical aids and coordinates axis in the 3D graphical view.
Note:
It is not possible always to position or copy the CE against the hull curve, however it is possible to draw the hull curve graphical aids.
Routing Direction
Route With Flow
Use to route the pipe in the head to tail direction.
Route Against Flow
Use to route the pipe in the tail to head direction.
Create/Modify Component
Angle
If the CE is an elbow or bend, use to modify the angle of the elbow or bend (a maximum and minimum angle can be specified).
Direction towards pick
If the CE is an elbow or a bend, use to modify the angle of the CE so that the leave or arrive is pointing towards a picked element in the 3D graphical view.
Position at Curve
If the CE is an elbow or a bend use to position the P0 of the CE on the defined curve. A red translucent tube draw aid is displayed.
Note:
It is not possible to use the position functionality when the current element is not an elbow or a bend. But the curve will display if the current element is another piping component or branch.
Copy, Orientate and Position Current Component
This functionality is only available when using the route next component functionality.
If the CE is a bend or elbow, the CE can be copied and then orientated and positioned accordingly. A red translucent tube draw aid is displayed.
If it is not possible the CE at the curve, then the CE is copied and can be orientated but not positioned.
Note:
It is not possible to use the copy functionality when the current element is not an elbow or a bend. But the curve will display if the current element is another piping component or branch.
Graphical Aids
Intersection
Coordinates
The directions available for selection are based on a coordinate system:
Local - Based on the leave/arrive direction of the CE (elbow or bend)
Orthogonal - Based on the leave/arrive direction of the CE (elbow or bend), these are projected in the horizontal plane
World - World coordinate system: X,Y,Z and -X, -Y, -Z.
Direction
The intersection direction is the direction of the hull plate in comparison to the CE and routing direction. The options available for selection are based on the coordinate system selected.
The available directions are demonstrated by the graphical aid axes in the 3D graphical view.
For example:
In the screen shot, the routing direction is the leave of the elbow is Y. So the routing line goes from the leave of the elbow in the Y direction. In relation to the routing line, the direction of the hull is either Y or -Z.
So in the example an intersection direction of -Z has been chosen. The blue lines show how this direction is used to calculate the graphical curve.
Each spine is calculated by going along the routing direction (Leave direction (Y)) and at each gap interval (in this case 100mm), using the intersection direction to create a curve spine of a given length (In this case a distance of 250mm)
A curve is then produced by joining up the ends of each of the spine lines.
Show
Use to toggle the graphical aids and hull curve in the 3D graphical view on or off.
Show Helper Aids
Use to display the blue graphical aid lines which can help to understand how the curve is being constructed.
Projection Plane
The red plane graphical aid is displayed in the 3D graphical view (vertically or horizontally) is only available when the Normal Line Type functionality is selected. Refer to Line Type for further information.
Used to project the normal direction from the hull into the pipe or routing plane so that the component or next component can be routed against the curve.
Clear Aids/Surface Elements
Use to clear the 3D graphical view of all graphical aids, for example - hull curve and selected surfaces).
Line Type
Normal
Use to set the orientation of the spines coming from the hull to Normal.
Draws the spines in the normal direction coming from the hull face. The normal direction is projected into the projection plane so that they are in line with the routing direction thus allowing the current or next component to be routed against the hull.
Note:
In the normal mode, the spines are yellow with a green curve.
Orthogonal
Draws the spines in the opposite direction to the intersection direction. Only the local coordinate system is available.
Note:
In the orthogonal mode, the spines are red with a yellow curve.
Line Offsets
Distance
Use to set the length of the spines coming from the hull plate (which sets the position of the curve).
Gap
Use to set the spacing between the blue graphical aid lines (These are positioned along the arrive/leave direction of the CE and are projected in the intersection direction until the shell plate is hit).
Component Sequence List
Use to scroll through and select individual components within the currently selected branch, refer to Component Sequence List for further information.
Local - Based on the leave/arrive direction of the CE (elbow or bend)
Orthogonal - Based on the leave/arrive direction of the CE (elbow or bend), these are projected in the horizontal plane
World - World coordinate system: X,Y,Z and -X, -Y, -Z.
Local - Based on the leave/arrive direction of the CE (elbow or bend)
Local - Based on the leave/arrive direction of the CE (elbow or bend)
Orthogonal - Based on the leave/arrive direction of the CE (elbow or bend), these are projected in the horizontal plane
Orthogonal - Based on the leave/arrive direction of the CE (elbow or bend), these are projected in the horizontal plane
World - World coordinate system: X,Y,Z and -X, -Y, -Z.
World - World coordinate system: X,Y,Z and -X, -Y, -Z.
Note:
Currently this functionality only supports the new style IPLATEs.
Note:
Only UPANEL or IPLATE are currently supported.
Note:
If the CE is not a bend or elbow this functionality is not available.
Note:
Switching between route modes updates the graphical aids and coordinates axis in the 3D graphical view.
Note:
It is not possible always to position or copy the CE against the hull curve, however it is possible to draw the hull curve graphical aids.
Note:
It is not possible to use the position functionality when the current element is not an elbow or a bend. But the curve will display if the current element is another piping component or branch.
Note:
It is not possible to use the copy functionality when the current element is not an elbow or a bend. But the curve will display if the current element is another piping component or branch.
Note:
In the normal mode, the spines are yellow with a green curve.
Note:
In the orthogonal mode, the spines are red with a yellow curve.

Note
:
Surfaces
Surface Selection
Identify element’
Esc
Note
:
Route
Route Current Element
Note
:
Route Next Component
Note
:
Note
:
Routing Direction
Route With Flow
Route Against Flow
Create/Modify Component
Angle
Direction towards pick
Position at Curve
Note
:
Copy, Orientate and Position Current Component
Note
:
Graphical Aids
Intersection
Coordinates
Local
Orthogonal
World
Direction
Show
Show Helper Aids
Projection Plane
Normal Line Type
Line Type
Clear Aids/Surface Elements
Line Type
Normal
Normal
Note
:
Orthogonal
Note
:
Line Offsets
Distance
Gap
Component Sequence List
Component Sequence List


All of the tasks carried out that are associated with the creation and modification are initiated from the Hull Routing tab of the Piping Component Editor window. Depending on the selections made, further functionality becomes available.

Hull Routing
Piping Component Editor


AVEVA Bocad Steel Interface allows you to export and import files using the AVEVA Bocad Steel Interface (ABS) format. This is a proprietary encrypted and compressed file format designed to reduce transfer file size and to increase security.
The interface is compatible with AVEVA Everything3D™ 2.1 and beyond, henceforth known as the base product.


The AVEVA Bocad Steel Interface Reference Manual has been written for users familiar with structural design practices, who may or may not have prior knowledge of the base product.
It is assumed that:
Users have a valid base product license and the software has been installed.
Users have a basic knowledge of the base product.
The user is familiar with the basic graphical user interface (GUI) features.
Users have a valid base product license and the software has been installed.
Users have a valid base product license and the software has been installed.
Users have a basic knowledge of the base product.
Users have a basic knowledge of the base product.
The user is familiar with the basic graphical user interface (GUI) features.
The user is familiar with the basic graphical user interface (GUI) features.


AVEVA Bocad Steel Interface is an application which allows you to export and import files using the AVEVA Bocad Steel Interface (ABS) format.


Use the ABSI - Export window to export a steel structure to an ABS file.

ABSI - Export


Click Mapping files to display the Export mapping files window which contains information about the mapping files that are to be used in the Export process.

The interface requires at least two external mapping tables to enable it to check that AVEVA Bocad Steel can accept the data. It also may use the Unicode mapping table if necessary. The mapping tables are for the Profiles and Materials between base product and the neutral file. The Unicode mapping table is to translate the base product Unicode strings into ASCII strings. The section Customize tells you how to arrange these files on the file system and what format they are to be. The interface also needs to know where the external mapping files are located on your computer network. For this, internal mapping tables are required. Refer to Internal Mapping Files which explains how to configure the interface to tell it where all the files are located.
You may have a generic set of mapping tables to map between the base product and AVEVA Bocad Steel. Or you may have a set for a particular steel fabricator.
The current file settings are indicated on the ABSI - Export mappings file window. Do not be concerned that the path name may be truncated by the insertion of the ellipsis (…): it is modified only for display purposes on the window.
The system also checks that these files are compatible with AVEVA Bocad Steel by checking only the identification line at the top of each mapping table. Refer to External Mapping Files for further information about the format of these mapping files.
The two main options are System and Manual which are activated by selecting the appropriate radio button.
System causes the interface to select automatically the mapping tables for AVEVA Bocad Steel according to the system configuration files.
Manual activates other radio buttons, which are initially greyed out for the System option. Selecting this option changes the window to be similar to below.

You can select the file type using the Profiles, Materials or Unicode radio buttons and enter the full path name of the file in the data entry area. You can also include system environment variables in the path name as long as they are in the proper base product format, for example AVEVA Bocad Steel %ENVVAR% being the base product representation of the ENVVAR environment variable.
Click carriage return, the interface checks for existence of the file and compatibility with AVEVA Bocad Steel.
You can choose by hand which mapping file to use by either entering its name in the text data entry field, or by using the Browse option to bring up a File Browser. You may use this browser to search for the relevant mapping file.
Once you have entered all the correct data on the Export Mapping Files window, click OK the interface variables are updated. Click Cancel to close the window, leaving the original interface variables unchanged.
Note:
The check is only that the file applies to AVEVA Bocad Steel and not that it is a correct file type or that its contents are correctly formatted.

Customize
Internal Mapping Files
External Mapping Files
Mapping files
Export mapping files
Customize
Internal Mapping Files
ABSI -
Export mappings file
External Mapping Files
Unicode
Note:
Export Mapping Files


Export file already exists
File exists, you will get the option to overwrite it.
Wrong place in database
You is most likely at the WORLD element in the database.
Illegal Transfer letter
You can only use transfer letters between A and Z.
Nothing to export
You has deselected both the Linear Members and Plates options.
Cannot decrement Transfer letter
You can not decrease the Transfer letter, only increment it.
Export file already exists
File exists, you will get the option to overwrite it.
Wrong place in database
You is most likely at the WORLD element in the database.
Illegal Transfer letter
You can only use transfer letters between A and Z.
Nothing to export
You has deselected both the Linear Members and Plates options.
Cannot decrement Transfer letter
You can not decrease the Transfer letter, only increment it.

Export file already exists
File exists, you will get the option to overwrite it.
Wrong place in database
You is most likely at the WORLD element in the database.
Illegal Transfer letter
You can only use transfer letters between A and Z.
Nothing to export
You has deselected both the Linear Members and Plates options.
Cannot decrement Transfer letter
You can not decrease the Transfer letter, only increment it.

Export file already exists
Wrong place in database
Illegal Transfer letter
Nothing to export
Cannot decrement Transfer letter


Click Export Information to display the ABSI - Export Information window which contains information about the export process.

You can either type the full path name of the output file, or click Browse to display a File Browser. The interface tests to see if the file exists and if it does, you will be asked whether you wish to overwrite it. If the file does exist and you want to overwrite it, the file mode beside Browse will change from WRITE to OVERWRITE. The output file is rechecked for write/overwrite status during the actual Export process. This is because you can perform Exports repeatedly without changing the output file name.
You can create and use any number of project header elements that are used to insert information into the transfer file. The interface assumes that there is a default one /FABGLOBAL. These elements are stored in the Application Data area. On export and import one can associate particular project header details with the transfer file. This can include the model offset and orientation to be applied to the model.
Different transfers can use different headers. You can select the correct one, or create a new one in from the Project Header drop down list. It is up to you to ensure that the correct header is used.

You can view the information contained by the chosen header element by clicking Inspect which displays the ABSI - Export Header window.

At first the entry fields are inactive so you can just read the contents. To modify the contents of the fields click Edit on the Export File Header Details window and the fields become active allowing you to enter any revised data. Click Apply and the data will be transferred back to the chosen header object, overwriting the original data. Click Cancel to leave all the data unchanged.

With this window, you can define a model offset and rotation for ease of use in Bocad.
Using the toggles on the ABSI - Export Information window, you can select whether to export Straight or Curved members, and Plates, with the additional option of including their holes. You are able to export Plates without their holes.
Note:
If you do not enter the full path name and just a plain file name, the output file is created in the folder which started the base product. You may also include system environment variables in the path name as long as they are in the proper base product format, for example: %ENVVAR% being the base product representation of the ENVVAR environment variable.
Note:
You cannot modify or delete /FABGLOBAL.

Export Information
ABSI - Export Information
Note:
ABSI - Export Header
Export File Header Details
Note:
ABSI -


If you have already selected something to Export, the Export Information window is updated to include the 3d world limit box of the export items.

You can see the limit box of the items to be exported in global terms, or in terms of the selected header element.

AVEVA Bocad Steel cannot handle such large coordinates as other AVEVA products, and here there is the opportunity to define in the file header a local origin, offset position and orientation in world coordinates. The model offset and orientation are used to translate the model in the ABS file. The East/North/Up position is entered in the fields indicated. It might take an iteration or two for the AVEVA model to be compatible with the AVEVA Bocad Steel model, such that the user of each system is happy with the Model Offset value. Once this is achieved, the Model Offset will be locked and it becomes fixed for future transfers. If you later try to modify these values, it must be an explicit decision. Refer to Managing the Model Limits and Offsets for further information.

The Model Offset values are stored in a system ZONE in the Application Data world /FABAPPDW. In case of emergency, using normal commands outside the interface, the ZONE can be locked or unlocked by hand.
You can transfer the minimum world coordinate of any model that is being displayed to the file header by pressing the World min button. Using the values as a basis, you can round the numbers to be more convenient.

Managing the Model Limits and Offsets
Export Information
Managing the Model Limits and Offsets


You can create a new header block by selecting New header… from the Project header drop down list.

The ABSI - Export Header window is displayed, you can populate the window with all the relevant details. Remember to fill in the name to appear in the header drop down list. This must be the basis of a valid Dabacon element name.
The Model Rotation is a rotation angle measured in degrees about the global Z axis following the right hand screw rule. It is usually assumed that the header is locked to prevent accidental changes

New header…
Project header
ABSI - Export Header
Model Rotation


This version of the interface allows you to transfer up to 5 numerical values and 5 text values to AVEVA Bocad Steel. The data are associated with linear members or plates. There is the equivalent functionality in AVEVA Bocad Steel, but they operate in different ways.
If required, you can transfer specific information about the model hierarchy to assist the AVEVA Bocad Steel user in managing the model in AVEVA Bocad Steel. This functionality is covered by user data, the interface comes with two sample configurations, but you can create more.

Use the toggles to turn fields on and off, you can then enter the Source type of element in the hierarchy above the element at which this data extraction is taking place. You can even extract data at the GENSEC, PANE or SCTN level. The attribute is the PDMS attribute name or the name of a user defined function that can perform more complex operations to return the correct value. As with all equivalent customization functionality, it is up to you to manage errors.
By default the system is suppled with two configurations, ANY and HIERARCHY. When viewing the HIERARCHY, ABSI Export User Data Set window is populated as follows:

If the attribute value is not immediately available, you can specify an alternative default attribute, function or value. And then if required enter descriptive text. The data on the window is encoded and included in the transfer file for the AVEVA Bocad Steel user to see what has been transferred.

This information is not stored in the database, but in the configuration file, which can be loaded by other projects. Refer to Customize for further information.
The interface checks that you are attempting to Export something and will output a message if there is nothing to export.
Once all the correct data has been entered on the Export Information window, click OK and the interface variables will be updated. Click Cancel to close the window, leaving the original interface variables unchanged.

Customize
ANY
HIERARCHY.
HIERARCHY, ABSI Export User Data Set
Customize
Export Information
Cancel


Click Run Information to display the Export window which allows you to view the Log File after the export process is complete by clicking to select the Log File? check box.

Click the Brief or Verbose radio buttons, you can choose which format messages are displayed.
The Test Run? option allows you to suppress the updating of all the Export flags. This is so that you can see if there will be a successful Export of the model. You may find that the Profile or Material mapping files are not quite up to date which might cause a failure in the Export process. Therefore, you can select this option to define this as a test run.
After the Export process has completed, Test Run? is reset to false. This is so that you are forced to state categorically each time the model is Exported that the run is a trial.
Once all the correct data has been entered on the Run Information window, click OK and the interface variables will be updated. Click Cancel to close the window, leaving the original interface variables unchanged.

Run Information
Export
Log File?
Brief
Verbose
Run Information


The Members pane allows you to navigate around the database hierarchy.
Though AVEVA E3D 2.1™ creates only GENSEC elements, old models might still contain SCTNs as well. The interface will still find SCTNs and export them. If a model is being imported and there are pre-existing SCTNs, these will be preserved, but all new members will be created as GENSECs.
If you add something to the Export list and has the item on display in a 3D Volume View it will be enhanced by changing its colour. The Export list is managed such that duplicate elements are removed and that items are exported only once.
There are several methods of adding elements to the Export list:
Add CE
Adds the current element to the list. This also implies all items below the current element in the database hierarchy. The WORL can not be added to the list.
Add by Pick
Allows you to select an item from the 3D Volume View. It is similar to other pick functions. Selection of this option brings up a Status window and puts you into a mode where an item from the 3D Volume View can be picked. You can also pick a sequence of items in succession to add to the Export list. Press Esc when complete. If you do not want to continue, press Esc.
Add Structure
Attempts to climb to the Structure owning the current element and add that to the Export list. A warning is displayed if there isn't an owning Structure.
There is also a set of methods by which you can remove items from the Export list. These options work only on entries in the Export list, rather than in the model. As with adding to the Export list, removing from the Export list will cause the item or items removed to be returned to the default colour as defined by this interface.
Note:
The colour may be different from the colour in which it may have originally been added to the Drawlist.
Remove CE
Looks for the name of the current element in the list and removes it if present.
Remove by Pick
Allows you to select something from the 3D Volume View and, if it is present in the Export list, the name will be removed. As with the Add by Pick option, you may select a series of items to attempt to remove from the Export list until Esc is pressed.
Remove Selected
Is a means by which the item selected in the Export list is subsequently removed. Select the item first in the list, then click Remove Selected.
Clear
Removes everything from the list.
Add CE
Adds the current element to the list. This also implies all items below the current element in the database hierarchy. The WORL can not be added to the list.
Add by Pick
Allows you to select an item from the 3D Volume View. It is similar to other pick functions. Selection of this option brings up a Status window and puts you into a mode where an item from the 3D Volume View can be picked. You can also pick a sequence of items in succession to add to the Export list. Press Esc when complete. If you do not want to continue, press Esc.
Add Structure
Attempts to climb to the Structure owning the current element and add that to the Export list. A warning is displayed if there isn't an owning Structure.
There is also a set of methods by which you can remove items from the Export list. These options work only on entries in the Export list, rather than in the model. As with adding to the Export list, removing from the Export list will cause the item or items removed to be returned to the default colour as defined by this interface.
Remove CE
Looks for the name of the current element in the list and removes it if present.
Remove by Pick
Allows you to select something from the 3D Volume View and, if it is present in the Export list, the name will be removed. As with the Add by Pick option, you may select a series of items to attempt to remove from the Export list until Esc is pressed.
Remove Selected
Is a means by which the item selected in the Export list is subsequently removed. Select the item first in the list, then click Remove Selected.
Clear
Removes everything from the list.
You may find that items are shown in the Export list do not exist, or have been renamed. The Export process will determine all the valid entries in the Export list and prepare the data accordingly. Clearing the list, or removing individual items will be performed as expected.
Add CE
Adds the current element to the list. This also implies all items below the current element in the database hierarchy. The WORL can not be added to the list.
Add by Pick
Allows you to select an item from the 3D Volume View. It is similar to other pick functions. Selection of this option brings up a Status window and puts you into a mode where an item from the 3D Volume View can be picked. You can also pick a sequence of items in succession to add to the Export list. Press Esc when complete. If you do not want to continue, press Esc.
Add Structure
Attempts to climb to the Structure owning the current element and add that to the Export list. A warning is displayed if there isn't an owning Structure.
There is also a set of methods by which you can remove items from the Export list. These options work only on entries in the Export list, rather than in the model. As with adding to the Export list, removing from the Export list will cause the item or items removed to be returned to the default colour as defined by this interface.
Note:
The colour may be different from the colour in which it may have originally been added to the Drawlist.
Remove CE
Looks for the name of the current element in the list and removes it if present.
Remove by Pick
Allows you to select something from the 3D Volume View and, if it is present in the Export list, the name will be removed. As with the Add by Pick option, you may select a series of items to attempt to remove from the Export list until Esc is pressed.
Remove Selected
Is a means by which the item selected in the Export list is subsequently removed. Select the item first in the list, then click Remove Selected.
Clear
Removes everything from the list.
Note:
Partial model transfers are supported by the interface, however, you must be aware of how the Import process handles partial model transfers. Refer to Comparison and Merging Processes.
Note:
The colour may be different from the colour in which it may have originally been added to the Drawlist.

Comparison and Merging Processes
Note:
Comparison and Merging Processes
Status
Note:
Add by Pick
Esc
Remove Selected.


Can't export the WORLD
You cannot export the WORLD
No owning Structure
Cannot climb to Structure element from current location in database.
Can't export the WORLD
You cannot export the WORLD
No owning Structure
Cannot climb to Structure element from current location in database.
Click Cancel to close the Export window.
Export executes the Export process. As it proceeds you are kept informed of the progress by means of messages at the bottom of the main window as well as by windows and prompts.
Can't export the WORLD
You cannot export the WORLD
No owning Structure
Cannot climb to Structure element from current location in database.

Can't export the WORLD
No owning Structure
Cancel
Export
Export


The Control drop-down menu has four options; Re-initialize, Configure, Map Converter and Exit. Changing any mapping files or any other variables:
The General drop-down menu has two options, Highlight and Clear ABSI History. Highlight displays the Highlighter window enabling you to identify new, changed and deleted items in the model. This has more relevance to the Import process, refer to Highlighting Changes in the Design for further information. Clear ABSI History enables one to clear the import/export history on the current element and all elements below that have date and time UDAs that are relevant to the AVEVA Bocad Steel Interface.
Re-initialize reloads files to save you having to rebuild the whole user interface from scratch
Configure enables you to define run parameters, model parameters, display colours and environment parameters. Refer to System Configuration for further information
Map Converter starts the tool that helps you rebuild Profile mapping files
Exit removes all forms and menus and global variables associated with the interface.
Re-initialize reloads files to save you having to rebuild the whole user interface from scratch
Re-initialize reloads files to save you having to rebuild the whole user interface from scratch
Configure enables you to define run parameters, model parameters, display colours and environment parameters. Refer to System Configuration for further information
Configure enables you to define run parameters, model parameters, display colours and environment parameters. Refer to System Configuration for further information
Map Converter starts the tool that helps you rebuild Profile mapping files
Map Converter starts the tool that helps you rebuild Profile mapping files
Exit removes all forms and menus and global variables associated with the interface.
Exit removes all forms and menus and global variables associated with the interface.

System Configuration
Highlighting Changes in the Design
Control
Re-
e
Configure, Map Converter and
Exit
Re-
e
Configure
System Configuration
Map Converter
Exit
General
Highlight
Clear ABSI
History
Highlight
Highlighter
Highlighting Changes in the Design
Clear ABSI History


Exporting from the base product all items are exported using millimetres as the distance units.
All reference data, such as any pre-existing reference model from the current session are removed before exporting anything. for further information on Importing and for further information about saving the reference model, refer to Import from AVEVA Bocad Steel.
Prior to any Export process, all fields are checked for validity.
In addition, there is an specific UDA, :FABEXCLUDE, attached to certain base product elements by which you can define whether the item is to be exported or not. Setting this logical flag to true will exclude the item from the Export process. Refer to UDAs for further information.
Before continuing, the Export process polls all the Configuration objects for the high water mark on Transfer and Revision numbers. It then updates the object applicable to the current MDB and user to contain the latest Transfer value. The list of all items listed in the Export list is then stored on Header element.
After verifying that all the data is correct and valid, the external program is called. The interface waits for a certain time until the program is finished. This waiting time is user configurable. If there are errors raised by the external program you are notified and more detailed information is placed in the log file. If the waiting period expires without the interface detecting that the external program has completed - it may have crashed, or even not exist, you will be asked if to carry on waiting for another time unit.

Click Yes and the interface will wait for another period of time. Click No to stop the interface where it is. Finally the system will indicate its completion, whether successful or not. This completion message should be read in conjunction with the log file, if any errors are indicated (if that option has been selected on the Run Information window).

To inspect the log file later, save it with the File > Save as option in the File Viewer window which will bring up a File Browser, or by clicking Save as to the suggested filename. Either way, if the file already exists, you will be asked whether to overwrite it. The log file window may then be closed by clicking Cancel.

If the Brief mode has been chosen on the Run Information window for displaying the log file, the window displaying the log file will filter out all Warning messages, leaving only the Error messages. Saving the log file, however, all messages will be retained in the file.
Is the output file named?
Is anything going to be exported?
Are the mapping tables compatible with AVEVA Bocad Steel?
Is there a valid Steel Standard table?
Is the output file named?
Is the output file named?
Is anything going to be exported?
Is anything going to be exported?
Are the mapping tables compatible with AVEVA Bocad Steel?
Are the mapping tables compatible with AVEVA Bocad Steel?
Is there a valid Steel Standard table?
Is there a valid Steel Standard table?

Import from AVEVA Bocad Steel
UDAs
Import from AVEVA Bocad Steel
UDAs
Run Information
File Viewer
Run Information


File does not exist
Somehow there is no log file. Are there issues regarding access rights to your work folder?
File does not exist
Somehow there is no log file. Are there issues regarding access rights to your work folder?

File does not exist
Somehow there is no log file. Are there issues regarding access rights to your work folder?

File does not exist


A series of checks is made before a Linear Member is output.
If any of the above criteria is not satisfied, the linear member does not even get exported to the output file.
As has been indicated before, Linear Members can be transferred as either Straight or Curved. However, GENSECs can be compound shapes with both straight and arc sections.
Once the Linear Member has been output, the relevant UDAs specific for the interface associated with Export are updated. These are principally the element's internal ID and UUID numbers and transfer and revision numbers. This is only the minimum core database changes that affect the modification dates and times.
The interface may not be able to update the export information on the elements. This would usually be because the database is read-only. If this is the case, a session related macro file is produced for execution immediately afterwards, or when one has write access to the database. This file is called updateVersionNos<export date/time>.mac and is stored in your work folder.
Is the SPRE set?
Is it a zero length member?
Does it have a valid material?
Is the Justification Pline mappable to a Cardinal Point if it is not a Cardinal Point itself?
Are the start and end points valid?
Is the SPRE set?
Is the SPRE set?
Is it a zero length member?
Is it a zero length member?
Does it have a valid material?
Does it have a valid material?
Is the Justification Pline mappable to a Cardinal Point if it is not a Cardinal Point itself?
Is the Justification Pline mappable to a Cardinal Point if it is not a Cardinal Point itself?
Are the start and end points valid?
Are the start and end points valid?
Note:
This will have an effect on the subsequent import process as the member will appear to have been deleted by AVEVA Bocad Steel since its export. In fact, the linear member never made the transfer to there in the first place.

Note:


Illegal or unset SPRE - not exported
SPRE must be valid.
Zero length Linear Member - not exported
Length less than user definable tolerance.
No material information - not exported
Cannot determine material properties for member.
No material match for nnnn. - Unknown material
:FABMGRADE cannot be matched with a material in the Properties database.
No material property match
As above
Inconsistent material
specification
The element's MATR and :FABMGRADE attributes are not consistent.
Multiply defined entries in
Material Table
Either a material to be mapped or a mapped profile appears more than once in the material file.
No match for material
The material is not in the material file
Syntax Error
Other, less specific, errors.
Unrecognized Parse State
This should not occur. If it does then it indicates a system error. Although the error is non-fatal it should be reported. A number representing the parse state will also be output.
No match for Cardinal Point nnnn
Pline or Cardinal Point not recognized. Neutral axis (Cardinal Point 10) assumed.
No Cardinal Point nnnn
JUSL unset.
Bad Cardinal Point nnnn
Cardinal Point/Pline identified is not valid. Does it exist? Neutral axis (Cardinal Point 10) assumed.
Problem exporting entity
Other errors found.
Profile cannot be mapped
The profile is not in the profile mapping file.
Profile is not in the standard
The profile is in the profile mapping file but is not in any one of the set of standards.
Profile is not the default
The profile is in the profile mapping file and is in one of the set of standards, but not the default standard.
Multiply defined entries in
Profile Table
Either a profile to be mapped or a mapped profile appears more than once in the profile mapping file.
Illegal or unset SPRE - not exported
SPRE must be valid.
Zero length Linear Member - not exported
Length less than user definable tolerance.
No material information - not exported
Cannot determine material properties for member.
No material match for nnnn. - Unknown material
:FABMGRADE cannot be matched with a material in the Properties database.
No material property match
As above
Inconsistent material
specification
The element's MATR and :FABMGRADE attributes are not consistent.
Multiply defined entries in
Material Table
Either a material to be mapped or a mapped profile appears more than once in the material file.
No match for material
The material is not in the material file
Syntax Error
Other, less specific, errors.
Unrecognized Parse State
This should not occur. If it does then it indicates a system error. Although the error is non-fatal it should be reported. A number representing the parse state will also be output.
No match for Cardinal Point nnnn
Pline or Cardinal Point not recognized. Neutral axis (Cardinal Point 10) assumed.
No Cardinal Point nnnn
JUSL unset.
Bad Cardinal Point nnnn
Cardinal Point/Pline identified is not valid. Does it exist? Neutral axis (Cardinal Point 10) assumed.
Problem exporting entity
Other errors found.
Profile cannot be mapped
The profile is not in the profile mapping file.
Profile is not in the standard
The profile is in the profile mapping file but is not in any one of the set of standards.
Profile is not the default
The profile is in the profile mapping file and is in one of the set of standards, but not the default standard.
Multiply defined entries in
Profile Table
Either a profile to be mapped or a mapped profile appears more than once in the profile mapping file.

Illegal or unset SPRE - not exported
SPRE must be valid.
Zero length Linear Member - not exported
Length less than user definable tolerance.
No material information - not exported
Cannot determine material properties for member.
No material match for nnnn. - Unknown material
:FABMGRADE cannot be matched with a material in the Properties database.
No material property match
As above
Inconsistent material
specification
The element's MATR and :FABMGRADE attributes are not consistent.
Multiply defined entries in
Material Table
Either a material to be mapped or a mapped profile appears more than once in the material file.
No match for material
The material is not in the material file
Syntax Error
Other, less specific, errors.
Unrecognized Parse State
This should not occur. If it does then it indicates a system error. Although the error is non-fatal it should be reported. A number representing the parse state will also be output.
No match for Cardinal Point nnnn
Pline or Cardinal Point not recognized. Neutral axis (Cardinal Point 10) assumed.
No Cardinal Point nnnn
JUSL unset.
Bad Cardinal Point nnnn
Cardinal Point/Pline identified is not valid. Does it exist? Neutral axis (Cardinal Point 10) assumed.
Problem exporting entity
Other errors found.
Profile cannot be mapped
The profile is not in the profile mapping file.
Profile is not in the standard
The profile is in the profile mapping file but is not in any one of the set of standards.
Profile is not the default
The profile is in the profile mapping file and is in one of the set of standards, but not the default standard.
Multiply defined entries in
Profile Table
Either a profile to be mapped or a mapped profile appears more than once in the profile mapping file.

Illegal or unset SPRE - not exported
Zero length Linear Member - not exported
No material information - not exported
No material match for nnnn. - Unknown material
No material property match
Inconsistent material
specification
Multiply defined entries in
Material Table
No match for material
Syntax Error
Un
ed Parse State
No match for Cardinal Point nnnn
No Cardinal Point nnnn
Bad Cardinal Point nnnn
Problem exporting entity
Profile cannot be mapped
Profile is not in the standard
Profile is not the default
Multiply defined entries in
Profile Table


Panels in the base product are to be transferred as Plates. This covers stiffeners, floor and toe plates. Bent plates are also transferred if they are expressed as their component flat plates. If Bent Plates are to be treated as Angle linear members then they should be modelled as such.
If the base product’s penetration functionality is used to generate Catalogue holes, the resultant holes, kicker plates and stiffeners are not exported because they are contained in a Catalogue definition. Some holes and negative primitives can be exported. Refer to Transferring Holes for further information.
The Description attribute will be used to store the flooring type, such as grating or chequer plate. This is passed as the type field (up to 24 characters).
The Material Grade transferred represents the material type. This is a text attribute, rather than the number field in the base product. Therefore a User Defined Attribute (UDA), :FABMGRADE, has been defined within the base product to store this information.
A basic series of tests is performed before the Plate is exported.
If any of the above criteria is not satisfied, the plate does not get exported in the output file.
Once the Plate has been output, the relevant UDAs specific for the interface associated with Export are updated. These are principally the element's internal ID and the UUID numbers and transfer and revision numbers.
Although both plates and holes are supposed to have a clockwise definition (right hand screw rule) for their boundaries in either the base product or in the file, the interface must be able to cope with either clockwise or anti clockwise directions. In exporting plates the vertex order is converted to satisfy the right-hand screw rule.
Plates with curved and straight segments to their boundaries can be transferred both to and from the base product. Because of the difference between the base product and boundary definitions, vertices will stand a high chance of being created in different places. Further, in order to recreate the shape, there may be a different number of vertices in the boundary. This makes it very difficult to compare the boundaries, especially on import.
In order to assist the transfer of these complex shapes, the vertices are given a type code as a design parameter. The code indicates whether the following boundary segment is straight, an arc, or whether the vertex is a created one not contained in the AVEVA Bocad Steel Interface file.
Is there any geometry?
Is the height valid?
Is it justified correctly?
Does it have a valid material?
Are there enough vertices?
Is there any geometry?
Is there any geometry?
Is the height valid?
Is the height valid?
Is it justified correctly?
Is it justified correctly?
Does it have a valid material?
Does it have a valid material?
Are there enough vertices?
Are there enough vertices?
Note:
Any edge preparation details and modelling, such as grinding, will be lost in the transfer operation.
Note:
This has an effect on the subsequent import process as the plate will appear to have been deleted by AVEVA Bocad Steel since its export. In fact, the plate never made the transfer in the first place.
Note:
Importing a Plate previously defined in base product, you may find the order of vertices to have been reversed.

Transferring Holes

Transferring Holes
Note:
Note:
Note:


Circular plates in the base product are identified by the number of vertices, the geometry and possibly the vertex type codes. There is no short-hand definition of a circular plate in the base product. As a result, a certain amount of geometric testing is involved in identifying and exporting circular plates. The interface recognizes only 4 or 5 point circles, where the 5th point is a duplicate of the first point.


No geometry information - not exported
No PLOO element. Plate cannot be exported.
Plate too thin -
not exported
Thickness less than user defined minimum. Plate not exported.
Not enough vertices -
not exported
Fewer than 3 vertices. Cannot define valid geometry so Plate is not exported.
No material information - not exported
Cannot determine material properties for member. A matching set of :FABMGRADE and Matref cannot be determined.
No material match for nnnn
Unknown material. :FABMGRADE cannot be matched with a material in the Properties database.
No material property match
As above
Inconsistent material
specification
The element's MATR and :FABMGRADE attributes are not consistent.
Multiply defined entries in
Material Table
Either a material to be mapped or a mapped profile appears more than once in the material mapping file.
No match for material
The material is not in the material mapping file.
Syntax Error
Other, less specific, errors.
Unrecognized Parse State
This should not occur. If it does then it indicates a system error. Although the error is non-fatal it should be reported. A number representing the parse state will also be output.
Problem exporting entity
Other errors found.
No geometry information - not exported
No PLOO element. Plate cannot be exported.
Plate too thin -
not exported
Thickness less than user defined minimum. Plate not exported.
Not enough vertices -
not exported
Fewer than 3 vertices. Cannot define valid geometry so Plate is not exported.
No material information - not exported
Cannot determine material properties for member. A matching set of :FABMGRADE and Matref cannot be determined.
No material match for nnnn
Unknown material. :FABMGRADE cannot be matched with a material in the Properties database.
No material property match
As above
Inconsistent material
specification
The element's MATR and :FABMGRADE attributes are not consistent.
Multiply defined entries in
Material Table
Either a material to be mapped or a mapped profile appears more than once in the material mapping file.
No match for material
The material is not in the material mapping file.
Syntax Error
Other, less specific, errors.
Unrecognized Parse State
This should not occur. If it does then it indicates a system error. Although the error is non-fatal it should be reported. A number representing the parse state will also be output.
Problem exporting entity
Other errors found.

No geometry information - not exported
No PLOO element. Plate cannot be exported.
Plate too thin -
not exported
Thickness less than user defined minimum. Plate not exported.
Not enough vertices -
not exported
Fewer than 3 vertices. Cannot define valid geometry so Plate is not exported.
No material information - not exported
Cannot determine material properties for member. A matching set of :FABMGRADE and Matref cannot be determined.
No material match for nnnn
Unknown material. :FABMGRADE cannot be matched with a material in the Properties database.
No material property match
As above
Inconsistent material
specification
The element's MATR and :FABMGRADE attributes are not consistent.
Multiply defined entries in
Material Table
Either a material to be mapped or a mapped profile appears more than once in the material mapping file.
No match for material
The material is not in the material mapping file.
Syntax Error
Other, less specific, errors.
Unrecognized Parse State
This should not occur. If it does then it indicates a system error. Although the error is non-fatal it should be reported. A number representing the parse state will also be output.
Problem exporting entity
Other errors found.

No geometry information - not exported
Plate too thin -
not exported
Not enough vertices -
not exported
No material information - not exported
No material match for nnnn
No material property match
Inconsistent material
specification
Multiply defined entries in
Material Table
No match for material
Syntax Error
Un
ed Parse State
Problem exporting entity


There is a limitation as to which holes are exported. Only secondary PLOO boundaries and NXTR elements can be handled as well as NBOX and NCYL under certain conditions. PLOOs are full depth penetrations: partial penetrations can be modelled using NXTR elements. Circular boundaries of holes and indentations can be imported and exported if recognized as such, by having 4 unique fillet vertices.
On import vertices in boundaries are given a DESP value according to the list below.

                  PVTLastPoint

                  0

                  PVTStraight

                  1

                  PVTArc

                  2

                  PVTFillet

                  3

                  PVTCircle

                  4

Using these values specific shapes, such as circles, ellipses, ., can be detected.
A message is output when the export process ignores most non loop-based negative primitives. This is because it is difficult to determine the geometric intersection with the PANEL, especially if the primitive axis is not perpendicular to the plate plane. In the future it may be possible to handle more of them, but only within tight geometrical constraints. Negative boxes and cylinders could be transferred only if a principal axis is parallel to the plate's normal. This means that the cylinder's Z-axis, and any of the box's X, Y or Z-axis must be parallel to the plate normal. We even have to limit NXTR elements those with an extrusion vector parallel to the panel plane normal. Some negatives are not exported at all:
(NBOX)
NPOLYH
(NCYL)
NSLC
NSno
NDIS
NCON
NPYR
NCTO
NRTO
(NXTR)
NREV
(NBOX)
NPOLYH
(NCYL)
NSLC
NSno
NDIS
NCON
NPYR
NCTO
NRTO
(NXTR)
NREV

Imported holes will be either NXTR or PLOO elements. A full penetration will be a PLOO, and a partial penetration will be an NXTR.
Any other negatives will not be compared or merged on import. Other pre-existing negatives will be just moved and updated to maintain their original position and orientation.

                  PVTLastPoint

                  0

                  PVTStraight

                  1

                  PVTArc

                  2

                  PVTFillet

                  3

                  PVTCircle

                  4

(NBOX)
NPOLYH
(NCYL)
NSLC
NSno
NDIS
NCON
NPYR
NCTO
NRTO
(NXTR)
NREV

                  PVTLastPoint

                  0

                  PVTStraight

                  1

                  PVTArc

                  2

                  PVTFillet

                  3

                  PVTCircle

                  4

PVTLastPoint
0
PVTStraight
1
PVTArc
2
PVTFillet
3
PVTCircle
4


The use of SAVEWORK on Export and Import

In order for the AVEVA Bocad Steel Interface, and more specifically the AVEVA Bocad Steel program, to be able to detect model changes, the interface needs to manage modification dates and times. These values are stored in the database as text strings, based on the last recorded Dabacon model modification date and time. For us to then save these dates and times we need to lock the changes in with a SAVEWORK. This implies some significant time difference between setting a text string attribute and the SAVEWORK. This time difference is model size dependent. We compare the database modification times with the time stored on the attribute with a 5 minute time buffer in order to determine, to the best of our ability, whether an element has been changed.
Importing does not do a SAVEWORK by itself, but because of this, there can become some significant time difference between the import, modification and database dates and times. Import, creation and modification dates and times are passed through the ABS file, but these can be significantly different from the Dabacon date and time.
Overall, this will make it difficult to compare models purely on dates and times.


Minimizing changes to the database on Import are not as critical because we are changing the model anyway. However, only elements that are new or modified will have the Import date/time values set. Elements that are identical between the exiting model and the incoming model will not be affected. If necessary, the Modification and Creation date/time values are taken from the ABS file. Again, to minimize the time difference a database SAVEWORK is executed as soon as possible after the model import and merge. However, for large models, the time difference between Importing and SAVEWORK can be significant.
The critical time interval in this process is the time taken to compare and merge the models. This is also affected by the response time of the user to the screen prompt asking whether to proceed with the import process. f he should go for a coffee during the import, and come back to see the screen prompt, OK to Merge? all this time will be accumulated in the import process.

OK to Merge?


Use the ABSI - Import window to import a steel structure from an AVEVA Bocad Steel Interface file.

A Warning window may be displayed stating mapping files are not found, this means local versions have not been set up, use the default set provided with the product.

ABSI -
Import
Warning


Click Mapping files to display the ABSI - Import mapping files window populated with information about the mapping files that will be used in the Import process.

The interface requires at least two external mapping tables to enable the interface to check that the base product can accept the data. It also may use the internal Profile Orientation and/or the Unicode mapping table if necessary. The mapping tables are for the Profiles, Materials, Unicode text string and for mapping the Profile orientations between the AVEVA Bocad Steel Interface file and the AVEVA steel catalogue. The section Customize explains how you can arrange these files on the file system and what format they are to be. The interface also needs to know where the external mapping files are located on your computer network. For this internal mapping tables are required. Refer to Customize which explains how you can configure the interface to let it know where all the files are located.
You can have a generic set of mapping tables to map between the base product and AVEVA Bocad Steel. Or you can have a set for a particular steel fabricator.
The current file settings are indicated on this window.
The system also checks that these files are compatible with AVEVA Bocad Steel by checking only the identification line at the top of each mapping table. Refer to Internal Mapping Files for further information about the format of these mapping files.
The two main options are Auto and Manual which are activated by selecting the appropriate radio button on the left hand side of the Import mapping files window.
The Auto option causes the interface to select automatically the mapping tables for AVEVA Bocad Steel, according to the system configuration files. When you come to execute the Import process, the Auto flag will cause the correct mapping files to be used based on the Input file header.
The Manual option activates other buttons, which are initially greyed out for the System option. Selecting this option changes the window to be similar to below.

You can select the file type using the Profiles, Materials or Unicode radio buttons above the text data entry field and enter the full path name of the file in the data entry area. You can also include system environment variables in the path name as long as they are in the proper base product format, for example: %ENVVAR% being the representation of the ENVVAR environment variable.
On clicking carriage return, the interface will check for existence of the file and its compatibility with AVEVA Bocad Steel.
You can choose by hand which mapping file to use by either entering its name in the text data entry field, or by using the Browse option to bring up a File Browser. Use this browser to search for the relevant mapping file.
Once all the correct data has been entered on the Import mapping files window, click OK and it updates the interface variables. Click Cancel to close the window, leaving the original interface variables unchanged.
Note:
Do not be concerned that the path name may be truncated by the insertion of the ellipsis (…): it is modified only for display purposes on the window.
Note:
The check is only that the file applies to AVEVA Bocad Steel and not that it is a correct file type or that its contents are correctly formatted.

Customize
Customize
Internal Mapping Files
Mapping files
ABSI -
Import mapping files
Customize
Customize
Note:
Internal Mapping Files
Import mapping files
Unicode
Note:
Import mapping files


Internal error
Internal lists are not in step.
Cannot find suitable
internal mapping list
Internal mapping files not found.
Suitable Mapping Table File not found
Mapping table found is not correct or it does not exist.
Not a suitable Mapping
Table File
Incorrect format of file, or empty file.
Bad Map File
Mapping file is not correct format. Possibly it is from another operating system.
Error on File Browser window
You has entered incorrect data on the file browser.
Internal error
Internal lists are not in step.
Cannot find suitable
internal mapping list
Internal mapping files not found.
Suitable Mapping Table File not found
Mapping table found is not correct or it does not exist.
Not a suitable Mapping
Table File
Incorrect format of file, or empty file.
Bad Map File
Mapping file is not correct format. Possibly it is from another operating system.
Error on File Browser window
You has entered incorrect data on the file browser.

Internal error
Internal lists are not in step.
Cannot find suitable
internal mapping list
Internal mapping files not found.
Suitable Mapping Table File not found
Mapping table found is not correct or it does not exist.
Not a suitable Mapping
Table File
Incorrect format of file, or empty file.
Bad Map File
Mapping file is not correct format. Possibly it is from another operating system.
Error on File Browser window
You has entered incorrect data on the file browser.

Internal error
Cannot find suitable
internal mapping list
Suitable Mapping Table File not found
Not a suitable Mapping
Table File
Bad Map File
Error on File Browser window


From the Import window, click Import Information to display the Import Information window which is populated with information about the import process.

You either types the full folder path name of the input file, or clicks Browse to bring up a File Browser. The interface tests to see if the file exists and if it does not you will be warned. As well as testing for the existence of the file, it is also tested for being a valid file by inspection of its header details.
On reading the file header information the interface will attempt to select a suitable header. If one does not exist you will be asked whether to create one for the import. If you want to override the recommended header element, it will be checked for compatibility.
You can view the header information of the chosen input file, click Inspect, to display the Input File Header Details from window with which you can determine whether the file is the correct one to Import.
From the Attributes page, you can see what user data is being transferred from AVEVA Bocad Steel.

Use the check boxes on the Import Information window, to select whether to import Linear Members and/or Plates or Holes.
Once all the correct data has been entered on the Import Information window, click OK and the interface variables updates. Click Cancel to close the window, leaving the original interface variables unchanged.
Note:
If you do not enter the full path name, the input file is assumed to be in the folder from which started the base product. You can also include system environment variables in the path name as long as they are in the proper base product format, for example. %ENVVAR% being the base product representation of the ENVVAR environment variable.

Import
Import Information
Import Information
Note:
Input File Header Details from
Attributes
Import Information
Holes
Import Information


Import file does not exist
File specified does not exist.
Not an ABSI File
File specified is not an ABSI file. This may also arise if the file you are inspecting has been transferred across hardware platforms.
Nothing to import
You deselect everything.
Import file does not exist
File specified does not exist.
Not an ABSI File
File specified is not an ABSI file. This may also arise if the file you are inspecting has been transferred across hardware platforms.
Nothing to import
You deselect everything.

Import file does not exist
File specified does not exist.
Not an ABSI File
File specified is not an ABSI file. This may also arise if the file you are inspecting has been transferred across hardware platforms.
Nothing to import
You deselect everything.

Import file does not exist
Not an ABSI File
Nothing to import


When a user selects a file to import from AVEVA Bocad Steel, the file can be inspected to see what additional data is being transferred.

From this window, you can see what data is being considered for transfer, the selected check boxes show what data will actually be transferred. There is also a field for a description of the data.
Once imported into PDMS, the data will be stored in UDAs, the numerical values will be stored in a real array, :FABRADATA. The text strings will be stored in an individual text UDA, :FABTADATA to :FABTEDATA. The index of these will direct you to the correct location.
Note:
Importing and exporting are two separate operations. The user data exported might have no correlation to the user data being imported. It is information that the receiver of the transfer file might find useful, once imported, you can use the data.

Note:


From the Import window, click Run Information to display the Import Run Information window. The window allows you to view the Log File after the import process is complete by clicking the Log File? check box.

Click either the Brief or Verbose radio buttons you can choose which format messages are displayed, the detail of these messages is given elsewhere.
As part of the Import process a reference model is constructed against which comparisons will be made. Save Reference Model allows you to keep this. Otherwise it will be deleted on completion of the Import process.
After the Import merging process has been performed, you can sort all new items into FRMW (Framework) elements according to their Material type. This option is selected by clicking the Sort on Material Type option.
During the Import process, comparisons are made for Linear Members and Plates between the existing model data and the imported model data. The default system configuration compares all the relevant data transferred in the file between the models. However, you can select which attributes may be ignored by the comparison process by clicking Edit Attribute Comparison List to display the Comparison Checklist window.

Use this window to deselect attributes for comparison but be aware that strange results may occur especially if you ignore positional and rotational attributes.
Finally, there are two validity checks you can perform on the incoming data which will make sure a subsequent Import run will have a chance of success. Activating these options overrides completely the Import choices made on the main window. With these validity checks you will be able to see a log file before any data is merged whatsoever.
Profile Mapping? enables you to see if the incoming Linear Member Profile specifications will be successfully mapped between systems. This is a relatively fast transaction as the file is just passed through the external program without any subsequent import or comparison in the base product. You will then be able to see the log file produced and take appropriate action.
There is a risk in either package that entity UUIDs may be duplicated. The Duplicate UUID selector gadget enables you to check for duplicate UUIDs in the incoming model. There are three options: NONE, NEW and GLOBAL. NONE deactivates the gadget and no checks are made. The import process just goes through unhindered. The NEW option allows you to check only the new imported items for duplicate UUIDs, while the GLOBAL option enables you to search all the available databases for duplicate UUIDs. Obviously these searches may involve a certain amount of time, but for the sake of validity, they would be worth using.
Once all the correct data has been entered on the Run Information window, click OK and the interface variables updates. Click Cancel to close the window, leaving the original interface variables unchanged
Note:
This reference model will be deleted next time you Exports or Imports anything. It is only transient data. Also, it may not be a complete model as some items may already have been transferred into the main model on merging.

Import
Run Information
Import Run Information
Log File?
Brief
Verbose
Note:
Comparison Checklist
UUID
Run Information


On the Import window the Members list can be used to navigate around the database hierarchy.
You must state where the Imported model is to be located. This must be a SITE, ZONE or STRU element. Using the Members list, navigate round the database to the correct storage location and click Store in: CE. The window text indicates where the Imported model will reside. If there is not enough space on the window, the SITE's reference number is output rather than its name.
The Import process is essentially a three phase operation. First a reference model is built which is then compared with the original model identified during the Store in: CE operation. Then, if required, the changes, additions and deletions encountered in the comparison phase are transferred to the actual model. Thus, using the Operations toggles, you can control how the Import process is to proceed.
You should be aware of how the model manages partial model transfers and where temporarily imported data goes before it is merged into the pre-existing model. See the sections describing the Import, Comparison and Merging processes.
Compare + Merge
Goes through the complete Import process - that is the import, comparison and merging are all completed without any interaction with you. This is only to be performed if you are absolutely sure that they will get the desired result.
Compare ( + Merge )
Imports the model and compare the reference model with the location chosen to be the storage area. At this point you will be asked whether to merge the models. Click Yes to continue with the merge process and complete the Import.
Merge from File
Takes a merge command file produced during the current session only and imports it directly into the model. The reference model must not have been deleted beforehand. Otherwise, you may lose any elements added to the model by AVEVA Bocad Steel. This is a very quick option and there are no checks, except what you want to do it.
Compare + Merge
Goes through the complete Import process - that is the import, comparison and merging are all completed without any interaction with you. This is only to be performed if you are absolutely sure that they will get the desired result.
Compare ( + Merge )
Imports the model and compare the reference model with the location chosen to be the storage area. At this point you will be asked whether to merge the models. Click Yes to continue with the merge process and complete the Import.
Merge from File
Takes a merge command file produced during the current session only and imports it directly into the model. The reference model must not have been deleted beforehand. Otherwise, you may lose any elements added to the model by AVEVA Bocad Steel. This is a very quick option and there are no checks, except what you want to do it.

Compare + Merge
Goes through the complete Import process - that is the import, comparison and merging are all completed without any interaction with you. This is only to be performed if you are absolutely sure that they will get the desired result.
Compare ( + Merge )
Imports the model and compare the reference model with the location chosen to be the storage area. At this point you will be asked whether to merge the models. Click Yes to continue with the merge process and complete the Import.
Merge from File
Takes a merge command file produced during the current session only and imports it directly into the model. The reference model must not have been deleted beforehand. Otherwise, you may lose any elements added to the model by AVEVA Bocad Steel. This is a very quick option and there are no checks, except what you want to do it.
Note:
These options may be completely overridden if you want to perform a validity check as on the Run Information window.

Import
Note:
Run Information
Yes


Bad element type
You is not trying to store imported data at a SITE, ZONE or STRU element.
Bad element type
You is not trying to store imported data at a SITE, ZONE or STRU element.

Bad element type
You is not trying to store imported data at a SITE, ZONE or STRU element.

Bad element type


Cancel closes the Import window.
Import executes the Import process. As it proceeds you are kept informed of the progress.

Import


The Control drop-down menu has four options; Re-initialize, Configure, Map Convertor and Exit. Changing any mapping files or any other variables:
The General drop-down menu has two options, Highlight and Clear ABSI History. Highlight displays the Highlighter window enabling you to identify new, changed and deleted items in the model. This has more relevance to the Import process, refer to Highlighting Changes in the Design for further information. Clear ABSI History enables one to clear the import/export history on the current element and all elements below that have date and time UDAs that are relevant to the AVEVA Bocad Steel Interface.
Re-initialize reloads files to save you having to rebuild the whole user interface from scratch
Configure enables you to define run parameters, model parameters, display colours and environment parameters. Refer to System Configuration for further information
Map Convertor starts the tool that helps you to rebuild Profile mapping files.
Exit removes all forms and menus and global variables associated with the interface.
Re-initialize reloads files to save you having to rebuild the whole user interface from scratch
Re-initialize reloads files to save you having to rebuild the whole user interface from scratch
Configure enables you to define run parameters, model parameters, display colours and environment parameters. Refer to System Configuration for further information
Configure enables you to define run parameters, model parameters, display colours and environment parameters. Refer to System Configuration for further information
Map Convertor starts the tool that helps you to rebuild Profile mapping files.
Map Convertor starts the tool that helps you to rebuild Profile mapping files.
Exit removes all forms and menus and global variables associated with the interface.
Exit removes all forms and menus and global variables associated with the interface.

System Configuration
Highlighting Changes in the Design
Control
Re-
e
Configure, Map Convertor and
Exit
Re-
e
Configure
System Configuration
Map Convertor
Exit
General
Highlight
Clear ABSI
History
Highlight
Highlighter
Highlighting Changes in the Design
Clear ABSI History


After clicking OK the fields in the window are checked for validity:
After verifying that all the data is correct and valid, the external program is called. The interface waits for a certain time until the program is finished. This waiting time is user configurable. If there are errors raised by the external program you are notified and more detailed information is placed in the log file. If the waiting period expires without the interface detecting that the external program has completed - it may have crashed, or not even exist. You will be asked if want to carry on waiting for another time unit.

Click Yes and the interface will wait for another period of time. Click No causes the interface to stop where it is. Finally the system will indicate its completion, whether successful or not. This completion message should be read in conjunction with the log file, if any errors are indicated.
You will be alerted to unsuccessful runs by the external program displaying an Error window, after which the process exits.

If the external program successfully completes, the processed file will be imported into the design model. Any reference data which may have been retained by you before will have been deleted beforehand.
The status line will inform you of the progress on importing the data, the length of the input macro is about 25 times the number of elements. Thus a file transferring 300 members is about 7500 lines long. This calculation can be useful when considering the maximum input file size. The size applies to this file and not to the original SDNF source file.
After the Import of everything, the material properties are reconciled with the :FABMGRADE attribute and, if possible, the MATR is also set to point to the appropriate property in the Properties database.
At this point, if you have chosen to be asked whether to Merge after the Compare operation, Confirm window is displayed.

Click Yes and the interface continues with the Merge process.
Click No and the Import process skips the Merging, but you are then given a chance to store the Merging commands in a file for use later on only in the current base product session. You cannot use a file from a previous session as the Import data may be incorrect.

You can save the Merge command file and then be prompted whether to see the Import log file. This Merge command file may then be used in the Merge from File option on the Import window. This latter option needs the reference model from this run to be kept. Therefore, you do not have the option below.
If you have merged the models, they will then be asked if they want to keep the reference model, verifying the option selected on the Run Information window.

Finally, you are asked whether to view the log file, if they have chosen that option on the Run Information window.

If you want to inspect the log file, they can then save it with the File > Save as option in the File Viewer window which will bring up a File Browser, or by clicking Save as to the suggested filename. If the file exists, you will be asked whether they want to overwrite it. The log file window can then be closed by clicking Cancel.

If you have chosen Brief mode on the Run Information window for displaying the log file, the window displaying the log file will filter out all Warning messages, leaving only the Error messages. To save the log file, however, all messages will be retained in the file.
Clicking on a line containing a base product reference number causes all graphical views to zoom in to the chosen item and to identify it. The interface also navigates to the item in the database and leave you there to perform any queries or operations.
Is the storage location valid?
Is there a valid input file?
Do we need to convert the file across platforms?
Are the Profile and Material mapping files valid?
Is the storage location valid?
Is the storage location valid?
Is there a valid input file?
Is there a valid input file?
Do we need to convert the file across platforms?
Do we need to convert the file across platforms?
Are the Profile and Material mapping files valid?
Are the Profile and Material mapping files valid?
Note:
This reference model will not be the complete model as imported as various attributes and elements might have been modified, deleted or moved around.

OK
Yes
No
base product
Import
Run Information
Note:
Run Information
File Viewer
Run Information


File does not exist
Somehow there is no log file Are there issues regarding access rights to your work folder?
Input file name not
specified
Something strange here. The name of the input command file generated has been forgotten.
Import file does not exist
Something strange here. The input command file has not been generated or it has been deleted, or is not found in the expected folder. Are there issues regarding access rights to your work folder?
Data store unset
The data store variable is unset or the SITE you have intended to store the imported data in is invalid. Has it been deleted since you set the store variable?
File does not exist
Somehow there is no log file Are there issues regarding access rights to your work folder?
Input file name not
specified
Something strange here. The name of the input command file generated has been forgotten.
Import file does not exist
Something strange here. The input command file has not been generated or it has been deleted, or is not found in the expected folder. Are there issues regarding access rights to your work folder?
Data store unset
The data store variable is unset or the SITE you have intended to store the imported data in is invalid. Has it been deleted since you set the store variable?

File does not exist
Somehow there is no log file Are there issues regarding access rights to your work folder?
Input file name not
specified
Something strange here. The name of the input command file generated has been forgotten.
Import file does not exist
Something strange here. The input command file has not been generated or it has been deleted, or is not found in the expected folder. Are there issues regarding access rights to your work folder?
Data store unset
The data store variable is unset or the SITE you have intended to store the imported data in is invalid. Has it been deleted since you set the store variable?

File does not exist
Input file name not
specified
Import file does not exist
Data store unset


The Import, Comparison and Merge process involves three stages. First, the model is imported. You then has the option of comparing the imported model with the original model, after which they may merge the new data into the old model, or the comparison and merge process can be performed as one with no user interaction. Although you can tell the system to Import, Compare and Merge the model straight away this should only be performed if you are sure of the end result. It is advised that you compare the models first and then inspect the results before merging.
You can decide to keep the imported reference model as has been described above - but is warned that this is only to be regarded as transitory information. It may also not be a complete representation of the data imported as some of it will get transferred to the real design area.
If the target area is empty, the Compare/Merge processes are bypassed which can be a lot faster when importing large amounts of data.


There are three conditions the interface looks for:
The fact that an item is in the imported file and not in the original model is indicative of one of two cases: that the item has indeed been added by AVEVA Bocad Steel; or that the item was never exported in the first place for some reason. This latter case might also occur if the original model has had items added to it since the export happened. Further, items may appear to have been deleted and their "clones" imported when the import store location is not the same as it was for the export process.
Below is a diagram illustrating the route through which the data is imported, compared and merged. New items are green, changed items are orange and deleted items are red.

It is clear from the above diagram that the interface supports partial model transfer as it just identifies those new or changed items. Anything indicated as deleted is more an indication that the item is not present in the Imported file. It is not deleted from the Original Model during the Merge process: "Deleted" items are simply moved to another SITE to enable you to recover them if necessary. So parts of models can be merged into the original model with no loss of data.
The Comparison process allows any potential changes, additions and deletions to the original model to be detected and shown in a 3D Volume View window, if there is one present and if the items are in the current Drawlist.
As for both Linear Members and Plates you can select which attributes are significant for Comparison. This is performed using the Comparison Checklist window which is a child of the Import Run Information window. By default, all the attributes transferred through the file are compared.
items in the imported file that are not in the original model - Added items;
items in the original model that are not in the imported file - Deleted items;
items that it can match between the imported file and the original model and checks for modifications - Changed items.
items in the imported file that are not in the original model - Added items;
items in the imported file that are not in the original model - Added items;
items in the original model that are not in the imported file - Deleted items;
items in the original model that are not in the imported file - Deleted items;
items that it can match between the imported file and the original model and checks for modifications - Changed items.
items that it can match between the imported file and the original model and checks for modifications - Changed items.
Note:
The Reference Model which is created is named according to your session, so that several user Reference Models could coexist at the same time. As they are named according to session, you are advised to take care to manage them and not to leave too many versions around to fill up your disk space.

Added
Deleted
Changed
Note:
Import Run Information


The following data attributes are compared between the original model and the reference model:
Importing a Linear Member also sets the Import date and time UDAs. On merging members the revision number, transfer number and code are updated.
The log file messages recording any differences are of two formats: in Brief mode the results are presented on one line; in Verbose mode you are told what the old value was and the new value is so that they can see how the model has been changed. Refer to Brief Format for further information about the brief log file format.
You may get a lot of apparent changes which may be caused by the failure to map the profile types between systems. The log file will indicate which profiles have not been mapped. It is advised that you resolve the Profile Mapping issues first before becoming too concerned with other changes recorded in the log file.
During the Import phase, an attempt is made to map the Cardinal Points in the incoming model with existing Plines that have been mapped onto them.
Start and end of Pline defined by Cardinal Point
Orientation and Beta angle
Specification Reference
Material grade and reference
Start and end of Pline defined by Cardinal Point
Start and end of Pline defined by Cardinal Point
Orientation and Beta angle
Orientation and Beta angle
Specification Reference
Specification Reference
Material grade and reference
Material grade and reference

Brief Format
Brief Format


The following data attributes are compared between the original model and the reference model:
Vertex positions are compared to within the user definable tolerance as described in the section on user customization of the interface.
Importing a Plate also sets the Import date and time UDAs. On merging members the revision number, transfer number and code are updated.
The log file messages recording any differences are of two formats: in Brief mode the results are presented on one line; in Verbose mode you are told what the old value was and the new value is so that they can see how the model has been changed. Refer to Brief Format for further information about the brief log file format.
We now compare plates with holes as secondary loops (PLOO) or NXTR primitives. We can now merge the imported model including new holes created outside of. However, because of the complexity of the comparison process, it is difficult to compare holes between the original and imported model. Where possible all other negative primitives representing holes in the original model are maintained. Therefore the comparison does not go down to the level of holes.
Position, orientation
Material grade and reference
Panel loop height and justification
Number of vertices
Position, orientation
Position, orientation
Material grade and reference
Material grade and reference
Panel loop height and justification
Panel loop height and justification
Number of vertices
Number of vertices
Note:
In Exporting a Plate, it has to be converted to the standard of being defined in a clockwise direction relative to the plane normal. Thus Importing a Plate previously defined in the base product you may find the order of vertices to have been reversed. This is because the base product is more tolerant about the ways in which you can define a plate.

Brief Format
Brief Format
Note:


Refer to diagram in Comparison and Merging Processes illustrating the route by which information is transferred from the Import, through the Comparison and on to the Merging processes.
The interface manages the Comparison and Merging of imported models so that other important engineering data is not lost or overwritten. However, other data, including connectivity may be lost.
You can separate the Comparison and Merging processes, so that they are able to view the log file in between operations. If you choose the Merge from File option on the main Import window, the Comparison process is deemed to have been completed and so all that remains to be done is the actual Merging. This is why the reference model for the current session must still be available, you will be prompted for confirmation.

If, during the Merge phase, items are to be merged, the lists of added and deleted items are reconciled with the original model - by being deleted or transferred from reference model. The storage SITE header details are then merged with the information in the header.
After the main model Merging has been completed, if you have chosen the Sort on Material Type option on the Import window, any new items will be sorted into FRMW groups according to their material type as specified by the :FABMGRADE attribute.
The version numbering system is described below, in Technical Information.

Comparison and Merging Processes
Technical Information
Comparison and Merging Processes
Import
Import
Technical Information