Quantcast
Channel: Bentley Communities
Viewing all 4567 articles
Browse latest View live

Advancing to CONNECT Edition

$
0
0

The CONNECT Edition version of MicroStation enables you to take a massive leap forward with cool features such as Item Types, Sheet Index, Parametric Modeling, and many more. Have you started using powerful properties-based features like Reports, Tables, and Display Rules in your projects yet? Additionally, there are also features such as Configuration, Ribbon UI, that are different and advanced than previous MicroStation versions. To help you in leveraging these advanced features and getting started with CONNECT Edition, we’ve put together an informative playlist of blog posts. Read along.    

Advancing your V8i WorkSpace to CONNECT Edition Configuration

Advancing your Custom V8i MDLAPPs to CONNECT Edition

Customizing your CONNECT Edition Applications for Maximum Productivity

Advancing to Latest Greatest of all Applications


Custom Line Style Series Part 5: Raster Line Styles

$
0
0

Custom line styles are a powerful and flexible feature that can be used to enhance the quality of your designs. They can be used to embellish a model with graphics that are quickly and easily placed by drawing something as simple as a line. Custom line styles can include vector-based geometry though Strokes and Point Symbols, and with the MicroStation CONNECT Edition Update 8, Raster components (consisting of raster images) are supported as well.

Raster line styles are used to supplement existing (geometric) lines styles, providing an alternative display for geometric styles that are based upon repeating raster images. These “raster” custom line styles are primarily useful in 2D drawing and can be very effective in producing high quality and highly efficient designs.

  • Introduced as a Technology Preview in MicroStation CONNECT Edition Update 7
  • Moved to Commercial Release Status in MicroStation CONNECT Edition Update 8

 

In the example below, the upper line style is the standard MicroStation {Rail Road} custom line style. It is defined by two continuous strokes for the tracks, and a point symbol (rectangular block) for the track ties. The lower example is a raster line style that is defined by a raster image.

(Shown above is a vector-based custom line style, below is a raster line style)

 

A Raster custom line style typically consists of a raster component (raster image) along with an underlying set of vector geometry. These components are then brought together using a Compound component.

If a Raster component exists for a line style, it will be used automatically when displaying to the screen or to output devices that support rasterized display. The individual components can be seen in the illustration below.

 

 

When the line style is used on non-raster output devices or older versions of MicroStation, the geometric line style components are automatically displayed.

(Raster line style as seen on a non-raster output device)

 

The MicroStation Connect Edition is delivered a variety of raster line style examples…several of which can be seen in the illustration shown below.

(Raster line style examples)

 

Placing an element using a raster line style is no different than placing an element using any other custom line style. From Attributes, the line style may be set as active, a scale factor assigned, etc.

(The Line Styles dialog showing the preview of the { Recycle Symbol 36” } raster line style)

 

The desired placement command is then chosen, and the element created. Raster line styles can be used in 2D and 3D models within virtually any discipline to quickly enhance a design. Possible uses may include:

  • Pavement markings (and other surface treatments that repeat in a linear fashion)
  • Map enhancements and thematic maps
  • Visualization

Here, the recycling “stencil” on the floor surrounding the recycling bins was created using one of the delivered raster line styles.

(Recycling symbol as a raster line style)

communities.bentley.com/.../3414.Raster-Line-Styles.mp4 

  

Another use for raster line styles is to produce output with a hand-drawn or sketched look. These “sketchy” line styles use a repeating raster image to provide a sketched appearance for the linework in a model. A combination of different sketchy line styles may easily be applied using Level Symbology Overrides and assigning different sketchy line styles to the various levels used within a design. The use of multiple sketchy line styles (of varying widths, darkness, etc.) would allow emphasis to be applied to specific features (such as differentiating between elements in the foreground .vs background) in a design.

  

(Several examples of “sketchy” line styles)

  

(Example of a “sketchy” line style in use in a model) 

  

Take a raster line style for a test drive today!

For more information on raster line styles, as well as step-by-step instructions for creating several raster line style examples, visit the Creating Custom Line Styles course on the Bentley LEARNserver.

 Happy LEARNing!

The Explorer - Part 1: The Introduction

$
0
0

When working on a project, you encounter many types of project related data.  Typical data may consist of CAD files originating from MicroStation or even AutoCAD.  Of that, there are many components that make up these which can range from models (design, drawing, sheet), saved views (plan, elevation, section, detail), and reference attachments.  Any number of styles such as dimension or text styles. Then there could be Items Types, Cells and Levels.  Perhaps your project consists of other, non-CAD data such as Adobe PDFs, Microsoft Word documents, Microsoft Excel workbooks, and their contents.  Maybe you deal with raster's like aerial imagery.  Even data like video or perhaps website links.

Now, when you are working with your project data, whatever data types that may be, have you ever been frustrated when you have to flip through many of these to get to the right model, and correct view?  Wouldn’t it be useful to have something simple that helps you do some organization? Is there a single place in MicroStation where we can list all this important information?

The answer is Yes - the Explorer dialog.

The Explorer dialog, found in the MicroStation CONNECT Edition, builds upon the foundation of the Project Explorer found in earlier editions of MicroStation. In the MicroStation CONNECT Edition, you can manage the project data using the Explorer dialog. It is a single interface that provides browsing function for files, links, items, resources, and sheet indexes.  It can become a central resource to organize your project data.

