At 9:29 UTC on September 4th Azure experienced a localized spike in temperature. Automated data center procedures to ensure data and hardware integrity went into effect when temperatures hit a specified threshold. Engineers are actively working to restore services.

Hevacomp Energy Assessor (Non-dwelling) Level 3 & 4 (SBEM)

Allows Hevacomp users - via an accredited Energy Assessor scheme provider - to work towards Energy Assessor status to show competency in production of EPC's using an approved SBEM interface. This works towards the Hevacomp Software Competency Exam, accepted by CIBSE and Stroma.

Energy Assessor course and examination will be held in our London office. Now open for registration via links below.

We are pleased to announce the availability of CONNECT Edition of the following Bentley Hydraulics and Hydrology products:

• PondPack CONNECT Edition (10.00.00.02)
• FlowMaster CONNECT Edition (10.00.00.02)

This release is available at no cost for SELECT and ELS subscribers and includes the following updates:

What's new in PondPack CONNECT Edition?

What's new in FlowMaster CONNECT Edition?

For more information on downloading this release, please see the following article: Downloading Haestad / Hydraulics and Hydrology Software

Custom line styles, like many other element types in MicroStation (such as text, patterns, and detailing symbols), can be used in Annotation Scale-based workflows. The key to working with “annotatable” line styles is to consistently size them based upon a 1:1 printing environment (base scale), with Annotation Scale controlling the scale of the display of the custom line style when it is used in design and drawing models, across multiple design files that use different annotation scales, and in reference attachments.

In the past:

Historically, many organizations did not print at a true 1:1, but rather printed at a scale. To help facilitate this style of printing, it was not uncommon for custom line styles to be pre-scaled based upon their most commonly used print scale. This allowed a custom line style to be placed with an active line style scale of 1.0 when used in a “full-size” drawing, or 0.5 for a “half-scale” drawing.

Exploring this further, if the standard print scale was 1:20, the components in a custom line style would have been scaled up by a factor of 20 when a custom line style was created. If the standard print scale is 1:40, the line style components would be pre-scaled by a factor of 40.

Let’s look at the following “Arrow” line style in greater detail using a print scale of 20 (1” of paper represents 20 units):

Custom line styles are based upon Master Units. If on the final print the line style repetition is to be 1 inch in length, and the print scale is 20, the total length of one instance of the repetition needs to be 20 master units when printed. The following stroke pattern illustrates this length of 20 units.

This stroke pattern is composed of three individual strokes. The first “dash” is 9 units, the arrow is 2 units, and the second dash is 9 units in length totaling an overall length of 20 master units.

A base scale of 1:1

To bring this custom line style forward such that it can be used in an annotation scale-based workflow (where printing is performed with a print scale of 1:1), the size of the line style components must be reduced to a true 1:1. In this example, each measurement would need to be 1/20^th the original size.

When used with an annotation scale of 1:20, the custom line style would be scaled up by a factor of 20, yielding the correct size.

Furthermore, the custom line style could be used in design files with any annotation scale, with each repetition still being displayed as 1” in length when printed.

Compound Scale

For those that have custom line styles that have been scaled to a predefined base scale (other than 1:1), and do not want to change their custom line style definitions to a base scale of 1:1, you may still be able to use Annotation Scale to affect the size of custom line styles by using “Compound Scale”.

Note: As discussed earlier, a predefined base scale is where the line style components have been pre-scaled by a factor such as 1:20 or 1:40, allowing line styles to be placed using a line style scale of 1.0

In Model Properties, the scale of custom line styles can be set to any one of the following:

• Global Line Style Scale
• Annotation Scale
• Compound Scale

Compound Scale is a combination of Global Line Style Scale and Annotation Scale…meaning it uses the values for both settings to affect the “scale” of custom line styles.

In the example shown previously, the Arrows custom line style components had been “sized up” by a factor of 20. For this line style definition to be used in an annotation scale-based workflow, the size of the existing stroke pattern was reduced by a factor of 20, thus setting it to a base scale of 1:1.

