https://communities.bentley.com/search?q=text%20editor%20dialog&groups=298Search results for 'text editor dialog'en-USTelligent Community 12https://communities.bentley.com/products/pipe_stress_analysis/w/pipe_stress_analysis__wiki/27290/05-autopipe-stress-isometric-customization---relocate-and-rotate-north-arrow-to-a-different-positionFri, 15 Dec 2023 00:36:00 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:27290Mike Dattilio/products/pipe_stress_analysis/w/pipe_stress_analysis__wiki/27290/05-autopipe-stress-isometric-customization---relocate-and-rotate-north-arrow-to-a-different-positionApplies To Product(s): AutoPIPE Version(s): CONNECT; Area: Isometric Original Author: Bentley Technical Support Group Date Logged & Current Version Feb. 2016 10.00.00.10 Problem: How to relocate north arrow to a different position & rotate to a new direction on an AutoPIPE Stress Isometric using OPIM? Solution: Relocate to a New position In order to relocate north arrow you have to perform following steps. 1. In AutoPIPE launch Openplant Isometric Manager from menu “File > Launch Openplant Isometric Manager” 2. Open any border file you want to modify from “[Installation Directory]\isoextractor\Borders\...” i.e. I have selected DGN\A0BORD.DGN 3. Press Settings>View Attributes 4. On View Attributes dialog select “Text Node” and close the dialog. You can see in the snapshot below 5. On top left you see North Arrow place holder along with the text nodes 6. Select the place-holder along with the text nodes 7. Now you can move the selection set to any place in the border. 8. After setting proper place close OpenPlant Isometric Manager. 9. Make sure to use the same border during export to Stress Isometric using AutoPIPE. Rotate North Arrow This requires a lot of manual manipulation in AutoPIPE v.11.02.xx.xx and lower OPIM versions. However, use the following process when using AutoPIPE 11.03.00.xx and higher. AutoPIPE v11.03.00.xx and higher Open "style.xml" from the following folder location: "C:\ProgramData\ Bentley\ AutoPIPE xx\ isoextractor\ projects\ project01\ stress\ Config\ style.xml" Find the following setting underhttps://communities.bentley.com/products/pipe_stress_analysis/w/pipe_stress_analysis__wiki/18438/04-define-a-displacement-at-a-support-or-node-point-in-autopipeThu, 14 Dec 2023 23:14:00 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:18438Mike Dattilio/products/pipe_stress_analysis/w/pipe_stress_analysis__wiki/18438/04-define-a-displacement-at-a-support-or-node-point-in-autopipeApplies To Product(s): AutoPIPE, Version(s): All Area: Modeling Original Author: Bentley Technical Support Group Problem: How to apply support displacement to a support? Solution: Assign displacement at a support There are 3 commands to add support displacement: 1. Thermal Anchor movement, 2. Imposed Support Displacement, 3.Import Impose Support Displacement values from Excel #1. Thermal Anchor movement Select or insert an anchor component, on this dialog are some fields to enter Thermal anchor movement (ex. Dy = 10 inch vertically up. User should be cautioned when adding additional movements to the same node point and load case. Example, thermal anchor movement has already been assigned to anchor A00 and will be applied to load case T1 as seen above. Now if "Impose support displacement" was also assigned as shown below at anchor A00 per T1 load case (Dy = 10 inches). what would be the expected results, that the ancor node point A00 would move 10 inches or 20 inches? Answer: 20 inches. First Thermal Anchor Movement was applied that caused the support to move the initial 10 inches. Afterwards, the Impose Support Displacement was added to the already displaced 10 inches for an additional 10 inches or a total of 20 inches, see the output report for A00 per load case Thermal 1: Note, total movement report = 20 inches vertically up for Thermal 1 load case. #2. Imposed Support Displacement In AutoPIPE simply assign a displacement at the support for any load case, GR, T1, T2, E1, etc during modelling. Caesar has limitation of defining only 9 displacements which have to be combined in post processing to specific load cases. a. Select Insert > Xtra data > Imposed Support Displacement... b. The Imposed Support Displacement dialog opens . c. Enter in values and click OK . These can also be applied to anchors but only act in the direction of the restraint. Note: 1. Imposed displacement on a support is applied at the base of the support i.e. ground displacement. The force applied at the pipe is a function of the imposed support displacement in a certain direction times the spring stiffness in that direction. 2. For non-linear analysis - gaps will be considered. Meaning, the supported pipe would not be affected until the support gaps are closed based on the amount the imposed displacement settings Example: given the following supports Impose support displacement = Dx = 5.00, Dy = 5.0, Dz=5.0. applied at Gravity load case. Supports: A02: V-stop - all gaps = 0.00 B02: Vstop - gap up = 100, gap down = 0.00 C02: Guide - all gaps = 0.00 D02: Guide - gap up and left = 100, gap down and right = 0.00 E02: Line Stop - al gaps = 0.00 F02: Guide + Line Stop - all gaps = 0.00 Question : Which of the supports will move Dx = 5, Dy = 5, Dz = 5? One, two, or all? Answer: C orrect Only 1, Node point F02 is the only node point that will be displaced 5.0 in all 3 axis directions. For all the other node points, as the support moves based on imposed displacement, the support does not affect the pipe until the gap in that direction is closed. 5 out of 6 support has gaps in one or more directions that will not be closed, thus the pipe is not affected by the imposed support displacement. 3. Once an impose support displacement has been added to a load case (ex. GR) from that load case on in the load sequence (Gr - T1 - P1) the support would always be present at that displaced location when each load case was applied. Example: Given combination GRT1P1 where impose support displacement has been assigned to T1, When analyzing load cases Gr, the support would be in it's original location. However when analyzing load case T1 and all following load cases in the load sequence, (i.e. P1), the support has been displaced to its new location based on displacement settings. However, all gaps are open and closed based on the movement of the support from the original location to the displaced location. Question: Will a support connected to another node point be affected by a defined impose support displacement? Answer: Correct, No, neither the supported location or the connected to node point will be affected by a defined impose support displacement. Why? Because the base of the support spring is actually defined as another node point. Therefore, unless the connected to point was supported by another support connected to ground, Impose support displacement will have no affect. Consider inserting a concentrated force equal to an amount o move the pipe as needed. #3. Import Impose Support Displacement values from Excel AutoPIPE V8i 09.05.xx.xx has a new feature to import Impose Support Displacements from Excel: Insert> Xtra Data> Excel Support Displacement: Using AutoPIPE's input grids a user can easily copy / paste highlighted information to MS Excel. However, the data needs to be in a certain format when copy / pasting from Excel to AutoPIPE. AutoPIPE supports the ability to transfer Imposed Support Displacements from Microsoft Office Excel, editions 2007 and later in as few as 1.2.3 steps. 1. Open Template file in Excel AutoPIPE provided the following template files in the following folder location: C:\ Bentley\AutoPIPE V8i SELECTseries \ Templates \ Template - Imposed Support Displacements.xls 2. Fill in the Template and save the file The template file has some default information to be used in training new users about the feature. Highlight and clear the cells of existing information; insert your own data as needed. Once all the data has been entered, save the file (*.xls, or *.xlsx). Note: All the Node points and Load entered into the Excel file must also reside in the model where this file is to be imported into 3. Inside of AutoPIPE, initiate the "Excel Support Displacement" command: Select the command, Insert> Xtra Data> Excel Support Displacement. This command will open the dialog displayed above. 4. Complete the dialog a. Browse for the Template file to be imported The following should appear: --------------------------- File Loaded --------------------------- The File has been successfully loaded and validated --------------------------- OK --------------------------- b. Options: (see AutoPIPE help for details about these features) i. Change the input units as required ii. Enable / Disable the "Override Records" c. Press "Import" button, the following may be displayed: --------------------------- Excel Data Not Imported --------------------------- No matching record found. Hence no Imposed Support Displacement record has been overriden. --------------------------- OK --------------------------- --------------------------- Excel Data Imported --------------------------- Excel Imposed Support Displacement data has been successfully inserted into the model --------------------------- OK --------------------------- Pressing OK button will close the dialog and display the" Import Log Report ", notifying the user of any warnings or errors found during the import process. a. Log Messages Details: The Record has been successfully Inserted This record has been successfully imported into AutoPIPE's "Impose Dis." tab on the input grids. Warning: The record is in Unrecognized format. Ignoring this Record. There is a problem with the formatting of a cell in the Excel file on this indicated row, and therefore the data will not be imported Example: Processing Record Number 7 ... B03 S2 1 4 10.5 5 4 3= The Excel template file has 9 columns of data required for each row. In this example only 8 column of data are indicated. There is an obvious space between 1 and 4 above. Upon further inspection this value should have been set to 0 instead of leaving this particular cell blank. Note: for each row in the Excel file there should be 9 cells of data, nothing should be left blank. Warning: XXXXXX exceeds the Maximum limit for point name. Ignoring this Record. As indicated by the message, this node point value in the Excel sheet violates AutoPIPE node point format. A node point in AutoPIPE can only have 4 characters, otherwise the following will be displayed: --------------------------- Error --------------------------- Point name can be 1-4 characters long. --------------------------- OK --------------------------- Example: Node point = A101234 Cell value is to large for a node point, fix issue by reduce cell information down to 4 characters or fewer, (i.e. A10) Warning: The Specified Point (XXXX) could not be found in the model and has been ignored. As indicated by the warning message, the indicated node point cannot be found in the model. Review both the model and Excel file for the correct node point name. The names must match exactly. b. Fixes for "Template - Imposed Support Displacements.XLS" AutoPIPE template file "Template - Imposed Support Displacements.xls" is used as a training tool. The following errors will occur when trying to import the file without fixing the file first: The following fixes should be made before the file can be imported successfully: 1. Open the "Template - Imposed Support Displacements.xls" in Excel and make the following changes a. Change Cell A4 from "A101234" to "A10" b. In cells C6, C12, and C18 enter "0" c. In cells D3, D9, and D15 enter "0" 2. Save file in Excel and close the application. 3. In AutoPIPE, create a model as indicated below: a. 4 segments with following node point names (Pipe properties and node point distance are not critical, use any reasonable settings / values) Seg A - A00 - A20 Seg B - B00 - B20 Seg C- C00 - C20 Seg D - D00 - D20 b. Select All the node points in the model and add Guide supports c. Import Excel file as directed above. Expected Log results: total records imported = 18, and 0 warnings / errors Note: 1. The Import Log report is saved as an *.EIL file in the same folder as the model. This EIL file can be opened by any text editor (ie. NotePad, Ultra Edit, Ms Word, etc..). 2. New Feature ( 991369 ) was logged to add impose displacement at soil node points. Assign displacement at a Node Point Question: Why displacements cannot be applied to a point without a support: Answer: Currently AutoPIPE can only apply imposed support displacements at a point which has a non-zero stiffness in the direction of the imposed support displacement. The reason, at least from static analysis stand point, is that imposed displacement is a boundary condition, pretty much the same as a support i.e. A support restricts the nodal movement to a certain value AND imposed displacement also restricts the nodal movement of a node to a certain value. Internally, the Imposed Support Displacements applied at a support are converted in to an applied force by using F = K.X, where K is the support stiffness in the direction of the imposed displacement, and X is the imposed displacement in that direction. This force then makes it way in to the Applied Force vector of the system equation described above. Possibility of applying an imposed nodal displacement without a support: There could be a possibility (in dynamic analysis and static analysis) to apply imposed displacements at a node which does not have any supports. Here are 2 suggestions: Suggestion #1: Use a trail and error approach of applying a concentrated Force at the node point in question, then check the displacements report for the actual amount of movement experienced, and vary the force as needed to achieve the proper displacement of the pipe. Suggestion #2: From the limited research we carried out, it seems to be known as Enforced Displacements or Prescribed Displacements. This could be then possible to apply these enforced harmonic displacements (which is determined from the response of an existing system) at a node without any support. The modal response of such a system would then correctly simulate the actual system (which potentially is not possible today as a support is required at that node). It could be possible to then determine the response of the whole system based on the imposed excitation of that node. This however would need to be researched and investigated to find an appropriate analytical solution and to couple that with the existing AutoPIPE engine. Value of the currently available procedures: The currently available procedure are employed successfully to determine the response of a system where the imposed displacements are applied at the point of origin of vibrations i.e. pumps. These points are otherwise rigid, hence the modal response is correct. See the earlier link from Karim with a response. See Also General FAQ's about Supports and Beams Bentley AutoPIPEhttps://communities.bentley.com/products/microstation/f/microstation-forum/253592/larger-text-in-file-directory-window/793193Thu, 14 Dec 2023 22:36:00 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:793193Andrew Bell/products/microstation/f/microstation-forum/253592/larger-text-in-file-directory-window/793193It appears that you're requesting assistance with MicroStation V8i on a Windows 11 system. It is worth noting, firstly, that V8i versions of Bentley software are not supported or certified for use on Windows 11 systems. We would strongly recommend that you should be upgrading to a version of MicroStation CONNECT Edition or MicroStation 2023 that has been certified for Windows 11. Installation Requirements (bentley.com) Supported Operating Systems Windows 11/ Windows 11 (22H2) - Home, Pro, Enterprise, and Education Windows 10 (64-bit)/ Windows 10 (22H2) - Home, Pro, Enterprise, and Education Windows Server 2019 Windows Server 2022* Bentley does not support its software running on Microsoft operating systems versions that Microsoft has "retired". For more information on Microsoft's application retirement policy, click here . For similar information on Bentley products, refer to the Bentley Product Support article. *LumenRT is not certified on Windows Server 2022. As Lorys suggested, the text size in the 'File Open' dialog, which I assume is what you're asking about, is a Windows setting. We would suggest checking the various options in Windows using a Google search. Change the size of text in Windows - Microsoft Supporthttps://communities.bentley.com/products/microstation/f/microstation-forum/253591/dimensionThu, 14 Dec 2023 18:39:00 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:253591Anthony Hlad/products/microstation/f/microstation-forum/253591/dimension1Using Connect ver 16. Have placed dimensions with 3/32 annotative text in the model. It is showing up in the sheet drawing as 3/32. Model scale is set to 24 and the reference is set to 24. I understand that 3/32 x 24 is 2-1/4. It was showing the annotative height of 3/32 in the text editor before. Now if I open the text of a dimension in the text editor the height is showing 2-1/4". If I place plain text it shows up as 3/32 in the text editor. How do I get my dimension text to show the annotative height of 3/32 in the text editor?https://communities.bentley.com/products/projectwise/w/wiki/46171/what-s-new-in-pw-webThu, 14 Dec 2023 17:57:00 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:46171Jason.Slocum/products/projectwise/w/wiki/46171/what-s-new-in-pw-webDecember 2023 Enhancements: Introduced ability to copy a document or project using Document Creation Wizard (DCW) and load attributes from original document(s). Added ability to copy flat sets using Document Creation Wizard (DCW) Added ability to version multiple files at the same time (previous behavior only allowed you to version one file at a time) UI enhancement to allow you to move info panel to the right or the bottom of the screen and resize to fill the entire grid view Bug Fixes: Previously, the file download progress bar would not advance past 0%, even though the file was being downloaded. This has been fixed and the progress bar now shows the correct download progress. Resolved issue where the environment name did not always display properly in the info panel Resolved issue when editing connections in document settings and enabling a work area connection, it did not properly reflect the primary connection status Fixed intermittent issue that resulted in newly created (not primary) connections not being displayed properly on document settings page Fixed issue where the document name was showing old document name and not the doc code naming in progress bar October 2023 Enhancements: Introduced ability to copy documents and folders without the use of Document Creation Wizard Shortened web links are generated when sharing files Attribute exchange updates will now be triggered when checking out or downloading documents (note that a WSG update is required in order to use this functionality) Flatsets now respect the option to 'Automatically Check Out documents in ProjectWise Drive' when set in parent folder Document Creation Wizard will automatically replace invalid Windows characters with a '-', matching Windows Explorer behavior (note that previously an error message was displayed but the invalid characters were not automatically replaced) Performance improvements when working with folders that contain a large number of documents (greater than 10,000 documents) Bug Fixes: Fixed timestamp discrepancy between ProjectWise Web and ProjectWise Explorer Fixed inconsistent timezone issue on attribute panel Fixed issue in Document Creation Wizard where the a document code that has an extension included in the file name did not properly add the correct extension to the file name Fixed issue when deleting an existing web connection which was preventing the same name to be used when creating a new web connection Fixed issues with notification messages being displayed too often when uploading multiple files and not being cleared after canceling downloads Improved error message when connection doesn't exist for a link November 2022 The following enhancements apply to both ProjectWise Web and ProjectWise 365 : View documents Users can open common Office 365 documents for viewing in a new browser tab, either by clicking the document name in the document list, or by clicking the check box next to the document and selecting View from the action menu. Office 365 co-authoring usability improvements Improved UI around Office 365 co-authoring to provide clear feedback to users around starting, joining, and ending sessions. Improved performance of initial project page load Initial page load was optimized. It should load faster for most users. Issues fixed Fixed document list column resizing issue. July 2022 UI update for Open, Check Out, Free Document open, check out, check in and free commands have been moved to the top of menus and the toolbar. Open in desktop app does not perform a permanent check out and allows ProjectWise Drive to make automatic check out, if needed. Open read-only in desktop app option was merged into Open in desktop app option, and will ask for read-only option when it is possible. Confirmations when freeing documents and ending co-authoring Ending an Office 365 co-authoring session now lists the users who participated in the session and asks for confirmation before proceeding, to avoid accidental data loss if the session was closed prematurely. New Versions for documents marked as Final You can now create a new version of a document that is marked as Final. Issues Fixed Files with some special characters in the name failed to be uploaded when using the Create Document Wizard. Fixed view selection issue on Out to me page. Sometimes picklist values were empty in the Attribute form of the Create Document Wizard. Other fixes June 2022 Auto user sync (requires ProjectWise Plug-in for WSG CONNECT Edition Update 3.4 R4 (10.00.03.462) or later) When auto user sync is enabled in the primary work area connection, the current participants of the work area are automatically added to the team members list of the ProjectWise project . ProjectWise Web will then synchronize the project with the work area participants list every 24 hours to make sure the team members list in the project is always up to date. In order to turn this setting on, the connection must be the primary connection. See Adding and Configuring Work Area Connections April 2022 This release introduces the following enhancements for work area connection management: Primary connection You can now designate one work area connection in each project as the primary connection . The primary connection establishes a one-to-one relationship between the project and work area and is used as the default connection by ProjectWise Web and other cloud services. Designating a connection as the primary connection also automatically enables the use of ProjectWise Drive in that connection. See Adding and Configuring Work Area Connections New permissions to allow non-IMS admins to manage project connections An administrative team member who is not an admin in Bentley IMS can now add or manage work area connections as long as they have BOTH of these project permissions enabled: PS Federated Connections > Modify PS Federated Connections Product Settings Service > Manage Settings See Work Area Connection Requirements Connection health check In the connections list, a warning or information icon will appear next to a connection that requires some kind of attention or additional configuration. For example, if the work area in the primary connection is not currently associated to the project, or if the version of the ProjectWise Plug-in for WSG needs to be updated. January 2022 New Features Out to me – See all documents checked out to me and Office 365 co-authoring sessions that I have joined in a project. This feature requires the latest version of WSG plugin (10.00.03.460) . Folder selection in Advanced search – limit advanced search to a folder. Active folder is automatically preselected. Improved simple search – simple search will perform all content and full text search. This is now the same as in ProjectWise Explorer. WebView links – Get link has an option to create a WebView link. Fixes Attributes were not displayed in document list when document and view environments were different but column names were the same. Attribute panel was not updated when document was moved in WRE workflow. Dates in Audit trail CSV export were formatted incorrectly. Other bug fixes. April / May 2021 update ProjectWise Drive (version 2021.3.x) enhancements: When you have this version (or later) of ProjectWise Drive installed, selecting an Office document and selecting Start co-authoring session or Join co-authoring session will open the Office document for co-authoring in your Office desktop app instead of in a new browser tab. (Note that ProjectWise Drive only needs to be installed for this feature to work - the work area connection does NOT need to be synchronized with ProjectWise Drive, neither does ProjectWise Drive need to be running, for this feature to work). If a document is currently checked out to you in ProjectWise Web, the document will now automatically become checked out to you in ProjectWise Drive: either as soon as you synchronize the work area connection with ProjectWise Drive or as soon as you sign in to ProjectWise Drive, if the work area connection was already synchronized but ProjectWise Drive was not running when you checked out the document in ProjectWise Web (In earlier versions, the document that was checked out to you in ProjectWise Web would be locked to you in ProjectWise Drive in these situations.) When a document is checked out to you in ProjectWise Drive, you can sign in to ProjectWise Drive on any computer and that document will be checked out to you there. Note that the local changes you make to a document on one computer are not automatically available on other computers where ProjectWise Drive is installed, so you should try to only work on a document from one location. You can now look up information about the current work area connection by selected Settings > About current connection . The dialog that opens shows the following details: Name of connection Description of connection Name of work area Bentley Web Services Gateway (WSG) URL ProjectWise datasource that contains the work area ProjectWise Plug-in for WSG version Bentley Web Services Gateway version Browser version Menu items related to working on folders have been added to the action menu when a folder is selected. A menu item has been added to the action menu when a PDF is selected - Open in PDF Markup Service (you can also still just click the PDF to open it). The Advanced Search dialog has been improved, and now shows the environment that the selected property or attribute belongs to. December 21, 2020 update includes: Features/enhancements in this update require the ProjectWise Web Services Gateway Plug-in 3.4.This PW WSG plug-in 3.4 is now available on software downloads. Hosted users can request MaS upgrade with your account manager/Help Ticket. Document Creation Wizard Requires PW WSG Plugin Version 3.4 - ProjectWise Web now has a Document Creation Wizard to help users create documents with or without document codes and attributes. New Office 365 Integration Workflow - Users with Office365 Subscriptions can collaborate on Office documents with multi-user editing. Full Text Search Requires PW WSG Plugin Version 3.4 - The Full Text Search works the same as ProjectWise Explorer’s Full Text Search, searching inside documents and attributes. My Advanced Searches - Users can now create advanced Searches and save them an “My Searches” for future use. Move documents with versions - Requires PW WSG Plugin Version 3.4 - Users can now move documents that have versions. December 1, 2020 Update includes: Folder Navigation Panel - Navigate your work areas with a folder hierarchy, as you do in ProjectWise Explorer. Share Connections with External Users - Admins can share work area connections easily and invite external organizations and participants into a project. User Sync Service - When creating a work area connection in ProjectWise Web, users can choose to sync participants form that work area that are set in ProjectWise Explorer. Searching Enhancements - Users can now create advanced searches and save them for future use. Users can also get links to saved searches to share with others. Various defect fixes. If you do not see the new features, refresh your browser and log out/in again.https://communities.bentley.com/products/hydraulics___hydrology/f/haestad-hydraulics-and-hydrology-forum/253464/xml-geometry-import/793136Thu, 14 Dec 2023 12:01:00 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:793136Luis Fernandes/products/hydraulics___hydrology/f/haestad-hydraulics-and-hydrology-forum/253464/xml-geometry-import/793136Hello, Polygons can be saved in ASCII text files. The default extension for Polygons files is *.xy, but not mandatory (just makes it easier to select in the open file dialog). This file is organized in blocks, each containing the vertices for a certain polygon. One block is defined by the following keywords: and . Note that these keywords are case sensitive. One file can contain an infinite number of blocks. Inside each block there are 2 columns: the left relates to the XX coordinates of the polygon vertices and the right one to the YY coordinates of the polygon vertices. If geographical coordinates are used, the left column is longitude and the right column is latitude. Here is an example: -9.5190 38.8148 -9.4545 38.5699 -9.2612 38.4098 -9.0372 38.4686 -9.0550 38.7375 -9.1291 38.8921 -9.2644 38.8792 -9.4384 38.8438 -9.5254 38.8373 -9.5190 38.8148 Kind regards, Luishttps://communities.bentley.com/products/pipe_stress_analysis/w/pipe_stress_analysis__wiki/69749/autopipe-2023-23-00-01---read-me-fileThu, 14 Dec 2023 11:47:00 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:69749Mike Dattilio/products/pipe_stress_analysis/w/pipe_stress_analysis__wiki/69749/autopipe-2023-23-00-01---read-me-fileApplies To Product(s): AutoPIPE Version(s): ALL Area: Readme Date Logged & Current Version Dec 2023 23.00.01.367 Note: 1. Select Link here for Release notes What is New & Changed in AutoPIPE® The following outline identifies new features and enhancements in the AutoPIPE 2023 Edition Minor Update 1 version 23.00.01.367. Piping Codes Added ASME NB 2021 - Class 1 Components. The stress indices calculations for branch connections made with fillet or partial penetration welds [NB-3683.8 (e)] have been updated. Added ASME NCD 2021 - Class 2 and Class 3 Components. ASME has combined ASME NC and ASME ND in to a single standard as ASME NCD. AutoPIPE now provides ASME NCD as a new piping code. There are no major changes in ASME NCD from ASME NC / ASME ND 2019. Added ASME B31.1 2022 - Power Piping. This edition of B31.1 has updated the axial stress calculations for Sustained and Occasional categories. There are changes to some material properties that are available in AutoPIPE libraries. ASME B31.12 Hydrogen Pipelines Code - Added support for using Option B for Hf calculations. All ASME B31J consistency Warning and Error messages have been improved to provide more details. Modeling Rotational Supports is updated to better represent gapped supports. Use SIF of 2.0 option for reducers in now enabled for B31J models. Introduced importance factor for snow loading and updated default input units. Reports Word Reports - To improve report customization, users can now add merge fields to report header and footer. Word Reports - Equipment report is now available for Word Reports. Support Output Report headers for Local direction are revised to more accurately indicate direction of rotating support gaps. Forces and Moments reports in tee local coordinates is now available for all piping codes. User Interface NEW Result Grids with new more powerful grid control. The new control provides functionality to Group results, Multi-column sorting, variety of filtering options, and Microsoft Excel like conditional formatting. The control also provides customizing header and footer for printing and print previews. New charting tool used for graphed data. Show options now displays labels for cut-short. Load Combination dialog - A new column is added to describe inconsistency in combinations. General AutoPIPE program with all modules has been updated to 64 Bit. Introduced QAR Entitlement for AutoPIPE licensing. Interoperability Enabled the offsets and rotation options for iTwin Analytical Synchronizer. Security Release Notes Update Power Platform to resolve security vulnerabilities CVE-2023-0286, CVE-2023-31038 and CVE-2023-45853. Update Boost Libraries for security vulnerability (CVE-2012-2677). AutoPIPE® Requirements More detailed installation information can be found in the AutoPIPE Quick Start Guide. Product Version Product AutoPIPE Version v.23.00.01.367 Language English Japanese Polish Chinese (Simplified) Included Applications Versions PCF Translator v.1.3.1.367 PDS Translator v.6.0.0.021 ADL Pipe Translator v.1.0.0.029 ME101 Translator v.1.0.0.007 Structural Property Catalog 10.00.00.015 Bentley DGN Preview Handler 10.17.01.556 Bentley DGN Thumbnail Provider 10.17.01.11 iTwin Analytical Synchronizer v.23.01.02.64 iTwin Service Add in V2 2.6.1.1 Connection Client 23.00.00.10 Microsoft SQL Server Compact 3.5 SP2 3.5.8080.0 Installation Requirements CD drive or access to the Internet required for product installation. The minimum system configuration for installation: Operating System Microsoft Windows 10 x64 Professional or higher Microsoft Windows 11 x64 Professional or higher .NET Framework 4.7.2 When installing the product through the installer program, the required components will be installed automatically. The contents of the Desktop Prerequisite Pack include: Microsoft ® .NET Framework 4.7.2 Microsoft ® VC++ 2015-2019 Redistributable (x64) - 14.29.30133.0 Microsoft ® Access Database Engine 2016 (x64) CONNECTION Client - 23.00.00.10 iTwin Services Add-In - 2.6.1.1 NOTE: AutoPIPE uses the following fonts on dialogs and in reports. These fonts are pre-installed with Microsft Windows. If any of these font are missing, the text on dialogs and in reports may appear smaller/larger than usual. To install missing fonts, please repair or reinstall Microsoft Windows. Arial Calibri Consolas Courier New Georgia Microsoft Sans Serif MS Sans Serif Segoe UI Times New Roman Minimum Profile The minimum recommended workstation profile for running AutoPIPE is: Memory 4 GB recommended. More memory almost always improves performance, particularly when working with larger models. Hard Disk 4 GB free disk space (not including Restore Point space requirements). Video Graphics Card Any industry-standard video card which supports OpenGL 3D graphics. ProjectWise ProjectWise Server 10.00.03.299 with ProjectWise Explorer 10.00.03.453, ProjectWise Server 8.11.11 with ProjectWise Explorer 8.11.11. Note: ProjectWise Server and ProjectWise Explorer are only required if Bentley's ProjectWise is used to manage project documents. OpenPlant Isometrics Manager CONNECT Edition Update 11 - 10.11.00.175 Note : Users can use OpenPlant Isometrics Manager (OPIM) to review Stress Isometrics created by AutoPIPE without an entitlement for OPIM, provided they are opened from within AutoPIPE. Direct use of OPIM without an entitlement will log usage and may lead to charges. Click here for more information. Word processing, spread sheets, and access database Compatibility is more streamlined with Microsoft® Office 64-bit. Please refer to this wiki here for installing AutoPIPE on machine with Microsoft® Office 32-bit. Download and Installation See the AutoPIPE Quick Start Guide ( ..\Documents\ Quickstart_AutoPIPE.pdf ) for more information on downloading and installing AutoPIPE. To complete the licensing process, you must have the appropriate roles assigned by your Site Administrator. If you have not been assigned these roles, you will need to obtain the name of your Site Administrator by submitting a Service Request at http://apps.bentley.com/srmanager/ProductSupport . If you are experiencing problems logging into your Bentley account, please contact Bentley at 1-800-BENTLEY (1-800-236-8539). Outside the United States +1 610-458-5000. Network Considerations - Network drives are only supported for data files. - AutoPIPE software must be installed on a local client workstation. - AutoPIPE data files (*.DAT) must have full read/write access to be opened and edited. Applications Included in the Installation Package AutoPIPE Standard, AutoPIPE Advanced, AutoPIPE Nuclear, and add-ons are installed from one executable. AutoPIPE Standard - The standard configuration of AutoPIPE includes these features: Hanger selection, static linear and non-linear, modal, and response spectrum (SRSS combination method only) Static Earthquake - ALA, ASCE, Chinese GB50011, Mexican CFE, and User Profile Static Wind - ASCE, UBC and User profile ASME B31.1, B31.3, B31J, B31.4, B31.8, European EN13480, and General piping code Rotating equipment reports Beam elements for modeling frames and supports Library utilities Thermal Bowing Snow Loading Analysis Sets for multiple static analyses STAAD Structural Libraries (17 countries) Flange Analysis, ANSI Check AutoPIPE Advanced - Incorporates all of the features of the Standard version, as listed above with the following additions: Harmonic, Force spectrum, Time history, and SAM Buried pipe NUREG combinations and code case 411 spectrum Static correction - Missing mass correction and ZPA Wave loading and buoyancy, fluid transient loads, and relief valve loads Nuclear power piping codes: ASME B31.1-1967 Offshore piping codes: ASME B31.4 Chap. IX, ASME B31.8 Chap. VIII, CSA-Z662 Sect. 11 International piping codes Flange Analysis: ASME Section VIII Div 1, Div 2, Appendix XI KHK Level 1 Buried pipe w/ automatic Soil Calculator 50 Response Spectrum load cases Canadian piping codes Russian SNIP 2.05.06-85 Oil & Gas ISO 14692 KHK Level 2 piping code (note 1) ASME B31.12 Hydrogen Industrial Piping code ASME B31.12 Hydrogen Pipelines piping code AutoPIPE Nuclear - Incorporates all of the features of the Advanced version, as listed above with the following additions: ASME Class I/II/III design JSME PPC ASME Class I Thermal transient analysis (TTA) ASME Class I Ovality, Gross discontinuity, Delta T1, T2 loadings Fatigue Analysis JSME S NC1-PPC KHK2 Add-on for AutoPIPE Advanced or Nuclear - allows the use of the Japanese KHK Level 2 piping code in the Advanced or Nuclear version. Intergraph PDS, SmartPlant, ADLPipe, and ME101 Translators - This release installs four translators to import models from other applications to AutoPIPE. NOTE: For further information on translators, please refer to their respective readme files. AutoPIPE Functionality for QA Approvals Modeling - all features Codes supported ASME NB, NC, ND, and NCD - all years listed ASME B31.1 and B31.3 - all years listed ASME BPVC Case N-755-1 (July, 2011) (ASME NC, ASME ND, and ASME B31.1 - code years 2004 and later., ASME NCD - 2021 and later code years) CSA N289.3-10, section 7.3.4, clause (c) (i) (ASME NB - code years 2007 and later) CSA N289.3-10, section 7.3.4, clause (c) (iv) (ASME B31.1 - code years 2007 and later) JSME S NC1 Class 2-PPC - all years listed MITI 501 - Class 3 ASME B31J-2017 (ASME B31.1 and B31.3 - code years 2012 and later) ASME B31E for QA approved codes only (code years 2008 and later) Libraries Materials ASME Nuclear material libraries for all years listed ASME B31.1 material libraries for all years listed ASME B31.3 material libraries for all years listed JSME material libraries for all years listed MITI material libraries for all years listed Component AUTOPIPE AUTOJIS Flanges Gasket Analysis Static Analysis with the exception of Hydrotest Dynamic Analysis Thermal Transient Analysis (TTA) Seismic Anchor Movements Flange Analysis (ASME Section VIII - Div1 and Div2, Section III - Appendix XI) Loading Conditions Loading Conditions include, but are not limited to, pressure, temperature, seismic, wind, fluid transient, steam relief, and thermal bowing Circumferential wall bending, Ring buckling, Building Settlement, and Seismic (SAM + Wave propagation) + Thermal loads (ASME B31.1 - 2004 and later code years) Circumferential wall bending, Ring buckling, and Seismic (SAM + Wave propagation) + Thermal loads (ASME NC and ASME ND - 2004 and later code years, ASME NCD - 2021 and later code years) Pre Processing for piping codes above Automatic Soil Stiffness Calculator (ASCE 2001, and PRCI 2009) Automatic Wind Pressure Profile Generator (ASCE 7-98, ASCE 7-02, ASCE 7-10, and ASCE 7-16) Automatic Seismic Load Generator (ASCE 2002 (ALA), and ASCE 2010, and ASCE 2016) Post Processing for piping codes above Code and Non-code Load Combinations for piping codes above Stress Summaries (Leakage, Rupture and Buried Pipe options included) for ASME Nuclear piping codes Onscreen Results Output reports Integration with STAAD Pro Unit Conversion Documentation Program Help : Detailed feature information may be accessed directly from the calling application by selecting the Help command, or by pressing the Help button from any of the application dialogs. Be sure to explore the program Help for answers to your questions. A set of supplemental How To, Tutorial, and Reference Information documents in PDF format are provided in the Supplemental Documentation folder ( Bentley AutoPIPE > Supplemental Information ) of the main Program Help file (autopipe.chm). Tutorials : Documentation for AutoPIPE applications is provided online in the Adobe.pdf format. These files are accessible from the Help Menu. All documents can be browsed, searched, or printed with the Adobe Acrobat Reader. Information and how to download a FREE copy of the Adobe Acrobat Reader can be obtained from http://www.adobe.com/ . It is highly recommended that you obtain the latest version of the Adobe Acrobat Reader. Piping Codes This sections contains the list of piping codes, code editions supported and AutoPIPE license edition (Standard, Advanced or Nuclear) for which these items are supported. Standard Edition Piping Codes Piping Code Description B31.1 Power Power Piping B31.3 Process Piping Process Piping B31.4 Liquid Trans. Liquid Transportation Systems for Hydrocarbons, Liquid Petroleum Gas, Anhydrous Ammonia and Alcohols B31.8 Gas Trans. & Dist. Gas Transmission and Distribution Piping Systems EN 13480 European Piping Code for Metallic Industrial Piping General General Piping Code ASME B31J Stress intensification factors, flexibility factors, and sustained stress factors used in B31 piping analysis Extra Codes Available in AutoPIPE Advanced Edition AutoPIPE Advanced includes all codes available in AutoPIPE Standard, as well as the following codes. Piping Code Description CSA-Z662 Canadian Standards Association, Oil and Gas Pipeline System CSA-Z662 Offshore Canadian Standards Association, Offshore Steel Pipelines BS 806 Design and Construction of Ferrous Piping Installations for and in Connection with Land Boilers BS 7159 Design and Construction of Glass Reinforced Plastics (GRP) Piping Systems for Individual Plants or Sites SPC-2 Swedish Piping Code, Method 2 TBK5-6 General Rules for Piping, The Norwegian Pressure Vessel Committee STOOMWEZEN Dutch Piping Rule D1101 of the Rules for Pressure Vessels DNV Offshore Det Norske Veritas, Rules for Submarine Pipelines MITI 501 3-1980 MITI 501 Class III Piping Code KHK KHK E 012 Piping Code, Seismic Level 1 or 2 (Seismic Level 2 requires a KHK 2 Add-On license) RCC-M French Piping Code for Power Industry SNCT French Piping Code for Process Industry SNIP Russian 2.05.06-85 Oil & Gas Russian SNIP piping code for oil and gas ISO 14692 Petroleum and Natural Gas Industries - Glass Reinforced Plastics (GRP) Piping B31.4 Offshore Offshore Liquid Piping Systems B31.8 Offshore Offshore Gas Transmission B31.12 Hydrogen Industrial Piping ASME B31.12 Hydrogen Pipelines (Section IP) B31.12 Hydrogen Pipelines ASME B31.12 Hydrogen Pipelines (Section PL) Extra Codes Available in AutoPIPE Nuclear Edition AutoPIPE Nuclear includes all codes available in AutoPIPE Standard and AutoPIPE Advanced, as well as the following codes. Piping Code Description ASME NB Nuclear Boiler and Pressure Vessel Code, Rules for Construction of Nuclear Power Plant Components; Division 1, Subsection NC, Class 1 Components ASME NC Nuclear Boiler and Pressure Vessel Code, Rules for Construction of Nuclear Power Plant Components; Division 1, Subsection NC, Class 2 Components ASME ND Nuclear Boiler and Pressure Vessel Code, Rules for Construction of Nuclear Power Plant Components; Division 1, Subsection ND, Class 3 Components ASME NCD Nuclear Boiler and Pressure Vessel Code, Rules for Construction of Nuclear Power Plant Components; Division 1, Subsection NCD, Class 2 and Class 3 Components JSME PPC Nuclear JSME S NC1: Rules on Design and Construction for Nuclear Power Plants, Class 2 Piping How to Activate AutoPIPE® Subscription Entitlement Service is Bentley's licensing model, providing enhanced security and optimized value for your Bentley Subscriptions. It is integrated with Bentley's Identity Management System (IMS) to allow near real-time reporting of usage, improved alert messaging to users and increased administrative capabilities to license administrators in your organization. It will not only give you more options to monitor and manage usage but also provide new, advanced licensing features that will enhance digital workflows. Activation With Subscription Entitlement Service, all users must be registered with Bentley's Identity Management System (IMS) and sign in to the CONNECTION Client to access Bentley applications. Product activation will now occur through user sign-in to the CONNECTION Client with a valid IMS ID associated with their account. User sign-in will replace traditional activation keys, offering enhanced security as administrators will be able to control which users have access to Bentley software. License entitlements are granted and maintained through Subscription Entitlement Service's Entitlement Management Service . By signing into the CONNECTION Client users can also find their organization's projects, download software updates, receive relevant notifications, and track their usage. Alerts Subscription Entitlement Service features the new license alerts notifications that can be set by an organization's license administrators to let the users know when they reach a set usage threshold. These notifications will alert the users that if they continue to use the product, a term license may be issued. The user in such a situation has the choice to quit the application before a license is used or acknowledge that a term license may be generated and proceed with starting the application, based on what settings the administrator chooses. Evaluation Only - No license information The product will run in evaluation mode. Go to www.bentley.com to request activation information. Silent Installation For SES Licensing:. AutopipeSetup.exe -s -LicenseType=Connect Error History The following outline identifies all major errors fixed in Release of AutoPIPE v23.0.1. Defect 1081769: Minimum sustained margin may be calculated incorrectly from sustained combinations If a sustained combination includes another combination at the stress level, AutoPIPE may incorrectly calculate a higher sustained load margin value than allowed for use in thermal combinations. This would result in a higher allowable stress being reported for thermal loads, leading to unconservative results. Defect 1304731: Moment values for dynamic load case(s) may be transformed to Tee local moment incorrectly Unsigned load cases or combinations, such as Response Spectrum, are not correctly applied to tee nodes where the in-plane and/or out-plane moment axes are negative to the global coordinate system. If the combination combines a signed load case and dynamic load case, and the combination method is summation, the combination will be unconservative if the signed load case is positive. If the combination method is subtraction, the combination will be unconservative if the signed load case is negative. Defect 1293450: EN13480: Welded and Contour tees may use incorrect equation to calculate SIF values AutoPIPE does not provide option to input the crotch radius and thickness values for Welding and Contour tees. Moreover, AutoPIPE uses the Flexibility Characteristic equation which is applicable only when the crotch radius and thickness limitations are being met. In situations in which the crotch radius and thickness limitations are not met, incorrect Flexibility Characteristics will be calculated leading to incorrect SIF calculations. Defect 1276201: EN 13480 (2017 + 2021 addenda): In-Plane SIF for Fitting Tee is calculated incorrectly The In-Plane SIF calculation for the Fitting Tee is not in accordance with the 2017+2021 addenda of the EN13480 European Code when the "Single SIF at point" option is unchecked in the Result Model Options. Defect 1265695: Ultimate Force Gap inputs for an Incline Support may incorrectly get linked to other Incline Supports in the model The Ultimate Force Gap inputs for a new Incline Support inserted in a model may incorrectly get linked to one or more previously available Incline Supports in the model. Modifying Ultimate Force Gap inputs for any one of the linked Incline Supports will update the corresponding inputs for other linked supports in the model. This behavior may cause unintentional changes to the support inputs and lead to incorrect, possibly unconservative Displacement, Forces, Moments, and Stress results. Defect 1094104: ASME Libraries: Density values for certain standard pipe materials may be inaccurate Material density for certain standard materials provided with ASME Nuclear material libraries are not exactly the same as provided by ASME Section II part D. Historically, these density values were gathered from various sources. The percentage difference between the density values ranges from a minimum of -3.37% to a maximum of 4.33%. Defect 1302846: Stoomwezen: Occasional load margin for thermal allowable may not be calculated correctly The occasional load margin may not be used correctly for thermal allowable values. This occurs when the units for the model are set to any other units than English or AutoPIPE. In cases where the sustained allowable results in the minimum margin for a point, program may ignore that margin and use a larger margin from occasional load combinations. Using the higher allowable will result in unconservative allowable for thermal load combinations. Defect 1275135: ASME B31.4: Longitudinal Pressure term may not get added to sustained stress ASME B31.4: Longitudinal Pressure term may not get added to sustained stress. This happens only when result model option "Use rest. long code eq." is checked and code compliance output report is generated via keyboard shortcut "CTRL+B". This defect only impacts B31.4 2009 and later code editions having result model option "Use rest. long code eq." enabled. Defect 1092804: Tee local coordinate transformation incorrectly occurs after modal combinations of dynamic analysis sets Tee local transformation is required by all codes to align the load directions with stress intensification factors for tees. Previously, AutoPIPE performed this transformation after modal and group combinations were performed on dynamic loads (for example, response spectrum may have multiple modes to combine together to get a single total response). These combinations typically result in unsigned values, of which can no longer be transformed. Defect 1197360: Flexible Joint Report: Coordinate Transformation of Displacements is not done correctly Flexible joints transformation matrix used to convert displacements from global to local coordinates is malformed. This transformation skews the flexible joint report results in a way that do not reflect the actual displacements. Defect 1200626: ASME B31.4 2019 does not allow B31J SIF capabilities for B31J reducers Program does not consider B31J Reducer SIF requirements (as per Table 1-1, sketch 3.1) for B31.4 Onshore 2019 edition, with B31J checked. However, the same capability is implemented as per B31J requirements for other piping codes (such as B31.1, with B31J enabled). Defect 1175721: ASME B31E: Operating load case is incorrectly assigning analysis set properties For ASME B31E combinations/categories, when operating load case selected in seismic B31E dialog is from the first analysis set e.g., T1[1], Pressure stress (PD/4t) is not included or incorrectly included from another analysis set based on temperature case in sustained stress calculations. Also, allowable and yield stress is incorrectly selected from another analysis set for calculation of sustained allowable. This will lead to incorrect, possibly unconservative, sustained stress and sustained allowable results for the model. Defect 1216775: Flexible Joint subreport incorrectly considers load reactions outside of the flexible joint The flexible joint output subreport is intended to display the deflections (translations and rotations) that occur across the flexible joint itself. Currently, AutoPIPE is doing this by transforming the global displacements (as shown in the Displacements report) into a coordinate system that is local to the flexible joint as designed. This can lead to incorrect results when the deflections are not occurring across the flexible joint, e.g. a thermal anchor movement somewhere else in the system. This imparts displacements, but not across the flexible joint. Defect 1123428: Security Vulnerability (CVE-2023-0286): Update Power Platform Updated Power Platform to version 23.0.1 that fixes security vulnerability CVE-2023-0286. Defect 1307828: Security Vulnerability (CVE-2023-31038): Update Power Platform Updated Power Platform to version 23.0.1 that fixes security vulnerability CVE-2023-31038. Defect 1307703: Security vulnerability (CVE-2023-45853) - Update Power Platform Updated Power Platform to version 23.0.1 that fixes security vulnerability CVE-2023-45853. Defect 1233810: Security Vulnerability (CVE-2012-2677): Update Boost Libraries Updated Boost libraries to fix security vulnerability CVE-2012-2677. Copyright TRADEMARK NOTICE Bentley, the "B" logo, AutoPIPE, MicroStation, ProjectWise, SELECT, and MDL are either registered or unregistered trademarks or service marks of Bentley Systems, Incorporated, or one of its direct or indirect wholly-owned subsidiaries. Other brands and product names are trademarks of their respective owners. COPYRIGHT NOTICE © 2023, Bentley Systems, Incorporated. All Rights Reserved. Including software, file formats, and audiovisual displays; may only be used pursuant to applicable software license agreement; contains confidential and proprietary information of Bentley Systems, Incorporated and/or third parties which is protected by copyright and trade secret law and may not be provided or otherwise made available without proper authorization. Complete copyright information can be found in the product by choosing Help > About. For reference, a copy of the End User License Agreement named "EULA.pdf" is included in the product installation folder. Corporate Headquarters Bentley Systems, Incorporated 685 Stockton Drive Exton, PA 19341, United States 1-800-BENTLEY (1 800 236 8539) Outside the United States +1 610 458 5000 Bentley EMEA Bentley Systems International Limited Charlemont Exchange 5th Floor, Charlemont Street Dublin 2, D02VN88, Ireland 1800 948 368 +353 1 436 4600 Bentley Asia Bentley Systems (Beijing) Co., Ltd. Unit 1402-06, Tower 1 China Central Place Beijing 100025, China 400 842 7516 +86 10 5929 7000 Online Information requires access to the Internet AutoPIPE Information Technical Information BE Communities Bentley Products Bentley Community See Also AutoPIPE Yearly Release Notes How do I download, install, and license AutoPIPE? Bentley AutoPIPEhttps://communities.bentley.com/products/digital-twin-cloud-services/itwin-services/w/synchronization-wiki/68291/missing-dataThu, 14 Dec 2023 08:45:00 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:68291Lidija Belcikova/products/digital-twin-cloud-services/itwin-services/w/synchronization-wiki/68291/missing-dataHere you will find an explanation and best practices for solving Missing Data related synchronization errors. Category: Missing Data Missing data errors are a common issue in Synchronization. Understanding the missing data errors requires a knowledge of what data is being synchronized into the Model. This highly depends on the file format being synchronized. This data can be synchronized into the Model along with the main design file: Reference xRef ( layer, Drawing Model) Raster Point Cloud Model Sheet model 3D view Alignment Material (Texture, Mapping (e.g. Cubic, Planar, etc.)) Text style Font Schema (element class) Properties Accompanying file, specific to data format Table of Contents Missing References Error: Dgn_0214, DgnV8_0132 Warning: DgnV8_0133 Missing Materials Error: Revit_0002 Missing Fonts Error: Revit_0025 Error: Dgn_0000 Element Warning: Dgn_0188 Line Style Warning: DgnV8_0046 Point Cloud File Warning: DgnV8_0068 Missing Dependency Info: Civil_0004 Warning: Civil_0010 Missing References Error: Dgn_0214, DgnV8_0132 Error message: "Reference attachment (.dgn) is missing from reference or master model .dgn" Issue: Reference attachments cannot be found in the defined location and can not be synchronized. As a result, the iTwin doesn't show all the input files (Master or References) in iModel Index or visibility tree in Desing Review. Cause: The reference file was deleted, renamed, or moved to another location. Reference hierarchies have changed (for example nesting depth changed). Scan References in ProjectWise Explorer were not run on the master file after the data import, move, and rename operation was completed in the DataSource. If this file is an i.dgn, then the references were not included correctly and need to be updated in the design application. Solution: Run Scan References on the master file from ProjectWise Explorer. Read more about why reference scanning is important and how to run ScanRef . In the design application used for the master file creation, go to the References dialog and fix any attachments that are missing. Items that need to be fixed are indicated in red. Read more about attachment fixing in design applications. Reference Manager dialog can be launched using Ribbon: Modeling > Home > Primary > Attach Tools split buttoning MicroStation application. If there are references in sheet models, they need to be fixed also. Run Scan References on the master file from ProjectWise Explorer. You can also open the sheet model to check for unresolved references marked in the i.dgn. When using the Infrastructure cloud portal, make sure references are linked to a master using a relative path. References can be linked to the master as relative path using as shown in Image 1 : Image 1 Warning: DgnV8_0133 Warning message: "Reference model is ignored because its display is turned off in the master model." Setting the reference file's display off in the master file is a common practice in various software applications, especially in computer-aided design (CAD) and 3D modeling environments. This is often done to simplify the view, optimize performance and file size, and reduce visual distractions. The synchronization logs this information and provides it for any potential issues analysis in the synchronization report. Issue: Reference files are missing in the iModel. Cause: The reference file's display is turned off in the master model. Solution: Open the source file in the Power Platform application where the source file was created (MicroStation, OpenBuildings Designer, or other). Go to Home -> References. In the opened References dialog notice that some references do not have a checkbox selected in the Reference Display column. (Highlighted in green in the below image.) This means that the display is turned off. If you need these references to be synchronized to the iModel, update the display setting in the source file, save the changes, and reprocess them to the iModel. If you do not want to process the disabled references to the iModel, please ignore this warning. Missing Materials Materials in drawing files are the digital representations of real-world materials that can be assigned to objects within your models. For example, you can apply a wood material to a model of a table to make it look like it's made of wood. So materials can contain information about the texture, color, reflectivity, transparency, and other visual properties of a surface. They can be custom-made or delivered with material libraries. There can be multiple reasons why material information is not visible in iModel Viewer, for example, Design Review. One of the reasons is that iModel Connector continues to increase the support for additional materials. However due to current limitations, this new material information will not be processed into existing iModels, but they are with newly created iModels. To work around this limitation, we recommend unmapping the source file and mapping it back to initiate full iModel reprocessing. Read more about the unmap procedure here https://communities.bentley.com/products/digital-twin-cloud-services/itwin-services/w/synchronization-wiki/51447/edit-a-connection . Note that if you are using a Version Compare with the contents of the model to be unmapped, all elements in the file will appear as new elements when doing version compare on change sets from before the unmap to after the re-import. Please find more reasons why material information is not visible and how to solve this below. Warning: Revit_0002 Warning message: "Missing image file: . Please place the texture file next to the source Revit file. If you run publishing locally, you may also install the recent Autodesk Material Library for standard textures. Issue: Visual fidelity issues in iModel such as missing textures in elements. Cause: The design model has defined Autodesk materials, but materials files are not provided in a way that synchronization can access them. Solution: Autodesk material files need to be provided manually for synchronization to be able to use them during the synchronization process. To fix the missing materials issue, please copy the material files from the Autodesk installation location C:\Program Files (x86)\Common Files\Autodesk Shared\Materials\{year of release} to the design file location. In case the Autodesk material library is not installed with the Autodesk product, or you do not have the materials files, use the Autodesk guidelines to install the materials library from the Autodesk Once the material library is installed, copy the material files to the same folder as the design file and start the synchronization to the iModel. Missing Fonts Warning: Revit_0025 Warning message: "Missing font: . Please place missing font file(s) next to the source Revit file." Issue: Visual fidelity issues in iModel such as wrong font, missing font characters, and incorrect font display size. Cause: The synchronization environment contains only a limited amount of Windows default fonts, that can be used during synchronization to Model. In case a unique, non-standard Windows font is used, a default system font will be used instead. Solution: All non-default Windows fonts need to be provided to Synchronization manually for those fonts to be used. If fonts are placed in the same location as the design file, they will be picked up by synchronization and the missing fonts messages will no longer be reported. Fonts can be copied from C:\Windows\Fonts. Error: Dgn_0000 Error message: "Could not locate font Courier New. Please place the font file(s) in the same directory as the design file." Issue: Visual fidelity issues in iModel such as wrong font, missing font characters, and incorrect font display size. Cause: The synchronization environment contains only a limited amount of Windows default fonts, that can be used during synchronization to Model. In case a unique, non-standard Windows font is used, a default system font will be used instead. Solution: All non-default Windows fonts need to be provided to Synchronization manually in order for those fonts to be used. If fonts are placed in the same location as the design file, they will be picked up by synchronization and the missing fonts messages will no longer be reported. Fonts can be copied from C:\Windows\Fonts. Element Warning: Dgn_0188 Warning message: "X Element(s) are skipped as these elements are invisible." Issue: Coming soon. Cause: Coming soon. Solution: Coming soon. Line Style Warning: DgnV8_0046 Warning message: "Could not find definition for line style [ ]. Some elements may not display properly." Issue: Coming soon. Cause: Coming soon. Solution: Coming soon. Point Cloud File Warning: DgnV8_0068 Warning message: "PointCloud file attachment is missing." Issue: The reality attachments like Point Clouds are not visible in iTwin Reality Data widget. Cause: The Point Clouds are not properly attached to the source file. Sufficient access rights to publish the reality data into ContextShare Service are not granted. Solution: Fix the PointClouds attachments: Open the source file design application, and open the PointClouds Attachment dialog from Ribbon: Modeling > Home > Primary > Attach Tools split button. Grant ProjectWise ContextShare "Create" permission for synchronization owner. Read more about how to publish point cloud data . All point clouds with less than 7 million points will go directly into the iModel. Point clouds greater than 7 million points require the use of a Context Data Share which would have to be set up for the project. Be aware that large point clouds can greatly increase processing times. Missing Dependency Info: Civil_0004 Info message: "No alignment found for source corridor 'Alignment Name'" Issue: Coming soon. Cause: Coming soon. Solution: Coming soon. Warning: Civil_0010 Warning message: "Ridge with name 'Name and ID number could not find its associated alignment. As a result, this bridge and its parts will be processed as generic graphics instead of physical bridge elements. This can affect what properties" Issue: Coming soon. Cause: Coming soon. Solution: Coming soon.https://communities.bentley.com/products/ram-staad/w/structural_analysis_and_design__wiki/42309/6-release-noteThu, 14 Dec 2023 05:57:00 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:42309Abhijeet Gundaye/products/ram-staad/w/structural_analysis_and_design__wiki/42309/6-release-noteRCDC (SACD) V2023 (23.00.03.63) This release mainly consists of implementation of minor enhancement and priority bugs. The following are some of the minor enhancements added to RCDC V23.00.03, 1. Calculation of Curvature ductility factor used for the Ductile Columns of Euro codes. RCDC is now providing following two options to consider the curvature ductility factor. • Compute curvature ductility factor based on the various inputs available in the program. • User defined curvature ductility factor. 2. Projection (offset) of pile-cap from edge of pile - The maximum permissible offset value has been now increased so that user can provide the higher values. 3. Pile capacity values (compression, Tension and shear) are allowed to provide up to two decimals in RCDC so that user can provide more accurate pile capacities for the pile cap design. To find out more about these features and other enhancements, please refer to the attached release notes. SACD (RCDC) Release Notes - V 23.00.03 RCDC (SACD) V2023 (23.00.02.43) We are pleased to announce the release of RCDC (STAAD Advanced Concrete Design / SACD) version 2023 (23.00.02.43). This is a minor release that consists of the following features, Beam Ductile detailing Enhancement – All design codes – The area of reinforcement provided is used in all cases to satisfy all ductile member-related detailing requirements in the beam module. Column effective length factor Enhancements in redesign tools – All design codes – The option to recompute the effective length factor at various stages of column design and redesign is now available. To find out more about these features and other enhancements, please refer to the attached release notes. SACD(RCDC)_Release Note - 2023.00.02 RCDC (SACD) V2023 (23.00.01.24) We are pleased to announce the release of RCDC V23 (23.00.01.24). This is a Patch Release to RCDC V23 (23.00.00.98) release. This release includes defect corrections in the Beam design module. Resolved Issues: Beam Auto Design - Error in the performing beam auto design operation in certain scenarios. RCDC is unable to perform the auto design operation of beam design due to an error in reading supports of the beam. This is not common but is found in the following cases. Beam entirely overlapped on the column/wall. The member starts node and end node are found within the extent of the length of the column/wall. Circular curved beams are present in a structure. The curved beam is modeled by creating multiple small straight segments with some angle in plan between the support to get the behavior of a curved beam. The issue was found in the reading of the geometry of the beam. The beam end supports are not identified properly in the above-mentioned cases, due to this the exception error occurred in the auto-design operation of the beam. The user is unable to design beams in RCDC. This issue has been resolved in RCDC V23.00.01.24. The correct column/wall supports are now identified for beams and auto-design operation can be performed without any error. RCDC (SACD) V2023 (23.00.00.98) We are pleased to announce the release of RCDC (STAAD Advanced Concrete Design / SACD) version 2023 (23.00.00.98). This is a minor release that consists of the following features, 1. Beam Crack-width check for corner Rebar - at the corner and side face of the beam – Indian code 2. Beam flexural calculation enhancement – ACI and NSCP codes 3. AS 3600:2018 – New check added for Minimum percentage reinforcement for the column based on axial load 4. Addition of 6 & 9 mm rebars for Column and Beam design in ACI (metric) and NSCP codes 5. Load Type reading for load cases from STAAD To find out more about these features and other enhancements, please refer to the attached release notes. SACD(RCDC)_Release Note - 23.00.00 RCDC (SACD) Connect Edition V11 Update6 (11.06.00.56) We are pleased to announce a release of RCDC (STAAD Advanced Concrete Design / SACD) 11.06.00.56 version. This is a Minor release which consist of following features, 1. Ductile column & Beam Joint check – Beams with end release have been Ignored – All codes 2. Column PM Interaction curve Presentation – 2D PM curve added– All codes 3. Column and Wall – Option to set maximum diameter for shear links – All codes 4. The beam is identified as non-Ductile if the beam is released at any one of the ends – All codes 5. Beam separate input for the side clear cover – All codes 6. Cantilever beam bottom reinforcement detailing without maximum spacing check if the bending moment is zero. 7. Update the design if the Footing Design file is created through the pedestal design 8. Optimizing the shear reinforcement provided in the beam if ductile, torsion and other spacing criteria are governing To find out more about the features added in this release, refer the attached release note. SACD(RCDC)_Release Note - 11.06.00 RCDC (SACD) Connect Edition V11 Update5 (11.05.00.155) We are pleased to announce a release of RCDC (STAAD Advanced Concrete Design / SACD) 11.05.00.155 version. This is a Minor release which consist of following features, ‘Update Pile-cap Design’ functionality in the Pile-cap module with a new analysis file- All Design codes The current footing design logic improved to accommodate axial force from columns that are tensile and when stability checks are performed General improvements in various modules of the ACI 318-2011 code 13mm rebar diameter added for the Euro code Cantilever beam to be ignored in the joint check of ductile column design Logic improvement in the shear design of the tank slab to satisfy the check To find out more about the features added in this release, refer the attached release note. SACD(RCDC)_Release Note - 11.05.00 RCDC (SACD) Connect Edition V11 Update4 (11.04.00.151) We are pleased to announce a release of RCDC (STAAD Advanced Concrete Design / SACD) 11.04.00.151 version. This is a Minor release which consist of following features, ‘Update Beam Design’ functionality in the beam module with a new analysis file- All Design codes Reading and ‘Design of Beams at Foundation Level’ without column modeled Different Reinforcement Grades for Main and Secondary reinforcement for Column module- All Design codes An additional option to calculate the Moment Capacity Reduction Factor (φ) for column design as per AS 3600:2018 ‘Design Change’ report for the ‘Update Design’ functionality in the column module An option to select the Strength Reduction Factor (φ) for shear design of special frames for ACI & NSCP code Pile-cap design for Columns with ‘Tensile Axial’ force- All Design codes Reading Tapered tank wall from STAAD physical modeler To find out more about the features added in this release, refer the attached release note. SACD(RCDC)_Release Note - 11.04.00 RCDC (SACD) Connect Edition V11 Update3.1 (11.03.01.10) This is a Hot fix to RCDC V11 Update 3 release. This release includes defect corrections in the ductile column design module. Resolved Issues: Ductile Column design – Error in the calculation of Issue in the final design of main reinforcement while performing various redesign operations. For columns that are designed using the Auto Design facility, RCDC allows some further redesign operations to be performed on those columns. Examples of these redesign operations are: a) Level Grouping - which allows all the columns at a given level to have the same reinforcement b) Level Ungrouping - which is the opposite of what is described in (a) above c) Grouping of any two or more columns specifically chosen for this task d) Un-grouping of any two or more previously grouped columns specifically chosen for this task e) Grouping/un-grouping using the Snapshots facility available in the Reports menu of RCDC f) An ignore/include operation is performed for some columns An error is present in the reinforcement that is calculated for ductile columns that are subjected to the afore-mentioned redesign operations if the user performs the following steps in the sequence described i) Performs Auto-design ii) Closes the file iii) Re-opens the file iv) Performs one or more of the redesign operations described in (a) through (f) above The error is in the calculation of the main reinforcement of the column. There are chances that the final reinforcement calculated would be lesser than the required reinforcement. This issue has been resolved in RCDC V11 Update 3.1. The correct design is now performed for the various redesign operations. The provided value of the reinforcement calculated for the above various redesign operations now satisfies the steel area required to resist the loads. Column design – ACI 318 (FPS unit codes) – Issue in length parameters on redesign Screen for grouped columns/walls. After the Auto design is performed for the column/wall, RCDC allows providing various parameters on the redesign screen. It also allows modifying the length parameters on the redesign screen. Length parameters include the unsupported length and effective length factor for the selected column/walls. If the column/walls are grouped, RCDC allows providing separate unsupported length and effective length factors for each column/wall. For the ACI 318-2011, ACI 318-2014, and ACI 318-2019 (FPS unit codes) there was an error in displaying the length parameters on the redesign screen for the grouped column/walls. The values of the unsupported length and effective length factor shown on the redesign screen for grouped columns/walls were not consistent with the values calculated during auto design or values provided by the user. This error too has been resolved in the RCDC V11 Update 3.1 release. The correct unsupported length and effective length factor values are now shown on the redesign screen which should enable the user to perform the redesign operations. RCDC (SACD) Connect Edition V11 Update3 (11.03.00.141) We are pleased to announce a release of RCDC (STAAD Advanced Concrete Design / SACD) 11.03.00.141 version. This is a Minor release which consist of following features, 1. Addition of American code ACI 318-19 (English Unit) 2. Update design functionality in footing module with new analysis file- All Design codes 3. Use of different Steel grades for Main and Shear reinforcement (Beams) – All Design Codes To find out more about the features added in this release, refer the attached release note. SACD(RCDC)_Release Note - 11.03.00 RCDC (SACD) Connect Edition V11 Update2 (11.02.00.200) We are pleased to announce a release of RCDC (STAAD Advanced Concrete Design / SACD) 11.02.00.200 version. This is a Minor release which consist of following features, 1. Addition of German Annex to Euro code – DIN EN 1992-1-1/NA :2013-04 2. Addition of American code ACI 318M-19 3. RCDC compatible with Windows 11 To find out more about the features added in this release, refer the attached release note. SACD(RCDC)_Release Note - 11.02.00 RCDC (SACD) Connect Edition V11 Update1 (11.01.00.180) We are pleased to announce a release of RCDC (STAAD Advanced Concrete Design / SACD) 11.01.00.180 version. This is a Minor release which consist of following features, 1. Addition of Soil and Fluid load in the load case list 2. Addition of load type for Earthquake and Wind loads in Euro code 3. Addition of Tapered and Stepped type wall in the Tank structure module 4. Exporting Tank geometry and reinforcement data to i-twin model through ISM 5. Addition of Pile-cap deign in Australian code – AS 3600:2018 To find out more about the features added in this release, refer the attached release note. SACD(RCDC)_Release Note - 11.01.00 RCDC (SACD) Connect Edition V11 (11.00.00.143) We are pleased to announce a release of RCDC (STAAD Advanced Concrete Design / SACD) 11.00.00.143 version. This is a major release which consist of addition of Australian code and Belgium Annex for BS EN Code. AS 3600:2018 (Australian Standard – Concrete Structures) is added in RCDC. With this addition, all the structural elements can now be designed using AS 3600:2018. Pile-cap module is available as ‘tech-preview’. NBN EN 1992-1-1 (ANB: 2010) (Belgium annex) is added in RCDC. With this addition, all the structural elements can now be designed using Belgium Annex of BS EN code. BS EN 02-1-1-2004 code (the base Eurocode), is now available with a new form for input for the various constants defined in BS EN code. The design of all elements would be based on these constants. User can change these factors to suit the local design requirements. Design of tank structures is now available for the Base Euro code (BS EN 02-1-1-2004), Singapore Annex (SS NA) and Malaysian Annex (MS NA). Column Beam Joint check is now performed as per BS EN 1998-1-2004 code for Base and all Annex of Euro code. when user selects the Ductile frame as Type High, joint check would be performed. For ACI code, RCDC now allows user to define the lateral loads (Earthquake & Wind) as ‘Factored or Un-factored’. Accordingly, appropriate load factors are used to create load combinations template. In Footing design, effect of buoyancy due to water is now considered in the minimum pressure check when water table is above the foundation level. To find out more about the features added in this release, refer the attached release note. SACD (RCDC) Release Note - 11.00.00 RCDC (SACD) Connect Edition V10 (10.00.00.278) We are pleased to announce a release of RCDC (STAAD Advanced Concrete Design / SACD) 10.00.00.278 version. This is a major release which consist of addition of new code and all new tank structures design module. NSCP – 2015 – (National Structural Code of the Philippines) is added in RCDC. With the addition of this code, all the structural elements can now be designed for NSCP – 2015 New module is added in RCDC for design of tank structures (liquid retaining structures). This is now available as General release. The design would be based on EN 02 -1-1- 2004 + EN 02 -3 – 2006 UK code Calculation and design for sway shear at supports in ductile beam as per from EN 08 – 1 -2004 has been implemented for medium and high-class ductility frames. To find out more about the features added in this release, refer the attached release note. SACD (RCDC) Release Note - 10.00.00 RCDC (SACD) Connect Edition V9 Update-4 (09.04.00.128) We are pleased to announce a release of RCDC ( STAAD Advanced Concrete Design / SACD) 09.04.00.128 version RCDC will read the SRSS and ABS type load combinations available in STAAD. Load combination form would be like repeat load cases for SRSS & ABS load combinations Reinforcement detailing of Ductile Beam (clause 7.1.1 of IS 13920-2016 and 21.2.7.3 of ACI 318M-2011 ) as per column size for IS and ACI code is available. New module is added to RCDC for design of structures with tanks (liquid retaining structures). This is added as ‘Tech Preview’ feature. The design would be based on EN 02 - 2004 + EN 03 – 2006 UK code To find out more about the features added in this release, refer the attached release note. SACD(RCDC)_Release Note - 09.04.00 RCDC (SACD) Connect Edition V9 Update-3 (09.03.00.25) We are pleased to announce a release of RCDC ( STAAD Advanced Concrete Design / SACD) 09.03.00.25 version. RCDC will now read the member forces from STAAD file for Repeat Load Cases with much easier process. Two Methods are available for Column capacity calculation for Joint check as per IS 13920-2016. Euro Code enhancement related to Shear reinforcement calculation for all modules available in RCDC. To find out more about the features added in this release, refer the attached release note. SACD(RCDC)_Release Note - 09.03.00 RCDC (SACD) 09.02.00.32 RCDC 09.02.00.32 is now available with some exiting features and some important enhancements. Design of Gravity column is included in RCDC for Indian an American concrete design codes. To find out more about the features added in this release, refer the attached release note. RCDC (SACD) 09.02.00.32_Release Note RCDC (SACD) 09.01.00 We are pleased to announce a release of RCDC ( STAAD Advanced Concrete Design / SACD) 09.01.00 version. User can now design shear walls if it is modelled as a parametric surface in STAAD. To find out more about the features added in this release, refer the attached release note. RCDC v9.1.0.0 Release Notes RCDC (SACD) 9.0.0 RCDC (SACD) is coming with Major release which consist of ACI 318-2011 and ACI 318-2014 with English Unit and rebar reference numbering as per US standard. These codes will be available for all design module like Column, Beam, Footing, Pile-cap and slab. To find out more about the features in this release, refer attached release note. RCDC V9.0.0 Release Note RCDC (SACD) 8.0.1 RCDC (SACD) is coming with a minor release which consist of ACI 318-2011 and ACI 318-2014 with FPS unit and rebar reference numbering as per the US standard. Currently these codes are available for Beam design Module It also includes the Update design feature for column. The advantage of the ‘Update Design’ option is that user can check the existing design (based on earlier analysis file) with the revised analysis file. To find out more about the features added in this release, refer the attached release note. RCDC (SACD) 08.00.01_Release notehttps://communities.bentley.com/products/assetwise/asset_performance_management/w/wiki/52417/available-featuresWed, 13 Dec 2023 19:05:00 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:52417Deborah Gardiner/products/assetwise/asset_performance_management/w/wiki/52417/available-featuresThe following product features have the availability status "Available" as of the APM 24.0.0 release. They are functionally complete and have been fully tested. A feature must be manually enabled at the enterprise level before you can use it in APM. Number Feature Description 000123 Inspection factor lookup based on integrity group, degradation, criticality, and confidence factor This feature provides the ability to extend the 3-dimensional inspection factor matrix to a fourth dimension, integrity group. This new capability allows you to define the Inspection Factor, Inspection Strategy, and Inspection Interval based on degradation type, criticality, confidence factor, and integrity group. Integrity group is identified on asset types, allowing an easy mechanism to group similar assets. For example, integrity groups can be created for piping systems, vessels, and heat exchangers. 000122 Standard task solution package data loader This feature introduces a new Standard Task Solution Package data loader. The data loader allows solution package references, including the four solution package references and cycle to be loaded for one or more standard tasks. The data loader is included as part of the Reliability Management data loaders on Enterprise. 000119 Solution package identification on standard task This feature introduces the ability to identify the solution packages to reference on a checksheet's request for work. 000118 Checksheet splitting This feature introduces the ability to split the readings on a checksheet across two or more checksheets. 000117 Ability to defer standard task next due date calculation until inspection is complete This feature introduces the ability to defer the calculation of the standard task's next due date until its open checksheets are completed. 000115 Practical RBI - criticality evaluation calculations This feature introduces the ability to automate the process of analyzing a failure mode's criticality through the use of lookup tables and delivered calculations. The ability for the user to define their own custom calculations is also supported. 000114 Ability to identify start and end locations on a video on indicator and measurement point reading This feature introduces the ability to identify one or more videos to a checksheet. Once the videos have been linked to the checksheet, the locations on the video where an anomaly can be seen can be identified on individual readings. Inspection videos are typically used in places where inspectors cannot access the equipment or structure themselves and an unmanned vehicle is used. 000113 Support for drilling platform asset specifications This feature introduces support for asset properties related to oil drilling platforms. 000112 Support for the ability to add readings to a checksheet based on the value of a reading This feature introduces the ability to have additional conditional readings added to a checksheet based on the state entered for a reading. For example, if an indicator is in alarm, additional checks or readings need to be taken. These additional readings are only required if the first reading is in alarm. With this feature, you can identify the conditional indicators as part of the indicator state properties. 000111 Solution package data loader This feature introduces two new data loaders for solution package tasks. The first allows the standard tasks associated with a solution package to be created or updated. The second allows task templates associated with a solution package template to be created or updated. 000110 Indicator due date data loader This feature introduces a new Indicator Due Date data loader. The data loader allows new due dates to be loaded for one or more indicators. The data loader is included as part of the Inspection Management data loaders on Enterprise. 000109 Prevent redrafting of a checksheet based on the checksheet status This feature introduces the ability to control the availability of the redraft method based on the checksheet status. 000108 Anomaly risk assessment This feature introduces the ability to integrate APM with an Anomaly Assessment and Tracking (AA&T) system. 000107 Calibration template support This feature introduces the ability to define calibration templates. Calibration templates can be used to provide default values for a checksheet subtype. Currently, five subtypes are supported to enter calibration details on a checksheet: Ultrasonic calibration, Radiography calibration, dye penetration inspection, magnetic particle inspection, and eddy current inspection. Calibration templates can be created for each subtype. 000106 Option to limit an asset status change to the current asset only This feature introduces the ability to limit an asset status change to the current asset only. The status of the asset's descendants is not updated. 000105 Support the ability to update the warehouse item's storage locations when entering a count This feature introduces the ability to correct the warehouse item's inventory storage locations when recording a count. The warehouse item's locations are updated when the resulting adjustment transaction is posted. 000104 Support for displaying asset PI&D or other document as part of the asset specifications This feature introduces the ability to display an asset document as part of the asset's specifications. The document displayed can be any document linked to the asset and can be a PDF, graphic image, Word document etc. 000103 Support for Platform Inspection subtypes on Measurement Point Readings This feature introduces the ability to record information related to platform inspections. It controls access to the following subtypes for measurement point readings: ·Platform general visual inspection ·Platform debris ·Platform scour ·Flooded member detection ·Weld survey ·Platform cathodic protection 000102 Support structural minimum thickness when calculating an asset's minimum thickness This feature expands the existing minimum thickness calculation function to include support for Structural Minimum Thickness. 000099 Support for reliability projects This feature expands the functionality associated with projects to allow the different types of analyses and other objects to bel linked to a project. The types of objects that can be linked to a project are: Strategy development analysis Asset prioritization analysis Asset condition analysis Reliability strategy selection analysis Failure or anomaly Root cause analysis Safety provision version Asset restoration plan SDA study 000098 Support for project tasks This feature introduces the ability to identify tasks to be performed for a project. Project tasks provide a simple method of identifying tasks or actions to be performed without requiring the use of work orders or tasks. Project tasks have a limited set of properties and are not meant to replace work orders and tasks in cases where work planning is required. 000097 Support site filtering rules of analysis team members This feature introduces the ability to control the employees who can be selected as team members. The new settings allow you to allow employees from: The same site as the analysis The same site and its higher level sites The same site and its lower level sites Sites in the same branch of the site hierarchy Any site These options apply to team members on a strategy development analysis, asset prioritization analysis, asset condition analysis, and RCA. 000096 Support for Dead Leg Piping section asset specifications This feature introduces the ability to define properties related to a dead leg piping sections on an asset's specifications. 000095 Support for Fabric Inspection subtype on Measurement Point Readings This feature introduces the ability to record information related to fabric or structure inspection for an oil drilling platform. 000093 Support for Oil Drilling Platform asset specifications This feature introduces the ability to define properties related to an oil drilling platform on an asset's specifications. 000092 Publish indicator readings to an external system This feature introduces the ability to publish indicator readings to an external system such as SAP or Maximo. 000091 Support for Oil and Gas asset specifications This feature introduces support for asset properties related to the oil and gas industry. 000090 Support display of an indicator's measurement point values in a grid format This feature introduces the ability to display an indicator reading's measurement point values in a grid format. The ability to compare the values for two readings is also supported 000089 Standard task due date data loader This feature introduces a new Standard Task Due Date data loader. The data loader allows new due dates or proposed due date to be loaded for a standard tasks. The data loader is included as part of the Inspection Management data loaders on Enterprise. 000088 Maintenance action plan corrective task data loader This feature introduces a new maintenance action plan inspection task data loader. The data loader allows corrective tasks and corrective solution packages to be loaded for maintenance action plans. 000087 Maintenance action plan inspection task data loader This feature introduces a new maintenance action plan inspection task data loader. The data loader allows inspection tasks to be loaded for maintenance action plans. 000085 Asset prioritization and condition analyses data loaders This feature introduces two new data loaders to the APM collection of data loaders: Asset prioritization analysis data loader and the asset condition analysis data loader. The asset prioritization analysis is part of the strategy development data loaders. The asset condition analysis is part of the asset health data loaders. 000084 Create checksheet from Interop work orders' and work requests' recommendations from events This feature introduces the ability to create a checksheet based on the recommendations from event on both Interop work orders and work requests. Solution packages are not required to generate the checksheets. When the features is enabled, the Create Checksheet (From Template) action is available on a task template. 000083 Ability to create a checksheet from a Task Template This feature introduces the ability to create a checksheet directly from a task template. When the features is enabled, the Create Checksheet (From Template) action is available on a task template 000082 Allow Interop Work Order and Interop Work Request to be manually set on a checksheet This feature allows users to manually select the source Interop Work Order and Interop Work Request on a checksheet. The source Interop Work Order and Interop Work Request references are typically set when the checksheet is created from the work order or linked to a work request. This feature allows users to set the link in cases where it was not automatically set. For example, if a checksheet is manually created and is related to a work order, the link can be manually set. 000081 Data loaders for degradation rates This feature introduces two new data loaders: Asset degradation rate data loader and Indicator degradation rate data loader. 000079 Data loader for Measurement Point readings This feature introduces a new data loader for Measurement point readings. 000078 Approvals support for requests for work This feature introduces support for approvals for Requests for Work. When the feature is enabled, standard APM approvals support is available for Requests for Work. 000077 Support for Interop work document change requests Work document change requests are used to request changes to an Interop Work Order or Interop Work Request. A change request can request: An update to the document's work status. For example, request that an SAP Maintenance Order be updated to TECO (technical complete) when the work is completed Enter a new comment Record hours work Update a Recommendation for Event as completed Record the actual start and end dates for the work Request the planned start and end dates be updated Change requests can also request that any of the user flex fields be updated. The user flex fields consist of 10 string fields, 5 date fields, 5 check boxes, and 5 reference numbers. When a change request is entered, it is communicated to the CMMS via AssetWise Interoperability where it is processed. If the request is accepted, the CMMS work order or request is updated. The APM copy of the work order or request is updated when the Sync Document object is received from AssetWise Interoperability. The APM document is only updated after the request is accepted and processed by the CMMS Work Document Change Requests are only available when AssetWise Interoperability is being used. 000076 Support for asset links This feature introduces the ability to link 1 to 5 assets to another asset. For example, in a electrical distribution network, the network protector and network switch can be linked to their transformer. The asset links can be manually maintained or automated using rules defined on the asset type. 000075 Support for user asset specifications This feature provides the ability to extend an asset's information through the use of User Asset Specifications. User asset specifications include support for the following properties: 5 string attributes 5 check boxes 5 dates 5 decimal number Using the settings of class User Asset Specification Settings, you can identify which of the 20 properties are being used. You are able to provide a name for each property used. Settings on asset type allow you to identify if user asset specifications are used with assets of a type. You can identify the user asset specification settings to use. This allows different properties to be used with different types of assets. User asset specifications are also a convenient location for adding custom properties to asset. 000074 Support for type of inspection evaluation as part of the failure mode RBI analysis This feature introduces a new step in the RBI Analysis process: the type of inspection analysis. Type of inspection analysis is performed after the confidence analysis. The results of the type of inspection can identify if an internal, external, in-service or out of service inspection is required. 000073 Support for circuit assets Ability to link circuits and the assets on a circuit. A circuit can identify things like an electrical circuit or corrosion loop. When this feature is enabled, you can identify up to 10 circuits that include the asset. An unlimited number of assets can be included on a circuit. To enable circuit support, there are settings on the asset type. For each type of asset you can: Identify that assets of the type can be included on a circuit Identify that assets of the type are a circuit On assets included on a circuit, you can view the list of circuits that asset is a part of. For a circuit asset, the Circuits view is visible. On this view, you can see the circuit's assets and a variety of information about the circuit and its assets, including: Process description Degradation information Operating parameters Failure modes Barriers Indicators Standard tasks Solution packages if you are using AssetWise Interoperability Work orders The Circuits tab on the site's assets view shows you a list of all the circuits at a site. The same level of information is displayed for each circuit as on the asset's Circuits view. When the feature is enabled you can: View the indicators associated with the circuit's assets when browsing indicators. For example, when browsing for indicators to include on a standard tasks or maintenance action plan. you can view the indicators for the circuit's assets Include the circuit's assets when creating the assets for a strategy development analysis 000069 Ability to link checksheets and Interoperability work requests This feature introduces the ability to link an Interop work order's checksheets to Interop work requests related to the work order. When the feature is enabled, the Checksheet and work request linking group box is included on the Checksheet Generation tab under the Checksheet settings the Inspection Management Settings. The settings in the group box are used to enable checksheet and work request linking. Work request and checksheet linking is only applicable when AssetWise Interoperability is being used. 000068 Support for follow-up requests for work This feature introduces the ability to generate a request for work based on the completion of a interop work order or work request. 000065 Display asset properties on selected objects This feature provides the ability to display a set of asset properties on the following objects: Checksheet Indicator reading Request for work When the feature is enabled, you are able to define at the asset type level on which objects you want asset properties displayed and the panel to use. An Asset Properties view (on checksheet) or page (Indicator Reading and Request for Work) is added to the user interface if the asset's asset type has enabled support for displaying asset properties. 000064 Ability to restrict the priorities used on a work request based on the maintenance group This feature provides the ability to define the available work priorities based on the maintenance group assigned to a request for work. When the feature is enabled, a new Priorities tab is displayed on the Maintenance Group Properties. On the Priorities tab, available priorities are restricted to the priorities identified on the maintenance group. When creating a request for work, the priorities available for selection are limited to the priorities that are valid for the maintenance group. The ability to restrict priorities based on maintenance group is only available when AssetWise Interop Work Documents are being used. 000063 Ability to make the creation of the work document mandatory on an indicator reading This feature introduces the ability to make the creation of a work document (request for work) mandatory based on the indicator state. This feature expands on the existing ability to create a work document as part of an indicator reading by making the creation of the work document mandatory. A new setting has been added to indicator state to make the work document mandatory. The ability to create a work document as part of an indicator reading is only available when using AssetWise Interoperability. 000062 Distribution Network work information on AssetWise Interoperability work documents This feature extends the information supported on AssetWise Interoperability work documents. The information includes properties related to working on electrical equipment in an urban area. This includes: How was the work identified High public exposure Commercial or industrial customer Urban area Remote or low population density area High fire risk area A waterway Is a traffic plan required Is flagging required Is this a customer issue Is a underground safety alert required Is a city moratorium on work active Is this a urban wildlife area Is the work related to a substation Is the work related to a company or regulatory board audit Does the work require verification Distribution network information is available for entry on a request for work, when acknowledging an alarm, creating a work document as part of an indicator reading, follow up work requests and other places where work can be initiated in APM. The information is also visible on Interop work requests, Interop work orders and solution packages. This feature is generally available. 000061 Regulatory reporting tracking support on assets This feature introduces the ability to track regulatory reporting information on assets When it is enabled, you can track up to three levels of regulatory information for an asset. For example, federal regulations, regional regulations, and industry organization requirements could be tracked. For each regulatory requirement being tracked you can: Identify the agency (Federal government, Regional government etc.) Define up to 10 check boxes. You are able to provide the text for each of the check boxes being used. For example, OHS Regulations, Federal environmental regulations, Provincial safety codes, and so on. A maximum of 100 characters can be entered to describe each check box Define up to 5 reporting dates. You are able to provide the name of each date being used. For example, last date reported on and next report due on could be the names for two of the dates Define up to 5 text attributes If regulatory reporting is supported, you can identify by the type of asset. 000060 Collector's note mandatory based on type of alarm and marking asset as unavailable for reading Ability to make it mandatory to enter collector's notes on manually-entered indicator readings, based on the alarm type or if the asset is unavailable for reading. This feature is generally available. 000058 Notes support Notes or asset notes allow notes to be added to a number of APM objects. See the list below. Each note consists of: A short description or title The note Time stamp information of when the note was entered and who entered it Optionally, a note can be reviewed. Reviewing a note allows a user to respond to the original note. The note type controls whether review is supported for a note. Depending on the source of the note, the note is also linked to related objects. As an example, a indicator reading note is also linked to the indicator and the checksheet the reading is on. Notes related to an asset-specific object are also linked to the asset. For example, a standard task note is linked to the standard task's asset. Notes are supported for the following types of objects: Asset Asset activity analysis Asset change request Asset health index Asset program profile Cable splice Check sheets Gas transaction Indicator, including indicator templates, KPIs and KPI templates Indicator readings Interop work order and work request Lab fluid sample Production loss event Request for work Safety override incident Standard tasks, including task templates 000057 Default approval route support Ability to identify a default approval route to use when an approval request is created. Default approval routes can be identified for each type of document that supports approval. A default set of approval routes can be identified for both employees and site. When an approval request is created, the current employee is checked to see it a default route has been identified. If a default route has been identified, it is used. If an employee default has not been identified, the system checks for a site default. The site default, if identified, is used. 000056 Review or approval support for Asset Change Requests This feature introduces the ability to implement the review or approval process for asset change requests. The review process is an informal process where a user with the appropriate security privileges can mark an asset change request as reviewed. The approval process is a formal process that uses APM approvals. When the approval process is used, asset change requests are submitted for approval. One or more approvers are required to approve the request before it can be sent to your asset registry system Asset change requests only apply when Bentley AssetWise Interoperability has been implemented. The objects associated with this functionality include: Asset change request Asset change request type Approval route Approval request 000055 Ability to request changes to asset properties outside of a construction form Asset change requests were introduced as part of Construction Management. They are used to communicate information to the external CMMS that owns assets. The asset update is performed in the CMMS and the resulting asset update request is then communicated to APM. The purpose of the functionality is to support the ability to initiate a properties change outside of a construction form. As with asset change requests initiated from a construction form, the new asset change request is only used when AssetWise Interoperability is used. The request is communicated to your asset registry system (typically your CMMS). The asset registry system accepts the request and updates its records. An Asset Sync event is then sent to APM, resulting in the APM asset being updated. Asset change requests only apply when Bentley AssetWise Interoperability has been implemented. The objects associated with the new asset change request capability include: New asset change request Asset change request type Asset change request status Asset change request template Approval request 000054 Fluid condition tracking and results This feature allows you to enable the APM Fluid Condition function. Fluid Condition allows you to export and import fluid samples to a Fluid Analysis Lab and record the results on a Fluid Condition checksheet. Enabling the feature allows you to: View the Fluid Analysis view on site and asset Define the values lists and settings that pertain to fluid condition Export fluid samples to either an internal or external fluid lab Import the results of the lab analysis into a fluid condition checksheet for review Monitor trends for the indicators used to track the fluid condition 000053 Fluid sample support This feature allows you to enable the ability to record information pertaining to a fluid sample on an Indicator Reading. Enabling the feature allows you to: Identify on an indicator that the indicator is used for record fluid sample information Identify on an indicator state that a sample was taken and allows the sample values to be entered on the reading Enter fluid sample information on an indicator reading When the feature is disabled, the fluid sample properties on indicator type, indicator, indicator state and reading are hidden. 000052 Remove overrides from a task template's standard tasks Support the ability to remove the overrides from Standard Tasks based on a Task Template. This feature introduces the ability to remove the overrides from a task template's standard tasks. Previously, it was necessary to open each standard task and remove its overrides. When this feature is enabled, it is now possible to remove the overrides from the task template itself. When performed, a list of the template's standard tasks with overrides is displayed. Select all or some of these standard tasks and click OK. The overrides are removed from the selected standard tasks. This feature is generally available. 000051 Support generation of checksheets for standard tasks without requiring a work order Support the Generation of Checksheets for standard tasks This feature introduces the ability to generate checksheets from APM standard tasks without requiring the use of work orders. When this feature is enabled, you are able to identify that a standard task does not require a work order. The standard tasks checksheets can be generated directly from the standard task. The standard task must be configured to track its due date. The task due date can be based on its frequency or indicators due dates. A new scheduled action is used to generate the checksheets on a recurring basis. This functionality is used to support Operator Care Rounds or Operator Inspections. This feature is generally available. 000050 Support ability to limit the duration that is scheduled for a work order task Support the ability to limit the duration scheduled per shift for a work order task This feature allows you to set a limit to the amount of time allocated to each shift when the work is scheduled. As described by the customer who submitted the request: I would like to see an enhancement made to the system so that a work task can be flagged or limited so that it will only schedule a portion of the hours for a shift and if possible, it would schedule it on consecutive days for the same number of hours until the hour requirement is met. What I would like to see it a way to make a weekly work order task (PM) that can be used for each day of the week but limit its hours for each day. For example, if you had a work order that required 15 hours per week, but you need to spread that out based on 3 hours per day on Monday through Friday without creating 5 separate tasks for 3 hours each. I have seen this done in other systems using the duration field to calculate this out. It had the option (a check-box was available when this option was desired) to manually enter a duration (rather than auto calculate) after the number of craftsmen and hours were entered on the order. If you stated that you needed 15 hours of work scheduled over a duration of 40 hours (settings for the day are 8 hours per day), then when you schedule that work order it would break it up into 5 consecutive days with 3 hours per day scheduled for that order. When the feature is enabled, you are able to identify that the work is to be limited to a set duration when it is scheduled. The scheduling limit can be defined on a standard task and is copied to the work order task. The limits can also be defined directly on the work order task. This feature is generally available. 000049 Link an acknowledgment to a work document with AssetWise Interoperability This feature allows you to acknowledge an indicator alarm by referencing an existing Request for Work, Interop Work Request, or Interop Work Order. When an alarm is acknowledged with an existing work document, a new Request for Work is not created. No information is passed to the CMMS. The link to the existing work document remains known to APM only. It is assumed the user knows that the scope of the existing work addresses the new alarm. When the feature is enabled, you are able to identify that an alarm is being acknowledged with an existing work document. The existing work document must be identified. When the feature is disabled, alarms can only be acknowledged with a new Request for Work. 000048 Support for user defined fields on AssetWise Interoperability Work Documents Support for user-defined fields with AssetWise Interoperability This feature allows you to extend the information on the Interop work documents to include a number of user fields. The user fields consist of: 10 string attributes named User String 1, User String 2, User String 3, User String 4, User String 5, User String 6, User String 7, User String 8, User String 9, and User String 10 5 date attributes named User Date 1, User Date 2,User Date 3,User Date 4, and User Date 5 5 check box (Booleans) named User Check Box 1, User Check Box 2, User Check Box 3, User Check Box 4, and User Check Box 5 When the feature is enabled, you are able to identify the user fields to be used and name each of the used fields. Additionally you are able to identify if any of the used fields are mandatory or read only by work type and site. User fields are supported on Interop work order, Interop work requests, solution packages, and requests for work. This includes all places where a request for work can be initiated, such as an alarm acknowledgment or follow up work request. When the feature is disabled, the user fields cannot be used. This feature is generally available. 000046 Failure codes support with AssetWise Interoperability Support for additional failure codes with AssetWise Interoperability This feature allows you to define the failure codes used on Interop work documents and failures. Enabling the feature allows you to: Use object part, damage and activity codes Use up to five flexible failure codes. When the failure codes are being used, you are able to identify the number of failure codes are used (1, 2, 3, 4, or 5),name each of the codes and identify which codes are mandatory on a work document Turn off failure codes When the feature is disabled, Object part, damage codes and activity codes are used. This feature is generally available. 000042 Support for critical parts identification on a maintenance action plan Critical Parts Analysis on a Maintenance Action Plan This feature provides the ability to identify the critical parts, or spares, required for a failure mode's action plans. The feature includes: The ability to define a catalog of critical parts The ability to identify the critical parts for a failure mode's action plans. The critical part can be identified by selecting the critical part from the critical parts catalog, a material resource form the resource catalog or by identifying the part directly on the action plan critical part record A list of all the parts required for an analysis as part of the Analysis Summary view Critical parts can be identified on all types of strategy development analyses, including templates. This feature is generally available. 000039 Criteria based probability evaluation on an asset prioritization analysis Criteria-based probability of failure evaluation as part of an asset prioritization analysis Provides the ability to assess the probability of failure for an asset based on multiple criteria when performing an asset prioritization analysis. The feature includes: Ability to identify the method used to analyze the probability of failure. The two supported methods are selecting the probability of failure from a list of probabilities or performing a formal analysis Ability to identify multiple criteria that are used to assess probability of failure Ability to identify multiple details for each probability of failure criterion Ability to identify the selection policy for the probability of failure Ability to analyze probability of failure as part of the asset's prioritization analysis When this feature is enabled, you are able to identify the method used to analyze the probability of failure. The two supported methods are by selecting the probability of failure from a list of probabilities or performing a formal analysis. If the feature is not enabled, only the simple method is available. This feature is generally available. 000036 Updating existing data to be ready for use with AssetWise Interoperability Updating data to be ready for AssetWise Interoperability Before implementing AssetWise Interoperability, it is necessary to update existing data objects to be ready for use. This is done by creating and processing AssetWise Data Readiness Requests. One or more AssetWise Data Readiness Requests are required for each type of object for which you have existing data that needs to be updated. Refer to the product implementation guides for more information. When this feature is enabled, you are able to create instances of AssetWise Data Readiness Requests from the Data Readiness Requests tab on the Interoperability Settings tab on the Enterprise's Integrations view. When the feature is disabled, the Data Readiness Requests tab is hidden. This feature is generally available. 000034 Advanced production loss accounting Advanced production loss accounting Provides additional functionality related to production loss accounting: Ability to identify multiple products per asset Ability to link production loss equations to a specific product Support for Production Loss Events When this feature is enabled, you are able to identify the production loss accounting level as basic or advanced for each site. Basic production loss accounting is based on downtime incidents and a single product per asset. Advanced production loss accounting enables the new functionality. The production loss accounting level is identified on the site's production view settings. This feature is generally available. 000033 Hierarchy recursion support for exports Hierarchy Recursion Support on Reports This feature enables the ability to define reports with hierarchy recursion support, for example, a list of Requests for Work for an asset and its descendants or a list of Requests for Work for a site and its ancestors. This feature is generally available. 000032 Integration with 4D Analytics This feature enables the ability to integrate APM with 4D Analytics system. The 4D Analytics integration allows you to view the readings history for an indicator where the readings are stored in the 4D Analytics system. Currently, 4D Analytics integration is only available if you are using SQL Server DBMS. 4D Analytics does not work with a Oracle DBMS. 000028 Asset change requests Asset Change Requests Asset change requests are used to communicate information to the external CMMS that owns assets. The asset update is performed in the CMMS and the resulting asset update request is then communicated to APM. Asset change requests only apply when Bentley AssetWise Interoperability has been implemented. Three types of asset change requests are supported: Property changes - Used to request a new asset or property updates to existing assets. This type of asset change request is currently only initiated from a construction form Asset status change - Used to request a change to an asset's status. Asset status change requests are currently only initiated from a work order's asset inspection status Remove equipment request - Used to request that an asset be removed from its current location and move to another location The objects associated with asset change requests include: Asset change request Asset change request type Asset change request status This feature is generally available. 000027 Asset program profile Asset Program Profiles This feature consists of a set of new objects that are used to generate reliability and inspection programs for assets. The objects associated with asset program profiles include: Asset program profiles - used to group a set of asset program profile details and processing rules Asset program profile details - filters used to identify the assets that the rules apply to, the inspection and reliability templates used to create the assets' objects, and the standard documents to assign to assets Generate Asset Program scheduled action - automatically updates the site's assets at predetermined intervals Asset program profiles can be created from the Assets view, Program Profiles tab. Asset programs can be manually generated from assets, asset program profiles, and the site. The features does not control the availability of the asset program profile functionality in the context of construction forms. This feature is generally available. 000024 Allowing work orders with multiple assets to be sent to SAP Allow work orders with multiple assets to be sent to SAP This feature allows work orders with tasks for different assets to be sent to SAP. Otherwise, only work orders where all of the tasks are for the same asset can be sent to SAP. When enabled, work orders with tasks for different assets can be sent to SAP. If the feature is enabled, the base product transform that converts the APM work order to a SAP maintenance order does not communicate the different assets to SAP. Only the primary task asset is sent to SAP. It is your responsibility to update the transform. This feature is generally available. 000023 Asset characteristics Asset Characteristics Support This feature consists of a set of objects that are used to import asset characteristics from an external CMMS (e.g. SAP). Once imported, the characteristic values can be mapped to asset properties, enabling standard system functions like: Ability to view the value on an Asset properties tab like the other asset properties Ability to include the property as a column on an asset configuration. This allows all of the standard configuration functions to be used, including: Filtering, including filter sets which use more than 1 characteristic value Sorting Grouping Counts Using the property as an input for a calculated indicator or KPI The objects associated with asset characteristics include: Characteristic class - used to group a set of characteristics Characteristic - a specific characteristic that is tracked Asset characteristic - the value for a characteristic for a specific asset Characteristic mapping set - used to define the rules for mapping data between asset characteristics and asset properties Data loaders for characteristics and asset characteristics - in the absence of an automated interface, data loaders can be used to import characteristic values This feature is generally available. 000022 Construction management Construction Management This feature consists of a set of new objects that are used to manage equipment construction activities performed by field crews at your facilities. The objects associated with construction management include: Construction forms - used to identify the equipment installed as part of a construction job. The equipment can be existing equipment that is being installed at a new location or new assets Construction form templates - used to identify the content, rules and behavior of the construction form Construction management is a view on both site and asset. This feature is generally available. 000021 Regulated gas management Regulated Gas Management This feature consists of a set of new objects that are used to manage regulated gases at your facilities. For example, you can manage activities related to sulfur hexafluoride (SF6), which is a highly regulated gas in some jurisdictions. When enabled, the feature can be used to track all activities for a type of gas. The objects associated with regulated gas management include: Gas type - used to identify a regulated gas being tracked Gas container - identifies the different types of containers (cylinders, bottles, etc.) the gas is stored in Gas vendor - identifies the vendors from whom the gas is purchased. Includes the ability to link the gas vendor to a purchasing supplier Gas transaction type - used to identify the different types of transactions performed for the gas and the characteristics and behavior of each Gas transaction - used to track all activities related to a regulated gas includes receipts and returns to vendors, equipment fills, container weights and loss to atmosphere events Regulated gas management is a view on both site and asset. This feature is generally available. 000017 Data loader for user site security profiles This feature consists of a new data loader for User Site Security Profiles. When enabled, this feature can be accessed from the Data Loaders view on Enterprise under the Personnel tab. 000009 Time zones by site Time Zones by Site This feature allows you to have a different time zone for each of your sites. Currently, all sites must use the Enterprise time, whether they are in the same time zone or not. When a different time zone is specified for a site, all date and time data will be displayed using the time zone selected. As always, all date and time data will continue to be stored on the database in Coordinated Universal Time format (UTC). When enabled, the time zone for a site can be set via its Properties dialog. This feature is generally available.https://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki/68316/dialogs-are-not-visible-or-will-not-openWed, 13 Dec 2023 16:00:00 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:68316Kara Goodwin/products/road___site_design/w/road_and_site_design__wiki/68316/dialogs-are-not-visible-or-will-not-openProduct: OpenRoad SignCAD 2023 Version: 23.00.00.151 Area: Troubleshooting Original Author: Bentley Global Technical Support Problem: Dialogs are not visible or will not open when using OpenRoads SignCAD. Solution: 1) If you are using multiple monitors, the dialog may be open off screen somewhere or displaying on another monitor. One of the simplest ways to test this is simply disconnect/disable one of the monitors and the dialog should be forced onto the screen. 2) Try raising your screen resolution since your monitor's resolution may be too low. A recommended screen resolution is 1920x1080. The steps to do this vary with the operating system and video card being used. Generally, the screen resolution can be changed by going to the Control Panel , opening the Display category and then selecting Screen Resolution . 3) Maximize the dialog in the Taskbar. Locate the OpenRoads SignCAD windows on the taskbar at the bottom of your screen and hover over it so you can see the windows open in that program. See the screen shot above. Right-click on the window that you cannot see (ex: Place Text dialog) and select "Maximize". The window should now cover the screen. Simply grab the window by left-clicking at the top of the window and dragging it down. 4) Close OpenRoads SignCAD. In File Explorer, browse to the C:\Users\firstname.lastname\AppData\Local\Bentley\OpenRoads SignCAD 2023.00 folder. Open the User.xml file in Notepad. Change the X, Y settings to 0 and save the changes to the file in Notepad (File>Save). Launch OpenRoads SignCAD and select different tools to see if the dialogs display correctly. 5) Delete the User.xml file. Navigate to C:\Users\firstname.lastname\AppData\Local\Bentley\ OpenRoads SignCAD 2023.00 and delete the User.xml file. Once the file is deleted, launch OpenRoads SignCAD and select different tools to see if the dialogs display correctly.https://communities.bentley.com/products/programming/microstation_programming/f/microstation-programming---forum/253245/mdl-native-code-programming---dialog-manager---publish-nested-structure/792974Wed, 13 Dec 2023 12:12:00 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:792974Benzi Papo/products/programming/microstation_programming/f/microstation-programming---forum/253245/mdl-native-code-programming---dialog-manager---publish-nested-structure/792974I tried something simple. Open the BasicDialogBox example from the MicroStation 2023 SDK and make two minor changes: Open basic.h and change the declaration of parameter1 to float : typedef struct basicglobals { float parameter1; /* used by text & option button item */ int parameter2; /* used by toggle button item */ } BasicGlobals; #endif Open basic.r and change the dialog text item format to "%f" : DItem_TextRsc TEXTID_Basic = { NOCMD, LCMD, SYNONYMID_Basic, NOHELP, MHELP, NOHOOK, NOARG, 4, "%f", "%f", "1", "3", NOMASK, NOCONCAT, TXT_Parameter1, "basicGlobals.parameter1" }; Now compile and load the app. You will see that parameter1 displays 0.0 even though it was initialized here: Private BasicGlobals basicGlobals = {1, 0}; Now change the declaration of parameter1 to double and "%lf" respectively. Compile and load again. Now parameter1 displays 1.0 as expected.https://communities.bentley.com/products/programming/microstation_programming/f/microstation-programming---forum/253531/mdl-s-decompiler/792946Wed, 13 Dec 2023 09:10:00 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:792946Jan Šlegr/products/programming/microstation_programming/f/microstation-programming---forum/253531/mdl-s-decompiler/792946[quote userid="1541565" url="~/products/programming/microstation_programming/f/microstation-programming---forum/253531/mdl-s-decompiler/792940"]My initial idea was to decompile the encapsulated MA file into any visual code through some means, such as MDL that can be opened in MicroStation V8i, and then learn the logic behind it to develop a similar tool in VS[/quote] So you are experienced C developer with MDL API knowledge? Because MDL code looks typically like this (or simpler, but can be even worse): Private void hideExample_dlogHook ( DialogMessage *dmP /* => a ptr to a dialog message */ ) { dmP->msgUnderstood = TRUE; switch (dmP->messageType) { case DIALOG_MESSAGE_DESTROY: { mdlDialog_cmdNumberQueue (FALSE, CMD_MDL_UNLOAD, mdlSystem_getCurrTaskID(), TRUE); mdlState_startDefaultCommand (); dmP->msgUnderstood = FALSE; break; }; default: dmP->msgUnderstood = FALSE; break; } } [quote userid="1541565" url="~/products/programming/microstation_programming/f/microstation-programming---forum/253531/mdl-s-decompiler/792940"]I just want to know the logic of its work and then use Visual Studio for development, not in MicroStation V8i. This may be a clever approach.[/quote] I do not quite understand the plan. Any development for MicroStation V8i can be done in any editor, not specifically Visual Studio, although it is probably the best tool. But it is editor only, more important is used compiler and linker (regardless C++ or NET is used), because it must respect requirements of the used MicroStation version (which for V8i was NET Framework 3.5 in the case of C#). [quote userid="1541565" url="~/products/programming/microstation_programming/f/microstation-programming---forum/253531/mdl-s-decompiler/792940"]I just want to know the logic of its work[/quote] Often better source of information is user and/or technical documentation, when the new code is written to follow the described workflows and requirements. [quote userid="1541565" url="~/products/programming/microstation_programming/f/microstation-programming---forum/253531/mdl-s-decompiler/792940"]I will not write program for MicroStation.[/quote] The context is not clear. So you application is a kind of interface, that communicates with MicroStation session, but controlled by some other program? [quote userid="1541565" url="~/products/programming/microstation_programming/f/microstation-programming---forum/253531/mdl-s-decompiler/792940"]The reason why I chose V8i SS3 is that this MA file seems to have been written in a very early version, and the developers at that time were no longer able to contact, so choosing an older version of the software may avoid compatibility issues.[/quote] It depends what you mean "very early version". If it was written for MicroStation/J or older, it is incompatible anyway, because it was based on old DGN V7 format with different structure and features than currently used DGN V8. it is not clear what you mean by "compatibility issues", because to chose so old version like V8i brings compatibility issues anyway: Not supported by Bentley Not certified for newer Windows Obsolete programming platforms (VS 2005 for C/C++ and NET Framework 3.5 for NET) Limited APIs (especially for NET, because of sharing API with VBA/COM). [quote userid="1541565" url="~/products/programming/microstation_programming/f/microstation-programming---forum/253531/mdl-s-decompiler/792940"]It seems an impossible solution now...[/quote] Yes, when you have no source codes. Regards, Janhttps://communities.bentley.com/products/programming/microstation_programming/f/microstation-programming---forum/253245/mdl-native-code-programming---dialog-manager---publish-nested-structure/792933Wed, 13 Dec 2023 08:29:00 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:792933Jan Šlegr/products/programming/microstation_programming/f/microstation-programming---forum/253245/mdl-native-code-programming---dialog-manager---publish-nested-structure/792933[quote userid="849891" url="~/products/programming/microstation_programming/f/microstation-programming---forum/253245/mdl-native-code-programming---dialog-manager---publish-nested-structure/792914"]The interesting thing is that the generated R file is identical when using either float or double variable declarations.[/quote] Maybe it is because in 64bit world, the smallest alignment unit are 8 bytes, so float (4 bytes) are aligned to be 8 bytes? [quote userid="849891" url="~/products/programming/microstation_programming/f/microstation-programming---forum/253245/mdl-native-code-programming---dialog-manager---publish-nested-structure/792914"]All dialog box text items use the "%lf" format.[/quote] But %lf" is for double. Did you try to use "%f"? Regards, Janhttps://communities.bentley.com/products/programming/microstation_programming/f/microstation-programming---forum/253245/mdl-native-code-programming---dialog-manager---publish-nested-structure/792914Wed, 13 Dec 2023 05:45:00 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:792914Benzi Papo/products/programming/microstation_programming/f/microstation-programming---forum/253245/mdl-native-code-programming---dialog-manager---publish-nested-structure/792914The interesting thing is that the generated R file is identical when using either float or double variable declarations. All dialog box text items use the "%lf" format. So I'm not really sure how the dialog manager distinguishes float from double . Here is one of the published structure definitions: typedef struct feature { // description WChar feaName[512]; // input area symb UInt32 areaFeaLevelCode; UInt32 areaFeaColor; UInt32 areaFeaWeight; Int32 areaFeaStyle; // border define int areaDoBorder; double areaBorderWidth; // background define int areaDoBackground; // single hatch int areaDoSingleHatch; double areaShatchSpacing; int areaShatchAngle; // cross hatch int areaDoCrossHatch; double areaChatchSpacing1; int areaChatchAngle1; double areaChatchSpacing2; int areaChatchAngle2; // patterning int areaDoPattern; int areaPatternAngle; double areaPatternRSpace; double areaPatternCSpace; double areaPatternScale; WChar areaPatternCell[512]; // multi color hatch int areaDoMultiHatch; double areaMhatchWidth1; double areaMhatchWidth2; double areaMhatchWidth3; int areaMhatchAngle; double areaMhatchSpacing; int areaMhatchDraw1; int areaMhatchDraw2; int areaMhatchDraw3; // display int areaDispDoGroup; UInt32 bckDispLevelCode; UInt32 borDispLevelCode; UInt32 shtDispLevelCode; UInt32 chtDispLevelCode; UInt32 mh1DispLevelCode; UInt32 mh2DispLevelCode; UInt32 mh3DispLevelCode; UInt32 symDispLevelCode; // include int areaIncludeAsArea; // feature code WChar feaCode[512]; } FEATURE; And here is the generated R file using createDataDef and publishStructures: DataDefBlock 2 = /* struct feature */ { {DTYPE_STRUCT, 1, 0, DTYPE_DOUBLE}, {DTYPE_ARRAY, 0, 512, 1}, /* feaName */ {DTYPE_SHORT, 1, ATTR_S_LE, FIRSTMEM | S_ALIGN(DTYPE_DOUBLE) | ARRAYMEM}, /* */ {DTYPE_LONG, 1, ATTR_L_LE, 0}, /* areaFeaLevelCode */ {DTYPE_LONG, 1, ATTR_L_LE, 0}, /* areaFeaColor */ {DTYPE_LONG, 1, ATTR_L_LE, 0}, /* areaFeaWeight */ {DTYPE_LONG, 1, ATTR_L_LE, 0}, /* areaFeaStyle */ {DTYPE_LONG, 1, ATTR_L_LE, 0}, /* areaDoBorder */ {DTYPE_DOUBLE, 1, ATTR_D_LE, 0}, /* areaBorderWidth */ {DTYPE_LONG, 1, ATTR_L_LE, 0}, /* areaDoBackground */ {DTYPE_LONG, 1, ATTR_L_LE, 0}, /* areaDoSingleHatch */ {DTYPE_DOUBLE, 1, ATTR_D_LE, 0}, /* areaShatchSpacing */ {DTYPE_LONG, 1, ATTR_L_LE, 0}, /* areaShatchAngle */ {DTYPE_LONG, 1, ATTR_L_LE, 0}, /* areaDoCrossHatch */ {DTYPE_DOUBLE, 1, ATTR_D_LE, 0}, /* areaChatchSpacing1 */ {DTYPE_LONG, 1, ATTR_L_LE, 0}, /* areaChatchAngle1 */ {DTYPE_DOUBLE, 1, ATTR_D_LE, 0}, /* areaChatchSpacing2 */ {DTYPE_LONG, 1, ATTR_L_LE, 0}, /* areaChatchAngle2 */ {DTYPE_LONG, 1, ATTR_L_LE, 0}, /* areaDoPattern */ {DTYPE_LONG, 1, ATTR_L_LE, 0}, /* areaPatternAngle */ {DTYPE_DOUBLE, 1, ATTR_D_LE, 0}, /* areaPatternRSpace */ {DTYPE_DOUBLE, 1, ATTR_D_LE, 0}, /* areaPatternCSpace */ {DTYPE_DOUBLE, 1, ATTR_D_LE, 0}, /* areaPatternScale */ {DTYPE_ARRAY, 0, 512, 1}, /* areaPatternCell */ {DTYPE_SHORT, 1, ATTR_S_LE, ARRAYMEM}, /* */ {DTYPE_LONG, 1, ATTR_L_LE, 0}, /* areaDoMultiHatch */ {DTYPE_DOUBLE, 1, ATTR_D_LE, 0}, /* areaMhatchWidth1 */ {DTYPE_DOUBLE, 1, ATTR_D_LE, 0}, /* areaMhatchWidth2 */ {DTYPE_DOUBLE, 1, ATTR_D_LE, 0}, /* areaMhatchWidth3 */ {DTYPE_LONG, 1, ATTR_L_LE, 0}, /* areaMhatchAngle */ {DTYPE_DOUBLE, 1, ATTR_D_LE, 0}, /* areaMhatchSpacing */ {DTYPE_LONG, 1, ATTR_L_LE, 0}, /* areaMhatchDraw1 */ {DTYPE_LONG, 1, ATTR_L_LE, 0}, /* areaMhatchDraw2 */ {DTYPE_LONG, 1, ATTR_L_LE, 0}, /* areaMhatchDraw3 */ {DTYPE_LONG, 1, ATTR_L_LE, 0}, /* areaDispDoGroup */ {DTYPE_LONG, 1, ATTR_L_LE, 0}, /* bckDispLevelCode */ {DTYPE_LONG, 1, ATTR_L_LE, 0}, /* borDispLevelCode */ {DTYPE_LONG, 1, ATTR_L_LE, 0}, /* shtDispLevelCode */ {DTYPE_LONG, 1, ATTR_L_LE, 0}, /* chtDispLevelCode */ {DTYPE_LONG, 1, ATTR_L_LE, 0}, /* mh1DispLevelCode */ {DTYPE_LONG, 1, ATTR_L_LE, 0}, /* mh2DispLevelCode */ {DTYPE_LONG, 1, ATTR_L_LE, 0}, /* mh3DispLevelCode */ {DTYPE_LONG, 1, ATTR_L_LE, 0}, /* symDispLevelCode */ {DTYPE_LONG, 1, ATTR_L_LE, 0}, /* areaIncludeAsArea */ {DTYPE_ARRAY, 0, 512, 1}, /* feaCode */ {DTYPE_SHORT, 1, ATTR_S_LE, ARRAYMEM}, /* */ {DTYPE_ENDSTRUCT, 1, DTYPE_SHORT, DTYPE_DOUBLE} }; CexprMemberList 1 = {{ {0xc0020008, 0, 37, 0x45003163}, /* feaName */ {0x3, 1024, 38, 0x2e64ea61}, /* areaFeaLevelCode */ {0x3, 1028, 39, 0x8064e08}, /* areaFeaColor */ {0x3, 1032, 40, 0x750c9e18}, /* areaFeaWeight */ {0x1, 1036, 41, 0x2064f51}, /* areaFeaStyle */ {0x1, 1040, 42, 0x10064e4c}, /* areaDoBorder */ {0x2, 1048, 43, 0x7d329518}, /* areaBorderWidth */ {0x1, 1056, 44, 0x1264d7cc}, /* areaDoBackground */ {0x1, 1060, 45, 0x50ca09a6}, /* areaDoSingleHatch */ {0x2, 1064, 46, 0x73cb01cf}, /* areaShatchSpacing */ {0x1, 1072, 47, 0x7332bf19}, /* areaShatchAngle */ {0x1, 1076, 48, 0x3464f126}, /* areaDoCrossHatch */ {0x2, 1080, 49, 0x539403cf}, /* areaChatchSpacing1 */ {0x1, 1088, 50, 0x5264fe63}, /* areaChatchAngle1 */ {0x2, 1096, 51, 0x509403d0}, /* areaChatchSpacing2 */ {0x1, 1104, 52, 0x5164fe64}, /* areaChatchAngle2 */ {0x1, 1108, 53, 0x740c9f66}, /* areaDoPattern */ {0x1, 1112, 54, 0x1e657719}, /* areaPatternAngle */ {0x2, 1120, 55, 0x49caef1f}, /* areaPatternRSpace */ {0x2, 1128, 56, 0x58caed3f}, /* areaPatternCSpace */ {0x2, 1136, 57, 0x76577c9}, /* areaPatternScale */ {0xc0020008, 1144, 58, 0x7932bb50}, /* areaPatternCell */ {0x1, 2168, 59, 0x236505a6}, /* areaDoMultiHatch */ {0x2, 2176, 60, 0x5b6550e1}, /* areaMhatchWidth1 */ {0x2, 2184, 61, 0x586550e2}, /* areaMhatchWidth2 */ {0x2, 2192, 62, 0x596550e3}, /* areaMhatchWidth3 */ {0x1, 2200, 63, 0x6d32a719}, /* areaMhatchAngle */ {0x2, 2208, 64, 0x6dcaa1cf}, /* areaMhatchSpacing */ {0x1, 2216, 65, 0x3d32a733}, /* areaMhatchDraw1 */ {0x1, 2220, 66, 0x3e32a734}, /* areaMhatchDraw2 */ {0x1, 2224, 67, 0x3f32a735}, /* areaMhatchDraw3 */ {0x1, 2228, 68, 0x4d328ef6}, /* areaDispDoGroup */ {0x3, 2232, 69, 0x3f620861}, /* bckDispLevelCode */ {0x3, 2236, 70, 0x2a65e861}, /* borDispLevelCode */ {0x3, 2240, 71, 0x3a6ce861}, /* shtDispLevelCode */ {0x3, 2244, 72, 0x2a64e861}, /* chtDispLevelCode */ {0x3, 2248, 73, 0x61618861}, /* mh1DispLevelCode */ {0x3, 2252, 74, 0x6261a861}, /* mh2DispLevelCode */ {0x3, 2256, 75, 0x6361c861}, /* mh3DispLevelCode */ {0x3, 2260, 76, 0x32704861}, /* symDispLevelCode */ {0x1, 2264, 77, 0x4eca988b}, /* areaIncludeAsArea */ {0xc0020008, 2268, 78, 0x4f003131}, /* feaCode */ }};https://communities.bentley.com/products/geotechnical1/w/openground-wiki/54020/template-studio-release-notesTue, 12 Dec 2023 14:00:00 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:54020Dan Roberts/products/geotechnical1/w/openground-wiki/54020/template-studio-release-notesThe below information will take you through the updates that are specific to this application. For more general information and product update videos, please see the general New Release page. v 10.0.1.1915 Released 12th December 2023 Fixed a bug where it wasnt possible to add decimals to fields in the UI v 10.0.1.1909 Released 6th November 2023 Updated the User Guide link as well as the order of the help icons v 10.0.1.1904 Released 5th December 2023 Fixed a bug where the point data image image and range image were removed v 10.0.1.1893 Released 30th November 2023 Security update for application v 10.0.1.1873 Released 14th November 2023 Implemented Location Clusters functionality for logs, enabling the display of data from both primary and associated locations. v 10.0.1.1837 Released 20th October 2023 Fixed a bug where previewing a combined log for a location type that had been removed or renamed resulted in the app crashing v 10.0.1.1827 Released 9th October 2023 Fixed a bug where elevation is incorrect on a quick section if the strip height was modified. v 10.0.1.1821 Released 5th October 2023 Fixed a bug where text boxes would not persist changes if the user edited and saved log immediately without changing focus to a different merged cell. v 10.0.1.1816 Released 28th September 2023 Fixed a bug with templates not previewing in some instances where they contain range text library items v 10.0.1.1807 Released 11th September 2023 Added document xml version to prevent features added to newer versions of studio from being opened with older versions that do not have this feature. Added support for new Callouts feature on range items v 10.0.1.1798 Released 6th September 2023 Bug fix to show a message when a user is trying to open the app on a cloud where the user is not active in. v 10.0.1.1764 Released 8th August 2023 General app stability update v 10.0.1.1737 Released 19th July 2023 Fixed a bug where an image uploaded directly via template images was not recognized when adding the static image library item. v 10.0.1.1728 Released 13th July 2023 New library Items added for depth area: "Point Image" and "Range Image" These new library items allow the adding of down borehole images at depth on a borehole log v 10.0.1.1724 Released 5th July 2023 Fixed a bug where Legend Block was available for all templates. Legend Block is now disabled for Header Sheet, Site Plan, Strip, Quick Section and Civils Section. v 10.0.1.1720 Released 30th June 2023 Fixed a bug where Template Studio would lock up after a longer period of time v 10.0.1.1710 Released 15th June 2023 Updated the template xml reader compatibility for future template enhancements v 10.0.1.1705 Released 14th June 2023 Fixed a bug where the preview of a template with Range Text Bar element wouldn't load after saving v 10.0.1.1700 Released 12th June 2023 Functionality implementation of Customisable Legends used on logs and a new dynamic template called a Project Sheet. Please see these articles for more information: Project Sheets Template Studio and Project Sheets and Legend Blocks v10.0.1.1652 Released 15th May 2023 Fixed the clipboard functionality Increased default zoom level for strips preview to 150% v10.0.1.641 Released 14th March 2023 Support for enabling log generation for Project level Master Template and Strips Sets v10.0.1.506 Released 14th March 2023 Fixed a bug where log with image grid wouldn't preview on initial load v10.0.1.489 Released 20th February 2023 CEFSharp integration for log template previews Bug fix for text visibility on Quick log to show continue text on Dynamic Logs where strips hide condition applied Bug fix for header sheets preview Bug fix where Follow-on Mode prevented previewing if Header and Footer remained the same v10.0.1.478 Released 19th January 2023 Fixed a bug with a follow on scale issue v10.0.1.475 Released 16th January 2023 Displaying a banner to access US government clouds Prompt user re-authentication after period of inactivity Fixed a bug where local save overwrites configuration pack template v10.0.1.456 Released 8th November 2022 Enable app to connect to commercial and government clouds FEDRAMP compliance application shut down logging v10.0.1.451 Released 26th October 2022 Fixed a bug with log presentation showing the log squashed in half v10.0.1.449 Released 12th October 2022 FIPS compliant app update v10.0.1.424 Released 19th August 2022 Added the ability to show the template that is currently open in the top of the window alongside the cloud name. v10.0.1.421 Released 13th July 2022 Fixed a bug where office/project logos wouldn't show on site plans v10.0.1.416 Released 16th June 2022 App updated after config pack model enhancements v10.0.1.414 Released 31st May 2022 Fixed a longstanding issue with problems authenticating due to netwonsoft installation v10.0.1.408 Released 19th May 2022 Updated app due to mandatory update required for data collector update 3 v10.0.1.404 Released 13th May 2022 Fixed a bug where users with project level configurations role couldn't save Ciivls Sections to a Project only Locally v10.0.1.397 Released 5th May 2022 Updated app in line with security update to infrastructure v10.0.1.367 Released 17th February 2022 updated in line with infrastructure improvements v10.0.1.361 Released 20th January 2022 Changed the wording of the strip options dialog to say "hide condition" instead of "visibility condition. This change should make it more obvious what the feature does as it is for hiding strips on logs v10.0.1.357 Released 12th November 2021 Added new runtime functions that can pull out the current Template name and Strip Set name. (Information Here ) Fixed a bug with repeating detailed descriptions which carried over 3 pages. v10.0.1.354 Released 19th October 2021 Fixed an issue where strips couldnt be saved because the groups were missing from range text boxes v10.0.1.352 Released 28th September 2021 Fixed issue with viewing project/office logo images on Templates v10.0.1.348 Released 20th August 2020 Fixed a bug where deleting strip sets from a master template saved under a different name to an existing one would also delete them from the original. Now when you save an existing master template with a new name all strip sets in the new template will have this marker after the name (1). This can be changed at any point. v10.0.1.346 Released 06th August 2021 Updated app to support migration to Azure Cloud infrastructure with fixes from previous 336 release which includes a fix for using table names title and not description in group selection. v10.0.1.336 Released 22nd June Fixed a bug which would prevent logs from being previewed in some circumstances as loading the template would remove the group associated with the added library item. v.10.0.1.291 Released 30th March 2021 Fixed a bug where the group name would show as the description for the group instead of the title Added a new checkbox to Dynamic Logs so it uses the first page header on log transition v.10.0.1.273 Released 11th January 2021 Fixed a visual bug with resizing depth columns, when columns were increased and then later decreased it could make the original columns look larger. This didnt affect the actual log preview. Fixed a bug where data label headers didnt show when the strip had more than one level in the header on Quick Sections Fixed a bug where bar charts border styling options were not being respected. Changed the Legend image drop down to now show the picklist groups associated with only the tables linked on the strips when used for Quick Sections. Improved the expressions engine allowing the query display of Project Config Packs and Picklist Sets on headers or footers v.10.0.1.264 Released 04th January 2021 This update contains the database model updates for AGS 4.0.4 changes. These changes have been communicated in the following communities article: https://communities.bentley.com/products/geotechnical1/b/geoblog/posts/openground-cloud-and-holebase-connect-edition-database-model-upgrades Fixed a bug with master fonts. The ribbon font list now uses the same source for fonts but the drop-down will remain blank unless a font is set, unlike before when 'Calibri' would be shown. v.10.0.1.257 Released 24th November 2020 Fixed a bug where the correct options were not available for the range text bar library item Fixed a bug which would crash Studio if a hbt was loaded which contained templates that didnt exist in that config pack. v.10.0.1.252 Released 12th November 2020 Added a fit to width checkbox for strips with graphic items this option now scales by X and tiles by Y resizing the hatch patterns. Added a last of index function to the expressions engine Example: LocationDetails Phase field = A+B+C. Expression: mid([LocationDetails.Phase], FindLast('+', [LocationDetails.Phase], len([LocationDetails.Phase]) - 1) + 1, len([LocationDetails.Phase])) The result = C Fixed a bug which prevented the header or footer area from being increased unless follow on mode was enabled. v.10.0.1.244 Released 26th October 2020 Fixed a bug where logs were always being saved to the Project when the Config Pack option was selected. v.10.0.1.240 Released 22nd October 2020 Added abliity to set negative increments for barcharts Fixed issue where log wouldnt preview when a monitoring pipe library item was added without a instrument type set in Professional Fixed an issue where log wouldnt preview if it contained a strip with a rotated text box which also had boundary line set v.10.0.1.232 Released 14th October 2020 Added new checkbox option in the strips depth column dialog which can only be be used on civil sections that enables the application of a centre point for the civils header label. This change is to solve an issue where if the strip had more than two columns the label would always be shown offset and unable to aligh with the initial columns. v.10.0.1.229 Released 25th September 2020 Fixed a bug with follow on headers and footers where the first page header or footer would be the size of the follow on instead. v.10.0.1.225 Released 12th August 2020 Added enhancements for Dynamic Logs to show values from strips on first page, last page or first and last. Merge option added to Dynamic Log dialog for when data changes based on type. v.10.0.1.204 Released 02nd July 2020 Fixed an issue where it wasn't possible to made adjustments to the header and footer area mm sizing of logs/sections v.10.0.1.196 Released 12th June 2020 Fixed an issue where the save template button was still active after pressed, this meant users could double press it which would cause Studio to crash and the log corrupted. v.10.0.1.193 Released 10th June 2020 Improved error messaging on log preview. If a log fails to preview messaging will be displayed for the following conditions: Missing field validation and Image grid sizing out of bounds v.10.0.1.187 Released 28th May 2020 App stability updates Restyled the icons when the window is shrunk Release of OpenGround Cloud Released 25th April 2020 Release of OpenGround Cloud and related applications Fix for speed issues on Project and Template list loading All of the notes below are relating to Keynetix.cloud and related products. These are included here for historic purposes. v10.0.1.153 Released 30th March 2020 Added validation into the Dynamic Log dialog so that it will prevent preview if incorrect syntax is used in the expression dialog Fixed a bug where if you had a blank Template Type in the Dynamic Template dialog it would crash. Now it asks for a valid entry Fixed a bug where having small grids for a log follow on would previously show as medium Fixed a bug which stopped logs from previewing when a strip hide condition was used. v10.0.1.140 Released 26th February 2020 Improved first page/follow on template setup by adding greater precision to units per page. field is now decimalised. fixed a bug where scale wouldn't show the numbers under certain scale alignment settings v10.0.1.136 Released 11th February 2020 Added a new feature for Headers and Footers called, First Page and Follow On. The First Page Follow-on functionality allows for a different first page to be used compared to the rest of the log template. For example, this allows for a bigger header and footer area to be used on the first page of the log template, with a smaller area assigned to these on the following pages, allowing for more depth area to be shown. v10.0.1.124 Released 21st January 2020 Fixed a bug affecting editing of tables causing the application to terminate. v10.0.1.110 Released 13th December 2019 Fixed a bug with previewing site plans. See user guide for information on how to use the new functionality by clicking here . v10.0.1.108 Released 11th December 2019 This release contains addition of new template type called "Dynamic Templates" See user guide for information on how to use the new functionality by clicking here . v10.0.1.94 Released 29th November 2019 Updated App for change to API and enhanced Security v10.0.1.83 Released 11th July 2019 Fixed display of connector symbols being used for range symbols on logs where previously if the connector carried on to the next page it would not be displayed. (Tile Y Selection only) Fixed a bug with displaying the ground scale values correctly if the hole had any inclination values applied. v10.0.1.81 Released 20th May 2019 Fixed a bug with quicklogs/log reports displaying. The bug would prevent previewing of the template where there was a vertical scale added which had the flag set for display ground level scale and the locations ground level was greater than 0 but less than 1. Fixed a bug with combined logs displaying duplicate data for range text box items where the data is on the transition depth. v10.0.1.78 Released 16th April 2019 Fixed a bug with combined logs displaying duplicated and squashed data when a straight line is used as the log transitions to next type. Increased app security. v10.0.1.74 Release 02nd April 2019 Fixed an bug with overwriting templates with the same name under the following scenario: Borehole Log 1 saved as a standard Borehole Log Template. Borehole Log 2 saved as Borehole Log 1 but as a Master Template. The template will be overwritten but in Enterprise you will see two templates with the same name. (please note that this change does mean that any template type saved with the same name as a different type of template will overwrite the previous one. For example saving a log as Test Log and a Site Plan as Test Log will mean the original log will be overwritten to become a site plan with the name Test Log.) v10.0.1.72 Released 13th March 2019 Fixed an issue affecting the installer when used on Windows 7. App would not launch due to missing file in the installer package. v10.0.1.70 Released 11st March 2019 App is updated be compatible with updates to the Keynetix.Cloud API v10.0.1.65 Released 1st March 2019 Fixed an issue with saving changes to existing templates where the save dialog would hang. v10.0.1.63 Released 28th February 2019 Improved the loading times of the template list. Retrieval of all available templates is now quicker. v10.0.1.61 Released 28th January 2019 App is updated be compatible with updates to the Keynetix.Cloud API v10.0.1.59 Release 19th November 2018 App is updated to support the enhanced security changes to cloud infrastructure. v10.0.1.58 Released 1st October 2018 Added Master Template Support. Fixed a bug where the groups selection for creating filter groups wasnt displaying the names instead would be blank. Fixed a bug where if you added a office field as a data label text but didnt have an office linked to the project Studio would display a record from the Location Details group. The top bar will now show what cloud is currently being used.https://communities.bentley.com/products/offshore/w/wiki/29967/sacs-executive-solutionsTue, 12 Dec 2023 06:19:00 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:29967Nurfaiza Mat/products/offshore/w/wiki/29967/sacs-executive-solutionsThis contains SACS wikis related to the SACS Executive program. 1. Getting Started with SACS 2. Legacy Modeler not working? 3. Change SACS Default Text Editor to Notepad++ 4. Enabling 64-Bit Precede in SACS 5. Enabling SACS License Preview in SACS 11.0+ 6. Working with the SACS Reports Database 7. Getting Started with Combined Postvue Database 8. External Editor File for SACS V23 9. Greyed Area 10. How to create your own Section Library? 11. Monitor Resolution Issue 12. Problem to run analysis in SACS 2023 13. SESAM to SACS Converter 14. Error on Illegal Load Case Selection 15. SACS to STAAD Conversion 16. Import to SACS 17. Arrange commands in alphabetical orderhttps://communities.bentley.com/products/pipe_stress_analysis/w/pipe_stress_analysis__wiki/69890/q20-digits-of-decimals-for-length-column-in-point-connectivity-section-is-not-aligned-with-value-given-in-edit-model-option-whyTue, 12 Dec 2023 05:59:00 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:69890Tanaji Gaikwad/products/pipe_stress_analysis/w/pipe_stress_analysis__wiki/69890/q20-digits-of-decimals-for-length-column-in-point-connectivity-section-is-not-aligned-with-value-given-in-edit-model-option-whyApplies To Product(s): AutoPIPE Version(s): ALL Area: Report Date Logged & Current Version Dec 2023 23.00.00.230 Problem: Digits of decimals for length column in Point Connectivity section is not aligned with value given in Edit Model Option, Why? Input: Output: Solution: Software is working as designed and user can change the decimal places for length column as per there requirement. Follow the steps given below, Step 1: Enter the required digits after decimal points in Edit model option, Step 2: Open the report template file (PointConnectivityDataTemplate.xml) from path: C:\Program Files (x86)\Bentley\AutoPIPE 2023\ReportTemplates\Text Step 3: Open the PonitConnectivityDataTemplate.xml file in any text editor (like Notepad++) and go to the Length section, Step 4: Copy the line number 104 (Marked in Red) and replace line number 80 and 92 with line number 104 as shown in above image. Save the file and run the analysis and you will get the required digits after decimal points in point connectivity report. See Also Report AutoPIPE Bentley LEARN Serverhttps://communities.bentley.com/products/microstation/w/microstation_-_wiki_jp/40438/00-itwin-capture-modelerTue, 12 Dec 2023 01:55:00 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:40438MTabata/products/microstation/w/microstation_-_wiki_jp/40438/00-itwin-capture-modelerプロダクト: iTwin Capture Modeler バージョン: 2023 環境: N\A エリア: インストール サブエリア: N\A ContextCaptureの製品名・ライセンス名称が「iTwin Capture Modeler」 変更されました。 資格グループ、警告メッセージの製品名も自動的にiTwin Capture Modelerに変更されます。 詳細に関しましては、 iTwin Capture Modeler FAQ 　サイトをご参照ください。 iTwin Capture Modeler2023 のインストール方法について以下をご参照ください。 ＜ 手 順 ＞ ① iTwin Capture Modeler2023のソフトウェアをダウンロードします。 検索対象を以下の様に変更します。「適用」を押します。 バージョン： 23.00.03.10 言語： Japanese 製品の種類： Language Pack ② iTwin Capture Modelerの英語版を先にインストールします。 iTwinCaptureModeler _ _en.exe　の英語版インストーラを右クリックし「管理者として実行」でインストールします。 次に、 iTwinCaptureModeler _ _ ja.exe 　日本語言語 パックを右クリックし「管理者として実行」でインストールします。 （日本語のフルインストーラはございません） （※）日本語言語 パックをインストール時に「Modify Setup」と表示された場合には、「Uninstall」を実行してレジストリ情報を削除し、再度インストーラを起動してください。 ③ CONNECTION Clientにサインインします。 詳細につきましては、以下のインストール方法についてのPDFをご参照ください。 communities.bentley.com/.../iTwinCaptureModelerInstallDoc20231212.pdf 日本語ドキュメントは、日本語Language Packをインストールされると基本操作に関する英語名.pdfは日本語版に上書きされます。 C:\Program Files\Bentley\iTwin Capture Modeler\doc 2023より「新規キャプチャ」を選択してから新規Blockが表示されるように変更されています。 ContextCapture 2023 User Guide 日本語版は、以下よりダウンロードして頂けます。 communities.bentley.com/.../ContextCapture-User-Guide-2023_5F00_ja.pdf Original Author: Mikihiko Tabatahttps://communities.bentley.com/products/assetwise/asset_performance_management/w/wiki/35113/debugging-report-design-problemsMon, 11 Dec 2023 22:05:00 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:35113Joseph Marin/products/assetwise/asset_performance_management/w/wiki/35113/debugging-report-design-problemsProduct(s): AssetWise Asset Reliability Version(s): 6.2+ Environment: ODC Area: N/A Subarea: N\A Problem e.g, Report design will not save. Solution Open the Settings Editor for the thick-client instance used for the report design, and add the following logging: Open the Settings Editor for the thick-client instance. Click on the Logging tab. On the What to Log tab, click on the New Rule toolbar button ( ), and select the New Empty Rule option. On the New Rule dialog, enter Ivara.Client.Designer.Reports.* in the name property, and set minlevel to Debug . On the What to Log tab, click on the New Rule toolbar button, and select the New Empty Rule option. On the New Rule dialog, enter Ivara.Reporting.* in the name property, and set minlevel to Debug . Click the Save button on the Settings Editor dialog. Close the Settings Editor dialog. Create/Open the report, make the required revisions. Save & Exit the report dessigner. Review the thick client's log file, looking for messages that pertain to the new rules. If you require assistance the the log file review, please submit a Service Request to APM Support clearly stating the problem area, if there is no current service request. Attach the thick-client log to the Service Request. NOTE: After messages have been logged for the problem, remember to turn off logging for the new rules. This can be accomplished by returning to the Settings Editor utility, and deleting the Ivara.Client.Designer.Reports.* and Ivara.Reporting.* logging rules. The change will be effective immediately, so there is no need to stop & restart the thick-clientinstance. See Also How to log APM messages to a custom file target