It provides hierarchical storage for information related to your project such as DGN and DWG files, models, references, Adobe PDFs, Microsoft Word documents, Microsoft Excel workbooks, and their contents, as well as other data file formats. It also hierarchically lists models in the active WorkSet, making the navigation within the WorkSet easier.

The Explorer dialog allows you to navigate easily through the models, saved views, and references in a DGN file, as well as to other supporting files that have been linked to the DGN file. For example, a DGN file may contain an index that lists the drawings in the file, as well as supporting documentation. You could use Explorer to add links from the items in the list to the drawings and supporting files, providing easy access to all documentation related to the WorkSet.

The Explorer dialog can be accessed from the Ribbon from several workflows: 

  • Ribbon: Drawing > Home > Primary

  • Ribbon: Modeling > Home > Primary

  • Ribbon: Admin > Home > Primary

  • Toolbox: Primary Tools

  • Default Function key menu: <Ctrl+F10>

In the image below, here we have the Drawing workflow shown.  And as such, from the Primary group of the Home tab, we can click the Explorer icon to open the dialog.

  • The File tab is used to browse and manage the file content such as models, references, saved views, levels, styles, templates, and so on.

  • The Items tab displays non-graphical business data in a DGN file in hierarchical order.

  • The Resources tab displays resources used in a DGN file in hierarchical order.

  • The SheetIndex tab allows you to manage sheet indexing. A sheet index is an organized and named collection of sheet models from one or more design files.

  • The Links tab can be used to see the linked data.

In this 5-part blog series, we will take a closer look at each one of these tabs and the capabilities, functionality and the role each one plays.  In the meantime, it is worth covering some of the different options for the Explorer dialog.

You can access this dialog from the Ribbon: File > Settings > User > Explorer Settings.  Remember, the integrated Ribbon Search can also locate and open dialogs and tools by simply type part or all of the name of what you are looking for.

The Explorer Settings controls many different settings, but, in short, it allows you to show or hide each of the tabs, and rather to show or hide individual related items within each respective tab.  In addition, it allows you enable or disable the setting for DGN Indexing.  More on that, later.

So, as mentioned above, over the next series of blogs on the Explorer, you’ll get a better understanding of the capabilities, functionality and the roles that each tab has.  From the different types of links available to target your project data, and what Link Sets are.  How easy and intuitive it is to setup a project with Explorer.  Display resources used in a DGN file or what is available from the DGN Library files.  Expose and aggregate non-graphical business data in a DGN file or reference.  Being able to browse and manage the file content from models, references, saved views, levels, styles, templates, and so on.  Manage sheets to create a construction document set.  And we’ll learn how Explorer allows for integration with other dialogs such as Print Organizer.

More importantly, at the end of this blog series, you will understand just how powerful of a tool that the Explorer really is, within MicroStation.  It allows you to explore (pun not intended) more interactively, resulting in higher quality of designs through improved coordination of project data.  You can think of Explorer as a hyper-linked table of contents to your project data…

The Explorer – Part Two: The File tab

$
0
0

In Part Two of the Explorer blog series, we will take a closer look at the Explorer dialog, File tab.

Browsing and Managing File Content

The File tab displays file content in categories such as models, saved views, references, levels, and so on.

File content can be browsed and managed by displaying the following content:

Browsing and Managing Model Content

You can also view the content of the active model. The model content includes saved views, levels, named groups, rasters, point clouds, references, elements, and so on. The model content is displayed by expanding the active model under the Models category. You can view the content of the active model only.

Right Clicking Categories

Expanding each category within the File tab, such as models, saved views, references, levels, and so on, lists items within that category or further sub-categories.  Here you will discover that there are numerous capabilities when right-clicking on items.   For instance, you can manage the file content displayed in the Explorer File tab in the following ways:

  • Right-clicking a category — You can select a menu item from the pop-up menu to perform actions on the file. For example, if you right-click the Models category you see Manage, New, Properties and Import. Selecting Manage opens the Models dialog.

  • Right-clicking an item within a category — You can select a menu item from the pop-up menu to perform actions on the selected item. For example, if you right-click a saved view within the saved views category you see Apply, Rename, Update, and Delete. Clicking Properties opens Properties dialog in which properties of element appear.

And not limited to the Properties dialog, but selection of the objects in Explorer dialog are synchronized to the selection of the corresponding objects in various modeless dialogs.

  • Right-clicking the Elements category — You can select Organize By to organize the elements in the list by Type, Name, Level, Color, Style, Weight, Class, Template, Transparency, and Priority.

  • Right-clicking an Element — When you right-click an element in the Elements category you see menu items related to the element type. For example, in the image below, here you can see a Text element has been right-clicked.  The contextual menu displays Manipulation commands like Copy, Move, Scale, etc.  Text editing commands, and so on.  Options found in the contextual menu are completely dependent from the element that was right-clicked and will vary.

  • Double-clicking a category — Expands or collapses the category.
  • Double-clicking an item within a category — Activates or opens the item, if possible. For example, double clicking on existing model will open the model.
  • Drag-and-drop operation — You can drag saved views and models (from the Models and Saved Views categories, respectively) into the view window. You can drag a model into a view window to attach it is as a reference in the active model. Similarly, you can press <Ctrl> and drag a model into a view window to place it as a cell or press <Alt> and drag a model or saved view into a view window to place it as a link on an element.

When you drag a model, saved view, model link, or saved view link from the Models, Saved Views, or the Explorer dialogs, the corresponding model or saved view is attached to the active file, the Reference Attachment Properties dialog opens so that you can make the required reference settings.

File Tab Icon bank