Rather than redefine a set of custom line styles using this approach, the Properties of the model could be altered to accommodate using Compound Scale. In Model Properties, set the following:

• Line Style Scale: Compound Scale
• Global Line Style Scale Factor: 0.05

Setting the Global Line Style Scale Factor to 0.05 reduces the scale of custom line styles in the model to 1/20^th their original size, essentially sets them to a base scale of 1:1.

Changing Line Style Scale to Compound Scale allows the Global Line Style Scale Factor to be implemented and allows any custom line styles in the model to be influenced by Annotation Scale.

Note: This requires that all custom line styles used within this type of workflow are consistently set to the same base scale such as 1:20. The settings in Model Properties for Line Style Scale and Global Line Style Scale Factor could be pre-set in any seed file to facilitate using this workflow in new design files that are created without a User have to change the properties in the new file.

Physical line styles

For custom line styles that do not need to be affected by a scale factor, meaning that the line style represents something measurable in the real world, the can be made physical using the “Physical” setting available in the Line Style Editor. This can be set individually per line style. This setting prevents a custom line style from being scaled by Global Line Style Scale Factor, Annotation Scale, or Compound Scale.

For more information on creating custom line styles, visit the course on the Bentley LEARNserver. 

• The Bentley LEARNserver course: DGNLib’s
• The Bentley LEARNserver course: Creating Custom Line Styles

Happy LEARNing!

Are you keeping your model in sync with a GIS? Do you wish you had more insight into what has changed since the last update? In this short demonstration, see how the ModelBuilder Snapshots feature in the CONNECT Edition of Bentley's Haestad products enables you to make better model synchronization decisions by keeping track of changes in your GIS.

Applicable Products: WaterCAD, WaterGEMS, HAMMER, SewerGEMS, SewerCAD, StormCAD, CivilStorm: CONNECT Edition Update 1 (10.01.00.XX) and greater

To learn more, check out the additional resources in the "See Also" section below.

https://youtu.be/X8EElbkcs4s

Want to see more? Sign in, click the More button and turn blog notifications on. Or, subscribe to our YouTube Channel.

This video is part of a growing library of useful information designed to provide effective tips and information about time-saving product features within Bentley’s Haestad | Hydraulics and Hydrology products. Be sure to check back frequently to view the latest video. Better yet, subscribe to this blog by turning Notifications On.

Yashodhan Joshi
Product Engineer
Bentley Systems, Inc.

See Also

Using ModelBuilder snapshots to help track changes and updates between source file and model file

Are you keeping your model in sync with a GIS? Do you wish you had more insight into what has changed since the last update? In this short demonstration, see how the ModelBuilder Snapshots feature in the CONNECT Edition of Bentley's Haestad products enables you to make better model synchronization decisions by keeping track of changes in your GIS.

Applicable Products: WaterCAD, WaterGEMS, HAMMER, SewerGEMS, SewerCAD, StormCAD, CivilStorm: CONNECT Edition Update 1 (10.01.00.XX) and greater

To learn more, check out the additional resources in the "See Also" section below.

https://youtu.be/X8EElbkcs4s

Want to see more? Sign in, click the More button and turn blog notifications on. Or, subscribe to our YouTube Channel.

This video is part of a growing library of useful information designed to provide effective tips and information about time-saving product features within Bentley’s Haestad | Hydraulics and Hydrology products. Be sure to check back frequently to view the latest video. Better yet, subscribe to this blog by turning Notifications On.

Yashodhan Joshi
Product Engineer
Bentley Systems, Inc.

See Also

Using ModelBuilder snapshots to help track changes and updates between source file and model file

Hello team,

i am facing problem while opening up Bentley Instrumentation and wiring.

when i try to launch Bentley I&W ,message pops ups. attached is the snap of message.

kinldy help.

thanks

Siddharaj Talawar

As part of this update we have added several features which you can test to ensure the features are working properly prior to the commercial release of Navigator CONNECT Edition Update 5. Below is a list of the new capabilities, as well as the link to download the update.

Click on the link to download the Navigator CONNECT Edition Beta Update 5.

