Structural Design
User Guide
SDNF Export/Import : Import from SDNF
Click Source Information to display the Import Source Information window which contains information about the 3D steel detailing package which the SDNF file is being transferred from.
The interface requires at least two external mapping tables for each Source Package to check that the design can accept the data. It also may use the Profile Orientation and/or the Unicode mapping table if necessary. The mapping tables are for the Steel Profiles, Materials, Unicode text string and for mapping the Profile orientations between the Neutral File and Model. The file arrangement on the system and required format is explained. Refer to Customise SDNF for further information. The interface also needs to know where the external mapping files are located on the computer network. For this internal mapping tables are required. The configuration and location of files is explained. Refer to Internal Mapping Files for further information.
The current file settings are indicated on this window. Changing the Source Package using the Source Package drop-down list on the right hand side of the window may cause the text to change giving the full path names of the respective files.
|
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 the Source Package by checking only the identification line at the top of each mapping table. The format of the mapping files is explained.Refer to Internal Mapping Files for further information.
The two main options are Auto and Manual which are activated by selecting the appropriate option button on the left hand side of the window.
The Auto option causes the interface to select automatically the mapping tables for the Source Package indicated by the Source Package drop-down list on the right hand side of the window, according to the system configuration files. When you execute the Import process, the Auto flag causes the correct mapping files to be used based on the Issue field in the Input file header. Details about the Input file header are available. Refer to Technical Information for further information.
The Manual option activates other option buttons, which are initially greyed out for the Auto option. Selecting this option changes the display of the window. For example
You can select the file type using the Profiles/Materials/Orient'n or Unicode radio buttons and input 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 AVEVA E3D™ format, for example, %ENVVAR% being the AVEVA E3D™ representation of the ENVVAR environment variable.
Press Enter, the interface checks for existence of the file and compatibility with the Source Package indicated by the Package drop-down list.
You can choose by hand which mapping file to use by either inputting its name in the text data entry field, or by using the Browse option to display a File Browser. Use this browser to search for the relevant mapping file.
Once all the correct data has been input on the Source Information window, click OK and the interface variables are updated. Click Cancel to close the window, leaving the original interface variables unchanged.
Click Import Information to display the Import Information window which contains information about the import process.
Either type the full folder path name of the input file, or click Browse to display a File Browser. The interface checks that the file exists and if it does not you are warned. As well as testing for the existence of the file, it is also tested for being a valid SDNF file by inspection of its header details.
In addition to the basic check for the input file being in SDNF format, the initial comments are scanned for the presence of a data table, which may list the Packets to follow and the number of items to be transferred in each one. If this table is present, it is analysed and the check boxes determining which Packets may be Imported are selected or deselected accordingly. Refer to Technical Information for further information.
On inputting the name of the file, if it is from a recognised SDNF Source Package and if Auto mode is set on the Source Information window, the Profile and Material mapping files are selected automatically and indicated in the Source Information window, if it currently displays, along with the updated Source Package drop-down list.
To view the SDNF Header (Packet 00) of the chosen input file, click Inspect to display the Input File Header Details window with which you can determine whether the file is the correct one to Import.
Using the check boxes on the Import Information window, if they are active, you can select whether to import Packet 10 (Linear Members), Packet 60 (Curved Members) and/or Packet 20 (Plates) or Packet 22 (Holes).
Once all the correct data has been input on the Import Information window, click OK and the interface variables are updated. Click Cancel to close the window, leaving the original interface variables unchanged.
Auto-detection of SDNF Formats
You can set up the default SDNF format version in the SDNFUserData.pmlfnc file, the default version of which can be found in the SDNF\dflts\user\SDNFPML\functions folder in the user data folder. The !!SDNFSDNFVersion variable must be precisely one of the two suggested text strings.
Click Run Information to display the Import Run Information window which allows you to view the Log File after the import process is complete, select the Log File? check box.
As part of the Import process a reference model is constructed against which comparisons are made. Save Reference Model allows you to keep this. Otherwise it is 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. Select the Sort on Material Type check box.
During the Import process, comparisons are made for Linear and Curved Members and Plates between the existing model data and the imported model data. The default AVEVA SDNF system configuration compares all the relevant data transferred in the SDNF file between the models. However, you can select which attributes may be ignored by the comparison process, click Edit Attribute Comparison List.
Profile Mapping? enables you to view if the incoming Linear Member Profile specifications are successfully mapped between systems. The transaction is relatively fast as the SDNF file is passed through the external program without any subsequent import or comparison in AVEVA E3D™. You are then able to view the log file produced and take appropriate action.
There is a risk in the external detailing package that entity mark numbers may be duplicated. The Duplicate Mark drop-down list enables you to check for duplicate numbers in the incoming model. There are three options: NONE, NEW and GLOBAL. NONE deactivates the drop-down list 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 mark numbers, while the GLOBAL option enables you to search all the available Design databases for duplicate numbers. 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 have been input on the Run Information window, click OK and the interface variables are updated. Click Cancel to close the window, leaving the original interface variables unchanged
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. The location 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 resides. 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.
|
Note:
|
These options may be completely overridden if you want to perform a validity check as on the Run Information window.
|
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. Refer to Comparison and Merge Processes for further information.
Compare ( + Merge ) imports the model and compares the reference model with the location chosen to be the storage area. At this point you are asked whether to merge the models. Click Yes to continue with the merge process and complete the Import.
Compare + Merge just goes through the complete Import process. For example, the import, comparison and merging are completed without any interaction. The action is only to be performed if you are absolutely sure that the outcome is correct.
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 the external detailing package. The option is very quick and there are no system checks.
The Control item on the Import window has just one option, Exit, which removes all forms and menus and global variables associated with the interface.
Import executes the Import process. As it proceeds you are kept informed of the progress.
The Control item on the Import window has four options: Re-initialise, Configure, Mapping Convertor and Exit. If you change any mapping files or any other variables:
Re-initialise reloads these 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, refer to AVEVA ABSI/SDNF Mapping File Converter for further information.
Exit command removes all forms and menus and global variables associated with the interface.
The General item has one option, Highlight which displays the Highlighter window enabling you to identify new, changed and deleted items in the model.
Click OK to check the fields in the window for validity:
Click Yes and the interface waits for another period of time. Click No to stop the interface where it is. Finally the system indicates its completion, whether successful or not. The completion message should be read in conjunction with the log file, if any errors are indicated.
At this point, if you have chosen to be asked whether to Merge after the Compare operation, a Confirm window displays.
Click Yes to continue with the Merge process.
Click No and the Import process skips the Merge process, you are then given a chance to store the Merging commands in a file for use later only in the current AVEVA E3D™ session. You cannot use a file from a previous SDNF session as the Import data may be incorrect.
You can save the Merge command file and then be prompted whether to view the Import log file. The Merge command file may then be used in the Merge from File option on the AVEVA SDNF - Import window. The latter option needs the reference model from this run to be kept. Therefore, some other options become unavailable.
If you have merged the models, you are then asked if you want to keep the reference model, verifying the option selected on the Run Information window.
Finally, you are then asked whether to view the log file, if you have chosen that option on the Run Information window.
If you want to inspect the log file, you can save it with the File > Save as option in the SDNF File Viewer window which displays a File Browser, or click Save as to the suggested filename. If the file exists, you are asked if you want to overwrite it. The log file window can then be closed, click Cancel.
If you have chosen Brief mode on the Run Information window for displaying the log file, the window displaying the log file filters out all warning messages, leaving only the error messages. To save the log file, however, all messages are be retained in the file.
There are three conditions the AVEVA SDNF 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 the external steel detailing package; or that the item was never exported in the first place for some reason. The 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.
As for both Linear Members and Plates you can select which attributes are significant for Comparison. The Comparison Checklist window which is a child of the Import Run Information window allows for this. By default, all the attributes transferred through the SDNF file are compared.
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 you can view how the model has been changed. Details about the brief log file format are available. Refer to Brief Format for further information.
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 you can view how the model has been changed. Details about the brief log file format are available. Refer to Brief Format for further information.
Refer to Comparison and Merge Processes for further information. The diagram illustrates the route by which information is transferred from the Import, through the Comparison and on to the Merging processes.
The AVEVA SDNF 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 you are able to view the log file in between operations. If you choose the Merge from File option on the main SDNF Import window, the Comparison process is deemed to have been completed and all that remains to be done is the actual Merging. The reference model for the current session must still be available. You are prompted for confirmation.
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 are sorted into FRMW groups according to their material type as specified by the :SDNFMGRADE attribute.
The version numbering system is described. Refer to Technical Information for further information.
For example, a new STRU may be created with the name of /SDNF-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:
For example, a new STRU may be created with the name of /SDNF-OLD-DEMO-SYSTEM/A.1 under the special SITE /SDNF-OLD-DEMO-SYSTEM. The components of this name are:
As has been described in Comparison and Merge Processes there are two validation checks that can be performed prior to the full import and merging of models.
The first option is for profile mapping. The Profile Mapping? check box on the Run Information window turns this on. The Import process initialises normally and calls the external program to process the incoming SDNF file. In so doing it checks for a complete mapping of the profiles in the mapping tables. A log file is produced. No further Import actions are undertaken with this option.
The options for this check are NEW and GLOBAL. NONE turns the facility off. NEW checks among all this run's imported members contained in the reference model for duplicate mark numbers, while GLOBAL checks the whole structural database, both imported and existing elements. These can be quite slow options as the reference model must be created and compared anyway.
Refer to Sample Validity Check Log File for further information.
From either the Import or Export windows, select General > Highlight from the top of the window to display the Highlighter window. The window allows you to identify in a graphical window whatever you want, either according to Import date, or by Transfer/Revision number combinations. The By option button switches the window into the appropriate mode. Both options work from the start element selected and indicate only those items that are in the drawlist.
The Selected items box part of the window allows you to select any combination of Added, Changed, or Deleted Items for identification, according to the date range.
By selecting the inclusive dates defining the limits of the range using the From and To date drop-down lists you can locate on the screen those items in the current drawlist which have been changed, added or deleted.
The rules of selecting the changed, deleted or added items are the same as Highlighting by Import Date. Refer to Highlight by Import Date for further information.
By selecting the versions defining the limits of the range using the From and To version drop-down lists you can identify on the screen those items in the current drawlist which have been changed, added or deleted.
The test can be performed after installing the AVEVA SDNF product to make sure that the installation is complete and correct. The test must follow immediately the Export test described. Refer to Testing AVEVA SDNF Export for further information. All the required testing material can be found below the sub-folder SDNF\test\results\export in the user data folder.
Take the SDNF file exported in the export test and modify it in a text editor. While referring to the description of the SDNF format. You can modify, for example, a mark number, a material and positions. Comparing the files SDNF-Test.sdn in the SDNF\test\results\export and the SDNF\test\results\import folders, which is found in the user data area, gives you some examples of edits that can be tested. Make sure that the resultant SDNF file is valid SDNF. Save the modified file under a different name, or in a different folder.
When that is finished, bring the SITE into view by adjusting the view limits. Refer to Limits for further information.
If required, modify the 3D view. Refer to Views for further information.
The Import window allows you to import a steel structure from a SDNF file.
Select the Auto option button and select AVEVA from the list of Source Packages on the Source Package drop-down list on the right hand side of the window. The system automatically detects the Source Package's Profile mapping table and Material mapping table.
Select the Save Reference Model? check box in order to safe any reference model.
Finally, you need to sort any new members added to the model by material type. Select the Sort on Material type? check box.
A validity check on the incoming data, prior to importing it, can be performed. Refer to Perform a Validity Check for further information.
Select the SITE into which the SDNF file is to be imported. Select SITE /TEST-SDNF-INTERFACE in the Members list and click CE by Store in:.
A two stage import is then performed. Comparing the models first before Merging. So, select the Compare (+ Merge) option button.
After the first stage of Import has taken place, you are asked by a Prompt window with the message. SDNF Interface (Confirm) - Model comparison completed. OK to merge models?. Click Yes to continue with the Merge process.
When the process is complete a Confirm window is displayed.
You are then asked if you want to inspect the log file. If you do, you can save it with the File > Save as option in the SDNF File Viewer window to display a File Browser, or click Save as to the suggested filename. The log file window can be closed by the Cancel.
You can then Export the merged model to a file SDNF-Test-Mrg.sdn and compare the new SDNF file with the one provided in the test/results/import folder.
If you want to perform a validity check on the incoming data before it is imported, display the Run Information window from the main Import window. Select GLOBAL for the Duplicate Mark Number search criterion. Click OK and fill in all the details on the main Import window.
Once all the details are correct on the Import window, click OK. The validation process is performed and in due course you are prompted to view the log file. Save the log file as SDNF-Test-Vfy.log and compare it with the results supplied in the test/results/import folder.
