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

Announcement of upcoming Bentley Manage Services Patch Weekend - 11 to 13 January 2019

$
0
0

This is a reminder of our upcoming regularly scheduled patch and maintenance weekend - January 11 thru 13th for Bentley ProjectWise Managed Services. We apologize for any disruption in service you may possibly see but the maintenance of your servers is pertinent for system health and security.

 

Microsoft releases its security patches on the second Tuesday of each month. Bentley Managed Services patches all hosted servers on the following weekend during non-business hours per the location of the hosted servers. Please view the Microsoft Security Updates site for the release notes for this month's patching. 

 

During each patch weekend, Bentley strives to keep the planned outage to 30 minutes or less per server farm (FQDN).

 

 Region

Locations

Day

Est Start Time

Asia Pacific

Asia, Australia, India, and Japan

Friday

13:00 UTC

Europe

Europe including the United Kingdom

Friday

19:00 UTC

Americas

Brazil, Canada, and the United States

Saturday

14:00 UTC

All

Sunday

As needed during non-business hours for that datacenter's location

 

 

To see a schedule of all 2019 patch weekends, please see the Bentley patch calendar  located within the Bentley Communities ProjectWise Hosting Services web site.


Critical Defect in OpenBridge Modeler CONNECT Edition - 2018 Release 3, v10.06.00.41

$
0
0

We have discovered a critical issue in the recent November 2018 release version of OpenBridge Modeler CE, which we would like to bring to your attention.

Note: This issue also affects the OpenBridge Designer CONNECT Edition product line, which includes this build of OpenBridge Modeler.

When working with US/Imperial units, the slope and angle constraints for any deck are not being modeled accurately. This affects all bridge decks including P/S Girder Bridge type, Steel Bridge type, Segmental and CIP Box Girder. The slope constraint is incorrectly reduced by a factor of 3.28 before it is applied. So a 2% slope is actually modeled with a 0.609% slope, leading to incorrect deck elevations and affecting layout of all other bridge elements under the deck. As a temporary workaround, user's can input a modified slope, multiplied by a factor of 3.28 to workaround this issue.

We apologize for this error, and are working to fix and issue a new build.
If you need further information, please contact our  technical support team.

Microsoft update for January 8 prevents users from being able to open a gINT project

$
0
0

Dear gINT Users,

Microsoft released a patch on Tuesday January 8.  Items in that patch will make the gINT database un-recognizable, and you will not be able to open gINT.

At this time we do not know the specific item in the patch, but we are working on things. This has our highest priority.

The error is non version specific for gINT.

Please watch this space for updates and information. We will be forth coming with more details as we find them.

Regards,

Katie

Katie Aguilar, PE

Product Manager I

katie.aguilar@bentley.com

Simple Quantities in the MicroStation CONNECT Edition

$
0
0

In today’s ever increasingly complex AEC work environments, drawings often contain a mixture of both graphical and business data. Graphical data is the design geometry represented in a drawing. This can be made up of simple lines, curves, and polygons or more complex solids, surfaces and meshes. This graphical data may also include text, dimensions and notes. Business data is the real-world information associated with the items represented by the graphics in the drawing.

If you consider a DGN model representing a facility, the facility can be made up of pumps, vessels, valves, pipes, and so on. These items can be represented graphically but may also have related business data defining their nongraphical properties. Examples of nongraphical properties may include a part number, manufacturer, material, identification number, pressure rating and so on.

Why is this useful? Business data can be obtained from a variety of sources, including the following:

  • MicroStation: Created in MicroStation.
  • Supplied by a vertical application such as OpenRoads Designer or AECOsim Building Designer.
  • Brought in from outside sources such as geographic shapefiles or Industry Foundation Class (IFC) files.

MicroStation works with different types of business data and defines the types of business items it will use. These different “Item Types” are organized and stored in domain-specific Libraries. When an item type such as a pump is to be created, the application can then use the “pump” Item Type to determine the different business properties available and gives you the ability to define specific property values when creating a pump.

In MicroStation, business data includes:

  • Item Types– Item types define the business properties for a specific type of item.
  • Items– Items are the individual representations of an Item type. For example, a facility might have a Centrifugal Pump Item Type defined but have multiple pumps represented in the design. Each pump would have the same properties but different values of these properties.
  • Relationship Types– Just as items are categorized by their types, relationships are also categorized by types. The relationship types generally convey some information about the nature of the relationship between the items. For example, a Pump item might have an “is annotated by” relationship with an annotation item. Similarly, it may also have an “equipment has nozzle“ relationship with a Nozzle item.
  • Libraries – Libraries hold a collection of Item Types and Relationship Types, usually related to a specific domain. You might have one library with Building Item Types and another Library with Plant Item Types.

In the MicroStation CONNECT Edition report definitions can be created to report on virtually anything. This can range from the properties of DGN files to model properties, Item data, cell names, and even simple element properties such as level or color. The resulting report may then be previewed in MicroStation, placed as a MicroStation table element, or exported to Excel or a comma-delimited file (.csv). Simple quantities may then be determined from the report results.

In the following example a report definition will be created to report on attributes associated with a geographic shapefile containing traffic signal data. The attributes for the shapefile are stored in the dBASE table file (.dbf) which is one of the three files required for a valid ESRI Shapefile. The attributes will appear in MicroStation as Item data attached to the traffic signal geometry.

Note: Shapefiles (*.shp) require at least three files in the same directory, with the same name and with the following extensions: .SHP (shape format; describe the feature geometry such as points, polylines, and polygons), .SHX (shape index format; a positional index of the feature geometry to allow seeking forwards and backwards quickly), and .DBF (attribute format; columnar attributes for each shape, in dBase III format).

Let’s get started by opening the design file CountyMap.dgn. This file contains a shapefile reference storing traffic signal data. The traffic signals are points, seen here as heavy red dots. The symbology of the traffic signals is displayed by assigning an element template to the shapefile from within the References dialog. A count of the traffic signals is desired, by signal type, and can be obtained from the shapefile’s attributes by creating a report definition.

Note: The active model in this file has several attached references and a Background Map displayed (available in View Attributes).

 

(Traffic signals shown as the heavy red dots)