The icon bank provides the following functions:

  • Refresh Active Tree refreshes the active tree to reflect changes to the DGN file.
  • Transparent turns on the transparency for selected graphical items.
  • Zoom will zoom to the selected graphical items.
  • Isolate will isolate the selected graphical items.

Performing Searches

In the File tab – and as we’ll see later – the Items, and Resources tabs of the Explorer dialog, you can search for objects within the tree. Based on the requirements, you can either perform a Simple search, Criteria search, or an Advanced search.

  • Simple searches allow you to conduct a search based on searched text.
  • Criteria searches allow you to create simple queries.
  • Advanced searches lets you build complex search conditions that can be saved for later use. Search results are stored in a folder that is named after the search condition. From the right-click menu of the search results folder you can save the results as report definitions (only for Criteria and Advanced search), edit search criteria, delete search criteria, or view properties.

So, as you can see, the File tab is a great way to browse and manage the content of the file.  It is a central location where normally you would have to investigate perhaps multiple dialogs the information you are looking for.  For instance, what levels are being used in the active model.  Or how many Drawing Boundaries there are in the model.  Or even what references are attached – and their content, as well. 

Next in Part Three of the Explorer blog series, we will take a look at the Items tab.  If you were familiar with the Item Browser dialog in previous versions of MicroStation, then it has been merged into the Explorer dialog.  The Items tab displays a list of folder-like nodes representing the “item types” which is the non-graphical, business data behind the graphical elements.

What's New in LEAP Bridge Concrete CONNECT Edition V18 Update 2? (October 29, 2018)

$
0
0

LEAP Bridge Concrete (LBC) CONNECT Edition V18 Update 2 (v18.02.00.12) with CONNECT Licensing is now available to all users on Bentley Software Downloads. This release contains enhancements and bug fixes. The main enhancements are summarized below.

  • State spec option for Nebraska
    LBC now supports the customized configurations, including the live load factor for the Strength Limit State I and the tension limit for Service Limit State III per Nebraska DOT’s practice.
  • Extended improvement concurrent shear/Torsion
    Finding the controlling case of the concurrent shear and torsion when the max shear is corresponding to multiple concurrent torsion or the max torsion is corresponding to multiple concurrent shear is now supported.
  • Extended FLS check per LRFD 8th Edition
    Updated the load factor of the live load for the Fatigue Limit State I for all the LBC modules.
  • Extended improvement of live load report
    Added the echo of user’s input into the detailed live load report to improve the user’s friendliness. Added a label differentiating the bearing loads due to truck from those due to lane.
  • Extended improvement on stepped cap pier
    The self-weight of steps is now included in the analysis and design.
    LBC now supports manual revision of the dimensions of autogenerated steps.
  • Manual input of moment for column loads
    LBC now supports moment as a load type input for pier column. This brings more flexibility to allow users to define complex loads for both column and footing design.


For the detailed release notes, see the attached PDF file.

CONNECT Licensing

This product version utilizes CONNECT Licensing, which is not supported by SELECT activation key(s). CONNECT Licensing features new behavior to enhance your organization’s user administration and security with mandatory user sign-in via CONNECTION Client to access the application. If you are already signed in to the CONNECTION Client, you have met this prerequisite. If you have not, please refer to the Administrator's Resource Center and/or contact your administrator for assistance in the registration and sign-in process. For more information about working with the Update service, visit the Update Infrastructure SharePoint page.

What's New in LEAP Bridge Concrete CONNECT Edition V18 Update 2? (October 29, 2018)

$
0
0

LEAP Bridge Concrete (LBC) CONNECT Edition V18 Update 2 (v18.02.00.12) with CONNECT Licensing is now available to all users on Bentley Software Downloads. This release contains enhancements and bug fixes. The main enhancements are summarized below.

  • State spec option for Nebraska
    LBC now supports the customized configurations, including the live load factor for the Strength Limit State I and the tension limit for Service Limit State III per Nebraska DOT’s practice.
  • Extended improvement concurrent shear/Torsion
    Finding the controlling case of the concurrent shear and torsion when the max shear is corresponding to multiple concurrent torsion or the max torsion is corresponding to multiple concurrent shear is now supported.
  • Extended FLS check per LRFD 8th Edition
    Updated the load factor of the live load for the Fatigue Limit State I for all the LBC modules.
  • Extended improvement of live load report
    Added the echo of user’s input into the detailed live load report to improve the user’s friendliness. Added a label differentiating the bearing loads due to truck from those due to lane.
  • Extended improvement on stepped cap pier
    The self-weight of steps is now included in the analysis and design.
    LBC now supports manual revision of the dimensions of auto-generated steps.
  • Manual input of moment for column loads
    LBC now supports moment as a load type input for pier column. This brings more flexibility to allow users to define complex loads for both column and footing design.


For the detailed release notes, see the attached PDF file.

CONNECT Licensing

This product version utilizes CONNECT Licensing, which is not supported by SELECT activation key(s). CONNECT Licensing features new behavior to enhance your organization’s user administration and security with mandatory user sign-in via CONNECTION Client to access the application. If you are already signed in to the CONNECTION Client, you have met this prerequisite. If you have not, please refer to the Administrator's Resource Center and/or contact your administrator for assistance in the registration and sign-in process. For more information about working with the Update service, visit the Update Infrastructure SharePoint page.

A Discussion on the OMEGA Option in Equilibrium Calculations in MOSES

$
0
0

Overview