• Native file support for DGN files: From the File Open screen in Navigator, you can open Bentley DGN files.
• Organizer: The Organizer is used to inspect the model by displaying a tree that organizes the model by properties. 
• KOQ support for application tool: You can specify the format of the units displayed by Navigator's tools and properties. You can specify the unit format by clicking a property's More Actions button and selecting the units from the dropdown, or you can access more advanced unit specifications by selecting Manage from the dropdown, which opens the Display Units Manager. The Display Units Manager can also be opened from the Settings page.
  
• Partial Alignment Selection: You can select a specified range of the model based on an alignment. This allows you to focus on a certain area of the model.

If you have any problems or you would like to send any feedback during your testing of Navigator CONNECT Edition Beta Update 5, you will find a feedback menu entry in the backstage menu. From the feedback menu entry you can send an email to the NavigatorBeta@bentley.com email address which has been created to capture feedback for this technology preview.

Please note that this technology preview of Navigator CONNECT Edition Update 5 is only available for Windows desktop.

Updating design files is often a necessary but tedious task that can be prone to errors and irregularities. When individual files are touched “by hand”, repeated actions can easily be altered or even missed entirely. Automating the update process by scripting out the desired set of actions can streamline and speed the process with a consistent set of output files. This can be achieved through a Batch Process using a script containing the desired commands to be processed.

The Batch Process Utility

The Batch Process utility lets you create and run a script that can be performed on individual files or entire directories of files. The script is a text file that contains a series of MicroStation key-ins that can run commands, MicroStation VBA Macros, or MDL applications. For example, you could use the Batch Process utility to quickly remove the unused levels from a selection of design files. The Batch Process utility also lets you define and save a batch process job file. A job file defines the script (command file) and the files to be processed with it. The job file can then be opened, allowing the same batch process to easily be re-run in the future.

Accessing the Batch Process Utility

In the MicroStation CONNECT Edition, the Batch Process utility may be accessed from Tools in the Backstage view or activated from Search Ribbon.

When selected, the Batch Process dialog opens.

(Batch Process dialog)

From Batch Process you may:

• Create, Open, or Edit a command file
• Add files or directories to process
• Open or Save a Batch Process job file
• Process a Batch Process job

The following steps are used to create a Batch Process:

1. Select a Batch Process command file.
2. Add files or directories to be processed.
3. Set the value for Initial Model (using Apply to Selection button).
4. Save a Batch Process job file (optional).
5. Run the Batch Process.
6. Review the results (including log file as desired).

The Command File

The Batch Process command file, or script, is used to process a sequence of commands on a selection of files. Command files may be composed to serve any variety of purposes. They can be created as a one off, used for a specific operation, or archived and used repeatedly across files, departments and disciplines, and projects. It can vary from very simple, consisting of but a single command, to quite complex where an extended series of commands are executed.

To create a command file, from Batch Process pick the icon: Create a new command file. You will then be prompted to provide a name and location for the new file, followed by picking Save to complete creating the file. The new command file then opens in a text editor, allowing the desired key-ins to be added.

(Batch Process command file)

When a new command file is generated, a template is used to provide a starting point for the new file being created. It is possible to modify the template to include a custom set of “default” comments and key-ins to be included in each new command file.

The command file is an ASCII text file containing one or more MicroStation Key-ins. Individual lines may consist of a single command (key-in) or contain a series of commands where each key-in contained in the line is separated by a semicolon.

When creating a command file, it is considered a “best practice” to document what is occurring within each line in the script. A liberal use of comments will assist with maintenance, updating, and in helping others to understand what is occurring. Comments begin with the “#” character. The comment symbol can be used at the beginning of a line or can occur at any point within the line. This can be seen in the example shown below.

(Use of commenting in Batch Process command file)

Comments can also be used to prevent a line from being executed without removing that line from the command file. Think of it as a way of “retiring” a command. The command still exists in the script and can be reactivated (by removing the comment symbol) when it is needed again.

Note: It is not necessary to access command files only through the Batch Process dialog. A command file can also be created/edited externally from MicroStation using the text editor of your choice.

Adding key-ins to the Command File