Each of these traffic signal elements (points) contains a “TrafficSignals” Item Type. The Item Type and its associated Item data can be viewed by selecting a traffic signal and reviewing the properties of the element in the Properties dialog. Each traffic signal contains the following Items:

  • CITY – Name of the city in which the signal device is located.
  • DEVICE_TYP – The type of traffic signal.
  • FID – Financial ID (used to uniquely track each traffic signal).
  • FILE_NO – A number assigned to each item in the shape file.
  • MAJOR_STRE – A street on which the device is located.
  • MINOR_STRE – A street on which the device is located.
  • X_COORD – X coordinate of the signal.
  • Y_COORD – Y coordinate of the signal.

(Item Type and Items as seen in the Properties dialog)

A report definition will now be created to report on the TrafficSignalsItem Type. The Reports dialog can be opened by picking the Reports tool located in the Analyze ribbon tab of the Drawing workflow.

Note: It is typically considered a “best practice” to store report definitions in a configured design library (.DGNLib) if they are to be used for more than a single instance or by multiple Users. The Traffic Signals report definition is being created in the active DGN file for simplicity in this example.

Start by creating a new category (folder) in which to store related types of reports. Here this folder is named Simple Quantities.

Next, a new report definition titled “Reports - Traffic Signals” is added.

With the report selected, in Properties, set the following:

Search Location

  • Location Type:Model
  • Location:Active file
  • Model:Active Model
  • Include Reference Attachments:Yes
  • Include Cell Contents: No

Included Items

  • Item Types:Traffic Signals
  • Filtered By:(Unfiltered)

Now, columns will be added to the report. From the left pane of the dialog, pick Columns. In the right pane of the dialog, pick “Add columns”. This opens the Select Columns to Add window. Expand TrafficSignals, selecting the desired items, and pick OK.

And finally Sorting Rules will be applied to selected Columns. From the list of Columns, right-click over CITY, and pick Sort on this column.

Repeat this process adding sorting rules for the following:

  • DEVICE_TYP
  • FID

Sorting Options can be left using their default values. Verify that the Sorting Rules are listed in the order as shown:

The results of the report are now ready to be viewed. From the Reports dialog, pick Preview results.

The preview window is then opened, displaying the newly created report.

As can be seen, there were 1,457 traffic signals being reported on. And although we have an overall total, we still do not know how many of each type of individual signal there is. This can be easily achieved using a simple “drag-n-drop” technique to group based upon a selected column. From the report preview window, drag-n-drop the DEVICE_TYP column heading into the row above the column headings.

This will then group the results based upon device type, providing totals for each type of signal contained in the report. As seen from the results, there are 3 signals that do not have a device type designated, 2 bridge signals, and 27 fire house signals with additional rows listed for the remaining signal types.

The following files are those used in this blog post. To use these files to follow along, extract the ZIP file, placing the files it contains along with the DGN in the same folder.

communities.bentley.com/.../5658.CountyMap.dgn

communities.bentley.com/.../5706.TrafficSignals.zip

The simple concepts and techniques shown here can be modified, adapted and expanded to suit your specific needs. Take a Report for a “test drive” today and see what the MicroStation CONNECT Edition can do to enhance you AEC workflows!

 

For more information on creating reports, as well as step-by-step instructions for creating several report definitions, visit the following LEARNing path on the Bentley LEARNserver:

Train the Trainer Master Class: MicroStation CONNECT Edition QuickStart for Existing Users

In addition to this Bentley LEARN course, there is a helpful Blog series on creating reports for CAD Administrators that includes the following:

Until next time,

Happy LEARNing!

Reporting for CAD Administrators: Working Units, Scales and Coordinate System Reporting

$
0
0

In a project if you ever have encountered a design file that came from outside your company, department or group, you probably already know that no two “dgn” files are equal. In some cases they don’t print correctly, line styles don’t display correctly or have differing design file settings, and the list goes on.

We are quite used to a design file appearing the way we want it to, based on our standards. Some of the worst “violations” of these standards involve scale, units and coordinate systems.

As a CAD Administrator or user, I would almost bet, that over the years you have needed a report that looks like this. A report displaying all design files, just design models, showing the units being used, (MU:SU), angle format, Annotation Scale if 1:1 or 1:500, what the Line Style Scale is set to, if a Geographic Coordinate System is defined or not and if so what is it set to.

In prior releases of MicroStation, this type of report would have been done by a custom application. Today in the MicroStation CONNECT Edition we have robust reporting capabilities allowing for a report to be created in minutes. Reports are typically thought of for use with Item Types and their properties, used to quantify graphic elements in MicroStation. However, we can use them for many other properties within a design file.

This Blog, the fourth in a series will focus on a common request, “needing a report of my WorkSet, showing all models in all design files, the units, their accuracy, Annotation and Design Scale, what Line Styles derive their scale from and if there is a GCS set in each model and if so, what GCS is set.”

The best place to create this report is not in the active file but rather a configured .dgnlib within your WorkSet, WorkSpace or Organizational standards. This allows everyone with that configured .dgnlib to have access to this report definition and other helpful CAD Management reports. That is not to say that it must be placed at one of these configuration levels, it can be placed anywhere within your configuration from the Personal.dgnlib to standards.cfg and anywhere in between.

We will start with a .Dgnlib, that has been placed into …\Configuration\Organization\Dgnlib. By placing the file in this location, MicroStation will make any reports it contains available for use by anyone using this WorkSpace/WorkSet. The file can also be “locked” using file permissions to be read-only for all but certain users. A copy of the .Dgnlib with this report and others has been provided for your use.

To create the report:

  • From the Drawing Workflow, pick the Analyze Ribbon Tab and Reports.
  • Next, create a NewCategory (or add to an existing category), calling it whatever you desire. In this example, I will stick with CAD Mgt Reports.
  • Create a New report definition called Units Scales GCS Report.
  • Then, pick the Units Scales GCS Report, and set Properties>Search Location>Location Type to Path.
  • Substitute your Location or desired Variable to locate your desired directory. Here I will use $(_USTN_WORKSETROOT).

Note: There are several Location Types that can be used. A simple Location Type of File or Model will run the report on the active file and model.  

Setting this to Path expands our possibilities, here are just a few others.

$(_DGNDIR) will allow you to check only the files in the active directory. In a scenario where you have a /DGN directory with several disciplines underneath, for examples /DGN/Roadway and /DGN/Signals, this would allow you to run the report only on the Signals by opening a design from that specific directory.