This document presents a discussion on the -omega option that is part of the &EQUI command. The &EQUI command in MOSES computes a static equilibrium position with a modified Newton method.  Also presented is an example when the -omega option in the &EQUI command is used to reach equilibrium.

Basic Theory

You can find a good description of the Newton method on Wikipedia.  The article in Wikipedia shows a sample of a single curve with one x-axis intercept.  The x-axis intercept is found after various tangent lines are calculated.  In our engineering world, the curve represents the force and moments at various positions and the tangents represent the stiffness of the system at each position.  The method presented works very efficiently for a single curve.  In the offshore world, bodies have six degrees of freedom.  There are at least six curves f(x), f(y), . . . f(rz) needed.  The axis we are interested in intercepting is the one represented by all forces and moments equal to zero.

In an ideal world, one would find the position where the forces and the moments equal zero.  The tangent lines would find a position where all six degrees of freedom intercept the axis.  Since this is an iterative method, it can be very time-consuming and thus inefficient, but there are options to help with efficiency.  The tolerance option is unique, and it controls how close to zero the forces and moments must get for the iterative process to stop.   The other options control the size, or distances, between each iteration.  This work discusses the omega option which controls the calculation of the tangent lines in the Newton method. 

A modified Newton method is used on the force and moment curves vs. position.  These curves will include any non-linearities due to hydrostatic stiffness and connectors.  Non-linearities in hydrostatic stiffness can be due to changes in shape.  Connectors such as catenary mooring lines are non-linear.  When there are several degrees of freedom to consider one cannot calculate the curves at all possible positions before starting the iterative process.  One method to get around this is to compute the tangent at each iteration from the change in forces and moments from the previous position.  For a change in position that does not result in a change in forces and moments, the tangent is flat.  For a change in position that changes forces and moments drastically, the tangent is near vertical. Depending on the offshore procedure being analyzed, there can be one or more curves that result in tangent lines that do not get the solution near the axis intercept. In these cases, the other &EQUI options can help.

Heave, roll and pitch motions are normally well behaved for an analysis of a single floating body without mooring lines.  Since there are no restraints in the surge, sway, and yaw motions the tangents for those curves could be flat.  Another example would be a barge moored to a quay with fenders and mooring lines.  For analysis with several fenders where not all fenders are engaged at each position, the non-linearities can cause the tangent to be almost vertical.  To avoid possible singularities in the stiffness matrix, MOSES augments the stiffness with a fraction of the inertia.  The equation used for stiffness is:

In the above examples, for an analysis of a single floating body, omega defaults to 0.2236.  For the example where flexible connectors are used, omega defaults to 0.0236. In essence, the stiffness is augmented with a fraction of the inertia.  

Sample Problem

Here an example where a change in omega is needed is reviewed.  For this example, the up_damage sample files are used as found in ..\hdesk\runs\samples\how_to directory. A training exercise is also based on this set of files; please contact support@bentley.com for a copy. 

The files model three compartments in a three-legged jacket.  The analysis files use the time domain to flood compartment Three and find an equilibrium position with the flooded leg.  In this example, the &EQUI command is used to find the new equilibrium position.  Reviewing the geometry, one would expect the flooding of compartment Three to rotate the jacket such that compartment Three is lowest in the water, or nearer to the seabed.  One also expects a pitch angle since the jacket buoyancy properties are not evenly distributed.  The jacket undamaged free-floating position is shown in Figure 1 and Figure 2.  The jacket in the equilibrium position after damaging compartment Three is shown in Figure 3 and Figure 4.

Figure 1: View from jacket top elevation in undamaged floating position (Click picture for larger view)

 

Figure 2:  View showing face floating on water plane in undamaged floating position (Click picture for larger view)

Figure 3: Side view of damaged floating position – Compartment Three is flooded (Click picture for larger view)

 

Figure 4:  View from jacket top elevation for damaged floating position – Compartment Three is flooded (Click picture for larger view)

The calculations presented here find equilibrium with the &EQUI command and three different values of omega: 0.1, 0.2236 and 0.6.  The default value of 0.2236 will be referred to as “default.”   The intent is to show a value smaller and a value larger in comparison to the default value. The files monitor the heave, roll, and pitch position at each iteration.  Plots showing the position vs. iteration are shown below in Figure 5 to Figure 7.  These plots also show the time domain results.  Plots showing the change in position vs. iteration are shown in Figure 8 to Figure 10.  A total of 150 iterations are shown.  The plots show the equilibrium position for omega = 0.6 and the time domain results agree.

In Figure 5 to Figure 7, one can see that for the default value and omega = 0.1 value plots, the trace oscillates.  This oscillation will be called chatter.  For roll, Figure 6, and pitch, Figure 7, the results for omega = 0.1 are farther from the solution in comparison to the default omega.  Reducing the omega value caused the solution to be farther from the solution.  The chatter is amplified in Figure 8 to Figure 10. 

Chatter usually implies the slope of the tangent is overestimating the next step.  The overestimate results in a reverse-overestimate to compensate the prior step.  This constant overestimate results in the chatter.  To exit the chatter a different step between the iterations is needed; however, we do not know how the step size.  Not knowing the step size, makes finding a different step size difficult.

The other &EQUI options let the user specify the step size, whereas the omega option lets the program change the step size depending on the stiffness calculations.  The omega option eliminates the need to know the step size. An increase in omega will decrease the step size.  Taking the recommendation, we should increase the value of omega.  It is evident that increasing omega to 0.6 results in a smooth curve without any chattering.  This is shown in figure 5 to 7, position vs. iteration. 