Virtually any valid MicroStation key-in can be added to a command file. This includes key-ins to control view attributes, update definitions such as levels and text styles, as well as run macros and MDL applications. The following are some sample key-ins that may be used in a command file:

Basic key-ins

Update all text fields in active model:

field update all model

Update a specific type of design library:

dgnlib update dimstyles

Turn off the display of construction elements in view 1 and update the display:

set construct off; selview 1; update 1

To run a macro (.bmr)

A MicroStation basic macro can be run using the following key-in syntax:

Run a macro:

macro play MacroNameHere

Note: For MicroStation to run a macro using this key-in, the macro must be located in a folder defined through the configuration variable MS_MACRO.

To load an MDL

An MDL application can be loaded using the following key-in syntax:

Load an MDL:

mdl load MDLNameHere

Note: This example will load an MDL application. The MDL must be located in a folder defined through the configuration variable MS_MDL. This will only load the MDL. Many MDL applications, once loaded, will have key-ins that then may be accessed. Many MDL’s only need to be loaded once, and once loaded stay loaded, and can be used across multiple files.

The following examples illustrate the use of key-ins and comments. Take a few moments and review the following command files:

communities.bentley.com/.../5355.MicroStation-CONNECT-Upgrade.txt          communities.bentley.com/.../8244.Project-Archival.txt          communities.bentley.com/.../1488.Project-Submittal.txt

Creating and Running a Batch Process

To create and run a Batch Process job is simple, consisting of a few basic steps as outlined earlier. We will now walk through these steps in greater detail.

1. Select a Batch Process command file.

The first step is to create or select a command file to use for the Batch Process. Here, the Browse button is being used to locate an existing Command File.

2. Add files or directories to be processed.

After the command file has been chosen, it is time to add files. In the lower left corner of the Select Files and Directories to process dialog, click the arrow to expand the dialog, displaying Selected Files. Browse the folder containing the files you wish to add. Select the files, pick Add, repeating this process until all desired files have been added. Pick Done.

Once the files have been added, the files can be reordered using the “Move” commands located in the Edit menu in the Batch Process dialog.

3. Set the value for Initial Model (using Apply to Selection button).

It is now time to set the value for Initial. This was initially set as “All Models” and is what is applied to files that are added to the Batch Process. It can be set before files are added or modified on a selection of files already listed in the Batch Process dialog. This is done by selecting one or more files, picking the desired setting, and clicking the button Apply to Selection.  

4. Save a Batch Process job file (optional).

If the same Batch Process will need to be run again at some point in the future, it is possible to save the existing Batch Process configuration as a Batch Process Job file. The Job file may then be opened, with the Batch Process automatically loading all the required information to run the Batch Process including the Command File, files to be processed, order, model settings, etc.

5. Run the Batch Process.

When the Batch Process has been configured as desired, it can then be ran using Process Batch Process Job. When selected, the Files to Process dialog opens. Pick Process to begin the Batch Process job.

The files are processed in the order shown in the dialog, with Status displaying the current position in the job.

6. Review the results (including log file as desired).

Once the Batch Process has completed, the results can then be viewed. In the Files to Process dialog the Status has updated, and processing time displayed.

It is also possible to display the content of the log file. The name and location of the log file can be determined from the Batch Process dialog by picking Edit> Log File Options… and viewing what is displayed in the Log File Options dialog.

Note: The location of the log file is determined by the value of the configuration variable _USTN_OUT.

The log file is an ASCII text file, viewable with any text editor. It displays the start time, files processed, processing time, and end time.

(Log file displaying the results of a completed Batch Process)

Note: The Batch Process opens each file in MicroStation. The amount of time required can vary depending upon the number of files to process, individual file size, or if the command file includes a more involved set of key-ins.

Additional Uses

You may wonder what the Batch Process utility can be used for. It is certainly not limited to just what was presented within this blog. The following list provides a few possible uses for the Batch Process utility and command file:

• Assist in migrating project files from a previous version of MicroStation to the MicroStation CONNECT Edition
• Updating existing CAD Standards in files
• Preparing to transfer a set of files to someone else
• Prepare a project for archival

 The uses are limited only by your imagination!