$(_USTN_WORKSPACEROOT) will allow you to check all files within a particular WorkSpace. This will run the report on all Projects or WorkSets within the WorkSpace Root directory.

$(_USTN_WORKSETROOT) will allow you to check all the files within a particular WorkSet. It will run the report on the particular WorkSet you have selected.       

  • From Included Items, pick Item Types, there will be a drop down that appears.
  • Then from Include these Item Types, pick Select an Item Type>Dgn Models, followed by Design Model, selecting OK when complete.
  • From the right side of the dialog, pick Add these related items, Model resides in a Design File > Files.
  • And also, from the right side of the dialog, pick Add related item, Model contains element > ACS. Click OK when complete.
    • At this point we have told MicroStation that the report will include all Design Models. It will also include related items about the design files, their models and their ACS’ if defined.

  • Next pick Columns under Units Scales GCS Report and pick Add columns.
  • Expand Files>General> File Name. Check FileName and pick OK.
    • Set the File Name Format, Path to False, Root to True, Extension to False.
    • Right Press and Rename the File Name to Design File Name.
    • Then Copy and Paste Design File Name, to Design File Extension. Changing the Root value and Path to False, Extension to True.
  • Next pick Columns under Units Scales GCS Report and pick Add columns.
  • Add the rest of the columns based on the table.

  • Right press on the Design File Name and pick Sort on this column.
    • Set Order to Ascending, Hide Repeated Values to No.
  • Next, you can preview your new Units Scales GCS Report. From Reports, pick Preview results.

Note: Don’t worry about the exact order of the columns, you can reorder the report columns via the Move Up and Move Down icons.

Note: The report definition, created in the .Dgnlib is configured at the Organizational level. Alternatively, you can import the report from the .Dgnlib into the active file if desired. This is found under Utilities on the Reports dialog.

Filtering Reports

You will take note that the report is based on all files as defined by the _USTN_WORKSETROOT variable. This includes all .dgn files, .cel and .Dgnlib files. This report is displaying every design file, including every cell in the cell library. To limit the results you can apply a filter to only view the design files (.dgn) files. Select the Filter icon on the Design File Extension column. Then, select only the .dgn file.

 Keep in mind, rather than “massaging” the data herein MicroStation, the original report can be exported to Microsoft Excel and filtered there. Select Export results from the Reports dialog.

Everyone learns a bit differently, so the text of this blog may help some, for those who just want the report, included is the .dgnlib for your use.

 I hope you found this Blog informative. This was the fourth in a series on CAD Administration Reporting. If you have suggestions for needed reports from a CAD Administration basis, please comment on the Blog. You may just see your suggestion featured in the series!

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.


Modeled in MicroStation CONNECT Edition

Like V8i? You'll Love CONNECT!

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

Tip: CAD Administrators may also find Upgrading to MicroStation CONNECT Edition article useful. 

The Explorer – Part Five: The Sheet Index tab

$
0
0

So far in our blog series on the Explorer, found within the MicroStation CONNECT Edition, we have done an overview of the Explorer.  We have 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.  We also talked about the Items tab, which lists business items contained in a DGN file.  We then talked about the Resources tab which displays common resources being used by a DGN file.  Here, in Part Five of the Explorer blog series, we will take a closer look at the Explorer dialog’s Sheet Index tab.

Now, to utilize and take advantage of the capabilities of the Sheet Index tab, there is a prerequisite.  As you may know, in MicroStation, there are three model types -- Design, Drawing, and Sheet. So, if your company or organization currently uses sheet models, or plans to in the future, then the Sheet Indexing feature will be a great benefit to you.

The Sheet Index tab allows you to manage sheet indexing.  Sheet Indexing enables the use of a central location to index sheets and control the number, order, properties of sheets and make publishing deliverables easier.  A sheet index is a centralized and structured collection of sheets in your project.  A sheet index can be useful in creating a construction document set (also called as sheet set or construction set) that contains all the sheets of your project.

When you access the Sheet Index tab, you will notice that the sheet index has the same name as the WorkSet.  In this case, Building 302.   When you create a WorkSet, a sheet index is automatically created in the DGN WorkSet file (.dgnws) for that WorkSet.  The .dgnws stores the WorkSet Sheet Index, WorkSet Properties, custom WorkSet Properties, and the WorkSet Link Set.

Along the icon bank of the Sheet Index tab, the first icon from the left is the Refresh.  This refreshes the content of the sheet index. Though the sheet index automatically refreshes when you make any changes, in some cases, you may need to refresh it manually by clicking this icon.

Moving to the right, the second icon is a toggle between Open Sheet Index for Edit and Make Sheet Index Read Only.  By default, the sheet index is read only.  When you click the Open Sheet Index for Edit icon, this allows you to make changes to the sheet index. All changes are written to the .dgnws file.  While the sheet index is being edited, other users cannot make changes to the sheet index.  While the sheet index is in edit mode, you will notice that there are several more icons available.

Clicking the Make Sheet Index Read Only icon turns off editing options on the sheet index. When you click this icon, the changes made to the sheet index are saved and other users can make changes to the sheet index.  The image below shows both icons.

Sheet Index: read-only mode                                              Sheet Index: edit mode                 

In this blog, we’ll be using an architectural project as an example.  At this stage of the project, the majority of the sheets have been completed with one more sheet needed to finish the set.  We are going to create a sheet index from scratch.  That is, the folder structure and the sheet numbering rules that accompany them.  Then we’ll add the sheets to these folders.

With the sheet index in edit mode, the third icon from the left is the Manage Sheet Index.

This opens the Manage Sheet Index dialog in which you can manage the sheet index and its properties.

Here you will find three tabs:

  • The Index tab displays the properties of the sheet index.  This will be for any sheets not contained in a folder.  Here you can set controls like the number of digits for the sheet number, the suffix or prefix that you want to be added to the sheet numbers, the increment value for sheet numbering, and the start number from which the sheet numbering will start, just to name a few.
  • The Folder tab displays the properties of the folders in a sheet index. The default properties are the same as that of the Index tab and they are applied to the sheets within folders.

For this example, we are going to add a custom Sheet Number Prefix “A-“ to both the Sheet and Folder tabs.

And there is one more tab:

  • The Sheet tab displays the custom properties added to the sheets. Some examples of custom properties are Project number, Address, Owner, Project lead, and so on.