Instead of chattering, oscillations, the motion could show values that move without a definite convergence.  Motion without a convergence will be referred to as wandering. Wandering is common in systems with mooring systems or other connectors. For a system that is wandering a decrease in omega is the recommended action.  A decrease in omega will decrease the dependence on the mass properties and increase the dependence on the connector stiffness.  The default omega for systems with connectors is 0.02236.  The default for systems with connectors is a factor of ten smaller in comparison to systems without connectors.  The default for systems with connectors is ten-squared times less dependent on the mass properties in comparison to systems without connectors. 

Lastly, it is worth comparing the results to those obtained in the time domain.  Another method of finding equilibrium is via the time domain.  We see in Figure 5 to Figure7 that the time domain results and the omega = 0.6 are converging on the same values.  The convergence to the same values lends confidence in our results. 

 

Figure 5: Heave position vs iteration (Click picture for larger view)

Figure 6:  Roll position vs iteration (Click picture for larger view)

 

Figure 7: Pitch position vs iteration

Figure 8:  Change in heave position vs iterations (Click picture for larger view)

Figure 9:  Change in roll position vs iterations (Click picture for larger view)

  

Figure 10:  Change in Pitch position vs iterations (Click picture for larger view)

Summary

In summary, for multi-body, procedures with connectors, or procedures with an unrestrained degree of freedom the static equilibrium can be difficult to find.  MOSES offers the omega option to increase efficiency.  It would be difficult to recommend specific values since stiffness is problem-specific and relative to the mass of the bodies and the stiffness of the connectors in the analysis.  We hope the example used here is helpful.

Download the PDF of this article!

gINT CONNECT Edition 10.00.00.69 (English, Chinese traditional, Chinese simplified) has been posted to Select Services


What’s New in LEAP Bridge Steel CONNECT Edition V18 U2?

$
0
0

LEAP Bridge Steel CONNECT Edition V18 U2 contains following minor enhancements and bug fixes:

Enhancements

• Transfer of appurtenances from OBM
• Transfer of cross-frame connection plates from OBM


Bug Fixes
This release fixes a few issues including:

• Error in field splice design per LRFD-8 regarding tension yielding on net section
• Error in field splice design per LRFD-7 regarding the calculation of web splice plate width
• Malfunctioning of wind load dialog box when “User Input” is selected
• Defect at rating reports where zero flexural rating factors are reported at supports (instead of infinity)

Note:This product version utilizes CONNECT Licensing, which is not supported by SELECT activation key(s). CONNECT Licensing features new behavior to enhance your organization’s user administration and security with mandatory user sign-in via CONNECTION Client to access the application. If you are already signed in to the CONNECTION Client, you have met this prerequisite. If you have not, please refer to the Administrator's Resource Center and/or contact your administrator for assistance in the registration and sign-in process.

For the detailed release notes, see the attached PDF file.

What’s New in LEAP Bridge Steel CONNECT Edition V18 U2?

$
0
0

LEAP Bridge Steel CONNECT Edition V18 U2 contains following minor enhancements and bug fixes:

Enhancements

• Transfer of appurtenances from OBM
• Transfer of cross-frame connection plates from OBM


Bug Fixes
This release fixes a few issues including:

• Error in field splice design per LRFD-8 regarding tension yielding on net section
• Error in field splice design per LRFD-7 regarding the calculation of web splice plate width
• Malfunctioning of wind load dialog box when “User Input” is selected
• Defect at rating reports where zero flexural rating factors are reported at supports (instead of infinity)

Note: This product version utilizes CONNECT Licensing, which is not supported by SELECT activation key(s). CONNECT Licensing features new behavior to enhance your organization’s user administration and security with mandatory user sign-in via CONNECTION Client to access the application. If you are already signed in to the CONNECTION Client, you have met this prerequisite. If you have not, please refer to the Administrator's Resource Center and/or contact your administrator for assistance in the registration and sign-in process.

For the detailed release notes, see the attached PDF file.

Setting Up in the Real World - Solids Working Area Tools

$
0
0
Coming soon; here's a teaser for Update 4: AECOsim Building Designer CONNECT Edition Update 4 includes new tools relating to the Solids Working Area (SWA). The importance and use of the SWA has been discussed in detail in previous articles in this series. The new tools highlight the importance of the SWA when working with AECOsim Building Designer and will help to avoid some of the problems that arise when working outside the SWA. When a file con...(read more)

New in MicroStation CONNECT Edition Update 11: Perforators (Technology Preview)

$
0
0

MicroStation CONNECT Edition Update 11 introduces an exciting new feature: Perforators (Technology Preview)

Functional Components get smarter, taking 3D parametric modeling a step further. 

 

When creating a parametric cell, you can now tag one or more parametric solids as "perforators" so that these will perforate their target solids when placed in a dgn file.

communities.bentley.com/.../2500.Define-Perforator-_2D00_-Pipe.mp4

 

Making a solid a perforator is very simple, you only need to select the "Define Perforator" button in the "Content" Ribbon Group, then select the solid you want to be a perforator and accept. 

There is an option to hide a perforator after placement, which means the perforating solid will not be shown in the dgn file after having perforated their target solid.

The perforation is associated with the parametric cell instance so that it will follow the cell if this is moved and deleted in case the cell is deleted.

A parametric cell with one or more perforators can be applied to parametric and smart solid, in the latter case the smart solid will be upgraded to a parametric solid in roder to maintain the dependency.

communities.bentley.com/.../3157.Perforators-Placement-_2D00_-Pipe.mp4

