Disclaimer
1.1 AVEVA does not warrant that the use of the AVEVA software will be uninterrupted, error-free or free from viruses.
1.2 AVEVA shall not be liable for: loss of profits; loss of business; depletion of goodwill and/or similar losses; loss of anticipated savings; loss of goods; loss of contract; loss of use; loss or corruption of data or information; any special, indirect, consequential or pure economic loss, costs, damages, charges or expenses which may be suffered by the user, including any loss suffered by the user resulting from the inaccuracy or invalidity of any data created by the AVEVA software, irrespective of whether such losses are suffered directly or indirectly, or arise in contract, tort (including negligence) or otherwise.
1.3 AVEVA's total liability in contract, tort (including negligence), or otherwise, arising in connection with the performance of the AVEVA software shall be limited to 100% of the licence fees paid in the year in which the user's claim is brought.
1.4 Clauses 1.1 to 1.3 shall apply to the fullest extent permissible at law.
1.5 In the event of any conflict between the above clauses and the analogous clauses in the software licence under which the AVEVA software was purchased, the clauses in the software licence shall take precedence.
Copyright
Copyright and all other intellectual property rights in this manual and the associated software, and every part of it (including source code, object code, any data contained in it, the manual and any other documentation supplied with it) belongs to, or is validly licensed by, AVEVA Solutions Limited or its subsidiaries.
All rights are reserved to AVEVA Solutions Limited and its subsidiaries. The information contained in this document is commercially sensitive, and shall not be copied, reproduced, stored in a retrieval system, or transmitted without the prior written permission of AVEVA Solutions Limited. Where such permission is granted, it expressly requires that this copyright notice, and the above disclaimer, is prominently displayed at the beginning of every copy that is made.
The manual and associated documentation may not be adapted, reproduced, or copied, in any material or electronic form, without the prior written permission of AVEVA Solutions Limited. The user may not reverse engineer, decompile, copy, or adapt the software. Neither the whole, nor part of the software described in this publication may be incorporated into any third-party software, product, machine, or system without the prior written permission of AVEVA Solutions Limited, save as permitted by law. Any such unauthorised action is strictly prohibited, and may give rise to civil liabilities and criminal prosecution.
The AVEVA software described in this guide is to be installed and operated strictly in accordance with the terms and conditions of the respective software licences, and in accordance with the relevant User Documentation. Unauthorised or unlicensed use of the software is strictly prohibited.
© Copyright 1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved. AVEVA shall not be liable for any breach or infringement of a third party's intellectual property rights where such breach results from a user's modification of the AVEVA software or associated documentation.
AVEVA Solutions Limited, High Cross, Madingley Road, Cambridge, CB3 0HB, United Kingdom
Trademark
AVEVA and Tribon are registered trademarks of AVEVA Solutions Limited or its subsidiaries. Unauthorised use of the AVEVA or Tribon trademarks is strictly forbidden.
AVEVA product/software names are trademarks or registered trademarks of AVEVA Solutions Limited or its subsidiaries, registered in the UK, Europe and other countries (worldwide).
The copyright, trademark rights, or other intellectual property rights in any other product or software, its name or logo belongs to its respective owner.
Revision Sheet
Date Version Comments / Remarks
May 2013 2.0 Design Parameters modifications June 2013 2.1 Model Limits Offsets modifications Sept 2013 2.2 Profile mapping Files modifications
AVEVA Bocad Steel Interface
Contents
Page
AVEVA Bocad Steel Interface
Introduction . . . 1:1
Assumptions . . . 1:1
Guide Structure . . . 1:1
Installation of the ABSI Product . . . 2:1
Version Specific Installation Issues . . . 2:1
Installation with AVEVA E3D™1.1 . . . 2:2
Export/Import. . . 3:1
Export to AVEVA Bocad Steel . . . 3:1
Import from AVEVA Bocad Steel . . . 3:20
Technical Information . . . 3:40
Transfer of Curved Members . . . 3:46
Stairs, Ladders and Handrailing . . . 3:48
Import Log Files . . . 3:49
Sample Validity Check Log File . . . 3:51
Environment . . . 3:52
Upgrading a Project . . . 3:55
Customise . . . 3:67
Supplementary Information . . . .A:1
Modification Dates and Times and the Base Product . . . A:1
First Time Export to AVEVA Bocad Steel . . . A:2
Import from AVEVA Bocad Steel . . . A:2
Subsequent Export to AVEVA Bocad Steel . . . A:2
Removal of History Data . . . A:3
Design Parameter Sized Profiles . . . A:3
Managing the Model Limits and Offsets . . . A:8
Initialisation of the ABSI Application . . . A:11
Catalogue Versions . . . A:11
Application Tools . . . A:11
User Customisation . . . A:18
1
Introduction
AVEVA Bocad Steel Interface allows the user 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 Plant 12 Series • AVEVA Outfitting 12 Series • AVEVA Everything3D™
henceforth known as the base product.
1.1
Assumptions
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.
1.2
Guide Structure
The AVEVA Bocad Steel Interface Reference Manual is divided into the following sections:
Introduction introduces this guide and summarises its scope.
Installation of the ABSI Product
how to install the product.
Export/Import gives a general overview of the facilities provided within the application.
Supplementary Information
2
Installation of the ABSI Product
The user will be able to install the ABSI product for the base product, so that the same product files will work with any target version. On installation a file Bocad_vars.bat is automatically produced that stores the folders where the product is installed. If required to have several versions of the application on a single machine, this file can be modified to access the correct version.
rem ---rem Add AVEVA Bocad Steel Interface variables
rem ---set BOCMAIN=C:\Program Files (x86)\AVEVA\Plant\ABSI2.2.0\
set BOCDATA=C:\Users\Public\Documents\AVEVA\Plant\ABSI2.2.0\
The installer allows the user to select where the main product (BOCMAIN) and the user modifiable parts (BOCDATA) are to be located. Once installed, the user will have to modify the main batch files for starting the base product. For the base product the file to modify is evars.bat or custom_evars.bat in the main executable folder. The same manual change is required in each file.
Add to the bottom of the file the following…
rem ---rem Add AVEVA Bocad Steel Interface variables
rem ---set BOCAD_INSTALLED_DIR=C:\Program Files (x86)\AVEVA\Plant\ABSI2.2.0 if exist "%BOCAD_INSTALLED_DIR%\Bocad.bat" call "%BOCAD_INSTALLED_DIR%\Boc ad.bat"
where the BOCAD_INSTALLED_DIR is the correct installation folder for your situation. For AVEVA PDMS12.0 SP6, AVEVA PDMS12.1 series and AVEVA Marine 12.1 the user must also copy the file called ‘bocad’ from BOCAD\bocad\addins to the addins folder in the UI area for the installed PDMS version, for example: C:\AVEVA\Plant\PDMS12.1SP2\PDMSUI\des\addins.
2.1
Version Specific Installation Issues
The PML index files in user accessible areas can be rebuilt easily. The problem is for the application core PML file index. If, for any reason, the user needs to regenerate the index, there are two files that might not get indexed by the PML REHASH ALL command in the AVEVA E3D™. This is most likely to happen with the base product. Following a PML
If they are not in the index file, they should be put in by hand so that E3D can use them.
2.2
Installation with AVEVA E3D™1.1
AVEVA E3D™1.1 was distributed with the option of installing the previous version of ABSI, ABSI1.1. Although there should not be an interference problem, once the old ABSI1.1 has been removed, the user is advised to remove the equivalent lines from the end of the evars.bat and evars.init files to ensure that the correct environment variables are initialised. For example: remove the following lines:
rem ---rem Add AVEVA Bocad Steel Interface variables
rem ---set BOCMAIN=%AVEVA_DESIGN_INSTALLED_DIR%
if exist "%BOCMAIN%Bocad_env.bat" call "%BOCMAIN%Bocad_env.bat" If problems persist, remove the old Bocad application by hand from the following locations (as PML files may be defined several times):
Once all traces of ABSI from AVEVA E3D™1.1.0 have been removed, the user must regenerate the pml.index for AVEVA E3D™. Unfortunately, as this is embedded in a folder that the user cannot change by normal methods, it has to be done by an administrator. A PML REHASH ALL will not work. The administrator must copy the original pml.index file to the desk top, then edit it by hand to remove all the references to Bocad folders and files. The file must then be copied back into place as an Administrator to override the security settings. Enter AVEVA E3D™, the ABSI options on the main tabs will not be displayed, proceed with the installation of this release.
C:\Program Files (x86)\AVEVA\Plant\E3D1.1.0\PMLLIB (bocad sub folder)
C:\Program Files (x86)\AVEVA\Plant\E3D1.1.0 (bocad_env.bat, possibly the bocad exe folder)
C:\Users\Public\Documents\AVEVA\Plant\E3D\Data1.1.0\... (bocad user data) The bocad addin
3
Export/Import
AVEVA Bocad Steel Interface is an application which allows the user to export and import files using the AVEVA Bocad Steel Interface (ABS) format.
3.1
Export to AVEVA Bocad Steel
AVEVA Plant and Outfitting 12 Series
To export a steel structure to an AVEVA Bocad Steel Interface file, select Utilities > AVEVA
Bocad Steel Interface > Export to AVEVA Bocad-3D to display the Export window.
A Warning message may be displayed stating mapping files are not found. This is because local versions have not been set up. Use the default set provided with the product.
AVEVA Everything3D™
To export a steel structure to an ABS file, on the Sections, Plates or Stairs Ladders
Mapping Files
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 main 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 Customise tells the user 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 the user’s 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.
The user may have a generic set of mapping tables to map between the base product and AVEVA Bocad Steel. Or the user may have a set for a particular steel fabricator.
The current file settings are indicated on this Export Target Information 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 details 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 buttons, which are initially greyed out for the System option.
The user 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. The user 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.
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.
The user can either choose by hand which mapping file to use by entering its name in the text data entry field, or by using the Browse option to bring up a File Browser. The user may use this browser to search for the relevant mapping file.
Once the user has 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
Error and Log File Messages
Export Information
Click Export Information to display the Export Information window which contains information about the export process.
The user can either type the full folder 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, the user will be asked whether to overwrite it. If the file does exist and the user wants 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 the user can perform repeat Exports without changing the output file name.
Note: If the user does not enter the full path name and just a plain file name, the output file 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 for AVEVA Bocad Steel, or it does not exist.
Not a suitable Mapping Table File
Incorrect format of file, or empty file, or wrong target for example not AVEVA Bocad Steel.
Bad Map File Mapping file is not correct format. Possibly it is from another operating system.
Error on File Browser window
base product format, for example: %ENVVAR% being the base product representation of the ENVVAR environment variable.
The ABS file may have several sections: a header, a set of Linear Members, and a set of Plates and their holes. The header is compulsory: any other section is optional.
The user 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 zones are stored in the Application Data area. On export and import one can associate the project header details with the transfer file. This can include the model offset and orientation applied to the model.
Different transfers can use different headers. The user can select the correct one, or create a new one in from the Project Header drop down list. It is up to the user to ensure that the correct header is used.
The user can view the information contained by the chosen header element by clicking
Inspect which displays the Export File Header Details window.
At first the entry fields are inactive so the user 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 the user 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, the user can define a model offset and rotation for ease of use in Bocad. Using the toggles on the Export Information window, the user can select whether to export Straight or Curved members, and Plates, with the additional option of including their holes. The user is able to export Plates without their holes.
Model Offsets and Orientations
If the user has already selected something to Export, the Export Information window is updated to include the 3d world limit box of the export items.
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 the user later tries to modify these values, it must be an explicit decision. Refer to Managing the Model Limits and Offsets for more information.
Create a new header block
The user can create a new header block by selecting New header… from the Project
header drop down list.
The ABSI - Export Header window is displayed, the user 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 Z axis following the right hand screw rule. It is usually assumed that the header is locked to prevent accidental changes
Transfer User Data
This version of the interface allows the user 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, the user 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 the user can create more.
Use the toggles to turn fields on and off. The user can then enter the Source type of element in the hierarchy above the element at which this data extraction is taking place. The user 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 customisation functionality, it is up to the user 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, the user can specify an alternative default attribute, function or value. And then if required enter descriptive text. The data on the
This information is not stored in the database, but in the configuration file, which can be loaded by other projects. Refer to Customise in Chapter Export/Import for more information. The interface checks that the user is 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.
Error and Log File Messages
Run Information
Click Run Information to display the Export window which allows the user to view the Log File after the export process is complete by clicking to select the Log File? check box.
Export file already exists File exists, the user will get the option to overwrite it.
Wrong place in database The user is most likely at the WORLD element in the database.
Illegal Transfer letter The user can only use transfer letters between A and Z.
Nothing to export The user has deselected both the Linear Members and Plates options.
Cannot decrement Transfer letter
The user can not decrease the Transfer letter, only increment it.
Click the Brief or Verbose radio buttons, the user can choose which format messages are displayed.
The Test Run? option allows the user to suppress the updating of all the Export flags. This is so that the user can see if there will be a successful Export of the model. The user 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, the user 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 the user is 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.
Members and Export List
The Members pane allows the user to navigate around the database hierarchy.
The user must enter the elements to be exported, Linear Profile or Planar members. The interface will locate all SCTNs, GENSECs and PANEs contained in, or implied by, the Export list. If the user adds 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.
Note: Partial model transfers are supported by the interface, however, the user must be
aware of how the Import process handles partial model transfers. Refer to
Comparison and Merging Processes.
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 the user 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 the user into a mode where an item from the 3D Volume View can be picked. The user can also pick a sequence of items in succession to add
The user 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.
Error and Log File Messages
Click Cancel to close the Export window.
Export executes the Export process. As it proceeds the user is kept informed of the
progress by means of messages at the bottom of the main window as well as by windows and prompts.
Control
The Control drop-down menu has three options; Re-initialise, Configure and Exit. Changing any mapping files or any other variables:
• Re-initialise reloads files to save the user having to rebuild the whole user interface
from scratch.
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 the user 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 the user 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, the user 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.
Can't export the WORLD The user cannot export the WORLD
No owning Structure Cannot climb to Structure element from current location in database.
• Exit removes all forms and menus and global variables associated with the interface.
The General drop-down menu has two options, Highlight and Clear ABSI History.
Highlight displays the Highlighter window enabling the user 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.
The Export Process
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 more details on Importing and for details about saving the reference model, refer to Import from AVEVA Bocad Steel.
Prior to any Export process, all fields are checked for validity. • 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?
In addition, there is an specific UDA, :FABEXCLUDE, attached to certain base product elements by which the user 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 the user is 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, the user 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
The above indicates a successful completion, while the below represents some problem encountered in the external program.
On completion of the external program, the status file is inspected and, if the result is favourable, the user will then be asked whether or not to view the log file, 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, the user 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.
Error and Log File Messages
Exporting Linear Members
A series of checks are made before a Linear Member is output. • 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?
If any of the above criteria is not satisfied, the linear member does not even get exported to the output file.
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.
As has been indicated before, Linear Members can be transferred as either Straight or Curved. In the base product, curved members are modelled using GENSECs. However, GENSECs can be compound shapes with both straight and arc sections.
File does not exist Somehow there is no log file. Are there issues regarding access rights to the user’s work folder?
UUID numbers and transfer and revision numbers. This is only as necessary to minimise 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 the user’s work folder.
Error and Log File Messages
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.
Unrecognised 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 recognised. 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.
Exporting Plates
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.
Note: Any edge preparation details and modelling, such as grinding, will be lost in the
transfer operation.
A basic series of tests is performed before the Plate is exported. • Is there any geometry?
• Is the height valid? • Is it justified correctly? • Does it have a valid material? • Are there enough vertices?
If any of the above criteria is not satisfied, the plate does not get exported in the output file.
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.
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.
Note: Importing a Plate previously defined in base product, the user may find the order of
vertices to have been reversed.
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
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.
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.
Circular Plates
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 recognises only 4 or 5 point circles, where the 5th point is a duplicate of the first point.
Error and Log File Messages
Transferring Holes
There is a limitation as to which holes are exported. Only secondary PLOO boundaries and NXTR elements can be handled. PLOOs are full depth penetrations: partial penetrations can be modelled using NXTR elements. Circular boundaries of holes and indentations can
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.
Unrecognised 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.
On import vertices in boundaries are given a DESP value according to the list below.
Using these values specific shapes, such as circles, ellipses, etc., can be detected.
A message is output when the export process ignores 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 some 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. The following negatives are not exported:
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.
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.
PVTLastPoint
0
PVTStraight
1
PVTArc
2
PVTFillet
3
PVTCircle
4
NBOX NPOLYH NCYL NSLC NSno
NDIS NCON NPYR NCTO NRTO
3.2
Import from AVEVA Bocad Steel
AVEVA Plant and Outfitting 12 Series
To import a steel structure from an AVEVA Bocad Steel Interface file, select Utilities >
AVEVA Bocad Steel Interface > Import from AVEVA Bocad-3D to display the Import
window.
AVEVA Everything3D™
To import a steel structure from an AVEVA Bocad Steel Interface file, on the SECTIONS,
PLATES or STAIRS LADDERS HANDRAILS tab, in the AVEVA Bocad Steel group, click Import to display the Import window.
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.
Mapping Files
Click Mapping files to display the 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 Customise explains how the user 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 the user’s computer network. For this internal mapping tables are required. Refer to Customise which explains how the user can configure the interface to let it know where all the files are located.
The user can have a generic set of mapping tables to map between the base product and AVEVA Bocad Steel. Or the user can have a set for a particular steel fabricator.
The current file settings are indicated on this window.
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.
The system also checks that these files are compatible with AVEVA Bocad Steel by checking the identification line at the top of each mapping table. Refer to Internal Mapping Files for details 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 the user comes 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.
The user 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. The user 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.
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.
The user can either choose by hand which mapping file to use by 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.
Error and Log File Messages
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
Import Information
From the Import window, click Import Information to display the Import Information window which is populated with information about the import process.
The user 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 the user 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.
Note: If the user does not enter the full path name, the input file is assumed to be in the
folder from which started the base product. The user 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.
On entering the name of the file, if Auto mode is set on the Import Information window, the Profile and Material mapping files are selected automatically and indicated in the Import
Information window.
On reading the file header information the interface will attempt to select a suitable header. If one does not exist the user will be asked whether to create one for the import. If the user wants to override the recommended header element, it will be checked for compatibility. The user can view the header information of the chosen input file, click Inspect, to display the Input File Header Details from window with which the user can determine whether the file is the correct one to Import.
From the Attributes page, the user 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
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.
Error and Log File Messages
Import User Data
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, the user 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 the user 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, the user can use the data.
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 the user is inspecting has been transferred across hardware platforms.
Run Information
From the Import window, click Run Information to display the Import Run Information window. The window is allows the user 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 the user can choose which format messages are displayed.
As part of the Import process a reference model is constructed against which comparisons will be made. Save Reference Model allows the user to keep this. Otherwise it will be deleted on completion of the Import process.
Note: This reference model will be deleted next time the user 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.
After the Import merging process has been performed, the user 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 entries transferred in the file between the models. However, the user can select which attributes may be ignored by the comparison process by clicking
Use this window to deselect attributes for comparison but be aware that strange results may occur especially if the user ignores positional and rotational attributes.
Finally, there are two validity checks the user 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 the user will be able to see a log file before any data is merged whatsoever.
Profile Mapping? enables the user 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. The user 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 the user 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 the user to check only the new imported items for duplicate UUIDs, while the
GLOBAL option enables the user 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
Members and Operations
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, the user can control how the Import process is to proceed.
Note: These options may be completely overridden if the user wants to perform a validity
check as on the Run Information window.
The user 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.
This is a very quick option and there are no checks, except what the user wants to do it.
Error and Log File Messages
Import and Cancel
Cancel closes the Import window.
Import executes the Import process. As it proceeds the user is kept informed of the
progress.
Import Bar Menu
The Control drop-down menu has three options; Re-initialise, Configure and Exit. Changing any mapping files or any other variables:
Compare + Merge Goes through the complete Import process - that is the import, comparison and merging are all completed without any interaction with the user. This is only to be performed if the user is 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 the user 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, the user may lose any elements added to the model by AVEVA Bocad Steel.
Bad element type The user is not trying to store imported data at a SITE, ZONE or STRU element.
• Configure enables the user to define run parameters, model parameters, display
colours and environment parameters. Refer to System Configuration for further information.
• Exit removes all forms and menus and global variables associated with the interface.
The General drop-down menu has two options, Highlight and Clear ABSI History.
Highlight displays the Highlighter window enabling the user 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.
Import Process
After clicking OK the fields in the window are checked for validity: • 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?
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 the user is 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 exist, the user will be asked if they 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.
The user 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 the user before will have been deleted beforehand.
The status line will inform the user of the progress on importing the data.
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 the user has chosen to be asked whether to Merge after the Compare operation, Confirm window is displayed.
Click Yes the interface continues with the Merge process.
Click No and the Import process skips the Merging, but the user is then given a chance to store the Merging commands in a file for use later on only in the current base product
session. The user cannot use a file from a previous session as the Import data may be
incorrect.
The user 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, the user does not have the option below.
If the user has 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, the user is asked whether to view the log file, if they have chosen that option on the
Run Information window.
If the user wants 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, the user will be asked whether they want to overwrite it. The log file window can then be closed by clicking Cancel.
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 the user there to perform any queries or operations.
Error and Log File Messages
Comparison and Merging Processes
The Import, Comparison and Merge process involves three stages. First, the model is imported. The user 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 the user can tell the system to Import, Compare and Merge the model straight away this should only be performed if the user is sure of the end result. It is advised that the user Compares the models first and then inspect the results before Merging.
The user 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.
The Comparison Process
There are three conditions the interface looks for:
• 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.
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.
File does not exist Somehow there is no log file Are there issues regarding access rights to the user’s 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 the user’s work folder?
Data store unset The data store variable is unset or the SITE the user had intended to store the imported data in is invalid. Has it been deleted since the user set the store variable?
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 the user to recover them if necessary. So parts of models can be merged into the original model with no loss of data.
Note: The Reference Model which is created is named according to the user session, so
that several user Reference Models could coexist at the same time. As they are named according to session, the user is advised to take care to manage them and not to leave too many versions around to fill up the users disk space.
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 the user 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.
Comparing Linear Members
The following data attributes are compared between the original model and the reference model:
• Start and end of Pline defined by Cardinal Point • Orientation and Beta angle
The log file messages recording any differences are of two formats: in Brief mode the results are presented on one line; in Verbose mode the user is 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 details about the brief log file format.
The user 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 the user resolves 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 (SNFA to SNFN) in the incoming model with existing Plines that have been mapped onto them.
Comparing Plates (PANE)
The following data attributes are compared between the original model and the reference model:
• Position, orientation
• Material grade and reference • Hold and Paint Spec UDAs • Panel loop height and justification • Number of vertices
Vertex positions compared to within the user definable tolerance as described in the section on user customisation 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 the user is 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 details about the brief log file format.
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 the user may find the order of vertices to have been reversed. This is because the base product is more tolerant about the ways in which the user can define a plate.
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.
The Merging Process
See the 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 user can separate the Comparison and Merging processes, so that they are able to view the log file in between operations. If the user chooses 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. The user will be prompted for confirmation.
If, during the Merge phase, items are to be merged, then 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 the user has 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.
Additional Items
Items added to the model are recorded as such; they are indicated by changing their colour, a suitable message is output to the log file and they are then transferred to a special area. Merging will transfer all the added items from the reference model to the original model. If required, they are then sorted according to material type.
The new items are gathered together into a site whose name is constructed from the Transfer and Revision Numbers so that the user can easily locate all items added at a specific version or date.
For example, a new STRU may be created with the name of /FAB-NEW-DEMO-SYSTEM/ A.1 under the container element as specified in the Store in: field on the Import window. The components of this name are as follows:
The user would thus be able to find all the added items to this MDB at this version. /FAB- the system prefix
NEW- identification of new element container <mdb name>- the current MDB, for example: /DEMO <user name>-/ the current user name, for example: SYSTEM <transfer nr>. the current Transfer letter, for example: 'A' <revision nr> the current revision number, for example: '1'
Deleted Items
Deleted items in the model are recorded as deleted during the Compare phase and remain in the reference model to be deleted later if not required. This separation of operations is so that the user can see what will be deleted during the Merge process. Before deletion the objects are changed in colour so that they may be identified.
Note: An item is not actually deleted from the original model. The apparent deletion may, in
fact, be because the item was never transferred to AVEVA Bocad Steel in the first place due to some reason. Alternatively it may have been created in the base product since the initial Export process had taken place.
'Deleted' items are disconnected from the old model and transferred from the current part of the database into a STRU created under the special 'Deleted' SITE.
As with the added items, the STRU is named out of components, thereby enabling the user to determine at which version items may have been removed from the model.
For example, a new STRU may be created with the name of /FAB-OLD-DEMO-SYSTEM/ A.1 under the special SITE /FAB-OLD-DEMO-SYSTEM. The components of this name are as follows:
The user would thus be able to find all the 'deleted' items to this MDB at this version.
Changed Items
In merging Plates the interface tries to keep the original vertices as they may have been used for locating dimensions on drawings: it may be that just the positions have been changed. However, the comparison only works in list order: the interface does not look around for another vertex in the same physical place, although it may be in a different list position. Extra unwanted vertices are deleted on merging and all new vertices are added to the end of the list. A totally new Plate is just imported directly.
Note: Changed objects are indicated as such by a change in colour.
/FAB- the system prefix
OLD- identification of new element container <mdb name>- the current MDB, for example: /DEMO <user name>-/ the current user name, for example: SYSTEM <transfer nr>. the current Transfer letter, for example: 'A' <revision nr> the current revision number, for example: '1'