Moving to the right of the Sheet Index icon bank, we’ll find the Create Folder.

By creating folders and subfolders, you can organize the sheets hierarchically in folders, according to your organizational needs within the sheet index.  Remember, folders have the ability to control properties such as numbering for the sheets, number of digits, sheet number prefix and suffix, start number, increment, and so on for sheets in each folder. For our architectural project, we’ll need six folders.

Please note that it is important to have the appropriate item pre-selected within the listing before creating a folder.  In this case, we had to select the WorkSet Name, Building 302, each time when creating folders.  Clicking Create Folder with a folder selected, creates a subfolder under that selected folder.

In our example here, we created 6 folders.  The sheet numbering controls were inherited from the previous step where we adjusted the settings in the Manage Sheet Index dialog.  Now, we can adjust these folders so that they have rules that are unique on a folder to folder basis.  In this case, we’ll adjust the “Start Number” for each respective folder.  To do that, we can simply right-click on a folder and select “Properties” from the content menu.  This opens the Properties dialog displaying the properties of the folder.

So now that we built our drawing sheet index folder structure, let’s now add the project’s sheets to their respective folders.  To do this, you should select the desired folder first.  In this case, we’ll start with the, General folder.  Then, we’ll click the Add Sheet icon from the icon bank of the Sheet Index tab.

The Add Sheet dialog opens.  You may link any sheet model from any design file of your project into a sheet index.  In the Add Sheet dialog, select the DGN file that contains the sheet model and we’ll click OK.  The next Add Sheet dialog opens which lists the sheet models available for being added to the sheet index.  Here, since we have the General folder selected, we’ll select the Cover Sheet, in this case.

The Cover Sheet is added to the General folder.  By doing so, the rules set to the General folder have been applied.  Take notice to the prefix, A-.

Now, this procedure explains adding sheet models from another file into the sheet index. To add a sheet model from the active file, open the sheet index in editing mode and you can just simply drag the sheet model from the Models dialog into the Explorer dialog Sheet Index tab.

So, now we will go ahead and add the rest of the sheets already generated to the index.

In the image above, it shows the completed task of adding the sheets.  Take note to the numbers within the Sheet Index. The number next to the WorkSet name indicates the total number of sheets for the set. Beside each folder name, the number shown represents the total number of sheets within that respective folder. And within each folder, there are two numbers in brackets next to each sheet. The first number represents the sheet sequence within that folder and the second number indicates the overall sequence relative to the sheet set.

The Sheet Index can be used now to navigate the sheet set.  For example, if we want to open the Plan Sheet, simply just double-click the sheet model and it will open it.

At this point, continuing with this architectural project as an example, we have added into our Sheet Index all of the existing sheets.  It’s important to note that you do not have to wait till the end of your project, when all of your sheets are generated, to then start to use the Sheet Index feature in MicroStation.

Matter of fact, it is probably best to start using it from the very start of your project.  So, setting up your folder structure at the beginning would be the way to go.  Furthermore, it is possible to set up a Sheet Index folder structure in your WorkSet Template file.  Meaning, when you create a new WorkSet (equivalent to V8i Projects), along with it will be the Sheet Index as it was created in the template.  That will save you time by not having to recreate the Sheet Index again and again.

So far in this blog, we have covered two ways of adding sheets to the index.  Those are by the Add Sheets icon and just mentioned, by dragging and dropping a sheet model from the Models dialog into the Explorer dialog Sheet Index tab.  There are a couple more ways of adding sheets to the Sheet Index.

Another way to add sheets to the Sheet Index is through the Models dialog.  To demonstrate this, for our project, we need to add an Enlarged Details Plan.

From the Models dialog, we click the, “Create a new model” icon.  We’ll then set the properties within the Create Model dialog for a Sheet model.  From here, in the Sheet Properties section, we’ll enable “Add To Sheet Index” and then click the “Select a folder from Sheet Index” icon to the right.  This then opens the Sheet Index Folder Picker dialog from which you can select the folder in which the sheet model should be added.  In this case, the 400 – Enlarged Detail Plans folder.

Another way to add sheets to the Sheet Index is through the Create Drawing dialog.  This is the dialog that is part of the Dynamic Views workflow.  It proceeds the use of Named Boundary tool, or any of the callout tools such as the Section Callout, Detail Callout, Elevation Callout and Plan Callout tools.  To demonstrate this, we begin by using the Named Boundary tool to create a detail of a staircase in our proposed building.

As you can see in the image below, in the Create Drawing dialog, within the Sheet model section, the current settings selection is creating a new sheet within the BSI300-Sheets.dgn file.  And since this is a new sheet, the Add To Sheet Index is available.

However, since we created the Enlarged Details Plan sheet model in the previous demonstration, we are not going to create a new sheet.  Rather, we are going to place Staircase A into Enlarged Details Plan, which is already part of our Sheet Index.

So, we’ll click OK to the Create Drawing dialog, adding Staircase A to the Enlarged Details Plan.  Upon doing so, the Enlarged Details Plan sheet model opens with Staircase A referenced to it.

Here in the sheet, if we were to zoom into the drawing title, you will notice the sheet number.

As another example, you can insert a field in text you are placing or editing whose content is derived from a property of the sheet index or sheet index folder. A field derived, for example, from the total sheets count would be updated should the total sheet count in the sheet index change.  Please note that the Sheet index and sheet index folder properties can be placed as fields only when the active model is a sheet model listed in the sheet index.

If we were to zoom into the title block area, here too, we will notice the sheet number.  This is a “text field” that is derived upon the property of the sheet model.

As you recall, this was all based on the rules applied to the 400 – Enlarged Detail Plans folder.  If we were to add more sheets to this folder, they too would inherit the same rules.  And to take this one step further, if we were to re-arrange by the drag-and-drop technique, the sheets within this folder, then the sheet numbers in both the title block and the drawing title would change to the new sheet number, accordingly.

Returning back to the Explorer, in the edit mode, the next icon to the right of Add Sheet is the Remove Sheet.  This will simply remove the selected sheet from the list.

The second from last icon (in both read-only and edit) is the Place as Table.

By clicking this, this starts the Place Table tool to place the index sheet.

An index sheet contains properties of all the sheets in the sheet index that is placed as a table.  The image below is a result of placing the Sheet Index table.  As you can see, it is in raw format.