A parametric cell can contain multiple perforators, each one with its own "show/hide after placement" setting.

As this is a Technology Preview feature, remember that it is still not to be used in production environment or data and pelase share your feedback with us!

New in MicroStation CONNECT Edition Update 11: Named Presentations (Technology Preview)

$
0
0

MicroStation CONNECT Edition Update 11 introduces an exciting new feature: Named Presentations

Named Presentations is a new MicroStation feature that lets you define a different representation of your components to be displaid in a particular view orientation, so that only the specified graphics will be shown in the assigned view orientation.

Named presentations works with parametric cells but the geometry doesn't need to be parametric or 2D/3D.

Setting up Named Presentation is very easy, you need to open the feature dialog, click the "Add" button and then tick the view orientation in which you want to display a particular set of geometry. Then simply select the geometry and accept. 

communities.bentley.com/.../3240.Door-with-Named-Pres.mp4

You can use the dialog to easily filter the geometry to display while eidting your component and to add/remove graphics to each presentation.

communities.bentley.com/.../0564.Door-with-Named-Pres_5F00_-Edit.mp4

You can also turn on or off Named Presentation display for each view from the View Attributes dialog, very simply.

communities.bentley.com/.../6445.Door-with-Named-Pres_5F00_-on_2D00_off.mp4

As this is a Technology Preview feature, remember that it is still not to be used in production environment or data and pelase share your feedback with us!

New in MicroStation CONNECT Edition Update 11: Item Types - Excel Interops (Technology Preview)

$
0
0

MicroStation CONNECT Edition Update 11 introduces an exciting new feature: Item Types Import/Export from/to Excel

With MicroStation CONNECT Edition Update 11 you can now import/export both your Item Types definitions and instance data from/to Excel. 


Being able to export and import Item Types' instance data to Excel means that you can now edit all the properties of your item types instances and have them updated in the dgn file by simply reimporting the amended Excel file.

You can export instance data from All item Types in a dgn model or only from instances in your current selection or those included in a fence.

You can also now define your item types libraries in Excel and have them created in a dgn by importing the Excel file. you can do this by first exporting a sample Item Type library to Excel and then use the exported data as a template for creating your complex libraries.

As this is a Technology Preview feature, remember that it is still not to be used in production environment or data and pelase share your feedback with us!

New in MicroStation CONNECT Edition Update 11: Extract Associative Elements (Technology Preview)

$
0
0

MicroStation CONNECT Edition Update 10 introduces a new exciting 3D modeling feature:

The Associative Extraction of Edges and Faces.

This tools lets you extract edges and faces from parametric solids keeping associativity with their parents elements.

The new Associative Extraction Tool works pretty much as the standard Extract Tool, it only adds a few more options, including Offsetting the extracted associative face and a couple more behavioural settings.

communities.bentley.com/.../Associative-Elements.mp4

These new "Associative Elements" can then be used as input elements for new parametric features, allowing you to drive very complex models with just a bunch of variables or pieces of geometry.

communities.bentley.com/.../Associative-Elements-2.mp4

As this is a Technology Preview feature, remember that it is still not to be used in production environment or with production data.

As always we value your opinion and greatly welcome your feedback!


MicroStation SDK sample- DimensionExample

$
0
0
Introduction ‘DimensionExample’ showcases the CRUD capabilities of the Dimension API What does the example demonstrate? The example describes the use of Dimension API to: Create a linear dimension on an element Create a linear dimension between two points Delete dimensions Modify the dimension text Read the dimension value To run the Example Load the ‘DimensionExample’ application using either keyin- mdl load dimension...(read more)

How to create a Parametric Feature Tree

$
0
0
Introduction Parametric Feature is powerful way of creating complex geometry associatively. Various parametric features can be combined to form a chain; often called as a feature tree. What does the example demonstrate? 'Parametric Feature Tree Tool' app demonstrates how to create a complex chain of Parametric Features programmatically. To run the Example Load the 'Parametric Feature Tree Tool' application using either ...(read more)

New in MicroStation CONNECT Edition Update 11: Configuration Assistant (Technology Preview)

$
0
0

The Configuration Assistant is designed to help a CAD Manager quickly create a CONNECT Configuration so they can re-use the CAD Standards from previous versions. The main purpose is to convert V8i WorkSpaces to CONNECT Configurations. The ability for a CAD Manager to use automated tools to create a CONNECT Configuration will allow them to start using CONNECT Edition products more quickly. One of the obstacles to upgrading to CONNECT is having a working configuration as we changed: variables, folder structures, configuration levels and files. The Configuration Assistant provides a tool to help easily create a CONNECT configuration.

The Configuration Assistant tool would allow CAD Managers to:

  • Create a Configuration by cloning a V8i Workspace standard
    • Use V8i WorkSpace folder structure and create clone (separate, but similar) folder structure for CONNECT Edition
    • Create configuration files to support folder structure [based on V8i]
    • Option to use UCFs and/or PCFs and be converted
      • UCFs to WorkSpaces and PCFs to WorkSets
      • Allow multiple PCFs to be converted at once
    • Advanced version of the Configuration Migration Wizard

The entry point is in the WorkSpace menu on the Work Page.

This opens the Configuration Assistant.

You first select the version and V8i WorkSpace you wish to convert. Then you can select if you want to have it copy/clone (Configuration with data files, most common use case) or have the new CONNECT Configuration point to the original V8i WorkSpace (hybrid of V8i and CONNECT pointing to the same WorkSpace/CAD Standard, not as common).

