Product(s): AECOsim Building Designer Version(s): CONNECT Edition (10.0.0.154) Environment: N/A Area: Workspace Subarea: Configuration Steps : Run 'Configuration Migration' Edit WorkSet.cfg and apply CONNECT configuration changes Apply CONNECT WorkSet folder changes Associate an active WorkSet to multiple files Using 'Batch Process' Datasets 1. Run 'Configuration Migration' The first step in the manual migration process is still to run the 'Configuration Migration'wizard to create a working WorkSet Configuration File (.cfg) and corresponding DGN WorkSet file (.dgnws). Please see How to Migrate V8i Project(.pcf) to CONNECT WorkSet(.cfg) . 2. Edit WorkSet.cfg and apply CONNECT configuration changes: In the CONNECT Edition, several configuration variable have been deprecated or superseded. While there is no negative impacts for leaving these orphaned configuration in your WorkSet.cfg, you may want to reference CONNECT Edition 'Deprecated and/or Superseded' Configuration Variables for a complete list of configuration variable if you intend to completely sanitize your configuration files for the CONNECT Edition. 1. Locate your V8i Project Configuration File (.pcf), open the file in a text editor such as Notepad or Notepad++ and copy all the contents within that file 2. Locate your new WorkSet Configuration file (.cfg), open the file in a text editor. With the exception of the line defining the _USTN_WORKSETROOT you will replace the entire contents of the WorkSet configuration file with the information copied from the V8i Project Configuration File (.pcf). e.g. Keep the following line from within the new WorkSet Configuration file (.cfg), this will identify the location of the project. _USTN_WORKSETROOT = C:\PROGRAMDATA\BENTLEY\AECOSIMBUILDINGDESIGNER V8I SS6\WORKSPACE\projects\BuildingExamples\BuildingTemplate_US\ Find & Replace (in the following order): Find and Replace the following values (do not match case as part of the find criteria). Find _USTN_PROJECTDATA Replace with _USTN_WORKSETROOT (8) Find PROJ_DATASET Replace with _USTN_WORKSETSTANDARDS (50) Find IFC_PROJECT Replace with IFC_WORKSET (10) Find BB_LEVEL_DGNLIBLIST Replace with MS_DGNLIBLIST_LEVELS (3) Find $(PROJDIR_FRAME) Replace with $(_USTN_WORKSETSTANDARDS)Frame/ (3) *Find $(_USTN_WORKSETROOT)support/dataset/ Replace with $(_USTN_WORKSETROOT)Standards/ (1) *Find $(_USTN_WORKSETROOT)support/out/ Replace with $(_USTN_WORKSETROOT)Output/ (1) Find $(_USTN_WORKSETROOT)designs/ Replace with $(_USTN_WORKSETDGNS) (3) Find > $(_USTN_WORKSETDGNS) Replace with $(MS_DESIGNDIR) (1) **Find Project Replace with WorkSet (1) **Find WorkSetShapes Replace with ProjectShapes (1) **Find Project Replace with WorkSet * Requires restructuring of v8i project folder structure, to accommodate CONNECT folder structures, see "Apply CONNECT WorkSet folder changes" below. ** STRUCTURAL_SHAPES About Workspace _USTN_PROJECTDESCR = Building Designer US Dataset Project Template # MS_DESIGNDIR: Design Model Directory # TF_DRAWINGS: Location of Drawing Extractions (can be over-written in the Drawing Definition). TF_DRAWINGS = $(_USTN_WORKSETROOT)extractions/ # ATFDIR_CELL: Prepends or overwrites the folder locations of cell libraries ATFDIR_CELL $(TF_DRAWINGS) #====================================================================== # Project Explorer: #====================================================================== # BB_PROJECTEXPLORER_LIBRARY_DIRECTORY: Specifies the location of the Project Explorer Library Folder BB_PROJECTEXPLORER_LIBRARY_DIRECTORY = $(_USTN_WORKSETSTANDARDS)dgnlib/ # BB_PROJECTEXPLORER_LIBRARY_FILE: Specifies the dgnlib to be used by the Project Explorer Assistant for tracking file changes. BB_PROJECTEXPLORER_LIBRARY_FILE = $(BB_PROJECTEXPLORER_LIBRARY_DIRECTORY)MasterProject.dgnlib # MS_PROJECTEXPLORER_EXTENSIONS: Specifies the name of the extension library for Project Explorer MS_PROJECTEXPLORER_EXTENSIONS = buildingproject.dll _USTN_CAPABILITY > +CAPABILITY_DGNLINK_NONDGN_REGIONLINKS #====================================================================== # Drawing Extractions: #====================================================================== # TFBXS_SEEDDIR: Location of Template Drawing Extraction Definition Seed Files # TFBXS_SEEDDIR = $(TFDIR)seed/DEM_templates/ # TFBXS_SEEDFILE: Seed file for seed Drawing Extraction Definitions. Can be set to point to a *.bxs or *.dgn file # TFBXS_SEEDFILE = $(TFBXS_SEEDDIR)DEM_Templates_$(bb_discipline).dgn # TF_DRAWSEED: Specifies the seed file to be used when a new drawing extraction file is created. # TF_DRAWSEED = DrawingSeed_DEM.dgn # BB_ANNOTATE_IN3DDGN: Causes Create Space to place physical space label into 3D instead of space artifact. # Needed to work with the DEM. # BB_ANNOTATE_IN3DDGN = 1 # STFDIR_DATA : $(STF_DATASET)data/ # STFDIR_SETTINGS : $(STF_DATASET)setting/ 3. Apply CONNECT WorkSet folder changes: In the CONNECT Edition, the folder structure and configuration variables were extended to accommodate user-definable standards at multiple levels throughout the Workspace/WorkSet organized into a shared standard folder. In order to align with these folders and CONNECT configuration variables, it is necessary to redefine and restructure the Project "support" folder delivered in V8i. This consist of the following folder structure changes: 1. Rename the old "support" folder to "Standards" 2. Move the contents in the "dataset" subdirectory into the "Standards" folder and delete the now empty "dataset" subdirectory. 3. Move the "Energydata" subdirectory into the "Standards" folder 4. CONNECT Edition also add two new subdirectories to Standards, not previously available in V8i, ...\Standards\Macro and ...\Standards\Symb 5. Move the "out" subdirectory to the root of the Workset and rename to "Output" ( \Output) 6. Move the "results" folder, used by Energy Services, and reside under "Output" 7. The "extractions" folder was discontinued, with the deprecation of the Drawing Extraction Manager in the CONNECT Edition 8. CONNECT Edition also applied Camel Case folder naming 4. Associate an active WorkSet to multiple files using 'Batch Process': In the CONNECT Edition, all DGNs should be associated with (or belong to) a WorkSet. DGN files belonging to a WorkSet include WorkSet information or WorkSet properties. This enables you to place WorkSet properties as text fields and title blocks. This also notifies the users if they try to open a DGN from outside of the active WorkSet, helping the users maintain the data integrity of their DGNs. When you open a DGN file in a WorkSet, the CONNECT Edition checks if the file belongs to the active WorkSet, considering you just upgrade your v8i project to a CONNECT WorkSet, all you DGNs still remain unassociated and you will receive alerts to associate your file with the active WorkSet. In order to reduce the overhead of manually associating each file with the Active WorkSet, You can use "Batch Process" to automate the association. You can associate an active WorkSet to multiple files using 'Batch Process' : 1. Launch CONNECT Edition application 2. Select Workspace>WorkSet - In the Welcome page, select the desired Workspace and WorkSet and open a file within that WorkSet. 3. Acknowledge Alert - You should receive the following alert ( the this case the active WorkSet was "Building"). Since this should be the first time you are opening the file in the CONNECT Edition, the file your opening should be unassociated. With the default option to "Use active WorkSet…", select 'Open' 4. Locate and Open the 'Batch Process' - To easily locate the 'Batch Process' feature you can take advantage of the Ribbon Bar search option, by simply starting to type 'Batch Process' in search box in the upper right side of the Ribbon Bar (see below) or it can be accessed from the backstage under File>Tools. 5. Browse for Command File -In the 'Batch Process' dialog, browse for the Associate_Workset_cmdfile.txt command file. By default, this command file should be delivered at …\Program Files\Bentley\AECOsim CONNECT Edition\AECOsimBuildingDesigner\Default\Data\. This file contains two keyins: ○ FILE ASSOCIATEWORKSET # Associate files to active WorkSet ○ FILEDESIGN SAVE SETTINGS # Save Setting 6. Select File to Batch Process - Select the files that you want to assign to the active WorkSet. Remember that CONNECT Edition checks for associated WorkSet during the following activities: ○ attaching references ○ attaching links to a link set ○ adding sheets to a sheet index ○ placing text fields pointing to WorkSet properties 7. Run the batch process. * Note: Disassociation of a DGN from a WorkSet is also available. To unassociate a WorkSet from a file, use the key-in FILE DISASSOCIATEWORKSET. Do not do a save settings, else the WorkSet will again be assigned to the active file. 5. Datasets: Currently, the differences between the AECOsim Building Designer SELECTseries 6, Update 1 and the CONNECT Edition datasets are minor. Therefore, there is most SELECTseries 6, Update1 should easily be reutilized and moved forward for CONNECT adoption. Dataset should remain major version specific, please do not share a SELECTseries 6, Update1 dataset with both the SELECTseries 6 and CONNECT Edition application. Make version specific copies.
↧
Wiki Page: CONNECT Edition - How to Manually migrate a V8i Project(.pcf) to a CONNECT WorkSet(.cfg) and adopt CONNECT folder structures
↧
Wiki Page: CONNECT Edition - What Configuration Changes have been made in Platform?
Product(s): AECOsim Building Designer Version(s): CONNECT Edition (10.0.0.154) Environment: N/A Area: General Subarea: N/A Background This is a basic overview of configuration changes made at CONNECT Edition Power Platform level. These changes are common to all Power Platform based CONNECT Edition applications. Further explanation of these changes can be found in the delivered help: Home > What's New > CONNECT Edition > New and Changed in MicroStationCONNECT Edition > Configuration and Home > Setting Up the Environment > Configuration Or in our online help documents at Bentley Product Documentation . Go to the Building Design tile, select 'AECOsim Building Designer Help' then click anywhere on the tile to proceed. Configuration changes in CONNECT Edition Please note that the following is intended as an overview of the installation and configuration changes in MicroStation CONNECT Edition 10.00.00.25 compared to previous versions as well as any future releases. Further information is available in the delivered help under: Home > What's New? > Please be sure to consult your site administrator of any changes being made to the configuration, as this may result in unwanted issues. I would also backup any original files and track changes being made (this will make it easier to undo any changes made if issues arise). The previous Workspace System folder now with the product In V8i, the System folder and its subfolders and files, were delivered under the Workspace folder structure and contained Bentley delivered configuration files. This created problems when CAD Administrators moved the Workspace folder and its subfolders and files to a networked location creating the possibility of version mismatches between application and the networked folders. So to avoid this issue and to make a clearer distintion between files that are fundamental to application finction and thsoe that can or should be site specific, CONNECT Edition applications store these resources in a folder named “Default”, a subfolder of the product folder ( eg. MicroStation (…\MicroStation\Default… or AECOsim Building Designer (...\AECOsimBuildingDesigner\Default...). This folder and its contents should not be modified and should only contain the Bentley delivered resource and configuration files. Additional configuration levels added Additional configuration levels nave been added to CONNECT Edition: Further explanation of these can be found in the delivered help: Home > Setting Up the Environment > Configuration > Configuration Concepts Some of the terminology that has changed Site is now Organization Project is now Workset User now really means User Worksets are now organized under a Workspace Further explanation of this can be found in the delivered help: Home > What's New? > New and Changed in MicroStation > Configuration Folder comparison and variable name changes Below is a comparison of the delivered directory structure and some of the configuration variables that are most commonly worked with: V8i CONNECT Edition NOTE: Pre-CONNECT Edition variables are struck through and the variables listed below the arrows are the CONNECT Edition equivalents. _USTN_WORKSPACEROOT has been re-purposed _USTN_WORKSPACEROOT is now used to define the root directory of a specific Workspace: Some new CONNECT configuration variables Here are some of the new configuration variables and their resulting folders in the new directory structure: Something to be aware of with the new variables is the similarity between two sets of variables: _USTN_WORKSPACEROOT and _USTN_WORKSPACE S ROOT (notice the extra “ S ”) _USTN_WORKSETROOT and _USTN_WORKSET S ROOT (notice the extra “ S ”)
↧
↧
Forum Post: RE: CONNECT Edition - Working units
Hi Borja, The working units are a display attribute. You can change them in existing files and in your seed files without affecting the size of any existing elements. This can be done from the Drawing Scale toolbox , I have this docked all the time as mentioned in that link. You can interactively change the displayed working units at any time. The key in SET UNITS e.g. SET UNITS Meters Millimeters can be used in a batch process to apply the required units to a set of existing files (note the US English spelling of 'meters') What must not be changed is the resolution, we recommend that the default of 1000 UOR/mm is used for all AECOsim Building Designer files (this is covered in more detail here ).
↧
Forum Post: RE: Excel Exchange no longer working
OK, we'll see what the log file says...
↧
Forum Post: RE: Parametric Content Creation
Hi Marc, My initial impression is that these new parametric cells are very promising and we did manage to link them and their parameters into the datagroup system with some success. That said, however, these cells will only be useful in some specific situations as there does not appear to be any integration of 2d symbols or penetrators. Or am I missing something here? Cheers, Joey
↧
↧
Wiki Page: CONNECT Edition - How to change Working Units
Product(s): AECOsim Building Designer Version(s): 10.00.00.154 Environment: N\A Area: Settings Subarea: Working Unit Background In default settings of AECOsim Building Designer Connect Edition, when you start working with US Dataset, you will find it has unit of Millimeter. If you need to change it, please go through the following steps. Steps to Accomplish Click on 'File' menu on top left of screen. Then click on 'Settings', select 'File' settings tab and click on 'Design file Settings' option. A pop-up window will open. On left hand side, under category tab of that pop-up window, please select 'Working Units'. On right hand side, under 'Linear Units' , please change 'Master Unit' and 'Sub Unit' to your preferable unit from drop-down. e.g. Meters. Once done, click on 'OK' and go back to your work window. You will be able to find that the working unit has been changed. From below image you can see that Millimeter Units (marked in red boundary) has changed to Meters (marked in blue boundary).
↧
Forum Post: RE: CONNECT Edition - Working units
Hi Borja, There is a community link regarding how to change How to change working units . You can try this also.
↧
Forum Post: RE: Parametric Content Creation
Hi Joey, Glad you have found the current capabilities useful. Some new parametric features were added in MicroStation CONNECT Update 5 that are also in ABD CONNECT. We don't have 2D symbols or perforators for these cells yet, work is in progress but I can't offer any more news about what we will have or when at present.
↧
Forum Post: RE: How to copy a curved line from reference file
Is Locate enabled for the reference? If I turn off Locate in the reference dialog I cannot use the referenced element.
↧
↧
Forum Post: ABD Revit Interop Workflows ?
Revit is the new DWG for many sectors. 1. Bentley STAAD/RAM users have a bi-directional ISM link with Revit 2. ABD has a one way link with i-model exporter for Revit 3. ABD has an IFC importer 4. Mstn has an IFC reference tool. 5. Mstn has inherited ABD's RFA importer. There seems to be considerable fragmentation here. I remember an old YII presentation where a long time Bentley ABD user Fitzpatrick Engineering Group had to use multiple exporting tools to cobble together enough info to interop with their Revit partners, just for structures. A consolidated tool would be a great help. I hope that Bentley has plans for a major push here. Ideally, the existing Revit ISM link would be upgraded to include non-structural information (Architectural, Mech and Electrical; as well as Environmental for AES). This would provide the most strightforward way to interop with the increasing number of Revit-based jobs. I think that in this context, the ISM would be part of the new 'Design Sync' platform, mentioned with the launch of ISM 4.0, but seems to have stalled. Probably bumped by the port to 64bit and Connect. A 'transaction hub' type workflow would fit in with the current BIM practice of weekly 'shares'. I think OpenPlant has added for very similar tools for better interaction between its MEP-focused authoring envionment and structural modeling. It is big advantge for ABD users that the ISM files can be Ref attached like a dgn. ISM is already used to store the copious settings and mapping tables that would be repeatedly used. One problem with IFC only transfer is the loss of parametrics / smarts. This is unlikely to be accepatble to clients and partners over the long term. RFA-Interpreter should form part of the ISM/DS Revit link. RFA Interpreter current does not support: Revit system types (walls, curtain wall, stairs, etc..) 2D only RFAs (title blocks tags, profiles, etc..) Embedded formats (DWG, SKP, etc. placed inside the RFA) Changing the original RFA definition Maybe the new ODA Teigha BIM API and Flux.io 's SDK might also be able to help crack the.rvt format? 2d information is a pretty big gap for any ABD user working with Revit.
↧
Forum Post: RE: ABD Revit Interop Workflows ?
Does the new/current ODA Teigha BIM API require REVIT License to work on .rvt?
↧
Wiki Page: Unable to find lighting file : xxx.xxx.IES
Product(s): AECOsim Building Designer Version(s): 08.11.09.866 Environment: N\A Area: Electrical Annotation and Design Subarea: N\A Problem When I am opening DGN file contains Electrical symbols, the message center shows following errors and the file takes bit of time to open. We have decided that these IES files are no longer needed. Solution The fastest way to remove the above error is to remove IES data from the file. Following steps requires to remove IES data from file. 1. Go to Setting tab > Rendering > Light Manager. 2. Select all BBES lighting symbols, Toggle off Properties and IES data option. (See below image) 3. Wait till process completes. 4. Restart the AECOsim Building Designer. This should resolve your IES files problem.
↧
Wiki Page: Parsing Error while trying to 'Place Concrete Beam' tool
Product(s): AECOsim Building Designer Version(s): 08.11.09.866 Environment: N\A Area: ProjectWise Integration Subarea: Error Background Error message is displayed when ‘Place Concrete Beam’ tool is used from the toolbox in AECOsim Building Designer integrated with ProjectWise. The same problem is not faced when working in offline mode. "violates enumeration constraint of 'PAZ BXC CEL RFA'. The attribute 'type' with value" failed to parse. Steps to Accomplish This problem indicates a ProjectWise problem in Managed Workspace. Also, this parsing error indicated a problem in the .xml file which keeps structural beam information. The error message displayed, can be due to a corrupted .xml file. Please go through the following steps to solve this issue, Follow the path below to the data group system folder to check the .xml file (Only for UK & SG Dataset) 'C:\ProgramData\Bentley\AECOsimBuildingDesigner V8i Ss6\WorkSpace\BuildingDatasets\Dataset_UK\datagroupsystem' To check, we must review the ‘StructuralCatalogTypesexts.xml’ . Follow the path below to the data group system folder to check the .xml file (For US and all other Dataset) 'C:\ProgramData\Bentley\AECOsimBuildingDesigner V8i Ss6\WorkSpace\BuildingDatasets\Dataset_US\datagroupsystem' To check, we must review the ‘_Dataset_catalogtypeexts.xml’. The image below shows ParaDef command in the ‘StructuralCatalogTypesexts.xml’ or ‘_Dataset_catalogtypeexts.xml’ . The ParaDef definition isn't used by components that do not rely on cells, such as columns, so the tool itself (code) doesn't know what to do with it. Just delete the ParaDef commands in the ‘StructuralCatalogTypesexts.xml’ or ‘_Dataset_catalogtypeexts.xml’ where the commands were present previously. Refer image below for reference. Now, when you try to ‘Place Concrete Beam’ tool from the toolbox, it will work perfectly in AECOsim Building Designer within ProjectWise.
↧
↧
Wiki Page: Break Wall command doesn't work
Product(s): AECOsim Building Designer Version(s): 08.11.09.863 Environment: N\A Area: Architectural Design Subarea: Walls Background While trying to place a wall by unlocking "graphic group lock" and "imply relationship lock" and then trying to break one layer of the wall (for example: insulation), the "break wall" command doesn't work from that moment even with the "locks" is switched back "ON". Steps to Accomplish This is a problem in the AECOsim 08.11.09.863 which has been already fixed in AECOsim 08.11.09.866 & CONNECT. Refer below to the video to check the workflow used to reproduce the solution in AECOsim Building Designer 08.11.09.866. (Please visit the site to view this video) It is recommended that you should upgrade your system to AECOsim Building Designer 08.11.09.866 or CONNECT Edition for resolution of this issue.
↧
Wiki Page: How to turn on/off multiple grids of multiple buildings
Product(s): AECOsim Building Designer Version(s): 10.00.00.154 Environment: N\A Area: Grid System Subarea: N\A Background When you have two or more than two buildings with two different grid systems, you are not able to turn on / off grid of your choice. Steps to Accomplish You can resolve this issue by following the steps below. Create a new Levels. Create a new Dimension Style. How to add or remove buildings from Building Manager. How to create new grids and change its settings. How to assign grids to building and turn off or on individually.
↧
Forum Post: RE: ABD Revit Interop Workflows ?
I don't think so. http://www.upfrontezine.com/2016/10/qa-with-the-oda-president-neil-peterson.html http://www.upfrontezine.com/2016/09/oda-opens-the-revit-file-format.html " The API provides the following benefits, the ODA says: Access data in Revit files without needing a license of Revit. Three years of an annual Revit subscription is $6,000. (Autodesk currently costs its annual subscriptions at 1/3 of the software's former permanent license price.) "
↧
Wiki Page: IFC - Export - Setting the Author Properties for Your Organisation
Product(s): AECOsim Building Designer Version(s): 08.11.09.829 Environment: N/A Area: Import/Export Subarea: IFC You would probably like to make the content of IFC Export Author properties consistent across your organisation. We do not have key-ins to apply content to these fields, but they can be populated by VBA. The attached VBA can be used to do this. If you run this on a test user you will find the IFC Export Author properties populated as shown below: To insert your own values edit the VBA replacing the placeholder text entries shown above with your own details. The Role field is populated by the list index number, starting at 0. For example: Architect = 4; Structural Engineer = 5; Mechanical Engineer = 10. The sequence contained in the VBA is to send a command to load the IFC module: CadInputQueue.SendKeyin "mdl load tfifc" Followed by a sequence of 'SetCExpressionValue' commands that set MDL variables, e.g.: SetCExpressionValue "g_exportInfo.stepFile.organization", "My Company Name", "TFIFC" This macro can be run manually or set to run automatically using the MS_VBAAUTOLOADPROJECTS variable at site or if project specific variations are needed at project level. (Please visit the site to view this file) Here is the full text of the macro with the placeholders highlighted: Sub SetIFCExportAuthorProperties() Dim startPoint As Point3d Dim point As Point3d, point2 As Point3d Dim lngTemp As Long ' Send a keyin that can be a command string CadInputQueue.SendKeyin "mdl load tfifc" ' Set a variable associated with a dialog box SetCExpressionValue "g_exportInfo.stepFile.modPerson.givenName", " My First name ", "TFIFC" SetCExpressionValue "g_exportInfo.stepFile.modPerson.familyName", " My Family Name ", "TFIFC" SetCExpressionValue "g_exportInfo.stepFile.modPerson.role", 4 , "TFIFC" SetCExpressionValue "g_exportInfo.stepFile.modPerson.sAddress.sTelecom.EMail", " my@email@.com ", "TFIFC" SetCExpressionValue "g_exportInfo.stepFile.modPerson.sAddress.sTelecom.TelephoneNumber", " 0000 000000 ", "TFIFC" SetCExpressionValue "g_exportInfo.stepFile.organization", " My Company Name ", "TFIFC" SetCExpressionValue "g_exportInfo.stepFile.modPerson.sAddress.sPostal.Country", " My Country ", "TFIFC" SetCExpressionValue "g_exportInfo.stepFile.modPerson.sAddress.sPostal.PostalCode", " My Postal Code ", "TFIFC" SetCExpressionValue "g_exportInfo.stepFile.modPerson.sAddress.sPostal.Town", " My Town ", "TFIFC" SetCExpressionValue "g_exportInfo.stepFile.modPerson.sAddress.sPostal.Region", " My Region/State/County ", "TFIFC" SetCExpressionValue "g_exportInfo.stepFile.modPerson.sAddress.sPostal.AddressLine", " My Address Line 1 ", "TFIFC" SetCExpressionValue "g_exportInfo.stepFile.modPerson.sAddress.sPostal.AddressLine2", " My Address Line 2 ", "TFIFC" CommandState.StartDefaultCommand End Sub Comments or Corrections? Bentley's Technical Support Group requests that you please confine any comments you have on this Wiki entry to this "Comments or Corrections?" section. THANK YOU!
↧
↧
Wiki Page: IFC - IFCOUT Key-in Command and Switches
Product(s): AECOsim Building Designer Version(s): 08.11.09.829 Environment: N/A Area: Import/Export Subarea: IFC This key-in and switches can be used with the Batch Process Utility as described in IFC - Batch Export to IFC using the Batch Processor . All your commands will generally start with ifcout * unless you need to apply a specific name, the * takes the source DGN filename as the name of the output IFC. There are six switches, corresponding to drop-down or tick box options in the IFC Export dialog, that can be applied to this key-in, they have a short and long form, e.g.: 'c' or 'cobie'. They also have arguments to control their operation, e.g.: 'm:FMH' or 'mvd:FMH' If no switches are applied their defaults will be applied: schema: 2x3 mvd: Coordination View cobie: off imodel: off optimize: on zip: off The result of the key-in 'ifcout *' command would be to create and optimise an IFC file using the IFC 2x3 Coordination View 2.0 Model View Definition. As I would always optimise the IFC, in most cases the switches only need to be applied if you need to output to the FM Handover Model View Definition and/or create COBie output or i-models. In the batch convert context it will probably be more useful to zip the files afterwards rather than have individual zip files (depending on the sizes of your outgoing IFC of course) so you may not need to use the z switch. Note: While testing the switches I have found that in AECOsim Building Designer SS6 the c switch will always create an i-model unless told not to by stating c:0 (or cobie:0), a defect has been filed to address this problem.
↧
Wiki Page: IFC - Batch Export to IFC using the Batch Processor
Product(s): AECOsim Building Designer Version(s): 08.11.09.829 Environment: N/A Area: Import/Export Subarea: IFC We currently have the ability to batch process IFC Export using the Batch Process Utility. This is a MicroStation platform tool that has many uses. Please refer to the 'Batch Process Utility' help topic for details of how to use this powerful utility. Once you are familiar with operation of the Batch Process Utility take the following steps: Having opened the Batch Process Utility create a new command file as directed in help. The command file must start with: mdl load tfifc followed by the ifcout command and the required switches, e.g.: ifcout * m:FMH z All of the available switches and further examples are documented in AECOsim Building Designer help, search for 'IFCOUT' in either AECOsim Building Designer SS5 or SS6. They are also discussed in IFC - IFCOUT Key-in Command and Switches .Note that the key-in modifiers only need to be added if you wish to change from the defaults. The default output settings are: COBie : Off I-model : Off Optimise : On Zip : Off mvd (Model View Definition) : Coordination View IFC Schema : 2x3 Here is what a command file containing these will look like: #---------------------------------------------------------------------- # # Command file for batchprocess utility # # This command file was originally copied from $(MS_DATA)cmdfiletemplate.txt. # Command file information: # - Lines that start with the '#' character are treated as comments and ignored. # #---------------------------------------------------------------------- mdl load tfifc ifcout * m:FMH z Generally the content for export will be in the default model so the Batch Process Utility 'Initial Model' option can be set to 'All Models' to avoid unnecessarily processing any Drawing or Sheet model that my be present in the files listed.
↧
Forum Post: End Type Connection in AECOsim Building Designer V8i SS5
How many End Type Connection in Mechanical AECOsim Building Designer V8i SS5 ? how can i create my own end type connection with complected shape like Victaulic connection in the firefighting system? Victaulic Coupling
↧