Once placed, you can begin working with the table by selecting it, and thereby utilizing the tools found in the contextual ribbon tab.  These are very similar to working with a Microsoft Excel spreadsheet. However, to get the desired result for our project, it would’ve taken many modifications to it.

Let’s take another approach for creating our sheet index.  Once placed, a report definition of the index sheet is also created in the Reports dialog.  Along the ribbon, from the Analyze tab, you can access the Reports dialog.

Here, you will find the Sheet Index report definition.  We’ll make a copy of this and modify it by removing unwanted columns, adding a Modeling column that was not originally part of the sheet index, and applying formatting and sorting rules.  Below is the resulting modified report definition, “Drawing Sheet Index”.

With the Drawing Sheet Index report definition ready to go, from the icon bank of the Reports dialog, we can click the Place as Table icon.  Notice in the Place Table tool setting window the Retain Association option.  With this enabled at placement time, it establishes a link from the report to the table.  So, whenever changes occur like adding sheets or removing sheets, the table can be made to update to reflect those changes to the Sheet Index.

And as a result, below is the Drawing Sheet Index as placed onto our Cover Sheet.

Once sheets are added to a sheet index, you can print all or a subset of the sheets by clicking the Print Organizer icon in Explorer's Sheet Index tab. The last icon (in both read-only and edit) is the Open Print Organizer.

Explorer seamlessly integrates with Print Organizer in a variety of ways to make it easy for you to print your project data. You can print all the sheets or a sub-set by selecting the appropriate folder.  In this case, we wish to create a PDF of the entire set.  To do this, we select the WorkSet name, Building 302 and click the Open Print Organizer icon.

The sheets are added to Print Organizer as variable print definitions which require a print style. Therefore, you will need to specify a print style when prompted for one. In this case, we will select the print style named PDF. Take note that these print styles would be expected to specify the appropriate printer driver configuration file and Paper size.

Upon selecting the Print Style, the Print Organizer opens. As you can see here, the folder structure was preserved.

When Print Organizer creates the print set, it iterates the sheet index link tree, starting with the selected node, and creates corresponding print set folders (if they exist) and variable print definitions. Each print definition corresponds to a single sheet in the index. Since variable print definitions are used, the print set construction finishes quickly.

The print set is a memory-resident print set and at no time will be written to disk, unless you decide to do that from Print Organizer. The name of the print set will be the name of the sheet index.

So, it is time to create the PDF so in the icon bank of the Print Organizer, we’ll click Print.  We’ll confirm the settings, making sure to enable Open print file after creation. Then we’ll click OK to publish the PDF.

And as a result, the Building 302 PDF opens.

So, the Sheet Index provides a great way to organize and manage all of the sheets in your project, into a centralized and structured collection.  Where you can control the number, order, properties of sheets and make publishing deliverables easier.  So, if your company or organization currently uses sheet models, or plans to in the future, then the Sheet Indexing feature will be a great benefit to you.

Next in Part Six of the Explorer blog series, we will take a look at the Links tab.  The Links tab can be used to see and manage the linked data, which can widely range from links to files, models, references, saved views, and supporting documentation.  So be sure to check out this final installment on the Explorer.

Tech Talk: Effective Rolling Stock Fleet Management February 5th and 6th

$
0
0

Join us for this new Tech Talk as we review how OpenRail for Asset Performance can help you improve the asset reliability and performance of your rolling stock fleet.

Topics discussed include:

  • Fleet Asset Hierarchy: define the assets at the level you maintain them
  • Tracking and Managing Key Performance Indicators (KPI)
  • Fleet Inspection Management through the total life cycle of assets
  • Managing a Fleet Management Reliability Program
  • Fleet Strategy Development with Root Cause Analysis and Reliability Centered Maintenance (RCM) methodologies

Register now for:


Like V8i? You'll Love CONNECT - Configuration Variables Dialog Improvements

$
0
0

As you are aware, the Configuration dialog is frequently required to modify the location of your library files or control the behavior of certain features.

Though a very useful dialog, it certainly had a few usability issues in V8i:

  • Finding a configuration variable – Since there were numerous configuration variables, it was cumbersome to find a specific configuration variable from the long list. Manually scrolling through the list was painstaking.
  • Need for session restart – Some configuration variables require restarting MicroStation session after you change their values. However, there was no way to know beforehand whether the configuration variable you edit will require session restart.
  • Consolidated list of defined configuration variables and their values – Say you wanted to check the location of all the DGN library related configuration variables. There was no way to get a consolidated list of all configuration variables and their values.
  • Not resizable – The dialog box was fixed in size.

The following enhancements to the Configuration Variables dialog overcame many of the issues you faced in V8i and hence saves time when working with configuration variables:

  • Search – You can now search for a configuration variable using the Search bar.
  • Status – The Restart icon in the flags column of the configuration variables list box indicates whether the configuration variable requires session restart for the changes to take effect.
  • Configuration variables list – Selecting File > Show Configuration Values opens a text file listing all the configuration variables, the Configuration level at which they are stored, and their values.
  • You can resize the dialog box.

The following video demonstrates the new enhancements in CONNECT Edition.

communities.bentley.com/.../5635.Configuration-Dialog-Improvements.mp4

CONNECT Licensing Benefits for OpenFlows Users

Additional information and a workaround for Users affected by the Microsoft patch

$
0
0

Dear gINT Users,

On January 8, 2019 Microsoft released updates (‘Patch Tuesday’) that included a security patch for the JET Database Engine. We have received numerous reports from users who are unable to open gINT projects after installing this patch. This patch was included in several Windows Updates (KBs) including those listed below (and possibly others).

We have been working with Microsoft to find a workaround to help those of you affected. The good news: Microsoft has identified the cause of the issue, and we have a workaround for users that need it until Microsoft releases a fix to the patch.

In the following paragraphs I will list the suspected cause, who this workaround applies to, what to do, and how to proceed moving forward. It will be a long post with many details. If you have any questions, please feel free to reach out. 

WHAT

The January 8 patch did not affect all users. As far as we can discern based on working with Microsoft, it affects users who have a field in their database with 32 or greater characters in the name. Also, the version of the Database the file is created in determines who is affected.

Our first recommendation is to uninstall the patch. If you cannot uninstall the patch, or it keeps being installed on your system, another workaround is to convert the database from the older database format (Access 97) to a newer format (Access 2002-2003). This allows users to open and use the file in gINT without changing the long field name(s). This can be done with Access 2010, or the script provided.