In part 2 of this series we will examine ways to obtain the required key-ins for use in command files.

 Happy LEARNing!

By default, we show all information for a Work Order no matter what the Work Type.

For some types of task, all of this information does not make sense.

If you open a particular Work Type (this can be done from the Work Management view, Settings tab, Work Type subtab), you can change what information is shown.

In my example, I have turned off most of the options and there are far fewer tabs and views to confuse users.

I've put together some examples of CONNECT Reports, with instructions on how to define them.  These were prompted by a need to find an alternative to MicroStation's venerable XYZ Text tool.  As well as an XYZ Text Report example, I've added a Cell Report and a Linear Report example.

Each example shows step-by-step how the Report is defined, with examples of CSV file and Excel file output.  You can download a ZIP file that contains the DGN file containing the Reports definitions and sample output data.

Key-ins are what drive the Batch Process utility. Adding key-ins to your command file allows you to direct the set of actions that will be applied and the order in which to apply them. It is possible to use MicroStation key-ins directly, run a MicroStation VBA Macro or an MDL application through a key-in, and potentially integrate key-ins from a specific vertical application if that application is also running (such as those commands associated with a specific PowerPlatform).

You may ask yourself, “How do I find the key-ins to use?” Locating the desired key-ins can range from quite easy to difficult, or not possible to locate at all if a key-in doesn’t exist for what you are trying to do. Let’s look at a couple of possibilities.

The Key-in Browser

The Key-in browser is probably the first place most will go to start looking for key-ins…it is logical to look for key-ins in a “Key-in” dialog. In the MicroStation CONNECT Edition the Key-in browser can be opened several different ways:

• From the Primary ribbon group in the Home tab of the Drawing workflow
• On the keyboard press <Enter>
• From Search Ribbon (search for Key-in)

 Let’s say that you want to remove any unused levels in a set of DGN files. In the Key-in dialog it is reasonable to begin searching for key-ins that start with the word delete.

Begin by typing in a few characters from the word delete. The display of key-ins is alphabetical…dropping to the first word (key-in) that begins with the characters supplied. You can see “delete” in the list within the first column.

Next, in the second column, scroll down in the list. Here you see displayed the key-ins that can be used to delete various things, including unused items. Pick “unused” in this column.

In the third column you will see displayed the individual types of unused items that can be deleted, including levels. The key-in for deleting unused levels from within the active DGN has just been discovered!

But not all key-ins are quite that logical to locate, with many key-ins having existed for many years and software generations.

Note: Not every command has an equivalent key-in. You may occasionally run into a situation where a key-in for what you are trying to do is not available

Review an Existing Tool

Another way to discover a key-in is to look at existing tools and interface items through the customize dialogs (Customize and Customize Ribbon). From Search Ribbon, type in the first few characters of the word “customize”, picking Customize from the search results shown. This opens the Customize dialog.

In the left pane of the Tools tab, expand Application Tools> MicroStation. Here you will find many of the tool boxes and tools found within MicroStation.

Pick a tool within a tool box. Once selected, you will see the Properties for that tool, including the Command Data. The Command Data is where the key-in for the command con be found. In the following illustration, Fit View has been selected. As can be seen in the Key-in field, the command to fit the view is “fit view extended”.

Finding a Key-in Using the Bentley Macro Recorder

Another way of attempting to locate a key-in is to record a command (or sequence of commands) using the Bentley Macro Recorder. The Bentley Macro Recorder provides a set of features to allow non-programmers to record and play back macros. Once recorded, the macro is saved as a .bmr file and stored at the location identified through the MS_MACRONEWFILEDIRECTORY configuration variable.

From the Utilities tab in the Drawing workflow, locate the Macros ribbon group. As was done in the previous example, an attempt will now be made to locate the “fit” command.

1. To begin recording a new macro, from Macros pick Record. The recorder will now record any action that is performed.
2. From the View tools, pick Fit View.
3. From Macros, pick Stop.
4. The create Macro dialog opens, prompting for a name for the new macro. In Name, type the name for the new macro and pick Save.
5. To view what was recorded by the macro, select the desired macro from the list and pick the command: Edit the currently selected macro