Next the you get the choice of what V8i Users and Projects to convert to CONNECT WorkSpaces and WorkSets.

 

Then you select the destination of the new CONNECT Configuration. You can select a local drive or a server drive.

Upon completion you can update your _USTN_CUSTOM_CONFIGURATION variable, which is the most common thing to do, then you can try your newly migrated CONNECT Configuration with any Bentley Power Product.

Finally, a report is generated giving a summary of the migration process and if it succeeded or failed.

Flow idea #2: Maintaining Deliverable List using Flow

$
0
0

This example flow demonstrates how to create ProjectWise document with a document code. It also shows how to use Excel spreadsheet for additional data and how to handle error situations without stopping flow execution.

Note that this flow example is a suggestion for ideas how to use Flow connector. It is not meant to provide the ultimate solution deliverable management using Bentley tools.

Scenario

Let’s imagine here is an Excel spreadsheet that serves as a deliverable registry. It is also used to track deliverable progress as percent complete.

Document controllers need to create deliverable documents without files in a project when new deliverables are identified, or a project is initially seeded. Also, they need to update percent complete in the spreadsheet every day. It is a time-consuming activity, so an automation would help!

For our example the spreadsheet looks like this:

The ID column is used for identification of rows by Excel Flow connector. In this eample ID column has a formula =row() to ensure that each row has a unique value in it.

The flow

The flow runs automatically every day at 10 am. Document controller used built in Flow recurrence trigger. See Variations chapter about other options to trigger this flow.

Then flow reads the spreadsheet stored in Microsoft Teams using Excel Online (Business) connector.

 

The next part of the flow is a loop through the returned rows to process each. (Flow adds Apply to each automatically when action references a property from a list of items).

Processing each row

The Status column in spreadsheet defines what action will be taken:

  • If column value is ‘New’ then flow will create a new document, record document name to spreadsheet and change Status to ‘Created’.
  • If column value is ‘Created’ then flow will update Percent Complete column form document attribute.

Inside the loop there is a Switch statement that controls the flow:

 

Create a new document

The first Case is for creating a new document when Status is ‘New’:

 

Document controller wants to generate document number for the document and then use it as name of the document. This is achieved in two steps: first a document is created with a temporary name in the discipline folder:

 

The document number is generated by ProjectWise when all attributes making document number are specified. The attributes values are taken from deliverable spreadsheet:

 

Note: to set serial number, you will need to remove read only flag in Complex environment via ProjectWise Administrator or else it will not be displayed in Flow. Note this change will not make it editable in ProjectWise interface because it is part of document code.

Once document is created, the Document Number will be known. Now the second step will rename the newly created document using the document number.

Document GUID from creation step is used to identify the new document.

Note that actions to create or modify document return attributes as they are in datasource after the action was completed. So, for example, if some attributes have default values then they will be returned after creation even if inputs were empty.

The last step in creation case is to update spreadsheet. Not the use of ID column for row identification. See the beginning of this article for how unique ID is ensured.

 

Updating Percent Complete

The second case will be executed if document already exists. In this case it will use Find document by Path or GUID action to retrieve document attributes and write percent complete value into spreadsheet:

Handling Errors

The last step in this Flow demonstrates a simple error handling technique. It may happen so that spreadsheet contains information that is out of sync with ProjectWise datasource. For example, existing deliverable document may be renamed, or new document attribute combination may produce a combination that was already used before. Usually when any action in flow fails the whole flow will fail. In this case Document Controller wants Flow to record failure and continue processing other rows.

To record the processing error update row action like this was added after switch statement:

Then it was configured to run only if an error occurs within Switch by setting ‘Configure run after’ options:

Then:

Variations

This flow is triggered on schedule. Here are other options that could be used to run a flow. Since this flow does not require inputs, essentially any trigger that could correlate to changes in deliverable list could be used.

Here are some trigger examples:

Deliverable Spreadsheet can have more columns and more actions not only creating new or reading percent complete.

The flow can be re-purposed for other situations when a spreadsheet could be used to maintain a set of documents in a convenient excel interface.

 

The Explorer – Part Three: The Items Tab

$
0
0

So far in our blog series on the Explorer, found within the MicroStation CONNECT Edition, we did an overview of the Explorer in Part One.  In Part Two, we talked about the capabilities of the File tab, which allows you to display the content of the file such as models, saved views, references, etc.  Here in Part Three of the Explorer blog series, we will take a closer look at the Explorer dialog’s Items tab.

Now, a typical DGN file contains graphics, and of course, those graphics are displayed in the model.  However, behind the graphics, there may be business data.  Business data is the real-world information associated with the items represented by the graphics in the model. 

In MicroStation V8i, to view this business data, you needed to utilize the Items Browser dialog.  The Items dialog showed a list of folder-like nodes representing the “item types” of the business items present in the DGN file. These Class Type nodes group the items by type, and when you expand them, you can see the individual “items” (component instances) contained in the DGN file.

(Item Browser from V8i)

With the MicroStation CONNECT Edition, the Item Browser dialog that you may have been familiar with in V8i has been merged into the Explorer dialog.  The Items tab within the Explorer, lists business items contained in a DGN file. Items are listed within groups that can be expanded or collapsed to see the individual items. Clicking the item selects the item in the current view. Likewise, selecting a group name selects all the items in that group. The expanded group is known as the active tree.

(The Explorer: Items Tab)

 

Items Tab Icon Bank