WHO

This Workaround is for users affected by the January 8 Microsoft patch and are unable to open a gINT project.

If you are able to open gINT and work in it, even if you have installed the patch, you do not need to use a workaround. However, we do recommend creating a copy of projects you are opening for the first time as there may be existing projects or data templates affected by the patch.

Errors received include:

Error 3343: Unrecognized database format

DatabaseAx.DBCloneFnB: DAO.Database: Unrecognized database format…

Database Structural Problem error

AxfilegINT.gINTfilevalidFNS errors:

 WHAT to do for current projects you are unable to open:

So you have a project affected by the January 8 patch, and cannot uninstall the patch or it keeps coming back. This information is for you on how to open the project or projects you need to open in gINT.  For this workaround you do not need to have Microsoft Access installed, or any specific version of Access.

You do need to run it on each project you cannot open and need to open until Microsoft issues a remedy for this error. Do not try to run gINT's "Repair and Compact" function as it may cause data to be lost. Also, as previously recommended, users should check the option to "Suppress Automatic File Compaction" option under gINT's System Properties.

Note: We are providing a VB script that we have tested internally on a few projects and it has worked. We cannot guarantee that it will work in all situations for all users. You are using the code at your own risk. We do recommend making a backup of any projects you use this workaround on before performing the workaround.

  1. Create a copy of the project file
  2. Download and install the following 32-bit or 64 bit (depending on your system) from Microsoft: https://www.microsoft.com/en-us/download/details.aspx?id=13255.
    1. Note: Use the defaults for installing (Chose “Reinstall or Repair…”)
  3. Download the script attached to this post. Delete the “.txt” extension so it is saved as “vbs”.
  4. Using Notepad or other simple editor, modify the ‘srcProject’ and ‘dstProject’ values in the updatejetversion.vbs file as follows:
    1. The ‘scrProject’ should be the entire path and name of the gINT Project you want to update
    2. The ‘dstProject’ should be a new name and where you want it saved.
    3. Example: srcProject = "C:\temp\projectname.gpj"; dstProject = "C:\temp\ranscript projectname.gpj"
  5. Start the command prompt
  6. At the command prompt, navigate to the folder where the script is located
    1. If you are unfamiliar with changing directories, you do this by typing in cd followed by the directly path at the command prompt. For example: cd C:\Users\Public\Documents
  7. At the command prompt type: Wscript updatejetversion.vbs
  8. The script will run. If you return to the folder where you saved the new project, open the project using gINT.
  9. Verify all project data is present and data saves. Continue working in the gINT project as you would normally.

WHAT to do moving forward with new projects

Your project or projects that were affected were created from a data template or project that had the older format. If you try to create a new project from a data template or project which is affected by the patch, you will be unable to do so as, with the January 8 Microsoft patch, it is an unreadable file.

To prevent the error from reoccurring with new projects, we suggest you make a data template from the project you just ran through the script, and let users know that this is the data template from which they should make new projects from now on.

Inside of gINT, with the new project open:

  1. In gINT’s navigation bar select Tools=> Make Data template
  2. Navigate to where you want to save the new data template.
  3. Enter a name in the file name path.
  4. Select Save.

You will need to let your fellow users know that this data template should be used for new projects from this point on.

In Conclusion

As mentioned, this is not the end. Microsoft is working on a solution to this issue as more software applications than gINT were affected. Please watch this space for updates and information once Microsoft has released a remedy.

Updates containing the patch that have been reported so far

KB

OS Targeted

Link

KB4480970

Windows 7 Service Pack 1, Windows Server 2008 R2 Service Pack 1

https://support.microsoft.com/en-us/help/4480970/windows-7-update-kb4480970

KB4480960

Windows 7 Service Pack 1, Windows Server 2008 R2 Service Pack 1

https://support.microsoft.com/en-us/help/4480960/windows-server-2008-kb4480960

KB4480964

Windows 8.1, Windows Server 2012 R2

https://support.microsoft.com/en-us/help/4480964/windows-8-1-update-kb4480964

KB4480961

Windows 10 version 1607, Windows Server 2016

https://support.microsoft.com/en-us/help/4480961/windows-10-update-kb4480961

KB4480973

Windows 10, version 1703

https://support.microsoft.com/en-us/help/4480973/windows-10-update-kb4480973

KB4480978

Windows 10 Version 1709 for x64-based Systems

https://support.microsoft.com/en-us/help/4480978/windows-10-update-kb4480978

KB4480966

Windows 10, version 1803

https://support.microsoft.com/en-us/help/4480966/windows-10-update-kb4480966

Like V8i ? You’ll Love CONNECT - Make Using Bing Maps a Snap by Using MicroStation CONNECT Edition

$
0
0

You like MicroStation V8i, but…  

Have you resisted using Bing Maps aerial and road information as a background to your design in MicroStation V8i because you weren’t quite sure about the licensing and costs involved or because it involved edits to the configuration files?

There are many reasons that you may say yes to that question. Among them;

  • Creating a Bing Maps account with Microsoft.
    • “…should I do it, my company or my IT department?”
  • Understanding the overwhelming license agreement when obtaining a Bing Maps key.
    • “… will I be charged for use or not?”
  • Obtaining a license
    • “… WOW there are a lot of license types available, which applies to me? ”
  • Keeping and updating the license key.
    • “…Just great, they expire after a given term, I get to do it all over again in three or six months.”
  • Creating a new MicroStation variable, MS_RASTER_BINGMAP_KEY.
    • “… can I even do that myself or do I need to involve my CAD Manager ?”
  • The Key must be in a CFG for MicroStation to read it.
    • “… which configuration file and can I even do that, and what is a CFG file anyway?“

Once every one of these issues are overcome, you need to restart MicroStation to re-read the CFG. Then assign a correct Geographic Coordinate System or GCS to the active model, next using Raster Manager, Attach Bing Maps, and then finally pick the layer desired. Not exactly point and shoot.

You’ll Love MicroStation CONNECT Edition because…