The macro editor is then opened with the recorded command displayed. What is seen here differs from that seen earlier when viewing the Fit View tool through the Customize dialog. When the macro was recorded, the number “1” was appended to the key-in: FIT VIEW EXTENDED 1

The addition of the “1” is used to designate which view window the command should be applied to. The key-in could be modified to specify any of the view windows 1-8:

• Key-in for view window 1: FIT VIEW EXTENDED 1
• Key-in for view window 2: FIT VIEW EXTENDED 2
• Key-in for view window 7: FIT VIEW EXTENDED 7

Note: The sequence that was recorded by the Bentley Macro Recorder could have been much more extensive than the example seen here. The macro could then be used to identify potential MicroStation key-ins or the macro could be ran as a macro file (.bmr file) using a key-in within a command file.

Additional useful key-ins

The following is a list of some additional key-ins that you may find useful when creating a command file, some of which are illustrated in the examples that may be downloaded from this blog post. Remember, when it makes sense to do so, more than a single command can be issued from a line within the command file. A string of commands is composed of individual key-ins (on a single line) that are separated by a semicolon. Additional useful key-ins include:

• selview 1: Used to identify a view window in which to perform an action.
• filedesign: Performs a “save settings”.
• macro playMacroNameHere: Used to run a macro from MicroStation.
• XY=xCord,yCord,zCord: Used to provide a coordinate (such as a data point) where xCord is the “X” coordinate value, yCord is the “Y” coordinate value, and zCord is the Z coordinate value.
• choose all: Used to select all elements in the model.
• choose none: Used to deselect all elements in the model.
• dgnlib update all: Updates all “local” definitions in a DGN to match the parent definitions stored in the configured DGNlibs.
• order element front: Used to bring elements to the front. Works well with a selection set.
• place smartline: The “place” command is used to activate many of the standard placement tools used to create elements. The word “smartline” can be replaced with the name of other tools (i.e. block, arc, etc.) and can have additional parameters applied to the command based upon the specific tool being called (the Key-in browser is a great place to find the additional parameters).
• set acsdisplay on: Used to enable the display of the ACS in a view.

These are certainly not the only key-ins that can be used in command files for the Batch Process utility. There are multitudes of additional useful key-ins that can be applied to meet your needs.

The Batch Process utility is a powerful tool in your Bentley toolbox. The next time you need run a sequence of commands give it a try!

Happy LEARNing!

This document explains how the added inertia coefficients and linearized damping coefficients are calculated and reported in MOSES. Often asked questions are also discussed at the end of the document.

MOSES v10.13 was used in generating results for this work.

Frequency Domain Analysis and Output Results

A frequency domain analysis is usually the basis for generating transfer functions (RAOs) for frequency dependent excitation forces, added mass and damping. The output from a typical radiation-diffraction frequency domain analysis usually contains added mass coefficients, added radii of gyration and linearized values. The linearization is needed due to the nonlinear damping effects particularly in the low frequency response.

MOSES provided the MATRICES command to return an additional PPO file in the answer directory when the -file option is used as in

matrices -file

The MATRICES command is issued in the Frequency Response Menu after the response amplitude operators have been calculated. The added mass and damping matrices are in 6 x 6 format and are reported for the periods and headings defined in G_PRESSURE. Note that the reported damping values are the maximum values over all headings and not the ones really used. This is valid for a spectral linearization, but not for a wave steepness one.

The Added Inertia Coefficients report in the output file contains the added mass coefficients and the added radii of gyration components as a function of frequency. A typical output table is shown in Figure 1.

                                                         Figure 1 Added inertia coefficients (Click image)

In the output file the Linearized Damping Coefficients are also tabulated with reference to Damping / Mass ratio and Damping Radii of Gyration as a function of frequency again. An example is shown in Figure 2.

                                            Figure 2 Linearized damping coefficients (Click image)