You can view items in your model by setting Zoom, Isolation or Transparency.  The icon bank provides the following functions:

  • Refresh Active Tree – refreshes the active tree to reflect changes to the DGN file.
  • Transparent – turns the graphics that are not associated with the selected items invisible. Selected item(s) remain opaque.
  • Zoom – will zoom to the selected items.
  • Isolate – displays only the selected item’s graphics. All other graphics are hidden.

In the architectural example, from the Items tab, we’ll expand the Doors.  Then when we select a particular instance in the Doors listing, we can see that selected item is highlighted (the handles can be disabled) within the view.

  

 The Items tab view tools can be toggled individually or any particular combination.  Here, we’ll begin by toggling on the Transparency view tool.

When you turn on Transparency, the entire model is rendered in transparent white with the selected item in its selection set color (design file settings).

With Zoom, the view zooms to the selected item in the model. In this example below, only Zoom was toggled on.  As you can see, view zooms into the selected door while the view is rendered in its original color.

  

And when Isolation mode is toggled, it displays the selected item apart from the rest of the graphics in the model.

Right-click Options

Right-clicking a selected Item(s) will provide the following:

  • Zoom – will zoom to the selected items.
  • Isolate – displays only the selected item’s graphics. All other graphics are hidden.  Both Zoom and Isolate work independently from the View Controls from the icon bank of the Items tab.
  • Clear Isolate – will remove/undo the display set created by the Isolate command, restoring the all the graphics in view to their previous view state.
  • Details – will open the Details dialog. This used to display information related to what is selected in any of the tabs of the Explorer dialog in a tabular format.  The information displayed, in some cases, can be edited and can be saved. There is a right-click menu that allows for finding or copying information, editing, and saving (see image further below in criteria search demonstration).
  • Properties – will display the Properties dialog and is used to review or modify the properties of the selection. The Properties dialog can be used to edit properties of data that have write permissions. This can include files, items, or elements (see image further below in criteria search demonstration).

 

Performing Searches

In the Items tab – just like we saw in the File tab and as we’ll see later in the Resources tab of the Explorer dialog, you can search for objects within the tree. Based on the requirements, you can either perform a Simple search, Criteria search, or an Advanced search. In short:

  • Simple searches allow you to conduct a search based on searched text.
  • Criteria searches allow you to create simple queries.
  • Advanced searches lets you build complex search conditions that can be saved for later use.

But let’s take a deeper look at performing searches.  In our first example of the types of searches you can perform, we will do a Simple Search.  In this case, we want to look up a furniture item.  We know the ID number of the piece of furniture and as such, we’ll type that into the Search field.  Here we’ll type, “374719” and click the Search icon or simply hit the Enter key.

Search results are stored in a folder that is named after the search condition at the bottom of the listing.   As shown below, the search netted 1 result.  In the example, the Zoom was toggled, and hence, the furniture item is located within the building.

To perform criteria search, we first need to click the Expand the Query Builder icon. 

The Add Criteria button then displays. From here, we need to type or select the item or property name for which we want to create the criteria.  In this case, we want to search for single-flush doors.  So, we’ll expand Doors and then select, Family. 

Next, we’ll need to enter the partial or complete value for search.  In this case, we’ll type Single-Flush into the field, and then click the Search icon.  Results display in search folder that is named after the entered condition.  As you can see, the search netted 10 single-flush doors.  In our example below, Transparent was toggled on.

From the right-click menu of the search results folder, you can save the results as report definitions (only for Criteria and Advanced search).   You can save the search result as a report and place a table from the report.

In addition, from the right-click menu, you can edit or delete the search criteria. You can view the results in the Details dialog as shown here.

And as well, view the results from the Properties dialog, as shown.

As another example of performing a Criteria search, here we are looking for double glass doors.

In our last example, we wish to perform a search for multiple types of items.  In this case, the building’s HVAC system.  In order to do this, we must perform an Advanced search.  To begin, we need to click Show Advanced Search Dialog icon.  Then from there, the Advanced Search dialog will open.  In the Search For field, we need to click the drop-down list box.  And then from there, select the option, Multiple types of items.

The Add or Remove Items dialog will open.  From here, we’ll select Air Terminals, Duct Fittings, Ducts, Flex Ducts, and Mechanical Equipment.

Once finished selecting the items to add, clicking OK returns you back to the Advanced Search.

At this point, we are finished building the search because we want to include all of the items.  It is possible to refine this search further within the dialog by setting conditions and/or criteria.  So, with that, we’ll go ahead a perform the search by clicking OK.

Just like before, the results display in search folder that is named after the entered condition.  As you can see, the search netted 388 items.  Expanding the search, you can see a further break down of the items in groups. 

In our example below, Transparent was toggled on.

In next image -- to show the search results in a different manner, the view toggles from the Items tab were toggled off and a display set created to isolate the results.

Again, just like you can from Criteria searches -- the right-click menu of the search results folder allows you to save the results as report definitions for Advanced searches, as well.

So, more and more, applications like OpenRoads, or AECOsim, and so on, can write business data to your graphics.  Even now, the MicroStation CONNECT Edition can write business data (i.e. user-defined properties) to your graphics.  All in all, graphics are starting to have more and more intelligence beyond what you just see in the model.  And as such, as you just saw, the Items tab provides a great way to expose those business items can contain in a DGN file.

Next, in Part Four of the Explorer blog series, we will take a look at the Resources tab.  The Resources tab displays common resources being used by a DGN file. Common resources include DGN library files and the active file.

Viewing all 4567 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>