Beginning with MicroStation CONNECT Edition- Update 7 Bing Maps are available as a background image. This addition to the MicroStation CONNECT Edition saves you time by eliminating the lengthy setup process. It saves you money as well, because it’s free. There is no key or account or potential charge to you or your organization. And finally, you save time and money by getting up to speed without additional training on Raster Manager, Bing Maps is just one click away in View Attributes, putting the power at your fingertips.

  • No separate Bing Maps Account needed.
  • No Bing Maps Key needed.
  • No MicroStation Variable to add.
  • No potential invoice from usage.
  • No expiring license keys.
  • Availability in View Attributes, no additional training needed.

To use Bing Maps in MicroStation CONNECT Edition, simply define a correct Geographic Coordinate System or GCS in the Active Model, then from the View Attributes, pick the Background Map Type.

If you don’t see Background Maps available under View Attributes, check the defined Geographic Coordinate System for that Active Model. If you don’t have a GCS defined, the option will not be available.

Then pick one of the three standard Bing Maps available, Street, Aerial and Hybrid. That’s all there is to it!

Leverage the power of Bing Maps today- remember a picture is worth a thousand words.

communities.bentley.com/.../7750.BingMaps.mp4

Like V8i ? You’ll Love CONNECT - Stay current with the latest geographic coordinate systems in MicroStation CONNECT Edition

$
0
0

You like MicroStation V8i, but…   

Have you ever looked for a Geographic Coordinate System (GCS) that is simply not available?  The list of Geographic Coordinate Systems in MicroStation V8i is static and “as-is”. The development to add any additional Geographic Coordinate Systems to V8i has ceased. 

You’ll Love MicroStation CONNECT Edition because…

The MicroStation CONNECT Edition has been updated numerous times over the past 3 years.  In several updates, new coordinate systems like China’s Geodetic Coordinate System (CGCS2000) or Germany’s Deutsche Bahn Reference Systems (EPSG:5681 and EPSG:5685) were added. Others such as EPSG:24500 covering an area of Singapore was updated, while others like many in the Czech Republic, Slovakia and former Czechoslovakia were added, updated and simply organized.

Save time and money and complete projects faster by being up to date. Using MicroStation CONNECT Edition ensures that your projects and designs leverage the most accurate and up-to-date Geographic Coordinate Systems.

Don’t you owe it to your designs to make sure you’re using the most current and up to date list of Geographic Coordinate Systems?  Check out MicroStation CONNECT Edition’s list of Geographic Coordinate Systems now.

Like V8i? You'll Love CONNECT – Locate Anything in Your Designs

$
0
0

You like MicroStation V8i, but…

Ever use Project Explorer in MicroStation V8i?  Then you know it was used to create and manage links to project data, such as other DGN’s, DWG’s, Office Documents, or even PDF’s.  Project Explorer, a very useful dialog, lacked the critical capability to search for objects within the design. For example, needing to locate a particular manhole, drainage structure or even room or building.

You’ll Love MicroStation CONNECT Edition because…

The new Explorer, in MicroStation CONNECT Edition, extends Project Explorer found in MicroStation V8i. With the new Explorer, you can manage project data in a browser-like interface for files, links, items, resources, and sheet indexes.  Let it become your central resource for organizing project data.

Search for objects across all resources, perform a simple search, a search based on criteria, or much more advanced search:

  • Use a simple search, such as text.
  • A Criteria search, such as areas above certain square footage or type of valve for example.
  • Use the Advanced search building a complex search that can be saved for later, such as all the areas above a certain square meter but below another value.  Search results are saved as report definitions for use later.

Visualize your data with new viewing tools, toggle them on individually or in any combination:

  • Transparent – This turns the graphics that are not associated with the selected items invisible. Selected item(s) remain opaque.
  • Zoom – This will zoom to the selected items.
  • Isolate – This displays only the selected item’s graphics.  All other graphics are hidden.

So, with MicroStation CONNECT Edition, the enhanced capabilities found within the Explorer dialog will allow you to query the data and thereby, locate anything in your designs.

communities.bentley.com/.../Explorer-Searches.mp4

Like V8i? You'll Love CONNECT – Stay Current with Online Help

$
0
0

You like MicroStation V8i, but…

In MicroStation V8i have you ever looked for an answer to a question using the Help documents?  Perhaps you are new to using AccuDraw and want to discover the AccuDraw shortcuts?  Or want to know exactly how to place a cylinder or use Dynamic Views?  Although, as informative as the V8i Help may seem, it does have its limitations:

  • Help is static – Because the Help documents are installed locally on the machine, Help topics become quickly out of date. There are only as up to date as the release date of MicroStation V8i.
  • Flat images – Images in Help are flat and boring. They lack support for animations.
  • No way to share help topics – Sharing Help topics across users and projects is not possible.

You’ll Love MicroStation CONNECT Edition because…

MicroStation CONNECT Edition’s product documentation is now delivered as Online Help.  You no longer need to use the old static, out of date local Help files.  With Online Help, you always have the most up to date version of Help. Some of the key features of Online Help are:

  • Get help at your fingertips, right in MicroStation.
  • Support for gif animations for better visual explanation.
  • Context sensitive.
  • Up to date documentation.
  • Improved interface.
  • Easy to share.

In MicroStation CONNECT Edition, pick Help from the Backstage, by pressing F1 or clicking the Help icon on the Ribbon.  You will need to be signed into CONNECTION Client to access online help. That is all there is to taking advantage of the most up to date product documentation.

Don’t have internet access?  Then you can view the offline help which is installed local your machine.  When accessed, Help will then open in your default web browser. Use of Online Help is controlled through a User Preference setting. This setting is unique to the user and may be enabled/disabled through Preferences within MicroStation.

On many topics you will note that video is embedded directly into the Online Help.  Need to know how to use the Place Cylinder or Modify Solid?  Rather than read a written description, watch an animated video.

A significant improvement in Bentley’s documentation is the ability for users to add comments.

communities.bentley.com/.../Online-Help.mp4


Like V8i? You’ll Love CONNECT – Stay Current with DWG Files

$
0
0

You like MicroStation V8i, but…

For many organizations working with multiple file formats is a requirement of their design and engineering software. MicroStation V8i offered many innovations and enhancements, including support for AutoCAD DWG files. This began in the initial release of V8i with reading/writing 2009 DWG files, with this followed by the implementation of RealDWG Libraries in subsequent versions supporting 2010, 2012, 2013, 2014, and 2016 DWG formats and Object Enablers.