The values from Figure 1 and Figure 2 are fitted into the matrices found in the PPO file. For demonstration, this work will focus on the values reported when the encounter period is 20 seconds. The rest of the figures in the matrix are found in a similar manner.

Figure 3 is a snapshot of the corresponding added mass and added radii of gyration coefficients as found in the output file.

             Figure 3 Normalized added mass and added radii of gyration coefficients (Click image)

The same values can be found in the PPO file with the necessary mathematical operation in the rotational degrees of freedom. The comparison is shown in Figure 4.

                                               Figure 4 Added mass matrix for T=20 sec. (Click image)

The reported added radii of gyration values in the rotational degrees of freedom are simply the squared values found in the output file, i.e.

Roll Added Mass = (4.221)² = 17.815

Pitch Added Mass = (11.345)² = 128.719

Yaw Added Mass = (12.089)² = 146.139

Similarly, the reported values of linearized damping coefficients at T=20sec. in the output file are found in PPO file (damping matrix). The values are reported diagonally in the matrix again as shown in Figure 5 and Figure 6.

                                                    Figure 5 Linearized damping coefficients (Click image)

                                                      Figure 6 Damping matrix for T=20sec. (Click image)

The reported damping values in the rotational degrees of freedom are simply the squared values found in the output file, i.e.

Roll Added Mass = (1.470)² = 2.161

Pitch Added Mass = (6.357)² = 40.417

Yaw Added Mass = (1.848)² = 3.414

Each requested period in the G_PRESSURE command will result in two matrices, i.e. one for added mass and one for damping.

Questions & Answers

Q: Do the reported damping values include the radiation component?

A: The reported damping does include radiation. In addition, the -cs_current option will also include viscous terms.

Q: How can I add, or control roll damping in my system?

A: One can use the -roll_damping option in &DESCRIBE PIECE command. Alternatively, bilge keels can be modelled.

Q: How can I add bilge keels in a model?

A: You can use the #PLATE command and use it on the appropriate points along the hull. Look at the b-keels example found in the hdesk directory of the installation files.

Q: The linearization of added mass and damping coefficient is done by 1/20 and is divided by the vessel weight. What is the nature of this ratio?

A: The 1/20 is the wave steepness used to linearize the added mass and damping equations spectrally. This ratio is a remnant from the days when computers could not linearize on a wave spectrum. To override this ratio, the -spectrum option is now available in the RAO command to specify the wave spectrum of the environment which will be used to linearize the motions equations spectrally.

Also see -steep and -rod_steep options in the RAO command to alter the default wave steepness for roll damping and Morison’s drag on bodies, and constant wave height for drag on rod elements.

Q: What is the #AMASS command doing and how is it used?

A: This is a command used to define an added mass matrix at a point. This is normally used with a linear drag matrix in the #DRAG command. It is required that these two commands are included in a jacket launch analysis so that drag and added mass of the barge is included.

Q: What are the units for Damping Radii of Gyration reported in the Linearized Damping Coefficients?

A: The units for damping radii of gyration would be length/sqrt(time).

Q: What are the units for radiation damping coefficients in MOSES output?

A: The output table reports “Values Normalized by Mass with Weight = xxx”. MOSES reports the weight of the body in question and needs to covert this to mass for computing the damping coefficient for later use in third-party applications. The translational components have units of 1/time, while the rotational components have units of length^2/time.

Q: Why is Damping divided by Mass in the linearized damping coefficients output?

A: The output table reports the mass (displacement) that has been used to carry out this division. Without this operation the damping coefficients would be very large numbers; it is used solely for convenience. Note that in the frequency domain, the units for damping after this division will be .1/time  

Q: Is the added mass coefficient reported by MOSES the total added mass? In other words, will the total added mass be the displacement × the added mass coefficient reported, or displacement × (1 + added mass coefficient reported).

A: What MOSES reports is the added mass. This differs from the hydrodynamic mass by 1; i.e. the hydrodynamic mass is the basic mass plus the added mass

I am excited to announce a new release of STAAD.Pro CONNECT Edition Update 3.