The AutoCAD format has continued to evolve with new versions of AutoCAD having been released, the DWG file format updated, and a variety of applications such as Civil 3D also updated potentially making the Object Enablers you used obsolete. This constant change in AutoCAD can cause you concerns, including:

  • Autodesk has continued to update the AutoCAD DWG format.
  • New versions of Object Enablers have been released.
  • The RealDWG Engine in MicroStation V8i will not be updated.

With future development in MicroStation V8i having ceased, you may wonder how you are going to continue supporting the use of DWG files.

 

You’ll love the MicroStation CONNECT Edition because…

The MicroStation CONNECT Edition is the latest software offering from Bentley Systems, offering unparalleled interoperability with support for a multitude of file formats and versions. This includes updated support for AutoCAD DWG files.

  • Support for 2018/2019 DWG file format
  • RealDWG 2016 support – MicroStation CONNECT Edition
  • RealDWG 2017 support – MicroStation CONNECT Edition Update 4
  • RealDWG 2018 support – MicroStation CONNECT Edition Update 7
  • Updated support for Object Enablers

When implementing the MicroStation CONNECT Edition, you will no longer see RealDWG listed in your installed programs. Rather, RealDWG has been integrated into the MicroStation installation and no longer appears as a separate application listed in your installed Programs.

Do you have the need to incorporate DWG files into your MicroStation based workflows? Start using RealDWG 2018 with the MicroStation CONNECT Edition today!

communities.bentley.com/.../RealDWG-2018_2D00_2019-Support.mp4

Like V8i? You’ll Love CONNECT – Tables in the MicroStation CONNECT Edition

$
0
0

You like MicroStation V8i, but…   

Placing tabular annotations is a frequent need that is encountered within a variety of disciplines. In MicroStation V8i there were many ways to accomplish this including:

  • Drawing a table manually with lines and text– This is a manual process, requiring each line and piece of text composing the table to be placed manually.
  • The MicroStation Basic “Table” macro– The “table” was created automatically using individual lines and pieces text, with the text being imported from an external text file. Row and column sizing were set manually when the table was placed, often requiring many iterations to get the table to appear in the desired fashion. Editing was not user-friendly, and this method did not provide for updating the data.
  • Paste Special (i.e. a linked or embedded Microsoft Excel Worksheet)– A popular method of bringing tabular data into MicroStation, this required a file from an outside application such as Microsoft Excel. The resulting table was not native to MicroStation, with editing performed using the original parent application (Excel).
  • Insert an object (i.e. Microsoft Excel Worksheet)– Similar to Paste Special, this allowed an empty table to be placed, with the table still linked to an outside application (Excel).

And while it was possible to use any of these methods, they could be cumbersome, difficult to edit, and may not be native to the MicroStation design environment.

 

You’ll love the MicroStation CONNECT Edition because…

The MicroStation CONNECT Edition offers a new Table tool that may be used to place a tabular data structure containing annotations such as a bill of materials, schedule or sheet index. It is native to MicroStation, behaving very similar to Microsoft Excel.

The new MicroStation CONNECT Edition Place Table tool offers the following enhancements:

  • A Table is a single element (not composed of individual lines and text).
  • A contextual ribbon tab housing an extensive set of tools used to edit a table and the data it contains.
  • Support for Title and Header rows.
  • Table data may be input manually, populated using a report definition, or through an external file with the latter 2 providing the ability to link the table to its data source for updating.
  • Easily modified using the table tools.
  • Table Seeds allow a new table to be placed based upon an existing standard.

 

Take a new MicroStation CONNECT Edition Table element for a test drive today!

communities.bentley.com/.../Advanced-Table-Element.mp4

SIG Workshop: MicroStation in D-A-CH – January

$
0
0

Guten Tag. Ich lade Sie ein zur einer weiteren Sitzung MicroStation Special Interest Group in D-A-CH am Freitag, den 25. Januar 2019 11:00 Uhr.

Thema: Neues von der MicroStation CONNECT Editio

Dabei geht es um folgende Inhalte:

  • Auswahllisten für Eigenschaften in Objekttypen
  • Was kann das Shrinkwrapper (Schrumpffolie) Tool?
  • Wie setze ich Perforatoren ein?
  • Benannte Präsentationen – was ist das?
  • Der Manager für Textfavoriten

Melden Sie sich noch heute an und sagen Sie es auch gern Ihren Kollegen weiter! SIG Meetings sind kostenlos und für alle Anwender von Bentley Software offen. Sie werden eine innovative Technologie Präsentation genießen und Zeit für Fragen und Antworten wird auch sein.

Als Teilnehmer erhalten Sie eine Professional Development Hour, die Ihrem Bentley Transcript hinzugefügt wird.

Wir sehen uns online!

Ronald Zeike
Senior Consultant MicroStation und PowerPlatform
Bentley Systems Germany GmbH

Update: MicroStation CONNECT SDK and VS2017

$
0
0

MicroStation CONNECT Edition Update 12 (and SDK) releases are fast approaching.  We would like to inform you in this release MicroStation and the SDK have set VS2017 as our default toolset used to build applications.  For those that have asked MicroStation CONNECT SDK U12 will be the first release to provide support for VS2017 and be set as the default toolset.  For everyone not already using VS2017, we recommend you install this latest update requirement (Microsoft Visual Studio 2017 Professional) at your earliest convenience.  As with previous compiler changes we always first recommend updating Visual Studio and (only if necessary) know that e.g. BUILD_USING_VS2015 can be provided to the bmake build tool (via command line, make files, or OS system environment variable) to hint building with older toolset compilers.

Thank you,
MicroStation SDK Team

New Tech Talk February 7: The Future of Transportation Asset Management

$
0
0

Join us for our first Tech Talk of the year on February 7th.

This new Tech Talk discusses the future of transportation asset management and what DOTs and agencies need to consider in order to make better decisions to improve operations. Through a review of industry trends and best practices this Tech Talk will help you identify opportunities to improve and enhance your road and bridge operations.

  • Make data driven decisions – the right data at the right time to make the right decisions
  • Reduce maintenance and operational costs – determine priorities, manage risk and improve decision making
  • Ensure regulatory compliance – fulfill regulatory and government reporting requirements
  • Enable Strategic Asset Management - improve service, safety and reliability through decision support tools

Registration links:

North America/Europe https://bit.ly/2MwyfNh

or Asia time zones https://bit.ly/2DBchpF

Viewing all 4605 articles
Browse latest View live


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