As part of our commitment to you to deliver new builds more frequently, we are making available this version which adds great new functionality to improve efficiency for engineers around the world and has resolved numerous issues that have been reported and thus highly recommend that this version is adopted to improve your working experience.

The principal developments and enhancements that are delivered in this new version of STAAD.Pro are:-

Steel AutoDrafting *

A frequently asked feature requested from STAAD.Pro users has been the ability to create general arrangement drawings quickly from a current STAAD.Pro model from within STAAD.Pro itself. So for those users, we have added a new Steel AutoDrafter Workflow to STAAD.Pro CONNECT Edition Update 3 that provides that ability for steel framed structures, either generate the drawing immediately or create a collection of drawings to generate on mass.

* Delivered in STAAD.Pro CONNECT Edition Update 3 as a technology preview and will be released as a fully commercial offering in the next release.

To utilise this feature, please contact your Bentley software provider to obtain an additional free license to add to your portfolio.

Enhanced Modelling

• Concrete Building Modelling

In order to create concrete framed models quicker, Planwin, the application behind the Building Planner Workflow has been added to modules included with a STAAD.Pro subscription, allowing rapid floor-based modelling.

* Delivered in STAAD.Pro CONNECT Edition Update 3 as a technology preview and will be released as a fully commercial offering in the next release.

To utilise this feature, please contact your Bentley software provider to obtain an additional free license to add to your portfolio.

• Physical Modelling

A key benefit in Physical Modelling is the creation of surfaces and having the meshes and managed automatically. A common feature in surfaces is the inclusion of circular openings which can now be included without having to define a faceted opening.  Not only that, but it seamlessly interoperates with a ISM repository. 

The spreadsheet component which drives so much of the physical workflow has been better integrated into the GUI with its own ribbon and sorting routines that make its use far more intuitive.

The most important step forward in physical modelling has been the implementation now of load cases, and load combinations which are now managed through the physical workflow.

Advanced Concrete Design (STAAD.Pro Advanced)

The popularity of the STAAD Advanced Concrete Design application to quickly create concrete designs and produce detail drawings has been widespread.  In order to further add productivity boosts to engineers using this valuable tool, we have added a new Advanced Concrete Design workflow. 

This feature is included with a ‘STAAD.Pro Advanced’ license, if you need to upgrade your license, please contact your Bentley software provider.

Updated Design Codes

The range of member design routines that STAAD.Pro can perform has been extended to provide better and more efficient designs

• AISC 360 – 16
  • Tubular profile design for HSS sections fabricated with high strength steel now leverages the benefits afforded in the design code.
  • More provisions added when considering the torsion forces in wide flange members with cover plates
• ACI 318 – 14
  • Provision of output using Metric units
• AIJ
  • Complete refactored design with support of Envelope design
• IS 13920:2016
  • Implmentation of the 2016 version of the Indian seismic concrete design code.

Seismic Loading

STAAD.Pro is used extensively for construction in locations which are seismically sensitive and requires checks to specific seismic conditions defined in publications such as in the IBC. 

With STAAD.Pro CONNECT Edition Update 3, Two new codes have been added in STAAD.Pro CONNECT Edition Update 3, IBC 2015 and IS 1893:2016.  These provide both additional static seismic loading routines and response spectrum definitions to these publications.

Steel Connection Design (RAM Connection)

The design of steel structures performed in STAAD.Pro is complimented with the design of the connections such as where the beam and columns meet.  Bentley provide this as a standalone tool called RAM Connection. However, engineers using STAAD.Pro can leverage the benefit of having the two software solutions linked through the Steel Connection workflow.

With STAAD.Pro CONNECT Edition Update 3

To utilise this feature, please contact your Bentley software provider to add the RAM Connection license to add to your portfolio.

Section Profile Database

A new steel database of tubular sections manufactured by APPL Apollo have been added to the range of standard sections available from the installation.

Note that if you are already using STAAD.Pro CONNECT Edition, you should be notified of the new build with the Bentley CONNECTION Client.

Revision History

No additional features have been added to the program, however the Revision History document details the issues that have been addressed and as with all builds is included in the ReadMe file which can be accessed from the Help section of the application and can also be found here.